Re: Q's about upgrading to hamm
So of those not so easily confused as the rest of us may well correct
this. I also have done the force on libc6 but think that it has something
to do with just exactly which 'old' libc5 is on your system. _If_ I
remember correctly, you can not install the libc5 from hamm first because
it _definately_ depends upon libc6.
Maybe some can confirm this, but if you don't upgrade to the latest bo
then there is a chance that you might not have exactly the expected
response when using the libc5->libc6 mini-HOWTO.
For the time (actually times since I had a similar problem with the
hamm/m68k version) that I did force, I followed the HOWTO exactly until
the force and then immediately upgraded each of the conflicting packages
before continuing with the HOWTO and that seemed to work without further
-->Please note email@example.com does not work<--
-->nor does <anyone>@<anyhost>.wconsult.com<--
==>and yes eventually I'll get the mailer figured out<==
from a 1996 Micro$loth ad campaign:
"The less you know about computers the more you want Micro$oft!"
See! They do get some things right!
On Fri, 5 Dec 1997, Scott J. Geertgens wrote:
> On Fri, 5 Dec 1997, Christopher Jason Morrone wrote:
> > Ok, I'd like to upgrade to hamm, because there are some things there that
> > I need. I'm following the libc5 to libc6 howto, but I've got a couple
> > questions/comments.
> > ...
> I recently did this upgrade myself and ran into the same conflict. I
> went ahead and forced it, and there didn't seem to be any adverse effects
> in doing so. I did notice there was a newer version of libc5 in the hamm
> directories, which made some reference of being better behaved in a libc6
> environment so it _may_ be possible to upgrade to that new libc5 package
> first and then put libc6 on. Doing so doesn't seem to be a necessity,
> however, since my machine seemed to do fine just by forcing.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .