Bug#944824: marked as done (pylint-celery (build-)depends on cruft package.)
Your message dated Tue, 10 Dec 2019 07:49:24 + with message-id and subject line Bug#944824: fixed in pylint-celery 0.3-5 has caused the Debian Bug report #944824, regarding pylint-celery (build-)depends on cruft package. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 944824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pylint-celery Version: 0.3-4 Severity: serious Tags: bullseye, sid, patch python3-plint-celery depends on and the pylint-celery source package build-depends on the pylint3 binary package which is no longer built by the pylint source package. The python 3 pylint functionlity is now in the pylint binary package. The build-dependency needs to be fixed manually, the binary dependency seems to follow along automatically once the built-dependency is fixed and the package rebuilt. Debdiff attatched, no intent to NMU. diff -Nru pylint-celery-0.3/debian/changelog pylint-celery-0.3/debian/changelog --- pylint-celery-0.3/debian/changelog 2018-09-26 10:59:29.0 + +++ pylint-celery-0.3/debian/changelog 2019-11-16 01:43:50.0 + @@ -1,3 +1,10 @@ +pylint-celery (0.3-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Update build-dependency for pylint3->pylint package rename. + + -- Peter Michael Green Sat, 16 Nov 2019 01:43:50 + + pylint-celery (0.3-4) unstable; urgency=medium * Team upload. diff -Nru pylint-celery-0.3/debian/control pylint-celery-0.3/debian/control --- pylint-celery-0.3/debian/control2018-09-26 10:58:31.0 + +++ pylint-celery-0.3/debian/control2019-11-16 01:43:50.0 + @@ -5,7 +5,7 @@ Uploaders: ChangZhuo Chen (陳昌倬) Build-Depends: debhelper-compat (= 11), dh-python, - pylint3, + pylint (>= 2.2.2-2), python3-all, python3-astroid, python3-celery, --- End Message --- --- Begin Message --- Source: pylint-celery Source-Version: 0.3-5 We believe that the bug you reported is fixed in the latest version of pylint-celery, 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. Gianfranco Costamagna (supplier of updated pylint-celery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Dec 2019 08:36:29 +0100 Source: pylint-celery Binary: python3-pylint-celery Architecture: source Version: 0.3-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Gianfranco Costamagna Description: python3-pylint-celery - Pylint plugin for code using the Celery library (Python3) Closes: 944824 Changes: pylint-celery (0.3-5) unstable; urgency=medium . * Team upload * Switch to new pylint (Closes: #944824) Checksums-Sha1: 926a02c7d31ff985e2ca1845aa8a4ad16fe10373 2145 pylint-celery_0.3-5.dsc 025dadab76c1a8b9db2f14d124522637c01d323a 2876 pylint-celery_0.3-5.debian.tar.xz 2ef31c50808bf387faf9517198ca26de55ebe579 8695 pylint-celery_0.3-5_source.buildinfo Checksums-Sha256: 659b7578f6c6d663fb3f0e110b9b4f6b902424891c0c05266ebb60345e8a1905 2145 pylint-celery_0.3-5.dsc c8cca1c49d89dec1c37021081ffd8314f0d0f4a3381c6e55987c506122a06486 2876 pylint-celery_0.3-5.debian.tar.xz 7ba32fd5b1f7cf08ac0f147a75c8b5d582cfe03545a753dac4e76c6e219bb815 8695 pylint-celery_0.3-5_source.buildinfo Files: 0c8ef078a6975bc5ba4da7557beb0146 2145 python optional pylint-celery_0.3-5.dsc 0b9b8cb728851b5078f16b1e980a2efb 2876 python optional pylint-celery_0.3-5.debian.tar.xz 9d3f37f5da556566d8be70c1f86519bb 8695 python optional pylint-celery_0.3-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIyBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl3vSyoACgkQ808JdE6f Xdni8g/4uG2sxuA1du+Kjg8xmlmOIfo7XjUfNwsWqXEny0k3Bn3UBSfY1SNqiJO3 GUxLc0B/mnkkAvlcAnCBrh6frzkSzU0kqnpOo3wJVlQcwDlugJ3pxG12bgIbJPLF EPI0k9oJE2qSb1Z7LwJBT25Crau3nLEtq4OTw6mpm8GI8XQQDr6FPauF9qwrQ3sw 9dW/ZfxRB0EmLi+1qhD81jscCa3QSrFhjVnc3XoqOzmU2AvxLMXiewxKDFUaCzUu
Processed: Re: Bug#940906: make autopkgtest working
Processing control commands: > severity -1 serious Bug #940906 [src:glm] glm: autopkgtest regression: CMake Error at CMakeLists.txt:6 (find_package): Severity set to 'serious' from 'important' -- 940906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938520: marked as done (sozi: Python2 removal in sid/bullseye)
Your message dated Tue, 10 Dec 2019 05:09:38 + with message-id and subject line Bug#946489: Removed package(s) from unstable has caused the Debian Bug report #938520, regarding sozi: 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.) -- 938520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sozi Version: 12.05-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:sozi 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: 12.05-1.1+rm Dear submitter, as the package sozi 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/946489 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#885482: marked as done (sozi: Depends on unmaintained pygtk)
Your message dated Tue, 10 Dec 2019 05:09:38 + with message-id and subject line Bug#946489: Removed package(s) from unstable has caused the Debian Bug report #885482, regarding sozi: 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.) -- 885482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sozi Version: 12.05-1.1 Severity: important 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: 12.05-1.1+rm Dear submitter, as the package sozi 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/946489 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#936978: marked as done (magicor: Python2 removal in sid/bullseye)
Your message dated Tue, 10 Dec 2019 05:09:01 + with message-id and subject line Bug#946488: Removed package(s) from unstable has caused the Debian Bug report #936978, regarding magicor: 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.) -- 936978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:magicor Version: 1.1-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html 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:magicor 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.1-4+rm Dear submitter, as the package magicor 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/946488 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#885352: marked as done (magicor: Depends on unmaintained pygtk)
Your message dated Tue, 10 Dec 2019 05:09:01 + with message-id and subject line Bug#946488: Removed package(s) from unstable has caused the Debian Bug report #885352, regarding magicor: 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.) -- 885352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: magicor Version: 1.1-4 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster X-Debbugs-CC: vch...@debian.org 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.1-4+rm Dear submitter, as the package magicor 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/946488 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#937568: marked as done (pytest-xdist: Python2 removal in sid/bullseye)
Your message dated Tue, 10 Dec 2019 02:43:17 + with message-id and subject line Bug#937568: fixed in pytest-xdist 1.30.0-2 has caused the Debian Bug report #937568, regarding pytest-xdist: 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.) -- 937568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pytest-xdist Version: 1.29.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:pytest-xdist 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-xdist Source-Version: 1.30.0-2 We believe that the bug you reported is fixed in the latest version of pytest-xdist, 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. Scott Talbert (supplier of updated pytest-xdist package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 Dec 2019 20:32:37 -0500 Source: pytest-xdist Architecture: source Version: 1.30.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Scott Talbert Closes: 937568 Changes: pytest-xdist (1.30.0-2) unstable; urgency=medium . * Remove Python 2 support (Closes: #937568) Checksums-Sha1: 4cc01b3c25b7f6725cb68149bd3c9e639ccb1448 2278 pytest-xdist_1.30.0-2.dsc 371cb65e29710743a9592b85fbe4c00964a5950a 4492 pytest-xdist_1.30.0-2.debian.tar.xz 781e38ba695a0349fbff81acb2f766a40f502fa1 6965 pytest-xdist_1.30.0-2_amd64.buildinfo Checksums-Sha256: fdd423f3c30bdcad8821cc303ce8d9595943e07de8cc94df37d16ab8e7043eaf 2278 pytest-xdist_1.30.0-2.dsc 6119887f4955fcb91743bee87c92c2680eb55c7254370e8fd0a20fcea579c35f 4492 pytest-xdist_1.30.0-2.debian.tar.xz 5fd103d497c477813bc773338e39dc664ac31fa062e4e9f1a205a5e5db55d7e8 6965 pytest-xdist_1.30.0-2_amd64.buildinfo Files:
Bug#946497: zfs-dkms: fails to build module for 5.3.0-3-amd64
[Andreas Beckmann] > during a test with piuparts I noticed your package failed to install. Thank you for the heads up. Looking at the attached log, I see gcc-9 is installed, and thus the error message is very strange: > Building initial module for 5.3.0-3-amd64 > configure: error: in `/var/lib/dkms/zfs/0.8.2/build': > configure: error: no acceptable C compiler found in $PATH > See `config.log' for more details Can gcc be broken? Or is it dkms? Or something else? I notice https://ci.debian.net/packages/z/zfs-linux/testing/amd64/ > passed 2019-12-06 13:15:16 UTC. Is the test insufficient to discover this problem, or did something change in the mean time? -- Happy hacking Petter Reinholdtsen
Processed: severity of 946492 is serious, found 903794 in 3.0-a9+debian.1-3
Processing commands for cont...@bugs.debian.org: > severity 946492 serious Bug #946492 [vdjtools] vdjtools: broken symlink: /usr/share/java/vdjtools.jar -> vdjtools-1.2.1+git20190311.jar Severity set to 'serious' from 'normal' > found 903794 3.0-a9+debian.1-3 Bug #903794 [lmbench-doc] lmbench-doc: broken symlinks: /usr/share/doc/lmbench-doc/man/*.8 -> lmbench.8 Marked as found in versions lmbench/3.0-a9+debian.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 903794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903794 946492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946497: zfs-dkms: fails to build module for 5.3.0-3-amd64
Package: zfs-dkms Version: 0.8.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up zfs-dkms (0.8.2-3) ... Loading new zfs-0.8.2 DKMS files... It is likely that 4.9.0-9-amd64 belongs to a chroot's host Building for 5.3.0-3-amd64 Building initial module for 5.3.0-3-amd64 configure: error: in `/var/lib/dkms/zfs/0.8.2/build': configure: error: no acceptable C compiler found in $PATH See `config.log' for more details Error! Bad return status for module build on kernel: 5.3.0-3-amd64 (x86_64) Consult /var/lib/dkms/zfs/0.8.2/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for libc-bin (2.29-5) ... Errors were encountered while processing: zfs-dkms /var/lib/dkms/zfs/0.8.2/build/make.log contains: DKMS make.log for zfs-0.8.2 for kernel 5.3.0-3-amd64 (x86_64) Tue Dec 10 00:50:52 UTC 2019 make: *** No targets specified and no makefile found. Stop. cheers, Andreas zfs-dkms_0.8.2-3.log.gz Description: application/gzip
Bug#946494: cpl-plugin-kmos-calib: download location no longer available ?
Package: cpl-plugin-kmos-calib Version: 2.1.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-kmos-calib (2.1.0+dfsg-1) ... --2019-12-09 20:55:08-- ftp://ftp.eso.org/pub/dfs/pipelines/kmos/kmos-kit-2.1.0.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/kmos ... done. ==> SIZE kmos-kit-2.1.0.tar.gz ... done. ==> PASV ... done.==> RETR kmos-kit-2.1.0.tar.gz ... No such file 'kmos-kit-2.1.0.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2019-12-09 20:55:08-- ftp://ftp.eso.org/pub/dfs/pipelines/kmos/kmos-kit-2.1.0-1.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/kmos ... done. ==> SIZE kmos-kit-2.1.0-1.tar.gz ... done. ==> PASV ... done.==> RETR kmos-kit-2.1.0-1.tar.gz ... No such file 'kmos-kit-2.1.0-1.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2019-12-09 20:55:09-- ftp://ftp.eso.org/pub/dfs/pipelines/kmos/kmos-kit-2.1.0-2.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/kmos ... done. ==> SIZE kmos-kit-2.1.0-2.tar.gz ... done. ==> PASV ... done.==> RETR kmos-kit-2.1.0-2.tar.gz ... No such file 'kmos-kit-2.1.0-2.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2019-12-09 20:55:09-- ftp://ftp.eso.org/pub/dfs/pipelines/kmos/kmos-kit-2.1.0-3.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/kmos ... done. ==> SIZE kmos-kit-2.1.0-3.tar.gz ... done. ==> PASV ... done.==> RETR kmos-kit-2.1.0-3.tar.gz ... No such file 'kmos-kit-2.1.0-3.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2019-12-09 20:55:09-- ftp://ftp.eso.org/pub/dfs/pipelines/kmos/kmos-kit-2.1.0-4.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/kmos ... done. ==> SIZE kmos-kit-2.1.0-4.tar.gz ... done. ==> PASV ... done.==> RETR kmos-kit-2.1.0-4.tar.gz ... No such file 'kmos-kit-2.1.0-4.tar.gz'. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2019-12-09 20:55:10-- ftp://ftp.eso.org/pub/dfs/pipelines/kmos/kmos-kit-2.1.0-5.tar.gz => '-' Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53 Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done.==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /pub/dfs/pipelines/kmos ... done. ==> SIZE kmos-kit-2.1.0-5.tar.gz ... done. ==> PASV ... done.==> RETR kmos-kit-2.1.0-5.tar.gz ... No such file 'kmos-kit-2.1.0-5.tar.gz'. gzip: stdin: unexpected end of
Bug#946396: marked as done (glibc+libxcrypt breaks cross-toolchain-base)
Your message dated Mon, 09 Dec 2019 23:19:57 +
with message-id
and subject line Bug#946396: fixed in glibc 2.29-6
has caused the Debian Bug report #946396,
regarding glibc+libxcrypt breaks cross-toolchain-base
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
946396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.29-5
Severity: serious
Justification: installation failure
Control: affects -1 + src:cross-toolchain-base
Since glibc added dependencies on libxcrypt, building
cross-toolchain-base produces packages that are not installable:
| $ dpkg-deb -I libc6-dev-arm64-cross_2.29-5cross1_all.deb
| new Debian package, version 2.0.
| size 2261068 bytes: control archive=12892 bytes.
| 833 bytes,17 lines control
|40350 bytes, 515 lines md5sums
| Package: libc6-dev-arm64-cross
| Version: 2.29-5cross1
| Section: libdevel
| Priority: optional
| Architecture: all
| Maintainer: GNU Libc Maintainers
| Source: cross-toolchain-base (42)
| Provides: libc-dev-arm64-cross, libc6-dev-arm64-dcv1
| Depends: libc6-arm64-cross (= 2.29-5cross1), linux-libc-dev-arm64-cross,
libcrypt1-dev-arm64-cross
| Conflicts: libc0.1-dev-arm64-cross, libc0.3-dev-arm64-cross,
libc6.1-dev-arm64-cross
| Description: GNU C Library: Development Libraries and Header Files (for
cross-compiling)
| This package was generated by dpkg-cross for cross compiling.
| .
| Contains the symlinks, headers, and object files needed to compile
| and link programs which use the standard C library.
| Built-Using: binutils (= 2.33.1-5), linux (= 5.3.15-1), gcc-9 (= 9.2.1-21),
glibc (= 2.29-5)
| Multi-Arch: foreign
| $
However, there is no libcrypt1-dev-arm64-cross package produced by
anything in the archive. For this reason glibc/2.29-5 should not migrate
to testing until there is a solution to this problem.
Helmut
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-6
We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno (supplier of updated glibc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 10 Dec 2019 00:06:38 +0100
Source: glibc
Architecture: source
Version: 2.29-6
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 946396
Changes:
glibc (2.29-6) unstable; urgency=medium
.
* debian/shlibs-add-udebs: drop libcrypt.
* Fix rebootstrap and cross-toolchain-base (Closes: #946396):
- debian/control.in/libc: replace libcrypt1 by ${libcrypt:Depends} and
libcrypt1-dev by ${libcrypt-dev:Depends}.
- debian/rules.d/debhelper.mk: add libcrypt:Depends=libcrypt1 and
libcrypt-dev:Depends=libcrypt1-dev to substvars unless build with stage1
or stage2 profiles.
Checksums-Sha1:
4aa42ac5584987db3b727431965c89777037924e 8735 glibc_2.29-6.dsc
75326bfdcf2f7ca4856a10535a2d57bd17bd1068 854388 glibc_2.29-6.debian.tar.xz
57f22c1c56f1fb21421f1013a2be1f720099f813 7465 glibc_2.29-6_source.buildinfo
Checksums-Sha256:
e80a6b41e4ee7fb105bf7df8c4f149bfe7301e66300b60f6b3e0f7e50baf745b 8735
glibc_2.29-6.dsc
c888fc710170410897d5d843fb0496c91cf5acd8236b67dd693e99f930b9a8e9 854388
glibc_2.29-6.debian.tar.xz
d6f7be30e31b4be28282fece0d6fff0a2ba71fd54985e543c23ab41b866a0494 7465
glibc_2.29-6_source.buildinfo
Files:
59b0f6ef82b536880e3b25f87ecb64d7 8735 libs required glibc_2.29-6.dsc
88265b7b5ec15e0ede5197a274d9a1e4 854388 libs required
glibc_2.29-6.debian.tar.xz
4212b81b9d32e6a9c463e8fb1d1039f2 7465 libs required
glibc_2.29-6_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl3u1B4ACgkQE4jA+Jno
M2v2GQ/+LHeVLATqk1ZirNPi0zfgn+Zglf8uqVtsG/gvOI6/N7lg4mnK/6CaJI1u
iknzU/khqXuNkd8AN3Fr8B4dDcInQlmfQAgwbZ9OOp1w2FUEHikMPyuFGLAaVucb
1rxWK+t0vThz98ZaQzkZuwjVBAEl1EpyFdh7YN8UINRA4rUcJMzUt6K9n/f+RnZp
Processed: Bug#946396 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #946396 [src:glibc] glibc+libxcrypt breaks cross-toolchain-base Ignoring request to alter tags of bug #946396 to the same tags previously set -- 946396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946396: marked as pending in glibc
Control: tag -1 pending
Hello,
Bug #946396 in glibc 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/glibc-team/glibc/commit/d02a521442881d7afabee90eacc454b314e06e39
Fix rebootstrap and cross-toolchain-base (Closes: #946396):
* Fix rebootstrap and cross-toolchain-base (Closes: #946396):
- debian/control.in/libc: replace libcrypt1 by ${libcrypt:Depends} and
libcrypt1-dev by ${libcrypt-dev:Depends}.
- debian/rules.d/debhelper.mk: add libcrypt:Depends=libcrypt1 and
libcrypt-dev:Depends=libcrypt1-dev to substvars unless build with stage1
or stage2 profiles.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/946396
Processed: Bug#946396 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #946396 [src:glibc] glibc+libxcrypt breaks cross-toolchain-base Added tag(s) pending. -- 946396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946396: marked as pending in glibc
Control: tag -1 pending
Hello,
Bug #946396 in glibc 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/glibc-team/glibc/commit/d02a521442881d7afabee90eacc454b314e06e39
Fix rebootstrap and cross-toolchain-base (Closes: #946396):
* Fix rebootstrap and cross-toolchain-base (Closes: #946396):
- debian/control.in/libc: replace libcrypt1 by ${libcrypt:Depends} and
libcrypt1-dev by ${libcrypt-dev:Depends}.
- debian/rules.d/debhelper.mk: add libcrypt:Depends=libcrypt1 and
libcrypt-dev:Depends=libcrypt1-dev to substvars unless build with stage1
or stage2 profiles.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/946396
Bug#946484: marked as done (internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found)
Your message dated Mon, 09 Dec 2019 23:07:24 + with message-id and subject line Bug#946484: fixed in python-internetarchive 1.9.0-2 has caused the Debian Bug report #946484, regarding internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 946484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: internetarchive Version: 1.8.5-1 Severity: grave The ia command doesn't work at all: $ ia help Traceback (most recent call last): File "/usr/bin/ia", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3250, in @_call_aside File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3234, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in _build_master ws.require(__requires__) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'backports.csv' distribution was not found and is required by internetarchive -- System Information: Architecture: i386 Versions of packages internetarchive depends on: ii python3 3.7.5-3 ii python3-internetarchive 1.8.5-1 -- Jakub Wilk --- End Message --- --- Begin Message --- Source: python-internetarchive Source-Version: 1.9.0-2 We believe that the bug you reported is fixed in the latest version of python-internetarchive, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antoine Beaupré (supplier of updated python-internetarchive 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, 09 Dec 2019 17:06:20 -0500 Source: python-internetarchive Architecture: source Version: 1.9.0-2 Distribution: unstable Urgency: medium Maintainer: Antoine Beaupré Changed-By: Antoine Beaupré Closes: 946484 Changes: python-internetarchive (1.9.0-2) unstable; urgency=medium . * do not require backports.csv in Python 3.5+ (Closes: #946484) Checksums-Sha1: 2d5e2fb42df9979c82be5de3a7b07c54e387a1f0 1995 python-internetarchive_1.9.0-2.dsc e01905dcf0ff5d51864851e56f85f6324fa0904f 13420 python-internetarchive_1.9.0-2.debian.tar.xz d17f6d2dab30c91666bc81af1a07753de59f005b 7110 python-internetarchive_1.9.0-2_amd64.buildinfo Checksums-Sha256: 628f75ae525549523ff1e249bd8d1d3cf136cea7e6d775af854b2cb32e7ceff8 1995 python-internetarchive_1.9.0-2.dsc fbfb85d793c55bac0b78e7bdc4ced0fcee0b11984698231b902f5e632baa8fef 13420 python-internetarchive_1.9.0-2.debian.tar.xz 01dc9572c3d83e10dfb3a144dd945048886f1d22273fb0afff89c90cf23632a0 7110 python-internetarchive_1.9.0-2_amd64.buildinfo Files: 781b0b822cc2638f68e7505622a8b5aa 1995 python optional python-internetarchive_1.9.0-2.dsc bc6ea19e5434db332ac7a36c1f9e7907 13420 python optional python-internetarchive_1.9.0-2.debian.tar.xz 9e1597cf17caa5354dc6754b6a62c805 7110 python optional python-internetarchive_1.9.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl3ux5UACgkQPqHd3bJh 2Xsfpgf/W8agg4YsAzgQGRChFekbJwPI5ggkkZJtawCRbaBc8wwydReIoJDFRCzF raQmQgSMSfLDsVSm8yLRFuzAp9wQ54qLS2sfXD1nvizCymTs/I5afuyZYykAILvz rF6M+4ly/qlEVf/az2tE7I703qiTy3ry/GWtk5OcQGQFB5S+/ronNIQRoXtjdobS ck5mXXRDmbzz5sULHNSVNkjbUfRB4tcDHRfVy3XM9FqwKIDHk13vLM0k5G9wzX1a FNQlVYhVPWXyfI+Bs8yWT6wqR+GpsWiI2O7ZBOSfjmaUJB8IsFQqmNnnIXDfoQpl JXrgyFTvr8EjsIdPFYnZsJuD22jnyA== =krej -END PGP SIGNATURE End Message ---
Bug#946405: nextcloud-desktop: Nextcloud desktop client crash when trying to enter login/password
Hello Ludovic, I tried to collect some more information from your crash dump. With debug symbols this backtrace should look like below. I guess you are running a nvidia graphics card with the nouveau drivers? As a workaround it may work if you start the client from a terminal by following: export LIBGL_ALWAYS_SOFTWARE=1 nextcloud Or maybe this: export QT_XCB_FORCE_SOFTWARE_OPENGL=1 nextcloud Maybe you can confirm my findings, and forward the output of following commands to this bug: lspci | grep VGA glxinfo | grep -i -E "GLX_MESA_query_renderer.:" -A5 Kind regards, Bernhard From submitter | Reconstructed #0 0x7fe16d9b6bde | 0x7f1811853bde #1 0x7fe16d9b6cf0 | 0x7f1811853cf0 #2 0x7fe16d9b7327 | 0x7f1811854327 #3 0x7fe166ea4840 | 0x7f180ad41840 <__restore_rt+0>: mov$0xf,%rax #4 0x7fe152142a8c | 0x7f17f754ca8c in list_del at ../src/util/list.h:91 #5 0x7fe152142c87 | 0x7f17f754cc87 in nouveau_fence_update at ../src/gallium/drivers/nouveau/nouveau_fence.c:128 #6 0x7fe152142f83 | 0x7f17f754cf83 in nouveau_fence_wait at ../src/gallium/drivers/nouveau/nouveau_fence.c:219 #7 0x7fe1523cf490 | 0x7f17f77d9490 in st_finish (st=st@entry=0x562393326c90) at ../src/mesa/state_tracker/st_cb_flush.c:69 #8 0x7fe1523cf4e0 | 0x7f17f77d94e0 in st_glFinish (ctx=) at ../src/mesa/state_tracker/st_cb_flush.c:104 #9 0x7fe166a5f156 | 0x7f180a8fc156 in QQuickWidgetPrivate::render (this=0x562392ccb0b0, needsSync=) at qquickwidget.cpp:295 #10 0x7fe166a5f2b6 | 0x7f180a8fc2b6 in QQuickWidgetPrivate::renderSceneGraph (this=0x562392ccb0b0) at qquickwidget.cpp:339 #11 0x7fe1675e509b QObject::event() | 0x7f180b48209b in QObject::event (this=this@entry=0x5623930a2130, e=e@entry=0x7ffcf1848bb0) at kernel/qobject.cpp:1232 #12 0x7fe167f7496b QWidget::event() | 0x7f180be1196b in QWidget::event (this=this@entry=0x5623930a2130, event=event@entry=0x7ffcf1848bb0) at kernel/qwidget.cpp:9353 #13 0x7fe166a62e5d QQuickWidget::event() | 0x7f180a8ffe5d in QQuickWidget::event (this=0x5623930a2130, e=0x7ffcf1848bb0) at qquickwidget.cpp:1525 #14 0x7fe17207cb50 | 0x7f1815f19b50 in QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5 #15 0x7fe167f364c1 QApplicationPrivate::notify_helper() | 0x7f180bdd34c1 in QApplicationPrivate::notify_helper (this=this@entry=0x562392919dd0, receiver=receiver@entry=0x5623930a2130, e=e@entry=0x7ffcf1848bb0) at kernel/qapplication.cpp:3726 #16 0x7fe167f3d970 QApplication::notify()| 0x7f180bdda970 in QApplication::notify (this=0x7ffcf1848ef0, receiver=0x5623930a2130, e=0x7ffcf1848bb0) at kernel/qapplication.cpp:3485 #17 0x7fe1675bb4f9 QCoreApplication::notifyInternal2() | 0x7f180b4584f9 in QCoreApplication::notifyInternal2 (receiver=0x5623930a2130, event=event@entry=0x7ffcf1848bb0) at ../../include/QtCore/5.11.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307 | 0x7f180b4a8ba8 in QCoreApplication::sendEvent (event=0x7ffcf1848bb0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 | 0x7f180b4a8ba8 in QTimerInfoList::activateTimers (this=0x562392954560) at kernel/qtimerinfo_unix.cpp:643 | 0x7f180b4a943c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 | 0x7f180b4a943c in idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:229 #18 0x7fe16760bba8 QTimerInfoList::activateTimers() | 0x7f180b4a8ba8 in QTimerInfoList::activateTimers (this=0x562392954560) at kernel/qtimerinfo_unix.cpp:643 #19 0x7fe16760c404 | 0x7f180b4a9404 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #20 0x7fe166ab9f2e g_main_context_dispatch | 0x7f180a956f2e in g_main_dispatch (context=0x7f17f8004ff0) at ../../../glib/gmain.c:3182 | 0x7f180a956f2e in g_main_context_dispatch (context=context@entry=0x7f17f8004ff0) at ../../../glib/gmain.c:3847 #21 0x7fe166aba1c8 | 0x7f180a9571c8 in g_main_context_iterate
Bug#946433: marked as done (python3-jpylyzer: missing Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1))
Your message dated Mon, 09 Dec 2019 22:21:48 + with message-id and subject line Bug#946433: fixed in jpylyzer 1.18.0-3.2 has caused the Debian Bug report #946433, regarding python3-jpylyzer: missing Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1) 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.) -- 946433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-jpylyzer Version: 1.18.0-3.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-jpylyzer_1.18.0-3.1_all.deb ... Unpacking python3-jpylyzer (1.18.0-3.1) ... dpkg: error processing archive /var/cache/apt/archives/python3-jpylyzer_1.18.0-3.1_all.deb (--unpack): trying to overwrite '/usr/bin/jpylyzer', which is also in package python-jpylyzer 1.18.0-3 Errors were encountered while processing: /var/cache/apt/archives/python3-jpylyzer_1.18.0-3.1_all.deb cheers, Andreas python-jpylyzer=1.18.0-3_python3-jpylyzer=1.18.0-3.1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: jpylyzer Source-Version: 1.18.0-3.2 We believe that the bug you reported is fixed in the latest version of jpylyzer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated jpylyzer 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, 09 Dec 2019 16:30:35 -0500 Source: jpylyzer Architecture: source Version: 1.18.0-3.2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 946433 Changes: jpylyzer (1.18.0-3.2) unstable; urgency=medium . * Non-maintainer upload. * Add Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1); Closes: #946433 Checksums-Sha1: 4962c1da3b5cbb992805e0e74d90455a45f618bf 2120 jpylyzer_1.18.0-3.2.dsc e4878b2f72ba504cc5945f479076a4dd7c686156 4040 jpylyzer_1.18.0-3.2.debian.tar.xz 667174dbd835b762eba6f0788e784ed3f71ebf46 8456 jpylyzer_1.18.0-3.2_source.buildinfo Checksums-Sha256: 05b640abe902f42d8ae11e5cab87415ad66c635231ad77de37aa56eed01e0187 2120 jpylyzer_1.18.0-3.2.dsc 8be25ff5b272ee525a71739d16a4c482573ab6ace0c56c53c32cd69f7eed2ebf 4040 jpylyzer_1.18.0-3.2.debian.tar.xz c0068efc059ae3b5bf33a0d19d7da78ee56d9670ee94db715abf29224291017a 8456 jpylyzer_1.18.0-3.2_source.buildinfo Files: 1bed36389f6c0969859f69ba4001341e 2120 python optional jpylyzer_1.18.0-3.2.dsc 51542d037dfc9c1b4a7a31032bd58116 4040 python optional jpylyzer_1.18.0-3.2.debian.tar.xz 7d8648c50961120b66479ec8ff34524a 8456 python optional jpylyzer_1.18.0-3.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3uvUQACgkQh588mTgB qU8LmhAAhyU75i8CzwbBTUREtGB/aQfsFc8zWUFDSwCPDnbRglBYVcz+TjPluMLE 1bToJd8GHqPTC0CzR6mUgmvRq8A2pxEDDGCgfj30gQlo/cL+ELcPcXPbJnSMaBd4 qeXiOrIZgSil6kEe0PXpCqlu2017h6SvQWOC5+eEyPJUXHAT2WveXzxU44ySh6zH EbjcWtGHOPL2O0UlcymGojdZ2H3rQD04x3QymXWvmSEXI/xOtQinfKAFxfA9RO30 g5HXGA5MEtlUffizdZCqpuYhvjszk3Hen3BVc6F8RCTUwchK/hhBQE5UvoE75fAk dQllf9SV5x74EoWNSHZOrXd0vRyrq41IJTUe00ry89GJgGzCk2+dtOo5IOG1yQ3t kJc7xRv5d+WQa1RUx/aLEdgGP3zjlZ9nncqPbzRlkfIEBMo8Jw3CQTb241/McdMJ ZVV+zE62ItIJ17OKLylokPIMEqV9Bl/5AatOJQFqEjDvy0hOze3gaMsBWTvRJJOg 22Ym7jXsD4uEC1ev2JmSfctBd9S+R1CYteUDjAik0akI7ZB+5CWHFzOjqSwmoWq0 5PFMUgj5O6ULmfhwZ1I35bOO3oeQznS21d3fhFauw2HaFP2qO3PYFiUGxqTBlWQO 7/+4I+650eSLX8xO3JbNswOAQ56ft9dSji0eAdE4sJzfo5fMtaY= =ddaY -END PGP SIGNATURE End Message ---
Bug#946484: internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found
On 2019-12-09 22:51:16, Jakub Wilk wrote: > Package: internetarchive > Version: 1.8.5-1 > Severity: grave > > The ia command doesn't work at all: > >$ ia help >Traceback (most recent call last): > File "/usr/bin/ia", line 6, in >from pkg_resources import load_entry_point > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > 3250, in >@_call_aside > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > 3234, in _call_aside >f(*args, **kwargs) > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > 3263, in _initialize_master_working_set >working_set = WorkingSet._build_master() > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > 583, in _build_master >ws.require(__requires__) > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > 900, in require >needed = self.resolve(parse_requirements(requirements)) > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > 786, in resolve >raise DistributionNotFound(req, requirers) >pkg_resources.DistributionNotFound: The 'backports.csv' distribution was > not found and is required by internetarchive This is strange. The requirements seem to be wrong: 'backports.csv < 1.07;python_version<"2.7"', 'backports.csv < 1.07;python_version<"3.4"', 'backports.csv;python_version>="2.7"', 'backports.csv;python_version>="3.4"', the latter two lines say we need the backport in python 3.4 and above, which is non-sensical: we *don't* need the backport then... I'll see what i can do. a. -- It will be a great day when our schools get all the money they need and the air force has to hold a bake sale to buy a bomber. - Unknown
Bug#946484: internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found
Package: internetarchive Version: 1.8.5-1 Severity: grave The ia command doesn't work at all: $ ia help Traceback (most recent call last): File "/usr/bin/ia", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3250, in @_call_aside File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3234, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in _build_master ws.require(__requires__) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'backports.csv' distribution was not found and is required by internetarchive -- System Information: Architecture: i386 Versions of packages internetarchive depends on: ii python3 3.7.5-3 ii python3-internetarchive 1.8.5-1 -- Jakub Wilk
Processed: jpylyzer: diff for NMU version 1.18.0-3.2
Processing control commands: > tags 946433 + patch Bug #946433 [python3-jpylyzer] python3-jpylyzer: missing Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1) Added tag(s) patch. -- 946433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946433: jpylyzer: diff for NMU version 1.18.0-3.2
Control: tags 946433 + patch
Dear maintainer,
I've prepared an NMU for jpylyzer (versioned as 1.18.0-3.2). The diff
is attached to this message.
Regards.
diff -Nru jpylyzer-1.18.0/debian/changelog jpylyzer-1.18.0/debian/changelog
--- jpylyzer-1.18.0/debian/changelog 2019-11-29 00:30:33.0 -0500
+++ jpylyzer-1.18.0/debian/changelog 2019-12-09 16:30:35.0 -0500
@@ -1,3 +1,10 @@
+jpylyzer (1.18.0-3.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1); Closes: #946433
+
+ -- Sandro Tosi Mon, 09 Dec 2019 16:30:35 -0500
+
jpylyzer (1.18.0-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru jpylyzer-1.18.0/debian/control jpylyzer-1.18.0/debian/control
--- jpylyzer-1.18.0/debian/control 2019-11-29 00:27:15.0 -0500
+++ jpylyzer-1.18.0/debian/control 2019-12-09 16:30:03.0 -0500
@@ -31,6 +31,8 @@
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends}
Suggests: pirl-image-tools
+Breaks: python-jpylyzer (<< 1.18.0-3.1)
+Replaces: python-jpylyzer (<< 1.18.0-3.1)
Description: JP2 (JPEG 2000 Part 1) validator and properties extractor
Validator and feature extractor for JP2 (JPEG 2000 Part 1 - ISO/IEC 15444-1)
images. Jpylyzer was specifically created to check that a JP2 file really
Bug#946347: Thunderbird: After dist-upgrade thunderbird thinks it is too old.
Control: severity -1 normal Hello Robert, On Sat, Dec 07, 2019 at 05:25:22PM +0100, Robert Pommrich wrote: > After a dist-upgrade from stretch to buster with thunderbird installed > in version 68.2.2-1~deb9u1 and being upgraded to version > 68.2.2-1~deb10u1 thunderbird shows a message at the start: > > "A newer version of Thunderbird may have made changes to your profile which > are no longer > compatible with this older version. > Use this profile only with that newer version, or create a new profile for > this installation of > Thunderbird. Creating a new profile requires setting up your accounts, > calendars and add-ond again." > > This is strange and should not happen, as the version of Thunderbird > is practically the same. this usaly happen if users have used some pre-built version from Mozilla. Seeing this message isn't something you can blame the Thunderbird package from Debian as you have used non packaged software on your own. https://support.mozilla.org/en-US/kb/unable-launch-older-version-profile Please adjust your local profile settings by reading the ressource I've linked above. Regards Carsten
Processed: Re: Bug#946347: Thunderbird: After dist-upgrade thunderbird thinks it is too old.
Processing control commands: > severity -1 normal Bug #946347 [thunderbird] Thunderbird: After dist-upgrade thunderbird thinks it is too old. Severity set to 'normal' from 'grave' -- 946347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944742: marked as done (assimp: testsuite regression)
Your message dated Mon, 09 Dec 2019 20:48:26 + with message-id and subject line Bug#944742: fixed in assimp 5.0.0~ds2-3 has caused the Debian Bug report #944742, regarding assimp: testsuite regression 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.) -- 944742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: assimp Version: 5.0.0~ds2-1 Severity: serious Hello, looks like the autopkgtest is failing... Can you please have a look? https://ci.debian.net/packages/a/assimp/ [3 4 5] [3 5 6]]bash: line 1: 1849 Segmentation fault /tmp/autopkgtest-lxc.niblnjc6/downtmp/build.0PA/src/debian/tests/quicktest.py 2> >(tee -a /tmp/autopkgtest-lxc.niblnjc6/downtmp/quicktest.py-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.niblnjc6/downtmp/quicktest.py-stdout) Looks like it regressed some time ago, and now this should be considered RC buggy according to policy thanks for having a look G. --- End Message --- --- Begin Message --- Source: assimp Source-Version: 5.0.0~ds2-3 We believe that the bug you reported is fixed in the latest version of assimp, 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. IOhannes m zmölnig (Debian/GNU) (supplier of updated assimp 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, 09 Dec 2019 21:03:46 +0100 Source: assimp Architecture: source Version: 5.0.0~ds2-3 Distribution: unstable Urgency: medium Maintainer: IOhannes m zmölnig (Debian/GNU) Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 944742 Changes: assimp (5.0.0~ds2-3) unstable; urgency=medium . * PyAssimp fixes * Add patch to handle faces with variable number of vertices in PyAssimp (Closes: #944742) * Update patch to fix struct-definition after discovering another problem * PyAssimp autopkgtest * Add many more file-extensions to the pyassimp autopkgtest * Add nicer error messages * Gracefully handle exceptions that are not AssimpErrors * Declare "assimp-testmodels" package as "multi-arch: foreign" Checksums-Sha1: f2590da8ad9e6be78763614e3e8fbd8a0a7d1d9a 2493 assimp_5.0.0~ds2-3.dsc 943ef6e35d4814d47cecaae6b7e23dc71bb0a965 26600 assimp_5.0.0~ds2-3.debian.tar.xz Checksums-Sha256: 518b72f7b2171aaabe9cae64e36df3865cb7de82952eb29fd558a5409ced4bb9 2493 assimp_5.0.0~ds2-3.dsc 45f19c882ec21474cc40ac4f12cd41e9ff5d94b754982c82cf5bcca451d07b5f 26600 assimp_5.0.0~ds2-3.debian.tar.xz Files: ede71dd2ce1db68aa80e7b6ce472c83d 2493 graphics optional assimp_5.0.0~ds2-3.dsc d543d42e24947a43344fd617e8638452 26600 graphics optional assimp_5.0.0~ds2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl3urfQWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+OsyD/9E3E9dJAUfNOTJH10lBSAWPlvw f3AhAjqCt8B7INum2MTnM9ExfW83V4SRCY/FW7lUw+Rc2FS6cTOXqrUpOTo6FE01 V2pj5mZ21hGTL1HrV41JY0OTc9j7uVCVaTJl1AUbRBgJzbStKK0DO7HbhanAMr4T LinMjjC0ZBHzo137E9z1G27W9Ta00z7qU/L6Op3WVOxVyBX8qURhxwAygorH/5Ni LQj8IyNFynzbweGRTCUGfM/pHrZetEx6LBResgR39jay8zNSTj49NQXUJhcj252c 7N5aTRo5mJ7j9oV5JjcmbKaut5ZhhQOxp1lUrNMi1LnmRqXZDnT8QdA0HL+hmcxi L1FhVRmHE2rzI4PLDXJjLecUZ2xtQrnfw+smIsJJ00pc972JNAhsJzU3PuiY6F3B 8WqgBy4wgaeS7jbBs+dSlZigrKNyUAwL2c/n/TDYz9atY+SmGCJWGO2RGzCNwYZr NYyob/KQ360AhQsM9XGfxo/6OcVPfQjzg42h+eTcr2C2PtN5FMKgaXsJRWuLIIx4 r94ydDrkmkWicSt+BeU65ZLaOGLwvlLcClVk6Ytk6ruw6drvMSq3b/uJzsZ7waF7 RZoB5uey1vYIS33NTClYEyV2iBOr+7+Rd40IR1eBpTMGceyAddHYLRARHHtUI/oV Tar5s8RvSgLNpymvEg== =SWNi -END PGP SIGNATURE End Message ---
Bug#946415: [Pkg-rust-maintainers] Bug#946415: rust-cargo Build-Depends on librust-crates-io-0.25+default-dev which doesn't exist
Paul, I do find this bugs valuable on my side. Thanks for filling them! Sylvestre Le 09/12/2019 à 00:30, Ximin Luo a écrit : Hi, This type of bug is a natural artifact of the way rust crates are structured and updated, and the Rust team is continually aware of these types of bugs. There is no need to file these types of bugs for packages in unstable as the testing migration script will prevent migrations anyway, rendering a RC bug report unbeneficial and contributing to more paperwork for the packaging team. Best, Ximin Paul Gevers: Source: rust-cargo Version: 0.37.0-1 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs Dear maintainers, Your package Build-Depends on librust-crates-io-0.25+default-dev but that package doesn't exist. Paul -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#945453: marked as done (camitk: FTBFS, uninstallable build-deps in unstable)
Your message dated Mon, 09 Dec 2019 20:43:02 +0100 with message-id <6fa2fefa7bfae02457636d4fe8c6f7a10d24f631.ca...@gmail.com> and subject line Re: camitk: FTBFS, uninstallable build-deps in unstable has caused the Debian Bug report #945453, regarding camitk: FTBFS, uninstallable build-deps in unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: camitk Version: 4.1.2-3 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Dear maintainers, The camitk package is not buildable in unstable because it build-depends on libgdcm2-dev and libvtkgdcm2-dev, which have been superseded by libgdcm-dev and libvtkgdcm-dev. After updating the build-dependencies, camitk still fails to build with an error: [...] Determining if the CXX compiler accepts the flag -fPIC passed with the following output: Change Dir: /<>/camitk-build/CMakeFiles/CMakeTmp Run Build Command(s):/usr/bin/make cmTC_14e9e/fast && make[2]: Entering directory '/<>/camitk-build/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_14e9e.dir/build.make CMakeFiles/cmTC_14e9e.dir/build make[3]: Entering directory '/<>/camitk-build/CMakeFiles/CMakeTmp' Building CXX object CMakeFiles/cmTC_14e9e.dir/DummyCXXFile.cxx.o /usr/bin/c++-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/cmTC_14e9e.dir/DummyCXXFile.cxx.o -c /usr/share/cmake-3.15/Modules/DummyCXXFile.cxx Linking CXX executable cmTC_14e9e /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_14e9e.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -rdynamic CMakeFiles/cmTC_14e9e.dir/DummyCXXFile.cxx.o -o cmTC_14e9e make[3]: Leaving directory '/<>/camitk-build/CMakeFiles/CMakeTmp' dh_auto_configure: cd camitk-build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_SKIP_RPATH:BOOL=TRUE -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=FALSE -DCMAKE_BUILD_TYPE:STRING=None -DCEP_IMAGING:BOOL=TRUE -DCEP_MODELING:BOOL=TRUE -DCEP_TUTORIALS:BOOL=TRUE -DAPIDOC_SDK:BOOL=TRUE .. returned exit code 1 make[1]: *** [debian/rules:66: override_dh_auto_configure] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:63: build] Error 2 (https://launchpad.net/ubuntu/+source/camitk/4.1.2-3ubuntu1/+build/18156646) The build system output here is fairly inscrutable, I'm not clear on what is actually failing. In any case, camitk has been removed from testing at some point, allowing the new opencv + gdcm to transition there, but somehow this never resulted in an RC bug filed against camitk. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 4.13.2-dfsg1-6 The latest version of insighttoolkit4-dev pulls in the right dependencies. best, Gert --- End Message ---
Bug#946470: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 09/12/2019 18.37, Rene Engelhard wrote: > Either asap or next week when rc1 will be there (but either way will be NEW > given the previous versions > are still waiting in NEW since mid-November...) No need to hurry ... as long as it is fixed once these packages go to sid. Andreas
Bug#946415: rust-cargo Build-Depends on librust-crates-io-0.25+default-dev which doesn't exist
Hi Ximin, On 09-12-2019 00:30, Ximin Luo wrote: > This type of bug is a natural artifact of the way rust crates are structured and updated, and the Rust team is continually aware of these types of bugs. There is no need to file these types of bugs for packages in unstable as the testing migration script will prevent migrations anyway, rendering a RC bug report unbeneficial and contributing to more paperwork for the packaging team. I'm member of the release team. Can you please elaborate how this is supposed to work, because rust is/was involved in several transitions that I'd like to finish. Because I know rust is "weird", I was holding off reporting this for quite some time, but in this case I am missing progress. It's unclear to me how this is supposed to work. Also, are you saying that the packages would build fine if rebuild in testing? Is this package "provided" by some other package. Is there better tooling available than inspecting the Binaries file on a mirror? Paul
Bug#945322: marked as done (ruby-maxitest: uninstallable in sid: Depends: ruby-minitest (< 5.12.0) but 5.13.0-1 is to be installed)
Your message dated Mon, 09 Dec 2019 19:06:23 + with message-id and subject line Bug#945322: fixed in ruby-maxitest 3.6.0-1 has caused the Debian Bug report #945322, regarding ruby-maxitest: uninstallable in sid: Depends: ruby-minitest (< 5.12.0) but 5.13.0-1 is to be installed 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.) -- 945322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-maxitest Version: 3.1.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: ruby-maxitest : Depends: ruby-minitest (< 5.12.0) but 5.13.0-1 is to be installed Cheers, Andreas --- End Message --- --- Begin Message --- Source: ruby-maxitest Source-Version: 3.6.0-1 We believe that the bug you reported is fixed in the latest version of ruby-maxitest, 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. Lucas Kanashiro (supplier of updated ruby-maxitest 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, 09 Dec 2019 15:37:04 -0300 Source: ruby-maxitest Architecture: source Version: 3.6.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Lucas Kanashiro Closes: 945322 Changes: ruby-maxitest (3.6.0-1) unstable; urgency=medium . * Team upload. * New upstream version 3.6.0 * d/control: update version constraint of ruby-minitest dependency (Closes: #945322) * Declare compliance with Debian Policy 4.4.1 * Update upstream copyright Checksums-Sha1: 6a2b059617fc19d3539ed6a0d3b72410eb61cdeb 2108 ruby-maxitest_3.6.0-1.dsc c45525935bebdb05a92c2064677802362374044a 10147 ruby-maxitest_3.6.0.orig.tar.gz 3c3ae52bb9f6143f3173430745e2f970b9cc139b 2412 ruby-maxitest_3.6.0-1.debian.tar.xz Checksums-Sha256: cc55ba808bac73e9a0d4905313daf0ca9f46197cf52d19a236fe4e21d0200111 2108 ruby-maxitest_3.6.0-1.dsc 629b42d4d17e6b50edbfa7f2b322235fac60d1a9e6e90416530fe6991c3abd2c 10147 ruby-maxitest_3.6.0.orig.tar.gz 623c08c6b73858af3ba0ec54482032ab8cc9ff2e40c99a8bc88e654e62383dbc 2412 ruby-maxitest_3.6.0-1.debian.tar.xz Files: 623238181dc985e780031e4d9884fa5d 2108 ruby optional ruby-maxitest_3.6.0-1.dsc b01e6b8059bcf88a1aff0d4097742668 10147 ruby optional ruby-maxitest_3.6.0.orig.tar.gz 6f41fad62fdf96353365cb6cb37181dd 2412 ruby optional ruby-maxitest_3.6.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJSBAEBCAA8FiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl3ul9geHGx1Y2FzLmth bmFzaGlyb0BjYW5vbmljYWwuY29tAAoJEPgjonKYg8l8T6cQAJ8RImHEqIgSvUAg Q3ud/OnkIEVynqJy4p00h4KGeOFzU7Ytx+9sFiByUUJEmaQMkbhWcCYH6hFeMbHr xdOoI/iJ/qWEc+fDZIRYxHYWi/gKub0PrT8uy2vovmCgLkvtRKgsGQ13s4DkgSFO /M68VfE+D69oXDnRnce8UzsDSY9szYxe2oMWf+qux942y9NJDFkuZ9ps7IWn4V5s GEx+90TftnYvGDAyQxQNko3qnjvQo2ABKf+8wNnx6hnrIyGLZmOuPtVLpIvitpwJ cnyUMtRRq6MJI/FoOi74fClluT+wdZgyDUE6QHRoJvUOgkws8DiPASskGdYzhBfJ DRt7EN2nCqHIfv60ZHtGCw1iA77hA47DzpQTrhG6iFMwKZZJKsB2+54vSTenGUhM sqk4Js1x898a8txJeP719ma4TgQmWxHRg1lq1/EMJlPiUr0THx8wBoKjQxOpHGLJ Kfh9gVLiA8ihpyg5rZGXlryEJvjpA4pl/MmKTqqbTLdxPj+YWabbkpnygQbSiwMX rKFSADVd13lSjApWFnNK3xfNH6gikE9JAJWGncYMFcy5+SFtDq77/LchS/isNwAR mMGErjSR/l9E5ruOCe9UkgoIAcsYHpkRTM1isoMR9x0UKkKwq4JK5yv+pUacIekw DsWuK9bwFah3dwYJeQQ48sSxubni =q8If -END PGP SIGNATURE End Message ---
Bug#945489: closed by Sylvestre Ledru (Bug#945489: fixed in llvm-toolchain-9 1:9.0.1~+rc2-1~exp1)
Hello, Le 09/12/2019 à 19:04, Lisandro Damián Nicanor Pérez Meyer a écrit : Hy Sylvestre! On 19/12/07 04:15, Debian Bug Tracking System wrote: [snip] Format: 1.8 Date: Tue, 03 Dec 2019 07:56:16 +0100 Source: llvm-toolchain-9 Architecture: source Version: 1:9.0.1~+rc2-1~exp1 Distribution: experimental Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 945489 Changes: llvm-toolchain-9 (1:9.0.1~+rc2-1~exp1) experimental; urgency=medium . * New snapshot release * Fix some paths, upstream moved from site-packages to dist-packages for python packages * Move yaml-bench from libclang-common-X.Y-dev to llvm-X.Y-tools where it belongs See http://lists.llvm.org/pipermail/llvm-dev/2019-December/137337.html * Add a project in the cmake-test to silent a warning (Closes: #945489) This fix went into experimental and cmake has been stagnant in unstable for more than 20 days already. Is there any chance to get the fix in unstable soon? Should we ask the RT to ignore the failure? Maybe do a NMU? Ignoring looks great. This is just a warning without any impact Cheers S
Processed: 937727
Processing commands for cont...@bugs.debian.org: > reassign 937727 src:python-enable Bug #937727 [ftp.debian.org] RM: python-enable -- RoQA; unmaintained; low popcon; blocking py2 removal; no rdeps Bug reassigned from package 'ftp.debian.org' to 'src:python-enable'. Ignoring request to alter found versions of bug #937727 to the same values previously set Ignoring request to alter fixed versions of bug #937727 to the same values previously set > retitle 937727 python-enable: convert package to Python 3 Bug #937727 [src:python-enable] RM: python-enable -- RoQA; unmaintained; low popcon; blocking py2 removal; no rdeps Changed Bug title to 'python-enable: convert package to Python 3' from 'RM: python-enable -- RoQA; unmaintained; low popcon; blocking py2 removal; no rdeps'. > thanks Stopping processing here. Please contact me if you need assistance. -- 937727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937727: RM python-enable
reassign -1 src:python-enable retitle -1 python-enable: convert package to Python 3 thanks Hi Dmitry, Yes, sorry for the delay but I have finally gotten some time to spend on my Debian packages. Thanks to you and Scott for taking care of traits, traitsui and pyface! I plan to work on enable and chaco and update them to Python 3. Regards, Varun On Mon, Dec 9, 2019 at 2:36 AM Dmitry Shachnev wrote: > Hi Varun! > > On Sun, Dec 08, 2019 at 10:35:51PM -0500, Scott Talbert wrote: > > Control: reassign -1 ftp.debian.org > > Control: retitle -1 RM: python-enable -- RoQA; unmaintained; low popcon; > blocking py2 removal; no rdeps > > I see you started working on python-enable in Git [1]. If you want to > prevent > removal of this package, please reassign this bug back to > src:python-enable. > > But the Python 3 package will have to go through the NEW queue anyway, no > matter if the old package is removed or not. > > [1]: > https://salsa.debian.org/python-team/modules/python-enable/commits/master > > -- > Dmitry Shachnev >
Bug#945489: closed by Sylvestre Ledru (Bug#945489: fixed in llvm-toolchain-9 1:9.0.1~+rc2-1~exp1)
Hy Sylvestre! On 19/12/07 04:15, Debian Bug Tracking System wrote: [snip] > Format: 1.8 > Date: Tue, 03 Dec 2019 07:56:16 +0100 > Source: llvm-toolchain-9 > Architecture: source > Version: 1:9.0.1~+rc2-1~exp1 > Distribution: experimental > Urgency: medium > Maintainer: LLVM Packaging Team > Changed-By: Sylvestre Ledru > Closes: 945489 > Changes: > llvm-toolchain-9 (1:9.0.1~+rc2-1~exp1) experimental; urgency=medium > . >* New snapshot release >* Fix some paths, upstream moved from site-packages > to dist-packages for python packages >* Move yaml-bench from libclang-common-X.Y-dev to llvm-X.Y-tools where > it belongs > See http://lists.llvm.org/pipermail/llvm-dev/2019-December/137337.html >* Add a project in the cmake-test to silent a warning > (Closes: #945489) This fix went into experimental and cmake has been stagnant in unstable for more than 20 days already. Is there any chance to get the fix in unstable soon? Should we ask the RT to ignore the failure? Maybe do a NMU? Thanks, Lisandro.
Bug#946470: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Hi, On Mon, Dec 09, 2019 at 05:20:49PM +0100, Andreas Beckmann wrote: > This bug is present in several libreoffice-l10n-?? packages > and libreoffice-help-common. Maybe also in more packages > depending on these failing ones since they cannot be tested. Nah, that script was just ran on -help-* and -l10n-*. > >From the attached log (scroll to the bottom...): > > 0m25.4s ERROR: FAIL: silently overwrites files via directory symlinks: > /usr/share/doc/libreoffice-l10n-de/changelog.Debian.gz > (libreoffice-l10n-de) != > /usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common) > /usr/share/doc/libreoffice-l10n-de -> libreoffice-common > /usr/share/doc/libreoffice-l10n-de/copyright (libreoffice-l10n-de) != > /usr/share/doc/libreoffice-common/copyright (libreoffice-common) > /usr/share/doc/libreoffice-l10n-de -> libreoffice-common > > 0m24.7s ERROR: FAIL: silently overwrites files via directory symlinks: > /usr/share/doc/libreoffice-help-common/changelog.Debian.gz > (libreoffice-help-common) != > /usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common) > /usr/sare/doc/libreoffice-help-common -> libreoffice-common > /usr/share/doc/libreoffice-help-common/copyright (libreoffice-help-common) > != /usr/share/doc/libreoffice-common/copyright (libreoffice-common) > /usr/share/doc/libreoffice-help-common -> libreoffice-common Hmm, actually this is what was meant with libreoffice (1:6.4.0~beta1-0reprotest1) experimental; urgency=medium * New upstream beta release * debian/rules: - add szl to (LANGPACK)ISOS so that we build a Upper Silesian l10n when languages get enabled again * debian/*.maintscript: fix ^^^ but that only fixed half of the problem, should have used /g (and didn't notice the second part also be broken...) (And that one was because of * debian/rules, debian/control.in, debian/*.maintscript: stop using --link-doc=. a) for -style-* as they cause a circular dependency (closes: #940303) and b) since it doesn't work anymore with the -core-nogui alternative in 1:6.4.0~alpha1-0reprotest1 Will fix and upload. Either asap or next week when rc1 will be there (but either way will be NEW given the previous versions are still waiting in NEW since mid-November...) Regards, Rene
Processed: Bug#946470 marked as pending in libreoffice
Processing control commands: > tag -1 pending Bug #946470 [libreoffice-l10n-de] libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added tag(s) pending. -- 946470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946470: marked as pending in libreoffice
Control: tag -1 pending Hello, Bug #946470 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/commit/e34126ba39c7cff7ea71a578ef4ba242cb9f0083 * debian/*.maintscript: fix again and update version (closes: #946470) (this message was generated automatically) -- Greetings https://bugs.debian.org/946470
Bug#946474: fluidsynth: Incomplete debian/copyright?
Source: fluidsynth Version: 2.0.5-1 Severity: serious Justication: Policy § 12.5 X-Debbugs-CC: Fabian Greffrath , ftpmas...@debian.org Hi, I just ACCEPTed fluidsynth from NEW but noticed it was missing attribution in debian/copyright for at least the Creative Commons documentation... This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#946473: llvm-9-tools: missing Breaks+Replaces: libclang-common-9-dev (<< 1:9.0.1~+rc2)
Package: llvm-9-tools Version: 1:9.0.1~+rc2-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../llvm-9-tools_1%3a9.0.1~+rc2-1~exp1_amd64.deb ... Unpacking llvm-9-tools (1:9.0.1~+rc2-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/llvm-9-tools_1%3a9.0.1~+rc2-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/llvm-9/bin/yaml-bench', which is also in package libclang-common-9-dev 1:9.0.0-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/llvm-9-tools_1%3a9.0.1~+rc2-1~exp1_amd64.deb cheers, Andreas libclang-common-9-dev=1:9.0.0-4_llvm-9-tools=1:9.0.1~+rc2-1~exp1.log.gz Description: application/gzip
Bug#943620: marked as done (gammapy's tests fail with numpy-1.17 and python3.8)
Your message dated Mon, 09 Dec 2019 17:05:32 +
with message-id
and subject line Bug#943620: fixed in gammapy 0.15-1
has caused the Debian Bug report #943620,
regarding gammapy's tests fail with numpy-1.17 and python3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
943620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gammapy
Version: 0.13-1
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8
As discussed by email, gammapy's tests fail with numpy-1.17 and python3.8.
/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py:522:
SystemError
_ test_energy_logspace _
i = 2, stacklevel = 3
def _index_deprecate(i, stacklevel=2):
try:
> i = operator.index(i)
E TypeError: 'numpy.float64' object cannot be interpreted as an
integer
/usr/lib/python3/dist-packages/numpy/core/function_base.py:22: TypeError
During handling of the above exception, another exception occurred:
def test_energy_logspace():
energy = energy_logspace(emin="0.1 TeV", emax="10 TeV", nbins=3)
assert energy.unit == "TeV"
assert_allclose(energy.value, [0.1, 1, 10])
energy = energy_logspace(emin=0.1, emax=10, nbins=3, unit="TeV")
assert energy.unit == "TeV"
assert_allclose(energy.value, [0.1, 1, 10])
> energy = energy_logspace(emin="0.1 TeV", emax="10 TeV", nbins=1,
per_decade=True)
gammapy/utils/tests/test_energy.py:16:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
gammapy/utils/energy.py:36: in energy_logspace
energy = np.logspace(x_min, x_max, nbins)
<__array_function__ internals>:5: in logspace
???
/usr/lib/python3/dist-packages/numpy/core/function_base.py:277: in logspace
y = linspace(start, stop, num=num, endpoint=endpoint, axis=axis)
<__array_function__ internals>:5: in linspace
???
/usr/lib/python3/dist-packages/numpy/core/function_base.py:128: in linspace
num = _index_deprecate(num)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
i = 2, stacklevel = 3
def _index_deprecate(i, stacklevel=2):
try:
i = operator.index(i)
except TypeError:
msg = ("object of type {} cannot be safely interpreted as "
"an integer.".format(type(i)))
i = int(i)
stacklevel += 1
> warnings.warn(msg, DeprecationWarning, stacklevel=stacklevel)
E DeprecationWarning: object of type cannot be
safely interpreted as an integer.
/usr/lib/python3/dist-packages/numpy/core/function_base.py:28:
DeprecationWarning
= 14 failed, 964 passed, 493 skipped in 86.80 seconds ==
--- End Message ---
--- Begin Message ---
Source: gammapy
Source-Version: 0.15-1
We believe that the bug you reported is fixed in the latest version of
gammapy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated gammapy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 09 Dec 2019 17:33:45 +0100
Source: gammapy
Architecture: source
Version: 0.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team
Changed-By: Ole Streicher
Closes: 943620
Changes:
gammapy (0.15-1) unstable; urgency=medium
.
* Update auto_test to use pytest
* Push Standards-Version to 4.4.1. No changes required.
* Remove d/compat
* New upstream version 0.15. Rediff patches (Closes: #943620)
* Fix setuptools_scm version number
* Update build dependencies
* Initialize __version__ with None if version info is unavailable
* Don't install gammapy binary
Checksums-Sha1:
8182ac812e2edff3ac5ba75486b3fbe6c1de2318 2521 gammapy_0.15-1.dsc
37130f6f78854053d27f6ea99f9136b6aba2203d 2047444 gammapy_0.15.orig.tar.gz
752f0dcb054d171af8068e92010c18e2e4b4cbf6 5764 gammapy_0.15-1.debian.tar.xz
Checksums-Sha256:
Processed: affects 942469
Processing commands for cont...@bugs.debian.org: > affects 942469 + r-cran-tidyverse Bug #942469 [r-cran-rmarkdown] r-cran-rmarkdown: directory to symlink conversion not correctly handled on upgrade Added indication that 942469 affects r-cran-tidyverse > thanks Stopping processing here. Please contact me if you need assistance. -- 942469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946223: marked as done ([NMU] FTFBS with CGAL 5.0)
Your message dated Mon, 09 Dec 2019 16:35:31 +
with message-id
and subject line Bug#946223: fixed in yade 2019.12~git~0~e74819ea-1
has caused the Debian Bug report #946223,
regarding [NMU] FTFBS with CGAL 5.0
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.)
--
946223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yade
Version: 2019.01a-3
Severity: serious
Tags: ftbfs
Control: block 944417 by -1
Hi,
the transition to CGAL 5.0 started (see bug #944417) and your package FTBFS.
Attached are two patches that fix the problem. In addition, one needs to add
"Build-Depends: libcgal-dev (>= 5.0~).
Just applying these two patches is not enough due to bug #938859. What is your
planned timeline for an upload to unstable?
Best regards,
Joachim
-- System Information:
Debian Release: 10.2
APT prefers stable-debug
APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'),
(700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Index: yade-2019.01a/CMakeLists.txt
===
--- yade-2019.01a.orig/CMakeLists.txt
+++ yade-2019.01a/CMakeLists.txt
@@ -299,7 +299,7 @@ IF(ENABLE_CGAL)
FILE(GLOB CGAL_SRC_LIB "lib/triangulation/*.cpp")
SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${CGAL_DEFINITIONS} -DYADE_CGAL")
-SET(LINKLIBS
"${LINKLIBS};${CGAL_LIBRARIES};${GMP_LIBRARIES};${GMPXX_LIBRARIES};")
+SET(LINKLIBS "${LINKLIBS};${GMP_LIBRARIES};${GMPXX_LIBRARIES};")
MESSAGE(STATUS "Found CGAL")
SET(CONFIGURED_FEATS "${CONFIGURED_FEATS} CGAL")
Index: yade-2019.01a/cMake/FindCGAL.cmake
===
--- yade-2019.01a.orig/cMake/FindCGAL.cmake
+++ yade-2019.01a/cMake/FindCGAL.cmake
@@ -7,38 +7,26 @@
# This module defines
# CGAL_DEFINITIONS: compiler flags for compiling with CGAL
# CGAL_INCLUDE_DIR: where to find CGAL.h
-# CGAL_LIBRARIES: the libraries needed to use CGAL
# CGAL_FOUND: if false, do not try to use CGAL
-IF(CGAL_INCLUDE_DIR AND CGAL_LIBRARIES)
+IF(CGAL_INCLUDE_DIR)
SET(CGAL_FOUND TRUE)
-ELSE(CGAL_INCLUDE_DIR AND CGAL_LIBRARIES)
+ELSE(CGAL_INCLUDE_DIR)
FIND_PATH(CGAL_INCLUDE_DIR CGAL/basic.h
/usr/include/
/usr/local/include/
$ENV{ProgramFiles}/CGAL/*/include/
$ENV{SystemDrive}/CGAL/*/include/
)
-FIND_LIBRARY(CGAL_LIBRARIES NAMES CGAL libCGAL
-PATHS
-/usr/lib
-/usr/local/lib
-/usr/lib/CGAL
-/usr/lib64
-/usr/local/lib64
-/usr/lib64/CGAL
-$ENV{ProgramFiles}/CGAL/*/lib/ms
-$ENV{SystemDrive}/CGAL/*/lib/ms
-)
-IF(CGAL_INCLUDE_DIR AND CGAL_LIBRARIES)
+IF(CGAL_INCLUDE_DIR)
SET(CGAL_FOUND TRUE)
-MESSAGE(STATUS "Found CGAL: ${CGAL_INCLUDE_DIR}, ${CGAL_LIBRARIES}")
+MESSAGE(STATUS "Found CGAL: ${CGAL_INCLUDE_DIR}")
INCLUDE_DIRECTORIES(${CGAL_INCLUDE_DIR})
-ELSE(CGAL_INCLUDE_DIR AND CGAL_LIBRARIES)
+ELSE(CGAL_INCLUDE_DIR)
SET(CGAL_FOUND FALSE)
MESSAGE(STATUS "CGAL not found.")
-ENDIF(CGAL_INCLUDE_DIR AND CGAL_LIBRARIES)
+ENDIF(CGAL_INCLUDE_DIR)
-MARK_AS_ADVANCED(CGAL_INCLUDE_DIR CGAL_LIBRARIES)
-ENDIF(CGAL_INCLUDE_DIR AND CGAL_LIBRARIES)
+MARK_AS_ADVANCED(CGAL_INCLUDE_DIR)
+ENDIF(CGAL_INCLUDE_DIR)
Index: yade-2019.01a/CMakeLists.txt
===
--- yade-2019.01a.orig/CMakeLists.txt
+++ yade-2019.01a/CMakeLists.txt
@@ -32,6 +32,8 @@
project(Yade C CXX)
cmake_minimum_required(VERSION 2.8.11)
+set(CMAKE_CXX_STANDARD 14)
+
set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/cMake")
INCLUDE(FindPythonInterp)
@@ -83,7 +85,7 @@ ELSE()
ENDIF()
ENDIF()
-SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC -O2 --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall -std=c++11")
+SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC -O2 --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall -std=c++14")
IF (DEBUG)
SET(CMAKE_VERBOSE_MAKEFILE 1)
--- End Message ---
--- Begin Message ---
Source: yade
Source-Version:
Bug#946470: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libreoffice-l10n-de Version: 1:6.4.0~beta1-0reprotest1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libreoffice-l10n-ja libreoffice-l10n-he libreoffice-l10n-in libreoffice-l10n-za libreoffice-help-common Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: sid -> experimental For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. This bug is present in several libreoffice-l10n-?? packages and libreoffice-help-common. Maybe also in more packages depending on these failing ones since they cannot be tested. >From the attached log (scroll to the bottom...): 0m25.4s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libreoffice-l10n-de/changelog.Debian.gz (libreoffice-l10n-de) != /usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common) /usr/share/doc/libreoffice-l10n-de -> libreoffice-common /usr/share/doc/libreoffice-l10n-de/copyright (libreoffice-l10n-de) != /usr/share/doc/libreoffice-common/copyright (libreoffice-common) /usr/share/doc/libreoffice-l10n-de -> libreoffice-common 0m24.7s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libreoffice-help-common/changelog.Debian.gz (libreoffice-help-common) != /usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common) /usr/share/doc/libreoffice-help-common -> libreoffice-common /usr/share/doc/libreoffice-help-common/copyright (libreoffice-help-common) != /usr/share/doc/libreoffice-common/copyright (libreoffice-common) /usr/share/doc/libreoffice-help-common -> libreoffice-common cheers, Andreas libreoffice-l10n-de_1:6.4.0~beta1-0reprotest1.log.gz Description: application/gzip
Processed: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Processing control commands: > affects -1 + libreoffice-l10n-ja libreoffice-l10n-he libreoffice-l10n-in > libreoffice-l10n-za libreoffice-help-common Bug #946470 [libreoffice-l10n-de] libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added indication that 946470 affects libreoffice-l10n-ja, libreoffice-l10n-he, libreoffice-l10n-in, libreoffice-l10n-za, and libreoffice-help-common -- 946470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946436: marked as done (libplplot-data: missing Breaks+Replaces: libplplot17 (<< 5.15.0+dfsg-8))
Your message dated Mon, 09 Dec 2019 15:37:41 + with message-id and subject line Bug#946436: fixed in plplot 5.15.0+dfsg-9 has caused the Debian Bug report #946436, regarding libplplot-data: missing Breaks+Replaces: libplplot17 (<< 5.15.0+dfsg-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.) -- 946436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libplplot-data Version: 5.15.0+dfsg-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libplplot-data_5.15.0+dfsg-8_all.deb ... Unpacking libplplot-data (5.15.0+dfsg-8) ... dpkg: error processing archive /var/cache/apt/archives/libplplot-data_5.15.0+dfsg-8_all.deb (--unpack): trying to overwrite '/usr/share/plplot5.15.0/cglobe.shp', which is also in package libplplot17:amd64 5.15.0+dfsg-7 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libplplot-data_5.15.0+dfsg-8_all.deb cheers, Andreas libplplot17=5.15.0+dfsg-7_libplplot-data=5.15.0+dfsg-8.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: plplot Source-Version: 5.15.0+dfsg-9 We believe that the bug you reported is fixed in the latest version of plplot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissière (supplier of updated plplot 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, 09 Dec 2019 00:18:34 -0300 Source: plplot Architecture: source Version: 5.15.0+dfsg-9 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Rafael Laboissière Closes: 946436 Changes: plplot (5.15.0+dfsg-9) unstable; urgency=medium . * d/control: Add necessary Breaks+Relplaces relationships for libplplot-data. Thanks to Andreas Beckmann, for reporting the bug. (Closes: #946436) Checksums-Sha1: c281cfd97a945f69166f20f9dc8c13ae73335f28 4405 plplot_5.15.0+dfsg-9.dsc a54db36058f63971b1b632388b26bf5cfeb27f45 51400 plplot_5.15.0+dfsg-9.debian.tar.xz 0829e372afcac291cf51a7cffe6aa73efc78acd7 41022 plplot_5.15.0+dfsg-9_amd64.buildinfo Checksums-Sha256: 761f7e3358d4ef9f4a179ddae5a527d122f0cacf30dba30dac8a755988b3307f 4405 plplot_5.15.0+dfsg-9.dsc 128227841934459f7340cb890cff6e1766652d575e899ce6d9eca9b1c768e61d 51400 plplot_5.15.0+dfsg-9.debian.tar.xz 678374e3f0023e3540226f17807e1d4c0da1fce57e1f83325c2230b51a8587fa 41022 plplot_5.15.0+dfsg-9_amd64.buildinfo Files: 41769968f792dec3e14585297ba38951 4405 math optional plplot_5.15.0+dfsg-9.dsc 0cdcede75f9252b585457c1aab7836db 51400 math optional plplot_5.15.0+dfsg-9.debian.tar.xz 748edfd655d8e478ebff66d0ef814723 41022 math optional plplot_5.15.0+dfsg-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAl3uZMkACgkQISSqGYN4 XJDZeBAAhbKgYPs9v4usqEtFguHo8ksI17Om3gEt2gmoi6j4GKHijDwVgVU91Hnf cOc3dMQUlgw4hfLA2VEYX5S2+szGVCwoSV4jjQld4cSPMGGIBFdyGjJ9AYdXnxAd SpTLR976U1YXKBGPQVv3sgoTs+sCQtvkJ6zzH24SgwQzBcwspMFZOQcmyj4MdrMd bnufqhyDHNssjaaYJZ48jQUxSeIKv/U0uJ8E4eovrWoDD3XhGsXX2aR5vhOxL3sz 9yx7gg7P8qUdWTnRwyV75jS7yW79hmXdC6rEo7cvfxMcj4vltdxLPxQYKDM/nMZS SAtamQYSfNb1gxeic/wHzYDfbaqMGbbLBPjPkU9R0y7ZXT2MiHJZGiiCDAJjklBA 7WHvjFvhFCoii0XiLxjV9KowbJlMEPUcXnezjZRfowUhzALuYrKhkbzjqeCnyQhv CUZT3tk0baXczLpnS3spJwWQYpp4Caqv+6PwV0ROxOtSW8ONgjqxdd4nigrdRwQT lJwAo7yW9IjjQfKFEuvA0Qoxahd6QONbg78HpJ9bB6EgVWuZUZpgkSMzHBYQeLWf psQ041MR1mgtQsYjXkS6qK9WewBHbfdwVr7BoZYWC1rWHsSi+WV6uz0y1ueXEIF1 yl6wZi2IoGjzFvvGUGpp0ttBC3f4fEUuvTDFQJivwtBv/MMZmeg= =7Fkw -END PGP
Bug#946465: librust-rand+alloc-dev: does not find upgrade path from buster to bullseye
Package: librust-rand+alloc-dev Version: 0.6.4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. >From the attached log (scroll to the bottom...): Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) librust-rand-core-0.2+alloc-dev:amd64 < 0.2.2-1+b1 @ii mK Ib > Broken librust-rand-core-0.2+alloc-dev:amd64 Depends on librust-rand-core-0.2-dev:amd64 < 0.2.2-1+b1 @ii mR > (= 0.2.2-1+b1) Considering librust-rand-core-0.2-dev:amd64 3 as a solution to librust-rand-core-0.2+alloc-dev:amd64 0 Removing librust-rand-core-0.2+alloc-dev:amd64 rather than change librust-rand-core-0.2-dev:amd64 Investigating (0) librust-rand-core-0.4-dev:amd64 < none -> 0.4.2-1 @un uN Ib > Broken librust-rand-core-0.4-dev:amd64 Breaks on librust-rand-core-dev:amd64 < 0.3.0-1 @ii mK > (< 0.4.3-~~) Considering librust-rand-core-dev:amd64 -1 as a solution to librust-rand-core-0.4-dev:amd64 -1 Holding Back librust-rand-core-0.4-dev:amd64 rather than change librust-rand-core-dev:amd64 Investigating (1) librust-rand-pcg-0.1-dev:amd64 < none -> 0.1.2-1+b1 @un uN Ib > Broken librust-rand-pcg-0.1-dev:amd64 Depends on librust-rand-core-0.4+default-dev:amd64 < none @un H > Considering librust-rand-core-0.4-dev:amd64 -1 as a solution to librust-rand-pcg-0.1-dev:amd64 -1 Holding Back librust-rand-pcg-0.1-dev:amd64 rather than change librust-rand-core-0.4+default-dev:amd64 Investigating (2) librust-rand-dev:amd64 < 0.5.5-2 -> 0.6.4-2 @ii umU Ib > Broken librust-rand-dev:amd64 Depends on librust-rand-pcg-0.1+default-dev:amd64 < none @un H > Considering librust-rand-pcg-0.1-dev:amd64 -1 as a solution to librust-rand-dev:amd64 1 Re-Instated librust-rand-core-0.4-dev:amd64 Re-Instated librust-rand-pcg-0.1-dev:amd64 Re-Instated librust-rand-dev:amd64 Investigating (2) librust-rand-core-0.4-dev:amd64 < none -> 0.4.2-1 @un uN Ib > Broken librust-rand-core-0.4-dev:amd64 Breaks on librust-rand-core-dev:amd64 < 0.3.0-1 @ii mK > (< 0.4.3-~~) Considering librust-rand-core-dev:amd64 -1 as a solution to librust-rand-core-0.4-dev:amd64 -1 Holding Back librust-rand-core-0.4-dev:amd64 rather than change librust-rand-core-dev:amd64 Investigating (3) librust-rand-pcg-0.1-dev:amd64 < none -> 0.1.2-1+b1 @un uN Ib > Broken librust-rand-pcg-0.1-dev:amd64 Depends on librust-rand-core-0.4+default-dev:amd64 < none @un H > Considering librust-rand-core-0.4-dev:amd64 -1 as a solution to librust-rand-pcg-0.1-dev:amd64 -1 Holding Back librust-rand-pcg-0.1-dev:amd64 rather than change librust-rand-core-0.4+default-dev:amd64 Investigating (4) librust-rand-dev:amd64 < 0.5.5-2 -> 0.6.4-2 @ii umU Ib > Broken librust-rand-dev:amd64 Depends on librust-rand-pcg-0.1+default-dev:amd64 < none @un H > Considering librust-rand-pcg-0.1-dev:amd64 -1 as a solution to librust-rand-dev:amd64 1 Removing librust-rand-dev:amd64 rather than change librust-rand-pcg-0.1+default-dev:amd64 Investigating (5) librust-rand+alloc-dev:amd64 < 0.5.5-2 -> 0.6.4-2 @ii pumU Ib > Broken librust-rand+alloc-dev:amd64 Depends on librust-rand-dev:amd64 < 0.5.5-2 | 0.6.4-2 @ii umR > (= 0.6.4-2) Considering librust-rand-dev:amd64 1 as a solution to librust-rand+alloc-dev:amd64 1 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: librust-rand+alloc-dev : Depends: librust-rand-dev (= 0.6.4-2) E: Unable to correct problems, you have held broken packages. Similar errors happen in several other rust packages, too, but this one has the most rdepends. I can't spot immediately how the correct upgrade path should look like, there are too many virtual packages involved. And probably this involves substituting a currently installed package for another one as well. Fixing this (and similar) bug(s) will probably need some Breaks to be added to some packages. cheers, Andreas librust-rand+alloc-dev_0.6.4-2.log.gz Description: application/gzip
Processed: notfound 603757 in 5:77, reassign 946412 to src:janus, tagging 946452
Processing commands for cont...@bugs.debian.org:
> notfound 603757 5:77
Bug #603757 {Done: Aurélien COUDERC } [kde-plasma-desktop]
plasma: Multiple-monitor issues with panel
No longer marked as found in versions meta-kde/5:77.
> reassign 946412 src:janus
Bug #946412 [janus-gateway] janus-gateway: upstream does not support stable
releases
Warning: Unknown package 'janus-gateway'
Bug reassigned from package 'janus-gateway' to 'src:janus'.
No longer marked as found in versions 0.
Ignoring request to alter fixed versions of bug #946412 to the same values
previously set
> tags 946452 + sid bullseye
Bug #946452 [src:mpqc3] mpqc3: FTBFS in sid
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
603757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603757
946412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946412
946452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#944742 marked as pending in assimp
Processing control commands: > tag -1 pending Bug #944742 [src:assimp] assimp: testsuite regression Added tag(s) pending. -- 944742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944742: marked as pending in assimp
Control: tag -1 pending Hello, Bug #944742 in assimp 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/debian/assimp/commit/3d74e9443f1c17e626c49764f9b8cc7ae71e76ac Add patch to handle faces with variable number of vertices in PyAssimp Closes: #944742 (hopefully this time for real) (this message was generated automatically) -- Greetings https://bugs.debian.org/944742
Bug#946448: marked as done (z3: FTBFS: ../src/util/mpz.cpp:57:30: error: definition of ‘uint32_t __builtin_ctz(uint32_t)’ ambiguates built-in declaration ‘int __builtin_ctz(unsigned int)’)
Your message dated Mon, 09 Dec 2019 13:20:11 +
with message-id
and subject line Bug#946448: fixed in z3 4.8.7-2
has caused the Debian Bug report #946448,
regarding z3: FTBFS: ../src/util/mpz.cpp:57:30: error: definition of ‘uint32_t
__builtin_ctz(uint32_t)’ ambiguates built-in declaration ‘int
__builtin_ctz(unsigned int)’
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.)
--
946448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: z3
Version: 4.8.7-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
z3 fails to build on all 32 bit architectures with:
| ../src/util/mpz.cpp:57:30: error: definition of ‘uint32_t
__builtin_ctz(uint32_t)’ ambiguates built-in declaration ‘int
__builtin_ctz(unsigned int)’
|57 | #define _trailing_zeros32(X) __builtin_ctz(X)
| | ^
| ../src/util/mpz.cpp:76:17: note: in expansion of macro ‘_trailing_zeros32’
|76 | inline uint32_t _trailing_zeros32(uint32_t x) {
| | ^
| make[2]: *** [Makefile:188: util/mpz.o] Error 1
See
https://buildd.debian.org/status/fetch.php?pkg=z3=i386=4.8.7-1=1575849231=0
for a full log
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: z3
Source-Version: 4.8.7-2
We believe that the bug you reported is fixed in the latest version of
z3, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabian Wolff (supplier of updated z3 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 09 Dec 2019 13:39:38 +0100
Source: z3
Architecture: source
Version: 4.8.7-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team
Changed-By: Fabian Wolff
Closes: 946448
Changes:
z3 (4.8.7-2) unstable; urgency=medium
.
* Adjust 01-intrinsics.patch to try to fix build failures on many
32-bit architectures (patch tested on i386) (Closes: #946448).
Checksums-Sha1:
5e95354f0e3a281ae576fcce9253d109552c33e0 2677 z3_4.8.7-2.dsc
3787299b145e4b536788a8798442a7fe145879b6 11520 z3_4.8.7-2.debian.tar.xz
8347dce3ff54416d7d97bcfe6032c2fc1a147c25 13532 z3_4.8.7-2_amd64.buildinfo
Checksums-Sha256:
b0cd4debb8296331c325fc3fcc92f8bec84b8d0f1b1259c1f8e50b92d9f3d153 2677
z3_4.8.7-2.dsc
a739192d3a75a2a2719bf3716e9727740cb89bf0a5de3f29d8988e1918f6f4c5 11520
z3_4.8.7-2.debian.tar.xz
be5eba9d436915e53c48ec7ea548d8ce2c309b5a1ff2e32015c03ae81a40065a 13532
z3_4.8.7-2_amd64.buildinfo
Files:
4c6438287a9cb5f3a5440adca054a519 2677 science optional z3_4.8.7-2.dsc
993274150e3ba4997692e0ecde48855f 11520 science optional
z3_4.8.7-2.debian.tar.xz
0a9feba5988db0abe8b88efeaa5f63d0 13532 science optional
z3_4.8.7-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEGKeQdgwAi1CfzfenilOItk1pK0kFAl3uRfMACgkQilOItk1p
K0mQwg//WAICRwwpbWKgndsEMUoT7rkPNMYqEU2t1VAfRxunG/OyrKW9ra9dpd5S
U8sG3v/qWjjdeOkbMbjWE/w8jOrbeEWURdlPhtZ9r2odYaGhARHtDTmNDbMzf5Lj
/sCst4hYNJOHts9qpbD+iltJQzp12hlOG0ucSTff9YCoMiFbiRZDx/y6o8dSzPyu
Z3vkFPgeuMPDdAtNgikBeQ7BUf31NBspX2DxifwkMTE14ClDaEAYf7ArT8zxGozs
3+9NDtXVHuLDVXPZnFgeWlz20dZs/8bIFUwiVSusycpBGD5enByhMXbLtz95jUKV
M5lXSP8nmC2TQxkVpT6jY6V52bupFAM4Nml968mZem06fBEa4Un1kuqCDEVPq4WI
Ck25m4RIoEzVk6V5dF5IvVwB2ScdpNAlT2sizUNxOKxBuZVUaoXJC3FYOCqOWEYh
dRlQnPbuoDgDtCozwLpPOY9Sb5LpMUIgxl9jkeDeZdKztUlj0OwTveLpuUgNGAIm
fnrv4yVgdA8z8KFharD+y1lJEKzCHA8ka4ZpcTjvteGfyiNknMNivys3TD2u4BNG
RwaifLFNZO9UcuFeYaGM+YasfLJIm0si2CaKC+u1eR7pjs0edX+00/ytEKb09MsJ
U5CCXNKmcLYQyk0jmyuv6Dv1sNu/lBIdsMnjgGxEhb4hTwRg7PE=
=5VrY
-END PGP SIGNATURE End Message ---
Bug#946455: marked as done (nomad: FTBFS (missing build-dependency on tzdata))
Your message dated Mon, 09 Dec 2019 12:49:28 + with message-id and subject line Bug#946455: fixed in nomad 0.10.2+dfsg1-2 has caused the Debian Bug report #946455, regarding nomad: FTBFS (missing build-dependency on tzdata) 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.) -- 946455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nomad Version: 0.10.2+dfsg1-1 Severity: serious Tags: ftbfs Dear maintainer: This package fails to build in a minimal chroot including only essential and build-essential packages: [...] --- FAIL: TestPeriodicConfig_ValidTimeZone (0.00s) structs_test.go:2717: Valid tz errored: 1 error occurred: * Invalid time zone "Africa/Abidjan": unknown time zone Africa/Abidjan I believe there is a missing build-dependency on tzdata. Thanks. --- End Message --- --- Begin Message --- Source: nomad Source-Version: 0.10.2+dfsg1-2 We believe that the bug you reported is fixed in the latest version of nomad, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated nomad 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, 09 Dec 2019 23:12:41 +1100 Source: nomad Architecture: source Version: 0.10.2+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Closes: 946455 Changes: nomad (0.10.2+dfsg1-2) unstable; urgency=medium . * Disabled "TestServerWithNodeConn_Path_Newest". * Build-Depends += "tzdata" (Closes: #946455) Thanks, Santiago Vila. * dev: exposed "testutil" as required by "nomad-driver-lxc". Checksums-Sha1: bfa52e65d1204f348abc6b1876df488f577c2f71 7617 nomad_0.10.2+dfsg1-2.dsc 8c56a23ee4d8192f9d81282ed10d0efaf873a190 30840 nomad_0.10.2+dfsg1-2.debian.tar.xz e0abfd444b062097835ee1fb58f2dfc6996b5203 22771 nomad_0.10.2+dfsg1-2_amd64.buildinfo Checksums-Sha256: 33654de424daa08efee0f03c31e1a8b7491a17217fd14b1c13bd322360cea8c8 7617 nomad_0.10.2+dfsg1-2.dsc ef7997a459ac31807c29927dc53287d023fe9881cfd6cb36024d39f2e10a7b91 30840 nomad_0.10.2+dfsg1-2.debian.tar.xz ea69e6f8252542ebd8a66f84d0c655e10cc00b9947f3a76d7496de155208baa8 22771 nomad_0.10.2+dfsg1-2_amd64.buildinfo Files: 99d754ab412d0e96b207e74b5f9ed18e 7617 devel optional nomad_0.10.2+dfsg1-2.dsc 8520eec393322f9aa5caada075f978a3 30840 devel optional nomad_0.10.2+dfsg1-2.debian.tar.xz 0af064618035f0ab5186b2d2186cfd2d 22771 devel optional nomad_0.10.2+dfsg1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAl3uPG8ACgkQUra72VOW jRvMQA/+Jcl3Rd/8RPzWWAA2cIxLUoA414Rt3gjn/zKtaXH3akmdNpZGo3Ulo3WU fPIec4bWJTyHrw/TVLceNw7nc2Z0YCOt0IpoAA1NApiNfQpUHqwMJtNXwRDfStH+ ixW8z7W/V5sIRGX8ps44+GPIYkfKTq9buKeuu3ZvvqZNmmsOJJvaY2Mvka7ULHam wucjy28RK6CMVSp7WljQnNppH4aZJGinKY6Yl5GvXfkMKCSsEsi7lm5zecNoaDv0 ASUGqeTRsrLZvjvr9TmxkbFBo5M5AC3DMWRHyB/GSZtWDgjX8mD7c0PE/fAiCxoA kBztnkaToHgy2gfjIiKNpFNZhFK3osDp+SUnMtWTDubfqevlUhsB+B4WbpGEtWT8 RFhq4vBz7D5+0SZb1dnb7dRs9J7OutAIQppHasmEEnAdANpUTHmSDgdBE7IJkv4+ SZWRWYGIZyk4EW3+gnU8vUgGZ2KOqflFzojcp5EILSqr2/fgtHhZqzqRI3ox3I5b MlK/n8zJ4xM7HBLuYWIrnb/q9xTquos4PLlxxumw5AXqtW+ImT/famOjlOqKJ8Ts Xg+RN/nVzGToxpEI1i4WUcsL/G050/CQtKdTxJ8SkPhnp3kcgeZFaA4gtXVOwk2f Xq0gGcLV/w9c6IFis0+WrIT1luxpZ5Y7nvWKz78pLHg07oz5U6M= =O2HD -END PGP SIGNATURE End Message ---
Bug#946427: marked as done (python3-vcf: missing Breaks+Replaces: python3-pyvcf)
Your message dated Mon, 09 Dec 2019 12:20:14 + with message-id and subject line Bug#946427: fixed in python-pyvcf 0.6.8+git20170215.476169c-5 has caused the Debian Bug report #946427, regarding python3-vcf: missing Breaks+Replaces: python3-pyvcf 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.) -- 946427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-vcf Version: 0.6.8+git20170215.476169c-3 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 without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-vcf_0.6.8+git20170215.476169c-3_amd64.deb ... Unpacking python3-vcf (0.6.8+git20170215.476169c-3) ... dpkg: error processing archive /var/cache/apt/archives/python3-vcf_0.6.8+git20170215.476169c-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/PyVCF-0.6.8.egg-info/PKG-INFO', which is also in package python3-pyvcf 0.6.8+git20170215.476169c-2+b1 Errors were encountered while processing: /var/cache/apt/archives/python3-vcf_0.6.8+git20170215.476169c-3_amd64.deb cheers, Andreas python3-pyvcf=0.6.8+git20170215.476169c-2+b1_python3-vcf=0.6.8+git20170215.476169c-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-pyvcf Source-Version: 0.6.8+git20170215.476169c-5 We believe that the bug you reported is fixed in the latest version of python-pyvcf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-pyvcf 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, 09 Dec 2019 11:12:54 +0100 Source: python-pyvcf Binary: python3-vcf pyvcf python-pyvcf-examples Architecture: source Version: 0.6.8+git20170215.476169c-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: python-pyvcf-examples - Example data for Variant Call Format (VCF) parser for Python python3-vcf - Variant Call Format (VCF) parser for Python 3 pyvcf - helper scripts for Variant Call Format (VCF) parser Closes: 946427 Changes: python-pyvcf (0.6.8+git20170215.476169c-5) unstable; urgency=medium . * Breaks+Replaces: python3-pyvcf Closes: #946427 * Run Build-Time test * Add autopkgtest * Depends: python3-pysam * Fix dependency for pyvcf package Checksums-Sha1: b0edec684f2cf8c214c36e7aa974ea60afa2256d 2396 python-pyvcf_0.6.8+git20170215.476169c-5.dsc 545abbc21fa2809bb771f04041387e87eb061bc8 5200 python-pyvcf_0.6.8+git20170215.476169c-5.debian.tar.xz Checksums-Sha256: dc273421016ef6bb1663545e0bdacd3d22853d41ddb593fe50cdf9b43393 2396 python-pyvcf_0.6.8+git20170215.476169c-5.dsc ae0f6bbc2adc3fbf7a8e9d7927c8ff5a3d2f9e34120a46a1678fd4446f2df55b 5200 python-pyvcf_0.6.8+git20170215.476169c-5.debian.tar.xz Files: eb83ce215167977db3b9b6e5fb0bb919 2396 python optional python-pyvcf_0.6.8+git20170215.476169c-5.dsc 6e0e3024e6001e2a7e177ffa5ed8f7a8 5200 python optional python-pyvcf_0.6.8+git20170215.476169c-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3uN48RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtE1Kw//ZN66YjRv2QS0b/7OA1RIxu9P7yIZrl1Q cHNyUTcI86kWYXqrgFlxxnJ2r7NYa0SzE8ZvwXx36Z0dho8iYBTxBCawV4vsbDAj qhYDa00xBIVNfMRbEJ/dfli/22+5u5jT+KFvy919E+QPsWPFzrYHIsbe7EYXqHEo Eemv4NP590kPio97R4C4+HFHtGWSWoZ476smnbBuNdEQ8GTO8nzFB2rB7uZQhsLN 4K8YuZ+6heCcXXmxK7VCubxPIuMLu+DNDAQBJ5d3L5z11PIUjVbG+Kc/I5JPK6oa M2P99wqiFmcjCslZHM6ELmbeZ8+3WjZZWUfuJ1B9u5YJtD5k04kXEWLIni1PEe8p AXSOsP9VpW3vwMUtZMblrlUeYGCvdJSGSQX7qvSK5J2AUoSCebhuNL9q3NE3tHnW givbkZESXHBDegMl8H0gBrYjnuVgmR5bU4DKxdCs++dHsMaxRmS9RH3y5OCnqbf0
Processed: Bug#946455 marked as pending in nomad
Processing control commands: > tag -1 pending Bug #946455 [src:nomad] nomad: FTBFS (missing build-dependency on tzdata) Added tag(s) pending. -- 946455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946455: marked as pending in nomad
Control: tag -1 pending Hello, Bug #946455 in nomad reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/nomad/commit/b865617c56c9dd203281d82c21a0567106e0469c Build-Depends += "tzdata" (Closes: #946455) Thanks, Santiago Vila. (this message was generated automatically) -- Greetings https://bugs.debian.org/946455
Processed: please stop building python-pytest-xdist now
Processing control commands: > severity -1 serious Bug #937568 [src:pytest-xdist] pytest-xdist: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' -- 937568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945472: python-datrie: FTBFS with recent hypothesis version
On 09.12.19 11:46, Andreas Tille wrote: > Hi, > > I have upgraded python-datrie in Git[1] to latest upstream version > (0.8). It shows the same issue - so I admit I have no better clue than > reporting the issue upstream which I'd rather leave to the official > Uploader of the package. > > BTW, we probably should expect build issues with Python 3.8[2] https://patches.ubuntu.com/p/python-datrie/python-datrie_0.7.1-3ubuntu1.patch didn't forward the hypothesis issues, because Debian didn't update that package for a long time. > Kind regards > > Andreas. > > [1] https://salsa.debian.org/python-team/modules/python-datrie > [2] https://github.com/pytries/datrie/issues/73 >
Bug#945472: python-datrie: FTBFS with recent hypothesis version
Hi, I have upgraded python-datrie in Git[1] to latest upstream version (0.8). It shows the same issue - so I admit I have no better clue than reporting the issue upstream which I'd rather leave to the official Uploader of the package. BTW, we probably should expect build issues with Python 3.8[2] Kind regards Andreas. [1] https://salsa.debian.org/python-team/modules/python-datrie [2] https://github.com/pytries/datrie/issues/73 -- http://fam-tille.de
Processed: severity of 937808 is important
Processing commands for cont...@bugs.debian.org: > # I don't think this warrants serious severity. > severity 937808 important Bug #937808 [src:python-hglib] python-hglib: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 937808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937727: RM python-enable
Hi Varun! On Sun, Dec 08, 2019 at 10:35:51PM -0500, Scott Talbert wrote: > Control: reassign -1 ftp.debian.org > Control: retitle -1 RM: python-enable -- RoQA; unmaintained; low popcon; > blocking py2 removal; no rdeps I see you started working on python-enable in Git [1]. If you want to prevent removal of this package, please reassign this bug back to src:python-enable. But the Python 3 package will have to go through the NEW queue anyway, no matter if the old package is removed or not. [1]: https://salsa.debian.org/python-team/modules/python-enable/commits/master -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)
Hi Thorsten, The issue I reported that prevented systemd-sysusers from being used without systemd as the init system has just been fixed (#926316). So in theory we should be able to use it with other init systems. But the fact that elogind conflicts with systemd creates another hurdle. If the conflict can't be lifted I can see two solutions, either elogind provides its own version of systemd-sysusers, or systemd-sysusers is extracted into an independent package that doesn't conflict with elogind (I've filed #946456 for that). Emmanuel Bourg
Bug#946455: nomad: FTBFS (missing build-dependency on tzdata)
Package: src:nomad Version: 0.10.2+dfsg1-1 Severity: serious Tags: ftbfs Dear maintainer: This package fails to build in a minimal chroot including only essential and build-essential packages: [...] --- FAIL: TestPeriodicConfig_ValidTimeZone (0.00s) structs_test.go:2717: Valid tz errored: 1 error occurred: * Invalid time zone "Africa/Abidjan": unknown time zone Africa/Abidjan I believe there is a missing build-dependency on tzdata. Thanks.
Bug#946425: marked as done (python3-pubsub: missing Breaks+Replaces: python3-pypubsub)
Your message dated Mon, 09 Dec 2019 08:41:34 + with message-id and subject line Bug#946425: fixed in python-pypubsub 4.0.3-4 has caused the Debian Bug report #946425, regarding python3-pubsub: missing Breaks+Replaces: python3-pypubsub 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.) -- 946425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pubsub Version: 4.0.3-3 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 without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-pubsub_4.0.3-3_all.deb ... Unpacking python3-pubsub (4.0.3-3) ... dpkg: error processing archive /var/cache/apt/archives/python3-pubsub_4.0.3-3_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/Pypubsub-4.0.3.egg-info/PKG-INFO', which is also in package python3-pypubsub 4.0.3-2 Errors were encountered while processing: /var/cache/apt/archives/python3-pubsub_4.0.3-3_all.deb cheers, Andreas python3-pypubsub=4.0.3-2_python3-pubsub=4.0.3-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-pypubsub Source-Version: 4.0.3-4 We believe that the bug you reported is fixed in the latest version of python-pypubsub, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-pypubsub 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, 09 Dec 2019 08:38:32 +0100 Source: python-pypubsub Binary: python3-pubsub Architecture: source Version: 4.0.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: python3-pubsub - Python 3 publish-subcribe library Closes: 946425 Changes: python-pypubsub (4.0.3-4) unstable; urgency=medium . * Breaks+Replaces: python3-pypubsub Closes: #946425 Checksums-Sha1: c9f5f4e9de1dbf0c7d52d2dcc5826c9dbd1f3722 2090 python-pypubsub_4.0.3-4.dsc 330591584864750d1475fde64c07d3f2d29e80f2 2316 python-pypubsub_4.0.3-4.debian.tar.xz Checksums-Sha256: 29f39a57b842f0c786f151f029327838177f4e87ee64b549ab443663a04cc366 2090 python-pypubsub_4.0.3-4.dsc 1402b033aa6a9a9e4b833721be2e0b706d993458e5042cdbef27a24f1215afcc 2316 python-pypubsub_4.0.3-4.debian.tar.xz Files: 24cbcce3aa098369e7cf643e85c781c5 2090 python optional python-pypubsub_4.0.3-4.dsc ef101e9c4fa7aaa3863e595527d9d16b 2316 python optional python-pypubsub_4.0.3-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3uAKYRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFUZQ//ZHRWF2oP6N2IlmPeyHeRYsYOlI0IKQAp d7Xzzu5XPWsjipcd+417xounozLxdFTEvIetMadcsum98TY/fYKGLm4zfben+HsG /+U/hHnn6EsAETgrIxKNLRWSGE77Lk9MVs9i3p6L3McRABmnZLKVKXvd+PY1Mh5c r/1M7FFCM8e/nXat7K+xs7gxlrZgJCxxSSBtt5SG8QPYYWj/pwvpj6My7s4jwlpV 79QfjOmX0vmN2x061PPmamYC73pFGNirOWANYviAlZ7T7QL2/saH2Gq2sNgvRcVU NiX9Bmlzcn1O65JYrQXdiYjA6xIaY30zHwmrP3Yl4EBVtjkkbq4LR2hgZjzBtRyQ QdkAaKZbPzOuvjtydUnVSLdDrV+Xkk8SSC/kaJBr/H0voyoUuXJdcw++KlDmHSZ+ re0W22hgmXXacS6k66MIL9NDbZEwM0gmcfZ7wMrxW/pBRCfNvRXiIsMeMULF54Gv s9pm/8cbOcCmERctgzgOTW+mAn2lZPAFjPDc1pIVxNndgtbIVFqnAP3bkNalRnFt qHTrT2++M6uEw0D6SZz/Yg9hvuCIVizU1QuvowhZjdFzkDS3Bqp4/B+WW9Hn30Dk TW94BOLgQc5HzXYpfBhvzs/PC2zMmqPzxmIWrIS5laAFROKYTjycSBhGCqEjVe7+ cud8D8Vh+XI= =opwB -END PGP SIGNATURE End Message ---
Bug#946426: marked as done (python-pbcore: depends on old pylint3)
Your message dated Mon, 09 Dec 2019 08:41:28 + with message-id and subject line Bug#946426: fixed in python-pbcore 1.7.1+git20191121.7947eb7+dfsg-3 has caused the Debian Bug report #946426, regarding python-pbcore: depends on old pylint3 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.) -- 946426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pbcore Version: 1..7.1+git20191121.7947eb7+dfsg-2 Severity: serious Hello, please switch pylint3 version to pylint, because the pylint3 is a cruft package, not built anymore thanks Gianfranco --- End Message --- --- Begin Message --- Source: python-pbcore Source-Version: 1.7.1+git20191121.7947eb7+dfsg-3 We believe that the bug you reported is fixed in the latest version of python-pbcore, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-pbcore 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, 09 Dec 2019 09:06:38 +0100 Source: python-pbcore Binary: python3-pbcore python-pbcore-doc Architecture: source Version: 1.7.1+git20191121.7947eb7+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: python-pbcore-doc - Python library for processing PacBio data files (documentation) python3-pbcore - Python 3 library for processing PacBio data files Closes: 946426 Changes: python-pbcore (1.7.1+git20191121.7947eb7+dfsg-3) unstable; urgency=medium . * Build-Depends: s/pylint3/pylint/ Closes: #946426 Checksums-Sha1: 41b71ff813e2419395a9ae57987423cb26a7a16f 2774 python-pbcore_1.7.1+git20191121.7947eb7+dfsg-3.dsc a88a981067cb2245c8e141e9b9e41e4f5666f6cf 7340 python-pbcore_1.7.1+git20191121.7947eb7+dfsg-3.debian.tar.xz Checksums-Sha256: af94c81460e3418d55e8d87fa7285ef1333982f00d915610359569e47569680b 2774 python-pbcore_1.7.1+git20191121.7947eb7+dfsg-3.dsc b5f0f5ba25c6a6aed3378546ec0eb6efa49847d5756d54481d83ebf728616687 7340 python-pbcore_1.7.1+git20191121.7947eb7+dfsg-3.debian.tar.xz Files: d97335096457f6e76062f8be7f25f3ab 2774 python optional python-pbcore_1.7.1+git20191121.7947eb7+dfsg-3.dsc 471007676d6837a3465ba04a8b85b7d1 7340 python optional python-pbcore_1.7.1+git20191121.7947eb7+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3uBE0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHnVg/9GAgEamoC7tUKLZBBncywBB/H+iMZi0NF hwCieE2OL2bbVPESU3rYfuOBPXdBNzkNjlf85Ui0DHwDYcirB+R+Xmyq+vFrxcb9 dPa+ZnBOUP3USOqwzPBWgquqgPEMiWBjfdk+Mlz9MNw1y2goitOK33n+TEfmv+14 TS9XpJhmYCGgSro72MQi1ZXji9UQHCLMjxsJb8QaEap9sN93bHlD0vztw0QQbDE6 75c9vEuFc1CcuqWUofcLsKXfSBYairSMhWRWPRgQF72xDcyz2vLQrCPrTF8BLM/T RfQU2+J6pF3vduG/idI2RDd5u/b7WhZpkWXYjirbyf5X0eR48mgJwfB33+CJ3yOv QfV+c7uXakvzsdd+8LRymfhucrmN1UHxt48/zqAQF8ZlmLCHwoMwQXDnwY0YThNR Y2gUzlkzINkZewfL5nlHZsQXNxDnT+bcMLEVWzQc33GlX5+AwZ0zXkyhuKIVuQZL 8N+3XQhAK36AJ18+kuyJuvw3sB0zS6WrWWej2+a6wqpXFBYweFHkYThsK5txvTg7 hn6jHxttAKswPSzZqnikjLyYXw5Y83AtRyi3teeXIEYWmH8buZd9m0GHvoX6ydFk BGyWegLwb2O/GPF7tlKNEki2eqlSuAxJieSPqlEZNt52MweNBjCFlrVaV51A4ZKc 1Jry4SnoNZU= =j3Er -END PGP SIGNATURE End Message ---
Bug#946264: marked as done (openems: FTBFS (affects CGAL transition))
Your message dated Mon, 09 Dec 2019 08:41:20 + with message-id and subject line Bug#946264: fixed in openems 0.0.35+git20190103.6a75e98+dfsg.1-2 has caused the Debian Bug report #946264, regarding openems: FTBFS (affects CGAL transition) 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.) -- 946264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openems Version: 0.0.35+git20190103.6a75e98+dfsg.1-1 Severity: serious Tags: ftbfs Control: block 944417 by -1 Hi, the transition to CGAL 5.0 started (see bug #944417). A binNMU would have been sufficient, but your package FTBFS for unrelated reasons. See https://buildd.debian.org/status/package.php?p=openems . This might be the same problem as in bug #944144, but I'm not sure. Best regards, Joachim --- End Message --- --- Begin Message --- Source: openems Source-Version: 0.0.35+git20190103.6a75e98+dfsg.1-2 We believe that the bug you reported is fixed in the latest version of openems, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated openems 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, 09 Dec 2019 15:54:42 +0800 Source: openems Architecture: source Version: 0.0.35+git20190103.6a75e98+dfsg.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 944144 946264 Changes: openems (0.0.35+git20190103.6a75e98+dfsg.1-2) unstable; urgency=medium . * Team upload. * Build-Depends: python3-all-dev not python3-all, to provide Python.h. Closes: #944144, #946264. Checksums-Sha1: 797de29797f0c6853c5b212c46bc84786efe100a 2734 openems_0.0.35+git20190103.6a75e98+dfsg.1-2.dsc 4bed1b874e90cb2026c9874c9967599910fa1d6b 14064 openems_0.0.35+git20190103.6a75e98+dfsg.1-2.debian.tar.xz Checksums-Sha256: 88c9ceed3c6d0f30d0bc1a37842dfe9a13d93c59cd79f02fd89c50e6c4f46f80 2734 openems_0.0.35+git20190103.6a75e98+dfsg.1-2.dsc 1fe4fdbd9e05a72cff7f924582bfae08260e741f748f4369d07d31cc4df2a01c 14064 openems_0.0.35+git20190103.6a75e98+dfsg.1-2.debian.tar.xz Files: e06b95e6cbff85f39a61e3a37c9b4e6b 2734 electronics optional openems_0.0.35+git20190103.6a75e98+dfsg.1-2.dsc e065589b7d255739ee3e54a61a610206 14064 electronics optional openems_0.0.35+git20190103.6a75e98+dfsg.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl3uAt4ACgkQVz7x5L1a AfpyYw/+KxkKwBRleiEH5c2/mxZCGlX8roQeHW058nKYQVwZfVG6tFuYZC4qHOMa K0CpU38lc4koybgZEp0QkqtaclIj4DCSo+OLNuE5vt0DX7M69n8AB7gLr1p2HMe8 L/pWd9Ks5My1tlzV4dDgCMS5kGm/BSzzd/bqhGPkGtGL3qryY0Nej8ZHYq4//vl3 U+pkoPthyp8+Yjl2Lk/nayIWK6begWn4JhWQABXndUGUdZUb2sIBVgCjqUOrSQH9 ozWvgZOHpZ/z702Oa/yepX7a5VNqCZFW3gsp3Y0QnitFdNfooCHuvTbkN8BbV+Ni FY5E4aaYEeKJnE3PraV1b9GJ1E72fQ6IOhvB7iKGMFU+qkVj68vtd/F+ZnNat112 5oKLbRjr5HYkRj+F2i2dzvrOPL+ljJEqtI9l9ZVlRrFK1JyNKOq1uOEJDIx/OQQw trgV8fs0coKPM1SW16UkVd0J9x1A792Avq3JwM3xqbRzYbvJ7JdGDL1TNWH23m4V rSKtZglM/ogvLYxXR4uh2jiz67+RSQ4VBRdfsbgKmarrmj70u9Mv3s19HbNRPUFb AmNby/01NNygGs8VXRCK2dXVLylsXMgbp62qK8cBUNJnASG+jPTkfhnorrpgX6PO 8oW5A9mFbk5lE9CbRKZ3nZiwmGO5TjpfuivM9/872k+aPLs3dVA= =W/6d -END PGP SIGNATURE End Message ---
Bug#946452: mpqc3: FTBFS in sid
Source: mpqc3 Version: 0.0~git20170114-4 Severity: serious Hello, mpqc3 seems to FTBFS in sid with the following: In file included from /<>/src/lib/chemistry/qc/libint2/tbintlibint2.h:33, from /<>/src/lib/chemistry/qc/libint2/tbintlibint2.cc:34: /<>/src/lib/chemistry/qc/libint2/tbosar.h:411:23: error: use of deleted function ‘libint2::detail::CoreEvalScratch >& libint2::detail::CoreEvalScratch >::operator=(const libint2::detail::CoreEvalScratch >&)’ 411 | coreints_scratch_ = libint2::detail::CoreEvalScratch>(l1+l2+l3+l4); | ~~^~~~ The same is observed in reproducible builds for 0.0~git20170114-4.1 [1]. As a side note, salsa.d.o does not contain changelog entry for 0.0~git20170114-4.1, and Vcs-Svn is inaccessible. Best, Andrius [1] https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/mpqc3_0.0~git20170114-4.1.rbuild.log.gz
