Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

Hi,

On Wed, Dec 25, 2019 at 06:26:49PM +0100, Christian Kastner wrote:
> 
> If you like gbp, then it's already a team win :-)

+1
  
> Yeah, the C++ symbols generated are the mangled versions. You need to
> unmangle them by piping the generated file through c++filt, and then add
> the (c++) prefix to tell dpkg-gensymbols about this. The
> UsingSymbolsFiles [1] page has a practical example on the bottom.
> 
> The c++filt(1) and dpkg-gensymbols(1) man pages have theoretical
> background on this, but TBH, I don't think it's needed.

As I tried to express:  I do not agree that the effort to maintain a
symbols file is really needed.  I just do so if upstream randomly
changes ABI.  Than dh_makeshlibs fails in the packaging step which is a
flag that we need to bump SOVERSION.  If you have other means to spot
the need of a SOVERSION bump that's fine.
 
> There are voices that say that symbols files for C++ libraries are
> overly hard to maintain, but in case of this specific upstream, I didn't
> have a negative experience, and it did help me detect breaking changes a
> few times.

Yes, exactly that's the point.   BTW, sometimes it helps to just have a
*.symbols.amd64 file which is sufficient to detect these changes while
there is no need to fiddle with other architectures which in some cases
might have different symbols and need extra care.

Kind regards and thanks for caring for these packages

  Andreas.
 
> [1] https://wiki.debian.org/UsingSymbolsFiles
> 

-- 
http://fam-tille.de

Bug#943608: tests segfault when run with Python 3.8

[Daniele Nicolodi]

On 25/12/2019 11:41, Pierre-Elliott Bécue wrote:
> Le mardi 10 décembre 2019 à 12:27:35-0700, Daniele Nicolodi a écrit :
>> Hello,
>>
>> On Tue, 26 Nov 2019 13:06:24 +0100 "Dr. Tobias Quathamer"
>>  wrote:> I've forwarded this bug upstream, and further
>> investigation by them
>>> seems to indicate that this is actually a bug in CPython.
>>>
>>> I'm therefore cloning and reassigning this bug, feel free to
>>> revert this if you don't agree.
>>
>> A while ago I opened a merge request with upstream with a workaround
>> that fixes the segfault with CPython 3.8. As it seems that CPython 3.8.1
>> will be released with the bug not fixed, it may be worth to apply the
>> patch to the Debian package.
>>
>> https://bitbucket.org/blais/beancount/pull-requests/139
>>
>> All the patch does is to make the C code Python 3.9 ready, avoiding
>> raising a warning, which ultimately results in the segfault. The patch
>> seems very low risk to me.
> 
> Dear Daniele,
> 
> Thanks for the patch.
> 
> I adapted it a little to reduce it's volume:
> 
> https://salsa.debian.org/python-team/applications/beancount/blob/debian/master/debian/patches/0003-parser-Work-around-python3.8-bug-causing-a-segmentat.patch
> 
> The #define PY_SSIZE_T_CLEAN was in both parser.h and parser.c, and the
> removal of the two other includes seems out of scope for this bugfix
> IMO.
> 
> Is it fine with you?

Because the PY_SSIZE_T_CLEAN define modifies the API exposed by
Python.h, I think it is better to explicitly define it everywhere
Python.h is included. However, if the reduced version solves the problem
you are seeing, I don't see a reason to insist.

Please note that removing the other two includes is technically also a
bug-fix as those are technically two Python internal header files. I
removed the includes because I am not sure how including those files
directly interacts with the changes to the public API enabled by
PY_SSIZE_T_CLEAN. Again, if you don't see any problem, I don't see a
reason to insist.

The patch I proposed has been merged upstream, along with another that
solves another problem in the test suite with Python 3.8 (although I
didn't encounter this second bug in my testing). You may want to base
your package on a more recent (but unreleased) version. Since the 2.2.3
release I see mainly bug-fixes and improvements to the emacs
beancount-mode (which I don't know if you package along with the
application).

Cheers,
Dan

Processed: tagging 938326

[Debian Bug Tracking System]

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

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

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

Processed: tagging 938248

[Debian Bug Tracking System]

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

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

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

Bug#945435: marked as done (nototools Build-Depends on python-fonttools which isn't build from source anymore)

[Debian Bug Tracking System]

Your message dated Thu, 26 Dec 2019 05:19:56 +
with message-id 
and subject line Bug#945435: fixed in nototools 0.2.0-1.1
has caused the Debian Bug report #945435,
regarding nototools Build-Depends on python-fonttools which isn't build from 
source anymore
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.)


-- 
945435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nototools
Version: 0~20170925-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

nototools is involved in the Python 2 removal of Debian. Unfortunately, one of
your Build-Depends, python-fonttools has been removed already and currenty
isn't build from source in either unstable or testing. Also (indirect)
dependencies from python-fonttools are not build anymore, python-fs and
python-backports.fs. I fear the only solution is to quickly move to the Python
3 package that you already have prepared in experimental.

Thanks

Paul


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

Versions of packages python-nototools depends on:
ii  python2.7.17-2
pn  python-fonttools  
pn  unicode-data  

python-nototools recommends no packages.

python-nototools suggests no packages.

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3a3WQACgkQnFyZ6wW9
dQp/SQf/VuvJpeB/JcFUhil3aSrmgfjSg9HEI9XEbWXIOjjERPNOetPxCBN8w2Hy
Or5QDRQks0ThQ4L+ReexfUua4CjXS+Ydpm2fBJ97ZI0eJSBYTsBg/ZCElGVWqcNZ
B0Tf6mACg6lQegWi6EjxwO+S4Jc1ciWGl6LbRiXe8BXMT4A7ATiA0VsjMsgjx0Tj
7s+JzNCsiJO5Wi5k8pa7hT5heu125IMa6n3EPKf9Fv6PycjHIyQVrGEvIKLkGW6L
EIGKGfxI0Iaf5jY5+abVrt6J8zTbYv1TOxuppz/mvZsuxo2I/15fKPMC44jjsG9L
lv5nsBoJyU9qIJ1SvLAWJxNdkpivsw==
=kdnk
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: nototools
Source-Version: 0.2.0-1.1

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated nototools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Dec 2019 04:07:54 +
Source: nototools
Architecture: source
Version: 0.2.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Peter Michael Green 
Closes: 943761 945435
Changes:
 nototools (0.2.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload to unstable (Closes: 945435)
   * Apply upstream commit c4a79c79f0da2e6385eab0d89bf5c6546b15e373
 "More updates to make Python 3 compatible" (Closes: 943761)
   * Add breaks and replaces on python-nototools.
   * Fix clean target.
Checksums-Sha1:
 f4e49eb45ad8186d49f16e94ad53c1391805f804 2132 nototools_0.2.0-1.1.dsc
 05a7817ee79e1a7f57242704fe7cf1e1c0a1f89e 21608 
nototools_0.2.0-1.1.debian.tar.xz
 44afb0789bed8bc658dee8ef0332d4d9a421600d 6327 
nototools_0.2.0-1.1_source.buildinfo
Checksums-Sha256:
 b66c00caba4411fea2569fee548ea3429b6340012ec5897f6a4940a57457e3fd 2132 
nototools_0.2.0-1.1.dsc
 81b6bed063b7390f82ec118cf199ae6f5d5c067106bb1ccf0f31efe3b2903a53 21608 
nototools_0.2.0-1.1.debian.tar.xz
 aeb28ae0bef2fe640d3d8d9e6f28053beee55c28b12024cbee3fb51aece2ec48 6327 
nototools_0.2.0-1.1_source.buildinfo
Files:
 07482c2f6e67b47f97ef0d94e8e66a06 2132 fonts optional nototools_0.2.0-1.1.dsc
 36041b15a9dbc6b5c6e0727b0a93113e 21608 fonts optional 
nototools_0.2.0-1.1.debian.tar.xz
 217afd4e53003ff1f6065edcea507955 6327 fonts optional 
nototools_0.2.0-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#943022: marked as done (fonts-noto-color-emoji: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 26 Dec 2019 05:19:27 +
with message-id 
and subject line Bug#943022: fixed in fonts-noto-color-emoji 0~20180810-1.1
has caused the Debian Bug report #943022,
regarding fonts-noto-color-emoji: 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.)


-- 
943022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-noto-color-emoji
Version: 0~20180810-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: fonts-noto-color-emoji
Source-Version: 0~20180810-1.1

We believe that the bug you reported is fixed in the latest version of
fonts-noto-color-emoji, 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.
Peter Michael Green  (supplier of updated 
fonts-noto-color-emoji package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Dec 2019 04:15:57 +
Source: fonts-noto-color-emoji
Architecture: source
Version: 0~20180810-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Peter Michael Green 
Closes: 943022
Changes:
 fonts-noto-color-emoji (0~20180810-1.1) unstable; urgency=medium
 .
   * Change build-dependencies from python-nototools to python3-nototools
 (Closes: 943022)
   * Apply upstream patches for python 3 support.
   * Clean up __pycache__ in clean target.
   * Clean up third_party/color_emoji/__pycache__ in clean target.
Checksums-Sha1:
 cdc231aff62572d58162f6f83c91727214475df8 2281 
fonts-noto-color-emoji_0~20180810-1.1.dsc
 37853920c3666e0878616405f524ec97d88245b7 10016 
fonts-noto-color-emoji_0~20180810-1.1.debian.tar.xz
 530f9c09a2cadc2cc64544bf3a0a457fb2fe953b 9175 
fonts-noto-color-emoji_0~20180810-1.1_source.buildinfo
Checksums-Sha256:
 bb8cfce4a3b2b2b5c93d85c0716748136ed8acd77e90c29ac29de29e68fb8449 2281 
fonts-noto-color-emoji_0~20180810-1.1.dsc
 

Bug#943761: marked as done (python3-nototools: fails to install: Sorry: IndentationError: unexpected indent (lint_cmap_reqs.py, line 56))

[Debian Bug Tracking System]

Your message dated Thu, 26 Dec 2019 05:19:56 +
with message-id 
and subject line Bug#943761: fixed in nototools 0.2.0-1.1
has caused the Debian Bug report #943761,
regarding python3-nototools: fails to install: Sorry: IndentationError: 
unexpected indent (lint_cmap_reqs.py, line 56)
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.)


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

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up python3-nototools (0.2.0-1) ...
  Sorry: IndentationError: unexpected indent (lint_cmap_reqs.py, line 56)
  dpkg: error processing package python3-nototools (--configure):
   installed python3-nototools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.29-2) ...
  Errors were encountered while processing:
   python3-nototools


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: nototools
Source-Version: 0.2.0-1.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Dec 2019 04:07:54 +
Source: nototools
Architecture: source
Version: 0.2.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Peter Michael Green 
Closes: 943761 945435
Changes:
 nototools (0.2.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload to unstable (Closes: 945435)
   * Apply upstream commit c4a79c79f0da2e6385eab0d89bf5c6546b15e373
 "More updates to make Python 3 compatible" (Closes: 943761)
   * Add breaks and replaces on python-nototools.
   * Fix clean target.
Checksums-Sha1:
 f4e49eb45ad8186d49f16e94ad53c1391805f804 2132 nototools_0.2.0-1.1.dsc
 05a7817ee79e1a7f57242704fe7cf1e1c0a1f89e 21608 
nototools_0.2.0-1.1.debian.tar.xz
 44afb0789bed8bc658dee8ef0332d4d9a421600d 6327 
nototools_0.2.0-1.1_source.buildinfo
Checksums-Sha256:
 b66c00caba4411fea2569fee548ea3429b6340012ec5897f6a4940a57457e3fd 2132 
nototools_0.2.0-1.1.dsc
 81b6bed063b7390f82ec118cf199ae6f5d5c067106bb1ccf0f31efe3b2903a53 21608 
nototools_0.2.0-1.1.debian.tar.xz
 aeb28ae0bef2fe640d3d8d9e6f28053beee55c28b12024cbee3fb51aece2ec48 6327 
nototools_0.2.0-1.1_source.buildinfo
Files:
 07482c2f6e67b47f97ef0d94e8e66a06 2132 fonts optional nototools_0.2.0-1.1.dsc
 36041b15a9dbc6b5c6e0727b0a93113e 21608 fonts optional 
nototools_0.2.0-1.1.debian.tar.xz
 217afd4e53003ff1f6065edcea507955 6327 fonts optional 
nototools_0.2.0-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl39ohkUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xv6hQ/+JF1OJ1WhYcRn7oOO1q83++z8DhdX
nEjT6MCECtee23JD/kReQgbU+vXMIBzKrJsQMMfOwB7NhzppYp1Y0UIY99ywCAAs
B3uL0N/fLf17z9OdAnthKo2B/xUbLRu7UAZkHbHptmwQnKAPCglwI3NqI+piYv9n
XbPjXDsO6f1OnuVakkWvmJb5Q/syW4hA2Sfu4+mmbhf+dlU2sma6fEVu7rTpnGAR
X7IUMFbhGtEmLalNGro8Vzb+MdYD3iU/0HdA2U8/H+qv3U3zWP8dHUhKxxFFSwzK
VLepTuY9C6JPi+MtiWpszG8/h2c59FNgN41v+KSUVz09wlTbKiZnFmi3PLpCKCXu
UmTWDeB745BM/AmxAFd/eRDumn3Sms6lifwS5b7QfxdeK7fX6nVFyFHpgegrKu1Q
S/Q/XLbI15o7Mh/84YVt03qywhka+n9n+/6LnDDvQr8vXnPdb53nufiaV3CNHk9Z
o1Rp5oaza/L73CLfELrpqvmHa/wo+G0ukwfO/78Sk4ozL3RR6u5fCwHIE6MYhhHi
FadrUkIcYJhv1jAcCZPNv4ci/XmoWP7BANG0JAE/7WvNEssJIpna1R7Aamf+RjPZ
U4pTl0SdGByOuMK/wF9YBZnb9KGV6pAMM5tsNZQTPy2MdnIiTT8RV+OCxEmoAZZD
qvFLSEZXgSmACtU=
=goux
-END PGP SIGNATURE End Message ---

Bug#943278: marked as done (spring: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 26 Dec 2019 02:46:56 +
with message-id 
and subject line Bug#943278: fixed in spring 104.0+dfsg-4
has caused the Debian Bug report #943278,
regarding spring: 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.)


