Bug#925819: marked as done (rrep: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 05:36:25 +
with message-id 
and subject line Bug#925819: fixed in rrep 1.3.6-2
has caused the Debian Bug report #925819,
regarding rrep: ftbfs with GCC-9
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.)


-- 
925819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rrep
Version: 1.3.6-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/rrep_1.3.6-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o fd-safer.o fd-safer.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o pipe-safer.o pipe-safer.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o wctype-h.o wctype-h.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o xmalloc.o xmalloc.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o xalloc-die.o xalloc-die.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o xstriconv.o xstriconv.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o yesno.o yesno.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o fcntl.o fcntl.c
rm -f t-charset.alias charset.alias && \
/bin/bash ./config.charset 'x86_64-pc-linux-gnu' > t-charset.alias && \
mv t-charset.alias charset.alias
rm -f t-ref-add.sed ref-add.sed && \
sed -e '/^#/d' -e 's/@''PACKAGE''@/rrep/g' ref-add.sin > t-ref-add.sed && \
mv t-ref-add.sed ref-add.sed
rm -f t-ref-del.sed ref-del.sed && \
sed -e '/^#/d' -e 's/@''PACKAGE''@/rrep/g' ref-del.sin > t-ref-del.sed && \
mv t-ref-del.sed ref-del.sed
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o unistr/u8-mbtoucr.o unistr/u8-mbtoucr.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o unistr/u8-uctomb.o unistr/u8-uctomb.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o unistr/u8-uctomb-aux.o unistr/u8-uctomb-aux.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. 

Bug#925766: marked as done (linux: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#925766: fixed in linux 5.2.9-1
has caused the Debian Bug report #925766,
regarding linux: ftbfs with GCC-9
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.)


-- 
925766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.28-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/linux_4.19.28-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-sched.1+ 
perf-sched.txt && \
mv /<>/debian/build/build-tools/tools/perf/perf-sched.1+ 
/<>/debian/build/build-tools/tools/perf/perf-sched.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-kvm.1+ 
/<>/debian/build/build-tools/tools/perf/perf-kvm.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-kvm.1+ perf-kvm.txt 
&& \
mv /<>/debian/build/build-tools/tools/perf/perf-kvm.1+ 
/<>/debian/build/build-tools/tools/perf/perf-kvm.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-annotate.1+ 
/<>/debian/build/build-tools/tools/perf/perf-annotate.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-annotate.1+ 
perf-annotate.txt && \
mv /<>/debian/build/build-tools/tools/perf/perf-annotate.1+ 
/<>/debian/build/build-tools/tools/perf/perf-annotate.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-top.1+ 
/<>/debian/build/build-tools/tools/perf/perf-top.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-top.1+ perf-top.txt 
&& \
mv /<>/debian/build/build-tools/tools/perf/perf-top.1+ 
/<>/debian/build/build-tools/tools/perf/perf-top.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-stat.1+ 
/<>/debian/build/build-tools/tools/perf/perf-stat.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-stat.1+ perf-stat.txt 
&& \
mv /<>/debian/build/build-tools/tools/perf/perf-stat.1+ 
/<>/debian/build/build-tools/tools/perf/perf-stat.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-ftrace.1+ 
/<>/debian/build/build-tools/tools/perf/perf-ftrace.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-ftrace.1+ 
perf-ftrace.txt && \
mv /<>/debian/build/build-tools/tools/perf/perf-ftrace.1+ 

Bug#925864: marked as done (xlog: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 04:16:19 +
with message-id 
and subject line Bug#925864: fixed in xlog 2.0.14-2
has caused the Debian Bug report #925864,
regarding xlog: ftbfs with GCC-9
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.)


-- 
925864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xlog
Version: 2.0.14-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/xlog_2.0.14-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
config.status: creating data/man/xlog.1
config.status: creating src/Makefile
config.status: creating src/logfile/Makefile
config.status: creating data/Makefile
config.status: creating data/desktop/Makefile
config.status: creating data/pixmaps/Makefile
config.status: creating data/mime/Makefile
config.status: creating data/man/Makefile
config.status: creating data/maps/Makefile
config.status: creating data/maps/3D2/Makefile
config.status: creating data/maps/3Y/Makefile
config.status: creating data/maps/E5/Makefile
config.status: creating data/maps/FK/Makefile
config.status: creating data/maps/FO/Makefile
config.status: creating data/maps/FR/Makefile
config.status: creating data/maps/HK0/Makefile
config.status: creating data/maps/JD/Makefile
config.status: creating data/maps/KH8/Makefile
config.status: creating data/maps/SV/Makefile
config.status: creating data/maps/VP6/Makefile
config.status: creating data/maps/VP8/Makefile
config.status: creating data/doc/Makefile
config.status: creating data/doc/manual/Makefile
config.status: creating data/doc/manual/output/Makefile
config.status: creating data/doc/manual/output/html/Makefile
config.status: creating data/doc/manual/output/html/search/Makefile
config.status: creating data/dxcc/Makefile
config.status: creating data/remote/Makefile
config.status: creating data/glabels/Makefile
config.status: creating data/utils/Makefile
config.status: creating data/images/Makefile
config.status: executing depfiles commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
dh_testdir
# Add here commands to compile the package.
/usr/bin/make
make[1]: Entering directory '/<>'
Making all in src
make[2]: Entering directory '/<>/src'
Making all in logfile
make[3]: Entering directory '/<>/src/logfile'
x86_64-linux-gnu-gcc -DPACKAGE_NAME=\"xlog\" -DPACKAGE_TARNAME=\"xlog\" 
-DPACKAGE_VERSION=\"2.0.14\" -DPACKAGE_STRING=\"xlog\ 2.0.14\" 
-DPACKAGE_BUGREPORT=\"kb1...@arrl.net\" -DPACKAGE_URL=\"\" -DPACKAGE=\"xlog\" 
-DVERSION=\"2.0.14\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_IPC_H=1 
-DHAVE_SYS_SHM_H=1 -DHAVE_STRPTIME=1 -DHAVE_STRCHR=1 -DHAVE_INDEX=1 
-DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -I.  -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2  
-Wall -g -O2 -Wall -Wno-unused-but-set-variable -Werror -MT logfile.o -MD -MP 
-MF .deps/logfile.Tpo -c -o logfile.o logfile.c
mv -f .deps/logfile.Tpo .deps/logfile.Po
x86_64-linux-gnu-gcc -DPACKAGE_NAME=\"xlog\" 

Processed: tagging 925700

[Debian Bug Tracking System]

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

> tags 925700 + upstream
Bug #925700 [src:gnucash] gnucash: ftbfs with GCC-9
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 925700 is forwarded to https://bugs.gnucash.org/show_bug.cgi?id=797356

[Debian Bug Tracking System]

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

> forwarded 925700 https://bugs.gnucash.org/show_bug.cgi?id=797356
Bug #925700 [src:gnucash] gnucash: ftbfs with GCC-9
Set Bug forwarded-to-address to 
'https://bugs.gnucash.org/show_bug.cgi?id=797356'.
> thanks
Stopping processing here.

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

Bug#935016: marked as done (pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 01:59:03 +
with message-id 
and subject line Bug#935016: fixed in pkg-js-tools 0.9.6
has caused the Debian Bug report #935016,
regarding pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools
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.)


-- 
935016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkg-js-tools
Version: 0.9.5
Severity: grave
Justification: renders package unusable

pkg-js-tools was based on add_command_options which disappears in
Debhelper 12.5.1. This renders pkg-js-tools unusable.
--- End Message ---
--- Begin Message ---
Source: pkg-js-tools
Source-Version: 0.9.6

We believe that the bug you reported is fixed in the latest version of
pkg-js-tools, 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 935...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated pkg-js-tools 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, 18 Aug 2019 08:28:28 +0200
Source: pkg-js-tools
Architecture: source
Version: 0.9.6
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 935016
Changes:
 pkg-js-tools (0.9.6) unstable; urgency=medium
 .
   * Fix debhelper sequence return value and update test (Closes: #935016)
Checksums-Sha1: 
 630c52ae3076d6bf258384096077f13efd6bf4aa 1975 pkg-js-tools_0.9.6.dsc
 9251516ad993f224e7377bb720219f041654aac1 28388 pkg-js-tools_0.9.6.tar.xz
Checksums-Sha256: 
 f85f045c4953fec4774afd4c8da45612c7146fb46c7bc3ef9c5f19f68d24bf7e 1975 
pkg-js-tools_0.9.6.dsc
 73676c795ea053917a76de89cef2f94ead7650be1f8850191eaa18990277513f 28388 
pkg-js-tools_0.9.6.tar.xz
Files: 
 76dcd3f9fae713950853a07e06ee1181 1975 devel optional pkg-js-tools_0.9.6.dsc
 7a9115600662cce1da8aa0df0e19dfb6 28388 devel optional pkg-js-tools_0.9.6.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl1Y8GsACgkQ9tdMp8mZ
7ukfhA/+Iw9zykBC8x2gRA79BLYqTUD/na7cW29J6q/fVywFAuLqERpCFfrl9DXe
0zpFVMSYu2ZS6zl8Y2Y8TwFvYfy4zTLueGgLvgJfAL+UrT4g1eB/4+/QVre5T0iZ
Vw9GV/p8aoqo4rTYdWDlIfX7s2UdtqefUqm9lOFFr0zSA9T0a27OhMIXkWNc5s5K
QRSQLovhEbcTrpI32kWvLZHmhhWLyaeAmjSQy9p+9VfHsTBCU2mhkeL0vvfBXQIK
jAaBCEqMOdQc0GQwYA+Xgs4iOX7A5oq30cSP0Oxh0F6BJ5BwKfMdmB3kVfp74ZbJ
hdd6BrCrQoYw5AThAumXWFvSGqRDf7z03bdd5UyvIKM3/z8RE72DfkcMvVI7cCpg
pyX3dU/q4PqsCBcNJMAjtZSMlqASgriG4+IfGeKQRZAKPaj+YlDpaDhpkV+XjuLt
bWEE/SfDZ6Z0uLsuykcmvZi3cKYa2NBRk+Y7bssDunY5YDNUfE0rVWBwLAz1YHme
IQpAu1MxI/dzNadP3OQ85yPp1YVRTiIVBi+CDqHA7Ft13mXla2yjPm9Jsw0WLetc
7RtmVvAFmlwsYHAyhkiouJ6wXY4xhyKA0EaEJN7G4IvR//BJ4btikR1uUFyq/RfG
gpbPAQTrFGLE7OSY4MqCSlBVjqJ1cKxecvglaMS586j8y/5O6yU=
=FrGH
-END PGP SIGNATURE End Message ---

Bug#925790: marked as done (nspr: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 01:47:00 +
with message-id 
and subject line Bug#925790: fixed in nspr 2:4.21-2
has caused the Debian Bug report #925790,
regarding nspr: ftbfs with GCC-9
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.)


-- 
925790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nspr
Version: 2:4.20-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/nspr_4.20-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
multiwait   Passed
nameshm1Passed
nonblockPassed
ntioto  Passed
ntohPassed
op_2longPassed
op_excl Passed
op_filnfPassed
op_filokPassed
op_nofilPassed
parent  Passed
parsetm Passed
perfPassed
pipepingPassed
pipeping2   Passed
pipeselfPassed
poll_nm Passed
poll_to Passed
pollablePassed
prftest Passed
prfzPassed
primblokPassed
providerPassed
prpollmlPassed
pushtop Passed
ranfile Passed
randseedPassed
reinit  Passed
rwlocktest  Passed
sel_spd Passed
selct_erPassed
selct_nmPassed
selct_toPassed
selintr Passed
semaPassed
semaerr Passed
semapingPassed
sendzlf Passed
server_test Passed
servr_kkPassed
servr_ukPassed
servr_kuPassed
servr_uuPassed
short_threadPassed
sigpipe Passed
sockopt Passed
sockpingPassed
sprintf Passed
stack   Passed
stdio   Passed
str2addrPassed
strod   Passed
switch  Passed
system  Passed
testbit Passed
testfilePassed
threads Passed
timemac Passed
timetestPassed
tpd Passed
udpsrv  Passed
version Passed
writev  Passed
xnotify Passed
zerolen Passed
END Tue Mar 26 16:10:41 UTC 2019
make[1]: *** [debian/rules:87: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:41: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: nspr
Source-Version: 2:4.21-2

We believe that the bug you reported is fixed in the latest version of
nspr, which is due to be installed in the 

Bug#934914: marked as done (m2crypto: non-buildd binaries)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 01:34:10 +
with message-id 
and subject line Bug#934914: fixed in m2crypto 0.31.0-6
has caused the Debian Bug report #934914,
regarding m2crypto: non-buildd binaries
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.)


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

