Bug#978833: marked as done (gwyddion: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Thu, 09 Sep 2021 05:18:51 +
with message-id 
and subject line Bug#978833: fixed in gwyddion 2.59-1
has caused the Debian Bug report #978833,
regarding gwyddion: ftbfs with autoconf 2.70
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 ow...@bugs.debian.org
immediately.)


-- 
978833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gwyddion
Version: 2.56-1
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/gwyddion_2.56-1_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
configure.ac:91: You should run autoupdate.
./lib/autoconf/general.m4:2328: AC_DIAGNOSE is expanded from...
m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:91: the top level
configure.ac:92: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:92: You should run autoupdate.
m4/libtool.m4:99: AC_PROG_LIBTOOL is expanded from...
configure.ac:92: the top level
configure.ac:147: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:147: You should run autoupdate.
./lib/autoconf/general.m4:203: AC_HELP_STRING is expanded from...
configure.ac:147: the top level
configure.ac:172: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:172: You should run autoupdate.
./lib/autoconf/general.m4:203: AC_HELP_STRING is expanded from...
configure.ac:172: the top level
configure.ac:244: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:244: You should run autoupdate.
./lib/autoconf/general.m4:203: AC_HELP_STRING is expanded from...
configure.ac:244: the top level
configure.ac:392: warning: The macro `AC_CHECK_LIBM' is obsolete.
configure.ac:392: You should run autoupdate.
m4/libtool.m4:3862: AC_CHECK_LIBM is expanded from...
m4/gwy-math.m4:2: GWY_CHECK_LIBM is expanded from...
configure.ac:392: the top level
configure.ac:659: warning: The macro `AC_HAVE_LIBRARY' is obsolete.
configure.ac:659: You should run autoupdate.
./lib/autoconf/libs.m4:138: AC_HAVE_LIBRARY is expanded from...
m4/gwy-hdf5.m4:61: GWY_LIB_HDF5 is expanded from...
configure.ac:659: the top level
configure.ac:805: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:805: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:673: AS_IF is expanded from...
./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from...
m4/gettext.m4:367: gt_INTL_MACOSX is expanded from...
m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from...
configure.ac:805: the top level
configure.ac:805: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:805: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:673: AS_IF is expanded from...
./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from...
m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from...
configure.ac:805: the top level
configure.ac:805: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:805: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:673: AS_IF is expanded from...
./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from...
m4/iconv.m4:20: AM_ICONV_LINK is expanded from...
m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from...
configure.ac:805: the top level
autoreconf: error: configure.ac: AM_GNU_GETTEXT is used, but not 
AM_GNU_GETTEXT_VERSION
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
Can't exec "gtkdocize": No such file or 

Bug#978890: marked as done (quvi: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Thu, 09 Sep 2021 04:03:50 +
with message-id 
and subject line Bug#978890: fixed in quvi 0.9.4-1.2
has caused the Debian Bug report #978890,
regarding quvi: ftbfs with autoconf 2.70
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 ow...@bugs.debian.org
immediately.)


-- 
978890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:quvi
Version: 0.9.4-1.1
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/quvi_0.9.4-1.1_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
glib_LIBS=''
gobject_CFLAGS=''
gobject_LIBS=''
host='x86_64-pc-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh=''
json_glib_CFLAGS=''
json_glib_LIBS=''
libcurl_CFLAGS=''
libcurl_LIBS=''
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
libquvi_CFLAGS=''
libquvi_LIBS=''
libxml_CFLAGS=''
libxml_LIBS=''
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='${localstatedir}/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target='x86_64-pc-linux-gnu'
target_alias=''
target_cpu='x86_64'
target_os='linux-gnu'
target_vendor='pc'

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "quvi"
#define PACKAGE_TARNAME "quvi"
#define PACKAGE_VERSION "0.9.4"
#define PACKAGE_STRING "quvi 0.9.4"
#define PACKAGE_BUGREPORT "http://quvi.sf.net/bugs/;
#define PACKAGE_URL "http://quvi.sf.net/;
#define BUILD_OPTS "--build=x86_64-linux-gnu
--prefix=/usr
--includedir=${prefix}/include
--mandir=${prefix}/share/man
--infodir=${prefix}/share/info
--sysconfdir=/etc
--localstatedir=/var
--disable-option-checking
--disable-silent-rules
--libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu
--disable-maintainer-mode
--disable-dependency-tracking"

