Bug#947748: marked as done (xorg-server: FTBFS in sid (probably due to newer mesa))

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 09:15:49 +0200
with message-id 
and subject line Re: Bug#947748: xorg-server: FTBFS in sid (probably due to 
newer mesa)
has caused the Debian Bug report #947748,
regarding xorg-server: FTBFS in sid (probably due to newer mesa)
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.)


-- 
947748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorg-server
Version: 2:1.20.6-1
Severity: serious
Tags: patch
Justification: FTBFS

Hello,

Probably since the upload of the newer mesa, xorg-server now FTBFS,
because it misses dri.pc and x11-xcb.pc. The attached patch fixes this.

Samuel

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

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

-- 
Samuel
"c'est pas nous qui sommes à la rue, c'est la rue qui est à nous"
--- debian/control.original 2019-12-29 23:42:11.163003763 +0100
+++ debian/control  2019-12-29 23:42:28.333138832 +0100
@@ -13,6 +13,7 @@
  xutils-dev (>= 1:7.6+4),
  xfonts-utils (>= 1:7.5+1),
  x11proto-dev (>= 2018.4),
+ libx11-xcb-dev,
  xtrans-dev (>= 1.3.5),
  libxau-dev (>= 1:1.0.5-2),
  libxdmcp-dev (>= 1:0.99.1),
@@ -27,6 +28,7 @@
  libaudit-dev [linux-any],
  libdrm-dev (>= 2.4.89) [!hurd-i386],
  libgl1-mesa-dev (>= 9.2),
+ mesa-common-dev,
  libunwind-dev [amd64 arm64 armel armhf hppa i386 ia64 mips64 mips64el mipsel 
powerpc powerpcspe ppc64 ppc64el sh4],
  libxmuu-dev (>= 1:0.99.1),
  libxext-dev (>= 1:0.99.1),
--- End Message ---
--- Begin Message ---
On 30.12.2019 0.47, Samuel Thibault wrote:
> Source: xorg-server
> Version: 2:1.20.6-1
> Severity: serious
> Tags: patch
> Justification: FTBFS
> 
> Hello,
> 
> Probably since the upload of the newer mesa, xorg-server now FTBFS,
> because it misses dri.pc and x11-xcb.pc. The attached patch fixes this.

I messed up the upload of 1.20.7-1, but -2 is in the archive now and
fixes this.

-- 
t--- End Message ---

Bug#948393: marked as done (foxtrotgps: fails to connect to gpsd despite SUCCESS message)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 06:34:14 +
with message-id 
and subject line Bug#948393: fixed in foxtrotgps 1.2.2-2
has caused the Debian Bug report #948393,
regarding foxtrotgps: fails to connect to gpsd despite SUCCESS message
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.)


-- 
948393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: foxtrotgps
Version: 1.2.2-1+b1
Severity: important

Dear Maintainer,

Foxtrotgps fails to connect to gpsd, but other clients work. Console prints: 
'connection to gpsd SUCCEEDED' but gps data is dever displayed. A build of 
1.2.2 from source works fine. I suspect the build got out of step with libgps. 
See also #948388.

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

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

Versions of packages foxtrotgps depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-2
ii  libatk1.0-0  2.34.1-1
ii  libbluetooth35.50-1+b1
ii  libc62.29-8
ii  libcurl3-gnutls  7.67.0-2
ii  libexif120.6.21-5.1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-2
ii  libglade2-0  1:2.6.4-2+b1
ii  libglib2.0-0 2.62.4-1
ii  libgps25 3.20-1
ii  libgtk2.0-0  2.24.32-4
ii  libpango-1.0-0   1.42.4-8
ii  libsqlite3-0 3.30.1+fossil191229-1
ii  libxml2  2.9.4+dfsg1-8

Versions of packages foxtrotgps recommends:
ii  gpsd  3.20-1

Versions of packages foxtrotgps suggests:
pn  gpsbabel
ii  python3 3.7.5-3
ii  python3-bs4 4.8.2-1
pn  python3-feedparser  
ii  python3-sqlalchemy  1.3.12+ds1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: foxtrotgps
Source-Version: 1.2.2-2

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

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

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated foxtrotgps 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, 15 Jan 2020 14:11:29 +0800
Source: foxtrotgps
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Paul Wise 
Changed-By: Paul Wise 
Closes: 948393
Changes:
 foxtrotgps (1.2.2-2) unstable; urgency=medium
 .
   [ Paul Wise ]
   * Add patch to fix build failure with gpsd 3.20 (Closes: #948393)
 .
   [ lintian-brush ]
   * Update standards version to 4.4.1, no changes needed.
   * Use full URL to Launchpad in upstream Repository metadata field
Checksums-Sha1:
 e51e131d09adf3badb993d3928a37bdfdc85cdbe 2170 foxtrotgps_1.2.2-2.dsc
 81ce8199076acf4c4587f1a49d184345ea1468a5 17664 foxtrotgps_1.2.2-2.debian.tar.xz
Checksums-Sha256:
 f53b87acd206bba0237a91f98c4aaf7c5f25d6e108cc1fa2146d5aa3716ecdf6 2170 
foxtrotgps_1.2.2-2.dsc
 7bc14ed3a2fb3985bc97d03f8a18a29e68b83f94f9d7edbfb3a017610c9ad2dc 17664 
foxtrotgps_1.2.2-2.debian.tar.xz
Files:
 2bdc3ad4e02f42af5fefec8a70db027d 2170 comm optional foxtrotgps_1.2.2-2.dsc
 f032814decdba92b5ffdfaa9aa490c8b 17664 comm optional 
foxtrotgps_1.2.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAl4erk0ACgkQMRa6Xp/6
aaMszxAAlzuvrLLklJmzgDsZ4iEujS5tYyU60WwOJi2LOWbjWH2NCSBv25p8FjWz

Bug#946624: marked as done (python-scipy: autopkgtest regularly times out)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 06:12:56 +
with message-id 
and subject line Bug#948946: Removed package(s) from unstable
has caused the Debian Bug report #946624,
regarding python-scipy: autopkgtest regularly times out
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.)


-- 
946624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-scipy
Version: 1.2.2-7
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout flaky

Dear maintainers,

Your package has an autopkgtest, great. However, I noticed that it
regularly fails without very clear changes. On top of that, very
recently your package started to time out regularly on ci.debian.net,
sometimes taking as long as 10 hours before doing so.

Can you please investigate the situation? Don't hesitate to ask for help
from the Debian CI team (in X-Debbugs-CC) if you need help solving this
issue.

To avoid wasting lots of time on the ci.debian.net infrastructure (the
test is trigger for quite some reverse dependencies), I have blacklisted
your package. If needed, please ping me to try any uploads you make that
should fix the issue if you are unsure and don't want to close this bug
until verified.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-scipy/3586494/log.gz

autopkgtest [00:44:10]:  summary
python2  FAIL timed out
python3  FAIL timed out
python2-smokePASS
python3-smokePASS
openblas FAIL timed out
atlasFAIL non-zero exit status 143



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.2.2-11+rm

Dear submitter,

as the package python-scipy has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 06:12:56 +
with message-id 
and subject line Bug#948946: Removed package(s) from unstable
has caused the Debian Bug report #938157,
regarding python-scipy: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-scipy

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

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

Dear submitter,

as the package python-scipy has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#948937: marked as done (gr-fcdproplus FTBFS missing build-dependencies on dh-python and liborc-0.4-dev)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 05:34:17 +
with message-id 
and subject line Bug#948937: fixed in gr-fcdproplus 3.8~20190817-3
has caused the Debian Bug report #948937,
regarding gr-fcdproplus FTBFS missing build-dependencies on dh-python and 
liborc-0.4-dev
to be marked as done.

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

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


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

Package: gr-fcdproplus
Version: 3.8~20190817-2
Severity: serious
Tags: patch.

gr-fcdproplus fails to build due to a missing dh-python, I initially noticed 
this on a raspbian autobuilder, but it's also happening on the reproducible 
builds site, so it's not raspbian specific.


dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/arm-linux-gnueabihf/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/arm-linux-gnueabihf/perl5/5.30 /usr/share/perl5 
/usr/lib/arm-linux-gnueabihf/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at (eval 16) 
line 1.
BEGIN failed--compilation aborted at (eval 16) line 1.

The fix for that was easy, just add the build-dependency on dh-python.

However when I tried to build it with the build-dependency added I got another 
build failure.


[ 47%] Built target doxygen_target
make[3]: *** No rule to make target 
'/usr/lib/arm-linux-gnueabihf/liborc-0.4.so', needed by 
'lib/libgnuradio-fcdproplus.so.3.8.0.0'.  Stop.
make[3]: *** Waiting for unfinished jobs


Again this was a missing build-dependency, this time on liborc-0.4-dev

After adding the build-dependencies on dh-python and liborc-0.4-dev I was able 
to get a succesful build. However my build environment was not clean, so it is 
possible that there were other missing build-dependencies I missed.

