Bug#946255: marked as done (dwz: returns exit status 1, causing FTBFS in deal.ii)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 07:38:52 +
with message-id 
and subject line Bug#946255: fixed in deal.ii 9.1.1-7
has caused the Debian Bug report #946255,
regarding dwz: returns exit status 1, causing FTBFS in deal.ii
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.)


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

Source: dwz
Version: 0.13-3
Severity: important
Affects: src:deal.ii

Hi Maintainer

Since upgrading to dwz 0.13-3 (and with 0.13-4), deal.ii FTBFS with the 
following error:


   dh_dwz -O--max-parallel=2
dwz: 
debian/libdeal.ii-9.1.1/usr/lib/x86_64-linux-gnu/libdeal.ii.so.9.1.1: 
Too many DIEs, not optimizing

dwz: Too few files for multifile optimization
dh_dwz: dwz 
-mdebian/libdeal.ii-9.1.1/usr/lib/debug/.dwz/x86_64-linux-gnu/libdeal.ii-9.1.1.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/libdeal.ii-9.1.1.debug -- 
debian/libdeal.ii-9.1.1/usr/lib/x86_64-linux-gnu/libdeal.ii.g.so.9.1.1 
debian/libdeal.ii-9.1.1/usr/lib/x86_64-linux-gnu/libdeal.ii.so.9.1.1 
returned exit code 1

make: *** [debian/rules:7: binary] Error 255

With dwz 0.13-1 and 0.13-2, the build is successful, but includes the 
same warnings:


   dh_dwz -O--max-parallel=2
dwz: 
debian/libdeal.ii-9.1.1/usr/lib/x86_64-linux-gnu/libdeal.ii.so.9.1.1: 
Too many DIEs, not optimizing

dwz: Too few files for multifile optimization
dh_dwz: No dwz multifile created, but not explicitly requested either so 
ignoring it.

