Bug#936857: marked as done (libfreenect: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 09 Apr 2020 05:18:29 +
with message-id 
and subject line Bug#936857: fixed in libfreenect 1:0.5.3-2
has caused the Debian Bug report #936857,
regarding libfreenect: 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.)


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

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: libfreenect
Source-Version: 1:0.5.3-2
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
libfreenect, 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.
Sandro Tosi  (supplier of updated libfreenect 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, 09 Apr 2020 00:50:52 -0400
Source: libfreenect
Architecture: source
Version: 1:0.5.3-2
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Bourdaud 
Changed-By: Sandro Tosi 
Closes: 936857
Changes:
 libfreenect (1:0.5.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; python bindings can be added again when packaging an
 upstream release supporting python3; Closes: #936857
Checksums-Sha1:
 5b1deef310cc670c8d23c2852520118897dac786 2388 libfreenect_0.5.3-2.dsc
 78154737e0713025ef761a9be038c0389ec1da66 30392 
libfreenect_0.5.3-2.debian.tar.xz
 e016e5579cb46799bb9c7260d0a48fd0bb8743e9 12086 
libfreenect_0.5.3-2_amd64.buildinfo
Checksums-Sha256:
 d873b15ba17f169264f90952208e30f413384cf4ce8abaa084774d734cdda435 2388 
libfreenect_0.5.3-2.dsc
 3063bcc6e6cd1327b6e8bf2e8d4ae1e40a0dbbc9c084003b85c0c7834b68c17a 30392 
libfreenect_0.5.3-2.debian.tar.xz
 

Processed: libfreenect: diff for version 1:0.5.3-2

[Debian Bug Tracking System]

Processing control commands:

> tags 936857 + patch
Bug #936857 [src:libfreenect] libfreenect: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#936857: libfreenect: diff for version 1:0.5.3-2

[Sandro Tosi]

Control: tags 936857 + patch


Dear maintainer,

I've prepared an upload for libfreenect (versioned as 1:0.5.3-2). The diff
is attached to this message.

Regards.

diff -Nru libfreenect-0.5.3/debian/changelog libfreenect-0.5.3/debian/changelog
--- libfreenect-0.5.3/debian/changelog	2016-01-01 22:37:38.0 -0500
+++ libfreenect-0.5.3/debian/changelog	2020-04-09 00:50:52.0 -0400
@@ -1,3 +1,11 @@
+libfreenect (1:0.5.3-2) unstable; urgency=medium
+
+  * Team upload.
+  * Drop python2 support; python bindings can be added again when packaging an
+upstream release supporting python3; Closes: #936857
+
+ -- Sandro Tosi   Thu, 09 Apr 2020 00:50:52 -0400
+
 libfreenect (1:0.5.3-1) unstable; urgency=medium
 
   * Recent upstream bugfix release
diff -Nru libfreenect-0.5.3/debian/control libfreenect-0.5.3/debian/control
--- libfreenect-0.5.3/debian/control	2016-01-01 22:37:38.0 -0500
+++ libfreenect-0.5.3/debian/control	2020-04-09 00:49:34.0 -0400
@@ -5,7 +5,7 @@
 Uploaders: Arne Bernin , Yaroslav Halchenko , Mark Renouf 
 Build-Depends: debhelper (>= 9), cmake,  pkg-config,
  libusb-1.0-0-dev(>= 1.0.18~), freeglut3-dev, libxmu-dev, libxi-dev,
- python-all-dev (>= 2.6.6-3~), cython, python-numpy, doxygen
+ doxygen
 X-Python-Version: 2.7
 Standards-Version: 3.9.6
 Homepage: http://openkinect.org/
@@ -104,27 +104,6 @@
  .
  This package contains the documentation of the API of libfreenect.
 
-Package: python-freenect
-Section: python
-Architecture: any
-Provides: ${python:Provides}
-Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends},
- libfreenect0.5 (= ${binary:Version}), python-numpy
-Suggests: python-matplotlib, python-opencv
-Description: library for accessing Kinect device -- Python bindings
- libfreenect is a cross-platform library that provides the necessary interfaces
- to activate, initialize, and communicate data with the Kinect hardware.
- Currently, the library supports access to RGB and depth video streams, motors,
- accelerometer and LED and provide binding in different languages (C++,
- Python...)
- .
- This library is the low level component of the OpenKinect project which is an
- open community of people interested in making use of the Xbox Kinect hardware
- with PCs and other devices.
- .
- This package provides freenect extension to use libfreenect functionality
- from Python and includes some demo scripts.
-
 Package: freenect
 Section: libs
 Architecture: any
diff -Nru libfreenect-0.5.3/debian/python-freenect.docs libfreenect-0.5.3/debian/python-freenect.docs
--- libfreenect-0.5.3/debian/python-freenect.docs	2016-01-01 22:37:38.0 -0500
+++ libfreenect-0.5.3/debian/python-freenect.docs	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-wrappers/python/README
diff -Nru libfreenect-0.5.3/debian/python-freenect.examples libfreenect-0.5.3/debian/python-freenect.examples
--- libfreenect-0.5.3/debian/python-freenect.examples	2016-01-01 22:37:38.0 -0500
+++ libfreenect-0.5.3/debian/python-freenect.examples	1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-wrappers/python/demo_*
-wrappers/python/frame_convert.py
diff -Nru libfreenect-0.5.3/debian/python-freenect.install libfreenect-0.5.3/debian/python-freenect.install
--- libfreenect-0.5.3/debian/python-freenect.install	2016-01-01 22:37:38.0 -0500
+++ libfreenect-0.5.3/debian/python-freenect.install	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-usr/lib/python*/*packages/freenect.so
diff -Nru libfreenect-0.5.3/debian/rules libfreenect-0.5.3/debian/rules
--- libfreenect-0.5.3/debian/rules	2016-01-01 22:37:38.0 -0500
+++ libfreenect-0.5.3/debian/rules	2020-04-09 00:49:51.0 -0400
@@ -5,12 +5,10 @@
 export MA_TRIPLET=`dpkg-architecture -qDEB_HOST_MULTIARCH`
 
 %:
-	dh $@ --with python2
+	dh $@
 
 override_dh_auto_configure:
 	dh_auto_configure -- \
-  -DBUILD_PYTHON:Bool=True \
-  -DPYTHON_EXECUTABLE:Path=/usr/bin/python \
   -DPROJECT_LIBRARY_INSTALL_DIR:Path="lib/$(MA_TRIPLET)"
 
 override_dh_auto_build-indep:
@@ -22,10 +20,6 @@
 	mkdir -p debian/html
 endif
 
-override_dh_python2:
-	dh_python2 -p python-freenect
-	if [ -x /usr/bin/dh_numpy ]; then dh_numpy -ppython-freenect; fi
-
 override_dh_installdocs:
 	dh_installdocs --all CONTRIB
 

Bug#956260: bkchem: should this package be removed?

[Sandro Tosi]

Package: bkchem
Severity: serious
Tags: bullseye, sid

Hello,
i think this pacakge should be removed from debian:


* python2-only
* dead upstream (last release in 2010)
* relatively low pop-con
* keeps in the archive at least 1 package that could be removed if we remove
  bkchem

if I dont receive within week a good reason to keep this pacakge in the archive,
i'll file for its removal.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages bkchem depends on:
ii  python  2.7.16-1
ii  python-pil  6.1.0-1
pn  python-pmw  

bkchem recommends no packages.

Versions of packages bkchem suggests:
ii  python-cairo  1.16.2-1+b1

Bug#938719: marked as done (trash-cli: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 09 Apr 2020 04:03:32 +
with message-id 
and subject line Bug#938719: fixed in trash-cli 0.17.1.14-3
has caused the Debian Bug report #938719,
regarding trash-cli: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:trash-cli

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: trash-cli
Source-Version: 0.17.1.14-3
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
trash-cli, 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 trash-cli package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Apr 2020 23:44:29 -0400
Source: trash-cli
Architecture: source
Version: 0.17.1.14-3
Distribution: unstable
Urgency: medium
Maintainer: Stefano Karapetsas 
Changed-By: Sandro Tosi 
Closes: 938719
Changes:
 trash-cli (0.17.1.14-3) unstable; urgency=medium
 .
   * Switch to python3; Closes: #938719
Checksums-Sha1:
 273ad2bfcf7bc9150a53322da82e3d7941abb828 2006 trash-cli_0.17.1.14-3.dsc
 2714c60ebf9a61e24420e97bf462256130f3ebab 4420 
trash-cli_0.17.1.14-3.debian.tar.xz
 e0378483af67b0be88bf4e1f514b659fbe3a9cad 6425 
trash-cli_0.17.1.14-3_source.buildinfo
Checksums-Sha256:
 845b1b96bf7bb9e3f2a46e009e01e87c2045f8b311e2212ceb31c214e19c8a66 2006 
trash-cli_0.17.1.14-3.dsc
 5107a5b662a2ea135119ba16c66cf861318d40b0abf79ce99e298f7ffd1db95f 4420 
trash-cli_0.17.1.14-3.debian.tar.xz
 5e1d794ed146d701ad6c1fd716b1deb3847cbcfc88a5729125d84c251c7bfcc4 6425 
trash-cli_0.17.1.14-3_source.buildinfo
Files:
 bb1f44d56338e804ef00a6e0fb1cc8d7 

Processed: Re: Bug#953367: geneweb-gui binary package might need to be removed for Bullseye

[Debian Bug Tracking System]

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

> severity 953367 normal
Bug #953367 [geneweb-gui] geneweb-gui binary package might need to be removed 
for Bullseye
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#954506: marked as done (ttyrec: FTBFS: ttyrec.c:60:10: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 09 Apr 2020 01:04:36 +
with message-id 
and subject line Bug#954506: fixed in ttyrec 1.0.8-5.1
has caused the Debian Bug report #954506,
regarding ttyrec: FTBFS: ttyrec.c:60:10: 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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -O2 -g -fomit-frame-pointer -Wall -DSVR4 -D_GNU_SOURCE   -c -o ttyrec.o 
> ttyrec.c
> ttyrec.c:60:10: fatal error: stropts.h: No such file or directory
>60 | #include 
>   |  ^~~
> compilation terminated.
> make[2]: *** [: ttyrec.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/ttyrec_1.0.8-5_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated ttyrec 
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: Mon, 06 Apr 2020 19:48:56 +0100
Source: ttyrec
Architecture: source
Version: 1.0.8-5.1
Distribution: unstable
Urgency: medium
Maintainer: NIIBE Yutaka 
Changed-By: Sudip Mukherjee 
Closes: 954506
Changes:
 ttyrec (1.0.8-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS. (Closes: #954506)
Checksums-Sha1:
 68d3e74933713411abc02744a7d38f990945ab69 1682 ttyrec_1.0.8-5.1.dsc
 0996e9820804b501e984b7ebef23cb9d6a99166c 35324 ttyrec_1.0.8-5.1.debian.tar.xz
 129cd708818689f1b5489e7de06ef0505cfaa104 5332 ttyrec_1.0.8-5.1_source.buildinfo
Checksums-Sha256:
 73b6e11a9805aea7056fa5cd62d60189ccb0faa456285b62cdd79090402e1282 1682 
ttyrec_1.0.8-5.1.dsc
 82d04c17db3ab7d069d5a814c0ae5147ebf91239006051987a6708967d8f8426 35324 
ttyrec_1.0.8-5.1.debian.tar.xz
 09efbc5679183f6c82f486aa97adf27b11d7c0654844ecb9a3112b53827e15f8 5332 
ttyrec_1.0.8-5.1_source.buildinfo
Files:
 830b8b9013d67d44a35a63bbc00489d9 1682 misc optional ttyrec_1.0.8-5.1.dsc
 50d1c0a47ae413887a4d5386bfd7970d 35324 misc optional 
ttyrec_1.0.8-5.1.debian.tar.xz
 a636b7a6cbb64f7a2a91948d9413135b 5332 misc optional 
ttyrec_1.0.8-5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6OcPcACgkQweDZLphv
fH53CQ//czzwXO/UZYVp23xRJhq+UEv0xZa08ujZd2FT2ZACsTQ81HvNzmFDsFY1
oVBXJFemqP7I7KKxirtUPN+jst1nMGfh6cSX/8MqyXREI+n9l1s5RiovizZWKTVO
nMGlO6P7mXBaE8JDtG5EV1bQkoYupN+fxk/KJuvgQtdrHdjFEHgyS9nNPjJg8p0W
a21Dva58rxMDJIpuOVZOuLCJvwENqWuxEySiT/PurxX8yYTWARoIecVQa3+Fl1ca
rbE6n1LS8ZXeBzQwDLYjBMdYWvVG25psTg05Z2jCbw3NWKgEyUDJRhvRMYU+HQJZ
PsV8bQzyYwfs72Gym732fi+dqVwmh4auNUUlFR12EBnO9NYTGpTKrDZ3zXBZppfu
DA6+gwULPJemAxEgShGNl7ZXmzJ+PTs0GufMlm/edOPt6KbNUK1KD0jjkY0lhNW7
Nip0zW/eOPVMY957bmBDraA1P4C+jMV2sh5FqVDx0hg7W8TuPHwyGkqecysF1tKr
1MqLL9Byw85m+3NUPDWk3hsqw6fgX9RYT7b61dMB+B8yCt43eipGb7bwdzF0/NB/
4e3SRRUeeCnxTXJyIN4JGi5e3dNeE748JXa5ZriG56h1on27svp/UQ2M7g+R9+ZT
ADw7IimewWChSkEcH5kyWlh45DqCye/OvdRiCRSGVUGcGBJey84=
=mG2/
-END PGP SIGNATURE End Message ---

Bug#954525: marked as done (nis: FTBFS: log_msg.c:35:1: error: static declaration of ‘gettid’ follows non-static declaration)

[Debian Bug Tracking System]

Your message dated Thu, 09 Apr 2020 00:20:00 +
with message-id 
and subject line Bug#954525: fixed in nis 3.17.1-4
has caused the Debian Bug report #954525,
regarding nis: FTBFS: log_msg.c:35:1: error: static declaration of ‘gettid’ 
follows non-static declaration
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..-D_REENTRANT=1 -Wall 
> -DUSE_BROADCAST=1 -DLOCALEDIR=\"/usr/share/locale\"   -DUSE_SD_NOTIFY=1 -O2 
> -Wall -g -MT log_msg.o -MD -MP -MF .deps/log_msg.Tpo -c -o log_msg.o log_msg.c
> log_msg.c:35:1: error: static declaration of ‘gettid’ follows non-static 
> declaration
>35 | gettid (void)
>   | ^~
> In file included from /usr/include/unistd.h:1170,
>  from log_msg.c:29:
> /usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: note: previous 
> declaration of ‘gettid’ was here
>34 | extern __pid_t gettid (void) __THROW;
>   |^~
> make[3]: *** [Makefile:435: log_msg.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/nis_3.17.1-3_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated nis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Apr 2020 19:42:24 +0100
Source: nis
Architecture: source
Version: 3.17.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sudip Mukherjee 
Closes: 954525
Changes:
 nis (3.17.1-4) unstable; urgency=medium
 .
   * QA upload.
   * Mark source format as quilt.
   * Import diff in quilt format.
   * Fix FTBFS. (Closes: #954525)
   * Update Standards-Version to 4.5.0
   * Add dependency on debhelper-compat.
 - Update compat level to 12.
Checksums-Sha1:
 97d8623a9c6d8936f496db6a5873302fa7b203b2 1737 nis_3.17.1-4.dsc
 043c45ecbb4bb25853d45d790746b618c0611cce 39536 nis_3.17.1-4.debian.tar.xz
 f58aeffb8dd01f28d0eda029a1374a55c4d08628 5304 nis_3.17.1-4_source.buildinfo
Checksums-Sha256:
 fe71c7559ffc28a989b59a4e74457e1af1447795a601912f76a45e5732e8f15f 1737 
nis_3.17.1-4.dsc
 43ffdc5e68ce9e90d97f29989a14621ab971786195f1bb5528186b0c6cdb9d12 39536 
nis_3.17.1-4.debian.tar.xz
 be7ca8bfc3964c647acde8743bfa29d0c5a8dbcad50dd2982e43826054ff489f 5304 
nis_3.17.1-4_source.buildinfo
Files:
 6c3c5abb51ab0a5ae6bfea8c1f8f86cd 1737 net optional nis_3.17.1-4.dsc
 19f4cab755c0f6f28a453c0683bc0d2b 39536 net optional nis_3.17.1-4.debian.tar.xz
 7f274ddf0003ec6dc6501dc7bbe450ee 5304 net optional 
nis_3.17.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6OZjsACgkQweDZLphv
fH7T/xAAg53irXtypWLp8kO+UTQ85ifhfNU/oGZ35doLVppGCxL9ni3zy0I+7V+0
06YQGXttH9w/JF/MGXrhE0IBT2amnIyUiqdRZ5kmfUSwMMqlcyMhEOgrybQYZuHm
FtCIPKo7OPbXV9/E/YVc3o1NgaAs4mUiERpGw13V8KoWLhhCBXyB5KTtDYaOD9Ab
ELw5b9psVjyf8amSXNz9ch843xp+Wr0Y84WGikqK6ba//BUtAMtrPmfEEOyjdNmC
3/iA8LJ5fGfK0W5f8oCnyiWCr4j4U6oR042SKCYkCpFuptVPnl0rBLl9gKX5VPqc
bDtI2wqLXvDUK2sndX84HZv+/vDPX5efHE4FiKkPO1f2q/WZXlc9dtSOz4nFJScy
3x81ZKkr9WZdDaXAh5CbSUefI7Sg0oZTHE0Y6ILk0JahoZFpJtLD4O9Svrgcjp4C

Bug#954311: Not just rendering issues...

[Pascal Giard]

Thanks for the information, I appreciate it.

Apparently I missed the transition from intel_drv to modesetting_drv.

After switching to modesetting (instead of intel) and purging
xserver-xorg-video-intel, the workaround in /etc/drirc is no longer needed.

Best regards,

-Pascal
--
Homepage (http://pascal.giard.info)
École de technologie supérieure (http://etsmtl.ca)




On Wed, Apr 8, 2020 at 10:52 AM Timo Aaltonen  wrote:

> On 8.4.2020 17.15, Pascal Giard wrote:
> > On Mon, Apr 6, 2020 at 12:05 PM Timo Aaltonen  > > wrote:
> >
> > On 6.4.2020 1.55, Pascal Giard wrote:
> > > Thanks A LOT for the /etc/drirc trick, it fixed the problem
> > > detailed below for me.
> > > Took me over an hour to figure out what was wrong and to end up on
> > this
> > > bug report.
> > >
> > > I have a Thinkpad T480 (Intel UHD 620).
> > >
> > > The new iris driver causes all my video players to crash (e.g.,
> VLC or
> > > mpv) and prevents Zoom from converting my recorded sessions.
> > Do you use xserver-xorg-video-intel? If yes, get rid of it.
> >
> >
> > I do use it, yes. Which driver am I suppose to use instead?
>
> The default, which is modesetting_drv.so from the xserver.
>
>
> --
> t
>

Bug#946853: marked as done (Fails to build with glibc 2.30)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 23:18:43 +
with message-id 
and subject line Bug#946853: fixed in ace 6.4.5+dfsg-1.1
has caused the Debian Bug report #946853,
regarding Fails to build with glibc 2.30
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.)


-- 
946853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ace
Version: 6.4.5+dfsg-1
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

The issue has been reported upstream and fixed in
https://github.com/DOCGroup/ACE_TAO/pull/939

The incoming patches is used in Ubuntu and fixes the issue

--- End Message ---
--- Begin Message ---
Source: ace
Source-Version: 6.4.5+dfsg-1.1
Done: Sudip Mukherjee 

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated ace package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Apr 2020 11:55:27 +0100
Source: ace
Architecture: source
Version: 6.4.5+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian ACE+TAO maintainers 
Changed-By: Sudip Mukherjee 
Closes: 946853
Changes:
 ace (6.4.5+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build failure. (Closes: #946853)
Checksums-Sha1:
 9e601382a73e647300f9c33328eb269dd6308961 4395 ace_6.4.5+dfsg-1.1.dsc
 b3a5aa6495f6bb143fcfc71b7f49dcac124e9129 37512 ace_6.4.5+dfsg-1.1.debian.tar.xz
 a9aef0f8e130103f1482bfe48f47b9ac7d584172 10626 
ace_6.4.5+dfsg-1.1_source.buildinfo
Checksums-Sha256:
 f764d08abc2775be3999dcd7d9268bb5ece866f5b2c7b236a6d58939fc16b3f2 4395 
ace_6.4.5+dfsg-1.1.dsc
 e0bf96df2f251d00ea9bb8b35fe6a451a0c2be572e669eedbaa6e84dde94d81d 37512 
ace_6.4.5+dfsg-1.1.debian.tar.xz
 bca253b667cbb39caed79a7c8668c6d8a058b6d8409dab64b04ef0f7f0f5743f 10626 
ace_6.4.5+dfsg-1.1_source.buildinfo
Files:
 4985fc582abbde151dccc342328fa09e 4395 devel optional ace_6.4.5+dfsg-1.1.dsc
 2b63aaa85a2cb2d4062aa5d086dd845a 37512 devel optional 
ace_6.4.5+dfsg-1.1.debian.tar.xz
 43bc0a839fe3832ffe7981a6b6c836b0 10626 devel optional 
ace_6.4.5+dfsg-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6OVoIACgkQweDZLphv
fH7DNBAA840ShxQI88txy74XT6zkjLI7nVew/v2pr4kFll6PZWOVMWVBR5ljFLS0
crBlhjVoLTSX1g+0DvlTeZeJU6F4ZIpZInMVV8seMfPJeDW28Nzx+OA7BYUn0v7D
VSV5w9QuPjt+VtCfy3+wEpFybH+cBeZw0qol7DRtOhAO9gHqywheYk64nOycFTKm
VmPr4ecYfoHq+Ks4ZeNVbZ/3rNnL6Aljc05Rwz7UY2veN+dy289JAKzHDshsAwTI
1FU2AijP4lLsN146bWavEJpV+G8pZhqv+qUQ9DsILIBB5QreovZtQxyHDNjEPesW
3yzBSM3o0apxM3zfSiSZyIvyYW+By7kHzIiZGOvhplz34IHY+RGwVVyMLrvgjbYw
Tj3MD+ogmmfPLffTiH7/YRFkCQE92Lnw20oK0CzlIPyrjVHc/OsflBAzp/JVN48T
1OYZgxG4rKRFsawUCxPwhie/K/Mq90VRuLZsXLrfLLNRmPbibee8t3Fw3a28Wwfb
nXUHQSvlLZKvzxABg83JlmnRiIGFo/8FoAyGe5rt7I2F2FgReti9RgQ/k+4zExw9
WEspsgQbG7v+wa/ZwUiYw0GCX/8Ej98ROMZUpVoW90w4KHxHOCxqRebujArzKbhC
fn6VuyKO4Qap7u8Fmnw0jDqF7PlkLVBK5sMSnXROGMgDz4lOvIg=
=PipM
-END PGP SIGNATURE End Message ---

Bug#952066: marked as done (jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 23:03:36 +
with message-id 
and subject line Bug#952066: fixed in jag 0.3.6-1
has caused the Debian Bug report #952066,
regarding jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.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.)


-- 
952066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jag
Version: 0.3.5-5
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):
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_OPENGL_LIB 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB 
> -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -Isrc -Isrc 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o src/gametools.o 
> src/gametools.cpp
> In file included from src/gamesound.h:33,
>  from src/gametools.cpp:33:
> /usr/include/SDL2/SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file 
> or directory
>25 | #include "SDL_stdinc.h"
>   |  ^~
> compilation terminated.
> make[1]: *** [Makefile:795: src/gametools.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/jag_0.3.5-5_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Carlos Donizete Froes  (supplier of updated jag package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Mar 2020 16:37:58 -0300
Source: jag
Architecture: source
Version: 0.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Carlos Donizete Froes 
Closes: 952066
Changes:
 jag (0.3.6-1) unstable; urgency=medium
 .
   * New upstream release. FTBFS bug fixed. (Closes: #952066)
   * debian/control:
 + Bumped Standards-Version to 4.5.0.
 + Set Rules-Requires-Root to no.
 - Removed ${source:Version} from Depends.
   * debian/copyright:
 + Added copyright information for contact.
 + Copyright updated for current years (2020).
   * Update debian/upstream/metadata years (2020).
   * Removed d/jag.6 and d/jag.desktop.
   * debian/jag.install:
 + Binary file path changed.
 + Changed the path of the jag.desktop file.
   * debian/manpages: Changed the path of the jag.6 file.
   * debian/rules: Removed override_dh_auto_clean.
Checksums-Sha1:
 f816527dec47dedf25df4a2554612c6ad48b4365 2194 jag_0.3.6-1.dsc
 386756e6f214fbb224d9265c39d1cdf1f19eb5d3 6905847 jag_0.3.6.orig.tar.bz2
 1a765f782fb8f2199840a459aa08a0ef4befdbcb 12436 jag_0.3.6-1.debian.tar.xz
 b0068b6a550a62ffd3e02fcd1daa122193511ae2 13386 jag_0.3.6-1_amd64.buildinfo
Checksums-Sha256:
 b589018921a638767de6402a23ba531c7dad7ae6a3552e087c972b73dd5212e4 2194 
jag_0.3.6-1.dsc
 fdd1bb977a23ac3c31271e4f9c9f1a849bb86fb79e63a5161f88641f19b1732e 6905847 
jag_0.3.6.orig.tar.bz2
 f3c638a8884b9f3325e7635ff2e1f6d2c6531a05ed2f2c480598944cd63d80f2 

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

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 22:20:28 +
with message-id 
and subject line Bug#953487: fixed in runescape 0.7-1
has caused the Debian Bug report #953487,
regarding runescape: binaries for non-free not auto-built
to be marked as done.

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

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


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

Hi,

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

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

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: runescape
Source-Version: 0.7-1
Done: Carlos Donizete Froes 

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

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

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

Debian distribution maintenance software
pp.
Carlos Donizete Froes  (supplier of updated runescape 
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, 15 Mar 2020 16:52:37 -0300
Source: runescape
Architecture: source
Version: 0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Carlos Donizete Froes 
Closes: 953487 953714
Changes:
 runescape (0.7-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #953487, #953714)
   * debian/control:
 + Bumped Standards-Version to 4.5.0.
 + Added in Build-Depends: default-jdk-headless | default-jdk.
 + Added in Depends: default-jre-headless.
   * Added autopkgtest.
   * debian/copyright:
 + Copyright information organized for contacts.
 + Copyright updated for current years (2020).
   * Update debian/upstream/metadata years (2020).
Checksums-Sha1:
 410dce3fee4bf2a94317770718dc080c910a5f13 2205 runescape_0.7-1.dsc
 eb71e63c73a739783a91a599d2f42db9e6210380 627878 runescape_0.7.orig.tar.bz2
 4e492e9569c007bb2d27315dd71bfc468406a47d 12836 runescape_0.7-1.debian.tar.xz
 3b2fc474816330c45a0ee1962a6cd17bfe8fb1d3 7241 runescape_0.7-1_amd64.buildinfo
Checksums-Sha256:
 d8e829c51dd1e1cc7b6c656ba2ce27ab9a7d1f5ecc3407ae432c5634b39d638f 2205 
runescape_0.7-1.dsc
 db2cf90335dae027486e3d93cf81e88c27b121eaf37988dfc99a543e0de1f0e3 627878 
runescape_0.7.orig.tar.bz2
 caf36feee7711e830783e40ed79a66a36092a31715983130c9edeec501e9f2fc 12836 
runescape_0.7-1.debian.tar.xz
 f7ed225e9d1bbf050142221da1c3105cf82673c177dbae67f7e07f2a1244c113 7241 
runescape_0.7-1_amd64.buildinfo
Files:
 71a3fa70eb996cf05e97ba17e34ae5c9 2205 non-free/games optional 
runescape_0.7-1.dsc
 4e412f344cb9e21966ab1abfedb9bb95 627878 non-free/games optional 
runescape_0.7.orig.tar.bz2
 362f45db6a41951ae9aaf603f58ef554 12836 non-free/games optional 
runescape_0.7-1.debian.tar.xz
 2f7c55721f64856171038a658cf5bcca 7241 non-free/games optional 
runescape_0.7-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl6OSoJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk7ysP+wdFH+SG+oD20jAzHa8uYCxLf/uH8ZjjkykL
9jwbYzHrDFLFI8WhFdw2x3QpJeWZyiZIDMeeJwP4Qt0ijDpPyZlxzgfaOH1mz5KB
AMJS10t8P1teVbBskNx5DExLDL5Z5AehMrBkW13pIFiXU6MELBM7qDecdJ55k08F
R9yRiQkBBBIijX7uIzKqGwt5bubzpS6UUldShOxfSJaTqmYq3AmtW0gkNJm5LGq6
t8hEB3l2u3CCL2ViogNb1vyezILNpDmszkxu7H00rzOSEDlhnUJCdH1Ind6kFWsD
qlYnHl0GF7AOkGdAnmBTs8zAc748qQek5Eyum2mm1W2u05OX3lKbgGY/HH6JkLBp
MR1nksbbRKeiVmgZifFRrc7DEpJnpbdaDI+6cikAehljd1NMi3eU8XQWG31Njnw1
EC/J8cgLuYBlgXPBC8RItOq5RJWGXjcL0fEMQRBuqP1/HVRlK2esIWWvK7yJLGWP
McHMrw30SV9NkRJD4u1mt/clugiIZONpzAabaHssxvklz2pVWjlNN+2Z2YUWaQ8r
K7LcPu7/bDlZybeFQoNo/mqgg45QBxw2HmeJ57ee7XLI8VttMoqXE4rcxmI1xG8q
z3/gKGuCQI4j4XcgXSWBTSwbu5ZY2hibO+wG5MP5M982xDfxutrnf/cQ7T502BYu

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

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 22:20:28 +
with message-id 
and subject line Bug#953714: fixed in runescape 0.7-1
has caused the Debian Bug report #953714,
regarding src:runescape: 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.)


-- 
953714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: runescape
Version: 0.5-1
Severity: serious
Control: fixed -1 0.6-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:runescape in
its current version in unstable has been trying to migrate for 120 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=runescape




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: runescape
Source-Version: 0.7-1
Done: Carlos Donizete Froes 

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

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

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

Debian distribution maintenance software
pp.
Carlos Donizete Froes  (supplier of updated runescape 
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, 15 Mar 2020 16:52:37 -0300
Source: runescape
Architecture: source
Version: 0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Carlos Donizete Froes 
Closes: 953487 953714
Changes:
 runescape (0.7-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #953487, #953714)
   * debian/control:
 + Bumped Standards-Version to 4.5.0.
 + Added in Build-Depends: default-jdk-headless | default-jdk.
 + Added in Depends: default-jre-headless.
   * Added autopkgtest.
   * debian/copyright:
 + Copyright information organized for contacts.
 + Copyright updated for current years (2020).
   * Update debian/upstream/metadata years (2020).
Checksums-Sha1:
 410dce3fee4bf2a94317770718dc080c910a5f13 2205 runescape_0.7-1.dsc
 eb71e63c73a739783a91a599d2f42db9e6210380 627878 runescape_0.7.orig.tar.bz2
 4e492e9569c007bb2d27315dd71bfc468406a47d 12836 runescape_0.7-1.debian.tar.xz
 3b2fc474816330c45a0ee1962a6cd17bfe8fb1d3 7241 runescape_0.7-1_amd64.buildinfo
Checksums-Sha256:
 d8e829c51dd1e1cc7b6c656ba2ce27ab9a7d1f5ecc3407ae432c5634b39d638f 2205 
runescape_0.7-1.dsc
 db2cf90335dae027486e3d93cf81e88c27b121eaf37988dfc99a543e0de1f0e3 627878 
runescape_0.7.orig.tar.bz2
 caf36feee7711e830783e40ed79a66a36092a31715983130c9edeec501e9f2fc 12836 
runescape_0.7-1.debian.tar.xz
 f7ed225e9d1bbf050142221da1c3105cf82673c177dbae67f7e07f2a1244c113 7241 
runescape_0.7-1_amd64.buildinfo
Files:
 71a3fa70eb996cf05e97ba17e34ae5c9 2205 non-free/games optional 
runescape_0.7-1.dsc
 4e412f344cb9e21966ab1abfedb9bb95 627878 non-free/games 

Bug#890931: marked as done (golang-github-gopherjs-gopherjs FTBFS with golang-1.10-go: undefined: ___GOPHERJS_REQUIRES_GO_VERSION_1_9___)

[Debian Bug Tracking System]

Your message dated Wed, 8 Apr 2020 22:18:59 +0200 (CEST)
with message-id 

and subject line closing this bug
has caused the Debian Bug report #890931,
regarding golang-github-gopherjs-gopherjs FTBFS with golang-1.10-go: undefined: 
___GOPHERJS_REQUIRES_GO_VERSION_1_9___
to be marked as done.

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

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


-- 
890931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-gopherjs-gopherjs
Version: 0.0~git20170927.0.4152256-5
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-gopherjs-gopherjs.html

...
   dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170927.0.4152256/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170927.0.4152256/obj-x86_64-linux-gnu/src\"
 -v -p 15 github.com/gopherjs/gopherjs github.com/gopherjs/gopherjs/build 
github.com/gopherjs/gopherjs/compiler 
github.com/gopherjs/gopherjs/compiler/analysis 
github.com/gopherjs/gopherjs/compiler/astutil 
github.com/gopherjs/gopherjs/compiler/filter 
github.com/gopherjs/gopherjs/compiler/natives 
github.com/gopherjs/gopherjs/compiler/prelude 
github.com/gopherjs/gopherjs/compiler/typesutil 
github.com/gopherjs/gopherjs/internal/sysutil github.com/gopherjs/gopherjs/js 
github.com/gopherjs/gopherjs/nosync github.com/gopherjs/gopherjs/tests 
github.com/gopherjs/gopherjs/tests/main 
github.com/gopherjs/gopherjs/tests/otherpkg
github.com/gopherjs/gopherjs/tests
github.com/gopherjs/gopherjs/js
github.com/gopherjs/gopherjs/nosync
github.com/gopherjs/gopherjs/tests/otherpkg
github.com/gopherjs/gopherjs/compiler/prelude
github.com/gopherjs/gopherjs/tests/main
golang.org/x/crypto/ssh/terminal
golang.org/x/sys/unix
github.com/neelance/sourcemap
github.com/kisielk/gotool
github.com/gopherjs/gopherjs/compiler/astutil
github.com/gopherjs/gopherjs/compiler/typesutil
golang.org/x/tools/go/types/typeutil
github.com/gopherjs/gopherjs/compiler/vendor/github.com/neelance/astrewrite
golang.org/x/tools/go/gcimporter15
github.com/spf13/pflag
github.com/gopherjs/gopherjs/compiler/natives
github.com/gopherjs/gopherjs/compiler/analysis
github.com/gopherjs/gopherjs/compiler/filter
github.com/gopherjs/gopherjs/compiler
github.com/spf13/cobra
github.com/fsnotify/fsnotify
github.com/gopherjs/gopherjs/internal/sysutil
# github.com/gopherjs/gopherjs/compiler
src/github.com/gopherjs/gopherjs/compiler/compiler.go:20:9: undefined: 
___GOPHERJS_REQUIRES_GO_VERSION_1_9___
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170927.0.4152256/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-gopherjs-gopherjs-0.0\~git20170927.0.4152256/obj-x86_64-linux-gnu/src\"
 -v -p 15 github.com/gopherjs/gopherjs github.com/gopherjs/gopherjs/build 
github.com/gopherjs/gopherjs/compiler 
github.com/gopherjs/gopherjs/compiler/analysis 
github.com/gopherjs/gopherjs/compiler/astutil 
github.com/gopherjs/gopherjs/compiler/filter 
github.com/gopherjs/gopherjs/compiler/natives 
github.com/gopherjs/gopherjs/compiler/prelude 
github.com/gopherjs/gopherjs/compiler/typesutil 
github.com/gopherjs/gopherjs/internal/sysutil github.com/gopherjs/gopherjs/js 
github.com/gopherjs/gopherjs/nosync github.com/gopherjs/gopherjs/tests 
github.com/gopherjs/gopherjs/tests/main 
github.com/gopherjs/gopherjs/tests/otherpkg returned exit code 2
make: *** [debian/rules:4: binary] Error 2
--- End Message ---
--- Begin Message ---

Version: 0.0~git20170927.0.4152256-6

Manually closing this bug because I forgot to add a corresponding 
changelog entry in the latest upload.


  Thorsten--- End Message ---

Processed: Re: [Pkg-javascript-devel] Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #956238 [src:npm] npm: autopkgtest failures in arm64 and ppc64el
Severity set to 'important' from 'serious'

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

Bug#956238: [Pkg-javascript-devel] Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

[Xavier]

Control: severity -1 important

Le 08/04/2020 à 20:18, Gianfranco Costamagna a écrit :
> Source: npm
> Version: 6.13.4+ds-2
> Severity: serious
> 
> Hello, looks like probably since version 6.x, a new autopkgtest introduced 
> has been failing on arm64, ppc64el and s390x (this one happens in Ubuntu, but 
> should be reproducible in Debian too).
> 
> https://ci.debian.net/packages/n/npm/unstable/arm64/
> https://ci.debian.net/packages/n/npm/unstable/ppc64el/
> 
> Can you please have a look?
> 
> thanks
> 
> Gianfranco

Hi,

the problem is "address already in use :::56443". It's difficult to
enable network tests without reserved port on debci machines.

So it's not a really a bug

Processed: Re: Bug#956245: /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command.

[Debian Bug Tracking System]

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

> tags 956245 + patch
Bug #956245 [dkms] /etc/kernel/header_postinst.d/dkms: Error! You must be root 
to use this command.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#956245: /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command.

[Thorsten Glaser]

tags 956245 + patch
thanks

On Wed, 8 Apr 2020, Thorsten Glaser wrote:

> /etc/kernel/header_postinst.d/dkms:
> Error! You must be root to use this command.

This is caused by line 3178 of /usr/sbin/dkms:
((UID == 0)) && return

I am root, but $UID is 1000. Changing the line to…
[[ $(id -u) = 0 ]] && return
… makes it succeed.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#956245: /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command.

[Thorsten Glaser]

Package: dkms
Version: 2.6.1-4
Severity: grave
Justification: renders package unusable

After installing a package that needs DKMS, I also wanted to install
the kernel headers, to make it usable. I get:

[…]

Unpacking linux-headers-4.19.0-8-amd64 (4.19.98-1) ...
Selecting previously unselected package linux-headers-amd64.
Preparing to unpack .../linux-headers-amd64_4.19+105+deb10u3_amd64.deb ...
Unpacking linux-headers-amd64 (4.19+105+deb10u3) ...
Setting up linux-compiler-gcc-8-x86 (4.19.98-1) ...
Setting up linux-kbuild-4.19 (4.19.98-1) ...
Setting up linux-headers-4.19.0-8-common (4.19.98-1) ...
Setting up linux-headers-4.19.0-8-amd64 (4.19.98-1) ...
/etc/kernel/header_postinst.d/dkms:
Error! You must be root to use this command.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/header_postinst.d at 
/var/lib/dpkg/info/linux-headers-4.19.0-8-amd64.postinst line 11.
dpkg: error processing package linux-headers-4.19.0-8-amd64 (--configure):
 installed linux-headers-4.19.0-8-amd64 package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-amd64:
 linux-headers-amd64 depends on linux-headers-4.19.0-8-amd64; however:
  Package linux-headers-4.19.0-8-amd64 is not configured yet.

dpkg: error processing package linux-headers-amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-4.19.0-8-amd64
 linux-headers-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

Kernel: Linux 4.19.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages dkms depends on:
ii  build-essential  12.6
ii  coreutils8.30-3
ii  dpkg-dev 1.19.7
ii  gcc  4:8.3.0-1
ii  kmod 26-1
ii  make 4.2.1-1.2
ii  patch2.7.6-3+deb10u1

Versions of packages dkms recommends:
ii  fakeroot 1.23-1
iu  linux-headers-amd64  4.19+105+deb10u3
ii  lsb-release  10.2019051400
ii  sudo 1.8.27-1+deb10u2

Versions of packages dkms suggests:
ii  menu2.1.47+b1
pn  python3-apport  

-- no debconf information

Processed: Re: Bug#956205: gitlab: Problem installing 12.8.8-6

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187
Bug #956205 [gitlab] gitlab: Problem installing 12.8.8-6
Bug #953415 [gitlab] gitlab: Top-level selectors may not contain the parent 
selector "&"
Set Bug forwarded-to-address to 
'https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187'.
Set Bug forwarded-to-address to 
'https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187'.

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

Bug#956205: gitlab: Problem installing 12.8.8-6

[Pirate Praveen]

Control: forwarded -1 
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187

On 2020, ഏപ്രിൽ 8 8:08:34 PM IST, Pirate Praveen  
wrote:
>Control: merge 953415 -1
>
>On 2020, ഏപ്രിൽ 8 3:59:36 PM IST, David L 
>wrote:
>>rake aborted!
>>SassC::SyntaxError: Error: Top-level selectors may not contain the
>>parent selector "&".
>>on line 6:9 of
>node_modules/@gitlab/ui/src/scss/components.scss
>
>It is already known and work around documented in
>https://wiki.debian.org/gitlab (it is a good idea to check that page
>for known issues). Upstream sassc gem is still using an older version
>of libsass and sassc is failing to build on CentOS 6, so it is
>currently not easy to reproduce for gitlab upstream.

I have opened MR upstream to reproduce the issue 
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187 if they provide a 
patch, we can include it. For now, downgrade libsass.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Processed: tagging 944169 ...

[Debian Bug Tracking System]

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

> tags 944169 + fixed-upstream
Bug #944169 [open-ath9k-htc-firmware] open-ath9k-htc-firmware: non-standard 
gcc/g++ used for build (gcc-8)
Added tag(s) fixed-upstream.
> forwarded 944169 
> https://github.com/qca/open-ath9k-htc-firmware/commit/98373807cb3f3a5d268d04b9cebeda60c3c1e38c
Bug #944169 [open-ath9k-htc-firmware] open-ath9k-htc-firmware: non-standard 
gcc/g++ used for build (gcc-8)
Set Bug forwarded-to-address to 
'https://github.com/qca/open-ath9k-htc-firmware/commit/98373807cb3f3a5d268d04b9cebeda60c3c1e38c'.
> thanks
Stopping processing here.

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

Bug#955295: marked as done (photofilmstrip: incompatible with python 3.8?)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 19:05:02 +
with message-id 
and subject line Bug#955295: fixed in photofilmstrip 3.7.3-1
has caused the Debian Bug report #955295,
regarding photofilmstrip: incompatible with 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.)


-- 
955295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: photofilmstrip
Version: 3.7.2-2
Severity: serious

% photofilmstrip
Traceback (most recent call last):
  File "/usr/bin/photofilmstrip", line 8, in 
main()
  File "/usr/lib/python3/dist-packages/photofilmstrip/GUI.py", line 46, in main
guiApp.Start()
  File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 41, in 
Start
self.InitI18N()
  File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 31, in 
InitI18N
ActionI18N().Execute()
  File "/usr/lib/python3/dist-packages/photofilmstrip/action/ActionI18N.py", 
line 43, in Execute
lang.install(True)
  File "/usr/lib/python3.8/gettext.py", line 352, in install
for name in allowed & set(names):
TypeError: 'bool' object is not iterable


% photofilmstrip-cli  
Traceback (most recent call last):
  File "/usr/bin/photofilmstrip-cli", line 8, in 
main()
  File "/usr/lib/python3/dist-packages/photofilmstrip/CLI.py", line 44, in main
exitCode = cliApp.Start()
  File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 41, in 
Start
self.InitI18N()
  File "/usr/lib/python3/dist-packages/photofilmstrip/AppMixin.py", line 31, in 
InitI18N
ActionI18N().Execute()
  File "/usr/lib/python3/dist-packages/photofilmstrip/action/ActionI18N.py", 
line 43, in Execute
lang.install(True)
  File "/usr/lib/python3.8/gettext.py", line 352, in install
for name in allowed & set(names):
TypeError: 'bool' object is not iterable
--- End Message ---
--- Begin Message ---
Source: photofilmstrip
Source-Version: 3.7.3-1
Done: Philipp Huebner 

We believe that the bug you reported is fixed in the latest version of
photofilmstrip, 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.
Philipp Huebner  (supplier of updated photofilmstrip 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Apr 2020 20:52:14 +0200
Source: photofilmstrip
Architecture: source
Version: 3.7.3-1
Distribution: unstable
Urgency: high
Maintainer: Python Applications Packaging Team 

Changed-By: Philipp Huebner 
Closes: 955295
Changes:
 photofilmstrip (3.7.3-1) unstable; urgency=high
 .
   * New upstream version 3.7.3 (Closes: #955295)
Checksums-Sha1:
 a769b611fac7ce1b83e67a08af8d5d657b228d01 2131 photofilmstrip_3.7.3-1.dsc
 3536a226abe5e69a4f4078b778896fa6d295daaf 7237239 
photofilmstrip_3.7.3.orig.tar.gz
 1bee1a6c36155413c4ce9a56947caabe6e0851fb 3104 
photofilmstrip_3.7.3-1.debian.tar.xz
 01e83bc4280f5f31da85244607b6436896eea34a 8916 
photofilmstrip_3.7.3-1_amd64.buildinfo
Checksums-Sha256:
 f02ee27fb87d4c263f63dee5b9787265cebf1988f0b8bdbc47645d0a2cf06eaf 2131 
photofilmstrip_3.7.3-1.dsc
 f1cfa95fd7de6bf38dd832831bcd37761c7b24f20a890f287c1979a20577d679 7237239 
photofilmstrip_3.7.3.orig.tar.gz
 5e0cbf5af18f38e298f4e6cb2f3e6c91865970ec4e3e2fc2396b178bc90589b0 3104 
photofilmstrip_3.7.3-1.debian.tar.xz
 2c03898246098a37b1354b4435e5cf6d40052e52f30eb4e0358be03464fb71a8 8916 
photofilmstrip_3.7.3-1_amd64.buildinfo
Files:
 ca962ae966691563bea209c77b9384da 2131 video optional photofilmstrip_3.7.3-1.dsc
 ab61a461949fd0c37d12d18cbf532547 7237239 video optional 
photofilmstrip_3.7.3.orig.tar.gz
 813c7ebc154b40a202dd41cc0b34c627 3104 video optional 
photofilmstrip_3.7.3-1.debian.tar.xz
 8094b5f313118557df5dce8ee6c9ccad 8916 video optional 
photofilmstrip_3.7.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAl6OHnsVHGRlYmFsYW5j
ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0c+f4P/04GGngcK4UV0eHTYVz+PYk+zQ8s
GdQWVhbqsr1NJxEWCw8+bgmee/gMtH88H4gSzbQlTEsBjmXjjsy+UzLnA3GF7CY1

Bug#952048: marked as done (iem-plugin-suite: FTBFS: ../../../resources/Standalone/MyStandaloneFilterWindow.h:132:47: error: cannot convert ‘juce::AudioIODeviceType*’ to ‘std::unique_ptr

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 18:48:45 +
with message-id 
and subject line Bug#952048: fixed in iem-plugin-suite 1.11.1-1
has caused the Debian Bug report #952048,
regarding iem-plugin-suite: FTBFS: 
../../../resources/Standalone/MyStandaloneFilterWindow.h:132:47: error: cannot 
convert ‘juce::AudioIODeviceType*’ to ‘std::unique_ptr’
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.)


-- 
952048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iem-plugin-suite
Version: 1.11.0-2
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):
> g++  -MMD -DLINUX=1 -DNDEBUG=1 -DJUCE_USE_CUSTOM_PLUGIN_STANDALONE_APP=1 
> -DJUCER_LINUX_MAKE_6D53C8B4=1 -DJUCE_APP_VERSION=0.4.0 
> -DJUCE_APP_VERSION_HEX=0x400 -I/usr/include/freetype2 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libpng16 -pthread 
> -I/usr/share/juce/modules/juce_audio_processors/format_types/VST3_SDK 
> -I../../JuceLibraryCode -I/usr/share/juce/modules -I/usr/local/include 
> -I../../../resources/ -Wdate-time -D_FORTIFY_SOURCE=2 -DJUCE_JACK=1 
> -DDEBIAN_BUILD=1 -fPIC -O3 -flto -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
> -I/usr/include/libpng16 -std=c++14 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -DJucePlugin_Build_VST=1 -DJucePlugin_Build_VST3=0 
> -DJucePlugin_Build_AU=0 -DJucePlugin_Build_AUv3=0 -DJucePlugin_Build_RTAS=0 
> -DJucePlugin_Build_AAX=0 -DJucePlugin_Build_Standalone=1 
> -DJucePlugin_Build_Unity=0 -DJUCE_SHARED_CODE=1  -o 
> "build/intermediate/Release/StandaloneApp_2a979640.o" -c 
> "../../../resources/Standalone/StandaloneApp.cpp"
> In file included from 
> ../../../resources/Standalone/MyStandaloneFilterWindow.h:68,
>  from ../../../resources/Standalone/StandaloneApp.cpp:58:
> ../../../resources/Standalone/IEM_JackAudio.h:91:170: warning: extra ‘;’ 
> [-Wpedantic]
>91 | JUCE_DECL_JACK_FUNCTION (jack_client_t*, jack_client_open, (const 
> char* client_name, jack_options_t options, jack_status_t* status, ...), 
> (client_name, options, status));
>   |   
>   
>  ^
> ../../../resources/Standalone/IEM_JackAudio.h:92:84: warning: extra ‘;’ 
> [-Wpedantic]
>92 | JUCE_DECL_JACK_FUNCTION (int, jack_client_close, (jack_client_t 
> *client), (client));
>   |   
>  ^
> ../../../resources/Standalone/IEM_JackAudio.h:93:80: warning: extra ‘;’ 
> [-Wpedantic]
>93 | JUCE_DECL_JACK_FUNCTION (int, jack_activate, (jack_client_t* client), 
> (client));
>   |   
>  ^
> ../../../resources/Standalone/IEM_JackAudio.h:94:82: warning: extra ‘;’ 
> [-Wpedantic]
>94 | JUCE_DECL_JACK_FUNCTION (int, jack_deactivate, (jack_client_t* 
> client), (client));
>   |   
>^
> ../../../resources/Standalone/IEM_JackAudio.h:95:89: warning: extra ‘;’ 
> [-Wpedantic]
>95 | JUCE_DECL_JACK_FUNCTION (char*, jack_get_client_name, (jack_client_t* 
> client), (client));
>   |   
>   ^
> ../../../resources/Standalone/IEM_JackAudio.h:96:98: warning: extra ‘;’ 
> [-Wpedantic]
>96 | JUCE_DECL_JACK_FUNCTION (jack_nframes_t, jack_get_buffer_size, 
> (jack_client_t* client), (client));
>   |   
>^
> ../../../resources/Standalone/IEM_JackAudio.h:97:98: warning: extra ‘;’ 
> [-Wpedantic]
>97 | JUCE_DECL_JACK_FUNCTION (jack_nframes_t, jack_get_sample_rate, 
> (jack_client_t* client), (client));
>   |   
>^
> ../../../resources/Standalone/IEM_JackAudio.h:98:138: warning: extra ‘;’ 
> [-Wpedantic]
>98 | JUCE_DECL_VOID_JACK_FUNCTION (jack_on_shutdown, (jack_client_t* 
> client, void (*function)(void* arg), void* arg), (client, function, arg));
>   |   

Bug#955815: marked as done (intel-opencl-clang: requires a source-only upload)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 18:34:41 +
with message-id 
and subject line Bug#955815: fixed in intel-opencl-clang 10.0.0-2
has caused the Debian Bug report #955815,
regarding intel-opencl-clang: requires a source-only upload
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.)


-- 
955815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-opencl-clang
Version: 9.0.0-1
Severity: serious

intel-opencl-clang currently cannot migrate:

Not built on buildd: arch all binaries uploaded by tjaal...@ubuntu.com, a new 
source-only upload is needed to allow migration
Not built on buildd: arch amd64 binaries uploaded by tjaal...@ubuntu.com

Since this is includes an Arch: all binary package, a binNMU won't help
in this case. Please perform an source-only upload to fix this issue.

I also wonder why libopencl-clang-dev is an Arch: all binary in the
first place. It contains an architecture specific interface -- the
symlink to the shared library provided by libopencl-clang9.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: intel-opencl-clang
Source-Version: 10.0.0-2
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the latest version of
intel-opencl-clang, 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.
Timo Aaltonen  (supplier of updated intel-opencl-clang 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Apr 2020 21:11:04 +0300
Source: intel-opencl-clang
Architecture: source
Version: 10.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL team 
Changed-By: Timo Aaltonen 
Closes: 955815
Changes:
 intel-opencl-clang (10.0.0-2) unstable; urgency=medium
 .
   * control: Build -dev on amd64/i386 like the lib. (Closes: #955815)
Checksums-Sha1:
 382ed2adbb44d6652f99e75162acbf686b0a8a05 2228 intel-opencl-clang_10.0.0-2.dsc
 244fa91a38db4818f81edf4306bebcc411ed4162 4248 
intel-opencl-clang_10.0.0-2.debian.tar.xz
 5c07068331b22f01897d5ba6e1cfb042dec9fca9 7892 
intel-opencl-clang_10.0.0-2_source.buildinfo
Checksums-Sha256:
 9b68891e51d466d86e7d09dd201d9854d83fd521328d4a214d53bad0bb6d3915 2228 
intel-opencl-clang_10.0.0-2.dsc
 f48086783d9d3122c377a074f6fc6889246a3862f5b4cde3bb984dc549bb3672 4248 
intel-opencl-clang_10.0.0-2.debian.tar.xz
 d188d7d8f306a440c546c924a0786092a7caaa0a6468786c71619e569621 7892 
intel-opencl-clang_10.0.0-2_source.buildinfo
Files:
 e2cc083f1025dd2160df7bb4a4de88d9 2228 libs optional 
intel-opencl-clang_10.0.0-2.dsc
 d35ddcf6459a2efda0aa7232ee468da4 4248 libs optional 
intel-opencl-clang_10.0.0-2.debian.tar.xz
 c26f6d1a3a17dc7c934ffe334ac048df 7892 libs optional 
intel-opencl-clang_10.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl6OE8cACgkQy3AxZaiJ
hNyOWA/+LkSKGR7gv3eJFDgy+hbucemnQV3mkfw2i6dShznUxRTvSqFLyIIvTdPr
ZBHTbqhB+RTgvRFRjYnnJ7Cas2x61CX8K3Jr05abFosucJZw5V8JNBc+T3T5MxSp
zmf/knUHcCVRmzjnru7AY8AUzbEHwbORWh+r8KXCLw1ESKbVU4fU/CDpDIrEd7Lv
P93luR8wlB/vuVNSLqOoQnl4SO2J3/J2T58WS0VpSHBrnX4MS3Ck594I8vn/IkJW
/eFp/lrCEbgpSmD6nenHvr7bht7cslrtN3XWZpuukT42VReFzmzHhP0jZiph4t2i
QdGvi5nJ4gSiE6jT9Naa1JQ2Uc3FAyKFjemkGVX7SH1fSdz5M25/ytexmjcHkZkc
zBK+OMsI4egk/AmQp13b6R3YJHa3FwPkVjQxJGs18/pkNnLwtcDlogi/kLDPJMHn
SIyIGu2sFvmnh8Z8y5fWSu+UbIsZTz1T1ogPdXM8m6iz0p5rme9dOChKb+wIDV/Y
12So9hI4H9Ujfn79fjIGuKYUsosxhc2S4/ad8EhEbjIAr3OVMLv2aAISkw4EJVpC
NhxbED8yifqPEYdz5dP/06NaYduCWFYcay30LhSwEIM2EKKAeELnOyX95/VNXFHd
/FakdOV3pdG6YhB7L5e2pPcfnUMClrhO8V4v2Oj3GNc2jZiCzVM=
=pzgr
-END PGP SIGNATURE End Message ---

Bug#955858: gparted: does not start, 'unable to init server', tmp.mount does not exist

[Phillip Susi]

Kyle B writes:

> (gpartedbin:11049): Gtk-WARNING **: 09:04:39.901: cannot open display:

What display server / desktop environment are you using?

Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

[Gianfranco Costamagna]

Source: npm
Version: 6.13.4+ds-2
Severity: serious

Hello, looks like probably since version 6.x, a new autopkgtest introduced has 
been failing on arm64, ppc64el and s390x (this one happens in Ubuntu, but 
should be reproducible in Debian too).

https://ci.debian.net/packages/n/npm/unstable/arm64/
https://ci.debian.net/packages/n/npm/unstable/ppc64el/

Can you please have a look?

thanks

Gianfranco

Bug#952250: marked as done (ecb: FTBFS: mv: cannot stat 'html-help/index.html': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 17:51:18 +
with message-id 
and subject line Bug#952250: fixed in ecb 2.50+git20170628-1
has caused the Debian Bug report #952250,
regarding ecb: FTBFS: mv: cannot stat 'html-help/index.html': 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.)


-- 
952250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ecb
Version: 2.40+git20140216-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> Makefile:38: Makefile.conf not found. Using defaults for Linux!
> Makefile:39: Create Makefile.conf from Makefile.conf.template to override the 
> defaults.
> Byte-compiling ECB with LOADPATH= ...
> emacs -batch -no-site-file -l ecb-compile-script --eval '(ecb-byte-compile t)'
> Compiler-macro error for cl-typep: (error "Unknown type button-release-event")
> Compiler-macro error for cl-typep: (error "Unknown type button-press-event")
> ECB 2.40 uses CEDET 2.0 (contains semantic 2.2, eieio 1.4, speedbar 1.0).
> Compiler-macro error for cl-typep: (error "Unknown type button-release-event")
> Compiler-macro error for cl-typep: (error "Unknown type button-press-event")
> tree-buffer.el: Missing value for option `t' of slot `modeline-menu-creator' 
> in struct tree-buffer-spec!
> tree-buffer.el:   I'll take `:read-only' to be an option rather than a 
> default value.
> tree-buffer.el: Missing value for option `t' of slot `sticky-parent-p' in 
> struct tree-buffer-spec!
> tree-buffer.el:   I'll take `:read-only' to be an option rather than a 
> default value.
> tree-buffer.el: Missing value for option `t' of slot `sticky-indent-string' 
> in struct tree-buffer-spec!
> tree-buffer.el:   I'll take `:read-only' to be an option rather than a 
> default value.
> tree-buffer.el: Missing value for option `t' of slot `sticky-parent-fn' in 
> struct tree-buffer-spec!
> tree-buffer.el:   I'll take `:read-only' to be an option rather than a 
> default value.
> tree-buffer.el: Missing value for option `t' of slot 
> `reduce-tree-for-incr-search-fn' in struct tree-buffer-spec!
> tree-buffer.el:   I'll take `:read-only' to be an option rather than a 
> default value.
> ecb-navigate.el: Obsolete name arg "node" to constructor ecb-dlist-node
> ecb-navigate.el: Obsolete name arg "First item" to constructor 
> ecb-nav-history-item
> ecb-navigate.el: Obsolete name arg "First item" to constructor 
> ecb-nav-history-item
> All requirements for ECB 2.40 fulfilled - Enjoy it!
> ‘defmethod’ is an obsolete macro (as of 25.1); use ‘cl-defmethod’ instead.
> ‘defgeneric’ is an obsolete macro (as of 25.1); use ‘cl-defgeneric’ instead.
> ‘defmethod’ is an obsolete macro (as of 25.1); use ‘cl-defmethod’ instead.
> ‘defgeneric’ is an obsolete macro (as of 25.1); use ‘cl-defgeneric’ instead.
> 
> In toplevel form:
> ecb-analyse.el:362:4:Warning: ‘call-next-method’ is an obsolete function (as
> of 25.1); use ‘cl-call-next-method’ instead.
> ‘defmethod’ is an obsolete macro (as of 25.1); use ‘cl-defmethod’ instead.
> ‘defgeneric’ is an obsolete macro (as of 25.1); use ‘cl-defgeneric’ instead.
> ecb-analyse.el:370:4:Warning: ‘call-next-method’ is an obsolete function (as
> of 25.1); use ‘cl-call-next-method’ instead.
> 
> In toplevel form:
> ecb-face.el:131:1:Warning: defcustom for ‘ecb-tree-guide-line-face’ fails to
> specify type
> ecb-face.el:131:1:Warning: defcustom for ‘ecb-tree-guide-line-face’ fails to
> specify type
> 
> In ecb-display-buffer-xemacs:
> ecb-layout.el:2002:37:Warning: ‘display-buffer-function’ is an obsolete
> variable (as of 24.3); use ‘display-buffer-alist’ instead.
> ecb-layout.el:2051:23:Warning: ‘display-buffer-function’ is an obsolete
> variable (as of 24.3); use ‘display-buffer-alist’ instead.
> ecb-layout.el:2235:40:Warning: ‘display-buffer-function’ is an obsolete
> variable (as of 24.3); use ‘display-buffer-alist’ instead.
> ecb-layout.el:2115:44:Warning: ‘special-display-function’ is an obsolete
> variable (as of 24.3); use ‘display-buffer-alist’ instead.
> ecb-layout.el:2097:38:Warning: ‘special-display-buffer-names’ is an obsolete
> variable (as of 24.3); use ‘display-buffer-alist’ instead.
> ecb-layout.el:2097:38:Warning: ‘special-display-function’ is an obsolete
> variable (as of 24.3); use ‘display-buffer-alist’ instead.
> 

Bug#952055: paulstretch: FTBFS: XMLwrapper.cpp:32:26: error: invalid use of incomplete type ‘mxml_node_t’ {aka ‘struct _mxml_node_s’}

[Sudip Mukherjee]

Hi,

I have raised a merge request to fix this issue. This is an issue due to
change in mxml.

https://salsa.debian.org/multimedia-team/paulstretch/-/merge_requests/1

Note: I could not test it, I am getting segfaults even with 2.2-2-4.


--
Regards
Sudip

Bug#953952: kmod: libkmod2-udeb contains binary instead of libraries

[Aurelien Jarno]

On 2020-04-05 02:21, Marco d'Itri wrote:
> On Mar 15, Aurelien Jarno  wrote:
> 
> > The kmod binaries are actually the one being used, so yes please add a
> > kmod-udeb.
> Does it look good to you?
> 
> https://salsa.debian.org/md/kmod/-/commit/801ce705d39efdae9411192b1c33aee8ad522cc7
> 
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./bin/
> -rwxr-xr-x root/root121656 2020-04-05 02:14 ./bin/kmod
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./etc/
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./etc/modprobe.d/
> -rw-r--r-- root/root   246 2020-04-05 02:14 ./etc/modprobe.d/aliases.conf
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./sbin/
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./bin/lsmod -> kmod
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/depmod -> /bin/kmod
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/insmod -> /bin/kmod
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/lsmod -> /bin/kmod
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/modinfo -> /bin/kmod
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/modprobe -> /bin/kmod
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./sbin/rmmod -> /bin/kmod
> 
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./usr/
> drwxr-xr-x root/root 0 2020-04-05 02:14 ./usr/lib/
> -rw-r--r-- root/root 76504 2020-04-05 02:14 ./usr/lib/libkmod.so.2.3.5
> lrwxrwxrwx root/root 0 2020-04-05 02:14 ./usr/lib/libkmod.so.2 -> 
> libkmod.so.2.3.5
> 
>  Package: kmod-udeb
>  Source: kmod
>  Version: 27-3
>  Architecture: amd64
>  Maintainer: Marco d'Itri 
>  Installed-Size: 133
>  Depends: libc6-udeb (>= 2.30)
>  Section: debian-installer
>  Priority: important
>  Description: libkmod shared library
>   This is a minimal version of kmod, only for use in the installation system.
> 
>  Package: libkmod2-udeb
>  Source: kmod
>  Version: 27-3
>  Architecture: amd64
>  Maintainer: Marco d'Itri 
>  Installed-Size: 80
>  Depends: libc6-udeb (>= 2.30)
>  Section: debian-installer
>  Priority: important
>  Description: libkmod shared library
>   This is a minimal version of libkmod2, only for use in the installation 
> system.
> 

Yep, that looks all good, thanks a lot.

Regards,
Aurelien

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


signature.asc
Description: PGP signature

Processed: bug 956229 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=132313

[Debian Bug Tracking System]

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

> forwarded 956229 https://rt.cpan.org/Ticket/Display.html?id=132313
Bug #956229 [src:libtickit-widget-floatbox-perl] FTBFS: test failures
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=132313'.
> thanks
Stopping processing here.

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

Bug#956229: FTBFS: test failures

[gregor herrmann]

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-

Processed (with 1 error): Re: Bug#940656: [Pkg-privacy-maintainers] Bug#940656: black screen after upgrade

[Debian Bug Tracking System]

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

> close 940656
Bug #940656 [torbrowser-launcher] torbrowser-launcher: Torbrowser downloads but 
apparmor stops from running, xfce
Marked Bug as done
> forcemerge 940656 942901
Bug #940656 {Done: Roger Shimizu } 
[torbrowser-launcher] torbrowser-launcher: Torbrowser downloads but apparmor 
stops from running, xfce
Bug #942901 {Done: Roger Shimizu } [torbrowser-launcher] 
torbrowser-launcher: Tor Browser 9.0 shows only black screens due to no write 
access to /dev/shm/org.mozilla.ipc.*.*
Failed to forcibly merge 940656: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

>
End of message, stopping processing here.

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

Processed (with 1 error): Re: Bug#940656: [Pkg-privacy-maintainers] Bug#940656: black screen after upgrade

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 942901
Bug #940656 [torbrowser-launcher] torbrowser-launcher: Torbrowser downloads but 
apparmor stops from running, xfce
Bug #942901 {Done: Roger Shimizu } [torbrowser-launcher] 
torbrowser-launcher: Tor Browser 9.0 shows only black screens due to no write 
access to /dev/shm/org.mozilla.ipc.*.*
Failed to forcibly merge 940656: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.


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

Processed: tagging 956211

[Debian Bug Tracking System]

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

> tags 956211 + wontfix
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) wontfix.
> 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#956152: rabbitmq-server: fails to install reliably on arm64

[Thomas Goirand]

On 4/7/20 10:35 PM, Paul Gevers wrote:
> Package: rabbitmq-server
> Version: 3.7.18-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky breaks
> Control: affects -1 mcollective
> 
> Dear maintainer(s),
> 
> As can be seen in the autopkgtests of mcollective [1], rabbitmq-server
> fails to reliably install on arm64 as it often fails to start.
> 
> Paul
> 
> [1] https://ci.debian.net/packages/m/mcollective/testing/arm64/
> 
> https://ci.debian.net/data/autopkgtest/testing/arm64/m/mcollective/4853115/log.gz
> 
> Setting up rabbitmq-server (3.7.18-1) ...
> Adding group `rabbitmq' (GID 109) ...
> Done.
> Adding system user `rabbitmq' (UID 107) ...
> Adding new user `rabbitmq' (UID 107) with group `rabbitmq' ...
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be
> preloaded (cannot open shared object file): ignored.
> Not creating home directory `/var/lib/rabbitmq'.
> Created symlink
> /etc/systemd/system/multi-user.target.wants/rabbitmq-server.service →
> /lib/systemd/system/rabbitmq-server.service.
> Job for rabbitmq-server.service failed because the control process
> exited with error code.
> See "systemctl status rabbitmq-server.service" and "journalctl -xe" for
> details.
> invoke-rc.d: initscript rabbitmq-server, action "start" failed.
> ● rabbitmq-server.service - RabbitMQ Messaging Server
>  Loaded: loaded (/lib/systemd/system/rabbitmq-server.service;
> enabled; vendor preset: enabled)
>  Active: activating (auto-restart) (Result: exit-code) since Mon
> 2020-04-06 20:55:24 UTC; 7ms ago
> Process: 2726 ExecStart=/usr/sbin/rabbitmq-server (code=exited,
> status=1/FAILURE)
>Main PID: 2726 (code=exited, status=1/FAILURE)
> dpkg: error processing package rabbitmq-server (--configure):
>  installed rabbitmq-server package post-installation script subprocess
> returned error exit status 1
> dpkg: dependency problems prevent configuration of autopkgtest-satdep:
>  autopkgtest-satdep depends on rabbitmq-server; however:
>   Package rabbitmq-server is not configured yet.
> 
> dpkg: error processing package autopkgtest-satdep (--configure):
>  dependency problems - leaving unconfigured
> 

Hi Paul,

How may I test installing rabbitmq-server on ARM64 ? I don't have such a
hardware...

Cheers,

Thomas Goirand (zigo)

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

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 16:03:49 +
with message-id 
and subject line Bug#937602: fixed in python-bcrypt 3.1.7-3
has caused the Debian Bug report #937602,
regarding python-bcrypt: 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.)


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

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-bcrypt
Source-Version: 3.1.7-3
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
python-bcrypt, 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-bcrypt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Apr 2020 11:44:03 -0400
Source: python-bcrypt
Architecture: source
Version: 3.1.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937602
Changes:
 python-bcrypt (3.1.7-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937602
Checksums-Sha1:
 414d8cfbf0c7d7a2e218dd84c4e48e742866eea4 2180 python-bcrypt_3.1.7-3.dsc
 4aca32b5cb6cf08c4e575cc33d2bf47fd5213703 14408 
python-bcrypt_3.1.7-3.debian.tar.xz
 bee350e45a0777cce22316a689a25fc7ac6796c7 7351 
python-bcrypt_3.1.7-3_source.buildinfo
Checksums-Sha256:
 6145e9cb23dc0adfc1b3ecb3d743918317d17b068c508215a4139115248838d1 2180 
python-bcrypt_3.1.7-3.dsc
 d828e852c2ce6a46cc6a5860cd28b6aa48191fb2bb5f688ef3559a95acf23c8b 14408 
python-bcrypt_3.1.7-3.debian.tar.xz
 2768256f4db38d308b221939de70b94c298330773ed27dd78490f61d6ef7a0f1 7351 
python-bcrypt_3.1.7-3_source.buildinfo
Files:
 

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

[Jérémy Lal]

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.

Jérémy

Bug#939951: Link upstream bug

[Ross Gammon]

forwarded 939951 https://github.com/kupferlauncher/keybinder/issues/16
thanks

Looks like upstream have committed a fix, but have not confirmed it by
closing the issue.

Ross

Processed: Link upstream bug

[Debian Bug Tracking System]

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

> forwarded 939951 https://github.com/kupferlauncher/keybinder/issues/16
Bug #939951 [src:keybinder-3.0] keybinder-3.0: fails to build with gtk-doc 1.32
Set Bug forwarded-to-address to 
'https://github.com/kupferlauncher/keybinder/issues/16'.
> thanks
Stopping processing here.

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

Processed: Bug#937602 marked as pending in python-bcrypt

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#937602: marked as pending in python-bcrypt

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #937602 in python-bcrypt 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-bcrypt/-/commit/202ffda4dc75ce2b1407a1eb381cc291ce3b5ae5


Drop python2 support; Closes: #937602


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937602

Processed: py2removal bugs severity updates - 2020-04-08 15:36:22.582420+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-gobject-2 is a module and has 0 external rdeps or not in testing
> # python-gobject-2-dev is a module and has 0 external rdeps or not in testing
> # python-gobject is a module and has 0 external rdeps or not in testing
> severity 937447 serious
Bug #937447 [src:pygobject-2] pygobject-2: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-bcrypt is a module and has 0 external rdeps or not in testing
> severity 937602 serious
Bug #937602 [src:python-bcrypt] python-bcrypt: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#948206: mitmproxy incompatible with python3-wsproto=0.15.0-2

[Andrej Shadura]

On 08/04/2020 16:58, Andrej Shadura wrote:
Uploading an NMU to DELAYED/0, including the upstream fix and two 
clean-up commits from the Janitor.


Sorry, I intended to upload it to DELAYED/1 but was hit by an off-by-one 
error.


--
Cheers,
  Andrej

Bug#952060: libsignon-glib: diff for NMU version 1.12-2.1

[Aurélien COUDERC]

Le 07/04/2020 à 09:52, Adrian Bunk a écrit :
> Control: tags 952060 + patch
> Control: tags 952060 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for libsignon-glib (versioned as 1.12-2.1) and 
> uploaded it to DELAYED/15. Please feel free to tell me if I should 
> cancel it.

Applied in git [1], thanks !

[1] https://salsa.debian.org/qt-kde-team/3rdparty/libsignon-glib


Happy hacking,
--
Aurélien

Bug#948206: marked as done (mitmproxy incompatible with python3-wsproto=0.15.0-2)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 15:03:48 +
with message-id 
and subject line Bug#948206: fixed in mitmproxy 4.0.4-6.1
has caused the Debian Bug report #948206,
regarding mitmproxy incompatible with python3-wsproto=0.15.0-2
to be marked as done.

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

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


-- 
948206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 4.0.4-6
Severity: grave
Tags: newcomer
Justification: renders package unusable

After upgrading python3-wsproto to version 0.15.0-2, mitmproxy fails
immediately with this error message:

ImportError: cannot import name 'WSConnection' from 'wsproto.connection'
(/usr/lib/python3/dist-packages/wsproto/connection.py)

As stated in the setup.py of mitmproxy, it requires the Python
module wsproto to be at least 0.14.0 and < 0.15.0 [1]:

"wsproto>=0.14.0,<0.15.0",

Downgrading the package with `apt install python3-wsproto=0.11.0-3` solves
this issue temporarily (this version is shown below).

[1] 
https://github.com/mitmproxy/mitmproxy/blob/7b638f1b6b543ec5e23170217a42ca0e5c421992/setup.py#L85


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

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

Versions of packages mitmproxy depends on:
ii  dpkg  1.19.7
ii  fonts-font-awesome5.0.10+really4.7.0~dfsg-1
ii  python3   3.7.5-3
ii  python3-blinker   1.4+dfsg1-0.3
ii  python3-brotli1.0.7-6
ii  python3-certifi   2019.11.28-1
ii  python3-click 7.0-3
ii  python3-cryptography  2.6.1-4
ii  python3-h11   0.8.1-2
ii  python3-h23.0.1-5
ii  python3-hyperframe5.2.0-4
ii  python3-kaitaistruct  0.8-3
ii  python3-ldap3 2.4.1-2
ii  python3-openssl   19.0.0-1
ii  python3-passlib   1.7.1-1
ii  python3-pkg-resources 41.4.0-1
ii  python3-pyasn10.4.2-3
ii  python3-pyparsing 2.4.2-1
ii  python3-pyperclip 1.7.0-1
ii  python3-ruamel.yaml   0.15.89-3+b1
ii  python3-sortedcontainers  2.1.0-2
ii  python3-tornado   6.0.3+really5.1.1-2
ii  python3-urwid 2.0.1-2+b2
ii  python3-wsproto   0.11.0-3

mitmproxy recommends no packages.

mitmproxy suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 4.0.4-6.1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mitmproxy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Apr 2020 16:47:13 +0200
Source: mitmproxy
Architecture: source
Version: 4.0.4-6.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Andrej Shadura 
Closes: 948206
Changes:
 mitmproxy (4.0.4-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Debian Janitor ]
   * Update standards version, no changes needed.
   * Bump debhelper from old 9 to 12.
 .
   [ Andrej Shadura ]
   * Apply an upstream patch for wsproto 0.13 compatibility (Closes: #948206)
Checksums-Sha1:
 85d10923bb50d2bc645ea30c67f3f333b22b1f99 2287 mitmproxy_4.0.4-6.1.dsc
 645128b4b7369f4eed1a7576b4eccfd68fd24f68 14060 
mitmproxy_4.0.4-6.1.debian.tar.xz
Checksums-Sha256:
 059f1231e9667584b8ddae670db1d0edb4236cdee4436ba3c6c983f3cccb760e 2287 
mitmproxy_4.0.4-6.1.dsc
 72d3cc4a73885772643d3d18ca258844e107075ee1ad1de5d8b86d6af6905ac0 14060 
mitmproxy_4.0.4-6.1.debian.tar.xz
Files:
 474273a3ef507843341ad1bc23374293 2287 net optional mitmproxy_4.0.4-6.1.dsc
 7879824aca8912575c10190c4e8ee0e2 14060 net optional 

Bug#952064: marked as done (labrea: FTBFS: ../inc/pcaputil.h:18:10: error: conflicting types for ‘pcap_open’)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 15:03:38 +
with message-id 
and subject line Bug#952064: fixed in labrea 2.5-stable-3.1
has caused the Debian Bug report #952064,
regarding labrea: FTBFS: ../inc/pcaputil.h:18:10: error: conflicting types for 
‘pcap_open’
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.)


-- 
952064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: labrea
Version: 2.5-stable-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):
> if gcc -DHAVE_CONFIG_H -I. -I. -I..  -I../inc -I- -I/usr/include 
> -I/usr/include   -Wall -g -O2 -Wall -MT labrea_init.o -MD -MP -MF 
> ".deps/labrea_init.Tpo" \
>   -c -o labrea_init.o `test -f 'labrea_init.c' || echo './'`labrea_init.c; \
> then mv -f ".deps/labrea_init.Tpo" ".deps/labrea_init.Po"; \
> else rm -f ".deps/labrea_init.Tpo"; exit 1; \
> fi
> cc1: note: obsolete option ‘-I-’ used, please use ‘-iquote’ instead
> In file included from labrea_init.c:51:
> ../inc/pcaputil.h:18:10: error: conflicting types for ‘pcap_open’
>18 | pcap_t * pcap_open(char *device);
>   |  ^
> In file included from /usr/include/pcap.h:43,
>  from ../inc/pcaputil.h:12,
>  from labrea_init.c:51:
> /usr/include/pcap/pcap.h:859:18: note: previous declaration of ‘pcap_open’ 
> was here
>   859 | PCAP_API pcap_t *pcap_open(const char *source, int snaplen, int flags,
>   |  ^
> labrea_init.c: In function ‘build_bpf_filter’:
> labrea_init.c:126:20: warning: pointer targets in passing argument 1 of 
> ‘strlen’ differ in signedness [-Wpointer-sign]
>   126 |   int len = strlen(texpr);
>   |^
>   ||
>   |u_char * {aka unsigned char *}
> In file included from labrea_init.c:29:
> /usr/include/string.h:385:35: note: expected ‘const char *’ but argument is 
> of type ‘u_char *’ {aka ‘unsigned char *’}
>   385 | extern size_t strlen (const char *__s)
>   |   ^~~
> labrea_init.c:130:15: warning: pointer targets in passing argument 1 of 
> ‘strlcpy’ differ in signedness [-Wpointer-sign]
>   130 |   if (strlcpy(p, chunk, len) >= len) {
>   |   ^
>   |   |
>   |   u_char * {aka unsigned char *}
> In file included from labrea_init.c:26:
> ../config.h:123:17: note: expected ‘char *’ but argument is of type ‘u_char 
> *’ {aka ‘unsigned char *’}
>   123 | size_t  strlcpy(char *, const char *, size_t);
>   | ^~
> labrea_init.c:130:18: warning: pointer targets in passing argument 2 of 
> ‘strlcpy’ differ in signedness [-Wpointer-sign]
>   130 |   if (strlcpy(p, chunk, len) >= len) {
>   |  ^
>   |  |
>   |  const u_char * {aka const unsigned char *}
> In file included from labrea_init.c:26:
> ../config.h:123:25: note: expected ‘const char *’ but argument is of type 
> ‘const u_char *’ {aka ‘const unsigned char *’}
>   123 | size_t  strlcpy(char *, const char *, size_t);
>   | ^~~~
> labrea_init.c: In function ‘read_number’:
> labrea_init.c:165:16: warning: pointer targets in passing argument 2 of 
> ‘strlcpy’ differ in signedness [-Wpointer-sign]
>   165 |   strlcpy(buf, p, sizeof(buf)); /* Copy, watching for buffer 
> overflow */
>   |^
>   ||
>   |u_char * {aka unsigned char *}
> In file included from labrea_init.c:26:
> ../config.h:123:25: note: expected ‘const char *’ but argument is of type 
> ‘u_char *’ {aka ‘unsigned char *’}
>   123 | size_t  strlcpy(char *, const char *, size_t);
>   | ^~~~
> labrea_init.c: In function ‘labrea_init’:
> labrea_init.c:375:28: warning: pointer targets in passing argument 1 of 
> ‘read_number’ differ in signedness [-Wpointer-sign]
>   375 |  io.intf_num = read_number(optarg);
>   |^~
>   ||
>   |char *
> labrea_init.c:159:22: note: expected ‘u_char *’ {aka ‘unsigned char *’} but 
> argument is of type ‘char *’
>   159 | read_number (u_char *p)
>   |  ^
> labrea_init.c:423:38: warning: pointer targets in passing argument 1 of 
> 

Bug#952060: marked as pending in libsignon-glib

[Aurélien Couderc]

Control: tag -1 pending

Hello,

Bug #952060 in libsignon-glib 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/qt-kde-team/3rdparty/libsignon-glib/-/commit/4b03ce137b10f1663e944e758ff7e6ec8986d7f3


NMU: Don't build with -Werror. (Closes: #952060) Thanks Adrian Bunk


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952060

Processed: Bug#952060 marked as pending in libsignon-glib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952060 [src:libsignon-glib] libsignon-glib: FTBFS: 
signon-auth-service.c:72:13: error: G_ADD_PRIVATE [-Werror]
Ignoring request to alter tags of bug #952060 to the same tags previously set

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

Bug#948206: mitmproxy incompatible with python3-wsproto=0.15.0-2

[Andrej Shadura]

On Sun, 05 Jan 2020 11:27:14 +0100 Adrian Vollmer 
 wrote:

Package: mitmproxy
Version: 4.0.4-6
Severity: grave
Tags: newcomer
Justification: renders package unusable

After upgrading python3-wsproto to version 0.15.0-2, mitmproxy fails
immediately with this error message:

ImportError: cannot import name 'WSConnection' from 'wsproto.connection'
(/usr/lib/python3/dist-packages/wsproto/connection.py)

As stated in the setup.py of mitmproxy, it requires the Python
module wsproto to be at least 0.14.0 and < 0.15.0 [1]:

"wsproto>=0.14.0,<0.15.0",

Downgrading the package with `apt install python3-wsproto=0.11.0-3` solves
this issue temporarily (this version is shown below).

[1] 
https://github.com/mitmproxy/mitmproxy/blob/7b638f1b6b543ec5e23170217a42ca0e5c421992/setup.py#L85


Uploading an NMU to DELAYED/0, including the upstream fix and two 
clean-up commits from the Janitor.


--
Cheers,
  Andrej
diff --git a/debian/changelog b/debian/changelog
index 24243762..37c4ef68 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+mitmproxy (4.0.4-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Debian Janitor ]
+  * Update standards version, no changes needed.
+  * Bump debhelper from old 9 to 12.
+
+  [ Andrej Shadura ]
+  * Apply an upstream patch for wsproto 0.13 compatibility (Closes: #948206)
+
+ -- Andrej Shadura   Wed, 08 Apr 2020 16:47:13 +0200
+
 mitmproxy (4.0.4-6) unstable; urgency=medium
 
   * Fix symlinks to fontawesome (Closes: #928749)
diff --git a/debian/compat b/debian/compat
deleted file mode 100644
index ec635144..
--- a/debian/compat
+++ /dev/null
@@ -1 +0,0 @@
-9
diff --git a/debian/control b/debian/control
index d6b82dc9..0e09f57f 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: mitmproxy
 Section: net
 Priority: optional
 Maintainer: Sebastien Delafond 
-Build-Depends: debhelper (>= 9), dh-python, python3, python3-setuptools,
+Build-Depends: dh-python, python3, python3-setuptools,
  pandoc,
  python3-blinker (>= 1.4),
  python3-brotli (>= 0.7.0),
@@ -27,8 +27,9 @@ Build-Depends: debhelper (>= 9), dh-python, python3, 
python3-setuptools,
  python3-sortedcontainers (>= 1.5.4),
  python3-tornado (>= 4.3),
  python3-urwid (>= 2.0.1),
- python3-wsproto (>= 0.11.0)
-Standards-Version: 4.3.0
+ python3-wsproto (>= 0.13.0),
+ debhelper-compat (= 12)
+Standards-Version: 4.4.0
 Vcs-Git: https://salsa.debian.org/debian/mitmproxy.git
 Vcs-Browser: https://salsa.debian.org/debian/mitmproxy
 Homepage: https://mitmproxy.org
diff --git a/debian/patches/0006-update-to-wsproto-0.13.patch 
b/debian/patches/0006-update-to-wsproto-0.13.patch
new file mode 100644
index ..15e71c27
--- /dev/null
+++ b/debian/patches/0006-update-to-wsproto-0.13.patch
@@ -0,0 +1,191 @@
+From: rpigott 
+Date: Sun, 27 Jan 2019 00:59:26 -0800
+Subject: update to wsproto 0.13
+
+Origin: upstream, https://github.com/mitmproxy/mitmproxy/commit/106948d99
+Bug-Debian: http://bugs.debian.org/948206
+Applied-Upstream: yes
+
+---
+ mitmproxy/proxy/protocol/websocket.py | 87 +--
+ setup.py  |  2 +-
+ 2 files changed, 44 insertions(+), 45 deletions(-)
+
+diff --git a/mitmproxy/proxy/protocol/websocket.py 
b/mitmproxy/proxy/protocol/websocket.py
+index 0d1964a..591bae7 100644
+--- a/mitmproxy/proxy/protocol/websocket.py
 b/mitmproxy/proxy/protocol/websocket.py
+@@ -4,8 +4,9 @@ from OpenSSL import SSL
+ 
+ 
+ import wsproto
+-from wsproto import events
+-from wsproto.connection import ConnectionType, WSConnection
++from wsproto import events, WSConnection
++from wsproto.connection import ConnectionType
++from wsproto.events import AcceptConnection, CloseConnection, Message, Ping, 
Request
+ from wsproto.extensions import PerMessageDeflate
+ 
+ from mitmproxy import exceptions
+@@ -56,47 +57,44 @@ class WebSocketLayer(base.Layer):
+ if 'Sec-WebSocket-Extensions' in handshake_flow.response.headers:
+ if PerMessageDeflate.name in 
handshake_flow.response.headers['Sec-WebSocket-Extensions']:
+ extensions = [PerMessageDeflate()]
+-self.connections[self.client_conn] = 
WSConnection(ConnectionType.SERVER,
+-  
extensions=extensions)
+-self.connections[self.server_conn] = 
WSConnection(ConnectionType.CLIENT,
+-  
host=handshake_flow.request.host,
+-  
resource=handshake_flow.request.path,
+-  
extensions=extensions)
++self.connections[self.client_conn] = 
WSConnection(ConnectionType.SERVER)
++self.connections[self.server_conn] = 
WSConnection(ConnectionType.CLIENT)
++
+ if extensions:
+-for conn in self.connections.values():
+-conn.extensions[0].finalize(conn, 

Bug#954311: Not just rendering issues...

[Timo Aaltonen]

On 8.4.2020 17.15, Pascal Giard wrote:
> On Mon, Apr 6, 2020 at 12:05 PM Timo Aaltonen  > wrote:
> 
> On 6.4.2020 1.55, Pascal Giard wrote:
> > Thanks A LOT for the /etc/drirc trick, it fixed the problem
> > detailed below for me.
> > Took me over an hour to figure out what was wrong and to end up on
> this
> > bug report.
> >
> > I have a Thinkpad T480 (Intel UHD 620).
> >
> > The new iris driver causes all my video players to crash (e.g., VLC or
> > mpv) and prevents Zoom from converting my recorded sessions.
> Do you use xserver-xorg-video-intel? If yes, get rid of it.
> 
> 
> I do use it, yes. Which driver am I suppose to use instead?

The default, which is modesetting_drv.so from the xserver.


-- 
t

Bug#954635: marked as done (CLI binding packages fail to install: Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 14:47:36 +
with message-id 
and subject line Bug#954635: fixed in mono 6.8.0.105+dfsg-3
has caused the Debian Bug report #954635,
regarding CLI binding packages fail to install: Unhandled Exception: 
System.TypeInitializationException: The type initializer for 'Sys' threw an 
exception
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.)


-- 
954635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-thecreeper-go-notify
Version: 0.0~git20160203.0.b5cd147-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.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), dh-golang, golang-go, dbus, xvfb, 
> xauth, libnotify-cil-dev, notification-daemon, libgtk-3-bin, golang-dbus-dev, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 10), dh-golang, golang-go, dbus, xvfb, 
> xauth, libnotify-cil-dev, notification-daemon, libgtk-3-bin, golang-dbus-dev, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [428 B]
> Get:5 copy:/<>/apt_archive ./ Packages [509 B]
> Fetched 1894 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> The following additional packages will be installed:
>   adwaita-icon-theme autoconf automake autopoint autotools-dev bsdmainutils
>   cli-common dbus dbus-user-session dconf-gsettings-backend dconf-service
>   debhelper dh-autoreconf dh-golang dh-strip-nondeterminism dmsetup dwz file
>   fontconfig fontconfig-config fonts-dejavu-core gettext gettext-base
>   glib-networking glib-networking-common glib-networking-services
>   golang-1.14-go golang-1.14-src golang-dbus-dev golang-go golang-src
>   groff-base gsettings-desktop-schemas gtk-update-icon-cache
>   hicolor-icon-theme intltool-debian libapparmor1 libarchive-zip-perl
>   libargon2-1 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0
>   libavahi-client3 libavahi-common-data libavahi-common3 libbrotli1 libbsd0
>   libcairo-gobject2 libcairo2 libcap2 libcolord2 libcroco3 libcryptsetup12
>   libcups2 libdatrie1 libdbus-1-3 libdbus-glib2.0-cil libdbus2.0-cil libdconf1
>   libdebhelper-perl libdevmapper1.02.1 libdrm-amdgpu1 libdrm-common
>   libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libedit2 libelf1
>   libepoxy0 libexif12 libexpat1 libfile-stripnondeterminism-perl
>   libfontconfig1 libfontenc1 libfreetype6 libfribidi0 libgdiplus
>   libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgif7 libgl1 libgl1-mesa-dri
>   libglapi-mesa libglib2.0-0 libglib2.0-cil libglvnd0 libglx-mesa0 libglx0
>   libgraphite2-3 libgssapi-krb5-2 libgtk-3-0 libgtk-3-bin libgtk-3-common
>   libgtk2.0-0 libgtk2.0-cil libgtk2.0-common libharfbuzz0b libice6 libicu63
>   libip4tc2 libjbig0 libjpeg62-turbo libjson-c4 libjson-glib-1.0-0
>   libjson-glib-1.0-common libk5crypto3 libkeyutils1 libkmod2 libkrb5-3
>   libkrb5support0 liblcms2-2 libllvm9 libmagic-mgc libmagic1
>   libmono-cairo4.0-cil libmono-corlib4.5-cil libmono-posix4.0-cil
>   libmono-security4.0-cil libmono-system-configuration4.0-cil
>   libmono-system-core4.0-cil libmono-system-drawing4.0-cil
>   libmono-system-numerics4.0-cil libmono-system-security4.0-cil
>   libmono-system-xml4.0-cil libmono-system4.0-cil libnotify-cil-dev
>   libnotify0.4-cil libpam-systemd libpango-1.0-0 libpangocairo-1.0-0
>   libpangoft2-1.0-0 libpciaccess0 libpipeline1 libpixman-1-0 libpng16-16
>   libproxy1v5 libpsl5 librest-0.7-0 librsvg2-2 librsvg2-common
>   libsensors-config libsensors5 libsigsegv2 libsm6 libsoup-gnome2.4-1
>   libsoup2.4-1 libsqlite3-0 libssl1.1 libsub-override-perl libthai-data
>   libthai0 libtiff5 

Bug#956205: gitlab: Problem installing 12.8.8-6

[Pirate Praveen]

Control: merge 953415 -1

On 2020, ഏപ്രിൽ 8 3:59:36 PM IST, David L  wrote:
>rake aborted!
>SassC::SyntaxError: Error: Top-level selectors may not contain the
>parent selector "&".
>on line 6:9 of node_modules/@gitlab/ui/src/scss/components.scss

It is already known and work around documented in 
https://wiki.debian.org/gitlab (it is a good idea to check that page for known 
issues). Upstream sassc gem is still using an older version of libsass and 
sassc is failing to build on CentOS 6, so it is currently not easy to reproduce 
for gitlab upstream.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#891901:

