Bug#972028: python-acora: diff for NMU version 2.2-1.3
Control: tags 972028 + patch
Control: tags 972028 + pending
Dear maintainer,
I've prepared an NMU for python-acora (versioned as 2.2-1.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
SR
diff -Nru python-acora-2.2/debian/changelog python-acora-2.2/debian/changelog
--- python-acora-2.2/debian/changelog 2019-12-22 20:03:28.0 -0800
+++ python-acora-2.2/debian/changelog 2020-10-15 22:32:00.0 -0700
@@ -1,3 +1,11 @@
+python-acora (2.2-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Delete generated C before build, and in clean, to ensure regeneration with
+cython. Fixes FTBFS with Python 3.9. (Closes: #972028)
+
+ -- Stefano Rivera Thu, 15 Oct 2020 22:32:00 -0700
+
python-acora (2.2-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru python-acora-2.2/debian/clean python-acora-2.2/debian/clean
--- python-acora-2.2/debian/clean 1969-12-31 16:00:00.0 -0800
+++ python-acora-2.2/debian/clean 2020-10-15 22:29:55.0 -0700
@@ -0,0 +1 @@
+acora/*.c
diff -Nru python-acora-2.2/debian/rules python-acora-2.2/debian/rules
--- python-acora-2.2/debian/rules 2019-12-22 20:03:23.0 -0800
+++ python-acora-2.2/debian/rules 2020-10-15 22:29:46.0 -0700
@@ -1,6 +1,7 @@
#!/usr/bin/make -f
export PYBUILD_NAME:= acora
+export PYBUILD_BEFORE_BUILD := rm -f $(wildcard acora/*.c)
export PYBUILD_BEFORE_TEST := cp -a test.py README.rst {build_dir}/
export PYBUILD_TEST_ARGS := {interpreter} {build_dir}/test.py
export PYBUILD_AFTER_TEST := rm -f {build_dir}/test.py {build_dir}/README.rst
Processed: python-acora: diff for NMU version 2.2-1.3
Processing control commands: > tags 972028 + patch Bug #972028 [src:python-acora] python-acora ftbfs with python3.9 as supported python version Added tag(s) patch. > tags 972028 + pending Bug #972028 [src:python-acora] python-acora ftbfs with python3.9 as supported python version Added tag(s) pending. -- 972028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 972032
Processing commands for cont...@bugs.debian.org: > tags 972032 + pending Bug #972032 [src:setools] python-setools ftbfs with python3.9 as supported python version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 972032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972317: FTBFS on ppc64el
Package: src:llvm-toolchain-9 Version: 1:9.0.1-14 Severity: serious Tags: ftbfs Dear Maintainer, Your package FTBFS on ppc64el: https://buildd.debian.org/status/package.php?p=llvm-toolchain-9 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: > clang-9: error: unable to execute command: Segmentation fault > clang-9: error: clang frontend command failed due to signal (use -v to > see invocation) > clang version 9.0.1-14+b1 > Target: powerpc64le-unknown-linux-gnu > Thread model: posix > InstalledDir: /<>/build-llvm/tools/clang/stage2-bins/bin > clang-9: note: diagnostic msg: PLEASE submit a bug report to > https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, > and associated run script. > clang-9: note: diagnostic msg: > > > PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: > Preprocessed source(s) and associated run script(s) are located at: > clang-9: note: diagnostic msg: /tmp/testCXXCompiler-2f55c9.cpp > clang-9: note: diagnostic msg: /tmp/testCXXCompiler-2f55c9.sh > clang-9: note: diagnostic msg: > > > gmake[3]: *** [CMakeFiles/cmTC_2f83f.dir/build.make:85: > CMakeFiles/cmTC_2f83f.dir/testCXXCompiler.cxx.o] Error 254 > gmake[3]: Leaving directory > '/<>/libcxxabi/build/CMakeFiles/CMakeTmp' > gmake[2]: *** [Makefile:140: cmTC_2f83f/fast] Error 2 > gmake[2]: Leaving directory > '/<>/libcxxabi/build/CMakeFiles/CMakeTmp' > > > > > > CMake will not be able to correctly generate this project. > Call Stack (most recent call first): > CMakeLists.txt:21 (project) > > > -- Configuring incomplete, errors occurred! > See also "/<>/libcxxabi/build/CMakeFiles/CMakeOutput.log". > See also "/<>/libcxxabi/build/CMakeFiles/CMakeError.log". > make[1]: *** [debian/rules:438: debian-libcxx-build] Error 1 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:282: binary-arch] Error 2 > dpkg-buildpackage: error: debian/rules binary-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
Bug#972318: FTBFS on ppc64el
Package: src:llvm-toolchain-10 Version: 1:10.0.1-6 Severity: serious Tags: ftbfs Dear Maintainer, Your package FTBFS on ppc64el: https://buildd.debian.org/status/package.php?p=llvm-toolchain-10 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: > ar ruv libFuzzer.a Fuzzer*.o > -g -O2 -fdebug-prefix-map=/<>/build-llvm=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 > Segmentation fault > ar: `u' modifier ignored since `D' is the default (see `U') > ar: creating libFuzzer.a > ar: Fuzzer*.o: No such file or directory > make[1]: *** [debian/rules:420: debian-libfuzzer-build] Error 1 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:286: binary-arch] Error 2 > dpkg-buildpackage: error: debian/rules binary-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
Processed: pymongo: diff for NMU version 3.10.0-2.1
Processing control commands: > tags 972207 + patch Bug #972207 [src:pymongo] pymongo ftbfs with python3.9 as supported python3 version Added tag(s) patch. > tags 972207 + pending Bug #972207 [src:pymongo] pymongo ftbfs with python3.9 as supported python3 version Added tag(s) pending. -- 972207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972207: pymongo: diff for NMU version 3.10.0-2.1
Control: tags 972207 + patch
Control: tags 972207 + pending
Dear maintainer,
I've prepared an NMU for pymongo (versioned as 3.10.0-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
SR
diff -Nru pymongo-3.10.0/debian/changelog pymongo-3.10.0/debian/changelog
--- pymongo-3.10.0/debian/changelog 2020-03-28 22:06:09.0 -0700
+++ pymongo-3.10.0/debian/changelog 2020-10-15 21:59:45.0 -0700
@@ -1,3 +1,10 @@
+pymongo (3.10.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix test failure on Python 3.9 (Closes: #972207)
+
+ -- Stefano Rivera Thu, 15 Oct 2020 21:59:45 -0700
+
pymongo (3.10.0-2) unstable; urgency=medium
* debian/patches/da778c501761f9c7fa0f2f1538e5d569d67ad044.patch
diff -Nru pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch
--- pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch 1969-12-31 16:00:00.0 -0800
+++ pymongo-3.10.0/debian/patches/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch 2020-10-15 21:58:50.0 -0700
@@ -0,0 +1,37 @@
+From: Shane Harvey
+Date: Thu, 10 Sep 2020 13:39:34 -0700
+Subject: PYTHON-2262 Test Python 3.9 in Evergreen
+
+Bug-Debian: https://bugs.debian.org/972207
+Bug-Upstream: https://jira.mongodb.org/browse/PYTHON-2262
+Origin: upstream, https://github.com/mongodb/mongo-python-driver/commit/fcb6a8ecbc98fceca138d74fb09b516b172bb4e0
+---
+ setup.py | 1 +
+ test/test_custom_types.py | 2 +-
+ 2 files changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index 7c0110f..1ddec32 100755
+--- a/setup.py
b/setup.py
+@@ -385,6 +385,7 @@ setup(
+ "Programming Language :: Python :: 3.6",
+ "Programming Language :: Python :: 3.7",
+ "Programming Language :: Python :: 3.8",
++"Programming Language :: Python :: 3.9",
+ "Programming Language :: Python :: Implementation :: CPython",
+ "Programming Language :: Python :: Implementation :: PyPy",
+ "Topic :: Database"],
+diff --git a/test/test_custom_types.py b/test/test_custom_types.py
+index ba0bb0c..685a51d 100644
+--- a/test/test_custom_types.py
b/test/test_custom_types.py
+@@ -255,7 +255,7 @@ class TestBSONFallbackEncoder(unittest.TestCase):
+
+ class TestBSONTypeEnDeCodecs(unittest.TestCase):
+ def test_instantiation(self):
+-msg = "Can't instantiate abstract class .* with abstract methods .*"
++msg = "Can't instantiate abstract class"
+ def run_test(base, attrs, fail):
+ codec = type('testcodec', (base,), attrs)
+ if fail:
diff -Nru pymongo-3.10.0/debian/patches/series pymongo-3.10.0/debian/patches/series
--- pymongo-3.10.0/debian/patches/series 2020-03-28 22:06:09.0 -0700
+++ pymongo-3.10.0/debian/patches/series 2020-10-15 21:58:50.0 -0700
@@ -1 +1,2 @@
da778c501761f9c7fa0f2f1538e5d569d67ad044.patch
+fcb6a8ecbc98fceca138d74fb09b516b172bb4e0.patch
Bug#957439: marked as done (libforms: ftbfs with GCC-10)
Your message dated Fri, 16 Oct 2020 03:35:32 + with message-id and subject line Bug#957439: fixed in libforms 1.2.3-1.6 has caused the Debian Bug report #957439, regarding libforms: ftbfs 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.) -- 957439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libforms Version: 1.2.3-1.4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. 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. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libforms_1.2.3-1.4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: .libs/roundbut.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/roundbut.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/scrollbar.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/scrollbar.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/scrollbut.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/scrollbut.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/select.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/select.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/signal.o:(.bss+0x8): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/signal.o:(.bss+0x10): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/sldraw.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/sldraw.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/slider.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/slider.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/space.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/space.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/spinner.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/spinner.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/symbols.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/symbols.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/sysdep.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/sysdep.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/tabfolder.o:(.bss+0x0):
Bug#972296: phpmyadmin: missing dependency (php-twig >= 2.9)
Package: phpmyadmin Version: 4:4.9.5+dfsg1-2~bpo10+1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? I tried to install this package: apt-cache policy phpmyadmin phpmyadmin: Installed: (none) Candidate: 4:4.9.5+dfsg1-2~bpo10+1 Version table: 4:4.9.5+dfsg1-2~bpo10+1 100 100 http://deb.debian.org/debian buster-backports/main amd64 Packages Install failed with a missing dependency: apt install phpmyadmin Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: phpmyadmin : Depends: php-twig (>= 2.9) but 2.6.2-2 is to be installed E: Unable to correct problems, you have held broken packages. There is, however, a dependency to package php-twig >= 2.9. Thw freshest version of this package available in Buster doesn't satisfy this dependency: apt-cache policy php-twig php-twig: Installed: (none) Candidate: 2.6.2-2 Version table: 2.13.1-1~bpo10+1 100 100 http://deb.debian.org/debian buster-backports/main amd64 Packages 2.6.2-2 500 500 http://deb.debian.org/debian buster/main amd64 Packages Package depencies should be checked. Is it really necessary to have php-twig in version 2.9? One should think this outdated version of phpMyAdmin can work with the php-twig package included in Buster. *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages phpmyadmin depends on: ii dbconfig-common 2.0.11+deb10u1 ii debconf [debconf-2.0] 1.5.71 pn libjs-openlayers pn libjs-sphinxdoc pn php ii php-common 2:76+0~20200511.26+debian10~1.gbpc9beb6 pn php-google-recaptcha ii php-json2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php-mbstring2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php-mysql 2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 pn php-phpmyadmin-motranslator pn php-phpmyadmin-shapefile pn php-phpmyadmin-sql-parser pn php-phpseclib pn php-psr-container pn php-symfony-expression-languag pn php-twig pn php-twig-extensions ii php-xml 2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php7.4-cli [php-cli]7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-json [php-json] 7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-mbstring [php-mbstring] 7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-xml [php-xml]7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii sensible-utils 0.0.12 ii ucf 3.0038+nmu1 Versions of packages phpmyadmin recommends: ii apache2 [httpd] 2.4.46-2~20200810.12+debian10 ii php-bz2 2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php-curl2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php-gd 2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 pn php-tcpdf ii php-zip 2:7.4+76+0~20200511.26+debian10~1.gbpc9beb6 ii php7.4-bz2 [php-bz2]7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-curl [php-curl] 7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-gd [php-gd] 7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 ii php7.4-zip [php-zip]7.4.11-1+0~20201008.26+debian10~1.gbpcf3106 Versions of packages phpmyadmin suggests: ii mariadb-server-10.3 [virtual-m 1:10.3.23-0+deb10u1 pn php-bacon-qr-code pn php-gd2 pn php-pragmarx-google2fa pn php-recode pn
Processed: reopening 957439
Processing commands for cont...@bugs.debian.org:
> reopen 957439
Bug #957439 {Done: Paul Wise } [src:libforms] libforms: ftbfs
with GCC-10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libforms/1.2.3-1.5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 957439 is forwarded to https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=9806bce102d0c079c2c486b25ae6bdac3c98eecf https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=2c1
Processing commands for cont...@bugs.debian.org:
> forwarded 957439
> https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=9806bce102d0c079c2c486b25ae6bdac3c98eecf
>
> https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=2c1a9f151baf50887a517280645ec23379fb96f8
Bug #957439 {Done: Paul Wise } [src:libforms] libforms: ftbfs
with GCC-10
Changed Bug forwarded-to-address to
'https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=9806bce102d0c079c2c486b25ae6bdac3c98eecf
https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=2c1a9f151baf50887a517280645ec23379fb96f8'
from
'https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=9806bce102d0c079c2c486b25ae6bdac3c98eecf'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 957439 is forwarded to https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=9806bce102d0c079c2c486b25ae6bdac3c98eecf
Processing commands for cont...@bugs.debian.org:
> forwarded 957439
> https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=9806bce102d0c079c2c486b25ae6bdac3c98eecf
Bug #957439 {Done: Paul Wise } [src:libforms] libforms: ftbfs
with GCC-10
Changed Bug forwarded-to-address to
'https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=9806bce102d0c079c2c486b25ae6bdac3c98eecf'
from
'https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=2c1a9f151baf50887a517280645ec23379fb96f8'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#957439: marked as done (libforms: ftbfs with GCC-10)
Your message dated Fri, 16 Oct 2020 02:52:10 + with message-id and subject line Bug#957439: fixed in libforms 1.2.3-1.5 has caused the Debian Bug report #957439, regarding libforms: ftbfs 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.) -- 957439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libforms Version: 1.2.3-1.4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. 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. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libforms_1.2.3-1.4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: .libs/roundbut.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/roundbut.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/scrollbar.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/scrollbar.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/scrollbut.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/scrollbut.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/select.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/select.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/signal.o:(.bss+0x8): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/signal.o:(.bss+0x10): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/sldraw.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/sldraw.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/slider.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/slider.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/space.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/space.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/spinner.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/spinner.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/symbols.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/symbols.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/sysdep.o:(.bss+0x0): multiple definition of `fli_handled_parent'; .libs/align.o:(.bss+0x0): first defined here /usr/bin/ld: .libs/sysdep.o:(.bss+0x8): multiple definition of `fli_handled_obj'; .libs/align.o:(.bss+0x8): first defined here /usr/bin/ld: .libs/tabfolder.o:(.bss+0x0):
Bug#966968: efp: FTBFS: efp.a65:line 89: 8000:Illegal segment error
On Mon, Sep 28, 2020 at 10:58:11AM +0200, Nicolas Boulenguez wrote:
> Package: src:efp
> Followup-For: Bug #966968
>
> asm_to_a65.pl translates efp.asm (DASM format) to efp.a65 (XA65
> format). The related lines are:
> # "org FOO" ==> "*=FOO"
> s/\s*org\s+/*=/;
> and
> s/\s*SEG\.U\s+\w+/.zero/;
> s/\s*SEG\s+/./;
> They rewrite
> ; *** DATA SEGMENT
> SEG.U data
> org $
> as
> ; *** DATA SEGMENT
> .zero
> *=$
> The '.zero' line is rejected by xa65 2.3.11.
> There has probably been a change in the syntax described in
> http://www.floodgap.com/retrotech/xa/dists/xa-2.3.11.tar.gz
> /doc/fileformat.txt
Hmm, this is strange. AFAICT, the '.zero' directive should be allowed. I
did a bit more investigation, and it definitely seems like there was a
change in xa65 to add an extra check for relmode on allowing that
statement. Looking at the diff for xat.c between 2.3.8 and 2.3.11, I
see:
if(n==Kzero) {
-/* if(segment!=SEG_ABS) { */
+ if(relmode) {
segment = SEG_ZERO;
t[0]=Ksegment;
t[1]=SEG_ZERO;
*ll=2;
er=E_OKDEF;
-/* } else {
+ } else {
er=E_ILLSEGMENT;
- }*/
+ }
} else
At this point, I think the easiest fix is to just use DASM and skip this
whole translation business. I downloaded it from
https://github.com/dasm-assembler/dasm and it seemed to run with no issues
and produce an identical efp.nes file. So, maybe we should just package it
and then update the efp to use that instead... it seems to be a much more
active project lately than xa65.
--Joe
Processed: tagging 952741
Processing commands for cont...@bugs.debian.org: > tags 952741 + bullseye sid Bug #952741 [src:puma] [RFH] FTBFS: Tests sometimes get stuck and the build gets forcefully terminated Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 952741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 972232 is forwarded to https://github.com/cooperative-computing-lab/cctools/commit/984f955fcf42c0c8293296a4beb568417d0b5a60
Processing commands for cont...@bugs.debian.org: > forwarded 972232 > https://github.com/cooperative-computing-lab/cctools/commit/984f955fcf42c0c8293296a4beb568417d0b5a60 Bug #972232 [src:cctools] cctools FTBFS on i386 with glibc 2.31 Set Bug forwarded-to-address to 'https://github.com/cooperative-computing-lab/cctools/commit/984f955fcf42c0c8293296a4beb568417d0b5a60'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 972232
Processing commands for cont...@bugs.debian.org: > tags 972232 + patch fixed-upstream Bug #972232 [src:cctools] cctools FTBFS on i386 with glibc 2.31 Added tag(s) patch and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 972232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972216: nmap: New NPSL 0.92 license likely non-free
control: severity -1 normal Hi Göran, thanks for your bug report. I think that the issue is less serious than it seems at first glance (see below). At the moment, I'm inclined to update debian/copyright (which must be done anyway), close the issue, and be done with this. The alternatives would be to move NMAP to non-free or drop it from Debian altogether. Or one could try to get into discussions with the fine folks at Insecure.Com LLC on how to properly write free(ish) software licenses. I have neither the time nor the energy to do the latter. > The latest nmap is under a new license that seems to go against > DFSG § 1 (Free Redistribution) seems to be intended to go against > DFSG § 6 (No Discrimination Against Fields of Endeavor), and it > could also be argued that it goes against DFSG § 9 (License Must > Not Contaminate Other Software). While I agree that the license is problematic, this is not entirely new. Even back in version 5 there was very similar bizarre language (in main.cc) about somebody's opinions on how the well-established term "derivative work" is supposed to include merely running a program and parsing its output. Every attempt at redefining what "derivative work" means is clumsy at best, especially while referring to the GPL; however, I don't see any problems with DFSG§1 or DFSG§6. The annotations are little more than the expression of the license author's opinion. Sentences that include "The idea here is…", "To avoid any misunderstandings…", or "we consider…" are not something that a licensee can reasonably be expected to agree to in order to accept a software license. Cheers, -Hilko
Processed: Re: Bug#972216: nmap: New NPSL 0.92 license likely non-free
Processing control commands: > severity -1 normal Bug #972216 [nmap] nmap: New NPSL 0.92 license likely non-free Severity set to 'normal' from 'serious' -- 972216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972016: marked as done (py-lmdb ftbfs with python3.9)
Your message dated Thu, 15 Oct 2020 23:35:08 + with message-id and subject line Bug#972016: fixed in py-lmdb 1.0.0-1 has caused the Debian Bug report #972016, regarding py-lmdb ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:py-lmdb Version: 0.98-1 Severity: important Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 [...] dh_auto_test -O--buildsystem=pybuild I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_lmdb/build; python3.9 -m unittest discover -v lmdb (unittest.loader._FailedTest) ... ERROR == ERROR: lmdb (unittest.loader._FailedTest) -- ImportError: Failed to import test module: lmdb Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.9_lmdb/build/lmdb/__init__.py", line 42, in from lmdb.cpython import * ImportError: /<>/.pybuild/cpython3_3.9_lmdb/build/lmdb/cpython.cpython-39-x86_64-linux-gnu.so: undefined symbol: _Py_ForgetReference During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/unittest/loader.py", line 470, in _find_test_path package = self._get_module_from_name(name) File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/.pybuild/cpython3_3.9_lmdb/build/lmdb/__init__.py", line 48, in from lmdb.cffi import * File "/<>/.pybuild/cpython3_3.9_lmdb/build/lmdb/cffi.py", line 347, in import cffi ModuleNotFoundError: No module named 'cffi' -- Ran 1 test in 0.000s FAILED (errors=1) --- End Message --- --- Begin Message --- Source: py-lmdb Source-Version: 1.0.0-1 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of py-lmdb, 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. Andrej Shadura (supplier of updated py-lmdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Oct 2020 13:08:00 +0200 Source: py-lmdb Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Berkeley DB Team Changed-By: Andrej Shadura Closes: 972016 Changes: py-lmdb (1.0.0-1) unstable; urgency=medium . [ Andrej Shadura ] * New upstream release (Closes: #972016) * Update upstream contacts. . [ Federico Ceratto ] * Add CI conf. Checksums-Sha1: 3a8ad8f91b20cb0737d2fcb3ab899fe7e4b5f035 1791 py-lmdb_1.0.0-1.dsc c28cda5cb125a17a3f3263a7c4b1de0456728246 880331 py-lmdb_1.0.0.orig.tar.gz 3905c5b2248ecb3b3076e61754e084952977a03d 5264 py-lmdb_1.0.0-1.debian.tar.xz Checksums-Sha256: 8677ef1dc8956bd90e7a7eef1454d6254c1696979ac2527ab4f92a4dd4b1e3cc 1791 py-lmdb_1.0.0-1.dsc e01bc4d62679b6e8c8962f1110f910cdfbdb2d750b145f02fae8b8a9d787f2f9 880331 py-lmdb_1.0.0.orig.tar.gz b1a87077b8649ef726f4ba486e1ae4cac46a7e4a6a1466e47ef6ae30c7e5e0dc 5264 py-lmdb_1.0.0-1.debian.tar.xz Files: d320d899a4b53afddead55b661d31dc8 1791 python optional py-lmdb_1.0.0-1.dsc e78c8c818c7e9e73c59e49aec4561375 880331 python optional py-lmdb_1.0.0.orig.tar.gz 6eb4d79d9e0de4a712be305d832d651a 5264 python optional py-lmdb_1.0.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl+IMP4ACgkQXkCM2RzY OdIaCgf+OdUuiS1LnFhBc70KbkfXoWW6/V7k0ErJPK8frn9KB4a1Ty52lEg+2+yq 21E2B+ZdxeobaWrIQPsNk0FXhR66PfHc5NLEjKsmI2vVDnGl0Sx34UuHb7BQrx1s /bjv9dVO9Wks8bQiMSo33e9Kvj/YiX71+2YUfbWCvps9sIE1+qi9ADrNeqlN7qEC ZoBN56Vevl6cqQBEjn6Z90Vl95yd24PWaacgMC8Q74JQAkmATlVDrNXTiSLjMXTY k5I/8ZUjwGHkI5Vj0Qd8/i5z8nFEfm7FYwcYY4Fr9JtXLcENPlTKiFPgMRMx6urW IAmo0mot+fKBeFvYW72MotSatXy0nA== =Q+gn -END PGP SIGNATURE End Message ---
Bug#957979: marked as done (xfce4-cpufreq-plugin: ftbfs with GCC-10)
Your message dated Thu, 15 Oct 2020 22:58:01 + with message-id and subject line Bug#957979: fixed in xfce4-cpufreq-plugin 1.2.2-1 has caused the Debian Bug report #957979, regarding xfce4-cpufreq-plugin: ftbfs 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.) -- 957979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xfce4-cpufreq-plugin Version: 1.2.1-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. 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. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/xfce4-cpufreq-plugin_1.2.1-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking whether to build with debugging support... minimum checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating panel-plugin/Makefile config.status: creating icons/Makefile config.status: creating icons/16x16/Makefile config.status: creating icons/22x22/Makefile config.status: creating icons/48x48/Makefile config.status: creating po/Makefile.in config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands dh_auto_build make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in panel-plugin make[3]: Entering directory '/<>/panel-plugin' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -pthread -I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/xfce4 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/xfce4/libxfce4ui-2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_ 64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/xfce4 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libcpufreq_la-xfce4-cpufreq-plugin.lo `test -f 'xfce4-cpufreq-plugin.c' || echo './'`xfce4-cpufreq-plugin.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -pthread -I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0
Processed: Re: Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
Processing control commands: > tag -1 confirmed Bug #972241 [src:libguestfs] FTBFS on amd64 and i386 (error: guestfs_launch failed) Added tag(s) confirmed. > tag -1 pending Bug #972241 [src:libguestfs] FTBFS on amd64 and i386 (error: guestfs_launch failed) Added tag(s) pending. -- 972241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
control: tag -1 confirmed control: tag -1 pending * Stéphane Glondu: > 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). Yes, This is unrelated to the OCaml update. I had noticed the build failure. I'm working to fix the issue properly and prepare a patch for upstream. Cheers, -Hilko
Processed: tagging 972016
Processing commands for cont...@bugs.debian.org: > tags 972016 + pending Bug #972016 [src:py-lmdb] py-lmdb ftbfs with python3.9 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 972016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972291: python-py2bit: Mistake in the Architecture: field
Source: python-py2bit Version: 0.3.0-5 Severity: serious Control: block 969757 by -1 python-py2bit (0.3.0-5) unstable; urgency=medium ... * Restrict architectures to those where build time test is passing Closes: #969757 ... The list of "build time test is passing" architectures are exactly the little endian architectures. A serious problem is that any-ppc64 should be replaced with ppc64el. any-ppc64 includes ppc64 (big endian, FTBFS), but it does not include ppc64el (little endian, release architecture, tests passed before). A minor issue is that m68k should be removed from Architecture, it is big endian and expected to be broken but built with nocheck.
Processed: python-py2bit: Mistake in the Architecture: field
Processing control commands:
> block 969757 by -1
Bug #969757 {Done: Andreas Tille } [src:python-py2bit]
src:python-py2bit: fails to migrate to testing for too long: FTBFS on s390x
969757 was not blocked by any bugs.
969757 was not blocking any bugs.
Added blocking bug(s) of 969757: 972291
--
969757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969757
972291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#901382: marked as done (node-katex: must build binary packages fonts-katex and libjs-katex)
Your message dated Thu, 15 Oct 2020 22:00:23 +
with message-id
and subject line Bug#901382: fixed in node-katex 0.10.2+dfsg-1
has caused the Debian Bug report #901382,
regarding node-katex: must build binary packages fonts-katex and libjs-katex
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.)
--
901382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-katex
Version: 0.8.3+dfsg-1
Severity: serious
Justification: Policy 11.8.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Binary package node-katex includes fonts and browser-optimized Javascript code.
The former must instead be packaged as binary package fonts-katex,
and the latter should instead be packaged as libjs-katex.
- Jonas
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlsfnYwACgkQLHwxRsGg
ASEfug//fe0w61RWi35dsyGtaBRNH0vX0Y/zjSSZFfQ6rNRYACjRcP0sq6PuZ7zj
3rzEfXN/Au1q2TjTPWwrQ06Mc8KX1ieCkK9uuaaQosWy+0pn0EqzKD19XPhTkBc9
CVuyOg43g1eGCD3Z/XktAD7EHcijTGjwtutaFBXbNOVGUHlWAxe0zgpLZxlEl9gu
W+LZAUfaCzXjwEtedww4J8DC3HZUdMCDk/gTnV1up9knZ78WvNImih+c4G75fPTk
VG5le7CLl6SyofvxjR+d6YcTjIaTrArEd6kLqZjk5h8DuZ6BNDYPdMzOVmXgRMPB
X7GGxjQ5T8a3vUtRxOpMm6m50Ug/Kcb+xWz3/f15g8Hp2P8ZkYQI5OgL+RpKUE7X
/MFyRdTz8t/2J1+BC4/CFV28LS/5Kt0Xy/Jrpr9jA9j5Qq5FpQGEoUpjtwo4H8PW
doMI/da6ogYAtUPt81DwCu69vLA46zqpJRzMfqGTahSKb2QZXA2FEcpHWbOHNEp8
idMMwGCUi9+9CSJY7iN1Ez6k/0ahMz93amBs8KBMASbLVVC4mZQR/as1n93gtus4
auOj739hpEBQ0bjvekBR7KsSHBgrh7rW9jCxFg3k7tOIQpLiIOBVwv1zvyyYDjIf
X4D0nx6+o/gFGUmIjxecPRYPZVnh6bfCcj2gVd9qZAbj6FFhEVM=
=YqwT
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-katex
Source-Version: 0.10.2+dfsg-1
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
node-katex, 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 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated node-katex package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 20 May 2020 17:30:55 +0530
Source: node-katex
Binary: fonts-katex katex libjs-katex
Architecture: source all
Version: 0.10.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Pirate Praveen
Description:
fonts-katex - Fast math typesetting for the web (fonts)
katex - Fast math typesetting for the web
libjs-katex - Fast math typesetting for the web (for browsers)
Closes: 901382 945556 961005
Changes:
node-katex (0.10.2+dfsg-1) unstable; urgency=medium
.
* New upstream version 0.9.0
* Build using webpack
* Bump debhelper compat to 11
* Add node-mini-css-extract-plugin as build dependency (still in NEW)
* Add node-babel-loader as build dependency
* Use /usr/share/nodejs for resolve options in webpack.config
* Skip cssnano by skipping minimize option
* Embed components: babel-plugin-version-inline
* New upstream version 0.10.2+dfsg (Closes: #961005)
* Use pkg-js-tools for component auto linking to node_modules
* Build babel-plugin-version-inline with babel 7
* Add node-css-loader as build dependency
* Add katex-fonts as a component and symlink to submodules directory
* Remove dist/contrib from orig source and clean
* Run rollup during build (Closes: #945556)
* Skip less-loader and use lessc command
* Fix katex command link and use pkg-js-tools auto install
* Add libjs-katex binary package
* Don't install any components in binary package
(add empty debian/nodejs/submodules file)
* Add fonts-katex binary package (Closes: #901382)
* Rename node-katex to katex and add Provides: node-katex
* Replace copy of fonts in libjs-katex with symbolic link to fonts-katex
* Replace duplicate copy of dist with symbolic link to libjs-katex
* Use salsa.debian.org in Vcs-* fields
* Use Breaks instead of conflicts
* Add Section: fonts for fonts-katex
* Add ${misc:Depends} to libjs-katex and fonts-katex
* Add deversion mangle for component katex-fonts
* Add comment to patch
Checksums-Sha1:
Processed: affects 971118
Processing commands for cont...@bugs.debian.org: > affects 971118 src:breezy Bug #971118 [src:dulwich] ERROR: test_send_remove_branch (dulwich.tests.compat.test_client.DulwichTCPClientTest) Added indication that 971118 affects src:breezy > thanks Stopping processing here. Please contact me if you need assistance. -- 971118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972185: libre0: stack smashing detected in v1.1.0
Hello Kevin, I don't know the details, but I guess there will no automatic rebuild of baresip triggered on migration. As far as I see [1], the only users of libre0 are baresip and librem0, so I guess both might need a rebuild. Maybe someone with more shared library packaging knowledge might give some pointers what steps need to be taken now? Kind regards, Bernhard [1] `apt-cache rdepends libre0` in an unstable VM.
Bug#971972: marked as done (vde-switch,vde-wirefilter,vdeplug: Miissing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1")
Your message dated Thu, 15 Oct 2020 20:45:21 + with message-id and subject line Bug#971972: fixed in vde2 2.3.2+r586-7 has caused the Debian Bug report #971972, regarding vde-switch,vde-wirefilter,vdeplug: Miissing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1" 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.) -- 971972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vde-switch,vde-wirefilter,vdeplug Version: 2.3.2+r586-5 Severity: serious Upgrading vde2 from 2.3.2+r586-2.2+b1 to 2.3.2+r586-5 fails for me as follows: Selecting previously unselected package vde-switch. Preparing to unpack .../44-vde-switch_2.3.2+r586-5_amd64.deb ... Unpacking vde-switch (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/44-vde-switch_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/vde_switch', which is also in package vde2 2.3.2+r586-2.2+b1 Selecting previously unselected package vde-wirefilter. Preparing to unpack .../45-vde-wirefilter_2.3.2+r586-5_amd64.deb ... Unpacking vde-wirefilter (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/45-vde-wirefilter_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/wirefilter', which is also in package vde2 2.3.2+r586-2.2+b1 Selecting previously unselected package vdeplug. Preparing to unpack .../46-vdeplug_2.3.2+r586-5_amd64.deb ... Unpacking vdeplug (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/46-vdeplug_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/dpipe', which is also in package vde2 2.3.2+r586-2.2+b1 Preparing to unpack .../47-vde2_2.3.2+r586-5_amd64.deb ... Unpacking vde2 (2.3.2+r586-5) over (2.3.2+r586-2.2+b1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-leAAf0/44-vde-switch_2.3.2+r586-5_amd64.deb /tmp/apt-dpkg-install-leAAf0/45-vde-wirefilter_2.3.2+r586-5_amd64.deb /tmp/apt-dpkg-install-leAAf0/46-vdeplug_2.3.2+r586-5_amd64.deb Looks as if the required Breaks and Replaces headers against the older versions of vde2 are missing in all three new packages. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: vde2 Source-Version: 2.3.2+r586-7 Done: Andrea Capriotti We believe that the bug you reported is fixed in the latest version of vde2, 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. Andrea Capriotti (supplier of updated vde2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Oct 2020 22:08:26 +0200 Source: vde2 Architecture: source Version: 2.3.2+r586-7 Distribution: unstable Urgency: medium Maintainer: Debian VSquare Team Changed-By: Andrea Capriotti Closes: 971972 Changes: vde2 (2.3.2+r586-7) unstable; urgency=medium . * d/control: Fix Breaks and Replaces again (Closes: #971972) Checksums-Sha1: c0d31bcfb4480e5c4e8db2cf6112c8d301f44faa 2479 vde2_2.3.2+r586-7.dsc 2e60718c1a2a826a9178379add52151983e3fa0e 16907 vde2_2.3.2+r586-7.diff.gz 457748255399f9c2e17a04c009c1881c338f5c22 6002 vde2_2.3.2+r586-7_source.buildinfo Checksums-Sha256: ab5d8b9ac86ad6e86883eaa648e5bf51807a83805f30d688e40a0adf77f01f6a 2479 vde2_2.3.2+r586-7.dsc 6c5e5abcde8b6d22f78b80e32c566f832131139d3064b3f42c98408a334f3d71 16907 vde2_2.3.2+r586-7.diff.gz 944eba0a10cada4d6ac992c5f4e13d5b18862e4f64dfd4c0b09447cce0aeeb0e 6002 vde2_2.3.2+r586-7_source.buildinfo Files: 910490eec7f9fc797b2dc8c6f1e26ddd
Bug#972288: openjdk-11 FTBFS with gcc-10
Source: openjdk-11 Version: 11.0.8+10-1.1 Severity: serious Tags: ftbfs openjdk-11 fails to build from source due to gcc-10 defaulting to -fno-commons. https://tests.reproducible-builds.org/debian/rbuild/bullseye/amd64/openjdk-11_11.0.8+10-1.1.rbuild.log.gz | /usr/bin/ld: /build/openjdk-11-11.0.8+10/build/support/native/java.base/libjava/childproc.o:./make/./src/java.base/unix/native/libjava/childproc.h:121: multiple definition of `parentPathv'; /build/openjdk-11-11.0.8+10/build/support/native/java.base/libjava/ProcessImpl_md.o:./make/./src/java.base/unix/native/libjava/childproc.h:121: first defined here http://crossqa.debian.net/build/openjdk-11_11.0.8+10-1_armel_20200930210757.log | ( /bin/rm -f /<>/build/buildjdk/support/native/java.base/libjava/BUILD_LIBJAVA_link.log && /usr/bin/x86_64-linux-gnu-gcc -Wl,--hash-style=both -Wl,-z,defs -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -Wl,-O1 -L/<>/build/buildjdk/support/modules_libs/java.base -L/<>/build/buildjdk/support/modules_libs/java.base/server -shared -Wl,--exclude-libs,ALL -Wl,-z,origin -Wl,-rpath,\$ORIGIN -Wl,-soname=libjava.so -o /<>/build/buildjdk/support/modules_libs/java.base/libjava.so @/<>/build/buildjdk/support/native/java.base/libjava/_BUILD_LIBJAVA_objectfilenames.txt /<>/build/buildjdk/support/native/java.base/libfdlibm.a -ljvm -lverify -ldl > >(/usr/bin/tee -a /<>/build/buildjdk/support/native/java.base/libjava/BUILD_LIBJAVA_link.log) 2> >(/usr/bin/tee -a /<>/build/buildjdk/support/native/java.base/libjava/BUILD_LIBJAVA_link.log >&2) || ( exitcode=$? && /bin/cp /<>/build/buildjdk/support/native/java.base/libjava/BUILD_LIBJAVA_link.log /<>/build/make-support/failure-logs/buildjdk_support_native_java.base_libjava_BUILD_LIBJAVA_link.log && /bin/cp /<>/build/buildjdk/support/native/java.base/libjava/BUILD_LIBJAVA_link.cmdline /<>/build/make-support/failure-logs/buildjdk_support_native_java.base_libjava_BUILD_LIBJAVA_link.cmdline && exit $exitcode ) ) ; | /usr/bin/ld: /<>/build/buildjdk/support/native/java.base/libjava/childproc.o:/<>/src/java.base/unix/native/libjava/childproc.h:121: multiple definition of `parentPathv'; /<>/build/buildjdk/support/native/java.base/libjava/ProcessImpl_md.o:/<>/src/java.base/unix/native/libjava/childproc.h:121: first defined here | collect2: error: ld returned 1 exit status | gmake[5]: *** [CoreLibraries.gmk:101: /<>/build/buildjdk/support/modules_libs/java.base/libjava.so] Error 1 Helmut
Bug#972285: Needs porting to PostgreSQL 13
Package: postgresql-12-python3-multicorn Version: 1.4.0-2 Severity: serious Multicorn needs to be ported to PostgreSQL 13, but unfortunately upstream isn't ready yet: https://github.com/Segfault-Inc/Multicorn/issues/261 https://github.com/Segfault-Inc/Multicorn/pull/260 This bug is to keep Multicorn out of testing until this has been resolved. (See also #972255.) Christoph
Processed: severity of 972281 is normal
Processing commands for cont...@bugs.debian.org: > severity 972281 normal Bug #972281 [linux-source-5.8] linux-source-5.8: Fails to compile with no LKMs if no Module.symvers Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 972281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972281: linux-source-5.8: Fails to compile with no LKMs if no Module.symvers
Package: linux-source-5.8 Version: 5.8.10-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) When compiling a static kernel (i.e. with no LKMs), which I have done many times before, deb-pkg fails after the compiling has finished unless the file Module.symvers is present in the source directory. It does not matter if the file is empty, which it will be if no modules are being used. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.8.10-20201015 (SMP w/2 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-source-5.8 depends on: ii binutils 2.35.1-1 ii xz-utils 5.2.4-1+b1 Versions of packages linux-source-5.8 recommends: ii bc1.07.1-2+b2 ii bison 2:3.7.2+dfsg-1 ii flex 2.6.4-8 ii gcc 4:10.2.0-1 ii libc6-dev [libc-dev] 2.31-3 pn linux-config-5.8 ii make 4.3-4 Versions of packages linux-source-5.8 suggests: ii libncurses-dev [ncurses-dev] 6.2+20200918-1 pn pkg-config pn qtbase5-dev -- no debconf information
Bug#971831: marked as done (autopkg test depends on unavailable package adequate)
Your message dated Thu, 15 Oct 2020 19:21:00 + with message-id and subject line Bug#971831: fixed in task 2.5.1+dfsg-11 has caused the Debian Bug report #971831, regarding autopkg test depends on unavailable package adequate 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.) -- 971831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:task Version: 2.5.1+dfsg-10 Severity: serious Tags: sid bullseye autopkg test depends on unavailable package adequate, which was removed from testing. [...] Package adequate is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'adequate' has no installation candidate adequate-taskwarrior FAIL badpkg blame: task --- End Message --- --- Begin Message --- Source: task Source-Version: 2.5.1+dfsg-11 Done: Gordon Ball We believe that the bug you reported is fixed in the latest version of task, 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. Gordon Ball (supplier of updated task 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 18:07:46 + Source: task Architecture: source Version: 2.5.1+dfsg-11 Distribution: unstable Urgency: medium Maintainer: Debian Tasktools Packaging Team Changed-By: Gordon Ball Closes: 971831 Changes: task (2.5.1+dfsg-11) unstable; urgency=medium . * Drop autopkgtest using (rc-buggy) adequate (Closes: #971831) Checksums-Sha1: 5d1c17f59472482686b6d887dbd4ea3182c69ca6 2110 task_2.5.1+dfsg-11.dsc 5ccdc2906bc54207f02e4c9d3501b5cda3dad9f3 38384 task_2.5.1+dfsg-11.debian.tar.xz a50ef91e0ae524b63ea5ef578562bf8ff56632eb 6943 task_2.5.1+dfsg-11_source.buildinfo Checksums-Sha256: aa2a3037d84c2fe3d300b205ba2e58c8a753c0dca2f008be23ee3295490c3f65 2110 task_2.5.1+dfsg-11.dsc 1e5fd4359fe771a979b07b239c3b4762f7c3e6da933ac16386ce6e1b4b279b5a 38384 task_2.5.1+dfsg-11.debian.tar.xz 000e75a0e8d0f224a085c969b253671b7113a8f9b65e907dcf13745f5435c352 6943 task_2.5.1+dfsg-11_source.buildinfo Files: 5a1cfb0a419e07ae194954a3262766ac 2110 utils optional task_2.5.1+dfsg-11.dsc 6b204fa6e7c86ca340580dfd933faef4 38384 utils optional task_2.5.1+dfsg-11.debian.tar.xz da42eb38f0f1ca6e347cf3836996ecc9 6943 utils optional task_2.5.1+dfsg-11_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl+Im34ACgkQo12v+60p 6N4khQ/+PEta2uMbc+MvWf1CG0pAE89s8fZCF+cHRXslAjI4FCFVmd3TIDJOfFoK 0Xz/lI5ND7VncvVIcxXnpDuesdmKBFp818JDIhJz8JLeXcxSywyTEalnzkBRydj3 c6sgkH8BNX03WptrgqsE7SSakes90eIRDGlFLrUfBVWaFHG+xn9DovLDVUMCxPro 5NjgbQql8raDYmP7s213VxIAKpuJUcoBnx97I5duSi5kDDLXPjDUZhtw3Uf47p1R LUgHhlImskiKKXlFCtA0jlWBnRft8EXBRBTDxHQVcBRKEO60E1Az4+TcPzTaeRQY gc9cGZxMr3z5KqKvTeD3UdV0l33P+6wZxqtZISP0ZDBHV7bzZroi68LTMP6Rtt7r SqDPeUznSDXZNhFpgYFGC/ALr1WBe8vM/z/nMwnqXpKpDKz9VLYHZcOrnCbhiMoJ p8C4PrMDeAY4EhyY1lgBLdDW5jQ4R8SjU+096Nj4ukw9lzczDpqcCc3rP1ZZGUha 9zkZi/hTUlkm47hCRVm851dmJfFXvjDzSZcp5tI571Rcr+sM1H64Y9eS8Ul7kR15 Ba0JnaLPTlX5siKHtO1WDQZIc+s629WISwXEFptbD19cexH7Q6wgLVnypAzMbECE gjyQ3KiY7CrFEhXte7yh78Kx7rfUM/ncgQFPHLJMPUzPYgS3zPk= =CX6T -END PGP SIGNATURE End Message ---
Processed: tagging 972251
Processing commands for cont...@bugs.debian.org: > tags 972251 + ftbfs Bug #972251 [src:python-line-profiler] python-line-profile ftbfs in unstable Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: transition: qtbase-opensource-src
Processing control commands: > block -1 by 957436 972154 972155 972156 972157 972158 972160 972175 972176 > 972177 972178 972179 Bug #972278 [release.debian.org] transition: qtbase-opensource-src 972278 was not blocked by any bugs. 972278 was not blocking any bugs. Added blocking bug(s) of 972278: 972176, 972178, 972157, 972154, 972155, 972175, 972177, 972179, 972158, 972156, 957436, and 972160 -- 972278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#935115: passing variable assignments to functions (was Re: Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX)
looks like it has been fixed, i can't reproduce in either unstable, testing or stable by the moment of now.
Processed: severity of 958476 is serious
Processing commands for cont...@bugs.debian.org: > severity 958476 serious Bug #958476 [python3-gevent] python3-gevent: gevent 1.4 not compatible with python 3.8 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 958476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972277: sensors-applet: Install the gnome-panel module in multi-arch location
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
Processed: [bts-link] source package src:nipy
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:nipy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #959138 (http://bugs.debian.org/959138) > # Bug title: numpy breaks nipy autopkgtest: No module named > 'numpy.testing.decorators' > # * https://github.com/nipy/nipy/issues/456 > # * remote status changed: open -> closed > # * closed upstream > tags 959138 + fixed-upstream Bug #959138 [src:nipy] numpy breaks nipy autopkgtest: No module named 'numpy.testing.decorators' Added tag(s) fixed-upstream. > usertags 959138 - status-open Usertags were: status-open. Usertags are now: . > usertags 959138 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 959138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972271: marked as done (cvxopt: binary-all FTBFS)
Your message dated Thu, 15 Oct 2020 17:48:48 + with message-id and subject line Bug#972271: fixed in cvxopt 1.2.5+dfsg-3 has caused the Debian Bug report #972271, regarding cvxopt: binary-all FTBFS 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.) -- 972271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cvxopt Version: 1.2.5+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=cvxopt=all=1.2.5%2Bdfsg-2=1602771489=0 ... dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_cvxopt/build; python3.9 -m unittest discover -v -s tests test_basic (test_basic.TestBasic) ... ERROR test_basic_complex (test_basic.TestBasic) ... ERROR test_basic_no_gsl (test_basic.TestBasic) ... ERROR test_cvxopt_init (test_basic.TestBasic) ... ERROR test_print (test_basic.TestBasic) ... ERROR test_custom_kkt (unittest.loader._FailedTest) ... ERROR test_options (test_dsdp.TestDSDP) ... skipped 'DSDP not available' test_sdp (test_dsdp.TestDSDP) ... skipped 'DSDP not available' test_ch10_acent2 (test_examples.TestExamples) ... ERROR test_ch10_l2ac (test_examples.TestExamples) ... ERROR test_ch10_lp (test_examples.TestExamples) ... ERROR test_ch8_conelp (test_examples.TestExamples) ... ERROR test_ch8_coneqp (test_examples.TestExamples) ... ERROR test_ch8_l1 (test_examples.TestExamples) ... ERROR test_ch8_l1regls (test_examples.TestExamples) ... ERROR test_ch8_lp (test_examples.TestExamples) ... ERROR test_ch8_mcsdp (test_examples.TestExamples) ... ERROR test_ch8_sdp (test_examples.TestExamples) ... ERROR test_ch8_socp (test_examples.TestExamples) ... ERROR test_ch9_acent (test_examples.TestExamples) ... ERROR test_ch9_acent2 (test_examples.TestExamples) ... ERROR test_ch9_gp (test_examples.TestExamples) ... ERROR test_ch9_l2ac (test_examples.TestExamples) ... ERROR test_ilp (test_glpk.TestGLPK) ... skipped 'GLPK not available' test_lp (test_glpk.TestGLPK) ... skipped 'GLPK not available' test_options (test_glpk.TestGLPK) ... skipped 'GLPK not available' test1 (test_gsl.TestGSL) ... skipped 'GSL not available' test2 (test_gsl.TestGSL) ... skipped 'GSL not available' test3 (test_gsl.TestGSL) ... skipped 'GSL not available' test_modeling (unittest.loader._FailedTest) ... ERROR test_conelp (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' test_lp (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' test_options (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' test_socp (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' == ERROR: test_basic (test_basic.TestBasic) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.9_cvxopt/build/tests/test_basic.py", line 19, in test_basic import cvxopt ModuleNotFoundError: No module named 'cvxopt' ... --- End Message --- --- Begin Message --- Source: cvxopt Source-Version: 1.2.5+dfsg-3 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of cvxopt, 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. Graham Inggs (supplier of updated cvxopt 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 17:29:19 + Source: cvxopt Architecture: source Version: 1.2.5+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Graham Inggs Closes: 972271 Changes: cvxopt (1.2.5+dfsg-3) unstable; urgency=medium . * Team upload * Do not try to run tests during arch:all build (Closes: #972271) Checksums-Sha1: 38cd69e004cc1cdff1f1a27dea3ef5e7e4d04268 2383 cvxopt_1.2.5+dfsg-3.dsc 2cb3ddc041e3841aa7617f5e67e266328233cb06 6972 cvxopt_1.2.5+dfsg-3.debian.tar.xz Checksums-Sha256: aed468c390359a346aee9f46e85b25d8a8610827fbef2d38323327feadd9e703 2383 cvxopt_1.2.5+dfsg-3.dsc 9dde77b45ebcffbaa7561801d6eb83c84550685c42c83ddae406e0141ecf7508 6972
Bug#972194: marked as done (pyside2 is not ready for python3.9)
Your message dated Thu, 15 Oct 2020 17:33:51 +
with message-id
and subject line Bug#972194: fixed in pyside2 5.15.0-4
has caused the Debian Bug report #972194,
regarding pyside2 is not ready for python3.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
972194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyside2
Version: 5.15.0-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
pyside2 is not ready for python3.9:
[...]
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from pyside2-5.15.0/debian/source/options:
--extend-diff-ignore=^[^/]*[.]egg-info/
debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.9 setup.py clean
Unsupported python version detected. Only these python versions are supported:
[(2, 7), (3, 5), (3, 6), (3, 7), (3, 8)]
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
python3.9 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.9 3.8" returned
exit code 13
make: *** [debian/rules:30: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: pyside2
Source-Version: 5.15.0-4
Done: Dmitry Shachnev
We believe that the bug you reported is fixed in the latest version of
pyside2, 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 pyside2 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:06:52 +0300
Source: pyside2
Architecture: source
Version: 5.15.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Closes: 972194
Changes:
pyside2 (5.15.0-4) unstable; urgency=medium
.
* Team upload.
* Drop preload-libglx-mesa.patch, not needed with glibc ≥ 2.31-1.
* Backport upstream patch to add support for Python 3.9 (closes: #972194).
Checksums-Sha1:
7ea89a1240b565ad3b12a1e8b3ef0c71cd04ad79 7272 pyside2_5.15.0-4.dsc
03968af105cd04ff24e248b5b53e4602949391b7 53764 pyside2_5.15.0-4.debian.tar.xz
dce2ccbbed2f940328fca109e597044404802366 8388 pyside2_5.15.0-4_source.buildinfo
Checksums-Sha256:
8320ec782ca945eb5668b0093edc73c0724baee811428f1fa37ba1eb1d9bf5d6 7272
pyside2_5.15.0-4.dsc
108f873b842e540d2ae10e264ba0620515f2b07ca8bfe03c3a88a616760cc337 53764
pyside2_5.15.0-4.debian.tar.xz
70538e9235f3700ae205668e5ee5d84b6ed4a81209f8009960566d758ec1b3e7 8388
pyside2_5.15.0-4_source.buildinfo
Files:
db5c32c9207fe2317f0a4d693dd64851 7272 python optional pyside2_5.15.0-4.dsc
4a494a2dee517131f8f28c0296e22699 53764 python optional
pyside2_5.15.0-4.debian.tar.xz
5367fbb422644702e365635d9e30056b 8388 python optional
pyside2_5.15.0-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl+Ign4THG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy6FcD/9OYGPbV6yp4GpNcuGVtYfX4uJLvBeU
JEKy9esEa7RPgsBjkBreHJSLxw/uLpLLEXAN+yQIvcTsHB0KpA/5bl1PtmZALnXq
egRmPzTWQez/ruHNyuN+6CelivXDa+23j7tx5Jmn2rcrJoyyLsLZaz3klV88Gf4H
efVP/qtKT+8OZPg9mvlVp6mYKTH3bkb23yDu2pddF7U88umiZn9Uml3ir0qrOvt7
gRJVTzraanFec5lqLtfLalkzM6C1EwaK0ZkdjfPUv/HnQSvgKclrkjsNQLKQa8Dp
3opnbjD+n4oTYQ3IEodkHJ2hJdKaej4UGTZjAquWdBLP8wW/Tu8fvUIkVFeVH/Zj
iGxBYXwtYRTfRwZMZPMxuIdbMIHNU1LrNNllQgbOlypXDPGd9lGDd0YYdHtlBZwy
MgSGtOqh9UukZPjggvsjJhxcDz318GYPVHkmDYqteR6aF531Gm8w6hzCConT0WGN
7RvFntYWKjnawcZ7OdEYRXzchLQE5qfjVFKCN9TZCDUJL5TcuUItuyNQ9ESSdoSF
b7HOQe+CUgOrwjEM2BstINe5qmezy271kQ+HCgCuyZZU2tX3jt+GluB6rGi3xjOy
lpEL+5MsEOz3TT/MF+eODvhOn/9e5l/llcgILQPJ4tMvaLZAhLVLlqPX4cdbWO1d
ZlubBfw7eZHyKA==
=3GCl
-END PGP SIGNATURE End Message ---
Bug#972185: marked as done (libre0: stack smashing detected in v1.1.0)
Your message dated Thu, 15 Oct 2020 13:19:37 -0400 with message-id and subject line Re: Bug#972185: libre0: stack smashing detected in v1.1.0 has caused the Debian Bug report #972185, regarding libre0: stack smashing detected in v1.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libre0 Version: 1.1.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, I went ahead and installed version 1.1.0-1 from unstable to go ahead and test the fix for #971980. --- kjotte@daedalus:~$ baresip baresip v1.0.0 Copyright (C) 2010 - 2020 Alfred E. Heggestad et al. Local network address: IPv6=enp0s25|2606:a000:a442:9800:efae:2f59:1855:7d4f ... baresip is ready. > 142 ua: using best effort AF: af=AF_INET6 call: connecting to 'sip:1...@pbx-int.home.nivex.net'.. *** stack smashing detected ***: terminated Aborted (core dumped) --- Not sure if this is a problem in the libre0 build or if baresip needs to be rebuilt against the new library version. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US, LC_CTYPE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libre0 depends on: ii libc6 2.31-3 ii libssl1.1 1.1.1g-1 ii zlib1g 1:1.2.11.dfsg-2 libre0 recommends no packages. libre0 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- OK, I'm going to go ahead and close this report out so libre0 can migrate to testing. I'll wait a few days after that to see if a report needs to be raised against baresip. On 10/15/20 12:50 PM, Bernhard Übelacker wrote: > Hello Kevin, > I don't know the details, but I guess there will no automatic > rebuild of baresip triggered on migration. > As far as I see [1], the only users of libre0 are > baresip and librem0, so I guess both might need a rebuild. > Maybe someone with more shared library packaging knowledge > might give some pointers what steps need to be taken now? > > Kind regards, > Bernhard > > [1] `apt-cache rdepends libre0` in an unstable VM. > --- End Message ---
Bug#971936: marked as done (blist ftbfs with python3-defaults (python3.9) from experimental)
Your message dated Thu, 15 Oct 2020 17:18:45 +
with message-id
and subject line Bug#971936: fixed in blist 1.3.6-7
has caused the Debian Bug report #971936,
regarding blist ftbfs with python3-defaults (python3.9) from experimental
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.)
--
971936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:blist
Version: 1.3.6-6
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
[...]
creating build/temp.linux-x86_64-3.9
creating build/temp.linux-x86_64-3.9/blist
x86_64-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 -DBLIST_FLOAT_RADIX_SORT=1 -I/usr/include/python3.9
-c blist/_blist.c -o build/temp.linux-x86_64-3.9/blist/_blist.o
blist/_blist.c: In function ‘unwrap_leaf_array’:
blist/_blist.c:4583:37: warning: implicit declaration of function
‘_PyObject_GC_IS_TRACKED’ [-Wimplicit-function-declaration]
4583 | if (leafs_n > 1 && !_PyObject_GC_IS_TRACKED(leafs[i]))
| ^~~
blist/_blist.c: In function ‘sort_ulong’:
blist/_blist.c:5387:31: warning: comparison of integer expressions of different
signedness: ‘Py_ssize_t’ {aka ‘long int’} and ‘long unsigned int’
[-Wsign-compare]
5387 | for (j = 0; j < NUM_PASSES; j++) {
| ^
blist/_blist.c:5393:31: warning: comparison of integer expressions of different
signedness: ‘Py_ssize_t’ {aka ‘long int’} and ‘long unsigned int’
[-Wsign-compare]
5393 | for (j = 0; j < NUM_PASSES; j++) {
| ^
blist/_blist.c:5403:23: warning: comparison of integer expressions of different
signedness: ‘Py_ssize_t’ {aka ‘long int’} and ‘long unsigned int’
[-Wsign-compare]
5403 | for (j = 0; j < NUM_PASSES; j++) {
| ^
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions
-Wl,-z,relro -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.9/blist/_blist.o -o
/<>/.pybuild/cpython3_3.9_blist/build/blist/_blist.cpython-39-x86_64-linux-gnu.so
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.8_blist/build/blist
copying blist/_sorteddict.py ->
/<>/.pybuild/cpython3_3.8_blist/build/blist
copying blist/_btuple.py ->
/<>/.pybuild/cpython3_3.8_blist/build/blist
copying blist/_sortedlist.py ->
/<>/.pybuild/cpython3_3.8_blist/build/blist
copying blist/__init__.py ->
/<>/.pybuild/cpython3_3.8_blist/build/blist
running build_ext
building 'blist._blist' extension
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/blist
x86_64-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 -DBLIST_FLOAT_RADIX_SORT=1 -I/usr/include/python3.8
-c blist/_blist.c -o build/temp.linux-x86_64-3.8/blist/_blist.o
blist/_blist.c: In function ‘sort_ulong’:
blist/_blist.c:5387:31: warning: comparison of integer expressions of different
signedness: ‘Py_ssize_t’ {aka ‘long int’} and ‘long unsigned int’
[-Wsign-compare]
5387 | for (j = 0; j < NUM_PASSES; j++) {
| ^
blist/_blist.c:5393:31: warning: comparison of integer expressions of different
signedness: ‘Py_ssize_t’ {aka ‘long int’} and ‘long unsigned int’
[-Wsign-compare]
5393 | for (j = 0; j < NUM_PASSES; j++) {
| ^
blist/_blist.c:5403:23: warning: comparison of integer expressions of different
signedness: ‘Py_ssize_t’ {aka ‘long int’} and ‘long unsigned int’
[-Wsign-compare]
5403 | for (j = 0; j < NUM_PASSES; j++) {
| ^
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions
-Wl,-z,relro -g
Processed: [bts-link] source package mruby
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package mruby > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #972051 (http://bugs.debian.org/972051) > # Bug title: CVE-2020-15866 > # * https://github.com/mruby/mruby/issues/5042 > # * remote status changed: (?) -> closed > # * closed upstream > tags 972051 + fixed-upstream Bug #972051 [mruby] CVE-2020-15866 Added tag(s) fixed-upstream. > usertags 972051 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 972051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#971936 marked as pending in blist
Processing control commands: > tag -1 pending Bug #971936 [src:blist] blist ftbfs with python3-defaults (python3.9) from experimental Added tag(s) pending. -- 971936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971936: marked as pending in blist
Control: tag -1 pending Hello, Bug #971936 in blist reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/blist/-/commit/2c10bfaf3fb034489bdb56e67932a01458319bbb Patch to support Python 3.9's hiding of internal GC API (Closes: #971936). (this message was generated automatically) -- Greetings https://bugs.debian.org/971936
Bug#972027: marked as done (pycxx needs a sourceful upload to support python3.9)
Your message dated Thu, 15 Oct 2020 16:49:05 + with message-id and subject line Bug#972027: fixed in pycxx 7.1.4-0.1 has caused the Debian Bug report #972027, regarding pycxx needs a sourceful upload to support python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pycxx Version: 7.1.3-0.2 Severity: important Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 pycxx needs a sourceful upload to support python3.9, to let packages like pysvn build: [...] Info: Configure for python 3.9.0 in exec_prefix /usr Debian lib directory %s /usr/lib/x86_64-linux-gnu Error: Cannot find PyCXX include CXX/Version.hxx - use --pycxx-dir make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' --- End Message --- --- Begin Message --- Source: pycxx Source-Version: 7.1.4-0.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of pycxx, 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. Matthias Klose (supplier of updated pycxx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Oct 2020 18:21:17 +0200 Source: pycxx Architecture: source Version: 7.1.4-0.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Matthias Klose Closes: 972027 Changes: pycxx (7.1.4-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream version, supporting Python 3.9. Closes: #972027. Checksums-Sha1: 378c919548cabe1da30a641bb5e51efa70f7975a 2108 pycxx_7.1.4-0.1.dsc c2ab70d53ef1a871fe1541bb280b9819c949d097 152376 pycxx_7.1.4.orig.tar.gz 691bd9435d271e3c2617568dcbebc85327ac59b8 8400 pycxx_7.1.4-0.1.debian.tar.xz d9c5eab5dd269978f2bf92d9105a4f050e95293f 6668 pycxx_7.1.4-0.1_source.buildinfo Checksums-Sha256: af936bae0947ad6457e683f53b12167ff4d0b08ab07e3283a84d5982b6fe2b5a 2108 pycxx_7.1.4-0.1.dsc 314314fbfaac9bdd9610d605c5f8d0b12b91f3f9c4fdab181bc1e021b6806b3d 152376 pycxx_7.1.4.orig.tar.gz dfa07193401ecada1dc88502ea910b7d7e2b9118ef612a0f966d2024bc4d810d 8400 pycxx_7.1.4-0.1.debian.tar.xz 039b9f2d12a8e84a956b6949962d57ea312f339a77a0fe72a5598bb63673f518 6668 pycxx_7.1.4-0.1_source.buildinfo Files: c00d22049be1a77c2c4566a96d20944e 2108 python optional pycxx_7.1.4-0.1.dsc 009f8a7e1977c31879daed380f2a638c 152376 python optional pycxx_7.1.4.orig.tar.gz 1438c2c97a1141d0248f09c250ca67a7 8400 python optional pycxx_7.1.4-0.1.debian.tar.xz 2b6909b593e7e9be9b2e05de2d351e65 6668 python optional pycxx_7.1.4-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl+HJb0QHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9e/qD/9W7BnhxtlPS6gnLQSW6a25+ExAqXkhM11N zt/o7Dob3qlJOG5EuLSuRZJB/qcl2fDYPCZ7hC9cFRBAUdHgW/pmFn9EJp8StwkI ml3oBofH5z7tqe6P9ENapspgeMGEgY9pIZEWsMoRbpSBft+j2bTwTMAALULoJxoQ VnwgjA2tpqNKLSXCKMU3LROWti0LFR9VtZjV+s9GGnU2+ctq73POYNhntJ6BOvJh ikw4rCyeyhIgJH5hdI826OanwagadeucoOqqZNCzH0TG1NDRg78iXo7Z3UopQm5K LIAQsvuIKQC/UanBpEfz+WKCw8avwmD8ZrNYlbY5aaqQSdjmyc7EWO/Z0RncNDY+ f6ZzPSIPas0C0Wt+DgUF1bNH3wek36WIwQe39D2UmAWHSh2xZPH9n8eMDeJiPXRY I7klT6MbHVXwj7M93R9vNYB5m9esxBr0cigxBrFYW1iOzO0sKgLK4/9RFxoKm/5k mJ5UZE7T87E4nsnmBZHAlVF08C7Idq0+O1aljB7OgFp2ybRJcvIHTGTmaZ30zkg1 ftAcb3Do9YhUNqiQ6Ey1LlFmpvnPWb0LTO6Iy4J8mZdBcZPfrBL0BB70AQCTD+iS m4MBt94/98wDXolWUov5hnMAAPUFQfg1CvSnyY9o1pXgtcqjXEfBWfB4Q11fZoM3 t1thCFY7Dw== =6dFZ -END PGP SIGNATURE End Message ---
Bug#951824: marked as done (stimfit needs a source only upload.)
Your message dated Thu, 15 Oct 2020 19:05:01 +0300 with message-id <20201015160501.GA18181@localhost> and subject line Re: Bug#951824: stimfit needs a source only upload. has caused the Debian Bug report #951824, regarding stimfit needs a source only upload. 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.) -- 951824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: stimfit Version: 0.16.0-1 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing. Please make a source-only upload so your package can migrate (and preferablly fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948020 at the same time). --- End Message --- --- Begin Message --- On Sat, Feb 22, 2020 at 06:03:55AM +, peter green wrote: > Package: stimfit > Version: 0.16.0-1 > Severity: serious > > The release team have decreed that non-buildd binaries can no longer migrate > to testing. Please make a source-only upload so your package can migrate (and > preferablly fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948020 at > the same time). This was fixed by a binNMU, which works as long as no binary-all packages were uploaded. cu Adrian--- End Message ---
Bug#971995: marked as done (python-greenlet ftbfs with python3-defaults (python3.9) from experimental)
Your message dated Thu, 15 Oct 2020 16:04:25 + with message-id and subject line Bug#972025: fixed in python-greenlet 0.4.17-1 has caused the Debian Bug report #972025, regarding python-greenlet ftbfs with python3-defaults (python3.9) from experimental 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.) -- 972025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-greenlet Version: 0.4.15-4.2 Severity: important Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 Python 3.9 doesn't define _Py_DEC_REFTOTAL anymore [0] A patch for upstream already was merged [1]. Please, consider new upstream release. [0] https://github.com/python/cpython/commit/49932fec62c616ec88da52642339d83ae719e924 [1] https://github.com/python-greenlet/greenlet/pull/161/files - Part of build: [...] building 'greenlet' extension creating build creating build/temp.linux-x86_64-3.9 x86_64-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 -I/usr/include/python3.9 -c greenlet.c -o build/temp.linux-x86_64-3.9/greenlet.o greenlet.c: In function ‘g_initialstub’: greenlet.c:823:4: warning: ‘PyEval_CallObjectWithKeywords’ is deprecated [-Wdeprecated-declarations] 823 |result = PyEval_CallObjectWithKeywords( |^~ In file included from /usr/include/python3.9/Python.h:145, from greenlet.h:8, from greenlet.c:5: /usr/include/python3.9/ceval.h:17:43: note: declared here 17 | Py_DEPRECATED(3.9) PyAPI_FUNC(PyObject *) PyEval_CallObjectWithKeywords( | ^ greenlet.c: In function ‘green_dealloc’: greenlet.c:1046:4: error: ‘_Py_DEC_REFTOTAL’ undeclared (first use in this function); did you mean ‘_Py_DECREF’? 1046 |_Py_DEC_REFTOTAL; |^~~~ |_Py_DECREF greenlet.c:1046:4: note: each undeclared identifier is reported only once for each function it appears in error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 make[1]: *** [debian/rules:24: build-python3.9] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2020-10-11T09:31:29Z 0xFA9DEC5DE11C63F1.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-greenlet Source-Version: 0.4.17-1 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of python-greenlet, 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. Laszlo Boszormenyi (GCS) (supplier of updated python-greenlet 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 07:11:38 +0200 Source: python-greenlet Architecture: source Version: 0.4.17-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 972025 Changes: python-greenlet (0.4.17-1) unstable; urgency=medium . [ Matthias Klose ] * New upstream version. - Python 3.9 compatibility. Closes: #972025. * Bump standards version. Checksums-Sha1: db4b952301149f68bcce8759b3c5a07ae2a32547 2091 python-greenlet_0.4.17-1.dsc 33973b9d5d012803d116fbc0e62fccf845a2327e 59443 python-greenlet_0.4.17.orig.tar.gz a69af8df484252eb5c506b4901f0221c73b11067 6664 python-greenlet_0.4.17-1.debian.tar.xz Checksums-Sha256: 0a64a8f8ef2918ac1eacfc0c297969887398fdccc354301de02ae0e03465a2c6 2091 python-greenlet_0.4.17-1.dsc c63c8258eef589a86c266a05385b1ed105cf2a7fc48f47c89bb0c1de48d90c00 59443 python-greenlet_0.4.17.orig.tar.gz
Bug#972025: marked as done (python-greenlet ftbfs with python3.9 as supported python version)
Your message dated Thu, 15 Oct 2020 16:04:25 + with message-id and subject line Bug#972025: fixed in python-greenlet 0.4.17-1 has caused the Debian Bug report #972025, regarding python-greenlet ftbfs with python3.9 as supported python 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.) -- 972025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-greenlet Version: 0.4.15-4.2 Severity: important Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 python3.9 setup.py build running build running build_ext building 'greenlet' extension creating build creating build/temp.linux-x86_64-3.9 x86_64-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 -I/usr/include/python3.9 -c greenlet.c -o build/temp.linux-x86_64-3.9/greenlet.o greenlet.c: In function ‘g_initialstub’: greenlet.c:823:4: warning: ‘PyEval_CallObjectWithKeywords’ is deprecated [-Wdeprecated-declarations] 823 |result = PyEval_CallObjectWithKeywords( |^~ In file included from /usr/include/python3.9/Python.h:145, from greenlet.h:8, from greenlet.c:5: /usr/include/python3.9/ceval.h:17:43: note: declared here 17 | Py_DEPRECATED(3.9) PyAPI_FUNC(PyObject *) PyEval_CallObjectWithKeywords( | ^ greenlet.c: In function ‘green_dealloc’: greenlet.c:1046:4: error: ‘_Py_DEC_REFTOTAL’ undeclared (first use in this function); did you mean ‘_Py_DECREF’? 1046 |_Py_DEC_REFTOTAL; |^~~~ |_Py_DECREF greenlet.c:1046:4: note: each undeclared identifier is reported only once for each function it appears in error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 --- End Message --- --- Begin Message --- Source: python-greenlet Source-Version: 0.4.17-1 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of python-greenlet, 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. Laszlo Boszormenyi (GCS) (supplier of updated python-greenlet 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 07:11:38 +0200 Source: python-greenlet Architecture: source Version: 0.4.17-1 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 972025 Changes: python-greenlet (0.4.17-1) unstable; urgency=medium . [ Matthias Klose ] * New upstream version. - Python 3.9 compatibility. Closes: #972025. * Bump standards version. Checksums-Sha1: db4b952301149f68bcce8759b3c5a07ae2a32547 2091 python-greenlet_0.4.17-1.dsc 33973b9d5d012803d116fbc0e62fccf845a2327e 59443 python-greenlet_0.4.17.orig.tar.gz a69af8df484252eb5c506b4901f0221c73b11067 6664 python-greenlet_0.4.17-1.debian.tar.xz Checksums-Sha256: 0a64a8f8ef2918ac1eacfc0c297969887398fdccc354301de02ae0e03465a2c6 2091 python-greenlet_0.4.17-1.dsc c63c8258eef589a86c266a05385b1ed105cf2a7fc48f47c89bb0c1de48d90c00 59443 python-greenlet_0.4.17.orig.tar.gz 7358cd37aef8701267a3b3b5bdb972a142347908c64b69d9d8dbf9149f0a1d61 6664 python-greenlet_0.4.17-1.debian.tar.xz Files: 2ebf032b2104634d9648ee944d3a0aa5 2091 python optional python-greenlet_0.4.17-1.dsc aa1d640f831770f13dc3d0ac0aeefb33 59443 python optional python-greenlet_0.4.17.orig.tar.gz f0cf24158d8f1d6d597f8b9bbffc0ec3 6664 python optional python-greenlet_0.4.17-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl+H26YACgkQ3OMQ54ZM yL/6RA/9HKnW8VVcN87B8oiKKcmeJ4kX+qfuOo6EqaUamnt7GD3HUndQpT98hje6 qU71aY6An6O4mdKHrZ/qbbk0alCTJUTv9xVELk7/TaNzm8V5rgoMFlMERSstiYZs A6XHpWJZ3jQDGMcUie5w+OLa+5LxcxKJTIPL9iK8MARN4xeBvx+zdFAoOmCDasPI
Processed: severity of 948020 is normal
Processing commands for cont...@bugs.debian.org: > severity 948020 normal Bug #948020 [src:stimfit] stimfit: b-d on python3-all-dev, but not built for all supported Python3 versions Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 948020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 951888 972023
Processing commands for cont...@bugs.debian.org: > forcemerge 951888 972023 Bug #951888 [src:python-enable] python-enable FTBFS with swig 4.0.1 Bug #951888 [src:python-enable] python-enable FTBFS with swig 4.0.1 Added tag(s) sid and bullseye. Bug #972023 [src:python-enable] python-enable ftbfs with python3.9 as supported python3 version Set Bug forwarded-to-address to 'https://github.com/enthought/enable/issues/360'. Added tag(s) ftbfs. Merged 951888 972023 > thanks Stopping processing here. Please contact me if you need assistance. -- 951888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951888 972023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#972271: cvxopt: binary-all FTBFS
Processing control commands: > tags -1 + pending Bug #972271 [src:cvxopt] cvxopt: binary-all FTBFS Added tag(s) pending. -- 972271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972271: cvxopt: binary-all FTBFS
Control: tags -1 + pending On Thu, 15 Oct 2020 at 17:30, Adrian Bunk wrote: > Source: cvxopt > Version: 1.2.5+dfsg-2 > Severity: serious > Tags: ftbfs Thanks. Fixed in git. [1] https://salsa.debian.org/science-team/cvxopt/-/commit/deac8299bfd81247ee36762734fd18b944d4a5fd
Bug#970230: closed by Debian FTP Masters (reply to Timo Aaltonen ) (Bug#970230: fixed in freeipa 4.8.10-1)
Control: reopen -1 On Mon, Sep 28, 2020 at 10:36:05AM +, Debian Bug Tracking System wrote: >... > freeipa (4.8.10-1) unstable; urgency=medium >... >* control: Build freeipa-client-epn only where nodejs is available. > (Closes: #970230) >... Unfortunately this was not sufficient to fix the build: https://buildd.debian.org/status/package.php?p=freeipa=sid cu Adrian
Processed: Re: Bug#970230 closed by Debian FTP Masters (reply to Timo Aaltonen ) (Bug#970230: fixed in freeipa 4.8.10-1)
Processing control commands:
> reopen -1
Bug #970230 {Done: Timo Aaltonen } [src:freeipa] freeipa
FTBFS on non-nodejs architectures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions freeipa/4.8.10-1.
--
970230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#972272: liquidsoap FTBFS on bytecode architectures
Source: liquidsoap Version: 1.4.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=liquidsoap=sid ... dh_missing -a dh_missing: warning: usr/lib/ocaml/liquidsoap/META exists in debian/tmp but is not installed to anywhere (related file: "src/META") dh_missing: error: missing files, aborting While detecting missing files, dh_missing noted some files with a similar name to those that were missing. This error /might/ be resolved by replacing references to the missing files with the similarly named ones that dh_missing found - assuming the content is identical. As an example, you might want to replace: * src/META with: * usr/lib/ocaml/liquidsoap/META in a file in debian/ or as argument to one of the dh_* tools called from debian/rules. (Note it is possible the paths are not used verbatim but instead directories containing or globs matching them are used instead) Alternatively, add the missing file to debian/not-installed if it cannot and should not be used. The following debhelper tools have reported what they installed (with files per package) * dh_elpa: liquidsoap (0), liquidsoap-mode (0) * dh_install: liquidsoap (6), liquidsoap-mode (1) * dh_installdocs: liquidsoap (2), liquidsoap-mode (0) * dh_installexamples: liquidsoap (6), liquidsoap-mode (0) * dh_installman: liquidsoap (1), liquidsoap-mode (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:14: binary-arch] Error 25
Bug#972271: cvxopt: binary-all FTBFS
Source: cvxopt Version: 1.2.5+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=cvxopt=all=1.2.5%2Bdfsg-2=1602771489=0 ... dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_cvxopt/build; python3.9 -m unittest discover -v -s tests test_basic (test_basic.TestBasic) ... ERROR test_basic_complex (test_basic.TestBasic) ... ERROR test_basic_no_gsl (test_basic.TestBasic) ... ERROR test_cvxopt_init (test_basic.TestBasic) ... ERROR test_print (test_basic.TestBasic) ... ERROR test_custom_kkt (unittest.loader._FailedTest) ... ERROR test_options (test_dsdp.TestDSDP) ... skipped 'DSDP not available' test_sdp (test_dsdp.TestDSDP) ... skipped 'DSDP not available' test_ch10_acent2 (test_examples.TestExamples) ... ERROR test_ch10_l2ac (test_examples.TestExamples) ... ERROR test_ch10_lp (test_examples.TestExamples) ... ERROR test_ch8_conelp (test_examples.TestExamples) ... ERROR test_ch8_coneqp (test_examples.TestExamples) ... ERROR test_ch8_l1 (test_examples.TestExamples) ... ERROR test_ch8_l1regls (test_examples.TestExamples) ... ERROR test_ch8_lp (test_examples.TestExamples) ... ERROR test_ch8_mcsdp (test_examples.TestExamples) ... ERROR test_ch8_sdp (test_examples.TestExamples) ... ERROR test_ch8_socp (test_examples.TestExamples) ... ERROR test_ch9_acent (test_examples.TestExamples) ... ERROR test_ch9_acent2 (test_examples.TestExamples) ... ERROR test_ch9_gp (test_examples.TestExamples) ... ERROR test_ch9_l2ac (test_examples.TestExamples) ... ERROR test_ilp (test_glpk.TestGLPK) ... skipped 'GLPK not available' test_lp (test_glpk.TestGLPK) ... skipped 'GLPK not available' test_options (test_glpk.TestGLPK) ... skipped 'GLPK not available' test1 (test_gsl.TestGSL) ... skipped 'GSL not available' test2 (test_gsl.TestGSL) ... skipped 'GSL not available' test3 (test_gsl.TestGSL) ... skipped 'GSL not available' test_modeling (unittest.loader._FailedTest) ... ERROR test_conelp (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' test_lp (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' test_options (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' test_socp (test_mosek.TestMOSEK) ... skipped 'MOSEK not available' == ERROR: test_basic (test_basic.TestBasic) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.9_cvxopt/build/tests/test_basic.py", line 19, in test_basic import cvxopt ModuleNotFoundError: No module named 'cvxopt' ...
Bug#972249: marked as done (unrardll needs a sourceful upload for python3.9)
Your message dated Thu, 15 Oct 2020 15:22:52 + with message-id and subject line Bug#972249: fixed in unrardll 0.1.4-1 has caused the Debian Bug report #972249, regarding unrardll needs a sourceful upload for python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:unrardll Version: 0.1.3-6 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 unrardll needs a sourceful upload for python3.9, packages in contrib are not built by the buildds. --- End Message --- --- Begin Message --- Source: unrardll Source-Version: 0.1.4-1 Done: Norbert Preining We believe that the bug you reported is fixed in the latest version of unrardll, 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. Norbert Preining (supplier of updated unrardll 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 23:31:27 +0900 Source: unrardll Binary: python3-unrardll python3-unrardll-dbgsym Architecture: source amd64 Version: 0.1.4-1 Distribution: unstable Urgency: medium Maintainer: Norbert Preining Changed-By: Norbert Preining Description: python3-unrardll - Python wrapper for the unrar shared library Closes: 972249 Changes: unrardll (0.1.4-1) unstable; urgency=medium . [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from old 10 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Add debian/watch file, using pypi. . [ Norbert Preining ] * Add signing key. * New upstream version 0.1.4. (Closes: #972249) * Remove patches included upstream. Checksums-Sha1: c53e2d43d6d2f9415543e268f36fd855aed73d5b 1849 unrardll_0.1.4-1.dsc 3c42b00f80e7048fc0d491ebc23c5550f5cf6ef9 10773780 unrardll_0.1.4.orig.tar.gz 80b02a2c6055d2ca2f2316b3770456f9253b02dd 833 unrardll_0.1.4.orig.tar.gz.asc 12d5fd44d7b99f1e92ff48d0d3eee75b1c5d1bce 4944 unrardll_0.1.4-1.debian.tar.xz 5de3ec10dbd122aafd394c92cb056d1b7205a5bb 40716 python3-unrardll-dbgsym_0.1.4-1_amd64.deb 53aa88cb8510ca7fbe732159723a959215b2b582 13476 python3-unrardll_0.1.4-1_amd64.deb 7f3f40c3857fb442a4347819649274918377b7c6 7468 unrardll_0.1.4-1_amd64.buildinfo Checksums-Sha256: b586970ffedc7b8d73daa0e16bf28a5bdaf71c29c9aa432817a4eca0b8122c31 1849 unrardll_0.1.4-1.dsc 4149c0729cf96a0bae80360e7d94dc40af1088c8da7f6eb8d10e09b8632e92ad 10773780 unrardll_0.1.4.orig.tar.gz 1cfdd3a631bddd51f9dbdfc30370704472245ade8e0929b9438296202ca39c39 833 unrardll_0.1.4.orig.tar.gz.asc 013a81b72ab2e38c9c027301569426131256088be1750d8e0e8cad6699567436 4944 unrardll_0.1.4-1.debian.tar.xz 7e48d9bebc063c68c93b3ea4a3b44f1060987fe361b71232e3d76fe2bef6a8f4 40716 python3-unrardll-dbgsym_0.1.4-1_amd64.deb 94550271a607e6c6b195d40942d50e10163c3540f1c7804154c13b938a04361b 13476 python3-unrardll_0.1.4-1_amd64.deb 1b1edbf5179699e1c303e315cea4a016df57a203a697166048924037f36aa8c6 7468 unrardll_0.1.4-1_amd64.buildinfo Files: 99dda54d0306d9c39cfd74cf50238536 1849 contrib/python optional unrardll_0.1.4-1.dsc dc6530958768230e1512c895c092c1b9 10773780 contrib/python optional unrardll_0.1.4.orig.tar.gz 52e4905c34a5a6f15e897a91669dc1b8 833 contrib/python optional unrardll_0.1.4.orig.tar.gz.asc 8635f40c3a545cf40ae7e56570361f4e 4944 contrib/python optional unrardll_0.1.4-1.debian.tar.xz 220fec637bf528eee128ef1136e99f87 40716 contrib/debug optional python3-unrardll-dbgsym_0.1.4-1_amd64.deb eb4f76c3494e211ba05cf9ca43d9a0ac 13476 contrib/python optional python3-unrardll_0.1.4-1_amd64.deb cd6abfeb9b0192eda750d03b51ccee54 7468 contrib/python optional unrardll_0.1.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl+IX3MACgkQ2A4JsIcU AGav9QgAve6ssPIPkoL4VwiuZ5+WN/ByUw2pxkV2/L7YZJyThggQKp2ZVoD95iyH kmnn0cR4DRdeMaGt42mAzygOjjPshIukVT8EZixKBnwaUCn+tw2izQj+3Hj/UsCJ
Bug#972266: marked as done (seqtools: flaky armhf autopkgtest on ci.debian.net: Error: signal 11:)
Your message dated Thu, 15 Oct 2020 14:54:32 + with message-id and subject line Bug#972266: fixed in seqtools 4.44.1+dfsg-6 has caused the Debian Bug report #972266, regarding seqtools: flaky armhf autopkgtest on ci.debian.net: Error: signal 11: 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.) -- 972266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seqtools Version: 4.44.1+dfsg-5 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The autopkgtest of seqtools turned up a couple of times on our list of regressions. I looked into the history of your autopkgtest and it fails regularly on armhf [1]. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. I copied the output at the bottom of this report. It seems the exact error (at least the message) changed between the early failures and latter failures. Please do get in touch if we need to dive into this together. Paul [1] https://ci.debian.net/user/britney/jobs?package=seqtools=migration-reference%2F0%5B%5D=unstable%5B%5D=testing%5B%5D=armhf https://ci.debian.net/data/autopkgtest/testing/armhf/s/seqtools/7473607/log.gz == Test 4 Detected sequence types: DNA vs. Protein Karlin/Altschul statistics for these sequences and score matrix: K = 0.128 Lambda = 0.299 => Expected MSP score in a 100x100 matrix = 23.934 Expected residue score in MSP = 1.362 => Expected MSP length = 18 Karlin/Altschul statistics for these sequences and score matrix: K = 0.131 Lambda = 0.306 => Expected MSP score in a 100x100 matrix = 23.493 Expected residue score in MSP = 1.363 => Expected MSP length = 17 Karlin/Altschul statistics for these sequences and score matrix: K = 0.129 Lambda = 0.300 => Expected MSP score in a 100x100 matrix = 23.861 Expected residue score in MSP = 1.388 => Expected MSP length = 17 4700 vs. 570 residues => 8.04 million dots. Exporting graphical image to 'test4'. Error: signal 11: Cannot print backtrace signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: seqtools Source-Version: 4.44.1+dfsg-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of seqtools, 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. Andreas Tille (supplier of updated seqtools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Oct 2020 16:10:33 +0200 Source: seqtools Architecture: source Version: 4.44.1+dfsg-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 972266 Changes: seqtools (4.44.1+dfsg-6) unstable; urgency=medium . * Ignore one flaky test on armhf Closes: #972266 Checksums-Sha1: 0f1c57771d58a0da2e6f95c79fac1ca4a7e4fc0c 2348 seqtools_4.44.1+dfsg-6.dsc eb862426d01233e337bdddb75d0c27cb9850e906 15420 seqtools_4.44.1+dfsg-6.debian.tar.xz 95e7cde0e24837b6b37225bd100a88bafdba292a 13540 seqtools_4.44.1+dfsg-6_amd64.buildinfo Checksums-Sha256: d0da1def96157f8cd62be79b69805ab3b43dd6b24512acadf4e20c3b97269cd5 2348 seqtools_4.44.1+dfsg-6.dsc 9b5cb7451c4fbf4204f4fc2d7fd9b299f23e20714439df13cf75c48950d114e9 15420 seqtools_4.44.1+dfsg-6.debian.tar.xz 5488f5c3d1e2175a0cd0549810efd3d5aaabcf877ca2c628379760b0dd92da3a 13540 seqtools_4.44.1+dfsg-6_amd64.buildinfo Files: a97e94a92865b0425069e82620dc1a8e 2348 science optional seqtools_4.44.1+dfsg-6.dsc 3c35ebe4e33c77e3866d43621ffe9248 15420 science optional seqtools_4.44.1+dfsg-6.debian.tar.xz a301e358a580a2a0c2d924ef856ac516 13540 science optional seqtools_4.44.1+dfsg-6_amd64.buildinfo
Bug#972267: gudhi: binary-all FTBFS
Source: gudhi Version: 3.3.0+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gudhi=3.3.0%2Bdfsg-2 ... for py3ver in 3.9 3.8 ; do \ dh_auto_install --buildsystem=cmake --no-parallel --builddirectory=build-py$py3ver/userversion ; \ done cd build-py3.9/userversion && make -j1 install DESTDIR=/<>/gudhi-3.3.0\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>/build-py3.9/userversion' /usr/bin/cmake -S/<> -B/<>/build-py3.9/userversion --check-build-system CMakeFiles/Makefile.cmake 0 make -f CMakeFiles/Makefile2 preinstall make[3]: Entering directory '/<>/build-py3.9/userversion' make[3]: Nothing to be done for 'preinstall'. make[3]: Leaving directory '/<>/build-py3.9/userversion' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "None" CMake Error at src/GudhUI/cmake_install.cmake:52 (file): file INSTALL cannot find "/<>/build-py3.9/userversion/src/GudhUI/GudhUI": No such file or directory. Call Stack (most recent call first): cmake_install.cmake:64 (include) make[2]: *** [Makefile:108: install] Error 1 ...
Processed: Re: elixir: cannot be installed without Erlang from unstable
Processing control commands: > tags -1 + patch Bug #939324 [elixir-lang] elixir: cannot be installed without Erlang from unstable Added tag(s) patch. > severity -1 grave Bug #939324 [elixir-lang] elixir: cannot be installed without Erlang from unstable Severity set to 'grave' from 'normal' -- 939324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961076: NXNS Attack (CVE-2020-12667)
El 14/10/20 a las 10:12, Andrew Savchenko escribió: > Dear Maintainers, > > Is there still a plan to backport a fix for CVE-2020-12667 into Buster? > > Looking at the changelog [1], there is nothing that indicates it is already > fixed. > > [1] > https://metadata.ftp-master.debian.org/changelogs//main/k/knot-resolver/knot-resolver_3.2.1-3_changelog Hi, It is up to the security-team (in CC) to accept or not the proposed backport. Cheers, -- Santiago signature.asc Description: PGP signature
Bug#972266: seqtools: flaky armhf autopkgtest on ci.debian.net: Error: signal 11:
Source: seqtools Version: 4.44.1+dfsg-5 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The autopkgtest of seqtools turned up a couple of times on our list of regressions. I looked into the history of your autopkgtest and it fails regularly on armhf [1]. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. I copied the output at the bottom of this report. It seems the exact error (at least the message) changed between the early failures and latter failures. Please do get in touch if we need to dive into this together. Paul [1] https://ci.debian.net/user/britney/jobs?package=seqtools=migration-reference%2F0%5B%5D=unstable%5B%5D=testing%5B%5D=armhf https://ci.debian.net/data/autopkgtest/testing/armhf/s/seqtools/7473607/log.gz == Test 4 Detected sequence types: DNA vs. Protein Karlin/Altschul statistics for these sequences and score matrix: K = 0.128 Lambda = 0.299 => Expected MSP score in a 100x100 matrix = 23.934 Expected residue score in MSP = 1.362 => Expected MSP length = 18 Karlin/Altschul statistics for these sequences and score matrix: K = 0.131 Lambda = 0.306 => Expected MSP score in a 100x100 matrix = 23.493 Expected residue score in MSP = 1.363 => Expected MSP length = 17 Karlin/Altschul statistics for these sequences and score matrix: K = 0.129 Lambda = 0.300 => Expected MSP score in a 100x100 matrix = 23.861 Expected residue score in MSP = 1.388 => Expected MSP length = 17 4700 vs. 570 residues => 8.04 million dots. Exporting graphical image to 'test4'. Error: signal 11: Cannot print backtrace signature.asc Description: OpenPGP digital signature
Bug#972247: marked as done (Probes fail with error: ‘struct mm_struct’ has no member named mmap_sem)
Your message dated Thu, 15 Oct 2020 13:36:53 +
with message-id
and subject line Bug#972247: fixed in systemtap 4.3-3
has caused the Debian Bug report #972247,
regarding Probes fail with error: ‘struct mm_struct’ has no member named
mmap_sem
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.)
--
972247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemtap
Version: 4.3-2
Severity: grave
With linux-image-5.8.0-3-amd64 version 5.8.14-1, stap fails as follows:
$ sudo stap -e 'probe oneshot { println("hello world") }'
[...]
/usr/share/systemtap/runtime/linux/access_process_vm.h: In function
‘__access_process_vm_’:
/usr/share/systemtap/runtime/linux/access_process_vm.h:32:19: error: ‘struct
mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
32 | down_read (>mmap_sem);
| ^~~~
| mmap_base
/usr/share/systemtap/runtime/linux/access_process_vm.h:87:17: error: ‘struct
mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
87 | up_read (>mmap_sem);
| ^~~~
| mmap_base
This upstream commit should fix the issue:
https://sourceware.org/git/?p=systemtap.git;a=commit;h=37066e2c3a9d9f48fc01b13ec0493b1c67551275
--- End Message ---
--- Begin Message ---
Source: systemtap
Source-Version: 4.3-3
Done: Emanuele Rocca
We believe that the bug you reported is fixed in the latest version of
systemtap, 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.
Emanuele Rocca (supplier of updated systemtap package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 15 Oct 2020 11:06:19 +0200
Source: systemtap
Architecture: source
Version: 4.3-3
Distribution: unstable
Urgency: high
Maintainer: Emanuele Rocca
Changed-By: Emanuele Rocca
Closes: 961830 969968 972247
Changes:
systemtap (4.3-3) unstable; urgency=high
.
* Add debian/patches/mmap_sem-transition.patch to fix stap error: ‘struct
mm_struct’ has no member named ‘mmap_sem’. (Closes: #972247)
* Add debian/patches/vermagic-hiding.patch to fix stap error: 'This header
can be included from kernel/module.c or *.mod.c only'
* Set architecture of binary packages to linux-any. (Closes: #969968)
* Add FORCE_SOURCE_DATE to debian/rules. (Closes: #961830)
* Use salsa-ci-team/pipeline/raw/master/recipes/debian.yml instead of
salsa-ci-team/pipeline/raw/master/salsa-ci.yml in our own salsa-ci.yml
configuration to fix CI pipeline error: undefined dependency:
extract-source.
Checksums-Sha1:
94e5c7657420aa826318d330208e7675521b9f02 3010 systemtap_4.3-3.dsc
2068415290a2a759e1f57a4bd54d604e2c5a53d9 31612 systemtap_4.3-3.debian.tar.xz
d77a522e334b89a9ba3b28575fa31adcc4d785bd 12176 systemtap_4.3-3_amd64.buildinfo
Checksums-Sha256:
c24ee69fecb6b6fe3fe5a526ca09213d1ff76718303fcc50e3c29974f19f5e19 3010
systemtap_4.3-3.dsc
cb768fe0dc61e44d5c76a6e6069952b3037915f4a6ffbb82aa2a729ef40ab34f 31612
systemtap_4.3-3.debian.tar.xz
50ede593cf2399ce1f06158dee39c331312128875f6d72655ebe8100639278ee 12176
systemtap_4.3-3_amd64.buildinfo
Files:
2a69030d66618359adc6b1924e434cab 3010 devel optional systemtap_4.3-3.dsc
7949de3d38dd5f0ac240d00e005cde34 31612 devel optional
systemtap_4.3-3.debian.tar.xz
297be8eb548aa11397e190a115e12884 12176 devel optional
systemtap_4.3-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAl+ITNoACgkQ1QhaB1D9
t6NMwg//YzYvXUuHi5Aq6G+EMV8tmiebq2JpAPmVG+QeAJe2U4+xVeXY0dKzvfx/
YB6/ixpl6OcCfE9Zxini18vp9WvH7ZCqYJ9xiEZRkE2i+KSb6ld/PoRGAQQesXcN
n8MK3V5/eJ46DgmzQU+1OMJZ6txgNW6ji8afhri7L/3+7ufyeINynbevfVqatO9F
Mzlx5K1XMw9mA6MVfTHIpUV87zlTEdG7x4V2WxsOVVe/EYqb+zlUeEslpUaX48G5
WBxbpWrq/qCOPvFVEGJiOsjZDluvGEdWF/S8xaidqXGVoSiwTrBe+Ot3EHnVXsIC
5jJoBLDHA48zHscViMZcjdbzR9q7ZpKO/7/wTiTc65dibXHetkhsBdYeGcD7FN6m
GbfXN+UU5FZ8B4MSKAN6wCslCSWjovLwBuwAEKOzhAg6M7H6czTT9lZybFAxB8M4
z6WVxeNXwInrqM0BgjQlhMe2/pmr5DPcqBpJ4JIw/FDhH8+nfU/gMOelUHa1rs+R
Bug#963655: marked as done (python-apt: FTBFS with Sphinx 3.1: Invalid C declaration: Expected end of definition. [error at 10] pkgAcquire::Item)
Your message dated Thu, 15 Oct 2020 12:49:22 + with message-id and subject line Bug#963655: fixed in python-apt 2.1.4 has caused the Debian Bug report #963655, regarding python-apt: FTBFS with Sphinx 3.1: Invalid C declaration: Expected end of definition. [error at 10] pkgAcquire::Item 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.) -- 963655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-apt Version: 2.1.3 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx3.1 Hi, python-apt fails to build with Sphinx 3.1, currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_apt/build/apt > copying apt/cache.py -> /<>/.pybuild/cpython3_3.8_apt/build/apt > copying apt/__init__.py -> > /<>/.pybuild/cpython3_3.8_apt/build/apt > copying apt/debfile.py -> /<>/.pybuild/cpython3_3.8_apt/build/apt > copying apt/package.py -> /<>/.pybuild/cpython3_3.8_apt/build/apt > copying apt/auth.py -> /<>/.pybuild/cpython3_3.8_apt/build/apt > copying apt/cdrom.py -> /<>/.pybuild/cpython3_3.8_apt/build/apt > copying apt/utils.py -> /<>/.pybuild/cpython3_3.8_apt/build/apt > creating /<>/.pybuild/cpython3_3.8_apt/build/apt/progress > copying apt/progress/text.py -> > /<>/.pybuild/cpython3_3.8_apt/build/apt/progress > copying apt/progress/__init__.py -> > /<>/.pybuild/cpython3_3.8_apt/build/apt/progress > copying apt/progress/base.py -> > /<>/.pybuild/cpython3_3.8_apt/build/apt/progress > creating /<>/.pybuild/cpython3_3.8_apt/build/aptsources > copying aptsources/__init__.py -> > /<>/.pybuild/cpython3_3.8_apt/build/aptsources > copying aptsources/sourceslist.py -> > /<>/.pybuild/cpython3_3.8_apt/build/aptsources > copying aptsources/distinfo.py -> > /<>/.pybuild/cpython3_3.8_apt/build/aptsources > copying aptsources/distro.py -> > /<>/.pybuild/cpython3_3.8_apt/build/aptsources > copying apt/py.typed -> /<>/.pybuild/cpython3_3.8_apt/build/apt > running build_ext > building 'apt_pkg' extension > creating build/temp.linux-x86_64-3.8 > creating build/temp.linux-x86_64-3.8/python > x86_64-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=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat > -Werror=format-security -Wno-write-strings -DDATE="Apr 25 2020" > -DTIME="11:05:50" -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.8 -c python/acquire.cc -o > build/temp.linux-x86_64-3.8/python/acquire.o -std=c++11 -Wno-write-strings > -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS -DAPT_10_CLEANER_HEADERS > -DPY_SSIZE_T_CLEAN > x86_64-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=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat > -Werror=format-security -Wno-write-strings -DDATE="Apr 25 2020" > -DTIME="11:05:50" -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.8 -c python/acquire-item.cc -o > build/temp.linux-x86_64-3.8/python/acquire-item.o -std=c++11 > -Wno-write-strings -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS > -DAPT_10_CLEANER_HEADERS -DPY_SSIZE_T_CLEAN > x86_64-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=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat > -Werror=format-security -Wno-write-strings -DDATE="Apr 25 2020" > -DTIME="11:05:50" -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.8 -c python/apt_pkgmodule.cc -o > build/temp.linux-x86_64-3.8/python/apt_pkgmodule.o -std=c++11 > -Wno-write-strings -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS > -DAPT_10_CLEANER_HEADERS -DPY_SSIZE_T_CLEAN > x86_64-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=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat >
Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10)
Hi Andreas, On 2020-10-15 15:26, Andreas Tille wrote: > when trying to build paw with gcc / fortran 10 there are some FORTRAN > errors: > > > ... > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (COMPLEX(4)/INTEGER(4)). > /<>/src/pawlib/comis/code/cs1200.F:138:24: > >76 | CALL CCOPYA(KOD(IPCP),KOD(IPCP+I),L) > |2 > .. > 138 | CALL CCOPYA(CX,KOD(IPCP-1),KLCMLX) > |1 I had the same problem with libccp4. Upstream has recommended turning off argument mismatch checks via FFLAGS, which I did in debian/rules [1]: FFLAGS += -fallow-argument-mismatch Of course this just silences the error, which should probably be fixed, especially if argument mismatch is not intentional. [1] https://salsa.debian.org/science-team/libccp4/-/commit/985597f71ee539e7e3242d43a60b271865e7672e Hope this helps, Andrius
Processed: Fortran issue in paw (Was: paw: ftbfs with GCC-10)
Processing control commands: > tags -1 help Bug #957665 [src:paw] paw: ftbfs with GCC-10 Added tag(s) help. -- 957665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10)
Control: tags -1 help Hi, when trying to build paw with gcc / fortran 10 there are some FORTRAN errors: ... Error: Type mismatch between actual argument at (1) and actual argument at (2) (COMPLEX(4)/INTEGER(4)). /<>/src/pawlib/comis/code/cs1200.F:138:24: 76 | CALL CCOPYA(KOD(IPCP),KOD(IPCP+I),L) |2 .. 138 | CALL CCOPYA(CX,KOD(IPCP-1),KLCMLX) |1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (COMPLEX(4)/INTEGER(4)). /<>/src/pawlib/comis/code/cs1200.F:154:24: 76 | CALL CCOPYA(KOD(IPCP),KOD(IPCP+I),L) |2 .. 154 | CALL CCOPYA(CX,KOD(IPCP-2),KLCMLX) |1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (COMPLEX(4)/INTEGER(4)). /<>/src/pawlib/comis/code/cs1200.F:183:22: ... Any hint how this can be solved? Kind regards Andreas. -- http://fam-tille.de
Bug#972261: FTBFS with OCaml 4.11.1 (-unsafe-string is not available)
Package: src:ocaml-melt Version: 1.4.0-3 Severity: serious Tags: ftbfs Dear Maintainer, Your package ocaml-melt FTBFS with OCaml 4.11.1 because -unsafe-string is no longer available. 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
Bug#972262: FTBFS with OCaml 4.11.1 (-unsafe-string is not available)
Package: src:ocamlviz Version: 1.01-4 Severity: serious Tags: ftbfs Dear Maintainer, Your package ocamlviz FTBFS with OCaml 4.11.1 because -unsafe-string is no longer available. 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
Bug#972138: marked as done (flatpak: fails to run if malcontent enabled but accountsservice, policykit-1 not installed)
Your message dated Thu, 15 Oct 2020 11:03:43 + with message-id and subject line Bug#972138: fixed in flatpak 1.8.2-3 has caused the Debian Bug report #972138, regarding flatpak: fails to run if malcontent enabled but accountsservice, policykit-1 not installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flatpak Version: 1.8.2-2 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! After upgrading to 1.8.2-2, I cannot run any Flatpak. I have tried com.spotify.Client and us.zoom.Zoom and both of them are returning the following error: error: The name org.freedesktop.Accounts was not provided by any .service files Downgrading to 1.8.2-1 fixes this problem. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental-debug'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-rc8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flatpak depends on: ii adduser3.118 ii bubblewrap 0.4.1-1 ii libappstream-glib8 0.7.17-1 ii libarchive13 3.4.3-2 ii libc6 2.31-4 ii libdconf1 0.38.0-1 ii libfuse2 2.9.9-3 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.66.1-1 ii libgpgme11 1.14.0-1 ii libjson-glib-1.0-0 1.6.0-1 ii libmalcontent-0-0 0.9.0-2 ii libostree-1-1 2020.6-1 ii libpolkit-agent-1-00.105-29 ii libpolkit-gobject-1-0 0.105-29 ii libseccomp22.4.4-1 ii libsoup2.4-1 2.72.0-2 ii libsystemd0246.6-1 ii libxau61:1.0.8-1+b2 ii libxml22.9.10+dfsg-6 ii libzstd1 1.4.5+dfsg-4 ii xdg-dbus-proxy 0.1.2-1 Versions of packages flatpak recommends: ii desktop-file-utils 0.26-1 ii gtk-update-icon-cache3.24.23-2 ii hicolor-icon-theme 0.17-2 ii libpam-systemd 246.6-1 ii p11-kit 0.23.21-2 ii policykit-1 0.105-29 ii shared-mime-info 2.0-1 ii xdg-desktop-portal 1.8.0-1 ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend] 1.8.0-1 Versions of packages flatpak suggests: ii avahi-daemon0.8-3 pn malcontent-gui - -- no debconf information -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl+FS9ISHGJlcm5hdEBk ZWJpYW4ub3JnAAoJEJWkL+g1NSX5U2cQAI2kacZSFRvURLJGiVhXn6FoNL1aLQnJ cVm8HfVbJ3Glf3yadvX6PWFRfs6deh2Z3V7gjKgHUhFwj6C+LhZb2Wd9YkC4Dl3K HgFmLE57NnYysA/AQ9cOq3quCGFGMfv4/t4M3r0omTMT1GREAz8WfnqSWFb5c+d1 k7TSq2jF5rg/+8kuEXxcmtGQz/Xd5DXK6VudEfYmBOrqFXCH71SRnICcLywjlFYw HimicbNaSP0Bdx9ZSInfMGYg5O4bRTr/DSrVViw/MlUf7PNJAgQyOp7sDwzffSJg G+SBROq5qKzdwBTTuTLSo3PlFxPLkZGR5jj7e1432IuJrzRdhdEXdln37I7rs6RR dOHEitpe399qUI+RNXg93ORiE8BR5XPs4Fth28V32bsgaLa87dWqivhXl3gwmqtz wJpHP7MU3vsf2D0r7MWqIEsfZJNWLMCot58tTLUB0Hut7DScjsqJBnF5lWEK+LZ0 /CHUr5I6D8xyKj7Skf1GKN6OT2ZtKA/xubF/Lx1V08Q5xJ/IlrVrvU1Pk+3p+AdY UrC+wB7a+0uTog6RD1aRRAhWT8i48PvaPvbxRAD2z99/Hy4ZhAjnINEsOEu/+4g/ iw4YBBWDtpFLRg4dbc1ttyEsH3jCOkB63RGXZzQfPNIm6mdhHwtlKZfi+2sDxAIA yipW/zOzeoSX =Vgzd -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: flatpak Source-Version: 1.8.2-3 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of flatpak, 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. Simon McVittie (supplier of updated flatpak 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
Bug#972259: FTBFS with OCaml 4.11.1 (-unsafe-string is not available)
Package: src:galax Version: 1.1-16 Severity: serious Tags: ftbfs Dear Maintainer, Your package galax FTBFS with OCaml 4.11.1 because -unsafe-string is no longer available. 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
Bug#970764: marked as done (python3-venv: /usr/bin/pyvenv is a dangling symlink, man page, too)
Your message dated Thu, 15 Oct 2020 10:50:35 + with message-id and subject line Bug#970764: fixed in python3-defaults 3.9.0-1 has caused the Debian Bug report #970764, regarding python3-venv: /usr/bin/pyvenv is a dangling symlink, man page, too 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.) -- 970764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-venv Version: 3.8.2-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: norb...@preining.info Hi something seems to have gone a bit wrong with the venv packaging, since both the actual binary pyvenv in /usr/bin, as well as the man page are both dangling symlinks, rendering the package unusable. Thanks Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.10 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-venv depends on: ii python33.8.2-3 ii python3-distutils 3.8.5-1 ii python3.8-venv 3.8.6~rc1-2 python3-venv recommends no packages. python3-venv suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python3-defaults Source-Version: 3.9.0-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python3-defaults, 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. Matthias Klose (supplier of updated python3-defaults package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Oct 2020 12:10:47 +0200 Source: python3-defaults Architecture: source Version: 3.9.0-1 Distribution: experimental Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 970764 Changes: python3-defaults (3.9.0-1) experimental; urgency=medium . * Default python3 version to 3.9. * Drop the venv binary and man page. Closes: #970764. Checksums-Sha1: 10f2eec0e77e9a3bde54430f173eea2fdd3cb901 2798 python3-defaults_3.9.0-1.dsc 6c522558a05e79f40606fbac66c6e3fa835ae9fc 139154 python3-defaults_3.9.0-1.tar.gz 4843ae4731e7111ea8563d38816160d6f2656d74 6748 python3-defaults_3.9.0-1_source.buildinfo Checksums-Sha256: f65bf88adaf081c8b589fef96b5dd9a4c98e8ea63988d64a7df5f2ec277222bc 2798 python3-defaults_3.9.0-1.dsc 846f8084a064af6ff89cb727bf8fd17319a2106fbcf1bc3808e941cff7566f1b 139154 python3-defaults_3.9.0-1.tar.gz 845cdd561569850fcda9289d4a6fe5a4463af45920211d3bf9c4c61a18634f0f 6748 python3-defaults_3.9.0-1_source.buildinfo Files: 99d8b9024ed1115a669f30082ac823ab 2798 python optional python3-defaults_3.9.0-1.dsc 056460ad01ded4c0f425b4bb83a4fb99 139154 python optional python3-defaults_3.9.0-1.tar.gz c72da9fd9eb3210312099ae950449b35 6748 python optional python3-defaults_3.9.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl+IJZkQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9R+/EACYRQ0smku63H7o0zrKM3/R7q49mEqUzEiO NmQOLPReb6GBjjRlpyW50H8XrXoKcl6S1Uv1YDiMyGX8ns4vS5xGOh1bQk2XV9c4 b5rVH1OckI4PngJZYY71FlfJQfL9mYqsj3nRmgoRMHLoZFOB8k53YSqlcdwEhJ20 nP25RpYpJprwZc9XSYiA+gPSK6+0+mAUv7w4nJGwcOTPTJQbUXRwlhMDJXN1bqvA RpgSSxt/7m9iivPU5RDtc8coFHqxyRC/+Q0Ym5Egcf3rqobxLZMIY47ACmuhYW5b pywpiQ85jXYVkCLc6Q71I2Geh4eZO1f3/4qT+cVdx/I/j+1kNv5XcyPY9OiZx6PV z6Olr3Jx18fJqYmqaaqkmyij6lkuHfRyUDUJwdn+jYLG2anPmH274o9qEpF7irGS ZIrL4f1wn0CuH66btf6/0CrV67TpPBvB3QLKjMl2kKQeGGYgSSOnYTFb0FRF26sh A5UO8oTQBOtfiYeNHtAD1hNPuo+mvhNqKTkIA5E9LkgT4cSGBPpMsDmQ+gjlKrqs GJCvLvylhJRabXxRtRCtlaDMQFxUtkl17sKLBGhZH93WEed+0To0JUo8te/KQOns I7wbi+RFoVjTgovggwhaunx3wnwqfSH7MVOfSTGrKaAAGzQGwfmIBl9U7S0XUNZC MYMr+9cxjA== =O8Yg -END PGP SIGNATURE End Message ---
Bug#972145: mct_manager_get_app_filter() fails closed if accountsservice not installed
On Tue, 13 Oct 2020 at 10:29:27 +0100, Simon McVittie wrote: > This would ideally not be a hard dependency, but the integration with > libmalcontent (parental controls) fails closed in some situations where > it should probably fail open. I've contacted upstream. I've worked around the symptom (#972138) by applying a patch to flatpak, which has been proposed upstream but not merged yet. I'm leaving the libmalcontent bug #972145 open, because I think it can also affect gnome-shell if Recommends are not installed. Again, I've sent a patch upstream but it hasn't been merged yet. smcv
Bug#972258: FTBFS (1 file would be reformatted)
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
Bug#972138: marked as pending in flatpak
Control: tag -1 pending Hello, Bug #972138 in flatpak reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/flatpak/-/commit/ca496b8f3fd53a35e0643bcaf325010e41e5ed1b Skip parental controls if accountsservice is not installed The malcontent package (which activates parental controls support) depends on accountsservice, but the libmalcontent-0-0 client library does not, so we need to cope gracefully with the case where neither malcontent nor accountsservice is installed. Presumably, in such installations the sysadmin did not want the parental controls feature. Ideally libmalcontent would do this itself (#972145). Closes: #972138 (this message was generated automatically) -- Greetings https://bugs.debian.org/972138
Processed: Bug#972138 marked as pending in flatpak
Processing control commands: > tag -1 pending Bug #972138 [flatpak] flatpak: fails to run if malcontent enabled but accountsservice, policykit-1 not installed Added tag(s) pending. -- 972138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957614: marked as done (nut: ftbfs with GCC-10)
Your message dated Thu, 15 Oct 2020 10:35:51 + with message-id and subject line Bug#957614: fixed in nut 2.7.4-13 has caused the Debian Bug report #957614, regarding nut: ftbfs 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.) -- 957614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nut Version: 2.7.4-12 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. 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. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/nut_2.7.4-12_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] dh_fixperms -O--no-parallel dh_missing -O--no-parallel dh_missing: warning: lib/x86_64-linux-gnu/libnutclient.la exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/x86_64-linux-gnu/libnutscan.la exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/x86_64-linux-gnu/libnutscan.a exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/x86_64-linux-gnu/libupsclient.la exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/nut/skel exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/man/man8/nut-recorder.8 exists in debian/tmp but is not installed to anywhere The following debhelper tools have reported what they installed (with files per package) * dh_install: libnutclient-dev (4), libnutclient0 (2), libnutscan-dev (6), libnutscan1 (2), libups-nut-perl (1), libupsclient-dev (5), libupsclient4 (2), nut (1), nut-cgi (6), nut-client (25), nut-doc (1), nut-ipmi (2), nut-powerman-pdu (1), nut-server (64), nut-snmp (1), nut-xml (1) * dh_installdocs: libnutclient-dev (4), libnutclient0 (4), libnutscan-dev (4), libnutscan1 (4), libups-nut-perl (4), libupsclient-dev (4), libupsclient4 (4), nut (20), nut-cgi (5), nut-client (4), nut-doc (4), nut-ipmi (4), nut-powerman-pdu (4), nut-server (4), nut-snmp (5), nut-xml (4) * dh_installman: libnutclient-dev (34), libnutclient0 (0), libnutscan-dev (17), libnutscan1 (0), libups-nut-perl (0), libupsclient-dev (17), libupsclient4 (0), nut (0), nut-cgi (6), nut-client (9), nut-doc (0), nut-ipmi (1), nut-powerman-pdu (1), nut-server (54), nut-snmp (1), nut-xml (1) 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 For a short-term work-around: Add the files to debian/not-installed dh_dwz -O--no-parallel dh_strip -O--no-parallel dh_makeshlibs -O--no-parallel dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libnutclient0/DEBIAN/symbols doesn't match completely debian/libnutclient0.symbols --- debian/libnutclient0.symbols (libnutclient0_2.7.4-12_amd64) +++ dpkg-gensymbolsav7k92 2020-02-26 12:29:01.898219842 + @@ -1,5 +1,6 @@ libnutclient.so.0 libnutclient0 #MINVER# * Build-Depends-Package: libnutclient-dev +
Bug#957020: marked as done (audit: ftbfs with GCC-10)
Your message dated Thu, 15 Oct 2020 10:04:08 + with message-id and subject line Bug#957020: fixed in audit 1:2.8.5-3.1 has caused the Debian Bug report #957020, regarding audit: ftbfs 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.) -- 957020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:audit Version: 1:2.8.5-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. 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. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/audit_2.8.5-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] |~ gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -DPIE -g -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auditctl-auditctl-llist.o `test -f 'auditctl-llist.c' || echo '../../../src/'`auditctl-llist.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -DPIE -g -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auditctl-delete_all.o `test -f 'delete_all.c' || echo '../../../src/'`delete_all.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -DPIE -g -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auditctl-auditctl-listing.o `test -f 'auditctl-listing.c' || echo '../../../src/'`auditctl-listing.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wno-pointer-sign -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o aureport.o ../../../src/aureport.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wno-pointer-sign -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auditd-config.o ../../../src/auditd-config.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wno-pointer-sign -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o ausearch-llist.o ../../../src/ausearch-llist.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wno-pointer-sign -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o aureport-options.o ../../../src/aureport-options.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wno-pointer-sign -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o ausearch-string.o ../../../src/ausearch-string.c gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I../../.. -I../../../lib -I../../../src/libev -I../../../auparse -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE
Bug#972251: python-line-profile ftbfs in unstable
Package: src:python-line-profiler
Version: 2.1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
likely not python3.9 specific, but needed to build for python3.9
[...]
I: pybuild base:217: /usr/bin/python3.9 setup.py build
running build
running build_py
copying line_profiler.py ->
/<>/.pybuild/cpython3_3.9_line-profiler/build
copying kernprof.py ->
/<>/.pybuild/cpython3_3.9_line-profiler/build
copying line_profiler_py35.py ->
/<>/.pybuild/cpython3_3.9_line-profiler/build
running build_ext
cythoning _line_profiler.pyx to _line_profiler.c
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File: /<>/_line_profiler.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
building '_line_profiler' extension
creating build
creating build/temp.linux-x86_64-3.9
x86_64-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 -I/usr/include/python3.9 -c _line_profiler.c -o
build/temp.linux-x86_64-3.9/_line_profiler.o
x86_64-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 -I/usr/include/python3.9 -c timers.c -o
build/temp.linux-x86_64-3.9/timers.o
timers.c:36:2: error: #error "This module requires gettimeofday() on non-Windows
platforms!"
36 | #error "This module requires gettimeofday() on non-Windows platforms!"
| ^
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.9 setup.py build
dh_auto_build: error: pybuild --build --test-pytest -i python{version} -p "3.9
3.8" returned exit code 13
make: *** [debian/rules:14: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
Bug#969494: r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’
Control: block -1 by 969426
Besides the missing r-cran-broom.mixed there might be another issue:
$ sh /usr/share/doc/r-cran-mice/run-unit-test
BEGIN TEST testthat.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-anova.R#2) ──
function 'enterRNGScope' not provided by package 'Rcpp'
Backtrace:
1. mice::mice(nhanes2, m = 10, print = FALSE, seed = 71242)
2. mice:::sampler(...)
3. mice:::sampler.univ(...)
5. mice::mice.impute.pmm(...)
6. mice:::matcher(yhatobs, yhatmis, k = donors)
--
http://fam-tille.de
Processed: Re: r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’
Processing control commands: > block -1 by 969426 Bug #969494 [src:r-cran-mice] r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’ 969494 was not blocked by any bugs. 969494 was blocking: 970330 971235 Added blocking bug(s) of 969494: 969426 -- 969494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972250: vienna-rna needs a sourceful upload for python3.9
Package: src:vienna-rna Version: 2.4.14+dfsg-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 vienna-rna needs a sourceful upload for python3.9, packages in contrib are not built by the buildds.
Bug#972249: unrardll needs a sourceful upload for python3.9
Package: src:unrardll Version: 0.1.3-6 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 unrardll needs a sourceful upload for python3.9, packages in contrib are not built by the buildds.
Bug#972032: setools ftbfs with python3.9 as supported python version
can be worked around by building without -Werror. Note that this won't work with Python 3.10 anymore. Uploaded to the delayed queue.
Bug#972247: Probes fail with error: ‘struct mm_struct’ has no member named mmap_sem
Package: systemtap
Version: 4.3-2
Severity: grave
With linux-image-5.8.0-3-amd64 version 5.8.14-1, stap fails as follows:
$ sudo stap -e 'probe oneshot { println("hello world") }'
[...]
/usr/share/systemtap/runtime/linux/access_process_vm.h: In function
‘__access_process_vm_’:
/usr/share/systemtap/runtime/linux/access_process_vm.h:32:19: error: ‘struct
mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
32 | down_read (>mmap_sem);
| ^~~~
| mmap_base
/usr/share/systemtap/runtime/linux/access_process_vm.h:87:17: error: ‘struct
mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
87 | up_read (>mmap_sem);
| ^~~~
| mmap_base
This upstream commit should fix the issue:
https://sourceware.org/git/?p=systemtap.git;a=commit;h=37066e2c3a9d9f48fc01b13ec0493b1c67551275
Bug#972016: py-lmdb ftbfs with python3.9
now uploaded to the delayed queue
Bug#972026: python-pyo ftbfs with python3.9 as supported python version
now uploaded to the delayed queue
Bug#972009: marked as done (gudhi ftbfs with python3.9 as supported python version)
Your message dated Thu, 15 Oct 2020 08:43:18 + with message-id and subject line Bug#972009: fixed in gudhi 3.3.0+dfsg-2 has caused the Debian Bug report #972009, regarding gudhi ftbfs with python3.9 as supported python 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.) -- 972009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gudhi Version: 3.3.0+dfsg-1 Severity: important Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 seem to be a packaging error [...] [100%] Built target python make[3]: Leaving directory '/<>/gudhi-3.3.0+dfsg/build/userversion' /usr/bin/cmake -E cmake_progress_start /<>/gudhi-3.3.0+dfsg/build/userversion/CMakeFiles 0 make[2]: Leaving directory '/<>/gudhi-3.3.0+dfsg/build/userversion' for py3ver in 3.9 ; do \ dh_auto_build --buildsystem=cmake --no-parallel --builddirectory=build-py$py3ver/userversion ; \ done cd build-py3.9/userversion && make -j1 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>/gudhi-3.3.0+dfsg/build-py3.9/userversion' make[2]: *** No targets specified and no makefile found. Stop. make[2]: Leaving directory '/<>/gudhi-3.3.0+dfsg/build-py3.9/userversion' dh_auto_build: error: cd build-py3.9/userversion && make -j1 "INSTALL=install --strip-program=true" returned exit code 2 make[1]: *** [debian/rules:63: override_dh_auto_build-arch] Error 25 make[1]: Leaving directory '/<>/gudhi-3.3.0+dfsg' make: *** [debian/rules:42: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: gudhi Source-Version: 3.3.0+dfsg-2 Done: Gard Spreemann We believe that the bug you reported is fixed in the latest version of gudhi, 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. Gard Spreemann (supplier of updated gudhi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Oct 2020 17:23:10 +0200 Source: gudhi Architecture: source Version: 3.3.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Gard Spreemann Changed-By: Gard Spreemann Closes: 972009 Changes: gudhi (3.3.0+dfsg-2) unstable; urgency=medium . * Treat all Python versions the same way during build. * Fix broken build with multiple Python versions. (Closes: #972009) Checksums-Sha1: 638515350733d505f07acd8b5d3eb381d57abfb0 3157 gudhi_3.3.0+dfsg-2.dsc 53f87178fc17319895b0754ca747be8c5bb730be 10940 gudhi_3.3.0+dfsg-2.debian.tar.xz e6e75028376d4ae7560989729ca8e81da445700a 10860 gudhi_3.3.0+dfsg-2_source.buildinfo Checksums-Sha256: 61379652f548e54d2df751088e905cf580ce667395b2dccc7dc2a86fbc090b62 3157 gudhi_3.3.0+dfsg-2.dsc 3f8e9eb7cd474f0c2578b35baec5880232b74265c671a21a0543f9ccc3646ec6 10940 gudhi_3.3.0+dfsg-2.debian.tar.xz 30f710e67d3427fe128473086ecba6b0c75b79af70e78b86bd8273eaf6d1e568 10860 gudhi_3.3.0+dfsg-2_source.buildinfo Files: 802be3dfd0b7587698a0b7c89d86dbb7 3157 math optional gudhi_3.3.0+dfsg-2.dsc 159c36d2a365cf4d0cd017791fe9f060 10940 math optional gudhi_3.3.0+dfsg-2.debian.tar.xz 9b3c4babdbd0ed2fb7dfba5324bb2f87 10860 math optional gudhi_3.3.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEz8XvhRCFHnNVtV6AnRFYKv1UjPoFAl+IATQSHGdzcHJAbm9u ZW1wdHkub3JnAAoJEJ0RWCr9VIz69L0QAJnQdG98trHCJR37QpDBfSufgzPTXPPZ BIu/EmAKRP6XESCYRKs5G+CRlo3sr70+rAw5m3zSq4WCA5sT2mUWUK7GtF89M/hU fJ0A1k+tsBgbKxynsQFrDtnQf6SpCkdLc25SizlB7LN/7fi3tUqcqfsn4yj6crJc w9F0/SVE09VXnWjBcSc63M5KJ1mlz65DPgBLl8MpDFP/PVOoaO26u9PUCtX1VhB2 nObQ09v+rSHlfR3kA7tYTBbgRAFCLqzIeqRCzmjQd6lyGqrCipd3Jm1x0dt9y0zT HNbkWvnEKLPLQKbwvSt8EaV362pORf3+pfLWOGdZsR6gDj+4NQo5soQBb+AtnZDL V8NyhRIOl5Zfwrz+yH0sYEzZE+IDozwZmgR0/4P/KyeI78yPDlBKS1d19BMBBZVE 3kBzXLb2tmY5QuY15aU2Tw6ej8e1WsW73utlOl4wDRI4bekvYCPsBhGVnlL4vOjh B4h3Smu8u7Qi1jdTRDCz/109C9u81w4cOmKZ6QonfNKs15ocyiztpBkHxQ9UBFsh Xs7i3Y1EopXh9hCOsyaG32jDnDvToeA60bEexUgiVLPyG/ZWOoUfa0Nfh36neX/+ eiIEXrEN5sfgZuTjSev/9sK9yWQrBO14n+inO0Yz743X1gPUgaQPJMeDrK+AHkNw wKZSonZFFvr+ =X83T
Bug#972246: numba ftbfs in unstable with python3.9 as supported python3 version
Package: src:numba Version: 0.51.2-1 Severity: serious Tags: sid bullseye ftbfs numba ftbfs in unstable, different failures on some architectures. See https://buildd.debian.org/status/package.php?p=numba - test suite time outs ? - packaging errors (armel, mips64el, ppc64el, ...)
Processed: Re: Bug#960769: swt4-gtk FTBFS on 32bit
Processing control commands: > severity -1 important Bug #960769 [src:swt4-gtk] swt4-gtk FTBFS on 32bit Severity set to 'important' from 'serious' -- 960769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960769: swt4-gtk FTBFS on 32bit
Control: severity -1 important Hi, On Mon, 5 Oct 2020 06:30:51 +0200 Sebastiaan Couwenberg wrote: > > The binaries for the 32-bit architectures were removed in #962915 [1], > > but only for version 4.13.0-1 in unstable. > > This was not sufficient to let it migrate to testing. > > The britney output logs a bunch of packages on i386. > > i386 & amd64 are the NOBREAKALL_ARCHES in britney.conf, see: [Release Team member hat on]: I have added hints to allow the breakage on i386 as this was now done on purpose. I've been watching this issue since August, but was waiting for all the right binary packages in unstable to be removed. This bug at severity serious was preventing swt4-gtk from migrating to testing, but as the 32 bit packages were removed, this bug should no longer blocking migration, hence I downgrade it now. Paul signature.asc Description: OpenPGP digital signature
Processed: tagging 972032
Processing commands for cont...@bugs.debian.org: > tags 972032 + ftbfs Bug #972032 [src:setools] python-setools ftbfs with python3.9 as supported python version Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 972230
Processing commands for cont...@bugs.debian.org: > tags 972230 + upstream Bug #972230 [jruby] CVE-2017-17742 CVE-2019-16201 CVE-2019-16254 CVE-2019-16255 CVE-2020-25613 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 972230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 972011
Processing commands for cont...@bugs.debian.org: > tags 972011 + ftbfs Bug #972011 [src:meliae] meliae's autopkg tests fail, and package ftbfs with python3.9 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 971669
Processing commands for cont...@bugs.debian.org:
> affects 971669 src:med-fichier
Bug #971669 {Done: Alastair McKinstry } [libopenmpi3]
libopenmpi3: armel mipsel: mca_pmix_pmix3x.so: undefined symbol:
OPAL_MCA_PMIX3X_PMIx_Get_version
Bug #972236 {Done: Alastair McKinstry } [libopenmpi3]
libopenmpi3: mca_pmix_pmix3x.so is still shipped on armel/mipsel
Added indication that 971669 affects src:med-fichier
Added indication that 972236 affects src:med-fichier
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
971669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971669
972236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 972028
Processing commands for cont...@bugs.debian.org: > tags 972028 + ftbfs Bug #972028 [src:python-acora] python-acora ftbfs with python3.9 as supported python version Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 972028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
