Le Mar 11 Avril 2006 15:08, Goswin von Brederlow a écrit :
> > right, but that makes a nasty circular dependency I thought we
> > should avoid at any rate ? Shouldn't libc-bin rather conflicts with
> > bad version of the libc ?
> I think that circle is unavoidable.
right, I forgot about the
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> Le Mar 11 Avril 2006 11:05, Goswin von Brederlow a écrit :
>> I'm assuming libc6 depends on libc-bin and libc-bin depends on libc6
>> here. The former is needed to always pull in libc-bin on upgrades and
>> the later is needed to ensure the minimum ve
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Tue, Apr 11, 2006 at 11:51:26AM +0200, Pierre Habouzit wrote:
>> Le Mar 11 Avril 2006 11:05, Goswin von Brederlow a écrit :
>
>> > I'm assuming libc6 depends on libc-bin and libc-bin depends on libc6
>> > here. The former is needed to always pull in
Le Mar 11 Avril 2006 12:09, Steve Langasek a écrit :
> On Tue, Apr 11, 2006 at 11:51:26AM +0200, Pierre Habouzit wrote:
> > Le Mar 11 Avril 2006 11:05, Goswin von Brederlow a écrit :
> > > I'm assuming libc6 depends on libc-bin and libc-bin depends on
> > > libc6 here. The former is needed to alway
On Tue, Apr 11, 2006 at 11:51:26AM +0200, Pierre Habouzit wrote:
> Le Mar 11 Avril 2006 11:05, Goswin von Brederlow a écrit :
> > I'm assuming libc6 depends on libc-bin and libc-bin depends on libc6
> > here. The former is needed to always pull in libc-bin on upgrades and
> > the later is needed t
Le Mar 11 Avril 2006 11:05, Goswin von Brederlow a écrit :
> Pierre Habouzit <[EMAIL PROTECTED]> writes:
> > Le Lun 10 Avril 2006 19:41, Aurelien Jarno a écrit :
> >> Anthony Towns a écrit :
> >> > Hi,
> >> >
> >> > This is a reject of the new -bin packages (both of them).
> >> >
> >> > The issues
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> Le Lun 10 Avril 2006 19:41, Aurelien Jarno a écrit :
>> Anthony Towns a écrit :
>> > Hi,
>> >
>> > This is a reject of the new -bin packages (both of them).
>> >
>> > The issues with the -bin package are that it may cause upgrade
>> > problems, both in
Aurelien, with the feedback provided by aj and your own. After the
small changes, i think you should upload it for experimental and ask
for tests. If you think it's ok for tests "as is", just drop the
package in experimental soon and let us see.
I think the experimental upload (or just a people.d.
Le Lun 10 Avril 2006 19:41, Aurelien Jarno a écrit :
> Anthony Towns a écrit :
> > Hi,
> >
> > This is a reject of the new -bin packages (both of them).
> >
> > The issues with the -bin package are that it may cause upgrade
> > problems, both in that upgrading from existing libc's may result in
> >
Hi all,
Today I have uploaded a new glibc which, among other changes, splits
libc6 into libc6 + libc-bin and libc6-dev into libc6-dev + libc-dev-bin.
Those changes are required to be able to implement multiarch, because
the files should not overlap. If we have for example an amd64 libc and
a
Hi,
This is a reject of the new -bin packages (both of them).
The issues with the -bin package are that it may cause upgrade problems, both
in that upgrading from existing libc's may result in a broken system between
the new libc6 being unpacked and the new libc-bin being installed (ldconfig
not
11 matches
Mail list logo
