Processed: Re: Bug#975488: lammps FTBFS: error: format not a string literal and no format arguments
Processing control commands: > severity -1 normal Bug #975488 [src:lammps] lammps FTBFS: error: format not a string literal and no format arguments Severity set to 'normal' from 'serious' -- 975488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975488: lammps FTBFS: error: format not a string literal and no format arguments
Control: severity -1 normal Per reproducible builds [1], lammps starting building again around 2020-11-30. The recent binNMU for Python 3.9 only was also successful. [1] https://tests.reproducible-builds.org/debian/history/amd64/lammps.html
Processed: Re: nagios-plugins-contrib: diff for NMU version 27.20200511+1+nmu1
Processing commands for cont...@bugs.debian.org: > tags 976218 + patch Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of check_ssl_cert Ignoring request to alter tags of bug #976218 to the same tags previously set > tags 976218 + pending Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of check_ssl_cert Ignoring request to alter tags of bug #976218 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 976218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925818: rocksdb: ftbfs with GCC-9
Hi Paul, On Sun, Dec 6, 2020 at 9:27 PM Paul Gevers wrote: > On Wed, 27 Mar 2019 19:47:52 + Matthias Klose wrote: > > The package fails to build in a test rebuild on at least amd64 with > > gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The > > severity of this report will be raised before the bullseye release, > > so nothing has to be done for the buster release. > > Do you intend to fix this soon in unstable too? The freeze of bullseye > is near and we'd want to have this bug fixed. Yeah, it's a bit confusing why someone tagged this as affecting experimental. I could _not_ confirm that the FTBFS happens there. Currently this goes in three paths. Try to find a patch for the Sid version of RocksDB, file a transition request for the experimental version (this would be the best ATM). Then I've patched and packaged the new upstream version, but as it switches to CMake build system it needs more testing. Cheers, Laszlo/GCS
Bug#976218: nagios-plugins-contrib: diff for NMU version 27.20200511+1+nmu1 (was: Bug#976218: file breaks nagios-plugins-contrib autopkgtest: SSL_CERT UNKNOWN www.debian.org: Unable to fetch a valid c
Control: tags 976218 + patch
Control: tags 976218 + pending
Dear maintainer,
to resolve this issue, I've prepared a NMU for nagios-plugins-contrib
(versioned as 27.20200511+1+nmu1), and uploaded it to DELAYED/5. Please
feel free to tell me if I should delay it longer.
Regards.
Christop
diff -Nru nagios-plugins-contrib-27.20200511+1/debian/changelog
nagios-plugins-contrib-27.20200511+1+nmu1/debian/changelog
--- nagios-plugins-contrib-27.20200511+1/debian/changelog 2020-05-11
17:08:39.0 +0200
+++ nagios-plugins-contrib-27.20200511+1+nmu1/debian/changelog 2020-12-06
21:20:03.0 +0100
@@ -1,3 +1,10 @@
+nagios-plugins-contrib (27.20200511+1+nmu1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Cherry-pick upstream fix for check_ssl_cert. Closes: #976218
+
+ -- Christoph Biedl Sun, 06 Dec 2020
21:20:03 +0100
+
nagios-plugins-contrib (27.20200511+1) unstable; urgency=medium
* [b6d2915] Fixing tests (again)
diff -Nru
nagios-plugins-contrib-27.20200511+1/debian/patches/check_ssl_cert/adjust-for-file-5.39
nagios-plugins-contrib-27.20200511+1+nmu1/debian/patches/check_ssl_cert/adjust-for-file-5.39
---
nagios-plugins-contrib-27.20200511+1/debian/patches/check_ssl_cert/adjust-for-file-5.39
1970-01-01 01:00:00.0 +0100
+++
nagios-plugins-contrib-27.20200511+1+nmu1/debian/patches/check_ssl_cert/adjust-for-file-5.39
2020-12-06 21:20:03.0 +0100
@@ -0,0 +1,20 @@
+Subject: Fixes #212 ("Unable to fetch a valid certificate issuer certificate")
+Origin: v1.119.0
+Upstream-Author: mat...@corti.li
+Date: Wed Jul 1 21:35:12 2020 +0200
+Bug-Debian: https://bugs.debian.org/976218
+
+Root cause: The file(1) program changed the output to "certificate" in
+versio 5.39
+
+--- a/check_ssl_cert/check_ssl_cert_1.98.0/check_ssl_cert
b/check_ssl_cert/check_ssl_cert_1.98.0/check_ssl_cert
+@@ -2450,7 +2450,7 @@
+ # check the result
+ if ! "${FILE_BIN}" "${ISSUER_CERT_TMP}" | grep -E -q ':
(ASCII|PEM)' ; then
+
+-if "${FILE_BIN}" "${ISSUER_CERT_TMP}" | grep -q ': data' ;
then
++if "${FILE_BIN}" "${ISSUER_CERT_TMP}" | grep -E -q
'(data|Certificate)' ; then
+
+ if [ -n "${DEBUG}" ] ; then
+ echo "[DBG] OCSP: converting issuer certificate from
DER to PEM"
diff -Nru nagios-plugins-contrib-27.20200511+1/debian/patches/series
nagios-plugins-contrib-27.20200511+1+nmu1/debian/patches/series
--- nagios-plugins-contrib-27.20200511+1/debian/patches/series 2020-05-11
17:08:39.0 +0200
+++ nagios-plugins-contrib-27.20200511+1+nmu1/debian/patches/series
2020-12-06 21:20:03.0 +0100
@@ -54,3 +54,4 @@
percona-nagios-plugins/python2to3
check_email_delivery/check_smtp_send-hello
dsa/python2to3
+check_ssl_cert/adjust-for-file-5.39
signature.asc
Description: PGP signature
Processed: nagios-plugins-contrib: diff for NMU version 27.20200511+1+nmu1 (was: Bug#976218: file breaks nagios-plugins-contrib autopkgtest: SSL_CERT UNKNOWN www.debian.org: Unable to fetch a valid ce
Processing control commands: > tags 976218 + patch Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of check_ssl_cert Added tag(s) patch. > tags 976218 + pending Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of check_ssl_cert Added tag(s) pending. -- 976218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976490: marked as done (libsis-base-java: FTBFS: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someLink)
Your message dated Mon, 07 Dec 2020 07:05:00 + with message-id and subject line Bug#976490: fixed in libsis-base-java 18.09~pre1+git20180928.45fbd31+dfsg-2 has caused the Debian Bug report #976490, regarding libsis-base-java: FTBFS: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someLink 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.) -- 976490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsis-base-java Version: 18.09~pre1+git20180928.45fbd31+dfsg-1 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -a > mkdir test ; cp -r source/java/ch test ; cp -r sourceTest/java/ch test > jh_build sis-base-test.jar test > warning: [options] bootstrap class path not set in conjunction with -source 7 > 1 warning > test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:362: warning - > invalid usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:401: warning - > invalid usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDArray.java:47: warning - invalid usage > of tag > > test/ch/systemsx/cisd/base/mdarray/MDArray.java:87: warning - invalid usage > of tag > > test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:47: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:87: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:47: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:87: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:47: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:87: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:47: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:87: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:47: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:87: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:47: warning - invalid > usage of tag > > test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:87: warning - invalid > usage of tag > > 16 warnings > LC_ALL=C java -Djava.library.path=source/c/.libs -classpath sis-base-test.jar > ch.systemsx.cisd.base.AllTests > Application: base > Version: UNKNOWN* > Java VM: OpenJDK 64-Bit Server VM (v11.0.9.1+1-post-Debian-1) > CPU Architecture: aarch64 > OS: Linux (v4.19.0-11-arm64) > Test class: NativeDataTests > > Running testIntToByteToInt > Arguments: [0, 0] > Arguments: [0, 1] > Arguments: [0, 2] > Arguments: [0, 3] > Arguments: [1, 0] > Arguments: [1, 1] > Arguments: [1, 2] > Arguments: [1, 3] > Arguments: [2, 0] > Arguments: [2, 1] > Arguments: [2, 2] > Arguments: [2, 3] > Arguments: [3, 0] > Arguments: [3, 1] > Arguments: [3, 2] > Arguments: [3, 3] > Running testIntChangeByteOrderAndBack > Running testShortChangeByteOrderAndBack > Running testCharChangeByteOrderAndBack > Running testLongChangeByteOrderAndBack > Running testFloatChangeByteOrderAndBack > Running testDoubleChangeByteOrderAndBack > Running testLongToByteToLong > Arguments: [0, 0] > Arguments: [0, 1] > Arguments: [0, 2] > Arguments: [0, 3] > Arguments: [1, 0] > Arguments: [1, 1] > Arguments: [1, 2] > Arguments: [1, 3] > Arguments: [2, 0] > Arguments: [2, 1] > Arguments: [2, 2] > Arguments: [2, 3] > Arguments: [3, 0] > Arguments: [3, 1] > Arguments: [3, 2] > Arguments: [3, 3] > Running testShortToByteToShort > Arguments: [0, 0] > Arguments: [0, 1] > Arguments: [0, 2] > Arguments: [0, 3] > Arguments: [1, 0] > Arguments: [1, 1] > Arguments: [1, 2] > Arguments: [1, 3] > Arguments: [2, 0] > Arguments: [2, 1] > Arguments: [2, 2] > Arguments: [2, 3] > Arguments: [3, 0] > Arguments: [3, 1] > Arguments: [3, 2] > Arguments: [3, 3] > Running testCharToByteToChar > Arguments: [0, 0] > Arguments: [0, 1] > Arguments: [0, 2] > Arguments: [0, 3] > Arguments: [1, 0] > Arguments: [1, 1] > Arguments: [1, 2] > Arguments: [1, 3] > Arguments: [2, 0] > Arguments: [2, 1] > Arguments: [2, 2] > Arguments: [2, 3] > Arguments:
Processed: Version tracking for manually closed xenium bug
Processing commands for cont...@bugs.debian.org:
> fixed 976480 0.0.2+ds-2
Bug #976480 {Done: Andreas Tille } [src:xenium] xenium:
FTBFS: utils.hpp:80:4: error: #error "Unsupported compiler"
Marked as fixed in versions xenium/0.0.2+ds-2.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
976480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976658: marked as done (debcargo is broken (and the autopkgtest didn't catch it).)
Your message dated Mon, 07 Dec 2020 05:48:54 + with message-id and subject line Bug#976658: fixed in rust-debcargo 2.4.3-3 has caused the Debian Bug report #976658, regarding debcargo is broken (and the autopkgtest didn't catch it). 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.) -- 976658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debcargo Version: 2.4.3-2+bw Severity: grave After the recent binnmu of debcargo. debcargo update (after deleting the cache) gives. Updating crates.io index Something failed: failed to fetch `https://github.com/rust-lang/crates.io-index` Caused by: invalid version 0 on git_proxy_options; class=Invalid (3) This issue was not caught by the autopkgtest. In order to check this was indeed caused by the libgit2 update (and not by one of the other updates that have happened since the last debcargo build in unstable) I did a test build with libgit2-dev from testing but everything else from unstable. That test build worked fine. I suspect rust-git2/rust-libgit2-sys need to be updated to match the new libgit2. I've got to go now, but I'll try look into this issue some more later tonight. --- End Message --- --- Begin Message --- Source: rust-debcargo Source-Version: 2.4.3-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-debcargo, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-debcargo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Dec 2020 05:21:57 + Source: rust-debcargo Architecture: source Version: 2.4.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 976658 Changes: rust-debcargo (2.4.3-3) unstable; urgency=medium . * Team upload. * Package debcargo 2.4.3 from crates.io using debcargo 2.4.3 * Bump dependency on git2 package, the old version is broken with new libgit2 (Closes: 976658). Checksums-Sha1: 1f9cba056493b5fd2286ebde0afcad3320a1d358 2870 rust-debcargo_2.4.3-3.dsc 47dbfe3f5ce3aabfda4f9839b3e965f67cbc8a09 3452 rust-debcargo_2.4.3-3.debian.tar.xz 04053911197234f18a79ba24b3590c97968dcafd 14555 rust-debcargo_2.4.3-3_source.buildinfo Checksums-Sha256: 9aef86caea7d79fc555dec6499f0ab4e108025c59b53711c38362c9e57e19de0 2870 rust-debcargo_2.4.3-3.dsc 0951c347c27ed8c0b6885e0e7f036740bcd8fe2c2963c717e25986a8808f3f4a 3452 rust-debcargo_2.4.3-3.debian.tar.xz 77455aa9423d832c8021b913f91b434a90c18805d78cd3643de9c377cbc69a54 14555 rust-debcargo_2.4.3-3_source.buildinfo Files: 268c2e266d7d4e3cfbbb1c5772b85c4a 2870 rust optional rust-debcargo_2.4.3-3.dsc d632d7d6db25804976b6d98db9434109 3452 rust optional rust-debcargo_2.4.3-3.debian.tar.xz 0a4fc37bd1aa6d4e1bcb1d65b0bc53d0 14555 rust optional rust-debcargo_2.4.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl/NvBYUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuHLQ//TOlZ8Mn68ETAgpc5Vxbpn36onZP8 8tcF1+Y4WnwHkNcFV7P8R/lVqlGJ4/d0/tj6EbveXCHzQ2FP0F46avjvryrGT6zp YEyohNPtIOuKhgS5q8RZP3AffUxBwRfFU3AIoebQOnLtfs0tOzD7VdTjMmoBW4Yl DfwJgrUV54SDIxCcFd9gw7bWB0LMTPkL/rp1zaju3UMwItsO9cAVtYprwc46XGJG tkiSGjMu07dGaxOqmq+MNRDJr/WIh/89VELPK9bKo/hnqgAW+PGHEaRiD33WFge1 7w1g7CaL5jXfyIOhCzAmp85hMPoYgSCehty99eUrmr2ZUxlS8elyx2xLgimO5tnn W8XBPpEt1TzDpYhZbgaw0KWnKqUaeSV3MT3JJ5+4IQjExEIFrPxlf9EWd+e1ZyX+ xIssSGxzRRfGou3fuaPsSkflBYLv32I5ecwVbEuo4YAoJqWlM8b8sBFYVvmfaZPn YdeK5WV7xg127aczaS+cB5mdldiKLaQjguTwiBNSZgXUB2dq/iyWyXYnPEgKemcD wW/1M9H0zj36a1S3BnSiDhF+EzjKxgWXJM4AzxrqHHS8/7CcS84x8CIP1idOpXb4 Vs9thRA7RKmHg5cAeXBlE+ATF5jAv6H2RVxs3nt8GDSPIHp0hu2Hrez5IsgEAzlN Gk8owGI2hj2NojA= =6lJT -END PGP SIGNATURE End Message ---
Bug#974705: Changes to job handling cause hangs in wait
On Thu, Dec 03, 2020 at 01:27:51PM +0100, Michael Biebl wrote: > > Hm, so I applied this change and switched backed to dash, but now I get > > autopkgtest systemd --test-name=timedated -s -- lxc -s autopkgtest-sid > ... > disable NTP > enable NTP > Terminated > autopkgtest [13:21:42]: test timedated: ---] > autopkgtest [13:21:42]: test timedated: - - - - - - - - - - results - - - - > - - - - - - > timedatedFAIL non-zero exit status 143 > > > Running with sh -x > ... > + kill 825 > + wait 825 > Terminated > > > Herbert, any idea what going wrong there? > (systemd 247.1-2 and dash 0.5.11+git20200708+dd9ef66-2) Sorry, my bad. wait(1) with no arguments ignores the error status of the child and always return zero. wait(1) specifically on a child obviously returns the error status of that child. Since the child was killed, we need to ignore that, so this works for me: wait $MONPID 2> /dev/null || : Thanks, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Processed: menu-cache: diff for NMU version 1.1.0-1.1
Processing control commands: > tags 957533 + patch Bug #957533 [src:menu-cache] menu-cache: ftbfs with GCC-10 Added tag(s) patch. > tags 957533 + pending Bug #957533 [src:menu-cache] menu-cache: ftbfs with GCC-10 Added tag(s) pending. -- 957533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957533: menu-cache: diff for NMU version 1.1.0-1.1
Control: tags 957533 + patch
Control: tags 957533 + pending
Dear maintainer,
Mateusz Łukasik has prepared an NMU for menu-cache (versioned as
1.1.0-1.1) and I've uploaded it to DELAYED/2. Please feel free to
tell me if I should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- NP: Caridad Cuervo: Yo no lloro mas
diff -Nru menu-cache-1.1.0/debian/changelog menu-cache-1.1.0/debian/changelog
--- menu-cache-1.1.0/debian/changelog 2017-11-04 01:11:57.0 +0100
+++ menu-cache-1.1.0/debian/changelog 2020-11-12 20:40:31.0 +0100
@@ -1,3 +1,10 @@
+menu-cache (1.1.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Take from Fedora patch for fix FTBFS with gcc-10. (Closes: #957533)
+
+ -- Mateusz Łukasik Thu, 12 Nov 2020 20:40:31 +0100
+
menu-cache (1.1.0-1) unstable; urgency=medium
* Replacing build dependency on libfm-dev with libfm-extra-dev
diff -Nru menu-cache-1.1.0/debian/patches/menu-cache-1.1.0-0001-Support-gcc10-compilation.patch menu-cache-1.1.0/debian/patches/menu-cache-1.1.0-0001-Support-gcc10-compilation.patch
--- menu-cache-1.1.0/debian/patches/menu-cache-1.1.0-0001-Support-gcc10-compilation.patch 1970-01-01 01:00:00.0 +0100
+++ menu-cache-1.1.0/debian/patches/menu-cache-1.1.0-0001-Support-gcc10-compilation.patch 2020-11-12 20:36:19.0 +0100
@@ -0,0 +1,108 @@
+From 1ce739649b4d66339a03fc0ec9ee7a2f7c141780 Mon Sep 17 00:00:00 2001
+From: Mamoru TASAKA
+Date: Fri, 24 Jan 2020 13:33:00 +0900
+Subject: [PATCH] Support gcc10 compilation
+
+gcc10 now defaults to -fno-common, and with gcc10 menu-cache compilation fails like
+
+/bin/ld: menu-merge.o:menu-cache-gen/menu-tags.h:167: multiple definition of `DirDirs'; main.o:menu-cache-gen/menu-tags.h:167: first defined here
+/bin/ld: menu-merge.o:menu-cache-gen/menu-tags.h:164: multiple definition of `AppDirs'; main.o:menu-cache-gen/menu-tags.h:164: first defined here
+/bin/ld: menu-merge.o:menu-cache-gen/menu-tags.h:52: multiple definition of `menuTag_Layout'; main.o:menu-cache-gen/menu-tags.h:52: first defined here
+
+
+This patch fixes compilation with gcc10: properly declaring variables in header with "extern", and also removing some unneeded variables in header files.
+---
+ menu-cache-gen/menu-tags.h | 55 --
+ 1 file changed, 17 insertions(+), 38 deletions(-)
+
+diff --git a/menu-cache-gen/menu-tags.h b/menu-cache-gen/menu-tags.h
+index f3fd7d3..f71c0bc 100644
+--- a/menu-cache-gen/menu-tags.h
b/menu-cache-gen/menu-tags.h
+@@ -22,38 +22,17 @@
+ #include
+ #include
+
+-FmXmlFileTag menuTag_Menu;
+-FmXmlFileTag menuTag_AppDir;
+-FmXmlFileTag menuTag_DefaultAppDirs;
+-FmXmlFileTag menuTag_DirectoryDir;
+-FmXmlFileTag menuTag_DefaultDirectoryDirs;
+-FmXmlFileTag menuTag_Include;
+-FmXmlFileTag menuTag_Exclude;
+-FmXmlFileTag menuTag_Filename;
+-FmXmlFileTag menuTag_Or;
+-FmXmlFileTag menuTag_And;
+-FmXmlFileTag menuTag_Not;
+-FmXmlFileTag menuTag_Category;
+-FmXmlFileTag menuTag_MergeFile;
+-FmXmlFileTag menuTag_MergeDir;
+-FmXmlFileTag menuTag_DefaultMergeDirs;
+-FmXmlFileTag menuTag_Directory;
+-FmXmlFileTag menuTag_Name;
+-FmXmlFileTag menuTag_Deleted;
+-FmXmlFileTag menuTag_NotDeleted;
+-FmXmlFileTag menuTag_OnlyUnallocated;
+-FmXmlFileTag menuTag_NotOnlyUnallocated;
+-FmXmlFileTag menuTag_All;
+-FmXmlFileTag menuTag_LegacyDir;
+-FmXmlFileTag menuTag_KDELegacyDirs;
+-FmXmlFileTag menuTag_Move;
+-FmXmlFileTag menuTag_Old;
+-FmXmlFileTag menuTag_New;
+-FmXmlFileTag menuTag_Layout;
+-FmXmlFileTag menuTag_DefaultLayout;
+-FmXmlFileTag menuTag_Menuname;
+-FmXmlFileTag menuTag_Separator;
+-FmXmlFileTag menuTag_Merge;
++extern FmXmlFileTag menuTag_AppDir;
++extern FmXmlFileTag menuTag_DirectoryDir;
++extern FmXmlFileTag menuTag_Include;
++extern FmXmlFileTag menuTag_Exclude;
++extern FmXmlFileTag menuTag_Filename;
++extern FmXmlFileTag menuTag_Or;
++extern FmXmlFileTag menuTag_And;
++extern FmXmlFileTag menuTag_Not;
++extern FmXmlFileTag menuTag_Category;
++extern FmXmlFileTag menuTag_All;
++extern FmXmlFileTag menuTag_LegacyDir;
+
+ typedef enum {
+ MERGE_NONE, /* starting value */
+@@ -152,19 +131,19 @@ typedef struct {
+ } MenuRule;
+
+ /* requested language(s) */
+-char **languages;
++extern char **languages;
+
+ /* list of menu files to monitor */
+-GSList *MenuFiles;
++extern GSList *MenuFiles;
+
+ /* list of menu dirs to monitor */
+-GSList *MenuDirs;
++extern GSList *MenuDirs;
+
+ /* list of available app dirs */
+-GSList *AppDirs;
++extern GSList *AppDirs;
+
+ /* list of available dir dirs */
+-GSList *DirDirs;
++extern GSList *DirDirs;
+
+ /* parse and merge menu files */
+ MenuMenu *get_merged_menu(const char *file, FmXmlFile **xmlfile, GError **error);
+@@ -177,7 +156,7 @@ gboolean save_menu_cache(MenuMenu *layout,
Bug#972722: marked as done (pyvows: ftbfs with python 3.9)
Your message dated Sun, 06 Dec 2020 23:56:20 -0300
with message-id <98857780a3280a91f0d97b6bc33c7a1943d6b663.ca...@debian.org>
and subject line done
has caused the Debian Bug report #972722,
regarding pyvows: ftbfs with python 3.9
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.)
--
972722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyvows
Version: 3.0.0-3
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
User: debian-pyt...@lists.debian.org
Usertags: python3.9
Dear Maintainer,
Now that python 3.9 is a supported version in unstable the build fails
in the following slightly alarming way:
dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9
in use)
I: pybuild base:217: python3.9 pyvows/cli.py tests/
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
:228: RuntimeWarning: greenlet.greenlet size
changed, may indicate binary incompatibility. Expected 144 from C header, got
152 from PyObject
Segmentation fault (core dumped)
E: pybuild pybuild:352: test: plugin custom failed with: exit code=139:
python3.9 pyvows/cli.py tests/
Cheers,
mwh
-- System Information:
Debian Release: bullseye/sid
APT prefers focal-updates
APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'),
(400, 'focal-proposed'), (100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi Michael,
Thank you, but it is not a pyvows bug. So, I'm closing it.
I've added 3.9 in travis CI and tests passed
https://travis-ci.org/github/heynemann/pyvows/builds/745289686
Running:
python3 -c 'import gevent; print("gevent", gevent.__version__); import
greenlet; print("greenlet", greenlet.__version__)'
Output:
:228: RuntimeWarning: greenlet.greenlet
size changed, may indicate binary incompatibility. Expected 144 from C
header, got 152 from PyObject
:228: RuntimeWarning: greenlet.greenlet
size changed, may indicate binary incompatibility. Expected 144 from C
header, got 152 from PyObject
:228: RuntimeWarning: greenlet.greenlet
size changed, may indicate binary incompatibility. Expected 144 from C
header, got 152 from PyObject
:228: RuntimeWarning: greenlet.greenlet
size changed, may indicate binary incompatibility. Expected 144 from C
header, got 152 from PyObject
gevent 1.4.0
greenlet 0.4.17
gevent fixed it, thanks again.
Cheers,
--
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com
signature.asc
Description: This is a digitally signed message part
--- End Message ---
Bug#976189: Bug 9761189 - How to fix
Hello Maintainer:
Came across this as well and did some digging to find the cause. Found that
Python 3.9 removed the getiterator attribute and replaced it with iter.
To fix, in file "/usr/lib/python3/dist-packages/catfish_lib/Builder.py" at
line 87 changed this line:
ele_widgets = tree.getiterator("object")
to
ele_widgets = tree.iter("object")
Also found one more line in the file needed to be changed (as I scanned to
see if "getiterator" was mentioned anywhere else in the file) and it's this
code at line 112:
ele_signals = tree.getiterator("signal")
Changed it to show:
ele_signals = tree.iter("signal")
Saved the original with .orig extension then saved changed file as
Builder.py.
Tested catfish again from terminal and it started right up and functioned
normally as I tested several searches. As I never did a patch diff before,
if anyone can create a patch from my notes here feel free to do so.
Cheers!
-R
Processed: severity of 976512 is important
Processing commands for cont...@bugs.debian.org: > severity 976512 important Bug #976512 [src:xtpcpp] xtpcpp: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libalglib.so', needed by 'src/xtpcpp'. Stop. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976514 is important
Processing commands for cont...@bugs.debian.org:
> severity 976514 important
Bug #976514 [src:tinyarray] tinyarray: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.8 3.9" --test-pytest
--test-args=../../../test_tinyarray.py returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 976523 is important
Processing commands for cont...@bugs.debian.org: > severity 976523 important Bug #976523 [src:spades] spades: FTBFS: jemalloc_internal.h:292:6: error: #error "No LG_QUANTUM definition for architecture; specify via CPPFLAGS" Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976581 is important
Processing commands for cont...@bugs.debian.org:
> severity 976581 important
Bug #976581 {Done: Sebastian Ramacher } [src:siconos]
siconos: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && make -j1 test
"ARGS=-E 'COLLECTION|python_test_lcp|dr_iso1'" ARGS\+=-j1 returned exit code 2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 976479 is important
Processing commands for cont...@bugs.debian.org: > severity 976479 important Bug #976479 [src:scrappie] scrappie: FTBFS: scrappie_matrix.h:5:14: fatal error: immintrin.h: No such file or directory Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976497 is important
Processing commands for cont...@bugs.debian.org:
> severity 976497 important
Bug #976497 [src:python-parasail] python-parasail: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 976553 is important
Processing commands for cont...@bugs.debian.org: > severity 976553 important Bug #976553 [src:mojoshader] mojoshader: FTBFS: segfaults Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976478 is important
Processing commands for cont...@bugs.debian.org: > severity 976478 important Bug #976478 [src:libecpint] libecpint: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976557 is important
Processing commands for cont...@bugs.debian.org: > severity 976557 important Bug #976557 [src:kafs-client] kafs-client: FTBFS: cc: error: unrecognized command-line option ‘-m64’ Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976469 is important
Processing commands for cont...@bugs.debian.org: > severity 976469 important Bug #976469 [src:haskell-xml-html-qq] haskell-xml-html-qq: FTBFS: tests failed Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976492 is important
Processing commands for cont...@bugs.debian.org:
> severity 976492 important
Bug #976492 {Done: Stephen Kitt } [src:bochs] bochs: FTBFS on
arm64: ld: cannot represent machine `i386'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 976524 is important
Processing commands for cont...@bugs.debian.org:
> severity 976524 important
Bug #976524 [src:bmtk] bmtk: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 976474 is important
Processing commands for cont...@bugs.debian.org: > severity 976474 important Bug #976474 [src:bcachefs-tools] bcachefs-tools: FTBFS: include/linux/log2.h:281:27: error: ‘PAGE_SHIFT’ undeclared (first use in this function); did you mean ‘PAGE_SIZE’? Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 976494 is important
Processing commands for cont...@bugs.debian.org:
> severity 976494 important
Bug #976494 [src:blastem] blastem: FTBFS on arm64: z80_to_x86.c:634:21: error:
invalid operands to binary - (have ‘code_ptr’ {aka ‘unsigned int *’} and
‘uint8_t *’ {aka ‘unsigned char *’})
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 953285 976484
Processing commands for cont...@bugs.debian.org: > forcemerge 953285 976484 Bug #953285 [src:rust-mach-o-sys] rust-mach-o-sys fails on architectures with unsigned char Bug #953285 [src:rust-mach-o-sys] rust-mach-o-sys fails on architectures with unsigned char Marked as found in versions rust-mach-o-sys/0.1.1-3. Added tag(s) bullseye and sid. Bug #976484 [src:rust-mach-o-sys] rust-mach-o-sys: unsigned values cannot be negated Severity set to 'normal' from 'serious' Added indication that 976484 affects src:rust-memsec Marked as found in versions rust-mach-o-sys/0.1.1-2. Merged 953285 976484 > thanks Stopping processing here. Please contact me if you need assistance. -- 953285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953285 976484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)
It was quite disappointing to see (or not see) the GUI/WM stop working after a causal system update (not upGrade). I was able to get the system somewhat back to normal by using the NOUVEAU driver instead of NVIDIA. BTW, even that was kind of tricking because the Nvidia driver blacklisted Nouveau at /etc/modprobe.d/nvidia-blacklists-nouveau.conf which remained even after purging everything related to Nvidia via APT. PS.: For some reason, the laptop no longer revived with Nouveau after a suspend (closing the laptop's lid). That was "bypassed" in the meantime by editing /etc/systemd/logind.conf and replacing all "suspends" with "ignores". Again, that was very disappointing !8-(. What happened with the golden 'Do no harm, don't break users' rule?! On Sun, Dec 6, 2020 at 1:33 PM Paolo Inaudi wrote: > > @jim_p Is it possible for you to avoid putting all system information > and Xorg logs in every message? > It makes the thread very difficult to follow on the online bug tracker. > > I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it > won't be my very last kernel version. > > -- > To unsubscribe, send mail to 976056-unsubscr...@bugs.debian.org.
Processed: severity of 976473 is important
Processing commands for cont...@bugs.debian.org: > severity 976473 important Bug #976473 [src:r-cran-s2] r-cran-s2: FTBFS: ../inst/include/s2/third_party/absl/base/internal/unaligned_access.h:289:8: error: ‘uint64’ does not name a type; did you mean ‘uint64_t’? Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#968730: fixed in nifticlib 3.0.1-1
Processing control commands:
> reopen -1
Bug #968730 {Done: Andreas Tille } [libnifti2] libnifti2:
libniftiio.so.2 not provided
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions nifticlib/3.0.1-1.
> notifxed -1 3.0.1-1
Unknown command or malformed arguments to command.
--
968730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#968730: fixed in nifticlib 3.0.1-1
control: reopen -1 control: notifxed -1 3.0.1-1 Hello, how can three different binaries provide the very same old -dev library? what happens now is that apt gets the old real cruft binary -dev package, and not the virtual provided one (because it seems to have higher priority). So the rebuilds won't pick up the new library. I think you have multiple ways to solve: 1) restore the old dev package as a binary package that depends on the three new split -dev 2) fix and patch all the reverse dependencies to depend on the right subpackage (or all if they need them all). Or something else I'm not aware right now. G. On Fri, 04 Dec 2020 15:00:41 + Debian FTP Masters wrote: > Source: nifticlib > Source-Version: 3.0.1-1 > Done: Andreas Tille > > We believe that the bug you reported is fixed in the latest version of > nifticlib, 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 968...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Andreas Tille (supplier of updated nifticlib package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Format: 1.8 > Date: Tue, 01 Dec 2020 22:17:54 +0100 > Source: nifticlib > Binary: libnifti-doc libnifti2-2 libnifti2-2-dbgsym libnifti2-dev > libnifticdf-dev libnifticdf2 libnifticdf2-dbgsym libniftiio-dev libniftiio2 > libniftiio2-dbgsym libznz-dev libznz3 libznz3-dbgsym nifti-bin > nifti-bin-dbgsym > Architecture: source all amd64 > Version: 3.0.1-1 > Distribution: unstable > Urgency: medium > Maintainer: Debian Med Packaging Team > > Changed-By: Andreas Tille > Description: > libnifti-doc - NIfTI library API documentation > libnifti2-2 - IO libraries for the NIfTI-1 data format > libnifti2-dev - IO libraries for the NIfTI-1 data format (development) > libnifticdf-dev - NIfTI functions to compute cumulative distributions > (development) > libnifticdf2 - NIfTI functions to compute cumulative distributions > libniftiio-dev - development low-level IO libraries for the NIfTI-1 data > format (n > libniftiio2 - low-level IO libraries for the NIfTI-1 data format (niftiio) > libznz-dev - low-level IO library znzlib for the NIfTI-1 data format > libznz3- low-level IO library znzlib for the NIfTI-1 data format > nifti-bin - tools shipped with the NIfTI library > Closes: 968730 > Changes: > nifticlib (3.0.1-1) unstable; urgency=medium > . >* Team upload. >* New upstream version > Closes: #968730 >* Standards-Version: 4.5.1 (routine-update) >* debhelper-compat 13 (routine-update) >* Make source package Section: science >* Separate binary packages for libznz, libniftiio, libnifticdf > Checksums-Sha1: > 4681c06fac5af0e49d0fbca060272c9c5c1b500a 2564 nifticlib_3.0.1-1.dsc
Processed: reassign 976687 to src:python-escript
Processing commands for cont...@bugs.debian.org: > reassign 976687 src:python-escript 5.5-5 Bug #976687 [src:python3-escript] python3-escript: mixing incompatible libpython and libboost_python Warning: Unknown package 'src:python3-escript' Bug reassigned from package 'src:python3-escript' to 'src:python-escript'. No longer marked as found in versions python3-escript/5.5-5. Ignoring request to alter fixed versions of bug #976687 to the same values previously set Bug #976687 [src:python-escript] python3-escript: mixing incompatible libpython and libboost_python Marked as found in versions python-escript/5.5-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 976687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-escript: mixing incompatible libpython and libboost_python
Processing control commands: > affects -1 python3-escript python3-escript-mpi Bug #976687 [src:python3-escript] python3-escript: mixing incompatible libpython and libboost_python Warning: Unknown package 'src:python3-escript' Added indication that 976687 affects python3-escript and python3-escript-mpi Warning: Unknown package 'src:python3-escript' -- 976687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: glom: mixing incompatible libpython and libboost_python
Processing control commands: > affects -1 glom libglom-1.30-0 Bug #976686 [src:glom] glom: mixing incompatible libpython and libboost_python Added indication that 976686 affects glom and libglom-1.30-0 -- 976686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976687: python3-escript: mixing incompatible libpython and libboost_python
Source: python3-escript Version: 5.5-5 Severity: serious Tags: bookworm sid Control: affects -1 python3-escript python3-escript-mpi $ objdump -p /usr/lib/python3-escript/esys/dudley/dudleycpp.so | grep python /usr/lib/python3-escript/esys/dudley/dudleycpp.so: file format elf64-x86-64 NEEDED libpython3.9.so.1.0 NEEDED libboost_python38.so.1.71.0 $ This is now no longer a problem for bullseye, but will again pop up during python3 transitions for bookworm.
Bug#976686: glom: mixing incompatible libpython and libboost_python
Source: glom Version: 1.30.4-6.1 Severity: serious Tags: bookworm sid Control: affects -1 glom libglom-1.30-0 $ objdump -p /usr/bin/glom | grep python NEEDED libpython3.9.so.1.0 NEEDED libboost_python38.so.1.71.0 $ This is now no longer a problem for bullseye, but will again pop up during python3 transitions for bookworm.
Bug#976573: pandas: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
On 05/12/20 at 13:47 +0100, Lucas Nussbaum wrote: Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye Does this imply that it was also tested and failed in bullseye? The log is marked unstable, and the test failures in it are #976620, which is probably unstable-only.
Bug#974063: marked as done (postgresql-13: FTBFS: timetz test failure)
Your message dated Sun, 06 Dec 2020 22:32:08 + with message-id and subject line Bug#974063: fixed in postgresql-11 11.10-0+deb10u1 has caused the Debian Bug report #974063, regarding postgresql-13: FTBFS: timetz test failure 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.) -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgresql-13 Version: 13.0-6 Severity: serious Justification: ftbfs Tags: ftbfs User: debian-p...@lists.debian.org Usertags: perl-5.32-transition Control: block 968912 with -1 Similar to postgresql-12 (#974061) postgresql-13 FTBFS on multiple archs, eg: https://buildd.debian.org/status/fetch.php?pkg=postgresql-13=amd64=13.0-6%2Bb1=1604915618=0 Unfortunately, postgresql-13 wasn't in sid at the point we did our last full rebuild test. plperl does seem to be implicated in the error output: 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger ERROR: object audit_tbls.schema_two_table_three of type table cannot be dropped 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE SQL statement "DROP TABLE IF EXISTS audit_tbls.schema_two_table_three" PL/pgSQL function test_evtrig_dropped_objects() line 8 at EXECUTE 2020-11-09 09:53:28.680 UTC client backend[31345] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger ERROR: object schema_one.table_three of type table cannot be dropped 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE 2020-11-09 09:53:28.818 UTC client backend[31345] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2020-11-09 09:53:28.985 UTC client backend[31345] pg_regress/event_trigger ERROR: pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function 2020-11-09 09:53:28.985 UTC client backend[31345] pg_regress/event_trigger STATEMENT: select pg_event_trigger_table_rewrite_oid(); 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger ERROR: rewrites not allowed 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger CONTEXT: PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE 2020-11-09 09:53:28.998 UTC client backend[31345] pg_regress/event_trigger STATEMENT: alter table rewriteme alter column foo type numeric; 2020-11-09 09:53:29.024 UTC client backend[31345] pg_regress/event_trigger ERROR: cannot alter type "rewritetype" because column "rewritemetoo3.a" uses it 2020-11-09 09:53:29.024 UTC client backend[31345] pg_regress/event_trigger STATEMENT: alter type rewritetype alter attribute a type varchar cascade; 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats LOG: wait_for_stats delayed 0.543818 seconds 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats CONTEXT: PL/pgSQL function wait_for_stats() line 48 at RAISE 2020-11-09 09:53:30.668 UTC client backend[31354] pg_regress/stats STATEMENT: SELECT wait_for_stats(); 2020-11-09 09:53:30.836 UTC postmaster[29982] LOG: received fast shutdown request 2020-11-09 09:53:30.836 UTC postmaster[29982] LOG: aborting any active transactions 2020-11-09 09:53:30.839 UTC postmaster[29982] LOG: background worker "logical replication launcher" (PID 29991) exited with exit code 1 2020-11-09 09:53:30.840 UTC checkpointer[29986] LOG: shutting down 2020-11-09 09:53:30.840 UTC checkpointer[29986] LOG: checkpoint starting: shutdown immediate 2020-11-09 09:53:31.100 UTC checkpointer[29986] LOG: checkpoint complete: wrote 10551 buffers (64.4%); 0 WAL file(s) added, 0 removed, 13 recycled; write=0.227 s, sync=0.000 s, total=0.259 s; sync files=0, longest=0.000 s, average=0.000 s; distance=220237 kB, estimate=220237 kB 2020-11-09 09:53:31.131 UTC postmaster[29982] LOG: database system is shut down Please could you take a look? Cheers Dominic --- End Message --- --- Begin Message --- Source: postgresql-11 Source-Version: 11.10-0+deb10u1 Done: Christoph Berg We believe that the bug you reported is fixed in the latest version of postgresql-11, 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
Processed: kmc: hangs at high cores count
Processing commands for cont...@bugs.debian.org: > retitle 954270 kmc: hangs at high cores count Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out Changed Bug title to 'kmc: hangs at high cores count' from 'kmc: arm64 autopkgtest time out'. > thanks Stopping processing here. Please contact me if you need assistance. -- 954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976658: debcargo is broken (and the autopkgtest didn't catch it).
debcargo (and cargo) is out of date in Debian and needs to be updated. We had been blocked on the FTP binary-NEW policy but there is some progress in that area. Alternatively you could use collapse_features to begin to update it, but I personally do not approve of it and haven't been spending time on it. X peter green: > Package: debcargo > Version: 2.4.3-2+bw > Severity: grave > > After the recent binnmu of debcargo. debcargo update > (after deleting the cache) gives. > >> >> Updating crates.io index >> Something failed: failed to fetch >> `https://github.com/rust-lang/crates.io-index` >> >> Caused by: >> invalid version 0 on git_proxy_options; class=Invalid (3) > > This issue was not caught by the autopkgtest. > > In order to check this was indeed caused by the libgit2 update (and not by > one of the > other updates that have happened since the last debcargo build in unstable) I > did a > test build with libgit2-dev from testing but everything else from unstable. > That > test build worked fine. > > I suspect rust-git2/rust-libgit2-sys need to be updated to match the new > libgit2. > > I've got to go now, but I'll try look into this issue some more later tonight. > -- GPG: ed25519/56034877E1F87C35 https://github.com/infinity0/pubkeys.git
Bug#975410: marked as done (src:sieve-connect: fails to migrate to testing for too long: maintainer built arch:all binary)
Your message dated Sun, 06 Dec 2020 21:19:09 + with message-id and subject line Bug#975410: fixed in sieve-connect 0.90-1.1 has caused the Debian Bug report #975410, regarding src:sieve-connect: fails to migrate to testing for too long: maintainer built arch:all binary 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.) -- 975410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sieve-connect Version: 0.88-1.1 Severity: serious Control: close -1 0.90-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:sieve-connect in its current version in unstable has been trying to migrate for 61 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 immediately closed this bug with the version in unstable, 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=sieve-connect signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: sieve-connect Source-Version: 0.90-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of sieve-connect, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated sieve-connect 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: Sat, 21 Nov 2020 21:21:37 +0100 Source: sieve-connect Architecture: source Version: 0.90-1.1 Distribution: unstable Urgency: medium Maintainer: Andrew Pollock Changed-By: Paul Gevers Closes: 975410 Changes: sieve-connect (0.90-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #975410) Checksums-Sha1: 25321c5a08d90f0a40bb7c60a0b6bbe14ac11e3b 1485 sieve-connect_0.90-1.1.dsc b458a14ceab127c4f2dc7aa752086133e5b0527c 2872 sieve-connect_0.90-1.1.debian.tar.xz Checksums-Sha256: bda7eedba6edfd31973f6b7870de813754a3e5400923559712796d321618d2c4 1485 sieve-connect_0.90-1.1.dsc 2d2985990b9ae59aec4e2b0a77b78a83ee047907e18bed316f763329a74b3c28 2872 sieve-connect_0.90-1.1.debian.tar.xz Files: 16ff9431a0a13d24a3430e6584469e0e 1485 net optional sieve-connect_0.90-1.1.dsc 4bd87b57090cfe894b791d726176ff55 2872 net optional sieve-connect_0.90-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl+5duoACgkQnFyZ6wW9 dQoFBAf/ZW3JMi9XQgvZm1WJ+PDv7FqtgFnnkVet8KdpsH+4sN8Cqz9HOmejTtG1 QwJP4yVuIzYgiFIIcqNBuHtBLQx2L+7AzimIIQMVJ8vFveKO39/VnGS1IRPtWIGx Q5/rW5EaImfWQtrZCHu0eHDFi0DmCxKboifTduOpfn9DEwFP2jYHnJJia35JFOXd +WND0eVvmCpWs5gpz8kgsf5AS1MFTeXLjR59+YkUieWL80woSzgNGFsVqI7AyQ+Y
Bug#976646: [Pkg-julia-devel] Bug#976646: julia: FTBFS on armhf
On 2020-12-07 05:36:58 +0900, Norbert Preining wrote: > Hi, > > thanks for the report, but that is really a porter/builder box problem: > > > | LLVM ERROR: out of memory > > Seems the machine couldn't deal with the required amount ( which is > considerable from my experience). > > I don't know what **we** can do here ... One could try the usual approaches of reducing the debug symbols to -g1 or optimization to -O1. And it's not usually the case the this is an actual out of memory issue, but a process that requires more than the mappable amount of memory. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Processed (with 1 error): Re: Bug#976573: pandas: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Processing commands for cont...@bugs.debian.org:
> affects 976573 pandas
Bug #976573 [python3-xlrd] pandas: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Added indication that 976573 affects pandas
> retitle 976573 xlrd: AttributeError if defusedxml is installed
Bug #976573 [python3-xlrd] pandas: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Changed Bug title to 'xlrd: AttributeError if defusedxml is installed' from
'pandas: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.8 3.9" returned exit code 13'.
> merge 976573 976620
Bug #976573 [python3-xlrd] xlrd: AttributeError if defusedxml is installed
Bug #976573 [python3-xlrd] xlrd: AttributeError if defusedxml is installed
Marked as found in versions python-xlrd/1.2.0-1.
Added tag(s) patch.
Bug #976620 [python3-xlrd] xlrd: if defusedxml installed, AttributeError:
'ElementTree' object has no attribute 'getiterator'
Added tag(s) ftbfs and sid.
Merged 976573 976620
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
976573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976573
976620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: ignore
Processing commands for cont...@bugs.debian.org: > tags 901952 bullseye-ignore Bug #901952 [tar] xdelta: expected from file (/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes Added tag(s) bullseye-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 901952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954270: [RFS] kmc: arm64 autopkgtest time out
Control: tag -1 + confirmed Control: tag -1 - unreproducible Hi Paul, Paul Gevers, on 2020-12-06 20:54:43 +0100: > It recently started to time out on amd64 too, but not always [1]. And > when we added armhf, that timed out too. The failures on amd64 that I > checked were all on ci-worker13, which is one of our hosts that runs > multiple debci-workers. That's common on our arm64 workers too. > [1] https://ci.debian.net/packages/k/kmc/testing/amd64/ Thanks for the pointers, I believe I found a reproducer! :) All failing CI runners all had in common a high NR_CPUS count, at least 32 cores. I don't have 32 cores at hand, but kmc provides an option -t to increase the parallelization. The following command, in the conditions of the autopkgtest, will hang on any machines: $ kmc -ci1 -m1 -k28 -t32 $ORIGDIR/debian/tests/sample_6.fastq.gz 1 . strace output looks like the program just deadlocks, I see no CPU consumption while the command is supposed to be running: strace: Process 3001579 attached with 23 threads [pid 3001633] futex(0x55b69bf9cb70, FUTEX_WAIT_PRIVATE, 0, NULL [pid 3001632] futex(0x55b69bf9cb70, FUTEX_WAIT_PRIVATE, 0, NULL [...] [pid 3001612] futex(0x55b69bf9cb70, FUTEX_WAIT_PRIVATE, 0, NULL [pid 3001579] futex(0x55b69bf9ce18, FUTEX_WAIT_PRIVATE, 0, NULL I suppose easy solution would be to cap the cores count of the program while working with upstream to find a proper fix. Will see what can be done about it. Have a good evening, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Processed: Re: [RFS] kmc: arm64 autopkgtest time out
Processing control commands: > tag -1 + confirmed Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out Added tag(s) confirmed. > tag -1 - unreproducible Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out Removed tag(s) unreproducible. -- 954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973634: marked as done (mpich: d/copyright does not mention vis.js)
Your message dated Sun, 06 Dec 2020 21:00:11 + with message-id and subject line Bug#973634: fixed in mpich 3.4~b1-1 has caused the Debian Bug report #973634, regarding mpich: d/copyright does not mention vis.js 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.) -- 973634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mpich Version: 3.4~a2+really3.3.2-2 Severity: serious Justification: Policy 2.3, 4.5, 12.5 X-Debbugs-CC: ftpmas...@debian.org Hello, d/copyright does not mention debian/missing-sources/vis.js, which has a different license and copyright. Same goes for the minified copies of vis.js in the source. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: mpich Source-Version: 3.4~b1-1 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of mpich, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated mpich package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Dec 2020 19:08:17 + Source: mpich Binary: libmpich-dev libmpich13 libmpich13-dbgsym mpich mpich-dbgsym mpich-doc Architecture: source amd64 all Version: 3.4~b1-1 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Description: libmpich-dev - Development files for MPICH libmpich13 - Shared libraries for MPICH mpich - Implementation of the MPI Message Passing Interface standard mpich-doc - Documentation for MPICH Closes: 956289 973634 Changes: mpich (3.4~b1-1) experimental; urgency=medium . * Enable pmix * New upstream release * Set VCS-Git to point to debian/latest branch * Standards-Version now 4.5.1 * Document vis.js, vis.min.js licensing. Closes: #973634 * Update d/copyright . Closes: #956289 Checksums-Sha1: 889fe622d2258914979cf0d1213fd2bd29fdac4b 2628 mpich_3.4~b1-1.dsc 60c6145601666f923545463c971d24890bab 13989332 mpich_3.4~b1.orig.tar.xz 0cd7a91dfd660ede57e55f32d4ce1d63c8338919 344000 mpich_3.4~b1-1.debian.tar.xz 6bf7e1e297818bfe92ea0626fe97ddca83b7c3ba 2637412 libmpich-dev_3.4~b1-1_amd64.deb c6d7bde30ab702da43aa334ac98838f55177de60 15347024 libmpich13-dbgsym_3.4~b1-1_amd64.deb cb7ce75970d41c8d73133408115a717b4d20e46f 2353212 libmpich13_3.4~b1-1_amd64.deb dd147e8232eb7b3b705e36979a13d21e201c932d 20744 mpich-dbgsym_3.4~b1-1_amd64.deb 9a034cadd9be7f17c55d607d74468534004f9a84 263132 mpich-doc_3.4~b1-1_all.deb b0bf29c2ac5c357185463844e7ee893aa444cdf0 13249 mpich_3.4~b1-1_amd64.buildinfo d9816ed2b825ed6ed5eb7d2b3434410463b36acd 41416 mpich_3.4~b1-1_amd64.deb Checksums-Sha256: 6fe2ded8aae95cce5171c4114dc4c776997e7b88a232c097ea9a13a5146874a7 2628 mpich_3.4~b1-1.dsc 993bf2ba1201b613b3f5da8349707a328117307a37f604176db23c731220e288 13989332 mpich_3.4~b1.orig.tar.xz 8bd200b3e9543346fcaf4b32b9a90d95fbd3afee956856484d34728e190ce95b 344000 mpich_3.4~b1-1.debian.tar.xz 02e32bca58fc00be8f7c0e72dce84c1a9101c707b1c49caf527c6184eaa22823 2637412 libmpich-dev_3.4~b1-1_amd64.deb c460142c0de3c6ee2342992b3bf2459d2dbcf97886169d4dc0652f2b1a9a813a 15347024 libmpich13-dbgsym_3.4~b1-1_amd64.deb fb2541ad1c5b59d1d875853c66d109c7ec7796d6f2bd9e1904da6fac242a4068 2353212 libmpich13_3.4~b1-1_amd64.deb 3608aa02d84aa9b1d33afe2567a6f97ecfc831b0a9d056aaff71e5cdc593a5bd 20744 mpich-dbgsym_3.4~b1-1_amd64.deb 614cdb484b87351e8d12c18e2a815186a1b2c875a2b2110a748e2b2145d1b17c 263132 mpich-doc_3.4~b1-1_all.deb 28a51d6d9f51f48a1f49896ad14fd882f6b20024fe5390281f7dbb9f62dfed11 13249 mpich_3.4~b1-1_amd64.buildinfo d9b0e9b309fe8017ad388ccffd43c52ba5754e2da093ae5fd065da38a1f6baa2 41416 mpich_3.4~b1-1_amd64.deb Files: 0d575f654d8d0d6cafc3d093c812aab5 2628 devel optional mpich_3.4~b1-1.dsc d300f26e678316a087aabd7cfe135f59 13989332 devel optional mpich_3.4~b1.orig.tar.xz 30ce98b17588b6ad630362eae2d38d01 344000 devel optional mpich_3.4~b1-1.debian.tar.xz 1360bae82fa84f79734dd88c94844301
Bug#956289: marked as done (Problems identified in debian/copyright)
Your message dated Sun, 06 Dec 2020 21:00:11 + with message-id and subject line Bug#956289: fixed in mpich 3.4~b1-1 has caused the Debian Bug report #956289, regarding Problems identified in debian/copyright 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.) -- 956289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mpich Version: 3.4~a2-3 Severity: serious I noticed that this package appears to have some issues with debian/copyright. A copyright is missing for: - src/hwloc/* - src/izem/* - src/mpi/romio - probably more... (I did not look at every subdirectory.) There is also a copyright paragraph for contrib/knem/, which is unused. There are also some Lintian warnings which would be beneficial to look at. If you need further clarification, please don't hesitate to ask. --- End Message --- --- Begin Message --- Source: mpich Source-Version: 3.4~b1-1 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of mpich, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated mpich package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Dec 2020 19:08:17 + Source: mpich Binary: libmpich-dev libmpich13 libmpich13-dbgsym mpich mpich-dbgsym mpich-doc Architecture: source amd64 all Version: 3.4~b1-1 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Description: libmpich-dev - Development files for MPICH libmpich13 - Shared libraries for MPICH mpich - Implementation of the MPI Message Passing Interface standard mpich-doc - Documentation for MPICH Closes: 956289 973634 Changes: mpich (3.4~b1-1) experimental; urgency=medium . * Enable pmix * New upstream release * Set VCS-Git to point to debian/latest branch * Standards-Version now 4.5.1 * Document vis.js, vis.min.js licensing. Closes: #973634 * Update d/copyright . Closes: #956289 Checksums-Sha1: 889fe622d2258914979cf0d1213fd2bd29fdac4b 2628 mpich_3.4~b1-1.dsc 60c6145601666f923545463c971d24890bab 13989332 mpich_3.4~b1.orig.tar.xz 0cd7a91dfd660ede57e55f32d4ce1d63c8338919 344000 mpich_3.4~b1-1.debian.tar.xz 6bf7e1e297818bfe92ea0626fe97ddca83b7c3ba 2637412 libmpich-dev_3.4~b1-1_amd64.deb c6d7bde30ab702da43aa334ac98838f55177de60 15347024 libmpich13-dbgsym_3.4~b1-1_amd64.deb cb7ce75970d41c8d73133408115a717b4d20e46f 2353212 libmpich13_3.4~b1-1_amd64.deb dd147e8232eb7b3b705e36979a13d21e201c932d 20744 mpich-dbgsym_3.4~b1-1_amd64.deb 9a034cadd9be7f17c55d607d74468534004f9a84 263132 mpich-doc_3.4~b1-1_all.deb b0bf29c2ac5c357185463844e7ee893aa444cdf0 13249 mpich_3.4~b1-1_amd64.buildinfo d9816ed2b825ed6ed5eb7d2b3434410463b36acd 41416 mpich_3.4~b1-1_amd64.deb Checksums-Sha256: 6fe2ded8aae95cce5171c4114dc4c776997e7b88a232c097ea9a13a5146874a7 2628 mpich_3.4~b1-1.dsc 993bf2ba1201b613b3f5da8349707a328117307a37f604176db23c731220e288 13989332 mpich_3.4~b1.orig.tar.xz 8bd200b3e9543346fcaf4b32b9a90d95fbd3afee956856484d34728e190ce95b 344000 mpich_3.4~b1-1.debian.tar.xz 02e32bca58fc00be8f7c0e72dce84c1a9101c707b1c49caf527c6184eaa22823 2637412 libmpich-dev_3.4~b1-1_amd64.deb c460142c0de3c6ee2342992b3bf2459d2dbcf97886169d4dc0652f2b1a9a813a 15347024 libmpich13-dbgsym_3.4~b1-1_amd64.deb fb2541ad1c5b59d1d875853c66d109c7ec7796d6f2bd9e1904da6fac242a4068 2353212 libmpich13_3.4~b1-1_amd64.deb 3608aa02d84aa9b1d33afe2567a6f97ecfc831b0a9d056aaff71e5cdc593a5bd 20744 mpich-dbgsym_3.4~b1-1_amd64.deb 614cdb484b87351e8d12c18e2a815186a1b2c875a2b2110a748e2b2145d1b17c 263132 mpich-doc_3.4~b1-1_all.deb 28a51d6d9f51f48a1f49896ad14fd882f6b20024fe5390281f7dbb9f62dfed11 13249 mpich_3.4~b1-1_amd64.buildinfo d9b0e9b309fe8017ad388ccffd43c52ba5754e2da093ae5fd065da38a1f6baa2 41416 mpich_3.4~b1-1_amd64.deb Files: 0d575f654d8d0d6cafc3d093c812aab5 2628 devel optional mpich_3.4~b1-1.dsc d300f26e678316a087aabd7cfe135f59 13989332 devel optional mpich_3.4~b1.orig.tar.xz
Bug#957468: Can this be closed?
Can BTS #957468 be closed? -- Brian T. Smith System Fabric Works Senior Principal Engineer bsm...@systemfabricworks.com GPG Key: 0xB3C2C7B73BA3CD7F
Processed: bts gets a bit confused about bugs against two packages when their closed
Processing commands for cont...@bugs.debian.org:
> reassign 974093 src:ruby-httparty 0.18.1-1
Bug #974093 {Done: =?utf-8?q?C=C3=A9dric_Boutillier?= }
[src:ruby-httparty, src:ruby-gitlab] ruby-httparty breaks ruby-gitlab
autopkgtest: Gitlab::Client.create_merge_request_discussion posts the correct
resource
Bug reassigned from package 'src:ruby-httparty, src:ruby-gitlab' to
'src:ruby-httparty'.
No longer marked as found in versions ruby-gitlab/4.14.1-1 and
ruby-httparty/0.18.1-1.
No longer marked as fixed in versions ruby-httparty/0.18.1-2.
Bug #974093 {Done: =?utf-8?q?C=C3=A9dric_Boutillier?= }
[src:ruby-httparty] ruby-httparty breaks ruby-gitlab autopkgtest:
Gitlab::Client.create_merge_request_discussion posts the correct resource
Marked as found in versions ruby-httparty/0.18.1-1.
> fixed 974093 0.18.1-2
Bug #974093 {Done: =?utf-8?q?C=C3=A9dric_Boutillier?= }
[src:ruby-httparty] ruby-httparty breaks ruby-gitlab autopkgtest:
Gitlab::Client.create_merge_request_discussion posts the correct resource
Marked as fixed in versions ruby-httparty/0.18.1-2.
> affects 974093 ruby-gitlab
Bug #974093 {Done: =?utf-8?q?C=C3=A9dric_Boutillier?= }
[src:ruby-httparty] ruby-httparty breaks ruby-gitlab autopkgtest:
Gitlab::Client.create_merge_request_discussion posts the correct resource
Added indication that 974093 affects ruby-gitlab
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
974093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Processed: assign to package that closed the bug
Processing commands for cont...@bugs.debian.org:
> # OOPS. assigned to the FIXED version...
> notfound 975188 0.3.2-1
Bug #975188 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-native-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
No longer marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> fixed 975188 0.3.2-1
Bug #975188 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-native-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
> notfound 975185 0.3.2-1
Bug #975185 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-openssl: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
No longer marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> fixed 975185 0.3.2-1
Bug #975185 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-openssl: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
> notfound 975182 0.3.2-1
Bug #975182 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-crypto-hash: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
No longer marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> fixed 975182 0.3.2-1
Bug #975182 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-crypto-hash: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
> notfound 975181 0.3.2-1
Bug #975181 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-publicsuffix: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
No longer marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> fixed 975181 0.3.2-1
Bug #975181 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-publicsuffix: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
> notfound 975172 0.3.2-1
Bug #975172 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-hyper-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
No longer marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> fixed 975172 0.3.2-1
Bug #975172 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-hyper-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975172
975181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975181
975182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975182
975185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975185
975188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#973712: Depends on argyll which is going away
Hi, On Fri, 6 Nov 2020 03:28:53 +0100 Guillem Jover wrote: > On Tue, 2020-11-03 at 19:32:03 +0100, Moritz Muehlenhoff wrote: > > argyll is filed for removal from the archive (#966416), but > > colord-sensor-argyll > > depends on it. > > The RC bugs filed against argyll have all been fixed now. And due to the FTBFS on s390x, the package is still around on s390x, so can be added again without a trip through NEW IIUC. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: block 975929 by 976629
Processing commands for cont...@bugs.debian.org: > block 975929 by 976629 Bug #975929 [check-manifest] python-logfury: autopkgtest tries to use pip to download and install code from the internet 975929 was not blocked by any bugs. 975929 was not blocking any bugs. Added blocking bug(s) of 975929: 976629 > thanks Stopping processing here. Please contact me if you need assistance. -- 975929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976646: [Pkg-julia-devel] Bug#976646: julia: FTBFS on armhf
Hi, thanks for the report, but that is really a porter/builder box problem: > | LLVM ERROR: out of memory Seems the machine couldn't deal with the required amount ( which is considerable from my experience). I don't know what **we** can do here ... Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#925775: mediastreamer2: ftbfs with GCC-9
Dear VOIP-team, On Wed, 27 Mar 2019 19:47:03 + Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for the buster release. Do you intent to fix this in unstable soon too? The freeze is getting closer and we'd like to have this fixed in bullseye too. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: assign to package that closed the bug
Processing commands for cont...@bugs.debian.org:
> reassign 975188 src:rust-foreign-types-0.3 0.3.2-1
Bug #975188 {Done: Fabio Rafael da Rosa }
[src:rust-native-tls] rust-native-tls: FTBFS: build-dependency not installable:
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Bug reassigned from package 'src:rust-native-tls' to
'src:rust-foreign-types-0.3'.
No longer marked as found in versions rust-native-tls/0.2.4-1.
No longer marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
Bug #975188 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-native-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> affects 975188 src:rust-native-tls
Bug #975188 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-native-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Added indication that 975188 affects src:rust-native-tls
> reassign 975185 src:rust-foreign-types-0.3 0.3.2-1
Bug #975185 {Done: Fabio Rafael da Rosa }
[src:rust-openssl] rust-openssl: FTBFS: build-dependency not installable:
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Bug reassigned from package 'src:rust-openssl' to 'src:rust-foreign-types-0.3'.
No longer marked as found in versions rust-openssl/0.10.29-1.
No longer marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
Bug #975185 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-openssl: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> affects 975185 src:rust-openssl
Bug #975185 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-openssl: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Added indication that 975185 affects src:rust-openssl
> reassign 975182 src:rust-foreign-types-0.3 0.3.2-1
Bug #975182 {Done: Fabio Rafael da Rosa }
[src:rust-crypto-hash] rust-crypto-hash: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Bug reassigned from package 'src:rust-crypto-hash' to
'src:rust-foreign-types-0.3'.
No longer marked as found in versions rust-crypto-hash/0.3.4-1.
No longer marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
Bug #975182 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-crypto-hash: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> affects 975182 src:rust-crypto-hash
Bug #975182 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-crypto-hash: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Added indication that 975182 affects src:rust-crypto-hash
> reassign 975181 src:rust-foreign-types-0.3 0.3.2-1
Bug #975181 {Done: Fabio Rafael da Rosa }
[src:rust-publicsuffix] rust-publicsuffix: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Bug reassigned from package 'src:rust-publicsuffix' to
'src:rust-foreign-types-0.3'.
No longer marked as found in versions rust-publicsuffix/1.5.2-1.
No longer marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
Bug #975181 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-publicsuffix: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> affects 975181 src:rust-publicsuffix
Bug #975181 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-publicsuffix: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Added indication that 975181 affects src:rust-publicsuffix
> reassign 975172 src:rust-foreign-types-0.3 0.3.2-1
Bug #975172 {Done: Fabio Rafael da Rosa }
[src:rust-hyper-tls] rust-hyper-tls: FTBFS: build-dependency not installable:
librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Bug reassigned from package 'src:rust-hyper-tls' to
'src:rust-foreign-types-0.3'.
No longer marked as found in versions rust-hyper-tls/0.3.2-2.
No longer marked as fixed in versions rust-foreign-types-0.3/0.3.2-1.
Bug #975172 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-hyper-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Marked as found in versions rust-foreign-types-0.3/0.3.2-1.
> affects 975172 src:rust-hyper-tls
Bug #975172 {Done: Fabio Rafael da Rosa }
[src:rust-foreign-types-0.3] rust-hyper-tls: FTBFS: build-dependency not
installable: librust-foreign-types-0.3+default-dev (>= 0.3.1-~~)
Added indication that 975172 affects src:rust-hyper-tls
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975172:
Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)
@jim_p Is it possible for you to avoid putting all system information and Xorg logs in every message? It makes the thread very difficult to follow on the online bug tracker. I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it won't be my very last kernel version.
Bug#963424: sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never')
Hi Anibal, On Sun, 21 Jun 2020 22:34:58 +0200 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Do you intent to fix this in unstable soon too? The freeze is getting close and we'd like to have this fixed in bullseye. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#925818: rocksdb: ftbfs with GCC-9
Dear Laszlo, On Wed, 27 Mar 2019 19:47:52 + Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for the buster release. Do you intend to fix this soon in unstable too? The freeze of bullseye is near and we'd want to have this bug fixed. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: [RFS] kmc: arm64 autopkgtest time out
Processing control commands: > severity -1 serious Bug #954270 [src:kmc] kmc: arm64 autopkgtest time out Severity set to 'serious' from 'important' -- 954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 957007
Processing commands for cont...@bugs.debian.org: > tags 957007 + ftbfs Bug #957007 [src:arpack] arpack: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#976573: pandas: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Processing commands for cont...@bugs.debian.org:
> tags 976573 - bullseye
Bug #976573 [src:pandas] pandas: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Removed tag(s) bullseye.
> reassign 976573 python3-xlrd
Bug #976573 [src:pandas] pandas: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Bug reassigned from package 'src:pandas' to 'python3-xlrd'.
No longer marked as found in versions pandas/1.1.4+dfsg-1.
Ignoring request to alter fixed versions of bug #976573 to the same values
previously set
> merge 976573 976620
Bug #976573 [python3-xlrd] pandas: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Unable to merge bugs because:
affects of #976620 is 'pandas' not ''
Failed to merge 976573: Did not alter merged bugs.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
976573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976573
976620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#976218: file breaks nagios-plugins-contrib autopkgtest: SSL_CERT UNKNOWN www.debian.org: Unable to fetch a valid certificate issuer certificate.
Processing control commands: > tags 976218 fixed-upstream Bug #976218 [src:nagios-plugins-contrib] nagios-plugins-contrib needs update of check_ssl_cert Added tag(s) fixed-upstream. -- 976218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976218: file breaks nagios-plugins-contrib autopkgtest: SSL_CERT UNKNOWN www.debian.org: Unable to fetch a valid certificate issuer certificate.
Control: tags 976218 fixed-upstream Paul Gevers wrote... > So, let's reassign appropriately. This was fixed¹ in upstream release 1.119.0, and I'll start preparing a NMU now. FWIW, upstream is already at version 1.124.0 while Debian unstable is at 1.98.0. Christoph ¹ https://github.com/matteocorti/check_ssl_cert/commit/99673c345ebf85d643abcc51022aec76af4a signature.asc Description: PGP signature
Bug#976573: pandas: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Hi, On 06/12/20 at 18:39 +, Rebecca N. Palmer wrote: > On 05/12/20 at 13:47 +0100, Lucas Nussbaum wrote: > > Tags: bullseye sid ftbfs > > Usertags: ftbfs-20201205 ftbfs-bullseye > > Does this imply that it was also tested and failed in bullseye? The log is > marked unstable, and the test failures in it are #976620, which is probably > unstable-only. I only tested on unstable, yes. (I tag bullseye+sid as a way to say "does not affect stable") Lucas
Processed: Re: Bug#976620: xlrd: if defusedxml installed, AttributeError: 'ElementTree' object has no attribute 'getiterator'
Processing control commands: > severity -1 serious Bug #976620 [python3-xlrd] xlrd: if defusedxml installed, AttributeError: 'ElementTree' object has no attribute 'getiterator' Severity set to 'serious' from 'normal' > affects -1 pandas Bug #976620 [python3-xlrd] xlrd: if defusedxml installed, AttributeError: 'ElementTree' object has no attribute 'getiterator' Added indication that 976620 affects pandas -- 976620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcemerge 972689 901148
Processing commands for cont...@bugs.debian.org: > forcemerge 972689 901148 Bug #972689 [timidity] Sound output is only working randomly Bug #918522 [timidity] No sound with PulseAudio when an NVidia GPU is installed. Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' Removed indication that 918522 affects pulseaudio Removed indication that 901148 affects pulseaudio Removed indication that 902330 affects pulseaudio Removed indication that 904652 affects pulseaudio Removed indication that 935081 affects pulseaudio Bug #972689 [timidity] Sound output is only working randomly Marked as found in versions timidity/2.14.0-8, pulseaudio/13.0-5, and timidity/2.14.0-3. Added tag(s) upstream, moreinfo, patch, and buster-ignore. Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via pulseaudio Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via pulseaudio Bug #904652 [timidity] pulseaudio: looses device and replace it with dummy package so no sound possible Bug #935081 [timidity] Intel sound not working after upgrade to Debian 10 Merged 901148 902330 904652 918522 935081 972689 > End of message, stopping processing here. Please contact me if you need assistance. -- 901148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901148 902330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902330 904652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904652 918522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918522 935081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935081 972689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976497: python-parasail: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 Inbox [Imap]/Sent
Control: forwarded -1 https://github.com/jeffdaily/parasail-python/issues/56 Forwarded the issue upstream, hopefully we will have a fix soonish with arm64 becoming more popular.
Bug#975527: marked as done (python-furl fails autopkg tests with Python 3.9)
Your message dated Sun, 06 Dec 2020 18:52:11 + with message-id and subject line Bug#975527: fixed in python-furl 2.1.0-2 has caused the Debian Bug report #975527, regarding python-furl fails autopkg tests with Python 3.9 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.) -- 975527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-furl Version: 2.1.0-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 [...] autopkgtest [00:05:37]: test unittest: [--- .F.. == FAIL: test_join (tests.test_furl.TestFurl) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.8rbxqsfs/downtmp/build.OpJ/src/tests/test_furl.py", line 2042, in test_join assert f.url == 'wss://slrp.com/foo:1' AssertionError -- Ran 76 tests in 7.731s FAILED (failures=1) autopkgtest [00:05:45]: test unittest: ---] autopkgtest [00:05:45]: test unittest: - - - - - - - - - - results - - - - - - - - - - unittest FAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: python-furl Source-Version: 2.1.0-2 Done: =?utf-8?q?I=C3=B1aki_Malerba?= We believe that the bug you reported is fixed in the latest version of python-furl, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iñaki Malerba (supplier of updated python-furl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Dec 2020 18:41:32 +0100 Source: python-furl Architecture: source Version: 2.1.0-2 Distribution: unstable Urgency: medium Maintainer: Iñaki Malerba Changed-By: Iñaki Malerba Closes: 975527 Changes: python-furl (2.1.0-2) unstable; urgency=medium . * Disable tests failing on python3.9 (Closes: #975527) Checksums-Sha1: 236fc0ea70e43835e5b8f0c57005e33fdf5ed471 1903 python-furl_2.1.0-2.dsc 7f76e62224f78f85dec65d286db91672246cd178 2952 python-furl_2.1.0-2.debian.tar.xz c293f85de47987a56bc7b197bf277906b288274f 5914 python-furl_2.1.0-2_source.buildinfo Checksums-Sha256: 6b5ea9ccce629d6683a909bbfb5fb3200e7f368e1e94a1713ca467182608ac8e 1903 python-furl_2.1.0-2.dsc 2f9beecd1c0856176cf6cf6d539052a5690056ffee56150ec7dcd4f0e9b01b66 2952 python-furl_2.1.0-2.debian.tar.xz 907ee084902249017407f9aeba8ebdab485fe5e98e29a15d244f82c441f2644a 5914 python-furl_2.1.0-2_source.buildinfo Files: c62c709f15911917feb6406568dec954 1903 python optional python-furl_2.1.0-2.dsc 6b9bd155640e1ba2ff7722547ba785de 2952 python optional python-furl_2.1.0-2.debian.tar.xz cffda98426fced831c72959ca0f787f7 5914 python optional python-furl_2.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE1ebJmvu2M+JYt+af57yRVE86UxsFAl/NI0YUHGluYWtpQG1h bGVyYmEuc3BhY2UACgkQ57yRVE86UxtvABAAg++CU1Nd1TcfscHui71++fzGumur aTaPh3DvWUbpzT+3ImvgMxWfBtfHJPP2hUw7w2yG4eSSQwh4KQY9ZIJg5eKFpO7k Dl+DTwM28Nrqm4rbFWPpx6qM42zTys+CPPQT6I4Wwd+Zf2sduTyU7VLi2jyRd/ne ah4UCtcGz/nA5dVmOx8wC7Vn+BytJANsE4uhOy/7JZ11zoXNfOlUCribbQYIv52u LZoD+7rlh78UpwGdES6D27ZTwGFBOPZRkI071ZKCS6caPk5hkRSyvdRHEhBlYb6W YL1mAEwlyvQ8ZruHAKvNzoEs4dYueUJo+qqy7nxhS6HirL80gYgmTMjn069tJnUN uz1fwpqoynkAqNuqXs3ttojsa+wdOKx51Atm+8Ps4TADwj7mI6kRZO2An3keM/DJ EtBigDrrK2zak324lscJZ2qaPusCD8dRAzdLLwx/oF1Wh3nTYaZdWBYE8+yRoZ3S PeMx3ZTPugcv6CqxPuFWdJRzItV/QFZY36wSdfBvT0xnL7MBhCFY3do/jvQmf5/P hR9T88UqDAAhxKampv105Qvu9drR1U2AKTe5bph7oHDoT5Zgb2BpaL28b3Sn6GJr X1z6LK2Iwv4dg1SRyjWPXP6HfiJkXkNPvN8SIiPle0nhanPaweyNR2o/q/EtK+xd 8uyrOEY+9HmxfO0= =T7Tq -END PGP SIGNATURE End Message ---
Processed: https://github.com/astropy/specutils/issues/737
Processing commands for cont...@bugs.debian.org:
> forwarded 976537 https://github.com/astropy/specutils/issues/737
Bug #976537 [src:specutils] specutils: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/astropy/specutils/issues/737'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976497: python-parasail: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Hello! On 12/6/20 7:38 PM, Nilesh Patra wrote: > I've no clue of where to even start debugging this. Any help/hints are > welcome and highly appreciated. My suggestion would be to report this issue upstream [1]. Since ARM is going to be more popular in the future with Apple switching their all their machines over from x86, I expect such issues to become more relevant. Adrian > [1] https://github.com/jeffdaily/parasail-python -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Processed: Re: python-parasail: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> tags -1 help
Bug #976497 [src:python-parasail] python-parasail: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Ignoring request to alter tags of bug #976497 to the same tags previously set
--
976497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976497: python-parasail: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Control: tags -1 help
Hi Debian Arm team,
I've no clue of where to even start debugging this. Any help/hints are welcome
and highly appreciated.
Thanks and regards
Nilesh
On Sat, 5 Dec 2020 13:51:16 +0100 Lucas Nussbaum wrote:
> Source: python-parasail
> Version: 1.2.1-1
> Severity: serious
> Justification: FTBFS on arm64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201205 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on arm64 (I don't know if it also fails on amd64).
>
> Relevant part (hopefully):
>> dpkg-buildpackage
>> -
>>
>> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
>> dpkg-buildpackage: info: source package python-parasail
>> dpkg-buildpackage: info: source version 1.2.1-1
>> dpkg-buildpackage: info: source distribution unstable
>> dpkg-buildpackage: info: source changed by Nilesh Patra
>> dpkg-source --before-build .
>> dpkg-buildpackage: info: host architecture arm64
>> debian/rules clean
>> dh clean --with python3 --buildsystem=pybuild
>> dh_auto_clean -O--buildsystem=pybuild
>> I: pybuild base:232: python3.9 setup.py clean
>> running clean
>> removing '/<>/.pybuild/cpython3_3.9/build' (and everything
>> under it)
>> 'build/bdist.linux-arm64' does not exist -- can't clean it
>> 'build/scripts-3.9' does not exist -- can't clean it
>> dh_autoreconf_clean -O--buildsystem=pybuild
>> dh_clean -O--buildsystem=pybuild
>> dpkg-source -b .
>> dpkg-source: info: using source format '3.0 (quilt)'
>> dpkg-source: info: building python-parasail using existing
>> ./python-parasail_1.2.1.orig.tar.gz
>> dpkg-source: info: using patch list from debian/patches/series
>> dpkg-source: info: building python-parasail in
>> python-parasail_1.2.1-1.debian.tar.xz
>> dpkg-source: info: building python-parasail in python-parasail_1.2.1-1.dsc
>> debian/rules binary
>> dh binary --with python3 --buildsystem=pybuild
>> dh_update_autotools_config -O--buildsystem=pybuild
>> dh_autoreconf -O--buildsystem=pybuild
>> dh_auto_configure -O--buildsystem=pybuild
>> I: pybuild base:232: python3.9 setup.py config
>> running config
>> dh_auto_build -O--buildsystem=pybuild
>> I: pybuild base:232: /usr/bin/python3 setup.py build
>> running build
>> running build_py
>> creating /<>/.pybuild/cpython3_3.9/build/parasail
>> copying parasail/bindings_v2.py ->
>> /<>/.pybuild/cpython3_3.9/build/parasail
>> copying parasail/__init__.py ->
>> /<>/.pybuild/cpython3_3.9/build/parasail
>> copying parasail/bindings_v1.py ->
>> /<>/.pybuild/cpython3_3.9/build/parasail
>> dh_auto_test -O--buildsystem=pybuild
>> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
>> python3.9 -m pytest tests
>> = test session starts
>> ==
>> platform linux -- Python 3.9.1rc1, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
>> rootdir: /<>
>> collected 16 items
>> tests/test_basic.py ...Segmentation fault
>> E: pybuild pybuild:353: test: plugin distutils failed with: exit code=139:
>> cd /<>/.pybuild/cpython3_3.9/build; python3.9 -m pytest tests
>> >> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
>> 3.9 returned exit code
signature.asc
Description: OpenPGP digital signature
Processed: Re: python-parasail: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> tags -1 help
Bug #976497 [src:python-parasail] python-parasail: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) help.
--
976497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976497: python-parasail: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Control: tags -1 help
Hi Debian Arm team,
I've no clue of where to even start debugging this. Any help/hints are welcome
and highly appreciated.
Thanks and regards
Nilesh
On Sat, 5 Dec 2020 13:51:16 +0100 Lucas Nussbaum wrote:
> Source: python-parasail
> Version: 1.2.1-1
> Severity: serious
> Justification: FTBFS on arm64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201205 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on arm64 (I don't know if it also fails on amd64).
>
> Relevant part (hopefully):
> > dpkg-buildpackage
> > -
> >
> > Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> > dpkg-buildpackage: info: source package python-parasail
> > dpkg-buildpackage: info: source version 1.2.1-1
> > dpkg-buildpackage: info: source distribution unstable
> > dpkg-buildpackage: info: source changed by Nilesh Patra
> >
> > dpkg-source --before-build .
> > dpkg-buildpackage: info: host architecture arm64
> > debian/rules clean
> > dh clean --with python3 --buildsystem=pybuild
> > dh_auto_clean -O--buildsystem=pybuild
> > I: pybuild base:232: python3.9 setup.py clean
> > running clean
> > removing '/<>/.pybuild/cpython3_3.9/build' (and everything
> > under it)
> > 'build/bdist.linux-arm64' does not exist -- can't clean it
> > 'build/scripts-3.9' does not exist -- can't clean it
> > dh_autoreconf_clean -O--buildsystem=pybuild
> > dh_clean -O--buildsystem=pybuild
> > dpkg-source -b .
> > dpkg-source: info: using source format '3.0 (quilt)'
> > dpkg-source: info: building python-parasail using existing
> > ./python-parasail_1.2.1.orig.tar.gz
> > dpkg-source: info: using patch list from debian/patches/series
> > dpkg-source: info: building python-parasail in
> > python-parasail_1.2.1-1.debian.tar.xz
> > dpkg-source: info: building python-parasail in python-parasail_1.2.1-1.dsc
> > debian/rules binary
> > dh binary --with python3 --buildsystem=pybuild
> > dh_update_autotools_config -O--buildsystem=pybuild
> > dh_autoreconf -O--buildsystem=pybuild
> > dh_auto_configure -O--buildsystem=pybuild
> > I: pybuild base:232: python3.9 setup.py config
> > running config
> > dh_auto_build -O--buildsystem=pybuild
> > I: pybuild base:232: /usr/bin/python3 setup.py build
> > running build
> > running build_py
> > creating /<>/.pybuild/cpython3_3.9/build/parasail
> > copying parasail/bindings_v2.py ->
> > /<>/.pybuild/cpython3_3.9/build/parasail
> > copying parasail/__init__.py ->
> > /<>/.pybuild/cpython3_3.9/build/parasail
> > copying parasail/bindings_v1.py ->
> > /<>/.pybuild/cpython3_3.9/build/parasail
> > dh_auto_test -O--buildsystem=pybuild
> > I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> > python3.9 -m pytest tests
> > = test session starts
> > ==
> > platform linux -- Python 3.9.1rc1, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> > rootdir: /<>
> > collected 16 items
> > tests/test_basic.py ...Segmentation fault
>> E: pybuild pybuild:353: test: plugin distutils failed with: exit code=139:
>> cd /<>/.pybuild/cpython3_3.9/build; python3.9 -m pytest tests
>> >> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
>> 3.9 returned exit code 13
signature.asc
Description: OpenPGP digital signature
Bug#959858: marked as done (snort-doc: missing Breaks+Replaces: snort (<< 2.9.15))
Your message dated Sun, 06 Dec 2020 18:07:10 + with message-id and subject line Bug#959858: fixed in snort 2.9.15.1-4 has caused the Debian Bug report #959858, regarding snort-doc: missing Breaks+Replaces: snort (<< 2.9.15) 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.) -- 959858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snort-doc Version: 2.9.15.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../snort-doc_2.9.15.1-2_all.deb ... Unpacking snort-doc (2.9.15.1-2) ... dpkg: error processing archive /var/cache/apt/archives/snort-doc_2.9.15.1-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/snort/README.PLUGINS', which is also in package snort 2.9.7.0-5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/snort-doc_2.9.15.1-2_all.deb This is probably caused by a behavioral change of dh_installdocs in recent debhelper compat levels. cheers, Andreas snort=2.9.7.0-5_snort-doc=2.9.15.1-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: snort Source-Version: 2.9.15.1-4 Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= We believe that the bug you reported is fixed in the latest version of snort, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña (supplier of updated snort 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: Sun, 06 Dec 2020 17:23:14 +0100 Source: snort Architecture: source Version: 2.9.15.1-4 Distribution: unstable Urgency: high Maintainer: Javier Fernández-Sanguino Peña Changed-By: Javier Fernández-Sanguino Peña Closes: 959858 Changes: snort (2.9.15.1-4) unstable; urgency=high . * debian/snort.docs, debian/snort-doc.docs debian/rules: Add README.csv and README.PLUGINS to the snort package and remove from the snort-doc. This fixes errors when upgrading from 2.9.7.0-5 which included these documents. (Closes: #959858) * debian/patches/fix_compile_errors: Add a patch to fix a compile error * debian/rules: Disable performance profiling to fix a compile error when linking (and also because it is not required in production systems) * debian/snort.postinst: Replace tempfile (deprecated) with mktemp * debian/snort.install: Add the binaries from the debian/tmp to avoid errors from dh_missing Checksums-Sha1: 68ad5746937dbe0911e2f48e1d6852a04aa63d10 2443 snort_2.9.15.1-4.dsc fc4295df4321dba0b54497f221daaf37388fca8f 754008 snort_2.9.15.1-4.debian.tar.xz bc361613a92682c2afb5f5618330f9645bfcb8e9 12329 snort_2.9.15.1-4_i386.buildinfo Checksums-Sha256: a979e768f514ae303e8daedf1cddcf8028782f8b19f90ffd238d9ceae3b12de8 2443 snort_2.9.15.1-4.dsc de2e303e535d9b6251e4efcbe4d5f8af45d0f20f6871c2760d9ec152578dafce 754008 snort_2.9.15.1-4.debian.tar.xz d3cd1df4a13a18efec6643a8698bb6ee38550781659405bdeab5eb2b9ffc9775 12329 snort_2.9.15.1-4_i386.buildinfo Files: 2ecb67a3e9f27f7e4995fdbb6b9260d6 2443 net optional snort_2.9.15.1-4.dsc e30f03e84955e0391d0ae9e42bc2fbce 754008 net optional snort_2.9.15.1-4.debian.tar.xz 4dc2824ace92af65d80bd732b303cdf6 12329 net optional snort_2.9.15.1-4_i386.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAl/NF90ACgkQix9vSKsl
Bug#976310: marked as done (node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function)
Your message dated Sun, 06 Dec 2020 18:04:08 + with message-id and subject line Bug#976310: fixed in gitlab 13.4.6-3 has caused the Debian Bug report #976310, regarding node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function 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.) -- 976310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-compression-webpack-plugin Version: 3.0.1-3 Severity: serious Control: affects -1 gitlab Installation of gitlab started failing with the following error. I think this is related to the recent update of node-schema-utils. Webpacking... /usr/share/nodejs/webpack/node_modules/webpack-cli/bin/cli.js:93 throw err; ^ TypeError: (0 , _schemaUtils.validate) is not a function at new CompressionPlugin (/usr/share/nodejs/compression-webpack-plu gin/dist/index.js:40:31) at Object. (/etc/gitlab/webpack.config.js:451:41) at Module._compile (/usr/share/nodejs/webpack/node_modules/v8-compi le-cache/v8-compile-cache.js:194:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:10 35:10) at Module.load (internal/modules/cjs/loader.js:879:32) at Function.Module._load (internal/modules/cjs/loader.js:724:14) at Module.require (internal/modules/cjs/loader.js:903:19) at require (/usr/share/nodejs/webpack/node_modules/v8-compile-cache /v8-compile-cache.js:161:20) at WEBPACK_OPTIONS (/usr/share/nodejs/webpack/node_modules/webpack- cli/bin/utils/convert-argv.js:114:13) at requireConfig (/usr/share/nodejs/webpack/node_modules/webpack-cl i/bin/utils/convert-argv.js:116:6) at /usr/share/nodejs/webpack/node_modules/webpack-cli/bin/utils/con vert-argv.js:123:17 at Array.forEach () at module.exports (/usr/share/nodejs/webpack/node_modules/webpack-c li/bin/utils/convert-argv.js:121:15) at /usr/share/nodejs/webpack/node_modules/webpack-cli/bin --- End Message --- --- Begin Message --- Source: gitlab Source-Version: 13.4.6-3 Done: Sruthi Chandran We believe that the bug you reported is fixed in the latest version of gitlab, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sruthi Chandran (supplier of updated gitlab 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: Sun, 06 Dec 2020 22:54:05 +0530 Source: gitlab Architecture: source Version: 13.4.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Sruthi Chandran Closes: 976310 Changes: gitlab (13.4.6-3) unstable; urgency=medium . [ Pirate Praveen ] * Use packaged version of css-loader, raw-loader, file-loader, style-loader and copy-webpack-plugin * Add schema-utils 3.0, mkdirp 1.0 and loader-utils 2.0 to package.json to force yarn to move incompatible versions from gitlab's node_modules directory to node_modules directory of other modules (Closes: #976310) Checksums-Sha1: a2306374260642fb932463bc4aed6870f74b78c2 3545 gitlab_13.4.6-3.dsc 5c686d804469dca27314c0dabeeed75c75a4908b 83280 gitlab_13.4.6-3.debian.tar.xz 37ba16aadd7c603fd7a8d1eaab8c8ef46156ec55 8933 gitlab_13.4.6-3_amd64.buildinfo Checksums-Sha256: 4a275ba2a4dfc429a273a52f8c64dfd5ca208077ea0a6ac5f516c0ba8ae65af0 3545 gitlab_13.4.6-3.dsc 5c52a96366ba438dbda3a5c014a7b41e52b0bc4f9aef21e7f28f6f785e9c0f45 83280 gitlab_13.4.6-3.debian.tar.xz 33562a90fdab6d89b8a4e1caa035eb88b27cde8e758e1f845d5592071a6553a0 8933 gitlab_13.4.6-3_amd64.buildinfo Files: f00a1721591b3492a827a64f9d123b4e 3545 contrib/net optional gitlab_13.4.6-3.dsc befc3b9693ff1adc5dddae2e15b7e746 83280 contrib/net optional gitlab_13.4.6-3.debian.tar.xz 0eafbfafbb78d0b2bc9d7635149d3b22 8933 contrib/net optional gitlab_13.4.6-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQGyBAEBCAAdFiEEcd3Fxr6GmkZB13n+x+ob4VdN7V0FAl/NF8MACgkQx+ob4VdN 7V06swv4tudxTKqpBSgKPGaehGA7//FoxdeY+MTtQZmnrPfCtOBuyPrAf+Jm0Rde kcgNUPlHZOlPKMb2+V4t6ACw4LJRsxsSX6NjrLXm6ox8RM9TgdfI1ITh877OkyL4
Bug#962203: DeprecationWarning: isAlive() is deprecated, use is_alive() instead
Package: debdelta
Version: 0.65
Followup-For: Bug #962203
X-Debbugs-Cc: calumlikesapple...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I have created an attached a patch. It is also availible as merge request !2
in the salsa repository.
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages debdelta depends on:
ii binutils 2.35.1-3
ii bzip2 1.0.8-4
ii libbz2-1.01.0.8-4
ii libc6 2.31-4
ii python3 3.8.6-1
ii python3-requests 2.24.0+dfsg-1
ii zlib1g1:1.2.11.dfsg-2
Versions of packages debdelta recommends:
ii bsdiff 4.3-21+b1
ii gnupg-agent 2.2.20-1
ii gnupg2 2.2.20-1
ii gpg-agent [gnupg-agent] 2.2.20-1
ii python3-apt 2.1.6
ii python3-debian 0.1.38
ii xdelta 1.1.3-9.3
ii xdelta3 3.0.11-dfsg-1+b1
ii xz-utils [lzma] 5.2.4-1+b1
Versions of packages debdelta suggests:
ii debdelta-doc 0.65
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl/NHNgdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzK5rA//S3+ySeshMWhTEp38
KOrKKWvR/vGOb2MjPILXU6VJfAcw7tIf/IbzvGkj3QM08f1eF3RElP4UwC4NCpj6
oTEYgq88lE0YTqYrdRJopM70pmcDArzvFpysudonUHJ8k2sUwr/5R18S8BooiGDw
iOs7BaAv3vJNyKfeYSJlIdMLiq1u52z6xooSg92Rb6b/rBC3il5frkpUsy4L/Jid
AHEGDhTAtyvwof/zdyjwVnMQvxoS5lsm5hkc7RNFpndkvRONTWNNOa0raYucbQ3K
vitJ+7BuNZ3GF/yi86+L1krOGpv5E5lbdlmhtqUMd1RcYw1VZpEcJ+3D45dDOxSg
wbIFV+ud+ATXC7yVYMQhDv/S3GSb/sKx7OrLJZX/67BrQZqMM3eB4BXarJe1o9gV
56znmh+hzGoGkzaZJmKHRNdhYK97rWXYts/4pUAnpICDkhMBbQ/D4OgVgA18dRR6
h4CsU+ynf0Z6Xb0bW9tPmkbj0a91mOvqNRvO1E9kwnSolsAjqJQ7HmQp0GLnDQfy
nxdCMGTIQOIWepdF8bi2WiGaSwvK2f2Q1LyxqEMsBf68uH3+IcCxsPKCrZ55w+gy
7NxRvlLwYilTFN20aZSTtFt7ntDPzLy6J9BulukLNjgD1AoW00Y/mlG+Af/hxMhc
fNhgaK9EUfEhOQeqOyoorBwEjok=
=4QZH
-END PGP SIGNATURE-
>From 4821b3f1fdb9118ba3c80b8077af63b5006d6ddb Mon Sep 17 00:00:00 2001
From: Calum McConnell
Date: Sun, 6 Dec 2020 12:53:52 -0500
Subject: [PATCH] Fix isAlive -> is_alive
---
debdelta/debdelta | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/debdelta/debdelta b/debdelta/debdelta
index b4a79c1..b7f258c 100755
--- a/debdelta/debdelta
+++ b/debdelta/debdelta
@@ -5460,9 +5460,9 @@ def delta_upgrade_(args):
#do something useful in the meantime
debs_down_size=0
debs_down_time=0
- if patching_thread.isAlive() and no_delta and VERBOSE > 1 :
+ if patching_thread.is_alive() and no_delta and VERBOSE > 1 :
logger.info(' Downloading deltas done, downloading debs while waiting for
patching thread.')
- while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
+ while patching_thread.is_alive() or ('a' in DEB_POLICY and no_delta):
if no_delta:
uri, newdeb = no_delta.pop()
thread_returns['downloaduri']=os.path.basename(uri)
@@ -5481,12 +5481,12 @@ def delta_upgrade_(args):
if http_conns[i] != None :
http_conns[i].close()
- while patching_thread.isAlive():
+ while patching_thread.is_alive():
time.sleep(0.1)
#terminate progress report
thread_returns['STOP']=True
- while progress_thread != None and progress_thread.isAlive():
+ while progress_thread != None and progress_thread.is_alive():
time.sleep(0.1)
if DO_PROGRESS:
--
2.29.2
Bug#957420: lib3mf: diff for NMU version 1.8.1+ds-3.1
On Sun, 06 Dec 2020 18:26:44 +0100, Torsten Paul wrote: > On 06.12.20 02:37, gregor herrmann wrote: > > Joel Ray Holveck has prepared an NMU for lib3mf (versioned as > > 1.8.1+ds-3.1) and I've uploaded it to DELAYED/7. Please feel free to > > tell me if I should delay it longer. > Thanks, for the NMU, that's great. I appreciate the help as > I'm still stuck with trying to get an OpenSCAD release out. That's great to hear, because the lack of OpenSCAD in testing was the reason why I came across this bug :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Peter Ratzenbeck: Lady Nothings Toye Puffe signature.asc Description: Digital Signature
Bug#976492: marked as done (bochs: FTBFS on arm64: ld: cannot represent machine `i386')
Your message dated Sun, 06 Dec 2020 17:48:34 +
with message-id
and subject line Bug#976492: fixed in bochs 2.6.11+dfsg-4
has caused the Debian Bug report #976492,
regarding bochs: FTBFS on arm64: ld: cannot represent machine `i386'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
976492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bochs
Version: 2.6.11+dfsg-3
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> make[2]: Entering directory '/<>/bios'
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
> biossums.o biossums.c
> cc -Wl,-z,relro -Wl,-z,now biossums.o -o biossums
> i686-linux-gnu-gcc -fno-stack-protector "-DBIOS_BUILD_DATE=\"`date -u -d '
> Sun Jan 5 08:36:00 CET 2020' '+%m/%d/%y'`\"" -E -P rombios.c > _rombios_.c
> bcc -o rombios.s -C-c -D__i86__ -0 -S _rombios_.c
> sed -e 's/^\.text//' -e 's/^\.data//' rombios.s > _rombios_.s
> as86 _rombios_.s -b tmp.bin -u- -w- -g -0 -j -O -l rombios.txt
> perl ./makesym.perl < rombios.txt > rombios.sym
> mv tmp.bin rombios16.bin
> ./biossums rombios16.bin
>
>
> PCI-Bios header at: 0x9620
> Current checksum: 0x07
> Calculated checksum: 0x07
>
>
> $PIR header at: 0x99D0
> Current checksum: 0x37
> Calculated checksum: 0x37
>
>
> $PnP header at: 0x9BB0
> Current checksum: 0xD1
> Calculated checksum: 0xB1 Setting checksum.
>
>
> Bios checksum at: 0x
> Current checksum: 0x00
> Calculated checksum: 0x15 Setting checksum.
> rm -f _rombios_.s
> i686-linux-gnu-gcc -fno-stack-protector -c -o rombios32start.o
> rombios32start.S
> cpp -P acpi-dsdt.dsl acpi-dsdt.dsl.i
> iasl -tc -p acpi-dsdt.hex acpi-dsdt.dsl.i
> acpi-dsdt.dsl.i 19: Device(PCI0) {
> Warning 3073 - Multiple types ^ (Device object requires either a
> _HID or _ADR, but not both)
>
> acpi-dsdt.dsl.i157: Method (_CRS, 0, NotSerialized)
> Remark 2120 - ^ Control Method should be
> made Serialized due to creation of named objects within
> (\_SB.PCI0.ISA.KBD._CRS)
>
> acpi-dsdt.dsl.i159: Name (TMP, ResourceTemplate ()
> Remark 2173 - ^ Creation of named
> objects within a method is highly inefficient, use globals or method local
> variables instead (\_SB.PCI0.ISA.KBD._CRS)
>
> acpi-dsdt.dsl.i186: Method (_CRS, 0, NotSerialized)
> Remark 2120 - ^ Control Method should be
> made Serialized due to creation of named objects within
> (\_SB.PCI0.ISA.MOU._CRS)
>
> acpi-dsdt.dsl.i188: Name (TMP, ResourceTemplate ()
> Remark 2173 -^ Creation of named
> objects within a method is highly inefficient, use globals or method local
> variables instead (\_SB.PCI0.ISA.MOU._CRS)
>
> acpi-dsdt.dsl.i202: Method (_CRS, 0, NotSerialized)
> Remark 2120 - ^ Control Method should be made
> Serialized due to creation of named objects within (\_SB.PCI0.ISA.FDC0._CRS)
>
> acpi-dsdt.dsl.i204: Name (BUF0, ResourceTemplate ()
> Remark 2173 - ^ Creation of named objects within a
> method is highly inefficient, use globals or method local variables instead
> (\_SB.PCI0.ISA.FDC0._CRS)
>
> acpi-dsdt.dsl.i230: Method (_CRS, 0, NotSerialized)
> Remark 2120 - ^ Control Method should be made
> Serialized due to creation of named objects within (\_SB.PCI0.ISA.LPT._CRS)
>
> acpi-dsdt.dsl.i232: Name (BUF0, ResourceTemplate ()
> Remark 2173 - ^ Creation of named objects within a
> method is highly inefficient, use globals or method local variables instead
> (\_SB.PCI0.ISA.LPT._CRS)
>
> acpi-dsdt.dsl.i257: Method (_CRS, 0, NotSerialized)
> Remark 2120 - ^ Control Method should be made
> Serialized due to creation of named objects within (\_SB.PCI0.ISA.COM1._CRS)
>
> acpi-dsdt.dsl.i259: Name (BUF0, ResourceTemplate ()
> Remark 2173 - ^ Creation of named objects within a
> method is highly inefficient, use globals or method local variables instead
Bug#973026: marked as done (python-executing's autopkg tests fail with python3.9)
Your message dated Sun, 06 Dec 2020 17:35:49 + with message-id and subject line Bug#973026: fixed in python-executing 0.5.3-1 has caused the Debian Bug report #973026, regarding python-executing's autopkg tests fail with python3.9 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.) -- 973026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-executing Version: 0.4.3-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 autopkgtest [22:01:06]: test unittest: [--- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.0jbyozrd/downtmp/build.4ij/src/tests/test_main.py", line 522, in assert tester[1 + 2] is tester File "/tmp/autopkgtest-lxc.0jbyozrd/downtmp/build.4ij/src/tests/utils.py", line 45, in __getitem__ self.check(node.slice.value, item) AttributeError: 'BinOp' object has no attribute 'value' autopkgtest [22:01:07]: test unittest: ---] --- End Message --- --- Begin Message --- Source: python-executing Source-Version: 0.5.3-1 Done: =?utf-8?q?I=C3=B1aki_Malerba?= We believe that the bug you reported is fixed in the latest version of python-executing, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iñaki Malerba (supplier of updated python-executing package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Dec 2020 18:00:55 +0100 Source: python-executing Architecture: source Version: 0.5.3-1 Distribution: unstable Urgency: medium Maintainer: Iñaki Malerba Changed-By: Iñaki Malerba Closes: 973026 Changes: python-executing (0.5.3-1) unstable; urgency=medium . * New upstream version 0.5.3 (Closes: #973026) * d/watch: Bump to version 4 * d/control: Bump standards and debhelper-compat versions Checksums-Sha1: ad2e0ac9a972dbef0d062a18e7b28ed079d05741 2118 python-executing_0.5.3-1.dsc ad1cc2f9da69bd28c381aae410a21574ccc14e34 303234 python-executing_0.5.3.orig.tar.gz 027377490c7167bcaf7628436016d719831b63b0 2720 python-executing_0.5.3-1.debian.tar.xz 51aa492c460818b689ed93e3dfd5c559676597a2 6028 python-executing_0.5.3-1_source.buildinfo Checksums-Sha256: 9f0f85e2c7ad95d5230ec9ef750b1f60c8312b827fa18b6bb9620fa68cc846b7 2118 python-executing_0.5.3-1.dsc 5ee1a7342f09720494e425fbafb1b2755db360aa0d0bd25917fdaa4ac9ceadba 303234 python-executing_0.5.3.orig.tar.gz 6cafe63e50ba6f84d5198ff3d69efe35bc655e45155a23f7b0dca4b9001e04c1 2720 python-executing_0.5.3-1.debian.tar.xz a0f8a137df7d9ea38c434bdd0c6244e17a40a9c4b79e026ec9ed6c3a3411da86 6028 python-executing_0.5.3-1_source.buildinfo Files: b4a64da286ddb9beb9d2051b41652fdb 2118 python optional python-executing_0.5.3-1.dsc 4a8f67219c62a5ca70cfdd8f94fb502e 303234 python optional python-executing_0.5.3.orig.tar.gz c3919c43da0f212aa1bd64bf309a8992 2720 python optional python-executing_0.5.3-1.debian.tar.xz d0cb465039d5b358b9fa44af4e799cf0 6028 python optional python-executing_0.5.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE1ebJmvu2M+JYt+af57yRVE86UxsFAl/NEMoUHGluYWtpQG1h bGVyYmEuc3BhY2UACgkQ57yRVE86UxtEDxAAhG3oClxYqfFmoZHc/i8+sAJqHOoo R8C1eGI0fyk8MbfKgEiOammCFYLq1XfqmidFfsK+nCYDLI+qOO31JLxPR2S83VhV Nw83FpTWptDczrbdcGI6Z7NtKR37hfgzoKOo4vjuISgXl8ztzMRh9BOzy7WKxRr1 RYTxwGYO7gAmvdshxvHeTbV4qx990CPsCMsli7lNSeqUXq+lkiHOXFugSYHkRZBT IkTZmwTknZtMEefYie0TMgkMIHbQ64femQB3RuDaHoekW1rQ1N6NqSi0lLzi47Zp osDdFg6rFHQZxdShGYqmiHJec+jJkVrgQhZNEiLJyMHjOQ09KcacQxHXlwGZdLOb vPmi8LZcVNJbBC6WEb6inDxHVr9ResVSFSLn9WO/vtc654n/6DyCAyz+OVw3YdM/ rYXCziiVdI+hlyTOWVwavOJ/zZlq7pRYSbEQHUcKHHPyQlFUeCWpe08EXt2hUMel bdcX6/H9VJLUBYbrzQCBmrZcbIhX28cxkXvKr+ix0TmG+x2iNhweEWQTo5Unti7X yWCQdq//ynUw4bYpuId4jnlWDLjwXkCndr517I47HQp2pqyHaHyLlVuadtqVVOan dRyCuubxCPUhBa07MXSMOUMUVQE+9l1HMKNY/DwUcPrlrygJ1bt9DYkKfJUED3hy IZfMs2LgLyE3FZ8= =DEuR -END PGP SIGNATURE End Message ---
Processed: Re: DeprecationWarning: isAlive() is deprecated, use is_alive() instead
Processing control commands: > severity -1 grave Bug #962203 [debdelta] DeprecationWarning: isAlive() is deprecated, use is_alive() instead Severity set to 'grave' from 'normal' -- 962203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: add forwarded information
Processing commands for cont...@bugs.debian.org: > forwarded 976270 https://tickets.puppetlabs.com/browse/FORGE-575 Bug #976270 [ruby-puppet-forge] ruby-puppet-forge: autopkgtest/ftbfs with ruby-faraday-middleware 1.x Set Bug forwarded-to-address to 'https://tickets.puppetlabs.com/browse/FORGE-575'. > End of message, stopping processing here. Please contact me if you need assistance. -- 976270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957420: lib3mf: diff for NMU version 1.8.1+ds-3.1
Hi! On 06.12.20 02:37, gregor herrmann wrote: > Joel Ray Holveck has prepared an NMU for lib3mf (versioned as > 1.8.1+ds-3.1) and I've uploaded it to DELAYED/7. Please feel free to > tell me if I should delay it longer. Thanks, for the NMU, that's great. I appreciate the help as I'm still stuck with trying to get an OpenSCAD release out. ciao, Torsten.
Processed (with 1 error): nova: title 976590 a unit test fails in arm64
Processing commands for cont...@bugs.debian.org: > title 976590 a unit test fails in arm64 Unknown command or malformed arguments to command. > severity 976590 important Bug #976590 [src:nova] nova: FTBFS: make[1]: pyversions: No such file or directory Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 976590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976590: How should I fix?
Hi, There's multiple ways how this could be fixed, probably one should be to disable the failing unit test if not running on amd64. I'll open an issue upstream for this, and see how it goes. In the mean while (ie: before I get an answer from upstream), I'll downgrade this bug to important. Cheers, Thomas Goirand (zigo)
Bug#976542: marked as done (python-biopython: FTBFS: AssertionError: 0 != 24)
Your message dated Sun, 06 Dec 2020 16:55:21 +
with message-id
and subject line Bug#976542: fixed in python-biopython 1.78+dfsg-4
has caused the Debian Bug report #976542,
regarding python-biopython: FTBFS: AssertionError: 0 != 24
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.)
--
976542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biopython
Version: 1.78+dfsg-3
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p Tests_avoid
> for avoid in PAML_tools EmbossPhylipNew MSAProbs_tool NACCESS_tool
> PopGen_GenePop PopGen_GenePop_EasyController XXmotif_tool PDB_ResidueDepth
> mmtf mmtf_online raxml_tool BioSQL_MySQLdb BioSQL_psycopg2 \
> ; do \
> mv Tests/test_${avoid}.py Tests_avoid ; \
> done
> mv: cannot stat 'Tests/test_NACCESS_tool.py': No such file or directory
> # For the doc package we need a clean testsuite without all the remaining
> files. So keep a clean copy here
> mkdir -p debian/tmp_tests
> cp -a Tests debian/tmp_tests
> # remove duplicated file
> rm -f debian/tmp_tests/Tests/Quality/example.fastq.gz
> # We also keep the tests we need to avoid for later inspection
> cp -a Tests_avoid debian/tmp_tests
> # in the Debian package dialign it is not needed to set DIALIGN2_DIR but the
> test is verifying this dir
> # to run the EMBOSS test test_Emboss also requires to have the environment
> variable EMBOSS_ROOT set
> LC_ALL=C.UTF-8 dh_auto_test -- --test --system=custom \
> --test-args='set -e; \
> mkdir -p {build_dir}/home; \
> mkdir -p {build_dir}/Doc/examples; \
> cp -a Doc/Tutorial.tex {build_dir}/Doc; \
> cp -a Doc/Tutorial {build_dir}/Doc; \
> cp -a Doc/examples {build_dir}/Doc; \
> cp -a Tests {build_dir}; \
> cd {build_dir}/Tests; \
> env DIALIGN2_DIR=/usr/share/dialign
> EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter} run_tests.py
> --offline'
> pybuild --test -i python{version} -p "3.8 3.9" --test --system=custom
> "--test-args=set -e; \\\
> mkdir -p {build_dir}/home; \\\
> mkdir -p {build_dir}/Doc/examples; \\\
> cp -a Doc/Tutorial.tex {build_dir}/Doc; \\\
> cp -a Doc/Tutorial {build_dir}/Doc; \\\
> cp -a Doc/examples {build_dir}/Doc; \\\
> cp -a Tests {build_dir}; \\\
> cd {build_dir}/Tests; \\\
> env DIALIGN2_DIR=/usr/share/dialign
> EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter} run_tests.py
> --offline"
> I: pybuild base:232: set -e; \
> mkdir -p
> /<>/.pybuild/cpython3_3.8/build/home; \
> mkdir -p
> /<>/.pybuild/cpython3_3.8/build/Doc/examples; \
> cp -a Doc/Tutorial.tex
> /<>/.pybuild/cpython3_3.8/build/Doc; \
> cp -a Doc/Tutorial
> /<>/.pybuild/cpython3_3.8/build/Doc; \
> cp -a Doc/examples
> /<>/.pybuild/cpython3_3.8/build/Doc; \
> cp -a Tests
> /<>/.pybuild/cpython3_3.8/build; \
> cd
> /<>/.pybuild/cpython3_3.8/build/Tests; \
> env DIALIGN2_DIR=/usr/share/dialign
> EMBOSS_ROOT=/usr/lib/emboss
> HOME=/<>/.pybuild/cpython3_3.8/build/home python3.8 run_tests.py
> --offline
> test_Ace ... ok
> test_Affy ... ok
> test_AlignIO ... ok
> test_AlignIO_ClustalIO ... ok
> test_AlignIO_EmbossIO ... ok
> test_AlignIO_FastaIO ... ok
> test_AlignIO_MauveIO ... ok
> test_AlignIO_PhylipIO ... ok
> test_AlignIO_convert ... ok
> test_AlignInfo ... ok
> test_Application ... ok
> test_BWA_tool ... ok
> test_BioSQL_MySQLdb_online ... skipping. internet not available
> test_BioSQL_mysql_connector ... skipping. BioSQL test configuration file
> biosql.ini missing (see biosql.ini.sample)
> test_BioSQL_mysql_connector_online ... skipping. internet not available
> test_BioSQL_psycopg2_online
Bug#973017: marked as done (python-django-import-export 's autopkg tests are failing with python3.9)
Your message dated Sun, 06 Dec 2020 17:35:01 +0100 with message-id <3b78c0280ad367aae469ee8fd77fe5aed155c256.ca...@gmail.com> and subject line Closing : fixed package migrated to testing has caused the Debian Bug report #973017, regarding python-django-import-export 's autopkg tests are failing with python3.9 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.) -- 973017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-django-import-export Version: 2.4.0-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 autopkgtest [19:11:54]: test command1: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import import_export; print(import_export)" ; done autopkgtest [19:11:54]: test command1: [--- Testing with python3.9: bash: line 1: python3.9: command not found --- End Message --- --- Begin Message --- Hi, the fixed package migrated to testing, so I can now close this. Cheers, JP--- End Message ---
Bug#976567: marked as done (libhmsbeagle: FTBFS: GPUInterface.h:221:27: error: there are no arguments to ‘malloc’ that depend on a template parameter, so a declaration of ‘malloc’ must be available [-
Your message dated Sun, 06 Dec 2020 16:23:07 +
with message-id
and subject line Bug#976567: fixed in libhmsbeagle 3.1.2+dfsg-9
has caused the Debian Bug report #976567,
regarding libhmsbeagle: FTBFS: GPUInterface.h:221:27: error: there are no
arguments to ‘malloc’ that depend on a template parameter, so a declaration of
‘malloc’ must be available [-fpermissive]
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.)
--
976567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhmsbeagle
Version: 3.1.2+dfsg-8
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
> -I../../libhmsbeagle -I/<> -I/<> -Wdate-time
> -D_FORTIFY_SOURCE=2 -I/usr/lib/jvm/java-11-openjdk-arm64/include
> -I/usr/lib/jvm/java-11-openjdk-arm64/include/linux -O3 -std=c++11 -D
> FW_OPENCL -I/usr/include/CL/include -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c -o libhmsbeagle_opencl_la-OpenCLPlugin.lo `test -f
> 'OpenCLPlugin.cpp' || echo './'`OpenCLPlugin.cpp
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../libhmsbeagle
> -I/<> -I/<> -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/lib/jvm/java-11-openjdk-arm64/include
> -I/usr/lib/jvm/java-11-openjdk-arm64/include/linux -O3 -std=c++11 -D
> FW_OPENCL -I/usr/include/CL/include -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c OpenCLPlugin.cpp -fPIC -DPIC -o
> .libs/libhmsbeagle_opencl_la-OpenCLPlugin.o
> In file included from /usr/include/CL/cl.h:20,
> from /usr/include/CL/opencl.h:24,
> from /<>/libhmsbeagle/GPU/GPUInterface.h:60,
> from /<>/libhmsbeagle/GPU/BeagleGPUImpl.h:39,
> from OpenCLPlugin.cpp:8:
> /usr/include/CL/cl_version.h:22:104: note: ‘#pragma message: cl_version.h:
> CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)’
>22 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not
> defined. Defaulting to 300 (OpenCL 3.0)")
> |
> ^
> In file included from /<>/libhmsbeagle/GPU/BeagleGPUImpl.h:39,
> from OpenCLPlugin.cpp:8:
> /<>/libhmsbeagle/GPU/GPUInterface.h: In member function ‘void
> opencl_device::GPUInterface::PrintfDeviceVector(GPUPtr, int, double, int*,
> Real)’:
> /<>/libhmsbeagle/GPU/GPUInterface.h:221:27: error: there are no
> arguments to ‘malloc’ that depend on a template parameter, so a declaration
> of ‘malloc’ must be available [-fpermissive]
> 221 | Real* hPtr = (Real*) malloc(sizeof(Real) * length);
> | ^~
> /<>/libhmsbeagle/GPU/GPUInterface.h:221:27: note: (if you use
> ‘-fpermissive’, G++ will accept your code, but allowing the use of an
> undeclared name is deprecated)
> make[6]: *** [Makefile:701: libhmsbeagle_opencl_la-OpenCLPlugin.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/05/libhmsbeagle_3.1.2+dfsg-8_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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
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: libhmsbeagle
Source-Version: 3.1.2+dfsg-9
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
libhmsbeagle, 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 976...@bugs.debian.org,
and the maintainer will reopen the bug
Bug#976480: marked as done (xenium: FTBFS: utils.hpp:80:4: error: #error "Unsupported compiler")
Your message dated Sun, 6 Dec 2020 17:14:18 +0100 with message-id <20201206161418.gt31...@an3as.eu> and subject line Bug was closed by upload of xenium (0.0.2+ds-2) has caused the Debian Bug report #976480, regarding xenium: FTBFS: utils.hpp:80:4: error: #error "Unsupported compiler" 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.) -- 976480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xenium Version: 0.0.2+ds-1 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > /usr/bin/c++ -DDEBUG -I/<>/. -isystem > /usr/src/googletest/googletest -isystem > /usr/src/googletest/googletest/include -fsanitize=thread -o > CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest-all.cc.o -c > /usr/src/googletest/googletest/src/gtest-all.cc > In file included from /<>/./xenium/marked_ptr.hpp:9, > from > /<>/./xenium/reclamation/detail/concurrent_ptr.hpp:9, > from > /<>/./xenium/reclamation/generic_epoch_based.hpp:9, > from /<>/benchmarks/reclaimers.hpp:4, > from /<>/benchmarks/hash_maps.hpp:3, > from /<>/benchmarks/hash_map_benchmark.cpp:4: > /<>/./xenium/utils.hpp:80:4: error: #error "Unsupported compiler" >80 | #error "Unsupported compiler" > |^ > In file included from /<>/./xenium/backoff.hpp:9, > from /<>/./xenium/vyukov_hash_map.hpp:10, > from /<>/benchmarks/hash_maps.hpp:11, > from /<>/benchmarks/hash_map_benchmark.cpp:4: > /<>/./xenium/detail/hardware.hpp:25:6: warning: #warning "No > hardware_pause implementation available - falling back to local volatile > noop." [-Wcpp] >25 | #warning "No hardware_pause implementation available - falling > back to local volatile noop." > | ^~~ > In file included from /<>/./xenium/marked_ptr.hpp:9, > from > /<>/./xenium/reclamation/detail/concurrent_ptr.hpp:9, > from > /<>/./xenium/reclamation/generic_epoch_based.hpp:9, > from /<>/benchmarks/reclaimers.hpp:4, > from /<>/benchmarks/hash_maps.hpp:3, > from /<>/benchmarks/hash_map_benchmark.cpp:4: > /<>/./xenium/utils.hpp: In function ‘uint64_t > xenium::utils::random()’: > /<>/./xenium/utils.hpp:84:12: error: ‘getticks’ was not declared > in this scope; did you mean ‘gettid’? >84 | return getticks() >> 4; > |^~~~ > |gettid > [ 14%] Building CXX object > CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest_main.cc.o > /usr/bin/c++ -DDEBUG -I/<>/. -isystem > /usr/src/googletest/googletest -isystem > /usr/src/googletest/googletest/include -fsanitize=thread -o > CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest_main.cc.o > -c /usr/src/googletest/googletest/src/gtest_main.cc > [ 17%] Linking CXX static library libgoogletest.a > /usr/bin/cmake -P CMakeFiles/googletest.dir/cmake_clean_target.cmake > /usr/bin/cmake -E cmake_link_script CMakeFiles/googletest.dir/link.txt > --verbose=1 > /usr/bin/ar qc libgoogletest.a > CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest-all.cc.o > CMakeFiles/googletest.dir/usr/src/googletest/googletest/src/gtest_main.cc.o > /usr/bin/ranlib libgoogletest.a > make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu' > [ 17%] Built target googletest > make -f CMakeFiles/gtest.dir/build.make CMakeFiles/gtest.dir/depend > make[4]: Entering directory '/<>/obj-aarch64-linux-gnu' > cd /<>/obj-aarch64-linux-gnu && /usr/bin/cmake -E cmake_depends > "Unix Makefiles" /<> /<> > /<>/obj-aarch64-linux-gnu /<>/obj-aarch64-linux-gnu > /<>/obj-aarch64-linux-gnu/CMakeFiles/gtest.dir/DependInfo.cmake > --color= > Scanning dependencies of target gtest > make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu' > make -f CMakeFiles/gtest.dir/build.make CMakeFiles/gtest.dir/build > make[4]: Entering directory '/<>/obj-aarch64-linux-gnu' > [ 20%] Building CXX object > CMakeFiles/gtest.dir/test/chase_work_stealing_deque_test.cpp.o > /usr/bin/c++ -DDEBUG -I/<>/. -isystem > /usr/src/googletest/googletest -isystem > /usr/src/googletest/googletest/include -fsanitize=thread -Wall -Wextra > -Werror -Wno-error=cpp -std=gnu++17 -o >
Bug#976656: marked as done (chemical-structures-data: missing Breaks+Replaces: chemical-structures (<< 2.2.dfsg.0-16))
Your message dated Sun, 06 Dec 2020 16:03:35 + with message-id and subject line Bug#976656: fixed in chemical-structures 2.2.dfsg.0-18 has caused the Debian Bug report #976656, regarding chemical-structures-data: missing Breaks+Replaces: chemical-structures (<< 2.2.dfsg.0-16) 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.) -- 976656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chemical-structures-data Version: 2.2.dfsg.0-16 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../chemical-structures-data_2.2.dfsg.0-16_all.deb ... Unpacking chemical-structures-data (2.2.dfsg.0-16) ... dpkg: error processing archive /var/cache/apt/archives/chemical-structures-data_2.2.dfsg.0-16_all.deb (--unpack): trying to overwrite '/usr/share/chemical-structures/acid_anhydrides/3-methylfuran-2_5-dione.cml', which is also in package chemical-structures 2.2.dfsg.0-15 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/chemical-structures-data_2.2.dfsg.0-16_all.deb cheers, Andreas chemical-structures=2.2.dfsg.0-15_chemical-structures-data=2.2.dfsg.0-16.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: chemical-structures Source-Version: 2.2.dfsg.0-18 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of chemical-structures, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated chemical-structures 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: Sun, 06 Dec 2020 16:44:50 +0100 Source: chemical-structures Architecture: source Version: 2.2.dfsg.0-18 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 976656 Changes: chemical-structures (2.2.dfsg.0-18) unstable; urgency=medium . * added Breaks + Replace stances. Closes: #976656; many thanks to Andreas Beckmann Checksums-Sha1: ff8aa9094a92e51f3b67051d0fc5b80412ed56dd 2160 chemical-structures_2.2.dfsg.0-18.dsc c71b41b30a7518a48dd4075b7a05562a69a7655c 21496 chemical-structures_2.2.dfsg.0-18.debian.tar.xz 880f67f705f487558aff6cc5b1f4fd282b459d3b 7868 chemical-structures_2.2.dfsg.0-18_source.buildinfo Checksums-Sha256: bc098ba7bf7168335dd790078de0a0f2ce786b32d7759cbfd0cba15d5a7907a3 2160 chemical-structures_2.2.dfsg.0-18.dsc 5380cef4c650d2827c9793111fe1165ea921e0beb4796aed1400fd580650ed6f 21496 chemical-structures_2.2.dfsg.0-18.debian.tar.xz 9652f090e2982b227e95cb448e2e1962de44ef79fc9d3b298adcab4e0643c082 7868 chemical-structures_2.2.dfsg.0-18_source.buildinfo Files: 51e1175de59f94d14fc6a15ed59f9c5b 2160 science optional chemical-structures_2.2.dfsg.0-18.dsc 7e7533a0c3f65bf746890ee9c9520a01 21496 science optional chemical-structures_2.2.dfsg.0-18.debian.tar.xz e4b75b0458ddb31cea7cf40331f98aeb 7868 science optional chemical-structures_2.2.dfsg.0-18_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl/M/NEUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjnmjxAAikRjFmiu1Tm5pjuoEo3Y56fAPyBi HzKztAPFOcvcnyZ8FA3pferizwWSsUMbLl3/Skle2Ju9I21p6uV9baEwD1CCgRj8 zQTmIq8YVV2OFGSRnPuU92hOuH5qfjcxeVy6wBqV+/NMgWZYNHbJ2VFaANS5obEJ HPS3aEDPSHbaW2OM53PvNoWlqi/R2vdWyUkmMPzrIJcnv3CawdXGcLnDA012R4Vd W3g4mD5A7wBvLR1lwIh3NM0K10agspYuR9fDm6I6esyVtLorgcD4/PG5rglCBXK2 NMKSMtv+6Sps1YZwal2mTmlUCkCGoWdIE3kSoPUckmLUKdMdriR5Uxzd0OnOKgHo
Bug#976658: debcargo is broken (and the autopkgtest didn't catch it).
Package: debcargo Version: 2.4.3-2+bw Severity: grave After the recent binnmu of debcargo. debcargo update (after deleting the cache) gives. Updating crates.io index Something failed: failed to fetch `https://github.com/rust-lang/crates.io-index` Caused by: invalid version 0 on git_proxy_options; class=Invalid (3) This issue was not caught by the autopkgtest. In order to check this was indeed caused by the libgit2 update (and not by one of the other updates that have happened since the last debcargo build in unstable) I did a test build with libgit2-dev from testing but everything else from unstable. That test build worked fine. I suspect rust-git2/rust-libgit2-sys need to be updated to match the new libgit2. I've got to go now, but I'll try look into this issue some more later tonight.
Bug#976506: marked as done (conda-package-handling: FTBFS on arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sun, 06 Dec 2020 15:50:07 +
with message-id
and subject line Bug#976506: fixed in conda-package-handling 1.7.2-2
has caused the Debian Bug report #976506,
regarding conda-package-handling: FTBFS on arm64: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.9 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.)
--
976506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conda-package-handling
Version: 1.7.2-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package conda-package-handling
> dpkg-buildpackage: info: source version 1.7.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Nilesh Patra
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture arm64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
> Cython directive 'language_level' not set, using 2 for now (Py2). This will
> change in a later release! File:
> /<>/src/conda_package_handling/archive_utils_cy.pyx
> tree = Parsing.p_module(s, pxd, full_module_name)
> Compiling src/conda_package_handling/archive_utils_cy.pyx because it changed.
> [1/1] Cythonizing src/conda_package_handling/archive_utils_cy.pyx
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-arm64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building conda-package-handling using existing
> ./conda-package-handling_1.7.2.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building conda-package-handling in
> conda-package-handling_1.7.2-1.debian.tar.xz
> dpkg-source: info: building conda-package-handling in
> conda-package-handling_1.7.2-1.dsc
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
> Cython directive 'language_level' not set, using 2 for now (Py2). This will
> change in a later release! File:
> /<>/src/conda_package_handling/archive_utils_cy.pyx
> tree = Parsing.p_module(s, pxd, full_module_name)
> Compiling src/conda_package_handling/archive_utils_cy.pyx because it changed.
> [1/1] Cythonizing src/conda_package_handling/archive_utils_cy.pyx
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/tarball.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/utils.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/api.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/exceptions.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/__main__.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/cli.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/conda_fmt.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/interface.py ->
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/_version.py ->
>
Bug#954403: working around that issue
Control: reassign -1 src:python3-defaults Control: severity -1 important We're working around that for now by not byte-compiling the problematic file in python3-joblib.
Processed: working around that issue
Processing control commands: > reassign -1 src:python3-defaults Bug #954403 [python3-minimal] joblib: configuration error installing python3-joblib Bug #975517 [python3-minimal] joblib fails to install with Python 3.9 Bug reassigned from package 'python3-minimal' to 'src:python3-defaults'. Bug reassigned from package 'python3-minimal' to 'src:python3-defaults'. No longer marked as found in versions python3-defaults/3.8.6-1. No longer marked as found in versions python3-defaults/3.8.6-1. Ignoring request to alter fixed versions of bug #954403 to the same values previously set Ignoring request to alter fixed versions of bug #975517 to the same values previously set > severity -1 important Bug #954403 [src:python3-defaults] joblib: configuration error installing python3-joblib Bug #975517 [src:python3-defaults] joblib fails to install with Python 3.9 Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' -- 954403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954403 975517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973030: marked as done (python-icecream's autopkg tests ar failing with python3.9)
Your message dated Sun, 6 Dec 2020 16:22:06 +0100
with message-id <94dd95f5-3691-686c-87eb-aa64127e5...@redhat.com>
and subject line Re: python-icecream's autopkg tests ar failing with python3.9
has caused the Debian Bug report #973030,
regarding python-icecream's autopkg tests ar failing with python3.9
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.)
--
973030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-icecream
Version: 2.0.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
autopkgtest [23:11:12]: test unittest: [---
..EEE.
==
ERROR: testArgToStringFunction (tests.test_icecream.TestIceCream)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/tests/test_icecream.py",
line 361, in testArgToStringFunction
ic(eins)
File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
172, in __call__
out = self._format(callFrame, *args)
File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
206, in _format
out = self._formatArgs(
File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
213, in _formatArgs
sanitizedArgStrs = [
File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
214, in
source.get_text_with_indentation(arg)
File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
110, in get_text_with_indentation
result = self.asttokens().get_text(node)
File "/usr/lib/python3/dist-packages/executing.py", line 340, in asttokens
return ASTTokens(
File "/usr/lib/python3/dist-packages/asttokens/asttokens.py", line 65, in
__init__
self.mark_tokens(self._tree)
File "/usr/lib/python3/dist-packages/asttokens/asttokens.py", line 76, in
mark_tokens
MarkTokens(self).visit_tree(root_node)
File "/usr/lib/python3/dist-packages/asttokens/mark_tokens.py", line 49, in
visit_tree
util.visit_tree(node, self._visit_before_children,
self._visit_after_children)
File "/usr/lib/python3/dist-packages/asttokens/util.py", line 186, in
visit_tree
ret = postvisit(current, par_value, value)
File "/usr/lib/python3/dist-packages/asttokens/mark_tokens.py", line 92, in
_visit_after_children
nfirst, nlast = self._methods.get(self, node.__class__)(node, first, last)
File "/usr/lib/python3/dist-packages/asttokens/mark_tokens.py", line 330, in
visit_keyword
util.expect_token(name, token.NAME, node.arg)
File "/usr/lib/python3/dist-packages/asttokens/util.py", line 56, in
expect_token
raise ValueError("Expected token %s, got %s on line %s col %s" % (
ValueError: Expected token NAME:'outputFunction', got
NAME:'originalOutputFunction' on line 55 col 5
--- End Message ---
--- Begin Message ---
This bug is now fixed after an update on the python-asttoken dependency.
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-icecream/8675022/log.gz
--
- ina
signature.asc
Description: OpenPGP digital signature
--- End Message ---
Bug#976656: chemical-structures-data: missing Breaks+Replaces: chemical-structures (<< 2.2.dfsg.0-16)
Package: chemical-structures-data Version: 2.2.dfsg.0-16 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../chemical-structures-data_2.2.dfsg.0-16_all.deb ... Unpacking chemical-structures-data (2.2.dfsg.0-16) ... dpkg: error processing archive /var/cache/apt/archives/chemical-structures-data_2.2.dfsg.0-16_all.deb (--unpack): trying to overwrite '/usr/share/chemical-structures/acid_anhydrides/3-methylfuran-2_5-dione.cml', which is also in package chemical-structures 2.2.dfsg.0-15 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/chemical-structures-data_2.2.dfsg.0-16_all.deb cheers, Andreas chemical-structures=2.2.dfsg.0-15_chemical-structures-data=2.2.dfsg.0-16.log.gz Description: application/gzip
Processed: Re: Bug#976366: Upgrade to 247 broke keyboard input on Wayland session
Processing control commands: > severity -1 important Bug #976366 [systemd] Upgrade to 247 broke keyboard input on Wayland session Severity set to 'important' from 'critical' > tags -1 unreproducible Bug #976366 [systemd] Upgrade to 247 broke keyboard input on Wayland session Added tag(s) unreproducible. -- 976366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