configure: exit 77
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking returned exit code 77
make: *** [debian/rules:4: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: quvi
Source-Version: 0.9.4-1.2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
quvi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated quvi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Sep 2021 23:17:49 -0400
Source: quvi
Architecture: source
Version: 0.9.4-1.2
Distribution: unstable
Urgency: high
Maintainer: Ansgar Burchardt 
Changed-By: Boyuan Yang 
Closes: 978890
Changes:
 quvi (0.9.4-1.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/control: Update Vcs-* fields.
   * debian/patches/0001: Fix FTBFS with autoconf 2.70 (Closes: #978890).
Checksums-Sha1:
 c7341ae07bafe166b32dd43a6c323b315c92 1908 

Bug#952354: marked as done (brebis: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::

[Debian Bug Tracking System]

Your message dated Thu, 09 Sep 2021 01:03:39 +
with message-id 
and subject line Bug#952354: fixed in brebis 0.10-2
has caused the Debian Bug report #952354,
regarding brebis: FTBFS: dh: error: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 
1.
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 ow...@bugs.debian.org
immediately.)


-- 
952354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brebis
Version: 0.10-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3
> dh: error: unable to load addon python3: Can't locate 
> Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
> Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) 
> line 1.
> BEGIN failed--compilation aborted at (eval 10) line 1.
> 
> make: *** [debian/rules:6: clean] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/brebis_0.10-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: brebis
Source-Version: 0.10-2
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
brebis, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated brebis package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Sep 2021 20:42:59 -0400
Source: brebis
Architecture: source
Version: 0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Carl Chenet 
Changed-By: Sandro Tosi 
Closes: 832190 952354
Changes:
 brebis (0.10-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove ancient X-Python3-Version field
   * Use debhelper-compat instead of debian/compat.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Add missing build dependency on dh addon; Closes: #952354
   * Bump debhelper from deprecated 9 to 12.
 .
   [ Sandro Tosi ]
   * Use the new Debian Python Team contact name and address
   * debian/control
 - set Section to admin; Closes: #832190
Checksums-Sha1:
 452ea8991d8c61b5d64305aef7662d6d101a7d51 1925 brebis_0.10-2.dsc
 175375c263f51a4ad4ccb8ae98fd3f846eda5d3b 2308 brebis_0.10-2.debian.tar.xz
 ca7574d00739f0416da155fb411642247f0de317 6376 brebis_0.10-2_source.buildinfo
Checksums-Sha256:
 f8fec19a065ddd27a55db19ac839ffadfbdb92d9c011c510a06c17481620b641 1925 
brebis_0.10-2.dsc
 47cb7cfb4041af4d9c708eca0326d9f85f8fb04d54bfb9c6516386176aef5d0d 2308 
brebis_0.10-2.debian.tar.xz
 0b6161e3703161c46d14b78cd1f292b25d4818f8fc3c97e915f225aa5f6ff453 6376 
brebis_0.10-2_source.buildinfo
Files:
 e1af1af2f363d1fbda76e3f4f2f19c14 1925 admin optional brebis_0.10-2.dsc
 9a384950bdc68dfc68d63c736ceac2b1 2308 admin optional 

Bug#952354: marked as pending in brebis

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #952354 in brebis reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/brebis/-/commit/2828821cafd9ca881bf5332dde5810ad0b5e2d92


Add missing build dependency on dh addon; Closes: #952354


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952354

Processed: Bug#952354 marked as pending in brebis

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952354 [src:brebis] brebis: FTBFS: dh: error: unable to load addon 
python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may 
need to install the Debian::Debhelper::Sequence::python3 module) (@INC 
contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 
/usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 
1.
Added tag(s) pending.

-- 
952354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

[Mike Hommey]

On Thu, Sep 09, 2021 at 12:52:03AM +0200, Aurelien Jarno wrote:
> control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27476
> 
> On 2021-09-09 00:21, Helmut Grohne wrote:
> > Source: nss
> > Version: 2:3.70-1
> > Severity: serious
> > Tags: ftbfs
> > X-Debbugs-Cc: debian-gl...@lists.debian.org
> > 
> > A native build of nss now fails as follows:
> > 
> > | x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC   -pipe 
> > -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
> > -Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE 
> > -D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT 
> > -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
> > -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT 
> > -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
> > -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include 
> > -I/<>/dist/public/coreconf 
> > -I/<>/dist/private/coreconf  nsinstall.c
> > | nsinstall.c: In function ‘main’:
> > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> > argument 2 value is 4096 [-Werror=nonnull]
> > |70 | #define GETCWD getcwd
> > |   |^
> > | nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’
> > |   239 |  cwd = GETCWD(0, PATH_MAX);
> > |   |^~
> > | In file included from nsinstall.c:20:
> > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ 
> > declared with attribute ‘write_only (1, 2)’
> > |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> > |   |  ^~
> > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> > argument 2 value is 4096 [-Werror=nonnull]
> > |70 | #define GETCWD getcwd
> > |   |^
> > | nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’
> > |   246 | todir = GETCWD(0, PATH_MAX);
> > |   | ^~
> > | In file included from nsinstall.c:20:
> > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ 
> > declared with attribute ‘write_only (1, 2)’
> > |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> > |   |  ^~
> > | cc1: all warnings being treated as errors
> > | make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1
> > | make[2]: Leaving directory '/<>/nss/coreconf/nsinstall'
> > | make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2
> > | make[1]: Leaving directory '/<>'
> > | make: *** [debian/rules:195: build] Error 2
> > | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> > status 2
> > 
> > It looks very much like this is due to the glibc 2.32 upload. My reading
> > of man getcwd is that the call of nss is legit (as a glibc extension).
> > Maybe this is a glibc bug?
> 
> This is indeed partially a glibc bug, already reported upstream there:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27476
> 
> Note however that the feature of calling getcwd(NULL, >0) is a GNU
> extension, and that the above code doesn't define _GNU_SOURCE, so this
> is also a bug in the package.

That said, it's also an extension in Solaris.

Mike

Processed: Re: Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 993973 libc6-dev
Bug #993973 [src:nss] nss FTBFS with glibc 2.32: error: argument 1 is null but 
the corresponding size argument 2 value is 4096 [-Werror=nonnull]
Bug reassigned from package 'src:nss' to 'libc6-dev'.
No longer marked as found in versions nss/2:3.70-1.
Ignoring request to alter fixed versions of bug #993973 to the same values 
previously set
> found 993973 2.32-1
Bug #993973 [libc6-dev] nss FTBFS with glibc 2.32: error: argument 1 is null 
but the corresponding size argument 2 value is 4096 [-Werror=nonnull]
Marked as found in versions glibc/2.32-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
993973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

[Mike Hommey]

reassign 993973 libc6-dev
found 993973 2.32-1
thanks

On Thu, Sep 09, 2021 at 12:21:52AM +0200, Helmut Grohne wrote:
> Source: nss
> Version: 2:3.70-1
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: debian-gl...@lists.debian.org
> 
> A native build of nss now fails as follows:
> 
> | x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC   -pipe 
> -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
> -Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE 
> -D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DDEBUG 
> -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
> -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT 
> -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
> -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include 
> -I/<>/dist/public/coreconf 
> -I/<>/dist/private/coreconf  nsinstall.c
> | nsinstall.c: In function ‘main’:
> | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> argument 2 value is 4096 [-Werror=nonnull]
> |70 | #define GETCWD getcwd
> |   |^
> | nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’
> |   239 |  cwd = GETCWD(0, PATH_MAX);
> |   |^~
> | In file included from nsinstall.c:20:
> | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
> with attribute ‘write_only (1, 2)’
> |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> |   |  ^~
> | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> argument 2 value is 4096 [-Werror=nonnull]
> |70 | #define GETCWD getcwd
> |   |^
> | nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’
> |   246 | todir = GETCWD(0, PATH_MAX);
> |   | ^~
> | In file included from nsinstall.c:20:
> | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
> with attribute ‘write_only (1, 2)’
> |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> |   |  ^~
> | cc1: all warnings being treated as errors
> | make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1
> | make[2]: Leaving directory '/<>/nss/coreconf/nsinstall'
> | make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2
> | make[1]: Leaving directory '/<>'
> | make: *** [debian/rules:195: build] Error 2
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
> 
> It looks very much like this is due to the glibc 2.32 upload. My reading
> of man getcwd is that the call of nss is legit (as a glibc extension).
> Maybe this is a glibc bug?

Quoting man getcwd:

  As an extension to the POSIX.1-2001 standard, glibc's getcwd() allocates
  the buffer dynamically using malloc(3) if buf is NULL. In this case, the
  allocated buffer has the length size unless size is zero, when buf is
  allocated as big as necessary

But that's from manpages-dev. The documentation from glibc itself says:

  The GNU C Library version of this function also permits you to specify
  a null pointer for the buffer argument. Then getcwd allocates a buffer
  automatically, as with malloc (see Unconstrained Allocation). If the
  size is greater than zero, then the buffer is that large; otherwise,
  the buffer is as large as necessary to hold the result. 

Which is essentially the same thing. The unistd.h header itself says:

  In GNU, if BUF is NULL, an array is allocated with `malloc'; the array
  is SIZE bytes long, unless SIZE == 0, in which case it is as big as
  necessary.

This doesn't fit with the use of __attribute__((access(write_only(1, 2
IMO.

Mike

Processed: Re: Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27476
Bug #993973 [src:nss] nss FTBFS with glibc 2.32: error: argument 1 is null but 
the corresponding size argument 2 value is 4096 [-Werror=nonnull]
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=27476'.

-- 
993973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

[Aurelien Jarno]

control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27476

On 2021-09-09 00:21, Helmut Grohne wrote:
> Source: nss
> Version: 2:3.70-1
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: debian-gl...@lists.debian.org
> 
> A native build of nss now fails as follows:
> 
> | x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC   -pipe 
> -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
> -Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE 
> -D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DDEBUG 
> -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
> -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT 
> -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
> -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include 
> -I/<>/dist/public/coreconf 
> -I/<>/dist/private/coreconf  nsinstall.c
> | nsinstall.c: In function ‘main’:
> | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> argument 2 value is 4096 [-Werror=nonnull]
> |70 | #define GETCWD getcwd
> |   |^
> | nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’
> |   239 |  cwd = GETCWD(0, PATH_MAX);
> |   |^~
> | In file included from nsinstall.c:20:
> | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
> with attribute ‘write_only (1, 2)’
> |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> |   |  ^~
> | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> argument 2 value is 4096 [-Werror=nonnull]
> |70 | #define GETCWD getcwd
> |   |^
> | nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’
> |   246 | todir = GETCWD(0, PATH_MAX);
> |   | ^~
> | In file included from nsinstall.c:20:
> | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
> with attribute ‘write_only (1, 2)’
> |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> |   |  ^~
> | cc1: all warnings being treated as errors
> | make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1
> | make[2]: Leaving directory '/<>/nss/coreconf/nsinstall'
> | make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2
> | make[1]: Leaving directory '/<>'
> | make: *** [debian/rules:195: build] Error 2
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
> 
> It looks very much like this is due to the glibc 2.32 upload. My reading
> of man getcwd is that the call of nss is legit (as a glibc extension).
> Maybe this is a glibc bug?

This is indeed partially a glibc bug, already reported upstream there:
https://sourceware.org/bugzilla/show_bug.cgi?id=27476

Note however that the feature of calling getcwd(NULL, >0) is a GNU
extension, and that the above code doesn't define _GNU_SOURCE, so this
is also a bug in the package.

Please also note that there are discussion to deprecate the support of
size > 0 when buf is NULL:
https://sourceware.org/bugzilla/show_bug.cgi?id=26545

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

Bug#993974: mpv: Can't play anything anymore

[Nelson A. de Oliveira]

Package: mpv
Version: 0.33.1-1
Severity: grave
Justification: renders package unusable

Hi!

After upgrading mpv from 0.32.0-3 to 0.33.1-1 it seems that I can't play
anything anymore.
(downgrading to 0.32.0-3 I can play videos again)

=
$ mpv palestra.mp4
libavutil: 56.70.100 -> 56.51.100
zsh: abort  mpv palestra.mp4
=

gdb doesn't help, it seems:

=
Program received signal SIGABRT, Aborted.
0x74640e71 in raise () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fffe8f083c0 (LWP 415593) "mpv"):
#0  0x74640e71 in raise () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x7462a536 in abort () at /lib/x86_64-linux-gnu/libc.so.6
#2  0x555ae79d in  ()
#3  0x55627f3d in  ()
#4  0x5562863a in  ()
#5  0x55628aa3 in  ()
#6  0x7462be4a in __libc_start_main () at 
/lib/x86_64-linux-gnu/libc.so.6
#7  0x5559acaa in  ()
=

Full "thread apply all bt full" is attached.

Thank you!

Best regards,
Nelson


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mpv depends on:
ii  libarchive13  3.4.3-2+b1
ii  libasound21.2.5.1-1
ii  libass9   1:0.15.1-2
ii  libavcodec58  7:4.3.2-0+deb11u2
ii  libavdevice58 7:4.3.2-0+deb11u2
ii  libavfilter7  7:4.3.2-0+deb11u2
ii  libavformat58 7:4.3.2-0+deb11u2
ii  libavutil56   7:4.3.2-0+deb11u2
ii  libbluray21:1.3.0-3
ii  libc6 2.32-2
ii  libcaca0  0.99.beta19-2.2
ii  libcdio-cdda2 10.2+2.0.0-1+b2
ii  libcdio-paranoia2 10.2+2.0.0-1+b2
ii  libcdio19 2.1.0-2
ii  libdrm2   2.4.107-2
ii  libdvdnav46.1.1-1
ii  libegl1   1.3.4-1
ii  libgbm1   21.2.1-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.19~dfsg-2
ii  libjpeg62-turbo   1:2.0.6-4
ii  liblcms2-22.12~rc1-2
ii  liblua5.2-0   5.2.4-1.1+b3
ii  libmujs1  1.1.3-2
ii  libplacebo120 3.120.3-2
ii  libpulse0 15.0+dfsg1-2
ii  librubberband21.9.0-1
ii  libsdl2-2.0-0 2.0.16+dfsg1-4
ii  libsixel1 1.8.6-2
ii  libswresample37:4.3.2-0+deb11u2
ii  libswscale5   7:4.3.2-0+deb11u2
ii  libuchardet0  0.0.7-1
ii  libva-drm22.12.0-2
ii  libva-wayland22.12.0-2
ii  libva-x11-2   2.12.0-2
ii  libva22.12.0-2
ii  libvdpau1 1.4-3
ii  libvulkan11.2.189.0-2
ii  libwayland-client01.19.0-2
ii  libwayland-cursor01.19.0-2
ii  libwayland-egl1   1.19.0-2
ii  libx11-6  2:1.7.2-1
ii  libxext6  2:1.3.3-1.1
ii  libxinerama1  2:1.1.4-2
ii  libxkbcommon0 1.3.0-1
ii  libxrandr22:1.5.1-1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1
ii  libzimg2  3.0.2+ds1-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages mpv recommends:
ii  xdg-utils   1.1.3-4.1
ii  youtube-dl  2021.06.06-1

mpv suggests no packages.

-- no debconf information
Starting program: /usr/bin/mpv palestra.mp4
Downloading separate debug info for /mnt/naoliv/system-supplied DSO at 
0x77fd...
Downloading separate debug info for /lib/x86_64-linux-gnu/liblua5.2.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libcaca.so.0...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libcdio_paranoia.so.2...
Downloading separate debug info for /lib/x86_64-linux-gnu/libcdio_cdda.so.2...
Downloading separate debug info for /lib/x86_64-linux-gnu/libcdio.so.19...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Downloading separate debug info for /lib/x86_64-linux-gnu/libavutil.so.56...
Downloading separate debug info for /lib/x86_64-linux-gnu/libavcodec.so.58...
Downloading separate debug info for /lib/x86_64-linux-gnu/libavformat.so.58...
Downloading separate debug info 

Bug#978954: marked as done (pepperflashplugin-nonfree: should not be part of bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 22:37:11 +
with message-id 
and subject line Bug#979047: Removed package(s) from unstable
has caused the Debian Bug report #978954,
regarding pepperflashplugin-nonfree: should not be part of bookworm
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 ow...@bugs.debian.org
immediately.)


-- 
978954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pepperflashplugin-nonfree
Version: 1.8.7
Severity: grave
Justification: renders package unusable

Dear Maintainer,

flash has been EOL today. Browsers are starting to block flash.
I think we should block this package goes into next release?

Yours,
Paul

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_TW:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils 2.35.1-6
ii  ca-certificates  20200601
ii  libgcc-s110.2.1-3
ii  libstdc++6   10.2.1-3
ii  wget 1.20.3-1+b3

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
ii  chromium   83.0.4103.116-3.1+b2
pn  ttf-dejavu 
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.8.8+rm

Dear submitter,

as the package pepperflashplugin-nonfree has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/979047

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#913368: marked as done (tpm2-pk11 (build-)depends on cruft packages.)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 22:36:01 +
with message-id 
and subject line Bug#941951: Removed package(s) from unstable
has caused the Debian Bug report #913368,
regarding tpm2-pk11 (build-)depends on cruft packages.
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 ow...@bugs.debian.org
immediately.)


-- 
913368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: tpm2-pk11
Version: 0~git20180426-1
Severity: serious

tpm2-pk11 build-depends on libsapi-dev and depends on libsapi0, these packages 
are no longer built by source package tpm2-tss. They appear to have been 
replaced by libtss2-dev and libtss2-esys0 .
--- End Message ---
--- Begin Message ---
Version: 0~git20180426-1+rm

Dear submitter,

as the package tpm2-pk11 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/941951

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

[Helmut Grohne]

Source: nss
Version: 2:3.70-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-gl...@lists.debian.org

A native build of nss now fails as follows:

| x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC   -pipe 
-ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
-Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE 
-D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DDEBUG 
-UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
-DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT 
-DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
-DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include 
-I/<>/dist/public/coreconf 
-I/<>/dist/private/coreconf  nsinstall.c
| nsinstall.c: In function ‘main’:
| nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
argument 2 value is 4096 [-Werror=nonnull]
|70 | #define GETCWD getcwd
|   |^
| nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’
|   239 |  cwd = GETCWD(0, PATH_MAX);
|   |^~
| In file included from nsinstall.c:20:
| /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
with attribute ‘write_only (1, 2)’
|   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
|   |  ^~
| nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
argument 2 value is 4096 [-Werror=nonnull]
|70 | #define GETCWD getcwd
|   |^
| nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’
|   246 | todir = GETCWD(0, PATH_MAX);
|   | ^~
| In file included from nsinstall.c:20:
| /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
with attribute ‘write_only (1, 2)’
|   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
|   |  ^~
| cc1: all warnings being treated as errors
| make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1
| make[2]: Leaving directory '/<>/nss/coreconf/nsinstall'
| make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:195: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

It looks very much like this is due to the glibc 2.32 upload. My reading
of man getcwd is that the call of nss is legit (as a glibc extension).
Maybe this is a glibc bug?

Helmut

Bug#750946: marked as done (libhtml-html5-parser-perl: UTF-8 character breaks parse_file)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 22:19:10 +
with message-id 
and subject line Bug#750946: fixed in libhtml-html5-parser-perl 0.992-1
has caused the Debian Bug report #750946,
regarding libhtml-html5-parser-perl: UTF-8 character breaks parse_file
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 ow...@bugs.debian.org
immediately.)


-- 
750946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhtml-html5-parser-perl
Version: 0.301-1
Severity: important

(with possible data loss as a consequence)

Consider the following HTML file:


http://www.w3.org/1999/xhtml;>
  

title
  
  
↓
  


On this file, the following script

#!/usr/bin/env perl

use strict;
use HTML::HTML5::Parser;

use utf8;# for the characters in the script.
use open ':encoding(UTF-8)'; # for the file arguments.
binmode STDIN, ':encoding(UTF-8)';   # for stdin.
binmode STDOUT, ':encoding(UTF-8)';  # for stdout.

@ARGV == 1 or die "Usage: $0 \n";

my $parser = HTML::HTML5::Parser->new;
my $doc = $parser->parse_file($ARGV[0]);
print "Charset: '", $parser->charset($doc), "'\n";
print $doc->toString();

outputs:

Charset: ''

http://www.w3.org/1999/xhtml;>

If I replace the ↓ (U+2193 DOWNWARDS ARROW) by é (U+00E9 LATIN SMALL
LETTER E WITH ACUTE), then I get:

Charset: 'utf-8'


http://www.w3.org/1999/xhtml; 
xmlns="http://www.w3.org/1999/xhtml;>

title
  
  
�
  



which is also incorrect, but at least the charset is correct.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libhtml-html5-parser-perl depends on:
ii  libhtml-html5-entities-perl   0.003-2
ii  libio-html-perl   1.00-1
ii  libtry-tiny-perl  0.22-1
ii  liburi-perl   1.60-1
ii  libxml-libxml-perl2.0116+dfsg-1
ii  perl  5.18.2-4
ii  perl-modules [libhttp-tiny-perl]  5.18.2-4

libhtml-html5-parser-perl recommends no packages.

Versions of packages libhtml-html5-parser-perl suggests:
pn  libxml-libxml-devel-setlinenumber-perl  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libhtml-html5-parser-perl
Source-Version: 0.992-1
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
libhtml-html5-parser-perl, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 750...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libhtml-html5-parser-perl 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Sep 2021 23:44:32 +0200
Source: libhtml-html5-parser-perl
Architecture: source
Version: 0.992-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Closes: 750946
Changes:
 libhtml-html5-parser-perl (0.992-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release(s)
 + fix encoding issues;
   closes: bug#750946
 .
   [ Salvatore Bonaccorso ]
   * update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * use MetaCPAN URIs (not search.cpan.org or www.cpan.org)
   * use secure GitHub URIs
 .
   [ Debian Janitor ]
   * set upstream metadata fields:
 Bug-Database Repository
 .
   [ Jonas Smedegaard ]
   * simplify rules;
 stop build-depend on dh-buildinfo cdbs
   * annotate test-only build-dependencies
   * use debhelper compatibility level 13 (not 9);
 build-depend on debhelper-compat (not debhelper)
   * set Rules-Requires-Root: no
   * enable autopkgtest
   * update watch file:
 + use file format 4
 + mention gbp --uscan in usage comment
 + use substitution strings
   * simplify source helper script copyright-check
   * update copyright info:
 + stop track no 

Processed: Re: Bug#993843: [Pkg-zsh-devel] Bug#993843: zsh-static segfaults immediately

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #993843 [zsh-static] zsh-static segfaults immediately
Severity set to 'important' from 'serious'

-- 
993843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993843: [Pkg-zsh-devel] Bug#993843: zsh-static segfaults immediately

[Axel Beckert]

Control: severity -1 important

Hi,

Vincent: Thanks for discovering the issue with a statically compiled
binary loading a dynamic library.

Lowering the severity again.

Vincent Lefevre wrote:
> > Please forgive my ignorange in the automated test suites, but perhaps for a
> > future test, would verifying the expected exit status of these commands help
> > intercept this (and any other) weird problem?  :-)
> > 
> >   zsh-static -f -c "exit 0"
> >   zsh-static -f -c "exit 1"
> 
> No, this wouldn't help, because the libc6 version zsh-static has
> been compiled against would be the same as the one for the test.

Of course this will help! The tests are not just run at build time.
The tests are also regularily run against zsh "as installed" via
autopkgtest. See https://ci.debian.net/packages/z/zsh/

> > For comparison, busybox is statically linked:
> > 
> > > strace /bin/busybox -f -c "exit 0" 2>&1 | grep
> > > '^open[a-zA-Z0-9_]*(.*"[^"]*lib.*\.so\>[^"]*"' echo $?
> > 1
> 
> busybox is dynamically linked:

You're both right — depending which busybox-built package you've
isntalled: "busybox" or "busybox-static".

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#993964: gitaly 14.0 fails to start with error panic: failed to open gzip reader: EOF

[Pirate Praveen]

On ബു, സെപ്റ്റം 8 2021 at 10:46:06 വൈകു 
+0530 +0530, Pirate Praveen  wrote:
Sep 08 16:02:18 gitlab gitaly[4823]: panic: failed to open gzip 
reader: EOF


Fixed by updating golang-goprotobuf to 1.5.2 (Thanks to Nilesh for help 
with troubleshooting).

Bug#991629: marked as done (cloud.debian.org: Bullseye AWS AMI: cloud-init creates duplicate #includedir in /etc/sudoers)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 22:02:07 +
with message-id 
and subject line Bug#991629: fixed in cloud-init 20.4.1-2+deb11u1
has caused the Debian Bug report #991629,
regarding cloud.debian.org: Bullseye AWS AMI: cloud-init creates duplicate 
#includedir in /etc/sudoers
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 ow...@bugs.debian.org
immediately.)


-- 
991629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cloud.debian.org
Severity: important

Dear Maintainer,

I built a couple of instances using the bullseye test image
(debian-11-amd64-daily-20210728-717, or ami-0311ee36441c551b3 in
eu-west-2). In the sudoers file there is a duplicate includedir
statement; at the end of the file you will find the following contents:

"""
# See sudoers(5) for more information on "@include" directives:

@includedir /etc/sudoers.d

# Added by cloud-init v. 20.4.1 on Wed, 28 Jul 2021 20:40:05 +
#includedir /etc/sudoers.d
"""

If the sudoers.d directory is empty or only contains simple User_Spec
entries then there is no issue with this, but with aliases and similar
things which cannot be duplicated you end up with syntax errors when
calling sudo, for example:

example : Jul 29 08:38:09 : test : parse error in /etc/sudoers.d/example near 
line 9 ; PWD=/ ; USER=root ;

Effectively, cloud-init should NOT install this additional line into the
sudoers file as it already ships with an equivalent line.
--- End Message ---
--- Begin Message ---
Source: cloud-init
Source-Version: 20.4.1-2+deb11u1
Done: Ross Vandegrift 

We believe that the bug you reported is fixed in the latest version of
cloud-init, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ross Vandegrift  (supplier of updated cloud-init 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 12 Aug 2021 18:47:26 -0600
Source: cloud-init
Architecture: source
Version: 20.4.1-2+deb11u1
Distribution: bullseye
Urgency: high
Maintainer: Debian Cloud Team 
Changed-By: Ross Vandegrift 
Closes: 991629
Changes:
 cloud-init (20.4.1-2+deb11u1) bullseye; urgency=high
 .
   * Team upload.
   * cherry-pick upstream fix for duplicate includes in /etc/sudoers
 (Closes: #991629)
Checksums-Sha1:
 eade1917c4fa5626726fc492012c9ffc4391ab6b 2445 cloud-init_20.4.1-2+deb11u1.dsc
 b293d766807274fcc2584c5ff1eba11ffb6678c6 29384 
cloud-init_20.4.1-2+deb11u1.debian.tar.xz
 50e4dada0aa2bb373fb2ef6266b69276c24157c8 6544 
cloud-init_20.4.1-2+deb11u1_source.buildinfo
Checksums-Sha256:
 d025f1173f9738919daee191700f369c494da2ef0433778596ac0c269432f77d 2445 
cloud-init_20.4.1-2+deb11u1.dsc
 2131e6a4480c5310e9a404a3e7caaca5bc74b922b2083857dac1f97adfe4838e 29384 
cloud-init_20.4.1-2+deb11u1.debian.tar.xz
 dd9fcaf48aed7b5b2d374625ec4e08ba3a38ce6dd834f2bc4bbfe3f039729588 6544 
cloud-init_20.4.1-2+deb11u1_source.buildinfo
Files:
 fd2904fafba9d976c0944bf33e15feb1 2445 admin optional 
cloud-init_20.4.1-2+deb11u1.dsc
 6e68b30564d4312d00e32b03362853f9 29384 admin optional 
cloud-init_20.4.1-2+deb11u1.debian.tar.xz
 b3fd87564ecd74c1a5e1c8a1f4945680 6544 admin optional 
cloud-init_20.4.1-2+deb11u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE65xaF5r2LDCTz+zyV68+Bn2yWDMFAmE5IPoRHG5vYWhtQGRl
Ymlhbi5vcmcACgkQV68+Bn2yWDPd/hAAlAkNrVuyiv8ncegDQaYtoKozalsZdDsB
X/AIVpFZdGatJEnhdtauMxmARL9xH1j3s7uVB7NxPSuL8zqhG/O1SXVp0m703bnU
wyCYd5ke6MUK4jpfwlF+G6h+jEDWN/0rDRqqPfEUWb9jZQR977BfxiNJROg113O7
u0crFtOrnvD7zoWxZETvElMVKQpomGk6Xg+aNul+uzCKXfhkSLh40aw4xzJa0Rjc
9kCGYliSTAUud8M8pGDOU45b55BDisrvt5oqrzZm4pxjK7rqJ7xQr7M1qKDfKKCX
JCgKsceZhfm+kH8mczHgTcOwfFmBUVMRveCPrkIrKhsUyTLJ5W486FBXK8QWK0e6
3Yb1zbpnGrIIvUMsjCufFs+81ojdHUNRHSqzyP0VlNFd0QkSnSA8s8YFxYRIKwfL
weuGwp3aurQHimvvNgDGZo7TCa3SzqFfnqWtoFuMPF1/3vJ7qpHcl308Eqc5J+4R
39aREKE9WW0Rp1dt0MHhrwqgL3E2L5T+e2oXWnnQKHjmsqySwmidKnzzzacldFwV
9M0h3UHIG8dzYpQMP8u5C4xkW3MuCUWkgWwfhLw2IZtZk1KYSWtO3E828mIdP3FD
HKJNO9SsItWGhL1dVzC7qz7vrp6t6JkihORsvCUSuRk7B2WuUnsm65F3ExbZpTcQ
IRUVKJBu4/A=
=LVaz
-END PGP SIGNATURE End Message ---

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

[Kevin J. McCarthy]

On Tue, Sep 07, 2021 at 08:20:49PM -0700, Kevin J. McCarthy wrote:
I think the probability of users encountering that in practice is low. 
But if you're going through the effort of back-porting the fix, please 
wait and I'll commit a corrected fix tomorrow.


This is still on a branch, waiting for some feedback/testing, but for 
now you can see the corrected sort at:

https://gitlab.com/muttmua/mutt/-/commit/fa2fef4618ed45d9f4011ea76fd8bc3844d59c88

This is applies on top of the commit from 2.1.2:
https://gitlab.com/muttmua/mutt/-/commit/647efbd151ee452eaca5f42e4f636a5ed7a32331

which depends on this commit if backported earlier than 1.13.4:
https://gitlab.com/muttmua/mutt/-/commit/6051760c2cf492ada1e06d910c0c2c05607c08bc

-Kevin

Bug#993665: marked as done (debianutils: tempfile still required in printer-driver-pnm2ppa)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 21:18:42 +
with message-id 
and subject line Bug#993665: fixed in debianutils 5.4-4
has caused the Debian Bug report #993665,
regarding debianutils: tempfile still required in printer-driver-pnm2ppa
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 ow...@bugs.debian.org
immediately.)


-- 
993665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debianutils
Version: 5.4-3
Severity: critical
Justification: breaks unrelated software

The tempfile saga is not over. It might be wise grepping through the
maintainer scripts of all packages.

printer-driver-pnm2ppa still requires it.

Best




-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.13+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debianutils depends on:
ii  libc6  2.31-17

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debianutils
Source-Version: 5.4-4
Done: Clint Adams 

We believe that the bug you reported is fixed in the latest version of
debianutils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated debianutils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Sep 2021 16:57:40 -0400
Source: debianutils
Binary: debianutils
Architecture: source amd64
Version: 5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Clint Adams 
Changed-By: Clint Adams 
Description:
 debianutils - Miscellaneous utilities specific to Debian
Closes: 993665
Changes:
 debianutils (5.4-4) unstable; urgency=medium
 .
   * Add Breaks on printer-driver-pnm2ppa.  closes: #993665.
Checksums-Sha1:
 37564a96a83237bee91dc06370ac770b5cc4530e 1879 debianutils_5.4-4.dsc
 89c15ac1e628a387795d41fc9aceaec3b222df3e 21464 debianutils_5.4-4.debian.tar.xz
 d96a2431bdc80ac0195177492ef438bdf7c2f072 4702 debianutils_5.4-4_amd64.buildinfo
 7edb9791553cf1253db01df38e1fb976cb8dac2f 93496 debianutils_5.4-4_amd64.deb
Checksums-Sha256:
 1619af1d123ad70046481a04af5a1bec3400dbdb06ad6403987e005e19b36593 1879 
debianutils_5.4-4.dsc
 d47e1eda2a36f1442e4a52e5db3ca733ab3ee7d66f40da2d1216daac01fd010a 21464 
debianutils_5.4-4.debian.tar.xz
 701cbe726623968b230bde2441311c0dc7d9977512bba4c33258ba55bd111eb2 4702 
debianutils_5.4-4_amd64.buildinfo
 7306089145a90e254567b3aaf6a9aea773bd787546d5d814d63722577b1d02d6 93496 
debianutils_5.4-4_amd64.deb
Files:
 49c4e1665647a4a6940f8b7ee0e25675 1879 utils required debianutils_5.4-4.dsc
 0f1c45bd8e199ce89862b6696911ea87 21464 utils required 
debianutils_5.4-4.debian.tar.xz
 4ac9e35f4ee06a863e73ef0b2b29f152 4702 utils required 
debianutils_5.4-4_amd64.buildinfo
 f632c24660fb66a023d5c43edbee9f55 93496 utils required 
debianutils_5.4-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAmE5JTwACgkQVZIzHhmd
OKhsXw//YdmgHBQjLtmTEcL+/+7NL5EHCfdlpsOpxwNPT/S/hhduIDhuXW84ze5B
L/3d9+2rosi0Nj2r4ZEGnX6y8spI+44UyzRvSi65FYgjJVddXObLD6T1d8VLckb2
D1sC0ymCPbgdBgRUQBv9EiSSIYE8GRiFeqQfrzqRpNQadDHMoQE15XDkI0dShA2D
6051wNc1V+y96nmhMyU6AL7XEW5po3vB5KD0jf1YLqLKpR/89uPbuP0Aa9aav+Re
i4wW/mWor3IxNt3H08hCrWexr2PLnrwu/Mo4+yoxS/1BUX9+hKySyoZzOIe2BJ0V
nPTI7sHFdAc+oh9hZvKe1MM2wtSaJHcnurkURS3Vd7ho6LWz5ThpH0TECb2XBvfX
NQpJyAV4MlXZoixr2Ozxl8FCzq8MArFHpENLQPHHaeZkHwP5fKA0xTMPr+K1S8Hr
YAKOPTIU9w91ikxakYkCVFt5OJHsTz68zyzLnuElC3vSBnE9turtPY8OVwA8LrpJ
PsBdpB7cTBi6nPHLojf1kJOdyZW/X6DzF8k8Iqq20TIpPvuh8qq8azx/2nGpCdIG
DgXt/hNaW/XfKBEwNFUiADjiXHxUTcATEYWJ3wclhM8ipFNBkU8mp6eN6+kxF3WG
QpebUkLd0b4ijEytNMhR7AbPMOtK+pz1Y/0vJP90/WkTtxCu6xA=
=isQu
-END PGP SIGNATURE End Message ---

Bug#993935: marked as pending in debian-edu-config

[Wolfgang Schweer]

Control: tag -1 pending

Hello,

Bug #993935 in debian-edu-config reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/7215fff69868d7b362240e5c2896850a5888ac60


Adjust sbin/debian-edu-ltsp-install. (Closes: #993935)

 Extend main server related exclude list.
 Add slapd and xrdp-sesman to the list of masked services.
 Ensure home directory access after above changes.

Signed-off-by: Wolfgang Schweer 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993935

Processed: Bug#993935 marked as pending in debian-edu-config

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993935 [debian-edu-config] debian-edu-ltsp-install: Netboot image exposes 
private data and crypto keys
Added tag(s) pending.

-- 
993935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993494: marked as done (thunderbird FTBFS with autoconf 2.71)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 20:36:36 +
with message-id 
and subject line Bug#993494: fixed in thunderbird 1:78.14.0-1
has caused the Debian Bug report #993494,
regarding thunderbird FTBFS with autoconf 2.71
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 ow...@bugs.debian.org
immediately.)


-- 
993494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thunderbird
Version: 1:78.4.0-1
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=thunderbird=sid
https://buildd.debian.org/status/package.php?p=thunderbird=experimental

...
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
autoreconf: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
autoreconf: error: configure.in: AC_INIT not found; not an autoconf script?
dh_autoreconf: error: autoreconf -f -i returned exit code 1
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:78.14.0-1
Done: Carsten Schoenert 

We believe that the bug you reported is fixed in the latest version of
thunderbird, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Sep 2021 19:57:22 +0200
Source: thunderbird
Architecture: source
Version: 1:78.14.0-1
Distribution: unstable
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 993494
Changes:
 thunderbird (1:78.14.0-1) unstable; urgency=medium
 .
   * [6dc6817] d/changelog: Correct TB version for referenced MFSA
   * [38f01f4] d/rules: Don't run dh_autoreconf
 (Closes: #993494)
   * [09c4cde] New upstream version 78.14.0
 Fixed CVE issues in upstream version 78.14.0 (MFSA 2021-42):
 CVE-2021-38493: Memory safety bugs fixed in Thunderbird 78.14 and
 Thunderbird 91.1
Checksums-Sha1:
 cd4139c629ec07d9dc7878c4a36ecc1efc8210b9 8135 thunderbird_78.14.0-1.dsc
 aae17f60119e112853b88f67f858c28c324ac396 11809480 
thunderbird_78.14.0.orig-thunderbird-l10n.tar.xz
 45e6422abd4f583d7dbf691ffd454194933e2fc4 372484692 
thunderbird_78.14.0.orig.tar.xz
 56c1f763b545945ecf33b67709dc077dba74d11c 707004 
thunderbird_78.14.0-1.debian.tar.xz
 8062e4faa26bff0e5bb6171d9627a3ff91ea6650 35668 
thunderbird_78.14.0-1_amd64.buildinfo
Checksums-Sha256:
 15fcbdb501a93abdbf5a7c1a748676307b115fce438ac2d87b76f9115f3ae43e 8135 
thunderbird_78.14.0-1.dsc
 54a3150bcce4c0b2e95d95a9165883bf678d9a8dd44d53a09d8229f5834365d4 11809480 
thunderbird_78.14.0.orig-thunderbird-l10n.tar.xz
 5aad14cbd05fa04d205e4ded37171213952eb8c5396d95c74dd423ade8d43842 372484692 
thunderbird_78.14.0.orig.tar.xz
 ea6b5ce75e886ab5b1a672e5f58d114acd35e4107d948c05e620cb4e6bdc0430 707004 
thunderbird_78.14.0-1.debian.tar.xz
 414884cd258dc02c15646818e320b71b2e24803309cc5d84b31aae1992fc8585 35668 
thunderbird_78.14.0-1_amd64.buildinfo
Files:
 f2aa31940737e6395572188ab6c94147 8135 mail optional thunderbird_78.14.0-1.dsc
 4c0c3db87a13087f78abbe715614d86e 11809480 mail optional 
thunderbird_78.14.0.orig-thunderbird-l10n.tar.xz
 b6ae5b0c2473e1da859dfbb20200a741 372484692 mail optional 
thunderbird_78.14.0.orig.tar.xz
 fabe078f47f37366cc9968c857104f5c 707004 mail optional 
thunderbird_78.14.0-1.debian.tar.xz
 51d669fea0e28a805d7580ead3cf2733 35668 mail optional 
thunderbird_78.14.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmE5EUEACgkQgwFgFCUd
HbDVFw/8DPCWWzjhovoN2Uag1yYFjzvWOSLHunOBkQn/Bl6cJ8+Mn/OYMjWJKwG0
oOol9Uku4PuA7roxKvKQzarEowO5Be8qCWELm8JpM9/XTq0OxuN6rT9hoxalXMhJ
TLMMfLuw/rUyJHpcSBFwhoACBLGG4E+YFTjnKIE8Xh/OjPwpy5eZ9dtVAqyQtHuQ
AAeSM/ZAOTrd1TnSMEKH/R/Xo73H/gR4uHHCFk9GyRtamzJu/ICYKcxNANeRrJiY
o7/VMw4bOgAG4q35WLK7uTBucQCBZO7Dxm7pVGHXQvJtjFHDVycp8jqCRT8nUxf9
Ngpe2cQV8JKdJkUR+bnox8p+vUWQ+lS2lhxI80DjYdeDKa6rxFrEZnt8vrJcMQtU
6GSezfZBedKtoI0uLlHCAnK9vH7pGRVl4Y9S/x9TXrODqenMvBQE32UFespeLzEV
utb1XPLMD3WFyJjUcwFCeJ+vW+PXdkiUHx7X2CreICiSCC0KsOpIr74z/ODzXNJY

Bug#993935: debian-edu-ltsp-install: Netboot image exposes private data and crypto keys

[Wolfgang Schweer]

[ Dominik George, 2021-09-08 ]
> Package: debian-edu-config
> Version: 2.11.56
> Severity: critical
> Tags: security
> Justification: root security hole
> X-Debbugs-Cc: Debian Security Team 
> 
> The LTSP netboot image produced by debian-edu-ltsp-install includes full 
> copies
> of files that should never leave the Debian Edu main server, if run on a 
> so-called
> "combined server" (a system using the Main Server and Terminal Server 
> profiles,
> as done in small installations).

Yes, confirmed.
 
> Among these files are full copies of, among others:
> 
>  - /var/lib/ldap, containing the full, unencrypted LDAP database with all
>private information on all users, password hashes, and Kerberos keys
>  - /etc/krb5-kdc, containing information on decrypting Kerberos data in the
>LDAP database
>  - /etc/gosa, containing the (encrypted) LDAP manager credentials, plus the
>key to decrypt it

These should be added to the exclude list, and some more. Other fixes 
are then needed, too.
 
> Any user with access to the local terminal server network can acquire 
> the netboot image, unauthenticated, and extract the listed information 
> from it.

SSH, tftp: I fail to get the SqushFS image file in both cases. But then 
I'm no expert.
 
> The issue is caused by the new LTSP system using the LTSP PnP system 
> now in all cases, thus packing the entire mai nserver filesystem in 
> squashfs image. The debian-edu-ltsp-install script produces a list of 
> files to exclude from the image, which is not sufficient, most 
> probably because it was tailored to the use case where the image is 
> produced from a dedicated Terminal Server instead of a combined 
> server.

Yes.
 
> IMHO, the use case of the combined server cannot be fixed. The new 
> LTSP system de facto disallows any use of a combiend server – even if 
> we make a very carefully curated list of excluded files, any 
> administrator would have to take care to add their own excludes for 
> just about any file they place on the main server that was not palced 
> there by the Debian Edu software. In fact, the whole new LTSP system 
> seems unfit to be used on any server that is not limited to producing 
> LTSP images, and supporting netbooting them.

While it's best to use separated LTSP servers (like recommended in the 
manual), people are used to get a turnkey system like the combined 
server. So maybe we should strive to keep that option (and add a hint to 
the exclude list in the manual).
 
> For now, the issue should be mitigated by carefully adding all 
> relevant paths that are known to exist only on the main server to the 
> exclude list, but I do not think that is a viable fix in the long 
> term.

I've set up a test environment and will take a look.

Wolfgang


signature.asc
Description: PGP signature

Bug#993955: marked as pending in lintian

[Felix Lechner]

Control: tag -1 pending

Hello,

Bug #993955 in lintian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/lintian/lintian/-/commit/88e5cc61afa5503ac24201c44787ef2d83f03f17


Drop recommendation to implement usr-merge for individual packages. (Closes: 
#993955)

This tag is a research tag. It was not issued for any packages, but the
description is accessible on Lintian's website and should reflect the current
consensus on the mailing lists.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993955

Processed: Bug#993955 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993955 [lintian] lintian: Offers incorrect/harmful advice regarding 
usrmerge
Added tag(s) pending.

-- 
993955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993915: libguestfs FTBFS on some buildds

[Aurelien Jarno]

control: tag -1 + patch

On 2021-09-08 09:32, Adrian Bunk wrote:
> Source: libguestfs
> Version: 1:1.44.1-4
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/logs.php?pkg=libguestfs=1%3A1.44.1-4
> 
> ...
> unset XDG_RUNTIME_DIR; \
>   if ! test -w /dev/kvm; then \
>   export LIBGUESTFS_BACKEND_SETTINGS=force_tcg; \
>   fi
> make -C /<>/debian/build-4 quickcheck
> make[2]: Entering directory '/<>/debian/build-4'
> ./run test-tool/libguestfs-test-tool
> libguestfs: error: converting path to absolute path: XDG_RUNTIME_DIR: 
> /run/user/2952: realpath: No such file or directory
>  
>  *IMPORTANT NOTICE
>  *
>  * When reporting bugs, include the COMPLETE, UNEDITED
>  * output below in your bug report.
>  *
>  
> /<>/debian/build-4/test-tool/.libs/libguestfs-test-tool: failed 
> parsing environment variables.
> Check earlier messages, and the output of the ‘printenv’ command.
> make[2]: *** [Makefile:3187: quickcheck] Error 1
> 
> 
> 08:46 < bunk> on x86 and arm64, *except* x86-grnet-01
> 08:46 < bunk> 1. Why not on grnet?
> 08:46 < bunk> 2. Is dh compat 13 worth a recommendation to the maintainer?
> 09:17 < aurel32> i guess it's because the buildds at grnet are using 
> pybuildd, which is not affected by the libpam-systemd/schroot bug
> 09:19 < aurel32> and yes debhelper compat 13 might help there, at least 
> present a stable environment
> 
> 
> The dh compat 13 change is
> 
>   The dh_auto_* helpers now reset the environment variables
>   HOME and common XDG_* variable.  Please see description of
>   the environment variables in "ENVIRONMENT" for how this is
>   handled.

Note that the issue has been introduced by the following commit:
https://salsa.debian.org/libvirt-team/libguestfs/-/commit/254b60b64de1346511a2262b5161973f5f01dcaa

Before that commit the unset and make where called in the same subshell,
so XDG_RUNTIME_DIR was correctly unset when calling make.

After that commit, the first part is executed in one subshell and the
make in another subshell, causing the first part to just be a noop.

Therefore a minimal fix is the following:

--- a/debian/rules
+++ b/debian/rules
@@ -130,7 +130,7 @@ ifneq "" "$(findstring 
$(DEB_HOST_ARCH),$(QUICKCHECK_ARCHITECTURES))"
unset XDG_RUNTIME_DIR; \
if ! test -w /dev/kvm; then \
export LIBGUESTFS_BACKEND_SETTINGS=force_tcg; \
-   fi
+   fi ; \
make -C $(CURDIR)/debian/build-$(BUILD_COUNT) quickcheck
 endif

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

Processed: Re: libguestfs FTBFS on some buildds

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #993915 [src:libguestfs] libguestfs FTBFS on some buildds
Added tag(s) patch.

-- 
993915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993967: License incompatible with current Qt

[Bastian Germann]

Package: tortoisehg
Severity: serious

At https://groups.google.com/g/thg-dev/c/AYFxHk5aLKg/ I started a conversation about TortoiseHg 
(GPLv2-only) having an incompatible license with the currently packaged PyQt5 version (GPLv3). In 
almost a year, upstream did not do anything to handle the issue, so I file this bug. It should be 
possible to convert the source to PySide2 or QtPy (handles PyQt and PySide versions).

Bug#993494: marked as done (thunderbird FTBFS with autoconf 2.71)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 17:37:20 +
with message-id 
and subject line Bug#993494: fixed in thunderbird 1:91.1.0-1
has caused the Debian Bug report #993494,
regarding thunderbird FTBFS with autoconf 2.71
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 ow...@bugs.debian.org
immediately.)


-- 
993494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thunderbird
Version: 1:78.4.0-1
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=thunderbird=sid
https://buildd.debian.org/status/package.php?p=thunderbird=experimental

...
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
autoreconf: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
autoreconf: error: configure.in: AC_INIT not found; not an autoconf script?
dh_autoreconf: error: autoreconf -f -i returned exit code 1
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:91.1.0-1
Done: Carsten Schoenert 

We believe that the bug you reported is fixed in the latest version of
thunderbird, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Sep 2021 07:36:10 +0200
Source: thunderbird
Architecture: source
Version: 1:91.1.0-1
Distribution: experimental
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 993494 993594
Changes:
 thunderbird (1:91.1.0-1) experimental; urgency=medium
 .
   * [0b1d9f9] New upstream version 91.1.0
 Fixed CVE issues in upstream version 91.1 (MFSA 2021-41):
 CVE-2021-38495: Memory safety bugs fixed in Thunderbird 91.1
   * [4313e64] Rebuild patch queue from patch-queue branch
 Added patch:
 fixes/Bug-1727113-Never-require-that-addons-are-signed-for-Thun.patch
 (Closes: #993594)
 Modified patch:
 
porting-armhf/Bug-1526653-Include-struct-definitions-for-user_vfp-and-u.patch
   * [234c566] d/rules: Don't run dh_autoreconf
 (Closes: #993494)
   * [bce15d7] thunderbird: Set package x11-utils as fallback
 Install x11-utils only if kdialog or zenity aren't present on the system.
Checksums-Sha1:
 39356feacaa05ab24dca1e47f9eb5f249300e60e 8463 thunderbird_91.1.0-1.dsc
 ba736f50a1e4373b5db138d00a0ade6bc7c867a3 12251968 
thunderbird_91.1.0.orig-thunderbird-l10n.tar.xz
 c8ea068d04f4d97b71fe4af3d468da5527a59de3 429020588 
thunderbird_91.1.0.orig.tar.xz
 f7ad9d5d0aca0973fc225ae43278ac6f8a43cb55 538228 
thunderbird_91.1.0-1.debian.tar.xz
 c83c52a8e5afb3043a907d135f78044c56ae4b33 36360 
thunderbird_91.1.0-1_amd64.buildinfo
Checksums-Sha256:
 9b9a62a966cac269c236e62321f40e154f30aaa70fc555d4afdb8832f88c67a9 8463 
thunderbird_91.1.0-1.dsc
 4464e5c1e55d31113960c1c69a6992806568e7cd7f1e33e928ba4883470488f6 12251968 
thunderbird_91.1.0.orig-thunderbird-l10n.tar.xz
 d9983183e618e563e6a9bd25448c491ad4e4e57c40b02483ab3c0d0f9dbaa380 429020588 
thunderbird_91.1.0.orig.tar.xz
 20746f6a65a677afed8cd2d8b8193afe39f004dc7685b3c0a8c7026a7d08cd28 538228 
thunderbird_91.1.0-1.debian.tar.xz
 613e3684e6286bc66bf4fd12c93e749d2d14553c430519717c877cc478dc7d8d 36360 
thunderbird_91.1.0-1_amd64.buildinfo
Files:
 4875278755787ddf14a2a288c1944ab0 8463 mail optional thunderbird_91.1.0-1.dsc
 039938a947f56de240a8b6772d043540 12251968 mail optional 
thunderbird_91.1.0.orig-thunderbird-l10n.tar.xz
 73dbde354f0d3db51f4b1f1f791501bf 429020588 mail optional 
thunderbird_91.1.0.orig.tar.xz
 1ec09d948a8ec8152097b61a4d05388d 538228 mail optional 
thunderbird_91.1.0-1.debian.tar.xz
 96eabf48b3717a1973f1fa64e7424967 36360 mail optional 
thunderbird_91.1.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmE47vUACgkQgwFgFCUd
HbDtHQ/+MDe9IRHbxxWxNvTtjT5p2iFllEAkBDm5XlEFEfnHsLiWQNLTwa+BkInQ
cJIP8nFWGrZ+ttYuy+0gXRwNkHbg6KDXZgoraYr7Cxj02Tp7eR9O2eX3ce9GQT+x
pJiDjcZiWavSjG7my/79CG7Pz6B6nzK8qHT+aNj2wT00of7KQUJqxXXZKg9K4/Ug

Bug#984956: closing 984956

[Samuel Thibault]

close 984956 4.1.1-5
thanks

Processed: closing 984956

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 984956 4.1.1-5
Bug #984956 {Done: Alastair McKinstry } [openmpi-bin] 
openmpi-bin: with mpirun --host : orte crashes with FORCE-TERMINATE 
[...] plm_base_launch_support.c
Marked as fixed in versions openmpi/4.1.1-5.
Bug #984956 {Done: Alastair McKinstry } [openmpi-bin] 
openmpi-bin: with mpirun --host : orte crashes with FORCE-TERMINATE 
[...] plm_base_launch_support.c
Bug 984956 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
984956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993964: gitaly 14.0 fails to start with error panic: failed to open gzip reader: EOF

[Pirate Praveen]

Package: gitaly
Version: 14.0.10+dfsg-1
Severity: grave

gitaly 14.0.10 from https://wiki.debian.org/gitlab/devel fails to start 
and


journalctl -xel -u gitaly --no-pager

gives the following error

Sep 08 16:02:18 gitlab gitaly[4823]: panic: failed to open gzip reader: 
EOF

Sep 08 16:02:18 gitlab gitaly[4823]: goroutine 1 [running]:
Sep 08 16:02:18 gitlab gitaly[4823]: 
gitlab.com/gitlab-org/gitaly/internal/praefect/protoregistry.init.0()
Sep 08 16:02:18 gitlab gitaly[4823]: 
gitlab.com/gitlab-org/gitaly/internal/praefect/protoregistry/protoregistry.go:32 
+0x227
Sep 08 16:02:18 gitlab systemd[1]: gitaly.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT

Bug#893077: marked as done (gnucash: FTBFS on Debian 9.4 (freshly installed) FAIL: test-report-utilities)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 18:49:51 +0200
with message-id <1c4646d2-e0c3-4c2e-86bb-439c5088d...@debian.org>
and subject line Re: Bug#893077: gnucash: FTBFS on Debian 9.4 (freshly 
installed) FAIL: test-report-utilities
has caused the Debian Bug report #893077,
regarding gnucash: FTBFS on Debian 9.4 (freshly installed) FAIL: 
test-report-utilities
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 ow...@bugs.debian.org
immediately.)


-- 
893077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash
Version: 2.6.18-1
Severity: serious
Justification: fails to build from source (but built successfully on other 
systems?)

Dimitry:

   * What led up to the situation?

Fresh install of Debian 9.4, updated via apt, and then:

apt build-dep gnucash
apt-get source gnucash

Unpacked files, did dpkgs-checkbuilddeps
(no error)
then:
dpkg-buildpackage -b -us -us -j8 (with and without -rfakeroot)

I get the following error that halts the build:

FAIL: test-report-utilities
==
   GnuCash 2.6.15: src/report/report-system/test/test-suite.log
==

# TOTAL: 5
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test-report-utilities
===

* 23:15:12  WARN  failed to load gncmod-backend-dbi from 
/usr/lib/x86_64-linux-gnu/gnucash/gnucash
* 23:15:12  CRIT  required library gncmod-backend-dbi not found.
* 23:15:12  WARN  failed to load gncmod-backend-xml from 
/usr/lib/x86_64-linux-gnu/gnucash/gnucash
* 23:15:12  CRIT  required library gncmod-backend-xml not found.
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;   or pass the --no-auto-compile argument to disable.
;;; compiling 
/usr/src/gnucash/gnucash-2.6.15/src/report/report-system/test/./test-report-utilities.scm
;;; compiling 
../../../../src/report/report-system/test/gnucash/report/report-system/test/test-extras.scm
;;; compiled 
/home/spambrat/.cache/guile/ccache/2.0-LE-8-2.0/usr/src/gnucash/gnucash-2.6.15/src/report/report-system/test/test-extras.scm.go
;;; compiled 
/home/spambrat/.cache/guile/ccache/2.0-LE-8-2.0/usr/src/gnucash/gnucash-2.6.15/src/report/report-system/test/test-report-utilities.scm.go
FAIL test-report-utilities (exit status: 1)
 

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
A new Debian release (bullseye) containing a fix was released as stable. Let's 
close this bug.--- End Message ---

Bug#978891: marked as done (r-cran-ncdf4: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 16:03:24 +
with message-id 
and subject line Bug#978891: fixed in r-cran-ncdf4 1.17-2
has caused the Debian Bug report #978891,
regarding r-cran-ncdf4: ftbfs with autoconf 2.70
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 ow...@bugs.debian.org
immediately.)


-- 
978891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:r-cran-ncdf4
Version: 1.17-1
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/r-cran-ncdf4_1.17-1_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -sa -rfakeroot
dpkg-buildpackage: info: source package r-cran-ncdf4
dpkg-buildpackage: info: source version 1.17-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Dylan Aïssi 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --buildsystem R
   dh_auto_clean -O--buildsystem=R
   dh_autoreconf_clean -O--buildsystem=R
   dh_clean -O--buildsystem=R
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building r-cran-ncdf4 using existing 
./r-cran-ncdf4_1.17.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building r-cran-ncdf4 in r-cran-ncdf4_1.17-1.debian.tar.xz
dpkg-source: info: building r-cran-ncdf4 in r-cran-ncdf4_1.17-1.dsc
 debian/rules build
dh build --buildsystem R
   dh_update_autotools_config -O--buildsystem=R
   dh_autoreconf -O--buildsystem=R
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cd tools && ./regenerate
rm: cannot remove '../Makefile': No such file or directory
rm: cannot remove '../src/Makevars': No such file or directory
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.
dh_auto_configure
make[1]: Leaving directory '/<>'
   dh_auto_build -O--buildsystem=R
   dh_auto_test -O--buildsystem=R
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary
dh binary --buildsystem R
   dh_testroot -O--buildsystem=R
   dh_prep -O--buildsystem=R
   dh_auto_install -O--buildsystem=R
I: R Package: ncdf4 Version: 1.17
I: Building using R version 4.0.2-1
I: R API version: r-api-4.0
I: Using built-time from d/changelog: Fri, 03 Jan 2020 18:51:25 +0100
mkdir -p /<>/debian/r-cran-ncdf4/usr/lib/R/site-library
R CMD INSTALL -l 
/<>/debian/r-cran-ncdf4/usr/lib/R/site-library --clean . 
"--built-timestamp='Fri, 03 Jan 2020 18:51:25 +0100'"
* installing *source* package ‘ncdf4’ ...
files ‘configure’, ‘configure.ac’, ‘tools/aclocal.m4’, ‘tools/configure.ac’ 
have the wrong MD5 checksums
** using staged installation
configure.ac: starting
./configure: line 1764: syntax error near unexpected token `;;'
./configure: line 1764: ` as_dir=./ ;;'
ERROR: configuration failed for package ‘ncdf4’
* removing ‘/<>/debian/r-cran-ncdf4/usr/lib/R/site-library/ncdf4’
dh_auto_install: error: R CMD INSTALL -l 
/<>/debian/r-cran-ncdf4/usr/lib/R/site-library --clean . 
"--built-timestamp='Fri, 03 Jan 2020 18:51:25 +0100'" returned exit code 1
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: r-cran-ncdf4
Source-Version: 1.17-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
r-cran-ncdf4, which is due to be installed in the Debian FTP 

Bug#993946: fakechroot: adduser fails with glibc 2.32

[Johannes Schauer Marin Rodrigues]

Quoting Johannes Schauer Marin Rodrigues (2021-09-08 13:59:02)
> since the upload of glibc 2.32 to unstable, adduser under fakechroot
> fails because it is not wrapping some library call and thus read the
> system's /etc/passwd instead of the chroot's.
> 
> Some bits from strace output:

I managed to create a more minimal reproducer for this problem:

$ perl -e 'print getpwnam("_apt")'

This is with glibc 2.31:

[pid  3889] getcwd("/tmp/chroot", 4096) = 12
[pid  3889] openat(AT_FDCWD, "/tmp/chroot/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
[pid  3889] lseek(3, 0, SEEK_CUR)   = 0
[pid  3889] fstat(3, {st_mode=S_IFREG|0644, st_size=922, ...}) = 0
[pid  3889] read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 922
[pid  3889] close(3)= 0
[pid  3889] getcwd("/tmp/chroot", 4096) = 12
[pid  3889] openat(AT_FDCWD, "/tmp/chroot/etc/shadow", O_RDONLY|O_CLOEXEC) = 3
[pid  3889] lseek(3, 0, SEEK_CUR)   = 0
[pid  3889] fstat(3, {st_mode=S_IFREG|0640, st_size=501, ...}) = 0
[pid  3889] read(3, "root:*:18878:0:9:7:::\ndaemon"..., 4096) = 501
[pid  3889] close(3)= 0

And this is with glibc 2.32:

[pid 2372761] openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
[pid 2372761] fstat(3, {st_mode=S_IFREG|0644, st_size=2902, ...}) = 0
[pid 2372761] lseek(3, 0, SEEK_SET) = 0
[pid 2372761] read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 2902
[pid 2372761] close(3)  = 0
[pid 2372761] openat(AT_FDCWD, "/etc/shadow", O_RDONLY|O_CLOEXEC) = -1 EACCES 
(Permission denied)

Curiously, with old glibc, there is an additional getcwd call before the
openat...

signature.asc
Description: signature

Bug#978891: r-cran-ncdf4: ftbfs with autoconf 2.70

[Nilesh Patra]

Hi Jeremy,

On 9/8/21 8:24 PM, Jeremy Sowden wrote:
>> [1] https://bugs.debian.org/978891
> 
> Try this patch.

Thank you very much, works perfectly!
I just uploaded with your patch applied.

Nilesh



OpenPGP_signature
Description: OpenPGP digital signature

Bug#978891: r-cran-ncdf4: ftbfs with autoconf 2.70

[Jeremy Sowden]

On 2021-09-08, at 16:06:34 +0200, Andreas Tille wrote:
> Control: tags -1 help
>
> Hi,
>
> I need to admit that from my naive perspective this is a bug in
> autoconf.  In the log that is provided in the bug report[1] you can see
> this here:
>
>dh_autoreconf -O--buildsystem=R
> configure.ac:44: warning: AC_OUTPUT should be used without arguments.
> configure.ac:44: You should run autoupdate.
> configure.ac:44: warning: AC_OUTPUT should be used without arguments.
> configure.ac:44: You should run autoupdate.
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> cd tools && ./regenerate
> rm: cannot remove '../Makefile': No such file or directory
> rm: cannot remove '../src/Makevars': No such file or directory
> configure.ac:44: warning: AC_OUTPUT should be used without arguments.
> configure.ac:44: You should run autoupdate.
> configure.ac:44: warning: AC_OUTPUT should be used without arguments.
> configure.ac:44: You should run autoupdate.
>
>
> This results later in:
>
>
> ** using staged installation
> configure.ac: starting
> ./configure: line 1764: syntax error near unexpected token `;;'
> ./configure: line 1764: ` as_dir=./ ;;'
> ERROR: configuration failed for package ‘ncdf4’
>
>
>
> I checked the resulting configure file and the part in question looks like:
>
>
> echo "configure.ac: starting"
>
>  as_dir=./ ;;
> */) ;;
> *) as_dir=$as_dir/ ;;
>   esac
> for ac_exec_ext in '' $ac_executable_extensions; do
>   if as_fn_executable_p "$as_dir$ac_word$ac_exec_ext"; then
> ac_cv_prog_HAS_NC_CONFIG="yes"
> printf "%s\n" "$as_me:${as_lineno-$LINENO}: found 
> $as_dir$ac_word$ac_exec_ext" >&5
> break 2
>   fi
> done
>
>
> It looks like a case statement intended but not injected by autoconf.  I
> have no idea how this can be influenced by some configure.ac statement.
>
> Kind regards
>
>Andreas.
>
> [1] https://bugs.debian.org/978891

Try this patch.

J.
From 2e5bda24d3b2799d21b5342290fbeed54cf83101 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden 
Date: Wed, 8 Sep 2021 14:50:40 +
Subject: [PATCH] Quote allowed M4 pattern.

Signed-off-by: Jeremy Sowden 
---
 tools/configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/configure.ac b/tools/configure.ac
index 7d781c514c2e..16579d35a8ab 100644
--- a/tools/configure.ac
+++ b/tools/configure.ac
@@ -2,7 +2,7 @@ AC_INIT(src/Makevars.in)
 
 echo "configure.ac: starting"
 
-m4_pattern_allow(AC_PATH_NETCDF)
+m4_pattern_allow([AC_PATH_NETCDF])
 
 : ${R_HOME=`R RHOME`}
 if test -z "${R_HOME}"; then
-- 
2.33.0



signature.asc
Description: PGP signature

Bug#993956: nfs-utils: trying to overwrite '/usr/share/man/man8/rpc.mountd.8.gz', which is also in package nfs-kernel-server 1:2.5.4-1~exp3

[Salvatore Bonaccorso]

Source: nfs-utils
Version: 1:2.5.4-1~exp3
Severity: serious
Justification: fails to upgrade
X-Debbugs-Cc: car...@debian.org

Hi

Trying to update from unstable to 1:2.5.4-1~exp3:

Preparing to unpack .../nfs-kernel-server_1%3a2.5.4-1~exp3_amd64.deb ...
Unpacking nfs-kernel-server (1:2.5.4-1~exp3) over (1:1.3.4-6) ...
Preparing to unpack .../nfs-common_1%3a2.5.4-1~exp3_amd64.deb ...
Unpacking nfs-common (1:2.5.4-1~exp3) over (1:1.3.4-6) ...
dpkg: error processing archive 
/var/cache/apt/archives/nfs-common_1%3a2.5.4-1~exp3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man8/rpc.mountd.8.gz', which is also in 
package nfs-kernel-server 1:2.5.4-1~exp3
nfs-utils.service is a disabled or a static unit not running, not starting it.
Errors were encountered while processing:
 /var/cache/apt/archives/nfs-common_1%3a2.5.4-1~exp3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Should rpc.mountd.8 be keept in the actual nfs-kernel-server package instead of
nfs-common as rpcmountd is nfs-kernel-server?

Regards,
Salvatore

Bug#993955: lintian: Offers incorrect/harmful advice regarding usrmerge

[Stuart Prescott]

Package: lintian
Version: 2.105.0
Severity: serious
Justification: unsuitable for release in the release maanger's opinion
X-Debbugs-Cc: stu...@debian.org

Dear Maintainer,

Following up on a conversation in #debian-qa, the current wording of the
classification tag "unmerged-usr" is problematic:

C: unmerged-usr
N: 
N:   The named file is being installed in a legacy location. Modern Debian 
systems install this file under /usr.
N:   
N:   Please move this file to a suitable place under the "merged /usr" scheme. 
Please consult the provided
N:   references as to where that might be.
N: 
N:   Please refer to https://wiki.debian.org/UsrMerge, 
https://wiki.debian.org/Teams/Dpkg/MergedUsr, Bug#978636,
N:   https://lists.debian.org/debian-devel/2020/11/#00232, 
https://lists.debian.org/debian-devel/2020/12/#00386,
N:   https://lists.debian.org/debian-devel-announce/2019/03/msg1.html, 
https://rusty.ozlabs.org/?p=236,
N:   https://www.linux-magazine.com/Issues/2019/228/Debian-usr-Merge, 
https://lwn.net/Articles/773342/, and
N:   https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/ 
for details.
N: 
N:   Visibility: classification
N:   Show-Always: no
N:   Check: files/hierarchy/merged-usr
N:   This tag is a classification. There is no issue in your package.

As noted in the discussion, there are two problems here:

* The advice "Please move this file" contradicts the emerging consensus on the
  correct way to handle the transition. There has been a long discussion on
  debian-devel about this where more details can be found. This consensus may
  well change, of course, and then we would want lintian to be opinionated...
  but the advice given in the tag is contrary to the current position.

* The tag is self-contradictory, offering both an instruction to act and
  also saying "There is no issue in your package."

As indicated by a member of the Release Team in the discussion in #debian-qa,
the first of these points is a serious problem for the bookworm development
cycle and needs fixing. This bug is filed with serious severity in accordance
with the BTS definition of serious: "in the release manager's opinion, makes
the package unsuitable for release" [1].

  [1] https://www.debian.org/Bugs/Developer#severities

Classification tags not shown by default but will still pop up and for
a problem such as this may cause significant issues with bullseye→bookworm
upgrades, it's important to get right.

I'm filing this as a bug so that it doesn't accidentally get forgotten and
to keep this change out of testing.

regards
Stuart

Bug#980692: dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/html5shiv.min.js is missing

[Graham Inggs]

The entry below was dropped from debian/changelog and I think it's the
reason why the BTS thinks this bug is not fixed in 2021.08.1+dfsg-2 in
unstable.


dask (2021.01.0+dfsg-1) unstable; urgency=medium

  [ Diane Trout ]
  * New upstream release
  * Fix fake http proxy url as dask's build system parses it
  * Modify the documentation build process to use local files
- Cache copies of yaml files hosted at raw.githubusercontent.com/dask/
in debian/
- Add target to debian/rules to download the files
  * Update Standards-Version to 4.5.1. No changes needed.
  * Use Rules-Requires-Root: no
  * Update to debhelper-compat 13
  * Add python-asyncssh-doc as doc dependency
  * Add link to sphinx_rtd_theme html5shiv.min.js
  * Use Debian version of js-yaml
  * Refresh patches
  * Update use-local-intersphinx to use the local asyncssh docs
  * Remove pandas-1.1 compatibility patches, resolved upstream
  * Require a version of sparse that includes SparseArray

  [ Stefano Rivera ]
  * Patch: Use youtube-nocookie.com in docs.

 -- Diane Trout   Thu, 21 Jan 2021 19:51:01 -0800

Bug#993119: marked as done (src:hp-search-mac: fails to migrate to testing for too long: maintainer built arch:all)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 14:35:31 +
with message-id 
and subject line Bug#993119: fixed in hp-search-mac 0.1.5.1
has caused the Debian Bug report #993119,
regarding src:hp-search-mac: fails to migrate to testing for too long: 
maintainer built arch:all
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 ow...@bugs.debian.org
immediately.)


-- 
993119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hp-search-mac
Version: 0.1.4+nmu1
Severity: serious
Control: close -1 0.1.5
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:hp-search-mac
has been trying to migrate for 98 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=hp-search-mac




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: hp-search-mac
Source-Version: 0.1.5.1
Done: Ola Lundqvist 

We believe that the bug you reported is fixed in the latest version of
hp-search-mac, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ola Lundqvist  (supplier of updated hp-search-mac package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Sep 2021 13:10:31 +0100
Source: hp-search-mac
Architecture: source
Version: 0.1.5.1
Distribution: unstable
Urgency: medium
Maintainer: Ola Lundqvist 
Changed-By: Ola Lundqvist 
Closes: 993119
Changes:
 hp-search-mac (0.1.5.1) unstable; urgency=medium
 .
   * Source only upload. Closes: #993119.
Checksums-Sha1:
 ded1a69c006ea200b9b14aed31e3c7c4f4438a9b 1424 hp-search-mac_0.1.5.1.dsc
 287e7ab8fba769e516a4c097b614dc9fcd221d17 12712 hp-search-mac_0.1.5.1.tar.gz
 586b43bce08260e9887efcb76771e8bd9e305080 5699 
hp-search-mac_0.1.5.1_source.buildinfo
Checksums-Sha256:
 0588f81c0f24a2ec0a643eca5a1c064973be59c2db01fe91ce7ed56d9a14493a 1424 
hp-search-mac_0.1.5.1.dsc
 5d0408675bed90aa34db53fc4cc8bc6ec840fc7926a2a351fe7dd85c1a66572b 12712 
hp-search-mac_0.1.5.1.tar.gz
 c4aba5f711d610c8ae40be417701b820fc77baa436fe0c85fa8debc18d5e6dc6 5699 
hp-search-mac_0.1.5.1_source.buildinfo
Files:
 931b91409fb12d49b0c9663515f32b7d 1424 admin optional hp-search-mac_0.1.5.1.dsc
 be75b19c463b3209849c907c6ccf409a 12712 admin optional 
hp-search-mac_0.1.5.1.tar.gz
 1ae19935e7d5e652023ef4e1d4f01a5f 5699 admin optional 
hp-search-mac_0.1.5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEIvIyxrHg9L8rJgpqXpDc+pQmh28FAmE4mt4ACgkQXpDc+pQm
h2/arxAAkTeaQMq1J7ROQV0jad6VOARvUXWqreXL3aus91C/G9MLMA+d11nHhaWi

Bug#993176: libssh2 FTBFS: configure.ac:130: error: m4_undefine: undefined macro: backend

[Nicolas Mora]

Hello,

Le 2021-08-28 à 07 h 54, Helmut Grohne a écrit :


libssh2 fails to build from source. A build ends as follows:


I can reproduce that too, not sure why it fails now...

libssh2 version 1.10 builds successfully though, and I'm currently 
working on packaging libssh2 1.10 with openssl 3.0.
If that's ok with you I'll close this bug when version 1.10 will be 
uploaded to sid.


/Nicolas

Processed: Re: r-cran-ncdf4: ftbfs with autoconf 2.70

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #978891 [src:r-cran-ncdf4] r-cran-ncdf4: ftbfs with autoconf 2.70
Added tag(s) help.

-- 
978891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978891: r-cran-ncdf4: ftbfs with autoconf 2.70

[Andreas Tille]

Control: tags -1 help

Hi,

I need to admit that from my naive perspective this is a bug in
autoconf.  In the log that is provided in the bug report[1] you can see
this here:

   dh_autoreconf -O--buildsystem=R
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cd tools && ./regenerate
rm: cannot remove '../Makefile': No such file or directory
rm: cannot remove '../src/Makevars': No such file or directory
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.
configure.ac:44: warning: AC_OUTPUT should be used without arguments.
configure.ac:44: You should run autoupdate.


This results later in:


** using staged installation
configure.ac: starting
./configure: line 1764: syntax error near unexpected token `;;'
./configure: line 1764: ` as_dir=./ ;;'
ERROR: configuration failed for package ‘ncdf4’



I checked the resulting configure file and the part in question looks like:


echo "configure.ac: starting"

 as_dir=./ ;;
*/) ;;
*) as_dir=$as_dir/ ;;
  esac
for ac_exec_ext in '' $ac_executable_extensions; do
  if as_fn_executable_p "$as_dir$ac_word$ac_exec_ext"; then
ac_cv_prog_HAS_NC_CONFIG="yes"
printf "%s\n" "$as_me:${as_lineno-$LINENO}: found 
$as_dir$ac_word$ac_exec_ext" >&5
break 2
  fi
done


It looks like a case statement intended but not injected by autoconf.  I
have no idea how this can be influenced by some configure.ac statement.

Kind regards

   Andreas.

[1] https://bugs.debian.org/978891

-- 
http://fam-tille.de

Bug#988673: centreon-connectors: diff for NMU version 19.10.0-1.1

[Sébastien Delafond]

On 08/09 16:54, Adrian Bunk wrote:
> I've prepared an NMU for centreon-connectors (versioned as
> 19.10.0-1.1) and uploaded it to DELAYED/14. Please feel free to tell
> me if I should cancel it.

Hi Adrian,

thanks a lot for taking of this, it's really appreciated.

Cheers,

-- 
Seb

Processed: centreon-connectors: diff for NMU version 19.10.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 988673 + patch
Bug #988673 [src:centreon-connectors] centreon-connectors: FTBFS: Could not 
find libgcrypt's headers
Added tag(s) patch.
> tags 988673 + pending
Bug #988673 [src:centreon-connectors] centreon-connectors: FTBFS: Could not 
find libgcrypt's headers
Added tag(s) pending.

-- 
988673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#988673: centreon-connectors: diff for NMU version 19.10.0-1.1

[Adrian Bunk]

Control: tags 988673 + patch
Control: tags 988673 + pending

Dear maintainer,

I've prepared an NMU for centreon-connectors (versioned as 19.10.0-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.

cu
Adrian
diff -Nru centreon-connectors-19.10.0/debian/changelog centreon-connectors-19.10.0/debian/changelog
--- centreon-connectors-19.10.0/debian/changelog	2019-12-27 09:03:21.0 +0200
+++ centreon-connectors-19.10.0/debian/changelog	2021-09-08 15:18:03.0 +0300
@@ -1,3 +1,10 @@
+centreon-connectors (19.10.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Build depend on libgcrypt20-dev. (Closes: #988673)
+
+ -- Adrian Bunk   Wed, 08 Sep 2021 15:18:03 +0300
+
 centreon-connectors (19.10.0-1) unstable; urgency=medium
 
   * Add debian/watch
diff -Nru centreon-connectors-19.10.0/debian/control centreon-connectors-19.10.0/debian/control
--- centreon-connectors-19.10.0/debian/control	2019-12-27 09:03:21.0 +0200
+++ centreon-connectors-19.10.0/debian/control	2021-09-08 15:18:03.0 +0300
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Freexian Packaging Team 
 Uploaders: Sebastien Delafond 
-Build-Depends: debhelper (>= 11), cmake, libcentreon-clib, pkg-config, libssh2-1-dev, libperl-dev
+Build-Depends: debhelper (>= 11), cmake, libcentreon-clib, pkg-config, libssh2-1-dev, libperl-dev, libgcrypt20-dev
 Standards-Version: 4.4.1
 Homepage: https://github.com/centreon/centreon-connectors
 Vcs-Browser: https://salsa.debian.org/centreon-team/centreon-connectors

Bug#990081: marked as done (golang-uber-goleak: ftbfs with gccgo-go)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 13:38:31 +
with message-id 
and subject line Bug#990081: fixed in golang-uber-goleak 1.1.10-1
has caused the Debian Bug report #990081,
regarding golang-uber-goleak: ftbfs with gccgo-go
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 ow...@bugs.debian.org
immediately.)


-- 
990081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: golang-uber-goleak
Version: 1.1.0-2
Severity: serious

This package ftbfs when built with gccgo-go (build log attached)

diff --git a/debian/control b/debian/control
index 90d37eb..9d17b02 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Testsuite: autopkgtest-pkg-go
Priority: optional
Build-Depends: debhelper-compat (= 12),
   dh-golang,
- golang-any,
+ gccgo-go,
   golang-github-stretchr-testify-dev
Standards-Version: 4.5.1
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-uber-goleak


This causes build failure in bullseye-backports as gccgo-go is 
preferred over golang-go. Either the dependency should be changed to 
golang-go or the failure with gccgo-go should be fixed.


sbuild (Debian sbuild) 0.79.1 (22 April 2020) on mahishi

+==+
| golang-uber-goleak 1.1.0-2 (amd64)   Sat, 19 Jun 2021 19:26:08 + |
+==+

Package: golang-uber-goleak
Version: 1.1.0-2
Source Version: 1.1.0-2
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-20ebc20d-645c-44ee-b371-d75872567fe5'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/golang-uber-goleak-FU5ilk/resolver-VvoqLt' with '<>'

+--+
| Update chroot|
+--+

Get:1 http://deb.debian.org/debian unstable InRelease [161 kB]
Get:2 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:3 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[63.6 kB]
Get:4 http://deb.debian.org/debian unstable/main Sources 
T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [55.7 kB]
Get:4 http://deb.debian.org/debian unstable/main Sources 
T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [55.7 kB]
Get:5 http://deb.debian.org/debian unstable/main amd64 Packages 
T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [71.4 kB]
Get:5 http://deb.debian.org/debian unstable/main amd64 Packages 
T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [71.4 kB]
Fetched 415 kB in 5s (83.1 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were automatically installed and are no longer required:
  bsdextrautils fontconfig-config fonts-dejavu-core krb5-locales libbrotli1
  libbsd0 libc-devtools libdeflate0 libexpat1 libfontconfig1 libfreetype6
  libgd3 libjbig0 libjpeg62-turbo libmd0 libnss-nis libnss-nisplus libpng16-16
  libtiff5 libwebp6 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxpm4
  manpages manpages-dev sensible-utils ucf
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  auto-apt-proxy libhogweed6 libnettle8
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 600 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 libnettle8 amd64 3.7.3-1 
[270 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 libhogweed6 amd64 
3.7.3-1 [320 kB]
Get:3 http://deb.debian.org/debian unstable/main amd64 auto-apt-proxy all 13.3 
[9320 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 600 kB in 0s (1898 kB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 

Bug#993665: debianutils: tempfile still required in printer-driver-pnm2ppa

[Clint Adams]

On Wed, Sep 08, 2021 at 02:40:50PM +0200, Bill Allombert wrote:
> It will also break any local shell scripts the user systems might depend
> on that happens to use tempfile, for little or no benefit to the users.

They get the benefit of needing to switch to an alternative that
is supported upstream and present on more operaitng systems.

Processed: closing 978815

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 978815
Bug #978815 [src:fluxbox] fluxbox: ftbfs with autoconf 2.70
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: gudev-sharp-3.0 is not (yet) in unstable

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 981997 important
Bug #981997 [gudev-sharp-1.0] Conflicting monodoc-gudev-manual binary built 
also by Package: gudev-sharp-3.0
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
981997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 991450 is forwarded to https://github.com/greatscottgadgets/ubertooth/pull/446

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 991450 https://github.com/greatscottgadgets/ubertooth/pull/446
Bug #991450 [src:ubertooth] gcc-arm-none-eabi breaks ubertooth autopkgtest: 
linking error
Set Bug forwarded-to-address to 
'https://github.com/greatscottgadgets/ubertooth/pull/446'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
991450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993722: FTBFS: tempfile: not found

[Bill Allombert]

On Sun, Sep 05, 2021 at 04:34:08PM +0200, Samuel Thibault wrote:
> Package: gap
> Version: 4.11.0-4
> Severity: serious
> Justification: FTBFS
> 
> Hello,
> 
> gap currently FTBFS in unstable because tempfile was removed from
> debianutils. You can probably use mktemp instead.

Thanks for reporting this bug and tell me about this removal!

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#993665: debianutils: tempfile still required in printer-driver-pnm2ppa

[Bill Allombert]

On Sat, Sep 04, 2021 at 10:41:37PM +0900, Norbert Preining wrote:
> Package: debianutils
> Version: 5.4-3
> Severity: critical
> Justification: breaks unrelated software
> 
> The tempfile saga is not over. It might be wise grepping through the
> maintainer scripts of all packages.
> 
> printer-driver-pnm2ppa still requires it.

It will also break any local shell scripts the user systems might depend
on that happens to use tempfile, for little or no benefit to the users.

Cheers,
Bill.

Bug#993885: marked as done (upgrade failures)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 12:19:01 +
with message-id 
and subject line Bug#993885: fixed in nfs-utils 1:2.5.4-1~exp3
has caused the Debian Bug report #993885,
regarding upgrade failures
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 ow...@bugs.debian.org
immediately.)


-- 
993885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: nfs-utils
Version: 1:2.5.4-1~exp2
Severity: serious

Hi Anibal

thanks for the previous upload, however, the upgrade of nfs-common from 
sid to experimental still fails:


---snip---
[...]
Get:2 http://debian.ethz.ch/debian experimental/main amd64 libnfsidmap1 
amd64 1:2.5.4-1~exp2 [78.4 kB]
Get:3 http://debian.ethz.ch/debian sid/main amd64 libevent-core-2.1-7 
amd64 2.1.12-stable-1 [139 kB]

Fetched 523 kB in 0s (3464 kB/s)
(Reading database ... 21068 files and directories currently installed.)
Preparing to unpack .../nfs-common_1%3a2.5.4-1~exp2_amd64.deb ...
Unpacking nfs-common (1:2.5.4-1~exp2) over (1:1.3.4-6) ...
dpkg: error processing archive 
/var/cache/apt/archives/nfs-common_1%3a2.5.4-1~exp2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man5/idmapd.conf.5.gz', which is 
also in package libnfsidmap2:amd64 0.25-6

Running in chroot, ignoring request.
All runlevel operations denied by policy
invoke-rc.d: policy-rc.d denied execution of restart.
Errors were encountered while processing:
 /var/cache/apt/archives/nfs-common_1%3a2.5.4-1~exp2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
---snap---

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:2.5.4-1~exp3
Done: Anibal Monsalve Salazar 

We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anibal Monsalve Salazar  (supplier of updated nfs-utils 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Sep 2021 21:27:04 +1000
Source: nfs-utils
Architecture: source
Version: 1:2.5.4-1~exp3
Distribution: experimental
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Anibal Monsalve Salazar 
Closes: 993885
Changes:
 nfs-utils (1:2.5.4-1~exp3) experimental; urgency=medium
 .
   * Fix upgrade failure
 Put idmapd.conf.5 in debian/libnfsidmap1.manpages
 Closes: #993885
Checksums-Sha1:
 97e016f1ab436dd5dd25a04cc79df73afc2edcbc 2430 nfs-utils_2.5.4-1~exp3.dsc
 a57ff47f3304cbfdab78304b1b10e49d41406345 52236 
nfs-utils_2.5.4-1~exp3.debian.tar.xz
 283bc7d9221ce9555d8650447d393a6678192c4b 8924 
nfs-utils_2.5.4-1~exp3_amd64.buildinfo
Checksums-Sha256:
 1c0fcd7684f982e9a4cccd661c512c7dcd41efde06343e4f73bc868907390b3a 2430 
nfs-utils_2.5.4-1~exp3.dsc
 6ad482afd511ab6985714de12a9205b44fd4332ebb51e21d144b1a3edccf033b 52236 
nfs-utils_2.5.4-1~exp3.debian.tar.xz
 58cd0c7a560c8afe8619d3dde82c65c71e12e8c4a0248f5fcf1c19f547abe8a5 8924 
nfs-utils_2.5.4-1~exp3_amd64.buildinfo
Files:
 61a05e52664bbdcf73f26ce5c92aa199 2430 net optional nfs-utils_2.5.4-1~exp3.dsc
 574bfa0efb215e69384d0abe42c86a38 52236 net optional 
nfs-utils_2.5.4-1~exp3.debian.tar.xz
 7b6621cee4a69a1d7d3e1c6a733bfb6c 8924 net optional 
nfs-utils_2.5.4-1~exp3_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJhOKZBAAoJEHxWrP6UeJfYtiEP/1RHqu6th9747FfV9TmNZp8C
JCT4ZUOi2RODQGWjYkBy63Dt6DgMjfVtdlUSO9uLXK092w5qUqSpZZqVu7cr3WF9
PJgAT7A1E7s/DmxQUJKJ9OK8b8Dt6sSFTpV0nyITKQXlDVHzu1sm3ALJAzA7kQAj
CUrUaKrtCbRp32vjNdFg28hB15+1WHc6lpEp07h2UGRZA46TYL4r0PlL4h/6SyLk
YxB34gwZ8duT5qANQRPs8EEw86DWzQkaR7PGI3qvmOWSsTgPwkwlCP9B2wd/wvd6
itAXoGPUUr4Ajg1Ie768JROOZbW2l+Vzz6LAuiNXY0vXxIIiiumfyTRG6c3m+Etm
RkOSmb2B9yOSFrsxanguZmlqDRji8IJN8JAUe/Ybc1hiNa8rfn01ph6W8+sRkIBe
tZPPJfqBiu/jKdnzUiYjqLRhZYmLMnDkpsaq1Ph4Cof31ooC9njGgzrUlm7nmPYl
qsKEZRkv3hON6xJyxTZE52b7Jj1waP8/773RBngeKqw4EMFaKQPZ//e9Isrzr+6y
xJG33+PMlyeCsZbqOaOzvia+VoK2/lVufZdXgwk9EfAaWct2mYO0yvDLnbeaAP/P
Lb7XpHvIOO8G5h5U7NDnywPN7iRrFtsUYaPFeFs11iyfCSCOFIT7awHONXA7I4XN
qAhAutFySlh93V9WNwM2
=nw07
-END PGP SIGNATURE End Message ---

Bug#978833: gwyddion: ftbfs with autoconf 2.70

[Adrian Bunk]

On Thu, Dec 31, 2020 at 02:27:46PM +, Matthias Klose wrote:
>...
> Can't exec "gtkdocize": No such file or directory at 
> /usr/share/autoconf/Autom4te/FileUtils.pm line 293.
>...

Adding gtk-doc-tools to the build dependencies fixes the build.

cu
Adrian

Bug#993946: fakechroot: adduser fails with glibc 2.32

[Johannes Schauer Marin Rodrigues]

Package: fakechroot
Version: 2.19-3.4
Severity: grave
Justification: renders package unusable

Hi,

since the upload of glibc 2.32 to unstable, adduser under fakechroot
fails because it is not wrapping some library call and thus read the
system's /etc/passwd instead of the chroot's.

Some bits from strace output:

$ adduser --force-badname --system --home /nonexistent --no-create-home _apt
[...]
[pid 2353931] openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
[pid 2353931] fstat(3, {st_mode=S_IFREG|0644, st_size=2902, ...}) = 0
[pid 2353931] lseek(3, 0, SEEK_SET) = 0
[pid 2353931] read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 2902
[pid 2353931] close(3)  = 0
[pid 2353931] openat(AT_FDCWD, "/etc/shadow", O_RDONLY|O_CLOEXEC) = -1 EACCES 
(Permission denied)
[pid 2353931] openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
[pid 2353931] fstat(3, {st_mode=S_IFREG|0644, st_size=2902, ...}) = 0
[pid 2353931] lseek(3, 0, SEEK_SET) = 0
[pid 2353931] read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 2902
[pid 2353931] close(3)  = 0
[pid 2353931] write(1, "The system user `_apt' already e"..., 48The system user 
`_apt' already exists. Exiting.
) = 48

This means that one cannot anymore create a chroot with apt using
fakechroot. Thus marking this bug as RC.

Thanks!

cheers, josch

Bug#978776: buzztrax: diff for NMU version 0.10.2-7.1

[Adrian Bunk]

Control: tags 978776 + patch
Control: tags 978776 + pending

Dear maintainer,

I've prepared an NMU for buzztrax (versioned as 0.10.2-7.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.

cu
Adrian
diff -Nru buzztrax-0.10.2/debian/changelog buzztrax-0.10.2/debian/changelog
--- buzztrax-0.10.2/debian/changelog	2020-04-17 16:24:58.0 +0300
+++ buzztrax-0.10.2/debian/changelog	2021-09-08 14:47:10.0 +0300
@@ -1,3 +1,10 @@
+buzztrax (0.10.2-7.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Build depend on gtk-doc-tools. (Closes: #978776)
+
+ -- Adrian Bunk   Wed, 08 Sep 2021 14:47:10 +0300
+
 buzztrax (0.10.2-7) unstable; urgency=medium
 
   [ Peter Michael Green ]
diff -Nru buzztrax-0.10.2/debian/control buzztrax-0.10.2/debian/control
--- buzztrax-0.10.2/debian/control	2020-04-17 16:24:58.0 +0300
+++ buzztrax-0.10.2/debian/control	2021-09-08 14:47:10.0 +0300
@@ -11,6 +11,7 @@
 libtool,
 gettext,
 intltool,
+gtk-doc-tools,
 pkg-config,
 libglib2.0-dev (>= 2.32.0),
 libgtk-3-dev (>= 3.4),

Processed: tagging 978833

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 978833 + ftbfs
Bug #978833 [src:gwyddion] gwyddion: ftbfs with autoconf 2.70
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: buzztrax: diff for NMU version 0.10.2-7.1

[Debian Bug Tracking System]

Processing control commands:

> tags 978776 + patch
Bug #978776 [src:buzztrax] buzztrax: ftbfs with autoconf 2.70
Added tag(s) patch.
> tags 978776 + pending
Bug #978776 [src:buzztrax] buzztrax: ftbfs with autoconf 2.70
Added tag(s) pending.

-- 
978776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 979973 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 979973 important
Bug #979973 [libpam-yubico] libpam-yubico does not use multiarch paths
Bug #990412 [libpam-yubico] libpam-yubico does not use multiarch paths
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
979973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979973
990412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 978822

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 978822 + ftbfs
Bug #978822 [src:gopher] gopher: ftbfs with autoconf 2.70
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: transition: evolution-data-server

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 992870
Bug #993945 [release.debian.org] transition: evolution-data-server
993945 was not blocked by any bugs.
993945 was not blocking any bugs.
Added blocking bug(s) of 993945: 992870
> block -1 by 993934
Bug #993945 [release.debian.org] transition: evolution-data-server
993945 was blocked by: 992870
993945 was not blocking any bugs.
Added blocking bug(s) of 993945: 993934
> block 991036 by -1
Bug #991036 [src:libhandy] libhandy: Should this package be removed in bookworm?
991036 was blocked by: 993852 993849 993853 993850
991036 was not blocking any bugs.
Added blocking bug(s) of 991036: 993945
> block 993850 by -1
Bug #993850 [src:gnome-calendar] gnome-calendar: Depends on deprecated libhandy 
version 0
993850 was not blocked by any bugs.
993850 was blocking: 991036
Added blocking bug(s) of 993850: 993945

-- 
991036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991036
993850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993850
993945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 978913

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 978913 + ftbfs
Bug #978913 [src:uisp] uisp: ftbfs with autoconf 2.70
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 978840

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 978840 + ftbfs
Bug #978840 [src:java2html] java2html: ftbfs with autoconf 2.70
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 978891

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 978891 + ftbfs
Bug #978891 [src:r-cran-ncdf4] r-cran-ncdf4: ftbfs with autoconf 2.70
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 978813 is forwarded to https://github.com/emcrisostomo/fswatch/commit/c662b50ad25db990cc44b3fb03a7194ea81d6304

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 978813 
> https://github.com/emcrisostomo/fswatch/commit/c662b50ad25db990cc44b3fb03a7194ea81d6304
Bug #978813 [src:fswatch] fswatch: ftbfs with autoconf 2.70
Set Bug forwarded-to-address to 
'https://github.com/emcrisostomo/fswatch/commit/c662b50ad25db990cc44b3fb03a7194ea81d6304'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#981496: svtools: ship with bullseye?

[Adrian Bunk]

On Sun, Jan 31, 2021 at 10:35:45PM +0100, Chris Hofstaedtler wrote:
> Package: svtools
> Version: 0.6-4
> Severity: important
> 
> Hi,
> 
> the package "svtools" has been orphaned by its original maintainer
> over 7 years ago. The Debian maintainer was also the upstream
> maintainer. Upstream has archived the project, and the last change
> was over 9 years ago.
> 
> Is this still useful software? Should we continue to ship it?
> 
> If you are interested, please speak up now.
>...

Jan, you intend to addopt daemontools.

Can you check whether svtools is still useful for Debian
(and if yes, ideally also adopt it)?

> Chris

Thanks
Adrian

Processed: bug 978882 is forwarded to https://git.lysator.liu.se/pikelang/pike/-/issues/10062

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 978882 https://git.lysator.liu.se/pikelang/pike/-/issues/10062
Bug #978882 [src:pike8.0] pike8.0: ftbfs with autoconf 2.70
Set Bug forwarded-to-address to 
'https://git.lysator.liu.se/pikelang/pike/-/issues/10062'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 978769 in 1:3.0.8.2-6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 978769 1:3.0.8.2-6
Bug #978769 [src:argus-clients] argus-clients: ftbfs with autoconf 2.70
Marked as found in versions argus-clients/1:3.0.8.2-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969240: playonlinux: please switch away from netcat

[Adrian Bunk]

Control: severity -1 important

On Fri, Aug 20, 2021 at 01:52:37PM +0200, Chris Hofstaedtler wrote:
> Control: severity -1 serious
> 
> * Chris Hofstaedtler  [210820 11:49]:
> > playonlinux Depends on netcat. This is a transitional package on
> > netcat-openbsd, and the transitional package should go away sooner
> > than later, preferably in bullseye.
> 
> The transitional "netcat" package is now gone in bookworm.
> Your package is therefore now uninstallable.

This is not true due to both netcat-openbsd and netcat-traditional
providing netcat.

The dependency should be improved to either
  netcat-openbsd
or
  netcat-openbsd | netcat
but (assuming the package works with netcat-traditional) this is not
an RC bug.

> Chris

cu
Adrian

Processed: Re: Bug#969240: playonlinux: please switch away from netcat

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #969240 [src:playonlinux] playonlinux: please switch away from netcat
Severity set to 'important' from 'serious'

-- 
969240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 978830 is forwarded to https://github.com/tristanheaven/gtkhash/commit/1f7e774f514e4822384db6f8a47914b408189c9e

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 978830 
> https://github.com/tristanheaven/gtkhash/commit/1f7e774f514e4822384db6f8a47914b408189c9e
Bug #978830 [src:gtkhash] gtkhash: ftbfs with autoconf 2.70
Set Bug forwarded-to-address to 
'https://github.com/tristanheaven/gtkhash/commit/1f7e774f514e4822384db6f8a47914b408189c9e'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993631: cfgrib FTBFS: test failures

[Adrian Bunk]

On Fri, Sep 03, 2021 at 10:02:07PM +0100, Alastair McKinstry wrote:
> This is a bug in python3-eccodes which now depends on ecmwflibs.
> Ecmwflibs in now in the NEW queue
>...

Seems the current workaround was not sufficient?
https://buildd.debian.org/status/fetch.php?pkg=cfgrib=amd64=0.9.9.0-1=1631098007=0

cu
Adrian

Bug#992527: node-gdal

[Momtchil Momtchev]

I suggest you switch to node-gdal-async (gdal-async on npm), the only 
version currently under active development. I fixed this bug a few 
months ago.



--
Momtchil Momtchev 

Bug#993631: marked as done (cfgrib FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 10:05:02 +
with message-id 
and subject line Bug#993631: fixed in eccodes-python 2:1.3.4-2
has caused the Debian Bug report #993631,
regarding cfgrib FTBFS: test failures
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 ow...@bugs.debian.org
immediately.)


-- 
993631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfgrib
Version: 0.9.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cfgrib=0.9.9.0-1

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
for p in python3.9; do \
PY3VERNUM=`echo $p | sed -e 's/python//' `; \
pybuild --test --test-pytest -i $p -p $PY3VERNUM  ;  \
done
I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_cfgrib/build; 
python3.9 -m pytest tests
= test session starts ==
platform linux -- Python 3.9.7, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /<>, configfile: pyproject.toml
collected 6 items / 9 errors / 2 skipped

 ERRORS 
__ ERROR collecting .pybuild/cpython3_3.9_cfgrib/build/tests/test_20_main.py ___
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_cfgrib/build/tests/test_20_main.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/gribapi/bindings.py:28: in 
import ecmwflibs as findlibs
E   ModuleNotFoundError: No module named 'ecmwflibs'

During handling of the above exception, another exception occurred:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_20_main.py:3: in 
from cfgrib import __main__
cfgrib/__init__.py:19: in 
from .cfmessage import CfMessage
cfgrib/cfmessage.py:29: in 
from . import messages
cfgrib/messages.py:28: in 
import eccodes  # type: ignore
/usr/lib/python3/dist-packages/eccodes/__init__.py:13: in 
from .eccodes import *  # noqa
/usr/lib/python3/dist-packages/eccodes/eccodes.py:12: in 
from gribapi import (
/usr/lib/python3/dist-packages/gribapi/__init__.py:13: in 
from .gribapi import *  # noqa
/usr/lib/python3/dist-packages/gribapi/gribapi.py:34: in 
from . import errors
/usr/lib/python3/dist-packages/gribapi/errors.py:16: in 
from .bindings import ENC, ffi, lib
/usr/lib/python3/dist-packages/gribapi/bindings.py:30: in 
import findlibs
E   ModuleNotFoundError: No module named 'findlibs'
...
=== short test summary info 
ERROR tests/test_20_main.py
ERROR tests/test_20_messages.py
ERROR tests/test_25_cfmessage.py
ERROR tests/test_30_dataset.py
ERROR tests/test_40_xarray_store.py
ERROR tests/test_40_xarray_to_grib_regular_ll.py
ERROR tests/test_50_datamodels.py
ERROR tests/test_50_sample_data.py
ERROR tests/test_50_xarray_getitem.py
!!! Interrupted: 9 errors during collection 
= 2 skipped, 9 errors in 1.97s =
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.9_cfgrib/build; python3.9 -m pytest tests
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 13



(m68k builds with nocheck)
--- End Message ---
--- Begin Message ---
Source: eccodes-python
Source-Version: 2:1.3.4-2
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
eccodes-python, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated eccodes-python 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Sep 2021 10:23:11 +0100
Source: eccodes-python
Architecture: source
Version: 2:1.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 993631
Changes:
 eccodes-python (2:1.3.4-2) unstable; urgency=medium
 .
   * 

Processed: tagging 992527, bug 992527 is forwarded to https://github.com/contra/node-gdal-next/issues/54

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 992527 + upstream
Bug #992527 [src:node-srs] node-srs: FTBFS with GDAL 3.3.1
Added tag(s) upstream.
> forwarded 992527 https://github.com/contra/node-gdal-next/issues/54
Bug #992527 [src:node-srs] node-srs: FTBFS with GDAL 3.3.1
Set Bug forwarded-to-address to 
'https://github.com/contra/node-gdal-next/issues/54'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
992527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993935: debian-edu-ltsp-install: Netboot image exposes private data and crypto keys

[Dominik George]

Package: debian-edu-config
Version: 2.11.56
Severity: critical
Tags: security
Justification: root security hole
X-Debbugs-Cc: Debian Security Team 

The LTSP netboot image produced by debian-edu-ltsp-install includes full copies
of files that should never leave the Debian Edu main server, if run on a 
so-called
"combined server" (a system using the Main Server and Terminal Server profiles,
as done in small installations).

Among these files are full copies of, among others:

 - /var/lib/ldap, containing the full, unencrypted LDAP database with all
   private information on all users, password hashes, and Kerberos keys
 - /etc/krb5-kdc, containing information on decrypting Kerberos data in the
   LDAP database
 - /etc/gosa, containing the (encrypted) LDAP manager credentials, plus the
   key to decrypt it

Any user with access to the local terminal server network can acquire the 
netboot
image, unauthenticated, and extract the listed information from it.

The issue is caused by the new LTSP system using the LTSP PnP system now in all
cases, thus packing the entire mai nserver filesystem in squashfs image. The
debian-edu-ltsp-install script produces a list of files to exclude from the 
image,
which is not sufficient, most probably because it was tailored to the use case 
where
the image is produced from a dedicated Terminal Server instead of a combined 
server.

IMHO, the use case of the combined server cannot be fixed. The new LTSP system 
de facto
disallows any use of a combiend server – even if we make a very carefully 
curated list
of excluded files, any administrator would have to take care to add their own 
excludes
for just about any file they place on the main server that was not palced there 
by the
Debian Edu software. In fact, the whole new LTSP system seems unfit to be used 
on any
server that is not limited to producing LTSP images, and supporting netbooting 
them.

For now, the issue should be mitigated by carefully adding all relevant paths 
that
are known to exist only on the main server to the exclude list, but I do not 
think
that is a viable fix in the long term.

Bug#993923: macaulay2: FTBFS on s390x: error: installPackage: 1 error(s) occurred running examples for package SparseResultants

[Torrance, Douglas]

Control: forwarded -1 https://github.com/Macaulay2/M2/issues/2162
Control: tags -1 pending

On Wed 08 Sep 2021 04:42:51 AM EDT, Sebastian Ramacher  
wrote:

| ../../m2/debugging.m2:20:6:(1):[9]: error: installPackage: 1 error(s) 
occurred running examples for package SparseResultants:
|
| _char_lp__Sparse__Resultant_rp.errors
| *
| -- -*- M2-comint -*- hash: 829653806
|
| i1 : R = denseResultant(2,2,1,CoefficientRing=>ZZ/331);
| Killed


Thanks for the report!  This has been reported upstream and there's a
(band-aid) fix in git for the next upload.


signature.asc
Description: PGP signature

Processed: Re: Bug#993923: macaulay2: FTBFS on s390x: error: installPackage: 1 error(s) occurred running examples for package SparseResultants

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/Macaulay2/M2/issues/2162
Bug #993923 [src:macaulay2] macaulay2: FTBFS on s390x: error: installPackage: 1 
error(s) occurred running examples for package SparseResultants
Set Bug forwarded-to-address to 'https://github.com/Macaulay2/M2/issues/2162'.
> tags -1 pending
Bug #993923 [src:macaulay2] macaulay2: FTBFS on s390x: error: installPackage: 1 
error(s) occurred running examples for package SparseResultants
Added tag(s) pending.

-- 
993923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993843: Processed: tagging 993843

[Vincent Lefevre]

On 2021-09-08 07:48:03 +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > tags 993843 + sid bookworm
> Bug #993843 [zsh-static] zsh-static segfaults immediately
> Added tag(s) sid and bookworm.

Note that while zsh-static is currently fine in bullseye, problems
might occur if some glibc security update needs to modify internals
concerning libnss.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#993333: marked as done (weechat: FTBFS: Target "irc" links to item " use `command -v' in scripts instead)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 09:41:55 +
with message-id 
and subject line Bug#99: fixed in weechat 3.2.1-1
has caused the Debian Bug report #99,
regarding weechat: FTBFS: Target "irc" links to item " use `command -v' in 
scripts instead
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 ow...@bugs.debian.org
immediately.)


-- 
99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: weechat
Version: 3.0.1-1
Severity: serious
Tags: ftbfs sid bookworm

This package fails to build from source on current sid.

It looks like this regressed with the recent change in debianutils
that made /usr/bin/which output a deprecation warning.

>From a build log:

   -- Found GCRYPT: /usr/bin/which: this version of `which' is deprecated; use 
`command -v' in scripts instead.
   -L/usr/lib/x86_64-linux-gnu -lgcrypt  
   
   [...]
   
   CMake Error at src/plugins/irc/CMakeLists.txt:20 (add_library):
 Target "irc" links to item " use `command -v' in scripts instead.
   
 -L/usr/lib/x86_64-linux-gnu -lgcrypt" which has leading or trailing
 whitespace.  This is now an error according to policy CMP0004.

A full log is available at

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/weechat.html

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: weechat
Source-Version: 3.2.1-1
Done: Emmanuel Bouthenot 

We believe that the bug you reported is fixed in the latest version of
weechat, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bouthenot  (supplier of updated weechat package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Sep 2021 20:25:39 +
Source: weechat
Architecture: source
Version: 3.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Emmanuel Bouthenot 
Changed-By: Emmanuel Bouthenot 
Closes: 99 993803
Changes:
 weechat (3.2.1-1) unstable; urgency=medium
 .
   * New upstream release
 - fix CVE-2021-40516: possible denial of service (crash) via a crafted
 WebSocket in relay plugin (Closes: #993803)
   * Add a patch to fix a FTBFS (related to recent changes on which command
 output) (Closes: #99)
   * Bump Standards-Version to 4.6.0.1
   * Remove useless HomePage field in upstream/metadata
Checksums-Sha1:
 9dd2a7ddabe02865c11abb881b63b510ad57d2b0 3100 weechat_3.2.1-1.dsc
 28f4f99461120442bf805b26baae70c91984c191 2261348 weechat_3.2.1.orig.tar.xz
 d0959910090f6fe7ffba714e39ff052448ef0f6d 833 weechat_3.2.1.orig.tar.xz.asc
 f5e7ed792bd78d9dbc9f950f0246dd74fbcbfcd3 18396 weechat_3.2.1-1.debian.tar.xz
 2ed988b7504772787364a5228c1b966b1ba0815e 9595 weechat_3.2.1-1_source.buildinfo
Checksums-Sha256:
 ab61da68d3c296acdff89dbd691b0878fef50da3518a4c74ab6a6b2489f799b8 3100 
weechat_3.2.1-1.dsc
 2bb3a708e006f2d22df9e813f3567569178f30ba4082fd8fb06ca0f6f4d1613f 2261348 
weechat_3.2.1.orig.tar.xz
 0201b7972d157f7bd30651adce0e91cbd8580b5f90597aba5c4978b9c85ff287 833 
weechat_3.2.1.orig.tar.xz.asc
 b872e745abd6df95d233e157ea52d9209d89609adfee18ec8323c9e32fbe034c 18396 
weechat_3.2.1-1.debian.tar.xz
 c9ca24872c02245acd4ef8e1b393e8f4ca85206a618ac71b7a2205fe46559f60 9595 
weechat_3.2.1-1_source.buildinfo
Files:
 cea75f3b51350f0cb29ddc236277a16f 3100 net optional weechat_3.2.1-1.dsc
 c66814bd841bf26fd8b0625b1cc46daa 2261348 net optional weechat_3.2.1.orig.tar.xz
 5927b76dc3df17b417d6b14ac49cc3e9 833 net optional weechat_3.2.1.orig.tar.xz.asc
 35c7a0aa7d08d1a1fda7ca8d568dd7a7 18396 net optional 
weechat_3.2.1-1.debian.tar.xz
 5691ea59ef795379a3d6638d7f01171c 9595 net optional 
weechat_3.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQ1Tfow3vJnf8QuHSwd3I5KdQsMFAmE4b8QACgkQSwd3I5Kd
QsMZ2BAAh7vquHqxAAI6QdEgjJ+LPHHZxr/SOKcXmbPxbFgt33v+9qWrlZebVpxh
d3MNULcEDOL+uVw8LMEguYhl6Z4KL+t9wmA5olgcLI5qv7oHp1SmFZqwsCofIkpX
Zt8Qk/tKB0p2L/byRSo3R0EU8bkmgTrrTe9mJ9+ZsfYDcClInK5ylMdKUEzFCbhX
+1WilFoyiwGbMQ3m/sDVwqoboMrUblH1g5ejJi0+Y1d/bY1ShKR58ay/XIvggCG6
gZisvfA19urx5cvsHTv8OtUeKygdxvzNQ9yk5eVqFfsOoo3L1N74iDQKuNqYgUm4

Processed: found 993701 in 18.06.1+ds.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 993701 18.06.1+ds.1-1
Bug #993701 [src:srslte] srslte: FTBFS with libsoapysdr 0.8
Marked as found in versions srslte/18.06.1+ds.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
993701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993870: marked as done (guesoglc FTBFS: make[2]: *** No rule to make target '../src/glew.c', needed by 'libGLC_la-glew.lo'. Stop.)

[Debian Bug Tracking System]

Your message dated Wed, 08 Sep 2021 09:10:35 +
with message-id 
and subject line Bug#993870: fixed in quesoglc 0.7.2-7
has caused the Debian Bug report #993870,
regarding guesoglc FTBFS: make[2]: *** No rule to make target '../src/glew.c', 
needed by 'libGLC_la-glew.lo'.  Stop.
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 ow...@bugs.debian.org
immediately.)


-- 
993870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quesoglc
Version: 0.7.2-6
Severity: serious
Tags: ftbfs

quesoglc fails to build from source in unstable. A non-parallel build
ends as follows:

| make[2]: *** No rule to make target '../src/glew.c', needed by 
'libGLC_la-glew.lo'.  Stop.
| make[2]: Leaving directory '/<>/build'
| make[1]: *** [Makefile:555: all-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:4: build-arch] Error 25
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: quesoglc
Source-Version: 0.7.2-7
Done: Paul Wise 

We believe that the bug you reported is fixed in the latest version of
quesoglc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated quesoglc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Sep 2021 16:43:15 +0800
Source: quesoglc
Architecture: source
Version: 0.7.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Paul Wise 
Closes: 993870
Changes:
 quesoglc (0.7.2-7) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
 + libglc-dev, libglc0: Add Multi-Arch: same.
 .
   [ Paul Wise ]
   * Work around breakage after autoconf upgrade (Closes: #993870)
   * Update watch file format version to 4.
   * Bump debhelper from deprecated 9 to 13.
 + debian/rules: Drop --fail-missing argument, now the default.
   * Set debhelper-compat version in Build-Depends.
   * Drop unnecessary dependency on dh-autoreconf.
   * Fix field name typo in debian/copyright (Licence => License).
   * Drop unnecessary dh arguments: --parallel
Checksums-Sha1:
 060287f9f5efe5769d52046ee9af2ed5542e4dd1 2129 quesoglc_0.7.2-7.dsc
 4d7615828f06adf5581e1115ed0bfe8679e67daa 24896 quesoglc_0.7.2-7.debian.tar.xz
Checksums-Sha256:
 a3dde2e25f0c836456b8720ce54484233891a214697081f495ae4943a6e18cbb 2129 
quesoglc_0.7.2-7.dsc
 caa108fcf4d9fbf19fd167333b8faedb44f919d1886cd910631782ed5b78d687 24896 
quesoglc_0.7.2-7.debian.tar.xz
Files:
 5c86ae83cfd6567c5006de200329e95b 2129 devel optional quesoglc_0.7.2-7.dsc
 bb67cd3951ed2a704093ea26282fd875 24896 devel optional 
quesoglc_0.7.2-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmE4ePEACgkQMRa6Xp/6
aaP8WA/+LGfLd/yYkX9knuNTWIosNylSLQeuLvmoffCBC6nXm9Nc6npGq/uZh/rm
StSHkGzJWfwQTusKPRtFYjxzYODf2Ae/lZsES0EeSPUyN0PdPn1LKBX+H9Yok3ZE
5RSMafLZ8XG8U2uXpercoG9z/uTMT4QAA429kZiVnKQ0Bb3+OoWEvoxSJxyBkz1o
X4pXvJ22i3AM00XpabR7u35nzchTRb7SrM+LuSkgpMZ9pV0p5iS+y2Mo64VK6dhL
vg80zQam9wX9d5obI7IcMLWRU479blq2PRHIHdgG3TNqpbTaBUUBrWZGM0jIYbz3
9CpMRX+2PiafD9Wu2lAoI/SXKi1arR/p030EM1TwskZPytHbODr0S7wlpn9hJKV+
XiSmLmdSBqGTghwzWHWIkCFRtfmZClZ0FviZD4xdtR7HNH7tG1xd2+dPzV4bgF7p
WrB8p9ZPnR4zTMg0scp8mH+EnPHVsDSNWs8lHSH0qFlXaw3QG9v8eshocTN6t6P8
x8/65hpMsvi+7YwMuPZO9Zf79BnzfiTuxtUG/VUki9cfhByeO+ewxKm2HApX8FM3
NxxPmgrBypWu4+tgYfZZXnrV2XbhMSOoOw1JhJqi/Gx1blveYKEMTbCBn+vp3xKl
IHFeEO0NCROG1Sx+bosuc/OwemCPxhuj/5ix59uI1SrKlOau1og=
=5oIc
-END PGP SIGNATURE End Message ---

Processed: Bug#993870 marked as pending in quesoglc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993870 [src:quesoglc] guesoglc FTBFS: make[2]: *** No rule to make target 
'../src/glew.c', needed by 'libGLC_la-glew.lo'.  Stop.
Added tag(s) pending.

-- 
993870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993870: marked as pending in quesoglc

[Paul Wise]

Control: tag -1 pending

Hello,

Bug #993870 in quesoglc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/games-team/quesoglc/-/commit/08d8aa2c374debae4306eea2921b4978568a9bf8


Work around breakage after autoconf upgrade (Closes: #993870)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993870

Bug#993923: macaulay2: FTBFS on s390x: error: installPackage: 1 error(s) occurred running examples for package SparseResultants

[Sebastian Ramacher]

Source: macaulay2
Version: 1.18+ds-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

|  -- making example results for "char(SparseResultant)"  
|  ulimit -c unlimited; ulimit -t 700; ulimit -m 85; ulimit -s 8192; ulimit 
-n 512;  cd /tmp/M2-4013178-0/26-rundir/; GC_MAXIMUM_HEAP_SIZE=400M 
"/<>/M2/usr-dist/s390x-Linux-Debian-buildd-unstable/bin/M2-binary" 
-q --int --no-randomize --no-readline --silent --stop --print-width 77 -e 
'needsPackage("SparseResultants",Reload=>true,FileName=>"/<>/M2/Macaulay2/packages/SparseResultants.m2")'
 <"/tmp/M2-4013178-0/0_char_lp__Sparse__Resultant_rp.m2" 
>>"/<>/M2/usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_char_lp__Sparse__Resultant_rp.errors"
 2>&1
| 
/<>/M2/usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_char_lp__Sparse__Resultant_rp.errors:0:1:
 (output file) error: Macaulay2 killed by signal 9
| /tmp/M2-4013178-0/0_char_lp__Sparse__Resultant_rp.m2:0:1: (input file)
| M2: *** Error 9
|  -- 4498.18 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_char_lp__Sparse__Resultant_rp.out
|  -- warning: missing file 
/<>/M2/usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_char_lp__Sparse__Resultant_rp.out
|  -- making example results for "char(SparseDiscriminant)"
-- 0.87047 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_char_lp__Sparse__Discriminant_rp.out
|  -- making example results for "permute" 
-- 0.559575 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_permute.out
|  -- making example results for "MultidimensionalMatrix * 
MultidimensionalMatrix" -- 0.469042 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/___Multidimensional__Matrix_sp_st_sp__Multidimensional__Matrix.out
|  -- making example results for "entries(MultidimensionalMatrix)" 
-- 0.435753 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_entries_lp__Multidimensional__Matrix_rp.out
|  -- making example results for "SparseResultant Thing"   
-- 0.438942 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/___Sparse__Resultant_sp__Thing.out
|  -- making example results for "genericSkewMultidimensionalMatrix"   
-- 0.916326 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_generic__Skew__Multidimensional__Matrix.out
|  -- making example results for "randomMultidimensionalMatrix"
-- 0.37824 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_random__Multidimensional__Matrix.out
|  -- making example results for "determinant(MultidimensionalMatrix)" 
-- 1.00178 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_determinant_lp__Multidimensional__Matrix_rp.out
|  -- making example results for "genericLaurentPolynomials"   
-- 0.409039 seconds elapsed
|  -- storing example results in 
../../../usr-dist/common/share/doc/Macaulay2/SparseResultants/example-output/_generic__Laurent__Polynomials.out
| ../../m2/debugging.m2:20:6:(1):[9]: error: installPackage: 1 error(s) 
occurred running examples for package SparseResultants:
|
| _char_lp__Sparse__Resultant_rp.errors
| *
| -- -*- M2-comint -*- hash: 829653806
|
| i1 : R = denseResultant(2,2,1,CoefficientRing=>ZZ/331);
| Killed
|
| ../../m2/installPackage.m2:719:14:(1):[8]: --back trace--
| ../../m2/methods.m2:119:80:(1):[7]: --back trace--
| ../../m2/option.m2:16:8:(1):[6]: --back trace--
| ../../m2/installPackage.m2:603:5:(1):[5]: --back trace--
| ../../m2/methods.m2:119:80:(1):[4]: --back trace--
| ../../m2/option.m2:16:8:(1):[3]: --back trace--
| currentString:1:1:(3):[2]: --back trace--
| Macaulay2/Core/startup.m2.in:561:33:(0):[1]: --back trace--
| Macaulay2/Core/startup.m2.in:672:6:(0): --back trace--
| make[3]: *** [Makefile:94: 
/<>/M2/usr-dist/s390x-Linux-Debian-buildd-unstable/lib/s390x-linux-gnu/Macaulay2/SparseResultants/.installed]
 Error 1
| make[3]: Leaving directory '/<>/M2/Macaulay2/packages'
| make[2]: *** [Makefile:14: all-in-packages] Error 2
| make[2]: Leaving directory '/<>/M2/Macaulay2'
| make[1]: *** [GNUmakefile:221: all-in-Macaulay2] Error 2
| make[1]: Leaving directory '/<>/M2'
| 

Bug#993870: guesoglc FTBFS: make[2]: *** No rule to make target '../src/glew.c', needed by 'libGLC_la-glew.lo'. Stop.

[Paul Wise]

Control: tags -1 + sid

On Tue, 7 Sep 2021 12:14:21 +0200 Helmut Grohne wrote:

> quesoglc fails to build from source in unstable.

This seems to have been caused by the update to autoconf, it does not
occur with bookworm and upgrading autoconf to sid causes the issue.

Looking at the config.log, the old autoconf seems to do the check
twice, which works the first time but fails the second time.

The g++ command-line is identical for all three of the checks.

The new autoconf seems to only do the check once, which then fails.

The failure with the old autoconf is due to missing -DGLEW_MX=1,
which is a bug in the patch adding GLEW mx support.

The failure with the new autoconf seems to be C++ related, the same
test file links successfully when named .c and built with gcc.

The difference is that autoconf 2.71 removed this from conftest.cpp:

   #ifdef __cplusplus
   extern "C"
   #endif

OTOH the library is entirely C not C++ so it should use conftest.c
instead of conftest.cpp for detecting the tests.

It looks like AX_CHECK_GLU pulls in C++ support, but as far as I can
tell it restores the language correctly after modifying it.

Moving the AX_CHECK_GLU check after the GLEW check fixes the build.

When I delete build/m4/ax_check_glu.m4 and try to use the one from
autoconf-archive, the build fails due to a circular dependency:

   configure.in:157: error: m4_require: circular dependency of 
AC_LANG_COMPILER(C++)

When I then add AC_PROG_CXX before AX_CHECK_GLU then that failure
doesn't happen and the build succeeds as conftest.c is used this time.

Unfortunately that workaround does not work for the original copy of
the AX_CHECK_GLU macro in the upstream tarball.

Removing use of AC_PROG_CXX/AC_LANG_PUSH/POP from the original copy of
the AX_CHECK_GLU macro in the upstream tarball works around the issue.

I have zero idea where to go from here but I'm going to apply that
workaround for now and the next upstream release will drop the embedded
code and m4 copies so should not be affected by this bug either.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Processed: Re: guesoglc FTBFS: make[2]: *** No rule to make target '../src/glew.c', needed by 'libGLC_la-glew.lo'. Stop.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + sid
Bug #993870 [src:quesoglc] guesoglc FTBFS: make[2]: *** No rule to make target 
'../src/glew.c', needed by 'libGLC_la-glew.lo'.  Stop.
Ignoring request to alter tags of bug #993870 to the same tags previously set

-- 
993870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 947900

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 947900 + sid bookworm
Bug #947900 [chemical-mime-data] chemical-mime-data: build-depends on 
unmaintained gnome-mime-data
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
947900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 991066

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 991066 + pending
Bug #991066 [src:vlfeat] vlfeat FTBFS with imagemagick with the #987504 change
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
991066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 991113

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 991113 + pending
Bug #991113 [libpam-chroot] libpam-chroot installs pam_chroot.so into the wrong 
directory
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
991113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 991057

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 991057 + pending
Bug #991057 [src:gri] gri FTBFS with imagemagick with the #987504 change
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
991057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 993316

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 993316 + sid bookworm
Bug #993316 [debhelper] rpcbind: missing /lib/systemd/system/rpcbind.service 
file
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
993316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 992527

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 992527 + sid bookworm
Bug #992527 [src:node-srs] node-srs: FTBFS with GDAL 3.3.1
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
992527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 993843

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 993843 + sid bookworm
Bug #993843 [zsh-static] zsh-static segfaults immediately
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
993843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 993698, tagging 993699, tagging 993770, tagging 993870, tagging 993874, tagging 993875

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 993698 + sid bookworm
Bug #993698 [src:hacktv] hacktv: FTBFS with libsoapysdr 0.8
Added tag(s) sid and bookworm.
> tags 993699 + sid bookworm
Bug #993699 [src:libxtrx] libxtrx: FTBFS with libsoapysdr 0.8
Added tag(s) sid and bookworm.
> tags 993770 + sid bookworm
Bug #993770 [src:dazzdb] dazzdb: autopkgtest failure with glibc 2.32
Added tag(s) bookworm and sid.
> tags 993870 + sid bookworm
Bug #993870 [src:quesoglc] guesoglc FTBFS: make[2]: *** No rule to make target 
'../src/glew.c', needed by 'libGLC_la-glew.lo'.  Stop.
Added tag(s) bookworm and sid.
> tags 993874 + sid bookworm
Bug #993874 [src:slurm] flurm FTBFS with glibc 2.32: fatal error: sys/sysctl.h: 
No such file or directory
Added tag(s) sid and bookworm.
> tags 993875 + sid bookworm
Bug #993875 [src:urlview] urlview FTBFS: configure: error: cannot find required 
auxiliary files: compile missing
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
993698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993698
993699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993699
993770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993770
993870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993870
993874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993874
993875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#993915: libguestfs FTBFS on some buildds

[Adrian Bunk]

Source: libguestfs
Version: 1:1.44.1-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=libguestfs=1%3A1.44.1-4

...
unset XDG_RUNTIME_DIR; \
if ! test -w /dev/kvm; then \
export LIBGUESTFS_BACKEND_SETTINGS=force_tcg; \
fi
make -C /<>/debian/build-4 quickcheck
make[2]: Entering directory '/<>/debian/build-4'
./run test-tool/libguestfs-test-tool
libguestfs: error: converting path to absolute path: XDG_RUNTIME_DIR: 
/run/user/2952: realpath: No such file or directory
 
 *IMPORTANT NOTICE
 *
 * When reporting bugs, include the COMPLETE, UNEDITED
 * output below in your bug report.
 *
 
/<>/debian/build-4/test-tool/.libs/libguestfs-test-tool: failed 
parsing environment variables.
Check earlier messages, and the output of the ‘printenv’ command.
make[2]: *** [Makefile:3187: quickcheck] Error 1


08:46 < bunk> on x86 and arm64, *except* x86-grnet-01
08:46 < bunk> 1. Why not on grnet?
08:46 < bunk> 2. Is dh compat 13 worth a recommendation to the maintainer?
09:17 < aurel32> i guess it's because the buildds at grnet are using pybuildd, 
which is not affected by the libpam-systemd/schroot bug
09:19 < aurel32> and yes debhelper compat 13 might help there, at least present 
a stable environment


The dh compat 13 change is

  The dh_auto_* helpers now reset the environment variables
  HOME and common XDG_* variable.  Please see description of
  the environment variables in "ENVIRONMENT" for how this is
  handled.