I just completed my first 5.2 install. For 'completeness' I 'tested out' yum update. Guess what? For this minimum install, there were 43Mb of updates to download. So I went over to my local repo server and setup a /centos/5.2/updates directory and started the rsync to get all the updates: 155 files taking up 943Mb. Already. Wow! Perhaps something to do with the initial build problem? But anyone that does an install from the CDs/DVD and includes OpenOffice, then turns around and updates, is in for a scary supprise. Yet another reason for the local repos....
Robert Moskowitz wrote:> I just completed my first 5.2 install. For 'completeness' I 'tested > out' yum update. > > Guess what? For this minimum install, there were 43Mb of updates to > download. > > So I went over to my local repo server and setup a /centos/5.2/updates > directory and started the rsync to get all the updates: > > 155 files taking up 943Mb. Already. Wow! Perhaps something to do > with the initial build problem? But anyone that does an install from > the CDs/DVD and includes OpenOffice, then turns around and updates, is > in for a scary supprise. Yet another reason for the local repos....I thought the 'updates' directory contained updates for everything from 5.0 forward ?
On Wed, Jun 25, 2008 at 10:38 PM, Robert Moskowitz <rgm at htt-consult.com> wrote:> I just completed my first 5.2 install. For 'completeness' I 'tested out' > yum update. > > Guess what? For this minimum install, there were 43Mb of updates to > download. > > So I went over to my local repo server and setup a /centos/5.2/updates > directory and started the rsync to get all the updates: > > 155 files taking up 943Mb. Already. Wow! Perhaps something to do with the > initial build problem? But anyone that does an install from the CDs/DVD and > includes OpenOffice, then turns around and updates, is in for a scary > supprise. Yet another reason for the local repos....This is actually perfectly normal. If you install C5.2 from the install media you will get what upstream released a month ago. Between then and now they released different updates. These are not but on the install media but end up in the updates repository to make sure the our and upstreams install media are as identical as possible. And no, the updates repo only contains updates for the running minor release. So currently it contains updates for 5.2. Regards, Tim -- Tim Verhoeven - tim.verhoeven.be at gmail.com - 0479 / 88 11 83 Hoping the problem magically goes away by ignoring it is the "microsoft approach to programming" and should never be allowed. (Linus Torvalds)
John R Pierce wrote:> Robert Moskowitz wrote: >> I just completed my first 5.2 install. For 'completeness' I 'tested >> out' yum update. >> >> Guess what? For this minimum install, there were 43Mb of updates to >> download. >> >> So I went over to my local repo server and setup a >> /centos/5.2/updates directory and started the rsync to get all the >> updates: >> >> 155 files taking up 943Mb. Already. Wow! Perhaps something to do with >> the initial build problem? But anyone that does an install from the >> CDs/DVD and includes OpenOffice, then turns around and updates, is in >> for a scary supprise. Yet another reason for the local repos.... > > I thought the 'updates' directory contained updates for everything > from 5.0 forward ?There are only 2 rpms dated Jun 18, all the rest are more recent So I would say they are all updates to 5.2. Plus the way that Johnny maintains the symlink, he would change over the the 5.2 updates the same time he changes over to the 5.2 base.
Tim Verhoeven wrote:> On Wed, Jun 25, 2008 at 10:38 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: > >> I just completed my first 5.2 install. For 'completeness' I 'tested out' >> yum update. >> >> Guess what? For this minimum install, there were 43Mb of updates to >> download. >> >> So I went over to my local repo server and setup a /centos/5.2/updates >> directory and started the rsync to get all the updates: >> >> 155 files taking up 943Mb. Already. Wow! Perhaps something to do with the >> initial build problem? But anyone that does an install from the CDs/DVD and >> includes OpenOffice, then turns around and updates, is in for a scary >> supprise. Yet another reason for the local repos.... >> > > This is actually perfectly normal. If you install C5.2 from the > install media you will get what upstream released a month ago.Is there some other way to do an install? I build my local repo from the install media as I learned from the wiki.> Between > then and now they released different updates. These are not but on the > install media but end up in the updates repository to make sure the > our and upstreams install media are as identical as possible. > > And no, the updates repo only contains updates for the running minor > release. So currently it contains updates for 5.2. > > Regards, > Tim > >
Johnny Hughes wrote:> Ralph Angenendt wrote: >> John R Pierce wrote: >>> I thought the 'updates' directory contained updates for everything >>> from 5.0 forward ? >> >> No. >> >> updates/ gets emptied out on a new point release and then is rebased on >> the os/ tree for the new release. >> > > Right ... BUT, base + updates are all the latest RPMS in the release, > so no one should think that is a problem.So how can you do an install based on all the latest? Can I create a /centos/install/i386 directory structure where I first rsync over the /centos/os/i386, then the /centos/update/i386, and then keep it current from both from the Centos mirrors? I would guess I would have to run createrepo myself as neither the base nor the update repodata would be right for the combined directory. I have quite a few installs to do still this week. I had been holding off on some builds, waiting for 5.2 to do them 'clean'.