Bug#924712: crypt() not available _XOPEN_SOURCE is defined
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 pgpJJ4HF3VsfR.pgp Description: PGP signature
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
On Sun, 25 Aug 2019 15:51:21 +0200 Francesco Poli wrote: > On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote: [...] > > 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? If you do not object (by the end of August), I can reassign the bug report to package manpages-dev. -- 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 pgpx9QUCGCKSs.pgp Description: PGP signature
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
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? -- 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 pgpy9wsedCAEs.pgp Description: PGP signature
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
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. I probably do not fully understand the issue: there seems to be a transition going on, from some deprecated crypt() implementation to libxcrypt. And this transition requires some small changes (basically different #include and #define directives) in C code using crypt(), if this code has to be recompiled on buster or later. But these different requirements are not yet documented in the appropriate [man page]. [man page]: <https://manpages.debian.org/buster/manpages-dev/crypt.3.en.html> Is this a decent summary of the situation? If this is the case, should this bug report be reassigned to package manpages-dev and fixed there? Please clarify, thanks for your time and patience! :-) -- 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 pgp5MDikA5Vhd.pgp Description: PGP signature
Bug#808181: libc6: Upgrade can make the linker unusable
On Fri, 18 Dec 2015 14:46:18 +0100 Aurelien Jarno wrote: [...] > binutils version 2.25.90.20151209-1 is now in testing, I am therefore > closing the bug. Thanks! I am another user who was bitten by this bug: I worked around it by installing binutils from unstable. In the meanwhile this bug report was being filed. I wonder: is there anything that can be done in order to ensure that glibc and binutils will always migrate in lockstep in the future? -- 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 pgpSMZ1k7GoFu.pgp Description: PGP signature
