Robinson Tiemuqinke wrote: > --- Jancio Wodnik <jancio_wodnik at wp.pl> wrote: > >> Robinson Tiemuqinke pisze: <snip> > I have had my local 5.0 update repository > (.../centos/5.0/updates/{SRPMS,i386,x86_64}/...) setup > and used it for my 900+ boxes's daily upgrade already. > The repository is synchronized with official Internet > mirrors daily to keep it current. > > My major concerns is: After the 5.1 is released, the > update channel/directory > (.../centos/5.1/updates/{SRPMS,i386,x86_64}/...) may > change to contain only updates for 5.1 > snapshot/release, not updates since 5.0. If so, then > all my Centos 5.0 boxes will suffer. > > I have the serious concern because most Centos Mirror > sites on Internet ONLY keep the updates for latest > release/snapshot, not holds updates since the > base(3.0, 4.0, 5.0 etc) release. This seems like a big > problem if we would like to install from base|initial > release (3.0, 4.0, 5.0) continuously and then use a > single up-to-date update/ repository to upgrade > machines to current level. > > For example, at Stanford's Centos 4 mirror site, only > 4.5 is mirrored while all the other > 4.0/4.1/4.2/4.3/4.4 are not. and in the updates/ > directory only updates for 4.5 are kept there. If the > same is true for all other sites honoring 5.0 series, > then I think I will definitely get screwed If I tried > to keep on using base 5.0 and daily synced updates/ > (exactly the same) for upgrade. > > Any mirror sites hold updates since base release? Or I > have to keep on adding more repositories to yum's > configuration? 5.0 distro, 5.0 updates, 5.1 distro, > 5.1 updates, 5.2 distro, 5.2 updates. etc. If so, then > it is too low-performanced and erro-prone. use 5 and make it a symlink to 5.0 ... on your mirror, move the symlink to 5.1 or 5.2 when the time comes ... and use 5 in your yum configs > > Any one have experience on upgrade Centos 4 releases > from 4.0 to 4.5 can shed a light on this? > > Thanks a lot. > > --Robinson Well ... if you look, WE use a 5 and not a 5.0 or a 5.1 in our CentOS-Base.repo 5 initially contains 5.0 ... and will contain 5.1. SO ... if you use the 5 and not 5.0 or 5.1 then you will be set. We do remove 5.0 when we add 5.1 (and 5.0 goes to our vault ... at <http://vault.centos.org/>. So ... if you sync down 5.0 ... I would sync down 5 and 5.0 and 5.1 and use 5 as the update source not 5.0 or 5.1. If you are using $releasever then you are already using 5 and not 5.0. Then when we shift, it will be seemless (as long as you have Base and Updates both turned on). We DO NOT put all updates since the beginning into updates, it is ONLY updates that to the CURRENT branch. However, base+updates of the current branch == all the latest RPMS, so a yum update against 5.1 base+updates from any other 5x will get you totally updated (once it is released and we have set 5.1 to the default). -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20071202/a55055e9/attachment-0004.sig>