Bug#972217: marked as done (python-crc32c FTBFS on arm64)
Your message dated Sun, 18 Oct 2020 04:49:00 +
with message-id
and subject line Bug#972217: fixed in python-crc32c 2.1-1.1
has caused the Debian Bug report #972217,
regarding python-crc32c FTBFS on arm64
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.)
--
972217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-crc32c
Version: 2.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-crc32c=arm64=2.1-1=1601652233=0
...
dh_auto_build -a -O--buildsystem=pybuild -O--test-pytest
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_ext
platform: aarch64, is_intel: 0, is_arm: 1
building 'crc32c' extension
creating build
creating build/temp.linux-arm64-3.8
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -DNDEBUG -DIS_ARM -I. -I/usr/include/python3.8 -c
_crc32c.c -o build/temp.linux-arm64-3.8/_crc32c.o -O3 -march=armv8-a+crc+crypto
_crc32c.c: In function ‘PyInit_crc32c’:
_crc32c.c:150:11: warning: implicit declaration of function
‘_crc32c_arm64_probe’; did you mean ‘_crc32c_intel_probe’?
[-Wimplicit-function-declaration]
150 | else if (_crc32c_arm64_probe()) {
| ^~~
| _crc32c_intel_probe
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -DNDEBUG -DIS_ARM -I. -I/usr/include/python3.8 -c
checkarm.c -o build/temp.linux-arm64-3.8/checkarm.o -O3
-march=armv8-a+crc+crypto
In file included from /usr/include/aarch64-linux-gnu/sys/auxv.h:25,
from checkarm.c:27:
checkarm.c: In function ‘_crc32c_arm64_probe’:
checkarm.c:32:22: error: expected identifier or ‘(’ before numeric constant
32 | const unsigned long HWCAP_CRC32 = 1 << 7;
| ^~~
error: command 'aarch64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p 3.8 returned exit
code 13
--- End Message ---
--- Begin Message ---
Source: python-crc32c
Source-Version: 2.1-1.1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-crc32c, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-crc32c package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 17 Oct 2020 19:47:59 -0700
Source: python-crc32c
Architecture: source
Version: 2.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Stefano Rivera
Closes: 972217
Changes:
python-crc32c (2.1-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Patch: HWCAP_CRC32 is already defined on arm64. Fixes FTBFS. Closes:
#972217
Checksums-Sha1:
fb7670e08b3050a298e5e4ee2d39c1dcf9000fb5 1352 python-crc32c_2.1-1.1.dsc
7e4a028420f8967ac3282514798305dce2c85413 4488
python-crc32c_2.1-1.1.debian.tar.xz
e51089a6eb2cb5f753e8fbb20a8f001b27beebda 5730
python-crc32c_2.1-1.1_source.buildinfo
Checksums-Sha256:
265f660004c53ed3a407009c39f252aef8253df2143d97d886fbbb8a668297fa 1352
python-crc32c_2.1-1.1.dsc
5e65ad35857b456cdd19386987b18b7f6f5156507d1258332f8da1583402787f 4488
python-crc32c_2.1-1.1.debian.tar.xz
0d2ddf0ed10a26b34e5d4b9414d954de8b514492dc91ae3bb10779dd2d2dd68b 5730
python-crc32c_2.1-1.1_source.buildinfo
Files:
e088cc5a3090e26cb4fa22b86302b21d 1352 python optional python-crc32c_2.1-1.1.dsc
2b9b7bd97012e5ce7cc0078ab0672810 4488 python
Bug#972217: python-crc32c: diff for NMU version 2.1-1.1
Quoting Stefano Rivera (2020-10-18 04:52:08) > Control: tags 972217 + patch > Control: tags 972217 + pending > > Dear maintainer, > > I've prepared an NMU for python-crc32c (versioned as 2.1-1.1) and > uploaded it to DELAYED/3. Please feel free to tell me if I > should delay it longer. On the contrary: Feel free to release it immediately. Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: python-crc32c: diff for NMU version 2.1-1.1
Processing control commands: > tags 972217 + patch Bug #972217 [src:python-crc32c] python-crc32c FTBFS on arm64 Added tag(s) patch. > tags 972217 + pending Bug #972217 [src:python-crc32c] python-crc32c FTBFS on arm64 Added tag(s) pending. -- 972217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972217: python-crc32c: diff for NMU version 2.1-1.1
Control: tags 972217 + patch
Control: tags 972217 + pending
Dear maintainer,
I've prepared an NMU for python-crc32c (versioned as 2.1-1.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru python-crc32c-2.1/debian/changelog python-crc32c-2.1/debian/changelog
--- python-crc32c-2.1/debian/changelog 2020-10-02 07:49:26.0 -0700
+++ python-crc32c-2.1/debian/changelog 2020-10-17 19:47:59.0 -0700
@@ -1,3 +1,10 @@
+python-crc32c (2.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch: HWCAP_CRC32 is already defined on arm64. Fixes FTBFS. Closes: #972217
+
+ -- Stefano Rivera Sat, 17 Oct 2020 19:47:59 -0700
+
python-crc32c (2.1-1) unstable; urgency=medium
[ upstream ]
diff -Nru python-crc32c-2.1/debian/patches/arm64-hwcap-defined.patch python-crc32c-2.1/debian/patches/arm64-hwcap-defined.patch
--- python-crc32c-2.1/debian/patches/arm64-hwcap-defined.patch 1969-12-31 16:00:00.0 -0800
+++ python-crc32c-2.1/debian/patches/arm64-hwcap-defined.patch 2020-10-17 19:47:59.0 -0700
@@ -0,0 +1,37 @@
+From: Stefano Rivera
+Date: Sat, 17 Oct 2020 19:35:51 -0700
+Subject: HWCAP_CRC32 is already defined on arm64
+
+On a standard GNU/Linux system, includes
+which defines HWCAP_CRC32.
+
+We probably have no need for a fallback, I'm sure anyone using this
+library will have HWCAP_CRC32 defined, but it doesn't really hurt to
+carry it, either...
+
+Bug-Debian: https://bugs.debian.org/972217
+Forwarded: https://github.com/ICRAR/crc32c/pull/21
+---
+ checkarm.c | 7 +--
+ 1 file changed, 5 insertions(+), 2 deletions(-)
+
+diff --git a/checkarm.c b/checkarm.c
+index 7957816..374eeef 100644
+--- a/checkarm.c
b/checkarm.c
+@@ -26,10 +26,13 @@
+
+ #include
+
++#ifndef HWCAP_CRC32
++/* see arch/arm64/include/uapi/asm/hwcap.h */
++#define HWCAP_CRC32 (1 << 7)
++#endif
++
+ int _crc32c_arm64_probe(void)
+ {
+- /* see arch/arm64/include/uapi/asm/hwcap.h */
+- const unsigned long HWCAP_CRC32 = 1 << 7;
+ unsigned long auxval;
+ auxval = getauxval(AT_HWCAP);
+ return (auxval & HWCAP_CRC32) != 0;
diff -Nru python-crc32c-2.1/debian/patches/series python-crc32c-2.1/debian/patches/series
--- python-crc32c-2.1/debian/patches/series 1969-12-31 16:00:00.0 -0800
+++ python-crc32c-2.1/debian/patches/series 2020-10-17 19:47:59.0 -0700
@@ -0,0 +1 @@
+arm64-hwcap-defined.patch
Bug#971147: marked as done (rust-onig-sys: FTBFS: unsatisfiable build-dependencies: librust-cexpr-0.3+default-dev (>= 0.3.3-~~), librust-clang-sys-0.28+clang-6-0-dev, librust-clang-sys-0.28+default-de
Your message dated Sat, 17 Oct 2020 22:51:01 + with message-id and subject line Bug#971147: fixed in rust-onig-sys 69.5.1-1 has caused the Debian Bug report #971147, regarding rust-onig-sys: FTBFS: unsatisfiable build-dependencies: librust-cexpr-0.3+default-dev (>= 0.3.3-~~), librust-clang-sys-0.28+clang-6-0-dev, librust-clang-sys-0.28+default-dev, librust-clang-sys-0.28+runtime-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 971147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-onig-sys Version: 69.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-bindgen-0.51+default-dev, librust-cc-1+default-dev, > librust-pkg-config-0.3+default-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-bindgen-0.51+default-dev, librust-cc-1+default-dev, > librust-pkg-config-0.3+default-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [441 B] > Get:5 copy:/<>/apt_archive ./ Packages [512 B] > Fetched 1910 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > librust-bindgen-dev : Depends: librust-cexpr-0.3+default-dev (>= 0.3.3-~~) > but it is not installable >Depends: librust-clang-sys-0.28+clang-6-0-dev but it > is not installable >Depends: librust-clang-sys-0.28+default-dev but it is > not installable >Depends: librust-clang-sys-0.28+runtime-dev but it is > not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/09/26/rust-onig-sys_69.2.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: rust-onig-sys Source-Version: 69.5.1-1 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of rust-onig-sys, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated rust-onig-sys 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, 18 Oct 2020 00:22:04 +0200 Source: rust-onig-sys Architecture: source Version: 69.5.1-1 Distribution: unstable Urgency: medium
Bug#972372: marked as done (sfepy FTBFS on 32bit with gcc 10)
Your message dated Sat, 17 Oct 2020 22:51:14 + with message-id and subject line Bug#972372: fixed in sfepy 2019.4-2.1 has caused the Debian Bug report #972372, regarding sfepy FTBFS on 32bit with gcc 10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sfepy Version: 2019.4-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/history/armhf/sfepy.html https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/armhf/sfepy.html https://buildd.debian.org/status/logs.php?pkg=sfepy=2019.4-2%2Bb2 ... Extension error: Could not import extension gen_term_table (exception: /<>/sfepy/discrete/common/extmods/cmesh.cpython-38-arm-linux-gnueabi.so: undefined symbol: _aux_hex) make[3]: *** [Makefile:35: html] Error 2 --- End Message --- --- Begin Message --- Source: sfepy Source-Version: 2019.4-2.1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of sfepy, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated sfepy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Oct 2020 13:02:43 -0700 Source: sfepy Architecture: source Version: 2019.4-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Stefano Rivera Closes: 972372 Changes: sfepy (2019.4-2.1) unstable; urgency=medium . * Non-maintainer upload. * Declare internal inline functions "static inline", fixing FTBFS on 32-bit archs (Closes: #972372). Checksums-Sha1: 41a6e7c7c27deaff68febcbb83ceb0db1c2ade42 1819 sfepy_2019.4-2.1.dsc 994ca37b1360f13ac2c6b5ce002b697827058d91 5556 sfepy_2019.4-2.1.debian.tar.xz 7bf8870f6e9455455d76907449a0b8c8f6e57ba1 9926 sfepy_2019.4-2.1_source.buildinfo Checksums-Sha256: 87f13992434f6e8ba044d03cb892e3ce357c4de06f8c2c7d10080a7d43796d6b 1819 sfepy_2019.4-2.1.dsc b6ef03e40b376d131b357b3832dcb16fb4666d3280f27b4f57dfd9534dd81f9c 5556 sfepy_2019.4-2.1.debian.tar.xz 12170497215f4af83065a898db3f164079afd10c0ecbdcc5bbb49be63fbddbde 9926 sfepy_2019.4-2.1_source.buildinfo Files: 7f90478f6e53ca51266ec508fd5c36fd 1819 python optional sfepy_2019.4-2.1.dsc 7432d6381f22c9ecfb6537e83c3372a9 5556 python optional sfepy_2019.4-2.1.debian.tar.xz 37b8220bdb44bc3fd7d68f344f0d7774 9926 python optional sfepy_2019.4-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCX4tOqgAKCRBHew2wJjpU 2E4QAQDsZqT1zXsmM7Li9ODhTkyE55b3EgRKvVYk2xC8fbAkbQEAvut1bddrga4Y p/uP0hc+ZVEPLIKr0rEfA0xUmbxScwQ= =WcVD -END PGP SIGNATURE End Message ---
Bug#972372: sfepy: diff for NMU version 2019.4-2.1
Hi Stefano, thanks for NMU, feel free to upload it immediately. Just push your changes into the git. Best regards, Anton Am Sa., 17. Okt. 2020 um 22:15 Uhr schrieb Stefano Rivera : > > Control: tags 972372 + patch > Control: tags 972372 + pending > > Dear maintainer, > > I've prepared an NMU for sfepy (versioned as 2019.4-2.1) and > uploaded it to DELAYED/3. Please feel free to tell me if I > should delay it longer. > > Regards. > > SR > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#970067: marked as done (lxc-templates: bullseye: /updates -> -security)
Your message dated Sat, 17 Oct 2020 21:39:04 +
with message-id
and subject line Bug#970067: fixed in lxc-templates 3.0.4-4
has caused the Debian Bug report #970067,
regarding lxc-templates: bullseye: /updates -> -security
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.)
--
970067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lxc-templates
Version: 3.0.4-3
Severity: serious
File: /usr/share/lxc/templates/lxc-debian
User: debian-de...@lists.debian.org
Usertags: bullseye-security
With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.
The lxc-debian script appears to write an apt sources.list that will
not provide security updates for sources.list scripts created in order
to cater to Debian bullseye images. I suggest that this script check
the version of the Debian release in question using distro-info and
then if the release is 11 or higher, then use $release-security
otherwise use $release/updates as before. It is much better to use
distro-info than to hard-code the release version numbers. It might
even be a good idea to include the security suite information in
distro-info itself and look it up from there.
$ grep -A3 -B23 /updates /usr/share/lxc/templates/lxc-debian
write_sourceslist()
{
local rootfs="$1"; shift
local release="$1"; shift
local arch="$1";shift
local prefix="deb"
if [ -n "${arch}" ]; then
prefix="deb [arch=${arch}]"
fi
if [ "$mainonly" = 1 ]; then
non_main=''
else
non_main=' contrib non-free'
fi
cat >> "${rootfs}/etc/apt/sources.list" << EOF
${prefix} $MIRROR ${release} main${non_main}
EOF
if [ "$release" != "unstable" -a "$release" != "sid" ]; then
cat >> "${rootfs}/etc/apt/sources.list" << EOF
${prefix} $SECURITY_MIRROR ${release}/updates main${non_main}
EOF
fi
}
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: lxc-templates
Source-Version: 3.0.4-4
Done: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
We believe that the bug you reported is fixed in the latest version of
lxc-templates, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pierre-Elliott Bécue (supplier of updated lxc-templates
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 17 Oct 2020 22:42:34 +0200
Source: lxc-templates
Architecture: source
Version: 3.0.4-4
Distribution: unstable
Urgency: medium
Maintainer: pkg-lxc
Changed-By: Pierre-Elliott Bécue
Closes: 959926 970067
Changes:
lxc-templates (3.0.4-4) unstable; urgency=medium
.
* d/patches/0002: Update lxc.debian template to document alternatives to the
download temmplate (Closes: #959926)
* d/control:
- Add mmdebstrap as a recommend
* d/README.Debian
- Add some local documentation to the package to help people not using the
download template
* d/patches/0003: Handle properly the security repositories for the future
releases. (Closes: #970067)
* d/gbp.conf: added default git-buildpackage config
* Bump debhelper-compat version to 13
Checksums-Sha1:
81960a2e9d3789e0772993e18abf90e2c0c40e94 2254 lxc-templates_3.0.4-4.dsc
55598c1e3e7505dfd8444e372ea4da9fb76e7283 7480
lxc-templates_3.0.4-4.debian.tar.xz
8727a9916d35429fdb952c00505bd8e8af8d0116 5823
lxc-templates_3.0.4-4_amd64.buildinfo
Checksums-Sha256:
39442645bef97f57aed6748336bffd7e4574db07b53c61050b61d3a641bf43b6 2254
lxc-templates_3.0.4-4.dsc
d447ce791ccdf0e027a6b94bbc273b344ce74873ac16f4a969d2c10e5dd0199d 7480
lxc-templates_3.0.4-4.debian.tar.xz
0ef5dbfc4d8e14a7b5a9fc1d72c5a423421279271f3a739e317dd34391466d9b 5823
lxc-templates_3.0.4-4_amd64.buildinfo
Files:
12cbe89046ccb20341891c0cf61ae0c9 2254 admin optional lxc-templates_3.0.4-4.dsc
Processed: tagging 972024
Processing commands for cont...@bugs.debian.org: > tags 972024 + pending Bug #972024 [src:python-geotiepoints] python-geotiepoints ftbfs with python3.9 as supported python3 version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 972024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972374: marked as done (qiskit-terra ftbfs with python3.9 as supported python3 version)
Your message dated Sat, 17 Oct 2020 20:48:05 +
with message-id
and subject line Bug#972374: fixed in qiskit-terra 0.12.0-2.1
has caused the Debian Bug report #972374,
regarding qiskit-terra ftbfs with python3.9 as supported python3 version
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.)
--
972374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qiskit-terra
Version: 0.12.0-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
qiskit-terra ftbfs with python3.9 as supported python3 version:
[...]
dh_auto_test -a -O--buildsystem=pybuild
pybuild --test -i python{version} -p "3.9 3.8"
I: pybuild pybuild:284: cp -r /<>/qiskit/schemas/examples
/<>/.pybuild/cpython3_3.9/build/qiskit/schemas
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9/build; python3.9
-m pytest test/python -k "not (test_generate_latex or TestLatexSourceGenerator
or test_jupyter_jobs_pbars)"
= test session starts ==
platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
rootdir: /<>
collected 0 items / 166 errors
ERRORS
_ ERROR collecting .pybuild/cpython3_3.9/build/test/python/test_dagcircuit.py __
/usr/lib/python3/dist-packages/py/_path/local.py:704: in pyimport
__import__(modname)
test/__init__.py:18: in
from qiskit.test.utils import generate_cases
qiskit/test/__init__.py:17: in
from .base import QiskitTestCase
qiskit/test/base.py:29: in
from .utils import Path, _AssertNoLogsContext, setup_test_logging
qiskit/test/utils.py:71: in
class _AssertNoLogsContext(unittest.case._AssertLogsContext):
E AttributeError: module 'unittest.case' has no attribute '_AssertLogsContext'
__ ERROR collecting .pybuild/cpython3_3.9/build/test/python/test_examples.py ___
/usr/lib/python3/dist-packages/py/_path/local.py:704: in pyimport
__import__(modname)
test/__init__.py:18: in
from qiskit.test.utils import generate_cases
qiskit/test/__init__.py:17: in
from .base import QiskitTestCase
qiskit/test/base.py:29: in
from .utils import Path, _AssertNoLogsContext, setup_test_logging
qiskit/test/utils.py:71: in
class _AssertNoLogsContext(unittest.case._AssertLogsContext):
E AttributeError: module 'unittest.case' has no attribute '_AssertLogsContext'
_ ERROR collecting .pybuild/cpython3_3.9/build/test/python/test_qasm_parser.py _
--- End Message ---
--- Begin Message ---
Source: qiskit-terra
Source-Version: 0.12.0-2.1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
qiskit-terra, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated qiskit-terra package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 17 Oct 2020 11:53:16 -0700
Source: qiskit-terra
Architecture: source
Version: 0.12.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Stefano Rivera
Closes: 972374
Changes:
qiskit-terra (0.12.0-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Patch: Support Python 3.9, in test infrastructure. Closes: #972374
Checksums-Sha1:
c8b2516ce4c797e44056c23675ea1f766b8e4f83 2005 qiskit-terra_0.12.0-2.1.dsc
6b1fbe76168cf283b3184d1d0970d8a0a89ab7b0 5984
qiskit-terra_0.12.0-2.1.debian.tar.xz
cf7ebd5f3fd1081be12dc265c12d24a4b6f2a13b 9390
qiskit-terra_0.12.0-2.1_source.buildinfo
Checksums-Sha256:
77e6e8f3b23901aea6bc1acb9607b87e912752e492ffb36905b9524c648449fc 2005
qiskit-terra_0.12.0-2.1.dsc
04effd5a709df061779d939b0c74b11c292d31268b969733bb315e8577028081 5984
qiskit-terra_0.12.0-2.1.debian.tar.xz
49b3d096e52466215578d563909fbd1dcdfae71b0ca36fb56592a084ba97d955 9390
qiskit-terra_0.12.0-2.1_source.buildinfo
Files:
01f6acb6455cec3396f461024ecc5e4a 2005 science optional
qiskit-terra_0.12.0-2.1.dsc
5b5c9f7d8c49d1173e398bd594719d02 5984 science optional
Bug#969494: marked as done (r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’)
Your message dated Sat, 17 Oct 2020 20:48:17 +
with message-id
and subject line Bug#969494: fixed in r-cran-mice 3.11.0-1
has caused the Debian Bug report #969494,
regarding r-cran-mice: autopkgtest regression: there is no package called
‘broom.mixed’
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.)
--
969494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-mice
Version: 3.10.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of r-cran-mice the autopkgtest of r-cran-mice fails
in testing when that autopkgtest is run with the binary packages of
r-cran-mice from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
r-cran-micefrom testing3.10.0-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
r-cran-mice/3.10.0-1. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=r-cran-mice
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-mice/6894306/log.gz
autopkgtest [02:08:37]: test run-unit-test: [---
BEGIN TEST testthat.R
R version 4.0.2 (2020-06-22) -- "Taking Off Again"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> library(testthat)
> library(mice)
Attaching package: ‘mice’
The following objects are masked from ‘package:base’:
cbind, rbind
>
> test_check("mice")
── 1. Error: (unknown) (@test-D3.R#48)
there is no package called ‘broom.mixed’
Backtrace:
1. base::library(broom.mixed, quietly = TRUE)
══ testthat results
═══
[ OK: 299 | SKIPPED: 1 | WARNINGS: 0 | FAILED: 1 ]
1. Error: (unknown) (@test-D3.R#48)
Error: testthat unit tests failed
Execution halted
autopkgtest [02:09:14]: test run-unit-test: ---]
a
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-mice
Source-Version: 3.11.0-1
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-mice, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-mice 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, 17 Oct 2020 22:19:54 +0200
Source: r-cran-mice
Architecture: source
Version: 3.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 969494
Changes:
r-cran-mice (3.11.0-1) unstable; urgency=medium
.
* New upstream version
* New Test-Depends: r-cran-broom.mixed
Closes: #969494
Checksums-Sha1:
e58ae9cc00909e7272463adf43801d19e630a352 2516 r-cran-mice_3.11.0-1.dsc
Bug#972334: llvm-toolchain-11: autopkgtest failure on i386: integration-test-suite-test FAIL non-zero exit status 2
Hello, According to Clang / LLVM documentation, -fsanitize=thread is not supported on i386. https://clang.llvm.org/docs/ThreadSanitizer.html Yeah, I submitted this PR a few days ago: https://github.com/opencollab/llvm-toolchain-integration-test-suite/pull/30 S
Bug#972374: qiskit-terra: diff for NMU version 0.12.0-2.1
Hi Stefano On Sat, 17 Oct 2020 at 21:03, Stefano Rivera wrote: > I've prepared an NMU for qiskit-terra (versioned as 0.12.0-2.1) and > uploaded it to DELAYED/3. Please feel free to tell me if I > should delay it longer. This looks good to me, please feel free to reschedule to 0 days. > Also, FYI, your git repo is missing on Salsa. It was marked private and I've made it public now. Regards Graham
Bug#972372: sfepy: diff for NMU version 2019.4-2.1
Control: tags 972372 + patch
Control: tags 972372 + pending
Dear maintainer,
I've prepared an NMU for sfepy (versioned as 2019.4-2.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru sfepy-2019.4/debian/changelog sfepy-2019.4/debian/changelog
--- sfepy-2019.4/debian/changelog 2020-01-21 11:29:55.0 -0800
+++ sfepy-2019.4/debian/changelog 2020-10-17 13:02:43.0 -0700
@@ -1,3 +1,11 @@
+sfepy (2019.4-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Declare internal inline functions "static inline", fixing FTBFS on 32-bit
+archs (Closes: #972372).
+
+ -- Stefano Rivera Sat, 17 Oct 2020 13:02:43 -0700
+
sfepy (2019.4-2) unstable; urgency=medium
* [40073a3] Trim trailing whitespace.
diff -Nru sfepy-2019.4/debian/patches/extern-inline.patch sfepy-2019.4/debian/patches/extern-inline.patch
--- sfepy-2019.4/debian/patches/extern-inline.patch 1969-12-31 16:00:00.0 -0800
+++ sfepy-2019.4/debian/patches/extern-inline.patch 2020-10-17 12:50:17.0 -0700
@@ -0,0 +1,35 @@
+Declare internal inline functions "static inline"
+
+Avoids FTBFS on 32-bit platforms where an undefined symbol _aux_hex was
+referenced from mesh.o.
+
+Author: Stefano Rivera
+Bug-Debian: https://bugs.debian.org/972372
+Bug-Upstream: https://github.com/sfepy/sfepy/issues/651
+--- a/sfepy/discrete/common/extmods/mesh.c
b/sfepy/discrete/common/extmods/mesh.c
+@@ -910,13 +910,13 @@
+ return(RET_OK);
+ }
+
+-inline float64 _det3x3(float64 j[9])
++static inline float64 _det3x3(float64 j[9])
+ {
+ return (j[0]*j[4]*j[8] + j[3]*j[7]*j[2] + j[1]*j[5]*j[6]
+ - j[2]*j[4]*j[6] - j[5]*j[7]*j[0] - j[1]*j[3]*j[8]);
+ }
+
+-inline float64 _tri_area(float64 *coors, uint32 *indices, uint32 nc)
++static inline float64 _tri_area(float64 *coors, uint32 *indices, uint32 nc)
+ {
+ #define VS(ic, id) (coors[nc*indices[ic] + id])
+
+@@ -945,7 +945,7 @@
+ #undef VS
+ }
+
+-inline float64 _aux_hex(float64 *coors, uint32 *indices, uint32 nc,
++static inline float64 _aux_hex(float64 *coors, uint32 *indices, uint32 nc,
+ int32 h, int32 i, int32 j, int32 k)
+ {
+ #define VS(ic, id) (coors[nc*indices[ic] + id])
diff -Nru sfepy-2019.4/debian/patches/series sfepy-2019.4/debian/patches/series
--- sfepy-2019.4/debian/patches/series 2020-01-21 11:29:55.0 -0800
+++ sfepy-2019.4/debian/patches/series 2020-10-17 12:46:14.0 -0700
@@ -1 +1,2 @@
20_reproducible_build.patch
+extern-inline.patch
Processed: sfepy: diff for NMU version 2019.4-2.1
Processing control commands: > tags 972372 + patch Bug #972372 [src:sfepy] sfepy FTBFS on 32bit with gcc 10 Added tag(s) patch. > tags 972372 + pending Bug #972372 [src:sfepy] sfepy FTBFS on 32bit with gcc 10 Added tag(s) pending. -- 972372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 972015 to pandas ftbfs with python 3.9 as supported python version
Processing commands for cont...@bugs.debian.org: > retitle 972015 pandas ftbfs with python 3.9 as supported python version Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version Changed Bug title to 'pandas ftbfs with python 3.9 as supported python version' from 'pandas ftbfs with python3 as supported python version'. Changed Bug title to 'pandas ftbfs with python 3.9 as supported python version' from 'pandas ftbfs with python3.9 as supported python version'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972015 972033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 972015
Processing commands for cont...@bugs.debian.org: > tags 972015 + ftbfs Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version Added tag(s) ftbfs. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972015 972033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957665: Fortran issue solved but symbols issues (Was: Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10))
Hi Andrius On Thu, Oct 15, 2020 at 03:34:15PM +0300, Andrius Merkys wrote: > > FFLAGS += -fallow-argument-mismatch Thanks a lot for the helpful hint which enabled me to do one step forward[1]. Unfortunately there are further errors: ... /usr/bin/ld: paw/cdf/shared/mlpdef.o:/build/paw-2.14.04.dfsg.2/build/pawlib/paw/cdf/mlpdef.c:155: multiple definition of `klnkaddr'; paw/cdf/shared/pawcdf.o:/build/paw-2.14.04.dfsg.2/build/pawlib/paw/cdf/pawcdf.c:155: first defined here /usr/bin/ld: warning: alignment 4 of symbol `pawch3_' in paw/ntuple/shared/c_decl.o is smaller than 16 in paw/code/shared/pawint3.o /usr/bin/ld: warning: size of symbol `hcfile_' changed from 12800 in paw/code/shared/hgetid.o to 4000 in paw/ntuple/shared/c_decl.o /usr/bin/ld: warning: size of symbol `pawc_' changed from 40004 in comis/code/shared/csdefn.o to 4 in paw/ntuple/shared/c_decl.o /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:31: multiple definition of `learn_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:31: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:40: multiple definition of `pat_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:40: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:19: multiple definition of `net_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:19: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:49: multiple definition of `divers_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:49: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:92: multiple definition of `Hessian'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:92: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:91: multiple definition of `ExamplesIndex'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:91: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:90: multiple definition of `JacobianMatrix'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:90: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:89: multiple definition of `Gamma'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:89: first defined here ... Any further hints are welcome Andreas. [1] https://salsa.debian.org/science-team/paw/-/commit/5b7695142d3580516168086feb3e97c2b1fac575 -- http://fam-tille.de
Processed: bug 972372 is forwarded to https://github.com/sfepy/sfepy/issues/651
Processing commands for cont...@bugs.debian.org: > forwarded 972372 https://github.com/sfepy/sfepy/issues/651 Bug #972372 [src:sfepy] sfepy FTBFS on 32bit with gcc 10 Set Bug forwarded-to-address to 'https://github.com/sfepy/sfepy/issues/651'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: qiskit-terra: diff for NMU version 0.12.0-2.1
Processing control commands: > tags 972374 + patch Bug #972374 [src:qiskit-terra] qiskit-terra ftbfs with python3.9 as supported python3 version Added tag(s) patch. > tags 972374 + pending Bug #972374 [src:qiskit-terra] qiskit-terra ftbfs with python3.9 as supported python3 version Added tag(s) pending. -- 972374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972374: qiskit-terra: diff for NMU version 0.12.0-2.1
Control: tags 972374 + patch Control: tags 972374 + pending Dear maintainer, I've prepared an NMU for qiskit-terra (versioned as 0.12.0-2.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Also, FYI, your git repo is missing on Salsa. Regards. SR diff -Nru qiskit-terra-0.12.0/debian/changelog qiskit-terra-0.12.0/debian/changelog --- qiskit-terra-0.12.0/debian/changelog 2020-08-15 03:26:42.0 -0700 +++ qiskit-terra-0.12.0/debian/changelog 2020-10-17 11:53:16.0 -0700 @@ -1,3 +1,10 @@ +qiskit-terra (0.12.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Patch: Support Python 3.9, in test infrastructure. Closes: #972374 + + -- Stefano Rivera Sat, 17 Oct 2020 11:53:16 -0700 + qiskit-terra (0.12.0-2) unstable; urgency=medium * d/patches: backport upstream fix. Closes: #964669 diff -Nru qiskit-terra-0.12.0/debian/patches/python3.9.patch qiskit-terra-0.12.0/debian/patches/python3.9.patch --- qiskit-terra-0.12.0/debian/patches/python3.9.patch 1969-12-31 16:00:00.0 -0800 +++ qiskit-terra-0.12.0/debian/patches/python3.9.patch 2020-10-17 11:37:15.0 -0700 @@ -0,0 +1,33 @@ +Adapt to the new location of the private _AssertLogsContext class in Python 3.9 + +Upstream has started to look at 3.9 support in +https://github.com/Qiskit/qiskit-terra/pull/5189 but haven't fixed this, yet. + +Author: Stefano Rivera +Bug-Debian: https://bugs.debian.org/972374 +Forwarded: no +--- a/qiskit/test/utils.py b/qiskit/test/utils.py +@@ -16,9 +16,12 @@ + + import logging + import os +-import unittest + from enum import Enum + from itertools import product ++try: ++from unittest._log import _AssertLogsContext ++except ImportError: ++from unittest.case import _AssertLogsContext + + from qiskit import __path__ as qiskit_path + +@@ -68,7 +71,7 @@ + logger.setLevel(level) + + +-class _AssertNoLogsContext(unittest.case._AssertLogsContext): ++class _AssertNoLogsContext(_AssertLogsContext): + """A context manager used to implement TestCase.assertNoLogs().""" + + # pylint: disable=inconsistent-return-statements diff -Nru qiskit-terra-0.12.0/debian/patches/series qiskit-terra-0.12.0/debian/patches/series --- qiskit-terra-0.12.0/debian/patches/series 2020-08-15 03:05:52.0 -0700 +++ qiskit-terra-0.12.0/debian/patches/series 2020-10-17 11:32:33.0 -0700 @@ -2,3 +2,4 @@ 0002-Simplify-networkx-dependency-declaration.patch 0003-Trim-included-package_data-in-setup.py.patch 0004-Fix-numpy-1.19.0-pulse-error-upstream-backport.patch +python3.9.patch
Bug#972277: marked as done (sensors-applet: Install the gnome-panel module in multi-arch location)
Your message dated Sat, 17 Oct 2020 18:35:35 + with message-id and subject line Bug#972277: fixed in sensors-applet 3.0.0+git6-0.5 has caused the Debian Bug report #972277, regarding sensors-applet: Install the gnome-panel module in multi-arch location 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.) -- 972277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sensors-applet Version: 3.0.0+git6-0.4 Severity: serious Justification: fails to build from source with gnome-panel 3.38 Tags: ftbfs patch pending Dear Maintainer, In gnome-panel 3.37.1, I enabled multi-arch support [1]. So the modules are now installed into multi-arch location. Today the new stable release (3.38.0) was released, and I uploaded it to unstable. I added Breaks against some packages, including sensors-applet, so a new upload will be needed to let gnome-panel migrate to testing. I have uploaded the attached patch to DELAYED/2 queue. I have already done some NMUs for this package, so I hope you won't mind another one. [1]: https://tracker.debian.org/news/1145753/accepted-gnome-panel-3371-1-source-into-experimental/ -- Dmitry Shachnev diff -Nru sensors-applet-3.0.0+git6/debian/changelog sensors-applet-3.0.0+git6/debian/changelog --- sensors-applet-3.0.0+git6/debian/changelog 2020-06-05 13:18:41.0 +0300 +++ sensors-applet-3.0.0+git6/debian/changelog 2020-10-15 20:44:32.0 +0300 @@ -1,3 +1,11 @@ +sensors-applet (3.0.0+git6-0.5) unstable; urgency=medium + + * Non-maintainer upload. + * Install libsensors-applet.so in multi-arch location, for compatibility +with gnome-panel 3.38 (closes: #-1). + + -- Dmitry Shachnev Thu, 15 Oct 2020 20:44:32 +0300 + sensors-applet (3.0.0+git6-0.4) unstable; urgency=medium * Non-maintainer upload. diff -Nru sensors-applet-3.0.0+git6/debian/sensors-applet.install sensors-applet-3.0.0+git6/debian/sensors-applet.install --- sensors-applet-3.0.0+git6/debian/sensors-applet.install 2020-06-05 13:18:41.0 +0300 +++ sensors-applet-3.0.0+git6/debian/sensors-applet.install 2020-10-15 20:44:32.0 +0300 @@ -1,3 +1,3 @@ -usr/lib/gnome-panel/modules/libsensors-applet.so +usr/lib/*/gnome-panel/modules/libsensors-applet.so usr/lib/*/sensors-applet/plugins/*.so usr/share signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: sensors-applet Source-Version: 3.0.0+git6-0.5 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of sensors-applet, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated sensors-applet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 15 Oct 2020 20:44:32 +0300 Source: sensors-applet Architecture: source Version: 3.0.0+git6-0.5 Distribution: unstable Urgency: medium Maintainer: Sam Morris Changed-By: Dmitry Shachnev Closes: 972277 Changes: sensors-applet (3.0.0+git6-0.5) unstable; urgency=medium . * Non-maintainer upload. * Install libsensors-applet.so in multi-arch location, for compatibility with gnome-panel 3.38 (closes: #972277). Checksums-Sha1: c0c532ada6e6eaebed0b48c5a4b21d5b420455f2 2364 sensors-applet_3.0.0+git6-0.5.dsc 1ffe0137654f39710d27b39f508d50860f17cb1d 20540 sensors-applet_3.0.0+git6-0.5.debian.tar.xz ba080c37dc593c5e20f15b43bd64bfd17e42ec38 15354 sensors-applet_3.0.0+git6-0.5_source.buildinfo Checksums-Sha256: f2f193cf74fa795e68916daac5d3c39e1121e095c465d014ca79f6afd338ed49 2364 sensors-applet_3.0.0+git6-0.5.dsc db607f64753d1677cbdef76532d77b0e58b902798c3b3c85e2a63d51a36de60a 20540 sensors-applet_3.0.0+git6-0.5.debian.tar.xz 42d9cb5ed73def22c081937db3cc579c086977e80dcb5cd1e7cc48e40dcb9700 15354 sensors-applet_3.0.0+git6-0.5_source.buildinfo Files: 3b8d8f5ac72b6eccd48fc7fc5f5768a6 2364 gnome optional sensors-applet_3.0.0+git6-0.5.dsc aa5f8313cd6533c1efccecaf13259a84 20540 gnome optional sensors-applet_3.0.0+git6-0.5.debian.tar.xz 8cae47ef9edb93767607c759c9ae3381
Bug#972334: llvm-toolchain-11: autopkgtest failure on i386: integration-test-suite-test FAIL non-zero exit status 2
Here are some extra details: -- Testing: 25 tests, 2 workers -- PASS: LLVM regression suite :: basic_clang_tidy.cpp (1 of 25) PASS: LLVM regression suite :: atomic_fetch.c (2 of 25) PASS: LLVM regression suite :: basic_lib++2.cpp (3 of 25) FAIL: LLVM regression suite :: basic_lldb.c (4 of 25) TEST 'LLVM regression suite :: basic_lldb.c' FAILED Script: -- : 'RUN: at line 1'; /usr/bin/clang-11 -g -o /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb.c.tmp /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/tests/basic_lldb.c : 'RUN: at line 2'; /usr/bin/lldb-11 -s /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/tests/basic_lldb.in /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb.c.tmp | grep "main at basic_lldb.c:" -- Exit Code: 1 Command Output (stderr): -- error: Lost debug server connection -- FAIL: LLVM regression suite :: basic_lldb2.cpp (5 of 25) TEST 'LLVM regression suite :: basic_lldb2.cpp' FAILED Script: -- : 'RUN: at line 1'; /usr/bin/clang++-11 -g -o /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb2.cpp.tmp /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/tests/basic_lldb2.cpp : 'RUN: at line 2'; /usr/bin/lldb-11 -s /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/tests/basic_lldb2.in /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb2.cpp.tmp | grep "stop reason = step over" -- Exit Code: 1 Command Output (stderr): -- error: Lost debug server connection -- PASS: LLVM regression suite :: basic_openmp.c (6 of 25) PASS: LLVM regression suite :: clang_format.c (7 of 25) PASS: LLVM regression suite :: code_coverage.cpp (8 of 25) PASS: LLVM regression suite :: code_profiling.cpp (9 of 25) PASS: LLVM regression suite :: from_chars.cpp (10 of 25) PASS: LLVM regression suite :: include_limits.c (11 of 25) PASS: LLVM regression suite :: llvm_config_libs.cpp (12 of 25) PASS: LLVM regression suite :: lto_and_cfi.c (13 of 25) PASS: LLVM regression suite :: minimal_llvm_cmake.txt (14 of 25) PASS: LLVM regression suite :: basic_lib++.cpp (15 of 25) PASS: LLVM regression suite :: partial-toolchain.cpp (16 of 25) PASS: LLVM regression suite :: rpass_inline.cpp (17 of 25) PASS: LLVM regression suite :: plugins.cpp (18 of 25) UNSUPPORTED: LLVM regression suite :: test_asan_heap.c (19 of 25) FAIL: LLVM regression suite :: test_asan_lc.c (20 of 25) TEST 'LLVM regression suite :: test_asan_lc.c' FAILED Script: -- : 'RUN: at line 4'; /usr/bin/clang-11 -fsanitize=address /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/tests/test_asan_lc.c -o /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_asan_lc.c.tmp -lc : 'RUN: at line 5'; /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_asan_lc.c.tmp -- Exit Code: 139 Command Output (stderr): -- /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_asan_lc.c.script: line 2: 2694 Segmentation fault /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_asan_lc.c.tmp -- FAIL: LLVM regression suite :: test_tsan.c (21 of 25) TEST 'LLVM regression suite :: test_tsan.c' FAILED Script: -- : 'RUN: at line 4'; /usr/bin/clang-11 -o /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp -fsanitize=thread -g -O1 /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/tests/test_tsan.c : 'RUN: at line 5'; /usr/bin/llvm-nm-11 /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp | grep __tsan : 'RUN: at line 6'; env TSAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp 2>&1 > /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp.out : 'RUN: at line 7'; grep -q "data race" /tmp/autopkgtest-lxc.zmambq90/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp.out -- Exit Code: 1 Command Output (stderr): -- clang: error: unsupported option '-fsanitize=thread' for target 'i686-pc-linux-gnu' -- PASS: LLVM regression suite :: warning_conversion.c (22 of 25) UNSUPPORTED: LLVM regression suite :: whole-toolchain.c (23 of 25) UNSUPPORTED: LLVM regression suite :: whole-toolchain.cpp (24 of 25) PASS: LLVM regression suite :: scanbuild_missing_delete.cpp (25 of 25) Unsupported Tests (3): LLVM regression suite :: test_asan_heap.c LLVM regression suite :: whole-toolchain.c LLVM regression suite :: whole-toolchain.cpp Failed Tests (4): LLVM regression suite :: basic_lldb.c LLVM regression suite :: basic_lldb2.cpp LLVM regression suite
Bug#972397: libguestfs: FTBFS: dh_install: error: missing files, aborting
Source: libguestfs Version: 1:1.42.0-10 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) libguestfs failed to build on the buildds: | dh_install -X.la -X.so.owner -Xbindtests -X/usr/lib/go/ -X/usr/lib/go- -Xpackages.orig -Xetc/php.d | dh_install: warning: Cannot find (any matches for) "usr/lib/python3*" (tried in ., debian/tmp) | | dh_install: warning: python3-guestfs missing files: usr/lib/python3* | dh_install: warning: Cannot find (any matches for) "usr/share/man/man3/guestfs-python.3*" (tried in ., debian/tmp) | | dh_install: warning: python3-guestfs missing files: usr/share/man/man3/guestfs-python.3* | dh_install: error: missing files, aborting | make[1]: *** [debian/rules:142: override_dh_install] Error 25 See https://buildd.debian.org/status/fetch.php?pkg=libguestfs=amd64=1%3A1.42.0-10=1602956228=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#972381: marked as done (python-biopython FTBFS with more than one supported python3 version)
Your message dated Sat, 17 Oct 2020 18:19:22 + with message-id and subject line Bug#972381: fixed in python-biopython 1.78+dfsg-3 has caused the Debian Bug report #972381, regarding python-biopython FTBFS with more than one supported python3 version 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.) -- 972381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-biopython Version: 1.78+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=python-biopython ... dh_missing -a -O--buildsystem=pybuild dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_advanced.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_advanced.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_align.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_align.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_appendix.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_appendix.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_blast.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_blast.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_cluster.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_cluster.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_contributing.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_contributing.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_cookbook.aux exists in debian/tmp but is not installed to anywhere ... dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_prodoc.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_prosite1.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_prosite2.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_psw.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_raxml_tool.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_samtools_tool.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_seq.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_translate.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/home/.cache/matplotlib/fontlist-v330.json exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: python-biopython-doc (0), python3-biopython (4), python3-biopython-sql (2) * dh_installdocs: python-biopython-doc (4), python3-biopython (4), python3-biopython-sql (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage
Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
* Richard W.M. Jones: > guestfsd: error while loading shared libraries: libtirpc.so.3: cannot > open shared object file: No such file or directory > > Did something change with how libtirpc gets packaged on Debian > or upstream? Yes, libtirpc package got renamed because that's what Debian does when a libaray SONAME changes. I hope that with the patch I just sent to the libgeustfs mailing list, this can all be ignored in the future. Cheers, -Hilko
Bug#972394: siconos: FTBFS could not find Python 3
Package: libsiconos-io-dev Version: 4.3.0+dfsg-1 Severity: serious Hi, while I was rebuilding all reverse-dependencies of bullet, I discovered that siconos fails to build from source. The issue is related to Python 3, maybe a missing build-dependency. Full build log is attached. The error message is: CMake Error at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message): Could NOT find Python3 (missing: Python3_INCLUDE_DIRS Python3_LIBRARIES Development NumPy Development.Module Development.Embed) (found version "3.9.0") Call Stack (most recent call first): /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:458 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.18/Modules/FindPython/Support.cmake:2966 (find_package_handle_standard_args) /usr/share/cmake-3.18/Modules/FindPython3.cmake:389 (include) cmake/SiconosSetup.cmake:58 (find_package) CMakeLists.txt:127 (include) Regards, Markus -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages libsiconos-io-dev depends on: pn libsiconos-io6 pn libsiconos-kernel-dev libsiconos-io-dev recommends no packages. libsiconos-io-dev suggests no packages. siconos_4.3.0+dfsg-1_amd64.build.gz Description: application/gzip
Processed: Re: Bug#957436: libfm-qt: ftbfs with GCC-10
Processing control commands: > tags -1 + pending Bug #957436 [src:libfm-qt] libfm-qt: ftbfs with GCC-10 Added tag(s) pending. -- 957436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957436: libfm-qt: ftbfs with GCC-10
Control: tags -1 + pending Hi! On Fri, Apr 17, 2020 at 11:04:16AM +, Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. As this failure is blocking the Qt 5.15 transition, I have uploaded the attached debdiff as NMU to DELAYED/5. -- Dmitry Shachnev diff -Nru libfm-qt-0.14.1/debian/changelog libfm-qt-0.14.1/debian/changelog --- libfm-qt-0.14.1/debian/changelog 2019-10-23 00:52:39.0 +0300 +++ libfm-qt-0.14.1/debian/changelog 2020-10-17 20:11:39.0 +0300 @@ -1,3 +1,10 @@ +libfm-qt (0.14.1-12.1) unstable; urgency=medium + + * Non-maintainer upload. + * Update symbols files for GCC 10 (closes: #957436). + + -- Dmitry Shachnev Sat, 17 Oct 2020 20:11:39 +0300 + libfm-qt (0.14.1-12) unstable; urgency=medium * Fixed symbol QRegEx -> QRegularExpression diff -Nru libfm-qt-0.14.1/debian/libfm-qt6.symbols libfm-qt-0.14.1/debian/libfm-qt6.symbols --- libfm-qt-0.14.1/debian/libfm-qt6.symbols 2019-10-23 00:50:33.0 +0300 +++ libfm-qt-0.14.1/debian/libfm-qt6.symbols 2020-10-17 20:11:39.0 +0300 @@ -1143,175 +1143,74 @@ (c++)"non-virtual thunk to Fm::RenameDialog::~RenameDialog()@Base" 0.10.0 (c++)"non-virtual thunk to Fm::SidePane::~SidePane()@Base" 0.10.0 (c++)"non-virtual thunk to Fm::ThumbnailJob::~ThumbnailJob()@Base" 0.12.0 + (c++)"std::_Fwd_list_base, std::allocator > >::_M_erase_after(std::_Fwd_list_node_base*, std::_Fwd_list_node_base*)@Base" 0.14.1 (c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !hurd-i386 !kfreebsd-i386 !m68k !powerpc !powerpcspe !sh4 !x32 )"std::_Hashtable, std::allocator > const, std::pair, std::allocator > const, std::shared_ptr >, std::allocator, std::allocator > const, std::shared_ptr > >, std::__detail::_Select1st, std::equal_to, std::allocator > const>, std::hash, std::allocator > >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_find_before_node(unsigned long, std::__cxx11::basic_string, std::allocator > const&, unsigned long) const@Base" 0.12.0 (c++|arch= !amd64 !arm64 !mips64el !ppc64el !s390x !alpha !ia64 !kfreebsd-amd64 !ppc64 !riscv64 !sparc64 )"std::_Hashtable, std::allocator > const, std::pair, std::allocator > const, std::shared_ptr >, std::allocator, std::allocator > const, std::shared_ptr > >, std::__detail::_Select1st, std::equal_to, std::allocator > const>, std::hash, std::allocator > >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_find_before_node(unsigned int, std::__cxx11::basic_string, std::allocator > const&, unsigned int) const@Base" 0.12.0 - (c++)"std::_Hashtable, std::allocator > const, std::pair, std::allocator > const, std::shared_ptr >, std::allocator, std::allocator > const, std::shared_ptr > >, std::__detail::_Select1st, std::equal_to, std::allocator > const>, std::hash, std::allocator > >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::clear()@Base" 0.12.0 - (c++)"std::_Hashtable, std::allocator > const, std::pair, std::allocator > const, std::shared_ptr >, std::allocator, std::allocator > const, std::shared_ptr > >, std::__detail::_Select1st, std::equal_to, std::allocator > const>, std::hash, std::allocator > >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::find(std::__cxx11::basic_string, std::allocator > const&)@Base" 0.12.0 - (optional|c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !hurd-i386 !m68k !powerpc !sh4 !x32 )"std::_Hashtable >, std::allocator > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned long, unsigned long, std::__detail::_Hash_node >, false>*, unsigned long)@Base" 0.13.0~ - (optional|c++|arch= armel armhf i386 mips mipsel hppa hurd-i386 m68k powerpc sh4 x32)"std::_Hashtable >, std::allocator > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned int, unsigned int, std::__detail::_Hash_node >, false>*, unsigned int)@Base" 0.13.0~ - (optional|c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !hurd-i386 !m68k !powerpc !sh4 !x32 )"std::_Hashtable >, std::allocator > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned long, unsigned long, std::__detail::_Hash_node
Bug#972241: marked as done (FTBFS on amd64 and i386 (error: guestfs_launch failed))
Your message dated Sat, 17 Oct 2020 17:05:03 + with message-id and subject line Bug#972241: fixed in libguestfs 1:1.42.0-10 has caused the Debian Bug report #972241, regarding FTBFS on amd64 and i386 (error: guestfs_launch failed) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libguestfs Version: 1:1.42.0-9 Severity: serious Tags: ftbfs Dear Maintainer, Your package FTBFS on amd64 and i386: https://buildd.debian.org/status/package.php?p=libguestfs=sid The rebuild was triggered by the update of OCaml from 4.08.1 to 4.11.1, but the error looks independent (I might be wrong). The build log ends with: > libguestfs: error: appliance closed the connection unexpectedly, see earlier > error messages > libguestfs: child_cleanup: 0x562f7794ec00: child process died > libguestfs: sending SIGTERM to process 3723 > libguestfs: qemu maxrss 405328K > libguestfs: error: guestfs_launch failed, see earlier error messages > libguestfs: closing guestfs handle 0x562f7794ec00 (state 0) > libguestfs: command: run: rm > libguestfs: command: run: \ -rf > /<>/debian/build-4/tmp/libguestfsv1zKZI > libguestfs: command: run: rm > libguestfs: command: run: \ -rf /tmp/libguestfsZpOSRI > make[2]: *** [Makefile:3087: quickcheck] Error 1 > make[2]: Leaving directory '/<>/debian/build-4' > make[1]: *** [debian/rules:126: override_dh_auto_test] Error 2 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:170: build-arch] Error 2 > dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit > status 2 Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 --- End Message --- --- Begin Message --- Source: libguestfs Source-Version: 1:1.42.0-10 Done: Hilko Bengen We believe that the bug you reported is fixed in the latest version of libguestfs, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated libguestfs 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, 17 Oct 2020 17:43:17 +0200 Source: libguestfs Architecture: source Version: 1:1.42.0-10 Distribution: unstable Urgency: medium Maintainer: Debian Libvirt Maintainers Changed-By: Hilko Bengen Closes: 972241 Changes: libguestfs (1:1.42.0-10) unstable; urgency=medium . * Build daemon, appliance only in last build * Add patch to generate library list for appliance (Closes: #972241) Checksums-Sha1: a4df2f2914959a891bd02b9ae7d14e83f513f9a6 5970 libguestfs_1.42.0-10.dsc 406055a3d5f682b002ff99a13d5052bb523332a0 43912 libguestfs_1.42.0-10.debian.tar.xz 6e62ddfc73f8d0caa2a79ca4c3836dd203cc1e31 18299 libguestfs_1.42.0-10_source.buildinfo Checksums-Sha256: a0349f1a1494f447515aeb0e9be6d878fa62164417893536bf83b155cce1d6c7 5970 libguestfs_1.42.0-10.dsc afcfa42d35c49f3aaf73f95c7ec6b9b325bfce2fa2d9f436ac23a146084cd6ea 43912 libguestfs_1.42.0-10.debian.tar.xz cded9d697176b4b94b5e7e1f886f2c68f8230d84f72c72b8822af55a7f0c5b7d 18299 libguestfs_1.42.0-10_source.buildinfo Files: efd4e4af8b3896fc3559574e5b4b5cb1 5970 libs optional libguestfs_1.42.0-10.dsc bc3575ece839d55ea881859c8a609ddb 43912 libs optional libguestfs_1.42.0-10.debian.tar.xz 09d65bd6ebbe780606fcbf54ebc13417 18299 libs optional libguestfs_1.42.0-10_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl+LH08SHGJlbmdlbkBk ZWJpYW4ub3JnAAoJEHW3EGNcITp+/VEQAJ7xRHtaNpc4I9tFO4XEo/oZLEkRSlna RtpXHGynFKbuNfZfNVoAli92CTUvFnX1f9kBIt7wkITpLrpbCpApx73MNdn7+vej Y0ewP5538Fwpiy0cvd2zUf1fo88JNor6iaUJaSCMew8RwADDhkStrfKFl6plaRw4
Bug#972258: marked as done (FTBFS (1 file would be reformatted))
Your message dated Sat, 17 Oct 2020 16:04:14 + with message-id and subject line Bug#972258: fixed in botch 0.22-5 has caused the Debian Bug report #972258, regarding FTBFS (1 file would be reformatted) 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.) -- 972258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:botch Version: 0.22-4 Severity: serious Tags: ftbfs Dear Maintainer, Your package botch currently FTBFS in sid: https://buildd.debian.org/status/package.php?p=botch The rebuild was triggered by the update of OCaml from 4.08.1 to 4.11.1, but the error looks independent (I might be wrong). The build log ends with: > pycodestyle --max-line-length=88 --ignore=E402,E203,W503 tools/*.py > black --check tools/*.py > would reformat /<>/tools/stat-html.py > Oh no! > 1 file would be reformatted, 38 files would be left unchanged. > make[2]: *** [Makefile:339: test-python] Error 1 > make[2]: Leaving directory '/<>' > make[1]: *** [debian/rules:25: override_dh_auto_test-arch] Error 2 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:7: binary-arch] Error 2 Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 --- End Message --- --- Begin Message --- Source: botch Source-Version: 0.22-5 Done: Johannes 'josch' Schauer We believe that the bug you reported is fixed in the latest version of botch, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes 'josch' Schauer (supplier of updated botch 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, 17 Oct 2020 16:53:50 +0200 Source: botch Architecture: source Version: 0.22-5 Distribution: unstable Urgency: medium Maintainer: Johannes 'josch' Schauer Changed-By: Johannes 'josch' Schauer Closes: 972258 Changes: botch (0.22-5) unstable; urgency=medium . * patch tools/stat-html.py to make black happy (closes: #972258) * add debian/patches/testsuite-fixes-new-ocaml.patch because of changes in dose3 and ocaml since the last upload Checksums-Sha1: a3a5ab42a57a1d79a99262c1090ed0a9fa9d71e5 3033 botch_0.22-5.dsc acdbbbf3a1a201961380e59934327c2e41df557e 1200668 botch_0.22-5.debian.tar.xz Checksums-Sha256: 448477ee060821ae70ab077cf148d8354fc07dae694626221395c636e6c89240 3033 botch_0.22-5.dsc 9572242a7809a74462d523dfeb7309e097e3228e4d24e56d6c342489c9049535 1200668 botch_0.22-5.debian.tar.xz Files: 99b4515230e2536ce80273718f33d694 3033 utils optional botch_0.22-5.dsc 14fc1702ee3147ebb88dca0236d58354 1200668 utils optional botch_0.22-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAl+LEOwACgkQ8sulx4+9 g+Hgmg/9G+jLQQrdMy0HTeaB1WBp2pICXesHxXzVovSEdv2bjTPIZAWxc/DLxgSD B/wDWWi7TvbeK7RiZ3jw8AJqdtvktv/0djuaOwvQBpjlXBxVk89XLgVoG3DrYE/n X7+poJK+eKJCV5DOi2+NQuFqc/0fOJv+j5weafi6gyRbl1kKJUPcMxlKaqLKgNsO xPWwx1gC+zyr3aGOMdVTQaoeWPE3At3TgWGlH1oKav5CnsOroKjEVUHycS8yCS4w JNst7CmFNw1oKxvuNUXklKivPO8+pi8oOmvjQNiQ/rMMIqgzOmB5L5U0iAWamTLc GqDT3i1C7But2n0Ot86FUe8KmefoeAXBmPvT20ppSWzIB8fIwvuv0u3iGOJMRgfM 6PuHzDAX9sT1Ft1TqH9jsHxfeyK5BcdAFNdgBRHnAlYofGCjOoAFb2VDxyj3f2Jg Ow3lLH8/7PdMZQ75V7REoV3yJk0p89/YgmiVHTcC8ETkzO2NXoDFcgRSE9N607yN ItsxH3w3CRJwrnQQo7qK/nNPP7tXEq/1R8rn4JrYbdsbeaZhvWFMoENScHjv4Vn9 7LSPKtgrwNbXlY5VArpPxJnoqase8Zje2nbeDf9biPklUu5jk489Hg/8DNQNIKTh 6V9n+AbeSfONkFpBYuHHv8L/fGVL+N/OYp/tKc+7ZljBBsus2fI= =9w3q -END PGP SIGNATURE End Message ---
Processed: tagging 972024
Processing commands for cont...@bugs.debian.org: > tags 972024 + ftbfs Bug #972024 [src:python-geotiepoints] python-geotiepoints ftbfs with python3.9 as supported python3 version Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: merge
Processing commands for cont...@bugs.debian.org: > forcemerge 969747 970259 925561 Bug #969747 [xfce4-weather-plugin] xfce4-weather-plugin: Weather plugin provides "No data" despite having internet connection and correct location Bug #969747 [xfce4-weather-plugin] xfce4-weather-plugin: Weather plugin provides "No data" despite having internet connection and correct location Marked as fixed in versions xfce4-weather-plugin/0.10.0-1. Marked as found in versions xfce4-weather-plugin/0.8.9-1. Added tag(s) fixed-upstream and upstream. Bug #925561 [xfce4-weather-plugin] xfce4-weather-plugin: API Outdated Marked as fixed in versions xfce4-weather-plugin/0.10.1-1. Added tag(s) upstream. Bug #970259 [xfce4-weather-plugin] xfce4-weather-plugin: API used is now obsolete Severity set to 'important' from 'grave' Marked as fixed in versions xfce4-weather-plugin/0.10.0-1 and xfce4-weather-plugin/0.10.1-1. Marked as found in versions xfce4-weather-plugin/0.8.9-1. Added tag(s) fixed-upstream. Merged 925561 969747 970259 > thanks Stopping processing here. Please contact me if you need assistance. -- 925561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925561 969747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969747 970259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merge
Processing commands for cont...@bugs.debian.org: > merge 969747 970259 925561 Bug #969747 [xfce4-weather-plugin] xfce4-weather-plugin: Weather plugin provides "No data" despite having internet connection and correct location Unable to merge bugs because: severity of #970259 is 'grave' not 'important' Failed to merge 969747: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 925561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925561 969747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969747 970259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972015: Bug#972033: python3.9 pandas
Control: tags -1 patch The underlying cause (and reason this is 3.9-specific) appears to be the mostly-removal of ast.Index and its replacement by a bare value. This appears to fix it, though I'm not yet sure if it's a good idea: --- a/pandas/core/computation/pytables.py +++ b/pandas/core/computation/pytables.py @@ -425,6 +425,10 @@ class PyTablesExprVisitor(BaseExprVisito value = value.value except AttributeError: pass +try: +slobj = slobj.value +except AttributeError: +pass try: return self.const_type(value[slobj], self.env)
Processed (with 1 error): fixed in xfce4-weather-plugin 0.10.1-1
Processing control commands: > fixed -1 0.10.1-1 Bug #969747 [xfce4-weather-plugin] xfce4-weather-plugin: Weather plugin provides "No data" despite having internet connection and correct location Marked as fixed in versions xfce4-weather-plugin/0.10.1-1. > merge -1 970259 Bug #969747 [xfce4-weather-plugin] xfce4-weather-plugin: Weather plugin provides "No data" despite having internet connection and correct location Unable to merge bugs because: severity of #970259 is 'grave' not 'important' Failed to merge 969747: Did not alter merged bugs. -- 969747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969747 970259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972015: Bug#972033: python3.9 pandas
This bug is not specific to DateTimeIndexes, and the immediate cause is
the index being passed to numpy as a
pandas.core.computation.pytables.Constant instead of an int:
$ python3.9
Python 3.9.0+ (default, Oct 16 2020, 17:57:59)
[GCC 10.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pandas as pd;from pandas.io.pytables import
HDFStore;s1=HDFStore("tmp1.h5","w");df=pd.DataFrame([[1,2,3],[4,5,6]],columns=['A','B','C']);s1.append("d1",df,data_columns=["B"]);df2=s1.select("d1","index>df.index[0]");print(type(df2.index[0]))
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pandas/io/pytables.py", line
876, in select
return it.get_result()
File "/usr/lib/python3/dist-packages/pandas/io/pytables.py", line
1930, in get_result
results = self.func(self.start, self.stop, where)
File "/usr/lib/python3/dist-packages/pandas/io/pytables.py", line
860, in func
return s.read(start=_start, stop=_stop, where=_where, columns=columns)
File "/usr/lib/python3/dist-packages/pandas/io/pytables.py", line
4483, in read
result = self._read_axes(where=where, start=start, stop=stop)
File "/usr/lib/python3/dist-packages/pandas/io/pytables.py", line
3682, in _read_axes
selection = Selection(self, where=where, start=start, stop=stop)
File "/usr/lib/python3/dist-packages/pandas/io/pytables.py", line
5167, in __init__
self.terms = self.generate(where)
File "/usr/lib/python3/dist-packages/pandas/io/pytables.py", line
5180, in generate
return PyTablesExpr(where, queryables=q, encoding=self.table.encoding)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/pytables.py",
line 573, in __init__
self.terms = self.parse()
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
806, in parse
return self._visitor.visit(self.expr)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
398, in visit
return visitor(node, **kwargs)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
404, in visit_Module
return self.visit(expr, **kwargs)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
398, in visit
return visitor(node, **kwargs)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
407, in visit_Expr
return self.visit(node.value, **kwargs)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
398, in visit
return visitor(node, **kwargs)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
699, in visit_Compare
return self.visit(binop)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
398, in visit
return visitor(node, **kwargs)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
520, in visit_BinOp
op, op_class, left, right = self._maybe_transform_eq_ne(node)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
441, in _maybe_transform_eq_ne
right = self.visit(node.right, side="right")
File
"/usr/lib/python3/dist-packages/pandas/core/computation/expr.py", line
398, in visit
return visitor(node, **kwargs)
File
"/usr/lib/python3/dist-packages/pandas/core/computation/pytables.py",
line 430, in visit_Subscript
return self.const_type(value[slobj], self.env)
File "/usr/lib/python3/dist-packages/pandas/core/indexes/range.py",
line 720, in __getitem__
return super().__getitem__(key)
File "/usr/lib/python3/dist-packages/pandas/core/indexes/base.py",
line 4111, in __getitem__
result = getitem(key)
IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis
(`None`) and integer or boolean arrays are valid indices
>>> import pdb;pdb.pm()
>
/usr/lib/python3/dist-packages/pandas/core/indexes/base.py(4111)__getitem__()
-> result = getitem(key)
(Pdb) p key
0
(Pdb) p type(key)
(Pdb)
Bug#972385: petsc4py: autopkgtest failure on amd64: Caught signal number 11 SEGV
Source: petsc4py Version: 3.13.0-8 Severity: serious User: debian...@lists.debian.org Usertags: regression X-Debbugs-Cc: debian...@lists.debian.org The autopkgtest for amd64 currently fail: | python3 run_demo.py | [0]PETSC ERROR: | [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range | [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger | [0]PETSC ERROR: or see https://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind | [0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors | [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run | [0]PETSC ERROR: to get more information on the crash. | -- | MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD | with errorcode 50162059. | | NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes. | You may or may not see output from other processes, depending on | exactly when Open MPI kills them. | -- | make[1]: *** [makefile:17: run] Error 139 See https://ci.debian.net/data/autopkgtest/testing/amd64/p/petsc4py/7426792/log.gz for the full log Regards, Aurelien
Bug#972384: rspamd: autopkgtest failure on i386: curl: (7) Failed to connect to 127.0.0.1 port 11334: Connection refused
Source: rspamd Version: 2.5-3 Severity: serious User: debian...@lists.debian.org Usertags: regression X-Debbugs-Cc: debian...@lists.debian.org The autopkgtest for i386 currently fail: | autopkgtest [22:03:01]: test install: ---] | autopkgtest [22:03:01]: test install: - - - - - - - - - - results - - - - - - - - - - | install FAIL stderr: curl: (7) Failed to connect to 127.0.0.1 port 11334: Connection refused | autopkgtest [22:03:01]: test install: - - - - - - - - - - stderr - - - - - - - - - - | curl: (7) Failed to connect to 127.0.0.1 port 11334: Connection refused | Warning: Transient problem: connection refused Will retry in 2 seconds. 3 | Warning: retries left. See https://ci.debian.net/data/autopkgtest/testing/i386/r/rspamd/7443860/log.gz for the full log. Regards, Aurelien
Bug#972380: braillefont FTBFS
tags 972380 +pending thanks Fixed in vcs. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#972380: braillefont FTBFS
Processing commands for cont...@bugs.debian.org: > tags 972380 +pending Bug #972380 [src:braillefont] braillefont FTBFS Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 972380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#972033: python3.9 pandas
Processing control commands: > tags -1 patch Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version Ignoring request to alter tags of bug #972033 to the same tags previously set Ignoring request to alter tags of bug #972015 to the same tags previously set -- 972015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972015 972033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#972033: python3.9 pandas
Processing control commands: > tags -1 patch Bug #972015 [src:pandas] pandas ftbfs with python3 as supported python version Bug #972033 [src:pandas] pandas ftbfs with python3.9 as supported python version Added tag(s) patch. Added tag(s) patch. -- 972015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972015 972033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forward 972006
Processing commands for cont...@bugs.debian.org: > forwarded 972006 https://github.com/pypr/compyle/issues/64 Bug #972006 [src:compyle] pycompyle ftbfs with python3.9 (test failures) Set Bug forwarded-to-address to 'https://github.com/pypr/compyle/issues/64'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 972374
Processing commands for cont...@bugs.debian.org: > tags 972374 + ftbfs Bug #972374 [src:qiskit-terra] qiskit-terra ftbfs with python3.9 as supported python3 version Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972381: python-biopython FTBFS with more than one supported python3 version
Source: python-biopython Version: 1.78+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=python-biopython ... dh_missing -a -O--buildsystem=pybuild dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_advanced.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_advanced.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_align.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_align.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_appendix.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_appendix.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_blast.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_blast.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_cluster.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_cluster.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_contributing.aux exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_contributing.tex exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Doc/Tutorial/chapter_cookbook.aux exists in debian/tmp but is not installed to anywhere ... dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_prodoc.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_prosite1.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_prosite2.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_psw.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_raxml_tool.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_samtools_tool.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_seq.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/Tests/test_translate.py exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/python3.9/dist-packages/home/.cache/matplotlib/fontlist-v330.json exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: python-biopython-doc (0), python3-biopython (4), python3-biopython-sql (2) * dh_installdocs: python-biopython-doc (4), python3-biopython (4), python3-biopython-sql (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built If the omission is intentional or no other helper can take care of this consider adding the paths to debian/not-installed. make: *** [debian/rules:42: binary-arch] Error 25
Bug#972380: braillefont FTBFS
Source: braillefont Version: 1.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=braillefont=sid ... dpkg-buildpackage: info: host architecture arm64 debian/rules clean make clean make[1]: Entering directory '/<>' rm -f braillefont braillefont.o 6x8font.h make[1]: Leaving directory '/<>' rm -rf debian/braillefont rm -f debian/substvars rm -f debian/debugsymbols rm -f debian/files rm -f build-stamp rm -rf debian/braillefont-dbgsym debian/rules binary-arch readelf: Error: 'braillefont': No such file readelf: Error: 'braillefont': No such file readelf: Error: 'braillefont': No such file readelf: Error: 'braillefont': No such file ### PKG braillefont ### # install executable install -m 755 -d debian/braillefont/usr/games install -m 755 braillefont debian/braillefont/usr/games install: cannot stat 'braillefont': No such file or directory make: *** [debian/rules:102: binary-arch] Error 1
Bug#972377: pyasn FTBFS: FileNotFoundError in tests
Source: pyasn Version: 1.6.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=pyasn=sid ... I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_pyasn/build; python3.8 -m nose -v tests Checks compatibility of PyASN 1.2 results with current pyasn for all 2014 ipasn dbs . ... SKIPPING - Python 2 or PyASN 1.2 not present ... ok Failure: FileNotFoundError ([Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.8_pyasn/build/tests/../data/ipasn_20140513.dat.gz') ... ERROR Tests pyasn.mrtx.parse_mrt_file() - converts a full (TD1) RIB file, and compares ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() - converts a full (TD2) RIB file, and compares ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() - converts a full (TD2) RIB file with IPv6; ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx internal classes by converting start of an RIB6 TD2 file (IPv6) ... ERROR Tests pyasn.mrtx internal classes by converting start of an RIB TD1 file ... ERROR Tests pyasn.mrtx internal classes by converting start of an RIB TD2 file ... ERROR Tests pyasn.mrtx.parse_mrt_file() with repeated prefixes causing errros (bug #39) ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() with routeviews WIDE archive TD1 (bug #42) ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() with skip_record_on_error set to True ... ERROR Tests pyasn.mrtx.parse_mrt_file() with skip_record_on_error set to default(False); ... ERROR Failure: FileNotFoundError ([Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.8_pyasn/build/tests/../data/ipasn_20140513.dat.gz') ... ERROR == ERROR: Failure: FileNotFoundError ([Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.8_pyasn/build/tests/../data/ipasn_20140513.dat.gz') -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in loadTestsFromName module = self.importer.importFromPath( File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.8/imp.py", line 234, in load_module return load_source(name, filename, file) File "/usr/lib/python3.8/imp.py", line 171, in load_source module = _load(spec) File "", line 702, in _load File "", line 671, in _load_unlocked File "", line 783, in exec_module File "", line 219, in _call_with_frames_removed File "/<>/.pybuild/cpython3_3.8_pyasn/build/tests/test_comparative.py", line 39, in class TestCorrectness(TestCase): File "/<>/.pybuild/cpython3_3.8_pyasn/build/tests/test_comparative.py", line 40, in TestCorrectness asndb = pyasn.pyasn(IPASN_DB_PATH) File "/<>/.pybuild/cpython3_3.8_pyasn/build/pyasn/__init__.py", line 64, in __init__ f = gzip.open(ipasn_file, 'rt') # Py2.6 doesn't support 'with' for gzip File "/usr/lib/python3.8/gzip.py", line 58, in open binary_file = GzipFile(filename, gz_mode, compresslevel) File "/usr/lib/python3.8/gzip.py", line 173, in __init__ fileobj = self.myfileobj = builtins.open(filename, mode or 'rb') FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.8_pyasn/build/tests/../data/ipasn_20140513.dat.gz' == ERROR: Tests pyasn.mrtx internal classes by converting start of an RIB6 TD2 file (IPv6) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.8_pyasn/build/tests/test_mrtx.py", line 309, in test_mrt6_table_dump_v2 f = BZ2File(RIB6_TD2_PARTDUMP, 'rb') File "/usr/lib/python3.8/bz2.py", line 96, in __init__ self._fp = _builtin_open(filename, mode) FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.8_pyasn/build/tests/../data/rib6.20151101.0600_firstMB.bz2' == ERROR: Tests pyasn.mrtx internal classes by converting start of an RIB TD1 file -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.8_pyasn/build/tests/test_mrtx.py", line 135, in test_mrt_table_dump_v1 f = BZ2File(RIB_TD1_PARTDUMP, 'rb') File "/usr/lib/python3.8/bz2.py", line 96, in __init__ self._fp = _builtin_open(filename, mode) FileNotFoundError: [Errno 2] No such file or directory:
Bug#972374: qiskit-terra ftbfs with python3.9 as supported python3 version
Package: src:qiskit-terra
Version: 0.12.0-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
qiskit-terra ftbfs with python3.9 as supported python3 version:
[...]
dh_auto_test -a -O--buildsystem=pybuild
pybuild --test -i python{version} -p "3.9 3.8"
I: pybuild pybuild:284: cp -r /<>/qiskit/schemas/examples
/<>/.pybuild/cpython3_3.9/build/qiskit/schemas
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9/build; python3.9
-m pytest test/python -k "not (test_generate_latex or TestLatexSourceGenerator
or test_jupyter_jobs_pbars)"
= test session starts ==
platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
rootdir: /<>
collected 0 items / 166 errors
ERRORS
_ ERROR collecting .pybuild/cpython3_3.9/build/test/python/test_dagcircuit.py __
/usr/lib/python3/dist-packages/py/_path/local.py:704: in pyimport
__import__(modname)
test/__init__.py:18: in
from qiskit.test.utils import generate_cases
qiskit/test/__init__.py:17: in
from .base import QiskitTestCase
qiskit/test/base.py:29: in
from .utils import Path, _AssertNoLogsContext, setup_test_logging
qiskit/test/utils.py:71: in
class _AssertNoLogsContext(unittest.case._AssertLogsContext):
E AttributeError: module 'unittest.case' has no attribute '_AssertLogsContext'
__ ERROR collecting .pybuild/cpython3_3.9/build/test/python/test_examples.py ___
/usr/lib/python3/dist-packages/py/_path/local.py:704: in pyimport
__import__(modname)
test/__init__.py:18: in
from qiskit.test.utils import generate_cases
qiskit/test/__init__.py:17: in
from .base import QiskitTestCase
qiskit/test/base.py:29: in
from .utils import Path, _AssertNoLogsContext, setup_test_logging
qiskit/test/utils.py:71: in
class _AssertNoLogsContext(unittest.case._AssertLogsContext):
E AttributeError: module 'unittest.case' has no attribute '_AssertLogsContext'
_ ERROR collecting .pybuild/cpython3_3.9/build/test/python/test_qasm_parser.py _
Bug#972340: marked as done (pyferret FTBFS with more than one supported python3 version)
Your message dated Sat, 17 Oct 2020 08:36:34 + with message-id and subject line Bug#972347: fixed in pyferret 7.6.3-2 has caused the Debian Bug report #972347, regarding pyferret FTBFS with more than one supported python3 version 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.) -- 972347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyferret Version: 7.6.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=pyferret=sid ... dh_missing -a dh_missing: warning: lib/python3.9/libpyferret.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/lib/python3.8/libpyferret.so") dh_missing: error: missing files, aborting ... --- End Message --- --- Begin Message --- Source: pyferret Source-Version: 7.6.3-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of pyferret, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated pyferret 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, 17 Oct 2020 08:52:39 +0100 Source: pyferret Architecture: source Version: 7.6.3-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 972347 972430 Changes: pyferret (7.6.3-2) unstable; urgency=medium . * Update d/not-installed to work with python3.9. Closes: #972430, #972347 * Minor fixes to d/copyright syntax * Include missing files in d/missing (from git HEAD): - load_dsg_mask_ftrset_var.F - disp_data_set_up.F - dsg_traj_alongxy_setup.F - tm_dsg_ftrset_facts.F - plot_vs_set_up.F - make_dsg_ftrset_mask.F - reload_dsg_ftrmaskvar.F - dsg_pltalong_setup.F - make_dsg_feature_mask_dirs.F Checksums-Sha1: c4619d3b21b1487d0eed381c6b25b7b28d5cd699 2223 pyferret_7.6.3-2.dsc 24d9eb445f3bef380d40e949cfbdffc3f35733aa 40384 pyferret_7.6.3-2.debian.tar.xz Checksums-Sha256: 6772e49fcaa5e9de0f45b0062d170e59f5e98febc263442f6d8d6d3944caac02 2223 pyferret_7.6.3-2.dsc 7beaeb4d5fa54f475df89990bf1c9f91b4e5003d29c5203ae83b728dc7582904 40384 pyferret_7.6.3-2.debian.tar.xz Files: 59db6238f5b71c005f0a0c49d5bc242f 2223 science optional pyferret_7.6.3-2.dsc 7106f9ede624845ba6e31a5a5e2d7d0a 40384 science optional pyferret_7.6.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl+KpyUACgkQy+a7Tl2a 06XNkw//ZlzZ+Xu4e++I1bxeCNueEf07EArVjiVB2vt4VfTVacYB4KH1VaKTpqXa 4t51kLzQphbSBaQadvTibr4TIsFIEh3leyBo03ZSfDrkDvACQeAofv27tsBFPlK7 yYYVwFRMhez7l4p4jjV3ljhjc4NBfwqZKb00Cku1d5q9Udjm9iY63IhfKWuISj87 +Bdl1E8aOwpZBi8GLb1KM3b8GEMMw8f4HaoKIjBYLrPCkdwpvTAmbYPWNYeboenA B+zPCMp1YABWinYrO/buqwSAA/xUkqBRKR+NjQMXyD8m1TJOjcK1E728M/cng6Zx 2Tk4P+himaPdylBa5HuXA3oo1+c15ePwoFIhjUKcTbBPfEOIVCEsQaDUh9YykqWt 1IIsFRZ5sO3jVGFraQXzeJosdO5h5WmxH3jlxXDYXzi1lZ4htij9tPH5TIW5fqEF /LA2u6uEGrNxgwMyFHZoKQbSDo9xM1CQ/TMqbXPggnIMEgQgiFhjWNdlPOAdUneW TkmcbAmMxIi75vvRaEYL0RMnbvpNyGn2Pftxf9kpn8/NmuNXbUQy9Q1ygchqzJL3 kzqKYixhok6DoYC4EZ29ybmB2avOSxSbsvvA2CW8czwXiE/Q2BKvFiUd4haS5s2Z RCv56Y5l+N3PWeGfhHIZd/t1IwyCFvUxUwdjfYg2N5xaWQ7cyo0= =M/Ys -END PGP SIGNATURE End Message ---
Bug#972347: marked as done (pyferret ftbfs with python3.9 as supported python3 version)
Your message dated Sat, 17 Oct 2020 08:36:34 +
with message-id
and subject line Bug#972347: fixed in pyferret 7.6.3-2
has caused the Debian Bug report #972347,
regarding pyferret ftbfs with python3.9 as supported python3 version
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.)
--
972347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyferret
Version: 5.3+dfsg1-3
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9
pyferret ftbfs with python3.9 as supported python3 version, packaging issue:
[...]
dh_python3 -a
D: dh_python3 dh_python3:161: version: 4.20200925
D: dh_python3 dh_python3:162: argv: ['/usr/bin/dh_python3', '-a']
D: dh_python3 dh_python3:163: options: {'guess_deps': True, 'skip_private':
False, 'verbose': False, 'arch': True, 'package': None, 'no_package': None,
'compile_all': False, 'vrange': None, 'regexpr': None,
'accept_upstream_versions': False, 'depends': None, 'depends_section': None,
'recommends': None, 'recommends_section': None, 'suggests': None,
'suggests_section': None, 'requires': None, 'shebang': None, 'ignore_shebangs':
False, 'clean_dbg_pkg': True, 'no_ext_rename': False, 'no_shebang_rewrite':
False, 'O': None}
D: dh_python3 dh_python3:164: args: []
D: dh_python3 dh_python3:165: supported Python versions: 3.8,3.9 (default=3.8)
D: dh_python3 debhelper:152: source=pyferret, binary packages=['python3-ferret']
D: dh_python3 dh_python3:183: processing package python3-ferret...
D: dh_python3 tools:102: fix_shebang (debian/python3-ferret/usr/bin/pyferret3):
doesn't look like a shebang: #! /bin/sh
I: dh_python3 fs:420: renaming gcircle-7.63-py3.8.egg-info to
gcircle-7.63.egg-info
I: dh_python3 fs:416: removing gcircle-7.63-py3.9.egg-info
(gcircle-7.63.egg-info is already available)
I: dh_python3 fs:420: renaming pipedviewer-7.63-py3.8.egg-info to
pipedviewer-7.63.egg-info
I: dh_python3 fs:416: removing pipedviewer-7.63-py3.9.egg-info
(pipedviewer-7.63.egg-info is already available)
I: dh_python3 fs:420: renaming pyferret-7.63-py3.8.egg-info to
pyferret-7.63.egg-info
I: dh_python3 fs:416: removing pyferret-7.63-py3.9.egg-info
(pyferret-7.63.egg-info is already available)
D: dh_python3 fs:260: package python3-ferret details = {'requires.txt': set(),
'egg-info':
{'debian/python3-ferret/usr/lib/python3/dist-packages/pipedviewer-7.63.egg-info',
'debian/python3-ferret/usr/lib/python3/dist-packages/gcircle-7.63.egg-info',
'debian/python3-ferret/usr/lib/python3/dist-packages/pyferret-7.63.egg-info'},
'nsp.txt': set(), 'shebangs': set(), 'public_vers': {Version('3')},
'private_dirs': {}, 'compile': True, 'ext_vers': {Version('3.8'),
Version('3.9')}, 'ext_no_version': set()}
D: dh_python3 depends:117: generating dependencies for package python3-ferret
D: dh_python3 pydist:142: trying to find dependency for multiprocessing
(python=None)
D: dh_python3 pydist:210: invoking dpkg -S
*python3/*/[Mm][Uu][Ll][Tt][Ii][Pp][Rr][Oo][Cc][Ee][Ss][Ss][Ii][Nn][Gg]-?*\.egg-info
D: dh_python3 pydist:226: dpkg -S did not find package for multiprocessing:
b'dpkg-query: no path found matching pattern
*python3/*/[Mm][Uu][Ll][Tt][Ii][Pp][Rr][Oo][Cc][Ee][Ss][Ss][Ii][Nn][Gg]-?*.egg-info\n'
I: dh_python3 pydist:229: Cannot find package that provides multiprocessing.
Please add package that provides it to Build-Depends or add "multiprocessing
python3-multiprocessing" line to debian/py3dist-overrides or add proper
dependency to Depends by hand and ignore this info.
D: dh_python3 pydist:142: trying to find dependency for numpy (python=None)
D: dh_python3 pydist:142: trying to find dependency for numpy (python=None)
D: dh_python3 depends:275: D={'python3 (<< 3.10)', 'python3 (>= 3.8~)',
'python3:any', 'python3:any (>= 3.6~)', 'python3-numpy'}; R=[]; S=[]; E=[],
B=[]; RT=[]
dh_lintian -a
install -d debian/python3-ferret/usr/share/lintian/overrides
install -p -m0644 debian/python3-ferret.lintian-overrides
debian/python3-ferret/usr/share/lintian/overrides/python3-ferret
dh_perl -a
dh_link -a
dh_strip_nondeterminism -a
dh_compress -a
cd debian/python3-ferret
chmod a-x usr/share/doc/python3-ferret/changelog.Debian
usr/share/doc/python3-ferret/changelog.Debian.amd64
gzip -9nf usr/share/doc/python3-ferret/changelog.Debian
usr/share/doc/python3-ferret/changelog.Debian.amd64
cd '/<>'
dh_fixperms -a
find debian/python3-ferret -true -print0 2>/dev/null | xargs -0r chown
--no-dereference 0:0
find
Bug#972372: sfepy FTBFS on 32bit with gcc 10
Source: sfepy Version: 2019.4-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/history/armhf/sfepy.html https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/armhf/sfepy.html https://buildd.debian.org/status/logs.php?pkg=sfepy=2019.4-2%2Bb2 ... Extension error: Could not import extension gen_term_table (exception: /<>/sfepy/discrete/common/extmods/cmesh.cpython-38-arm-linux-gnueabi.so: undefined symbol: _aux_hex) make[3]: *** [Makefile:35: html] Error 2
Bug#972340: pyferret FTBFS with more than one supported python3 version
I sat down to have a look at this, and struggled to figure out what the
package is actually trying to do in its build.
There's some wacky stuff going on, which isn't actually working, so I
started by trimming that out, and enabling set -e.
> dh_missing: warning: lib/python3.9/libpyferret.so exists in debian/tmp but is
> not installed to anywhere (related file:
> "debian/tmp/lib/python3.8/libpyferret.so")
From what I can see, this library is a symlink, created for other
libraries to link to, but not installing under that name, only as a
Python C extension.
With the attached patchset, I can get it to build with 3.8 and 3.9,
which gets us to the same state as unstable, which is totally broken:
$ pyferret3
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pyferret/__init__.py", line 75, in
from pyferret import libpyferret
ImportError:
/usr/lib/python3/dist-packages/pyferret/libpyferret.cpython-38-x86_64-linux-gnu.so:
undefined symbol: load_dsg_mask_ftrset_var_
>>>
Then there's all the shared libraries in
/usr/lib/ferret-vis/external_functions/pylibs that want to link to
libpyferret:
$ ldd /usr/lib/ferret-vis/external_functions/pylibs/subtract.so
linux-vdso.so.1 (0x7ffdd76ad000)
libeatmydata.so => /usr/lib/x86_64-linux-gnu/libeatmydata.so
(0x7f30e9d3d000)
libpyferret.so => not found
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f30e9d37000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f30e9b72000)
/lib64/ld-linux-x86-64.so.2 (0x7f30e9d4f000)
I don't know what's supposed to use those, but they probably shouldn't
be linking to a library that isn't installed.
If there are plugins like this that need to link to C Python Extensions,
I don't know if it makes any sense to build pyferret for multiple Python
versions. But I don't know enough about the package, to understand
exactly what they are for, and how they're meant to be linked.
So... Some patches attached that get us to the broken status-quo of
unstable, but not sure that that's a useful place to be. I'm certainly
not going to NMU them.
I'd have filed an MR, but the git repo is out of date...
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
From e6f7f375be676af36ce19c0e2e2057ba55d84094 Mon Sep 17 00:00:00 2001
From: Stefano Rivera
Date: Fri, 16 Oct 2020 23:01:16 -0700
Subject: [PATCH 1/4] debian/rules: set -e; before any multi-command lines.
---
debian/changelog | 7 +++
debian/rules | 2 ++
2 files changed, 9 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 7c959ea..977e734 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+pyferret (7.6.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/rules: set -e; before any multi-command lines.
+
+ -- Stefano Rivera Fri, 16 Oct 2020 23:00:38 -0700
+
pyferret (7.6.3-1) unstable; urgency=medium
* New upstream release
diff --git a/debian/rules b/debian/rules
index 5ba46b2..5c7c0f2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -41,6 +41,7 @@ override_dh_auto_install:
# Horrible hack breaks The Debian Way. I'm doing the build in the 'install' phase, as i'm installing into debian/tmp
# Doing it any earlier, and dh_prep will remove debian/tmp.
# This means I'm also doing 'test' after the Install, not between during make & install. gack.
+ set -e; \
for p in $(PY3) ; do \
mkdir -p $(INSTALLDIR)/lib/$$p ; \
cp $(CURDIR)/install/lib/$$p/site-packages//pyferret/libpyferret.cpython-$$l-$(ARCH).so \
@@ -57,6 +58,7 @@ override_dh_auto_install:
@echo "Now doing bench tests"
ln -s debian/pyferret3 $(INSTALLDIR)/lib/$(shell py3versions -d)/pyferret
# First build necessary files
+ set -e; \
for p in $(PY3) ; do \
sed -e 's%@ARCH@%${ARCH}%' \
-e 's%@LIBDIR@%${LIBDIR}%' \
--
2.28.0
From 626a273af6853f66e5e989df539e53dcd31a3e7f Mon Sep 17 00:00:00 2001
From: Stefano Rivera
Date: Fri, 16 Oct 2020 23:01:53 -0700
Subject: [PATCH 2/4] debian/rules: Drop cp that wasn't executing, because
there is no "l" variable.
---
debian/changelog | 2 ++
debian/rules | 2 --
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 977e734..79073a0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,8 @@ pyferret (7.6.3-1.1) UNRELEASED; urgency=medium
* Non-maintainer upload.
* debian/rules: set -e; before any multi-command lines.
+ * debian/rules: Drop cp that wasn't executing, because there is no "l"
+variable.
-- Stefano Rivera Fri, 16 Oct 2020 23:00:38 -0700
diff --git a/debian/rules b/debian/rules
index 5c7c0f2..75b0854 100755
--- a/debian/rules
+++ b/debian/rules
@@ -44,8 +44,6 @@ override_dh_auto_install:
set -e; \
for p in $(PY3) ; do \
mkdir -p $(INSTALLDIR)/lib/$$p ; \
- cp $(CURDIR)/install/lib/$$p/site-packages//pyferret/libpyferret.cpython-$$l-$(ARCH).so \
Processed: notfound 972340 in pyferret/5.3+dfsg1-3
Processing commands for cont...@bugs.debian.org: > notfound 972340 pyferret/5.3+dfsg1-3 Bug #972340 [src:pyferret] pyferret FTBFS with more than one supported python3 version Bug #972347 [src:pyferret] pyferret ftbfs with python3.9 as supported python3 version The source pyferret and version 5.3+dfsg1-3 do not appear to match any binary packages No longer marked as found in versions pyferret/5.3+dfsg1-3. No longer marked as found in versions pyferret/5.3+dfsg1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 972340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972340 972347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 963639 is forwarded to https://github.com/pygame/pygame/issues/2202
Processing commands for cont...@bugs.debian.org: > forwarded 963639 https://github.com/pygame/pygame/issues/2202 Bug #963639 [src:pygame] pygame: FTBFS with Sphinx 3.1: Invalid C declaration: Expected identifier in nested name. [error at 9] PyObject \*pgExc_BufferError Set Bug forwarded-to-address to 'https://github.com/pygame/pygame/issues/2202'. > thanks Stopping processing here. Please contact me if you need assistance. -- 963639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859926: speechd-up: fails to install
Hi Dennis, Samuel, On 02-09-2020 17:46, Dennis Filder wrote: > I looked into this a bit and came up with the attached patch (written > against 0.10.1-2), but for further improvement I'd need some feedback. > > The patch adds a new thread that is on the lookout for Pulseaudio > processes and reconfigures/restarts the output modules accordingly > once it finds one. This allows speech-dispatcher (with the correct > privileges) to transition between ALSA and Pulseaudio without the need > for a restart (albeit with the loss of the not-yet-spoken messages in > the module and a pause of about 1-2 seconds). In my experience it > works quite nicely. > > I don't doubt that making the output modules do the transition > themselves without restarting them would be better, but that would > require changes far more intrusive than the ones in this patch. > > N.B.: For this to fix the original bug during installation of > speechd-up, the default for AudioOutputMethod would have to be changed > to "pulse,alsa". @Dennis, thanks a lot for working on this. Did you send this upstream as well? If not, can you do it or do you prefer we do it? @Samuel, what do you think of the patch. It's way to involved for me to judge, but it claims to solve a long standing RC issue. Paul signature.asc Description: OpenPGP digital signature
