On Sun, 21 Jun 1998, Alexander Shumakovitch wrote:
> On Sun, Jun 21, 1998 at 03:35:53PM +0200, Alexander Shumakovitch wrote:
> > Unfortunately, dselect not only doesn't upgrade from 2.0.7pre1-4 to 2.0.7-1,
> > but it wants to upgrade FROM 2.0.7-1 TO 2.0.7.pre1-4 now! And moreover I
> > have
> > broken dependencies now, since apt_0.0.16 depends on libc6 >=2.0.4pre1. It
> ^^^^^^^^^
> > implies that I should either "upgrade" to the previous version, or forget
> > about using apt method in dselect until it's fixed. :-(
> Sorry, should be 2.0.7pre1 there, of course.
>
OK, I knew this was comming, but I really don't have a choice about what I
did. Let me put my point of view clearly on the table.
There are three situations to consider:
1. Upgrading pure bo to hamm (the current situation works fine)
2. Fresh install (no problems here either)
3. Everyone else
In both cases 1 and 3 at least the glibc packages need to be upgraded by
hand.
This should be advertised heavily.
Once the archives are up-to-date there will be no "pre" packages around to
confuse dselect after the "by hand" upgrade
I hope that everyone working on testing and those other folks brave enough
to work with a pre-release version, will be capable of managing this
transition. Cases 1 and 2 will never notice the difference.
Luck,
Dwarf
--
_-_-_-_-_- Author of "The Debian Linux User's Guide" _-_-_-_-_-_-
aka Dale Scheetz Phone: 1 (850) 656-9769
Flexible Software 11000 McCrackin Road
e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308
_-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
