On Sat, 31 Aug 2019 15:04:06 +0200 Aurelien Jarno wrote: > On 2019-08-25 15:51, Francesco Poli wrote: > > On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote: > > > > > * Francesco Poli: > > > > > > > Hello everyone, > > > > I am sorry to ask, but... I cannot understand what's the status of > > > > [this bug report]. > > > > > > > > [this bug report]: <https://bugs.debian.org/924712> > > > > > > > > A serious bug for libc6-dev without any apparent activity since last > > > > March? Sure there must have been some hidden progress that I cannot > > > > see. > > > > > > We provided a solution acceptable to the reporter. I do not think > > > further action is needed on the glibc side. The manual page needs to > > > be updated to reflect the change, but that's not part of glibc. > > > > OK, good. > > Thanks for your prompt reply! > > > > Why is the bug report being kept open, though? > > Should it be reassigned to package manpages-dev and fixed there? > > manpages-dev doesn't provide the manpage for crypt(3) anymore. Oops, I hadn't noticed that. Thanks a lot for clarifying! > It is now > provided by libcrypt2-dev. The crypt functions are getting removed from > the glibc and will be provided by this external library. I guess we'll > do the transition after getting glibc 2.29 into unstable. > > As the version provided by libcrypt2-dev doesn't have the reported > issue, I am closing the bug. Good, thanks for stepping in! Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
Attachment:
pgpbZ8eZq8ajr.pgp
Description: PGP signature