Processed: 1026603 is forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 1026603 https://github.com/warner/foolscap/issues/93 Bug #1026603 [src:foolscap] foolscap: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec' Set Bug forwarded-to-address to 'https://github.com/warner/foolscap/issues/93'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026603: foolscap: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Hello, On Tue, 20 Dec 2022 18:11:51 +0100 Lucas Nussbaum > During a rebuild of all packages in sid, your package failed to build on amd64. [skip] > File "/<>/.pybuild/cpython3_3.11/build/foolscap/remoteinterface.py", line 191, in initFromMethod > names, _, _, typeList = inspect.getargspec(method) > ^^ > AttributeError: module 'inspect' has no attribute 'getargspec' inspect.getargspec has been deprecated for some time [1] and most likely finally removed in Python 3.11. I have attempted to replace it with inspect.getfullargspec as seen somewhere else [2], but this did not work. [1] https://docs.python.org/3/library/inspect.html [2] https://github.com/pyinvoke/invoke/issues/833#issuecomment-1293148106 Andrius
Processed: Solving the bug
Processing control commands: > tags -1 patch Bug #1026757 [src:gatk-native-bindings] gatk-native-bindings: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 25 Added tag(s) patch. -- 1026757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026757: Solving the bug
Control: tags -1 patch Hello, I reopened the bug because the issue was fixed on my laptop but not on the buildds. I did additional tests and reproduced the issue on porterboxes. It vanishes when one removes the exports of ANT_HOME and JAVA_HOME in debian/rules. I met a similar issue in another package some time ago... If no one else does it, I will upload the fix later in the day. Cheers, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Processed: reopening 1026757
Processing commands for cont...@bugs.debian.org:
> reopen 1026757
Bug #1026757 {Done: Pierre Gruet } [src:gatk-native-bindings]
gatk-native-bindings: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_build] Error 25
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gatk-native-bindings/1.0.0+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027079: marked as done (ruby-listen: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: @snapshots[dir].invalidate(type, rel_path, options))
Your message dated Wed, 28 Dec 2022 04:25:04 +
with message-id
and subject line Bug#1027079: fixed in ruby-listen 3.7.0-2
has caused the Debian Bug report #1027079,
regarding ruby-listen: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error: @snapshots[dir].invalidate(type, rel_path, options)
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.)
--
1027079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-listen
Version: 3.7.0-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-listen failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: @snapshots[dir].invalidate(type, rel_path, options)
>
> # received :invalidate
> with unexpected arguments
> expected: (:dir, ".", {:recursive=>true}) (keyword arguments)
>got: (:dir, ".", {:recursive=>true}) (options hash)
> # ./lib/listen/adapter/base.rb:108:in `_queue_change'
> # ./lib/listen/adapter/polling.rb:36:in `_process_event'
> # ./lib/listen/adapter/base.rb:44:in `block (2 levels) in configure'
> # ./lib/listen/adapter/polling.rb:26:in `block (2 levels) in _run'
> # ./lib/listen/adapter/polling.rb:25:in `each'
> # ./lib/listen/adapter/polling.rb:25:in `block in _run'
> # ./lib/listen/adapter/polling.rb:23:in `loop'
> # ./lib/listen/adapter/polling.rb:23:in `_run'
> # ./lib/listen/adapter/base.rb:79:in `block in start'
> # ./lib/listen/thread.rb:26:in `rescue_and_log'
> # ./lib/listen/thread.rb:18:in `block in new'
>
> Finished in 0.37831 seconds (files took 0.20262 seconds to load)
> 312 examples, 22 failures, 1 pending
>
> Failed examples:
>
> rspec ./spec/lib/listen/adapter/linux_spec.rb:137 # Listen::Adapter::Linux
> instance methods _callback recognizes close_write as modify
> rspec ./spec/lib/listen/adapter/linux_spec.rb:142 # Listen::Adapter::Linux
> instance methods _callback recognizes moved_to as moved_to
> rspec ./spec/lib/listen/adapter/linux_spec.rb:147 # Listen::Adapter::Linux
> instance methods _callback recognizes moved_from as moved_from
> rspec ./spec/lib/listen/directory_spec.rb:275 # Listen::Directory#scan with
> recursive on with empty record with subdir present in dir snapshots changes
> for subdir
> rspec ./spec/lib/listen/directory_spec.rb:218 # Listen::Directory#scan with
> recursive on with file.rb & subdir in record with empty dir snapshots changes
> for file & subdir path
> rspec ./spec/lib/listen/directory_spec.rb:239 # Listen::Directory#scan with
> recursive on with file.rb & subdir in record with subdir2 path present
> snapshots changes for file, file2 & subdir paths
> rspec ./spec/lib/listen/directory_spec.rb:75 # Listen::Directory#scan with
> recursive off with file & subdir in record with empty dir snapshots changes
> for file path and dir that doesn't exist
> rspec ./spec/lib/listen/directory_spec.rb:92 # Listen::Directory#scan with
> recursive off with file & subdir in record when subdir is removed notices
> subdir does not exist
> rspec ./spec/lib/listen/adapter/base_spec.rb:91 # Listen::Adapter::Base
> handling events when an event occurs passes invalidates the snapshot based on
> the event
> rspec ./spec/lib/listen/listener_spec.rb:300 # Listen::Listener#ignore! with
> existing ignore options deletes ignore options
> rspec ./spec/lib/listen/listener_spec.rb:289 # Listen::Listener#ignore! with
> existing ignore! options overwrites existing ignore options
> rspec ./spec/lib/listen/listener_spec.rb:247 # Listen::Listener#ignore with
> existing ignore options adds up to existing ignore options
> rspec ./spec/lib/listen/listener_spec.rb:262 # Listen::Listener#ignore with
> existing ignore options (array) adds up to existing ignore options
> rspec ./spec/lib/listen/listener_spec.rb:313 # Listen::Listener#only with
> existing only options overwrites existing ignore options
> rspec ./spec/lib/listen/silencer/controller_spec.rb:43 #
> Listen::Silencer::Controller append_ignores with no previous :ignore rules
> when providing as array sets the given :ignore rules
> rspec ./spec/lib/listen/silencer/controller_spec.rb:35 #
> Listen::Silencer::Controller append_ignores with no previous :ignore rules
> when providing multiple arguments sets the given :ignore rules as a flat array
> rspec ./spec/lib/listen/s
Processed: Bug#1027079 marked as pending in ruby-listen
Processing control commands: > tag -1 pending Bug #1027079 [src:ruby-listen] ruby-listen: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: @snapshots[dir].invalidate(type, rel_path, options) Added tag(s) pending. -- 1027079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027079: marked as pending in ruby-listen
Control: tag -1 pending Hello, Bug #1027079 in ruby-listen 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/ruby-team/ruby-listen/-/commit/6cdf5d3b6db9da49d0fc17454895c6d9d0e85087 Fix FTBFS with rspec-mock 3.12 and ruby 3.1 (Closes: #1027079). (this message was generated automatically) -- Greetings https://bugs.debian.org/1027079
Bug#1027075: marked as done (ruby-guard: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed.)
Your message dated Wed, 28 Dec 2022 03:36:04 +
with message-id
and subject line Bug#1027075: fixed in ruby-guard 2.18.0-3
has caused the Debian Bug report #1027075,
regarding ruby-guard: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1027075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-guard
Version: 2.18.0-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-guard failed to build.
Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1
> │
> └──┘
>
> GEM_PATH=/<>/debian/ruby-guard/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
> ruby3.1 -e gem\ \"guard\"
>
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-guard/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=/<>/debian/ruby-guard/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
> ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation
> Run options: include {:focus=>true}
>
> All examples were filtered out; ignoring {:focus=>true}
>
> Randomized with seed 28844
>
> Guard::UI
> .deprecation
> with GUARD_GEM_SILENCE_DEPRECATIONS set to 1
> silences deprecations
> with GUARD_GEM_SILENCE_DEPRECATIONS unset
> behaves like a logger method
> resets the line with the :reset option
> logs the message with the given severity
> with the :only option
> prevents logging other messages
> allows logging matching messages
> with the :except option
> prevents logging matching messages
> allows logging other messages
> .action_with_scopes
> without a scope
> with a global plugin scope
> shows the global plugin scoped action
> with a global group scope
> shows the global group scoped action
> with a groups scope
> stub me: ENV[COLUMNS]!
>
> Finished in 0.17765 seconds (files took 0.47034 seconds to load)
> 10 examples, 0 failures
>
> Randomized with seed 28844
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed.
The full build log is attached.
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
ruby-guard.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-guard
Source-Version: 2.18.0-3
Done: HIGUCHI Daisuke (VDR dai)
We believe that the bug you reported is fixed in the latest version of
ruby-guard, 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 furt
Processed: Bug#1027075 marked as pending in ruby-guard
Processing control commands: > tag -1 pending Bug #1027075 [src:ruby-guard] ruby-guard: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed. Added tag(s) pending. -- 1027075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027075: marked as pending in ruby-guard
Control: tag -1 pending Hello, Bug #1027075 in ruby-guard 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/ruby-team/ruby-guard/-/commit/903ab59fd940563c05e61a020479ef77f0c852a6 fix FTBFS with rspec-mock 3.12 and ruby 3+ (Closes: #1027075). (this message was generated automatically) -- Greetings https://bugs.debian.org/1027075
Bug#1027120: marked as done (phcpack: FTBFS: dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed.)
Your message dated Wed, 28 Dec 2022 03:09:04 + with message-id and subject line Bug#1027120: fixed in phcpack 2.4.86+dfsg-3 has caused the Debian Bug report #1027120, regarding phcpack: FTBFS: dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phcpack Version: 2.4.86+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=phcpack&arch=amd64&ver=2.4.86%2Bdfsg-2%2Bb3&stamp=1672159517&raw=0 dh_dwz -a -O--buildsystem=pybuild dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed. dh_dwz: error: dwz -mdebian/python3-phcpy/usr/lib/debug/.dwz/x86_64-linux-gnu/python3-phcpy.debug -M/usr/lib/debug/.dwz/x86_64-linux-gnu/python3-phcpy.debug -- debian/python3-phcpy/usr/lib/python3/dist-packages/phcpy/phcpy2c3.cpython-310-x86_64-linux-gnu.so debian/python3-phcpy/usr/lib/python3/dist-packages/phcpy/phcpy2c3.cpython-311-x86_64-linux-gnu.so died with signal 6 dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed. dh_dwz: error: dwz -- debian/phcpack/usr/bin/phc died with signal 6 dh_dwz: error: Aborting due to earlier error make: *** [debian/rules:11: binary-arch] Error 25 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: phcpack Source-Version: 2.4.86+dfsg-3 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of phcpack, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated phcpack package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 27 Dec 2022 21:26:50 -0500 Source: phcpack Built-For-Profiles: noudeb Architecture: source Version: 2.4.86+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Math Team Changed-By: Doug Torrance Closes: 1027120 Changes: phcpack (2.4.86+dfsg-3) unstable; urgency=medium . [ Nicolas Boulenguez ] * Trivial changes for dh-ada-library/8.2 . [ Doug Torrance ] * debian/control - Bump Standards-Version to 4.6.2. * debian/rules - Skip dh_dwz to avoid build failure (Closes: #1027120). Checksums-Sha1: 10947fe580a86d598534d023f4bba1319c6b9d48 2577 phcpack_2.4.86+dfsg-3.dsc 3ef59c34241fdb51d58257ded71803e011916a4c 18296 phcpack_2.4.86+dfsg-3.debian.tar.xz 5a3f48bf0323fa6cc41484384c065494dcf13265 12939 phcpack_2.4.86+dfsg-3_source.buildinfo Checksums-Sha256: 7dc1a226d4181c5c288435fb8be4b56d3d725ae91a2dbca3ca0a3e141afa2b43 2577 phcpack_2.4.86+dfsg-3.dsc cb8363151dad16f99d8777f95d1783c1ca23aa8615338acd495cea98bb0d30d7 18296 phcpack_2.4.86+dfsg-3.debian.tar.xz 6f85a1e30f8565e8d2955ef49d2f4a81190eb3f8989a9c13afa762da941d9cfe 12939 phcpack_2.4.86+dfsg-3_source.buildinfo Files: a9805e051d6c371295b86fcd65b0af7b 2577 math optional phcpack_2.4.86+dfsg-3.dsc 183e34422115e751ca8bbe44af7a16d9 18296 math optional phcpack_2.4.86+dfsg-3.debian.tar.xz d2cb86935e51cadbb711fcbd023758b6 12939 math optional phcpack_2.4.86+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEupghwS4HiU+y5K0AkdxKd57FyRAFAmOrqeUVHGR0b3JyYW5j ZUBkZWJpYW4ub3JnAAoJEJHcSneexckQzJAP/19rz4MsfksfWIrD6XN4+Fnf/nY7 DV0gXiFYbQQb/Le1xXb4qe/OG6QtLrbAl+PK4qYkkGwvY71GseBUYTK8SWbVf3zH qSqMLfYZkOruZLi0QImnlf91jS08UP/BAM1GJGAlyyYn6ZnOl/W4yZQzeo/QD/bV KKZhJ9ZGrWWIw+RPBOreCFjb4EFjw2Fp8K7pvF4tryGFCbUMmoQVLlD/GkBAq4nR et9+pE7zwBp6aihF1bAAh9qZqMWp/f+NwKj4HQ6kLHF1bmprKcOtNZ2hR3SqZY+E 8cHu8qHduDra2SndIvSHzEOjgCnQpAA3PbHgHIsAViZkPshzXraan79FAhkp1PN/ jqUJIiLZqoDhOlvSjux+pyCrQTETsTphutHUDCqWnARpbvXuJ2Z0SK48jv9zNRON VrJwgDpEDGa/aFM5VcstXFSAtXG3EUScqNzS7jEgF8q54GKyU8H9mENzdO1l7dLs tpQe/TnKjJtTv6PcjYnDvq4OYQr+1CPVRRCzA9CwtiOdSJ8y7jqrvCKhgbHTtHLU 6gzmpHD9ImurCMCE3z1ow84qMPrcAU02iNyKTpfCKobwp/Lirjc6klSaW
Bug#1027083: marked as done (ruby-notiffany: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: expect(foo_object).to receive(:notify).with("Hello", foo: "bar"))
Your message dated Wed, 28 Dec 2022 01:50:26 +
with message-id
and subject line Bug#1027083: fixed in ruby-notiffany 0.1.3-4
has caused the Debian Bug report #1027083,
regarding ruby-notiffany: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error: expect(foo_object).to
receive(:notify).with("Hello", foo: "bar")
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.)
--
1027083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-notiffany
Version: 0.1.3-3
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-notiffany failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: expect(foo_object).to receive(:notify).with("Hello",
> foo: "bar")
>
> # received
> :notify with unexpected arguments
> expected: ("Hello", {:foo=>"bar"}) (keyword arguments)
>got: ("Hello", {:foo=>"bar"}) (options hash)
> # ./spec/lib/notiffany/notifier_spec.rb:336:in `block (6 levels) in
> '
>
> Finished in 0.25327 seconds (files took 0.16632 seconds to load)
> 183 examples, 17 failures, 2 pending
>
> Failed examples:
>
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:67 #
> Notiffany::Notifier::TerminalNotifier#notify should allow the title to be
> customized
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:57 #
> Notiffany::Notifier::TerminalNotifier#notify should call the notifier.
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:78 #
> Notiffany::Notifier::TerminalNotifier#notify without a title set should show
> the app name in the title
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:45 #
> Notiffany::Notifier::TerminalNotifier#notify with options passed at
> initialization overwrites object options with passed options
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:38 #
> Notiffany::Notifier::TerminalNotifier#notify with options passed at
> initialization uses these options by default
> rspec ./spec/lib/notiffany/notifier/rb_notifu_spec.rb:80 #
> Notiffany::Notifier::Notifu#notify without additional options shows the
> notification with the default options
> rspec ./spec/lib/notiffany/notifier/rb_notifu_spec.rb:101 #
> Notiffany::Notifier::Notifu#notify with additional options can override the
> default options
> rspec ./spec/lib/notiffany/notifier/rb_notifu_spec.rb:40 #
> Notiffany::Notifier::Notifu#notify with options passed at initialization uses
> these options by default
> rspec ./spec/lib/notiffany/notifier/detected_spec.rb:112 #
> Notiffany::Notifier::Detected#add with manually configured notifiers when not
> available shows a warning
> rspec ./spec/lib/notiffany/notifier/detected_spec.rb:103 #
> Notiffany::Notifier::Detected#add with manually configured notifiers when not
> available does not add the library
> rspec ./spec/lib/notiffany/notifier/detected_spec.rb:108 #
> Notiffany::Notifier::Detected#add with manually configured notifiers when not
> available does not raise an error
> rspec ./spec/lib/notiffany/notifier/growl_spec.rb:144 #
> Notiffany::Notifier::Growl#notify with options Growl cannot handle passes
> options only Growl can handle
> rspec ./spec/lib/notiffany/notifier_spec.rb:182 #
> Notiffany::Notifier#initialize with custom notifier config when connected
> when enabled when supported when available adds the notifier to the
> notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:145 #
> Notiffany::Notifier#initialize with custom notifier config when not connected
> when enabled when supported when available adds the notifier to the
> notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:360 # Notiffany::Notifier.notify
> with multiple notifiers when connected when enabled sends notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:368 # Notiffany::Notifier.notify
> with multiple notifiers when connected when enabled when a child process
> sends notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:335 # Notiffany::Notifier.notify
> with multiple notifiers when not connected when a child process sends
> notifications
>
> Randomized with seed 32791
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integratio
Bug#1012631: marked as done (tcp-wrappers: d/copyright is incomplete)
Your message dated Wed, 28 Dec 2022 01:50:39 + with message-id and subject line Bug#1012631: fixed in tcp-wrappers 7.6.q-32 has caused the Debian Bug report #1012631, regarding tcp-wrappers: d/copyright is incomplete 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.) -- 1012631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcp-wrappers Version: 7.6.q-31 Severity: important Hi, tcp-wrappers's debian/copyright file is missing the BSD license in strcasecmp.c. Please add it. It would be nice of you to convert it to the machine-readable format. Also, there is a copyright notice in debian/patches/05_wildcard_matching that has to be included. The covered patch portion claims to be "under free license", so it might be covered by an additional license. Thanks, Bastian --- End Message --- --- Begin Message --- Source: tcp-wrappers Source-Version: 7.6.q-32 Done: Marco d'Itri We believe that the bug you reported is fixed in the latest version of tcp-wrappers, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri (supplier of updated tcp-wrappers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Dec 2022 02:39:26 +0100 Source: tcp-wrappers Architecture: source Version: 7.6.q-32 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri Changed-By: Marco d'Itri Closes: 1012631 Changes: tcp-wrappers (7.6.q-32) unstable; urgency=medium . [ Bastian Germann ] * Converted debian/copyright to machine-readable format. (Closes: #1012631) . [ Marco d'Itri ] * Added some autopkgtest tests. * Enabled hardening=+all. Checksums-Sha1: 33671a070b8f743897bba6e26a1936ff6a402370 1390 tcp-wrappers_7.6.q-32.dsc 62d426b44cfa17976b2ddd7d97fbdb2609c8518c 38040 tcp-wrappers_7.6.q-32.debian.tar.xz bcadc9c4a31be46dcd5fb740cb008b0b761408c0 6474 tcp-wrappers_7.6.q-32_amd64.buildinfo Checksums-Sha256: c9620a45e897c786b99890b54c6ea916df2380b6f3260e1e6442a1f8b5066997 1390 tcp-wrappers_7.6.q-32.dsc deec7966808407ddcb11581380c7253c348bd8780da6c9ee17fa9e7a729539fe 38040 tcp-wrappers_7.6.q-32.debian.tar.xz f2ffc7aa2c5ab09f0e4c465c59b7123a2bdbedbafac3f0fbe3324071befac566 6474 tcp-wrappers_7.6.q-32_amd64.buildinfo Files: d2547dfe022e453549a9d5b8aab179bc 1390 net optional tcp-wrappers_7.6.q-32.dsc 8152f6da523207adcf1b4d9958b478b5 38040 net optional tcp-wrappers_7.6.q-32.debian.tar.xz 93ddfcc7d1be226f8f2caf62132c56c0 6474 net optional tcp-wrappers_7.6.q-32_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCY6ue0gAKCRDLPsM64d7X gSEpAQDpnKv4rbomqwuZaYV1wnG+V64CmArhSCpLCy69Jx9vpgD/dLB1yy37x+9F dR3QBc6UThMJN4u/YcfGMOEjnIsJaws= =aq+Z -END PGP SIGNATURE End Message ---
Bug#1027114: docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced)
On Tue, 27 Dec 2022, 15:18 Sebastian Ramacher, wrote: > ---> Making bundle: dynbinary (in bundles/dynbinary) > Building: bundles/dynbinary-daemon/dockerd-20.10.21+dfsg1 > GOOS="" GOARCH="" GOARM="" > # github.com/docker/docker/daemon/graphdriver/btrfs > daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced > undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method > max_referenced) > make[1]: *** [debian/rules:114: override_dh_auto_build] Error 2 > make[1]: Leaving directory '/<>' > Looks like it's probably the recently reported https://github.com/moby/moby/issues/44698 👀 - Tianon >
Processed: Bug#1027083 marked as pending in ruby-notiffany
Processing control commands:
> tag -1 pending
Bug #1027083 [src:ruby-notiffany] ruby-notiffany: FTBFS with ruby-rspec 3.12:
ERROR: Test "ruby3.1" failed: Failure/Error: expect(foo_object).to
receive(:notify).with("Hello", foo: "bar")
Added tag(s) pending.
--
1027083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027083: marked as pending in ruby-notiffany
Control: tag -1 pending Hello, Bug #1027083 in ruby-notiffany 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/ruby-team/ruby-notiffany/-/commit/19306907a056e4f6df643497fb2b44dd40eac9a4 fix FTBFS with ruby-rspec 3.12 and ruby3.1 (Closes: #1027083). (this message was generated automatically) -- Greetings https://bugs.debian.org/1027083
Processed: fixed 1023239 in 057+157-1~bpo11+1, fixed 1021229 in 057+157-1~bpo11+1 ...
Processing commands for cont...@bugs.debian.org:
> fixed 1023239 057+157-1~bpo11+1
Bug #1023239 {Done: Thomas Lange } [dracut] dracut:
[regression] missing grep
Marked as fixed in versions dracut/057+157-1~bpo11+1.
> fixed 1021229 057+157-1~bpo11+1
Bug #1021229 {Done: Thomas Lange } [dracut-core] dracut:
dracut-shutdown.service fails because dracut looks for initramfs instead initrd
Marked as fixed in versions dracut/057+157-1~bpo11+1.
> fixed 1017411 057+157-1~bpo11+1
Bug #1017411 {Done: Thomas Lange } [dracut] dracut:
90kernel-modules spends 150ms doing a 3ms grep in bash
Marked as fixed in versions dracut/057+157-1~bpo11+1.
> fixed 1016741 057+157-1~bpo11+1
Bug #1016741 {Done: Thomas Lange } [dracut-network] Wrong
paths to nm-initrd-generator
Marked as fixed in versions dracut/057+157-1~bpo11+1.
> fixed 1016727 057+157-1~bpo11+1
Bug #1016727 {Done: Thomas Lange } [dracut] dracut: FIDO2
support for encrypted root FS is missing libraries (libz.so.*)
Marked as fixed in versions dracut/057+157-1~bpo11+1.
> fixed 1016051 057+157-1~bpo11+1
Bug #1016051 {Done: Thomas Lange } [dracut] dracut: Wrong
path to `$prefix/dbus/system.d/bluetooth.conf`
Marked as fixed in versions dracut/057+157-1~bpo11+1.
> fixed 1015922 057+157-1~bpo11+1
Bug #1015922 {Done: Thomas Lange } [dracut-core] dracut-core:
grep missing in 90lvm/lvm_scan
Marked as fixed in versions dracut/057+157-1~bpo11+1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1015922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015922
1016051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016051
1016727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016727
1016741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016741
1017411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017411
1021229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021229
1023239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1025530: llvm-toolchain-15: FTBFS with grpc 1.51+
Source: llvm-toolchain-15 Version: 1:15.0.6-3 Followup-For: Bug #1025530 X-Debbugs-Cc: trib...@gmail.com Dear Maintainer, Where can I download the previous (libllvm15_15.0.6-3_i386.deb) i386 deb file, so I can continue my installation? Regards, Robin van Westrenen -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/16 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
Bug#1026646: marked as done (python-meshio: FTBFS: mv: cannot stat 'debian/python3-meshio/usr/lib/python3.10/dist-packages/share/paraview*': No such file or directory)
Your message dated Wed, 28 Dec 2022 00:10:45 + with message-id and subject line Bug#1026646: fixed in python-meshio 7.0.0-2 has caused the Debian Bug report #1026646, regarding python-meshio: FTBFS: mv: cannot stat 'debian/python3-meshio/usr/lib/python3.10/dist-packages/share/paraview*': No such file or directory 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.) -- 1026646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-meshio Version: 7.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_testroot -O--buildsystem=pybuild >dh_prep -O--buildsystem=pybuild >debian/rules override_dh_auto_install > make[1]: Entering directory '/<>' > dh_auto_install > I: pybuild plugin_pyproject:160: Copying package built for python3.11 to > destdir > I: pybuild plugin_pyproject:160: Copying package built for python3.10 to > destdir > dh_movefiles -pmeshio-tools --sourcedir=debian/python3-meshio usr/bin > mkdir -p debian/meshio-tools/usr/share > mv debian/python3-meshio/usr/lib/python3.10/dist-packages/share/paraview* > debian/meshio-tools/usr/share > mv: cannot stat > 'debian/python3-meshio/usr/lib/python3.10/dist-packages/share/paraview*': No > such file or directory > make[1]: *** [debian/rules:31: override_dh_auto_install] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/python-meshio_7.0.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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 mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-meshio Source-Version: 7.0.0-2 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of python-meshio, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated python-meshio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Dec 2022 00:43:12 +0100 Source: python-meshio Architecture: source Version: 7.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 1026646 Changes: python-meshio (7.0.0-2) unstable; urgency=medium . * Team upload. * update debian/rules: tools now install paraview script correctly into usr/share not the python module dir. Closes: #1026646. * debian/tests: run tests over all supported python versions * Standards-Version: 4.6.2 Checksums-Sha1: 23e2cbb29b33f8655f104b0cb7f430712e259fdb 2608 python-meshio_7.0.0-2.dsc 02b2b71f53c3c39ef75c8f273bb90c7d990dd141 27928 python-meshio_7.0.0-2.debian.tar.xz Checksums-Sha256: 8ea2f6612e31d0b8f6214a6ccffd250deee332ac60af3bd00c23677c728138a9 2608 python-meshio_7.0.0-2.dsc a553037804ca8d8e18718aab2dd6dbb7f6d1ed4d0511d0ee6b5eba6b14dfdb97 27928 python-meshio_7.0.0-2.debian.tar.xz Files: b63184e86951defb48ac82536d222629 2608 python optional python-meshio_7.0.0-2.dsc 7b6cd283231fc3530183ed742242ff2d 27928 python optional python-meshio_7.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8m
Bug#1023697: wolfSSL 5.5.4 uploaded
Hi, > there is considerable interest in using WolfSSL I uploaded version 5.5.4-1, which was released last week, to the archive. Kind regards Felix Lechner
Bug#966783: marked as done (python-pmw: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 28 Dec 2022 00:00:09 + with message-id and subject line Bug#966783: fixed in python-pmw 2.1-1 has caused the Debian Bug report #966783, regarding python-pmw: 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.) -- 966783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pmw Version: 1.3.2-6 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 --- Source: python-pmw Source-Version: 2.1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of python-pmw, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated python-pmw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 17:24:06 +0100 Source: python-pmw Binary: python-pmw-doc python3-pmw Architecture: source all Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Description: python-pmw-doc - Pmw -- Python MegaWidgets (documentation) python3-pmw - Pmw -- Python MegaWidgets (python3 module) Closes: 886617 890750 938036 966783 994095 Changes: python-pmw (2.1-1) unstable; urgency=medium . * Team upload. * debian/copyright: + Add missing GPL-2+. + Convert to machine-readable format. . [ Boyuan Yang ] * Take over package maintenance via ITS process. (Closes: #994095) * New upstream release. (Closes: #890750) + Migrate to python3. (Closes: #886617, #938036, #966783) * debian/control: + Bump Standards-Version to 4.6.0. + Bump debhelper compat to v13. + Add Vcs-* fields to use git packaging repo under Debian Python Team. + Add Homepage field. + Mark python-pmw-doc package as Multi-Arch: foreign. * debian/rules: Rewrite with dh13 syntax. Checksums-Sha1: c6eec4860f422297add73c203349085e680d3408 1871 python-pmw_2.1-1.dsc 8f6c2aea0a46dda6afd858cf1df204c0e7114249 1076920 python-pmw_2.1.orig.tar.gz b21fa4a2e23b4f6a4ec39c5a64d0852a50a4322f 5104 python-pmw_2.1-1.debian.tar.xz 1d951bc54ee7121dd98e7d6381d1a80127144bab 213288 python-pmw-doc_2.1-1_all.deb fc633bc6ab8de6242d4767a3fcbe4d990ffbb9ad 7265 python-pmw_2.1-1_amd64.buildinfo b12dba93636318904ee23aa4f4b6e63f1dc68787 66280 python3-pmw_2.1-1_all.deb Checksums-Sha256: d5ea44ea6781e8bdf0edcab95846ec21233eaea62af0cab3cc666287c3adc735 1871 python-pmw_2.1-1.dsc c35a92a6cabacd866467f7a1a19ab01b8e8175aadfc083c93ac8baf98e92b6ce 1076920 python-pmw_2.1.orig.tar.gz 3d4b98806d2a41898f8c4684eefa7f381541696d6f421d160229b441c556f3cc 5104 python-pmw_2.1-1.debian.tar.xz 2160e0c0f93ab402062cd802bd947180d2cb5dc472a2709f261c789d7d683bcf 213288 python-pmw-doc_2.1-1_all.deb 9bdc162f0ba843a614d64dbbc32c64d19258273fbdc5f0e3b8e10e9a3a024687 7265 python-pmw_2.1-1_amd64.buildinfo 1d09a686e5a9385027c0eb598c865039b0053316a58481bab86b5a87ac4b689f 66280 python3-pmw_2.1-1_all.deb Files: c2e04
Bug#938036: marked as done (python-pmw: Python2 removal in sid/bullseye)
Your message dated Wed, 28 Dec 2022 00:00:09 + with message-id and subject line Bug#938036: fixed in python-pmw 2.1-1 has caused the Debian Bug report #938036, regarding python-pmw: 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.) -- 938036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pmw Version: 1.3.2-6 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:python-pmw 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: python-pmw Source-Version: 2.1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of python-pmw, 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 python-pmw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 17:24:06 +0100 Source: python-pmw Binary: python-pmw-doc python3-pmw Architecture: source all Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Description: python-pmw-doc - Pmw -- Python MegaWidgets (documentation) python3-pmw - Pmw -- Python MegaWidgets (python3 module) Closes: 886617 890750 938036 966783 994095 Changes: python-pmw (2.1-1) unstable; urgency=medium . * Team upload. * debian/copyright: + Add missing GPL-2+. + Convert to machine-readable format. . [ Boyuan Yang ] * Take over package maintenance via ITS process. (Closes: #994095) * New upstream release. (Closes: #890750) + Migrate to python3. (Closes: #886617, #938036, #966783) * debian/control: + Bump Standards-Version to 4.6.0. + Bump debhelper compat to v13. + Add Vcs-* fields to use git packaging repo under Debian Python
Bug#886617: marked as done (python-pmw: Please package version 2.1 and include Python 3 support)
Your message dated Wed, 28 Dec 2022 00:00:09 + with message-id and subject line Bug#886617: fixed in python-pmw 2.1-1 has caused the Debian Bug report #886617, regarding python-pmw: Please package version 2.1 and include Python 3 support 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.) -- 886617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pmw Version: 1.3.2-6 Severity: wishlist Dear Maintainer, Version 2.0.0 of python-pmw has been released for a while now and includes Python 3 support as well. It would be good to have it available in Debian, perhaps as a second source package if that is required to support both Python 2 and Python 3. https://sourceforge.net/projects/pmw/ thanks Stuart --- End Message --- --- Begin Message --- Source: python-pmw Source-Version: 2.1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of python-pmw, 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 886...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated python-pmw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Nov 2022 17:24:06 +0100 Source: python-pmw Binary: python-pmw-doc python3-pmw Architecture: source all Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Description: python-pmw-doc - Pmw -- Python MegaWidgets (documentation) python3-pmw - Pmw -- Python MegaWidgets (python3 module) Closes: 886617 890750 938036 966783 994095 Changes: python-pmw (2.1-1) unstable; urgency=medium . * Team upload. * debian/copyright: + Add missing GPL-2+. + Convert to machine-readable format. . [ Boyuan Yang ] * Take over package maintenance via ITS process. (Closes: #994095) * New upstream release. (Closes: #890750) + Migrate to python3. (Closes: #886617, #938036, #966783) * debian/control: + Bump Standards-Version to 4.6.0. + Bump debhelper compat to v13. + Add Vcs-* fields to use git packaging repo under Debian Python Team. + Add Homepage field. + Mark python-pmw-doc package as Multi-Arch: foreign. * debian/rules: Rewrite with dh13 syntax. Checksums-Sha1: c6eec4860f422297add73c203349085e680d3408 1871 python-pmw_2.1-1.dsc 8f6c2aea0a46dda6afd858cf1df204c0e7114249 1076920 python-pmw_2.1.orig.tar.gz b21fa4a2e23b4f6a4ec39c5a64d0852a50a4322f 5104 python-pmw_2.1-1.debian.tar.xz 1d951bc54ee7121dd98e7d6381d1a80127144bab 213288 python-pmw-doc_2.1-1_all.deb fc633bc6ab8de6242d4767a3fcbe4d990ffbb9ad 7265 python-pmw_2.1-1_amd64.buildinfo b12dba93636318904ee23aa4f4b6e63f1dc68787 66280 python3-pmw_2.1-1_all.deb Checksums-Sha256: d5ea44ea6781e8bdf0edcab95846ec21233eaea62af0cab3cc666287c3adc735 1871 python-pmw_2.1-1.dsc c35a92a6cabacd866467f7a1a19ab01b8e8175aadfc083c93ac8baf98e92b6ce 1076920 python-pmw_2.1.orig.tar.gz 3d4b98806d2a41898f8c4684eefa7f381541696d6f421d160229b441c556f3cc 5104 python-pmw_2.1-1.debian.tar.xz 2160e0c0f93ab402062cd802bd947180d2cb5dc472a2709f261c789d7d683bcf 213288 python-pmw-doc_2.1-1_all.deb 9bdc162f0ba843a614d64dbbc32c64d19258273fbdc5f0e3b8e10e9a3a024687 7265 python-pmw_2.1-1_amd64.buildinfo 1d09a686e5a9385027c0eb598c865039b0053316a58481bab86b5a87ac4b689f 66280 python3-pmw_2.1-1_all.deb Files: c2e043a9fdedabff056dbbd62af945b6 1871 python optional python-pmw_2.1-1.dsc 64bb62cb851a6c915be6f98e56a89e4e 1076920 python optional python-pmw_2.1.orig.tar.gz bb9f2b8255c312abff097ce108030f28 5104 python optional python-pmw_2.1-1.debian.tar.xz 01f4b342f50ab855c9141920a793df27 213288 doc optional python-pmw-doc_2.1-1_all.deb 931c70e367f51c6e54d98084f906a6e8 7265 python optional python-pmw_2.1-1_amd64.buildinfo 904fa5e86ae729483ef27471c662714b 66280 python optional python3-pmw_2.1-1_all.deb -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmNzzhwQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFCRmDACje19VUNoqsXfis+0vFPK70wso2npxDn1d kSa7C1xLnLOprtE2rPm4gvheMZpOZnn5zKP+JV5ZM3HSNrhVP
Bug#1026757: marked as done (gatk-native-bindings: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 25)
Your message dated Tue, 27 Dec 2022 23:50:28 + with message-id and subject line Bug#1026757: fixed in gatk-native-bindings 1.0.0+dfsg-1 has caused the Debian Bug report #1026757, regarding gatk-native-bindings: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 25 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.) -- 1026757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gatk-native-bindings Version: 1.0.0-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build -- jar > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=gatk-native-bindings > -Dfile.encoding=UTF-8 --parallel --max-workers=8 jar > OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=permit; > support was removed in 17.0 > Initialized native services in: /<>/.gradle/native > To honour the JVM settings for this build a new JVM will be forked. Please > consider using the daemon: > https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html. > Starting process 'Gradle build daemon'. Working directory: > /<>/.gradle/daemon/4.4.1 Command: > /usr/lib/jvm/java-17-openjdk-amd64/bin/java > -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar > -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp > /usr/share/gradle/lib/gradle-launcher-4.4.1.jar > org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1 > Successfully started process 'Gradle build daemon' > An attempt to start the daemon took 1.208 secs. > The client will now receive all logging from the daemon (pid: 1153077). The > daemon log file: /<>/.gradle/daemon/4.4.1/daemon-1153077.out.log > Daemon will be stopped at the end of the build stopping after processing > Closing daemon's stdin at end of input. > The daemon will no longer process any standard input. > Using 8 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@1ec3cd8a > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@1ec3cd8a > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@27eb4497 > > 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.assemblePara
Bug#1027116: golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no fi
Control: reassign -1 src:golang-github-containers-storage 1.43.0+ds1-3 Control: affects -1 src:golang-github-containers-buildah src:libpod On 2022-12-28 00:20:58 +0100, Sebastian Ramacher wrote: > Source: golang-github-containers-buildah > Version: 1.28.0+ds1-3 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > https://buildd.debian.org/status/fetch.php?pkg=golang-github-containers-buildah&arch=amd64&ver=1.28.0%2Bds1-3%2Bb1&stamp=1672115946&raw=0 > > # github.com/containers/storage/drivers/btrfs > src/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: > args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has > no field or method max_referenced) The file is from golang-github-containers-storage-dev. Reassigning accordingly. Cheers > github.com/containers/storage/drivers/copy > github.com/containers/storage/drivers/devmapper > github.com/containers/common/pkg/supplemented > database/sql/driver > github.com/containers/storage/pkg/lockfile > github.com/containers/storage/drivers/vfs > github.com/containers/storage/pkg/stringid > github.com/google/uuid > github.com/containers/storage/pkg/stringutils > github.com/containers/storage/pkg/tarlog > github.com/tchap/go-patricia/patricia > github.com/mistifyio/go-zfs > github.com/google/go-intervals/intervalset > github.com/vbatts/tar-split/tar/asm > github.com/containers/storage/pkg/truncindex > github.com/containerd/stargz-snapshotter/estargz/errorutil > golang.org/x/sync/errgroup > github.com/cyphar/filepath-securejoin > github.com/containers/image/directory/explicitfilepath > github.com/containerd/stargz-snapshotter/estargz > github.com/containers/storage/drivers/zfs > github.com/containers/image/directory > github.com/containers/image/docker/policyconfiguration > github.com/containers/image/internal/streamdigest > github.com/containers/image/internal/uploadreader > github.com/containers/image/pkg/sysregistriesv2 > github.com/docker/docker-credential-helpers/credentials > golang.org/x/sys/execabs > golang.org/x/net/internal/socks > github.com/docker/docker-credential-helpers/client > github.com/docker/go-connections/tlsconfig > github.com/containers/image/pkg/docker/config > golang.org/x/net/proxy > github.com/docker/distribution/registry/api/errcode > github.com/docker/go-connections/sockets > github.com/docker/distribution/digestset > github.com/gorilla/mux > github.com/docker/distribution/reference > github.com/containers/image/pkg/tlsclientconfig > github.com/docker/distribution/registry/client/auth/challenge > gopkg.in/yaml.v2 > github.com/containers/image/docker/internal/tarfile > github.com/docker/docker/api/types/blkiodev > github.com/docker/distribution/registry/api/v2 > github.com/docker/docker/api/types/mount > github.com/docker/docker/api/types/strslice > github.com/docker/go-connections/nat > github.com/docker/docker/api/types/container > github.com/docker/docker/api/types/filters > github.com/containers/image/docker/archive > github.com/docker/docker/api/types/registry > github.com/gogo/protobuf/proto > github.com/docker/docker/api/types/network > github.com/docker/docker/api/types/time > github.com/docker/docker/errdefs > net/http/httputil > github.com/containers/image/oci/internal > github.com/containers/image/oci/layout > github.com/sylabs/sif/pkg/sif > github.com/containers/image/oci/archive > github.com/ghodss/yaml > github.com/containers/image/docker > github.com/containers/image/tarball > github.com/containers/image/sif > github.com/opencontainers/runc/libcontainer/utils > github.com/opencontainers/runc/libcontainer/apparmor > text/template/parse > github.com/containers/common/pkg/apparmor/internal/supported > github.com/containers/common/pkg/capabilities > github.com/containers/common/pkg/cgroupv2 > github.com/containers/common/pkg/util > github.com/containers/common/pkg/download > github.com/containers/common/pkg/timetype > github.com/containers/common/pkg/retry > github.com/containers/common/pkg/filters > github.com/containers/common/pkg/signal > github.com/chzyer/readline > text/template > github.com/lunixbochs/vtclean > github.com/juju/ansiterm/tabwriter > github.com/mattn/go-isatty > github.com/mattn/go-colorable > github.com/juju/ansiterm > github.com/manifoldco/promptui/list > github.com/containers/common/pkg/apparmor > github.com/manifoldco/promptui/screenbuf > github.com/disiqueira/gotree > github.com/docker/docker/api/types/swarm/runtime > database/sql > github.com/containers/common/pkg/config > github.com/manifoldco/promptui > github.com/docker/docker/api/types/swarm > github.com/docker/docker/api/types > github.com/containers/image/pkg/shortnames > github.com/docker/docker/api/types/volume > github.com/docker/docker/client > github.com/seccomp/libseccomp-golang > github.com/containers/buildah/docker > github.com/containers/ocicrypt/helpers > github.com/jinzhu/copier > github.com/containers
Processed: affects 1027116
Processing commands for cont...@bugs.debian.org: > affects 1027116 src:skopeo Bug #1027116 [src:golang-github-containers-storage] golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) Added indication that 1027116 affects src:skopeo > thanks Stopping processing here. Please contact me if you need assistance. -- 1027116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1027116: golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_
Processing control commands: > reassign -1 src:golang-github-containers-storage 1.43.0+ds1-3 Bug #1027116 [src:golang-github-containers-buildah] golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) Bug reassigned from package 'src:golang-github-containers-buildah' to 'src:golang-github-containers-storage'. No longer marked as found in versions golang-github-containers-buildah/1.28.0+ds1-3. Ignoring request to alter fixed versions of bug #1027116 to the same values previously set Bug #1027116 [src:golang-github-containers-storage] golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) Marked as found in versions golang-github-containers-storage/1.43.0+ds1-3. > affects -1 src:golang-github-containers-buildah src:libpod Bug #1027116 [src:golang-github-containers-storage] golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) Added indication that 1027116 affects src:golang-github-containers-buildah and src:libpod -- 1027116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027122: nomad-driver-podman: FTBFS: unknown error
Source: nomad-driver-podman Version: 0.1.0-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nomad-driver-podman&arch=amd64&ver=0.1.0-2%2Bb7&stamp=1672122772&raw=0 cd _build && go install -trimpath -v -p 4 github.com/hashicorp/nomad-driver-podman github.com/hashicorp/nomad-driver-podman/iopodman github.com/hashicorp/nomad-driver-podman/version src/github.com/hashicorp/nomad/vendor/github.com/hashicorp/hcl/v2/pos_scanner.go:7:2: cannot find package "github.com/apparentlymart/go-textseg/v12/textseg" in any of: /<>/_build/src/github.com/hashicorp/nomad/vendor/github.com/apparentlymart/go-textseg/v12/textseg (vendor tree) /usr/lib/go-1.19/src/github.com/apparentlymart/go-textseg/v12/textseg (from $GOROOT) /<>/_build/src/github.com/apparentlymart/go-textseg/v12/textseg (from $GOPATH) dh_auto_build: error: cd _build && go install -trimpath -v -p 4 github.com/hashicorp/nomad-driver-podman github.com/hashicorp/nomad-driver-podman/iopodman github.com/hashicorp/nomad-driver-podman/version returned exit code 1 Cheers -- Sebastian Ramacher
Bug#1026912: marked as done (hypre: autopkgtest regularly timeouts on armhf)
Your message dated Tue, 27 Dec 2022 23:36:12 + with message-id and subject line Bug#1026912: fixed in hypre 2.26.0-3 has caused the Debian Bug report #1026912, regarding hypre: autopkgtest regularly timeouts on armhf 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.) -- 1026912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hypre Version: 2.18.2-1 Severity: serious User: debian...@lists.debian.org Usertags: timeout Control: found -1 2.25.0-2 2.26.0-2 2.22.1-3 Dear maintainer(s), Your package has an autopkgtest, great. However, it fails regularly on armhf. What's worse, it regularly fails because it seems to hang and eventually times out due to autopkgtest. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. Also tests that time out (while normally running in much less time) are bad for our infrastructure. I have added your package to our reject_list and will remove it once this bug is closed. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/armhf/h/hypre/29021897/log.gz Building ij_mv ... mpicc -o ij_mv ij_mv.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi -c -o ij_mm.o ij_mm.c Building ij_mm ... mpicc -o ij_mm ij_mm.o -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist -I/usr/lib/arm-linux-gnueabihf/openmpi/include -I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi -c zboxloop.c -o zboxloop.obj Building zboxloop ... mpicc -o zboxloop zboxloop.obj -L/lib -lHYPRE -Wl,-rpath,/lib -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm Running tests for HYPRE testing began at Mon Dec 5 09:15:39 CST 2022 running TEST_ams ... autopkgtest [12:02:11]: ERROR: timed out on command "su -s /bin/bash debci OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: hypre Source-Version: 2.26.0-3 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of hypre, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated hypre package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 27 Dec 2022 21:46:13 +0100 Source: hypre Architecture: source Version: 2.26.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 1026912 Changes: hypre (2.26.0-3) unstable; urgency=medium . * Team upload. * debian/tests: armhf has been placed in the black list (Architecture: !armhf) for occasionally failing debci tests. Closes: #1026912. * Standards-Version: 4.6.2 Checksums-Sha1: b2a888d55c2376222387e1ec91232f41aa2c5279 3436 hypre_2.26.0-3.dsc d197ab81eaebdb9d5592d006f08a07cae4fa2f2a 18736 hypre_2.26.0-3.debian.tar.xz Checksums-Sha256: 87ec2b1f80025d3d6507bf691aba831631e3d857ffc47cb18a5da70236da210b 3436 hypre_2.26.0-3.dsc fb5cff595d3b98a8b3b65b8fa79119cb945e780481e571e9b60d192cd6e0975b 18736 hypre_2.26.0-3.debian.tar.xz Files: 52f3662d447b01cc81301f23625f8fa4 3436 math optional hypre_2.26.0-3.dsc b0bd10758973ab809bac77d9e39a0c8c 18736 math optional hypre_2.26.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmOreKsACgkQVz7x5L1a AfoJKg//Zp0JzobpP/4svPHQkT9fkYrDY3tDmo41dNmpodSLpboWoYAiIrvQFSD3 fyeNxV6GzD477tl+egwvgDA
Processed: tagging 1027111, tagging 1027112, tagging 1027114, tagging 1027115, tagging 1027116, tagging 1027117 ...
Processing commands for cont...@bugs.debian.org: > tags 1027111 + sid bookworm Bug #1027111 [src:wine] wine: FTBFS: error: writing 56 bytes into a region of size 8 Added tag(s) bookworm and sid. > tags 1027112 + sid bookworm Bug #1027112 [src:bazel-bootstrap] bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' Added tag(s) sid and bookworm. > tags 1027114 + sid bookworm Bug #1027114 [src:docker.io] docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) Added tag(s) bookworm and sid. > tags 1027115 + sid bookworm Bug #1027115 [src:gobgp] gobgp: FTBFS: unknown error Added tag(s) bookworm and sid. > tags 1027116 + sid bookworm Bug #1027116 [src:golang-github-containers-buildah] golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) Added tag(s) sid and bookworm. > tags 1027117 + sid bookworm Bug #1027117 [src:iem-plugin-suite] iem-plugin-suite: FTBFS: error: ‘class juce::AudioProcessorPlayer’ has no member named ‘audioDeviceIOCallback’; did you mean ‘AudioIODeviceCallback’? Added tag(s) sid and bookworm. > tags 1027118 + sid bookworm Bug #1027118 [src:zabbix] zabbix: FTBFS: error: invalid use of void expression Added tag(s) sid and bookworm. > tags 1027119 + sid bookworm Bug #1027119 [src:yara] yara: FTBFS: FAIL: test-magic Added tag(s) sid and bookworm. > tags 1027120 + sid bookworm Bug #1027120 [src:phcpack] phcpack: FTBFS: dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed. Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027111 1027112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027112 1027114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027114 1027115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027115 1027116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027116 1027117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027117 1027118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027118 1027119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027119 1027120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026598: blocked by NEW queue
In order to fix this issue, I'm waiting for https://ftp-master.debian.org/new/rust-trust-dns-server_0.22.0-1.html to make it out of (binary) NEW. -- regards, Reinhard
Bug#1026618: marked as done (rust-trust-dns-client: FTBFS: build-dependency not installable: librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~))
Your message dated Tue, 27 Dec 2022 18:31:31 -0500 with message-id and subject line Fixed in 0.22.0-1 has caused the Debian Bug report #1026618, regarding rust-trust-dns-client: FTBFS: build-dependency not installable: librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~) 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.) -- 1026618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-trust-dns-client Version: 0.21.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-cfg-if-1+default-dev, > librust-data-encoding-2+default-dev (>= 2.2.0-~~), > librust-futures-channel-0.3+std-dev (>= 0.3.5-~~), > librust-futures-util-0.3+std-dev (>= 0.3.5-~~), > librust-lazy-static-1+default-dev (>= 1.2.0-~~), librust-log-0.4+default-dev, > librust-radix-trie-0.2+default-dev, librust-rand-0.8+default-dev, > librust-thiserror-1+default-dev (>= 1.0.20-~~), librust-time-0.3+default-dev, > librust-tokio-1+default-dev, librust-tokio-1+rt-dev, > librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~), build-essential, > fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-cfg-if-1+default-dev, > librust-data-encoding-2+default-dev (>= 2.2.0-~~), > librust-futures-channel-0.3+std-dev (>= 0.3.5-~~), > librust-futures-util-0.3+std-dev (>= 0.3.5-~~), > librust-lazy-static-1+default-dev (>= 1.2.0-~~), librust-log-0.4+default-dev, > librust-radix-trie-0.2+default-dev, librust-rand-0.8+default-dev, > librust-thiserror-1+default-dev (>= 1.0.20-~~), librust-time-0.3+default-dev, > librust-tokio-1+default-dev, librust-tokio-1+rt-dev, > librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~), build-essential, > fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [560 B] > Get:5 copy:/<>/apt_archive ./ Packages [636 B] > Fetched 2159 B in 0s (174 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: > librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~) but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2022/12/20/rust-trust-dns-client_0.21.2-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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 mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 0.22.0-1 This was fixed the
Bug#1027120: phcpack: FTBFS: dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed.
Source: phcpack Version: 2.4.86+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=phcpack&arch=amd64&ver=2.4.86%2Bdfsg-2%2Bb3&stamp=1672159517&raw=0 dh_dwz -a -O--buildsystem=pybuild dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed. dh_dwz: error: dwz -mdebian/python3-phcpy/usr/lib/debug/.dwz/x86_64-linux-gnu/python3-phcpy.debug -M/usr/lib/debug/.dwz/x86_64-linux-gnu/python3-phcpy.debug -- debian/python3-phcpy/usr/lib/python3/dist-packages/phcpy/phcpy2c3.cpython-310-x86_64-linux-gnu.so debian/python3-phcpy/usr/lib/python3/dist-packages/phcpy/phcpy2c3.cpython-311-x86_64-linux-gnu.so died with signal 6 dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed. dh_dwz: error: dwz -- debian/phcpack/usr/bin/phc died with signal 6 dh_dwz: error: Aborting due to earlier error make: *** [debian/rules:11: binary-arch] Error 25 Cheers -- Sebastian Ramacher
Bug#997083: marked as done (python2.7: FTBFS: tests fail: test_curses test_distutils test_signal test_site test_tk)
Your message dated Tue, 27 Dec 2022 23:25:10 + with message-id and subject line Bug#1027108: Removed package(s) from unstable has caused the Debian Bug report #997083, regarding python2.7: FTBFS: tests fail: test_curses test_distutils test_signal test_site test_tk 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.) -- 997083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python2.7 Version: 2.7.18-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > == > > FAIL: test_type (test_tkinter.test_widgets.MenuTest) > > -- > > Traceback (most recent call last): > > File "/<>/Lib/lib-tk/test/test_tkinter/test_widgets.py", line > 1165, in test_type > > 'normal', 'tearoff', 'menubar') > > File "/<>/Lib/lib-tk/test/widget_tests.py", line 168, in > checkEnumParam > > errmsg='ambiguous' + errmsg2) > > File "/<>/Lib/lib-tk/test/widget_tests.py", line 82, in > checkInvalidParam > > widget[name] = value > > AssertionError: TclError not raised > > > > == > > FAIL: test_from (test_tkinter.test_widgets.ScaleTest) > > -- > > Traceback (most recent call last): > > File "/<>/Lib/lib-tk/test/test_tkinter/test_widgets.py", line > 864, in test_from > > self.checkFloatParam(widget, 'from', 100, 14.9, 15.1, conv=round) > > File "/<>/Lib/lib-tk/test/widget_tests.py", line 117, in > checkFloatParam > > self.checkParam(widget, name, value, conv=conv, **kwargs) > > File "/<>/Lib/lib-tk/test/widget_tests.py", line 68, in > checkParam > > self.assertEqual2(widget[name], expected, eq=eq) > > File "/<>/Lib/lib-tk/test/widget_tests.py", line 52, in > assertEqual2 > > self.assertEqual(actual, expected, msg) > > AssertionError: 14.9 != 15.0 > > > > -- > > Ran 689 tests in 1.441s > > > > FAILED (failures=2) > > test test_tk failed -- multiple errors occurred > > 5 tests failed again: > > test_curses test_distutils test_signal test_site test_tk > > > > == Tests result: FAILURE then FAILURE == > > > > 369 tests OK. > > > > 5 tests failed: > > test_curses test_distutils test_signal test_site test_tk > > > > 23 tests skipped: > > test_aepack test_al test_applesingle test_bsddb185 test_cd test_cl > > test_dl test_gdb test_gl test_imageop test_imgfile test_kqueue > > test_macos test_macostools test_msilib test_pep277 > > test_scriptpackages test_startfile test_sunaudiodev > > test_unicode_file test_winreg test_winsound test_zipfile64 > > 1 skip unexpected on linux2: > > test_gdb > > > > 5 re-run tests: > > test_curses test_distutils test_signal test_site test_tk > > > > Total duration: 10 min 27 sec > > Tests result: FAILURE then FAILURE > > make[1]: *** [Makefile:901: test] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/python2.7_2.7.18-9_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 2.7.18-13.2+rm Dear submitter, as the package python2.7 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/1027108 The version of this package that was in Debian prior to this removal can still be found using https://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
Bug#938198: marked as done (python-stdlib-extensions: Python2 removal in sid)
Your message dated Tue, 27 Dec 2022 23:23:11 + with message-id and subject line Bug#1027106: Removed package(s) from unstable has caused the Debian Bug report #938198, regarding python-stdlib-extensions: Python2 removal in sid 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.) -- 938198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-stdlib-extensions Version: 2.7.16-2 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:python-stdlib-extensions 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.7.18-1+rm Dear submitter, as the package python-stdlib-extensions 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/1027106 The version of this package that was in Debian prior to this removal can still be found using https://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#937695: marked as done (python-defaults: Python2 removal in sid)
Your message dated Tue, 27 Dec 2022 23:24:11 + with message-id and subject line Bug#1027107: Removed package(s) from unstable has caused the Debian Bug report #937695, regarding python-defaults: Python2 removal in sid 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.) -- 937695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-defaults Version: 2.7.16-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:python-defaults 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.7.18-3+rm Dear submitter, as the package python-defaults 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/1027107 The version of this package that was in Debian prior to this removal can still be found using https://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#937569: marked as done (python2.7: Python2 removal in sid)
Your message dated Tue, 27 Dec 2022 23:25:10 + with message-id and subject line Bug#1027108: Removed package(s) from unstable has caused the Debian Bug report #937569, regarding python2.7: Python2 removal in sid 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.) -- 937569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python2.7 Version: 2.7.16-3 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:python2.7 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.7.18-13.2+rm Dear submitter, as the package python2.7 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/1027108 The version of this package that was in Debian prior to this removal can still be found using https://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#1027119: yara: FTBFS: FAIL: test-magic
Source: yara
Version: 4.2.3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=yara&arch=amd64&ver=4.2.3-2&stamp=1672148217&raw=0
FAIL: test-magic
failed to compile rule << import "magic" rule test { condition:
magic.type() contains "PE32+ executable" and ( magic.mime_type() ==
"application/x-dosexec" or magic.mime_type() ==
"application/vnd.microsoft.portable-executable" } >>: line 1: syntax error
FAIL test-magic (exit status: 1)
Cheers
--
Sebastian Ramacher
Bug#1027117: iem-plugin-suite: FTBFS: error: ‘class juce::AudioProcessorPlayer’ has no member named ‘audioDeviceIOCallback’; did you mean ‘AudioIODeviceCallback’?
Source: iem-plugin-suite Version: 1.13.0-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=iem-plugin-suite&arch=amd64&ver=1.13.0-3%2Bb1&stamp=1672120155&raw=0 [ 8%] Building CXX object AllRADecoder/CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o cd /<>/obj-x86_64-linux-gnu/AllRADecoder && /usr/bin/c++ -DDONT_SET_USING_JUCE_NAMESPACE=1 -DJUCE_DISPLAY_SPLASH_SCREEN=0 -DJUCE_GLOBAL_MODULE_SETTINGS_INCLUDED=1 -DJUCE_MODAL_LOOPS_PERMITTED=1 -DJUCE_MODULE_AVAILABLE_juce_audio_basics=1 -DJUCE_MODULE_AVAILABLE_juce_audio_devices=1 -DJUCE_MODULE_AVAILABLE_juce_audio_formats=1 -DJUCE_MODULE_AVAILABLE_juce_audio_plugin_client=1 -DJUCE_MODULE_AVAILABLE_juce_audio_processors=1 -DJUCE_MODULE_AVAILABLE_juce_audio_utils=1 -DJUCE_MODULE_AVAILABLE_juce_core=1 -DJUCE_MODULE_AVAILABLE_juce_data_structures=1 -DJUCE_MODULE_AVAILABLE_juce_dsp=1 -DJUCE_MODULE_AVAILABLE_juce_events=1 -DJUCE_MODULE_AVAILABLE_juce_graphics=1 -DJUCE_MODULE_AVAILABLE_juce_gui_basics=1 -DJUCE_MODULE_AVAILABLE_juce_gui_extra=1 -DJUCE_MODULE_AVAILABLE_juce_opengl=1 -DJUCE_MODULE_AVAILABLE_juce_osc=1 -DJUCE_SHARED_CODE=1 -DJUCE_STANDALONE_APPLICATION=JucePlugin_Build_Standalone -DJUCE_TARGET_HAS_BINARY_DATA=1 -DJUCE_USE_CURL=0 -DJUCE_USE_CUSTOM_PLUGIN_STANDALONE_APP=1 -DJUCE_USE_FLAC=0 -DJUCE_USE_LAME_AUDIO_FORMAT=0 -DJUCE_USE_MP3AUDIOFORMAT=0 -DJUCE_USE_OGGVORBIS=0 -DJUCE_USE_WINDOWS_MEDIA_FORMAT=0 -DJUCE_VST3_CAN_REPLACE_VST2=0 -DJUCE_WEB_BROWSER=0 -DJucePlugin_AAXCategory=0 -DJucePlugin_AAXDisableBypass=0 -DJucePlugin_AAXDisableMultiMono=0 -DJucePlugin_AAXIdentifier=com.IEM.AllRADecoder -DJucePlugin_AAXManufacturerCode=JucePlugin_ManufacturerCode -DJucePlugin_AAXProductId=JucePlugin_PluginCode -DJucePlugin_ARACompatibleArchiveIDs=\"\" -DJucePlugin_ARAContentTypes=0 -DJucePlugin_ARADocumentArchiveID=\"com.IEM.AllRADecoder.aradocumentarchive.1\" -DJucePlugin_ARAFactoryID=\"com.IEM.AllRADecoder.arafactory.0.9.2\" -DJucePlugin_ARATransformationFlags=0 -DJucePlugin_AUExportPrefix=AllRADecoderAU -DJucePlugin_AUExportPrefixQuoted=\"AllRADecoderAU\" -DJucePlugin_AUMainType="'aufx'" -DJucePlugin_AUManufacturerCode=JucePlugin_ManufacturerCode -DJucePlugin_AUSubType=JucePlugin_PluginCode -DJucePlugin_Build_AAX=0 -DJucePlugin_Build_AU=0 -DJucePlugin_Build_AUv3=0 -DJucePlugin_Build_LV2=0 -DJucePlugin_Build_Standalone=1 -DJucePlugin_Build_Unity=0 -DJucePlugin_Build_VST3=0 -DJucePlugin_Build_VST=1 -DJucePlugin_CFBundleIdentifier=com.IEM.AllRADecoder -DJucePlugin_Desc=\"AllRADecoder\" -DJucePlugin_EditorRequiresKeyboardFocus=0 -DJucePlugin_Enable_ARA=0 -DJucePlugin_IsMidiEffect=0 -DJucePlugin_IsSynth=0 -DJucePlugin_Manufacturer=\"IEM\" -DJucePlugin_ManufacturerCode=0x49454d41 -DJucePlugin_ManufacturerEmail=\"\" -DJucePlugin_ManufacturerWebsite=\"\" -DJucePlugin_Name=\"AllRADecoder\" -DJucePlugin_PluginCode=0x416c5261 -DJucePlugin_ProducesMidiOutput=0 -DJucePlugin_VSTCategory=kPlugCategEffect -DJucePlugin_VSTNumMidiInputs=16 -DJucePlugin_VSTNumMidiOutputs=16 -DJucePlugin_VSTUniqueID=JucePlugin_PluginCode -DJucePlugin_Version=0.9.2 -DJucePlugin_VersionCode=0x902 -DJucePlugin_VersionString=\"0.9.2\" -DJucePlugin_Vst3Category=\"Fx\" -DJucePlugin_WantsMidiInput=0 -DLINUX=1 -DNDEBUG=1 -D_NDEBUG=1 -I/<>/resources -I/<>/obj-x86_64-linux-gnu/AllRADecoder/AllRADecoder_artefacts/JuceLibraryCode -I/<>/AllRADecoder/Source -I/usr/include/libpng16 -I/<>/obj-x86_64-linux-gnu/juce_binarydata_LAF_fonts/JuceLibraryCode -I/usr/share/juce/modules -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/lv2 -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/serd -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/sord -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/sord/src -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/sratom -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/lilv -I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/lilv/src -I/usr/include/freetype2 -isystem /usr/share/juce/modules/juce_audio_processors/format_types/VST3_SDK -g -O2 -ffile- prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DJUCE_JACK=1 -DJUCE_MODAL_LOOPS_PERMITTED=1 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT AllRADecoder/CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o -MF CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o.d -o CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o -c /usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp In file included from
Bug#1027118: zabbix: FTBFS: error: invalid use of void expression
Source: zabbix Version: 1:6.0.10+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=zabbix&arch=amd64&ver=1%3A6.0.10%2Bdfsg-1%2Bb1&stamp=1672133685&raw=0 simple.c: In function ‘check_https’: simple.c:180:65: error: invalid use of void expression 180 | if (CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_USERAGENT, "Zabbix " ZABBIX_VERSION)) || | ^ simple.c:181:69: error: invalid use of void expression 181 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_URL, https_host)) || | ^ simple.c:182:69: error: invalid use of void expression 182 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_PORT, (long)port)) || | ^ simple.c:183:69: error: invalid use of void expression 183 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_NOBODY, 1L)) || | ^ simple.c:184:69: error: invalid use of void expression 184 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_SSL_VERIFYPEER, 0L)) || | ^ simple.c:185:69: error: invalid use of void expression 185 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_SSL_VERIFYHOST, 0L)) || | ^ simple.c:186:69: error: invalid use of void expression 186 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_TIMEOUT, (long)timeout)) || | ^ simple.c:187:69: error: invalid use of void expression 187 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = ZBX_CURLOPT_ACCEPT_ENCODING, ""))) | ^ simple.c:196:73: error: invalid use of void expression 196 | if (CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = CURLOPT_INTERFACE, CONFIG_SOURCE_IP))) | ^ make[6]: *** [Makefile:500: libsimplesysinfo_a-simple.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1027116: golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no fi
Source: golang-github-containers-buildah Version: 1.28.0+ds1-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=golang-github-containers-buildah&arch=amd64&ver=1.28.0%2Bds1-3%2Bb1&stamp=1672115946&raw=0 # github.com/containers/storage/drivers/btrfs src/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) github.com/containers/storage/drivers/copy github.com/containers/storage/drivers/devmapper github.com/containers/common/pkg/supplemented database/sql/driver github.com/containers/storage/pkg/lockfile github.com/containers/storage/drivers/vfs github.com/containers/storage/pkg/stringid github.com/google/uuid github.com/containers/storage/pkg/stringutils github.com/containers/storage/pkg/tarlog github.com/tchap/go-patricia/patricia github.com/mistifyio/go-zfs github.com/google/go-intervals/intervalset github.com/vbatts/tar-split/tar/asm github.com/containers/storage/pkg/truncindex github.com/containerd/stargz-snapshotter/estargz/errorutil golang.org/x/sync/errgroup github.com/cyphar/filepath-securejoin github.com/containers/image/directory/explicitfilepath github.com/containerd/stargz-snapshotter/estargz github.com/containers/storage/drivers/zfs github.com/containers/image/directory github.com/containers/image/docker/policyconfiguration github.com/containers/image/internal/streamdigest github.com/containers/image/internal/uploadreader github.com/containers/image/pkg/sysregistriesv2 github.com/docker/docker-credential-helpers/credentials golang.org/x/sys/execabs golang.org/x/net/internal/socks github.com/docker/docker-credential-helpers/client github.com/docker/go-connections/tlsconfig github.com/containers/image/pkg/docker/config golang.org/x/net/proxy github.com/docker/distribution/registry/api/errcode github.com/docker/go-connections/sockets github.com/docker/distribution/digestset github.com/gorilla/mux github.com/docker/distribution/reference github.com/containers/image/pkg/tlsclientconfig github.com/docker/distribution/registry/client/auth/challenge gopkg.in/yaml.v2 github.com/containers/image/docker/internal/tarfile github.com/docker/docker/api/types/blkiodev github.com/docker/distribution/registry/api/v2 github.com/docker/docker/api/types/mount github.com/docker/docker/api/types/strslice github.com/docker/go-connections/nat github.com/docker/docker/api/types/container github.com/docker/docker/api/types/filters github.com/containers/image/docker/archive github.com/docker/docker/api/types/registry github.com/gogo/protobuf/proto github.com/docker/docker/api/types/network github.com/docker/docker/api/types/time github.com/docker/docker/errdefs net/http/httputil github.com/containers/image/oci/internal github.com/containers/image/oci/layout github.com/sylabs/sif/pkg/sif github.com/containers/image/oci/archive github.com/ghodss/yaml github.com/containers/image/docker github.com/containers/image/tarball github.com/containers/image/sif github.com/opencontainers/runc/libcontainer/utils github.com/opencontainers/runc/libcontainer/apparmor text/template/parse github.com/containers/common/pkg/apparmor/internal/supported github.com/containers/common/pkg/capabilities github.com/containers/common/pkg/cgroupv2 github.com/containers/common/pkg/util github.com/containers/common/pkg/download github.com/containers/common/pkg/timetype github.com/containers/common/pkg/retry github.com/containers/common/pkg/filters github.com/containers/common/pkg/signal github.com/chzyer/readline text/template github.com/lunixbochs/vtclean github.com/juju/ansiterm/tabwriter github.com/mattn/go-isatty github.com/mattn/go-colorable github.com/juju/ansiterm github.com/manifoldco/promptui/list github.com/containers/common/pkg/apparmor github.com/manifoldco/promptui/screenbuf github.com/disiqueira/gotree github.com/docker/docker/api/types/swarm/runtime database/sql github.com/containers/common/pkg/config github.com/manifoldco/promptui github.com/docker/docker/api/types/swarm github.com/docker/docker/api/types github.com/containers/image/pkg/shortnames github.com/docker/docker/api/types/volume github.com/docker/docker/client github.com/seccomp/libseccomp-golang github.com/containers/buildah/docker github.com/containers/ocicrypt/helpers github.com/jinzhu/copier github.com/containers/common/pkg/parse github.com/containers/image/pkg/blobcache github.com/containers/buildah/pkg/chrootuser github.com/containers/buildah/pkg/blobcache github.com/containers/buildah/pkg/overlay golang.org/x/crypto/chacha20 golang.org/x/crypto/curve25519/internal/field golang.org/x/crypto/internal/poly1305 golang.org/x/crypto/blowfish golang.org/x/crypto/curve25519 github.com/containerd/containerd/pkg/userns golang.org/x/crypto/ssh/internal/bcrypt_pbkdf github.com/containers/image/docker/daemon github.com/contain
Bug#966725: marked as done (childsplay: Unversioned Python removal in sid/bullseye)
Your message dated Tue, 27 Dec 2022 23:20:01 + with message-id and subject line Bug#1027113: Removed package(s) from unstable has caused the Debian Bug report #936298, regarding childsplay: 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.) -- 936298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:childsplay Version: 3.3-2 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: 3.3-2+rm Dear submitter, as the package childsplay 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/1027113 The version of this package that was in Debian prior to this removal can still be found using https://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#936298: marked as done (childsplay: Python2 removal in sid/bullseye)
Your message dated Tue, 27 Dec 2022 23:20:01 + with message-id and subject line Bug#1027113: Removed package(s) from unstable has caused the Debian Bug report #936298, regarding childsplay: 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.) -- 936298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:childsplay Version: 3.3-2 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:childsplay 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: 3.3-2+rm Dear submitter, as the package childsplay 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/1027113 The version of this package that was in Debian prior to this removal can still be found using https://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#912485: marked as done (childsplay: Please migrate to python3-pygame)
Your message dated Tue, 27 Dec 2022 23:20:01 + with message-id and subject line Bug#1027113: Removed package(s) from unstable has caused the Debian Bug report #912485, regarding childsplay: Please migrate to python3-pygame 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.) -- 912485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: childsplay Severity: wishlist User: python-modules-t...@lists.alioth.debian.org Usertags: python3-migration Dear maintainer, thanks for maintaining a pygame-based game in Debian! As you might have heard, Python 2 will be end of life in the not so far future. Thus, I would like to start to get the reverse dependencies of the Python 2 version of pygame down, so this can be done with some time and not in a hurried effort that probably makes us loose games from Debian. If you already know that your game will work with Python 3, please build against and depend on python3-pygame, which has long been available in sid and will migrate to buster shortly. If you do not yet know whether this will work, your chances that it will just work are still quite good, so please just give it a shot. If you find your package does not work with Python 3 yet, you can⦠a) â¦check what to do with upstream b) â¦try to patch it (and forward your patch upstream) c) â¦tag this bug report help - the next pygame-fluent kangaroo is reserved for you! Feel free to ask any questions if you are unsure what to do. Cheers, Nik --- End Message --- --- Begin Message --- Version: 3.3-2+rm Dear submitter, as the package childsplay 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/1027113 The version of this package that was in Debian prior to this removal can still be found using https://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#1027115: gobgp: FTBFS: unknown error
Source: gobgp Version: 2.34.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=gobgp&arch=amd64&ver=2.34.0-1%2Bb4&stamp=1672114096&raw=0 /<>/obj-x86_64-linux-gnu/src/google.golang.org/protobuf/types/known/timestamppb (from $GOPATH) dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 github.com/osrg/gobgp/api github.com/osrg/gobgp/cmd/gobgp github.com/osrg/gobgp/cmd/gobgpd github.com/osrg/gobgp/internal/pkg/apiutil github.com/osrg/gobgp/internal/pkg/config github.com/osrg/gobgp/internal/pkg/table github.com/osrg/gobgp/internal/pkg/version github.com/osrg/gobgp/internal/pkg/zebra github.com/osrg/gobgp/pkg/config github.com/osrg/gobgp/pkg/packet/bgp github.com/osrg/gobgp/pkg/packet/bmp github.com/osrg/gobgp/pkg/packet/mrt github.com/osrg/gobgp/pkg/packet/rtr github.com/osrg/gobgp/pkg/server returned exit code 1 make: *** [debian/rules:8: binary-arch] Error 25 Cheers -- Sebastian Ramacher
Bug#1026506: marked as done (ormar: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Tue, 27 Dec 2022 23:17:19 +
with message-id
and subject line Bug#1026506: fixed in ormar 0.12.0-2
has caused the Debian Bug report #1026506,
regarding ormar: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ormar
Version: 0.12.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build"
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11_ormar
> * Building wheel...
> Successfully built ormar-0.12.0-py3-none-any.whl
> I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.11 with
> "installer" module
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build"
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.10_ormar
> * Building wheel...
> Successfully built ormar-0.12.0-py3-none-any.whl
> I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.10 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_ormar/build;
> python3.11 -m pytest --asyncio-mode=auto
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>/.pybuild/cpython3_3.11_ormar/build
> plugins: anyio-3.6.2, tornasync-0.6.0.post2, asyncio-0.20.3
> asyncio: mode=Mode.AUTO
> collected 411 items / 19 errors
>
> ERRORS
>
> _ ERROR collecting
> tests/test_exclude_include_dict/test_excluding_fields_in_fastapi.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11_ormar/build/tests/test_exclude_include_dict/test_excluding_fields_in_fastapi.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_exclude_include_dict/test_excluding_fields_in_fastapi.py:10: in
>
> from starlette.testclient import TestClient
> /usr/lib/python3/dist-packages/starlette/testclient.py:16: in
> import httpx
> E ModuleNotFoundError: No module named 'httpx'
> __ ERROR collecting tests/test_fastapi/test_binary_fields.py
> ___
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11_ormar/build/tests/test_fastapi/test_binary_fields.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_fastapi/test_binary_fields.py:10: in
> from starlette.testclient import TestClient
> /usr/lib/python3/dist-packages/starlette/testclient.py:16: in
> import httpx
> E ModuleNotFoundError: No module named 'httpx'
> __ ERROR collecting tests/test_fastapi/test_choices_schema.py
> __
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11_ormar/build/tests/test_fastapi/test_choices_schema.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_fastapi/test_choices_schema.py:11: in
> from starlette.testclient import TestClient
> /usr/lib/python3/dist-packages/starlette/testclient.py:16: in
> import httpx
> E ModuleNotFoundError: No module named 'httpx'
> _ ERROR collecting
> tests/test_fastapi/test_docs_with_multiple_relations_to_one.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11_ormar/build/tests/tes
Bug#1026258: marked as done (FTBFS: missing build dependency and failing tests)
Your message dated Tue, 27 Dec 2022 23:17:19 +
with message-id
and subject line Bug#1026258: fixed in ormar 0.12.0-2
has caused the Debian Bug report #1026258,
regarding FTBFS: missing build dependency and failing tests
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.)
--
1026258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ormar
Version: 0.12.0-1
Severity: serious
Tag: ftbfs
Dear Maintainer,
ormar currently fails to build from source for two reasons. The first is
several error message like these when running the test suite:
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_fastapi/test_skip_reverse_models.py:8: in
from starlette.testclient import TestClient
/usr/lib/python3/dist-packages/starlette/testclient.py:16: in
import httpx
E ModuleNotFoundError: No module named 'httpx'
_ ERROR collecting tests/test_fastapi/test_wekref_exclusion.py
_
(Taken from the build log when the package got synced to Ubuntu, but
I've also reproduced this on Sid
https://launchpadlibrarian.net/638906557/buildlog_ubuntu-lunar-amd64.ormar_0.12.0-1_BUILDING.txt.gz)
These errors are the easy part, it simply needs
python3-httpx
added as a build dependency. With this in place, the build result
changes from 19 errors to 2 failing tests. I don't know why they are
failing though, whether it is due to api changes in the test client
used, or the functionality of the package.
=== FAILURES
===
__ test_all_endpoints
__
def test_all_endpoints():
client = TestClient(app)
with client as client:
item = {
"name": "test",
"categories": [{"name": "test cat"}, {"name": "test
cat2"}],
}
response = client.post("/items/", json=item)
item_check = Item(**response.json())
assert item_check.id is not None
assert item_check.categories[0].id is not None
no_pk_item = client.get(f"/items/{item_check.id}",
json=item).json()
E TypeError: TestClient.get() got an unexpected keyword
argument 'json'
tests/test_fastapi/test_excluding_fields.py:118: TypeError
__ test_all_endpoints
__
def test_all_endpoints():
client = TestClient(app)
with client as client:
response = client.post("/categories/", json={"name": "test
cat"})
category = response.json()
response = client.post(
"/items/", json={"name": "test", "id": 1, "category":
category}
)
item = Item(**response.json())
assert item.pk is not None
response = client.get("/items/")
items = [Item(**item) for item in response.json()]
assert items[0] == item
item.name = "New name"
response = client.put(f"/items/{item.pk}", json=item.dict())
assert response.json() == item.dict()
response = client.get("/items/")
items = [Item(**item) for item in response.json()]
assert items[0].name == "New name"
response = client.get("/items/raw/")
items = [Item(**item) for item in response.json()]
assert items[0].name == "New name"
assert items[0].category.name is None
response = client.get(f"/items/{item.pk}")
new_item = Item(**response.json())
assert new_item == item
response = client.delete(f"/items/{item.pk}")
assert response.json().get("deleted_rows", "__UNDEFINED__")
!= "__UNDEFINED__"
response = client.get("/items/")
items = response.json()
assert len(items) == 0
client.post("/items/", json={"name": "test_2", "id": 2,
"category": category})
response = client.get("/items/")
items = response.json()
assert len(items) == 1
item = Item(**items[0])
response = client.delete(f"/items/{item.pk}",
json=item.dict())
E TypeError: TestClient.delete() got an unexpected keyword
argument 'json'
tests/test_fastapi/test_more_reallife_fastapi.py:150: TypeError
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT poli
Bug#1026020: marked as done (python3-starlette: starlette.testclient requires module httpx)
Your message dated Tue, 27 Dec 2022 23:17:19 + with message-id and subject line Bug#1026020: fixed in ormar 0.12.0-2 has caused the Debian Bug report #1026020, regarding python3-starlette: starlette.testclient requires module httpx 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.) -- 1026020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-starlette Version: 0.23.1-1 Severity: serious Control: affects -1 src:ormar -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package does not depend on python3-httpx, which causes the build (and the autopkgtest) of src:ormar to fail. Presumbably, this dependency has been satisfied indirectly before, but I did not look into it further. Relevant excerpt from https://ci.debian.net/data/autopkgtest/testing/amd64/o/ormar/29316569/log.gz follows: = test session starts == platform linux -- Python 3.10.9, pytest-7.1.2, pluggy-1.0.0+repack -- /usr/bin/python3.10 cachedir: .pytest_cache rootdir: /tmp/autopkgtest-lxc.jzly90qs/downtmp/autopkgtest_tmp plugins: anyio-3.6.2, tornasync-0.6.0.post2, asyncio-0.19.0 asyncio: mode=auto collecting ... collected 40 items / 1 error ERRORS _ ERROR collecting tests/test_exclude_include_dict/test_excluding_fields_in_fastapi.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.jzly90qs/downtmp/autopkgtest_tmp/tests/test_exclude_include_dict/test_excluding_fields_in_fastapi.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.10/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_exclude_include_dict/test_excluding_fields_in_fastapi.py:10: in from starlette.testclient import TestClient /usr/lib/python3/dist-packages/starlette/testclient.py:16: in import httpx E ModuleNotFoundError: No module named 'httpx' Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmOYXCoACgkQ+C8H+466 LVlargwA4BqYCtrjO5Gi8rC92lC6cnfTj/62WqBR4LWlfSbAOjbb7ESswRLKewG/ EMgKZ+K6YGfApO/Yks6UgjFtPOAYjcsC4usTP+um3LIvwdlFM1838ABg+Uqcuwzy 8yq+ut8CMYTBQjjaSCXFkH/vX7/TTYbsv4ADLhojpa9Ie6a/YQxDBVrmh7UIjnRG gDYPwY681KDihuKa9mWQEUtH7UJkPmy7jkTKryHaRnbFQwcEN655PNoFMNPhog9M /UHZ8tAUxd4eLnrccPSo02cAtDF8OgyBBAwI36n54Vq6k63sDOhF3psbqE8zzW3t fTw+yQP1VVoXJYwxrNM+MlW266epM96Wv+OMugnZPgtgVz5FjY4W4CNHCqKvoZkF pRcVTorRSKHuj/N/ET1ARtC4UN08tAt1DoADdZozH2HBjSaBLDLKMLwJGBZLAPUd nm2/okHr1s23Ke/TUU787l1uA8OeCo3ufb/NAqnoVqpsNJK5c4ZQ0HoL6MY5NXiK wR1o3vki =vrqf -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: ormar Source-Version: 0.12.0-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of ormar, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated ormar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 27 Dec 2022 17:43:20 -0500 Source: ormar Architecture: source Version: 0.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Sandro Tosi Closes: 1026020 1026258 1026506 Changes: ormar (0.12.0-2) unstable; urgency=medium . * debian/control - add httpx to b-d, needed by tests (via starlette.testclient); Closes: #1026020, #1026506 * debian/patches/PR971.patch - make tests compatible with new starlette/httpx; Closes: #1026258 Checksums-Sha1: ee7f3cb7de1903e4afee0a1807042a45a17991df 2685 ormar_0.12.0-2.dsc 4f4654f517a035692d5e5f31938bc85fea84003d 3648 ormar_0.12.0-2.debian.tar.xz f492748c9012816943c5423578826ef2ec1ae495 8747 ormar_0.12.0-2_source.buildinfo Checksums-Sha256: ff42715a3da0c1010145c76e5d1e8c38e465b01b4035109af4dbe1116396eefe 2685 ormar_0.12.0-2.dsc 08a8dfab93cbff551e8d7c749e83c82527aea4f2e649a4b1e497071143d749a9 3648 ormar_0.12.0-2.debian.tar.xz 23f3df44
Bug#1027114: docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced)
Source: docker.io Version: 20.10.21+dfsg1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=amd64&ver=20.10.21%2Bdfsg1-1%2Bb1&stamp=1672110377&raw=0 ---> Making bundle: dynbinary (in bundles/dynbinary) Building: bundles/dynbinary-daemon/dockerd-20.10.21+dfsg1 GOOS="" GOARCH="" GOARM="" # github.com/docker/docker/daemon/graphdriver/btrfs daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) make[1]: *** [debian/rules:114: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher
Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'
Source: bazel-bootstrap Version: 4.2.3+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=bazel-bootstrap&arch=amd64&ver=4.2.3%2Bds-1%2Bb1&stamp=1671977092&raw=0 ␛[1A␛[K␛[31m␛[1mERROR: ␛[0m/<>/src/main/cpp/BUILD:91:10: Linking src/main/cpp/client failed: (Exit 1): gcc failed: error executing command (cd /tmp/bazel_hloBSNSM/out/execroot/io_bazel && \ exec env - \ CCACHE_DISABLE=1 \ CCACHE_TEMPDIR=/<>/debian/ccachetmp \ LC_ALL=C \ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \ PWD=/proc/self/cwd \ /usr/bin/gcc @bazel-out/k8-dbg/bin/src/main/cpp/client-2.params) Execution platform: //:default_host_platform ␛[32m[111 / 127]␛[0m 3 actions running //src/main/java/com/google/devtools/build/lib/bazel:BazelServer; 5s local JavacBootstrap .../devtools/build/singlejar/libbootstrap.jar; 2s local JavacBootstrap .../devtools/build/buildjar/libstarlark-deps.jar; 2s local ␛[1A␛[K ␛[1A␛[K ␛[1A␛[K ␛[1A␛[K/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 'absl::debian3::Mutex::Lock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' /usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 'absl::debian3::Mutex::Lock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' collect2: error: ld returned 1 exit status ␛[32m[111 / 127]␛[0m 3 actions running Cheers -- Sebastian Ramacher
Processed: Re: Bug#1019665: ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:
Processing control commands: > affects -1 src:jekyll Bug #1019665 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError: Added indication that 1019665 affects src:jekyll -- 1019665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019665: ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:
Control: affects -1 src:jekyll On Mon, 26 Dec 2022 17:54:13 +0100 Lucas Nussbaum wrote: > On 17/12/22 at 14:51 +0100, Diederik de Haas wrote: > > There is an upstream PR: https://github.com/dtao/safe_yaml/pull/101 > > which tried to address this, but someone who tried it still got errors. > > > > Last upstream commit was from 2019-02-22 and there are several PRs open > > and it looks like the maintainer hasn't responded to any of them for > 5 > > YEARS > > Since ruby-crack no longer depends on ruby-safe-yaml, ruby-safe-yaml > should probably just be removed from testing (and Debian)... And with that jekyll: https://tracker.debian.org/pkg/jekyll https://bugs.debian.org/1026427 is a bug about that. signature.asc Description: This is a digitally signed message part.
Bug#1027111: wine: FTBFS: error: writing 56 bytes into a region of size 8
Source: wine Version: 7.0~repack-11 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=wine&arch=amd64&ver=7.0%7Erepack-11&stamp=1671780374&raw=0 x86_64-w64-mingw32-gcc -c -o dlls/user32/painting.cross.o dlls/user32/painting.c -Idlls/user32 -Iinclude -Iinclude/msvcrt -I./libs/png -D__WINESRC__ -D_USER32_ -D_WINABLE_ -D_UCRT -D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -Wabsolute-value -Wno-format -Wformat-overflow -Wnonnull -mcx16 -gdwarf-4 -Werror -Wdate-time -g -O2 -ffile-prefix-map=/<>=. -Wno-array-bounds -Wno-format dlls/user32/message.c: In function ‘unpack_message’: dlls/user32/message.c:1428:9: error: writing 56 bytes into a region of size 8 [-Werror=stringop-overflow=] 1428 | memcpy( &ps->mcs, &mcs, sizeof(mcs) ); | ^ dlls/user32/message.c:197:15: note: destination object ‘szClass’ of size 8 197 | ULONGLONG szClass; | ^~~ dlls/user32/message.c:1216:9: error: writing 56 bytes into a region of size 4 [-Werror=stringop-overflow=] 1216 | memcpy( &ps->cis, &cis, sizeof(cis) ); | ^ dlls/user32/message.c:113:19: note: destination object ‘CtlType’ of size 4 113 | UINT CtlType; | ^~~ dlls/user32/message.c:1201:9: error: writing 32 bytes into a region of size 4 [-Werror=stringop-overflow=] 1201 | memcpy( &ps->dls, &dls, sizeof(dls) ); | ^ dlls/user32/message.c:103:19: note: destination object ‘CtlType’ of size 4 103 | UINT CtlType; | ^~~ dlls/user32/message.c:1189:9: error: writing 32 bytes into a region of size 4 [-Werror=stringop-overflow=] 1189 | memcpy( &ps->mis, &mis, sizeof(mis) ); | ^ dlls/user32/message.c:93:19: note: destination object ‘CtlType’ of size 4 93 | UINT CtlType; | ^~~ dlls/user32/message.c:1176:9: error: writing 64 bytes into a region of size 4 [-Werror=stringop-overflow=] 1176 | memcpy( &ps->dis, &dis, sizeof(dis) ); | ^ dlls/user32/message.c:78:19: note: destination object ‘CtlType’ of size 4 78 | UINT CtlType; | ^~~ dlls/user32/message.c:1142:9: error: writing 80 bytes into a region of size 8 [-Werror=stringop-overflow=] 1142 | memcpy( &ps->cs, &cs, sizeof(cs) ); | ^~ dlls/user32/message.c:59:19: note: destination object ‘lpCreateParams’ of size 8 59 | ULONGLONG lpCreateParams; | ^~ Cheers -- Sebastian Ramacher
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reopen 1025650 =
Bug #1025650 {Done: Samuel Henrique } [ftp.debian.org]
ftp.debian.org: Nmap Public Source License Version 0.94 - Is it DFSG-compliant?
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions nmap/7.92+dfsg2-2~exp1.
> --
Stopping processing here.
Please contact me if you need assistance.
--
1025650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1023830: widelands: FTBFS on s390x
Control: severity -1 important On Mon, 26 Dec 2022 17:07:55 +0100 Tobias Frost wrote: > Control: block -1 by 1027028 > > FWIIW, I've requested removal of widelands on s390x. Once this is done, this > bug can be downgraded in severity. > This has happened now. Downgrading severity to "important" to let widelands migrate. -- tobi
Processed: Re: widelands: FTBFS on s390x
Processing control commands: > severity -1 important Bug #1023830 [src:widelands] widelands: FTBFS on s390x Severity set to 'important' from 'serious' -- 1023830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003744: marked as done (php-horde-crypt: (autopkgtest) needs update for php8.1: errorHandler(), 4 passed and exactly 5 expected)
Your message dated Tue, 27 Dec 2022 22:08:26 + with message-id and subject line Bug#1003744: fixed in php-horde-crypt 2.7.12-7 has caused the Debian Bug report #1003744, regarding php-horde-crypt: (autopkgtest) needs update for php8.1: errorHandler(), 4 passed and exactly 5 expected 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.) -- 1003744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-horde-crypt Version: 2.7.12-6 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:php-defaults Control: block 976811 by -1 Dear maintainer(s), [In contrast to earlier bugs filed, this issue seems to really break functionality.] We are in the transition of replacing php7.4 with php8.1 [0]. With a recent upload of php-defaults the autopkgtest of php-horde-crypt fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing92 php-horde-cryptfrom testing2.7.12-6 versioned deps from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of php-defaults to testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 7.4 and may help to identify what needs to be updated. php-commom added a whole set of versioned Breaks to make sure the right packages from current unstable are pulled in during testing. If the issue is caused by a missing breaks, please reasign this bug to php-common. 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/976811 [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-crypt/18284133/log.gz PHP Deprecated: Horde_Stream implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /usr/share/php/Horde/Stream.php on line 27 PHP Deprecated: Horde_Stream_Temp implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /usr/share/php/Horde/Stream/Temp.php on line 23 PHPUnit 9.5.11 by Sebastian Bergmann and contributors. Runtime: PHP 8.1.1 Configuration: /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/phpunit.xml Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/Pgp/BinaryTest.php Class name was 'Horde_Crypt_Pgp_BinaryTest', expected 'BinaryTest' Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/PgpKeyserverTest.php Class name was 'Horde_Crypt_PgpKeyserverTest', expected 'PgpKeyserverTest' Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/PgpParseTest.php Class name was 'Horde_Crypt_PgpParseTest', expected 'PgpParseTest' Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/SmimeTest.php Class name was 'Horde_Crypt_SmimeTest', expected 'SmimeTest' PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php on line 247 PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php on line 248 ..PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php on line 247 PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest
Bug#938644: marked as done (telepathy-ring: Python2 removal in sid/bullseye)
Your message dated Tue, 27 Dec 2022 21:47:51 + with message-id and subject line Bug#1027042: Removed package(s) from unstable has caused the Debian Bug report #938644, regarding telepathy-ring: 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.) -- 938644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:telepathy-ring Version: 2.3.24-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-ring 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.3.24-2+rm Dear submitter, as the package telepathy-ring 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/1027042 The version of this package that was in Debian prior to this removal can still be found using https://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#1026579: marked as done (python-testtools: FTBFS: tests failed)
Your message dated Tue, 27 Dec 2022 21:42:34 +
with message-id
and subject line Bug#1026579: fixed in python-testtools 2.5.0-4
has caused the Debian Bug report #1026579,
regarding python-testtools: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-testtools
Version: 2.5.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -ex ; for pyvers in 3.11 3.10; do \
> PYTHONPATH=/<> PYTHON=python$pyvers python$pyvers -m
> testtools.run testtools.tests.test_suite ; \
> done
> + PYTHONPATH=/<> PYTHON=python3.11 python3.11 -m testtools.run
> testtools.tests.test_suite
> :128: RuntimeWarning: 'testtools.run' found in sys.modules
> after import of package 'testtools', but prior to execution of
> 'testtools.run'; this may result in unpredictable behaviour
> Tests running...
> ==
> ERROR: testtools.tests.test_distutilscmd.TestCommandTest.test_test_module
> --
> Empty attachments:
> stdout
>
> Traceback (most recent call last):
> File "/<>/testtools/tests/test_distutilscmd.py", line 61, in
> test_test_module
> dist.run_command('test')
> File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in
> run_command
> self.set_defaults()
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 340, in
> __call__
> self._analyse_package_layout(ignore_ext_modules)
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 373, in
> _analyse_package_layout
> or self._analyse_flat_layout()
>^^^
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 430, in
> _analyse_flat_layout
> return self._analyse_flat_packages() or self._analyse_flat_modules()
>^
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 436, in
> _analyse_flat_packages
> self._ensure_no_accidental_inclusion(top_level, "packages")
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 466, in
> _ensure_no_accidental_inclusion
> raise PackageDiscoveryError(cleandoc(msg))
> setuptools.errors.PackageDiscoveryError: Multiple top-level packages
> discovered in a flat-layout: ['debian', 'testtools'].
>
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
>
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
>
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
>
> To find more information, look for "package discovery" on setuptools docs.
> ==
> ERROR: testtools.tests.test_distutilscmd.TestCommandTest.test_test_suite
> --
> Empty attachments:
> stdout
>
> Traceback (most recent call last):
> File "/<>/testtools/tests/test_distutilscmd.py", line 83, in
> test_test_suite
> dist.run_command('test')
> File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in
> run_command
> self.set_defaults()
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 340, in
> __call__
> self._analyse_package_layout(ignore_ext_modules)
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 373, in
> _analyse_package_layout
> or self._analyse_flat_layout()
>^^^
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 430, in
> _analyse_flat_layout
> return self._analyse_flat_packages() or self._analyse_flat_modules()
>^
> File "/usr/lib/python3/dist-packages/setuptools/discovery.py", line 436, in
> _analyse_flat_packages
> s
Bug#1025753: marked as done (FTBFS: Java compilation error (cannot find symbols))
Your message dated Tue, 27 Dec 2022 21:44:06 + with message-id and subject line Bug#1026917: Removed package(s) from unstable has caused the Debian Bug report #1025753, regarding FTBFS: Java compilation error (cannot find symbols) 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.) -- 1025753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jruby-openssl Version: 0.9.21-4 Severity: serious Tags: ftbfs Dear Maintainer, jruby-openssl currently fails to build with the following error message: [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /build/jruby-openssl-0.9.21/src/main/java/org/jruby/ext/openssl/x509store/Lookup.java:[74,25] cannot find symbol symbol: class ChannelDescriptor location: package org.jruby.util.io [ERROR] /build/jruby-openssl-0.9.21/src/main/java/org/jruby/ext/openssl/x509store/Lookup.java:[75,25] cannot find symbol symbol: class ChannelStream location: package org.jruby.util.io [ERROR] /build/jruby-openssl-0.9.21/src/main/java/org/jruby/ext/openssl/x509store/Lookup.java:[76,25] cannot find symbol symbol: class FileExistsException location: package org.jruby.util.io [INFO] 3 errors Tested in pbuilder on my Sid system. Same error seemed to happen when the package got synced to Ubuntu [1] Btw, looks like the problematic imports are gone in latest upstream [2] so this might be resolved by upgrading to newer release :) [1] https://launchpad.net/ubuntu/+source/jruby-openssl/0.9.21-4/+build/24611214 [2] https://github.com/jruby/jruby-openssl/blob/master/src/main/java/org/jruby/ext/openssl/x509store/Lookup.java -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/3 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 -- mvh / best regards Hans Joachim Desserud http://desserud.org --- End Message --- --- Begin Message --- Version: 0.9.21-4+rm Dear submitter, as the package jruby-openssl 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/1026917 The version of this package that was in Debian prior to this removal can still be found using https://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#1023712: marked as done (why3 breaks frama-c (autopkgtest): missing versioned Breaks?)
Your message dated Tue, 27 Dec 2022 21:35:54 + with message-id and subject line Bug#1023712: fixed in frama-c 20220511-manganese-3 has caused the Debian Bug report #1023712, regarding why3 breaks frama-c (autopkgtest): missing versioned Breaks? 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.) -- 1023712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: why3 Control: found -1 why3/1.5.1-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks Dear maintainer(s), With a recent upload of why3 the autopkgtest of frama-c fails in testing when that autopkgtest is run with the binary packages of why3 from unstable. It passes when run with only packages from testing. In tabular form: passfail why3 from testing1.5.1-1 frama-cfrom testing20220511-manganese-1.3 all others from testingfrom testing I copied some of the output at the bottom of this report. The message seems serious enough (to my eyes) that you'd want to prevent this on partial upgrades and during dist-upgrades. Does why3 (version in unstable) really break the version of frama-c in testing? Then adding a *versioned* Breaks might be a good idea. Maybe the failure isn't as bad as it looks, then please just close this bug report (but be warned, why3 might migrate then, while the fixed frama-c seems stuck). Currently this regression is blocking the migration of why3 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=why3 https://ci.debian.net/data/autopkgtest/testing/amd64/f/frama-c/28047266/log.gz [kernel] User Error: cannot load plug-in 'frama-c-wp': cannot load module Details: implementation mismatch on Why3 [kernel] User Error: Deferred error message was emitted during execution. See above messages for more information. [kernel] Frama-C aborted: invalid user input. autopkgtest [20:18:19]: test eva OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: frama-c Source-Version: 20220511-manganese-3 Done: Ralf Treinen We believe that the bug you reported is fixed in the latest version of frama-c, 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. Ralf Treinen (supplier of updated frama-c package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 27 Dec 2022 21:00:26 +0100 Source: frama-c Architecture: source Version: 20220511-manganese-3 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Ralf Treinen Closes: 1023712 Changes: frama-c (20220511-manganese-3) unstable; urgency=medium . * Create a versioned dependency on libwhy3-ocaml-dev (closes: #1023712). As a consequence, remove dependency on libwhy3-ocaml-dev in the tests. * Standards-Version 4.6.2 (no change) Checksums-Sha1: a85e80371c3d63345d9c4a65d58294c2bf60da92 2407 frama-c_20220511-manganese-3.dsc 475924960094539e4fe94290c7b595eb8322164a 16200 frama-c_20220511-manganese-3.debian.tar.xz 8b5eab2be1cc039adca5ab64e13956aafb244580 16723 frama-c_20220511-manganese-3_source.buildinfo Checksums-Sha256: d57d4a2faceba559cf461a1b146b7774fdf27c9a2802c8db0f637635205a965c 2407 frama-c_20220511-manganese-3.dsc 1811f59a32b2d4fec3e2aff223fb13f4ec8c9a097bd1536cd4be1bb2e956dbe9 16200 frama-c_20220511-manganese-3.debian.tar.xz 465603f5fbe682045246fcc3055923468b6584b2553efbc3c8c107311e9ae96a 16723 frama-c_20220511-manganese-3_source.buildinfo Files: 9cc2dd85f24b9a840d2114981f12aa73 2407 devel optional frama-c_20220511-manganese-3.dsc a32f321c9473966208af467abba35c1c 16200 devel optional frama-c_20220
Bug#1017104: marked as done (during removal fails to remove /var/log/git-daemon)
Your message dated Tue, 27 Dec 2022 22:27:25 +0100 with message-id <1541c783-f4f8-1df9-6eab-a3f2b3d11...@debian.org> and subject line Re: src:git: fails to migrate to testing for too long: piuparts reports issue has caused the Debian Bug report #1017104, regarding during removal fails to remove /var/log/git-daemon 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.) -- 1017104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git Version: 1:2.35.1-1 Severity: serious Control: close -1 1:2.36.1-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:git has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The excuses pages tells us that piuparts is reporting an issue with bin:git-daemon-run during removal: rmdir: failed to remove '/var/log/git-daemon': No such file or directory Unknown option: f deluser USER If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=git OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1:2.39.0-1 On Mon, 13 Jun 2022 21:22:09 +0200 Paul Gevers wrote: The excuses pages tells us that piuparts is reporting an issue with bin:git-daemon-run during removal: rmdir: failed to remove '/var/log/git-daemon': No such file or directory Unknown option: f deluser USER The excuses page is now clean, piuparts is happy. Paul (And now to the right address) OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1027062: marked as done (python3-sqlmodel -- Uninstallable with new sqlalchemy in unstable)
Your message dated Tue, 27 Dec 2022 21:23:59 + with message-id and subject line Bug#1027062: fixed in sqlmodel 0.0.8-2 has caused the Debian Bug report #1027062, regarding python3-sqlmodel -- Uninstallable with new sqlalchemy in unstable 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.) -- 1027062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-sqlmodel Version: 0.0.8-1 Severity: serious X-Debbugs-Cc: mo...@debian.org Hi, The pyproject.toml of sqlmodel enforces a strictly less than dep on sqlalchemy version 1.4.41 however the current version of sqlalchemy in unstable is 1.4.45, and hence sqlmodel is unstallable. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-sqlmodel depends on: ii python33.10.6-1 pn python3-pydantic pn python3-sqlalchemy pn python3-typing-extensions python3-sqlmodel recommends no packages. python3-sqlmodel suggests no packages. --- End Message --- --- Begin Message --- Source: sqlmodel Source-Version: 0.0.8-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of sqlmodel, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated sqlmodel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 27 Dec 2022 15:47:04 -0500 Source: sqlmodel Architecture: source Version: 0.0.8-2 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 1027061 1027062 Changes: sqlmodel (0.0.8-2) unstable; urgency=medium . * debian/control - add httpx to b-d, needed by tests; Closes: #1027061 * debian/patches/PR510.patch - allow to use sqlalchemy 1.4.45, which is currently in unstable; Closes: #1027062 * debian/patches/PR519.patch - ensure tests compatibility with sqlalchemy/1.4.45 Checksums-Sha1: 5e84bb51e0b1bb1ef10e24fdc33012e4c1c3957c 2253 sqlmodel_0.0.8-2.dsc 98b353e4889cdd4ef27cf337da2e1b6c4a32cae4 4832 sqlmodel_0.0.8-2.debian.tar.xz 7072be6f598f04b385a45913c2b791933e49b3b5 8334 sqlmodel_0.0.8-2_source.buildinfo Checksums-Sha256: 287551c5f71237738c0d7db962e9859e63ab506955913cb49713a9c8c2fa1aeb 2253 sqlmodel_0.0.8-2.dsc 63b4b5b40424ded1db1a2853e2ab1564238c1f3717c301369e3b78325a4334b3 4832 sqlmodel_0.0.8-2.debian.tar.xz 4f6e21b2130e08a8fe861552ae25536ae74a9463b3956e058593081f9f6fc648 8334 sqlmodel_0.0.8-2_source.buildinfo Files: 969cf54f10dc8434158c2d7ccbd14722 2253 python optional sqlmodel_0.0.8-2.dsc 573131639ec391cfb46bbc3137147e99 4832 python optional sqlmodel_0.0.8-2.debian.tar.xz d4ab9db6a0f1cbac8f3c0a41e96df95d 8334 python optional sqlmodel_0.0.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmOrWd8ACgkQh588mTgB qU/rHw/+IN1x+L5LBZ3HSrjvhelNO4q2Z0RCQEkjE8ofURS1TYIoSjXLYWn1OONA xvBPvqt/rpABXtLOFHVKv2MkJbqbyqBFCFVHqqu9/sAsqbMV4AFdF8Wb5Kh2os49 NmzpFZ/W24pvUT/vyZz7mKesS9KtKG1EnLxCdHUhfppE7B0d3kjV7vS9X6mV3uP9 K/d9VfCo5Ikpb8VeaOCxvoGYe/506I2smCBpyeKWqdItH2nuKiIN8FEEpoy+sFNt oM/exBPz0P4qX8FpSRo4sfKEW74lcKyJD/IFgaTRKHp/qDF0bDjitQQL+l8DDvXc FCe+vAxjLaSMDf07tdxAmNmFgDsPLLMuU5gjIKiQXYfolLqzUN5GBX5k7A7Xclzk HzDmTz2sdapJ4rLIJQIEretf2uOaMVoDtHSJy/GgTAH33oKi1ooBnJ9bQVi7ndic qOkmuWv2jLlMREs1LNS575jtwnUN5799uMjCYhcgT02DMxT65f33LOKUSQ7tWt4D QA0UQed8VknXgQ+zq/nibjA8JLzuy//zw4mPpVDbRJC2wj6NhWMbqL6xhcNYv70H Pnji86yHUqMJaWPWDcIh1ZzCE1Q4sjDP3Ky+qaoOxYwMTkdwaKlt6SeQhwWMO4jw RHWjeXEFEAcpfSedc8ILny7vjQhPaVRzYwpP7W/OPjoL6G+3jC0= =09A9 -END PGP SIGNATURE End Message ---
Bug#1027061: marked as done (sqlmodel -- FTBFS with python3.11)
Your message dated Tue, 27 Dec 2022 21:23:59 + with message-id and subject line Bug#1027061: fixed in sqlmodel 0.0.8-2 has caused the Debian Bug report #1027061, regarding sqlmodel -- FTBFS with python3.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sqlmodel Version: 0.0.8-1 Severity: serious X-Debbugs-Cc: mo...@debian.org Hi, sqlmodel FTBFS with tonnes of: I: pybuild base:240: PYTHONPATH=/<> python3.11 -m pytest -k 'not test_create_db_and_table' = test session starts == platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack rootdir: /<> plugins: anyio-3.6.2 collected 83 items / 25 errors / 3 deselected / 80 selected ERRORS _ ERROR collecting docs_src/tutorial/fastapi/app_testing/tutorial001/test_main.py _ ImportError while importing test module '/<>/docs_src/tutorial/fastapi/app_testing/tutorial001/test_main.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) docs_src/tutorial/fastapi/app_testing/tutorial001/test_main.py:2: in from fastapi.testclient import TestClient /usr/lib/python3/dist-packages/fastapi/testclient.py:1: in from starlette.testclient import TestClient as TestClient # noqa /usr/lib/python3/dist-packages/starlette/testclient.py:16: in import httpx E ModuleNotFoundError: No module named 'httpx' _ ERROR collecting docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_001.py _ ImportError while importing test module '/<>/docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_001.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_001.py:1: in from fastapi.testclient import TestClient /usr/lib/python3/dist-packages/fastapi/testclient.py:1: in from starlette.testclient import TestClient as TestClient # noqa /usr/lib/python3/dist-packages/starlette/testclient.py:16: in import httpx E ModuleNotFoundError: No module named 'httpx' _ ERROR collecting docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_002.py _ ImportError while importing test module '/<>/docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_002.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_002.py:1: in from fastapi.testclient import TestClient /usr/lib/python3/dist-packages/fastapi/testclient.py:1: in from starlette.testclient import TestClient as TestClient # noqa /usr/lib/python3/dist-packages/starlette/testclient.py:16: in import httpx E ModuleNotFoundError: No module named 'httpx' -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: sqlmodel Source-Version: 0.0.8-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of sqlmodel, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated sqlmodel 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.
Processed: fixed 1026531 2.30.0-3
Processing commands for cont...@bugs.debian.org: > fixed 1026531 2.30.0-3 Bug #1026531 [src:swift] swift: FTBFS: AssertionError: 23 != Marked as fixed in versions swift/2.30.0-3. > End of message, stopping processing here. Please contact me if you need assistance. -- 1026531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1026579 marked as pending in python-testtools
Processing control commands: > tag -1 pending Bug #1026579 [src:python-testtools] python-testtools: FTBFS: tests failed Added tag(s) pending. -- 1026579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026579: marked as pending in python-testtools
Control: tag -1 pending Hello, Bug #1026579 in python-testtools 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/python/python-testtools/-/commit/88636f042a40f47dd9db5f29d36022f8953c30e4 * Add upsteram py3.11 patches (Closes: #1026579): - py3.11-Fix_various_test_failures.patch - py3.11-Upgrade_asserts_with_teyit.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1026579
Processed: affects 1027094
Processing commands for cont...@bugs.debian.org: > affects 1027094 bind9 Bug #1027094 [src:bind-dyndb-ldap] FTBFS against bind9 9.18.10 Added indication that 1027094 affects bind9 > thanks Stopping processing here. Please contact me if you need assistance. -- 1027094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027094: FTBFS against bind9 9.18.10
On 27/12/22 09:43 PM, Santiago Vila wrote: > > bind-dyndb-ldap has a tight dependency on the upstream version of bind9-libs > > (built by src:bind9) and needs to be rebuilt on every new upstream version > > until https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 is fixed. > > Hello. I suppose this is the reason it does not build in stable either. > > Should we use the "found" directive with this bug, > or it is better to file it as a separate bug? I suspect this is a different bug (possibly for the same reason, changed API within a stable release of bind9, but since the breaking code is very fresh I doubt the same thing affects stable). So better file a new one. Bernhard
Processed: Re: Bug#1027094: FTBFS against bind9 9.18.10
Processing control commands: > forwarded -1 https://pagure.io/bind-dyndb-ldap/issue/216 Bug #1027094 [src:bind-dyndb-ldap] FTBFS against bind9 9.18.10 Set Bug forwarded-to-address to 'https://pagure.io/bind-dyndb-ldap/issue/216'. -- 1027094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027094: FTBFS against bind9 9.18.10
Control: forwarded -1 https://pagure.io/bind-dyndb-ldap/issue/216
On 27/12/22 06:16 PM, Bernhard Schmidt wrote:
Hi,
so this is really massively broken :-(
> ../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
>21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
> | ^~~
That one has been introduced in 9.18.9+. There is an open pull request
upstream at https://pagure.io/bind-dyndb-ldap/pull-request/215 , which
(together with bumping LIBDNS_VERSION_MAJOR in
d/p/hardcode-version.diff) fixes the logging errors.
> ../../src/ldap_driver.c: In function ‘allrdatasets’:
> ../../src/ldap_driver.c:474:71: error: passing argument 5 of
> ‘dns_db_allrdatasets’ makes integer from pointer without a cast
> [-Werror=int-conversion]
> 474 | return dns_db_allrdatasets(ldapdb->rbtdb, node, version, now,
> iteratorp);
> |
> ^
> |
> |
> |
> dns_rdatasetiter_t ** {aka struct dns_rdatasetiter **}
Those appear to be new issues in 9.18.10. I have filed a new upstream
bugreport at https://pagure.io/bind-dyndb-ldap/issue/216 . Both
dns_db_allrdatasets and dns_zt_apply gained an additional argument
https://gitlab.isc.org/isc-projects/bind9/-/commit/1de9c052107a6f24e565441f53e4d8b33bb2e30a
https://gitlab.isc.org/isc-projects/bind9/-/commit/6f998bbe518ae629685404bcfddcfd6067176660
and while my attempts to monkeypatch the additional 0 argument into
dns_db_allrdatasets cleared most of the warnings I'm lost with the
remaining errors. Does not really help that I barely know C, my
knowledge ends pretty much here and I have no idea how to go further.
In file included from ../../src/zone_register.h:8,
from ../../src/ldap_convert.c:28:
/usr/include/dns/zt.h:171:28: error: unknown type name ‘isc_rwlocktype_t’; did
you mean ‘isc_rwlock_t’?
171 | dns_zt_apply(dns_zt_t *zt, isc_rwlocktype_t lock, bool stop,
isc_result_t *sub,
|^~~~
|isc_rwlock_t
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -std=gnu99 -O2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wno-uninitialized -fvisibility=hidden
-fno-delete-null-pointer-checks -std=gnu11 -c ../../src/ldap_helper.c -fPIC
-DPIC -o .libs/ldap_la-ldap_helper.o
../../src/ldap_driver.c:950:9: error: initialization of ‘isc_result_t
(*)(dns_db_t *, dns_dbnode_t *, dns_dbversion_t *, unsigned int,
isc_stdtime_t, dns_rdatasetiter_t **)’ {aka ‘enum isc_result (*)(struct dns_db
*, void *, void *, unsigned int, unsigned int, struct dns_rdatasetiter **)’}
from incompatible pointer type ‘isc_result_t (*)(dns_db_t *, dns_dbnode_t *,
dns_dbversion_t *, isc_stdtime_t, dns_rdatasetiter_t **)’ {aka ‘enum
isc_result (*)(struct dns_db *, void *, void *, unsigned int, struct
dns_rdatasetiter **)’} [-Werror=incompatible-pointer-types]
950 | allrdatasets,
| ^~~~
../../src/ldap_driver.c:950:9: note: (near initialization for
‘ldapdb_methods.allrdatasets’)
Bug#1025530: (no subject)
Blocking proper system updates, can't the i386 version be rolled back until all other versions are compilable? -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
Bug#1026715: marked as done (cpplint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Tue, 27 Dec 2022 20:45:42 +
with message-id
and subject line Bug#1026715: fixed in cpplint 1.6.1-2
has caused the Debian Bug report #1026715,
regarding cpplint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpplint
Version: 1.6.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> running config
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> running build
> running build_py
> copying cpplint.py -> /<>/.pybuild/cpython3_3.11_cpplint/build
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying cpplint.py -> /<>/.pybuild/cpython3_3.10_cpplint/build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:307: cp -r /<>/samples
> /<>/.pybuild/cpython3_3.11_cpplint/build
> I: pybuild base:240: cd
> /<>/.pybuild/cpython3_3.11_cpplint/build; python3.11 -m pytest
> /<>/*test.py
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>, configfile: setup.cfg
> plugins: cov-4.0.0
> collected 208 items
>
> ../../../cpplint_clitest.py [
> 5%]
> ../../../cpplint_unittest.py ... [
> 26%]
> [
> 61%]
> [
> 95%]
> F
> [100%]
>
> === FAILURES
> ===
> __ UsageTest.testHelp
> __
>
> self =
>
> def testHelp(self):
> (status, out, err) = RunShellCommand(BASE_CMD + ' --help')
> self.assertEqual(0, status)
> self.assertEqual(b'', out)
> > self.assertTrue(err.startswith(b'\nSyntax: cpplint'))
> E AssertionError: False is not true
>
> ../../../cpplint_clitest.py:70: AssertionError
> _ NoRepoSignatureTests.testBoostSample
> _
>
> self =
>
> def testBoostSample(self):
> > self.checkAllInFolder('./samples/boost-sample', 4)
>
> ../../../cpplint_clitest.py:173:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> ../../../cpplint_clitest.py:119: in checkAllInFolder
> self._checkDef(os.path.join(dirpath, f))
> ../../../cpplint_clitest.py:128: in _checkDef
> self._runAndCheck(path,
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self =
> definition_file = './samples/boost-sample/exclude.def'
> args = '--recursive --exclude=headers/* src', expected_status = 1
> expected_out = ['Done processing src/inspect/unnamed_namespace_check.hpp',
> 'Done processing src/tr1/c_policy.hpp', 'Total errors found: 107', '']
> expected_err = ['src/inspect/unnamed_namespace_check.hpp:0: No #ifndef
> header guard found, suggested CPP variable is:
> SAMPLES_BOOST_...mespace_check.hpp:21: Anonymous namespace should be
> terminated with "// namespace" [readability/namespace] [5]', ...]
>
> def _runAndCheck(
> self,
> definition_file,
> args,
> expected_status,
> expected_out,
> expected_err
> ):
> rel_cwd = os.path.dirname(definition_file)
> cmd = BASE_CMD + self.get_extra_command_args(rel_cwd) + args
> cwd = os.path.join(self._root, rel_cwd)
> # command to reproduce, do not forget first two lines have special
> meaning
> print("\ncd " + cwd + " && " + cmd + " 2> ")
> (status, out, err) = RunShellComman
Bug#1027094: FTBFS against bind9 9.18.10
El 27/12/22 a las 18:16, Bernhard Schmidt escribió: Source: bind-dyndb-ldap Version: 11.10-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: team+...@tracker.debian.org bind-dyndb-ldap has a tight dependency on the upstream version of bind9-libs (built by src:bind9) and needs to be rebuilt on every new upstream version until https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 is fixed. Hello. I suppose this is the reason it does not build in stable either. Should we use the "found" directive with this bug, or it is better to file it as a separate bug? Thanks.
Processed: reassign 1027085 to src:zfs-linux
Processing commands for cont...@bugs.debian.org: > reassign 1027085 src:zfs-linux Bug #1027085 [src:linux] linux-image-5.10.0-20-amd64: failed to load zfs modules - after automatic update Bug reassigned from package 'src:linux' to 'src:zfs-linux'. No longer marked as found in versions linux/5.10.158-2. Ignoring request to alter fixed versions of bug #1027085 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1027085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025096: nanoc: FTBFS in bullseye, and will also FTBFS in bookworm next year
reopen 1025096
found 1025096 4.11.23-1
fixed 1025096 4.12.14-1
thanks
Please consider fixing this in stable as well.
I attach a proposal for a 4.11.23-1+deb11u1 version,
which is just a backport of the fix applied in 4.12.14-1.
Thanks.diff -Nru nanoc-4.11.23/debian/changelog nanoc-4.11.23/debian/changelog
--- nanoc-4.11.23/debian/changelog 2021-02-06 15:28:54.0 +0100
+++ nanoc-4.11.23/debian/changelog 2022-12-23 15:24:01.0 +0100
@@ -1,3 +1,9 @@
+nanoc (4.11.23-1+deb11u1) bullseye; urgency=medium
+
+ * Disable test that checks for the current year (Closes: #1025096)
+
+ -- Antonio Terceiro Fri, 23 Dec 2022 11:24:01 -0300
+
nanoc (4.11.23-1) unstable; urgency=medium
* New upstream version 4.11.23
diff -Nru
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
---
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
1970-01-01 01:00:00.0 +0100
+++
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
2022-12-23 15:24:01.0 +0100
@@ -0,0 +1,21 @@
+From: Antonio Terceiro
+Date: Fri, 23 Dec 2022 11:20:14 -0300
+Subject: Disable test that requires a given file to contain the current year
+
+This is a time bomb for any downstream distributors
+
+Forwarded: not-needed
+---
+ nanoc-core/spec/nanoc/core_spec.rb | 1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/nanoc-core/spec/nanoc/core_spec.rb
b/nanoc-core/spec/nanoc/core_spec.rb
+@@ -4,6 +4,7 @@
+
+ describe Nanoc::Core do
+ it 'has up-to-date version information' do
++skip "This is a time bomb for downstream distributors"
+ current_year = Date.today.year
+ expect(described_class.version_information).to match(/–#{current_year} /)
+ end
diff -Nru nanoc-4.11.23/debian/patches/series
nanoc-4.11.23/debian/patches/series
--- nanoc-4.11.23/debian/patches/series 2021-02-06 15:28:54.0 +0100
+++ nanoc-4.11.23/debian/patches/series 2022-12-23 15:24:01.0 +0100
@@ -15,3 +15,4 @@
0015-nanoc-core-skip-tests-that-fail-under-autopkgtest.patch
0016-filesystem_spec-skip-tests-that-fail-on-debian.patch
0017-nanoc-core-require-nanoc-version-for-test.patch
+0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
Processed: nanoc: FTBFS in bullseye, and will also FTBFS in bookworm next year
Processing commands for cont...@bugs.debian.org:
> reopen 1025096
Bug #1025096 {Done: Antonio Terceiro } [src:nanoc] nanoc:
FTBFS in bullseye, and will also FTBFS in bookworm next year
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions nanoc/4.12.14-1.
> found 1025096 4.11.23-1
Bug #1025096 [src:nanoc] nanoc: FTBFS in bullseye, and will also FTBFS in
bookworm next year
Ignoring request to alter found versions of bug #1025096 to the same values
previously set
> fixed 1025096 4.12.14-1
Bug #1025096 [src:nanoc] nanoc: FTBFS in bullseye, and will also FTBFS in
bookworm next year
Marked as fixed in versions nanoc/4.12.14-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1025096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1027062 marked as pending in sqlmodel
Processing control commands: > tag -1 pending Bug #1027062 [python3-sqlmodel] python3-sqlmodel -- Uninstallable with new sqlalchemy in unstable Added tag(s) pending. -- 1027062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027062: marked as pending in sqlmodel
Control: tag -1 pending Hello, Bug #1027062 in sqlmodel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sqlmodel/-/commit/81d4ab3692cde3104133e47d72bcd048e67106a9 allow to use sqlalchemy 1.4.45, which is currently in unstable; Closes: #1027062 (this message was generated automatically) -- Greetings https://bugs.debian.org/1027062
Bug#1019640: marked as done (ruby-mono-logger: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in `start': coverage mea
Your message dated Tue, 27 Dec 2022 19:05:35 + with message-id and subject line Bug#1019640: fixed in ruby-mono-logger 1.1.1-2 has caused the Debian Bug report #1019640, regarding ruby-mono-logger: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in `start': coverage measurement is already setup (RuntimeError) 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.) -- 1019640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-mono-logger Version: 1.1.1-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-mono-logger with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in > `start': coverage measurement is already setup (RuntimeError) > from > /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in > `start_coverage_with_criteria' > from > /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:343:in > `start_coverage_measurement' > from > /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:59:in > `start' > from /usr/lib/ruby/vendor_ruby/coveralls.rb:74:in `start!' > from /usr/lib/ruby/vendor_ruby/coveralls.rb:19:in `wear!' > from /<>/test/mri_logger_test.rb:10:in `' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in > `block in ' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `select' > from > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in > `' > [32m[Coveralls] Set up the SimpleCov formatter.[0m > [32m[Coveralls] Using SimpleCov's default settings.[0m > [33m[Coveralls] Outside the CI environment, not sending data.[0m > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/mri_logger_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-mono-logger/ruby-mono-logger_1.1.1-1+rebuild1663007849_amd64-2022-09-12T18:37:30Z.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-mono-logger Source-Version: 1.1.1-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of ruby-mono-logger, 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. Nilesh Patra (supplier of updated ruby-mono-logger package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Dec 2022 00:16:07 +0530 Source: ruby-mono-logger Architecture: source Version: 1.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Nilesh Patra Closes: 1019640 Changes: ruby-mono-logger (1.1.1-2) unstable; urgency=medium . * Team Upload.
Bug#1019628: marked as done (ruby-rspec-expectations: raise_error() matcher does not work with ruby3.1)
Your message dated Tue, 27 Dec 2022 18:51:34 +
with message-id
and subject line Bug#1019628: fixed in ruby-rspec 3.12.0c0e1m1s0-1
has caused the Debian Bug report #1019628,
regarding ruby-rspec-expectations: raise_error() matcher does not work with
ruby3.1
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.)
--
1019628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-hashie
Version: 3.5.5-4
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-hashie with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
>expected NoMethodError with "The property 'middle_name' is not defined
> for DashTest.", got # defined for DashTest.
>
> fail NoMethodError, "The property '#{property}' is not defined
> for #{self.class.name}."
> > with backtrace:
> # ./lib/hashie/dash.rb:206:in `fail_no_property_error!'
> # ./lib/hashie/dash.rb:184:in `assert_property_exists!'
> # ./lib/hashie/dash.rb:136:in `[]='
> # ./lib/hashie/dash.rb:143:in `block in merge'
> # ./lib/hashie/dash.rb:142:in `each'
> # ./lib/hashie/dash.rb:142:in `merge'
> # ./spec/hashie/dash_spec.rb:266:in `block (4 levels) in (required)>'
> # ./spec/hashie/dash_spec.rb:266:in `block (3 levels) in (required)>'
> # ./spec/hashie/dash_spec.rb:266:in `block (3 levels) in (required)>'
>
> Finished in 0.3638 seconds (files took 0.55129 seconds to load)
> 650 examples, 6 failures
>
> Failed examples:
>
> rspec ./spec/hashie/dash_spec.rb:107 # DashTest errors out for a non-existent
> property
> rspec ./spec/hashie/dash_spec.rb:140 # DashTest writing to properties fails
> writing to a non-existent property using []=
> rspec ./spec/hashie/dash_spec.rb:144 # DashTest writing to properties works
> for an existing property using []=
> rspec ./spec/hashie/dash_spec.rb:157 # DashTest reading from properties fails
> reading from a non-existent property using []
> rspec ./spec/hashie/dash_spec.rb:222 # DashTest#new fails with non-existent
> properties
> rspec ./spec/hashie/dash_spec.rb:265 # DashTest#merge fails with non-existent
> properties
>
> /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/hashie/array_spec.rb ./spec/hashie/clash_spec.rb
> ./spec/hashie/dash_spec.rb ./spec/hashie/extensions/autoload_spec.rb
> ./spec/hashie/extensions/coercion_spec.rb
> ./spec/hashie/extensions/dash/coercion_spec.rb
> ./spec/hashie/extensions/dash/indifferent_access_spec.rb
> ./spec/hashie/extensions/deep_fetch_spec.rb
> ./spec/hashie/extensions/deep_find_spec.rb
> ./spec/hashie/extensions/deep_locate_spec.rb
> ./spec/hashie/extensions/deep_merge_spec.rb
> ./spec/hashie/extensions/ignore_undeclared_spec.rb
> ./spec/hashie/extensions/indifferent_access_spec.rb
> ./spec/hashie/extensions/indifferent_access_with_rails_hwia_spec.rb
> ./spec/hashie/extensions/key_conversion_spec.rb
> ./spec/hashie/extensions/mash/keep_original_keys_spec.rb
> ./spec/hashie/extensions/mash/safe_assignment_spec.rb
> ./spec/hashie/extensions/mash/symbolize_keys_spec.rb
> ./spec/hashie/extensions/merge_initializer_spec.rb
> ./spec/hashie/extensions/method_access_spec.rb
> ./spec/hashie/extensions/strict_key_access_spec.rb
> ./spec/hashie/extensions/stringify_keys_spec.rb
> ./spec/hashie/extensions/symbolize_keys_spec.rb ./spec/hashie/hash_spec.rb
> ./spec/hashie/mash_spec.rb ./spec/hashie/parsers/yaml_erb_parser_spec.rb
> ./spec/hashie/rash_spec.rb ./spec/hashie/trash_spec.rb
> ./spec/hashie/utils_spec.rb ./spec/hashie/version_spec.rb
> ./spec/hashie_spec.rb ./spec/integration/omniauth/integration_spec.rb
> ./spec/integration/rails-without-dependency/integration_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-hashie/ruby-hashie_3.5.5-4+rebuild1663007681_amd64-2022-09-12T18:34:42Z.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 uns
Processed: severity of 1027058 is serious, severity of 1027060 is serious, severity of 1027059 is serious
Processing commands for cont...@bugs.debian.org: > severity 1027058 serious Bug #1027058 [src:ruby-github-api] ruby-github-api: FTBFS with ruby-hashie 5.0.0-1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'hashie' (>= 3.5.2, ~> 3.5) among 104 total gem(s) (Gem::MissingSpecError) Severity set to 'serious' from 'important' > severity 1027060 serious Bug #1027060 [src:ruby-varia-model] ruby-varia-model: FTBFS with ruby-hashie 5.0.0-1: unsatisfiable build-dependency: ruby-hashie (< 4.0.0) but 5.0.0-1 is to be installed Severity set to 'serious' from 'important' > severity 1027059 serious Bug #1027059 [src:ruby-rash-alt] ruby-rash-alt: FTBFS with ruby-hashie 5.0.0-1: ERROR: Test "ruby3.1" Could not find 'hashie' (~> 3.4) among 98 total gem(s) (Gem::MissingSpecError) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027058 1027059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027059 1027060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1027066 is serious, severity of 1027067 is serious, severity of 1027071 is serious ...
Processing commands for cont...@bugs.debian.org:
> severity 1027066 serious
Bug #1027066 [src:atig] atig: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error: user = t.get("users/show", { screen_name: nick})
Severity set to 'serious' from 'important'
> severity 1027067 serious
Bug #1027067 [src:ruby-bunny] ruby-bunny: FTBFS with ruby-rspec 3.12: ERROR:
Test "ruby3.1" failed: Failure/Error: expect(ch).to
receive(:exchange_bind).with(src1, dst, routing_key: "abc")
Severity set to 'serious' from 'important'
> severity 1027071 serious
Bug #1027071 [src:ruby-eim-xml] ruby-eim-xml: FTBFS with ruby-rspec 3.12:
ERROR: Test "ruby3.1" failed: Failure/Error:
EimXML::Formatter.write(element, opt.merge(:preservers=>PRESERVE_SPACES))
Severity set to 'serious' from 'important'
> severity 1027072 serious
Bug #1027072 [src:ruby-fission] ruby-fission: FTBFS with ruby-rspec 3.12:
ERROR: Test "ruby3.1" failed: Failure/Error:
Fission::Action::VM::Stopper.new(self).stop(options)
Severity set to 'serious' from 'important'
> severity 1027073 serious
Bug #1027073 [src:ruby-gh] ruby-gh: FTBFS with ruby-rspec 3.12: ERROR: Test
"ruby3.1" failed: Failure/Error: expect { subject['/x'] }.to
raise_error(GH::Error(:response_status => 500))
Severity set to 'serious' from 'important'
> severity 1027074 serious
Bug #1027074 [src:ruby-grape] ruby-grape: FTBFS with ruby-rspec 3.12: ERROR:
Test "ruby3.1" failed: Failure/Error:
namespace_inheritable(:version_options, options)
Severity set to 'serious' from 'important'
> severity 1027075 serious
Bug #1027075 [src:ruby-guard] ruby-guard: FTBFS with ruby-rspec 3.12: ERROR:
Test "ruby3.1" failed.
Severity set to 'serious' from 'important'
> severity 1027076 serious
Bug #1027076 [src:ruby-influxdb] ruby-influxdb: FTBFS with ruby-rspec 3.12:
ERROR: Test "ruby3.1" failed.
Severity set to 'serious' from 'important'
> severity 1027078 serious
Bug #1027078 [src:ruby-jira] ruby-jira: FTBFS with ruby-rspec 3.12: ERROR: Test
"ruby3.1" failed: Failure/Error: result.push(client.Issue.build(issue))
Severity set to 'serious' from 'important'
> severity 1027079 serious
Bug #1027079 [src:ruby-listen] ruby-listen: FTBFS with ruby-rspec 3.12: ERROR:
Test "ruby3.1" failed: Failure/Error: @snapshots[dir].invalidate(type,
rel_path, options)
Severity set to 'serious' from 'important'
> severity 1027080 serious
Bug #1027080 [src:ruby-localhost] ruby-localhost: FTBFS: tests fail randomly
Ignoring request to change severity of Bug 1027080 to the same value.
> severity 1027081 serious
Bug #1027081 [src:ruby-multi-json] ruby-multi-json: FTBFS with ruby-rspec 3.12:
ERROR: Test "ruby3.1" failed: Failure/Error: self.load_options =
self.dump_options = value
Severity set to 'serious' from 'important'
> severity 1027082 serious
Bug #1027082 [src:ruby-mysql2] ruby-mysql2: FTBFS: ERROR: Test "ruby3.1"
failed: mysqld crashes at startup
Ignoring request to change severity of Bug 1027082 to the same value.
> severity 1027083 serious
Bug #1027083 [src:ruby-notiffany] ruby-notiffany: FTBFS with ruby-rspec 3.12:
ERROR: Test "ruby3.1" failed: Failure/Error: expect(foo_object).to
receive(:notify).with("Hello", foo: "bar")
Severity set to 'serious' from 'important'
> severity 1027086 serious
Bug #1027086 [src:ruby-rest-client] ruby-rest-client: FTBFS with ruby-rspec
3.12: ERROR: Test "ruby3.1" failed: Failure/Error:
Severity set to 'serious' from 'important'
> severity 1027087 serious
Bug #1027087 [src:ruby-rubocop-performance] ruby-rubocop-performance: FTBFS:
ERROR: Test "ruby3.1" failed: Failure/Error: subject(:config) {
RuboCop::ConfigLoader.load_file('config/default.yml') }
Ignoring request to change severity of Bug 1027087 to the same value.
> severity 1027088 serious
Bug #1027088 [src:ruby-seamless-database-pool] ruby-seamless-database-pool:
FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:
master_connection = send("#{master_config[:adapter]}_connection".to_sym,
master_config)
Severity set to 'serious' from 'important'
> severity 1027089 serious
Bug #1027089 [src:ruby-simplecov] ruby-simplecov: FTBFS with ruby-rspec 3.12:
ERROR: Test "ruby3.1" failed: Failure/Error:
Coverage.start(start_arguments)
Severity set to 'serious' from 'important'
> severity 1027090 serious
Bug #1027090 [src:ruby-slack-messenger] ruby-slack-messenger: FTBFS with
ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:
Severity set to 'serious' from 'important'
> severity 1027091 serious
Bug #1027091 [src:ruby-slack-notifier] ruby-slack-notifier: FTBFS with
ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: client.post
endpoint, params
Severity set to 'serious' from 'important'
> severity 1027092 serious
Bug #1027092 [src:ruby-stomp] ruby-stomp: FTBFS with ruby-rspec 3.12: ERROR:
Test "ruby3.1" failed: Failure/Error:
Severity set to 'serious' from 'important'
> severity 1027093 seriou
Bug#1027094: FTBFS against bind9 9.18.10
Source: bind-dyndb-ldap
Version: 11.10-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: team+...@tracker.debian.org
bind-dyndb-ldap has a tight dependency on the upstream version of bind9-libs
(built by src:bind9) and needs to be rebuilt on every new upstream version
until https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 is fixed.
This worked fine until bind9 9.18.8, but fails in 9.18.10
https://buildd.debian.org/status/fetch.php?pkg=bind-dyndb-ldap&arch=amd64&ver=11.10-1%2Bb5&stamp=1671812545&raw=0
This is rather serious as it prevents the migration of 9.18.10 to testing
which includes systemd notify support and upstream bugfixes. Also bind9 has
followed upstream security releases during bullseye already, so it will
break later if 9.18.10 misses the freeze due to this issue.
Possible commits:
https://gitlab.isc.org/isc-projects/bind9/-/compare/v9_18_8...v9_18_10?from_project_id=1
In file included from ../../src/zone_register.h:8,
from ../../src/ldap_convert.c:28:
/usr/include/dns/zt.h:171:28: error: unknown type name ‘isc_rwlocktype_t’; did
you mean ‘isc_rwlock_t’?
171 | dns_zt_apply(dns_zt_t *zt, isc_rwlocktype_t lock, bool stop,
isc_result_t *sub,
|^~~~
|isc_rwlock_t
make[3]: *** [Makefile:592: ldap_la-ldap_convert.lo] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from ../../src/util.h:17,
from ../../src/bindcfg.h:10,
from ../../src/ldap_driver.c:39:
../../src/ldap_driver.c: In function ‘beginload’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
| ^~~
../../src/ldap_driver.c:220:9: note: in expansion of macro ‘fatal_error’
220 | fatal_error("ldapdb: method beginload() should never be
called");
| ^~~
In file included from /usr/include/isc/util.h:312,
from /usr/include/isc/atomic.h:22,
from /usr/include/isc/refcount.h:19,
from ../../src/ldap_driver.c:16:
/usr/include/isc/error.h:42:1: note: declared here
42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
| ^~~
../../src/ldap_driver.c: In function ‘endload’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
| ^~~
../../src/ldap_driver.c:237:9: note: in expansion of macro ‘fatal_error’
237 | fatal_error("ldapdb: method endload() should never be called");
| ^~~
/usr/include/isc/error.h:42:1: note: declared here
42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
| ^~~
../../src/ldap_driver.c: In function ‘dump’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
| ^~~
../../src/ldap_driver.c:266:9: note: in expansion of macro ‘fatal_error’
266 | fatal_error("ldapdb: method dump() should never be called");
| ^~~
/usr/include/isc/error.h:42:1: note: declared here
42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
| ^~~
../../src/ldap_driver.c: In function ‘allrdatasets’:
../../src/ldap_driver.c:474:71: error: passing argument 5 of
‘dns_db_allrdatasets’ makes integer from pointer without a cast
[-Werror=int-conversion]
474 | return dns_db_allrdatasets(ldapdb->rbtdb, node, version, now,
iteratorp);
|
^
| |
|
dns_rdatasetiter_t ** {aka struct dns_rdatasetiter **}
In file included from ../../src/ldap_driver.c:22:
/usr/include/dns/db.h:1162:57: note: expected ‘isc_stdtime_t’ {aka ‘unsigned
int’} but argument is of type ‘dns_rdatasetiter_t **’ {aka ‘struct
dns_rdatasetiter **’}
1162 | unsigned int options, isc_stdtime_t now,
| ~~^~~
../../src/ldap_driver.c:474:16: error: too few arguments to function
‘dns_db_allrdatasets’
474 | return dns_db_allrdatasets(ldapdb->rbtdb, node, version, now,
iteratorp);
|^~~
/usr/include/dns/db.h:1161:1: note: declared here
1161 | dns_db_allrdatasets(dns_db_t *db, dns_dbnode_t *node, dns_dbversion_t
*version,
| ^~~
../../src/ldap_driver.c: In function ‘node_isempty’:
../../src/ldap_driver.c:517:62: error: passing argument 5 of
‘dns_db_allrdatasets’ makes integer from po
Bug#1027087: ruby-rubocop-performance: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: subject(:config) { RuboCop::ConfigLoader.load_file('config/default.yml') }
Source: ruby-rubocop-performance
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-rubocop-performance failed to build. I retried with the version in
the archive, and obtained the same failure so this is not related to
ruby-rspec.
Relevant part of the build log (hopefully):
> Failure/Error: subject(:config) {
> RuboCop::ConfigLoader.load_file('config/default.yml') }
>
> RuboCop::ValidationError:
>`Performance` cops have been extracted to the `rubocop-performance`
> gem.
>(obsolete configuration found in config/default.yml, please update it)
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_obsoletion.rb:43:in
> `reject_obsolete!'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_validator.rb:78:in
> `check_obsoletions'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_validator.rb:44:in
> `validate'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config.rb:49:in
> `check'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config.rb:38:in
> `create'
> #
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_loader.rb:57:in
> `load_file'
> # ./spec/project_spec.rb:5:in `block (3 levels) in '
> # ./spec/project_spec.rb:34:in `block (4 levels) in '
> # ./spec/project_spec.rb:33:in `each'
> # ./spec/project_spec.rb:33:in `block (3 levels) in '
>
> Finished in 24.75 seconds (files took 2.65 seconds to load)
> 7975 examples, 5 failures
>
> Failed examples:
>
> rspec ./spec/project_spec.rb:40 # RuboCop Performance Project default
> configuration file sorts configuration keys alphabetically
> rspec ./spec/project_spec.rb:22 # RuboCop Performance Project default
> configuration file requires a nicely formatted `VersionAdded` metadata for
> all cops
> rspec ./spec/project_spec.rb:14 # RuboCop Performance Project default
> configuration file has a nicely formatted description for all cops
> rspec ./spec/project_spec.rb:47 # RuboCop Performance Project default
> configuration file has a SupportedStyles for all EnforcedStyle and
> EnforcedStyle is valid
> rspec ./spec/project_spec.rb:32 # RuboCop Performance Project default
> configuration file has a period at EOL of description
>
> Randomized with seed 20775
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
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
ruby-rubocop-performance.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
Bug#1027085: linux-image-5.10.0-20-amd64: failed to load zfs modules - after automatic update
Package: src:linux Version: 5.10.158-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: ben...@demaine.info Installed this machine 12 months ago, and never did any manual update. Obviously, there are background automatic updates, because these kernels are more recent than my install: -rw-r--r-- 1 root root 6.7M 2 sept. 15:54 vmlinuz-5.10.0-18-amd64 -rw-r--r-- 1 root root 6.7M 13 déc. 21:46 vmlinuz-5.10.0-20-amd64 which are not default for a machine installed in december 2021. I rarely reboot; but last week the computer refused to reboot with message: failed to load zfs modules I forgot to remove QUIET option; I will record screen with quiet removed. So: vmlinuz-5.10.0-20-amd64 bugs vmlinuz-5.10.0-18-amd64 works (now) vmlinuz-5.10.0-16-amd64 had been auto-removed; and when I reinstalled it, it did not work. This means the bug may not be in linux-image-5.10.0-20-amd64 but either in a dep, or an other system utility. When I will bring the bootlog, I will check deeper against #1015295 #1017399 #1019544 #1022202 Issue was discussed here, but no-one have a clue about ZFS specifics: https://forums.debian.net/viewtopic.php?p=764805 Installation had been done following https://wiki.debian.org/ZFS https://arstechnica.com/gadgets/2021/06/a-quick-start-guide-to-openzfs-native-encryption/ -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Latitude E6430 product_version: 01 chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A24 board_vendor: Dell Inc. board_name: 0H3MT5 board_version: A00 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Dell 3rd Gen Core processor DRAM Controller [1028:0534] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ivb_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [1028:0534] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+ LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes, Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s (downgraded), Width x16 (ok) TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd- AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
Bug#1027061: marked as pending in sqlmodel
Control: tag -1 pending Hello, Bug #1027061 in sqlmodel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sqlmodel/-/commit/cdc5a478f73cdb40aaedd02761b1233dd9e9118a add httpx to b-d, needed by tests; Closes: #1027061 (this message was generated automatically) -- Greetings https://bugs.debian.org/1027061
Processed: Bug#1027061 marked as pending in sqlmodel
Processing control commands: > tag -1 pending Bug #1027061 [src:sqlmodel] sqlmodel -- FTBFS with python3.11 Added tag(s) pending. -- 1027061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026346: petsc4py: autopkgtest needs update for new version of numpy: OverflowError: Python int too large to convert to C int
Source: petsc4py Followup-For: Bug #1026346 Control: affects 1027044 src:petsc4py As far as I can tell, this error is the python/numpy verson of "missing symbol" error after a library update with ABI bump. A similar error was found in many packages depending on numpy during the recent upgrade to numpy 1.23. Packages built after that (in unstable) saw the same error from their older version in testing, which cleared once the new packages (numpy and these new packages) migrated to testing. We have sonames to manage shared library dependencies, and manage library package updates using Transition bugs. In principle we have the same mechanism with numpy, python3-numpy Provides: python3-numpy-abi9, python3-numpy-api16 and correspondingly python3-petsc4py-real3.18 Depends: python3-numpy-abi9 and there is a new Transition bug filed (Bug#1027044) to now update numpy to 1.24. I'm not sure why the numpy abi mechanism has failed this time with petsc4py and numpy 1.23. Perhaps the abi declaration is buggy and numpy 1.23 does not actually provide python3-numpy-abi9. In any case, I expect the error to clear after rebuilding petsc4py against the latest numpy. Since the numpy transtion Bug#1027044 is filed, the problem should clear as part of that transition.
Bug#1027082: ruby-mysql2: FTBFS: ERROR: Test "ruby3.1" failed: mysqld crashes at startup
Source: ruby-mysql2 Version: 0.5.3-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-mysql2 failed to build. I retried it with the version in the archive, and obtained the same failure. Relevant part of the build log (hopefully): > adduser: Warning: The home dir /nonexistent you specified can't be accessed: > No such file or directory > Unpacking mariadb-server-10.6 (1:10.6.11-1) ... > Selecting previously unselected package libpython3.10-minimal:amd64. > Preparing to unpack .../libpython3.10-minimal_3.10.9-1_amd64.deb ... > Unpacking libpython3.10-minimal:amd64 (3.10.9-1) ... > Selecting previously unselected package libexpat1:amd64. > Preparing to unpack .../libexpat1_2.5.0-1_amd64.deb ... > Unpacking libexpat1:amd64 (2.5.0-1) ... > Selecting previously unselected package python3.10-minimal. > Preparing to unpack .../python3.10-minimal_3.10.9-1_amd64.deb ... > Unpacking python3.10-minimal (3.10.9-1) ... > Setting up libpython3.10-minimal:amd64 (3.10.9-1) ... > Setting up libexpat1:amd64 (2.5.0-1) ... > Setting up python3.10-minimal (3.10.9-1) ... > Selecting previously unselected package python3-minimal. > (Reading database ... 17541 files and directories currently installed.) > Preparing to unpack .../0-python3-minimal_3.10.6-3+b1_amd64.deb ... > Unpacking python3-minimal (3.10.6-3+b1) ... > Selecting previously unselected package media-types. > Preparing to unpack .../1-media-types_8.0.0_all.deb ... > Unpacking media-types (8.0.0) ... > Selecting previously unselected package libmpdec3:amd64. > Preparing to unpack .../2-libmpdec3_2.5.1-2_amd64.deb ... > Unpacking libmpdec3:amd64 (2.5.1-2) ... > Selecting previously unselected package libsqlite3-0:amd64. > Preparing to unpack .../3-libsqlite3-0_3.40.0-2_amd64.deb ... > Unpacking libsqlite3-0:amd64 (3.40.0-2) ... > Selecting previously unselected package libpython3.10-stdlib:amd64. > Preparing to unpack .../4-libpython3.10-stdlib_3.10.9-1_amd64.deb ... > Unpacking libpython3.10-stdlib:amd64 (3.10.9-1) ... > Selecting previously unselected package python3.10. > Preparing to unpack .../5-python3.10_3.10.9-1_amd64.deb ... > Unpacking python3.10 (3.10.9-1) ... > Selecting previously unselected package libpython3-stdlib:amd64. > Preparing to unpack .../6-libpython3-stdlib_3.10.6-3+b1_amd64.deb ... > Unpacking libpython3-stdlib:amd64 (3.10.6-3+b1) ... > Setting up python3-minimal (3.10.6-3+b1) ... > Selecting previously unselected package python3. > (Reading database ... 17953 files and directories currently installed.) > Preparing to unpack .../000-python3_3.10.6-3+b1_amd64.deb ... > Unpacking python3 (3.10.6-3+b1) ... > Selecting previously unselected package netbase. > Preparing to unpack .../001-netbase_6.4_all.deb ... > Unpacking netbase (6.4) ... > Selecting previously unselected package sensible-utils. > Preparing to unpack .../002-sensible-utils_0.0.17_all.deb ... > Unpacking sensible-utils (0.0.17) ... > Selecting previously unselected package openssl. > Preparing to unpack .../003-openssl_3.0.7-1_amd64.deb ... > Unpacking openssl (3.0.7-1) ... > Selecting previously unselected package ca-certificates. > Preparing to unpack .../004-ca-certificates_20211016_all.deb ... > Unpacking ca-certificates (20211016) ... > Selecting previously unselected package libmagic-mgc. > Preparing to unpack .../005-libmagic-mgc_1%3a5.41-4_amd64.deb ... > Unpacking libmagic-mgc (1:5.41-4) ... > Selecting previously unselected package libmagic1:amd64. > Preparing to unpack .../006-libmagic1_1%3a5.41-4_amd64.deb ... > Unpacking libmagic1:amd64 (1:5.41-4) ... > Selecting previously unselected package file. > Preparing to unpack .../007-file_1%3a5.41-4_amd64.deb ... > Unpacking file (1:5.41-4) ... > Selecting previously unselected package gettext-base. > Preparing to unpack .../008-gettext-base_0.21-10_amd64.deb ... > Unpacking gettext-base (0.21-10) ... > Selecting previously unselected package libuchardet0:amd64. > Preparing to unpack .../009-libuchardet0_0.0.7-1_amd64.deb ... > Unpacking libuchardet0:amd64 (0.0.7-1) ... > Selecting previously unselected package groff-base. > Preparing to unpack .../010-groff-base_1.22.4-9_amd64.deb ... > Unpacking groff-base (1.22.4-9) ... > Selecting previously unselected package bsdextrautils. > Preparing to unpack .../011-bsdextrautils_2.38.1-4_amd64.deb ... > Unpacking bsdextrautils (2.38.1-4) ... > Selecting previously unselected package libpipeline1:amd64. > Preparing to unpack .../012-libpipeline1_1.5.7-1_amd64.deb ... > Unpacking libpipeline1:amd64 (1.5.7-1) ... > Selecting previously unselected package man-db. > Preparing to unpack .../013-man-db_2.11.1-1_amd64.deb ... > Unpacking man-db (2.11.1-1) ... > Selecting previously unselected package m4. > Preparing to unpack .../014-m4_1.4.19-1_amd64.deb ... > Unpacking m4 (1.4.19-1) ... > Selecting previously unselected p
Bug#1027080: ruby-localhost: FTBFS: tests fail randomly
Source: ruby-localhost Version: 1.1.9-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-localhost failed to build. I retried it with ruby-rspec 3.10 from the archive, and I got one successfull build, and one failure exactly like the one below. So this means the test suite fails randomly, and that is a problem. Relevant part of the build log (hopefully): > 2.2) Failure/Error: expect(status).to be_success > expected `#.success?` to be > truthy, got false > # ./spec/localhost/protocol_spec.rb:42:in `block (2 levels) in (required)>' > # > /usr/share/rubygems-integration/all/gems/async-rspec-1.16.1/lib/async/rspec/reactor.rb:93:in > `block (4 levels) in ' > # > /usr/share/rubygems-integration/all/gems/async-rspec-1.16.1/lib/async/rspec/reactor.rb:57:in > `block in run_in_reactor' > # > /usr/share/rubygems-integration/all/gems/async-1.30.3/lib/async/task.rb:261:in > `block in make_fiber' > > Finished in 2.71 seconds (files took 0.22921 seconds to load) > 10 examples, 2 failures > > Failed examples: > > rspec './spec/localhost/protocol_spec.rb[1:1:2]' # Localhost::Authority > behaves like valid protocol can connect using HTTP over TLSv1.2 > rspec './spec/localhost/protocol_spec.rb[1:2:2]' # Localhost::Authority > behaves like valid protocol can connect using HTTP over default > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is attached. 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 ruby-localhost.log.gz Description: application/gzip signature.asc Description: PGP signature
Bug#965924: marked as done (zemberek-ooo: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 27 Dec 2022 15:07:12 + with message-id and subject line Bug#965924: fixed in zemberek-ooo 1.0~rc2-10.5 has caused the Debian Bug report #965924, regarding zemberek-ooo: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zemberek-ooo Version: 1.0~rc2-10.4 Severity: normal Usertags: compat-5-6-removal Hi, The package zemberek-ooo uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: zemberek-ooo Source-Version: 1.0~rc2-10.5 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of zemberek-ooo, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated zemberek-ooo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 Dec 2022 09:47:05 +0800 Source: zemberek-ooo Architecture: source Version: 1.0~rc2-10.5 Distribution: unstable Urgency: low Maintainer: Rail Aliev Changed-By: Ying-Chun Liu (PaulLiu) Closes: 802416 965924 1017942 Changes: zemberek-ooo (1.0~rc2-10.5) unstable; urgency=low . * Non-maintainer upload. (Closes: #1017942) * Bump debhelper compat to 10. (Closes: #965924) * Fix FTBFS due to missing ure-link (Closes: #802416) Checksums-Sha1: 1947f8023fffa0170b3f13d8578b56d99f0f8d96 2140 zemberek-ooo_1.0~rc2-10.5.dsc f4f4fe889acb7dbfe8a250011b765ff3260301f7 3344 zemberek-ooo_1.0~rc2-10.5.debian.tar.xz e80980790e9c40721fc2baff5b5f9b1bfa2c5638 13489 zemberek-ooo_1.0~rc2-10.5_source.buildinfo Checksums-Sha256: 9ee88ef29183bd371859a50149caab0e5a3eaaab9d9d790e87b5da205a9b2fc7 2140 zemberek-ooo_1.0~rc2-10.5.dsc 20762c376b5aef5e10fcb1cdc223bd6379efef84033b4870fcb7d70c50bd060c 3344 zemberek-ooo_1.0~rc2-10.5.debian.tar.xz 790575a8c72be6f53c4ae2005889e1f034f740d9025e2906241b14dbcd302a8d 13489 zemberek-ooo_1.0~rc2-10.5_source.buildinfo Files: cff6f8b8c49d26549f4b121a3eb86b21 2140 text optional zemberek-ooo_1.0~rc2-10.5.dsc 21b8b8445f8d261c28fb8181507af955 3344 text optional zemberek-ooo_1.0~rc2-10.5.debian.tar.xz e657c55b694f3fecd259d0c657302edf 13489 text optional zemberek-ooo_1.0~rc2-10.5_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOdz9sTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiBlOD/wO2wMT0cn8gVNsxSxY8n89jNKIPT8m 80vRXHUXFMggXlC7xVV95lSzK4hHb4OQyEtqmeTuKy75GOLWvc+jVJ8QZ5rOUvo7 fMeZOI86gpU3kzJxcU3FmctQ9kVs1AIqHewJksC4eeJHRSlgg1TD+i+K5t/kmKrP iQQLO3md8CQLpQ7wQrGJ6eYuDW43D8hmLnJ3XU9ADNTO+7lO6J/MQewfYRKnsP0K sr2qs94WxpuD9jHCKPrJKSWHZ7xBq22wnTzS09PC0Srqq7MbVsSfnd8wdheIdeDV Ra4YpzYm6iq8f4z7QH1vGko9gB125s75Pxr/PqegxjWIyVFWXGX7VeiDlfyP/fuE +XUaHlk7unj1r9TaMrljGTPdAQ9YVSWkX08NNzvY+svvNeCNaRTydfDD+9Ra3NJi iRylt3p9PqhhLdf1L/3rh4tkHhQ2AR/10rqrAjbXT5+tmltV1YF4tx3mKFb5T3Th rSyBGtQrzx6qNfiaWl2E6K6+3ANY90DOX8TkQRr72byjsKkxYpU/2typovioTkGs NY9bNsIUryjfimeVXlhJq
Bug#802416: marked as done (zemberek-ooo: FTBFS: /usr/lib/libreoffice/ure-link/share/java does not exist)
Your message dated Tue, 27 Dec 2022 15:07:12 + with message-id and subject line Bug#802416: fixed in zemberek-ooo 1.0~rc2-10.5 has caused the Debian Bug report #802416, regarding zemberek-ooo: FTBFS: /usr/lib/libreoffice/ure-link/share/java does not exist 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.) -- 802416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zemberek-ooo Version: 1.0~rc2-10.4 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: compile-java: [javac] /zemberek-ooo-1.0~rc2/build.xml:60: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 11 source files to /zemberek-ooo-1.0~rc2/build/classes BUILD FAILED /zemberek-ooo-1.0~rc2/build.xml:167: The following error occurred while executing this line: /zemberek-ooo-1.0~rc2/build.xml:60: /usr/lib/libreoffice/ure-link/share/java does not exist. Total time: 0 seconds Possibly related to https://bugs.debian.org/802402 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/zemberek-ooo.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: zemberek-ooo Source-Version: 1.0~rc2-10.5 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of zemberek-ooo, 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 802...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated zemberek-ooo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 Dec 2022 09:47:05 +0800 Source: zemberek-ooo Architecture: source Version: 1.0~rc2-10.5 Distribution: unstable Urgency: low Maintainer: Rail Aliev Changed-By: Ying-Chun Liu (PaulLiu) Closes: 802416 965924 1017942 Changes: zemberek-ooo (1.0~rc2-10.5) unstable; urgency=low . * Non-maintainer upload. (Closes: #1017942) * Bump debhelper compat to 10. (Closes: #965924) * Fix FTBFS due to missing ure-link (Closes: #802416) Checksums-Sha1: 1947f8023fffa0170b3f13d8578b56d99f0f8d96 2140 zemberek-ooo_1.0~rc2-10.5.dsc f4f4fe889acb7dbfe8a250011b765ff3260301f7 3344 zemberek-ooo_1.0~rc2-10.5.debian.tar.xz e80980790e9c40721fc2baff5b5f9b1bfa2c5638 13489 zemberek-ooo_1.0~rc2-10.5_source.buildinfo Checksums-Sha256: 9ee88ef29183bd371859a50149caab0e5a3eaaab9d9d790e87b5da205a9b2fc7 2140 zemberek-ooo_1.0~rc2-10.5.dsc 20762c376b5aef5e10fcb1cdc223bd6379efef84033b4870fcb7d70c50bd060c 3344 zemberek-ooo_1.0~rc2-10.5.debian.tar.xz 790575a8c72be6f53c4ae2005889e1f034f740d9025e2906241b14dbcd302a8d 13489 zemberek-ooo_1.0~rc2-10.5_source.buildinfo Files: cff6f8b8c49d26549f4b121a3eb86b21 2140 text optional zemberek-ooo_1.0~rc2-10.5.dsc 21b8b8445f8d261c28fb8181507af955 3344 text optional zemberek-ooo_1.0~rc2-10.5.debian.tar.xz e657c55b694f3fecd259d0c657302edf 13489 text optional zemberek-ooo_1.0~rc2-10.5_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOdz9sTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiBlOD/wO2wMT0cn8gVNsxSxY8n89jNKIPT8m 80vRXHUXFMggXlC7xVV95lSzK4hHb4OQyEtqmeTuKy75GOLWvc+jVJ8QZ5rOUvo7 fMeZOI86gpU3kzJxcU3FmctQ9kVs1AIqHewJksC4eeJHRSlgg1TD+i+K5t/kmKrP iQQLO3md8CQLpQ7wQrGJ6eYuDW43D8hmLnJ3XU9ADNTO+7lO6J/MQewfYRKnsP0K sr2qs94WxpuD9jHCKPrJKSWHZ7xBq22wnTzS09PC0Srqq7MbVsSfnd8wdheIdeDV Ra4YpzYm6iq8f4z7QH1vGko9gB125s75Pxr/PqegxjWIyVFWXGX7VeiDlfyP/fuE +XUaHlk7unj1r9TaMrljGTPdAQ9YVSWkX08NNzvY+svvNeCNaRTydfDD+9Ra3NJi iRylt3p9PqhhLdf1L/3rh4tkHhQ2AR/10rqrAjbXT5+tmltV1YF4tx3mKFb5T3Th rSyBGtQrzx6qNfiaWl2E6K6+3ANY90DOX8TkQRr72byjsKkxYpU/2typovioTkGs NY9bNsIUryjfimeVXlhJqvbnqN7UMSO5I0GfJjLaxSG/yQ4peue4g+gI0JE07hxU 4lUG5PjScupwQB32tnbI1Ar3MZuI8ArAKMdy92QCG1h8nyT+ly9ghuuzqK+T8QzO cijiwX6dsgJjvw== =
Bug#1023530: nut: flaky autopkgtest: varying failures
Hi, On 27-12-2022 13:38, Paul Gevers wrote: It's impossible for me to reproduce this locally, can you still see that in the CI runs? You can trigger the test yourself to. Just hit one of the recycle (♲) buttons (I recommend using a migration-reference/0 run for those retries). I triggered 6 runs on armel; 1 failed: https://ci.debian.net/packages/n/nut/unstable/armel/ Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1026312: meson: diff for NMU version 1.0.0-1.1
Hi Eli (2022.12.24_21:46:13_-0400) > This patch is non-upstreamable. For context, this patch is along the same lines as changes you are making in your refactor, upstream in https://github.com/mesonbuild/meson/pull/11133 Your refactor goes further and removes distutils use entirely, where possible. It's still required on older Debian systems, because the deb_system scheme was patched into distutils but not sysconfig at the time. So, I still think we should be landing this patch in Debian, until your refactor is released, and I haven't cancelled the NMU. > I must confess however that I am surprised that setuptools is installed > in your buildd at all -- Meson doesn't use it, and projects using Meson > most likely don't also need setuptools at the same time. So this should > be a moot point. > > If setuptools is not installed, it cannot overwrite the stdlib > distutils. And there's a viable approach to not using distutils by the > time distutils is removed from the stdlib. To expand on what Eli is saying here, if meson Conflicted with python3-setuptools, or exported SETUPTOOLS_USE_DISTUTILS=stdlib, then this patch would not be required. However, such a conflict wouldn't be ideal for user systems. And virtualenvs still come with setuptools by default, so meson probably needs to be able to coexist with it. For the export option, I wouldn't want to patch something like that into our meson, unless we had to. That should be an upstream decision. I think coexisting with setuptools and setuptools-distutils is the best way forward. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1026980: marked as done (pyqt5: FTBFS on mipsel (MemoryError))
Your message dated Tue, 27 Dec 2022 14:43:26 +
with message-id
and subject line Bug#1026980: fixed in pyqt5 5.15.7+dfsg-3
has caused the Debian Bug report #1026980,
regarding pyqt5: FTBFS on mipsel (MemoryError)
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.)
--
1026980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyqt5
Version: 5.15.7+dfsg-2
Severity: serious
Tags: upstream ftbfs
Control: block 1025863 by -1
Dear Maintainer,
Your package FTBFS on mipsel, even on buildds where it built successfully
before, during the qtbase-opensource-src transition:
Generating the _QOpenGLFunctions_2_0 bindings...
sip-build: An internal error occurred...
Traceback (most recent call last):
File "/usr/bin/sip-build", line 33, in
sys.exit(load_entry_point('sip==6.7.5', 'console_scripts', 'sip-build')())
File "/usr/lib/python3/dist-packages/sipbuild/tools/build.py", line 37, in
main
handle_exception(e)
File "/usr/lib/python3/dist-packages/sipbuild/exceptions.py", line 81, in
handle_exception
raise e
File "/usr/lib/python3/dist-packages/sipbuild/tools/build.py", line 34, in
main
project.build()
File "/usr/lib/python3/dist-packages/sipbuild/project.py", line 244, in build
self.builder.build()
File "/usr/lib/python3/dist-packages/sipbuild/builder.py", line 48, in build
self._generate_bindings()
File "/usr/lib/python3/dist-packages/sipbuild/builder.py", line 277, in
_generate_bindings
buildable = bindings.generate()
File "/usr/lib/python3/dist-packages/sipbuild/bindings.py", line 166, in
generate
spec, sip_files = parse(self.sip_file, SIP_VERSION, encoding,
File "/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser.py",
line 36, in parse
protected_is_public, include_dirs, sip_module, is_strict).parse(
File
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser_manager.py",
line 1505, in parse
self._parser.parse(self._read(sip_file, raw_sip_file),
File "/usr/lib/python3/dist-packages/ply/yacc.py", line 331, in parse
return self.parseopt(input, lexer, debug, tracking, tokenfunc)
File "/usr/lib/python3/dist-packages/ply/yacc.py", line 823, in parseopt
p.callable(pslice)
File "/usr/lib/python3/dist-packages/sipbuild/generator/parser/rules.py",
line 765, in p_include_simple
pm.push_file(p, 1)
File
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser_manager.py",
line 1685, in push_file
self._lexer.input(self._read(sip_file, raw_sip_file))
File
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser_manager.py",
line 2120, in _read
self._input = f.read()
File "/usr/lib/python3.10/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
MemoryError
https://buildd.debian.org/status/fetch.php?pkg=pyqt5&arch=mipsel&ver=5.15.7%2Bdfsg-2%2Bb1&stamp=1671914840&raw=0
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
Source: pyqt5
Source-Version: 5.15.7+dfsg-3
Done: Dmitry Shachnev
We believe that the bug you reported is fixed in the latest version of
pyqt5, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated pyqt5 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 27 Dec 2022 16:51:02 +0300
Source: pyqt5
Architecture: source
Version: 5.15.7+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Dmitry Shachnev
Closes: 1026980
Changes:
pyqt5 (5.15.7+dfsg-3) unstable; urgency=medium
.
* Disable generation of .pyi files on mipsel to reduce memory consumption
(closes: #1026980).
* Update Lintian overrides for the pointed hints.
* Bump Standards-Version to 4.6.2, no changes needed.
Checksums-Sha1:
3a854005217139e7baa1b3500bca36d14b9a4376 4407 pyqt5_5.15.7+dfsg-3.dsc
d870b14fe9a93cf99a26c99408bc0c82e9ec83fc 17748
pyqt5_5.15.7+dfsg-3.debian.tar.xz
d2950954deebc7edf95d1e4080e994
Bug#1026980: marked as pending in pyqt5
Control: tag -1 pending Hello, Bug #1026980 in pyqt5 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pyqt5/-/commit/d20365bb3aefff2b00f5aaf5f928f45a3cb42974 Disable generation of .pyi files on mipsel to reduce memory consumption. Closes: #1026980. (this message was generated automatically) -- Greetings https://bugs.debian.org/1026980
Processed: Bug#1026980 marked as pending in pyqt5
Processing control commands: > tag -1 pending Bug #1026980 [src:pyqt5] pyqt5: FTBFS on mipsel (MemoryError) Added tag(s) pending. -- 1026980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969697: marked as done (autogen: please upgrade to guile-3.0 soon, if feasible)
Your message dated Tue, 27 Dec 2022 13:49:14 + with message-id and subject line Bug#969697: fixed in autogen 1:5.19.96-3 has caused the Debian Bug report #969697, regarding autogen: please upgrade to guile-3.0 soon, if feasible 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.) -- 969697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: autogen Severity: wishlist Please migrate to guile-3.0 as soon as it's feasible. If we can, I'd like to have the option to drop guile-2.2 from bullseye, so that we won't have to maintain two versions throughout that release. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 --- End Message --- --- Begin Message --- Source: autogen Source-Version: 1:5.19.96-3 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of autogen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated autogen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 27 Dec 2022 14:17:07 +0100 Source: autogen Architecture: source Version: 1:5.19.96-3 Distribution: experimental Urgency: low Maintainer: Andreas Metzler Changed-By: Andreas Metzler Closes: 969697 Changes: autogen (1:5.19.96-3) experimental; urgency=low . * Run wrap-and-sort -ast. * Build against guile-3.0 (Closes: #969697) * Uploaded only to clean-up noise for guile-3.0 transition be closing experimental-only bug. Checksums-Sha1: 1022c60cff7f521df7dc0bd6baf8fe20179477fa 2400 autogen_5.19.96-3.dsc 85b5a47fab5e45c713c7eef172dea62ef5d18366 22356 autogen_5.19.96-3.debian.tar.xz Checksums-Sha256: 7ff38d1a4cfc1f95554711b74d5ac4ce11cdff027e534604a0afcc230b79f140 2400 autogen_5.19.96-3.dsc 62d8a5d7e38206c7b0a3171e4242e981cd38fb9b25bf2d25a6cd7f36f8f7eca1 22356 autogen_5.19.96-3.debian.tar.xz Files: 6b8777ef1403838f9c81c9273110804c 2400 devel optional autogen_5.19.96-3.dsc 90a494ff507d5a6bb80548a18e2e771d 22356 devel optional autogen_5.19.96-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmOq8yIACgkQpU8BhUOC FIQOEBAAgUz33EhvLFUqbN+m3FIfe2YhakC083IxZYtCoyt0uyoF3/m3pgJzij67 q4BLNiFe2rGJhwZokjHQoOCU3ZkP5YFM7yGRHRH8c7RT1eFjUYgmLi4+Z/I8yScI aIOOe+AwhAcZYJLm7gu7uH7dBHvoE251SdpJzAujdfVBJa7l9Cqw6ze+m/1sPzeR tSscVl+t1rnEEg+SUABJ2VYZJ/VjzhYJDyvpNQsKxB6F5G91bvtBPBkHA4fMbvj7 vysv7foKTirjo781bNuwNMMQr0IfRsXGhyravxhAzkUDYy0O6e0aEH9nDhgsF6Sm uE5q/iG8OkEOE3OcsmIYrHg6hxYO681CuHgqEWn01SCsgN3hEFveg5e/HchkDUXb gHcPkM0mNstnKSKabfFlB31/VomaNoh/v6Rn/xhKibG5F4WY+lHeFAdFDSzqYoOp svpHEaXjucg4qxtErptlbUcB+obzEjJO4qTs5co1tS/mpXA3tg1+5hvQO7db/Nm4 dQuLFJRVaQl/Rteq/ptEYtOSH3p517K/rXyN8fUAXShGWbKo3qksa2mSC3hXSgkP KRItzzqN0m+EFnIXr5oz7m8bZDDePmQDvjroUxx6uOKsOf+1ZoIn4XqJkvtJYmVQ mUWzUHZoEhGP2fv7JsHgrAlHNpG4Y4+pnnn0QOmr67EwxibBNTI= =g76S -END PGP SIGNATURE End Message ---
