Bug#950707: [monit] Depends: libcrypt1 (>= 1:4.1.0) but it is not going to be installed

[Jean-Marc LACROIX]

Package: monit
Version: 1:5.20.0-6
Severity: grave

Dear maintainers,

Many thanks for the packaging of this application on Debian Gnu/Linux.

It seems there is one dependancy change (?) on recent monit Buster 10.2.
As a result, it is not more possible to install monit Debian package
on Buster 10.2 release.

My configuration is 

ansible@srv-nfs-110:~$ cat /etc/debian_version
10.2


ansible@srv-nfs-110:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster

ansible@srv-nfs-110:~$ uname -a
Linux srv-nfs-110 4.14.150-odroidxu4 #1 SMP PREEMPT Mon Oct 28 07:56:57 
CET 2019 armv7l GNU/Linux


ansible@srv-nfs-110:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#"
/etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb 
http://ftp.fr.debian.org/debian buster-backports main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb 
http://ftp.debian.org/debian/ buster main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_next.list:deb 
http://ftp.debian.org/debian/ bullseye main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb 
http://ftp.debian.org/debian/ stretch main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb 
http://security.debian.org buster/updates main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb 
http://ftp.fr.debian.org/debian buster-updates main contrib non-free



ansible@srv-nfs-110:~$ grep P 
/etc/apt/preferences.d/preferences_debian_v_10_buster* |grep -v "#"

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release 
o=Debian,l=Debian,n=buster-update

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 901
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release 
o=Debian,l=Debian,n=buster

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 900
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release 
o=Debian,l=Debian,n=buster-backports

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release 
o=Debian,l=Debian,n=stretch

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 400
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release 
o=Debian,l=Debian,n=testing

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release 
o=Debian,l=Debian,n=unstable

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: udev
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release 
o=Debian,l=Debian,n=*

/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Package: 
dhcpcd5
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin: 
release *
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin-Priority: 
-1
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Package: 
elogind
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin: 
release *
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin-Priority: 
-1
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Package: 
systemd
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin: 
release *
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin-Priority: 
-1

ansible@srv-nfs-110:~$



ansible@srv-nfs-110:~$ deborphan

ansible@srv-nfs-110:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version 
Architecture Description

+++-=-===--===


The issue !

ansible@srv-nfs-110:~$ sudo apt install monit
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distributi

Bug#842882: marked as done (jp2a: Version 1.0.7 improper to be released)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 03:04:39 +
with message-id 
and subject line Bug#842882: fixed in jp2a 1.0.8-1
has caused the Debian Bug report #842882,
regarding jp2a: Version 1.0.7 improper to be released
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.)


-- 
842882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jp2a
Version: 1.0.7-1
Severity: important
Tags: upstream

The upstream declared that 1.0.7 version was a mistake. More details here:

https://github.com/cslarsen/jp2a/issues/6#issuecomment-257672782

This version is in experimental and cannot be send to unstable.