-- 
943278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spring
Version: 104.0+dfsg-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 (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: spring
Source-Version: 104.0+dfsg-4

We believe that the bug you reported is fixed in the latest version of
spring, 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.
Markus Koschany  (supplier of updated spring 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: Thu, 26 Dec 2019 02:11:33 +0100
Source: spring
Architecture: source
Version: 104.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 943278
Changes:
 spring (104.0+dfsg-4) unstable; urgency=medium
 .
   * Add glstub.patch and fix FTBFS because NULL is not defined in glstub.c.
   * Drop B-D on python-pygccxml. (Closes: #943278)
   * Declare compliance with Debian Policy 4.4.1.
   * Use canonical VCS URI.
   * Switch to debhelper-compat = 12.
Checksums-Sha1:
 c5efc646916093162573f6fe84a323f758151966 2519 spring_104.0+dfsg-4.dsc
 408d6bd06246f7db1a23ccea5d744e9b1b6fbe4a 16700 
spring_104.0+dfsg-4.debian.tar.xz
 f5300456cee282327306901c07cb50431c27c359 19701 
spring_104.0+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 f807cde09d53dc6c6f803b6e21619dbd92e8bef5a9826dbba5398ba77dad57d3 2519 
spring_104.0+dfsg-4.dsc
 47547bdb1ba6e9923fcd2cec1b57d093601e4e175c356848f9cda1875a44ed66 16700 
spring_104.0+dfsg-4.debian.tar.xz
 08514ba343ba44a3c21b09d7d78602b519f72b79f5d80ca1bab498796a692189 19701 
spring_104.0+dfsg-4_amd64.buildinfo
Files:
 4361089537f5891cbd1ea54afc9b0266 

Bug#947392: mesa-common-dev: missing Depends: libgl-dev (>= 1.3)

[Andreas Beckmann]

Package: mesa-common-dev
Version: 19.3.0~rc6-1
Severity: serious

mesa-common-dev needs to depend on libgl-dev
after the headers were moved.

The missing headers cause e.g. a FTBFS in pycuda.


Andreas

Bug#947387: [Python-modules-team] Bug#947387: python3-pcapy: missing Breaks+Replaces: python-pcapy

[Emmanuel Arias]

Hello!

I've pushed to salsa the fix.

I CC to Raphaël that help me to upload.

Raphaël, please could you review my patch?

Thanks!

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El mié., 25 de dic. de 2019 a la(s) 21:54, Andreas Beckmann
(a...@debian.org) escribió:
>
> Package: python3-pcapy
> Version: 0.11.4-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'stable'.
> It installed fine in 'stable', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>
> This test intentionally skipped 'testing' to find file overwrite
> problems before packages migrate from 'unstable' to 'testing'.
>
> From the attached log (scroll to the bottom...):
>
>   Preparing to unpack .../python3-pcapy_0.11.4-1_amd64.deb ...
>   Unpacking python3-pcapy (0.11.4-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/python3-pcapy_0.11.4-1_amd64.deb (--unpack):
>trying to overwrite '/usr/share/doc-base/pcapy', which is also in package 
> python-pcapy 0.10.8-1+b1
>   Errors were encountered while processing:
>/var/cache/apt/archives/python3-pcapy_0.11.4-1_amd64.deb
>
>
> cheers,
>
> Andreas
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Bug#937073: marked as done (mopidy-dleyna: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 26 Dec 2019 01:50:11 +
with message-id 
and subject line Bug#937073: fixed in mopidy-dleyna 2.0.0-1
has caused the Debian Bug report #937073,
regarding mopidy-dleyna: 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.)


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

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: mopidy-dleyna
Source-Version: 2.0.0-1

We believe that the bug you reported is fixed in the latest version of
mopidy-dleyna, 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.
Stein Magnus Jodal  (supplier of updated mopidy-dleyna 
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: Thu, 26 Dec 2019 02:19:34 +0100
Source: mopidy-dleyna
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Stein Magnus Jodal 
Changed-By: Stein Magnus Jodal 
Closes: 937073
Changes:
 mopidy-dleyna (2.0.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Switch from Python 2 to 3 (Closes: #937073)
   * Bump debhelper from 10 to 12
   * Disable tests because of pkg_resurces usage
   * d/control: Bump Standards-Version to 4.4.1, no changes
   * d/control: Require mopidy >= 3
   * d/control: Update Description
   * d/copyright: Update copyright years
   * d/copyright: Use HTTPS for the copyright spec
   * d/rules: Update changelog name
Checksums-Sha1:
 73b9d46c453afe4e6c780feeea16552efaeef313 2024 mopidy-dleyna_2.0.0-1.dsc
 af89852e64afe1a946adc5c9599fba5829a9ddd7 21238 mopidy-dleyna_2.0.0.orig.tar.gz
 6529287d08a957cbcb5d4dd5677ed46d8caf3508 2500 

Bug#937070: marked as done (mopidy-alsamixer: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 26 Dec 2019 01:20:07 +
with message-id 
and subject line Bug#937070: fixed in mopidy-alsamixer 2.0.0-1
has caused the Debian Bug report #937070,
regarding mopidy-alsamixer: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mopidy-alsamixer

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: mopidy-alsamixer
Source-Version: 2.0.0-1

We believe that the bug you reported is fixed in the latest version of
mopidy-alsamixer, 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.
Stein Magnus Jodal  (supplier of updated mopidy-alsamixer 
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: Thu, 26 Dec 2019 01:45:22 +0100
Source: mopidy-alsamixer
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Stein Magnus Jodal 
Changed-By: Stein Magnus Jodal 
Closes: 937070
Changes:
 mopidy-alsamixer (2.0.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Switch from Python 2 to 3 (Closes: #937070)
   * d/clean: Remove custom clean rules
   * d/control: Bump Standards-Version to 4.4.1, no changes
   * d/control: Bump debhelper from 9 to 12
   * d/control: Require Mopidy >= 3
   * d/control: Update Description
   * d/control: Update Homepage
   * d/copyright: Update copyright years
   * d/copyright: Use HTTPS for the copyright spec
   * d/rules: Remove pytest config
   * Disable tests because of pkg_resurces usage
Checksums-Sha1:
 f6eaa7fdbb8fa62b3e44a133e7956c23480da5e6 2005 mopidy-alsamixer_2.0.0-1.dsc
 0225a1db5ed1235a6c941e408eca8066f9690220 11882 

Bug#936249: bugs-everywhere: Python2 removal in sid/bullseye

[maxigas]

On Wed, Dec 25 2019, Moritz Mühlenhoff wrote:

> On Fri, Aug 30, 2019 at 07:12:24AM +, Matthias Klose wrote:
>> Package: src:bugs-everywhere
>> Version: 1.1.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
>
> bugs-everywhere is dead upstream, the last commits are from 2013.
>
> Are you planning to port it to Python 3 yourself? Otherwise I'll
> request it's removal from the archive.

Hm, i'm sorry but i don't think i will have the time to port it.

-- 
Maxigas, kiberpunk
FA00 8129 13E9 2617 C614 0901 7879 63BC 287E D166
Lecturer in Critical Digital Media Practice
Centre for Science Studies
Department of Sociology
Lancaster University

https://relay70.metatron.ai/

Unix is a Registered Bell of AT Trademark Laboratories. - Donn Seeley

O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

Bug#947387: python3-pcapy: missing Breaks+Replaces: python-pcapy

[Andreas Beckmann]

Package: python3-pcapy
Version: 0.11.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Preparing to unpack .../python3-pcapy_0.11.4-1_amd64.deb ...
  Unpacking python3-pcapy (0.11.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pcapy_0.11.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/pcapy', which is also in package 
python-pcapy 0.10.8-1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-pcapy_0.11.4-1_amd64.deb


cheers,

Andreas


python-pcapy=0.10.8-1+b1_python3-pcapy=0.11.4-1.log.gz
Description: application/gzip

Bug#945500: marked as done (mopidy-doc: unhandled symlink to directory conversion: /usr/share/doc/mopidy/html)

[Debian Bug Tracking System]

Your message dated Thu, 26 Dec 2019 00:34:52 +
with message-id 
and subject line Bug#945500: fixed in mopidy 3.0.1-1
has caused the Debian Bug report #945500,
regarding mopidy-doc: unhandled symlink to directory conversion: 
/usr/share/doc/mopidy/html
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.)


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

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster->sid
  buster->bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m28.5s ERROR: installs objects over existing directory symlinks:
  /usr/share/doc/mopidy/html/_images (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  /usr/share/doc/mopidy/html/_images/api_explorer.jpg (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/api_explorer.jpg (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  /usr/share/doc/mopidy/html/_images/auto.jpg (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/auto.jpg (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  
/usr/share/doc/mopidy/html/_images/graphviz-447df13b0da1e5b321116097b13e78f159de2dad.png
 (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/graphviz-447df13b0da1e5b321116097b13e78f159de2dad.png
 (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  
/usr/share/doc/mopidy/html/_images/graphviz-447df13b0da1e5b321116097b13e78f159de2dad.png.map
 (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/graphviz-447df13b0da1e5b321116097b13e78f159de2dad.png.map
 (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  
/usr/share/doc/mopidy/html/_images/graphviz-608d5bd384e8795489b24521adabe750e806c0f5.png
 (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/graphviz-608d5bd384e8795489b24521adabe750e806c0f5.png
 (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  
/usr/share/doc/mopidy/html/_images/graphviz-608d5bd384e8795489b24521adabe750e806c0f5.png.map
 (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/graphviz-608d5bd384e8795489b24521adabe750e806c0f5.png.map
 (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  
/usr/share/doc/mopidy/html/_images/graphviz-83721fec34402e69947264b6c560c4315088ccdf.png
 (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/graphviz-83721fec34402e69947264b6c560c4315088ccdf.png
 (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  
/usr/share/doc/mopidy/html/_images/graphviz-83721fec34402e69947264b6c560c4315088ccdf.png.map
 (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/graphviz-83721fec34402e69947264b6c560c4315088ccdf.png.map
 (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  
/usr/share/doc/mopidy/html/_images/graphviz-b5588201ffdf8aaba776d9ceb236875d6720583a.png
 (mopidy-doc) != 
/usr/share/doc/mopidy-doc/html/_images/graphviz-b5588201ffdf8aaba776d9ceb236875d6720583a.png
 (?)
/usr/share/doc/mopidy/html -> ../mopidy-doc/html
  

Bug#947385: openstack-cluster-installer-agent: missing Breaks+Replaces: openstack-cluster-installer (<< 24)

[Andreas Beckmann]

Package: openstack-cluster-installer-agent
Version: 24
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 .../openstack-cluster-installer-agent_24_all.deb ...
  Unpacking openstack-cluster-installer-agent (24) ...
  dpkg: error processing archive 
/var/cache/apt/archives/openstack-cluster-installer-agent_24_all.deb (--unpack):
   trying to overwrite '/usr/bin/openstack-cluster-installer-agent', which is 
also in package openstack-cluster-installer 23
  Errors were encountered while processing:
   /var/cache/apt/archives/openstack-cluster-installer-agent_24_all.deb


cheers,

Andreas


openstack-cluster-installer=23_openstack-cluster-installer-agent=24.log.gz
Description: application/gzip

Bug#947273: marked as done (odhcp6c: FTBFS with GCC 9: error: '__builtin_strncpy' specified bound 16 equals destination size)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 23:50:23 +
with message-id 
and subject line Bug#947273: fixed in odhcp6c 1.1+git20190906.e199804-1
has caused the Debian Bug report #947273,
regarding odhcp6c: FTBFS with GCC 9: error: '__builtin_strncpy' specified bound 
16 equals destination size
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.)


-- 
947273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odhcp6c
Version: 1.1+git20160131-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

odhcp6c FTBFS with GCC 9:

[ 33%] Building C object CMakeFiles/odhcp6c.dir/src/dhcpv6.c.o
/usr/bin/cc -D_GNU_SOURCE  -g -O2 
-fdebug-prefix-map=/build/odhcp6c-1.1+git20160131=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -std=c99   
-Wall -Werror -Wextra -pedantic -o CMakeFiles/odhcp6c.dir/src/dhcpv6.c.o   -c 
/build/odhcp6c-1.1+git20160131/src/dhcpv6.c
In file included from /usr/include/string.h:494,
 from /build/odhcp6c-1.1+git20160131/src/dhcpv6.c:22:
In function 'strncpy',
inlined from 'init_dhcpv6' at 
/build/odhcp6c-1.1+git20160131/src/dhcpv6.c:132:2:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error: 
'__builtin_strncpy' specified bound 16 equals destination size 
[-Werror=stringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
cc1: all warnings being treated as errors


Andreas


odhcp6c_1.1+git20160131-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: odhcp6c
Source-Version: 1.1+git20190906.e199804-1

We believe that the bug you reported is fixed in the latest version of
odhcp6c, 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.
Ben Hutchings  (supplier of updated odhcp6c 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 22:52:53 +
Source: odhcp6c
Architecture: source
Version: 1.1+git20190906.e199804-1
Distribution: experimental
Urgency: medium
Maintainer: Ben Hutchings 
Changed-By: Ben Hutchings 
Closes: 947273
Changes:
 odhcp6c (1.1+git20190906.e199804-1) experimental; urgency=medium
 .
   * New upstream version:
 - Upstream version is commit e199804b602a48eb69f0752584c0ad28495b82ad
   dated 2019-09-06
 - dhcpv6: fix strncpy bounds (Closes: #947273)
   * debian/control: Point Vcs URLs to Salsa
   * debian/copyright: Introduce License paragraph for GPL-2+
   * debian/control, debian/copyright: Change upstream to official OpenWRT repo
   * debian/rules, debian/watch: Replace get-orig-source with watch file
Checksums-Sha1:
 7ce05907d2208563714a6088e5a7e8657f4cc1bb 1951 
odhcp6c_1.1+git20190906.e199804-1.dsc
 2c99770b86489417882d1a5a286d60e03a59f755 36612 
odhcp6c_1.1+git20190906.e199804.orig.tar.xz
 03fc094724a93679801632c02dc4c45508e5501a 2836 
odhcp6c_1.1+git20190906.e199804-1.debian.tar.xz
 27ade8f14db2dec00a328f702197653a298a236d 7289 
odhcp6c_1.1+git20190906.e199804-1_source.buildinfo
Checksums-Sha256:
 0a908d977f2b249862ab6ed5b1ace9a2e6fd5cca37d804887d68d3b6710b8e1d 1951 
odhcp6c_1.1+git20190906.e199804-1.dsc
 085e716d2b450b9058f5a342623701b6fc5892e43e257b408ef66ebc985efbe9 36612 
odhcp6c_1.1+git20190906.e199804.orig.tar.xz
 e4313bd499b09c66a35a0abd5466d57ee4a4faa05050f78881a5dc40fe304d33 2836 
odhcp6c_1.1+git20190906.e199804-1.debian.tar.xz
 530118519c34c886eb54b5c42feafd88442966e275a94747cf1d81fd1f95f5d0 7289 
odhcp6c_1.1+git20190906.e199804-1_source.buildinfo
Files:
 2f553630036edab578301f37514ddc5c 1951 net optional 
odhcp6c_1.1+git20190906.e199804-1.dsc
 c5068f517df697b1d8f595ab1604431e 36612 net optional 
odhcp6c_1.1+git20190906.e199804.orig.tar.xz
 9205ee9fad6c2040e7a311425f9f5be5 2836 net optional 
odhcp6c_1.1+git20190906.e199804-1.debian.tar.xz
 d29215f5ec70323b896bd7b9be41 7289 net optional 

Bug#946470: marked as done (libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 23:01:43 +
with message-id 
and subject line Bug#946470: fixed in libreoffice 1:6.4.0~beta1-3
has caused the Debian Bug report #946470,
regarding libreoffice-l10n-de: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
946470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-l10n-de
Version: 1:6.4.0~beta1-0reprotest1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libreoffice-l10n-ja libreoffice-l10n-he 
libreoffice-l10n-in libreoffice-l10n-za libreoffice-help-common

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  sid -> experimental

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


This bug is present in several libreoffice-l10n-?? packages
and libreoffice-help-common. Maybe also in more packages
depending on these failing ones since they cannot be tested.

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

0m25.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libreoffice-l10n-de/changelog.Debian.gz (libreoffice-l10n-de) 
!= /usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common)
/usr/share/doc/libreoffice-l10n-de -> libreoffice-common
  /usr/share/doc/libreoffice-l10n-de/copyright (libreoffice-l10n-de) != 
/usr/share/doc/libreoffice-common/copyright (libreoffice-common)
/usr/share/doc/libreoffice-l10n-de -> libreoffice-common

0m24.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libreoffice-help-common/changelog.Debian.gz 
(libreoffice-help-common) != 
/usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common)
/usr/share/doc/libreoffice-help-common -> libreoffice-common
  /usr/share/doc/libreoffice-help-common/copyright (libreoffice-help-common) != 
/usr/share/doc/libreoffice-common/copyright (libreoffice-common)
/usr/share/doc/libreoffice-help-common -> libreoffice-common


cheers,

Andreas


libreoffice-l10n-de_1:6.4.0~beta1-0reprotest1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.4.0~beta1-3

We believe that the bug you reported is fixed in the latest version of
libreoffice, 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.
Rene Engelhard  (supplier of updated libreoffice 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, 09 Dec 2019 18:10:48 +0100
Source: libreoffice
Binary: fonts-opensymbol libjuh-java libjurt-java liblibreofficekitgtk 
liblibreofficekitgtk-dbgsym libofficebean-java libreoffice 

Processed: kernel-package: diff for NMU version 13.018+nmu2

[Debian Bug Tracking System]

Processing control commands:

> tags 947340 + patch
Bug #947340 {Done: Ben Hutchings } [src:kernel-package] 
kernel-common conflicts with current linux-base
Added tag(s) patch.
> tags 947340 + pending
Bug #947340 {Done: Ben Hutchings } [src:kernel-package] 
kernel-common conflicts with current linux-base
Added tag(s) pending.

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

Bug#947340: kernel-package: diff for NMU version 13.018+nmu2

[Ben Hutchings]

Control: tags 947340 + patch
Control: tags 947340 + pending

I've uploaded the previously prepared NMU for kernel-package
(versioned as 13.018+nmu2), with a reference to this bug report.  My
changes are also available at
.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program
than vice versa.
diff -Nru kernel-package-13.018+nmu1/Makefile kernel-package-13.018+nmu2/Makefile
--- kernel-package-13.018+nmu1/Makefile	2016-02-16 23:35:18.0 +
+++ kernel-package-13.018+nmu2/Makefile	2019-03-24 22:18:52.0 +
@@ -110,7 +110,6 @@
done)
 	$(install_file)debian/copyright  	  $(DOCDIR)/copyright
 	$(install_file)kernel-pkg.conf.5 	  $(MAN5DIR)/kernel-pkg.conf.5
-	$(install_file)kernel-img.conf.5 	  $(MAN5DIR)/kernel-img.conf.5
 	$(install_file)kernel-package.5  	  $(MAN5DIR)/kernel-package.5
 	$(install_file)make-kpkg.8   	  $(MAN1DIR)/make-kpkg.1
 	$(install_file)kernel-packageconfig.8 $(MAN8DIR)/
@@ -119,10 +118,6 @@
  mkdir -p $(MANTOP)/$$lang/man5;   \
   test ! -f kernel-pkg.conf.$$lang.5  ||   \
$(install_file) kernel-pkg.conf.$$lang.5   $(MANTOP)/$$lang/man5/kernel-pkg.conf.5; \
-  test ! -f kernel-img.conf.$$lang.5  || test -d $(MANTOP)/$$lang/man5||   \
- mkdir -p $(MANTOP)/$$lang/man5;   \
-  test ! -f kernel-img.conf.$$lang.5  ||   \
-   $(install_file) kernel-img.conf.$$lang.5   $(MANTOP)/$$lang/man5/kernel-img.conf.5; \
   test ! -f kernel-package.$$lang.5   || test -d $(MANTOP)/$$lang/man5||   \
  mkdir -p $(MANTOP)/$$lang/man5;   \
   test ! -f kernel-package.$$lang.5   ||   \
@@ -163,8 +158,6 @@
 	for lang in de fr; do\
   test ! -f kernel-pkg.conf.$$lang.5 ||  \
 rm  kernel-pkg.conf.$$lang.5  ;  \
-	  test ! -f kernel-img.conf.$$lang.5 ||  \
-rm  kernel-img.conf.$$lang.5  ;  \
 	  test ! -f kernel-package.$$lang.5 ||   \
 rm  kernel-package.$$lang.5   ;  \
 	  test ! -f make-kpkg.$$lang.8 ||\
diff -Nru kernel-package-13.018+nmu1/debian/changelog kernel-package-13.018+nmu2/debian/changelog
--- kernel-package-13.018+nmu1/debian/changelog	2017-07-16 09:52:57.0 +0100
+++ kernel-package-13.018+nmu2/debian/changelog	2019-12-25 22:27:29.0 +
@@ -1,3 +1,13 @@
+kernel-package (13.018+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * kernel-common: Remove kernel-img.conf(5) and recommend linux-base
+instead (Closes: #947340; see #925415)
+  * Refresh translation files for removal of kernel-img.conf(5)
+  * debian/control: Point Vcs-{Browser,Git} at Salsa
+
+ -- Ben Hutchings   Wed, 25 Dec 2019 22:27:29 +
+
 kernel-package (13.018+nmu1) unstable; urgency=medium
 
   [ Tobias Frost ]
diff -Nru kernel-package-13.018+nmu1/debian/control kernel-package-13.018+nmu2/debian/control
--- kernel-package-13.018+nmu1/debian/control	2016-02-16 23:35:18.0 +
+++ kernel-package-13.018+nmu2/debian/control	2019-03-24 22:21:47.0 +
@@ -1,6 +1,6 @@
 Source: kernel-package
-VCS-Git: https://anonscm.debian.org/git/users/srivasta/debian/kernel-package.git
-VCS-Browser: https://anonscm.debian.org/gitweb/?p=users/srivasta/debian/kernel-package.git;a=summary
+VCS-Git: https://salsa.debian.org/srivasta/kernel-package.git
+VCS-Browser: https://salsa.debian.org/srivasta/kernel-package
 Priority: optional
 Section: kernel
 Build-Depends-Indep: po4a (>= 0.31), debhelper (>= 9)
@@ -29,6 +29,7 @@
 Package: kernel-common
 Architecture: all
 Depends: ${misc:Depends}
+Recommends: linux-base (>= 4.6~)
 Suggests: kernel-package
 Enhances: kernel-package, linux-image
 Replaces: kernel-package (<= 13.008)
diff -Nru kernel-package-13.018+nmu1/debian/kernel-common.manpages kernel-package-13.018+nmu2/debian/kernel-common.manpages
--- kernel-package-13.018+nmu1/debian/kernel-common.manpages	2016-02-16 23:35:18.0 +
+++ kernel-package-13.018+nmu2/debian/kernel-common.manpages	1970-01-01 01:00:00.0 +0100
@@ -1,3 +0,0 @@
-kernel-img.conf.5
-kernel-img.conf.de.5
-kernel-img.conf.fr.5
diff -Nru kernel-package-13.018+nmu1/kernel-img.conf.5 kernel-package-13.018+nmu2/kernel-img.conf.5
--- kernel-package-13.018+nmu1/kernel-img.conf.5	2016-02-16 23:35:18.0 +
+++ kernel-package-13.018+nmu2/kernel-img.conf.5	1970-01-01 01:00:00.0 +0100
@@ -1,266 +0,0 @@
-.\" Hey, Emacs! This is an -*- nroff -*- source file.

Bug#947340: marked as done (kernel-common conflicts with current linux-base)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 22:34:39 +
with message-id 
and subject line Bug#947340: fixed in kernel-package 13.018+nmu2
has caused the Debian Bug report #947340,
regarding kernel-common conflicts with current linux-base
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.)


-- 
947340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
Source: kernel-package
Source-Version: 13.018+nmu2

We believe that the bug you reported is fixed in the latest version of
kernel-package, 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.
Ben Hutchings  (supplier of updated kernel-package 
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 22:27:29 +
Source: kernel-package
Architecture: source
Version: 13.018+nmu2
Distribution: unstable
Urgency: medium
Maintainer: Manoj Srivastava 
Changed-By: Ben Hutchings 
Closes: 947340
Changes:
 kernel-package (13.018+nmu2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * kernel-common: Remove kernel-img.conf(5) and recommend linux-base
 instead (Closes: #947340; see #925415)
   * Refresh translation files for removal of kernel-img.conf(5)
   * debian/control: Point Vcs-{Browser,Git} at Salsa
Checksums-Sha1:
 fab39d764b2ffae7515606998cc18b9a9f1f986c 1667 kernel-package_13.018+nmu2.dsc
 53b4b3517c7df12a655ad4788844e11abad5a127 315012 
kernel-package_13.018+nmu2.tar.xz
 005ce874d751d78fc413c4e788ec0003e0ed3c0d 4418 
kernel-package_13.018+nmu2_source.buildinfo
Checksums-Sha256:
 a9e1dc8dc5cb1da7a9c974385c9370103dd3a7424697390e3922e6729973ad11 1667 
kernel-package_13.018+nmu2.dsc
 a362255b902495a543db78d3cf8b86808cf98c281d7d24b5c7b2ac99f2f3 315012 
kernel-package_13.018+nmu2.tar.xz
 42c231b975b72fe8cd902dc4adba3ed66c2af50d87678076c621ea222a3ea3b6 4418 
kernel-package_13.018+nmu2_source.buildinfo
Files:
 7a3cd62368b8197733ec22c3e3689c04 1667 kernel optional 
kernel-package_13.018+nmu2.dsc
 b813fb832e5a99c1a87b6c0a26bcf5d6 315012 kernel optional 
kernel-package_13.018+nmu2.tar.xz
 b0dd2c2fe77499a1b2a21060421fa21b 4418 kernel optional 
kernel-package_13.018+nmu2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl4D41gACgkQ57/I7JWG
EQnM9w//fVZpwR2+NM5JvtNyQa340FCSsxOdzOKInK90sOsIYtu++LaVOANYt8wS
TRhEKP3GGOEpC1eLn3QgxW7AtxGRzoXAS5oOg6LYJQwe+vrL45G6q6niholXQ1fG
0yqoESJD8DjeCijWEQKDgz0Q6CSF1Fr6VTM6YtJatvSDHOORiioMP8IksqytPOKD
1DXxW96JpXHti4ZMdZS4HcWua4Om9sf58Xb3kQPSo/xFyB1Dtoq3cLuvKs8rKaw8
eE94+v+RlXWPEEh+WsGHwx3ABaRrrlyrPnIkNwuxVQeO2BX1RVHeD1N6nWeaTZnF
saIO9Z1miuOMzf//f/2i+7D6bZoGLQNO/L0sHsgxzq6Oa6pL9ciqamJMgr1Nul3V
IB4/yjygTMtiNIJd/eCNl+lPnDEcPWJxptPiz2gSzmvR3HrI2EbHiuxwhMiasR9p
jVk0PWLe1FYsEa6MH+Ct3TTUjEU5fFcI8kZ7E9V8JbpDIPIW5TPak+1uDm20C+yz
O5M49JTFy0jfOmkRaTINlvcVLs4riPQeSxYJ6QBE1RuxmDqwyKiMSVgMbMKdKryt
Pm8zPFqjZ/RPPandjhGZduHFCTXSBxc5fEUGabXjL8DugKpjxNH42RE+WhpugH5v
WwgL6psuevsfqMylUGMq6D97kZE4EAIU/NlW75lkyxDGC1/+5UI=
=y2rW
-END PGP SIGNATURE End Message ---

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

[Holger Levsen]

On Wed, Dec 25, 2019 at 11:09:17PM +0100, Nis Martensen wrote:
> There is now a (very small) merge request on Salsa that fixes the
> failure you describe:
> https://salsa.debian.org/debian/piuparts/merge_requests/16
> 
> Are there further tests that could be run to see if there are more problems?

I can now see the next problem, this is what is displayed on the slave
side:

22:25:42 Running section testing2sid (precedence=2)
22:25:43 communication with master failed
22:25:43 Connection to master closed

and this is in master-error.log.x:

piupartsm@pejacevic:/srv/piuparts.debian.org/master$ cat master-error.log.30959
Traceback (most recent call last):
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
433, in 
main()
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
425, in main
while m.do_transaction():
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
268, in do_transaction
self._commands[command](command, args)
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
324, in _reserve
package = self._binary_db.reserve_package()
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 869, in reserve_package
for p in self._find_packages_ready_for_testing():
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 854, in _find_packages_ready_for_testing
for pn in self.get_pkg_names_in_state("waiting-to-be-tested")]
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 718, in get_pkg_names_in_state
self._compute_package_states()
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 672, in _compute_package_states
todo = 
self._initialize_package_states(use_cached_success=use_cached_success, 
check_outdated=False)
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 653, in _initialize_package_states
state = self._lookup_package_state(package, use_cached_success, 
check_outdated)
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 540, in _lookup_package_state
for dep in package.dependencies():
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 140, in dependencies
vlist += self._parse_dependencies(header)
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 119, in _parse_dependencies
parser = DependencyParser(self[header_name])
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/dependencyparser.py",
 line 189, in __init__
self._list = self._parse_dependencies()
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/dependencyparser.py",
 line 211, in _parse_dependencies
dep = self._parse_dependency()
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/dependencyparser.py",
 line 224, in _parse_dependency
dep = self._parse_possible_dependency()
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/dependencyparser.py",
 line 237, in _parse_possible_dependency
(op, version) = self._parse_version_dependency()
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/dependencyparser.py",
 line 266, in _parse_version_dependency
self._cursor.mynext(self._cursor)
TypeError: mynext() takes 1 positional argument but 2 were given


again, help very welcome!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C



signature.asc
Description: PGP signature

Processed: coinor-libdylp-dev: ships headers owned by coinor-libcoinutils-dev, coinor-libosi-dev

[Debian Bug Tracking System]

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

> owner 947360 !
Bug #947360 [coinor-libdylp-dev] coinor-libdylp-dev: ships headers owned by 
coinor-libcoinutils-dev, coinor-libosi-dev
Owner recorded as Sudip Mukherjee .
>
End of message, stopping processing here.

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

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

[Ben Hutchings]

Control: reassign -1 src:kernel-package 13.018+nmu1
Control: retitle -1 kernel-common conflicts with current linux-base
Control: affects -1 linux-base

On Wed, 2019-12-25 at 03:06 +0100, Christoph Anton Mitterer wrote:
> 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.

Manoj suggested that the kernel team should take over kernel-img.conf,
and I prepared updates to both linux-base and kernel-package (see <
https://salsa.debian.org/benh/kernel-package>).  However I never got a
response from him as to whether he or I should upload kernel-package.

I suppose I should just go ahead and do that now.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program
than vice versa.



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

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:kernel-package 13.018+nmu1
Bug #947340 [linux-base] linux-base: can't be upgraded
Bug reassigned from package 'linux-base' to 'src:kernel-package'.
No longer marked as found in versions linux-base/4.6.
Ignoring request to alter fixed versions of bug #947340 to the same values 
previously set
Bug #947340 [src:kernel-package] linux-base: can't be upgraded
Marked as found in versions kernel-package/13.018+nmu1.
> retitle -1 kernel-common conflicts with current linux-base
Bug #947340 [src:kernel-package] linux-base: can't be upgraded
Changed Bug title to 'kernel-common conflicts with current linux-base' from 
'linux-base: can't be upgraded'.
> affects -1 linux-base
Bug #947340 [src:kernel-package] kernel-common conflicts with current linux-base
Added indication that 947340 affects linux-base

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

Processed: Re: spring: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

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

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

Processed: block 938262 with 936358

[Debian Bug Tracking System]

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

> block 938262 with 936358
Bug #938262 {Done: Georges Khaznadar } 
[src:python-whiteboard] python-whiteboard: Python2 removal in sid/bullseye
938262 was not blocked by any bugs.
938262 was blocking: 936358 937513 937695 937960 938275 942981
Added blocking bug(s) of 938262: 936358 and 942981
> thanks
Stopping processing here.

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

Processed (with 1 error): block 938262 with 36358

[Debian Bug Tracking System]

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

> block 938262 with 36358
Bug #938262 {Done: Georges Khaznadar } 
[src:python-whiteboard] python-whiteboard: Python2 removal in sid/bullseye
No valid blocking bug(s) given; not doing anything
Failed to set blocking bugs of 938262: Unknown/archived blocking bug(s):36358.

> thanks
Stopping processing here.

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

Processed: tagging 942914

[Debian Bug Tracking System]

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

> tags 942914 + fixed
Bug #942914 {Done: Mike Gabriel } [src:caja-mediainfo] 
caja-mediainfo: Python2 removal in sid/bullseye
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Processed: tagging 925824

[Debian Bug Tracking System]

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

> tags 925824 + fixed-upstream
Bug #925824 [src:sgt-puzzles] sgt-puzzles: ftbfs with GCC-9
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#945920: Random Chromium crashes

[Michel Meyers]

Hello,

Same here unfortunately. It has fixed the SIGSEGV when opening the Task 
Manager, but as feared, that crash seems to be separate from the 
randomly occurring one.


- Michel

Bug#947373: python3-guestfs: missing Breaks+Replaces: python-guestfs

[Andreas Beckmann]

Package: python3-guestfs
Version: 1:1.40.2-3
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 .../python3-guestfs_1%3a1.40.2-4_amd64.deb ...
  Unpacking python3-guestfs (1:1.40.2-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-guestfs_1%3a1.40.2-4_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/ja/man3/guestfs-python.3.gz', which is 
also in package python-guestfs 1:1.40.2-2+b12
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-guestfs_1%3a1.40.2-4_amd64.deb


cheers,

Andreas


python-guestfs=1:1.40.2-2+b12_python3-guestfs=1:1.40.2-4.log.gz
Description: application/gzip

Bug#947371: dpdk: FTBFS during indep-only build

[Andreas Beckmann]

Source: dpdk
Version: 19.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

dpdk/experimental FTBFS during the indep-only build. (Both arch+indep
and arch-only work fine.) This was not observed on the buildds due to
the arch+indep maintainer upload (probably needed for NEW processing).

   dh_install -i -O--buildsystem=meson
dh_install: Cannot find (any matches for) "usr/share/dpdk/examples" (tried in 
., debian/tmp)

dh_install: dpdk-doc missing files: usr/share/dpdk/examples


Andreas


dpdk_19.11-1_indep.log.gz
Description: application/gzip

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

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 20:45:37 +
with message-id 
and subject line Bug#947310: fixed in mesa 19.3.1-3
has caused the Debian Bug report #947310,
regarding mesa: FTBFS on mipsel: Cannot find (any matches for) 
"usr/lib/*/libvulkan_*.so"
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.)


-- 
947310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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=mipsel=19.3.1-2=1576796202=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
--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 19.3.1-3

We believe that the bug you reported is fixed in the latest version of
mesa, 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.
Timo Aaltonen  (supplier of updated mesa 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 22:05:01 +0200
Source: mesa
Architecture: source
Version: 19.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 947310
Changes:
 mesa (19.3.1-3) unstable; urgency=medium
 .
   * control, rules: Actually build radv on mipsel, drop mips from
 everywhere since it's not an arch anymore. (Closes: #947310)
Checksums-Sha1:
 af838c5c878f8ea45a354c65b839284b261125c6 5253 mesa_19.3.1-3.dsc
 508d908eea42b6930a2efb66aa5ac27473adb964 138813 mesa_19.3.1-3.diff.gz
 e0e89c3d1c1b94036691c8f27a6e8959b4f1701d 9385 mesa_19.3.1-3_source.buildinfo
Checksums-Sha256:
 e33d90c8594218a6b57c08371340fc39ada9ac5c754ba7efbe1bcad09fb4bf24 5253 
mesa_19.3.1-3.dsc
 a4dd183fdff3a5d8d3bc6580f272ae0f98c1f0e7cba8334dc7d645e9d69064be 138813 
mesa_19.3.1-3.diff.gz
 c0cd892dec905cdc2d527c5bfa28d8955a334e193bec1a98e58492c5e7fb1626 9385 
mesa_19.3.1-3_source.buildinfo
Files:
 0a6e6c70a1a2139650647e8913a89734 5253 graphics optional mesa_19.3.1-3.dsc
 94a8c71295dc8e8caa19e94ebf0728f7 138813 graphics optional mesa_19.3.1-3.diff.gz
 db7d9de3d54fa12a395fa2afa83ecce9 9385 graphics optional 
mesa_19.3.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl4DwTIACgkQy3AxZaiJ
hNzvhQ/8CeZGWgrWYZLQDDeOARTlO6qTBqTMccup7x0UsuOF6vKPC6NcWpDVf8r9
YrqOpSaJpBjSjnMr0yUO6C8iEq2VfLjqCUQL2VEYKXyXwj5nHPkGejvaLN2Oi4wC
Fgf7JgEMEI+SwMyE1pRHi4jT33JuKMVRcM5j0BpmwbcOfE1XiHyK19t3UHxoVJg5
B2/az6zgmjXlgwbGX18U9YMOckVWMvzgneTsYzXGAun7yQ6ifk1fN4Kzc+dqGRsX
wwjWxwYfYxZEev2s7Dm6Gf/UY6zZLx+Qp7qlUMcMv8quAwUnaXTqdHauArik+MyS

Bug#945678: marked as done (ompl: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 20:45:50 +
with message-id 
and subject line Bug#945678: fixed in ompl 1.4.2+ds1-5
has caused the Debian Bug report #945678,
regarding ompl: 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.)


-- 
945678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ompl
Version: 1.4.2+ds1-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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.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: ompl
Source-Version: 1.4.2+ds1-5

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

Debian distribution maintenance software
pp.
Leopold Palomo-Avellaneda  (supplier of updated ompl 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 20:42:51 +0100
Source: ompl
Architecture: source
Version: 1.4.2+ds1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Leopold Palomo-Avellaneda 
Closes: 945678
Changes:
 ompl (1.4.2+ds1-5) unstable; urgency=medium
 .
   * Added r-cran-shinyjs, r-cran-v8, r-cran-dbplyr dependencies
 to ompl-plannerarena package.
   * Moves to Python3. Closes: #945678
Checksums-Sha1:
 dd2059955b82c3c2b756beb3390c0e377718b91a 2376 ompl_1.4.2+ds1-5.dsc
 6fc0b4c8ef584fc4e3380604761171aed3127ba1 22757110 ompl_1.4.2+ds1.orig.tar.gz
 846b6814873fb36eed634df69009dfbcc2dba60a 7900 ompl_1.4.2+ds1-5.debian.tar.xz
 8ccab985cdd8b158dc518e16df8d3e7662681add 12266 
ompl_1.4.2+ds1-5_source.buildinfo
Checksums-Sha256:
 b3a27f1582d91e864761e24185faf6ca056a171b2c603b06034f829a55081ca6 2376 
ompl_1.4.2+ds1-5.dsc
 3cc8df5dcd5bd93ef36ca8c41962f06ac64a64e6c5f6878c261598b3aa9261b1 22757110 
ompl_1.4.2+ds1.orig.tar.gz
 4e431e6415cb53bd90ac38678f7d718c868573a6f8ae09a580f8fb7622f7c6f3 7900 
ompl_1.4.2+ds1-5.debian.tar.xz
 7b11adddb4ec5d5b7f109f906c95951905e3f8eb5ed4530d952e6153b08e620d 12266 

Bug#937617: Debdiff, and NMU with DELAYED/7

[Thomas Goirand]

Hi,

Here's the proposed NMU debdiff. I'm uploading it to delayed/7 since the
bug has been opened for so long, there's no reverse dependency for the
py2 only package, and the package will be AUTORM in 22 days.

Cheers,

Thomas Goirand (zigo)
diff -u python-boto-2.49.0/debian/changelog python-boto-2.49.0/debian/changelog
--- python-boto-2.49.0/debian/changelog
+++ python-boto-2.49.0/debian/changelog
@@ -1,3 +1,10 @@
+python-boto (2.49.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Removed Python 2 support (Closes: #937617).
+
+ -- Thomas Goirand   Wed, 25 Dec 2019 21:28:06 +0100
+
 python-boto (2.49.0-2) unstable; urgency=medium
 
   * Re-enable boto.vendored package (for regions sub-pacakge).
diff -u python-boto-2.49.0/debian/control python-boto-2.49.0/debian/control
--- python-boto-2.49.0/debian/control
+++ python-boto-2.49.0/debian/control
@@ -3,11 +3,8 @@
 Priority: optional
 Maintainer: Eric Evans 
 Build-Depends: debhelper-compat (= 12),
-   python-all (>= 2.6.6-3),
-   python-setuptools,
python3-all (>= 3.2),
python3-setuptools,
-   python-six,
python3-six,
dh-python
 XS-Testsuite: autopkgtest
@@ -16,34 +13,6 @@
 Vcs-Git: https://salsa.debian.org/eevans/python-boto.git
 Standards-Version: 4.4.0
 
-Package: python-boto
-Architecture: all
-Depends: python-requests, ${misc:Depends}, ${python:Depends}, python-six
-Provides: ${python:Provides}
-Description: Python interface to Amazon's Web Services - Python 2.x
- Boto is a Python interface to the infrastructure services available from
- Amazon.
- .
- Boto supports the following services:
-  * Elastic Compute Cloud (EC2)
-  * Elastic MapReduce
-  * CloudFront
-  * DynamoDB
-  * SimpleDB
-  * Relational Database Service (RDS)
-  * Identity and Access Management (IAM)
-  * Simple Queue Service (SQS)
-  * CloudWatch
-  * Route53
-  * Elastic Load Balancing (ELB)
-  * Flexible Payment Service (FPS)
-  * Simple Storage Service (S3)
-  * Glacier
-  * Elastic Block Store (EBS)
-  * and many more...
- .
- This package provides the Python 2.x module.
-
 Package: python3-boto
 Architecture: all
 Depends: python3-requests, ${misc:Depends}, ${python3:Depends}, python3-six
reverted:
--- python-boto-2.49.0/debian/gbp.conf
+++ python-boto-2.49.0.orig/debian/gbp.conf
@@ -1,7 +0,0 @@
-[DEFAULT]
-upstream-branch   = upstream
-debian-branch = master
-
-[buildpackage]
-pbuilder  = True
-pbuilder-options  = --source-only-changes
diff -u python-boto-2.49.0/debian/rules python-boto-2.49.0/debian/rules
--- python-boto-2.49.0/debian/rules
+++ python-boto-2.49.0/debian/rules
@@ -1,6 +1,5 @@
 #!/usr/bin/make -f
 
-PYTHONS:=$(shell pyversions -vr)
 PYTHON3S:=$(shell py3versions -vr)
 
 clean:
@@ -19,7 +18,7 @@
 build-stamp:
dh_testdir
 
-   python setup.py build
+   python3 setup.py build
 
touch build-stamp
 
@@ -27,18 +26,6 @@
dh_testdir
dh_installdirs
 
-   # Python 2.x
-   set -e ; for pyvers in $(PYTHONS); do \
-   python$$pyvers setup.py install --root 
$(CURDIR)/debian/python-boto \
-   --install-scripts usr/share/doc/python-boto/examples/ \
-   --install-layout=deb ; \
-   done
-
-   for f in `find $(CURDIR)/debian/python-boto -name \*.py`; do \
-   sed -e '\,^#!/usr/bin/env python,d' < $$f > $$f.tmp; \
-   mv $$f.tmp $$f; \
-   done
-
# Python 3.x
set -e ; for pyvers in $(PYTHON3S); do \
python$$pyvers setup.py install --root 
$(CURDIR)/debian/python3-boto \
@@ -54,7 +41,6 @@
dh_installchangelogs
dh_compress
dh_fixperms
-   dh_python2
dh_python3
dh_gencontrol
dh_installdeb
diff -u python-boto-2.49.0/debian/tests/control 
python-boto-2.49.0/debian/tests/control
--- python-boto-2.49.0/debian/tests/control
+++ python-boto-2.49.0/debian/tests/control
@@ -1,3 +1,3 @@
 Tests: unit
-Depends: python-boto, python-nose (>= 1.3.0), python-mock (>= 1.0.1), 
python-httpretty (>= 0.6.3)
+Depends: python3-boto, python3-nose (>= 1.3.0), python3-mock (>= 1.0.1), 
python3-httpretty (>= 0.6.3)
 Restrictions: allow-stderr
diff -u python-boto-2.49.0/debian/tests/unit 
python-boto-2.49.0/debian/tests/unit
--- python-boto-2.49.0/debian/tests/unit
+++ python-boto-2.49.0/debian/tests/unit
@@ -5,5 +5,5 @@
 cd "$ADTTMP"
 
-for python in $(pyversions -i); do
+for python in $(py3versions -i); do
 $python tests/test.py unit > /dev/null
 done

Bug#947367: lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0'

[Paul Gevers]

Source: lebiniou, lebiniou-data
Control: found -1 lebiniou/3.32-1
Control: found -1 lebiniou-data/3.28-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of lebiniou the autopkgtest of lebiniou-data fails
in testing on when that autopkgtest is run with the binary packages of
lebiniou from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
lebiniou   from testing3.32-1
lebiniou-data  from testing3.28-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of lebiniou to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/l/lebiniou-data/3757794/log.gz

autopkgtest [14:11:01]: test command1: lebiniou --stats
autopkgtest [14:11:01]: test command1: [---
[k] Using default configuration file: /home/debci/.lebiniourc
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4568:(_snd_config_evaluate) function
snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4568:(_snd_config_evaluate) function snd_func_concat
returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4568:(_snd_config_evaluate) function snd_func_refer
returned error: No such file or directory
ALSA lib conf.c:5047:(snd_config_expand) Evaluate error: No such file or
directory
ALSA lib pcm.c:2564:(snd_pcm_open_noupdate) Unknown PCM default
O_o error opening PCM device default
autopkgtest [14:11:02]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Processed: lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0'

[Debian Bug Tracking System]

Processing control commands:

> found -1 lebiniou/3.32-1
Bug #947367 [src:lebiniou, src:lebiniou-data] lebiniou breaks lebiniou-data 
arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
Marked as found in versions lebiniou/3.32-1.
> found -1 lebiniou-data/3.28-2
Bug #947367 [src:lebiniou, src:lebiniou-data] lebiniou breaks lebiniou-data 
arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
Marked as found in versions lebiniou-data/3.28-2.

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

Processed: tagging 875137

[Debian Bug Tracking System]

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

> tags 875137 + pending
Bug #875137 [src:qjoypad] [qjoypad] Future Qt4 removal from Buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#943608: tests segfault when run with Python 3.8

[Pierre-Elliott Bécue]

Le mardi 10 décembre 2019 à 12:27:35-0700, Daniele Nicolodi a écrit :
> Hello,
> 
> On Tue, 26 Nov 2019 13:06:24 +0100 "Dr. Tobias Quathamer"
>  wrote:> I've forwarded this bug upstream, and further
> investigation by them
> > seems to indicate that this is actually a bug in CPython.
> > 
> > I'm therefore cloning and reassigning this bug, feel free to
> > revert this if you don't agree.
> 
> A while ago I opened a merge request with upstream with a workaround
> that fixes the segfault with CPython 3.8. As it seems that CPython 3.8.1
> will be released with the bug not fixed, it may be worth to apply the
> patch to the Debian package.
> 
> https://bitbucket.org/blais/beancount/pull-requests/139
> 
> All the patch does is to make the C code Python 3.9 ready, avoiding
> raising a warning, which ultimately results in the segfault. The patch
> seems very low risk to me.

Dear Daniele,

Thanks for the patch.

I adapted it a little to reduce it's volume:

https://salsa.debian.org/python-team/applications/beancount/blob/debian/master/debian/patches/0003-parser-Work-around-python3.8-bug-causing-a-segmentat.patch

The #define PY_SSIZE_T_CLEAN was in both parser.h and parser.c, and the
removal of the two other includes seems out of scope for this bugfix
IMO.

Is it fine with you?

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#947364: libgl-dev: Missing dependency on libx11-dev

[Andreas Metzler]

Package: libgl-dev
Version: 1.3.0-5
Severity: serious

Hello,

libgl-dev seems to lack a dependency on libx11-dev. Rebuilding e.g.
3depict results in the following error:

/usr/include/GL/glx.h:30:10: fatal error: X11/Xlib.h: No such file or directory
   30 | #include 

cu Andreas

Bug#947363: colord-kde: FTBFS XEventHandler.cpp:25:10: fatal error: xcb/randr.h: No such file or directory

[Andreas Beckmann]

Source: colord-kde
Version: 0.5.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

colord-kde/experimental FTBFS in a curent sid/experimental environment:

/build/colord-kde-0.5.0/colord-kded/XEventHandler.cpp:25:10: fatal error: 
xcb/randr.h: No such file or directory
   25 | #include 
  |  ^
compilation terminated.

Probably a direct Build-Depends: libxcb-randr0-dev is now needed while
this was previously pulled by some other B-D.


Andreas


colord-kde_0.5.0-3.log.gz
Description: application/gzip

Bug#937563: marked as done (pytest-mock: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 18:05:56 +
with message-id 
and subject line Bug#937563: fixed in pytest-mock 1.10.4-3
has caused the Debian Bug report #937563,
regarding pytest-mock: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pytest-mock

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: pytest-mock
Source-Version: 1.10.4-3

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pytest-mock 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 12:39:37 -0500
Source: pytest-mock
Architecture: source
Version: 1.10.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937563
Changes:
 pytest-mock (1.10.4-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937563
Checksums-Sha1:
 38a5c150c62ea8b473df756514824dc698e67bf0 2180 pytest-mock_1.10.4-3.dsc
 392ab904d177a162c2e4751c788416aaf0ef5c55 4052 
pytest-mock_1.10.4-3.debian.tar.xz
 b05df0dd2e07725b35db5b6689241681c56f76a2 6194 
pytest-mock_1.10.4-3_source.buildinfo
Checksums-Sha256:
 a33b6c706c988f52d05e6f7715d043a3682cff7eb4e85b98a6b9021254b7815f 2180 
pytest-mock_1.10.4-3.dsc
 eef3a18dd72f24eaa7ed9de507f8b6e535243e3c25dfeaa5de0c436f51dd1d84 4052 
pytest-mock_1.10.4-3.debian.tar.xz
 de27e6e63faf852a2bf826348277123ddf4347897ad694f550e8ca76c62da8db 6194 

Bug#933474: marked as done (cubicsdr: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 18:04:41 +
with message-id 
and subject line Bug#933474: fixed in cubicsdr 0.2.5+dfsg-2
has caused the Debian Bug report #933474,
regarding cubicsdr: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Source: cubicsdr
Source-Version: 0.2.5+dfsg-2

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated cubicsdr 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 18:50:28 +0100
Source: cubicsdr
Architecture: source
Version: 0.2.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 933474
Changes:
 cubicsdr (0.2.5+dfsg-2) unstable; urgency=medium
 .
   * Rebuild against wxWidgets GTK 3 package. (Closes: #933474)
   * Recommend soapysdr-module-all, we need at least one module.
   * Add debian/gitlab-ci.yml.
Checksums-Sha1:
 bb7db8ca28a02b48378ed3c9f8bb506cf005c413 2126 cubicsdr_0.2.5+dfsg-2.dsc
 762c50fe1feb2caf5817359f488f8049b622bd43 10148 
cubicsdr_0.2.5+dfsg-2.debian.tar.xz
Checksums-Sha256:
 bd239a4e4aa435b2983de3e0cc65b91860beb302b8dd7c872afaf74569e50b81 2126 
cubicsdr_0.2.5+dfsg-2.dsc
 5294eed487b8c1f5bc08560360f551fc49b142675073088894b4ace99b82f13f 10148 
cubicsdr_0.2.5+dfsg-2.debian.tar.xz
Files:
 a9cc8c52aba60933b1326fc1da6932bc 2126 hamradio optional 
cubicsdr_0.2.5+dfsg-2.dsc
 4fda598fbda977d4a939509137c9899d 10148 hamradio optional 
cubicsdr_0.2.5+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl4DohoACgkQTFprqxLS
p655nhAAi5652FMlZyWv5OlcUqXC8cjtRDqBq53kL+l7xv7y04xFcbNZklE7fOkg
FnzS9YsSFrERPUQF1ztSHMXuQIGLFBCrnXSQiorEaMg2slXOU8x1764x9MJv6TeS
P0da+1ROfoEU2t1guzo+l/lCDQVnp8MdjbyuIGv6pyxzWiU2rlIk35zlqB4jJNVT
RQ2OJdbnHvxLv8uQNiGcrlnVy5DYHdam9jwtvlI11oDjqjbp8QPk/3FqiMxeIJS+
L2blShwMi0IIIHHqVm94f+w6Awn0zqJb8TUKfB17qD2iBwjMZbe3IIFSKiyOHG8f
pQZHoIViuxo67ZIB4kr4b/zTeGsB0dtmgUoubs6tT6ZEotkEB7R8weWDV/nJS/pE
HG26hSG7ZJz0VM4s9C9ce3qMACjSfkMIQChwBJDl+49jFJZnmJsrXBTtDqTodR8c
3U+HqpPa5LW/aIf0C8JXwfBJJnMyanpN71cbXMtDiN+4VzsBWBmz83ai78HVYq+v
hrkSL71XQRpYfWSGEJqo5TtoG54H1PbdoLj4fCr5HHiCfSP6xr/CpmWxUj3pKskc
P1x/wGopjCSc2yTMKwtswXOVt9RYtb+VL1RmKNeApLRcMH1/38rRxbkZuBbLmMqs
KBfUudasxH1rxBSDY6ONHiDWFkmJOz2T7wuNHGPmRkoR/WUzrsE=
=QUoX
-END PGP SIGNATURE End Message ---

Processed: Please switch to Python 3

[Debian Bug Tracking System]

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

> fixed 932543 1.1.1+git20191122.ec024c3-1
Bug #932543 {Done: Andreas Tille } [src:python-pbcommand] 
Please switch to Python 3
Marked as fixed in versions python-pbcommand/1.1.1+git20191122.ec024c3-1.
> thanks
Stopping processing here.

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

Bug#936924: Moving libsvm to Debian Science team

[Chen-Tse Tsai]

Got it. Thanks! I missed the c++filt part.

Chen-Tse


On Wed, Dec 25, 2019 at 12:27 PM Christian Kastner  wrote:

> On 2019-12-25 18:08, Chen-Tse Tsai wrote:
> > Thanks Andreas and Christian for the updates/comments. I agree that I
> > should have been more verbose in the changelog. I'm tracing all the
> > commits to learn more about packaging. I was playing with gbp for
> > updating upstream. I really like how it works with git! No worries, my
> > time was not wasted anyway.
>
> If you like gbp, then it's already a team win :-)
>
> >
> > I talked to Christian briefly about the symbol file. He added one for
> > liblinear4. I have a question about this file. The symbol file I
> > generated looks a bit different from liblinear4.symbols, in which
> > several lines start with (c++) and contain the exact parameters. I
> > couldn't figure out how to make dpkg-gensymbols produce this.
>
> Yeah, the C++ symbols generated are the mangled versions. You need to
> unmangle them by piping the generated file through c++filt, and then add
> the (c++) prefix to tell dpkg-gensymbols about this. The
> UsingSymbolsFiles [1] page has a practical example on the bottom.
>
> The c++filt(1) and dpkg-gensymbols(1) man pages have theoretical
> background on this, but TBH, I don't think it's needed.
>
> There are voices that say that symbols files for C++ libraries are
> overly hard to maintain, but in case of this specific upstream, I didn't
> have a negative experience, and it did help me detect breaking changes a
> few times.
>
> [1] https://wiki.debian.org/UsingSymbolsFiles
>

Processed: Please switch to Python 3

[Debian Bug Tracking System]

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

> reassign 932543 src:python-pbcommand 1.1.1-1
Bug #932543 {Done: Andreas Tille } [python-pbcommand] Please 
switch to Python 3
Bug reassigned from package 'python-pbcommand' to 'src:python-pbcommand'.
No longer marked as found in versions python-pbcommand/1.1.1-1.
No longer marked as fixed in versions 
python-pbcommand/1.1.1+git20191122.ec024c3-1.
Bug #932543 {Done: Andreas Tille } [src:python-pbcommand] 
Please switch to Python 3
Marked as found in versions python-pbcommand/1.1.1-1.
> thanks
Stopping processing here.

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

Bug#947352: marked as done (python-pyqt5.qtwebengine: No install candidate in raspbian stretch/buster/bullseye/sid)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 20:34:43 +0300
with message-id <20191225173443.ga3...@mitya57.me>
and subject line Re: Bug#947352: python-pyqt5.qtwebengine: No install candidate 
in raspbian stretch/buster/bullseye/sid
has caused the Debian Bug report #947352,
regarding python-pyqt5.qtwebengine: No install candidate in raspbian 
stretch/buster/bullseye/sid
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.)


-- 
947352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyqt5.qtwebengine
Version: 5.11.3+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Unknown

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Apt-get dist-upgrade -> uninstall calibre and install puthon-qt5 packages
Work around: apt-get upgrade and leave rest of the packages at old level.

   * What was the outcome of this action?

Apt-get dist-upgrade wants to uninstall calibre as it wants to upgrade
python-gt5 packages and this package isn't available in raspbian.

   * What outcome did you expect instead?

Correct upgrade of all installed packages, including calibre.

Calibre upgrad e would be from 4.0.0+really3.48.dfsg-1 to 4.6.0+dfsg-1

This is probably a raspbian only issue or a calibre dependency that should
be fixed.

*** End of the template - remove these template lines ***


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux bullseye/sid
Release:oldstable
Codename:   sid
Architecture: armv7l

Kernel: Linux 4.19.57-v7+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) 
(ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE=en_US.ISO8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi Jan,

On Wed, Dec 25, 2019 at 12:29:58PM +0100, Jan Huijsmans wrote:
> [...]
>
>* What outcome did you expect instead?
>
> Correct upgrade of all installed packages, including calibre.
>
> Calibre upgrade would be from 4.0.0+really3.48.dfsg-1 to 4.6.0+dfsg-1
>
> This is probably a raspbian only issue or a calibre dependency that should
> be fixed.

Qt WebEngine itself is not available for Raspbian.

There is nothing I can do about this in Debian, you should discuss this with
Raspbian maintainers.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---

Processed: py2removal RC severity updates - 2019-12-25 17:36:55.637219+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-pytest-mock is a module and has 0 external rdeps or not in testing
> severity 937563 serious
Bug #937563 [src:pytest-mock] pytest-mock: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#936924: Moving libsvm to Debian Science team

[Christian Kastner]

On 2019-12-25 18:08, Chen-Tse Tsai wrote:
> Thanks Andreas and Christian for the updates/comments. I agree that I
> should have been more verbose in the changelog. I'm tracing all the
> commits to learn more about packaging. I was playing with gbp for
> updating upstream. I really like how it works with git! No worries, my
> time was not wasted anyway.

If you like gbp, then it's already a team win :-)
 
> 
> I talked to Christian briefly about the symbol file. He added one for
> liblinear4. I have a question about this file. The symbol file I
> generated looks a bit different from liblinear4.symbols, in which
> several lines start with (c++) and contain the exact parameters. I
> couldn't figure out how to make dpkg-gensymbols produce this.

Yeah, the C++ symbols generated are the mangled versions. You need to
unmangle them by piping the generated file through c++filt, and then add
the (c++) prefix to tell dpkg-gensymbols about this. The
UsingSymbolsFiles [1] page has a practical example on the bottom.

The c++filt(1) and dpkg-gensymbols(1) man pages have theoretical
background on this, but TBH, I don't think it's needed.

There are voices that say that symbols files for C++ libraries are
overly hard to maintain, but in case of this specific upstream, I didn't
have a negative experience, and it did help me detect breaking changes a
few times.

[1] https://wiki.debian.org/UsingSymbolsFiles

Bug#936924: Moving libsvm to Debian Science team

[Chen-Tse Tsai]

Thanks Andreas and Christian for the updates/comments. I agree that I
should have been more verbose in the changelog. I'm tracing all the commits
to learn more about packaging. I was playing with gbp for updating
upstream. I really like how it works with git! No worries, my time was not
wasted anyway.

I talked to Christian briefly about the symbol file. He added one for
liblinear4. I have a question about this file. The symbol file I generated
looks a bit different from liblinear4.symbols, in which several lines start
with (c++) and contain the exact parameters. I couldn't figure out how to
make dpkg-gensymbols produce this.

Thanks,
Chen-Tse


On Wed, Dec 25, 2019 at 10:02 AM Andreas Tille  wrote:

> On Wed, Dec 25, 2019 at 03:04:47PM +0100, Christian Kastner wrote:
> > On 2019-12-25 10:59, Andreas Tille wrote:
> > > Kind regards
> > >
> > >Andreas.
> >
> > I've re-read my original message and feel that I was overly harsh. I was
> > irritated about the rushed upgrade as in private communication with
> > Chen-Tse, I highlighted precisely the possible complexity of this
> > upgrade and how it should be performed properly -- but, that was private
> > communication.
>
> I admit I did not considered it overly harsh.  My upload was in fact not
> the best idea and your response just reflected it.
>
> > Apologies.
>
> Thanks but from my point of view not needed.  Everything is fine at my
> side and as I said I'll now leave the issue to you who are more
> comfortable with that package.  Something that came to my mind later:
> When upstream does not mark SOVERSIONs:  In this case I usually add a
> symbols file.  Thats more maintenance burden but usually helps to spot
> issues with ABI changes.
>
> Kind regards
>
>Andreas.
>
>
> --
> http://fam-tille.de
>

Bug#947360: coinor-libdylp-dev: ships headers owned by coinor-libcoinutils-dev, coinor-libosi-dev

[Andreas Beckmann]

Package: coinor-libdylp-dev
Version: 1.10.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages.

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

  Selecting previously unselected package coinor-libdylp-dev.
  Preparing to unpack .../coinor-libdylp-dev_1.10.4-1_amd64.deb ...
  Unpacking coinor-libdylp-dev (1.10.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/coin/CoinAlloc.hpp', which is also in 
package coinor-libcoinutils-dev 2.11.3+repack1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb

  Selecting previously unselected package coinor-libdylp-dev.
  Preparing to unpack .../coinor-libdylp-dev_1.10.4-1_amd64.deb ...
  Unpacking coinor-libdylp-dev (1.10.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/coin/OsiAuxInfo.hpp', which is also in 
package coinor-libosi-dev 0.108.5+repack1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb


cheers,

Andreas


coinor-libcoinutils-dev=2.11.3+repack1-1_coinor-libdylp-dev=1.10.4-1.log.gz
Description: application/gzip

Bug#891993: syrthes-gui uses obsolete libs Qt4 and Python2

[Moritz Mühlenhoff]

On Sun, Sep 15, 2019 at 03:57:47PM +0200, Gilles Filippini wrote:
> > syrthes is the only remaining packages blocking the removal of pyqwt5. Are
> > you planning to port the GUI yourself, should we (temporarily, until fixed)
> > drop the syrthes-gui package or if that's not an option, should syrthes be
> > (temporarily) removed altogether?
> 
> Syrthes' upstream is quite unresponsive. A version 5 should be on its
> way but there is no place to download it from and the preview I had more
> than one year ago brought many dependencies with unclear licensing.
> 
> I think the best option for now would be to just drop syrthes-gui.

Patch attached.

Cheers,
Moritz
diff -aur syrthes-4.3.0-dfsg1.orig/debian/control syrthes-4.3.0-dfsg1/debian/control
--- syrthes-4.3.0-dfsg1.orig/debian/control	2019-01-06 02:09:26.0 +0100
+++ syrthes-4.3.0-dfsg1/debian/control	2019-09-13 23:14:11.711235465 +0200
@@ -4,7 +4,6 @@
 Maintainer: Debian Science Maintainers 
 Uploaders: Gilles Filippini 
 Build-Depends: debhelper (>= 9~), python, dh-python, libmedc-dev, libhdf5-mpi-dev, libmetis-dev, libscotch-dev,
- pyqt4-dev-tools, python-qwt5-qt4,
  code-saturne-bin (>= 4.0.0) [!s390x], code-saturne-include (>= 4.0.0) [!s390x]
 Standards-Version: 4.3.0
 Homepage: https://www.edf.fr/en/the-edf-group/world-s-largest-power-company/activities/research-and-development/scientific-communities/simulation-softwares?logiciel=10818
@@ -34,15 +33,6 @@
  creating new SYRTHES cases, converting mesh files to SYRTHES, or converting
  SYRTHES files to MED or Ensight formats.
 
-Package: syrthes-gui
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-qwt5-qt4, syrthes (>= 4.1.1~)
-Description: Transient thermal simulations in complex solid geometries - GUI
- SYRTHES is a general purpose thermal software developed at EDF R which
- models conduction and radiation heat transfers in complex geometries.
- .
- This package contains a graphical user interface for SYRTHES.
-
 Package: syrthes-tests
 Architecture: all
 Depends: ${misc:Depends}, ${python:Depends}, python
Nur in syrthes-4.3.0-dfsg1/debian: control~.

Bug#936249: bugs-everywhere: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:12:24AM +, Matthias Klose wrote:
> Package: src:bugs-everywhere
> Version: 1.1.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

bugs-everywhere is dead upstream, the last commits are from 2013.

Are you planning to port it to Python 3 yourself? Otherwise I'll
request it's removal from the archive.

Cheers,
Moritz

Bug#945920: Hot Fix did not work for me

[Luis Finotti]

FWIW, the hot fix proposed by Stefan Bühler did not work for me...

# inxi -v3
System:Host: l5580 Kernel: 5.3.14-towo.1-siduction-amd64 x86_64 bits:
64 compiler: gcc v: 9.2.1 Desktop: KDE Plasma 5.14.5
   Distro: siduction 18.2.0 Patience - kde - (201803072323) base:
Debian GNU/Linux bullseye/sid
Machine:   Type: Laptop System: Dell product: Latitude 5580 v: N/A serial:
C306PN2
   Mobo: Dell model: 0DN786 v: A00 serial: /C306PN2/CNCMK0074D014B/
UEFI: Dell v: 1.16.0 date: 07/03/2019
Battery:   ID-1: BAT0 charge: 44.9 Wh condition: 44.9/68.0 Wh (66%) model:
BYD DELL KCM8281 status: Full
CPU:   Topology: Quad Core model: Intel Core i7-7820HQ bits: 64 type:
MT MCP arch: Kaby Lake rev: 9 L2 cache: 8192 KiB
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 46398
   Speed: 3897 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 2514
2: 3566 3: 3424 4: 2903 5: 3383 6: 3074 7: 3758
   8: 3492
Graphics:  Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v:
kernel bus ID: 00:02.0
   Device-2: NVIDIA GM107 [GeForce 940MX] vendor: Dell driver: N/A
bus ID: 01:00.0
   Display: x11 server: X.Org 1.20.6 driver: modesetting unloaded:
fbdev,vesa resolution: 1920x1080~60Hz
   OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
v: 4.6 Mesa 19.3.1 direct render: Yes
Network:   Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v:
3.2.6-k port: f040 bus ID: 00:1f.6
   IF: enp0s31f6 state: down mac: d4:81:d7:bc:94:0c
   Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network
Adapter vendor: Dell driver: ath10k_pci v: kernel
   port: e000 bus ID: 02:00.0
   IF: wlp2s0 state: up mac: 5c:ea:1d:7c:fe:63
   Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-6:3
Drives:Local Storage: total: 238.47 GiB used: 139.30 GiB (58.4%)
Info:  Processes: 299 Uptime: 4d 23h 55m Memory: 15.52 GiB used: 3.93
GiB (25.3%) Init: systemd runlevel: 5 Compilers:
   gcc: 9.2.1 Shell: bash v: 5.0.11 inxi: 3.0.37

# apt policy chromium
chromium:
  Installed: 79.0.3945.79-1
  Candidate: 79.0.3945.79-1
  Version table:
 *** 79.0.3945.79-1 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status

# sha1sum /usr/lib/chromium/chromium*
036f623e158cffaa91be63df307bb2eda4d359e1  /usr/lib/chromium/chromium
5056c781602f4bbd41f06b3bd1940b6edbd7dc8c
 /usr/lib/chromium/chromium-pre-patched

Let me know if I can provide any more info.

Luis

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

[Andreas Tille]

Hi Julien,

can you imagine any process that might delete the existing manpage?

Kind regards

   Andreas.

On Wed, Dec 25, 2019 at 10:44:37AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi!
> 
> El mié., 25 dic. 2019 08:34, Andreas Tille  escribió:
> 
> > Hi Lisandro,
> >
> > On Wed, Dec 25, 2019 at 07:05:22AM -0300, Lisandro Damián Nicanor Pérez
> > Meyer wrote:
> > >
> > > Sorry, I forgot to mention that the build failures came directly from
> > > buildds, so I would expect then to be ok.
> >
> > Well, buildd or not - I can not reproduce and it technically makes
> > no sense to me, sorry.
> >
> 
> I will blame myself again for not being verbose enough:
> 
> https://buildd.debian.org/status/package.php?p=bppphyview
> 
> It's not failing on all archs.

-- 
http://fam-tille.de

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

On Wed, Dec 25, 2019 at 03:04:47PM +0100, Christian Kastner wrote:
> On 2019-12-25 10:59, Andreas Tille wrote:
> > Kind regards
> > 
> >Andreas.
> 
> I've re-read my original message and feel that I was overly harsh. I was
> irritated about the rushed upgrade as in private communication with
> Chen-Tse, I highlighted precisely the possible complexity of this
> upgrade and how it should be performed properly -- but, that was private
> communication.

I admit I did not considered it overly harsh.  My upload was in fact not
the best idea and your response just reflected it.
 
> Apologies.

Thanks but from my point of view not needed.  Everything is fine at my
side and as I said I'll now leave the issue to you who are more
comfortable with that package.  Something that came to my mind later:
When upstream does not mark SOVERSIONs:  In this case I usually add a
symbols file.  Thats more maintenance burden but usually helps to spot
issues with ABI changes.

Kind regards

   Andreas.
 

-- 
http://fam-tille.de

Bug#936924: Moving libsvm to Debian Science team

[Christian Kastner]

On 2019-12-25 10:59, Andreas Tille wrote:
> Kind regards
> 
>Andreas.

I've re-read my original message and feel that I was overly harsh. I was
irritated about the rushed upgrade as in private communication with
Chen-Tse, I highlighted precisely the possible complexity of this
upgrade and how it should be performed properly -- but, that was private
communication.

Apologies.

Bug#945672: fortunes-mario: Python2 removal in sid/bullseye

[Juhani Numminen]

Control: tags -1 patch

On Wed, 27 Nov 2019 23:58:48 + Sandro Tosi  wrote:
> Source: fortunes-mario
> Version: 0.21-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

Dear Maintainers,

I propose that we stop shipping the python2 file which in fact is
part of build system for a PDF, and ship the actual PDF book in
the package instead. How do you find this approach?

An NMU patch is attached and I've tested it using sbuild.

Regards,
Juhani
diff -Nru fortunes-mario-0.21/debian/changelog 
fortunes-mario-0.21/debian/changelog
--- fortunes-mario-0.21/debian/changelog2015-08-22 06:19:48.0 
+0300
+++ fortunes-mario-0.21/debian/changelog2019-12-25 15:06:52.0 
+0200
@@ -1,3 +1,11 @@
+fortunes-mario (0.21-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Converted livro.py to python3 (Closes: #945672).
+  * Ship the actual book PDF instead of its build files.
+
+ -- Juhani Numminen   Wed, 25 Dec 2019 15:06:52 
+0200
+
 fortunes-mario (0.21-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru fortunes-mario-0.21/debian/control fortunes-mario-0.21/debian/control
--- fortunes-mario-0.21/debian/control  2015-08-18 03:31:52.0 +0300
+++ fortunes-mario-0.21/debian/control  2019-12-25 15:06:52.0 +0200
@@ -3,7 +3,13 @@
 Priority: optional
 Maintainer: Otavio Salvador 
 Uploaders: Fernando Ike de Oliveira 
-Build-Depends: debhelper (>= 9)
+Build-Depends: debhelper (>= 9),
+   ghostscript,
+   poppler-utils,
+   psutils,
+   python3,
+   texlive-lang-portuguese,
+   texlive-latex-extra,
 Build-Depends-Indep: fortune-mod (>= 1.99.1-6)
 Standards-Version: 3.9.6
 Homepage: http://github.com/fike/fortunes-mario
@@ -13,7 +19,6 @@
 Package: fortunes-mario
 Architecture: all
 Depends: fortune-mod (>= 1.99.1-6), 
- python, 
  ${misc:Depends}
 Provides: fortune-cookie-db
 Description: Fortunes files from Mario
diff -Nru fortunes-mario-0.21/debian/docs fortunes-mario-0.21/debian/docs
--- fortunes-mario-0.21/debian/docs 2015-08-22 06:10:43.0 +0300
+++ fortunes-mario-0.21/debian/docs 2019-12-25 14:54:27.0 +0200
@@ -2,3 +2,4 @@
 LEIAME
 BUGS
 CREDITOS
+livro/mario_fortunes-livro.pdf
diff -Nru fortunes-mario-0.21/debian/install fortunes-mario-0.21/debian/install
--- fortunes-mario-0.21/debian/install  2015-08-18 03:31:52.0 +0300
+++ fortunes-mario-0.21/debian/install  2019-12-25 13:02:32.0 +0200
@@ -1,2 +1 @@
 mario.*usr/share/games/fortunes/
-livro  usr/share/games/fortunes/
diff -Nru fortunes-mario-0.21/debian/patches/livro-bash-in-make.patch 
fortunes-mario-0.21/debian/patches/livro-bash-in-make.patch
--- fortunes-mario-0.21/debian/patches/livro-bash-in-make.patch 1970-01-01 
02:00:00.0 +0200
+++ fortunes-mario-0.21/debian/patches/livro-bash-in-make.patch 2019-12-25 
15:05:59.0 +0200
@@ -0,0 +1,12 @@
+Description: livro/Makefile requires bash
+ dash cannot expand brace expansion {tex,dvi,...} in the clean target
+Author: Juhani Numminen 
+
+--- a/livro/Makefile
 b/livro/Makefile
+@@ -1,3 +1,5 @@
++SHELL=/bin/bash
++
+ all: booklet_from_pdf
+ 
+ SRCDIR=../
diff -Nru fortunes-mario-0.21/debian/patches/livro-latex-utf8.patch 
fortunes-mario-0.21/debian/patches/livro-latex-utf8.patch
--- fortunes-mario-0.21/debian/patches/livro-latex-utf8.patch   1970-01-01 
02:00:00.0 +0200
+++ fortunes-mario-0.21/debian/patches/livro-latex-utf8.patch   2019-12-25 
15:05:24.0 +0200
@@ -0,0 +1,14 @@
+Description: the encoding used is utf8
+Author: Juhani Numminen 
+
+--- a/livro/livro.py
 b/livro/livro.py
+@@ -13,7 +13,7 @@
+ \usepackage[brazil]{babel}
+ \usepackage{indentfirst}
+ % #\usepackage[T1]{fontenc}
+-\usepackage[latin1]{inputenc}
++\usepackage[utf8x]{inputenc}
+ \usepackage{fancyhdr}
+ \usepackage{fancyvrb}
+ \usepackage{url}
diff -Nru fortunes-mario-0.21/debian/patches/livro-python3.patch 
fortunes-mario-0.21/debian/patches/livro-python3.patch
--- fortunes-mario-0.21/debian/patches/livro-python3.patch  1970-01-01 
02:00:00.0 +0200
+++ fortunes-mario-0.21/debian/patches/livro-python3.patch  2019-12-25 
15:05:36.0 +0200
@@ -0,0 +1,21 @@
+Description: convert the python2 script to python3
+Author: Juhani Numminen 
+
+--- a/livro/livro.py
 b/livro/livro.py
+@@ -1,4 +1,5 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
++# -*- coding: utf-8 -*-
+ 
+ import sys
+ 
+@@ -68,7 +69,7 @@
+ tex_file.write(r'\chapter{' + section_name + '}\n')
+ tex_file.write(bminipage + '\n')
+ 
+-print section_name
++print(section_name)
+ if section_name == 'mario.arteascii':
+ tex_file.write(bverbatimascii + '\n')
+ elif 

Processed: Re: Bug#945672: fortunes-mario: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #945672 [src:fortunes-mario] fortunes-mario: Python2 removal in sid/bullseye
Added tag(s) patch.

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

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

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

El mié., 25 dic. 2019 08:34, Andreas Tille  escribió:

> Hi Lisandro,
>
> On Wed, Dec 25, 2019 at 07:05:22AM -0300, Lisandro Damián Nicanor Pérez
> Meyer wrote:
> >
> > Sorry, I forgot to mention that the build failures came directly from
> > buildds, so I would expect then to be ok.
>
> Well, buildd or not - I can not reproduce and it technically makes
> no sense to me, sorry.
>

I will blame myself again for not being verbose enough:

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

It's not failing on all archs.

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

[Pierre-Elliott Bécue]

Le mercredi 25 décembre 2019 à 13:16:21+0100, Moritz Mühlenhoff a écrit :
> On Tue, Dec 24, 2019 at 11:30:58PM +0100, Pierre-Elliott Bécue wrote:
> > 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
> 
> Ack, I've just filed an RM bug.
> 
> Cheers,

Sandro Tosi already asked for the removal in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947099

Cheers,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#947266: python3-geopandas: ships /usr/lib/python3/dist-packages/examples/*

[Andreas Beckmann]

On 24/12/2019 05.31, Sebastiaan Couwenberg wrote:
> The packages doesn't install the examples there itself, it seems that
> pybuild does that without being explicitly told to.
> 
> This seems to be a bug in pybuild not geopandas.
> 
> Are you sure this is a bug in geopandas?

It may not be a bug in src:geopandas (if it disappears using a fixed
toolchain), but it is a bug in python3-geopandas as we have it now. Or
rather before -2.

Andreas

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

[Moritz Mühlenhoff]

On Tue, Dec 24, 2019 at 11:30:58PM +0100, Pierre-Elliott Bécue wrote:
> 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

Ack, I've just filed an RM bug.

Cheers,
Moritz

Bug#939362: marked as done (grantlee5: FTBFS with Qt 5.12.4 in experimental)

[Debian Bug Tracking System]

Your message dated Wed, 25 Dec 2019 12:04:36 +
with message-id 
and subject line Bug#939362: fixed in grantlee5 5.2.0-1
has caused the Debian Bug report #939362,
regarding grantlee5: FTBFS with Qt 5.12.4 in experimental
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.)


-- 
939362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grantlee5
Version: 5.1.0-2.1
Severity: serious
Tags: experimental
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

Dear maintainers,

The grantlee5 package fails to build with the version of Qt in experimental,
5.12.4.  This was discovered because Ubuntu also has Qt 5.12.4 in its devel
series, so grantlee5 5.1.0-2.1 has failed to build on all architectures:

[...]
FAIL!  : TestInternationalization::testIntegers(integer-02) Compared values are 
not the same
   Actual   (frLocalizer->localizeNumber(integer)): "7\u202F000"
   Expected (frInteger)   : "7\u00A"
   Loc: [/<>/templates/tests/testinternationalization.cpp(838)]
[...]
Totals: 67 passed, 8 failed, 0 skipped, 0 blacklisted, 22ms
* Finished testing of TestInternationalization *

11/12 Test #12: plainmarkupbuildertest ...   Passed0.03 sec
12/12 Test #11: htmlbuildertest ..   Passed0.04 sec

92% tests passed, 1 tests failed out of 12

Total Test time (real) =   0.12 sec

The following tests FAILED:
 10 - testinternationalization (Failed)
Errors while running CTest
make[2]: *** [Makefile:76: test] Error 8
[...]

  (https://launchpad.net/ubuntu/+source/grantlee5/5.1.0-2.1)

I don't know why the behavior of Qt has changed, but this will eventually
become a serious bug on grantlee5 in unstable once Qt is updated there.

-- 
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: grantlee5
Source-Version: 5.2.0-1

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

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

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated grantlee5 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 12:52:51 +0100
Source: grantlee5
Architecture: source
Version: 5.2.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Krap Maintainers 
Changed-By: Pino Toscano 
Closes: 939362
Changes:
 grantlee5 (5.2.0-1) experimental; urgency=medium
 .
   * New upstream release:
 - fixes build with Qt 5.12 (Closes: #939362)
   * Update watch file to the new download location, and allow xz as format.
   * Switch Vcs-* fields to salsa.debian.org.
   * Add the configuration for the CI on salsa.
   * Update the build dependencies according to the upstream build system:
 - bump cmake to 3.5
 - remove libboost-dev, and qtscript5-dev, no more required
 - add qtdeclarative5-dev
   * Update the patches:
 - datatime-fractional.diff: drop, fixed upstream
   * Add Build-Depends-Package in symbols files.
   * Bump the debhelper compatibility to 12:
 - switch the debhelper build dependency to debhelper-compat 12
 - remove debian/compat
 - remove --parallel for dh, as now done by default
 - switch from dh_install to dh_missing for --fail-missing
 - drop the dh_makeshlibs override, as:
   - -V is done by default
   - plugins are no more misdetected as shared libraries, and thus no need
 to manually exclude them
   * Drop the migration from grantlee5-dbg, no more needed after two Debian
 stable releases.
   * Bump Standards-Version to 4.4.1, no changes required.
   * Mark the library packages as Multi-Arch: same.
   * Remove the , and lcov build dependencies, as they are not used 

Bug#947352: python-pyqt5.qtwebengine: No install candidate in raspbian stretch/buster/bullseye/sid

[Jan Huijsmans]

Package: python-pyqt5.qtwebengine
Version: 5.11.3+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Unknown

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Apt-get dist-upgrade -> uninstall calibre and install puthon-qt5 packages
Work around: apt-get upgrade and leave rest of the packages at old level.

   * What was the outcome of this action?

Apt-get dist-upgrade wants to uninstall calibre as it wants to upgrade
python-gt5 packages and this package isn't available in raspbian.

   * What outcome did you expect instead?

Correct upgrade of all installed packages, including calibre.

Calibre upgrad e would be from 4.0.0+really3.48.dfsg-1 to 4.6.0+dfsg-1

This is probably a raspbian only issue or a calibre dependency that should
be fixed.

*** End of the template - remove these template lines ***


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux bullseye/sid
Release:oldstable
Codename:   sid
Architecture: armv7l

Kernel: Linux 4.19.57-v7+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) 
(ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE=en_US.ISO8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Andreas Tille]

Hi Lisandro,

On Wed, Dec 25, 2019 at 07:05:22AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> 
> Sorry, I forgot to mention that the build failures came directly from
> buildds, so I would expect then to be ok.

Well, buildd or not - I can not reproduce and it technically makes
no sense to me, sorry.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#925411: Removing kernel-package? (was: kernel-package: Not suitable for release)

[Bastian Blank]

Hi Manoj

Do you oppose that we finally shoot kernel-package dead, aka remove it
from the archive?

Regards,
Bastian

-- 
Youth doesn't excuse everything.
-- Dr. Janice Lester (in Kirk's body), "Turnabout Intruder",
   stardate 5928.5.

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

[Bastian Blank]

Hi Christoph

On Wed, Dec 25, 2019 at 03:06:19AM +0100, Christoph Anton Mitterer wrote:
> Since last April, the package can't be upgraded as it conflicts with
> the current version of kernel-common.

kernel-common was neither released in Stretch, nor in Buster.

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

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925411

Regards,
Bastian

-- 
Either one of us, by himself, is expendable.  Both of us are not.
-- Kirk, "The Devil in the Dark", stardate 3196.1

Processed: bug 938176 is forwarded to https://github.com/barryp/py-smbpasswd/pull/3

[Debian Bug Tracking System]

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

> forwarded 938176 https://github.com/barryp/py-smbpasswd/pull/3
Bug #938176 [src:python-smbpasswd] python-smbpasswd: Python2 removal in 
sid/bullseye
Set Bug forwarded-to-address to 'https://github.com/barryp/py-smbpasswd/pull/3'.
> thanks
Stopping processing here.

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

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

[Lisandro Damián Nicanor Pérez Meyer]

Hi Andreas!

El mié., 25 dic. 2019 04:24, Andreas Tille  escribió:

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


Sorry, I forgot to mention that the build failures came directly from
buildds, so I would expect then to be ok.

Cheers, Lisandro.

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

[Debian Bug Tracking System]

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

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

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

Bug#945920: Chromium segfaults - analysis and binary hotfix

[Stefan Bühler]

Hi.

Thanks for the hint with reproducing it via the Task Manager, makes 
debugging a lot easier :)

So the problem is `task_manager::TaskManagerImpl::Refresh()` calling
`memory_instrumentation::MemoryInstrumentation::GetInstance()` and using the
returned pointer without checking it; but is is `NULL`; this is what the
segfault in
`memory_instrumentation::MemoryInstrumentation::RequestPrivateMemoryFootprint()`
(0x55...f87; dereferencing `this` from register `rdi`) is about.

(gdb) frame 1
(gdb) disassemble /r
Dump of assembler code for function 
_ZN12task_manager15TaskManagerImpl7RefreshEv:
...
   0x591ba757 <+39>:41 80 bd 99 01 00 00 00 cmpb   $0x0,0x199(%r13)
   0x591ba75f <+47>:0f 84 7b 02 00 00   je 0x591ba9e0 
<_ZN12task_manager15TaskManagerImpl7RefreshEv+688>
   0x591ba765 <+53>:a8 80   test   $0x80,%al
   0x591ba767 <+55>:0f 85 b3 01 00 00   jne0x591ba920 
<_ZN12task_manager15TaskManagerImpl7RefreshEv+496>
...
(gdb) info proc mappings
...
  Start Addr   End Addr   Size Offset objfile
  0x4000 0x6035b000  0xae070000x0 
/usr/lib/chromium/chromium
  0x6035b000 0x60922000   0x5c7000  0xae06000 
/usr/lib/chromium/chromium
  0x60922000 0x6098b0000x69000  0xb3cd000 
/usr/lib/chromium/chromium

So for a hotfix I changed the `je` at `+47` into `jne`; this negates
the check for `!waiting_for_memory_dump_` in
https://github.com/chromium/chromium/blob/master/chrome/browser/task_manager/sampling/task_manager_impl.cc#L603
and should make it never use that block.

The offset of `0f 84` in the file is:
0x591ba75f - 0x4000 = 0x3C6675F

To patch it to `0f 85`:

$ cp -a /usr/lib/chromium/chromium /usr/lib/chromium/chromium-pre-patched
$ printf '3C66760: 85\n' | xxd -r -  /usr/lib/chromium/chromium
$ sha1sum /usr/lib/chromium/chromium*
036f623e158cffaa91be63df307bb2eda4d359e1  /usr/lib/chromium/chromium
5056c781602f4bbd41f06b3bd1940b6edbd7dc8c  /usr/lib/chromium/chromium-pre-patched

cheers,
Stefan

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

On Wed, Dec 25, 2019 at 10:03:00AM +0100, Christian Kastner wrote:
> Andreas, what are you doing?
> 
> On 2019-12-25 07:52, Andreas Tille wrote:
> > On Tue, Dec 24, 2019 at 10:39:55AM -0500, Chen-Tse Tsai wrote:
> >> 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.
> 
> 24 files changed, but debian/changelog only contains two entries.
> Nothing about changes to debhelper compat level, patches, etc. It would
> have been far more helpful to Chen-Tse (and thus to the team) to supply
> feedback on this.

  [ Andreas Tille ]
  * Secure URI in copyright format
  * Remove trailing whitespace in debian/changelog
  * Remove trailing whitespace in debian/control
  * Remove trailing whitespace in debian/copyright
  * Trim trailing whitespace.
  * Use secure URI in Homepage field.
  * Fix day-of-week for changelog entry 2.91-1.
  * Use Files-Excluded to exclude Windows binaries

Compat-level was changed before:

  e544cbc2 (Chen-Tse Tsai  2019-12-24 22:20:23 -0500  7)  debhelper-compat (= 
12),

> Looking at Salsa, you also imported the new upstream version 3.24 an
> hour ago, something that Chen-Tse said just before that he would be
> working on? Is he wasting his time now?

I intended to help by recommending some automatic procedure
that fixes a lot of lintian issues.
 
> Furthermore, I indicated previously that after 3 years, we will almost
> certainly need a transition (upstream's versioning does not reflect
> SOVER. We arrived at liblinear4 from liblinear1 entirely from Debian
> builds discovering backwards-incompatible changes). Did you check this
> before updating to 3.24?
> 
> Can you please not rush things like this?

Sorry about this.  I should not have uploaded.

> This package has been sitting
> there for 3 years, a few Christmas Holiday days more or less will not
> make a difference. I (who happens to maintain another package by the
> same upstream) offered to help from the 27th; this could have waited
> until then and would have profited from doing so.

I agree and will not rush without coordination with this package. 

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: tagging 939362

[Debian Bug Tracking System]

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

> tags 939362 + pending
Bug #939362 [src:grantlee5] grantlee5: FTBFS with Qt 5.12.4 in experimental
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
939362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939362
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 + pending
Bug #938051 [src:python-psycogreen] python-psycogreen: Python2 removal in 
sid/bullseye
Added tag(s) pending.
> 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#936924: Moving libsvm to Debian Science team

[Christian Kastner]

Andreas, what are you doing?

On 2019-12-25 07:52, Andreas Tille wrote:
> On Tue, Dec 24, 2019 at 10:39:55AM -0500, Chen-Tse Tsai wrote:
>> 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.

24 files changed, but debian/changelog only contains two entries.
Nothing about changes to debhelper compat level, patches, etc. It would
have been far more helpful to Chen-Tse (and thus to the team) to supply
feedback on this.

Looking at Salsa, you also imported the new upstream version 3.24 an
hour ago, something that Chen-Tse said just before that he would be
working on? Is he wasting his time now?

Furthermore, I indicated previously that after 3 years, we will almost
certainly need a transition (upstream's versioning does not reflect
SOVER. We arrived at liblinear4 from liblinear1 entirely from Debian
builds discovering backwards-incompatible changes). Did you check this
before updating to 3.24?

Can you please not rush things like this? This package has been sitting
there for 3 years, a few Christmas Holiday days more or less will not
make a difference. I (who happens to maintain another package by the
same upstream) offered to help from the 27th; this could have waited
until then and would have profited from doing so.

Bug#947346: Useless in Debian

[David Prévot]

Package: php-fig-link-util
Version: 1.1.0-1
Severity: serious

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

I packaged php-fig-link-util as used by symfony, but symfony does not
use is anymore (it contains php-symfony-web-link that also provide
php-psr-link-implementation). There is a priori little point to ship
php-fig-link-util in the next stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature