Aurelien Jarno (2019-12-06):
> There should be no changes needed on the d-i side. libc6-udeb has a
> new dependency on libcrypt1-udeb. When packages get rebuilt against
> libxcrypt, they'll have a direct dependency on libcrypt1-udeb.
>
> There is a small impact on size (~100kB) as libxcrypt
On 2019-12-06 22:46, Cyril Brulebois wrote:
> Hi,
>
> Marco d'Itri (2019-10-07):
> > Dear debian-boot: for the benefit of the ftpmasters, please confirm that
> > you have no objections to src:libxcrypt generating a libcrypt1-udeb
> > package (initially in experimental) which will provide
Hi,
Marco d'Itri (2019-10-07):
> Dear debian-boot: for the benefit of the ftpmasters, please confirm that
> you have no objections to src:libxcrypt generating a libcrypt1-udeb
> package (initially in experimental) which will provide crypt(3)
> currently in the libc udeb.
>
> > I guess we
On Nov 05, Aurelien Jarno wrote:
> We have done a new upload of glibc into sid. I have just merged the
> changes to the libxcrypt branch. You might want to update your branch by
> adding 1 to the debian revision for the breaks/conflicts.
I have uploaded 4.4.10-2 targeted to experimental with
On 2019-10-20 19:19, Aurelien Jarno wrote:
> On 2019-10-10 01:30, Marco d'Itri wrote:
> > On Oct 09, Aurelien Jarno wrote:
> >
> > > I have implemented the first option in the libxcrypt branch:
> > >
> > > https://salsa.debian.org/glibc-team/glibc/tree/libxcrypt
> > And here you can see a
On 2019-10-10 01:30, Marco d'Itri wrote:
> On Oct 09, Aurelien Jarno wrote:
>
> > I have implemented the first option in the libxcrypt branch:
> >
> > https://salsa.debian.org/glibc-team/glibc/tree/libxcrypt
> And here you can see a tentative libxcrypt package: does it look right
> to you?
>
On Oct 09, Aurelien Jarno wrote:
> I have implemented the first option in the libxcrypt branch:
>
> https://salsa.debian.org/glibc-team/glibc/tree/libxcrypt
And here you can see a tentative libxcrypt package: does it look right
to you?
On 2019-10-07 14:16, Aurelien Jarno wrote:
> On 2019-10-07 00:31, Marco d'Itri wrote:
> > On Oct 07, Aurelien Jarno wrote:
> >
> > Dear debian-boot: for the benefit of the ftpmasters, please confirm that
> > you have no objections to src:libxcrypt generating a libcrypt1-udeb
> > package
On 2019-10-07 00:31, Marco d'Itri wrote:
> On Oct 07, Aurelien Jarno wrote:
>
> Dear debian-boot: for the benefit of the ftpmasters, please confirm that
> you have no objections to src:libxcrypt generating a libcrypt1-udeb
> package (initially in experimental) which will provide crypt(3)
>
On Oct 07, Aurelien Jarno wrote:
Dear debian-boot: for the benefit of the ftpmasters, please confirm that
you have no objections to src:libxcrypt generating a libcrypt1-udeb
package (initially in experimental) which will provide crypt(3)
currently in the libc udeb.
> I guess we should keep
On 2019-10-07 00:00, Marco d'Itri wrote:
> On Oct 06, Aurelien Jarno 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
>
On Oct 06, Aurelien Jarno 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
On 2019-10-06 22:04, Marco d'Itri wrote:
> On Oct 06, Aurelien Jarno wrote:
>
> > The libxcrypt implementation is indeed source backward compatible,
> > however doesn't seem binary backward compatible. libc6 provides
> > libcrypt.so.1 while libxcrypt provides libcrypt.so.2.
> It provides both,
Hi,
On 2019-10-06 17:55, Marco d'Itri wrote:
> Package: glibc
> Version: 2.29-2
> Severity: normal
>
> The libc implementation of crypt(3) has been deprecated since 2.28.
> libxcrypt is needed to support modern hashing algorithms.
>
> How do you want to coordinate switching to libxcrypt?
>
>
On Oct 06, Aurelien Jarno wrote:
> The libxcrypt implementation is indeed source backward compatible,
> however doesn't seem binary backward compatible. libc6 provides
> libcrypt.so.1 while libxcrypt provides libcrypt.so.2.
It provides both, but currently I am not even building libcrypt.so.2
Package: glibc
Version: 2.29-2
Severity: normal
The libc implementation of crypt(3) has been deprecated since 2.28.
libxcrypt is needed to support modern hashing algorithms.
How do you want to coordinate switching to libxcrypt?
The libxcrypt implementation is source and binary backward
16 matches
Mail list logo
