On one mirror that I tried, at least. So, is it live yet? :-) -- Florin Andrei florin.myip.org
On Tue, 31 Mar 2009, Florin Andrei wrote:> On one mirror that I tried, at least. > > So, is it live yet? :-)Almost. Another several more hours before they all sync, and then we're good to go. BTW, how does this work? If I want to go from 5.2 to 5.3, can I just type "yum upgrade"? If so, what /etc/yum.repos.d entry has to be active for that? ******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
on 3-31-2009 10:41 AM Florin Andrei spake the following:> On one mirror that I tried, at least. > > So, is it live yet? :-) >The announcement will tell you if it is live. Prior updates seem to have been done like this; Packages and ISO's are synced to mirrors. Maybe packages first, then ISO's. When a sufficient set of mirrors are synced (a large percentage), the yum metadata is synced. I think there are methods in place to check if a mirror is fully up. When this is done, then the release announcement is done. The mirror servers do their thing and assign fully updated mirrors out to the public. That way the faster mirrors aren't overwhelmed with downloads as the slower mirrors are still catching up, and systems don't try to yum update on an incomplete mirror and break. Do everyone a favor and wait another day or so. If you saw ISO's they may not be complete yet, and you will add bandwidth load for nothing. When you see a release announcement, then all bets are off, and everyone will be pounding the mirrors anyway. Happy CentOS'ing! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature URL: <lists.centos.org/pipermail/centos/attachments/20090331/a988dc1a/attachment-0003.sig>
On Tuesday 31 March 2009 18:41:48 Florin Andrei wrote:> On one mirror that I tried, at least. > > So, is it live yet? :-)Well It's live on my local mirror. I've just done a yum update on a test server and everything seems OK. So it looks like the wait was worth it. Good job to all those CentOS developers. regards, Tony -- Dept. of Comp. Sci. University of Limerick.
Sorin Srbu wrote:>> -----Original Message----- >> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf >> Of Gilbert Sebenste >> Sent: Tuesday, March 31, 2009 7:44 PM >> To: CentOS mailing list >> Subject: Re: [CentOS] I see 5.3 ISO images on the mirrors >> >> On Tue, 31 Mar 2009, Florin Andrei wrote: >> >>> On one mirror that I tried, at least. >>> >>> So, is it live yet? :-) >> Almost. Another several more hours before they all sync, and then we're >> good to go. > > Really?? Excellent, you rock guys! > > >> BTW, how does this work? If I want to go from 5.2 to 5.3, can I just >> type "yum upgrade"? If so, what /etc/yum.repos.d entry has to be active >> for that? > > Minor version upgrades (eg 5.2 > 5.3): yum updateNot sure it matters but I usually do yum update yum rpm yum clean all yum update I heard elsewhere that there can be problems if you do not update glibc before updating the rest of the OS. I heard that after two of my boxes were already updated the above way and they didn't experience any issues, so maybe it was bogus, but it certainly can't hurt to do yum update glibc first. remote server, be sure to do it inside of screen.
Sorin Srbu wrote:> "Yum upgrade" or "yum update"? What's the take on that one here on the list?Oh God, Not Again! upgrade and update do exactly the same, except if *YOU* yourself turned off "obsoletes=1" in /etc/yum.conf. There is *NO* difference. Ralph -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <lists.centos.org/pipermail/centos/attachments/20090401/7fbd94e5/attachment-0003.sig>
2009/4/1 Sorin Srbu <sorin.srbu at orgfarm.uu.se>:> I've now updated a machine with CentOS v5.3 x86_64. On this first test, the > glibc didn't update at all and threw up an dependency error. Running yum > update; no yum clean all run first, upgraded everything with no errors. Go > figure.I had the same problem with dependencies. I had to do # yum update glibc glibc-devel But when I looked in the Release Notes for CentOS-5.3, it doesn't mention "yum update glibc" at all, so maybe that upstream bug has been solved for CentOS-5.3?