[qmailtoaster] Heads up Centos 5 toasters

2009-03-31 Thread DG
C 5.3 will hit the streets today sometime. the torrents are already up and seeded waiting for the official announcement (i've got mine already). the torrent is available from one of the developers site. (got the link from twitter.com/centos) watch toaster performance if you have a cron'ed

Re: [qmailtoaster] Heads up Centos 5 toasters

2009-03-31 Thread Phil Leinhauser
Thanks for the heads up Fuzzy. You're right, it's not a good idea to be in a hurry to grab the latest and greatest especially in a production environment. C 5.3 will hit the streets today sometime. the torrents are already up and seeded waiting for the official announcement (i've got mine

Re: [qmailtoaster] Heads up Centos 5 toasters

2009-03-31 Thread Jake Vickers
Phil Leinhauser wrote: Thanks for the heads up Fuzzy. You're right, it's not a good idea to be in a hurry to grab the latest and greatest especially in a production environment. C 5.3 will hit the streets today sometime. the torrents are already up and seeded waiting for the official

Re: [qmailtoaster] Heads up Centos 5 toasters

2009-03-31 Thread Lucian Cristian
quote The update should be: yum update glibc yum update IIRC, it's because of some bug in upstream. However using this method should work fine. end quote regards Lucian On 31.03.2009 19:32, Jake Vickers wrote: Phil Leinhauser wrote: Thanks for the heads up Fuzzy. You're right, it's

Re: [qmailtoaster] Heads up Centos 5 toasters

2009-03-31 Thread DG
Lucian Cristian wrote: The update should be: yum update glibc yum update IIRC, it's because of some bug in upstream. However using this method should work fine. indeed, that is the number 1 item from the release notes. 4. Known Issues When updating from 5.2 to 5.3 you can run into a

Re: [qmailtoaster] Heads up Centos 5 toasters

2009-03-31 Thread Phil Leinhauser
Oh joy... I can only imagine the traffic this will generate here on the list when people start upgrading tomorrow. Lucian Cristian wrote: The update should be: yum update glibc yum update IIRC, it's because of some bug in upstream. However using this method should work fine. indeed,