Processed: block 953701 with 954628

[Debian Bug Tracking System]

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

> block 953701 with 954628
Bug #953701 {Done: Paul Gevers } [src:pycallgraph] 
src:pycallgraph: fails to migrate to testing for too long
953701 was not blocked by any bugs.
953701 was not blocking any bugs.
Added blocking bug(s) of 953701: 954628
> thanks
Stopping processing here.

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

Processed: block 953781 with 953996

[Debian Bug Tracking System]

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

> block 953781 with 953996
Bug #953781 [src:julia] src:julia: fails to migrate to testing for too long
953781 was not blocked by any bugs.
953781 was not blocking any bugs.
Added blocking bug(s) of 953781: 953996
> thanks
Stopping processing here.

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

Bug#956400: marked as done (qpdf: FTBFS on multiple 32-bit architectures, needs libatomic)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 22:54:12 -0400
with message-id <19e51f3b-81ec-4039-8023-e924ab054...@www.fastmail.com>
and subject line fixed in 10.0.1-2
has caused the Debian Bug report #956400,
regarding qpdf: FTBFS on multiple 32-bit architectures, needs libatomic
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.)


-- 
956400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qpdf
Version: 10.0.1-1
Severity: serious
Justification: ftbfs
User: debian-...@lists.debian.org
Usertags: armel

Hi!

qpdf fails to build from source on multiple architectures due to
missing symbols from libatomic [1]:

/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[1]: *** [libtests/build.mk:52: libtests/build/aes] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: *** [libtests/build.mk:52: libtests/build/bits] Error 1
make[1]: *** [zlib-flate/build.mk:22: zlib-flate/build/zlib-flate] Error 1
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[1]: *** [libtests/build.mk:52: libtests/build/buffer] Error 1
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status

This is a known issue with gcc [2] and can be fixed by linking against
libatomic, similar to apt-cacher-ng [3] and [4]. Please apply such
a fix for armel, mipsel, m68k, powerpc and sh4.

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=qpdf=armel=10.0.1-1=1586486160=0
>  
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862002
> [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859689
--- End Message ---
--- Begin Message ---
Version: 10.0.1-2

I listed the wrong bug number in debian/changelog (accidentally copying the bug 
number from an earlier changelog entry), so this message is to close the bug 
now that the fix has been uploaded and did actually fix the problem.--- End Message ---

Bug#956400: Processed: retitle 956400 to qpdf: FTBFS on multiple 32-bit architectures, needs libatomic

[Jay Berkenbilt]

Oops, I fixed this, but I made a cut and paste error and "Closed" the wrong bug 
number in the changelog. I wlll clean it up tomorrow by removing the fixed 
version from the wrong bug and adding it to the right one.

On Fri, Apr 10, 2020, at 1:39 PM, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > retitle 956400 qpdf: FTBFS on multiple 32-bit architectures, needs libatomic
> Bug #956400 [src:qpdf] pdf: FTBFS on multiple 32-bit architectures, needs 
> libatomic
> Changed Bug title to 'qpdf: FTBFS on multiple 32-bit architectures, needs 
> libatomic' from 'pdf: FTBFS on multiple 32-bit architectures, needs 
> libatomic'.
> > thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.
> -- 
> 956400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956400
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> 

Bug#956339: unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures

[Paul Wise]

Control: reopen -1

On Fri, 2020-04-10 at 21:28 +0800, Paul Wise wrote:

> I've tested this by downgrading popularity-contest using snapshot.d.o,
> adding changes to a conffile and then running u-u. The result is that I
> get this in the report, so it looks fixed again:

Actually it looks like this is not fixed after all. This time I got
both the popularity-contest upgrade failure due to conffile prompt and
the message that popularity-contest needs to be upgraded manually:

Subject:[package on hold] unattended-upgrades result for host: FAILURE

Unattended upgrade result: All upgrades installed

Packages that attempted to upgrade:
 ... popularity-contest ...

...

Log started: 2020-04-11  09:31:17
apt-listchanges: Reading changelogs...
Preconfiguring packages ...
apt-listchanges: Reading changelogs...
Preconfiguring packages ...
Preparing to unpack .../popularity-contest_1.70_all.deb ...
Unpacking popularity-contest (1.70) over (1.69) ...
Setting up popularity-contest (1.70) ...

Configuration file '/etc/cron.daily/popularity-contest'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** popularity-contest (Y/I/N/O/D/Z) [default=N] ? dpkg: error
processing package popularity-contest (--configure):
 end of file on stdin at conffile prompt
Processing triggers for man-db (2.9.1-1) ...
Errors were encountered while processing:
 popularity-contest
Log ended: 2020-04-11  09:31:50

...

Unattended-upgrades log:
Starting unattended upgrades script
Allowed origins are: origin=Debian,codename=bullseye,label=Debian, 
origin=Debian,codename=bullseye,label=Debian-Security, 
origin=Debian,codename=bullseye-security,label=Debian-Security, origin=Debian
Initial blacklist: 
Initial whitelist (not strict): 
Package popularity-contest has conffile prompt and needs to be upgraded manually
Packages that will be upgraded: ... popularity-contest ...
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
Installing the upgrades failed!
error message: installArchives() failed
dpkg returned a error! See 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: Re: Bug#956339: unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #956339 {Done: Paul Wise } [unattended-upgrades] 
unattended-upgrades: regression: packages with conffile prompts are no longer 
skipped, leading to upgrade failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.2.

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

Bug#939995: libltcsmpte: no reverse dependencies - remove from the archive?

[Boyuan Yang]

X-Debbugs-CC: sramac...@debian.org ales...@debian.org ro...@gareus.org

Hi,

On Tue, 10 Sep 2019 22:29:52 +0200 Sebastian Ramacher 
wrote:
> Package: src:libltcsmpte
> Version: 0.4.4-1
> Severity: serious
> Tags: sid bullseye
> 
> libltcsmpte currently does not have any reverse dependencies in the
> archive. So, do we still need the package to be in the archive? If not,
> I'd suggest to remove it.

Since the original maintainers did not reply in the last 6 months and that the
upstream of libltcsmpte indeed indicated that the library has been superceded,
I will proceed with submitting removal request.

If you have any thoughts, please let me know immediately.

-- 
Regards,
Boyuan Yang


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

Bug#937784: marked as done (python-gevent: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 11 Apr 2020 00:33:56 +
with message-id 
and subject line Bug#937784: fixed in python-gevent 1.4.0-1.2
has caused the Debian Bug report #937784,
regarding python-gevent: 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.)


