Hi all,
I have attached a backport of reposync from yum-utils CVS to yum 2.4 in CentOS 4. There may still be a bug luring here or there, but it would be nice to hear if it works for others.
Thanks, Daniel
On Fri, 2007-04-27 at 11:44 +0200, Daniel de Kok wrote:
Hi all,
I have attached a backport of reposync from yum-utils CVS to yum 2.4 in CentOS 4. There may still be a bug luring here or there, but it would be nice to hear if it works for others.
Thanks, Daniel
Thanks to Daniel for this backport :P
We will be adding this to yum-utils after we give it some testing ... so lets get it tested and we can move forward from there.
Thanks, Johnny Hughes
On 4/27/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Fri, 2007-04-27 at 11:44 +0200, Daniel de Kok wrote:
Hi all,
I have attached a backport of reposync from yum-utils CVS to yum 2.4 in CentOS 4. There may still be a bug luring here or there, but it would be nice to hear if it works for others.
Thanks, Daniel
Thanks to Daniel for this backport :P
We will be adding this to yum-utils after we give it some testing ... so lets get it tested and we can move forward from there.
Seems to work for me on CentOS 4 i386. I suppose, by design, it does not check to see if a repo is already "local" or not. I have a mix of "local" repos and remote ones. When I did a test run with a 'reposync.py -u', it grabbed everything. Of course, the same thing happens with the version on CentOS 5.
Akemi
On Fri, 27 Apr 2007 17:37:01 -0700 "Akemi Yagi" amyagi@gmail.com wrote:
Seems to work for me on CentOS 4 i386. I suppose, by design, it does not check to see if a repo is already "local" or not. I have a mix of "local" repos and remote ones. When I did a test run with a 'reposync.py -u', it grabbed everything. Of course, the same thing happens with the version on CentOS 5.
Correct. This version should behave exactly like reposync in CentOS5. Normally, you'll want to use it with the --repoid parameter to explicitly specify the repositories that you would like to sync.
Thanks for testing this!
-- Daniel
On 4/28/07, Daniel de Kok danieldk@pobox.com wrote:
On Fri, 27 Apr 2007 17:37:01 -0700 "Akemi Yagi" amyagi@gmail.com wrote:
Seems to work for me on CentOS 4 i386. I suppose, by design, it does not check to see if a repo is already "local" or not. I have a mix of "local" repos and remote ones. When I did a test run with a 'reposync.py -u', it grabbed everything. Of course, the same thing happens with the version on CentOS 5.
Correct. This version should behave exactly like reposync in CentOS5. Normally, you'll want to use it with the --repoid parameter to explicitly specify the repositories that you would like to sync.
Thanks for that info (-repoid). How do you specify more than one?
Akemi
On Sat, 28 Apr 2007 03:24:25 -0700 "Akemi Yagi" amyagi@gmail.com wrote:
Thanks for that info (-repoid). How do you specify more than one?
Multiple --repoid parameters are additive. For example:
reposync -n --repoid=updates --repoid=extras
I wrote a short manual page for reposync, I'll add some examples to that as well.
-- Daniel
On 4/28/07, Daniel de Kok danieldk@pobox.com wrote:
On Sat, 28 Apr 2007 03:24:25 -0700 "Akemi Yagi" amyagi@gmail.com wrote:
Thanks for that info (-repoid). How do you specify more than one?
Multiple --repoid parameters are additive. For example:
reposync -n --repoid=updates --repoid=extras
I wrote a short manual page for reposync, I'll add some examples to that as well.
-- Daniel
Thanks. That will help.
Akemi
On Sat, 2007-04-28 at 12:36 +0200, Daniel de Kok wrote:
On Sat, 28 Apr 2007 03:24:25 -0700 "Akemi Yagi" amyagi@gmail.com wrote:
Thanks for that info (-repoid). How do you specify more than one?
Multiple --repoid parameters are additive. For example:
reposync -n --repoid=updates --repoid=extras
I wrote a short manual page for reposync, I'll add some examples to that as well.
have you considered sending these items upstream?
-sv
Hi Seth,
On Sat, 28 Apr 2007 08:19:55 -0400 seth vidal skvidal@linux.duke.edu wrote:
On Sat, 2007-04-28 at 12:36 +0200, Daniel de Kok wrote:
Multiple --repoid parameters are additive. For example:
reposync -n --repoid=updates --repoid=extras
I wrote a short manual page for reposync, I'll add some examples to that as well.
have you considered sending these items upstream?
Yes, I planned submitting patches after testing things here.
-- Daniel
PS. <ot>I just submitted a patch for adding a GPG signature option for reposync to the yum bugzilla.</ot>
On Sat, 2007-04-28 at 14:23 +0200, Daniel de Kok wrote:
Hi Seth,
On Sat, 28 Apr 2007 08:19:55 -0400 seth vidal skvidal@linux.duke.edu wrote:
On Sat, 2007-04-28 at 12:36 +0200, Daniel de Kok wrote:
Multiple --repoid parameters are additive. For example:
reposync -n --repoid=updates --repoid=extras
I wrote a short manual page for reposync, I'll add some examples to that as well.
have you considered sending these items upstream?
Yes, I planned submitting patches after testing things here.
Good, thanks.
-- Daniel
PS. <ot>I just submitted a patch for adding a GPG signature option for reposync to the yum bugzilla.</ot>
Yeah, it was assigned to tim. Should be all set.
-sv
On Sat, 2007-04-28 at 08:42 -0400, seth vidal wrote:
On Sat, 2007-04-28 at 14:23 +0200, Daniel de Kok wrote:
Hi Seth,
On Sat, 28 Apr 2007 08:19:55 -0400 seth vidal skvidal@linux.duke.edu wrote:
On Sat, 2007-04-28 at 12:36 +0200, Daniel de Kok wrote:
Multiple --repoid parameters are additive. For example:
reposync -n --repoid=updates --repoid=extras
I wrote a short manual page for reposync, I'll add some examples to that as well.
have you considered sending these items upstream?
Yes, I planned submitting patches after testing things here.
Good, thanks.
-- Daniel
PS. <ot>I just submitted a patch for adding a GPG signature option for reposync to the yum bugzilla.</ot>
Yeah, it was assigned to tim. Should be all set.
-sv
Seth,
We had a need for this app on CentOS-4 ... we want it to do what it already does in the newer versions. I would have thought that the guys who wrote it would have already done it for the CentOS-4 version of python if they were interested in providing it there too :D
Are you interested in backport type things like this to yum-utils and other aps (for older versions)?
If yes, we are certainly glad to provide that info.
Thanks, Johnny Hughes
On Sat, 28 Apr 2007, Johnny Hughes wrote:
We had a need for this app on CentOS-4 ... we want it to do what it already does in the newer versions. I would have thought that the guys who wrote it would have already done it for the CentOS-4 version of python if they were interested in providing it there too :D
Are you interested in backport type things like this to yum-utils and other aps (for older versions)?
If yes, we are certainly glad to provide that info.
Johnny, why not include CentOS 3 as well ?
python 1.5 is definitely too old, but python 2.2 must be within reach.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
On Sat, 2007-04-28 at 18:11 +0200, Dag Wieers wrote:
On Sat, 28 Apr 2007, Johnny Hughes wrote:
We had a need for this app on CentOS-4 ... we want it to do what it already does in the newer versions. I would have thought that the guys who wrote it would have already done it for the CentOS-4 version of python if they were interested in providing it there too :D
Are you interested in backport type things like this to yum-utils and other aps (for older versions)?
If yes, we are certainly glad to provide that info.
Johnny, why not include CentOS 3 as well ?
python 1.5 is definitely too old, but python 2.2 must be within reach.
too much work, not enough benefit.
-sv
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
seth vidal a écrit :
On Sat, 2007-04-28 at 18:11 +0200, Dag Wieers wrote:
On Sat, 28 Apr 2007, Johnny Hughes wrote:
We had a need for this app on CentOS-4 ... we want it to do what it already does in the newer versions. I would have thought that the guys who wrote it would have already done it for the CentOS-4 version of python if they were interested in providing it there too :D
Are you interested in backport type things like this to yum-utils and other aps (for older versions)?
If yes, we are certainly glad to provide that info.
Johnny, why not include CentOS 3 as well ?
python 1.5 is definitely too old, but python 2.2 must be within reach.
too much work, not enough benefit.
-sv
Hello,
too much work to include python2.x in Centos 3 ?
Regards
js.
jean-seb wrote:
too much work to include python2.x in Centos 3 ?
whats wrong with the python-2.x already in there ?
On Sat, 2007-04-28 at 22:39 +0400, jean-seb wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
seth vidal a écrit :
On Sat, 2007-04-28 at 18:11 +0200, Dag Wieers wrote:
On Sat, 28 Apr 2007, Johnny Hughes wrote:
We had a need for this app on CentOS-4 ... we want it to do what it already does in the newer versions. I would have thought that the guys who wrote it would have already done it for the CentOS-4 version of python if they were interested in providing it there too :D
Are you interested in backport type things like this to yum-utils and other aps (for older versions)?
If yes, we are certainly glad to provide that info.
Johnny, why not include CentOS 3 as well ?
python 1.5 is definitely too old, but python 2.2 must be within reach.
too much work, not enough benefit.
-sv
Hello,
too much work to include python2.x in Centos 3 ?
too much work to add features to a distro that's in maintenance/security-only mode.
-sv
seth vidal wrote:
too much work to add features to a distro that's in maintenance/security-only mode.
actually, centos-3 isnt in main mode as yet :) there is going to be a 3.9 release
On Sat, 2007-04-28 at 19:49 +0100, Karanbir Singh wrote:
seth vidal wrote:
too much work to add features to a distro that's in maintenance/security-only mode.
actually, centos-3 isnt in main mode as yet :) there is going to be a 3.9 release
<eyeroll>
So you seriously think of new features being added to centos-3 at this point? -sv
seth vidal wrote:
<eyeroll>
So you seriously think of new features being added to centos-3 at this point?
Not unless someone who wants it offers up a patch, and there is some reasonable assurance that nothing else needs to 'move around to accomodate it'.
Also, your point on C3 being almost in Maint mode needs to be considered - if the distro is going to completely freeze over in 5 - 6 months from now, I'd pass on anything that has a major impact.
- KB
seth vidal a écrit :
On Sat, 2007-04-28 at 22:39 +0400, jean-seb wrote:
too much work to add features to a distro that's in maintenance/security-only mode.
-sv
Maybe for Centos team :)
Because of my work, I'm in charge of Gralinux AS 3. The goal of Centos is to stay "close" to RH: Centos 3 is a RHAS3 clone, Centos4 is a RHAS4 clone; that's not the case for Gralinux AS3 (postfix/mysql come from RHAS4, php5 from RHWS) That's why I "lose" my time to backport things like python24, php5 for the old Gralinux; maybe this work could be useful to Centos ?
RHAS3 (and Centos 3 of course) is a real good distribution, and very stable :) , so backport software to it is not a bad idea I think.
Maybe a little "survey" of "what Centos are you using" could be a good starting point to know if Centos3 could have some backports?
Regards
js.
ps: sorry for my english ...
jean-seb wrote:
Maybe for Centos team :)
Firstly, there seems to be some confusion here - you are asking about the amountof work required to port python-2.x into centos-3 which is odd. Mainly because centos-3 already has a python-2.x.
that's not the case for Gralinux AS3 (postfix/mysql come from RHAS4, php5 from RHWS) That's why I "lose" my time to backport things like python24, php5 for the old Gralinux; maybe this work could be useful to Centos ?
sure, we have a centos-plus repo, have you considered contributing to that ?
RHAS3 (and Centos 3 of course) is a real good distribution, and very stable :) , so backport software to it is not a bad idea I think.
feel free to submit patches, CentOS as a distro will stay close to the distro-objective of being as close to upstream as is reasonable - however, being community and project driven there are enough alternative paths on offer to support 'divergent paths' as long as they remain 'optional' to the user and their use is clearly defined.
Maybe a little "survey" of "what Centos are you using" could be a good starting point to know if Centos3 could have some backports?
I disagree. Surveys of this nature never really bring up a true picture of reality out there. We do have some reasonable idea of what percentage of the users are running C3, and trust me - compared to the number of people using CentOS-4/5 the -3 users are a very small number now.
But that does not mean we dont want to do anything with CentOS-3 anymore - so if you were to submit patches, they will get considered in the right repo/path.
- KB
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Karanbir Singh a écrit :
jean-seb wrote:
Maybe for Centos team :)
Firstly, there seems to be some confusion here - you are asking about the amountof work required to port python-2.x into centos-3 which is odd. Mainly because centos-3 already has a python-2.x.
python2.2 is in upstream. but some software need python24 (fail2ban, zope, recent versions of yum? (<off topic>i hate yum ...</off topic>) )
that's not the case for Gralinux AS3 (postfix/mysql come from RHAS4, php5 from RHWS) That's why I "lose" my time to backport things like python24, php5 for the old Gralinux; maybe this work could be useful to Centos ?
sure, we have a centos-plus repo, have you considered contributing to that ?
Not yet (because of lack of time :)
RHAS3 (and Centos 3 of course) is a real good distribution, and very stable :) , so backport software to it is not a bad idea I think.
feel free to submit patches, CentOS as a distro will stay close to the distro-objective of being as close to upstream as is reasonable
- however, being community and project driven there are enough
alternative paths on offer to support 'divergent paths' as long as they remain 'optional' to the user and their use is clearly defined.
Maybe a little "survey" of "what Centos are you using" could be a good starting point to know if Centos3 could have some backports?
I disagree. Surveys of this nature never really bring up a true picture of reality out there. We do have some reasonable idea of what percentage of the users are running C3, and trust me - compared to the number of people using CentOS-4/5 the -3 users are a very small number now.
small .. very small??
But that does not mean we dont want to do anything with CentOS-3 anymore - so if you were to submit patches, they will get considered in the right repo/path.
- KB
I need to maintain gralinux AS 3 for 2 years, so i will backport stuff from RHAS3 / 5 on it. I will consider your offer soon (could be usefull for the poor Centos3 users :)
Regards
js.
jean-seb wrote:
python2.2 is in upstream. but some software need python24 (fail2ban, zope, recent versions of yum?
your original email indicates 2.x...
(<off topic>i hate yum ...</off topic>) )
feel free to not use it.. no one will mind.
sure, we have a centos-plus repo, have you considered contributing to that ?
Not yet (because of lack of time :)
So you are then in the same situation as Seth, when he pointed out in a way that he didnt have the time to really get into this. I dont think there is such a thing as shortage of time - there are 24 hrs in a day, and thats pretty much every day of every year really. When people say that they 'lack time' I presume it means that their priorities are elsewhere and they would rather be working on something else.
small .. very small??
yes indeed, wont make 2 digits in percentage points
I need to maintain gralinux AS 3 for 2 years, so i will backport stuff from RHAS3 / 5 on it.
CentOS-3 is going to be here for longer than 2 years from now ...
- KB
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Karanbir Singh a écrit :
jean-seb wrote:
python2.2 is in upstream. but some software need python24 (fail2ban, zope, recent versions of yum?
your original email indicates 2.x...
my mistake; python24 :)
(<off topic>i hate yum ...</off topic>) )
feel free to not use it.. no one will mind.
I don't use it :)
sure, we have a centos-plus repo, have you considered contributing to that ?
Not yet (because of lack of time :)
So you are then in the same situation as Seth, when he pointed out in a way that he didnt have the time to really get into this. I dont think there is such a thing as shortage of time - there are 24 hrs in a day, and thats pretty much every day of every year really. When people say that they 'lack time' I presume it means that their priorities are elsewhere and they would rather be working on something else.
The main problem was to take time to: present myself and to know how upload files for Centos team:
That's done now :)
And yes, my priorities was to do other things; but after all, it can by useful (php5 on Centos-3, yeah ;)
A detail: there rpms are in the "main" Gralinux (we use apt-get for updates): so there are supported (contrary Extra repo in Centos)
please find the srpms here (maybe , some of them are in dag/at repo, others from RHEL4, RHWS..):
http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/Bastille-3.0.4-1gral.... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/apachetop-0.12.5-1gra... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/bandwidthd-2.0.1-2gra... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/bash-completion-20050... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/ccze-0.2.1-1gral.src.... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/convmv-1.10-1gral.src... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/courier-imap-3.0.8-3g... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/cyrus-imapd-2.2.12-4g... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/dansguardian-2.8.0.6-... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/dhcp-3.0.1-11.1gral.s... (include dhcpreport.pl) http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/fail2ban-0.6.2-1gral.... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/graphviz-2.2-1gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/iptraf-3.0.0-1gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/john-1.6-1gral.src.rp... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/lzo-1.08-3gral.src.rp... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/mod_cband-0.9.7.4-2gr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/mysql-4.1.12-4gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/mysqlclient10-3.23.58... (to support software linked with mysql3) http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/nagios-1.4.1-1gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/nagios-nrpe-2.4-1gral... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/nagios-nsca-2.5-2gral... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/nagios-plugins-1.4.2-... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/nasm-0.98.38-3.src.rp... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/nessus-2.2.9-1gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/nmap-3.93-3gral.src.r... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/openvpn-2.0.7-1gral.s... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/ocaml-3.07-2.src.rpm http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/pam_mount-0.9.16-1gra... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/pam_mysql-0.7RC1-1gra... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/pcre-4.5-3.2.RHEL4.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/perl-5.8.5-36.RHEL4.s... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/php-5.1.6-3.16gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/phpmyadmin-2.9.2-2gra... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/postfix-2.2.10-3gral.... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/proftpd-1.3.0a-2gral.... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/pwgen-2.05-17gral.src... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/python24-2.4.3-2gral.... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/reiserfs-utils-3.6.18... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/rpmlint-0.61-1gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/sarg-2.2.2-1gral.src.... (some people hate my for this) http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/synaptic-0.55.1-2gral... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/tripwire-2.3.1.2-7.1.... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/usermin-1.220-1gral.s... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/webmin-1.300-1gral.sr... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/wol-0.7.1-1gral.src.r... http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/xmms-1.2.7-1gral.src.... (support for mp3, no stupid software patents in UE) http://www.gralinux.org/gralinux/AS3/i686/SRPMS.source/zabbix-1.1.4-1gral.sr...
small .. very small??
yes indeed, wont make 2 digits in percentage points
I need to maintain gralinux AS 3 for 2 years, so i will backport stuff from RHAS3 / 5 on it.
CentOS-3 is going to be here for longer than 2 years from now ...
- KB
Regards
js.
On Sat, 2007-04-28 at 18:11 +0200, Dag Wieers wrote:
On Sat, 28 Apr 2007, Johnny Hughes wrote:
We had a need for this app on CentOS-4 ... we want it to do what it already does in the newer versions. I would have thought that the guys who wrote it would have already done it for the CentOS-4 version of python if they were interested in providing it there too :D
Are you interested in backport type things like this to yum-utils and other aps (for older versions)?
If yes, we are certainly glad to provide that info.
Johnny, why not include CentOS 3 as well ?
python 1.5 is definitely too old, but python 2.2 must be within reach.
WRT to our current need, the person who is going to maintain cobbler for CentOS-4 and CentOS-5 asked for this utility (reposync) in yum-utils for CentOS-4 so that the app can work the same in both versions.
I don't think we are going to provide cobbler for CentOS-3 ... though we are working on a yum-2.4.x for the CentOS-3 centosplus repo.
We are working out the last remaining technical issue with yum-2.4 on CentOS-3 (that we have found thus far), which is that yum-2.0 (and up2date in C3) sets newly installed kernels to be the default. In EL4, that is handled by the OS script "/sbin/new-kernel-pkg" (provided by mkinitrd), however in EL3 that functionality was done instead by up2date / yum. We won't modify how mkinitrd works on CentOS-3 (that is a very important core package and we don't change that kind of functionality from upstream), thus the only ohter option is to modify yum to do it.
For anyone concerned about upgrading their yum in CentOS-3 ... this will be a CentOSPlus only, and thus totally optional, update. You will have to purposely enable the CentOSPlus repo and upgrade to get it (once we get it completed).
yum-2.4 will offer significant benefits to CentOS-3 over the current yum-2.0 solution (fastestmirror / priorities / protectbase plugins, working mirrorlists, repomd support, etc.). It will require that the repos in question do generate the newer repomd repodata files for their EL3 repositories (CentOS and RPMForge already do).
Thanks, Johnny Hughes
On Sun, 29 Apr 2007, Johnny Hughes wrote:
On Sat, 2007-04-28 at 18:11 +0200, Dag Wieers wrote:
On Sat, 28 Apr 2007, Johnny Hughes wrote:
We had a need for this app on CentOS-4 ... we want it to do what it already does in the newer versions. I would have thought that the guys who wrote it would have already done it for the CentOS-4 version of python if they were interested in providing it there too :D
Are you interested in backport type things like this to yum-utils and other aps (for older versions)?
If yes, we are certainly glad to provide that info.
Johnny, why not include CentOS 3 as well ?
python 1.5 is definitely too old, but python 2.2 must be within reach.
WRT to our current need, the person who is going to maintain cobbler for CentOS-4 and CentOS-5 asked for this utility (reposync) in yum-utils for CentOS-4 so that the app can work the same in both versions.
I don't think we are going to provide cobbler for CentOS-3 ... though we are working on a yum-2.4.x for the CentOS-3 centosplus repo.
We are working out the last remaining technical issue with yum-2.4 on CentOS-3 (that we have found thus far), which is that yum-2.0 (and up2date in C3) sets newly installed kernels to be the default. In EL4, that is handled by the OS script "/sbin/new-kernel-pkg" (provided by mkinitrd), however in EL3 that functionality was done instead by up2date / yum. We won't modify how mkinitrd works on CentOS-3 (that is a very important core package and we don't change that kind of functionality from upstream), thus the only ohter option is to modify yum to do it.
That should be doable from a plugin, without touching yum itself.
- Panu -
On Fri, 2007-05-04 at 22:52 +0300, Panu Matilainen wrote:
On Sun, 29 Apr 2007, Johnny Hughes wrote:
We are working out the last remaining technical issue with yum-2.4 on CentOS-3 (that we have found thus far), which is that yum-2.0 (and up2date in C3) sets newly installed kernels to be the default. In EL4, that is handled by the OS script "/sbin/new-kernel-pkg" (provided by mkinitrd), however in EL3 that functionality was done instead by up2date / yum. We won't modify how mkinitrd works on CentOS-3 (that is a very important core package and we don't change that kind of functionality from upstream), thus the only ohter option is to modify yum to do it.
That should be doable from a plugin, without touching yum itself.
This was initially implemented as a plugin. But we decided to integrate this into yum, following the principle of least surprise. E.g. on machines with a modified yum configuration (where plugins are not enabled), a plugin would modify behavior from what it was previously.
-- Daniel
On Fri, 2007-05-04 at 22:02 +0200, Daniel de Kok wrote:
On Fri, 2007-05-04 at 22:52 +0300, Panu Matilainen wrote:
On Sun, 29 Apr 2007, Johnny Hughes wrote:
We are working out the last remaining technical issue with yum-2.4 on CentOS-3 (that we have found thus far), which is that yum-2.0 (and up2date in C3) sets newly installed kernels to be the default. In EL4, that is handled by the OS script "/sbin/new-kernel-pkg" (provided by mkinitrd), however in EL3 that functionality was done instead by up2date / yum. We won't modify how mkinitrd works on CentOS-3 (that is a very important core package and we don't change that kind of functionality from upstream), thus the only ohter option is to modify yum to do it.
That should be doable from a plugin, without touching yum itself.
This was initially implemented as a plugin. But we decided to integrate this into yum, following the principle of least surprise. E.g. on machines with a modified yum configuration (where plugins are not enabled), a plugin would modify behavior from what it was previously.
Right ... doing it as a plugin is a great idea, and if we were adding it as optional functionality where it did not exist already that would be the method we chose.
But in this case, it is already built into the version 2.0.8 yum that this will replace in CentOS-3. So this is providing functionality that already exists in the current yum to the newer yum. I don't think I want to roll in the "requirement" to also enable and properly configure "plugins" to get normal out of the box behavior of the older version in the newer one.
The new patch is only applied into yum-2.4.x IF it is compiled on a system with python-2.2 (el3) ... if compiled on python >= 2.3 (el4) then it is not applied.
The process will be to upgrade/install the new yum (plus requirements) as a separate install out of CentOSPlus for C3 ... then adjust your yum.conf to use /etc/yum.repo.d/, then use the new yum.
Thanks, Johnny Hughes
-
Akemi Yagi -
Dag Wieers -
Daniel de Kok -
jean-seb -
Johnny Hughes -
Johnny Hughes -
Karanbir Singh -
Panu Matilainen -
seth vidal