[Daniele Scasciafratte]

I found this ticket because I have the same issue after 2 years.
With the version on sid I had the same problem so I tried with the
experimental because is more updated and the one used by debian is very old.
I am getting the same errors reported here and Ifixed it as suggested in
this ticket and now is starting, well at least the errors are different now:

Exception in thread "main" java.lang.ExceptionInInitializerError
at processing.app.Preferences.save(Preferences.java:799)
at processing.app.Preferences.init(Preferences.java:271)
at processing.app.Base.main(Base.java:143)
Caused by: java.lang.NumberFormatException: For input string: "14-"
at
java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2054)
at
java.base/jdk.internal.math.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
at java.base/java.lang.Float.parseFloat(Float.java:461)
at java.base/java.lang.Float.(Float.java:560)
at processing.core.PApplet.(Unknown Source)
... 3 more
Exception in thread "SocketListener(192-168-1-14.local.)" Exception in
thread "SocketListener(192-168-50-1.local.)" Exception in thread
"SocketListener(fe80-0-0-0-59c-f276-980b-d12a-wlp4s0.local.)"
java.lang.AbstractMethodError: Receiver class
processing.app.zeroconf.jmdns.ArduinoDNSTaskStarter$1 does not define or
inherit an implementation of the resolved method 'abstract void
startResponder(javax.jmdns.impl.DNSIncoming, java.net.InetAddress, int)' of
interface javax.jmdns.impl.DNSTaskStarter.
at javax.jmdns.impl.JmDNSImpl.startResponder(JmDNSImpl.java:1753)
at javax.jmdns.impl.JmDNSImpl.handleQuery(JmDNSImpl.java:1543)
at javax.jmdns.impl.SocketListener.run(SocketListener.java:59)
java.lang.AbstractMethodError: Receiver class
processing.app.zeroconf.jmdns.ArduinoDNSTaskStarter$1 does not define or
inherit an implementation of the resolved method 'abstract void
startResponder(javax.jmdns.impl.DNSIncoming, java.net.InetAddress, int)' of
interface javax.jmdns.impl.DNSTaskStarter.
at javax.jmdns.impl.JmDNSImpl.startResponder(JmDNSImpl.java:1753)
at javax.jmdns.impl.JmDNSImpl.handleQuery(JmDNSImpl.java:1543)
at javax.jmdns.impl.SocketListener.run(SocketListener.java:59)
java.lang.AbstractMethodError: Receiver class
processing.app.zeroconf.jmdns.ArduinoDNSTaskStarter$1 does not define or
inherit an implementation of the resolved method 'abstract void
startResponder(javax.jmdns.impl.DNSIncoming, java.net.InetAddress, int)' of
interface javax.jmdns.impl.DNSTaskStarter.
at javax.jmdns.impl.JmDNSImpl.startResponder(JmDNSImpl.java:1753)
at javax.jmdns.impl.JmDNSImpl.handleQuery(JmDNSImpl.java:1543)
at javax.jmdns.impl.SocketListener.run(SocketListener.java:59)
Exception in thread
"SocketListener(fe80-0-0-0-800-27ff-fe00-0-vboxnet0.local.)"
java.lang.AbstractMethodError: Receiver class
processing.app.zeroconf.jmdns.ArduinoDNSTaskStarter$1 does not define or
inherit an implementation of the resolved method 'abstract void
startResponder(javax.jmdns.impl.DNSIncoming, java.net.InetAddress, int)' of
interface javax.jmdns.impl.DNSTaskStarter.
at javax.jmdns.impl.JmDNSImpl.startResponder(JmDNSImpl.java:1753)
at javax.jmdns.impl.JmDNSImpl.handleQuery(JmDNSImpl.java:1543)
at javax.jmdns.impl.SocketListener.run(SocketListener.java:59)