Eriberto
--- End Message ---
--- Begin Message ---
Source: jp2a
Source-Version: 1.0.8-1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated jp2a 
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, 04 Feb 2020 22:22:24 -0300
Source: jp2a
Architecture: source
Version: 1.0.8-1
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho 
Changed-By: Joao Eriberto Mota Filho 
Closes: 842882 848673
Changes:
 jp2a (1.0.8-1) unstable; urgency=medium
 .
   * New upstream version 1.0.8. (Closes: #842882, LP: #1252209)
   * Being the maintainer again. (Closes: #848673)
   * New upstream homepage.
   * debian/control:
   - Added 'Rules-Requires-Root: no' to source stanza.
   - Bumped Standards-Version to 4.5.0.
   * debian/copyright:
   - Added Upstream-Contact field.
   - Added new rights for upstream and packaging.
   - Updated packaging copyright years.
   * debian/docs: created to provide the BUGS file.
   * debian/patches/:
   - 10_fix-manpage.patch: removed. The upstream fixed a macro manpage.
 Thanks.
   - 10_spelling-manpage.patch: created to fix a spelling error in manpage.
   * debian/salsa-ci.yml: added to provide CI tests for Salsa.
   * debian/source/include-binaries: added to allow binaries in CI tests.
   * debian/tests/*: created to provide some CI tests.
Checksums-Sha1:
 8c435839b5c504e049e05c343a13be8d97309c16 1867 jp2a_1.0.8-1.dsc
 c2f1c9ea65cf63a2443dc9da768fa8a6b0310b12 236823 jp2a_1.0.8.orig.tar.gz
 1608bbb35a38297fe90073c0774ed08b17d6a58d 40992 jp2a_1.0.8-1.debian.tar.xz
 2225e9bcc84330d2a260817b32c1458a6e1ea513 6163 jp2a_1.0.8-1_source.buildinfo
Checksums-Sha256:
 74062e3c6edc20cc1c1bb538f283738e49e845900a164ab4211391e5fa7aa706 1867 
jp2a_1.0.8-1.dsc
 4ea8dd558d2d95ffd230113af478a645133c26f1ced9f9871b37630ae774f069 236823 
jp2a_1.0.8.orig.tar.gz
 82c9e314e2bf4f48c4aafd6ed8598e5aa619a2606dc26bb51c203d99eb99c301 40992 
jp2a_1.0.8-1.debian.tar.xz
 0f03bc031567fef53a9e4600acf0a39e6dcb96e9fb993aa8cbf198ae666c7e28 6163 
jp2a_1.0.8-1_source.buildinfo
Files:
 155257de3021c75ac8d25a92cad67984 1867 graphics optional jp2a_1.0.8-1.dsc
 3060c420c2b63484c023a0af62977053 236823 graphics optional 
jp2a_1.0.8.orig.tar.gz
 4a59e7f884b853ee35fb16d8d94b437e 40992 graphics optional 
jp2a_1.0.8-1.debian.tar.xz
 3e4bcaba028383ac4ca147e439036f49 6163 graphics optional 
jp2a_1.0.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl46K5AACgkQ3mO5xwTr
6e8fCxAAg1aUm2ZhbEiaEItE23C7705Ll8fNobBRGmTnJ04QUoRWnxoPk9WkRaZa
rtR1sIOrBu2rlwxbAP31sZu3WG+x1wqFrOLevo4cc1GnoLQV2FbErvSDihzpzFAL
T1C/cL2yc3LwU4s37kPPint+uJFJyW82XIEAfFeLznWoyZ9N0m7o+tKFnoX9n2wP
KwixWBZGxiUtP02ol/5/kB3awO7Uht5kPo3NpUFQ75pwTGGSZWmRhjkk6D/WaitH
bCBQnJ5SUpxZGwEuu2Ae6wDatufJ5s/6MYcFoWKpIbnvAdGC73gsil2Tw5/reLQu
RAqyo9l1iqH+7a9tHgf0DB8G00r8UwtWWyKjL3A1oS8uKJ6zXU7KKb+TPOySO30t
CQbzpTWY17qcQWEtXaLxQW3k1j4LOhvi8Z1jlvVhrqGnwZWvvW2OO4OC5/6mEpRc
NxZdAUiSs8OzPtmlkJMuw6ywXpq/TRVoXn0N8fu0HfbsoXxZMAJxIE+cXsn4P4ls
PyRsR1gZfyGDh9nCUMIyBYY9+nmwswRslp1mlkpRQ/tucdbT3dBOXEDrBO844/V3
k1/zviuuo0Mdd6WXv1dJYNfYM3uI2UuUXV+JR1w99E9vqo5/KP9llECMHg59g1sj
u7bu/LdCYpDTBtiA7O3SzZVS1kqo/g48h+SR5WRELTh3dQnl+ZM=
=bvOM
-END PGP SIGNATURE End Message ---

Processed (with 1 error): upstream Py3 support

[Debian Bug Tracking System]

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

> forwarded 938746 
> https://git.launchpad.net/ufw/commit/?id=0074e3c44ff122bd320d0d631e68e8964d293557
Bug #938746 [src:ufw] ufw: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 
'https://git.launchpad.net/ufw/commit/?id=0074e3c44ff122bd320d0d631e68e8964d293557'.
> tags 942146 wontfix # removal planned
Unknown tag/s: #, removal, planned.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore.

Bug #942146 [src:koji] koji: CVE-2019-17109
Added tag(s) wontfix.
> forwarded 938637 https://bugs.freedesktop.org/show_bug.cgi?id=80803
Bug #938637 [src:telepathy-gabble] telepathy-gabble: Python2 removal in 
sid/bullseye
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=80803'.
> tags 938637 fixed-upstream
Bug #938637 [src:telepathy-gabble] telepathy-gabble: Python2 removal in 
sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#937525: marked as done (RM: pyro -- removal triggered by the Python2 removal)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:55:46 +
with message-id 
and subject line Bug#937525: Removed package(s) from unstable
has caused the Debian Bug report #937525,
regarding RM: pyro -- removal triggered by the Python2 removal
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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pyro

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 ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  pyro |   1:3.16-3 | source, all
  pyro-doc |   1:3.16-3 | all
pyro-examples |   1:3.16-3 | all
  pyro-gui |   1:3.16-3 | all

--- Reason ---
removal triggered by the Python2 removal
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 937...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/937525

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 

Bug#921384: marked as done (node-stringprep breaks node-xmpp autopkgtest)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:54:20 +
with message-id 
and subject line Bug#950658: Removed package(s) from unstable
has caused the Debian Bug report #921384,
regarding node-stringprep breaks node-xmpp autopkgtest
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.)


-- 
921384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-stringprep, node-xmpp
Control: found -1 node-stringprep/0.8.0-5
Control: found -1 node-xmpp/0.3.2-4
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of node-stringprep the autopkgtest of node-xmpp
fails in testing when that autopkgtest is run with the binary packages
of node-stringprep from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
node-stringprepfrom testing0.8.0-5
node-xmpp  from testing0.3.2-4
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 node-stringprep
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? If needed, please change the
bug's severity.

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=node-stringprep

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-xmpp/1853210/log.gz

autopkgtest [05:55:44]: test command2: vows --spec
autopkgtest [05:55:44]: test command2: [---

  ♢ JID

  parsing
✓ parse a "domain" JID
✓ parse a "user@domain" JID
✓ parse a "domain/resource" JID
✓ parse a "user@domain/resource" JID
✓ parse an internationalized domain name as unicode
✗ parse an internationalized domain name as ascii/punycode
»
actual expected

öxn--ko-eka.de
 // /usr/lib/nodejs/vows/lib/assert/macros.js:14
✗ parse a JID with punycode
»
actual expected

приме́р.рфxn--lsa92diaqnge.xn--p1ai
 // /usr/lib/nodejs/vows/lib/assert/macros.js:14
  serialization
✓ serialize a "domain" JID
✓ serialize a "user@domain" JID
✓ serialize a "domain/resource" JID
✓ serialize a "user@domain/resource" JID
  equality
✓ parsed JIDs should be equal
✓ parsed JIDs should be not equal
✓ should ignore case in user
✓ should ignore case in domain
✓ should not ignore case in resource
✓ should ignore international caseness

✗ Broken » 15 honored ∙ 2 broken (0.015s)

autopkgtest [05:55:45]: test command2: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.3.2-4+rm

Dear submitter,

as the package node-xmpp 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/950658

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#896206: marked as done (python-sciscipy: scilab fails to import)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:51:42 +
with message-id 
and subject line Bug#950515: Removed package(s) from unstable
has caused the Debian Bug report #896206,
regarding python-sciscipy: scilab fails to import
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.)


-- 
896206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-sciscipy
Version: 1.0.1-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-sciscipy importing the module scilab
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scilab.py", line 69, in 
cdll.LoadLibrary("/usr/lib/scilab/libscilab.so.0")
  File "/usr/lib/python2.7/ctypes/__init__.py", line 444, in LoadLibrary
return self._dlltype(name)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 366, in __init__
self._handle = _dlopen(self._name, mode)
OSError: /usr/lib/scilab/libscilab.so.0: cannot open shared object file: No 
such file or directory

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 1.0.1-2+rm

Dear submitter,

as the package sciscipy 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/950515

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#884535: marked as done (sciscipy FTBFS with scilab 6.0.0-1)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:51:42 +
with message-id 
and subject line Bug#950515: Removed package(s) from unstable
has caused the Debian Bug report #884535,
regarding sciscipy FTBFS with scilab 6.0.0-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.)


-- 
884535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sciscipy
Version: 1.0.1-2
Severity: serious
Tags: buster sid

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

...
   dh_auto_build
dh_auto_build: Compatibility levels before 9 are deprecated (level 5 in use)
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
copying scilab.py -> build/lib.linux-x86_64-2.7
running build_ext
building 'sciscipy' extension
C compiler: x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-j9xj4T/python2.7-2.7.14=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC

creating build/temp.linux-x86_64-2.7
compile options: '-DSCI="/usr/local/share/scilab" -DSCIDEBUG=0 -DNUMPY=1 
-I/usr/include/scilab -I/usr/include/scilab/core 
-I/usr/include/scilab/call_scilab 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c'
x86_64-linux-gnu-gcc: deallocator.c
In file included from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1809:0,
 from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
 from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
 from deallocator.h:7,
 from deallocator.c:7:
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
 warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it by " \
  ^~~
In file included from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:27:0,
 from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
 from deallocator.h:7,
 from deallocator.c:7:
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/__multiarray_api.h:1453:1:
 warning: '_import_array' defined but not used [-Wunused-function]
 _import_array(void)
 ^
x86_64-linux-gnu-gcc: util.c
In file included from /usr/include/scilab/api_scilab.h:36:0,
 from util.h:8,
 from util.c:2:
/usr/include/scilab/api_stack_common.h:486:1: warning: function declaration 
isn't a prototype [-Wstrict-prototypes]
 SciErr sciErrInit();
 ^~
util.c: In function 'read_sci_type':
util.c:27:38: error: 'pvApiCtx' undeclared (first use in this function); did 
you mean 'pStrCtx'?
 sciErr = readNamedMatrixOfDouble(pvApiCtx, "_tmp_value_", &m, &n, NULL);
  ^~~~
  pStrCtx
util.c:27:38: note: each undeclared identifier is reported only once for each 
function it appears in
util.c: In function 'is_real':
util.c:55:31: error: 'pvApiCtx' undeclared (first use in this function); did 
you mean 'pStrCtx'?
 return !isNamedVarComplex(pvApiCtx, name);
   ^~~~
   pStrCtx
util.c:56:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
In file included from /usr/include/scilab/api_scilab.h:36:0,
 from util.h:8,
 from util.c:2:
/usr/include/scilab/api_stack_common.h:486:1: warning: function declaration 
isn't a prototype [-Wstrict-prototypes]
 SciErr sciErrInit();
 ^~
util.c: In function 'read_sci_type':
util.c:27:38: error: 'pvApiCtx' undeclared (first use in this function); did 
you mean 'pStrCtx'?
 sciErr = readNamedMatrixOfDouble(pvApiCtx, "_tmp_value_", &m, &n, NULL);
  ^~~~
  pStrCtx
util.c:27:38: note: each undeclared identifier is reported only once for each 
function it appears in
util.c: In function 'is_real':
util.c:55:31: error: 'pvApiCtx' undeclared (first use in this function); di

Bug#938445: marked as done (sciscipy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:51:42 +
with message-id 
and subject line Bug#950515: Removed package(s) from unstable
has caused the Debian Bug report #938445,
regarding sciscipy: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:sciscipy

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

Dear submitter,

as the package sciscipy 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/950515

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#949859: marked as done (RM: google-apputils-python -- RoQA; leaf package; deprecated upstream; RC buggy)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:47:56 +
with message-id 
and subject line Bug#949859: Removed package(s) from unstable
has caused the Debian Bug report #949859,
regarding RM: google-apputils-python -- RoQA; leaf package; deprecated 
upstream; RC buggy
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.)


-- 
949859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-apputils-python
Severity: serious

Hello,
i think we should remove google-apputils-python from debian:

* last upstream release in 2014
* upstream marked[1] it as "Obsolete. Please migrate to absl-py instead."
* no reverse dependencies for both py2 and py3 packages
* RC-buggy since a year and a half with no action on a (simple?) bug

[1] https://pypi.org/project/google-apputils/

If i dont hear back within a week with a good reason to keep this package, i'll
file for its removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

google-apputils-python |0.4.1-1 | source
python-google-apputils |0.4.1-1 | all
python3-google-apputils |0.4.1-1 | all

--- Reason ---
RoQA; leaf package; deprecated upstream; RC buggy
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 949...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/949859

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#950445: marked as done (RM: python-couchdb -- RoQA; python2-only; leaf package; deprecated upstream)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:49:04 +
with message-id 
and subject line Bug#950445: Removed package(s) from unstable
has caused the Debian Bug report #950445,
regarding RM: python-couchdb -- RoQA; python2-only; leaf package; deprecated 
upstream
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.)


-- 
950445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-couchdb
Severity: serious

Hello,
i believe this package should be removed from debian:

* currently py2 only in Debian, with py3 support upstream
* no reverse dependencies
* low popcon
* deprecated upstram, python-cloudant suggested as a better replacement
  (https://github.com/djc/couchdb-python/blob/master/README.rst)

If i dont hear a good reason to keep this package in Debian within a week, i'll
file for its removal.

Regards,
Sandro

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

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

Versions of packages python-couchdb depends on:
ii  libjs-jquery   3.3.1~dfsg-3
ii  libjs-underscore   1.9.1~dfsg-1
ii  python 2.7.16-1
ii  python-simplejson  3.16.0-1

python-couchdb recommends no packages.

Versions of packages python-couchdb suggests:
pn  couchdb  
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-couchdb |   0.10-1.1 | source, all

--- Reason ---
RoQA; python2-only; leaf package; deprecated upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/950445

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#950064: marked as done (pyxb FTBFS with Python 3.8 as supported version)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:47:31 +
with message-id 
and subject line Bug#946602: Removed package(s) from unstable
has caused the Debian Bug report #950064,
regarding pyxb FTBFS with Python 3.8 as supported version
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.)


-- 
950064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyxb
Version: 1.2.6+dfsg-2
Severity: serious
Tags: ftbfs bullseye sid

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

...
tests/trac/test-trac-0231.py failed in compile: function takes 3 arguments plus 
optional tzinfo (8 given)
Traceback (most recent call last):
  File "setup.py", line 222, in 
setup(name='PyXB',
  File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
dist.run_commands()
  File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
  File "setup.py", line 150, in run
eval(rv, g)
  File "test_trac_0231", line 47, in 
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 1818, in 
GeneratePython
modules = generator.bindingModules()
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 2881, in 
bindingModules
self.__generateBindings()
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 2868, in 
__generateBindings
GenerateSTD(std, self)
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 558, in 
GenerateSTD
GenerateFacets(std, generator, **kw)
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 409, in 
GenerateFacets
outf.write("%s = %s(%s)\n" % binding_module.literal( (facet_var, fc, argset 
), **kw))
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 1562, in 
literal
return self.__bindingIO.literal(*args, **kw)
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 1229, in 
literal
return pythonLiteral(*args, **kw)
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 208, in 
pythonLiteral
return type(value)(pythonLiteral(list(value), **kw))
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 200, in 
pythonLiteral
return [ pythonLiteral(_v, **kw) for _v in value ]
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 200, in 

return [ pythonLiteral(_v, **kw) for _v in value ]
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 196, in 
pythonLiteral
return ', '.join([ '%s=%s' % (k, pythonLiteral(v, **kw)) for (k, v) in 
six.iteritems(value) ])
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 196, in 

return ', '.join([ '%s=%s' % (k, pythonLiteral(v, **kw)) for (k, v) in 
six.iteritems(value) ])
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/generate.py", line 219, in 
pythonLiteral
return PrefixModule(value, value.pythonLiteral())
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/basis.py", line 1133, in 
pythonLiteral
return self.PythonLiteral(self)
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/basis.py", line 1127, in 
PythonLiteral
value = value.xsdLiteral()
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/basis.py", line 1010, in 
xsdLiteral
return self.XsdLiteral(self)
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/datatypes.py", line 761, in 
XsdLiteral
value += datetime.timedelta(minutes=cls.__MinutesPerHalfDay)
  File "/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/datatypes.py", line 685, in 
__new__
raise TypeError('function takes %d arguments plus optional tzinfo (%d 
given)' % (len(cls._ValidFields), len(args)))
TypeError: function takes 3 arguments plus optional tzinfo (8 given)
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.2.6+dfsg-3+rm

Dear submitter,

as the package pyxb 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/946602

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

Bug#899527: marked as done (google-apputils-python: Invalid maintainer address cloud-packa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:48:03 +
with message-id 
and subject line Bug#949859: Removed package(s) from unstable
has caused the Debian Bug report #899527,
regarding google-apputils-python: Invalid maintainer address 
cloud-packa...@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.)


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

Dear uploader of google-apputils-python,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package google-apputils-python since the list address
cloud-packa...@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
cloud-packa...@lists.alioth.debian.org is 2.

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

Dear submitter,

as the package google-apputils-python 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/949859

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

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:48:03 +
with message-id 
and subject line Bug#949859: Removed package(s) from unstable
has caused the Debian Bug report #936637,
regarding google-apputils-python: 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.)


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

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

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

Dear submitter,

as the package google-apputils-python 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/949859

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

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:49:10 +
with message-id 
and subject line Bug#950445: Removed package(s) from unstable
has caused the Debian Bug report #937664,
regarding python-couchdb: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-couchdb

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

Dear submitter,

as the package python-couchdb 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/950445

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#933483: marked as done (python3-pyxb: missing Breaks+Replaces: python-pyxb)

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:47:31 +
with message-id 
and subject line Bug#946602: Removed package(s) from unstable
has caused the Debian Bug report #933483,
regarding python3-pyxb: missing Breaks+Replaces: python-pyxb
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.)


-- 
933483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyxb
Version: 1.2.6+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../python3-pyxb_1.2.6+dfsg-3_all.deb ...
  Unpacking python3-pyxb (1.2.6+dfsg-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pyxb_1.2.6+dfsg-3_all.deb (--unpack):
   trying to overwrite '/usr/bin/pyxbdump', which is also in package 
python-pyxb 1.2.6+dfsg-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-pyxb_1.2.6+dfsg-3_all.deb


cheers,

Andreas


python-pyxb=1.2.6+dfsg-2_python3-pyxb=1.2.6+dfsg-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.2.6+dfsg-3+rm

Dear submitter,

as the package pyxb 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/946602

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

[Debian Bug Tracking System]

Your message dated Wed, 05 Feb 2020 00:48:38 +
with message-id 
and subject line Bug#950436: Removed package(s) from unstable
has caused the Debian Bug report #937393,
regarding pyblosxom: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pyblosxom

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.3-3+rm

Dear submitter,

as the package pyblosxom 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/950436

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#950695: seaborn: FTBFS test failure in TestFacetGrid.test_set_ticklabels

[Rebecca N. Palmer]

Package: python3-seaborn
Version: 0.9.0-2
Severity: serious

Found during statsmodels transition testing, but also occurs without 
statsmodels.  I have not investigated further.


__ TestFacetGrid.test_set_ticklabels 
___


self = 

def test_set_ticklabels(self):

g = ag.FacetGrid(self.df, row="a", col="b")
g.map(plt.plot, "x", "y")
xlab = [l.get_text() + "h" for l in g.axes[1, 0].get_xticklabels()]
ylab = [l.get_text() for l in g.axes[1, 0].get_yticklabels()]

g.set_xticklabels(xlab)
g.set_yticklabels(rotation=90)

got_x = [l.get_text() for l in g.axes[1, 1].get_xticklabels()]
got_y = [l.get_text() for l in g.axes[0, 0].get_yticklabels()]
npt.assert_array_equal(got_x, xlab)
npt.assert_array_equal(got_y, ylab)

x, y = np.arange(10), np.arange(10)
df = pd.DataFrame(np.c_[x, y], columns=["x", "y"])
g = ag.FacetGrid(df).map(pointplot, "x", "y", order=x)
g.set_xticklabels(step=2)
got_x = [int(l.get_text()) for l in g.axes[0, 0].get_xticklabels()]
npt.assert_array_equal(x[::2], got_x)

g = ag.FacetGrid(self.df, col="d", col_wrap=5)
g.map(plt.plot, "x", "y")
g.set_xticklabels(rotation=45)
g.set_yticklabels(rotation=75)
for ax in g._bottom_axes:
for l in ax.get_xticklabels():
>   nt.assert_equal(l.get_rotation(), 45)

seaborn/tests/test_axisgrid.py:485:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

/usr/lib/python3.8/unittest/case.py:912: in assertEqual
assertion_func(first, second, msg=msg)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _


self = , first = 0.0, second = 45
msg = '0.0 != 45'

def _baseAssertEqual(self, first, second, msg=None):
"""The default assertEqual implementation, not type specific."""
if not first == second:
standardMsg = '%s != %s' % _common_shorten_repr(first, second)
msg = self._formatMessage(msg, standardMsg)
>   raise self.failureException(msg)
E   AssertionError: 0.0 != 45

/usr/lib/python3.8/unittest/case.py:905: AssertionError

Processed: severity of 950637 is normal

[Debian Bug Tracking System]

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

> severity 950637 normal
Bug #950637 [src:xtables-addons] update build-dep on iptables-dev
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: py2removal bugs severity updates - 2020-02-04 21:35:26.447826+00:00

[Debian Bug Tracking System]

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

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

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

Bug#950688: marked as done (boost1.71: python autopkgtest fails)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 21:36:27 +
with message-id 
and subject line Bug#950688: fixed in boost1.71 1.71.0-6
has caused the Debian Bug report #950688,
regarding boost1.71: python autopkgtest fails
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.)


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

Source: boost1.71
Version: 1.71.0-5
Severity: serious

The boost1.71 python autopkgtest fails with cmake >= 3.16 because the python
include path isn't added correctly.

In debian/tests/srcs/python/CMakeLists.txt the variable Python_INCLUDE_DIR
is used but the correct variable is Python_INCLUDE_DIRS (S at the end).

I'm not quite sure why this worked before but Python_INCLUDE_DIR isn't part
of the documented FindPython interface. See:
https://cmake.org/cmake/help/v3.15/module/FindPython.html

Filing as serious since it blocks cmake migrating to testing.

Cheers,
Felix
--- End Message ---
--- Begin Message ---
Source: boost1.71
Source-Version: 1.71.0-6

We believe that the bug you reported is fixed in the latest version of
boost1.71, 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.
Anton Gladky  (supplier of updated boost1.71 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, 04 Feb 2020 22:10:35 +0100
Source: boost1.71
Architecture: source
Version: 1.71.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Anton Gladky 
Closes: 950688
Changes:
 boost1.71 (1.71.0-6) unstable; urgency=medium
 .
   * [ef8987f] Fix python autopkgtest. (closes: #950688)
   * [aad42c4] Trim trailing whitespace.
   * [5b9edee] Fix failing autopkgtest graph-parallel
Checksums-Sha1:
 4e52030537a275502ab0530c8221a2166a4ca348 8296 boost1.71_1.71.0-6.dsc
 103e322ef0810a63fafa04f2b43bfb552638bbbe 359780 
boost1.71_1.71.0-6.debian.tar.xz
 fa371601e6e1b629994a4b3eda16d7b1a15c0bd9 12319 
boost1.71_1.71.0-6_source.buildinfo
Checksums-Sha256:
 5348765ff57dfdbdc2e1b630b4f07ad1e636644981b348c839734b78c35b9974 8296 
boost1.71_1.71.0-6.dsc
 39e43cb4ba6916b01f95c139043f9e22b08a9380869982f665ca6e29169602b3 359780 
boost1.71_1.71.0-6.debian.tar.xz
 8d9f26dc841790a6d04ca4808f7b61fca69a67854906e639a85e669e73a3798b 12319 
boost1.71_1.71.0-6_source.buildinfo
Files:
 d8fd1a200c30c2830c0e763cd3ef6221 8296 libs optional boost1.71_1.71.0-6.dsc
 8803e51d85ba31a9a1ef3c7fbdcd8a87 359780 libs optional 
boost1.71_1.71.0-6.debian.tar.xz
 a4963610fc98252d26a905eb79ac2cc3 12319 libs optional 
boost1.71_1.71.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl453igACgkQ0+Fzg8+n
/waOXw//ZkxlTSAPJ1wTbqcf/UzBMdknoIx2ONoEppr6dK+6S90WFAtUJAoq8c1T
USi2Y11KmrL9hc1NO8kNc0UHoDA1OXIdWlUS5wIIpVR1Uo4aoIgRITIniu+yugYj
q2A5I7yqYJoBnVHqcenMwetgK1y91prDHvzwDU+dlmjGRbGe41UWp0VsUdX1LDhA
HeuK+WqmiTnrxp5b58ASi9uUExYhnLlY1HO64q1Za5Op59ctXUCUhPnVIoZM1D4E
lNKfHqh0DaBNRSkOKTtDXb04HxaEOqAevvQ1h8/czgEC5YOqXrTfML+yYjhJbn5G
OnltZnMD7y964xnfKQ853bmTgQ8xEfTcg431+Dfcgq7zdyWWqSBJB3zM7Wszp7a6
EEaVR2Fgh9o+TLG5qSTnuQv3jAzSdqHsq99pOwgL9s8T11mvP7w82LfHJDftSRp3
63NcyniDfpXZTnX88Yb06oOMu75m3ErXk9qrenRfZjgBFwWmaMobTfv/yIB0W9e2
viGlV9As81ITALex1V/C4Tu0JXuprXOM7/rfOdoNP5+f+YxN2Fe0htVKF1sZIdZQ
yzlZP2VN2m5xjO3siR+OS148rZrWFWHFpbB+9JEHdA0V4r+c4HnzPvmDWmwOkVa7
xjljqd49YvePofXHW0fEgxQPq3wPJa5s0lgBVIn8EHgLN5tDsAY=
=IQax
-END PGP SIGNATURE End Message ---

Bug#950372: Is radare2 suitable for stable Debian releases?

[Moritz Mühlenhoff]

On Sat, Feb 01, 2020 at 08:51:08PM +0100, Salvatore Bonaccorso wrote:
> Hi Hilko,
> 
> On Sat, Feb 01, 2020 at 12:57:27AM +0100, Hilko Bengen wrote:
> > * Moritz Mühlenhoff:
> > 
> > >> FTR, this was as well raised back in [1]. AFAIK there was no direct
> > >> feedback to the question from Moritz back then.
> > >
> > > Yeah, we should at least remove radare2 from oldstable (IIRC for
> > > buster there's an rdep which prevents that)
> > 
> > That reverse dependency is radare2-cutter which should be treated the
> > same as radare2, IMO.
> 
> So, there would be a point release for buster and stretch very soon.
> 
> If you feel there is agreement within the Debian Security Tools team
> on it, can any of you fill the respective removal requests for the
> upcoming point release?

Given that the point releases are close, I went ahead and filed removal
bugs.

Cheers,
Moritz

Bug#949081: marked as done (wget2 FTBFS: makeinfo: command not found)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 20:46:45 +
with message-id 
and subject line Bug#949081: fixed in wget2 1.99.1-2.1
has caused the Debian Bug report #949081,
regarding wget2 FTBFS: makeinfo: 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.)


-- 
949081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wget2
Version: 1.99.1-2
Severity: serious
Tags: ftbfs

wget2 fails to build from source in unstable. A build ends with:

| /bin/bash /<>/build-aux/missing makeinfo --force -o ./wget2.info 
./wget2.texi
| /<>/build-aux/missing: line 81: makeinfo: command not found
| WARNING: 'makeinfo' is missing on your system.
|  You should only need it if you modified a '.texi' file, or
|  any other file indirectly affecting the aspect of the manual.
|  You might want to install the Texinfo package:
|  
|  The spurious makeinfo call might also be the consequence of
|  using a buggy 'make' (AIX, DU, IRIX), in which case you might
|  want to install GNU make:
|  
| make[3]: *** [Makefile:1719: wget2.stamp] Error 127
| make[3]: Leaving directory '/<>/docs'
| make[2]: *** [Makefile:1579: all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:1488: all] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:43: build-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is also reproduced by crossqa, but not yet reproduced by
reproducible builds, so it likely is a fairly recent regression.
http://crossqa.debian.net/build/wget2_1.99.1-2_armel_20200115220118.log

I suppose that this is a result of gnulib having dropped its dependency
on texinfo, so now wget2 needs to depend on texinfo itself.

Helmut
--- End Message ---
--- Begin Message ---
Source: wget2
Source-Version: 1.99.1-2.1

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated wget2 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, 28 Jan 2020 14:51:45 -0500
Source: wget2
Architecture: source
Version: 1.99.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Noël Köthe 
Changed-By: Boyuan Yang 
Closes: 949081
Changes:
 wget2 (1.99.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild against new gnulib snapshot (20200127).
   * debian/control: Add explicit build-dependency on texinfo.
 (Closes: #949081)
Checksums-Sha1:
 593e6136359cb113e344298ddf6d62e43c01062c 2385 wget2_1.99.1-2.1.dsc
 a5535ed4bbf9ca056d609a110099345f8ff6680b 3704 wget2_1.99.1-2.1.debian.tar.xz
 04b4d034481becc1070c42a49a193dcd374b5c09 10469 wget2_1.99.1-2.1_amd64.buildinfo
Checksums-Sha256:
 80845731c4bdb04a81b1d6aaccdc659699dc9a79f0c43df31464a3b3ead82476 2385 
wget2_1.99.1-2.1.dsc
 d466c158330e5aa5ba9f5de44167d694d4800fdd03d729a8cb4e9e5bea8465b1 3704 
wget2_1.99.1-2.1.debian.tar.xz
 6766570c91298ebdc30edafd9c9d355e3134a546cb62e2c6001a272a9376f4b0 10469 
wget2_1.99.1-2.1_amd64.buildinfo
Files:
 d979be2518850aadc4b8b6222e721a8b 2385 web optional wget2_1.99.1-2.1.dsc
 6ec9fb4158d43d4f2f28ff525dccb7aa 3704 web optional 
wget2_1.99.1-2.1.debian.tar.xz
 a4217224bc6bfe47933be50f943121f7 10469 web optional 
wget2_1.99.1-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl4wk2oACgkQwpPntGGC
Ws4vdw//WQfLcMpQ/0NngyEQf1vJbxpo2oTonrFWi9O5Ig0Y4Obuz3/+6oT2HEE6
SwCy3fkNCYaMMkYMZ9y9kpcbL8jTLM0FVFSsuAKGIAITfOzanuzVrN5GYlOSSxR/
+lHX4/+dLfEwRDd20YIcS5lagBBIowzW9rGFhUykcCy7WHqtClcBIWVE4+LMUlVx
aIPiXjTSKK6SKKKD/J4yz21wGKl02k9xds+bOFrnajbxKkuB5LMPkT531ncPx+Kz
BGd5PAu6BTlbb9C/OI3U41MVb/cxRDahXfXk0wfTH3LkqF5yXqG4pBwGhz5bnrtG
Vz+SF2FfmZf9mGFAjpRZveIlT5+aWX47bhkCKhARmUy9jXCWOScEbdHfoS0FnIad
zJPKI8KAsO9ZBekEnj3f6dQFLmxwa8Up1HRZsD4pw7RLnM50Y6G4sOlZp+YV7r+p
60b9OXa5qaACD5UKVfiECS

Bug#950640: marked as done (pycdio FTBFS with more than one supported python3 version)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 20:46:13 +
with message-id 
and subject line Bug#950640: fixed in pycdio 2.1.0-1
has caused the Debian Bug report #950640,
regarding pycdio FTBFS with more than one supported python3 version
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.)


-- 
950640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycdio
Version: 2.0.0-1
Severity: serious
Tags: ftbfs

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

...
creating build/temp.linux-arm64-3.8/swig
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c swig/pycdio_wrap.c -o 
build/temp.linux-arm64-3.8/swig/pycdio_wrap.o
swig/pycdio_wrap.c:149:11: fatal error: Python.h: No such file or directory
  149 | # include 
  |   ^~
compilation terminated.


The build dependency on python3-dev should be corrected to python3-all-dev.
--- End Message ---
--- Begin Message ---
Source: pycdio
Source-Version: 2.1.0-1

We believe that the bug you reported is fixed in the latest version of
pycdio, 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.
Timo Aaltonen  (supplier of updated pycdio 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, 04 Feb 2020 21:35:13 +0200
Source: pycdio
Architecture: source
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Timo Aaltonen 
Changed-By: Timo Aaltonen 
Closes: 950640
Changes:
 pycdio (2.1.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * source/options: Extend diff-ignore.
   * control: Correct python dev dependency. (Closes: #950640)
   * control: Use debhelper-compat.
Checksums-Sha1:
 d1de46abecfbf46ceefa9c07acd7d7a8478881b1 1942 pycdio_2.1.0-1.dsc
 188fdbc176d0e0fd2c08520f76cd7e8f9e477c20 241434 pycdio_2.1.0.orig.tar.gz
 3e8a1eae7ab337450686c467c632057b0336817c 1544 pycdio_2.1.0-1.debian.tar.xz
 b62ea528996d80c5cfcc0e318904b993fa397ed8 6982 pycdio_2.1.0-1_source.buildinfo
Checksums-Sha256:
 c61d07bd39599b5206d5efe83bfc0bcd02ac1347608e282ffb9811078e8e6635 1942 
pycdio_2.1.0-1.dsc
 d6d2e59d16339788835eed62ff75cfa38e7caa6f7e290dcc0d07f8ec30de6705 241434 
pycdio_2.1.0.orig.tar.gz
 b48db6facd270d1614426bc463e2ee5ecb4e3392d4b1146e8de31ad37b33e2a8 1544 
pycdio_2.1.0-1.debian.tar.xz
 c284ff5bb461cb1d2237b8e7d283df95dc8d60c57a836e1c3666e5fbe494d345 6982 
pycdio_2.1.0-1_source.buildinfo
Files:
 58e9f02f0424aedd669eb121e05969fc 1942 python optional pycdio_2.1.0-1.dsc
 d1adcee07dc0f510a983547bf5046632 241434 python optional 
pycdio_2.1.0.orig.tar.gz
 214f884ada70d93fba1e2cec2a29cb27 1544 python optional 
pycdio_2.1.0-1.debian.tar.xz
 48c7a23c5ef9e891ab2cbfd76e33d62e 6982 python optional 
pycdio_2.1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl45x5AACgkQy3AxZaiJ
hNzmyhAAmk3jmS1YIUgPM0Nyvkt4zLOdwHlcTDmCkdqNiRlYj3/16XIIlrJJAUKD
un8durxdrxPiXGiAzJxm5+4/IoyfjrqxBkRz9mKfWgF0/AwqmpEQXj04oI4uFD+n
hEuH6YrcOjFkOv2Fi72ejzy+uLe29fTxGom3WNN2YsbvGW3G4KLSwGTPxwr+fhOy
zS4sfb0GuB0iSaGIQxb0PX0N+k+T968dlkq6CK05tu8mhwPJbjh9LGcabEtusB1C
ReGjLPQFn5F7S9dD1phXU/9x2IfoB1bdTMb3+F/WfREVutTqkrXdxX8YrwoLJgRE
/tcFVX4tJ3PINUv9Rr9T3WRy+Lu4RVs6CTinwdnPcPgr0aBvTNH3j+TQimrvVKw+
NZeBOtyNwgECttcS4CpU6xVY+w8TQgS6cURuBBWrmpOoz8MNbJ+jVfQiWM3Ysjog
OakymXzF0d0TD22Y3K5NXu2qtYQXeLBPNmL7fpzq+v79Z+p71LZa5fs46Q6RRDaA
XK5tWQd2RiHlIK+XC4qjZZ3G7YI5LVZE9ZkqfsflVWSmmO7gNlfXUMJx7QTocp5Y
XOqFVw/UW/hn2ZFAFEgy2ZaWzouRbczv9X/OjBqzklE17OrvOU3fsIiBCJ1VVpz0
ABdPntXqfyTQDU1pA5gaYShv2uH0Ra14JwquUWKTWOJrHSm1Txc=
=DdG2
-END PGP SIGNATURE End Message ---

Bug#946599: marked as done (libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id 
and subject line Bug#950389: fixed in glibc 2.29-10
has caused the Debian Bug report #950389,
regarding libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole 
system
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.)


-- 
950389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcrypt1
Version: 1:4.4.10-5
Severity: critical
Justification: breaks the whole system

I’ve did a “sudo apt-get --purge dist-upgrade” and ended with,
see screenshot below.

Thankfully, I had a root session in a chroot open and used
the program, statically linked, from http://koltsoff.com/pub/getroot/
to recover access outside the chroot, by using dpkg -i --force-all
first on libc6_*.deb, then libcrypt1_*.deb. Afterwards, normal recovery
mechanisms apply.

Log:

Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  fonts-noto-hinted fonts-noto-ui-core liblouis19 libxml-simple-perl
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  libpcre2-posix0*
The following NEW packages will be installed:
  fonts-cantarell libcrypt1:i386 libcrypt1:amd64 libcrypt1 libcrypt1-dev:i386 
libcrypt1-dev liblouis20
  libpcre2-posix2 libxstring-perl linux-image-5.3.0-3-amd64:amd64
The following packages have been kept back:
  libegl1 libgl1 libgles2 libglvnd0 libglx0 librsvg2-2:i386 libselinux1:i386 
libv4l-0:i386 libv4lconvert0:i386
  libvirt-clients libvirt-daemon libvirt-daemon-system libvirt0 python3-libvirt 
tomcat9
The following packages will be upgraded:
  bochsbios debhelper debianutils drkonqi dwz fig2dev fonts-comfortaa git 
git-doc git-man gitk gitweb glibc-doc
  gstreamer1.0-alsa:i386 gstreamer1.0-alsa gstreamer1.0-libav:i386 
gstreamer1.0-plugins-bad:i386
  gstreamer1.0-plugins-base gstreamer1.0-plugins-base:i386 
gstreamer1.0-plugins-good:i386
  gstreamer1.0-plugins-ugly:i386 intel-microcode:amd64 iptables kde-spectacle 
kinit kio kwalletmanager
  libbrlapi0.7 libc-bin libc-dev-bin libc-l10n libc6:i386 libc6 libc6:amd64 
libc6-dbg libc6-dev:i386 libc6-dev
  libdbus-glib-1-2:i386 libdbus-glib-1-2 libdebhelper-perl 
libgstreamer-plugins-bad1.0-0:i386
  libgstreamer-plugins-base1.0-0:i386 libgstreamer-plugins-base1.0-0 
libgstreamer1.0-0:i386 libgstreamer1.0-0
  libhttp-cookies-perl libio-pty-perl libip4tc2 libip6tc2 libiptc0 
libjs-bootstrap4 libjs-popper.js
  libjs-sphinxdoc libkaccounts1 libkf5activities5 libkf5bookmarks5 
libkf5completion5 libkf5configwidgets5
  libkf5crash5 libkf5declarative5 libkf5globalaccel-bin libkf5globalaccel5 
libkf5globalaccelprivate5
  libkf5iconthemes5 libkf5jobwidgets5 libkf5kcmutils5 libkf5khtml5 
libkf5kiocore5 libkf5kiontlm5
  libkf5kiowidgets5 libkf5kipi32.0.0 libkf5kirigami2-5 libkf5newstuff5 
libkf5newstuffcore5 libkf5notifications5
  libkf5parts5 libkf5purpose-bin libkf5purpose5 libkf5quickaddons5 
libkf5textwidgets5 libkf5wallet-bin
  libkf5wallet5 libkwalletbackend5-5 liblinux-epoll-perl liblist-someutils-perl 
liblouis-bin liblouis-data
  liblouisutdml-bin liblouisutdml-data liblouisutdml9 libmime-lite-perl 
libmoox-late-perl libmysofa0:i386
  libmysofa0 libokular5core8 libpcre2-16-0 libpcre2-32-0 libpcre2-8-0:i386 
libpcre2-8-0 libpcre2-dev
  libqmobipocket2 libsepol1 libsepol1-dev libserd-0-0:i386 libserd-0-0 
libslirp0 libsnappy1v5:i386 libsnappy1v5
  libsord-0-0:i386 libsord-0-0 libspecio-perl libsratom-0-0:i386 libsratom-0-0 
libtype-tiny-perl libvncclient1
  libvncserver1 libwireshark-data libwmf0.2-7 libx265-179:i386 libx265-179 
libxtables12 libz3-4:i386
  linux-image-amd64:amd64 linux-libc-dev linux-libc-dev:i386 locales 
locales-all netbase node-glob okular
  python3-requests python3-urllib3 qml-module-org-kde-kcm 
qml-module-org-kde-kirigami2
  qml-module-org-kde-kquickcontrolsaddons systemsettings tcpdump texlive 
texlive-base texlive-bibtex-extra
  texlive-extra-utils texlive-font-utils texlive-fonts-extra 
texlive-fonts-extra-doc texlive-fonts-extra-links
  texlive-fonts-recommended texlive-fonts-recommended-doc texlive-formats-extra 
texlive-full texlive-games
  texlive-humanities texlive-humanities-doc texlive-lang-arabic 
texlive-lang-chinese texlive-lang-cjk
  texlive-lang-cyrillic texlive-lang-czechslovak texlive-lang-english 
texlive-lang-european texlive-lang-french
  texlive-lang-german texlive-lang-greek texlive-lang-italian 
texlive-lang-korean texlive-lang-other
  texlive-lang-polish texlive-lang-portuguese texlive-lang-spanish 
t

Bug#950389: marked as done (libc6 s390x preinstall script fails)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id 
and subject line Bug#946599: fixed in glibc 2.29-10
has caused the Debian Bug report #946599,
regarding libc6 s390x preinstall script fails
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.)


-- 
946599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-0ubuntu3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I currently use multi arch with s390x on Debian testing in an amd64 container
for continuous integration purposes for an upstream project, fwupd.

In the last day or so the container setup is failing with the following:

Selecting previously unselected package libc6:s390x.
Preparing to unpack .../2-libc6_2.29-9_s390x.deb ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open
shared object file: No such file or directory
dpkg: error processing archive /tmp/apt-dpkg-install-
Fec8mr/2-libc6_2.29-9_s390x.deb (--unpack):
 new libc6:s390x package pre-installation script subprocess returned error exit
status 127
Unpacking gcc-9-base:s390x (9.2.1-25) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-Fec8mr/2-libc6_2.29-9_s390x.deb
E: Could not configure 'libc6:s390x'.
E: Could not perform immediate configuration on 'libgcc1:s390x'. Please see man
5 apt.conf under APT::Immediate-Configure for details. (2)

The full log is available here: https://travis-
ci.org/fwupd/fwupd/jobs/644533041#L1250



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

Kernel: Linux 5.3.0-19-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

Versions of packages libc6 depends on:
ii  libgcc1  1:9.2.1-25ubuntu1

Versions of packages libc6 recommends:
ii  libidn2-0  2.2.0-2

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.73
pn  glibc-doc  
ii  locales2.30-0ubuntu3

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-10

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

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

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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, 04 Feb 2020 20:37:26 +0100
Source: glibc
Architecture: source
Version: 2.29-10
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 946599 950389
Changes:
 glibc (2.29-10) unstable; urgency=medium
 .
   * debian/debhelper.in/libc.{preinst,postrm}: Remove fallback to dpkg
 --print-architecture for pre-multiarch systems.
   * debian/debhelper.in/libc.preinst: fallback to text output in case
 perl debconf is used and perl is not usable.  Closes: #946599, #950389.
   * debian/patches/git-updates.diff: update from upstream stable branch.
Checksums-Sha1:
 d61faeac8d5822e35195c73b4bcbebd19d4b8346 8739 glibc_2.29-10.dsc
 cd6643d22f0bae8fefb9739e576f5db0f180f696 868696 glibc_2.29-10.debian.tar.xz
 edbd48a2726ce369893809d6212c1afdc5035a6f 7763 glibc_2.29-10_source.buildinfo
Checksums-Sha256:
 4365adda24264fd57faabafd0429a5f123635790fc6391d8abc2ecc15072f2b3 8739 
glibc_2.29-10.dsc
 d66ef632e204670b237b8f1a9e76e1aa9e7d5fc96d271f33128a10474740ea62 868696 
glibc_2.29-10.debian.tar.xz
 ce967535a6577186b521335a0fba06a97a0a6e096997297af4fdda134e77aa8a 7763 
glibc_2.29-10_source.buildinfo
Files:
 b5d0587c8d19387f86bba0337e2b284c 8739 libs required glibc_2.29-10.dsc
 bedc735e647a3dce401b4a27908b991b 868696 libs required 
glibc_2.29-10.debian.tar.xz
 f235628b42d0b84843bb632995bba7b5 7763 libs required 
glibc_2.29-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl45yI0A

Bug#950389: marked as done (libc6 s390x preinstall script fails)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id 
and subject line Bug#950389: fixed in glibc 2.29-10
has caused the Debian Bug report #950389,
regarding libc6 s390x preinstall script fails
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.)


-- 
950389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-0ubuntu3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I currently use multi arch with s390x on Debian testing in an amd64 container
for continuous integration purposes for an upstream project, fwupd.

In the last day or so the container setup is failing with the following:

Selecting previously unselected package libc6:s390x.
Preparing to unpack .../2-libc6_2.29-9_s390x.deb ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open
shared object file: No such file or directory
dpkg: error processing archive /tmp/apt-dpkg-install-
Fec8mr/2-libc6_2.29-9_s390x.deb (--unpack):
 new libc6:s390x package pre-installation script subprocess returned error exit
status 127
Unpacking gcc-9-base:s390x (9.2.1-25) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-Fec8mr/2-libc6_2.29-9_s390x.deb
E: Could not configure 'libc6:s390x'.
E: Could not perform immediate configuration on 'libgcc1:s390x'. Please see man
5 apt.conf under APT::Immediate-Configure for details. (2)

The full log is available here: https://travis-
ci.org/fwupd/fwupd/jobs/644533041#L1250



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

Kernel: Linux 5.3.0-19-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

Versions of packages libc6 depends on:
ii  libgcc1  1:9.2.1-25ubuntu1

Versions of packages libc6 recommends:
ii  libidn2-0  2.2.0-2

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.73
pn  glibc-doc  
ii  locales2.30-0ubuntu3

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-10

We believe that the bug you reported is fixed in the latest version of
glibc, 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.
Aurelien Jarno  (supplier of updated glibc 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, 04 Feb 2020 20:37:26 +0100
Source: glibc
Architecture: source
Version: 2.29-10
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 946599 950389
Changes:
 glibc (2.29-10) unstable; urgency=medium
 .
   * debian/debhelper.in/libc.{preinst,postrm}: Remove fallback to dpkg
 --print-architecture for pre-multiarch systems.
   * debian/debhelper.in/libc.preinst: fallback to text output in case
 perl debconf is used and perl is not usable.  Closes: #946599, #950389.
   * debian/patches/git-updates.diff: update from upstream stable branch.
Checksums-Sha1:
 d61faeac8d5822e35195c73b4bcbebd19d4b8346 8739 glibc_2.29-10.dsc
 cd6643d22f0bae8fefb9739e576f5db0f180f696 868696 glibc_2.29-10.debian.tar.xz
 edbd48a2726ce369893809d6212c1afdc5035a6f 7763 glibc_2.29-10_source.buildinfo
Checksums-Sha256:
 4365adda24264fd57faabafd0429a5f123635790fc6391d8abc2ecc15072f2b3 8739 
glibc_2.29-10.dsc
 d66ef632e204670b237b8f1a9e76e1aa9e7d5fc96d271f33128a10474740ea62 868696 
glibc_2.29-10.debian.tar.xz
 ce967535a6577186b521335a0fba06a97a0a6e096997297af4fdda134e77aa8a 7763 
glibc_2.29-10_source.buildinfo
Files:
 b5d0587c8d19387f86bba0337e2b284c 8739 libs required glibc_2.29-10.dsc
 bedc735e647a3dce401b4a27908b991b 868696 libs required 
glibc_2.29-10.debian.tar.xz
 f235628b42d0b84843bb632995bba7b5 7763 libs required 
glibc_2.29-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl45yI0A

Bug#946599: marked as done (libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id 
and subject line Bug#946599: fixed in glibc 2.29-10
has caused the Debian Bug report #946599,
regarding libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole 
system
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.)


-- 
946599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcrypt1
Version: 1:4.4.10-5
Severity: critical
Justification: breaks the whole system

I’ve did a “sudo apt-get --purge dist-upgrade” and ended with,
see screenshot below.

Thankfully, I had a root session in a chroot open and used
the program, statically linked, from http://koltsoff.com/pub/getroot/
to recover access outside the chroot, by using dpkg -i --force-all
first on libc6_*.deb, then libcrypt1_*.deb. Afterwards, normal recovery
mechanisms apply.

Log:

Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  fonts-noto-hinted fonts-noto-ui-core liblouis19 libxml-simple-perl
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  libpcre2-posix0*
The following NEW packages will be installed:
  fonts-cantarell libcrypt1:i386 libcrypt1:amd64 libcrypt1 libcrypt1-dev:i386 
libcrypt1-dev liblouis20
  libpcre2-posix2 libxstring-perl linux-image-5.3.0-3-amd64:amd64
The following packages have been kept back:
  libegl1 libgl1 libgles2 libglvnd0 libglx0 librsvg2-2:i386 libselinux1:i386 
libv4l-0:i386 libv4lconvert0:i386
  libvirt-clients libvirt-daemon libvirt-daemon-system libvirt0 python3-libvirt 
tomcat9
The following packages will be upgraded:
  bochsbios debhelper debianutils drkonqi dwz fig2dev fonts-comfortaa git 
git-doc git-man gitk gitweb glibc-doc
  gstreamer1.0-alsa:i386 gstreamer1.0-alsa gstreamer1.0-libav:i386 
gstreamer1.0-plugins-bad:i386
  gstreamer1.0-plugins-base gstreamer1.0-plugins-base:i386 
gstreamer1.0-plugins-good:i386
  gstreamer1.0-plugins-ugly:i386 intel-microcode:amd64 iptables kde-spectacle 
kinit kio kwalletmanager
  libbrlapi0.7 libc-bin libc-dev-bin libc-l10n libc6:i386 libc6 libc6:amd64 
libc6-dbg libc6-dev:i386 libc6-dev
  libdbus-glib-1-2:i386 libdbus-glib-1-2 libdebhelper-perl 
libgstreamer-plugins-bad1.0-0:i386
  libgstreamer-plugins-base1.0-0:i386 libgstreamer-plugins-base1.0-0 
libgstreamer1.0-0:i386 libgstreamer1.0-0
  libhttp-cookies-perl libio-pty-perl libip4tc2 libip6tc2 libiptc0 
libjs-bootstrap4 libjs-popper.js
  libjs-sphinxdoc libkaccounts1 libkf5activities5 libkf5bookmarks5 
libkf5completion5 libkf5configwidgets5
  libkf5crash5 libkf5declarative5 libkf5globalaccel-bin libkf5globalaccel5 
libkf5globalaccelprivate5
  libkf5iconthemes5 libkf5jobwidgets5 libkf5kcmutils5 libkf5khtml5 
libkf5kiocore5 libkf5kiontlm5
  libkf5kiowidgets5 libkf5kipi32.0.0 libkf5kirigami2-5 libkf5newstuff5 
libkf5newstuffcore5 libkf5notifications5
  libkf5parts5 libkf5purpose-bin libkf5purpose5 libkf5quickaddons5 
libkf5textwidgets5 libkf5wallet-bin
  libkf5wallet5 libkwalletbackend5-5 liblinux-epoll-perl liblist-someutils-perl 
liblouis-bin liblouis-data
  liblouisutdml-bin liblouisutdml-data liblouisutdml9 libmime-lite-perl 
libmoox-late-perl libmysofa0:i386
  libmysofa0 libokular5core8 libpcre2-16-0 libpcre2-32-0 libpcre2-8-0:i386 
libpcre2-8-0 libpcre2-dev
  libqmobipocket2 libsepol1 libsepol1-dev libserd-0-0:i386 libserd-0-0 
libslirp0 libsnappy1v5:i386 libsnappy1v5
  libsord-0-0:i386 libsord-0-0 libspecio-perl libsratom-0-0:i386 libsratom-0-0 
libtype-tiny-perl libvncclient1
  libvncserver1 libwireshark-data libwmf0.2-7 libx265-179:i386 libx265-179 
libxtables12 libz3-4:i386
  linux-image-amd64:amd64 linux-libc-dev linux-libc-dev:i386 locales 
locales-all netbase node-glob okular
  python3-requests python3-urllib3 qml-module-org-kde-kcm 
qml-module-org-kde-kirigami2
  qml-module-org-kde-kquickcontrolsaddons systemsettings tcpdump texlive 
texlive-base texlive-bibtex-extra
  texlive-extra-utils texlive-font-utils texlive-fonts-extra 
texlive-fonts-extra-doc texlive-fonts-extra-links
  texlive-fonts-recommended texlive-fonts-recommended-doc texlive-formats-extra 
texlive-full texlive-games
  texlive-humanities texlive-humanities-doc texlive-lang-arabic 
texlive-lang-chinese texlive-lang-cjk
  texlive-lang-cyrillic texlive-lang-czechslovak texlive-lang-english 
texlive-lang-european texlive-lang-french
  texlive-lang-german texlive-lang-greek texlive-lang-italian 
texlive-lang-korean texlive-lang-other
  texlive-lang-polish texlive-lang-portuguese texlive-lang-spanish 
t

Processed: found 950512 in 0.3-4, fixed 950535 in 1.8.3-2, tagging 950633, tagging 950662, tagging 950675 ...

[Debian Bug Tracking System]

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

> found 950512 0.3-4
Bug #950512 [src:quotecolors] quotecolors: not usable anymore with TB>= 68.x
Marked as found in versions quotecolors/0.3-4.
> fixed 950535 1.8.3-2
Bug #950535 [iptables] iptables-restore segfaults on nat table
Marked as fixed in versions iptables/1.8.3-2.
> tags 950633 + sid bullseye
Bug #950633 [morris] morris: FTBFS with boost1.71 deprecated signals library is 
removed
Added tag(s) bullseye and sid.
> tags 950662 + experimental
Bug #950662 {Done: Adrian Bunk } [src:pybel] pybel FTBFS: test 
failures
Added tag(s) experimental.
> tags 950675 + experimental
Bug #950675 [doxygen] doxygen-latex is now useless, should be removed from the 
archive?
Added tag(s) experimental.
> found 950675 1.8.16-2
Bug #950675 [doxygen] doxygen-latex is now useless, should be removed from the 
archive?
Marked as found in versions doxygen/1.8.16-2.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 947034 + pending
Bug #947034 [src:python-passlib] Fails to build with python3.8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#949939: marked as done (custodia build depends on the removed pep8 transitional package)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 19:35:28 +
with message-id 
and subject line Bug#949939: fixed in custodia 0.6.0-5
has caused the Debian Bug report #949939,
regarding custodia build depends on the removed pep8 transitional 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.)


-- 
949939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: custodia
Version: 0.6.0-4
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.
--- End Message ---
--- Begin Message ---
Source: custodia
Source-Version: 0.6.0-5

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated custodia 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, 04 Feb 2020 21:05:02 +0200
Source: custodia
Architecture: source
Version: 0.6.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 949939
Changes:
 custodia (0.6.0-5) unstable; urgency=medium
 .
   * control: Build-depend on python3-pep8 instead of pep8. (Closes:
 #949939)
Checksums-Sha1:
 72be293433f2fcc2c72b3e192df644f744f34d19 2203 custodia_0.6.0-5.dsc
 abb10b4b034423da39b8c8659ff97cc5db0b913c 4296 custodia_0.6.0-5.debian.tar.xz
 fbda859ed7fc5acc84ee0e5d60d9399a25197d7f 7245 custodia_0.6.0-5_source.buildinfo
Checksums-Sha256:
 626b246854fef8d7accb2c319086f89ad07cd07da444a3eaeadf5b332cd5af7c 2203 
custodia_0.6.0-5.dsc
 1b32d0c4f1a90c4677dfbc872d4bc8dbde6607b9274634366e4b94a6c516c678 4296 
custodia_0.6.0-5.debian.tar.xz
 7bffee7d5bc3382ba614fa16bd23d177be4f21358626ecd8dce781701645a6b1 7245 
custodia_0.6.0-5_source.buildinfo
Files:
 d02e053592a809f903996ab5a9d9a25f 2203 admin optional custodia_0.6.0-5.dsc
 03bd5f3afc82491d8e4d536f798b255a 4296 admin optional 
custodia_0.6.0-5.debian.tar.xz
 a7a687028d1d5ba02f5b93f493e333ef 7245 admin optional 
custodia_0.6.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl45wMEACgkQy3AxZaiJ
hNxc4w//YoG6JFqmSazeqxCPysKQ+ifYWsrosIXMEHpNe+qLQ+jNrN/4IeWXkkbs
Lv5MsJMif4Z/MXwiw1UcRUg35CjyA3hkr3D0a6oz854cR5IQuPPzCuC9YgsFAE2w
gwEpHPNeKI2+ggaYM0HoIocitbURo1hxcpPHgNr9KITx1ZkpDKKovQzPZ7btNvrr
Q2sJbuyuc8ypiqN4q/YSMEIy08TrFBYr6nK9yzhjtB1eH2FN9OSMCKNKNbW25abr
munnHBPpWZJJuua5icEKOcmCXEIzirmdmPCTd9fHmJZM3kC3AFhwJjMW1FNMqPII
bZ7fHhSMFo4nLGNf/xonPMstxULKetvx2JzVJdpsP51x2MOMow7F3M0VN4WJF0e/
g0xF3bDDcst1to/qDbnZWruCi7X3pNyH2+5NIiZSg2jxMYgUmPCYXDOhLSA+AEaF
Lv7/FqehMoZd5kvKdfgHfgQNtbSJ2JbrW0Z11o/b+tvz+XpASnVJ53acfrkulxxi
r4Npg1cHlRj4K8Zyh+udXVcVOTP9f6jgq8QbqIU5x7rglDIKCoQ294m/nzHMOOF8
qp4jYt6e1YGhwUu/4S/3Sdk/hlHTPedrlBI6QJfJwCgr4SQb8fTgHr7NSvWHgHzY
/hCF5bn6t5p7F2qSaeGdcmmMfJEHc9rFb32xFxNVLqHQDKLv08c=
=SGXs
-END PGP SIGNATURE End Message ---

Processed: Bug#946599 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #946599 [libc6] libcrypt1: failure to switch from libc6 to libcrypt1 hoses 
the whole system
Bug #950389 [libc6] libc6 s390x preinstall script fails
Added tag(s) pending.
Added tag(s) pending.

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

Bug#946599: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #946599 in glibc 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/glibc-team/glibc/commit/04373a4e6df6b3c61fa4bbf78f8409aadc7d2753


debian/debhelper.in/libc.preinst: fallback to text output in case perl debconf 
is used and perl is not usable.  Closes: #946599, 950389.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/946599

Processed: forcibly merging 950389 946599

[Debian Bug Tracking System]

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

> forcemerge 950389 946599
Bug #950389 [libc6] libc6 s390x preinstall script fails
Bug #946599 [libc6] libcrypt1: failure to switch from libc6 to libcrypt1 hoses 
the whole system
Severity set to 'grave' from 'important'
Marked as found in versions glibc/2.29-9.
Merged 946599 950389
> thanks
Stopping processing here.

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

Processed (with 1 error): merging 950389 946599

[Debian Bug Tracking System]

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

> merge 950389 946599
Bug #950389 [libc6] libc6 s390x preinstall script fails
Unable to merge bugs because:
severity of #946599 is 'important' not 'grave'
Failed to merge 950389: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#892558: marked as done (ruby-rspec-puppet FTBFS with Ruby 2.5)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 18:50:59 +
with message-id 
and subject line Bug#892558: fixed in ruby-rspec-puppet 2.7.8-1
has caused the Debian Bug report #892558,
regarding ruby-rspec-puppet FTBFS with Ruby 2.5
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.)


-- 
892558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec-puppet
Version: 2.6.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rspec-puppet.html

...
Failures:

  1) trusted_facts without node set should contain 
Notify[certname-my_node.my_node]
 Failure/Error: it { should contain_notify("certname-my_node.my_node") }
   expected that the catalogue would contain 
Notify[certname-my_node.my_node]
 # ./spec/classes/trusted_facts_spec.rb:7:in `block (3 levels) in '

  2) trusted_facts without node set should contain Notify[hostname-my_node]
 Failure/Error: it { should contain_notify("hostname-my_node") }
   expected that the catalogue would contain Notify[hostname-my_node]
 # ./spec/classes/trusted_facts_spec.rb:9:in `block (3 levels) in '

  3) regsubst 
 Failure/Error: facts.each { |k, v| Facter.add(k) { setcode { v } } }

 RuntimeError:
   fact "clientversion" already has the maximum number of resolutions 
allowed (100).
 # ./lib/rspec-puppet/support.rb:363:in `add'
 # ./lib/rspec-puppet/support.rb:363:in `block in stub_facts!'
 # ./lib/rspec-puppet/support.rb:363:in `each'
 # ./lib/rspec-puppet/support.rb:363:in `stub_facts!'
 # ./lib/rspec-puppet/example/function_example_group.rb:152:in 
`build_compiler'
 # ./lib/rspec-puppet/example/function_example_group.rb:128:in `compiler'
 # ./lib/rspec-puppet/example/function_example_group.rb:87:in `block in 
find_function'
 # ./lib/rspec-puppet/support.rb:318:in `with_vardir'
 # ./lib/rspec-puppet/example/function_example_group.rb:83:in 
`find_function'
 # ./lib/rspec-puppet/example/function_example_group.rb:79:in `subject'
 # ./spec/functions/regsubst_spec.rb:6:in `block (2 levels) in '

  4) regsubst 
 Failure/Error: facts.each { |k, v| Facter.add(k) { setcode { v } } }

 RuntimeError:
   fact "clientversion" already has the maximum number of resolutions 
allowed (100).
 # ./lib/rspec-puppet/support.rb:363:in `add'
 # ./lib/rspec-puppet/support.rb:363:in `block in stub_facts!'
 # ./lib/rspec-puppet/support.rb:363:in `each'
 # ./lib/rspec-puppet/support.rb:363:in `stub_facts!'
 # ./lib/rspec-puppet/example/function_example_group.rb:152:in 
`build_compiler'
 # ./lib/rspec-puppet/example/function_example_group.rb:128:in `compiler'
 # ./lib/rspec-puppet/example/function_example_group.rb:87:in `block in 
find_function'
 # ./lib/rspec-puppet/support.rb:318:in `with_vardir'
 # ./lib/rspec-puppet/example/function_example_group.rb:83:in 
`find_function'
 # ./lib/rspec-puppet/example/function_example_group.rb:79:in `subject'
 # ./spec/functions/regsubst_spec.rb:7:in `block (2 levels) in '

  5) regsubst 
 Failure/Error: facts.each { |k, v| Facter.add(k) { setcode { v } } }

 RuntimeError:
   fact "clientversion" already has the maximum number of resolutions 
allowed (100).
 # ./lib/rspec-puppet/support.rb:363:in `add'
 # ./lib/rspec-puppet/support.rb:363:in `block in stub_facts!'
 # ./lib/rspec-puppet/support.rb:363:in `each'
 # ./lib/rspec-puppet/support.rb:363:in `stub_facts!'
 # ./lib/rspec-puppet/example/function_example_group.rb:152:in 
`build_compiler'
 # ./lib/rspec-puppet/example/function_example_group.rb:128:in `compiler'
 # ./lib/rspec-puppet/example/function_example_group.rb:87:in `block in 
find_function'
 # ./lib/rspec-puppet/support.rb:318:in `with_vardir'
 # ./lib/rspec-puppet/example/function_example_group.rb:83:in 
`find_function'
 # ./lib/rspec-puppet/example/function_example_group.rb:79:in `subject'
 # ./spec/functions/regsubst_spec.rb:8:in `block (2 levels) in '

  6) split 
 Failure/Error: facts.each { |k, v| Facter.add(k) { setcode { v } } }

 RuntimeError:
   fact "clientversion" already has the maximum number of resolutions 
allowed (100).
 # ./lib/rspec-puppet/support.rb:363:in `add'
 # ./lib/rspec-puppet/support.rb:363:in `block in stub_facts!'
 # ./lib/rspec-puppet/support.rb:363:in `each'
 # ./lib/rspec-puppet/support.rb:363:in `stub_facts!'
 # ./lib/rspec-puppet/example/function_example_group.rb:152:in 
`build_compiler'
 

Processed: severity of 893735 is important

[Debian Bug Tracking System]

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

> severity 893735 important
Bug #893735 [src:paraview] paraview FTBFS on armel/armhf: 
QVTKOpenGLWidget.cxx:458:3: error: 'QOpenGLFunctions_3_2_Core' was not declared 
in this scope
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#950688: boost1.71: python autopkgtest fails

[Felix Geyer]

Source: boost1.71
Version: 1.71.0-5
Severity: serious

The boost1.71 python autopkgtest fails with cmake >= 3.16 because the python
include path isn't added correctly.

In debian/tests/srcs/python/CMakeLists.txt the variable Python_INCLUDE_DIR
is used but the correct variable is Python_INCLUDE_DIRS (S at the end).

I'm not quite sure why this worked before but Python_INCLUDE_DIR isn't part
of the documented FindPython interface. See:
https://cmake.org/cmake/help/v3.15/module/FindPython.html

Filing as serious since it blocks cmake migrating to testing.

Cheers,
Felix

Processed: Correct the version

[Debian Bug Tracking System]

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

> notfound 950677 211
Bug #950677 [src:pglogical-ticker] pglogical-ticker FTBFS with PostgreSQL 12
The source 'pglogical-ticker' and version '211' do not appear to match any 
binary packages
No longer marked as found in versions pglogical-ticker/211.
> found 950677 1.4.0-1
Bug #950677 [src:pglogical-ticker] pglogical-ticker FTBFS with PostgreSQL 12
Marked as found in versions pglogical-ticker/1.4.0-1.
> thanks
Stopping processing here.

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

Processed: block 950677 with 948942

[Debian Bug Tracking System]

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

> block 950677 with 948942
Bug #950677 [src:pglogical-ticker] pglogical-ticker FTBFS with PostgreSQL 12
950677 was not blocked by any bugs.
950677 was not blocking any bugs.
Added blocking bug(s) of 950677: 948942
> thanks
Stopping processing here.

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

Bug#892558: marked as pending in ruby-rspec-puppet

[Sebastien Badia]

Control: tag -1 pending

Hello,

Bug #892558 in ruby-rspec-puppet 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/ruby-team/ruby-rspec-puppet/commit/a9742a7d8a20969d8d303b357cb1a3d6bec3dbcd


d/patch: Xit upstream failing tests (Closes: #892558)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892558

Processed: Bug#892558 marked as pending in ruby-rspec-puppet

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892558 [src:ruby-rspec-puppet] ruby-rspec-puppet FTBFS with Ruby 2.5
Added tag(s) pending.

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

Bug#950677: pglogical-ticker FTBFS with PostgreSQL 12

[Finzel, Jeremy]

I cannot build pglogical-ticker for postgres 12 because it depends on
pglogical, which is still not available for postgres 12.

Thank you,

*Jeremy Finzel*

*Database Administrator Tech Lead*
*M* 630-777-4520





On Tue, Feb 4, 2020 at 11:15 AM Adrian Bunk  wrote:

> Source: pglogical-ticker
> Version: 211
> Severity: serious
> Tags: ftbfs
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tests.reproducible-2Dbuilds.org_debian_rb-2Dpkg_unstable_amd64_pglogical-2Dticker.html&d=DwICAg&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=DqdWOTTF4YJBUfeNWvxJoag6GeBeW-A_9xfI4JO4szc&m=x4wGvjAj1rScjqBLt-vwkfu821jGVk14Ul8MqyIZlVQ&s=gNMPJbS_Jb8Xu6AyyaFXWf-zn5Z2yTYsv23jpkn6Vsc&e=
>
> ...
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control  2019-09-12 03:21:00.0 -1200
> +++ debian/control.2ofOpA   2020-01-30 11:15:37.578761355 -1200
> @@ -7,9 +7,8 @@
>  Homepage:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_enova_pglogical-5Fticker&d=DwICAg&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=DqdWOTTF4YJBUfeNWvxJoag6GeBeW-A_9xfI4JO4szc&m=x4wGvjAj1rScjqBLt-vwkfu821jGVk14Ul8MqyIZlVQ&s=e8XUYIKf_iLYzoM4ooF8TOKqtteGqEg_HU7wfxKDtNY&e=
>  Vcs-Git:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_enova_pglogical-5Fticker.git&d=DwICAg&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=DqdWOTTF4YJBUfeNWvxJoag6GeBeW-A_9xfI4JO4szc&m=x4wGvjAj1rScjqBLt-vwkfu821jGVk14Ul8MqyIZlVQ&s=mzcbMwtYHmyhaU2Wl-Iwm43pW5IVU_WlJsGmb99_QjI&e=
>
> -Package: postgresql-11-pglogical-ticker
> +Package: postgresql-12-pglogical-ticker
>  Architecture: any
> -Depends: postgresql-11, postgresql-11-pglogical, ${shlibs:Depends},
> ${misc:Depends}
> +Depends: postgresql-12, postgresql-12-pglogical, ${shlibs:Depends},
> ${misc:Depends}
>  Description: Have time-based replication delay for pglogical
> - A pglogical extension to get time-based replication delay for PostgreSQL
> 11.
> -
> + A pglogical extension to get time-based replication delay for PostgreSQL
> 12.
> Error: debian/control needs updating from debian/control.in. Run
> 'pg_buildext updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
>

Bug#885267: coccinelle: Depends on unmaintained pygtk

[eamanu]

Source: coccinelle
Version: 1.0.4.deb-3

Hi everybody,

This issue was forward to upstream [1].

The dependency will be remove from coccinelle soon

[1] https://systeme.lip6.fr/pipermail/cocci/2020-February/006836.html

Cheers,
eamanu

Bug#949981: marked as done (budgie-extras: Build-Depends on pep8 which has been removed)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 18:04:20 +
with message-id 
and subject line Bug#949981: fixed in budgie-extras 0.92.0-2
has caused the Debian Bug report #949981,
regarding budgie-extras: Build-Depends on pep8 which has been removed
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.)


-- 
949981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: budgie-extras
Version: 0.9.1-1
Severity: serious
Tags: ftbfs sid bullseye
Control: fixed -1 0.91.0-1

budgie-extras Build-Depends on the pep8 transitional package, which has
already been removed (see #940736). This makes budgie-extras unbuildable
in unstable. Please build-depend on pycodestyle instead, and if necessary
update any build scripts that run the 'pep8' executable so they run
'pycodestyle' instead.

The version in experimental appears to have fixed this already.

smcv
--- End Message ---
--- Begin Message ---
Source: budgie-extras
Source-Version: 0.92.0-2

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

Debian distribution maintenance software
pp.
David Mohammed  (supplier of updated budgie-extras 
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, 04 Feb 2020 17:42:43 +
Source: budgie-extras
Binary: budgie-app-launcher-applet budgie-applications-menu-applet 
budgie-brightness-controller-applet budgie-clockworks-applet 
budgie-countdown-applet budgie-dropby-applet budgie-extras-common 
budgie-extras-daemon budgie-fuzzyclock-applet budgie-hotcorners-applet 
budgie-kangaroo-applet budgie-keyboard-autoswitch-applet 
budgie-network-manager-applet budgie-previews budgie-previews-applet 
budgie-quickchar budgie-quicknote-applet budgie-recentlyused-applet 
budgie-rotation-lock-applet budgie-showtime-applet budgie-takeabreak-applet 
budgie-trash-applet budgie-visualspace-applet budgie-wallstreet 
budgie-weathershow-applet budgie-window-mover-applet budgie-window-shuffler 
budgie-workspace-overview-applet budgie-workspace-stopwatch-applet 
budgie-workspace-wallpaper-applet
Architecture: source
Version: 0.92.0-2
Distribution: unstable
Urgency: medium
Maintainer: David Mohammed 
Changed-By: David Mohammed 
Description:
 budgie-app-launcher-applet - Applet to provide an alternative means to launch 
applications
 budgie-applications-menu-applet - Stylish Applications Menu for Budgie-Desktop
 budgie-brightness-controller-applet - Applet to control the brightness of the 
screen
 budgie-clockworks-applet - Applet to display clock across multiple time zones
 budgie-countdown-applet - Applet providing a countdown capability on the 
Budgie Desktop
 budgie-dropby-applet - Applet to popup when a USB device is connected
 budgie-extras-common - Shared component of budgie-extras applets
 budgie-extras-daemon - Extras daemon for budgie-extras capabilities
 budgie-fuzzyclock-applet - Show the time in a fuzzy way
 budgie-hotcorners-applet - Applet providing hotcorners capabilities for the 
Budgie Desktop
 budgie-kangaroo-applet - Applet to allow quick file-browsing
 budgie-keyboard-autoswitch-applet - Applet adding the ability to set a 
different keyboard layout per
 budgie-network-manager-applet - Network Manager Applet for the budgie-desktop
 budgie-previews - Provides window previews capabilities for the Budgie Desktop
 budgie-previews-applet - transitional package
 budgie-quickchar - GUI to find and choose locale characters
 budgie-quicknote-applet - Applet providing simple notes capability for the 
Budgie Desktop
 budgie-recentlyused-applet - Applet displays files recently accessed for the 
Budgie Desktop
 budgie-rotation-lock-applet - Applet to lock or unlock the screen rotation
 budgie-showtime-applet - Applet displaying date and time on the Budgie Desktop
 budgie-takeabreak-applet - Applet to prompt when to take-a-break for a set 
period of time
 budgie-trash-applet - Applet allows access to trash capabilities for the 
Budgie Desktop
 budgie-visualspace-applet - Show and manage windows in worksp

Bug#950672: hy: diff for NMU version 0.17.0-1.1

[stefanor]

Hi Tianon (2020.02.04_17:18:33_+)
> I'm hoping to get 0.18.0 packaged soon, which (as you mentioned)
> should make this moot, but I don't see any harm in getting a fix in
> sooner (really, feel free to skip DELAYED entirely if you want to get
> this fixed faster).

Thanks, rescheduled to 0.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#950672: hy: diff for NMU version 0.17.0-1.1

[Tianon Gravi]

On Tue, 4 Feb 2020 at 08:57, Stefano Rivera  wrote:
> I've prepared an NMU for hy (versioned as 0.17.0-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Nice, I think this is perfectly reasonable, thanks!

I'm hoping to get 0.18.0 packaged soon, which (as you mentioned)
should make this moot, but I don't see any harm in getting a fix in
sooner (really, feel free to skip DELAYED entirely if you want to get
this fixed faster).

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#950594: marked as done (flang FTBFS: dwz: Too many DIEs, not optimizing)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 17:20:48 +
with message-id 
and subject line Bug#950594: fixed in flang 20190329-5
has caused the Debian Bug report #950594,
regarding flang FTBFS: dwz: Too many DIEs, not optimizing
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.)


-- 
950594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flang
Version: 20190329-4
Severity: serious
Tags: ftbfs

...
   dh_dwz -O--buildsystem=cmake 
-O--builddirectory=/tmp/flang-20190329/debian/build
install -d debian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu
dwz -mdebian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug -- 
debian/flang-7/usr/bin/flang-7 debian/flang-7/usr/bin/flang1 
debian/flang-7/usr/bin/flang2
dwz: debian/flang-7/usr/bin/flang-7: Too many DIEs, not optimizing
dwz: debian/flang-7/usr/bin/flang1: DWARF compression not beneficial - old size 
2259002 new size 2265054
dh_dwz: error: dwz 
-mdebian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.debug -- 
debian/flang-7/usr/bin/flang-7 debian/flang-7/usr/bin/flang1 
debian/flang-7/usr/bin/flang2 returned exit code 1
make: *** [debian/rules:14: binary] Error 25
--- End Message ---
--- Begin Message ---
Source: flang
Source-Version: 20190329-5

We believe that the bug you reported is fixed in the latest version of
flang, 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.
Alastair McKinstry  (supplier of updated flang 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: Tue, 04 Feb 2020 09:31:51 +
Source: flang
Architecture: source
Version: 20190329-5
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Alastair McKinstry 
Closes: 950594
Changes:
 flang (20190329-5) unstable; urgency=medium
 .
   * Override dh_dwz as it FTBFS. Closes: #950594
Checksums-Sha1:
 b184aa9d6bea757f9be2cc274e0b7e9bde1bca68 2151 flang_20190329-5.dsc
 ad5f90f5b27d3c179b3ddb0c2875235d831dd84a 15608 flang_20190329-5.debian.tar.xz
Checksums-Sha256:
 8c1d3a7bb3aa825a338d506d6e67e06e0678ab3e1af5baa15abae7509380a39f 2151 
flang_20190329-5.dsc
 a5013fcb28a5afd700adedac3855d780523b53a5dfa8d3afee27fa0a4273987c 15608 
flang_20190329-5.debian.tar.xz
Files:
 057f194e8187bd66bd0889e586033872 2151 devel optional flang_20190329-5.dsc
 2caf9d741c8d91a4d655a333d48a45a2 15608 devel optional 
flang_20190329-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl45pIEACgkQy+a7Tl2a
06U5jQ//em0W/VUdpRrwvyVhVOOW29PJ8N9ZmfaD3WsGhIz4HGtxOnqsrHEneXrM
zFz0Di51dT2TWRGs0KIkgMUmBlfkfAU6O1fvdo3rsUyyib43SCBR7lmyEN4NeW5F
xJY8ePuZ8T9y4Ar1bszbQlaKnoYLGxQ7sA8JDDic7BxIB+VGINXO+ihqCFlc/3a1
h9S3PLjFxoskxKPan0IIT2jUyu4eyM6u79z2hEyUXdmRajJSV5m6HaDrEyQd2x0p
oljAvHvrpfNMfMmVADfsQWN5pif4WuoofVHRFSuBsvYCrvaWQUvukxtzecK/tnFx
UdfsK7vvFigH/7gQfqzZAR5NB0qUYLplmS7ynmk3wqfM2Obph00Qz8mwWs2FZn+A
975Vt9QKHrnc7WmtI5t/O1YFYakYvPc9XNCmdAjseu4dhRNZEKb9Eqn1y1LMHIjd
SVsA2XyTgDwI8tyitMsJdi5S2iTr/GBpScxX+ngcg33iNWWdjv+/WvGNcbH9/4Mb
E2pP5Di3rsiMO/xZNsc6BNdPbIPyJL7K29gLnbSLuSzZr5z7vEdelT8jZu7T6BYr
nCAui8Q8x2pbkK+W1+qanIkS5Pw7+hvljtgt8sh+DVsER8cPb0vYHg3QQ63MKuzV
1knkjeaNZvvzo6MRGFt3nFSklmu/YQMAR5pPRQ3jkoPr/+8zWsc=
=b2WF
-END PGP SIGNATURE End Message ---

Bug#950677: pglogical-ticker FTBFS with PostgreSQL 12

[Adrian Bunk]

Source: pglogical-ticker
Version: 211
Severity: serious
Tags: ftbfs

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

...
 fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control  2019-09-12 03:21:00.0 -1200
+++ debian/control.2ofOpA   2020-01-30 11:15:37.578761355 -1200
@@ -7,9 +7,8 @@
 Homepage: https://github.com/enova/pglogical_ticker
 Vcs-Git: https://github.com/enova/pglogical_ticker.git
 
-Package: postgresql-11-pglogical-ticker
+Package: postgresql-12-pglogical-ticker
 Architecture: any
-Depends: postgresql-11, postgresql-11-pglogical, ${shlibs:Depends}, 
${misc:Depends}
+Depends: postgresql-12, postgresql-12-pglogical, ${shlibs:Depends}, 
${misc:Depends}
 Description: Have time-based replication delay for pglogical
- A pglogical extension to get time-based replication delay for PostgreSQL 11.
-
+ A pglogical extension to get time-based replication delay for PostgreSQL 12.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9: 
debian/control] Error 1

Bug#950676: s3ql: missing build dependency on dh-python

[Adrian Bunk]

Source: s3ql
Version: 3.3.2+dfsg-1
Severity: serious
Tags: ftbfs

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

...
 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc
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) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 11) line 
1.
BEGIN failed--compilation aborted at (eval 11) line 1.

make: *** [debian/rules:8: clean] Error 25

Bug#943423: libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental)

[Aurelien Jarno]

clone 943423 -1
reassign -1 doxygen
retitle -1 doxygen-latex is now useless, should be removed from the archive?
block 943423 by -1
thanks

On 2019-11-05 20:54, Aurelien Jarno wrote:
> tag 943423 + moreinfo
> 
> Hi,
> 
> On 2019-10-24 18:59, Paolo Greppi wrote:
> > Package: libccfits-doc
> > Version: 2.5+dfsg-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
> > 
> > It FTBFS with this error:
> > 
> > /usr/bin/make -C latex
> > make[2]: Entering directory '/<>/latex'
> > rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg 
> > *.bbl refman.pdf
> > pdflatex refman
> > This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) 
> > (preloaded format=pdflatex)
> >  restricted \write18 enabled.
> > entering extended mode
> > (./refman.tex
> > LaTeX2e <2018-12-01>
> > 
> > make[2]: *** [Makefile:8: refman.pdf] Error 1
> > make[2]: Leaving directory '/<>/latex'
> > make[1]: *** [debian/rules:15: override_dh_auto_build-indep] Error 2
> > make[1]: Leaving directory '/<>'
> > make: *** [debian/rules:6: build] Error 2
> > 
> > More details can be found in the file latex/refman.log at the end of the 
> > build.
> > I attach it.
> > 
> > This had been notified already for doxygen 1.8.15 but the bug was closed:
> > https://bugs.debian.org/921296
> 
> The bug was closed because it's not a bug of the ccfits package. The
> ccfits package doesn't do anything fancy, it uses doxygen to generate
> a latex file and runs pdflatex on it. doxygen should be fixed instead
> to generate valid latex output.

doxygen 1.8.16 has been uploaded to unstable, and doxygen-latex is still
unable to produce valid latex output. If doxygen-latex is not supported
by upstream anymore, maybe it's time to just drop it?

Aurelien

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

Processed: Re: Bug#943423: libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental)

[Debian Bug Tracking System]

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

> clone 943423 -1
Bug #943423 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)
Bug 943423 cloned as bug 950675
> reassign -1 doxygen
Bug #950675 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)
Bug reassigned from package 'src:ccfits' to 'doxygen'.
No longer marked as found in versions ccfits/2.5+dfsg-1.
Ignoring request to alter fixed versions of bug #950675 to the same values 
previously set
> retitle -1 doxygen-latex is now useless, should be removed from the archive?
Bug #950675 [doxygen] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)
Changed Bug title to 'doxygen-latex is now useless, should be removed from the 
archive?' from 'libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)'.
> block 943423 by -1
Bug #943423 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)
943423 was not blocked by any bugs.
943423 was not blocking any bugs.
Added blocking bug(s) of 943423: 950675
> thanks
Stopping processing here.

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

Processed: hy: diff for NMU version 0.17.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 950672 + pending
Bug #950672 [src:hy] FTBFS: Tests fail with Python 3.8
Added tag(s) pending.

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

Bug#950672: hy: diff for NMU version 0.17.0-1.1

[Stefano Rivera]

Control: tags 950672 + pending

Dear maintainer,

I've prepared an NMU for hy (versioned as 0.17.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

SR
diff -Nru hy-0.17.0/debian/changelog hy-0.17.0/debian/changelog
--- hy-0.17.0/debian/changelog	2019-08-19 18:21:26.0 -0700
+++ hy-0.17.0/debian/changelog	2020-02-04 08:40:08.0 -0800
@@ -1,3 +1,10 @@
+hy (0.17.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Support Python 3.8 (Closes: #950672)
+
+ -- Stefano Rivera   Tue, 04 Feb 2020 08:40:08 -0800
+
 hy (0.17.0-1) unstable; urgency=medium
 
   * Update to 0.17.0 upstream release (Closes: #913044, #892264, #913048)
diff -Nru hy-0.17.0/debian/patches/py38.patch hy-0.17.0/debian/patches/py38.patch
--- hy-0.17.0/debian/patches/py38.patch	1969-12-31 16:00:00.0 -0800
+++ hy-0.17.0/debian/patches/py38.patch	2020-02-04 08:40:08.0 -0800
@@ -0,0 +1,53 @@
+Description: Support posonlyargs in Python 3.8
+Author: Kodi Arfer 
+Author: Stefano Rivera 
+Origin: upstream, https://github.com/hylang/hy/commit/ba9b0239c7fa2a02478e8456ed3867c6f2fec0c5
+Origin: upstream, https://github.com/hylang/hy/commit/36708e8e996700da256943b3e8162a29fa381473
+Bug-Debian: https://bugs.debian.org/950672
+
+--- a/hy/compiler.py
 b/hy/compiler.py
+@@ -1145,7 +1145,7 @@
+ expr,
+ name=fname,
+ args=ast.arguments(
+-args=[], vararg=None, kwarg=None,
++args=[], vararg=None, kwarg=None, posonlyargs=[],
+ kwonlyargs=[], kw_defaults=[], defaults=[]),
+ body=f(parts).stmts,
+ decorator_list=[])
+@@ -1524,6 +1524,7 @@
+ args = ast.arguments(
+ args=main_args, defaults=defaults,
+ vararg=rest,
++posonlyargs=[],
+ kwonlyargs=kwonly, kw_defaults=kw_defaults,
+ kwarg=kwargs)
+ 
+--- a/hy/_compat.py
 b/hy/_compat.py
+@@ -37,10 +37,12 @@
+ finally:
+ traceback = None
+ 
+-code_obj_args = ['argcount', 'kwonlyargcount', 'nlocals', 'stacksize',
++code_obj_args = ['argcount', 'posonlyargcount', 'kwonlyargcount', 'nlocals', 'stacksize',
+  'flags', 'code', 'consts', 'names', 'varnames',
+  'filename', 'name', 'firstlineno', 'lnotab', 'freevars',
+  'cellvars']
++if not PY38:
++code_obj_args.remove("posonlyargcount")
+ else:
+ def raise_from(value, from_value=None):
+ raise value
+--- a/tests/native_tests/native_macros.hy
 b/tests/native_tests/native_macros.hy
+@@ -391,7 +391,7 @@
+   ;; Now, let's use a `require`d macro that depends on another macro defined only
+   ;; in this scope.
+   (defmacro local-test-macro [x]
+-(.format "This is the local version of `nonlocal-test-macro` returning {}!" x))
++(.format "This is the local version of `nonlocal-test-macro` returning {}!" (int x)))
+ 
+   (assert (= "This is the local version of `nonlocal-test-macro` returning 3!"
+  (test-module-macro-2 3)))
diff -Nru hy-0.17.0/debian/patches/series hy-0.17.0/debian/patches/series
--- hy-0.17.0/debian/patches/series	2019-08-16 15:57:27.0 -0700
+++ hy-0.17.0/debian/patches/series	2020-02-04 08:15:19.0 -0800
@@ -1 +1,2 @@
 hy-history.patch
+py38.patch

Processed: found 946289 in 1.8.4-1

[Debian Bug Tracking System]

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

> found 946289 1.8.4-1
Bug #946289 {Done: Arturo Borrero Gonzalez } [iptables] ufw: 
fails to start with iptables 1.8.4
Marked as found in versions iptables/1.8.4-1.
> thanks
Stopping processing here.

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

Processed: doxygen 1.8.16 is now in unstable

[Debian Bug Tracking System]

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

> reassign 943451 src:ppl 1:1.2-7
Bug #943451 [libppl-doc] libppl-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Bug reassigned from package 'libppl-doc' to 'src:ppl'.
No longer marked as found in versions ppl/1:1.2-7.
Ignoring request to alter fixed versions of bug #943451 to the same values 
previously set
Bug #943451 [src:ppl] libppl-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Marked as found in versions ppl/1:1.2-7.
> tags 943451 ftbfs bullseye sid
Bug #943451 [src:ppl] libppl-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Added tag(s) ftbfs, bullseye, and sid.
> severity 943451 serious
Bug #943451 [src:ppl] libppl-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Severity set to 'serious' from 'normal'
> reassign 943450 src:openms 2.4.0-real-1
Bug #943450 [openms-doc] openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Bug reassigned from package 'openms-doc' to 'src:openms'.
No longer marked as found in versions openms/2.4.0-real-1.
Ignoring request to alter fixed versions of bug #943450 to the same values 
previously set
Bug #943450 [src:openms] openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Marked as found in versions openms/2.4.0-real-1.
> tags 943450 ftbfs bullseye sid
Bug #943450 [src:openms] openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Added tag(s) ftbfs, sid, and bullseye.
> severity 943450 serious
Bug #943450 [src:openms] openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental
Severity set to 'serious' from 'normal'
> reassign 943423 src:ccfits 2.5+dfsg-1
Bug #943423 [libccfits-doc] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 
from experimental)
Bug reassigned from package 'libccfits-doc' to 'src:ccfits'.
No longer marked as found in versions ccfits/2.5+dfsg-1.
Ignoring request to alter fixed versions of bug #943423 to the same values 
previously set
Bug #943423 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)
Marked as found in versions ccfits/2.5+dfsg-1.
> tags 943423 ftbfs bullseye sid
Bug #943423 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)
Added tag(s) bullseye, sid, and ftbfs.
> severity 943423 serious
Bug #943423 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from 
experimental)
Severity set to 'serious' from 'normal'
> tags 921298 ftbfs bullseye sid
Bug #921298 [src:libstxxl] libstxxl: FTBFS with upcoming doxygen 1.8.15
Added tag(s) bullseye, sid, and ftbfs.
> severity 921298 serious
Bug #921298 [src:libstxxl] libstxxl: FTBFS with upcoming doxygen 1.8.15
Severity set to 'serious' from 'normal'
> tags 921297 ftbfs bullseye sid
Bug #921297 [src:qevercloud] qevercloud: FTBFS with upcoming doxygen 1.8.15
Added tag(s) ftbfs, sid, and bullseye.
> severity 921297 serious
Bug #921297 [src:qevercloud] qevercloud: FTBFS with upcoming doxygen 1.8.15
Severity set to 'serious' from 'normal'
> tags 921300 ftbfs bullseye sid
Bug #921300 [frobby] frobby: FTBFS with upcoming doxygen 1.8.15
Added tag(s) ftbfs, bullseye, and sid.
> severity 921300 serious
Bug #921300 [frobby] frobby: FTBFS with upcoming doxygen 1.8.15
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#950581: marked as done (python-django: CVE-2020-7471: Potential SQL injection via StringAgg(delimiter))

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 16:35:05 +
with message-id 
and subject line Bug#950581: fixed in python-django 2:2.2.10-1
has caused the Debian Bug report #950581,
regarding python-django: CVE-2020-7471: Potential SQL injection via 
StringAgg(delimiter)
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.)


-- 
950581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 2:2.2.9-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1:1.11.27-1~deb10u1

Hi,

The following vulnerability was published for python-django.

CVE-2020-7471[0]:
| Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3
| allows SQL Injection if untrusted data is used as a StringAgg
| delimiter (e.g., in Django applications that offer downloads of data
| as a series of rows with a user-specified column delimiter). By
| passing a suitably crafted delimiter to a
| contrib.postgres.aggregates.StringAgg instance, it was possible to
| break escaping and inject malicious SQL.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-7471
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7471
[1] https://www.djangoproject.com/weblog/2020/feb/03/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.2.10-1

We believe that the bug you reported is fixed in the latest version of
python-django, 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.
Chris Lamb  (supplier of updated python-django 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: Tue, 04 Feb 2020 17:19:01 +0100
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 2:2.2.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Closes: 950581
Changes:
 python-django (2:2.2.10-1) unstable; urgency=medium
 .
   * New upstream security release. (Closes: #950581)
 
   * Bump Standards-Version to 4.5.0.
Checksums-Sha1:
 254e06173d4dab9d1b58e0bfec92b7593e42a3ed 2777 python-django_2.2.10-1.dsc
 86b0f5160b52cc4330d17cd69090f7f240c9fb47 8865888 
python-django_2.2.10.orig.tar.gz
 f96689c16794a8945dcb7bdaf510d45c35d4f4ba 25904 
python-django_2.2.10-1.debian.tar.xz
 943cff2750967caea7830dd6bc2ff7b7940e0dbc 7619 
python-django_2.2.10-1_amd64.buildinfo
Checksums-Sha256:
 e96c6fe7c03379b3159566ab238674b00063b5ce1da9f52e45a7374da3dc81d6 2777 
python-django_2.2.10-1.dsc
 1226168be1b1c7efd0e66ee79b0e0b58b2caa7ed87717909cd8a57bb13a7079a 8865888 
python-django_2.2.10.orig.tar.gz
 1d5156001874ac0e5e5693a60e63bcf42afa5e53d9112221f2968e95563ed077 25904 
python-django_2.2.10-1.debian.tar.xz
 9417781fba2bf62da6dd16a819ef0c82f484b1fec92dc2e425f65c92040520b9 7619 
python-django_2.2.10-1_amd64.buildinfo
Files:
 01740bb921173edf589ad811a858ba3a 2777 python optional 
python-django_2.2.10-1.dsc
 10f192f8565ab137aea2dda4a4cb3d26 8865888 python optional 
python-django_2.2.10.orig.tar.gz
 902d39d823258522f7b02700507583f6 25904 python optional 
python-django_2.2.10-1.debian.tar.xz
 295bb6a33d9cf2592e0ba0aa77ed8a54 7619 python optional 
python-django_2.2.10-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl45mv0ACgkQHpU+J9Qx
HlimbRAAnJJJukZjcayg417PaGOib9dA8Fvzun7fEMlJ1Zk+sGq45kGwQIOqHTa1
MYNIhs94jM/7Ttprrmc/U5zRb4K2ICv4oWD5uj29D9V15VmspJhAUglf3m5sk5Sh
ydCV2HWhlnQ/+pptR+qemb7Zk6A/U12yWZkVgYX1sM4bKrKVkLmteCAT2QZrkkBJ
kQET5eIK30PzOMQfICmgL48LTse9IodBDv7kdpUDyDR7WYkpKQdhb12GrMc5eGNO
qRLdm+12+vbKgTbJ1cKE5w5V2Ql4gLa8FaxhwrmA71C+jZA1+exL/fCD0TyqbzQF
RjkKrbB6ZyVA/b9jh4aULjO+lXfcwYFLINFnYEt4kEMiGXoKeKw3vNRpF/VbZgpz
EYC2vVfc/gO8iG0GnYydddS8Aq+Wyx

Bug#950581: marked as pending in python-django

[Chris Lamb]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-django/commit/5eca46bbe33eb6f08e9798166e217fbe4534e97a


New upstream security release. (Closes: #950581)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950581

Processed: Bug#950581 marked as pending in python-django

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950581 [src:python-django] python-django: CVE-2020-7471: Potential SQL 
injection via StringAgg(delimiter)
Added tag(s) pending.

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

Bug#950660: marked as done (python-pyproj FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 16:20:15 +
with message-id 
and subject line Bug#950660: fixed in python-pyproj 2.4.2+ds-3
has caused the Debian Bug report #950660,
regarding python-pyproj FTBFS: test failures
to be marked as done.

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

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


-- 
950660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyproj
Version: 2.4.2+ds-2
Severity: serious
Tags: ftbfs

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

...
=== FAILURES ===
__ test_datum __

aoi_data_directory = None

def test_datum(aoi_data_directory):
p1 = Proj(proj="latlong", datum="WGS84")
s_1 = -111.5
s_2 = 45.2591944
p2 = Proj(proj="utm", zone=10, datum="NAD27")
x2, y2 = transform(p1, p2, s_1, s_2)
>   assert_almost_equal((x2, y2), (1402291.0833290431, 5076289.591846835))
E   AssertionError: 
E   Arrays are not almost equal to 7 decimals
E   
E   Mismatch: 100%
E   Max absolute difference: 5.10040385
E   Max relative difference: 3.63719338e-06
Ex: array([1402285.9829252, 5076292.4212746])
Ey: array([1402291.083329 , 5076289.5918468])

test/test_datum.py:12: AssertionError
 test_doctests _

aoi_data_directory = None

def test_doctests(aoi_data_directory):
"""run the examples in the docstrings using the doctest module"""

with warnings.catch_warnings():
warnings.filterwarnings(
"ignore",
"You will likely lose important projection information when",
UserWarning,
)

failure_count_proj, test_count = doctest.testmod(pyproj.proj, 
verbose=True)
failure_count_crs, test_count_crs = doctest.testmod(pyproj.crs, 
verbose=True)
failure_count_geod, test_count_geod = doctest.testmod(pyproj.geod, 
verbose=True)
failure_count_transform, test_count_transform = doctest.testmod(
pyproj.transformer, verbose=True
)

failure_count = (
failure_count_proj
+ failure_count_crs
+ failure_count_geod
+ failure_count_transform
)
# Missing shapely wheels for Windows, non x86_64 platforms, and python 
3.8
expected_failure_count = 0
try:
import shapely  # noqa
except ImportError:
if (
os.name == "nt"
or platform.uname()[4] != "x86_64"
or (sys.version_info.major, sys.version_info.minor) >= (3, 8)
):
expected_failure_count = 6

# if the below line fails, doctests have failed
>   assert (
failure_count == expected_failure_count
), "{0} of the doctests in " "lib/pyproj/__init__.py 
failed".format(failure_count)
E   AssertionError: 3 of the doctests in lib/pyproj/__init__.py failed
E   assert 3 == 0
E -3
E +0

test/test_doctest_wrapper.py:50: AssertionError
...
 test_transform__out_of_bounds _

def test_transform__out_of_bounds():
with pytest.warns(FutureWarning):
transformer = Transformer.from_proj("+init=epsg:4326", 
"+init=epsg:27700")
if LooseVersion(proj_version_str) >= LooseVersion("6.3.0"):
with pytest.raises(ProjError):
>   transformer.transform(10, 10, errcheck=True)
E   Failed: DID NOT RAISE 

test/test_transformer.py:266: Failed
_ test_transformer__operations__scope_remarks __

def test_transformer__operations__scope_remarks():
transformer = Transformer.from_crs(28356, 7856)
assert transformer.scope is None
assert [op.scope for op in transformer.operations] == [
None,
"Conformal transformation of GDA94 coordinates that have been 
derived through "
"GNSS CORS.",
None,
]
>   assert [op.remarks for op in transformer.operations] == [
None,
"Scale difference in ppb where 1/billion = 1E-9. Derivation 
excluded Cocos, "
"Christmas and Macquarie Islands but is applied there. See codes 
8444-46 for "
"equivalents using NTv2 method. See code 844

Processed: retitle 950662 to pybel FTBFS: test failures

[Debian Bug Tracking System]

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

> retitle 950662 pybel FTBFS: test failures
Bug #950662 {Done: Adrian Bunk } [src:pybel] pybel FTBFS; test 
failures
Changed Bug title to 'pybel FTBFS: test failures' from 'pybel FTBFS; test 
failures'.
> thanks
Stopping processing here.

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

Processed: tagging 950662

[Debian Bug Tracking System]

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

> tags 950662 + ftbfs
Bug #950662 {Done: Adrian Bunk } [src:pybel] pybel FTBFS: test 
failures
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#950666: node-terser FTBFS: test failures

[Adrian Bunk]

Source: node-terser
Version: 4.1.2-4
Severity: serious
Tags: ftbfs

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

...
  231 passing (47s)
  4 pending
  7 failing

  1) bin/uglifyjs (2)
   Should dump AST as JSON:
 Uncaught Command failed: "/usr/bin/node" bin/uglifyjs 
test/input/global_defs/simple.js -mco ast
ERROR: ENOENT: no such file or directory, open 'ast'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at read_file (/build/1st/node-terser-4.1.2/bin/uglifyjs:353:19)
at /build/1st/node-terser-4.1.2/bin/uglifyjs:176:37
at Array.forEach ()
at Object. (/build/1st/node-terser-4.1.2/bin/uglifyjs:175:28)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)

  Error: Command failed: "/usr/bin/node" bin/uglifyjs 
test/input/global_defs/simple.js -mco ast
  ERROR: ENOENT: no such file or directory, open 'ast'
  at Object.openSync (fs.js:443:3)
  at Object.readFileSync (fs.js:343:35)
  at read_file (bin/uglifyjs:353:19)
  at /build/1st/node-terser-4.1.2/bin/uglifyjs:176:37
  at Array.forEach ()
  at Object. (bin/uglifyjs:175:28)
  at Module._compile (internal/modules/cjs/loader.js:778:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
  at Module.load (internal/modules/cjs/loader.js:653:32)
  at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
  
  at ChildProcess.exithandler (child_process.js:294:12)
  at maybeClose (internal/child_process.js:982:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
...

Bug#950101: marked as done (python-xarray-doc: FTBFS with new ipython)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 15:20:58 +
with message-id 
and subject line Bug#950101: fixed in python-xarray 0.15.0-1
has caused the Debian Bug report #950101,
regarding python-xarray-doc: FTBFS with new ipython
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.)


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

Package: python-xarray-doc
Version: 0.14.1-2
Severity: serious
Control: tags -1 patch

ipython_directive examples are executed at build time.  xarray has some 
examples that fail without optional dependencies Debian doesn't have 
(e.g. h5netcdf) and/or downloaded data.  This used to put the error 
message in the documentation (non-ideal but I prefer it to no 
documentation), but in ipython_directive 7, it defaults to failing the 
whole documentation build.


Fix: this can be turned off by adding

ipython_warning_is_error = False

anywhere in the top level of doc/conf.py.
--- End Message ---
--- Begin Message ---
Source: python-xarray
Source-Version: 0.15.0-1

We believe that the bug you reported is fixed in the latest version of
python-xarray, 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.
Alastair McKinstry  (supplier of updated python-xarray 
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: Tue, 04 Feb 2020 14:22:30 +
Source: python-xarray
Binary: python-xarray-doc python3-xarray
Architecture: source all
Version: 0.15.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Description:
 python-xarray-doc - documentation for xarray
 python3-xarray - N-D labeled arrays and datasets in Python 3
Closes: 950101
Changes:
 python-xarray (0.15.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Patches cftime_xfail.patch, 0c73a38_Fix_CRS.patch, xfail-dask.patch
 no longer needed.
   * Add patch to disable failures with new ipython. Closes:  #950101
   * Patch no-installer.patch: Don't try to pip install anything
   * Depend on python3-nbsphinx, python3-cfgrib, pandoc,python3-numpydoc
Checksums-Sha1:
 cfc8fe67aa15e30732ea9c76a1e0e68165bb2601 3122 python-xarray_0.15.0-1.dsc
 b52a4dba159e2eb046d68007397dbd69a06d3392 1686796 
python-xarray_0.15.0.orig.tar.xz
 dec0e409f70f1ab75f3a070e2d3c2edacdaa4fab 15452 
python-xarray_0.15.0-1.debian.tar.xz
 11c38cea95e0ce0e82289142c790d8fcd8db45d5 5094376 
python-xarray-doc_0.15.0-1_all.deb
 8e8344f623cd9afd29059d8fc234f34ab1fa83fb 14970 
python-xarray_0.15.0-1_amd64.buildinfo
 799fb669939b867f411d70a80d0868a9e19c840b 28932 python3-xarray_0.15.0-1_all.deb
Checksums-Sha256:
 2636d8873989334ab7521cd86e108cd2fead7d565aa4be9f02c6835125e82bc7 3122 
python-xarray_0.15.0-1.dsc
 5910a8d63acbe979b50258d0bc908ce3dc3c07fbb39ebe98b08393c12f1cf68f 1686796 
python-xarray_0.15.0.orig.tar.xz
 4dfb1bd70bf127bfdddec74d0d2848a90f9309d50c192c0cd5a661c75d93b700 15452 
python-xarray_0.15.0-1.debian.tar.xz
 e0d499897d0b9c9cbd227d578310948d2a6765212d11d0d64562033584243da2 5094376 
python-xarray-doc_0.15.0-1_all.deb
 29867fab0af5d7447cdde72a233da8e4b37ae8fad8d93d8ba282375eb9961c85 14970 
python-xarray_0.15.0-1_amd64.buildinfo
 675be50d7fa6245d0efd8976e11f6410052db494b43c2cb56d3d74fb8a6153bc 28932 
python3-xarray_0.15.0-1_all.deb
Files:
 929b39871a5c713c0c04380f0d8c9175 3122 python optional 
python-xarray_0.15.0-1.dsc
 ca1b375d23f31feaecb89e55655384ff 1686796 python optional 
python-xarray_0.15.0.orig.tar.xz
 f299dc92bdd80435c13396343554cc51 15452 python optional 
python-xarray_0.15.0-1.debian.tar.xz
 e4efe7928fa730b86e2dd998457246d8 5094376 doc optional 
python-xarray-doc_0.15.0-1_all.deb
 dc27f18d08012b32831b49356f9b9532 14970 python optional 
python-xarray_0.15.0-1_amd64.buildinfo
 a28955801569ddfd616ee8c65fc3286e 28932 python optional 
python3-xarray_0.15.0-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl45h44ACgkQy+a7Tl2a
06WeLQ/+Nw0yZEbpOWtKWSSfaQIo7fBRPi44s38z0hCkmu5ID40qmiNEj2xP7n8z
ow5F2owDGrAgfSFPo7M1YUVYu6d5ZPaQSK8lsLEhQQQmo9M4WC6b

Bug#950663: empy FTBFS with more than one supported python3 version

[Adrian Bunk]

Source: empy
Version: 3.3.2-3
Severity: serious
Tags: ftbfs

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

...
install -m 755 
/build/1st/empy-3.3.2/debian/python-empy/usr/lib/python2.*/dist-packages/em.py 
/build/1st/empy-3.3.2/debian/python-empy/usr/bin/empy
install -m 755 
/build/1st/empy-3.3.2/debian/python3-empy/usr/lib/python3.*/dist-packages/em.py 
/build/1st/empy-3.3.2/debian/python3-empy/usr/bin/empy3
install: target '/build/1st/empy-3.3.2/debian/python3-empy/usr/bin/empy3' is 
not a directory
make[1]: *** [debian/rules:19: override_dh_auto_install] Error 1

Bug#950579: marked as done (libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: cannot find -lgcc_s)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 15:19:36 +
with message-id 
and subject line Bug#950579: fixed in gcc-10 10-20200204-1
has caused the Debian Bug report #950579,
regarding libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: cannot find 
-lgcc_s
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.)


-- 
950579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcc1
Version: 1:10-20200202-1
Severity: serious
Justification: FTBFS
Tags: ftbfs
Control: affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex

https://buildd.debian.org/status/fetch.php?pkg=glib2.0&arch=s390x&ver=2.62.4-2&stamp=1580755175&file=log

> Package versions:
[with linebreaks added for legibility, quoting only the most
libgcc-adjacent packages]
> gcc_4:9.2.1-3.1
> gcc-10-base_10-20200202-1
> gcc-9_9.2.1-25
> gcc-9-base_9.2.1-25
> libgcc-9-dev_9.2.1-25
> libgcc-s1_10-20200202-1
> libgcc1_1:10-20200202-1
...
> Sanity check compiler command line: cc
> /<>/debian/build/deb/meson-private/sanitycheckc.c
> -o /<>/debian/build/deb/meson-private/sanitycheckc.exe
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-z,defs
> -Wl,--no-as-needed -Wl,-O1
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> /usr/bin/ld: cannot find -lgcc_s
> collect2: error: ld returned 1 exit status
> 
> -
> 
> meson.build:1:0: ERROR: Compiler cc can not compile programs.

Presumably the dependencies and Breaks should be such that it isn't
possible to get into a situation where libgcc_s can't be linked.

Recent builds of xterm, hdrmerge and esorex show similar symptoms.

smcv
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10-20200204-1

We believe that the bug you reported is fixed in the latest version of
gcc-10, 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.
Matthias Klose  (supplier of updated gcc-10 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: Tue, 04 Feb 2020 15:52:16 +0100
Source: gcc-10
Architecture: source
Version: 10-20200204-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 950550 950579
Changes:
 gcc-10 (10-20200204-1) unstable; urgency=medium
 .
   * GCC snapshot, taken from the trunk (20200202, 0303907ea5d).
   * On architectures where libgcc_s.so is a symlink, replace the symlink with
 a simple linker script.
   * Add breaks on libgcc-N-dev packages on arm64, s390x and sparc64.
 Closes: #950550, #950579.
Checksums-Sha1:
 a75b91ef2226b43fa9176ab985fba129496f9563 27973 gcc-10_10-20200204-1.dsc
 ad3e2e6a339a4fabc846ce4f19916e3b2493661b 75638679 
gcc-10_10-20200204.orig.tar.gz
 0f81b5a1baf938c6b19e32eaaf26a4be2fc619f9 558312 
gcc-10_10-20200204-1.debian.tar.xz
 3aea62227599e4be2477d47ab219b0932a640651 10660 
gcc-10_10-20200204-1_source.buildinfo
Checksums-Sha256:
 4a0fb0d79f9719dd9c11bc55b82bcd1f79285f006956778d14b3c51b664effe8 27973 
gcc-10_10-20200204-1.dsc
 36ce3690146c4ea9c10167065547f3614f34719e04b7806efdfdb9c326d40927 75638679 
gcc-10_10-20200204.orig.tar.gz
 e9d0a7332bfeafc4bf47cfe09717f648a0a8d2a1a33e6e6df27fee1af8770e9f 558312 
gcc-10_10-20200204-1.debian.tar.xz
 833ebdcd6d1aa91c652ae1442cb59fdaf18553d04b501d9e4c267a0ce5de36f7 10660 
gcc-10_10-20200204-1_source.buildinfo
Files:
 bb5a752fc1ba600bed87402e8b35a579 27973 devel optional gcc-10_10-20200204-1.dsc
 8db631f2c45690b48080d6c883494789 75638679 devel optional 
gcc-10_10-20200204.orig.tar.gz
 98397672bb8cc360ec239eb9e85770da 558312 devel optional 
gcc-10_10-20200204-1.debian.tar.xz
 b7e9cc78b6071a48a9026844a0681685 10660 devel optional 
gcc-10_10-20200204-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl45iKwQHGRva29AZGVi
aWFuLm9yZw

Bug#950662: pybel FTBFS; test failures

[Adrian Bunk]

Source: pybel
Version: 0.12.1-1
Severity: serious
Tags: ftbgs bullseye sid
Control: close -1 0.13.1-1

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

...
==
FAIL: test_gmod_unabbreviated 
(tests.test_parse.test_parse_bel_variants.TestGeneModification)
--
Traceback (most recent call last):
  File 
"/build/1st/pybel-0.12.1/.pybuild/cpython3_3.8_pybel/build/tests/test_parse/test_parse_bel_variants.py",
 line 224, in test_gmod_unabbreviated
self.assertEqual(self.expected, result.asDict())
AssertionError: {'kind': 'gmod', 'identifier': {'namespace': 'bel', 'name': 
'Me'}} != {'kind': 'gmod', 'identifier': [{'namespace': 'bel', 'name': 'Me'}]}

--
Ran 657 tests in 110.810s

FAILED (failures=10, errors=8, skipped=1)
(, 2)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd 
/build/1st/pybel-0.12.1/.pybuild/cpython3_3.8_pybel/build; python3.8 -m 
unittest discover -v 
dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned 
exit code 13
make: *** [debian/rules:7: build] Error 25


This is already fixed in the version in experimental.

Processed: pybel FTBFS; test failures

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.13.1-1
Bug #950662 [src:pybel] pybel FTBFS; test failures
Marked as fixed in versions pybel/0.13.1-1.
Bug #950662 [src:pybel] pybel FTBFS; test failures
Marked Bug as done

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

Bug#950660: python-pyproj FTBFS: test failures

[Adrian Bunk]

Source: python-pyproj
Version: 2.4.2+ds-2
Severity: serious
Tags: ftbfs

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

...
=== FAILURES ===
__ test_datum __

aoi_data_directory = None

def test_datum(aoi_data_directory):
p1 = Proj(proj="latlong", datum="WGS84")
s_1 = -111.5
s_2 = 45.2591944
p2 = Proj(proj="utm", zone=10, datum="NAD27")
x2, y2 = transform(p1, p2, s_1, s_2)
>   assert_almost_equal((x2, y2), (1402291.0833290431, 5076289.591846835))
E   AssertionError: 
E   Arrays are not almost equal to 7 decimals
E   
E   Mismatch: 100%
E   Max absolute difference: 5.10040385
E   Max relative difference: 3.63719338e-06
Ex: array([1402285.9829252, 5076292.4212746])
Ey: array([1402291.083329 , 5076289.5918468])

test/test_datum.py:12: AssertionError
 test_doctests _

aoi_data_directory = None

def test_doctests(aoi_data_directory):
"""run the examples in the docstrings using the doctest module"""

with warnings.catch_warnings():
warnings.filterwarnings(
"ignore",
"You will likely lose important projection information when",
UserWarning,
)

failure_count_proj, test_count = doctest.testmod(pyproj.proj, 
verbose=True)
failure_count_crs, test_count_crs = doctest.testmod(pyproj.crs, 
verbose=True)
failure_count_geod, test_count_geod = doctest.testmod(pyproj.geod, 
verbose=True)
failure_count_transform, test_count_transform = doctest.testmod(
pyproj.transformer, verbose=True
)

failure_count = (
failure_count_proj
+ failure_count_crs
+ failure_count_geod
+ failure_count_transform
)
# Missing shapely wheels for Windows, non x86_64 platforms, and python 
3.8
expected_failure_count = 0
try:
import shapely  # noqa
except ImportError:
if (
os.name == "nt"
or platform.uname()[4] != "x86_64"
or (sys.version_info.major, sys.version_info.minor) >= (3, 8)
):
expected_failure_count = 6

# if the below line fails, doctests have failed
>   assert (
failure_count == expected_failure_count
), "{0} of the doctests in " "lib/pyproj/__init__.py 
failed".format(failure_count)
E   AssertionError: 3 of the doctests in lib/pyproj/__init__.py failed
E   assert 3 == 0
E -3
E +0

test/test_doctest_wrapper.py:50: AssertionError
...
 test_transform__out_of_bounds _

def test_transform__out_of_bounds():
with pytest.warns(FutureWarning):
transformer = Transformer.from_proj("+init=epsg:4326", 
"+init=epsg:27700")
if LooseVersion(proj_version_str) >= LooseVersion("6.3.0"):
with pytest.raises(ProjError):
>   transformer.transform(10, 10, errcheck=True)
E   Failed: DID NOT RAISE 

test/test_transformer.py:266: Failed
_ test_transformer__operations__scope_remarks __

def test_transformer__operations__scope_remarks():
transformer = Transformer.from_crs(28356, 7856)
assert transformer.scope is None
assert [op.scope for op in transformer.operations] == [
None,
"Conformal transformation of GDA94 coordinates that have been 
derived through "
"GNSS CORS.",
None,
]
>   assert [op.remarks for op in transformer.operations] == [
None,
"Scale difference in ppb where 1/billion = 1E-9. Derivation 
excluded Cocos, "
"Christmas and Macquarie Islands but is applied there. See codes 
8444-46 for "
"equivalents using NTv2 method. See code 8447 for alternative 
including "
"distortion model for Aus only.",
None,
]
E   AssertionError: assert [None, 'Scale... only.', None] == [None, 'Scale 
... only.', None]
E At index 1 diff: 'Scale difference in ppb where 1/billion = 1E-9. See 
CT codes 8444-46 for NTv2 method giving equivalent results for Christmas 
Island, Cocos Islands and Australia respectively. See CT code 8447 for 
alternative including distortion model for Australia only.' != 'Scale 
difference in ppb where 1/billion = 1E-9. Derivation excluded Cocos, Christmas 
and Macquarie Islands but is applied there. See codes 8444-46 for equivalents 
using NTv2 method. See code 8447 for alternative including distortion model for 
Aus only.'
E Full diff:
E [None,
E -  'Scal

Bug#950661: pytest-bdd FTBFS with Python 3.8 as supported version

[Adrian Bunk]

Source: pytest-bdd
Version: 3.1.1-1
Severity: serious
Tags: ftbfs

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

...
dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest"
I: pybuild base:217: python3.8 -m pytest
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 193, in _run_module_as_main
return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 86, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/pytest.py", line 102, in 
raise SystemExit(pytest.main())
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 63, in 
main
config = _prepareconfig(args, plugins)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 206, 
in _prepareconfig
return pluginmanager.hook.pytest_cmdline_parse(
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286, in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92, in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83, in 
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 203, in 
_multicall
gen.send(outcome)
  File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line 94, in 
pytest_cmdline_parse
config = outcome.get_result()
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in 
get_result
raise ex[1].with_traceback(ex[2])
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in 
_multicall
res = hook_impl.function(*args)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 739, 
in pytest_cmdline_parse
self.parse(args)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 947, 
in parse
self._preparse(args, addopts=addopts)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 893, 
in _preparse
self.pluginmanager.load_setuptools_entrypoints("pytest11")
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 297, in 
load_setuptools_entrypoints
plugin = ep.load()
  File "/usr/lib/python3.8/importlib/metadata.py", line 76, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1014, in _gcd_import
  File "", line 991, in _find_and_load
  File "", line 975, in _find_and_load_unlocked
  File "", line 655, in _load_unlocked
  File "", line 618, in _load_backward_compatible
  File "/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py", line 304, 
in load_module
exec(co, mod.__dict__)
  File "/build/1st/pytest-bdd-3.1.1/pytest_bdd/plugin.py", line 27, in 
def trace():
  File "/build/1st/pytest-bdd-3.1.1/pytest_bdd/steps.py", line 188, in decorator
contribute_to_module(
  File "/build/1st/pytest-bdd-3.1.1/pytest_bdd/steps.py", line 261, in 
contribute_to_module
func = recreate_function(func, module=module)
  File "/build/1st/pytest-bdd-3.1.1/pytest_bdd/steps.py", line 245, in 
recreate_function
set_code(func, CodeType(*args))
TypeError: an integer is required (got type bytes)
E: pybuild pybuild:341: test: plugin custom failed with: exit code=1: python3.8 
-m pytest
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 
3.7" --system=custom "--test-args={interpreter} -m pytest" returned exit code 13
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 25

Bug#950628: marked as done (cryptsetup-initramfs: can't unlock argon2 keyslots: incompatible with libgcc1 1:10-20200202-1)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 15:04:29 +
with message-id 
and subject line Bug#950628: fixed in cryptsetup 2:2.2.2-3
has caused the Debian Bug report #950628,
regarding cryptsetup-initramfs: can't unlock argon2 keyslots: incompatible with 
libgcc1 1:10-20200202-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.)


-- 
950628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup-initramfs
Version: 2:2.2.2-2
Severity: critical

The side effect of initramfs logic used to find libgcc leads to
unbootable system if libgcc is in different location than libc. Maybe
something like "ldconfig -p | grep libgcc_s.so.1" should be used to
locate libgcc instead?

Details:

The recent update of libgcc1 to version 1:10-20200202-1 (unstable) moved
it from:
/lib/x86_64-linux-gnu/libgcc_s.so.1
to:
/lib/libgcc_s.so.1

The initramfs hook for cryptsetup is still looking for it using previous
location based on libc:

# cat /usr/share/initramfs-tools/hooks/cryptroot
[...]
LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')"
find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read
so; do
copy_exec "$so"
done

# echo $(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')
/lib/x86_64-linux-gnu

# ldd /sbin/cryptsetup
[...]
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4b0b6c)

This leads to omission of libgcc_s.so.1 in initramfs and makes unlocking
the root drive impossible (in case of LUKS2 at least) because of the
following error:
libgcc_s.so.1 must be installed for pthread_cancel to work

I created initramfs hook in /etc/ that includes libgcc and it solves the
problem (obviously as workaround):
cp /lib/libgcc_s.so.1 "${DESTDIR}/usr/lib/"

The difference in libgcc1 packages:
(version 1:10-20200202-1)
# dpkg -L libgcc1
/.
/lib
/lib/libgcc_s.so.1
/lib/x86_64-linux-gnu
/usr
/usr/share
/usr/share/doc
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libgcc1
/usr/share/doc/libgcc1

(version 1:9.2.1-25)
# dpkg -L libgcc1
/.
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/libgcc_s.so.1
/usr
/usr/share
/usr/share/doc
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libgcc1
/usr/share/doc/libgcc1


Thanks,
Karol
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.2.2-3

We believe that the bug you reported is fixed in the latest version of
cryptsetup, 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.
Guilhem Moulin  (supplier of updated cryptsetup 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, 04 Feb 2020 14:11:12 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.2.2-3
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team 

Changed-By: Guilhem Moulin 
Closes: 939766 950628
Changes:
 cryptsetup (2:2.2.2-3) unstable; urgency=high
 .
   * initramfs hook: Workaround fix for the libgcc_s's source location.
 (Closes: #950628, #939766.)  See #950254 for the proper fix.
Checksums-Sha1:
 6bd7a7e6ba24d977ac565cf74a2f3f4449193e06 2853 cryptsetup_2.2.2-3.dsc
 e7725801be13e865dece73f159a51b0da43f5df9 112644 
cryptsetup_2.2.2-3.debian.tar.xz
 e1fdc125342a250480383be6a3770192c9aa0bd9 9583 
cryptsetup_2.2.2-3_amd64.buildinfo
Checksums-Sha256:
 8c7b444bfc4ae0af1276eb7518925cde8646136297ea92f964e877f6dc7dfa04 2853 
cryptsetup_2.2.2-3.dsc
 56295914d8d03a4d3a35b53cb8396234b0fc0ec83705afa112e6789d3e8c26ca 112644 
cryptsetup_2.2.2-3.debian.tar.xz
 3849f212716aeb9b39bbb16c9a9852553a0bd9e6dea390701f8ef0279e483f32 9583 
cryptsetup_2.2.2-3_amd64.buildinfo
Files:
 bb05b359202e996ab652e7afc7283a3f 2853 admin optional cryptsetup_2.2.2-3.dsc
 ef62099e3d2ac07cf768f8d5a317eaf3 112644 admin optional 
cryptsetup_2.2.2-3.debian.tar.xz
 362ea373ae35913a0c2aa6cc8c22e4f7 9583 admin optional 
cryptsetup_2.2.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJ

Bug#950659: python-deeptoolsintervals FTBFS with more than one supported python3 version

[Adrian Bunk]

Source: python-deeptoolsintervals
Version: 0.1.9-1
Severity: serious
Tags: ftbfs

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

...
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/build/1st/python-deeptoolsintervals-0.1.9=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -I/usr/include/python3.8 -c 
deeptoolsintervals/tree/tree.c -o 
build/temp.linux-amd64-3.8/deeptoolsintervals/tree/tree.o
deeptoolsintervals/tree/tree.c:1:10: fatal error: Python.h: No such file or 
directory
1 | #include 
  |  ^~
compilation terminated.


The build dependency on python3-dev should be corrected to python3-all-dev.

Bug#950422: marked as done (node-sinon: (build-)depends on node-array-from which has been requested to be removed)

[Debian Bug Tracking System]

Your message dated Tue, 4 Feb 2020 15:51:52 +0100
with message-id 
and subject line node-sinon requires node-array-from
has caused the Debian Bug report #950422,
regarding node-sinon: (build-)depends on node-array-from which has been 
requested to be removed
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.)


-- 
950422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-sinon
Version: 8.1.0+ds-1
Severity: serious
Control: block 945308 with -1

Hi,

node-command-join has been requested to be removed (#945308), but
node-sinon still (build-)depends on it.

Please find a solution.


Andreas
--- End Message ---
--- Begin Message ---
node-sinon requires node-array-from, then ROM-RM node-array-from is no
more appropriate.

Cheers,
Xavier--- End Message ---

Processed: notfound 950540 in 1.9.8-2

[Debian Bug Tracking System]

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

> notfound 950540 1.9.8-2
Bug #950540 [haveged] System hangs at startup
No longer marked as found in versions haveged/1.9.8-2.
> thanks
Stopping processing here.

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

Processed: found 950540 in 1.9.8-3

[Debian Bug Tracking System]

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

> found 950540 1.9.8-3
Bug #950540 [haveged] System hangs at startup
Marked as found in versions haveged/1.9.8-3.
> thanks
Stopping processing here.

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

Bug#950657: marked as done (node-eslint-plugin-flowtype: needed files not built)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 14:43:18 +
with message-id 
and subject line Bug#950657: fixed in node-eslint-plugin-flowtype 2.25.0-2
has caused the Debian Bug report #950657,
regarding node-eslint-plugin-flowtype: needed files not built
to be marked as done.

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

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


-- 
950657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-eslint-plugin-flowtype
Version: 2.25.0-1
Severity: serious

Package is unusable since files are not built during build
--- End Message ---
--- Begin Message ---
Source: node-eslint-plugin-flowtype
Source-Version: 2.25.0-2

We believe that the bug you reported is fixed in the latest version of
node-eslint-plugin-flowtype, 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.
Xavier Guimard  (supplier of updated 
node-eslint-plugin-flowtype 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, 04 Feb 2020 15:14:26 +0100
Source: node-eslint-plugin-flowtype
Architecture: source
Version: 2.25.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 950657
Changes:
 node-eslint-plugin-flowtype (2.25.0-2) unstable; urgency=medium
 .
   * Team upload
   * Bump debhelper compatibility level to 12
   * Declare compliance with policy 4.5.0
   * Add "Rules-Requires-Root: no"
   * Change section to javascript
   * Add debian/gbp.conf
   * Add upstream/metadata
   * Update VCS fields to salsa
   * Build missing files using babel (Closes: #950657)
   * Use pkg-js-tools auto install
Checksums-Sha1: 
 86a3694d3e4ea8fac366fed5bf64adbcdf275f8e 2323 
node-eslint-plugin-flowtype_2.25.0-2.dsc
 20b0de7d4b67e5ccf07261b0ce3b5e330ddd61ac 2676 
node-eslint-plugin-flowtype_2.25.0-2.debian.tar.xz
Checksums-Sha256: 
 34f1d8631235020ae087e5c4246965a620a7655f0feb4a9e9da34cbdf984e94e 2323 
node-eslint-plugin-flowtype_2.25.0-2.dsc
 58f7e9929bbbdc8a991afb0a0f0808846008f28b70306dc5eab6c699c0b3bd96 2676 
node-eslint-plugin-flowtype_2.25.0-2.debian.tar.xz
Files: 
 420fca360f91dd86f87fd8903bc76162 2323 javascript optional 
node-eslint-plugin-flowtype_2.25.0-2.dsc
 b9f0b3a3161ca9070398064d45a38557 2676 javascript optional 
node-eslint-plugin-flowtype_2.25.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl45fScACgkQ9tdMp8mZ
7umLog/+MsKMinGH93Bk6c4Z8TULim4FEP/b2iDRZ426ZUMjf/sHYWpjI+mrFUEx
F9v25Az2Nf5ko/2sR+qm+peTPHqwy2p20yhCaaouVzbrTC09sk7icaeuzoxxK7tP
y373PhDjWZjqK0jjW5QQSj5VavLqNJY5fGO0GZIJXQE7hTfjB9nxQbnpiq90O9dz
2UwN1T3sXdUn+xEX0DLDrsvKUwe3oPG86djw41CHkenMwoa8KuLnxqTxyYN4CIeP
GIo2t+Db8kxXsN2+fBxGArWpG4mrEhvJe411zl9TYQ1Uz0Hgb/qbYZ+flwlVP6vl
m30JVdytRKewlsUB1vef1zlAKp0qeGt4EaKL3qEC12DPfpWHpxnkSVbynKpeUEGD
iLAKZv2slfsK2u3tQWLBc7kUHVmkRFA4yQUX9PaGhZ1v0HgNcNdKa4dhnODQfSwE
qvgRqTkxOIK6HIN25U4FhBBN3yoPlG41/JKVa4pfRu+aZ2/l8Pzkjohs+MEOsdwr
gJ5ImMIcHLrsJ4vpjX9y0wyIymUU5PZdWulLkstlE8v2T361D8EtqsWMLKR1gMaK
HOVyZR+0ki8rSFd+io+x1Y6z2RuigSWsXLgLp6RV+yHOqNVbesMbMUM9gBfxXl6V
s8ZuED/WfHF8QOPz7Ny/6EnEyqLK/Szzq4n8wdZvDHM9/2yBws4=
=BUlk
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 14:41:47 +
with message-id 
and subject line Bug#947563: fixed in glob2 0.9.4.4-3
has caused the Debian Bug report #947563,
regarding FTBFS with scons 3.1.2-1
to be marked as done.

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

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


-- 
947563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glob2
Version: 0.9.4.4-2.5
Severity: important
Usertags: scons_ftbfs


Hello, 

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

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

Please check it and fix the error.

CU
Jörg

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

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

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


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

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


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

dpkg-checkbuilddeps: error: Unmet build dependencies: libsdl1.2-dev (>= 1.2.0) 
libsdl-image1.2-dev (>= 1.2.0) libsdl-net1.2-dev (>= 1.2.0) libsdl-ttf2.0-dev 
libvorbis-dev libspeex-dev libboost-dev libboost-thread-dev libboost-system-dev 
libboost-date-time-dev portaudio19-dev libboost-math-dev bsdiff sharutils
W: Unmet build-dependency in source
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null pop -a -R || test $? = 2
No patch removed
rm -rf .pc debian/stamp-patched
dh_testdir
dh_testroot
rm -f build-stamp 
dh_clean
dh_clean: Compatibility levels before 9 are deprecated (level 6 in use)
scons --portaudio=true -c
scons: Reading SConscript files ...
NameError: global name 'Options' is not defined:
  File "/data/entwicklung/linux/debian/trans_scons/glob2-0.9.4.4/SConstruct", 
line 321:
main()
  File "/data/entwicklung/linux/debian/trans_scons/glob2-0.9.4.4/SConstruct", 
line 239:
establish_options(env)
  File "/data/entwicklung/linux/debian/trans_scons/glob2-0.9.4.4/SConstruct", 
line 16:
opts = Options('options_cache.py')
make: *** [debian/rules:46: clean] Error 2


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: glob2
Source-Version: 0.9.4.4-3

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated glob2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 14:42:49 +0100
Source: glob2
Architecture: source
Version: 0.9.4.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Reiner Herrmann 
Closes: 947563
Changes:
 glob2 (0.9.4.4-3) unstable; urgency=medium
 .
   * QA upload.
   * Orphan package. (see: #845283)
   * Fix build with Python3-enabled scons. (Closes: #947563)
   * Convert to source format 3.0 (quilt).
   * Convert to dh-style build.
   * Update to debhelper compat 12.
   * Update Standards-Version to 4.5.0:
 - drop menu file
 - declare that d/rules does not require root
   * Drop ancient version restrictions.
   * Drop unneeded d/*.dirs and README.source.
   * Mark glob2-data as Multi-Arch: foreign.
   * Build with all hardening options.
   * Remove trailing whitespace from d/changelog.
Checksums-Sha1:
 12fc0ee4caf5b64382e026802c8ce0929bae5f93 2073 glob2_0.9.4.4-3.dsc
 880e7ea2d7a9f2333543db67db4fc592a641478e 25588 glob2_0.9.4.4-3.debian.tar.xz
 6a11220b4e472b8ded688c5aea8145616d7e775a 11462 glob2_0.9.4.4-3_amd64.buildinfo
Checksums-Sha256:
 f1bcd41ed25ebb98815bba4c53f780717d16e86f471b69b9faadb15f9fb99a17 2073 
glob2_0.9.4.4-3.dsc
 5ab9236006b8f87dc2723a392261fb7d2bf40c06ea32ac48e73153e26a0aeff3 25588 
glob2_0.9.4.4-3.debian.tar.xz
 e784b2e568e211722b8a84ae422a6baf3009602debbabb84e1f4

Bug#787350: marked as done ([RC][cc-by-nc-sa] Please clarify license of a few svg files)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 14:41:25 +
with message-id 
and subject line Bug#787350: fixed in fontmatrix 0.6.1+git20190730-2
has caused the Debian Bug report #787350,
regarding [RC][cc-by-nc-sa] Please clarify license of a few svg files
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.)


-- 
787350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fontmatrix
Severity: serious
version: 0.6.0+svn20110930-1.1
user: lintian-ma...@debian.org
usertags: license-problem-cc-by-nc-sa

Hi,

Could you please clarify the license of:
src/icons/application-fontmatrix-vectors.svg
src/icons/application-fontmatrix-systray-vectors.svg
src/graphic-resources/about-vectors.svg
claimed on source to be cc-by-nc-sa, thus non free.

If it is really a non free image please purge these files.

If it is a false positive please override like in 
http://sources.debian.net/src/freecad/0.14.3702%2Bdfsg-3/debian/source/lintian-overrides/
and add a changelog entry and a full explanation on debian/copyright. You may 
ask upstream to remove this cc-by-sa-nc tag on the svg file

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: fontmatrix
Source-Version: 0.6.1+git20190730-2

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated fontmatrix 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, 04 Feb 2020 13:14:47 +0100
Source: fontmatrix
Architecture: source
Version: 0.6.1+git20190730-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Gürkan Myczko 
Closes: 607148 787350 820140
Changes:
 fontmatrix (0.6.1+git20190730-2) unstable; urgency=medium
 .
   * Add Vcs fields.
   * Bump standards version to 4.5.0.
   * d/README.source. (Closes: #787350)
   * d/control: drop Oleksandr Moskalenko. (Closes: #820140)
   * Upstream fixed FTBFS. (Closes: #607148)
Checksums-Sha1:
 0279060aec74cb244b6a31386c83bed84f56005c 2184 
fontmatrix_0.6.1+git20190730-2.dsc
 3930fb4cb7e9bef08c567015624b214988262ee2 6180 
fontmatrix_0.6.1+git20190730-2.debian.tar.xz
 6d3a0dd2cd6461b3839d28605897b15f014c03d7 11510 
fontmatrix_0.6.1+git20190730-2_source.buildinfo
Checksums-Sha256:
 327977ebef64ca2d13ed3b834da90555bbdd560187eadedfed1d0f2caefbc45c 2184 
fontmatrix_0.6.1+git20190730-2.dsc
 0ba239b7f6a5a1a4f1b54b9465737652684cbffa3c34025812bcc354f61617fa 6180 
fontmatrix_0.6.1+git20190730-2.debian.tar.xz
 48895ab3e8905672f64759c3ec0c2fd66bb77c47fb6bafa01a674f6dd10ea2fc 11510 
fontmatrix_0.6.1+git20190730-2_source.buildinfo
Files:
 cbafae4bea2c0d59df44bcb24c7bc5d5 2184 graphics optional 
fontmatrix_0.6.1+git20190730-2.dsc
 b1a91fd2913baf899b0ab48e3d82e2af 6180 graphics optional 
fontmatrix_0.6.1+git20190730-2.debian.tar.xz
 5283df76e466ad3453aef1f7747156e2 11510 graphics optional 
fontmatrix_0.6.1+git20190730-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl45dwUACgkQweDZLphv
fH5E8A/9ESQFwL3XLr9Ht/POSu0K2IqP7xLOkr7mdrES5j+28tufjXfCAaxLKUp6
EbpVLOmLYvRlX4nb0Tyk2kugSATI/NSxi1K/HXXaMHbcDPIG6NvjCquckuVdN5NY
pWPWBRYxN//1UViPNZevOE/+HqwYjG+zr6PmxlEJxy6iuIg9kHTIooP2sINKiPtg
uISRhjoHTlK311l1Sd0I1iO2JrkxIQv4+888iPvPIoOGTl8eKhKWQ7OcyyPCupYj
lLVBlFutT9yN+qZSrbyWPKH31MpU9aJnE8Ns+lsV5mQ5SgvSdTPiEmrwbGYCMEjc
6zU4DvAGCxSof6KbH61vfmYfplXYHbitSNcV0bhrPrPhTUzRV/cBc3zMj4gXt3sF
gZd/dKIgyXwv0qthoemoSsaR73stNc52h8aWVrs2E9aSDqnIEkKuC0IAF+HlbbHk
MmcZrg3HNAxiCBvUV9yZl9ZCkFVCWFIbalEY2hr2aW1Tk9cP1N9Fq/tpy89oCKTc
BxYeIAZl4jJt19DgW/1hTviW6RvNrxBz689IS6SNVPxmN5NL2rRr+UQklePCj5kc
8fZJ7UtiKWeFD5IzfA1XhPXRCjs5aH0gBjVMIu6SafgiVRI69Xt5kZUyYfyaS62F
KU5Z9F2PuIETZvBBUXfUJDS6UKanV4LQEspBgfI4zCWTThoatoE=
=hCqZ
-END PGP SIGNATURE End Message ---

Bug#950339: marked as done (src:powder: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 14:43:56 +
with message-id 
and subject line Bug#950339: fixed in powder 118+dfsg1-3
has caused the Debian Bug report #950339,
regarding src:powder: invalid maintainer address
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.)


-- 
950339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
X-Debbugs-Cc: kilob...@angband.pl, Gürkan Myczko 
Source: powder
Source-Version: 118+dfsg1-2
Severity: serious

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 
>   pkg-games-de...@lists.debian.org
> host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]
> SMTP error from remote mail server after RCPT 
> TO::
> 550 5.1.1 :
> Recipient address rejected: User unknown in virtual alias table

Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;pkg-games-devel@lists.debian.org
Status: 5.0.0
Remote-MTA: dns; bendel.debian.org
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table

--- End Message ---
--- Begin Message ---
Source: powder
Source-Version: 118+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
powder, 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.
Gürkan Myczko  (supplier of updated powder 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, 04 Feb 2020 14:47:50 +0100
Source: powder
Architecture: source
Version: 118+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Gürkan Myczko 
Closes: 950339
Changes:
 powder (118+dfsg1-3) unstable; urgency=medium
 .
   * Fix maintainer address. (Closes: #950339)
   * Bump standards version to 4.5.0.
Checksums-Sha1:
 fbf42f0b0865a5672b05c948777bb07257c41565 1943 powder_118+dfsg1-3.dsc
 a8c91faca060b09f00c3918c635c2c3217d1f074 5756 powder_118+dfsg1-3.debian.tar.xz
 cabdaca6fc2b77b9bcf30c4654a08466993f0dc4 8803 
powder_118+dfsg1-3_source.buildinfo
Checksums-Sha256:
 72eaa963db56ac6676a98dedd782b0600d431148648342a1a5a821f76c6da1af 1943 
powder_118+dfsg1-3.dsc
 4303bc9f3fdb1083e445cfebcbf2734df37132857489c93f52c93289593ff28d 5756 
powder_118+dfsg1-3.debian.tar.xz
 1f59e2338b433a08cc1f42ee5cbb68c014342d6dd3d9008860fa43adc22cf8e6 8803 
powder_118+dfsg1-3_source.buildinfo
Files:
 96450e7f1b6ff1626a88c1b0f263bc2e 1943 non-free/games optional 
powder_118+dfsg1-3.dsc
 cd89bb0bcd07c496e9c5fccab1e18ca6 5756 non-free/games optional 
powder_118+dfsg1-3.debian.tar.xz
 f74e68f8b0b67a744ffbf953d57c886a 8803 non-free/games optional 
powder_118+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl45eSQACgkQweDZLphv
fH7eag//ecfhOk3jbR4Big8Q2W+aw5ILZuKyOf8DMxrMsV9u32tDZpZlXbPi67do
lXa1Y4hnQKZzVLlemmwuv58ERKwDgNduH0aMQRs77SABYR9FqStQb4dXCt0/0/kd
FCQH+peOTCXF4xme9w08GntBYvVhXgcYMWv8D3QoDopPUvEPhrqqmFUK7Si4+RnV
EExYpgmW8InZJsgDhufRG6id0GYazt29hbde82R4EMDxisidarm6IxceLz9myTrt
tU1uS+x0WBegu5566qXm3eixaTlyM//odKldrnj0Sw5otanADWcbF9GxDvp2msNa
e3w6Yh2DVZ7oJzYBNxyEknPa+yjzj/6n61HvFDj0Xlm3SAlj5hP4Cd1swFsD1uWW
1slYDjHI6dDHS7m9h7LYCdg6z8NGEQ4nAD0p51kT+aYskXva44ZhXDFD33VaKz5d
HeDVw4a6ZKVnvfzAIjQZ5pwGR32oJANHlXKp45TrQK0ecXO2M3bigmJaUKdfGo7S
+xoBmhI/nZf7Nq2wlasMtZCeHsjZWRXjTBF4zoxu4azWJZsfJhAo54sYimiU9m4E
inlLKccX88KqVLDIpAkikrlLlX2GaIXDKQYtjjmdUsnDfuLnVrWD5U9kKYmfbH90
ZyOozsQ+2I8zJDsdKLWYEVg/b3NoH442kAm3pDG5CJinj9gDOyk=
=7qgd
-END PGP SIGNATURE End Message ---

Bug#948418: marked as done (pyrit ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 14:44:03 +
with message-id 
and subject line Bug#948418: fixed in pyrit 0.5.1+git20180801-2
has caused the Debian Bug report #948418,
regarding pyrit ftbfs in unstable
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.)


-- 
948418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyrit
Version: 0.5.1+git20180801-1
Severity: serious
Tags: sid bullseye

[...]
==
ERROR: testEval (__main__.DatabaseTestCase)
--
Traceback (most recent call last):
  File "test_pyrit.py", line 306, in testEval
self.cli.eval_results(storage)
  File
"/<>/pyrit-0.5.1+git20180801/.pybuild/cpython2_2.7/build/pyrit_cli.py",
line 342, in eval_results
pwcount, essid_results = storage.getStats()
  File
"/<>/pyrit-0.5.1+git20180801/.pybuild/cpython2_2.7/build/cpyrit/storage.py",
line 965, in getStats
q = q.outerjoin(PYR2_DBObject).outerjoin(PAW2_DBObject)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2292, in
outerjoin
from_joinpoint=from_joinpoint,
  File "", line 2, in _join
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/base.py", line 220, in
generate
fn(self, *args[1:], **kw)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2447, in
_join
left, right, onclause, prop, create_aliases, outerjoin, full
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2470, in
_join_left_to_right
) = self._join_determine_implicit_left_side(left, right, onclause)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2603, in
_join_determine_implicit_left_side
"Can't determine which FROM clause to join "
InvalidRequestError: Can't determine which FROM clause to join from, there are
multiple FROMS which can join to this entity. Try adding an explicit ON clause
to help resolve the ambiguity.

--
Ran 15 tests in 43.711s

FAILED (errors=1)
Testing with filesystem-storage...
Testing with database-storage...
E: pybuild pybuild:341: test: plugin custom failed with: exit code=1: cd
/<>/pyrit-0.5.1+git20180801/test/ && python2.7 test_pyrit.py
--- End Message ---
--- Begin Message ---
Source: pyrit
Source-Version: 0.5.1+git20180801-2

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

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

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated pyrit 
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, 04 Feb 2020 14:40:46 +0100
Source: pyrit
Architecture: source
Version: 0.5.1+git20180801-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Raphaël Hertzog 
Closes: 948418
Changes:
 pyrit (0.5.1+git20180801-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Samuel Henrique ]
   * Add salsa-ci.yml
 .
   [ Raphaël Hertzog ]
   * Fix FTBFS by being explicit on fields to use for a join (Closes: #948418)
   * Replace last use of $ADTTMP by $AUTOPKGTEST_TMP (in a comment only)
Checksums-Sha1:
 845bba0e69ae188829b588781fb74afbd85aaf85 1871 pyrit_0.5.1+git20180801-2.dsc
 42d68cde4c4f4e115c2ba39b6d2137efb16a3499 14592 
pyrit_0.5.1+git20180801-2.debian.tar.xz
 da27e90f1f198f6258c0ec3cd67b6c9db444be95 7143 
pyrit_0.5.1+git20180801-2_source.buildinfo
Checksums-Sha256:
 4a25d85974b155d3c552aaac60a3a0fb7fcf21b095b34a929de2edafffc93764 1871 
pyrit_0.5.1+git20180801-2.dsc
 ca7d5c97617182402d8cf44e262ea04764b9a1eabbec3ec29da47467e7e418ed 14592 
pyrit_0.5.1+git20180801-2.debian.tar.xz
 28f66f6a86e490798e140f60fe23716567b35840d7f21f643d9387f3e3db1243 7143 
pyrit_0.5.1+git20180801-2_source.buildinfo
Files:
 bda8a5df6e6d59514ff1019a6170b3b7 1871 net optional 
pyrit_0.5.1+git20180801-2.dsc
 c5d316bfb139a00ef08e0f1cad4e511b 14592 net optional 
pyrit_0.5.1+git20180801-2.debian.tar.xz
 50f55ac0f8a759c06e73f

Processed: retitle 950628 to cryptsetup-initramfs: can't unlock argon2 keyslots: incompatible with libgcc1 1:10-20200202-1

[Debian Bug Tracking System]

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

> retitle 950628 cryptsetup-initramfs: can't unlock argon2 keyslots: 
> incompatible with libgcc1 1:10-20200202-1
Bug #950628 [cryptsetup-initramfs] System with encrypted root unbootable 
because initramfs hooks don't include libgcc located in /lib
Changed Bug title to 'cryptsetup-initramfs: can't unlock argon2 keyslots: 
incompatible with libgcc1 1:10-20200202-1' from 'System with encrypted root 
unbootable because initramfs hooks don't include libgcc located in /lib'.
> thanks
Stopping processing here.

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

Bug#950657: node-eslint-plugin-flowtype: needed files not built

[Xavier Guimard]

Package: node-eslint-plugin-flowtype
Version: 2.25.0-1
Severity: serious

Package is unusable since files are not built during build

Bug#950568: node-copy-webpack-plugin FTBFS: test failures

[Xavier Guimard]

Package: node-copy-webpack-plugin
Version: 4.3.0-6
Followup-For: Bug #950568

This package depends on webpack-log which is not packaged.

Bug#950654: FTBFS: node-eslint-plugin-html seems unusable without eslint

[Xavier Guimard]

Package: node-eslint-plugin-html
Version: 3.2.1-1
Severity: serious

This package seems unusable without eslint. See
https://ci.debian.net/data/autopkgtest/unstable/amd64/n/node-eslint-plugin-html/3801441/log.gz

Bug#948418: marked as pending in pyrit

[Raphaël Hertzog]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pkg-security-team/pyrit/commit/be704dc56b9e2736d967cc402ce0257664de0e37


Fix FTBFS by trying to help the join

Closes: #948418


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/948418

Processed: Bug#948418 marked as pending in pyrit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #948418 [src:pyrit] pyrit ftbfs in unstable
Added tag(s) pending.

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

Processed: ITP: gcc64 -- compiler host64 and target 32 with multilib

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 950542 950545 950547 950549 950550
Bug #950652 [wnpp] ITP: gcc64 -- compiler host64 and target 32 with multilib
950652 was not blocked by any bugs.
950652 was not blocking any bugs.
Added blocking bug(s) of 950652: 950550, 950549, 950542, 950547, and 950545

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

Bug#950644: gnome-books: Should depend on tracker-extract

[Manolo Díaz]

Package: gnome-books
Version: 3.31.90-3
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

Trying to launch gnome-books from Xfce desktop it fails with

(org.gnome.Books:18574): GLib-GIO-ERROR **: 13:57:13.838: Settings schema 
'org.freedesktop.Tracker.Miner.Files' is not installed

Installing tracker-extract fixes the problem.

Best Regards,
Manolo Díaz


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

Kernel: Linux 5.5.1+ (SMP w/8 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-books depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-evince-3.03.30.2-3
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-gepub-0.6 0.6.0-2
ii  gir1.2-gnomedesktop-3.0  3.30.2.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-pango-1.0 1.42.4-7~deb10u1
ii  gir1.2-tracker-2.0   2.1.8-2
ii  gir1.2-webkit2-4.0   2.26.3-1~deb10u1
ii  gjs  1.54.3-1
ii  gnome-online-miners  3.30.0-2
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libevdocument3-4 3.30.2-3
ii  libevview3-3 3.30.2-3
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgnome-desktop-3-173.30.2.1-2
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-7~deb10u1
ii  libpangocairo-1.0-0  1.42.4-7~deb10u1
ii  tracker  2.1.8-2

Versions of packages gnome-books recommends:
pn  gir1.2-lokdocview-0.1  
pn  gnome-user-docs
pn  libgsf-bin 
pn  unoconv

gnome-books suggests no packages.

-- no debconf information

Processed: retitle 937525 to RM: pyro -- removal triggered by the Python2 removal

[Debian Bug Tracking System]

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

> # fix title
> retitle 937525 RM: pyro -- removal triggered by the Python2 removal
Bug #937525 [ftp.debian.org] RM: PKG -- removal triggered by the Python2 removal
Changed Bug title to 'RM: pyro -- removal triggered by the Python2 removal' 
from 'RM: PKG -- removal triggered by the Python2 removal'.
> thanks
Stopping processing here.

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

Bug#950639: pymupdf FTBFS with mupdf 1.15

[Adrian Bunk]

Source: pymupdf
Version: 1.14.16-1
Severity: serious
Tags: ftbfs

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

...
fitz/fitz_wrap.c:4630:28: error: ‘FZ_ERROR_TRYLATER’ undeclared (first use in 
this function); did you mean ‘FZ_ERROR_SYNTAX’?
...

Bug#937525: Please remove pyro

[Alastair McKinstry]

Hi,

As the 'pyro' maintainer, it should be removed from debian/unstable.

Its only rdep is 'cylc', and the latest version of cylc (unstable) does 
not use pyro; pyro is already removed from testing.


(cylc is awaiting a full new release that will be python3 clean, that 
version (due now) will not use pyro.


pyro2 is python3- clean

Regards

Alastair McKinstry

--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.

Processed: 937525 RM: PKG -- removal triggered by the Python2 removal

[Debian Bug Tracking System]

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

> reassign 937525 ftp.debian.org
Bug #937525 [src:pyro] pyro: Python2 removal in sid/bullseye
Bug reassigned from package 'src:pyro' to 'ftp.debian.org'.
No longer marked as found in versions pyro/1:3.16-3.
Ignoring request to alter fixed versions of bug #937525 to the same values 
previously set
> retitle 937525  RM: PKG -- removal triggered by the Python2 removal
Bug #937525 [ftp.debian.org] pyro: Python2 removal in sid/bullseye
Changed Bug title to 'RM: PKG -- removal triggered by the Python2 removal' from 
'pyro: Python2 removal in sid/bullseye'.
> thanks
Stopping processing here.

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

Bug#950640: pycdio FTBFS with more than one supported python3 version

[Adrian Bunk]

Source: pycdio
Version: 2.0.0-1
Severity: serious
Tags: ftbfs

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

...
creating build/temp.linux-arm64-3.8/swig
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c swig/pycdio_wrap.c -o 
build/temp.linux-arm64-3.8/swig/pycdio_wrap.o
swig/pycdio_wrap.c:149:11: fatal error: Python.h: No such file or directory
  149 | # include 
  |   ^~
compilation terminated.


The build dependency on python3-dev should be corrected to python3-all-dev.

Bug#950638: pykwalify FTBFS: TestCore.test_core_files failure

[Adrian Bunk]

Source: pykwalify
Version: 1.7.0-2
Severity: serious
Tags: ftbfs bullseye sid

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

...
=== FAILURES ===
___ TestCore.test_core_files ___
...
>   compare(sorted(c.validation_errors), sorted(errors), 
> prefix="Wrong validation errors when parsing files : {0} : {1} : {2}".format(
f, document_index, document.get('name', 'UNKNOWN')))
E   AssertionError: Wrong validation errors when parsing files 
: 
/build/1st/pykwalify-1.7.0/.pybuild/cpython3_3.8/build/tests/files/fail/test_type_float.yaml
 : 1 : fail-type-float-2: sequence not as expected:
E   
E   same:
E   []
E   
E   first:
E   ["Value 'True' is not of type 'float'. Path: '/1'",
E"Value 'foo' is not of type 'float'. Path: '/0'"]
E   
E   second:
E   ["Value 'foo' is not of type 'float'. Path: '/0'"]
E   
E   While comparing [0]: 
E   "Value 'True' is not of type 'float'. Path: '/1'"
E   !=
E   "Value 'foo' is not of type 'float'. Path: '/0'"

tests/test_core.py:571: AssertionError
...

Bug#950637: update build-dep on iptables-dev

[Arturo Borrero Gonzalez]

Source: xtables-addons
Version: 3.7-1
Severity: serious

It seems xtables-addons build-deps on iptables-dev, which no longer exists.

Please update the build-deps of xtables-addons. You probably need the
libxtables-dev package instead.

This is apparently preventing the migration of iptables from sid to testing.

regards.

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

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

Bug#950632: marked as done (gcc-8/8.3.0-27 binaries not built from 8.3.0-27 sources on s390x)

[Debian Bug Tracking System]

Your message dated Tue, 04 Feb 2020 12:19:19 +
with message-id 
and subject line Bug#950632: fixed in gcc-8 8.3.0-28
has caused the Debian Bug report #950632,
regarding gcc-8/8.3.0-27 binaries not built from 8.3.0-27 sources on s390x
to be marked as done.

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

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


-- 
950632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8
Version: 8.3.0-27
Severity: serious

gcc-8/s390x has been manually uploaded to fix the breakage introduced
by gcc-10. However it has not been built from the 8.3.0-27 sources. At
least the changelog file is different from other architectures, causing
multiarch co-installability issues:

--- amd64/usr/share/doc/gcc-8-base/changelog.Debian   2020-02-03 
07:07:47.0 +
+++ s390x/usr/share/doc/gcc-8-base/changelog.Debian   2020-02-03 
07:07:47.0 +
@@ -13,8 +13,8 @@
   * Dump the config.log for the configure step when it fails.
   * On architectures where libgcc_s.so is a symlink, replace the symlink with
 a simple linker script.
-  * libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir.
-Addresses: #950525.
+  * libgcc-dev: Fix libgcc_so.1 symlink when building without common libraries.
+Closes: #950525.
   * Bump standards version.

  -- Matthias Klose   Mon, 03 Feb 2020 08:07:47 +0100
--- End Message ---
--- Begin Message ---
Source: gcc-8
Source-Version: 8.3.0-28

We believe that the bug you reported is fixed in the latest version of
gcc-8, 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.
Matthias Klose  (supplier of updated gcc-8 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: Tue, 04 Feb 2020 12:57:33 +0100
Source: gcc-8
Architecture: source
Version: 8.3.0-28
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 950632
Changes:
 gcc-8 (8.3.0-28) unstable; urgency=medium
 .
   * Sourceful no-change upload. Closes: #950632.
Checksums-Sha1:
 de4d9612ca218c5fcbfc87a4f470bfbab852823a 19704 gcc-8_8.3.0-28.dsc
 5420de743c157082ad3f5610656c26efb028e059 1122196 gcc-8_8.3.0-28.diff.gz
 4e0140a0a0f858cd7923d29d17351cbf961b39e2 9290 gcc-8_8.3.0-28_source.buildinfo
Checksums-Sha256:
 4d4c78c186f64c3fbcdb1ffb40719a857abbfa9051305298b7e2350124bed481 19704 
gcc-8_8.3.0-28.dsc
 62488fd5db693fa84d9fc0621bf49470a6435f28ea7f6979c4ad65d1504a5dc6 1122196 
gcc-8_8.3.0-28.diff.gz
 9f7f2b0d024009f6a54e3248d9e089936f93c7de87f611a3f5c8ddcff8bb5d0a 9290 
gcc-8_8.3.0-28_source.buildinfo
Files:
 72cd7efdd194ee8f8483f311a6f4b2ef 19704 devel optional gcc-8_8.3.0-28.dsc
 15323899e83a27854cafe9e96287418f 1122196 devel optional gcc-8_8.3.0-28.diff.gz
 8b97d66eabe81a1d55dcfc386a3da99f 9290 devel optional 
gcc-8_8.3.0-28_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl45XQMQHGRva29AdWJ1
bnR1LmNvbQAKCRC9fqpgd4+m9c2rD/9MJAGakUF2o2Q2p3XdduVFR0Q+gmquWSxF
mNcJUNxBA84TeLRuVd1/a3wGHWWVgyfJi/jXgQZGqXKJde4EeVCUCS3/1iNCZRBU
JAk4baw+14woG/ASj7bGJmv+dgiFW/eU/E8akuJivfgAJCbHYmvKRexjga18Ym6n
kHNyB5fMvqrC8Ah9OrnPIEJ5af3uys5vsvtG6d5jgnmxAUutTX7GnRRbY+EQYl01
LDSEMnnXO8LMa2b7UjelhG5JM9YA+PccgK9JDTTkk9+6pKPKOw3c+zJlpO7iXT4D
mQmGd/QJrcUifHprxw9MlJJrh8Jcj7M98AQ4qZS/YbDPz0iCU4kwxvsTOzhGvfQW
S+dGgMFmaT6pIpAzXxw//zqYuzKzpuCReDYHKWPW/irbklnziEsv2o4oH/92QEtG
UPCAVkjd9hvKznXxmGGhLYVbkdi/xsiZKt5juHMk/Ue2OY+y3AWQ3EzmPjM3EpLA
k05OamVlc4ZEhfn2fgTwdJyiUJ+N7AFKgKAARezsfoUTvYaJxB4PeT2H5yoaT22Y
AU1iNoe9Q/kdgruYHsR49wt7Giv8+C6pRWfF+RtqYTsuueBbDsV3cT26bDM3MwOb
mS0r2fQcKDTg0riecL0CuK0YLhQXmbij7v8NoV0adyCj0vZPX08StHa3h5iQfnA5
0ChUQY8Xtg==
=ebGY
-END PGP SIGNATURE End Message ---

Bug#950633: morris: FTBFS with boost1.71 deprecated signals library is removed

[Dimitri John Ledkov]

Package: morris
Version: 0.2-5
Severity: serious
Tags: ftbfs

Dear Maintainer,

boost1.71 has removed the deprecated signals library, thus morris
cannot be build against the upcoming boost ABI.

Given how old the libraries it uses are, maybe we should even remove
morris from the archive, as it is no longer practical to keep it in.

Regards,

Dimitri.

Bug#950632: gcc-8/8.3.0-27 binaries not built from 8.3.0-27 sources on s390x

[Aurelien Jarno]

Source: gcc-8
Version: 8.3.0-27
Severity: serious

gcc-8/s390x has been manually uploaded to fix the breakage introduced
by gcc-10. However it has not been built from the 8.3.0-27 sources. At
least the changelog file is different from other architectures, causing
multiarch co-installability issues:

--- amd64/usr/share/doc/gcc-8-base/changelog.Debian   2020-02-03 
07:07:47.0 +
+++ s390x/usr/share/doc/gcc-8-base/changelog.Debian   2020-02-03 
07:07:47.0 +
@@ -13,8 +13,8 @@
   * Dump the config.log for the configure step when it fails.
   * On architectures where libgcc_s.so is a symlink, replace the symlink with
 a simple linker script.
-  * libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir.
-Addresses: #950525.
+  * libgcc-dev: Fix libgcc_so.1 symlink when building without common libraries.
+Closes: #950525.
   * Bump standards version.

  -- Matthias Klose   Mon, 03 Feb 2020 08:07:47 +0100

Bug#950628: System with encrypted root unbootable because initramfs hooks don't include libgcc located in /lib

[Karol Augustin]

Package: cryptsetup-initramfs
Version: 2:2.2.2-2
Severity: critical

The side effect of initramfs logic used to find libgcc leads to
unbootable system if libgcc is in different location than libc. Maybe
something like "ldconfig -p | grep libgcc_s.so.1" should be used to
locate libgcc instead?

Details:

The recent update of libgcc1 to version 1:10-20200202-1 (unstable) moved
it from:
/lib/x86_64-linux-gnu/libgcc_s.so.1
to:
/lib/libgcc_s.so.1

The initramfs hook for cryptsetup is still looking for it using previous
location based on libc:

# cat /usr/share/initramfs-tools/hooks/cryptroot
[...]
LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')"
find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read
so; do
copy_exec "$so"
done

# echo $(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')
/lib/x86_64-linux-gnu

# ldd /sbin/cryptsetup
[...]
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4b0b6c)

This leads to omission of libgcc_s.so.1 in initramfs and makes unlocking
the root drive impossible (in case of LUKS2 at least) because of the
following error:
libgcc_s.so.1 must be installed for pthread_cancel to work

I created initramfs hook in /etc/ that includes libgcc and it solves the
problem (obviously as workaround):
cp /lib/libgcc_s.so.1 "${DESTDIR}/usr/lib/"

The difference in libgcc1 packages:
(version 1:10-20200202-1)
# dpkg -L libgcc1
/.
/lib
/lib/libgcc_s.so.1
/lib/x86_64-linux-gnu
/usr
/usr/share
/usr/share/doc
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libgcc1
/usr/share/doc/libgcc1

(version 1:9.2.1-25)
# dpkg -L libgcc1
/.
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/libgcc_s.so.1
/usr
/usr/share
/usr/share/doc
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libgcc1
/usr/share/doc/libgcc1


Thanks,
Karol

Bug#950624: libgcc-s1: libgcc_s.so.1 can be missing after upgrade on usrmerge systems

[Sven Joachim]

Package: libgcc-s1
Version: 10-20200202-1
Severity: serious

On systems where /lib is a symlink to /usr/lib (which is the case for
every new buster installation, for instance), it can easily happen that
/usr/lib/$DEB_HOST_MUTIARCH/libgcc_s.so.1 disappears on upgrades.  This
happens whenever libgcc-s1 is unpacked before the new libgcc1, because
the old libgcc1 package ships /lib/$DEB_HOST_MUTIARCH/libgcc_s.so.1
which is in the same place, but unfortunately dpkg does not detect that
this means there is a file conflict.

This actually happened to me in a usrmerge chroot, here is the relevant
excerpt from dpkg.log:

,
| # grep libgcc.*1: /var/log/dpkg.log
| 2020-02-04 10:02:17 install libgcc-s1:amd64  10-20200202-1
| 2020-02-04 10:02:17 status half-installed libgcc-s1:amd64 10-20200202-1
| 2020-02-04 10:02:17 status unpacked libgcc-s1:amd64 10-20200202-1
| 2020-02-04 10:02:17 configure libgcc-s1:amd64 10-20200202-1 
| 2020-02-04 10:02:17 status unpacked libgcc-s1:amd64 10-20200202-1
| 2020-02-04 10:02:17 status half-configured libgcc-s1:amd64 10-20200202-1
| 2020-02-04 10:02:17 status installed libgcc-s1:amd64 10-20200202-1
| 2020-02-04 10:02:17 upgrade libgcc1:amd64 1:9.2.1-1 1:10-20200202-1
| 2020-02-04 10:02:17 status half-configured libgcc1:amd64 1:9.2.1-1
| 2020-02-04 10:02:17 status unpacked libgcc1:amd64 1:9.2.1-1
| 2020-02-04 10:02:17 status half-installed libgcc1:amd64 1:9.2.1-1
| 2020-02-04 10:02:17 status unpacked libgcc1:amd64 1:10-20200202-1
| 2020-02-04 10:02:17 configure libgcc1:amd64 1:10-20200202-1 
| 2020-02-04 10:02:17 status unpacked libgcc1:amd64 1:10-20200202-1
| 2020-02-04 10:02:17 status half-configured libgcc1:amd64 1:10-20200202-1
| 2020-02-04 10:02:17 status installed libgcc1:amd64 1:10-20200202-1
`

Fortunately "apt reinstall libgcc-s1" remedies the situation, but if the
system is rebooted before that, the effects could be more drastic (see
#950254 and #950551).


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

Kernel: Linux 5.5.1-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Processed: tagging 950622

[Debian Bug Tracking System]

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

> tags 950622 + bullseye sid
Bug #950622 [src:python-sqt] python-sqt FTBFS with more than one supported 
python3 version
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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