Bug#952353: swiftsc: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module)

[Logan Rosen]

Package: swiftsc
Version: 0.5-1.1
Followup-For: Bug #952353
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

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

  * Build-depend on dh-python to fix FTBFS due to missing python3.pm.

Thanks for considering the patch.

Logan

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

Kernel: Linux 5.4.0-25-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru swiftsc-0.5/debian/control swiftsc-0.5/debian/control
--- swiftsc-0.5/debian/control  2019-10-29 09:31:26.0 -0400
+++ swiftsc-0.5/debian/control  2020-04-20 22:04:15.0 -0400
@@ -2,7 +2,7 @@
 Section: python
 Priority: optional
 Maintainer: Kouhei Maeda 
-Build-Depends: debhelper (>= 8.0.0), pep8, python3-all, python3-setuptools, 
python3-requests, python3-magic, python3-pytest, python3-mock
+Build-Depends: debhelper (>= 8.0.0), dh-python, pep8, python3-all, 
python3-setuptools, python3-requests, python3-magic, python3-pytest, 
python3-mock
 Standards-Version: 3.9.4
 X-Python-Version: >= 2.6, >= 3.2
 Homepage: https://github.com/mkouhei/swiftsc

Bug#951931: marked as done (alsa-tools: FTBFS: hdsp.h:77:7: error: variable or field ‘__user’ declared void)

[Debian Bug Tracking System]

Your message dated Tue, 21 Apr 2020 00:18:37 +
with message-id 
and subject line Bug#951931: fixed in alsa-tools 1.2.2-1
has caused the Debian Bug report #951931,
regarding alsa-tools: FTBFS: hdsp.h:77:7: error: variable or field ‘__user’ 
declared void
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.)


-- 
951931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alsa-tools
Version: 1.1.7-1
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):
> x86_64-linux-gnu-g++ -DPACKAGE_NAME=\"hdspconf\" 
> -DPACKAGE_TARNAME=\"hdspconf\" -DPACKAGE_VERSION=\"1.4\" 
> -DPACKAGE_STRING=\"hdspconf\ 1.4\" -DPACKAGE_BUGREPORT=\"\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"hdspconf\" -DVERSION=\"1.4\" -DSTDC_HEADERS=1 
> -DHAVE_LIBASOUND=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security   -I/usr/include/freetype2 -I/usr/include/libpng16
> -fno-exceptions -MT hdspconf.o -MD -MP -MF .deps/hdspconf.Tpo -c -o 
> hdspconf.o hdspconf.cxx
> In file included from hdspconf.cxx:27:
> /usr/include/alsa/sound/hdsp.h:77:7: error: variable or field ‘__user’ 
> declared void
>77 |  void __user *firmware_data; /* 24413 x 4 bytes */
>   |   ^~
> /usr/include/alsa/sound/hdsp.h:77:7: error: expected ‘;’ at end of member 
> declaration
>77 |  void __user *firmware_data; /* 24413 x 4 bytes */
>   |   ^~
>   | ;
> make[2]: *** [Makefile:340: hdspconf.o] Error 1

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated alsa-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Apr 2020 01:48:04 +0200
Source: alsa-tools
Architecture: source
Version: 1.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Jordi Mallach 
Closes: 894189 896471 949114 949115 951931
Changes:
 alsa-tools (1.2.2-1) unstable; urgency=medium
 .
   * New upstream release.
 - hdspmixer: Use __u32 and __u64 for RMS array types (closes: #951931)
   * Apply patches from Vagrant Cascadiant to fix reproducibility issues with
 the emu10k1MIDIEffects example Makefile:
 - strip instances of build path out of example Makefile (closes: #949114).
 - set GREP, MKDIR_P, SED and SHELL from ./configure, to prevent
   variations when built on a system with merged /usr (closes: #949115).
   * Run dh_update_autotools_config before running configure (closes: #894189).
   * Merge MR !2 from Olivier Humbert to improve alsa-tools-gui desktop
 integration, by replacing our .desktop files by the upstream-provided
 ones, and applying several improvements (closes: #896471).
Checksums-Sha1:
 c55a0eaab61ea95377c229fdecbe89eb66783eb0 2421 alsa-tools_1.2.2-1.dsc
 64c3d8ec578386861e2c6f3b0a926453cdac2497 1876266 alsa-tools_1.2.2.orig.tar.bz2
 cf69b9dd684d4ce2be11b6f4360caf87612a258e 39024 alsa-tools_1.2.2-1.debian.tar.xz
 b35c3bb5172938f775abfd9f170b2ddc883ec283 16589 
alsa-tools_1.2.2-1_amd64.buildinfo
Checksums-Sha256:
 4527fc252761a0cc3e6716755bb03a57c6779963c1050c997157dfcabbf008db 2421 
alsa-tools_1.2.2-1.dsc
 

Bug#942647: marked as done (celery-batches: Incomplete debian/copyright, etc.)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 23:48:37 +
with message-id 
and subject line Bug#942647: fixed in celery-batches 0.2-2
has caused the Debian Bug report #942647,
regarding celery-batches: Incomplete debian/copyright, etc.
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.)


-- 
942647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: celery-batches
Version: 0.2-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: ftpmas...@debian.org, deba...@debian.org, rodrilopez@gmail.com

Hi,

I just ACCEPTed celery-batches from NEW but the FTP team noticed docs/
has a different license not mentioned in debian/copyright.

This is in no way exhaustive so please check over the entire package
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: celery-batches
Source-Version: 0.2-2
Done: Martin 

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

Debian distribution maintenance software
pp.
Martin  (supplier of updated celery-batches 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, 20 Apr 2020 23:19:23 +
Source: celery-batches
Architecture: source
Version: 0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Martin 
Closes: 942647
Changes:
 celery-batches (0.2-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ana Rodríguez López ]
   * Fix debian/copyright (Closes: #942647)
Checksums-Sha1:
 d74e3037e1ecd69f72545319c7d4c70cd276fad9 2083 celery-batches_0.2-2.dsc
 b9d855c5f992dc339ba254e10dcc7ec7a7d02bbd 7180 
celery-batches_0.2-2.debian.tar.xz
 4887b5d2deb6c39c947e76e206c6dca49bb575cd 6833 
celery-batches_0.2-2_amd64.buildinfo
Checksums-Sha256:
 92bc8b2bb0f4a09a1ec622d9d2f9524f1f8c9621525959697bf075c3a2daa765 2083 
celery-batches_0.2-2.dsc
 a0c357f6a84b552d409acaf1a9efa3b208502447033f4eaedd0f52406b7aab60 7180 
celery-batches_0.2-2.debian.tar.xz
 d8dc722aefdc3cd32b0c33e966b30b84b0dd8cee0729fe5a83862cdc8e28d460 6833 
celery-batches_0.2-2_amd64.buildinfo
Files:
 14418bee861f001894966863d9085426 2083 python optional celery-batches_0.2-2.dsc
 d9fc9c74ac9fb692c1846fd7946aa7fe 7180 python optional 
celery-batches_0.2-2.debian.tar.xz
 9b46b138ce91f1086337b70cbe77c791 6833 python optional 
celery-batches_0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAl6eLwwACgkQ4+Chwoa5
Y+rpAg/5AVWJ9FV50q8JU1mPuVErzQrimEkJbF0xF7AkNn7Q76QeqKJcoVvzZKPl
C6g21QZlpZl0bgDbdwi4CR/+aKHYoBkya9720hVhYIH4qz7Vioxtwc/RyJqC4vaP
OuxehPUoV7GGwyitVARhgtIXgrZsx2xB1ALb1309uF3+ax99WF2+PUJl3H7pywMJ
Iov/pIM3IGf/F/UPmhsID5cyH6hy5wA5suOs9ay2GY1fwiOga2H268RYNF9/bcV1
TXcm86WoU4Ww/YxSopPyn1OgFMELaSQNKTZIrF9SblEFKrtcObZEntxtkCWg0S7O
+LoSpotTMsHSVNaq4ArQTXDLCIlnD8/K/fT8cndP6lpHRYJ68j8dHf7W8oPHL7/d
cE1FEkkCGAvsIWo1x/MsTfem8y63X8KOhX7KZfLWvKtwiR7aBMIA2CfpT815tiju
igjR56XddsOQXrxx/z0Sxy/1vmJ3oNkhsShV2hFWXOY9/tnnOBHQWc0+t42Bcn5c
FqZbtcoVuwgo0y0zZEQVQzqMMuUkCjBIbOUEN0yTSw8ODTwqYZBx51bBRO0IXMT3
VHbYXKxPZdfrcQ+oVTw1ons2RbKxiZItDZOxUdZPFOSNyp+RJl1boMRH+6LX1g+A
2mWDhfyVWc29bd0asZkZZopgs6E8u6pDf1hcXJKbWnVxqj0trBo=
=sUgH
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:50:10 +
with message-id 
and subject line Bug#938073: fixed in python-pylibacl 0.5.4-3
has caused the Debian Bug report #938073,
regarding python-pylibacl: 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.)


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

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-pylibacl
Source-Version: 0.5.4-3
Done: Iustin Pop 

We believe that the bug you reported is fixed in the latest version of
python-pylibacl, 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.
Iustin Pop  (supplier of updated python-pylibacl 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, 20 Apr 2020 23:37:21 +0200
Source: python-pylibacl
Architecture: source
Version: 0.5.4-3
Distribution: unstable
Urgency: medium
Maintainer: Iustin Pop 
Changed-By: Iustin Pop 
Closes: 938073
Changes:
 python-pylibacl (0.5.4-3) unstable; urgency=medium
 .
   * Remove python-setuptools dependency, not needed, and allows really
 fixing the Python 2 bug (Closes: #938073).
   * Bump standards version (no changes needed).
Checksums-Sha1:
 8478cdf8cdafe061bb466e9861750f27e2827953 2479 python-pylibacl_0.5.4-3.dsc
 a59eac60d52fca738603805749321471c175b918 37016 
python-pylibacl_0.5.4.orig.tar.gz
 75b4f1bef4719d9910ed2b37d01c0f488e572b2b 833 
python-pylibacl_0.5.4.orig.tar.gz.asc
 792013d9250fd0b7d218a1004e1c5b9bc1554cfb 8652 
python-pylibacl_0.5.4-3.debian.tar.xz
 312e66a57e03afde0274836ff84445082f5db076 8640 
python-pylibacl_0.5.4-3_source.buildinfo
Checksums-Sha256:
 

Bug#937068: marked as done (moosic: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:10:33 +
with message-id 
and subject line Bug#958358: Removed package(s) from unstable
has caused the Debian Bug report #937068,
regarding moosic: 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.)


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

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 1.5.6-1+rm

Dear submitter,

as the package moosic 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/958358

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#954571: marked as done (zlibc: FTBFS: altnames.c:31:5: error: conflicting types for ‘getdents64’)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:09:27 +
with message-id 
and subject line Bug#958293: Removed package(s) from unstable
has caused the Debian Bug report #954571,
regarding zlibc: FTBFS: altnames.c:31:5: error: conflicting types for 
‘getdents64’
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.)


-- 
954571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zlibc
Version: 0.9k-4.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):
> gcc -g -O2 -Wall -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc\" -Dx86_64 -Dpc 
> -Dlinux_gnu -I. -I. -fpic -c altnames.c
> altnames.c:31:5: error: conflicting types for ‘getdents64’
>31 | int getdents64(int fd, struct dirent64 *dirp, unsigned int count);
>   | ^~
> In file included from /usr/include/dirent.h:404,
>  from sysincludes.h:107,
>  from altnames.c:5:
> /usr/include/x86_64-linux-gnu/bits/dirent_ext.h:29:18: note: previous 
> declaration of ‘getdents64’ was here
>29 | extern __ssize_t getdents64 (int __fd, void *__buffer, size_t 
> __length)
>   |  ^~
> make[1]: *** [Makefile:90: altnames.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/zlibc_0.9k-4.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 ---
Version: 0.9k-4.3+rm

Dear submitter,

as the package zlibc 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/958293

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

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:10:55 +
with message-id 
and subject line Bug#958359: Removed package(s) from unstable
has caused the Debian Bug report #938290,
regarding pytracer: 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.)


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

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

Dear submitter,

as the package pytracer 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/958359

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

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:11:30 +
with message-id 
and subject line Bug#958360: Removed package(s) from unstable
has caused the Debian Bug report #937470,
regarding pylirc: 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.)


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

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-3.1+rm

Dear submitter,

as the package pylirc 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/958360

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#899585: marked as done (libnss-securepass: Invalid maintainer address pkg-securepass-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:06:11 +
with message-id 
and subject line Bug#958233: Removed package(s) from unstable
has caused the Debian Bug report #899585,
regarding libnss-securepass: Invalid maintainer address 
pkg-securepass-de...@lists.alioth.debian.org
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.)


-- 
899585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libnss-securepass
Version: 0.5-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of libnss-securepass,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libnss-securepass since the list address
pkg-securepass-de...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-securepass-de...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


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

Dear submitter,

as the package libnss-securepass 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/958233

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#899809: marked as done (mod-authz-securepass: Invalid maintainer address pkg-securepass-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:06:41 +
with message-id 
and subject line Bug#958234: Removed package(s) from unstable
has caused the Debian Bug report #899809,
regarding mod-authz-securepass: Invalid maintainer address 
pkg-securepass-de...@lists.alioth.debian.org
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.)


-- 
899809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mod-authz-securepass
Version: 0~20150105.gitda462d3-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of mod-authz-securepass,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package mod-authz-securepass since the list address
pkg-securepass-de...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-securepass-de...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0~20150105.gitda462d3-1+rm

Dear submitter,

as the package mod-authz-securepass 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/958234

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#943305: marked as done (golang-github-bradfitz-http2: build-depends not satisfiable)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:04:45 +
with message-id 
and subject line Bug#958201: Removed package(s) from unstable
has caused the Debian Bug report #943305,
regarding golang-github-bradfitz-http2: build-depends not satisfiable
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.)


-- 
943305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-bradfitz-http2
Version: 0.0~git20150509-2
Severity: serious
Tags: ftbfs
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

golang-github-bradfitz-http2 build-depends on golang-go.crypto-dev,
which only exists in old[old]stable.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 0.0~git20150509-2+rm

Dear submitter,

as the package golang-github-bradfitz-http2 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/958201

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#895555: marked as done (golang-github-endophage-gotuf depends on cruft package)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:05:22 +
with message-id 
and subject line Bug#958205: Removed package(s) from unstable
has caused the Debian Bug report #89,
regarding golang-github-endophage-gotuf depends on cruft package
to be marked as done.

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

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


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

Package: golang-github-endophage-gotuf
Version: 0.0~git20151020.0.2df1c8e-1
Severity: serious

golang-github-endophage-gotuf depends on golang-go.crypto-dev which is no 
longer built by golang-go.crypto
--- End Message ---
--- Begin Message ---
Version: 0.0~git20151020.0.2df1c8e-1+rm

Dear submitter,

as the package golang-github-endophage-gotuf 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/958205

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#902011: marked as done (golang-gopkg-libgit2-git2go.v27: FTBFS on i386: diff.go:441: constant 2147483648 overflows DiffOptionsFlag)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:05:03 +
with message-id 
and subject line Bug#958203: Removed package(s) from unstable
has caused the Debian Bug report #902011,
regarding golang-gopkg-libgit2-git2go.v27: FTBFS on i386: diff.go:441: constant 
2147483648 overflows DiffOptionsFlag
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.)


-- 
902011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gopkg-libgit2-git2go.v27
Version: 0.27+git20180529.9abc050-1
Severity: serious
Justification: fails to build from source

Hi,

golang-gopkg-libgit2-git2go.v27 builds fine on amd64, but FTBFS on i386:

   dh_auto_build -O--buildsystem=golang
cd obj-i686-linux-gnu && go install 
-gcflags=\"-trimpath=/build/golang-gopkg-libgit2-git2go.v27-0.27\+git20180529.9abc050/obj-i686-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/golang-gopkg-libgit2-git2go.v27-0.27\+git20180529.9abc050/obj-i686-linux-gnu/src\"
 -v -p 4 gopkg.in/libgit2/git2go.v27
gopkg.in/libgit2/git2go.v27
# gopkg.in/libgit2/git2go.v27
src/gopkg.in/libgit2/git2go.v27/diff.go:441: constant 2147483648 overflows 
DiffOptionsFlag
dh_auto_build: cd obj-i686-linux-gnu && go install 
-gcflags=\"-trimpath=/build/golang-gopkg-libgit2-git2go.v27-0.27\+git20180529.9abc050/obj-i686-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/golang-gopkg-libgit2-git2go.v27-0.27\+git20180529.9abc050/obj-i686-linux-gnu/src\"
 -v -p 4 gopkg.in/libgit2/git2go.v27 returned exit code 2
debian/rules:7: recipe for target 'build' failed


Andreas


golang-gopkg-libgit2-git2go.v27_0.27+git20180529.9abc050-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.27+git20180529.9abc050-2+rm

Dear submitter,

as the package golang-gopkg-libgit2-git2go.v27 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/958203

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#924115: marked as done (golang-gopkg-data-dog-go-sqlmock.v1-dev: directory vs. symlink conflict: /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:04:25 +
with message-id 
and subject line Bug#958198: Removed package(s) from unstable
has caused the Debian Bug report #924115,
regarding golang-gopkg-data-dog-go-sqlmock.v1-dev: directory vs. symlink 
conflict: /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1
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.)