dh_dwz: Common issues include no debug information at all (missing -g) and
dh_dwz: compressed debug information (#931891).

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: deal.ii
Source-Version: 9.1.1-7

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

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

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated deal.ii package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Dec 2019 07:10:35 +
Source: deal.ii
Architecture: source
Version: 9.1.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Graham Inggs 
Closes: 946255
Changes:
 deal.ii (9.1.1-7) unstable; urgency=medium
 .
   * Double up the limit of debug information entries
 (Closes: #946255)
   * Bump Standards-Version to 4.4.1, no changes
Checksums-Sha1:
 88ba7aada8d45965399b7ef6d93881a1e705e1c7 2733 deal.ii_9.1.1-7.dsc
 63f1eeaed6618bbfff37f9e837a0aa9990c81ba7 8708 deal.ii_9.1.1-7.debian.tar.xz
Checksums-Sha256:
 cb6754a5cf4949bf5bc32944ba6906cc4c8f32b5c2ca9794eef1f14d4eb93567 2733 
deal.ii_9.1.1-7.dsc
 719cf45e5898ee0e92b1dac099ad0f0badf6f0c512010d51d0bca0248f18be83 8708 
deal.ii_9.1.1-7.debian.tar.xz
Files:
 c64e0809d0a5981170994c06f4271d24 2733 libs optional deal.ii_9.1.1-7.dsc
 a3e7580bfd2bf5d855aba44efada69bd 8708 libs optional 
deal.ii_9.1.1-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl4DDFwACgkQr8/sjmac
4cI/fA//YEWRUvqSkJJwiCVN3dP9P2LU1quLYl1tS9NEXNVAvi5YDia9OoDJ36FR
EXpV+DQaHwnZ22UDsaQ2T9ajbfqU5LFFYwFxpijFRpQqBtu2R++ud0rC+iYPzV6Q
TjwXI9aEnLYUTcoHFGFx2Wz9Y2pg04xzB+eOdOqUo9Bb5B4GyDi1srMVmGZMSxav
hzJIw+Di4hVBE5YKXyLTTMSuz3wJJBKYa9aYvw85CGHWJtAWVjPCs0enpFTjImkv
dKZ32w/+Y86jx27uQ8UZCjV7jTKc0JRfHVBKVJ+FjosZLtbsFRB2nUm7whOHhlmo
vMTmtx1uMg0yOfEZlK+aMGYdrboQhZpTatJi1q0DL6cYDSv0aFslUJiOljk7SYUO
uIXjT/8bnLpv2T/kjf0wfV90s31C2+BQlCsaVwHtUP2ZcAF9Hg521yAGwSCal6LJ
FPFUELhx+gvFJP5yllQaEhgU9DCUfyJTJHIPnrQkzM3mSn2lbANO3WHzR6E+KBTL
U3cHvIx7abDs0DdOGix2utUi2W6OL0M6K9BCQ3/N8jRz1r/Nkon+g/q2x1aToqg/
u6Y9h6bQKgSMUKMWKS5ZTLK1N1yb7xnzRngGnGBxQikqDaoTH0CI1sxXB3k5HhvF
TjXVr0wa3PjphdVCfku4bShE01jtm/5ZIeSvwrPgGX8Y7Lps50k=
=xk3J
-END PGP SIGNATURE End Message ---

Bug#947329: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

[Andreas Tille]

Control: tags -1 unreproducible
Control: tags -1 moreinfo

Hi,

On Tue, Dec 24, 2019 at 03:56:45PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> 
> Hi! During a rebuild of your package it FTBFS with the following error:
> 
> dh_installman: mv debian/bppphyview/usr/share/man/man1/phyview.1.dh-new 
> debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

That's pretty strange.  The very simple debian/bppphyview.manpages just
specifies man/*.1 and man/phyview.1 exists in the source.  I've checked
the build in a pbuilder chroot and it builds nicely.  Are you really sure
that your build environment is OK?

Kind regards, Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#947329: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #947329 [src:bppphyview] FTBFS: 
debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory
Added tag(s) unreproducible.
> tags -1 moreinfo
Bug #947329 [src:bppphyview] FTBFS: 
debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory
Added tag(s) moreinfo.

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

Bug#943448: marked as done (beets autopkgtest unnecessarily tests against non-default python)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 07:34:58 +
with message-id 
and subject line Bug#943448: fixed in beets 1.4.9-1
has caused the Debian Bug report #943448,
regarding beets autopkgtest unnecessarily tests against non-default python
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.)


-- 
943448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: beets
Version: 1.4.7-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

With the introduction of python3.8 as a "supported" python in Ubuntu, the
beets autopkgtest is now failing because it is incompatible with python3.8:

[...]
==
ERROR: test_delete_original_file (test.test_art.ArtImporterTest)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.QpUJrP/autopkgtest_tmp/test/test_art.py", line 503, in 
test_delete_original_file
self._fetch_art(True)
  File "/tmp/autopkgtest.QpUJrP/autopkgtest_tmp/test/test_art.py", line 472, in 
_fetch_art
self.plugin.assign_art(self.session, self.task)
  File "/tmp/autopkgtest.QpUJrP/autopkgtest_tmp/beetsplug/fetchart.py", line 
828, in assign_art
self._set_art(task.album, candidate, not self.src_removed)
  File "/tmp/autopkgtest.QpUJrP/autopkgtest_tmp/beetsplug/fetchart.py", line 
813, in _set_art
album.set_art(candidate.path, delete)
  File "/usr/share/beets/beets/library.py", line 1148, in set_art
artdest = self.art_destination(path)
  File "/usr/share/beets/beets/library.py", line 1122, in art_destination
filename_tmpl = Template(
  File "/usr/share/beets/beets/util/functemplate.py", line 558, in __init__
self.compiled = self.translate()
  File "/usr/share/beets/beets/util/functemplate.py", line 591, in translate
func = compile_func(
  File "/usr/share/beets/beets/util/functemplate.py", line 147, in compile_func
prog = compile(mod, '', 'exec')
TypeError: required field "posonlyargs" missing from arguments

[...]

  (http://autopkgtest.ubuntu.com/packages/b/beets/focal/amd64)

I understand that it's useful to get early indications that your software is
incompatible with upcoming versions of python, but it's not appropriate to
use autopkgtests in this way, because beets is an application not a module
and will only ever be executed using /usr/bin/python3 on the system - you
have added an artificial test dependency on python3-all and as a result
these failing tests will artificially block the addition of python3.8 as a
supported (but not default) python version in the archive.

The attached patch adjusts the test and the build-dependencies so that the
beets tests instead test the actual behavior that is relevant to the package.

P.S. also, heads up that beets is incompatible with python3.8. ;)

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru beets-1.4.7/debian/control beets-1.4.7/debian/control
--- beets-1.4.7/debian/control  2018-08-20 08:55:31.0 -0700
+++ beets-1.4.7/debian/control  2019-10-24 12:23:32.0 -0700
@@ -9,7 +9,7 @@
  debhelper (>= 10),
  dh-python,
  libc-bin (>= 2.13),
- python3-all (>= 3.4),
+ python3 (>= 3.4),
  python3-bs4,
  python3-flask,
  python3-jellyfish,
diff -Nru beets-1.4.7/debian/tests/unittests beets-1.4.7/debian/tests/unittests
--- beets-1.4.7/debian/tests/unittests  2018-08-20 08:55:31.0 -0700
+++ beets-1.4.7/debian/tests/unittests  2019-10-24 12:22:59.0 -0700
@@ -5,8 +5,6 @@
 export LC_ALL=C.UTF-8
 export PYTHONPATH=/usr/share/beets
 
-pythons="$(py3versions -s)"
-
 cp -a test $AUTOPKGTEST_TMP
 cd "$AUTOPKGTEST_TMP"
 
@@ -14,7 +12,4 @@
 # __path__ to ensure that their local beetsplug is used.
 ln -s /usr/share/beets/beetsplug .
 
-for python in $pythons; do
-   echo "=== $python ==="
-   $python -m unittest discover -p 'test_*' 2>&1
-done
+python3 -m unittest discover -p 'test_*' 2>&1
--- End Message ---
--- Begin Message ---
Source: beets
Source-Version: 1.4.9-1

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

A summary of the changes between this version and the previous

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

Hi Chen-Tse,

On Tue, Dec 24, 2019 at 10:39:55AM -0500, Chen-Tse Tsai wrote:
> Thanks, Andreas.
> 
> I just submitted a PR for dropping python2 dependencies:
> https://salsa.debian.org/science-team/libsvm/merge_requests/1
> 
> Any comment is appreciated. I'll be working on upgrading to new upstream.

Looks very good!  I injected the patch by Helmut Grohne (#862234) as well.

For the upgrade I was simply using

   
https://salsa.debian.org/r-pkg-team/maintenance-utilities/blob/master/routine-update

I developed it for R packages but it works for other packages as well.

Since I noticed that the new upstream source includes some windows
binaries I'll remove them via Files-Excluded.  I hope that you are
happy that I'm doing these routine tasks and will sponsor the
package for you once ready.

Kind regards, Andreas.
 
> Thanks,
> Chen-Tse
> 
> 
> On Mon, Dec 23, 2019 at 4:03 PM Andreas Tille  wrote:
> 
> > On Mon, Dec 23, 2019 at 03:06:37PM -0500, Chen-Tse Tsai wrote:
> > > I have a quick question. Previously the python modules are installed to
> > > /usr/share/pyshared/. Should I use /usr/lib/python3/dist-packages instead
> > > if I change it to python3? I see this in the policy and this is also what
> > > liblinear uses. Just want to double check.
> >
> > Yes, follow liblinear example.
> >
> > Thanks for your work on this
> >
> >  Andreas.
> >
> > --
> > http://fam-tille.de
> >

-- 
http://fam-tille.de

Processed: py2removal RC severity updates - 2019-12-25 03:37:03.778142+00:00

[Debian Bug Tracking System]

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

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

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

Bug#936454: marked as done (dulwich: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 03:19:17 +
with message-id 
and subject line Bug#936454: fixed in dulwich 0.19.14-3
has caused the Debian Bug report #936454,
regarding dulwich: 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.)


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

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated dulwich package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Dec 2019 17:54:20 -0500
Source: dulwich
Architecture: source
Version: 0.19.14-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936454
Changes:
 dulwich (0.19.14-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #936454
Checksums-Sha1:
 0a608bc0694d33072afc776ff8b6f17967fcfc1b 2358 dulwich_0.19.14-3.dsc
 7523d7c36194350bb97c0eeca8e474f7c63decc3 37060 dulwich_0.19.14-3.debian.tar.xz
 e8ff755887736a7f82de121e53a1882af2aaec09 7870 
dulwich_0.19.14-3_source.buildinfo
Checksums-Sha256:
 ebe9dbd06a9d037a6b17783abce80927855119b290c57e6ea72ca179bddd7652 2358 
dulwich_0.19.14-3.dsc
 43f8b079a52e9209112958d0461acebf6a4129f0e829c056ff326ba0632e6770 37060 
dulwich_0.19.14-3.debian.tar.xz
 6cabe9df9815b3dedf8bf523f1e4031774461d6bdb7002c7465fa24ae2ed5636 7870 
dulwich_0.19.14-3_source.buildinfo
Files:
 b1f5d9328a9abb322bfb39373c2e3285 2358 python optional dulwich_0.19.14-3.ds

Bug#936610: marked as done (ghp-import: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 02:41:30 +
with message-id 
and subject line Bug#936610: fixed in ghp-import 0.5.5-2
has caused the Debian Bug report #936610,
regarding ghp-import: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:ghp-import

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated ghp-import 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, 24 Dec 2019 20:43:26 -0500
Source: ghp-import
Architecture: source
Version: 0.5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Closes: 936610
Changes:
 ghp-import (0.5.5-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Switch to python3; Closes: #936610
   * debian/control
 - update Enhances to `pelican`
 - bump Standards-Version to 4.4.1 (no changes needed)
Checksums-Sha1:
 842136212329b67407ca29fe2869cf995e89661a 2013 ghp-import_0.5.5-2.dsc
 19e98e494ce5c3ff891c2e9a2c47b7ec9d96789b 2064 ghp-import_0.5.5-2.debian.tar.xz
 8c50db3ee9867539cdbe500ebd9315b5537d9677 6142 
ghp-import_0.5.5-2_source.buildinfo
Checksums-Sha256:
 77dc4ed10d91195f1ac348efe6f07f11b7e50b122858cc3311cec10d598ed013 2013 
ghp-import_0.5.5-2.dsc
 e917d6e2333ce43f0d281c2b2

Bug#947340: linux-base: can't be upgraded

[Christoph Anton Mitterer]

Package: linux-base
Version: 4.6
Severity: grave
Justification: renders package unusable


Hi.

Since last April, the package can't be upgraded as it conflicts with
the current version of kernel-common.

Would be nice if this could be resolved.

Probably it's this change:
  * Take over kernel-img.conf(5) manual page from kernel-common 

 ▒
(Closes: #925415)   

 ▒
but then this should be reflected in kernel-common, or it should have
been coordinated with its maintainer in the first place.

Cheers,
Chris.

Bug#947339: slingshot: should this package be removed?

[Sandro Tosi]

Source: slingshot
Severity: serious

Hello,
iI think there are several issues with slingshot:

- python2-only package
- upstream dormant since 8+ years
- no updates on https://github.com/ryanakca/slingshot/issues/9 since Aug 9

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

Regards,
Sandro

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

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

Versions of packages slingshot depends on:
ii  fonts-freefont-ttf  20120503-9
ii  python  2.7.16-1
pn  python-pygame   

slingshot recommends no packages.

slingshot suggests no packages.

Bug#937544: pyspread: Python2 removal in sid/bullseye

[Sandro Tosi]

Hey Andreas,
upstream is porting this application to python3 at
https://gitlab.com/pyspread/pyspread and they just released an alpha
version for it. Since pyspread is no longer in testing, then maybe you
can consider package this version for unstable? this will unlock
several python2 modules pyspread depends on.

thanks for considering,
Sandro

Bug#947338: cherrytree: should this package be removed?

[Sandro Tosi]

Source: cherrytree
Severity: serious

Hello,
i believe there are several issues with cherrytree:

- python2-only application
- depends on pygtk, deprecated
- depends on gtksourceview, deprecated
- upstream is rewriting it in C++, so there's no hope for a py3k port

i think it's time to remove it (and eventuall re-introduce it in Debian once the
C++ port is completed); if i dont hear back within a week with a good reason to
keep this package in Debian, i'll file for it's removal.

Regards,
Sandro


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

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

Versions of packages cherrytree depends on:
ii  p7zip-full 16.02+dfsg-6
ii  python 2.7.16-1
ii  python-chardet 3.0.4-3
ii  python-dbus1.2.8-3
pn  python-enchant 
ii  python-gtk22.24.0-6
pn  python-gtksourceview2  

cherrytree recommends no packages.

cherrytree suggests no packages.

Processed: fixed 938861 in 0.4~20171211.r234ef16+dfsg-1, closing 938861

[Debian Bug Tracking System]

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

> fixed 938861 0.4~20171211.r234ef16+dfsg-1
Bug #938861 {Done: Sandro Tosi } [src:yagv] yagv: Python2 
removal in sid/bullseye
Marked as fixed in versions yagv/0.4~20171211.r234ef16+dfsg-1; no longer marked 
as fixed in versions 0.4~20171211.r234ef16+dfsg-1.
> close 938861 0.4~20171211.r234ef16+dfsg-1
Bug #938861 {Done: Sandro Tosi } [src:yagv] yagv: Python2 
removal in sid/bullseye
Ignoring request to alter fixed versions of bug #938861 to the same values 
previously set
Bug #938861 {Done: Sandro Tosi } [src:yagv] yagv: Python2 
removal in sid/bullseye
Bug 938861 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#938861: fixed 938861 in 0.4~20171211.r234ef16+dfsg-1, closing 938861

[Chow Loong Jin]

fixed 938861 0.4~20171211.r234ef16+dfsg-1
close 938861 0.4~20171211.r234ef16+dfsg-1
thanks

Bug#937950: marked as done (python-nose-exclude: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 23:35:43 +
with message-id 
and subject line Bug#937950: fixed in python-nose-exclude 0.5.0-2
has caused the Debian Bug report #937950,
regarding python-nose-exclude: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-nose-exclude

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

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

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-nose-exclude 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Dec 2019 00:05:03 +0100
Source: python-nose-exclude
Architecture: source
Version: 0.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 928574 937950
Changes:
 python-nose-exclude (0.5.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Use team+openst...@tracker.debian.org as maintainer
   * Use debhelper-compat instead of debian/compat.
 .
   [ Thomas Goirand ]
   * Remove Julien Danjou from uploaders (Closes: #928574).
   * Removed Python 2 support (Closes: #937950).
Checksums-Sha1:
 112cc630ea60ff1d71cdcee7d2d5d35cfb13c6e2 2165 python-nose-exclude_0.5.0-2.dsc
 17a25e6401299fed33281c40fbe7a723c58b974c 2780 
python-nose-exclude_0.5.0-2.debian.tar.xz
 52ac1c82c645d3ba024d9857356d79b634a2c0c9 6265 
python-nose-exclude_0.5.0-2_amd64.buildinfo
Checksums-Sha256:
 d6b98e48af526cf8d7bd4787a3775eb0f6e632b8858ed

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

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 23:10:17 +
with message-id 
and subject line Bug#937899: fixed in python-logutils 0.3.3-7
has caused the Debian Bug report #937899,
regarding python-logutils: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-logutils

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

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

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-logutils 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, 24 Dec 2019 23:45:39 +0100
Source: python-logutils
Architecture: source
Version: 0.3.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 937899
Changes:
 python-logutils (0.3.3-7) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Changed upstream homepage to bitbucket.org
   * d/control: Use team+openst...@tracker.debian.org as maintainer
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
   * Use debhelper-compat instead of debian/compat.
   * d/control: Set Vcs-* to salsa.debian.org
   * d/watch: Use https protocol
 .
   [ Daniel Baumann ]
   * Updating vcs fields.
   * Updating copyright format url.
   * Updating maintainer field.
   * Running wrap-and-sort -bast.
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles.
 .
   [ Thomas Goirand ]
   * Removed Python 2 support (Closes: #937899

Bug#936902: marked as done (libplist: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 18:11:31 -0500
with message-id 

and subject line Re: libplist: Python2 removal in sid/bullseye
has caused the Debian Bug report #936902,
regarding libplist: 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.)


-- 
936902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libplist
Version: 2.0.1~git20190104.3f96731-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:libplist

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.1.0-2

On Fri, 30 Aug 2019 07:24:02 + Matthias Klose  wrote:
> Package: src:libplist
> Version: 2.0.1~git20190104.3f96731-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

https://salsa.debian.org/imobiledevice-team/libplist/commit/dc008c2fd5e499a3422f1d9e49e132d1683e6e5e--- End Message ---

Bug#938861: marked as done (yagv: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 17:47:40 -0500
with message-id 

and subject line Re: yagv: Python2 removal in sid/bullseye
has caused the Debian Bug report #938861,
regarding yagv: 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.)


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

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

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~20171211.r234ef16+dfsg-1

On Fri, 30 Aug 2019 07:59:19 + Matthias Klose  wrote:
> Package: src:yagv
> Version: 0.4~20130422.r5bd15ed+dfsg-4
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

https://tracker.debian.org/news/1088912/accepted-yagv-0420171211r234ef16dfsg-1-source-into-unstable/--- End Message ---

Bug#937900: [pkg-lxc-devel] Bug#937900: python-lxc: Python2 removal in sid/bullseye

[Pierre-Elliott Bécue]

Le 24 décembre 2019 21:08:39 GMT+01:00, Antonio Terceiro  
a écrit :
>On Thu, Dec 19, 2019 at 07:58:15PM +, Evgeni Golov wrote:
>> Hi Moritz,
>> 
>> yeah, that sounds reasonable.
>> 
>> PEB, terceiro, any objections?
>
>nope, just go ahead

Same
-- 
PEB (from my phone)

Bug#946816: marked as done (archmage 1:0.4.0-1 is missing a dependency on python3-sgmllib3k)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 22:19:19 +
with message-id 
and subject line Bug#946816: fixed in archmage 1:0.4.1-1
has caused the Debian Bug report #946816,
regarding archmage 1:0.4.0-1 is missing a dependency on python3-sgmllib3k
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.)


-- 
946816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: archmage
Version: 1:0.3.1-4
Severity: grave
Justification: renders package unusable

archmage 0.4 has introduced the dependency on sgmllib3k. This library has not 
yet
entered Debian archive (sitting in NEW), so archmage is broken.

This bug is filed to prevent archmage 0.4 from entering testing until sgmllib3k 
is
available and a new package release can be uploaded

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

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

Versions of packages archmage depends on:
ii  python 2.7.17-2
ii  python-bs4 4.8.0-2
ii  python-chm 0.8.4.1-3+b1
ii  python-lxml4.4.1-1+b1
ii  python-setuptools  41.4.0-1

archmage recommends no packages.

Versions of packages archmage suggests:
pn  elinks | links 
pn  htmldoc
pn  libapache2-mod-python  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: archmage
Source-Version: 1:0.4.1-1

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

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

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

Debian distribution maintenance software
pp.
Mikhail Gusarov  (supplier of updated archmage 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, 24 Dec 2019 10:05:17 +0100
Source: archmage
Architecture: source
Version: 1:0.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Mikhail Gusarov 
Changed-By: Mikhail Gusarov 
Closes: 946816
Changes:
 archmage (1:0.4.1-1) unstable; urgency=low
 .
   * New upstream release:
 - debian/rules: Enable testsuite.
 - debian/source/lintian-overrides: Add override for test CHM file.
   * Add missing python3-sgmllib3k dependency (Closes: #946816).
   * Require python3-chm >= 0.8.6, otherwise chmlib.chm_open fails on
 Unicode filenames.
Checksums-Sha1:
 8f6c722e8bf1d10fd534de579bc1c0054b16fad2 1704 archmage_0.4.1-1.dsc
 b242de8965de5d5cc22f201e900746aa47e2ebd6 31012 archmage_0.4.1.orig.tar.gz
 ee783427503368f300e3215ba0abef3ee0a93a6f 4428 archmage_0.4.1-1.debian.tar.xz
 ccc1c31d539f5c14a9de7eba06d3ccc93b8a 5195 archmage_0.4.1-1_source.buildinfo
Checksums-Sha256:
 00681ca0b50fb2cbece028c60214d41ce11d8beead0abed778d930f0fd942821 1704 
archmage_0.4.1-1.dsc
 1ae5563125ef6f032cef0001ae2c95a2539b1e2afffd1dd42f91144814dfa1e7 31012 
archmage_0.4.1.orig.tar.gz
 c2e77bdaf786115a9f4e8441ebeaa7a29415fc735d9d28ab4509e71e09886197 4428 
archmage_0.4.1-1.debian.tar.xz
 4bf1f11f624c56c4650c8f69039f5b6b832da887be18d1b532ebf7621142eb42 5195 
archmage_0.4.1-1_source.buildinfo
Files:
 5413a173c5d363deb4c51842d486e771 1704 utils optional archmage_0.4.1-1.dsc
 bf8493ff86c4687553fa134907b545ab 31012 utils optional 
archmage_0.4.1.orig.tar.gz
 b49b1f32b237d599eca23e627112b6d7 4428 utils optional 
archmage_0.4.1-1.debian.tar.xz
 e5a0cc56b2266105c9336685d060082a 5195 utils optional 
archmage_0.4.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE6mdM4hvGehkaRy4s/eS3QibJkzgFAl4CingACgkQ/eS3QibJ
kzhVAAf+N2hmCqWQ75A4Bljv9tmNBufAHv0NncAAfd52ePTyNkLoaHqTO6ePb4ik
DLZ/UX6ZL4iVUXtQ44bxpz3SQ96zlJgUrGqI0ap4uNGtn9hQ7bASweAeOuyYjWS5
ZKYvgjqvMQ708GhzCkRxUa8vXAz3XsFqd/upOg7k0ZiMS9K/Jpgflg8LEXMIVU3A
pQZMrNiE8HoPN1dnn3Get9zgIG/WZtQzMNGSNfuGjZmQcpVkE05myfRDqxLl+R0/
9he/FzYeUUvJvhc9J8uayDFhzSTamBHqYeTX69EuTYj73+LFJQGIyQ2H8LI+YI5x
WQcCZrBCYRG9+zb6ee/3w6aosxAByg==
=n+nB
-END PGP SIGNATURE End Message ---

Bug#938510: marked as done (soapysdr: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 22:07:12 +
with message-id 
and subject line Bug#938510: fixed in soapysdr 0.7.1-3
has caused the Debian Bug report #938510,
regarding soapysdr: 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.)


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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated soapysdr 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, 24 Dec 2019 22:57:15 +0100
Source: soapysdr
Architecture: source
Version: 0.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 938510
Changes:
 soapysdr (0.7.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 module. (Closes: #938510)
   * Add debian/gitlab-ci.yml; disable reprotest for now.
   * Add autopkgtest along the contents of .travis.yml.
Checksums-Sha1:
 28c6c06cce9e667e5ca3115a8f2f3323af2be38f 2466 soapysdr_0.7.1-3.dsc
 06de6d9044008ba2a25af956716baa0f560283af 6436 soapysdr_0.7.1-3.debian.tar.xz
Checksums-Sha256:
 be3b4e0c1885c52fe6ebf8733b6d43a34d216f2c3d93302a5db7d54bd05b045d 2466 
soapysdr_0.7.1-3.dsc
 b724fd4d89142014075c187f4991a3f9c2190ab78aba5ebc3872248a6b56a909 6436 
soapysdr_0.7.1-3.debian.tar.xz
Files:
 977c46c539a878390bbbe71d8e04d990 2466 hamradio optional soapysdr_0.7.1-3.dsc
 e4e1112817cc6188e40ce5724d261dc3 6436 hamradio optional 
soapysdr_0.7.1-

Bug#943901: marked as done (ipykernel: failing tests with python3.8)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 22:04:21 +
with message-id 
and subject line Bug#943901: fixed in ipykernel 5.1.3-1
has caused the Debian Bug report #943901,
regarding ipykernel: failing tests with python3.8
to be marked as done.

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

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


-- 
943901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ipykernel
Version: 4.9.0-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

The ipykernel package fails to build from source in Ubuntu focal, because
Ubuntu has begun the transition to python3.8 and ipykernel 4.9.0 is not
source-compatible with python3.8:

[...]
==
ERROR: Does executing code in an in-process kernel work?
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.8/build/ipykernel/inprocess/tests/test_kernelmanager.py",
 line 63, in test_execute
assert km.kernel.shell.user_ns['foo'] == 1
KeyError: 'foo'
 >> begin captured stdout << -
status
status

- >> end captured stdout << --
 >> begin captured logging << 
asyncio: DEBUG: Using selector: EpollSelector
ipykernel.inprocess.ipkernel: DEBUG: 
*** MESSAGE TYPE:kernel_info_request***
ipykernel.inprocess.ipkernel: DEBUG:Content: {}
   --->
   
ipykernel.inprocess.ipkernel: DEBUG: kernel_info_request: {'header': {'msg_id': 
'ea45d6d2-e4a08f7948d5f1853d12015e', 'msg_type': 'kernel_info_request', 
'username': 'buildd', 'session': '903e4bd4-9ea897ba7f841240791a9cec', 'date': 
datetime.datetime(2019, 10, 28, 13, 23, 42, 542565, tzinfo=tzlocal()), 
'version': '5.3'}, 'msg_id': 'ea45d6d2-e4a08f7948d5f1853d12015e', 'msg_type': 
'kernel_info_request', 'parent_header': {}, 'metadata': {}, 'content': {}, 
'buffers': []}
ipykernel.inprocess.ipkernel: DEBUG: {'header': {'msg_id': 
'2c3237e1-51c523aa6cb893a3872aea62', 'msg_type': 'kernel_info_reply', 
'username': 'buildd', 'session': '903e4bd4-9ea897ba7f841240791a9cec', 'date': 
datetime.datetime(2019, 10, 28, 13, 23, 42, 544275, 
tzinfo=datetime.timezone.utc), 'version': '5.3'}, 'msg_id': 
'2c3237e1-51c523aa6cb893a3872aea62', 'msg_type': 'kernel_info_reply', 
'parent_header': {'msg_id': 'ea45d6d2-e4a08f7948d5f1853d12015e', 'msg_type': 
'kernel_info_request', 'username': 'buildd', 'session': 
'903e4bd4-9ea897ba7f841240791a9cec', 'date': datetime.datetime(2019, 10, 28, 
13, 23, 42, 542565, tzinfo=tzlocal()), 'version': '5.3'}, 'content': {'status': 
'ok', 'protocol_version': '5.1', 'implementation': 'ipython', 
'implementation_version': '5.8.0', 'language_info': {'name': 'python', 
'version': '3.8.0', 'mimetype': 'text/x-python', 'codemirror_mode': {'name': 
'ipython', 'version': 3}, 'pygments_lexer': 'ipython3', 'nbconvert_exporter': 
'python', 'file_extension': '.py'}, 'banner': 'Python 3.8.0 (default, Oct 27 
2019, 15:36:55) \nType "copyright", "credits" or "license" for more 
information.\n\nIPython 5.8.0 -- An enhanced Interactive Python.\n? -> 
Introduction and overview of IPython\'s features.\n%quickref -> Quick 
reference.\nhelp  -> Python\'s own help system.\nobject?   -> Details about 
\'object\', use \'object??\' for extra details.\n', 'help_links': [{'text': 
'Python Reference', 'url': 'https://docs.python.org/3.8'}, {'text': 'IPython 
Reference', 'url': 'https://ipython.org/documentation.html'}, {'text': 'NumPy 
Reference', 'url': 'https://docs.scipy.org/doc/numpy/reference/'}, {'text': 
'SciPy Reference', 'url': 'https://docs.scipy.org/doc/scipy/reference/'}, 
{'text': 'Matplotlib Reference', 'url': 
'https://matplotlib.org/contents.html'}, {'text': 'SymPy Reference', 'url': 
'http://docs.sympy.org/latest/index.html'}, {'text': 'pandas Reference', 'url': 
'https://pandas.pydata.org/pandas-docs/stable/'}]}, 'metadata': {}, 'tracker': 
}
ipykernel.inprocess.ipkernel: DEBUG: 
*** MESSAGE TYPE:execute_request***
ipykernel.inprocess.ipkernel: DEBUG:Content: {'code': 'foo = 1', 'silent': 
False, 'store_history': True, 'user_expressions': {}, 'allow_stdin': True}
   --->
   
ipykernel.inprocess.ipkernel: DEBUG: execute_request: {'header': {'msg_id': 
'88b61e78-dea95246add40e9375153a50', 'msg_type': 'execute_request', 'username': 
'buildd', 'session': '903e4bd4-9ea897ba7f841240791a9cec', 'date': 
datetime.datetime(2019, 10, 28, 13, 23, 4

Processed: Turning 936966 to a removal request

[Debian Bug Tracking System]

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

> severity 936966 normal
Bug #936966 [src:londonlaw] londonlaw: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> retitle  936966 RM: londonlaw -- ROM; removal triggered by the Python2 removal
Bug #936966 [src:londonlaw] londonlaw: Python2 removal in sid/bullseye
Changed Bug title to 'RM: londonlaw -- ROM; removal triggered by the Python2 
removal' from 'londonlaw: Python2 removal in sid/bullseye'.
> reassign 936966 ftp.debian.org
Bug #936966 [src:londonlaw] RM: londonlaw -- ROM; removal triggered by the 
Python2 removal
Bug reassigned from package 'src:londonlaw' to 'ftp.debian.org'.
No longer marked as found in versions londonlaw/0.2.1-20.
Ignoring request to alter fixed versions of bug #936966 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#935672: marked as done (librust-backtrace+addr2line-dev/amd64 unsatisfiable Depends: librust-addr2line-0.9+std-dev)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 21:36:31 +
with message-id 
and subject line Bug#935672: fixed in rust-backtrace 0.3.40-1
has caused the Debian Bug report #935672,
regarding librust-backtrace+addr2line-dev/amd64 unsatisfiable Depends: 
librust-addr2line-0.9+std-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.)


-- 
935672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-backtrace
Version: 0.3.34-1
Severity: serious
Affects: src:rust-addr2line
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

The rust-backtrace package depends on a newer rust-addr2line than is
available in the Debian archive.

librust-backtrace+addr2line-dev/amd64 unsatisfiable Depends: 
librust-addr2line-0.9+std-dev

Only rust-addr2line 0.7 is currently available.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rust-backtrace
Source-Version: 0.3.40-1

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

Debian distribution maintenance software
pp.
Wolfgang Silbermayr  (supplier of updated 
rust-backtrace 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, 24 Dec 2019 21:20:07 +
Source: rust-backtrace
Architecture: source
Version: 0.3.40-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Wolfgang Silbermayr 
Closes: 935672
Changes:
 rust-backtrace (0.3.40-1) unstable; urgency=medium
 .
   * Package backtrace 0.3.40 from crates.io using debcargo 2.4.0
   * Closes: #935672
Checksums-Sha1:
 f1addc57515f9597b86fa75148ecb79e58ac3224 3278 rust-backtrace_0.3.40-1.dsc
 1e43fddd0b40aa95220dbb43946e95c85885e66e 64696 
rust-backtrace_0.3.40.orig.tar.gz
 1849682521da1dd412a056b51aa46ed94b57f529 4128 
rust-backtrace_0.3.40-1.debian.tar.xz
 95c1d0d2642920cfcfeedbae0edf51176da6c9ee 6956 
rust-backtrace_0.3.40-1_source.buildinfo
Checksums-Sha256:
 fc8203cbfa9c5dcbc9319edf49a5a0debd67b5f46a7b01ae3892115e1a7c75f3 3278 
rust-backtrace_0.3.40-1.dsc
 0ac10bef49db9dea3f77edef7742f09c5e33e01b30b0462c6954ef19285ab37a 64696 
rust-backtrace_0.3.40.orig.tar.gz
 a27fa71cf69f585d65ad66054ff7dae2ed04c9aeeb74014a44965791a4a62a53 4128 
rust-backtrace_0.3.40-1.debian.tar.xz
 5fc9c3880484cfd644a7f5e54dc0d7aa8fca297a66248cfb27558c992e459874 6956 
rust-backtrace_0.3.40-1_source.buildinfo
Files:
 bb6a725923200163e571c2e0c19379ec 3278 rust optional rust-backtrace_0.3.40-1.dsc
 3a24e39b15a12a7ebc3cfbd5be5dcee7 64696 rust optional 
rust-backtrace_0.3.40.orig.tar.gz
 a6cd2f9fd1715f13106d85ca0b22acc3 4128 rust optional 
rust-backtrace_0.3.40-1.debian.tar.xz
 91293f64306d1c04fb770459165448d4 6956 rust optional 
rust-backtrace_0.3.40-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXgKBCgAKCRDrH8jaRfsp
MLecAP9IsAtmjyVsAaipYrf2bAwNSjbwUOjiIv8BTTqBqWuaaAEAoq9L5ypr1x4j
++ncLCGT6sJmgQmHxxW5TxxDIjI+JAQ=
=jyhs
-END PGP SIGNATURE End Message ---

Bug#910945: marked as done (fontcustom: autopkgtest fails)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 21:04:53 +
with message-id 
and subject line Bug#910945: fixed in fontcustom 2.0.0+ds4-5.1
has caused the Debian Bug report #910945,
regarding fontcustom: autopkgtest fails
to be marked as done.

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

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


-- 
910945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontcustom
Version: 2.0.0+ds4-5

The fontcustom autopkgtest fails.

https://ci.debian.net/packages/f/fontcustom/testing/amd64/

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: fontcustom
Source-Version: 2.0.0+ds4-5.1

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated fontcustom 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, 19 Dec 2019 20:02:14 +0100
Source: fontcustom
Architecture: source
Version: 2.0.0+ds4-5.1
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Viau 
Changed-By: Paul Gevers 
Closes: 910945 936537
Changes:
 fontcustom (2.0.0+ds4-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Convert to Python 3, thanks to Graham Inggs (Closes: #936537)
   * gemspec: update json to 2.0, thanks to Alexandre Viau (Closes:
 #910945)
   * Drop "Testsuite: autopkgtest-pkg-ruby" as it isn't testing anything
 and requires more non-trivial work to get it working
Checksums-Sha1:
 70884b65de7ef9ee02b894ac40ac1bc513dff47d 1683 fontcustom_2.0.0+ds4-5.1.dsc
 da2ac0ac6e1e0908660e5a2080c28165c2f6dc90 3764 
fontcustom_2.0.0+ds4-5.1.debian.tar.xz
Checksums-Sha256:
 7b6cab1adba64a8225580cb1deb3ad51613ad91686e864c8546a39ae7fb90315 1683 
fontcustom_2.0.0+ds4-5.1.dsc
 264414c953668189f1e1738e3901a9c73da29a381b1ed978f43c9949b523340b 3764 
fontcustom_2.0.0+ds4-5.1.debian.tar.xz
Files:
 02a7f4ae1019e404796c57fe2464f7d1 1683 fonts optional 
fontcustom_2.0.0+ds4-5.1.dsc
 d949e75cb1762517abdf6ddedf78a3ae 3764 fonts optional 
fontcustom_2.0.0+ds4-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl372kMACgkQnFyZ6wW9
dQo9bAf+KAVWzCjrfy2wqkZFLAwpodHsUR8M0FQ26VLSiafmd0a/dvlepKo7s9yK
o43/c7qpqaZOY3A73ueAUBiheWmBo0lAtVi1yVBynaJ/e4DDXxY8Hr+7cHHmH8/p
txS2osmP1AqT2rPJ8b0CKkt7/Sreuk0rcL0eEBNZ3G+BaKSJ3fAwOv2kd22ogsfy
rciAcez3wchsvxoqYBe/8yu380kuhit8QRXfsy+mArTOlgizj4eYO105N2P0vG+4
atvx1Svpq1YC/NcuMu3C3FTxv6OIcjxjhm4gbTSHx1Z57TBMwjTRF01bV5X6zb6Y
oeVB0Gh4vdNdrju7mqOLudVAv9DqlA==
=q8Z6
-END PGP SIGNATURE End Message ---

Bug#946837: marked as done (vagrant: Does not work with virtualbox 6.1 from unstable)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 20:47:34 +
with message-id 
and subject line Bug#946837: fixed in vagrant 2.2.6+dfsg-2
has caused the Debian Bug report #946837,
regarding vagrant: Does not work with virtualbox 6.1 from unstable
to be marked as done.

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

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


-- 
946837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vagrant
Version: 2.2.6+dfsg-1
Severity: serious

Hi!

The package does not work anymore since virtualbox 6.1 got upload to
unstable.

To get this working this just requires a couple of changes, which can
be easily applied as a local patch. Something like what is described
at .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.2.6+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated vagrant 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, 24 Dec 2019 16:54:36 -0300
Source: vagrant
Architecture: source
Version: 2.2.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 946837 946838
Changes:
 vagrant (2.2.6+dfsg-2) unstable; urgency=medium
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Antonio Terceiro ]
   * Add patch to avoid /etc/exports growing forever
   * Add patch for VirtualBox 6.1 support (Closes: #946837)
   * Add Breaks: on unsupported VirtualBox versions (Closes: #946838)
Checksums-Sha1:
 639f31dce19e73125c36f91a6acf0a3ae8c4c419 2468 vagrant_2.2.6+dfsg-2.dsc
 7e6581e100df41ee0c0f82b4fb39be2b909efe4a 14040 
vagrant_2.2.6+dfsg-2.debian.tar.xz
 33136ed7eb96eddba6e961943b06441d847aa843 13280 
vagrant_2.2.6+dfsg-2_source.buildinfo
Checksums-Sha256:
 df5540a7498b6fd13603b046c5f1aa922c5794265a6f997189f3245bb7d97fe7 2468 
vagrant_2.2.6+dfsg-2.dsc
 560613cf54bcd31582fc07ece65c16fe67643d32a3d0d853056183867d666d38 14040 
vagrant_2.2.6+dfsg-2.debian.tar.xz
 142b118cd9a8ca47b560d43bde8a1746dc234f6d8b3748e0394bc08288663c61 13280 
vagrant_2.2.6+dfsg-2_source.buildinfo
Files:
 5d416b695de28987a92b8362177a020c 2468 admin optional vagrant_2.2.6+dfsg-2.dsc
 9362d6763eadffac029b2ab13e7515c9 14040 admin optional 
vagrant_2.2.6+dfsg-2.debian.tar.xz
 5a6e060c4ab2061d4cd0cac369bdc4c4 13280 admin optional 
vagrant_2.2.6+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAl4CbbAACgkQ/A2xu81G
C94s7Q//YWDVDUxUMEYCopVIr8wiD5JN6oCfbrSFdz8VDcg4O9vv7mOhH2l7fUaG
pxdUume1gf0lzmIQx9444qsO965a92hL7/fj6L0zZs2hVN+hRcw87DqQjZAqM0Ye
cGa36Bh2NC8u/g2uJBm/6Cz3KAzKMH21P2enK8QspZqIy84+yefLlfgA8Tz1mq8F
7xVbc2dH1CT5/mPeacGhMqMB0oPGcnZI1A37Vvy1HuiI0KQuTPI4m/RHMmISiEtk
N1/Wv1uByK7OtRQyMu2vXCmnpr+gFPVbOHfNpCIOKR8RporouVW04If1trlmK03k
j5t2VN2KRnuCbDepa7xT/XRB/lZtuaaHD5niJpyHrXwaBWxu2mYCdVUA7JkTFQ7V
K5PtVj1euqqGRkLjQLROw4SU6hz0hNnezBJTsohRBsEifMYl2xzMyrrGxHN6dQ+2
4pfslhyz5jsjCNWP5J987i4+DTex1I4dPEXSo7syrqEbragD0co5sZ8IttHhV1pE
dde5hWgylkqeZXoPokfHCGttcEW0Kwt5EVFo2Dwe6VRIWlDBE3czM5eYMFZX1w+a
XRfVDV6t7kv/QhMwTz7ymoqYfJnrCmwqQViovzMWsLlu8QEBPVX2Q1Uh7AfQg1z0
IyP4sVn687JzpQehl5aSCTCWz01qlHYEAvwhDVauRjF4xVLPYCo=
=EB0+
-END PGP SIGNATURE End Message ---

Bug#947252: marked as done (deepin-qt5dxcb-plugin FTBFS: Project ERROR: x11-xcb development package not found)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 20:38:21 +
with message-id 
and subject line Bug#947252: fixed in deepin-qt5dxcb-plugin 5.0.1-3
has caused the Debian Bug report #947252,
regarding deepin-qt5dxcb-plugin FTBFS: Project ERROR: x11-xcb development 
package not found
to be marked as done.

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

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


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

deepin-qt5dxcb-plugin fails to build from source since very recently.
Five days ago, it still cross built:
http://crossqa.debian.net/src/deepin-qt5dxcb-plugin

Now it fails (cross and native):
|dh_auto_configure
| qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed" "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed" 
QMAKE_STRIP=: PREFIX=/usr
| Info: creating stash file /<>/.qmake.stash
|dh_auto_build
| make -j8
| make[1]: Entering directory '/<>'
| cd platformplugin/ && ( test -e Makefile.qt5platform-plugin || 
/usr/lib/qt5/bin/qmake -o Makefile.qt5platform-plugin 
/<>/platformplugin/qt5platform-plugin.pro 'QMAKE_CFLAGS_RELEASE=-g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CXXFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2' 'QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed' 'QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' 
QMAKE_STRIP=: PREFIX=/usr ) && make -f Makefile.qt5platform-plugin
| sh: 1: git: not found
| Project MESSAGE: /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms
| Project ERROR: x11-xcb development package not found
| make[1]: *** [Makefile:47: 
sub-platformplugin-qt5platform-plugin-pro-make_first] Error 3
| make[1]: Leaving directory '/<>'
| dh_auto_build: make -j8 returned exit code 2
| make: *** [debian/rules:20: binary] Error 255
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

I guess something around it changed and makes it ftbfs now.

Helmut
--- End Message ---
--- Begin Message ---
Source: deepin-qt5dxcb-plugin
Source-Version: 5.0.1-3

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated deepin-qt5dxcb-plugin 
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, 24 Dec 2019 12:52:11 -0500
Source: deepin-qt5dxcb-plugin
Architecture: source
Version: 5.0.1-3
Distribution: unstable
Urgency: high
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang 
Closes: 947252
Changes:
 deepin-qt5dxcb-plugin (5.0.1-3) unstable; urgency=high
 .
   * debian/control: Add missing build-dependencies.
 (Closes: #947252)
Checksums-Sha1:
 a7ff858e9923a2165998cf314dc6f0ac818858e7 2640 deepin-qt5dxcb-plugin_5.0.1-3.dsc
 a5327587977de5f24f0f0c786a82ba2fcdf0a1c5 23868 
deepin-qt5dxcb-

Bug#937900: [pkg-lxc-devel] Bug#937900: python-lxc: Python2 removal in sid/bullseye

[Antonio Terceiro]

On Thu, Dec 19, 2019 at 07:58:15PM +, Evgeni Golov wrote:
> Hi Moritz,
> 
> yeah, that sounds reasonable.
> 
> PEB, terceiro, any objections?

nope, just go ahead


signature.asc
Description: PGP signature

Bug#936932: marked as done (libvigraimpex: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 19:00:15 +
with message-id 
and subject line Bug#936932: fixed in libvigraimpex 1.11.1+dfsg-3
has caused the Debian Bug report #936932,
regarding libvigraimpex: 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.)


-- 
936932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg1-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:libvigraimpex

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

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

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

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

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated libvigraimpex 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Dec 2019 18:20:46 +0100
Source: libvigraimpex
Binary: libvigraimpex-dev libvigraimpex-doc libvigraimpex11 
libvigraimpex11-dbgsym python-vigra-doc python3-vigra python3-vigra-dbgsym
Architecture: source amd64 all
Version: 1.11.1+dfsg-3
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Metzler 
Description:
 libvigraimpex-dev - development files for the C++ computer vision library
 libvigraimpex-doc - Documentation for the C++ computer vision library
 libvigraimpex11 - C++ computer vision library
 python-vigra-doc - Documentation for Python3 bindings for the C++ computer 
vision li
 python3-vigra - Python3 bindings for the C++ computer vision library
Closes: 852052 936932
Changes:
 libvigraimpex (1.11.1+dfsg-3) experimental; urgency=medium
 .
   [ Daniel Stender ]
   * Orphaning package.
 .
   [ Andreas Tille ]
   * debhelper-compat 12
   *

Bug#947330: FTBFS: *** No rule to make target 'libc2b.a', needed by '../bin/cb2bib'. Stop.

[Lisandro Damián Nicanor Pérez Meyer]

Source: cb2bib
Version: 1.9.9-1
Severity: serious
Justification: FTBFS

Hi! During a rebuild of your package it FTBFS with the following error:

g++ -pipe -g -O2 -fdebug-prefix-map=/<>/debian/build/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -dM -E -o 
moc_predefs.h /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/data/dummy.cpp
make[3]: *** No rule to make target 'libc2b.a', needed by '../bin/cb2bib'.  
Stop.

Thanks for your work, Lisandro.

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

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

Bug#947329: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

[Lisandro Damián Nicanor Pérez Meyer]

Source: bppphyview
Version: 0.6.1-1
Severity: serious
Justification: FTBFS

Hi! During a rebuild of your package it FTBFS with the following error:

dh_installman: mv debian/bppphyview/usr/share/man/man1/phyview.1.dh-new 
debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

Thanks for your work!

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

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

Bug#947328: FTBFS: dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory

[Lisandro Damián Nicanor Pérez Meyer]

Source: xca
Version: 2.1.2-2
Severity: serious
Justification: FTBFS

Hi! During a rebuild your package FTBFS with the following error:

dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new 
debian/xca/usr/share/man/man1/xca.1: No such file or directory

Thanks for your work!

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

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

Bug#947327: FTBFS: /usr/bin/env: ‘python’: No such file or directory

[Lisandro Damián Nicanor Pérez Meyer]

Source: poppler
Version: 0.71.0-6
Severity: serious
Justification: FTBFS

Hi! During a rebuild of your package it FTBFS with the following error:

[ 58%] Generating glib-docs-build.stamp
cd /<>/obj-x86_64-linux-gnu/glib/reference && 
../../../make-glib-api-docs --src-dir=/<> 
--build-dir=/<>/obj-x86_64-linux-gnu
/usr/bin/env: ‘python’: No such file or directory
make[3]: *** [glib/reference/CMakeFiles/glib-docs.dir/build.make:64: 
glib/reference/glib-docs-build.stamp] Error 127
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:672: 
glib/reference/CMakeFiles/glib-docs.dir/all] Error 2

Thanks for your work, Lisandro.

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

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

Bug#947326: dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC

[Lisandro Damián Nicanor Pérez Meyer]

Source: antimony
Version: 0.9.3-1
Severity: serious
Justification: FTBFS

Hi! While rebuilding your package against a new Qt version it FTBFS due to some 
python error:

dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=cmake
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 
1.
BEGIN failed--compilation aborted at (eval 10) line 1.

Thnaks for your work, Lisandro.

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

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

Bug#947325: snapd: strict confinement is not enabled

[Mattia Monga]

Package: snapd
Version: 2.42.1-1
Severity: grave
Tags: security
Justification: user security hole

If one installs the example snap hello-world and launches hello-world.evil in 
apparmored system the application is NOT strictly confined by default.

~$ snap run hello-world.evil
Hello Evil World!
This example demonstrates the app confinement
You should see a permission denied error next
If you see this line the confinement is not working correctly, please file a bug


My snap debug info

~$ snap debug confinement
partial

~$ snap debug sandbox-features
apparmor: kernel:caps kernel:domain kernel:file kernel:mount 
kernel:namespaces kernel:network_v8 kernel:policy kernel:ptrace kernel:query 
kernel:rlimit kernel:signal parser:unsafe policy:downgraded 
support-level:partial
confinement-options:  classic devmode
dbus: mediated-bus-access
kmod: mediated-modprobe
mount:freezer-cgroup-v1 layouts mount-namespace 
per-snap-persistency per-snap-profiles per-snap-updates per-snap-user-profiles 
stale-base-invalidation
seccomp:  bpf-actlog bpf-argument-filtering kernel:allow 
kernel:errno kernel:kill_process kernel:kill_thread kernel:log kernel:trace 
kernel:trap kernel:user_notif
udev: device-cgroup-v1 tagging

I believe the default setting should be "strict" or, at least, the package 
should have clear documentation on how to enable the strict mode (which, 
according to upstream, is the default...) 




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

Kernel: Linux 5.3.15 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages snapd depends on:
ii  adduser  3.118
ii  apparmor 2.13.3-7
ii  ca-certificates  20190110
ii  gnupg2.2.17-3
ii  libapparmor1 2.13.3-7
ii  libc62.29-6
ii  libcap2  1:2.27-1
ii  libseccomp2  2.4.2-2
ii  libudev1 244-3
ii  openssh-client   1:8.1p1-2
ii  squashfs-tools   1:4.4-1
ii  systemd  244-3
ii  udev 244-3

Versions of packages snapd recommends:
ii  gnupg  2.2.17-3

Versions of packages snapd suggests:
ii  zenity  3.32.0-4

-- no debconf information

Bug#947266: marked as done (python3-geopandas: ships /usr/lib/python3/dist-packages/examples/*)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 17:19:17 +
with message-id 
and subject line Bug#947266: fixed in python-geopandas 0.6.2-2
has caused the Debian Bug report #947266,
regarding python3-geopandas: ships /usr/lib/python3/dist-packages/examples/*
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.)


-- 
947266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-geopandas
Version: 0.6.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

python3-geopandas ships files with generic names at the generic location
/usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on
README.txt) with other packages doing the same wrong thing.
Moving this to /usr/lib/python3/dist-packages/examples/geopandas/ should
probably be OK.


Andreas
--- End Message ---
--- Begin Message ---
Source: python-geopandas
Source-Version: 0.6.2-2

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

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

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated python-geopandas 
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, 24 Dec 2019 17:48:27 +0100
Source: python-geopandas
Architecture: source
Version: 0.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 947266
Changes:
 python-geopandas (0.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop Name field from upstream metadata.
   * Don't install examples.
 (closes: #947266)
Checksums-Sha1:
 5607dee990083464d449d0aca7252c8854d26b18 2408 python-geopandas_0.6.2-2.dsc
 6df188cce93f30a252264393c07e4df5ebf3d28b 1321672 
python-geopandas_0.6.2-2.debian.tar.xz
 a256a57f902676c262f85699cc59bdb02ece6b96 13135 
python-geopandas_0.6.2-2_amd64.buildinfo
Checksums-Sha256:
 fc674b504cb6a26b1725303505f01ea38e57a0202cc0d3b01fb6229ebdc540c4 2408 
python-geopandas_0.6.2-2.dsc
 7068e0e384743e686fa5c3e729e329899589879f89396b98103f7ad3c0747306 1321672 
python-geopandas_0.6.2-2.debian.tar.xz
 dd00986e41577d9afb0187733e6dad64bd6c03fe6f52132f52d8201992bc9b4f 13135 
python-geopandas_0.6.2-2_amd64.buildinfo
Files:
 4a1d51dc9e5479e1f81e2f15ee64bb23 2408 python optional 
python-geopandas_0.6.2-2.dsc
 ac99583a9b1293808fab0bd06091118a 1321672 python optional 
python-geopandas_0.6.2-2.debian.tar.xz
 eeb574323a95d7bf3a228481d240ffb9 13135 python optional 
python-geopandas_0.6.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl4CRNIACgkQZ1DxCuiN
SvFkhBAA1sltluVoZHbjdM5VZCC3piUG3OazKdNTSQMalI3kLn2Zp+AoPWtTM8Jn
3LqJ6WBPZBCHYf+/mhVENlyE0MnMvFDNOuk9NFT2DXykrBonJU9qceRkrYLMCcLf
lCxLY2XO5LGnb5oPsYlDdXUOJGlDPBAHl9eN5RegUDfgkRYM5qUme60vrEhtan73
5Rpk/iDsoMWnaqTwwCi/KCzB+SfmCATaG7vz5QDT1GZRbS0/NHGcnRqX5LDfphS/
lYBlE5oWaBIdZpXvJnbXVDF0uxbCIHhD5X3kEoQ3OKoxCnWSB7e3XU6h7Lx6KRXA
pWNHhVGsbnBYNTn+lUpcqIBIf/ht3yBLsJg/7jH3UUQn/oYD62QR6xiFghFxSNkn
kU2604rv98P5R2qQmu18Slpzkgq+WFrvkpoMrUGgAL+CgmZdxQ2Rxu6cOv/r7JyS
Dy4C4NcnnfDtdLvIvvkhGGKGaIbj1wZZrpQDiyM1WQYIWKGz7R3gSnn8GzMhC/sU
5DpyjHnPgtutKaHNLYk90xoxQGO4FIAoDprAN6yzo3+230/Pm4BDwu/tjtcIHt17
PnYa7yatgCdc1JpQvps4658dUu1xMDp9ve6QQlaY520BEdCWFvlngUgZPE9EJqrG
1m4JfAYTkZYhVKQ226EOO9rhzwtE1sh4/rj89WkN6qWsSe3EfNk=
=EJqL
-END PGP SIGNATURE End Message ---

Bug#938358: marked as done (responses: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 16:04:59 +
with message-id 
and subject line Bug#938358: fixed in responses 0.9.0-2
has caused the Debian Bug report #938358,
regarding responses: 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.)


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

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated responses 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, 24 Dec 2019 10:47:48 -0500
Source: responses
Architecture: source
Version: 0.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938358
Changes:
 responses (0.9.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * d/changelog: Remove trailing whitespaces
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938358
Checksums-Sha1:
 4f22c71e256434cc46e6a8099230c6ca5cd717e7 2127 responses_0.9.0-2.dsc
 e19c668f4afff2e7ab537d3a9479b995b90d3559 2892 responses_0.9.0-2.debian.tar.xz
 31811bdaabef66bc7fb85cae70f6c92ea09e6580 7079 
responses_0.9.0-2_source.buildinfo
Checksums-Sha256:
 971601c4bdd7aad09fd3a296512daa020210b4deb316ae685caa264dcfe0a596 2127 
responses_0.9.0-2.dsc
 4706bf25e4a256d7568c227bc57f797eb59fd6b68354bcf84ea1b4987c

Bug#947216: yapps2: should this package be removed?

[Colin Watson]

On Mon, Dec 23, 2019 at 06:29:05PM -0500, Sandro Tosi wrote:
> Colin Watson wrote:
> > I've made a DELAYED/10 NMU to fix these bugs, as well as removing the
> > Python 2 binary package and fixing #911730.  I think that gets things
> 
> thanks for quickly addressing this. I think you can upload your NMU
> directly to unstable, the maintainer doesnt seem responsive and you're
> fixing an RC bug.

The maintainer replied to ack my NMU, so I rescheduled it and it's been
accepted now.

Thanks,

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

Processed: py2removal RC severity updates - 2019-12-24 15:40:36.175437+00:00

[Debian Bug Tracking System]

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

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

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

Bug#936924: Moving libsvm to Debian Science team

[Chen-Tse Tsai]

Thanks, Andreas.

I just submitted a PR for dropping python2 dependencies:
https://salsa.debian.org/science-team/libsvm/merge_requests/1

Any comment is appreciated. I'll be working on upgrading to new upstream.

Thanks,
Chen-Tse


On Mon, Dec 23, 2019 at 4:03 PM Andreas Tille  wrote:

> On Mon, Dec 23, 2019 at 03:06:37PM -0500, Chen-Tse Tsai wrote:
> > I have a quick question. Previously the python modules are installed to
> > /usr/share/pyshared/. Should I use /usr/lib/python3/dist-packages instead
> > if I change it to python3? I see this in the policy and this is also what
> > liblinear uses. Just want to double check.
>
> Yes, follow liblinear example.
>
> Thanks for your work on this
>
>  Andreas.
>
> --
> http://fam-tille.de
>

Bug#938864: marked as done (yapps2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 15:23:11 +
with message-id 
and subject line Bug#938864: fixed in yapps2 2.2.1-3.1
has caused the Debian Bug report #938864,
regarding yapps2: 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.)


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

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

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

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated yapps2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Dec 2019 22:05:40 +
Source: yapps2
Architecture: source
Version: 2.2.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Urlichs 
Changed-By: Colin Watson 
Closes: 911730 911752 911753 938864
Changes:
 yapps2 (2.2.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop Python 2 support (closes: #938864).
   * Write __future__ import before preparser (closes: #911730).
   * Convert Scanner.print_line_with_pointer to Python 3 print syntax
 (closes: #911753).
   * Port documentation and examples to Python 3 (closes: #911752).
Checksums-Sha1:
 77406f76605477f548eea44d73a9e940de9df3c6 1874 yapps2_2.2.1-3.1.dsc
 313e50cde0130e208ac23ece88bc1ce7907efea5 28477 yapps2_2.2.1-3.1.diff.gz
Checksums-Sha256:
 c8cac3ea6c16d3854b221ea637a7ed47e3af9d75315963f07196db374f31 1874 
yapps2_2.2.1-3.1.dsc
 b41f6ec42dadb3ce55d45bc9e068f5713e69b453e9098313c4fac73d626fea68 28477 
yapps2_2.2.1-3.1.diff.gz
Files:
 4edea926922e2d5776e8b469d1f32cd2 1874 p

Bug#947319: missing directory

[Jérôme Bouat]

It seems a directory is missing :
---
Could not enumerate user data directory /var/lib/lightdm/data: Error opening 
directory '/var/lib/lightdm/data': No such file or directory
---

I attached the last lines of my /var/log/syslog
Dec 24 15:31:43 l systemd[1]: anacron.service: Succeeded.
Dec 24 15:39:30 l systemd[1]: Starting Cleanup of Temporary Directories...
Dec 24 15:39:31 l systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Dec 24 15:39:31 l systemd[1]: Started Cleanup of Temporary Directories.
Dec 24 15:47:42 l systemd[1]: Started Getty on tty2.
Dec 24 15:47:47 l systemd[1]: Started Session 5 of user j.
Dec 24 16:05:02 l systemd[1]: Stopping Authorization Manager...
Dec 24 16:05:02 l systemd[1]: Stopped target Sound Card.
Dec 24 16:05:02 l systemd[1]: Stopping Save/Restore Sound Card State...
Dec 24 16:05:02 l systemd[1]: Stopped target Graphical Interface.
Dec 24 16:05:02 l systemd[1]: Stopped target Multi-User System.
Dec 24 16:05:02 l systemd[1]: Stopped target Login Prompts.
Dec 24 16:06:37 l systemd-modules-load[168]: Inserted module 'firewire_sbp2'
Dec 24 16:06:37 l systemd[1]: Starting Flush Journal to Persistent Storage...
Dec 24 16:06:37 l systemd[1]: Started Flush Journal to Persistent Storage.
Dec 24 16:06:37 l systemd[1]: Started Set the console keyboard layout.
Dec 24 16:06:37 l systemd[1]: Reached target Local File Systems (Pre).
Dec 24 16:06:37 l systemd[1]: Started udev Kernel Device Manager.
Dec 24 16:06:37 l systemd-udevd[197]: Using default interface naming scheme 
'v240'.
Dec 24 16:06:37 l systemd-udevd[197]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
Dec 24 16:06:37 l systemd-udevd[202]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
Dec 24 16:06:37 l systemd[1]: Condition check resulted in Rebuild Hardware 
Database being skipped.
Dec 24 16:06:37 l systemd[1]: Condition check resulted in FUSE Control File 
System being skipped.
Dec 24 16:06:37 l systemd[1]: Condition check resulted in File System Check on 
Root Device being skipped.
Dec 24 16:06:37 l systemd[1]: Condition check resulted in Set Up Additional 
Binary Formats being skipped.
Dec 24 16:06:37 l systemd[1]: Condition check resulted in Kernel Configuration 
File System being skipped.
Dec 24 16:06:37 l systemd[1]: Found device RTL-8100/8101L/8139 PCI Fast 
Ethernet Adapter.
Dec 24 16:06:37 l systemd[1]: Found device FUJITSU_MHM2100AT 5.
Dec 24 16:06:37 l systemd[1]: Activating swap 
/dev/disk/by-uuid/03a421c3-c67f-4c3a-8731-8b01bf8b9571...
Dec 24 16:06:37 l systemd[1]: Activated swap 
/dev/disk/by-uuid/03a421c3-c67f-4c3a-8731-8b01bf8b9571.
Dec 24 16:06:37 l systemd[1]: Reached target Swap.
Dec 24 16:06:37 l systemd[1]: tmp.mount: Directory /tmp to mount over is not 
empty, mounting anyway.
Dec 24 16:06:37 l systemd[1]: Mounting /tmp...
Dec 24 16:06:37 l systemd[1]: Mounted /tmp.
Dec 24 16:06:37 l systemd[1]: Reached target Local File Systems.
Dec 24 16:06:37 l systemd[1]: Condition check resulted in Commit a transient 
machine-id on disk being skipped.
Dec 24 16:06:37 l systemd[1]: Starting Set console font and keymap...
Dec 24 16:06:37 l systemd[1]: Starting Load AppArmor profiles...
Dec 24 16:06:37 l systemd[1]: Starting Create Volatile Files and Directories...
Dec 24 16:06:37 l systemd[1]: Started Set console font and keymap.
Dec 24 16:06:37 l systemd[1]: Started Create Volatile Files and Directories.
Dec 24 16:06:37 l apparmor.systemd[256]: Restarting AppArmor
Dec 24 16:06:37 l apparmor.systemd[256]: Reloading AppArmor profiles
Dec 24 16:06:37 l systemd[1]: Starting Network Time Synchronization...
Dec 24 16:06:37 l systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Dec 24 16:06:37 l systemd[1]: Started Update UTMP about System Boot/Shutdown.
Dec 24 16:06:37 l kernel: [0.00] Linux version 4.19.0-6-686-pae 
(debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP 
Debian 4.19.67-2+deb10u2 (2019-11-11)
Dec 24 16:06:37 l kernel: [0.00] x86/fpu: x87 FPU will use FXSAVE
Dec 24 16:06:37 l kernel: [0.00] BIOS-provided physical RAM map:
Dec 24 16:06:37 l kernel: [0.00] BIOS-e820: [mem 
0x-0x0009f7ff] usable
Dec 24 16:06:37 l kernel: [0.00] BIOS-e820: [mem 
0x0009f800-0x0009] reserved
Dec 24 16:06:37 l kernel: [0.00] BIOS-e820: [mem 
0x000ea400-0x000f] reserved
Dec 24 16:06:37 l kernel: [0.00] BIOS-e820: [mem 
0x0010-0x0ffe] usable
Dec 24 16:06:37 l kernel: [0.00] BIOS-e820: [mem 
0x0fff-0x0bff] ACPI data
Dec 24 16:06:37 l kernel: [0.00] BIOS-e820: [mem 
0x0c00-0x0fff] ACPI NVS
Dec 24 16:06:37 l kernel: [0.00] BIOS-e820: [mem 
0xfffe-0x] reserved
Dec 24 16:06:37 l kernel: [0.00] Notice: NX (Execute Disable) 
protection missing in CPU!
Dec 24 16:06:37 l ker

Processed (with 1 error): forcibly merging 937012 947296

[Debian Bug Tracking System]

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

> forcemerge 937012 947296
Bug #937012 [src:mercurial-keyring] mercurial-keyring: Python2 removal in 
sid/bullseye
Bug #947296 [src:mercurial-keyring] mercurial-keyring: Python2 removal in 
sid/bullseye
Severity set to 'normal' from 'serious'
947296 was not blocked by any bugs.
947296 was blocking: 937009 937011 937695 937870 938168
Added blocking bug(s) of 947296: 937009
947296 was blocked by: 937009
947296 was blocking: 937009 937011 937695 937870 938168
Added blocking bug(s) of 947296: 937011
Bug #947296 [src:mercurial-keyring] mercurial-keyring: Python2 removal in 
sid/bullseye
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #947296 [src:mercurial-keyring] mercurial-keyring: Python2 removal in 
sid/bullseye
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #947296 [src:mercurial-keyring] mercurial-keyring: Python2 removal in 
sid/bullseye
After four attempts, the following changes were unable to be made:
blockedby of #947296 is '937009 937011' not '937011 937009'
Failed to forcibly merge 937012: Unable to modify bugs so they could be merged.

> thanks
Stopping processing here.

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

Bug#947319: lightdm: fails during startup (no invite)

[Jerome]

Package: lightdm
Version: 1.26.0-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
Fresh install.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I never saw lightdm working since I installed the new system.

   * What was the outcome of this action?
I can't use the graphical environnement.

   * What outcome did you expect instead?
Enable graphical environnement.

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

Kernel: Linux 4.19.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.16-1
ii  debconf [debconf-2.0]  1.5.71
ii  libaudit1  1:2.8.4-3
ii  libc6  2.28-10
ii  libgcrypt201.8.4-5
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libpam-systemd [logind]241-7~deb10u2
ii  libpam0g   1.3.1-5
ii  libxcb11.13.1-2
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.6-1
ii  lsb-base   10.2019051400

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
pn  accountsservice  
pn  upower   
pn  xserver-xephyr   

-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm

Processed: severity of 835340 is serious

[Debian Bug Tracking System]

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

> severity 835340 serious
Bug #835340 [python-pymetar] python-pymetar: http://weather.noaa.gov/ no longer 
available
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#944486: marked as done (libtrilinos-belos-dev: missing Breaks+Replaces: libtrilinos-muelu-dev (<< 12.14))

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 13:58:10 +
with message-id 
and subject line Bug#944486: fixed in trilinos 12.14.1-2
has caused the Debian Bug report #944486,
regarding libtrilinos-belos-dev: missing Breaks+Replaces: libtrilinos-muelu-dev 
(<< 12.14)
to be marked as done.

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

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


-- 
944486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtrilinos-belos-dev
Version: 12.14.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libtrilinos-belos-dev_12.14.1-1_amd64.deb ...
  Unpacking libtrilinos-belos-dev:amd64 (12.14.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtrilinos-belos-dev_12.14.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/trilinos/BelosOperatorT.hpp', which is 
also in package libtrilinos-muelu-dev:amd64 12.12.1-8
  Errors were encountered while processing:
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
   /var/cache/apt/archives/libtrilinos-belos-dev_12.14.1-1_amd64.deb


cheers,

Andreas


libtrilinos-muelu-dev=12.12.1-8_libtrilinos-belos-dev=12.14.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: trilinos
Source-Version: 12.14.1-2

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

Debian distribution maintenance software
pp.
Nico Schlömer  (supplier of updated trilinos 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, 24 Dec 2019 13:24:19 +
Source: trilinos
Architecture: source
Version: 12.14.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Nico Schlömer 
Closes: 944486 944688
Changes:
 trilinos (12.14.1-2) unstable; urgency=medium
 .
   [ Nico Schlömer ]
   * Fix multi-arch issue with Kokkos
   * Add Intrepid 2 (Closes: #944688)
 .
   [ Graham Inggs ]
   * Add iframeResizer v2.3.1 sources to debian/missing-sources
   * Add Breaks and Replaces on libtrilinos-muelu-dev (<< 12.14)
 to libtrilinos-belos-dev (Closes: #944486)
   * Double up the limit of debug information entries
Checksums-Sha1:
 21ed13edeec2ac04de8a2392f2750aa88298c1f6 12029 trilinos_12.14.1-2.dsc
 d00b29a4b22cfa3da8cf3d7ccb36556148b16e3f 25440 trilinos_12.14.1-2.debian.tar.xz
Checksums-Sha256:
 2da477ce3483299f851e6cea1714a77e02c57db69a7b17ba36bd2d0543c02ed8 12029 
trilinos_12.14.1-2.dsc
 4ad5382a498b19c4ea688e5de6d1d7cd247f0ac6908bea46326fec484f9189a1 25440 
trilinos_12.14.1-2.debian.tar.xz
Files:
 fc009ced1ce52f30ef8d960f5d8cd8a0 12029 science optional trilinos_12.14.1-2.dsc
 13289506504974bd726bccd0e39f0a0c 25440 science optional 
trilinos_12.14.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl4CE1cACgkQr8/sjmac
4cJbfhAAkYsHDVlkc/y5Mjikz9fyOpcQexifZ6TYqtWFTDQcdz1n6nmi5dfRJJTI
pmUkX3VAokAkytBvMtDFoI0z3Sjv7/kWcvn88Jxy3tGBOqWv9gJhgv4czPzGQQpF
62U6EGVqOEPhe9uwGmIknJhQoqKRnnfMC3urugq6zsPQqZZNGV0jRlvOxCAz0ywf
BhNjsqGBjJHcH3KID5/fF/2pKEK1sqS2XqE1V/rg3t3wA41tMPuRO5uc0ymWBZKk
6icc16OHGrdRsTjbLDhXL7OdSr0j6XSyT5hhJaMJBPOZvtS8eirJdPFgh+YM0hMQ
s+ImlU+rrI2rJBvtJ3QLLX9lmCIy8u9qqfujrRbcT1eCckhwZJ85NYOXDapFm9dU
bn7Js/5qMxB+7jXwKZt4VCo+tK4fkonnsO8JfZ9vFMVNVh1ysepVYIATZ4JmP5CE
8OvjrQ0Ti+5N+a9dE+U/TMGCv93INx3ZRT+HhwdCMoRYgc0hBHgyC1sfHunqrox7
abSaceXJxhdndLSIh1TOd7FNSTGCbw5k5TjcT03O0q5u2e4o8238RtcXfswuRDZO
Gf88LlmIvjrVQUSbuZN8O0bigIj37XGLnEBvAbzSMj586NtyOfDBW3PSnmHtRWRk
3RFsG91yjHPlf9vu4CuaoTo/gTZKWYwwta1flSf3WERJedt8fZ4=
=36Oa
-END PGP SIGNATURE End Message ---

Bug#944688: marked as done (trilinos: intrepid2 package is not shipped)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 13:58:10 +
with message-id 
and subject line Bug#944688: fixed in trilinos 12.14.1-2
has caused the Debian Bug report #944688,
regarding trilinos: intrepid2 package is not shipped
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.)


-- 
944688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deal.ii
Version: 9.1.1-6
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

Your package is part of the assimp transition. I scheduled binNMU's but you
package fails to build everywhere it build in the past.

Looking at the reproducible-builds infra, it seems your package started to
FTBFS before this transition with the same error. Maybe this is related to the
gcc-9 change?

Paul

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

Tail of log for deal.ii on amd64:

Source file was:

#include 

int main()
{
  int *i = new int;
  std::auto_ptr x(i);
  return 0;
}

dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
"-DDEAL_II_CXX_FLAGS=-Wno-nonnull-compare -Wno-address" 
-DCMAKE_PREFIX_PATH=/usr/lib/x86_64-linux-gnu/hdf5/openmpi\;/usr/include/hdf5/openmpi
 -DCMAKE_BUILD_TYPE=DebugRelease -DDEAL_II_ALLOW_AUTODETECTION=OFF 
-DDEAL_II_ALLOW_BUNDLED=OFF -DDEAL_II_ALLOW_PLATFORM_INTROSPECTION=OFF 
-DDEAL_II_HAVE_FP_EXCEPTIONS=FALSE -DDEAL_II_COMPONENT_DOCUMENTATION=ON 
-DDEAL_II_WITH_ARPACK=ON -DDEAL_II_WITH_ASSIMP=ON -DDEAL_II_WITH_BOOST=ON 
-DDEAL_II_WITH_BZIP2=ON -DDEAL_II_WITH_GMSH=ON -DDEAL_II_WITH_GSL=ON 
-DDEAL_II_WITH_HDF5=ON -DDEAL_II_WITH_LAPACK=ON -DDEAL_II_WITH_MPI=ON 
-DDEAL_II_WITH_MUPARSER=ON -DDEAL_II_WITH_NETCDF=ON 
-DDEAL_II_WITH_OPENCASCADE=ON -DDEAL_II_WITH_P4EST=ON -DDEAL_II_WITH_PETSC=ON 
-DDEAL_II_WITH_SCALAPACK=ON -DDEAL_II_WITH_SLEPC=ON -DDEAL_II_WITH_SUNDIALS=ON 
-DDEAL_II_WITH_THREADS=ON -DDEAL_II_WITH_TRILINOS=ON -DDEAL_II_WITH_UMFPACK=ON 
-DDEAL_II_WITH_ZLIB=ON -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=OFF 
-DDEAL_II_BASE_NAME=deal.ii 
-DDEAL_II_DOCHTML_RELDIR=share/doc/libdeal.ii-doc/html 
-DDEAL_II_DOCREADME_RELDIR=share/doc/libdeal.ii-doc 
-DDEAL_II_EXAMPLES_RELDIR=share/doc/libdeal.ii-doc/examples 
-DDEAL_II_LIBRARY_RELDIR=lib/x86_64-linux-gnu 
-DDEAL_II_PROJECT_CONFIG_RELDIR=share/cmake/deal.II 
-DDEAL_II_SHARE_RELDIR=share/deal.ii/ .. returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-arch] Error 2



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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3MWl4ACgkQnFyZ6wW9
dQrxEAf8CG69Mbfvso8sU1HZrRrDy4Qq7RB+vWDaWYd3MPuXGgsAS+B+h7oyqvJL
G6aCdWz9Z1YOXw5KLDi31R72O24GtBW5wqb9KKDWC049H3ACMXXIf6NU6+13Fsd+
iJZNOWn0C2MJ3KyJL5yrpTze+JAMOYHZXUqaT38EWcI1JoLqf7EchKKdTVPuNJLt
f9reZDe7/25D6e47BHOq5r1/PAkG5HhRe48v72adRW3LPIFY3l2NEv86nxzdfCoA
B4oQS+bDQTSHsct2y96ORkOpGfTBiwr9rq5uLU1dF66YXQQ+V7a09ZhOboUa48+x
+QeCc/XcN+/LADOH8dFWb0RnNhsECw==
=RTT1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: trilinos
Source-Version: 12.14.1-2

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

Debian distribution maintenance software
pp.
Nico Schlömer  (supplier of updated trilinos package)

(This message was generated automatically at their request; if you
believe that the

Processed: tagging 938076

[Debian Bug Tracking System]

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

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

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

Processed: tagging 835340

[Debian Bug Tracking System]

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

> tags 835340 + fixed-upstream
Bug #835340 [python-pymetar] python-pymetar: http://weather.noaa.gov/ no longer 
available
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 938051

[Debian Bug Tracking System]

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

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

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

Bug#947001: [R-pkg-team] Bug#947001: r-base blocked by r-bioc-{iranges, s4vectors}

[Dirk Eddelbuettel]

On 24 December 2019 at 09:34, Graham Inggs wrote:
| Control: severity -1 serious
| 
| On Mon, 23 Dec 2019 at 22:30, Dirk Eddelbuettel  wrote:
| > I would be very surprised if these were not self-inflicted by us. I know 
CRAN
| > (much) better than BioC, but both of them are doing extensive self-tests 
(and
| > generally without any arbitrary restrictions, say about timing and versions)
| > we may impose.
| 
| This situation reminds me of #877288, where I believe Debian's
| autopkgtests detected the problem before upstream.

Maybe, maybe not.  Here is the BioC build report for iranges and s4vectors:

  http://bioconductor.org/checkResults/3.10/bioc-LATEST/IRanges/
  http://bioconductor.org/checkResults/3.10/bioc-LATEST/S4Vectors/

"All green".

To me th likeliest cause is one of synchronization: BioC generally "steps" in
full releases dependenting on R releases, that does not map to our rolling
scheme. That is, to me, what happened in #877288 too -- R releases and BioC
releases out of step.  (And I still don't know what the best move would
be as thinks could break with either BioC release or devel...)

| > I tried a quick test on a Debian testing machine I use for (extensive)
| > reverse dependency checks (at the upstream level) but it was incloncusive.
| 
| Hopefully we get an answer from upstream BioConductor soon.

Well as shown above there is not bug they see.  

| > Still a pity that r-base is held back by this.
| 
| This is better than allowing a package that breaks others to migrate
| into testing.

What if the breakage is in fact self-inflicted?

| If there is no progress for some time, Release Team may remove
| r-bioc-iranges and r-bioc-s4vectors from testing to allow r-base to
| migrate, as in any other transition.

I guess we have to wait. I run R via the CRAN-ports-for-Ubuntu or via
unstable-on-testing so I have R 3.6.2 on both but it is not fair to our users
to withhold it.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#947313: python3-pecan: fails to install

[Bernd Zeimetz]

Package: python3-pecan
Version: 1.3.3-2
Severity: serious

python3-pecan fails to install:

Errors were encountered while processing:
 python3-pecan
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up python3-pecan (1.3.3-2) ...
update-alternatives: error: alternative path /usr/bin/python3-pecan doesn't 
exist
dpkg: error processing package python3-pecan (--configure):
 installed python3-pecan package post-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 python3-pecan


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#947310: mesa: FTBFS on mipsel: Cannot find (any matches for) "usr/lib/*/libvulkan_*.so"

[Simon McVittie]

Source: mesa
Version: 19.3.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

mesa doesn't seem to be building Vulkan drivers on mipsel, but the
Architecture field of mesa-vulkan-drivers says it should be:

https://buildd.debian.org/status/fetch.php?pkg=mesa&arch=mipsel&ver=19.3.1-2&stamp=1576796202&raw=0
> Vulkan drivers:  no
...
> dh_install -a
> dh_install: Cannot find (any matches for) 
> "usr/share/vulkan/explicit_layer.d/*.json" (tried in ., debian/tmp)
> 
> dh_install: mesa-vulkan-drivers missing files: 
> usr/share/vulkan/explicit_layer.d/*.json
> dh_install: Cannot find (any matches for) "usr/share/vulkan/icd.d/*.json" 
> (tried in ., debian/tmp)
> 
> dh_install: mesa-vulkan-drivers missing files: usr/share/vulkan/icd.d/*.json
> dh_install: Cannot find (any matches for) "usr/lib/*/libvulkan_*.so" (tried 
> in ., debian/tmp)
> 
> dh_install: mesa-vulkan-drivers missing files: usr/lib/*/libvulkan_*.so
> dh_install: Cannot find (any matches for) 
> "usr/lib/*/libVkLayer_MESA_overlay.so" (tried in ., debian/tmp)
> 
> dh_install: mesa-vulkan-drivers missing files: 
> usr/lib/*/libVkLayer_MESA_overlay.so
> dh_install: missing files, aborting

This might be because mipsel is present in the list of architectures where
LLVM is enabled (confflags_GALLIUM += -Dllvm=true etc.), and is present in
the list of architectures where the Vulkan loader is enabled
(confflags_VULKAN += -Dvulkan-overlay-layer=true), but is absent from the
list of architectures where VULKAN_DRIVERS += amd, despite that list being
documented as "only build on the subset of arches where we have LLVM enabled
and where the Vulkan loader is built".

smcv

Bug#943187: marked as done (qmidiarp: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 10:20:11 +
with message-id 
and subject line Bug#943187: fixed in qmidiarp 0.6.5-3
has caused the Debian Bug report #943187,
regarding qmidiarp: 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.)


-- 
943187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qmidiarp
Version: 0.6.5-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
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 there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: qmidiarp
Source-Version: 0.6.5-3

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated qmidiarp 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, 24 Dec 2019 10:56:25 +0100
Source: qmidiarp
Architecture: source
Version: 0.6.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 943187
Changes:
 qmidiarp (0.6.5-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ Olivier Humbert ]
   * Update copyright (http -> https + bump 2019)
 .
   [ Adrian Bunk ]
   * Build-depend on scour instead of python-scour (Closes: #943187)
 .
   [ Sebastian Ramacher ]
   * debian/: Bump debhelper compat to 12
   * debian/control: Bump Standards-Version
   * debian/copyright: Document appdata license
Checksums-Sha1:
 051d3e695529ab314f0ec47e3636b043633815e2 2074 qmidiarp_0.6.5-3.dsc
 ba284e4f50b96636786de8035889a31695ad993b 6936 qmidiarp_0.6.5-3.debian.tar.xz
Checksums-Sha256:
 179fd939b7ac01e64f88080ef9888be1a57ada226582e4a6c9d4a41b1b1a29d4 2074 
qmidiarp_0.6.5-3.dsc
 ff2f2541086e7847d8920cdba8d80fb13315ac7514368fffa8d6ce74c14d34a1 6936 
qmidiarp_0.6.5-3.debian.tar.xz
Files:
 8bcefe9500afd375d942511540284b66 2074 sound optional qmidi

Processed: severity of 947299 is wishlist, severity of 947300 is wishlist

[Debian Bug Tracking System]

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

> severity 947299 wishlist
Bug #947299 [src:hgsubversion] hgsubversion: Python2 removal in sid/bullseye
Severity set to 'wishlist' from 'serious'
> severity 947300 wishlist
Bug #947300 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

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

Bug#947306: waitress: CVE-2019-16785 CVE-2019-16786

[Salvatore Bonaccorso]

Source: waitress
Version: 1.3.1-4
Severity: grave
Tags: security upstream

Hi,

The following vulnerabilities were published for waitress, both are
fixed in new upstream version 1.4.0.

CVE-2019-16785[0]:
| Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230
| which states: "Although the line terminator for the start-line and
| header fields is the sequence CRLF, a recipient MAY recognize a single
| LF as a line terminator and ignore any preceding CR." Unfortunately if
| a front-end server does not parse header fields with an LF the same
| way as it does those with a CRLF it can lead to the front-end and the
| back-end server parsing the same HTTP message in two different ways.
| This can lead to a potential for HTTP request smuggling/splitting
| whereby Waitress may see two requests while the front-end server only
| sees a single HTTP message. This issue is fixed in Waitress 1.4.0.


CVE-2019-16786[1]:
| Waitress through version 1.3.1 would parse the Transfer-Encoding
| header and only look for a single string value, if that value was not
| chunked it would fall through and use the Content-Length header
| instead. According to the HTTP standard Transfer-Encoding should be a
| comma separated list, with the inner-most encoding first, followed by
| any further transfer codings, ending with chunked. Requests sent with:
| "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and
| the request would use a Content-Length header instead to determine the
| body size of the HTTP message. This could allow for Waitress to treat
| a single request as multiple requests in the case of HTTP pipelining.
| This issue is fixed in Waitress 1.4.0.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-16785
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16785
[1] https://security-tracker.debian.org/tracker/CVE-2019-16786
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16786

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: tagging 937923

[Debian Bug Tracking System]

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

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

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

Processed: tagging 937931

[Debian Bug Tracking System]

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

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

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

Bug#937730: Bug#934264: Please update (4.6.2?) and provide/switch to python3

[Andreas Tille]

On Tue, Dec 24, 2019 at 09:49:18AM +0200, Adrian Bunk wrote:
> 
> Works for me (with test failures later), but I am using plain chroot.
> 
> Problems related to running graphical tests are not something I would 
> care too much about right now, important would be that the package 
> builds and works.
> 
> After disabling the tests and dh_numpy -> dh_numpy3 in debian/rules the 
> package builds for me.
> 
> Trying to install the resulting package fails with:
> E: Package 'python3-wxgtk3.0' has no installation candidate
> E: Package 'python3-envisage' has no installation candidate
> 
> python3-wxgtk4.0 exists (not sure whether it also works with mayavi2).

I pushed all this to Git.
 
> python-envisage has not yet been converted to Python3 and seems to be 
> required:
> $ mayavi2
> Traceback (most recent call last):
>   File "/usr/bin/mayavi2", line 464, in 
> from mayavi.plugins.app import Mayavi, setup_logger
>   File "/usr/lib/python3/dist-packages/mayavi/plugins/app.py", line 19, in 
> 
> from .mayavi_workbench_application import MayaviWorkbenchApplication
>   File 
> "/usr/lib/python3/dist-packages/mayavi/plugins/mayavi_workbench_application.py",
>  line 13, in 
> from envisage.ui.workbench.api import WorkbenchApplication
> ModuleNotFoundError: No module named 'envisage'

That's recorded as TODO item in d/changelog now.

Thanks for all your hints, Andreas.

-- 
http://fam-tille.de

Processed: bug 937903 is forwarded to https://github.com/nobrin/macaron/issues/44

[Debian Bug Tracking System]

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

> forwarded 937903 https://github.com/nobrin/macaron/issues/44
Bug #937903 [src:python-macaron] python-macaron: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'https://github.com/nobrin/macaron/issues/44'.
> thanks
Stopping processing here.

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

Processed: reassign 947293 to src:libkate, forcibly merging 946632 947293

[Debian Bug Tracking System]

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

> reassign 947293 src:libkate 0.4.1-10
Bug #947293 [libkate] libkate: autopkgtest failures due to libkate-tools removal
Bug reassigned from package 'libkate' to 'src:libkate'.
No longer marked as found in versions 0.4.1-10.
Ignoring request to alter fixed versions of bug #947293 to the same values 
previously set
Bug #947293 [src:libkate] libkate: autopkgtest failures due to libkate-tools 
removal
Marked as found in versions libkate/0.4.1-10.
> forcemerge 946632 947293
Bug #946632 [src:libkate] libkate: autopkgtest regression: tests removed 
executables
Bug #946632 [src:libkate] libkate: autopkgtest regression: tests removed 
executables
Added tag(s) patch.
Bug #947293 [src:libkate] libkate: autopkgtest failures due to libkate-tools 
removal
Merged 946632 947293
> thanks
Stopping processing here.

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

Processed: tagging 937664

[Debian Bug Tracking System]

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

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

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

Processed: tagging 937682

[Debian Bug Tracking System]

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

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

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

Bug#947293: libkate: autopkgtest failures due to libkate-tools removal

[Sebastian Ramacher]

Control: forcemerge 946632 -1

On 2019-12-23 21:31:26, Steve Langasek wrote:
> Package: libkate
> Version: 0.4.1-10
> Severity: serious
> Tags: patch
> Justification: autopkgtest regression
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu focal ubuntu-patch
> 
> Dear maintainers,
> 
> With the removal of libkate-tools in libkate 0.4.1-10, the libkate
> autopkgtest consistently fails, because all of the commands it previously
> attempted to run were in the libkate-tools package:
> 
> [...]
> autopkgtest [12:55:24]: test test-cmd-tools:  - - - - - - - - - - stderr - - 
> - - - - - - - -
> /tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
>  25: kateenc: not found
> /tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
>  31: katalyzer: not found
> /tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
>  37: katedec: not found
> /tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
>  40: errorunable to run katedec: not found
> [...]
> 
>   
> (https://ci.debian.net/data/autopkgtest/unstable/amd64/libk/libkate/3520793/log.gz)

That's #946632.

> 
> I think the autopkgtest should simply be dropped, since there is nothing
> left for it to do at present.  Please see the attached patch.
> 
> Cheers,
> -- 
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developer   https://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org

> diff -Nru libkate-0.4.1/debian/tests/control 
> libkate-0.4.1/debian/tests/control
> --- libkate-0.4.1/debian/tests/control2019-11-26 16:03:42.0 
> -0600
> +++ libkate-0.4.1/debian/tests/control1969-12-31 18:00:00.0 
> -0600
> @@ -1,2 +0,0 @@
> -Depends: @
> -Tests: test-cmd-tools
> diff -Nru libkate-0.4.1/debian/tests/test-cmd-tools 
> libkate-0.4.1/debian/tests/test-cmd-tools
> --- libkate-0.4.1/debian/tests/test-cmd-tools 2019-11-26 16:03:42.0 
> -0600
> +++ libkate-0.4.1/debian/tests/test-cmd-tools 1969-12-31 18:00:00.0 
> -0600
> @@ -1,49 +0,0 @@
> -#!/bin/sh
> -#
> -# Test the kate command line tools to ensure they can run without
> -# returning an error.
> -
> -set -e
> -
> -retval=0
> -
> -success() { echo "success:" "$@"; }
> -error() { echo "error:" "$@"; retval=1; }
> -
> -cat > input.srt < -1
> -00:00:08,000 --> 00:00:14,000
> -This is a simple subtext block
> -that will be encoded into an ogg file.
> -
> -2
> -00:00:15,000 --> 00:00:16,000
> -This is the second subtext block.
> -
> -EOF
> -
> -if kateenc -t srt -l cy -c SUB -o output.ogg input.srt ; then
> -success "kateenc could encode an SRT file to OGG"
> -else
> -error "unable to run kateenc"
> -fi
> -
> -if katalyzer output.ogg ; then
> -success "running katalyzer worked"
> -else
> -error "unable to run katalyser"
> -fi
> -
> -if katedec output.ogg ; then
> -success "running katedec worked"
> -else
> -error"unable to run katedec"
> -fi
> -
> -if KateDJ  --version ; then
> -success "running KateDJ worked"
> -else
> -error "unable to run KateDJ"
> -fi
> -
> -exit $retval


-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: snowballz: Raising py2removal bug severity

[Debian Bug Tracking System]

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

> severity 938509 serious
Bug #938509 [src:snowballz] snowballz: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> stop
Stopping processing here.

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

Processed (with 1 error): Re: Bug#947293: libkate: autopkgtest failures due to libkate-tools removal

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 946632 -1
Bug #946632 [src:libkate] libkate: autopkgtest regression: tests removed 
executables
Unable to merge bugs because:
package of #947293 is 'libkate' not 'src:libkate'
Failed to forcibly merge 946632: Did not alter merged bugs.


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

Bug#946082: marked as done (should depend on shiboken2)

[Debian Bug Tracking System]

Your message dated Tue, 24 Dec 2019 08:45:58 +
with message-id 
and subject line Bug#946082: fixed in pyside2 5.13.2-2.1
has caused the Debian Bug report #946082,
regarding should depend on shiboken2
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.)


-- 
946082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libshiboken2-dev
Version: 5.13.2-2
Severity: important

Since PySide 5.13, the CMake files shipped in libshiboken2-dev have a
dependency on the /usr/bin/shiboken2 executable. If the shiboken2 package is
not installed, find_package(Shiboken2) fails in CMake.

Installing shiboken2 fixes the issue.

This breaks the build of packages which build-depend on libshiboken2-dev. For
example:
https://buildd.debian.org/status/fetch.php?pkg=freecad&arch=amd64&ver=0.18.4%2Bdfsg1-1%2Bb1&stamp=1574113872&raw=0

How to reproduce:

$ cat > CMakeFiles.txt
find_package(Shiboken2)
^D

$ cmake -Wno-dev .
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Shiboken2Config: Using default python: .cpython-38-x86_64-linux-gnu
CMake Error at /usr/lib/x86_64-linux-
gnu/cmake/Shiboken2-5.13.2/Shiboken2Targets.cmake:75 (message):
  The imported target "Shiboken2::shiboken2" references the file

 "/usr/bin/shiboken2"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/Shiboken2-5.13.2/Shiboken2Targets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/x86_64-linux-
gnu/cmake/Shiboken2-5.13.2/Shiboken2Config.cpython-38-x86_64-linux-gnu.cmake:40
(include)
  /usr/lib/x86_64-linux-gnu/cmake/Shiboken2-5.13.2/Shiboken2Config.cmake:5
(include)
  CMakeLists.txt:1 (find_package)


-- Configuring incomplete, errors occurred!
See also "/tmp/shiboken2/CMakeFiles/CMakeOutput.log".








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

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

Versions of packages libshiboken2-dev depends on:
ii  libshiboken2-py3-5.13  5.13.2-2
ii  python3-dev3.7.5-3

libshiboken2-dev recommends no packages.

libshiboken2-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pyside2
Source-Version: 5.13.2-2.1

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated pyside2 
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, 24 Dec 2019 09:22:39 +0100
Source: pyside2
Binary: python-pyside2-doc libpyside2-py3-5.13 libpyside2-dev 
python3-pyside2.qtcore shiboken2 libshiboken2-py3-5.13 libshiboken2-dev 
shiboken2-doc pyside2-tools python3-pyside2uic python3-pyside2.qtwidgets 
python3-pyside2.qt3drender python3-pyside2.qtquick 
python3-pyside2.qtpositioning py

Processed (with 1 error): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 912487 src:pyntor
Bug #912487 [pyntor] pyntor: Please migrate to python3-pygame
Bug reassigned from package 'pyntor' to 'src:pyntor'.
Ignoring request to alter found versions of bug #912487 to the same values 
previously set
Ignoring request to alter fixed versions of bug #912487 to the same values 
previously set
> forcemerge 937492 912487
Bug #937492 [src:pyntor] pyntor: Python2 removal in sid/bullseye
Bug #912487 [src:pyntor] pyntor: Please migrate to python3-pygame
Severity set to 'serious' from 'wishlist'
937441 was blocked by: 936513 936148 937726 938488 943075 945632 937330 936577 
937621 936559 945731 937743 938592 938509 945671 936298 936978 937492 936550 
936945 943027 938328 945699 937431 938497 937553
937441 was blocking: 937695 937960 938168 938528
Added blocking bug(s) of 937441: 912487
937695 was blocked by: 937940 942931 937168 938280 947299 936954 937326 945624 
943062 938502 936288 936214 937599 943090 937304 937166 936493 937680 936937 
936855 937758 937328 938022 937123 938744 936527 942960 937221 937634 937598 
937712 937213 936289 936977 938055 947298 937169 938665 938455 945707 937657 
937329 937265 937467 936673 936982 937759 937596 936124 938100 942992 937094 
938807 938613 936303 942971 947296 938621 937494 938234 938841 936185 938412 
938850 936189 937318 937269 937600 937549 938157 936206 936472 936858 945732 
943040 938059 936631 938459 938669 936443 945688 938582 936208 937962 942933 
936285 938794 938843 938623 937548 938174 936859 942973 938554 937268 938180 
938611 935358 936902 936188 938056 938887 936114 936105 938666 937266 936450 
945743 936812 936660 938458 945689 937044 937330 942942 937211 937444 938058 
936748 937300 883173 937845 946929 937625 937896 938129 938216 943265 936276 
938541 940199 937684 938507 943067 937618 938261 937451 937944 938270 945675 
937051 938593 937898 936522 937616 938027 936950 933775 938427 943213 938369 
936932 936683 936238 936972 937619 936120 937717 936392 938366 945702 943166 
942981 938252 937090 945635 938311 938230 936749 936601 937490 946928 938753 
936279 937062 942964 937462 936943 937899 943168 938219 938837 937895 943044 
945678 936798 943223 938204 936275 936477 938591 943266 937053 938152 937453 
938572 938790 937663 938130 945639 938263 936179 938854 947302 937848 937628 
938543 938762 945676 936745 936559 936796 937615 936482 943268 938226 938587 
939115 939104 938365 938229 938116 936941 936454 936176 937334 937040 945636 
936556 937440 936799 938751 938532 938313 938922 942983 938184 936437 936235 
943121 937849 936993 936558 943113 936681 937727 938877 936110 938125 937459 
942986 943161 936606 937059 943116 943229 937794 939111 938361 936996 936339 
936945 938370 943125 936608 942914 937012 937832 937412 942988 938384 937850 
936685 937157 938549 943184 938755 936998 936173 938269 937577 936844 936310 
938600 938546 936271 936338 945673 936793 937927 937891 943204 938444 937058 
938223 937458 943017 938330 938044 938211 937554 938268 937611 943119 937843 
937174 936336 936999 937456 936707 937666 945642 942989 936609 936741 936688 
943230 936605 936614 938315 936551 938166 938328 942924 937022 943115 938674 
943104 936995 938680 936946 938111 937422 938758 936867 938168 943126 938363 
937274 936686 938756 938326 943163 936894 936743 938759 938596 936562 938545 
937100 938657 938329 938467 936242 942909 937621 936787 937234 937841 936689 
938094 943225 936949 936335 943027 938598 938712 936772 937665 945692 937257 
937455 926244 937055 945671 943218 936273 942910 938848 938628 937762 945746 
936147 942978 938374 937263 943056 938380 936101 936388 936183 943180 937587 
937119 938615 938604 936305 936840 936314 943058 942939 937204 937417 937837 
938846 938626 945748 942976 937572 936449 938663 938053 943157 936495 936297 
937184 937321 937550 937751 937170 937118 937532 943012 938727 936544 937125 
938357 947232 942979 936853 937116 937229 943134 936448 937161 938440 942938 
938040 945647 936635 936702 945745 936737 943257 938051 937593 937218 938661 
938451 937270 937225 937427 936164 936890 938616 937027 937129 943234 936678 
942975 937956 938300 936862 938845 936181 938625 936610 937507 943100 938670 
937740 938618 936103 937261 935212 936385 937541 938684 936496 936247 936445 
938462 943280 937126 942935 936638 936283 943274 937959 937115 945664 936498 
936309 937230 938490 937912 937323 937252 936777 937538 938013 936337 938421 
937694 943227 937769 936473 937904 943070 936706 937457 937255 943018 937667 
943061 938465 936442 938501 937926 937579 938655 937536 937159 938700 936724 
938065 945733 936708 937814 937034 943016 938294 936785 938583 937888 942950 
942991 937474 937080 937768 942972 937074 937480 936865 938622 936693 937576 
937929 936981 937539 937156 936813 945742 937889 936821 936641 936709 936433 
943052 942987 937222 937711 936997 937510 936377 942943 938873 937578 943026 
937644 938774 938581 938068 937961 938780 938468 945731 937885 93791

Processed: Re: should depend on shiboken2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #946082 [libshiboken2-dev] should depend on shiboken2
Severity set to 'serious' from 'important'
> tags -1 patch pending
Bug #946082 [libshiboken2-dev] should depend on shiboken2
Added tag(s) pending and patch.

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

Processed (with 1 error): forcibly merging 937457 939109

[Debian Bug Tracking System]

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

> forcemerge 937457 939109
Bug #937457 [src:pyhoca-gui] pyhoca-gui: Python2 removal in sid/bullseye
Bug #939109 [src:pyhoca-gui] pyhoca-gui: Python2 removal in sid/bullseye -- 
drop python-distutils-extra build dependency
Failed to forcibly merge 937457: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> thanks
Stopping processing here.

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

Processed: bug 937403 is forwarded to https://github.com/pycassa/pycassa/issues/240

[Debian Bug Tracking System]

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

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

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

Processed: tagging 937387

[Debian Bug Tracking System]

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

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

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

Processed: tagging 937269

[Debian Bug Tracking System]

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

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

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