-- 
937784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-gevent
Version: 1.3.7-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:python-gevent

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: python-gevent
Source-Version: 1.4.0-1.2
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-gevent 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: Fri, 10 Apr 2020 20:03:00 -0400
Source: python-gevent
Architecture: source
Version: 1.4.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Sandro Tosi 
Closes: 937784 953956
Changes:
 python-gevent (1.4.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937784
   * Install documentation in python-gevent-doc dir; Closes: #953956
Checksums-Sha1:
 1b9fb9dccdb4b45240de624b2112bcd374392a2f 2192 python-gevent_1.4.0-1.2.dsc
 a8712c2ab0537296de572ce5b0908ae71fd36f37 71868 
python-gevent_1.4.0-1.2.debian.tar.xz
 65bacb271f1e49f7dce8d8caac3e0ae989c3cf3f 10078 
python-gevent_1.4.0-1.2_amd64.buildinfo
Checksums-Sha256:
 ebc9a18c32b3aa3499c997464e806e221c101c54184567bf1355d9359c882827 2192 
python-gevent_1.4.0-1.2.dsc
 0c9ab87760e8e1270eb04ed86f8795f6b80fc19b6cfda36ac2c47f978cc0241b 71868 
python-gevent_1.4.0-1.2.debian.tar.xz
 

Processed: python-gevent: diff for NMU version 1.4.0-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 937784 + patch
Bug #937784 [src:python-gevent] python-gevent: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #937784 to the same tags previously set
> tags 953956 + patch
Bug #953956 [python-gevent-doc] python-gevent-doc: should install doc in 
/usr/share/doc/python-gevent-doc/
Ignoring request to alter tags of bug #953956 to the same tags previously set

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

Bug#937784: python-gevent: diff for NMU version 1.4.0-1.2

[Sandro Tosi]

Control: tags 937784 + patch
Control: tags 953956 + patch


Dear maintainer,

I've prepared an NMU for python-gevent (versioned as 1.4.0-1.2). The diff
is attached to this message.

Please consider maintaining python-gevent with the Debian Python Modules team

Regards.

diff -Nru python-gevent-1.4.0/debian/changelog python-gevent-1.4.0/debian/changelog
--- python-gevent-1.4.0/debian/changelog	2020-03-14 18:47:23.0 -0400
+++ python-gevent-1.4.0/debian/changelog	2020-04-10 20:03:00.0 -0400
@@ -1,3 +1,11 @@
+python-gevent (1.4.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937784
+  * Install documentation in python-gevent-doc dir; Closes: #953956
+
+ -- Sandro Tosi   Fri, 10 Apr 2020 20:03:00 -0400
+
 python-gevent (1.4.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-gevent-1.4.0/debian/control python-gevent-1.4.0/debian/control
--- python-gevent-1.4.0/debian/control	2020-03-14 18:46:50.0 -0400
+++ python-gevent-1.4.0/debian/control	2020-04-10 19:14:24.0 -0400
@@ -1,35 +1,20 @@
 Source: python-gevent
 Priority: optional
 Maintainer: Laszlo Boszormenyi (GCS) 
-Build-Depends: debhelper (>= 11), dh-python, python-all-dev,
+Build-Depends: debhelper (>= 11), dh-python,
  dh-exec,
- libevent-dev (>= 1.4), python-greenlet (>= 0.4.15) | python-codespeak-lib (<< 1.0),
- python-all-dbg,
- python-greenlet-dbg, python3-greenlet-dbg,
- python-setuptools, python3-setuptools,
- python-cffi,  python-cffi-backend-dbg,
+ libevent-dev (>= 1.4),
+ python3-greenlet-dbg,
+ python3-setuptools,
  python3-cffi, python3-cffi-backend-dbg,
  python3-all-dev, python3-all-dbg, python3-greenlet (>= 0.4.15),
  python3-sphinx, python3-repoze.sphinx.autointerface,
- cython, cython-dbg, cython3,
+ cython3, cython3-dbg,
  libev-dev, libc-ares-dev
 Standards-Version: 4.3.0
 Section: python
 Homepage: http://www.gevent.org/
 
-Package: python-gevent-dbg
-Section: debug
-Architecture: any
-Depends: ${misc:Depends}, python-gevent (= ${binary:Version}), ${shlibs:Depends}, ${python:Depends},
- python-greenlet-dbg
-Provides: ${python:Provides}
-XB-Python-Version: ${python:Versions}
-Description: gevent is a coroutine-based Python networking library - debugging symbols
- gevent uses greenlet to provide a high-level synchronous API on top of
- libevent event loop.
- .
- This is the debugging symbols for gevent.
-
 Package: python-gevent-doc
 Section: doc
 Architecture: all
@@ -41,17 +26,6 @@
  .
  This is the documentation for gevent.
 
-Package: python-gevent
-Section: python
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, python-greenlet (>= 0.3.2) | python-codespeak-lib (<< 1.0)
-Provides: ${python:Provides}
-XB-Python-Version: ${python:Versions}
-Suggests: python-gevent-doc, python-gevent-dbg, python-openssl
-Description: gevent is a coroutine-based Python networking library
- gevent uses greenlet to provide a high-level synchronous API on top of
- libevent event loop.
-
 Package: python3-gevent
 Section: python
 Architecture: any
diff -Nru python-gevent-1.4.0/debian/python-gevent-dbg.install python-gevent-1.4.0/debian/python-gevent-dbg.install
--- python-gevent-1.4.0/debian/python-gevent-dbg.install	2018-07-07 13:23:32.0 -0400
+++ python-gevent-1.4.0/debian/python-gevent-dbg.install	1969-12-31 19:00:00.0 -0500
@@ -1,4 +0,0 @@
-usr/lib/python2*/*-packages/gevent/*_d.so
-usr/lib/python2*/*-packages/gevent/libev/*_d.so
-usr/lib/python2*/*-packages/gevent/libuv/*_d.so
-usr/lib/python2*/*-packages/gevent/resolver/*_d.so
diff -Nru python-gevent-1.4.0/debian/python-gevent.docs python-gevent-1.4.0/debian/python-gevent.docs
--- python-gevent-1.4.0/debian/python-gevent.docs	2011-05-17 10:45:37.0 -0400
+++ python-gevent-1.4.0/debian/python-gevent.docs	1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-README.rst
-TODO
diff -Nru python-gevent-1.4.0/debian/python-gevent.install python-gevent-1.4.0/debian/python-gevent.install
--- python-gevent-1.4.0/debian/python-gevent.install	2018-07-07 13:23:32.0 -0400
+++ python-gevent-1.4.0/debian/python-gevent.install	1969-12-31 19:00:00.0 -0500
@@ -1,10 +0,0 @@
-usr/lib/python2*/*-packages/gevent/*.py
-usr/lib/python2*/*-packages/gevent/*[!_][!d].so
-usr/lib/python2*/*-packages/gevent/_ffi/*.py
-usr/lib/python2*/*-packages/gevent/libev/*.py
-usr/lib/python2*/*-packages/gevent/libev/*[!_][!d].so
-usr/lib/python2*/*-packages/gevent/libuv/*.py
-usr/lib/python2*/*-packages/gevent/libuv/*[!_][!d].so
-usr/lib/python2*/*-packages/gevent/resolver/*.py
-usr/lib/python2*/*-packages/gevent/resolver/*[!_][!d].so
-usr/lib/python2*/*-packages/*.egg-info
diff -Nru python-gevent-1.4.0/debian/rules python-gevent-1.4.0/debian/rules
--- python-gevent-1.4.0/debian/rules	2020-03-14 18:47:20.0 -0400
+++ python-gevent-1.4.0/debian/rules	2020-04-10 19:53:23.0 -0400
@@ -6,10 +6,10 @@
 
 export SHELL = /bin/bash
 

Processed: python-gevent: diff for NMU version 1.4.0-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 937784 + patch
Bug #937784 [src:python-gevent] python-gevent: Python2 removal in sid/bullseye
Added tag(s) patch.
> tags 953956 + patch
Bug #953956 [python-gevent-doc] python-gevent-doc: should install doc in 
/usr/share/doc/python-gevent-doc/
Added tag(s) patch.

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

Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept

[Colin Watson]

Control: reassign -1 python-wsgi-intercept 1.8.1-2
Control: clone -1 -2
Control: reassign -2 python3-httplib2 0.14.0-1
Control: retitle -2 python3-httplib2 >= 1.13.0 breaks python3-wsgi-intercept << 
1.9.0
Control: block -2 by -1

On Tue, Feb 11, 2020 at 11:43:03PM +0100, Andreas Beckmann wrote:
> I have a little trouble getting what you mean here:
> 
> On Mon, 10 Feb 2020 17:52:33 +0100 =?UTF-8?Q?H=c3=a5vard_Flaget_Aasen?=
>  wrote:
> > Though they write that the change was indeed in the httplib2 package.
> 
> * the change that introduced the bug
> * the change that fixed the bug (is there an embedded copy of httplib2
> somewhere?)
> * both ?

wsgi-intercept reimplements a bit of httplib2's interface in order to
intercept calls to it.  Until version 1.9.0, the way it did so violated
httplib2's reasonable expectations of its own interface, that is, that
httplib2 could reasonably add more keyword arguments to its own classes'
__init__ methods.  This is a perfectly normal way to extend interfaces
in Python, and it only broke because wsgi-intercept was making
unwarranted assumptions.

https://github.com/cdent/wsgi-intercept/commit/c4d44f5712e85d302db7e80e16156ca9c501bb6b
(in part) fixes this by ignoring those extra keyword arguments for the
purpose of interception, which indeed seems sensible since details of
TLS versions aren't very relevant when you're writing tests that
intercept network calls and redirect them to a WSGI application.

So, I disagree with Thomas that this is principally a bug in httplib2,
and I'm reassigning it back to wsgi-intercept.  The main part of the fix
should be to upgrade wsgi-intercept to 1.9.0 or newer.  However, it
would probably be appropriate for python3-httplib2 to declare a Breaks
on python3-wsgi-intercept (<< 1.9.0) once a fixed version exists in the
archive, so I'm cloning a part of this bug for that.

-- 
Colin Watson   [cjwat...@debian.org]

Processed: Re: Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-wsgi-intercept 1.8.1-2
Bug #950038 [python3-httplib2] python-wsgi-intercept FTBFS: test failures
Bug reassigned from package 'python3-httplib2' to 'python-wsgi-intercept'.
No longer marked as found in versions python-httplib2/0.14.0-1.
Ignoring request to alter fixed versions of bug #950038 to the same values 
previously set
Bug #950038 [python-wsgi-intercept] python-wsgi-intercept FTBFS: test failures
There is no source info for the package 'python-wsgi-intercept' at version 
'1.8.1-2' with architecture ''
Unable to make a source version for version '1.8.1-2'
Marked as found in versions 1.8.1-2.
> clone -1 -2
Bug #950038 [python-wsgi-intercept] python-wsgi-intercept FTBFS: test failures
Bug 950038 cloned as bug 956427
> reassign -2 python3-httplib2 0.14.0-1
Bug #956427 [python-wsgi-intercept] python-wsgi-intercept FTBFS: test failures
Bug reassigned from package 'python-wsgi-intercept' to 'python3-httplib2'.
No longer marked as found in versions 1.8.1-2.
Ignoring request to alter fixed versions of bug #956427 to the same values 
previously set
Bug #956427 [python3-httplib2] python-wsgi-intercept FTBFS: test failures
Marked as found in versions python-httplib2/0.14.0-1.
> retitle -2 python3-httplib2 >= 1.13.0 breaks python3-wsgi-intercept << 1.9.0
Bug #956427 [python3-httplib2] python-wsgi-intercept FTBFS: test failures
Changed Bug title to 'python3-httplib2 >= 1.13.0 breaks python3-wsgi-intercept 
<< 1.9.0' from 'python-wsgi-intercept FTBFS: test failures'.
> block -2 by -1
Bug #956427 [python3-httplib2] python3-httplib2 >= 1.13.0 breaks 
python3-wsgi-intercept << 1.9.0
956427 was not blocked by any bugs.
956427 was not blocking any bugs.
Added blocking bug(s) of 956427: 950038

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

Bug#937694: marked as done (python-decorator: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 22:48:52 +
with message-id 
and subject line Bug#937694: fixed in python-decorator 4.4.2-2
has caused the Debian Bug report #937694,
regarding python-decorator: 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.)


-- 
937694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-decorator
Version: 4.3.0-1.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:python-decorator

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: python-decorator
Source-Version: 4.4.2-2
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-decorator 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: Fri, 10 Apr 2020 18:39:17 -0400
Source: python-decorator
Architecture: source
Version: 4.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937694
Changes:
 python-decorator (4.4.2-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937694
Checksums-Sha1:
 f706b4945d35bd14c9ec50bf8b525f88f5243c2b 2070 python-decorator_4.4.2-2.dsc
 2457c189129a7f3005613c51f74a628880c7150d 3840 
python-decorator_4.4.2-2.debian.tar.xz
 778e9fe30e6064012f94cb74332098c81d4782aa 6509 
python-decorator_4.4.2-2_source.buildinfo
Checksums-Sha256:
 f49e148f5dcf02c2eb1607d2ef6b2b3616ed24eb137cb0742c12e90d9d35f6b0 2070 
python-decorator_4.4.2-2.dsc
 e25d0c993f8361171112e9b477939827919e1967c2381f8bc41aa81982cac82b 3840 
python-decorator_4.4.2-2.debian.tar.xz
 273c61d4cec7b247dabf6c24bbb99f256f29d3e3070329c43e213a70e86d83fc 6509 

Processed: Bug#937694 marked as pending in python-decorator

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#937694: marked as pending in python-decorator

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #937694 in python-decorator 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/python-decorator/-/commit/12618e371f2ec8a24b784b4f3deec0f2eb06e443


Drop python2 support; Closes: #937694


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937694

Processed: py2removal bugs severity updates - 2020-04-10 22:36:11.833844+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
> # and https://lists.debian.org/debian-python/2020/03/msg00087.html
> # mail threads for more details on this severity update
> # python-gevent is a module and has 0 external rdeps or not in testing
> severity 937784 serious
Bug #937784 [src:python-gevent] python-gevent: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-decorator is a module and has 0 external rdeps or not in testing
> severity 937694 serious
Bug #937694 [src:python-decorator] python-decorator: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # python-trollius is a module and has 0 external rdeps or not in testing
> severity 938229 serious
Bug #938229 [src:python-trollius] python-trollius: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#956423: node-request: deprecated upstream: should not be part of next stable Debian release

[Jérémy Lal]

Le ven. 10 avr. 2020 à 23:48, Jonas Smedegaard  a écrit :

> Package: node-request
> Version: 2.88.1-4
> Severity: grave
> Justification: renders package unusable
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Upstream has deprecated this module:
> https://github.com/request/request/issues/3142
>
> It already has seen no new updates for a year,
> and is not expected to do so:
> This module is unsuitable for next stable Debian release!
>
> Upstream issue discusses alternatives to use instead.
>

Yes, node-request should be dropped.
Best smooth (transition-wise) replacement is "got":
https://github.com/sindresorhus/got#comparison
I'm using it everywhere, it works, it's alive and well documented.

Jérémy

Bug#956423: node-request: deprecated upstream: should not be part of next stable Debian release

[Jonas Smedegaard]

Package: node-request
Version: 2.88.1-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Upstream has deprecated this module:
https://github.com/request/request/issues/3142

It already has seen no new updates for a year,
and is not expected to do so:
This module is unsuitable for next stable Debian release!

Upstream issue discusses alternatives to use instead.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6Q6LkACgkQLHwxRsGg
ASHgqg/9FXRMJxxxpyv7BZHDM+dj3CMBHCHqjd29i+I3kyHND8HBe4sncafdXN9/
0gAQsxtG3Ad81jqY0gGV2wMTf7jMQUGnF4F58TJCbZXcsDehfb4DGjTT4Z20rEoA
bd+pc8uMEojCYq+/Qd8yw9FW/MUgFmNEjZBG6MSM9O4QhxHEfVL4HlERK+DR+wok
f5WyvIfQrx5jlpiXcIT+mA0WmbI+kYqCnfF8zf09q2R1uMLr1XgRVkCei1BXI51d
PgLFWVgLXDshHJJJ2S/DNCdPRaW6vB0U9v31slnZcGgPuMvyz8rXuZqI8VlcaPo5
DAIAeJBV0ZLZx+gM1gxcYZdmoDB1OOvyTmSKkDb7axoiFLQZCScou+XMCCSP2QNW
NknuCkVphX4t4iNIgBZbypm4vw3xRyBJq+tdD3G4A1Myy/52ItXiPfx0GfgtuQsQ
OnNUceTZcYr/qHqptnxvRQ09yBQWQhuckkbVWWEddHIUJohlDs1M3Tjpu71rdULc
O85hZHZX/hUN0vyPBKfDTO7zlQJxpwyYYuVniRN7PQNLa3sY/En3cUZ6sQNTKKwM
JbG+Jxw4pHao7M6tYHslaTX19rh6QvLcCZI7526Qm2Ktc9Oi6VoP/5b14UzLIbdB
fPrPcnFRuY6ymbtGb27zqq+7ww2r2MWnRqVR1E8kNLY2Zrg8blM=
=nQxC
-END PGP SIGNATURE-

Bug#950221: marked as done (natsort 6.0 doesn't support Python 3.8)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 21:40:08 +
with message-id 
and subject line Bug#950221: fixed in natsort 7.0.1-0.1
has caused the Debian Bug report #950221,
regarding natsort 6.0 doesn't support Python 3.8
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.)


-- 
950221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:natsort
Version: 6.0.0-1.2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

natsort 6.0 doesn't support Python 3.8, 6.2 is the first version supporting it.
There's also a 7.0 release.
--- End Message ---
--- Begin Message ---
Source: natsort
Source-Version: 7.0.1-0.1
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated natsort package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Apr 2020 15:57:14 -0400
Source: natsort
Architecture: source
Version: 7.0.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Scott Talbert 
Closes: 950221
Changes:
 natsort (7.0.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update to new upstream release 7.0.1 (Closes: #950221)
   * Fix doc-base paths
Checksums-Sha1:
 bfa727201e60ae74f472c9d709d85f5fa5d085c0 2146 natsort_7.0.1-0.1.dsc
 578162cff6086f37bef57b17feb6732c90c9360c 133269 natsort_7.0.1.orig.tar.gz
 698711c5205ac78ebc393845f8de53b7a66dd4cd 4048 natsort_7.0.1-0.1.debian.tar.xz
 05bc6274761a99fc34cd05078b86cf5b6be5e9a4 7585 natsort_7.0.1-0.1_amd64.buildinfo
Checksums-Sha256:
 f53cb6a9a6fbc92a2c3ca297c5647026d906f5072c5b8c3fef8a1fea7b7cda2c 2146 
natsort_7.0.1-0.1.dsc
 bbb9ed51c001b6cb3c3b874ab2eb952e7458e5acc688c81e329a29d58b7dfbd2 133269 
natsort_7.0.1.orig.tar.gz
 26b862bd2eaf79b7002af8dd1dbc594caed5ad7e9eb87b6c3fb505d594033675 4048 
natsort_7.0.1-0.1.debian.tar.xz
 7b9495f1c1fe62b58c48a09199521c16cb688d67daa3e556df11d6b178a123a3 7585 
natsort_7.0.1-0.1_amd64.buildinfo
Files:
 a99be368817fe0b48f64677d9870cb26 2146 python optional natsort_7.0.1-0.1.dsc
 973fb6f44b8479066d4f31a15c4a6a70 133269 python optional 
natsort_7.0.1.orig.tar.gz
 dfb3ec8b5ef2feee793f22f7e4b99695 4048 python optional 
natsort_7.0.1-0.1.debian.tar.xz
 1d9267059a2798a90a5ef7868a279aa6 7585 python optional 
natsort_7.0.1-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAl6Q0isPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iiMT0P/2AeyTpBovEIB7lL9PHUGv6t3OhPHOpWi4+U
52qmey+mbxR4Venn1yp0clFpSuRVtMvloYZJIJdLZQ1Rkt8581gf/FlBfE4YmDDB
K/pvp83S/y/iJno4krODQDpO5S1ZPEVSF8I5JfLcUd1K+tCPfDlwrXsU970N9Tpd
SDnkhbOmNjIhFN5EZehKJYbAqCToHndFN8i1IDsvS+Bb/zU8ryw6WIPOnxoMBC/U
txbu0dY8wTG4qhapUwwQGM3BqVJxZVBrEcd8zIvW4UlvZdOXz1Hl+GELsQ1pLkpp
MtzYCegmg4nOOMsm4qb8HIpD733mJr+Oy/YbQzma+T9iyjUOEPq8FqpcFCL/qrlP
ShI0I9U0pBIP0inZORSHy+4I1tpM7uj3IdmtG/Bwo3nJpw5o4I+etVGzIMp37QJ2
UqJMN3qfRKN4iVO+4fnifJyxpc8LOOJ7MGtICMrrvGq78DVhIRm0gX85zQ0fWfsR
NyKJ1+/BUZfzruuuqs8HHF+0MeiTYYq9gGpxfjPFlIgDDOG7zuu9gn01LG7Fr1Na
1EuPfvHm4i2GWaWuPB92bxZwP/RZ1vyMOrQ4L9QLPn8dQt7ef71uXR8G7lM/41LL
A7nuebZuMZbZilI734PEf/TqDyA7qQWlPhDW0J/lDMO+Pd15Cni00GXpOB/BQ7+g
3emD73he
=LfuM
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 21:39:51 +
with message-id 
and subject line Bug#955012: fixed in librouteros 3.0.0-1.1
has caused the Debian Bug report #955012,
regarding src:librouteros: 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.)


-- 
955012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librouteros
Version: 2.2.0-1
Severity: serious
Control: fixed -1 3.0.0-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:librouteros
in its current version in unstable has been trying to migrate for 60
days [2]. Hence, I am filing this bug.

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

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

I have 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
[2] https://qa.debian.org/excuses.php?package=librouteros




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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated librouteros 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, 26 Mar 2020 20:39:57 +0100
Source: librouteros
Architecture: source
Version: 3.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Paul Gevers 
Closes: 955012
Changes:
 librouteros (3.0.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #955012)
Checksums-Sha1:
 e6aa315562bbe9a3bcd48cbc7932a8961e9248c4 1828 librouteros_3.0.0-1.1.dsc
 720cc8ffda8b8a9b63219714d45b781a3c93db80 2060 
librouteros_3.0.0-1.1.debian.tar.xz
Checksums-Sha256:
 ac7c1622a9c6e9e9205c838fe9d312478c115b85dc1c2c8dc90e19b5f09ffdc3 1828 
librouteros_3.0.0-1.1.dsc
 780972840140492ee4ef9f7c2b08812de471e9e7ecb08923c9e27693dc96b43c 2060 
librouteros_3.0.0-1.1.debian.tar.xz
Files:
 4b982da093904c28c81f0a932bc56f86 1828 python optional librouteros_3.0.0-1.1.dsc
 728267b57831ddf5e6dfb21b3cd6ba14 2060 python optional 
librouteros_3.0.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl59BTcACgkQnFyZ6wW9
dQpwWAf9FUy17lNP+WfUSG+w7NaYw9mLTdUqtYjT4ChfJ7MdK7xolNClzL8YXyWQ
Xbkm6G+psbgO7sNiCJArX/DPqDqA0usCe7rIrl/nMQPN9zbI+V/Yap3M2L/6H6Vv
jFiuSTLVveX3TnI6aHDfzXtmfILVM/P0EM1M3QfM7dj1XHd876kiH2myvyYrV5Nl
Y35fbjtojL5dlnBiP5ciCasD7h97W4PmozICItp2sY2WhmTvtwgHxTRbO/Xxpz4U
QN2gEZdFkQqT/zOXAwQhDBmY7b+pbKDlDi1nLzBvvKKADgXRvIfPijz0S03GaYQr

Bug#955652: marked as done (dvdbackup: FTBFS: dvdbackup.c:1282:29: error: ‘ifo_handle_t’ {aka ‘struct ’} has no member named ‘file’)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 21:34:58 +
with message-id 
and subject line Bug#955652: fixed in dvdbackup 0.4.2-4.1
has caused the Debian Bug report #955652,
regarding dvdbackup: FTBFS: dvdbackup.c:1282:29: error: ‘ifo_handle_t’ {aka 
‘struct ’} has no member named ‘file’
to be marked as done.

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

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


-- 
955652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvdbackup
Version: 0.4.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -DLOCALEDIR=\"/usr/share/locale\" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -pedantic -Wall -Wextra  -c -o dvdbackup.o dvdbackup.c
> dvdbackup.c: In function ‘DVDWriteCells’:
> dvdbackup.c:172:22: warning: unused parameter ‘title_set_info’ 
> [-Wunused-parameter]
>   172 |   title_set_info_t * title_set_info, titles_info_t * titles_info,
>   |   ~~~^~
> dvdbackup.c: In function ‘DVDCopyIfoBup’:
> dvdbackup.c:1282:29: error: ‘ifo_handle_t’ {aka ‘struct ’} has no 
> member named ‘file’
>  1282 |  size = DVDFileSize(ifo_file->file) * DVD_VIDEO_LB_LEN;
>   | ^~
> dvdbackup.c:1295:22: error: ‘ifo_handle_t’ {aka ‘struct ’} has no 
> member named ‘file’
>  1295 |  DVDFileSeek(ifo_file->file, 0);
>   |  ^~
> dvdbackup.c:1297:27: error: ‘ifo_handle_t’ {aka ‘struct ’} has no 
> member named ‘file’
>  1297 |  if (DVDReadBytes(ifo_file->file,buffer,size) != size) {
>   |   ^~
> make[3]: *** [Makefile:392: dvdbackup.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/04/02/dvdbackup_0.4.2-4_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: dvdbackup
Source-Version: 0.4.2-4.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated dvdbackup 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Apr 2020 17:57:40 +0200
Source: dvdbackup
Architecture: source
Version: 0.4.2-4.1
Distribution: unstable
Urgency: medium
Maintainer: Stephen Gran 
Changed-By: Sebastian Ramacher 
Closes: 955652
Changes:
 dvdbackup (0.4.2-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/libdvdread6.1.0.patch: Adapt to API changes in libdvdread
 6.1.0 (Closes: #955652)
 Thanks to Felix Palmen for the patch.
Checksums-Sha1:
 b91f08cdb83f85b4506f87330efde7b0e59b82e5 2015 dvdbackup_0.4.2-4.1.dsc
 e872e7bc851cfe2741678a1cb74fd71cdbedfffb 7804 dvdbackup_0.4.2-4.1.debian.tar.xz
Checksums-Sha256:
 97630e6fbe7c81a3555fc313d16bdb8b59ad59d6c5f303d1ff87fe067392f1cf 2015 
dvdbackup_0.4.2-4.1.dsc
 9a7563696291c309ccdb07cbadc0b1457edc6ddb26f670dddc630c094ddd53eb 7804 
dvdbackup_0.4.2-4.1.debian.tar.xz
Files:
 98d5c3f3a6b62bd6f373dbd8f1f1d8a3 2015 video optional dvdbackup_0.4.2-4.1.dsc
 84287ede8b3e7ffddf6c634cbcc9f8b8 7804 video optional 
dvdbackup_0.4.2-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl6KP0EACgkQafL8UW6n
GZMJIw//a1vAYY+YuvUAB5kruPDIQfx0VCQJRrGSZEtqnNxUz10jycKKBQt/M1Tp
2bEhYLKaaKqufLEZT7m2M1MMImkPQVDG/yHFrmAcYRrs/JvryqFhfAyett3rA+Or
OM5UmdkCWxB3r0j0UVeF71d9SvOTO74d0dsQBQhTDcN1lBA6Y02aL7lxJa3jDENE

Bug#956211: marked as done (nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 21:36:53 +
with message-id 
and subject line Bug#956211: fixed in gitlab 12.9.2-2
has caused the Debian Bug report #956211,
regarding nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL 
ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript 
heap out of memory
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.)


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

Package: nodejs
Version: 10.19.0~dfsg-3
Severity: grave
Control: notfound -1 12.13.1~dfsg-1


nodejs 10 crashed (retried again) and on the same machine nodejs 12 
worked.
This has been working upto gitlab 12.8.8 and the failure appeared when 
trying to update to 12.9.2 (just installing gitlab from experimental in 
an lxc container).


Error log:

Webpacking...

<--- Last few GCs --->

[24574:0x115ca70] 107413 ms: Mark-sweep 1198.8 (1412.3) -> 1198.8 
(1394.3) MB, 416.5 / 0.0 ms (average mu = 0.279, current mu = 0.173) 
allocation failure GC in old space requested
[24574:0x115ca70] 107885 ms: Mark-sweep 1198.8 (1394.3) -> 1198.7 
(1377.3) MB, 471.2 / 0.0 ms (average mu = 0.156, current mu = 0.000) 
allocation failure GC in old space requested



<--- JS stacktrace --->

 JS stack trace =

   0: ExitFrame [pc: 0x3a074a953601]
Security context: 0x2f623c1aee11 
   1: byteLength(aka byteLength) [0x2f084ce7fc21] [buffer.js:~508] 
[pc=0x3a074cfbb510](this=0x310243e825d9 
,string=0x169dd7c44199 string[17095443]>,encoding=0x2f623c1f2a51 )

   2: arguments adaptor frame: 3->2
   3: fromString(aka fromString) [0xffe581cb31] [buffer.js:~333] 
[pc=0x3a074c17a1b7](this=0x310243e825d9 

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation 
failed - JavaScript heap out of memory

1: 0x7f7c4fc60ea8 node::Abort() [/lib/x86_64-linux-gnu/libnode.so.64]
2: 0x7f7c4fc60ef1 [/lib/x86_64-linux-gnu/libnode.so.64]
3: 0x7f7c4fe89642 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, 
char const*, bool) [/lib/x86_64-linux-gnu/libnode.so.64]
4: 0x7f7c4fe89894 
v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char 
const*, bool) [/lib/x86_64-linux-gnu/libnode.so.64]

5: 0x7f7c5021ad32 [/lib/x86_64-linux-gnu/libnode.so.64]
6: 0x7f7c5022be43 
v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, 
v8::GCCallbackFlags) [/lib/x86_64-linux-gnu/libnode.so.64]
7: 0x7f7c5022c72c 
v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, 
v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) 
[/lib/x86_64-linux-gnu/libnode.so.64]
8: 0x7f7c5022e6e5 v8::internal::Heap::AllocateRawWithLigthRetry(int, 
v8::internal::AllocationSpace, v8::internal::AllocationAlignment) 
[/lib/x86_64-linux-gnu/libnode.so.64]
9: 0x7f7c5022e731 v8::internal::Heap::AllocateRawWithRetryOrFail(int, 
v8::internal::AllocationSpace, v8::internal::AllocationAlignment) 
[/lib/x86_64-linux-gnu/libnode.so.64]
10: 0x7f7c501fb149 
v8::internal::Factory::AllocateRawWithImmortalMap(int, 
v8::internal::PretenureFlag, v8::internal::Map*, 
v8::internal::AllocationAlignment) [/lib/x86_64-linux-gnu/libnode.so.64]
11: 0x7f7c502036e0 v8::internal::Factory::NewRawTwoByteString(int, 
v8::internal::PretenureFlag) [/lib/x86_64-linux-gnu/libnode.so.64]
12: 0x7f7c5033fec5 
v8::internal::String::SlowFlatten(v8::internal::Handle, 
v8::internal::PretenureFlag) [/lib/x86_64-linux-gnu/libnode.so.64]
13: 0x7f7c4fe93768 v8::String::Utf8Length() const 
[/lib/x86_64-linux-gnu/libnode.so.64]

14: 0x7f7c4fc7b6d5 [/lib/x86_64-linux-gnu/libnode.so.64]
15: 0x3a074a953601
Aborted
dpkg: error processing package gitlab (--install):
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 12.9.2-2
Done: Pirate Praveen 

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab 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

Bug#955013: marked as done (src:boxer-data: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 21:34:18 +
with message-id 
and subject line Bug#955013: fixed in boxer-data 10.8.12+nmu1
has caused the Debian Bug report #955013,
regarding src:boxer-data: 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.)


-- 
955013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boxer-data
Version: 10.8.11
Severity: serious
Control: fixed -1 10.8.12
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:boxer-data in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

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

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

I have 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
[2] https://qa.debian.org/excuses.php?package=boxer-data




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: boxer-data
Source-Version: 10.8.12+nmu1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated boxer-data 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, 26 Mar 2020 20:39:30 +0100
Source: boxer-data
Architecture: source
Version: 10.8.12+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Boxer developers 
Changed-By: Paul Gevers 
Closes: 955013
Changes:
 boxer-data (10.8.12+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #955013)
Checksums-Sha1:
 8419ec8017314b0df247a31b3047cf1af6231aa7 1488 boxer-data_10.8.12+nmu1.dsc
 284fbfc2779859351c19668c9e1f558166851fad 90232 boxer-data_10.8.12+nmu1.tar.xz
Checksums-Sha256:
 18869684e6b4d5907069b462a1f324bb21e6583d334352d5fe044604d2ec4c57 1488 
boxer-data_10.8.12+nmu1.dsc
 b4122ead0fcfb68c1e388f9707425303cbd43d3e3d729713d765ce1c8b844832 90232 
boxer-data_10.8.12+nmu1.tar.xz
Files:
 183316e8631cf8a62f55e06591c38d45 1488 misc optional boxer-data_10.8.12+nmu1.dsc
 b44994297f311d00d8e665bdf0b4fc76 90232 misc optional 
boxer-data_10.8.12+nmu1.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl59BRYACgkQnFyZ6wW9
dQqnbQf7B21z2dufsFzMxJEpb7WmyA+e5+DALJVQQxnpjKunBYOgGQwQHGMSTeSZ
gADw/J/Ij+/NZ/jhqYfJ5fhDU+a6KvHcsH3xvZQgZOSV6lHdy9tllPtIDDiVSdlj
vZDKg583W6rQK3+txldn4m3mY3Os9z8ohcVIhTwwy0mOWk+QD3X6ecvQzlC7+6t4
jhFJRLNRP7nItYtOfZevILdD0k8QBmnVL/fH6B6gSo8Hw46AmcBf3QZHT5dUc0wX
nfygoqZwuVKIq459Z0RM08xrpYXO+VmSSaKnlg1TZshG1KcZR9ZOhJuvFF/YsBXe

Bug#950221: salsa: Please transfer natsort from debian to python-team/modules

[Joerg Jaspert]

On 15734 March 1977, Scott Talbert wrote:

Hello again Salsa admins.  Can you please transfer natsort to 
python-team/modules?


I would like to get natsort fixed ASAP.


https://salsa.debian.org/python-team/modules/natsort

--
bye, Joerg

Bug#956420: src:pynwb: fails to migrate to testing for too long

[Paul Gevers]

Source: pynwb
Version: 0.5.1-2
Severity: serious
Control: fixed -1 1.2.1-2
Tags: sid bullseye
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:pynwb in its
current version in unstable has been trying to migrate for 62 days [2].
Hence, I am filing this bug.

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

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

I have 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.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

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




signature.asc
Description: OpenPGP digital signature

Processed: src:pynwb: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.2.1-2
Bug #956420 [src:pynwb] src:pynwb: fails to migrate to testing for too long
Marked as fixed in versions pynwb/1.2.1-2.

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

Bug#956419: src:speechd-el: fails to migrate to testing for too long

[Paul Gevers]

Source: speechd-el
Version: 2.8-2.1
Severity: serious
Control: fixed -1 2.9-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:speechd-el in
its current version in unstable has been trying to migrate for 63 days
[2]. Hence, I am filing this bug.

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

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

I have 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
[2] https://qa.debian.org/excuses.php?package=speechd-el




signature.asc
Description: OpenPGP digital signature

Processed: src:speechd-el: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.9-1
Bug #956419 [src:speechd-el] src:speechd-el: fails to migrate to testing for 
too long
Marked as fixed in versions speechd-el/2.9-1.

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

Bug#956288: Problems identified in debian/copyright

[Thomas Lange]

Hi Michael,

thanks for your proposal. I've patched the copyright file and uploaded
a new version.

I left this part unchanged, since it's a different license
which is different to the license for Files: *

Files: install/dracut-install.c
Copyright:
 (C) 2012 Harald Hoyer
 (C) 2012 Red Hat, Inc.  All rights reserved.
License: LGPL-2.1+

-- 
regards Thomas

Processed: sipxtapi: diff for NMU version 3.3.0~test17-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 954547 + patch
Bug #954547 [src:sipxtapi] sipxtapi: FTBFS: os/linux/OsTaskLinux.cpp:52:19: 
error: ‘int gettid()’ was declared ‘extern’ and later ‘static’ [-fpermissive]
Added tag(s) patch.
> tags 954547 + pending
Bug #954547 [src:sipxtapi] sipxtapi: FTBFS: os/linux/OsTaskLinux.cpp:52:19: 
error: ‘int gettid()’ was declared ‘extern’ and later ‘static’ [-fpermissive]
Added tag(s) pending.

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

Bug#954547: sipxtapi: diff for NMU version 3.3.0~test17-3.1

[Sudip Mukherjee]

Control: tags 954547 + patch
Control: tags 954547 + pending

Dear maintainer,

I've prepared an NMU for sipxtapi (versioned as 3.3.0~test17-3.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru sipxtapi-3.3.0~test17/debian/changelog 
sipxtapi-3.3.0~test17/debian/changelog
--- sipxtapi-3.3.0~test17/debian/changelog  2018-04-13 21:49:44.0 
+0100
+++ sipxtapi-3.3.0~test17/debian/changelog  2020-04-10 20:32:50.0 
+0100
@@ -1,3 +1,10 @@
+sipxtapi (3.3.0~test17-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS. (Closes: #954547) 
+
+ -- Sudip Mukherjee   Fri, 10 Apr 2020 20:32:50 
+0100
+
 sipxtapi (3.3.0~test17-3) unstable; urgency=high
 
   [ Rene Engelhard ]
diff -Nru sipxtapi-3.3.0~test17/debian/patches/fix_gettid.patch 
sipxtapi-3.3.0~test17/debian/patches/fix_gettid.patch
--- sipxtapi-3.3.0~test17/debian/patches/fix_gettid.patch   1970-01-01 
01:00:00.0 +0100
+++ sipxtapi-3.3.0~test17/debian/patches/fix_gettid.patch   2020-04-10 
20:32:47.0 +0100
@@ -0,0 +1,39 @@
+Description: Fix FTBFS
+ Latest glibc has defined gettid() and as a result there was a conflict.
+ Rename gettid() to sys_gettid() to use our own gettid instead of using
+ the gettid() from glibc.
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/954547
+
+---
+
+--- sipxtapi-3.3.0~test17.orig/sipXportLib/src/os/linux/OsTaskLinux.cpp
 sipxtapi-3.3.0~test17/sipXportLib/src/os/linux/OsTaskLinux.cpp
+@@ -27,7 +27,7 @@
+ #include 
+ #undef _P1003_1B_VISIBLE
+ 
+-// Include to access gettid() syscall for debug purposes
++// Include to access sys_gettid() syscall for debug purposes
+ #include 
+ 
+ // APPLICATION INCLUDES
+@@ -49,7 +49,7 @@
+ 
+ // EXTERNAL FUNCTIONS
+ #ifndef ANDROID // [
+-static inline int gettid() {return syscall(SYS_gettid);}
++static inline int sys_gettid() {return syscall(SYS_gettid);}
+ #endif // !ANDROID ]
+ 
+ // EXTERNAL VARIABLES
+@@ -783,7 +783,7 @@ void * OsTaskLinux::taskEntry(void* arg)
+ 
+// Log Thread ID for debug purposes
+OsSysLog::add(FAC_KERNEL, PRI_DEBUG, "OsTaskLinux::taskEntry: Started task 
%s with lwp=%d, pid=%d",
+- pTask->mName.data(), gettid(), getpid());
++ pTask->mName.data(), sys_gettid(), getpid());
+ 
+ #ifdef ANDROID // [
+pTask->setPriority(pTask->mPriority);
diff -Nru sipxtapi-3.3.0~test17/debian/patches/series 
sipxtapi-3.3.0~test17/debian/patches/series
--- sipxtapi-3.3.0~test17/debian/patches/series 2018-04-13 21:49:44.0 
+0100
+++ sipxtapi-3.3.0~test17/debian/patches/series 2020-04-10 20:31:11.0 
+0100
@@ -2,3 +2,4 @@
 openssl11.patch
 cppunit.patch
 add-license-rfc-4634.patch
+fix_gettid.patch

Bug#956211: [Pkg-javascript-devel] Bug#956211: Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]

[Jérémy Lal]

Le ven. 10 avr. 2020 à 21:15, Pirate Praveen  a
écrit :

> Control: reassign -1 gitlab
> Control: tags -1 -wontfix
>
> On Sat, Apr 11, 2020 at 12:32 am, Pirate Praveen
>  wrote:
> >
> >
> > On Fri, Apr 10, 2020 at 8:58 pm, Jérémy Lal 
> > wrote:
> >>
> >>
> >> Le ven. 10 avr. 2020 à 20:50, Pirate Praveen
> >>   a écrit :
> >>>
> >>>
> >>>  On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal 
> >>>   wrote:
> >>>  > Package: nodejs
> >>>  > Version: 10.19.0~dfsg-3
> >>>  > Followup-For: Bug #956211
> >>>  >
> >>>  > Pirate, i repeat, please try
> >>>  >
> >>>  > webpack --max-old-space-size=4096
> >>>  >
> >>>  > Or even a higher value. If it works, it's up to gitlab to use
> >>> that
> >>>  > flag.
> >>>  >
> >>>
> >>>  root@gitlab-buster:/usr/share/gitlab# runuser -u ${gitlab_user} --
> >>> sh
> >>>  -c 'webpack --max-old-space-size=8192 --config
> >>>   config/webpack.config.js'
> >>>
> >>>  I tried 4096, 6144, 8192, 16384 and all failed. How much higher
> >>>   should
> >>>  I go?
> >>
> >> Not further :)
> >> However then maybe that flag has no effect.
> >> Another way to pass the flag is by setting the environment variable:
> >> NODE_OPTIONS="–max-old-space-size=2048"
> >> Then again, runuser need to be told to handle this correctly.
> >>
> >
> > I will try this, probably tomorrow.
> >
>
> runuser -u ${gitlab_user} -- sh -c
> 'NODE_OPTIONS="--max-old-space-size=2048" webpack
> --max-old-space-size=16384 --config config/webpack.config.js'
>
> This worked. Thanks a lot.
>

Nice. My bad for having "googled" the answer.
Of course you need to remove the useless --max-old-space-size in your line.
 'NODE_OPTIONS="--max-old-space-size=2048" webpack
 --config config/webpack.config.js

but i bet you already noticed that.

>>>
> >>>  > Nodejs applications using high memory must use that kind of
> >>>  > workaround.
> >>>
> >>>  I was also exploring if excluding system libraries from
> >>> babel-loader
> >>>  reduces memory footprint.
> >>
> >> Yep, i saw that.
> >> Can you give me a quick way to reproduce the OOM error ?
> >>
> > If you are okay setting up gitlab from experimental on an lxc or vm
> > then instructions are here https://wiki.debian.org/gitlab
> >
> > Else I can set it up on a test VPS and give you access, possibly
> > tomorrow.
>

Well, if it worked, i won't bother and you shouldn't either.
Anyway i'm cool with following the wiki.

Jérémy

Bug#956229: marked as done (FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 19:48:47 +
with message-id 
and subject line Bug#956229: fixed in libtickit-widget-floatbox-perl 0.06-1
has caused the Debian Bug report #956229,
regarding FTBFS: test failures
to be marked as done.

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

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


-- 
956229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtickit-widget-floatbox-perl
Version: 0.05-1
Severity: serious
Tags: upstream ftbfs sid bullseye
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package started to fail its test after uploading one of the other
Tickit::* packages:

perl Build test --verbose 1
t/00use.t . 
ok 1 - use Tickit::Widget::FloatBox;
1..1
ok
Argument "Tickit::Rect[(0,0)..(80,25)]" isn't numeric in subroutine entry at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Tickit/Test.pm line 253.
Argument "Tickit::Rect[(0,0)..(100,30)]" isn't numeric in subroutine entry at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Tickit/Test.pm line 253.
t/01base-child.t .. 
ok 1 - defined $widget
ok 2 - scalar $widget->children
ok 3 - $widget->children[0]
ok 4 - $widget->children[0]->parent
ok 5 - $widget->lines with no bounds
ok 6 - $widget->cols with no bounds
ok 7 - child render rect
ok 8 - child render rect after term resize
1..8
ok
Too many arguments for subroutine 'Tickit::Widget::FloatBox::Float::BUILD' at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Object/Pad.pm line 378.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
t/02float.t ... 
ok 1 - Display initially
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed 
Too many arguments for subroutine 'Tickit::Widget::FloatBox::Float::BUILD' at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Object/Pad.pm line 378.
t/03hide-show.t ... 
Dubious, test returned 255 (wstat 65280, 0xff00)
No subtests run 
t/99pod.t . skipped: Test::Pod 1.00 required for testing POD

Test Summary Report
- ---
t/02float.t (Wstat: 65280 Tests: 1 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/03hide-show.t (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=5, Tests=10,  1 wallclock secs ( 0.02 usr  0.02 sys +  0.49 cusr  0.04 
csys =  0.57 CPU)
Result: FAIL
Failed 2/5 test programs. 0/10 subtests failed.



Cf. also 
https://ci.debian.net/data/autopkgtest/unstable/amd64/libt/libtickit-widget-floatbox-perl/4827036/log.gz
or http://www.cpantesters.org/cpan/report/c560fee6-75c9-11ea-9a78-d3801f24ea8f


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl6OB1ZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbLmg//VNUTviCtjmL7KoHLxkoCiOPCtdMFB2m8uwvSLwGCM4JFxtFej1BteesG
btzZnnF720TF6lgHxdG9MY86e8sf0Kf7azZibtRWcnLkeDkA4rRHpFrOuPuG6Pxj
nB+LVtZYjZoiOhkw4CgKW/9ltfMz/LdmVtQcFRwl3k892lpVj84Yp/TmqL8h5lY+
iZWsYLMZMUyLxel6noMwHDLfbe+lEUGs0xjkxE3zGKXy7Ux+iESPGRChwRYYdDgr
AbMQhyoxrk1iY+T6pnEtE+t+y49EC/pxPDgFwZLsVEU6XpgPUmtinib+ZEUjI6Z5
yIEDrG8SnFNqwhiulvsc17EASycdOwM5zVIPrLfXDp/k/TaLNjDzJsqU0WJfoTDP
hJjAQOfqwM8nLEpe/21L63kYBqaPTIXZjwU1Lk3WNPVOOrMY0pAstaPH195Aai6K
YtAvJ3dkxnC4zWK4MNyfzVtC2BjKdnsbuzbd0ONhKzQrgcibgIvxYldQY06AFuO2
qFol7wBgyK2i5unw2J/jO1FqpuvwssTnEw8lqvEXn5s1DnVxrRnhPAUT7F7Qva3l
1vmpZuCdJHCSYcOmn1dIEa1PhisTpOC1ColmFIAp5reYBPkR3RseJ9/5OwEtif9d
5bhmNkBmREYn4Nj/WrpxnFnJ28vPgUlvFaZvkX9jMfanUq6xhTM=
=Z6i2
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libtickit-widget-floatbox-perl
Source-Version: 0.06-1
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libtickit-widget-floatbox-perl package)

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


-BEGIN PGP SIGNED MESSAGE-

Bug#871563: Downgrading severity of manpages-fr-extra bug

[Dr. Tobias Quathamer]

control: severity -1 important

Hi,

I'm downgrading this bug to allow the NMU of manpages-fr-extra to
migrate to testing. The latest upload replaces the previous package with
a transitional dummy package which depends on manpages-fr and
manpages-fr-dev.

Those packages are now generated from the source package manpages-l10n,
which provides up-to-date translations for the French manpages.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Processed: Downgrading severity of manpages-fr-extra bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #871563 [manpages-fr-extra] manpages-fr-extra outdated
Severity set to 'important' from 'serious'

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

Bug#952103: marked as done (svnkit: FTBFS: [javac] /<>/svnkit-javahl16/src/main/java/org/apache/subversion/javahl/SVNClient.java:14: error: SVNClient is not abstract and does not over

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 19:24:57 +
with message-id 
and subject line Bug#952103: fixed in svnkit 1.8.14-4
has caused the Debian Bug report #952103,
regarding svnkit: FTBFS: [javac] 
/<>/svnkit-javahl16/src/main/java/org/apache/subversion/javahl/SVNClient.java:14:
 error: SVNClient is not abstract and does not override abstract method 
blame(String,Revision,Revision,Revision,boolean,boolean,DiffOptions,BlameRangeCallback,BlameLineCallback)
 in ISVNClient
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.)


-- 
952103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: svnkit
Version: 1.8.14-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> VERSION=$(dpkg-parsechangelog | grep Version: | cut -d' ' -f 2); \
> echo $VERSION | { \
>   IFS='.-+' read MAJOR MINOR MICRO DFSG DEBIAN; \
>   export MAJOR MINOR MICRO DEBIAN; \
> ant -f debian/build.xml -propertyfile debian/ant.properties; \
> };
> Buildfile: /<>/debian/build.xml
> 
> init-environment:
> 
> compile-library:
> [mkdir] Created dir: /<>/svnkit/bin
> [mkdir] Created dir: /<>/svnkit-cli/bin
> [mkdir] Created dir: /<>/svnkit-javahl16/bin
> [javac] /<>/debian/build.xml:20: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 1074 source files to /<>/svnkit/bin
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] 
> /<>/svnkit/src/main/java/org/tmatesoft/svn/core/internal/util/SVNPathUtil.java:58:
>  warning: non-varargs call of varargs method with inexact argument type for 
> last parameter;
> [javac] SVNErrorMessage err = 
> SVNErrorMessage.create(SVNErrorCode.FS_PATH_SYNTAX, "Invalid control 
> character ''{0}'' in path ''{1}''", new String[]{"0x" + 
> SVNFormatUtil.getHexNumberFromByte((byte) ch), path});
> [javac]   
>  ^
> [javac]   cast to Object for a varargs call
> [javac]   cast to Object[] for a non-varargs call and to suppress this 
> warning
> [javac] 
> /<>/svnkit/src/main/java/org/tmatesoft/svn/core/wc/admin/SVNAdminClient.java:1622:
>  warning: non-varargs call of varargs method with inexact argument type for 
> last parameter;
> [javac] SVNErrorMessage err = 
> SVNErrorMessage.create(SVNErrorCode.IO_ERROR, "Session is rooted at ''{0}'' 
> but the repos root is ''{1}''", new SVNURL[] {
> [javac]   
> ^
> [javac]   cast to Object for a varargs call
> [javac]   cast to Object[] for a non-varargs call and to suppress this 
> warning
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 3 warnings
> [javac] /<>/debian/build.xml:23: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 124 source files to /<>/svnkit-cli/bin
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 warning
> [javac] /<>/debian/build.xml:26: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 38 source files to /<>/svnkit-javahl16/bin
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] 
> /<>/svnkit-javahl16/src/main/java/org/apache/subversion/javahl/SVNClient.java:14:
>  error: SVNClient is not abstract and does not override abstract method 
> 

Bug#956385: marked as done (node-request: uses internet access during build)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 19:23:38 +
with message-id 
and subject line Bug#956385: fixed in node-request 2.88.1-4
has caused the Debian Bug report #956385,
regarding node-request: uses internet access during build
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.)


-- 
956385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-request
Version: 2.88.1-3
Severity: serious

Hello,
looks like the dh_auto_test process is trying to go on internet, and this is 
forbidden by policy.
I found this problem on Ubuntu builders, where the internet access is more 
strictly forbidden.


[...]
not ok 549 should be equal
  ---
operator: equal
expected: false
actual:   true
at: Request._callback (/<>/tests/test-localAddress.js:11:7)
stack: |-
  Error: should be equal
  at Test.assert [as _assert] (/usr/lib/nodejs/tape/lib/test.js:235:54)
  at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.equal (/usr/lib/nodejs/tape/lib/test.js:395:10)
  at Test.bound [as equal] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Request._callback 
(/<>/tests/test-localAddress.js:11:7)
  at self.callback (/<>/request.js:185:22)
  at Request.emit (events.js:198:13)
  at Request.onRequestError (/<>/request.js:881:8)
  at ClientRequest.emit (events.js:198:13)
  at Socket.socketErrorListener (_http_client.js:401:9)
  at Socket.emit (events.js:198:13)
  at emitErrorNT (internal/streams/destroy.js:91:8)
  at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
  at process._tickCallback (internal/process/next_tick.js:63:19)
  ...
ok 550 should be equal
# bind to local address
ok 551 should not be equal
ok 552 should be equal
# bind to local address on redirect
not ok 553 should be equal
  ---
operator: equal
expected: |-
  null
actual: |-
  { [Error: getaddrinfo ENOTFOUND google.com google.com:80] errno: 
'ENOTFOUND', code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'google.com', 
host: 'google.com', port: 80 }
at: Request._callback (/<>/tests/test-localAddress.js:45:7)
stack: |-
  Error: getaddrinfo ENOTFOUND google.com google.com:80
  at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
  ...
/<>/tests/test-localAddress.js:46
t.equal(res.request.localAddress, localIPS[0])
^

TypeError: Cannot read property 'request' of undefined
at Request._callback (/<>/tests/test-localAddress.js:46:17)
at self.callback (/<>/request.js:185:22)
at Request.emit (events.js:198:13)
at Request.onRequestError (/<>/request.js:881:8)
at ClientRequest.emit (events.js:198:13)
at Socket.socketErrorListener (_http_client.js:401:9)
at Socket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: node-request
Source-Version: 2.88.1-4
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-request package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Apr 2020 20:53:45 +0200
Source: node-request
Architecture: source
Version: 2.88.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 956385
Changes:
 node-request (2.88.1-4) unstable; urgency=medium
 .
   * Team upload
   * Disable tests that require network access (Closes: #956385)
Checksums-Sha1: 
 

Bug#956211: [Pkg-javascript-devel] Bug#956211: Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]

[Pirate Praveen]

Control: reassign -1 gitlab
Control: tags -1 -wontfix

On Sat, Apr 11, 2020 at 12:32 am, Pirate Praveen 
 wrote:



On Fri, Apr 10, 2020 at 8:58 pm, Jérémy Lal  
wrote:



Le ven. 10 avr. 2020 à 20:50, Pirate Praveen 
 a écrit :



 On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal  
wrote:

 > Package: nodejs
 > Version: 10.19.0~dfsg-3
 > Followup-For: Bug #956211
 >
 > Pirate, i repeat, please try
 >
 > webpack --max-old-space-size=4096
 >
 > Or even a higher value. If it works, it's up to gitlab to use 
that

 > flag.
 >

 root@gitlab-buster:/usr/share/gitlab# runuser -u ${gitlab_user} --
sh
 -c 'webpack --max-old-space-size=8192 --config 
config/webpack.config.js'


 I tried 4096, 6144, 8192, 16384 and all failed. How much higher 
should

 I go?


Not further :)
However then maybe that flag has no effect.
Another way to pass the flag is by setting the environment variable:
NODE_OPTIONS="–max-old-space-size=2048"
Then again, runuser need to be told to handle this correctly.



I will try this, probably tomorrow.



runuser -u ${gitlab_user} -- sh -c 
'NODE_OPTIONS="--max-old-space-size=2048" webpack 
--max-old-space-size=16384 --config config/webpack.config.js'


This worked. Thanks a lot.



 > Nodejs applications using high memory must use that kind of
 > workaround.

 I was also exploring if excluding system libraries from 
babel-loader

 reduces memory footprint.


Yep, i saw that.
Can you give me a quick way to reproduce the OOM error ?

If you are okay setting up gitlab from experimental on an lxc or vm 
then instructions are here https://wiki.debian.org/gitlab


Else I can set it up on a test VPS and give you access, possibly 
tomorrow.



Jérémy


--
Pkg-javascript-devel mailing list
pkg-javascript-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Processed: Re: [Pkg-javascript-devel] Bug#956211: Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 gitlab
Bug #956211 [nodejs] nodejs 10 segfaults when running webpack on gitlab 12.9.2 
- FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - 
JavaScript heap out of memory
Bug reassigned from package 'nodejs' to 'gitlab'.
No longer marked as found in versions nodejs/10.15.2~dfsg-2 and 
nodejs/10.19.0~dfsg-3.
Ignoring request to alter fixed versions of bug #956211 to the same values 
previously set
> tags -1 -wontfix
Bug #956211 [gitlab] nodejs 10 segfaults when running webpack on gitlab 12.9.2 
- FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - 
JavaScript heap out of memory
Removed tag(s) wontfix.

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

Processed: severity of 955019 is grave, severity of 955020 is grave, severity of 951537 is grave

[Debian Bug Tracking System]

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

> # rasing severity to RC as package orphaned and should not be included with 
> these open security fixes for bullseye
> severity 955019 grave
Bug #955019 [src:php-horde-trean] php-horde-trean: CVE-2020-8865
Severity set to 'grave' from 'important'
> severity 955020 grave
Bug #955020 [src:php-horde-form] php-horde-form: CVE-2020-8866
Severity set to 'grave' from 'important'
> severity 951537 grave
Bug #951537 [src:php-horde-data] php-horde-data: CVE-2020-8518
Ignoring request to change severity of Bug 951537 to the same value.
> thanks
Stopping processing here.

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

Bug#956211: [Pkg-javascript-devel] Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]

[Pirate Praveen]

On Fri, Apr 10, 2020 at 8:58 pm, Jérémy Lal  wrote:



Le ven. 10 avr. 2020 à 20:50, Pirate Praveen 
 a écrit :



 On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal  
wrote:

 > Package: nodejs
 > Version: 10.19.0~dfsg-3
 > Followup-For: Bug #956211
 >
 > Pirate, i repeat, please try
 >
 > webpack --max-old-space-size=4096
 >
 > Or even a higher value. If it works, it's up to gitlab to use that
 > flag.
 >

 root@gitlab-buster:/usr/share/gitlab# runuser -u ${gitlab_user} -- 
sh
 -c 'webpack --max-old-space-size=8192 --config 
config/webpack.config.js'


 I tried 4096, 6144, 8192, 16384 and all failed. How much higher 
should

 I go?


Not further :)
However then maybe that flag has no effect.
Another way to pass the flag is by setting the environment variable:
NODE_OPTIONS="–max-old-space-size=2048"
Then again, runuser need to be told to handle this correctly.



I will try this, probably tomorrow.



 > Nodejs applications using high memory must use that kind of
 > workaround.

 I was also exploring if excluding system libraries from babel-loader
 reduces memory footprint.


Yep, i saw that.
Can you give me a quick way to reproduce the OOM error ?

If you are okay setting up gitlab from experimental on an lxc or vm 
then instructions are here https://wiki.debian.org/gitlab


Else I can set it up on a test VPS and give you access, possibly 
tomorrow.



Jérémy

Bug#956211: [Pkg-javascript-devel] Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]

[Jérémy Lal]

Le ven. 10 avr. 2020 à 20:50, Pirate Praveen  a
écrit :

>
>
> On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal  wrote:
> > Package: nodejs
> > Version: 10.19.0~dfsg-3
> > Followup-For: Bug #956211
> >
> > Pirate, i repeat, please try
> >
> > webpack --max-old-space-size=4096
> >
> > Or even a higher value. If it works, it's up to gitlab to use that
> > flag.
> >
>
> root@gitlab-buster:/usr/share/gitlab# runuser -u ${gitlab_user} -- sh
> -c 'webpack --max-old-space-size=8192 --config config/webpack.config.js'
>
> I tried 4096, 6144, 8192, 16384 and all failed. How much higher should
> I go?
>

Not further :)
However then maybe that flag has no effect.
Another way to pass the flag is by setting the environment variable:
NODE_OPTIONS="–max-old-space-size=2048"
Then again, runuser need to be told to handle this correctly.


>
> > Nodejs applications using high memory must use that kind of
> > workaround.
>
> I was also exploring if excluding system libraries from babel-loader
> reduces memory footprint.


Yep, i saw that.
Can you give me a quick way to reproduce the OOM error ?

Jérémy

Processed: Bug#956385 marked as pending in node-request

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #956385 [src:node-request] node-request: uses internet access during build
Added tag(s) pending.

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

Bug#956385: marked as pending in node-request

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #956385 in node-request 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-request/-/commit/06e91201f88d4d6e183ef710aa238ac7138f2fd0


Disable tests that require network access

Closes: #956385


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/956385

Processed: Bug#952103 marked as pending in svnkit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952103 [src:svnkit] svnkit: FTBFS: [javac] 
/<>/svnkit-javahl16/src/main/java/org/apache/subversion/javahl/SVNClient.java:14:
 error: SVNClient is not abstract and does not override abstract method 
blame(String,Revision,Revision,Revision,boolean,boolean,DiffOptions,BlameRangeCallback,BlameLineCallback)
 in ISVNClient
Added tag(s) pending.

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

Bug#952103: marked as pending in svnkit

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #952103 in svnkit 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/java-team/svnkit/-/commit/b077a4f77e6f7186e332ce20b2f9585666d77e5a


Import Debian changes 1.8.14-4

svnkit (1.8.14-4) unstable; urgency=medium

  * Team upload.
  * Fix FTBFS. (Closes: #952103)
  * Update Standards-Version to 4.5.0
  * Use debhelper-compat.
- Update compat level to 12.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952103

Bug#956211: [Pkg-javascript-devel] Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]

[Pirate Praveen]

On Fri, Apr 10, 2020 at 7:35 pm, Jérémy Lal  wrote:

Package: nodejs
Version: 10.19.0~dfsg-3
Followup-For: Bug #956211

Pirate, i repeat, please try

webpack --max-old-space-size=4096

Or even a higher value. If it works, it's up to gitlab to use that 
flag.




root@gitlab-buster:/usr/share/gitlab# runuser -u ${gitlab_user} -- sh 
-c 'webpack --max-old-space-size=8192 --config config/webpack.config.js'


I tried 4096, 6144, 8192, 16384 and all failed. How much higher should 
I go?


Nodejs applications using high memory must use that kind of 
workaround.


I was also exploring if excluding system libraries from babel-loader 
reduces memory footprint.

Bug#956405: ruby-enumerable-statistics: FTBFS on amd64/unstable: find: [..] No such file or directory

[Chris Lamb]

Source: ruby-enumerable-statistics
Version: 2.0.1+dfsg-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Tags: fbtfs

Dear Maintainer,

ruby-enumerable-statistics fails to build from source in unstable/amd64:

  […]

 dh_compress -X.rb -O--buildsystem=ruby
 debian/rules override_dh_fixperms
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20200410190019.WRLDvzI39v.ags.ruby-enumerable-statistics/ruby-enumerable-statistics-2.0.1+dfsg'
  dh_fixperms
  find 
debian/ruby-enumerable-statistics/usr/lib/*/rubygems-integration/*/gems/enumerable-statistics-*/yard/templates/
 -type f |xargs chmod -x
  find: 
'debian/ruby-enumerable-statistics/usr/lib/*/rubygems-integration/*/gems/enumerable-statistics-*/yard/templates/':
 No such file or directory
  chmod: missing operand
  Try 'chmod --help' for more information.
  make[1]: *** [debian/rules:16: override_dh_fixperms] Error 123
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20200410190019.WRLDvzI39v.ags.ruby-enumerable-statistics/ruby-enumerable-statistics-2.0.1+dfsg'
  make: *** [debian/rules:7: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ruby-enumerable-statistics.2.0.1+dfsg-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#951224: marked as done (securefs: autopkgtest regression: libutf8proc.so.2: cannot open shared object file: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 17:50:19 +
with message-id 
and subject line Bug#951224: fixed in securefs 0.9.0+ds-1.1
has caused the Debian Bug report #951224,
regarding securefs: autopkgtest regression: libutf8proc.so.2: cannot open 
shared object file: 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.)


-- 
951224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: securefs
Version: 0.9.0+ds-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of securefs the autopkgtest of securefs fails in
testing when that autopkgtest is run with the binary packages of
securefs from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
securefs   from testing0.9.0+ds-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/securefs/4264369/log.gz

autopkgtest [05:49:56]: test command2: cd obj-x86_64-linux-gnu &&
./securefs_test
autopkgtest [05:49:56]: test command2: [---
./securefs_test: error while loading shared libraries: libutf8proc.so.2:
cannot open shared object file: No such file or directory
autopkgtest [05:49:56]: test command2: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: securefs
Source-Version: 0.9.0+ds-1.1
Done: Yanhao Mo 

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

Debian distribution maintenance software
pp.
Yanhao Mo  (supplier of updated securefs 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: Sat, 11 Apr 2020 01:10:15 +0800
Source: securefs
Architecture: source
Version: 0.9.0+ds-1.1
Distribution: unstable
Urgency: medium
Maintainer: Yanhao Mo 
Changed-By: Yanhao Mo 
Closes: 951224
Changes:
 securefs (0.9.0+ds-1.1) unstable; urgency=medium
 .
   * Add test dependency libutf8proc2 (Closes: #951224).
Checksums-Sha1:
 6e9fce77901a08a7724270180d582f761ff02142 2087 securefs_0.9.0+ds-1.1.dsc
 2b31f8f3165937bf0dba7901693d7f304e7bb7cf 5632 
securefs_0.9.0+ds-1.1.debian.tar.xz
 f0a7d06f9e660145135ddcd803db11587756927d 7462 
securefs_0.9.0+ds-1.1_amd64.buildinfo
Checksums-Sha256:
 cc0f7aebd2a53daf45b57014380c854ae69a7b95d472993ad978af1a0e714004 2087 
securefs_0.9.0+ds-1.1.dsc
 007c317f665f18dd50fcbf6479744eae4eb87151bdb42437c7ebf51676897f8a 5632 
securefs_0.9.0+ds-1.1.debian.tar.xz
 c7426394e478bf9a707fe472e84439a16887800e58b15236de4cb666568c50c7 7462 
securefs_0.9.0+ds-1.1_amd64.buildinfo
Files:
 ba5569f0299b31ba6344f1be97f17736 2087 utils optional securefs_0.9.0+ds-1.1.dsc
 b95edc54436592edf4922070c6e80ed3 5632 utils optional 
securefs_0.9.0+ds-1.1.debian.tar.xz
 88e27b5532cd1148a07ad8b526183b2c 7462 utils optional 
securefs_0.9.0+ds-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEb9bJQfCTGv6uM2+ujv2XAviIsq4FAl6QrC4THHlhbmhhb2Nz
QGdtYWlsLmNvbQAKCRCO/ZcC+IiyrrTgEACyIDl1MyHpXv9PkWtCROl/+f5KsgQM
953JrPO2GXxtS0ZLpj/7KbvX8dxnDSucFhqA3uA5rVy0bkmTO32e7nOz3K3xJS51
Xxex7v3s357dZbZPbAo6rGbiOP/svOLOCtcQQA9CLc8/l9quE8MI9aF9zMRC/c64
sM1rgkA6ADGaRRvlwUem7KzGNWXZ/ae14sNOuhwsFdK/Gecxt397Zdrhc1fUWGhW
XLJximIVmS45V7Ik4/UhcrQZ+tkmbL/hEtnfTCn4G5GL0YPSztAHXqMQlXNzcLeO
M488sZ2JvYjxiIq5FcOdjB8R20AMqtcNepm/4zPBchkNk4zTNOmXf0LWX2TlAll3
jhGFYlDb583Z3/7SErxRVZb62SvijoaUYlwn3eSrvxXRCvzsEF1zW+6B9g9xFyP/
knfHAY9O5rOuCej9rjiCSY3TALlZnzo9BSv4tUbH/WNmJ1nVTpkXoapC6XleYt+9

Processed: Re: [Pkg-javascript-devel] Bug#956211: nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap

[Debian Bug Tracking System]

Processing control commands:

> tag -1 help
Bug #956211 [nodejs] nodejs 10 segfaults when running webpack on gitlab 12.9.2 
- FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - 
JavaScript heap out of memory
Added tag(s) help.

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

Bug#956211: [Pkg-javascript-devel] Bug#956211: nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap ou

[Pirate Praveen]

Control: tag -1 help

On Wed, Apr 8, 2020 at 4:08 pm, Jérémy Lal  wrote:

Tags: wontfix

Le mer. 8 avr. 2020 à 15:48, Pirate Praveen 
 a écrit :

Package: nodejs
 Version: 10.19.0~dfsg-3
 Severity: grave
 Control: notfound -1 12.13.1~dfsg-1


 nodejs 10 crashed (retried again) and on the same machine nodejs 12
 worked.
 This has been working upto gitlab 12.8.8 and the failure appeared 
when
 trying to update to 12.9.2 (just installing gitlab from 
experimental in

 an lxc container).


This is a known issue with nodejs and high memory usage, which happen
to be better with nodejs 12 (but only because gitlab assets 
compilation does

not go way above 2GB usage).

There is no way to fix it in general: you will always find use cases 
that make

nodejs crash as soon as it is using GB of heap memory space.

Any nodejs < 14 version is affected (because who knows, v8 might make 
it
possible for node to fix it in nodejs 14) but not in the same way 
(some fail at 1.4GB,

others at 2GB of heap space usage).

You can try running it with this flag:
webpack --max-old-space-size=4096

Note also that using a high value by default is not a good solution 
either.




Thanks for the answer. It may be possible to reduce memory usage by 
excluding system libraries (in /usr/lib/nodejs, /usr/share/nodejs, 
/usr/share/javascript) during transpiling (babel loader). Can someone 
help me with the correct regex for doing it? All examples on the 
internet shows excluding node_modules only.


Currently it is patched to exclude core-js from babel-loader,

test: /\.js$/,
exclude: [ path =>
  
/node_modules\/(?!tributejs)|node_modules|vendor[\\/]assets/.test(path) 
&

&
  !/\.vue\.js/.test(path),
/\bcore-js\b/,
/\bwebpack\/buildin\b/
],
loader: 'babel-loader',

I tried adding '/usr/share/nodejs' as string, 
path.resolve('/usr/share/nodejs') but it did not seem to work.



Jérémy

Bug#950221: salsa: Please transfer natsort from debian to python-team/modules

[Scott Talbert]

On Sat, 14 Mar 2020, Adrian Bunk wrote:


Hi,

please transfer natsort from debian to python-team/modules,
see #950221 for background.


Hello again Salsa admins.  Can you please transfer natsort to 
python-team/modules?


I would like to get natsort fixed ASAP.

Thanks,
Scott

Processed: retitle 956400 to qpdf: FTBFS on multiple 32-bit architectures, needs libatomic

[Debian Bug Tracking System]

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

> retitle 956400 qpdf: FTBFS on multiple 32-bit architectures, needs libatomic
Bug #956400 [src:qpdf] pdf: FTBFS on multiple 32-bit architectures, needs 
libatomic
Changed Bug title to 'qpdf: FTBFS on multiple 32-bit architectures, needs 
libatomic' from 'pdf: FTBFS on multiple 32-bit architectures, needs libatomic'.
> thanks
Stopping processing here.

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

Bug#956211: [Re: nodejs 10 segfaults when running webpack on gitlab 12.9.2]

[Jérémy Lal]

Package: nodejs
Version: 10.19.0~dfsg-3
Followup-For: Bug #956211

Pirate, i repeat, please try

webpack --max-old-space-size=4096

Or even a higher value. If it works, it's up to gitlab to use that flag.

Nodejs applications using high memory must use that kind of workaround.

Jérémy.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (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=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nodejs depends on:
ii  libc6  2.30-4
ii  libnode64  10.19.0~dfsg-3

Versions of packages nodejs recommends:
ii  ca-certificates  20190110
ii  nodejs-doc   10.19.0~dfsg-3

Versions of packages nodejs suggests:
ii  npm  6.14.4+ds-1

-- no debconf information

Processed: retitle 956400 to pdf: FTBFS on multiple 32-bit architectures, needs libatomic

[Debian Bug Tracking System]

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

> retitle 956400 pdf: FTBFS on multiple 32-bit architectures, needs libatomic
Bug #956400 [src:qpdf] pdf: FTBFS on multiple 32-bit architectures, needs 
libatomic
Ignoring request to change the title of bug#956400 to the same title
> thanks
Stopping processing here.

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

Processed: plans for uploading a newer icu to unstable

[Debian Bug Tracking System]

Processing control commands:

> block 956211 by -1
Bug #956211 [nodejs] nodejs 10 segfaults when running webpack on gitlab 12.9.2 
- FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - 
JavaScript heap out of memory
956211 was not blocked by any bugs.
956211 was not blocking any bugs.
Added blocking bug(s) of 956211: 956402

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

Bug#954637: marked as done (ivtools: FTBFS: os_stropts.h:56:17: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 18:18:17 +0100
with message-id <20200410171817.o5famn57ja5hyb4v@debian>
and subject line Re: ivtools: FTBFS: os_stropts.h:56:17: fatal error: 
stropts.h: No such file or directory
has caused the Debian Bug report #954637,
regarding ivtools: FTBFS: os_stropts.h:56:17: 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.)


-- 
954637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ivtools
Version: 1.2.11a2-4
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):
> /bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
> -Dcplusplus_2_1 -Div2_6_incompatible -I./src/include -D__ACE_INLINE__ 
> -DHAVE_ACE -Div2_6_compatible -I./src -I./src/include/IV-2_6 -I./src/include 
> -I./src/include/ivstd -DCLIPPOLY -I/usr/include/clippoly -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wno-write-strings -Wno-deprecated -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wall 
> -Wno-narrowing -Wno-unused-variable -Wno-char-subscripts 
> -Wno-maybe-uninitialized -Wno-sign-compare -c -o 
> src/OverlayUnidraw/libOverlayUnidrawPART2_la-aceimport.lo `test -f 
> 'src/OverlayUnidraw/aceimport.cc' || echo './'`src/OverlayUnidraw/aceimport.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Dcplusplus_2_1 
> -Div2_6_incompatible -I./src/include -D__ACE_INLINE__ -DHAVE_ACE 
> -Div2_6_compatible -I./src -I./src/include/IV-2_6 -I./src/include 
> -I./src/include/ivstd -DCLIPPOLY -I/usr/include/clippoly -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wno-write-strings -Wno-deprecated -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wall 
> -Wno-narrowing -Wno-unused-variable -Wno-char-subscripts 
> -Wno-maybe-uninitialized -Wno-sign-compare -c src/OverlayUnidraw/aceimport.cc 
>  -fPIC -DPIC -o src/OverlayUnidraw/.libs/libOverlayUnidrawPART2_la-aceimport.o
> In file included from /usr/include/ace/OS_NS_stropts.h:30,
>  from /usr/include/ace/OS_NS_sys_socket.h:28,
>  from /usr/include/ace/ACE.inl:5,
>  from /usr/include/ace/ACE.h:887,
>  from /usr/include/ace/String_Base.cpp:4,
>  from /usr/include/ace/String_Base.h:880,
>  from /usr/include/ace/SString.h:21,
>  from /usr/include/ace/DLL.h:23,
>  from /usr/include/ace/Service_Object.h:23,
>  from /usr/include/ace/Acceptor.h:16,
>  from ./src/OverlayUnidraw/aceimport.h:31,
>  from src/OverlayUnidraw/aceimport.cc:30:
> /usr/include/ace/os_include/os_stropts.h:56:17: fatal error: stropts.h: No 
> such file or directory
>56 | #  include /**/ 
>   | ^~~
> compilation terminated.
> make[3]: *** [Makefile:7829: 
> src/OverlayUnidraw/libOverlayUnidrawPART2_la-aceimport.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/ivtools_1.2.11a2-4_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 ---
This was caused by "ace", and is now fixed with "ace_6.4.5+dfsg-1.1".

+--+
| Summary  |
+--+

Build Architecture: amd64
Build Type: full
Build-Space: 484160
Build-Time: 145
Distribution: unstable
Host Architecture: amd64
Install-Time: 25
Job: ivtools
Machine Architecture: amd64
Package: ivtools
Package-Time: 175
Source-Version: 1.2.11a2-4
Space: 484160
Status: successful
Version: 1.2.11a2-4


So, marking it as done. Please feel free to reopen if you think it 

Bug#956400: pdf: FTBFS on multiple 32-bit architectures, needs libatomic

[John Paul Adrian Glaubitz]

Source: qpdf
Version: 10.0.1-1
Severity: serious
Justification: ftbfs
User: debian-...@lists.debian.org
Usertags: armel

Hi!

qpdf fails to build from source on multiple architectures due to
missing symbols from libatomic [1]:

/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[1]: *** [libtests/build.mk:52: libtests/build/aes] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: *** [libtests/build.mk:52: libtests/build/bits] Error 1
make[1]: *** [zlib-flate/build.mk:22: zlib-flate/build/zlib-flate] Error 1
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[1]: *** [libtests/build.mk:52: libtests/build/buffer] Error 1
/usr/bin/ld: /<>/libqpdf/build/.libs/libqpdf.so: undefined 
reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status

This is a known issue with gcc [2] and can be fixed by linking against
libatomic, similar to apt-cacher-ng [3] and [4]. Please apply such
a fix for armel, mipsel, m68k, powerpc and sh4.

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=qpdf=armel=10.0.1-1=1586486160=0
>  
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862002
> [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859689

Bug#936273: marked as done (capstone: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 17:03:35 +
with message-id 
and subject line Bug#936273: fixed in capstone 4.0.1+really+3.0.5-2
has caused the Debian Bug report #936273,
regarding capstone: 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.)


-- 
936273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:capstone
Version: 4.0.1+really+3.0.5-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:capstone

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: capstone
Source-Version: 4.0.1+really+3.0.5-2
Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?= 

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated capstone 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Apr 2020 18:30:01 +0200
Source: capstone
Architecture: source
Version: 4.0.1+really+3.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Raphaël Hertzog 
Closes: 936273
Changes:
 capstone (4.0.1+really+3.0.5-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Samuel Henrique ]
   * Add salsa-ci.yml
   * Configure git-buildpackage for Debian pkg-security-tools
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Use secure URI in Homepage field.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #936273
 .
   [ Raphaël Hertzog ]
   * Drop non-existing file in debian/copyright
   * Avoid a 

Processed: reproduced the error on buster (backports/fasttrack) as well

[Debian Bug Tracking System]

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

> found 956211 10.15.2~dfsg-2
Bug #956211 [nodejs] nodejs 10 segfaults when running webpack on gitlab 12.9.2 
- FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - 
JavaScript heap out of memory
Marked as found in versions nodejs/10.15.2~dfsg-2.
> thanks
Stopping processing here.

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

Bug#936273: marked as pending in capstone

[Raphaël Hertzog]

Control: tag -1 pending

Hello,

Bug #936273 in capstone 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/pkg-security-team/capstone/-/commit/905a53a68b64173c102754c8aa5015004b4ea8b3


Import Debian changes 4.0.1+really+3.0.5-1.1

capstone (4.0.1+really+3.0.5-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Drop python2 support; Closes: #936273


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936273

Processed: Bug#936273 marked as pending in capstone

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#938595: marked as done (sugar-toolkit-gtk3: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 16:35:52 +
with message-id 
and subject line Bug#938595: fixed in sugar-toolkit-gtk3 0.116-6
has caused the Debian Bug report #938595,
regarding sugar-toolkit-gtk3: 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.)


-- 
938595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sugar-toolkit-gtk3
Version: 0.112-3
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:sugar-toolkit-gtk3

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: sugar-toolkit-gtk3
Source-Version: 0.116-6
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
sugar-toolkit-gtk3, 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 sugar-toolkit-gtk3 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: Fri, 10 Apr 2020 12:18:22 -0400
Source: sugar-toolkit-gtk3
Architecture: source
Version: 0.116-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Sugar Team 
Changed-By: Sandro Tosi 
Closes: 938595
Changes:
 sugar-toolkit-gtk3 (0.116-6) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938595
Checksums-Sha1:
 614dc1b880c6992456923069580e7adb09d62586 2654 sugar-toolkit-gtk3_0.116-6.dsc
 0d5ad310c286bb70fb9cc62f70b4c4a890f39291 20232 
sugar-toolkit-gtk3_0.116-6.debian.tar.xz
 5eafc97cee163710bd2b3861b767e28b31a29c3c 14695 
sugar-toolkit-gtk3_0.116-6_source.buildinfo
Checksums-Sha256:
 8adc58de5b405187e005f14b3484d8df7f0e5383f5b56d465c4e0c648fe24b31 2654 
sugar-toolkit-gtk3_0.116-6.dsc
 0332fd8bfa1796a0f222db8a3b00acc507abefcc3afd6a063b2eeffaa1aa5c8b 20232 
sugar-toolkit-gtk3_0.116-6.debian.tar.xz
 

Bug#942469: marked as done (r-cran-rmarkdown: directory to symlink conversion not correctly handled on upgrade)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 16:35:38 +
with message-id 
and subject line Bug#942469: fixed in r-cran-rmarkdown 2.1+dfsg-2
has caused the Debian Bug report #942469,
regarding r-cran-rmarkdown: directory to symlink conversion not correctly 
handled on upgrade
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.)


-- 
942469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-rmarkdown
Version: 1.16+dfsg-1
Severity: normal

  Hi,

  While trying to reproduce a bug in another package (r-cran-dt, I will
submit it after this one), I notice an error while pandoc is invoked:
[...]
/usr/bin/pandoc +RTS -K512m -RTS small_test.utf8.md --to html4 --from 
markdown+autolink_bare_uris+tex_math_single_backslash+smart --output 
small_test.html --email-obfuscation none --self-contained --standalone 
--section-divs --template /usr/lib/R/site-library/rmarkdown/rmd/h/default.html 
--highlight-style tango --css style.css --variable 'theme:cerulean' 
--include-in-header /tmp/Rtmpo7H2Mq/rmarkdown-str53cc33e4db8.html --mathjax 
--variable 
'mathjax-url:https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML'
 --lua-filter /usr/lib/R/site-library/rmarkdown/rmd/lua/pagebreak.lua 
--lua-filter /usr/lib/R/site-library/rmarkdown/rmd/lua/latex-div.lua 
pandoc: 
/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/css/../fonts/glyphicons-halflings-regular.eot:
 openBinaryFile: does not exist (No such file or directory)
Erreur : pandoc document conversion failed with error 1
Exécution arrêtée

Looking with apt-file, I see that 
/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/css/../fonts/glyphicons-halflings-regular.eot
was provided by r-cran-rmarkdown.
Looking at the git history of r-cran-rmarkdown, I see that in 7bd53b7c34
these files where removed and replaced by a symlink. However,
for file in fonts/ subdir, this is the whole subdir that is
symlinked and not the files themselves.

dpkg do not correctly handle dir to symlink when upgrading
(due to the fact that the sysadmin can decide to replace
dir by symlinks to manage its disks if I remember).
So support in preinst/postinst is required.

And indeed, on my machine, I can see that
/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/fonts
is still a (empty) real directory :
$ ls -ld /usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/fonts
drwxr-xr-x 2 root root 4096 juil.  9 15:20 
/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/fonts

I fix the bug by removing the directory and reinstalling the
package :
$ sudo rmdir /usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/fonts
$ sudo apt install --reinstall r-cran-rmarkdown
[...]
Dépaquetage de r-cran-rmarkdown (1.16+dfsg-1) sur (1.16+dfsg-1) ...
[...]
$ ls -ld /usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/fonts
lrwxrwxrwx 1 root root 53 oct.   7 15:00 
/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/fonts -> 
../../../../../../../share/javascript/bootstrap/fonts

  So, for people upgrading the package, you will have to
fix this dir to symlink conversion in a pre/post-inst script.

  Regards,
Vincent


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

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

Versions of packages r-cran-rmarkdown depends on:
ii  fonts-font-awesome   5.0.10+really4.7.0~dfsg-1
ii  libjs-bootstrap  3.4.1+dfsg-1
ii  libjs-highlight.js   9.12.0+dfsg1-4
ii  libjs-jquery 3.3.1~dfsg-3
ii  libjs-jquery-ui  1.12.1+dfsg-5
ii  libjs-modernizr  2.6.2+ds1-3
ii  libjs-prettify   2015.12.04+dfsg-1.1
ii  pandoc   2.5-2+b1
ii  r-base-core [r-api-3.5]  3.6.1-6
ii  r-cran-base64enc 0.1-3-2
ii  r-cran-evaluate  0.14-1
ii  r-cran-htmltools 0.4.0-1
ii  r-cran-jsonlite  1.6+dfsg-1
ii  r-cran-knitr 1.25+dfsg-1
ii  r-cran-mime  0.7-1
ii  r-cran-shiny 1.3.2+dfsg-1
ii  r-cran-stringr   1.4.0-1
ii  r-cran-tinytex   0.16-1
ii  r-cran-xfun  0.10-1
ii  r-cran-yaml  2.2.0-1

Versions of packages r-cran-rmarkdown recommends:

Bug#956393: rust-unicode-width: uninstallable featureset packages.

[peter green]

Source: rust-unicode-width
Version: 0.1.7-1
Severity: serious

librust-unicode-width+std-dev and librust-unicode-width+rustc-dep-of-std-dev 
are not installable as they depend on 
librust-rustc-std-workspace-std-1+default-dev which does not seem to exist in 
debian.

This is blocking the rust-unicode-width source package from migrating to 
testing, which in turn is holding up rust-cbindgen from getting back into 
testing.

googling seems to suggest that "rustc-std-workspace-std" is a "hack for the 
compilers own build system" and not something intended for general use.

Should these featureset packages simply be dropped?

Processed: bug 938432 is forwarded to https://github.com/rigred/sandsifter/issues/10

[Debian Bug Tracking System]

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

> forwarded 938432 https://github.com/rigred/sandsifter/issues/10
Bug #938432 [src:sandsifter] sandsifter: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 
'https://github.com/rigred/sandsifter/issues/10'.
> thanks
Stopping processing here.

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

Bug#955997: rust-libc: autopkgtest failure.

[peter green]

notfound 955997 0.22-6-1
found 955997 0.2.66-1
found 955997 0.2.68-1
thanks

The autopkgtest is still failing with rust-libc 0.2.68-1 and rustc 1.42-1

Is it possible to enable/disable (or make non-fatal) autopkgtests on a per-featureset 
basis? if so should the test for the "dep-of-std" featureset be disabled/made 
not fatal so we can get this package (and it's reverse dependencies) back into testing?

Processed: re: rust-libc: autopkgtest failure.

[Debian Bug Tracking System]

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

> notfound 955997 0.22-6-1
Bug #955997 [rust-libc] rust-libc: autopkgtest failure.
There is no source info for the package 'rust-libc' at version '0.22-6-1' with 
architecture ''
Unable to make a source version for version '0.22-6-1'
No longer marked as found in versions 0.22-6-1.
> found 955997 0.2.66-1
Bug #955997 [rust-libc] rust-libc: autopkgtest failure.
There is no source info for the package 'rust-libc' at version '0.2.66-1' with 
architecture ''
Unable to make a source version for version '0.2.66-1'
Marked as found in versions 0.2.66-1.
> found 955997 0.2.68-1
Bug #955997 [rust-libc] rust-libc: autopkgtest failure.
There is no source info for the package 'rust-libc' at version '0.2.68-1' with 
architecture ''
Unable to make a source version for version '0.2.68-1'
Marked as found in versions 0.2.68-1.
> thanks
Stopping processing here.

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

Bug#953487: fixed in runescape 0.7-1

[Carlos Donizete Froes]

Hi Markus,

I hope everything is fine with you and your family.

> I had uploaded the new version of runescape to fix bug 953487 because
> you stated in
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953487#25
> 
> that the package has been whitelisted. Apparently this is not the case
> hence I am writing to non-f...@buildd.debian.org again and I kindly ask
> that runescape is whitelisted for autobuilding. The package is basically
> a script and the license allows autobuilding.

I am grateful that you uploaded this latest version of runescape, but I didn't
quite understand what happened in those discussions in the posted messages.

I will create a new icon and add a warning when starting the script, as
mentioned in the message https://bugs.debian.org/953487#54

I want to thank Stephen for offering help in solving the problem of validating
the downloaded JAR file, where I don't know how I do it at the moment.

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀  2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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

Processed: Re: ldns: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #936832 [src:ldns] ldns: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#936832: ldns: Python2 removal in sid/bullseye

[Santiago Ruano Rincón]

Control: tags -1 + pending

On Fri, 30 Aug 2019 07:22:47 + Matthias Klose  wrote:
> Package: src:ldns
> Version: 1.7.0-4
> 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
…

I've prepared the required changes to drop the python-ldns package in
this branch
https://salsa.debian.org/dns-team/ldns/-/tree/936832-stop-building-python-ldns
and the corresponding MR:
https://salsa.debian.org/dns-team/ldns/-/merge_requests/1

Unless Ondřej (or someone else) objects, I will apply them along with
the package for the latest upstream release (1.7.1).

Cheers,

 -- Santiago


signature.asc
Description: PGP signature

Bug#956159: Package depends on python-glade2 python-gtk2, which are no longer in sid

[Vincent Lefevre]

On 2020-04-08 06:34:18 +0800, 積丹尼 Dan Jacobson wrote:
> Package: wicd-gtk
> Severity: critical
> Version: 1.7.4+tb2-6
> 
> Package depends on python-glade2 python-gtk2, which are no longer in sid.

I suppose that this is related to bug 885140.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885140

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

Bug#956385: node-request: uses internet access during build

[Gianfranco Costamagna]

Source: node-request
Version: 2.88.1-3
Severity: serious

Hello,
looks like the dh_auto_test process is trying to go on internet, and this is 
forbidden by policy.
I found this problem on Ubuntu builders, where the internet access is more 
strictly forbidden.


[...]
not ok 549 should be equal
  ---
operator: equal
expected: false
actual:   true
at: Request._callback (/<>/tests/test-localAddress.js:11:7)
stack: |-
  Error: should be equal
  at Test.assert [as _assert] (/usr/lib/nodejs/tape/lib/test.js:235:54)
  at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.equal (/usr/lib/nodejs/tape/lib/test.js:395:10)
  at Test.bound [as equal] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Request._callback 
(/<>/tests/test-localAddress.js:11:7)
  at self.callback (/<>/request.js:185:22)
  at Request.emit (events.js:198:13)
  at Request.onRequestError (/<>/request.js:881:8)
  at ClientRequest.emit (events.js:198:13)
  at Socket.socketErrorListener (_http_client.js:401:9)
  at Socket.emit (events.js:198:13)
  at emitErrorNT (internal/streams/destroy.js:91:8)
  at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
  at process._tickCallback (internal/process/next_tick.js:63:19)
  ...
ok 550 should be equal
# bind to local address
ok 551 should not be equal
ok 552 should be equal
# bind to local address on redirect
not ok 553 should be equal
  ---
operator: equal
expected: |-
  null
actual: |-
  { [Error: getaddrinfo ENOTFOUND google.com google.com:80] errno: 
'ENOTFOUND', code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'google.com', 
host: 'google.com', port: 80 }
at: Request._callback (/<>/tests/test-localAddress.js:45:7)
stack: |-
  Error: getaddrinfo ENOTFOUND google.com google.com:80
  at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
  ...
/<>/tests/test-localAddress.js:46
t.equal(res.request.localAddress, localIPS[0])
^

TypeError: Cannot read property 'request' of undefined
at Request._callback (/<>/tests/test-localAddress.js:46:17)
at self.callback (/<>/request.js:185:22)
at Request.emit (events.js:198:13)
at Request.onRequestError (/<>/request.js:881:8)
at ClientRequest.emit (events.js:198:13)
at Socket.socketErrorListener (_http_client.js:401:9)
at Socket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Processed: genwqe-user: diff for NMU version 4.0.18-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 954611 + patch
Bug #954611 [src:genwqe-user] genwqe-user: FTBFS: hw_defs.h:36:21: error: 
static declaration of ‘gettid’ follows non-static declaration
Added tag(s) patch.
> tags 954611 + pending
Bug #954611 [src:genwqe-user] genwqe-user: FTBFS: hw_defs.h:36:21: error: 
static declaration of ‘gettid’ follows non-static declaration
Added tag(s) pending.

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

Bug#954611: genwqe-user: diff for NMU version 4.0.18-3.1

[Sudip Mukherjee]

Control: tags 954611 + patch
Control: tags 954611 + pending

Dear maintainer,

I've prepared an NMU for genwqe-user (versioned as 4.0.18-3.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru genwqe-user-4.0.18/debian/changelog 
genwqe-user-4.0.18/debian/changelog
--- genwqe-user-4.0.18/debian/changelog 2017-03-09 14:44:34.0 +
+++ genwqe-user-4.0.18/debian/changelog 2020-04-10 14:38:27.0 +0100
@@ -1,3 +1,10 @@
+genwqe-user (4.0.18-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS. (Closes: #954611)
+
+ -- Sudip Mukherjee   Fri, 10 Apr 2020 14:38:27 
+0100
+
 genwqe-user (4.0.18-3) unstable; urgency=medium
 
   * Change Architecture to linux-any.
diff -Nru genwqe-user-4.0.18/debian/patches/fix_gettid.patch 
genwqe-user-4.0.18/debian/patches/fix_gettid.patch
--- genwqe-user-4.0.18/debian/patches/fix_gettid.patch  1970-01-01 
01:00:00.0 +0100
+++ genwqe-user-4.0.18/debian/patches/fix_gettid.patch  2020-04-10 
14:38:27.0 +0100
@@ -0,0 +1,297 @@
+Description: Fix FTBFS
+ Latest glibc has defined gettid() and as a result there was a conflict.
+ Rename gettid() to sys_gettid() to use our own gettid instead of using
+ the gettid() from glibc.
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/954611
+
+---
+
+--- genwqe-user-4.0.18.orig/lib/card_defs.h
 genwqe-user-4.0.18/lib/card_defs.h
+@@ -32,19 +32,19 @@
+ #include 
+ #include/* For SYS_xxx definitions */
+ 
+-static inline pid_t gettid(void)
++static inline pid_t sys_gettid(void)
+ {
+   return (pid_t)syscall(SYS_gettid);
+ }
+ 
+ #define pr_err(fmt, ...)  \
+   fprintf(stderr, "%08x.%08x %s:%u: Error: " fmt, \
+-  getpid(), gettid(), __FILE__, __LINE__, ## __VA_ARGS__)
++  getpid(), sys_gettid(), __FILE__, __LINE__, ## __VA_ARGS__)
+ 
+ #define pr_warn(fmt, ...) do {
\
+   if (_dbg_flag)  \
+   fprintf(stderr, "%08x.%08x %s:%u: Warn: " fmt,  \
+-  getpid(), gettid(), __FILE__, __LINE__, \
++  getpid(), sys_gettid(), __FILE__, __LINE__, 
\
+   ## __VA_ARGS__);\
+   } while (0)
+ 
+@@ -56,7 +56,7 @@ static inline pid_t gettid(void)
+ #define   pr_info(fmt, ...) do {  
\
+   if (_dbg_flag)  \
+   fprintf(stderr, "%08x.%08x %s:%u: Info: " fmt,  \
+-  getpid(), gettid(), __FILE__, __LINE__, \
++  getpid(), sys_gettid(), __FILE__, __LINE__, 
\
+   ## __VA_ARGS__);\
+   } while (0)
+ 
+--- genwqe-user-4.0.18.orig/lib/ddcb_capi.c
 genwqe-user-4.0.18/lib/ddcb_capi.c
+@@ -61,7 +61,7 @@ extern FILE *libddcb_fd_out;
+ 
+ #include/* For SYS_xxx definitions */
+ 
+-static inline pid_t gettid(void)
++static inline pid_t sys_gettid(void)
+ {
+   return (pid_t)syscall(SYS_gettid);
+ }
+@@ -69,25 +69,25 @@ static inline pid_t gettid(void)
+ #define VERBOSE0(fmt, ...) do {   
\
+   if (libddcb_fd_out) \
+   fprintf(libddcb_fd_out, "%08x.%08x: " fmt,  \
+-  getpid(), gettid(), ## __VA_ARGS__);\
++  getpid(), sys_gettid(), ## __VA_ARGS__);
\
+   } while (0)
+ 
+ #define VERBOSE1(fmt, ...) do {   
\
+   if (libddcb_fd_out && (libddcb_verbose > 0))\
+   fprintf(libddcb_fd_out, "%08x.%08x: " fmt,  \
+-  getpid(), gettid(), ## __VA_ARGS__);\
++  getpid(), sys_gettid(), ## __VA_ARGS__);
\
+   } while (0)
+ 
+ #define VERBOSE2(fmt, ...) do {   
\
+   if (libddcb_fd_out && (libddcb_verbose > 1))\
+   fprintf(libddcb_fd_out, "%08x.%08x: " fmt,  \
+-  getpid(), gettid(), ## __VA_ARGS__);\
++  getpid(), sys_gettid(), ## __VA_ARGS__);
\
+   } while (0)
+ 
+ #define VERBOSE3(fmt, ...) do {   
\
+   if (libddcb_fd_out && (libddcb_verbose > 3))\
+   fprintf(libddcb_fd_out, "%08x.%08x: " fmt,  \
+-  getpid(), gettid(), ## __VA_ARGS__);\
++  getpid(), sys_gettid(), ## __VA_ARGS__);
\
+   } while (0)
+ 
+ #define 

Bug#955535: Bug #955535: httping: flaky autopkgtest: PING google.com:80

[Abhijith PA]

Hi Aron

On 03/04/20 7:24 am, Aron Xu wrote:
> Hi,
> 
> The two different results are caused by different CI workers - some of
> our workers at ci.d.n does not have reliable network to public
> services, in this case to google.com:80, which makes the test result
> flaky.
> 
> Would you mind to consider setting up something locally (a small web
> server) in testing environment to facilitate this test? If that's okay
> I can help to cook a patch.

Yep, I was planning to run python simplehttpserver. If you are
interested in preparing a patch you are more than welcome. :)


--abhijith

Bug#955535: httping: flaky autopkgtest: PING google.com:80

[Abhijith PA]

Thanks for reporting.

On 02/04/20 12:26 pm, Sebastian Andrzej Siewior wrote:
> Source: httping
> Version: 2.5-5
> Severity: serious
> Tags: sid bullseye
> User: debian...@lists.debian.org
> Usertags: flaky
> 
> The test for httping passed on amd64[0] and failed on arm64[1]. Looking
> at the failed log
> |autopkgtest [17:03:58]: test command3: httping -F -c 4 http://google.com
> |autopkgtest [17:03:58]: test command3: [---
> |PING google.com:80 (/):
> |connect time out
> |
> |connect time out
> |
> |connect time out
> |
> |connect time out
> |
> |--- http://google.com/ ping statistics ---
> |4 connects, 0 ok, 100.00% failed, time 124118ms
> |autopkgtest [17:06:02]: test command3: ---]
> |autopkgtest [17:06:02]: test command3:  - - - - - - - - - - results - - - - 
> - - - - - -
> |command3 FAIL non-zero exit status 127
> |autopkgtest [17:06:02]:  summary
> |command1 PASS
> |command2 PASS
> |command3 FAIL non-zero exit status 127
> 
> it seems to have failed because the test is not allowed to connect to
> the internet (or google itself).
> Could it be verified what the test policy is in regard to network access
> and then
> - run the test again once CI enabled network access on all nodes
> - removed that test from CI.

httping -F -c 4 http://google.com was kind of off hand smoke test. It
was working in amd64 ci and I didn't bothered to look in to other archs.
I will try to run some simple http server locally and ping to that.


--abhijith

Bug#956339: marked as done (unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 21:28:19 +0800
with message-id <0268f4dc7ec88e40d4161bd2247164d00e3d32da.ca...@debian.org>
and subject line Re: Bug#956339: unattended-upgrades: regression: packages with 
conffile prompts are no longer skipped, leading to upgrade failures
has caused the Debian Bug report #956339,
regarding unattended-upgrades: regression: packages with conffile prompts are 
no longer skipped, leading to upgrade failures
to be marked as done.

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

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


-- 
956339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unattended-upgrades
Version: 2.1
Severity: serious

Today I noticed that packages with conffile prompts are no longer
skipped, which can lead to upgrade failures because dpkg stdin is not
connected to any terminal. I think this is a regression since the work
to enable pinning to work with unattended-upgrades.

Package installation log:
Log started: 2020-04-10  13:09:11
apt-listchanges: Reading changelogs...
apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
apt-listchanges: Reading changelogs...
Preparing to unpack .../sgml-base_1.30_all.deb ...
Unpacking sgml-base (1.30) over (1.29.1) ...
Setting up popularity-contest (1.70) ...

Configuration file '/etc/cron.daily/popularity-contest'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** popularity-contest (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package popularity-contest (--configure):
 end of file on stdin at conffile prompt
Errors were encountered while processing:
 popularity-contest
-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (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 unattended-upgrades depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  lsb-base   11.1.0
ii  lsb-release11.1.0
ii  python33.8.2-2
ii  python3-apt1.9.10
ii  python3-dbus   1.2.16-1
ii  python3-distro-info0.23
ii  ucf3.0038+nmu1
ii  xz-utils   5.2.4-1+b1

Versions of packages unattended-upgrades recommends:
ii  anacron 2.3-29
ii  cron [cron-daemon]  3.0pl1-136
ii  systemd-sysv244.3-1

Versions of packages unattended-upgrades suggests:
ii  bsd-mailx  8.1.2-0.20180807cvs-1+b1
ii  exim4-daemon-light [mail-transport-agent]  4.93-13
ii  needrestart3.5-1
ii  powermgmt-base 1.36
ii  python3-gi 3.36.0-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 2.2

On Fri, 2020-04-10 at 09:32 +0200, Bálint Réczey wrote:

> I may have already fixed the the issue with the fix for LP: #1871639.
> Could you please monitor if the problem shows up with 2.2, too?

I've tested this by downgrading popularity-contest using snapshot.d.o,
adding changes to a conffile and then running u-u. The result is that I
get this in the report, so it looks fixed again:

Subject:[package on hold] unattended-upgrades result for host: FAILURE

Unattended upgrade result: All upgrades installed

Packages that attempted to upgrade:
 popularity-contest

...
Package popularity-contest has conffile prompt and needs to be upgraded manually
Packages that will be upgraded: popularity-contest
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed 

Bug#936572: marked as done (fusil: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 13:23:36 +
with message-id 
and subject line Bug#956327: Removed package(s) from unstable
has caused the Debian Bug report #936572,
regarding fusil: 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.)


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

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 ---
Version: 1.5-1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#937447: marked as done (pygobject-2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 13:23:10 +
with message-id 
and subject line Bug#930138: Removed package(s) from unstable
has caused the Debian Bug report #937447,
regarding pygobject-2: 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.)


-- 
937447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pygobject-2
Version: 2.28.6-13
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:pygobject-2

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 ---
Version: 3.34.0+2.28.6-14+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#955541: marked as done (Login fails for a user name with non-ascii characters)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 11:35:55 +
with message-id 
and subject line Bug#955541: fixed in systemd 245.4-3
has caused the Debian Bug report #955541,
regarding Login fails for a user name with non-ascii characters
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.)


-- 
955541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 245-2
Severity: serious
Forwarded: https://github.com/systemd/systemd/issues/15141


Usernames that contain a number (or digit) as first character are
rejected by v245:
https://github.com/systemd/systemd/blob/v245/src/basic/user-util.c#L710
This will lead to login failures.

By default, adduser will not allow such usernames to be created, but can
be forced to do so via --force-badname.

While a leading dot is really questionable, the validation should be
relaxed for a leading number.



-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-6
ii  libapparmor1 2.13.3-7
ii  libaudit11:2.8.5-2+b1
ii  libblkid12.34-0.1
ii  libc62.30-2
ii  libcap2  1:2.32-1
ii  libcrypt11:4.4.15-1
ii  libcryptsetup12  2:2.3.0-1
ii  libgcrypt20  1.8.5-5
ii  libgnutls30  3.6.12-2
ii  libgpg-error01.37-1
ii  libidn2-02.3.0-1
ii  libip4tc21.8.4-3
ii  libkmod2 27-2
ii  liblz4-1 1.9.2-2
ii  liblzma5 5.2.4-1+b1
ii  libmount12.34-0.1
ii  libpam0g 1.3.1-5
ii  libpcre2-8-0 10.34-7
ii  libseccomp2  2.4.3-1
ii  libselinux1  3.0-1+b1
ii  libsystemd0  245-2
ii  mount2.34-0.1
ii  util-linux   2.34-0.1

Versions of packages systemd recommends:
ii  dbus  1.12.16-2

Versions of packages systemd suggests:
ii  policykit-10.105-26
ii  systemd-container  245-2

Versions of packages systemd is related to:
ii  dracut   048+80-2
pn  initramfs-tools  
ii  libnss-systemd   245-2
ii  libpam-systemd   245-2
ii  udev 245-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 245.4-3
Done: Michael Biebl 

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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: Fri, 10 Apr 2020 11:55:15 +0200
Source: systemd
Architecture: source
Version: 245.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Closes: 945000 955541
Changes:
 systemd (245.4-3) unstable; urgency=medium
 .
   [ Dan Streetman ]
   * d/rules: in dh_auto_test, include meson param --print-errorlogs.
 Also, don't cat testlog.txt; it's noisy and not very helpful.
 Upstream request:
 https://github.com/systemd/systemd/pull/14338#issuecomment-603432989
 .
   [ Michael Biebl ]
   * pid1: by default make user units inherit their umask from the user manager
 (Closes: #945000)
   * user-util: rework how we validate user names.
 This reworks the user validation infrastructure. There are now two
 modes. In regular mode we are strict and test against a strict set of
 valid chars. And in "relaxed" mode we just filter out some really
 obvious, dangerous stuff. i.e. strict is whitelisting what is OK, but
 "relaxed" is blacklisting what is really not OK.
 The idea is that we use strict mode whenever we allocate a new user,
 while "relaxed" mode is used when we 

Processed: Bug#955541 marked as pending in systemd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #955541 [systemd] Login fails for a user name with non-ascii characters
Added tag(s) pending.

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

Bug#955541: marked as pending in systemd

[Michael Biebl]

Control: tag -1 pending

Hello,

Bug #955541 in systemd 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/systemd-team/systemd/-/commit/2148ba0fc70c2d5dc5f23505ed0775c615c27a8e


user-util: rework how we validate user names

This reworks the user validation infrastructure. There are now two
modes. In regular mode we are strict and test against a strict set of
valid chars. And in "relaxed" mode we just filter out some really
obvious, dangerous stuff. i.e. strict is whitelisting what is OK, but
"relaxed" is blacklisting what is really not OK.

The idea is that we use strict mode whenever we allocate a new user,
while "relaxed" mode is used when we process users registered elsewhere.

Closes: #955541


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/955541

Bug#956365: redmine: unmet dependencies

[Dragos Jarca]

Package: redmine
Version: 4.0.6-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I use both gitlab and redmine.
When upgraded gitlab to 12.8.8-x, redmine was uninstalled because of 
unmet dependencies, and cannot be reinstalled.


apt-get install redmine
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 redmine : Depends: ruby-actionpack-xml-parser but it is not going to 
be installed
   Depends: ruby-roadie-rails (>= 1.3.0) but it is not going to 
be installed

E: Unable to correct problems, you have held broken packages.

Please upgrade redmine to 4.1.1 and solve the dependencies problems, so 
I can use redmine again.


Regards,
Dragos

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 
'experimental'), (500, 'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to C.UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages redmine depends on:
ii  dbconfig-common 2.0.13
ii  debconf [debconf-2.0]   1.5.73
ii  libjs-chart.js  2.9.3+dfsg-2
ii  libjs-jquery    3.3.1~dfsg-3
ii  libjs-jquery-ui 1.12.1+dfsg-5
pn  libjs-raphael   
ii  redmine-pgsql   4.0.6-2
ii  ruby    1:2.7+1
pn  ruby-actionpack-action-caching  
pn  ruby-actionpack-xml-parser  
ii  ruby-bundler    2.1.4-1
ii  ruby-coderay    1.1.2-3
pn  ruby-csv    
ii  ruby-i18n   1.8.2-2
pn  ruby-jquery-rails   
ii  ruby-mail   2.7.1+dfsg1-1
ii  ruby-mime-types 3.3.1-1
ii  ruby-mimemagic  0.3.2+dfsg-1
ii  ruby-mini-mime  1.0.1-1
ii  ruby-net-ldap   0.16.1-1
ii  ruby-nokogiri   1.10.7+dfsg1-2+b1
ii  ruby-rack   2.1.1-1
ii  ruby-rack-test  0.7.0-1
ii  ruby-rails  2:6.0.2.1+dfsg-3
ii  ruby-rails-dom-testing  2.0.3-3
pn  ruby-rails-observers    
pn  ruby-rbpdf  
ii  ruby-redcarpet  3.5.0-1+b1
ii  ruby-request-store  1.5.0-2
pn  ruby-rmagick    
pn  ruby-roadie 
pn  ruby-roadie-rails   
ii  ruby-rouge  3.15.0-1

Versions of packages redmine recommends:
pn  passenger  

Versions of packages redmine suggests:
pn  bzr 
pn  cvs 
pn  darcs   
ii  git 1:2.25.1-1
pn  mercurial   
pn  ruby-fcgi   
pn  subversion  

Processed: closing 956266

[Debian Bug Tracking System]

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

> close 956266 1.42.0+dfsg1-1
Bug #956266 [rustc] rustc: build-depends-indep on old version of wasi-libc
There is no source info for the package 'rustc' at version '1.42.0+dfsg1-1' 
with architecture ''
Unable to make a source version for version '1.42.0+dfsg1-1'
Marked as fixed in versions 1.42.0+dfsg1-1.
Bug #956266 [rustc] rustc: build-depends-indep on old version of wasi-libc
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#956266: closing 956266

[Ximin Luo]

close 956266 1.42.0+dfsg1-1
thanks

Bug#955606: marked as done (gxr: FTBFS with gulkan 0.14)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 12:34:29 +0200
with message-id <96e5a7c0-f187-ea86-ccdb-d988198c6...@debian.org>
and subject line Re: gxr: FTBFS with gulkan 0.14
has caused the Debian Bug report #955606,
regarding gxr: FTBFS with gulkan 0.14
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.)


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

The gulkan transition started, but gxr fails to build against the new
gulkan version:
| Run-time dependency gulkan-0.13 found: NO (tried pkgconfig)
|
| ../meson.build:64:0: ERROR: Dependency "gulkan-0.13" not found, tried 
pkgconfig
|
| A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 0.14.0-1

On Fri, 3 Apr 2020 11:01:22 +0200 Sebastian Ramacher  
wrote:
> Source: gxr
> Version: 0.13.2-2
> Severity: serious
> Tags: ftbfs sid buster
> Justification: fails to build from source (but built successfully in the past)
> 
> The gulkan transition started, but gxr fails to build against the new
> gulkan version:
> | Run-time dependency gulkan-0.13 found: NO (tried pkgconfig)
> |
> | ../meson.build:64:0: ERROR: Dependency "gulkan-0.13" not found, tried 
> pkgconfig
> |
> | A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt

This is now fixed in gxr 0.14.0.

Cheers,
Emilio--- End Message ---

Bug#956277: marked as done (wifite's autopkg tests depend on pyrit)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 10:21:56 +
with message-id 
and subject line Bug#956277: fixed in wifite 2.5.2-3
has caused the Debian Bug report #956277,
regarding wifite's autopkg tests depend on pyrit
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.)


-- 
956277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wifite
Version: 2.5.2-2
Severity: serious
Tags: sid bullseye

wifite's autopkg tests still depend on the removed pyrit, causing the tests to 
fail.
--- End Message ---
--- Begin Message ---
Source: wifite
Source-Version: 2.5.2-3
Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?= 

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated wifite 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Apr 2020 11:49:07 +0200
Source: wifite
Architecture: source
Version: 2.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Raphaël Hertzog 
Closes: 956277
Changes:
 wifite (2.5.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop pyrit from autopkgtest deps (Closes: #956277)
Checksums-Sha1:
 7f376a89e7ea6d3de6b10b3818d9eb7a1fc7b0e6 1673 wifite_2.5.2-3.dsc
 28305a75265d6cd4e7d35b2dfa8bab9f603b2b37 6432 wifite_2.5.2-3.debian.tar.xz
 22aa8deb82ede74c90e63f0251e88ef795fc684c 8188 wifite_2.5.2-3_source.buildinfo
Checksums-Sha256:
 63deccb018f434e46072281cb07c9d1839ea16377c3bfb53a6fb4775ed7b77b9 1673 
wifite_2.5.2-3.dsc
 3d3cbd60f28204abb05c883b29a7e2bfcbc2da68dc7a744b44bcc643a54634bc 6432 
wifite_2.5.2-3.debian.tar.xz
 c51602e06e157f7b4f8695988c9ec62c728a273668ee5a3ced493bf5af63f67b 8188 
wifite_2.5.2-3_source.buildinfo
Files:
 682480fed04986a5fdea209117496050 1673 net optional wifite_2.5.2-3.dsc
 b436cd5eaa0b3b51096044aab4f6462d 6432 net optional wifite_2.5.2-3.debian.tar.xz
 ac3392e416e19947e445b49f531d26ab 8188 net optional 
wifite_2.5.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl6QQTEACgkQA4gdq+vC
mrm7ZggAh+3YPUBqXQ3sbYg6AKbktPayjTPkwlJtzoFMkv+q0kSCaTAma4BeK67I
mPdheBG0fp5SFmh4K2KDnpRzyvZwOF6UsyLeV8kRhMr1638jpHvJ2WjtJ1tjoJpQ
+OBT5QDvR4pLJRbAEMTx0qD27VjQ8fWjLNiFjcspO1wg3z6He+S8L+O7RVRzz4Xy
Rq490fjm7E8opwzoGm4nT80GQCghkgVm2FkF2y0d2u5nw2cg0ignckAcD0QuE0E2
xO5yjBs4PgCWZooj9DNQzm+Txwi0vbYWVN9TVNgeZr38fsU2nhSxYGt1Id3gQYk7
tKV+zi84vYDw6e3ZhNq05p94nA8xIw==
=e6Gg
-END PGP SIGNATURE End Message ---

Bug#956277: marked as pending in wifite

[Raphaël Hertzog]

Control: tag -1 pending

Hello,

Bug #956277 in wifite 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/pkg-security-team/wifite/-/commit/40549d7cbaacfafa9b9196c7c6253ea408836880


Drop pyrit from autopkgtest deps

Closes: #956277


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/956277

Processed: Bug#956277 marked as pending in wifite

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #956277 [src:wifite] wifite's autopkg tests depend on pyrit
Added tag(s) pending.

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

Bug#953487: fixed in runescape 0.7-1

[Markus Koschany]

I suggest we wait a little for a response from
non-f...@buildd.debian.org before we make another upload. However if
there is no response in two weeks, we can just proceed by making a
binary upload of runescape.

Bug #956275 can be resolved by replacing the runescape.png icon. The
license is most likely not BSD-2-clause. You should either document the
correct license, the image must be distributable at least, or you can
create or find your own icon. For instance you could create an image the
same size with a black, red or blue background and then you add the R S
initials in white. Simple icon, easily done.

Bug #956276 is about an additional verification step, e.g. to verify the
integrity of the launcher with a hashsum. You could store the value in a
text file in our Git repository and then fetch the value and compare it
with the hashsum of the binary before you run the java command. By
storing the value in Git we can adjust the value whenever there is a new
runescape update without having to make another Debian upload. This
could be especially useful for stable releases. In any case I would try
to avoid to hardcode the value.

I don't consider bug #956276 release critical because there is no Debian
Policy justification for it and there is no more risk involved than
downloading the file with a web browser normally poses, so it should be
treated as a normal or important bug. What you can and should do is to
improve the package description. It should be clear that src:runescape
is a mere script that downloads and runs the runescape launcher and that
Debian cannot guarantee the integrity of this binary file because it is
non-free and it is closed source. So simply warn about that in the
package description and when your script is executed. The warning
message could be displayed in a text terminal or you could use zenity to
make it more user friendly and obvious.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#953487: fixed in runescape 0.7-1

[Markus Koschany]

Hello Carlos,

I had uploaded the new version of runescape to fix bug 953487 because
you stated in

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953487#25

that the package has been whitelisted. Apparently this is not the case
hence I am writing to non-f...@buildd.debian.org again and I kindly ask
that runescape is whitelisted for autobuilding. The package is basically
a script and the license allows autobuilding.

Thanks,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#956110: marked as done (sabnzbdplus: Depends on cruft packages)

[Debian Bug Tracking System]

Your message dated Fri, 10 Apr 2020 08:49:03 +
with message-id 
and subject line Bug#956110: fixed in sabnzbdplus 3.0.0~0git20200408+dfsg-1
has caused the Debian Bug report #956110,
regarding sabnzbdplus: Depends on cruft packages
to be marked as done.

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

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


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

Note: Using the FTBFS tag since it is the closest one we have.

sabnzbdplus depends on python-cheetah, which is not longer built by
cheetah.  Once it is decrufted, the package will be uninstallable.

This is also true for python-configobj, no longer built by configobj.

Since we can't release with cruft packages, this is an RC issue.  Please
update the package to drop these dependencies (I have not assessed if
this is feasible short of a Python 3 port).

Scott K
--- End Message ---
--- Begin Message ---
Source: sabnzbdplus
Source-Version: 3.0.0~0git20200408+dfsg-1
Done: JCF Ploemen (jcfp) 

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

Debian distribution maintenance software
pp.
JCF Ploemen (jcfp)  (supplier of updated sabnzbdplus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Apr 2020 14:28:35 +
Source: sabnzbdplus
Architecture: source
Version: 3.0.0~0git20200408+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: JCF Ploemen (jcfp) 
Changed-By: JCF Ploemen (jcfp) 
Closes: 938425 956110
Changes:
 sabnzbdplus (3.0.0~0git20200408+dfsg-1) unstable; urgency=medium
 .
   [ JCF Ploemen (jcfp) ]
   * New upstream release:
 + adds support for Python3. (Closes: #938425, #956110)
 + based on a snapshot of the 'develop' branch of upstream git
   (commit c0d0964). Files and directories that won't be part of
   regular upstream tarballs have been removed, and missing
   javascript sources merged as usual along the lines of the
   get-orig-source target.
   * Tests:
 + add superficial basic-runs autopkgtest.
 + add upstream testsuite as autopkgtest.
   * Control:
 + switch python dependencies to their python3 equivalents.
 + remove build-deps on imagemagick and librsvg2-bin, previously
   used to convert a logo image for use as an icon.
 + remove deps on libjs-jquery-tablesorter (rss feed issues), and
   libjs-excanvas, libjs-mochikit (no longer needed after removal
   of the smpl theme).
 + add deps on python3-chardet, python3-cherrypy3,
   python3-feedparser, python3-portend, and python3-sabyenc.
 + bump recommends on python3-cryptography, par2, and unrar to
   hard dependencies and remove obsolete versioning of unrar.
 + add recommends on python3-notify2, python3-dbus, unzip.
 + add Pre-Depends: ${misc:Pre-Depends}, needed to ensure a recent
   init-system-helpers version is available to assorted automagic
   maintainer scripts.
   * Copyright:
 + bump years for packaging and upstream.
 + remove obsolete entries related to the smpl interface theme.
 + correct the filename of the moment.js entry.
 + convert to machine-readable format.
 + use 'Expat' rather than 'MIT' as license shortname.
   * Compat: bump level to 12 (from 11).
   * Patches:
 + remove 06_use_packaged_modules.diff (no longer needed), and
   90_rss_feed_without_id_would_crash (fixed upstream).
 + refresh all others.
 + extend patch 09 to also cover the certificate validation check.
 + add 10_pytest_mods to make the upstream testsuite find packaged
   files, for use with continuous integration.
   * d/README.Debian: remove cherrypy rationale, obsolete.
   * Rules:
 + switch to python3.
 + cleanup the list of excluded files in the dh_install override.
 + remove dh_compress override now that examples are excluded by
   default.
 + remove 

Processed: openafs-modules-dkms: piuparts failure on package installation

[Debian Bug Tracking System]

Processing control commands:

> block 953709 by -1
Bug #953709 {Done: Benjamin Kaduk } [src:openafs] src:openafs: 
fails to migrate to testing for too long
953709 was not blocked by any bugs.
953709 was not blocking any bugs.
Added blocking bug(s) of 953709: 956358

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

Processed: block 953720 with 951306

[Debian Bug Tracking System]

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

> block 953720 with 951306
Bug #953720 [src:snek] src:snek: fails to migrate to testing for too long
953720 was not blocked by any bugs.
953720 was not blocking any bugs.
Added blocking bug(s) of 953720: 951306
> thanks
Stopping processing here.

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

Bug#956358: openafs-modules-dkms: piuparts failure on package installation

[Adrian Bunk]

Package: openafs-modules-dkms
Version: 1.8.6~pre1-3
Severity: serious
Control: block 953709 by -1

https://piuparts.debian.org/sid/source/o/openafs.html

...
  Loading new openafs-1.8.6pre1 DKMS files...
  It is likely that 4.19.0-8-amd64 belongs to a chroot's host
  Building for 5.4.0-4-amd64
  Building initial module for 5.4.0-4-amd64
  Error! Bad return status for module build on kernel: 5.4.0-4-amd64 (x86_64)
  Consult /var/lib/dkms/openafs/1.8.6pre1/build/make.log for more information.
  dpkg: error processing package openafs-modules-dkms (--configure):
   installed openafs-modules-dkms package post-installation script subprocess 
returned error exit status 10
  Processing triggers for libc-bin (2.30-4) ...
  Errors were encountered while processing:
   openafs-modules-dkms
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Processed: closing 949983

[Debian Bug Tracking System]

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

> close 949983
Bug #949983 [src:python-apt] python-apt: Build-Depends on pep8 which has been 
removed
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: don't explicitly request python 3.7 for the build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #951829 [src:openvdb] python3-openvdb: build against the default python3 
version
Severity set to 'normal' from 'serious'

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

Bug#951829: don't explicitly request python 3.7 for the build

[Mathieu Malaterre]

Control: severity -1 normal

On Fri, Mar 27, 2020 at 12:57 PM Emilio Pozuelo Monfort
 wrote:
>
> Control: reopen -1 7.0.0-1
> Control: retitle -1 python3-openvdb: build against the default python3 version
>
> On Mon, 24 Feb 2020 11:10:49 +0100 Mathieu Malaterre  wrote:
> > Control: tags -1 + patch
> > Control: retitle -1 replace python3-all-dev with python3.7-dev
>
> Err, that's not really the solution.
>
> The not ideal solution was to build for the default python version, i.e.
> build-depend on python3-dev and use python3. That would have built against
> python3.7 when that was the default, and against python3.8 now that it has
> changed. And with a binNMU from the release team, you wouldn't have even 
> noticed.

Oh ok. I missed that.

> The ideal solution is to build against python3-all-dev and build for *all*
> supported python versions. So that when python3.7 and python3.8 are both
> supported, you build the python extension for both of them.

Just for later reference. Doing so would imply going the kde package
style (eg. pykde4), which means somehow importing the
"overriden_command" from dhmk.mk (pkg-kde-tools). After that doing
lots of boilerplate code to execute $(foreach) on all python version,
just because python3.8 cannot deal with a python3.7 module.

Given that openvdb is a beast to compile (mips64el even failed), a
beast to execute unit test there is no possible way a double
compilation + double testing will ever work on those arches, I am
marking this solution as wontfix. I'll go ahead and implement the
previous solution where a binNMU is required.

Thanks,