bleeding edge repo

What’s the best way to enable Joe’s bleed repo listed here: http://www.virtualmin.com/documentation/id,virtualmin_bleeding_edge_packages/

Is there a way to enable it just for PHP?

FYI, I created a vmbleed fle with the below config inside the yum.repos.d dir.

[vmbleed] name=vmbleed RHEL/ CentOS $releasever - $basearch baseurl=http://software.virtualmin.com/bleed/centos/5/i386/ enabled=1 gpgcheck=0

Then i get this error:
Loading "fastestmirror" plugin

Error getting repository data for vmbleed, repository not found

Suggestions?

I think that should work. That URL seems correct to me. I’ll test it, and get back to you. I’m working on an updated PHP for that repo anyway.

I’ve used up my brain power on this one, I eagerly await your findings Joe. I want to setup a Magento store and can’t w/o the PHP 5.2+.

Thanks!

The following repo file worked for me to replace the stock centos 5.1.6 packages with your php-[*-]5.2.6-1.el5.vmbleed.i386.rpm packages:

[vmbleed]
name=vmbleed RHEL/ CentOS $releasever - $basearch
baseurl=http://software.virtualmin.com/bleed/centos/5/i386/
enabled=1
gpgcheck=0
includepkgs=php*

HOWEVER, since doing that I see that you have added php-[*-]5.2.8-1.el5.vmbleed.i386.rpm packages to the repo. When I run yum update, yum does not detect the new packages. It seems that the files in /bleed/centos/5/i386/repodata have not been updated to list the new packages. Is this deliberate?

Can you give me the settings for x64?

Thanks

[vmbleed]
name=vmbleed RHEL/ CentOS $releasever - $basearch
baseurl=http://software.virtualmin.com/bleed/centos/5/x86_64/
enabled=1
gpgcheck=0
includepkgs=php*

Sorry for answering my own post; this is for other users that might find this.

HOWEVER, since doing that I see that you have added php-[*-]5.2.8-1.el5.vmbleed.i386.rpm packages to the repo. When I run yum update, yum does not detect the new packages. It seems that the files in /bleed/centos/5/i386/repodata have not been updated to list the new packages. Is this deliberate?

I seem to be having a similar problem updating php 5.2.6 to 5.2.8 as well…

I suspect that was purely an oversight.

I’ll shoot Joe an email to make sure that the repo data is updated :wink:
-Eric

Thanks Eric.