Bug#938839: marked as done (xcb-proto: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Mar 2020 05:53:51 + with message-id and subject line Bug#938839: fixed in xcb-proto 1.14-1 has caused the Debian Bug report #938839, regarding xcb-proto: 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.) -- 938839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xcb-proto Version: 1.13-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:xcb-proto 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: xcb-proto Source-Version: 1.14-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xcb-proto, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xcb-proto 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: Fri, 27 Mar 2020 07:16:22 +0200 Source: xcb-proto Architecture: source Version: 1.14-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 938839 Changes: xcb-proto (1.14-1) unstable; urgency=medium . * New upstream release. * control: Use debhelper-compat, bump to 12. * control: Bump policy to 4.5.0. * docs: Updated. * Drop python-xcbgen (Closes: #938839) Checksums-Sha1: 68c81670343964966b0f399273436bacd0bbf2e7 1982 xcb-proto_1.14-1.dsc d14c18cb9f87a73d5a75301cefa210cdfeebc715 194242 xcb-proto_1.14.orig.tar.gz 8536602133f8a63555204df436d1ec05a218ae36 4778 xcb-proto_1.14-1.diff.gz 3331dff1390482f685a432fcca9e13559ff4e941 7077 xcb-proto_1.14-1_source.buildinfo Checksums-Sha256: 4a0ad8c87ed9aafca124cc36ee3917b61260eecba330aaa01002452c2df4c400 1982 xcb-proto_1.14-1.dsc 1c3fa23d091fb5e4f1e9bf145a902161cec00d260fabf880a7a248b02ab27031 194242
Processed: owner 954713
Processing commands for cont...@bugs.debian.org: > owner 954713 tmanc...@debian.org Bug #954713 [src:commons-configuration2] commons-configuration2: CVE-2020-1953 Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 954713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954402: m2crypto: FTBFS since openssl 1.1.1e
> So the test expects no error. Since the commit mention there is an > error where earlier there was none. From the Changes file: > > | *) Properly detect EOF while reading in libssl. Previously if we hit an EOF > |while reading in libssl then we would report an error back to the > |application (SSL_ERROR_SYSCALL) but errno would be 0. We now add > |an error to the stack (which means we instead return SSL_ERROR_SSL) and > |therefore give a hint as to what went wrong. > > OpenSSL 1.1.1d with the commit question leads to this behaviour. isnt this a regression in openssl then? why there's no RC bug filed against openssl and you filed this bug against a downstream package? i'm still not clear what you expect us to do with regards to m2crypto: should we skip the failing test? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#936570: marked as done (funkload: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Mar 2020 03:25:09 + with message-id and subject line Bug#955024: Removed package(s) from unstable has caused the Debian Bug report #936570, regarding funkload: 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.) -- 936570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:funkload Version: 1.17.1-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:funkload 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.17.1-2+rm Dear submitter, as the package funkload 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/955024 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#945712: marked as done (nitroshare: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Mar 2020 03:22:32 + with message-id and subject line Bug#954963: Removed package(s) from unstable has caused the Debian Bug report #942777, regarding nitroshare: 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.) -- 942777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nitroshare Version: 0.3.3-1.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.3.3-1.1+rm Dear submitter, as the package nitroshare 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/954963 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#920811: marked as done (wfrog: Depends on removed pygooglechart)
Your message dated Fri, 27 Mar 2020 03:23:20 + with message-id and subject line Bug#954967: Removed package(s) from unstable has caused the Debian Bug report #920811, regarding wfrog: Depends on removed pygooglechart 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.) -- 920811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wfrog Version: 0.8.2+svn973-1 Severity: grave Justification: renders package unusable wfrog is currently uninstallable due to the removal of pygooglechart (See http://bugs.debian.org/920779 for details). Scott K --- End Message --- --- Begin Message --- Version: 0.8.2+svn973-1+rm Dear submitter, as the package wfrog 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/954967 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#939478: marked as done (wfrog: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Mar 2020 03:23:20 + with message-id and subject line Bug#954967: Removed package(s) from unstable has caused the Debian Bug report #939478, regarding wfrog: 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.) -- 939478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wfrog Version: 0.8.2+svn973-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:cheetah 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. pgpNwtGmoNF8t.pgp Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 0.8.2+svn973-1+rm Dear submitter, as the package wfrog 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/954967 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#942777: marked as done (nitroshare-nautilus: Please port to python3-nautlius)
Your message dated Fri, 27 Mar 2020 03:22:32 + with message-id and subject line Bug#954963: Removed package(s) from unstable has caused the Debian Bug report #942777, regarding nitroshare-nautilus: Please port to python3-nautlius 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.) -- 942777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nitroshare-nautilus Version: 0.3.3-1.1 Severity: important Control: block 937115 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs python-nautilus Hello, Your package nitroshare-nautilus 0.3.3-1.1 depends on the python(2) bindings for nautilus. The src:nautilus-python package (currently stuck in NEW) was just uploaded building a new python3-nautilus package. This is a preparation for dropping the python-nautilus binary package, as there's currently ongoing work to remove python2 from debian. Please port your package to the new python3-nautilus bindings as soon as possible. On behalf of the Debian GNOME Team, Andreas Henriksson To: mainto...@bugs.debian.org Subject: nitroshare-nautilus: Please port to python3-nautlius Package: nitroshare-nautilus Version: 0.3.3-1.1 Severity: important Control: block 937115 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs python-nautilus Hello, Your package nitroshare-nautilus 0.3.3-1.1 depends on the python(2) bindings for nautilus. The src:nautilus-python package (currently stuck in NEW) was just uploaded building a new python3-nautilus package. This is a preparation for dropping the python-nautilus binary package, as there's currently ongoing work to remove python2 from debian. Please port your package to the new python3-nautilus bindings as soon as possible. On behalf of the Debian GNOME Team, Andreas Henriksson To: mainto...@bugs.debian.org Subject: nitroshare-nautilus: Please port to python3-nautlius Package: nitroshare-nautilus Version: 0.3.3-1.1 Severity: important Control: block 937115 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs python-nautilus Hello, Your package nitroshare-nautilus 0.3.3-1.1 depends on the python(2) bindings for nautilus. The src:nautilus-python package (currently stuck in NEW) was just uploaded building a new python3-nautilus package. This is a preparation for dropping the python-nautilus binary package, as there's currently ongoing work to remove python2 from debian. Please port your package to the new python3-nautilus bindings as soon as possible. On behalf of the Debian GNOME Team, Andreas Henriksson To: mainto...@bugs.debian.org Subject: nitroshare-nautilus: Please port to python3-nautlius Package: nitroshare-nautilus Version: 0.3.3-1.1 Severity: important Control: block 937115 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs python-nautilus Hello, Your package nitroshare-nautilus 0.3.3-1.1 depends on the python(2) bindings for nautilus. The src:nautilus-python package (currently stuck in NEW) was just uploaded building a new python3-nautilus package. This is a preparation for dropping the python-nautilus binary package, as there's currently ongoing work to remove python2 from debian. Please port your package to the new python3-nautilus bindings as soon as possible. On behalf of the Debian GNOME Team, Andreas Henriksson --- End Message --- --- Begin Message --- Version: 0.3.3-1.1+rm Dear submitter, as the package nitroshare 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/954963 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#917840: marked as done (nitroshare-nautilus: missing Depends: python-requests)
Your message dated Fri, 27 Mar 2020 03:22:32 + with message-id and subject line Bug#954963: Removed package(s) from unstable has caused the Debian Bug report #917840, regarding nitroshare-nautilus: missing Depends: python-requests 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.) -- 917840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nitroshare-nautilus Version: 0.3.3-1 Severity: important Dear Maintainer, The Nautilus Extension nitroshare-nautilus depends on the package python-requests which is not automatically installed as a dependency when the extension is installed. After installing python-requests manually it works as expected. System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nitroshare-nautilus depends on: ii nitroshare 0.3.3-1+b1 ii python-nautilus 1.2.2-2 nitroshare-nautilus recommends no packages. nitroshare-nautilus suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.3.3-1.1+rm Dear submitter, as the package nitroshare 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/954963 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#849087: marked as done (gourmet: Port to Python 3 and python3-gst-1.0)
Your message dated Fri, 27 Mar 2020 03:18:57 + with message-id and subject line Bug#954890: Removed package(s) from unstable has caused the Debian Bug report #849087, regarding gourmet: Port to Python 3 and python3-gst-1.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.) -- 849087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gourmet Severity: normal User: sl...@debian.org Usertags: python-gst-1.0-removal Hi, your package currently depends on python-gst-1.0. Upstream is planning to drop Python 2.x support in the near future, leaving only Python 3 support. Please update your package to Python 3 to make this as painless as possible later. Thanks! Sebastian signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 0.17.4-7+rm Dear submitter, as the package gourmet 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/954890 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#937175: marked as done (nxt-python: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Mar 2020 03:18:24 + with message-id and subject line Bug#954889: Removed package(s) from unstable has caused the Debian Bug report #937175, regarding nxt-python: 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.) -- 937175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nxt-python Version: 2.2.2-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:nxt-python 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: 2.2.2-4+rm Dear submitter, as the package nxt-python 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/954889 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#886276: marked as done (gourmet: Depends on unmaintained pygtk)
Your message dated Fri, 27 Mar 2020 03:18:57 + with message-id and subject line Bug#954890: Removed package(s) from unstable has caused the Debian Bug report #886276, regarding gourmet: 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.) -- 886276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gourmet Version: 0.17.4-4 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 soon. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 0.17.4-7+rm Dear submitter, as the package gourmet 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/954890 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#885467: marked as done (python-nxt-filer: Depends on unmaintained pygtk)
Your message dated Fri, 27 Mar 2020 03:18:24 + with message-id and subject line Bug#954889: Removed package(s) from unstable has caused the Debian Bug report #885467, regarding python-nxt-filer: 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.) -- 885467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-nxt-filer Version: 2.2.2-4 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: 2.2.2-4+rm Dear submitter, as the package nxt-python 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/954889 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#936561: marked as done (freshen: Python2 removal in sid/bullseye)
Your message dated Fri, 27 Mar 2020 03:20:47 + with message-id and subject line Bug#954946: Removed package(s) from unstable has caused the Debian Bug report #936561, regarding freshen: 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.) -- 936561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freshen Version: 0.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:freshen If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.2-2+rm Dear submitter, as the package freshen 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/954946 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#936641: marked as done (gourmet: Port to Python 3 and python3-gst-1.0)
Your message dated Fri, 27 Mar 2020 03:18:57 + with message-id and subject line Bug#954890: Removed package(s) from unstable has caused the Debian Bug report #849087, regarding gourmet: Port to Python 3 and python3-gst-1.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.) -- 849087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gourmet Version: 0.17.4-7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:gourmet If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.17.4-7+rm Dear submitter, as the package gourmet 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/954890 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#955027: php-recode: uninstallable due to php7.4-recode dependency
Package: php-recode Version: 2:7.4+74 Severity: grave Justification: renders package unusable Dear Maintainer, The php-recode package is currently not installable because it depends on php7.4-recode, which doesn't exist. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-recode depends on: ii php-common 2:74 ii php7.3-recode 7.3.15-3 php-recode recommends no packages. php-recode suggests no packages. -- no debconf information
Bug#952329: marked as done (sndobj: FTBFS: ModuleNotFoundError: No module named 'distutils.sysconfig':)
Your message dated Thu, 26 Mar 2020 23:42:26 + with message-id and subject line Bug#952329: fixed in sndobj 2.6.7+ds1-3 has caused the Debian Bug report #952329, regarding sndobj: FTBFS: ModuleNotFoundError: No module named 'distutils.sysconfig': 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.) -- 952329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sndobj Version: 2.6.7+ds1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p lib > scons ALSA=true OSS=false JACK=true customLIBS=pthread > customLIBPATH=/usr/lib/x86_64-linux-gnu customCCFLAGS="-Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security" > customCXXFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" customSHLINKFLAGS="-Wl,-z,relro" > scons: Reading SConscript files ... > ModuleNotFoundError: No module named 'distutils.sysconfig': > File "/<>/SConstruct", line 28: > import distutils.sysconfig > make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/sndobj_2.6.7+ds1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: sndobj Source-Version: 2.6.7+ds1-3 Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= We believe that the bug you reported is fixed in the latest version of sndobj, 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 952...@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 sndobj package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 27 Mar 2020 00:19:43 +0100 Source: sndobj Architecture: source Version: 2.6.7+ds1-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 952329 Changes: sndobj (2.6.7+ds1-3) unstable; urgency=medium . * Team upload. . * B-D on python3-distutils (Closes: #952329) * Add salsa-ci configuration * Bump standards version to 4.5.0 Checksums-Sha1: d5692929acdc9127de0beebd93682949c64488c5 2225 sndobj_2.6.7+ds1-3.dsc da375315dccda232aed0efdd5acb2f8bd4ba3a60 12196 sndobj_2.6.7+ds1-3.debian.tar.xz Checksums-Sha256: d01ad25c1f2b14a530208b45f3671d27f7179f92212217d7b853e0f53c9edcd1 2225 sndobj_2.6.7+ds1-3.dsc 63b2f10bfa31ec622ff38f83173b3e07c83c77b9649fba0f2252bf41c42d0216 12196 sndobj_2.6.7+ds1-3.debian.tar.xz Files: 9c62cfce23e7d078e6dbefb344e42349 2225 sound optional sndobj_2.6.7+ds1-3.dsc e7e4f9b38dec76b3fd79fe917e2cc672 12196 sound optional sndobj_2.6.7+ds1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl59ObsWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+MoCD/0dEinwaH4wnH9URZ0r6FPZzlzu FVobXbhJc5GN8NewX8MqP50GPQ9MzVZcVMTKA3TuNDNCf89IYsiGpNNHFduMFIi5 jI38WzjcOkBFheoktk8AQIdlp5sxI2EzjGJ4tG3dy4W9JACuNN4RP7ygVBfSANBa LWNQId07aOiGXajEf+3D8QL+CLf4jeF2sXYmugz/NYD31cKupMVBOPq54474czFq e6nJLQ/FHFg1IYTsjowZZ6Ayd4wQmifeWLHIuEiEmp/l2l/wTkn/2Rt7uHr40Q0y hwF5gj1QIyAcaJXk7YKB4oDWQs8Xc5i1P1VCILKjIrQA6w+jCljO8dVsQjrF1vmO IpQRTY3LxtsUfP5TZrWP3wFJaWMk08BhPn72Xus/dR5r4zjzlta1Kk0w8byFYmP2 hQ1eu1nmQjYzCVN2IvzIGjsGf04fOVbRxO9cHwgs7KLse+ZqVBOBEHWhhDAqFaR2 mJx0yE13Z0uqfgPh7j0GFWcphgJTHdhBXmPSQuldgAi/VR/8syoKb3hC2bNoEtHI DscLyenY4lsvymljYZ+NFqTj2IpUMEwSbArckSGWuZyrHkehVVoJ+sTHVO1mLhZq
Bug#954702: marked as done (acorn: FTBFS: You have passed an unrecognized option)
Your message dated Thu, 26 Mar 2020 23:34:50 + with message-id and subject line Bug#954702: fixed in acorn 6.2.1+ds+~cs11.24.3-1 has caused the Debian Bug report #954702, regarding acorn: FTBFS: You have passed an unrecognized option 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.) -- 954702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: acorn Version: 6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-14 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p build/acorn/ > cp -rf acorn build > # remove identifier > rm -f build/acorn//src/identifier.js > touch build/acorn/builddir.stamp > node bin/generate-identifier-regex.js acorn/src/identifier.js > > build/acorn/src/identifier.js > cd build && TRANSPILE=babel6 BABEL_PRESET=es2015 rollup -c > acorn/rollup.config.js > (!) You have passed an unrecognized option > Unknown input option: entry, moduleName, sourceMap, targets. Allowed options: > acorn, acornInjectPlugins, cache, chunkGroupingSize, context, > experimentalCacheExpiry, experimentalOptimizeChunks, > experimentalTopLevelAwait, external, inlineDynamicImports, input, > manualChunks, moduleContext, onwarn, perf, plugins, preserveModules, > preserveSymlinks, shimMissingExports, treeshake, watch > > undefined → stdout... > [!] Error: You must supply options.input to rollup > Error: You must supply options.input to rollup > at new Graph (/usr/share/nodejs/rollup/src/Graph.js:93:19) > at Object.rollup (/usr/share/nodejs/rollup/src/rollup/index.js:131:23) > at Object.build [as default] > (/usr/share/nodejs/rollup/bin/src/run/build.js:41:10) > at /usr/share/nodejs/rollup/bin/src/run/index.js:117:39 > at process._tickCallback (internal/process/next_tick.js:68:7) > at Function.Module.runMain (internal/modules/cjs/loader.js:834:11) > at startup (internal/bootstrap/node.js:283:19) > at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3) > > make[1]: *** [debian/rules:56: build/acorn/build.stamp] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/03/22/acorn_6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-14_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: acorn Source-Version: 6.2.1+ds+~cs11.24.3-1 Done: =?utf-8?q?Bastien_Roucari=C3=A8s?= We believe that the bug you reported is fixed in the latest version of acorn, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated acorn 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: Fri, 27 Mar 2020 00:30:06 +0100 Source: acorn Architecture: source Version: 6.2.1+ds+~cs11.24.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Bastien Roucariès Closes: 940708 954702 Changes: acorn (6.2.1+ds+~cs11.24.3-1) unstable; urgency=medium . [ Xavier Guimard ] * Team upload * Fix components list in debian/gbp.conf * Fix for rollup 1 (Closes: #954702) * Use checksum+ctype uscan features (Closes: #940708) * Repack current version into 6.2.1+ds+~cs11.24.3 * Add "Rules-Requires-Root: no" * Update lintian overrides Checksums-Sha1: b680c7d1f48a9c1daf3a56ea3812cdfc720e6f38 6534 acorn_6.2.1+ds+~cs11.24.3-1.dsc 4d39686fcaa844a4d5c414a75d3f73c7e438e643 5900
Bug#954901: ghostscript: runtime error: malloc(): invalid size (unsorted)
Dear Maintainer, I tried to collect some more information and might have found something. The allocator aborts at the backtrace below. A valgrind run points to the same function txt_add_fragment. There is seems that in line 2121 the allocation takes place with 12 bytes total, then a memset is done with 12 bytes. But in line 2126 the memcpy is done with 24 bytes. This is because allocation is done with penum->TextBufferIndex == 3, but the memcpy uses penum->text.size == 6. (For the given input file.) The same pattern in lines 2134 to 2139. But I have no clue if the variables are the right ones, or contain wrong values. It might be related to this upstream bug, which touches the same lines: https://bugs.ghostscript.com/show_bug.cgi?id=701877 Kind regards, Bernhard https://sources.debian.org/src/ghostscript/9.52%7Edfsg-1/devices/vector/gdevtxtw.c/#L2121 https://git.ghostscript.com/?p=ghostpdl.git;a=blob;f=devices/vector/gdevtxtw.c;h=87f9355d8771e1fa546b4eb687ae4078ef2abdff;hb=HEAD#l2121 2121 penum->text_state->Widths = (float *)gs_malloc(tdev->memory->stable_memory, 2122 penum->TextBufferIndex, sizeof(float), "txtwrite alloc widths array"); 2123 if (!penum->text_state->Widths) 2124 return gs_note_error(gs_error_VMerror); 2125 memset(penum->text_state->Widths, 0x00, penum->TextBufferIndex * sizeof(float)); 2126 memcpy(penum->text_state->Widths, penum->Widths, penum->text.size * sizeof(float)); (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7fb706bae55b in __GI_abort () at abort.c:79 #2 0x7fb706c06ff8 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fb706d13f3e "%s\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x7fb706c0e39a in malloc_printerr (str=str@entry=0x7fb706d16010 "malloc(): invalid size (unsorted)") at malloc.c:5339 #4 0x7fb706c11304 in _int_malloc (av=av@entry=0x7fb706d45b80 , bytes=bytes@entry=62) at malloc.c:3736 #5 0x7fb706c12a74 in __GI___libc_malloc (bytes=bytes@entry=62) at malloc.c:3058 #6 0x7fb7070a3445 in gs_heap_alloc_bytes (mem=0x5600c40c5c40, size=14, cname=0x7fb7072389c8 "txtwrite alloc sorted text buffer") at ./base/gsmalloc.c:191 #7 0x7fb706fe88e1 in txt_add_fragment (penum=0x5600c45abea8, tdev=) at ./devices/vector/gdevtxtw.c:2141 #8 textw_text_process (pte=0x5600c45abea8) at ./devices/vector/gdevtxtw.c:2241 #9 0x7fb70717b8a0 in op_show_continue (i_ctx_p=0x5600c40f9778) at ./psi/zchar.c:690 #10 op_show_continue (i_ctx_p=0x5600c40f9778) at ./psi/zchar.c:685 #11 0x7fb70715d739 in interp (perror_object=, pref=, pi_ctx_p=) at ./psi/interp.c:1300 #12 gs_call_interp (pi_ctx_p=pi_ctx_p@entry=0x5600c40c6590, pref=pref@entry=0x775a4350, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x775a43cc, perror_object=) at ./psi/interp.c:520 #13 0x7fb70715ec7a in gs_interpret (pi_ctx_p=pi_ctx_p@entry=0x5600c40c6590, pref=pref@entry=0x775a4350, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x775a43cc, perror_object=, perror_object@entry=0x775a43d0) at ./psi/interp.c:477 #14 0x7fb70715153e in gs_main_interpret (perror_object=0x775a43d0, pexit_code=0x775a43cc, user_errors=1, pref=0x775a4350, minst=) at ./psi/imain.c:791 #15 gs_main_run_string_end (minst=minst@entry=0x5600c40c64f0, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x775a43cc, perror_object=perror_object@entry=0x775a43d0) at ./psi/imain.c:791 #16 0x7fb7071515d1 in gs_main_run_string_with_length (str=, length=, perror_object=0x775a43d0, pexit_code=0x775a43cc, user_errors=1, minst=0x5600c40c64f0) at ./psi/imain.c:735 #17 gs_main_run_string_with_length (minst=0x5600c40c64f0, str=0x5600c41c2720 "<6f75742e706466>.runfile", length=24, user_errors=1, pexit_code=0x775a43cc, perror_object=0x775a43d0) at ./psi/imain.c:721 #18 0x7fb7071534ef in run_string (minst=minst@entry=0x5600c40c64f0, str=str@entry=0x5600c41c2720 "<6f75742e706466>.runfile", options=options@entry=3, user_errors=user_errors@entry=1, pexit_code=0x775a43cc, pexit_code@entry=0x0, perror_object=0x775a43d0, perror_object@entry=0x0) at ./psi/imainarg.c:1119 #19 0x7fb7071537e6 in runarg (minst=minst@entry=0x5600c40c64f0, arg=arg@entry=0x775a4508 "out.pdf", post=post@entry=0x7fb70725cc5c ".runfile", options=options@entry=3, user_errors=1, pexit_code=pexit_code@entry=0x0, perror_object=0x0, pre=0x7fb70723aced "") at ./psi/imainarg.c:1088 #20 0x7fb707153904 in argproc (arg=0x775a4508 "out.pdf", minst=0x5600c40c64f0) at ./psi/imainarg.c:1010 #21 argproc (minst=0x5600c40c64f0, arg=0x775a4508 "out.pdf") at ./psi/imainarg.c:995 #22 0x7fb707155010 in gs_main_init_with_args01 (minst=minst@entry=0x5600c40c64f0, argc=7, argv=0x775a5038) at ./psi/imainarg.c:241 #23 0x7fb7071552b9 in gs_main_init_with_args (minst=0x5600c40c64f0, argc=, argv=) at
Bug#936188: bbqsql: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:11:19AM +, Matthias Klose wrote: > Package: src:bbqsql > 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. Hi Marcos, bbqsql seems dead upstream, development mostly stopped in 2013 and the author mentions in https://github.com/Neohapsis/bbqsql/pull/61 "he no longer works for the company". Are you planning to port it to Python 3 yourself or should it be removed? Cheers, Moritz
Bug#938612: sx: Python2 removal in sid/bullseye
On Tue, Jan 21, 2020 at 12:02:45AM +1100, Stuart Prescott wrote: > It seems that the upstream for src:sx has disappeared and so I guess the > porting work to change this package to be Python 3 compatible has not been > done. > > At a quick glance, the porting doesn't look that hard to do, but is it > worthwhile for what appears to be a low popcon, dead upstream package? Is > removal a better option at this stage? Hi Laszlo, what do think, should we remove sx? Cheers, Moritz
Processed: Re: ghdl: non-standard gcc/g++ used for build (gcc-8)
Processing control commands: > block 954831 with -1 Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9 954831 was blocked by: 944170 944172 944169 944177 944167 954831 was not blocking any bugs. Added blocking bug(s) of 954831: 944181 > severity -1 serious Bug #944181 [ghdl] ghdl: non-standard gcc/g++ used for build (gcc-8) Severity set to 'serious' from 'important' -- 944181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944181 954831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: gcc-mingw-w64: non-standard gcc/g++ used for build (gcc-8)
Processing control commands: > block 954831 with -1 Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9 954831 was blocked by: 944177 944172 944169 944170 954831 was not blocking any bugs. Added blocking bug(s) of 954831: 944167 > severity -1 serious Bug #944167 [gcc-mingw-w64] gcc-mingw-w64: non-standard gcc/g++ used for build (gcc-8) Severity set to 'serious' from 'important' -- 944167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944167 954831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: open-ath9k-htc-firmware: non-standard gcc/g++ used for build (gcc-8)
Processing control commands: > block 954831 with -1 Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9 954831 was blocked by: 944170 944177 954831 was not blocking any bugs. Added blocking bug(s) of 954831: 944169 > severity -1 serious Bug #944169 [open-ath9k-htc-firmware] open-ath9k-htc-firmware: non-standard gcc/g++ used for build (gcc-8) Severity set to 'serious' from 'important' -- 944169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944169 954831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: openzwave: non-standard gcc/g++ used for build (gcc-8)
Processing control commands: > block 954831 with -1 Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9 954831 was blocked by: 944169 944170 944177 954831 was not blocking any bugs. Added blocking bug(s) of 954831: 944172 > severity -1 serious Bug #944172 [openzwave] openzwave: non-standard gcc/g++ used for build (gcc-8) Severity set to 'serious' from 'important' -- 944172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944172 954831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: mysql-workbench: non-standard gcc/g++ used for build (gcc-8)
Processing control commands: > block 954831 with -1 Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9 954831 was blocked by: 944170 954831 was not blocking any bugs. Added blocking bug(s) of 954831: 944177 > severity -1 serious Bug #944177 [mysql-workbench] mysql-workbench: non-standard gcc/g++ used for build (gcc-8) Severity set to 'serious' from 'important' -- 944177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944177 954831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: kfreebsd-10: non-standard gcc/g++ used for build (gcc-8)
Processing control commands: > block 954831 with -1 Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9 954831 was not blocked by any bugs. 954831 was not blocking any bugs. Added blocking bug(s) of 954831: 944170 > severity -1 serious Bug #944170 [kfreebsd-10] kfreebsd-10: non-standard gcc/g++ used for build (gcc-8) Severity set to 'serious' from 'important' -- 944170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944170 954831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
Jens, the log indicates the machine has an Intel(R) HD Graphics 530 (Skylake GT2) GPU. Is this the same for the other machines? I have been trying to reproduce for several days, also running on Intel drivers, but with a 5500 series GPU and also I am on "testing" so I have newer Xorg and kernel. Tormod
Bug#950090: marked as done (gcc-mingw-w64: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Thu, 26 Mar 2020 20:53:24 + with message-id and subject line Bug#950090: fixed in gcc-mingw-w64 22~exp3 has caused the Debian Bug report #950090, regarding gcc-mingw-w64: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 950090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-mingw-w64 Version: 22~exp2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + gcc-mingw-w64-x86-64 gfortran-mingw-w64-x86-64 g++-mingw-w64-x86-64 gobjc-mingw-w64-x86-64 gobjc++-mingw-w64-x86-64 gnat-mingw-w64-x86-64 Control: affects -1 + gcc-mingw-w64-i686 gfortran-mingw-w64-i686 g++-mingw-w64-i686 gobjc-mingw-w64-i686 gobjc++-mingw-w64-i686 gnat-mingw-w64-i686 Control: found -1 gcc-mingw-w64/9.2.1-21+22~exp2 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. >From the attached log (scroll to the bottom...): 0m37.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/g++-mingw-w64-i686/changelog.Debian.gz (g++-mingw-w64-i686) != /usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base) /usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base /usr/share/doc/g++-mingw-w64-i686/changelog.gz (g++-mingw-w64-i686) != /usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base) /usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base /usr/share/doc/g++-mingw-w64-i686/copyright (g++-mingw-w64-i686) != /usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base) /usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base /usr/share/doc/gcc-mingw-w64-i686/changelog.Debian.gz (gcc-mingw-w64-i686) != /usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base) /usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base /usr/share/doc/gcc-mingw-w64-i686/changelog.gz (gcc-mingw-w64-i686) != /usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base) /usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base /usr/share/doc/gcc-mingw-w64-i686/copyright (gcc-mingw-w64-i686) != /usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base) /usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base 0m36.2s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/gcc-mingw-w64-x86-64/changelog.Debian.gz (gcc-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base) /usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base /usr/share/doc/gcc-mingw-w64-x86-64/changelog.gz (gcc-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base) /usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base /usr/share/doc/gcc-mingw-w64-x86-64/copyright (gcc-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base) /usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base /usr/share/doc/gfortran-mingw-w64-x86-64/changelog.Debian.gz (gfortran-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz
Processed: Re: FTBFS with OCaml 4.08.1 (implementation/interface mismatch)
Processing control commands: > tags -1 pending Bug #944365 [src:frama-c] FTBFS with OCaml 4.08.1 (implementation/interface mismatch) Added tag(s) pending. -- 944365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944365: FTBFS with OCaml 4.08.1 (implementation/interface mismatch)
control: tags -1 pending in deferred/5 G. On Fri, 08 Nov 2019 16:54:04 +0100 =?utf-8?q?St=C3=A9phane_Glondu?= wrote: > Package: src:frama-c > Version: 20171101+sulfur+dfsg-2 > Severity: serious > Tags: ftbfs > User: debian-ocaml-ma...@lists.debian.org > Usertags: ocaml-4.08-transition > > Dear Maintainer, > > frama-c FTBFS with OCaml 4.08.1: > > https://buildd.debian.org/status/package.php?p=frama-c > > > Cheers, > > -- > Stéphane > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled
Bug#952329: marked as pending in sndobj
Control: tag -1 pending Hello, Bug #952329 in sndobj 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/multimedia-team/sndobj/-/commit/efde09ea35be848140cabc45209ff866f76a0381 B-D onpython3-distutils Closes: #952329 (this message was generated automatically) -- Greetings https://bugs.debian.org/952329
Processed: Bug#952329 marked as pending in sndobj
Processing control commands: > tag -1 pending Bug #952329 [src:sndobj] sndobj: FTBFS: ModuleNotFoundError: No module named 'distutils.sysconfig': Added tag(s) pending. -- 952329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954826: libgcc-8-dev: depends on unavailable version of libgcc-s1
On 3/26/20 8:51 PM, Colomban Wendling wrote: > Hi, > > Sorry if I'm too far off the tree, but isn't this just an overlook of > the dependency switch from libgcc1 (which has an "1" epoch) to the > libgcc-s1 (which doesn't have an epoch)? > > ATM at least clang-9 (which is still the default in unstable) depends on > libgcc-8-dev, and while I probably miss some important details, I fail > to see why we have to drop gcc-8 because of this? yes, but we cannot rebuild the package, because it build-depends on gnat-8. Filed a removal bug for gcc-8 instead.
Bug#954826: libgcc-8-dev: depends on unavailable version of libgcc-s1
Hi, Sorry if I'm too far off the tree, but isn't this just an overlook of the dependency switch from libgcc1 (which has an "1" epoch) to the libgcc-s1 (which doesn't have an epoch)? ATM at least clang-9 (which is still the default in unstable) depends on libgcc-8-dev, and while I probably miss some important details, I fail to see why we have to drop gcc-8 because of this? Regards, Colomban
Bug#954635: golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depends-
Control: reassign -1 src:mono 6.8.0.105+dfsg-2 Control: retitle -1 CLI binding packages fail to install: Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception Control: affects -1 src:golang-github-thecreeper-go-notify libglib2.0-cil libgdcm-cil Control: severity -1 grave On Sun, 22 Mar 2020 08:45:16 +0100 Lucas Nussbaum wrote: > Source: golang-github-thecreeper-go-notify > Version: 0.0~git20160203.0.b5cd147-4 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200321 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): [snip] > Setting up librest-0.7-0:amd64 (0.8.1-1+b1) ... > Setting up libgtk-3-0:amd64 (3.24.14-1) ... > Setting up libgtk2.0-0:amd64 (2.24.32-4) ... > Setting up libgtk-3-bin (3.24.14-1) ... > Setting up notification-daemon (3.20.0-4) ... > Setting up libmono-system-numerics4.0-cil (6.8.0.105+dfsg-2) ... > Setting up libmono-system-core4.0-cil (6.8.0.105+dfsg-2) ... > Setting up dh-autoreconf (19) ... > Setting up libmono-system-security4.0-cil (6.8.0.105+dfsg-2) ... > Setting up mono-runtime-sgen (6.8.0.105+dfsg-2) ... > Setting up mono-runtime (6.8.0.105+dfsg-2) ... > update-alternatives: using /usr/bin/mono to provide /usr/bin/cli (cli) in > auto mode > Setting up libmono-system-configuration4.0-cil (6.8.0.105+dfsg-2) ... > Setting up debhelper (12.9) ... > Setting up libmono-corlib4.5-cil (6.8.0.105+dfsg-2) ... > Setting up libmono-cairo4.0-cil (6.8.0.105+dfsg-2) ... > Setting up libmono-system-xml4.0-cil (6.8.0.105+dfsg-2) ... > Setting up dh-golang (1.48) ... > Setting up libmono-system4.0-cil (6.8.0.105+dfsg-2) ... > Setting up libmono-posix4.0-cil (6.8.0.105+dfsg-2) ... > Setting up libmono-system-drawing4.0-cil (6.8.0.105+dfsg-2) ... > Setting up libdbus2.0-cil (0.8.1-2) ... > * Installing 1 assembly from libdbus2.0-cil into Mono > > Unhandled Exception: > System.TypeInitializationException: The type initializer for 'Sys' threw an > exception. ---> System.DllNotFoundException: System.Native assembly: assembly> type: member:(null) > at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() > at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 >--- End of inner exception stack trace --- > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, > System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) > [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 > at System.IO.File.Exists (System.String path) [0x00058] in > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in > <3a4d36ecef0a47439a72108fe400486f>:0 > at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in > <3a4d36ecef0a47439a72108fe400486f>:0 > [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The > type initializer for 'Sys' threw an exception. ---> > System.DllNotFoundException: System.Native assembly: > type: member:(null) > at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() > at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 >--- End of inner exception stack trace --- > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, > System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) > [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 > at System.IO.File.Exists (System.String path) [0x00058] in > <12b418a7818c4ca0893feeaaf67f1e7f>:0 > at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in > <3a4d36ecef0a47439a72108fe400486f>:0 > at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in > <3a4d36ecef0a47439a72108fe400486f>:0 > E: installing Assembly /usr/lib/cli/dbus-sharp-2.0/dbus-sharp.dll failed > E: Installation of libdbus2.0-cil with /usr/share/cli-common/runtimes.d/mono > failed > dpkg: error processing package libdbus2.0-cil (--configure): > installed libdbus2.0-cil package post-installation script subprocess > returned error exit status 29 > Setting up mono-4.0-gac (6.8.0.105+dfsg-2) ... > Setting up libglib2.0-cil (2.12.40-3) ... I am seeing this in more places, see e.g. https://piuparts.debian.org/sid/fail/libgdcm-cil_3.0.5-1.log I can easily reproduce those in both testing and sid chroots by installing libglib2.0-cil or libgdcm-cil (probably others are affected as well but I just tried those). A subsequent `apt install -f' manages to configure the affected package, so I wonder if this is related to mono not working properly until mono-runtime-common is configured due to the absence of /etc/mono/config, which
Processed: src:librouteros: fails to migrate to testing for too long
Processing control commands: > fixed -1 3.0.0-1 Bug #955012 [src:librouteros] src:librouteros: fails to migrate to testing for too long Marked as fixed in versions librouteros/3.0.0-1. -- 955012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955013: src:boxer-data: fails to migrate to testing for too long
Source: boxer-data Version: 10.8.11 Severity: serious Control: fixed -1 10.8.12 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:boxer-data in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=boxer-data signature.asc Description: OpenPGP digital signature
Processed: Re: golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depen
Processing control commands: > reassign -1 src:mono 6.8.0.105+dfsg-2 Bug #954635 [src:golang-github-thecreeper-go-notify] golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depends-main-dummy Bug reassigned from package 'src:golang-github-thecreeper-go-notify' to 'src:mono'. No longer marked as found in versions golang-github-thecreeper-go-notify/0.0~git20160203.0.b5cd147-4. Ignoring request to alter fixed versions of bug #954635 to the same values previously set Bug #954635 [src:mono] golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depends-main-dummy Marked as found in versions mono/6.8.0.105+dfsg-2. > retitle -1 CLI binding packages fail to install: Unhandled Exception: > System.TypeInitializationException: The type initializer for 'Sys' threw an > exception Bug #954635 [src:mono] golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depends-main-dummy Changed Bug title to 'CLI binding packages fail to install: Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception' from 'golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depends-main-dummy'. > affects -1 src:golang-github-thecreeper-go-notify libglib2.0-cil libgdcm-cil Bug #954635 [src:mono] CLI binding packages fail to install: Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception Added indication that 954635 affects src:golang-github-thecreeper-go-notify, libglib2.0-cil, and libgdcm-cil > severity -1 grave Bug #954635 [src:mono] CLI binding packages fail to install: Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception Severity set to 'grave' from 'serious' -- 954635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955012: src:librouteros: fails to migrate to testing for too long
Source: librouteros Version: 2.2.0-1 Severity: serious Control: fixed -1 3.0.0-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:librouteros in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=librouteros signature.asc Description: OpenPGP digital signature
Processed: src:boxer-data: fails to migrate to testing for too long
Processing control commands: > fixed -1 10.8.12 Bug #955013 [src:boxer-data] src:boxer-data: fails to migrate to testing for too long Marked as fixed in versions boxer-data/10.8.12. -- 955013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954774: marked as done (mozjs68: FTBFS on armel: rust/cargo using armv7-unknown-linux-gnueabi, should be armv5te-unknown-linux-gnueabi)
Your message dated Thu, 26 Mar 2020 19:20:00 +
with message-id
and subject line Bug#954774: fixed in mozjs68 68.6.0-1
has caused the Debian Bug report #954774,
regarding mozjs68: FTBFS on armel: rust/cargo using
armv7-unknown-linux-gnueabi, should be armv5te-unknown-linux-gnueabi
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.)
--
954774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs68
Version: 68.5.0-2
Severity: serious
Tags: ftbfs
Justification: will break gjs and gnome-shell which previously worked
X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org
Control: block 954422 by -1
mozjs68 FTBFS on armel:
> checking for cargo... /usr/bin/cargo
> checking rustc version... 1.40.0
> checking cargo version... 1.39.0
> checking for rust target triplet...
> DEBUG: Creating `/tmp/conftest5opOdA.rs` with content:
> DEBUG: | pub extern fn hello() { println!("Hello world"); }
> DEBUG: Executing: `/usr/bin/rustc --crate-type staticlib
> --target=armv7-unknown-linux-gnueabi -o /tmp/conftestpb2Eua.rlib
> /tmp/conftest5opOdA.rs`
> DEBUG: The command returned non-zero exit status 1.
> DEBUG: Its error output was:
> DEBUG: | error[E0463]: can't find crate for `std`
> DEBUG: | |
> DEBUG: | = note: the `armv7-unknown-linux-gnueabi` target may not be
> installed
>From the cargo and rustc buildd logs, it looks as though it should be
using --target=armv5te-unknown-linux-gnueabi instead. I'm not sure where
this build system gets its idea of what the most appropriate target is.
cargo has https://sources.debian.org/src/cargo/0.40.0-3/debian/bin/cargo/
and https://sources.debian.org/src/rustc/1.40.0+dfsg1-5/debian/architecture.mk/
(/usr/share/rustc/architecture.mk) which know how to map GNU tuples to
rustc targets - we should probably be using at least architecture.mk, and
possibly also the cargo wrapper.
It isn't clear whether firefox-esr would have had this problem or not,
because it's BD-uninstallable in stable and unstable for orthogonal
reasons (it B-D on nodejs which isn't available on armel).
This is not technically a regression, because mozjs68 is a new package,
but it'll be a regression for gjs (when we get gjs to build successfully
on buildds at all, which I'm making progress on).
This needs to be resolved, one way or another, before the GNOME 3.36
transition can go through. It can either be resolved by making mozjs68
build successfully on armel, or by removing gjs, gnome-shell and all their
reverse-dependencies from armel, like we had to do for s390x in buster.
smcv
--- End Message ---
--- Begin Message ---
Source: mozjs68
Source-Version: 68.6.0-1
Done: Iain Lane
We believe that the bug you reported is fixed in the latest version of
mozjs68, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Iain Lane (supplier of updated mozjs68 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 26 Mar 2020 17:52:32 +
Source: mozjs68
Architecture: source
Version: 68.6.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Iain Lane
Closes: 954774
Changes:
mozjs68 (68.6.0-1) experimental; urgency=medium
.
[ Marco Trevisan (Treviño) ]
* New upstream release with security fixes:
- https://www.mozilla.org/en-US/firefox/68.6.0/releasenotes/
.
[ Simon McVittie ]
* d/rules: Swap --host and --target.
The Mozilla build system's terminology is not the same as Autoconf's,
and previous versions of the mozjs Debian packages got the translation
wrong.
* d/rules: Ask moz.configure to give us more information
* d/rules: Print complete config.log if configure fails
* d/rules: Forcibly set appropriate values for the Rust targets,
fixing FTBFS on armel (Closes: #954774)
Checksums-Sha1:
83098a35973b4eb748e1881000c8feae0a96567b 2324 mozjs68_68.6.0-1.dsc
98eb63629e8889caa738fa15591fe8eeba73b227 75303520 mozjs68_68.6.0.orig.tar.xz
ebf61971af52f1f1d07376bb2251c41018d98c2b 43376
Bug#954992: marked as done (gdcm: b-dep on cli-common-dev, which is unavailable on mips64el)
Your message dated Thu, 26 Mar 2020 18:42:04 + with message-id and subject line Bug#954992: fixed in gdcm 3.0.5-1.1 has caused the Debian Bug report #954992, regarding gdcm: b-dep on cli-common-dev, which is unavailable on mips64el 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.) -- 954992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:gdcm version: 3.0.5-1 severity: serious tags: ftbfs Hi, The latest upload of gdcm to unstable cannot be built on mips64el: https://buildd.debian.org/status/package.php?p=gdcm It build-depends on cli-common-dev, which depends on mono-utils, which is unavailable on mips64el. Please note that this blocks the python3-defaults transition. Cheers, Ivo --- End Message --- --- Begin Message --- Source: gdcm Source-Version: 3.0.5-1.1 Done: Ivo De Decker We believe that the bug you reported is fixed in the latest version of gdcm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ivo De Decker (supplier of updated gdcm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 26 Mar 2020 18:08:36 + Source: gdcm Architecture: source Version: 3.0.5-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Ivo De Decker Closes: 954992 Changes: gdcm (3.0.5-1.1) unstable; urgency=medium . * Non-maintainer upload. * Refresh debian/control to add correct mono arches. This fixes FTBFS on mips64el. Closes: #954992 Checksums-Sha1: 9a8b35400e76d445bd3e8a872515f7da39efd16b 3741 gdcm_3.0.5-1.1.dsc a312d9815622732467904693378554d276fbebfa 22548 gdcm_3.0.5-1.1.debian.tar.xz d2d4fd2a356102e06f8c7e6e777159723d3f0eef 31103 gdcm_3.0.5-1.1_source.buildinfo Checksums-Sha256: 631a19b14da2f74e2b6489ad2335c7f66cf185c8b449e960f7f62f634bfcafe8 3741 gdcm_3.0.5-1.1.dsc 1344402fa1d5a9fe87f0b2b6b95fee6d02fe90a14ce527f5b19c76ac8fa30fd8 22548 gdcm_3.0.5-1.1.debian.tar.xz 952d2c12ae53696b3f4944174e0d053589cada802bc5503d3bb0a9b930af5544 31103 gdcm_3.0.5-1.1_source.buildinfo Files: 3aaa8e56c218924ca7491e1a0f2dced6 3741 libs optional gdcm_3.0.5-1.1.dsc d721221dc67636b055c83d7dde71c314 22548 libs optional gdcm_3.0.5-1.1.debian.tar.xz aa920d58171ad8598448bea1a1fb150c 31103 libs optional gdcm_3.0.5-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEE9GM4QTXwpzdLbkGwrEC7WJcE6vwFAl588W0WHGl2by5kZWRl Y2tlckB1Z2VudC5iZQAKCRCsQLtYlwTq/D9mD/0ceqplmJNqintcgpHffDT8kPlQ ierMBccnMBesBKMzVmFrz/2LAArXR849QruAXiAkDG8wzu/c1wBmX3kc7YHdrWSm 993r0ylwD4ii92SS5VP41iaNtXdxbySQRTt+5gRDPJhq9x5VFskm9sw2StVlk6Wi f+1eQx/xWNu3kk5NY05dSZvMq7X2bzSIfHBL7qEib89409EGBVUEXasmSed1oTE6 zSc8L7sNiian8nEol+Z8WYrepVIWU9wwOWHv1ikUuHdRyM3vxj0mtAN6aiQ9ZTeM 6zkxKz6ewMQ0QIm26mwYujw7zeRXoxS9e6LRsewQIXxo18uAzHf5b9aW9Izoq1/6 UdivzUowLEu0lNxfFa5LQe6UZujyrW5RRehKevNuQwQrWZJLBjKYDW+iDEEpHJrG XUGh1aZd8imnZpcig6MVbbIKcM3Js0kDMN13myWzrWRCurtxmgH607ZzcLTHEC+e YF+DTkfAetGzpNdyux5w46pmE/FpRjvELrAspnUDEIJOm0uEyJvNjUDqBo+RpFFZ H7+9gADlgcC9Il8rmtElex1+X1ETZrTWppc8QQmLKYdG7ZudMosgTIYMkMnh8ewP chDJwAn7mbJAiwoMd7jkxZW65AguUMQ67zKRVSexXGW7F12E0xky9I91b5uFcoag /0ek25UyvYkz9Y2YWw== =X/SE -END PGP SIGNATURE End Message ---
Bug#952016: ruby-graffiti: FTBFS: ERROR: Test "ruby2.7" failed.
Package: src:ruby-graffiti
Followup-For: Bug #952016
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After some digging one issue is in
/tmp/build-area/ruby-graffiti-2.3.1/debian/ruby-graffiti/usr/lib/ruby/vendor_ruby/graffiti/squish.rb:106:in
`upcase!'
Error: [..]: FrozenError: can't modify frozen String: ""
The offending line is
> @order_dir.upcase!
Fixing this leaves just one other failure which is in
/tmp/build-area/ruby-graffiti-2.3.1/debian/ruby-graffiti/usr/lib/ruby/vendor_ruby/graffiti/sql_mapper.rb:832:in
`gsub!'
Error: [..]: FrozenError: can't modify frozen String: ""
> @global_filter.gsub!(/#{Regexp.escape(node)}\b/) do
HTH, Daniel
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl58+AQACgkQS80FZ8KW
0F1ROBAAlL5YtYi+CVAUblsNBCEsrwtopp1s7/iN7mSzKxdVBxuAXQyKxixDKpZd
CyCp14BzLfwDTvbzlBscq8a6jAj3rtIDBNTZHbvMII5PS5Aeuy3vmUTIS90z87/z
uJBfsQ5OrsRsaUFOOY4QFjWXQu7BCLymsVZnUhBlwGP4F3afuxiojgtOPyeDYYtP
23xD8J+vy6Yuz/vFfIs3ygnXG4hdtiB4k9jLf8xRbXiqD3GVclNbhQA4CXo5V2ok
6O30g26F8kyWfRHsh3ktNYDI5ELeN1lPBXIuiFdI16BmEl+WHoHCapooY1an5gN3
XRUXr7/bUiRoKnnU1Btlx3oOAcAlUx2d19mh7kHdEPKzXH6SyvfnOb32BdnM111r
hrsi6Zq80u2jcqHMP4/6CqwCHi5h7QvIf2bYM89VWwKBv3n9ARRPAQKh6k7l1wgo
ou4OQ90I15CO5yfEWmGMD1dNhnmTbIiEOUV0Dpj5UzqHRkggRw0iju4uw2LQ4XCK
/JiYGVIrp08OnSrIvZYhjE1EX1UWJDadO+ItLx7xQf0zXS96SuqTCigPaWEDySrV
G+lhICaQj8Yj9doKFZUTBo4XfQfbDtHkduHBxSJ7fUBtAJdUqSPOwG3QAtMnYV6k
iwmdp4PJhrNFHw7Ou96laIW2EVG7Zvddn9ORQVcNUPIR/Sbh79M=
=w+14
-END PGP SIGNATURE-
Processed: [bts-link] source package src:ghdl
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ghdl > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #952110 (http://bugs.debian.org/952110) > # Bug title: ghdl FTBFS with LLVM 9 > # * https://github.com/ghdl/ghdl/pull/935 > # * remote status changed: (?) -> closed > # * closed upstream > tags 952110 + fixed-upstream Bug #952110 [src:ghdl] ghdl FTBFS with LLVM 9 Bug #952324 [src:ghdl] ghdl: FTBFS: Unhandled version llvm 9.0.1 Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 952110 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #952324 (http://bugs.debian.org/952324) > # Bug title: ghdl: FTBFS: Unhandled version llvm 9.0.1 > # * https://github.com/ghdl/ghdl/pull/935 > # * remote status changed: (?) -> closed > # * closed upstream > tags 952324 + fixed-upstream Bug #952324 [src:ghdl] ghdl: FTBFS: Unhandled version llvm 9.0.1 Bug #952110 [src:ghdl] ghdl FTBFS with LLVM 9 Ignoring request to alter tags of bug #952324 to the same tags previously set Ignoring request to alter tags of bug #952110 to the same tags previously set > usertags 952324 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 952110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952110 952324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:todoman
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:todoman
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was
debian-bts-l...@lists.debian.org).
> # remote status report for #952161 (http://bugs.debian.org/952161)
> # Bug title: todoman: FTBFS: dh_auto_test: error: pybuild --test
> --test-pytest -i python{version} -p "3.8 3.7" returned exit code 13
> # * https://github.com/pimutils/todoman/issues/379
> # * remote status changed: open -> closed
> # * closed upstream
> tags 952161 + fixed-upstream
Bug #952161 [src:todoman] todoman: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.7" returned exit code 13
Added tag(s) fixed-upstream.
> usertags 952161 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 952161 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#952084: marked as done (ruby-twitter-text: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:)
Your message dated Thu, 26 Mar 2020 17:50:51 +
with message-id
and subject line Bug#952084: fixed in ruby-twitter-text 1.14.7+conformance-2
has caused the Debian Bug report #952084,
regarding ruby-twitter-text: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
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.)
--
952084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-twitter-text
Version: 1.14.7+conformance-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error:
>@to_char_a ||= if chars.kind_of?(Enumerable)
> chars.to_a
>else
> char_array = []
> 0.upto(char_length - 1) { |i| char_array <<
> [chars.slice(i)].pack('U') }
> char_array
>
> FrozenError:
>can't modify frozen String: ""
> # /<>/lib/twitter-text/extractor.rb:17:in `to_char_a'
> # /<>/lib/twitter-text/rewriter.rb:5:in `rewrite_entities'
> # /<>/lib/twitter-text/rewriter.rb:57:in `rewrite_urls'
> # /<>/lib/twitter-text/deprecation.rb:11:in `block in
> deprecate'
> # /<>/spec/rewriter_spec.rb:341:in `block (3 levels) in
> '
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/autolinking_spec.rb:22:in `block (5 levels) in (required)>'.
>
> `failure_message_for_should_not` is deprecated. Use
> `failure_message_when_negated` instead. Called from
> /<>/spec/spec_helper.rb:73:in `block in '.
> `failure_message_for_should_not` is deprecated. Use
> `failure_message_when_negated` instead. Called from
> /<>/spec/spec_helper.rb:100:in `block in '.
> `failure_message_for_should_not` is deprecated. Use
> `failure_message_when_negated` instead. Called from
> /<>/spec/spec_helper.rb:125:in `block in '.
>
> `failure_message_for_should` is deprecated. Use `failure_message` instead.
> Called from /<>/spec/spec_helper.rb:65:in `block in (required)>'.
> `failure_message_for_should` is deprecated. Use `failure_message` instead.
> Called from /<>/spec/spec_helper.rb:92:in `block in (required)>'.
> `failure_message_for_should` is deprecated. Use `failure_message` instead.
> Called from /<>/spec/spec_helper.rb:117:in `block in (required)>'.
> Too many uses of deprecated '`failure_message_for_should`'. Pass
> `--deprecation-out` or set `config.deprecation_stream` to a file for full
> output.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 9 deprecation warnings total
>
> Finished in 0.15979 seconds (files took 0.39763 seconds to load)
> 524 examples, 5 failures
>
> Failed examples:
>
> rspec /<>/spec/hithighlighter_spec.rb:50 #
> Twitter::HitHighlighter highlight without links should correctly highlight
> last-word hits
> rspec /<>/spec/hithighlighter_spec.rb:80 #
> Twitter::HitHighlighter highlight with links should fail gracefully with bad
> hits
> rspec /<>/spec/hithighlighter_spec.rb:84 #
> Twitter::HitHighlighter highlight with links should not mess up with touching
> tags
> rspec /<>/spec/rewriter_spec.rb:453 # Twitter::Rewriter rewrite
> urls with a URL ending in allowed punctuation does not consume ending
> punctuation
> rspec /<>/spec/rewriter_spec.rb:463 # Twitter::Rewriter rewrite
> urls with a URL preceded in forbidden characters should be rewritten
>
> Coverage report generated for RSpec to /<>/coverage. / 1180
> LOC (94.15%) covered.
> SimpleCov failed with exit 1
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-twitter-text_1.14.7+conformance-1_unstable.log
A list of current common problems and possible solutions is available at
Bug#954623: marked as done (dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/custom.js is missing)
Your message dated Thu, 26 Mar 2020 17:49:16 + with message-id and subject line Bug#954623: fixed in dask-sphinx-theme 1.3.1-2 has caused the Debian Bug report #954623, regarding dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/custom.js is missing 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.) -- 954623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dask Version: 2.11.0+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with python3,sphinxdoc --buildsystem=pybuild >dh_testroot -O--buildsystem=pybuild >dh_prep -O--buildsystem=pybuild >dh_auto_install -O--buildsystem=pybuild > I: pybuild base:217: /usr/bin/python3.7 setup.py install --root > /<>/debian/python3-dask > running install > running build > running build_py > running egg_info > writing dask.egg-info/PKG-INFO > writing dependency_links to dask.egg-info/dependency_links.txt > writing requirements to dask.egg-info/requires.txt > writing top-level names to dask.egg-info/top_level.txt > reading manifest file 'dask.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > writing manifest file 'dask.egg-info/SOURCES.txt' > UPDATING /<>/.pybuild/cpython3_3.7_dask/build/dask/_version.py > set /<>/.pybuild/cpython3_3.7_dask/build/dask/_version.py to > '2.11.0+dfsg' > running install_lib > creating /<>/debian/python3-dask > creating /<>/debian/python3-dask/usr > creating /<>/debian/python3-dask/usr/lib > creating /<>/debian/python3-dask/usr/lib/python3.7 > creating /<>/debian/python3-dask/usr/lib/python3.7/dist-packages > creating > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > copying /<>/.pybuild/cpython3_3.7_dask/build/dask/cache.py -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > creating > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/diagnostics/profile_visualize.py > -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/diagnostics/profile.py > -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/diagnostics/progress.py > -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/diagnostics/__init__.py > -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics > creating > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics/tests > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/diagnostics/tests/__init__.py > -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics/tests > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/diagnostics/tests/test_progress.py > -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics/tests > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/diagnostics/tests/test_profiler.py > -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/diagnostics/tests > copying /<>/.pybuild/cpython3_3.7_dask/build/dask/distributed.py > -> /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/multiprocessing.py -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > copying /<>/.pybuild/cpython3_3.7_dask/build/dask/callbacks.py > -> /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > copying /<>/.pybuild/cpython3_3.7_dask/build/dask/core.py -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > copying /<>/.pybuild/cpython3_3.7_dask/build/dask/__init__.py -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > copying > /<>/.pybuild/cpython3_3.7_dask/build/dask/compatibility.py -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask > creating > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/bag > copying /<>/.pybuild/cpython3_3.7_dask/build/dask/bag/avro.py -> > /<>/debian/python3-dask/usr/lib/python3.7/dist-packages/dask/bag > copying /<>/.pybuild/cpython3_3.7_dask/build/dask/bag/text.py -> >
Bug#952084: marked as pending in ruby-twitter-text
Control: tag -1 pending Hello, Bug #952084 in ruby-twitter-text 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/ruby-team/ruby-twitter-text/-/commit/c7b546767804f4ca4e000a44d670c523e5b3c596 Add patch to fix FrozenError-caused FTBFS * d/patches/5001-fix-ruby27-frozenerror.patch: Add new patch. - Fix FrozenError issued by Ruby 2.7 (closes: #952084). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/952084
Processed: Bug#952084 marked as pending in ruby-twitter-text
Processing control commands: > tag -1 pending Bug #952084 [src:ruby-twitter-text] ruby-twitter-text: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: Added tag(s) pending. -- 952084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:gubbins: fails to migrate to testing for too long: ftbfs on i386
Processing control commands: > fixed -1 2.4.1-1 Bug #955006 [src:gubbins] src:gubbins: fails to migrate to testing for too long: ftbfs on i386 Marked as fixed in versions gubbins/2.4.1-1. -- 955006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955006: src:gubbins: fails to migrate to testing for too long: ftbfs on i386
Source: gubbins Version: 2.3.5-1 Severity: serious Control: fixed -1 2.4.1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:gubbins in its current version in unstable has been trying to migrate for 64 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=gubbins signature.asc Description: OpenPGP digital signature
Bug#951979: Anything related to recent patch from Ubuntu?
Well I did some more digging.
I believe it's the Python variables which are wrong. Specifically the
${Python_INCLUDE_DIR}
I believe the correct variable is ${Python_INCLUDE_DIRS}
I made a patch, which patches the old patch.
I created a merge request in salsa with the change.
Håvard
Bug#944553: midori deletes my files
Control: severity -1 important On Tue, 18 Feb 2020, Sergio Durigan Junior wrote: > Thanks for the report. > > It's not clear from your description whether tmpa_crtoef.htm is the > only file that triggers this behaviour, or if this happens with any file > when you try opening it with Midori. > > I gave it a quick try with a simple file here and could not reproduce > the issue: Given this and the lack of upstream answer I'm downgrading this bug to important because midori has been removed from testing due to this unreproducible issue! Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS signature.asc Description: PGP signature
Processed: Re: Bug#944553: midori deletes my files
Processing control commands: > severity -1 important Bug #944553 [midori] midori deletes my files Severity set to 'important' from 'grave' -- 944553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952011: marked as done (bitstruct: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" --system=custom "--test-args={interpreter} setup.py test" returned exit code 13)
Your message dated Thu, 26 Mar 2020 16:49:25 +
with message-id
and subject line Bug#952011: fixed in bitstruct 8.9.0-1
has caused the Debian Bug report #952011,
regarding bitstruct: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.8 3.7" --system=custom "--test-args={interpreter}
setup.py test" returned exit code 13
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.)
--
952011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bitstruct
Version: 3.7.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
> I: pybuild base:217: python3.8 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> writing bitstruct.egg-info/PKG-INFO
> writing dependency_links to bitstruct.egg-info/dependency_links.txt
> writing top-level names to bitstruct.egg-info/top_level.txt
> reading manifest file 'bitstruct.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'bitstruct.egg-info/SOURCES.txt'
> running build_ext
> test_bad_float_size (tests.test_bitstruct.BitStructTest)
> Test of bad float size. ... ok
> test_bad_format (tests.test_bitstruct.BitStructTest)
> Test of bad format. ... ok
> test_byte_order (tests.test_bitstruct.BitStructTest)
> Test pack/unpack with byte order information in the format string. ... ok
> test_byte_order_format (tests.test_bitstruct.BitStructTest)
> Test of a format with only byte order informationx. ... ok
> test_byteswap (tests.test_bitstruct.BitStructTest)
> Byte swap. ... ok
> test_calcsize (tests.test_bitstruct.BitStructTest)
> Calculate size. ... ok
> test_compile (tests.test_bitstruct.BitStructTest) ... ok
> test_empty_format (tests.test_bitstruct.BitStructTest)
> Test of empty format type. ... ok
> test_endianness (tests.test_bitstruct.BitStructTest)
> Test pack/unpack with endianness information in the format string. ... ok
> test_pack (tests.test_bitstruct.BitStructTest)
> Pack values. ... FAIL
> test_pack_unpack (tests.test_bitstruct.BitStructTest)
> Pack and unpack values. ... ok
> test_performance_integers (tests.test_bitstruct.BitStructTest)
> Test pack/unpack performance with integers. ... ok
> test_performance_mixed_types (tests.test_bitstruct.BitStructTest)
> Test pack/unpack performance with mixed types. ... ok
> test_signed_integer (tests.test_bitstruct.BitStructTest)
> Pack and unpack signed integer values. ... ok
> test_unpack (tests.test_bitstruct.BitStructTest)
> Unpack values. ... ok
> test_unsigned_integer (tests.test_bitstruct.BitStructTest)
> Pack and unpack unsigned integer values. ... ok
>
> ==
> FAIL: test_pack (tests.test_bitstruct.BitStructTest)
> Pack values.
> --
> Traceback (most recent call last):
> File "/<>/tests/test_bitstruct.py", line 94, in test_pack
> pack('r5', 1.0)
> TypeError: cannot convert 'float' object to bytearray
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/<>/tests/test_bitstruct.py", line 97, in test_pack
> self.assertEqual(
> AssertionError: "cannot convert 'float' object to bytearray" != "'float'
> object is not iterable"
> - cannot convert 'float' object to bytearray
> + 'float' object is not iterable
>
>
> --
> Ran 16 tests in 3.015s
>
> FAILED (failures=1)
> Test failed:
>
> pack time: 0.4917159940014244 s (9.834319880028488e-06 s/pack)
> pack time compiled: 0.19851595500222174 s (3.970319100044435e-06 s/pack)
> unpack time: 0.4506532360028359 s (9.013064720056718e-06 s/unpack)
> unpack time compiled: 0.16778694900131086 s (3.3557389800262172e-06 s/unpack)
>
> pack time: 0.5904734639989329 s (1.1809469279978658e-05 s/pack)
> pack time compiled: 0.2874713269993663 s (5.7494265399873255e-06 s/pack)
> unpack time: 0.5556427190022077 s (1.1112854380044155e-05 s/unpack)
> unpack time compiled: 0.2673477409989573 s (5.346954819979146e-06 s/unpack)
> error:
Processed: closing 952080
Processing commands for cont...@bugs.debian.org: > close 952080 1.9.1-2 Bug #952080 [src:ruby-faker] ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed. Marked as fixed in versions ruby-faker/1.9.1-2. Bug #952080 [src:ruby-faker] ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed. Marked Bug as done > # the bug was closed by ruby-faker (1.9.1-2) > # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952080#19 > # ruby-fakefs later just addressed the same bug by accident > thanks Stopping processing here. Please contact me if you need assistance. -- 952080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955000: azure-cli: Autopkgtest failure in unstable
Package: azure-cli
Version: 2.0.81+ds-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it is the closest one we have.
Now that humanfriendly is fixed to provide the missing files, azure-cli
has what looks like a real test failure [1]. Here's the relevant log
extract:
=== FAILURES ===
__ TestProgress.test_progress_indicator_indet_stdview __
self =
def test_progress_indicator_indet_stdview(self):
# tests the indeterminate progress standardout view
outstream = MockOutstream()
view = progress.IndeterminateStandardOut(out=outstream)
view.write({})
self.assertEqual(view.spinner.label, 'In Progress')
before = view.spinner.total
view.write({})
after = view.spinner.total
> self.assertTrue(after >= before)
E TypeError: '>=' not supported between instances of 'NoneType' and
'NoneType'
../autopkgtest-lxc.r8vnoncs/downtmp/autopkgtest_tmp/tests_core/test_progress.py:63:
TypeError
Scott K
[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/a/azure-cli/4686987/log.gz
Bug#952080: closing 952080
close 952080 1.9.1-2 # the bug was closed by ruby-faker (1.9.1-2) # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952080#19 # ruby-fakefs later just addressed the same bug by accident thanks
Bug#952043: marked as done (ruby-ole: FTBFS: ERROR: Test "ruby2.7" failed: /<>/lib/ole/storage/base.rb:352:in `': superclass mismatch for class Header (TypeError))
Your message dated Thu, 26 Mar 2020 16:07:15 +
with message-id
and subject line Bug#952043: fixed in ruby-ole 1.2.11.8-2
has caused the Debian Bug report #952043,
regarding ruby-ole: FTBFS: ERROR: Test "ruby2.7" failed:
/<>/lib/ole/storage/base.rb:352:in `': superclass
mismatch for class Header (TypeError)
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.)
--
952043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ole
Version: 1.2.11.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /<>/lib/ole/storage/base.rb:352:in `': superclass
> mismatch for class Header (TypeError)
> from /<>/lib/ole/storage/base.rb:21:in `'
> from /<>/lib/ole/storage/base.rb:9:in `'
> from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in
> `require'
> from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in
> `require'
> from /<>/lib/ole/storage.rb:1:in `'
> from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in
> `require'
> from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in
> `require'
> from /<>/test/test_filesystem.rb:27:in `'
> from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in
> `require'
> from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in
> `require'
> from -e:1:in `block in '
> from -e:1:in `each'
> from -e:1:in `'
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-ole_1.2.11.8-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-ole
Source-Version: 1.2.11.8-2
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-ole, 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 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-ole package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 26 Mar 2020 16:24:17 +0100
Source: ruby-ole
Architecture: source
Version: 1.2.11.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Daniel Leidert
Closes: 856368 952043
Changes:
ruby-ole (1.2.11.8-2) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Use secure URI in debian/watch.
* Bump debhelper from old 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
.
[ Daniel Leidert ]
* d/control: Add Testsuite and Rules-Requires-Root field.
(Uploaders): Remove Ryan Niebur (closes: #856368). Thanks for your work.
(Standards-Version): Bump to 4.5.0.
(Depends): Use ${ruby:Depends} and remove interpreter.
* d/copyright (Copyright): Add team.
* d/ruby-test-files.yaml: Replace file by d/ruby-tests.rake.
* d/ruby-tests.rake: Add new rake test file (closes: #952043).
* d/watch: Use github release page as source.
* d/patches/*: Remove unused patches and empty series file.
* d/upstream/metadata: Add YAML frontmatter, Archive and Changelog fields.
Checksums-Sha1:
57e310d7a7c692e92c5a11f9b8c20ee51e14d9c4 2056 ruby-ole_1.2.11.8-2.dsc
312e3ae701f5b8e3d43d969d0f8bf16dceeabe89 4692 ruby-ole_1.2.11.8-2.debian.tar.xz
b39b45e5e5a97e7227ca7d432bb3ab7255c01e07
Bug#954999: eclipse-titan still encodes an upper dependency on gcc
Package: eclipse-titan Version: 6.6.1-1 Severity: serious Tags sid bullseye eclipse-titan still encodes an upper dependency on gcc. The changelog says this is fixed upstream, nevertheless the package still has this dependency. Plus this dependency is bogus. The gcc-9 package changed to 9.3, and eclipse-titan still seems to work. So an upper dependency on the gcc dependency package doesn't make sene.
Bug#952043: ruby-ole: FTBFS: ERROR: Test "ruby2.7" failed: /<>/lib/ole/storage/base.rb:352:in `': superclass mismatch for class Header (TypeError)
Package: src:ruby-ole Followup-For: Bug #952043 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The issue seems to be that every test file prepends lib/ to the LOAD_PATH leading to conflicting/duplicate definitions. Changing from d/ruby-test-files.yaml to d/ruby-tests.rake fixes the issue. Otherwise removing the lines, where lib/ is prepended, works too. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl58yRIACgkQS80FZ8KW 0F0ZUQ/9GBHmh9JR0DsVSALUdAvfubfFvXpv1iooy1yVJqH+JDWRr2bxCqXKTWak vnE/eoOzkg1MOMxbelD+8yTb5yA+HxGVasVuGz0xU9eCzpEXcaPelFO8o7ha3wZH /VzWDUEaL0nbouTFzdFskbwxNwWgcNsLtXJIWuFiqOc705JEuPKXXZfeWa7mS4tZ DK7ys4wqGqTwn5QvZE1b106YudJYGwu+BoH/wu1qDle/IYeHh++yS3VS37QClStm IrBpBYGD7mF8jYxMwa995JR14Uf1A0Gb7GZ96xX2NWQP+8uaP2wnAtOZNHSJFJQL 7/zulVEpmZ3+jzu7f1/W3+huZQvpTNjUKaUvyCaw549DuKm7o5O56zUx4AGfBu4a MQU8ONGzBz9UJ6H6v4fF6rA1AZLbJ+r4nTJCE2Eyj2aGUcT533F8WfFf4CXCeWQs jKTfHe5RCr3+hZqpwQIpj5aqouTc0lgGKV9jNZNrKLYECgY9mMP3teUILnJs/l0I bYC7q72f2F3UbZ8YmCouFZGSh+9BmlW5V3gwxMSaaP2BSkrbGP1QgCQ4wQdkSf9n rp3RdXjC+9sk+W0+qNrYzvC8qvpvye9NY0nezl4Ogy5nLA41Lpp986a4NcDyBtTp quCCAodg6nLDVNy9s96aj1oAxuoyK3uURSjNiiqWc6ZOld/cJhI= =4GZO -END PGP SIGNATURE-
Bug#951688: marked as done (src:aspell-ta: fails to migrate to testing for too long)
Your message dated Thu, 26 Mar 2020 15:04:21 + with message-id and subject line Bug#951688: fixed in aspell-ta 20040424-1-2.1 has caused the Debian Bug report #951688, regarding src:aspell-ta: fails to migrate to testing for too long 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.) -- 951688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aspell-ta Version: 20040424-1-1 Severity: serious Control: fixed -1 20040424-1-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:aspell-ta in its current version in unstable has been trying to migrate for 362 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: aspell-ta Source-Version: 20040424-1-2.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of aspell-ta, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated aspell-ta package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 12 Mar 2020 13:52:58 +0100 Source: aspell-ta Architecture: source Version: 20040424-1-2.1 Distribution: unstable Urgency: medium Maintainer: Debian-IN Team Changed-By: Paul Gevers Closes: 951688 Changes: aspell-ta (20040424-1-2.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #951688) Checksums-Sha1: 517456d612c7d07f1058eb2ee3eebd60cec581bc 1936 aspell-ta_20040424-1-2.1.dsc 1b5f0acfca1713c983087dd3d1c8643d593f7e95 3412 aspell-ta_20040424-1-2.1.debian.tar.xz Checksums-Sha256: e9bab7c23e6ef6ea48e8ca72b6748f5353e18543d02ebcde6ffc33ea045704ef 1936 aspell-ta_20040424-1-2.1.dsc 232fa64be45f3f75e2c85abe033c6f28526d5cb49fd62b733a7b13b4e1cc40c6 3412 aspell-ta_20040424-1-2.1.debian.tar.xz Files: ee57605a91033f0adab31acebf80746e 1936 localization optional aspell-ta_20040424-1-2.1.dsc e6d9c0511c6605e20c0c883ec9b11f9b 3412 localization optional aspell-ta_20040424-1-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl5qMNEACgkQnFyZ6wW9 dQqR5wf/V9Z7qcF/+YHjvA3jNElkM+ujGPy3RdYiTeG92R4/I6Zj/0UrrWXtTIkh vjm9iqjYXii5yZUND+d6VYXk5jG1jT6xPRbSZ54r/tCC0q4prXsKEoBxYfH6qpX+ QaczQk8IA+0VRaxnpwlxpO1Akf81yV3xQ0rIK7cNnQ+CHGguFX0QwZc2bexW4oIA qgHk3dwQTccOzM1T3LHlviq1kF9QJ9vQuXluGoDN9Ui2rAQ9kpBYRufOa3+8JCqB SxeCSS5pLKBQRrFvAZsydLBA4A88xEXKxeeW5ti+F8zmDn7+0N/5RjonEoFVamgP arbdOvk+8fht5vSAC5dNWbqtFwSc2A== =tF5L -END PGP SIGNATURE End Message ---
Bug#951945: marked as done (cramfsswap: FTBFS: cramfsswap.c:348: undefined reference to `crc32')
Your message dated Thu, 26 Mar 2020 14:46:33 + with message-id and subject line Bug#951945: fixed in cramfsswap 1.4.1-1.2 has caused the Debian Bug report #951945, regarding cramfsswap: FTBFS: cramfsswap.c:348: undefined reference to `crc32' 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.) -- 951945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cramfsswap Version: 1.4.1-1.1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/cc4uCS9T.o: in function `main': > /<>/cramfsswap.c:348: undefined reference to `crc32' > /usr/bin/ld: /<>/cramfsswap.c:350: undefined reference to `crc32' > /usr/bin/ld: /<>/cramfsswap.c:350: undefined reference to `crc32' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/cramfsswap_1.4.1-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: cramfsswap Source-Version: 1.4.1-1.2 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of cramfsswap, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated cramfsswap 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: Fri, 20 Mar 2020 20:30:45 +0100 Source: cramfsswap Architecture: source Version: 1.4.1-1.2 Distribution: unstable Urgency: medium Maintainer: Juliane Holzt Changed-By: Håvard Flaget Aasen Closes: 871410 951945 Changes: cramfsswap (1.4.1-1.2) unstable; urgency=medium . * Non-maintainer upload. * Reorder library in Makefile closes: #951945 * Fix FTCBFS: closes: #871410 - Let dh_auto_build pass cross compilers to make - Make compiler substitutable in Makefile Patch by Helmut Grohne Checksums-Sha1: 90db98bc07a238f1d1df93805ac7c005a7d7100b 1424 cramfsswap_1.4.1-1.2.dsc 751497b54b0da07eb79ba8afb6bbd587cb6dba00 12587 cramfsswap_1.4.1-1.2.tar.gz c91297cf3de0b41cff2d94bebbb2fee95ece99db 5335 cramfsswap_1.4.1-1.2_source.buildinfo Checksums-Sha256: c79e5dc4653b09562bcb3915f0b7dabcbe48209953b4f945adc9c41ee571e10f 1424 cramfsswap_1.4.1-1.2.dsc df7531c89b37dc4aba126c446f84b764fe3515296c77993057d03ab5e0cd8410 12587 cramfsswap_1.4.1-1.2.tar.gz 0932b283e07f0d10e2df42f9313fb0f9b505cba2c8bfbcd87089cad8ad14a06c 5335 cramfsswap_1.4.1-1.2_source.buildinfo Files: ff0c31d29ec64a19ae7fc6c27e7f48ac 1424 utils extra cramfsswap_1.4.1-1.2.dsc 9e4a3431112a0aaa6ec36daa7f4b3320 12587 utils extra cramfsswap_1.4.1-1.2.tar.gz fa315838368f5cb2fdd9f0389ebf5d2e 5335 utils extra cramfsswap_1.4.1-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl58t8UACgkQweDZLphv fH4vXw//XpViRXI5hB8qz1WEvkbqCoFvRG3bbcaqbzUbEZY0nJOsOgffNSqxCc2v oJEgWb1YJjloR015pQyBvdyPD3Zzx5U8wSh/FlQ7TBbzCw1cgOlVXZ1XegmeetJz aKBdRLlfsp8mM2WLwBShKSwfamQ1uH5HyEEeT/88vRcsQCLwA7EmJ9R9JRBiAutJ w29oiJEgxOc8E8BZenYLy0rkimyvxawrXHpJaHONZHOhEjGvLcj+4GVyvbczFRSD lqFbksijwImyadyiBuhUbNYtrij7rAIh9TPecxe+R1BCeYhp7MQXPB+21RVgA5ek cc7iv+ppKwQS2uON87o1IsCIr6m7C4W5WmIQ3xLI42AktorbzQ39ySGsTXyTsQlV chfmRlz9pO/NtuXnEVRGsC4ePNT9YvOhxqhzAHQHHZuqQMxjytOlIspsyCEfEyv5 OWCfEynq4c9+kfIU9JQ7cnY6pFQeUTnUWfycBCNjWzKP6zV7CfBpfGtyDfRmR21a PaPtedfkEuJ1rQ+4TCKmK8ok3rJNkNaBiG7HjZy1x1k7gvQrJ3kzRAyK4IqbLMs4 ZVgWEb8MnYGOFDBzFSTspwDWIPzzUwzQPFQLlFE/jQvoh2Wh2GzkscPdPhCIdnmr FJoLo1/0DWiVZkcFujuxxRynbFdbVia+GLYZEA7wGOlsGWfpyuU= =BjxR -END PGP SIGNATURE End Message ---
Processed: Re: Bug#952628: hepmc3: FTBFS: Feature.h:296:69: internal compiler error: in get_fns, at cp/tree.c:2455
Processing control commands: > reassign -1 gcc-9 9.2.1-28 Bug #952628 [src:hepmc3] hepmc3: FTBFS: Feature.h:296:69: internal compiler error: in get_fns, at cp/tree.c:2455 Bug reassigned from package 'src:hepmc3' to 'gcc-9'. No longer marked as found in versions hepmc3/3.1.2-2. Ignoring request to alter fixed versions of bug #952628 to the same values previously set Bug #952628 [gcc-9] hepmc3: FTBFS: Feature.h:296:69: internal compiler error: in get_fns, at cp/tree.c:2455 Marked as found in versions gcc-9/9.2.1-28. > affects -1 src:hepmc3 Bug #952628 [gcc-9] hepmc3: FTBFS: Feature.h:296:69: internal compiler error: in get_fns, at cp/tree.c:2455 Added indication that 952628 affects src:hepmc3 -- 952628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952628: hepmc3: FTBFS: Feature.h:296:69: internal compiler error: in get_fns, at cp/tree.c:2455
Control: reassign -1 gcc-9 9.2.1-28 Control: affects -1 src:hepmc3 Looks like a gcc regression somewhere after 9.2.1-24 and no later than 9.2.1-28: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hepmc3.html cu Adrian
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 954992 sid bullseye Bug #954992 [src:gdcm] gdcm: b-dep on cli-common-dev, which is unavailable on mips64el Added tag(s) sid and bullseye. > user debian-pyt...@lists.debian.org Setting user to debian-pyt...@lists.debian.org (was ma...@debian.org). > usertags 954992 python3.8 There were no usertags set. Usertags are now: python3.8. > End of message, stopping processing here. Please contact me if you need assistance. -- 954992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954992: Info received (Bug#954992: gdcm: b-dep on cli-common-dev, which is unavailable on mips64el)
Bug introduced during clean-up: * https://salsa.debian.org/med-team/gdcm/-/commit/13759c10cd9b560f12c454e05dd8d5e6fa133420
Bug#954685: marked as done (node-rollup-plugin-babel: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)
Your message dated Thu, 26 Mar 2020 13:04:30 + with message-id and subject line Bug#954685: fixed in node-rollup-plugin-babel 3.0.7-1 has caused the Debian Bug report #954685, regarding node-rollup-plugin-babel: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 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.) -- 954685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-rollup-plugin-babel Version: 3.0.3-7 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-rollup-plugin-babel > dpkg-buildpackage: info: source version 3.0.3-7 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Bastien Roucariès > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with nodejs >dh_auto_clean --buildsystem=nodejs > rm -rf ./node_modules/.cache >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building node-rollup-plugin-babel using existing > ./node-rollup-plugin-babel_3.0.3.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building node-rollup-plugin-babel in > node-rollup-plugin-babel_3.0.3-7.debian.tar.xz > dpkg-source: info: building node-rollup-plugin-babel in > node-rollup-plugin-babel_3.0.3-7.dsc > debian/rules binary > dh binary --with nodejs >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/./build > cd ./. && sh -e debian/nodejs/./build > > ./src/index.js → dist/rollup-plugin-babel.cjs.js, > dist/rollup-plugin-babel.es.js... > created dist/rollup-plugin-babel.cjs.js, dist/rollup-plugin-babel.es.js in > 83ms >dh_auto_test --buildsystem=nodejs > /bin/sh -e debian/tests/pkg-js/test > > > rollup-plugin-babel > 1) runs code through babel > > > 0 passing (147ms) > 1 failing > > 1) rollup-plugin-babel >runs code through babel: > TypeError: Cannot read property 'indexOf' of undefined > at Context.it (test/test.js:47:19) > > > > dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2020/03/22/node-rollup-plugin-babel_3.0.3-7_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: node-rollup-plugin-babel Source-Version: 3.0.7-1 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-rollup-plugin-babel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-rollup-plugin-babel 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, 24 Mar 2020 11:55:51 +0100 Source: node-rollup-plugin-babel Architecture: source Version: 3.0.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 954685 Changes: node-rollup-plugin-babel (3.0.7-1) unstable; urgency=medium . * Team upload * New upstream version 3.0.7 * Refresh patches * Fix test for rollup 1 (Closes: #954685) * Fix testsuite and remove duplicated autopkgtest require * Fix copyright format
Processed: Re: Bug#954992: gdcm: b-dep on cli-common-dev, which is unavailable on mips64el
Processing control commands: > tags -1 patch confirmed Bug #954992 [src:gdcm] gdcm: b-dep on cli-common-dev, which is unavailable on mips64el Added tag(s) patch and confirmed. -- 954992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954992: gdcm: b-dep on cli-common-dev, which is unavailable on mips64el
Control: tags -1 patch confirmed $ touch debian/control.in $ make -f ./debian/rules debian/control thanks
Bug#954992: gdcm: b-dep on cli-common-dev, which is unavailable on mips64el
package: src:gdcm version: 3.0.5-1 severity: serious tags: ftbfs Hi, The latest upload of gdcm to unstable cannot be built on mips64el: https://buildd.debian.org/status/package.php?p=gdcm It build-depends on cli-common-dev, which depends on mono-utils, which is unavailable on mips64el. Please note that this blocks the python3-defaults transition. Cheers, Ivo
Bug#954589: marked as done (seqan3: FTBFS: two_dimensional_matrix_test.cpp:43:15: error: invalid type ‘__vector(1) int’ as initializer for a vector of type ‘const __vector(1) int’)
Your message dated Thu, 26 Mar 2020 12:34:43 + with message-id and subject line Bug#954589: fixed in seqan3 3.0.1+ds-9 has caused the Debian Bug report #954589, regarding seqan3: FTBFS: two_dimensional_matrix_test.cpp:43:15: error: invalid type ‘__vector(1) int’ as initializer for a vector of type ‘const __vector(1) 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.) -- 954589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seqan3 Version: 3.0.1+ds-8 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -DSEQAN3_HAS_BZIP2=1 -DSEQAN3_HAS_ZLIB=1 > -Ivendor/googletest/googletest/include -I/<>/test/include > -I/<>/include -isystem > /<>/submodules/sdsl-lite/include -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fuse-ld=gold -DNDEBUG -O3 -std=c++2a -Wdate-time > -D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Werror -fconcepts -pthread -MD > -MT > alignment/matrix/detail/CMakeFiles/two_dimensional_matrix_test.dir/two_dimensional_matrix_test.cpp.o > -MF > alignment/matrix/detail/CMakeFiles/two_dimensional_matrix_test.dir/two_dimensional_matrix_test.cpp.o.d > -o > alignment/matrix/detail/CMakeFiles/two_dimensional_matrix_test.dir/two_dimensional_matrix_test.cpp.o > -c > /<>/test/unit/alignment/matrix/detail/two_dimensional_matrix_test.cpp > /<>/test/unit/alignment/matrix/detail/two_dimensional_matrix_test.cpp: > In instantiation of ‘std::vector create_matrix_storage() [with score_type > = __vector(1) int; seqan3::detail::matrix_major_order order = > seqan3::detail::matrix_major_order::row]’: > /usr/include/gtest/internal/gtest-internal.h:460:40: recursively required > from > ‘gtest_suite_iterator_fixture_::compare_geq int, std::allocator<__vector(1) int>, > seqan3::detail::matrix_major_order::column> >::compare_geq()’ > /usr/include/gtest/internal/gtest-internal.h:460:40: required from > ‘testing::Test* testing::internal::TestFactoryImpl::CreateTest() > [with TestClass = > gtest_suite_iterator_fixture_::compare_geq int, std::allocator<__vector(1) int>, > seqan3::detail::matrix_major_order::column> >]’ > /usr/include/gtest/internal/gtest-internal.h:460:9: required from here > /<>/test/unit/alignment/matrix/detail/two_dimensional_matrix_test.cpp:43:15: > error: invalid type ‘__vector(1) int’ as initializer for a vector of type > ‘const __vector(1) int’ >43 | storage_t row_wise > | ^~~~ > /<>/test/unit/alignment/matrix/detail/two_dimensional_matrix_test.cpp:50:15: > error: invalid type ‘__vector(1) int’ as initializer for a vector of type > ‘const __vector(1) int’ >50 | storage_t column_wise > | ^~~ > /<>/test/unit/alignment/matrix/detail/two_dimensional_matrix_test.cpp: > In instantiation of ‘std::vector create_matrix_storage() [with score_type > = __vector(1) int; seqan3::detail::matrix_major_order order = > seqan3::detail::matrix_major_order::column]’: > /usr/include/gtest/internal/gtest-internal.h:460:40: recursively required > from > ‘gtest_suite_iterator_fixture_::compare_geq int, std::allocator<__vector(1) int>, > seqan3::detail::matrix_major_order::column> >::compare_geq()’ > /usr/include/gtest/internal/gtest-internal.h:460:40: required from > ‘testing::Test* testing::internal::TestFactoryImpl::CreateTest() > [with TestClass = > gtest_suite_iterator_fixture_::compare_geq int, std::allocator<__vector(1) int>, > seqan3::detail::matrix_major_order::column> >]’ > /usr/include/gtest/internal/gtest-internal.h:460:9: required from here > /<>/test/unit/alignment/matrix/detail/two_dimensional_matrix_test.cpp:43:15: > error: invalid type ‘__vector(1) int’ as initializer for a vector of type > ‘const __vector(1) int’ >43 | storage_t row_wise > | ^~~~ > /<>/test/unit/alignment/matrix/detail/two_dimensional_matrix_test.cpp:50:15: > error: invalid type ‘__vector(1) int’ as initializer for a vector of type > ‘const __vector(1) int’ >50 | storage_t column_wise > | ^~~ > [67/502] : && /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -fuse-ld=gold > -DNDEBUG -O3 -std=c++2a -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro >
Bug#942633: marked as done (gitlab ssh access broken with protobuf 3.10)
Your message dated Thu, 26 Mar 2020 12:20:44 +
with message-id
and subject line Bug#942633: fixed in gitlab 12.8.6-1
has caused the Debian Bug report #942633,
regarding gitlab ssh access broken with protobuf 3.10
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.)
--
942633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 12.1.14-1
Severity: important
Dear Maintainer,
During the installation of the package, this warning is displayed:
GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... FAIL. Please update
gitlab-shell to 9.3.0 from 9.1.0
But currently the latest version of gitlab-shell available in
experimental is 9.1.0.
It is not possible anymore to interact with the repository through ssh:
$ git fetch
gitaly-upload-pack: fatal: error: %v
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$
Server-side, this error is displayed in gitlab-shell logs:
time="2019-10-19T11:04:07+02:00" level=info msg="finished HTTP request"
duration=0.014533625 gitaly_embedded=false method=POST pid=426
url="http://localhost:8080/api/v4/internal/allowed;
time="2019-10-19T11:04:07+02:00" level=info msg="executing git command"
command="gitaly-upload-pack unix:/run/gitlab/sockets/private/gitaly.socket
{\"repository\":{},\"gl_repository\":\"project-2\",\"gl_project_path\":\"romain/weboob\",\"gl_id\":\"key-3\",\"gl_username\":\"romain\",\"git_config_options\":[],\"git_protocol\":null}"
pid=426 user="user with id key-3"
time="2019-10-19T11:04:07+02:00" level=error msg="error: %v" error="rpc error:
code = InvalidArgument desc = Storage can not be found by name ''" pid=426
I don't know if the two issues are related, but there is a good chance.
The solution would be to package gitlab-shell 9.3.0 in experimental.
Best regards,
Romain
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gitlab depends on:
ii asciidoctor 2.0.10-2
ii bc 1.07.1-2+b2
ii bundler 1.17.3-3
ii bzip2 1.0.8-2
ii dbconfig-pgsql 2.0.13
ii debconf [debconf-2.0] 1.5.73
ii gitlab-common 12.1.14-1
ii gitlab-workhorse8.5.2+debian-1
ii libjs-bootstrap4 [node-bootstrap] 4.3.1+dfsg2-1
ii libjs-pdf 1.5.188+dfsg-1
ii libjs-popper.js [node-popper.js]1.14.6+ds2-2
ii libjs-uglify2.8.29-6
ii lsb-base11.1.0
ii nginx 1.16.1-2
ii nginx-extras [nginx]1.16.1-2
ii node-autosize 4.0.2~dfsg1-3
ii node-axios 0.19.0+dfsg-2
ii node-brace-expansion1.1.8-1
ii node-cache-loader 2.0.1-2
ii node-chart.js 2.7.3+dfsg-5
ii node-core-js2.4.1-2
ii node-css-loader 1.0.1-1
ii node-d3 4.13.0-10
ii node-d3-array 1.2.4-2
ii node-d3-axis1.0.12-2
ii node-d3-brush 1.0.6-3
ii node-d3-ease1.0.5-2
ii node-d3-scale 1.0.7-6
ii node-d3-selection 1.4.0-5
ii node-d3-shape 1.3.5-2
ii node-d3-time1.0.11-3
ii node-d3-time-format
Processed: notfound 952693 in dbusada/0.5.0-3
Processing commands for cont...@bugs.debian.org:
> notfound 952693 dbusada/0.5.0-3
Bug #952693 {Done: Nicolas Boulenguez }
[src:dbusada,src:ahven] dbusada: unbuildable in unstable: requires experimental
libahven
No longer marked as found in versions dbusada/0.5.0-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#948974: marked as done (logging-tree ftbfs, failing tests)
Your message dated Thu, 26 Mar 2020 11:22:44 +
with message-id
and subject line Bug#948974: fixed in logging-tree 1.8.1-0.1
has caused the Debian Bug report #948974,
regarding logging-tree ftbfs, failing tests
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.)
--
948974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:logging-tree
Version: 1.8-1
Severity: serious
Tags: sid bullseye
logging-tree ftbfs, failing tests:
[...]
dh_auto_test -O--buildsystem=pybuild
pybuild --test -i python{version} -p "3.8 3.7"
I: pybuild base:217: cd
/<>/.pybuild/cpython3_3.8_logging_tree/build; python3.8 -m unittest
discover -v
test_2_dot_5_handlers (logging_tree.tests.test_format.FormatTests) ... FAIL
test_2_dot_6_handlers (logging_tree.tests.test_format.FormatTests) ... ok
test_fancy_tree (logging_tree.tests.test_format.FormatTests) ... ok
test_formatter_that_is_not_a_Formatter_instance
(logging_tree.tests.test_format.FormatTests) ... ok
test_formatter_with_no_fmt_attributes
(logging_tree.tests.test_format.FormatTests) ... ok
test_handler_with_parent_attribute_that_is_none
(logging_tree.tests.test_format.FormatTests) ... ok
test_handler_with_wrong_parent_attribute
(logging_tree.tests.test_format.FormatTests) ... ok
test_most_handlers (logging_tree.tests.test_format.FormatTests) ... ok
test_nested_handlers (logging_tree.tests.test_format.FormatTests) ... ok
test_printout (logging_tree.tests.test_format.FormatTests) ... ok
test_simple_tree (logging_tree.tests.test_format.FormatTests) ... ok
test_default_tree (logging_tree.tests.test_node.NodeTests) ... ok
test_one_level_tree (logging_tree.tests.test_node.NodeTests) ... ok
test_two_level_tree (logging_tree.tests.test_node.NodeTests) ... ok
test_two_level_tree_with_placeholder (logging_tree.tests.test_node.NodeTests)
... ok
==
FAIL: test_2_dot_5_handlers (logging_tree.tests.test_format.FormatTests)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests/test_format.py",
line 152, in test_2_dot_5_handlers
self.assertEqual(build_description(), '''\
AssertionError: '<--"[102 chars]t=0\n |\n o<--"asyncio"\n | Level
NOTS[147 chars]NG\n' != '<--"[102 chars]t=0\n'
<--""
Level WARNING
Handler TimedRotatingFile '/bar/two.txt' when='H' interval=3600
backupCount=0
-|
-o<--"asyncio"
-| Level NOTSET so inherits level WARNING
-|
-o<--[concurrent]
-|
-o<--"concurrent.futures"
-Level NOTSET so inherits level WARNING
--
Ran 15 tests in 0.022s
FAILED (failures=1)
E: pybuild pybuild:342: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.8_logging_tree/build; python3.8 -m unittest
discover -v
dh_auto_test: pybuild --test -i python{version} -p "3.8 3.7" returned exit code
13
--- End Message ---
--- Begin Message ---
Source: logging-tree
Source-Version: 1.8.1-0.1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
logging-tree, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated logging-tree package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 12 Mar 2020 11:47:32 +0200
Source: logging-tree
Architecture: source
Version: 1.8.1-0.1
Distribution: unstable
Urgency: low
Maintainer: Federico Ceratto
Changed-By: Adrian Bunk
Closes: 948974
Changes:
logging-tree (1.8.1-0.1) unstable; urgency=low
.
* Non-maintainer upload.
* New upstream release.
- Fixes tests with Python 3.8. (Closes: #948974)
Checksums-Sha1:
fe7d3162937365d2a25648449e13ab262ac35cbd 1960 logging-tree_1.8.1-0.1.dsc
ba57ebfac6f340a3fb5091bbafb6269c24e979a0 8500 logging-tree_1.8.1.orig.tar.gz
0d4e890a9bb0bdea57f608324a9fd72280356bd0 2052
Bug#954502: marked as done (newsboat: FTBFS: unsatisfiable build-dependencies: librust-regex-1-dev librust-gettext-rs-0.4-dev)
Your message dated Thu, 26 Mar 2020 11:56:45 +0100 with message-id <20200326105645.ga6...@tsipinakis.com> and subject line Re: Bug#954502: newsboat: FTBFS: unsatisfiable build-dependencies: librust-regex-1-dev librust-gettext-rs-0.4-dev has caused the Debian Bug report #954502, regarding newsboat: FTBFS: unsatisfiable build-dependencies: librust-regex-1-dev librust-gettext-rs-0.4-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: newsboat Version: 2.18-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), libncursesw5-dev, libxml2-dev, > libstfl-dev, libsqlite3-dev, perl, pkg-config, libcurl4-gnutls-dev, > libjson-c-dev, asciidoc, libxml2-utils, xsltproc, docbook-xml, docbook-xsl, > cargo, librust-chrono-0.4-dev, librust-time-0.1-dev, librust-rand-0.7-dev, > librust-once-cell-1+parking-lot-dev, librust-regex-1-dev, librust-url-2-dev, > librust-dirs-2-dev, librust-xdg-2-dev, librust-backtrace-0.3-dev, > librust-backtrace-sys-0.1-dev, librust-unicode-width-0.1-dev, > librust-nom-4-dev, librust-unicode-segmentation-1-dev, > librust-curl-sys-0.4+ssl-dev, librust-libc-0.2-dev, > librust-gettext-rs-0.4-dev, librust-natord-1-dev, librust-clap-2-dev, > librust-gettext-sys-0.19-dev, librust-tempfile-3-dev, > librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-fork-dev, > librust-proptest-0.9+timeout-dev, librust-percent-encoding-2-dev, > librust-section-testing-0.0.4-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), libncursesw5-dev, > libxml2-dev, libstfl-dev, libsqlite3-dev, perl, pkg-config, > libcurl4-gnutls-dev, libjson-c-dev, asciidoc, libxml2-utils, xsltproc, > docbook-xml, docbook-xsl, cargo, librust-chrono-0.4-dev, > librust-time-0.1-dev, librust-rand-0.7-dev, > librust-once-cell-1+parking-lot-dev, librust-regex-1-dev, librust-url-2-dev, > librust-dirs-2-dev, librust-xdg-2-dev, librust-backtrace-0.3-dev, > librust-backtrace-sys-0.1-dev, librust-unicode-width-0.1-dev, > librust-nom-4-dev, librust-unicode-segmentation-1-dev, > librust-curl-sys-0.4+ssl-dev, librust-libc-0.2-dev, > librust-gettext-rs-0.4-dev, librust-natord-1-dev, librust-clap-2-dev, > librust-gettext-sys-0.19-dev, librust-tempfile-3-dev, > librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-fork-dev, > librust-proptest-0.9+timeout-dev, librust-percent-encoding-2-dev, > librust-section-testing-0.0.4-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [672 B] > Get:5 copy:/<>/apt_archive ./ Packages [759 B] > Fetched 2394 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: > sbuild-build-depends-main-dummy : Depends: librust-regex-1-dev >Depends: librust-gettext-rs-0.4-dev > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/03/21/newsboat_2.18-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
Processed: tagging 954712, tagging 947523, tagging 947534, tagging 947541, tagging 947542, tagging 947530 ...
Processing commands for cont...@bugs.debian.org:
> tags 954712 - sid bullseye
Bug #954712 [src:consul] consul: FTBFS: dh_auto_test: error: cd _build && go
test -vet=off -v -p 4 -short -failfast -timeout 8m github.com/hashicorp/consul
[...] github.com/hashicorp/consul/version returned exit code 1
Removed tag(s) bullseye and sid.
> tags 947523 + sid bullseye
Bug #947523 [src:gconf-editor] gconf-editor: build-depends on deprecated
gnome-doc-utils
Added tag(s) sid and bullseye.
> tags 947534 + sid bullseye
Bug #947534 [src:mp3splt] mp3splt: build-depends on deprecated gnome-doc-utils
Added tag(s) sid and bullseye.
> tags 947541 + sid bullseye
Bug #947541 [src:viking] viking: build-depends on deprecated gnome-doc-utils
Added tag(s) bullseye and sid.
> tags 947542 + sid bullseye
Bug #947542 [src:xiphos] xiphos: build-depends on deprecated gnome-doc-utils
Added tag(s) sid and bullseye.
> tags 947530 + sid bullseye
Bug #947530 [src:gnome-system-tools] gnome-system-tools: build-depends on
deprecated gnome-doc-utils
Added tag(s) sid and bullseye.
> tags 947521 + sid bullseye
Bug #947521 [src:florence] florence: build-depends on deprecated gnome-doc-utils
Added tag(s) bullseye and sid.
> tags 954638 - sid bullseye
Bug #954638 {Done: Nilesh Patra }
[src:golang-github-mattn-go-runewidth] golang-github-mattn-go-runewidth: FTBFS:
dh_auto_test: error: cd _build && go test -vet=off -v -p 4
github.com/mattn/go-runewidth returned exit code 1
Removed tag(s) bullseye and sid.
> found 954954 10-20200312-2
Bug #954954 [libstdc++6] libstdc++6: symbols file on armel incomplete
Marked as found in versions gcc-10/10-20200312-2.
> found 954948 20200103-3
Bug #954948 {Done: Jonas Smedegaard } [fonts-noto] [d-i bullseye
alpha2] Sinhala font missing
Marked as found in versions fonts-noto/20200103-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947521
947523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947523
947530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947530
947534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947534
947541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947541
947542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947542
954638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954638
954712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954712
954948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954948
954954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#953966: buildbot: autopkgtest failure with Python 3.8 as default
Control: severity -1 important The autopkgtests seem to work now: https://ci.debian.net/user/britney/jobs?package=buildbot[]=testing[]=amd64 The bug may have been fixed by: python3-defaults 3.8.2-2 Lets leave it open for a while to see if the tests are stable now. -- Robin
Processed: Re: Bug#953966: buildbot: autopkgtest failure with Python 3.8 as default
Processing control commands: > severity -1 important Bug #953966 [src:buildbot] buildbot: autopkgtest failure with Python 3.8 as default Severity set to 'important' from 'serious' -- 953966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 953897 libncbi-vdb2 2.10.3+dfsg-1 Bug #953897 [src:ncbi-vdb, src:sra-sdk] ncbi-vdb breaks sra-sdk autopkgtest: undefined symbol: vdb_mbedtls_md_setup Bug reassigned from package 'src:ncbi-vdb, src:sra-sdk' to 'libncbi-vdb2'. No longer marked as found in versions sra-sdk/2.9.3+dfsg-1 and ncbi-vdb/2.10.3+dfsg-1. Ignoring request to alter fixed versions of bug #953897 to the same values previously set Bug #953897 [libncbi-vdb2] ncbi-vdb breaks sra-sdk autopkgtest: undefined symbol: vdb_mbedtls_md_setup Marked as found in versions ncbi-vdb/2.10.3+dfsg-1. > reassign 952627 libncbi-vdb2 2.10.3+dfsg-1 Bug #952627 [src:skesa] skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init' Bug reassigned from package 'src:skesa' to 'libncbi-vdb2'. No longer marked as found in versions skesa/2.3.0-2. Ignoring request to alter fixed versions of bug #952627 to the same values previously set Bug #952627 [libncbi-vdb2] skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init' Marked as found in versions ncbi-vdb/2.10.3+dfsg-1. > forcemerge 952627 953897 Bug #952627 [libncbi-vdb2] skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init' Bug #953897 [libncbi-vdb2] ncbi-vdb breaks sra-sdk autopkgtest: undefined symbol: vdb_mbedtls_md_setup Added tag(s) ftbfs. Merged 952627 953897 > retitle 952627 libncbi-vdb2 uses undefined symbols Bug #952627 [libncbi-vdb2] skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init' Bug #953897 [libncbi-vdb2] ncbi-vdb breaks sra-sdk autopkgtest: undefined symbol: vdb_mbedtls_md_setup Changed Bug title to 'libncbi-vdb2 uses undefined symbols' from 'skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init''. Changed Bug title to 'libncbi-vdb2 uses undefined symbols' from 'ncbi-vdb breaks sra-sdk autopkgtest: undefined symbol: vdb_mbedtls_md_setup'. > affects 952627 src:skesa Bug #952627 [libncbi-vdb2] libncbi-vdb2 uses undefined symbols Bug #953897 [libncbi-vdb2] libncbi-vdb2 uses undefined symbols Added indication that 952627 affects src:skesa Added indication that 953897 affects src:skesa > thanks Stopping processing here. Please contact me if you need assistance. -- 952627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952627 953897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 952619 954624
Processing commands for cont...@bugs.debian.org: > forcemerge 952619 954624 Bug #952619 [src:deltachat-core] deltachat-core: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu returned exit code 1 Bug #954624 [src:deltachat-core] deltachat-core: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu returned exit code 1 Merged 952619 954624 > thanks Stopping processing here. Please contact me if you need assistance. -- 952619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952619 954624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#952614: dropwatch: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Processing control commands: > severity -1 important Bug #952614 [src:dropwatch] dropwatch: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Severity set to 'important' from 'serious' -- 952614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952614: dropwatch: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Control: severity -1 important On Wed, Feb 26, 2020 at 05:13:29PM +0100, Lucas Nussbaum wrote: > Source: dropwatch > Version: 1.5.1-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200225 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > This rebuild was done by building only architecture:any binary packages > (binary-arch target of debian/rules). >... > > make[3]: Entering directory '/<>/tests' > > make[4]: Entering directory '/<>/tests' > > E: Build killed with signal TERM after 150 minutes of inactivity >... This never failed on a buildd for a release architecture, which is the usual criteria for FTBFS being RC: https://buildd.debian.org/status/package.php?p=dropwatch The only past failure on a release architecture was on s390x for an unrelated reason (#950525). Reproducible has 100% success: https://tests.reproducible-builds.org/debian/history/dropwatch.html cu Adrian
Processed: tagging 951779
Processing commands for cont...@bugs.debian.org:
> tags 951779 + fixed
Bug #951779 {Done: Gianfranco Costamagna }
[src:pitivi] pitivi: missing libpython link?
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
951779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#954697: marked as done (node-debbundle-insert-module-globals: FTBFS: Error: ENOENT: no such file or directory, open 'buffer')
Your message dated Thu, 26 Mar 2020 08:46:33 + with message-id and subject line Bug#954697: fixed in node-debbundle-insert-module-globals 7.2.0+ds+~1.0.0+~1.2.0+~1.1.3-3 has caused the Debian Bug report #954697, regarding node-debbundle-insert-module-globals: FTBFS: Error: ENOENT: no such file or directory, open 'buffer' 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.) -- 954697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-debbundle-insert-module-globals Version: 7.2.0+ds+~1.0.0+~1.2.0+~1.1.3-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd node-dash-ast && tap -R spec test > > test/index.js > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > 4 passing (831.934ms) > cd node-get-assigned-identifiers && tap -R spec test > > test/index.js > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > 12 passing (501.577ms) > cd node-undeclared-identifiers && tap -R spec test > > test/index.js > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > 23 passing (525.82ms) > NODE_PATH=/usr/share/nodejs:/usr/lib/nodejs tap -R spec test/*.js > > test/always.js > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should not be equal > > ✓ should be equal > > ✓ should not be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > test/global.js > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > test/immediate.js > - test/immediate.js > test/insert.js > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > test/isbuffer.js > > ✓ is a buffer > > ✓ not a buffer (string) > > ✓ not a buffer (object) > > ✓ buffer not required in source > events.js:174 > throw er; // Unhandled 'error' event > ^ > > Error: ENOENT: no such file or directory, open 'buffer' > Emitted 'error' event at: > at ReadStream. (/usr/share/nodejs/module-deps/index.js:405:22) > at ReadStream.emit (events.js:198:13) > at lazyFs.open (internal/fs/streams.js:115:12) > at FSReqWrap.args [as oncomplete] (fs.js:140:20) > > ✓ absolute path not required in source > > 1) test count !== plan > test/return.js > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > test/roots.js > - test/roots.js > test/sourcemap.js > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equivalent > > ✓ should be equal > > ✓ should be equal > > ✓ should be equal > test/subdir.js > > ✓ should be equal > test/unprefix.js > > ✓ should be equal > > ✓ should be equal > > ✓ should be falsy > > 49 passing (6s) > 2 pending > 1 failing > > 1) test/isbuffer.js test count !== plan: > > test count !== plan > + expected - actual > > -5 > +1 > > > > make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1 The full build log is
Bug#952610: marked as done (meson: autopkgtests regressions)
Your message dated Thu, 26 Mar 2020 07:19:23 +
with message-id
and subject line Bug#952610: fixed in meson 0.54.0~rc1-1
has caused the Debian Bug report #952610,
regarding meson: autopkgtests regressions
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.)
--
952610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meson
Version: 0.53.2-1
Severity: serious
Hello, looks like you have an autopkgtest failure left with the new version...
Can you please also consider the following patch to fix some autopkgtest and
include some more test that are now
not run because of rustc/valac not installed in the environment?
(skipifnot is a good workaround in the new release, but since we have tools,
better have a more comprehensive testsuite!)
diff -Nru meson-0.53.2/debian/changelog meson-0.53.2/debian/changelog
--- meson-0.53.2/debian/changelog 2020-02-25 17:02:37.0 +0100
+++ meson-0.53.2/debian/changelog 2020-02-26 12:42:13.0 +0100
@@ -1,3 +1,15 @@
+meson (0.53.2-1ubuntu1) focal; urgency=medium
+
+ [ Stefano Rivera ]
+ * debian/patches/use_python3_tests.patch:
+- Update use_python3_tests.patch to catch one more python binary use.
+
+ [ Rico Tzschichholz ]
+ * debian/tests/control:
+- Explicit depends on rustc and valac, so autopkgtests can pick it up
+
+ -- Rico Tzschichholz Wed, 26 Feb 2020 12:42:13 +0100
+
meson (0.53.2-1) unstable; urgency=medium
* New upstream release. Closes: #950020, #951487
diff -Nru meson-0.53.2/debian/patches/series meson-0.53.2/debian/patches/series
--- meson-0.53.2/debian/patches/series 2020-01-07 20:00:50.0 +0100
+++ meson-0.53.2/debian/patches/series 2020-02-26 12:41:49.0 +0100
@@ -1,2 +1,3 @@
1-disable-openmpi.patch
2-disable-rootdir-test.patch
+use_python3_tests.patch
diff -Nru meson-0.53.2/debian/patches/use_python3_tests.patch
meson-0.53.2/debian/patches/use_python3_tests.patch
--- meson-0.53.2/debian/patches/use_python3_tests.patch 1970-01-01
01:00:00.0 +0100
+++ meson-0.53.2/debian/patches/use_python3_tests.patch 2020-02-26
12:41:49.0 +0100
@@ -0,0 +1,11 @@
+--- a/run_unittests.py
b/run_unittests.py
+@@ -6587,7 +6587,7 @@
+ # remove the build dependency on python2-dev. Keep the tests
+ # but only run them if dev packages are available.
+ raise unittest.SkipTest('Not running Python 2 tests because
dev packages not installed.')
+-self._simple_test('python', 'python')
++self._simple_test('python', 'python2')
+
+ @unittest.skipIf(is_windows(), 'Setting up multiple compilers on windows
is hard')
+ @skip_if_env_set('CC')
diff -Nru meson-0.53.2/debian/tests/control meson-0.53.2/debian/tests/control
--- meson-0.53.2/debian/tests/control 2020-01-22 23:17:22.0 +0100
+++ meson-0.53.2/debian/tests/control 2020-02-26 12:41:49.0 +0100
@@ -5,7 +5,7 @@
Depends: meson, ninja-build, clang
Tests: exhaustive
-Depends: meson, @builddeps@
+Depends: meson, @builddeps@, rustc, valac
Tests: crossbuild
this is the left failure:
Remember to add the correct --libdir arg to Meson invocation.
The Meson build system
Version: 0.53.2
Source dir: /tmp/autopkgtest-lxc.ooct3ila/downtmp/autopkgtest_tmp/testproject
Build dir:
/tmp/autopkgtest-lxc.ooct3ila/downtmp/autopkgtest_tmp/testproject/build
Build type: cross build
Project name: tutorial
Project version: undefined
meson.build:1:0: ERROR: Unknown compiler(s): ['cc', 'gcc', 'clang', 'pgcc',
'icc']
The follow exceptions were encountered:
Running "cc --version" gave "[Errno 2] No such file or directory: 'cc': 'cc'"
Running "gcc --version" gave "[Errno 2] No such file or directory: 'gcc': 'gcc'"
Running "clang --version" gave "[Errno 2] No such file or directory: 'clang':
'clang'"
Running "pgcc --version" gave "[Errno 2] No such file or directory: 'pgcc':
'pgcc'"
Running "icc --version" gave "[Errno 2] No such file or directory: 'icc': 'icc'"
A full log can be found at
/tmp/autopkgtest-lxc.ooct3ila/downtmp/autopkgtest_tmp/testproject/build/meson-logs/meson-log.txt
autopkgtest [03:38:21]: test crossbuild: ---]
autopkgtest [03:38:21]: test crossbuild: - - - - - - - - - - results - - - - -
- - - - -
crossbuild FAIL non-zero exit status 1
autopkgtest [03:38:21]: summary
basicmeson PASS
clangmeson PASS
exhaustive PASS
crossbuild FAIL non-zero exit status 1
thanks
Gianfranco
--- End Message ---
---
Bug#954977: "Daily Limit Exceeded" connection error
Package: evolution Version: 3.36.0-1 Severity: grave I am currently seeing the following error come up in evolution when trying to connect to my gmail accounts. Presumably it is a knock on effect of increased usage brought on by the lock down for COVID-19. Someone needs to get the quota bumped up. filing against evolution; apologies if it should have been against gnome-online-accounts, i was not certain. ``` Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 ```
