The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Looking for a reason to not orphan my howto

On Mon, 29 Dec 1997, Scott Ellis wrote:

> Well, it's finally been done.  With the 2.06 version of libc6, it is
> completely impossible to have both libc5-dev and libc6 coexist on the
> same system without forcing the dependancys and fighting with dselect
> over it.
>
> I'm looking for someone (like the libc6 or libc5 maintainers) to
> provide me with a good reason why I shouldn't abandon my upgrade
> howto.  My intention in writing it was to provide people running bo
> a "least upgrade" method of installing libc6 packages without having
> to break their current development environment.  This is no longer
> possible without telling people to force libc6 to install, an option
> I consider unacceptable.  Debian USED to be good at minimal package
> upgrades, but this doesn't seem to be the case anymore.  I guess we're
> going down the RedHat path of "upgrade everything, we don't care about
> making it work otherwise."

i think that most of us just accept that there are some fundamental
incompatibilities between libc5 development and libc6 and just want to
get the transition to libc6 out of the way as quickly (and buglessly) as
possible so that debian can get back to being a "live" (i.e. upgrade as
much or as little as you want whenever you want) distribution.

It may be *possible* to hack libc5 and libc6 (and the relevant -dev
packages) so that they can work together.  However it probably isn't
worth the effort of spending so much energy on something which will have
a useful lifespan of maybe 3 or 4 months at most, especially when you
consider that we are already behind schedule (as usual :-) for our release
of hamm/2.0

for the handful of people who won't want to upgrade to hamm/libc6
when it's released but still want newer versions of various packages,
they will be able to download the debianised source and build a libc5
version.

this is not perfect and it will cause problems for some people but
switching to libc6 is a big change - bigger even than the a.out to ELF
transition we went through some time ago.


Your HOWTO is extremely useful as a guide for people wanting to safely
upgrade from bo (or earlier) to hamm.  It works.  My guess is that most of
the people who use your howto don't give a damn about libc5-dev, they just
want to upgrade to hamm without destroying their system in the process.  i
think that that's an excellent reason to not abandon your work.

 
craig


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .