On 2019-10-07 00:00, Marco d'Itri wrote:
> On Oct 06, Aurelien Jarno <aurel...@aurel32.net> wrote:
> 
> > Ah this doesn't match the version in unstable, it's only in NEW for now.
> > I guess we need to wait for it to get out of there first.
> For reasons which I do not understand, the ftpmasters obliquely let me 
> know that they will not accept libxcrypt from NEW until the libc 
> maintainers will explicitly confirm that we have agreed on a plan to use 
> it. Do you mind confirming this?

AFAIK, the glibc team have never been asked about that.

For the ftpmasters: I confirm we'll replace libcrypt.so.1 from libc6 by
the one from libxcrypt. Therefore please accept the package.

> > > So I think that libc6 should have Depends/Replaces on libcrypt1.
> > Agreed for the Depends. I don't get why it needs a Replaces. On the
> > other hand libcrypt1 needs a Replaces: libc6, libc6.1, libc0.1, libc0.3
> > with the correct version.
> Yes, this is what I meant. So:
> 
> Package: libcrypt1
> Breaks: libc6 (<< 2.29-X)
> Replaces: libc6 (<< 2.29-X)
> 
> Package: libcrypt1-dev
> Breaks: libc6-dev (<< 2.29-X)
> Replaces: libc6-dev (<< 2.29-X)
> 
> Package: libc6
> Depends: libcrypt1
> 
> Package: libc6-dev
> Depends: libcrypt1-dev
> 
> And all the architecture-specific variations which I will figure out.

This is libc0.1, libc0.3, libc6 and libc6.1 for the library package. 
This is libc0.1-dev, libc0.3-dev, libc6-dev and libc6.1-dev for the
library packages.

I guess we should keep building libcrypt1 for the bi/tri-arch packages.

> (Also, do not forget about the man pages in the -dev packages.)

The man page was not provided by the -dev package but by manpages-dev.

> There is also a libcrypt1 udeb: do you prefer to start building it now 
> or deal with it later?

We must build the libcrypt1 udeb, and add a depends from libc6-deb to
libcrypt1-udeb, otherwise we might break d-i. At some point we might
want to rebuild all udebs (at least by hand to detect the affected
udebs) and drop that dependency.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature

Reply via email to