Bug#955555: gitlab: uninitialized constant APIGuard
Hi I told you that in amd64 The problem is that I cannot upgrade to experimental(12.8.8-3) because there are missing ruby packages on amd64 You solved https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955202 but not https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955197. root@a:~# apt install gitlab/experimental Reading package lists... Done Building dependency tree Reading state information... Done Selected version '12.8.8-4' (Debian:experimental [all]) for 'gitlab' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gitlab : Depends: ruby-unicode-plot but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@a:~# apt-show-versions -a ruby-unicode-plot No oldstable version No stable version No testing version No testing-updates version ruby-unicode-plot:all 0.0.4-1 unstable ftp.debian.org No experimental version ruby-unicode-plot:all not installed root@a:~# apt install ruby-unicode-plot Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ruby-unicode-plot : Depends: ruby-enumerable-statistics (>= 2.0.1) but it is not installable E: Unable to correct problems, you have held broken packages. root@a:~# apt-show-versions -a ruby-enumerable-statistics ruby-enumerable-statistics not installed (not available) More, now redmine is uninstalled because of ruby-actionpack-xml-parser. Thx, Dragos Jarca On 02.04.2020 19:35, Pirate Praveen wrote: Control: fixed -1 12.8.6-1 On 2020, ഏപ്രിൽ 2 8:05:53 PM IST, Dragos Jarca wrote: Package: gitlab Version: 12.6.8-3 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, I upgraded packages: Start-Date: 2020-04-02 10:00:27 Commandline: apt-get dist-upgrade Install: libllvm10:amd64 (1:10.0.0-1, automatic), ruby-sync:amd64 (0.5.0-2, automatic) Upgrade: libpython3.7-minimal:amd64 (3.7.7-1, 3.7.7-1+b1), python3-werkzeug:amd64 (0.16.1+dfsg1-1, 0.16.1+dfsg1-2), glib-networking-services:amd64 (2.64.0-1, 2.64.1-1), libpython3.8-dbg:amd64 (3.8.2-1, 3.8.2-1+b1), libpython3.8-dev:amd64 (3.8.2-1, 3.8.2-1+b1), php-phpseclib:amd64 (2.0.25-1, 2.0.26-1), libgirepository-1.0-1:amd64 (1.62.0-5+b1, 1.64.0-2), libpython3.8-minimal:amd64 (3.8.2-1, 3.8.2-1+b1), glib-networking:amd64 (2.64.0-1, 2.64.1-1), dash:amd64 (0.5.10.2-6, 0.5.10.2-7), ruby-memoist:amd64 (0.16.2-1, 0.16.2-2), ruby-tins:amd64 (1.1.0-1, 1.1.0-2), libhiredis0.14:amd64 (0.14.0-6, 0.14.1-1), libffi-dev:amd64 (3.3-3, 3.3-4), libdbd-pg-perl:amd64 (3.10.4-1, 3.10.5-1), yarnpkg:amd64 (1.19.1-1, 1.21.1-2), nodejs:amd64 (10.17.0~dfsg-2, 10.19.0~dfsg-3), libpython3.8:amd64 (3.8.2-1, 3.8.2-1+b1), python3.7:amd64 (3.7.7-1, 3.7.7-1+b1), python3.8:amd64 (3.8.2-1, 3.8.2-1+b1), ruby-mini-magick:amd64 (4.9.2-1.1, 4.9.5-2), bubblewrap:amd64 (0.4.0-1, 0.4.1-1), node-d3-quadtree:amd64 (1.0.6-2, 1.0.7-1), libpq5:amd64 (12.2-1+b1, 12.2-4), libpython3.7-stdlib:amd64 (3.7.7-1, 3.7.7-1+b1), glib-networking-common:amd64 (2.64.0-1, 2.64.1-1), python3.7-minimal:amd64 (3.7.7-1, 3.7.7-1+b1), ruby-state-machines-activemodel:amd64 (0.5.1-3, 0.7.1-2), libpq-dev:amd64 (12.2-1+b1, 12.2-4), npm:amd64 (6.14.2+ds-2, 6.14.3+ds-1), python3-future:amd64 (0.18.2-1, 0.18.2-2), postgresql-12:amd64 (12.2-1+b1, 12.2-4), gir1.2-glib-2.0:amd64 (1.62.0-5+b1, 1.64.0-2), python3.8-minimal:amd64 (3.8.2-1, 3.8.2-1+b1), python3-acme:amd64 (1.1.0-1, 1.3.0-2), libconfuse-common:amd64 (3.2.2+dfsg-1, 3.2.2+dfsg-2), ruby-omniauth:amd64 (1.9.0-1, 1.9.1-1), shared-mime-info:amd64 (1.10-1, 1.15-1), libnode-dev:amd64 (10.17.0~dfsg-2, 10.19.0~dfsg-3), libwnck-3-0:amd64 (3.32.0-1, 3.36.0-1), ruby-warden:amd64 (1.2.3-2, 1.2.8-1), libpython3.8-stdlib:amd64 (3.8.2-1, 3.8.2-1+b1), libnode64:amd64 (10.17.0~dfsg-2, 10.19.0~dfsg-3), libwnck-3-common:amd64 (3.32.0-1, 3.36.0-1), libpcap0.8:amd64 (1.9.1-2, 1.9.1-3), libffi7:amd64 (3.3-3, 3.3-4), python3.8-dbg:amd64 (3.8.2-1, 3.8.2-1+b1), python3.8-dev:amd64 (3.8.2-1, 3.8.2-1+b1), libconfuse2:amd64 (3.2.2+dfsg-1, 3.2.2+dfsg-2), postgresql-client-12:amd64 (12.2-1+b1, 12.2-4) End-Date: 2020-04-02 10:05:57 Start-Date: 2020-04-02 10:14:16 Commandline: apt-get -t unstable install gitlab-shell Upgrade: gitlab-shell:amd64 (10.3.0+debian-3.1, 11.0.0+debian-2) End-Date: 2020-04-02 10:14:37 After that gitlab stop starting. The error is: rake aborted! NameError: uninitialized constant APIGuard
Bug#955544: marked as done (capnproto: FTBFS on s390x)
Your message dated Fri, 03 Apr 2020 05:33:28 +
with message-id
and subject line Bug#955544: fixed in capnproto 0.7.0-6
has caused the Debian Bug report #955544,
regarding capnproto: FTBFS on s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
955544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: capnproto
Version: 0.7.0-5
Severity: serious
Tags: patch upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
capnproto 0.7.0-5 failed to build in Ubuntu Focal on s390x:
https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1870055
In an upstream issue:
https://github.com/capnproto/capnproto/issues/962
They pointed at a fix:
https://github.com/capnproto/capnproto/pull/761
The attached patch is that fix.
-- System Information:
Debian Release: bullseye/sid
APT prefers focal-security
APT policy: (500, 'focal-security'), (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-21-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.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 capnproto depends on:
ii libc6 2.31-0ubuntu6
pn libcapnp-0.7.0
ii libgcc-s1 10-20200324-1ubuntu1
ii libstdc++6 10-20200324-1ubuntu1
capnproto recommends no packages.
capnproto suggests no packages.
commit ce4dd5a1031ee741c676daaea89ae3d1b19f2bb2
Author: David Renshaw
Date: Fri Nov 16 21:23:58 2018 -0500
initialize anonymous enums in isPlausiblyText() and isPlausiblyJson()
diff --git a/src/capnp/compiler/capnp.c++ b/c++/src/capnp/compiler/capnp.c++
index e39db556..8e8c459b 100644
--- a/src/capnp/compiler/capnp.c++
+++ b/src/capnp/compiler/capnp.c++
@@ -1377,7 +1377,7 @@ private:
}
Plausibility isPlausiblyText(kj::ArrayPtr prefix) {
-enum { PREAMBLE, COMMENT, BODY } state;
+enum { PREAMBLE, COMMENT, BODY } state = PREAMBLE;
for (char c: prefix.asChars()) {
switch (state) {
@@ -1427,7 +1427,7 @@ private:
}
Plausibility isPlausiblyJson(kj::ArrayPtr prefix) {
-enum { PREAMBLE, COMMENT, BODY } state;
+enum { PREAMBLE, COMMENT, BODY } state = PREAMBLE;
for (char c: prefix.asChars()) {
switch (state) {
--- End Message ---
--- Begin Message ---
Source: capnproto
Source-Version: 0.7.0-6
Done: tony mancill
We believe that the bug you reported is fixed in the latest version of
capnproto, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
tony mancill (supplier of updated capnproto package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 02 Apr 2020 21:15:54 -0700
Source: capnproto
Architecture: source
Version: 0.7.0-6
Distribution: unstable
Urgency: medium
Maintainer: Tom Lee
Changed-By: tony mancill
Closes: 955544
Changes:
capnproto (0.7.0-6) unstable; urgency=medium
.
* Apply patch for FTBFS on s390x (Closes: #955544)
Thank you to Michał Sawicz for the bug report and patch.
* Bump Standards-Version to 4.5.0
* Specify debhelper compat 12 via debhelper-compat dependency
* Specify "Rules-Requires-Root: no" in debian/control
Checksums-Sha1:
bb462bf69c4155184ea457aa867ed0d1a28c485e 2198 capnproto_0.7.0-6.dsc
ba848eab6fb15c5a92d1d006eb4c5e012f48fad2 9868 capnproto_0.7.0-6.debian.tar.xz
ef5976dbd18c6aae06c68c6e53b585c303611156 8511 capnproto_0.7.0-6_amd64.buildinfo
Checksums-Sha256:
5b0d895652ba8c238a79b6bbd20abb052ae0d6c8a3c38ec5445d4c4a5799a7fa 2198
capnproto_0.7.0-6.dsc
5e66706b94cc37a929a1671cb82d91cf8909abf1c5766c47f4f624dc6a420385 9868
capnproto_0.7.0-6.debian.tar.xz
82d3f211b75fd74d6306e3fe2e5c7e1cd8b72ec572627452271a634a9bc9063d 8511
capnproto_0.7.0-6_amd64.buildinfo
Files:
3ceeda7c07bb03e64aa3a6bb9ed5d0e2 2198 devel optional capnproto_0.7.0-6.dsc
Bug#937597: marked as done (python-backports-abc: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:57:18 + with message-id and subject line Bug#955529: Removed package(s) from unstable has caused the Debian Bug report #937597, regarding python-backports-abc: 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.) -- 937597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-backports-abc Version: 0.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:python-backports-abc 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.5-2+rm Dear submitter, as the package python-backports-abc 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/955529 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#885506: marked as done (yorick-yao: Depends on unmaintained pygtk)
Your message dated Fri, 03 Apr 2020 04:55:37 + with message-id and subject line Bug#955587: Removed package(s) from unstable has caused the Debian Bug report #885506, regarding yorick-yao: Depends on unmaintained pygtk 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.) -- 885506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yorick-yao Version: 5.4.0-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings (and gtk3). For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 5.4.0-1+rm Dear submitter, as the package yorick-yao 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/955587 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#945726: marked as done (yorick-yao: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:55:37 + with message-id and subject line Bug#955587: Removed package(s) from unstable has caused the Debian Bug report #945726, regarding yorick-yao: 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.) -- 945726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yorick-yao Version: 5.4.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 5.4.0-1+rm Dear submitter, as the package yorick-yao 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/955587 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#937124: marked as done (ndpmon: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:50:43 + with message-id and subject line Bug#955516: Removed package(s) from unstable has caused the Debian Bug report #937124, regarding ndpmon: 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.) -- 937124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ndpmon Version: 1.4.0-2.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:ndpmon 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.4.0-2.1+rm Dear submitter, as the package ndpmon 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/955516 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#937600: marked as done (python-backports-shutil-get-terminal-size: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:52:03 + with message-id and subject line Bug#955522: Removed package(s) from unstable has caused the Debian Bug report #937600, regarding python-backports-shutil-get-terminal-size: 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.) -- 937600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-backports-shutil-get-terminal-size Version: 1.0.0-5 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-backports-shutil-get-terminal-size 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.0-5+rm Dear submitter, as the package python-backports-shutil-get-terminal-size 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/955522 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#937701: marked as done (python-dingus: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:51:02 + with message-id and subject line Bug#955517: Removed package(s) from unstable has caused the Debian Bug report #937701, regarding python-dingus: 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.) -- 937701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-dingus Version: 0.3.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-dingus 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.4-1+rm Dear submitter, as the package python-dingus 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/955517 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#951861: marked as done (OpenSSL linking without license exception)
Your message dated Fri, 03 Apr 2020 04:50:43 + with message-id and subject line Bug#955516: Removed package(s) from unstable has caused the Debian Bug report #951861, regarding OpenSSL linking without license exception 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.) -- 951861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ndpmon Severity: serious This package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. Please replace libssl with a GPL compatible library. I successfully compiled with libwolfssl which has an OpenSSL API compatibility layer. --- End Message --- --- Begin Message --- Version: 1.4.0-2.1+rm Dear submitter, as the package ndpmon 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/955516 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#937777: marked as done (python-gasp: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:49:08 + with message-id and subject line Bug#955513: Removed package(s) from unstable has caused the Debian Bug report #93, regarding python-gasp: 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.) -- 93: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-gasp Version: 0.3.4-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:python-gasp 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.4-2+rm Dear submitter, as the package python-gasp 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/955513 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#890168: marked as done (python-gasp: Please switch to python-gobject-2/python-gi)
Your message dated Fri, 03 Apr 2020 04:49:08 + with message-id and subject line Bug#955513: Removed package(s) from unstable has caused the Debian Bug report #890168, regarding python-gasp: Please switch to python-gobject-2/python-gi 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.) -- 890168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-gasp Version: 0.3.4-2 Severity: important Tags: buster sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: pygobject-trans-rm Dear Maintainer, Your package python-gasp depends against the python-gobject transitional package. We would like to drop this transitional package for buster. Could you please switch to either python-gobject-2 (if your package is using the old python binding for GObject) or to python-gi (if your package is using the new gobject-introspection one). Please don't hesitate to contact me if you have any questions. Kind Regards, Laurent Bigonville --- End Message --- --- Begin Message --- Version: 0.3.4-2+rm Dear submitter, as the package python-gasp 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/955513 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#945694: marked as done (pwrkap: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:50:15 + with message-id and subject line Bug#955515: Removed package(s) from unstable has caused the Debian Bug report #945694, regarding pwrkap: 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.) -- 945694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pwrkap Version: 7.30-5 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 7.30-5+rm Dear submitter, as the package pwrkap 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/955515 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#937141: marked as done (nicotine: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:49:46 + with message-id and subject line Bug#955514: Removed package(s) from unstable has caused the Debian Bug report #937141, regarding nicotine: 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.) -- 937141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nicotine Version: 1.2.16+dfsg-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:nicotine 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.16+dfsg-1.1+rm Dear submitter, as the package nicotine 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/955514 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#945710: marked as done (neopi: Python2 removal in sid/bullseye)
Your message dated Fri, 03 Apr 2020 04:51:33 + with message-id and subject line Bug#955518: Removed package(s) from unstable has caused the Debian Bug report #945710, regarding neopi: 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.) -- 945710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: neopi Version: 0.0+git20120821.98-6 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.0+git20120821.98-6+rm Dear submitter, as the package neopi 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/955518 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#885357: marked as done (nicotine: Depends on unmaintained pygtk)
Your message dated Fri, 03 Apr 2020 04:49:46 + with message-id and subject line Bug#955514: Removed package(s) from unstable has caused the Debian Bug report #885357, regarding nicotine: Depends on unmaintained pygtk 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.) -- 885357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nicotine Version: 1.2.16+dfsg-1.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings (and gtk3). For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 1.2.16+dfsg-1.1+rm Dear submitter, as the package nicotine 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/955514 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#885363: marked as done (pwrkap-gui: Depends on unmaintained pygtk)
Your message dated Fri, 03 Apr 2020 04:50:15 + with message-id and subject line Bug#955515: Removed package(s) from unstable has caused the Debian Bug report #885363, regarding pwrkap-gui: Depends on unmaintained pygtk 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.) -- 885363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pwrkap-gui Version: 7.30-5 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings (and gtk3). For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 7.30-5+rm Dear submitter, as the package pwrkap 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/955515 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#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>
On Thu, Apr 2, 2020 at 8:06 AM James McCoy wrote: > Just as an FYI, the OpenSSL changes have been partially reverted[1] > upstream for the 1.1.1f release. The change will be re-introduced in > 3.0, so using the ifdef, instead of OpenSSL version, was the prudent > choice. > Thanks for the update. I'm guessing Debian Sid will just jump to OpenSSL 1.1.1f and we'll all pretend that 1.1.1e never happened. =) I think this takes some of the pressing nature to get a 1.3.10 out the door. That said, I'm trying to go down the rabbit hole of becoming friendly with all of the cmake environments...it'll probably take me a fair bit of time to get comfortable enough to cut a 1.4.x release that uses cmake as the primary build system. (I finally got my VS 2019 in a state tonight where it can now build the dependency chains...) Cheers. -- justin
Bug#955596: python-h5netcdf: h5py.File needs access mode specified
Source: python-h5netcdf Version: 0.7.1-1 Severity: serious Justification: debci h5py.File opens 'r' by default, so you need to specify other modes such as 'w' if needed e.g. test_optional_netcdf4_attrs[testfile.nc] with h5.File(tmp_local_or_remote_netcdf, 'w') as f: instead of with h5.File(tmp_local_or_remote_netcdf) as f: if needed for writing. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#955595: python-fabio: h5py.File needs access mode specified
Source: python-fabio
Version: 0.9.0+dfsg-4
Severity: serious
Justification: debci
h5py.File opens in 'r' mode by default. So you need to specify 'w' or
other if needed to write, etc.
e.g. /usr/lib/python3/dist-packages/fabio/nexus.py, line 140
self.h5 = h5py.File(self.filename.split("::")[0], 'w')
instead of
self.h5 = h5py.File(self.filename.split("::")[0])
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#954576: yt: 1
Source: yt Followup-For: Bug #954576 Not sure if it's the same bug as reported here, but yt needs to update its h5py interface (see debci test failures). Files are opened 'r' by default so you need to specify f = h5py.File(filename, 'w') instead of f = h5py.File(filename) if you want to open for writing. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#955535: Bug #955535: httping: flaky autopkgtest: PING google.com:80
Hi, The two different results are caused by different CI workers - some of our workers at ci.d.n does not have reliable network to public services, in this case to google.com:80, which makes the test result flaky. Would you mind to consider setting up something locally (a small web server) in testing environment to facilitate this test? If that's okay I can help to cook a patch. Regards, Aron
Bug#950112: gplaycli: 502 Bad Gateway, does not work at all
On Sat, 28 Mar 2020 09:10:49 +0800 Paul Wise wrote: > Control: tags -1 + fixed-upstream > > On Tue, 28 Jan 2020 23:50:24 +0100 Thorsten Glaser wrote: > > > After installation, gplaycli --help works (but please do add > > a manual page), but nothing else: > > The error is now different: > > $ gplaycli -d com.skype.raider > [ERROR] Unknown error: New version of protocol release. Update gplaycli and check https://github.com/matlink/gplaycli This error only happens if you're relying on tokens. If you disable tokens in /etc/gplaycli/gplaycli.conf, then the versions currently in sid and buster will work. Unfortunately, the token dispenser wasn't working for me again just now. I'm considering ways to make this fail nicely in such a way that it defaults to trying the token dispenser, but if that fails it provides instructions on adding a google login. > > There is a new upstream release that fixes this and the other errors, > please update to version 3.29: > > https://github.com/matlink/gplaycli/releases/tag/3.29 > > I also think that you should ask for removal of the package from Debian > earlier Debian releases, since it is very broken there now. > > https://www.debian.org/doc/manuals/developers-reference/developer-duties.en.html#maintain-packages-in-stable > >$ rmadison gplaycli >debian: >gplaycli | 0.2.1-1 | oldstable | source, all >gplaycli | 3.25+ds-1~bpo9+1 | stretch-backports | source, all >gplaycli | 3.25+ds-1| stable| source, all It does appear that even with tokens disabled and using a login, the version in stable doesn't work, with the server returning UNKNOWN_ERR. I guess I'll have to request removal from buster. I'm not too worried about stretch and the stretch-backports, as support will be dropped in ~3 months.. >gplaycli | 3.27+dfsg-1 | unstable | source, all > > You can request removal from stretch and buster by doing this: > > * run: `reportbug release.debian.org` > * select: 5 rm Stable/Testing removal requests > * enter the version: buster 3.25+ds-1, stretch 0.2.1-1 > * enter No specific architectures > * enter an explanation: Google Play API changes broke the tool > * send the bug report > > Repeat these steps for each of stretch and buster. > > For the stretch-backports suite I think you would need to send a mail > to the backports mailing list asking for it to be removed. > > https://backports.debian.org/Contribute/ > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise
Processed: closing 936040
Processing commands for cont...@bugs.debian.org: > # > https://tracker.debian.org/news/1114599/accepted-isc-kea-175-1-source-amd64-all-into-unstable-unstable/ > close 936040 1.7.5-1 Bug #936040 [src:isc-kea] isc-kea: CVE-2019-6472 CVE-2019-6473 CVE-2019-6474 Marked as fixed in versions isc-kea/1.7.5-1. Bug #936040 [src:isc-kea] isc-kea: CVE-2019-6472 CVE-2019-6473 CVE-2019-6474 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 936040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955583: ruby-defaults breaks ruby-mousetrap-rails autopkgtest: TypeError: no implicit conversion of String into Integer
Source: ruby-defaults, ruby-mousetrap-rails Control: found -1 ruby-defaults/1:2.7 Control: found -1 ruby-mousetrap-rails/1.4.6-6 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of ruby-defaults the autopkgtest of ruby-mousetrap-rails fails in testing when that autopkgtest is run with the binary packages of ruby-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-defaults from testing1:2.7 ruby-mousetrap-rails from testing1.4.6-6 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby-defaults to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-mousetrap-rails/4779223/log.gz Bundle complete! 19 Gemfile dependencies, 77 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. + bundle exec rake assets:precompile rake aborted! TypeError: no implicit conversion of String into Integer /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in `block in require' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:257:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in `require' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in `block in require' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:257:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in `require' /tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/boot.rb:4:in `require' /tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/boot.rb:4:in `' /tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/application.rb:1:in `require_relative' /tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/application.rb:1:in `' /tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/Rakefile:4:in `require_relative' /tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/Rakefile:4:in `' (See full trace by running task with --trace) signature.asc Description: OpenPGP digital signature
Processed: ruby-defaults breaks ruby-mousetrap-rails autopkgtest: TypeError: no implicit conversion of String into Integer
Processing control commands: > found -1 ruby-defaults/1:2.7 Bug #955583 [src:ruby-defaults, src:ruby-mousetrap-rails] ruby-defaults breaks ruby-mousetrap-rails autopkgtest: TypeError: no implicit conversion of String into Integer Marked as found in versions ruby-defaults/1:2.7. > found -1 ruby-mousetrap-rails/1.4.6-6 Bug #955583 [src:ruby-defaults, src:ruby-mousetrap-rails] ruby-defaults breaks ruby-mousetrap-rails autopkgtest: TypeError: no implicit conversion of String into Integer Marked as found in versions ruby-mousetrap-rails/1.4.6-6. -- 955583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955582: facter: autopkgtest needs update for new version of ruby-defaults: deprecation *warning* on stderr
Source: facter Version: 3.11.0-3 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-defaults [X-Debbugs-CC: debian...@lists.debian.org, ruby-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of ruby-defaults the autopkgtest of facter fails in testing when that autopkgtest is run with the binary packages of ruby-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-defaults from testing1:2.7 facter from testing3.11.0-3 all others from testingfrom testing I copied some of the output at the bottom of this report. I think the only issue that the autopkgtest is showing is that you're using a deprecated method. If you can't fix the code on the short term (best) or run the test suite without emitting warnings (a good thing to do anyways, autopkgtest isn't meant to catch those), please consider adding the allow-stderr restriction for the time being. Currently this regression is blocking the migration of ruby-defaults to testing [1]. Of course, ruby-defaults shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-defaults was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-defaults should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. 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=ruby-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/f/facter/4775724/log.gz autopkgtest [07:14:35]: test puppet: - - - - - - - - - - results - - - - - - - - - - puppet FAIL stderr: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete signature.asc Description: OpenPGP digital signature
Processed: facter: autopkgtest needs update for new version of ruby-defaults: deprecation *warning* on stderr
Processing control commands: > affects -1 src:ruby-defaults Bug #955582 [src:facter] facter: autopkgtest needs update for new version of ruby-defaults: deprecation *warning* on stderr Added indication that 955582 affects src:ruby-defaults -- 955582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tryton-server breaks tryton-modules-stock-supply autopkgtest: trytond.exceptions.UserError: You can not write in this document!
Processing control commands: > found -1 tryton-server/5.0.19-1 Bug #955580 [src:tryton-server, src:tryton-modules-stock-supply] tryton-server breaks tryton-modules-stock-supply autopkgtest: trytond.exceptions.UserError: You can not write in this document! Marked as found in versions tryton-server/5.0.19-1. > found -1 tryton-modules-stock-supply/5.0.4-1 Bug #955580 [src:tryton-server, src:tryton-modules-stock-supply] tryton-server breaks tryton-modules-stock-supply autopkgtest: trytond.exceptions.UserError: You can not write in this document! Marked as found in versions tryton-modules-stock-supply/5.0.4-1. -- 955580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955580: tryton-server breaks tryton-modules-stock-supply autopkgtest: trytond.exceptions.UserError: You can not write in this document!
Source: tryton-server, tryton-modules-stock-supply
Control: found -1 tryton-server/5.0.19-1
Control: found -1 tryton-modules-stock-supply/5.0.4-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of tryton-server the autopkgtest of
tryton-modules-stock-supply fails in testing when that autopkgtest is
run with the binary packages of tryton-server from unstable. It passes
when run with only packages from testing. In tabular form:
passfail
tryton-serverfrom testing5.0.19-1
tryton-modules-stock-supply from testing5.0.4-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of tryton-server to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=tryton-server
https://ci.debian.net/data/autopkgtest/testing/amd64/t/tryton-modules-stock-supply/4784547/log.gz
==
FAIL:
/usr/lib/python3/dist-packages/trytond/modules/stock_supply/tests/scenario_stock_supply_purchase_request.rst
Doctest: scenario_stock_supply_purchase_request.rst
--
Traceback (most recent call last):
File "/usr/lib/python3.8/doctest.py", line 2197, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for
scenario_stock_supply_purchase_request.rst
File
"/usr/lib/python3/dist-packages/trytond/modules/stock_supply/tests/scenario_stock_supply_purchase_request.rst",
line 0
--
File
"/usr/lib/python3/dist-packages/trytond/modules/stock_supply/tests/scenario_stock_supply_purchase_request.rst",
line 167, in scenario_stock_supply_purchase_request.rst
Failed example:
create_purchase = Wizard('purchase.request.create_purchase', [pr])
Exception raised:
Traceback (most recent call last):
File "/usr/lib/python3.8/doctest.py", line 1329, in __run
exec(compile(example.source, filename, "single",
File "",
line 1, in
create_purchase = Wizard('purchase.request.create_purchase', [pr])
File "/usr/lib/python3/dist-packages/proteus/__init__.py", line
1169, in __init__
self.execute(self.start_state)
File "/usr/lib/python3/dist-packages/proteus/__init__.py", line
1195, in execute
result = self._proxy.execute(self.session_id, data, self.state,
File "/usr/lib/python3/dist-packages/proteus/config.py", line 195,
in __call__
result = rpc.result(meth(*args, **kwargs))
File "/usr/lib/python3/dist-packages/trytond/wizard/wizard.py",
line 280, in execute
cls.check_access()
File "/usr/lib/python3/dist-packages/trytond/wizard/wizard.py",
line 242, in check_access
ModelAccess.check(model, 'write')
File "/usr/lib/python3/dist-packages/trytond/ir/model.py", line
522, in check
cls.raise_user_error(mode, model_name)
File "/usr/lib/python3/dist-packages/trytond/error.py", line 74,
in raise_user_error
raise UserError(error)
trytond.exceptions.UserError: You can not write in this document!
(purchase.request) -
signature.asc
Description: OpenPGP digital signature
Processed: tryton-server breaks tryton-modules-purchase-request autopkgtest: trytond.exceptions.UserError: You can not write in this document!
Processing control commands: > found -1 tryton-server/5.0.19-1 Bug #955578 [src:tryton-server, src:tryton-modules-purchase-request] tryton-server breaks tryton-modules-purchase-request autopkgtest: trytond.exceptions.UserError: You can not write in this document! Marked as found in versions tryton-server/5.0.19-1. > found -1 tryton-modules-purchase-request/5.0.3-1 Bug #955578 [src:tryton-server, src:tryton-modules-purchase-request] tryton-server breaks tryton-modules-purchase-request autopkgtest: trytond.exceptions.UserError: You can not write in this document! Marked as found in versions tryton-modules-purchase-request/5.0.3-1. -- 955578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955578: tryton-server breaks tryton-modules-purchase-request autopkgtest: trytond.exceptions.UserError: You can not write in this document!
Source: tryton-server, tryton-modules-purchase-request
Control: found -1 tryton-server/5.0.19-1
Control: found -1 tryton-modules-purchase-request/5.0.3-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of tryton-server the autopkgtest of
tryton-modules-purchase-request fails in testing when that autopkgtest
is run with the binary packages of tryton-server from unstable. It
passes when run with only packages from testing. In tabular form:
passfail
tryton-serverfrom testing5.0.19-1
tryton-modules-purchase-request from testing5.0.3-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of tryton-server to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=tryton-server
https://ci.debian.net/data/autopkgtest/testing/amd64/t/tryton-modules-purchase-request/4784546/log.gz
==
FAIL:
/usr/lib/python3/dist-packages/trytond/modules/purchase_request/tests/scenario_purchase_request.rst
Doctest: scenario_purchase_request.rst
--
Traceback (most recent call last):
File "/usr/lib/python3.8/doctest.py", line 2197, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for scenario_purchase_request.rst
File
"/usr/lib/python3/dist-packages/trytond/modules/purchase_request/tests/scenario_purchase_request.rst",
line 0
--
File
"/usr/lib/python3/dist-packages/trytond/modules/purchase_request/tests/scenario_purchase_request.rst",
line 170, in scenario_purchase_request.rst
Failed example:
create_purchase = Wizard('purchase.request.create_purchase',
[pr])
Exception raised:
Traceback (most recent call last):
File "/usr/lib/python3.8/doctest.py", line 1329, in __run
exec(compile(example.source, filename, "single",
File "", line 1, in
create_purchase = Wizard('purchase.request.create_purchase',
File "/usr/lib/python3/dist-packages/proteus/__init__.py", line
1169, in __init__
self.execute(self.start_state)
File "/usr/lib/python3/dist-packages/proteus/__init__.py", line
1195, in execute
result = self._proxy.execute(self.session_id, data, self.state,
File "/usr/lib/python3/dist-packages/proteus/config.py", line 195,
in __call__
result = rpc.result(meth(*args, **kwargs))
File "/usr/lib/python3/dist-packages/trytond/wizard/wizard.py",
line 280, in execute
cls.check_access()
File "/usr/lib/python3/dist-packages/trytond/wizard/wizard.py",
line 242, in check_access
ModelAccess.check(model, 'write')
File "/usr/lib/python3/dist-packages/trytond/ir/model.py", line
522, in check
cls.raise_user_error(mode, model_name)
File "/usr/lib/python3/dist-packages/trytond/error.py", line 74,
in raise_user_error
raise UserError(error)
trytond.exceptions.UserError: You can not write in this document!
(purchase.request) -
signature.asc
Description: OpenPGP digital signature
Processed: src:praat: fails to migrate to testing for too long: ftbfs mips64el
Processing control commands: > fixed -1 6.1.09-1 Bug #955576 [src:praat] src:praat: fails to migrate to testing for too long: ftbfs mips64el Marked as fixed in versions praat/6.1.09-1. -- 955576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955576: src:praat: fails to migrate to testing for too long: ftbfs mips64el
Source: praat Version: 6.1.08-1 Severity: serious Control: fixed -1 6.1.09-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:praat in its current version in unstable has been trying to migrate for 62 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=praat signature.asc Description: OpenPGP digital signature
Processed: urwid-satext: Please make another source-only upload to allow testing migration
Processing commands for cont...@bugs.debian.org: > fixed 952479 0.8.0~hg144.bfab04d0a745-1 Bug #952479 [src:urwid-satext] urwid-satext: Please make another source-only upload to allow testing migration Marked as fixed in versions urwid-satext/0.8.0~hg144.bfab04d0a745-1. > notfound 953708 0.8.0~hg144.bfab04d0a745-1 Bug #953708 [src:urwid-satext] src:urwid-satext: fails to migrate to testing for too long Ignoring request to alter found versions of bug #953708 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 952479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952479 953708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955575: src:securefs: fails to migrate to testing for too long
Source: securefs Version: 0.8.3+ds-1 Severity: serious Control: fixed -1 0.9.0+ds-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:securefs in its current version in unstable has been trying to migrate for 63 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=securefs signature.asc Description: OpenPGP digital signature
Processed: src:securefs: fails to migrate to testing for too long
Processing control commands: > fixed -1 0.9.0+ds-1 Bug #955575 [src:securefs] src:securefs: fails to migrate to testing for too long Marked as fixed in versions securefs/0.9.0+ds-1. -- 955575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:django-housekeeping
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:django-housekeeping
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was
debian-bts-l...@lists.debian.org).
> # remote status report for #951918 (http://bugs.debian.org/951918)
> # Bug title: django-housekeeping: FTBFS: dh_auto_test: error: pybuild --test
> -i python{version} -p "3.8 3.7" returned exit code 13
> # * https://github.com/spanezz/django-housekeeping/issues/5
> # * remote status changed: open -> closed
> # * closed upstream
> tags 951918 + fixed-upstream
Bug #951918 [src:django-housekeeping] django-housekeeping: FTBFS: dh_auto_test:
error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13
Added tag(s) fixed-upstream.
> usertags 951918 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 951918 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
951918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 932842 in 2.28.0-1, fixed 941137 in 2.28.0-1, notfixed 646128 in 2.0.0 ..., tagging 926279 ...
Processing commands for cont...@bugs.debian.org:
> # fix bug metadata to allow archival
> fixed 932842 2.28.0-1
Bug #932842 {Done: Alberto Garcia } [libwebkit2gtk-4.0-37]
libwebkit2gtk-4.0-37: Surf hangs after switching from a HLS stream
Marked as fixed in versions webkit2gtk/2.28.0-1.
> fixed 941137 2.28.0-1
Bug #941137 {Done: Alberto Garcia } [libwebkit2gtk-4.0-37]
libwebkit2gtk-4.0-37: libwebkit2gtk does not play AAC (or just a few seconds)
Marked as fixed in versions webkit2gtk/2.28.0-1.
> notfixed 646128 2.0.0
Bug #646128 {Done: Norbert Preining } [calibre]
Conversion to MOBI-format fails, if X Window System is not present
There is no source info for the package 'calibre' at version '2.0.0' with
architecture ''
Unable to make a source version for version '2.0.0'
No longer marked as fixed in versions 2.0.0.
> fixed 646128 2.0.0+dfsg-1
Bug #646128 {Done: Norbert Preining } [calibre]
Conversion to MOBI-format fails, if X Window System is not present
Marked as fixed in versions calibre/2.0.0+dfsg-1.
> notfixed 922319 slurm-wlm/19.05.3.2-1
Bug #922319 {Done: Gennaro Oliva } [slurm-wlm] Build
libpam-slurm-adopt package for Slurm
The source slurm-wlm and version 19.05.3.2-1 do not appear to match any binary
packages
No longer marked as fixed in versions slurm-wlm/19.05.3.2-1.
> fixed 922319 19.05.3.2-1
Bug #922319 {Done: Gennaro Oliva } [slurm-wlm] Build
libpam-slurm-adopt package for Slurm
Marked as fixed in versions slurm-llnl/19.05.3.2-1.
> tags 926279 + sid bullseye
Bug #926279 {Done: Tomasz Buchert } [mininet] mininet:
switch from cgroup-bin to cgroup-tools
Added tag(s) bullseye and sid.
> tags 242936 - bullseye buster stretch sid jessie
Bug #242936 {Done: Andreas Tille } [libgdchart-gd2-noxpm-dev]
libgdchart-gd2-noxpm-dev: Examples fail to compile
Removed tag(s) stretch, buster, sid, bullseye, and jessie.
> tags 554582 =
Bug #554582 {Done: Mario Limonciello } [libsmbios]
libsmbios_2.0.3.dfsg-1(ia64/unstable): FTBFS: matching constraint does not
allow a register
Removed tag(s) squeeze, wheezy, stretch, buster, sid, bullseye, and jessie.
> tags 657771 =
Bug #657771 {Done: Emmanuel Bourg } [src:jinput] jinput:
FTBFS(!linux):
Bug #767051 {Done: Emmanuel Bourg } [src:jinput]
libjinput-java: uninstallable on kfreebsd
Removed tag(s) wheezy, stretch, buster, sid, bullseye, and jessie.
Removed tag(s) bullseye, jessie, sid, wheezy, buster, and stretch.
> fixed 735435 2.2.0+dfsg-2.3
Bug #735435 {Done: Debian FTP Masters }
[gnoemoe] gnoemoe: diff for NMU version 2.2.0+dfsg-2.3
Marked as fixed in versions gnoemoe/2.2.0+dfsg-2.3.
> tags 757834 - bullseye buster sid stretch jessie
Bug #757834 {Done: intrigeri } [libtext-charwidth-perl]
libtext-charwidth-perl: Creates empty /usr/lib/perl5 directory when built with
perl 5.20
Removed tag(s) bullseye, jessie, sid, buster, and stretch.
> tags 758379 - bullseye buster sid stretch
Bug #758379 {Done: Sébastien Villemot } [src:ffcall]
ffcall: FTBFS on arm64
Bug #849653 {Done: Sébastien Villemot } [src:ffcall]
ffcall: FTBFS on arm64: make[2]: *** No rule to make target
'avcall-aarch64.lo', needed by 'avcall.lo'.
Removed tag(s) stretch, buster, sid, and bullseye.
Removed tag(s) bullseye, sid, buster, and stretch.
> tags 790177 - stretch
Bug #790177 {Done: Willem van den Akker } [src:gtkterm]
gtkterm: depends on vte which is deprecated
Removed tag(s) stretch.
> tags 823876 =
Bug #823876 {Done: Bdale Garbee } [src:atlc] atlc: change build
dependency to libgsl-dev
Removed tag(s) buster, stretch, bullseye, and sid.
> tags 842379 - sid stretch bullseye buster
Bug #842379 {Done: Gianfranco Costamagna }
[src:libb2] libb2: FTBFS on non-x86 architectures
Removed tag(s) bullseye, sid, stretch, and buster.
> tags 849662 - sid stretch buster bullseye
Bug #849662 {Done: David Steele } [src:gocryptfs] gocryptfs:
FTBFS on arm64: panic: page size incorrect: 65536
Removed tag(s) buster, stretch, bullseye, and sid.
> tags 849668 - sid stretch buster bullseye
Bug #849668 {Done: Héctor Orón Martínez }
[src:intel-processor-trace] intel-processor-trace: FTBFS on arm: error:
'PAGE_SIZE' undeclared
Removed tag(s) sid, bullseye, buster, and stretch.
> tags 860645 =
Bug #860645 {Done: Andreas Tille } [src:trinityrnaseq]
trinityrnaseq: FTBFS on i386: unsatisfiable build-dependencies: jellyfish (>=
2.1.4), parafly
Removed tag(s) bullseye, sid, stretch, and buster.
> tags 860652 - buster bullseye sid stretch
Bug #860652 {Done: Andreas Tille } [src:snap-aligner]
snap-aligner: FTBFS on i386: SNAPLib/SortedDataWriter.cpp:338:70: error: no
matching function for call to 'max(long unsigned int, _int64)'
Removed tag(s) buster, stretch, bullseye, and sid.
> tags 882630 - buster bullseye sid stretch
Bug #882630 {Done: Martin Pitt } [systemd-bootchart]
systemd-bootchart: debian/copyright refers to CC0 by URL
Removed tag(s) bullseye, sid, buster, and stretch.
> tags 882631 =
Bug #882631 {Done: Sandro Knauß } [picmi] picmi:
debian/copyright refers to CC0 by URL
Removed tag(s) buster,
Bug#955567: kalgebra: Output is always blank
Package: kalgebra Version: 4:17.08.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, KAlgebra shows nothing in its output screen. This only applies to the algebraic displays, the graphs and dictionary tabs seem to work fine. Reproduce: Enter any equation into the input text box and press enter. Expected: The result of the equation and the equation inputted should be visible. Actual: Nothing appears. Even the border of the frame appears missing. Also: Right clicking on the empty area causes a context menu to appear in the wrong place. I'm not sure if that's related. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kalgebra depends on: ii kalgebra-common 4:17.08.3-2 ii kio 5.54.1-1 ii libanalitza8 4:17.08.3-2+b3 ii libanalitzagui8 4:17.08.3-2+b3 ii libanalitzaplot8 4:17.08.3-2+b3 ii libanalitzawidgets8 4:17.08.3-2+b3 ii libc62.28-10 ii libkf5configcore55.54.0-1+deb10u1 ii libkf5configwidgets5 5.54.0-1 ii libkf5coreaddons55.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqt5core5a 5.11.3+dfsg1-1+deb10u3 ii libqt5gui5 5.11.3+dfsg1-1+deb10u3 ii libqt5webenginewidgets5 5.11.3+dfsg-2+deb10u1 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u3 ii libreadline7 7.0-5 ii libstdc++6 8.3.0-6 kalgebra recommends no packages. kalgebra suggests no packages. -- no debconf information
Bug#955566: khmer: autopkgtest regression: undefined references
Source: khmer Version: 2.1.2+dfsg-6 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Since 2019-11 the autopkgtest of khmer is failing. I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/unstable/amd64/k/khmer/4760829/log.gz + pkg=khmer + [ /tmp/autopkgtest-lxc.zxrjb5bi/downtmp/autopkgtest_tmp = ] + cd /tmp/autopkgtest-lxc.zxrjb5bi/downtmp/autopkgtest_tmp + pkg-config oxli --static --cflags + pkg-config oxli --static --libs + c++ -o test-prog-static -static -std=c++11 -I/usr/local/include -I/usr/include/oxli/smhasher /usr/share/doc/khmer-common/test-compile.cc -L/usr/local/lib -loxli -lbz2 -lz + ./test-prog-static + pkg-config oxli --cflags + pkg-config oxli --libs + c++ -o test-prog-dynamic -std=c++11 -I/usr/local/include -I/usr/include/oxli/smhasher /usr/share/doc/khmer-common/test-compile.cc -L/usr/local/lib -loxli /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzerror' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `deflateInit2_' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzeof' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `deflate' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `deflateEnd' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `crc32' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `inflate' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `inflateInit2_' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzclearerr' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `inflateEnd' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzopen64' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzwrite' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzopen' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `BZ2_bzWriteClose' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `BZ2_bzReadOpen' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `BZ2_bzRead' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzdirect' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzclose' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzdopen' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gzread' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `BZ2_bzWriteOpen' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `BZ2_bzReadClose' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/liboxli.so: undefined reference to `gztell64' collect2: error: ld returned 1 exit status signature.asc Description: OpenPGP digital signature
Bug#955555: gitlab: uninitialized constant APIGuard
Control: fixed -1 12.8.6-1 On 2020, ഏപ്രിൽ 2 8:05:53 PM IST, Dragos Jarca wrote: >Package: gitlab >Version: 12.6.8-3 >Severity: grave >Tags: a11y >Justification: renders package unusable > >Dear Maintainer, > >I upgraded packages: > >Start-Date: 2020-04-02 10:00:27 >Commandline: apt-get dist-upgrade >Install: libllvm10:amd64 (1:10.0.0-1, automatic), ruby-sync:amd64 >(0.5.0-2, automatic) >Upgrade: libpython3.7-minimal:amd64 (3.7.7-1, 3.7.7-1+b1), >python3-werkzeug:amd64 (0.16.1+dfsg1-1, 0.16.1+dfsg1-2), >glib-networking-services:amd64 (2.64.0-1, 2.64.1-1), >libpython3.8-dbg:amd64 (3.8.2-1, 3.8.2-1+b1), libpython3.8-dev:amd64 >(3.8.2-1, 3.8.2-1+b1), php-phpseclib:amd64 (2.0.25-1, 2.0.26-1), >libgirepository-1.0-1:amd64 (1.62.0-5+b1, 1.64.0-2), >libpython3.8-minimal:amd64 (3.8.2-1, 3.8.2-1+b1), glib-networking:amd64 > >(2.64.0-1, 2.64.1-1), dash:amd64 (0.5.10.2-6, 0.5.10.2-7), >ruby-memoist:amd64 (0.16.2-1, 0.16.2-2), ruby-tins:amd64 (1.1.0-1, >1.1.0-2), libhiredis0.14:amd64 (0.14.0-6, 0.14.1-1), libffi-dev:amd64 >(3.3-3, 3.3-4), libdbd-pg-perl:amd64 (3.10.4-1, 3.10.5-1), >yarnpkg:amd64 >(1.19.1-1, 1.21.1-2), nodejs:amd64 (10.17.0~dfsg-2, 10.19.0~dfsg-3), >libpython3.8:amd64 (3.8.2-1, 3.8.2-1+b1), python3.7:amd64 (3.7.7-1, >3.7.7-1+b1), python3.8:amd64 (3.8.2-1, 3.8.2-1+b1), >ruby-mini-magick:amd64 (4.9.2-1.1, 4.9.5-2), bubblewrap:amd64 (0.4.0-1, > >0.4.1-1), node-d3-quadtree:amd64 (1.0.6-2, 1.0.7-1), libpq5:amd64 >(12.2-1+b1, 12.2-4), libpython3.7-stdlib:amd64 (3.7.7-1, 3.7.7-1+b1), >glib-networking-common:amd64 (2.64.0-1, 2.64.1-1), >python3.7-minimal:amd64 (3.7.7-1, 3.7.7-1+b1), >ruby-state-machines-activemodel:amd64 (0.5.1-3, 0.7.1-2), >libpq-dev:amd64 (12.2-1+b1, 12.2-4), npm:amd64 (6.14.2+ds-2, >6.14.3+ds-1), python3-future:amd64 (0.18.2-1, 0.18.2-2), >postgresql-12:amd64 (12.2-1+b1, 12.2-4), gir1.2-glib-2.0:amd64 >(1.62.0-5+b1, 1.64.0-2), python3.8-minimal:amd64 (3.8.2-1, 3.8.2-1+b1), > >python3-acme:amd64 (1.1.0-1, 1.3.0-2), libconfuse-common:amd64 >(3.2.2+dfsg-1, 3.2.2+dfsg-2), ruby-omniauth:amd64 (1.9.0-1, 1.9.1-1), >shared-mime-info:amd64 (1.10-1, 1.15-1), libnode-dev:amd64 >(10.17.0~dfsg-2, 10.19.0~dfsg-3), libwnck-3-0:amd64 (3.32.0-1, >3.36.0-1), ruby-warden:amd64 (1.2.3-2, 1.2.8-1), >libpython3.8-stdlib:amd64 (3.8.2-1, 3.8.2-1+b1), libnode64:amd64 >(10.17.0~dfsg-2, 10.19.0~dfsg-3), libwnck-3-common:amd64 (3.32.0-1, >3.36.0-1), libpcap0.8:amd64 (1.9.1-2, 1.9.1-3), libffi7:amd64 (3.3-3, >3.3-4), python3.8-dbg:amd64 (3.8.2-1, 3.8.2-1+b1), python3.8-dev:amd64 >(3.8.2-1, 3.8.2-1+b1), libconfuse2:amd64 (3.2.2+dfsg-1, 3.2.2+dfsg-2), >postgresql-client-12:amd64 (12.2-1+b1, 12.2-4) >End-Date: 2020-04-02 10:05:57 > >Start-Date: 2020-04-02 10:14:16 >Commandline: apt-get -t unstable install gitlab-shell >Upgrade: gitlab-shell:amd64 (10.3.0+debian-3.1, 11.0.0+debian-2) >End-Date: 2020-04-02 10:14:37 > >After that gitlab stop starting. > >The error is: > >rake aborted! >NameError: uninitialized constant APIGuard Please use gitlab from experimental. Its a lot of work to backport patches to get grape 1.3 working with 12.6.x. Also please always check wiki.debian.org/gitlab for any work arounds. >/usr/share/gitlab/lib/gitlab/patch/draw_route.rb:32:in `instance_eval' >/usr/share/gitlab/lib/api/api.rb:5:in `' >/usr/share/gitlab/lib/api/api.rb:4:in `' >/usr/share/gitlab/lib/api/api.rb:3:in `' >/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies/interlock.rb:14:in > >`block in loading' >/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/concurrency/share_lock.rb:151:in > >`exclusive' >/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies/interlock.rb:13:in > >`loading' >(eval):4:in `draw_route' >/usr/share/gitlab/lib/gitlab/patch/draw_route.rb:32:in `instance_eval' >/usr/share/gitlab/lib/gitlab/patch/draw_route.rb:32:in `draw_route' >/usr/share/gitlab/lib/gitlab/patch/draw_route.rb:19:in `draw_ce' >/usr/share/gitlab/lib/gitlab/patch/draw_route.rb:13:in `draw' >/usr/share/gitlab/config/routes.rb:171:in `block in ' >/usr/share/rubygems-integration/all/gems/actionpack-5.2.4.1/lib/action_dispatch/routing/route_set.rb:432:in > >`instance_exec' >/usr/share/rubygems-integration/all/gems/actionpack-5.2.4.1/lib/action_dispatch/routing/route_set.rb:432:in > >`eval_block' >/usr/share/rubygems-integration/all/gems/actionpack-5.2.4.1/lib/action_dispatch/routing/route_set.rb:414:in > >`draw' >/usr/share/gitlab/config/routes.rb:4:in `' >/usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application/routes_reloader.rb:41:in > >`block in load_paths' >/usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application/routes_reloader.rb:41:in > >`each' >/usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application/routes_reloader.rb:41:in > >`load_paths'
Processed: Re: Bug#955555: gitlab: uninitialized constant APIGuard
Processing control commands: > fixed -1 12.8.6-1 Bug #95 [gitlab] gitlab: uninitialized constant APIGuard Marked as fixed in versions gitlab/12.8.6-1. -- 95: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955561: src:r-cran-rmarkdown: fails to migrate to testing for too long
Source: r-cran-rmarkdown Version: 1.15+dfsg-1 Severity: serious Control: fixed -1 2.1+dfsg-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:r-cran-rmarkdown in its current version in unstable has been trying to migrate for 66 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-rmarkdown signature.asc Description: OpenPGP digital signature
Processed: tagging 952062
Processing commands for cont...@bugs.debian.org: > tags 952062 + patch Bug #952062 [src:openjfx] openjfx: FTBFS: gtktypeutils.h:236:64: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations] Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 952062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:r-cran-rmarkdown: fails to migrate to testing for too long
Processing control commands: > fixed -1 2.1+dfsg-1 Bug #955561 [src:r-cran-rmarkdown] src:r-cran-rmarkdown: fails to migrate to testing for too long Marked as fixed in versions r-cran-rmarkdown/2.1+dfsg-1. -- 955561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952062: openjfx: Patch to use -Wno-error=deprecated-declarations
Source: openjfx
Version: 11.0.2+1-1
Tags: patch
Followup-For: Bug #952062
Dear Maintainer,
Using -Werror is great for CI, not so much for unstable where compiler
updates tend cause breakage like this.
The attached patch adds -Wno-error=deprecated-declarations to fix the
FTBFS.
Kind Regards,
Bas
diff -Nru openjfx-11.0.2+1/debian/changelog openjfx-11.0.2+1/debian/changelog
--- openjfx-11.0.2+1/debian/changelog 2019-01-20 16:25:28.0 +0100
+++ openjfx-11.0.2+1/debian/changelog 2020-04-02 16:56:59.0 +0200
@@ -1,3 +1,11 @@
+openjfx (11.0.2+1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix FTBFS due to -Werror=deprecated-declarations.
+(closes: #952062)
+
+ -- Bas Couwenberg Thu, 02 Apr 2020 16:56:59 +0200
+
openjfx (11.0.2+1-1) unstable; urgency=medium
* New upstream release
diff -Nru
openjfx-11.0.2+1/debian/patches/no-error_deprecated-declarations.patch
openjfx-11.0.2+1/debian/patches/no-error_deprecated-declarations.patch
--- openjfx-11.0.2+1/debian/patches/no-error_deprecated-declarations.patch
1970-01-01 01:00:00.0 +0100
+++ openjfx-11.0.2+1/debian/patches/no-error_deprecated-declarations.patch
2020-04-02 16:53:26.0 +0200
@@ -0,0 +1,14 @@
+Description: Fix FTBFS due to -Werror=deprecated-declarations.
+Author: Bas Couwenberg
+Bug-Debian: https://bugs.debian.org/952062
+
+--- a/buildSrc/linux.gradle
b/buildSrc/linux.gradle
+@@ -45,6 +45,7 @@ def commonFlags = [
+ "-fno-strict-aliasing", "-fPIC", "-fno-omit-frame-pointer", //
optimization flags
+ "-fstack-protector",
+ "-Wno-error=cast-function-type",
++"-Wno-error=deprecated-declarations",
+ "-Wextra", "-Wall", "-Wformat-security", "-Wno-unused",
"-Wno-parentheses", "-Werror=implicit-function-declaration"] // warning flags
+
+ commonFlags.addAll("dpkg-buildflags --get CPPFLAGS
".execute().text.trim().split(" "))
diff -Nru openjfx-11.0.2+1/debian/patches/series
openjfx-11.0.2+1/debian/patches/series
--- openjfx-11.0.2+1/debian/patches/series 2019-01-20 00:35:49.0
+0100
+++ openjfx-11.0.2+1/debian/patches/series 2020-04-02 16:50:51.0
+0200
@@ -15,3 +15,4 @@
26-disable-webkit-jit-for-armv4.patch
29-glibc-compatibility.patch
disable-jit-for-non-x86.patch
+no-error_deprecated-declarations.patch
Bug#955006: marked as done (src:gubbins: fails to migrate to testing for too long: ftbfs on i386)
Your message dated Thu, 02 Apr 2020 16:05:44 + with message-id and subject line Bug#955006: fixed in gubbins 2.4.1-2 has caused the Debian Bug report #955006, regarding src:gubbins: fails to migrate to testing for too long: 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.) -- 955006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gubbins Version: 2.3.5-1 Severity: serious Control: fixed -1 2.4.1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:gubbins in its current version in unstable has been trying to migrate for 64 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=gubbins signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gubbins Source-Version: 2.4.1-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of gubbins, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated gubbins package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Apr 2020 17:03:51 +0200 Source: gubbins Architecture: source Version: 2.4.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 955006 Changes: gubbins (2.4.1-2) unstable; urgency=medium . * Versioned Build-Depends: raxml (>= 8.2.12+dfsg-5) Closes: #955006 * Add salsa-ci file (routine-update) * Rules-Requires-Root: no (routine-update) Checksums-Sha1: 039ea6e591c535fc1bbf747d60a65b5e646ec951 2186 gubbins_2.4.1-2.dsc e5da6e573284fd0d6fd76f13b248187a8f054fb1 6480 gubbins_2.4.1-2.debian.tar.xz 771bfb950d1b3285192f581d71dad6cbf83264eb 8089 gubbins_2.4.1-2_amd64.buildinfo Checksums-Sha256: be2ec846ee288b134a8052cfe044f3740113206036deeff6bc00a3e2573fe5c3 2186 gubbins_2.4.1-2.dsc 87f5ed50f6be3b1d3c4345642c9483c28f5f1ca78cd94e43eab52a7ec2cca04f 6480 gubbins_2.4.1-2.debian.tar.xz b62d830ba4776a864a1cde25edd6a1e38f830bb28ffe4e21fc3fa3ad2e62b219 8089 gubbins_2.4.1-2_amd64.buildinfo Files: 353fe8fa10268b690796e03148a0fefe 2186 science optional gubbins_2.4.1-2.dsc df48aefe412b94c26ebb2a96e038a6cc 6480 science optional gubbins_2.4.1-2.debian.tar.xz b1881d0f4e1b26fc91dfe075f655e907 8089 science optional gubbins_2.4.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6GCZMRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFevQ//R1BlqBKCAGRFMDAm/dmqnO1egtHf5dSb 7QoOqZND8Nwm73BdCcG1iQ2DxNMaOVuz2NcpGSYSTb1CPp/z8+LwOKW984iYMXU3 uUuGCYuCwq28707Xhf1HWKukaQpUFmJoIYfEg70V21Z6vCT2AL9b2ShuuVRGBdBZ 0ZztqnnU4OTg6Cj7MaTkZhQHmHbhi9sYuzBB4Q/BQk1n3kuBdIDZFKCc2g8MeZDz
Bug#955527: kernelshark: Crash (SIGSEGV) when pressing the "+" button
X-Debbugs-CC: by...@debian.org I can reproduce the problem when I have kernelshark open without any trace file. But the error is not seen if the trace file is opened using kernelshark (which is the normal usecase). Can you please confirm if you have seen the problem with or without a tracefile opened? -- Regards Sudip
Bug#955234: marked as done (FTBFS: help2man missing, /etc/machine-id not available by default on buildds)
Your message dated Thu, 02 Apr 2020 15:35:39 +
with message-id
and subject line Bug#955234: fixed in libjcat 0.1.0-2
has caused the Debian Bug report #955234,
regarding FTBFS: help2man missing, /etc/machine-id not available by default on
buildds
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.)
--
955234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjcat
Version: 0.1.0-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source
libjcat FTBFS on all the buildds due to a missing B-D on help2man.
After fixing that, the tests fail (in a minimal chroot) because they try
to produce a signature for /etc/machine-id, which isn't guaranteed to
exist.
Fixed here: https://salsa.debian.org/efi-team/libjcat/-/merge_requests/1
smcv
--- End Message ---
--- Begin Message ---
Source: libjcat
Source-Version: 0.1.0-2
Done: Mario Limonciello
We believe that the bug you reported is fixed in the latest version of
libjcat, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mario Limonciello (supplier of updated libjcat
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, 01 Apr 2020 16:49:21 -0500
Source: libjcat
Architecture: source
Version: 0.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI team
Changed-By: Mario Limonciello
Closes: 955234 955258 955259
Changes:
libjcat (0.1.0-2) unstable; urgency=medium
.
[ Simon McVittie ]
* Fix FTBFS:
- Add missing B-D on help2man (Closes: #955258)
- jcat-self-test: Sign /etc/os-release instead of /etc/machine-id.
The autobuilders use a minimal chroot that doesn't necessarily have
a machine ID, but base-files gives us /etc/os-release.
(Closes: #955234)
* Fix -dev package dependencies:
- libjcat-dev: Add missing -dev dependencies for dependency libraries
- libjcat-dev: Add missing dependency on a matching libjcat1
- d/control: Enable gir debhelper sequence.
Otherwise ${gir:Depends} won't be generated.
* Install test data so that the installed-tests can pass
* Add some simple autopkgtest coverage
(Closes: #955259)
.
[ Mario Limonciello ]
* Backport a few other patches from upstream related to installed-tests
usage.
Checksums-Sha1:
9f3613483234cadd4d7042bfde71ade0abdcab55 2494 libjcat_0.1.0-2.dsc
64e798716d05db58dcbb3edf76bbfee2d1592c7e 60808 libjcat_0.1.0.orig.tar.gz
74d11e44e10cccd8229d73514007acd7138e7556 7052 libjcat_0.1.0-2.debian.tar.xz
df628c308ab1f9193142c20f93aec8875adf7230 14313 libjcat_0.1.0-2_source.buildinfo
Checksums-Sha256:
49dac313c9c45a0ebdeb90975458214b9e2c861ace14057e8e060781862a95fa 2494
libjcat_0.1.0-2.dsc
07bce18b9b4ddbfd3e106251a540884be0715047aaece7f53dcdaed1bd2f1b11 60808
libjcat_0.1.0.orig.tar.gz
f85cbf2e0737a89d4d9c0b37cd8bdf566ba9bc92789f83aff5c1bc4da8709549 7052
libjcat_0.1.0-2.debian.tar.xz
22c1cb2030d4f24846b6e36234ebebfc4a39678a9a13aa22976351cf872fa22a 14313
libjcat_0.1.0-2_source.buildinfo
Files:
08d71e0d78388478adf0affd93669439 2494 libs optional libjcat_0.1.0-2.dsc
3e83a3ab71e001480a86b49864a186f3 60808 libs optional libjcat_0.1.0.orig.tar.gz
fd128a844cf8e182a9b8b46fce31959d 7052 libs optional
libjcat_0.1.0-2.debian.tar.xz
c2ab2943d35fcf9eced29ebbadeb8235 14313 libs optional
libjcat_0.1.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJPBAEBCgA5FiEECwtuSU6dXvs5GA2aLRkspiR3AnYFAl6F/MwbHG1hcmlvLmxp
bW9uY2llbGxvQGRlbGwuY29tAAoJEC0ZLKYkdwJ2wtkP+gLWl54IiK1ucc+UyMeS
0UB53QFGynIH+bscNCErD9bIacrVS3k1DGDF4Xs9KRGcIwfiZRtNJvyYKaIHgijK
nA9HFH/UVz16N7+3NvFc8g8nCcWx8i+j0GSV+T8Bbwbr14g22yFCpOolUQLIrTV0
uvBjpbhuHjF8c35TmaSaGNQejzattMBTD1jzYluOTvXqZO7DYZx22p89x8aKPu5N
Tbl3EwxuRbRksxf7/CAjboOilXNYmiofL8yckoSRHURLRfSuOAeydeWJR5NGAbn4
KBJGemZYEvM3VjqCIpYoawUloWux9IfbBmUay+lCHWpjp8W5kTqYC1s+XOu31n5Q
etDUQth4gQeaDtw/CSM9X4kIwrvNynu5pYAXb51jyvE3lwUOKcpBfR3eJc3qh71p
CwfTGXlKCDvSN/lCf3tuvxuVaTO7BrXehfyOJLdQDV+7xTDifkrxg3NAHJrN95RN
Bug#955471: theano: test failures
Control: severity -1 normal Control: tags -1 upstream patch pending Control: forwarded -1 https://github.com/Theano/theano/pull/6749 On closer inspection, this isn't a "silently wrong answer" bug after all, so lowering the severity. Some parts of it appear to be caused by numpy 1.17 and some parts by scipy 1.3.
Bug#955558: npmjs.com version is using embedded copy of jquery at 1.9.0
This may need to be adapted to our node-jquery version which is at 3.4.0
Bug#937565: marked as done (pytest-runner: Python2 removal in sid/bullseye)
Your message dated Thu, 02 Apr 2020 15:11:59 + with message-id and subject line Bug#937565: fixed in pytest-runner 2.11.1-1.2 has caused the Debian Bug report #937565, regarding pytest-runner: 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.) -- 937565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pytest-runner Version: 2.11.1-1.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pytest-runner If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: pytest-runner Source-Version: 2.11.1-1.2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of pytest-runner, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pytest-runner package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Apr 2020 10:40:58 -0400 Source: pytest-runner Architecture: source Version: 2.11.1-1.2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937565 Changes: pytest-runner (2.11.1-1.2) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #937565 Checksums-Sha1: 785153b73cb55287b7ba200768cd1076c99ed3b4 2135 pytest-runner_2.11.1-1.2.dsc 96745e555c6491d43e0aec8f928613ac7bd653dc 2440 pytest-runner_2.11.1-1.2.debian.tar.xz 6ed6ef9f5f5c0e3548116fe22d3a55eca17b6266 7971 pytest-runner_2.11.1-1.2_amd64.buildinfo Checksums-Sha256: c7fd5979fe7ff03af01e134f0852af41c63da2adcd6b86d7999448c257f20250 2135 pytest-runner_2.11.1-1.2.dsc 5aeba91cf8278cd059f180d988b8625478d645ecae5a4399a2d15d96b7acf85f 2440 pytest-runner_2.11.1-1.2.debian.tar.xz ed77a48418ba7ffb796eec7c854eb2dcc340f214c328564056ade97054769fe7
Bug#955558: node-jquery.waitforimages broken Uncaught TypeError: Cannot read property 'dataset' of null
Package: node-jquery.waitforimages Version: 2.4.0+ds-5 Severity: grave Justification: breaks its only reverse dependency gitlab gitlab's web ui does not show list of files and web console has this error, index.js?d252:17 Uncaught TypeError: Cannot read property 'dataset' of null at jQuery.fn.init.eval (index.js?d252:17) at jQuery.fn.init.$.fn.waitForImages (jquery.waitforimages.js?d87d:180) at HTMLDocument.eval (index.js?d252:17) More details https://gitlab.com/gitlab-org/gitlab/-/issues/213120 Switching to jquery.waitforimages from npmjs.com fixes the problem.
Processed: Re: Bug#955471: theano: test failures
Processing control commands: > severity -1 normal Bug #955471 [python3-theano] theano: test failures Severity set to 'normal' from 'serious' > tags -1 upstream patch pending Bug #955471 [python3-theano] theano: test failures Added tag(s) upstream, pending, and patch. > forwarded -1 https://github.com/Theano/theano/pull/6749 Bug #955471 [python3-theano] theano: test failures Set Bug forwarded-to-address to 'https://github.com/Theano/theano/pull/6749'. -- 955471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948552: marked as done (libschroedinger-maeparser1: SONAME change without package name change)
Your message dated Thu, 02 Apr 2020 15:01:05 + with message-id and subject line Bug#948552: fixed in schroedinger-maeparser 1.2.3-1 has caused the Debian Bug report #948552, regarding libschroedinger-maeparser1: SONAME change without package name change 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.) -- 948552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu schroedinger-coordgenlibs_1.3-1 . ANY . unstable . -m "Rebuild against libschroedinger-maeparser-dev >= 1.2.2-1" The binNMU of rdkit (#946247) did not fix #945985; it appears that it is schroedinger-coordgenlibs that actually needs rebuilding to pick up the new filename of libmaeparser: $ ldd /usr/lib/x86_64-linux-gnu/libcoordgen.so.1.3 linux-vdso.so.1 (0x7fff9f9bd000) libmaeparser.so.1.2 => not found libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f5445999000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5445854000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f544583a000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f544567a000) /lib64/ld-linux-x86-64.so.2 (0x7f5445c12000) (rebuilding the package has the linking pick up libmaeparser.so.1 instead) thanks Stuart --- End Message --- --- Begin Message --- Source: schroedinger-maeparser Source-Version: 1.2.3-1 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of schroedinger-maeparser, 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. Andrius Merkys (supplier of updated schroedinger-maeparser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Mar 2020 02:38:51 -0400 Source: schroedinger-maeparser Binary: libmaeparser-dev libmaeparser1 libmaeparser1-dbgsym Architecture: source amd64 Version: 1.2.3-1 Distribution: experimental Urgency: medium Maintainer: Debian Science Team Changed-By: Andrius Merkys Description: libmaeparser-dev - Development files to parse Schrödinger Maestro files libmaeparser1 - parser for Schrödinger Maestro files Closes: 948552 Changes: schroedinger-maeparser (1.2.3-1) experimental; urgency=medium . * Team upload. * New upstream version 1.2.3 * Refreshing cmake_standard_dirs.patch. * Dropping pull-55.patch: applied upstream. * Renaming binary packages according to the SONAME (Closes: #948552) * Adding Rules-Requires-Root: no. * Wrapping and sorting. * Using debhelper-compat; bumping (no changes). * Not creating empty usr/share/cmake/ directory. * Adding build dependency on zlib1g-dev. Checksums-Sha1: 451f3a42f21dd39a0f35d3d6d629dbbe0fd82ead 2237 schroedinger-maeparser_1.2.3-1.dsc 0687597139a3b58832fdceae7fc3b66e5ffeb1db 38435 schroedinger-maeparser_1.2.3.orig.tar.gz 80273c20992beee0ea970f3c2b2ab355e494db64 3700 schroedinger-maeparser_1.2.3-1.debian.tar.xz 823ff1dc4b2667dc28961bb11a35c4349f469576 12900 libmaeparser-dev_1.2.3-1_amd64.deb 56f9dc749afa78d549aeb8a594203ecf7a1bdecd 1660816 libmaeparser1-dbgsym_1.2.3-1_amd64.deb d8c5df487eb2194aac09d2efd0caf9d87c2db27d 87260 libmaeparser1_1.2.3-1_amd64.deb de0e3913568d2de13ea49a418bb8cad31f4c1530 8144 schroedinger-maeparser_1.2.3-1_amd64.buildinfo Checksums-Sha256: 809c83ac46a64b42ee56febd4aaca2d1961a6ac5e9f7ff79d85b68f95ade6ef1 2237 schroedinger-maeparser_1.2.3-1.dsc ca2e2dead8a1fdd74b624ca0f0c4dde205d0b8abbbfdd62de0786f2d3f6f291c 38435 schroedinger-maeparser_1.2.3.orig.tar.gz 0a5d89845f91d1994345fd757e45e6ad1a2164d5dff15291205086eca87c5077 3700 schroedinger-maeparser_1.2.3-1.debian.tar.xz 48afc33987ac8a717b557dd7f3cc18e14541cd27189401b83049276de6da2c31 12900 libmaeparser-dev_1.2.3-1_amd64.deb 91387479c954203fe1d1689a6d99d311d5baa234eee0f7da36b3d2656396f072 1660816 libmaeparser1-dbgsym_1.2.3-1_amd64.deb 707900d7a8def68a4c4d98e6716cf13a7e1cf8d1b671fa4363510283814f094d 87260
Bug#953550: marked as done (mailutils: FTBFS with Python 3.8: undefined reference)
Your message dated Thu, 02 Apr 2020 15:00:26 + with message-id and subject line Bug#953550: fixed in mailutils 1:3.8-1 has caused the Debian Bug report #953550, regarding mailutils: FTBFS with Python 3.8: undefined reference 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.) -- 953550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mailutils Version: 1:3.7-2 Severity: serious Tags: ftbfs bullseye sid Hi Maintainer mailutils FTBFS when rebuilt with Python 3.8 [1]. I've copied what I hope is a relevant part of the log below. Regards Graham [1] https://buildd.debian.org/status/package.php?p=mailutils /bin/bash ../libtool --tag=CC --mode=link gcc -g -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdeclaration-after-statement -ggdb -Wl,-z,relro -Wl,-z,now -Wl,--no-as-needed -o maidag deliver.o forward.o lmtp.o maidag.o mailquota.o script.o util.o ../lib/libmuscript.a ../lib/libmuaux.la ../libmu_sieve/libmu_sieve.la ../libproto/mbox/libmu_mbox.la ../libproto/mh/libmu_mh.la ../libproto/maildir/libmu_maildir.la ../libproto/dotmail/libmu_dotmail.la ../libproto/imap/libmu_imap.la ../libproto/pop/libmu_pop.la ../libmu_auth/libmu_auth.la ../libproto/mailer/libmu_mailer.la -lgsasl -lgnutls -lldap -lpam -ldl ../libmailutils/libmailutils.la ../libmu_scm/libmu_scm.la ../libproto/mbox/libmu_mbox.la ../libproto/mh/libmu_mh.la ../libproto/maildir/libmu_maildir.la ../libproto/dotmail/libmu_dotmail.la ../libproto/imap/libmu_imap.la ../libproto/pop/libmu_pop.la ../libproto/mailer/libmu_mailer.la ../python/3/libmu_py/libmu_py.la ../libmu_dbm/libmu_dbm.la -lguile-2.2 -lgc -lcrypt -lpthread -ldl -lutil -lm -lm -lkyotocabinet ../lib/libmutcpwrap.a -lnsl -lwrap -lcrypt -lpthread libtool: link: gcc -g -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdeclaration-after-statement -ggdb -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--no-as-needed -o .libs/maidag deliver.o forward.o lmtp.o maidag.o mailquota.o script.o util.o ../lib/libmuscript.a ../lib/.libs/libmuaux.so ../libmu_sieve/.libs/libmu_sieve.so ../libmu_auth/.libs/libmu_auth.so /usr/lib/x86_64-linux-gnu/libgsasl.so -lgnutls -lldap -lpam ../libmailutils/.libs/libmailutils.so ../libmu_scm/.libs/libmu_scm.so ../libproto/mbox/.libs/libmu_mbox.so ../libproto/mh/.libs/libmu_mh.so ../libproto/maildir/.libs/libmu_maildir.so ../libproto/dotmail/.libs/libmu_dotmail.so ../libproto/imap/.libs/libmu_imap.so ../libproto/pop/.libs/libmu_pop.so ../libproto/mailer/.libs/libmu_mailer.so ../python/3/libmu_py/.libs/libmu_py.so ../libmu_dbm/.libs/libmu_dbm.so -lguile-2.2 -lgc -ldl -lutil -lm -lkyotocabinet ../lib/libmutcpwrap.a -lnsl -lwrap -lcrypt -lpthread /usr/bin/ld: ../python/3/libmu_py/.libs/libmu_py.so: undefined reference to `PyErr_SetNone' /usr/bin/ld: ../python/3/libmu_py/.libs/libmu_py.so: undefined reference to `_Py_Dealloc' /usr/bin/ld: ../python/3/libmu_py/.libs/libmu_py.so: undefined reference to `PyLong_FromLong' /usr/bin/ld: ../python/3/libmu_py/.libs/libmu_py.so: undefined reference to `PyModule_Create2' /usr/bin/ld: ../python/3/libmu_py/.libs/libmu_py.so: undefined reference to `PyDict_SetItemString' /usr/bin/ld: ../python/3/libmu_py/.libs/libmu_py.so: undefined reference to `PySys_SetArgv' --- End Message --- --- Begin Message --- Source: mailutils Source-Version: 1:3.8-1 Done: Jordi Mallach We believe that the bug you reported is fixed in the latest version of mailutils, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jordi Mallach (supplier of updated mailutils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Mar 2020 22:30:43 +0100 Source: mailutils Binary: libmailutils-dev libmailutils-dev-dbgsym libmailutils6 libmailutils6-dbgsym libmu-dbm6 libmu-dbm6-dbgsym mailutils mailutils-common mailutils-comsatd mailutils-comsatd-dbgsym mailutils-dbgsym mailutils-doc mailutils-guile mailutils-imap4d
Bug#954787: marked as done (uwsgi FTBFS against ruby 2.7)
Your message dated Thu, 02 Apr 2020 15:01:10 +
with message-id
and subject line Bug#954787: fixed in uwsgi 2.0.18-9
has caused the Debian Bug report #954787,
regarding uwsgi FTBFS against ruby 2.7
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.)
--
954787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uwsgi
Version: 2.0.18-8
Severity: serious
User pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: ruby2.7-transition
Dear Maintainer,
We are removing ruby 2.5 support and src:uwsgi FTBFS against ruby 2.7, check
this build log:
https://buildd.debian.org/status/fetch.php?pkg=uwsgi=amd64=2.0.18-8%2Bb1=1584640520=0
The attached debdiff fixes the FTBFS.
Thanks for considering the patch!
--
Lucas Kanashiro
diff -Nru uwsgi-2.0.18/debian/changelog uwsgi-2.0.18.new/debian/changelog
--- uwsgi-2.0.18/debian/changelog 2020-02-28 11:19:58.0 -0300
+++ uwsgi-2.0.18.new/debian/changelog 2020-03-23 10:58:08.173556963 -0300
@@ -1,3 +1,12 @@
+uwsgi (2.0.18-9) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Allow build against ruby2.7
++ d/control: update ruby binary name from uwsgi-plugin-rack-ruby2.5 to
+ uwsgi-plugin-rack-ruby2.7
+
+ -- Lucas Kanashiro Mon, 23 Mar 2020 10:54:14
-0300
+
uwsgi (2.0.18-8) unstable; urgency=medium
* fix have uwsgi-plugin-python3 provide virtual httpd-wsgi3
diff -Nru uwsgi-2.0.18/debian/control uwsgi-2.0.18.new/debian/control
--- uwsgi-2.0.18/debian/control 2020-02-28 11:14:05.0 -0300
+++ uwsgi-2.0.18.new/debian/control 2020-03-23 10:54:12.629262461 -0300
@@ -827,7 +827,7 @@
This package provides Python 3 WSGI plugin for uWSGI
(linked with Python 3 runtime).
-Package: uwsgi-plugin-rack-ruby2.5
+Package: uwsgi-plugin-rack-ruby2.7
Architecture: any
Depends:
uwsgi-core (= ${binary:Version}),
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.18-9
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
uwsgi, 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 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated uwsgi package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 23 Mar 2020 15:44:29 +0100
Source: uwsgi
Binary: libapache2-mod-ruwsgi libapache2-mod-ruwsgi-dbg libapache2-mod-uwsgi
libapache2-mod-uwsgi-dbg python-uwsgidecorators python3-uwsgidecorators uwsgi
uwsgi-app-integration-plugins uwsgi-core uwsgi-dbg uwsgi-dev uwsgi-emperor
uwsgi-extra uwsgi-infrastructure-plugins uwsgi-plugin-alarm-curl
uwsgi-plugin-alarm-xmpp uwsgi-plugin-asyncio-python
uwsgi-plugin-asyncio-python3 uwsgi-plugin-curl-cron uwsgi-plugin-emperor-pg
uwsgi-plugin-fiber uwsgi-plugin-gccgo uwsgi-plugin-geoip
uwsgi-plugin-gevent-python uwsgi-plugin-gevent-python3 uwsgi-plugin-glusterfs
uwsgi-plugin-graylog2 uwsgi-plugin-greenlet-python
uwsgi-plugin-greenlet-python3 uwsgi-plugin-jvm-openjdk-11
uwsgi-plugin-jwsgi-openjdk-11 uwsgi-plugin-ldap uwsgi-plugin-lua5.1
uwsgi-plugin-lua5.2 uwsgi-plugin-mono uwsgi-plugin-psgi uwsgi-plugin-python
uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.7 uwsgi-plugin-rados
uwsgi-plugin-rbthreads uwsgi-plugin-ring-openjdk-11 uwsgi-plugin-router-access
uwsgi-plugin-servlet-openjdk-11
uwsgi-plugin-sqlite3 uwsgi-plugin-tornado-python uwsgi-plugin-tornado-python3
uwsgi-plugin-xslt uwsgi-plugins-all
uwsgi-src
Architecture: source amd64 all
Version: 2.0.18-9
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team
Changed-By: Jonas Smedegaard
Description:
libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi
libapache2-mod-uwsgi - uwsgi module for Apache2 (mod_uwsgi)
libapache2-mod-uwsgi-dbg - debugging symbols for Apache2 mod_uwsgi
python-uwsgidecorators - module of decorators for elegant access to uWSGI API
(Python 2)
python3-uwsgidecorators - module of decorators for elegant access to uWSGI API
(Python 3)
uwsgi -
Bug#936825: marked as done (lazyarray: Python2 removal in sid/bullseye)
Your message dated Thu, 02 Apr 2020 15:00:19 + with message-id and subject line Bug#936825: fixed in lazyarray 0.3.3-1 has caused the Debian Bug report #936825, regarding lazyarray: 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.) -- 936825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lazyarray Version: 0.1.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:lazyarray 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: lazyarray Source-Version: 0.3.3-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of lazyarray, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated lazyarray package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 05 Mar 2020 13:26:30 +0100 Source: lazyarray Binary: python3-lazyarray Architecture: source all Version: 0.3.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Description: python3-lazyarray - Python module providing a NumPy-compatible lazily-evaluated array Closes: 782922 936825 Changes: lazyarray (0.3.3-1) unstable; urgency=medium . * Team upload. * New upstream version (using latest commit) * Take over into Debian Science team maintenance * Add watch file * Switch to Python3 Closes: #936825, #782922 * Standards-Version: 4.5.0 (routine-update) * debhelper-compat 12 (routine-update) * Testsuite: autopkgtest-pkg-python (routine-update) * Secure URI in copyright format (routine-update) * Add salsa-ci file (routine-update) * Use secure URI in Homepage field. * Point watch file to github * Set upstream metadata fields:
Bug#936659: marked as done (gr-hpsdr: Python2 removal in sid/bullseye)
Your message dated Thu, 02 Apr 2020 15:00:14 + with message-id and subject line Bug#936659: fixed in gr-hpsdr 1.2.1-1 has caused the Debian Bug report #936659, regarding gr-hpsdr: 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.) -- 936659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gr-hpsdr Version: 1.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:gr-hpsdr 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: gr-hpsdr Source-Version: 1.2.1-1 Done: bott...@debian.org (A. Maitland Bottoms) We believe that the bug you reported is fixed in the latest version of gr-hpsdr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated gr-hpsdr 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: Fri, 27 Mar 2020 20:09:58 -0400 Source: gr-hpsdr Binary: gr-hpsdr gr-hpsdr-dbgsym libgnuradio-hpsdr1.2.1 libgnuradio-hpsdr1.2.1-dbgsym Architecture: source amd64 Version: 1.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: A. Maitland Bottoms Description: gr-hpsdr - gnuradio interface module for OpenHPSDR protocol 1 libgnuradio-hpsdr1.2.1 - gnuradio library for OpenHPSDR protocol 1 Closes: 936659 Changes: gr-hpsdr (1.2.1-1) unstable; urgency=medium . * New upstream tag * port to gnuradio 3.8, Python3 (Closes: #936659) * DH 12, bump S-V, priority optional. * Move Vcs headers to salsa. (Thanks Christoph Berg) Checksums-Sha1: 9792da0401e4e6c84cb07f5185903bfa6a5608c7 2164 gr-hpsdr_1.2.1-1.dsc 434567232d3a6320029e72e6672122b091963904 83816 gr-hpsdr_1.2.1.orig.tar.xz 59c41927470e3c53ea247d87e172db43c49e8064 53048 gr-hpsdr_1.2.1-1.debian.tar.xz
Bug#875579: marked as done (FTBFS with Java 9: library path guessed wrong)
Your message dated Thu, 02 Apr 2020 15:00:18 + with message-id and subject line Bug#875579: fixed in jcc 3.6-1 has caused the Debian Bug report #875579, regarding FTBFS with Java 9: library path guessed wrong 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.) -- 875579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jcc Version: 2.22 Severity: normal User: debian-j...@lists.debian.org Usertags: default-java9 This package fails to build with default-jdk pointing to openjdk-9-jdk. Please fix it, so that we can start the transition to Java 9. The wiki has some common problems and their solutions: https://wiki.debian.org/Java/Java9Pitfalls The guess of the path of the libraries is wrong: https://sources.debian.net/src/jcc/2.22-1/debian/rules/#L24 See the wiki about "/jre". Build log: x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -W[...] -L/usr/lib/jvm/default-java/jre/lib/amd64 -ljava -L/usr/lib/jvm/default-java/jre/lib/amd64/server -ljvm [...] /usr/bin/ld: cannot find -ljava /usr/bin/ld: cannot find -ljvm collect2: error: ld returned 1 exit status Cheers, Chris. --- End Message --- --- Begin Message --- Source: jcc Source-Version: 3.6-1 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of jcc, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated jcc 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: Sat, 15 Feb 2020 23:19:15 -0300 Source: jcc Binary: python3-jcc Architecture: source amd64 Version: 3.6-1 Distribution: unstable Urgency: medium Maintainer: Emmanuel Arias Changed-By: Emmanuel Arias Description: python3-jcc - generator for a Python extension from Java classes (Python 3) Closes: 875579 885955 922568 Changes: jcc (3.6-1) unstable; urgency=medium . [ Emmanuel Arias ] * New upstream version 3.6 * New maintainer (Closes: #922568): - Add myself to Maintainer field on d/control. * Bump debhelper to 12 (from 9.2): - Update debhelper to debhelper-compat on d/control Build-Depends. * Update Vcs-* repository to salsa repository. * Add myself on debian/* files copyright on d/copyright. * Bump Standard-Version to 4.4.1 * d/control: add autopkgtest-pkg-python * Remove Python2 support. * d/control: Remove X-Python-Version for Python 2 * d/salsa-ci.yml: enable salsa-ci. * d/gbp.conf: add gbp.conf file. . [Ludovico Cavedon] * Fix jdk path with Java 9 (Closes: #875579). * Fall-back to client-mode JVM is the server-mode one is not available (Closes: #885955). * Refresh patches. * Create python-jcc and python3-jcc packages, and make jcc a transitional one. Expand the "default-jdk" symlink at build time, so the run-time dependency is on the correct JDK version. * Make sure to depend on the JRE package we built against. Do not link against libjava as it is not necessary. * Change priority extra to optional. * No longer remove JCC.egg-info/SOURCES.txt during clean. * Add lintian-overrides for JRE rpath (needed because libjvm.so does not have an SONAME). * Build library with hardening=+all hardening flags. Checksums-Sha1: 4f4a48a9a7a2a6a856a5eb25ce40e2405836891f 1896 jcc_3.6-1.dsc 85f7202afd187c1dc75c998f962acc7006a731ee 185005 jcc_3.6.orig.tar.gz 37af9215a2f598c480914fcb28d8b60c9d0ab3e0 7164 jcc_3.6-1.debian.tar.xz 8b697551585b5383ca7e1005c0912fa54e9ebb9e 8915 jcc_3.6-1_amd64.buildinfo 39e0736d2d498a5cb4bd587b2d0ddb128a104a64 241268 python3-jcc_3.6-1_amd64.deb Checksums-Sha256: 5c10201f666e379ef51206b286d43db0fbcb66145445ddc94c3a91387fa43bcb 1896 jcc_3.6-1.dsc 375f25b7186a67327ba9c031ee357b85c17d1569f4c2dd1d2fccea39eb670048 185005 jcc_3.6.orig.tar.gz d5deff39a215a84492974c03b310191650c2ef1f4fbf10b404b167d6e93ba805 7164 jcc_3.6-1.debian.tar.xz 9a1f4f7567704b6eab8cc5741d52abb2703dcda7e1a82a0bb215356b04d4d928 8915 jcc_3.6-1_amd64.buildinfo
Bug#955555: gitlab: uninitialized constant APIGuard
Package: gitlab Version: 12.6.8-3 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, I upgraded packages: Start-Date: 2020-04-02 10:00:27 Commandline: apt-get dist-upgrade Install: libllvm10:amd64 (1:10.0.0-1, automatic), ruby-sync:amd64 (0.5.0-2, automatic) Upgrade: libpython3.7-minimal:amd64 (3.7.7-1, 3.7.7-1+b1), python3-werkzeug:amd64 (0.16.1+dfsg1-1, 0.16.1+dfsg1-2), glib-networking-services:amd64 (2.64.0-1, 2.64.1-1), libpython3.8-dbg:amd64 (3.8.2-1, 3.8.2-1+b1), libpython3.8-dev:amd64 (3.8.2-1, 3.8.2-1+b1), php-phpseclib:amd64 (2.0.25-1, 2.0.26-1), libgirepository-1.0-1:amd64 (1.62.0-5+b1, 1.64.0-2), libpython3.8-minimal:amd64 (3.8.2-1, 3.8.2-1+b1), glib-networking:amd64 (2.64.0-1, 2.64.1-1), dash:amd64 (0.5.10.2-6, 0.5.10.2-7), ruby-memoist:amd64 (0.16.2-1, 0.16.2-2), ruby-tins:amd64 (1.1.0-1, 1.1.0-2), libhiredis0.14:amd64 (0.14.0-6, 0.14.1-1), libffi-dev:amd64 (3.3-3, 3.3-4), libdbd-pg-perl:amd64 (3.10.4-1, 3.10.5-1), yarnpkg:amd64 (1.19.1-1, 1.21.1-2), nodejs:amd64 (10.17.0~dfsg-2, 10.19.0~dfsg-3), libpython3.8:amd64 (3.8.2-1, 3.8.2-1+b1), python3.7:amd64 (3.7.7-1, 3.7.7-1+b1), python3.8:amd64 (3.8.2-1, 3.8.2-1+b1), ruby-mini-magick:amd64 (4.9.2-1.1, 4.9.5-2), bubblewrap:amd64 (0.4.0-1, 0.4.1-1), node-d3-quadtree:amd64 (1.0.6-2, 1.0.7-1), libpq5:amd64 (12.2-1+b1, 12.2-4), libpython3.7-stdlib:amd64 (3.7.7-1, 3.7.7-1+b1), glib-networking-common:amd64 (2.64.0-1, 2.64.1-1), python3.7-minimal:amd64 (3.7.7-1, 3.7.7-1+b1), ruby-state-machines-activemodel:amd64 (0.5.1-3, 0.7.1-2), libpq-dev:amd64 (12.2-1+b1, 12.2-4), npm:amd64 (6.14.2+ds-2, 6.14.3+ds-1), python3-future:amd64 (0.18.2-1, 0.18.2-2), postgresql-12:amd64 (12.2-1+b1, 12.2-4), gir1.2-glib-2.0:amd64 (1.62.0-5+b1, 1.64.0-2), python3.8-minimal:amd64 (3.8.2-1, 3.8.2-1+b1), python3-acme:amd64 (1.1.0-1, 1.3.0-2), libconfuse-common:amd64 (3.2.2+dfsg-1, 3.2.2+dfsg-2), ruby-omniauth:amd64 (1.9.0-1, 1.9.1-1), shared-mime-info:amd64 (1.10-1, 1.15-1), libnode-dev:amd64 (10.17.0~dfsg-2, 10.19.0~dfsg-3), libwnck-3-0:amd64 (3.32.0-1, 3.36.0-1), ruby-warden:amd64 (1.2.3-2, 1.2.8-1), libpython3.8-stdlib:amd64 (3.8.2-1, 3.8.2-1+b1), libnode64:amd64 (10.17.0~dfsg-2, 10.19.0~dfsg-3), libwnck-3-common:amd64 (3.32.0-1, 3.36.0-1), libpcap0.8:amd64 (1.9.1-2, 1.9.1-3), libffi7:amd64 (3.3-3, 3.3-4), python3.8-dbg:amd64 (3.8.2-1, 3.8.2-1+b1), python3.8-dev:amd64 (3.8.2-1, 3.8.2-1+b1), libconfuse2:amd64 (3.2.2+dfsg-1, 3.2.2+dfsg-2), postgresql-client-12:amd64 (12.2-1+b1, 12.2-4) End-Date: 2020-04-02 10:05:57 Start-Date: 2020-04-02 10:14:16 Commandline: apt-get -t unstable install gitlab-shell Upgrade: gitlab-shell:amd64 (10.3.0+debian-3.1, 11.0.0+debian-2) End-Date: 2020-04-02 10:14:37 After that gitlab stop starting. The error is: rake aborted! NameError: uninitialized constant APIGuard /usr/share/gitlab/lib/gitlab/patch/draw_route.rb:32:in `instance_eval' /usr/share/gitlab/lib/api/api.rb:5:in `' /usr/share/gitlab/lib/api/api.rb:4:in `' /usr/share/gitlab/lib/api/api.rb:3:in `' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies/interlock.rb:14:in `block in loading' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/concurrency/share_lock.rb:151:in `exclusive' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies/interlock.rb:13:in `loading' (eval):4:in `draw_route' /usr/share/gitlab/lib/gitlab/patch/draw_route.rb:32:in `instance_eval' /usr/share/gitlab/lib/gitlab/patch/draw_route.rb:32:in `draw_route' /usr/share/gitlab/lib/gitlab/patch/draw_route.rb:19:in `draw_ce' /usr/share/gitlab/lib/gitlab/patch/draw_route.rb:13:in `draw' /usr/share/gitlab/config/routes.rb:171:in `block in ' /usr/share/rubygems-integration/all/gems/actionpack-5.2.4.1/lib/action_dispatch/routing/route_set.rb:432:in `instance_exec' /usr/share/rubygems-integration/all/gems/actionpack-5.2.4.1/lib/action_dispatch/routing/route_set.rb:432:in `eval_block' /usr/share/rubygems-integration/all/gems/actionpack-5.2.4.1/lib/action_dispatch/routing/route_set.rb:414:in `draw' /usr/share/gitlab/config/routes.rb:4:in `' /usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application/routes_reloader.rb:41:in `block in load_paths' /usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application/routes_reloader.rb:41:in `each' /usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application/routes_reloader.rb:41:in `load_paths' /usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application/routes_reloader.rb:20:in `reload!' /usr/share/rubygems-integration/all/gems/railties-5.2.4.1/lib/rails/application.rb:168:in `reload_routes!' /usr/share/gitlab/config/application.rb:283:in `block in ' /usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/lazy_load_hooks.rb:69:in `block in execute_hook'
Bug#937565: pytest-runner: diff for NMU version 2.11.1-1.2
Control: tags 937565 + patch
Dear maintainer,
I've prepared an NMU for pytest-runner (versioned as 2.11.1-1.2). The diff
is attached to this message.
Regards.
diff -Nru pytest-runner-2.11.1/debian/changelog pytest-runner-2.11.1/debian/changelog
--- pytest-runner-2.11.1/debian/changelog 2018-09-27 13:35:32.0 -0400
+++ pytest-runner-2.11.1/debian/changelog 2020-04-02 10:40:58.0 -0400
@@ -1,3 +1,10 @@
+pytest-runner (2.11.1-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #937565
+
+ -- Sandro Tosi Thu, 02 Apr 2020 10:40:58 -0400
+
pytest-runner (2.11.1-1.1) unstable; urgency=high
* Non-maintainer upload.
diff -Nru pytest-runner-2.11.1/debian/control pytest-runner-2.11.1/debian/control
--- pytest-runner-2.11.1/debian/control 2018-09-27 13:35:32.0 -0400
+++ pytest-runner-2.11.1/debian/control 2020-04-02 10:40:38.0 -0400
@@ -5,10 +5,6 @@
Uploaders: Brian May ,
Build-Depends: debhelper (>= 9),
dh-python (>= 2.20160609~),
- python-all,
- python-pytest,
- python-setuptools,
- python-setuptools-scm,
python3-all,
python3-pytest,
python3-setuptools,
@@ -18,18 +14,6 @@
Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/pytest-runner.git
Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/pytest-runner.git
-Package: python-pytest-runner
-Architecture: all
-Depends: ${misc:Depends},
- ${python:Depends},
- python-pkg-resources,
- python-setuptools,
-Description: Invoke py.test as distutils command with dependency resolution - Python 2.x
- Setup scripts can use pytest-runner to add setup.py test support for pytest
- runner.
- .
- This package contains the Python 2 module.
-
Package: python3-pytest-runner
Architecture: all
Depends: ${misc:Depends},
diff -Nru pytest-runner-2.11.1/debian/rules pytest-runner-2.11.1/debian/rules
--- pytest-runner-2.11.1/debian/rules 2017-07-11 03:56:07.0 -0400
+++ pytest-runner-2.11.1/debian/rules 2020-04-02 10:40:47.0 -0400
@@ -4,7 +4,7 @@
export PYBUILD_NAME=pytest-runner
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_installchangelogs:
dh_installchangelogs CHANGES.rst
Processed: pytest-runner: diff for NMU version 2.11.1-1.2
Processing control commands: > tags 937565 + patch Bug #937565 [src:pytest-runner] pytest-runner: Python2 removal in sid/bullseye Added tag(s) patch. -- 937565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952041: marked as done (ruby-hoe: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Thu, 02 Apr 2020 14:34:38 + with message-id and subject line Bug#952041: fixed in ruby-hoe 3.22.1+dfsg1-1 has caused the Debian Bug report #952041, regarding ruby-hoe: FTBFS: ERROR: Test "ruby2.7" failed. 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.) -- 952041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-hoe Version: 3.21.0+dfsg1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-hoe/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"hoe\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-hoe/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-hoe/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_hoe_test.rb" > "test/test_hoe.rb" "test/test_hoe_debug.rb" "test/test_hoe_gemcutter.rb" > "test/test_hoe_package.rb" "test/test_hoe_publish.rb" "test/test_hoe_test.rb" > -v > Run options: -v --seed 6193 > > # Running: > > TestHoeGemcutter#test_gemcutter_tasks_defined = 0.00 s = . > TestHoeDebug#test_check_manifest = 0.00 s = . > TestHoeDebug#test_check_manifest_generated = 0.00 s = . > TestHoeDebug#test_check_manifest_missing = 0.00 s = . > TestHoePackage#test_prerelease_version_regular = 0.00 s = . > TestHoePackage#test_prerelease_version_prerelease = 0.00 s = . > TestHoePackage#test_prerelease_version_pre = 0.00 s = . > TestHoeTest#test_make_test_cmd_with_different_testlibs = 0.00 s = . > TestHoe#test_activate_plugins = 0.01 s = . > TestHoe#test_extensions = 0.01 s = . > TestHoe#test_initialize_plugins_hoerc = 0.00 s = . > TestHoe#test_class_bad_plugins = 0.00 s = . > TestHoe#test_license = 0.00 s = . > TestHoe#test_metadata = 0.00 s = . > TestHoe#test_multiple_calls_to_license = 0.00 s = . > TestHoe#test_plugins = 0.00 s = . > TestHoe#test_file_read_utf = 0.00 s = . > TestHoe#test_with_config_overrides = 0.00 s = . > TestHoe#test_no_license = 0.00 s = . > TestHoe#test_initialize_intuit_ambiguous = 0.00 s = . > TestHoe#test_read_manifest = 0.00 s = . > TestHoe#test_parse_urls_hash = 0.00 s = . > TestHoe#test_parse_urls_ary = 0.00 s = . > TestHoe#test_with_config_default = 0.00 s = . > TestHoe#test_rename = 0.00 s = . > TestHoe#test_activate_plugins_hoerc = 0.00 s = . > TestHoe#test_class_load_plugins = 0.00 s = . > TestHoe#test_initialize_intuit = 0.00 s = . > TestHoe#test_possibly_better = 0.00 s = F > TestHoe#test_nosudo = 0.00 s = . > TestHoe#test_setting_licenses = 0.00 s = . > TestHoePublish#test_make_rdoc_cmd = 0.00 s = . > > Finished in 0.084995s, 376.4912 runs/s, 1153.0043 assertions/s. > > 1) Failure: > TestHoe#test_possibly_better [/<>/test/test_hoe.rb:274]: > Expected: 2020-02-23 00:00:00 UTC > Actual: 2020-02-06 00:00:00 UTC > > 32 runs, 98 assertions, 1 failures, 0 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_hoe_test.rb" > "test/test_hoe.rb" "test/test_hoe_debug.rb" "test/test_hoe_gemcutter.rb" > "test/test_hoe_package.rb" "test/test_hoe_publish.rb" "test/test_hoe_test.rb" > -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby2.7" failed. The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-hoe_3.21.0+dfsg1-1_unstable.log A list of current common problems and possible solutions is available at
Processed: py2removal bugs severity updates - 2020-04-02 14:36:13.062615+00:00
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 > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-pytest-runner is a module and has 0 external rdeps or not in testing > severity 937565 serious Bug #937565 [src:pytest-runner] pytest-runner: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954826: marked as done (libgcc-8-dev: depends on unavailable version of libgcc-s1)
Your message dated Thu, 02 Apr 2020 14:22:14 + with message-id and subject line Bug#954826: fixed in gcc-8 8.4.0-3 has caused the Debian Bug report #954826, regarding libgcc-8-dev: depends on unavailable version of libgcc-s1 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.) -- 954826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgcc-8-dev Version: 8.4.0-2 Severity: grave The latest version of gcc-8 is not installable because libgcc-8-dev depends on libgcc-s1 (>= 1:8.4.0-2), but the version of libgcc-s1 in the archive does not have an epoch and is therefore too low to fulfill this requirement. The same holds for libgcc-7-dev 7.5.0-6. --- End Message --- --- Begin Message --- Source: gcc-8 Source-Version: 8.4.0-3 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-8, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Apr 2020 15:30:15 +0200 Source: gcc-8 Architecture: source Version: 8.4.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 954826 Changes: gcc-8 (8.4.0-3) unstable; urgency=medium . * Update to git 20200402 from the gcc-8 branch. - Fix PR target/93819 (PPC), PR target/87583 (PPC), PR gcov-profile/91601, PR lto/94249, PR c++/84733, PR fortran/94030, PR fortran/92775, PR fortran/93484. * Fix libgcc-sN dependency generation. Closes: #954826. Checksums-Sha1: d7cfa6375fea311e617c6a69856257f8f2efd729 19729 gcc-8_8.4.0-3.dsc 747f057570ae2f9ee31127978b58f83133b259de 655645 gcc-8_8.4.0-3.diff.gz 34f68d5294b368043b8c79bebec74127431923dc 9443 gcc-8_8.4.0-3_source.buildinfo Checksums-Sha256: 4a45f6c7948fa65c8813dbef87c5f382586e5f70fca2f64dbe2ecf23c7ffdd38 19729 gcc-8_8.4.0-3.dsc 38e5a2b6168a63f769c202de9a642cff22733650e55cb6a96e0cb30780aed036 655645 gcc-8_8.4.0-3.diff.gz f29a324696f9683d9dd5bb4837dafb18cc48d8f06a4aba3c5f58472b4a2b61af 9443 gcc-8_8.4.0-3_source.buildinfo Files: 2374c313066556a48ad62c62b4d09d8a 19729 devel optional gcc-8_8.4.0-3.dsc dc6901d6f7d221a41875c573ccc52c1e 655645 devel optional gcc-8_8.4.0-3.diff.gz cf31a11d62897fd5c6e335240342ca04 9443 devel optional gcc-8_8.4.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl6F6eMQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9Wk8D/90V6tPPn7MkJDMWw0x+WTAPKdJHmVlBBQy gvtTm4Q8ASHvmNJm6pD99mFEBmFbA1RJuUcMTMPzGK1v+Fegt4mf6BBNYErqDlN8 S3sJvir4dPDngZalO1jPRaVs5R1c7XdFJe4EucpBYqrlufb/+5FpPkvY4KSM6wG/ WQMmh2w440F3+74ABgr1DJmvYNl/yKPAAvsO9f4sd1w/8LMSmqa5mZ7fN7FH3vL4 7wMXovDFYxFBg6BkEHqZz25x0xOjujqEe+Zrt+k8Kh1KL+d2XjO5B3hA/JJSE5Bt whO/58pOId3yTu7eSOhNoOU5SwgEMkmDanAXY92XXGq4hhZw49nhqBOWILVlngdN GWGCq7TuRUowsXw2Q61COf06ELKTGqVsZSstPNqwivqVvOs05DcfUBXTk9tTSUMG r8HITiBuU66IDAzpgbNzrSQocZMB5ShZ9K5SDOjUaBEcxWH3J4Kq6aWFhDXqoS6M HP9+99aU09x1NQK9BjxLCgzKtQS+a4HtXxByks918wtrHs9k6U70ZRSDc9cGPFtM MwXjnwkoA4zRgZsTA9E08vb4yNeLP1ENZt1Ll3Z4XQsF9/hS8EExJFJiL8mtBnkQ g2UvGCMiOpUd+KDJVI5ABlykinbRayL1ocOmkJCUWqitIEbln5qStkWpl3r+fEBw peYjlcf6uw== =F1Rf -END PGP SIGNATURE End Message ---
Processed: Closing fv crashes XWayland and Gnome
Processing control commands: > reassign -1 xwayland 2:1.20.4-1 Bug #954121 [ftools-fv] ftools-fv: Closing fv crashes XWayland and Gnome Bug reassigned from package 'ftools-fv' to 'xwayland'. No longer marked as found in versions ftools-fv/5.5+dfsg-2. Ignoring request to alter fixed versions of bug #954121 to the same values previously set Bug #954121 [xwayland] ftools-fv: Closing fv crashes XWayland and Gnome Marked as found in versions xorg-server/2:1.20.4-1. > affects -1 ftools-fv Bug #954121 [xwayland] ftools-fv: Closing fv crashes XWayland and Gnome Added indication that 954121 affects ftools-fv > severity -1 important Bug #954121 [xwayland] ftools-fv: Closing fv crashes XWayland and Gnome Severity set to 'important' from 'critical' -- 954121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 955511 to ftp.debian.org, severity of 955511 is normal ...
Processing commands for cont...@bugs.debian.org: > reassign 955511 ftp.debian.org Bug #955511 [src:xbmc-pvr-addons] xbmc-pvr-addons: Should be removed from testing Bug reassigned from package 'src:xbmc-pvr-addons' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #955511 to the same values previously set Ignoring request to alter fixed versions of bug #955511 to the same values previously set > severity 955511 normal Bug #955511 [ftp.debian.org] xbmc-pvr-addons: Should be removed from testing Severity set to 'normal' from 'serious' > retitle 955511 RM: xbmc-pvr-addons -- RoM; builds only obsolete transitional > packages Bug #955511 [ftp.debian.org] xbmc-pvr-addons: Should be removed from testing Changed Bug title to 'RM: xbmc-pvr-addons -- RoM; builds only obsolete transitional packages' from 'xbmc-pvr-addons: Should be removed from testing'. > thanks Stopping processing here. Please contact me if you need assistance. -- 955511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954121: Closing fv crashes XWayland and Gnome
Control: reassign -1 xwayland 2:1.20.4-1 Control: affects -1 ftools-fv Control: severity -1 important Hi, I do not see why this is a bug in ftools-fv: an X server should never just crash when some commands are sent. The crash also happens when I start ftools-fv on a remote computer and use xwayland just as the X11 server via network. The crash also does not happen with the standard xorg server, but only with xwayland. Therefore, I reassign it to that package. I however have no idea how to debug this. Best Ole
Processed: reassign 955442 to src:openssl, fixed 955442 in 1.1.1f-1, affects 955442, tagging 955144 ...
Processing commands for cont...@bugs.debian.org:
> reassign 955442 src:openssl 1.1.1e-1
Bug #955442 {Done: Sebastian Andrzej Siewior }
[src:openssl, src:libio-socket-ssl-perl] openssl breaks libio-socket-ssl-perl
autopkgtest: 20 times "not ok"
Bug reassigned from package 'src:openssl, src:libio-socket-ssl-perl' to
'src:openssl'.
No longer marked as found in versions libio-socket-ssl-perl/2.067-1 and
openssl/1.1.1e-1.
No longer marked as fixed in versions openssl/1.1.1f-1.
Bug #955442 {Done: Sebastian Andrzej Siewior }
[src:openssl] openssl breaks libio-socket-ssl-perl autopkgtest: 20 times "not
ok"
Marked as found in versions openssl/1.1.1e-1.
> fixed 955442 1.1.1f-1
Bug #955442 {Done: Sebastian Andrzej Siewior }
[src:openssl] openssl breaks libio-socket-ssl-perl autopkgtest: 20 times "not
ok"
Marked as fixed in versions openssl/1.1.1f-1.
> affects 955442 + src:libio-socket-ssl-perl
Bug #955442 {Done: Sebastian Andrzej Siewior }
[src:openssl] openssl breaks libio-socket-ssl-perl autopkgtest: 20 times "not
ok"
Added indication that 955442 affects src:libio-socket-ssl-perl
> tags 955144 + sid experimental
Bug #955144 {Done: Sylvestre Ledru } [libclang-dev]
libclang-dev: package could not be installed
Added tag(s) sid and experimental.
> tags 955488 + sid bullseye
Bug #955488 [nat-rtsp-dkms] nat-rtsp-dkms: Does not build with kernel >= 5.3
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
955144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955144
955442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955442
955488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#885506: bumping severity of pygtk bugs
On Thu, Apr 02, 2020 at 02:58:38PM +0200, Thibaut Paumard wrote: > Le 01/04/2020 à 23:13, Moritz Mühlenhoff a écrit : > > On Mon, Oct 07, 2019 at 04:53:03PM +0200, Thibaut Paumard wrote: > >> Dear Jeremy, > >> > >> Thanks, I have warned upstream that YAO will be removed if not updated > >> to Python 3 and Gtk 3. > > > > It's now the last package blocking the removal of pygtk, let's remove it. > > > > Sure. > > Did you already/ can you fill the RM bug? Ack, I'll do that later the evening. Cheers, Moritz
Bug#954584: marked as done (gtk+3.0: FTBFS: testsuite/reftests/flipping-icons.ui: FAIL)
Your message dated Thu, 02 Apr 2020 13:49:16 + with message-id and subject line Bug#954584: fixed in gtk+3.0 3.24.16-1 has caused the Debian Bug report #954584, regarding gtk+3.0: FTBFS: testsuite/reftests/flipping-icons.ui: FAIL 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.) -- 954584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtk+3.0 Version: 3.24.14-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/debian/build/deb' > make[4]: Leaving directory '/<>/debian/build/deb' > make[3]: Leaving directory '/<>/debian/build/deb' > make[2]: *** [Makefile:747: check-recursive] Error 1 > make[2]: Target 'check' not remade because of errors. > make[2]: Leaving directory '/<>/debian/build/deb' > dh_auto_test: error: cd debian/build/deb && make -j4 check VERBOSE=1 -k check > -j1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/03/21/gtk+3.0_3.24.14-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: gtk+3.0 Source-Version: 3.24.16-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of gtk+3.0, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated gtk+3.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Apr 2020 13:15:25 +0100 Source: gtk+3.0 Architecture: source Version: 3.24.16-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 953105 954584 Changes: gtk+3.0 (3.24.16-1) unstable; urgency=medium . * Team upload * New upstream release * Drop patches that came from upstream * d/p/supp-Use-a-single-suppressions-file-for-lib-lib64-and-mul.patch: Add patch to make valgrind suppressions match Debian libraries * Update forwarding status for some patches that were sent upstream * d/p/Don-t-test-default-constructed-GdkPixbuf-properties.patch: Drop patch. Build-depend on gdk-pixbuf 2.40 instead of working around a bug in older versions. * d/rules: Mark some reftests as allowed to fail. These reftests are sensitive to the build environment (exact versions of Pango, fonts etc.) and are disabled in upstream's CI. (Closes: #954584) * d/p/updateiconcache-Sort-list-of-entries.patch: Backport patch from GTK 4 to make the icon cache reproducible (Closes: #953105) * d/p/build-Generate-gdk.gresource.xml-in-sorted-order.patch: Sort GDK resources to improve reproducibility. The combination of this and fixing #953105 should hopefully make the package reliably reproducible. * d/README.source: Write down how to inspect reftest failures Checksums-Sha1: 681feca029967a2d0e8581372dc6b643e45d9a0e 4040 gtk+3.0_3.24.16-1.dsc 407496ffcf762dffb06bd71f40145fcaf941e130 20417592 gtk+3.0_3.24.16.orig.tar.xz 19492382da45b33b5bda9de642160c984a963eff 157004 gtk+3.0_3.24.16-1.debian.tar.xz 7d567c9583ac359e2c49095fc935481326a7cc8b 15037 gtk+3.0_3.24.16-1_source.buildinfo Checksums-Sha256: 7bdf9e745b7054ba9f1ed3a4c3e0a318e40afaf952df9fc0d060fc1b7a9b2ec2 4040 gtk+3.0_3.24.16-1.dsc 0d5e1e1494101b8c0c63c0526180780559eee469f021ca0d714018b20fa3d8e8 20417592 gtk+3.0_3.24.16.orig.tar.xz 387e2cb38a4c685ea13324b512b77c96e3a9007126450e098b474bccdc396eed 157004 gtk+3.0_3.24.16-1.debian.tar.xz c79ac28e5d53f0f1bcbf74249f09c200c4ee72755eb2d7da7ce86aa80560b0e4 15037
Bug#954826: marked as done (libgcc-8-dev: depends on unavailable version of libgcc-s1)
Your message dated Thu, 02 Apr 2020 13:33:36 + with message-id and subject line Bug#954826: fixed in gcc-10 10-20200402-1 has caused the Debian Bug report #954826, regarding libgcc-8-dev: depends on unavailable version of libgcc-s1 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.) -- 954826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgcc-8-dev Version: 8.4.0-2 Severity: grave The latest version of gcc-8 is not installable because libgcc-8-dev depends on libgcc-s1 (>= 1:8.4.0-2), but the version of libgcc-s1 in the archive does not have an epoch and is therefore too low to fulfill this requirement. The same holds for libgcc-7-dev 7.5.0-6. --- End Message --- --- Begin Message --- Source: gcc-10 Source-Version: 10-20200402-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-10, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-10 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Apr 2020 15:01:48 +0200 Source: gcc-10 Architecture: source Version: 10-20200402-1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 954826 954954 Changes: gcc-10 (10-20200402-1) unstable; urgency=medium . * GCC snapshot, taken from the trunk (20200402, 86c92411320). * Fix PR target/94254 (PPC), proposed patch. * Update libstdc++6 symbols file for armel. Closes: #954954. * libgcc-sN: Provide libgcc-sN with an epoch version to rebuild gcc-8. Closes: #954826. Checksums-Sha1: 7d28aa661c2b8cad975ccdb2ce7be82a1cc0ccb6 27934 gcc-10_10-20200402-1.dsc fd4eb7c3180f6193121b95c6d5f2901807ac9e37 89075849 gcc-10_10-20200402.orig.tar.gz 2038a1099c1b7cb96f337ef2f5ce68c6033a55da 557380 gcc-10_10-20200402-1.debian.tar.xz 18584bea44f10c4952628b89d4a8762e3ab55eed 10689 gcc-10_10-20200402-1_source.buildinfo Checksums-Sha256: 00d2ee94c24b8b6eee2ee43b94c7baf80399198d2fcf182882676f6da0a8f149 27934 gcc-10_10-20200402-1.dsc 2a2471ede4f0a9ad7d5566d187cb1ab71b804f487d913c7d449dcfc70cf145a2 89075849 gcc-10_10-20200402.orig.tar.gz ad7e185c8f49bfc12589dbc92b15ce5238f16474e681518381d38153183a3e2a 557380 gcc-10_10-20200402-1.debian.tar.xz 06a2286293e61faf553d20b7c3859e9508435cf18234e204419888dc37e116d4 10689 gcc-10_10-20200402-1_source.buildinfo Files: ff343bad55e374b56b552bd0a7e95179 27934 devel optional gcc-10_10-20200402-1.dsc ddb79b1f0e75c38e1cbd838945eb2d05 89075849 devel optional gcc-10_10-20200402.orig.tar.gz ae14d0625e9479be6b454d37340bc643 557380 devel optional gcc-10_10-20200402-1.debian.tar.xz 8d4e8496c7faf863146b76b560dca9cb 10689 devel optional gcc-10_10-20200402-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl6F5JwQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9Yz8EACcN6RlP7F6ex0/ViK61LjXVDRwIGjcSfbf o593egOxJEuCanyOiw6ZWKVAZeZ+sXLK7T3Sd96k3BNrG5tiPnyvjQ2km9tdoWu5 F6mgPH7sarxSf0xPyGUaeK80zx3lPWmUhRhh2ZUVf+0DgfCBimm8txScO7GjM4eb wEHEuyq02wDm78EDA/4tvJhn/meWWMdIM7VYoOdWVvND7ilISDoE95AbSxn2WbUe DXBVlYu9S0aZpnWG19dHRcB90M8MHAsUzkaQNu3A0CyDezcN5z6IA10DhIe/lXop YFdCMPlW1VXE1abBeajBlD6K2FE0GMLOBV5m+DeC/208lDjLT+zez5Ms21m/2DZq y896nNcNCZFiPzaXFOLMD9ZO69LKHshC3OfA8ZltZmNhPJ8AHpuFF68gWo54kiuS PF3r2NJXwSP8CMQQ+MvtNML1BgwPiE8yekl+BNbZEiYnanwlgqWYiXrTdYpX+Fs3 6Ham8R4Tx3qoKFkP5sxN6n8lkfRHjmJwkHl7KUDhmFpOqGlCzkcV3oXqBqjg3CG0 3/G3RjiM4BRMqWvMPYtbHg6mO3uNJ2FHKV57Cs/hh+RD0nzD6R1b46lnMfb2D9KS R+1uCBHmqnYTf8SZt/1ZGuy1a/86WGb1XoxkufRiYo0HdsfwRqFJhEQL5QjDRKSW A8PtGKM2Ew== =8wIN -END PGP SIGNATURE End Message ---
Bug#954584: marked as pending in gtk+3.0
Control: tag -1 pending Hello, Bug #954584 in gtk+3.0 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/gnome-team/gtk3/-/commit/975ef47c60c8808e7faa85aa7352992e365a34df Mark some reftests as allowed to fail These reftests are sensitive to the build environment (exact versions of Pango, fonts etc.) and are disabled in upstream's CI. Closes: #954584 (this message was generated automatically) -- Greetings https://bugs.debian.org/954584
Bug#954954: marked as done (libstdc++6: symbols file on armel incomplete)
Your message dated Thu, 02 Apr 2020 13:33:36 + with message-id and subject line Bug#954954: fixed in gcc-10 10-20200402-1 has caused the Debian Bug report #954954, regarding libstdc++6: symbols file on armel incomplete 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.) -- 954954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: libstdc++6 severity: serious Hi, It seems the symbols file for libstdc++6 is missing some symbols on armel. The build adds these with the latest version. This causes new builds that use these symbols to pick up an (unnecessary) versioned dependency on the latest gcc in unstable. As this bug sometimes causes testing migrations to block on the migration of gcc, and thus interferes with transitions, I'm filing this as serious. This currently is the case with the opencv binNMU on armel, which is blocked behind gcc-10, blocking the python3-defauls transition. Maybe the build should we configured to fail when new symbols are discovered, to avoid similar issues in the future. Thanks! Ivo --- End Message --- --- Begin Message --- Source: gcc-10 Source-Version: 10-20200402-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-10, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-10 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Apr 2020 15:01:48 +0200 Source: gcc-10 Architecture: source Version: 10-20200402-1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 954826 954954 Changes: gcc-10 (10-20200402-1) unstable; urgency=medium . * GCC snapshot, taken from the trunk (20200402, 86c92411320). * Fix PR target/94254 (PPC), proposed patch. * Update libstdc++6 symbols file for armel. Closes: #954954. * libgcc-sN: Provide libgcc-sN with an epoch version to rebuild gcc-8. Closes: #954826. Checksums-Sha1: 7d28aa661c2b8cad975ccdb2ce7be82a1cc0ccb6 27934 gcc-10_10-20200402-1.dsc fd4eb7c3180f6193121b95c6d5f2901807ac9e37 89075849 gcc-10_10-20200402.orig.tar.gz 2038a1099c1b7cb96f337ef2f5ce68c6033a55da 557380 gcc-10_10-20200402-1.debian.tar.xz 18584bea44f10c4952628b89d4a8762e3ab55eed 10689 gcc-10_10-20200402-1_source.buildinfo Checksums-Sha256: 00d2ee94c24b8b6eee2ee43b94c7baf80399198d2fcf182882676f6da0a8f149 27934 gcc-10_10-20200402-1.dsc 2a2471ede4f0a9ad7d5566d187cb1ab71b804f487d913c7d449dcfc70cf145a2 89075849 gcc-10_10-20200402.orig.tar.gz ad7e185c8f49bfc12589dbc92b15ce5238f16474e681518381d38153183a3e2a 557380 gcc-10_10-20200402-1.debian.tar.xz 06a2286293e61faf553d20b7c3859e9508435cf18234e204419888dc37e116d4 10689 gcc-10_10-20200402-1_source.buildinfo Files: ff343bad55e374b56b552bd0a7e95179 27934 devel optional gcc-10_10-20200402-1.dsc ddb79b1f0e75c38e1cbd838945eb2d05 89075849 devel optional gcc-10_10-20200402.orig.tar.gz ae14d0625e9479be6b454d37340bc643 557380 devel optional gcc-10_10-20200402-1.debian.tar.xz 8d4e8496c7faf863146b76b560dca9cb 10689 devel optional gcc-10_10-20200402-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl6F5JwQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9Yz8EACcN6RlP7F6ex0/ViK61LjXVDRwIGjcSfbf o593egOxJEuCanyOiw6ZWKVAZeZ+sXLK7T3Sd96k3BNrG5tiPnyvjQ2km9tdoWu5 F6mgPH7sarxSf0xPyGUaeK80zx3lPWmUhRhh2ZUVf+0DgfCBimm8txScO7GjM4eb wEHEuyq02wDm78EDA/4tvJhn/meWWMdIM7VYoOdWVvND7ilISDoE95AbSxn2WbUe DXBVlYu9S0aZpnWG19dHRcB90M8MHAsUzkaQNu3A0CyDezcN5z6IA10DhIe/lXop YFdCMPlW1VXE1abBeajBlD6K2FE0GMLOBV5m+DeC/208lDjLT+zez5Ms21m/2DZq y896nNcNCZFiPzaXFOLMD9ZO69LKHshC3OfA8ZltZmNhPJ8AHpuFF68gWo54kiuS PF3r2NJXwSP8CMQQ+MvtNML1BgwPiE8yekl+BNbZEiYnanwlgqWYiXrTdYpX+Fs3 6Ham8R4Tx3qoKFkP5sxN6n8lkfRHjmJwkHl7KUDhmFpOqGlCzkcV3oXqBqjg3CG0 3/G3RjiM4BRMqWvMPYtbHg6mO3uNJ2FHKV57Cs/hh+RD0nzD6R1b46lnMfb2D9KS R+1uCBHmqnYTf8SZt/1ZGuy1a/86WGb1XoxkufRiYo0HdsfwRqFJhEQL5QjDRKSW A8PtGKM2Ew== =8wIN -END PGP SIGNATURE End Message ---
Processed: tagging 955456
Processing commands for cont...@bugs.debian.org: > tags 955456 + ftbfs Bug #955456 [bitshuffle] FTBFS: test file tmp_test_filters.h5 does not exist Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 955456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#954584 marked as pending in gtk+3.0
Processing control commands: > tag -1 pending Bug #954584 [src:gtk+3.0] gtk+3.0: FTBFS: testsuite/reftests/flipping-icons.ui: FAIL Added tag(s) pending. -- 954584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955553: haproxy - unreachable maintainer
Package: src:haproxy Severity: serious Mail to the maintainer address hapr...@tracker.debian.org bounces: | host ticharich.debian.org [2607:f8f0:614:1::1274:64] | SMTP error from remote mail server after RCPT TO:: | 550 Unrouteable address Do you mean team+hapr...@tracker.debian.org? Regards, Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0
Processed: affects 951087
Processing commands for cont...@bugs.debian.org: > affects 951087 + src:dhewm3 Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail to find SDL2 Added indication that 951087 affects src:dhewm3 > thanks Stopping processing here. Please contact me if you need assistance. -- 951087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955552: xpdf: FTBFS with poppler 0.85.0: error: 'getModRegion' was not declared in this scope
Source: xpdf Version: 3.04-13exp3 Severity: serious Tags: ftbfs sid bullseye experimental Justification: fails to build from source (but built successfully in the past) Hi, xpdf/experimental FTBFS against libpoppler-dev/experimental (0.85.0-1): debian/rules override_dh_auto_build make[1]: Entering directory '/build/xpdf-3.04' x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/build/xpdf-3.04=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo -I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args -Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H -DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\" -c -o build/CoreOutputDev.o build/CoreOutputDev.cc build/CoreOutputDev.cc: In member function 'virtual void CoreOutputDev::dump()': build/CoreOutputDev.cc:50:5: error: 'getModRegion' was not declared in this scope 50 | getModRegion(, , , ); | ^~~~ compilation terminated due to -Wfatal-errors. make[1]: *** [: build/CoreOutputDev.o] Error 1 make[1]: Leaving directory '/build/xpdf-3.04' make: *** [debian/rules:50: build] Error 2 The version in sid (3.04-13) has the same problem. Andreas xpdf_3.04-13exp3.log.gz Description: application/gzip
Bug#885506: bumping severity of pygtk bugs
Le 01/04/2020 à 23:13, Moritz Mühlenhoff a écrit : > On Mon, Oct 07, 2019 at 04:53:03PM +0200, Thibaut Paumard wrote: >> Dear Jeremy, >> >> Thanks, I have warned upstream that YAO will be removed if not updated >> to Python 3 and Gtk 3. > > It's now the last package blocking the removal of pygtk, let's remove it. > Sure. Did you already/ can you fill the RM bug? Regards, Thibaut. > Cheers, > Moritz > signature.asc Description: OpenPGP digital signature
Bug#954826: libgcc-8-dev: depends on unavailable version of libgcc-s1
On 02/04/2020 11.13, Matthias Klose wrote:
> On 4/2/20 1:30 AM, Andreas Beckmann wrote:
>> On Thu, 26 Mar 2020 21:02:59 +0100 Matthias Klose wrote:
>>> yes, but we cannot rebuild the package, because it build-depends on gnat-8.
>>> Filed a removal bug for gcc-8 instead.
>>
>> An easy fix would probably be to temporarily add a versioned
>> Provides: libgcc-s1 (= 1:${binary:Version})
or rather libgcc1-s1 (= ${gcc:EpochVersion})
>> to libgcc-s1 in src:gcc-10 which should make libgcc-8-dev installable
>> again, s.t. gcc-8 can be rebuilt fixed.
>
> that's a good idea.
I had gcc-10 rebuilding last night with that change (see attached patch)
and just tried it in a pbuilder sid chroot.
* libgcc-8-dev was installable again
* downgrading gcc-10 to the sid version (i.e. switching again to a
version without that provides) worked as well (after removing
libgcc-8-dev first, of course).
Andreas
diff -Nru gcc-10-10-20200324/debian/changelog gcc-10-10-20200324/debian/changelog
--- gcc-10-10-20200324/debian/changelog 2020-03-24 13:38:16.0 +0100
+++ gcc-10-10-20200324/debian/changelog 2020-04-02 01:59:01.0 +0200
@@ -1,3 +1,10 @@
+gcc-10 (10-20200324-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * work around broken gcc-8 dependencies (Closes: #954826)
+
+ -- Andreas Beckmann Thu, 02 Apr 2020 01:59:01 +0200
+
gcc-10 (10-20200324-1) unstable; urgency=medium
* GCC snapshot, taken from the trunk (20200324, 906b3eb9df6).
diff -Nru gcc-10-10-20200324/debian/control gcc-10-10-20200324/debian/control
--- gcc-10-10-20200324/debian/control 2020-03-24 13:19:44.0 +0100
+++ gcc-10-10-20200324/debian/control 2020-04-02 01:59:01.0 +0200
@@ -44,7 +44,7 @@
Section: libs
Priority: optional
Depends: gcc-10-base (= ${gcc:Version}), ${shlibs:Depends}, ${misc:Depends}
-Provides: libgcc1 (= ${gcc:EpochVersion}), libgcc-s1-armel [armel], libgcc-s1-armhf [armhf]
+Provides: libgcc1-s1 (= ${gcc:EpochVersion}), libgcc1 (= ${gcc:EpochVersion}), libgcc-s1-armel [armel], libgcc-s1-armhf [armhf]
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Breaks: ${libgcc:Breaks}
diff -Nru gcc-10-10-20200324/debian/control.m4 gcc-10-10-20200324/debian/control.m4
--- gcc-10-10-20200324/debian/control.m4 2020-03-20 20:41:20.0 +0100
+++ gcc-10-10-20200324/debian/control.m4 2020-04-02 01:59:01.0 +0200
@@ -206,7 +206,7 @@
Section: ifdef(`TARGET',`devel',`libs')
Priority: optional
Depends: BASELDEP, ${shlibs:Depends}, ${misc:Depends}
-Provides: libgcc1`'LS (= ${gcc:EpochVersion}), ifdef(`TARGET',`libgcc-s1-TARGET-dcv1',`libgcc-s1-armel [armel], libgcc-s1-armhf [armhf]')
+Provides: libgcc-s1 (= ${gcc:EpochVersion}), libgcc1`'LS (= ${gcc:EpochVersion}), ifdef(`TARGET',`libgcc-s1-TARGET-dcv1',`libgcc-s1-armel [armel], libgcc-s1-armhf [armhf]')
ifdef(`MULTIARCH', `Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
')`'dnl
Bug#952042: marked as done (ruby-fakeweb: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Thu, 02 Apr 2020 12:20:23 +
with message-id
and subject line Bug#952042: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-2
has caused the Debian Bug report #952042,
regarding ruby-fakeweb: FTBFS: ERROR: Test "ruby2.7" failed.
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.)
--
952042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fakeweb
Version: 1.3.0+git20170806+dfsg1-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7
> │
> └──┘
>
> GEM_PATH=/<>/debian/ruby-fakeweb/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
> ruby2.7 -e gem\ \"fakeweb\"
>
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rb
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=/<>/debian/ruby-fakeweb/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
> ruby2.7 debian/ruby-tests.rb
> Loaded suite debian/ruby-tests
> Started
> .F
> ===
> Failure: test_real_http_request(TestFakeWeb):
> unexpected invocation: #.write_nonblock("GET
> /main/rss/hotnews/hotnews.rss HTTP/1.1\r\nAccept-Encoding:
> gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nAccept: */*\r\nUser-Agent:
> Ruby\r\nHost: images.apple.com\r\n\r\n", {:exception => false})
> unsatisfied expectations:
> - expected at least once, not yet invoked:
> #.read_nonblock(any_parameters)
> - expected exactly once, not yet invoked:
> #.write(all_of(includes("GET /main/rss/hotnews/hotnews.rss
> HTTP/1.1"), includes("Host: images.apple.com")))
> satisfied expectations:
> - allowed any number of times, not yet invoked:
> #.close(any_parameters)
> - allowed any number of times, invoked once:
> #.closed?(any_parameters)
> - allowed any number of times, invoked once:
> #.setsockopt(any_parameters)
> - expected at least once, invoked once: Socket.===(#)
> - expected at least once, invoked once: TCPSocket.open("images.apple.com",
> 80, nil, nil)
> /usr/lib/ruby/2.7.0/net/protocol.rb:277:in `block in write0'
> /usr/lib/ruby/2.7.0/net/protocol.rb:275:in `each'
> /usr/lib/ruby/2.7.0/net/protocol.rb:275:in `each_with_index'
> /usr/lib/ruby/2.7.0/net/protocol.rb:275:in `write0'
> /usr/lib/ruby/2.7.0/net/protocol.rb:248:in `block in write'
> /usr/lib/ruby/2.7.0/net/protocol.rb:265:in `writing'
> /usr/lib/ruby/2.7.0/net/protocol.rb:247:in `write'
> /usr/lib/ruby/2.7.0/net/http/generic_request.rb:335:in `write_header'
> /usr/lib/ruby/2.7.0/net/http/generic_request.rb:129:in `exec'
> /usr/lib/ruby/2.7.0/net/http.rb:1521:in `block in transport_request'
> /usr/lib/ruby/2.7.0/net/http.rb:1519:in `catch'
> /usr/lib/ruby/2.7.0/net/http.rb:1519:in `transport_request'
> /usr/lib/ruby/2.7.0/net/http.rb:1492:in `request'
> /usr/lib/ruby/2.7.0/net/http.rb:1241:in `get'
> /<>/test/test_fake_web.rb:390:in `block in
> test_real_http_request'
> 387:
> 388: resp = nil
> 389: Net::HTTP.start('images.apple.com') do |query|
> => 390: resp = query.get('/main/rss/hotnews/hotnews.rss')
> 391: end
> 392: assert resp.body.include?('Apple')
> 393: assert resp.body.include?('News')
> /usr/lib/ruby/2.7.0/net/http.rb:933:in `start'
> /usr/lib/ruby/2.7.0/net/http.rb:606:in `start'
> /<>/test/test_fake_web.rb:389:in `test_real_http_request'
> ===
> F
> ===
> Failure:
>
Bug#955550: unavailable test dependency libstdc++-riscv32-unknown-elf-newlib-nano
Package: src:binutils-riscv64-unknown-elf Version: 2.32.2019.08+dfsg-1 Severity: serious Tags: sid bullseye unavailable test dependency libstdc++-riscv32-unknown-elf-newlib-nano. tests are always failing.
Bug#895037: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Hi Mike, This (obviously) wasn't done for buster, but it might be time to revisit it for bullseye. On Mon, Oct 22, 2018 at 10:13:32AM +, Mike Gabriel wrote: > > On Fri, Apr 06, 2018 at 01:07:39PM +, Mike Gabriel wrote: > > > Package: src:libappindicator > > > Severity: serious > > > > > > The libappindicator package is currently QA team maintained in Debian and > > > shall be phased out hopfully during the buster release cycle. The > > > alternative (maintained upstream and Debian-downstream) is > > > libayatana-appindicator. > > > > > > There is a lot of porting work to do (little patches are required for each > > > application), to let all AppIndicator aware applications build against the > > > new and supported AppIndicator shared lib fork "libayatana-appindicator". > > > > > > For details, please see [1] > > > > > > For a list of applications that require porting and the porting status, > > > see > > > [2] > > > > What's the status of this? Looking at testing, there are still quite a few > > packages remaining that (build-)depend on libappindicator: > > I wish I could give more time to writing patches against the listed > packages. Possibly, I should do a bug filing round first and then add > patches, when I get to working on individual packages. > > > # Broken Depends: [...] > The above list is irrelevant, what counts are the build-deps. Well, this was the output of dak rm. These dependencies need to be resolved someway before the removal can be done. But I suspect your point is that these will be solved when the build-depends (for the same packages) are solved, so it's better to look at the build-depends. [snip] Note that the list of packages with broken build-depends shown by dak rm isn't much shorter than it was a year ago. > > To help the overview of what's still missing, it might be good to add > > blocking > > bugs for every package to this one. It seems this wasn't done. Please add blocking bugs to this bug, so it's easy to see what's missing. Looking at the list of usertagged bugs you mentioned, it seems most of these bugs are listed as fixed. So the remaining packages either don't have a bug, or the bug wasn't usertagged. If you want to get this done for bullseye, please upgrade these bugs to serious. Autoremovals will take care of some of the packages. The rest will need manual fixes. Cheers, Ivo
Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>
On Mon, Mar 30, 2020 at 07:00:46PM -0400, James McCoy wrote: > On Mon, Mar 30, 2020 at 02:53:40PM -0400, Justin Erenkrantz wrote: > > Here's a tentative patch that causes the test cases to pass with OpenSSL > > 1.1.1e+ for me on Debian Sid. > > > > James, can you please give it a go and confirm that it works for you? > > The package does build and pass tests with the patch. Thanks! > > > Before I commit, we'd also need to gate this based on the new OpenSSL > > constant. We could gate based upon the OpenSSL version number, but I think > > if we can confine to this one area, gating based on ifdef is likely prudent. > > +1 Just as an FYI, the OpenSSL changes have been partially reverted[1] upstream for the 1.1.1f release. The change will be re-introduced in 3.0, so using the ifdef, instead of OpenSSL version, was the prudent choice. [1]: https://github.com/openssl/openssl/pull/11400 Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Processed: bug 954584 is forwarded to https://gitlab.gnome.org/GNOME/gtk/-/issues/2561
Processing commands for cont...@bugs.debian.org: > forwarded 954584 https://gitlab.gnome.org/GNOME/gtk/-/issues/2561 Bug #954584 [src:gtk+3.0] gtk+3.0: FTBFS: testsuite/reftests/flipping-icons.ui: FAIL Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gtk/-/issues/2561'. > thanks Stopping processing here. Please contact me if you need assistance. -- 954584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952041: more information
I can successfully run `rake` inside the source tree, but `debuild` fails. The problem is the created .gemspec file debian/-ruby-hoe/. It's date field seems to respond to spec.date in test_hoe.rb. But this only happens with Ruby 2.7, not with Ruby 2.5. signature.asc Description: This is a digitally signed message part
Bug#931529: Acknowledgement (gnome: Session locking does not possible)
Control: severity -1 important On Wed, Jul 10, 2019 at 09:34:42AM +0200, Charles BLANC ROLIN wrote: > The problem was solved after delete ~/.config/ directory. Downgrading, as there seems to be a workaround. Ivo
Processed: Re: Bug#931529: Acknowledgement (gnome: Session locking does not possible)
Processing control commands: > severity -1 important Bug #931529 [gdm3] gnome: Session locking does not possible Severity set to 'important' from 'grave' -- 931529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954614: marked as done (puppet-beaker: FTBFS: [31mFailure/Error: [0mrequire [31m[1;31m'[0m[31mpry[1;31m'[0m[31m[0m[0m)
Your message dated Thu, 02 Apr 2020 11:19:59 + with message-id and subject line Bug#954614: fixed in puppet-beaker 4.21.0-1 has caused the Debian Bug report #954614, regarding puppet-beaker: FTBFS: [31mFailure/Error: [0mrequire [31m[1;31m'[0m[31mpry[1;31m'[0m[31m[0m[0m 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.) -- 954614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppet-beaker Version: 4.1.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rspec > /usr/lib/ruby/vendor_ruby/pry/cli.rb:4: warning: already initialized constant > Pry::CLI::NoOptionsError > /usr/lib/ruby/vendor_ruby/pry/cli.rb:4: warning: previous definition of > NoOptionsError was here > /usr/lib/ruby/vendor_ruby/pry.rb:11: warning: already initialized constant > Pry::DEFAULT_HOOKS > /usr/lib/ruby/vendor_ruby/pry.rb:11: warning: previous definition of > DEFAULT_HOOKS was here > /usr/lib/ruby/vendor_ruby/pry.rb:18: warning: already initialized constant > Pry::DEFAULT_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:18: warning: previous definition of > DEFAULT_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:27: warning: already initialized constant > Pry::SIMPLE_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:27: warning: previous definition of > SIMPLE_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:36: warning: already initialized constant > Pry::CLIPPED_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:36: warning: previous definition of > CLIPPED_PRINT was here > [] > /usr/lib/ruby/vendor_ruby/pry/cli.rb:4: warning: previous definition of > NoOptionsError was here > /usr/lib/ruby/vendor_ruby/pry.rb:11: warning: already initialized constant > Pry::DEFAULT_HOOKS > /usr/lib/ruby/vendor_ruby/pry.rb:11: warning: previous definition of > DEFAULT_HOOKS was here > /usr/lib/ruby/vendor_ruby/pry.rb:18: warning: already initialized constant > Pry::DEFAULT_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:18: warning: previous definition of > DEFAULT_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:27: warning: already initialized constant > Pry::SIMPLE_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:27: warning: previous definition of > SIMPLE_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:36: warning: already initialized constant > Pry::CLIPPED_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:36: warning: previous definition of > CLIPPED_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:41: warning: already initialized constant > Pry::DEFAULT_EXCEPTION_HANDLER > /usr/lib/ruby/vendor_ruby/pry.rb:41: warning: previous definition of > DEFAULT_EXCEPTION_HANDLER was here > /usr/lib/ruby/vendor_ruby/pry.rb:63: warning: already initialized constant > Pry::DEFAULT_CONTROL_D_HANDLER > /usr/lib/ruby/vendor_ruby/pry.rb:63: warning: previous definition of > DEFAULT_CONTROL_D_HANDLER was here > /usr/lib/ruby/vendor_ruby/pry.rb:78: warning: already initialized constant > Pry::DEFAULT_SYSTEM > /usr/lib/ruby/vendor_ruby/pry.rb:78: warning: previous definition of > DEFAULT_SYSTEM was here > /usr/lib/ruby/vendor_ruby/pry/cli.rb:4: warning: already initialized constant > Pry::CLI::NoOptionsError > /usr/lib/ruby/vendor_ruby/pry/cli.rb:4: warning: previous definition of > NoOptionsError was here > /usr/lib/ruby/vendor_ruby/pry/cli.rb:4: warning: already initialized constant > Pry::CLI::NoOptionsError > /usr/lib/ruby/vendor_ruby/pry/cli.rb:4: warning: previous definition of > NoOptionsError was here > /usr/lib/ruby/vendor_ruby/pry.rb:11: warning: already initialized constant > Pry::DEFAULT_HOOKS > /usr/lib/ruby/vendor_ruby/pry.rb:11: warning: previous definition of > DEFAULT_HOOKS was here > /usr/lib/ruby/vendor_ruby/pry.rb:18: warning: already initialized constant > Pry::DEFAULT_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:18: warning: previous definition of > DEFAULT_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:27: warning: already initialized constant > Pry::SIMPLE_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:27: warning: previous definition of > SIMPLE_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:36: warning: already initialized constant > Pry::CLIPPED_PRINT > /usr/lib/ruby/vendor_ruby/pry.rb:36: warning: previous definition of > CLIPPED_PRINT was here > /usr/lib/ruby/vendor_ruby/pry.rb:41: warning: already initialized constant >
Bug#954572: marked as done (ruby-pry-byebug: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Thu, 02 Apr 2020 11:04:05 + with message-id and subject line Bug#954572: fixed in ruby-pry-byebug 3.9.0-1 has caused the Debian Bug report #954572, regarding ruby-pry-byebug: FTBFS: ERROR: Test "ruby2.7" failed. 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.) -- 954572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-pry-byebug Version: 3.7.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-pry-byebug/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"pry-byebug\" > /usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not find > 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-pry-byebug/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0', > execute `gem env` for more information > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in > activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in > `activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1405:in `block in > activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in > `activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block > in gem' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.2) > byebug (11.1.1) > cgi (default: 0.1.0) > coderay (1.1.2) > columnize (0.9.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0, 1.2.1) > diff-lcs (1.3) > docile (1.1.5) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > io-console (default: 0.5.3) > ipaddr (default: 1.2.2) > irb (default: 1.2.1) > json (2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > method_source (1.0.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.6) > prime (default: 0.1.1) > pry (0.12.2) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rake (13.0.1) > rdoc (default: 6.2.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.2) > rexml (default: 3.2.3) > rspec (3.9.0) > rspec-core (3.9.1) > rspec-expectations (3.9.0) > rspec-mocks (3.9.1) > rspec-support (3.9.2) > rss (default: 0.2.8) > sdbm (default: 1.0.0) > simplecov (0.18.5) > simplecov-html (0.11.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.4) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.0) > xmlrpc (0.3.0) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed. The full build log is available from: http://qa-logs.debian.net/2020/03/21/ruby-pry-byebug_3.7.0-2_unstable.log A list of current
Bug#954174: marked as done (login broken for usernames starting with a number (badname))
Your message dated Thu, 02 Apr 2020 10:19:13 + with message-id and subject line Bug#954174: fixed in systemd 245.4-1 has caused the Debian Bug report #954174, regarding login broken for usernames starting with a number (badname) 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.) -- 954174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 245-2 Severity: serious Forwarded: https://github.com/systemd/systemd/issues/15141 Usernames that contain a number (or digit) as first character are rejected by v245: https://github.com/systemd/systemd/blob/v245/src/basic/user-util.c#L710 This will lead to login failures. By default, adduser will not allow such usernames to be created, but can be forced to do so via --force-badname. While a leading dot is really questionable, the validation should be relaxed for a leading number. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.53-6 ii libapparmor1 2.13.3-7 ii libaudit11:2.8.5-2+b1 ii libblkid12.34-0.1 ii libc62.30-2 ii libcap2 1:2.32-1 ii libcrypt11:4.4.15-1 ii libcryptsetup12 2:2.3.0-1 ii libgcrypt20 1.8.5-5 ii libgnutls30 3.6.12-2 ii libgpg-error01.37-1 ii libidn2-02.3.0-1 ii libip4tc21.8.4-3 ii libkmod2 27-2 ii liblz4-1 1.9.2-2 ii liblzma5 5.2.4-1+b1 ii libmount12.34-0.1 ii libpam0g 1.3.1-5 ii libpcre2-8-0 10.34-7 ii libseccomp2 2.4.3-1 ii libselinux1 3.0-1+b1 ii libsystemd0 245-2 ii mount2.34-0.1 ii util-linux 2.34-0.1 Versions of packages systemd recommends: ii dbus 1.12.16-2 Versions of packages systemd suggests: ii policykit-10.105-26 ii systemd-container 245-2 Versions of packages systemd is related to: ii dracut 048+80-2 pn initramfs-tools ii libnss-systemd 245-2 ii libpam-systemd 245-2 ii udev 245-2 -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 245.4-1 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of systemd, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Apr 2020 11:58:18 +0200 Source: systemd Architecture: source Version: 245.4-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Michael Biebl Closes: 952767 954174 954755 Changes: systemd (245.4-1) unstable; urgency=medium . [ Michael Biebl ] * New upstream version 245.4 - Allow names starting with a digit (Closes: #954174) - Recognize davfs as network file system (Closes: #954755) * Enable systemd-pstore.service by default on new installs and upgrades (Closes: #952767) * Revert "Enable seccomp support on riscv64" This requires further changes to the source code and a newer, not yet officially released, libseccomp. Since this complicates backports revert this change for the time being. . [ Dan Streetman ] * d/t/logind: use grep -s when checking /sys/power/state. Some kernels in Ubuntu (e.g. linux-kvm) do not enable CONFIG_PM, which results in stderr output when the logind test tries to grep the power state file, causing the test to fail. The test already handles skipping the test if suspend isn't supported, so just use -s to
Processed: Re: Bug#947827: Missing symbols in -lblas ?
Processing control commands: > severity -1 serious Bug #947827 [libatlas3-base] Missing symbols in -lblas ? Severity set to 'serious' from 'normal' -- 947827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Affected versions
Processing commands for cont...@bugs.debian.org: > found 944177 8.0.19+dfsg-1 Bug #944177 [mysql-workbench] mysql-workbench: non-standard gcc/g++ used for build (gcc-8) Marked as found in versions mysql-workbench/8.0.19+dfsg-1. > found 944181 0.35+git20181129+dfsg-4 Bug #944181 [ghdl] ghdl: non-standard gcc/g++ used for build (gcc-8) Marked as found in versions ghdl/0.35+git20181129+dfsg-4. > found 944169 1.4.0-97-g75b3e59+dfsg-3 Bug #944169 [open-ath9k-htc-firmware] open-ath9k-htc-firmware: non-standard gcc/g++ used for build (gcc-8) There is no source info for the package 'open-ath9k-htc-firmware' at version '1.4.0-97-g75b3e59+dfsg-3' with architecture '' Unable to make a source version for version '1.4.0-97-g75b3e59+dfsg-3' Marked as found in versions 1.4.0-97-g75b3e59+dfsg-3. > stop Stopping processing here. Please contact me if you need assistance. -- 944169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944169 944177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944177 944181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955544: capnproto: FTBFS on s390x
Package: capnproto
Version: 0.7.0-5
Severity: serious
Tags: patch upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
capnproto 0.7.0-5 failed to build in Ubuntu Focal on s390x:
https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1870055
In an upstream issue:
https://github.com/capnproto/capnproto/issues/962
They pointed at a fix:
https://github.com/capnproto/capnproto/pull/761
The attached patch is that fix.
-- System Information:
Debian Release: bullseye/sid
APT prefers focal-security
APT policy: (500, 'focal-security'), (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-21-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.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 capnproto depends on:
ii libc6 2.31-0ubuntu6
pn libcapnp-0.7.0
ii libgcc-s1 10-20200324-1ubuntu1
ii libstdc++6 10-20200324-1ubuntu1
capnproto recommends no packages.
capnproto suggests no packages.
commit ce4dd5a1031ee741c676daaea89ae3d1b19f2bb2
Author: David Renshaw
Date: Fri Nov 16 21:23:58 2018 -0500
initialize anonymous enums in isPlausiblyText() and isPlausiblyJson()
diff --git a/src/capnp/compiler/capnp.c++ b/c++/src/capnp/compiler/capnp.c++
index e39db556..8e8c459b 100644
--- a/src/capnp/compiler/capnp.c++
+++ b/src/capnp/compiler/capnp.c++
@@ -1377,7 +1377,7 @@ private:
}
Plausibility isPlausiblyText(kj::ArrayPtr prefix) {
-enum { PREAMBLE, COMMENT, BODY } state;
+enum { PREAMBLE, COMMENT, BODY } state = PREAMBLE;
for (char c: prefix.asChars()) {
switch (state) {
@@ -1427,7 +1427,7 @@ private:
}
Plausibility isPlausiblyJson(kj::ArrayPtr prefix) {
-enum { PREAMBLE, COMMENT, BODY } state;
+enum { PREAMBLE, COMMENT, BODY } state = PREAMBLE;
for (char c: prefix.asChars()) {
switch (state) {
Bug#954724: marked as done (ruby-guard: FTBFS: ERROR: Test "ruby2.7" failed. Could not find 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] (Gem::MissingSpecVersionError))
Your message dated Thu, 02 Apr 2020 09:50:47 + with message-id and subject line Bug#954724: fixed in ruby-guard 2.16.2-1 has caused the Debian Bug report #954724, regarding ruby-guard: FTBFS: ERROR: Test "ruby2.7" failed. Could not find 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] (Gem::MissingSpecVersionError) 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.) -- 954724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-guard Version: 2.16.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-guard/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"guard\" > /usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not find > 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-guard/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0', > execute `gem env` for more information > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in > activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in > `activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1405:in `block in > activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in > `activate_dependencies' > from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block > in gem' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.2) > cgi (default: 0.1.0) > coderay (1.1.2) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0, 1.2.1) > diff-lcs (1.3) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > ffi (1.12.2) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > formatador (0.2.5) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > io-console (default: 0.5.3) > ipaddr (default: 1.2.2) > irb (default: 1.2.1) > json (default: 2.3.0) > listen (3.1.5) > logger (default: 1.4.2) > lumberjack (1.0.13) > matrix (default: 0.2.0) > method_source (1.0.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > nenv (0.3.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > notiffany (0.1.3) > observer (default: 0.1.0) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.6) > prime (default: 0.1.1) > pry (0.12.2) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rake (13.0.1) > rb-inotify (0.9.10) > rdoc (default: 6.2.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.2) > rexml (default: 3.2.3) > rspec (3.9.0) > rspec-core (3.9.1) > rspec-expectations (3.9.0) > rspec-mocks (3.9.1) > rspec-support (3.9.2) > rss (default: 0.2.8) > sdbm (default: 1.0.0) > shellany (0.0.1) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.4) > thor (0.19.4) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.0) > xmlrpc (0.3.0) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test
Processed: retitle 955541 to Login fails for a user name with non-ascii characters ...
Processing commands for cont...@bugs.debian.org: > retitle 955541 Login fails for a user name with non-ascii characters Bug #955541 [systemd] Login fails for a user name with non-ascii characters, forwarded -1 https://github.com/systemd/systemd/issues/15090 Changed Bug title to 'Login fails for a user name with non-ascii characters' from 'Login fails for a user name with non-ascii characters, forwarded -1 https://github.com/systemd/systemd/issues/15090'. > forwarded 955541 https://github.com/systemd/systemd/issues/15090 Bug #955541 [systemd] Login fails for a user name with non-ascii characters Changed Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/15090' from 'https://github.com/systemd/systemd/issues/15141'. > thanks Stopping processing here. Please contact me if you need assistance. -- 955541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955539: libreoffice: Incomplete upgrade due to libreoffice-math conflict
severity 955539 serious found 955539 1:6.4.2~rc1-1 close 955539 1:6.4.2-3 thanks On Thu, Apr 02, 2020 at 11:04:43AM +0200, Josep Lladonosa i Capell wrote: > Source: libreoffice > Version: partial upgrade to 6.4.2-2~bpo10+1 version due to libreoffice-math > 6.3.2-1~bpo10+1 conflict No, Version: is parsed. It is not a free-form text. It gets parsed to the version graph you see iin the upper right corner... And in this case, also note https://backports.debian.org/Instructions/ --- Report Bugs Please report bugs that you found in the packages to the backports mailing list and NOT to the Debian BTS! --- Although in this case the bug is not backports-specific and already fixed, so it doesn't really matter much... > Conflict was caused by libreoffice-math 6.4.2-2~bpo10+1 that was trying to get > installed with the same existing package 1:6.3.2-1~bpo10+1x. [...] > S'està preparant per a desempaquetar …/libreoffice- > math_1%3a6.4.2-2~bpo10+1_amd64.deb… > S'està desempaquetant libreoffice-math (1:6.4.2-2~bpo10+1) sobre > (1:6.3.2-1~bpo10+1)… > dpkg: s'ha produït un error en processar l'arxiu > /var/cache/apt/archives/libreoffice-math_1%3a6.4.2-2~bpo10+1_amd64.deb > (--unpack): > s'està intentant sobreescriure > «/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml», > que també està en el paquet libreoffice-common 1:6.3.2-1~bpo10+1 > dpkg-deb: s'ha produït un error: el subprocés «enganxa» ha estat finalitzat > pel > senyal (La canonada s’ha trencat) > Restoring backup of /usr/share/doc/libreoffice-math ... > S'han trobat errors en processar: > /var/cache/apt/archives/libreoffice-math_1%3a6.4.2-2~bpo10+1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > ++ Yeah, known bug. Already fixed in 6.4.2-3 which I cannot backport yet due to it not being in testing yet. libreoffice (1:6.4.2-3) unstable; urgency=medium [...] - libreoffice-math: Add Breaks/Replaces libreoffice-common (<< 1:6.4.2~rc1~) [...] -- Rene Engelhard Sat, 28 Mar 2020 06:53:24 +0100 Regards, Rene
Processed: closing 955539
Processing commands for cont...@bugs.debian.org:
> close 955539 1:6.4.3~rc1-3
Bug #955539 {Done: Rene Engelhard } [libreoffice-math]
libreoffice: Incomplete upgrade due to libreoffice-math conflict
Marked as fixed in versions libreoffice/1:6.4.3~rc1-3.
Bug #955539 {Done: Rene Engelhard } [libreoffice-math]
libreoffice: Incomplete upgrade due to libreoffice-math conflict
Bug 955539 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
955539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
