Bug#937413: pycryptopp: Python2 removal in sid/bullseye

[Vasudev Kamath]

Hi Moritz,

Moritz Mühlenhoff  writes:
>
> Hi Vasudev,
>
> https://github.com/tahoe-lafs/pycryptopp/issues/36#issuecomment-504130020 
> states:
>
> | The Tahoe-LAFS project has decided it is not interested in porting
> | pycryptopp to Python 3. Instead, Tahoe-LAFS is switching to the
> | "cryptography" library.
> | 
> | I don't have any problem with anyone else taking on this porting effort
> | but I'm closing this to reflect the fact that the maintainers have
> | no plans of taking this on.
>
> Given that the now removed tahoe-lafs was the only reverse dependency,
> let's also remove pycryptopp?

Right upstream stopped using it a while ago but I could not get that
change in tahoe-lafs during that time due to dependency on
magic-wormhole lib which was py3 only and could not work with
tahoe-lafs in archive.

I missed  this let me file a bug to get this as well removed from the
archive. Thanks for bringing this up.

Cheers,
Vasudev

Processed: severity of 959828 is important

[Debian Bug Tracking System]

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

> severity 959828 important
Bug #959828 [systemctl] systemctl: `Provides: systemd`, but doesn't provide 
what systemd does
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

[Dmitry Smirnov]

On Wednesday, 6 May 2020 8:28:09 AM AEST Ansgar wrote:
> The last upload adds `Provides: systemd`, but `systemctl` obviously
> doesn't provide the same (or similar) functionality as the `systemd`
> package.

It does provide similar functionality under certain circumstances such as 
inside application containers where "systemd" (or init system) is not 
present.

The purpose of "systemctl" package is to provide alternative "systemctl" 
utility to manage systemd services without systemd. Of course is it not a 
complete implementation but IMHO quite sufficient to be practically useful 
and warrant for "Provides: systemd".

The unfortunate problem why I had to introduce "Provides: systemd" is 
discussed in #959174.


> As a random example, systemd-tmpfiles and other utilities are not
> provided by `systemctl`.

It would be ridiculous to re-implement all broad systemd functionality.
However service management functionality is mature enough and that's a 
primary feature of systemd as well.

-- 
Cheers,
 Dmitry Smirnov.

---

I am easily satisfied with the very best.
-- Winston Churchill


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

Bug#938846: marked as done (xia: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 23:48:13 +
with message-id 
and subject line Bug#959796: Removed package(s) from unstable
has caused the Debian Bug report #938846,
regarding xia: 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.)


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

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

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

Dear submitter,

as the package xia 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/959796

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

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 23:49:04 +
with message-id 
and subject line Bug#959824: Removed package(s) from unstable
has caused the Debian Bug report #938365,
regarding ropemode: 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.)


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

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

Dear submitter,

as the package ropemode 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/959824

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#959801: marked as done (ropemode: Consider removing it from Debian)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 23:49:04 +
with message-id 
and subject line Bug#959824: Removed package(s) from unstable
has caused the Debian Bug report #959801,
regarding ropemode: Consider removing it from Debian
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.)


-- 
959801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ropemode
Severity: serious
Version: 0.4-1
X-Debbugs-CC: python-modules-t...@lists.alioth.debian.org

Package ropemode has been orphaned by its original maintainer and is python2-
only. Perhaps it's time for us to have it removed from Debian.

Package ropemode has no reverse dependencies or reverse build-dependencies.

I will submit a removal request 21 days later (After May 26, 2020) in hope
that someone may pick up this package and migrate it to python3.

-- 
Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 0.4-1+rm

Dear submitter,

as the package ropemode 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/959824

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#959565: libjdom2-intellij-java: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':contrib:co

[Emmanuel Bourg]

Control: reassign -1 libxalan2-java
Control: found -1 2.7.2-3
Control: severity -1 important
Control: affects -1 + libjdom2-intellij-java
Control: retitle -1 libxalan2-java: xml-apis dependency left in the 
xalan:serializer pom

The actual issue is with libxalan2-java, because the xalan:serializer
pom depends on xml-apis but the package doesn't depend on libjaxp1.3-java.

Processed: Re: Bug#959565: libjdom2-intellij-java: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configurati

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libxalan2-java
Bug #959565 [src:libjdom2-intellij-java] libjdom2-intellij-java: FTBFS: 
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':contrib:compileClasspath'.
Bug reassigned from package 'src:libjdom2-intellij-java' to 'libxalan2-java'.
No longer marked as found in versions 
libjdom2-intellij-java/2.0.6+git20180529-2.
Ignoring request to alter fixed versions of bug #959565 to the same values 
previously set
> found -1 2.7.2-3
Bug #959565 [libxalan2-java] libjdom2-intellij-java: FTBFS: 
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':contrib:compileClasspath'.
Marked as found in versions libxalan2-java/2.7.2-3.
> severity -1 important
Bug #959565 [libxalan2-java] libjdom2-intellij-java: FTBFS: 
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':contrib:compileClasspath'.
Severity set to 'important' from 'serious'
> affects -1 + libjdom2-intellij-java
Bug #959565 [libxalan2-java] libjdom2-intellij-java: FTBFS: 
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':contrib:compileClasspath'.
Added indication that 959565 affects libjdom2-intellij-java
> retitle -1 libxalan2-java: xml-apis dependency left in the xalan:serializer 
> pom
Bug #959565 [libxalan2-java] libjdom2-intellij-java: FTBFS: 
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':contrib:compileClasspath'.
Changed Bug title to 'libxalan2-java: xml-apis dependency left in the 
xalan:serializer pom' from 'libjdom2-intellij-java: FTBFS: 
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':contrib:compileClasspath'.'.

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

Bug#959567: marked as done (dom4j: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':testCompile

[Emmanuel Bourg]

> Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: Could 
> not resolve xml-apis:xml-apis:debian.
> Required by:
> project : > xalan:xalan:debian > xalan:serializer:debian

The actual issue is with libxalan2-java, because the xalan:serializer
pom depends on xml-apis but the package doesn't depend on
libjaxp1.3-java. Any package depending on xalan is likely to fail similarly.

The xml-apis artifact contains the javax.xml classes now integrated in
the JDK. In most cases this dependency can be dropped (from the poms and
the packages dependencies).

Emmanuel Bourg

Bug#942988: displaycal: Python2 removal in sid/bullseye

[Florian Höch]

Hey, just letting you know upstream is indeed still alive.

As you have noticed, things take longer than expected, and not all is 
due to the move to Python3. While I appreciate the offer to help, at the 
moment it would make things harder to juggle for me.


The reason there is no commits over at SF is also that I'm going to move 
code repos. Too much going on atm.


--
Florian Höch
https://displaycal.net

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

[Ansgar]

Package: systemctl
Version: 1.4.4147-2
Severity: serious

The last upload adds `Provides: systemd`, but `systemctl` obviously
doesn't provide the same (or similar) functionality as the `systemd`
package.

As a random example, systemd-tmpfiles and other utilities are not
provided by `systemctl`.

Ansgar

Bug#959637: marked as done (beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 22:03:36 +
with message-id 
and subject line Bug#959637: fixed in beads 1.1.19+dfsg-1
has caused the Debian Bug report #959637,
regarding beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev
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.)


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), cmake, qtbase5-dev, 
> qttools5-dev, libodsstream-qt5-dev, cimg-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), cmake, qtbase5-dev, 
> qttools5-dev, libodsstream-qt5-dev, cimg-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [403 B]
> Get:5 copy:/<>/apt_archive ./ Packages [486 B]
> Fetched 1846 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libodsstream-qt5-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/beads_1.1.18+dfsg-4_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: beads
Source-Version: 1.1.19+dfsg-1
Done: Filippo Rusconi 

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

Debian distribution maintenance software
pp.
Filippo Rusconi  (supplier of updated beads 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, 05 May 2020 20:08:31 +0200
Source: beads
Binary: beads beads-dbgsym
Architecture: source amd64
Version: 1.1.19+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team 

Changed-By: Filippo Rusconi 
Description:
 beads  - 2-DE electrophoresis gel image spot detection
Closes: 959637
Changes:
 beads (1.1.19+dfsg-1) unstable; urgency=low
 .
   * New version updating the CMake build system to match
 the changes operated in the libodsstream package
 (closes: #959637) and the name of the libodsstream-dev
 package name. Thanks a lot to Lucas Nussbaum
  and Andreas Tille
  for reporting the problem.
 .
   * Standards-Version: 4.5.0 (no changes needed).
 .
   * Changed the inra.fr 

Bug#937413: pycryptopp: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:33:16AM +, Matthias Klose wrote:
> Package: src:pycryptopp
> Version: 0.7.1-4
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> 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.

Hi Vasudev,

https://github.com/tahoe-lafs/pycryptopp/issues/36#issuecomment-504130020 
states:

| The Tahoe-LAFS project has decided it is not interested in porting
| pycryptopp to Python 3. Instead, Tahoe-LAFS is switching to the
| "cryptography" library.
| 
| I don't have any problem with anyone else taking on this porting effort
| but I'm closing this to reflect the fact that the maintainers have
| no plans of taking this on.

Given that the now removed tahoe-lafs was the only reverse dependency,
let's also remove pycryptopp?

Cheers,
Moritz

Bug#959582: marked as done (castle-game-engine: FTBFS: tries to write stuff to homedir?)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 20:34:10 +
with message-id 
and subject line Bug#959582: fixed in castle-game-engine 6.4+dfsg1-3
has caused the Debian Bug report #959582,
regarding castle-game-engine: FTBFS: tries to write stuff to homedir?
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.)


-- 
959582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: castle-game-engine
Version: 6.4+dfsg1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc/pasdoc/logo'
> inkscape castle_game_engine_icon.svg \
>   --export-width=256 \
>   --export-height=256 \
>   --export-background=white \
>   --export-background-opacity=0 \
>   --export-png=castle_game_engine_icon.png
> 
> ** (process:17485): WARNING **: 04:12:44.583: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option --export-png=castle_game_engine_icon.png
> make[2]: *** [Makefile:9: castle_game_engine_icon.png] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/05/01/castle-game-engine_6.4+dfsg1-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated castle-game-engine 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, 05 May 2020 21:48:26 +0200
Source: castle-game-engine
Architecture: source
Version: 6.4+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Paul Gevers 
Closes: 959582
Changes:
 castle-game-engine (6.4+dfsg1-3) unstable; urgency=medium
 .
   * Add inkscape-dropped--export-png.patch, thanks Lucas Nussbaum for
 reporting Closes: #959582
   * d/control: Add versioned B-D on inkscape
   * d/control: use canonical Vcs-Browser
   * Bump compat (via debhelper-compat) to 13
   * Add d/castle-game-engine-src.lintian-overrides as the issue is only
 with packages build with cge
   * Add lintian override for dh-exec-subst-unknown-variable
   * Drop embedded ttf files that can be (and are) linked from packages
   * Bump standards
Checksums-Sha1:
 56a06bfb047b85e46be6de8688b2a436d4253539 2316 
castle-game-engine_6.4+dfsg1-3.dsc
 1ef61cc1411c44115f799446f5a4abe38128a40b 22424 
castle-game-engine_6.4+dfsg1-3.debian.tar.xz
Checksums-Sha256:
 797ae5d1aedc71d7a9faacb807bc8268dd4ad62036956c2fe6c11d0785442d40 2316 
castle-game-engine_6.4+dfsg1-3.dsc
 22f728be045f696f49509de2ec377f0add826bfe9af9d0ba13e7d3f08a41c07f 22424 
castle-game-engine_6.4+dfsg1-3.debian.tar.xz
Files:
 800f786468996b772fc10b7f2f629585 2316 misc optional 
castle-game-engine_6.4+dfsg1-3.dsc
 55e7b9f93a24a25def1e98524c0a8034 22424 misc optional 
castle-game-engine_6.4+dfsg1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl6xwzgACgkQnFyZ6wW9
dQrXGQf+NFrwGcP2CcSRIkWQhARqmq5kwLr8ZGP6Icl+k8kURI4MyimIBCmFjeiO
m7ShuEor4sIyhH/R6UAm4J5Kf9YQGXGDdXmAwKESvM8BzjYqbeV+Aom5aPN4W3hy
XrJt0+wNu/57OWNsRKySSb8AAy9GY7kIrZ/6A4zTFBrJLpMxRZzt+OEapSWo9syF
PnVzxibmJh8haS6RfpnsMvLrtJfGKmwcktAQjlXxCvhN518iWoJX/ckrbsrDrR/h
yNAno3WjhRQ1AbMl3rXePr+ntea8FJdjKjyI+SbFfgRXqaW5EscNbRW10Bw+6RBi
Ywr35gcXQzPenDoEWxkgI28hU0oFlw==
=1271
-END PGP SIGNATURE End Message ---

Bug#959697: marked as done (mpfi: FTBFS on arch where texinfo is not installed)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 20:35:15 +
with message-id 
and subject line Bug#959697: fixed in mpfi 1.5.3+ds-4
has caused the Debian Bug report #959697,
regarding mpfi: FTBFS on arch where texinfo is not installed
to be marked as done.

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

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


-- 
959697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpfi
Version: 1.5.3+ds-3
Severity: serious

Hello, looks like the current mpfi is trying to build documentation on arch:any 
now, and without makeinfo installed it FTBFS now.

libtool: link: ar cr .libs/libmpfi.a  abs.o acos.o acosh.o add.o add_d.o 
add_fr.o add_q.o add_si.o add_ui.o add_z.o alea.o asin.o asinh.o atan2.o atan.o 
atanh.o bisect.o blow.o cbrt.o clear.o cmp.o cmp_sym_pi.o constants.o cos.o 
cosh.o csc.o csch.o cot.o coth.o d_div.o d_sub.o diam.o div.o div_2exp.o 
div_2si.o div_2ui.o div_d.o div_fr.o div_q.o div_si.o div_ui.o div_z.o error.o 
exp.o exp2.o expm1.o fr_div.o fr_sub.o get_endpoints.o get_fr.o get_d.o 
get_prec.o get_version.o has_zero.o hypot.o increase.o init.o intersect.o 
interv_d.o interv_fr.o interv_q.o interv_si.o interv_ui.o interv_z.o inp_str.o 
inv.o is_empty.o is_inside.o log.o log10.o log1p.o log2.o mag.o mid.o mig.o 
mul.o mul_2exp.o mul_2si.o mul_2ui.o mul_d.o mul_fr.o mul_q.o mul_si.o mul_ui.o 
mul_z.o neg.o out_str.o predicates.o print_binary.o put.o put_d.o put_fr.o 
put_q.o put_si.o put_ui.o put_z.o q_div.o q_sub.o quadrant.o revert_if_needed.o 
round_prec.o sec.o sech.o set.o set_d.o set_fr.o set_prec.o set_q.o set_si.o 
set_str.o set_ui.o set_z.o si_div.o si_sub.o sign.o sin.o sinh.o sqr.o sqrt.o 
sub.o sub_d.o sub_fr.o sub_q.o sub_si.o sub_ui.o sub_z.o swap.o tan.o tanh.o 
ui_div.o ui_sub.o union.o urandom.o z_div.o z_sub.o
libtool: link: ranlib .libs/libmpfi.a
libtool: link: ( cd ".libs" && rm -f "libmpfi.la" && ln -s "../libmpfi.la" 
"libmpfi.la" )
make[5]: Leaving directory '/<>/mpfi-1.5.3+ds/_build/src'
make[4]: Leaving directory '/<>/mpfi-1.5.3+ds/_build/src'
Making all in tests
make[4]: Entering directory '/<>/mpfi-1.5.3+ds/_build/tests'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/<>/mpfi-1.5.3+ds/_build/tests'
Making all in doc
make[4]: Entering directory '/<>/mpfi-1.5.3+ds/_build/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd ../../doc && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/mpfi-1.5.3+ds/build-aux/missing makeinfo --version) 
>/dev/null 2>&1; then \
  for f in ../../doc/mpfi.info ../../doc/mpfi.info-[0-9] 
../../doc/mpfi.info-[0-9][0-9] ../../doc/mpfi.i[0-9] 
../../doc/mpfi.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/mpfi-1.5.3+ds/build-aux/missing makeinfo   -I 
../../doc \
 -o ../../doc/mpfi.info ../../doc/mpfi.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd ../../doc; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd ../../doc && \
  $restore $backupdir/* `echo "./../../doc/mpfi.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/mpfi-1.5.3+ds/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[4]: *** [Makefile:354: ../../doc/mpfi.info] Error 127
make[4]: Leaving directory '/<>/mpfi-1.5.3+ds/_build/doc'
make[3]: *** [Makefile:404: all-recursive] Error 1
make[3]: Leaving directory '/<>/mpfi-1.5.3+ds/_build'
make[2]: *** [Makefile:336: all] Error 2
make[2]: Leaving directory '/<>/mpfi-1.5.3+ds/_build'
dh_auto_build: error: cd _build && make -j4 returned exit code 2
make[1]: *** [debian/rules:31: override_dh_auto_build-arch] Error 25
make[1]: Leaving directory '/<>/mpfi-1.5.3+ds'
make: *** [debian/rules:23: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Moving texinfo and texlive-latex-base from b-d-indep to b-d "hides" the problem.

Gianfranco
--- End Message ---
--- Begin Message ---
Source: mpfi
Source-Version: 1.5.3+ds-4
Done: Jerome Benoit 

We 

Bug#939962: builds in git

[ygrek]

Hi,

 Upstream moved to https://github.com/SKS-Keyserver/sks-keyserver
 git master builds with 4.08 : 
https://travis-ci.org/github/SKS-Keyserver/sks-keyserver/jobs/683544082
 I will look to make a release

-- 

Bug#955689: libcatmandu-filestore-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255

[Niko Tyni]

On Fri, Apr 03, 2020 at 09:52:13PM +0200, Lucas Nussbaum wrote:
> Source: libcatmandu-filestore-perl
> Version: 1.13-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200402 ftbfs-bullseye

> > # Error:  Can't locate Data/UUID.pm in @INC (you may need to install 
> > the Data::UUID module) (@INC contains: /<>/blib/lib 
> > /<>/blib/arch /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 
> > /<>/blib/lib/Catmandu/DirectoryIndex/UUID.pm line 12.

This was unmasked by libcatmandu-perl 1.2011-1 dropping its dependency
on libdata-uuid-perl.

It looks like Data::UUID was not necessary at all, so upstream has
dropped it in

  
https://github.com/LibreCat/Catmandu-FileStore/commit/0e9e2d09dae88f6a0ca39edf0a342f8364c43f22

-- 
Niko Tyni   nt...@debian.org

Processed: libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 955689
Bug #959818 [libcatmandu-perl] libcatmandu-perl: 1.2011-1 breaks 
libcatmandu-filestore-perl
959818 was not blocked by any bugs.
959818 was not blocking any bugs.
Added blocking bug(s) of 959818: 955689

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

Bug#959818: libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl

[Niko Tyni]

Package: libcatmandu-perl
Version: 1.2011-1
Severity: serious
Control: block -1 with 955689

1.2011-1 in unstable dropped its dependency on libdata-uuid-perl,
unmasking a missing dependency in libcatmandu-filestore-perl (#955689).
This was noticed by autopkgtest checks, currently preventing testing
migration of libcatmandu-perl.

libcatmandu-filestore-perl should be fixed first, and libcatmandu-perl
should then declare a Breaks relation on the earlier versions
of libcatmandu-filestore-perl to prevent partial upgrades where
libcatmandu-perl is updated before libcatmandu-filestore-perl.
-- 
Niko Tyni   nt...@debian.org

Bug#863650: Fix available

[Jan Niehusmann]

Hi,

I submitted a patch for this issue upstream:
https://github.com/pam-pgsql/pam-pgsql/pull/16

Jan

Processed: oggvideotools: Test dependency on pysycache-i18n that will likely be removed

[Debian Bug Tracking System]

Processing control commands:

> block 912504 by -1
Bug #912504 [src:pysycache] pysycache: Please migrate to python3-pygame
912504 was not blocked by any bugs.
912504 was blocking: 937441 937695
Added blocking bug(s) of 912504: 959814
> block 937553 by -1
Bug #937553 [src:pysycache] pysycache: Python2 removal in sid/bullseye
937553 was blocked by: 945632
937553 was blocking: 937441 937695
Added blocking bug(s) of 937553: 959814

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

Bug#959814: oggvideotools: Test dependency on pysycache-i18n that will likely be removed

[Adrian Bunk]

Source: oggvideotools
Version: 0.9.1-5
Severity: serious
Tags: ftbfs bullseye sid
Control: block 912504 by -1
Control: block 937553 by -1

pysycache-i18n will likely be removed due to #912504 and #937553.

Options are to change yet again to another ogg for this test,
or to remove this specific test.

Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 Peter Cock 

Hi Peter,

with the upload of ncbi-blast+ version 2.10 Biopython test is running
into failures (see 

   https://bugs.debian.org/959587#10

)

Could you please adjust the Biopython test suite accordingly?

Kind regards

 Andreas.

On Tue, May 05, 2020 at 11:38:23AM -0400, Aaron M. Ucko wrote:
> 
> > Since there is a strong relation in time with your upload and this
> > FTBFS of biopython do you think that this could be connected:
> 
> Yes, per https://www.ncbi.nlm.nih.gov/books/NBK131777/, the upgrade to
> 2.10.0 changed the default database version (controlled by makeblastdb's
> -blastdb_version flag) from 4 to 5, causing some output files to change
> names (and formats):
> 
> *.nsd -> *.nnd
> *.nsi -> *.nni
> *.psd -> *.pnd
> *.psi -> *.pni
> 
> Thanks for checking!

-- 
http://fam-tille.de

Processed: Re: Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #959587 [src:python-biopython] python-biopython: FTBFS: AssertionError: 
False is not true
Added tag(s) upstream.
> forwarded -1 Peter Cock 
Bug #959587 [src:python-biopython] python-biopython: FTBFS: AssertionError: 
False is not true
Set Bug forwarded-to-address to 'Peter Cock '.

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

Bug#787599: marked as done (Some sources are not included in your package)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 18:33:25 +
with message-id 
and subject line Bug#787599: fixed in ganglia-web 3.6.1-3.1
has caused the Debian Bug report #787599,
regarding Some sources are not included in your 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.)


-- 
787599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ganglia-web
version; 3.6.1-1
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:

js/jquery.scrollTo-1.4.3.1-min.js
js/jquery.qtip.min.js
js/jquery-ui.min.js


Please override the following and add why on override file
js/protovis-r3.2.js (source is js/protovis-d3.2.js)
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.widget.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.tooltip.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.tabs.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.spinner.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.sortable.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.slider.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.selectable.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.resizable.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.progressbar.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.position.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.mouse.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.menu.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-transfer.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-slide.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-shake.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-scale.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-pulsate.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-highlight.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-fold.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-fade.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-explode.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-drop.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-clip.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-bounce.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.effect-blind.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.droppable.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.draggable.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.dialog.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.datepicker.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.core.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.button.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.autocomplete.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery.ui.accordion.min.js
contrib/jquery-ui-1.10.2/ui/minified/jquery-ui.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-zh-TW.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-zh-HK.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-zh-CN.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-vi.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-uk.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-tr.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-tj.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-th.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-ta.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-sv.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-sr.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-sr-SR.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-sq.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-sl.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-sk.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-ru.min.js
contrib/jquery-ui-1.10.2/ui/minified/i18n/jquery.ui.datepicker-ro.min.js

Processed: src:libqtdbusmock: fails to migrate to testing for too long: FTBFS on all release archs

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.7+bzr49+repack1-4
Bug #959813 [src:libqtdbusmock] src:libqtdbusmock: fails to migrate to testing 
for too long: FTBFS on all release archs
Marked as fixed in versions libqtdbusmock/0.7+bzr49+repack1-4.
Bug #959813 [src:libqtdbusmock] src:libqtdbusmock: fails to migrate to testing 
for too long: FTBFS on all release archs
Marked Bug as done

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

Bug#959813: src:libqtdbusmock: fails to migrate to testing for too long: FTBFS on all release archs

[Paul Gevers]

Source: libqtdbusmock
Version: 0.7+bzr49+repack1-3
Severity: serious
Control: close -1 0.7+bzr49+repack1-4
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Tianon Gravi]

On Sun, 3 May 2020 at 06:12, Lucas Nussbaum  wrote:
> > ...
> > === warnings summary 
> > ===
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_fors[sfor]
> >   /<>/hy/models.py:133: RuntimeWarning: coroutine '' 
> > was never awaited
> > return super(HySymbol, cls).__new__(cls, s)
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_fors[gfor]
> >   /usr/lib/python3/dist-packages/funcparserlib/parser.py:232: 
> > RuntimeWarning: coroutine '' was never awaited
> > self.pos = pos
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_empty_for
> >   /usr/lib/python3/dist-packages/_pytest/nodes.py:192: RuntimeWarning: 
> > coroutine '' was never awaited
> > return (x[1] for x in self.iter_markers_with_node(name=name))
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/core.hy::test_parse_args
> >   /usr/lib/python3/dist-packages/funcparserlib/parser.py:322: 
> > RuntimeWarning: coroutine '' was never awaited
> > raise NoParseError('got unexpected token', s)
> >
> > -- Docs: https://docs.pytest.org/en/latest/warnings.html
> > === 5 failed, 547 passed, 54 deselected, 4 warnings in 8.47 seconds 
> > 
> > E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd 
> > /<>/.pybuild/cpython3_3.8_hy/build; python3.8 -m pytest -k 
> > '-test_bin -test_hy2py'
> > dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 
> > returned exit code 13
>
> ...

Oh, fun times.

I was definitely over my head with this one, so I reached out to the
Hy community and was pointed to https://bugs.python.org/issue39562,
which does seem quite related from my own limited understanding, so
this might technically be a bug in the Python package?

I'm including the Debian Python list on CC to hopefully see if someone
there can provide some assistance figuring out what's necessary here.
O:)

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

Processed: affects 959374

[Debian Bug Tracking System]

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

> affects 959374 src:proteinortho
Bug #959374 [src:diamond-aligner] diamond-aligner FTBFS on big endian
Added indication that 959374 affects src:proteinortho
> thanks
Stopping processing here.

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

Bug#939932: marked as done (varnish-modules: FTBFS after new varnish update)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 18:19:37 +
with message-id 
and subject line Bug#939932: fixed in varnish-modules 0.16.0-1
has caused the Debian Bug report #939932,
regarding varnish-modules: FTBFS after new varnish update
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.)


-- 
939932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: varnish-modules
Version: 0.15.0-1
Severity: serious

Hello, can you please update the package to cope with new varnish APIs?
the current package FTBFS in sid.

Upstream PR 142 might help in the porting work
https://github.com/varnish/varnish-modules/pull/142/files

G.
--- End Message ---
--- Begin Message ---
Source: varnish-modules
Source-Version: 0.16.0-1
Done: Stig Sandbeck Mathisen 

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

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

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

Debian distribution maintenance software
pp.
Stig Sandbeck Mathisen  (supplier of updated varnish-modules 
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, 05 May 2020 19:48:59 +0200
Source: varnish-modules
Architecture: source
Version: 0.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Varnish Package Maintainers 
Changed-By: Stig Sandbeck Mathisen 
Closes: 939932
Changes:
 varnish-modules (0.16.0-1) unstable; urgency=medium
 .
   [ Jonas Genannt ]
   * New upstream version 0.16.0 (Closes: #939932)
   * debian/patches removed all patches, included into new upstream version
   * debian/NEWS: added information about missing cookie vmod
   * debian/control:
 * updated description (cookie removed)
 * bump varnish depends to 6.4.0
 * bumpd standards version
   * debian/rules: tarball has no bootstrap included
   * copyright: updated to new tarball
Checksums-Sha1:
 916ae84a116d33f488ee78ce345d22406a4c1858 2349 varnish-modules_0.16.0-1.dsc
 7a0bacbabf099bd3d0fb1fd4e56de4c2cbffa5d2 430173 
varnish-modules_0.16.0.orig.tar.gz
 d6ac9d95a5e10c764f788c8e4229a7c55af8e83e 5436 
varnish-modules_0.16.0-1.debian.tar.xz
Checksums-Sha256:
 b255619b781b47974c4f409a26edf97d538f09b8f4be9647c4134cbeb0d4d6bd 2349 
varnish-modules_0.16.0-1.dsc
 bab1cbcad6ab77a5cf75af51b15f666ff15cf77a50b04031f399dca8e95d05de 430173 
varnish-modules_0.16.0.orig.tar.gz
 19d492799dbc15f33359d58b82cf31cba4539fb1ecf5a8e1c9389b55cd70c432 5436 
varnish-modules_0.16.0-1.debian.tar.xz
Files:
 93160862a80fc23f91bb006a53aa236f 2349 web optional varnish-modules_0.16.0-1.dsc
 e0974f34a989e851db6ddef44e9451f8 430173 web optional 
varnish-modules_0.16.0.orig.tar.gz
 d1a147616e8184ca61532ea0056ad0d3 5436 web optional 
varnish-modules_0.16.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEeZ5n7uInSAMeBaLcfbqVjBwFVTgFAl6xqZAPHHNzbUBkZWJp
YW4ub3JnAAoJEH26lYwcBVU4I04P/3sqSTjahAZxJ8OPV0CYTQWWJJ8P6+u6Tkel
b+sYvGcL28e6SbTxdYNTufi9VFwJxdqU1gRvzMEiqLFc2bhL9E/qvMu36sdFn/FY
bROFPZ0FjAjkp9r07MgRoOjKkSLKtZbZhRdZ6B8N9z/F7zAXksGNHhQieZJ2Lbsv
xytgDweKUzq8z1NQdXL11ri4caOJXynzqAhautEpk1mreXwejPILkT4GKR7Ka1Ou
HE9H7bsezDh5NGuL5dsc1FVgoNOfl5IF62HE/9/z0/6CtYdWYtWLWrJvpqhXgSN4
ThX9h6nm0+gnW2bC5NATo9r4q3oQUZHCljAD1XGuqFecrvUew1CruPvwIM/PhLLU
aB7P5ZzEWmYQFvWWXXZK8ntU1YDebdbfc5/xFcwbzN3oqqAfmHpTm8R+qGvMVtAZ
wzRvn01v/BsufjSvew47cbmr6KwNRwl/1ViZuveGsubyb4VjfDZd5Vle7KNSTs6G
lpixbqGu8iKaeUhU1bgU4w+CEe7gRwoHpmbC2aJxvNAjdREYYzysYSzYcOBea9FQ
31xRYn5PFJ4+kKqbzDikyv6mfWi44OqxA9iW+uof9iR380VhSsWxkH04uz208GjG
V0BRqrpLP+7Ue+zz/T4bQ3GBzgyEpWP9nIfj3K9lo0yrJIuxsDZ/4Yx3tm9rK3Te
FoECX/JF
=UQT7
-END PGP SIGNATURE End Message ---

Bug#959607: marked as done (mailscripts: FTBFS: imap-dl:94: error: Incompatible types in assignment (expression has type "Tuple[Literal['OK'], List[bytes]]", variable has type "Tuple[str, List[Union[b

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 18:18:36 +
with message-id 
and subject line Bug#959607: fixed in mailscripts 0.20-1
has caused the Debian Bug report #959607,
regarding mailscripts: FTBFS: imap-dl:94: error: Incompatible types in 
assignment (expression has type "Tuple[Literal['OK'], List[bytes]]", variable 
has type "Tuple[str, List[Union[bytes, Tuple[bytes, bytes")
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./tests/email-print-mime-structure.sh
> Testing alternative.eml
> Testing attachment.eml
> Testing encrypted.eml (PGPy)
> /usr/lib/python3/dist-packages/pgpy/decorators.py:129: UserWarning: Message 
> was encrypted with this key's subkey: 7C2FAA4DF93C37B2. Decrypting with 
> that...
>   return action(_key, *args, **kwargs)
> Testing encrypted.eml (GnuPG PGP/MIME)
> Testing simple.eml
> Testing smime-encrypted.eml (OpenSSL)
> Testing smime-encrypted.eml (GnuPG S/MIME)
> gpgsm: 992 bytes of 3DES encrypted text
> gpgsm: processing certBag
> gpgsm: issuer certificate (#/CN=Sample LAMPS Certificate Authority) not found
> gpgsm: 872 bytes of 3DES encrypted text
> gpgsm: processing certBag
> gpgsm: 1224 bytes of 3DES encrypted text
> gpgsm: DBG: keygrip= D3 E5 44 6E 1D 01 22 86 F3 97 4B F4 BB CD 56 19 4A 2B E5 
> FC
> Testing smime-signed.eml
> mypy --strict ./email-print-mime-structure
> Success: no issues found in 1 source file
> mypy --strict ./imap-dl
> imap-dl:94: error: Incompatible types in assignment (expression has type 
> "Tuple[Literal['OK'], List[bytes]]", variable has type "Tuple[str, 
> List[Union[bytes, Tuple[bytes, bytes")
> imap-dl:185: error: unused 'type: ignore' comment
> imap-dl:197: error: Argument 2 to "auth_gssapi" has incompatible type 
> "IMAP4"; expected "IMAP4_SSL"
> imap-dl:199: error: Argument 2 to "auth_builtin" has incompatible type 
> "IMAP4"; expected "IMAP4_SSL"
> imap-dl:213: error: Incompatible types in assignment (expression has type 
> "Optional[bytes]", variable has type "Union[bytes, Tuple[bytes, bytes]]")
> imap-dl:220: error: Argument 1 to "pull_msgs" has incompatible type "IMAP4"; 
> expected "IMAP4_SSL"
> imap-dl:227: error: Incompatible types in assignment (expression has type 
> "Tuple[str, Union[List[None], List[Union[bytes, Tuple[bytes, bytes]", 
> variable has type "Tuple[str, List[Union[bytes, Tuple[bytes, bytes")
> Found 7 errors in 1 file (checked 1 source file)
> make[1]: *** [Makefile:15: check] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/mailscripts_0.19-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated mailscripts 
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, 05 May 2020 10:53:38 -0700
Source: mailscripts
Architecture: source
Version: 0.20-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Closes: 955011 958391 959607
Changes:
 mailscripts (0.20-1) unstable; urgency=medium
 .
   * imap-dl: Fix failure when python3-gssapi isn't installed (Closes: #955011).
 Thanks to 

Processed: Bug#959637: marked as done (beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

[Debian Bug Tracking System]

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

> reopen 959637
Bug #959637 {Done: Filippo Rusconi } [src:beads] beads: 
FTBFS: build-dependency not installable: libodsstream-qt5-dev
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libodsstream/0.7.8-1.
> #Reopening because I closed it by error.
> thanks
Stopping processing here.

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

Bug#954645: closed by Lucas Nussbaum (unreproducible FTBFS)

[Sebastiaan Couwenberg]

Control: tags -1 patch

On Fri, 3 Apr 2020 21:40:10 +0200 Lucas Nussbaum wrote:
> > I'm closing those bugs: those failures are no longer reproducible,
> > checking again 12 hours later. Either they were caused by another
> > package that was fixed in the meantime, or they are random failures.
> 
> Actually, this is reproducible.

It seems to be reproducible only in specific environments. On my system
with cowbuilder it builds fine. But on the reproducible builds systems
with pbuilder you see the same test failures as you.

The attached patch should help, it adds build dependencies for the
modules required for tests, among them is pytest for which
ModuleNotFoundError exceptions were raised.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru behave-1.2.6/debian/control behave-1.2.6/debian/control
--- behave-1.2.6/debian/control 2020-01-25 13:57:18.0 +0100
+++ behave-1.2.6/debian/control 2020-05-05 18:14:19.0 +0200
@@ -11,6 +11,8 @@
python3-nose,
python3-parse,
python3-parse-type,
+   python3-path,
+   python3-pytest,
python3-setuptools,
python3-six,
python3-sphinx,

Processed: Re: Bug#954645 closed by Lucas Nussbaum (unreproducible FTBFS)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #954645 [src:behave] behave: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.7 3.8" returned exit code 13
Added tag(s) patch.

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

Bug#959637: marked as done (beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 16:33:44 +
with message-id 
and subject line Bug#959637: fixed in libodsstream 0.7.8-1
has caused the Debian Bug report #959637,
regarding beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev
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.)


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), cmake, qtbase5-dev, 
> qttools5-dev, libodsstream-qt5-dev, cimg-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), cmake, qtbase5-dev, 
> qttools5-dev, libodsstream-qt5-dev, cimg-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [403 B]
> Get:5 copy:/<>/apt_archive ./ Packages [486 B]
> Fetched 1846 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libodsstream-qt5-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/beads_1.1.18+dfsg-4_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Filippo Rusconi  (supplier of updated libodsstream package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 30 Apr 2020 16:19:46 +0200
Source: libodsstream
Binary: libodsstream-dev libodsstream-doc libodsstream-qt5-0 
libodsstream-qt5-dev libodsstream0 libodsstream0-dbgsym ods2tsv ods2tsv-dbgsym
Architecture: source amd64 all
Version: 0.7.8-1
Distribution: unstable
Urgency: low
Maintainer: The Debichem Group 
Changed-By: Filippo Rusconi 
Description:
 libodsstream-dev - C++ library to read or write ODS files (development files)
 libodsstream-doc - doxygen documentation of the ODSstream library
 libodsstream-qt5-0 - transitional package
 libodsstream-qt5-dev - transitional package
 libodsstream0 - C++ library to read or write ODS files
 ods2tsv- ODS to TSV file converter
Closes: 959637
Changes:
 

Processed: Re: broadcom-sta-dkms: Wl driver 6.30.223.271 (r587334) failed with code 21

[Debian Bug Tracking System]

Processing control commands:

> notfixed -1 6.30.223.271-14
Bug #959002 [broadcom-sta-dkms] broadcom-sta-dkms: Wl driver 6.30.223.271 
(r587334) failed with code 21
No longer marked as fixed in versions broadcom-sta/6.30.223.271-14.
> severity -1 important
Bug #959002 [broadcom-sta-dkms] broadcom-sta-dkms: Wl driver 6.30.223.271 
(r587334) failed with code 21
Severity set to 'important' from 'grave'

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

Bug#959002: broadcom-sta-dkms: Wl driver 6.30.223.271 (r587334) failed with code 21

[Roger Shimizu]

control: notfixed -1 6.30.223.271-14
control: severity -1 important

Dear Gert,

Please CC me when you reply.
Thank you!

> bullseye:
> status installed broadcom-sta-dkms:all 6.30.223.271-14
> buster-backports:
> status installed broadcom-sta-dkms:all 6.30.223.271-14~bpo10+1
> This also did not work with same errors.
> At the buster-backports version I tried the command dpkg-reconfigure
> broadcom-sta-dkms , that gave same errors.
> Also restarts did not help.

I thought you worked well with previous version, but failed with new
version, so marked this ticket as grave.
Now I understand your report is not about a regression.
So lower the severity.

All hardware I have still work well with latest version
(6.30.223.271-14), so I think your hardware may be not supported by
this driver.
We cannot say whether a specific hardware is supported by this driver
or not, until we tried it.

> I have no idea this has some relation, but at April a new version of
> wireless-regdb is upgraded with lot of changes.

If you can modprobe the driver sucessfully, but have problem
connecting to some Wifi AP, it may be related to wireless-regdb.
So I don't think it matters for your case.

> I do not understand why this problem is marked as fixed at
> 6.30.223.271-14, because this just is the version I used when I got the
> problem.

Sorry, I mistook your problem for another one.
So I update the flag this time.

> Is my device not supported and broadcom-sta-dkms:all 6.30.223.271-14
> working without problem for other devices?

I guess so, and you'd better try other drivers listed on wiki:
- https://wiki.debian.org/bcm43xx
- https://wiki.debian.org/brcm80211
- https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx

> In that case perhaps the installation Wiki should be updated to show the
> exceptions?

I'm afraid that's not possible because only the hardware vendor can decide such.
And usually package maintainer don't have all hardware ..

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#959637: Please provide pristine-tar for libodsstream - or at least way to get upstream source (Was: Bug#959637: beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

[Filippo Rusconi]

Greetings, Andreas,

I hope you are doing fine in these difficult times.

On Tue, May 05, 2020 at 02:25:58PM +0200, Andreas Tille wrote:

Hi Filippo,

I tried to investigate this issue of beads:

On Sun, May 03, 2020 at 02:34:20PM +0200, Lucas Nussbaum wrote:

During a rebuild of all packages in sid, your package failed to build
on amd64.
...
Relevant part (hopefully):
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libodsstream-qt5-dev but it is 
not going to be installed


and checked the salsa repository of libodsstream[1].  I was running
routine-update on it and when it tried to build the package it was
unable to find the original source tarball in pristine-tar branch.
There is no watch file and I failed to find any other hint how to obtain
the upstream source.

Would you mind writing a working watch file or at least inject
pristine-tar to enable others building right from Salsa?


Thank you so much for your report. Yeah, I forgot to gbp import-orig. The git
repos I was working on did not have one, oddly enough.

I am currently fixing that issue. Will be uploading in the next minutes and
closing the bug, and pushing to salsa.

Now, the beads project depends on libodsstream, but Olivier failed to recall me
of it. So it almost certainly will fail using libodsstream because I have
totally rewritten the CMake build system. CMake dialect variable names most
probably differ in libodsstream and beads. 


I'll give a look at it.

Ciao
Filippo

--

⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
⣾⠁⢠⠒⠀⣿⡁   Research scientist at CNRS
⢿⡄⠘⠷⠚⠋⠀   Debian Developer
⠈⠳⣄  http://msxpertsuite.org
  http://www.debian.org

Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

[Elimar Riesebieter]

There are official patches from saltstack available here:

2018.3.x 
2017.7.x 
2016.x.x 

I requested them via
https://www.saltstack.com/lp/request-patch-april-2020/

Please notice that there are more CVE' not fixed yet:

CVE-2019-17361 => 2016.11.2+ds-1+deb9u2 and 2018.3.4+dfsg1-6
CVE-2019-1010259 => 2016.11.2+ds-1+deb9u2
CVE-2018-15751 => 2016.11.2+ds-1+deb9u2

See https://security-tracker.debian.org/tracker/source-package/salt.

I asked saltstack for patches of those as well.

HTH
Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

Bug#949222: Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

[Simon McVittie]

On Tue, 05 May 2020 at 17:37:53 +0200, Salvatore Bonaccorso wrote:
> Do you have respective stretch and buster setups which you could
> expose those packages to?

Sorry, no: the owner of the machines I was looking at asked me to switch
over to upstream's packages.

smcv

Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

[Aaron M. Ucko]

Andreas Tille  writes:

> I've checked ncbi-blast+ and your last upload does not seem to be
> pushed.

AFAICT, it's all properly at https://salsa.debian.org/med-team/ncbi-blastplus.

> Since there is a strong relation in time with your upload and this
> FTBFS of biopython do you think that this could be connected:

Yes, per https://www.ncbi.nlm.nih.gov/books/NBK131777/, the upgrade to
2.10.0 changed the default database version (controlled by makeblastdb's
-blastdb_version flag) from 4 to 5, causing some output files to change
names (and formats):

*.nsd -> *.nnd
*.nsi -> *.nni
*.psd -> *.pnd
*.psi -> *.pni

Thanks for checking!

BTW, python-biopython's build dependency on emboss reminded me that
emboss-data is still probably overkill for emboss(-lib)'s needs and
could stand to be split up (#682042).

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#949222: Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

[Salvatore Bonaccorso]

Hi Simon,

On Tue, May 05, 2020 at 03:01:45PM +0100, Simon McVittie wrote:
> On Mon, 04 May 2020 at 01:34:33 +0200, Guilhem Moulin wrote:
> >   CVE-2020-11651
> >   CVE-2020-11652
> 
> I found myself needing to mitigate this for a salt deployment, so I
> tried backporting the upstream patches to buster.
> 
> The attached are not at all thoroughly-tested and should be reviewed
> carefully by someone who knows the codebase, but they seem to work, and
> the proof-of-concept from
> https://github.com/rossengeorgiev/salt-security-backports no longer reports
> that the master is vulnerable. This was only a stopgap, because that
> deployment is now using the packages from saltstack.com instead, but it
> might be useful to the salt maintainers.
> 
> There are also unofficial backports in
> https://github.com/rossengeorgiev/salt-security-backports - I tried doing
> the cherry-picks myself and then compared what I got with those, in an
> attempt to guard against mistakes (by either myself or the author of those
> backports).
> 
> Note that patch 0003 contains unofficial workarounds for regressions in the
> release that fixed those CVEs, which you might prefer to exclude from an
> official update.

I did actually work on that already yesterday and uploaded the
attached debdiffs to security-master *but* I'm in need of someone
using salt to effectively ina good way to test them. 

Do you have respective stretch and buster setups which you could
expose those packages to?

Regards,
Salvatore
diff -Nru salt-2016.11.2+ds/debian/changelog salt-2016.11.2+ds/debian/changelog
--- salt-2016.11.2+ds/debian/changelog  2018-04-20 14:33:54.0 +0200
+++ salt-2016.11.2+ds/debian/changelog  2020-05-04 14:29:16.0 +0200
@@ -1,3 +1,14 @@
+salt (2016.11.2+ds-1+deb9u3) stretch-security; urgency=high
+
+  * Non-maintainer upload by the Security Team.
+  * Address CVE-2020-11651 and CVE-2020-11652 (Closes: #959684)
+Thanks to Daniel Wozniak 
+  * Add note about log messages to hardening salt docs
+  * salt-api NET API with the ssh client enabled is vulnerable to command
+injection (CVE-2019-17361) (Closes: #949222)
+
+ -- Salvatore Bonaccorso   Mon, 04 May 2020 14:29:16 +0200
+
 salt (2016.11.2+ds-1+deb9u2) stretch; urgency=medium
 
   * Fix CVE-2017-8109: salt-ssh minion copied over configuration from the
diff -Nru 
salt-2016.11.2+ds/debian/patches/Add-note-about-log-messages-to-hardening-salt-docs.patch
 
salt-2016.11.2+ds/debian/patches/Add-note-about-log-messages-to-hardening-salt-docs.patch
--- 
salt-2016.11.2+ds/debian/patches/Add-note-about-log-messages-to-hardening-salt-docs.patch
   1970-01-01 01:00:00.0 +0100
+++ 
salt-2016.11.2+ds/debian/patches/Add-note-about-log-messages-to-hardening-salt-docs.patch
   2020-05-04 14:29:16.0 +0200
@@ -0,0 +1,41 @@
+From: "Daniel A. Wozniak" 
+Date: Mon, 13 Apr 2020 07:01:07 +
+Subject: Add note about log messages to hardening salt docs
+Origin: 
https://github.com/saltstack/salt/commit/4631781376ddc9ee9d279f407ac3d0b78644fae7
+
+---
+ doc/topics/hardening.rst | 4 
+ salt/master.py   | 2 +-
+ 2 files changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/doc/topics/hardening.rst b/doc/topics/hardening.rst
+index c645b84128e4..569ad654af69 100644
+--- a/doc/topics/hardening.rst
 b/doc/topics/hardening.rst
+@@ -57,6 +57,10 @@ Salt hardening tips
+   particularly sensitive minions. There is also :ref:`salt-ssh` or the
+   :mod:`modules.sudo ` if you need to further restrict
+   a minion.
++- Monitor specific security releated log messages. Salt ``salt-master`` logs
++  attempts to access methods which are not exposed to network clients. These 
log
++  messages are logged at the ``error`` log level and start with ``Requested
++  method not exposed``.
+ 
+ .. _salt-users: https://groups.google.com/forum/#!forum/salt-users
+ .. _salt-announce: https://groups.google.com/forum/#!forum/salt-announce
+diff --git a/salt/master.py b/salt/master.py
+index 7d1444cf1221..aae55f1828e1 100644
+--- a/salt/master.py
 b/salt/master.py
+@@ -1162,7 +1162,7 @@ class TransportMethods(object):
+ try:
+ return getattr(self, name)
+ except AttributeError:
+-log.error("Expose method not found: %s", name)
++log.error("Requested method not exposed: %s", name)
+ else:
+ log.error("Requested method not exposed: %s", name)
+ 
+-- 
+2.20.1
+
diff -Nru 
salt-2016.11.2+ds/debian/patches/Fix-CVE-2020-11651-and-Fix-CVE-2020-11652-2016.11.2.patch
 
salt-2016.11.2+ds/debian/patches/Fix-CVE-2020-11651-and-Fix-CVE-2020-11652-2016.11.2.patch
--- 
salt-2016.11.2+ds/debian/patches/Fix-CVE-2020-11651-and-Fix-CVE-2020-11652-2016.11.2.patch
  1970-01-01 01:00:00.0 +0100
+++ 
salt-2016.11.2+ds/debian/patches/Fix-CVE-2020-11651-and-Fix-CVE-2020-11652-2016.11.2.patch
  2020-05-04 14:29:16.0 +0200
@@ -0,0 +1,237 @@
+From 006219501bbb3a81a9fb64975035011016d5a7eb Mon Sep 17 

Bug#959364: PR with patch

[Gard Spreemann]

Oops, I was a bit careless. Let me clarify: the patch in my PR is not
from the actual upstream for the package, but rather from the fork [1]
linked to by Thomas Koch in #959729 [2].

[1] https://github.com/teleshoes/acpi_call

[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959729#10

Bug#948706: greylistd: python3 version fails to start - conversion from python 2 very broken

[Benedikt Spranger]

Followup-For: Bug #948706
Package: greylistd
Version: 0.8.8.8
Tags: patch

Hi,
I run into the very same problems while setting up a system. Since I
found some spare cycles I looked at the code and made some patches.

For simpler development I have set up a git repo and have import the
packages found on snapshots.debian.org to provide a package history.

You can find the git repo under 

https://github.com/eurovibes/greylistd

Regards
Bene Spranger
>From 376957c38203c951b9b6071c4ebfc13139d3ab2c Mon Sep 17 00:00:00 2001
From: Benedikt Spranger 
Date: Mon, 4 May 2020 00:25:24 +0200
Subject: [PATCH 01/10] Conciliate indentation

greylistd-setup-exim4 fail with
TabError: inconsistent use of tabs and spaces in indentation

Untabify greylistd-setup-exim4.

Signed-off-by: Benedikt Spranger 
---
 program/greylistd-setup-exim4 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/program/greylistd-setup-exim4 b/program/greylistd-setup-exim4
index a8c467a..821670c 100755
--- a/program/greylistd-setup-exim4
+++ b/program/greylistd-setup-exim4
@@ -1,7 +1,7 @@
 #!/usr/bin/python3
 
-### FILE:	greylist-setup-exim4
-### PURPOSE:	Add a greylisting statement to Exim 4 configuration file
+### FILE:   greylist-setup-exim4
+### PURPOSE:Add a greylisting statement to Exim 4 configuration file
 
 
 from sys   import version, stdin, stderr, argv, exit
@@ -251,7 +251,7 @@ def exim4_configure (lines, aclname, options):
 try:
 netmask = int(options["netmask"])
 except:
-	nmstring=options["netmask"]
+nmstring=options["netmask"]
 raise RuntimeError("Invalid netmask size: '%(nmstring)s'"%vars())
 ### org   raise "Invalid netmask size: '%s'"%options["netmask"]
 
-- 
2.26.0.rc2

>From 5265e1c4c346567334d10370f0f81c366e3a865f Mon Sep 17 00:00:00 2001
From: Benedikt Spranger 
Date: Mon, 4 May 2020 14:55:55 +0200
Subject: [PATCH 02/10] Ensure python 3.6 or greater

The greylistd package switched to Python 3 and uses some features
introduced in Python 3.6. Update the version check to fit.

Signed-off-by: Benedikt Spranger 
---
 program/greylistd-setup-exim4 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/program/greylistd-setup-exim4 b/program/greylistd-setup-exim4
index 821670c..5ddc1fa 100755
--- a/program/greylistd-setup-exim4
+++ b/program/greylistd-setup-exim4
@@ -10,8 +10,8 @@ from osimport listdir, spawnl, P_WAIT
 from reimport compile
 
 ### Ensure that we can run this program
-if version < "2.3":
-stderr.write("This program requires Python 2.3 or newer\n")
+if version < "3.6":
+stderr.write("This program requires Python 3.0 or newer\n")
 exit(1)
 
 
-- 
2.26.0.rc2

>From ed347398c93602b59e4dcea0998d9f13cc6447f1 Mon Sep 17 00:00:00 2001
From: Benedikt Spranger 
Date: Mon, 4 May 2020 00:56:36 +0200
Subject: [PATCH 03/10] Remove trailing whitespaces

Perform a overall code cleanup by removing trailing whitespaces.
No functional change.

Signed-off-by: Benedikt Spranger 
---
 program/greylist  |  4 +---
 program/greylistd | 24 +++-
 program/greylistd-setup-exim4 | 12 ++--
 3 files changed, 18 insertions(+), 22 deletions(-)

diff --git a/program/greylist b/program/greylist
index 2603a33..88050d8 100755
--- a/program/greylist
+++ b/program/greylist
@@ -46,7 +46,6 @@ sockfile = "/var/run/greylistd/socket"
 commands = ("add", "delete", "check", "update",
 "stats", "list",  "clear", "save",
 "reload", "mrtg")
-
 
 
 def usage (progname, message=None):
@@ -114,7 +113,6 @@ elif not action in commands:
 usage(progname, "Invalid action: '%s'"%action)
 
 
-
 confParser = ConfigParser()
 confParser.read(conffile)
 try:
@@ -149,7 +147,7 @@ while stat:
 
 except IOError:
 break
-
+
 else:
 if not firstword and stat.strip():
 firstword = stat.split(None, 1)[0]
diff --git a/program/greylistd b/program/greylistd
index 58348b6..906dfab 100755
--- a/program/greylistd
+++ b/program/greylistd
@@ -3,10 +3,10 @@
 ### FILE:	greylistd.py
 ### PURPOSE:	Simple greylisting daemon.  See "greylistd(8)".
 ###		For an introduction to greylisting, see:
-### 		http://projects.puremagic.com/greylisting/
+###		http://projects.puremagic.com/greylisting/
 ###
-### 		This program listens for connections on a UNIX domain
-###		socket, presumably from an MTA such as Exim.  Nominally, 
+###		This program listens for connections on a UNIX domain
+###		socket, presumably from an MTA such as Exim.  Nominally,
 ###		it reads an identifier (referred to as a "triplet"),
 ###		and returns a single word ("white" or "grey") depending
 ### on prior knowledge of said identifier.
@@ -270,7 +270,7 @@ def saveToFile (datafile, dictionary, perm=0600):

Bug#958798: marked as done (cpufreqd: FTBFs on ppc64el)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 14:48:31 +
with message-id 
and subject line Bug#958798: fixed in cpufreqd 2.4.2-2.3
has caused the Debian Bug report #958798,
regarding cpufreqd: FTBFs on ppc64el
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.)


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

cpufreqd failed to build on ppc64el:
https://buildd.debian.org/status/fetch.php?pkg=cpufreqd=ppc64el=2.4.2-2.2%2Bb2=1587771408=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cpufreqd
Source-Version: 2.4.2-2.3
Done: =?utf-8?b?RnLDqWTDqXJpYyBCb25uYXJk?= 

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

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

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

Debian distribution maintenance software
pp.
Frédéric Bonnard  (supplier of updated cpufreqd 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, 05 May 2020 16:12:20 +0200
Binary: cpufreqd cpufreqd-dbgsym
Source: cpufreqd
Architecture: ppc64el source
Version: 2.4.2-2.3
Distribution: unstable
Urgency: medium
Maintainer: Mattia Dongili 
Changed-By: Frédéric Bonnard 
Closes: 958798
Description: 
 cpufreqd   - fully configurable daemon for dynamic frequency and voltage scali
Changes:
 cpufreqd (2.4.2-2.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build on power : call to libcpupower *available_frequencies
 functions can be made directly since kernel 5.6.7 (Closes: #958798).
Checksums-Sha1: 
 4905cc818f88fd71766f95fdb3e2e6499dd08ea9 2020 cpufreqd_2.4.2-2.3.dsc
 82153a8de7b69e389865db8710a02f31f54fb29b 11816 cpufreqd_2.4.2-2.3.debian.tar.xz
 3330a3426942ca01eaa8eb1a3c9cea77a8299f85 141260 
cpufreqd-dbgsym_2.4.2-2.3_ppc64el.deb
 b2bc46763ca84ee2fead9f16d2bdd568f7499229 5868 
cpufreqd_2.4.2-2.3_ppc64el.buildinfo
 db3ac1dda881fbc5fdabeec7da98a0ed67bae3a4 79644 cpufreqd_2.4.2-2.3_ppc64el.deb
Checksums-Sha256: 
 873115b9ac8a66c6fd1284d6ceb71c4d1cc38948f673cd5f6356fe93be124cc4 2020 
cpufreqd_2.4.2-2.3.dsc
 49341e361f6836de2d9d8bcc5f820af5f2165592ad9202b672a9f9867f7d62c7 11816 
cpufreqd_2.4.2-2.3.debian.tar.xz
 afd179abf185df846cb41665e2bc3a99208e03b1ebac34ff378bec8b8a7de709 141260 
cpufreqd-dbgsym_2.4.2-2.3_ppc64el.deb
 5c03de9c8eb7e4c768472668c193478a53e98ee8c7bfd7a39a0e40706eec82e7 5868 
cpufreqd_2.4.2-2.3_ppc64el.buildinfo
 cd21942a61742392c2a2f4b5fbaa298758cf2bc1b254cd91a2e6a36a533e2860 79644 
cpufreqd_2.4.2-2.3_ppc64el.deb
Files: 
 2078966b0b11384e2b3979959c98c696 2020 admin optional cpufreqd_2.4.2-2.3.dsc
 3a20e8c487e160a88419ec304b5480c2 11816 admin optional 
cpufreqd_2.4.2-2.3.debian.tar.xz
 a70dfbc230670a51b303ff02ae605eab 141260 debug optional 
cpufreqd-dbgsym_2.4.2-2.3_ppc64el.deb
 5fbb78892684dfa59442a35a055bf8a0 5868 admin optional 
cpufreqd_2.4.2-2.3_ppc64el.buildinfo
 710bdabf1ed952174700c539302cb372 79644 admin optional 
cpufreqd_2.4.2-2.3_ppc64el.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEh9vVdWFVIC7DiF6Ta3SY/LmzWKwFAl6xd+ESHGZyZWRpekBk
ZWJpYW4ub3JnAAoJEGt0mPy5s1iskVYP/0YdFQSHpOze4dS2kMXcyQBCq/eiGmi7
VrH9Zx7iv6AxqZNySu5YMF8QNE/BXitCAoGkpuFc++siA9oZiic/FY2WTF/44GS0
ogPrkdVSM6j6wr593tOBVFir8SIjCn8P9it10KT8qLJZX3mAiy1IwoWc6q4/m47s
S65L6x4wqd4JKHgj2XjT5EHRkxa2WDk8GlnSlditVq2TNlf5jLeBlc1/pW4CAyRe
syW6tjtOGtcu4ZhRHDTPgL+mxbCZAhAuJWS1G2Zm3/nbZurRrTkevvZldx9htG3/
QM9s38iJmCCtmDdPML/YDHRR5bnYX3y7BQE3Rj7ULmAvBgl1Jj0c3FqwDnU8y1Vo
8L0v8OAmG2rNKat+pkDnS6Q8zkEDapU59CempeI8FcPXb+FYEG/EaTpMaT2S2ool
Jcis3qt8BDM2Ve9XHVRbwe89v/lfcCgVP+xqJp05/QMFDsv/wrjPEU1PKfeEu8eH
mtjrPHbLhsar9gwIrjsKv64WViWfSfxxdCmTC3m8lxRVJT7RUCTC7P2OWDiPpYmc
yhjqJNwF/Hxw9Qt6ezw4W4dInJ0f4wwqcJJjYntICDJ9f1wYW7xmSaEf4EIl0t80
2+kfnaeOWeQEewekApgt8koAGcMYVvcoD95aIvTbO5UMi6I1dp/AZjGxfRYbnfmk
v043x5G0XFA9
=ZM9m
-END PGP SIGNATURE End Message ---

Processed: The matplotlib problem was a temporary problem during the Python 3.7 -> 3.8 transiton

[Debian Bug Tracking System]

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

> severity 955656 important
Bug #955656 {Done: Andreas Tille } [src:python-cobra] 
python-cobra: FTBFS: E   ModuleNotFoundError: No module named 'matplotlib'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#949222: Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

[Simon McVittie]

On Mon, 04 May 2020 at 01:34:33 +0200, Guilhem Moulin wrote:
>   CVE-2020-11651
>   CVE-2020-11652

I found myself needing to mitigate this for a salt deployment, so I
tried backporting the upstream patches to buster.

The attached are not at all thoroughly-tested and should be reviewed
carefully by someone who knows the codebase, but they seem to work, and
the proof-of-concept from
https://github.com/rossengeorgiev/salt-security-backports no longer reports
that the master is vulnerable. This was only a stopgap, because that
deployment is now using the packages from saltstack.com instead, but it
might be useful to the salt maintainers.

There are also unofficial backports in
https://github.com/rossengeorgiev/salt-security-backports - I tried doing
the cherry-picks myself and then compared what I got with those, in an
attempt to guard against mistakes (by either myself or the author of those
backports).

Note that patch 0003 contains unofficial workarounds for regressions in the
release that fixed those CVEs, which you might prefer to exclude from an
official update.

smcv
>From f17495581f0d7cc7bb94fa2c1f97517d16e2dd7a Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Mon, 4 May 2020 12:39:29 +0100
Subject: [PATCH 1/4] Apply upstream patch for CVE-2019-17361

Signed-off-by: Simon McVittie 
Closes: #949222
---
 .../0003-Use-renamed-python3-tornado4.patch   | 185 ++--
 ...17361-various-netapi-fixes-and-tests.patch | 280 ++
 debian/patches/series |   1 +
 3 files changed, 376 insertions(+), 90 deletions(-)
 create mode 100644 debian/patches/CVE-2019-17361-various-netapi-fixes-and-tests.patch

diff --git a/debian/patches/0003-Use-renamed-python3-tornado4.patch b/debian/patches/0003-Use-renamed-python3-tornado4.patch
index 01ad3154bf..1f0878a7a0 100644
--- a/debian/patches/0003-Use-renamed-python3-tornado4.patch
+++ b/debian/patches/0003-Use-renamed-python3-tornado4.patch
@@ -1,54 +1,53 @@
-From d17823525d0842ea3e643b024714643b4949ec1b Mon Sep 17 00:00:00 2001
 From: Benjamin Drung 
 Date: Mon, 17 Dec 2018 20:35:19 +0100
 Subject: [PATCH 3/3] Use renamed python3-tornado4
 
 ---
- doc/conf.py   | 17 
- salt/client/__init__.py   |  5 +++-
- salt/client/mixins.py |  5 +++-
- salt/crypt.py | 11 +---
- salt/engines/ircbot.py|  8 --
- salt/engines/webhook.py   | 11 +---
- salt/fileclient.py|  5 +++-
- salt/master.py|  5 +++-
- salt/minion.py| 17 
- salt/netapi/rest_tornado/__init__.py  | 13 +++---
- salt/netapi/rest_tornado/saltnado.py  | 20 +-
- .../rest_tornado/saltnado_websockets.py   |  9 ---
- salt/pillar/__init__.py   |  5 +++-
- salt/transport/client.py  |  9 +--
- salt/transport/ipc.py | 23 +++-
- salt/transport/mixins/auth.py |  5 +++-
- salt/transport/tcp.py | 26 +--
- salt/transport/zeromq.py  | 20 +-
- salt/utils/asynchronous.py|  8 --
- salt/utils/event.py   |  8 --
- salt/utils/gitfs.py   |  5 +++-
- salt/utils/http.py| 11 +---
- salt/utils/process.py |  5 +++-
- salt/utils/thin.py|  5 +++-
- salt/utils/zeromq.py  |  8 --
- salt/version.py   | 10 +--
- tests/integration/__init__.py |  8 --
- .../files/engines/runtests_engine.py  |  8 +++---
- tests/integration/modules/test_gem.py |  5 +++-
- tests/integration/modules/test_ssh.py |  5 +++-
- tests/support/helpers.py  |  8 --
- tests/unit/fileserver/test_gitfs.py   |  5 +++-
- tests/unit/modules/test_random_org.py |  5 +++-
- tests/unit/netapi/test_rest_tornado.py| 20 +-
- tests/unit/test_minion.py | 18 +
- tests/unit/transport/test_ipc.py  | 11 +---
- tests/unit/transport/test_tcp.py  | 14 +++---
- tests/unit/transport/test_zeromq.py   | 13 --
- tests/unit/utils/test_asynchronous.py | 11 +---
- tests/unit/utils/test_context.py  | 11 +---
- tests/unit/utils/test_event.py|  5 +++-
- 41 files changed, 314 insertions(+), 107 deletions(-)
+ doc/conf.py| 17 ++
+ salt/client/__init__.py|  5 -
+ salt/client/mixins.py  |  5 -
+ salt/crypt.py  

Bug#959801: ropemode: Consider removing it from Debian

[Boyuan Yang]

Source: ropemode
Severity: serious
Version: 0.4-1
X-Debbugs-CC: python-modules-t...@lists.alioth.debian.org

Package ropemode has been orphaned by its original maintainer and is python2-
only. Perhaps it's time for us to have it removed from Debian.

Package ropemode has no reverse dependencies or reverse build-dependencies.

I will submit a removal request 21 days later (After May 26, 2020) in hope
that someone may pick up this package and migrate it to python3.

-- 
Thanks,
Boyuan Yang


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

Processed: Re: Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #959783 [src:util-linux] util-linux: 2.35.1-1 FTBFS in pbuilder chroot: 
testsuite fails in misc/fallocate and misc/mountpoint
Severity set to 'important' from 'serious'
> tags -1 + upstream
Bug #959783 [src:util-linux] util-linux: 2.35.1-1 FTBFS in pbuilder chroot: 
testsuite fails in misc/fallocate and misc/mountpoint
Added tag(s) upstream.

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

Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

[Chris Hofstaedtler]

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

Hi Mark Hindley,

thanks for your report. See below.

* Mark Hindley  [200505 13:27]:
> Unfortunately the testsuite fails when building in a pbuilder/cowbuilder
> chroot. In particular misc/fallocate and misc/mountpoint.
> 
> The issues appear to be:
> 
>  misc/fallocate: the expected failure case has not been migrated to the new 
> test
>framework with clear separation of stdout and stderr.

Could you put this into a patch that has the proper Signed-off-by
headers so this can be fixed upstream, please?

>  misc/mountpoint: This assumes / is a mountpoint which is not the case in a
> chroot.
> 
> Patches addressing both of these failures are below. However, I am aware that
> using /proc as the test mountpoint is a linux only solution, so you may well
> prefer another approach.

Well, as long as we are trading implementation details, I'd rather
stay with something that already works within sbuild and on the
buildd network.

> Thanks.
> 
> Mark

Best,
Chris

Bug#938846: xia: Python2 removal in sid/bullseye

[François Lafont]

Hi,

On 5/5/20 11:17 AM, Moritz Muehlenhoff wrote:


See 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#removing-packages


Thx for the link. I think the bug report has been sent.
Bye.

--
François Lafont

Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

[Andreas Tille]

Hi Aaron,

I've checked ncbi-blast+ and your last upload does not seem to be
pushed.

Since there is a strong relation in time with your upload and this
FTBFS of biopython do you think that this could be connected:

On Sun, May 03, 2020 at 02:43:59PM +0200, Lucas Nussbaum wrote:
> > ==
> > FAIL: test_fasta_db_nucl (test_NCBI_BLAST_tools.BlastDB)
> > Test makeblastdb wrapper with nucleotide database.
> > --
> > Traceback (most recent call last):
> >   File 
> > "/<>/.pybuild/cpython3_3.8/build/Tests/test_NCBI_BLAST_tools.py",
> >  line 248, in test_fasta_db_nucl
> > self.assertTrue(os.path.isfile("GenBank/NC_005816.fna.nsd"))
> > AssertionError: False is not true
> > 
> > ==
> > FAIL: test_fasta_db_prot (test_NCBI_BLAST_tools.BlastDB)
> > Test makeblastdb wrapper with protein database.
> > --
> > Traceback (most recent call last):
> >   File 
> > "/<>/.pybuild/cpython3_3.8/build/Tests/test_NCBI_BLAST_tools.py",
> >  line 213, in test_fasta_db_prot
> > self.assertTrue(os.path.isfile("GenBank/NC_005816.faa.psd"))
> > AssertionError: False is not true
> > 
> > --
> > Ran 519 tests in 222.972 seconds
> > 
> > FAILED (failures = 1)

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#959637: Please provide pristine-tar for libodsstream - or at least way to get upstream source (Was: Bug#959637: beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

[Andreas Tille]

Hi Filippo,

I tried to investigate this issue of beads:

On Sun, May 03, 2020 at 02:34:20PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> ...
> Relevant part (hopefully):
> > The following packages have unmet dependencies:
> >  sbuild-build-depends-main-dummy : Depends: libodsstream-qt5-dev but it is 
> > not going to be installed

and checked the salsa repository of libodsstream[1].  I was running
routine-update on it and when it tried to build the package it was
unable to find the original source tarball in pristine-tar branch.
There is no watch file and I failed to find any other hint how to obtain
the upstream source.

Would you mind writing a working watch file or at least inject
pristine-tar to enable others building right from Salsa?

Thanks a lot

   Andreas.

[1] https://salsa.debian.org/debichem-team/libodsstream

-- 
http://fam-tille.de

Bug#956675: cyvcf2: test failures on mipsel, ppc64el and s390x

[Andreas Tille]

Hi Adrian,

On Tue, May 05, 2020 at 10:17:30AM +0300, Adrian Bunk wrote:
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > 
> > cyvcf2 failed to build on mipsel (where it built before),
> >...
> 
> The mipsel failure is "FTBFS on Loongson", this needs blacklisting on 
> the Loongson buildds.

Thanks a lot for this hint.  Do I need to do this to get this happen?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#959590: marked as done (erlang-p1-tls: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile test returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 11:48:25 +
with message-id 
and subject line Bug#959590: fixed in erlang-p1-tls 1.1.5-2
has caused the Debian Bug report #959590,
regarding erlang-p1-tls: FTBFS: dh_auto_test: error: make --no-print-directory 
-f /usr/share/dh-rebar/make/dh-rebar.Makefile test returned exit code 2
to be marked as done.

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

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


-- 
959590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-p1-tls
Version: 1.1.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./configure
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether make sets $(MAKE)... yes
> checking for an ANSI C-conforming const... yes
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for stdlib.h... (cached) yes
> checking for GNU libc compatible malloc... yes
> checking for ANSI C header files... (cached) yes
> checking for erl... /usr/bin/erl
> checking for erlc... /usr/bin/erlc
> checking for SSL_free in -lssl... yes
> checking for SHA1_Init in -lcrypto... yes
> checking openssl/ssl.h usability... yes
> checking openssl/ssl.h presence... yes
> checking for openssl/ssl.h... yes
> checking openssl/err.h usability... yes
> checking openssl/err.h presence... yes
> checking for openssl/err.h... yes
> checking openssl/sha.h usability... yes
> checking openssl/sha.h presence... yes
> checking for openssl/sha.h... yes
> checking openssl/opensslv.h usability... yes
> checking openssl/opensslv.h presence... yes
> checking for openssl/opensslv.h... yes
> configure: creating ./config.status
> config.status: creating vars.config
> dh_auto_configure
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> configure
> make[2]: Nothing to be done for 'configure'.
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> build
> echo rebar_compile
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Evaluating config script "/<>/rebar.config.script"
> DEBUG: Consult config file "/<>/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file "/<>/src/fast_tls.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps  : []
> DEBUG: Plugins requested while processing /<>: []
> DEBUG: Predirs: []
> ==> erlang-p1-tls-1.1.5 (compile)
> DEBUG: Matched required ERTS version: 10.7.1 -> .*
> DEBUG: Matched required OTP release: 22 -> .*
> DEBUG: Min OTP version unconfigured
> DEBUG: erl_opts [debug_info,debug_info,{src_dirs,["src"]}]
> DEBUG: Files to compile first: []
> DEBUG: Starting 3 compile worker(s)
> DEBUG: Worker exited cleanly
> Compiled src/p1_sha.erl
> DEBUG: Worker exited cleanly
> Compiled src/fast_tls.erl
> DEBUG: Worker exited cleanly
> DEBUG: Skipping deps parse of c_src/fast_tls.d: enoent
> DEBUG: Last mod is 0 on c_src/fast_tls.o
> INFO:  sh info:
>   cwd: "/<>"
>   cmd: cc -c -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DHAS_ERTS_EXIT -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -g -Wall -fPIC -MMD  
> -I"/usr/lib/erlang/lib/erl_interface-3.13.2/include" 
> -I"/usr/lib/erlang/erts-10.7.1/include"   c_src/fast_tls.c -o c_src/fast_tls.o
> DEBUG:opts: [{env,[{"REBAR_DEPS_DIR",
>   "/<>/deps"},
>  {"ERL_LIBS",
>   "/<>/deps"},
>  

Processed: found 956083 in 1.0-5

[Debian Bug Tracking System]

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

> found 956083 1.0-5
Bug #956083 [autopostgresqlbackup] autopostgresqlbackup: Fails to detect when 
DB dumps fail, and saves useless backups
Marked as found in versions autopostgresqlbackup/1.0-5.
> thanks
Stopping processing here.

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

Processed: node-bash-match: Please remove dependency to node-cross-spawn

[Debian Bug Tracking System]

Processing control commands:

> block 958403 by -1
Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does 
risky path mangling, and does it wrong in current release 5.1.0
958403 was blocked by: 959788 959786 959784 959789 959785 959787
958403 was not blocking any bugs.
Added blocking bug(s) of 958403: 959790

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

Processed: node-bluebird: Please remove dependency to node-cross-spawn

[Debian Bug Tracking System]

Processing control commands:

> block 958403 by -1
Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does 
risky path mangling, and does it wrong in current release 5.1.0
958403 was blocked by: 959785 959787 959784 959786
958403 was not blocking any bugs.
Added blocking bug(s) of 958403: 959788

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

Processed: npm: Please remove dependency to node-cross-spawn

[Debian Bug Tracking System]

Processing control commands:

> block 958403 by -1
Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does 
risky path mangling, and does it wrong in current release 5.1.0
958403 was blocked by: 959784 959786 959787 959785 959788
958403 was not blocking any bugs.
Added blocking bug(s) of 958403: 959789

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

Processed: node-fbjs: Please remove dependency to node-cross-spawn

[Debian Bug Tracking System]

Processing control commands:

> block 958403 by -1
Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does 
risky path mangling, and does it wrong in current release 5.1.0
958403 was not blocked by any bugs.
958403 was not blocking any bugs.
Added blocking bug(s) of 958403: 959784

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

Processed (with 1 error): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 912504 src:pysycache
Bug #912504 [pysycache] pysycache: Please migrate to python3-pygame
Bug reassigned from package 'pysycache' to 'src:pysycache'.
Ignoring request to alter found versions of bug #912504 to the same values 
previously set
Ignoring request to alter fixed versions of bug #912504 to the same values 
previously set
> forcemerge 937553 912504
Bug #937553 [src:pysycache] pysycache: Python2 removal in sid/bullseye
Bug #912504 [src:pysycache] pysycache: Please migrate to python3-pygame
Severity set to 'serious' from 'wishlist'
937695 was blocked by: 945645 943050 938365 936498 938469 938328 937997 943007 
937549 936767 938219 936132 943257 936898 943302 936605 938127 936954 938579 
936312 936539 936161 937697 937048 936366 936570 912487 936474 938178 938072 
937385 938591 937508 936296 936892 937489 937148 937009 945653 936775 936318 
938735 938027 937042 938094 937259 938593 938834 937889 936736 938322 956334 
945651 938220 936337 938295 938377 943281 947501 936564 939115 938419 938315 
938373 936640 936738 938649 937748 936113 937679 943044 938819 938176 943287 
942909 942942 936298 938269 936810 936717 945657 936316 936111 936362 936984 
937355 937459 938076 938794 938420 943253 936325 943003 936274 943180 938608 
936167 938772 937691 938326 937304 936496 937993 938234 937742 938727 936514 
943144 936829 936761 937709 937791 938672 937233 938708 936632 943026 943115 
943173 937642 936105 936243 937609 937412 936661 937197 938858 937124 937398 
942930 937793 937231 938301 936932 942979 938694 937576 945639 937262 945670 
935208 936241 936154 938458 937942 936663 938546 937392 936447 936885 937523 
936938 937024 938006 938486 937268 937225 942991 937290 937437 936740 936847 
943126 937521 936917 938702 936485 938380 936638 947232 939487 945664 937648 
937730 937837 937418 936551 943214 942993 938256 938852 937779 938676 937431 
939483 936611 93 937462 936975 936913 936843 936936 937831 937433 936557 
938102 938008 937572 939481 937091 937266 938509 938488 942924 937527 938542 
936911 937946 936841 936443 937212 937816 937179 934870 936667 937191 938923 
936285 938049 938108 937396 938621 938002 936855 937578 937825 937079 937030 
937890 937218 937724 938921 938706 938350 937193 943122 936247 936804 945745 
938623 936455 936581 937425 937468 937329 938307 938856 938252 939103 937490 
937237 936714 938130 945654 938816 938212 937635 936561 938862 936170 937488 
937149 936473 938572 936319 943240 936532 938310 937102 938831 936645 937258 
938416 937888 938462 936873 943047 936815 936945 956333 936687 949572 938431 
938594 936228 937252 937307 938490 938237 936951 938425 945713 937286 936164 
938468 938329 938724 936222 937548 937456 938890 938797 937482 936899 937621 
945736 938578 936538 937923 937049 936426 936900 938216 943141 943254 937458 
937927 936511 938866 938262 938909 945684 938360 937694 936271 945738 938793 
945640 938231 938124 936957 936428 936536 936465 943143 938412 936513 937288 
938642 937627 943205 936657 936215 945717 943004 936273 936828 938233 937672 
936865 936114 938730 938837 938418 938779 936683 937256 937852 936739 938097 
938648 947302 936877 936981 943043 936770 938374 937749 939641 943104 937678 
936226 938521 938818 938437 938290 937452 936681 936299 938268 936477 943041 
936983 937006 945732 938392 938523 945661 942972 936939 937269 943198 937902 
937023 937819 937176 936187 945663 937135 936388 936783 936505 936670 938748 
937597 943213 942994 943275 937419 937021 937602 937373 937778 938709 937895 
938742 937727 937035 936700 937326 938289 936850 936757 937234 938691 938859 
938046 937495 942978 937420 936153 943192 937794 937076 943060 936450 937123 
935209 938355 943098 938459 945740 938693 938697 942976 936584 936751 937579 
937078 943232 945636 938924 937869 938502 943096 938549 953220 936358 939104 
936753 945675 936803 937328 937194 942935 937606 936181 937295 937377 936844 
936207 953219 942921 936914 946849 938746 937834 943217 937593 938347 938259 
937776 937094 936787 936880 945667 936183 936614 937027 938009 936444 937072 
938385 938489 943196 936745 936480 938557 937645 945624 937532 937415 936149 
937473 943166 937170 938184 936509 938613 943018 938675 938500 943279 943112 
938443 938841 936635 943230 937714 937265 937687 937945 937471 937815 936888 
936935 937563 943037 938611 938441 938843 937064 937222 937826 936921 936706 
942914 938455 938359 937499 937164 938581 937320 938754 936856 936307 937426 
937538 938285 936923 938040 883173 937899 936482 938705 943012 938583 946928 
945746 937039 936548 938084 937070 937465 937536 912491 937428 937271 938587 
942970 942939 936972 943090 945748 937764 936546 938663 936927 943068 937511 
938154 945630 937900 938241 943116 936303 936708 943133 936672 936994 933775 
937273 938632 938545 937657 936627 937600 936288 937513 936858 938661 938243 
938485 937334 936702 936678 938389 938847 938204 937822 938638 943033 942964 
936749 948846 937770 

Processed: node-foreground-child: Please remove dependency to node-cross-spawn

[Debian Bug Tracking System]

Processing control commands:

> block 958403 by -1
Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does 
risky path mangling, and does it wrong in current release 5.1.0
958403 was blocked by: 959784 959786 959785
958403 was not blocking any bugs.
Added blocking bug(s) of 958403: 959787

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

Processed: node-execa: Please remove dependency to node-cross-spawn

[Debian Bug Tracking System]

Processing control commands:

> block 958403 by -1
Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does 
risky path mangling, and does it wrong in current release 5.1.0
958403 was blocked by: 959785 959784
958403 was not blocking any bugs.
Added blocking bug(s) of 958403: 959786

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

Processed: node-node-sass: Please remove dependency to node-cross-spawn

[Debian Bug Tracking System]

Processing control commands:

> block 958403 by -1
Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does 
risky path mangling, and does it wrong in current release 5.1.0
958403 was blocked by: 959784
958403 was not blocking any bugs.
Added blocking bug(s) of 958403: 959785

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

Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

[Mark Hindley]

Source: util-linux
Version: 2.35.1-1
Severity: serious
Justification: FTBFS
Tags: patch

Dear Maintainer,

Thanks for packaging the new version of util-linux.

Unfortunately the testsuite fails when building in a pbuilder/cowbuilder
chroot. In particular misc/fallocate and misc/mountpoint.

The issues appear to be:

 misc/fallocate: the expected failure case has not been migrated to the new test
 framework with clear separation of stdout and stderr.

 misc/mountpoint: This assumes / is a mountpoint which is not the case in a
  chroot.

Patches addressing both of these failures are below. However, I am aware that
using /proc as the test mountpoint is a linux only solution, so you may well
prefer another approach.

Thanks.

Mark
--- a/tests/ts/misc/fallocate
+++ b/tests/ts/misc/fallocate
@@ -30,7 +30,7 @@
# fs type of $TS_OUTDIR, could be used to skip this test early
fs_type=$(${TS_CMD_FINDMNT} -n -o FSTYPE -T ${TS_OUTDIR})
 
-   grep -qi "fallocate: fallocate failed:.*not supported" $TS_OUTPUT \
+   grep -qi "fallocate: fallocate failed:.*not supported" $TS_ERRLOG \
&& ts_skip "'${fs_type}' not supported"
 fi
 
--- a/tests/ts/misc/mountpoint
+++ b/tests/ts/misc/mountpoint
@@ -8,15 +8,16 @@
 
 ts_check_test_command "$TS_CMD_MOUNTPOINT"
 
-ln -s / ./symlink-to-root
+# Use /proc: / is not a mountpoint in a build chroot.
+ln -s /proc ./symlink-to-proc
 
 ts_init_subtest "default"
-$TS_CMD_MOUNTPOINT ./symlink-to-root >> $TS_OUTPUT 2>> $TS_ERRLOG
+$TS_CMD_MOUNTPOINT ./symlink-to-proc >> $TS_OUTPUT 2>> $TS_ERRLOG
 echo $? >> $TS_OUTPUT 2>> $TS_ERRLOG
 ts_finalize_subtest
 
 ts_init_subtest "nofollow"
-$TS_CMD_MOUNTPOINT --nofollow ./symlink-to-root >> $TS_OUTPUT 2>> $TS_ERRLOG
+$TS_CMD_MOUNTPOINT --nofollow ./symlink-to-proc >> $TS_OUTPUT 2>> $TS_ERRLOG
 echo $? >> $TS_OUTPUT 2>> $TS_ERRLOG
 ts_finalize_subtest
 
@@ -25,5 +26,5 @@
 echo $? >> $TS_OUTPUT 2>> $TS_ERRLOG
 ts_finalize_subtest
 
-rm -f ./symlink-to-root
+rm -f ./symlink-to-proc
 ts_finalize
--- a/tests/expected/misc/mountpoint-default
+++ b/tests/expected/misc/mountpoint-default
@@ -1,2 +1,2 @@
-./symlink-to-root is a mountpoint
+./symlink-to-proc is a mountpoint
 0
--- a/tests/expected/misc/mountpoint-nofollow
+++ b/tests/expected/misc/mountpoint-nofollow
@@ -1,2 +1,2 @@
-./symlink-to-root is not a mountpoint
+./symlink-to-proc is not a mountpoint
 1

Bug#959775: marked as done (pycsw: FTBFS with sphinx 2.4)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 10:33:43 +
with message-id 
and subject line Bug#959775: fixed in pycsw 2.4.2+dfsg-3
has caused the Debian Bug report #959775,
regarding pycsw: FTBFS with sphinx 2.4
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.)


-- 
959775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pycsw
Version: 2.4.2+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

pycsw started to FTBFS when sphinx 2.4 reached sid:

[...]
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html # 
HTML generator
Running Sphinx v2.4.3
making output directory... done
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 31 source files that are out of date
updating environment: [new config] 31 added, 0 changed, 0 removed
reading sources... [  3%] administration
reading sources... [  6%] api
reading sources... [  9%] ckan
reading sources... [ 12%] committers
reading sources... [ 16%] configuration
reading sources... [ 19%] contributing
reading sources... [ 22%] csw-support
reading sources... [ 25%] distributedsearching
reading sources... [ 29%] docker
reading sources... [ 32%] geonode
reading sources... [ 35%] hhypermap
reading sources... [ 38%] index
reading sources... [ 41%] installation
reading sources... [ 45%] introduction
reading sources... [ 48%] json
reading sources... [ 51%] license
reading sources... [ 54%] migration-guide
reading sources... [ 58%] oaipmh
reading sources... [ 61%] odc
reading sources... [ 64%] opensearch
reading sources... [ 67%] outputschemas
reading sources... [ 70%] profiles
reading sources... [ 74%] repofilters
reading sources... [ 77%] repositories
reading sources... [ 80%] sitemaps
reading sources... [ 83%] soap
reading sources... [ 87%] sru
reading sources... [ 90%] support
reading sources... [ 93%] testing
reading sources... [ 96%] tools
reading sources... [100%] transactions

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  3%] administration

Theme error:
An error happened in rendering the page administration.
Reason: TemplateNotFound('i')
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/pycsw-2.4.2+dfsg'
make: *** [debian/rules:11: build] Error 2


Andreas


pycsw_2.4.2+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pycsw
Source-Version: 2.4.2+dfsg-3
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated pycsw 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, 05 May 2020 12:00:43 +0200
Source: pycsw
Binary: pycsw pycsw-wsgi python3-pycsw
Architecture: source all
Version: 2.4.2+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 pycsw  - OGC compliant metadata (Catalogue Service for the Web) server
 pycsw-wsgi - WSGI Apache CSW service based on pycsw
 python3-pycsw - OGC compliant metadata (Catalogue Service for the Web) server 
- P
Closes: 959775
Changes:
 pycsw (2.4.2+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop pycsw-doc package, FTBFS with sphinx 2.4.
 (closes: #959775)
Checksums-Sha1:
 2a5df79b4611703901e5e7143f991563fba33cda 2411 pycsw_2.4.2+dfsg-3.dsc
 f84a5231e13ded9489614bfa58545f2fbcd7d68d 17108 pycsw_2.4.2+dfsg-3.debian.tar.xz
 f61b680754ef9813f8852742a56f8e2adeb01664 125940 pycsw-wsgi_2.4.2+dfsg-3_all.deb
 d9c4be115286be69f191a0e98a65eee7e66145ba 20944 pycsw_2.4.2+dfsg-3_all.deb
 3dfc20abcbe3fcedfb8acab7e6fd258286e1d218 11415 
pycsw_2.4.2+dfsg-3_amd64.buildinfo
 f9f04d70f7d4cb5f627a7b4997f57a2756b2d8cf 245768 
python3-pycsw_2.4.2+dfsg-3_all.deb
Checksums-Sha256:
 

Bug#958901: marked as done (qreator does not start properly)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 10:05:39 +
with message-id 
and subject line Bug#958901: fixed in qreator 16.06.1-5
has caused the Debian Bug report #958901,
regarding qreator does not start properly
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.)


-- 
958901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qreator
Version: 16.06.1-3.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed qreator on my system (with a KDE desktop).

I started qreator but did not see any response or window popping up:


rd@h370:~/Downloads$ qreator -w
/usr/share/qreator/qreator_lib/Builder.py:21: PyGIWarning: Gtk was imported 
without specifying a version first. Use gi.require_version('Gtk', '3.0') before 
import to ensure that the right version gets loaded.
  from gi.repository import GObject, Gtk # pylint: disable=E0611
/usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py:18: PyGIWarning: 
GtkChamplain was imported without specifying a version first. Use 
gi.require_version('GtkChamplain', '0.12') before import to ensure that the 
right version gets loaded.
  from gi.repository import Gtk, GtkChamplain, Clutter, Champlain
/usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py:20: PyGIWarning: 
GtkClutter was imported without specifying a version first. Use 
gi.require_version('GtkClutter', '1.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import GtkClutter
/usr/share/qreator/qreator/qrcodes/QRCodeWifiGtk.py:20: PyGIWarning: NM was 
imported without specifying a version first. Use gi.require_version('NM', 
'1.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GLib, GdkPixbuf, NM
No handlers could be found for logger "qreator_lib"

I would have expected to see something similar to the windows shown here 
https://wiki.ubuntuusers.de/Qreator/


-- System Information:
Debian Release: 10.3
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (105, 
'proposed-updates'), (105, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages qreator depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  geoclue-2.0  2.5.2-1
ii  gir1.2-champlain-0.120.12.16-3
ii  gir1.2-clutter-1.0   1.26.2+dfsg-10
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-geoclue-2.0   2.5.2-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-gtkchamplain-0.12 0.12.16-3
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-nm-1.01.14.6-2+deb10u1
ii  python   2.7.16-1
ii  python-cairo 1.16.2-1+b1
ii  python-dbus  1.2.8-3
ii  python-gi3.30.4-1
ii  python-gi-cairo  3.30.4-1
ii  python-pil   5.4.1-2+deb10u1
ii  python-qrencode  1.2-4+b2
ii  python-requests  2.21.0-1
ii  python-vobject   0.9.6.1-0.1
ii  python-xdg   0.25-5

qreator recommends no packages.

qreator suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qreator
Source-Version: 16.06.1-5
Done: Chow Loong Jin 

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

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

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated qreator package)

(This message was generated 

Bug#955665: marked as done (ofxstatement-plugins: FTBFS: AssertionError: Failed doctest test for ofxstatement.plugins.tests.test_litas_esis.doctest_LitasEsisCsvStatementParser)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 10:05:19 +
with message-id 
and subject line Bug#955665: fixed in ofxstatement-plugins 20200505
has caused the Debian Bug report #955665,
regarding ofxstatement-plugins: FTBFS: AssertionError: Failed doctest test for 
ofxstatement.plugins.tests.test_litas_esis.doctest_LitasEsisCsvStatementParser
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd ofxstatement-otp && python3 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing src/ofxstatement_otp.egg-info/PKG-INFO
> writing dependency_links to src/ofxstatement_otp.egg-info/dependency_links.txt
> writing entry points to src/ofxstatement_otp.egg-info/entry_points.txt
> writing namespace_packages to 
> src/ofxstatement_otp.egg-info/namespace_packages.txt
> writing requirements to src/ofxstatement_otp.egg-info/requires.txt
> writing top-level names to src/ofxstatement_otp.egg-info/top_level.txt
> reading manifest file 'src/ofxstatement_otp.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'src/ofxstatement_otp.egg-info/SOURCES.txt'
> running build_ext
> 
> --
> Ran 0 tests in 0.000s
> 
> OK
> # run pytest with doctest and ignore exit code 5 (no tests found)
> cd ofxstatement-otp && PYTEST_ADDOPTS=--doctest-modules python3 setup.py 
> pytest; \
>   PYTEST_RESULT=$?; \
>   test $PYTEST_RESULT -eq 5 && exit 0; \
>   exit $PYTEST_RESULT
> running pytest
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing src/ofxstatement_otp.egg-info/PKG-INFO
> writing dependency_links to src/ofxstatement_otp.egg-info/dependency_links.txt
> writing entry points to src/ofxstatement_otp.egg-info/entry_points.txt
> writing namespace_packages to 
> src/ofxstatement_otp.egg-info/namespace_packages.txt
> writing requirements to src/ofxstatement_otp.egg-info/requires.txt
> writing top-level names to src/ofxstatement_otp.egg-info/top_level.txt
> reading manifest file 'src/ofxstatement_otp.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'src/ofxstatement_otp.egg-info/SOURCES.txt'
> running build_ext
> = test session starts 
> ==
> platform linux -- Python 3.8.2, pytest-4.6.9, py-1.8.1, pluggy-0.13.0
> rootdir: /<>/ofxstatement-otp
> collected 0 items
> 
> === warnings summary 
> ===
> src/ofxstatement/plugins/otp.py:143
>   /<>/ofxstatement-otp/src/ofxstatement/plugins/otp.py:143: 
> DeprecationWarning: invalid escape sequence \d
> re.compile('\d+\.\d+\.\d+ \d+'),
> 
> src/ofxstatement/plugins/otp.py:144
>   /<>/ofxstatement-otp/src/ofxstatement/plugins/otp.py:144: 
> DeprecationWarning: invalid escape sequence \d
> re.compile('[\d,]+EUR.*')
> 
> -- Docs: https://docs.pytest.org/en/latest/warnings.html
> == 2 warnings in 0.02 seconds 
> ==
> cd ofxstatement-mbank-sk && python3 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing src/ofxstatement_mbank.sk.egg-info/PKG-INFO
> writing dependency_links to 
> src/ofxstatement_mbank.sk.egg-info/dependency_links.txt
> writing entry points to src/ofxstatement_mbank.sk.egg-info/entry_points.txt
> writing na

Processed: Re: Bug#959775: pycsw: FTBFS with sphinx 2.4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #959775 [pycsw] pycsw: FTBFS with sphinx 2.4
Added tag(s) upstream.
> forwarded -1 https://github.com/geopython/pycsw/issues/609
Bug #959775 [pycsw] pycsw: FTBFS with sphinx 2.4
Set Bug forwarded-to-address to 'https://github.com/geopython/pycsw/issues/609'.

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

Bug#959775: pycsw: FTBFS with sphinx 2.4

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/geopython/pycsw/issues/609

Thanks for reporting this issue, I've forwarded it upstream.

Perhaps the issue is easy to fix, if not the docs will be removed at
least until this issue is fixed.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#938846: xia: Python2 removal in sid/bullseye

[Moritz Muehlenhoff]

On Tue, May 05, 2020 at 11:04:13AM +0200, François Lafont wrote:
> Hi,
> 
> On 5/4/20 10:54 PM, jmm@inutil.?Q?M=C3=BChlenhoff?= wrote:
> 
> > Can you please file a removal bug (reportbug ftp.debian.org), then? It can
> > still be reintroduced when ported to Python 3 at some point.
> 
> Currently I have no idea what is a "removal bug" but I'll search and proceed 
> after work.

See 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#removing-packages

Cheers,
Moritz

Bug#938846: xia: Python2 removal in sid/bullseye

[François Lafont]

Hi,

On 5/4/20 10:54 PM, jmm@inutil.?Q?M=C3=BChlenhoff?= wrote:


Can you please file a removal bug (reportbug ftp.debian.org), then? It can
still be reintroduced when ported to Python 3 at some point.


Currently I have no idea what is a "removal bug" but I'll search and proceed 
after work.

Regards.

--
François Lafont

Processed: Settings some additional flags to the closed bug...

[Debian Bug Tracking System]

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

> tags 959540 wontfix
Bug #959540 {Done: Ole Streicher } [src:scamp] scamp FTBFS 
on 32bit: test failures
Added tag(s) wontfix.
> severity 959540 normal
Bug #959540 {Done: Ole Streicher } [src:scamp] scamp FTBFS 
on 32bit: test failures
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#959473: orthanc-dicomweb build-dependencies unsatisfiable on armel

[Sébastien Jodogne]

Thanks for your in-depth analysis!

As this problem is way too involved given my understanding of the Debian
package management process, I have followed the simple path you provided
by requesting the removal of the armel binaries of orthanc-dicomweb:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959776

Bug#959540: marked as done (scamp FTBFS on 32bit: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 5 May 2020 10:38:13 +0200
with message-id 
and subject line Re: scamp FTBFS on 32bit: test failures
has caused the Debian Bug report #959540,
regarding scamp FTBFS on 32bit: 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.)


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

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

...
FAIL: test_chealpix
===

test_chealpix: test_chealpix.c:31: main: Assertion `neigh[j] == testneigh[j]' 
failed.
FAIL test_chealpix (exit status: 134)

FAIL: test_crossid_single_catalog
=

FAIL test_crossid_single_catalog (exit status: 139)

FAIL: test_crossid_single_catalog_moving


FAIL test_crossid_single_catalog_moving (exit status: 139)

FAIL: test_integration01.py
===


> WARNING: This executable has been compiled using a version of the ATLAS 
> library without support for multithreading. Performance will be degraded.

sh: 1: convert: not found

> WARNING: FLAGS parameter not found in catalog GAIA-DR1_1334+3754_r46.cat


> Could not allocate memory for fdata2 (npix2=268500992 elements) at line 125 
> in module fft.c !

/usr/lib/python3/dist-packages/astropy/config/configuration.py:557: 
ConfigurationMissingWarning: Configuration defaults will be used due to 
FileNotFoundError:2 on None
  warn(ConfigurationMissingWarning(msg))
Running Test #1 ...
SCAMP execution  ... failed
Traceback (most recent call last):
  File "./test_integration01.py", line 46, in 
contrast_as_min = np.amin(fields.array["AS_Contrast"])
  File "<__array_function__ internals>", line 5, in amin
  File "/usr/lib/python3/dist-packages/numpy/core/fromnumeric.py", line 2745, 
in amin
return _wrapreduction(a, np.minimum, 'min', axis, None, out,
  File "/usr/lib/python3/dist-packages/numpy/core/fromnumeric.py", line 88, in 
_wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
  File "/usr/lib/python3/dist-packages/numpy/ma/core.py", line 5640, in min
result = self.filled(fill_value).min(
  File "/usr/lib/python3/dist-packages/numpy/core/_methods.py", line 34, in 
_amin
return umr_minimum(a, axis, None, out, keepdims, initial, where)
ValueError: zero-size array to reduction operation minimum which has no identity
FAIL test_integration01.py (exit status: 1)


Testsuite summary for SCAMP 2.7.8

# TOTAL: 5
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  4
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to astroma...@astromatic.net

make[4]: *** [Makefile:781: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix
Control: severity -1 normal

Upstream does not provide 32 bit support any longer, and supporting it
is not easy. So, I asked to remove the 32 bit binaries from Debian;
otherwise this remains unfixed.

Best regards

Ole--- End Message ---

Bug#959772: game-data-packager: FTBFS with inkscape 1.0

[Simon McVittie]

Control: tags -1 + pending

On Tue, 05 May 2020 at 10:06:03 +0200, Andreas Beckmann wrote:
> game-data-packager started to FTBFS with inkscape 1.0

I believe this is already fixed in git.

smcv

Processed: Re: Bug#959772: game-data-packager: FTBFS with inkscape 1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #959772 [src:game-data-packager] game-data-packager: FTBFS with inkscape 1.0
Added tag(s) pending.

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

Bug#959772: game-data-packager: FTBFS with inkscape 1.0

[fabian]

Am 2020-05-05 10:06, schrieb Andreas Beckmann:

Unknown option --export-png=out/wolf-common.png
Unknown option --export-png=out/zork-inquisitor.png
Unknown option --export-png=out/grimfandango.png


Looks like this has been repleaced with the --export-type="png" option 
which doesn't take the filename of the output file anymore.


 - Fabian

Bug#959775: pycsw: FTBFS with sphinx 2.4

[Andreas Beckmann]

Package: pycsw
Version: 2.4.2+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

pycsw started to FTBFS when sphinx 2.4 reached sid:

[...]
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html # 
HTML generator
Running Sphinx v2.4.3
making output directory... done
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 31 source files that are out of date
updating environment: [new config] 31 added, 0 changed, 0 removed
reading sources... [  3%] administration
reading sources... [  6%] api
reading sources... [  9%] ckan
reading sources... [ 12%] committers
reading sources... [ 16%] configuration
reading sources... [ 19%] contributing
reading sources... [ 22%] csw-support
reading sources... [ 25%] distributedsearching
reading sources... [ 29%] docker
reading sources... [ 32%] geonode
reading sources... [ 35%] hhypermap
reading sources... [ 38%] index
reading sources... [ 41%] installation
reading sources... [ 45%] introduction
reading sources... [ 48%] json
reading sources... [ 51%] license
reading sources... [ 54%] migration-guide
reading sources... [ 58%] oaipmh
reading sources... [ 61%] odc
reading sources... [ 64%] opensearch
reading sources... [ 67%] outputschemas
reading sources... [ 70%] profiles
reading sources... [ 74%] repofilters
reading sources... [ 77%] repositories
reading sources... [ 80%] sitemaps
reading sources... [ 83%] soap
reading sources... [ 87%] sru
reading sources... [ 90%] support
reading sources... [ 93%] testing
reading sources... [ 96%] tools
reading sources... [100%] transactions

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  3%] administration

Theme error:
An error happened in rendering the page administration.
Reason: TemplateNotFound('i')
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/pycsw-2.4.2+dfsg'
make: *** [debian/rules:11: build] Error 2


Andreas


pycsw_2.4.2+dfsg-2.log.gz
Description: application/gzip

Bug#959772: game-data-packager: FTBFS with inkscape 1.0

[Andreas Beckmann]

Source: game-data-packager
Version: 64
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

game-data-packager started to FTBFS with inkscape 1.0:

[...]
inkscape --export-png=out/wolf-common.png -w96 -h96 data/wolf-common.svg
inkscape --export-png=out/grimfandango.png -w96 -h96 data/grimfandango.svg
inkscape --export-png=out/zork-inquisitor.png -w96 -h96 data/zork-inquisitor.svg
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Unknown option --export-png=out/wolf-common.png
Unknown option --export-png=out/zork-inquisitor.png
Unknown option --export-png=out/grimfandango.png
make[2]: *** [Makefile:139: out/zork-inquisitor.png] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** [Makefile:139: out/grimfandango.png] Error 1
make[2]: *** [Makefile:139: out/wolf-common.png] Error 1
make[2]: Leaving directory '/build/game-data-packager-64'
dh_auto_build: error: make -j3 returned exit code 2


Andreas


game-data-packager_64.log.gz
Description: application/gzip

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 959364 acpi-call-dkms
Bug #959364 [src:acpi-call] acpi-call-dkms: fails to build on kernel 5.6
Bug reassigned from package 'src:acpi-call' to 'acpi-call-dkms'.
No longer marked as found in versions acpi-call/1.1.0-5.
Ignoring request to alter fixed versions of bug #959364 to the same values 
previously set
> merge 959364 959729
Bug #959364 [acpi-call-dkms] acpi-call-dkms: fails to build on kernel 5.6
Bug #959729 [acpi-call-dkms] Build error with kernel 5.6
Added tag(s) ftbfs, sid, bullseye, and patch.
Bug #959364 [acpi-call-dkms] acpi-call-dkms: fails to build on kernel 5.6
Marked as found in versions acpi-call/1.1.0-5.
Merged 959364 959729
> thanks
Stopping processing here.

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

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> severity 959729 serious
Bug #959729 [acpi-call-dkms] Build error with kernel 5.6
Severity set to 'serious' from 'normal'
> merge 959729 959364
Bug #959729 [acpi-call-dkms] Build error with kernel 5.6
Unable to merge bugs because:
package of #959364 is 'src:acpi-call' not 'acpi-call-dkms'
Failed to merge 959729: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#959364: PR with patch

[Gard Spreemann]

I've cherry-picked the upstream fix as a patch in the gspr/bug-959364
branch of https://salsa.debian.org/gspr/acpi-call.git. It fixes the
problem for me.

A pull request for the maintainer follows.

***

The following changes since commit 8474a4b865725bedc46a1be0b30dbc2a6b2df84c:

  Update changelog for 1.1.0-5 release (2019-05-31 17:34:38 +0200)

are available in the Git repository at:

  https://salsa.debian.org/gspr/acpi-call.git 
625bdbfb2133f29c1c37ab775551e2f106459017

for you to fetch changes up to 625bdbfb2133f29c1c37ab775551e2f106459017:

  Add patch 0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch 
(2020-05-05 09:26:30 +0200)


Gard Spreemann (1):
  Add patch 0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch

 .../0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch  | 31 
+++
 debian/patches/series|  1 +
 2 files changed, 32 insertions(+)
 create mode 100644 
debian/patches/0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch

diff --git 
a/debian/patches/0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch
 
b/debian/patches/0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch
new file mode 100644
index 000..d2fdee3
--- /dev/null
+++ 
b/debian/patches/0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch
@@ -0,0 +1,31 @@
+From: Nikita Knutov 
+Date: Thu, 9 Apr 2020 09:45:40 +0300
+Subject: fix for 5.6+ kernels. file_operations dtype is changed
+
+---
+ acpi_call.c | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/acpi_call.c b/acpi_call.c
+index 7f2adb8..3574a44 100644
+--- a/acpi_call.c
 b/acpi_call.c
+@@ -318,11 +318,18 @@ static ssize_t acpi_proc_read( struct file *filp, char 
__user *buff,
+ return ret;
+ }
+ 
++#if LINUX_VERSION_CODE >= KERNEL_VERSION(5, 6, 0)
++static struct proc_ops proc_acpi_operations = {
++  .proc_read = acpi_proc_read,
++  .proc_write = acpi_proc_write,
++};
++#else
+ static struct file_operations proc_acpi_operations = {
+ .owner= THIS_MODULE,
+ .read = acpi_proc_read,
+ .write= acpi_proc_write,
+ };
++#endif
+ 
+ #else
+ static int acpi_proc_read(char *page, char **start, off_t off,
diff --git a/debian/patches/series b/debian/patches/series
index a8b7e9f..93663bb 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 0003-Fix-memory-leak-on-args.patch
 0001-Fix-compatibility-with-Linux-3.17.patch
 0002-Fix-build-4.12-copy-from-user.patch
+0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch


signature.asc
Description: PGP signature

Bug#959685: marked as done (security concerns for stable release)

[Debian Bug Tracking System]

Your message dated Tue, 5 May 2020 08:43:27 +0100
with message-id 

and subject line Re: Bug#959685: security concerns for stable release
has caused the Debian Bug report #959685,
regarding security concerns for stable release
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.)


-- 
959685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kubernetes
Severity: serious
X-Debbugs-Cc: t...@security.debian.org

Hi the kubernetes maintainer,

Copying from kubernetes docs[1].
> The Kubernetes project maintains release branches for the most recent three 
> minor releases.
> Minor releases occur approximately every 3 months, so each minor release 
> branch is maintained for approximately 9 months

[1] 
https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions

So could you provide your plan to support kubernetes in Debian stable release, 
thanks?
CCed the security team as well for their options.

-- 
Shengjing Zhu
--- End Message ---
--- Begin Message ---
Hi,

The overwhelming majority of software in Debian have no release policy, any
kind of governance to speak of or even a vague promise of support. Most of
us are still not opening 'serious' bugs against thousands of packages based
on our deep 'concerns' to sabotage them. This is primarily the Bug Tracking
System and not the Concern Tracking System. Kubernetes on the other hand
has a history of taking security problems seriously and fixing them
promptly.

In the past 5 years of the Kubernetes project there were some 14 security
bugs worthy of a CVE #. Based on the size of the project and the scrutiny
that it benefits from that is a pretty small number. Also, not all of those
bugs were very serious - some were. Not all of those bugs affected old
releases - some did. For some of them a mitigation was possible without
replacing binaries - not in all cases tough. At this point we are talking
about a fraction of a small number to start with. In the remaining cases we
can still backport the available patches ourselves if needs be or reach out
to the community if needed.

Also, since Kubernetes (and almost all Go programs) is essentially shipped
as a static binary, upgrading to a newer version simpler, as in it won't be
affecting all other packages installed. Obviously the actual process of
upgrading Kubernetes can be more involved, depending on the configuration
of an installation.

I'm closing this concern for now.

On Mon, 4 May 2020, 01:09 Shengjing Zhu,  wrote:

> Package: kubernetes
> Severity: serious
> X-Debbugs-Cc: t...@security.debian.org
>
> Hi the kubernetes maintainer,
>
> Copying from kubernetes docs[1].
> > The Kubernetes project maintains release branches for the most recent
> three minor releases.
> > Minor releases occur approximately every 3 months, so each minor release
> branch is maintained for approximately 9 months
>
> [1]
> https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions
>
> So could you provide your plan to support kubernetes in Debian stable
> release, thanks?
> CCed the security team as well for their options.
>
> --
> Shengjing Zhu
>
--- End Message ---

Processed: Problem is also in buster

[Debian Bug Tracking System]

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

> tags 956020 buster
Bug #956020 [mydumper] mydumper FTBFS on armel/armhf/mips/mipsel , needs to 
link against libm.
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#956675: cyvcf2: test failures on mipsel, ppc64el and s390x

[Adrian Bunk]

On Tue, Apr 14, 2020 at 10:45:56AM +0200, Sebastian Ramacher wrote:
> Source: cyvcf2
> Version: 0.11.6-2
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the past)
> 
> cyvcf2 failed to build on mipsel (where it built before),
>...

The mipsel failure is "FTBFS on Loongson", this needs blacklisting on 
the Loongson buildds.

cu
Adrian

Processed: Merge with the root cause bug

[Debian Bug Tracking System]

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

> reassign 954603 python3-humanfriendly
Bug #954603 {Done: Andreas Tille } [src:cyvcf2] cyvcf2: 
FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 
"3.7 3.8" returned exit code 13
Bug reassigned from package 'src:cyvcf2' to 'python3-humanfriendly'.
No longer marked as found in versions cyvcf2/0.11.6-1.
No longer marked as fixed in versions cyvcf2/0.11.6-2.
> unarchive 954640
Bug #954640 {Done: Scott Kitterman } 
[python3-humanfriendly] python3-humanfriendly: humanfriendly.terminal module 
missing from package
Unarchived Bug 954640
> forcemerge 954640 954603
Bug #954640 {Done: Scott Kitterman } 
[python3-humanfriendly] python3-humanfriendly: humanfriendly.terminal module 
missing from package
Bug #954603 {Done: Andreas Tille } [python3-humanfriendly] 
cyvcf2: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.7 3.8" returned exit code 13
Marked as fixed in versions humanfriendly/8.1-2.
Marked as found in versions humanfriendly/8.1-1.
Merged 954603 954640
> affects 954640 src:cyvcf2 src:azure-cli
Bug #954640 {Done: Scott Kitterman } 
[python3-humanfriendly] python3-humanfriendly: humanfriendly.terminal module 
missing from package
Bug #954603 {Done: Andreas Tille } [python3-humanfriendly] 
cyvcf2: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.7 3.8" returned exit code 13
Added indication that 954640 affects src:cyvcf2 and src:azure-cli
Added indication that 954603 affects src:cyvcf2 and src:azure-cli
> thanks
Stopping processing here.

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

Processed: closing 954607

[Debian Bug Tracking System]

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

> close 954607
Bug #954607 [src:golang-github-twstrike-gotk3adapter] 
golang-github-twstrike-gotk3adapter: FTBFS: Errors while processing: 
libglib2.0-cil  libgio-cil  sbuild-build-depends-main-dummy 
golang-github-gotk3-gotk3-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: bug 953289 is forwarded to gene...@discussion.soxr.p.re.sourceforge.net

[Debian Bug Tracking System]

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

> forwarded 953289 gene...@discussion.soxr.p.re.sourceforge.net
Bug #953289 [libsoxr0] ABI change in libsoxr 0.1.3
Set Bug forwarded-to-address to 'gene...@discussion.soxr.p.re.sourceforge.net'.
> thanks
Stopping processing here.

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

Processed: forcibly merging 954602 957556

[Debian Bug Tracking System]

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

> forcemerge 954602 957556
Bug #954602 [src:modglue] modglue: FTBFS: socket.h:285:33: error: flexible 
array member ‘cmsghdr::__cmsg_data’ not at end of ‘struct 
modglue::pipe::send_blocking_(const char*, int)::’
Bug #957556 [src:modglue] modglue: ftbfs with GCC-10
Severity set to 'serious' from 'normal'
Added tag(s) ftbfs.
Merged 954602 957556
> thanks
Stopping processing here.

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

Processed: closing 954563

[Debian Bug Tracking System]

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

> close 954563
Bug #954563 [src:python-dugong] python-dugong: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.7 3.8" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: tagging 954517

[Debian Bug Tracking System]

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

> tags 954517 + fixed-upstream
Bug #954517 [src:python-junit-xml] python-junit-xml: FTBFS: dh_auto_test: 
error: pybuild --test -i python{version} -p 3.8 returned exit code 13
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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