Package: m2crypto
Version: 0.31.0-5
Severity: serious

The release team have decreed that binaries not built on a buildd can no longer 
migrate to testing. Please make a source-only upload so your package can 
migrate.
--- End Message ---
--- Begin Message ---
Source: m2crypto
Source-Version: 0.31.0-6

We believe that the bug you reported is fixed in the latest version of
m2crypto, 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 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated m2crypto 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, 18 Aug 2019 18:29:59 +0200
Source: m2crypto
Architecture: source
Version: 0.31.0-6
Distribution: unstable
Urgency: medium
Maintainer: Daniel Stender 
Changed-By: Daniel Stender 
Closes: 934914
Changes:
 m2crypto (0.31.0-6) unstable; urgency=medium
 .
   * Perform complete source-only upload (Closes: #934914).
Checksums-Sha1: 
 378fa0cea8189a20cace685cdfe046df9d2bba65 2444 m2crypto_0.31.0-6.dsc
 5be8141620a03035073cb1eca40738ed0540faf0 59716 m2crypto_0.31.0-6.debian.tar.xz
Checksums-Sha256: 
 c74cc48aec6150d7fe81bf2847463a36ac10d8f473c780a935876bfbce708f84 2444 
m2crypto_0.31.0-6.dsc
 89699cc56d0f7fb1a127dac26373e932ae11f9b08e439ca4ae8c711e5fad6651 59716 
m2crypto_0.31.0-6.debian.tar.xz
Files: 
 9acac8b42560ac31a3ca5c273ef981db 2444 python optional m2crypto_0.31.0-6.dsc
 75327a52d83f56bacf0cc04c60d24776 59716 python optional 
m2crypto_0.31.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERsscqJ6jt0N2dh25FeCa9N9RgsgFAl1Zf7QACgkQFeCa9N9R
gsjblg/+MgmIsTimQLjw8AFJL6S9deH5zGPPmJidSunrPRlnScNOb2hugtTpq4Wp
kPpBYt8XVFllForguzPrXpo2xDh9cSSlttzOoMjQPNGzDWZcVjclFrHEcVESHDL4
1oEvIpy3ZcS114p8qsuIgv8l2fvEqu7QcifsUn6+t6hHlxa3Pq39WtHX9jByjmG0
63L6AXWYSXJuku6myNdg1d1TX3gZScNOpA6St3/S04DU9s+n0M1S9If3eFGejLT/
ciG/+Q1E9rEBtnbznA+MfjfYHXWqcV478lhil9WN8tJfZHBh7qpxtR0FpM4U585s
Mg+/Bi06Z9NGs/SMFZguMnApnEdaGBehAIf/yHn6Qq+JR0xRAJLkTNX1pxCAXt1R
nt94q96M8UztNab2awo2uXgHjOpjzK6pXenfza+HG8UbDnET7nTBe6jL2OjXvVEs
/HgP60wtgcLbnYCgO0CjBHM1g8FgwgrwEpqnurjHxYaIannVUsk3CgFeRUS6POZM
m3T/si/rmDAJq5uOKqs9s7bXaBzLifCGQ1ZkPXDMyBWWBUKHDTiDgL58Yrr2Ga6q
U/gjEHKrDpOJe1W1IH/0+OKK6ZUnlX1mkRjkCQiyXKLfZVNcnLLKaz0xJAO89vEb
1r4LU7l0NdvzsVJj0TY0BEAyQg1RsemUbgxCJi5IYY7p8ncoq1U=
=S7Bg
-END PGP SIGNATURE End Message ---

Bug#925756: marked as done (libosmocore: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 00:59:25 +
with message-id 
and subject line Bug#925756: fixed in libosmocore 0.12.1-3
has caused the Debian Bug report #925756,
regarding libosmocore: ftbfs with GCC-9
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.)


-- 
925756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libosmocore
Version: 0.12.1-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/libosmocore_0.12.1-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
-Testing creating Assignment Complete
-Testing creating Assignment Complete (AoIP)
-Testing creating Assignment Failure
-Testing creating Assignment Failure (AoIP)
-Testing creating Clear Request
-Testing creating Paging Request
-Testing creating DTAP
-Testing prepend DTAP
-test_gsm0808_enc_dec_cell_id_list_lac: encoded: 1a 07 05 01 24 ab cd 56 78 (rc 
= 9)
 test_cell_id_list_add
- cell_id_list == CGI[0]:{}
-gsm0808_cell_id_list_add(, ) --> rc = 1
- cell_id_list == LAC[1]:{123}
-gsm0808_cell_id_list_add(, ) --> rc = 0
- cell_id_list == LAC[1]:{123}
-gsm0808_cell_id_list_add(, ) --> rc = 2
- cell_id_list == LAC[3]:{123, 456, 789}
-gsm0808_cell_id_list_add(, ) --> rc = 0
- cell_id_list == LAC[3]:{123, 456, 789}
-gsm0808_cell_id_list_add(, ) --> rc = 0
- cell_id_list == LAC[3]:{123, 456, 789}
-gsm0808_cell_id_list_add(, ) --> rc = -22
- cell_id_list == LAC[3]:{123, 456, 789}
-* can't add to BSS list
- cell_id_list == BSS[0]
-gsm0808_cell_id_list_add(, ) --> rc = -22
- cell_id_list == BSS[0]
-* other types (including NO_CELL) take on new type iff empty
- cell_id_list == NO-CELL[0]
-gsm0808_cell_id_list_add(, ) --> rc = 1
- cell_id_list == CGI[1]:{001-02-3-4}
-gsm0808_cell_id_list_add(, ) --> rc = 0
- cell_id_list == CGI[1]:{001-02-3-4}
-gsm0808_cell_id_list_add(, ) --> rc = 2
- cell_id_list == CGI[3]:{001-02-3-4, 001-002-3-4, 005-006-7-8}
-gsm0808_cell_id_list_add(, ) --> rc = 0
- cell_id_list == CGI[3]:{001-02-3-4, 001-002-3-4, 005-006-7-8}
-* test gsm0808_cell_id_list_name_buf()'s return val
-  strlen(gsm0808_cell_id_list_name(cil)) == 45
-  gsm0808_cell_id_list_name_buf(buf, 46, cil)) == 45 "CGI[3]:{001-02-3-4, 
001-002-3-4, 005-006-7-8}"
-  gsm0808_cell_id_list_name_buf(buf, 23, cil)) == 45 "CGI[3]:{001-02-3-4, 00"
-  gsm0808_cell_id_list_name_buf(buf, 11, cil)) == 45 "CGI[3]:{00"
-  gsm0808_cell_id_list_name_buf(buf, 5, cil)) == 45 "CGI["
-  gsm0808_cell_id_list_name_buf(buf, 2, cil)) == 45 "C"
-  gsm0808_cell_id_list_name_buf(buf, 1, cil)) == 45 ""
-  gsm0808_cell_id_list_name_buf(buf, 0, cil)) == 45 "#"
-* list-full behavior
-cil.id_list_len = 126
-gsm0808_cell_id_list_add(, ) --> rc = 1
-cil.id_list_len = 127
-cil.id_list_len = 126
-gsm0808_cell_id_list_add(, ) --> rc = -28
-cil.id_list_len = 127
-gsm0808_cell_id_list_add(, ) --> rc = -28
-cil.id_list_len = 127
 test_cell_id_list_add done
-test_gsm0808_enc_dec_cell_id_lac: encoded: 05 03 05 01 24 (rc = 5)
-test_gsm0808_enc_dec_cell_id_bss: encoded: 05 01 06 (rc = 3)
-test_gsm0808_enc_dec_cell_id_no_cell: encoded: 05 01 03 (rc = 3)
-test_gsm0808_enc_dec_cell_id_lai_and_lac: encoded: 05 06 04 21 63 54 23 42 (rc 
= 8)

Bug#925740: marked as done (libedlib: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Aug 2019 00:34:56 +
with message-id 
and subject line Bug#925740: fixed in libedlib 1.2.4-2
has caused the Debian Bug report #925740,
regarding libedlib: ftbfs with GCC-9
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.)


-- 
925740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libedlib
Version: 1.2.4-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/libedlib_1.2.4-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
creating edlib.egg-info
writing edlib.egg-info/PKG-INFO
writing dependency_links to edlib.egg-info/dependency_links.txt
writing top-level names to edlib.egg-info/top_level.txt
writing manifest file 'edlib.egg-info/SOURCES.txt'
reading manifest file 'edlib.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'edlib.egg-info/SOURCES.txt'
Copying edlib.egg-info to 
/<>/debian/python3-edlib/usr/lib/python3.7/dist-packages/edlib-1.2.3.post1.egg-info
Skipping SOURCES.txt
running install_scripts
/usr/lib/python3/dist-packages/setuptools/dist.py:475: UserWarning: Normalizing 
'1.2.3-1' to '1.2.3.post1'
  normalized_version,
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
file-rename 's/_static\.a/.a/' `find debian -name libedlib_static.a`
d-shlibmove --commit \
--multiarch \
--devunversioned \
--exclude-la \
--movedev debian/tmp/usr/include/* usr/include \
debian/tmp/usr/lib/*.so
Library package automatic movement utility
set -e
install -d -m 755 debian/libedlib-dev/usr/lib/x86_64-linux-gnu
install -d -m 755 debian/libedlib0/usr/lib/x86_64-linux-gnu
mv debian/tmp/usr/lib/libedlib.a debian/libedlib-dev/usr/lib/x86_64-linux-gnu
mv debian/tmp/usr/lib/libedlib.so debian/libedlib-dev/usr/lib/x86_64-linux-gnu
mv /<>/debian/tmp/usr/lib/libedlib.so.0 
debian/libedlib0/usr/lib/x86_64-linux-gnu
mv /<>/debian/tmp/usr/lib/libedlib.so.1.2.3 
debian/libedlib0/usr/lib/x86_64-linux-gnu
PKGDEV=libedlib-dev
PKGSHL=libedlib0
install -d -m 755 debian/libedlib-dev/usr/include
mv debian/tmp/usr/include/edlib.h debian/libedlib-dev/usr/include
make[1]: Leaving directory '/<>'
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installexamples -a
   dh_installman -a
   dh_python3 -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_dwz -a
   dh_strip -a
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libedlib0/DEBIAN/symbols doesn't match 
completely debian/libedlib0.symbols
--- debian/libedlib0.symbols (libedlib0_1.2.4-1_amd64)
+++ dpkg-gensymbolsR_He6e   2019-03-26 16:47:24.379121607 +
@@ -1,7 +1,9 @@
 libedlib.so.0 libedlib0 #MINVER#
  
_ZN18EqualityDefinitionC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPK17EdlibEqualityPairi@Base
 1.2.3
  
_ZN18EqualityDefinitionC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPK17EdlibEqualityPairi@Base
 1.2.3
- 

Bug#934593: marked as done (binutils-mipsen: uses wrong source version when binNMUed)

[Debian Bug Tracking System]

Your message dated Sun, 18 Aug 2019 23:14:01 +
with message-id 
and subject line Bug#934593: fixed in binutils-mipsen 3~c2
has caused the Debian Bug report #934593,
regarding binutils-mipsen: uses wrong source version when binNMUed
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.)


-- 
934593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:binutils-mipsen
version: 3~c1
severity: serious
tags: ftbfs

Hi,

A binNMU for binutils-mipsen was rejected by the archive:

coccia:~ $ cat 
/srv/ftp-master.debian.org/queue/reject/binutils-mipsen_3~c1+b1_amd64.changes.reason
binutils-mips64-linux-gnuabi64_2.32.51.20190727-1cross1+b1_amd64.deb: trying to 
install to unstable, but could not find source

This is caused by the wrong source version:

https://buildd.debian.org/status/fetch.php?pkg=binutils-mipsen=amd64=3%7Ec1%2Bb1=1565572631=0

binutils-mips64-linux-gnuabi64_2.32.51.20190727-1cross1+b1_amd64.deb


 new Debian package, version 2.0.
 size 2530448 bytes: control archive=4212 bytes.
 869 bytes,21 lines  control  
   13940 bytes,   157 lines  md5sums  
  26 bytes, 1 lines  triggers 
 Package: binutils-mips64-linux-gnuabi64
 Source: binutils-mipsen (3~c1+b1)
 Version: 2.32.51.20190727-1cross1+b1

Obviously, this should be

Source: binutils-mipsen (3~c1)

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: binutils-mipsen
Source-Version: 3~c2

We believe that the bug you reported is fixed in the latest version of
binutils-mipsen, 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 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
YunQiang Su  (supplier of updated binutils-mipsen 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: Thu, 15 Aug 2019 09:21:15 +0800
Source: binutils-mipsen
Binary: binutils-mips64-linux-gnuabi64 binutils-mips64-linux-gnuabi64-dbg 
binutils-mips64-linux-gnuabin32 binutils-mips64-linux-gnuabin32-dbg 
binutils-mips64el-linux-gnuabin32 binutils-mips64el-linux-gnuabin32-dbg 
binutils-mipsisa32r6-linux-gnu binutils-mipsisa32r6-linux-gnu-dbg 
binutils-mipsisa32r6el-linux-gnu binutils-mipsisa32r6el-linux-gnu-dbg 
binutils-mipsisa64r6-linux-gnuabi64 binutils-mipsisa64r6-linux-gnuabi64-dbg 
binutils-mipsisa64r6-linux-gnuabin32 binutils-mipsisa64r6-linux-gnuabin32-dbg 
binutils-mipsisa64r6el-linux-gnuabi64 binutils-mipsisa64r6el-linux-gnuabi64-dbg 
binutils-mipsisa64r6el-linux-gnuabin32 
binutils-mipsisa64r6el-linux-gnuabin32-dbg
Architecture: source amd64
Version: 3~c2
Distribution: unstable
Urgency: medium
Maintainer: YunQiang Su 
Changed-By: YunQiang Su 
Description:
 binutils-mips64-linux-gnuabi64 - GNU binary utilities, for 
mips64-linux-gnuabi64 target
 binutils-mips64-linux-gnuabi64-dbg - GNU binary utilities, for 
mips64-linux-gnuabi64 target (debug sym
 binutils-mips64-linux-gnuabin32 - GNU binary utilities, for 
mips64-linux-gnuabin32 target
 binutils-mips64-linux-gnuabin32-dbg - GNU binary utilities, for 
mips64-linux-gnuabin32 target (debug sy
 binutils-mips64el-linux-gnuabin32 - GNU binary utilities, for 
mips64el-linux-gnuabin32 target
 binutils-mips64el-linux-gnuabin32-dbg - GNU binary utilities, for 
mips64el-linux-gnuabin32 target (debug
 binutils-mipsisa32r6-linux-gnu - GNU binary utilities, for 
mipsisa32r6-linux-gnu target
 binutils-mipsisa32r6-linux-gnu-dbg - GNU binary utilities, for 
mipsisa32r6-linux-gnu target (debug sym
 binutils-mipsisa32r6el-linux-gnu - GNU binary utilities, for 
mipsisa32r6el-linux-gnu target
 binutils-mipsisa32r6el-linux-gnu-dbg - GNU binary utilities, for 
mipsisa32r6el-linux-gnu target (debug s
 binutils-mipsisa64r6-linux-gnuabi64 - GNU binary utilities, for 
mipsisa64r6-linux-gnuabi64 target
 binutils-mipsisa64r6-linux-gnuabi64-dbg - GNU binary utilities, for 
mipsisa64r6-linux-gnuabi64 target (debu
 binutils-mipsisa64r6-linux-gnuabin32 - GNU binary utilities, for 
mipsisa64r6-linux-gnuabin32 target
 

Bug#926534: marked as done (libgps changed API of gps_read)

[Debian Bug Tracking System]

Your message dated Sun, 18 Aug 2019 23:11:49 +
with message-id 
and subject line Bug#926534: fixed in aweather 0.8.1-1.2
has caused the Debian Bug report #926534,
regarding libgps changed API of gps_read
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.)


-- 
926534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aweather
Version: 0.8.1-1

Hi,
libgps changed the gps_read implementation in [0].
To be clear the change in gpsd is currently only in experimental. This
is a heads up for the post buster transition that will come sooner or
later.

Upstream aweather [1] seems to be rather static or dead. At least
there is no way to report the issue there as [2] is down.

The change isn't too hard and will be compatible with older versions
of gpsd. Therefore I'd appreciate if you could include this change in
when-/whatever the next upload to aweather will happen. I'll let the
gpsd maintainer know about the bug, so that we can consider it when
kicking off the transition.

I'll submit a salsa MP once I have the bug number to reference it.

OTOH - this package wasn't touched in quite some time, upstream seems
dead as well and popcon [3] (if you trust the data) is rather low - so
removal might be an option as well?.


[0]: https://git.savannah.gnu.org/cgit/gpsd.git/commit/?id=6bba8b329
[1]: http://pileus.org/aweather/development
[2]: http://pileus.org/dev/projects/aweather/issues
[3]: https://qa.debian.org/popcon.php?package=aweather

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: aweather
Source-Version: 0.8.1-1.2

We believe that the bug you reported is fixed in the latest version of
aweather, 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 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated aweather 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: Sun, 18 Aug 2019 23:21:00 +0200
Source: aweather
Architecture: source
Version: 0.8.1-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Bernd Zeimetz 
Closes: 926534
Changes:
 aweather (0.8.1-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Support new libgps API. Closes: #926534
 Thanks: Christian Ehrhardt
Checksums-Sha1:
 2fb81962ac5eb249144cb8e52a68e11d74e36669 2203 aweather_0.8.1-1.2.dsc
 69590d8fa8c3d161a8b4f1feabaa09aa496b775e 3332 aweather_0.8.1-1.2.debian.tar.xz
 ab3c21ecc3335cc541b8c0ebe5e426b10d55a4f7 12739 
aweather_0.8.1-1.2_source.buildinfo
Checksums-Sha256:
 4d8f4b8c1d5d0b59e8d96a92c7f2accb4e491eab4f3939f49f7096cf6ee5d461 2203 
aweather_0.8.1-1.2.dsc
 3904f3c7018e910348e939a6dc21468e467cc37e9ba6e241e8407d5440d58cbf 3332 
aweather_0.8.1-1.2.debian.tar.xz
 eb82d82a933b7e11229c944d70aa27968fe293b0482b8beab843596603340bb1 12739 
aweather_0.8.1-1.2_source.buildinfo
Files:
 325c22c318709abca9d5a7ec08d8ebf7 2203 science extra aweather_0.8.1-1.2.dsc
 2c2fee3df9d75df79f882f11b7e4987c 3332 science extra 
aweather_0.8.1-1.2.debian.tar.xz
 cae2e6ba47092a0dac9d422af6e39868 12739 science extra 
aweather_0.8.1-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl1ZwZQQHGJ6ZWRAZGVi
aWFuLm9yZwAKCRDrNhcab/lDX44RD/9YObb7sjCNzNr6tAtu8B1GqxXpQULWfb1O
0J6MlSHfMFrgL1OTV/mIrp1DzSmcvd14RNwr/Rvxb6dHONF6Y9JrvwAFz9c4ou/j
mtBhcRugN5dOuJsVOEstDhnpgf3mXvn9KkUV21XWJYZyaNw3nGIoE2TQxHS0UQ+K
u87xoZMSto4z7rIGXN+H6SLKGx49wGFhTSqCYsDI1wWKXEtvJ9Z/+y6eq1G+0ANW
XzJOq+2stWRcpE49yweD/F+m9JqH2w3sH3l8Nm/bs9OBAcE5m9MfjlB2aY8cZDcu
vKkz6U3DLBBMeXpN20eTHjP1Mmavqmp0DJjUIHzvf3TNValVqhnxm0Db1hZ11JjT
3BpBCiBB2DCyozjGlPFfvOicML1N2ylnZ4Uh5/JFTp/RSItwPuX4t5aIkvDW/rZt
8iH10QVWBLRWSjs9zNDScWSH+gKJ1VV6XO9FAU+cwmKCrF4CObKhXLE443FiRFq1
4toUIJknIDVWSgaY0tA8b06HFRr3Q4oHfpEAb/FxYTXuudfvvdjSzamBbUTRo0C4
uXMXdGlRwG5Qtv5gTjFkQrTyznWGhw22641K+w0RE2p1kavd2v8A04Vs5E89DRkT
TAC9HI/rmgfv8eihhM1qmzAvTrIBVb41RJXAIuUm4DIWZHY4eEESvkOOPGM6LfP0
5GS2nEgNKQ==
=G/lX
-END PGP SIGNATURE End Message ---

Bug#932185: marked as done (auto-multiple-choice depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Sun, 18 Aug 2019 23:11:39 +
with message-id 
and subject line Bug#932185: fixed in auto-multiple-choice 1.4.0-2
has caused the Debian Bug report #932185,
regarding auto-multiple-choice depends on cruft package.
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.)


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

Package: auto-multiple-choice
Version: 1.4.0-1
Tags: bullseye, sid

Auto-multiple choice depends on texlive-generic-recommended which is no longer 
built by texlive-base. texlive-generic-reccomended seems to be a transitional 
package so presumablly you just need to update your dependency.
--- End Message ---
--- Begin Message ---
Source: auto-multiple-choice
Source-Version: 1.4.0-2

We believe that the bug you reported is fixed in the latest version of
auto-multiple-choice, 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 932...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexis Bienvenüe  (supplier of updated auto-multiple-choice 
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, 18 Aug 2019 20:48:56 +0200
Source: auto-multiple-choice
Architecture: source
Version: 1.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alexis Bienvenüe 
Changed-By: Alexis Bienvenüe 
Closes: 922567 932185
Changes:
 auto-multiple-choice (1.4.0-2) unstable; urgency=medium
 .
   * Updates OpenCV build includes for use with OpenCV4. Closes: #922567.
   * Drops unused and deprecated latex-generic-recommended dependency.
 Closes: #932185.
   * Bump standards version to 4.4.0: no change needed.
   * Bump debhelper compat version to 12: no change needed.
   * Don't register sample PDF subjects and LaTeX package description
 as documentation files.
Checksums-Sha1:
 9d33523e7c4dc0b81d5c6aa4a972bee52b4ecf46 2707 auto-multiple-choice_1.4.0-2.dsc
 25f34ecc85300daa1b4862d4889f3ae7097d26d4 12172 
auto-multiple-choice_1.4.0-2.debian.tar.xz
 fc5e8d403843b088240c37d61c9e83d022e5b374 22996 
auto-multiple-choice_1.4.0-2_amd64.buildinfo
Checksums-Sha256:
 cd8792ccc73f10dc23926445d2971cb62ba01b54a4364f072a4eba2cdfaec93f 2707 
auto-multiple-choice_1.4.0-2.dsc
 2c34964fca65246f6906e19db9c501cb6615f86957651b3147cb3d81d53b8e78 12172 
auto-multiple-choice_1.4.0-2.debian.tar.xz
 df12e9402052b4994aaa20d9ec5420dd14f025dbbacd8440dbf2c1fb872722e5 22996 
auto-multiple-choice_1.4.0-2_amd64.buildinfo
Files:
 7518fb6b57fb9d706fec2b8b62a33538 2707 education optional 
auto-multiple-choice_1.4.0-2.dsc
 f3a4b5ca98cdb67e548b05b5de1244df 12172 education optional 
auto-multiple-choice_1.4.0-2.debian.tar.xz
 cf0fd20ac13510ba55ea25f6da7186c6 22996 education optional 
auto-multiple-choice_1.4.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEqiIrIniZMZ7KPBo2StWOMGjmaeIFAl1ZoL8RHHBhZG9AcGFz
c29pcmUuZnIACgkQStWOMGjmaeJaZA/9EEz1RT4bHIhka51WrlUqD1qTMKfK3SVn
CO7i/jOtV+bxFFWUvU9bLSrEUDpvOdUEdF4KyBuwAv694inNLGn+ENaLIASZeb7N
Ujscdhw/4nSKScdTb1BGpWp58p4cmlZDW2xUPlLFvNoQi+a4hEirPXH9vq6w8hND
9ZREeWpTDTxnbFpVhwTI5AaMCs+9fZbimCzWLXLijgTGNSgxn2Ye8g/tSa27lXwe
q1e8iyvVauLMii8Z7KNfi8jZ2Pzm8hLcUcquyjMBrbLx0jsSYXZRwbNwsAB5/ZL9
HMcbB76m3QFNIbRtl/mdP4BKhonL/egVtHCxufGuFsZFi1d6xDxgxFUMKAelhjO/
fNXFYPbxsT1dJF5rUEXwkAxZbGcopVVDbQkYU/gKzbEXrvnBh435n4SEn7sfBQtJ
Uj2haxHzdqfixtFNzHnuXYk9ZjtCUAQLDnwgMdQjo5TL2vMZBLlV2sO5lg6Qb6YR
akwZ1rkYJqNuDe2kLFM/79tU61MH3u7Oo90Lp9odX3IQ6UcvYmiN/7ErUrpml2BR
ZpGgNAxIghB+pSDGa/qRVsN//0t/jHD+Cy4MMdWz1f9G733W5dZevKJz8UKj+Cz7
zsBMVUl3QopkgnIX0SgAaGTkjuMh3nfHmsZcOE5jDEIwIPADr1f9goxDN4k8aydn
9RrEVqQAoho=
=IovJ
-END PGP SIGNATURE End Message ---

Bug#925626: marked as done (acpi-support: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Aug 2019 23:00:37 +
with message-id 
and subject line Bug#925626: fixed in acpi-support 0.143-1
has caused the Debian Bug report #925626,
regarding acpi-support: ftbfs with GCC-9
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.)


-- 
925626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:acpi-support
Version: 0.142-8
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/acpi-support_0.142-8_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

dpkg-buildpackage: info: source package acpi-support
dpkg-buildpackage: info: source version 0.142-8
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael Meskes 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with quilt,systemd
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use)
make -C debian/addons/fakekey clean
make[2]: Entering directory '/<>/debian/addons/fakekey'
rm -f acpi_fakekey acpi_fakekeyd
make[2]: Leaving directory '/<>/debian/addons/fakekey'
make[1]: Leaving directory '/<>'
   dh_quilt_unpatch
No patch removed
   dh_clean
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
 debian/rules build-arch
dh build-arch --with quilt,systemd
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_quilt_patch -a
Applying patch asus-wireless.sh.diff
patching file asus-wireless.sh

Applying patch ibm.diff
patching file ibm-wireless.sh

Applying patch key-constants.diff
patching file key-constants

Applying patch state-funcs.diff
patching file lib/state-funcs

Applying patch undock.sh.diff
patching file undock.sh

Now at patch undock.sh.diff
   dh_update_autotools_config -a
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
make -C debian/addons/fakekey all
make[2]: Entering directory '/<>/debian/addons/fakekey'
gcc -Wall -g -O2 -fdebug-prefix-map=/<>/debian/addons/fakekey=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -o acpi_fakekey acpi_fakekey.c
gcc -Wall -g -O2 -fdebug-prefix-map=/<>/debian/addons/fakekey=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -lsystemd -o acpi_fakekeyd acpi_fakekeyd.c
In file included from /usr/include/unistd.h:25,
 from acpi_fakekeyd.c:2:
/usr/include/features.h:184:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  184 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
/usr/bin/ld: /tmp/ccPiAyCW.o: in function `create_fifo':
./acpi_fakekeyd.c:22: undefined reference to `sd_listen_fds'
/usr/bin/ld: ./acpi_fakekeyd.c:27: undefined reference to `sd_is_fifo'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:7: acpi_fakekeyd] Error 1
make[2]: Leaving directory 

Bug#925819: rrep ftbfs: patch available

[Arno Onken]

Dear Matthias,

Thank you for reporting the rrep ftbfs with GCC-9.

The build failed because GCC-9 has the --as-needed flag enabled by default and 
misses libacl references present in libgnu.a.  Simply reordering the LDADD 
libraries in Makefile.am fixes this bug.

I uploaded rrep_1.3.6-2 to mentors:
https://mentors.debian.net/package/rrep
The changeset is very small and I am looking for a sponsor.

Regards,
Arno

Processed: tagging 934951, tagging 935041, found 935016 in 12.5.1, tagging 895037, tagging 895038

[Debian Bug Tracking System]

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

> tags 934951 + sid bullseye
Bug #934951 [src:elasticsearch-curator] elasticsearch-curator: build-dependency 
python-elasticsearch (< 6.0.0) unsatisfiable in sid
Added tag(s) bullseye and sid.
> tags 935041 + sid bullseye
Bug #935041 [src:mh-e] mh-e: unbuildable in testing due to missing B-D
Added tag(s) sid and bullseye.
> found 935016 12.5.1
Bug #935016 [debhelper] pkg-js-tools: An unannounced change in "debhelper" 
breaks pkg-js-tools
Marked as found in versions debhelper/12.5.1.
> tags 895037 - buster buster-ignore
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; 
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Removed tag(s) buster and buster-ignore.
> tags 895038 - buster buster-ignore
Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to 
libayatana-indicator instead
Removed tag(s) buster-ignore and buster.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 921694 https://github.com/aircrack-ng/mdk4/issues/38
Bug #921694 [src:mdk4] mdk4: FTBFS randomly when built in parallel (undefined 
reference to `getFrequencyFromChannel')
Set Bug forwarded-to-address to 'https://github.com/aircrack-ng/mdk4/issues/38'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#849862: kmidimon needs updaing to latest libdrumstick (1.0.2-1)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #849862 [kmidimon] kmidimon needs updaing to latest libdrumstick (1.0.2-1)
Severity set to 'serious' from 'wishlist'

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

Bug#875180: [scribus] Future Qt4 removal from Buster

[Mattia Rizzolo]

On Mon, Apr 09, 2018 at 08:13:45AM +0200, intrigeri wrote:
> Lisandro Damián Nicanor Pérez Meyer:
> > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> 
> It looks like the upstream 1.5.x development branch is based on Qt5.
> The 1.5.3 release notes say it's now stable enough to be used for
> actual workflows.

FTR of this bug, I've heard voices that 1.5.x might turn into a stable
1.6.0 within half a year.  I don't know how actually far we are from
that, but it might be true :)

Guess bullseye will stay without a scribus for a few months then…

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#875026: marked as pending in libquazip

[Andreas Tille]

Control: tag -1 pending

Hello,

Bug #875026 in libquazip 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/med-team/libquazip/commit/9bc9ff825028c54bad04b419c923166d2d011a0c


Removed obsolete build dependency libqt4-dev (Closes: #875026)
* Switched to debhelper-compat (=12)
* Removed not needed build dependency d-shlibs
* Bumped Standards-Version to 4.4.0, no changes needed
* Removed Qt4 packages from control and fixed the description of Qt5 packages
* Modified debian/rules to fit Qt5 only builds
* Don't provide statically linked files anymore
* Added the now needed install files
* Fixed symbols for gcc-9
* Added Build-Depends-Package field to symbols
* Removed superfluous Section entry from libquazip5-1
* Removed obsolete libquazip5-headers package, combined with -dev,
  -dev is useless without -headers and vice versa - and it doesn't hurt
  if a cmake file is installed in non-cmake builds. Set Breaks and Replaces.
* Added myself to copyright
* Added myself to uploaders


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/875026

Processed: Bug#875026 marked as pending in libquazip

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #875026 [src:libquazip] [libquazip] Future Qt4 removal from Buster
Added tag(s) pending.

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

Processed: Re: Bug#935000: intel-media-driver-non-free: FTBFS in sid (gcc-9)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #935000 [src:intel-media-driver-non-free] intel-media-driver-non-free: 
FTBFS in sid (gcc-9)
Severity set to 'normal' from 'serious'

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

Bug#935000: intel-media-driver-non-free: FTBFS in sid (gcc-9)

[Sebastian Ramacher]

Control: severity -1 normal

On 2019-08-17 23:57:11, Gianfranco Costamagna wrote:
> Source: intel-media-driver-non-free
> Version: 19.2.1+ds1-1
> Severity: serious
> 
> Hello, your package FTBFS with default gcc-9 because of
> cc1plus: error: ???-Werror=??? argument 
> ???-Werror=implicit-function-declaration??? is not valid for C++ [-Werror]

Did you check that this actually fails in the same way? I get

| cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
is not valid for C++

and it builds just fine. Downgrading accordingly.

> Please also make the testsuite not run on Ubuntu builders, for some reasons 
> builders gets stuck when running it

Instead of hiding the issue, shouldn't somebody on the Ubuntu side
investigate why that happens?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#934992: network-manager breaks systemd autopkgtest

[Paul Gevers]

Hi Michael,

You already got a bit further, but nevertheless.

On 18-08-2019 18:39, Michael Biebl wrote:
> Paul, which lxc version was used to run the autopkgtest tests?

We are currently running stretch on 11/12 of the workers and buster on
the other one (number 12).

> Is it possible to get access to a system with the exact same
> configuration as on ci.debian.net so one can interactively debug this issue?

Is this still needed? It can be done of course.

Paul

FYI, we filed a regression bug against lxc the other day, so yes, there
is an issue with the latest one in sid/bullseye:
https://bugs.debian.org/934983 lxc: lxc-attach loses exit code of
executed command



signature.asc
Description: OpenPGP digital signature

Bug#934976: defendguin-data: Bill Gates images used, questionable copyright status

[Bill Kendrick]

Hey Christian, et al,

Yeah, the sounds probably included a lot of samples from the real
Defender arcade game, probably taken from a sound archive FTP site,
back in the day.

The Bill Gates image was based on art from Slashdot; and yeah,
somehow, they gave me permission to use it.

I've been meaning to redo Defendguin some day -- basically an art/sound
refresh.

When I do, I'll make sure to let you all know.  For now, yeah, drop it.

Thanks!

-bill!


On Sat, Aug 17, 2019 at 07:50:21PM +0200, Christian T. Steigies wrote:
> Hi Bill,
> On Sat, Aug 17, 2019 at 05:15:08PM +0200, Fabio Pesari wrote:
> > Package: defendguin-data
> > Version: 0.0.12-7
> > Severity: serious
> > Tags: upstream
> > Justification: Policy 2.3
> > 
> > Dear Maintainer,
> > 
> > defendguin-data uses real-life photographs of Bill Gates (from the 70s, I
> > believe) in the defendguin/images/evilbill directory. I doubt those are
> > released under a free license.
> > 
> > The audio files in the defendguin/sounds directory are also suspicious, they
> > sound like they have been sampled from sources whose copyright status isn't
> > clear.
> > 
> > For this reason, I think these files should not be distributed by Debian.
> > 
> > 
> > 
> > -- System Information:
> > Debian Release: bullseye/sid
> >   APT prefers testing
> >   APT policy: (500, 'testing')
> > Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
> > (charmap=UTF-8)
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> > 
> > -- no debconf information
> 
> In the AUTHORS file you write "used with permission" for the "photo".
> I don't see this mentioned under the Sound Effects. Do you think there is a
> copyright problem or not? If there is a problem, I would probably just drop
> the package from Debian, I don't think its worth the effort to create new
> images and sound files for this old package.
> 
> thanks,
> Christian
> 

-- 
-bill!
Sent from my computer

Bug#875138: Can we remove qsapecng?

[Lisandro Damián Nicanor Pérez Meyer]

Hi Simone! qsapecng seems to be the last package using qwt along Qt4.
I checked and upstream seems to have stopped it's development at least
a couple of years ago. Would it be ok for you if I proceed to remove
this package from Debian? In this way we can prevent qwt from being
removed from testing.

Thanks, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Processed: Blocking

[Debian Bug Tracking System]

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

> block 875165 by 875138
Bug #875165 [src:qwt] [qwt] Future Qt4 removal from Buster
875165 was blocked by: 875135 875138 875065 875083 874900
875165 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #875165 to the same blocks 
previously set
> thanks
Stopping processing here.

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

Bug#875165: Qt4 rdeps

[Lisandro Damián Nicanor Pérez Meyer]

Control: block -1 875138

Hi! I have been searching for qwt's qt4 rdeps using dak. From the list below the
only package that seems to be using qt4's qwtis

  https://packages.debian.org/source/sid/qsapecng

I think once that package is solved we can proceed with the removal of the Qt4
part of qwt.

The list:

ssh mirror.ftp-master.debian.org "dak rm -Rn qwt"
Will remove the following packages from unstable:

libqwt-dev |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libqwt-doc |6.1.4-1 | all
libqwt-headers |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libqwt-qt5-6 |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libqwt-qt5-dev |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libqwt6abi1 |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libqwtmathml-dev |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libqwtmathml-qt5-6 |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libqwtmathml-qt5-dev |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libqwtmathml6abi1 |6.1.4-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
   qwt |6.1.4-1 | source

Maintainer: Gudjon I. Gudjonsson 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
aseba: aseba [amd64 arm64 i386 mips mips64el mipsel ppc64el s390x]
caneda: caneda
gazebo: gazebo9 [amd64 i386]
gazebo9-plugin-base [amd64 i386]
libgazebo9 [amd64 i386]
libgazebo9-dev [amd64 i386]
gnuradio: gnuradio
  libgnuradio-qtgui3.7.13
  libgnuradio-qtgui3.8.0
gr-radar: gr-radar
  libgnuradio-radar3.7
linssid: linssid
nlkt: nlkt
odin: mitools
  odin
otb: libotb-dev [amd64 i386]
 libotbmonteverdigui-6.6-1 [amd64 i386]
pyqt-qwt: python3-pyqt5.qwt
qgis: libqgis-app3.4.10
  libqgis-customwidgets
  libqgis-dev
  libqgis-gui3.4.10
  libqgisgrass7-3.4.10
  python3-qgis
  qgis
  qgis-plugin-grass
  qgis-provider-grass
  qgis-providers
qsapecng: qsapecng
qstopmotion: qstopmotion

# Broken Build-Depends:
aseba: libqwt-qt5-dev
caneda: libqwt-qt5-dev
gazebo: libqwt-qt5-dev
gnuradio: libqwt-qt5-dev
gr-radar: libqwt-qt5-dev
libterralib: libqwt-qt5-dev
linssid: libqwt-headers |libqwt-dev
 libqwt-qt5-6
mozc: libqwt-qt5-dev
nlkt: libqwt-qt5-dev
odin: libqwt-dev
otb: libqwt-qt5-dev
pyqt-qwt: libqwt-qt5-dev (>= 6.1.3)
qgis: libqwt-qt5-dev
qsapecng: libqwt-dev (>= 6.1.0)
qstopmotion: libqwt-qt5-dev
wsjtx: libqwt-dev
xygrib: libqwt-qt5-dev (>= 6.1.2)

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 921542 5.0.1-1~exp1
Bug #921542 {Done: Ben Hutchings } [src:linux] tc qdisc 
kernel crash
Marked as fixed in versions linux/5.0.1-1~exp1.
> thanks
Stopping processing here.

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

Bug#934992: network-manager breaks systemd autopkgtest

[Michael Biebl]

Control: reassign -1 systemd 241-7

Am 18.08.19 um 18:39 schrieb Michael Biebl:
> Am 18.08.19 um 17:18 schrieb Michael Biebl:

>> I've created an LXC container via
>> autopkgtest-build-lxc debian bullseye
>> and got the same autopkgtest failure using this container.
>> So this looks like a regression that was introduced outside of
>> systemd/network-manager
>>
>> I've also tried a qemu backed autopkgtest run and there the tests
>> completed successfully.
>> Might this be a regression introduced by LXC itself (and or in
>> combination with a newer kernel?)
> 
> My test system is running unstable, i.e. I was using
> lxc_1:3.1.0+really3.0.4-1
> After downgrading lxc to 1:3.1.0+really3.0.3-8, boot-smoke did
> successfully pass again.
> 
> Paul, which lxc version was used to run the autopkgtest tests?
> 
> Is it possible to get access to a system with the exact same
> configuration as on ci.debian.net so one can interactively debug this issue?

Dear lxc maintainers, sorry for the noise.
Afaics this is actually a bug in the boot-smoke autopkgtest and not
related to lxc, so tentatively reassigning to systemd.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: network-manager breaks systemd autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd 241-7
Bug #934992 [src:network-manager, src:systemd] network-manager breaks systemd 
autopkgtest
Bug reassigned from package 'src:network-manager, src:systemd' to 'systemd'.
No longer marked as found in versions systemd/241-7, network-manager/1.19.90-2, 
and network-manager/1.20.0-1.
Ignoring request to alter fixed versions of bug #934992 to the same values 
previously set
Bug #934992 [systemd] network-manager breaks systemd autopkgtest
Marked as found in versions systemd/241-7.

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

Bug#934992: [Pkg-utopia-maintainers] Bug#934992: network-manager breaks systemd autopkgtest

[Michael Biebl]

Am 18.08.19 um 13:01 schrieb Andreas Henriksson:
> So apparently polkitd is not running after the first reboot attempt. I
> have no clue why or how to investigate why so I guess I'll leave that to
> the professionals.
> 
> Maybe it would be useful to change the test to do
> "pidof polkitd || fail" to gather more autopkgtest artifacts information
> for debugging purposes? i.e. the boot-smoke-journal.txt file.

Hm, I have to say I don't quite get the check for
"pidof polkitd" either.

polkit.service is a dbus activated service, i.e. it is started on demand
and not statically during boot.
So boot-smoke was relying on "something" triggering the start of
polkit.service.

Seems that older network manager versions did trigger the start of
polkit.service, so this test only worked "by accident".
See the attached bullseye.txt and sid.txt which confirm this suspicion.

Martin, do you remember why you chose to check for "pidof polkitd"?
This seems rather unreliable when we rely on "some other component" to
trigger it's start.
Shouldn't we rather check for a service which is installed by the test
and hooked into multi-user.target, like "pidof NetworkManager"?


Afaics, this looks like a bug in boot-smoke to me for making wrong
assumption. I would like Martin's feedback on this though.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
root@autopkgtest-bullseye:/tmp/autopkgtest-lxc.qoaowm2l/downtmp/build.Ira/src# 
systemctl status polkit.service NetworkManager.service
* polkit.service - Authorization Manager
   Loaded: loaded (/lib/systemd/system/polkit.service; static; vendor preset: 
enabled)
   Active: inactive (dead)
 Docs: man:polkit(8)

* NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead) since Sun 2019-08-18 17:16:00 UTC; 11s ago
 Docs: man:NetworkManager(8)
  Process: 63 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, 
status=0/SUCCESS)
 Main PID: 63 (code=exited, status=0/SUCCESS)

root@autopkgtest-bullseye:/tmp/autopkgtest-lxc.qoaowm2l/downtmp/build.Ira/src# 
systemctl start NetworkManager.service

root@autopkgtest-bullseye:/tmp/autopkgtest-lxc.qoaowm2l/downtmp/build.Ira/src# 
systemctl status polkit.service NetworkManager.service
* polkit.service - Authorization Manager
   Loaded: loaded (/lib/systemd/system/polkit.service; static; vendor preset: 
enabled)
   Active: active (running) since Sun 2019-08-18 17:16:25 UTC; 1s ago
 Docs: man:polkit(8)
 Main PID: 225 (polkitd)
Tasks: 4 (limit: 4915)
   Memory: 3.4M
   CGroup: /system.slice/polkit.service
   `-225 /usr/lib/policykit-1/polkitd --no-debug

Aug 18 17:16:25 autopkgtest-bullseye systemd[1]: Starting Authorization 
Manager...
Aug 18 17:16:25 autopkgtest-bullseye polkitd[225]: started daemon version 0.105 
using authority implementation `local' version `0.105'
Aug 18 17:16:25 autopkgtest-bullseye systemd[1]: Started Authorization Manager.

* NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Sun 2019-08-18 17:16:24 UTC; 1s ago
 Docs: man:NetworkManager(8)
 Main PID: 215 (NetworkManager)
Tasks: 4 (limit: 4915)
   Memory: 2.9M
   CGroup: /system.slice/NetworkManager.service
   `-215 /usr/sbin/NetworkManager --no-daemon

Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4084] Loaded device plugin: NMAtmManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.1
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4101] Loaded device plugin: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4106] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4123] Loaded device plugin: NMTeamFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4133] device (lo): carrier: link connected
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4137] manager: (lo): new Generic device 
(/org/freedesktop/NetworkManager/Devices/1)
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4144] device (eth0): carrier: link connected
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4147] manager: (eth0): new Veth device 
(/org/freedesktop/NetworkManager/Devices/2)
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4154] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 18 17:16:25 autopkgtest-bullseye NetworkManager[215]:   
[1566148585.4196] manager: startup complete

root@autopkgtest-bullseye:/tmp/autopkgtest-lxc.qoaowm2l/downtmp/build.Ira/src# 
apt-cache 

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 921542 5.0
Bug #921542 {Done: Ben Hutchings } [src:linux] tc qdisc 
kernel crash
The source 'linux' and version '5.0' do not appear to match any binary packages
Marked as fixed in versions linux/5.0.
> thanks
Stopping processing here.

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

Bug#921542: Close this

[Jiri Palecek]

fixed 921542 src:linux/5.0

thanks


Hello

the patch fixing this problem has been included in 5.0, so it should
probably be closed.


    Jiri Palecek

Bug#875071: closed by Martin Quinson (ns3 does not actually depends on Qt4)

[Lisandro Damián Nicanor Pérez Meyer]

Hi Martin!

On Sun, 18 Aug 2019 at 13:45, Debian Bug Tracking System
 wrote:
[snip]
> -- Forwarded message --
> From: Martin Quinson 
> To: 875071-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 18 Aug 2019 18:33:58 +0200
> Subject: ns3 does not actually depends on Qt4
> Hello,
>
> I fail to see why this bug was ever open. This is the netanim part of
> ns3 that (used to) depends on Qt4.
>
> According to the changelog and git logs, I built netanim from the ns3
> sources for 3 days only: from v3.25+dfsg2-2 (released 17 Apr 2016) to
> v3.25+dfsg2-3 (released 20 Apr 2016). I removed it right away because
> of #821369 (ns3 and netanim: error when trying to install together).
>
> This bug, #875071, was opened against ns3 source package v3.26+dfsg-1
> on 9 Sep 2017. I did not close it before because we need to
> re-integrate netanim at some point since both ns3 and netanim are
> built (partially) from the same sources. This is still to be done,
> but that's not a reason to leave #875071 open, thus closing.

Werid, but good to know we have one less package to go :-)

Thanks!

--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#875071: marked as done ([ns3] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 18 Aug 2019 18:33:58 +0200
with message-id <20190818163358.GB21960@nouzonket>
and subject line ns3 does not actually depends on Qt4
has caused the Debian Bug report #875071,
regarding [ns3] Future Qt4 removal from Buster
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.)


-- 
875071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ns3
Version: 3.26+dfsg-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Hello,

I fail to see why this bug was ever open. This is the netanim part of
ns3 that (used to) depends on Qt4. 

According to the changelog and git logs, I built netanim from the ns3
sources for 3 days only: from v3.25+dfsg2-2 (released 17 Apr 2016) to
v3.25+dfsg2-3 (released 20 Apr 2016). I removed it right away because
of #821369 (ns3 and netanim: error when trying to install together).

This bug, #875071, was opened against ns3 source package v3.26+dfsg-1
on 9 Sep 2017. I did not close it before because we need to
re-integrate netanim at some point since both ns3 and netanim are
built (partially) from the same sources. This is still to be done, 
but that's not a reason to leave #875071 open, thus closing.

Sorry for the delay,
Mt.

-- 
I don't suffer from Insanity, I enjoy every minute of it...


signature.asc
Description: PGP signature
--- End Message ---

Bug#934992: network-manager breaks systemd autopkgtest

[Michael Biebl]

Am 18.08.19 um 17:18 schrieb Michael Biebl:
> Am 17.08.19 um 21:23 schrieb Paul Gevers:
>> Source: network-manager, systemd
>> Control: found -1 network-manager/1.20.0-1
>> Control: found -1 network-manager/1.19.90-2
>> Control: found -1 systemd/241-7
>> Severity: serious
>> X-Debbugs-CC: debian...@lists.debian.org
>> User: debian...@lists.debian.org
>> Usertags: breaks needs-update
>>
>> Dear maintainers,
>>
>> With a recent upload of network-manager the autopkgtest of systemd fails
>> in testing when that autopkgtest is run with the binary packages of
>> network-manager from unstable. It passes when run with only packages
>> from testing. In tabular form:
>>passfail
>> network-managerfrom testing1.20.0-1
>> systemdfrom testing241-7
>> versioned deps [0] from testingfrom unstable
>> all others from testingfrom testing
>>
>> I copied some of the output at the bottom of this report. (It doesn't
>> show anything that isn't there in a successful run, normally it continues).
>>
>> Currently this regression is blocking the migration of network-manager
>> to testing [1]. Due to the nature of this issue, I filed this bug report
>> against both packages. Can you please investigate the situation and
>> reassign the bug to the right package?
>>
>> More information about this bug and the reason for filing it can be found on
>> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>>
>> Paul
>>
>> [0] You can see what packages were added from the second line of the log
>> file quoted below. The migration software adds source package from
>> unstable to the list if they are needed to install packages from
>> network-manager/1.20.0-1. I.e. due to versioned dependencies or
>> breaks/conflicts.
>> [1] https://qa.debian.org/excuses.php?package=network-manager
>>
>> https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/2754701/log.gz
>>
>> autopkgtest [12:20:19]: test boot-smoke: [---
>> reboot #0
>> bash: line 1:  6405 Killed
>> /tmp/autopkgtest-lxc.d0a1dm24/downtmp/build.Yzc/src/debian/tests/boot-smoke
>> 2> >(tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stderr >&2)
 (tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stdout)
>> autopkgtest [12:20:20]: test process requested reboot with marker 1
>> checking for failed unmounts for user systemd
>> checking for connection timeouts
>> checking that polkitd runs
>> autopkgtest [12:20:31]: test boot-smoke: ---]
>>
> 
> I've created an LXC container via
> autopkgtest-build-lxc debian bullseye
> and got the same autopkgtest failure using this container.
> So this looks like a regression that was introduced outside of
> systemd/network-manager
> 
> I've also tried a qemu backed autopkgtest run and there the tests
> completed successfully.
> Might this be a regression introduced by LXC itself (and or in
> combination with a newer kernel?)

My test system is running unstable, i.e. I was using
lxc_1:3.1.0+really3.0.4-1
After downgrading lxc to 1:3.1.0+really3.0.3-8, boot-smoke did
successfully pass again.

Paul, which lxc version was used to run the autopkgtest tests?

Is it possible to get access to a system with the exact same
configuration as on ci.debian.net so one can interactively debug this issue?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#933002: docker.io: CVE-2019-13139

[Adam D. Barratt]

On Sun, 2019-08-18 at 16:56 +0200, Arnaud Rebillout wrote:
> * The bug you want to fix in stable must be fixed in unstable
>   already (and not waiting in NEW or the delayed queue)
> 
> My issue with this particular bug (#933002) is that for now,
> docker.io  doesn't build in unstable. It will take a while before it
> builds again,  as there was changes in the dependency tree.
> 
> On the other hand, fixing this bug in stable is just a matter of 
> importing the patch from upstream and rebuilding the package.
> 
> So how am I supposed to handle that? Waiting for docker.io to be
> fixed  and built again in unstable will delay the fix in stable for
> weeks, I  don't think it's a good option.

Nevertheless, that is the case I'm afraid. Updates to stable via
proposed-updates are not appropriate for urgent security updates - that
is what the security archive is for.

Looking at https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=docker.io
, there doesn't appear to be a bug filed for the build failure, so
there's no indication of what the issues are, nor what needs to be done
to fix them.

Regards,

Adam

Bug#934992: network-manager breaks systemd autopkgtest

[Michael Biebl]

Am 17.08.19 um 21:23 schrieb Paul Gevers:
> Source: network-manager, systemd
> Control: found -1 network-manager/1.20.0-1
> Control: found -1 network-manager/1.19.90-2
> Control: found -1 systemd/241-7
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
> 
> Dear maintainers,
> 
> With a recent upload of network-manager the autopkgtest of systemd fails
> in testing when that autopkgtest is run with the binary packages of
> network-manager from unstable. It passes when run with only packages
> from testing. In tabular form:
>passfail
> network-managerfrom testing1.20.0-1
> systemdfrom testing241-7
> versioned deps [0] from testingfrom unstable
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report. (It doesn't
> show anything that isn't there in a successful run, normally it continues).
> 
> Currently this regression is blocking the migration of network-manager
> to testing [1]. Due to the nature of this issue, I filed this bug report
> against both packages. Can you please investigate the situation and
> reassign the bug to the right package?
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [0] You can see what packages were added from the second line of the log
> file quoted below. The migration software adds source package from
> unstable to the list if they are needed to install packages from
> network-manager/1.20.0-1. I.e. due to versioned dependencies or
> breaks/conflicts.
> [1] https://qa.debian.org/excuses.php?package=network-manager
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/2754701/log.gz
> 
> autopkgtest [12:20:19]: test boot-smoke: [---
> reboot #0
> bash: line 1:  6405 Killed
> /tmp/autopkgtest-lxc.d0a1dm24/downtmp/build.Yzc/src/debian/tests/boot-smoke
> 2> >(tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stderr >&2)
>>> (tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stdout)
> autopkgtest [12:20:20]: test process requested reboot with marker 1
> checking for failed unmounts for user systemd
> checking for connection timeouts
> checking that polkitd runs
> autopkgtest [12:20:31]: test boot-smoke: ---]
> 

I've created an LXC container via
autopkgtest-build-lxc debian bullseye
and got the same autopkgtest failure using this container.
So this looks like a regression that was introduced outside of
systemd/network-manager

I've also tried a qemu backed autopkgtest run and there the tests
completed successfully.
Might this be a regression introduced by LXC itself (and or in
combination with a newer kernel?)

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#933002: docker.io: CVE-2019-13139

[Arnaud Rebillout]

  Dear Release Team,

I'm new to the process of uploading to stable, I need your guidance on 
that one.


From the buster announce:

   * The bug you want to fix in stable must be fixed in unstable
 already (and not waiting in NEW or the delayed queue)

My issue with this particular bug (#933002) is that for now, docker.io 
doesn't build in unstable. It will take a while before it builds again, 
as there was changes in the dependency tree.


On the other hand, fixing this bug in stable is just a matter of 
importing the patch from upstream and rebuilding the package.


So how am I supposed to handle that? Waiting for docker.io to be fixed 
and built again in unstable will delay the fix in stable for weeks, I 
don't think it's a good option.


Best regards,

  Arnaud

Bug#932781: marked as done (gnome-shell crashed on laptop lid close)

[Debian Bug Tracking System]

Your message dated Sun, 18 Aug 2019 15:18:32 +0100
with message-id <20190818141832.ga15...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#932428, Bug#932767, Bug#932781: gnome-shell crashes 
involving monitor changes
has caused the Debian Bug report #932781,
regarding gnome-shell crashed on laptop lid close
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.)


-- 
932781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.30.2-9
Severity: important

Dear Maintainer,

Closing laptop lid normally puts laptop sleep and I get back my session on 
reopen. But after recent update
I see that I get logged out and closer inspection revealed that gnome-shell is 
crashing with following error

[  746.169795] gnome-shell[13847]: segfault at 2300022 ip 7f3718787e04 
sp 7ffd56a0f0b0 error 4 in libwayland-server.so.0.1.0[7f3718787000+7000]

I managed to get the coredump and backtrace of the same. I'm attaching it with 
this bug report.

Cheers,
Vasudev


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, arm64

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evolution-data-server3.30.5-1.1
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-atspi-2.0 2.30.0-7
ii  gir1.2-freedesktop   1.58.3-2
ii  gir1.2-gcr-3 3.28.1-1
ii  gir1.2-gdesktopenums-3.0 3.33.1-1
ii  gir1.2-gdm-1.0   3.30.2-3
ii  gir1.2-geoclue-2.0   2.5.3-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gnomebluetooth-1.03.28.2-3
ii  gir1.2-gnomedesktop-3.0  3.30.2.1-2
ii  gir1.2-gtk-3.0   3.24.10-1
ii  gir1.2-gweather-3.0  3.28.3-1
ii  gir1.2-ibus-1.0  1.5.19-4+b1
ii  gir1.2-mutter-3  3.30.2-7
ii  gir1.2-nm-1.01.18.0-3
ii  gir1.2-nma-1.0   1.8.22-2
ii  gir1.2-pango-1.0 1.42.4-6
ii  gir1.2-polkit-1.00.105-25
ii  gir1.2-rsvg-2.0  2.44.10-2.1
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-upowerglib-1.00.99.10-1
ii  gjs  1.54.3-1+b1
ii  gnome-backgrounds3.30.0-1
ii  gnome-settings-daemon3.30.2-3
ii  gnome-shell-common   3.30.2-9
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcanberra-gtk3-0   0.30-7
ii  libcanberra0 0.30-7
ii  libcroco30.6.12-3
ii  libecal-1.2-19   3.30.5-1.1
ii  libedataserver-1.2-233.30.5-1.1
ii  libgcr-base-3-1  3.28.1-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgirepository-1.0-11.58.3-2
ii  libgjs0g 1.54.3-1+b1
ii  libglib2.0-0 2.60.5-1
ii  libglib2.0-bin   2.60.5-1
ii  libgstreamer1.0-01.16.0-2
ii  libgtk-3-0   3.24.10-1
ii  libical3 3.0.5-1
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-3-03.30.2-7
ii  libnm0   1.18.0-3
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  

Bug#934962: syncthing: FTBFS with 'build cache is disabled by GOCACHE=off, but required as of Go 1.12'

[Arnaud Rebillout]

On 8/17/19 1:02 PM, Bruno Kleinert wrote:

[…]
cd _build/src/github.com/syncthing/syncthing && go run script/genassets.go gui

lib/auto/gui.files.go

build cache is disabled by GOCACHE=off, but required as of Go 1.12
make[1]: *** [debian/rules:54: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:34: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
[…]


You must set GOCACHE to a directory inside the build directory. This is 
needed since Go 1.12, as the error message hints.


For an example see: 
https://salsa.debian.org/go-team/packages/golang-github-docker-docker-credential-helpers/commit/397ff4dd01216ede71468ccffd7b2d25078a5ff3


Cheers,

  Arnaud

Bug#935042: Program phones home by default

[Robie Basak]

Package: lynis
Version: 2.6.2-1
Severity: serious
Justification: privacy leak

By default, this program appears to make a DNS query to
lynis-latest-version.cisofy.com. thus leaking information about the
system and the fact that the user is running an audit. This is
particularly egregious in the case of a security audit tool, as it
reveals to observers that the sysadmin performing the audit may be
concerned about the system's security. Note that this information is
being revealed both to whoever controls "cisofy.com" and also to any
network observers as DNS queries are still typically unencrypted.

I believe that Debian has held the long standing philosophy that this
kind of privacy leak must not be permitted by default. Debian users
generally assume that the package maintainer has taken care of this kind
of thing, and that it is safe to assume that there is no information
being exfiltrated from the system without the user's explicit
permission.

Please patch the default configuration so that there is no privacy leak.

If this issue affects existing stable releases, I suggest that a stable
update is also necessary, or perhaps even a security update.


signature.asc
Description: PGP signature

Bug#935041: mh-e: unbuildable in testing due to missing B-D

[Esa Peuha]

Source: mh-e
Version: 8.5-2.1
Severity: serious

Currently mh-e build-depends on emacs25-nox | emacs25 | emacs24 but
none of these packages exist in testing. This makes mh-e unbuildable.
Please build-depend on emacs-nox | emacs-gtk instead.

Processed: Re: Fwd: [Pkg-utopia-maintainers] Bug#933930: Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

[Debian Bug Tracking System]

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

> retitle 933930 network-manager: Ethernet connection fails with internal DHCP 
> client if DHCPNAK from alternate server comes first
Bug #933930 [network-manager] network-manager: Ethernet connection sometimes 
fails with internal dhcp client
Changed Bug title to 'network-manager: Ethernet connection fails with internal 
DHCP client if DHCPNAK from alternate server comes first' from 
'network-manager: Ethernet connection sometimes fails with internal dhcp 
client'.
>
End of message, stopping processing here.

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

Bug#935037: nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516

[Salvatore Bonaccorso]

Source: nginx
Version: 1.14.2-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1.10.3-1+deb9u2
Control: found -1 1.10.3-1

Hi,

The following vulnerabilities were published for nginx.

CVE-2019-9511[0]:
| Some HTTP/2 implementations are vulnerable to window size manipulation
| and stream prioritization manipulation, potentially leading to a
| denial of service. The attacker requests a large amount of data from a
| specified resource over multiple streams. They manipulate window size
| and stream priority to force the server to queue the data in 1-byte
| chunks. Depending on how efficiently this data is queued, this can
| consume excess CPU, memory, or both.


CVE-2019-9513[1]:
| Some HTTP/2 implementations are vulnerable to resource loops,
| potentially leading to a denial of service. The attacker creates
| multiple request streams and continually shuffles the priority of the
| streams in a way that causes substantial churn to the priority tree.
| This can consume excess CPU.


CVE-2019-9516[2]:
| Some HTTP/2 implementations are vulnerable to a header leak,
| potentially leading to a denial of service. The attacker sends a
| stream of headers with a 0-length header name and 0-length header
| value, optionally Huffman encoded into 1-byte or greater headers. Some
| implementations allocate memory for these headers and keep the
| allocation alive until the session dies. This can consume excess
| memory.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-9511
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9511

https://github.com/nginx/nginx/commit/a987f81dd19210bc30b62591db331e31d3d74089
[1] https://security-tracker.debian.org/tracker/CVE-2019-9513
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9513

https://github.com/nginx/nginx/commit/5ae726912654da10a9a81b2c8436829f3e94f69f
[2] https://security-tracker.debian.org/tracker/CVE-2019-9516
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9516

https://github.com/nginx/nginx/commit/6dfbc8b1c2116f362bb871efebbf9df576738e89
[3] 
https://www.nginx.com/blog/nginx-updates-mitigate-august-2019-http-2-vulnerabilities/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

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

Processed: nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.10.3-1+deb9u2
Bug #935037 [src:nginx] nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516
Marked as found in versions nginx/1.10.3-1+deb9u2.
> found -1 1.10.3-1
Bug #935037 [src:nginx] nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516
Marked as found in versions nginx/1.10.3-1.

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

Bug#934992: network-manager breaks systemd autopkgtest

[Andreas Henriksson]

Hi,

I had a quick look and hoping my incomplete findings might be helpful...

On Sat, Aug 17, 2019 at 09:23:17PM +0200, Paul Gevers wrote:
[...]
> With a recent upload of network-manager the autopkgtest of systemd fails
> in testing when that autopkgtest is run with the binary packages of
> network-manager from unstable.
[...]

>From the autopkgtest log:

<<
autopkgtest [12:20:19]: test boot-smoke: [---
reboot #0
bash: line 1:  6405 Killed  
/tmp/autopkgtest-lxc.d0a1dm24/downtmp/build.Yzc/src/debian/tests/boot-smoke 2> 
>(tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stderr >&2) > >(tee 
-a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stdout)
autopkgtest [12:20:20]: test process requested reboot with marker 1
checking for failed unmounts for user systemd
checking for connection timeouts
checking that polkitd runs
autopkgtest [12:20:31]: test boot-smoke: ---]
autopkgtest [12:20:32]: test boot-smoke:  - - - - - - - - - - results - - - - - 
- - - - -
boot-smoke   FAIL non-zero exit status 1
<<


Given the above above output I assume this is where we bail out (note:
script is 'set -e'):
https://sources.debian.org/src/systemd/241-7/debian/tests/boot-smoke/#L51
(Otherwise we should have seen the "checking that there are no running
jobs" output as well.)

So apparently polkitd is not running after the first reboot attempt. I
have no clue why or how to investigate why so I guess I'll leave that to
the professionals.

Maybe it would be useful to change the test to do
"pidof polkitd || fail" to gather more autopkgtest artifacts information
for debugging purposes? i.e. the boot-smoke-journal.txt file.

HTH

Regards,
Andreas Henriksson

Bug#935017: debhelper breaks strip-nondeterminism autopkgtest

[Sven Joachim]

Control: reassign -1 debhelper 12.5.1

On 2019-08-18 06:45 +, Niels Thykier wrote:

> Control: reassign -1 strip-nondeterminism
>
>
> On Sun, 18 Aug 2019 08:19:37 +0200 Paul Gevers  wrote:
>> Source: debhelper, strip-nondeterminism
>> Control: found -1 debhelper/12.5.1
>> Control: found -1 debhelper/12.5
>> Control: found -1 strip-nondeterminism/1.5.0-1
>> Severity: serious
>> X-Debbugs-CC: debian...@lists.debian.org
>> User: debian...@lists.debian.org
>> Usertags: breaks needs-update
>>
>> Dear maintainers,
>>
>> With a recent upload of debhelper the autopkgtest of
>> strip-nondeterminism fails in testing when that autopkgtest is run with
>> the binary packages of debhelper from unstable. It passes when run with
>> only packages from testing. In tabular form:
>>passfail
>> debhelper  from testing12.5.1
>> strip-nondeterminism   from testing1.5.0-1
>> all others from testingfrom testing
>>
>> I copied some of the output at the bottom of this report.
>>
>> Currently this regression is blocking the migration of debhelper to
>> testing [1]. Due to the nature of this issue, I filed this bug report
>> against both packages. Can you please investigate the situation and
>> reassign the bug to the right package?
>>
>> More information about this bug and the reason for filing it can be found on
>> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>>
>> Paul
>>
>> [1] https://qa.debian.org/excuses.php?package=debhelper
>>
>> https://ci.debian.net/data/autopkgtest/testing/amd64/s/strip-nondeterminism/2758965/log.gz
>>
>> 1..2
>> not ok 1 - bin/dh_strip_nondeterminism --help returns 255
>>
>> #   Failed test 'bin/dh_strip_nondeterminism --help returns 255'
>> #   at t/binaries.t line 42.
>> ok 2 - bin/strip-nondeterminism --help returns 0
>> # Looks like you failed 1 test of 2.
>>
>
> I cannot reproduce this locally in a sane way. For me, it returned 1
> before and after upgrading to debhelper/12.5.1 (from 12.4).  Digging in
> the tests, it looks like strip-nondeterminism is *not* testing the
> installed binaries[1].

This may be so, but the installed dh_strip-nondeterminism fails in the
same way:

,
| $ dh_strip_nondeterminism --help
| dh_strip_nondeterminism: "debian/control" not found. Are you sure you are in 
the correct directory?
`

The same error is seen with "dh --help" (which worked in 12.4, although
it is not documented) and "dh --list", which is supposed to work from
any directory.

Cheers,
   Sven

Processed: Re: Bug#935017: debhelper breaks strip-nondeterminism autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 debhelper 12.5.1
Bug #935017 [strip-nondeterminism] debhelper breaks strip-nondeterminism 
autopkgtest
Bug reassigned from package 'strip-nondeterminism' to 'debhelper'.
Ignoring request to alter found versions of bug #935017 to the same values 
previously set
Ignoring request to alter fixed versions of bug #935017 to the same values 
previously set
Bug #935017 [debhelper] debhelper breaks strip-nondeterminism autopkgtest
Marked as found in versions debhelper/12.5.1.

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

Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

[Antoine Amarilli]

Hi Chris,

Thanks for writing the patch! I tested it on
. For some reason it didn't
apply cleanly to debian/rules, but it did apply fine to xtrlock.c and I
manually added -DMULTITOUCH to debian/rules to enable it.

So, the patch works fine on my machine. All input from the touchscreen
seems to be blocked (in particular touching the touchscreen no longer
moves the mouse cursor with the lock icon).

However, I think I see a problem with the patch's design. If I
understand correctly, the patch makes xtrlock grab all devices
initially. But if the attacker plugs in a new device after xtrlock is
started (e.g., an USB multitouch trackpad), then it wouldn't be grabbed,
right?

I can't try out this exact scenario because I don't have such a USB
device, and I can't easily disconnect my laptop's touchscreen. However,
I have tried blocking the touchscreen by writing 0 to
/sys/bus/usb/devices/3-1.5/authorized (the touchscreen then disappears
from the output of xinput). If I run "sleep 10 ; echo 1 | sudo tee
authorized" in the background and run xtrlock (to simulate plugging in
the touchscreen after 10 seconds), then sure enough, once the
touchscreen is "plugged" it is not grabbed by xtrlock and the initial
problem still occurs.

Of course the patch is already a big improvement, but do you have any
idea about how to address this problem with new devices being plugged in
while xtrlock is running?

Best,

-- 
Antoine Amarilli


On Fri, Aug 16, 2019 at 05:46:07PM -0700, Chris Lamb wrote:
> Chris Lamb wrote:
> 
> > Patch attached that works for me on my Dell XPS 13
> 
> Antoine, does the patch attached to:
> 
>   https://bugs.debian.org/830726#43
> 
> … also work for you? If so, I will go ahead and upload.
> 
> 
> Best wishes,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org  chris-lamb.co.uk
>`-


signature.asc
Description: PGP signature

Processed: closing 875064

[Debian Bug Tracking System]

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

> # octomap switched to QT5
> close 875064 1.9.0+dfsg-2
Bug #875064 [src:octomap] [octomap] Future Qt4 removal from Buster
Marked as fixed in versions octomap/1.9.0+dfsg-2.
Bug #875064 [src:octomap] [octomap] Future Qt4 removal from Buster
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#934969: xfce4-power-manager FTBFS: undefined reference to `xfce_titled_dialog_new_with_mixed_buttons'

[Yves-Alexis Perez]

On Sat, 2019-08-17 at 07:53 +0200, Helmut Grohne wrote:
> xfce4-power-manager fails to build from source for every architecture on
> the buildds. A typical failure is:

Hi Helmut, thanks for the report. It seems that xfpm requires libxfe4ui 4.13
although that's not in configure.ac.

Xfce 4.14 upload should happen soon, we're waiting for the RT feedback on
xfconf/xfce4-panel transitions first. We can upload a new version with the
build-deps updated but that won't change much until libxfce4ui 4.14 is
uploaded anyway.

Regards,
-- 
Yves-Alexis

Processed: Re: noudeb build profile no longer working when building systemd

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #934999 [debhelper] noudeb build profile no longer working when building 
systemd
Severity set to 'serious' from 'normal'

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

Processed: found 926699 in 1

[Debian Bug Tracking System]

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

> found 926699 1
Bug #926699 [debootstrap,usrmerge] libc6-{i386,x32}: installing, removing, 
reinstalling in a --merged-usr system results in unmerged /lib{32,x32}
There is no source info for the package 'debootstrap' at version '1' with 
architecture ''
There is no source info for the package 'usrmerge' at version '1' with 
architecture ''
Unable to make a source version for version '1'
Marked as found in versions 1.
> thanks
Stopping processing here.

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

Bug#931809: gnome-shell-extension-multi-monitors: Error loading extension

[Daniel Baumann]

severity 931809 important
thanks

Hi,

the extension works for me, both on buster (16) and bullseye/sid (18).

lacking any responses from the maintainer, I'm taking the liberty now to
lowering the severity as this one bug report (which unreproducible to
me, at least) shouldn't block it from entering testing completly (and
thus making it possible for my "metapackage"-package to enter testing, too).

Regards,
Daniel

Processed: Re: gnome-shell-extension-multi-monitors: Error loading extension

[Debian Bug Tracking System]

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

> severity 931809 important
Bug #931809 [gnome-shell-extension-multi-monitors] 
gnome-shell-extension-multi-monitors: Error loading extension
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#875075: [openscenegraph] Future Qt4 removal from Buster

[Sebastiaan Couwenberg]

On Sat, 23 Sep 2017 11:47:59 +0200 "Manuel A. Fernandez Montecelo" wrote:
> This package will be removed after rdeps migrate to openscenegraph-3.4 or a 
> later version (which does support Qt5), or rdeps are removed, or if nothing 
> else, when the removal of Qt4 happens.
> 
> (We plan to poke rdeps withing a few months, we don't want this version 
> shipped in Buster).

The only remaining libopenscenegraph100v5 rdeps are opensurgsim & kido,
I wouldn't wait for them to stop using openscenegraph.

More problematic is that the libopenthreads packages are still only
provided by openscenegraph and not openscenegraph-3.4. Please stop
providing those packages from src:openscenegraph and build them from
src:openscenegraph-3.4 instead.

This RC bug affects all rdeps of openscenegraph-3.4 too because of that.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: debhelper breaks strip-nondeterminism autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 strip-nondeterminism
Bug #935017 [src:debhelper, src:strip-nondeterminism] debhelper breaks 
strip-nondeterminism autopkgtest
Bug reassigned from package 'src:debhelper, src:strip-nondeterminism' to 
'strip-nondeterminism'.
No longer marked as found in versions debhelper/12.5.1, debhelper/12.5, and 
strip-nondeterminism/1.5.0-1.
Ignoring request to alter fixed versions of bug #935017 to the same values 
previously set

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

Bug#935017: debhelper breaks strip-nondeterminism autopkgtest

[Niels Thykier]

Control: reassign -1 strip-nondeterminism


On Sun, 18 Aug 2019 08:19:37 +0200 Paul Gevers  wrote:
> Source: debhelper, strip-nondeterminism
> Control: found -1 debhelper/12.5.1
> Control: found -1 debhelper/12.5
> Control: found -1 strip-nondeterminism/1.5.0-1
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
> 
> Dear maintainers,
> 
> With a recent upload of debhelper the autopkgtest of
> strip-nondeterminism fails in testing when that autopkgtest is run with
> the binary packages of debhelper from unstable. It passes when run with
> only packages from testing. In tabular form:
>passfail
> debhelper  from testing12.5.1
> strip-nondeterminism   from testing1.5.0-1
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration of debhelper to
> testing [1]. Due to the nature of this issue, I filed this bug report
> against both packages. Can you please investigate the situation and
> reassign the bug to the right package?
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=debhelper
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/s/strip-nondeterminism/2758965/log.gz
> 
> 1..2
> not ok 1 - bin/dh_strip_nondeterminism --help returns 255
> 
> #   Failed test 'bin/dh_strip_nondeterminism --help returns 255'
> #   at t/binaries.t line 42.
> ok 2 - bin/strip-nondeterminism --help returns 0
> # Looks like you failed 1 test of 2.
> 

I cannot reproduce this locally in a sane way. For me, it returned 1
before and after upgrading to debhelper/12.5.1 (from 12.4).  Digging in
the tests, it looks like strip-nondeterminism is *not* testing the
installed binaries[1].

So for now I am punting it to strip-nondeterminism (even if only on a
technicality).  If you can dig out the real problem, please reassign
back/file a bug as appropriate.


Thanks,
~Niels

[1]:
https://salsa.debian.org/reproducible-builds/strip-nondeterminism/blob/master/t/binaries.t

Bug#874921: marked as done ([ifrit] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 18 Aug 2019 06:51:00 +
with message-id 
and subject line Bug#935005: Removed package(s) from unstable
has caused the Debian Bug report #874921,
regarding [ifrit] Future Qt4 removal from Buster
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.)


-- 
874921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ifrit
Version: 4.1.2-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 4.1.2-6+rm

Dear submitter,

as the package ifrit 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/935005

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

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#935016: [Pkg-javascript-devel] Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Xavier]

Le 18/08/2019 à 08:29, Niels Thykier a écrit :
> Control: reassign -1 debhelper
> Control: affects -1 pkg-js-tools
> 
> Xavier:
>> Le 18/08/2019 à 08:15, Xavier a écrit :
>>> [...]
>>>
>>> Works fine until debhelper 12.5. Then dh returns:
>>>
>>>   dh: unable to load addon nodejs: Debian/Debhelper/Sequence/nodejs.pm
>>>   did not return a true value at (eval 13) line 1.
>>>   BEGIN failed--compilation aborted at (eval 13) line 1.
>>>
>>>
>>> Next debug:
>>>   # perl -le 'use Debian::Debhelper::Sequence::nodejs'
>>>   Undefined subroutine ::add_command_options called at
>>>  /usr/share/perl5/Debian/Debhelper/Sequence/nodejs.pm line 8.
>>>
>>> [...]
> Thanks for debugging this.  This is a regression in debhelper that broke
> pkg-js-tools and nothing else.
> 
> Thanks,
> ~Niels

Thanks, I just fixed this in pkg-js-tools 0.9.6

Cheers,
Xavier

Bug#935016: marked as pending in pkg-js-tools

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #935016 in pkg-js-tools 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/js-team/pkg-js-tools/commit/7ca4a79bbdd9ba5fcb1ca1910cd95b10fdd10fe6


Fix debhelper sequence return value and update test

Closes: #935016


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935016

Bug#935016: [Pkg-javascript-devel] Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Niels Thykier]

Control: reassign -1 debhelper
Control: affects -1 pkg-js-tools

Xavier:
> Le 18/08/2019 à 08:15, Xavier a écrit :
>> [...]
>>
>> Works fine until debhelper 12.5. Then dh returns:
>>
>>   dh: unable to load addon nodejs: Debian/Debhelper/Sequence/nodejs.pm
>>   did not return a true value at (eval 13) line 1.
>>   BEGIN failed--compilation aborted at (eval 13) line 1.
>>
>>
>> Next debug:
>>   # perl -le 'use Debian::Debhelper::Sequence::nodejs'
>>   Undefined subroutine ::add_command_options called at
>>  /usr/share/perl5/Debian/Debhelper/Sequence/nodejs.pm line 8.
>>
>> [...]
Thanks for debugging this.  This is a regression in debhelper that broke
pkg-js-tools and nothing else.

Thanks,
~Niels

Processed: Re: [Pkg-javascript-devel] Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 debhelper
Bug #935016 [pkg-js-tools] pkg-js-tools: An unannounced change in "debhelper" 
breaks pkg-js-tools
Bug reassigned from package 'pkg-js-tools' to 'debhelper'.
No longer marked as found in versions pkg-js-tools/0.9.5.
Ignoring request to alter fixed versions of bug #935016 to the same values 
previously set
> affects -1 pkg-js-tools
Bug #935016 [debhelper] pkg-js-tools: An unannounced change in "debhelper" 
breaks pkg-js-tools
Added indication that 935016 affects pkg-js-tools

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

Processed: Bug#935016 marked as pending in pkg-js-tools

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935016 [debhelper] pkg-js-tools: An unannounced change in "debhelper" 
breaks pkg-js-tools
Added tag(s) pending.

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

Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Niels Thykier]

Control: tags -1 moreinfo

On Sun, 18 Aug 2019 07:55:59 +0200 Xavier Guimard  wrote:
> Package: pkg-js-tools
> Version: 0.9.5
> Severity: grave
> Justification: renders package unusable
> 
> pkg-js-tools was based on add_command_options which disappears in
> Debhelper 12.5.1. This renders pkg-js-tools unusable.
> 
> 

Hi,

No, add_command_options has not been (intentionally?) removed in
debhelper 12.5.1.

Could you please clarify what made you file this bug?  Did you get an
error/did something break?

Thanks,
~Niels

Processed: Re: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #935016 [pkg-js-tools] pkg-js-tools: An unannounced change in "debhelper" 
breaks pkg-js-tools
Added tag(s) moreinfo.

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

Bug#935016: [Pkg-javascript-devel] Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Xavier]

Le 18/08/2019 à 08:15, Xavier a écrit :
> Le 18/08/2019 à 08:08, Niels Thykier a écrit :
>> Control: tags -1 moreinfo
>>
>> On Sun, 18 Aug 2019 07:55:59 +0200 Xavier Guimard  wrote:
>>> Package: pkg-js-tools
>>> Version: 0.9.5
>>> Severity: grave
>>> Justification: renders package unusable
>>>
>>> pkg-js-tools was based on add_command_options which disappears in
>>> Debhelper 12.5.1. This renders pkg-js-tools unusable.
>>>
>>>
>>
>> Hi,
>>
>> No, add_command_options has not been (intentionally?) removed in
>> debhelper 12.5.1.
>>
>> Could you please clarify what made you file this bug?  Did you get an
>> error/did something break?
>>
>> Thanks,
>> ~Niels
> 
> Hi,
> 
> pkg-js-tools "Sequence" is simply:
> 
>   #!/usr/bin/perl
>   # debhelper sequence file
> 
>   use warnings;
>   use strict;
>   use Debian::Debhelper::Dh_Lib;
> 
>   add_command_options("dh_auto_test", "--buildsystem=nodejs");
>   add_command_options("dh_auto_configure", "--buildsystem=nodejs");
>   add_command_options("dh_auto_build", "--buildsystem=nodejs");
>   add_command_options("dh_auto_install", "--buildsystem=nodejs");
>   add_command_options("dh_auto_clean", "--buildsystem=nodejs");
> 
> Works fine until debhelper 12.5. Then dh returns:
> 
>   dh: unable to load addon nodejs: Debian/Debhelper/Sequence/nodejs.pm
>   did not return a true value at (eval 13) line 1.
>   BEGIN failed--compilation aborted at (eval 13) line 1.
> 
> 
> Next debug:
>   # perl -le 'use Debian::Debhelper::Sequence::nodejs'
>   Undefined subroutine ::add_command_options called at
>  /usr/share/perl5/Debian/Debhelper/Sequence/nodejs.pm line 8.
> 
> 
> I think I have to change to "insert_before" commands, isn't it ?

Found: debhelper changed probably the way to load Sequence file. Now it
uses probably a "require" that checks returned value

Cheers,

Processed: debhelper breaks strip-nondeterminism autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 debhelper/12.5.1
Bug #935017 [src:debhelper, src:strip-nondeterminism] debhelper breaks 
strip-nondeterminism autopkgtest
Marked as found in versions debhelper/12.5.1.
> found -1 debhelper/12.5
Bug #935017 [src:debhelper, src:strip-nondeterminism] debhelper breaks 
strip-nondeterminism autopkgtest
Marked as found in versions debhelper/12.5.
> found -1 strip-nondeterminism/1.5.0-1
Bug #935017 [src:debhelper, src:strip-nondeterminism] debhelper breaks 
strip-nondeterminism autopkgtest
Marked as found in versions strip-nondeterminism/1.5.0-1.

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

Bug#935017: debhelper breaks strip-nondeterminism autopkgtest

[Paul Gevers]

Source: debhelper, strip-nondeterminism
Control: found -1 debhelper/12.5.1
Control: found -1 debhelper/12.5
Control: found -1 strip-nondeterminism/1.5.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of debhelper the autopkgtest of
strip-nondeterminism fails in testing when that autopkgtest is run with
the binary packages of debhelper from unstable. It passes when run with
only packages from testing. In tabular form:
   passfail
debhelper  from testing12.5.1
strip-nondeterminism   from testing1.5.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of debhelper to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=debhelper

https://ci.debian.net/data/autopkgtest/testing/amd64/s/strip-nondeterminism/2758965/log.gz

1..2
not ok 1 - bin/dh_strip_nondeterminism --help returns 255

#   Failed test 'bin/dh_strip_nondeterminism --help returns 255'
#   at t/binaries.t line 42.
ok 2 - bin/strip-nondeterminism --help returns 0
# Looks like you failed 1 test of 2.



signature.asc
Description: OpenPGP digital signature

Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Xavier]

Le 18/08/2019 à 08:08, Niels Thykier a écrit :
> Control: tags -1 moreinfo
> 
> On Sun, 18 Aug 2019 07:55:59 +0200 Xavier Guimard  wrote:
>> Package: pkg-js-tools
>> Version: 0.9.5
>> Severity: grave
>> Justification: renders package unusable
>>
>> pkg-js-tools was based on add_command_options which disappears in
>> Debhelper 12.5.1. This renders pkg-js-tools unusable.
>>
>>
> 
> Hi,
> 
> No, add_command_options has not been (intentionally?) removed in
> debhelper 12.5.1.
> 
> Could you please clarify what made you file this bug?  Did you get an
> error/did something break?
> 
> Thanks,
> ~Niels

Hi,

pkg-js-tools "Sequence" is simply:

  #!/usr/bin/perl
  # debhelper sequence file

  use warnings;
  use strict;
  use Debian::Debhelper::Dh_Lib;

  add_command_options("dh_auto_test", "--buildsystem=nodejs");
  add_command_options("dh_auto_configure", "--buildsystem=nodejs");
  add_command_options("dh_auto_build", "--buildsystem=nodejs");
  add_command_options("dh_auto_install", "--buildsystem=nodejs");
  add_command_options("dh_auto_clean", "--buildsystem=nodejs");

Works fine until debhelper 12.5. Then dh returns:

  dh: unable to load addon nodejs: Debian/Debhelper/Sequence/nodejs.pm
  did not return a true value at (eval 13) line 1.
  BEGIN failed--compilation aborted at (eval 13) line 1.


Next debug:
  # perl -le 'use Debian::Debhelper::Sequence::nodejs'
  Undefined subroutine ::add_command_options called at
 /usr/share/perl5/Debian/Debhelper/Sequence/nodejs.pm line 8.


I think I have to change to "insert_before" commands, isn't it ?

Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

[Xavier Guimard]

Package: pkg-js-tools
Version: 0.9.5
Severity: grave
Justification: renders package unusable

pkg-js-tools was based on add_command_options which disappears in
Debhelper 12.5.1. This renders pkg-js-tools unusable.