Processed: Re: Bug#956205: gitlab: Problem installing 12.8.8-6

[Debian Bug Tracking System]

Processing control commands:

> merge 953415 -1
Bug #953415 [gitlab] gitlab: Top-level selectors may not contain the parent 
selector "&"
Bug #956205 [gitlab] gitlab: Problem installing 12.8.8-6
There is no source info for the package 'gitlab' at version '12.8.8-6+fto10+1' 
with architecture ''
Unable to make a source version for version '12.8.8-6+fto10+1'
Marked as found in versions gitlab/12.6.8-1.
Bug #953415 [gitlab] gitlab: Top-level selectors may not contain the parent 
selector "&"
There is no source info for the package 'gitlab' at version '12.8.8-6+fto10+1' 
with architecture ''
Unable to make a source version for version '12.8.8-6+fto10+1'
Marked as found in versions 12.8.8-6+fto10+1.
Merged 953415 956205

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

Processed: frobtads: diff for NMU version 1:1.2.4-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 836934 + pending
Bug #836934 [src:frobtads] frobtads: FTBFS with GCC 6: error: exception cleanup 
for this placement new selects non-placement operator delete
Added tag(s) pending.
> tags 871215 + pending
Bug #871215 [src:frobtads] frobtads: FTBFS with GCC-7: error: ISO C++ forbids 
comparison between pointer and integer
Added tag(s) pending.

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