-- 
924115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-gopkg-data-dog-go-sqlmock.v1-dev
Version: 1.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.

Your package ships:

/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/*

but package golang-github-data-dog-go-sqlmock-dev ships:

/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock


Installing something over existing symlinks is considered bad practice.
See e.g. https://lists.debian.org/87ehlevcrf@windlord.stanford.edu

It may break in subtle ways and dpkg cannot detect this as a problem.
* Your package might silently overwrite files installed at the symlink
  destination by other packages.
* If the package shipping the symlink decides to make the link point
  somewhere else (or turn it into a real directory), the files owned
  by your package "will be lost" somewhere in the filesystem.
* Depending on installation order the problematic path will be created
  either as a symlink or a directory: the package installed first will
  "win" and all others have "lost".
  Note that dpkg intentionally does not replace directories with
  symlinks and vice versa, see in particular the end of point 4 in
  
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
  (Note: Adding Pre-Depends is *not* a solution.)

Please move the files shipped in your package to the "real" location.

>From the attached log (scroll to the bottom...):

0m16.8s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/argument.go 
(golang-gopkg-data-dog-go-sqlmock.v1-dev) != 
/usr/share/gocode/src/github.com/DATA-DOG/go-sqlmock/argument.go 
(golang-github-data-dog-go-sqlmock-dev)
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock
  /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/argument_test.go 
(golang-gopkg-data-dog-go-sqlmock.v1-dev) != 
/usr/share/gocode/src/github.com/DATA-DOG/go-sqlmock/argument_test.go 
(golang-github-data-dog-go-sqlmock-dev)
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock
  /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/driver.go 
(golang-gopkg-data-dog-go-sqlmock.v1-dev) != 
/usr/share/gocode/src/github.com/DATA-DOG/go-sqlmock/driver.go 
(golang-github-data-dog-go-sqlmock-dev)
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock
  /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/driver_test.go 
(golang-gopkg-data-dog-go-sqlmock.v1-dev) != 
/usr/share/gocode/src/github.com/DATA-DOG/go-sqlmock/driver_test.go 
(golang-github-data-dog-go-sqlmock-dev)
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock
  /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/examples 
(golang-gopkg-data-dog-go-sqlmock.v1-dev) != 
/usr/share/gocode/src/github.com/DATA-DOG/go-sqlmock/examples 
(golang-github-data-dog-go-sqlmock-dev)
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock
  /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/examples/basic 
(golang-gopkg-data-dog-go-sqlmock.v1-dev) != 
/usr/share/gocode/src/github.com/DATA-DOG/go-sqlmock/examples/basic 
(golang-github-data-dog-go-sqlmock-dev)
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock
  /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/examples/basic/basic.go 
(golang-gopkg-data-dog-go-sqlmock.v1-dev) != 
/usr/share/gocode/src/github.com/DATA-DOG/go-sqlmock/examples/basic/basic.go 
(golang-github-data-dog-go-sqlmock-dev)
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1 -> 
../../github.com/DATA-DOG/go-sqlmock
  
/usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1/examples/basic/basic_test.go
 

Bug#895554: marked as done (golang-github-bradfitz-http2-dev depends on cruft package)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:04:45 +
with message-id 
and subject line Bug#958201: Removed package(s) from unstable
has caused the Debian Bug report #895554,
regarding golang-github-bradfitz-http2-dev depends on cruft package
to be marked as done.

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

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


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

Package: golang-github-bradfitz-http2-dev
Version: 0.0~git20150509-2
Severity: serious

golang-github-bradfitz-http2-dev depends on golang-go.crypto-dev which is no 
longer built by golang-go.crypto
--- End Message ---
--- Begin Message ---
Version: 0.0~git20150509-2+rm

Dear submitter,

as the package golang-github-bradfitz-http2 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/958201

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#958362: pdfrw: fails with python 3.7+ -- abandoned upstream

[Johannes 'josch' Schauer]

Source: pdfrw
Version: 0.4-2
Severity: grave
Justification: renders package unusable

Hi,

the package fails with Python 3.7 and newer. Starting from Python 3.7,
StopIteration is a RuntimeError (see PEP 479). But pdfrw still uses
StopIteration:

https://github.com/pmaupin/pdfrw/issues/145
https://github.com/pmaupin/pdfrw/issues/199

This package recently got its python2 package removed but since tests
are disabled, nobody noticed that its tests fail with Python 3.7+:

https://github.com/pmaupin/pdfrw/issues/198
https://github.com/pmaupin/pdfrw/issues/197

Other upstream bugs indicating that the package is broken on Python3:

https://github.com/pmaupin/pdfrw/issues/193
https://github.com/pmaupin/pdfrw/issues/170

Upstream didn't close bugs for two years and the last commit was more
than two years ago. Upstream admits not having time at the moment here:

https://github.com/pmaupin/pdfrw/issues/195

And is looking for additional maintainers here:

https://github.com/pmaupin/pdfrw/issues/191

In this state, pdfrw should not be included in the next Debian stable
release.

Thanks!

cheers, josch



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

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

Bug#945961: xz-utils: FTBFS: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'

[Tiago Daitx]

On Thu, 9 Apr 2020 16:35:13 +0200 Sebastian Andrzej Siewior
 wrote:
> I suggested already something in [0]. Back then we were hoping for some
> feedback from the debhelper team.
> Now I was just asking if Jonathan is handling this and/or if we could
> also bump to current upstream version while at it.
>
> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945961#10

As Dimitri pointed out we have also been affected by this but in
Ubuntu - we found it out recently when doing archive rebuilds on
Focal. The proposed fix in #10 does workaround the issue and it is not
necessary to change the build-arch rules as Dimitri suggested.

I do wonder if this is in fact a regression in debhelper. I tracked it
down to debhelper 12.4 to 12.5 and while I haven't been able to
pinpoint exactly what particular change there is causing it I believe
it is in how double colon rules are being interpreted. It seems the
debhelper changes somehow fail to detect the build-arch rules.

Unless someone knows enough perl to dig into debhelper changes between
12.4 and 12.5 and check if that is in fact a regression, I would
suggest to simply apply the proposed change in comment #10.

Thanks for your help =)

Tiago Daitx

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 923327 src:xapers
Bug #923327 [xapers] xapers: intermittent autopkgtest failures (escaped 
underscores in XAPERS_ROOT?)
Bug reassigned from package 'xapers' to 'src:xapers'.
No longer marked as found in versions xapers/0.8.2-1.1.
Ignoring request to alter fixed versions of bug #923327 to the same values 
previously set
> forcemerge 954805 923327
Bug #954805 [src:xapers] src:xapers: Fails autopkgtest due to test assumptions 
about paths
Bug #923327 [src:xapers] xapers: intermittent autopkgtest failures (escaped 
underscores in XAPERS_ROOT?)
Severity set to 'serious' from 'normal'
Marked as found in versions xapers/0.8.2-1.1.
Added tag(s) ftbfs.
Merged 923327 954805
> thanks
Stopping processing here.

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

Bug#947089: marked as done (uftrace: blocked migration to testing: autopkgtest times out on arm64 and FTBFS on armhf)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 20:49:53 +
with message-id 
and subject line Bug#947089: fixed in uftrace 0.9.4-0.1
has caused the Debian Bug report #947089,
regarding uftrace: blocked migration to testing: autopkgtest times out on arm64 
and FTBFS on armhf
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.)


-- 
947089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uftrace
Version: 0.9.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of uftrace you added an autopkgtest to uftrace,
great. However, it fails due to timeout on arm64. Currently this failure
is blocking the migration to testing [1]. Additionally the package fails
to armhf [2]. The amd64 binary upload can be fixed by a binNMU, but we
prefer source only uploads nowadays. Can you please investigate the
situation and fix the arm64 autopkgtest timeout and armhf ftbfs?

Paul

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

[2]
Tail of log for uftrace on armhf:

gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o
/<>/libmcount/symbol-libelf.op
/<>/utils/symbol-libelf.c
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/libmcount/symbol.op
/<>/utils/symbol.c
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/arch/arm/mcount.op
/<>/arch/arm/mcount.S
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o /<>/arch/arm/plthook.op
/<>/arch/arm/plthook.S
gcc -D_GNU_SOURCE -ffile-prefix-map=/<>=. -Wdate-time
-D_FORTIFY_SOURCE=2 -iquote /<> -iquote /<>
-iquote /<>/arch/arm -W -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -O2 -g -DHAVE_CXA_DEMANGLE
-DHAVE_LIBPYTHON2 -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW
-DHAVE_ARM_HARDFP -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE
-D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW  -DHAVE_LIBCAPSTONE
-I/usr/include/capstone   -fPIC -fvisibility=hidden
-fno-omit-frame-pointer -c -o
/<>/arch/arm/mcount-support.op
/<>/arch/arm/mcount-support.c
/<>/arch/arm/mcount-support.c: In function
‘mcount_arch_parent_location’:
/<>/arch/arm/mcount-support.c:289:2: error: ‘cache’
undeclared (first use in this function)
  289 |  cache = lookup_cache(_cache, sym->addr, true);
  |  ^
/<>/arch/arm/mcount-support.c:289:2: note: each undeclared
identifier is reported only once for each function it appears in
make[2]: *** [Makefile:28: /<>/arch/arm/mcount-support.op]
Error 1
make[1]: *** [Makefile:242: /<>/arch/arm/mcount-entry.op]
Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:14: binary-arch] Error 255



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: uftrace
Source-Version: 0.9.4-0.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version 

Bug#958196: marked as done (knitpy: Out-of-sync unstable/testing versions (non-source-only upload))

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 20:35:24 +
with message-id 
and subject line Bug#958196: fixed in knitpy 0.1.1~git20180430-2
has caused the Debian Bug report #958196,
regarding knitpy: Out-of-sync unstable/testing versions (non-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.)


-- 
958196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: knitpy
Severity: serious
Version: 0.1.1~git20180430-1
X-Debbugs-CC: mir...@debian.org

Dear Debian knitpy maintainer,

The latest upload of package knitpy was not a source-only upload. As a result,
this package did not migrate to Testing.

As announced in 
https://lists.debian.org/debian-devel-announce/2020/02/msg5.html ,
packages that are out-of-sync between Testing and Sid for more than 60 days
are considered to be release-critial. Please consider making another source-
only upload as described in https://wiki.debian.org/SourceOnlyUpload to fix
this issue.

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: knitpy
Source-Version: 0.1.1~git20180430-2
Done: Miriam Ruiz 

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

Debian distribution maintenance software
pp.
Miriam Ruiz  (supplier of updated knitpy 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, 20 Apr 2020 21:54:28 +0200
Source: knitpy
Architecture: source
Version: 0.1.1~git20180430-2
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz 
Changed-By: Miriam Ruiz 
Closes: 958196
Changes:
 knitpy (0.1.1~git20180430-2) unstable; urgency=medium
 .
   * Source-only upload. Closes: #958196
Checksums-Sha1:
 7e9a87fae2225e505be374790b514cf345768226 1856 knitpy_0.1.1~git20180430-2.dsc
 152c4fbefdfd0057013a4c01c2169265497da41e 5720 
knitpy_0.1.1~git20180430-2.debian.tar.xz
 b88f23cf611d0f1373ae302c011a105e9f2a34e4 7913 
knitpy_0.1.1~git20180430-2_amd64.buildinfo
Checksums-Sha256:
 98a9dfa0cb77c637834cac5c958007763743bbac74d1d91bb85cd43c049c6d9a 1856 
knitpy_0.1.1~git20180430-2.dsc
 55b4fc18427d6926820711debbddc2b77f7946dd4594039252012a96f41dd813 5720 
knitpy_0.1.1~git20180430-2.debian.tar.xz
 11e8522de8c20c5bc0740a3c752ee6267afc07361b64ff47b84dd8b763f862f3 7913 
knitpy_0.1.1~git20180430-2_amd64.buildinfo
Files:
 fb1e932125c449be80af421f572cf152 1856 python optional 
knitpy_0.1.1~git20180430-2.dsc
 237b33b7673e1a19915ea2dffa88ccdf 5720 python optional 
knitpy_0.1.1~git20180430-2.debian.tar.xz
 d69b1a662c39d22b3bef09923d1f16bb 7913 python optional 
knitpy_0.1.1~git20180430-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEde/EE4cQX/r0OS4CX45r4JKP+voFAl6d/voACgkQX45r4JKP
+vqYuQ/7BFWAQIh1QHLfv81cB9y/zflQ2OuEQHzie7gjJr+JEGA2aR8vD4hBdBya
g8lUoioR9e/hTM0JdydW9M0OMK1Y993jlkIJ5h3qlyD3/kr3DhdsBOiQ2x4wmXga
rQ6jHAIVl1R0yCZZYeBiJ7DnnZTLcpNKduI1R3OZ1VWPd7sLVO3K2bxlplLeQJNT
H4DUIVokhrIQ051qlXX+cDAQ8/c2FIpmvF2XrnhXkgoUo8wRUlKXOM/1SyjD1Uhe
MDj1Gs/Pxwa7v4XgOhLUo+Yc8QJBR9eGmue/oF5t7YvA1TVDd9gvwfc+v9Qg5bJ/
zvYmQSl8GORXd/Xnv94JRzrOwf7lGCPm4SUZ3MqR/WFeluGONbq1MkIvpzqPjIc2
iHXFdUYvZVbU/Bz4mBqFZCHH87tqeC2sPBXthvLufww08A03l+ibhJSbVw61+Yo+
+G+1x9AHL1t07s4r7VhgmC73PRJsWU2a9lWhfh0xKXfm1p06pe2jcYY/ew99lGXR
WND5x2WxJ+x7n54ZtYrP5B9Qnr8gaKKufLR+CWYqMopRcvH4dDFGrxWk2yM/fGdg
W+n80vQQlFVX6sFVNM4VmRpbiqekvOVKCxixspWJk6A7Vo0ZS7hh+w8ekRhD7+8k
PdxlpFZlX4hx9dL+mW7XO2ejHZP3whwtXizqNeAeyXPlMx6iRAA=
=n4gX
-END PGP SIGNATURE End Message ---

Processed: block 945699 with 927312

[Debian Bug Tracking System]

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

> block 945699 with 927312
Bug #945699 [src:pysiogame] pysiogame: Python2 removal in sid/bullseye
945699 was blocked by: 945632
945699 was blocking: 937441 937695
Added blocking bug(s) of 945699: 927312
> thanks
Stopping processing here.

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

Processed: block 912491 with 927312

[Debian Bug Tracking System]

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

> block 912491 with 927312
Bug #912491 [src:pysiogame] pysiogame: Please migrate to python3-pygame
912491 was not blocked by any bugs.
912491 was blocking: 937441 937695
Added blocking bug(s) of 912491: 927312
> thanks
Stopping processing here.

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

Processed: tagging 952006

[Debian Bug Tracking System]

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

> tags 952006 + fixed
Bug #952006 {Done: Michael Fladischer } [src:drf-extensions] 
drf-extensions: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.8 3.7" --system=custom 
"--test-args=PYTHONPATH='.:tests_app' {interpreter} /usr/bin/django-admin test 
--settings=settings tests_app" returned exit code 13
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Processed: Set bugs forwarded

[Debian Bug Tracking System]

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

> forwarded 955068 https://github.com/scikit-image/scikit-image/issues/4603
Bug #955068 [src:skimage] skimage: FTBFS with Sphinx 2.4: dh_sphinxdoc: error: 
debian/python-skimage-doc/usr/share/doc/python-skimage-doc/html/./../dev/_static/docversions.js
 is missing
Set Bug forwarded-to-address to 
'https://github.com/scikit-image/scikit-image/issues/4603'.
> thanks
Stopping processing here.

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

Bug#925754: Fixed in newer release of libopenshot / libopenshot-audio

[FeRD]

On Wed, 29 Jan 2020 10:08:55 +0100 Matthias Klose  wrote:
> libopenshot-audio 0.1.8 still fails to build

Quite right, sorry. libopenshot-audio-0.1.8 fixed building with GCC *less
than* 9,
but GCC9 coming along broke it again.

On Fedora / RPM Fusion we were building with commit 7001b68[1],
which was at the time an unreleased commit on the development branch.

However, since then both 0.1.9 and 0.2.0 have been released,
including fixes to build with GCC 9 and 10 respectively, IIRC.
(I know 0.2.0 builds with GCC 10 for sure, since I've done it myself.)

Current releases:

libopenshot-audio-0.2.0:
https://github.com/OpenShot/libopenshot-audio/archive/v0.2.0.tar.gz

libopenshot-0.2.5:
https://github.com/OpenShot/libopenshot/archive/v0.2.5.tar.gz

OpenShot 2.5.1 (openshot-qt):
https://github.com/OpenShot/openshot-qt/archive/v2.5.1.tar.gz


[1]:
https://github.com/OpenShot/libopenshot-audio/commit/7001b68787c0881a44bcafba98cccae509a31644

Bug#958318: src:python-setuptools: Incomplete debian/copyright

[Scott Kitterman]

Actually I was slightly wrong about the changes due to the upcoming policy 
change.  A copy of the license will still be needed in debian/copyright for

pkg_resources/_vendor/pyparsing.py:
setuptools/_vendor/pyparsing.py:
pkg_resources/_vendor/six.py:
setuptools/_vendor/six.py:

It's only the missing copyright attributions that wouldn't be a problem under 
the upcoming change.

Scott K

Processed: severity of 956956 is important

[Debian Bug Tracking System]

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

> severity 956956 important
Bug #956956 [src:lazarus] lazarus: flaky autopkgtest on arm64: 
EAccessViolation, EInOutError
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#958351: marked as done (plasma-mediacenter: autopkgtest needs update for new version of debhelper: failure on warning)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 22:14:01 +0200
with message-id <1807280.VexMbDOJx2@thyrus>
and subject line Re: Bug#958351: plasma-mediacenter: autopkgtest needs update 
for new version of debhelper: failure on warning
has caused the Debian Bug report #958351,
regarding plasma-mediacenter: autopkgtest needs update for new version of 
debhelper: failure on warning
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.)


-- 
958351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-mediacenter
Version: 5.7.5-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, debhel...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:debhelper

Dear maintainer(s),

With a recent upload of debhelper the autopkgtest of plasma-mediacenter
fails in testing when that autopkgtest is run with the binary packages
of debhelper from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
debhelper  from testing13
plasma-mediacenter from testing5.7.5-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. You can
prevent failure on output to stderr by add the "allow-stderr"
restriction if you don't want such failures.

Currently this regression is blocking the migration of debhelper to
testing [1]. Of course, debhelper shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
debhelper was intended and your package needs to update to the new
situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from debhelper should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/plasma-mediacenter/5068495/log.gz

autopkgtest [01:39:03]: test testsuite: [---
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.yfcatxg0/downtmp/build.Oe3/src/obj-x86_64-linux-gnu
Start 1: pmctest-medialibrarytest
1/9 Test #1: pmctest-medialibrarytest .   Passed   36.02 sec
Start 2: pmctest-singletonfactorytest
2/9 Test #2: pmctest-singletonfactorytest .   Passed0.02 sec
Start 3: pmctest-pmcmediatest
3/9 Test #3: pmctest-pmcmediatest .   Passed0.02 sec
Start 4: pmctest-mediatest
4/9 Test #4: pmctest-mediatest    Passed0.02 sec
Start 5: pmctest-mediacentertest
5/9 Test #5: pmctest-mediacentertest ..   Passed0.00 sec
Start 6: pmctest-itemcachetest
6/9 Test #6: pmctest-itemcachetest    Passed0.02 sec
Start 7: pmctest-pmcalbumtest
7/9 Test #7: pmctest-pmcalbumtest .   Passed0.02 sec
Start 8: pmctest-pmcartisttest
8/9 Test #8: pmctest-pmcartisttest    Passed0.02 sec
Start 9: pmctest-runtimedatatest
9/9 Test #9: pmctest-runtimedatatest ..   Passed0.02 sec

100% tests passed, 0 tests failed out of 9

Total Test time (real) =  36.16 sec
autopkgtest [01:39:39]: test testsuite: ---]
autopkgtest [01:39:40]: test testsuite:  - - - - - - - - - - results - -
- - - - - - - -
testsuiteFAIL stderr: dh_auto_test: warning: Compatibility
levels before 10 are deprecated (level 9 in use)
autopkgtest [01:39:40]: test testsuite:  - - - - - - - - - - stderr - -
- - - - - - - -
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: plasma-mediacenter
Version: 5.7.5-2

In data lunedì 20 aprile 2020 22:03:13 CEST, Paul Gevers ha scritto:
> Source: plasma-mediacenter
> Version: 5.7.5-1
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org, debhel...@packages.debian.org
> Tags: sid bullseye

Processed: xfig: autopkgtest needs update for new version of debhelper: hidden problem

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:debhelper
Bug #958352 [src:xfig] xfig: autopkgtest needs update for new version of 
debhelper: hidden problem
Added indication that 958352 affects src:debhelper

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

Bug#958352: xfig: autopkgtest needs update for new version of debhelper: hidden problem

[Paul Gevers]

Source: xfig
Version: 1:3.2.7b-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, debhel...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:debhelper

Dear maintainer(s),

With a recent upload of debhelper the autopkgtest of xfig fails in
testing when that autopkgtest is run with the binary packages of
debhelper from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
debhelper  from testing13
xfig   from testing1:3.2.7b-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. I don't spot
anything in there, you may want to avoid redirecting to /dev/null during
testing.

Currently this regression is blocking the migration of debhelper to
testing [1]. Of course, debhelper shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
debhelper was intended and your package needs to update to the new
situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from debhelper should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/x/xfig/5068355/log.gz

autopkgtest [01:32:00]: test xfig-testsuite: [---
Running autoconf
Running dh_auto_configure
Building required test programs
Running testsuite
/bin/bash './testsuite' AUTOTEST_PATH='/usr/bin'
## --- ##
## xfig 3.2.7b test suite. ##
## --- ##

Rudimentary tests

  1: Report version  ok
  2: Validate desktop file   ok

Integration tests

  3: ignore too many comment lines, ticket #47   ok

Unit tests

  4: Allow coordinates equal to INT_MIN  FAILED
(testsuite.at:82)
  5: Test round_coords() FAILED
(testsuite.at:87)

## - ##
## Test results. ##
## - ##

ERROR: All 5 tests were run,
2 failed unexpectedly.
## -- ##
## testsuite.log was created. ##
## -- ##

Please send `tests/testsuite.log' and all information you think might help:

   To: 
   Subject: [xfig 3.2.7b] testsuite: 4 5 failed

You may investigate any problem if you feel able to do so, in which
case the test suite provides a good starting point.  Its output may
be found below `tests/testsuite.dir'.

make: *** [Makefile:618: installcheck-local] Error 1
autopkgtest [01:32:05]: test xfig-testsuite: ---]
autopkgtest [01:32:05]: test xfig-testsuite:  - - - - - - - - - -
results - - - - - - - - - -
xfig-testsuite   FAIL stderr: ERROR: All 5 tests were run,



signature.asc
Description: OpenPGP digital signature

Bug#958351: plasma-mediacenter: autopkgtest needs update for new version of debhelper: failure on warning

[Paul Gevers]

Source: plasma-mediacenter
Version: 5.7.5-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, debhel...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:debhelper

Dear maintainer(s),

With a recent upload of debhelper the autopkgtest of plasma-mediacenter
fails in testing when that autopkgtest is run with the binary packages
of debhelper from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
debhelper  from testing13
plasma-mediacenter from testing5.7.5-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. You can
prevent failure on output to stderr by add the "allow-stderr"
restriction if you don't want such failures.

Currently this regression is blocking the migration of debhelper to
testing [1]. Of course, debhelper shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
debhelper was intended and your package needs to update to the new
situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from debhelper should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/plasma-mediacenter/5068495/log.gz

autopkgtest [01:39:03]: test testsuite: [---
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.yfcatxg0/downtmp/build.Oe3/src/obj-x86_64-linux-gnu
Start 1: pmctest-medialibrarytest
1/9 Test #1: pmctest-medialibrarytest .   Passed   36.02 sec
Start 2: pmctest-singletonfactorytest
2/9 Test #2: pmctest-singletonfactorytest .   Passed0.02 sec
Start 3: pmctest-pmcmediatest
3/9 Test #3: pmctest-pmcmediatest .   Passed0.02 sec
Start 4: pmctest-mediatest
4/9 Test #4: pmctest-mediatest    Passed0.02 sec
Start 5: pmctest-mediacentertest
5/9 Test #5: pmctest-mediacentertest ..   Passed0.00 sec
Start 6: pmctest-itemcachetest
6/9 Test #6: pmctest-itemcachetest    Passed0.02 sec
Start 7: pmctest-pmcalbumtest
7/9 Test #7: pmctest-pmcalbumtest .   Passed0.02 sec
Start 8: pmctest-pmcartisttest
8/9 Test #8: pmctest-pmcartisttest    Passed0.02 sec
Start 9: pmctest-runtimedatatest
9/9 Test #9: pmctest-runtimedatatest ..   Passed0.02 sec

100% tests passed, 0 tests failed out of 9

Total Test time (real) =  36.16 sec
autopkgtest [01:39:39]: test testsuite: ---]
autopkgtest [01:39:40]: test testsuite:  - - - - - - - - - - results - -
- - - - - - - -
testsuiteFAIL stderr: dh_auto_test: warning: Compatibility
levels before 10 are deprecated (level 9 in use)
autopkgtest [01:39:40]: test testsuite:  - - - - - - - - - - stderr - -
- - - - - - - -
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)



signature.asc
Description: OpenPGP digital signature

Processed: plasma-mediacenter: autopkgtest needs update for new version of debhelper: failure on warning

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:debhelper
Bug #958351 [src:plasma-mediacenter] plasma-mediacenter: autopkgtest needs 
update for new version of debhelper: failure on warning
Added indication that 958351 affects src:debhelper

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

Processed: devscripts: autopkgtest needs update for new version of debhelper

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:debhelper
Bug #958350 [src:devscripts] devscripts: autopkgtest needs update for new 
version of debhelper
Added indication that 958350 affects src:debhelper

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

Bug#958350: devscripts: autopkgtest needs update for new version of debhelper

[Paul Gevers]

Source: devscripts
Version: 2.20.2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, debhel...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:debhelper

Dear maintainer(s),

With a recent upload of debhelper the autopkgtest of devscripts fails in
testing when that autopkgtest is run with the binary packages of
debhelper from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
debhelper  from testing13
devscripts from testing2.20.2
all others from testingfrom testing

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

Currently this regression is blocking the migration of debhelper to
testing [1]. Of course, debhelper shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
debhelper was intended and your package needs to update to the new
situation.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/devscripts/5068354/log.gz

./test_package_lifecycle --installed
gpg: writing to '/tmp/gpg.H7gNz/secring.gpg'
gpg: armor header: Version: GnuPG v1
gpg: writing to '/tmp/gpg.H7gNz/pubring.gpg'
gpg: armor header: Version: GnuPG v1
gpg: using pgp trust model
/tmp/gpg.H7gNz/pubring.gpg
--
pub   rsa4096 2015-09-02 [SC]
  CF218F0E7EABF584B7E20402C77E2D6872543FAF
uid   [ unknown] uscan test key (no secret) 
sub   rsa4096 2015-09-02 [E]

test_debuild
ASSERT:standard output of debuild --no-conf --no-lintian
--preserve-envvar=PATH --preserve-envvar=PERL5LIB
--preserve-envvar=DEBFULLNAME --preserve-envvar=DEBEMAIL
--preserve-envvar=GNUPGHOME --set-envvar=NO_PKG_MANGLE=1 -k'uscan test
key (no secret) ' matches
/tmp/autopkgtest-lxc.8rtfp1uo/downtmp/build.7Up/src/test/package_lifecycle/debuild.txt\n
expected:<0> but was:<1>
10,11d9
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
< dh_clean: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
19d16
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
22,27d18
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
< dh_installdocs: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
< dh_installchangelogs: warning: Compatibility levels before 10 are
deprecated (level 9 in use)
< dh_compress: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
< dh_missing: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
< dh_installdeb: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
test_dscverify
test_dscextractControl
test_dscextractChangelog
test_debchange
test_list_unreleased
test_debuild2
ASSERT:standard output of debuild --no-conf --no-lintian
--preserve-envvar=PATH --preserve-envvar=PERL5LIB
--preserve-envvar=DEBFULLNAME --preserve-envvar=DEBEMAIL
--preserve-envvar=GNUPGHOME --set-envvar=NO_PKG_MANGLE=1 -k'uscan test
key (no secret) ' matches
/tmp/autopkgtest-lxc.8rtfp1uo/downtmp/build.7Up/src/test/package_lifecycle/debuild.txt\n
expected:<0> but was:<1>
10,11d9
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
< dh_clean: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
19d16
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
22,27d18
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
< dh_installdocs: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
< dh_installchangelogs: warning: Compatibility levels before 10 are
deprecated (level 9 in use)
< dh_compress: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
< dh_missing: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
< dh_installdeb: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
test_debuild_forcesign
ASSERT:standard output of debuild --no-conf --no-lintian
--preserve-envvar=PATH --preserve-envvar=PERL5LIB
--preserve-envvar=DEBFULLNAME --preserve-envvar=DEBEMAIL
--preserve-envvar=GNUPGHOME --set-envvar=NO_PKG_MANGLE=1 --force-sign
-k'uscan test key (no secret) ' matches
/tmp/autopkgtest-lxc.8rtfp1uo/downtmp/build.7Up/src/test/package_lifecycle/debuild.txt\n
expected:<0> but was:<1>
10,11d9
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
< dh_clean: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
19d16
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
22,27d18
< dh: warning: Compatibility levels before 10 are deprecated (level 9 in
use)
< dh_installdocs: warning: 

Bug#954132: marked as done (wine build depends on unicode-data (< 13) but 13.0.0-2 is to be installed)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 19:50:06 +
with message-id 
and subject line Bug#954132: fixed in wine 5.0-4
has caused the Debian Bug report #954132,
regarding wine build depends on unicode-data (< 13) but 13.0.0-2 is to be 
installed
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.)


-- 
954132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wine
Version: 5.0-3
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:wine : Depends: unicode-data (< 13) but 13.0.0-2 is to be installed
--- End Message ---
--- Begin Message ---
Source: wine
Source-Version: 5.0-4
Done: Jens Reyer 

We believe that the bug you reported is fixed in the latest version of
wine, 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.
Jens Reyer  (supplier of updated wine 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, 20 Apr 2020 20:49:41 +0200
Source: wine
Architecture: source
Version: 5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Jens Reyer 
Closes: 954132
Changes:
 wine (5.0-4) unstable; urgency=medium
 .
   * Switch to git branches 'bullseye' and 'upstream-stable'.
   * Support building with unicode-data 13 (closes: #954132).
 - Thanks to Graham Inggs.
Checksums-Sha1:
 fc316b1a5fb1fc79ff8dd59d1db1170ccf2fb67e 3940 wine_5.0-4.dsc
 ce5d512a89f9c62f24b140506a53c8f8698f9e4f 214280 wine_5.0-4.debian.tar.xz
 bb6aab3d5630eec0232f484a9fb1a49bbf49ce07 19899 wine_5.0-4_all.buildinfo
Checksums-Sha256:
 ab349416bee43ea01ef9c9dcc1e3c43ba8f1a7ccc46192537b8ae92133af07ee 3940 
wine_5.0-4.dsc
 093ef3ecfcb82a2d81bd3a9f32bb0ee4615d43853222e0a0715919601b7d41a0 214280 
wine_5.0-4.debian.tar.xz
 73894052a705c5024dc03a9dc0fc293453c9b24158878d29119e5eac313c4a97 19899 
wine_5.0-4_all.buildinfo
Files:
 d12f93d5e3e47edefd8439462d62fa96 3940 otherosfs optional wine_5.0-4.dsc
 936c5931fd98af8c3c67da8b9e664c42 214280 otherosfs optional 
wine_5.0-4.debian.tar.xz
 f524c03ad1ba454c21c2d7ab567cca6b 19899 otherosfs optional 
wine_5.0-4_all.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEo+4EaAPA6D5jhqo9YIQSAytXMHYFAl6d9zEACgkQYIQSAytX
MHaZthAAzC9U+7GJOjaacTn4VhI2NpK6iZWYiinSf3g393hX0KdJn4kYWg/jduYZ
DYWD85hI7jemEYt/SQ+/yp2Vm9zAgobecmixZ+niYZZNMWU9gGVt0m8jik1cQ39z
7qkK7pFe0axEYRXNnlXtxrVX+/tOcRNcU0WvZnn9agnxCsmPzZgFRrolBfnBVmMS
Zlce64z2oV1DTYT3k8nvuRlrBT/L5bUs4Qvy0dL8InerSeUUsdrz00JwPTXBZI6a
o3LhAnkh72P+ekaeIA3bGb0ulwAYMXklVjgslcwwWHLxk8g1uPVrsUu0oAsGIi44
BpMNcHP/X4WF7Ltm7fQjdu8bzjzdJGDIm+3DauYL8lWUECuq6InaN4cWXfmQVDyu
EoGHFmUtkMdLVLhXN3uvMYaQEFohU7GTxDztIN5B99aA8DuJuaHyWppOBzHJ10b+
E+/BE7xRX0IMnEEoGZtC0lJjfXcrN7tTxATX2SHxL6jqP8ZX4lZ/LgUCCk3LPW/B
rHqdDnapdTCSqpqIr5iUUF1E0Va35nGNLmUKxJj9UbDI5RGvm0YOJDYvSyXwPnzZ
bmAUkcPUz2dJO3jBAH9Q/4vUp2fQgPGorVUlWGeIrnVdVhosFrM+Fc0wzpVv/MC4
CIxJ1j9H5cDbSWyrQs/1HiYa0Mt9DKBMtNSol7BuyL1buIw5Ydw=
=L1ZH
-END PGP SIGNATURE End Message ---

Bug#954676: marked as done (pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 19:49:17 +
with message-id 
and subject line Bug#954676: fixed in pasdoc 0.15.0-2
has caused the Debian Bug report #954676,
regarding pasdoc: FTBFS: dh_installman: error: Could not determine section for 
./pasdoc.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.)


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary
>dh_testroot
>dh_prep
>dh_auto_install
>dh_install
>dh_installdocs
>dh_installchangelogs
>dh_installman
> dh_installman: error: Could not determine section for ./pasdoc.1
> dh_installman: error: Aborting due to earlier error
> make: *** [debian/rules:13: binary] Error 25

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Apr 2020 21:18:23 +0200
Source: pasdoc
Architecture: source
Version: 0.15.0-2
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Paul Gevers 
Closes: 954676
Changes:
 pasdoc (0.15.0-2) unstable; urgency=medium
 .
   * Use dh_install instead of dh_installman as help2man is broken (Closes:
 #954676)
   * Switch to compat 13 (via debhelper-compat B-D)
   * Bump standards to 4.5.0
   * Fix Vcs-Browser field
   * Add check for DEB_BUILD_OPTIONS in dh_auto_test override
   * Add R³: no
Checksums-Sha1:
 ffabf924c9c7a4c52864ab1974e1f6c4e7903018 1779 pasdoc_0.15.0-2.dsc
 b5d76aa8d7fda727af79ba85cf833b728ac23769 6256 pasdoc_0.15.0-2.debian.tar.xz
Checksums-Sha256:
 adbb5ae032b9115d77530bc0b4804cbffc1e8389926c8423146b1165843273e0 1779 
pasdoc_0.15.0-2.dsc
 74ad7cc837bf5995c86316802ce8630e5aebb3942c9acacd57cc2a7f593c5960 6256 
pasdoc_0.15.0-2.debian.tar.xz
Files:
 b1057d4e307057b1b950ea8daa1d8d77 1779 doc optional pasdoc_0.15.0-2.dsc
 f18d1156a8e413d3b45189511e95af42 6256 doc optional 
pasdoc_0.15.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl6d914ACgkQnFyZ6wW9
dQrWVwf/TVL9Txg1yEp5L4BWRlXaeCrRy075wIJ0oGy7ZhP+PLBGJCBknF99EaZ5
DMXWwbAHJj9WjL1VFI0aZUgs+bJi9FW+lHfaW8VhEOFyg9rE7WTFn6b/gqnklRIi
ELtFtM3imqHrrGdnUfnXTSM35Zcz+hyK6eWjcYVXyzni9p0rGkymfa9Rzfmgmrpl
kbT19zib+JE/gCrAJHOPeRvqdFL9ExaZT2Jg9bULEWQWinKy0Tgz/ET1w1Kwi7l1
jnvp73EiFrLgTqSycXclGLD9rUkG46cOaSEmZZWCH8A7GINUisQteLh6buw9szMY
smvrg9B5Av2U867JbXweLfZue6A5yg==
=4KUi
-END PGP SIGNATURE End Message ---

Bug#954676: pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1

[Paul Gevers]

Dear Michalis,

On 30-03-2020 14:11, Michalis Kamburelis wrote:
> The PasDoc manpage in Debian is done using
> 
> help2man --output=pasdoc.1 --name="documentation tool for Pascal source code" 
> \
>  --no-info bin/pasdoc

I just uploaded a new version of pasdoc to the Debian archive, but in
the process I filed two bugs, one against debhelper (bug #958343) and
one against help2man (bug #958345). It turns out that a recent help2man
started to create invalid .TH lines in the produced man file. It seems
to be very much related to what pasdoc output on the first line.
Apparently that's a bit unconventional.

No need to adapt, as I work around it now, but you *may* want to be in
line with other programs.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Re: Massive memory leak in openshot 2.4.4 leads to freeze

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/OpenShot/openshot-qt/issues/2237
Bug #955975 [openshot-qt] Massive memory leak in openshot 2.4.4 leads to freeze
Set Bug forwarded-to-address to 
'https://github.com/OpenShot/openshot-qt/issues/2237'.
> forwarded 925754 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754
Bug #925754 [src:libopenshot] libopenshot: ftbfs with GCC-9
Set Bug forwarded-to-address to 
'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754'.
> tags 925754 + fixed-upstream ftbfs
Bug #925754 [src:libopenshot] libopenshot: ftbfs with GCC-9
Added tag(s) fixed-upstream and ftbfs.

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

Bug#955975: Massive memory leak in openshot 2.4.4 leads to freeze

[John Scott]

Control: forwarded -1 https://github.com/OpenShot/openshot-qt/issues/2237
Control: forwarded 925754 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754
Control: tags 925754 + fixed-upstream ftbfs

Hi,
> Version: 1:2.4.4-dmo4

OpenShot 2.4.4 isn't part of Debian yet. It seems you've probably gotten your
package from a third-party repository. Have you tried the 2.4.3 package? If
you're using Buster it should be available. OpenShot is broken on newer
releases for the time being however.

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

Bug#955656: marked as done (python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib')

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 17:36:07 +
with message-id 
and subject line Bug#955656: fixed in python-cobra 0.18.0-1
has caused the Debian Bug report #955656,
regarding python-cobra: FTBFS: E   ModuleNotFoundError: No module named 
'matplotlib'
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.7 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7_cobra/build/cobra
> copying cobra/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra
> copying cobra/exceptions.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra
> creating /<>/.pybuild/cpython3_3.7_cobra/build/cobra/util
> copying cobra/util/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/util
> copying cobra/util/array.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/util
> copying cobra/util/util.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/util
> copying cobra/util/solver.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/util
> copying cobra/util/context.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/util
> creating /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/configuration.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/object.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/species.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/singleton.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/gene.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/dictlist.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/metabolite.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/reaction.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/model.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/formula.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> copying cobra/core/solution.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/core
> creating 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/geometric.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/room.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/loopless.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/deletion.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/gapfilling.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/phenotype_phase_plane.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/variability.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/sampling.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/parsimonious.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/summary.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/moma.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> copying cobra/flux_analysis/reaction.py -> 
> /<>/.pybuild/cpython3_3.7_cobra/build/cobra/flux_analysis
> creating /<>/.pybuild/cpython3_3.7_cobra/build/cobra/test
> copying cobra/test/__init__.py -> 
> 

Bug#955656: python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib'

[Andreas Tille]

Hi Pierre,

a, now I've got it!  Great it runs now.  Uploaded thanks to
your hint, Andreas.

On Mon, Apr 20, 2020 at 06:24:00PM +0200, Pierre Gruet wrote:
> Hi Andreas,
> 
> Le 20/04/2020 à 12:08, Andreas Tille a écrit :
> > 
> > Thanks a lot for checking.  The issue is that we can not build the recent
> > upstream version as I wrote in
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10
> > 
> > Most probably that's *not* a problem of python-cobra but rather of
> > python2-sbml5 (I think Liubov in CC found this out but I simply forgot). 
> > If you have any spare resources could you please verify this?  Please
> > checkout latest Git
> > 
> >https://salsa.debian.org/med-team/python-cobra
> >
> 
> Sorry for maybe explaining things unclearly in my previous email, but what
> you suggest is what I did: I took your packaging of version 0.18.0-1 in
> Salsa, and I could build it without a problem in a sid chroot.
> Some test have ``xfail'' result, but none has ``fail''.
> 
> I understand the problem you showed in
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10
> 
> means some module could not be loaded, but as I did not encounter this
> problem while building, I wrote to you this morning in order to try to
> understand the reason.
> 
> >
> > Kind regards and thanks again for your attempt to help
> > 
> > Andreas.
> > 
> 
> I hope this can help, or at least that we can understand the reason why we
> have different results at a 16-day interval.
> 
> All the best,
> Pierre
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#958313: libnitrokey: FTBFS on mipsel: symbol changes

[Szczepan Zalega | Nitrokey]

On 4/20/20 2:59 PM, Ivo De Decker wrote:
> package: src:libnitrokey
> version: 3.4.1-4
> severity: serious
> tags: ftbfs
> 
> A binnmu of libnitrokey on mipsel (to bring the versions in sync for
> multiarch) failed:
> 
> https://buildd.debian.org/status/package.php?p=libnitrokey
> 
> Note that only mipsel was rebuilt (because the binNMU version was lower), so
> it's possible that this issue isn't limited to mipsel.
> 

Hi!

I do not have much experience in this kind of errors, but for me from
the symbols diff it looks like the change comes from building with C++17
standard set (is it not now the default for GCC?). CMake has it set to
C++14 and units are built with it as far as I see, yet the C++17
prefixed symbol is shown:
```
-
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
3.4.1
+
_ZNSt6vectorIhSaIhEE17_M_realloc_insertIJhEEEvN9__gnu_cxx17__normal_iteratorIPhS1_EEDpOT_@Base
3.4.1-4+b1
```

-- 
Best regards,
Szczepan

Bug#951918: marked as done (django-housekeeping: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 16:48:38 +
with message-id 
and subject line Bug#951918: fixed in django-housekeeping 1.1+git20200402-1
has caused the Debian Bug report #951918,
regarding django-housekeeping: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.8 3.7" returned exit code 13
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.)


-- 
951918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-housekeeping
Version: 1.1-1.1
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):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> running config
> I: pybuild base:217: python3.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.8 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/tests.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/models.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/toposort.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/task.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/run.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/report.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping
> creating 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management
> copying django_housekeeping/management/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management
> creating 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management/commands
> copying django_housekeeping/management/commands/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management/commands
> copying django_housekeeping/management/commands/housekeeping.py -> 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build/django_housekeeping/management/commands
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/tests.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/models.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/toposort.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/task.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/run.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> copying django_housekeeping/report.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping
> creating 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management
> copying django_housekeeping/management/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management
> creating 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management/commands
> copying django_housekeeping/management/commands/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management/commands
> copying django_housekeeping/management/commands/housekeeping.py -> 
> /<>/.pybuild/cpython3_3.7_django-housekeeping/build/django_housekeeping/management/commands
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.8_django-housekeeping/build; python3.8 
> -m 

Bug#955656: python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib'

[Pierre Gruet]

Hi Andreas,

Le 20/04/2020 à 12:08, Andreas Tille a écrit :
> 
> Thanks a lot for checking.  The issue is that we can not build the recent
> upstream version as I wrote in
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10
> 
> Most probably that's *not* a problem of python-cobra but rather of
> python2-sbml5 (I think Liubov in CC found this out but I simply forgot). 
> If you have any spare resources could you please verify this?  Please
> checkout latest Git
> 
>https://salsa.debian.org/med-team/python-cobra
>

Sorry for maybe explaining things unclearly in my previous email, but what
you suggest is what I did: I took your packaging of version 0.18.0-1 in
Salsa, and I could build it without a problem in a sid chroot.
Some test have ``xfail'' result, but none has ``fail''.

I understand the problem you showed in

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10

means some module could not be loaded, but as I did not encounter this
problem while building, I wrote to you this morning in order to try to
understand the reason.

>
> Kind regards and thanks again for your attempt to help
> 
> Andreas.
> 

I hope this can help, or at least that we can understand the reason why we
have different results at a 16-day interval.

All the best,
Pierre

Bug#958335: python3-caffe-cuda: No longer installable, please upgrade

[Celelibi]

Package: python3-caffe-cuda
Version: 1.0.0+git20180821.99bd997-2+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

python3-caffe-cuda is uninstallable because of its dependencies. Both
direct and indirect.

It depends on python3 << 3.8. While Python 3.8 is now the default
version.

There seem to be similar issues with the other dependencies.

Best regards,
Celelibi


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

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

Versions of packages python3-caffe-cuda depends on:
ii  cython3 0.29.14-1
ii  libboost-python1.67.0   1.67.0-17
ii  libboost-system1.67.0   1.67.0-17
ii  libc6   2.30-4
pn  libcaffe-cuda1  
ii  libgcc-s1 [libgcc1] 10-20200411-1
ii  libgcc1 1:10-20200411-1
ii  libgoogle-glog0v5   0.4.0-1
pn  libprotobuf17   
pn  libpython3.7
ii  libstdc++6  10-20200411-1
ii  python3 3.8.2-3
ii  python3-dateutil2.7.3-3
ii  python3-gflags  1.5.1-7
ii  python3-h5py2.10.0-2+b1
ii  python3-ipython 7.13.0-1
pn  python3-leveldb 
ii  python3-matplotlib  3.1.2-2
ii  python3-networkx2.4-3
ii  python3-nose1.3.7-5
ii  python3-numpy [python3-numpy-abi9]  1:1.17.4-5
ii  python3-pandas  0.25.3+dfsg-9
ii  python3-pil 6.2.1-2+b1
ii  python3-protobuf3.11.4-4
ii  python3-scipy   1.3.3-3+b1
ii  python3-six 1.14.0-2
ii  python3-skimage 0.16.2-2
ii  python3-yaml5.3.1-1+b1

python3-caffe-cuda recommends no packages.

python3-caffe-cuda suggests no packages.

Bug#958223: marked as done (eslint: autopkgtest failure: ESLint couldn't find the plugin "eslint-plugin-eslint-plugin")

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 16:03:59 +
with message-id 
and subject line Bug#958223: fixed in eslint 5.16.0~dfsg-1
has caused the Debian Bug report #958223,
regarding eslint: autopkgtest failure: ESLint couldn't find the plugin 
"eslint-plugin-eslint-plugin"
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.)


-- 
958223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eslint
Version: 5.0.1~dfsg-4
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: always-fails

Dear maintainer(s),

With a recent upload of eslint you added an autopkgtest, great. However,
it fails. I copied some of the output at the bottom of this report.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/e/eslint/4723665/log.gz

autopkgtest [09:13:37]: test command2:  NODE_PATH=tools find lib conf
bin tests/lib/util tests/lib/config tests/lib/code-path-analysis
tests/lib/formatters tests/lib/testers tests/lib/rules tests/bin
tests/lib/*.js -type f -name '*.js' -not -path
tests/lib/code-path-analysis/code-path.js -exec eslint --format tap
--report-unused-disable-directives {} +
autopkgtest [09:13:37]: test command2: [---

Oops! Something went wrong! :(

ESLint: 5.0.1.
ESLint couldn't find the plugin "eslint-plugin-eslint-plugin". This can
happen for a couple different reasons:

1. If ESLint is installed globally, then make sure
eslint-plugin-eslint-plugin is also installed globally. A
globally-installed ESLint cannot find a locally-installed plugin.

2. If ESLint is installed locally, then it's likely that the plugin
isn't installed correctly. Try reinstalling by running the following:

npm i eslint-plugin-eslint-plugin@latest --save-dev

Path to ESLint package: /usr/share/nodejs/eslint

If you still can't figure out the problem, please stop by
https://gitter.im/eslint/eslint to chat with the team.

autopkgtest [09:13:39]: test command2: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: eslint
Source-Version: 5.16.0~dfsg-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated eslint 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, 20 Apr 2020 17:10:54 +0200
Source: eslint
Architecture: source
Version: 5.16.0~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 958223
Changes:
 eslint (5.16.0~dfsg-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release(s)
 .
   [ Jonas Smedegaard ]
   * drop patches cherry-picked upstream now applied;
 drop patch 2001 obsoleted by upstream refactoring
   * add patch cherry-picked upstream to use newer eslint-utils
   * add patch 2001 to downgrade babel-code-frame
   * update patch 2004
   * unfuzz and update patches
   * (build-)depend on node-eslint-utils
   * copyright: strip a generated file when repackaging source
   * tighten to build-depend versioned on node-eslint-plugin-node
   * fix have helper script tap-todo fail if no tests were run
   * update workarounds for failing tests
   * stop tolerate test failure when targeting experimental
   * autopkgtest: fix depend on node-eslint-plugin-eslint-plugin;
 closes: bug#958223, thanks to Paul Gevers
Checksums-Sha1:
 7a8f48e666fe3a41940b66555e5e29123d8f8f18 3354 eslint_5.16.0~dfsg-1.dsc
 f3d3400cda258acf97034dc7356ae86ee19b0717 1000888 eslint_5.16.0~dfsg.orig.tar.xz
 ac1f79ac677b9bf3eaa40c194423c89b3df0fdc2 26928 

Bug#958312: Confirmation that the patch works

[Arnaud Rebillout]

Thanks for the detailed bug report, I'm rebuilding a package to check 
that it's all good on my side. I'll probably upload a new revision tomorrow.


On 4/20/20 8:33 PM, Patrick Georgi wrote:

To follow up on my earlier statement that I'd test the patch: the deb sources + 
that patch don't show the segfault on my system anymore.

Bug#958318: src:python-setuptools: Incomplete debian/copyright

[Scott Kitterman]

Package: src:python-setuptools
Version: 40.8.0-1
Severity: serious
Justification: Policy 2.3

While reviewing src:setuptools in New, I noticed a number of omissions
from debian/copyright which apply to this package as well.

Copyright and license information from the following files is missing.
Under current Debian Policy (4.5.0) these are all required.  An upcoming
policy change will relax the requirement so that license text and
copyright attributions that are shipped in text form in the package are
not required to be in debian/copyright.  Once that change is part of
policy, then only the changes relative to LICENSE and pkg_resources/_vendor/
appdirs.py will be required (the license text is missing from
appdirs.py).

Scott K

LICENSE:
Copyright (C) 2016 Jason R Coombs 

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

pkg_resources/_vendor/pyparsing.py:
setuptools/_vendor/pyparsing.py:
# Copyright (c) 2003-2018  Paul T. McGuire

pkg_resources/_vendor/six.py:
setuptools/_vendor/six.py:
# Copyright (c) 2010-2015 Benjamin Peterson

# Copyright (c) 2010-2015 Benjamin Peterson
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in all
# copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.


pkg_resources/_vendor/appdirs.py:
# Copyright (c) 2005-2010 ActiveState Software Inc.
# Copyright (c) 2013 Eddy Petrișor

According to the link in the file, the license is:

# This is the MIT license

Copyright (c) 2010 ActiveState Software Inc.

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Bug#958312: Confirmation that the patch works

[Patrick Georgi]

To follow up on my earlier statement that I'd test the patch: the deb sources + 
that patch don't show the segfault on my system anymore.

Bug#937144: [Python-modules-team] Bug#938756: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

[Scott Kitterman]

On Monday, April 20, 2020 8:51:10 AM EDT peter green wrote:
> On 20/04/2020 08:57, Thomas Goirand wrote:
> >> Option 1: fix all four packages to be python 2 free.
> >> 
> >> Option 2: Remove python2 stuff from traceback2, python-funcsigs and
> >> numba. Break the dependencies of nipype in sid.
> >> 
> >> Option 3: Remove python2 stuff from traceback2, modify python-funcsigs
> >> so it still builds the python2 package but does not run tests with
> >> python 2.
> > 
> > Funcsigs is a backport of the PEP 362 function signature features from
> > Python 3.3's inspect module.
> 
> Thanks for the info.
> 
> > Python 2 has never been removed from this
> > package. Though instead, we shall remove this source package entirely
> > from Debian.
> 
> # Broken Depends:
> nipype: python-nipype
> pytest: pypy-pytest
> python-logfury: python3-logfury
> python-oslo.utils: python3-oslo.utils
> 
> # Broken Build-Depends:
> beaker: python3-funcsigs
> kombu: python3-funcsigs
> nipype: python-funcsigs
> pagure: python3-funcsigs
> pytest: pypy-funcsigs
> python-oslo.log: python3-funcsigs
> python-oslo.utils: python3-funcsigs (>= 0.4)
> ripe-atlas-cousteau: python3-funcsigs
> 
> If what you say is correct then it sounds like the python3-funcsigs revese
> depedencies could be dealt with fairly easily.
> 
> But that still leaves the question of what to do about the dependency of
> pytest on pypy-funcsigs ? should pypy modules be removed from pytest and
> it's reverse-dependencies in the same way that regular python2 modules
> were? how feasible is that? are pypy-* packages only useful with python2
> pypy or are they also useful with python3 pypy?

The Python 2 pypy variant isn't being dropped, so if pypy-funcsigs has 
rdepends, it should probably stay.  In the interest of maintaining momentum on 
the Python 2, I think it would be better to just drop python-funcsigs and sort 
out the future of pypy-funcsigs and python3-funcsigs later.

> > Traceback2 *already* has Python 2 support removed in Sid. I uploaded
> > this on the 21st of march, pressured by its potential autoremoval.
> 
> Sorry it seems I got my package names mixed up when writing the list of
> options. I said traceback2 where I meant unittest2.
> > There's no other choice but to fix nipype at this point, or wait until
> > it gets autoremoved from Testing.
> 
> It already was autoremoved from testing.
> 
> >   IMO, it'd be fine to NMU a new
> > upstream release if you contact the current maintainer and/or using the
> > delayed queue.
> 
> A new upstream release for a package I do not use is not something I feel
> comfortable NMUing. I was hoping that my initial mail would prompt action
> on the parts of the nipype maintainers but if they don't respond then I
> tend towards ignoring breakage of sid-only packages that need non-trivial
> fixes.

The current nipype maintainer is well aware of the issue.  AIUI they are 
holding off on uploading to Unstable until they are confident the Python 3 port 
is sufficiently mature.  Since it's already out of Testing and uninstallable in 
Sid, you can ignore causing further breakage (it won't get any more 
uninstallable).

> > IMO, we should get unittest2 free of Py2 support ASAP, and open an FTP
> > team bug to get funcsigs removed from Debian.

I think the original option 2 still makes the most sense.

Scott K


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

Bug#955660: marked as done (mender-client: FTBFS: app.DeploymentHook does not implement "github.com/mendersoftware/log/vendor/github.com/sirupsen/logrus".Hook (wrong type for Fire method))

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 13:04:23 +
with message-id 
and subject line Bug#955660: fixed in mender-client 2.2.0-4
has caused the Debian Bug report #955660,
regarding mender-client: FTBFS: app.DeploymentHook does not implement 
"github.com/mendersoftware/log/vendor/github.com/sirupsen/logrus".Hook (wrong 
type for Fire method)
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -O--buildsystem=golang -- \
>   -ldflags "-X github.com/mendersoftware/mender/conf.Version=2.2.0-3"
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 -ldflags "-X 
> github.com/mendersoftware/mender/conf.Version=2.2.0-3" 
> github.com/mendersoftware/mender github.com/mendersoftware/mender/app 
> github.com/mendersoftware/mender/cli github.com/mendersoftware/mender/client 
> github.com/mendersoftware/mender/client/test 
> github.com/mendersoftware/mender/conf 
> github.com/mendersoftware/mender/datastore 
> github.com/mendersoftware/mender/device 
> github.com/mendersoftware/mender/installer 
> github.com/mendersoftware/mender/inventory 
> github.com/mendersoftware/mender/statescript 
> github.com/mendersoftware/mender/store 
> github.com/mendersoftware/mender/system 
> github.com/mendersoftware/mender/system/testing 
> github.com/mendersoftware/mender/tests github.com/mendersoftware/mender/utils
> math/bits
> runtime/internal/sys
> internal/cpu
> runtime/internal/atomic
> runtime/internal/math
> unicode/utf8
> internal/race
> sync/atomic
> unicode
> internal/bytealg
> math
> internal/testlog
> container/list
> encoding
> unicode/utf16
> internal/nettrace
> runtime/cgo
> runtime
> crypto/subtle
> crypto/internal/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/subtle
> github.com/bmatsuo/lmdb-go/internal/lmdbarch
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> io
> strconv
> internal/oserror
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> bytes
> reflect
> bufio
> strings
> hash
> hash/crc32
> internal/syscall/unix
> time
> crypto
> crypto/internal/randutil
> crypto/hmac
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> path
> regexp/syntax
> vendor/golang.org/x/text/transform
> golang.org/x/text/transform
> internal/poll
> context
> internal/fmtsort
> encoding/binary
> regexp
> github.com/remyoudompheng/go-liblzma
> os
> encoding/base64
> github.com/mendersoftware/log/vendor/golang.org/x/sys/unix
> fmt
> net
> github.com/mendersoftware/log/vendor/github.com/mendersoftware/scopestack
> encoding/json
> log
> compress/flate
> github.com/mendersoftware/log/vendor/github.com/sirupsen/logrus
> crypto/cipher
> compress/gzip
> crypto/aes
> crypto/des
> math/big
> crypto/sha512
> crypto/ed25519/internal/edwards25519
> crypto/md5
> crypto/sha1
> crypto/sha256
> encoding/hex
> encoding/pem
> path/filepath
> net/url
> crypto/elliptic
> encoding/asn1
> crypto/rand
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> crypto/x509/pkix
> crypto/ecdsa
> vendor/golang.org/x/crypto/cryptobyte
> io/ioutil
> vendor/golang.org/x/crypto/chacha20
> vendor/golang.org/x/crypto/poly1305
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/curve25519
> github.com/bmatsuo/lmdb-go/lmdb
> vendor/golang.org/x/crypto/chacha20poly1305
> log/syslog
> crypto/x509
> github.com/mendersoftware/log/vendor/github.com/sirupsen/logrus/hooks/syslog
> github.com/pkg/errors
> github.com/mendersoftware/log
> github.com/davecgh/go-spew/spew
> github.com/pmezard/go-difflib/difflib
> github.com/stretchr/objx
> gopkg.in/yaml.v2
> crypto/tls
> vendor/golang.org/x/text/unicode/bidi
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/text/unicode/norm
> net/textproto
> vendor/golang.org/x/net/http2/hpack
> vendor/golang.org/x/net/idna
> mime
> mime/quotedprintable
> net/http/httptrace
> mime/multipart
> net/http/internal
> vendor/golang.org/x/net/http/httpguts
> vendor/golang.org/x/net/http/httpproxy
> flag
> golang.org/x/text/unicode/bidi
> net/http
> golang.org/x/text/unicode/norm
> golang.org/x/text/secure/bidirule
> golang.org/x/net/http2/hpack
> os/user
> golang.org/x/net/idna
> golang.org/x/net/http/httpguts
> os/exec

Bug#958312: docker.io: signal SIGSEGV: segmentation violation shortly after starting the daemon

[Patrick Georgi]

Package: docker.io
Version: 19.03.7+dfsg1-1
Severity: critical
Tags: patch upstream
Justification: breaks unrelated software

Dear Maintainer,

The update to 19.03.7 led to a reproducible issue with docker shortly after
starting the daemon:

Apr 20 14:30:27 fsn dockerd[488555]: panic: runtime error: invalid memory 
address or nil pointer dereference
Apr 20 14:30:27 fsn dockerd[488555]: [signal SIGSEGV: segmentation violation 
code=0x1 addr=0x11 pc=0x55a05b5ac02b]
Apr 20 14:30:27 fsn dockerd[488555]: goroutine 2029 [running]:
Apr 20 14:30:27 fsn dockerd[488555]: 
github.com/docker/libnetwork.(*resolver).ServeDNS(0xc000e38380, 0x55a05cbea2c0, 
0xc0014b94a0, 0xc0018bd5f0)
Apr 20 14:30:27 fsn dockerd[488555]: 
/build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/docker/libnetwork/resolver.go:487
 +0x79b
Apr 20 14:30:27 fsn dockerd[488555]: 
github.com/miekg/dns.(*Server).serveDNS(0xc000dab200, 0xc000c0f200, 0x21, 
0x200, 0xc0014b94a0)
Apr 20 14:30:27 fsn dockerd[488555]: 
/build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/miekg/dns/server.go:609
 +0x2e2
Apr 20 14:30:27 fsn dockerd[488555]: 
github.com/miekg/dns.(*Server).serveUDPPacket(0xc000dab200, 0xc0011cf6b0, 
0xc000c0f200, 0x21, 0x200, 0xc00020a7e0, 0xc000fa7c00)
Apr 20 14:30:27 fsn dockerd[488555]: 
/build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/miekg/dns/server.go:549
 +0xb4
Apr 20 14:30:27 fsn dockerd[488555]: created by 
github.com/miekg/dns.(*Server).serveUDP
Apr 20 14:30:27 fsn dockerd[488555]: 
/build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/miekg/dns/server.go:479
 +0x28c
Apr 20 14:30:27 fsn systemd[1]: docker.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT

Still testing out, but
https://github.com/SamWhited/libnetwork/commit/bea32b018c874ef35396ef46a3908ca0f9367d76
was merged in upstream, seems relevant and is part of upstream 19.03.8

So either apply that to 19.3.7 or update to 19.3.8?

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

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 docker.io depends on:
ii  adduser 3.118
ii  iptables1.8.4-3
ii  libc6   2.30-4
ii  libdevmapper1.02.1  2:1.02.167-1+b1
ii  libltdl72.4.6-14
ii  libnspr42:4.25-1
ii  libnss3 2:3.51-1
ii  libseccomp2 2.4.3-1+b1
ii  libsystemd0 245.5-1
ii  lsb-base11.1.0
ii  runc1.0.0~rc10+dfsg1-1
ii  tini0.18.0-1+b1

Versions of packages docker.io recommends:
ii  ca-certificates  20190110
ii  cgroupfs-mount   1.4
ii  git  1:2.26.1-1
ii  needrestart  3.5-1
ii  xz-utils 5.2.4-1+b1

Versions of packages docker.io suggests:
pn  aufs-tools 
ii  btrfs-progs5.6-1
ii  debootstrap1.0.123
pn  docker-doc 
ii  e2fsprogs  1.45.6-1
pn  rinse  
ii  xfsprogs   5.4.0-1
ii  zfsutils-linux [zfsutils]  0.8.3-2

-- no debconf information
>From bea32b018c874ef35396ef46a3908ca0f9367d76 Mon Sep 17 00:00:00 2001
From: Sam Whited 
Date: Wed, 18 Mar 2020 12:06:23 -0400
Subject: [PATCH] Fixes a panic in the DNS resolver

Under certain conditions it appears that the DNS response and returned
error can be nil. When this happens, checking resp.Truncated results in
a nil panic so we must first check that the response is not nil before
checking if a truncated response was received.

See moby/moby#40715

Signed-off-by: Sam Whited 
---
 resolver.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/resolver.go b/resolver.go
index 7e02a37a5b..e32522a254 100644
--- a/resolver.go
+++ b/resolver.go
@@ -484,7 +484,7 @@ func (r *resolver) ServeDNS(w dns.ResponseWriter, query 
*dns.Msg) {
resp, err = co.ReadMsg()
// Truncated DNS replies should be sent to the client 
so that the
// client can retry over TCP
-   if err != nil && !resp.Truncated {
+   if err != nil && (resp != nil && !resp.Truncated) {
r.forwardQueryEnd()
logrus.Debugf("[resolver] read from DNS server 
failed, %s", err)
continue

Bug#958313: libnitrokey: FTBFS on mipsel: symbol changes

[Ivo De Decker]

package: src:libnitrokey
version: 3.4.1-4
severity: serious
tags: ftbfs

Hi,

A binnmu of libnitrokey on mipsel (to bring the versions in sync for
multiarch) failed:

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

Note that only mipsel was rebuilt (because the binNMU version was lower), so
it's possible that this issue isn't limited to mipsel.

Cheers,

Ivo

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

[peter green]

On 20/04/2020 08:57, Thomas Goirand wrote:

Option 1: fix all four packages to be python 2 free.

Option 2: Remove python2 stuff from traceback2, python-funcsigs and
numba. Break the dependencies of nipype in sid.

Option 3: Remove python2 stuff from traceback2, modify python-funcsigs
so it still builds the python2 package but does not run tests with
python 2.

Funcsigs is a backport of the PEP 362 function signature features from
Python 3.3's inspect module.

Thanks for the info.

Python 2 has never been removed from this
package. Though instead, we shall remove this source package entirely
from Debian.

# Broken Depends:
nipype: python-nipype
pytest: pypy-pytest
python-logfury: python3-logfury
python-oslo.utils: python3-oslo.utils

# Broken Build-Depends:
beaker: python3-funcsigs
kombu: python3-funcsigs
nipype: python-funcsigs
pagure: python3-funcsigs
pytest: pypy-funcsigs
python-oslo.log: python3-funcsigs
python-oslo.utils: python3-funcsigs (>= 0.4)
ripe-atlas-cousteau: python3-funcsigs

If what you say is correct then it sounds like the python3-funcsigs revese 
depedencies could be dealt with fairly easily.

But that still leaves the question of what to do about the dependency of pytest 
on pypy-funcsigs ? should pypy modules be removed from pytest and it's 
reverse-dependencies in the same way that regular python2 modules were? how 
feasible is that? are pypy-* packages only useful with python2 pypy or are they 
also useful with python3 pypy?


Traceback2 *already* has Python 2 support removed in Sid. I uploaded
this on the 21st of march, pressured by its potential autoremoval.


Sorry it seems I got my package names mixed up when writing the list of 
options. I said traceback2 where I meant unittest2.


There's no other choice but to fix nipype at this point, or wait until
it gets autoremoved from Testing.

It already was autoremoved from testing.

  IMO, it'd be fine to NMU a new
upstream release if you contact the current maintainer and/or using the
delayed queue.

A new upstream release for a package I do not use is not something I feel 
comfortable NMUing. I was hoping that my initial mail would prompt action on 
the parts of the nipype maintainers but if they don't respond then I tend 
towards ignoring breakage of sid-only packages that need non-trivial fixes.


IMO, we should get unittest2 free of Py2 support ASAP, and open an FTP
team bug to get funcsigs removed from Debian.

Cheers,

Thomas Goirand (zigo)

Processed: Bug#955660 marked as pending in mender-client

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #955660 [src:mender-client] mender-client: FTBFS: app.DeploymentHook does 
not implement 
"github.com/mendersoftware/log/vendor/github.com/sirupsen/logrus".Hook (wrong 
type for Fire method)
Added tag(s) pending.

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

Bug#955660: marked as pending in mender-client

[Lluis M. Campos]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/go-team/packages/mender-client/-/commit/1269df9f0844a3b0e93771a990b0990d310f3cbc


Add patches to switch to upstream sirupsen/logrus v1.5

Gbp-Dch: Full
Closes: #955660


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/955660

Bug#956365: redmine: unmet dependencies

[duck]

Control: severity -1 normal
Control: tag -1 + unreproducible


Quack,

I just made a fresh install on today's unstable and cannot reproduce 
your installation problem.


Involed libraried are:
Setting up ruby-roadie-rails (1.3.0-2) ...
Setting up ruby-roadie (4.0.0-1) ...
Setting up ruby-actionpack-xml-parser (2.0.1-3) ...

So maybe something was amiss in unstable at the time, or your gitlab 
installation added local gems, but this worked when I uploaded and it 
works now too. Did you install gitlab using the package? Could you see 
if this still a problem now?


As for 4.1 I don't see the relationship. Anyway I need to wait in order 
to get buster-bpo in order and then either 4.1 or 4.2 would come in.


Regards.

--
Marc Dequènes

Processed: Re: redmine: unmet dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #956365 [redmine] redmine: unmet dependencies
Severity set to 'normal' from 'grave'
> tag -1 + unreproducible
Bug #956365 [redmine] redmine: unmet dependencies
Added tag(s) unreproducible.

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

Bug#955694: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).

[Matthias Klose]

On 4/20/20 11:52 AM, Gilles Filippini wrote:
> I'd like to do a bisect between openjdk-11 11.0.6+10-2 and 11.0.7+9-1 to
> better understand the problem but I can't find the corresponding branch
> on the openjdk Mercurial repo.

http://hg.openjdk.java.net/jdk-updates/jdk11u/

Bug#666707: hfsprogs is not DFSG-Free

[Tobias Frost]

Discussion thread on d-legal:

https://lists.debian.org/debian-legal/2020/04/msg1.html)

Bug#666707: hfsprogs is not DFSG-Free

[John Paul Adrian Glaubitz]

Hello!

I have done some research and I do not think that the claim that this
software is not dfsg-free is correct.

First of all, the license claimed in debian/copyright is incorrect. The
upstream package that hfsprogs is based on - diskdev_cmds-332.25 [1] -
is not covered by the APSL-2.0 but versions 1.0, 1.1 and 1.2 [2, 3, 4].

Secondly, the APSL-1.2 [5] does not fail the dissident test in my opinion
as claimed in [6] as the paragraph 2.2 (c), which mandates the public 
distribution
of modifications to the software package, talks about "Deployed Modifications",
i.e. public distribution:

> (c)  You must make Source Code of all Your Deployed Modifications publicly
>  available under the terms of this License, including the license grants
>  set forth in Section 3 below, for as long as you Deploy the Covered Code
>  or twelve (12) months from the date of initial Deployment, whichever
>  is longer. You should preferably distribute the Source Code of Your
>  Deployed Modifications electronically (e.g. download from a web site); 
> and

What "Deploy" means, is explained in 1.4:

> 1.4  "Deploy" means to use, sublicense or distribute Covered Code other than
>  for Your internal research and development (R) and/or Personal Use,
>  and includes without limitation, any and all internal use or distribution
>  of Covered Code within Your business or organization except for R use
>  and/or Personal Use, as well as direct or indirect sublicensing or 
> distribution
>  of Covered Code by You to any third party in any form or manner.

Thus, the license does not fail the dissident test as explained in [7] as the
requirement for public distribution of modifications explicitly excludes 
personal
use and/or use in research and development.

I do not see how the APSL-1.2 deviates from the GPL-2 here which also requires 
the
distribution of modifications outside personal use [8]:

>  3. You may copy and distribute the Program (or a work based on it, under 
> Section
> 2) in object code or executable form under the terms of Sections 1 and 2 
> above
> provided that you also do one of the following:
> 
> a) Accompany it with the complete corresponding machine-readable source 
> code,
>which must be distributed under the terms of Sections 1 and 2 above on 
> a
>medium customarily used for software interchange; or, 
> b) Accompany it with a written offer, valid for at least three years, to 
> give
>any third party, for a charge no more than your cost of physically 
> performing
>source distribution, a complete machine-readable copy of the 
> corresponding
>source code, to be distributed under the terms of Sections 1 and 2 
> above on
>a medium customarily used for software interchange; or, 
> c) Accompany it with the information you received as to the offer to 
> distribute
>corresponding source code. (This alternative is allowed only for 
> noncommercial
>distribution and only if you received the program in object code or 
> executable
>form with such an offer, in accord with Subsection b above.) 

The GPL-2 is even stricter as it mandates three years of availability of 
modifications
in 3. b) while the APSL-1.2 requires only 12 months.

Adrian

> [1] https://opensource.apple.com/source/diskdev_cmds/diskdev_cmds-332.25/
> [2] 
> https://opensource.apple.com/source/diskdev_cmds/diskdev_cmds-332.25/newfs_hfs.tproj/newfs_hfs.c.auto.html
> [3] 
> https://opensource.apple.com/source/diskdev_cmds/diskdev_cmds-332.25/fsck_hfs.tproj/fsck_hfs.c.auto.html
> [4] 
> https://opensource.apple.com/source/diskdev_cmds/diskdev_cmds-332.25/mount_hfs.tproj/mount_hfs.c.auto.html
> [5] https://opensource.apple.com/source/hfs/hfs-522.0.9/APPLE_LICENSE
> [6] https://lists.debian.org/debian-legal/2001/09/msg00103.html
> [7] https://wiki.debian.org/DissidentTest
> [8] https://www.gnu.org/licenses/old-licenses/gpl-2.0.html

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#955656: python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib'

[Andreas Tille]

Hi Pierre,

On Mon, Apr 20, 2020 at 11:35:33AM +0200, Pierre Gruet wrote:
> I gave it a try this morning but was not able to reproduce your issue in a
> sid chroot, with the most recent version of python-cobra that is packaged in
> the Salsa repository.
> The test session can be successfully launched in my chroot. Yet, I see that
> some tests do not pass, which is maybe another libsbml-related matter. This
> does not prevent the build from being done.
> 
> Could you please either try again or give details on your configuration for
> reproducing the issue?

Thanks a lot for checking.  The issue is that we can not build the recent
upstream version as I wrote in

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10

Most probably that's *not* a problem of python-cobra but rather of
python2-sbml5 (I think Liubov in CC found this out but I simply forgot). 
If you have any spare resources could you please verify this?  Please
checkout latest Git

   https://salsa.debian.org/med-team/python-cobra

Kind regards and thanks again for your attempt to help

Andreas.

-- 
http://fam-tille.de

Processed: tagging 950839

[Debian Bug Tracking System]

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

> tags 950839 + fixed-upstream
Bug #950839 [src:reprounzip] reprounzip autopkg test fails with python 3.8
Bug #951957 [src:reprounzip] reprounzip: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.8 3.7" returned exit code 13
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#955673: marked as done (ruby-slim: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: cannot load such file -- rake/testtask)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 10:04:31 +
with message-id 
and subject line Bug#955673: fixed in ruby-slim 4.0.1-3
has caused the Debian Bug report #955673,
regarding ruby-slim: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: cannot 
load such file -- rake/testtask
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.)


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

Hi,

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

Relevant part (hopefully):
> LoadError: cannot load such file -- rake/testtask
> /<>/Rakefile:7:in `'
> debian/ruby-tests.rb:4:in `'
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/04/02/ruby-slim_4.0.1-2_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
ruby-slim, 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.
Cédric Boutillier  (supplier of updated ruby-slim 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, 20 Apr 2020 01:40:55 +0200
Source: ruby-slim
Architecture: source
Version: 4.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Closes: 955673
Changes:
 ruby-slim (4.0.1-3) unstable; urgency=medium
 .
   * Team upload
   * Remove bundler from Rakefile to load correctly rake/testtask
 in a clean building environment (Closes: #955673)
   * Bump Standards-Version to 4.5.0 (no changes needed)
   * Remove unnecessary build-depend on debhelper
   * Add japanese README file
   * Check dependencies and gemfile install scheme
Checksums-Sha1:
 6136c5bc296c488bdc054ecb4899cc0f3a109ce9 1895 ruby-slim_4.0.1-3.dsc
 efbb00512baaf3098fe0b51e24ece84aaf79745b 4940 ruby-slim_4.0.1-3.debian.tar.xz
 b64357ac564fa0e979e2bde77a4dc6558ac166f8 14101 
ruby-slim_4.0.1-3_source.buildinfo
Checksums-Sha256:
 3322e81d7bda60fd0a9214d5f7dc7a1fe1895e5b9422a8bd051c63088b871d11 1895 
ruby-slim_4.0.1-3.dsc
 7626aab0887bf4a6182e9aecb7c6b58abdeca58124d4e4bf0fd29f1aa5ec8d40 4940 
ruby-slim_4.0.1-3.debian.tar.xz
 e0fe83ce3951544e9686bfe3d1354400dad5118ee6a9a7fe41e77ea8943a2a5a 14101 
ruby-slim_4.0.1-3_source.buildinfo
Files:
 f28aaca0b17d6b5e3f30be5cd607d87a 1895 ruby optional ruby-slim_4.0.1-3.dsc
 2f2c4b83aa85604b82237bc6df794131 4940 ruby optional 
ruby-slim_4.0.1-3.debian.tar.xz
 3d22cfe5187c8d50ad2078f3067d0245 14101 ruby optional 
ruby-slim_4.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAl6dbsYACgkQia+CtznN
IXq5Qgf/Wk0Y49+rxllyZGRv26NaTnKCYXcvUfazcfsREu24ICBPDhrZzAfAjdT+
og+phsHBnPyJE8zaMwC6vtf1UcwG0siT41pu7w2NxVVjyA5mveP2dOMsiU8EX9hG
b5rRIgxy1X7L2wxe6e663fkwuhxh0Y08auMCcJ7A9Bv4kknJzezi8o5bcRLXz3k4
BbEzE8dZxQGYqRJIZt0v7Y1e/9fVOD9WQKqpi9AluErzUFOU0Blsutqi/FYTSvNP
vFMPy+Vxg6vLA861+sp+mEKBvAct5PiyjLNHJWNxwLjtqbCopoX/25+R+z4cLsYv
22fNWi2UiATwXa4q6yImmPPdHrKQ5Q==
=zjZM
-END PGP SIGNATURE End Message ---

Processed (with 1 error): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 912485 src:childsplay
Bug #912485 [childsplay] childsplay: Please migrate to python3-pygame
Bug reassigned from package 'childsplay' to 'src:childsplay'.
Ignoring request to alter found versions of bug #912485 to the same values 
previously set
Ignoring request to alter fixed versions of bug #912485 to the same values 
previously set
> forcemerge 936298 912485
Bug #936298 [src:childsplay] childsplay: Python2 removal in sid/bullseye
Bug #912485 [src:childsplay] childsplay: Please migrate to python3-pygame
Set Bug forwarded-to-address to 'https://savannah.nongnu.org/bugs/?53770'.
Severity set to 'serious' from 'wishlist'
937441 was blocked by: 943075 937492 945731 937726 938488 943027 938509 938328 
936550 936978 936298 912491 938592 912495 936945 945699 936559 936513 945671 
937621 936577 937330 937431 945632 937553 912487 938497 936148 937743
937441 was blocking: 937695 937960 938168 938528
Added blocking bug(s) of 937441: 912485
937960 was blocked by: 937544 937731 938509 937186 937209 936999 938445 937024 
937007 937295 937091 942925 938006 936161 937088 936797 938753 938384 938500 
937041 937116 936660 945671 937414 938488 937003 936983 937167 938471 936319 
937657 936159 937945 937291 937718 937256 937606 938613 937026 936298 937040 
936952 937022 937005 936275 937551 938462 937037 943171 938510 938751 937099 
937266 943188 937262 938859 938796 936628 937019 936285 937743 942992 937852 
936995 937030 936311 937144 942972 937427 937389 936870 937039 937330 943029 
937455 937616 936207 942939 937490 937554 937654 937145 938301 937426 936816 
937023 938458 936261 935450 937727 937640 938412 937236 937605 937255 938310 
936652 938663 937258 936190 942973 938262 937480 937004 937796 936274 936328 
937547 937751 938289 934852 936531 938572 937032 937433 943017 938008 937036 
937055 938379 936154 937267 937489 936578 937497 938157 943005 937585 937021 
936704 936996 936825 937541 938661 936857 936227 937441 938009 937452 937491 
937485 936769 937827 937944 938738 942991 938444 937028 942988 937250 937143 
938295 936932 936276 937006 937675 942952 943169 934870 936894 938568 937961 
937823 937253 938674 937140 936363 937061 937034 937498 936767 937431
937960 was blocking: 937558 937569 937695 937715 938168 938234 942939 943169
Added blocking bug(s) of 937960: 912485
937695 was blocked by: 937054 937845 938052 937423 936772 937592 937835 938594 
883150 937547 938864 937675 936911 945738 937145 936316 937260 937135 945748 
942963 938653 938737 937794 938164 937162 938792 936661 936904 937229 945702 
937826 938718 936700 947302 945717 943223 937126 938541 936123 936319 936770 
938050 937937 936511 937860 936748 936738 936974 936445 937262 937160 938790 
937245 938027 936462 937084 936717 938346 937129 938336 937021 938683 936702 
937605 945661 936426 938425 938843 937816 936752 936362 938072 942944 937074 
943018 942934 945727 936693 947294 943213 936335 937116 936345 938436 937413 
936984 947231 939487 942991 936921 943047 936326 943037 936954 936727 937119 
948847 937323 937011 943113 938243 938233 938070 937819 936416 936113 936329 
937696 937004 938315 938002 936521 936584 938439 936813 943090 942935 938793 
943266 942945 937654 936628 936820 942962 936344 936857 936222 938909 937377 
937593 943287 936120 943061 937422 938053 937487 943222 947303 938579 942926 
93 938680 943120 936996 936169 936391 936985 937779 936599 936266 943157 
938188 936869 937068 936463 937709 937457 937263 938650 938858 942960 956334 
943166 937993 936955 937420 938301 937398 938509 936187 937776 936596 936269 
937621 943122 937684 938682 936866 937307 938314 937005 936887 937312 938451 
942929 936585 938083 936999 943257 936166 936968 937144 938278 936877 936753 
936637 936363 938073 938586 938230 937498 937834 938567 938595 937055 937844 
937320 936177 938672 936298 938865 939260 943207 945690 937759 938808 943298 
938600 936810 936207 937891 936212 938108 938559 936110 937099 937412 937191 
938351 883173 943210 936898 936434 936690 938130 936444 937611 936975 938232 
937234 943112 938178 937244 938840 938648 938638 938830 945647 938381 945692 
938589 938670 938471 936107 943198 936783 938556 937961 943277 936812 937387 
937085 938617 937291 936505 937410 938003 942930 937243 936527 943136 937233 
942940 938216 937070 937048 936443 936825 942978 936433 937038 938819 936609 
936952 936125 936550 938011 937439 937449 938685 943125 936249 936721 938696 
938004 936146 937072 937728 942942 936927 937143 938116 938655 939481 943031 
936225 937673 943041 936950 938219 937425 937843 938528 938816 936606 943225 
938699 936149 937000 945721 936839 937446 945676 936982 936580 936246 956333 
936548 936972 936538 938262 937264 938160 943115 937027 936689 936464 938235 
936570 938947 938590 937050 942958 938860 938668 945695 945667 937931 937941 
938226 936704 938605 936815 938829 936900 938084 937082 937336 938129 938313 
936667 938260 936695 936343 937737 936572 938794 937164 

Processed (with 1 error): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 933928 src:macsyfinder
Bug #933928 [macsyfinder] macsyfinder: Port to Python3 needed
Bug reassigned from package 'macsyfinder' to 'src:macsyfinder'.
Ignoring request to alter found versions of bug #933928 to the same values 
previously set
Ignoring request to alter fixed versions of bug #933928 to the same values 
previously set
> forcemerge 936977 933928
Bug #936977 [src:macsyfinder] macsyfinder: Python2 removal in sid/bullseye
Bug #933928 [src:macsyfinder] macsyfinder: Port to Python3 needed
Severity set to 'serious' from 'normal'
Failed to forcibly merge 936977: 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.

> thanks
Stopping processing here.

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

Bug#956287: marked as done (Problems identified in debian/copyright)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 10:00:21 +
with message-id 
and subject line Bug#956287: fixed in llvm-toolchain-snapshot 
1:11~++20200411120955+c65e6079fc9-1~exp1
has caused the Debian Bug report #956287,
regarding Problems identified in debian/copyright
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.)


-- 
956287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-toolchain-snapshot
Version: 11~++20200307074845+ec1d1f6ae70-1~exp1
Severity: serious

I noticed that this package appears to have some issues with debian/copyright.

Binary data exists with no indication that it can be rebuilt from source:
- lldb/unittests/ObjectFile/ELF/Inputs/early-section-headers.so
- lldb/unittests/Target/Inputs/TestModule.so
- soo many *.so files
- also many *.exe files
- Note: Test data is *not* excluded from DFSG.

These have a copyright/license that is not represented in d/copyright:
- lib/External/{many}
- llvm/utils/unittest/googletest/*
- llvm/utils/unittest/googlemock/*
- llvm/test/YAMLParser/*
- clang/lib/Headers/cuda_wrappers/*
- llvm/include/llvm/Support/MD5.h
  + Note: pseudonyms don't need to be represented; "2001 Alexander Peslyak
"
- clang/lib/Headers/:
  + avx512vlvp2intersectintrin.h
  + avx512vp2intersectintrin.h
- Note: This is not an exhaustive list.

libcxx/* indicates the wrong license *and* omits a copyright holder. (just
delete that paragraph) The same applies to polly/tools/GPURuntime/; it is
correctly represented when the paragraph is deleted).

clang/lib/Headers/* is represented as using Expat; this is not correct.

Multiple copyright blocks are mentioned for source that does not exist:
- lib/Support/reg*
- lldb/test/unittest2/*
- polly/lib/JSON/*
- test/YAMLParser/*
- utils/unittest/googletest/*

Note: If `polly/lib/JSON/` existed, "fixme" would have been unacceptable. It
should have copied LICENSE.txt.


Although not critical, the machine-readable copyright spec expects license
texts to either be with that paragraph or as an entirely unique paragraph. In
this case, it applies to BSD-3-Clause, expat, and u-of-i-bsd-like. Please see
missing-license-paragraph-in-dep5-copyright for additional information.

Also, it is not required to use four separate paragraphs;
"compiler-rt/lib/BlocksRuntime/*" is sufficient.

It is also possible to combine files:

Files:
  compiler-rt/lib/BlocksRuntime/*
  lldb/tools/debugserver/source/MacOSX/stack_logging.h
Copyright: 1999-2007 Apple Inc.
License: Apple


If you need further clarification, please don't hesitate to ask.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-snapshot
Source-Version: 1:11~++20200411120955+c65e6079fc9-1~exp1
Done: Sylvestre Ledru 

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated 
llvm-toolchain-snapshot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Apr 2020 12:27:18 +0200
Source: llvm-toolchain-snapshot
Binary: clang-11 clang-11-dbgsym clang-11-doc clang-11-examples clang-format-11 
clang-format-11-dbgsym clang-tidy-11 clang-tidy-11-dbgsym clang-tools-11 
clang-tools-11-dbgsym clangd-11 clangd-11-dbgsym libc++-11-dev libc++1-11 
libc++1-11-dbgsym libc++abi-11-dev libc++abi1-11 libc++abi1-11-dbgsym 
libclang-11-dev libclang-common-11-dev libclang-common-11-dev-dbgsym 
libclang-cpp11 libclang-cpp11-dbgsym libclang-cpp11-dev libclang1-11 
libclang1-11-dbgsym libfuzzer-11-dev liblld-11 liblld-11-dev liblldb-11 
liblldb-11-dbgsym liblldb-11-dev libllvm-11-ocaml-dev libllvm11 
libllvm11-dbgsym libomp-11-dev libomp-11-dev-dbgsym libomp-11-doc libomp5-11 
libomp5-11-dbgsym lld-11 lld-11-dbgsym lldb-11 lldb-11-dbgsym llvm-11 
llvm-11-dbgsym llvm-11-dev llvm-11-dev-dbgsym llvm-11-doc llvm-11-examples 
llvm-11-runtime llvm-11-runtime-dbgsym llvm-11-tools llvm-11-tools-dbgsym 
python3-clang-11 python3-lldb-11
Architecture: source amd64 all
Version: 

Processed (with 1 error): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 912491 src:pysiogame
Bug #912491 [pysiogame] pysiogame: Please migrate to python3-pygame
Bug reassigned from package 'pysiogame' to 'src:pysiogame'.
Ignoring request to alter found versions of bug #912491 to the same values 
previously set
Ignoring request to alter fixed versions of bug #912491 to the same values 
previously set
> forcemerge 945699 912491
Bug #945699 [src:pysiogame] pysiogame: Python2 removal in sid/bullseye
Bug #912491 [src:pysiogame] pysiogame: Please migrate to python3-pygame
Severity set to 'serious' from 'wishlist'
937441 was blocked by: 936298 938488 936559 936550 936945 938509 945731 945632 
937492 937743 937621 936978 945671 936513 937726 937431 937330 912487 938497 
943075 938592 937553 912495 936577 938328 945699 943027 936148
937441 was blocking: 937695 937960 938168 938528
Added blocking bug(s) of 937441: 912491
937695 was blocked by: 938862 938442 942979 936830 943036 938521 937240 937945 
937320 937262 936580 937725 936501 937050 938840 938460 937397 936340 936745 
938704 936944 937402 948846 936724 936297 937187 937800 938330 937318 943007 
936362 943115 938735 937296 938503 937888 936274 936690 945688 943192 936627 
936770 936950 937269 938004 938510 937538 939259 936523 937383 942972 937970 
937750 937355 936508 937275 937025 943166 936211 937254 936283 937193 938875 
937647 938528 938116 937044 938854 938674 938290 937336 936337 938655 938794 
938227 937492 937579 938347 945690 936688 937890 938484 936207 937827 945627 
936564 938587 938473 945646 937237 938056 912487 937458 936467 936847 938068 
938611 938326 938837 937089 938683 938131 937565 936591 937307 942931 943018 
936982 936559 942938 937572 938618 937499 937103 937451 938061 943083 936148 
938756 945724 938593 943102 937082 936681 937516 883173 937415 938094 938697 
945745 942112 942943 938777 942981 936932 938181 947231 938364 937039 943163 
938887 938100 937196 936643 936120 945665 936859 945715 936891 937445 936702 
947301 937287 937140 938029 943041 936425 938359 936638 938391 938279 936864 
936444 943299 937527 938648 937902 937386 936118 936526 937162 937816 936111 
936709 943266 938641 943258 937175 936817 936852 936631 938216 937032 936450 
943048 938729 936939 937293 936183 936155 937169 943033 945672 936898 943292 
937680 938272 937470 938188 938022 942988 937831 938596 938785 938380 937137 
937513 936241 938301 936321 937581 938231 937500 935208 936978 936758 937617 
938127 936482 942990 936530 938562 936672 937778 938540 937071 883157 938753 
936792 938419 937221 936880 936107 938053 937843 937463 945643 938476 936310 
936665 937691 943124 937078 945702 936914 937771 938686 938554 938243 936303 
938828 943145 946929 937333 937714 936751 937664 936799 938457 938412 936328 
938803 937210 937588 938308 936489 937203 937838 938810 938353 937266 936392 
938273 937437 936885 937378 936267 938545 937258 943032 942995 945673 938866 
938195 936535 937048 938858 937884 937033 937505 938490 938639 936358 945684 
936366 936721 938427 938008 937534 938701 936941 938892 936853 936649 938385 
938780 937406 937903 938708 938176 942976 938001 943039 937910 943196 936728 
937622 937314 943287 937733 936271 937041 943140 937748 938157 942957 942912 
936214 937251 936189 936933 936710 938632 936660 945728 938400 936561 937202 
937124 936787 938759 938098 937145 936420 937496 938671 942934 943067 937519 
945710 936125 943210 937860 937440 938614 945642 938764 938052 936418 937462 
937842 943203 938260 938322 937475 938809 936673 937454 937339 938752 936793 
936483 936577 937209 936150 936829 937576 943014 937993 938329 936474 937849 
938059 936455 936556 938488 937170 938249 937086 939491 937557 945721 936309 
936282 937560 936894 936706 937819 936936 947730 938361 938184 937421 938219 
937937 943275 936167 945695 936522 937166 942973 943254 937895 938650 936737 
943193 938394 938502 938431 943044 938295 938625 938212 937549 937036 938377 
938438 937410 945740 936634 936363 943240 936868 936448 938047 945657 943262 
938644 936114 937151 937403 936856 943050 936605 936289 937428 938276 937263 
937635 938509 936433 938443 938863 945676 937389 936529 937007 936877 937115 
936612 936657 938730 956333 937718 936225 936762 937011 937996 936920 936997 
942942 938479 938234 942960 936132 938592 938160 936740 936345 938689 937083 
937834 938845 938465 947502 937102 937055 937224 936585 937720 936796 936804 
937074 937962 936918 937677 937245 938558 937940 937487 938682 939104 936983 
937020 936911 943121 938472 937694 937270 936769 936619 945706 943466 937783 
943237 938515 937969 936775 936955 938416 936370 936974 937711 936695 945639 
938087 938684 938556 938309 938568 939102 936249 936329 943201 937952 936678 
939487 945701 938239 938455 946928 936916 937065 937692 943126 936798 943280 
938483 849087 942950 938829 938150 936809 937079 937998 937666 936667 938793 
937658 936717 936972 936752 937229 938411 936105 938418 936614 938232 937779 
936322 937959 937016 

Bug#950384: marked as done (apertium-id-ms FTBFS with apertium 3.6.1)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 10:00:10 +
with message-id 
and subject line Bug#950384: fixed in apertium-ind-zlm 0.1.2-1
has caused the Debian Bug report #950384,
regarding apertium-id-ms FTBFS with apertium 3.6.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.)


-- 
950384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-id-ms
Version: 0.1.1~r57551-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-id-ms.html

...
make -j16
make[1]: Entering directory '/build/1st/apertium-id-ms-0.1.1~r57551'
make  all-am
make[2]: Entering directory '/build/1st/apertium-id-ms-0.1.1~r57551'
apertium-validate-dictionary apertium-id-ms.id-ms.dix
apertium-validate-dictionary apertium-id-ms.id-ms.dix
apertium-validate-dictionary apertium-id-ms.ms.dix
apertium-validate-dictionary apertium-id-ms.id.dix
apertium-validate-dictionary apertium-id-ms.id.dix
apertium-validate-dictionary apertium-id-ms.ms.dix
apertium-validate-transfer apertium-id-ms.id-ms.t1x
apertium-validate-transfer apertium-id-ms.ms-id.t1x
apertium-validate-modes modes.xml
apertium-validate-modes modes.xml
apertium-preprocess-transfer apertium-id-ms.id-ms.t1x id-ms.t1x.bin
apertium-gen-modes modes.xml
apertium-preprocess-transfer apertium-id-ms.ms-id.t1x ms-id.t1x.bin
apertium-gen-modes modes.xml
apertium-id-ms.ms.dix:2380: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['mempersalinnya__vblex'] in unique 
identity-constraint 'pardef-unique'.
cp *.mode modes/
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:787: modes/ms-id.mode] Error 1
--- End Message ---
--- Begin Message ---
Source: apertium-ind-zlm
Source-Version: 0.1.2-1
Done: Kartik Mistry 

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

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

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-ind-zlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Mar 2020 20:23:28 +0530
Source: apertium-ind-zlm
Binary: apertium-id-ms apertium-ind-zlm
Architecture: source all
Version: 0.1.2-1
Distribution: experimental
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 apertium-id-ms - Transitional dummy package for apertium-ind-zlm
 apertium-ind-zlm - Apertium translation data for the Indonesian-Malay pair
Closes: 950384
Changes:
 apertium-ind-zlm (0.1.2-1) experimental; urgency=low
 .
   [ Tino Didriksen ]
   * New upstream release:
 + Renamed from apertium-id-ms to apertium-ind-zlm
 + Fix FTBFS with apertium 3.6 (Closes: #950384)
   * Bundles apertium-ind 0.2.0 and apertium-zlm 0.2.0
 .
   [ Kartik Mistry ]
   * debian/control:
 + Switch to debhelper-compat.
 + Updated Standards-Version to 4.5.0
 + Added 'Rules-Requires-Root' field.
   * Added debian/upstream/metadata file.
Checksums-Sha1:
 1e022dccb42ea058824e12bcfbf05b7f514131e2 2148 apertium-ind-zlm_0.1.2-1.dsc
 5ab74281081725a16da2e22e1cabbb882aee8d3b 365573 
apertium-ind-zlm_0.1.2.orig.tar.bz2
 32628d3d92caac45b8137a51d1c0de6397e310f9 2652 
apertium-ind-zlm_0.1.2-1.debian.tar.xz
 08ff4fc8e7b8fcf7e908ee9da76f1dfbc1ac9933 2432 apertium-id-ms_0.1.2-1_all.deb
 258cb341d84de2954c13e91c8119e1a8470d007d 451608 
apertium-ind-zlm_0.1.2-1_all.deb
 5d3557e374762909fe7ecf5fa73e5f39da34f969 6985 
apertium-ind-zlm_0.1.2-1_amd64.buildinfo
Checksums-Sha256:
 1bc3e2da22921a32afe96272c4b3b719d5b18a1e6e306409a2b2468d1d1b3697 2148 
apertium-ind-zlm_0.1.2-1.dsc
 4636d420503d7b46b3750fa4c2823f93cbeefb7f476fae49e1de29bd357c7e4c 365573 
apertium-ind-zlm_0.1.2.orig.tar.bz2
 3b0a2162bb5279243f9e393c3051e021400f14920259679b44f00147548ab3a1 2652 
apertium-ind-zlm_0.1.2-1.debian.tar.xz
 d926d662c8a2bec9df74c3b02f735673c7e8fd7e23a608a86d54aefa72bee9bf 2432 
apertium-id-ms_0.1.2-1_all.deb
 

Processed: tagging 936798

[Debian Bug Tracking System]

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

> tags 936798 + fixed-upstream
Bug #936798 [src:kissplice] kissplice: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#955694: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).

[Gilles Filippini]

Control: tags -1 + help

Lucas Nussbaum a écrit le 03/04/2020 à 21:55 :
> Source: scilab
> Version: 6.1.0+dfsg1-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200402 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
[...]
>> -- Building documentation (en_US) --
>> LANG=en_US.UTF-8 LC_ALL=C SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1 
>> _JAVA_OPTIONS='-Djava.awt.headless=true' HOME=/tmp ./bin/scilab-adv-cli 
>> -noatomsautoload -nb -l en_US -nouserstartup -e "try 
>> xmltojar([],[],'en_US');catch disp(lasterror()); exit(-1);end;exit(0);"
>> Picked up _JAVA_OPTIONS: 
>> -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/java/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep-graphicsio-emf-2.1.jar:/usr/share/java/freehep-graphics2d-2.1.1.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine-1.0.4.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop-1.0.7.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath-1.0.7.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-runtime.jar:modules/commons/jar/org.scilab.modules.commons.jar:modules/console/jar/org.scilab.modules.console.jar:modules/history_browser/jar/org.scilab.modules.history_browser.jar:modules/jvm/jar/org.scilab.modules.jvm.jar:modules/graph/jar/org.scilab.modules.graph.jar:modules/scinotes/jar/org.scilab.modules.scinotes.jar:modules/localization/jar/org.scilab.modules.localization.jar:modules/renderer/jar/org.scilab.modules.renderer.jar:modules/javasci/jar/org.scilab.modules.javasci.jar:modules/ui_data/jar/org.scilab.modules.ui_data.jar:modules/core/jar/org.scilab.modules.core.jar:modules/completion/jar/org.scilab.modules.completion.jar:modules/gui/jar/org.scilab.modules.gui.jar:modules/helptools/jar/org.scilab.modules.helptools.jar:modules/external_objects_java/tests/libintl.jar:modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:modules/scirenderer/jar/scirenderer.jar:modules/types/jar/org.scilab.modules.types.jar:modules/preferences/jar/org.scilab.modules.preferences.jar:modules/action_binding/jar/org.scilab.modules.action_binding.jar:modules/history_manager/jar/org.scilab.modules.history_manager.jar:modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:modules/xcos/jar/org.scilab.modules.xcos.jar:modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:
>>  -Djava.awt.headless=true
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath 
>> (file:/<>/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar) to 
>> field java.lang.ClassLoader.sys_paths
>> WARNING: Please consider reporting this to the maintainers of 
>> org.scilab.modules.jvm.LibraryPath
>> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> Could not access to the Main Scilab Class:
>> Exception in thread "main" java.lang.ExceptionInInitializerError
>>  at org.scilab.modules.localization.Messages.gettext(Unknown Source)
>>  at org.scilab.modules.commons.xml.XConfiguration.(Unknown 
>> Source)
>>  at org.scilab.modules.core.Scilab.(Unknown Source)
>> Caused by: java.lang.NullPointerException
>>  at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2646)
>>  at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:830)
>>  at java.base/java.lang.System.loadLibrary(System.java:1870)
>>  at org.scilab.modules.localization.MessagesJNI.(Unknown Source)
>>  ... 3 more
>>
>> Scilab cannot create Scilab Java Main-Class (we have not been able to find 
>> the main Scilab class. Check if the Scilab and thirdparty packages are 
>> available).
>> make[2]: *** [Makefile:2250: doc] Error 1
> 
> The full build log is available from:
>http://qa-logs.debian.net/2020/04/02/scilab_6.1.0+dfsg1-1_unstable.log

This is a runtime error, not a build one. It occurs the very same way
when running the current scilab binary (6.1.0+dfsg1-1) with openjdk-11
11.0.7+9-1.

A change 

Processed: Re: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + help
Bug #955694 [src:scilab] scilab: FTBFS: Scilab cannot create Scilab Java 
Main-Class (we have not been able to find the main Scilab class. Check if the 
Scilab and thirdparty packages are available).
Added tag(s) help.

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

Bug#955656: python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib'

[Pierre Gruet]

Hi Andreas,

I gave it a try this morning but was not able to reproduce your issue in a
sid chroot, with the most recent version of python-cobra that is packaged in
the Salsa repository.
The test session can be successfully launched in my chroot. Yet, I see that
some tests do not pass, which is maybe another libsbml-related matter. This
does not prevent the build from being done.

Could you please either try again or give details on your configuration for
reproducing the issue?

All the best,
Pierre

Bug#958075: crispy-doom: file conflict with chocolate-doom

[Fabian Greffrath]

Hi Sven,

Am 18.04.2020 07:50, schrieb Sven Joachim:

Since chocolate-doom was there first to ship the offending file, I
assume it should be removed from crispy-doom.


I'll take care of that with the next upload, thank you!

 - Fabian

Bug#956286: marked as done (Problems identified in debian/copyright)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 08:33:45 +
with message-id 
and subject line Bug#956286: fixed in folks 0.14.0-1
has caused the Debian Bug report #956286,
regarding Problems identified in debian/copyright
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.)


-- 
956286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: folks
Version: 0.13.2-2~exp1
Severity: serious

I noticed that this package appears to have some issues with debian/copyright.

Missing copyright holders:
- Philip Withnall
- Intel Corporation
- Canonical Ltd.
- Renato Araujo Oliveira Filho
- Red Hat, Inc.
- Will Thompson
- Zeeshan Ali (Khattak)
- There may be more.

If you need further clarification, please don't hesitate to ask.
--- End Message ---
--- Begin Message ---
Source: folks
Source-Version: 0.14.0-1
Done: Laurent Bigonville 

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

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

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated folks package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Apr 2020 09:35:30 +0200
Source: folks
Architecture: source
Version: 0.14.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Closes: 679740 956286
Changes:
 folks (0.14.0-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/copyright: Adjust the Copyright holders (Closes: #956286)
 .
 folks (0.13.2-2) unstable; urgency=medium
 .
   * debian/control.in: Mark the -dev packages as multi-arch same
   * Build the documentation and create new -doc packages (Closes: #679740)
Checksums-Sha1:
 21e4a76dd2e35940336ffc6e0a9d1e9a806cef30 3119 folks_0.14.0-1.dsc
 6f95ab20d6e6a8be6cdd58e4281aade243cefd92 520924 folks_0.14.0.orig.tar.xz
 088d69313ede177e6c706b3ec958bacc31d64c2f 11804 folks_0.14.0-1.debian.tar.xz
 6c23d4de3ed94379bb10bd4cc06296b945b5f0f3 6940 folks_0.14.0-1_source.buildinfo
Checksums-Sha256:
 e9e573bb9ec720b241965520ae356087302f7d9e310e7cd24a72e023c3026f9f 3119 
folks_0.14.0-1.dsc
 d6e778da637d3b33fd9a6b45115e8157d8868211dc08b943d1075b5eb7282bb9 520924 
folks_0.14.0.orig.tar.xz
 92a734dbb629229fb356fc2115dc7e6469fdde7869d0fbe42048c168613445e0 11804 
folks_0.14.0-1.debian.tar.xz
 914111b72c71e7bcd371036127ac1f8d54cae71591344d05dbe50d310626faf0 6940 
folks_0.14.0-1_source.buildinfo
Files:
 9dd6585f91d079de8fb6df356cd384eb 3119 libs optional folks_0.14.0-1.dsc
 dc852fceab9e84362b675d5ffcd4803e 520924 libs optional folks_0.14.0.orig.tar.xz
 a8526fc5c1aa0d2036f16717d0b05fa7 11804 libs optional 
folks_0.14.0-1.debian.tar.xz
 9119fdcbc087570fe490509def0d6039 6940 libs optional 
folks_0.14.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl6dUZcRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9VVuwf8Cjd4WXT6/+YJUe6PDcj/LaflVM3HuCKM
/ziD63HzNC7NZmfSVOlvMAs8R/i2BC1bZqylRp5mn86lavh3srvq39KqZayKWGgx
Suy+nZR+C61Tjj0ftRlcJUcQZxc4jkp4L+D9nIPw6yPJWiZhdXYSZuK3wFgqWkSO
Mj89ClKTlHUTu9mKdKAudLP/00FHKFUSAjj3Tye0/azzALbidXWIK0LHEXjUIBCN
PCdgx/BUrUGkmKuXuJ+dYWH63aBeeE1dVdlVMROCzOoQZK0jyxxkc82ZMcuRMCJA
EbS8WqA/kgrk1wZO6EwTgII3ZpyrWkJ1vtyk1nBa8E5NTSV19s+Qxg==
=Yb+N
-END PGP SIGNATURE End Message ---

Bug#952127: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

[Thomas Goirand]

On 4/20/20 4:36 AM, peter green wrote:
> (using -quiet aliases where multiple involved packages have the same
> maintainer listed.
> 
> Hi
> 
> I have just been running some self-contained buildability tests on
> bullseye and these tests indicated that the python-linecache2 and
> python-traceback2 source packages have been unbuildable in testing for
> 170+ days. Both are fixed in unstable by removing python 2 support, but
> can't migrate to testing because the python-unittest2 binary package
> depends on the python-traceback2 binary package. The python2 removal bug
> for python-traceback2 lists python-funcsigs as a blocker. The python2
> removal bug for python-traceback2 lists nipype and numba as blockers.
> 
> unittest2 and python-funcsigs seem to be just module packages, so
> dropping python2 support should be simple. numba seems to be a case of
> leftover recommends and test-triggers so that should be a pretty easy
> job to clean up too.
> 
> nipype on the other hand looks like it needs a new upstream release. It
> seems this was previously blocked on a package passing new, but said
> package has now passed new.
> 
> python-funcsigs seems to have a build-dependency on python-traceback2
> but not a binary dependency, this suggests that the dependency is only
> used to run tests at build time.
> 
> nipype and numba are not currently in testing.
> 
> This IMO leaves three potential ways forward
> 
> Option 1: fix all four packages to be python 2 free.
> 
> Option 2: Remove python2 stuff from traceback2, python-funcsigs and
> numba. Break the dependencies of nipype in sid.
> 
> Option 3: Remove python2 stuff from traceback2, modify python-funcsigs
> so it still builds the python2 package but does not run tests with
> python 2.

Funcsigs is a backport of the PEP 362 function signature features from
Python 3.3's inspect module. Python 2 has never been removed from this
package. Though instead, we shall remove this source package entirely
from Debian.

Traceback2 *already* has Python 2 support removed in Sid. I uploaded
this on the 21st of march, pressured by its potential autoremoval.

> If the maintainers of nipype are willing to upload a python 3 version
> soon, then option 1 is IMO the preffered way forward, but a new upstream
> version is not something I would be prepared to NMU.

There's no other choice but to fix nipype at this point, or wait until
it gets autoremoved from Testing. IMO, it'd be fine to NMU a new
upstream release if you contact the current maintainer and/or using the
delayed queue.

> Otherwise I am inclined towards option 2. Depending on what responses I
> get to this mail I may implement this option through NMUs later.

IMO, we should get unittest2 free of Py2 support ASAP, and open an FTP
team bug to get funcsigs removed from Debian.

Cheers,

Thomas Goirand (zigo)

Bug#958222: marked as done (edflib: autopkgtest failure: gcc: Command not found)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 07:33:26 +
with message-id 
and subject line Bug#958222: fixed in edflib 1.16-3
has caused the Debian Bug report #958222,
regarding edflib: autopkgtest failure: gcc: Command not found
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.)


-- 
958222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: edflib
Version: 1.16-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: always-fails

Dear maintainer(s),

With a recent upload of edflib you added an autopkgtest, great. However,
it fails. I suspect you are just missing test dependencies. I copied
some of the output at the bottom of this report.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/e/edflib/4738699/log.gz

autopkgtest [15:14:29]: test run-unit-test: [---
gcc -Wall -Wextra -Wshadow -Wformat-nonliteral -Wformat-security
-Wtype-limits -g -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -c unittest.c
-o unittest.o
make: gcc: Command not found
make: *** [Makefile:20: unittest.o] Error 127
autopkgtest [15:14:29]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: edflib
Source-Version: 1.16-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated edflib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Apr 2020 09:12:13 +0200
Source: edflib
Architecture: source
Version: 1.16-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 958222
Changes:
 edflib (1.16-3) unstable; urgency=medium
 .
   * Test-Depends: build-essential
 Closes: #958222
Checksums-Sha1:
 8b45e16d30b1c1acba2ecf6e755d22694df2afb8 2023 edflib_1.16-3.dsc
 a98dc26630a1b482aebdc64591701c7a70136267 20056 edflib_1.16-3.debian.tar.xz
 c205b5bd94fe037695b39643db1713740fb93a2e 6908 edflib_1.16-3_amd64.buildinfo
Checksums-Sha256:
 3d5ca62131e4eeca5e09d7e4065c5495af8e41f39d0085425943f77351f8f650 2023 
edflib_1.16-3.dsc
 9841143c43a9e18603f16ac9f07b8e317c732a981a0482450dc225b8e57dd3a0 20056 
edflib_1.16-3.debian.tar.xz
 b0b77e57d5959964fa5250cf84bdd20bca469d39932fff5f8ca25de466197e78 6908 
edflib_1.16-3_amd64.buildinfo
Files:
 f97b2a649310cabec79cf25cab5aef79 2023 libs optional edflib_1.16-3.dsc
 a3e844c641168c84c6a0a9a459ce102f 20056 libs optional 
edflib_1.16-3.debian.tar.xz
 9348a2bdf87be584b789cea18734a6bd 6908 libs optional 
edflib_1.16-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6dS+0RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE2rA/7BKixbc5Myyjo0AzBlpag43Mh2l6L7JEV
fYL+hbFldxhTKZMYEyCrxRAMFj4guCcCD2ThVrULFkrr8+tJCd5jxitTaGmlbI25
uiZWO+zpsQWnxaZEyu+/OfX4kbK3EMAZHH0AQayoBtT8N0e7JJI+y3M2jbbzhASb
dO6Lw44Q5So8c3faDKTfJXiZbVG2zc+3CQppLzKM9BOzgCdyI35ABXkfRfaoWYfR
EYQgkj60h1Gk77ZmmGjVo9+nVCj4QWK2wI95MJIfUcf2s5w52JkI6id7bjOgiATS
+67GcrquhXbN5SqCxKstQAGWr83k97tDt2lgDMT9rD7HtolX6OPgroGLhzlcXt/1
UhtZm5gFQSPejxfJAEPSqRiIq570MbZwKssi9HOvCq+LPNhcNGz4o6GE6pRBQmOD
NNzzOVcuvcctnBPnvjUoSxWmzjx8n7jkkvZunrOcX+vzQI2WCBtWaeoO8bRS7Mrk
2wwbII7+nzVETJbMiJwe+ndRwwxdD4iFlz+FWJ3WYsoIQ0rGy8YjpyM6JQH0GmZj
YM2kQHGO/zHX27W0TrkUK/XDC0lXkX0/WhEtijsHv2KN89gnIMq4uOdP1YL61YKk
KHCrobWhoKqx8zDf30B8RUHRygU8y1vnO23M7DiBdVBjNf/ncpCtVxtI6TnleZq6
Qepn2wk1L1Y=
=C43J
-END PGP SIGNATURE End Message ---

Bug#955070: possible fix with new upstream location and 0.8.1-rc3 release

[Jordan Justen]

I opened a merge request in salsa to potentially help fix this bug:

https://salsa.debian.org/openstack-team/libs/python-doc8/-/merge_requests/1

It seems like the python-oslosphinx package is causing the FTBFS,
since it's not compatible with Sphinx 2.4.

I found a new upstream location for doc8, but they only had an rc3 for
a new release. The rc3 release did not depend on oslosphinx, and
therefore, the package was able to build.

Looking at `apt showpkg python3-doc8`, I wasn't able to find a
specific package to test against the new python3-doc8 build.

If this looks like the right direction to fix the FTBFS, I can upload
a build to debian.mentors.net if that would be helpful.


signature.asc
Description: signature

Processed: severity of 956697 is normal

[Debian Bug Tracking System]

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

> severity 956697 normal
Bug #956697 [src:mercurial] mercurial: flaky autopkgtests
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#951978: vala-panel: FTBFS: ./obj-x86_64-linux-gnu/../util/misc.c:100: multiple definition of `vala_panel_reset_schema_with_children'; util/gtk/libutil-gtk.a(misc.c.o):./obj-x86_64-linux-gnu/../uti

[Mike Gabriel]

Control: forwarded -1  
https://gitlab.com/vala-panel-project/vala-panel/-/issues/115


On  So 23 Feb 2020 08:29:39 CET, Lucas Nussbaum wrote:


Source: vala-panel
Version: 0.4.91+dfsg1-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):
/usr/bin/ld: util/libutil.a(misc.c.o): in function  
`vala_panel_reset_schema_with_children':
./obj-x86_64-linux-gnu/../util/misc.c:100: multiple definition of  
`vala_panel_reset_schema_with_children';  
util/gtk/libutil-gtk.a(misc.c.o):./obj-x86_64-linux-gnu/../util/misc.c:100:  
first defined here

collect2: error: ld returned 1 exit status


The full build log is available from:

http://qa-logs.debian.net/2020/02/22/vala-panel_0.4.91+dfsg1-2_unstable.log


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

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


Checking with upstream about this...

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp6E0Iny2tYU.pgp
Description: Digitale PGP-Signatur

Processed: your mail

[Debian Bug Tracking System]

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

> severity 949361 important
Bug #949361 [src:r-cran-ranger] r-cran-ranger: autopkgtest regression on some 
architectures
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#955315: marked as done (fusiondirectory depends on php-recode which has been dropped)

[Debian Bug Tracking System]

Your message dated Mon, 20 Apr 2020 06:03:35 +
with message-id 
and subject line Bug#955315: fixed in fusiondirectory 1.3-2
has caused the Debian Bug report #955315,
regarding fusiondirectory depends on php-recode which has been dropped
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.)


-- 
955315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fusiondirectory
Version: 1.3-1
Severity: serious
Justification: not installable
X-Debbugs-CC: php-defau...@package.debian.org
Control: block 955027 by -1

Dear maintainer(s),

The php-defaults source package dropped the php-recode package that your
package depends on. Please fix your code to not require php-recode, or
align with the php-defaults maintainers how this situation should be fixed.

Paul





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: fusiondirectory
Source-Version: 1.3-2
Done: Mike Gabriel 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Apr 2020 07:47:13 +0200
Source: fusiondirectory
Architecture: source
Version: 1.3-2
Distribution: unstable
Urgency: medium
Maintainer: FusionDirectory Packagers 
Changed-By: Mike Gabriel 
Closes: 955315
Changes:
 fusiondirectory (1.3-2) unstable; urgency=medium
 .
   * debian/control:
 + Drop php-recode from D. An alternative code path to its usage exists
   (iconv). (Closes: #955315).
Checksums-Sha1:
 1650dd61bce60ffa15155ff5161887743c9a9aa7 12654 fusiondirectory_1.3-2.dsc
 0f84fd0dc272d82cab27ab7107ee2025a64fff10 45884 
fusiondirectory_1.3-2.debian.tar.xz
 074e02806fb2522fbdd3a275ed62fb90fb872df8 9694 
fusiondirectory_1.3-2_source.buildinfo
Checksums-Sha256:
 454e5fdd395588e2ea4e4ef61ae7a81857aed3a9da74e403a5774d1497219670 12654 
fusiondirectory_1.3-2.dsc
 f3d38107007a0238e8933f3d3388e933b54d28bf5f1cf0e15e3d46a31a8b3b19 45884 
fusiondirectory_1.3-2.debian.tar.xz
 7c5b99ccadf8fa6427fe618065c88014cd8374bdb13180c0b3f26eeb563bc21e 9694 
fusiondirectory_1.3-2_source.buildinfo
Files:
 635160ce1aebd7213dc82f22a057be63 12654 web optional fusiondirectory_1.3-2.dsc
 caef11bede563187bdfe71c046468656 45884 web optional 
fusiondirectory_1.3-2.debian.tar.xz
 49734306e2f931e5e637eba3b3f8a81d 9694 web optional 
fusiondirectory_1.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl6dN4oVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxM7UP/1S6GENZuBni4BfQ5oxNlFZOKJ6f
Rk1x5BpyKRhQsRa6IGoP2xHaf5PVmXbpKjNQqMPbRSYjclQ2cqYvtb+zbvYEjERs
8j7sISqoF1pybfNeCr269dblV/CwNpuTacj4g7KGknrG/ubq+4dK8lBxnWYrF8B+
+N03S4Wta1Bb8ew16SX3pDfrvcW9ko6k3qbaROIywYn/yKYhv747A4FaTLG11y92
DcwLsliY1PCJB7pnWB2Qos/6B0IG74sNWi6JG5qxWNV3m5rccvb7VFSYyI74zUDk
FIQzKZ3bNxaY/0Z8kSUswdeWbKivOr6F7jeil5aeus3BFTSD7GeRRcEnYhS+6FBf
dtZoh7EyXCXN08omeCxPq9dBXYfTFImb+5XfYuOm4x8jgFDmqd7cF5RqH2zGZLt3
YoAYmDKROrC+MXxttbBMGXkYrLDWJJWcRemJ9MSPNJ0vREur/tgv5ub1LrYHe2cu
u6f5UJ37WyqDtGCJTojLpFO3s7F9dBzlB/QIQ0IXrhZMCqHxo/DZroVhwSUSPXX8
MKvkVWqpm9gkKC8v1RQUMximc+IL9SH4Hu3wDDrXSG72mWCjR5iz1z/9KO+0+Nc7
Kay+JkMkk88x7uB8UrUi9ISVrFB/ZkEpErT8GyeQGviMbuuULTl5Q2RYNq2jejjp
rQ+OMCk00z1SdhcU
=AIyB
-END PGP SIGNATURE End Message ---