--- End Message ---
--- Begin Message ---
Source: gr-fcdproplus
Source-Version: 3.8~20190817-3

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

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

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-fcdproplus 
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, 15 Jan 2020 00:06:08 -0500
Source: gr-fcdproplus
Architecture: source
Version: 3.8~20190817-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: A. Maitland Bottoms 
Closes: 948937
Changes:
 gr-fcdproplus (3.8~20190817-3) unstable; urgency=medium
 .
   * depend upon dh-python since python3-dev no longer does
   * also add depends on liborc-0.4-dev (Closes: #948937)
 thanks peter!
Checksums-Sha1:
 cb59ff607a12f4fb75dd35105a1705fd7e2e7726 2516 gr-fcdproplus_3.8~20190817-3.dsc
 826b623a44dc5ba98baadbfc0f31685f80aca8a5 191928 
gr-fcdproplus_3.8~20190817-3.debian.tar.xz
 230ae0a112cd08c69f2d49d42f57a5a180961dc7 19018 
gr-fcdproplus_3.8~20190817-3_amd64.buildinfo
Checksums-Sha256:
 c3f750980cbb0c6b18c759f8382daa43cc886bf01315c5a729297a7200380ff2 2516 
gr-fcdproplus_3.8~20190817-3.dsc
 669cf3117a2b179a875d094e3f30e6c9eedda03b92ffc57b780b8c1936201780 191928 
gr-fcdproplus_3.8~20190817-3.debian.tar.xz
 5a7fec9326c3bea136d83f290f582af2530d6793ac7d502e5e17a1900a25de87 19018 
gr-fcdproplus_3.8~20190817-3_amd64.buildinfo
Files:
 ba20e4461b3ff2f6116faa9587e4a3fe 2516 hamradio optional 
gr-fcdproplus_3.8~20190817-3.dsc
 b623d96a83c0eb26760d188461a1beed 191928 hamradio optional 
gr-fcdproplus_3.8~20190817-3.debian.tar.xz
 aa22a4d1bde0974326d20b32aa69df8e 19018 hamradio optional 
gr-fcdproplus_3.8~20190817-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl4en7wACgkQUEHxiR9E
4JAhhQ/+Nw0Se8/60XDZ5My/VVLQXn/P2nOcmpTbeScDBCEHwRFiqjAGalLOUN3J
1SNYmXa0vcoWHzobQauGhdWDIhh6t5BIP1pNhIzNcCbf9aWhuKA1ZDYlaVD4FRu1
t56b+oW7kM7swr6soKeJ3aJgXbk1AyN9vBkRo+4mdEVo6fxYdKxt3POmvDoflCbI
SUGpICn6Qrjl7fi/umdr9BV05RDlcrAUYpxG+iUr8rg097qJ70zfPjEDwhdI9/n+

Bug#948828: marked as done (python-whoosh ftbfs in unstable)

[Danny Griffin]

On Mon, Jan 13, 2020, 3:42 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Mon, 13 Jan 2020 15:39:25 -0500
> with message-id  ffovz...@mail.gmail.com>
> and subject line Re: [Python-modules-team] Bug#948828: python-whoosh ftbfs
> in unstable
> has caused the Debian Bug report #948828,
> regarding python-whoosh ftbfs in unstable
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
>
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
>
>
> --
> 948828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948828
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Mon, 13 Jan 2020 21:03:46 +0100
> Subject: python-whoosh ftbfs in unstable
> Package: src:python-whoosh
> Version: 2.7.4+git6-g9134ad92-4
> Severity: serious
> Tags: sid bullseye
>
> python-whoosh ftbfs in unstable:
>
> [...]
> The HTML pages are in docs/build/html.
> make[1]: Leaving directory
> '/<>/python-whoosh-2.7.4+git6-g9134ad92'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd
>
> /<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
> python2.7 -m pytest tests
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
> exec code in run_globals
>   File "/usr/lib/python2.7/dist-packages/pytest.py", line 102, in 
> raise SystemExit(pytest.main())
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line
> 63,
> in main
> config = _prepareconfig(args, plugins)
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line
> 207,
> in _prepareconfig
> pluginmanager=pluginmanager, args=args
>   File "/usr/lib/python2.7/dist-packages/pluggy/hooks.py", line 286, in
> __call__
> return self._hookexec(self, self.get_hookimpls(), kwargs)
>   File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 92, in
> _hookexec
> return self._inner_hookexec(hook, methods, kwargs)
>   File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 86, in
> 
> firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 203, in
> _multicall
> gen.send(outcome)
>   File "/usr/lib/python2.7/dist-packages/_pytest/helpconfig.py", line 94,
> in
> pytest_cmdline_parse
> config = outcome.get_result()
>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 81, in
> get_result
> _reraise(*ex)  # noqa
>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 187, in
> _multicall
> res = hook_impl.function(*args)
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line
> 687,
> in pytest_cmdline_parse
> self.parse(args)
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line
> 895,
> in parse
> self._preparse(args, addopts=addopts)
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line
> 829,
> in _preparse
> self._initini(args)
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line
> 760,
> in _initini
> config=self,
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py",
> line 127,
> in determine_setup
> rootdir, inifile, inicfg = getcfg([ancestor], config=config)
>   File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py",
> line 51,
> in getcfg
> pytrace=False,
>   File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 119,
> in fail
> raise Failed(msg=msg, pytrace=pytrace)
> builtins.Failed: [pytest] section in setup.cfg files is no longer
> supported,
> change to [tool:pytest] instead.
> E: pybuild pybuild:342: test: plugin distutils failed with: exit code=1: cd
>
> /<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
> python2.7 -m pytest tests
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7
> returned
> exit code 13
> make: *** [debian/rules:5: build] Error 255
>
>
>
> -- Forwarded message --
> From: Sandro Tosi 
> To: Matthias Klose , 948828-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 13 Jan 2020 15:39:25 -0500
> Subject: Re: [Python-modules-team] Bug#948828: python-whoosh ftbfs in
> unstable
> Version: 2.7.4+git6-g9134ad92-5
>
> On Mon, Jan 13, 2020 at 3:06 PM Matthias Klose  wrote:
> >
> > Package: src:python-whoosh
> > Version: 2.7.4+git6-g9134ad92-4
> > Severity: 

Bug#948938: marked as done (gr-iqbal FTBFS missing build-dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 05:04:11 +
with message-id 
and subject line Bug#948938: fixed in gr-iqbal 0.38-4
has caused the Debian Bug report #948938,
regarding gr-iqbal FTBFS missing build-dependency on dh-python
to be marked as done.

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

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


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

Package: gr-iqbal
Version: 0.38-3
Severity: serious
Tags: patch

gr-rds FTBFS due to a missing build-dependency on dh-python,


dh clean --with python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/arm-linux-gnueabihf/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/arm-linux-gnueabihf/perl5/5.30 /usr/share/perl5 
/usr/lib/arm-linux-gnueabihf/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at (eval 16) 
line 1.
BEGIN failed--compilation aborted at (eval 16) line 1.


I initially noticed this on a raspbian autobuilder, but it is also happening on 
the reproducible builds site, so it's not raspbian specific.

The fix is a simple matter of adding the build-depedency.
--- End Message ---
--- Begin Message ---
Source: gr-iqbal
Source-Version: 0.38-4

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

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

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-iqbal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2020 23:26:33 -0500
Source: gr-iqbal
Architecture: source
Version: 0.38-4
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 948938
Changes:
 gr-iqbal (0.38-4) unstable; urgency=medium
 .
   * depend upon dh-python since python3-dev no longer does (Closes: #948938)
 thanks peter!
   * also add depends on liborc-0.4-dev
Checksums-Sha1:
 ebd71e47eb7b55c3cbf2029e188bdb4fc765d805 2500 gr-iqbal_0.38-4.dsc
 4dc28cc45fe630bbcbbf18d7c2e0aa0a4cbb193d 14152 gr-iqbal_0.38-4.debian.tar.xz
 f552e9a4d4e510b9f61da44a3c4996aad1ac5aea 18386 gr-iqbal_0.38-4_amd64.buildinfo
Checksums-Sha256:
 60878646eb534f95ee3b837945cb47879a2660862b4293f43741e1f007b88e47 2500 
gr-iqbal_0.38-4.dsc
 573efd720a9aaf472d8faa6da82158eb9ffadcc65fdc194c4fc260446fe29980 14152 
gr-iqbal_0.38-4.debian.tar.xz
 6e1170e8f1fe4f44f5e67dcb2bedbf46cb91a5920e7f5e4c4e6572a5315cc4bb 18386 
gr-iqbal_0.38-4_amd64.buildinfo
Files:
 f25d4a038ada993e2cad6b1ef9365089 2500 libs optional gr-iqbal_0.38-4.dsc
 9a2aedeef38d42905815f7fe5c098209 14152 libs optional 
gr-iqbal_0.38-4.debian.tar.xz
 50041e0abc6988f7567b3b949ae00772 18386 libs optional 
gr-iqbal_0.38-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl4emOwACgkQUEHxiR9E
4JAnfBAAqlbu59Rf5Pb7rKsP9F2gKfAIDg7fTGqWkuMqFyxewOyekWRvjQ2W5KvU
4ecJ6foBeW4jBIIWgZJsY26Aspb+nYuDi1r8fdtsXqzDRWVRyCjRTi67Z9HkEd9U
FH+MuHZQU9iaYK9KRoOTC/9k1HaOB0RHAzKvBnl7WxSN6XEPGo17lwr5A5E9+eyS
btEhVvc8/2aYXnLKi272sPtB1U2hfh6u3eOuWnlsAuplXqMYEzovMW2HgYI/SRq7
EnXmcgxz0KAafGiZx5s0mV0WjjsN+STTB0CXJcIkBWilSTPPjVjthhiLruWPAmsV
7atZQAsGLmoFywnyfnNHH/PI0Gdo3pkgalkT8p5bt6Lv/I03/f6uN0xN92S8so5l
b8xFoNLXobuWFFJEqFsZ+QZN+Z8vuSE0FtdM4/+MI1+yWQLN6xNyLhjpvDKCmAzu
lYR6qSVv5FRW34T5hXFfGWUOcHlJU2qJC6LdjxpVdvHS6dtsX4Wl6KISJTE3GMRF
R8BROLmjUAGknJzcjYw9oTXQSIYN/0SOdel/RrIl8nkTjwNp4pKjOipQWChpwlem
wPBXEnyH2LczR+T4oo27TGGTTkILrx3iR5fBxWn+7CbKPWLHbtaQNApE2AstVRFO
7bChNwRuwaOHa/qABKkM/lvcGuaZofcqJbgcsfVXhAZF9Jx4Wfo=
=GOHV
-END PGP SIGNATURE End Message ---

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> # Reassign and forcemerge to properly
> # deal with this false XCA FTBFS bug.
> # These commands written at the suggestion of
> # the #debian-devel IRC channel.
> reassign 947328 debhelper 12.7.1
Bug #947328 {Done: Thomas Ward } [src:xca] FTBFS: 
dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or 
directory
Bug reassigned from package 'src:xca' to 'debhelper'.
No longer marked as found in versions xca/2.1.2-2.
No longer marked as fixed in versions debhelper/12.7.2.
Bug #947328 {Done: Thomas Ward } [debhelper] FTBFS: 
dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or 
directory
Marked as found in versions debhelper/12.7.1.
> forcemerge 947328 943705
Bug #947328 {Done: Thomas Ward } [debhelper] FTBFS: 
dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or 
directory
Bug #947328 {Done: Thomas Ward } [debhelper] FTBFS: 
dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or 
directory
Marked as fixed in versions debhelper/12.7.2.
Bug #943705 {Done: Niels Thykier } [debhelper] 
dh_installman: man-recode integration gets confused if both foo.1 and foo.1.gz 
exist
Failed to forcibly merge 947328: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

>
End of message, stopping processing here.

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

Bug#938157: [Python-modules-team] Bug#938157: python-scipy: Python2 removal in sid/bullseye

[Sandro Tosi]

On Mon, Jan 13, 2020 at 9:08 PM Drew Parsons  wrote:
>
> On 2020-01-14 02:13, Sandro Tosi wrote:
> >> >It's just that there is no extra effort required in this case.
> >> >python3-scipy does indeed need the effort taken, but once that effort
> >> >is
> >> >done, it's no more effort to apply the same fix to python-scipy.  So
> >> >yes, please do focus on fixing python3-scipy! :)
> >>
> >> Yes, maybe so, but delaying the python2-rm blocks other work and thus
> >> delays and complicates getting that major effort completed.  Let's
> >> not.
> >
> > exactly, i really dont understand what's the value of fixing something
> > that's gonna be removed anyway.
> >
> > I think i'm just gonna wait a couple more days and then file a RM
>
> Fair enough then.  I'm out-voted :)

i pulled the trigger and opened #948946 :)

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

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

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 03:34:51 +
with message-id 
and subject line Bug#937580: fixed in python-argcomplete 1.8.1-1.1
has caused the Debian Bug report #937580,
regarding python-argcomplete: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-argcomplete

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

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

We believe that the bug you reported is fixed in the latest version of
python-argcomplete, 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 python-argcomplete package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2020 16:48:14 -0500
Source: python-argcomplete
Architecture: source
Version: 1.8.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini 
Changed-By: Sandro Tosi 
Closes: 937580
Changes:
 python-argcomplete (1.8.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937580
Checksums-Sha1:
 164c2c0757460ba7e9b62d6bc77ea94955110f03 2052 python-argcomplete_1.8.1-1.1.dsc
 c8877be2b5a7b148532d636ee39027d8143e5ead 7036 
python-argcomplete_1.8.1-1.1.debian.tar.xz
 23caec92dc4a9eb70626d91c41587934a8e4fd88 6684 
python-argcomplete_1.8.1-1.1_source.buildinfo
Checksums-Sha256:
 c48210f3ca759ec1aea9337e8d37b31dc75baed760486ad6d4c1d628109f12ca 2052 
python-argcomplete_1.8.1-1.1.dsc
 6dde5ad8a872abd2245ca12b5a03cf214777da58bd134bac40299177f4b052ec 7036 
python-argcomplete_1.8.1-1.1.debian.tar.xz
 

Processed: py2removal bugs severity updates - 2020-01-15 03:36:05.154125+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # mgltools-mglutil is an application, has low popcon (24 < 300), and has 0 
> external rdeps or not in testing
> severity 937025 serious
Bug #937025 [src:mgltools-mglutil] mgltools-mglutil: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # mgltools-molkit is an application, has low popcon (15 < 300), and has 0 
> external rdeps or not in testing
> severity 937026 serious
Bug #937026 [src:mgltools-molkit] mgltools-molkit: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # mgltools-networkeditor is an application, has low popcon (9 < 300), and has 
> 0 external rdeps or not in testing
> severity 937027 serious
Bug #937027 [src:mgltools-networkeditor] mgltools-networkeditor: Python2 
removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # mgltools-support is an application, has low popcon (15 < 300), and has 0 
> external rdeps or not in testing
> severity 937035 serious
Bug #937035 [src:mgltools-support] mgltools-support: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # python-simpy is a module and has 0 external rdeps or not in testing
> # python-simpy-gui is a module and has 0 external rdeps or not in testing
> severity 938174 serious
Bug #938174 [src:python-simpy] python-simpy: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: retitle 849087 to gourmet: Port to Python 3 and python3-gst-1.0

[Debian Bug Tracking System]

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

> retitle 849087 gourmet: Port to Python 3 and python3-gst-1.0
Bug #849087 [src:gourmet] Port to Python 3 and python3-gst-1.0
Bug #936641 [src:gourmet] gourmet: Python2 removal in sid/bullseye
Changed Bug title to 'gourmet: Port to Python 3 and python3-gst-1.0' from 'Port 
to Python 3 and python3-gst-1.0'.
Changed Bug title to 'gourmet: Port to Python 3 and python3-gst-1.0' from 
'gourmet: Python2 removal in sid/bullseye'.
> thanks
Stopping processing here.

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

Bug#937580: python-argcomplete: diff for NMU version 1.8.1-1.1

[Sandro Tosi]

Control: tags 937580 + patch


Dear maintainer,

I've prepared an NMU for python-argcomplete (versioned as 1.8.1-1.1). The diff
is attached to this message.

Please consider maintaining this package with DPMT

Regards.

diff -Nru python-argcomplete-1.8.1/debian/changelog python-argcomplete-1.8.1/debian/changelog
--- python-argcomplete-1.8.1/debian/changelog	2017-01-24 12:05:43.0 -0500
+++ python-argcomplete-1.8.1/debian/changelog	2020-01-14 16:48:14.0 -0500
@@ -1,3 +1,10 @@
+python-argcomplete (1.8.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937580
+
+ -- Sandro Tosi   Tue, 14 Jan 2020 16:48:14 -0500
+
 python-argcomplete (1.8.1-1) unstable; urgency=medium
 
   * Fix Vcs-Git URL in debian/control
diff -Nru python-argcomplete-1.8.1/debian/control python-argcomplete-1.8.1/debian/control
--- python-argcomplete-1.8.1/debian/control	2017-01-24 12:05:43.0 -0500
+++ python-argcomplete-1.8.1/debian/control	2020-01-14 16:47:49.0 -0500
@@ -2,34 +2,12 @@
 Maintainer: Marco Nenciarini 
 Section: python
 Priority: optional
-Build-Depends: python-setuptools (>= 0.6b3), python-all, debhelper (>= 10),
+Build-Depends: debhelper (>= 10),
  dh-python, python3-all, python3-setuptools, tcsh,
- python-wheel, python-pexpect, python-coverage, python-flake8,
  python3-wheel, python3-pexpect, python3-coverage, python3-flake8
 Standards-Version: 3.9.8.0
 Vcs-Git: https://alioth.debian.org/anonscm/git/collab-maint/python-argcomplete.git
 Vcs-Browser: https://anonscm.debian.org/gitweb/?p=collab-maint/python-argcomplete.git
-X-Python-Version: >= 2.6
-X-Python3-Version: >= 3.2
-
-Package: python-argcomplete
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
-Description: bash tab completion for argparse
- Argcomplete provides easy, extensible command line tab completion of
- arguments for your Python script.
- .
- It makes two assumptions:
- .
-  * You're using bash as your shell
-  * You're using argparse to manage your command line arguments/options
- .
- Argcomplete is particularly useful if your program has lots of
- options or subparsers, and if your program can dynamically suggest
- completions for your argument/option values (for example, if the user
- is browsing resources over the network).
- .
- This package provides the module for Python 2.x.
 
 Package: python3-argcomplete
 Architecture: all
diff -Nru python-argcomplete-1.8.1/debian/patches/py3k-scripts.patch python-argcomplete-1.8.1/debian/patches/py3k-scripts.patch
--- python-argcomplete-1.8.1/debian/patches/py3k-scripts.patch	1969-12-31 19:00:00.0 -0500
+++ python-argcomplete-1.8.1/debian/patches/py3k-scripts.patch	2020-01-14 16:48:14.0 -0500
@@ -0,0 +1,24 @@
+--- a/scripts/activate-global-python-argcomplete
 b/scripts/activate-global-python-argcomplete
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # PYTHON_ARGCOMPLETE_OK
+ 
+ # Copyright 2012-2013, Andrey Kislyuk and argcomplete contributors.
+--- a/scripts/python-argcomplete-check-easy-install-script
 b/scripts/python-argcomplete-check-easy-install-script
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ 
+ # Copyright 2012-2013, Andrey Kislyuk and argcomplete contributors.
+ # Licensed under the Apache License. See https://github.com/kislyuk/argcomplete for more info.
+--- a/scripts/register-python-argcomplete
 b/scripts/register-python-argcomplete
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # PYTHON_ARGCOMPLETE_OK
+ 
+ # Copyright 2012-2013, Andrey Kislyuk and argcomplete contributors.
diff -Nru python-argcomplete-1.8.1/debian/patches/py3k-tests.patch python-argcomplete-1.8.1/debian/patches/py3k-tests.patch
--- python-argcomplete-1.8.1/debian/patches/py3k-tests.patch	1969-12-31 19:00:00.0 -0500
+++ python-argcomplete-1.8.1/debian/patches/py3k-tests.patch	2020-01-14 16:48:14.0 -0500
@@ -0,0 +1,39 @@
+--- a/test/prog
 b/test/prog
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # PYTHON_ARGCOMPLETE_OK
+ """Test script used by test.TestBash."""
+ import argparse
+--- a/test/test.py
 b/test/test.py
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # -*- coding: utf-8 -*-
+ 
+ from __future__ import absolute_import, division, print_function, unicode_literals
+@@ -1024,11 +1024,11 @@ class TestBashGlobal(TestBash):
+ 
+ def test_python_completion(self):
+ self.sh.run_command('cd ' + TEST_DIR)
+-self.assertEqual(self.sh.run_command('python ./prog basic f\t'), 'foo\r\n')
++self.assertEqual(self.sh.run_command('python3 ./prog basic f\t'), 'foo\r\n')
+ 
+ def test_python_filename_completion(self):
+ self.sh.run_command('cd ' + TEST_DIR)
+-self.assertEqual(self.sh.run_command('python ./pro\tbasic f\t'), 'foo\r\n')
++self.assertEqual(self.sh.run_command('python3 ./pro\tbasic f\t'), 'foo\r\n')
+ 
+ def 

Processed: python-argcomplete: diff for NMU version 1.8.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 937580 + patch
Bug #937580 [src:python-argcomplete] python-argcomplete: Python2 removal in 
sid/bullseye
Added tag(s) patch.

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

Processed: tagging 948393

[Debian Bug Tracking System]

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

> # not an optimal patch
> tags 948393 - patch
Bug #948393 [foxtrotgps] foxtrotgps: fails to connect to gpsd despite SUCCESS 
message
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#948942: pglogical: FTBFS: mismatch with the default postgres

[Mattia Rizzolo]

Source: pglogical
Version: 2.2.2-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid/amd64 chroot.
Attached is the full build log, hopefully relevant excerpt follows:

dpkg-buildpackage: info: source package pglogical
dpkg-buildpackage: info: source version 2.2.2-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael Banck 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control  2019-08-05 03:16:36.0 -1200
+++ debian/control.MbbcD5   2021-02-13 05:49:21.180202588 -1200
@@ -12,9 +12,9 @@
 Vcs-Git: https://salsa.debian.org/postgresql/pglogical.git
 Homepage: https://www.2ndquadrant.com/en/resources/pglogical/ 
 
-Package: postgresql-11-pglogical
+Package: postgresql-12-pglogical
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-11
+Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-12
 Suggests:
 Description: Logical Replication Extension for PostgreSQL
  The pglogical extension provides logical streaming replication between
@@ -27,4 +27,3 @@
  several databases into a Data Warehouse, It utilises the Logical Decoding
  features available since PostgreSQL 9.4 working with low overhead on both
  provider and subscriber.
-
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9: 
debian/control] Error 1
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Wed Jan 15 00:53:48 UTC 2020
I: pbuilder-time-stamp: 1579049628
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/pglogical_2.2.2-1.dsc]
I: copying [pkgs/pglogical_2.2.2.orig.tar.gz]
I: copying [pkgs/pglogical_2.2.2-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Mon Aug  5 17:12:14 2019 UTC
gpgv:using RSA key 9CA877749FAB2E4FA96862ECDC686A27B43481B0
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./pglogical_2.2.2-1.dsc
dpkg-source: info: extracting pglogical in pglogical-2.2.2
dpkg-source: info: unpacking pglogical_2.2.2.orig.tar.gz
dpkg-source: info: unpacking pglogical_2.2.2-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying pglogical_create_subscriber_set_port.patch
dpkg-source: info: applying adapt_tap_tests.patch
dpkg-source: info: applying test_socketdir.patch
dpkg-source: info: applying v94_tap_support.patch
dpkg-source: info: applying test_increase_timeouts.patch
dpkg-source: info: applying test_configuration.patch
dpkg-source: info: applying pglogical_dump.patch
dpkg-source: info: applying post-2.2.2.patch
dpkg-source: info: applying alternative_regression_outputs.patch
I: using fakeroot in build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/pglogical_2.2.2-1.dsc' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev binfmt-support bsdmainutils
  clang-9 comerr-dev debhelper dh-autoreconf dh-strip-nondeterminism dwz file
  gcc-8-base gettext gettext-base groff-base intltool-debian krb5-multidev
  lib32gcc1 lib32stdc++6 libarchive-zip-perl libbsd-dev libbsd0 libc6-i386
  libclang-common-9-dev libclang-cpp9 libcroco3 libdebhelper-perl libedit-dev
  libedit2 libelf1 libffi-dev libfile-stripnondeterminism-perl libgc1c2
  libgcc-8-dev libglib2.0-0 libgssapi-krb5-2 libgssrpc4 libk5crypto3
  libkadm5clnt-mit11 libkadm5srv-mit11 libkdb5-9 libkeyutils1 libkrb5-3
  libkrb5support0 libldap-2.4-2 libldap-common libllvm9 libmagic-mgc libmagic1
  libmpdec2 libmpx2 libncurses-dev libncurses6 libobjc-8-dev libobjc4
  libpam0g-dev libpcre2-16-0 libpcre2-32-0 libpcre2-dev libpcre2-posix2
  libpfm4 libpipeline1 libpq-dev libpq5 libprocps7 libpython3-stdlib
  libpython3.7-minimal libpython3.7-stdlib libsasl2-2 libsasl2-modules-db
  libselinux1-dev libsepol1-dev libsigsegv2 libssl-dev libstdc++-8-dev
  libsub-override-perl libtinfo-dev libtool libuchardet0 

Bug#948943: php-solr: FTBFS: all tests fail

[Mattia Rizzolo]

Source: php-solr
Version: 2.5.0-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid/amd64 chroot.
Attached is the full build log, hopefully relevant excerpt follows:


=
TIME END 2020-01-15 01:40:44

=
TEST RESULT SUMMARY
-
Exts skipped:0
Exts tested :   15
-

Number of tests :  151   151
Tests skipped   :0 (  0.0%) 
Tests warned:0 (  0.0%) (  0.0%)
Tests failed:  151 (100.0%) (100.0%)
Expected fail   :0 (  0.0%) (  0.0%)
Tests passed:0 (  0.0%) (  0.0%)
-
Time taken  :3 seconds
=


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Wed Jan 15 01:40:02 UTC 2020
I: pbuilder-time-stamp: 1579052402
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/php-solr_2.5.0-1.dsc]
I: copying [pkgs/php-solr_2.5.0.orig.tar.gz]
I: copying [pkgs/php-solr_2.5.0-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Thu Aug  8 07:09:18 2019 UTC
gpgv:using RSA key 30B933D80FCE3D981A2D38FB0C99B70EF4FCBB07
gpgv:issuer "ond...@sury.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./php-solr_2.5.0-1.dsc
dpkg-source: info: extracting php-solr in php-solr-2.5.0
dpkg-source: info: unpacking php-solr_2.5.0.orig.tar.gz
dpkg-source: info: unpacking php-solr_2.5.0-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-Remove-extra-check-for-curl-headers.patch
I: using fakeroot in build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/php-solr_2.5.0-1.dsc' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev bsdmainutils chrpath debhelper
  dh-autoreconf dh-php dh-strip-nondeterminism dwz file gettext gettext-base
  groff-base intltool-debian libarchive-zip-perl libargon2-1 libbrotli1
  libbsd0 libcroco3 libcurl4 libcurl4-openssl-dev libdebhelper-perl libedit2
  libelf1 libexporter-tiny-perl libfile-stripnondeterminism-perl libglib2.0-0
  libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0
  libldap-2.4-2 libldap-common liblist-moreutils-perl libmagic-mgc libmagic1
  libnghttp2-14 libpcre2-16-0 libpcre2-32-0 libpcre2-dev libpcre2-posix2
  libpipeline1 libpsl5 librtmp1 libsasl2-2 libsasl2-modules-db libsigsegv2
  libsodium23 libssh2-1 libssl-dev libsub-override-perl libtool libuchardet0
  m4 man-db php-all-dev php-common php7.3-cli php7.3-common php7.3-dev
  php7.3-json php7.3-opcache php7.3-readline po-debconf psmisc sensible-utils
  shtool ucf xml2
debconf: delaying package configuration, since apt-utils is not installed
0 upgraded, 72 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/19.8 MB of archives.
After this operation, 75.9 MB of additional disk space will be used.
Selecting previously unselected package libbsd0:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 13530 files and directories currently installed.)
Preparing to unpack .../00-libbsd0_0.10.0-1_amd64.deb ...
Unpacking libbsd0:amd64 (0.10.0-1) ...
Selecting previously unselected package bsdmainutils.
Preparing to unpack .../01-bsdmainutils_11.1.2+b1_amd64.deb ...
Unpacking bsdmainutils (11.1.2+b1) ...
Selecting previously unselected package libuchardet0:amd64.
Preparing to unpack 

Processed: tagging 948917 ..., found 948914 in 0~1.0-2 ..., tagging 948914 ..., tagging 948876, tagging 948859 ...

[Debian Bug Tracking System]

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

> tags 948917 + sid bullseye
Bug #948917 [src:screengrab] FTBFS: No rule to make target 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.so'
Added tag(s) sid and bullseye.
> retitle 948917 screengrab: FTBFS: No rule to make target 
> '/usr/lib/x86_64-linux-gnu/libglib-2.0.so'
Bug #948917 [src:screengrab] FTBFS: No rule to make target 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.so'
Changed Bug title to 'screengrab: FTBFS: No rule to make target 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.so'' from 'FTBFS: No rule to make target 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.so''.
> found 948914 0~1.0-2
Bug #948914 [src:qmath3d] FTBFS: The qmake executable '/usr/bin/qmake' failed 
with exit code 1.
Marked as found in versions qmath3d/0~1.0-2.
> retitle 948914 qmath3d: FTBFS: The qmake executable '/usr/bin/qmake' failed 
> with exit code 1.
Bug #948914 [src:qmath3d] FTBFS: The qmake executable '/usr/bin/qmake' failed 
with exit code 1.
Changed Bug title to 'qmath3d: FTBFS: The qmake executable '/usr/bin/qmake' 
failed with exit code 1.' from 'FTBFS: The qmake executable '/usr/bin/qmake' 
failed with exit code 1.'.
> tags 948914 + sid bullseye
Bug #948914 [src:qmath3d] qmath3d: FTBFS: The qmake executable '/usr/bin/qmake' 
failed with exit code 1.
Added tag(s) sid and bullseye.
> retitle 948912 regina-normal: FTBFS: can not find boost >= 1.55
Bug #948912 [src:regina-normal] FTBFS: can not find boost >= 1.55
Changed Bug title to 'regina-normal: FTBFS: can not find boost >= 1.55' from 
'FTBFS: can not find boost >= 1.55'.
> tags 948876 + sid bullseye
Bug #948876 [src:kodi] kodi: FTBFS: something segfaults
Added tag(s) sid and bullseye.
> tags 948859 + sid bullseye
Bug #948859 [src:coccinelle] coccinelle: Package is uninstallable
Added tag(s) sid and bullseye.
> retitle 948897 openbios: FTBFS: error: taking address of packed member of 
> 'struct ' may result in an unaligned pointer value
Bug #948897 [src:openbios] Subject: openbios: FTBFS: error: taking address of 
packed member of 'struct ' may result in an unaligned pointer value
Changed Bug title to 'openbios: FTBFS: error: taking address of packed member 
of 'struct ' may result in an unaligned pointer value' from 
'Subject: openbios: FTBFS: error: taking address of packed member of 'struct 
' may result in an unaligned pointer value'.
> tags 948897 + sid bullseye
Bug #948897 [src:openbios] openbios: FTBFS: error: taking address of packed 
member of 'struct ' may result in an unaligned pointer value
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

[dirdi]

Package: initramfs-tools
Version: 0.135
Followup-For: Bug #948257

Just want to confirm Pierrick's observation that rolling back kmod and
libkmod2 to version 26-3 fixes the logspam.

Bug#948940: FTBFS: /plugins/owncloud-ui/owncloud.cpp:54:23: error: invalid use of incomplete type ‘class QWindow’

[Lisandro Damián Nicanor Pérez Meyer]

Source: kaccounts-providers
Version: 4:17.08.3-1
Severity: serious
Tags: ftbfs
Justification: FTBFS on all archs

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

/plugins/owncloud-ui/owncloud.cpp:54:23: error: invalid use of incomplete type 
‘class QWindow’

The build logs can be found here:



Kinds regards, Lisandro.

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

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

-- no debconf information

Bug#948939: FTBFS: rkward/windows/rkworkplace.cpp:71:2: error: ‘QVBoxLayout’ was not declared in this scope

[Lisandro Damián Nicanor Pérez Meyer]

Source: rkward
Version: 0.7.0b-1.1
Severity: serious
Tags: ftbfs
Justification: FTBFS on all archs

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

/<>/rkward/windows/../dataeditor/twintable.h:117:7: warning: 
‘virtual void TwinTable::objectMetaChanged(RObject*)’ can be marked override 
[-Wsuggest-override]
  117 |  void objectMetaChanged (RObject* changed);
  |   ^
/<>/rkward/windows/rkworkplace.cpp: In constructor 
‘RKWorkplace::RKWorkplace(QWidget*)’:
/<>/rkward/windows/rkworkplace.cpp:71:2: error: ‘QVBoxLayout’ was 
not declared in this scope; did you mean ‘QLayout’?
   71 |  QVBoxLayout *message_layout = new QVBoxLayout (message_area);

You can find the build logs here: 


Thanks for your work, Lisandro.

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

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

Bug#947996: marked as done (golang-github-mailru-easyjson FTBFS in testing/unstable)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 00:34:08 +
with message-id 
and subject line Bug#947996: fixed in golang-github-mailru-easyjson 0.7.0-1
has caused the Debian Bug report #947996,
regarding golang-github-mailru-easyjson FTBFS in testing/unstable
to be marked as done.

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

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


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

source: golang-github-mailru-easyjson
version: 0.0~git20161103.0.159cdb8-1.1
severity: serious
tags: bullseye, sid, ftbfs

golang-github-mailru-easyjson FTBFS in testing/unstable, I first noticed this 
on a raspbian autobuilder, but it's also happening on the reproducible builds 
tests, so it's not raspbian specific.


easyjson -all 
/build/1st/golang-github-mailru-easyjson-0.0~git20161103.0.159cdb8/obj-x86_64-linux-gnu/src/github.com/mailru/easyjson/tests/data.go
failed to initialize build cache at /nonexistent/first-build/.cache/go-build: 
mkdir /nonexistent: permission denied
Bootstrap failed: exit status 1


--- End Message ---
--- Begin Message ---
Source: golang-github-mailru-easyjson
Source-Version: 0.7.0-1

We believe that the bug you reported is fixed in the latest version of
golang-github-mailru-easyjson, 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.
Martina Ferrari  (supplier of updated 
golang-github-mailru-easyjson 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, 15 Jan 2020 00:13:06 +
Source: golang-github-mailru-easyjson
Architecture: source
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martina Ferrari 
Closes: 947996
Changes:
 golang-github-mailru-easyjson (0.7.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Alexandre Viau ]
   * Point Vcs-* urls to salsa.debian.org.
 .
   [ Martina Ferrari ]
   * Update gbp.conf.
   * Automated cme fixes, including bumping dh compat,
 which closes: #947996.
   * Add watchfile.
   * Instead of patching the Makefile, run the code generator from
 debian/rules.
   * Fix short descriptions.
Checksums-Sha1:
 16208ad96357b58523845c2f5847ea454c4a6dd8 2313 
golang-github-mailru-easyjson_0.7.0-1.dsc
 d69dca5ceffc0fb2bb9961199d75d2e9b57c9ac6 72840 
golang-github-mailru-easyjson_0.7.0.orig.tar.gz
 4f1c63926a844901f15b4d613a61608cdbf0947a 3292 
golang-github-mailru-easyjson_0.7.0-1.debian.tar.xz
 e80e2c582e2861c91aa34bcd45eb8b77f921f553 6039 
golang-github-mailru-easyjson_0.7.0-1_amd64.buildinfo
Checksums-Sha256:
 96c74becf056259155db7563e21c76742e4dce51d0d9106e09a4a0f5a6947744 2313 
golang-github-mailru-easyjson_0.7.0-1.dsc
 6229c0ec172b9409b7b6799eddec5280a0359389bd89c1a890ef52960d6bd7b6 72840 
golang-github-mailru-easyjson_0.7.0.orig.tar.gz
 c45a73fc6e5e4998da668fd8078fa414f0092b713b2972c7bdf09e7e05cd5c3a 3292 
golang-github-mailru-easyjson_0.7.0-1.debian.tar.xz
 94e5ffd1ed625118b3d9d0cca31b4351b9be73699a605630ba428dc52e99144d 6039 
golang-github-mailru-easyjson_0.7.0-1_amd64.buildinfo
Files:
 47131aa19a27df03ee49a5513cc38d18 2313 devel optional 
golang-github-mailru-easyjson_0.7.0-1.dsc
 ff8ed18ebe2fa7d93cf6c528adf04791 72840 devel optional 
golang-github-mailru-easyjson_0.7.0.orig.tar.gz
 e706360769e73abc4ea69e63b039ff61 3292 devel optional 
golang-github-mailru-easyjson_0.7.0-1.debian.tar.xz
 81460f9162eb2d9d6aa3a9cb9ac28da9 6039 devel optional 
golang-github-mailru-easyjson_0.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAl4eWWoACgkQXdjgv5Gj
09plshAAhaROGkHeIZA93b/ZLfuwg00galI/3xw+X80kuWnKlrrRWGggavlWFCic
HUEIhiRVrGA9zwzFJnaCYq+xavukJ27KUIsmi6WuwkNYqP/Jf3S5he1DXdZxQjDZ
ynp5sII3GGebLWuZzYQF75ZBPoNYPt60/WdFPobhzcmjRHzjqGhsRcpsQv0fyeFV
m/ueL0JdAxwYJhST75T7DVjSxoHTs4EIiwlUO9YqIKqo4p4gTWp5vfSdvJjE8WJz
ohRN7FXOIKE5e1exF4eVsRuRfa3OWsA98OaD0BM053xm3iYhRuulioxD5ZfQoM4A
aP5IvOEoJxwb1GPcXUqDEiak5BvEuAysQbIhAS55kZWykPWCONn3e5s2Ks0ekt6W
yd4kg8Hq47WLlksHkNIjN/XzEKRLvLdnUhjespB468e/jjNsSX9B6/lpPMcx/Par

Bug#948268: marked as done (Crashes after startup)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jan 2020 00:35:12 +
with message-id 
and subject line Bug#948268: fixed in slirp 1:1.0.17-9
has caused the Debian Bug report #948268,
regarding Crashes after startup
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.)


-- 
948268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slirp
Version: 1:1.0.17-8+b1
Severity: grave

Hey;

When starting slirp it crashes almost immediately; Backtrace from gdb:
```
(gdb) bt
#0  ip_slowtimo () at ip_input.c:457
#1  0x55568a82 in main_loop () at ./main.c:980
#2  0x97c6 in main (argc=1, argv=0x7fffdf38) at ./main.c:95
```

Looking at the code the ipq next/prev "pointer" fields in the ipq structure are
32 bits, which doesn't work that well on 64 bit systems.

Setting to grave as most people these days run 64 bit systems on which slirp
will be completely unustable.

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

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

Versions of packages slirp depends on:
ii  libc6  2.29-8

slirp recommends no packages.

slirp suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: slirp
Source-Version: 1:1.0.17-9

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

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

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

Debian distribution maintenance software
pp.
Roberto Lumbreras  (supplier of updated slirp 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, 15 Jan 2020 00:54:06 +0100
Source: slirp
Architecture: source
Version: 1:1.0.17-9
Distribution: unstable
Urgency: medium
Maintainer: Roberto Lumbreras 
Changed-By: Roberto Lumbreras 
Closes: 948268
Changes:
 slirp (1:1.0.17-9) unstable; urgency=medium
 .
   * Fix crash after startup bug (Closes: #948268)
   * Make it compile on GNU Hurd.
   * Updated standards and minor fixes.
Checksums-Sha1:
 8f1449f048fb07d861f30ac6e70aeb8264339269 1733 slirp_1.0.17-9.dsc
 2bcb9abe3fb9706c3abd3946d10390726981a9c8 14616 slirp_1.0.17-9.debian.tar.xz
 2babc926bdb215ecc39fa5c62324b508fc420b56 6329 slirp_1.0.17-9_amd64.buildinfo
Checksums-Sha256:
 c0fa24bb40de04ca12df68620467d1059880e53f74594cd448ec3b5cb947a300 1733 
slirp_1.0.17-9.dsc
 8a736a35613693e1a307912c88ba24c1359c5595afcea56dfb552ca7f9476df3 14616 
slirp_1.0.17-9.debian.tar.xz
 5171c68449da07c1576aba410fdcb2ca5340a30a04298913ce16a3792d89bdc2 6329 
slirp_1.0.17-9_amd64.buildinfo
Files:
 a4b4c1c450021c12bf5364a9f1b46787 1733 net optional slirp_1.0.17-9.dsc
 2b061d3fc92a07319b69097c66de94f3 14616 net optional 
slirp_1.0.17-9.debian.tar.xz
 80b310fce938bc29c737a22234725f8b 6329 net optional 
slirp_1.0.17-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE0P8TF3YtXzyApcdAtn7iEBIpC00FAl4eWXYRHHJvdmVyQGRl
Ymlhbi5vcmcACgkQtn7iEBIpC02GKRAAsmNFHKRr3q0SQS5r0oPVZ1vYfmE8/oCs
hzVaifxpvXxS85KvwZVXa+Lqnn+dYsVkehVqFhCftAW3V92YH2M7CGJO2gbteJny
tctHWkP7RM3Y4xTsQdeKq/BfT7oMYSx6qxI4hc5irFHjlW/tYoorvDH6BaUA+N5m
aAuwrv+wxGcGV8v21zQZ347mpA+zWDRYDSWC3uurOlIUuSbmVHAnW5ywkNXEGoW7
GxlkDb3BZoIe44y2MdAp4iOo9yvopaQOPkmBl+H2A+CAzg/tmok8Wgx8QldxIP/c
/5QwsGQJz5U88lLLtuKxDcFWEUJKdaaHtEvJSX/uhE6kUuo+jn48gin5V40grSNo
E1QSQX7eqBXE0Rgw7wlOv9gk1OaPYCP2VF5gbad4AaKHfuZIEJ+95WYa7J+wfXO/
zE3oByzveCIrM50ZOJcbdEGycacPVFxJ9haTDXvRkkrgHcrW19cQkiWVObNP/Hvu
K60GUhpkpXTXkWa4hjE+hEbopDjNWjxSyd66NSRLuN7zT+GzVflEP20WJc/jpiI3
NzXohZuDovrBfLAN2xkGUgFkc4s98vmDmSwnQw6Pi2N38f9AmKEHJS4x7kfu/v/o
JP0OsOjj1gZRZ5a1/e/I1y0x78kUJBDfT/xIcb9smPd3pWWp88h2vJmgCB8K9OlH
Zo3IMfhWoZY=
=cBeF
-END PGP SIGNATURE End Message ---

Bug#948937: gr-fcdproplus FTBFS missing build-dependencies on dh-python and liborc-0.4-dev

[peter green]

Package: gr-fcdproplus
Version: 3.8~20190817-2
Severity: serious
Tags: patch.

gr-fcdproplus fails to build due to a missing dh-python, I initially noticed 
this on a raspbian autobuilder, but it's also happening on the reproducible 
builds site, so it's not raspbian specific.


dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/arm-linux-gnueabihf/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/arm-linux-gnueabihf/perl5/5.30 /usr/share/perl5 
/usr/lib/arm-linux-gnueabihf/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at (eval 16) 
line 1.
BEGIN failed--compilation aborted at (eval 16) line 1.

The fix for that was easy, just add the build-dependency on dh-python.

However when I tried to build it with the build-dependency added I got another 
build failure.


[ 47%] Built target doxygen_target
make[3]: *** No rule to make target 
'/usr/lib/arm-linux-gnueabihf/liborc-0.4.so', needed by 
'lib/libgnuradio-fcdproplus.so.3.8.0.0'.  Stop.
make[3]: *** Waiting for unfinished jobs


Again this was a missing build-dependency, this time on liborc-0.4-dev

After adding the build-dependencies on dh-python and liborc-0.4-dev I was able 
to get a succesful build. However my build environment was not clean, so it is 
possible that there were other missing build-dependencies I missed.

Bug#948938: gr-iqbal FTBFS missing build-dependency on dh-python

[peter green]

Package: gr-iqbal
Version: 0.38-3
Severity: serious
Tags: patch

gr-rds FTBFS due to a missing build-dependency on dh-python,


dh clean --with python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/arm-linux-gnueabihf/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/arm-linux-gnueabihf/perl5/5.30 /usr/share/perl5 
/usr/lib/arm-linux-gnueabihf/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at (eval 16) 
line 1.
BEGIN failed--compilation aborted at (eval 16) line 1.


I initially noticed this on a raspbian autobuilder, but it is also happening on 
the reproducible builds site, so it's not raspbian specific.

The fix is a simple matter of adding the build-depedency.

Bug#948936: gr-rds FTBFS missing build-dependency on dh-python

[peter green]

Package: gr-rds
Version: 3.8.0.0.f1c584a-2
Severity: serious
Tags: patch

gr-rds FTBFS due to a missing build-dependency on dh-python,


dh clean --with python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/arm-linux-gnueabihf/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/arm-linux-gnueabihf/perl5/5.30 /usr/share/perl5 
/usr/lib/arm-linux-gnueabihf/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at (eval 16) 
line 1.
BEGIN failed--compilation aborted at (eval 16) line 1.


I initially noticed this on a raspbian autobuilder, but it is also happening on 
the reproducible builds site, so it's not raspbian specific.

The fix is a simple matter of adding the build-depedency.

Processed: RM python-wxmpl

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #938269 [src:python-wxmpl] python-wxmpl: Python2 removal in sid/bullseye
Bug reassigned from package 'src:python-wxmpl' to 'ftp.debian.org'.
No longer marked as found in versions python-wxmpl/2.0.0-2.1.
Ignoring request to alter fixed versions of bug #938269 to the same values 
previously set
> retitle -1 RM: python-wxmpl -- RoQA; dead upstream; unmaintained; low popcon; 
> blocking py2 removal
Bug #938269 [ftp.debian.org] python-wxmpl: Python2 removal in sid/bullseye
Changed Bug title to 'RM: python-wxmpl -- RoQA; dead upstream; unmaintained; 
low popcon; blocking py2 removal' from 'python-wxmpl: Python2 removal in 
sid/bullseye'.

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

Bug#938269: RM python-wxmpl

[Scott Talbert]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: python-wxmpl -- RoQA; dead upstream; unmaintained; low 
popcon; blocking py2 removal

Bug#937033: marked as done (mgltools-scenario2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:20:40 +
with message-id 
and subject line Bug#948879: Removed package(s) from unstable
has caused the Debian Bug report #937033,
regarding mgltools-scenario2: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mgltools-scenario2

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

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

Dear submitter,

as the package mgltools-scenario2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948879

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Bug#947996 marked as pending in golang-github-mailru-easyjson

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #947996 [src:golang-github-mailru-easyjson] golang-github-mailru-easyjson 
FTBFS in testing/unstable
Added tag(s) pending.

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

Bug#768898: marked as done (libmapper: Unsuitable for Testing, please keep it in Unstable for a while)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:21:55 +
with message-id 
and subject line Bug#948883: Removed package(s) from unstable
has caused the Debian Bug report #768898,
regarding libmapper: Unsuitable for Testing, please keep it in Unstable for a 
while
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.)


-- 
768898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmapper
Version: 0.3~git+20141027-1
Severity: serious

Libmapper upstream developers request that the current version be kept in
Debian Unstable, since the current commit is not connected to any
official release, nor the library is ready to be widely used at this
point.

See discussion at
https://groups.google.com/forum/#!topic/dot_mapper/79irfhK6790

This bug severity will be lower in the right time.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libmapper depends on:
ii  libc6  2.19-11
ii  liblo7 0.28-3
ii  multiarch-support  2.19-9
ii  zlib1g 1:1.2.8.dfsg-2

libmapper recommends no packages.

libmapper suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.3~git+20141027-1+rm

Dear submitter,

as the package libmapper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948883

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#937037: marked as done (mgltools-utpackages: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:21:05 +
with message-id 
and subject line Bug#948880: Removed package(s) from unstable
has caused the Debian Bug report #937037,
regarding mgltools-utpackages: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mgltools-utpackages

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

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

Dear submitter,

as the package mgltools-utpackages has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948880

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#768901: marked as done (python-libmapper: Unsuitable for Testing, please keep it in Unstable for a while)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:21:55 +
with message-id 
and subject line Bug#948883: Removed package(s) from unstable
has caused the Debian Bug report #768898,
regarding python-libmapper: Unsuitable for Testing, please keep it in Unstable 
for a while
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.)


-- 
768898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-libmapper
Version: 0.3~git+20141027-1
Severity: serious

Libmapper upstream developers request that the current version be kept
in Debian Unstable, since the current commit is not connected to any
official release, nor the library is ready to be widely used at this
point.

See discussion at
https://groups.google.com/forum/#!topic/dot_mapper/79irfhK6790

This bug severity will be lower in the right time.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-libmapper depends on:
ii  libc6  2.19-11
ii  liblo7 0.28-3
ii  libmapper  0.3~git+20141027-1
ii  python 2.7.8-1

python-libmapper recommends no packages.

python-libmapper suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.3~git+20141027-1+rm

Dear submitter,

as the package libmapper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948883

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#936891: marked as done (libmapper: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:21:55 +
with message-id 
and subject line Bug#948883: Removed package(s) from unstable
has caused the Debian Bug report #936891,
regarding libmapper: 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.)


-- 
936891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmapper
Version: 0.3~git+20141027-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:libmapper

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

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

Dear submitter,

as the package libmapper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948883

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#947996: marked as pending in golang-github-mailru-easyjson

[Martina Ferrari]

Control: tag -1 pending

Hello,

Bug #947996 in golang-github-mailru-easyjson reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-mailru-easyjson/commit/c077713ba7aae044bc8dbcddf17f50fb79ce6432


Automated cme fixes, including bumping dh compat, which closes: #947996.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947996

Bug#937042: marked as done (mgltools-webservices: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:23:12 +
with message-id 
and subject line Bug#948893: Removed package(s) from unstable
has caused the Debian Bug report #937042,
regarding mgltools-webservices: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mgltools-webservices

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

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

Dear submitter,

as the package mgltools-webservices has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948893

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#937038: marked as done (mgltools-viewerframework: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:21:29 +
with message-id 
and subject line Bug#948882: Removed package(s) from unstable
has caused the Debian Bug report #937038,
regarding mgltools-viewerframework: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mgltools-viewerframework

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

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

Dear submitter,

as the package mgltools-viewerframework has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948882

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#937039: marked as done (mgltools-vision: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:22:19 +
with message-id 
and subject line Bug#948887: Removed package(s) from unstable
has caused the Debian Bug report #937039,
regarding mgltools-vision: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mgltools-vision

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

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

Dear submitter,

as the package mgltools-vision has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948887

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#937030: marked as done (mgltools-pyautodock: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:20:06 +
with message-id 
and subject line Bug#948878: Removed package(s) from unstable
has caused the Debian Bug report #937030,
regarding mgltools-pyautodock: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mgltools-pyautodock

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

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

Dear submitter,

as the package mgltools-pyautodock has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948878

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#768900: marked as done (libmapper-dev: Unsuitable for Testing, please keep it in Unstable for a while)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:21:55 +
with message-id 
and subject line Bug#948883: Removed package(s) from unstable
has caused the Debian Bug report #768898,
regarding libmapper-dev: Unsuitable for Testing, please keep it in Unstable for 
a while
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.)


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

Libmapper upstream developers request that the current version be kept
in Debian Unstable, since the current commit is not connected to any
official release, nor the library is ready to be widely used at this
point.

See discussion at
https://groups.google.com/forum/#!topic/dot_mapper/79irfhK6790

This bug severity will be lower in the right time.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 0.3~git+20141027-1+rm

Dear submitter,

as the package libmapper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948883

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#937041: marked as done (mgltools-volume: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:22:41 +
with message-id 
and subject line Bug#948889: Removed package(s) from unstable
has caused the Debian Bug report #937041,
regarding mgltools-volume: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mgltools-volume

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

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

Dear submitter,

as the package mgltools-volume has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948889

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#936488: marked as done (epylog: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 23:23:36 +
with message-id 
and subject line Bug#948896: Removed package(s) from unstable
has caused the Debian Bug report #936488,
regarding epylog: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:epylog

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

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

Dear submitter,

as the package epylog has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/948896

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

[Валерий Заподовников]

Yes, this fix
https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/23/diffs
indeed at least silenced (maybe fixed) those wornings after
update-initramfs -u

Hope you will pull that in initramfs-tools-core as shown by dpkg -S
./mkinitramfs


And *I hope* it will happen faster than with this obnoxious bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931930

Processed: tagging 948393

[Debian Bug Tracking System]

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

> tags 948393 + patch
Bug #948393 [foxtrotgps] foxtrotgps: fails to connect to gpsd despite SUCCESS 
message
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#948935: pius ftbfs, doesn't install multiple build dependencies

[Matthias Klose]

Package: src:pius
Version: 3.0.0-1
Severity: serious
Tags:sid bullseye patch

pius ftbfs, doesn't install multiple build dependencies. The alternatives in the
b-d are bogus. please just b-d on python3-all.

patch at
http://launchpadlibrarian.net/460610285/pius_3.0.0-1build1_3.0.0-1ubuntu1.diff.gz

Bug#948777: marked as done (viking: FTBFS error: incompatible types when initializing type 'time_t')

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 22:06:53 +
with message-id 
and subject line Bug#948777: fixed in viking 1.7-2
has caused the Debian Bug report #948777,
regarding viking: FTBFS error: incompatible types when initializing type 
'time_t'
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.)


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

Dear maintainer,

while doing a rebuild in a standard unstable chroot, your package failed
to build.


gcc -DHAVE_CONFIG_H -I.  -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DVIKING_DATADIR=\""/usr/share/viking"\" -DVIKING_SYSCONFDIR=\""/etc/viking"\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -D_GNU_SOURCE -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/libgeoclue-2.0 -I/usr/include/gio-unix-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-ffile-prefix-map=/build/1st/viking-1.7=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o viktrwlayer_export.o viktrwlayer_export.c
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from viking.h:25,
 from vikaggregatelayer.c:23:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: 'GTypeDebugFlags' is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from viking.h:25,
 from vikaggregatelayer.c:23:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from viking.h:25,
 from vikgpslayer.c:32:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: 'GTimeVal' is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from 

Processed: severity of 948393 is serious

[Debian Bug Tracking System]

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

> severity 948393 serious
Bug #948393 [foxtrotgps] foxtrotgps: fails to connect to gpsd despite SUCCESS 
message
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#948388: navit: fails to connect to gpsd

[Bernd Zeimetz]

Hi,

On 1/9/20 12:43 AM, Paul Wise wrote:
> On Wed, 2020-01-08 at 23:45 +0100, Bernd Zeimetz wrote:
> 
>> If necessary I can upload 3.19 to unstable again as 3.20-1+3.19 or so.
> 
> Personally, I think just go ahead with the transition, inform the
> release team of the ABI break and file the needed FTBFS RC bugs.


that happened.

I've tried to rebuild navit, but the current version FTBFS for me, it
fails to link libpthreads (with s..).

Somebody with more navit know-how needs to fix that, then I'm happy to
help with the gpsd api changes.


Bernd


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

Processed: severity of 948388 is serious

[Debian Bug Tracking System]

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

> severity 948388 serious
Bug #948388 [navit] navit: fails to connect to gpsd
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#948930: python-socksipychain: autopkgtest regression: No module named sockschain

[Paul Gevers]

Source: python-socksipychain
Version: 2.1.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of python-socksipychain the autopkgtest of
python-socksipychain fails in testing when that autopkgtest is run with
the binary packages of python-socksipychain from unstable. It passes
when run with only packages from testing. In tabular form:
   passfail
python-socksipychainfrom testing2.1.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems that
you forgot to update the autopkgtest when you dropped Python2 support.

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-socksipychain

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-socksipychain/3803227/log.gz

autopkgtest [16:41:59]: test command1: set -e ; for py in $(pyversions
-r 2>/dev/null) ; do cd "$ADTTMP" ; echo "Testing with $py:" ; $py -c
"import sockschain; print sockschain" ; done
autopkgtest [16:41:59]: test command1: [---
Testing with python2.7:
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named sockschain
autopkgtest [16:41:59]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#948918: marked as done (libbiod FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 21:35:38 +
with message-id 
and subject line Bug#948918: fixed in libbiod 0.2.3+git20191120.b8eecef-2
has caused the Debian Bug report #948918,
regarding libbiod FTBFS on i386
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.)


-- 
948918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbiod
Version: 0.2.3+git20191120.b8eecef-1
Severity: serious
Tags: ftbfs

Dear maintainers,

libbiod FTBFS on i386. In case the software intentionally doesn't support 
32-bit,
the old binary package should be removed as it's currently preventing libundead 
removal.

I have quoted the error message from the log below.
https://buildd.debian.org/status/fetch.php?pkg=libbiod=i386=0.2.3%2Bgit20191120.b8eecef-1=1576379323=0
-
[42/199] ldc2 -I=biod@sha -I=. -I=.. -enable-color -O -g -release -wi 
-relocation-model=pic -O3 -release -enable-inlining -boundscheck=off 
-of='biod@sha/bio_std_file_fasta.d.o' -c ../bio/std/file/fasta.d
FAILED: biod@sha/bio_std_file_fasta.d.o 
ldc2 -I=biod@sha -I=. -I=.. -enable-color -O -g -release -wi 
-relocation-model=pic -O3 -release -enable-inlining -boundscheck=off 
-of='biod@sha/bio_std_file_fasta.d.o' -c ../bio/std/file/fasta.d
../bio/std/file/fasta.d(81): Error: cannot implicitly convert expression i - 
this.lineLen of type ulong to uint
../bio/std/file/fasta.d(81): Error: cannot implicitly convert expression i of 
type ulong to uint
../bio/std/file/fasta.d(83): Error: cannot implicitly convert expression i - 
this.lineLen of type ulong to uint
../bio/std/file/fasta.d(236): Error: cannot implicitly convert expression 
reference.seqLen + reference.seqLen / reference.lineLen of type ulong to uint
../bio/std/file/fasta.d(238): Error: cannot implicitly convert expression 
region.len() + region.len() / reference.lineLen of type ulong to uint
-

Regards,
Juhani
--- End Message ---
--- Begin Message ---
Source: libbiod
Source-Version: 0.2.3+git20191120.b8eecef-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 Jan 2020 21:35:33 +0100
Source: libbiod
Architecture: source
Version: 0.2.3+git20191120.b8eecef-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 948918
Changes:
 libbiod (0.2.3+git20191120.b8eecef-2) unstable; urgency=medium
 .
   * Restrict architectures to amd64 and arm64 where the package
 really builds
 Closes: #948918
Checksums-Sha1:
 1c31f92d83df6628aa8af20ac724a88442ad4a05 2173 
libbiod_0.2.3+git20191120.b8eecef-2.dsc
 3907ab0d0407a86da20c268499977a9b7b4207c0 5544 
libbiod_0.2.3+git20191120.b8eecef-2.debian.tar.xz
 212fb1e8bf79698b5ef265896eab11653288290b 15821 
libbiod_0.2.3+git20191120.b8eecef-2_source.buildinfo
Checksums-Sha256:
 d020a3205a29cf437bff3462c05dc4311353e23d435f1bd455cac367311558da 2173 
libbiod_0.2.3+git20191120.b8eecef-2.dsc
 52f2375e62727ccf624f961bc0f9859ad2666bb99349b8c24fd5367c33d939ef 5544 
libbiod_0.2.3+git20191120.b8eecef-2.debian.tar.xz
 b0dc7a5da59b0265dc2bb0a52fd1d86a57a691618ea0345f67231fb532e608a2 15821 
libbiod_0.2.3+git20191120.b8eecef-2_source.buildinfo
Files:
 1c203c4858ac503ff3b08dce23e6c0ab 2173 science optional 
libbiod_0.2.3+git20191120.b8eecef-2.dsc
 bbf5e72de6fde6e56930059b60df0dab 5544 science optional 
libbiod_0.2.3+git20191120.b8eecef-2.debian.tar.xz
 7b23acba23f08fb7a5dae9a4e0cd02a1 15821 science optional 
libbiod_0.2.3+git20191120.b8eecef-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl4eMUAOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtFUaA//ecXovWf7r++PBe8OYIrtMIdL1caqfiLScN2d
oa2AOeN59rkrX7+gSU1vYFFOaCUU5w7WwE7z83Ob7o26JPCM3a8WajAb1qVCpndv
X4WODOURR5GNkYhYikFnOMwmuzOhIA7Zrydc6D6R5Wrv6l9drjlp6QJiguQQxOrC
5cEyZcRBrduEdB+nxhMJKqHmsjWT9WXX2hfj9a8q9qFc8SL8rhrevT9PvVC4kVQy

Processed: py2removal bugs severity updates - 2020-01-14 21:35:57.381298+00:00

[Debian Bug Tracking System]

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

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

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

Processed: severity of 943015 is serious, severity of 943073 is serious, severity of 943066 is serious ...

[Debian Bug Tracking System]

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

> severity 943015 serious
Bug #943015 [src:fonts-ebgaramond] fonts-ebgaramond: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943073 serious
Bug #943073 [src:fonts-fantasque-sans] fonts-fantasque-sans: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943066 serious
Bug #943066 [src:fonts-karmilla] fonts-karmilla: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943077 serious
Bug #943077 [src:fonts-lohit-deva] fonts-lohit-deva: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943078 serious
Bug #943078 [src:fonts-lohit-deva-marathi] fonts-lohit-deva-marathi: Python2 
removal in sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943020 serious
Bug #943020 [src:fonts-lohit-deva-nepali] fonts-lohit-deva-nepali: Python2 
removal in sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943011 serious
Bug #943011 [src:fonts-lohit-gujr] fonts-lohit-gujr: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943080 serious
Bug #943080 [src:fonts-monoid] fonts-monoid: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> severity 943088 serious
Bug #943088 [src:fonts-smc-suruma] fonts-smc-suruma: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
943011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943011
943015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943015
943020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943020
943066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943066
943073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943073
943077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943077
943078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943078
943080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943080
943088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#948929: mawk: autopkgtest regression: new output to stderr

[Paul Gevers]

Source: mawk
Version: 1.3.3-19
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of mawk the autopkgtest of mawk fails in testing
when that autopkgtest is run with the binary packages of mawk from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
mawk   from testing1.3.3-19
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test
doesn't fail by itself, but apparently there is a new warning that is
printed to stderr that makes the autopkgtest fail. Either suppress that
warning, or add the allow-stderr restriction to the autopkgtest definition.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mawk/3793105/log.gz

autopkgtest [11:48:56]: test mawktest: [---
mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan


testing input and field splitting
input and field splitting OK

testing regular expression matching
mawk: line 1: regular expression /a\ ... exceeds implementation
size limit
regular expression matching OK

testing checking for write errors
checking for write errors OK

testing arrays and flow of control
array test OK

testing function calls and general stress test
general stress test passed

tested mawk seems OK
autopkgtest [11:48:56]: test mawktest: ---]
autopkgtest [11:48:56]: test mawktest:  - - - - - - - - - - results - -
- - - - - - - -
mawktest FAIL stderr: mawk: line 1: regular expression
/a\ ... exceeds implementation size limit



signature.asc
Description: OpenPGP digital signature

Bug#948931: sumo-tools depends on both python and python3

[Matthias Klose]

Package: sumo-tools
Version: 1.3.1-5
Severity: serious
Tags: sid bullseye

sumo-tools depends on both python and python3. Is this really intended?

Bug#948925: pbseqlib ftbfs with libpbbam1.0.6

[Andreas Tille]

Hi Paul,

thanks for your bug report.

On Tue, Jan 14, 2020 at 09:45:59PM +0100, Paul Gevers wrote:
> Source: pbseqlib
> Version: 5.3.1+dfsg-2.1
> Severity: serious
> Justification: ftbfs
> Tags: ftbfs sid bullseye
> 
> Dear maintainer,
> 
> pbbam started a transition and I scheduled binNMUs for pbseqlib.
> However, they failed. Please investigate.
> 
> Paul
> 
> https://buildd.debian.org/status/package.php?p=pbseqlib
> 
> Tail of log for pbseqlib on amd64:
> 
> /usr/include/pbbam/BamRecord.h:19:10: fatal error:
> pbcopper/data/MappedRead.h: No such file or directory
>19 | #include 
>   |  ^~~~
> compilation terminated.

I admit there are lots of problems currently with PacBio software
(packages mostly start with pb*).  We tried hard to get the latest
versions libpbcopper and libpbbam to build but upstream has quite a weak
release management and besides this has on some projects disabled the
issue tracker effectively preventing us from issues like this.  The
only way to do the transition is removing blockers like this from
testing for the moment.

In addition to the complex situation the former Uploader Afif had to
reduce his involvement and so I try to take this stack on my shoulders
as well.  We need to see how this might work out until next freeze but
may be we need to drop some of the packages from Debian.  Since its not
clear for the moment whether we can fix these issues after a new
upstream release easily I do not think that the time for removal has
come right now - so simply lets drop it from testing for the moment.

Kind regards and thanks for your QA work

   Andreas.

-- 
http://fam-tille.de

Bug#948926: blasr ftbfs with libpbbam1.0.6

[Paul Gevers]

Source: blasr
Version: 5.3.3+dfsg-2
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

pbbam started a transition and I scheduled binNMUs for blasr.
However, they failed. Please investigate.

Paul

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

Tail of log for blasr on amd64:

Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency pbbam found: NO

meson.build:54:0: ERROR: Could not generate cargs for pbbam:
Package pbcopper was not found in the pkg-config search path.
Perhaps you should add the directory containing `pbcopper.pc'
to the PKG_CONFIG_PATH environment variable
Package 'pbcopper', required by 'pbbam', not found


A full log can be found at /<>/build/meson-logs/meson-log.txt
make[1]: *** [debian/rules:36: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:33: build-arch] Error 2



signature.asc
Description: OpenPGP digital signature

Bug#948925: pbseqlib ftbfs with libpbbam1.0.6

[Paul Gevers]

Source: pbseqlib
Version: 5.3.1+dfsg-2.1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

pbbam started a transition and I scheduled binNMUs for pbseqlib.
However, they failed. Please investigate.

Paul

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

Tail of log for pbseqlib on amd64:

/usr/include/pbbam/BamRecord.h:19:10: fatal error:
pbcopper/data/MappedRead.h: No such file or directory
   19 | #include 
  |  ^~~~
compilation terminated.
make[4]: *** [/<>/pbdata//../rules.mk:20: SMRTReadUtils.o]
Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/pbdata'
make[3]: *** [makefile:19: libpbdata] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [makefile:8: all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j4 "INSTALL=install --strip-program=true"
PREFIX_INC=.. returned exit code 2
make[1]: *** [debian/rules:31: override_dh_auto_build] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:25: build-arch] Error 2



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#948919: sambamba FTBFS: undefined reference to 'cram_to_bam'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #948919 [src:sambamba] sambamba FTBFS: undefined reference to 'cram_to_bam'
Added tag(s) help.
> tags -1 upstream
Bug #948919 [src:sambamba] sambamba FTBFS: undefined reference to 'cram_to_bam'
Added tag(s) upstream.
> forwarded -1 Pjotr Prins 
Bug #948919 [src:sambamba] sambamba FTBFS: undefined reference to 'cram_to_bam'
Set Bug forwarded-to-address to 'Pjotr Prins '.

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

Bug#915209: Info received (perl: FTBFS in the year 2020: cpan/Time-Local/t/Local.t failure)

[Niko Tyni]

On Tue, Jan 14, 2020 at 03:26:33PM +1100, Dean Hamstead wrote:
> The attached patch is for 5.24.1 old-stable and is derived from
> https://rt.cpan.org/Public/Bug/Display.html?id=124787

Thanks! I'll try to get this in the next oldstable point release,
currently scheduled for February.
-- 
Niko Tyni   nt...@debian.org

Bug#944455: marked as done (pgcli: missing dependency on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 20:44:20 +
with message-id 
and subject line Bug#944455: fixed in pgcli 2.2.0-3
has caused the Debian Bug report #944455,
regarding pgcli: missing dependency on python3-pkg-resources
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.)


-- 
944455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgcli
Version: 1.9.1-3
Severity: serious

pgcli does not run out-of-the-box after installing it in a minimal
sid (or buster) chroot:

# pgcli
Traceback (most recent call last):
  File "/usr/bin/pgcli", line 6, in 
  from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

Andreas
--- End Message ---
--- Begin Message ---
Source: pgcli
Source-Version: 2.2.0-3

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

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

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

Debian distribution maintenance software
pp.
Lennart Weller  (supplier of updated pgcli package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 Jan 2020 11:22:17 +0100
Source: pgcli
Binary: pgcli
Architecture: source all
Version: 2.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Lennart Weller 
Changed-By: Lennart Weller 
Description:
 pgcli  - CLI for Postgres
Closes: 944455
Changes:
 pgcli (2.2.0-3) unstable; urgency=medium
 .
   * pkg-resources hard dependency for minimal systems (Closes: #944455)
Checksums-Sha1:
 76684979624d7053cdfff95c4b21abf28e3dd1c8 1934 pgcli_2.2.0-3.dsc
 7ef4e84e27fbe407607bb2da8aca5e234eac8d83 13936 pgcli_2.2.0-3.debian.tar.xz
 0570134519c3591260b4c0a49d086f8052d9bfb7 78784 pgcli_2.2.0-3_all.deb
 2b7031d6b5777e4b3af9b52f21c72cc8b5251c83 6821 pgcli_2.2.0-3_amd64.buildinfo
Checksums-Sha256:
 23260d28767fefe602c8aebc2f5d08e3658093cf6e7c800df6e8de0353bc552e 1934 
pgcli_2.2.0-3.dsc
 9370492a538c1620fa50b9b677a678aa4700976357551fb5841dbac0038406be 13936 
pgcli_2.2.0-3.debian.tar.xz
 05bd8937fb078ef5564fbe3d9dd142868329e95609849dd851424a45c6d74a3a 78784 
pgcli_2.2.0-3_all.deb
 4a9242cdf28ea5b8103ddfbdc26511a52d56802500fe2f08434b9ffa165a6555 6821 
pgcli_2.2.0-3_amd64.buildinfo
Files:
 099cb247f1f98647e80f15cf7620bfda 1934 database optional pgcli_2.2.0-3.dsc
 dae8ed9d1d90e237ea14742ef1d52dde 13936 database optional 
pgcli_2.2.0-3.debian.tar.xz
 6c24a293d324f80902d5fcae9e5fc825 78784 database optional pgcli_2.2.0-3_all.deb
 e66d1d8d320f6690683b06fb2f7683de 6821 database optional 
pgcli_2.2.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJBBAEBCgArFiEERF1NBzmGgbU+WCnwLH/PgPT3bEMFAl4eIQgNHGxod0ByaW5n
MC5kZQAKCRAsf8+A9PdsQ49hD/4gvFhDa2hRGwVHCP8Z58ULOl2/zL+a7RtL45Nh
jrnfSU8kRx6hwOeSfMVH20fdjtHRG3u2EPssOb3o47Mk6tTfTITbgbqD1qeX6XO6
kKGvDSp2SJrBXwr/It9rKSEnBaofZCZdVvldedrqGpg3MZF0MjnTGq8Y0oqiZ6kW
dXEY3qsvLo0sP0bKzNx6gveLqGbUOYXrHUcF0+t0yL2iEnC1mDbA+mkgyVu5FMhK
aPRpiewuF4oyRTQS7pjcDb/gqAVTRxTujPupf0ed1Y9Ht9OJ5JGPvNLi2fj08QmS
2175FW9/jJO6EIzYXxU+F7kQsRQXG1VOWWaBx4BmUJ5QiewBNNgI9DKm8O63oIXN
Js6mehhJ6pk9UbE2lk8RDs1LW9TLIzc0ZTWLt+OBoRnR4xszChgtj/OrY+KLbswm
CSgeEiymFo/2paRuS946AGaryG8c0uLoxzeMAkt3jCjhOm+TGjIM2yVrwuWwHsCU
jLjCpPZVE1AJ/EojpZjm5b+PW3QDHeUMK69fINUBvziUCY/3gV2mmLF3Jf3TwrnQ
RnPz6mdriIiyG6eZhaZraPqjZpS0Vgn2YEsmG7Zh4Ff+lp15u41nNcBQbG6Ajw7I
L6oLY0ObLOTNzg+NjscyjtO6Jvnjmj1NXYQsN6Rw/vVymi9jAQ9TahubikQ47u3S
achioA==
=vkls
-END PGP SIGNATURE End Message ---

Bug#948919: sambamba FTBFS: undefined reference to 'cram_to_bam'

[Andreas Tille]

Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 Pjotr Prins 

Hi Matthias and Pjotr,

I'd like to forward another bug in Sambabma.

Any idea how to finally get sambamba build smoothly?

Kind regards

  Andreas.


On Tue, Jan 14, 2020 at 08:32:08PM +0200, Juhani Numminen wrote:
> Source: libbiod
> Version: 0.7.1-1
> Severity: serious
> Tags: ftbfs
> 
> Hello,
> 
> This new FTBFS is also being discussed on #907489 but I think they
> are separate issues.
> 
> I have quoted the error message from the log below.
> https://buildd.debian.org/status/fetch.php?pkg=sambamba=amd64=0.7.1-1=1576381970=0
> 
> FAILED: sambamba 
> ldc2  -of=sambamba 'sambamba@exe/sambamba_main.d.o' 
> 'sambamba@exe/sambamba_depth.d.o' 'sambamba@exe/sambamba_fixbins.d.o' 
> 'sambamba@exe/sambamba_flagstat.d.o' 'sambamba@exe/sambamba_index.d.o' 
> 'sambamba@exe/sambamba_markdup2.d.o' 'sambamba@exe/sambamba_markdup.d.o' 
> 'sambamba@exe/sambamba_merge.d.o' 'sambamba@exe/sambamba_pileup.d.o' 
> 'sambamba@exe/sambamba_slice.d.o' 'sambamba@exe/sambamba_sort.d.o' 
> 'sambamba@exe/sambamba_subsample.d.o' 
> 'sambamba@exe/sambamba_utils_common_bed.d.o' 
> 'sambamba@exe/sambamba_utils_common_file.d.o' 
> 'sambamba@exe/sambamba_utils_common_filtering.d.o' 
> 'sambamba@exe/sambamba_utils_common_intervaltree.d.o' 
> 'sambamba@exe/sambamba_utils_common_ldc_gc_workaround.d.o' 
> 'sambamba@exe/sambamba_utils_common_overwrite.d.o' 
> 'sambamba@exe/sambamba_utils_common_pratt_parser.d.o' 
> 'sambamba@exe/sambamba_utils_common_progressbar.d.o' 
> 'sambamba@exe/sambamba_utils_common_queryparser.d.o' 
> 'sambamba@exe/sambamba_utils_common_readstorage.d.o' 
> 'sambamba@exe/sambamba_utils_common_tmpdir.d.o' 
> 'sambamba@exe/sambamba_utils_view_alignmentrangeprocessor.d.o' 
> 'sambamba@exe/sambamba_utils_view_headerserializer.d.o' 
> 'sambamba@exe/sambamba_validate.d.o' 'sambamba@exe/sambamba_view.d.o' 
> 'sambamba@exe/utils_lz4.d.o' 'sambamba@exe/utils_strip_bcf_header.d.o' 
> 'sambamba@exe/utils_version_.d.o' 'sambamba@exe/cram_exception.d.o' 
> 'sambamba@exe/cram_htslib.d.o' 'sambamba@exe/cram_reader.d.o' 
> 'sambamba@exe/cram_reference.d.o' 'sambamba@exe/cram_slicereader.d.o' 
> 'sambamba@exe/cram_wrappers.d.o' 'sambamba@exe/cram_writer.d.o' 
> 'sambamba@exe/thirdparty_mergesort.d.o' 
> 'sambamba@exe/thirdparty_unstablesort.d.o' 
> 'sambamba@exe/ldc_version_info_.d.o' -L=-L--allow-shlib-undefined -O -g 
> -release -wi -L=-z -L=relro -L=--start-group 
> -L=/usr/lib/x86_64-linux-gnu/libbiod.a -L=/usr/lib/x86_64-linux-gnu/libz.a 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liblz4.so 
> /usr/lib/x86_64-linux-gnu/libhts.so -L=--end-group -L=-rpath 
> -L=/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu
> slicereader.d:71: error: undefined reference to 'cram_to_bam'
> collect2: error: ld returned 1 exit status
> -
> 
> Regards,
> Juhani
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Processed: Re: Bug#948901: open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

[Debian Bug Tracking System]

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

> tag 948901 + pending
Bug #948901 [src:open-infrastructure-service-tools] 
open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: 
expected one argument
Added tag(s) pending.
> tag 948902 + pending
Bug #948902 [src:open-infrastructure-storage-tools] 
open-infrastructure-storage-tools: FTBFS: a2x: error: argument --asciidoc-opts: 
expected one argument
Added tag(s) pending.
> tag 948903 + pending
Bug #948903 [src:open-infrastructure-system-tools] 
open-infrastructure-system-tools: FTBFS: a2x: error: argument --asciidoc-opts: 
expected one argument
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#948756: scgi: should this package be removed?

[Neil Schemenauer]

Latest code is on github:

https://github.com/nascheme/scgi

Latest commit was in Sept 2019.  I would upload a new package to
Debian but my GPG key has been removed and I have not yet been able
to find someone to sign a new key for me.

OTOH, I don't object to removing the package from Debian since I
suspect it is not heavily used and people can just install it from
the PyPI.

Bug#948901: open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

[Daniel Baumann]

tag 948901 + pending
tag 948902 + pending
tag 948903 + pending
thanks

On 1/14/20 5:40 PM, Mattia Rizzolo wrote:
> your package failed to rebuild in a standard sid chroot.

thanks for the reports.

asciidoc changed the order of arguments or something like that, I
already fixed it in one of my other packages.

I'll upload new versions of all of them anyway, at latest on Saturday.

Regards,
Daniel

Processed: Oops, I filed a bug against the wrong package...

[Debian Bug Tracking System]

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

> reassign 948919 src:sambamba
Bug #948919 [src:libbiod] sambamba FTBFS: undefined reference to 'cram_to_bam'
Bug reassigned from package 'src:libbiod' to 'src:sambamba'.
No longer marked as found in versions libbiod/0.7.1-1.
Ignoring request to alter fixed versions of bug #948919 to the same values 
previously set
> found 948919 0.7.1-1
Bug #948919 [src:sambamba] sambamba FTBFS: undefined reference to 'cram_to_bam'
The source 'sambamba' and version '0.7.1-1' do not appear to match any binary 
packages
Marked as found in versions sambamba/0.7.1-1.
>
End of message, stopping processing here.

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

Bug#948920: package build-depends on python-doc

[Matthias Klose]

Package: src:python-gmusicapi
Version: 12.1.1-2
Severity: serious
Tags: sid bullseye

The package build-depends on python-doc, but uses Python3 otherwise.

Processed: sambamba and libbiod FTBFS blocking libundead removal

[Debian Bug Tracking System]

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

> block 908670 by 948918 948919
Bug #908670 [ftp.debian.org] ROM: libundead: Please remove this package from 
Debian
908670 was not blocked by any bugs.
908670 was not blocking any bugs.
Added blocking bug(s) of 908670: 948919 and 948918
> thanks
Stopping processing here.

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

Bug#948919: sambamba FTBFS: undefined reference to 'cram_to_bam'

[Juhani Numminen]

Source: libbiod
Version: 0.7.1-1
Severity: serious
Tags: ftbfs

Hello,

This new FTBFS is also being discussed on #907489 but I think they
are separate issues.

I have quoted the error message from the log below.
https://buildd.debian.org/status/fetch.php?pkg=sambamba=amd64=0.7.1-1=1576381970=0

FAILED: sambamba 
ldc2  -of=sambamba 'sambamba@exe/sambamba_main.d.o' 
'sambamba@exe/sambamba_depth.d.o' 'sambamba@exe/sambamba_fixbins.d.o' 
'sambamba@exe/sambamba_flagstat.d.o' 'sambamba@exe/sambamba_index.d.o' 
'sambamba@exe/sambamba_markdup2.d.o' 'sambamba@exe/sambamba_markdup.d.o' 
'sambamba@exe/sambamba_merge.d.o' 'sambamba@exe/sambamba_pileup.d.o' 
'sambamba@exe/sambamba_slice.d.o' 'sambamba@exe/sambamba_sort.d.o' 
'sambamba@exe/sambamba_subsample.d.o' 
'sambamba@exe/sambamba_utils_common_bed.d.o' 
'sambamba@exe/sambamba_utils_common_file.d.o' 
'sambamba@exe/sambamba_utils_common_filtering.d.o' 
'sambamba@exe/sambamba_utils_common_intervaltree.d.o' 
'sambamba@exe/sambamba_utils_common_ldc_gc_workaround.d.o' 
'sambamba@exe/sambamba_utils_common_overwrite.d.o' 
'sambamba@exe/sambamba_utils_common_pratt_parser.d.o' 
'sambamba@exe/sambamba_utils_common_progressbar.d.o' 
'sambamba@exe/sambamba_utils_common_queryparser.d.o' 
'sambamba@exe/sambamba_utils_common_readstorage.d.o' 
'sambamba@exe/sambamba_utils_common_tmpdir.d.o' 
'sambamba@exe/sambamba_utils_view_alignmentrangeprocessor.d.o' 
'sambamba@exe/sambamba_utils_view_headerserializer.d.o' 
'sambamba@exe/sambamba_validate.d.o' 'sambamba@exe/sambamba_view.d.o' 
'sambamba@exe/utils_lz4.d.o' 'sambamba@exe/utils_strip_bcf_header.d.o' 
'sambamba@exe/utils_version_.d.o' 'sambamba@exe/cram_exception.d.o' 
'sambamba@exe/cram_htslib.d.o' 'sambamba@exe/cram_reader.d.o' 
'sambamba@exe/cram_reference.d.o' 'sambamba@exe/cram_slicereader.d.o' 
'sambamba@exe/cram_wrappers.d.o' 'sambamba@exe/cram_writer.d.o' 
'sambamba@exe/thirdparty_mergesort.d.o' 
'sambamba@exe/thirdparty_unstablesort.d.o' 'sambamba@exe/ldc_version_info_.d.o' 
-L=-L--allow-shlib-undefined -O -g -release -wi -L=-z -L=relro -L=--start-group 
-L=/usr/lib/x86_64-linux-gnu/libbiod.a -L=/usr/lib/x86_64-linux-gnu/libz.a 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liblz4.so 
/usr/lib/x86_64-linux-gnu/libhts.so -L=--end-group -L=-rpath 
-L=/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu
slicereader.d:71: error: undefined reference to 'cram_to_bam'
collect2: error: ld returned 1 exit status
-

Regards,
Juhani

Bug#948918: libbiod FTBFS on i386

[Juhani Numminen]

Source: libbiod
Version: 0.2.3+git20191120.b8eecef-1
Severity: serious
Tags: ftbfs

Dear maintainers,

libbiod FTBFS on i386. In case the software intentionally doesn't support 
32-bit,
the old binary package should be removed as it's currently preventing libundead 
removal.

I have quoted the error message from the log below.
https://buildd.debian.org/status/fetch.php?pkg=libbiod=i386=0.2.3%2Bgit20191120.b8eecef-1=1576379323=0
-
[42/199] ldc2 -I=biod@sha -I=. -I=.. -enable-color -O -g -release -wi 
-relocation-model=pic -O3 -release -enable-inlining -boundscheck=off 
-of='biod@sha/bio_std_file_fasta.d.o' -c ../bio/std/file/fasta.d
FAILED: biod@sha/bio_std_file_fasta.d.o 
ldc2 -I=biod@sha -I=. -I=.. -enable-color -O -g -release -wi 
-relocation-model=pic -O3 -release -enable-inlining -boundscheck=off 
-of='biod@sha/bio_std_file_fasta.d.o' -c ../bio/std/file/fasta.d
../bio/std/file/fasta.d(81): Error: cannot implicitly convert expression i - 
this.lineLen of type ulong to uint
../bio/std/file/fasta.d(81): Error: cannot implicitly convert expression i of 
type ulong to uint
../bio/std/file/fasta.d(83): Error: cannot implicitly convert expression i - 
this.lineLen of type ulong to uint
../bio/std/file/fasta.d(236): Error: cannot implicitly convert expression 
reference.seqLen + reference.seqLen / reference.lineLen of type ulong to uint
../bio/std/file/fasta.d(238): Error: cannot implicitly convert expression 
region.len() + region.len() / reference.lineLen of type ulong to uint
-

Regards,
Juhani

Processed: Tag ftbfs

[Debian Bug Tracking System]

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

> tag 948917 ftbfs
Bug #948917 [src:screengrab] FTBFS: No rule to make target 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.so'
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#948917: FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/libglib-2.0.so'

[Lisandro Damián Nicanor Pérez Meyer]

Source: screengrab
Version: 1.101-1
Severity: serious
Justification: FTBFS on all archs

Hi! During a rebuild your package FTBFS on all affected archs:




The error seems to be:

make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libglib-2.0.so', 
needed by 'src/modules/extedit/libextedit.so.1.0.0'.  Stop.

Kinds regards, Lisandro.


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

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

Processed (with 6 errors): Two different FTBFS separated

[Debian Bug Tracking System]

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

> clone 907489 -1
Bug #907489 {Done: Matthias Klumpp } [src:sambamba] sambamba 
FTBFS
Bug 907489 cloned as bug 948916
Failed to clone 907489: Not altering archived bugs; see unarchive.

> reopen -1
Failed to reopen -1: The 'bug' parameter ("-1") to Debbugs::Control::set_done 
did not pass regex check
.

> notfound -1 0.6.7-2
Failed to remove found on -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_found did not pass regex check
.

> found-1 0.7.1-1
Failed to add found on -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_found did not pass regex check
.

> retitle -1 sambamba FTBFS: undefined reference to 'cram_to_bam'
Failed to set the title of -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_title did not pass regex check
.

> block 908670 by -1
Failed to set blocking bugs of 908670: Invalid blocking bug(s):-1.

> stop
Stopping processing here.

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

Processed: Tagging bugs

[Debian Bug Tracking System]

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

> tag 948911 ftbfs
Bug #948911 [src:klog] klog: FTBFS on mipsel: {standard input}:107582: Error: 
branch out of range
Added tag(s) ftbfs.
> tag 948912 ftbfs
Bug #948912 [src:regina-normal] FTBFS: can not find boost >= 1.55
Added tag(s) ftbfs.
> tag 948913 ftbfs
Bug #948913 [src:sleepyhead] FTBFS: No rule to make target 'QtWebKit/QWebView', 
needed by 'ui_report.h'.  Stop
Added tag(s) ftbfs.
> tag 948914 ftbfs
Bug #948914 [src:qmath3d] FTBFS: The qmake executable '/usr/bin/qmake' failed 
with exit code 1.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#948914: FTBFS: The qmake executable '/usr/bin/qmake' failed with exit code 1.

[Lisandro Damián Nicanor Pérez Meyer]

Source: qmath3d
Version: 0~1.0-2)
Severity: serious
Justification: FTBFS on all archs

Hi Wookey! During a rebuild of your package it FTBFS:



The error seems to be:

WARNING: Error setting up Qt for '/usr/bin/qmake': The qmake executable 
'/usr/bin/qmake' failed with exit code 1.

And looking at the package's source code you are not exporting QT_SELECT 
widely, just during configure time.

Let me suggest you to simply export QT_SELECT as described in



Thanks for your work!

Lisandro.

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

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

Processed: Tagging FTBFS

[Debian Bug Tracking System]

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

> tag 948783 ftbfs
Bug #948783 {Done: Bastian Germann } [src:gambas3] 
gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this function)
Ignoring request to alter tags of bug #948783 to the same tags previously set
> tag 948790 ftbfs
Bug #948790 {Done: Gianfranco Costamagna } 
[src:gambas3] gambas3 ftbfs in unstable
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#948913: FTBFS: No rule to make target 'QtWebKit/QWebView', needed by 'ui_report.h'. Stop

[Lisandro Damián Nicanor Pérez Meyer]

Source: sleepyhead
Version: 1.0.0-beta-2+dfsg-7
Severity: serious
Justification: FTBFS: can not complete target

Hi! During a rebuild your package FTBFS:



The error seems to be:

/usr/lib/qt5/bin/uic ../../sleepyhead/mainwindow.ui -o ui_mainwindow.h
/usr/lib/qt5/bin/uic ../../sleepyhead/oximetry.ui -o ui_oximetry.h
/usr/lib/qt5/bin/uic ../../sleepyhead/preferencesdialog.ui -o 
ui_preferencesdialog.h
make[2]: *** No rule to make target 'QtWebKit/QWebView', needed by 
'ui_report.h'.  Stop.
make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory '/<>/_build/sleepyhead'
make[1]: *** [Makefile:47: sub-sleepyhead-make_first-ordered] Error 2
make[1]: Leaving directory '/<>/_build'
dh_auto_build: cd _build && make -j4 returned exit code 2
make: *** [debian/rules:17: build-arch] Error 255
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Kinds regards, Lisandro.

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

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

Bug#948912: FTBFS: can not find boost >= 1.55

[Lisandro Damián Nicanor Pérez Meyer]

Source: regina-normal
Version: 5.1-6
Severity: serious
Justification: Fails to build from source: can't find boost

During a rebuild your package failed to build form source:



CMake outputs the following error:


-
-- The following REQUIRED packages could NOT be located on your system.
-- You must install these packages before continuing.
-
   * Boost (>= 1.55)  
 Essential: C++ components (iostreams, python)

-

Kinds regards, Lisandro.

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

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

Bug#948911: klog: FTBFS on mipsel: {standard input}:107582: Error: branch out of range

[Lisandro Damián Nicanor Pérez Meyer]

Source: klog
Version: 0.9.8.1-1.1
Severity: serious
Justification: Fails to build from source on mipsel

Hi! During a rebuild your package FTBFS:




The bug seems related just to mipsel.

Kinds regards, Lisandro.

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

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

Bug#948908: plasma-desktop: FTBFS: error: ‘targetDesktop’ was not declared in this scope

[Dmitry Shachnev]

Source: plasma-desktop
Version: 4:5.14.5.1-4
Severity: serious
Tags: ftbfs sid

Dear maintainer,

During a recent rebuild plasma-desktop failed with the following error:

  /<>/applets/pager/plugin/pagermodel.cpp: In member function 
‘void PagerModel::moveWindow(int, double, double, int, int, qreal, qreal)’:
  /<>/applets/pager/plugin/pagermodel.cpp:524:14: error: 
‘targetDesktop’ was not declared in this scope; did you mean ‘addDesktop’?
524 | Q_UNUSED(targetDesktop)
|  ^
  /<>/applets/pager/plugin/pagermodel.cpp:525:14: error: 
‘sourceDesktop’ was not declared in this scope; did you mean ‘showDesktop’?
525 | Q_UNUSED(sourceDesktop)
|  ^

The full build log can be seen here:
https://buildd.debian.org/status/fetch.php?pkg=plasma-desktop=amd64=4%3A5.14.5.1-4%2Bb2=1578738060=0

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#948907: ktp-call-ui: FTBFS: QDBusArgument: No such file or directory

[Dmitry Shachnev]

Source: ktp-call-ui
Version: 17.08.3-1
Severity: serious
Tags: ftbfs sid

Dear maintainer,

During a recent rebuild ktp-call-ui failed with the following error:

  [ 35%] Building CXX object 
libqtf/CMakeFiles/qtf.dir/qtf_autogen/mocs_compilation.cpp.o
  [...]
  In file included from /usr/include/telepathy-qt5/TelepathyQt/types.h:30,
   from /usr/include/telepathy-qt5/TelepathyQt/Types:8,
   from 
/usr/include/telepathy-qt5/TelepathyQt/_gen/cli-channel.h:12,
   from /usr/include/telepathy-qt5/TelepathyQt/channel.h:30,
   from /usr/include/telepathy-qt5/TelepathyQt/Channel:8,
   from 
/usr/include/telepathy-qt5/TelepathyQt/call-channel.h:29,
   from /usr/include/telepathy-qt5/TelepathyQt/CallChannel:8,
   from 
/<>/obj-x86_64-linux-gnu/libqtf/qtf_autogen/EWIEGA46WW/../../../../libqtf/qtf.h:29,
   from 
/<>/obj-x86_64-linux-gnu/libqtf/qtf_autogen/EWIEGA46WW/moc_qtf.cpp:9,
   from 
/<>/obj-x86_64-linux-gnu/libqtf/qtf_autogen/mocs_compilation.cpp:2:
  /usr/include/telepathy-qt5/TelepathyQt/_gen/types.h:15:10: fatal error: 
QDBusArgument: No such file or directory
 15 | #include 
|  ^~~
  compilation terminated.

The full build log can be seen here:
https://buildd.debian.org/status/fetch.php?pkg=ktp-call-ui=amd64=17.08.3-1%2Bb2=1578708417=0

Feel free to reassign to libtelepathy-qt5-dev if needed.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#938625: marked as done (tap.py: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 17:04:41 +
with message-id 
and subject line Bug#938625: fixed in tap.py 2.6.2-3
has caused the Debian Bug report #938625,
regarding tap.py: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:tap.py

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: tap.py
Source-Version: 2.6.2-3

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2020 11:45:47 -0500
Source: tap.py
Architecture: source
Version: 2.6.2-3
Distribution: unstable
Urgency: medium
Maintainer: Python Modules Team 
Changed-By: Sandro Tosi 
Closes: 938625
Changes:
 tap.py (2.6.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #938625
Checksums-Sha1:
 6d8ab05e9dc1d3883416f9dbf9ad30d77d025234 2401 tap.py_2.6.2-3.dsc
 945eebd2ed07badf7e8f1ae9a3647b3c9936f2d5 7328 tap.py_2.6.2-3.debian.tar.xz
 2b533e15ff0a14e1e6f1014173463d548ff469c3 7383 tap.py_2.6.2-3_source.buildinfo
Checksums-Sha256:
 aae32ec571e47642b67b2b5f4cfa071bca255eb2e55ca5f5a6cda675d11a35d3 2401 
tap.py_2.6.2-3.dsc
 6ae11ea1c2cedb85350b99905766ce4faf787bbb35514532ca8c9a07640a879d 7328 
tap.py_2.6.2-3.debian.tar.xz
 df39b02b12f3bd055d2d33394a61697c5fbba11e531d032a6c40972aa10b25aa 7383 
tap.py_2.6.2-3_source.buildinfo
Files:
 d01d73071c62d3f47ea6049424fbf469 2401 python optional tap.py_2.6.2-3.dsc
 a7a326ce4011da0cb8fee13c4a094ce7 7328 python 

Bug#938625: marked as pending in tap.py

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/tap.py/commit/c836e1e93170be01c3bea7eed3d3e2ea90dac98e


Drop python2 support; Closes: #938625


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938625

Processed: Bug#938625 marked as pending in tap.py

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938625 [src:tap.py] tap.py: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#948903: open-infrastructure-system-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

[Mattia Rizzolo]

Source: open-infrastructure-system-tools
Version: 20190301-lts1-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot.
Attached is the full build log, hopefully relevant excerpt follows:


   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/build/open-infrastructure-system-tools-20190301-lts1'
dh_auto_build
/usr/bin/make -C system-boot
make[2]: Entering directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-boot'
Nothing to build.
make[2]: Leaving directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-boot'
/usr/bin/make -C system-build
make[2]: Entering directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-build'
Nothing to build.
make[2]: Leaving directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-build'
/usr/bin/make -C system-config
make[2]: Entering directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-config'
Nothing to build.
make[2]: Leaving directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-config'
/usr/bin/make -C system-images
make[2]: Entering directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-images'
/usr/bin/make -C share/man
make[3]: Entering directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-images/share/man'
for FILE in *.txt; \
do \
a2x --asciidoc-opts "-a revdate=20161115" --doctype=manpage 
--format=manpage ${FILE}; \
done
usage: usage: a2x [OPTIONS] ASCIIDOC_FILE
a2x: error: argument --asciidoc-opts: expected one argument
make[3]: *** [Makefile:38: man] Error 2
make[3]: Leaving directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-images/share/man'
make[2]: *** [Makefile:26: build] Error 2
make[2]: Leaving directory 
'/build/open-infrastructure-system-tools-20190301-lts1/system-images'
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 2
make[1]: Leaving directory 
'/build/open-infrastructure-system-tools-20190301-lts1'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Tue Jan 14 15:21:01 UTC 2020
I: pbuilder-time-stamp: 1579015261
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/open-infrastructure-system-tools_20190301-lts1-1.dsc]
I: copying 
[pkgs/open-infrastructure-system-tools_20190301-lts1.orig.tar.xz]
I: copying 
[pkgs/open-infrastructure-system-tools_20190301-lts1-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Sat Mar  2 17:41:54 2019 UTC
gpgv:using RSA key 8136ED25C7D67E92C74A429255CF1BF986ABB9C7
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on 
./open-infrastructure-system-tools_20190301-lts1-1.dsc
dpkg-source: info: extracting open-infrastructure-system-tools in 
open-infrastructure-system-tools-20190301-lts1
dpkg-source: info: unpacking 
open-infrastructure-system-tools_20190301-lts1.orig.tar.xz
dpkg-source: info: unpacking 
open-infrastructure-system-tools_20190301-lts1-1.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/open-infrastructure-system-tools_20190301-lts1-1.dsc' 
to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  asciidoc asciidoc-base asciidoc-common autoconf automake autopoint
  autotools-dev bsdmainutils debhelper dh-autoreconf dh-strip-nondeterminism
  docbook-xml docbook-xsl dwz file gettext gettext-base groff-base
  intltool-debian libarchive-zip-perl libbsd0 libcroco3 libdebhelper-perl
  libelf1 libfile-stripnondeterminism-perl libglib2.0-0 libmagic-mgc libmagic1
  libmpdec2 libpipeline1 libpython3-stdlib libpython3.7-minimal
  libpython3.7-stdlib libsigsegv2 libsub-override-perl libtool libuchardet0
  libxml2-utils m4 man-db po-debconf python3 python3-minimal python3.7
  python3.7-minimal sensible-utils sgml-base sgml-data xml-core
debconf: delaying package configuration, since apt-utils is not installed
0 upgraded, 49 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/17.2 MB of archives.
After this operation, 80.6 MB of additional disk space will be used.
Selecting previously unselected 

Bug#948902: open-infrastructure-storage-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

[Mattia Rizzolo]

Source: open-infrastructure-storage-tools
Version: 20190301-lts1-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot.
Attached is the full build log, hopefully relevant excerpt follows:

dh_auto_install -- 
DESTDIR=/build/open-infrastructure-storage-tools-20190301-lts1/debian/open-infrastructure-ceph-tools
make -j4 install 
DESTDIR=/build/open-infrastructure-storage-tools-20190301-lts1/debian/tmp 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" 
DESTDIR=/build/open-infrastructure-storage-tools-20190301-lts1/debian/open-infrastructure-ceph-tools
make[2]: Entering directory 
'/build/open-infrastructure-storage-tools-20190301-lts1'
make -C share/man
make[3]: Entering directory 
'/build/open-infrastructure-storage-tools-20190301-lts1/share/man'
for FILE in *.txt; \
do \
a2x --asciidoc-opts "-a revdate=20190301-lts1" --doctype=manpage 
--format=manpage ${FILE}; \
done
usage: usage: a2x [OPTIONS] ASCIIDOC_FILE
a2x: error: argument --asciidoc-opts: expected one argument
make[3]: *** [Makefile:37: man] Error 2
make[3]: Leaving directory 
'/build/open-infrastructure-storage-tools-20190301-lts1/share/man'
make[2]: *** [Makefile:55: build] Error 2
make[2]: Leaving directory 
'/build/open-infrastructure-storage-tools-20190301-lts1'
dh_auto_install: make -j4 install 
DESTDIR=/build/open-infrastructure-storage-tools-20190301-lts1/debian/tmp 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" 
DESTDIR=/build/open-infrastructure-storage-tools-20190301-lts1/debian/open-infrastructure-ceph-tools
 returned exit code 2
make[1]: *** [debian/rules:12: override_dh_auto_install] Error 255
make[1]: Leaving directory 
'/build/open-infrastructure-storage-tools-20190301-lts1'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Tue Jan 14 15:20:40 UTC 2020
I: pbuilder-time-stamp: 1579015240
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/open-infrastructure-storage-tools_20190301-lts1-1.dsc]
I: copying 
[pkgs/open-infrastructure-storage-tools_20190301-lts1.orig.tar.xz]
I: copying 
[pkgs/open-infrastructure-storage-tools_20190301-lts1-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Sat Mar  2 18:54:04 2019 UTC
gpgv:using RSA key 8136ED25C7D67E92C74A429255CF1BF986ABB9C7
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on 
./open-infrastructure-storage-tools_20190301-lts1-1.dsc
dpkg-source: info: extracting open-infrastructure-storage-tools in 
open-infrastructure-storage-tools-20190301-lts1
dpkg-source: info: unpacking 
open-infrastructure-storage-tools_20190301-lts1.orig.tar.xz
dpkg-source: info: unpacking 
open-infrastructure-storage-tools_20190301-lts1-1.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/open-infrastructure-storage-tools_20190301-lts1-1.dsc' 
to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  apache2-dev asciidoc asciidoc-base asciidoc-common autoconf automake
  autopoint autotools-dev bsdmainutils debhelper dh-autoreconf
  dh-strip-nondeterminism docbook-xml docbook-xsl dwz file gettext
  gettext-base groff-base intltool-debian libapr1 libapr1-dev libaprutil1
  libaprutil1-dev libarchive-zip-perl libbsd0 libcroco3 libdebhelper-perl
  libelf1 libexpat1-dev libfile-stripnondeterminism-perl libglib2.0-0
  libldap-2.4-2 libldap-common libldap2-dev libmagic-mgc libmagic1 libmpdec2
  libpipeline1 libpython3-stdlib libpython3.7-minimal libpython3.7-stdlib
  libsasl2-2 libsasl2-modules-db libsctp-dev libsctp1 libsigsegv2
  libsub-override-perl libtool libuchardet0 libxml2-utils m4 man-db openssl
  po-debconf python3 python3-minimal python3.7 python3.7-minimal
  sensible-utils sgml-base sgml-data uuid-dev xml-core
debconf: delaying package configuration, since apt-utils is not installed
0 upgraded, 64 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/20.8 MB of archives.
After this operation, 101 MB of additional disk space will be used.
Selecting previously unselected package libbsd0:amd64.
(Reading database ... 
(Reading database ... 5%

Bug#948901: open-infrastructure-service-tools: FTBFS: a2x: error: argument --asciidoc-opts: expected one argument

[Mattia Rizzolo]

Source: open-infrastructure-service-tools
Version: 20190301-lts1-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot.
Attached is the full build log, hopefully relevant excerpt follows:

dh_auto_install -- 
DESTDIR=/build/open-infrastructure-service-tools-20190301-lts1/debian/open-infrastructure-apache-tools
make -j4 install 
DESTDIR=/build/open-infrastructure-service-tools-20190301-lts1/debian/tmp 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" 
DESTDIR=/build/open-infrastructure-service-tools-20190301-lts1/debian/open-infrastructure-apache-tools
make[2]: Entering directory 
'/build/open-infrastructure-service-tools-20190301-lts1'
make -C share/man
make[3]: Entering directory 
'/build/open-infrastructure-service-tools-20190301-lts1/share/man'
for FILE in *.txt; \
do \
a2x --asciidoc-opts "-a revdate=20190301-lts1" --doctype=manpage 
--format=manpage ${FILE}; \
done
usage: usage: a2x [OPTIONS] ASCIIDOC_FILE
a2x: error: argument --asciidoc-opts: expected one argument
make[3]: *** [Makefile:37: man] Error 2
make[3]: Leaving directory 
'/build/open-infrastructure-service-tools-20190301-lts1/share/man'
make[2]: *** [Makefile:27: build] Error 2
make[2]: Leaving directory 
'/build/open-infrastructure-service-tools-20190301-lts1'
dh_auto_install: make -j4 install 
DESTDIR=/build/open-infrastructure-service-tools-20190301-lts1/debian/tmp 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" 
DESTDIR=/build/open-infrastructure-service-tools-20190301-lts1/debian/open-infrastructure-apache-tools
 returned exit code 2
make[1]: *** [debian/rules:12: override_dh_auto_install] Error 255
make[1]: Leaving directory 
'/build/open-infrastructure-service-tools-20190301-lts1'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Tue Jan 14 15:20:14 UTC 2020
I: pbuilder-time-stamp: 1579015214
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/open-infrastructure-service-tools_20190301-lts1-1.dsc]
I: copying 
[pkgs/open-infrastructure-service-tools_20190301-lts1.orig.tar.xz]
I: copying 
[pkgs/open-infrastructure-service-tools_20190301-lts1-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Sat Mar  2 15:11:35 2019 UTC
gpgv:using RSA key 8136ED25C7D67E92C74A429255CF1BF986ABB9C7
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on 
./open-infrastructure-service-tools_20190301-lts1-1.dsc
dpkg-source: info: extracting open-infrastructure-service-tools in 
open-infrastructure-service-tools-20190301-lts1
dpkg-source: info: unpacking 
open-infrastructure-service-tools_20190301-lts1.orig.tar.xz
dpkg-source: info: unpacking 
open-infrastructure-service-tools_20190301-lts1-1.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/open-infrastructure-service-tools_20190301-lts1-1.dsc' 
to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  apache2-dev asciidoc asciidoc-base asciidoc-common autoconf automake
  autopoint autotools-dev bsdmainutils debhelper dh-autoreconf
  dh-strip-nondeterminism docbook-xml docbook-xsl dwz file fontconfig
  fontconfig-config fonts-dejavu-core gettext gettext-base groff-base
  hicolor-icon-theme imagemagick imagemagick-6-common imagemagick-6.q16
  intltool-debian libapr1 libapr1-dev libaprutil1 libaprutil1-dev
  libarchive-zip-perl libbsd0 libcairo2 libcroco3 libdatrie1 libde265-0
  libdebhelper-perl libelf1 libexpat1-dev libfftw3-double3
  libfile-stripnondeterminism-perl libfontconfig1 libfreetype6 libfribidi0
  libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libglib2.0-0 libgraphite2-3
  libharfbuzz0b libheif1 libjbig0 libjpeg62-turbo liblcms2-2 libldap-2.4-2
  libldap-common libldap2-dev liblqr-1-0 libltdl7 libmagic-mgc libmagic1
  libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmpdec2 libnuma1 libopenjp2-7
  libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpipeline1
  libpixman-1-0 libpng16-16 libpython3-stdlib libpython3.7-minimal
  libpython3.7-stdlib librsvg2-2 librsvg2-bin libsasl2-2 libsasl2-modules-db
  libsctp-dev libsctp1 libsigsegv2 

Bug#925629: aghermann: ftbfs with GCC-9

[andrei zavada]

> what is the canonical upstream source for this project?
It would be https://gitlab.com/hmmr/aghermann. I'll amend the links on
my page shortly.

On Tue, 14 Jan 2020 at 17:51, Matthew Fernandez
 wrote:
>
> Thanks for being clear, Andrei. And thanks for your work building and 
> maintaining this package.
>
> I jumped into this thread knowing nothing about this package but merely 
> recognizing a compiler error. Now that I look up what it does, I don’t have 
> the necessary background to fully understand its functionality. It does look 
> like it’s still seeing some usage in Debian though [0]. I’m comfortable with 
> C++, so Andreas, if you still want to proceed with the packaging work, I’m 
> happy to review your changes.
>
> By the way, what is the canonical upstream source for this project? All the 
> repo links on the homepage [1] except SourceForge are broken and I assume no 
> one is using SourceForge these days.
>
>   [0]: https://qa.debian.org/popcon.php?package=aghermann
>   [1]: http://johnhommer.com/academic/code/aghermann/

Processed: your mail

[Debian Bug Tracking System]

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

> severity 948867 serious
Bug #948867 [gst-plugins-base1.0] The dev shoulds depends on libx11-xcb-dev
Severity set to 'serious' from 'normal'
> retitle 948867 gst-plugins-base1.0 FTBFS: dpkg-gensymbols: error: some 
> symbols or patterns disappeared in the symbols file
Bug #948867 [gst-plugins-base1.0] The dev shoulds depends on libx11-xcb-dev
Changed Bug title to 'gst-plugins-base1.0 FTBFS: dpkg-gensymbols: error: some 
symbols or patterns disappeared in the symbols file' from 'The dev shoulds 
depends on libx11-xcb-dev'.
> thanks
Stopping processing here.

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

Bug#936488: epylog: Python2 removal in sid/bullseye

[Tiago Bortoletto Vaz]

On 2020-01-14 10:13, Stuart Prescott wrote:
> This package appears to be dead upstream (upstream URL doesn't work and I 
> can't find it anywhere else).
> 
> With a low popcon (inst: 9), perhaps it's time to remove this package.

Indeed. I've asked for removal:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948896

Bests,

-- 
tiago

Bug#948897: Subject: openbios: FTBFS: error: taking address of packed member of 'struct ' may result in an unaligned pointer value

[Mattia Rizzolo]

Source: openbios
Version: 1.1.git20181001-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot:


powerpc-linux-gnu-gcc $EXTRACFLAGS -m32 -mcpu=604 -msoft-float 
-fno-builtin-bcopy -fno-builtin-log2 -Os -g 
-DNATIVE_BITWIDTH_EQUALS_HOST_BITWIDTH -USWAP_ENDIANNESS -Wall 
-Wredundant-decls -Wshadow -Wpointer-arith -Wstrict-prototypes 
-Wmissing-declarations -Wundef -Wendif-labels -Wstrict-aliasing -Wwrite-strings 
-Wmissing-prototypes -Wnested-externs -Werror -MMD -MP -MT 
target/drivers/usbohci.o -MF 'target/drivers/usbohci.d' 
-I/build/1st/openbios-1.1.git20181001/include 
-I/build/1st/openbios-1.1.git20181001/kernel/include -I./target/include -c -o 
target/drivers/usbohci.o /build/1st/openbios-1.1.git20181001/drivers/usbohci.c
In file included from /build/1st/openbios-1.1.git20181001/drivers/usbohci.c:43:
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c: In function 'ohci_init':
/build/1st/openbios-1.1.git20181001/drivers/usbohci_private.h:259:31: error: 
taking address of packed member of 'struct ' may result in an 
unaligned pointer value [-Werror=address-of-packed-member]
  259 | #define OHCI_INST(controller) ((ohci_t*)((controller)->instance))
  |   ^
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c:235:26: note: in 
expansion of macro 'OHCI_INST'
  235 |  u32 *const intr_table = 
OHCI_INST(controller)->hcca->HccaInterruptTable;
  |  ^
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c: In function 
'ohci_create_intr_queue':
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c:701:26: error: taking 
address of packed member of 'struct ' may result in an unaligned 
pointer value [-Werror=address-of-packed-member]
  701 |  u32 *const intr_table = ohci->hcca->HccaInterruptTable;
  |  ^~~~
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c: In function 
'ohci_destroy_intr_queue':
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c:732:26: error: taking 
address of packed member of 'struct ' may result in an unaligned 
pointer value [-Werror=address-of-packed-member]
  732 |  u32 *const intr_table = ohci->hcca->HccaInterruptTable;
  |  ^~~~
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c: In function 
'ohci_process_done_queue':
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c:838:4: error: converting 
a packed 'td_t' {aka 'volatile struct '} pointer (alignment 1) to a 
'intrq_td_t' {aka 'struct _intrq_td'} pointer (alignment 4) may result in an 
unaligned pointer value [-Werror=address-of-packed-member]
  838 |intrq_td_t *const td = INTRQ_TD_FROM_TD(done_td);
  |^~
/build/1st/openbios-1.1.git20181001/drivers/usbohci.c:605:8: note: defined here
  605 | struct _intrq_td {
  |^
cc1: all warnings being treated as errors
make[2]: *** [rules.mak:233: target/drivers/usbohci.o] Error 1
make[2]: Leaving directory '/build/1st/openbios-1.1.git20181001/obj-ppc'
make[1]: *** [debian/rules:25: obj-ppc/.built] Error 2
make[1]: Leaving directory '/build/1st/openbios-1.1.git20181001'
make: *** [debian/rules:18: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#925629: aghermann: ftbfs with GCC-9

[Matthew Fernandez]

Thanks for being clear, Andrei. And thanks for your work building and 
maintaining this package.

I jumped into this thread knowing nothing about this package but merely 
recognizing a compiler error. Now that I look up what it does, I don’t have the 
necessary background to fully understand its functionality. It does look like 
it’s still seeing some usage in Debian though [0]. I’m comfortable with C++, so 
Andreas, if you still want to proceed with the packaging work, I’m happy to 
review your changes.

By the way, what is the canonical upstream source for this project? All the 
repo links on the homepage [1] except SourceForge are broken and I assume no 
one is using SourceForge these days.

  [0]: https://qa.debian.org/popcon.php?package=aghermann 

  [1]: http://johnhommer.com/academic/code/aghermann/

Processed: py2removal bugs severity updates - 2020-01-14 15:36:07.932268+00:00

[Debian Bug Tracking System]

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

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

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

Bug#948895: neomutt: FTBFS: test failure

[Mattia Rizzolo]

Source: neomutt
Version: 2019+dfsg.1-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot:

test/neomutt-test
Test test_mutt_addr_cat...  [ OK ]
Test test_mutt_addr_cmp...  [ OK ]
Test test_mutt_addr_copy... [ OK ]
...
Test test_mutt_date_gmtime...   [ OK ]
Test test_mutt_date_is_day_name...  [ OK ]
Test test_mutt_date_localtime...[ FAILED ]
  Case December, 2000:
mutt_date_localtime.c:36: Check tm.tm_hour == 12... failed
  Case June, 2000:
mutt_date_localtime.c:48: Check (tm.tm_hour == 12) || (tm.tm_hour == 11)... 
failed
  hour = 23
mutt_date_localtime.c:51: Check tm.tm_mday == 25... failed
mutt_date_localtime.c:54: Check tm.tm_wday == 0... failed
mutt_date_localtime.c:55: Check tm.tm_yday == 176... failed
  Case Today:
mutt_date_localtime.c:61: Check tm.tm_yday >= 119... failed
Test test_mutt_date_localtime_format... [ FAILED ]
  mutt_date_localtime_format.c:49: Check result == true... failed
Test test_mutt_date_local_tz... [ OK ]
Test test_mutt_date_make_date...[ OK ]
Test test_mutt_date_make_imap...[ FAILED ]
  mutt_date_make_imap.c:43: Check result == true... failed
Test test_mutt_date_make_time...[ FAILED ]
  Case {0,0,0,1,0,1,0} = 9223372036854775807:
mutt_date_make_time.c:74: Check result == 946684800... failed
Test test_mutt_date_make_tls... [ OK ]
Test test_mutt_date_normalize_time...   [ OK ]
Test test_mutt_date_parse_date...   [ OK ]
...
Test test_url_tobuffer...   [ OK ]
Test test_url_tostring...   [ OK ]
FAILED: 4 of 377 unit tests have failed.
make[1]: *** [Makefile:1150: test] Error 1
make[1]: Leaving directory 
'/build/1st/neomutt-2019+dfsg.1/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j15 test VERBOSE=1 returned exit 
code 2
make: *** [debian/rules:20: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#936488: epylog: Python2 removal in sid/bullseye

[Stuart Prescott]

This package appears to be dead upstream (upstream URL doesn't work and I 
can't find it anywhere else).

With a low popcon (inst: 9), perhaps it's time to remove this package.

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Processed: limit source to python-pyknon, tagging 938072

[Debian Bug Tracking System]

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

> limit source python-pyknon
Limiting to bugs with field 'source' containing at least one of 'python-pyknon'
Limit currently set to 'source':'python-pyknon'

> tags 938072 + pending
Bug #938072 [src:python-pyknon] python-pyknon: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#948422: marked as done (python-pint ftbfs with Python 3.8)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 14:44:05 +
with message-id 
and subject line Bug#948422: fixed in python-pint 0.10.1-1
has caused the Debian Bug report #948422,
regarding python-pint ftbfs with Python 3.8
to be marked as done.

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

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


-- 
948422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pint
Version: 0.9-2
Severity: serious
Tags: sid bullseye

in unstable:

[...]
==
ERROR: test_nonnumeric_magnitudes
(pint.testsuite.test_quantity.TestQuantityToCompact)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_pint/build/pint/testsuite/test_quantity.py",
line 419, in test_nonnumeric_magnitudes
self.assertRaises(RuntimeError, self.compareQuantity_compact(x,x))
  File "/usr/lib/python3.8/unittest/case.py", line 816, in assertRaises
return context.handle('assertRaises', args, kwargs)
  File "/usr/lib/python3.8/unittest/case.py", line 202, in handle
callable_obj(*args, **kwargs)
TypeError: 'NoneType' object is not callable

--
Ran 802 tests in 26.214s

FAILED (SKIP=17, errors=1)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.8_pint/build; python3.8 -m nose -v
dh_auto_test: pybuild --test --test-nose -i python{version} -p "3.8 3.7"
returned exit code 13
make: *** [debian/rules:6: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: python-pint
Source-Version: 0.10.1-1

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

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

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-pint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 Jan 2020 13:49:58 +0100
Source: python-pint
Architecture: source
Version: 0.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Closes: 948422
Changes:
 python-pint (0.10.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #948422).
   * Bump Standards-Version to 4.4.1.
   * Rebase patches.
   * Bump debhelper compat level to 12 and use debhelper-compat
   * Add python3-setuptools-scm to B-D.
   * Add python3-nbsphinx and pandoc to B-D-I.
   * Switch from nose to pytest (same as upstream).
   * d/copyright: Fix for new upstream release.
Checksums-Sha1:
 d7d1f2a6513eb398715bdc445b774374feada959 2295 python-pint_0.10.1-1.dsc
 b22d6e6640d629291e17d70c443c05569617ffd5 241277 python-pint_0.10.1.orig.tar.gz
 9f95d8f0204c0c96dd2dd601c8aaa7f11af4f6be 5948 
python-pint_0.10.1-1.debian.tar.xz
 41d3a3d6f97561d9842476d0bc5f695fe664c230 9567 
python-pint_0.10.1-1_amd64.buildinfo
Checksums-Sha256:
 f94f87f83fd7cd98b53641955754b7e514846d6d9fef7b481acd6a79c69f8321 2295 
python-pint_0.10.1-1.dsc
 a5bf18700a088b3da450c0ea103bd957f68cc7e67f30993b3f707b4b05a9cc05 241277 
python-pint_0.10.1.orig.tar.gz
 e708678c3d74440fb8db4f6a8c379b135660222764c1a72e29ed48e92688 5948 
python-pint_0.10.1-1.debian.tar.xz
 1ce92e927fe4359bc045eae16c54f6843eadf364b74a102ad89bd07ec9918a9f 9567 
python-pint_0.10.1-1_amd64.buildinfo
Files:
 08a3b2ec91015e2d614d1cc667101e9f 2295 python optional python-pint_0.10.1-1.dsc
 966176338bbe31e3f0182a4fe35b6ea3 241277 python optional 
python-pint_0.10.1.orig.tar.gz
 8bb8f2df5a66d066356c7f00497c80a9 5948 python optional 
python-pint_0.10.1-1.debian.tar.xz
 66ac441c103cf81cb2b45e50d11ab246 9567 python optional 
python-pint_0.10.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl4dyVsACgkQNXMSVZ0e
BksJRA//fAMbpmoqTSatve+EVVy1xoCf/jqRSpdjbAX4fN7W/bNy2BGgny5/gtUy
ylSlOw0lnBnQWa8bGDfT0mMy2FaRfAx0jnFll1PCTfD7lhs00kjeNWsYXxYx4Us/

Bug#947573: Nuitka and scons

[Kay Hayen]

Hello,

Nuitka is very much ported to Python3 for a long time. I have done the
changes to the packaging, which remove Python2 dependencies for Bullseye
and Sid, but I wanted to keep the packaging working for Wheezy and higher,
so this took more time.

Nuitka has been not building due to rst2pdf failures for 4 months prior to
this, only very recently this build dependency was fixed. Scons was never
blocking, since Nuitka doesn't care about it.

My debian Sid builds of Nuitka still seem to pull in scons and python2 with
it, but I trust that nothing of scons really matters to me there. Note that
Nuitka is used with Python3 scons a lot for years now.

Question fro me: I am also upstream of the package. Do we need a
pre-release of Nuitka right now? Or would be be OK if I continue upstream
work for 1-2 weeks more, and make this a more complete release, where I
also cover a few more open points of Python 3.8 compatibility? Otherwise I
could also (ask my sponsor to) upload in 2-3 days.

Best regards,
Kay

Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

On 20/01/14 02:03, Michael Crusoe wrote:
> On Wed, 27 Nov 2019 16:00:05 +0200 Povilas Kanapickas 
> wrote:
> > On 11/27/19 1:19 PM, Michael Crusoe wrote:
> > > Maybe this patch from Ubuntu will help?
> > >
> http://patches.ubuntu.com/c/cppreference-doc/cppreference-doc_20170409-1.1ubuntu1.patch
> >
> > Hi,
> >
> > I will look into this bug ASAP. Couldn't do this so far due to lack of
> > time due to my work.
> 
> I've tested the patch and it works in a pbuilder chroot. Here's a pull
> request for it: https://github.com/p12tic/cppreference-doc_debian/pull/5
> 
> It would be great to get this fixed soon, the new seqan3 package build-deps
> on cppreference-doc and I'd like to see that migrate to testing.

Indeed the patch looks pretty fine.

Povilas: I'll NMU the package in ~3 days if we get no reply from you, or even 
sooner if you allow me to do it.

Michael: please feel free to ping me in ~3 days.

Cheers, Lisandro.

Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.

[Michael Crusoe]

On Wed, 27 Nov 2019 16:00:05 +0200 Povilas Kanapickas 
wrote:
> On 11/27/19 1:19 PM, Michael Crusoe wrote:
> > Maybe this patch from Ubuntu will help?
> >
http://patches.ubuntu.com/c/cppreference-doc/cppreference-doc_20170409-1.1ubuntu1.patch
>
> Hi,
>
> I will look into this bug ASAP. Couldn't do this so far due to lack of
> time due to my work.

I've tested the patch and it works in a pbuilder chroot. Here's a pull
request for it: https://github.com/p12tic/cppreference-doc_debian/pull/5

It would be great to get this fixed soon, the new seqan3 package build-deps
on cppreference-doc and I'd like to see that migrate to testing.

Thanks for all your work!