Bug#954311: Not just rendering issues...

[Pascal Giard]

On Mon, Apr 6, 2020 at 12:05 PM Timo Aaltonen  wrote:

> On 6.4.2020 1.55, Pascal Giard wrote:
> > Thanks A LOT for the /etc/drirc trick, it fixed the problem
> > detailed below for me.
> > Took me over an hour to figure out what was wrong and to end up on this
> > bug report.
> >
> > I have a Thinkpad T480 (Intel UHD 620).
> >
> > The new iris driver causes all my video players to crash (e.g., VLC or
> > mpv) and prevents Zoom from converting my recorded sessions.
> Do you use xserver-xorg-video-intel? If yes, get rid of it.
>
>
I do use it, yes. Which driver am I suppose to use instead?

Thanks,

-Pascal

Processed: py2removal bugs severity updates - 2020-04-08 13:45:03.681072+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
> # kodi-x11 is an application, has low popcon (275 <= 1000), and has 0 
> external rdeps or not in testing
> # kodi-wayland is an application, has low popcon (189 <= 1000), and has 0 
> external rdeps or not in testing
> # kodi-gbm is an application, has low popcon (12 <= 1000), and has 0 external 
> rdeps or not in testing
> # kodi-eventclients-ps3 is an application, has low popcon (159 <= 1000), and 
> has 0 external rdeps or not in testing
> severity 936805 serious
Bug #936805 [src:kodi] kodi: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # ladish is an application, has low popcon (364 <= 1000), and has 0 external 
> rdeps or not in testing
> severity 936812 serious
Bug #936812 [src:ladish] ladish: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: Bug#938154 marked as pending in python-sabyenc

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: 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]

