Bug#945473: marked as done (fix installation of extensions with Python 3.8)
Your message dated Thu, 28 Nov 2019 07:19:08 + with message-id and subject line Bug#945473: fixed in libtorrent-rasterbar 1.1.13-1.1 has caused the Debian Bug report #945473, regarding fix installation of extensions with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libtorrent-rasterbar Version: 1.1.13-1 Severity: serious Tags: sid bullseye ftbfs patch User: debian-pyt...@lists.debian.org Usertags: python3.8 fix installation of extensions with Python 3.8. proposed patch at https://patches.ubuntu.com/libt/libtorrent-rasterbar/libtorrent-rasterbar_1.1.13-1ubuntu1.patch --- End Message --- --- Begin Message --- Source: libtorrent-rasterbar Source-Version: 1.1.13-1.1 We believe that the bug you reported is fixed in the latest version of libtorrent-rasterbar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated libtorrent-rasterbar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Nov 2019 17:42:44 +0100 Source: libtorrent-rasterbar Architecture: source Version: 1.1.13-1.1 Distribution: unstable Urgency: medium Maintainer: Cristian Greco Changed-By: Matthias Klose Closes: 936927 945473 Changes: libtorrent-rasterbar (1.1.13-1.1) unstable; urgency=medium . * Non-maintainer upload. * Stop building the Python2 packages. Closes: #936927. * Fix installation of the python3.8 extension. Closes: #945473. Checksums-Sha1: 7f2b91df9a02e5ec06afcf718f33e0af908d4937 2618 libtorrent-rasterbar_1.1.13-1.1.dsc 4aa1d6741266b41beb3c9886df0eb812e5dc9c0e 16556 libtorrent-rasterbar_1.1.13-1.1.debian.tar.xz 95443bbe600c6157c447aa6c02c8a33fa07df280 8395 libtorrent-rasterbar_1.1.13-1.1_source.buildinfo Checksums-Sha256: a8b8cb88d5e1c417166e4c696e2d696476e35069a1bc7c4a3980558889d02722 2618 libtorrent-rasterbar_1.1.13-1.1.dsc 13c3fb2ccf9cb043092b485707b31b87c1dfbf3177d2eb47379dab8d504ebae1 16556 libtorrent-rasterbar_1.1.13-1.1.debian.tar.xz 5f02e4bb44ceb85d370337f81184ada10ad223dc5c6991e5c8460dd702d5ea7d 8395 libtorrent-rasterbar_1.1.13-1.1_source.buildinfo Files: d55a6fb548326655be505ef4e77ecf76 2618 libs optional libtorrent-rasterbar_1.1.13-1.1.dsc 125e2b9f69f36469817110dc4a6a8fac 16556 libs optional libtorrent-rasterbar_1.1.13-1.1.debian.tar.xz 86ee55c893d9be4aac0fcc7eb238c40c 8395 libs optional libtorrent-rasterbar_1.1.13-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl3czCIQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9THTD/4w2+y9vChhkC53gtTiYiO56/NnosTQ3Wso ndHBt+F1lpqtdrrAruw9HGdGmfe2xM7GjfqLl+tyZTuVRO8Rxres+dHlhFX4rJIP 9cljOzHBd3qomGKXdlArI0X7ADkY80wBLwIqTrvB45TbkGo+zjZY5fQ+4n3QAIXc OppapI10lfaxsMpxX35BN3xbEwDTV+bPDpBWxUCU/Z6PV5Ittdhf8Rp5r5iU2Y6L wH4yg6q/biyQLELogIjbnaSr3BsnRTKiigsWBZKbTl2SyGLoXfb+egIKUaUlYAkm 9MmKxAfU6CQloxtaFgpCXl27gvuiHppFrDIGtCFpCTkD46eU/ocO2fYgk6kSde4X Ze3gaOuvKi0Ip1/VlGQ2iViIQTlmEDwFPX6Ioa+9T9mIf5hPWjI5qPB1INnlbhFJ E8TUC7NVlAIzQ0Ai2HOV7jC/WwnCZwX4O0Czp/d6taMQWFkw/HSn9YgWsKwoApe8 ECPWT9wguibmAVwvxQ0BW0iBCJ/9iHdAYkC+CrLl9Hry3TpfQBaYCIQjSOYnfasE QeMlA81h22/9kzZuYk1ae/lPb3Z7k0psV3PAZshcmvgkTiHmCfRQ9vqnbyKxJ7l1 C62seqTS1bbZotPQwBwIcsWArICgvAbTAlx/bnWWBO+ZN+uYCrxUXpNB5ElhbBfJ OtFFzMqZ0Q== =TtqI -END PGP SIGNATURE End Message ---
Bug#936222: marked as done (bluewho: Python2 removal in sid/bullseye)
Your message dated Thu, 28 Nov 2019 06:40:21 + with message-id and subject line Bug#945617: Removed package(s) from unstable has caused the Debian Bug report #936222, regarding bluewho: 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.) -- 936222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bluewho Version: 0.1-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:bluewho 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.1-2+rm Dear submitter, as the package bluewho 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/945617 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#885257: marked as done (agtl: Depends on unmaintained pygtk)
Your message dated Thu, 28 Nov 2019 06:39:59 + with message-id and subject line Bug#945615: Removed package(s) from unstable has caused the Debian Bug report #885257, regarding agtl: 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.) -- 885257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: agtl Version: 0.8.0.3-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. 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: 0.8.0.3-1.1+rm Dear submitter, as the package agtl 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/945615 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#885270: marked as done (d-rats: Depends on unmaintained pygtk)
Your message dated Thu, 28 Nov 2019 06:39:34 + with message-id and subject line Bug#945573: Removed package(s) from unstable has caused the Debian Bug report #885270, regarding d-rats: 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.) -- 885270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: d-rats Version: 0.3.3-4 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. 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: 0.3.3-4+rm Dear submitter, as the package d-rats 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/945573 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#936442: marked as done (d-rats: Python2 removal in sid/bullseye)
Your message dated Thu, 28 Nov 2019 06:39:34 + with message-id and subject line Bug#945573: Removed package(s) from unstable has caused the Debian Bug report #936442, regarding d-rats: 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.) -- 936442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:d-rats Version: 0.3.3-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:d-rats 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.3-4+rm Dear submitter, as the package d-rats 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/945573 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#934858: marked as done (Please port viewvc to Python 3 or get it removed from Sid/Bullseye)
Your message dated Thu, 28 Nov 2019 06:38:34 + with message-id and subject line Bug#935691: Removed package(s) from unstable has caused the Debian Bug report #934858, regarding Please port viewvc to Python 3 or get it removed from 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.) -- 934858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: viewvc Version: 1.1.26 Severity: serious Hi, Viewvc seems to be Python 2 only, and having a quick look, it needs a lot of work to make it work under Python 3. Since we want to get Python 2 removed from Bullseye, you have no choice but to either port it to Python3, convince upstream to do so, or drop the package from Bullseye (and continue to maintain it for the next 5 years in Buster). Your thoughts? Cheers, Thomas Goirand (zigo) --- End Message --- --- Begin Message --- Version: 1.1.26-1+rm Dear submitter, as the package viewvc 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/935691 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#885254: marked as done (bluewho: Depends on deprecated pygtk)
Your message dated Thu, 28 Nov 2019 06:40:21 + with message-id and subject line Bug#945617: Removed package(s) from unstable has caused the Debian Bug report #885254, regarding bluewho: Depends on deprecated 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.) -- 885254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bluewho Version: 0.1-2 Severity: serious Tags: sid buster User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk 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. 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: 0.1-2+rm Dear submitter, as the package bluewho 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/945617 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#936111: marked as done (agtl: Python2 removal in sid/bullseye)
Your message dated Thu, 28 Nov 2019 06:39:59 + with message-id and subject line Bug#945615: Removed package(s) from unstable has caused the Debian Bug report #936111, regarding agtl: 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.) -- 936111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:agtl Version: 0.8.0.3-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:agtl 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.8.0.3-1.1+rm Dear submitter, as the package agtl 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/945615 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#931695: libgit-raw-perl: FTBFS with libgit2 0.28
tags 931695 +patch thanks Some poking around revealed that upstream fixed this by removing the last (NULL) parameter from the call. This was done in a commit titled "minor fixes". https://github.com/jacquesg/p5-Git-Raw/commit/30f7a4491ab453d28ae1fa1b393fcd023f6c344d . There was also another apparently unrelated change in the commit, which did not seem relavent to the version in Debian. I did a test build with this change in a raspbian bullseye-staging chroot. A couple of tests failed, but that could have just been my build environment, I decided this was good enough to disable the testsuite and upload to raspbian. While working on this I ran into an issue with the clean target not cleaning up properly, so I fixed that too. A debdiff should appear soon at https://debdiffs.raspbian.org/main/libg/libgit-raw-perl No intent to NMU in debian.
Processed: re: libgit-raw-perl: FTBFS with libgit2 0.28
Processing commands for cont...@bugs.debian.org: > tags 931695 +patch Bug #931695 [src:libgit-raw-perl] libgit-raw-perl: FTBFS with libgit2 0.28 Bug #944912 [src:libgit-raw-perl] libgit-raw-perl: FTBFS with libgit2 0.28 Added tag(s) patch. Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 931695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931695 944912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945751: openafs-modules-dkms: openafs-dkms kernel module does not build for kernel 5.3.0-2-amd64
Package: openafs-modules-dkms Version: 1.8.4~pre1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The openafs-dkms kernel module fails to build on kernel 5.3.0-2 on buster. In file included from /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/rx_kmutex.c:24: /var/lib/dkms/openafs/1.8.4pre1/build/src/afs/LINUX/osi_compat.h: In function ‘afs_linux_search_keyring’: /var/lib/dkms/openafs/1.8.4pre1/build/src/afs/LINUX/osi_compat.h:225:12: error: too few arguments to function ‘keyring_search’ 225 | key_ref = keyring_search( |^~ In file included from /usr/src/linux- headers-5.3.0-2-common/include/linux/cred.h:13, from /usr/src/linux- headers-5.3.0-2-common/include/linux/seq_file.h:12, from /usr/src/linux- headers-5.3.0-2-common/include/linux/seq_file_net.h:5, from /usr/src/linux- headers-5.3.0-2-common/include/net/net_namespace.h:177, from /usr/src/linux- headers-5.3.0-2-common/include/linux/netdevice.h:38, from /usr/src/linux- headers-5.3.0-2-common/include/net/inet_sock.h:19, from /usr/src/linux- headers-5.3.0-2-common/include/linux/udp.h:16, from /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/./netinet/udp.h:1, from /var/lib/dkms/openafs/1.8.4pre1/build/src/rx/rx_kcommon.h:110, from /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/rx_kmutex.c:20: /usr/src/linux-headers-5.3.0-2-common/include/linux/key.h:387:18: note: declared here 387 | extern key_ref_t keyring_search(key_ref_t keyring, | ^~ make[5]: *** [/usr/src/linux-headers-5.3.0-2-common/scripts/Makefile.build:286: /var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP/rx_kmutex.o] Fehler 1 make[4]: *** [/usr/src/linux-headers-5.3.0-2-common/Makefile:1639: _module_/var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP] Fehler 2 make[3]: *** [/usr/src/linux-headers-5.3.0-2-common/Makefile:179: sub-make] Fehler 2 make[3]: Verzeichnis „/usr/src/linux-headers-5.3.0-2-amd64“ wird verlassen FAILURE: make exit code 2 make[2]: *** [Makefile.afs:280: openafs.ko] Fehler 1 make[2]: Verzeichnis „/var/lib/dkms/openafs/1.8.4pre1/build/src/libafs/MODLOAD-5.3.0-2-amd64-SP“ wird verlassen make[1]: *** [Makefile:187: linux_compdirs] Fehler 2 make[1]: Verzeichnis „/var/lib/dkms/openafs/1.8.4pre1/build/src/libafs“ wird verlassen make: *** [Makefile:15: all] Fehler 2 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_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 openafs-modules-dkms depends on: ii dkms 2.8.1-3 ii libc6-dev 2.29-3 ii perl 5.30.0-9 Versions of packages openafs-modules-dkms recommends: ii openafs-client 1.8.4~pre1-1 openafs-modules-dkms suggests no packages. -- no debconf information
Bug#944648: sagemath FTBFS on i386
All three failures give the error message
OverflowError: Python int too large to convert to C long
from
File "sage/rings/polynomial/polynomial_integer_dense_flint.pyx", line 284, in
sage.rings.polynomial.polynomial_integer_dense_flint.Polynomial_integer_dense_flint.__init__
(build/cythonized/sage/rings/polynomial/polynomial_integer_dense_flint.cpp:6548)
fmpz_poly_set_coeff_si(self.__poly, i, a)
Help on finding a fix would be appreciated.
On line 282 of that file (assuming the version at
https://github.com/sagemath/sage/blob/master/src/sage/rings/polynomial/polynomial_integer_dense_flint.pyx
is the same as the one in the Debian package).
"if type(a) is int:"
If that conditional is true then the code takes a fast path, which assumes that the value
of "a" fits in a C long.
In python 2 "int" was a type limited to the size of a c long, so the check was
appropriate. However in python 3 "int" is an arbitrary precision type, so we need to
check if it will fit in the range of a C long.
There are several other conditionals on types being "int" in the file that presumably
need fixing in the same way. I also spotted a "isinstance(x0, long):" which i'm pretty
sure will fail in python 3 as there is no type long in python 3.
I have attached a completely untested patch.
Description: fix python integer type checks in polynomial_integer_dense_flint.pyx
python 3 changes the standard integer types, in python2 a python "int" was
equivilent to a C "long" and a python "long" was an arbitary precision type.
In python 3 a python "int" is now an arbitary precision type and a python
"long" does not exist any more.
This patch adds additional checks that a python int will fit in the range of
a C long before passing it to routines that require it to fit in one. It also
locally defines long=int on python 3 so that isinstance(x0,long) will correctly
test for an arbitary precision python integer.
Author: Peter Michael Green
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update: 2019-11-28
--- sagemath-8.9.orig/sage/src/sage/rings/polynomial/polynomial_integer_dense_flint.pyx
+++ sagemath-8.9/sage/src/sage/rings/polynomial/polynomial_integer_dense_flint.pyx
@@ -36,12 +36,21 @@ from __future__ import absolute_import,
from cysignals.memory cimport sig_free
from cysignals.signals cimport sig_on, sig_off
+from libc.limits cimport LONG_MIN
+from libc.limits cimport LONG_MAX
+
include "sage/libs/ntl/decl.pxi"
from cpython.int cimport PyInt_AS_LONG
from sage.libs.gmp.mpz cimport *
from sage.arith.long cimport pyobject_to_long
+import sys
+#we use this later in an isinstance test to detect a python arbitary precision
+#integer
+if sys.version_info.major > 3:
+long = int
+
from sage.rings.polynomial.polynomial_element cimport Polynomial
from sage.structure.element cimport ModuleElement, Element
from sage.structure.element import coerce_binop
@@ -241,7 +250,7 @@ cdef class Polynomial_integer_dense_flin
# now fill them in
for ii, a in x:
i = ii[0] if type(ii) is tuple else ii
-if type(a) is int:
+if (type(a) is int) and (LONG_MIN <= a <= LONG_MAX):
sig_on()
fmpz_poly_set_coeff_si(self.__poly, i, a)
sig_off()
@@ -279,7 +288,7 @@ cdef class Polynomial_integer_dense_flin
sig_off()
for i from 0 <= i < len(x):
a = x[i]
-if type(a) is int:
+if (type(a) is int) && (LONG_MIN <= a <= LONG_MAX):
sig_on()
fmpz_poly_set_coeff_si(self.__poly, i, a)
sig_off()
@@ -398,7 +407,7 @@ cdef class Polynomial_integer_dense_flin
( x0).__poly)
sig_off()
return f
-if isinstance(x0, int):
+if isinstance(x0, int) and (LONG_MIN <= x0 <= LONG_MAX):
z = Integer.__new__(Integer)
sig_on()
fmpz_init(a_fmpz)
@@ -1287,7 +1296,7 @@ cdef class Polynomial_integer_dense_flin
"""
if n < 0:
raise IndexError("n must be >= 0")
-if isinstance(value, int):
+if isinstance(value, int) and (LONG_MIN <= value <= LONG_MAX):
sig_on()
fmpz_poly_set_coeff_si(self.__poly, n, value)
sig_off()
Processed: Re: Bioperl 1.7.4 should not migrate to Buster
Processing control commands:
> found -1 1.7.6-1
Bug #921495 {Done: michael.cru...@gmail.com (Michael R. Crusoe)}
[libbio-perl-perl] Bioperl 1.7.4 should not migrate to Buster
Marked as found in versions bioperl/1.7.6-1; no longer marked as fixed in
versions bioperl/1.7.6-1 and reopened.
--
921495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921495: Bioperl 1.7.4 should not migrate to Buster
Followup-For: Bug #921495 Control: found -1 1.7.6-1 libbio-perl-perl is missing proper Breaks+Replaces: libbio-perl-run-perl (<< 1.7.3) There is a typoed (lib?io-perl-run-perl) and wrongly versioned Breaks: libio-perl-run-perl (<= 1.7.3-1), roary (<= 3.12.0+dfsg-2) without corresponding Replaces. (Without the typo it would break the 'fixed' version in sid, too.) And (<< 1.7.3-1) would be wrong, too, since it hits a potential 1.7.3-1~bpo10+1 Also the broken version of roary is likely wrong: you most likely want roary (<< 3.13) (just think of a buster-pu upload of roary 3.12.0+dfsg-2+deb10u1). Andreas
Bug#885254: bluewho: Depends on deprecated pygtk
On Fri, Dec 29, 2017 at 10:48:57AM +0200, Juhani Numminen wrote: > Control: tags -1 fixed-upstream > > On Mon, 25 Dec 2017 23:39:04 -0500 Jeremy Bicha wrote: > > > 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. > > > > 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. > > The latest upstream version bluewho 0.2.2 (from 2014) uses GObject > Introspection and GTK+ 3 already. There wasn't any reaction in two years, so I've filed a removal bug now. Cheers, Moritz
Bug#885270: bumping severity of pygtk bugs
On Tue, Nov 26, 2019 at 05:27:08PM -0600, Steve Conklin wrote: > I have no intention to port it. Filing a removal bug sounds appropriate. > > Thanks, > > Steve Conklin Ack, I've just filed an RM bug. Cheers, Moritz
Bug#945610: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/launchpadlib/version.txt'
Package: python3-launchpadlib Version: 1.10.8-1 Severity: grave After upgrade, my scripts that use launchpadlib now fail at import (see below). AFAIK, this makes this version unusable by most or all users, but obviously feel free to lower the severity if that is incorrect. dannf@xps13:~$ python3 \Python 3.7.5 (default, Oct 27 2019, 15:43:29) [GCC 9.2.1 20191022] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from launchpadlib.launchpad import Launchpad Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/launchpadlib/__init__.py", line 19, in "launchpadlib", "version.txt").strip() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1157, in resource_string self, resource_name File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1401, in get_resource_string return self._get(self._fn(self.module_path, resource_name)) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1616, in _get with open(path, 'rb') as stream: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/launchpadlib/version.txt' >>> -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-launchpadlib depends on: ii python3 3.7.5-3 ii python3-httplib20.11.3-2 ii python3-keyring 18.0.1-1 ii python3-lazr.restfulclient 0.14.2-2 ii python3-lazr.uri1.0.3-4 ii python3-simplejson 3.16.0-2+b1 ii python3-wadllib 1.3.3-3 python3-launchpadlib recommends no packages. Versions of packages python3-launchpadlib suggests: ii python3-pkg-resources 41.4.0-1 pn python3-testresources -- no debconf information
Bug#945420: marked as done (symbols file needs adjustments for mipsel and sparc64)
Your message dated Wed, 27 Nov 2019 21:20:30 + with message-id and subject line Bug#945420: fixed in libkolabxml 1.1.6-6 has caused the Debian Bug report #945420, regarding symbols file needs adjustments for mipsel and sparc64 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.) -- 945420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libkolabxml Version: 1.1.6-5 Severity: serious Tags: sid bullseye ftbfs The symbols file needs adjustments for mipsel and sparc64, or else the package will stay in unstable. --- End Message --- --- Begin Message --- Source: libkolabxml Source-Version: 1.1.6-6 We believe that the bug you reported is fixed in the latest version of libkolabxml, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Knauß (supplier of updated libkolabxml 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, 27 Nov 2019 21:56:30 +0100 Source: libkolabxml Architecture: source Version: 1.1.6-6 Distribution: unstable Urgency: medium Maintainer: Debian Kolab Maintainers Changed-By: Sandro Knauß Closes: 945420 Changes: libkolabxml (1.1.6-6) unstable; urgency=medium . * Update symbols from buildds for 1.1.6 (Closes: #945420) Checksums-Sha1: 2be689539da422d1ce2a494a94d04c5fc1509801 2388 libkolabxml_1.1.6-6.dsc 3e3d995a13eed27c28810103ad24681e1ec88262 61240 libkolabxml_1.1.6-6.debian.tar.xz 4c98c21b93b588e7ae48a0d8820871a0c828b493 12900 libkolabxml_1.1.6-6_source.buildinfo Checksums-Sha256: 5de83ace57529006e14d4415ec0f0d95300afa917a89c66d7817fa0c7fe3dbf2 2388 libkolabxml_1.1.6-6.dsc 1c4cc58c82644017b8b64e14b2dd6d7ee6e392debcddf9831fd262370347cabf 61240 libkolabxml_1.1.6-6.debian.tar.xz 9635e7048d83ed2a3d850c73c373371cb532bf9a9d15d8c1734c84e94d7e427f 12900 libkolabxml_1.1.6-6_source.buildinfo Files: 8133d84e879136589b1b8064bd3de9ea 2388 libs optional libkolabxml_1.1.6-6.dsc bc40af30ce9e83dbb3ab753a5a7d4b8d 61240 libs optional libkolabxml_1.1.6-6.debian.tar.xz c6b77950b41be94b112c2cb0d417af8f 12900 libs optional libkolabxml_1.1.6-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAl3e4yYRHGhlZmVlQGRl Ymlhbi5vcmcACgkQ462wCFBgVjb59w/+JI59BqUNIgCgGcGd7qVl9FzeCVkQf9mZ 6x6sDdTzWWvlOrsgtUUoODa6jWFU6Nc8QTqTO54cpe8Q3dBCPK7c7FGHece6qWIO aW3KiyB4Nf4ztyzSWLF1EpLqgsw59lLI2CoFcFkhpMit/2JuHjGgkcHunVK3FwvQ N6SMrqDpZrcbTaBOApsE79WHX2NjEnCyvQ7pLw341hPEgdTjbYzMJB+ElYpFrlzL UBkf0LIUR8NYZDHCDSGYdk7ZTJPENmWvmvRLQ5tCuzdIOl8IwcUz1pHlLF048w+e Dp8K2dJZWYqgYqQ+Cy8dknZN8ny7FZ60KDfIcECRRA/j2zOA43lPheZRtfe2QUyd 023MgmEWHS1aQwMH5JFGfX8pzvL+964Iq4JMVDNlMSIf3ZK0zC2+jdhcWSzJQWN/ sNCoa2RglG4HAzwFeWlwbIpAfYr/9Zk4+xeTQSp4y1RwRGalnie8+snOucrqiccD qPxF13pCT2RwFd5QpCZ+KRf2EB3xyI+zOvztBqARQF0HwfEy3x+CNiltBOOVKjNU 5rn/BKfin0rCEvuFvkehOdToBNqBzscHOsiTew3AsKMujHqC9G1gcTcgAVWIf/uB YDlBBuxabs41MpQxhYLWSDamYg0HfTim6ia9gl2uSiWqARwzaJ0FnT2fdoUtZ6Pc ZWUYmW4qvWk= =JHcJ -END PGP SIGNATURE End Message ---
Bug#945605: python-neovim: autopkgtest needs update for new version of neovim: Invalid option name: 'listchars'
Source: python-neovim
Version: 0.3.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, neo...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:neovim
Dear maintainers,
With a recent upload of neovim the autopkgtest of python-neovim fails in
testing when that autopkgtest is run with the binary packages of neovim
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
neovim from testing0.4.3-2
python-neovim from testing0.3.0-1
versioned deps [0] from testingfrom unstable
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 neovim to testing
[1]. Of course, neovim shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in neovim 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 neovim 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
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
neovim/0.4.3-2. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=neovim
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-neovim/3517661/log.gz
=== FAILURES
===
_ test_options
_
vim =
def test_options(vim):
> assert vim.options['listchars'] == 'tab:> ,trail:-,nbsp:+'
test/test_vim.py:84:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/neovim/api/common.py:88: in __getitem__
return self._get(key)
/usr/lib/python3/dist-packages/neovim/api/nvim.py:180: in request
res = self._session.request(name, *args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self =
method = 'nvim_get_option', args = ('listchars',), kwargs = {}, async_ =
False
v = [[1, b"Invalid option name: 'listchars'"], None]
err = [1, b"Invalid option name: 'listchars'"], rv = None
def request(self, method, *args, **kwargs):
"""Send a msgpack-rpc request and block until as response is
received.
If the event loop is running, this method must have been called by a
request or notification handler running on a greenlet. In that case,
send the quest and yield to the parent greenlet until a response is
available.
When the event loop is not running, it will perform a blocking
request
like this:
- Send the request
- Run the loop until the response is available
- Put requests/notifications received while waiting into a queue
If the `async_` flag is present and True, a asynchronous
notification
is sent instead. This will never block, and the return value or
error
is ignored.
"""
async_ = check_async(kwargs.pop('async_', None), kwargs, False)
if async_:
self._async_session.notify(method, args)
return
if kwargs:
raise ValueError("request got unsupported keyword
argument(s): {}"
.format(', '.join(kwargs.keys(
if self._is_running:
v = self._yielding_request(method, args)
else:
v = self._blocking_request(method, args)
if not v:
# EOF
raise IOError('EOF')
err, rv = v
if err:
info("'Received error: %s", err)
> raise self.error_wrapper(err)
E neovim.api.nvim.NvimError: b"Invalid option name: 'listchars'"
signature.asc
Description: OpenPGP digital signature
Processed: python-neovim: autopkgtest needs update for new version of neovim: Invalid option name: 'listchars'
Processing control commands: > affects -1 src:neovim Bug #945605 [src:python-neovim] python-neovim: autopkgtest needs update for new version of neovim: Invalid option name: 'listchars' Added indication that 945605 affects src:neovim -- 945605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945602: wrong path for constants.xml/presets.xml prevent the program from starting
Package: qwinff Version: 0.2.1-1 Severity: grave Steps to reproduce the problem: - run qwinff from the desktop launcher of from a terminal emulator What happens: - An error dialog is shown with the message "Cannot load /home/user/constants.xml. The program will exit now." - In addition, when qwinff is launched from a terminal, there is the error "Failed to read file: "/home/user/constants.xml" - Clicking the "Ok" button closes the error message, but the program is in fact still running (appears in ps aux output/task managers). When run from a terminal it does not give back STDIN unless I stop/kill/Ctrl+C it Workaround: - a quick search reveals a file /usr/share/qwinff/constants.xml. Copying this file to /home/user/constants.xml makes the error message disappear. A second message is shown about missing presets.xml, the same workaround can be applied (it's also in /usr/share/qwinff/) Suggested fix: I don't know. The makefile (https://github.com/qwinff/qwinff/blob/master/Makefile#L65) explicitely says to install these files in $(DATA_PATH) so I assume this path was incorrectly set when the package was built. Rebuild and test this time :) Severity grave because the program does not work at all by default unless you find the workaround. Thank you in advance
Processed: Bug#943448 marked as pending in beets
Processing control commands: > tag -1 pending Bug #943448 [beets] beets autopkgtest unnecessarily tests against non-default python Added tag(s) pending. -- 943448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943448: marked as pending in beets
Control: tag -1 pending Hello, Bug #943448 in beets reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/beets/commit/1977a03530609fe0a4dc1b4dd8cde5b9b8e3ddc1 Run autopkgtests only against the default Python 3. (Closes: #943448) (this message was generated automatically) -- Greetings https://bugs.debian.org/943448
Bug#944474: marked as done (autopkg tests fail on 32bit architectures)
Your message dated Wed, 27 Nov 2019 18:35:22 + with message-id and subject line Bug#944474: fixed in openblas 0.3.7+ds-4 has caused the Debian Bug report #944474, regarding autopkg tests fail on 32bit architectures 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.) -- 944474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:openblas Version: 0.3.7+ds-3 Severity: serious Tags: sid bullseye patch The autopkg tests fail on 32bit architectures, because the 64bit packages are not available. Feel free to extend the list of 32bit archs to other architectures. http://launchpadlibrarian.net/450747895/openblas_0.3.7+ds-3_0.3.7+ds-3ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: openblas Source-Version: 0.3.7+ds-4 We believe that the bug you reported is fixed in the latest version of openblas, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated openblas 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, 27 Nov 2019 17:49:02 +0100 Source: openblas Architecture: source Version: 0.3.7+ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Sébastien Villemot Closes: 944474 Changes: openblas (0.3.7+ds-4) unstable; urgency=medium . * Don’t run the 64-bit autopkgtests on 32-bit architectures. Thanks to Matthias Klose (Closes: #944474) * Bump S-V to 4.4.1 Checksums-Sha1: 9f176e04da9af081bf7813fabfc04cd455ccb41b 4821 openblas_0.3.7+ds-4.dsc 1c5a717ed91bbf4336e1517794d0fc5c4a767acf 21120 openblas_0.3.7+ds-4.debian.tar.xz 23069b75b4fd0c456688af18babec80342177afe 12769 openblas_0.3.7+ds-4_amd64.buildinfo Checksums-Sha256: 91da0fb10cfb0103184d3b8508d964a7d5086dbcbec6aefdb776d930e15d5245 4821 openblas_0.3.7+ds-4.dsc 050fcb24708b72689fc52e3ebf444ec13766a4da11514fb99a4fff734e75e74d 21120 openblas_0.3.7+ds-4.debian.tar.xz 60d1e60c215c2475d5c7e04c5656bd8a2975ae153c6d8a3d206ec59b701797db 12769 openblas_0.3.7+ds-4_amd64.buildinfo Files: e944fe44dcba3d521ed5084d3b9d7f02 4821 devel optional openblas_0.3.7+ds-4.dsc 1084e60d2cb4c48ccf2b17efdd77991d 21120 devel optional openblas_0.3.7+ds-4.debian.tar.xz 93b2fab0e67004cb03b36c342d964b20 12769 devel optional openblas_0.3.7+ds-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl3evCYACgkQLOzpNQ7O vkos+BAAnN24YAiSpp0P+7p7Q4LoPus/3+ydbBoErj/1LS6wKWFQmx6u1yGb84NR w6Mvy8Fmygv4WlFE+AbmEm/BtvST+W7mNryREk5VdbVGqRsHyHzzbOlWcKCYvnS/ mIZmOFtFXwiz51aMMT4+mOaW1mzOfqrN6YTQP6dLJQYX46XrWNKxykKuzZDcckKt Pw+k84PXEPfuQRpPF7ze034yedBTMNDHuNTCsvO6ZaN2MHFo/vy7MG7IXURCWSA3 e67W95k8e2YNr6agu8NvDlRRDp5muwol1Co3nI/PD+b5c888VFN7KWDEMcnnN9aB w7WSeWpm0kJWq+7usrk+Sbza69NJfsu9FyaZp/pL1e0ANF7nwi2FdRnDipfy4q/t f8xzbwjagEK4MosZEf7K0Q2aD3HFEorM52NdWuw314bOd5si+Gzf6nG9nruuP4vt ewhyf6B/7WntSrC9hzA1EIwGQNrYqwwR0EhVSUEPzMynWc5ZRQMpKM2HEXPKtxIy /OVTuwZ+m8kZjzh25w70/5r+V65rWZam1gb01owdplTSLEZzRplYiqQqM4hDZYsq vNrXJB5H/b91m8yWh5rzzToh1emV4MSa8qphVcRfjNp7o9ZDu2M//R01rkFnvD2Y 2Llq3XWkTW7GtHQiDcyFLPwNNOo9D2ACFcLeP+yL5H0PgnTBS/0= =mq1S -END PGP SIGNATURE End Message ---
Bug#942056: [ovs-dev] [PATCH] debian: Update list of copyright holders.
On Wed, Oct 9, 2019 at 10:35 AM Ben Pfaff wrote: > > The list of copyright holders was incomplete and out of date. This > updates it based on a "grep" for copyright notices, which I reviewed by > hand. > > CC: 942...@bugs.debian.org > Reported-by: Chris Lamb > Reported-at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942056 > Signed-off-by: Ben Pfaff > --- LGTM. Acked-by: Yi-Hung Wei
Bug#945214: Confirming the issue
I have the same problem with different packages on debian sid. There is any workaround to fix it until a new release?
Bug#945595: New mpv in sid breaks smplayer
Package: smplayer Version: 19.10.2~ds0-0.siduction Severity: grave Hi, new mpv 0.30* don't play well with smplayer in sid - new 19.10.* will solve that problem. No action needed right now, will work on it. Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.11-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smplayer depends on: ii libc6 2.29-3 ii libgcc1 1:9.2.1-20 ii libqt5core5a5.12.5+dfsg-2 ii libqt5dbus5 5.12.5+dfsg-2 ii libqt5gui5 5.12.5+dfsg-2 ii libqt5network5 5.12.5+dfsg-2 ii libqt5script5 5.12.5+dfsg-2 ii libqt5widgets5 5.12.5+dfsg-2 ii libqt5xml5 5.12.5+dfsg-2 ii libstdc++6 9.2.1-20 ii libx11-62:1.6.8-1 ii mplayer 2:1.3.0-8+b5 ii mpv 0.30.0-1 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages smplayer recommends: ii smplayer-l10n19.10.2~ds0-0.siduction ii smplayer-themes 1:18.6.0-1 smplayer suggests no packages. -- no debconf information
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 944743 6.0.0-1 Bug #944743 [jupyter-notebook] jupyter-notebook: systemd user unit enabled by default, despite per-system TCP port Ignoring request to alter found versions of bug #944743 to the same values previously set > severity 944743 serious Bug #944743 [jupyter-notebook] jupyter-notebook: systemd user unit enabled by default, despite per-system TCP port Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 944743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942187: marked as done (libxdmf-dev: conflict with older libxdmf3)
Your message dated Wed, 27 Nov 2019 15:20:46 + with message-id and subject line Bug#942187: fixed in xdmf 3.0+git20190531-4 has caused the Debian Bug report #942187, regarding libxdmf-dev: conflict with older libxdmf3 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.) -- 942187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxdmf-dev Version: 3.0+git20190531-1 Severity: normal Dear Maintainer, I upgraded libxdmf-dev and libxdmf3 on my system (more precisely, I ran "sudo apt install libloki-dev" which caused the update of those 2 packages) and got the following error: Unpacking libxdmf-dev (3.0+git20190531-1) over (3.0+git20160803-5+b1) ... dpkg: error processing archive /var/cache/apt/archives/libxdmf-dev_3.0+git20190531-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/xdmf/openmpi/libXdmf.so', which is also in package libxdmf3:amd64 3.0+git20160803-5+b1 It seems that a file was moved from libxdmf3 to libxdmf-dev without adding any conflicts/replaces/breaks (whichever is required in this situation so apt updates things in the right order). It is easy enough to work around but it would still be good to fix it. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.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 libxdmf-dev depends on: ii libgzstream-dev 1.5+dfsg-4 ii libloki-dev 0.1.7-3+b3 ii libxdmf3 3.0+git20190531-1 libxdmf-dev recommends no packages. libxdmf-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: xdmf Source-Version: 3.0+git20190531-4 We believe that the bug you reported is fixed in the latest version of xdmf, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated xdmf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 27 Nov 2019 14:21:03 + Source: xdmf Architecture: source Version: 3.0+git20190531-4 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 942187 942468 Changes: xdmf (3.0+git20190531-4) unstable; urgency=medium . * Add Breaks: libxdmf3 to libxdmf-dev. Closes: #942187, #942468 * Depend on mpi-default-dev Checksums-Sha1: f4e07297506b475e8cd04e84588db9c80ced7ed7 2248 xdmf_3.0+git20190531-4.dsc b60d6361b357a19a3f18e191aca41c4d1f17d7bb 23044 xdmf_3.0+git20190531-4.debian.tar.xz Checksums-Sha256: edf1c359cd587bea010fce762f0b64bb6fd594b0c5d389a432f7b70669df239f 2248 xdmf_3.0+git20190531-4.dsc bc636c5eac2c363f5abb22037bc9692d3ee7fac0198556d051a4a3b71ca0c0a0 23044 xdmf_3.0+git20190531-4.debian.tar.xz Files: e4ad22de937db80723fe0d5ff24f330f 2248 science optional xdmf_3.0+git20190531-4.dsc 35ecf344299d37284db14ea24854cb03 23044 science optional xdmf_3.0+git20190531-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl3ejOAACgkQy+a7Tl2a 06XNDg/+IKofLMnkJRY+xx0WsuXNMHPs5qjCydPdLNThUohXcg+FiPaKTM+mqq+M VAI5ffwp+MHoRX+Kv87n3BbNnZBdE+QeQ0h9jUsuKvo2ppo0/sGe52Uo2uiAWPtb 7xVLvYVYuozJ22OfXFHJ1NrE+dCxzNCgeIXbYRK45g3DWCbzdLAMMqcy2dn0wYWV IydUTpBPquaeH9KVhDmKHSsrmt9wyqnlDY7uEtNg4p/IFQRh6HaxuVNFL7udtuA7 aCp3aYwTF2lVdwaL4IoqxZXpfuHl4SFyxMUxw6dBI1xZ4bGX8lYG0SkutdO8r+IW q4WhbotoPoYDrCQLEWPF1aGmlRJamD0r5+UD37fwqDaOJIenIBwgzSZwNj7at0MU 292iCBO9GRXDJoECQTSbfL92k1WyUIWG5x/z/Q9QVj6qBetKJsFHOIe9PthDLhju nvxYFearnt4UX1uVW1Vjm95olOshk3SrcOjydZOxvqKUl+tblKJjlRmp+drucuLZ
Bug#942468: marked as done (libxdmf-dev: Incompatible libloki header)
Your message dated Wed, 27 Nov 2019 15:20:46 + with message-id and subject line Bug#942468: fixed in xdmf 3.0+git20190531-4 has caused the Debian Bug report #942468, regarding libxdmf-dev: Incompatible libloki header 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.) -- 942468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxdmf-dev Version: 3.0+git20160803-5+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Starting in version 3.0+git20190531-1 of this package, the libloki header were removed and the dependency on libloki-dev was introduced. Unfortunately, libxdmf has modified the core/loki/Visitor.h header file from the original libloki code (see https://gitlab.kitware.com/xdmf/xdmf/blob/master/core/loki/Visitor.h). The original header file from the libloki-dev package is incompatible with the libxdmf code, which means that no application can be built with libxdmf-dev version 3.0+git20190531-1. Removing the libloki and libloki-dev packages and downgrading to libxdmf-dev version 3.0+git20160803-5 fixes the issue, since that resotres the libloki headers shipped with libxdmf. I recommend removing the libloki-dev depencency and mark it as conflicting again (which it is), and shipping the libloki headers with the libxdmf-dev package (as does the xdmf code at https://gitlab.kitware.com/xdmf/xdmf). Thanks for mainting this package! Best, Jonas -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/48 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libxdmf-dev depends on: ii libgzstream-dev 1.5+dfsg-4 ii libxdmf3 3.0+git20160803-5+b1 libxdmf-dev recommends no packages. libxdmf-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: xdmf Source-Version: 3.0+git20190531-4 We believe that the bug you reported is fixed in the latest version of xdmf, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated xdmf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 27 Nov 2019 14:21:03 + Source: xdmf Architecture: source Version: 3.0+git20190531-4 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 942187 942468 Changes: xdmf (3.0+git20190531-4) unstable; urgency=medium . * Add Breaks: libxdmf3 to libxdmf-dev. Closes: #942187, #942468 * Depend on mpi-default-dev Checksums-Sha1: f4e07297506b475e8cd04e84588db9c80ced7ed7 2248 xdmf_3.0+git20190531-4.dsc b60d6361b357a19a3f18e191aca41c4d1f17d7bb 23044 xdmf_3.0+git20190531-4.debian.tar.xz Checksums-Sha256: edf1c359cd587bea010fce762f0b64bb6fd594b0c5d389a432f7b70669df239f 2248 xdmf_3.0+git20190531-4.dsc bc636c5eac2c363f5abb22037bc9692d3ee7fac0198556d051a4a3b71ca0c0a0 23044 xdmf_3.0+git20190531-4.debian.tar.xz Files: e4ad22de937db80723fe0d5ff24f330f 2248 science optional xdmf_3.0+git20190531-4.dsc 35ecf344299d37284db14ea24854cb03 23044 science optional xdmf_3.0+git20190531-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl3ejOAACgkQy+a7Tl2a 06XNDg/+IKofLMnkJRY+xx0WsuXNMHPs5qjCydPdLNThUohXcg+FiPaKTM+mqq+M VAI5ffwp+MHoRX+Kv87n3BbNnZBdE+QeQ0h9jUsuKvo2ppo0/sGe52Uo2uiAWPtb 7xVLvYVYuozJ22OfXFHJ1NrE+dCxzNCgeIXbYRK45g3DWCbzdLAMMqcy2dn0wYWV IydUTpBPquaeH9KVhDmKHSsrmt9wyqnlDY7uEtNg4p/IFQRh6HaxuVNFL7udtuA7 aCp3aYwTF2lVdwaL4IoqxZXpfuHl4SFyxMUxw6dBI1xZ4bGX8lYG0SkutdO8r+IW q4WhbotoPoYDrCQLEWPF1aGmlRJamD0r5+UD37fwqDaOJIenIBwgzSZwNj7at0MU
Bug#945591: ruby-pry-byebug: ships /usr/bin/rubocop, /usr/bin/bundle
Package: ruby-pry-byebug Version: 3.7.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../ruby-pry-byebug_3.7.0-1_all.deb ... Unpacking ruby-pry-byebug (3.7.0-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-pry-byebug_3.7.0-1_all.deb (--unpack): trying to overwrite '/usr/bin/rubocop', which is also in package rubocop 0.52.1+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/ruby-pry-byebug_3.7.0-1_all.deb Preparing to unpack .../ruby-pry-byebug_3.7.0-1_all.deb ... Unpacking ruby-pry-byebug (3.7.0-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-pry-byebug_3.7.0-1_all.deb (--unpack): trying to overwrite '/usr/bin/bundle', which is also in package ruby-bundler 1.17.3-3 Errors were encountered while processing: /var/cache/apt/archives/ruby-pry-byebug_3.7.0-1_all.deb cheers, Andreas rubocop=0.52.1+dfsg-1_ruby-pry-byebug=3.7.0-1.gz Description: application/gzip
Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.
On 11/27/19 1:19 PM, Michael Crusoe wrote: > On Thu, 21 Nov 2019 10:35:24 -0300 > =?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= > mailto:lisan...@debian.org>> wrote: >> Source: cppreference-doc >> Version: 20170409-1 >> Severity: serious >> Justification: FTBFS >> >> Hi! Your package is currently trying to install a file no longer > created since Qt4 support was dropped. >> There seems to be Qt5 build dependencies, so maybe something else is > going on. If you need help please pin me. > > Maybe this patch from Ubuntu will help? > http://patches.ubuntu.com/c/cppreference-doc/cppreference-doc_20170409-1.1ubuntu1.patch Hi, I will look into this bug ASAP. Couldn't do this so far due to lack of time due to my work. Regards, Povilas
Processed: reassign 944135 to src:linux, tagging 945489, tagging 945567, tagging 945566, tagging 945545
Processing commands for cont...@bugs.debian.org:
> reassign 944135 src:linux
Bug #944135 {Done: Bdale Garbee } [linux-image-5.2.0-3-amd64]
laptop audio not working
Warning: Unknown package 'linux-image-5.2.0-3-amd64'
Bug reassigned from package 'linux-image-5.2.0-3-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.2.17+1.
Ignoring request to alter fixed versions of bug #944135 to the same values
previously set
> tags 945489 + experimental
Bug #945489 [src:llvm-toolchain-9] llvm-toolchain-9: autopkgtest needs update
for new version of cmake: fails on warning
Added tag(s) experimental.
> tags 945567 + sid bullseye
Bug #945567 [src:network-manager-strongswan] network-manager-strongswan FTBFS:
error: G_ADD_PRIVATE
Added tag(s) sid and bullseye.
> tags 945566 + sid bullseye
Bug #945566 {Done: Mike Gabriel }
[src:ayatana-indicator-application] ayatana-indicator-application FTBFS: error:
G_ADD_PRIVATE
Added tag(s) bullseye and sid.
> tags 945545 + sid bullseye
Bug #945545 [src:xpp] xpp FTBFS: error: invalid use of incomplete type 'ipp_t'
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
944135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944135
945489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945489
945545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945545
945566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945566
945567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): rework bugs
Processing commands for cont...@bugs.debian.org: > affects 944636 ginkgocadx Bug #944636 [src:insighttoolkit4] insighttoolkit4: CMake missing files for imported targets Added indication that 944636 affects ginkgocadx > affects 944636 elastix Bug #944636 [src:insighttoolkit4] insighttoolkit4: CMake missing files for imported targets Added indication that 944636 affects elastix > merge 944636 945505 945454 Bug #944636 [src:insighttoolkit4] insighttoolkit4: CMake missing files for imported targets Unable to merge bugs because: affects of #945505 is '' not 'elastix,ginkgocadx,src:otb' package of #945505 is 'insighttoolkit4' not 'src:insighttoolkit4' affects of #945454 is '' not 'elastix,ginkgocadx,src:otb' package of #945454 is 'insighttoolkit4' not 'src:insighttoolkit4' Failed to merge 944636: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 944636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944636 945454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945454 945505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): rework bugs
Processing commands for cont...@bugs.debian.org: > reassign 945505 insighttoolkit4 4.13.2-dfsg1-1 Bug #945505 [src:ginkgocadx] ginkgocadx: FTBFS with current insighttoolkit and gdcm Bug reassigned from package 'src:ginkgocadx' to 'insighttoolkit4'. No longer marked as found in versions ginkgocadx/3.8.8-2. Ignoring request to alter fixed versions of bug #945505 to the same values previously set Bug #945505 [insighttoolkit4] ginkgocadx: FTBFS with current insighttoolkit and gdcm There is no source info for the package 'insighttoolkit4' at version '4.13.2-dfsg1-1' with architecture '' Unable to make a source version for version '4.13.2-dfsg1-1' Marked as found in versions 4.13.2-dfsg1-1. > reassign 945454 insighttoolkit4 4.13.2-dfsg1-1 Bug #945454 [src:elastix] elastix: FTBFS with current opencv and gdcm Bug reassigned from package 'src:elastix' to 'insighttoolkit4'. No longer marked as found in versions elastix/4.9.0-1. Ignoring request to alter fixed versions of bug #945454 to the same values previously set Bug #945454 [insighttoolkit4] elastix: FTBFS with current opencv and gdcm There is no source info for the package 'insighttoolkit4' at version '4.13.2-dfsg1-1' with architecture '' Unable to make a source version for version '4.13.2-dfsg1-1' Marked as found in versions 4.13.2-dfsg1-1. > merge 944636 945505 945454 Bug #944636 [src:insighttoolkit4] insighttoolkit4: CMake missing files for imported targets Unable to merge bugs because: affects of #945454 is '' not 'src:otb' package of #945454 is 'insighttoolkit4' not 'src:insighttoolkit4' affects of #945505 is '' not 'src:otb' package of #945505 is 'insighttoolkit4' not 'src:insighttoolkit4' Failed to merge 944636: Did not alter merged bugs. > affects 944636 ginkgocadx elastix Failed to mark 944636 as affecting package(s): failed to get lock on /srv/bugs.debian.org/spool/lock/944636 -- Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/944636 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > End of message, stopping processing here. Please contact me if you need assistance. -- 944636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944636 945454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945454 945505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.
On Thu, 21 Nov 2019 10:35:24 -0300 =?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= < lisan...@debian.org> wrote: > Source: cppreference-doc > Version: 20170409-1 > Severity: serious > Justification: FTBFS > > Hi! Your package is currently trying to install a file no longer created since Qt4 support was dropped. > There seems to be Qt5 build dependencies, so maybe something else is going on. If you need help please pin me. Maybe this patch from Ubuntu will help? http://patches.ubuntu.com/c/cppreference-doc/cppreference-doc_20170409-1.1ubuntu1.patch
Bug#945566: marked as done (ayatana-indicator-application FTBFS: error: G_ADD_PRIVATE)
Your message dated Wed, 27 Nov 2019 10:49:30 +
with message-id
and subject line Bug#945566: fixed in ayatana-indicator-application 0.5.3-1
has caused the Debian Bug report #945566,
regarding ayatana-indicator-application FTBFS: error: G_ADD_PRIVATE
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.)
--
945566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ayatana-indicator-application
Version: 0.5.2-2
Severity: serious
Tags: ftbfs
ayatana-indicator-application fails to build from source in unstable.
It's a regression of recent glib2.0 changes.
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ayatana-indicator-application_0.5.2-2.rbuild.log.gz
| application-service-watcher.c: In function 'application_service_watcher_init':
| application-service-watcher.c:155:13: error: G_ADD_PRIVATE [-Werror]
| 155 | ApplicationServiceWatcherPrivate * priv =
APPLICATION_SERVICE_WATCHER_GET_PRIVATE(self);
| | ^~~
Also seen by crossqa since almost two months:
http://crossqa.debian.net/build/ayatana-indicator-application_0.5.2-2_ppc64el_20191001070120.log
Helmut
--- End Message ---
--- Begin Message ---
Source: ayatana-indicator-application
Source-Version: 0.5.3-1
We believe that the bug you reported is fixed in the latest version of
ayatana-indicator-application, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 945...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated
ayatana-indicator-application package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 27 Nov 2019 11:19:34 +0100
Source: ayatana-indicator-application
Architecture: source
Version: 0.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Ayatana Packagers
Changed-By: Mike Gabriel
Closes: 945566
Changes:
ayatana-indicator-application (0.5.3-1) unstable; urgency=medium
.
* New upstream release.
- Avoid GLib2.0's deprecated privates ABI. (Closes: #945566)."
* debian/patches:
+ Drop 0001-Make-systemd-optional.-If-systemd-is-not-available-a.patch.
Shipped upstream.
* debian/{control,compat}:
+ Switch to debhelper-compat notation. Bump DH compat level to version 12.
* debian/control:
+ Set Section: from gnome to x11.
+ Bump Standards-Version: to 4.4.1. No changes needed.
+ Add Rules-Requires-Root: field and set it to "no".
Checksums-Sha1:
93d67862bc0151b386dc2a2cc81de70bb7b1fece 2870
ayatana-indicator-application_0.5.3-1.dsc
fcfcebc011a12aa6b0b53bf135203cd776287a19 99579
ayatana-indicator-application_0.5.3.orig.tar.gz
a475eedabd486ddaf8b9926e14682b2cad3a5461 833
ayatana-indicator-application_0.5.3.orig.tar.gz.asc
bad6242bf8007975f80685b0871252341020b2f3 12168
ayatana-indicator-application_0.5.3-1.debian.tar.xz
afc1c3c8919e3bc8ca793a3783598d9fe6e8e521 17970
ayatana-indicator-application_0.5.3-1_source.buildinfo
Checksums-Sha256:
5805696f00ee92a960e841d5a215f380c26da41a3a4760061af281f2947c48b8 2870
ayatana-indicator-application_0.5.3-1.dsc
f251967e76795536a4812011a14d71d30125297e31af5c969f0f7def364fc77d 99579
ayatana-indicator-application_0.5.3.orig.tar.gz
0de71df1d597dbdd58b4a54ec828b3895e1001ecf22058aa0e27cd9094274be8 833
ayatana-indicator-application_0.5.3.orig.tar.gz.asc
50617744432ad1a513a1fe850e40846fb84c9e15ffa6b0d7bbb795169002eb46 12168
ayatana-indicator-application_0.5.3-1.debian.tar.xz
b96b696a3dfa9d31637c7be66511398834de9d75eb1391f33ff282b3517cb7eb 17970
ayatana-indicator-application_0.5.3-1_source.buildinfo
Files:
a0e2c44cb866c7ef7c6948be12e86ef7 2870 x11 optional
ayatana-indicator-application_0.5.3-1.dsc
598ff644ea9d22b879e81dde23f1140b 99579 x11 optional
ayatana-indicator-application_0.5.3.orig.tar.gz
107ab9068abf9489b62fdc1d7276338a 833 x11 optional
ayatana-indicator-application_0.5.3.orig.tar.gz.asc
718b6fb24bf81865e1718f4fd72ff595 12168 x11 optional
ayatana-indicator-application_0.5.3-1.debian.tar.xz
6980d85d22d236cf2c476beb0ebb8fb2 17970 x11 optional
ayatana-indicator-application_0.5.3-1_source.buildinfo
Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged
On 2019, നവംബർ 27 2:04:19 PM IST, Romain Bignon wrote: >Hi, > >A new strange thing, I don't know if you encountered that, today at >6h32 >packagekit run, tried to restart gitlab, and failed: It'd be a good idea to turn off unattended upgrades in unstable. >Nov 27 06:32:24 weboob gitlab-unicorn[28831]: Bundler::GemNotFound: >Could not find gem 'rubyzip (>= 1.2.2, ~> 1.2)' in any of the gem >sources listed in your Gemfile. ruby-zip was updated to 2.0.0. >I had to install manually rubyzip with gem at the right version to fix >gitlab. > >To understand, packagekit has updated something? This should be fixed in latest version of gitlab. >Romain -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged
Hi, A new strange thing, I don't know if you encountered that, today at 6h32 packagekit run, tried to restart gitlab, and failed: Nov 27 06:32:18 weboob dbus-daemon[464]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.10456' (uid=0 pid=28562 comm="/usr/bin/gdbus call --system --dest org.freedeskto") Nov 27 06:32:18 weboob systemd[1]: Starting PackageKit Daemon... Nov 27 06:32:18 weboob PackageKit: daemon start Nov 27 06:32:18 weboob dbus-daemon[464]: [system] Successfully activated service 'org.freedesktop.PackageKit' Nov 27 06:32:18 weboob systemd[1]: Started PackageKit Daemon. Nov 27 06:32:18 weboob gitlab-workhorse[20628]: git.weboob.org 46.229.168.139 - - [2019/11/27:06:32:18 +0100] "GET /P4ncake/devel/tree/6f5f41fe574ad35b11e024b7c10bb2950d0689b2 HTTP/1.1" 200 40794 "" "Mozilla/5.0 (compatible; SemrushBot/6~bl; +http://www.semrush.com/bot.html)" %!f(int64=108) Nov 27 06:32:19 weboob systemd[1]: Reloading. Nov 27 06:32:19 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Nov 27 06:32:19 weboob systemd[1]: Configuration file /etc/systemd/system/postfix.service.d/override.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. Nov 27 06:32:19 weboob systemd[1]: /lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done" Nov 27 06:32:19 weboob systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Nov 27 06:32:20 weboob systemd[1]: Reloading. Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Nov 27 06:32:20 weboob systemd[1]: Configuration file /etc/systemd/system/postfix.service.d/override.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done" Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Nov 27 06:32:20 weboob systemd[1]: Reloading. Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Nov 27 06:32:20 weboob systemd[1]: Configuration file /etc/systemd/system/postfix.service.d/override.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done" Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Nov 27 06:32:20 weboob gitaly[20604]: time="2019-11-27T06:32:20+01:00" level=error msg="lstat /var/lib/gitlab/repositories/+gitaly/cache: no such file or directory" storage=default Nov 27 06:32:20 weboob systemd[1]: Reloading. Nov 27 06:32:21 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Nov 27 06:32:21 weboob systemd[1]: Configuration file /etc/systemd/system/postfix.service.d/override.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. Nov 27 06:32:21 weboob systemd[1]: /lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done" Nov 27 06:32:21 weboob
Bug#885270: bumping severity of pygtk bugs
On 26/11/2019 23:27, Steve Conklin wrote: > I have no intention to port it. Filing a removal bug sounds appropriate. Agreed, time for it to vanish. Colin -- Colin Tuckley | +44(0)1223 830814 | PGP/GnuPG Key Id G8TMV | +44(0)7799 143369 | 0xFA0C410738C9D903
