On Sat, 1 Jan 2000, David Walluck wrote:
> Oops.. this went to the wrong place...
>
> -------- Original Message --------
> Subject: Re: [Cooker] Oxygen upgrade difficulties
> Date: Fri, 31 Dec 1999 17:13:32 -0500
> From: David Walluck <[EMAIL PROTECTED]>
> To: Jacques Le Marois <[EMAIL PROTECTED]>
> References: <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
>
> Jacques Le Marois wrote:
> > David,
> >
> > Just curious - how do you upgrade daily ? This could be useful for
> > others users...
> >
> > Jacques
>
> Let me clarify what I meant by `upgrade daily'. I meant that each day I
> go online and get the Cooker updates for that day. I do this as a cron
> job. I can't use rsync because I only have about 100M free, so there is
> not enough room to mirror the entire distribution. I use a perl script I
> found called rhupd, which unfortunately doesn't seem to be being
> maintained. I'll attach it here because it is only 12K.
>
> In your cron you might want to do something like this:
>
> cd /home/cooker
> rhupd -a > cooker-updates-`date +%Y%m%d`.log 2>&1
> rpm -Uvh --nodeps --force *.rpm > cooker-install-`date +%Y%m%d`.log 2>&1
> rm -rf *.rpm
>
> Unfortunately, there's still many conflicts between packages which
> requires a --force. The --nodeps is needed because a required update
> might not be mirrored yet. I've never had anything break because of
> this, though. Also, sometimes the updates aren't recognized. For
> example, Mesa-3.1 is newer than Mesa-3.1cvs, but numerically it's
> not, so you'd have to realize this and grab the update yourself. This
> has worked well for me so far, and hopefully it will be useful for
> others as well.
>
> I suggested that MandakeUpdate use the Cooker mirrors while in Cooker,
> and then switch to Oxygen mirror for the release RPM. This would let us
> upgrade daily using MandrakeUpdate. Unfortunately, this is a graphical
> program and can't easily be automated. What I'd really like to see is
> someone from Mandrake pickup this rhupd script and maybe do something
> like this in the Mandrake release. There is also a program called
> autorpm, but I found this to be too cumbersome.
>
> One other thing I'd like to mention is the rpmverify script that can be
> found in Mandrake Contrib. This is very useful for finding failed
> dependencies or missing files in packages. For example, the script
> exposed problems with the ncurses, acroread, and initscripts RPMS, among
> others. Some of these, like the ncurses symlinks bug, have been in the
> bug database for a long time and never been fixed.
>
See the archives about ncurses i refuse to fix it again if it's just going
to get lost ;)
You stated the Mesa versions backwards but we get the idea, we'll be
makeing minor changes to the release numbering scheme after 7.0 to cooker
packages, so in theory you'll be able todo actual upgrades from
cooker -> cooker
cooker -> beta
stable -> cooker
cooker -> stable
And all the combo's of the above, should be fully functional after the
next stable release.
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