Processing control commands:

> notfound -1 12.13.1~dfsg-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
Ignoring request to alter found versions of bug #956211 to the same values 
previously set

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

Bug#938154: marked as pending in python-sabyenc

[jcfp]

Control: tag -1 pending

Hello,

Bug #938154 in python-sabyenc 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-sabyenc/-/commit/409fe383181c46f49f2b7d6a0422202885c417c3


Upload to unstable. (Closes: #938154)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938154

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 out of memory

[Pirate Praveen]

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):

Processed: bug 956084 is forwarded to https://lists.gnu.org/archive/html/bug-inetutils/2020-04/msg00010.html

[Debian Bug Tracking System]

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

> forwarded 956084 
> https://lists.gnu.org/archive/html/bug-inetutils/2020-04/msg00010.html
Bug #956084 [inetutils-telnetd] inetutils-telnetd: CVE-2020-10188
Set Bug forwarded-to-address to 
'https://lists.gnu.org/archive/html/bug-inetutils/2020-04/msg00010.html'.
> thanks
Stopping processing here.

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

Bug#956202: gnome-calendar crashes immediately after start

[Simon McVittie]

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

On Wed, 08 Apr 2020 at 12:16:47 +0200, Matthias Brennwald wrote:
> Running it from the terminal:
> >> gnome-calendar 
> Segmentation fault

Does it print any other messages?

If you run it with "G_MESSAGES_DEBUG=all gnome-calendar", does *that*
print any messages? (You might need to edit the output to avoid
private information appearing: please make it obvious where you have
done so, for example replacing email addresses with XXX@XXX.)

Does anything appear in the systemd journal when you run it? You should
get at least one line in the journal mentioning the segmentation fault
itself; you might also get relevant log messages from components like
evolution-data-server. (Again, you might need to edit out private
information: please make it obvious where you have done so.)

Please install debug symbols and try to get a backtrace that would indicate
to developers what is crashing and why: see
https://wiki.debian.org/HowToGetABacktrace for more information.

> Severity: critical

No, one program crashing does not make your entire operating system
unusable, and is not a root security vulnerability.

I can't reproduce this crash myself, so it seems gnome-calendar is not
entirely unusable for everyone.

smcv

Processed: Re: Bug#956202: gnome-calendar crashes immediately after start

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #956202 [gnome-calendar] gnome-calendar crashes immediately after start
Severity set to 'important' from 'critical'
> tags -1 + moreinfo
Bug #956202 [gnome-calendar] gnome-calendar crashes immediately after start
Added tag(s) moreinfo.

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

Bug#937274: marked as done (petit: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:51:34 +
with message-id 
and subject line Bug#956132: Removed package(s) from unstable
has caused the Debian Bug report #937274,
regarding petit: 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.)


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

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.1.1-1+rm

Dear submitter,

as the package petit 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/956132

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 ---

Processed: labrea: diff for NMU version 2.5-stable-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 952064 + patch
Bug #952064 [src:labrea] labrea: FTBFS: ../inc/pcaputil.h:18:10: error: 
conflicting types for ‘pcap_open’
Added tag(s) patch.
> tags 952064 + pending
Bug #952064 [src:labrea] labrea: FTBFS: ../inc/pcaputil.h:18:10: error: 
conflicting types for ‘pcap_open’
Added tag(s) pending.

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

Bug#952064: labrea: diff for NMU version 2.5-stable-3.1

[Sudip Mukherjee]

Control: tags 952064 + patch
Control: tags 952064 + pending

Dear maintainer,

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

--
Regards
Sudip

diff -u labrea-2.5-stable/debian/changelog labrea-2.5-stable/debian/changelog
--- labrea-2.5-stable/debian/changelog
+++ labrea-2.5-stable/debian/changelog
@@ -1,3 +1,10 @@
+labrea (2.5-stable-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS. (Closes: #952064)
+
+ -- Sudip Mukherjee   Wed, 08 Apr 2020 13:06:10 
+0100
+
 labrea (2.5-stable-3) unstable; urgency=low
 
   * Adopting the package (Closes: #424715).
diff -u labrea-2.5-stable/debian/patches/series 
labrea-2.5-stable/debian/patches/series
--- labrea-2.5-stable/debian/patches/series
+++ labrea-2.5-stable/debian/patches/series
@@ -2,0 +3 @@
+fix_pcap_open.patch
only in patch2:
unchanged:
--- labrea-2.5-stable.orig/debian/patches/fix_pcap_open.patch
+++ labrea-2.5-stable/debian/patches/fix_pcap_open.patch
@@ -0,0 +1,54 @@
+Description: Fix FTBFS
+ libpcap moved the declaration of pcap_open() to pcap.h and so its now
+ visible to labrea. So, it had a conflict with the private pcap_open()
+ which labrea has defined. Rename pcap_open() to _pcap_open().
+
+ ref: 
https://github.com/the-tcpdump-group/libpcap/commit/a372536befc9b1ee1d355058daa2eb9f66aa0c59
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/952064
+
+---
+
+--- a/inc/pcaputil.h
 b/inc/pcaputil.h
+@@ -15,7 +15,7 @@
+ #endif
+ 
+ 
+-pcap_t * pcap_open(char *device);
++pcap_t * _pcap_open(char *device);
+ int   pcap_dloff(pcap_t *pcap);
+ int   pcap_filter(pcap_t *pcap, const char *fmt, ...);
+ void  pcap_stat (pcap_t *pd);
+--- a/src/lbio.c
 b/src/lbio.c
+@@ -190,7 +190,7 @@ open_winpcap_adapter()
+   /*
+* Open the WinPcap device for sniffing
+*/
+-  if ((io.pcap = pcap_open(io.adapter_name_list[j])) == NULL) {
++  if ((io.pcap = _pcap_open(io.adapter_name_list[j])) == NULL) {
+ warnx("*** Couldn't open WinPcap adapter" );
+ return(-1);
+   }
+@@ -286,7 +286,7 @@ lbio_init(u_char *dev, u_char *texpr)
+   util_clean_exit(1);
+ 
+   } else { /* open Unix pcap device for sniffing */
+-if ((io.pcap = pcap_open(io.ifent->intf_name)) == NULL) {
++if ((io.pcap = _pcap_open(io.ifent->intf_name)) == NULL) {
+   warnx("*** Couldn't open pcap device for sniffing" );
+   util_clean_exit(1);
+ }
+--- a/src/pcaputil.c
 b/src/pcaputil.c
+@@ -52,7 +52,7 @@
+ #include "pcaputil.h"
+ 
+ pcap_t *
+-pcap_open(char *device)
++_pcap_open(char *device)
+ {
+   char ebuf[PCAP_ERRBUF_SIZE];
+   pcap_t *pcap;

Bug#936546: marked as done (forg: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:51:58 +
with message-id 
and subject line Bug#956133: Removed package(s) from unstable
has caused the Debian Bug report #936546,
regarding forg: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:forg

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: 0.5.1-7.2+rm

Dear submitter,

as the package forg 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/956133

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#938614: marked as done (syncthing-gtk: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:50:51 +
with message-id 
and subject line Bug#956129: Removed package(s) from unstable
has caused the Debian Bug report #938614,
regarding syncthing-gtk: 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.)


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

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

Dear submitter,

as the package syncthing-gtk 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/956129

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#936343: marked as done (cron-deja-vu: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:51:13 +
with message-id 
and subject line Bug#956130: Removed package(s) from unstable
has caused the Debian Bug report #936343,
regarding cron-deja-vu: 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.)


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

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: 0.4-5.1+rm

Dear submitter,

as the package cron-deja-vu 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/956130

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#936819: marked as done (lavapdu: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:52:25 +
with message-id 
and subject line Bug#956156: Removed package(s) from unstable
has caused the Debian Bug report #936819,
regarding lavapdu: 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.)


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

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

Dear submitter,

as the package lavapdu 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/956156

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#938233: marked as done (python-typing: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:49:58 +
with message-id 
and subject line Bug#947020: Removed package(s) from unstable
has caused the Debian Bug report #938233,
regarding python-typing: 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.)


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

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.6.6-2+rm

Dear submitter,

as the package python-typing 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/947020

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#937842: marked as done (Should not be released with bullsye: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 12:49:27 +
with message-id 
and subject line Bug#935573: Removed package(s) from unstable
has caused the Debian Bug report #937842,
regarding Should not be released with bullsye: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-ipaddr

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: 2.2.0-2+rm

Dear submitter,

as the package python-ipaddr 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/935573

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#953367: geneweb-gui binary package might need to be removed for Bullseye

[Sébastien Villemot]

Le mercredi 08 avril 2020 à 08:10 -0400, Guillaume Brochu a écrit :
> As I can see, lablgtk2 should be repaired soon:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677#95
> 
> My understanding is that geneweb-gui does not depend on the problematic 
> component (gtksourceview2) of lablgtk2.
> 
> So I propose to wait for this fix. Then, I might need your help if there are 
> some manual operations to do in order to bring back geneweb in testing.
> 
> As I can also see, this bug (953367) is now tagged as an "issues preventing 
> migration", which was not my intent.
> https://tracker.debian.org/pkg/geneweb

geneweb has been removed from testing and cannot migrate back because
this bug (#953367) is of severity serious.

geneweb will automatically migrate back to testing when this bug is
fixed (or, alternatively, if it is downgraded to a lesser severity).

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#955167:

[Dylan Aïssi]

Hi,

The autopkgtest regression is now fixed in the new version
0.9-1+dfsg-1 which passes according to debci [1]. BUT, if we look at
the log file there are a lot of errors which are not detected (?) by
debci [2]. By looking at the history of tests, it seems this behavior
was already present in the oldest log (2019-12-14). So, probably there
are not a regression, but anyway these errors should be fixed as well.

Best,
Dylan

[1] https://ci.debian.net/packages/r/r-cran-sf/
[2] 
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-sf/4877284/log.gz

Bug#953367: geneweb-gui binary package might need to be removed for Bullseye

[Guillaume Brochu]

Bonjour Sébastien,


As I can see, lablgtk2 should be repaired soon:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677#95

My understanding is that geneweb-gui does not depend on the problematic
component (gtksourceview2) of lablgtk2.

So I propose to wait for this fix. Then, I might need your help if there
are some manual operations to do in order to bring back geneweb in testing.

As I can also see, this bug (953367) is now tagged as an "issues preventing
migration", which was not my intent.
https://tracker.debian.org/pkg/geneweb

With best regards,


Guillaume

Le mer. 8 avr. 2020 à 04:33, Sébastien Villemot  a
écrit :

> Dear Guillaume,
>
> Le dimanche 08 mars 2020 à 11:54 -0400, Guillaume Brochu a écrit :
> > Package: geneweb-gui
> > Version: 6.08+git20181019+dfsg-2
> > Severity: serious
> > X-Debbugs-CC: sebast...@debian.org
> >
> > geneweb-gui binary package might need to be removed for Bullseye, for
> > the two following reasons:
>
> As you may have seen, geneweb has been removed from testing because of
> this bug.
>
> Isn’t it the time for dropping the geneweb-gui package, so that geneweb
> can get back into testing?
>
> Best,
>
> --
> ⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
> ⣾⠁⢠⠒⠀⣿⡁  Debian Developer
> ⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
> ⠈⠳⣄  https://www.debian.org
>
>

Bug#956084: inetutils-telnetd: CVE-2020-10188

[Guillem Jover]

Hi!

On Tue, 2020-04-07 at 13:41:09 +1000, Paul Szabo wrote:
> Package: inetutils-telnetd
> Severity: critical
> Tags: security
> Justification: root security hole

> Looking in https://security-tracker.debian.org/tracker/CVE-2020-10188 :
> 
>   utility.c in telnetd in netkit telnet through 0.17 allows remote
>   attackers to execute arbitrary code via short writes or urgent data,
>   because of a buffer overflow involving the netclear and nextitem
>   functions.

Thanks for the report!

> Seems to me that inetutils contains the same (vulnerable) utility.c
> functions. Please check.

I've reported this upstream, as I don't think I'll have the immediate
time to deal with this myself. I've just skimmed over the original
advisory and inetutils code and it seems like the relevant code is
there. I've run the PoC exploit and the info leak seems to be valid,
but the memory layout is not due to the code differences so there's an
assert triggered, but I still think the exploit would otherwise work.

The mail has not yet reached the upstream list, I'll update the
forwarded control data once that's the case.

Thanks,
Guillem

Bug#947556: marked as done (FTBFS with scons 3.1.2-1)

[Debian Bug Tracking System]

Your message dated Wed, 08 Apr 2020 10:48:38 +
with message-id 
and subject line Bug#947556: fixed in create-resources 0.1.3-6
has caused the Debian Bug report #947556,
regarding FTBFS with scons 3.1.2-1
to be marked as done.

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

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


-- 
947556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: create-resources
Version: 0.1.3-5
Severity: important
Usertags: scons_ftbfs


Hello, 

in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far. 

However, an error occurred while building your package. The build log
is attached.

Please check it and fix the error.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

dh clean
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/data/entwicklung/linux/debian/trans_scons/create-resources-0.1.3'
dh_auto_clean
dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use)
rm -f .sconsign.dblite
make[1]: Leaving directory 
'/data/entwicklung/linux/debian/trans_scons/create-resources-0.1.3'
   debian/rules override_dh_clean
make[1]: Entering directory 
'/data/entwicklung/linux/debian/trans_scons/create-resources-0.1.3'
dh_clean -XSConscript~
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
make[1]: Leaving directory 
'/data/entwicklung/linux/debian/trans_scons/create-resources-0.1.3'
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building create-resources using existing 
./create-resources_0.1.3.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building create-resources in 
create-resources_0.1.3-5.debian.tar.xz
dpkg-source: info: building create-resources in create-resources_0.1.3-5.dsc
I: Generating source changes file for original dsc
dpkg-genchanges: info: not including original source code in upload
W: cgroups are not available on the host, not using them.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Dec 27 11:51:59 CET 2019
I: pbuilder-time-stamp: 1577443919
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/sid-amd64-base.tgz]
I: copying local configuration
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: Mounting /var/cache/debs
I: policy-rc.d already exists
W: Could not create compatibility symlink because /tmp/buildd exists and 
it is not a directory
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [../create-resources_0.1.3-5.dsc]
I: copying [../create-resources_0.1.3.orig.tar.gz]
I: copying [../create-resources_0.1.3-5.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package 
(create-resources_0.1.3-5.dsc)
dpkg-source: info: extracting create-resources in create-resources-0.1.3
dpkg-source: info: unpacking create-resources_0.1.3.orig.tar.gz
dpkg-source: info: unpacking create-resources_0.1.3-5.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-add_name_header_to_GIMP_palettes.patch
I: using fakeroot in build.
I: Installing the build-deps
I: user script /var/cache/pbuilder/build//304480/tmp/hooks/D05deps 
starting
Get:1 file:/var/cache/debs ./ InRelease
Ign:1 file:/var/cache/debs ./ InRelease
Get:2 file:/var/cache/debs ./ Release
Ign:2 file:/var/cache/debs ./ Release
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packages
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packages
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packages
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs 

Bug#956204: pdftk-java: pdftk Unsupported major.minor version 52.0

[merlin]

Package: pdftk-java
Version: 3.0.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
When i use pdftk
***
I have this problem
pdftk input BonDeCommande-20063569-20200409.pdf
BonDeCommande-20064317-20200409.pdf BonDeCommande-20063577-20200409.pdf
BonDeCommande-20064648-20200409.pdf cat output Leclerc.pdf
Exception in thread "main" java.lang.UnsupportedClassVersionError:
com/gitlab/pdftk_java/pdftk : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: com.gitlab.pdftk_java.pdftk.  Program will exit.
Best regards.
Philippe Merlin
***



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

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

Versions of packages pdftk-java depends on:
ii  default-jre-headless [java8-runtime-headless] 2:1.11-72
ii  libbcprov-java1.61-1
ii  libcommons-lang3-java 3.8-2
ii  openjdk-10-jre-headless [java8-runtime-headless]  10.0.2+13-2
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.7+9-1
ii  openjdk-8-jre-headless [java8-runtime-headless]   8u252-b07-1
ii  openjdk-9-jre-headless [java8-runtime-headless]   9.0.4+12-4

pdftk-java recommends no packages.

Versions of packages pdftk-java suggests:
ii  poppler-utils [xpdf-utils]  0.71.0-6

-- no debconf information

Bug#956205: gitlab: Problem installing 12.8.8-6

[David L]

Package: gitlab
Version: 12.8.8-6+fto10+1
Severity: grave
Justification: renders package unusable

Hi,

Gitlab 12.8.8 installation fails.

Log:

Bundle complete! 198 Gemfile dependencies, 362 gems now installed.
Gems in the groups development and test were not installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Running final rake tasks and tweaks...
gitlab_production database is not empty, skipping gitlab setup

Precompiling assets...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Attention: used pure ruby version of MurmurHash3
/usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant 
Gitlab::COM_URL
/usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was 
here
/usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant 
Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of 
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant 
Gitlab::SUBDOMAIN_REGEX
/usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of 
SUBDOMAIN_REGEX was here
/usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant 
Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of VERSION was 
here
/usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant 
Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of 
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant 
Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of 
HTTP_PROXY_ENV_VARS was here
yarn install v1.22.4
[1/4] Resolving packages...
success Already up-to-date.
$ node ./scripts/frontend/postinstall.js
success Dependency postinstall check passed.
Done in 1.45s.
rake aborted!
SassC::SyntaxError: Error: Top-level selectors may not contain the parent 
selector "&".
on line 6:9 of node_modules/@gitlab/ui/src/scss/components.scss
from line 13:9 of node_modules/@gitlab/ui/src/scss/gitlab_ui.scss
from line 5:9 of app/assets/stylesheets/framework.scss
from line 19:9 of app/assets/stylesheets/application.scss
>>   &.gl-avatar-identicon-bg#{$i} {

   --^
/usr/share/gitlab/node_modules/@gitlab/ui/src/scss/../components/base/avatar/avatar.scss:82
/usr/share/rubygems-integration/all/gems/sassc-2.2.1/lib/sassc/engine.rb:49:in 
`render'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned error 
exit status 1


Thanks,

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

Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.10-2
ii  bc  1.07.1-2+b2
ii  bundler 2.1.4-1
ii  bzip2   1.0.8-2
ii  dbconfig-pgsql  2.0.13
ii  debconf [debconf-2.0]   1.5.73
ii  exim4-daemon-light [mail-transport-agent]   4.93-13
ii  gitlab-common   12.8.8-6+fto10+1
ii  gitlab-workhorse8.30+debian-1
ii  libjs-bootstrap4 [node-bootstrap]   4.4.1+dfsg1-2
ii  libjs-popper.js [node-popper.js]1.16.0+ds2-1
ii  libjs-uglify2.8.29-6
ii  lsb-base11.1.0
ii  nginx   1.16.1-3
ii  nginx-full [nginx]  1.16.1-3
ii  node-autosize   4.0.2~dfsg1-3
ii  node-axios  0.19.0+dfsg-2
ii  node-brace-expansion1.1.11-1
ii  node-cache-loader   2.0.1-2
ii  node-chart.js   2.9.3+dfsg-2
ii  node-clipboard  2.0.6+ds-1
ii  node-core-js3.6.1-3
ii  node-css-loader 1.0.1+repack-1
ii  node-d3

Bug#947556: marked as pending in create-resources

[Ross Gammon]

Control: tag -1 pending

Hello,

Bug #947556 in create-resources 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/multimedia-team/create-resources/-/commit/7060a8daf2e7de54ffa173fa186d9f4fbfd54cee


Apply patch to fix FTBFS with Python3 Scons

Closes: #947556
Thanks: Reiner Herrmann


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947556

Processed: Bug#947556 marked as pending in create-resources

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #947556 [src:create-resources] FTBFS with scons 3.1.2-1
Added tag(s) pending.

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

Bug#956202: gnome-calendar crashes immediately after start

[Matthias Brennwald]

Package: gnome-calendar
Version: 3.36.0-1
Severity: critical

Dear Maintainer,

After a recent update to my system, gnome-calendar crashes immediately after 
staring it.

Running it from the terminal:
>> gnome-calendar 
Segmentation fault


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

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

Versions of packages gnome-calendar depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gsettings-desktop-schemas3.36.0-1
ii  libc62.30-4
ii  libcairo21.16.0-4
ii  libdazzle-1.0-0  3.36.0-1
ii  libecal-2.0-13.36.1-1
ii  libedataserver-1.2-243.36.1-1
ii  libedataserverui-1.2-2   3.36.1-1
ii  libgeoclue-2-0   2.5.6-1
ii  libglib2.0-0 2.64.1-1
ii  libgoa-1.0-0b3.36.0-1
ii  libgtk-3-0   3.24.14-1
ii  libgweather-3-16 3.36.0-1
ii  libhandy-0.0-0   0.0.13-2
ii  libical3 3.0.8-1
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libsoup2.4-1 2.70.0-1

Versions of packages gnome-calendar recommends:
ii  evolution-data-server  3.36.1-1

gnome-calendar suggests no packages.

-- no debconf information

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> retitle 955316 r-cran-svglite autopkgtest fails: Error: symbol font
Bug #955316 [src:r-cran-svglite] r-cran-svglite autopkgtest fails: there is no 
package called 'xml2'
Changed Bug title to 'r-cran-svglite autopkgtest fails: Error: symbol font' 
from 'r-cran-svglite autopkgtest fails: there is no package called 'xml2''.
> family is 'Symbol'
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#953367: geneweb-gui binary package might need to be removed for Bullseye

[Sébastien Villemot]

Dear Guillaume,

Le dimanche 08 mars 2020 à 11:54 -0400, Guillaume Brochu a écrit :
> Package: geneweb-gui
> Version: 6.08+git20181019+dfsg-2
> Severity: serious
> X-Debbugs-CC: sebast...@debian.org
> 
> geneweb-gui binary package might need to be removed for Bullseye, for
> the two following reasons:

As you may have seen, geneweb has been removed from testing because of
this bug.

Isn’t it the time for dropping the geneweb-gui package, so that geneweb
can get back into testing?

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Processed: tagging 952039

[Debian Bug Tracking System]

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

> tags 952039 + fixed
Bug #952039 {Done: Daniel Leidert } [src:ruby-graphviz] 
ruby-graphviz: FTBFS: ERROR: Test "ruby2.7" failed: 
/<>/test/output/dot/hello_test.rb:18:in `': 
undefined method `graph' for nil:NilClass (NoMethodError)
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#956190: dh-python's autopkg tests fail with python3.8 as the only supported python3 version

[Matthias Klose]

Package: dh-python
Version: 4.20200315
Severity: serious
Tags: sid bullseye

dh-python's autopkg tests fail with python3.8 as the only supported python3 
version.

Processed: tagging 947541

[Debian Bug Tracking System]

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

> tags 947541 + fixed-upstream
Bug #947541 [src:viking] viking: build-depends on deprecated gnome-doc-utils
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 947541 is forwarded to https://github.com/viking-gps/viking/commit/18d7c02d5829ec796efaa6b0fba0632f478048ba#diff-67e997bcfdac55191033d57a16d1408a

[Debian Bug Tracking System]

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

> forwarded 947541 
> https://github.com/viking-gps/viking/commit/18d7c02d5829ec796efaa6b0fba0632f478048ba#diff-67e997bcfdac55191033d57a16d1408a
Bug #947541 [src:viking] viking: build-depends on deprecated gnome-doc-utils
Set Bug forwarded-to-address to 
'https://github.com/viking-gps/viking/commit/18d7c02d5829ec796efaa6b0fba0632f478048ba#diff-67e997bcfdac55191033d57a16d1408a'.
> thanks
Stopping processing here.

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

Processed: tagging 947542

[Debian Bug Tracking System]

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

> tags 947542 + fixed-upstream
Bug #947542 [src:xiphos] xiphos: build-depends on deprecated gnome-doc-utils
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 947540

[Debian Bug Tracking System]

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

> tags 947540 + upstream
Bug #947540 [src:stardict] stardict: build-depends on deprecated gnome-doc-utils
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#953996: [Pkg-julia-devel] Bug#953996: julia: FTBFS on ppc64el

[Graham Inggs]

On Wed, 1 Apr 2020 at 09:36,  wrote:
> Any follow-up/update on this? Looks like 11 April package will be auto-
> removed if not fixed? Is this even fixable?

I bisected the commits between 1.3.0 and 1.3.1 and found that
reverting the following commit allows the build to succeed on ppc64el:
ccall: report static compile-time load issues correctly (#34062) [1]

However, even in previous "successful" builds on ppc64el [2], I see
tests aborted and LLVM ERROR.
I think removal of the ppc64el binary is the way to go.


[1] 
https://github.com/JuliaLang/julia/commit/78615011ec61ec0043c34afadaec5cd4862424b9
[2] https://buildd.debian.org/status/logs.php?pkg=julia=ppc64el

Processed: bug 947533 is forwarded to https://github.com/kupferlauncher/kupfer/pull/129

[Debian Bug Tracking System]

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

> forwarded 947533 https://github.com/kupferlauncher/kupfer/pull/129
Bug #947533 [src:kupfer] kupfer: build-depends on deprecated gnome-doc-utils
Set Bug forwarded-to-address to 
'https://github.com/kupferlauncher/kupfer/pull/129'.
> thanks
Stopping processing here.

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

Processed: tagging 947533

[Debian Bug Tracking System]

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

> tags 947533 + fixed-upstream
Bug #947533 [src:kupfer] kupfer: build-depends on deprecated gnome-doc-utils
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#955456: FTBFS: test file tmp_test_filters.h5 does not exist

[Drew Parsons]

Package: bitshuffle
Followup-For: Bug #955456

Incidentally, Thorsten, another way of handling h5py and bitshuffle's
build against hfd5-mpi is to explicitly access h5py-mpi.

That is, patch out bitshuffle to replace
  import h5py
with
  import h5py._debian_h5py_mpi as h5py

(in bitshuffle/h5.pyx and in tests).

In that case h5py-mpi gets loaded directly by bitshuffle, so will be active 
even in a
serial process.

Bug#946853: Upgrade to ACE 6.5.8

[Johnny Willemsen]

Hi,

Not a problem, years ago I asked several times whether people could
assist me with the process to be allowed to upgrade ACE as part of the
release procedure. Currently I upload the packages to github/vanderbilt
but also provide them to OpenSuSE Build service, vcpkg, homebrew. Adding
an upload to debian wouldn't take much long but I have no idea how to be
able to do that currently, maybe someone could contact me directly at
jwillem...@remedy.nl to discuss that.

Johnny

On 4/7/20 11:43 PM, Sudip Mukherjee wrote:
> On Tue, Apr 07, 2020 at 01:57:44PM +0200, Johnny Willemsen wrote:
>> Hi,
>>
>> Would help everyone when someone could upgrade ACE to 6.5.8, the most
>> recent micro
> I can have a look at the upgrade, but I am not allowed to do that as NMU.
> It might be better if the maintainer does it. And also, there is another
> pending RC bug #899440, I can not do NMU for that. :(
>
> Though I will suggest that we upload the NMU first and unblock ivtools,
> which is failing due to ACE, #954637.
>
> --
> Regards
> Sudip