Bug#1024890: ntcard - build-dependencies unsatisfiable on 32-bit.
Hi Peter, Am Sun, Nov 27, 2022 at 02:30:15PM + schrieb Peter Michael Green: > Package: ntcard > Version: 1.2.2+dfsg-4 > Severity: serious > > ntcard build-depends on libnthash-dev which is no longer available on 32-bit > architectures. > > There are in general 3 potential soloutions for this (in roughly descending > order of preference) > > 1. Fix your build-dependencies so they are once again available on all > release architectures. > 2. Eliminate the build-dependencies in question, either generally or on > those specific architectures. Both it not possible. > 3. Declare your package unsupported on 32-bit architectures and file a > removal bug with the ftpmasters. For what architecture should we file a removal bug? The package was never released on 32 bit architectures so I see no point in bothering ftpmaster. > I do not know which are pratical in the case of your particular package. As far as I know its a frequently used method to add Build-Depends that are not available for a certain architecture to prevent autobuilders from building those packages under these architectures. If I would explicitly restrict the architectures of nthash it would need manual intervention if libbtllib-dev might become available also for 32 bit (which is probably not the case - but at least in theory this is the reason to *not* provide a list of supported architectures). Could you please give any reason which backs up your choice "serious" for this bug report? IMHO the package is perfectly OK and the bug should be closed. Kind regards Andreas. -- http://fam-tille.de
Bug#1023020: cmark-gfm: FTBFS on s390x
Scott Talbert writes: > @Keith, do you have time to upload this patch? Unfortunately, this is > blocking a large number of packages from migrating to testing. > Alternatively, any objections to an NMU? I didn't get to this today, and might not until thursday or friday. Happy for your to NMU if you like. -- -keith signature.asc Description: PGP signature
Bug#1024998: g810-led: Security risk: Leaves /dev/input/event* with read and write permissions for all users
On Wed, 30 Nov 2022 06:59:41 +0100, Salvatore Bonaccorso wrote: > The issue got CVE-2022-46338 assigned by MITRE. > > Stephen, the issue is marked no-dsa for bullseye, but a fix might go > still trough the upcoming point release (scheduled for 17th december). Thanks, I’ll submit a stable update. Regards, Stephen pgpwU4NmoIwN8.pgp Description: OpenPGP digital signature
Bug#1025135: libcoap2: Do not ship in bookworm
Source: libcoap2 Version: 4.2.1-1 Severity: serious The API version 2 of libcoap was given up long ago and is replaced by API v3. The last version for v2 was released on 2019. Thus no upstream development and no updates will happen for this package and we should not ship libcoap2 packages in bookworm onward. There is a replacement avaialable - users should switch to libcoap3. https://tracker.debian.org/pkg/libcoap3 Regards Carsten
Bug#1024998: g810-led: Security risk: Leaves /dev/input/event* with read and write permissions for all users
Control: retitle -1 g810-led: Security risk: Leaves /dev/input/event* with read and write permissions for all users (CVE-2022-46338) On Mon, Nov 28, 2022 at 03:45:16PM +0100, Xavi Drudis Ferran wrote: > Package: g810-led > Version: 0.4.2-2.1 > Severity: critical > Tags: patch upstream security > Justification: root security hole > X-Debbugs-Cc: xdru...@tinet.cat, Debian Security Team > > > Dear Maintainer, > > I hesitate to file as critical, but I came across a bug report in > upstream that looked serious enough since it would allow all local > processes to eavesdrop on keyboard input, including passwords, etc. I > haven't tried an exploit, but it seemed better to just restrict > /dev/input/event* permissions to those of other event dev files. > > Without this patch, I can read /dev/input/event2 and /dev/input/event3 as a > normal user. I see bytes in /dev/input/event2 when typing as a normal > user and also typing in another terminal (Konsole) typing as > root. event3 only shows the characters typed by the normal user. > > With the patch I can't read /dev/input/event* as a normal user. > > And the bug is publically reported upstream (some 10 days ago). > >* What led up to the situation? > > Reviewing upstream bugs, found https://github.com/MatMoul/g810-led/issues/293 > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > Nothing really. I wrote the patch, rebuilt, and observed the > permissions were fixed. My keyboard seems to work both with and > without the patch (needs a kernel with CONFIG_HIDRAW), when calling > g810-led as root. As normal user it doesn't work (both with or without > patch), due to no permission for /dev/hidraw2. > > It should really be fixed upstream, but maybe it's worth fixing meanwhile > or removing the package temporarily ? The issue got CVE-2022-46338 assigned by MITRE. Stephen, the issue is marked no-dsa for bullseye, but a fix might go still trough the upcoming point release (scheduled for 17th december). Regards, Salvatore
Processed: Re: Bug#1024998: g810-led: Security risk: Leaves /dev/input/event* with read and write permissions for all users
Processing control commands:
> retitle -1 g810-led: Security risk: Leaves /dev/input/event* with read and
> write permissions for all users (CVE-2022-46338)
Bug #1024998 {Done: Stephen Kitt } [g810-led] g810-led:
Security risk: Leaves /dev/input/event* with read and write permissions for all
users
Changed Bug title to 'g810-led: Security risk: Leaves /dev/input/event* with
read and write permissions for all users (CVE-2022-46338)' from 'g810-led:
Security risk: Leaves /dev/input/event* with read and write permissions for all
users'.
--
1024998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1024496: qiskit-terra: FTBFS with Python 3.11 as a supported version
Source: qiskit-terra Followup-For: Bug #1024496 It seems like upstream has fixed the issue: https://github.com/Qiskit/qiskit-terra/commit/75d66dd8ba34627addc4914eafa38775fc74ca92 But from #1008625, upgrading it maybe need more dependencies, this will cost more time. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008625 -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1012897: marked as done (aspectc++: ftbfs with GCC-12)
Your message dated Wed, 30 Nov 2022 02:49:15 + with message-id and subject line Bug#1012897: fixed in aspectc++ 1:2.3+git20221129-1 has caused the Debian Bug report #1012897, regarding aspectc++: ftbfs with GCC-12 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.) -- 1012897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aspectc++ Version: 1:2.3+git20211104-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/aspectc++_2.3+git20211104-2_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /<>/Puma/gen-release/step1/src/CCSemExpr.cc: In member function ‘Puma::CTypeInfo* Puma::CCSemExpr::resolve(Puma::CT_CastExpr*, Puma::CTree*)’: /<>/Puma/gen-release/step1/src/CCSemExpr.cc:2154:23: warning: variable ‘t1’ set but not used [-Wunused-but-set-variable] 2154 | CTypeInfo *result, *t1; | ^~ /<>/Puma/gen-release/step1/src/CCSemExpr.cc: In member function ‘Puma::CTypeInfo* Puma::CCSemExpr::resolve(Puma::CT_DynamicCast*, Puma::CTree*)’: /<>/Puma/gen-release/step1/src/CCSemExpr.cc:2196:23: warning: variable ‘t1’ set but not used [-Wunused-but-set-variable] 2196 | CTypeInfo *result, *t1; | ^~ /<>/Puma/gen-release/step1/src/CCSemExpr.cc: In member function ‘Puma::CTypeInfo* Puma::CCSemExpr::resolve(Puma::CT_StaticCast*, Puma::CTree*)’: /<>/Puma/gen-release/step1/src/CCSemExpr.cc:2235:23: warning: variable ‘t1’ set but not used [-Wunused-but-set-variable] 2235 | CTypeInfo *result, *t1; | ^~ /<>/Puma/gen-release/step1/src/CCSemExpr.cc: In member function ‘Puma::CTypeInfo* Puma::CCSemExpr::resolve(Puma::CT_ReintCast*, Puma::CTree*)’: /<>/Puma/gen-release/step1/src/CCSemExpr.cc:2277:23: warning: variable ‘t1’ set but not used [-Wunused-but-set-variable] 2277 | CTypeInfo *result, *t1; | ^~ /<>/Puma/gen-release/step1/src/CCSemExpr.cc: In member function ‘Puma::CTypeInfo* Puma::CCSemExpr::resolve(Puma::CT_ConstCast*, Puma::CTree*)’: /<>/Puma/gen-release/step1/src/CCSemExpr.cc:2319:23: warning: variable ‘t1’ set but not used [-Wunused-but-set-variable] 2319 | CTypeInfo *result, *t1; | ^~ Compiling CCInstantiation.cc... Compiling DeducedArgument.cc... /<>/Puma/gen-release/step1/src/CCSyntax.cc: In static member function ‘static bool Puma::CCSyntax::NestedNameSpec::__exec_old_parse(Puma::CCSyntax&)’: /<>/Puma/gen-release/step1/src/CCSyntax.cc:734:10: error: ‘seq’ is not a member of ‘Puma::Syntax’ 734 | return seq (s); | ^~ /<>/Puma/gen-release/step1/src/CCSyntax.cc: In static member function ‘static bool Puma::CCSyntax::NewDeclarator::parse(Puma::CCSyntax&)’: /<>/Puma/gen-release/step1/src/CCSyntax.cc:967:12: error: ‘seq’ is not a member of ‘Puma::Syntax’ 967 | (seq (s) && |^~ /<>/Puma/gen-release/step1/src/CCSyntax.cc: In static member function ‘static bool Puma::CCSyntax::DirectNewDeclarator::parse(Puma::CCSyntax&)’: /<>/Puma/gen-release/step1/src/CCSyntax.cc:977:18: error: ‘seq’ is not a member of ‘Puma::Syntax’
Bug#1012184: marked as done (aspectc++: Please upgrade to llvm-toolchain-14)
Your message dated Wed, 30 Nov 2022 02:49:15 + with message-id and subject line Bug#1012184: fixed in aspectc++ 1:2.3+git20221129-1 has caused the Debian Bug report #1012184, regarding aspectc++: Please upgrade to llvm-toolchain-14 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.) -- 1012184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aspectc++ Version: 1:2.3+git20211104-2 Severity: serious Dear maintainer, Because we want to reduce the amount of llvm-toolchain source packages in testing, I am going to remove src:llvm-toolchain-12 from bookworm. Once the source is removed, your package will fail to build from source in bookworm. Please migrate your builld dependency to a different version of llvm-*dev and libclang-*dev, ideally to the unversioned one. Currently we have llvm-11-dev and llvm-13-dev, and libclang-11-dev and libclang-13-dev in testing too, but we'll try to remove 11 of both before the bookworm release. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: aspectc++ Source-Version: 1:2.3+git20221129-1 Done: Reinhard Tartler We believe that the bug you reported is fixed in the latest version of aspectc++, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler (supplier of updated aspectc++ package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Nov 2022 17:54:11 -0500 Source: aspectc++ Architecture: source Version: 1:2.3+git20221129-1 Distribution: unstable Urgency: medium Maintainer: Reinhard Tartler Changed-By: Reinhard Tartler Closes: 1004884 1012184 1012897 Changes: aspectc++ (1:2.3+git20221129-1) unstable; urgency=medium . * New upstream version * Build against llvm-14, closes: #1012184, #1004884, #1012897 Checksums-Sha1: 3023233f247a8fabe4d8d7d85a059c6aeb983539 2329 aspectc++_2.3+git20221129-1.dsc 3417be3fc677b6ac5cb7450aa4a024751b0b4b07 4307643 aspectc++_2.3+git20221129.orig.tar.bz2 dff6090d5e317b30fc2df7bc5e21e8ac1b8764cd 15340 aspectc++_2.3+git20221129-1.debian.tar.xz Checksums-Sha256: 87ab9e01847dafb022cdfde56585fbc291a09f16d92f603d374661eaaf3a9357 2329 aspectc++_2.3+git20221129-1.dsc 8b3ebf9701b7d3a031728d4f56aec177693699ea462dccbfe93b667151803842 4307643 aspectc++_2.3+git20221129.orig.tar.bz2 ce73276f3dc0936d1dd1e1f860ee394a10944d4a898670069865f98e251e39c9 15340 aspectc++_2.3+git20221129-1.debian.tar.xz Files: 658b68c25dfe64b09af09a359ddae2ca 2329 devel optional aspectc++_2.3+git20221129-1.dsc 53dacbf413a9328c13f3b35f5df2a26e 4307643 devel optional aspectc++_2.3+git20221129.orig.tar.bz2 dc138519bfe3437b205cc80424352a1d 15340 devel optional aspectc++_2.3+git20221129-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmOGwIAUHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJsuIxxAAsaofA4g0oIgtnAgP19ZMi8DkFeF8 0MhNHoTeh6ni+VLSDy3zx6J6bzWe6ZEA8BIj4lTU0Jr+vAs+0eRI2Hplx9G+G3HK tQwJL780lmvHrHfG9G9j1b15fhSdKFs/wyne/G2DK1FFMJVahSD90hWElbwgjlP9 Z+AasnjWWM2mg2iV3O/TEH4BwVyvGkWSAUj3hazpEM567oywdmF/Oa/AOtRBGBcF AO1yGaBbaE1Yd02WwJ6ze3SQvDE4oWMjuoD3DagHpFeSIUJCiAdQebw0ClLtzevf M7QzlLX91T3zHOsTAIz0dVQOwrM3dWcF6e4biOZAlWSAzeRfy+BSsGF3xyjOrEZo S8XJAwxLnRN3D+b16qiwBNLNpTsJ00yx3hx2V5NMdlBd1xJ+wqstWr4aAfXX3ijQ 5SDVcXkuZceovJWGinAy1EnaSx9TYA2rOY9QBwXQZS9ghOkLQ+pK+lJScGyOxrbU sCYzzytK68vki+KgPSUOEr2RM0DHgqmwwcbOd5IMkdEfHqtYJzmyQ4iZspVMODP6 K67i3MAp0pzScOZ0UDmlxuMPf83w2bYeC4oF6bVEpQZ1H5GbpyPFvvnBHTF/00EQ KzwFJQHx2Nnrty/lgBZXnBuJWoRbsC7XfI6tK2ZY9aaKAYZoXMHYlyJXiQHx8+dg hjNCA6rpGz6dCqc= =8mK0 -END PGP SIGNATURE End Message ---
Bug#1023020: cmark-gfm: FTBFS on s390x
On Tue, 29 Nov 2022, Chris Hofstaedtler wrote: * Sebastian Ramacher [221129 11:21]: Source: cmark-gfm Version: 0.29.0.gfm.6-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=cmark-gfm=s390x=0.29.0.gfm.6-2=1666810004=0 --- expected HTML +++ actual HTML @@ -7,15 +7,15 @@ mailto:scyt...@pokemon.com;>scyt...@pokemon.com/mailto:beedr...@pokemon.com;>beedr...@pokemon.com mailto:scyt...@pokemon.com;>mailto:scyt...@pokemon.com This is a mailto:scyt...@pokemon.com;>mailto:scyt...@pokemon.com -mailto:scyt...@pokemon.com;>mailto:scyt...@pokemon.com. +mailto:mailto:scyt...@pokemon.com;>scyt...@pokemon.com. This is caused by an out-of-bounds read on a memory buffer, which seems to be masked by stack layout on little-endian archs(?). PR for upstream is here: https://github.com/github/cmark-gfm/pull/296/files I've verified on zelenka.d.o this fixes the build failure. Thanks for the fix, Chris! I was trying to look into this myself earlier. @Keith, do you have time to upload this patch? Unfortunately, this is blocking a large number of packages from migrating to testing. Alternatively, any objections to an NMU? Thanks, Scott
Bug#1025025: ImportError: cannot import name 'Application' from 'cleo'
Hi, Thanks for the report. I'm working in the new upstream release of poetry. As you mentioned this will be fixed. Fyi, poetry-core and python-cleo are ready. Cheers, -- Emmanuel OpenPGP_0xFA9DEC5DE11C63F1.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Processed: tagging 1025025
Processing commands for cont...@bugs.debian.org: > tags 1025025 + pending Bug #1025025 [python3-poetry] ImportError: cannot import name 'Application' from 'cleo' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1020178
Processing commands for cont...@bugs.debian.org:
> tags 1020178 + fixed
Bug #1020178 {Done: Lev Lamberov } [src:esup-el] esup-el:
FTBFS: (file-missing "Cannot open load file" "No such file or directory"
"comp")
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: python-pysam ftbfs with python3.11 reduced severity
Processing control commands: > severity -1 important Bug #1024425 [src:python-pysam] python-pysam: FTBFS with Python 3.11 as a supported version Severity set to 'important' from 'serious' -- 1024425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cofoja: diff for NMU version 1.3-4.1
Processing control commands: > tags 1012063 + patch Bug #1012063 [src:cofoja] cofoja: FTBFS with OpenJDK 17: module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module Added tag(s) patch. > tags 1012063 + pending Bug #1012063 [src:cofoja] cofoja: FTBFS with OpenJDK 17: module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module Added tag(s) pending. -- 1012063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024425: python-pysam ftbfs with python3.11 reduced severity
Control: severity -1 important Hi, I just uploaded python-pysam 0.20 with python3-dev support only for the time being. This can be raised later on when python3.11 becomes the default, or a last time when python3.10 is to be dropped. Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#1012063: cofoja: diff for NMU version 1.3-4.1
Control: tags 1012063 + patch
Control: tags 1012063 + pending
Dear maintainer,
I've prepared an NMU for cofoja (versioned as 1.3-4.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru cofoja-1.3/debian/changelog cofoja-1.3/debian/changelog
--- cofoja-1.3/debian/changelog 2018-11-29 23:20:57.0 +0200
+++ cofoja-1.3/debian/changelog 2022-11-29 23:29:31.0 +0200
@@ -1,3 +1,10 @@
+cofoja (1.3-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Backport upstream fix for FTBFS with OpenJDK 17. (Closes: #1012063)
+
+ -- Adrian Bunk Tue, 29 Nov 2022 23:29:31 +0200
+
cofoja (1.3-4) unstable; urgency=medium
* Team upload.
diff -Nru cofoja-1.3/debian/patches/0001-java9-doesn-t-need-tools.jar.patch cofoja-1.3/debian/patches/0001-java9-doesn-t-need-tools.jar.patch
--- cofoja-1.3/debian/patches/0001-java9-doesn-t-need-tools.jar.patch 1970-01-01 02:00:00.0 +0200
+++ cofoja-1.3/debian/patches/0001-java9-doesn-t-need-tools.jar.patch 2022-11-29 23:29:31.0 +0200
@@ -0,0 +1,33 @@
+From a832cc817a3e5a3c3b5ac99b5cf5183f2c987ebb Mon Sep 17 00:00:00 2001
+From: "Chris West (Faux)"
+Date: Wed, 23 Aug 2017 14:46:11 +0100
+Subject: java9 doesn't need tools.jar
+
+---
+ build.xml | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/build.xml b/build.xml
+index 3410f53..e891a96 100644
+--- a/build.xml
b/build.xml
+@@ -209,9 +209,15 @@
+
+
+
+-
++
++
++
++
++
+
++
+
++
+
+
+Date: Thu, 24 Aug 2017 20:58:09 +0100
+Subject: Add configure message if tools.jar is not needed
+
+---
+ build.xml | 15 ++-
+ 1 file changed, 10 insertions(+), 5 deletions(-)
+
+diff --git a/build.xml b/build.xml
+index e891a96..308fcec 100644
+--- a/build.xml
b/build.xml
+@@ -30,6 +30,10 @@
+
+
+
++
++
++
++
+
+
+
+@@ -201,7 +205,12 @@
+
+
+
+-
++
++
++
++
++
++
+
+
+
+@@ -209,10 +218,6 @@
+
+
+
+-
+-
+-
+-
+
+
+
+--
+2.30.2
+
diff -Nru cofoja-1.3/debian/patches/0003-Switch-to-if-unless-set-instead-of-true-for-conditio.patch cofoja-1.3/debian/patches/0003-Switch-to-if-unless-set-instead-of-true-for-conditio.patch
--- cofoja-1.3/debian/patches/0003-Switch-to-if-unless-set-instead-of-true-for-conditio.patch 1970-01-01 02:00:00.0 +0200
+++ cofoja-1.3/debian/patches/0003-Switch-to-if-unless-set-instead-of-true-for-conditio.patch 2022-11-29 23:29:31.0 +0200
@@ -0,0 +1,47 @@
+From fe6d2ac03741ed6722c13b8011b4ae323d05 Mon Sep 17 00:00:00 2001
+From: Nhat Minh Le
+Date: Thu, 24 Aug 2017 21:49:41 +0100
+Subject: Switch to if/unless:set instead of :true for variables
+
+---
+ build.xml | 8
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/build.xml b/build.xml
+index 308fcec..f8f5593 100644
+--- a/build.xml
b/build.xml
+@@ -205,10 +205,10 @@
+
+
+
+-
++
+
+
+-
++
+
+
+
+@@ -316,7 +316,7 @@
+
+
+
+-
++
+
+
+
+@@ -334,7 +334,7 @@
+
+
+
+-
++
+
+
+
+--
+2.30.2
+
diff -Nru cofoja-1.3/debian/patches/0004-Add-add-opens-for-masked-internal-com.sun.tools-APIs.patch cofoja-1.3/debian/patches/0004-Add-add-opens-for-masked-internal-com.sun.tools-APIs.patch
--- cofoja-1.3/debian/patches/0004-Add-add-opens-for-masked-internal-com.sun.tools-APIs.patch 1970-01-01 02:00:00.0 +0200
+++ cofoja-1.3/debian/patches/0004-Add-add-opens-for-masked-internal-com.sun.tools-APIs.patch 2022-11-29 23:29:31.0 +0200
@@ -0,0 +1,85 @@
+From b62618fa472e3f885622f51181256c540e8e8b86 Mon Sep 17 00:00:00 2001
+From: Nhat Minh Le
+Date: Thu, 24 Aug 2017 21:51:07 +0100
+Subject: Add --add-opens for masked internal com.sun.tools APIs in Java 9
+
+---
+ build.xml | 30 +++---
+ default.properties | 1 +
+ 2 files changed, 24 insertions(+), 7 deletions(-)
+
+diff --git a/build.xml b/build.xml
+index f8f5593..540c689 100644
+--- a/build.xml
b/build.xml
+@@ -34,6 +34,15 @@
+
+
+
++
++
++
++
++
++
++
++
++
+
+
+
+@@ -80,8 +89,14 @@
+
+
+
+-
++
+
++
++
++
++
+
+
+
+@@ -203,19 +218,20 @@
+
+
+
+-
++
+
+
+-
++
+
+
+-
++
++
+
+
+-
++
+
+-
+-
++
++
+
+
+
+diff --git a/default.properties b/default.properties
+index ba01f4a..7d413d0 100644
+--- a/default.properties
b/default.properties
+@@ -13,3 +13,4 @@ debug=true
+
+ ## Location of the JDK 'tools.jar' or 'classes.jar' (on Mac OS X).
+ tools.jar=${java.home}/../lib/tools.jar
++add-opens=true
+--
+2.30.2
+
diff -Nru
Processed: python-taskflow: (autopkgtest) needs update for python3.11: MismatchError
Processing control commands: > affects -1 src:python3-defaults Bug #1025126 [src:python-taskflow] python-taskflow: (autopkgtest) needs update for python3.11: MismatchError Added indication that 1025126 affects src:python3-defaults -- 1025126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025126: python-taskflow: (autopkgtest) needs update for python3.11: MismatchError
Source: python-taskflow Version: 5.0.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-taskflow fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-taskflowfrom testing5.0.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-taskflow/28750734/log.gz == FAIL: taskflow.tests.unit.test_utils_iter_utils.IterUtilsTest.test_while_is_not taskflow.tests.unit.test_utils_iter_utils.IterUtilsTest.test_while_is_not -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/tmp/autopkgtest-lxc.96kwtgri/downtmp/build.Po9/src/taskflow/tests/unit/test_utils_iter_utils.py", line 144, in test_while_is_not self.assertEqual(['a'], File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 393, in assertEqual self.assertThat(observed, matcher, message) File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 480, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = ['a'] actual= ['a', 'b', 'c', 'd', 'e', 'f', 'g', 'h', 'i', 'j', 'k', 'l', 'm', 'n', 'o', 'p', 'q', 'r', 's', 't', 'u', 'v', 'w', 'x', 'y', 'z'] -- Ran 1719 tests in 50.317s FAILED (failures=1, skipped=92) OpenPGP_signature Description: OpenPGP digital signature
Bug#1025125: ruby-sinatra: CVE-2022-45442: Reflected File Download attack
Source: ruby-sinatra Version: 2.2.2-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ruby-sinatra. CVE-2022-45442[0]: | Sinatra is a domain-specific language for creating web applications in | Ruby. An issue was discovered in Sinatra 2.0 before 2.2.3 and 3.0 | before 3.0.4. An application is vulnerable to a reflected file | download (RFD) attack that sets the Content-Disposition header of a | response when the filename is derived from user-supplied input. | Version 2.2.3 and 3.0.4 contain patches for this issue. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-45442 https://www.cve.org/CVERecord?id=CVE-2022-45442 [1] https://github.com/sinatra/sinatra/security/advisories/GHSA-2x8x-jmrp-phxw [2] https://github.com/sinatra/sinatra/commit/1808bcdf3424eab0c659ef2d0e85579aab977a1a Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: python-sushy: (autopkgtest) needs update for python3.11: AssertionError: expected call not found
Processing control commands: > affects -1 src:python3-defaults Bug #1025124 [src:python-sushy] python-sushy: (autopkgtest) needs update for python3.11: AssertionError: expected call not found Added indication that 1025124 affects src:python3-defaults -- 1025124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025124: python-sushy: (autopkgtest) needs update for python3.11: AssertionError: expected call not found
Source: python-sushy
Version: 4.3.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-sushy fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-sushy from testing4.3.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-sushy/28750733/log.gz
==
FAIL:
sushy.tests.unit.test_connector.ConnectorOpTestCase.test_access_error_basic_auth
sushy.tests.unit.test_connector.ConnectorOpTestCase.test_access_error_basic_auth
--
testtools.testresult.real._StringException: Traceback (most recent call
last):
File "/usr/lib/python3.11/unittest/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
^
File
"/tmp/autopkgtest-lxc.71ai3cya/downtmp/build.UmE/src/sushy/tests/unit/test_connector.py",
line 554, in test_access_error_basic_auth
mock_log.assert_called_once_with(
File "/usr/lib/python3.11/unittest/mock.py", line 214, in
assert_called_once_with
return mock.assert_called_once_with(*args, **kwargs)
^
File "/usr/lib/python3.11/unittest/mock.py", line 945, in
assert_called_once_with
return self.assert_called_with(*args, **kwargs)
File "/usr/lib/python3.11/unittest/mock.py", line 933, in
assert_called_with
raise AssertionError(_error_message()) from cause
AssertionError: expected call not found.
Expected: warning("We have encountered an AccessError when using 'basic'
authentication. %(err)s", {'err': 'HTTP GET
http://redfish/v1/SessionService returned code HTTPStatus.FORBIDDEN.
unknown error Extended information: none'})
Actual: warning("We have encountered an AccessError when using 'basic'
authentication. %(err)s", {'err': 'HTTP GET
http://redfish/v1/SessionService returned code 403. unknown error
Extended information: none'})
--
Ran 574 tests in 2.995s
FAILED (failures=1)
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1025122: python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Source: python-stone
Version: 3.3.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-stone fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-stone from testing3.3.1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-stone/28750732/log.gz
=== FAILURES
===
__ TestGeneratedPython.test_alias_validators
___
self = testMethod=test_alias_validators>
def setUp(self):
# Sanity check: stone must be importable for the compiler
to work
importlib.import_module('stone')
# Compile spec by calling out to stone
p = subprocess.Popen(
[sys.executable,
'-m',
'stone.cli',
'python_types',
'output',
'-',
'--',
'--package',
'output'],
stdin=subprocess.PIPE,
stderr=subprocess.PIPE)
_, stderr = p.communicate(
input=(test_spec + test_ns2_spec).encode('utf-8'))
if p.wait() != 0:
raise AssertionError('Could not execute stone tool: %s' %
stderr.decode('utf-8'))
E AssertionError: Could not execute stone tool:
/usr/lib/python3/dist-packages/stone/cli.py:8: DeprecationWarning: the
imp module is deprecated in favour of importlib and slated for removal
in Python 3.12; see the module's documentation for alternative uses
E import imp # pylint: disable=deprecated-module
E Traceback (most recent call last):
E File "", line 198, in _run_module_as_main
E File "", line 88, in _run_code
E File "/usr/lib/python3/dist-packages/stone/cli.py", line
380, in
E api = main()
E ^^
E File "/usr/lib/python3/dist-packages/stone/cli.py", line
250, in main
E api = specs_to_ir(specs, debug=debug,
E ^^^
E File
"/usr/lib/python3/dist-packages/stone/frontend/frontend.py", line 55, in
specs_to_ir
E route_whitelist_filter=route_whitelist_filter).generate_IR()
E ^
E File
"/usr/lib/python3/dist-packages/stone/frontend/ir_generator.py", line
297, in generate_IR
E self._populate_type_attributes()
E File
"/usr/lib/python3/dist-packages/stone/frontend/ir_generator.py", line
694, in _populate_type_attributes
E data_type = self._resolve_type(env,
alias._ast_node.type_ref)
E
^
E File
"/usr/lib/python3/dist-packages/stone/frontend/ir_generator.py", line
1159, in _resolve_type
E data_type = self._instantiate_data_type(
E
E File
"/usr/lib/python3/dist-packages/stone/frontend/ir_generator.py", line
1077, in _instantiate_data_type
E argspec = inspect.getargspec(data_type_class.__init__)
# noqa: E501 # pylint: disable=deprecated-method,useless-suppression
E ^^
E AttributeError: module 'inspect' has no attribute
'getargspec'. Did you mean: 'getargs'?
test/test_python_gen.py:838: AssertionError
___ TestGeneratedPython.test_aliases
___
self =
def setUp(self):
# Sanity check: stone must be importable for the compiler
to work
importlib.import_module('stone')
# Compile spec by calling out to stone
p = subprocess.Popen(
[sys.executable,
'-m',
'stone.cli',
'python_types',
'output',
Bug#1025121: python-stack-data: (autopkgtest) needs update for python3.11: AssertionError
Source: python-stack-data
Version: 0.5.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-stack-data fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-stack-data from testing0.5.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-stack-data/28750731/log.gz
=== FAILURES
===
test_variables
def test_variables():
options = Options(before=1, after=0)
assert repr(options) == ('Options(after=0, before=1, ' +
'blank_lines=,' +
' include_signature=False, ' +
'max_lines_per_piece=6,
pygments_formatter=None)')
def foo(arg, _arg2: str = None, *_args, **_kwargs):
y = 123986
str(y)
x = {982347298304}
str(x)
return (
FrameInfo(inspect.currentframe(), options),
arg,
arg,
)[0]
frame_info = foo('this is arg')
assert sum(line.is_current for line in frame_info.lines) == 1
body = frame_info.scope.body
tup = body[-1].value.value.elts
call = tup[0]
assert frame_info.executing.node == call
E AssertionError: assert None ==
E+ where None = 0x7f3677c694d0>.node
E+where 0x7f3677c694d0> = FrameInfo('/tmp/autopkgtest-lxc.0v1rnt08/downtmp/autopkgtest_tmp/tests/test_core.py',
line 219, code foo>).executing
tests/test_core.py:233: AssertionError
_ test_example
_
def test_example():
from .samples.example import bar
result = bar()
print(result)
assert result == """\
bar at line 27
--
25 | def bar():
26 | names = {}
27 > exec("result = foo()", globals(),
names)
28 | return names["result"]
names = {}
at line 1
--
foo at line 20
--
6 | def foo():
(...)
8 | lst = [1]
10 | lst.insert(0, x)
11 | lst.append(
12 | [
13 | 1,
(...)
18 | 6
19 | ][0])
20 > result = print_stack(
21 | )
22 | return result
[
1,
2,
3,
4,
5,
6
][0] = 1
lst = [1, 1, 1]
x = 1
"""
E assert 'bar at line ... \nx = 1 \n\n' == 'bar at line ... \nx =
1 \n\n'
E Skipping 82 identical leading characters in diff, use -v to show
E - 27 > exec("result = foo()", globals(),
names)
E ? --
---
E + 27 > exec("result = foo()", globals(), names)
E 28 | return names["result"]
E names = {} E ...
E E ...Full output truncated (34 lines hidden), use
'-vv' to show
tests/test_core.py:578: AssertionError
- Captured stdout call
-
bar at line 27
--
25 | def bar():
26 | names = {}
27 > exec("result = foo()", globals(), names)
28 | return names["result"]
names = {}
at line 1
--
foo at line 20
--
6 | def foo():
(...)
8 | lst = [1]
10 | lst.insert(0, x)
11 | lst.append(
12 | [
13 | 1,
(...)
18 | 6
19 | ][0])
20 > result = print_stack(
21 | )
22 | return result
[
1,
2,
3,
4,
5,
6
][0] = 1 lst =
Processed: python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Processing control commands: > affects -1 src:python3-defaults Bug #1025122 [src:python-stone] python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' Added indication that 1025122 affects src:python3-defaults -- 1025122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-stack-data: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025121 [src:python-stack-data] python-stack-data: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025121 affects src:python3-defaults -- 1025121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: blocking migration of python3-defaults
Processing commands for cont...@bugs.debian.org: > severity 1024877 serious Bug #1024877 [src:python-softlayer] python-softlayer: tests fail with python 3.11 Severity set to 'serious' from 'important' > user debian-pyt...@lists.debian.org Setting user to debian-pyt...@lists.debian.org (was elb...@debian.org). > usertag 1024877 python3.11 There were no usertags set. Usertags are now: python3.11. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025119: python-ratelimiter: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Source: python-ratelimiter Version: 1.2.0.post0-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-ratelimiter fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-ratelimiter from testing1.2.0.post0-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-ratelimiter/28750383/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/ratelimiter.py", line 36, in class RateLimiter(object): File "/usr/lib/python3/dist-packages/ratelimiter.py", line 127, in RateLimiter __aexit__ = asyncio.coroutine(__exit__) ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? autopkgtest [23:15:36]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Bug#1025118: python-pytest-subtests: (autopkgtest) needs update for python3.11: AssertionError
Source: python-pytest-subtests
Version: 0.8.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-pytest-subtests fails in testing when that autopkgtest is run
with the binary packages of python3-defaults from unstable. It passes
when run with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-pytest-subtests from testing0.8.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pytest-subtests/28750729/log.gz
=== FAILURES
===
__ TestSubTest.test_simple_terminal_normal[unittest]
___
self =
simple_script =
local('/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py')
testdir = local('/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2')>
runner = 'unittest'
@pytest.mark.parametrize("runner", ["unittest", "pytest-normal",
"pytest-xdist"])
def test_simple_terminal_normal(self, simple_script, testdir, runner):
if runner == "unittest":
result = testdir.run(sys.executable, simple_script)
result.stderr.fnmatch_lines(
[
"FAIL: test_foo (__main__.T) [custom] (i=1)",
"AssertionError: 1 != 0",
"FAIL: test_foo (__main__.T) [custom] (i=3)",
"AssertionError: 1 != 0",
"Ran 1 test in *",
"FAILED (failures=2)",
]
)
E Failed: nomatch: 'FAIL: test_foo (__main__.T) [custom] (i=1)'
E and: 'FF'
E and:
'=='
E and: 'FAIL: test_foo (__main__.T.test_foo) [custom] (i=1)'
E and:
'--'
E and: 'Traceback (most recent call last):'
E and: ' File
"/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py",
line 8, in test_foo'
E and: 'self.assertEqual(i % 2, 0)'
E and: 'AssertionError: 1 != 0'
E and: ''
E and:
'=='
E and: 'FAIL: test_foo (__main__.T.test_foo) [custom] (i=3)'
E and:
'--'
E and: 'Traceback (most recent call last):'
E and: ' File
"/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py",
line 8, in test_foo'
E and: 'self.assertEqual(i % 2, 0)'
E and: 'AssertionError: 1 != 0'
E and: ''
E and:
'--'
E and: 'Ran 1 test in 0.001s'
E and: ''
E and: 'FAILED (failures=2)'
E remains unmatched: 'FAIL: test_foo (__main__.T) [custom] (i=1)'
/tmp/autopkgtest-lxc.agke3g8v/downtmp/autopkgtest_tmp/tests/test_subtests.py:142:
Failed
- Captured stdout call
-
running: /usr/bin/python3.11
/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py
in: /tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2
- Captured stderr call
-
FF
==
FAIL: test_foo (__main__.T.test_foo) [custom] (i=1)
--
Traceback (most recent call last):
File
"/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py",
line 8, in test_foo
self.assertEqual(i % 2, 0)
AssertionError: 1 != 0
==
FAIL: test_foo
Processed: python-ratelimiter: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Processing control commands: > affects -1 src:python3-defaults Bug #1025119 [src:python-ratelimiter] python-ratelimiter: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added indication that 1025119 affects src:python3-defaults -- 1025119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-pytest-subtests: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025118 [src:python-pytest-subtests] python-pytest-subtests: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025118 affects src:python3-defaults -- 1025118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025117: python-pyramid: (autopkgtest) needs update for python3.11: 'Translations' object has no attribute 'lgettext'
Source: python-pyramid
Version: 2.0+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-pyramid fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-pyramid from testing2.0+dfsg-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pyramid/28750382/log.gz
=== FAILURES
===
___ TestTranslations.test_ldgettext
self =
def test_ldgettext(self):
t = self._makeOne()
self.assertEqual(t.ldgettext('messages', 'foo'), b'Voh')
tests/test_i18n.py:426: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , domain = 'messages', message = 'foo'
def ldgettext(self, domain, message):
"""Like ``lgettext()``, but look the message up in the specified
domain.
"""
return self._domains.get(domain, self).lgettext(message)
E AttributeError: 'Translations' object has no attribute 'lgettext'
/usr/lib/python3/dist-packages/pyramid/i18n.py:342: AttributeError
___ TestTranslations.test_ldngettext
___
self =
def test_ldngettext(self):
t = self._makeOne()
self.assertEqual(t.ldngettext('messages', 'foo1', 'foos1', 1), b'Voh1')
tests/test_i18n.py:441: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , domain = 'messages', singular = 'foo1'
plural = 'foos1', num = 1
def ldngettext(self, domain, singular, plural, num):
"""Like ``lngettext()``, but look the message up in the specified
domain.
"""
return self._domains.get(domain, self).lngettext(singular, plural, num)
E AttributeError: 'Translations' object has no attribute 'lngettext'
/usr/lib/python3/dist-packages/pyramid/i18n.py:360: AttributeError
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1025116: python-pybedtools: (autopkgtest) needs update for python3.11: No module named 'pysam.libchtslib'
Source: python-pybedtools Version: 0.9.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-pybedtools fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-pybedtools from testing0.9.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pybedtools/28750381/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/pybedtools/__init__.py", line 16, in from . import contrib File "/usr/lib/python3/dist-packages/pybedtools/contrib/__init__.py", line 3, in from . import venn_maker File "/usr/lib/python3/dist-packages/pybedtools/contrib/venn_maker.py", line 11, in from pybedtools import helpers File "/usr/lib/python3/dist-packages/pybedtools/helpers.py", line 12, in import pysam File "/usr/lib/python3/dist-packages/pysam/__init__.py", line 5, in from pysam.libchtslib import * ModuleNotFoundError: No module named 'pysam.libchtslib' autopkgtest [23:15:21]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: python-pyramid: (autopkgtest) needs update for python3.11: 'Translations' object has no attribute 'lgettext'
Processing control commands: > affects -1 src:python3-defaults Bug #1025117 [src:python-pyramid] python-pyramid: (autopkgtest) needs update for python3.11: 'Translations' object has no attribute 'lgettext' Added indication that 1025117 affects src:python3-defaults -- 1025117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-pybedtools: (autopkgtest) needs update for python3.11: No module named 'pysam.libchtslib'
Processing control commands: > affects -1 src:python3-defaults Bug #1025116 [src:python-pybedtools] python-pybedtools: (autopkgtest) needs update for python3.11: No module named 'pysam.libchtslib' Added indication that 1025116 affects src:python3-defaults -- 1025116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-phx-class-registry: (autopkgtest) needs update for python3.11: python3.11: command not found
Processing control commands: > affects -1 src:python3-defaults Bug #1025115 [src:python-phx-class-registry] python-phx-class-registry: (autopkgtest) needs update for python3.11: python3.11: command not found Added indication that 1025115 affects src:python3-defaults -- 1025115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025115: python-phx-class-registry: (autopkgtest) needs update for python3.11: python3.11: command not found
Source: python-phx-class-registry Version: 3.0.5-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-phx-class-registry fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-phx-class-registry from testing3.0.5-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-phx-class-registry/28750380/log.gz [*] testing on python3.11: bash: line 1: python3.11: command not found autopkgtest [23:15:16]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1025114: python-parameterized: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Source: python-parameterized Version: 0.8.1-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-parameterized fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-parameterized from testing0.8.1-5 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-parameterized/28750379/log.gz == ERROR: test suite for '/usr/lib/python3/dist-packages/parameterized/test.py'> -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/suite.py", line 228, in run self.tearDown() File "/usr/lib/python3/dist-packages/nose/suite.py", line 351, in tearDown self.teardownContext(ancestor) File "/usr/lib/python3/dist-packages/nose/suite.py", line 367, in teardownContext try_run(context, names) File "/usr/lib/python3/dist-packages/nose/util.py", line 453, in try_run inspect.getargspec(func) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' -- Ran 96 tests in 0.045s FAILED (SKIP=1, errors=1) autopkgtest [23:15:24]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Processed: python-parameterized: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Processing control commands: > affects -1 src:python3-defaults Bug #1025114 [src:python-parameterized] python-parameterized: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' Added indication that 1025114 affects src:python3-defaults -- 1025114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-os-win: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Processing control commands: > affects -1 src:python3-defaults Bug #1025112 [src:python-os-win] python-os-win: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' Added indication that 1025112 affects src:python3-defaults -- 1025112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025112: python-os-win: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Source: python-os-win Version: 5.7.1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-os-win fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-os-win from testing5.7.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-os-win/28750378/log.gz == FAIL: os_win.tests.unit.test_utilsfactory.TestHyperVUtilsFactory.test_utils_public_signatures os_win.tests.unit.test_utilsfactory.TestHyperVUtilsFactory.test_utils_public_signatures -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/tmp/autopkgtest-lxc.f4g2jevo/downtmp/build.Pwx/src/os_win/tests/unit/test_utilsfactory.py", line 167, in test_utils_public_signatures self.assertPublicAPISignatures(base_class, tested_class) File "/tmp/autopkgtest-lxc.f4g2jevo/downtmp/build.Pwx/src/os_win/tests/unit/test_utilsfactory.py", line 189, in assertPublicAPISignatures baseargs = inspect.getargspec(basemethods[name]) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' OpenPGP_signature Description: OpenPGP digital signature
Processed: python-omegaconf: (autopkgtest) needs update for python3.11: mutable default for field params is not allowed
Processing control commands: > affects -1 src:python3-defaults Bug #1025111 [src:python-omegaconf] python-omegaconf: (autopkgtest) needs update for python3.11: mutable default for field params is not allowed Added indication that 1025111 affects src:python3-defaults -- 1025111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025111: python-omegaconf: (autopkgtest) needs update for python3.11: mutable default for field params is not allowed
Source: python-omegaconf
Version: 2.2.2-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-omegaconf fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-omegaconf from testing2.2.2-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-omegaconf/28750377/log.gz
+
PYTHONPATH=/tmp/autopkgtest-lxc.4vq75_au/downtmp/build.XHu/src/debian/tmp/usr/lib/python3/dist-packages
http_proxy=127.0.0.1:9 https_proxy=127.0.0.9:9 HTTP_PROXY=127.0.0.1:9
HTTPS_PROXY=127.0.0.1:9 PYTHON=python3.11 python3.11 -m pytest tests -v
ImportError while loading conftest
'/tmp/autopkgtest-lxc.4vq75_au/downtmp/build.XHu/src/tests/conftest.py'.
tests/__init__.py:96: in
@dataclass
/usr/lib/python3.11/dataclasses.py:1220: in dataclass
return wrap(cls)
/usr/lib/python3.11/dataclasses.py:1210: in wrap
return _process_class(cls, init, repr, eq, order, unsafe_hash,
/usr/lib/python3.11/dataclasses.py:958: in _process_class
cls_fields.append(_get_field(cls, name, type, kw_only))
/usr/lib/python3.11/dataclasses.py:815: in _get_field
raise ValueError(f'mutable default {type(f.default)} for field '
E ValueError: mutable default 'tests.ConcretePlugin.FoobarParams'> for field params is not allowed:
use default_factory
autopkgtest [23:15:46]: test unittests
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1025110: python-novaclient: (autopkgtest) needs update for python3.11: conflicting subparser
Source: python-novaclient
Version: 2:18.1.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-novaclient fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-novaclient from testing2:18.1.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-novaclient/28750728/log.gz
==
FAIL:
novaclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_actions_with_versioned_args
novaclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_actions_with_versioned_args
--
testtools.testresult.real._StringException: Traceback (most recent call
last):
File "/usr/lib/python3.11/unittest/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
^
File
"/tmp/autopkgtest-lxc.8wmmwvjy/downtmp/build.5yv/src/novaclient/tests/unit/test_shell.py",
line 920, in test_load_actions_with_versioned_args
shell._find_actions(subparsers, fake_actions_module,
File
"/tmp/autopkgtest-lxc.8wmmwvjy/downtmp/build.5yv/src/novaclient/shell.py",
line 450, in _find_actions
subparser = subparsers.add_parser(
^^
File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument : conflicting subparser:
another-fake-action
==
FAIL:
novaclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_versioned_actions
novaclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_versioned_actions
--
testtools.testresult.real._StringException: Traceback (most recent call
last):
File
"/tmp/autopkgtest-lxc.8wmmwvjy/downtmp/build.5yv/src/novaclient/tests/unit/test_shell.py",
line 800, in test_load_versioned_actions
shell._find_actions(subparsers, fake_actions_module,
File
"/tmp/autopkgtest-lxc.8wmmwvjy/downtmp/build.5yv/src/novaclient/shell.py",
line 450, in _find_actions
subparser = subparsers.add_parser(
^^
File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument : conflicting subparser:
another-fake-action
OpenPGP_signature
Description: OpenPGP digital signature
Processed: python-novaclient: (autopkgtest) needs update for python3.11: conflicting subparser
Processing control commands: > affects -1 src:python3-defaults Bug #1025110 [src:python-novaclient] python-novaclient: (autopkgtest) needs update for python3.11: conflicting subparser Added indication that 1025110 affects src:python3-defaults -- 1025110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-marshmallow-dataclass: (autopkgtest) needs update for python3.11: ValueError: mutable default for field data is not allowed
Processing control commands: > affects -1 src:python3-defaults Bug #1025108 [src:python-marshmallow-dataclass] python-marshmallow-dataclass: (autopkgtest) needs update for python3.11: ValueError: mutable default for field data is not allowed Added indication that 1025108 affects src:python3-defaults -- 1025108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-memory-profiler: (autopkgtest) needs update for python3.11: cannot import name 'coroutine' from 'asyncio'
Processing control commands: > affects -1 src:python3-defaults Bug #1025109 [src:python-memory-profiler] python-memory-profiler: (autopkgtest) needs update for python3.11: cannot import name 'coroutine' from 'asyncio' Added indication that 1025109 affects src:python3-defaults -- 1025109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025109: python-memory-profiler: (autopkgtest) needs update for python3.11: cannot import name 'coroutine' from 'asyncio'
Source: python-memory-profiler Version: 0.60-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-memory-profiler fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-memory-profiler from testing0.60-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-memory-profiler/28750375/log.gz Testing with python3.11: python3.11 -m memory_profiler test/test_func.py Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/lib/python3/dist-packages/memory_profiler.py", line 10, in from asyncio import coroutine, iscoroutinefunction ImportError: cannot import name 'coroutine' from 'asyncio' (/usr/lib/python3.11/asyncio/__init__.py) make: *** [Makefile:6: test] Error 1 autopkgtest [23:14:56]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1025108: python-marshmallow-dataclass: (autopkgtest) needs update for python3.11: ValueError: mutable default for field data is not allowed
Source: python-marshmallow-dataclass
Version: 8.5.8-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-marshmallow-dataclass fails in testing when that autopkgtest is
run with the binary packages of python3-defaults from unstable. It
passes when run with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-marshmallow-dataclass from testing8.5.8-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-marshmallow-dataclass/28750374/log.gz
=== FAILURES
===
_ TestClassSchema.test_final_infers_type_from_default
__
self = testMethod=test_final_infers_type_from_default>
def test_final_infers_type_from_default(self):
# @dataclasses.dataclass
class A:
data: Final = "a"
# @dataclasses.dataclass
class B:
data: Final = A()
# NOTE: This workaround is needed to avoid a Mypy crash.
# See:
https://github.com/python/mypy/issues/10090#issuecomment-865971891
if not TYPE_CHECKING:
A = dataclasses.dataclass(A)
B = dataclasses.dataclass(B)
tests/test_class_schema.py:242: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.11/dataclasses.py:1220: in dataclass
return wrap(cls)
/usr/lib/python3.11/dataclasses.py:1210: in wrap
return _process_class(cls, init, repr, eq, order, unsafe_hash,
/usr/lib/python3.11/dataclasses.py:958: in _process_class
cls_fields.append(_get_field(cls, name, type, kw_only))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
cls = 'tests.test_class_schema.TestClassSchema.test_final_infers_type_from_default..B'>
a_name = 'data', a_type = typing.Final, default_kw_only = False
def _get_field(cls, a_name, a_type, default_kw_only):
# Return a Field object for this field name and type.
ClassVars and
# InitVars are also returned, but marked as such (see
f._field_type).
# default_kw_only is the value of kw_only to use if there isn't
a field()
# that defines it.
# If the default value isn't derived from Field, then it's
only a
# normal default value. Convert it to a Field().
default = getattr(cls, a_name, MISSING)
if isinstance(default, Field):
f = default
else:
if isinstance(default, types.MemberDescriptorType):
# This is a field in __slots__, so it has no default value.
default = MISSING
f = field(default=default)
# Only at this point do we know the name and the type. Set
them.
f.name = a_name
f.type = a_type
# Assume it's a normal field until proven otherwise. We're
next
# going to decide if it's a ClassVar or InitVar, everything else
# is just a normal field.
f._field_type = _FIELD
# In addition to checking for actual types here, also check for
# string annotations. get_type_hints() won't always work for us
# (see https://github.com/python/typing/issues/508 for example),
# plus it's expensive and would require an eval for every string
# annotation. So, make a best effort to see if this is a ClassVar
# or InitVar using regex's and checking that the thing referenced
# is actually of the correct type.
# For the complete discussion, see
https://bugs.python.org/issue33453
# If typing has not been imported, then it's impossible for any
# annotation to be a ClassVar. So, only look for ClassVar if
# typing has been imported by any module (not necessarily cls's
# module).
typing = sys.modules.get('typing')
if typing:
if (_is_classvar(a_type, typing)
or (isinstance(f.type, str)
and _is_type(f.type, cls, typing, typing.ClassVar,
Bug#1025107: python-limits: (autopkgtest) needs update for python3.11: AssertionError
Source: python-limits Version: 2.7.0-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-limits fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-limits from testing2.7.0-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-limits/28750372/log.gz Traceback (most recent call last): File "/tmp/autopkgtest-lxc.mnkehych/downtmp/autopkgtest_tmp/memcached_storage.py", line 12, in assert True == fixed_window.hit(one_per_second, "test_namespace", "foo") AssertionError autopkgtest [23:14:41]: test python3-tests OpenPGP_signature Description: OpenPGP digital signature
Processed: python-limits: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025107 [src:python-limits] python-limits: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025107 affects src:python3-defaults -- 1025107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-icecream: (autopkgtest) needs update for python3.11: ValueError: not enough values to unpack (expected 2, got 1)
Processing control commands: > affects -1 src:python3-defaults Bug #1025106 [src:python-icecream] python-icecream: (autopkgtest) needs update for python3.11: ValueError: not enough values to unpack (expected 2, got 1) Added indication that 1025106 affects src:python3-defaults -- 1025106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025106: python-icecream: (autopkgtest) needs update for python3.11: ValueError: not enough values to unpack (expected 2, got 1)
Source: python-icecream
Version: 2.1.3-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-icecream fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-icecreamfrom testing2.1.3-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-icecream/28750371/log.gz
FFF.EE.EFEFFEEF.E.FF.FFFEFE
==
ERROR: testComments (tests.test_icecream.TestIceCream.testComments)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 291, in testComments
assert lineIsContextAndTime(err.getvalue())
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 115, in lineIsContextAndTime
context, time = line.split(' at ')
^
ValueError: not enough values to unpack (expected 2, got 1)
==
ERROR: testComplicated (tests.test_icecream.TestIceCream.testComplicated)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 308, in testComplicated
assert lineIsContextAndTime(err.getvalue().splitlines()[0])
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 115, in lineIsContextAndTime
context, time = line.split(' at ')
^
ValueError: not enough values to unpack (expected 2, got 1)
==
ERROR: testContextAbsPathMultiLine
(tests.test_icecream.TestIceCream.testContextAbsPathMultiLine)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 502, in testContextAbsPathMultiLine
assert lineIsAbsPathContext(firstLine)
^^^
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 142, in lineIsAbsPathContext
int(lineNumber) > 0 and
^^^
ValueError: invalid literal for int() with base 10: ' Failed to access
the underlying source code for analysis. Was ic() invoked'
==
ERROR: testDifferentName
(tests.test_icecream.TestIceCream.testDifferentName)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 323, in testDifferentName
assert lineIsContextAndTime(err.getvalue())
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 115, in lineIsContextAndTime
context, time = line.split(' at ')
^
ValueError: not enough values to unpack (expected 2, got 1)
==
ERROR: testFormat (tests.test_icecream.TestIceCream.testFormat)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/tests/test_icecream.py",
line 511, in testFormat
"""comment"""; noop(); s = ic.format( # noqa
^^
File
"/tmp/autopkgtest-lxc.hwa09bp6/downtmp/build.H96/src/icecream/icecream.py",
line 225, in format
out = self._format(callFrame, *args)
Bug#1025105: python-hypothesis: (autopkgtest) needs update for python3.11: AssertionError
Source: python-hypothesis Version: 6.36.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-hypothesis fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-hypothesis from testing6.36.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-hypothesis/28750370/log.gz ImportError while loading conftest '/tmp/autopkgtest-lxc.t_1nxhv7/downtmp/build.qdA/src/hypothesis-python/tests/conftest.py'. tests/conftest.py:39: in assert sys.version_info.releaselevel == "alpha" E AssertionError autopkgtest [23:14:38]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Processed: python-hypothesis: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025105 [src:python-hypothesis] python-hypothesis: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025105 affects src:python3-defaults -- 1025105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-h2: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025103 [src:python-h2] python-h2: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025103 affects src:python3-defaults -- 1025103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025103: python-h2: (autopkgtest) needs update for python3.11: AssertionError
Source: python-h2
Version: 4.1.0-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-h2 fails in testing when that autopkgtest is run with the binary
packages of python3-defaults from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-h2 from testing4.1.0-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-h2/28750369/log.gz
=== FAILURES
===
TestEventReprs.test_remotesettingschanged_repr
self =
def test_remotesettingschanged_repr(self):
"""
RemoteSettingsChanged has a useful debug representation.
"""
e = h2.events.RemoteSettingsChanged()
e.changed_settings = {
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE:
h2.settings.ChangedSetting(
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE,
2**16, 2**15
),
}
> assert repr(e) == (
""setting=SettingCodes.INITIAL_WINDOW_SIZE,
original_value=65536, "
"new_value=32768)}>"
)
E AssertionError: assert '' ==
''
E Skipping 54 identical leading characters in diff, use -v to show
E - g(setting=SettingCodes.INITIAL_WINDOW_SIZE,
original_value=65536, new_value=32768)}>
E ?
E + g(setting=4, original_value=65536, new_value=32768)}>
E ? ^
test/test_events.py:210: AssertionError
_ TestEventReprs.test_streamreset_repr
_
self =
def test_streamreset_repr(self):
"""
StreamEnded has a useful debug representation.
"""
e = h2.events.StreamReset()
e.stream_id = 919
e.error_code = h2.errors.ErrorCodes.ENHANCE_YOUR_CALM
e.remote_reset = False
> assert repr(e) == (
""
)
E AssertionError: assert '' ==
''
E - error_code:ErrorCodes.ENHANCE_YOUR_CALM, remote_reset:False>
E ?
E +
E ?^^
test/test_events.py:252: AssertionError
TestEventReprs.test_settingsacknowledged_repr
_
self =
def test_settingsacknowledged_repr(self):
"""
SettingsAcknowledged has a useful debug representation.
"""
e = h2.events.SettingsAcknowledged()
e.changed_settings = {
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE:
h2.settings.ChangedSetting(
h2.settings.SettingCodes.INITIAL_WINDOW_SIZE,
2**16, 2**15
),
}
> assert repr(e) == (
""setting=SettingCodes.INITIAL_WINDOW_SIZE,
original_value=65536, "
"new_value=32768)}>"
)
E AssertionError: assert '' ==
''
E Skipping 53 identical leading characters in diff, use -v to show
E - g(setting=SettingCodes.INITIAL_WINDOW_SIZE,
original_value=65536, new_value=32768)}>
E ?
E + g(setting=4, original_value=65536, new_value=32768)}>
E ? ^
test/test_events.py:287: AssertionError
___ TestEventReprs.test_connectionterminated_repr[None-None]
___
self =
additional_data = None, data_repr = 'None'
@pytest.mark.parametrize("additional_data,data_repr", [
(None, "None"),
(b'some data', "736f6d652064617461")
])
def test_connectionterminated_repr(self, additional_data, data_repr):
"""
ConnectionTerminated has a useful debug representation.
"""
e = h2.events.ConnectionTerminated()
e.error_code = h2.errors.ErrorCodes.INADEQUATE_SECURITY
e.last_stream_id = 33
e.additional_data = additional_data
> assert repr(e) == (
Bug#1025102: python-gbulb: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Source: python-gbulb Version: 0.6.1-0.1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-gbulb fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-gbulb from testing0.6.1-0.1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-gbulb/28750368/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/gbulb/__init__.py", line 1, in from .glib_events import * File "/usr/lib/python3/dist-packages/gbulb/glib_events.py", line 227, in class GLibBaseEventLoop(_BaseEventLoop, GLibBaseEventLoopPlatformExt): File "/usr/lib/python3/dist-packages/gbulb/glib_events.py", line 320, in GLibBaseEventLoop @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? autopkgtest [23:14:08]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: python-gbulb: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Processing control commands: > affects -1 src:python3-defaults Bug #1025102 [src:python-gbulb] python-gbulb: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added indication that 1025102 affects src:python3-defaults -- 1025102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1024998 in 0.4.2-2, found 1024998 in 0.4.2-1
Processing commands for cont...@bugs.debian.org:
> found 1024998 0.4.2-2
Bug #1024998 {Done: Stephen Kitt } [g810-led] g810-led:
Security risk: Leaves /dev/input/event* with read and write permissions for all
users
Marked as found in versions g810-led/0.4.2-2.
> found 1024998 0.4.2-1
Bug #1024998 {Done: Stephen Kitt } [g810-led] g810-led:
Security risk: Leaves /dev/input/event* with read and write permissions for all
users
Marked as found in versions g810-led/0.4.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#937049: mini-buildd: Python2 removal in sid/bullseye
Why don't you move the experimental to unstable now? The unstable mini.buildd version is not usable but is now the last reverse dependency of python-setuptools (sphinx and nuitka only have it as optional alternatives).
Processed: src:racon: fails to migrate to testing for too long: Build-Depends not available on 32 bits
Processing control commands: > close -1 1.5.0-3 Bug #1025100 [src:racon] src:racon: fails to migrate to testing for too long: Build-Depends not available on 32 bits Marked as fixed in versions racon/1.5.0-3. Bug #1025100 [src:racon] src:racon: fails to migrate to testing for too long: Build-Depends not available on 32 bits Marked Bug as done -- 1025100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025100: src:racon: fails to migrate to testing for too long: Build-Depends not available on 32 bits
Source: racon Version: 1.5.0-2 Severity: serious Control: close -1 1.5.0-3 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:racon has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on 32 bits architectures, and since than the build dependency isn't even available anymore there. You either need to fix libthread-pool-dev on 32 bits architectures or have racon binaries removed from the architectures where libthread-pool-dev doesn't build. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=racon OpenPGP_signature Description: OpenPGP digital signature
Bug#1025096: nanoc: FTBFS in bullseye, and will also FTBFS in bookworm next year
Package: src:nanoc
Version: 4.11.23-1
Severity: serious
Tags: ftbfs, patch
Dear maintainer:
During a rebuild of all packages in bullseye I noticed that this package
does not build from source anymore:
1) Nanoc::Core has up-to-date version information
Failure/Error: expect(described_class.version_information).to
match(/–#{current_year} /)
expected "Nanoc 4.11.23 © 2007–2021 Denis Defreyne.\nRunning
ruby 2.7.4 (2021-07-07) on x86_64-linux-gnu with RubyGems 3.2.5.\n" to
match /–2022 /
Diff:
@@ -1,2 +1,3 @@
-/–2022 /
+Nanoc 4.11.23 © 2007–2021 Denis Defreyne.
+Running ruby 2.7.4 (2021-07-07) on x86_64-linux-gnu with
RubyGems 3.2.5.
This happens because there is a test which expects the current year to
be equal to 2021, which naturally fails now that we are in 2022, and
will fail forever from now on.
I include a trivial patch to disable the test in bullseye.
Note also that the current version in testing/unstable also has the bug
in "latent state", as it will fail from 2023 onwards. To check this, try
building the package after setting current_year to 2023 as in
poc.diff.txt and you will see what happens next year.
Thanks.
[ p.s. I'm having a dejavu. Didn't I report something like this a few
years ago? ]--- a/nanoc-core/spec/nanoc/core_spec.rb
+++ b/nanoc-core/spec/nanoc/core_spec.rb
@@ -3,8 +3,8 @@
require 'nanoc/version'
describe Nanoc::Core do
- it 'has up-to-date version information' do
-current_year = Date.today.year
-expect(described_class.version_information).to match(/–#{current_year} /)
- end
+# it 'has up-to-date version information' do
+#current_year = Date.today.year
+#expect(described_class.version_information).to match(/–#{current_year} /)
+# end
end
--- a/nanoc-core/spec/nanoc/core_spec.rb
+++ b/nanoc-core/spec/nanoc/core_spec.rb
@@ -4,7 +4,7 @@ require 'nanoc/version'
describe Nanoc::Core do
it 'has up-to-date version information' do
-current_year = Date.today.year
+current_year = 2023
expect(described_class.version_information).to match(/–#{current_year} /)
end
end
Bug#1024318: gv: x11 output driver not found
It has also been reported here (not really a ghostview bug I think): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023330
Bug#932345: profile-sync-daemon: Debian specific error "I require modinfo but it's not installed"
Hi, On Mon, May 25, 2020 at 5:13 PM Shengjing Zhu wrote: > > Control: forward -1 > https://github.com/graysky2/profile-sync-daemon/commit/25d6e40c8cb7d126e5cc4a05263133158156a2f7 > Control: tags -1 + fixed-upstream I've uploaded NMU to delay/5, with the above path applied. Please tell me if you don't want that. -- Shengjing Zhu
Processed: bug 932345 is forwarded to https://github.com/graysky2/profile-sync-daemon/commit/25d6e4 ...
Processing commands for cont...@bugs.debian.org: > forwarded 932345 > https://github.com/graysky2/profile-sync-daemon/commit/25d6e40c8cb7d126e5cc4a05263133158156a2f7 Bug #932345 [profile-sync-daemon] profile-sync-daemon: Debian specific error "I require modinfo but it's not installed" Set Bug forwarded-to-address to 'https://github.com/graysky2/profile-sync-daemon/commit/25d6e40c8cb7d126e5cc4a05263133158156a2f7'. > severity 932345 serious Bug #932345 [profile-sync-daemon] profile-sync-daemon: Debian specific error "I require modinfo but it's not installed" Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 932345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025029: python-docutils: (autopkgtest) needs update for python3.11: 'NoneType' object is not subscriptable
Hi Stuart! On Wed, Nov 30, 2022 at 12:36:29AM +1100, Stuart Prescott wrote: > Version: 0.19+dfsg-2 > > The failing test in python-docutils in sid is fixed in the version in > experimental. Can the 0.19 release be uploaded to sid, or does the fix need > to be backported? Unfortunately this is blocked by sphinx-rtd-theme which still does not support docutils 0.18 or 0.19: - https://github.com/readthedocs/sphinx_rtd_theme/issues/1302 - https://github.com/readthedocs/sphinx_rtd_theme/issues/1322 - https://github.com/readthedocs/sphinx_rtd_theme/pull/1336 - https://github.com/readthedocs/sphinx_rtd_theme/pull/1381 (Also blocked by Sphinx, but it's blocked by sphinx-rtd-theme too.) I will try to identify fixes and cherry-pick them to 0.18. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: rm fbpanel
Processing commands for cont...@bugs.debian.org: > retitle 1022932 RM: fbpanel -- RoQA; p2 leftover; dead upstream; unmaintained Bug #1022932 [src:fbpanel] Should fbpanel be removed? Changed Bug title to 'RM: fbpanel -- RoQA; p2 leftover; dead upstream; unmaintained' from 'Should fbpanel be removed?'. > reassign 1022932 ftp.debian.org Bug #1022932 [src:fbpanel] RM: fbpanel -- RoQA; p2 leftover; dead upstream; unmaintained Bug reassigned from package 'src:fbpanel' to 'ftp.debian.org'. No longer marked as found in versions fbpanel/7.0-4.3. Ignoring request to alter fixed versions of bug #1022932 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 1022932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932820: marked as done (vanguards: Migrate to PyPy3 (Python 3))
Your message dated Tue, 29 Nov 2022 14:42:03 +
with message-id
and subject line Bug#932820: fixed in vanguards 0.3.1-2.3
has caused the Debian Bug report #932820,
regarding vanguards: Migrate to PyPy3 (Python 3)
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.)
--
932820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vanguards
Version: 0.3.1-1
Severity: normal
Hi,
please use Python 3 instead of PyPy, because we are going to remove
unsupported PyPy.
Debdiff attached.
Thanks.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_SOFTLOCKUP
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8),
LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vanguards depends on:
pn pypy
pn pypy-ipaddress
pn pypy-setuptools
pn pypy-stem
pn tor
vanguards recommends no packages.
vanguards suggests no packages.
diff -Nru vanguards-0.3.1/debian/control vanguards-0.3.1/debian/control
--- vanguards-0.3.1/debian/control 2019-02-06 20:10:43.0 +0100
+++ vanguards-0.3.1/debian/control 2019-07-23 18:29:04.0 +0200
@@ -6,11 +6,10 @@
Build-Depends: debhelper (>= 11),
dh-exec,
dh-python,
- pypy,
- pypy-setuptools,
- pypy-stem (>= 1.6.0-3.1),
- pypy-pytest,
- pypy-ipaddress
+ python3,
+ python3-setuptools,
+ python3-stem (>= 1.6.0-3.1),
+ python3-pytest,
Standards-Version: 4.1.5
Vcs-Browser: https://github.com/mikeperry-tor/vanguards
Vcs-Git: https://github.com/mikeperry-tor/vanguards
@@ -19,8 +18,7 @@
Package: vanguards
Architecture: all
Depends: ${misc:Depends},
- ${pypy:Depends},
- pypy-ipaddress,
+ ${python3:Depends},
tor
Description: Additional protections for Tor Onion Services
vanguards uses the Stem Tor control port library to connect to a Tor control
diff -Nru vanguards-0.3.1/debian/changelog vanguards-0.3.1/debian/changelog
--- vanguards-0.3.1/debian/changelog2019-05-28 11:15:00.0 +0200
+++ vanguards-0.3.1/debian/changelog2019-07-23 18:32:54.0 +0200
@@ -1,3 +1,10 @@
+vanguards (0.3.1-2) UNRELEASED; urgency=medium
+
+ * Use Python 3 instead of PyPy, because we are going to remove unsupported
+PyPy
+
+ -- Ondřej Nový Tue, 23 Jul 2019 18:32:54 +0200
+
vanguards (0.3.1-1) unstable; urgency=medium
* New upstream version 0.3.1
diff -Nru vanguards-0.3.1/debian/rules vanguards-0.3.1/debian/rules
--- vanguards-0.3.1/debian/rules2019-02-06 20:09:54.0 +0100
+++ vanguards-0.3.1/debian/rules2019-07-23 18:25:20.0 +0200
@@ -1,7 +1,7 @@
#!/usr/bin/make -f
%:
- dh $@ --with pypy --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
--- End Message ---
--- Begin Message ---
Source: vanguards
Source-Version: 0.3.1-2.3
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
vanguards, 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 932...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann (supplier of updated vanguards package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Nov 2022 09:34:36 +0100
Source: vanguards
Architecture: source
Version: 0.3.1-2.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers
Changed-By: Bastian Germann
Closes: 932820 970316
Changes:
vanguards (0.3.1-2.3) unstable; urgency=medium
.
* Non-maintainer upload.
* Remove irl from Uploaders (Closes: #970316)
* Migrate to Python 3
Processed: notforwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 978079 Bug #978079 [ftp.debian.org] RM: rawkit -- RoQA; pypy leftover; non-functional; dead upstream; no rdeps Unset Bug forwarded-to-address > End of message, stopping processing here. Please contact me if you need assistance. -- 978079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1022307, tagging 938249, tagging 1020729, fixed 682836 in 0.3.1-3, tagging 673406 ...
Processing commands for cont...@bugs.debian.org:
> tags 1022307 - sid bookworm
Bug #1022307 [src:python-biopython] python-biopython: FTBFS: tests choke on
t_coffee
Removed tag(s) bookworm and sid.
> tags 938249 - bullseye
Bug #938249 {Done: Micha Lenk } [src:python-virtualenv]
python-virtualenv: Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 1020729 + sid bookworm experimental
Bug #1020729 {Done: Carsten Schoenert } [src:quart]
autopkgtest failure with python-werkzeug 2.2.2
Added tag(s) experimental, bookworm, and sid.
> fixed 682836 0.3.1-3
Bug #682836 {Done: Thomas Goirand } [python-greenlet] keystone
does not start up
There is no source info for the package 'python-greenlet' at version '0.3.1-3'
with architecture ''
Unable to make a source version for version '0.3.1-3'
Marked as fixed in versions 0.3.1-3.
> tags 673406 + sid bookworm
Bug #673406 [dnprogs] Shouldn't be a native Debian package
Added tag(s) bookworm and sid.
> tags 1025029 - bookworm sid
Bug #1025029 {Done: Stuart Prescott } [src:python-docutils]
python-docutils: (autopkgtest) needs update for python3.11: 'NoneType' object
is not subscriptable
Removed tag(s) sid and bookworm.
> tags 1021857 - sid bookworm
Bug #1021857 {Done: Sylvestre Ledru } [llvm-14-dev]
llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov"
references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022334 {Done: Sylvestre Ledru } [llvm-14-dev]
qtcreator: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_configure]
Error 2
Bug #1022337 {Done: Sylvestre Ledru } [llvm-14-dev]
qt6-tools: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022349 {Done: Sylvestre Ledru } [llvm-14-dev] iwyu:
FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
Bug #1022351 {Done: Sylvestre Ledru } [llvm-14-dev]
bpfcc: FTBFS: make[1]: *** [debian/rules:35: override_dh_auto_configure] Error 2
Bug #1022353 {Done: Sylvestre Ledru } [llvm-14-dev]
doxygen: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
Bug #1022366 {Done: Sylvestre Ledru } [llvm-14-dev]
irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 2
Bug #1022375 {Done: Sylvestre Ledru } [llvm-14-dev]
halide: FTBFS: make[2]: *** [debian/rules:97: perform_stage_build] Error 2
Bug #1022381 {Done: Sylvestre Ledru } [llvm-14-dev]
cvise: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2
Bug #1022409 {Done: Sylvestre Ledru } [llvm-14-dev] ccls:
FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2
Bug #1022414 {Done: Sylvestre Ledru } [llvm-14-dev]
bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure]
Error 2
Removed tag(s) sid and bookworm.
Removed tag(s) sid and bookworm.
Removed tag(s) sid and bookworm.
Removed tag(s) sid and bookworm.
Removed tag(s) bookworm and sid.
Removed tag(s) bookworm and sid.
Removed tag(s) bookworm and sid.
Removed tag(s) bookworm and sid.
Removed tag(s) bookworm and sid.
Removed tag(s) bookworm and sid.
Removed tag(s) sid and bookworm.
> tags 1025063 + sid bookworm
Bug #1025063 [src:gnomekiss] gnomekiss FTBFS: Makefile:262: *** missing
separator. Stop.
Added tag(s) bookworm and sid.
> tags 938322 + experimental
Bug #938322 {Done: Dmitry Shachnev }
[src:qtwebengine-opensource-src] qtwebengine-opensource-src: Python2 removal in
sid/bullseye
Added tag(s) experimental.
> tags 1021559 + experimental
Bug #1021559 {Done: Paul Gevers } [src:u-boot] src:u-boot:
fails to migrate to testing for too long: unresolved RC bug
Added tag(s) experimental.
> tags 994510 + experimental
Bug #994510 [libunwind8] libunwind8 abuses setcontext() causing SIGSEGV on i386
with glibc >= 2.32
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020729
1021559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021559
1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857
1022307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022307
1022334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022334
1022337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022337
1022349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022349
1022351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022351
1022353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022353
1022366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022366
1022375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022375
1022381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022381
1022409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022409
1022414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022414
1025029:
Processed: RM rawkit
Processing commands for cont...@bugs.debian.org: > retitle 978079 RM: rawkit -- RoQA; pypy leftover; non-functional; dead > upstream; no rdeps Bug #978079 [python3-rawkit] python3-rawkit: Support for libraw20 missing Changed Bug title to 'RM: rawkit -- RoQA; pypy leftover; non-functional; dead upstream; no rdeps' from 'python3-rawkit: Support for libraw20 missing'. > block 1011926 by 978079 Bug #1011926 [pypy] pypy shouldn't be shipped in bookworm 1011926 was blocked by: 983470 937510 1019975 938168 932820 1018738 1019976 1011926 was not blocking any bugs. Added blocking bug(s) of 1011926: 978079 > reassign 978079 ftp.debian.org Bug #978079 [python3-rawkit] RM: rawkit -- RoQA; pypy leftover; non-functional; dead upstream; no rdeps Bug reassigned from package 'python3-rawkit' to 'ftp.debian.org'. No longer marked as found in versions rawkit/0.6.0-2. Ignoring request to alter fixed versions of bug #978079 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 1011926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011926 978079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024154: llvm-toolchain-14: FTBFS: testsuite hangs on i386, x32
Hi, I see a -9 changelog entry (in the -10~exp1 upload) that disabled the hanging tests, but no such package has reached the archive, yet. Andreas
Bug#1024857: marked as done (beaker: (autopkgtest) needs update for python3.11: python3.11: command not found)
Your message dated Tue, 29 Nov 2022 13:49:13 + with message-id and subject line Bug#1024857: fixed in beaker 1.11.0-3 has caused the Debian Bug report #1024857, regarding beaker: (autopkgtest) needs update for python3.11: python3.11: command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: beaker Version: 1.11.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of beaker fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 beaker from testing1.11.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. It seems that your tests tries to run against all supported python versions but doesn't secure that they are installed. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/b/beaker/28706376/log.gz [*] testing on python3.11: bash: line 1: python3.11: command not found autopkgtest [14:13:53]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: beaker Source-Version: 1.11.0-3 Done: Stuart Prescott We believe that the bug you reported is fixed in the latest version of beaker, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stuart Prescott (supplier of updated beaker 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, 30 Nov 2022 00:08:43 +1100 Source: beaker Architecture: source Version: 1.11.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stuart Prescott Closes: 1024857 Changes: beaker (1.11.0-3) unstable; urgency=medium . * Team upload. * Fix autopkgtest tests to depend on python3-all before iterating over all supported interpreters (Closes: #1024857). * Add Rules-Requires-Root: no. Checksums-Sha1: 0e737c994106c74ea55a18ee6b5a005c9310cf72 2213 beaker_1.11.0-3.dsc 94d91bfab5b42569367c76110f0257155abce698 7684 beaker_1.11.0-3.debian.tar.xz f4eb474936058892e18c3def84b070588209c401 6425 beaker_1.11.0-3_source.buildinfo Checksums-Sha256: 7d6c237f71cf4ddeb97986f90f46a609492605fbeb150a6234582118031ec3ba 2213 beaker_1.11.0-3.dsc 7c0b335968da2f7f6cff856ba5d9c90651ed57d1290d0ea65eca373f5b192012 7684 beaker_1.11.0-3.debian.tar.xz 94da41a234b4b4bfb69a4542f601a5b45fd013cff09fbdc3e539be962860c786 6425 beaker_1.11.0-3_source.buildinfo Files: bb830e5e03c143c576e120e62317e7f5 2213 python optional beaker_1.11.0-3.dsc d3c07d400ef433f4aa1809365009429a 7684 python optional beaker_1.11.0-3.debian.tar.xz 3ccf0a8591d09a6755350137083f64e3 6425 python optional beaker_1.11.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmOGC9YSHHN0dWFydEBk ZWJpYW4ub3JnAAoJELvBfrsTlvL3fA8P/AnkZI7X87BEaaywOEztO3MOFR5v2/nO go6ipGjNV8qgScItgCudVX0Zpc382LxyADDNFQhTjB1Zu6kdfJCLTxu79SAwH3VG 3jREff28jIiZ7r8EARU6MZRMCK2D474AQ7UGX4vPUAt6wupd3vABiEpP20jGDCT8 NZUdAa9BodISnh8nNxuFULDW2H3Ke0VSkJu+W538oInS4TqWz32fw2QBNoDgWj/a PKVURNP+7rZSzBa/2MASIoH/6tIUnIVkDKfybCnRZ8xE66djg3lBypdGI/TgBLTB
Bug#932820: NMU: vanguards: Use Python 3 instead of PyPy, because we are going to remove unsupported PyPy
Please find a NMU debiff attached.
This was just uploaded.diff -Nru vanguards-0.3.1/debian/changelog vanguards-0.3.1/debian/changelog
--- vanguards-0.3.1/debian/changelog2022-10-15 12:55:36.0 +0200
+++ vanguards-0.3.1/debian/changelog2022-11-29 09:34:36.0 +0100
@@ -1,3 +1,11 @@
+vanguards (0.3.1-2.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove irl from Uploaders (Closes: #970316)
+ * Migrate to Python 3 (Closes: #932820)
+
+ -- Bastian Germann Tue, 29 Nov 2022 09:34:36 +0100
+
vanguards (0.3.1-2.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru vanguards-0.3.1/debian/control vanguards-0.3.1/debian/control
--- vanguards-0.3.1/debian/control 2020-06-04 21:31:34.0 +0200
+++ vanguards-0.3.1/debian/control 2022-11-29 09:34:36.0 +0100
@@ -1,17 +1,15 @@
Source: vanguards
Maintainer: Debian Privacy Tools Maintainers
-Uploaders: Iain R. Learmonth , Ana Custura
+Uploaders: Ana Custura
Section: net
Priority: optional
Build-Depends: debhelper (>= 11),
dh-exec,
dh-python,
- pypy,
- pypy-setuptools,
+ python3-all:any,
+ python3-setuptools,
python3-pytest ,
- python3-stem (>= 1.6.0-3.1) ,
- pypy-stem (>= 1.6.0-3.1),
- pypy-ipaddress
+ python3-stem
Standards-Version: 4.1.5
Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/vanguards
Vcs-Git: https://salsa.debian.org/pkg-privacy-team/vanguards.git
@@ -20,8 +18,7 @@
Package: vanguards
Architecture: all
Depends: ${misc:Depends},
- ${pypy:Depends},
- pypy-ipaddress,
+ ${python3:Depends},
tor
Description: Additional protections for Tor Onion Services
vanguards uses the Stem Tor control port library to connect to a Tor control
diff -Nru vanguards-0.3.1/debian/rules vanguards-0.3.1/debian/rules
--- vanguards-0.3.1/debian/rules2020-06-04 21:30:41.0 +0200
+++ vanguards-0.3.1/debian/rules2022-11-29 09:34:36.0 +0100
@@ -1,7 +1,7 @@
#!/usr/bin/make -f
%:
- dh $@ --with pypy --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
Bug#1025029: marked as done (python-docutils: (autopkgtest) needs update for python3.11: 'NoneType' object is not subscriptable)
Your message dated Wed, 30 Nov 2022 00:36:29 +1100 with message-id and subject line Re: Bug#1025029: python-docutils: (autopkgtest) needs update for python3.11: 'NoneType' object is not subscriptable has caused the Debian Bug report #1025029, regarding python-docutils: (autopkgtest) needs update for python3.11: 'NoneType' object is not subscriptable 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.) -- 1025029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-docutils Version: 0.17.1+dfsg-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-docutils fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-docutilsfrom testing0.17.1+dfsg-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-docutils/28728887/log.gz /tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/test_parsers/test_recommonmark/test_section_headers.py:37: DeprecationWarning: invalid escape sequence '\ ' """\ /tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/test_parsers/test_recommonmark/test_section_headers.py:50: DeprecationWarning: invalid escape sequence '\ ' """\ /tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/test_parsers/test_recommonmark/test_section_headers.py:164: DeprecationWarning: invalid escape sequence '\ ' """\ Traceback (most recent call last): File "/tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/./alltests.py", line 88, in suite = suite() ^^^ File "/tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/./alltests.py", line 78, in suite suite = package_unittest.loadTestModules(DocutilsTestSupport.testroot, ^^ File "/tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/package_unittest.py", line 102, in loadTestModules module = import_module(mod) ^^ File "/tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/package_unittest.py", line 133, in import_module mod = __import__(name) File "/tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/test_parsers/test_rst/test_directives/test_tables.py", line 67, in null_bytes_exception = DocutilsTestSupport.exception_data(null_bytes)[0] ~~^^^ TypeError: 'NoneType' object is not subscriptable /tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/test_parsers/test_recommonmark/test_section_headers.py:37: DeprecationWarning: invalid escape sequence '\ ' """\ /tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/test_parsers/test_recommonmark/test_section_headers.py:50: DeprecationWarning: invalid escape sequence '\ ' """\ /tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test/test_parsers/test_recommonmark/test_section_headers.py:164: DeprecationWarning: invalid escape sequence '\ ' """\ Testing Docutils 0.17.1 with Python 3.10.8 on 2022-11-27 at 23:02:34 OS: Linux 5.10.0-19-cloud-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) (linux, Linux-5.10.0-19-cloud-amd64-x86_64-with-glibc2.36) Working directory: /tmp/autopkgtest-lxc.7f33ovby/downtmp/autopkgtest_tmp/test Docutils package: /usr/lib/python3/dist-packages/docutils test_pickle (test_pickle.PickleTests) ... ok test_error_handler (test_settings.ConfigEnvVarFileTests) ... ok test_list
Bug#1025063: gnomekiss FTBFS: Makefile:262: *** missing separator. Stop.
Source: gnomekiss Version: 2.0-6.1 Severity: serious Tags: ftbfs gnomekiss fails to build from source in unstable. A build now ends as follows: |dh_auto_build | make -j8 | make[1]: Entering directory '/<>' | Makefile:262: *** missing separator. Stop. | make[1]: Leaving directory '/<>' | dh_auto_build: error: make -j8 returned exit code 2 | make: *** [debian/rules:15: build] Error 25 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut
Bug#1023020: cmark-gfm: FTBFS on s390x
* Sebastian Ramacher [221129 11:21]: > Source: cmark-gfm > Version: 0.29.0.gfm.6-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > https://buildd.debian.org/status/fetch.php?pkg=cmark-gfm=s390x=0.29.0.gfm.6-2=1666810004=0 > > --- expected HTML > +++ actual HTML > @@ -7,15 +7,15 @@ > mailto:scyt...@pokemon.com;>scyt...@pokemon.com/ href="mailto:beedr...@pokemon.com;>beedr...@pokemon.com > mailto:scyt...@pokemon.com;>mailto:scyt...@pokemon.com > This is a href="mailto:scyt...@pokemon.com;>mailto:scyt...@pokemon.com > -mailto:scyt...@pokemon.com;>mailto:scyt...@pokemon.com. > +mailto:mailto:scyt...@pokemon.com;>scyt...@pokemon.com. This is caused by an out-of-bounds read on a memory buffer, which seems to be masked by stack layout on little-endian archs(?). PR for upstream is here: https://github.com/github/cmark-gfm/pull/296/files I've verified on zelenka.d.o this fixes the build failure. Chris
Processed: rm
Processing commands for cont...@bugs.debian.org: > retitle 938168 RM: python-setuptools -- RoQA; py2 leftover Bug #938168 [src:python-setuptools] python-setuptools: Python2 removal in sid/bullseye Changed Bug title to 'RM: python-setuptools -- RoQA; py2 leftover' from 'python-setuptools: Python2 removal in sid/bullseye'. > tags 938168 - bookworm Bug #938168 [src:python-setuptools] RM: python-setuptools -- RoQA; py2 leftover Removed tag(s) bookworm. > reassign 938168 ftp.debian.org Bug #938168 [src:python-setuptools] RM: python-setuptools -- RoQA; py2 leftover Bug reassigned from package 'src:python-setuptools' to 'ftp.debian.org'. No longer marked as found in versions python-setuptools/41.1.0-1. Ignoring request to alter fixed versions of bug #938168 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 938168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017950: marked as done (librust-prometheus+procfs-dev depends on non-existent librust-procfs-dev)
Your message dated Tue, 29 Nov 2022 10:11:15 + with message-id and subject line procfs now in unstable has caused the Debian Bug report #1017950, regarding librust-prometheus+procfs-dev depends on non-existent librust-procfs-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-prometheus+procfs-dev Version: 0.13.0-2 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic Hi Jelmer, The rust-prometheus source package builds a binary package, librust-prometheus+procfs-dev, which is uninstallable because it depends on librust-procfs-0.10-dev; but rust-procfs is not present anywhere in Debian. Please either upload rust-procfs to Debian or drop this binary package, which prevents rust-prometheus from being releasable. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- rust-procfs has now landed in unstable, resolving this bug. -- Jelmer Vernooij PGP Key: https://www.jelmer.uk/D729A457.asc--- End Message ---
Processed: bug 1024998 is forwarded to https://github.com/MatMoul/g810-led/pull/297
Processing commands for cont...@bugs.debian.org:
> forwarded 1024998 https://github.com/MatMoul/g810-led/pull/297
Bug #1024998 {Done: Stephen Kitt } [g810-led] g810-led:
Security risk: Leaves /dev/input/event* with read and write permissions for all
users
Set Bug forwarded-to-address to 'https://github.com/MatMoul/g810-led/pull/297'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1024754: marked as done (r-bioc-mofa: Should not block BioC 3.16 transition)
Your message dated Tue, 29 Nov 2022 08:49:54 + with message-id and subject line Bug#1024754: fixed in r-bioc-mofa 1.6.1+dfsg-8 has caused the Debian Bug report #1024754, regarding r-bioc-mofa: Should not block BioC 3.16 transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-mofa Version: 1.6.1+dfsg-7 Severity: critical Tags: ftbfs Justification: breaks unrelated software X-Debbugs-Cc: 1023...@bugs.debian.org Since r-bioc-mofa depends r-bioc-multiassayexperiment with RC bug #1024748 and thus it is blocking the BioC 3.16 transition[1] for an undetermined time. To not create any blocker for other packages r-bioc-mofa should be removed from testing which is the purpose of this bug. Kind regards Andreas. [1] https://release.debian.org/transitions/html/r-api-bioc-3.16.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: r-bioc-mofa Source-Version: 1.6.1+dfsg-8 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-bioc-mofa, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-bioc-mofa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Nov 2022 08:35:43 +0100 Source: r-bioc-mofa Architecture: source Version: 1.6.1+dfsg-8 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1024754 Changes: r-bioc-mofa (1.6.1+dfsg-8) unstable; urgency=medium . * Team upload. * Build with 3.16 BioC API Closes: #1024754 * Reduce piuparts noise in transitions (routine-update) Checksums-Sha1: 05408cd296725fb99f73a0bc1faad549e96846a2 2540 r-bioc-mofa_1.6.1+dfsg-8.dsc b28f09dfff9df26e3a9379148c3fd48bfdbffed6 3948 r-bioc-mofa_1.6.1+dfsg-8.debian.tar.xz 8ee78378e256aecb280250ffc9aeac60638520a5 17276 r-bioc-mofa_1.6.1+dfsg-8_amd64.buildinfo Checksums-Sha256: a01051d43f6dd95e6798b8392f7f76f8655354d38ffb190dc6aa580f95e25830 2540 r-bioc-mofa_1.6.1+dfsg-8.dsc 67bea781e063cfed8de203bdb159b8b894d9af47e17f29582272949a4a4c5eb8 3948 r-bioc-mofa_1.6.1+dfsg-8.debian.tar.xz ac147c21cafbc984b448106aa32337c6e286d6032f07f532c03100e6d586cb15 17276 r-bioc-mofa_1.6.1+dfsg-8_amd64.buildinfo Files: 428824d307e64861ea72c9c9650d7133 2540 gnu-r optional r-bioc-mofa_1.6.1+dfsg-8.dsc 37623b82d72f8832f7e89ddb24d5e98f 3948 gnu-r optional r-bioc-mofa_1.6.1+dfsg-8.debian.tar.xz 4dcc22f29baa0fe460f694d6bcbe9894 17276 gnu-r optional r-bioc-mofa_1.6.1+dfsg-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmOFt1gRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHZOQ/+N7ZIHTmBVsLpahTB7fwiURxitkBdaxKp 40Itc+j8fsVWSxCzqjulK/Jq5D3+Vp1GbvqKZEKSB/Pn+IAXrMMKLvmvvdCvKay7 TizuzSu06UeTi1cerpY5/dDXoJQETBRsGxcngJgc2Clu3uXCsD4ceDFnmIsPg+00 nRnrfEhoiQm0JPjLYsjQx+f8AMU2/LunHFIZV/EeZMuxU+WXGnKG0uIekRlZhWMf xeRiH5KIPL0ehjJJlVnjv9KKp/X3ta0c6qcyT7iTOOefTVjV/PVNTPhkZKx1dSN0 2Hy/fCde/aB++AmQp/SKq/C9B2EAHjIGTiM+VVQ1gShm2f4QHJK9rpSgKrutUyTg CQSllDmqe1Cf5uuqLay7koKad1JfGvtyfWHDWIxwK0mje6VxxmtjOjR5ivG8lDgW MoBxrfKxqBAnXu2fCbwBOP2qxijld1UeUTpURk9Z+YKPb2vydj79lA7MfNFwrhmQ ZiFPu2RggYBDqPQp41idNR+xkhTu83Qg2+gvPBBTOFbbWX666cKbD8IxKuJRcn2J 4fmLnDS+E9RXIwQSrt+eeB+d6J3R2h0JyTmjJnCswIyqNv9nl5DlJcsdLtBvCZge jZGe3xh5fJvOqZ2PqagaSc0rs0S6AIK2TT26pVe48PEWU6fRLdnpL56SLXs6Tjdl 2CObkPhnKQI= =s8Gj -END PGP SIGNATURE End Message ---
Bug#1019808: marked as done (openbabel: Please transition to wxwidgets3.2)
Your message dated Tue, 29 Nov 2022 08:48:56 + with message-id and subject line Bug#1019808: fixed in openbabel 3.1.1+dfsg-8 has caused the Debian Bug report #1019808, regarding openbabel: Please transition to wxwidgets3.2 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.) -- 1019808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openbabel Severity: normal Control: block 1019416 by -1 Hi, Please transition openbabel from wxwidgets3.0 to wxwidgets3.2. wxWidgets 3.2 (a new API/ABI stable release) has been released a few months ago and is now packaged in unstable as wxwidgets3.2. Upstream has stopped supporting wxWidgets 3.0, so the Debian wx team would like to migrate all wx package users to wxwidgets3.2 for bullseye, with the plan to remove wxwidgets3.0 before release. For most packages, the transition should be as simple as changing Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some packages may require small patches; I'm happy to help with those (and I have some already from working on this transition in Fedora already). Thanks, Scott --- End Message --- --- Begin Message --- Source: openbabel Source-Version: 3.1.1+dfsg-8 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of openbabel, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated openbabel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Nov 2022 10:26:44 -0500 Source: openbabel Architecture: source Version: 3.1.1+dfsg-8 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1019808 Changes: openbabel (3.1.1+dfsg-8) unstable; urgency=medium . * Acknowledge NMUs. * Fix debian/watch to watch GitHub tags. * Transition to wxwidgets3.2 (Closes: #1019808) * Simplify a path in debian/copyright. * Bump debhelper from old 12 to 13. * Set upstream metadata fields: Repository-Browse. * Update standards version to 4.6.1, no changes needed. * Remove Homepage from debian/upstream/metadata. Checksums-Sha1: d14c607227bd34daa30f5e837e16efb392e32a4b 2821 openbabel_3.1.1+dfsg-8.dsc 9af39d5985321320f40b3067ebd349f6ca819145 21136 openbabel_3.1.1+dfsg-8.debian.tar.xz dc6817e3ec159f78b465d47578f153475e3db8fe 12646 openbabel_3.1.1+dfsg-8_source.buildinfo Checksums-Sha256: 4caf206b0fddd5864c5ab07f3f8f10ff1ebc00b895f00bfbfd1a23cbe0cdc76d 2821 openbabel_3.1.1+dfsg-8.dsc f7df6496d1eaeb479d6d651cd232e6a6d205faf0de6f208234f71332a2ba2564 21136 openbabel_3.1.1+dfsg-8.debian.tar.xz 97ad7b60c20c7b01f75a73a2cb20c714386a7090af59f7f6101fd50cfe4affbb 12646 openbabel_3.1.1+dfsg-8_source.buildinfo Files: 2744a7e49e68d4ed1f40ad97a9bfbb7e 2821 science optional openbabel_3.1.1+dfsg-8.dsc 72e20d0fa0b9ff39c7a0def2fc893700 21136 science optional openbabel_3.1.1+dfsg-8.debian.tar.xz 55d34e19d57e7f1cdd11ddd69dbd7066 12646 science optional openbabel_3.1.1+dfsg-8_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmOFwcwSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHDWwP/RSYNP0utKaYm9uO/BhfFEDaIDS0pwYv rmogjKEi7ETQELi09CdGD2IGB5b8QNwI0suVDFYIc/04p6+ynWgGyCnFxkb2ylJU d7i/rQulueaXUN7uluvfaLwMi4CSK09iT97wd1QkB0cX3bQPU0nPK4+WVskDvj5i Al4F80kOT5l51dd69MBMbUJYDj+MeYBA5sJcScYuoM5fYZSguUzKsg91gdwfW0fG iYOlr2KSoBnRhgBQauYiFfaS0xXA/qkncjj6Ya1VxopRKb6tA9YzM8VQgzWLb7/g +C3pgeRW1DbxN1TqIDeNFeYmFFuDxu9NGN7mkeI8rpiA33ic0xSf04tx0PjeTGIv iX7xdhi2VpSIIhIc0gFylxtdwT+e7gCbD+7FnPy0gdZOOj6XhgOgh5KeQKCyU/5/ 4o05+/N9aH/KhG6BdQLH/h5NbU4E1q8p3I//BcpzY308FUaEEmNAm8DTIysVrsvu nazs0Ye4U8wIJEqfUBGv4k857YUXJkrq3ptpg6MootS3oqXyAmiCun/fjoMra1hg DPZfxWfk2cSs8ggkafKRh88z8Dd8Kl+hU311C4GLAHnVVrwLRPEU4PgF+kBS8vkF YjbaX+LFtRwQlcBFLNG+zt9PDjvJ7vn2JC98YZDd/bjIU0wLFExYSk+U9nonQ2hR poj0PDN4XRPn =SZuK -END PGP SIGNATURE End Message ---
Bug#1024597: marked as done (r-bioc-demixt FTBFS: dependency ‘DSS’ is not available for package ‘DeMixT’)
Your message dated Tue, 29 Nov 2022 08:49:35 + with message-id and subject line Bug#1024597: fixed in r-bioc-demixt 1.14.0+dfsg-1 has caused the Debian Bug report #1024597, regarding r-bioc-demixt FTBFS: dependency ‘DSS’ is not available for package ‘DeMixT’ 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.) -- 1024597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-demixt Version: 1.14.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=r-bioc-demixt=1.14.0-1 ... I: Using built-time from d/changelog: Mon, 21 Nov 2022 13:38:58 +0100 mkdir -p /<>/debian/r-bioc-demixt/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-bioc-demixt/usr/lib/R/site-library --clean . "--built-timestamp='Mon, 21 Nov 2022 13:38:58 +0100'" ERROR: dependency ‘DSS’ is not available for package ‘DeMixT’ * removing ‘/<>/debian/r-bioc-demixt/usr/lib/R/site-library/DeMixT’ dh_auto_install: error: R CMD INSTALL -l /<>/debian/r-bioc-demixt/usr/lib/R/site-library --clean . "--built-timestamp='Mon, 21 Nov 2022 13:38:58 +0100'" returned exit code 1 make: *** [debian/rules:4: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: r-bioc-demixt Source-Version: 1.14.0+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-bioc-demixt, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-bioc-demixt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Nov 2022 09:12:51 +0100 Source: r-bioc-demixt Architecture: source Version: 1.14.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1024597 Changes: r-bioc-demixt (1.14.0+dfsg-1) unstable; urgency=medium . * Team upload. * Repack upstream source to exclude HTML doc with compressed JS * Build-Depends: r-bioc-dss Closes: #1024597 * Add lintian-overrides (see lintian bug #1017966) Checksums-Sha1: 382b2e7edfc85c9b64836ed3afeb740d589cd692 2395 r-bioc-demixt_1.14.0+dfsg-1.dsc 5aa5135d2af92d0034a52840d39a852002b37006 3474724 r-bioc-demixt_1.14.0+dfsg.orig.tar.xz 4345ce56be21e866de3d81ab6bfbee84254a69f5 3400 r-bioc-demixt_1.14.0+dfsg-1.debian.tar.xz aacdd028fe1a16ce7540250ea6e7d329dd135092 17279 r-bioc-demixt_1.14.0+dfsg-1_amd64.buildinfo Checksums-Sha256: fa58aa7c231cbdc59c41e2b0236ea40369fbd0e981950b6208b49f2718bbe156 2395 r-bioc-demixt_1.14.0+dfsg-1.dsc ba328847c06ebea9292211634b7ec70570363d10cd3901940ff986175a3bae44 3474724 r-bioc-demixt_1.14.0+dfsg.orig.tar.xz f84df3f1e6a65115373a30fc8afc65803ae0aaa49c703fe851ff98916e28f8c1 3400 r-bioc-demixt_1.14.0+dfsg-1.debian.tar.xz 2718a6b1af0284fe6d462bfca0d81827be4ca224f3c5d10eb67207178180272d 17279 r-bioc-demixt_1.14.0+dfsg-1_amd64.buildinfo Files: d4e106576c9ed537ed67ce7c9df42676 2395 gnu-r optional r-bioc-demixt_1.14.0+dfsg-1.dsc e015b2121ff9555e66d9691ff26e8533 3474724 gnu-r optional r-bioc-demixt_1.14.0+dfsg.orig.tar.xz 703aef48dc68eddf2dc5bdfb76db39c3 3400 gnu-r optional r-bioc-demixt_1.14.0+dfsg-1.debian.tar.xz fd002814114f1b904b1afb97b3fb3b92 17279 gnu-r optional r-bioc-demixt_1.14.0+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmOFwD8RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtF/DQ//dmkwAbaDVWcWfdTAytGA42ENPbpClAcd /jZEA/XbvZp/Do0e63i0eQH24+FYPEftXCZAyqSAU5K3hMs2lE7LDfCuGgnjffy0 25Xp0qGNjB9kPoaiK1ypi8kH/pVgjy+K923Gm5P6Dgi+qGmWHthcQ/CDW8mfl5Td CbueWLGgSAv4fvmy26YlnilMnAdDlcsEIFOVgnBnzy7th67aQ+tHluVwAiN0qVmV AnmCEJvGFXX63afA5VgOUMTwbo579lkwuVwQRPsNcz0oqLv5mgWM7sqHQv4kWy7h HLHwWsnNmCMBFn8jxltzYtJPWl7+JWAFPJgsgonF3AyoubOkojoWeqiGDZje++Eq awgKSIbVLpjSGGl+MEp1IR8Rb/fX1gC12se+Nca40MDQ2TrvsNDPzozOlB1d1GGy MAY+CFsPdRF5PUtIo/4Uns7r/zmzSBs92551KmQluPBR9XnOwc89fqiVbbEhtwLX mBM5jbwZQWjC8mkYsd6SvtXjqk/TAFfpTxNiPkMt3eZgTed7i05VFKGBw2IpA0qb GTkXgDBsnIbPlgHnG5XDUEERCjS+PpMFY6dqZm7p+VWbymKAybzdhoCQtMJCecUX
Bug#1025048: texlive-lang: Should not migrate to testing
Source: texlive-lang Version: 2022.20221123-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, this piece of software is tightly bind to package texlive-extra. This package in turn currently can't migrate to testing due to incompatibility to LaTeXML. The issue is known at upstream [1], but currently I'm failing to solve the issue using the provided pull request. I hope for a solution from LaTeXML upstream soon. For now the latest TL snapshot dhould no migrate to testing. Hilmar [1] https://github.com/brucemiller/LaTeXML/issues/1985 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- sigmentation fault signature.asc Description: PGP signature
Bug#1025047: texlive-base: Should not migrate to testing
Source: texlive-base Version: 2022.20221123-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, this piece of software is tightly bind to package texlive-extra. This package in turn currently can't migrate to testing due to incompatibility to LaTeXML. The issue is known at upstream [1], but currently I'm failing to solve the issue using the provided pull request. I hope for a solution from LaTeXML upstream soon. For now the latest TL snapshot dhould no migrate to testing. Hilmar [1] https://github.com/brucemiller/LaTeXML/issues/1985 -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 3381 Nov 29 09:12 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Oct 12 23:25 /usr/share/texmf/ls-R -> /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Nov 27 23:33 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Nov 27 23:33 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files -rw-r--r-- 1 root root 475 Oct 14 12:18 /etc/texmf/web2c/texmf.cnf lrwxrwxrwx 1 root root 33 Nov 27 23:33 /usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN lrwxrwxrwx 1 root root 32 Nov 27 23:33 /usr/share/texmf/web2c/updmap.cfg -> /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 5130 Nov 29 09:10 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Sep 4 2021 mktex.cnf -rw-r--r-- 1 root root 475 Oct 14 12:18 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tex-common depends on: ii ucf 3.0043 Versions of packages tex-common suggests: ii debhelper 13.11.1 Versions of packages texlive-base is related to: ii tex-common6.18 ii texlive-binaries 2022.20220321.62855-4+b1 -- sigmentation fault signature.asc Description: PGP signature
