[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#924712: marked as done (crypt() not available _XOPEN_SOURCE is defined)

Your message dated Sat, 31 Aug 2019 15:04:06 +0200
with message-id <20190831130406.GA31416@aurel32.net>
and subject line Re: Bug#924712: crypt() not available _XOPEN_SOURCE is defined
has caused the Debian Bug report #924712,
regarding crypt() not available _XOPEN_SOURCE is defined
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
924712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924712
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6-dev
Version: 2.28-8
Severity: serious

Hi,

The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
crypt() to be available.

But it looks that it's currently the opposite, if _XOPEN_SOURCE is
defined, the function cannot be found.

This actually looks like a regression compared to stretch.

Regards,
Laurent Bigonville

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages manpages-dev depends on:
ii  manpages  4.16-1

manpages-dev recommends no packages.

Versions of packages manpages-dev suggests:
ii  man-db [man-browser]  2.8.5-2

-- no debconf information

--- End Message ---
--- Begin Message --- 
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. 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.

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

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: