Bug#1021857: CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message):
Salut Sylvestre ! On Wed, Nov 30, 2022 at 9:21 PM Sylvestre Ledru wrote: > > btw, do you know what caused this in cmake? (seems that it is caused by > a new cmake version). > > (or not to make sure that all binaries aren't exported?) If you have a build-tree of llvm-14, here is what I would do: $ cd obj-* $ DESTDIR=/tmp/sylvestre make install $ find /tmp/sylvestre -name mlir-tblgen output1 $ grep mlir-tblgen /tmp/sylvestre/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake output2 -> verify output1 & output2 matches > > Le 28/11/2022 à 12:07, Mathieu Malaterre a écrit : > > Control: found 1021857 1:14.0.6-2 > > > > -- Found LibXml2: /usr/lib/x86_64-linux-gnux32/libxml2.so (found > > version "2.9.14") > > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > > (message): > >The imported target "mlir-tblgen" references the file > > > > "/usr/lib/llvm-14/bin/mlir-tblgen" > > > >but this file does not exist. Possible reasons include: > > > >* The file was deleted, renamed, or moved to another location. > > > >* An install or uninstall procedure did not complete successfully. > > > >* The installation package was faulty and contained > > > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > > >but not all the files it references. > > > > Call Stack (most recent call first): > >/usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) > >openvdb_ax/openvdb_ax/CMakeLists.txt:105 (find_package) > > > > > > > > * > > https://buildd.debian.org/status/fetch.php?pkg=openvdb&arch=x32&ver=10.0.0-7&stamp=1669627540&raw=0 > > > > ___ > > Pkg-llvm-team mailing list > > pkg-llvm-t...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team
Bug#1024954: marked as done (librcsb-core-wrapper: (autopkgtest) needs update for python3.11: initialization of CorePyWrap raised unreported exception)
Your message dated Thu, 01 Dec 2022 07:35:55 + with message-id and subject line Bug#1024954: fixed in librcsb-core-wrapper 1.005-11 has caused the Debian Bug report #1024954, regarding librcsb-core-wrapper: (autopkgtest) needs update for python3.11: initialization of CorePyWrap raised unreported exception 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.) -- 1024954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librcsb-core-wrapper Version: 1.005-10 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 librcsb-core-wrapper 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 librcsb-core-wrapper from testing1.005-10 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/libr/librcsb-core-wrapper/28726239/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in SystemError: initialization of CorePyWrap raised unreported exception autopkgtest [17:14:04]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: librcsb-core-wrapper Source-Version: 1.005-11 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of librcsb-core-wrapper, 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 librcsb-core-wrapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Dec 2022 08:15:25 +0100 Source: librcsb-core-wrapper Architecture: source Version: 1.005-11 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1024954 Changes: librcsb-core-wrapper (1.005-11) unstable; urgency=medium . * s/python3-all-dev/python3-dev/ to ignore python3.11 for the moment Closes: #1024954 * Standards-Version: 4.6.1 (routine-update) * Avoid explicitly specifying -Wl,--as-needed linker flag. Checksums-Sha1: f99b7a513c9d5576e35cec6b7e545b8e3764d037 2517 librcsb-core-wrapper_1.005-11.dsc caebe82bb72910bae74ae90817faaf34cb514944 21152 librcsb-core-wrapper_1.005-11.debian.tar.xz 5c4d906f6f70aff2f5f44755d3f1e611b4d712d0 11403 librcsb-core-wrapper_1.005-11_amd64.buildinfo Checksums-Sha256: 4c6e6b97fb1bba4143b6c9ccace5705e20088c6db0c34d87ebfa3a62ad7b5b1e 2517 librcsb-core-wrapper_1.005-11.dsc 0c67dadc5b20483a6cfbc33960ae6e64627eb4e56a5f8a92dc981f605d4ff752 21152 librcsb-core-wrapper_1.005-11.debian.tar.xz 27a42f4c256fe936c54fcfec71e9d5a11cc64d5f28ee39bf807e1327f31086fd 11403 librcsb-core-wrapper_1.005-11_amd64.buildinfo Files: 1baf8655bd2988d5be68f2b4040f2025 2517 libs optional librcsb-core-wrapper_1.005-11.dsc 3b2eec9dce31b4363f8f6b15aec703ed 21152 libs optional librcsb-core-wrapper_1.005-11.debian.tar.xz 014c13261293c7287446f0b4672bbe74 11403 libs optional librcsb-core-wrapper_1.005-11_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiE
Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1
Hi Andreas, Sorry for not answering earlier, but I'm still in the process of finalizing the GNU Health / Orthanc conference, and I'm extremely busy with my academic activities. I admit I would have loved if you would have made some noise about this conference on the Debian Med list. I hope you had a successful conference. The conference was great success, and I advertised about it on the Debian Med mailing list back in August: https://lists.debian.org/debian-med/2022/08/msg00060.html Unfortunately, I got no feedback from our community. The openSUSE community was present, and I hope we'll get submissions from our community in the next edition of this joint conference. I'll have a look by Wednesday 30th November. Do you think you can work on this in the next couple of days? Yes, as soon as I finalize a research application that could gather funding for Orthanc and GNU Health... sorry for the delay, I got feedback yesterday that required a rework for this application. Cheers, Sébastien- -- Sébastien Jodogne Mail: s.jodo...@orthanc-labs.com Web: http://www.orthanc-labs.com/ Twitter: https://twitter.com/sjodogne
Bug#1025222: clblas: ftbfs due to Could NOT find PythonInterp
Source: clblas Version: 2.12-2 Severity: serious Tags: ftbfs Dear Maintainer, The package has ftbfs issue due to: ``` -- Found OPENCL: /usr/lib/x86_64-linux-gnu/libOpenCL.so (found version "2.0") -- FindOpenCL /usr/lib/x86_64-linux-gnu/libOpenCL.so, /usr/include -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found suitable version "1.74.0", minimum required is "1.33.0") found components: program_options -- Boost_PROGRAM_OPTIONS_LIBRARY: Boost::program_options CMake Error at /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE) Call Stack (most recent call first): /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.25/Modules/FindPythonInterp.cmake:170 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) library/CMakeLists.txt:17 (find_package) ... ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=clblas&arch=amd64&ver=2.12-2&stamp=1669843177&raw=0 It is easy to fix the issue and I will update it once verifing. -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1
Hi Sébastien, On Thu, 24 Nov 2022 17:37:36 you wrote > Sorry for not answering earlier, but I'm still in the process of > finalizing the GNU Health / Orthanc conference, and I'm extremely busy > with my academic activities. I admit I would have loved if you would have made some noise about this conference on the Debian Med list. I hope you had a successful conference. > I'll have a look by Wednesday 30th November. Do you think you can work on this in the next couple of days? Kind regards Andreas. -- http://fam-tille.de
Processed: Bug#1024784 marked as pending in swift
Processing control commands: > tag -1 pending Bug #1024784 [src:swift] swift: (autopkgtest) needs update for python3.11: Segmentation fault Added tag(s) pending. -- 1024784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024155: Fixed in Git [Re: libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3)]
Control: tags -1 pending Hi Aaron, I have fixed this issue in Git. I'm wondering about the status of the ncbi-vdb transition[1]. Isn't it time to upload the packages to unstable now? Just let me know if you need any help. Kind regards Andreas. PS: Do you have any information whether it is sensible to upgrade to sra-sdk version 3.0.1? [1] https://release.debian.org/transitions/html/auto-ncbi-vdb.html -- http://fam-tille.de
Bug#1024784: marked as pending in swift
Control: tag -1 pending Hello, Bug #1024784 in swift reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/swift/-/commit/24020d48e1c9c688c53abfaf35c8410298cd1f5c Add Fix_DB_tests_on_py311.patch (Closes: #1024784). (this message was generated automatically) -- Greetings https://bugs.debian.org/1024784
Processed: Fixed in Git [Re: libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3)]
Processing control commands: > tags -1 pending Bug #1024155 [libngs-c++-dev] libngs-c++-dev: missing Breaks+Replaces: libncbi-vdb-dev (<< 3), libngs-sdk-dev (<< 3) Added tag(s) pending. -- 1024155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: 1024526 is forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 1024526 https://github.com/simbody/simbody/issues/751 Bug #1024526 [src:simbody] simbody: FTBFS on ppc64el, mips64el Set Bug forwarded-to-address to 'https://github.com/simbody/simbody/issues/751'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025203: r-cran-glmmtmb: FTBFS on mipsel
Hi, Am Wed, Nov 30, 2022 at 10:08:14PM +0100 schrieb Paul Gevers: > Source: r-cran-glmmtmb > Version: 1.1.4+dfsg-3 > Severity: serious > Tags: ftbfs > Justification: ftbfs > > Dear maintainer(s), > > Your package failed to build from source on mipsel, where it built > successfully in the past. > > https://buildd.debian.org/status/fetch.php?pkg=r-cran-glmmtmb&arch=mipsel&ver=1.1.5%2Bdfsg-1&stamp=1669057119&raw=0 > ... > cc1plus: out of memory allocating 1058400 bytes after a total of 59473920 > bytes Isn't this just a matter of the autobuilders hardware? If not I do not see any other clue but removing the package for mipsel. Kind regards Andreas. -- http://fam-tille.de
Bug#1011711: marked as done (ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: expect(e).to be_a(TypeError))
Your message dated Thu, 01 Dec 2022 04:36:07 +
with message-id
and subject line Bug#1011711: fixed in ruby-jwt 2.5.0-1
has caused the Debian Bug report #1011711,
regarding ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: expect(e).to
be_a(TypeError)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1011711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jwt
Version: 2.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> expect(e).to be_a(TypeError)
> expect(e.message).to eq('no implicit conversion of
> OpenSSL::PKey::RSA into String')
> end
> end
>
> expected # 3.0> to be a kind of NoMethodError
> # ./spec/jwk/decode_with_jwk_spec.rb:93:in `block (5 levels) in (required)>'
>
> Finished in 9.17 seconds (files took 0.24023 seconds to load)
> 239 examples, 48 failures
>
> Failed examples:
>
> rspec ./spec/jwk/ec_spec.rb:11 # JWT::JWK::EC.new when a keypair with both
> keys given creates an instance of the class
> rspec ./spec/jwk/ec_spec.rb:19 # JWT::JWK::EC.new when a keypair with only
> public key is given creates an instance of the class
> rspec './spec/jwk/ec_spec.rb[1:3:1:1:1]' # JWT::JWK::EC.import when crv=P-256
> when keypair is private returns a private key
> rspec './spec/jwk/ec_spec.rb[1:3:1:1:2:1]' # JWT::JWK::EC.import when
> crv=P-256 when keypair is private with a custom "kid" value imports that
> "kid" value
> rspec './spec/jwk/ec_spec.rb[1:3:1:2:1:1]' # JWT::JWK::EC.import when
> crv=P-256 when keypair is public returns a public key returns a hash with the
> public parts of the key
> rspec './spec/jwk/ec_spec.rb[1:3:2:2:1:1]' # JWT::JWK::EC.import when
> crv=P-384 when keypair is public returns a public key returns a hash with the
> public parts of the key
> rspec './spec/jwk/ec_spec.rb[1:3:2:1:1]' # JWT::JWK::EC.import when crv=P-384
> when keypair is private returns a private key
> rspec './spec/jwk/ec_spec.rb[1:3:2:1:2:1]' # JWT::JWK::EC.import when
> crv=P-384 when keypair is private with a custom "kid" value imports that
> "kid" value
> rspec './spec/jwk/ec_spec.rb[1:3:3:2:1:1]' # JWT::JWK::EC.import when
> crv=P-521 when keypair is public returns a public key returns a hash with the
> public parts of the key
> rspec './spec/jwk/ec_spec.rb[1:3:3:1:1]' # JWT::JWK::EC.import when crv=P-521
> when keypair is private returns a private key
> rspec './spec/jwk/ec_spec.rb[1:3:3:1:2:1]' # JWT::JWK::EC.import when
> crv=P-521 when keypair is private with a custom "kid" value imports that
> "kid" value
> rspec ./spec/jwk/ec_spec.rb:64 # JWT::JWK::EC#export when private key is
> requested returns a hash with the both parts of the key
> rspec ./spec/jwk/ec_spec.rb:45 # JWT::JWK::EC#export when keypair with public
> key is exported returns a hash with the public parts of the key
> rspec ./spec/jwk/ec_spec.rb:55 # JWT::JWK::EC#export when keypair with public
> key is exported when a custom "kid" is provided exports it
> rspec ./spec/jwk/ec_spec.rb:32 # JWT::JWK::EC#export when keypair with
> private key is exported returns a hash with the both parts of the key
> rspec ./spec/integration/readme_examples_spec.rb:261 # README.md code test
> claims JWK
> rspec ./spec/integration/readme_examples_spec.rb:53 # README.md code test
> algorithm usage ECDSA
> rspec ./spec/jwk_spec.rb:14 # JWT::JWK.import creates a ::JWT::JWK::RSA
> instance
> rspec ./spec/jwk_spec.rb:36 # JWT::JWK.import when keypair with defined kid
> is imported returns the predefined kid if jwt_data contains a kid
> rspec ./spec/jwk_spec.rb:21 # JWT::JWK.import parsed from JSON creates a
> ::JWT::JWK::RSA instance from JSON parsed JWK
> rspec ./spec/jwk_spec.rb:59 # JWT::JWK.new when EC key is given
> rspec './spec/jwt_spec.rb[1:12:1]' # JWT alg: ES256 should generate a valid
> token
> rspec './spec/jwt_spec.rb[1:12:2]' # JWT alg: ES256 should decode a valid
> token
> rspec './spec/jwt_spec.rb[1:12:3]' # JWT alg: ES256 wrong key should raise
> JWT::DecodeError
> rspec './spec/jwt_spec.rb[1:12:4]' # JWT alg: ES256 wrong key and verify =
> false should not raise JWT::DecodeError
> rspec ./spec/jwt_spec.rb:342 # JWT Invalid ECDSA curve_name should raise
> JWT::IncorrectAlgorithm
> rspec './spec/jwt_spec.rb[1:14:4]' # JWT alg: ES512 wrong key and verify =
> f
Bug#1025214: dkms: --environment-overrides causes several module build failures
Control: severity -1 grave
Hi!
Guess who just spent two hours chasing this down in a big upgrade with
a half-bootable system in the mean-time :)
Retagging as grave ("unusable by most or all users, or causes data loss"
feels more appropriate than "severe violation of Debian policy").
I cannot tell you just how /tempting/ critical ‒ "makes unrelated
software on the system (or the whole system) break" is,
probably would be even more so if I weren't on battery :)
My system's on ZFS. Needs ZFS to boot, actually. It's very cool to see
" doesn't exist" in the log. Much cooler still to find that
I can run make myself in the build directory and it works! Very cool and
fun to spend multiple minutes per iteration with ZFS's long
configuration times!
The dkms bit from apt-listchanges is
-- >8 --
dkms (3.0.8-2) unstable; urgency=medium
* export-CC, exact-cc: Merge and improve the two patches. Ensure that
compiler is set and exported as early in the prepartion stage as
possible, is not subsequently unset (already unset at the start of the
dkms script), and also export MAKEFLAGS to ensure that environment CC
variable is used by kernel's Makefile. Fixes LP: #1997841
* Drop dangling unapplied patch from git.
-- Dimitri John Ledkov Thu, 24 Nov 2022
14:59:45 +
dkms (3.0.8-1) unstable; urgency=medium
[ Andreas Beckmann ]
* update watch file
* message consistency
[ Gianfranco Costamagna ]
* New upstream version 3.0.8
* Drop upstream patches:
- 2b76d4aa29e65ae4ed8e89685c4e729f1276c5fc
- 3ca52f8769bdf7ebdc83735355fff7c5c0664152
- 7f3c4b03c506e40f0a5ce9315a8ade88b108ce0f
- 8d60956f6dcda0679066954215eb8be4045413b4
- 985bfd584f0e87bc726865bfdc17887d4713c854
* Refresh patches
-- Gianfranco Costamagna Fri, 18 Nov 2022 22:34:50
+0100
-- >8 --
I downgraded to 3.0.8-1 from snapshot.d.o (which surprisingly didn't
explode despite how fucked my dpkg config state was). That worked.
Please consider verifying whether an "improvement" doesn't straight-up
break every user before uploading.
This graph shows that the nvidia driver /alone/ is /4%/ of all reporting
installations (unfiltered rdeps for dkms):
https://qa.debian.org/popcon-graph.php?packages=zfs-dkms+zfs-dkms+r8168-dkms+nvidia-legacy-390xx-kernel-dkms+nvidia-kernel-dkms+broadcom-sta-dkms+zfs-dkms+acpi-call-dkms+dahdi-dkms+r8168-dkms+nvidia-tesla-470-kernel-dkms+nvidia-tesla-460-kernel-dkms+nvidia-tesla-450-kernel-dkms+nvidia-tesla-418-kernel-dkms+nvidia-legacy-390xx-kernel-dkms+nvidia-kernel-dkms+broadcom-sta-dkms+xtrx-dkms+xtables-addons-dkms+wireguard-dkms+west-chamber-dkms+v4l2loopback-dkms+tp-smapi-dkms+openrazer-driver-dkms+openafs-modules-dkms+octavia-agent+nat-rtsp-dkms+lttng-modules-dkms+live-task-recommended+lime-forensics-dkms+vpoll-dkms+langford-dkms+jool-dkms+iptables-netflow-dkms+gost-crypto-dkms+evdi-dkms+dpdk-kmods-dkms+dm-writeboost-dkms+digimend-dkms+ddcci-dkms+acpi-call-dkms+bbswitch-dkms+adv-17v35x-dkms&show_installed=on&want_percent=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
:)
At least it didn't migrate to testing.
наб
signature.asc
Description: PGP signature
Processed: Re: Bug#1025214: dkms: --environment-overrides causes several module build failures
Processing control commands: > severity -1 grave Bug #1025214 [dkms] dkms: --environment-overrides causes several module build failures Severity set to 'grave' from 'serious' -- 1025214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025214: dkms: --environment-overrides causes several module build failures
Package: dkms
Version: 3.0.8-2
Severity: serious
Hi,
export MAKEFLAGS="--environment-overrides" causes several modules to
fail to build since this seems to inject unwanted environment variable
values into various build processes.
E.g. the nvidia modules react fragile to the ARCH variable, therefore we
unset that variable first:
MAKE[0]="unset ARCH; env NV_VERBOSE=1 \
make ${parallel_jobs+-j$parallel_jobs} modules KERNEL_UNAME=${kernelver}"
but that does not work any longer. Verbose output shows that it tries to
build with ARCH=x86 (I have no clue where that value comes from)
instead of ARCH=x86_64 (which it even attempts to set).
I think you are mixing two things in the export-CC.patch:
1.) try to get the correct CC value from the kernel (.kernelvariables,
.config, ...) and export that for the benefit of the module build
system, overriding any CC value found in the environment (which is
likely to be wrong) (this does not need to be propagated back to
kbuild)
2.) support overriding the CC used by kbuild (and the module build
system) with some custom value
Andreas
PS: shouldn't you rather append to MAKEFLAGS and not override them?
Bug#972211: FTBFS with OCaml 4.11.1 (-unsafe-string is not available)
Package: mldonkey Followup-For: Bug #972211 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-19-amd64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available
Package: gnome-shell Version: 43.1-2 Severity: serious Justification: Policy 3.8 Dear Maintainer, Recently a general upgrade was executed with gnome-shell upgrading from version 43.0-2 to 43.1-2. After this upgrade the gnome-shell wayland screen is flickering and mangled at any action. Flickering stops after short time, but screen often is mangled. During flickering different old or background screens are shown. Also the logon-screen is flickering and mangled. Some user-friendly person has decided to stop support for the i915 dri driver. As a "service" the mesa-upgrade at Debian also automatically deletes this driver. If an old i915-dri driver is moved to the original location, the flickering problem is gone. Also if "Gnome on Xorg" is started there is no flickering problem. In that case swrast is used for software rendering. I do not know which method gnome with wayland is using, but it is not swrast. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 6.0.0-4-686-pae (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gir1.2-accountsservice-1.0 22.08.8-1+b1 ii gir1.2-adw-1 1.2.0-1 ii gir1.2-atk-1.0 2.46.0-4 ii gir1.2-atspi-2.0 2.46.0-4 ii gir1.2-freedesktop 1.74.0-2 ii gir1.2-gcr-3 3.41.1-1+b1 ii gir1.2-gdesktopenums-3.0 43.0-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1 ii gir1.2-gdm-1.0 43.0-1 ii gir1.2-geoclue-2.0 2.6.0-2 ii gir1.2-glib-2.0 1.74.0-2 ii gir1.2-gnomebluetooth-3.0 42.4-1 ii gir1.2-gnomedesktop-3.0 43-2 ii gir1.2-graphene-1.0 1.10.8-1 ii gir1.2-gstreamer-1.0 1.20.4-1 ii gir1.2-gtk-3.0 3.24.35-1 ii gir1.2-gtk-4.0 4.8.2+ds-3 ii gir1.2-gweather-4.0 4.2.0-1 ii gir1.2-ibus-1.0 1.5.27-4 ii gir1.2-mutter-11 43.0-2 ii gir1.2-nm-1.0 1.40.4-1 ii gir1.2-nma-1.0 1.10.4-2 ii gir1.2-pango-1.0 1.50.10+ds-1 ii gir1.2-polkit-1.0 122-1 ii gir1.2-rsvg-2.0 2.54.5+dfsg-1 ii gir1.2-soup-3.0 3.2.1-2 ii gir1.2-upowerglib-1.0 0.99.20-1+b1 ii gir1.2-webkit2-4.1 2.38.2-1+b1 ii gnome-backgrounds 43-1 ii gnome-settings-daemon 43.0-3 ii gnome-shell-common 43.1-2 ii gsettings-desktop-schemas 43.0-1 ii gstreamer1.0-pipewire 0.3.61-1 ii libatk-bridge2.0-0 2.46.0-4 ii libatk1.0-0 2.46.0-4 ii libc6 2.36-5 ii libcairo2 1.16.0-6 ii libecal-2.0-2 3.46.1-1+b2 ii libedataserver-1.2-27 3.46.1-1+b2 ii libgcr-base-3-1 3.41.1-1+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libgirepository-1.0-1 1.74.0-2 ii libgjs0g 1.74.1-1 ii libgles2 1.5.0-1 ii libglib2.0-0 2.74.1-2 ii libglib2.0-bin 2.74.1-2 ii libgnome-autoar-0-0 0.4.3-1 ii libgnome-desktop-3-20 43-2 ii libgraphene-1.0-0 1.10.8-1 ii libgtk-3-0 3.24.35-1 ii libgtk-4-1 4.8.2+ds-3 ii libical3 3.0.16-1+b1 ii libjson-glib-1.0-0 1.6.6-1 ii libmutter-11-0 43.0-2 ii libnm0 1.40.4-1 ii libpango-1.0-0 1.50.10+ds-1 ii libpangocairo-1.0-0 1.50.10+ds-1 ii libpolkit-agent-1-0 122-1 ii libpolkit-gobject-1-0 122-1 ii libpulse-mainloop-glib0 16.1+dfsg1-2+b1 ii libpulse0 16.1+dfsg1-2+b1 ii libsecret-1-0
Bug#1024890: ntcard - build-dependencies unsatisfiable on 32-bit.
On 30/11/2022 07:29, Andreas Tille wrote: 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? armel armhf i386 mipsel s390x (390x is not 32-bit but is also affected, I missed that when initially filing the bug). The package was never released on 32 bit architectures ntcard was built on all release architectures and binaries for all architetures are currently in testing. After it was built, nthash was removed on 32-bit and big-endian architectures as documented in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023060 Could you please give any reason which backs up your choice "serious" for this bug report? The rc policy says Packages must autobuild without failure on all architectures on which they are supported. Packages must be supported on as many architectures as is reasonably possible. Packages are assumed to be supported on all architectures for which they have previously built successfully. Prior builds for unsupported architectures must be removed from the archive (contact -release or ftpmaster if this is the case). Ref: RT? Packages must be buildable within the same release. Ref: RT?
Bug#1025171: zfs-dkms FTBFS against 6.0.0-5-amd64
There isn't enough detail to be sure, but this might be the same issue I hit on sid yesterday, so adding it here. It might also count as a dkms bug for all I know. In my case, zfs-dkms fails to build against either of my currently installed kernels (5.19.0-1-amd64, 6.0.0-5-amd64), but only after updating the package dkms to version 3.0.8-2 (from 3.0.8-1). This appears to be the result of the changes to the export-CC.patch: https://sources.debian.org/patches/dkms/3.0.8-2/export-CC.patch/ The 3.0.8-2 version adds the following commands to the prepare_build() function: export CC=$CC export MAKEFLAGS="--environment-overrides" I've verified that zfs-dkms builds fine for me if I temporarily comment out the second line from /usr/sbin/dkms. A build log for a failed attempt (with the flag present) is at: https://0x0.st/o0fu.txt The log also includes a dump of the environment variables at the start of the build, from a command I added to the dkms script. Digging a little deeper, it appears that when `--environment-overrides` is set, a number of required command-line options (in particular, an -I option to add /var/lib/dkms/zfs/2.1.6/build/include in the include search path) fail to be set. I didn't manage to trace why exactly that is, but you can see both a failing and a working example (for one object file) at: https://0x0.st/o0EC.txt FWIW, it seems like the build environment dkms uses inherits whatever was present in the environment when apt was called. If this is the case, then it feels to me including the `--environment-overrides` flag has potential to make things brittle. The effect of the flag is to: "Give variables taken from the environment precedence over variables from makefiles." Any arbitrary environment variables the user may have set for their own purposes might be unexpectedly overriding important variables from the Makefile(s).
Bug#1024898: mozc: FTBFS on armel
In the hope that working around https://bugs.debian.org/1023525 would fix also this build failure on armel, I NMU'ed a workaround to experimental: https://salsa.debian.org/debian/mozc/-/commit/cc5301a0 It made no difference wrt the armel FTBFS, though. -- Gunnar Hjalmarsson
Processed: rm
Processing commands for cont...@bugs.debian.org: > retitle 943301 RM: zyn -- RoQA; py2 leftover; RC buggy; dead upstream Bug #943301 [src:zyn] zyn: Python2 removal in sid/bullseye Changed Bug title to 'RM: zyn -- RoQA; py2 leftover; RC buggy; dead upstream' from 'zyn: Python2 removal in sid/bullseye'. > reassign 943301 ftp.debian.org Bug #943301 [src:zyn] RM: zyn -- RoQA; py2 leftover; RC buggy; dead upstream Bug reassigned from package 'src:zyn' to 'ftp.debian.org'. No longer marked as found in versions zyn/1+git.20100609+dfsg0-4. Ignoring request to alter fixed versions of bug #943301 to the same values previously set > severity 943301 normal Bug #943301 [ftp.debian.org] RM: zyn -- RoQA; py2 leftover; RC buggy; dead upstream Severity set to 'normal' from 'serious' > retitle 945625 RM: cicero -- RoQA; py2 leftover; dead upstream Bug #945625 [src:cicero] cicero: Python2 removal in sid/bullseye Changed Bug title to 'RM: cicero -- RoQA; py2 leftover; dead upstream' from 'cicero: Python2 removal in sid/bullseye'. > reassign 945625 ftp.debian.org Bug #945625 [src:cicero] RM: cicero -- RoQA; py2 leftover; dead upstream Bug reassigned from package 'src:cicero' to 'ftp.debian.org'. No longer marked as found in versions cicero/0.7.2-5. Ignoring request to alter fixed versions of bug #945625 to the same values previously set > severity 945625 normal Bug #945625 [ftp.debian.org] RM: cicero -- RoQA; py2 leftover; dead upstream Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 943301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943301 945625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle
Processing commands for cont...@bugs.debian.org: > retitle 937695 python-defaults: Python2 removal in sid/bookworm Bug #937695 [src:python-defaults] python-defaults: Python2 removal in sid/bullseye Changed Bug title to 'python-defaults: Python2 removal in sid/bookworm' from 'python-defaults: Python2 removal in sid/bullseye'. > tags 937695 - wontfix Bug #937695 [src:python-defaults] python-defaults: Python2 removal in sid/bookworm Removed tag(s) wontfix. > End of message, stopping processing here. Please contact me if you need assistance. -- 937695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024784: This is a bug in the Python 3.11 interpreter
FYI, this is what it goes down to: https://github.com/python/cpython/pull/99902 So this is a bug in the Python interpreter. There's a Swift patch to work around the issue: https://review.opendev.org/c/openstack/swift/+/866051 I'll probably apply it temporarily, until the Python 3.11 get the fix. Cheers, Thomas Goirand (zigo)
Bug#938639: marked as done (telepathy-haze: Python2 removal in sid/bullseye)
Your message dated Wed, 30 Nov 2022 21:06:58 + with message-id and subject line Bug#938639: fixed in telepathy-haze 0.8.1-0.1 has caused the Debian Bug report #938639, regarding telepathy-haze: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:telepathy-haze Version: 0.8.0-2.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:telepathy-haze If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: telepathy-haze Source-Version: 0.8.1-0.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of telepathy-haze, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated telepathy-haze package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 30 Nov 2022 21:12:31 +0100 Source: telepathy-haze Architecture: source Version: 0.8.1-0.1 Distribution: unstable Urgency: medium Maintainer: Debian Telepathy maintainers Changed-By: Bastian Germann Closes: 938639 Changes: telepathy-haze (0.8.1-0.1) unstable; urgency=medium . * Non-maintainer upload * New upstream version 0.8.1 (Closes: #938639) Checksums-Sha1: 0bc9f7a233be55c13c84769cf7477c1ad34eedc9 1997 telepathy-haze_0.8.1-0.1.dsc 55399e6948f98fca3840e1b430482bb6177401b6 621492 telepathy-haze_0.8.1.orig.tar.gz f7c5c1a34171f382c127d5f5294df2793002bfca 4332 telepathy-haze_0.8.1-0.1.debian.tar.xz 05402e764cba833a567ec9fd899c696537271c0d 9525 telepathy-haze_0.8.1-0.1_source.buildinfo Checksums-Sha256: 8359aecb2a194d34eb276a8085335344d664aa9667e5c53ee7b2735ee0867466 1997 telepathy-haze_0.8.1-0.1.dsc 704befa42eec2173eca4bac01ffd004014665f2bad46dc8948e5423364cde30a 62149
Bug#1025203: r-cran-glmmtmb: FTBFS on mipsel
Source: r-cran-glmmtmb Version: 1.1.4+dfsg-3 Severity: serious Tags: ftbfs Justification: ftbfs Dear maintainer(s), Your package failed to build from source on mipsel, where it built successfully in the past. Paul https://buildd.debian.org/status/fetch.php?pkg=r-cran-glmmtmb&arch=mipsel&ver=1.1.5%2Bdfsg-1&stamp=1669057119&raw=0 dh binary-arch --buildsystem R dh_update_autotools_config -a -O--buildsystem=R dh_autoreconf -a -O--buildsystem=R dh_auto_configure -a -O--buildsystem=R dh_auto_build -a -O--buildsystem=R dh_auto_test -a -O--buildsystem=R create-stamp debian/debhelper-build-stamp dh_testroot -a -O--buildsystem=R dh_prep -a -O--buildsystem=R dh_auto_install --destdir=debian/r-cran-glmmtmb/ -a -O--buildsystem=R I: R packages needed for DEP8: glmmtmb I: R Package: glmmTMB Version: 1.1.5 I: Building using R version 4.2.2.20221110-1 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Fri, 18 Nov 2022 11:40:30 +0100 mkdir -p /<>/r-cran-glmmtmb-1.1.5\+dfsg/debian/r-cran-glmmtmb/usr/lib/R/site-library R CMD INSTALL -l /<>/r-cran-glmmtmb-1.1.5\+dfsg/debian/r-cran-glmmtmb/usr/lib/R/site-library --clean . "--built-timestamp='Fri, 18 Nov 2022 11:40:30 +0100'" * installing *source* package ‘glmmTMB’ ... files ‘inst/doc/covstruct.html’, ‘inst/doc/hacking.html’, ‘inst/doc/mcmc.html’, ‘inst/doc/miscEx.html’, ‘inst/doc/parallel.html’, ‘inst/doc/sim.html’, ‘inst/doc/troubleshooting.html’ are missing file ‘DESCRIPTION’ has the wrong MD5 checksum ** using staged installation ** libs make[1]: Entering directory '/<>/src' g++ -std=gnu++14 -I"/usr/share/R/include" -DNDEBUG -DTMBAD_FRAMEWORK -I'/usr/lib/R/site-library/TMB/include' -I'/usr/lib/R/site-library/RcppEigen/include' -fopenmp -fpic -g -O2 -ffile-prefix-map=/build/r-base-jMlmip/r-base-4.2.2.20221110=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c glmmTMB.cpp -o glmmTMB.o cc1plus: out of memory allocating 1058400 bytes after a total of 59473920 bytes make[1]: *** [/usr/lib/R/etc/Makeconf:178: glmmTMB.o] Error 1 make[1]: Leaving directory '/<>/src' make[1]: Entering directory '/<>/src' make[1]: Leaving directory '/<>/src' ERROR: compilation failed for package ‘glmmTMB’ * removing ‘/<>/debian/r-cran-glmmtmb/usr/lib/R/site-library/glmmTMB’ dh_auto_install: error: R CMD INSTALL -l /<>/r-cran-glmmtmb-1.1.5\+dfsg/debian/r-cran-glmmtmb/usr/lib/R/site-library --clean . "--built-timestamp='Fri, 18 Nov 2022 11:40:30 +0100'" returned exit code 1 make: *** [debian/rules:4: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2
Bug#1025202: gscan2pdf: autopkgtest regression: Can't open scanners/Brother_DCP-7025
Source: gscan2pdf Version: 2.13.0-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of gscan2pdf the autopkgtest of gscan2pdf fails in testing when that autopkgtest is run with the binary packages of gscan2pdf from unstable. It passes when run with only packages from testing. In tabular form: passfail gscan2pdf from testing2.13.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 to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gscan2pdf https://ci.debian.net/data/autopkgtest/testing/amd64/g/gscan2pdf/28805770/log.gz t/01_NetPBM.t . 1..14 ok 1 - use Gscan2pdf::NetPBM; ok 2 - get_size_from_PNM pbm 8x5 depth 8 ok 3 - get_size_from_PNM pbm 9x6 depth 8 ok 4 - get_size_from_PNM pbm 8x5 depth 16 ok 5 - get_size_from_PNM pbm 9x6 depth 16 ok 6 - get_size_from_PNM pgm 8x5 depth 8 ok 7 - get_size_from_PNM pgm 9x6 depth 8 ok 8 - get_size_from_PNM pgm 8x5 depth 16 ok 9 - get_size_from_PNM pgm 9x6 depth 16 ok 10 - get_size_from_PNM ppm 8x5 depth 8 ok 11 - get_size_from_PNM ppm 9x6 depth 8 ok 12 - get_size_from_PNM ppm 8x5 depth 16 ok 13 - get_size_from_PNM ppm 9x6 depth 16 ok 14 - 0-length PNM ok t/02_Scanner_Options_Brother_DCP-7025.t ... 1..3 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/Brother_DCP-7025: No such file or directory at t/02_Scanner_Options_Brother_DCP-7025.t line 10. Error: no options supplied at t/02_Scanner_Options_Brother_DCP-7025.t line 11. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/3 subtests t/02_Scanner_Options_Brother_MFC_5100c.t .. 1..4 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/Brother_MFC_5100c: No such file or directory at t/02_Scanner_Options_Brother_MFC_5100c.t line 11. Error: no options supplied at t/02_Scanner_Options_Brother_MFC_5100c.t line 12. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 3/4 subtests t/02_Scanner_Options_Brother_MFC_8860DN.t . 1..4 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/Brother_MFC-8860DN: No such file or directory at t/02_Scanner_Options_Brother_MFC_8860DN.t line 11. Error: no options supplied at t/02_Scanner_Options_Brother_MFC_8860DN.t line 12. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 3/4 subtests t/02_Scanner_Options_brother.t 1..3 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/brother: No such file or directory at t/02_Scanner_Options_brother.t line 10. Error: no options supplied at t/02_Scanner_Options_brother.t line 11. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/3 subtests t/02_Scanner_Options_canonLiDE25.t 1..3 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/canonLiDE25: No such file or directory at t/02_Scanner_Options_canonLiDE25.t line 10. Error: no options supplied at t/02_Scanner_Options_canonLiDE25.t line 11. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/3 subtests t/02_Scanner_Options_canoscan_FB_630P.t ... 1..3 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/canoscan_FB_630P: No such file or directory at t/02_Scanner_Options_canoscan_FB_630P.t line 10. Error: no options supplied at t/02_Scanner_Options_canoscan_FB_630P.t line 11. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/3 subtests t/02_Scanner_Options_epson1.t . 1..4 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/epson1: No such file or directory at t/02_Scanner_Options_epson1.t line 11. Error: no options supplied at t/02_Scanner_Options_epson1.t line 12. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 3/4 subtests t/02_Scanner_Options_epson_3490.t . 1..3 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/epson_3490: No such file or directory at t/02_Scanner_Options_epson_3490.t line 10. Error: no options supplied at t/02_Scanner_Options_epson_3490.t line 11. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/3 subtests t/02_Scanner_Options_epson_gt_2500.t .. 1..4 ok 1 - use Gscan2pdf::Scanner::Options; Can't open scanners/Epson_GT-2500: No such file or directory at t/02_Scanner_Options_epson_gt_2500.t line 11. Error: no options supplied at
Processed: raise severity (python2-rm)
Processing commands for cont...@bugs.debian.org: > severity 936323 serious Bug #936323 [src:condor] condor: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 943061 serious Bug #943061 [src:faumachine] faumachine: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938645 normal Bug #938645 [src:telepathy-salut] telepathy-salut: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > retitle 938645 RM: telepathy-salut -- RoQA; py2 leftover; dead upstream Bug #938645 [src:telepathy-salut] telepathy-salut: Python2 removal in sid/bullseye Changed Bug title to 'RM: telepathy-salut -- RoQA; py2 leftover; dead upstream' from 'telepathy-salut: Python2 removal in sid/bullseye'. > reassign 938645 ftp.debian.org Bug #938645 [src:telepathy-salut] RM: telepathy-salut -- RoQA; py2 leftover; dead upstream Bug reassigned from package 'src:telepathy-salut' to 'ftp.debian.org'. No longer marked as found in versions telepathy-salut/0.8.1-5.1 and telepathy-salut/0.8.1-7. Ignoring request to alter fixed versions of bug #938645 to the same values previously set > severity 943113 serious Bug #943113 [src:lvtk] lvtk: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 942993 serious Bug #942993 [src:dmtcp] dmtcp: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 951902 serious Bug #951902 [src:duktape] duktape: python2 is required to regenerate some source files Severity set to 'serious' from 'normal' > severity 943301 serious Bug #943301 [src:zyn] zyn: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 945665 serious Bug #945665 [src:dump1090-mutability] dump1090-mutability: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936323 938645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938645 942993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942993 943061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943061 943113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943113 943301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943301 945665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945665 951902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tkcalendar: (autopkgtest) needs update for two supported python versions: Xvfb failed to start
Processing control commands: > affects -1 src:python3-defaults Bug #1025201 [src:tkcalendar] tkcalendar: (autopkgtest) needs update for two supported python versions: Xvfb failed to start Added indication that 1025201 affects src:python3-defaults -- 1025201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025201: tkcalendar: (autopkgtest) needs update for two supported python versions: Xvfb failed to start
Source: tkcalendar Version: 1.6.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 tkcalendar 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 tkcalendar from testing1.6.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/t/tkcalendar/28796449/log.gz === python3.11 === test_calendar_buttons_functions (tests.test_calendar.TestCalendar.test_calendar_buttons_functions) ... ok test_calendar_calevents (tests.test_calendar.TestCalendar.test_calendar_calevents) ... ok test_calendar_get_set (tests.test_calendar.TestCalendar.test_calendar_get_set) ... ok test_calendar_init (tests.test_calendar.TestCalendar.test_calendar_init) ... ok test_calendar_other_fcts (tests.test_calendar.TestCalendar.test_calendar_other_fcts) ... ok test_calendar_selection (tests.test_calendar.TestCalendar.test_calendar_selection) ... ok test_calendar_virtual_events (tests.test_calendar.TestCalendar.test_calendar_virtual_events) ... ok test_dateentry_drop_down (tests.test_dateentry.TestDateEntry.test_dateentry_drop_down) Check whether drop down opens on click. ... ok test_dateentry_functions (tests.test_dateentry.TestDateEntry.test_dateentry_functions) ... ok test_dateentry_get_set (tests.test_dateentry.TestDateEntry.test_dateentry_get_set) ... ok test_dateentry_init (tests.test_dateentry.TestDateEntry.test_dateentry_init) ... ok test_tooltip (tests.test_tooltip.TestTooltip.test_tooltip) ... ok test_tooltip_config (tests.test_tooltip.TestTooltipWrapper.test_tooltip_config) ... ok test_tooltipwrapper (tests.test_tooltip.TestTooltipWrapper.test_tooltipwrapper) ... ok test_tooltipwrapper_init (tests.test_tooltip.TestTooltipWrapper.test_tooltipwrapper_init) ... ok -- Ran 15 tests in 0.734s OK === python3.10 === xvfb-run: error: Xvfb failed to start autopkgtest [01:17:47]: test unittest OpenPGP_signature Description: OpenPGP digital signature
Bug#1025200: ruby-mime-types-data breaks ruby-mime-types autopkgtest: not found
Source: ruby-mime-types-data, ruby-mime-types Control: found -1 ruby-mime-types-data/3.2022.0105-1 Control: found -1 ruby-mime-types/3.4.1-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of ruby-mime-types-data the autopkgtest of ruby-mime-types fails in testing when that autopkgtest is run with the binary packages of ruby-mime-types-data from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-mime-types-data from testing3.2022.0105-1 ruby-mime-typesfrom testing3.4.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 ruby-mime-types-data to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-mime-types-data https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-mime-types/28796478/log.gz /tmp/autopkgtest-lxc.l3u7sp3x/downtmp/wrapper.sh: 124: exec: /tmp/autopkgtest-lxc.l3u7sp3x/downtmp/build.oKA/src/debian/tests/smoke-test: not found autopkgtest [01:22:31]: test smoke-test OpenPGP_signature Description: OpenPGP digital signature
Processed: ruby-mime-types-data breaks ruby-mime-types autopkgtest: not found
Processing control commands: > found -1 ruby-mime-types-data/3.2022.0105-1 Bug #1025200 [src:ruby-mime-types-data, src:ruby-mime-types] ruby-mime-types-data breaks ruby-mime-types autopkgtest: not found Marked as found in versions ruby-mime-types-data/3.2022.0105-1. > found -1 ruby-mime-types/3.4.1-1 Bug #1025200 [src:ruby-mime-types-data, src:ruby-mime-types] ruby-mime-types-data breaks ruby-mime-types autopkgtest: not found Marked as found in versions ruby-mime-types/3.4.1-1. -- 1025200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025197: zope.exceptions: (autopkgtest) needs update for python3.11: 'DummyTB' object has no attribute 'tb_lasti'
Source: zope.exceptions
Version: 4.5-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
zope.exceptions 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
zope.exceptionsfrom testing4.5-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/z/zope.exceptions/28796455/log.gz
=== FAILURES
===
TextExceptionFormatterTests.test_formatException_recursion_in_tb_stack
self =
testMethod=test_formatException_recursion_in_tb_stack>
def test_formatException_recursion_in_tb_stack(self):
import traceback
fmt = self._makeOne()
err = ValueError('testing')
tb_recurse = DummyTB()
tb_recurse.tb_lineno = 27
r_f = tb_recurse.tb_frame = DummyFrame()
r_f.f_lineno = 27
r_f.f_locals['__exception_formatter__'] = 1
tb = DummyTB()
tb.tb_frame = DummyFrame()
tb.tb_next = tb_recurse
lines = fmt.formatException(ValueError, err, tb)
/usr/lib/python3/dist-packages/zope/exceptions/tests/test_exceptionformatter.py:347:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/zope/exceptions/exceptionformatter.py:186:
in formatException
result.extend(traceback.format_tb(tb))
/usr/lib/python3.11/traceback.py:59: in format_tb
return extract_tb(tb, limit=limit).format()
/usr/lib/python3.11/traceback.py:74: in extract_tb
return StackSummary._extract_from_extended_frame_gen(
/usr/lib/python3.11/traceback.py:416: in _extract_from_extended_frame_gen
for f, (lineno, end_lineno, colno, end_colno) in frame_gen:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
tb = 0x7fea63c25110>
def _walk_tb_with_full_positions(tb):
# Internal version of walk_tb that yields full code positions
including
# end line and column information.
while tb is not None:
positions = _get_code_position(tb.tb_frame.f_code, tb.tb_lasti)
E AttributeError: 'DummyTB' object has no attribute 'tb_lasti'
/usr/lib/python3.11/traceback.py:353: AttributeError
=== warnings summary
===
../../../../usr/lib/python3/dist-packages/zope/exceptions/tests/test_exceptionformatter.py:869
/usr/lib/python3/dist-packages/zope/exceptions/tests/test_exceptionformatter.py:869:
PytestCollectionWarning: cannot collect test class
'TestingTracebackSupplement' because it has a __init__ constructor
(from: tests/test_exceptionformatter.py)
class TestingTracebackSupplement(object):
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info
FAILED
tests/test_exceptionformatter.py::TextExceptionFormatterTests::test_formatException_recursion_in_tb_stack
=== 1 failed, 79 passed, 1 warning in 0.18s
autopkgtest [01:18:35]: test upstream-unittest
OpenPGP_signature
Description: OpenPGP digital signature
Processed: zope.exceptions: (autopkgtest) needs update for python3.11: 'DummyTB' object has no attribute 'tb_lasti'
Processing control commands: > affects -1 src:python3-defaults Bug #1025197 [src:zope.exceptions] zope.exceptions: (autopkgtest) needs update for python3.11: 'DummyTB' object has no attribute 'tb_lasti' Added indication that 1025197 affects src:python3-defaults -- 1025197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: zfp: (autopkgtest) needs update for python3.11: No module named 'zfpy'
Processing control commands: > affects -1 src:python3-defaults Bug #1025196 [src:zfp] zfp: (autopkgtest) needs update for python3.11: No module named 'zfpy' Added indication that 1025196 affects src:python3-defaults -- 1025196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025196: zfp: (autopkgtest) needs update for python3.11: No module named 'zfpy'
Source: zfp Version: 1.0.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 zfp 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 zfpfrom testing1.0.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/z/zfp/28796454/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'zfpy' autopkgtest [01:18:36]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Bug#1025195: watcher-dashboard: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Source: watcher-dashboard
Version: 8.0.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
watcher-dashboard 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
watcher-dashboard from testing8.0.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/w/watcher-dashboard/28796452/log.gz
Running migrations:
Applying contenttypes.0001_initial... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying auth.0001_initial... OK
Applying auth.0002_alter_permission_name_max_length... OK
Applying auth.0003_alter_user_email_max_length... OK
Applying auth.0004_alter_user_username_opts... OK
Applying auth.0005_alter_user_last_login_null... OK
Applying auth.0006_require_contenttypes_0002... OK
Applying auth.0007_alter_validators_add_error_messages... OK
Applying auth.0008_alter_user_username_max_length... OK
Applying auth.0009_alter_user_last_name_max_length... OK
Applying auth.0010_alter_group_name_max_length... OK
Applying auth.0011_update_proxy_permissions... OK
Applying auth.0012_alter_user_first_name_max_length... OK
Applying sessions.0001_initial... OK
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared')...
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.2p5z09al/downtmp/build.k2W/src/manage.py",
line 23, in
execute_from_command_line(sys.argv)
File
"/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 419, in execute_from_command_line
utility.execute()
File
"/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
line 23, in run_from_argv
super().run_from_argv(argv)
File "/usr/lib/python3/dist-packages/django/core/management/base.py",
line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py",
line 398, in execute
output = self.handle(*args, **options)
^
File
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
line 55, in handle
failures = test_runner.run_tests(test_labels)
^^
File "/usr/lib/python3/dist-packages/django/test/runner.py", line
728, in run_tests
self.run_checks(databases)
File "/usr/lib/python3/dist-packages/django/test/runner.py", line
665, in run_checks
call_command('check', verbosity=self.verbosity, databases=databases)
File
"/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 181, in call_command
return command.execute(*args, **defaults)
^^
File "/usr/lib/python3/dist-packages/django/core/management/base.py",
line 398, in execute
output = self.handle(*args, **options)
^
File
"/usr/lib/python3/dist-packages/django/core/management/commands/check.py",
line 63, in handle
self.check(
File "/usr/lib/python3/dist-packages/django/core/management/base.py",
line 419, in check
all_issues = checks.run_checks(
^^
File "/usr/lib/python3/dist-packages/django/core/checks/registry.py",
line 76, in run_checks
new_errors = check(app_configs=app_configs, databases=databases)
^^^
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py",
line 13, in check_url_config
return check_resolver(resolver)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py",
line 23, in check_resolver
return check_method()
^^
File "/usr/lib/python3/dist-packages
Processed: watcher-dashboard: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Processing control commands: > affects -1 src:python3-defaults Bug #1025195 [src:watcher-dashboard] watcher-dashboard: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' Added indication that 1025195 affects src:python3-defaults -- 1025195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025194: tpot: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Source: tpot Version: 0.11.7+dfsg-4 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 tpot 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 tpot from testing0.11.7+dfsg-4 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/t/tpot/28796450/log.gz == ERROR: Assert that get_params returns the exact dictionary of parameters used by TPOT. -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/tmp/autopkgtest-lxc.aob2cy93/downtmp/autopkgtest_tmp/python3.11/tests/tpot_tests.py", line 480, in test_get_params initializer = inspect.getargspec(TPOTBase.__init__) ^^ AttributeError: module 'inspect' has no attribute 'getargspec' -- Ran 249 tests in 50.080s OpenPGP_signature Description: OpenPGP digital signature
Processed: tagpy: (autopkgtest) needs update for python3.11: initialization of _tagpy raised unreported exception
Processing control commands: > affects -1 src:python3-defaults Bug #1025193 [src:tagpy] tagpy: (autopkgtest) needs update for python3.11: initialization of _tagpy raised unreported exception Added indication that 1025193 affects src:python3-defaults -- 1025193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tpot: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Processing control commands: > affects -1 src:python3-defaults Bug #1025194 [src:tpot] tpot: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' Added indication that 1025194 affects src:python3-defaults -- 1025194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025193: tagpy: (autopkgtest) needs update for python3.11: initialization of _tagpy raised unreported exception
Source: tagpy Version: 2013.1-9 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 tagpy 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 tagpy from testing2013.1-9 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/t/tagpy/28796448/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/tagpy/__init__.py", line 24, in import _tagpy SystemError: initialization of _tagpy raised unreported exception autopkgtest [01:17:35]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Bug#1025192: sublime-music: (autopkgtest) needs update for python3.11: mutable default for field current_album_search_query is not allowed
Source: sublime-music
Version: 0.11.16-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
sublime-music 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
sublime-music from testing0.11.16-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/s/sublime-music/28796444/log.gz
=== python3.11 ===
= test session starts
==
platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack --
/usr/bin/python3.11
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.1ezw684c/downtmp/autopkgtest_tmp,
configfile: setup.cfg
collecting ... collected 0 items / 12 errors
ERRORS
ERROR collecting tests/config_test.py
_
tests/config_test.py:6: in
from sublime_music.adapters import ConfigurationStore
/usr/lib/python3/dist-packages/sublime_music/adapters/__init__.py:11: in
from .manager import AdapterManager, DownloadProgress, Result,
SearchResult
/usr/lib/python3/dist-packages/sublime_music/adapters/manager.py:33: in
from sublime_music.config import ProviderConfiguration
/usr/lib/python3/dist-packages/sublime_music/config.py:12: in
from .ui.state import UIState
/usr/lib/python3/dist-packages/sublime_music/ui/state.py:41: 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 'sublime_music.adapters.adapter_base.AlbumSearchQuery'> for field
current_album_search_query is not allowed: use default_factory
ERROR collecting tests/config_test.py
_
tests/config_test.py:6: in
from sublime_music.adapters import ConfigurationStore
/usr/lib/python3/dist-packages/sublime_music/adapters/__init__.py:11: in
from .manager import AdapterManager, DownloadProgress, Result,
SearchResult
/usr/lib/python3/dist-packages/sublime_music/adapters/manager.py:33: in
from sublime_music.config import ProviderConfiguration
/usr/lib/python3/dist-packages/sublime_music/config.py:12: in
from .ui.state import UIState
/usr/lib/python3/dist-packages/sublime_music/ui/state.py:41: 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 'sublime_music.adapters.adapter_base.AlbumSearchQuery'> for field
current_album_search_query is not allowed: use default_factory
ERROR collecting tests/adapter_tests/adapter_manager_tests.py
_
tests/adapter_tests/adapter_manager_tests.py:6: in
from sublime_music.adapters import (
/usr/lib/python3/dist-packages/sublime_music/adapters/__init__.py:11: in
from .manager import AdapterManager, DownloadProgress, Result,
SearchResult
/usr/lib/python3/dist-packages/sublime_music/adapters/manager.py:33: in
from sublime_music.config import ProviderConfiguration
/usr/lib/python3/dist-packages/sublime_music/config.py:12: in
from .ui.state import UIState
/usr/lib/python3/dist-packages/sublime_music/ui/state.py:41: in
@dataclass
/usr/lib/python3.11/dataclasses.py:1220: in dataclass
Bug#1021857: CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message):
btw, do you know what caused this in cmake? (seems that it is caused by a new cmake version). (or not to make sure that all binaries aren't exported?) thanks Sylvestre Le 28/11/2022 à 12:07, Mathieu Malaterre a écrit : Control: found 1021857 1:14.0.6-2 -- Found LibXml2: /usr/lib/x86_64-linux-gnux32/libxml2.so (found version "2.9.14") CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message): The imported target "mlir-tblgen" references the file "/usr/lib/llvm-14/bin/mlir-tblgen" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) openvdb_ax/openvdb_ax/CMakeLists.txt:105 (find_package) * https://buildd.debian.org/status/fetch.php?pkg=openvdb&arch=x32&ver=10.0.0-7&stamp=1669627540&raw=0 ___ Pkg-llvm-team mailing list pkg-llvm-t...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team
Processed: sublime-music: (autopkgtest) needs update for python3.11: mutable default for field current_album_search_query is not allowed
Processing control commands: > affects -1 src:python3-defaults Bug #1025192 [src:sublime-music] sublime-music: (autopkgtest) needs update for python3.11: mutable default for field current_album_search_query is not allowed Added indication that 1025192 affects src:python3-defaults -- 1025192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025190: sqlitedict: (autopkgtest) needs update for python3.11: AssertionError
Source: sqlitedict
Version: 2.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
sqlitedict 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
sqlitedict from testing2.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/s/sqlitedict/28796443/log.gz
=== FAILURES
===
TablenamesTest.test_tablenames
self =
def test_tablenames(self):
fname = norm_file('tests/db/tablenames-test-1.sqlite')
SqliteDict(fname)
self.assertEqual(SqliteDict.get_tablenames(fname), ['unnamed'])
fname = norm_file('tests/db/tablenames-test-2.sqlite')
with SqliteDict(fname, tablename='table1'):
self.assertEqual(SqliteDict.get_tablenames(fname), ['table1'])
E AssertionError: Lists differ: ['table1', 'table2'] != ['table1']
E E First list contains 1 additional elements.
E First extra element 1:
E 'table2'
E E - ['table1', 'table2']
E + ['table1']
tests/test_core.py:293: AssertionError
OpenPGP_signature
Description: OpenPGP digital signature
Processed: sqlitedict: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025190 [src:sqlitedict] sqlitedict: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025190 affects src:python3-defaults -- 1025190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025189: spyder: (autopkgtest) needs update for python3.11: Signal sig_response(QString,PyQt_PyObject) not emitted after 30000 ms
Source: spyder
Version: 5.3.3+dfsg-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
spyder 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
spyder from testing5.3.3+dfsg-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/s/spyder/28806955/log.gz
=== FAILURES
===
__ test_plugin_first_response_request
__
qtbot_module =
completion_receiver =
(0x7fb1231c7a30>,
object at 0x7fb11dcc7910>)
@pytest.mark.order(1)
def test_plugin_first_response_request(qtbot_module,
completion_receiver):
completion, receiver = completion_receiver
# Parameters to perform a textDocument/didOpen request
params = {
'file': 'test2.py',
'language': 'python',
'version': 2,
'text': "# This is some text with some classe\nimport os\n\n",
'response_instance': receiver,
'offset': 1,
'diff': '',
'selection_start': 0,
'selection_end': 0,
'codeeditor': receiver,
'requires_response': False
}
with qtbot_module.waitSignal(receiver.sig_response,
timeout=3) as blocker:
completion.send_request(
'python', CompletionRequestTypes.DOCUMENT_DID_OPEN, params)
params = {
'file': 'test2.py',
'line': 1,
'column': 8,
'offset': 43,
'diff': '',
'response_instance': receiver,
'codeeditor': receiver,
'requires_response': True
}
with qtbot_module.waitSignal(receiver.sig_response,
timeout=3) as blocker:
completion.send_request(
'python', CompletionRequestTypes.DOCUMENT_HOVER, params)
_, response = blocker.args
assert len(response['params']) > 0
E AssertionError: assert 0 > 0
E+ where 0 = len('')
spyder/plugins/completion/tests/test_plugin.py:253: AssertionError
___ test_get_signature[lsp_provider]
___
lsp_client_and_completion =
(object at 0x7fb11da1eb00>,
object at 0x7fb11da1ed40>)
qtbot =
@pytest.mark.order(3)
def test_get_signature(lsp_client_and_completion, qtbot):
client, completion = lsp_client_and_completion
# Parameters to perform a textDocument/didChange request
params = {
'file': 'test.py',
'language': 'python',
'version': 1,
'text': "import os\nos.walk(\n",
'codeeditor': completion,
'requires_response': False
}
# Perform the request
with qtbot.waitSignal(completion.sig_response, timeout=3):
E pytestqt.exceptions.TimeoutError: Signal
sig_response(QString,PyQt_PyObject) not emitted after 3 ms
spyder/plugins/completion/providers/languageserver/tests/test_client.py:76:
TimeoutError
__ test_get_completions[lsp_provider]
__
lsp_client_and_completion =
(object at 0x7fb11da1eb00>,
object at 0x7fb11da1ed40>)
qtbot =
@pytest.mark.order(3)
def test_get_completions(lsp_client_and_completion, qtbot):
client, completion = lsp_client_and_completion
# Parameters to perform a textDocument/didChange request
params = {
'file': 'test.py',
'language': 'python',
'version': 1,
'text': "import o",
'codeeditor': completion,
'requires_response': False
}
# Perform the request
with qtbot.waitSignal(completion.sig_response, timeout=3):
E pytestqt.exceptions.TimeoutError: Signal
sig_response(QString,PyQt_PyObject) not emitted after 3 ms
spyde
Processed: spyder: (autopkgtest) needs update for python3.11: Signal sig_response(QString,PyQt_PyObject) not emitted after 30000 ms
Processing control commands: > affects -1 src:python3-defaults Bug #1025189 [src:spyder] spyder: (autopkgtest) needs update for python3.11: Signal sig_response(QString,PyQt_PyObject) not emitted after 3 ms Added indication that 1025189 affects src:python3-defaults -- 1025189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025188: spyder-unittest: (autopkgtest) needs update for python3.11: AssertionError
Source: spyder-unittest
Version: 0.5.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
spyder-unittest 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
spyder-unittestfrom testing0.5.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/s/spyder-unittest/28796442/log.gz
=== FAILURES
===
__ test_run_tests_using_unittest_and_display_results
___
qtbot =
widget = 0x7fd5120a29e0>
tmpdir =
local('/tmp/pytest-of-debci/pytest-0/test_run_tests_using_unittest_0')
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7fd5120bba10>
def test_run_tests_using_unittest_and_display_results(
qtbot, widget, tmpdir, monkeypatch):
"""Basic check."""
os.chdir(tmpdir.strpath)
testfilename = tmpdir.join('test_foo.py').strpath
with open(testfilename, 'w') as f:
f.write("import unittest\n"
"class MyTest(unittest.TestCase):\n"
" def test_ok(self): self.assertEqual(1+1, 2)\n"
" def test_fail(self): self.assertEqual(1+1, 3)\n")
MockQMessageBox = Mock()
monkeypatch.setattr('spyder_unittest.widgets.unittestgui.QMessageBox',
MockQMessageBox)
config = Config(wdir=tmpdir.strpath, framework='unittest',
coverage=False)
with qtbot.waitSignal(widget.sig_finished, timeout=1,
raising=True):
widget.run_tests(config)
MockQMessageBox.assert_not_called()
model = widget.testdatamodel
assert model.rowCount() == 2
assert model.index(0, 0).data(Qt.DisplayRole) == 'FAIL'
assert model.index(0, 1).data(Qt.DisplayRole) == 't.M.test_fail'
E AssertionError: assert 't.M.test_f.test_fail' == 't.M.test_fail'
E - t.M.test_fail
E + t.M.test_f.test_fail
E ? +++
/tmp/autopkgtest-lxc.6hcp6lhp/downtmp/build.hJ9/src/spyder_unittest/widgets/tests/test_unittestgui.py:210:
AssertionError
OpenPGP_signature
Description: OpenPGP digital signature
Processed: spyder-unittest: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025188 [src:spyder-unittest] spyder-unittest: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025188 affects src:python3-defaults -- 1025188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025187: golang-github-crewjam-saml: CVE-2022-41912: Signature bypass via multiple Assertion elements
Source: golang-github-crewjam-saml Version: 0.4.6-3 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for golang-github-crewjam-saml. CVE-2022-41912[0]: | The crewjam/saml go library prior to version 0.4.9 is vulnerable to an | authentication bypass when processing SAML responses containing | multiple Assertion elements. This issue has been corrected in version | 0.4.9. There are no workarounds other than upgrading to a fixed | version. 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-41912 https://www.cve.org/CVERecord?id=CVE-2022-41912 [1] https://github.com/crewjam/saml/security/advisories/GHSA-j2jp-wvqg-wc2g Regards, Salvatore
Bug#1025185: sphinx: (autopkgtest) needs update for python3.11: AssertionError
Source: sphinx Version: 4.5.0-4 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 sphinx 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 sphinx from testing4.5.0-4 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/s/sphinx/28796439/log.gz === FAILURES === _ test_restify _ def test_restify(): assert restify(int) == ":py:class:`int`" assert restify(int, "smart") == ":py:class:`int`" assert restify(str) == ":py:class:`str`" assert restify(str, "smart") == ":py:class:`str`" assert restify(None) == ":py:obj:`None`" assert restify(None, "smart") == ":py:obj:`None`" assert restify(Integral) == ":py:class:`numbers.Integral`" assert restify(Integral, "smart") == ":py:class:`~numbers.Integral`" assert restify(Struct) == ":py:class:`struct.Struct`" assert restify(Struct, "smart") == ":py:class:`~struct.Struct`" assert restify(TracebackType) == ":py:class:`types.TracebackType`" assert restify(TracebackType, "smart") == ":py:class:`~types.TracebackType`" > assert restify(Any) == ":py:obj:`~typing.Any`" E AssertionError: assert ':py:class:`~typing.Any`' == ':py:obj:`~typing.Any`' E - :py:obj:`~typing.Any` E ? ^^^ E + :py:class:`~typing.Any` E ? ^ tests/test_util_typing.py:55: AssertionError OpenPGP_signature Description: OpenPGP digital signature
Processed: sphinx: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025185 [src:sphinx] sphinx: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025185 affects src:python3-defaults -- 1025185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025184: sphinx-testing: (autopkgtest) needs update for python3.11: invalid mode: 'U'
Source: sphinx-testing Version: 1.0.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 sphinx-testing 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 sphinx-testing from testing1.0.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/s/sphinx-testing/28796440/log.gz /usr/lib/python3/dist-packages/babel/messages/catalog.py:13: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13 from cgi import parse_header test_abspath (test_path.TestPath.test_abspath) ... ok test_basename (test_path.TestPath.test_basename) ... ok test_copytree (test_path.TestPath.test_copytree) ... ok test_dirname (test_path.TestPath.test_dirname) ... ok test_exists (test_path.TestPath.test_exists) ... ok test_instantiate (test_path.TestPath.test_instantiate) ... ok test_isabs (test_path.TestPath.test_isabs) ... ok test_isdir (test_path.TestPath.test_isdir) ... ok test_isfile (test_path.TestPath.test_isfile) ... ok test_islink (test_path.TestPath.test_islink) ... ok test_ismount (test_path.TestPath.test_ismount) ... ok test_jonpath (test_path.TestPath.test_jonpath) ... ok test_listdir (test_path.TestPath.test_listdir) ... ok test_makedirs (test_path.TestPath.test_makedirs) ... ok test_move (test_path.TestPath.test_move) ... ok test_read_bytes (test_path.TestPath.test_read_bytes) ... ok test_read_text (test_path.TestPath.test_read_text) ... ERROR test_rmtree (test_path.TestPath.test_rmtree) ... ok test_suffix (test_path.TestPath.test_suffix) ... ok test_unlink (test_path.TestPath.test_unlink) ... ok test_utime (test_path.TestPath.test_utime) ... ok test_write_bytes (test_path.TestPath.test_write_bytes) ... /tmp/autopkgtest-lxc.yr0akpjp/downtmp/autopkgtest_tmp/tests/test_path.py:226: ResourceWarning: unclosed file <_io.BufferedReader name='/tmp/tmpkuvdvjne/test.file'> text = open(filename, 'rb').read() ResourceWarning: Enable tracemalloc to get the object allocation traceback ok test_write_text (test_path.TestPath.test_write_text) ... /tmp/autopkgtest-lxc.yr0akpjp/downtmp/autopkgtest_tmp/tests/test_path.py:210: ResourceWarning: unclosed file <_io.TextIOWrapper name='/tmp/tmp4l6oluer/test.file' mode='r' encoding='UTF-8'> text = open(filename).read() ResourceWarning: Enable tracemalloc to get the object allocation traceback ok test_mkdtemp (test_tmpdir.TestTmpdir.test_mkdtemp) ... ok test_with_tmpdir (test_tmpdir.TestTmpdir.test_with_tmpdir) ... ok test_TestApp (test_util.TestSphinxTesting.test_TestApp) ... /usr/lib/python3/dist-packages/sphinx/util/images.py:4: DeprecationWarning: 'imghdr' is deprecated and slated for removal in Python 3.13 import imghdr ok test_TestApp_cleanup (test_util.TestSphinxTesting.test_TestApp_cleanup) ... ok test_TestApp_cleanup_when_cleanup_on_errors (test_util.TestSphinxTesting.test_TestApp_cleanup_when_cleanup_on_errors) ... ok test_TestApp_when_copy_srcdir_to_tmpdir (test_util.TestSphinxTesting.test_TestApp_when_copy_srcdir_to_tmpdir) ... ERROR test_TestApp_when_create_new_srcdir (test_util.TestSphinxTesting.test_TestApp_when_create_new_srcdir) ... ERROR test_TestApp_when_srcdir_and_create_new_srcdir_conflict (test_util.TestSphinxTesting.test_TestApp_when_srcdir_and_create_new_srcdir_conflict) ... ok test_TestApp_when_srcdir_is_None (test_util.TestSphinxTesting.test_TestApp_when_srcdir_is_None) ... ok test_TestApp_when_srcdir_specified (test_util.TestSphinxTesting.test_TestApp_when_srcdir_specified) ... ERROR test_with_app (test_util.TestSphinxTesting.test_with_app) ... ok test_with_app_bad_args (test_util.TestSphinxTesting.test_with_app_bad_args) ... ok test_with_app_return_value (test_util.TestSphinxTesting.test_with_app_return_value) ... ok test_with_app_write_docstring (test_util.TestSphinxTesting.test_with_app_write_docstring) ... ERROR test_with_app_write_docstring_by_name (test_util.TestSphinxTesting.test_with_app_write_d
Processed: sphinx-testing: (autopkgtest) needs update for python3.11: invalid mode: 'U'
Processing control commands: > affects -1 src:python3-defaults Bug #1025184 [src:sphinx-testing] sphinx-testing: (autopkgtest) needs update for python3.11: invalid mode: 'U' Added indication that 1025184 affects src:python3-defaults -- 1025184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025183: silx: (autopkgtest) needs update for python3.11: Segmentation fault
Source: silx Version: 1.1.0+dfsg-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 silx 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 silx from testing1.1.0+dfsg-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/s/silx/28796438/log.gz Testing with python3.11: = test session starts == platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack rootdir: /tmp/autopkgtest-lxc.btdfxoen/downtmp/autopkgtest_tmp plugins: xvfb-2.0.0 collected 1796 items app/test/test_convert.py [ 0%] app/view/test/test_launcher.py . [ 0%] app/view/test/test_view.py FF [ 2%] gui/data/test/test_arraywidget.py sFFF [ 3%] gui/data/test/test_dataviewer.py FFF [ 5%] FFF [ 5%] gui/data/test/test_numpyaxesselector.py F [ 6%] gui/data/test/test_textformatter.py [ 7%] gui/dialog/test/test_colormapdialog.py FEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFEFE [ 8%] FEFE [ 8%] gui/dialog/test/test_datafiledialog.py F [ 10%] FF [ 10%] gui/dialog/test/test_imagefiledialog.py Fatal Python error: Segmentation fault Current thread 0x7fb29d541040 (most recent call first): File "/usr/lib/python3/dist-packages/silx/gui/utils/testutils.py", line 334 in qWait File "/usr/lib/python3/dist-packages/silx/gui/utils/testutils.py", line 393 in qWaitForDestroy File "/usr/lib/python3/dist-packages/silx/gui/dialog/test/test_imagefiledialog.py", line 124 in _deleteDialog File "/usr/lib/python3/dist-packages/silx/gui/dialog/test/test_imagefiledialog.py", line 151 in tearDown File "/usr/lib/python3.11/unittest/case.py", line 584 in _callTearDown File "/usr/lib/python3.11/unittest/case.py", line 626 in run File "/usr/lib/python3.11/unittest/case.py", line 678 in __call__ File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 327 in runtest File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 166 in pytest_runtest_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 259 in File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 338 in from_call File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 258 in call_runtest_hook File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 219 in call_and_report File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 130 in runtestprotocol File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 111 in pytest_runtest_protocol File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 347 in pytest_runtestloop File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 322 in _main File "/usr/lib/python3/dist-packages/_pytest/main.py", line 268 in wrap_session File "/usr/lib/python3/dist-packages/_pytest/main.py", line 315 in pytest_cmdline_main File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in _hookexec File "/usr/lib/pyt
Processed: silx: (autopkgtest) needs update for python3.11: Segmentation fault
Processing control commands: > affects -1 src:python3-defaults Bug #1025183 [src:silx] silx: (autopkgtest) needs update for python3.11: Segmentation fault Added indication that 1025183 affects src:python3-defaults -- 1025183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025180: qiskit-aer: (autopkgtest) needs update for python3.11: No module named 'qiskit.transpiler.passes.routing.cython.stochastic_swap.utils'
Source: qiskit-aer
Version: 0.4.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
qiskit-aer 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
qiskit-aer from testing0.4.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/q/qiskit-aer/28796434/log.gz
Testing with python3.11:
/usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:76:
DeprecationWarning: `np.float` is a deprecated alias for the builtin
`float`. To silence this warning, use `float` by itself. Doing this will
not modify any behavior and is safe. If you specifically wanted the
numpy scalar type, use `np.float64` here.
Deprecated in NumPy 1.20; for more details and guidance:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
numpy.integer, numpy.float,
/usr/lib/python3/dist-packages/qiskit/__init__.py:53: RuntimeWarning:
Could not import the Aer provider from the qiskit-aer package. Install
qiskit-aer or check your installation.
warnings.warn('Could not import the Aer provider from the qiskit-aer '
/usr/lib/python3/dist-packages/qiskit/__init__.py:60: RuntimeWarning:
Could not import the IBMQ provider from the qiskit-ibmq-provider
package. Install qiskit-ibmq-provider or check your installation.
warnings.warn('Could not import the IBMQ provider from the '
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/qiskit/__init__.py", line 67, in
from qiskit.execute import execute
File "/usr/lib/python3/dist-packages/qiskit/execute.py", line 24, in
from qiskit.compiler import transpile, assemble
File "/usr/lib/python3/dist-packages/qiskit/compiler/__init__.py",
line 35, in
from .transpile import transpile
File "/usr/lib/python3/dist-packages/qiskit/compiler/transpile.py",
line 16, in
from qiskit.transpiler import Layout, CouplingMap
File "/usr/lib/python3/dist-packages/qiskit/transpiler/__init__.py",
line 76, in
from .transpile_circuit import transpile_circuit
File
"/usr/lib/python3/dist-packages/qiskit/transpiler/transpile_circuit.py",
line 17, in
from qiskit.transpiler.preset_passmanagers import
(level_0_pass_manager,
File
"/usr/lib/python3/dist-packages/qiskit/transpiler/preset_passmanagers/__init__.py",
line 31, in
from .level0 import level_0_pass_manager
File
"/usr/lib/python3/dist-packages/qiskit/transpiler/preset_passmanagers/level0.py",
line 23, in
from qiskit.transpiler.passes import Unroller
File
"/usr/lib/python3/dist-packages/qiskit/transpiler/passes/__init__.py",
line 116, in
from .routing import BasicSwap
File
"/usr/lib/python3/dist-packages/qiskit/transpiler/passes/routing/__init__.py",
line 19, in
from .stochastic_swap import StochasticSwap
File
"/usr/lib/python3/dist-packages/qiskit/transpiler/passes/routing/stochastic_swap.py",
line 30, in
from .cython.stochastic_swap.utils import nlayout_from_layout
ModuleNotFoundError: No module named
'qiskit.transpiler.passes.routing.cython.stochastic_swap.utils'
autopkgtest [01:17:01]: test autodep8-python3
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1025182: rich: (autopkgtest) needs update for python3.11: AssertionError
Source: rich
Version: 12.4.4-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
rich 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
rich from testing12.4.4-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/r/rich/28796437/log.gz
=== FAILURES
===
__ test_inspect_text
___
@skip_pypy3
def test_inspect_text():
expected = (
"╭ ─╮\n"
"│ str(object='') -> str │\n"
"│ str(bytes_or_buffer[, encoding[, errors]]) -> │\n"
"│ str│\n"
"││\n"
"│ 33 attribute(s) not shown. Run │\n"
"│ inspect(inspect) for options. │\n"
"╰╯\n"
)
print(repr(expected))
assert expected == render("Hello")
E AssertionError: assert '╭───...──╯\n' ==
'╭───...──╯\n'
E Skipping 248 identical leading characters in diff, use -v to show
E Skipping 140 identical trailing characters in diff, use -v to show
E│
E - │ 34 attribut
E ?^
E + │ 33 attribut
E ?^
tests/test_inspect.py:102: AssertionError
- Captured stdout call
-
"╭ ─╮\n│ str(object='') ->
str │\n│ str(bytes_or_buffer[, encoding[,
errors]]) -> │\n│ str│\n│
│\n│ 33 attribute(s) not
shown. Run │\n│ inspect(inspect) for options.
│\n╰╯\n"
test_inspect_builtin_function
_
@skip_pypy3
def test_inspect_builtin_function():
expected = (
"╭── ───╮\n"
"│ def print(...) │\n"
"││\n"
"│ print(value, ..., sep=' ', end='\\n', │\n"
"│ file=sys.stdout, flush=False) │\n"
"││\n"
"│ 29 attribute(s) not shown. Run │\n"
"│ inspect(inspect) for options. │\n"
"╰╯\n"
)
assert expected == render(print)
E AssertionError: assert '╭── ...──╯\n' ==
'╭── ...──╯\n'
E Skipping 53 identical leading characters in diff, use -v to show
E + def print(...) │
E - def print(*args, sep=' ', end='\n', file=None, │
E - │ flush=False): │
E ││
E - │ Prints the values to a stream, or to │
E - │ sys.stdout by default. │...
E E ...Full output truncated (10 lines hidden), use
'-vv' to show
tests/test_inspect.py:142: AssertionError
__ test_inspect_integer_with_methods
___
@skip_py36
@skip_py37
@skip_py38
@skip_py39
def test_inspect_integer_with_methods():
expected = (
"╭ ─╮\n"
"│ int([x]) -> integer│\n"
"│ int(x, base=10) -> integer │\n"
"│
Bug#1025181: qiskit-ibmq-provider: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Source: qiskit-ibmq-provider
Version: 0.4.6-4
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
qiskit-ibmq-provider 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
qiskit-ibmq-provider from testing0.4.6-4
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/q/qiskit-ibmq-provider/28796435/log.gz
Testing with python3.11:
/usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:76:
DeprecationWarning: `np.float` is a deprecated alias for the builtin
`float`. To silence this warning, use `float` by itself. Doing this will
not modify any behavior and is safe. If you specifically wanted the
numpy scalar type, use `np.float64` here.
Deprecated in NumPy 1.20; for more details and guidance:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
numpy.integer, numpy.float,
/usr/lib/python3/dist-packages/qiskit/__init__.py:53: RuntimeWarning:
Could not import the Aer provider from the qiskit-aer package. Install
qiskit-aer or check your installation.
warnings.warn('Could not import the Aer provider from the qiskit-aer '
/usr/lib/python3/dist-packages/qiskit/providers/ibmq/api/rest/validation.py:35:
RemovedInMarshmallow4Warning: The 'missing' argument to fields is
deprecated. Use 'load_default' instead.
_status = String(required=False, missing=None)
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/qiskit/__init__.py", line 58, in
from qiskit.providers.ibmq import IBMQ
File
"/usr/lib/python3/dist-packages/qiskit/providers/ibmq/__init__.py", line
20, in
from .ibmqfactory import IBMQFactory
File
"/usr/lib/python3/dist-packages/qiskit/providers/ibmq/ibmqfactory.py",
line 21, in
from .accountprovider import AccountProvider
File
"/usr/lib/python3/dist-packages/qiskit/providers/ibmq/accountprovider.py",
line 26, in
from .api.clients import AccountClient
File
"/usr/lib/python3/dist-packages/qiskit/providers/ibmq/api/clients/__init__.py",
line 18, in
from .account import AccountClient
File
"/usr/lib/python3/dist-packages/qiskit/providers/ibmq/api/clients/account.py",
line 35, in
from .websocket import WebsocketClient
File
"/usr/lib/python3/dist-packages/qiskit/providers/ibmq/api/clients/websocket.py",
line 113, in
class WebsocketClient(BaseClient):
File
"/usr/lib/python3/dist-packages/qiskit/providers/ibmq/api/clients/websocket.py",
line 126, in WebsocketClient
@asyncio.coroutine
^
AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you
mean: 'coroutines'?
autopkgtest [01:16:47]: test autodep8-python3
OpenPGP_signature
Description: OpenPGP digital signature
Processed: rich: (autopkgtest) needs update for python3.11: AssertionError
Processing control commands: > affects -1 src:python3-defaults Bug #1025182 [src:rich] rich: (autopkgtest) needs update for python3.11: AssertionError Added indication that 1025182 affects src:python3-defaults -- 1025182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: qiskit-ibmq-provider: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Processing control commands: > affects -1 src:python3-defaults Bug #1025181 [src:qiskit-ibmq-provider] qiskit-ibmq-provider: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added indication that 1025181 affects src:python3-defaults -- 1025181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pyvows: (autopkgtest) needs update for python3.11: No module named 'gevent._gevent_c_hub_local'
Processing control commands: > affects -1 src:python3-defaults Bug #1025179 [src:pyvows] pyvows: (autopkgtest) needs update for python3.11: No module named 'gevent._gevent_c_hub_local' Added indication that 1025179 affects src:python3-defaults -- 1025179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: qiskit-aer: (autopkgtest) needs update for python3.11: No module named 'qiskit.transpiler.passes.routing.cython.stochastic_swap.utils'
Processing control commands: > affects -1 src:python3-defaults Bug #1025180 [src:qiskit-aer] qiskit-aer: (autopkgtest) needs update for python3.11: No module named 'qiskit.transpiler.passes.routing.cython.stochastic_swap.utils' Added indication that 1025180 affects src:python3-defaults -- 1025180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025179: pyvows: (autopkgtest) needs update for python3.11: No module named 'gevent._gevent_c_hub_local'
Source: pyvows Version: 3.0.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 pyvows 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 pyvows from testing3.0.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/pyvows/28796433/log.gz === python3.11 === 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/pyvows/__main__.py", line 12, in sys.exit(main()) ^^ File "/usr/lib/python3/dist-packages/pyvows/cli.py", line 184, in main result = run( File "/usr/lib/python3/dist-packages/pyvows/cli.py", line 136, in run from pyvows.core import Vows File "/usr/lib/python3/dist-packages/pyvows/core.py", line 20, in from pyvows.decorators import _batch, async_topic, capture_error, skip_if File "/usr/lib/python3/dist-packages/pyvows/decorators.py", line 15, in from pyvows.runner import SkipTest File "/usr/lib/python3/dist-packages/pyvows/runner/__init__.py", line 10, in from pyvows.runner.gevent import VowsParallelRunner as VowsRunner File "/usr/lib/python3/dist-packages/pyvows/runner/gevent.py", line 27, in from gevent.pool import Pool File "/usr/lib/python3/dist-packages/gevent/__init__.py", line 86, in from gevent._hub_local import get_hub File "/usr/lib/python3/dist-packages/gevent/_hub_local.py", line 101, in import_c_accel(globals(), 'gevent.__hub_local') File "/usr/lib/python3/dist-packages/gevent/_util.py", line 148, in import_c_accel mod = importlib.import_module(cname) ^^ File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ModuleNotFoundError: No module named 'gevent._gevent_c_hub_local' autopkgtest [01:16:00]: test unittests OpenPGP_signature Description: OpenPGP digital signature
Bug#1025178: python-wadllib: (autopkgtest) needs update for python3.11: Deprecation warning on stderr
Source: python-wadllib Version: 1.3.6-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-wadllib 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-wadllib from testing1.3.6-2 all others from testingfrom testing I copied some of the output at the bottom of this report. The test doesn't fail itself, but it prints output on stderr which by default (without allow-stderr restriction) is interpreted as failure. 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-wadllib/28796431/log.gz = python3.11 = Running tests at level 1 Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Running: /usr/lib/python3/dist-packages/wadllib/docs/NEWS.rst /usr/lib/python3/dist-packages/wadllib/docs/index.rstindex.rst[140]>:1: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13 import cgi Ran 2 tests with 0 failures, 0 errors and 0 skipped in 0.049 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. = python3.10 = Running tests at level 1 Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Running: /usr/lib/python3/dist-packages/wadllib/docs/NEWS.rst /usr/lib/python3/dist-packages/wadllib/docs/index.rst Ran 2 tests with 0 failures, 0 errors and 0 skipped in 0.055 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. autopkgtest [01:15:34]: test py3 OpenPGP_signature Description: OpenPGP digital signature
Processed: python-wadllib: (autopkgtest) needs update for python3.11: Deprecation warning on stderr
Processing control commands: > affects -1 src:python3-defaults Bug #1025178 [src:python-wadllib] python-wadllib: (autopkgtest) needs update for python3.11: Deprecation warning on stderr Added indication that 1025178 affects src:python3-defaults -- 1025178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#816393: Works now?
* Helge Kreutzmann : > for what is worth: > helge@samd:/tmp$ debget nghttp2 > Get:1 http://172.16.18.51:/ftp.de.debian.org/debian bullseye/main > amd64 nghttp2 all 1.43.0-1 [14.4 kB] > Fetched 14.4 kB in 0s (117 kB/s) For anyone reading along: this "success" is, because nghttp2 switched to tar.bz2 orig tarballs. Chris
Bug#1025175: asyncio_mqtt.Client("localhost") fails with a TypeError
Package: python3-asyncio-mqtt
Version: 0.13.0-1
Severity: grave
$ python3 -c 'import asyncio_mqtt; asyncio_mqtt.Client("localhost")'
Exception ignored in:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/paho/mqtt/client.py", line 660, in
__del__
self._reset_sockets()
File "/usr/lib/python3/dist-packages/paho/mqtt/client.py", line 704, in
_reset_sockets
self._sock_close()
File "/usr/lib/python3/dist-packages/paho/mqtt/client.py", line 691, in
_sock_close
if not self._sock:
AttributeError: 'Client' object has no attribute '_sock'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/asyncio_mqtt/client.py", line 222, in
__init__
self._client: mqtt.Client = mqtt.Client(
TypeError: Client.__init__() got an unexpected keyword argument
'reconnect_on_failure'
$
The reconnect_on_failure keyword argument has been added to paho mqtt
quite recently and the Debian package hasn't been updated yet. So to fix
this bug you have two options:
a) Reupload 0.10.0 (with some really version).
b) Upload a new paho mqtt and upload python3-asyncio-mqtt with a suitable
version constraint.
In both cases, please do add an autopkgtest and a build-time test or
something. Such a fundamental failure shouldn't have entered unstable
much less migrated to testing. And I should have restarted my
application sooner. ;)
Helmut
Bug#1024890: marked as done (ntcard - build-dependencies unsatisfiable on 32-bit.)
Your message dated Wed, 30 Nov 2022 23:46:29 +0530 with message-id <20221130181629.dmg4zce7dxpn5...@nileshpatra.info> and subject line Re: ntcard - build-dependencies unsatisfiable on 32-bit. has caused the Debian Bug report #1024890, regarding ntcard - build-dependencies unsatisfiable on 32-bit. 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.) -- 1024890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. 3. Declare your package unsupported on 32-bit architectures and file a removal bug with the ftpmasters. I do not know which are pratical in the case of your particular package. --- End Message --- --- Begin Message --- On Sun, 27 Nov 2022 14:30:15 + Peter Michael Green wrote: > Package: ntcard > Version: 1.2.2+dfsg-4 > Severity: serious > 3. Declare your package unsupported on 32-bit architectures and file a > removal bug with the ftpmasters. This has been implemented and processed with Bug#1024985, closing. -- Best, Nilesh signature.asc Description: PGP signature --- End Message ---
Bug#896395: marked as done (python3-sphinxcontrib.rubydomain: sphinxcontrib.rubydomain fails to import)
Your message dated Wed, 30 Nov 2022 18:03:23 +
with message-id
and subject line Bug#1024570: Removed package(s) from unstable
has caused the Debian Bug report #896395,
regarding python3-sphinxcontrib.rubydomain: sphinxcontrib.rubydomain fails to
import
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.)
--
896395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sphinxcontrib.rubydomain
Version: 0.1~dev-20100804-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-sphinxcontrib.rubydomain importing the module
sphinxcontrib.rubydomain
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/sphinxcontrib/rubydomain.py", line 23,
in
from sphinx.util.compat import Directive
ImportError: cannot import name 'Directive'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Version: 0.1~dev-20100804-4+rm
Dear submitter,
as the package sphinxcontrib-rubydomain has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1024570
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#896327: marked as done (python-sphinxcontrib.rubydomain: sphinxcontrib.rubydomain fails to import)
Your message dated Wed, 30 Nov 2022 18:03:23 +
with message-id
and subject line Bug#1024570: Removed package(s) from unstable
has caused the Debian Bug report #896327,
regarding python-sphinxcontrib.rubydomain: sphinxcontrib.rubydomain fails to
import
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.)
--
896327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-sphinxcontrib.rubydomain
Version: 0.1~dev-20100804-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-sphinxcontrib.rubydomain importing the module
sphinxcontrib.rubydomain
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/sphinxcontrib/rubydomain.py", line 23,
in
from sphinx.util.compat import Directive
ImportError: cannot import name Directive
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Version: 0.1~dev-20100804-4+rm
Dear submitter,
as the package sphinxcontrib-rubydomain has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1024570
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#938774: marked as done (viewmol: Python2 removal in sid/bullseye)
Your message dated Wed, 30 Nov 2022 17:57:46 + with message-id and subject line Bug#1022931: Removed package(s) from unstable has caused the Debian Bug report #938774, regarding viewmol: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:viewmol Version: 2.4.1-25 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:viewmol If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.4.1-26+rm Dear submitter, as the package viewmol has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1022931 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#967229: marked as done (viewmol: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 30 Nov 2022 17:57:46 + with message-id and subject line Bug#1022931: Removed package(s) from unstable has caused the Debian Bug report #967229, regarding viewmol: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:viewmol Version: 2.4.1-26 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.4.1-26+rm Dear submitter, as the package viewmol has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1022931 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#936507: marked as done (fbpanel: Python2 removal in sid/bullseye)
Your message dated Wed, 30 Nov 2022 17:58:15 + with message-id and subject line Bug#1022932: Removed package(s) from unstable has caused the Debian Bug report #936507, regarding fbpanel: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fbpanel Version: 7.0-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:fbpanel If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 7.0-4.3+rm Dear submitter, as the package fbpanel has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1022932 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#673406: marked as done (Shouldn't be a native Debian package)
Your message dated Wed, 30 Nov 2022 17:57:14 + with message-id and subject line Bug#1021094: Removed package(s) from unstable has caused the Debian Bug report #673406, regarding Shouldn't be a native Debian package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 673406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnprogs Version: 2.59 Severity: normal I can't see any good reason why this software is packaged in Debian-native form. Despite the old message in the debian/changelog for version 2.25: * Get rid of the "-1" in the version number as it's not right, this really is a debian package. But include a README.Debian to keep some people happy. there isn't a README.Debian anywhere I can see, but there is an rpm.spec file suggesting this could/should be built for RPM systems too. -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Version: 2.65+rm Dear submitter, as the package dnprogs has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1021094 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#967207: marked as done (raul: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 30 Nov 2022 17:55:35 + with message-id and subject line Bug#1017939: Removed package(s) from unstable has caused the Debian Bug report #967207, regarding raul: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:raul Version: 0.8.0+dfsg0-0.1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.8.0+dfsg0-0.1+rm Dear submitter, as the package raul has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1017939 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#939065: marked as done (BD on python-rdkit which isn't build anymore and isn't in bullseye)
Your message dated Wed, 30 Nov 2022 17:54:43 + with message-id and subject line Bug#1009281: Removed package(s) from unstable has caused the Debian Bug report #939065, regarding BD on python-rdkit which isn't build anymore and isn't in bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 939065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cinfony Version: 1.2-3 Severity: serious Tags: ftbfs sid bullseye Control: found -1 1.2-4 Recently the rdkit package has stopped building the python-rdkit package. This is an issue for your package as it build-depends on it. Unfortunately the migration software doesn't detected this kind of situation yet, so your package also FTBFS in bullseye since 2019-08-15. The package is still available in unstable as cruft. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1.2-4+rm Dear submitter, as the package cinfony has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1009281 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#936303: marked as done (cinfony: Python2 removal in sid/bullseye)
Your message dated Wed, 30 Nov 2022 17:54:43 + with message-id and subject line Bug#1009281: Removed package(s) from unstable has caused the Debian Bug report #936303, regarding cinfony: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cinfony Version: 1.2-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:cinfony If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.2-4+rm Dear submitter, as the package cinfony has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1009281 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1017939: marked as done (RM: raul -- unmaintained, RC-buggy, no-reverse-deps)
Your message dated Wed, 30 Nov 2022 17:55:29 + with message-id and subject line Bug#1017939: Removed package(s) from unstable has caused the Debian Bug report #1017939, regarding RM: raul -- unmaintained, RC-buggy, no-reverse-deps 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.) -- 1017939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: raul Version: 0.8.0+dfsg0-0.1 Severity: serious User: tobi-rm-proposals@d.o Usertags: rm-proposal Dear Maintainer, This package is de-facto unmaintained since 2010. It has no reverse dependencies in Debian. It is currently RC buggy with those bugs: #967207 [S| | ] [src:raul] raul: Unversioned Python removal in sid/bullseye I therefore propose to RM the package. There is an ITS (CC'ed), but that ITS seems to have stalled. If you disagree, just close this bug, but please show the package some love. If you agree, reassign the bug to ftp.debian.org If there is no answer, I will reassing the bug in exactly 3 months to ftp.debian.org to make the RM happen. -- tobi --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libraul-dev | 0.8.0+dfsg0-0.1 | arm64, mips64el libraul-dev | 0.8.0+dfsg0-0.1+b1 | amd64, armel, armhf, i386, s390x libraul-dev | 0.8.0+dfsg0-0.1+b2 | mipsel libraul-dev | 0.8.0+dfsg0-0.1+b3 | ppc64el libraul-doc | 0.8.0+dfsg0-0.1 | all libraul10 | 0.8.0+dfsg0-0.1 | arm64, mips64el libraul10 | 0.8.0+dfsg0-0.1+b1 | amd64, armel, armhf, i386, s390x libraul10 | 0.8.0+dfsg0-0.1+b2 | mipsel libraul10 | 0.8.0+dfsg0-0.1+b3 | ppc64el raul | 0.8.0+dfsg0-0.1 | source --- Reason --- unmaintained, RC-buggy, no-reverse-deps -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1017...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1017939 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Re: python-pkg-resources: please add Breaks against the unversioned python packages
Processing control commands: > unblock 942959 by -1 Bug #942959 [src:dh-python] dh-python: Python2 removal in sid/bullseye 942959 was blocked by: 936854 938168 936298 938774 937049 966801 966725 936323 1024476 938637 953377 990318 936303 938921 942959 was blocking: 937695 Removed blocking bug(s) of 942959: 990318 > severity -1 normal Bug #990318 [python-pkg-resources] python-pkg-resources: please add Breaks against the unversioned python packages Severity set to 'normal' from 'serious' > tags -1 wontfix Bug #990318 [python-pkg-resources] python-pkg-resources: please add Breaks against the unversioned python packages Added tag(s) wontfix. -- 942959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942959 990318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990318: python-pkg-resources: please add Breaks against the unversioned python packages
Control: unblock 942959 by -1 Control: severity -1 normal Control: tags -1 wontfix The package is going to be removed in bookworm, so no upgrade scenarios are to be considered in the future.
Processed: blocks
Processing commands for cont...@bugs.debian.org: > block 942959 by 1024476 Bug #942959 [src:dh-python] dh-python: Python2 removal in sid/bullseye 942959 was blocked by: 936303 938921 966801 938637 938774 936854 936298 936323 966725 953377 990318 937049 942959 was blocking: 937695 Added blocking bug(s) of 942959: 1024476 > block 1011926 by 1024476 Bug #1011926 [pypy] pypy shouldn't be shipped in bookworm 1011926 was blocked by: 1018738 1019975 983470 937510 978079 938168 1019976 932820 1011926 was not blocking any bugs. Added blocking bug(s) of 1011926: 1024476 > End of message, stopping processing here. Please contact me if you need assistance. -- 1011926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011926 942959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: rm
Processing commands for cont...@bugs.debian.org: > reassign 938921 ftp.debian.org Bug #938921 [src:zorp] RM: zorp -- RoQA; py2 leftover Bug #953377 [src:zorp] RM: zorp -- RoQA; py2 leftover Bug #966801 [src:zorp] RM: zorp -- RoQA; py2 leftover Bug reassigned from package 'src:zorp' to 'ftp.debian.org'. Bug reassigned from package 'src:zorp' to 'ftp.debian.org'. Bug reassigned from package 'src:zorp' to 'ftp.debian.org'. No longer marked as found in versions zorp/7.0.1~alpha2-3 and zorp/6.0.10-4. No longer marked as found in versions zorp/7.0.1~alpha2-3 and zorp/6.0.10-4. No longer marked as found in versions zorp/6.0.10-4 and zorp/7.0.1~alpha2-3. Ignoring request to alter fixed versions of bug #938921 to the same values previously set Ignoring request to alter fixed versions of bug #953377 to the same values previously set Ignoring request to alter fixed versions of bug #966801 to the same values previously set > severity 938921 normal Bug #938921 [ftp.debian.org] RM: zorp -- RoQA; py2 leftover Bug #953377 [ftp.debian.org] RM: zorp -- RoQA; py2 leftover Bug #966801 [ftp.debian.org] RM: zorp -- RoQA; py2 leftover Severity set to 'normal' from 'serious' Severity set to 'normal' from 'serious' Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 938921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938921 953377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953377 966801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: zorp: Python2 removal in Debian sid/bookworm
Processing control commands: > retitle 938921 RM: zorp -- RoQA; py2 leftover Bug #938921 [src:zorp] zorp: Python2 removal in sid/bullseye Bug #953377 [src:zorp] src:zorp: Depends/Build-Depends on cruft package python-dnspython Bug #966801 [src:zorp] zorp: Unversioned Python removal in sid/bullseye Changed Bug title to 'RM: zorp -- RoQA; py2 leftover' from 'zorp: Python2 removal in sid/bullseye'. Changed Bug title to 'RM: zorp -- RoQA; py2 leftover' from 'src:zorp: Depends/Build-Depends on cruft package python-dnspython'. Changed Bug title to 'RM: zorp -- RoQA; py2 leftover' from 'zorp: Unversioned Python removal in sid/bullseye'. -- 938921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938921 953377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953377 966801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938921: zorp: Python2 removal in Debian sid/bookworm
Control: retitle 938921 RM: zorp -- RoQA; py2 leftover On Thu, 5 May 2022 10:20:23 +0200 puskas.ja...@balasys.hu wrote: We are in a process of re-writing our code, which will address (among others) the problems listed in the issue. However it will take quite some time so our estimation is about Autumn 2022 (Oct) when we will get there. Is the possible not to remove our package from Debian repository and close this case so that we do not need to go through the process again to get it back there later on? It does not seem like there has been any work put in to port zorp to Python 3. October has passed...
Processed: rm
Processing commands for cont...@bugs.debian.org: > retitle 1022931 RM: viewmol -- RoQA; py2 leftover; dead upstream; alternative > available Bug #1022931 [src:viewmol] Should viewmol be removed? Changed Bug title to 'RM: viewmol -- RoQA; py2 leftover; dead upstream; alternative available' from 'Should viewmol be removed?'. > reassign 1022931 ftp.debian.org Bug #1022931 [src:viewmol] RM: viewmol -- RoQA; py2 leftover; dead upstream; alternative available Bug reassigned from package 'src:viewmol' to 'ftp.debian.org'. No longer marked as found in versions viewmol/2.4.1-26. Ignoring request to alter fixed versions of bug #1022931 to the same values previously set > severity 1022931 normal Bug #1022931 [ftp.debian.org] RM: viewmol -- RoQA; py2 leftover; dead upstream; alternative available Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1022931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: telepathy-gabble: Python2 removal in sid/bullseye
Processing control commands: > retitle -1 RM: telepathy-gabble -- RoQA; removal triggered by the Python2 > removal Bug #938637 [src:telepathy-gabble] telepathy-gabble: Python2 removal in sid/bullseye Changed Bug title to 'RM: telepathy-gabble -- RoQA; removal triggered by the Python2 removal' from 'telepathy-gabble: Python2 removal in sid/bullseye'. > severity -1 normal Bug #938637 [src:telepathy-gabble] RM: telepathy-gabble -- RoQA; removal triggered by the Python2 removal Severity set to 'normal' from 'serious' > reassign -1 ftp.debian.org Bug #938637 [src:telepathy-gabble] RM: telepathy-gabble -- RoQA; removal triggered by the Python2 removal Bug reassigned from package 'src:telepathy-gabble' to 'ftp.debian.org'. No longer marked as found in versions telepathy-gabble/0.18.4-1. Ignoring request to alter fixed versions of bug #938637 to the same values previously set > notforwarded -1 Bug #938637 [ftp.debian.org] RM: telepathy-gabble -- RoQA; removal triggered by the Python2 removal Unset Bug forwarded-to-address -- 938637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938637: telepathy-gabble: Python2 removal in sid/bullseye
Control: retitle -1 RM: telepathy-gabble -- RoQA; removal triggered by the Python2 removal Control: severity -1 normal Control: reassign -1 ftp.debian.org Control: notforwarded -1 There are telepathy-gabble-0.99.* tags on the git repo which have been published before the 0.18.4 version but seem to have the py2 converted to py3. It does not look like anybody is putting in any work in Debian or upstream, so let's remove this package.
Bug#1025171: zfs-dkms FTBFS against 6.0.0-5-amd64
Package: zfs-dkms Version: 2.1.6-3 Severity: serious It was built againt 6.0.0-3-amd64 on my sid machine, but suddenly stopped working with the recent 6.0.0-5-amd64 kernel.
Bug#1023020: cmark-gfm: FTBFS on s390x
On Wed, 30 Nov 2022, Keith Packard wrote: 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? Thanks for the NMU! Did you happen to create a git repo with this change? I just noticed that the salsa repo is in my private space. g...@salsa.debian.org:keithp/cmark-gfm.git No, I didn't, since I wasn't aware you were using a Vcs for packaging (no Vcs listed in d/control). I can send you a merge request with the changes, if you'd like? Regards, Scott
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? Thanks for the NMU! Did you happen to create a git repo with this change? I just noticed that the salsa repo is in my private space. g...@salsa.debian.org:keithp/cmark-gfm.git -- -keith signature.asc Description: PGP signature
Processed: dh-python
Processing commands for cont...@bugs.debian.org: > block 942959 by 990318 Bug #942959 [src:dh-python] dh-python: Python2 removal in sid/bullseye 942959 was blocked by: 936854 936298 936303 937049 938637 936323 953377 966801 938774 938921 966725 942959 was blocking: 937695 Added blocking bug(s) of 942959: 990318 > tags 942959 - bullseye Bug #942959 [src:dh-python] dh-python: Python2 removal in sid/bullseye Removed tag(s) bullseye. > End of message, stopping processing here. Please contact me if you need assistance. -- 942959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000653: Fix php-mail build
Hi I have uploaded a fixed package as NMU to the deferred queue. Am 17.11.22 um 13:55 schrieb Christoph Martin: do you plan to release a new version with the proposed fix anytime soon? I build it locally with the fix and it builds fine. I could upload the package if this is ok for you. Christoph OpenPGP_signature Description: OpenPGP digital signature
Bug#1000596: php-db Update
I have uploaded a fixed package as NMU to to the deferred queue. Am 17.11.22 um 14:13 schrieb Christoph Martin: I just tried to build php-db with the new upstream version 1.11.0 and it builds without a problem. Do you plan to upload the updated package any time soon? If you need help, please let me know. Christoph OpenPGP_signature Description: OpenPGP digital signature
Bug#1023020: marked as done (cmark-gfm: FTBFS on s390x)
Your message dated Wed, 30 Nov 2022 16:04:10 + with message-id and subject line Bug#1023020: fixed in cmark-gfm 0.29.0.gfm.6-2.1 has caused the Debian Bug report #1023020, regarding cmark-gfm: FTBFS on s390x 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.) -- 1023020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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&arch=s390x&ver=0.29.0.gfm.6-2&stamp=1666810004&raw=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. ailto:mailto:scyt...@pokemon.com";>scyt...@pokemon.com -mailto:scyt...@pokemon.com";>mailto:scyt...@pokemon.com/ -mailto:scyt...@pokemon.com";>mailto:scyt...@pokemon.com/message -mailto:scyt...@pokemon.com";>mailto:scyt...@pokemon.com/mailto:beedr...@pokemon.com";>mailto:beedr...@pokemon.com +mailto:mailto:scyt...@pokemon.com";>scyt...@pokemon.com/ +mailto:mailto:scyt...@pokemon.com";>scyt...@pokemon.com/message +mailto:mailto:scyt...@pokemon.com";>scyt...@pokemon.com/mailto:beedr...@pokemon.com";>mailto:beedr...@pokemon.com xmpp:scyt...@pokemon.com xmpp:scyt...@pokemon.com. -xmpp:scyt...@pokemon.com/message -xmpp:scyt...@pokemon.com/message. +xmpp:mailto:scyt...@pokemon.com";>scyt...@pokemon.com/message +xmpp:mailto:scyt...@pokemon.com";>scyt...@pokemon.com/message. Email me at:mailto:scyt...@pokemon.com";>scyt...@pokemon.com http://www.github.com";>www.github.com http://www.github.com/%C3%A1";>www.github.com/á http://www.google.com/a_b";>www.google.com/a_b 29 passed, 1 failed, 0 errored, 0 skipped 13: 25 passed, 0 failed, 0 errored, 0 skipped 13/13 Test #13: regressiontest_executable .. Passed0.11 sec 85% tests passed, 2 tests failed out of 13 Total Test time (real) = 2.99 sec The following tests FAILED: 9 - extensions_executable (Failed) 10 - roundtrip_extensions_executable (Failed) Errors while running CTest make[1]: *** [Makefile:74: test] Error 8 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: cmark-gfm Source-Version: 0.29.0.gfm.6-2.1 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of cmark-gfm, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated cmark-gfm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 30 Nov 2022 10:41:13 -0500 Source: cmark-gfm Architecture: source Version: 0.29.0.gfm.6-2.1 Distribution: unstable Urgency: medium Maintainer: Keith Packard Changed-By: Scott Talbert Closes: 1023020 Changes: cmark-gfm (0.29.0.gfm.6-2.1) unstable; urgency=medium . * Non-maintainer upload. * Apply patch to fix FTBFS on s390x (Closes: #1023020) Checksums-Sha1: bc2aa05c063fd422bf023f3e1ce3a89048bb7ac1 2209 cmark-gfm_0.29.0.gfm.6-2.1.dsc 6d73730bda709754d05eab3425f4e1d7d0495b0b 12536 cmark-gfm_0.29.0.gfm.6-2.1.debian.tar.xz af15c91b138500ea875067441db9e6f8e3e924a9 9749 cmark-gfm_0.29.0.gfm.6-2.1_amd64.buildinfo Checksums-Sha256: 949d43bf181fcef47a216618577d7375dd426db81a2110c446bff65a788d277f 2209 cmark-gfm_0.29.0.gfm.6-2.1.dsc 3907be379c3fa0d81a57ecf202bd27effedf377179ee7a7f05366957534c3d82 12536 cmark-gfm_0.29.0.gfm.6-2.1.debian.tar.xz 88d365a903804bf1abfab8c267e4e26caae2a1014696d4dcda6a2f9da29f0b16 9749 cmark-gfm_0.29.0.gfm.6-2.1_amd64.buildinfo Files: 51f9f005c40c02e124499a12fe521724 2209 text optional cmark-gfm_0.29.0.gfm.6-2.1.dsc c19c274fa8dccf5a98b8fc1599c3e5e4 12536 text optional cmark-gfm_0.29.0.gfm.6-2.1.debian.tar.xz b7fcc61
Bug#1019637: marked as done (ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is memoized'))
Your message dated Wed, 30 Nov 2022 15:09:48 +
with message-id
and subject line Bug#1019637: fixed in ruby-memoizable 0.4.2-3
has caused the Debian Bug report #1019637,
regarding ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
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.)
--
1019637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-memoizable
Version: 0.4.2-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-memoizable with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> Failure/Error: expect { subject }.to raise_error(NameError, 'No method
> bar is memoized')
>
>expected NameError with "No method bar is memoized", got # No method bar is memoized
>
>fail NameError, "No method #{name} is memoized"
>> with backtrace:
> # ./lib/memoizable/memory.rb:30:in `block in []'
> # ./lib/memoizable/memory.rb:29:in `[]'
> # ./lib/memoizable/module_methods.rb:81:in
> `unmemoized_instance_method'
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:6:in
> `block (2 levels) in '
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in
> `block (4 levels) in '
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in
> `block (3 levels) in '
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in
> `block (3 levels) in '
>
> Finished in 0.04572 seconds (files took 0.11871 seconds to load)
> 68 examples, 1 failure
>
> Failed examples:
>
> rspec
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:39 #
> Memoizable::ModuleMethods#unmemoized_instance_method when the method was not
> memoized raises an exception
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> ./spec/integration/serializable_spec.rb
> ./spec/shared/call_super_shared_spec.rb
> ./spec/unit/memoizable/class_methods/included_spec.rb
> ./spec/unit/memoizable/instance_methods/freeze_spec.rb
> ./spec/unit/memoizable/instance_methods/memoize_spec.rb
> ./spec/unit/memoizable/memory_spec.rb
> ./spec/unit/memoizable/method_builder/call_spec.rb
> ./spec/unit/memoizable/method_builder/class_methods/new_spec.rb
> ./spec/unit/memoizable/method_builder/original_method_spec.rb
> ./spec/unit/memoizable/module_methods/included_spec.rb
> ./spec/unit/memoizable/module_methods/memoize_spec.rb
> ./spec/unit/memoizable/module_methods/memoized_predicate_spec.rb
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb
> --format documentation failed
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-memoizable/ruby-memoizable_0.4.2-2+rebuild1663007825_amd64-2022-09-12T18:37:06Z.build
To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-memoizable
Source-Version: 0.4.2-3
Done: Cédric Boutillier
We believe that the bug you reported is fixed in the latest version of
ruby-memoizable, 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...@bug
Bug#1011923: marked as done (ice-builder-gradle: FTBFS with OpenJDK 17 due to an illegal reflective access)
Your message dated Wed, 30 Nov 2022 15:33:20 +0100 with message-id and subject line Re: Bug#1011923: ice-builder-gradle: FTBFS with OpenJDK 17 due to an illegal reflective access has caused the Debian Bug report #1011923, regarding ice-builder-gradle: FTBFS with OpenJDK 17 due to an illegal reflective access 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.) -- 1011923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ice-builder-gradle Version: 1.4.5-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 ice-builder-gradle fails to build with OpenJDK 17, Gradle breaks on an illegal reflective access: make[1]: Entering directory '/<>' gradle --gradle-user-home /<>/.gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies -PlicenseURL="file:///usr/share/doc/gradle-ice-builder-plugin/copyright" > Initialized native services in: /<>/.gradle/native Using 8 worker leases. Creating new cache for fileHashes, path /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access org.gradle.cache.internal.DefaultCacheAccess@4d098f9b Creating new cache for resourceHashesCache, path /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, access org.gradle.cache.internal.DefaultCacheAccess@4d098f9b Creating new cache for fileHashes, path /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access org.gradle.cache.internal.DefaultCacheAccess@617fe9e1 FAILURE: Build failed with an exception. * What went wrong: Could not create service of type ScriptPluginFactory using BuildScopeServices.createScriptPluginFactory(). > Could not create service of type PluginResolutionStrategyInternal using BuildScopeServices.createPluginResolutionStrategy(). * Try: Run with --debug option to get more log output. Run with --scan to get full insights. * Exception is: org.gradle.internal.service.ServiceCreationException: Could not create service of type ScriptPluginFactory using BuildScopeServices.createScriptPluginFactory(). at org.gradle.internal.service.DefaultServiceRegistry$FactoryMethodService.invokeMethod(DefaultServiceRegistry.java:797) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:748) at org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:574) at org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:623) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.assembleParameters(DefaultServiceRegistry.java:761) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:747) at org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:574) at org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:623) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.assembleParameters(DefaultServiceRegistry.java:761) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:747) at org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:574) at org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:623) at org.gradle.internal.service.DefaultServiceRegistry.doGet(DefaultServiceRegistry.java:344) at org.gradle.internal.service.DefaultServiceRegistry.get(DefaultServiceRegistry.java:325) at org.gradle.initialization.DefaultGradleLauncherFactory.doNewInstance(DefaultGradleLauncherFactory.java:174) at org.gradle.initialization.DefaultGradleLauncherFactory.newInstance(DefaultGradleLauncherFactory.java:106) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:40) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30) at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:39) at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:25) at o
Bug#1019664: marked as done (ruby-rspec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure })
Your message dated Wed, 30 Nov 2022 13:50:58 +
with message-id
and subject line Bug#1019664: fixed in ruby-rspec 3.10.0c1e1m2s3-2
has caused the Debian Bug report #1019664,
regarding ruby-rspec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise
failure }
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1019664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec
Version: 3.10.0c1e1m2s3-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-rspec with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts|
> raise failure }
>expected /received: 0 times/ but nothing was raised
> # ./spec/rspec/support/deprecation_helpers_spec.rb:66:in `block (4
> levels) in '
> # ./spec/rspec/support/deprecation_helpers_spec.rb:65:in `block (3
> levels) in '
>
> 2) RSpec::Support::ShellOut can shell out to ruby with the current load path
> # Need to investigate why this is failing -- see
> https://travis-ci.org/rspec/rspec-core/jobs/60327106 and
> https://travis-ci.org/rspec/rspec-support/jobs/60296920 for examples
> # ./spec/rspec/support/spec/shell_out_spec.rb:22
>
> Finished in 0.7821 seconds (files took 0.18394 seconds to load)
> 553 examples, 0 failures, 2 pending
>
> Randomized with seed 24209
>
> cd -
> Failed: rspec-core, rspec-expectations
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-rspec/ruby-rspec_3.10.0c1e1m2s3-1+rebuild1663008138_amd64-2022-09-12T18:42:19Z.build
To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-rspec
Source-Version: 3.10.0c1e1m2s3-2
Done: Cédric Boutillier
We believe that the bug you reported is fixed in the latest version of
ruby-rspec, 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.
Cédric Boutillier (supplier of updated ruby-rspec package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 30 Nov 2022 14:27:18 +0100
Source: ruby-rspec
Architecture: source
Version: 3.10.0c1e1m2s3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Cédric Boutillier
Closes: 1019664
Changes:
ruby-rspec (3.10.0c1e1m2s3-2) unstable; urgency=medium
.
* Bump Standards-Version to 4.6.1 (no changes needed)
* Bump debhelper compatibility level to 13
* Fix test failures with ruby3.1
- Disable error highlighting with ruby3.1 when running tests
with --disable-error_highlight ruby option
(Closes: #1019664)
- Add patch to call correct interpreter in rspec-support 'shell out' specs
Checksums-Sha1:
f117db6bedefbe7bd12536b8af4a6c9819b8abe5 1886 ruby-rspec_3.10.0c1e1m2s3-2.dsc
015dd69bb12fbd1d15469f4af6104fd552d2cc6a 882578
ruby-rspec_3.10.0c1e1m2s3.orig.tar.gz
5e2a7010852726a57c7407fb2bed9b740d21622a 12016
ruby-rspec_3.10.0c1e1m2s3-2.debian.tar.xz
205ceae0b172f73e00cadebfbe253f8912b7c829 11405
ruby-rspec_3.10.0c1e1m2s3-2_amd64.buildinfo
Checksu
Bug#1024632: [Pkg-erlang-devel] Bug#1024632: erlang: CVE-2022-37026 Client Authentication Bypass
Hi Markus, On Wed, Nov 30, 2022 at 4:15 PM Markus Koschany wrote: > > Hello, > > I have prepared a security update for Bullseye which fixes CVE-2022-37026. > Sergei could you review the update please? I am attaching the debdiff. I'm also preparing a fix for CVE-2022-37026, but I'll gladly consider your patch first. Thank you for the work! -- Sergei Golovan
