[cooker-amd64] Re: Segmentation fault, coreutils-5.0-7.1.92mdk I thought this was fixed?

[Duncan]

Steve Hollingsworth posted <401186BC.4000502@trecorde.net>, excerpted
below,  on Fri, 23 Jan 2004 15:40:28 -0500:

> I'm running the version
> coreutils-5.0-7.1.92mdk (>coreutils-5.0.91-7mdk, yes?)

No.  The dash between the numbers is the version/release separator.  Thus,
you are now running coreutils version 5.0, release 7.1.92 mandrake, while
the one you are comparing to is coreutils version 5.0.91, release 7
mandrake.  Version 5.0 is less than version 5.0.91, so release numbers
don't need to be compared.

Occasionally, urpmi gets confused too, and will attempt to install an
older version over a newer version.  When this happens, it should be
reported as a bug, so it can be fixed.  Whether that's what happened in
your case I'm not sure, but I am sure 5.0 is less than 5.0.91, not
greater, so however it happened, you have an old version now.

If urpmi is confused, you may need to do a manual update, possibly forcing
it to do what it thinks is a downgrade.  Or, you can report the bug, and
wait until it is properly fixed and the fix available on your mirror, if
you prefer.

Once you get a newer version, if it's still attempting to install the
older version over the new one, you may need to add the old one to your
urpmi skip-list (/etc/urpmi/skip.list), until the older version works its
way out of the system. Note that in ordered to specify the old version,
not just ALL versions of that package, you will need to use a regex match,
thus, /^coreutils-5\.0-7\.1\.92mdk/, as simply putting
coreutils-5.0-7.1.92mdk won't keep it from trying to install, and simply
putting coreutils will cause it to ignore the package altogether, even
when a new version comes out.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin