Bug#954622: marked as done (jitterdebugger: FTBFS: jitterdebugger.c:139:14: error: static declaration of ‘gettid’ follows non-static declaration)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 03:50:28 +
with message-id 
and subject line Bug#954622: fixed in jitterdebugger 0.3.1+git20200117.b90ff3a-1
has caused the Debian Bug report #954622,
regarding jitterdebugger: FTBFS: jitterdebugger.c:139:14: error: static 
declaration of ‘gettid’ follows non-static declaration
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.)


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

Hi,

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

Relevant part (hopefully):
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -pedantic -Wall -Wstrict-aliasing=1 
> -Wno-unused-result -pthread -O2 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
> jittersamples.o jittersamples.c
> In file included from jittersamples.c:12:
> jitterdebugger.h:43:36: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>43 | #define err_handler(error, fmt, arg...) do { \
>   |^~~
> jitterdebugger.h:46:30: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>46 | #define warn_handler(fmt, arg...) do {  \
>   |  ^~~
> jitterdebugger.h:49:27: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>49 | #define err_abort(fmt, arg...) do { \
>   |   ^~~
> In file included from jitterutils.c:11:
> jitterdebugger.h:43:36: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>43 | #define err_handler(error, fmt, arg...) do { \
>   |^~~
> jitterdebugger.h:46:30: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>46 | #define warn_handler(fmt, arg...) do {  \
>   |  ^~~
> jitterdebugger.h:49:27: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>49 | #define err_abort(fmt, arg...) do { \
>   |   ^~~
> jitterutils.c: In function ‘ringbuffer_write’:
> jitterdebugger.h:13:1: warning: ISO C forbids braced-groups within 
> expressions [-Wpedantic]
>13 | ({ \
>   | ^
> jitterutils.c:63:9: note: in expansion of macro ‘READ_ONCE’
>63 |  read = READ_ONCE(rb->read);
>   | ^
> jitterdebugger.h:20:1: warning: ISO C forbids braced-groups within 
> expressions [-Wpedantic]
>20 | ({ \
>   | ^
> jitterutils.c:73:2: note: in expansion of macro ‘WRITE_ONCE’
>73 |  WRITE_ONCE(rb->write, rb->write + 1);
>   |  ^~
> jitterutils.c: In function ‘ringbuffer_read’:
> jitterdebugger.h:13:1: warning: ISO C forbids braced-groups within 
> expressions [-Wpedantic]
>13 | ({ \
>   | ^
> jitterutils.c:81:10: note: in expansion of macro ‘READ_ONCE’
>81 |  write = READ_ONCE(rb->write);
>   |  ^
> jitterdebugger.h:20:1: warning: ISO C forbids braced-groups within 
> expressions [-Wpedantic]
>20 | ({ \
>   | ^
> jitterutils.c:89:2: note: in expansion of macro ‘WRITE_ONCE’
>89 |  WRITE_ONCE(rb->read, rb->read + 1);
>   |  ^~
> In file included from jitterdebugger.c:24:
> jitterdebugger.h:43:36: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>43 | #define err_handler(error, fmt, arg...) do { \
>   |^~~
> jitterdebugger.h:46:30: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>46 | #define warn_handler(fmt, arg...) do {  \
>   |  ^~~
> jitterdebugger.h:49:27: warning: ISO C does not permit named variadic macros 
> [-Wvariadic-macros]
>49 | #define err_abort(fmt, arg...) do { \
>   |   ^~~
> jitterdebugger.c: In function ‘sig_handler’:
> jitterdebugger.h:20:1: warning: ISO C forbids braced-groups within 
> expressions [-Wpedantic]
>20 | ({ \
>   | ^
> jitterdebugger.c:63:2: note: in expansion of macro ‘WRITE_ONCE’
>63 |  WRITE_ONCE(shutdown, 1);
>   |  ^~
> jitterdebugger.c: At top level:
> jitterdebugger.c:139:14: error: static declaration of ‘gettid’ follows 
> non-static declaration
>   139 | static pid_t gettid(void)
>   

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Paul Wise]

On Sun, 2020-03-22 at 20:45 -0700, Felix Lechner wrote:

> Well, that's what I did with xdeb, but it is causing #954415.

BTW, re the lintian binary-is-wrong-architecture tag description,
Emdebian no longer exists so it would be best to not mention it.

> My inclination is yes, although personal profiles will soon become
> very tweakable.

Sounds good to me.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Felix Lechner]

Hi Paul,

On Sun, Mar 22, 2020 at 8:40 PM Paul Wise  wrote:
>
> Will the new Perl tests be enabled by default?

Well, that's what I did with xdeb, but it is causing #954415.

My inclination is yes, although personal profiles will soon become
very tweakable.

Kind regards

Felix Lechner

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Paul Wise]

On Sun, 2020-03-22 at 19:50 -0700, Felix Lechner wrote:

> Regarding the 'affects' setting

That just means that folks reporting bugs against lintian are more
likely to see the existing pkg-perl-tools bug rather than filing
another duplicate bug report like I did.

> please know that the checks in pkg-perl-tools will soon become part
> of Lintian (except perhaps the one requiring network access)

Excellent, the more tests the better.

Will the new Perl tests be enabled by default?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#892344: literki: Please use 'pkg-config' to find FreeType 2

[Logan Rosen]

Package: literki
Version: 0.0.0+20100113.git1da40724-1.2
Followup-For: Bug #892344
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/control: Build-depend on pkg-config.
  * d/p/06_use_pkg-config.patch: Use pkg-config instead of removed
freetype-config to fix FTBFS.

Thanks for considering the patch.

Logan

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

Kernel: Linux 5.4.0-18-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru literki-0.0.0+20100113.git1da40724/debian/control 
literki-0.0.0+20100113.git1da40724/debian/control
--- literki-0.0.0+20100113.git1da40724/debian/control   2016-01-24 
07:42:40.0 -0500
+++ literki-0.0.0+20100113.git1da40724/debian/control   2020-03-22 
23:17:53.0 -0400
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian freesmartphone.org Team 

 Uploaders: Timo Jyrinki 
-Build-Depends: debhelper (>= 7), libfreetype6-dev, libpng-dev, libfakekey-dev, 
libxi-dev, libxcb1-dev, libxrender-dev, libxrandr-dev, libpng++-dev
+Build-Depends: debhelper (>= 7), libfreetype6-dev, libpng-dev, libfakekey-dev, 
libxi-dev, libxcb1-dev, libxrender-dev, libxrandr-dev, libpng++-dev, pkg-config
 Standards-Version: 3.8.4
 Homepage: http://git.senfdax.de/?p=literki
 Vcs-Git: http://git.debian.org/git/pkg-fso/literki.git
diff -Nru 
literki-0.0.0+20100113.git1da40724/debian/patches/06_use_pkg-config.patch 
literki-0.0.0+20100113.git1da40724/debian/patches/06_use_pkg-config.patch
--- literki-0.0.0+20100113.git1da40724/debian/patches/06_use_pkg-config.patch   
1969-12-31 19:00:00.0 -0500
+++ literki-0.0.0+20100113.git1da40724/debian/patches/06_use_pkg-config.patch   
2020-03-22 23:17:53.0 -0400
@@ -0,0 +1,13 @@
+--- a/Makefile
 b/Makefile
+@@ -4,8 +4,8 @@
+ 
+ CXXCOMPILE=g++
+ 
+-CFLAGS=-g `freetype-config --cflags`
+-LDFLAGS=-g `freetype-config --libs`
++CFLAGS=-g `pkg-config --cflags freetype2`
++LDFLAGS=-g `pkg-config --libs freetype2`
+ 
+ %.o: %.cpp
+   $(CXXCOMPILE) $(CFLAGS) -c $<
diff -Nru literki-0.0.0+20100113.git1da40724/debian/patches/series 
literki-0.0.0+20100113.git1da40724/debian/patches/series
--- literki-0.0.0+20100113.git1da40724/debian/patches/series2016-01-26 
11:23:32.0 -0500
+++ literki-0.0.0+20100113.git1da40724/debian/patches/series2020-03-22 
23:17:36.0 -0400
@@ -3,3 +3,4 @@
 04_fix_desktop.diff
 05_fix_ftbfs_binutils-gold.patch
 libpng16.patch
+06_use_pkg-config.patch

Bug#939260: marked as done (websploit: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 03:09:08 +
with message-id 
and subject line Bug#939260: fixed in websploit 4.0.4-1
has caused the Debian Bug report #939260,
regarding websploit: Python2 removal in sid/bullseye
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.)


-- 
939260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:websploit
Version: 3.0.0-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.

  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:websploit

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: websploit
Source-Version: 4.0.4-1
Done: =?utf-8?b?U1ogTGluICjmnpfkuIrmmbop?= 

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

Debian distribution maintenance software
pp.
SZ Lin (林上智)  (supplier of updated websploit 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, 22 Mar 2020 22:45:35 +0800
Source: websploit
Architecture: source
Version: 4.0.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: SZ Lin (林上智) 
Closes: 939260
Changes:
 websploit (4.0.4-1) unstable; urgency=medium
 .
   [ SZ Lin (林上智) ]
   * Team upload.
   * Add upstream metadata
   * Correct license from GPL-3+ to Expat in d/copyright
 .
   [ Marcos Fouces ]
   * Update watch file to new upstream repo (same author).
   * Swith to pybuild build system.
   * Migrate to Python3. (Closes:#939260)
   * Remove d/websploit.install as it is no more needed.
   * Update README file extension in d/websploit.docs.
   * Remove unneeded __pychache__ directories in package.
   * Add dependency on python-setuptools.
   * Bump to Standards-Version 4.5.0 (no changes required).
   * Delete unneeded Recommends field.
   * Add Rules-Requires-Root: no in control file.
   * Update copyright 

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Felix Lechner]

Hi Paul,

On Sun, Mar 22, 2020 at 7:44 PM Paul Wise  wrote:
>
> Yeah, doing with this mail.

Regarding the 'affects' setting, please know that the checks in
pkg-perl-tools will soon become part of Lintian (except perhaps the
one requiring network access). It will reduce problems like this.

Kind regards
Felix Lechner

Bug#938759: marked as done (urwid: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 02:50:35 +
with message-id 
and subject line Bug#938759: fixed in urwid 2.0.1-3
has caused the Debian Bug report #938759,
regarding urwid: Python2 removal in sid/bullseye
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.)


-- 
938759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:urwid
Version: 2.0.1-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:urwid

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: urwid
Source-Version: 2.0.1-3
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated urwid 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, 22 Mar 2020 21:58:15 -0400
Source: urwid
Architecture: source
Version: 2.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938759
Changes:
 urwid (2.0.1-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
   * Use debhelper-compat instead of debian/compat.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Add missing colon in closes line.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938759
Checksums-Sha1:
 66c4fffb5cffb70b0cee756fdf5335a73dfd5065 2081 urwid_2.0.1-3.dsc
 e7ae037c73c594103c10fcb33d5f479954629ffa 5312 urwid_2.0.1-3.debian.tar.xz
 593b3a292fa95c41bf8d0da4668ead24977c2372 8089 urwid_2.0.1-3_source.buildinfo

Bug#954762: systraq: Annoying as Hell

[Brice Hunt]

Package: systraq
Version: 20160803-3
Severity: critical
Tags: security
Justification: breaks unrelated software

Dear Maintainer,

You annoyed me with your jackass hourly cron job (once a day is sufficient) Now
I'm annoying you.

Enjoy Jackass

Solution: uninstall Debian, go with a distro that doesn't use jackasses instead
of developers.



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

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

Versions of packages systraq depends on:
ii  adduser3.118
ii  bsd-mailx  8.1.2-0.20180807cvs-1+b1
ii  debsums2.2.5
ii  exim4  4.93-12
ii  exim4-daemon-light [mail-transport-agent]  4.93-12
ii  filetraq   0.3
ii  make   4.2.1-1.2
ii  net-tools  1.60+git20180626.aebd88e-1
ii  procps 2:3.3.16-4

systraq recommends no packages.

systraq suggests no packages.

-- no debconf information

Bug#938294: marked as done (pyusb: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 02:50:08 +
with message-id 
and subject line Bug#938294: fixed in pyusb 1.0.2-2
has caused the Debian Bug report #938294,
regarding pyusb: Python2 removal in sid/bullseye
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.)


-- 
938294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyusb
Version: 1.0.2-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pyusb

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: pyusb
Source-Version: 1.0.2-2
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyusb 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, 22 Mar 2020 21:53:52 -0400
Source: pyusb
Architecture: source
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938294
Changes:
 pyusb (1.0.2-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/watch: Use https protocol
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938294
Checksums-Sha1:
 94bb471794715dc0832c55c558419a7983cd46b0 1955 pyusb_1.0.2-2.dsc
 04bd5a7cc3f911a0a2454e60b50273c11c9a6ba4 4876 pyusb_1.0.2-2.debian.tar.xz
 13b461be6115f7b261c2e8d7017ddaac59539a55 6320 pyusb_1.0.2-2_source.buildinfo
Checksums-Sha256:
 913f9d7a5ba947cd65a1a0f285b85f3421bdacfbdcc3e524e6327bd4fad24d61 1955 
pyusb_1.0.2-2.dsc
 4071860ff464be25889a798f405f5a11ed5cfe898086eb93ebb56b6798e9c749 4876 
pyusb_1.0.2-2.debian.tar.xz
 4884f00d61222cda4e4b6fd4061b6dba142d540f60172f501c1c7ae6953cd77e 6320 
pyusb_1.0.2-2_source.buildinfo
Files:
 

Processed: Re: Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pkg-perl-tools
Bug #954761 [lintian] lintian: crashes with: coercion for "original_severity" 
failed: Unknown tag severity serious
Bug reassigned from package 'lintian' to 'pkg-perl-tools'.
No longer marked as found in versions lintian/2.59.0 and lintian/2.58.0.
Ignoring request to alter fixed versions of bug #954761 to the same values 
previously set
> forcemerge 954331 -1
Bug #954331 {Done: gregor herrmann } [pkg-perl-tools] 
pkg-perl-tools: Please adjust Severity values in tag declarations
Bug #954761 [pkg-perl-tools] lintian: crashes with: coercion for 
"original_severity" failed: Unknown tag severity serious
Severity set to 'grave' from 'serious'
Marked Bug as done
Removed indication that 954761 affects lintian
Marked as fixed in versions pkg-perl-tools/0.59.
Marked as found in versions pkg-perl-tools/0.58.
Merged 954331 954761

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

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Paul Wise]

Control: reassign -1 pkg-perl-tools
Control: forcemerge 954331 -1

On Sun, 2020-03-22 at 18:35 -0700, Felix Lechner wrote:

> This is #954331 in pkg-perl-tools, which is already done.
> 
> Not sure how to best close this bug. Maybe 'forcemerge'?

Yeah, doing with this mail.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: affects 954761

[Debian Bug Tracking System]

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

> affects 954761 lintian
Bug #954761 [lintian] lintian: crashes with: coercion for "original_severity" 
failed: Unknown tag severity serious
Added indication that 954761 affects lintian
> thanks
Stopping processing here.

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

Bug#954512: nextepc: FTBFS: sysctl.h:21:2: error: #warning "The header is deprecated and will be removed." [-Werror=cpp]

[Sukchan Lee]

Hi Lucas,

nextepc was deprecated. Please use open5gs(
https://github.com/open5gs/open5gs) project.

Thanks and regards,
   Sukchan

On Sun, Mar 22, 2020 at 4:39 AM Lucas Nussbaum  wrote:

> Source: nextepc
> Version: 0.3.10+nods-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200321 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H
> -I. -I../..  -I../../lib/ipfw/objs/include_e -include glue.h
> -D_DEFAULT_SOURCE -D_BSD_SOURCE -DUSERSPACE -D__BSD_VISIBLE -DNEED_STRTONUM
> -DNEED_ROUNDUP2 -DNEED_SYSCTLBYNAME -DNEED_SIN_LEN -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -Werror -Wno-shift-negative-value
> -Wno-unused-but-set-variable -Wno-unknown-warning-option -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wno-unused-result -c -o tables.lo tables.c
> > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../..
> -I../../lib/ipfw/objs/include_e -include glue.h -D_DEFAULT_SOURCE
> -D_BSD_SOURCE -DUSERSPACE -D__BSD_VISIBLE -DNEED_STRTONUM -DNEED_ROUNDUP2
> -DNEED_SYSCTLBYNAME -DNEED_SIN_LEN -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Werror -Wno-shift-negative-value -Wno-unused-but-set-variable
> -Wno-unknown-warning-option -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -Wno-unused-result -c ipfw2.c  -fPIC -DPIC -o .libs/ipfw2.o
> > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../..
> -I../../lib/ipfw/objs/include_e -include glue.h -D_DEFAULT_SOURCE
> -D_BSD_SOURCE -DUSERSPACE -D__BSD_VISIBLE -DNEED_STRTONUM -DNEED_ROUNDUP2
> -DNEED_SYSCTLBYNAME -DNEED_SIN_LEN -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Werror -Wno-shift-negative-value -Wno-unused-but-set-variable
> -Wno-unknown-warning-option -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -Wno-unused-result -c tables.c  -fPIC -DPIC -o .libs/tables.o
> > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../..
> -I../../lib/ipfw/objs/include_e -include glue.h -D_DEFAULT_SOURCE
> -D_BSD_SOURCE -DUSERSPACE -D__BSD_VISIBLE -DNEED_STRTONUM -DNEED_ROUNDUP2
> -DNEED_SYSCTLBYNAME -DNEED_SIN_LEN -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Werror -Wno-shift-negative-value -Wno-unused-but-set-variable
> -Wno-unknown-warning-option -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -Wno-unused-result -c dummynet.c  -fPIC -DPIC -o .libs/dummynet.o
> > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../..
> -I../../lib/ipfw/objs/include_e -include glue.h -D_DEFAULT_SOURCE
> -D_BSD_SOURCE -DUSERSPACE -D__BSD_VISIBLE -DNEED_STRTONUM -DNEED_ROUNDUP2
> -DNEED_SYSCTLBYNAME -DNEED_SIN_LEN -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Werror -Wno-shift-negative-value -Wno-unused-but-set-variable
> -Wno-unknown-warning-option -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -Wno-unused-result -c ipv6.c  -fPIC -DPIC -o .libs/ipv6.o
> > In file included from dummynet.c:21:
> > /usr/include/x86_64-linux-gnu/sys/sysctl.h:21:2: error: #warning "The
>  header is deprecated and will be removed." [-Werror=cpp]
> >21 | #warning "The  header is deprecated and will be
> removed."
> >   |  ^~~
> > In file included from ipfw2.c:27:
> > /usr/include/x86_64-linux-gnu/sys/sysctl.h:21:2: error: #warning "The
>  header is deprecated and will be removed." [-Werror=cpp]
> >21 | #warning "The  header is deprecated and will be
> removed."
> >   |  ^~~
> > In file included from tables.c:23:
> > /usr/include/x86_64-linux-gnu/sys/sysctl.h:21:2: error: #warning "The
>  header is deprecated and will be removed." [-Werror=cpp]
> >21 | #warning "The  header is deprecated and will be
> removed."
> >   |  ^~~
> > /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H
> -I. -I../..  -I../../lib/ipfw/objs/include_e -include glue.h
> -D_DEFAULT_SOURCE -D_BSD_SOURCE -DUSERSPACE -D__BSD_VISIBLE -DNEED_STRTONUM
> -DNEED_ROUNDUP2 -DNEED_SYSCTLBYNAME -DNEED_SIN_LEN -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -Werror -Wno-shift-negative-value
> -Wno-unused-but-set-variable -Wno-unknown-warning-option -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wno-unused-result -c -o expand_number.lo
> expand_number.c
> > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../..
> -I../../lib/ipfw/objs/include_e -include glue.h -D_DEFAULT_SOURCE
> -D_BSD_SOURCE -DUSERSPACE -D__BSD_VISIBLE -DNEED_STRTONUM -DNEED_ROUNDUP2
> -DNEED_SYSCTLBYNAME -DNEED_SIN_LEN -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Werror -Wno-shift-negative-value -Wno-unused-but-set-variable
> -Wno-unknown-warning-option -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -Wno-unused-result -c expand_number.c  -fPIC -DPIC -o 

Bug#938759: marked as pending in urwid

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/urwid/-/commit/b79e3d0121baf0085152bca76f10969311c1654a


Drop python2 support; Closes: #938759


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938759

Processed: Bug#938759 marked as pending in urwid

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938759 [src:urwid] urwid: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Processed: Bug#938294 marked as pending in pyusb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938294 [src:pyusb] pyusb: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#938294: marked as pending in pyusb

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/pyusb/-/commit/0a55d736c8313be957f76034cd0ae5d2c3ac5926


Drop python2 support; Closes: #938294


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938294

Processed: Bug#954712 marked as pending in consul

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954712 [src:consul] consul: FTBFS: dh_auto_test: error: cd _build && go 
test -vet=off -v -p 4 -short -failfast -timeout 8m github.com/hashicorp/consul 
[...] github.com/hashicorp/consul/version returned exit code 1
Added tag(s) pending.

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

Bug#954712: marked as pending in consul

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #954712 in consul 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/go-team/packages/consul/-/commit/147f42baf54aa620606798fddb1e022b8f2edfcd


Disabled failing "TestTakeReturn" (Closes: #954712).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954712

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Felix Lechner]

Hi Paul,

On Sun, Mar 22, 2020 at 6:30 PM Paul Wise  wrote:
>
> Lintian::Tag::Info::load(Lintian::Tag::Info=HASH(0x556c92ea6f30), 
> "/usr/share/lintian/tags/pkg-perl/module-build-tiny-needs-newe"...)

This is #954331 in pkg-perl-tools, which is already done.

Not sure how to best close this bug. Maybe 'forcemerge'?

Kind regards

Felix Lechner

Processed: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.59.0
Bug #954761 [lintian] lintian: crashes with: coercion for "original_severity" 
failed: Unknown tag severity serious
Marked as found in versions lintian/2.59.0.

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

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

[Paul Wise]

Package: lintian
Version: 2.58.0
Severity: serious
Control: found -1 2.59.0
Usertags: crash

Whenever I run lintian (either source or binaries) I get the following
crash. The configuration file and options used don't appear to cause
this crash. It appears to happen with all packages I try.

$ lintian nsis_3.05-1.dsc
coercion for "original_severity" failed: Unknown tag severity serious
Lintian::Tag::Info::__ANON__("serious") called at (eval 125) line 28
eval {...} called at (eval 125) line 27

Lintian::Tag::Info::original_severity(Lintian::Tag::Info=HASH(0x556c92ea6f30), 
"serious") called at /usr/share/perl5/Lintian/Tag/Info.pm line 182
Lintian::Tag::Info::load(Lintian::Tag::Info=HASH(0x556c92ea6f30), 
"/usr/share/lintian/tags/pkg-perl/module-build-tiny-needs-newe"...) called at 
/usr/share/perl5/Lintian/Profile.pm line 224
Lintian::Profile::load(Lintian::Profile=HASH(0x556c92a0a5c8), undef, 
ARRAY(0x556c9049c528), HASH(0x556c90740b90)) called at /usr/bin/lintian line 221
dplint::load_profile(undef) called at 
/usr/share/lintian/commands/lintian.pm line 712
eval {...} called at /usr/share/lintian/commands/lintian.pm line 712
main::main() called at /usr/bin/lintian line 46
eval {...} called at /usr/bin/lintian line 46
main::__ANON__("/usr/share/lintian/commands/lintian.pm") called at 
/usr/bin/lintian line 119
dplint::run_tool("/usr/bin/lintian", "lintian") called at 
/usr/bin/lintian line 298
dplint::main() called at /usr/bin/lintian line 382

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 
'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils 2.34-5
ii  bzip21.0.8-2
ii  diffstat 1.63-1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.38-4
ii  gettext  0.19.8.1-10
ii  gpg  2.2.19-3
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b3
ii  libarchive-zip-perl  1.68-1
ii  libcapture-tiny-perl 0.48-1
ii  libclass-xsaccessor-perl 1.19-3+b3
ii  libclone-perl0.43-2
ii  libdevel-size-perl   0.83-1+b1
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libfont-ttf-perl 1.06-1
ii  libhtml-parser-perl  3.72-5
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.75-1
ii  libipc-run-perl  20180523.0-2
ii  libjson-maybexs-perl 1.004000-1
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmoo-perl  2.003006-1
ii  libmoox-aliases-perl 0.001006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.108-1
ii  libsereal-decoder-perl   4.011+ds-1
ii  libsereal-encoder-perl   4.011+ds-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3200-1
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.008001-2
ii  liburi-perl  1.76-2
ii  libxml-libxml-perl   2.0134+dfsg-2
ii  libxml-writer-perl   0.625-1
ii  libyaml-libyaml-perl 0.80+repack-2+b1
ii  man-db   2.9.1-1
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-9
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b6

Versions of packages lintian suggests:
ii  binutils-multiarch 2.34-5
ii  libtext-template-perl  1.58-1

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#954639: gftp: FTBFS: pty.c:65:10: fatal error: stropts.h: No such file or directory

[Logan Rosen]

Package: gftp
Version: 2.0.19-5
Followup-For: Bug #954639
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/glibc-2.30.patch: Fix FTBFS against glibc >= 2.30 with cherrypicked
patch from upstream Git.

Thanks for considering the patch.

Logan

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

Kernel: Linux 5.4.0-18-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gftp-2.0.19/debian/patches/glibc-2.30.patch 
gftp-2.0.19/debian/patches/glibc-2.30.patch
--- gftp-2.0.19/debian/patches/glibc-2.30.patch 1969-12-31 19:00:00.0 
-0500
+++ gftp-2.0.19/debian/patches/glibc-2.30.patch 2020-03-22 20:49:10.0 
-0400
@@ -0,0 +1,24 @@
+From 371c494a34c1820544d6563fb7ef5ca51a0ee199 Mon Sep 17 00:00:00 2001
+From: Brian Masney 
+Date: Thu, 21 Jul 2016 05:05:18 -0400
+Subject: [PATCH] fixed compiling on some versions of Linux. Patch picked up
+ from the Fedora Project at
+ https://github.com/repoforge/rpms/blob/master/specs/gftp/gftp-stropts.patch
+
+---
+ lib/pty.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/lib/pty.c b/lib/pty.c
+index f7cb1f9..f9d609b 100644
+--- a/lib/pty.c
 b/lib/pty.c
+@@ -61,7 +61,7 @@ _gftp_ptys_open (int fdm, int fds, char *pts_name)
+ 
+ #elif HAVE_GRANTPT
+ 
+-#if !(defined(__FreeBSD__) || defined(__NetBSD__) || defined(__APPLE__))
++#if !(defined(__FreeBSD__) || defined(__NetBSD__) || defined(__APPLE__) || 
defined(__linux__))
+ #include 
+ #endif
+ 
diff -Nru gftp-2.0.19/debian/patches/series gftp-2.0.19/debian/patches/series
--- gftp-2.0.19/debian/patches/series   2016-11-29 14:24:17.0 -0500
+++ gftp-2.0.19/debian/patches/series   2020-03-22 20:49:23.0 -0400
@@ -1,3 +1,4 @@
 01-hurd_do_not_use_PATH_MAX.patch
 desktop-file-binary
 fix-configure.in.patch
+glibc-2.30.patch

Bug#953749: marked as done (ceph: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 00:22:10 +
with message-id 
and subject line Bug#953749: fixed in ceph 14.2.8-2
has caused the Debian Bug report #953749,
regarding ceph: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x
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.)


-- 
953749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:ceph
version: 14.2.8-1
severity: serious
tags: ftbfs

Hi,

The latest upload of ceph to unstable fails on armel, armhf, i386, mips64el, 
mipsel, s390x:

https://buildd.debian.org/status/package.php?p=ceph

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 14.2.8-2
Done: Bernd Zeimetz 

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated ceph 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: Mon, 23 Mar 2020 00:14:25 +0100
Source: ceph
Architecture: source
Version: 14.2.8-2
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Bernd Zeimetz 
Closes: 953749
Changes:
 ceph (14.2.8-2) unstable; urgency=medium
 .
   * [eed9184] Fix 32bit issues in src/mds/PurgeQueue.cc
 mips64el (as reported in the bug report) built fine.
 s390x is a buildd issue, gets stuck sometimes for unknown (and not
 reproducible) reasons.
 Other build issues are fixed hopefully.
 Thanks to Ivo De Decker (Closes: #953749)
Checksums-Sha1:
 33111ddad356ba749393038e2db96630793f97f9 5850 ceph_14.2.8-2.dsc
 77cec0c6af35b47bc0ca34b9d9a75efae79dbf50 109428 ceph_14.2.8-2.debian.tar.xz
 f685b53d39de916e1e1b31fad63bebf4fea03554 20217 ceph_14.2.8-2_source.buildinfo
Checksums-Sha256:
 5f225f31595d2fb8a3c00a3ff9e22db59b3a1c3a965d9209eb5fe685e88d322c 5850 
ceph_14.2.8-2.dsc
 f65d036f2f18739cbdbd6dcd10af06e7ede35648862d13f3f867088a5ed13c4d 109428 
ceph_14.2.8-2.debian.tar.xz
 3ff4272919415ab314e06b5b20cc43d935573a5c29a533a48c3cdf082e4f2740 20217 
ceph_14.2.8-2_source.buildinfo
Files:
 12bf7f76f0a22ff0a0b5429fa82578e3 5850 admin optional ceph_14.2.8-2.dsc
 5dade9116de496b264debb04a8f636e3 109428 admin optional 
ceph_14.2.8-2.debian.tar.xz
 a2f86f93049da06de5cc27789a7b47e6 20217 admin optional 
ceph_14.2.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl5386kACgkQ6zYXGm/5
Q1+xsQ//T1cjui9Qh2TJLBLIOLoJqjlZF5EPicKAJRQbzzMI2G2x5kk82TNsy9JM
3gbBADwtoIjOe3cXlpcdzqU8QvHhQy+O/RrWw6nqQcnRR6W+lBE4boWPL4/RnGHd
Q9s1WbyIyLpbhIuLUgzylaTxEMuhk/iPvKxjSDmscpPTXkA/3VYC/rkzIwaD3qGO
daBSOekKdb9xBI9LuaTSpzHKGqyuHDeUUKOYwjjbEheyn6YhD6EFOTDjl6UJcsTL
NkKER8b8gbWW8VCEf32QVVaAwfQ/Oi+2zCfbFWaw//VUH7DfZhea+AbVBVYo0ySC
Cfc6Wm1uxArfrC+NQ0Ztw2SkQnCjBMCduBWnr92XKcAU2KHIubWuxYxI4SSPU+fJ
Pb3kDtAWKnwvem99q0vSYmwC0jgX3bIgrpVhvWpCrMO500j+dgs+Yt6O0fWsiTlp
C0rqluhl1ZQArUkd0fVlaB5zoRnsntsp531Fe8sMsy+vOqDuElPNAgEFI0tb/2hS
ExJoTn1CBJmLX5GDEkHVbk0eMWpwWHSMUYfPc4KPid39Lb4fjyE5x9/T7T2V3X70
Al6jMeLqZBRPt/kvHbAdOm2OLGCJKTTHlkhCczewW7zbttmKXqWDc4vXsq/HQLms
GjnxqGwHuVr0SLWBbQjDALFLWuWY9U/ZmA87yZQ1Atj8wvMUD7w=
=KB2V
-END PGP SIGNATURE End Message ---

Bug#954482: marked as done (src:pyx3: Autopkgtest failure due to use of py3versions -i)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 00:09:10 +
with message-id 
and subject line Bug#954482: fixed in pyx3 0.15-3
has caused the Debian Bug report #954482,
regarding src:pyx3: Autopkgtest failure due to use of py3versions -i
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.)


-- 
954482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyx3
Version: 0.15-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Note: Using the FTBFS tag because it's the closest we have.

This package failed a recent autopkgtest and this is one of the blockers for
python3-defaults migration.  It failed because python3.7 was installed in the
chroot and the current autopkgtest doesn't handle that.

Autopkgtests should be run for all supported versions.  The package attempts
to do that, but in a way that is unreliable.

Based on a review of the failure log (I have not looked at the package, so
there's a small chance the root cause is different), the autopkgtest uses the
output of py3versions -i to iterate over available python3 versions.  The -i
flag indicates all installed versions.  In many cases python3.7 is still
partially installed, so it is included in the tests, but fails.

The reliable way to do this is add python3-all to your tests depends in
debian/tests/control and change the py3versions call to py3versions -s.  These
two steps will ensure all supported python3 interpreters are fully installed
and that the tests are run against them.

As this is a blocker for getting python3.8 as default python3 into bullseye,
please address this soon.  I'm open to doing NMUs if anyone would like the
support.  Please let me know if you would like for me to do that.

Scott K
--- End Message ---
--- Begin Message ---
Source: pyx3
Source-Version: 0.15-3
Done: Stuart Prescott 

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated pyx3 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: Mon, 23 Mar 2020 10:05:15 +1100
Source: pyx3
Architecture: source
Version: 0.15-3
Distribution: unstable
Urgency: medium
Maintainer: Stuart Prescott 
Changed-By: Stuart Prescott 
Closes: 954482
Changes:
 pyx3 (0.15-3) unstable; urgency=medium
 .
   * Fix autopkgtest failure due to use of py3versions -i, with thanks to Scott
 Kitterman (Closes: #954482).
   * Update Standards-Version to 4.5.0 (no changes required).
   * Add "Rules-Requires-Root: no".
Checksums-Sha1:
 c788c3321c9fd776c104d6920ff49ad01f1787e3 2300 pyx3_0.15-3.dsc
 b3b39e4d4317f69d467bfb7054db8c852219c605 17776 pyx3_0.15-3.debian.tar.xz
 b30a8523491f3180c4f248ae3d14c5ba21dcd02d 10997 pyx3_0.15-3_amd64.buildinfo
Checksums-Sha256:
 4ce33a7ec5b4a316bab57bc683fb63d93bf9e55c1b88ff7a3706de3c2edb4f25 2300 
pyx3_0.15-3.dsc
 9813b3498548d60d28a46cfbf7e2093033a8d24df876149b67a694a83d781c35 17776 
pyx3_0.15-3.debian.tar.xz
 b81c5b834a75d2787e73230ca71959ed536d184f34d1384bf5ec88ffa8701ce0 10997 
pyx3_0.15-3_amd64.buildinfo
Files:
 544129c0c19d7814b2f8ab6fa3c88634 2300 python optional pyx3_0.15-3.dsc
 a5f17cb81c868bdb2074d30084408f6e 17776 python optional 
pyx3_0.15-3.debian.tar.xz
 01a147423ccce86d8638f7a96726d0c0 10997 python optional 
pyx3_0.15-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAl5396IACgkQu8F+uxOW
8vf/TQ/+IuWFptMzstFTuU33+lL3vvmVoma2WyJBKzBxuvB4Cdpzzwua5JnajBdA
0HxwtV7npVfh9xcTjmQZ+qmLWowPz2H8GIZapCAYIKPeDwYcfrDBOw+mA3+tVOZk
wynqLXFLkOKCxoRNy+pj5XrygUTOY9M81V/9b/tjaqeRU/6SY6ivrF1qIkoX0m2q
tkRo7meBAhTefRj7r2Cu3UxxM9hzEplOpEvhsU6t9n0nZDxb4Eyfh9om4WtLegyb
2wfCqyFrkR+jWBbODw5f/buq77BQLKzm1tUwVfN+dk7Z/iXyyg6k0arLLl+Vqlyr
3vsEujnroKHxeujXDgPBcAzQEhGqdZt5QkelCnin0E1qLoDG6/XDfWskdrx31epU
tIhiwHQQglHG2konLiOsljnF+xnW8UhGDECVMl4WCHxLfZy9CkUyWd4xZuKfxvNL
X87gO9QlYHm8cHj8+XpkcmXTI4WNvXEIMNdVAq4h7PGthjEuoEpeVQI11j6CPLgt

Processed: Bug#953749 marked as pending in ceph

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #953749 [src:ceph] ceph: FTBFS on armel, armhf, i386, mips64el, mipsel, 
s390x
Added tag(s) pending.

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

Bug#953749: marked as pending in ceph

[Bernd Zeimetz]

Control: tag -1 pending

Hello,

Bug #953749 in ceph 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/ceph-team/ceph/-/commit/eed9184f97c1a15e0120c447a8a65ec0491d293b


Fix 32bit issues in src/mds/PurgeQueue.cc

mips64el (as reported in the bug report) built fine.
s390x is a buildd issue, gets stuck sometimes for unknown (and not
reproducible) reasons.
Other build issues are fixed hopefully.

Closes: #953749
Thanks: Ivo De Decker


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953749

Bug#954555: marked as done (safeclib: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:37:01 +
with message-id 
and subject line Bug#954555: fixed in safeclib 3.5-3
has caused the Debian Bug report #954555,
regarding safeclib: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
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.)


-- 
954555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: safeclib
Version: 3.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/tests'
> PASS: t_memmove_s
> PASS: t_memcpy_s
> PASS: t_memset_s
> PASS: t_sprintf_s
> PASS: t_strcat_s
> PASS: t_strncat_s
> PASS: t_strncpy_s
> PASS: t_strcpy_s
> PASS: t_strnlen_s
> PASS: t_strtok_s
> PASS: t_sscanf_s
> PASS: t_vsprintf_s
> PASS: t_strerror_s
> PASS: t_strerrorlen_s
> PASS: t_mbsrtowcs_s
> PASS: t_mbstowcs_s
> PASS: t_wcsrtombs_s
> PASS: t_wctomb_s
> PASS: t_wcstombs_s
> PASS: t_wcrtomb_s
> PASS: t_wcsnlen_s
> PASS: t_wcscat_s
> PASS: t_wcscpy_s
> PASS: t_wcsncpy_s
> PASS: t_wcsncat_s
> PASS: t_wmemmove_s
> PASS: t_wmemcpy_s
> PASS: t_wcstok_s
> PASS: t_swprintf_s
> PASS: t_vswprintf_s
> PASS: t_fwprintf_s
> PASS: t_vfwprintf_s
> PASS: t_swscanf_s
> PASS: t_vswscanf_s
> PASS: t_vwscanf_s
> PASS: t_fwscanf_s
> PASS: t_vfwscanf_s
> PASS: t_wscanf_s
> PASS: t_wmemcmp_s
> PASS: t_wcscmp_s
> PASS: t_wcsncmp_s
> PASS: t_wcsicmp_s
> PASS: t_wcsstr_s
> PASS: t_wcsnatcmp_s
> PASS: t_wcsset_s
> PASS: t_wcsnset_s
> PASS: t_wcscoll_s
> PASS: t_wcslwr_s
> PASS: t_wcsupr_s
> FAIL: t_towfc_s
> PASS: t_towlower
> PASS: t_memcpy32_s
> PASS: t_wcsnorm_s
> PASS: t_memcpy16_s
> PASS: t_memcmp_s
> PASS: t_memcmp32_s
> PASS: t_memcmp16_s
> PASS: t_memmove32_s
> PASS: t_memmove16_s
> PASS: t_memset32_s
> PASS: t_memset16_s
> PASS: t_memzero_s
> PASS: t_memzero32_s
> PASS: t_wcsfc_s
> PASS: t_strcasecmp_s
> PASS: t_memzero16_s
> PASS: t_strcasestr_s
> PASS: t_strcmpfld_s
> PASS: t_strcmp_s
> PASS: t_strcpyfldin_s
> PASS: t_strcpyfldout_s
> PASS: t_strcpyfld_s
> PASS: t_strcspn_s
> PASS: t_strfirstchar_s
> PASS: t_strfirstdiff_s
> PASS: t_strfirstsame_s
> PASS: t_strisascii_s
> PASS: t_strisalphanumeric_s
> PASS: t_strisdigit_s
> PASS: t_strishex_s
> PASS: t_strislowercase_s
> PASS: t_strismixed_s
> PASS: t_strispassword_s
> PASS: t_strlastchar_s
> PASS: t_strisuppercase_s
> PASS: t_strlastdiff_s
> PASS: t_towupper
> PASS: t_strlastsame_s
> PASS: t_strljustify_s
> PASS: t_strnatcmp_s
> PASS: t_strnterminate_s
> PASS: t_strpbrk_s
> PASS: t_strremovews_s
> PASS: t_strprefix_s
> PASS: t_strspn_s
> PASS: t_strchr_s
> PASS: t_strrchr_s
> PASS: t_memchr_s
> PASS: t_strstr_s
> PASS: t_memrchr_s
> PASS: t_strtouppercase_s
> PASS: t_strtolowercase_s
> PASS: t_strset_s
> PASS: t_strnset_s
> PASS: t_strzero_s
> PASS: t_strcoll_s
> PASS: t_timingsafe_memcmp
> PASS: t_memccpy_s
> PASS: t_timingsafe_bcmp
> PASS: t_fprintf_s
> PASS: t_vprintf_s
> PASS: t_printf_s
> PASS: t_vfprintf_s
> PASS: t_tmpfile_s
> PASS: t_gets_s
> PASS: t_fopen_s
> PASS: t_freopen_s
> PASS: t_asctime_s
> PASS: t_ctime_s
> PASS: t_gmtime_s
> PASS: t_getenv_s
> PASS: t_localtime_s
> PASS: t_bsearch_s
> PASS: t_qsort_s
> =
>Safe C Library 04062019.0-ga99a05: tests/test-suite.log
> =
> 
> # TOTAL: 124
> # PASS:  123
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: t_towfc_s
> ===
> 
> test_towfc_s 211  Error: towfc(U+A7C7) => A7C7 "A7C8" status=C LATIN CAPITAL 
> LETTER D WITH SHORT STROKE OVERLAY
> test_towfc_s 211  Error: towfc(U+A7C9) => A7C9 "A7CA" status=C LATIN CAPITAL 
> LETTER S WITH SHORT STROKE OVERLAY
> test_towfc_s 211  Error: towfc(U+A7F5) => A7F5 "A7F6" status=C LATIN CAPITAL 
> LETTER REVERSED HALF H
> FAIL t_towfc_s (exit status: 6)
> 
> 
> Testsuite summary for Safe C Library 04062019.0-ga99a05
> 
> # TOTAL: 124
> # PASS:  123
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/test-suite.log
> Please report to https://github.com/rurban/safeclib/issues
> 

Bug#954756: puppet-module-aboe-chrony depends on obsolete transitional package.

[peter green]

Package: puppet-module-aboe-chrony
Version: 0.2.4-2
Severity: serious

puppet-module-aboe-chrony depends on the puppet-common transitional package 
which is no longer built by the puppet source package. Please update your 
dependencies.

Bug#954706: closing 954706

[Antonio Terceiro]

close 954706 2.2.7+dfsg-1
thanks

this has been fixed with the upload of 2.2.7+dfsg-1 yesterday.

Bug#951916: proftpd-mod-vroot: proftpd cannot load mod_vroot

[Hilmar Preuße]

Control: severity -1 important
Control: tags -1 + moreinfo

Am 23.02.2020 um 04:27 teilte Nikolai Lusan mit:

> Trying to run proftpd with mod_vroot. The following error causes hosts using 
> vroot to not be loaded:
> 
>   # service proftpd check-config
>   2020-02-23 13:19:36,841 kiev proftpd[537394]: mod_dso/0.5: unable to 
> load 'mod_vroot.c'; check to see if '/usr/lib/proftpd/mod_vroot.la' exists
>   2020-02-23 13:19:36,841 kiev proftpd[537394]: fatal: LoadModule: error 
> loading module 'mod_vroot.c': No such file or directory on line 93 of 
> '/etc/proftpd/modules.conf'
>   2020-02-23 13:19:36,841 kiev proftpd[537394]: warning: unable to 
> include '/etc/proftpd/modules.conf': Operation not permitted
>   ProFTPD configuration OK
> 
I'm unable to reproduce. Tagging.

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#951916: proftpd-mod-vroot: proftpd cannot load mod_vroot

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #951916 [proftpd-mod-vroot] proftpd-mod-vroot: proftpd cannot load mod_vroot
Severity set to 'important' from 'grave'
> tags -1 + moreinfo
Bug #951916 [proftpd-mod-vroot] proftpd-mod-vroot: proftpd cannot load mod_vroot
Added tag(s) moreinfo.

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

Bug#954555: safeclib: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Adam Borowski]

On Sun, Mar 22, 2020 at 09:24:01AM +0100, Lucas Nussbaum wrote:
> Source: safeclib
> Version: 3.5-2
> Severity: serious
> Justification: FTBFS on amd64

> > FAIL: t_towfc_s
> > ===
> > 
> > test_towfc_s 211  Error: towfc(U+A7C7) => A7C7 "A7C8" status=C LATIN 
> > CAPITAL LETTER D WITH SHORT STROKE OVERLAY
> > test_towfc_s 211  Error: towfc(U+A7C9) => A7C9 "A7CA" status=C LATIN 
> > CAPITAL LETTER S WITH SHORT STROKE OVERLAY
> > test_towfc_s 211  Error: towfc(U+A7F5) => A7F5 "A7F6" status=C LATIN 
> > CAPITAL LETTER REVERSED HALF H
> > FAIL t_towfc_s (exit status: 6)

This is a disagreement between the version of UnicodeData.txt libc has been
built with, and what's shipped in the unicode-data package.  The latter has
been already updated for Unicode 13.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄

Bug#954644: marked as done (proftpd-mod-tar: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:22:51 +0100
with message-id <862c72d7-c54b-6e72-7702-fc15df0cd...@web.de>
and subject line Re: Bug#954644: proftpd-mod-tar: FTBFS: conf.h:57:11: fatal 
error: stropts.h: No such file or directory
has caused the Debian Bug report #954644,
regarding proftpd-mod-tar: FTBFS: conf.h:57:11: fatal error: stropts.h: No such 
file or directory
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.)


-- 
954644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-tar
Version: 0.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-tar prxs -c mod_tar.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_tar.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_tar.c  -fPIC -DPIC -o 
> .libs/mod_tar.o
> In file included from mod_tar.c:27:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-tar_0.4-1_unstable.log

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

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

Am 22.03.2020 um 08:19 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: closing 954706

[Debian Bug Tracking System]

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

> close 954706 2.2.7+dfsg-1
Bug #954706 [src:vagrant] vagrant: FTBFS: Failed to load /dev/null because it 
doesn't contain valid YAML hash
Marked as fixed in versions vagrant/2.2.7+dfsg-1.
Bug #954706 [src:vagrant] vagrant: FTBFS: Failed to load /dev/null because it 
doesn't contain valid YAML hash
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#954526: marked as done (proftpd-mod-msg: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:19:35 +0100
with message-id <6204f1c6-98a9-2e02-ffd2-00ac6612f...@web.de>
and subject line Re: Bug#954526: proftpd-mod-msg: FTBFS: conf.h:57:11: fatal 
error: stropts.h: No such file or directory
has caused the Debian Bug report #954526,
regarding proftpd-mod-msg: FTBFS: conf.h:57:11: fatal error: stropts.h: No such 
file or directory
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.)


-- 
954526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-msg
Version: 0.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-msg prxs -c mod_msg.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_msg.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_msg.c  -fPIC -DPIC -o 
> .libs/mod_msg.o
> In file included from mod_msg.c:28:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-msg_0.5-2_unstable.log

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

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

Am 22.03.2020 um 08:19 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#954567: marked as done (proftpd-mod-fsync: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:17:27 +0100
with message-id 
and subject line Re: Bug#954567: proftpd-mod-fsync: FTBFS: conf.h:57:11: fatal 
error: stropts.h: No such file or directory
has caused the Debian Bug report #954567,
regarding proftpd-mod-fsync: FTBFS: conf.h:57:11: fatal error: stropts.h: No 
such file or directory
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.)


-- 
954567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-fsync
Version: 0.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-fsync prxs -c mod_fsync.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_fsync.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_fsync.c  -fPIC -DPIC -o 
> .libs/mod_fsync.o
> In file included from mod_fsync.c:28:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-fsync_0.3-2_unstable.log

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

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

Am 22.03.2020 um 08:19 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#954575: marked as done (proftpd-mod-dnsbl: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:14:34 +0100
with message-id 
and subject line Re: Bug#954575: proftpd-mod-dnsbl: FTBFS: conf.h:57:11: fatal 
error: stropts.h: No such file or directory
has caused the Debian Bug report #954575,
regarding proftpd-mod-dnsbl: FTBFS: conf.h:57:11: fatal error: stropts.h: No 
such file or directory
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.)


-- 
954575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-dnsbl
Version: 0.1.5-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-dnsbl prxs -c mod_dnsbl.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_dnsbl.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_dnsbl.c  -fPIC -DPIC -o 
> .libs/mod_dnsbl.o
> In file included from mod_dnsbl.h:36,
>  from mod_dnsbl.c:32:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-dnsbl_0.1.5-5_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Am 22.03.2020 um 08:19 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to
> build on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#885468: bumping severity of pygtk bugs

[Moritz Mühlenhoff]

On Sun, Dec 15, 2019 at 10:40:56PM +0100, Moritz Mühlenhoff wrote:
> On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote:
> > Control: severity -1 serious
> > Control: tags -1 -buster
> > 
> > 
> > As part of the Python2 removal, it is our intent that pygtk will be removed 
> > from Testing before the release of Debian 11
> > "Bullseye". Therefore, I am bumping the severity of this bug to Serious to 
> > ensure that there is plenty of warning before
> > the Debian 11 release and to make the eventual removal of pygtk as smooth 
> > as possible.
> 
> The latest pycha 0.8.1 (while ported to Python 3) still uses pygtk2 and there
> are no reverse deps in the archive, shall we remove it?

I filed an RM bug now.

Cheers,
Moritz

Bug#954494: marked as done (proftpd-mod-counter: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:11:53 +0100
with message-id <6f8140a0-892b-3f8b-5eb7-60b855f15...@web.de>
and subject line Re: Bug#954494: proftpd-mod-counter: FTBFS: conf.h:57:11: 
fatal error: stropts.h: No such file or directory
has caused the Debian Bug report #954494,
regarding proftpd-mod-counter: FTBFS: conf.h:57:11: fatal error: stropts.h: No 
such file or directory
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.)


-- 
954494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-counter
Version: 0.6.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-counter prxs -c mod_counter.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_counter.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_counter.c  -fPIC -DPIC 
> -o .libs/mod_counter.o
> In file included from mod_counter.c:28:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-counter_0.6.2-1_unstable.log

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

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

Am 22.03.2020 um 08:19 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#954618: marked as done (proftpd-mod-clamav: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:10:06 +0100
with message-id <2928387a-5a0a-56fe-609b-5ab3ced7c...@web.de>
and subject line Re: Bug#954618: proftpd-mod-clamav: FTBFS: conf.h:57:11: fatal 
error: stropts.h: No such file or directory
has caused the Debian Bug report #954618,
regarding proftpd-mod-clamav: FTBFS: conf.h:57:11: fatal error: stropts.h: No 
such file or directory
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.)


-- 
954618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-clamav
Version: 0.14~rc2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-clamav prxs -c mod_clamav.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_clamav.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_clamav.c  -fPIC -DPIC -o 
> .libs/mod_clamav.o
> In file included from mod_clamav.c:30:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/21/proftpd-mod-clamav_0.14~rc2-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Am 22.03.2020 um 08:18 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#954545: marked as done (proftpd-mod-autohost: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 23:06:59 +0100
with message-id 
and subject line Re: Bug#954545: proftpd-mod-autohost: FTBFS: conf.h:57:11: 
fatal error: stropts.h: No such file or directory
has caused the Debian Bug report #954545,
regarding proftpd-mod-autohost: FTBFS: conf.h:57:11: fatal error: stropts.h: No 
such file or directory
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.)


-- 
954545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-autohost
Version: 0.4-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-autohost prxs -c mod_autohost.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_autohost.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_autohost.c  -fPIC -DPIC 
> -o .libs/mod_autohost.o
> In file included from mod_autohost.c:31:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-autohost_0.4-2_unstable.log

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

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

Am 22.03.2020 um 08:18 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#954561: marked as done (proftpd-mod-case: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 22:54:45 +0100
with message-id <0cde1da8-f02f-401c-a247-94f742d71...@web.de>
and subject line Re: Bug#954561: proftpd-mod-case: FTBFS: conf.h:57:11: fatal 
error: stropts.h: No such file or directory
has caused the Debian Bug report #954561,
regarding proftpd-mod-case: FTBFS: conf.h:57:11: fatal error: stropts.h: No 
such file or directory
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.)


-- 
954561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-case
Version: 0.7+git73896501cf-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-case prxs -c mod_case.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_case.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_case.c  -fPIC -DPIC -o 
> .libs/mod_case.o
> In file included from mod_case.c:23:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/21/proftpd-mod-case_0.7+git73896501cf-1_unstable.log

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

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

Am 22.03.2020 um 08:18 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#954621: marked as done (proftpd-mod-vroot: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 22:51:04 +0100
with message-id <8205386b-f68c-f7a2-62d0-1315b380c...@web.de>
and subject line Re: Bug#954621: proftpd-mod-vroot: FTBFS: conf.h:57:11: fatal 
error: stropts.h: No such file or directory
has caused the Debian Bug report #954621,
regarding proftpd-mod-vroot: FTBFS: conf.h:57:11: fatal error: stropts.h: No 
such file or directory
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.)


-- 
954621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-vroot
Version: 0.9.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg0.html:
> * The obsolete and never-implemented XSI STREAMS header files 
>   and  have been removed.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> DESTDIR=/<>/debian/proftpd-mod-vroot prxs -c mod_vroot.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_vroot.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 
> -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -fno-omit-frame-pointer -Werror=implicit-function-declaration 
> -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_vroot.c  -fPIC -DPIC -o 
> .libs/mod_vroot.o
> In file included from mod_vroot.h:29,
>  from mod_vroot.c:32:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or 
> directory
>57 | # include 
>   |   ^~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-vroot_0.9.8-1_unstable.log

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

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

Am 22.03.2020 um 08:19 teilte Lucas Nussbaum mit:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
Has been solved by BinNMU of proftp (Bug#954449).

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: py2removal bugs severity updates - 2020-03-22 21:36:54.482537+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-urwid is a module and has 0 external rdeps or not in testing
> severity 938759 serious
Bug #938759 [src:urwid] urwid: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-usb is a module and has 0 external rdeps or not in testing
> severity 938294 serious
Bug #938294 [src:pyusb] pyusb: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

[Ondřej Surý]

Control: reassign -1 libdns-export1110

I think I see the problem:

(sid-amd64)root@calcifer:/home/ondrej# ldd /usr/sbin/dhcpd
linux-vdso.so.1 (0x7ffe5236a000)
libeatmydata.so => /usr/lib/x86_64-linux-gnu/libeatmydata.so 
(0x7efc93c96000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x7efc93a64000)
^^^
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x7efc939eb000)
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x7efc939dd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7efc9381a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7efc93815000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 
(0x7efc93527000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7efc93506000)
libdns-export.so.1110 => /lib/x86_64-linux-gnu/libdns-export.so.1110 
(0x7efc932cb000)
^^^
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163 (0x7efc9329c000)
/lib64/ld-linux-x86-64.so.2 (0x7efc93da)

So, dhcpd links with libdns-export.so.1109, but libisccfg-export.so.163 links 
with libdns-export.so.1110.

The symbols in libdns-export.so are not versioned, hence the crash, because 
dns_g_mctx gets initialized
in one library, but the symbol in other library gets used (and not initialized).

A isc-dhcpd binNMU should help right away.  I can also bump the 
libisccfg-export.so.163 SOVERSION,
but it will take longer.

Ondrej
--
Ondřej Surý
ond...@sury.org



> On 22 Mar 2020, at 20:43, Sven Hartge  wrote:
> 
> On 22.03.20 20:38, Ondřej Surý wrote:
> 
>> could you try in isolated environment try installing isc-dhcp and bind
>> 9.16 and check the libraries that the crashing process links (using ldd)
>> and perhaps generate a strace?
>> 
>> That is if you have time right now, I won’t have time to sit at computer
>> until tomorrow morning (CET).
> 
> Same for me. It will take until tomorrow CET morning before I can do that.
> 
> I took a look at the ldd output while debugging this, but failed to make
> a note of it and it already scrolled outside of my screen buffer
> unfortunately.
> 
> 
> Grüße,
> Sven.
> 



signature.asc
Description: Message signed with OpenPGP

Processed: Re: Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libdns-export1110
Bug #954736 [bind9] Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT
Bug reassigned from package 'bind9' to 'libdns-export1110'.
No longer marked as found in versions bind9/1:9.16.1-2.
Ignoring request to alter fixed versions of bug #954736 to the same values 
previously set

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

Bug#954693: marked as done (node-promise: FTBFS: Error: Cannot find module 'acorn/dist/walk')

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 20:46:05 +
with message-id 
and subject line Bug#954693: fixed in node-promise 8.1.0-1
has caused the Debian Bug report #954693,
regarding node-promise: FTBFS: Error: Cannot find module 'acorn/dist/walk'
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> node build
> internal/modules/cjs/loader.js:638
> throw err;
> ^
> 
> Error: Cannot find module 'acorn/dist/walk'
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:636:15)
> at Function.Module._load (internal/modules/cjs/loader.js:562:25)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at Object. (/<>/build.js:6:12)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/node-promise_8.0.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: node-promise
Source-Version: 8.1.0-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-promise 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, 22 Mar 2020 20:58:55 +0100
Source: node-promise
Architecture: source
Version: 8.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 914614 954693
Changes:
 node-promise (8.1.0-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Bump debhelper from old 10 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update Vcs-* headers from URL redirect.
   * Use canonical URL in Vcs-Git.
 .
   [ Xavier Guimard ]
   * Declare compliance with policy 4.5.0
   * Use pkg-js-tools auto install
   * New upstream version 8.1.0 (Closes: #914614)
   * Add patch for acorn 6 (Closes: #954693)
   * Add dependency to node-asap
   * Add "Rules-Requires-Root: no"
   * Add debian/gbp.conf
Checksums-Sha1: 
 3cf8c5aa61811a7498cb2dc9234442fe641c8f51 2054 node-promise_8.1.0-1.dsc
 93b1725f96096ea06547a1925146720aaf5be857 17416 node-promise_8.1.0.orig.tar.gz
 8cc45e8767921dc89ab71e7f63115d6e957a6141 26324 
node-promise_8.1.0-1.debian.tar.xz
Checksums-Sha256: 
 8f9bfe9defac7c17ba22ca33bf9c188d81e830732700afc922ab571579906b1c 2054 
node-promise_8.1.0-1.dsc
 4554cde3267249e9f1630f63276d0413457440d7f7b974da3d4c20a47e927fd8 17416 
node-promise_8.1.0.orig.tar.gz
 9a1cc81b2d50844bb6f6cc27d7354dc1184ec07e06f37b05ac40246c22561b41 26324 
node-promise_8.1.0-1.debian.tar.xz
Files: 
 4d7e

Bug#954720: marked as done (node-entities: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 20:45:53 +
with message-id 
and subject line Bug#954720: fixed in node-entities 2.0.0+dfsg-4
has caused the Debian Bug report #954720,
regarding node-entities: FTBFS: dh_auto_test: error: /bin/sh -e 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
954720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-entities
Version: 2.0.0+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tsc
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
> 
> Run tests with Mocha
> 
> Rules & Behavior
>   --allow-uncaught   Allow uncaught errors to propagate
> [boolean]
>   --async-only, -A   Require all tests to use a callback (async) or
>  return a Promise  
> [boolean]
>   --bail, -b Abort ("bail") after first test failure   
> [boolean]
>   --check-leaks  Check for global variable leaks   
> [boolean]
>   --delayDelay initial execution of root suite 
> [boolean]
>   --exit Force Mocha to quit after tests complete  
> [boolean]
>   --forbid-only  Fail if exclusive test(s) encountered 
> [boolean]
>   --forbid-pending   Fail if pending test(s) encountered   
> [boolean]
>   --global, --globalsList of allowed global variables
> [array]
>   --retries  Retry failed tests this many times 
> [number]
>   --slow, -s Specify "slow" test threshold (in milliseconds)
>   [string] [default: 
> 75]
>   --timeout, -t, --timeouts  Specify test timeout threshold (in milliseconds)
> [string] [default: 
> 2000]
>   --ui, -u   Specify user interface[string] [default: 
> "bdd"]
> 
> Reporting & Output
>   --color, -c, --colors Force-enable color output  
> [boolean]
>   --diffShow diff on failure
>[boolean] [default: 
> true]
>   --full-trace  Display full stack traces  
> [boolean]
>   --growl, -G   Enable Growl notifications 
> [boolean]
>   --inline-diffsDisplay actual/expected 
> differences
> inline within each string  
> [boolean]
>   --reporter, -RSpecify reporter to use
>   [string] [default: 
> "spec"]
>   --reporter-option, --reporter-options,Reporter-specific options
>   -O()   
> [array]
> 
> Configuration
>   --config   Path to config file   [string] [default: (nearest rc 
> file)]
>   --opts Path to `mocha.opts` (DEPRECATED)
>  [string] [default: 
> "./test/mocha.opts"]
>   --package  Path to package.json for config
> [string]
> 
> File Handling
>   --extension  File extension(s) to load   [array] [default: 
> js]
>   --file   Specify file(s) to be loaded prior to root suite
>execution   [array] [default: 
> (none)]
>   --ignore, --exclude  Ignore file(s) or glob pattern(s)
>[array] [default: 
> (none)]
>   --recursive  Look for tests in subdirectories
> [boolean]
>   --require, -rRequire module  [array] [default: 
> (none)]
>   --sort, -S   Sort test files 
> [boolean]
>

Bug#954694: marked as done (twitter-bootstrap4: FTBFS: Error: Too many arguments.)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 20:46:55 +
with message-id 
and subject line Bug#954694: fixed in twitter-bootstrap4 4.4.1+dfsg1-2
has caused the Debian Bug report #954694,
regarding twitter-bootstrap4: FTBFS: Error: Too many arguments.
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.)


-- 
954694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twitter-bootstrap4
Version: 4.4.1+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p dist/css dist/js dist/tmp
> sassc -m auto scss/bootstrap.scss dist/tmp/bootstrap.css
> Error: Too many arguments.
> See 'sassc -h'
> make[1]: *** [debian/rules:8: override_dh_auto_build] Error 64

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/22/twitter-bootstrap4_4.4.1+dfsg1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: twitter-bootstrap4
Source-Version: 4.4.1+dfsg1-2
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated twitter-bootstrap4 
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, 22 Mar 2020 20:45:44 +0100
Source: twitter-bootstrap4
Architecture: source
Version: 4.4.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 954694
Changes:
 twitter-bootstrap4 (4.4.1+dfsg1-2) unstable; urgency=medium
 .
   * Update sassc use: replace "-m auto" by "--sourcemap=auto" (Closes: #954694)
   * Declare compliance with policy 4.5.0
Checksums-Sha1: 
 f3ff44c797b2b5d95ad9e0164a785b1eabbdb6c9 2299 
twitter-bootstrap4_4.4.1+dfsg1-2.dsc
 cc580489f5b72da7550a5a5763380cbc7cc0ee2a 18528 
twitter-bootstrap4_4.4.1+dfsg1-2.debian.tar.xz
Checksums-Sha256: 
 03e1e7ac4b2616fd85dd0ece9f66e68c60e46587cb3914a4b4884be183c9d201 2299 
twitter-bootstrap4_4.4.1+dfsg1-2.dsc
 2a7995ae64eed3ba91932b663340fa55513dbef540bff5f38db1738ddb3f823e 18528 
twitter-bootstrap4_4.4.1+dfsg1-2.debian.tar.xz
Files: 
 8ab8595cbb37d13b1553d86e92af260c 2299 javascript optional 
twitter-bootstrap4_4.4.1+dfsg1-2.dsc
 690de7f597262be4ffe81d52f2c5e02e 18528 javascript optional 
twitter-bootstrap4_4.4.1+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl53wVgACgkQ9tdMp8mZ
7umrYg/+OJKWXMKJcq99clBs0D6mveRCaV0GMWdnfT+QhzeprPgkHk7YyKaDNeb+
PXuka6dxcvFnr9cYg3pP4ofLMlEf2/jFlJGB5k22uSTUn+b6PyFVNDr6nrtrGygu
UXqf34Y4epkM2JulhstwxeyCBPKmtQ9/kriBX+/KOOqwqdFv3nc/dS7pcSZU4akB
2wjyFCnOFmNuI/7gDvZNLVpKeXzYx4eKhgw2Vc3hCVugDskrcOAUWf1j+5wPRQVC
myf+5A1gccIG+KseFRYXiP9/JDu3gBSz1iaE8De3O0azv3gc+U4OHdlYpL8UbSpG
FopYAPwikJ9zH68AHIz+qubtFxN2Q+fbCmpZUNTAdgKtRNiqXdmMLjFKRAfpSVW5
88106rGJda/ClWU+kOUwhSE/JJujPgh9STHhk/YXWqg6aljPE+ryeMQw+Lzn0XAu
RSH7Za4zcUQSlfWKyHByWKNT0DPQs5iYabJ1O6uFqKZm1JHCc7fe/cOwWs6yw/8a
U9V0ErOwv7qrk+Trob1qzSG0avLn2sZX+d+Fbn9LKm8hTuQz0DvbCY1kT2RgVd65
vQruCthXPzH7mEZJZoc8PNW2b2I38XpwBC7v2M7GFcfBmBBuvPyxxTAcYF5iyoNt
DuTu4dmYjd+J0U3dj45dbww0JVvS4pH55A3RXMekuqCBvPhdcLQ=
=TBsR
-END PGP SIGNATURE End Message ---

Bug#934842: marked as done (libbusiness-hours-perl: FTBFS in stretch)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 20:41:55 +
with message-id 
and subject line Bug#934842: fixed in libbusiness-hours-perl 0.13-0+deb9u1
has caused the Debian Bug report #934842,
regarding libbusiness-hours-perl: FTBFS in stretch
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.)


-- 
934842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libbusiness-hours-perl
Version: 0.12-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Business::Hours
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cp lib/Business/Hours.pm blib/lib/Business/Hours.pm
Manifying 1 pod document
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" 
"-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef 
*Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t

#   Failed test at t/1-business-hours.t line 16.
#  got: '0'
# expected: '162000'

#   Failed test 'Got seconds'
#   at t/1-business-hours.t line 24.

#   Failed test at t/1-business-hours.t line 27.
#  got: '0'
# expected: '162000'

#   Failed test at t/1-business-hours.t line 50.
#  got: '378000'
# expected: '32400'
Set::IntSpan::_copy_run_list: Bad order 2: 72000--1
 at /<>/blib/lib/Business/Hours.pm line 270.
# Looks like you planned 17 tests but ran 12.
# Looks like you failed 4 tests of 12 run.
# Looks like your test exited with 255 just after 12.
t/1-business-hours.t .. 
1..17
ok 1 - use Business::Hours;
ok 2
ok 3
not ok 4
ok 5
not ok 6 - Got seconds
not ok 7
not ok 8
ok 9
ok 10
ok 11
ok 12
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 9/17 subtests 
t/2-holidays.t  
1..6
ok 1 - use Business::Hours;
ok 2 - An object of class 'Business::Hours' isa 'Business::Hours'
ok 3 - no holidays by default
ok 4 - set some holidays
ok 5 - skipped new year holiday
ok 6 - skipped new year holiday
ok
t/99-pod-coverage.t ... skipped: Test::Pod::Coverage 1.00 required for testing 
POD coverage
t/99-pod.t  skipped: Test::Pod 1.00 required for testing POD

Test Summary Report
---
t/1-business-hours.t (Wstat: 65280 Tests: 12 Failed: 4)
  Failed tests:  4, 6-8
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 17 tests but ran 12.
Files=4, Tests=18,  1 wallclock secs ( 0.05 usr  0.01 sys +  0.23 cusr  0.02 
csys =  0.31 CPU)
Result: FAIL
Failed 1/4 test programs. 4/18 subtests failed.
Makefile:819: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbusiness-hours-perl.html

where you can get another build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: libbusiness-hours-perl
Source-Version: 0.13-0+deb9u1
Done: Adrian Bunk 

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

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please 

Bug#830726: marked as done (xtrlock: CVE-2016-10894: xtrlock does not block multitouch events)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 20:42:49 +
with message-id 
and subject line Bug#830726: fixed in xtrlock 2.8+deb9u1
has caused the Debian Bug report #830726,
regarding xtrlock: CVE-2016-10894: xtrlock does not block multitouch events
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.)


-- 
830726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtrlock
Version: 2.8
Severity: normal
Tags: upstream

Dear Maintainer,

xtrlock appears not to block multitouch events when the session is locked, so
that any user stumbling upon a locked session can still input multitouch events.

One could imagine that this could constitute a security vulnerability (requiring
physical access to the machine).

Steps to reproduce (on a computer with a suitably configured touchscreen):

1. Open chromium (my example of a program that processes multitouch events) and
put it in fullscreen mode.
2. Check that you can pinch and zoom (put two fingers of the screen and move
them closer or further apart to change the zoom level).
3. Run xtrlock to lock the session.
4. With xtrlock running, put one finger on the screen and leave it there (the
mouse pointer with the xtrlock lock icon follows that finger). While doing this,
perform the pinch and zoom with two other fingers.

Observed result:

The pinch and zoom is taken into account by chromium even though the session is
locked.

Expected result:

The event should not be seen by chromium while the session is locked.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xtrlock depends on:
ii  libc6 2.22-13
ii  libx11-6  2:1.6.3-1

xtrlock recommends no packages.

xtrlock suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: xtrlock
Source-Version: 2.8+deb9u1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated xtrlock 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, 16 Jan 2020 16:00:52 +
Source: xtrlock
Binary: xtrlock
Architecture: source
Version: 2.8+deb9u1
Distribution: stretch
Urgency: high
Maintainer: Matthew Vernon 
Changed-By: Chris Lamb 
Description:
 xtrlock- Minimal X display lock program
Closes: 830726
Changes:
 xtrlock (2.8+deb9u1) stretch; urgency=high
 .
   * CVE-2016-10894: Attempt to grab multitouch devices which are not
 intercepted via XGrabPointer.
 .
 xtrlock did not block multitouch events so an attacker could still input
 and thus control various programs such as Chromium, etc. via so-called
 "multitouch" events such as pan scrolling, "pinch and zoom", or even being
 able to provide regular mouse clicks by depressing the touchpad once and
 then clicking with a secondary finger.
 .
 This fix does not the situation where Eve plugs in a multitouch device
 *after* the screen has been locked. For more information on this angle,
 please see . (Closes: #830726)
Checksums-Sha1:
 3868359c01d305263ab4a2d75a3b782a18947bcc 1457 xtrlock_2.8+deb9u1.dsc
 e3a12ff00c5e7b01ab5d093eafa1e26defb24f0b 21823 xtrlock_2.8+deb9u1.tar.gz
 28f7890c85279f310c5256e3174e4760aba36072 5503 
xtrlock_2.8+deb9u1_amd64.buildinfo
Checksums-Sha256:
 0c165522c0f09e3ca44ccd26e1bc24ae6496aee76c4ae1216805b8127a4e3387 1457 
xtrlock_2.8+deb9u1.dsc
 33c26b5c1e345c6840e54f636316fa43de230872dce235f48cc81e1ceaae5bbe 21823 
xtrlock_2.8+deb9u1.tar.gz
 d874d380feb66b97c89e42553a149a2d17e6e58643f05094af8d2b4b19e9ec56 5503 
xtrlock_2.8+deb9u1_amd64.buildinfo
Files:
 

Processed: Re: Bug#954573: quilt: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

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

> reopen 954573
Bug #954573 {Done: Lucas Nussbaum } [src:quilt] quilt: FTBFS: 
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Bug reopened
Ignoring request to alter fixed versions of bug #954573 to the same values 
previously set
> severity 954573 important
Bug #954573 [src:quilt] quilt: FTBFS: dh_auto_test: error: make -j4 check 
VERBOSE=1 returned exit code 2
Severity set to 'important' from 'serious'
> retitle 954573 quilt: FTBFS randomly in faildiff.test
Bug #954573 [src:quilt] quilt: FTBFS: dh_auto_test: error: make -j4 check 
VERBOSE=1 returned exit code 2
Changed Bug title to 'quilt: FTBFS randomly in faildiff.test' from 'quilt: 
FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2'.
> thanks
Stopping processing here.

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

Bug#954689: ocsinventory-server: FTBFS: Error: Too many arguments.

[Xavier]

Le 22/03/2020 à 14:56, Lucas Nussbaum a écrit :
> Source: ocsinventory-server
> Version: 2.5+dfsg1-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200322 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
>> [...]
>> sassc -m auto --style compressed 
>> ocsreports/libraries/select2/css/select2.css 
>> ocsreports/libraries/select2/css/select2.min.css
>> Error: Too many arguments.
>> See 'sassc -h'
>> make[1]: *** [debian/rules:19: override_dh_auto_build] Error 64

sassc changed: '-m auto' should be replaced by '--sourcemap=auto'

Bug#953488: marked as done (powder: binaries for non-free not auto-built)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 21:17:21 +0100
with message-id <20200322201721.gb8...@angband.pl>
and subject line Re: powder_118+dfsg1-3_amd64.changes ACCEPTED into unstable, 
unstable
has caused the Debian Bug report #953488,
regarding powder: binaries for non-free not auto-built
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.)


-- 
953488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:powder
version: 118+dfsg1-3
severity: serious
tags: ftbfs

Hi,

The latest upload of powder to unstable has no binaries.
The buildds are not building it, because it is in non-free.

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary maintainer uploads for
sources in contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
On Sun, Mar 22, 2020 at 08:11:48PM +, Debian FTP Masters wrote:
> Accepted:

> Binary: powder powder-dbgsym
> Architecture: amd64
> Version: 118+dfsg1-3

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄--- End Message ---

Processed: Bug#954693 marked as pending in node-promise

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954693 [src:node-promise] node-promise: FTBFS: Error: Cannot find module 
'acorn/dist/walk'
Added tag(s) pending.

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

Bug#954693: marked as pending in node-promise

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #954693 in node-promise 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/node-promise/-/commit/784261819f8745a49170800f4345bd6b2bf69995


Add patch for acorn 6

Closes: #954693


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954693

Bug#954236: marked as done (python-bleach: CVE-2020-6816: mutation XSS)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 19:52:17 +
with message-id 
and subject line Bug#954236: fixed in python-bleach 3.1.2-0+deb10u1
has caused the Debian Bug report #954236,
regarding python-bleach: CVE-2020-6816: mutation XSS
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.)


-- 
954236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-bleach
Version: 3.1.1-0+deb10u1
Severity: serious
Tags: security upstream

>From the upstream CHANGES for 3.1.2, which I just noticed:

**Security fixes**

* ``bleach.clean`` behavior parsing embedded MathML and SVG content
  with RCDATA tags did not match browser behavior and could result in
  a mutation XSS.

  Calls to ``bleach.clean`` with ``strip=False`` and ``math`` or
  ``svg`` tags and one or more of the RCDATA tags ``script``,
  ``noscript``, ``style``, ``noframes``, ``iframe``, ``noembed``, or
  ``xmp`` in the allowed tags whitelist were vulnerable to a mutation
  XSS.

  This security issue was confirmed in Bleach version v3.1.1. Earlier
  versions are likely affected too.

  Anyone using Bleach <=v3.1.1 is encouraged to upgrade.

  https://bugzilla.mozilla.org/show_bug.cgi?id=1621692

The mozilla bug is not public

Scott K
--- End Message ---
--- Begin Message ---
Source: python-bleach
Source-Version: 3.1.2-0+deb10u1
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated python-bleach 
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, 19 Mar 2020 00:14:11 -0400
Source: python-bleach
Architecture: source
Version: 3.1.2-0+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Closes: 954236
Changes:
 python-bleach (3.1.2-0+deb10u1) buster-security; urgency=high
 .
   * New upstream security release (Closes: #954236)
 - Addresses CVE-2020-6816
Checksums-Sha1:
 897fe2266b40310ab04611d91aa5698d0592e03b 2923 python-bleach_3.1.2-0+deb10u1.dsc
 6252011e6a456c7440e1ac7c1ca50c15b687ccda 159862 python-bleach_3.1.2.orig.tar.gz
 a50e015e7eaf23b7a9d122a3eccc4b260aa5490e 5268 
python-bleach_3.1.2-0+deb10u1.debian.tar.xz
 9f4ed8ebd3a62506f32c3416399a55d11102ff11 7497 
python-bleach_3.1.2-0+deb10u1_source.buildinfo
Checksums-Sha256:
 1d7fdde1794c1c21338ab72624d6e42f742cde24a0ac1d215fffc3abcb9d5810 2923 
python-bleach_3.1.2-0+deb10u1.dsc
 9e4853bb0d84cb649a95ec2423214afe47e340b1fe80d089f5c30170f6fa3caf 159862 
python-bleach_3.1.2.orig.tar.gz
 261ca2d07938c4e4a3229bcff9c4d4aab3a81b020bacd2bb156baf431744ffbf 5268 
python-bleach_3.1.2-0+deb10u1.debian.tar.xz
 dd694b4b58aae6d52da445f9c10a772e7ef51bbcd0ae9538d4732f3ca3bb0458 7497 
python-bleach_3.1.2-0+deb10u1_source.buildinfo
Files:
 13ca5c577f888751e7d2891035fd799a 2923 python optional 
python-bleach_3.1.2-0+deb10u1.dsc
 cf28379755fd1ac4fe399e1c188d1ba0 159862 python optional 
python-bleach_3.1.2.orig.tar.gz
 404ba1dba7abbe9955d006944fe05bd2 5268 python optional 
python-bleach_3.1.2-0+deb10u1.debian.tar.xz
 0c96eb79364b3675e7972fcc6a7f23e0 7497 python optional 
python-bleach_3.1.2-0+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl51AvUACgkQeNfe+5rV
mvEPERAAnLjqZY7Ewk49gPeFb2eDJ/lYGd7YMEu02MKuQSqAcMMiWy/0aq08j0GX
HYyIqXcsG2Sf2AM/PN/LOc7udMV1yAukJnQQVA/khbEhQBVdSO+1yRCvkFqkX4Ry
dvcMjvw8P1bME9V4f6HmuBZQaNfLRrrIWA1uFri2HlCV8lcKhaMZ4lGcEZg4qGFx
9DjFKhN4L0dwywlRCB8HPIn8w6S7te30My+4B0TJrV28OTA8j+eFPQja+/NzskHf
FC53+DV4Sl58H9g8G7siHp3GtH4vs4pcvNv9yPSyW0z0mB1jHm9wpv8kxY4hsdM+
9gGjhyG4pLXZWNLxwmlJg+uv1rYkEOzgSODmjUaesjCx+nM0j4KgIRR5N1gx9a+s
pULuo/qB2TFAN784IexIIuctxC7kMEgnvCaEvteUjBDuAcBA+uHXkcLgvCaXNCvh
3W2UbvwRWP6hfbdlOQiT/mIqUgN/TNw5E7hAa7ntxXAmczDAb/mxBlaVPnUdfQKF
yWbjsbNoSgvNbFol2tD8lSHDqVG/zZKbJKNY+UZHCAIukAppLFn+lkky+T38RKhJ
8ZmB0T77KsXNNCMvbbGteYwH3jXdYjqtUX6au+ybIecov0XZwkMXFHbxLqzfTojB

Bug#953322: marked as done (src:sec: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 19:49:59 +
with message-id 
and subject line Bug#953322: fixed in sec 2.8.2-1.1
has caused the Debian Bug report #953322,
regarding src:sec: fails to migrate to testing for too long
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.)


-- 
953322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sec
Version: 2.8.1-1
Severity: serious
Control: fixed -1 2.8.2-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sec
Source-Version: 2.8.2-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated sec 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: Sat, 07 Mar 2020 19:52:57 +0100
Source: sec
Architecture: source
Version: 2.8.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jaakko Niemi 
Changed-By: Paul Gevers 
Closes: 953322
Changes:
 sec (2.8.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #953322)
Checksums-Sha1:
 0648bd5fe1aa6721564739504d50d1109b78eb59 1157 sec_2.8.2-1.1.dsc
 d729d4d32d9b71063c9a0a80ea3a7d3b197d593f 147422 sec_2.8.2-1.1.tar.gz
Checksums-Sha256:
 a8730894780d681797f9c9866b197815f5394fcd1cb90d0a51f0d15e701eacba 1157 
sec_2.8.2-1.1.dsc
 781b4695adb387c5156812a54b6f2c656544e0b450a60e34248e1fad1db0bb15 147422 
sec_2.8.2-1.1.tar.gz
Files:
 b671acc684a4ea951950a3f56e2e1339 1157 utils optional sec_2.8.2-1.1.dsc
 34c3f2170a692b858163995cdc2a5663 147422 utils optional sec_2.8.2-1.1.tar.gz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl5j7cMACgkQnFyZ6wW9
dQrA2Qf+I2WBEHpWkthLMVnZCzOTvoww3QhQiIjpMM0t1x6M6M5d3eGPalirY+yB
fk+MEkw7NJnJi6jJgtJmWXDAjwfaB3b1nsJTfsivQ3SWmBm+dcL5314b8mGdjvDK
VvV8Je8h5JOyuZOShtl6D2XYyogwRbCuUzInTNqF6/2M+QLpoRASEa4YGVGJ7Y/z
O0ZiTYcf5LyiOlGILc6m0UKlnv1uumAkkrHmKKeDK+EhiT/BIAUcmMc+k7kZQUtJ
AVmQ6Ih76ISuZuJen3aehTO5kaVTpeSiqJJqUyA++mijyBYhZzDmM5fcSahAwDkA
Vl/rDp7/r1ixlfbUJ9aiJtZHgkP7iQ==
=iS7p
-END PGP SIGNATURE End Message ---

Bug#953320: marked as done (src:python-sievelib: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 19:49:52 +
with message-id 
and subject line Bug#953320: fixed in python-sievelib 1.1.1-3.1
has caused the Debian Bug report #953320,
regarding src:python-sievelib: fails to migrate to testing for too long
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.)


-- 
953320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-sievelib
Version: 1.1.0-1
Severity: serious
Control: fixed -1 1.1.1-3
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-sievelib
Source-Version: 1.1.1-3.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated python-sievelib 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: Sat, 07 Mar 2020 19:52:38 +0100
Source: python-sievelib
Architecture: source
Version: 1.1.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Paul Gevers 
Closes: 953320
Changes:
 python-sievelib (1.1.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #953320)
Checksums-Sha1:
 7e6854ee5d5569cce468920687a7dd005ec0f364 1942 python-sievelib_1.1.1-3.1.dsc
 28f6a75063085e7626a517ed61af6c1787f61449 3304 
python-sievelib_1.1.1-3.1.debian.tar.xz
Checksums-Sha256:
 4362c5e665a7c15aac130fb104982e9b0dc36d638800f466b8af4f6875c1bfb8 1942 
python-sievelib_1.1.1-3.1.dsc
 98479ed8eac5dc9735cd81753f0fff98a476b168e86662880ab11d19fedcead6 3304 
python-sievelib_1.1.1-3.1.debian.tar.xz
Files:
 57d70730139efb859322e241578d1c93 1942 python optional 
python-sievelib_1.1.1-3.1.dsc
 933e59e10ed9452aa5261f3860038410 3304 python optional 
python-sievelib_1.1.1-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl5j7dYACgkQnFyZ6wW9
dQqTOQgAtQn90lV9fnbKyAtYy/t5hnFQ6m0rW75zV0esDAkqqym6dMgCDSpKpi1b
lIcs2eYYmXUgsfFulgquyQuwmOeTfOw/n5uaTK2mSJcqVt9hn60sM5AMOwnH9IrD
cswQNjdHVxwmg+wua3KKqhtbaQsasxSX6tUIJypYECHeY96vJi6VJs3/Uq7glabH
MjRQmb463PgbSNq5Wo+F62X/9/ptSSdNBwROtGnLHJa7cF0oaEmo81EebuuJw418
38dpu4ecsD/Z7vZYe++G4stT/vQHzcDyiFCY3ArPUZxmKXjn3RzmJr3E+NBcfAum

Processed: Bug#954694 marked as pending in twitter-bootstrap4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954694 [src:twitter-bootstrap4] twitter-bootstrap4: FTBFS: Error: Too many 
arguments.
Added tag(s) pending.

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

Bug#954719: [Pkg-javascript-devel] Bug#954719: node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

[Xavier]

Control: fixed -1 0.4.10-5

Le 22/03/2020 à 16:27, Lucas Nussbaum a écrit :
> Source: node-immutable-tuple
> Version: 0.4.10-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200322 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Bug#954694: marked as pending in twitter-bootstrap4

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #954694 in twitter-bootstrap4 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/twitter-bootstrap4/-/commit/f8724b3fa1d6b58437c29ad3d8202347c946d4b4


Update sassc use: replace "-m auto" by "--sourcemap=auto"

Closes: #954694


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954694

Processed: Re: [Pkg-javascript-devel] Bug#954719: node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.4.10-5
Bug #954719 [src:node-immutable-tuple] node-immutable-tuple: FTBFS: 
dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1
Marked as fixed in versions node-immutable-tuple/0.4.10-5.

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

Bug#954719: marked as done (node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 19:49:30 +
with message-id 
and subject line Bug#954719: fixed in node-immutable-tuple 0.4.10-6
has caused the Debian Bug report #954719,
regarding node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
954719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-immutable-tuple
Version: 0.4.10-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./scripts/build.sh
> (!) You have passed an unrecognized option
> Unknown input option: sourcemap. Allowed options: acorn, acornInjectPlugins, 
> cache, chunkGroupingSize, context, experimentalCacheExpiry, 
> experimentalOptimizeChunks, experimentalTopLevelAwait, external, 
> inlineDynamicImports, input, manualChunks, moduleContext, onwarn, perf, 
> plugins, preserveModules, preserveSymlinks, shimMissingExports, treeshake, 
> watch
> 
> /<>/src/tuple.js → ../dist/tuple.js...
> created ../dist/tuple.js in 80ms
> (!) You have passed an unrecognized option
> Unknown input option: sourcemap. Allowed options: acorn, acornInjectPlugins, 
> cache, chunkGroupingSize, context, experimentalCacheExpiry, 
> experimentalOptimizeChunks, experimentalTopLevelAwait, external, 
> inlineDynamicImports, input, manualChunks, moduleContext, onwarn, perf, 
> plugins, preserveModules, preserveSymlinks, shimMissingExports, treeshake, 
> watch
> 
> /<>/src/tuple.js → ../dist/tuple.mjs...
> created ../dist/tuple.mjs in 78ms
> uglifyjs dist/tuple.js -o dist/tuple.min.js
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
> 
> Run tests with Mocha
> 
> Rules & Behavior
>   --allow-uncaught   Allow uncaught errors to propagate
> [boolean]
>   --async-only, -A   Require all tests to use a callback (async) or
>  return a Promise  
> [boolean]
>   --bail, -b Abort ("bail") after first test failure   
> [boolean]
>   --check-leaks  Check for global variable leaks   
> [boolean]
>   --delayDelay initial execution of root suite 
> [boolean]
>   --exit Force Mocha to quit after tests complete  
> [boolean]
>   --forbid-only  Fail if exclusive test(s) encountered 
> [boolean]
>   --forbid-pending   Fail if pending test(s) encountered   
> [boolean]
>   --global, --globalsList of allowed global variables
> [array]
>   --retries  Retry failed tests this many times 
> [number]
>   --slow, -s Specify "slow" test threshold (in milliseconds)
>   [string] [default: 
> 75]
>   --timeout, -t, --timeouts  Specify test timeout threshold (in milliseconds)
> [string] [default: 
> 2000]
>   --ui, -u   Specify user interface[string] [default: 
> "bdd"]
> 
> Reporting & Output
>   --color, -c, --colors Force-enable color output  
> [boolean]
>   --diffShow diff on failure
>[boolean] [default: 
> true]
>   --full-trace  Display full stack traces  
> [boolean]
>   --growl, -G   Enable Growl notifications 
> [boolean]
>   --inline-diffsDisplay actual/expected 
> differences
> inline within each string  
> [boolean]
>   --reporter, -RSpecify reporter to use
>   [string] [default: 
> "spec"]
>   --reporter-option, --reporter-options,Reporter-specific options
>   -O  

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

[Ondřej Surý]

The src:bind9 package doesn’t even provide -dev package, so you are still 
compiling against 9.11.

Ondrej
--
Ondřej Surý 

> On 22 Mar 2020, at 20:09, Sven Hartge  wrote:
> 
> On 22.03.20 19:07, Sven Hartge wrote:
> 
>> Interestingly, isc-dhcp-server 4.4.1 does not even compile against the
>> current 9.16 libs from Sid right now. Something is very broken here.
> 
> I have to correct that part. It seems my checkout from Salsa was wrong,
> as recompiling the source package works.
> 
> Grüße,
> Sven.
> 

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

[Ondřej Surý]

> On 22 Mar 2020, at 19:39, Sven Hartge  wrote:
> 
> Interestingly, isc-dhcp-server 4.4.1 does not even compile against the
> current 9.16 libs from Sid right now. Something is very broken here.

It should not. There’s bind9-libs compatibility package for isc-dhcp and 
others. Let’s keep the bug open till we find the cause. I might do a second 
upload with “Breaks:” to prevent people installing it.

Ondrej
--
Ondřej Surý 

Bug#954686: marked as done (mapsforge: FTBFS: Could not resolve :osmosis-core-0.47:.)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 19:21:44 +
with message-id 
and subject line Bug#954686: fixed in mapsforge 0.13.0+dfsg.1-2
has caused the Debian Bug report #954686,
regarding mapsforge: FTBFS: Could not resolve :osmosis-core-0.47:.
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.)


-- 
954686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mapsforge
Version: 0.13.0+dfsg.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Set version string correctly
> if [ ! -f build.gradle.debsave ]; then \
>   sed -i.debsave 's/master-SNAPSHOT/0.13.0/' build.gradle ;\
> fi
> dh_auto_configure
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=gradle
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=mapsforge -Dfile.encoding=UTF-8 
> --parallel --max-workers=4 jar
> Initialized native services in: /<>/.gradle/native
> Using 4 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@7c7d3c46
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@7c7d3c46
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@f713686
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access using Lookup on 
> org.gradle.internal.reflect.JavaMethod 
> (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class 
> java.lang.ClassLoader
> WARNING: Please consider reporting this to the maintainers of 
> org.gradle.internal.reflect.JavaMethod
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@7377781e
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
>   Settings file found (/<>/settings.gradle), but 
> rootProject.name isn't defined
>   Root project name not defined in settings.gradle, defaulting to 
> 'mapsforge' instead of the name of the root directory 
> 'mapsforge-0.13.0+dfsg.1'
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'mapsforge', project ':mapsforge-core', 
> project ':mapsforge-map', project ':mapsforge-map-awt', project 
> ':mapsforge-map-reader', project ':mapsforge-map-writer', project 
> ':mapsforge-poi', project ':mapsforge-samples-awt', project 
> ':mapsforge-themes']
>   Keep-alive timer started
>   Adding Debian repository to project 'mapsforge'
>   Adding Debian repository to project 'mapsforge-core'
>   Adding Debian repository to project 'mapsforge-map'
>   Adding Debian repository to project 'mapsforge-map-awt'
>   Adding Debian repository to project 'mapsforge-map-reader'
>   Adding Debian repository to project 'mapsforge-map-writer'
>   Adding Debian repository to project 'mapsforge-poi'
>   Adding Debian repository to project 'mapsforge-samples-awt'
>   Adding Debian repository to project 'mapsforge-themes'
> Parallel execut

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

[Sven Hartge]

On 22.03.20 19:07, Sven Hartge wrote:

> Interestingly, isc-dhcp-server 4.4.1 does not even compile against the
> current 9.16 libs from Sid right now. Something is very broken here.

I have to correct that part. It seems my checkout from Salsa was wrong,
as recompiling the source package works.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): forcibly merging 954574 949109

[Debian Bug Tracking System]

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

> forcemerge 954574 949109
Bug #954574 [src:wmnd] wmnd: FTBFS: ../../src/drivers.c:36:10: fatal error: 
sys/stropts.h: No such file or directory
Unable to merge bugs because:
package of #949109 is 'wmnd' not 'src:wmnd'
Failed to forcibly merge 954574: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#938929: Dependency problem with iptables and libvirt-daemon-system

[Ivo De Decker]

Control: severity -1 normal
Control: tags -1 moreinfo

Hi,

On Fri, Aug 30, 2019 at 12:45:16PM +0200, Julian Hyordey wrote:
> apt show libvirt-daemon-system
> Package: libvirt-daemon-system
> Version: 5.0.0-4
> Priority: optional
> Section: admin
> Source: libvirt
> Maintainer: Debian Libvirt Maintainers <
> pkg-libvirt-maintain...@lists.alioth.debian.org>
> Installed-Size: 466 kB
> Depends: debconf (>= 0.5) | debconf-2.0, libacl1 (>= 2.2.23), libapparmor1 (>=
> 2.6~devel), libaudit1 (>= 1:2.2.1), libblkid1 (>= 2.16), libc6 (>= 2.14),
> libcap-ng0 (>= 0.7.9), libdbus-1-3 (>= 1.9.14), libdevmapper1.02.1 (>=
> 2:1.02.20), libgnutls30 (>= 3.6.5), libnl-3-200 (>= 3.2.7), libnl-route-3-200
> (>= 3.2.7), libnuma1 (>= 2.0.11), libselinux1 (>= 2.0.82), libvirt0 (>= 
> 5.0.0),
> libxml2 (>= 2.7.4), libyajl2 (>= 2.0.4), adduser, gettext-base, lsb-base,
> libvirt-clients (= 5.0.0-4), libvirt-daemon (= 5.0.0-4), iptables (>= 1.8.1-1)
> | firewalld, logrotate, policykit-1
> [...]
>  .
> So If I want to migrate from iptables to nftables on my KVM hypervisor, I 
> can't
> remove iptables without removing  libvirt-daemon-system. A bit annoying for an
> hypervisor.

Can't you just install nftables, use it, and leave iptables installed?

Ivo

Processed: Re: Dependency problem with iptables and libvirt-daemon-system

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #938929 [libvirt-daemon-system] Dependency problem with iptables and 
libvirt-daemon-system
Severity set to 'normal' from 'grave'
> tags -1 moreinfo
Bug #938929 [libvirt-daemon-system] Dependency problem with iptables and 
libvirt-daemon-system
Added tag(s) moreinfo.

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

Bug#925709: marked as done (gsasl: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 19:35:03 +0100
with message-id <20200322183501.ga6...@debian.org>
and subject line Re: gsasl: ftbfs with GCC-9
has caused the Debian Bug report #925709,
regarding gsasl: 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.)


-- 
925709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gsasl
Version: 1.8.0-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/gsasl_1.8.0-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.

[...]
PASS: test-shutdown
PASS: test-signal-h
PASS: test-snprintf
PASS: test-sockets
PASS: test-stat
PASS: test-stdalign
PASS: test-stdbool
PASS: test-stddef
PASS: test-stdint
PASS: test-stdio
PASS: test-stdlib
PASS: test-strerror
PASS: test-striconv
PASS: test-string
PASS: test-symlink
PASS: test-sys_select
PASS: test-sys_socket
PASS: test-sys_stat
PASS: test-sys_time
PASS: test-sys_types
PASS: test-sys_uio
PASS: test-init.sh
PASS: test-thread_self
glthread_create failed
FAIL: test-thread_create
PASS: test-time
PASS: test-unistd
PASS: test-u8-mbtoucr
PASS: test-u8-uctomb
PASS: test-unsetenv
PASS: test-vasnprintf
PASS: test-vasprintf
test-vc-list-files-git.sh: skipped test: git not found in PATH
SKIP: test-vc-list-files-git.sh
test-vc-list-files-cvs.sh: skipped test: cvs not found in PATH
SKIP: test-vc-list-files-cvs.sh
PASS: test-verify
PASS: test-verify.sh
PASS: test-version-etc.sh
PASS: test-wchar
PASS: test-wcrtomb.sh
Skipping test: not a native Windows system
SKIP: test-wcrtomb-w32-1.sh
Skipping test: not a native Windows system
SKIP: test-wcrtomb-w32-2.sh
Skipping test: not a native Windows system
SKIP: test-wcrtomb-w32-3.sh
Skipping test: not a native Windows system
SKIP: test-wcrtomb-w32-4.sh
Skipping test: not a native Windows system
SKIP: test-wcrtomb-w32-5.sh
PASS: test-wctype-h
PASS: test-xalloc-die.sh
==
2 of 90 tests failed
(20 tests were not run)
Please report to bug-gs...@gnu.org
==
make[5]: *** [Makefile:2612: check-TESTS] Error 1
make[5]: Leaving directory '/<>/gltests'
make[4]: *** [Makefile:2761: check-am] Error 2
make[4]: Leaving directory '/<>/gltests'
make[3]: *** [Makefile:2483: check-recursive] Error 1
make[3]: Leaving directory '/<>/gltests'
make[2]: *** [Makefile:2763: check] Error 2
make[2]: Leaving directory '/<>/gltests'
make[1]: *** [Makefile:1269: check-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113: 
debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Version: 1.8.1-1

On Sat, Aug 24, 2019 at 12:49:28PM +0200, Simon Josefsson wrote:
> Thanks for the report.  I have uploaded 1.8.1-1 that from what I can
> tell fixes this, but it would be good if you could confirm that it
> builds fine for you too?

The test history from r-b confirms that it builds fine (and the buildinfo file
there confirms the build was done with gcc 9):

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

Ivo--- End Message ---

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

[Sven Hartge]

Package: bind9
Version: 1:9.16.1-2
Severity: critical
Justification: breaks unrelated packages

Hi!

The recent upgrade from 1:9.11.16+dfsg-2 to 1:9.16.1-1 causes
isc-dhcp-server to die upon start with SIGABRT, creating the following
backtrace:

8<
GNU gdb (Debian 9.1-2) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/dhcpd...
Reading symbols from 
/usr/lib/debug/.build-id/ed/444f0630db7a22e134b6492994fb9e5481c253.debug...
[New LWP 3946312]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `dhcpd -t'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt full
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 4, 223338299409, 0, 0, 139816691506048, 262160, 
139816690240512, 0, 15, 257, 5501063141756457984, 1, 44, 4294967295, 
4294967295}}
pid = 
tid = 
ret = 
#1  0x7f299c21a55b in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x30, sa_sigaction = 0x30}, 
sa_mask = {__val = {139816691747131, 139816692083696, 4398046511104, 17, 
139816692083456, 
  94694505873952, 139816693949594, 924, 48, 0, 139816691767231, 
94694505873952, 5501063141756457984, 94694505873952, 1, 0}}, sa_flags = 0, 
  sa_restorer = 0x561fc7fa88e0 }
sigs = {__val = {32, 0 }}
#2  0x7f299c3da3ff in isc_assertion_failed (file=file@entry=0x7f299c421e9b 
"../../../lib/isc/hash.c", line=line@entry=217, 
type=type@entry=isc_assertiontype_require, 
cond=cond@entry=0x7f299c42047a "mctx != ((void *)0)") at 
../../../lib/isc/assertions.c:52
No locals.
#3  0x7f299c3df6fa in isc_hash_create (mctx=, 
entropy=entropy@entry=0x0, limit=limit@entry=255) at ../../../lib/isc/hash.c:225
result = 0
#4  0x7f299c4b36bf in initialize () at ../../../lib/dns/lib.c:91
result = 
result = 
#5  dns_lib_init () at ../../../lib/dns/lib.c:127
result = 
#6  0x561fc7f3b498 in dhcp_context_create (flags=1, local4=0x0, local6=0x0) 
at isclib.c:171
result = 
#7  0x561fc7eb6f17 in main (argc=2, argv=0x7ffd9f040a18) at dhcpd.c:404
fd = 
i = 
status = 
ent = 
s = 
cftest = 0
lftest = 0
pid = 
pbuf = 
"\006\t\004\237\375\177\000\000\265\311)\234)\177\000\000\000\000\000"
daemon = 
dfd = {-1, -1}
quiet = 0
server = 0x0
result = 
seed = 
ip = 
parse = 0xc2
lose = 0
have_dhcpd_conf = 0
have_dhcpd_db = 0
have_dhcpd_pid = 0
local_family_set = 0
traceinfile = 0x0
traceoutfile = 0x0
set_user = 0x0
set_group = 0x0
set_chroot = 0x0
8<

I needed to downgrade quite many library packages out of the whole ISC
library ecosystem back down to the ones in testing to be able to start
dhcpd again:

2020-03-22 18:52:14 upgrade libbind9-161:amd64 1:9.11.17+dfsg-2 1:9.11.16+dfsg-2
2020-03-22 18:52:15 upgrade libisccfg163:amd64 1:9.11.17+dfsg-2 1:9.11.16+dfsg-2
2020-03-22 18:52:16 upgrade libirs161:amd64 1:9.11.17+dfsg-2 1:9.11.16+dfsg-2
2020-03-22 18:52:46 upgrade bind9-libs:amd64 1:9.16.1-2 1:9.16.1-1
2020-03-22 18:52:50 upgrade libisccc161:amd64 1:9.11.17+dfsg-2 1:9.11.16+dfsg-2
2020-03-22 18:52:51 upgrade libisc1105:amd64 1:9.11.17+dfsg-2 1:9.11.16+dfsg-2
2020-03-22 18:54:10 upgrade liblwres161:amd64 1:9.11.17+dfsg-2 1:9.11.16+dfsg-2
2020-03-22 18:57:05 upgrade libirs-export161:amd64 1:9.11.17+dfsg-2 
1:9.11.16+dfsg-2
2020-03-22 18:58:18 upgrade libisc-export1105:amd64 1:9.11.17+dfsg-2 
1:9.11.16+dfsg-2
2020-03-22 19:02:22 upgrade libisccfg-export163-dbgsym:amd64 1:9.11.17+dfsg-2 
1:9.11.16+dfsg-2
2020-03-22 19:02:26 upgrade libisccfg-export163:amd64 1:9.11.17+dfsg-2 
1:9.11.16+dfsg-2

Interestingly, isc-dhcp-server 4.4.1 does not even compile against the
current 9.16 libs from Sid right now. Something is very broken here.

Grüße,
Sven.

-- System Information:
Debian 

Processed: tagging 932725

[Debian Bug Tracking System]

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

> # mips is no longer in testing or unstable
> tags 932725 + buster
Bug #932725 [src:libunwind] libunwind8: segfault on MIPS, fix needs backporting
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#954610: marked as done (golang-logrus: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/sirupsen/logrus github.com/sirupsen/logrus/hooks/syslog github.com

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 18:22:08 +
with message-id 
and subject line Bug#954610: fixed in golang-logrus 1.4.2.98.gd417be0-1
has caused the Debian Bug report #954610,
regarding golang-logrus: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
go test -vet=off -v -p 4 github.com/sirupsen/logrus 
github.com/sirupsen/logrus/hooks/syslog github.com/sirupsen/logrus/hooks/test 
github.com/sirupsen/logrus/internal/testutils returned exit code 1
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/sirupsen/logrus github.com/sirupsen/logrus/hooks/syslog 
> github.com/sirupsen/logrus/hooks/test 
> github.com/sirupsen/logrus/internal/testutils
> internal/race
> runtime/internal/sys
> internal/cpu
> sync/atomic
> runtime/internal/atomic
> runtime/internal/math
> unicode
> unicode/utf8
> internal/bytealg
> encoding
> math/bits
> internal/testlog
> math
> unicode/utf16
> internal/nettrace
> runtime
> runtime/cgo
> container/list
> crypto/internal/subtle
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/subtle
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> bytes
> reflect
> bufio
> strings
> hash
> hash/crc32
> regexp/syntax
> crypto
> time
> internal/syscall/unix
> crypto/internal/randutil
> crypto/hmac
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> regexp
> path
> encoding/binary
> internal/fmtsort
> context
> internal/poll
> golang.org/x/sys/unix
> encoding/base64
> crypto/cipher
> crypto/sha512
> os
> crypto/aes
> crypto/des
> crypto/ed25519/internal/edwards25519
> crypto/md5
> fmt
> net
> path/filepath
> crypto/sha1
> encoding/json
> log
> io/ioutil
> encoding/hex
> github.com/pmezard/go-difflib/difflib
> github.com/davecgh/go-spew/spew
> gopkg.in/yaml.v2
> github.com/sirupsen/logrus
> compress/flate
> compress/gzip
> github.com/sirupsen/logrus/hooks/test
> math/big
> crypto/sha256
> encoding/pem
> net/url
> vendor/golang.org/x/crypto/chacha20
> vendor/golang.org/x/crypto/poly1305
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/curve25519
> vendor/golang.org/x/crypto/chacha20poly1305
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> crypto/ecdsa
> crypto/x509/pkix
> vendor/golang.org/x/crypto/cryptobyte
> vendor/golang.org/x/text/unicode/bidi
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> vendor/golang.org/x/text/secure/bidirule
> mime
> mime/quotedprintable
> net/http/internal
> log/syslog
> crypto/x509
> vendor/golang.org/x/net/idna
> github.com/sirupsen/logrus/hooks/syslog
> net/textproto
> flag
> runtime/debug
> mime/multipart
> vendor/golang.org/x/net/http/httpguts
> vendor/golang.org/x/net/http/httpproxy
> runtime/trace
> testing
> crypto/tls
> net/http/httptrace
> net/http
> net/http/httptest
> github.com/stretchr/testify/assert
> github.com/stretchr/testify/require
> github.com/sirupsen/logrus/internal/testutils
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/sirupsen/logrus github.com/sirupsen/logrus/hooks/syslog 
> github.com/sirupsen/logrus/hooks/test 
> github.com/sirupsen/logrus/internal/testutils
> === RUN   TestRegister
> --- PASS: TestRegister (0.00s)
> === RUN   TestDefer
> --- PASS: TestDefer (0.00s)
> === RUN   TestHandler
> --- PASS: TestHandler (0.34s)
> === RUN   TestEntryWithError
> --- PASS: TestEntryWithError (0.00s)
> === RUN   TestEntryWithContext
> --- PASS: TestEntryWithContext (0.00s)
> === RUN   TestEntryPanicln
> --- PASS: TestEntryPanicln (0.00s)
> === RUN   TestEntryPanicf
> --- PASS: TestEntryPanicf (0.00s)
> === RUN   TestEntryHooksPanic
> --- PASS: TestEntryHooksPanic (0.00s)
> === RUN   

Bug#954729: src:mesa: X won't start after upgrading mesa

[Timo Aaltonen]

On 22.3.2020 17.38, Chow Loong Jin wrote:
> Package: src:mesa
> Version: 20.0.2-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
>> * What led up to the situation?
> 
> Upgraded mesa packages from 19.3.3-1 to 20.0.2-1.
> 
>> * What exactly did you do (or not do) that was effective (or
>>   ineffective)?
> 
> Tried to boot
> 
>> * What was the outcome of this action?
> 
> X wouldn't start (log attached)
> 
>> * What outcome did you expect instead?
> 
> X starts.
> 

Your kernel (4.9) is probably too old for the new iris dri driver.

-- 
t

Bug#954579: datalad-container: FTBFS: build-dependency not installable: datalad (>= 0.11.5~)

[Yaroslav Halchenko]

On Sun, 22 Mar 2020, Lucas Nussbaum wrote:

> Source: datalad-container
> Version: 0.5.0-1

Thank you for the report.  1.0.0-1 was built but forgotten to be
uploaded at the end of Feb.  Now it would need to wait until datalad
0.12.4 is uploaded first which would resolve incompatibilities with
recent git annex and git releases.  Hopefully later today/tomorrow

Cheers,
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: bug 954549 is forwarded to https://github.com/json-iterator/go/issues/419

[Debian Bug Tracking System]

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

> forwarded 954549 https://github.com/json-iterator/go/issues/419
Bug #954549 [src:golang-github-json-iterator-go] 
golang-github-json-iterator-go: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/json-iterator/go 
github.com/json-iterator/go/any_tests github.com/json-iterator/go/api_tests 
github.com/json-iterator/go/benchmarks 
github.com/json-iterator/go/extension_tests github.com/json-iterator/go/extra 
github.com/json-iterator/go/misc_tests github.com/json-iterator/go/skip_tests 
github.com/json-iterator/go/type_tests github.com/json-iterator/go/value_tests 
returned exit code 1
Set Bug forwarded-to-address to 
'https://github.com/json-iterator/go/issues/419'.
> thanks
Stopping processing here.

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

Bug#954675: marked as done (phpdox: FTBFS: dh_installman: error: Could not determine section for ./debian/tmp/phpdox.1)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 17:04:38 +
with message-id 
and subject line Bug#954675: fixed in phpdox 0.12.0-3
has caused the Debian Bug report #954675,
regarding phpdox: FTBFS: dh_installman: error: Could not determine section for 
./debian/tmp/phpdox.1
to be marked as done.

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

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


-- 
954675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phpdox
Version: 0.12.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir debian/tmp
> cd debian/phpdox/usr/share/php && \
>   help2man --no-info \
>   --name='phpDox command line interface' \
>   ../../bin/phpdox \
>   > /<>/debian/tmp/phpdox.1
> dh_installman
> dh_installman: error: Could not determine section for ./debian/tmp/phpdox.1
> dh_installman: error: Aborting due to earlier error
> make[1]: *** [debian/rules:15: override_dh_installman] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/phpdox_0.12.0-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: phpdox
Source-Version: 0.12.0-3
Done: =?utf-8?q?David_Pr=C3=A9vot?= 

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated phpdox 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, 22 Mar 2020 06:48:08 -1000
Source: phpdox
Architecture: source
Version: 0.12.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 954675
Changes:
 phpdox (0.12.0-3) unstable; urgency=medium
 .
   * Fix manpage with recent help2man (Closes: #954675)
   * debian/control:
 + Drop versioned dependency satisfied in (old)stable
 + Update Standards-Version to 4.5.0
   * debian/upstream/metadata:
 + Remove obsolete fields Contact, Name
 + Set fields Bug-Database, Bug-Submit, Repository, Repository-Browse
Checksums-Sha1:
 59d32587b55eba2c5d2c051fbb7472e7f1e531b4 1823 phpdox_0.12.0-3.dsc
 77f3b74edfb1ea6515284f63e2adf99e8594cb76 9196 phpdox_0.12.0-3.debian.tar.xz
 9324b857daba6d9ec16b43197fe35b753e93dbe6 9022 phpdox_0.12.0-3_amd64.buildinfo
Checksums-Sha256:
 698e384912d3634fa38a7e830dd0dfd8e508883bd3637adc764839909becfe09 1823 
phpdox_0.12.0-3.dsc
 01d891b3d81bc6117acdf424d1002a05ffed97a0aa23352708a22892c0e3b82c 9196 
phpdox_0.12.0-3.debian.tar.xz
 4cd9eacfbe6520d70f3b7b7256ef651182dd0b53825d1b93334fbd047f1b6cb1 9022 
phpdox_0.12.0-3_amd64.buildinfo
Files:
 4671d6e334a6363bf3a0ac96ac7c4ce6 1823 php optional phpdox_0.12.0-3.dsc
 5bc07fbd1b3d4e431cb06d0d2e690c6f 9196 php optional 
phpdox_0.12.0-3.debian.tar.xz
 2c4ff996898bad66b32f9fed6506b637 9022 php optional 
phpdox_0.12.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAl53mCMSHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08biQH/15f+aJAef1MkjiJcpKgbOlqRTeOy5O+
4uxvycgtIv1FaxH4wCeAGAHxTKCjGrRASE8IseqSQG9PlSQR1mTgbgm7OLjpV/wW
sua4aEJwJigs1qo5PF055p25fiH0ennGARfVM5rC8QqLlorLt8fmKEEDyhYDezor
MxRiuq92dEAHk3Fm0WuocWsZbechO4229Inx540vJ0ybM+J7O9RHT8/e/iCjgqD+
gmfIq+HlDAV4zGAKnnbM7hVXPK1sjZ1KcVdUM+N5+81g/hxyTaQXZdX/61QxEvys
P0oDYTzix05u1WXc5KH+V/0HRCDktubsWuVE2qgOKYCX7/2U40ngEc4=
=C0Aa
-END PGP SIGNATURE End Message ---

Processed: limit source to phpdox, tagging 954675

[Debian Bug Tracking System]

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

> limit source phpdox
Limiting to bugs with field 'source' containing at least one of 'phpdox'
Limit currently set to 'source':'phpdox'

> tags 954675 + pending
Bug #954675 [src:phpdox] phpdox: FTBFS: dh_installman: error: Could not 
determine section for ./debian/tmp/phpdox.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#954451: marked as done (src:tox: Please remove python2 autopkgtests that use virtualenv)

[Debian Bug Tracking System]

Your message dated Sun, 22 Mar 2020 16:34:45 +
with message-id 
and subject line Bug#954451: fixed in tox 3.13.2-2
has caused the Debian Bug report #954451,
regarding src:tox: Please remove python2 autopkgtests that use virtualenv
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.)


-- 
954451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tox
Version: 3.13.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Note: Using FTBFS to cover autopkgtest failure as it is a rough
equivalent (package can't migrate to testing).

The python-virtualenv package can no longer support creation of python2
virtualenvs without external downloads, which are not allowed for
packages in Main.  The ipaddr module is no longer in Testing and is
required for this.  As a result, tox python2 autopkgtests now fail:

py2 create: /tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2
ERROR: invocation failed (exit code 1), logfile: 
/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/log/py2-1.log
== log start ===
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File 
"/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/lib/python2.7/site-packages/pip/__main__.py",
 line 16, in 
from pip._internal.cli.main import main as _main  # isort:skip # noqa
  File 
"/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/lib/python2.7/site-packages/pip/_internal/cli/main.py",
 line 10, in 
from pip._internal.cli.autocompletion import autocomplete
  File 
"/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/lib/python2.7/site-packages/pip/_internal/cli/autocompletion.py",
 line 9, in 
from pip._internal.cli.main_parser import create_main_parser
  File 
"/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/lib/python2.7/site-packages/pip/_internal/cli/main_parser.py",
 line 7, in 
from pip._internal.cli import cmdoptions
  File 
"/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/lib/python2.7/site-packages/pip/_internal/cli/cmdoptions.py",
 line 25, in 
from pip._internal.locations import USER_CACHE_DIR, get_src_prefix
  File 
"/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/lib/python2.7/site-packages/pip/_internal/locations.py",
 line 20, in 
from pip._internal.utils.compat import WINDOWS
  File 
"/tmp/autopkgtest-lxc.zhf4r5q1/downtmp/autopkgtest_tmp/.tox/py2/lib/python2.7/site-packages/pip/_internal/utils/compat.py",
 line 29, in 
import ipaddr as ipaddress  # type: ignore
ImportError: No module named ipaddr

I'm happy to do an NMU to simply drop the tests if you would like.
Please let me know if you plan to take care of it.  I will probably NMU
in a week (including the NMU diff in this bug once I have it ready) if I
don't.

Thanks,

Scott K
--- End Message ---
--- Begin Message ---
Source: tox
Source-Version: 3.13.2-2
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated tox 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, 22 Mar 2020 12:10:23 -0400
Source: tox
Architecture: source
Version: 3.13.2-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Scott Kitterman 
Closes: 954451
Changes:
 tox (3.13.2-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Scott Kitterman ]
   * Drop tests for python2, they can no longer be run from just packages in
 Testing (Closes: #954451).
Checksums-Sha1:
 383a591768ba08b0af27ae3845cca958f62059f0 2299 

Bug#954690: [Pkg-utopia-maintainers] Bug#954690: udisks2: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Michael Biebl]

Am 22.03.20 um 14:43 schrieb Lucas Nussbaum:
> Source: udisks2
> Version: 2.8.4-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200322 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
>> make[7]: Entering directory '/<>/src/tests'
>> ../../build-aux/test-driver: line 107: 25219 Aborted "$@" > 
>> $log_file 2>&1
>> FAIL: udisks-test
>> 
>>udisks 2.8.4: src/tests/test-suite.log
>> 
>>
>> # TOTAL: 1
>> # PASS:  0
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  1
>> # XPASS: 0
>> # ERROR: 0
>>
>> .. contents:: :depth: 2
>>
>> FAIL: udisks-test
>> =
>>
>> # random seed: R02S75a7e9375430409f104dc3d1401f0dde
>> 1..23
>> # Start of udisks tests
>> # Start of daemon tests
>> # Start of spawned_job tests
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 1 /udisks/daemon/spawned_job/successful
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 2 /udisks/daemon/spawned_job/failure
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 3 /udisks/daemon/spawned_job/missing_program
>> ok 4 /udisks/daemon/spawned_job/cancelled_at_start
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 5 /udisks/daemon/spawned_job/cancelled_midway
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 6 /udisks/daemon/spawned_job/override_signal_handler
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 7 /udisks/daemon/spawned_job/premature_termination
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 8 /udisks/daemon/spawned_job/read_stdout
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 9 /udisks/daemon/spawned_job/read_stderr
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 10 /udisks/daemon/spawned_job/exit_status
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> ok 11 /udisks/daemon/spawned_job/abnormal_termination
>> # GLib-DEBUG: posix_spawn avoided (fd close requested) (child_setup 
>> specified) 
>> **
>> udisks-test:ERROR:test.c:358:binary_output_on_spawned_job_completed: 
>> assertion failed (standard_output->len == 200): (0 == 200)
>> Bail out! 
>> udisks-test:ERROR:test.c:358:binary_output_on_spawned_job_completed: 
>> assertion failed (standard_output->len == 200): (0 == 200)
>> FAIL udisks-test (exit status: 134)


When building the same package inside a buster chroot, the test-suite
passes.
I wonder if this is change/regression in glib2.0?



signature.asc
Description: OpenPGP digital signature

Bug#954451: marked as pending in tox

[Scott Kitterman]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/applications/tox/-/commit/17ec50d82414cd9134c2a2cfe29b635a970ee3a3


* Drop tests for python2, they can no longer be run from just packages in
  Testing (Closes: #954451).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954451

Processed: Bug#954451 marked as pending in tox

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954451 [src:tox] src:tox: Please remove python2 autopkgtests that use 
virtualenv
Added tag(s) pending.

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

Processed: Bug#954583 marked as pending in sahara

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954583 [src:sahara] sahara: FTBFS: make[1]: pyversions: Command not found
Added tag(s) pending.

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

Bug#954583: marked as pending in sahara

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #954583 in sahara 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/openstack-team/services/sahara/-/commit/8e29db7c033dd63ab07d247c62272a1a953c4826


* Blacklist 3 unit tests which are failing, and have been reported upstream
at: https://storyboard.openstack.org/#!/story/2007450. (Closes: #954583).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954583

Processed: tagging 954566

[Debian Bug Tracking System]

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

> tags 954566 + confirmed
Bug #954566 [src:cura-engine] cura-engine: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#954729: src:mesa: X won't start after upgrading mesa

[Chow Loong Jin]

Package: src:mesa
Version: 20.0.2-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

> * What led up to the situation?

Upgraded mesa packages from 19.3.3-1 to 20.0.2-1.

> * What exactly did you do (or not do) that was effective (or
>   ineffective)?

Tried to boot

> * What was the outcome of this action?

X wouldn't start (log attached)

> * What outcome did you expect instead?

X starts.

-- 
Kind regards,
Loong Jin


Xorg.0.log.old
Description: Xorg.0.log from the crash


signature.asc
Description: PGP signature

Processed: fixed 952946 in 1:9.11.17-1, fixed 952946 in 1:9.16.0-1

[Debian Bug Tracking System]

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

> fixed 952946 1:9.11.17-1
Bug #952946 [src:bind9] bind9: Replace PKCS11 headers provided by OASIS
The source 'bind9' and version '1:9.11.17-1' do not appear to match any binary 
packages
Marked as fixed in versions bind9/1:9.11.17-1.
> fixed 952946 1:9.16.0-1
Bug #952946 [src:bind9] bind9: Replace PKCS11 headers provided by OASIS
Marked as fixed in versions bind9/1:9.16.0-1.
> thanks
Stopping processing here.

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

Bug#954722: spring: FTBFS: unistd_ext.h:34:16: error: conflicting declaration of ‘__pid_t gettid()’ with ‘C’ linkage

[Lucas Nussbaum]

Source: spring
Version: 104.0+dfsg-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/test && /usr/bin/c++  
> -DASIO_STANDALONE -DBOOST_NO_FENV_H -DBOOST_TEST_DYN_LINK 
> -DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSTREFLOP_SSE 
> -DSYNCCHECK -DUNIT_TEST -DUSE_LIBSQUISH -D_GLIBCXX_USE_NANOSLEEP 
> -D_RANDOM_TCC -I/<>/obj-x86_64-linux-gnu/src-generated/engine 
> -I/<>/rts -I/<>/rts/lib/asio/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -std=gnu++11 
> -fdiagnostics-color=auto -mtune=generic -msse -mfpmath=sse -mno-sse2 
> -mno-sse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx 
> -mno-fma -mno-fma4 -mno-xop -mno-lwp -mno-avx2 -fsingle-precision-constant 
> -frounding-math -mieee-fp -pipe -fno-strict-aliasing  -fvisibility=hidden  
> -fvisibility-inlines-hidden -pthread  -O2  -Wformat -Wformat-security 
> -DNDEBUG -g   -DTHREADPOOL -DUNITSYNC -o 
> CMakeFiles/test_ThreadPool.dir/engine/System/testThreadPool.cpp.o -c 
> /<>/test/engine/System/testThreadPool.cpp
> In file included from /usr/include/unistd.h:1170,
>  from /usr/include/boost/config/stdlib/libstdcpp3.hpp:78,
>  from /usr/include/boost/config.hpp:49,
>  from /usr/include/boost/thread/detail/config.hpp:11,
>  from /usr/include/boost/thread/future.hpp:11,
>  from 
> /<>/test/engine/System/testThreadPool.cpp:12:
> /usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: error: conflicting 
> declaration of ‘__pid_t gettid()’ with ‘C’ linkage
>34 | extern __pid_t gettid (void) __THROW;
>   |^~
> In file included from /<>/rts/System/Platform/Threading.h:9,
>  from /<>/rts/System/Threading/ThreadPool.h:66,
>  from 
> /<>/test/engine/System/testThreadPool.cpp:3:
> /<>/rts/System/Platform/Linux/ThreadSupport.h:24:5: note: 
> previous declaration with ‘C++’ linkage
>24 | int gettid ();
>   | ^~
> In file included from /usr/include/unistd.h:1170,
>  from /usr/include/boost/config/stdlib/libstdcpp3.hpp:78,
>  from /usr/include/boost/config.hpp:49,
>  from /usr/include/boost/thread/detail/config.hpp:11,
>  from /usr/include/boost/thread/future.hpp:11,
>  from 
> /<>/test/engine/System/testThreadPool.cpp:12:
> /usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: error: declaration of 
> ‘__pid_t gettid() throw ()’ has a different exception specifier
>34 | extern __pid_t gettid (void) __THROW;
>   |^~
> In file included from /<>/rts/System/Platform/Threading.h:9,
>  from /<>/rts/System/Threading/ThreadPool.h:66,
>  from 
> /<>/test/engine/System/testThreadPool.cpp:3:
> /<>/rts/System/Platform/Linux/ThreadSupport.h:24:5: note: from 
> previous declaration ‘int gettid()’
>24 | int gettid ();
>   | ^~
> make[5]: *** [test/CMakeFiles/test_ThreadPool.dir/build.make:66: 
> test/CMakeFiles/test_ThreadPool.dir/engine/System/testThreadPool.cpp.o] Error 
> 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/spring_104.0+dfsg-5_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#954720: node-entities: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-entities
Version: 2.0.0+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tsc
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
> 
> Run tests with Mocha
> 
> Rules & Behavior
>   --allow-uncaught   Allow uncaught errors to propagate
> [boolean]
>   --async-only, -A   Require all tests to use a callback (async) or
>  return a Promise  
> [boolean]
>   --bail, -b Abort ("bail") after first test failure   
> [boolean]
>   --check-leaks  Check for global variable leaks   
> [boolean]
>   --delayDelay initial execution of root suite 
> [boolean]
>   --exit Force Mocha to quit after tests complete  
> [boolean]
>   --forbid-only  Fail if exclusive test(s) encountered 
> [boolean]
>   --forbid-pending   Fail if pending test(s) encountered   
> [boolean]
>   --global, --globalsList of allowed global variables
> [array]
>   --retries  Retry failed tests this many times 
> [number]
>   --slow, -s Specify "slow" test threshold (in milliseconds)
>   [string] [default: 
> 75]
>   --timeout, -t, --timeouts  Specify test timeout threshold (in milliseconds)
> [string] [default: 
> 2000]
>   --ui, -u   Specify user interface[string] [default: 
> "bdd"]
> 
> Reporting & Output
>   --color, -c, --colors Force-enable color output  
> [boolean]
>   --diffShow diff on failure
>[boolean] [default: 
> true]
>   --full-trace  Display full stack traces  
> [boolean]
>   --growl, -G   Enable Growl notifications 
> [boolean]
>   --inline-diffsDisplay actual/expected 
> differences
> inline within each string  
> [boolean]
>   --reporter, -RSpecify reporter to use
>   [string] [default: 
> "spec"]
>   --reporter-option, --reporter-options,Reporter-specific options
>   -O()   
> [array]
> 
> Configuration
>   --config   Path to config file   [string] [default: (nearest rc 
> file)]
>   --opts Path to `mocha.opts` (DEPRECATED)
>  [string] [default: 
> "./test/mocha.opts"]
>   --package  Path to package.json for config
> [string]
> 
> File Handling
>   --extension  File extension(s) to load   [array] [default: 
> js]
>   --file   Specify file(s) to be loaded prior to root suite
>execution   [array] [default: 
> (none)]
>   --ignore, --exclude  Ignore file(s) or glob pattern(s)
>[array] [default: 
> (none)]
>   --recursive  Look for tests in subdirectories
> [boolean]
>   --require, -rRequire module  [array] [default: 
> (none)]
>   --sort, -S   Sort test files 
> [boolean]
>   --watch, -w  Watch files in the current working directory for 
> changes
>
> [boolean]
>   --watch-filesList of paths or globs to watch   
> [array]
>   --watch-ignore   List of paths or globs to exclude from watching
>   [array] [default: 
> ["node_modules",".git"]]
> 
> Test Filters
>   --fgrep, -f   Only run tests containing this string   
> [string]
>   --grep, -gOnly run tests matching this string or regexp   
> [string]
>   --invert, -i  Inverts --grep and --fgrep matches 
> [boolean]
> 
> Positional Arguments
>   spec  One or more files, directories, or globs to test
>

Bug#954721: pry: FTBFS: ERROR: Test "ruby2.7" failed. Could not find 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] (Gem::MissingSpecVersionError)

[Lucas Nussbaum]

Source: pry
Version: 0.12.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/pry/usr/share/rubygems-integration/all:/<>/.gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"pry\"
> /usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not find 
> 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/pry/usr/share/rubygems-integration/all:/<>/.gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0',
>  execute `gem env` for more information
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in 
> activate_dependencies'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem'
>   from -e:1:in `'
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.2)
> cgi (default: 0.1.0)
> coderay (1.1.2)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0, 1.2.1)
> diff-lcs (1.3)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> gist (5.0.0)
> io-console (default: 0.5.3)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.1)
> json (2.3.0)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> method_source (1.0.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (default: 0.1.0)
> net-telnet (0.1.1)
> observer (default: 0.1.0)
> open3 (default: 0.1.0)
> openssl (default: 2.1.2)
> ostruct (default: 0.2.0)
> power_assert (1.1.6)
> prime (default: 0.1.1)
> pstore (default: 0.1.0)
> psych (default: 3.1.0)
> racc (default: 1.4.16)
> rake (13.0.1)
> rdoc (default: 6.2.1)
> readline (default: 0.0.2)
> readline-ext (default: 0.1.0)
> reline (default: 0.1.2)
> rexml (default: 3.2.3)
> rspec (3.9.0)
> rspec-core (3.9.1)
> rspec-expectations (3.9.0)
> rspec-mocks (3.9.1)
> rspec-support (3.9.2)
> rss (default: 0.2.8)
> sdbm (default: 1.0.0)
> singleton (default: 0.1.0)
> stringio (default: 0.1.0)
> strscan (default: 1.0.3)
> test-unit (3.3.4)
> timeout (default: 0.1.0)
> tracer (default: 0.1.0)
> uri (default: 0.10.0)
> webrick (default: 1.6.0)
> xmlrpc (0.3.0)
> yaml (default: 0.1.0)
> zlib (default: 1.1.0)
> ERROR: Test "ruby2.7" failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/pry_0.12.2-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#954723: golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/scopestack returned exit code 2

[Lucas Nussbaum]

Source: golang-github-mendersoftware-scopestack
Version: 0.0~git20180403.c2f5599-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/mendersoftware/scopestack
> runtime/internal/sys
> container/list
> internal/cpu
> runtime/internal/atomic
> runtime/internal/math
> math/bits
> unicode/utf8
> internal/race
> sync/atomic
> internal/bytealg
> unicode
> math
> internal/testlog
> runtime
> internal/reflectlite
> sync
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> strings
> reflect
> time
> internal/syscall/unix
> internal/poll
> internal/fmtsort
> os
> fmt
> github.com/mendersoftware/scopestack
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/scopestack
> # github.com/mendersoftware/scopestack 
> [github.com/mendersoftware/scopestack.test]
> src/github.com/mendersoftware/scopestack/scope_stack_test.go:23:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/scopestack/scope_stack_test.go:29:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/scopestack/scope_stack_test.go:35:2: undefined: 
> mendertesting.AssertTrue
> FAIL  github.com/mendersoftware/scopestack [build failed]
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/scopestack returned exit code 2

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/22/golang-github-mendersoftware-scopestack_0.0~git20180403.c2f5599-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#954725: datatables-extensions: FTBFS: Parse error

[Lucas Nussbaum]

Source: datatables-extensions
Version: 0.0+git20150910.28fd64e+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> for min in `find debian -name "*.min.js"` ; do \
> closure-compiler  --charset 'utf-8' --js `echo ${min} | sed 's/\.min//'` 
> --js_output_file ${min} ; \
> done
> debian/libjs-jquery-datatables-extensions/usr/share/javascript/jquery-datatables-extensions/JSZip/jszip.js:12:
>  WARNING - Suspicious code. The result of the 'not' operator is not being 
> used.
> !function(e){if("object"==typeof exports&&"undefined"!=typeof 
> module)module.exports=e();else if("function"==typeof 
> define&)define([],e);else{var f;"undefined"!=typeof 
> window?f=window:"undefined"!=typeof global?f=global:"undefined"!=typeof 
> self&&(f=self),f.JSZip=e()}}(function(){var define,module,exports;return 
> (function e(t,n,r){function s(o,u){if(!n[o]){if(!t[o]){var a=typeof 
> require=="function"&if(!u&)return a(o,!0);if(i)return 
> i(o,!0);throw new Error("Cannot find module '"+o+"'")}var 
> f=n[o]={exports:{}};t[o][0].call(f.exports,function(e){var 
> n=t[o][1][e];return s(n?n:e)},f,f.exports,e,t,n,r)}return n[o].exports}var 
> i=typeof require=="function"&for(var 
> o=0;o ^
> 
> 0 error(s), 1 warning(s)
> debian/libjs-jquery-datatables-extensions/usr/share/javascript/jquery-datatables-extensions/pdfmake/build/pdfmake.js:327:
>  ERROR - Parse error. IE8 (and below) will parse trailing commas in array and 
> object literals incorrectly. If you are targeting newer versions of JS, set 
> the appropriate language_in option.
> hLineWidth: function(i) { return 0; },
> ^
> 
[...]
> 33028 error(s), 0 warning(s)
> make[1]: *** [debian/rules:10: override_dh_install] Error 127

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/22/datatables-extensions_0.0+git20150910.28fd64e+dfsg-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#954726: mftrace: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: mftrace
Version: 1.2.20+git20191022.3b4bc2e-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/bin/python3 mftrace.py --glyphs 65 -V ecbi0900 &&  /usr/bin/python3 
> mftrace.py --glyphs 65 -V logo10 &&  /usr/bin/python3 mftrace.py --glyphs 65 
> -V cmr11 &
> This is METAFONT, Version 2.7182818 (TeX Live 2019/Debian) (preloaded base=mf)
> 
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecbi0900.mf
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exbase.mf)
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecbi.mf
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/extextit.mf
>  Ok (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exaccess.mf
>  Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/expseudo.mf
>  Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exileast.mf
>  Ok [158] [160] [161] [162] [163] [164] [165] [166] [167] [168] [169] [170]
> [171] [172] [173] [174] [175] [176] [177] [178] [179] [180] [181] [182]
> [183] [184] [185] [186] [187] [188])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exilwest.mf
>  Ok [224] [225] [226] [227] [228] [229] [230] [231] [232] [233] [234] [235]
> [236] [237] [238] [239] [240] [241] [242] [243] [244] [245] [246] [247]
> [248] [249] [250] [251] [252] [253] [254] [255])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exruwest.mf
>  Ok [192] [193] [194] [195] [196] [197] [198] [199] [200] [201] [202] [203]
> [204] [205] [206] [207] [208] [209] [210] [211] [212] [213] [214] [215]
> [216] [217] [218] [219] [220] [221] [222] [223])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrueast.mf
>  Ok [128] [129] [130] [131] [132] [133] [134] [135] [136] [137] [138] [139]
> [140] [141] [142] [143] [144] [145] [146] [147] [148] [149] [150] [151]
> [152] [153] [154] [155] [156] [157])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exbraces.mf
>  Ok [94] [126] [23] [40] [41] [60] [124] [62] [91] [93] [92] [123] [125]
> [95] [127] [32])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/expunct.mf
>  Ok [14] [15] [19] [20] [13] [18] [33] [39] [42] [43] [44] [46] [47] [58]
> [59] [61] [96] [189] [17] [45] [16] [21] [22])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exaccent.mf
>  Ok [0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exsign.mf
>  Ok [24] [34] [35] [36] [37] [64] [191] [159])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exilig.mf
>  Ok [25] [26] [27] [28] [29] [30] [31])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exitalp.mf
>  Ok [38] [63] [190])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrulett.mf
>  Ok [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78]
> [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exillett.mf
>  Ok [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108]
> [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120]
> [121] [122])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exidigit.mf
>  Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exiligtb.mf
>  Ok) ) ) )
> Font metrics written on ecbi0900.tfm.
> Output written on ecbi0900.8030gf (256 characters, 1150484 bytes).
> Transcript written on ecbi0900.log.
> Cannot find your hotkey definition file!
> mftrace @VERSION@
> Font `ecbi0900'...
> Opening pipe `kpsewhich ecbi0900.tfm'
> Temporary directory is `/tmp/tmpj8y7r0db'
> Opening pipe `kpsewhich tex256.enc'
> Using encoding file: 
> `/usr/share/texlive/texmf-dist/fonts/enc/dvips/base/tex256.enc'
> Running Metafont...Invoking `mf '\mode:=lexmarks; mag:=6.691667; nonstopmode; 
> input ecbi0900''
> 
> 
> Tracing bitmaps...
> Invoking `/<>/gf2pbm -n 65 -o char.pbm ecbi0900.8030gf'
> 
> Opening pipe `/<>/gf2pbm -n 65 -s ecbi0900.8030gf'
> Invoking `potrace -u 1  -q -c --eps --output=char.eps char.pbm '
> 
> Invoking `fontforge --help > pfv 2>&1 '
> 
> Assembling raw font to `ecbi0900.pfa.raw'... 
> Invoking `t1asm --pfa mftrace.t1asm ecbi0900.pfa.raw'
> 
> 
> Invoking `fontforge -quiet -script to-ttf.pe ecbi0900.pfa.raw 
> /usr/share/texlive/texmf-dist/fonts/tfm/jknappen/ec/ecbi0900.tfm'
> 
> Fontforge script #!/usr/bin/env fontforge
> Open ($1);
> MergeKern($2);
> RoundToInt ();
> Generate(&quo

Bug#954719: node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-immutable-tuple
Version: 0.4.10-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./scripts/build.sh
> (!) You have passed an unrecognized option
> Unknown input option: sourcemap. Allowed options: acorn, acornInjectPlugins, 
> cache, chunkGroupingSize, context, experimentalCacheExpiry, 
> experimentalOptimizeChunks, experimentalTopLevelAwait, external, 
> inlineDynamicImports, input, manualChunks, moduleContext, onwarn, perf, 
> plugins, preserveModules, preserveSymlinks, shimMissingExports, treeshake, 
> watch
> 
> /<>/src/tuple.js → ../dist/tuple.js...
> created ../dist/tuple.js in 80ms
> (!) You have passed an unrecognized option
> Unknown input option: sourcemap. Allowed options: acorn, acornInjectPlugins, 
> cache, chunkGroupingSize, context, experimentalCacheExpiry, 
> experimentalOptimizeChunks, experimentalTopLevelAwait, external, 
> inlineDynamicImports, input, manualChunks, moduleContext, onwarn, perf, 
> plugins, preserveModules, preserveSymlinks, shimMissingExports, treeshake, 
> watch
> 
> /<>/src/tuple.js → ../dist/tuple.mjs...
> created ../dist/tuple.mjs in 78ms
> uglifyjs dist/tuple.js -o dist/tuple.min.js
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
> 
> Run tests with Mocha
> 
> Rules & Behavior
>   --allow-uncaught   Allow uncaught errors to propagate
> [boolean]
>   --async-only, -A   Require all tests to use a callback (async) or
>  return a Promise  
> [boolean]
>   --bail, -b Abort ("bail") after first test failure   
> [boolean]
>   --check-leaks  Check for global variable leaks   
> [boolean]
>   --delayDelay initial execution of root suite 
> [boolean]
>   --exit Force Mocha to quit after tests complete  
> [boolean]
>   --forbid-only  Fail if exclusive test(s) encountered 
> [boolean]
>   --forbid-pending   Fail if pending test(s) encountered   
> [boolean]
>   --global, --globalsList of allowed global variables
> [array]
>   --retries  Retry failed tests this many times 
> [number]
>   --slow, -s Specify "slow" test threshold (in milliseconds)
>   [string] [default: 
> 75]
>   --timeout, -t, --timeouts  Specify test timeout threshold (in milliseconds)
> [string] [default: 
> 2000]
>   --ui, -u   Specify user interface[string] [default: 
> "bdd"]
> 
> Reporting & Output
>   --color, -c, --colors Force-enable color output  
> [boolean]
>   --diffShow diff on failure
>[boolean] [default: 
> true]
>   --full-trace  Display full stack traces  
> [boolean]
>   --growl, -G   Enable Growl notifications 
> [boolean]
>   --inline-diffsDisplay actual/expected 
> differences
> inline within each string  
> [boolean]
>   --reporter, -RSpecify reporter to use
>   [string] [default: 
> "spec"]
>   --reporter-option, --reporter-options,Reporter-specific options
>   -O()   
> [array]
> 
> Configuration
>   --config   Path to config file   [string] [default: (nearest rc 
> file)]
>   --opts Path to `mocha.opts` (DEPRECATED)
>  [string] [default: 
> "./test/mocha.opts"]
>   --package  Path to package.json for config
> [string]
> 
> File Handling
>   --extension  File extension(s) to load   [array] [default: 
> js]
>   --file   Specify file(s) to be loaded prior to root suite
>execution   [array] [default: 
> (none)]
>   --ignore, --exclude  Ignore file(s) or glob pattern(s)
>[array] [default: 
> (none)]
>   --recursive  Look for tests in subdirectori

Bug#954724: ruby-guard: FTBFS: ERROR: Test "ruby2.7" failed. Could not find 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] (Gem::MissingSpecVersionError)

[Lucas Nussbaum]

Source: ruby-guard
Version: 2.16.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-guard/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"guard\"
> /usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not find 
> 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-guard/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0',
>  execute `gem env` for more information
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in 
> activate_dependencies'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1405:in `block in 
> activate_dependencies'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem'
>   from -e:1:in `'
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.2)
> cgi (default: 0.1.0)
> coderay (1.1.2)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0, 1.2.1)
> diff-lcs (1.3)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> ffi (1.12.2)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> formatador (0.2.5)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> io-console (default: 0.5.3)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.1)
> json (default: 2.3.0)
> listen (3.1.5)
> logger (default: 1.4.2)
> lumberjack (1.0.13)
> matrix (default: 0.2.0)
> method_source (1.0.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> nenv (0.3.0)
> net-pop (default: 0.1.0)
> net-smtp (default: 0.1.0)
> net-telnet (0.1.1)
> notiffany (0.1.3)
> observer (default: 0.1.0)
> open3 (default: 0.1.0)
> openssl (default: 2.1.2)
> ostruct (default: 0.2.0)
> power_assert (1.1.6)
> prime (default: 0.1.1)
> pry (0.12.2)
> pstore (default: 0.1.0)
> psych (default: 3.1.0)
> racc (default: 1.4.16)
> rake (13.0.1)
> rb-inotify (0.9.10)
> rdoc (default: 6.2.1)
> readline (default: 0.0.2)
> readline-ext (default: 0.1.0)
> reline (default: 0.1.2)
> rexml (default: 3.2.3)
> rspec (3.9.0)
> rspec-core (3.9.1)
> rspec-expectations (3.9.0)
> rspec-mocks (3.9.1)
> rspec-support (3.9.2)
> rss (default: 0.2.8)
> sdbm (default: 1.0.0)
> shellany (0.0.1)
> singleton (default: 0.1.0)
> stringio (default: 0.1.0)
> strscan (default: 1.0.3)
> test-unit (3.3.4)
> thor (0.19.4)
> timeout (default: 0.1.0)
> tracer (default: 0.1.0)
> uri (default: 0.10.0)
> webrick (default: 1.6.0)
> xmlrpc (0.3.0)
> yaml (default: 0.1.0)
> zlib (default: 1.1.0)
> ERROR: Test "ruby2.7" failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/ruby-guard_2.16.1-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Processed: Bug#952199 marked as pending in golang-github-boltdb-bolt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952199 [src:golang-github-boltdb-bolt] golang-github-boltdb-bolt: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short 
github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt returned exit code 1
Added tag(s) pending.

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