Bug#1026627: marked as done (ruby-omniauth-twitter: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:)
Your message dated Sun, 22 Jan 2023 07:51:04 + with message-id and subject line Bug#1026627: fixed in ruby-omniauth 2.1.1-1 has caused the Debian Bug report #1026627, regarding ruby-omniauth-twitter: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: 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.) -- 1026627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-omniauth-twitter Version: 1.4.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): > NoMethodError: >undefined method `[]' for nil:NilClass > > @env['SCRIPT_NAME'] || '' > ^^^ > # > /usr/share/rubygems-integration/all/gems/omniauth-2.1.0/lib/omniauth/strategy.rb:501:in > `script_name' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.1.0/lib/omniauth/strategy.rb:450:in > `callback_path' > # ./lib/omniauth/strategies/twitter.rb:78:in `callback_path' > # ./spec/omniauth/strategies/twitter_spec.rb:171:in `block (4 levels) in > ' > > Finished in 0.05119 seconds (files took 0.93798 seconds to load) > 21 examples, 1 failure > > Failed examples: > > rspec ./spec/omniauth/strategies/twitter_spec.rb:170 # > OmniAuth::Strategies::Twitter request_phase with no callback_url set should > return the default callback_path value > > Coverage report generated for RSpec to /<>/coverage. 49 / 51 LOC > (96.08%) covered. > Stopped processing SimpleCov as a previous error not related to SimpleCov has > been detected > /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 > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2022/12/20/ruby-omniauth-twitter_1.4.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=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=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: ruby-omniauth Source-Version: 2.1.1-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of ruby-omniauth, 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. Nilesh Patra (supplier of updated ruby-omniauth package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 22 Jan 2023 13:00:49 +0530 Source: ruby-omniauth Architecture: source Version: 2.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Nilesh Patra Closes: 1026627 Changes: ruby-omniauth (2.1.1-1) unstable; urgency=medium . [ Pirate Praveen ] * Team Upload. * Update minimum version of ruby-rack to 2.2.3 . [ Debian Janitor ] * Set field Upstream-Contact in debian/copyright. * Set upstream metadata fields: Security-Contact. * Remove obsolete fields Contact, Name from debian/upstream/metadata (already present in machine-readable debian/copyright). . [ Nilesh Patra ] * New upstream version 2.1.1 (Closes: #1026627) * Bump Standards-Version to 4.6.2 (no changes needed) Checksums-Sha1: ca523b62f4fe97661cfd0a38f1d85c2d13424d05 1587
Bug#1005634: marked as done (installing symlink 'vendor/assets/javascripts/leaflet-src.js.erb' pointing to parent path /usr/share/javascript/leaflet/leaflet.js [...] is not allowed)
Your message dated Sun, 22 Jan 2023 07:50:55 + with message-id and subject line Bug#1005634: fixed in ruby-leaflet-rails 1.6.0+dfsg-3 has caused the Debian Bug report #1005634, regarding installing symlink 'vendor/assets/javascripts/leaflet-src.js.erb' pointing to parent path /usr/share/javascript/leaflet/leaflet.js [...] is not allowed 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.) -- 1005634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-leaflet-rails Version: 1.6.0+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 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 '/<>' > mkdir -p vendor/assets/javascripts > ln -sf /usr/share/javascript/leaflet/leaflet.js > vendor/assets/javascripts/leaflet-src.js.erb > dh_auto_build > dh_ruby --build >dh_ruby --build > make[1]: Leaving directory '/<>' >dh_auto_test -O--buildsystem=ruby > dh_ruby --test >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=ruby >dh_prep -O--buildsystem=ruby >dh_auto_install --destdir=debian/ruby-leaflet-rails/ -O--buildsystem=ruby > dh_ruby --install > /<>/ruby-leaflet-rails-1.6.0\+dfsg/debian/ruby-leaflet-rails >dh_ruby --install > /usr/bin/ruby2.7 -S gem build --config-file /dev/null --verbose > /tmp/d20220212-1230077-skv39d/gemspec > Failed to load /dev/null because it doesn't contain valid YAML hash > WARNING: license value 'BSD' is invalid. Use a license identifier from > http://spdx.org/licenses or 'Nonstandard' for a nonstandard license. > Did you mean '0BSD'? > WARNING: no homepage specified > WARNING: vendor/assets/javascripts/leaflet-src.js.erb is a symlink, which is > not supported on all platforms > WARNING: open-ended dependency on rails (>= 4.2.0) is not recommended > if rails is semantically versioned, use: > add_runtime_dependency 'rails', '~> 4.2', '>= 4.2.0' > WARNING: open-ended dependency on simplecov-rcov (>= 0, development) is not > recommended > use a bounded requirement, such as '~> x.y' > WARNING: See https://guides.rubygems.org/specification-reference/ for help > Successfully built RubyGem > Name: leaflet-rails > Version: 1.6.0 > File: leaflet-rails-1.6.0.gem > /usr/bin/ruby2.7 -S gem install --config-file /dev/null --verbose --local > --verbose --no-document --ignore-dependencies --install-dir > debian/ruby-leaflet-rails/usr/share/rubygems-integration/all > /tmp/d20220212-1230077-skv39d/leaflet-rails-1.6.0.gem > Failed to load /dev/null because it doesn't contain valid YAML hash > ERROR: While executing gem ... (Gem::Package::SymlinkError) > installing symlink 'vendor/assets/javascripts/leaflet-src.js.erb' > pointing to parent path /usr/share/javascript/leaflet/leaflet.js of > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0 > is not allowed > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/lib/leaflet-rails.rb > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/lib/leaflet-rails/version.rb > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/lib/leaflet-rails/view_helpers.rb > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/vendor/assets/images/layers-2x.png > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/vendor/assets/images/layers.png > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/vendor/assets/images/marker-icon-2x.png > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/vendor/assets/images/marker-icon.png > /<>/debian/ruby-leaflet-rails/usr/share/rubygems-integration/all/gems/leaflet-rails-1.6.0/vendor/assets/images/marker-shadow.png > /usr/lib/ruby/vendor_ruby/gem2deb.rb:54:in `run': /usr/bin/ruby2.7 -S gem > install --config-file /dev/null --verbose --local --verbose --no-document > --ignore-dependencies --install-dir > debian/ruby-leaflet-rails/usr/share/rubygems-integration/all > /tmp/d20220212-1230077-skv39d/leaflet-rails-1.6.0.gem (Gem2Deb::CommandFailed) > from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:212:in `run_gem' > from
Bug#1028451: 2nd DisplayPort doesn't get video
Hi Didier, On Sat, Jan 21, 2023 at 05:43:03PM +0100, Didier 'OdyX' Raboud wrote: > Control: tags -1 +patch > > Le vendredi, 20 janvier 2023, 21.38:42 h CET Salvatore Bonaccorso a écrit : > > There is the patchset currently asked for inclusion at > > https://lore.kernel.org/stable/20230119235200.441386-1-harry.wentl...@amd.co > > m/T/#m3b5b3616eac750cfd7c9bd00ac1cf95006a6aeec which is for addressing this > > issue. > > Indeed. I can confirm this fixes my issue with the attached patch on top of > 6.1.7-1, which is all 4 patches from : > https://gitlab.freedesktop.org/hwentland/linux/-/commits/mst_regression_6.1 > aka: > https://gitlab.freedesktop.org/hwentland/linux/-/compare/ > 21e996306a6afaae88295858de0ffb8955173a15...1521e9dcb431f31c15a0256cb619b09cca3efc4e? > from_project_id=12209=false > > I hope this can either get to 6.1 stable, or be backported / carried over by > Debian! Happy to MR this if it makes sense! perfect thanks for testing! You could add an explicit Tested-by on the patch sumission thread. I expect the patches to be reviewed and acked soon, then they should tickle in in 6.1.y. Will pick those up with our packaging workflow. Regards, Salvatore
Processed: user debian-pyt...@lists.debian.org, usertagging 1028697, tagging 1028697 ...
Processing commands for cont...@bugs.debian.org: > user debian-pyt...@lists.debian.org Setting user to debian-pyt...@lists.debian.org (was p...@debian.org). > usertags 1028697 + python3.11 There were no usertags set. Usertags are now: python3.11. > tags 1028697 + patch Bug #1028697 [src:pydispatcher] pydispatcher: FTBFS: TypeError: HTMLDoc.heading() takes from 2 to 3 positional arguments but 5 were given Added tag(s) patch. > forwarded 1028697 https://github.com/mcfletch/pydispatcher/pull/3 Bug #1028697 [src:pydispatcher] pydispatcher: FTBFS: TypeError: HTMLDoc.heading() takes from 2 to 3 positional arguments but 5 were given Set Bug forwarded-to-address to 'https://github.com/mcfletch/pydispatcher/pull/3'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1005634 marked as pending in ruby-leaflet-rails
Processing control commands: > tag -1 pending Bug #1005634 [src:ruby-leaflet-rails] installing symlink 'vendor/assets/javascripts/leaflet-src.js.erb' pointing to parent path /usr/share/javascript/leaflet/leaflet.js [...] is not allowed Added tag(s) pending. -- 1005634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005634: marked as pending in ruby-leaflet-rails
Control: tag -1 pending Hello, Bug #1005634 in ruby-leaflet-rails 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-leaflet-rails/-/commit/b4c8407616018a3cec32852087f0c0c075d355cc Copy assets instead of symlink (Closes: #1005634) (this message was generated automatically) -- Greetings https://bugs.debian.org/1005634
Processed: reassign
Processing commands for cont...@bugs.debian.org: > reassign 1026627 ruby-omniauth 2.1.0-1 Bug #1026627 [src:ruby-omniauth-twitter] ruby-omniauth-twitter: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: Bug reassigned from package 'src:ruby-omniauth-twitter' to 'ruby-omniauth'. No longer marked as found in versions ruby-omniauth-twitter/1.4.0-1. Ignoring request to alter fixed versions of bug #1026627 to the same values previously set Bug #1026627 [ruby-omniauth] ruby-omniauth-twitter: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: Marked as found in versions ruby-omniauth/2.1.0-1. > stop Stopping processing here. Please contact me if you need assistance. -- 1026627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029292: lomiri-greeter: Depends: lomiri-system-compositor but it is not installable
On 23/01/20 08:54PM, Mike Gabriel wrote: > Hi Adrian, hi Marius, > > On Fr 20 Jan 2023 19:48:19 CET, Adrian Bunk wrote: > > > Package: lomiri-greeter > > Version: 0.1~git20230111.ba0fc6a-4 > > Severity: serious > > > > The following packages have unmet dependencies: > > lomiri-greeter : Depends: lomiri-system-compositor but it is not > > installable > > > Thanks Adrian for spotting this. > > @Marius: is it more realistic to get lomiri-system-compositor operate on top > of Miral or should we drop lomiri-greeter from the lomiri bin:pkg for a > while until we can bring lomiri-system-compositor to Debian? > > @Marius: Or might it be legitimate to simply drop l-s-c from Depends: of > lomiri-greeter. Sorry Mike for the dual email, but forgot to hit reply-all We can simply just drop l-s-c as its not needed to run a greeter session. But it will be needed for a mobile style login greeter, but thats not needed for now. Thanks! Marius > > Request for feedback! > > Thanks, > Mike > -- > > DAS-NETZWERKTEAM > c\o Technik- und ?kologiezentrum Eckernf?rde > Mike Gabriel, Marienthaler Str. 17, 24340 Eckernf?rde > mobile: +49 (1520) 1976 148 > landline: +49 (4351) 850 8940 > > GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 > mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de >
Bug#1026631: marked as done (ruby-scientist: FTBFS: ERROR: Test "ruby3.1" failed: debian/ruby-tests.rb:3:in `': Could not run tests (RuntimeError))
Your message dated Sun, 22 Jan 2023 07:23:16 + with message-id and subject line Bug#1026631: fixed in ruby-scientist 1.6.3-1 has caused the Debian Bug report #1026631, regarding ruby-scientist: FTBFS: ERROR: Test "ruby3.1" failed: debian/ruby-tests.rb:3:in `': Could not run tests (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.) -- 1026631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-scientist Version: 1.6.0-2 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/ruby-tests.rb:3:in `': Could not run tests (RuntimeError) > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2022/12/20/ruby-scientist_1.6.0-2_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=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=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: ruby-scientist Source-Version: 1.6.3-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of ruby-scientist, 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. Nilesh Patra (supplier of updated ruby-scientist package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 22 Jan 2023 12:34:52 +0530 Source: ruby-scientist Architecture: source Version: 1.6.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Nilesh Patra Closes: 1026631 Changes: ruby-scientist (1.6.3-1) unstable; urgency=medium . [ Debian Janitor ] * Team Upload. * Apply multi-arch hints. + ruby-scientist + Add Multi-Arch: foreign. . [ Nilesh Patra ] * New upstream version 1.6.3 (Closes: #1026631) * Bump Standards-Version to 4.6.2 (no changes needed) Checksums-Sha1: 9a714d16a895fd574bc0414763dd2aaed8e5e15f 1473 ruby-scientist_1.6.3-1.dsc ff57c70f2c4fa284a9d0abf647c7bd884a1817bc 20965 ruby-scientist_1.6.3.orig.tar.gz 70a1e54b711c426563b99e271b121fd1a3b9235a 3340 ruby-scientist_1.6.3-1.debian.tar.xz e1a182f4808c9446409472c9546fa4a1c5eccbca 9092 ruby-scientist_1.6.3-1_amd64.buildinfo Checksums-Sha256: 71cccba3d2367d258fb0c7fb7b62dc60706d84eca94d4a2f85ce3d379e134e54 1473 ruby-scientist_1.6.3-1.dsc daffbef533c441ed90ff1efc7f95ee0a0f9853e028711070835d4d3d7ffb29de 20965 ruby-scientist_1.6.3.orig.tar.gz 2c34cf8ff88124545612ce7fdfa4756f1965e3d9a312bc053e6fc45ffb8814b2 3340 ruby-scientist_1.6.3-1.debian.tar.xz b613e946a6a79e8f604eba1f58d8ee65641f5549fd55b5b0e8b85552d637759c 9092 ruby-scientist_1.6.3-1_amd64.buildinfo Files: e7fab0f5ee9ec066378398bd45b11807 1473 ruby optional ruby-scientist_1.6.3-1.dsc 7c105835ad9bfaa7b7ec399ce94b9d2d 20965 ruby optional ruby-scientist_1.6.3.orig.tar.gz 97365c448a3db74f7f85708cf20cf36e 3340 ruby optional ruby-scientist_1.6.3-1.debian.tar.xz 3bca876a52a049baa561b95f71c0eeb8 9092 ruby optional ruby-scientist_1.6.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY8zg3QAKCRAqJ5BL1yQ+ 2oFoAP45JsjTYCjJF5ang0UZRdxAtDaT78uPg5ULQ6L3WTGOQgD7BR7zrMGEp5wr lGmPx8O97kr0I/ZfGvWrQswnJo6kUgI= =He2G -END PGP SIGNATURE End Message ---
Processed: fix+close
Processing commands for cont...@bugs.debian.org: > fixed 1027348 0.17.1-2 Bug #1027348 [src:ruby-gitlab-labkit] ruby-gitlab-labkit: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'actionpack' (>= 5.0.0, < 6.1.0) among 131 total gem(s) (Gem::MissingSpecError) Marked as fixed in versions ruby-gitlab-labkit/0.17.1-2. > close 1027348 Bug #1027348 [src:ruby-gitlab-labkit] ruby-gitlab-labkit: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'actionpack' (>= 5.0.0, < 6.1.0) among 131 total gem(s) (Gem::MissingSpecError) Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1027348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1027192 1029248
Processing commands for cont...@bugs.debian.org: > forcemerge 1027192 1029248 Bug #1027192 [src:binoculars] binoculars: autopkgtest fail with numpy/1.24.1 Bug #1029248 [src:binoculars] binoculars: FTBFS: AttributeError: module 'numpy' has no attribute 'bool'. Unable to parse configuration option 'maskmatrix'. The error can quite likely be solved by modifying the option in the configuration file. Added tag(s) patch. Bug #1027192 [src:binoculars] binoculars: autopkgtest fail with numpy/1.24.1 Added tag(s) bookworm and sid. Merged 1027192 1029248 > thanks Stopping processing here. Please contact me if you need assistance. -- 1027192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027192 1029248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: scikit-learn: FTBFS: build-dependency not installable: python-numpy-doc
Processing control commands: > tags -1 patch Bug #1029249 [src:scikit-learn] scikit-learn: FTBFS: build-dependency not installable: python-numpy-doc Added tag(s) patch. -- 1029249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029249: scikit-learn: FTBFS: build-dependency not installable: python-numpy-doc
Control: tags -1 patch A fix has been committed in git: https://salsa.debian.org/science-team/scikit-learn/-/commit/2f2538d7538f693f3600713fc816c07f8a0990da Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1029291: marked as done (qtmir-tests and qml-module-qtmir both ship qtmir-demo-client.desktop)
Your message dated Sun, 22 Jan 2023 06:19:37 + with message-id and subject line Bug#1029291: fixed in qtmir 0.8.0~git20230115.30c2337-3 has caused the Debian Bug report #1029291, regarding qtmir-tests and qml-module-qtmir both ship qtmir-demo-client.desktop 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.) -- 1029291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qtmir Version: 0.8.0~git20230115.30c2337-2 Severity: serious Control: affects -1 qtmir-tests qml-module-qtmir https://piuparts.debian.org/sid/fail/qtmir-tests_0.8.0~git20230115.30c2337-2.log ... Unpacking qtmir-tests (0.8.0~git20230115.30c2337-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-4YfO5r/253-qtmir-tests_0.8.0~git20230115.30c2337-2_amd64.deb (--unpack): trying to overwrite '/usr/share/applications/qtmir-demo-client.desktop', which is also in package qml-module-qtmir:amd64 0.8.0~git20230115.30c2337-2 Errors were encountered while processing: /tmp/apt-dpkg-install-4YfO5r/253-qtmir-tests_0.8.0~git20230115.30c2337-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- End Message --- --- Begin Message --- Source: qtmir Source-Version: 0.8.0~git20230115.30c2337-3 Done: Marius Gripsgard We believe that the bug you reported is fixed in the latest version of qtmir, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gripsgard (supplier of updated qtmir package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Jan 2023 05:54:37 + Source: qtmir Built-For-Profiles: noudeb Architecture: source Version: 0.8.0~git20230115.30c2337-3 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Marius Gripsgard Closes: 1029291 Changes: qtmir (0.8.0~git20230115.30c2337-3) unstable; urgency=medium . * debian/.install: Spesify that we only want xwayland desktop & icon file in qml-module-qtmir (closes: #1029291) Checksums-Sha1: 426914a52924d10fe50af14e1a8618c79aab989c 3349 qtmir_0.8.0~git20230115.30c2337-3.dsc c0c517a719036e702696f693b4ded52d4deb68e1 252072 qtmir_0.8.0~git20230115.30c2337.orig.tar.xz 88c0ed38c58f52ef5150bb4df9bfb4687baa2ab8 40456 qtmir_0.8.0~git20230115.30c2337-3.debian.tar.xz d2ae1d6390d3070b239dc6f3b1c4f82eb661990c 21942 qtmir_0.8.0~git20230115.30c2337-3_source.buildinfo Checksums-Sha256: 1121afd96b9fbde31cb8e48c06c9e221ad03a4b8e69c6ec1b01d535a31b98f35 3349 qtmir_0.8.0~git20230115.30c2337-3.dsc 141f4dc53257d10e71180d6b15936d709d29d824e8bbe7e2e34cd70a3e732d8f 252072 qtmir_0.8.0~git20230115.30c2337.orig.tar.xz 9514be9648d68543f41679b044c2c4b5c73b1e2f60731361bd43152e521efeed 40456 qtmir_0.8.0~git20230115.30c2337-3.debian.tar.xz 4d3f7530089856976c06332cc793f92f35df15c6512bd9f51d4806957ff9e905 21942 qtmir_0.8.0~git20230115.30c2337-3_source.buildinfo Files: 52a16c40929a81bca1c056723a7c48e1 3349 libs optional qtmir_0.8.0~git20230115.30c2337-3.dsc 5a4b3cc79b11ab006ab089fd6077bc9e 252072 libs optional qtmir_0.8.0~git20230115.30c2337.orig.tar.xz f92dcd22c9918c46bc47a9b0f5f173ec 40456 libs optional qtmir_0.8.0~git20230115.30c2337-3.debian.tar.xz 6c6d8d0e8c9092930f4d04e41302dbdb 21942 libs optional qtmir_0.8.0~git20230115.30c2337-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEm65oPpnDJVLXb56DuvnOw/aSJ4kFAmPM0FcTHG1hcml1c0B1 YnBvcnRzLmNvbQAKCRC6+c7D9pIniaxQEAChYutZzxOPDpelmHab04E90N5Y1fSt G7cMW336chOoMwjZEhuWqbdjn83NG8BmcjUz1q/uUCk5bq1Mxy+q738Oer3bnoHi 7kCrgAyFyZ24r/WirXF5DtVRTp2prHFerDxWMeFbrisjhlDDp/Wges3S5zjYWfwt pmorBer3j4CE8ihxWGo73RDWM8FlvqulFk2q5YG2nmE3zXyYQC8rjUSZ+JvCQxyw h3MIRa3yw73otaL4cPo+nk8a2/addPJpiK6ZIFfNt+GLrasU0Su+G82V/GrGUOME Vd15JDgCfM89xFTvXuwCdHgivtBxh30qyTcbEQq86R4ZaoTHZB7PmXV13n6q66Oq VhJU6+6tmFQ5aOTkcj/Z9eNEEcwgacvr06xri+asQ+v3UJUTuOKg/XVwkz55DlpD DwFVf4UZ5SV9wX+EwARLXaKihyyQ/s7Uznab8U9MsOCpnE/hJBD2haG5MHZYeCuZ iYEHZb/PfQXEHOD479RoZFdw//jgFAitbFT3CVqF7doRAD2Ylnvo5RdCRd+dlIfX UGteRO9EENehrD29EvsdCN6TnYZnru9YmJ1+NcrosCAqX4DplzdSN1ujO+wz4eWC
Bug#1027352: marked as done (ruby-activerecord-import: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such f
Your message dated Sun, 22 Jan 2023 06:08:45 + with message-id and subject line Bug#1027352: fixed in ruby-activerecord-import 1.4.1-1 has caused the Debian Bug report #1027352, regarding ruby-activerecord-import: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such file -- mocha/mini_test (LoadError) 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.) -- 1027352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-activerecord-import Version: 1.4.0-0.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221230 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is likely due to the upgrade of mocha. See https://lists.debian.org/debian-ruby/2022/12/msg00064.html Relevant part (hopefully): > :85:in > `require': cannot load such file -- mocha/mini_test (LoadError) > from > :85:in > `require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in > `block in require' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in > `load_dependency' > from > /usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in > `require' > from /<>/test/test_helper.rb:25:in `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/import_test.rb:1: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 > `' > rake aborted! > Command failed with status (1) > > Tasks: TOP => default => test:sqlite3 > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2022/12/30/ruby-activerecord-import_1.4.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-20221230;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221230=lu...@debian.org=1=1=1=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: ruby-activerecord-import Source-Version: 1.4.1-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of ruby-activerecord-import, 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. Nilesh Patra (supplier of updated ruby-activerecord-import package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 22 Jan 2023 11:10:59 +0530 Source: ruby-activerecord-import Architecture: source Version: 1.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Nilesh Patra Closes: 1027352 Changes: ruby-activerecord-import (1.4.1-1) unstable; urgency=medium . * Team Upload. * Add patch to fix FTBFS (Closes: #1027352) * New upstream version 1.4.1 * Bump Standards-Version to 4.6.2 (no changes needed) * Refresh/Re-diff patches Checksums-Sha1: 0d6b15364c481cb17f5f4bcaaf6b1afb7fee1cb1 1760 ruby-activerecord-import_1.4.1-1.dsc b44d8ef1db23745fb79697dce358a1876eef1355 64960 ruby-activerecord-import_1.4.1.orig.tar.gz
Processed: Bug#1027352 marked as pending in ruby-activerecord-import
Processing control commands: > tag -1 pending Bug #1027352 [src:ruby-activerecord-import] ruby-activerecord-import: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such file -- mocha/mini_test (LoadError) Added tag(s) pending. -- 1027352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027352: marked as pending in ruby-activerecord-import
Control: tag -1 pending Hello, Bug #1027352 in ruby-activerecord-import 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-activerecord-import/-/commit/69cb0d9ff3fb9d3a348b41d43d1aeffc09b1e9e3 Add patch to fix FTBFS (Closes: #1027352) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027352
Bug#1029174: marked as done (dhcpcd-base: Brakes networking completely)
Your message dated Sun, 22 Jan 2023 07:40:49 +0200
with message-id
and subject line Re: Bug#1029176: please check dhcpcd 9.4.1-14 in unstable
has caused the Debian Bug report #1029174,
regarding dhcpcd-base: Brakes networking completely
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.)
--
1029174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dhcpcd-base
Version: 9.4.1-13
Severity: grave
Justification: renders package unusable
When this version is installed, all networking is broken, e.g.
root@twentytwo:~# LC_ALL=C ping lwn.net
ping: lwn.net: Temporary failure in name resolution
I cannot access *any* outside resource. No IP, no ssh, no ping, ..
Additionally, comands involving network state take several minutes,
i.e. running into timeouts. E.g.
systemctl restart networking
Or shutdown takes several minutes (for each interface) before
completion.
If I strace such a command, I see:
access("/run/network/ifstate.enp3s0", R_OK) = 0
openat(AT_FDCWD, "/run/network/ifstate.enp3s0",
O_RDWR|O_CREAT|O_APPEND|O_CLOEXEC, 0666) = 3
fcntl(3, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = -1
EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
write(2, "ifdown: ", 8ifdown: ) = 8
write(2, "waiting for lock on /run/network"..., 47waiting for lock on
/run/network/ifstate.enp3s0) = 47
write(2, "\n", 1
) = 1
fcntl(3, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}
And there it hangs. (I did not search if this is the only place for
hangs, but it was the first).
Downgrading to 9.4.1-11 fixes the problem, i.e. the machine behaves
normally after reboot.
This is reproducible, i.e. upgrading to -13 and rebooting and the
broken network is back; downgrading and rebooting and the network is
fine again.
Please tell me which data you need to further boil this down and I can
provide it.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dhcpcd-base depends on:
ii adduser 3.130
ii libc6 2.36-8
ii libudev1 252.4-1
dhcpcd-base recommends no packages.
dhcpcd-base suggests no packages.
-- no debconf information
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Fri, Jan 20, 2023 at 5:11 PM Martin-Éric Racine
wrote:
>
> On Thu, Jan 19, 2023 at 10:25 PM Beat Bolli wrote:
> > On 19.01.23 16:35, Martin-Éric Racine wrote:
> > > We've just pushed dhcpcd 9.4.1-14 into unstable. Can you please check
> > > whether that fixes it?
> >
> > Indeed, this new version works.
>
> Marking FIXED as of 9.4.1-14 . I'll wait until it has trickled down to
> Testing before closing.
Closing.
Martin-Éric--- End Message ---
Processed: tagging 1027236 ...
Processing commands for cont...@bugs.debian.org: > tags 1027236 + fixed-upstream Bug #1027236 [src:pyemd] pyemd: autopkgtest fail with numpy/1.24.1 Added tag(s) fixed-upstream. > forwarded 1027236 > https://github.com/wmayner/pyemd/commit/34631658ae0cc555001b692623c23c02ed8d5611 Bug #1027236 [src:pyemd] pyemd: autopkgtest fail with numpy/1.24.1 Set Bug forwarded-to-address to 'https://github.com/wmayner/pyemd/commit/34631658ae0cc555001b692623c23c02ed8d5611'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1028886 ...
Processing commands for cont...@bugs.debian.org:
> tags 1028886 + fixed-upstream
Bug #1028886 [src:pyemd] pyemd: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Added tag(s) fixed-upstream.
> forwarded 1028886
> https://github.com/wmayner/pyemd/commit/34631658ae0cc555001b692623c23c02ed8d5611
Bug #1028886 [src:pyemd] pyemd: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/wmayner/pyemd/commit/34631658ae0cc555001b692623c23c02ed8d5611'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029380: marked as done (sra-toolkit: Has hard-coded dependency on obsolete libncbi-wvdb2 (>= 2.10.6+dfsg-3~),)
Your message dated Sat, 21 Jan 2023 22:24:33 -0500
with message-id
and subject line Re: Bug#1029380: sra-toolkit: Has hard-coded dependency on
obsolete libncbi-wvdb2 (>= 2.10.6+dfsg-3~),
has caused the Debian Bug report #1029380,
regarding sra-toolkit: Has hard-coded dependency on obsolete libncbi-wvdb2 (>=
2.10.6+dfsg-3~),
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1029380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sra-toolkit
Version: 2.11.3+dfsg-1
Severity: serious
sra-toolkit has a manually Depends: libncbi-wvdb2 (>= 2.10.6+dfsg-3~)
But libncbi-wvdb2 is no longer built from source.
Generally, you should let ${shlibs:Depends} add the dependency so that
a simple rebuild can handle many soname bump transitions.
Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 3.0.3+dfsg-2
Jeremy Bicha writes:
> Generally, you should let ${shlibs:Depends} add the dependency so that
> a simple rebuild can handle many soname bump transitions.
I generally do. ;-) However, this hint was historically necessary to
pick up a change needed for https://bugs.debian.org/961347 . At any
rate, I already dropped it for 3.x, whose FTBFS I'll address within the
next day or two.
Thanks for the report!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu--- End Message ---
Bug#1028871: djangorestframework: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Source: djangorestframework
Followup-For: Bug #1028871
In pygments (an upstream dependency) version 2.13.0, HTML rendering was
updated[1] to use inline elements to encapsulate whitespace.
To address some resulting test failures, upstream pinned[2] to pygments version
2.12.0 recently.
Currently Debian does not version pin the pygments dependency for
djangorestframework.
A fix could add version pinning, or alternatively apply a patch that extracts
text contents from the received HTML document in the relevant test case(s);
something like:
import xml.etree.ElementTree as ET
doc = ET.fromstring('hello there')
"".join(doc.text) # hello there
[1] -
https://github.com/pygments/pygments/commit/147b22face65617514ccfa8512c6b097b07cad4c
[2] - https://github.com/encode/django-rest-framework/pull/8530
Bug#1026602: marked as done (python-unicodecsv: FTBFS: AssertionError: [['ab\x00c']] != None)
Your message dated Sun, 22 Jan 2023 00:41:42 + with message-id and subject line Bug#1026602: fixed in python-unicodecsv 0.14.1-6 has caused the Debian Bug report #1026602, regarding python-unicodecsv: FTBFS: AssertionError: [['ab\x00c']] != None 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.) -- 1026602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-unicodecsv Version: 0.14.1-5 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 --with python3 >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 > creating /<>/.pybuild/cpython3_3.11_unicodecsv/build/unicodecsv > copying unicodecsv/__init__.py -> > /<>/.pybuild/cpython3_3.11_unicodecsv/build/unicodecsv > copying unicodecsv/test.py -> > /<>/.pybuild/cpython3_3.11_unicodecsv/build/unicodecsv > copying unicodecsv/py2.py -> > /<>/.pybuild/cpython3_3.11_unicodecsv/build/unicodecsv > copying unicodecsv/py3.py -> > /<>/.pybuild/cpython3_3.11_unicodecsv/build/unicodecsv > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10_unicodecsv/build/unicodecsv > copying unicodecsv/__init__.py -> > /<>/.pybuild/cpython3_3.10_unicodecsv/build/unicodecsv > copying unicodecsv/test.py -> > /<>/.pybuild/cpython3_3.10_unicodecsv/build/unicodecsv > copying unicodecsv/py2.py -> > /<>/.pybuild/cpython3_3.10_unicodecsv/build/unicodecsv > copying unicodecsv/py3.py -> > /<>/.pybuild/cpython3_3.10_unicodecsv/build/unicodecsv >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py test > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > creating unicodecsv.egg-info > writing unicodecsv.egg-info/PKG-INFO > writing dependency_links to unicodecsv.egg-info/dependency_links.txt > writing top-level names to unicodecsv.egg-info/top_level.txt > writing manifest file 'unicodecsv.egg-info/SOURCES.txt' > reading manifest file 'unicodecsv.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE' > writing manifest file 'unicodecsv.egg-info/SOURCES.txt' > running build_ext > test_char_write (unicodecsv.test.TestArrayWrites) ... ok > test_double_write (unicodecsv.test.TestArrayWrites) ... ok > test_float_write (unicodecsv.test.TestArrayWrites) ... ok > test_int_write (unicodecsv.test.TestArrayWrites) ... ok > test_blankline (unicodecsv.test.TestDialectExcel) ... ok > test_dubious_quote (unicodecsv.test.TestDialectExcel) ... ok > test_empty_fields (unicodecsv.test.TestDialectExcel) ... ok > test_inline_quote (unicodecsv.test.TestDialectExcel) ... ok > test_inline_quotes (unicodecsv.test.TestDialectExcel) ... ok > test_lone_quote (unicodecsv.test.TestDialectExcel) ... ok > test_newlines (unicodecsv.test.TestDialectExcel) ... ok > test_null (unicodecsv.test.TestDialectExcel) ... ok > test_quote_and_quote (unicodecsv.test.TestDialectExcel) ... ok > test_quote_fieldsep (unicodecsv.test.TestDialectExcel) ... ok > test_quoted (unicodecsv.test.TestDialectExcel) ... ok > test_quoted_nl (unicodecsv.test.TestDialectExcel) ... ok > test_quoted_quote (unicodecsv.test.TestDialectExcel) ... ok > test_quoted_quotes (unicodecsv.test.TestDialectExcel) ... ok > test_quotes (unicodecsv.test.TestDialectExcel) ... ok > test_quotes_and_more (unicodecsv.test.TestDialectExcel) ... ok > test_simple (unicodecsv.test.TestDialectExcel) ... ok > test_simple_writer (unicodecsv.test.TestDialectExcel) ... ok > test_single (unicodecsv.test.TestDialectExcel) ... ok > test_single_quoted_quote (unicodecsv.test.TestDialectExcel) ... ok > test_single_writer (unicodecsv.test.TestDialectExcel) ... ok > test_singlequoted (unicodecsv.test.TestDialectExcel) ... ok > test_singlequoted_left_empty
Bug#1029380: sra-toolkit: Has hard-coded dependency on obsolete libncbi-wvdb2 (>= 2.10.6+dfsg-3~),
Package: sra-toolkit
Version: 2.11.3+dfsg-1
Severity: serious
sra-toolkit has a manually Depends: libncbi-wvdb2 (>= 2.10.6+dfsg-3~)
But libncbi-wvdb2 is no longer built from source.
Generally, you should let ${shlibs:Depends} add the dependency so that
a simple rebuild can handle many soname bump transitions.
Thank you,
Jeremy Bicha
Processed: Bug#1026602 marked as pending in python-unicodecsv
Processing control commands: > tag -1 pending Bug #1026602 [src:python-unicodecsv] python-unicodecsv: FTBFS: AssertionError: [['ab\x00c']] != None Added tag(s) pending. -- 1026602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026602: marked as pending in python-unicodecsv
Control: tag -1 pending Hello, Bug #1026602 in python-unicodecsv 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/python-unicodecsv/-/commit/0b389ddfb8a76b37129e682753c58d149133113c fix test for Python 3.11 (Closes: #1026602) thanks to s3v for the right hint (this message was generated automatically) -- Greetings https://bugs.debian.org/1026602
Bug#1028181: marked as pending in runit
Control: tag -1 pending Hello, Bug #1028181 in runit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/runit/-/commit/31798bad784058f891c7102c7091620bb0a4259c runit-init: depends on mount for linux archs add a dependency on mount for linux architectures; it's used by initscripts (but the dependency is in sysvinit-core). For non linux archs the mount bin is shipped by `hurd' and `freebsd-utils' packages that are priority required and essential, so no explicit dependency is needed Closes: #1028181 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028181
Processed: Bug#1028181 marked as pending in runit
Processing control commands: > tag -1 pending Bug #1028181 [runit-init] runit-init makes the system unbootable Added tag(s) pending. -- 1028181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1026493
Processing commands for cont...@bugs.debian.org: > tags 1026493 - pending Bug #1026493 [src:wcc] wcc: FTBFS: elf-sframe.c:526: undefined reference to `sframe_encoder_write' Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028084: guidata FTBFS with Python 3.11 as default version
Source: guidata Followup-For: Bug #1028084 Dear Maintainer, Maybe some good news: It's possible that the Debian janitor has already taken care of the tasks required to fix this failure, if the following analysis is correct: - Upstream version v2.3.1 includes Python 3.11 compatibility[1] - The janitor has upgraded to v2.3.1[2] - A patch-refresh build against v2.3.1 failed[3] due to a python3-spyder bug - The python3-spyder bug[4] has recently been fixed If so, perhaps a refresh of the Salsa CI pipeline and/or re-build of the package may clear the way to close this bug. Thanks, James [1] - https://github.com/PierreRaybaut/guidata/releases/tag/v2.3.1 [2] - https://salsa.debian.org/science-team/guidata/-/commit/40754dac42c30cde0d9a413fd7935dfa9c5346c3 [3] - https://salsa.debian.org/science-team/guidata/-/jobs/3729413#L538 [4] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024008
Bug#1022040: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:42:00 + with message-id and subject line Bug#1029345: Removed package(s) from unstable has caused the Debian Bug report #1022040, regarding Removal notice: obsolete 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.) -- 1022040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-language-haskell-extract Version: 0.2.4-10 Severity: serious I intend to remove this package: * The current version FTBFS and is incompatible with the latest GHC * Seems unmaintained; Last upload almost 10 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.2.4-10+rm Dear submitter, as the package haskell-language-haskell-extract 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/1029345 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#1013775: marked as done (haskell-language-haskell-extract FTBFS: error: Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’)
Your message dated Sat, 21 Jan 2023 22:42:00 +
with message-id
and subject line Bug#1029345: Removed package(s) from unstable
has caused the Debian Bug report #1013775,
regarding haskell-language-haskell-extract FTBFS: error: Couldn't match
expected type ‘Maybe Exp’ with actual type ‘Exp’
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.)
--
1013775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-language-haskell-extract
Version: 0.2.4-10
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-language-haskell-extract=sid
...
src/Language/Haskell/Extract.hs:28:30: error:
• Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’
• In the expression: LitE $ StringL n
In the first argument of ‘TupE’, namely
‘[LitE $ StringL n, VarE $ mkName n]’
In the expression: TupE [LitE $ StringL n, VarE $ mkName n]
|
28 | let makePair n = TupE [ LitE $ StringL n , VarE $ mkName n]
|
src/Language/Haskell/Extract.hs:28:49: error:
• Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’
• In the expression: VarE $ mkName n
In the first argument of ‘TupE’, namely
‘[LitE $ StringL n, VarE $ mkName n]’
In the expression: TupE [LitE $ StringL n, VarE $ mkName n]
|
28 | let makePair n = TupE [ LitE $ StringL n , VarE $ mkName n]
| ^^^
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 707
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.2.4-10+rm
Dear submitter,
as the package haskell-language-haskell-extract 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/1029345
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#1028563: marked as done (nyx: Does not work with python 3.11 anymore)
Your message dated Sat, 21 Jan 2023 22:37:14 +
with message-id
and subject line Bug#1028563: fixed in nyx 2.1.0-2.2
has caused the Debian Bug report #1028563,
regarding nyx: Does not work with python 3.11 anymore
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.)
--
1028563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nyx
Version: 2.1.0-2.1
Severity: important
X-Debbugs-Cc: bts.debian@schaefer-home.eu
Hi,
I just installed python 3.11, and now I get teh follwoing when starting
nyx:
Traceback (most recent call last):
File "/usr/bin/nyx", line 33, in
sys.exit(load_entry_point('nyx==2.1.0', 'console_scripts', 'nyx')())
^^
File "/usr/lib/python3/dist-packages/nyx/__init__.py", line 176, in main
nyx.starter.main()
File "/usr/lib/python3/dist-packages/stem/util/conf.py", line 288, in wrapped
if 'config' in inspect.getargspec(func).args:
^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean:
'getargs'?
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_GB:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nyx depends on:
ii python33.11.1-1
ii python3-pkg-resources 65.6.3-1
ii python3-stem 1.8.1-1.1
nyx recommends no packages.
Versions of packages nyx suggests:
ii tor 0.4.7.12-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nyx
Source-Version: 2.1.0-2.2
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
nyx, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated nyx package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 22 Jan 2023 03:31:29 +0530
Source: nyx
Architecture: source
Version: 2.1.0-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli
Changed-By: Nilesh Patra
Closes: 1028563
Changes:
nyx (2.1.0-2.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Add patch to fix fallout with python 3.11 (Closes: #1028563)
Checksums-Sha1:
beb9637a47495b03dc9456cc7c25b1ab0100bcb1 1376 nyx_2.1.0-2.2.dsc
55cb3057003fc4f971b4ced59d9a721cd196c3f7 8732 nyx_2.1.0-2.2.debian.tar.xz
a14282b281a32b91b128d3c159d3614b58bf1a9a 5829 nyx_2.1.0-2.2_amd64.buildinfo
Checksums-Sha256:
a7dc99b241e3f4ecde17adf166bedca3acd08056359803a44fda6c774d481c33 1376
nyx_2.1.0-2.2.dsc
ac3d6960c8b87974a98ca2e26866046f77daadbdfc84a66142c4cd147024827a 8732
nyx_2.1.0-2.2.debian.tar.xz
f923aa672a30f7ee3e8ecf9eb1bcc4588eb3e910cd218d91b0c133e8e234117e 5829
nyx_2.1.0-2.2_amd64.buildinfo
Files:
1a8494b5bcfcac0da4a6a31c52972f32 1376 comm optional nyx_2.1.0-2.2.dsc
eadae63938286cfdea77efc8dad7d789 8732 comm optional nyx_2.1.0-2.2.debian.tar.xz
0cf374521a66720b02eb0afd4cf72289 5829 comm optional
nyx_2.1.0-2.2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY8xhXwAKCRAqJ5BL1yQ+
2lwrAP4qDnFE+Qzp4DQmBXKobydTSu4tOHV6tVbqJfcqbK4ndgD/QCvjQ2iS4skq
xMn0Dtuka5PvI38HxXU7lleYjUQzJg4=
=OpI5
-END PGP SIGNATURE End Message ---
Bug#1026383: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:38:15 + with message-id and subject line Bug#1029344: Removed package(s) from unstable has caused the Debian Bug report #1026383, regarding Removal notice: obsolete 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.) -- 1026383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-simple-templates Version: 1.0.0-1 Severity: serious I intend to remove the haskell-simple suite from Debian: * It FTBFS with latest aeson, no fix for more than 1 year (see https://github.com/alevy/simple/issues/26) * Seems unmaintained: Home page doesn't work; Last upload more than 2 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 1.0.0-1+rm Dear submitter, as the package haskell-simple-templates 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/1029344 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#1026382: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:37:48 + with message-id and subject line Bug#1029343: Removed package(s) from unstable has caused the Debian Bug report #1026382, regarding Removal notice: obsolete 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.) -- 1026382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-simple Version: 1.0.0-1 Severity: serious I intend to remove the haskell-simple-* suite from Debian: * It FTBFS with latest aeson, no fix for more than 1 year (see https://github.com/alevy/simple/issues/26) * Seems unmaintained: Home page doesn't work; Last upload more than 2 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 1.0.0-1+rm Dear submitter, as the package haskell-simple 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/1029343 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#1026161: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:35:58 + with message-id and subject line Bug#1029339: Removed package(s) from unstable has caused the Debian Bug report #1026161, regarding Removal notice: obsolete 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.) -- 1026161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-ekg-json Version: 0.1.0.6-7 Severity: serious I intend to remove this package. It's a dependency of haskell-ekg, which we plan on removing (see #1026158). If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.1.0.6-7+rm Dear submitter, as the package haskell-ekg-json 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/1029339 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#1026160: marked as done (Removal notice: unused library)
Your message dated Sat, 21 Jan 2023 22:36:24 + with message-id and subject line Bug#1029338: Removed package(s) from unstable has caused the Debian Bug report #1026160, regarding Removal notice: unused library 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.) -- 1026160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-ekg-core Version: 0.1.1.7-2 Severity: serious I intend to remove this package. It's a dependency of haskell-ekg, which we plan on removing (see #1026158). If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.1.1.7-2+rm Dear submitter, as the package haskell-ekg-core 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/1029338 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#1026158: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:34:38 + with message-id and subject line Bug#1029337: Removed package(s) from unstable has caused the Debian Bug report #1026158, regarding Removal notice: obsolete 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.) -- 1026158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-ekg Version: 0.4.0.15-6 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 4 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.4.0.15-6+rm Dear submitter, as the package haskell-ekg 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/1029337 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#1022910: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:37:16 + with message-id and subject line Bug#1029341: Removed package(s) from unstable has caused the Debian Bug report #1022910, regarding Removal notice: obsolete 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.) -- 1022910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-regex-compat-tdfa Version: 0.95.1.4-8 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 9 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.95.1.4-8+rm Dear submitter, as the package haskell-regex-compat-tdfa 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/1029341 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#1022908: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:36:50 + with message-id and subject line Bug#1029340: Removed package(s) from unstable has caused the Debian Bug report #1022908, regarding Removal notice: obsolete 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.) -- 1022908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-pipes-aeson Version: 0.4.1.8-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 5 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.4.1.8-4+rm Dear submitter, as the package haskell-pipes-aeson 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/1029340 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#1022909: marked as done (Removal notice: obsolete)
Your message dated Sat, 21 Jan 2023 22:36:50 + with message-id and subject line Bug#1029340: Removed package(s) from unstable has caused the Debian Bug report #1022908, regarding Removal notice: obsolete 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.) -- 1022908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-pipes-aeson Version: 0.4.1.8-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 8 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.4.1.8-4+rm Dear submitter, as the package haskell-pipes-aeson 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/1029340 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#1021575: marked as done (haskell-pipes-aeson FTBFS: Couldn't match type)
Your message dated Sat, 21 Jan 2023 22:36:50 + with message-id and subject line Bug#1029340: Removed package(s) from unstable has caused the Debian Bug report #1021575, regarding haskell-pipes-aeson FTBFS: Couldn't match type 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.) -- 1021575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-pipes-aeson Version: 0.4.1.8-4 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/fetch.php?pkg=haskell-pipes-aeson=amd64=0.4.1.8-4%2Bb4=1658618925=0 ... src/Pipes/Aeson/Unchecked.hs:34:10: error: • Couldn't match type ‘c0’ with ‘Producer' PB.ByteString m0 ()’ Expected: Data.ByteString.Lazy.Internal.ByteString -> c0 Actual: Data.ByteString.Lazy.Internal.ByteString -> Producer' PB.ByteString m0 () Cannot instantiate unification variable ‘c0’ with a type involving polytypes: Producer' PB.ByteString m0 () • In the first argument of ‘(.)’, namely ‘PB.fromLazy’ In the expression: PB.fromLazy . Ae.encode In an equation for ‘encode’: encode = PB.fromLazy . Ae.encode | 34 | encode = PB.fromLazy . Ae.encode | ^^^ src/Pipes/Aeson/Unchecked.hs:34:10: error: • Couldn't match type ‘c0’ with ‘Producer' PB.ByteString m ()’ Expected: a -> Producer' PB.ByteString m () Actual: a -> c0 Cannot instantiate unification variable ‘c0’ with a type involving polytypes: Producer' PB.ByteString m () • In the expression: PB.fromLazy . Ae.encode In an equation for ‘encode’: encode = PB.fromLazy . Ae.encode • Relevant bindings include encode :: a -> Producer' PB.ByteString m () (bound at src/Pipes/Aeson/Unchecked.hs:34:1) | 34 | encode = PB.fromLazy . Ae.encode | ^^^ src/Pipes/Aeson/Unchecked.hs:37:19: error: • Couldn't match type: forall x'1 x1. Proxy x'1 x1 () PB.ByteString m1 () with: Proxy () a () PB.ByteString m () Expected: a -> Proxy () a () PB.ByteString m () Actual: a -> Producer' PB.ByteString m1 () • In the second argument of ‘for’, namely ‘encode’ In the second argument of ‘(>->)’, namely ‘for cat encode’ In the expression: p >-> for cat encode • Relevant bindings include p :: Proxy x' x () a m a' (bound at src/Pipes/Aeson/Unchecked.hs:36:41) | 37 | p >-> for cat encode = for p (\a -> PB.fromLazy (Ae.encode a)) | ^^ ... --- End Message --- --- Begin Message --- Version: 0.4.1.8-4+rm Dear submitter, as the package haskell-pipes-aeson 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/1029340 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#1017322: marked as done (haskell-simple-templates: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:160: build-ghc-stamp] Error 25)
Your message dated Sat, 21 Jan 2023 22:38:15 +
with message-id
and subject line Bug#1029344: Removed package(s) from unstable
has caused the Debian Bug report #1017226,
regarding haskell-simple-templates: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:160: build-ghc-stamp] 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.)
--
1017226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-simple-templates
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-simple-templates-doc.substvars
> dh_installdirs -plibghc-simple-templates-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/9JTNW6Ngrh -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-simple-templates-dev
> libghc-simple-templates-prof
> libghc-simple-templates-doc
> Running dh_listpackages
> libghc-simple-templates-dev
> libghc-simple-templates-prof
> libghc-simple-templates-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/simple-templates-1.0.0/
> --datasubdir=simple-templates
> --htmldir=/usr/share/doc/libghc-simple-templates-doc/html/
> --enable-library-profiling --enable-tests
> Using Parsec parser
> Configuring simple-templates-1.0.0...
> Dependency aeson >=0.7: using aeson-2.0.3.0
> Dependency attoparsec: using attoparsec-0.14.4
> Dependency base <6: using base-4.15.1.0
> Dependency scientific: using scientific-0.3.7.0
> Dependency text: using text-1.2.5.0
> Dependency unordered-containers: using unordered-containers-0.2.17.0
> Dependency vector: using vector-0.12.3.1
> Dependency HUnit: using HUnit-1.6.2.0
> Dependency aeson >=0.7: using aeson-2.0.3.0
> Dependency attoparsec: using attoparsec-0.14.4
> Dependency base <6: using base-4.15.1.0
> Dependency hspec: using hspec-2.8.5
> Dependency scientific: using scientific-0.3.7.0
> Dependency simple-templates: using simple-templates-1.0.0
> Dependency vector: using vector-0.12.3.1
> Source component graph:
> component lib
> component test:test-simple-templates dependency lib
> Configured component graph:
> component simple-templates-1.0.0-E9LpJ19hRHcC7XGzlO2bhy
> include aeson-2.0.3.0-AMpeUvq093B6yWOa7oRnlZ
> include attoparsec-0.14.4-ASUOPk5RpsVDRcb75ybcSE
> include base-4.15.1.0
> include scientific-0.3.7.0-7BCpthzRrIo63GoBWzRPfh
> include text-1.2.5.0
> include unordered-containers-0.2.17.0-FS8hZKYGMqLFC8ibuPNvjR
> include vector-0.12.3.1-TXkE6leK98EdYcmdk29JF
> component
> simple-templates-1.0.0-1ES1avNHogEKJizK4K0K2M-test-simple-templates
> include HUnit-1.6.2.0-6A7GkX10OfW69odZH6xHBm
> include aeson-2.0.3.0-AMpeUvq093B6yWOa7oRnlZ
> include attoparsec-0.14.4-ASUOPk5RpsVDRcb75ybcSE
> include base-4.15.1.0
> include hspec-2.8.5-ztFhIZtg6636xJR5cbSTr
> include scientific-0.3.7.0-7BCpthzRrIo63GoBWzRPfh
> include simple-templates-1.0.0-E9LpJ19hRHcC7XGzlO2bhy
> include vector-0.12.3.1-TXkE6leK98EdYcmdk29JF
> Linked component graph:
> unit simple-templates-1.0.0-E9LpJ19hRHcC7XGzlO2bhy
> include aeson-2.0.3.0-AMpeUvq093B6yWOa7oRnlZ
> include attoparsec-0.14.4-ASUOPk5RpsVDRcb75ybcSE
> include base-4.15.1.0
> include scientific-0.3.7.0-7BCpthzRrIo63GoBWzRPfh
> include text-1.2.5.0
> include unordered-containers-0.2.17.0-FS8hZKYGMqLFC8ibuPNvjR
> include
Bug#1017226: marked as done (haskell-simple: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev-1.4.7.1-e9a35, libghc-attoparsec-dev-0.13.2.4-b0216, libghc-base-dev-4.13.0.0-2f220, libghc-scien
Your message dated Sat, 21 Jan 2023 22:38:15 + with message-id and subject line Bug#1029344: Removed package(s) from unstable has caused the Debian Bug report #1017226, regarding haskell-simple: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev-1.4.7.1-e9a35, libghc-attoparsec-dev-0.13.2.4-b0216, libghc-base-dev-4.13.0.0-2f220, libghc-scientific-dev-0.3.6.2-3ce19, libghc-text-dev-1.2.4.0-a7a6e, libghc-unordered-containers-dev-0.2.10.0-71273, libghc-vector-dev-0.12.1.2-29734, haddock-interface-35, libghc-aeson-prof-1.4.7.1-e9a35, libghc-attoparsec-prof-0.13.2.4-b0216, libghc-base-prof-4.13.0.0-2f220, libghc-scientific-prof-0.3.6.2-3ce19, libghc-text-prof-1.2.4.0-a7a6e, libghc-unordered-containers-prof-0.2.10.0-71273, libghc-vector-prof-0.12.1.2-29734 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.) -- 1017226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-simple Version: 1.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 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: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-aeson-dev, libghc-aeson-prof, > libghc-attoparsec-dev, libghc-base64-bytestring-dev, > libghc-base64-bytestring-prof, libghc-blaze-builder-dev, > libghc-blaze-builder-prof, libghc-bytestring-dev, libghc-bytestring-prof, > libghc-cmdargs-dev, libghc-directory-dev, libghc-directory-prof, > libghc-filepath-dev, libghc-filepath-prof, libghc-hspec-contrib-dev, > libghc-hspec-dev, libghc-http-types-dev, libghc-http-types-prof, > libghc-mime-types-dev, libghc-mime-types-prof, libghc-monad-control-dev (>= > 1.0.0.0), libghc-monad-control-prof, libghc-process-dev, libghc-setenv-dev, > libghc-simple-templates-dev (>= 1.0.0), libghc-simple-templates-prof, > libghc-transformers-base-dev, libghc-transformers-base-prof, > libghc-transformers-dev, libghc-transformers-prof, > libghc-unordered-containers-dev, libghc-unordered-containers-prof, > libghc-vector-dev, libghc-vector-prof, libghc-wai-dev (>= 3.0), > libghc-wai-extra-dev, libghc-wai-extra-prof, libghc-attoparsec-prof, > libghc-cmdargs-prof, libghc-setenv-prof, libghc-hspec-prof, > libghc-hspec-contrib-prof, build-essential, fakeroot, ghc-doc, > libghc-aeson-doc, libghc-base64-bytestring-doc, libghc-blaze-builder-doc, > libghc-bytestring-doc, libghc-directory-doc, libghc-filepath-doc, > libghc-http-types-doc, libghc-mime-types-doc, libghc-monad-control-doc, > libghc-simple-templates-doc, libghc-transformers-base-doc, > libghc-transformers-doc, libghc-unordered-containers-doc, libghc-vector-doc, > libghc-wai-doc, libghc-wai-extra-doc > Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-aeson-dev, libghc-aeson-prof, > libghc-attoparsec-dev, libghc-base64-bytestring-dev, > libghc-base64-bytestring-prof, libghc-blaze-builder-dev, > libghc-blaze-builder-prof, libghc-bytestring-dev, libghc-bytestring-prof, > libghc-cmdargs-dev, libghc-directory-dev, libghc-directory-prof, > libghc-filepath-dev, libghc-filepath-prof, libghc-hspec-contrib-dev, > libghc-hspec-dev, libghc-http-types-dev, libghc-http-types-prof, > libghc-mime-types-dev, libghc-mime-types-prof, libghc-monad-control-dev (>= > 1.0.0.0), libghc-monad-control-prof, libghc-process-dev, libghc-setenv-dev, > libghc-simple-templates-dev (>= 1.0.0), libghc-simple-templates-prof, > libghc-transformers-base-dev, libghc-transformers-base-prof, > libghc-transformers-dev, libghc-transformers-prof, > libghc-unordered-containers-dev, libghc-unordered-containers-prof, > libghc-vector-dev, libghc-vector-prof, libghc-wai-dev (>= 3.0), > libghc-wai-extra-dev, libghc-wai-extra-prof, libghc-attoparsec-prof, > libghc-cmdargs-prof, libghc-setenv-prof, libghc-hspec-prof, > libghc-hspec-contrib-prof, build-essential, fakeroot, ghc-doc, > libghc-aeson-doc, libghc-base64-bytestring-doc, libghc-blaze-builder-doc, > libghc-bytestring-doc, libghc-directory-doc, libghc-filepath-doc, >
Bug#1017212: marked as done (haskell-ekg: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev (< 1.6), libghc-ekg-json-dev (< 0.2), libghc-ekg-json-dev (>= 0.1), libghc-ekg-json-prof, libghc-sna
Your message dated Sat, 21 Jan 2023 22:34:38 + with message-id and subject line Bug#1029337: Removed package(s) from unstable has caused the Debian Bug report #1017212, regarding haskell-ekg: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev (< 1.6), libghc-ekg-json-dev (< 0.2), libghc-ekg-json-dev (>= 0.1), libghc-ekg-json-prof, libghc-snap-server-dev (< 1.2), libghc-snap-server-prof, libghc-ekg-json-doc, libghc-snap-server-doc 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.) -- 1017212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-ekg Version: 0.4.0.15-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 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: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.4), libghc-aeson-dev (<< > 1.6), libghc-aeson-prof, libghc-ekg-core-dev (<< 0.2), libghc-ekg-core-dev > (>= 0.1), libghc-ekg-core-prof, libghc-ekg-json-dev (<< 0.2), > libghc-ekg-json-dev (>= 0.1), libghc-ekg-json-prof, libghc-network-dev (<< > 3.2), libghc-network-prof, libghc-snap-core-dev (<< 1.1), > libghc-snap-core-prof, libghc-snap-server-dev (<< 1.2), > libghc-snap-server-prof, libghc-unordered-containers-dev (<< 0.3), > libghc-unordered-containers-prof, build-essential, fakeroot, ghc-doc, > libghc-aeson-doc, libghc-ekg-core-doc, libghc-ekg-json-doc, > libghc-network-doc, libghc-snap-core-doc, libghc-snap-server-doc, > libghc-unordered-containers-doc > Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.4), libghc-aeson-dev (<< > 1.6), libghc-aeson-prof, libghc-ekg-core-dev (<< 0.2), libghc-ekg-core-dev > (>= 0.1), libghc-ekg-core-prof, libghc-ekg-json-dev (<< 0.2), > libghc-ekg-json-dev (>= 0.1), libghc-ekg-json-prof, libghc-network-dev (<< > 3.2), libghc-network-prof, libghc-snap-core-dev (<< 1.1), > libghc-snap-core-prof, libghc-snap-server-dev (<< 1.2), > libghc-snap-server-prof, libghc-unordered-containers-dev (<< 0.3), > libghc-unordered-containers-prof, build-essential, fakeroot, ghc-doc, > libghc-aeson-doc, libghc-ekg-core-doc, libghc-ekg-json-doc, > libghc-network-doc, libghc-snap-core-doc, libghc-snap-server-doc, > libghc-unordered-containers-doc > 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 [558 B] > Get:5 copy:/<>/apt_archive ./ Packages [637 B] > Fetched 2158 B in 0s (159 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: libghc-aeson-dev (< 1.6) but > 2.0.3.0-1+b1 is to be installed >Depends: libghc-ekg-json-dev (< 0.2) but > it is not going to be installed >Depends: libghc-ekg-json-dev (>= 0.1) but > it is not going to be installed >Depends: libghc-ekg-json-prof but it is > not going to be installed >Depends: libghc-snap-server-dev (< 1.2) > but it is not going to be installed >Depends: libghc-snap-server-prof but it is > not going to be installed >Depends: libghc-ekg-json-doc but it is not >
Bug#1017209: marked as done (haskell-ekg-json: FTBFS: unsatisfiable build-dependency: libghc-aeson-dev (< 1.6) but 2.0.3.0-1+b1 is to be installed)
Your message dated Sat, 21 Jan 2023 22:35:58 + with message-id and subject line Bug#1029339: Removed package(s) from unstable has caused the Debian Bug report #1017209, regarding haskell-ekg-json: FTBFS: unsatisfiable build-dependency: libghc-aeson-dev (< 1.6) but 2.0.3.0-1+b1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-ekg-json Version: 0.1.0.6-7 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 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: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.4), libghc-aeson-dev (<< > 1.6), libghc-aeson-prof, libghc-ekg-core-dev (<< 0.2), libghc-ekg-core-dev > (>= 0.1), libghc-ekg-core-prof, libghc-unordered-containers-dev (<< 0.3), > libghc-unordered-containers-prof, build-essential, fakeroot, ghc-doc, > libghc-aeson-doc, libghc-ekg-core-doc, libghc-unordered-containers-doc > Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, > haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.4), libghc-aeson-dev (<< > 1.6), libghc-aeson-prof, libghc-ekg-core-dev (<< 0.2), libghc-ekg-core-dev > (>= 0.1), libghc-ekg-core-prof, libghc-unordered-containers-dev (<< 0.3), > libghc-unordered-containers-prof, build-essential, fakeroot, ghc-doc, > libghc-aeson-doc, libghc-ekg-core-doc, libghc-unordered-containers-doc > 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 [488 B] > Get:5 copy:/<>/apt_archive ./ Packages [564 B] > Fetched 2015 B in 0s (150 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: libghc-aeson-dev (< 1.6) but > 2.0.3.0-1+b1 is to be installed > 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/08/13/haskell-ekg-json_0.1.0.6-7_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=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 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: 0.1.0.6-7+rm Dear submitter, as the package haskell-ekg-json 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/1029339 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
Bug#1013785: marked as done (haskell-regex-compat-tdfa FTBFS: Bang pattern in expression context: !0)
Your message dated Sat, 21 Jan 2023 22:37:16 +
with message-id
and subject line Bug#1029341: Removed package(s) from unstable
has caused the Debian Bug report #1013785,
regarding haskell-regex-compat-tdfa FTBFS: Bang pattern in expression context:
!0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1013785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-regex-compat-tdfa
Version: 0.95.1.4-8
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-regex-compat-tdfa=sid
...
Text/Regex.hs:142:22: error:
Bang pattern in expression context: !0
Did you mean to add a space after the '!'?
|
142 | let matches = map (!0) (matchAll delim strIn)
| ^^
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 707
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.95.1.4-8+rm
Dear submitter,
as the package haskell-regex-compat-tdfa 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/1029341
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#1019230: Bug#1021276: Pending snort 2.9.20 update
On Sat, Jan 21, 2023 at 10:53:24PM +0100, Markus Koschany wrote: > Hi Javier, > > Am Freitag, dem 20.01.2023 um 22:23 +0100 schrieb Javier Fernandez-Sanguino: > > Dear Markus, > > > > Thank you for preparing. Could you please share the patch you are working > > on? > > Snort is available in Salsa. Maybe you could upload / provide there your > > propose changes in a separate branch? > > I'm adding the security team to CC to give them a heads-up because the snort > update is also relevant for stable and oldstable. I'm not allowed to push to > your Git repository on salsa. I will just attach my debian directory to the RC > bug reports next. > > First of all I decided to package 2.9.20 because this version seems less > intrusive than the new 3.x series. Thanks for fixing up buster/bullseye for existing users (which I think is best catered by moving to 2.9.20, but I don't think snort should be in Bookworm: - No upload since almost 1.5 years, zero followup to #1019230 or #1021276 until your poke - What's worse: The security progress is completely intransparent, apart from dropping new releases with vague Cisco advisories Cheers, Moritz
Processed: Re: nyx: Does not work with python 3.11 anymore
Processing control commands: > severity -1 serious Bug #1028563 [nyx] nyx: Does not work with python 3.11 anymore Severity set to 'serious' from 'important' -- 1028563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: vtk-dicom: diff for NMU version 0.8.14-3.1
Processing control commands: > tags 1029178 + patch Bug #1029178 [src:vtk-dicom] vtk-dicom: autopkgtest failure Added tag(s) patch. > tags 1029178 + pending Bug #1029178 [src:vtk-dicom] vtk-dicom: autopkgtest failure Added tag(s) pending. -- 1029178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029178: vtk-dicom: diff for NMU version 0.8.14-3.1
Control: tags 1029178 + patch
Control: tags 1029178 + pending
Dear maintainer,
I've prepared an NMU for vtk-dicom (versioned as 0.8.14-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru vtk-dicom-0.8.14/debian/changelog vtk-dicom-0.8.14/debian/changelog
--- vtk-dicom-0.8.14/debian/changelog 2023-01-17 14:58:40.0 +0100
+++ vtk-dicom-0.8.14/debian/changelog 2023-01-21 22:41:32.0 +0100
@@ -1,3 +1,10 @@
+vtk-dicom (0.8.14-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * debian/control: Use ${python3:Depends} (Closes: #1029178)
+
+ -- Sebastian Ramacher Sat, 21 Jan 2023 22:41:32 +0100
+
vtk-dicom (0.8.14-3) unstable; urgency=medium
* Team upload.
diff -Nru vtk-dicom-0.8.14/debian/control vtk-dicom-0.8.14/debian/control
--- vtk-dicom-0.8.14/debian/control 2023-01-10 08:04:03.0 +0100
+++ vtk-dicom-0.8.14/debian/control 2023-01-21 22:38:41.0 +0100
@@ -63,7 +63,7 @@
Package: python3-vtk-dicom
Architecture: any
Section: python
-Depends: python3, python3-vtk9, ${misc:Depends}, ${shlibs:Depends}
+Depends: ${python3:Depends}, python3-vtk9, ${misc:Depends}, ${shlibs:Depends}
Provides: ${python3:Provides}
Description: DICOM for VTK - Python
This package contains a set of classes for managing DICOM
Bug#1019230: Bug#1021276: Pending snort 2.9.20 update
Hi Javier, Am Freitag, dem 20.01.2023 um 22:23 +0100 schrieb Javier Fernandez-Sanguino: > Dear Markus, > > Thank you for preparing. Could you please share the patch you are working on? > Snort is available in Salsa. Maybe you could upload / provide there your > propose changes in a separate branch? I'm adding the security team to CC to give them a heads-up because the snort update is also relevant for stable and oldstable. I'm not allowed to push to your Git repository on salsa. I will just attach my debian directory to the RC bug reports next. First of all I decided to package 2.9.20 because this version seems less intrusive than the new 3.x series. For better long-term support it would be better to go for 3.x but I leave this decision to you. I have refreshed all patches and dropped the autoconf, fix_compile_errors and fix_ftbfs_in_manual.tex patches because the package builds fine without them. In debhelper-compat 13 auto-reconfiguration is the default now. There are still a couple of Lintian errors and warnings about snort which are also present in the current unstable version. I only removed the Windows binaries from the source tarball so far. https://udd.debian.org/lintian/?packages=snort I didn't touch anything else in your package. You just need to run uscan and remove the dll files again if you want to upload yourself. If you don't have time for that, let me know, and I'll take care of the rest. Best, Markus P.S.: Your VCS repository is not up-to-date, the last update is missing. signature.asc Description: This is a digitally signed message part
Bug#1028413: (no subject)
Hi, this bug is still there for me. All packages updated to bookworm/testing. Let me know, if you need more info. Thanks in advance, Diego.
Bug#1018691: closed by Pirate Praveen (closing already fixed bug)
I can confirm that indeed nehko can now start properly in Debian testing. Thanks! This is an automatic notification regarding your Bug report which was filed against the nheko package: #1018691: reportbug: nheko fails to start. Undefined symbol It has been closed by Pirate Praveen . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Pirate Praveen by replying to this email.
Bug#979955: marked as done (ruby-rails-assets-jquery-fullscreen-plugin: node-uglify is deprecated in favor of uglifyjs)
Your message dated Sat, 21 Jan 2023 21:15:16 +
with message-id
and subject line Bug#979955: fixed in
ruby-rails-assets-jquery-fullscreen-plugin 0.5.0+dfsg-6
has caused the Debian Bug report #979955,
regarding ruby-rails-assets-jquery-fullscreen-plugin: node-uglify is deprecated
in favor of uglifyjs
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.)
--
979955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rails-assets-jquery-fullscreen-plugin
Severity: important
ruby-rails-assets-jquery-fullscreen-plugin build depends on
node-uglify which is deprecated and will be removed from bullseye
(#958117), please update your (build) dependency in favor of uglifyjs
or uglifyjs.terser
https://bugs.debian.org/958117
(sent using mass-bug)
--- End Message ---
--- Begin Message ---
Source: ruby-rails-assets-jquery-fullscreen-plugin
Source-Version: 0.5.0+dfsg-6
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
ruby-rails-assets-jquery-fullscreen-plugin, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated
ruby-rails-assets-jquery-fullscreen-plugin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 22 Jan 2023 00:17:12 +0530
Source: ruby-rails-assets-jquery-fullscreen-plugin
Architecture: source
Version: 0.5.0+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Pirate Praveen
Closes: 979955
Changes:
ruby-rails-assets-jquery-fullscreen-plugin (0.5.0+dfsg-6) unstable;
urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Apply multi-arch hints. + ruby-rails-assets-jquery-fullscreen-plugin:
Add :any qualifier for ruby dependency.
.
[ Pirate Praveen ]
* Switch build dependency to uglifyjs (from node-uglify) (Closes: #979955)
* Bump Standards-Version to 4.6.2 (no changes needed)
* Switch to ${ruby:Depends} for ruby dependencies
Checksums-Sha1:
a511bf5124df732cf9504e2a31a1d4b568166dae 2538
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6.dsc
29a8853de33fc33697de6d97e1b0d23743a9e337 4544
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6.debian.tar.xz
4bc1041ae69dc6e5d00dedf531984a09faf12935 10156
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6_amd64.buildinfo
Checksums-Sha256:
0bd899e4fa9ba18706138252e2d87927456788f2879c3b8ea9c25864e9c05ec7 2538
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6.dsc
3d6755b824f16011f3b63edcfdb29532c02b50e1e25e648017a1f000cf46265c 4544
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6.debian.tar.xz
05022381227b08f4d11aae89ea0ceab9794ff98261b47e48fb7c0c9094eb6c66 10156
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6_amd64.buildinfo
Files:
2fb7113ff32014c1351e9af3325f4815 2538 ruby optional
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6.dsc
148d15de2adc4c53e42f716cbe75f2e4 4544 ruby optional
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6.debian.tar.xz
be9a5c193fb053a79617a0fbe711ca6c 10156 ruby optional
ruby-rails-assets-jquery-fullscreen-plugin_0.5.0+dfsg-6_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAmPMNzsACgkQj1PgGTsp
S3XIDQ//eqt2A/mQYpCOv8u+Vgl5B7qlaLdKtV27Jj0Esrw7Rvl8p0EmWdRf4+le
Pq+HawVGsthST5mdhKmyFELsKwHk83r97Xb//CDQGeDRlStOnNryapUXS7YCwsyH
XYv2YBg2OiN2NEIRbfNbum3osA6CjItqMWH+zTfiSfJZ4+15rT033BhwpAGKrYjn
BvXOBkez1vfCBkyADU1B+oyu3chFdymBsDo/4O/DSpO6vZb9XxwR8rKGALY/NNcc
69dVTx4V6cGgqzGCqOqe6vreRZ32ngbGtfIMPXwPKhbneF2sqPX8n8tCHSv2Ougy
VULzEsM3DE8wsLuInAh+fwcm1VEZ/L/g3QMpKBeel4BxIpz7KJQpP1oWEji1wetS
1YDSb4IJXWfN8DYzE0MT0MiwDjsXPDxeBA4gj7OQ4S8ysjIwgnsex3iC78qgxeVT
X7V/SByNOiOhpgH/+D4RNDNPJZ2vzzShyB1m0HoOkyH0T+/oalbCg+Vyo8f/WSvf
gn099Ok9kMkO1RY/ldn4S3d+QTJKI6jn7MqhuKsC0q3cGYP5WnxTzGyjXegrDHzY
tL/QuZJEYjbp8M2kKptHIl3z26qvnTpdNvShqYCbSvLBQDIYXAh5L4L6skOSUTIV
NER1i/OspqbNix6b8zDd18YSgeMGk8C+vqyXXSHq7LGzKY6TcSQ=
=b1ap
-END PGP SIGNATURE End Message ---
Bug#1028619: marked as done (rich: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1)
Your message dated Sat, 21 Jan 2023 21:15:08 + with message-id and subject line Bug#1028619: fixed in rich 13.0.0-1.1 has caused the Debian Bug report #1028619, regarding rich: autopkgtest is failng after updating pygments to 2.14.0+dfsg-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.) -- 1028619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rich Version: 13.0.0-1 Severity: serious Dear Maintainer, after the upload of pygments 2.14.0+dfsg-1 your package is failung while running the autopkgtest. The failed part in detail is: === FAILURES === ___ test_python_render_simple_indent_guides def test_python_render_simple_indent_guides(): syntax = Syntax( CODE, lexer="python", line_numbers=False, theme="ansi_light", code_width=60, word_wrap=False, indent_guides=True, ) rendered_syntax = render(syntax) print(repr(rendered_syntax)) expected = '\x1b[34mdef\x1b[0m \x1b[32mloop_first_last\x1b[0m(values: Iterable[T]) -> Iterable[Tuple[\x1b[36mb\x1b[0m\n\x1b[2m│ \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│ \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n\x1b[2m│ \x1b[0m\x1b[34mtry\x1b[0m:\n\x1b[2m│ │ \x1b[0mprevious_value = \x1b[36mnext\x1b[0m(iter_values)\n\x1b[2m│ \x1b[0m\x1b[34mexcept\x1b[0m \x1b[36mStopIteration\x1b[0m:\n\x1b[2m│ │ \x1b[0m\x1b[34mreturn\x1b[0m\n\x1b[2m│ \x1b[0mfirst = \x1b[34mTrue\x1b[0m\n\x1b[2m│ \x1b[0m\x1b[34mfor\x1b[0m value \x1b[35min\x1b[0m iter_values:\n\x1b[2m│ │ \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mFalse\x1b[0m, previous_value\n\x1b[2m│ │ \x1b[0mfirst = \x1b[34mFalse\x1b[0m\n\x1b[2m│ │ \x1b[0mprevious_value = value\n\x1b[2m│ \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mTrue\x1b[0m, previous_value\n' > assert rendered_syntax == expected E assert '\x1b[34mdef\...vious_value\n' == '\x1b[34mdef\...vious_value\n' E Skipping 81 identical leading characters in diff, use -v to show E mb␛[0m E - ␛[2m│ ␛[0m␛[33m"""Iterate and generate a tuple with a flag for first an␛[0m E + ␛[2;37m│ ␛[0m␛[33m"""Iterate and generate a tuple with a flag for first an␛[0m E ?+++ E ␛[2m│ ␛[0miter_values = ␛[36miter␛[0m(values) E ␛[2m│ ␛[0m␛[34mtry␛[0m:... E E ...Full output truncated (10 lines hidden), use '-vv' to show tests/test_syntax.py:114: AssertionError - Captured stdout call - '\x1b[34mdef\x1b[0m \x1b[32mloop_first_last\x1b[0m(values: Iterable[T]) -> Iterable[Tuple[\x1b[36mb\x1b[0m\n\x1b[2;37m│ \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│ \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n\x1b[2m│ \x1b[0m\x1b[34mtry\x1b[0m:\n\x1b[2m│ │ \x1b[0mprevious_value = \x1b[36mnext\x1b[0m(iter_values)\n\x1b[2m│ \x1b[0m\x1b[34mexcept\x1b[0m \x1b[36mStopIteration\x1b[0m:\n\x1b[2m│ │ \x1b[0m\x1b[34mreturn\x1b[0m\n\x1b[2m│ \x1b[0mfirst = \x1b[34mTrue\x1b[0m\n\x1b[2m│ \x1b[0m\x1b[34mfor\x1b[0m value \x1b[35min\x1b[0m iter_values:\n\x1b[2m│ │ \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mFalse\x1b[0m, previous_value\n\x1b[2m│ │ \x1b[0mfirst = \x1b[34mFalse\x1b[0m\n\x1b[2m│ │ \x1b[0mprevious_value = value\n\x1b[2m│ \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mTrue\x1b[0m, previous_value\n' _ test_python_render_line_range_indent_guides __ def test_python_render_line_range_indent_guides(): syntax = Syntax( CODE, lexer="python", line_numbers=False, theme="ansi_light", code_width=60, word_wrap=False, line_range=(2, 3), indent_guides=True, ) rendered_syntax = render(syntax) print(repr(rendered_syntax)) expected = '\x1b[2m│ \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│ \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n' > assert rendered_syntax == expected E assert '\x1b[2;37m│ ...[0m(values)\n' == '\x1b[2m│ \...[0m(values)\n' E - ␛[2m│ ␛[0m␛[33m"""Iterate and generate a tuple with a flag for first an␛[0m E + ␛[2;37m│
Bug#1028672: marked as done (python-xmlrunner: FTBFS: AttributeError: 'tuple' object has no attribute 'shortDescription')
Your message dated Sat, 21 Jan 2023 21:14:37 + with message-id and subject line Bug#1028672: fixed in python-xmlrunner 3.2.0-2 has caused the Debian Bug report #1028672, regarding python-xmlrunner: FTBFS: AttributeError: 'tuple' object has no attribute 'shortDescription' 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.) -- 1028672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-xmlrunner Version: 3.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 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 >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > copying xmlrunner/__init__.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > copying xmlrunner/__main__.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > copying xmlrunner/runner.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > copying xmlrunner/builder.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > copying xmlrunner/result.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > copying xmlrunner/unittest.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > copying xmlrunner/version.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner > creating > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner/extra > copying xmlrunner/extra/__init__.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner/extra > copying xmlrunner/extra/xunit_plugin.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner/extra > copying xmlrunner/extra/djangotestrunner.py -> > /<>/.pybuild/cpython3_3.11_xmlrunner/build/xmlrunner/extra > running egg_info > creating unittest_xml_reporting.egg-info > writing unittest_xml_reporting.egg-info/PKG-INFO > writing dependency_links to > unittest_xml_reporting.egg-info/dependency_links.txt > writing requirements to unittest_xml_reporting.egg-info/requires.txt > writing top-level names to unittest_xml_reporting.egg-info/top_level.txt > writing manifest file 'unittest_xml_reporting.egg-info/SOURCES.txt' > reading manifest file 'unittest_xml_reporting.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE' > writing manifest file 'unittest_xml_reporting.egg-info/SOURCES.txt' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py test > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > writing unittest_xml_reporting.egg-info/PKG-INFO > writing dependency_links to > unittest_xml_reporting.egg-info/dependency_links.txt > writing requirements to unittest_xml_reporting.egg-info/requires.txt > writing top-level names to unittest_xml_reporting.egg-info/top_level.txt > reading manifest file 'unittest_xml_reporting.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE' > writing manifest file 'unittest_xml_reporting.egg-info/SOURCES.txt' > running build_ext > test_append_cdata_closing_tags_into_cdata_section > (tests.builder_test.TestXMLBuilderTest.test_append_cdata_closing_tags_into_cdata_section) > ... ok > test_append_invalid_unicode_cdata_section > (tests.builder_test.TestXMLBuilderTest.test_append_invalid_unicode_cdata_section) > ... ok > test_append_tag_with_invalid_unicode_values > (tests.builder_test.TestXMLBuilderTest.test_append_tag_with_invalid_unicode_values) > ... ok > test_append_tag_with_valid_unicode_values > (tests.builder_test.TestXMLBuilderTest.test_append_tag_with_valid_unicode_values) > ... ok > test_append_valid_unicode_cdata_section > (tests.builder_test.TestXMLBuilderTest.test_append_valid_unicode_cdata_section) > ... ok > test_begin_nested_context > (tests.builder_test.TestXMLBuilderTest.test_begin_nested_context) ... ok > test_current_context_tag >
Bug#1028671: marked as done (python-django-tagging: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.11" --system=custom "--test-args=PYTHONPATH=. DJANGO_SETTINGS_MODULE=taggin
Your message dated Sat, 21 Jan 2023 21:14:30 +
with message-id
and subject line Bug#1028671: fixed in python-django-tagging 1:0.5.0-4
has caused the Debian Bug report #1028671,
regarding python-django-tagging: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.11" --system=custom "--test-args=PYTHONPATH=.
DJANGO_SETTINGS_MODULE=tagging.tests.settings django-admin test --verbosity=2"
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.)
--
1028671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-tagging
Version: 1:0.5.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 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_test -- --system=custom --test-args="PYTHONPATH=.
> DJANGO_SETTINGS_MODULE=tagging.tests.settings django-admin test --verbosity=2"
> I: pybuild base:240: PYTHONPATH=.
> DJANGO_SETTINGS_MODULE=tagging.tests.settings django-admin test --verbosity=2
> Creating test database for alias 'default'
> ('file:memorydb_default?mode=memory=shared')...
> Operations to perform:
> Synchronize unmigrated apps: tests
> Apply all migrations: auth, contenttypes, sessions, tagging
> Synchronizing apps without migrations:
> Creating tables...
> Creating table tests_perch
> Creating table tests_parrot
> Creating table tests_link
> Creating table tests_article
> Creating table tests_formtest
> Creating table tests_formtestnull
> Creating table tests_formmultiplefieldtest
> Running deferred SQL...
> Running migrations:
> Applying contenttypes.0001_initial... OK
> Applying contenttypes.0002_remove_content_type_name... OK
> Applying auth.0001_initial... OK
> Applying auth.0002_alter_permission_name_max_length... OK
> Applying auth.0003_alter_user_email_max_length... OK
> Applying auth.0004_alter_user_username_opts... OK
> Applying auth.0005_alter_user_last_login_null... OK
> Applying auth.0006_require_contenttypes_0002... OK
> Applying auth.0007_alter_validators_add_error_messages... OK
> Applying auth.0008_alter_user_username_max_length... OK
> Applying auth.0009_alter_user_last_name_max_length... OK
> Applying auth.0010_alter_group_name_max_length... OK
> Applying auth.0011_update_proxy_permissions... OK
> Applying auth.0012_alter_user_first_name_max_length... OK
> Applying sessions.0001_initial... OK
> Applying tagging.0001_initial... OK
> Applying tagging.0002_on_delete... OK
> Applying tagging.0003_adapt_max_tag_length... OK
> System check identified some issues:
>
> WARNINGS:
> tagging.Tag: (models.W042) Auto-created primary key used when not defining a
> primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> TaggingConfig.default_auto_field attribute to point to a subclass of
> AutoField, e.g. 'django.db.models.BigAutoField'.
> tagging.TaggedItem: (models.W042) Auto-created primary key used when not
> defining a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> TaggingConfig.default_auto_field attribute to point to a subclass of
> AutoField, e.g. 'django.db.models.BigAutoField'.
> tests.Article: (models.W042) Auto-created primary key used when not defining
> a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.FormMultipleFieldTest: (models.W042) Auto-created primary key used when
> not defining a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.FormTest: (models.W042) Auto-created primary key used when not defining
> a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.FormTestNull: (models.W042) Auto-created primary key used when not
> defining a primary key type, by
Bug#1028793: marked as done (pymodbus: FTBFS: TypeError: BaseEventLoop.create_datagram_endpoint() got an unexpected keyword argument 'reuse_address')
Your message dated Sat, 21 Jan 2023 21:14:14 + with message-id and subject line Bug#1028793: fixed in pymodbus 3.0.0-6 has caused the Debian Bug report #1028793, regarding pymodbus: FTBFS: TypeError: BaseEventLoop.create_datagram_endpoint() got an unexpected keyword argument 'reuse_address' 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.) -- 1028793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pymodbus Version: 3.0.0-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 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 '/<>' > PYTHONPATH=/<> dh_auto_test > I: pybuild base:240: cd > /<>/.pybuild/cpython3_3.11_pymodbus/build; python3.11 -m pytest > test > = 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, asyncio-0.20.3 > asyncio: mode=Mode.AUTO > collected 443 items > > test/test_all_messages.py ...[ > 0%] > test/test_bit_read_messages.py . [ > 2%] > test/test_bit_write_messages.py .[ > 4%] > test/test_client.py [ > 16%] > .. [ > 16%] > test/test_client_sync.py [ > 23%] > test/test_client_sync_diag.py . [ > 24%] > test/test_datastore.py ... [ > 31%] > test/test_device.py .[ > 36%] > test/test_diag_messages.py . [ > 38%] > test/test_events.py .. [ > 39%] > test/test_examples.py ...FF.F[ > 47%] > test/test_exceptions.py .[ > 47%] > test/test_factory.py ... [ > 50%] > test/test_file_message.py ...[ > 55%] > test/test_framers.py . [ > 66%] > test/test_interfaces.py .[ > 67%] > test/test_mei_messages.py [ > 69%] > test/test_other_messages.py ... [ > 70%] > test/test_payload.py . [ > 72%] > test/test_pdu.py [ > 73%] > test/test_register_read_messages.py ... [ > 76%] > test/test_register_write_messages.py [ > 79%] > test/test_remote_datastore.py [ > 79%] > test/test_repl_client.py .. [ > 80%] > test/test_server_asyncio.py FE...FEFEFEFEFE.FE [ > 85%] > test/test_server_context.py ... [ > 88%] > test/test_transaction.py .. [ > 98%] > test/test_utilities.py . [ > 99%] > test/test_version.py .. > [100%] > > ERRORS > > __ ERROR at teardown of AsyncioServerTest.test_async_start_udp_server > __ > > self = testMethod=test_async_start_udp_server> > > async def asyncTearDown(self): > """Clean up the test environment""" > if self.server is not None: > await self.server.server_close() > self.server = None > if self.task is not None: > await asyncio.sleep(0.1) > if not self.task.cancelled(): > self.task.cancel() > try: > > await self.task > E TypeError: BaseEventLoop.create_datagram_endpoint() got > an unexpected keyword argument 'reuse_address' > > test/test_server_asyncio.py:142: TypeError >
Bug#1029367: pdns-recursor: CVE-2023-22617
Source: pdns-recursor Version: 4.8.0-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for pdns-recursor. CVE-2023-22617[0]: | A remote attacker might be able to cause infinite recursion in | PowerDNS Recursor 4.8.0 via a DNS query that retrieves DS records for | a misconfigured domain, because QName minimization is used in QM | fallback mode. This is fixed in 4.8.1. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-22617 https://www.cve.org/CVERecord?id=CVE-2023-22617 [1] https://www.openwall.com/lists/oss-security/2023/01/20/1 [2] https://downloads.powerdns.com/patches/2023-01/ [3] https://github.com/PowerDNS/pdns/pull/12442 Regards, Salvatore
Bug#1028699: marked as done (bustle: FTBFS: pcap-reader.c:238: undefined reference to `pcap_open_offline')
Your message dated Sat, 21 Jan 2023 20:51:31 + with message-id and subject line Bug#1028699: fixed in bustle 0.8.0-2 has caused the Debian Bug report #1028699, regarding bustle: FTBFS: pcap-reader.c:238: undefined reference to `pcap_open_offline' 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.) -- 1028699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bustle Version: 0.8.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccCLNMJy.o: in function `initable_init': > /<>/c-sources/pcap-reader.c:238: undefined reference to > `pcap_open_offline' > /usr/bin/ld: /<>/c-sources/pcap-reader.c:254: undefined > reference to `pcap_datalink' > /usr/bin/ld: /<>/c-sources/pcap-reader.c:257: undefined > reference to `pcap_datalink_val_to_name' > /usr/bin/ld: /<>/c-sources/pcap-reader.c:242: undefined > reference to `pcap_fopen_offline' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/01/13/bustle_0.8.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=lu...@debian.org=1=1=1=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: bustle Source-Version: 0.8.0-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of bustle, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated bustle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 22:28:17 +0200 Source: bustle Architecture: source Version: 0.8.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 1028699 Changes: bustle (0.8.0-2) unstable; urgency=medium . * Declare compliance with Debian policy 4.6.1 * Patch to compile with newer libpcap (Closes: #1028699) Checksums-Sha1: 22492eb4c8759d8758ec62913c8b1d4cdd66379d 2285 bustle_0.8.0-2.dsc 98880ef380dd07311f40e6e898cedc9e074365eb 6020 bustle_0.8.0-2.debian.tar.xz 231ab4c033f0c5145935d7d177e36db98be5a5b8 15849 bustle_0.8.0-2_amd64.buildinfo Checksums-Sha256: 83a7763f82b9eae41beefc0ebf5b9a87fb003f42f023e89c2275e81762a2faad 2285 bustle_0.8.0-2.dsc 1d76d95fd8beb820ae8e9ab96f73175790beaf5de184d86ef7e2e99ef3bfdce6 6020 bustle_0.8.0-2.debian.tar.xz a1026ab04a375e3d76ad3a5c4614ce2077baaf4b521f19d3bf7b8e23852e2f52 15849 bustle_0.8.0-2_amd64.buildinfo Files: cd732b4a8174deded5765bc1bd9a3c92 2285 devel optional bustle_0.8.0-2.dsc 010a426e8f8dac3748b7b61cab459b83 6020 devel optional bustle_0.8.0-2.debian.tar.xz f69c2d1cc08cc720b6ed3e22bbe1bcab 15849 devel optional bustle_0.8.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmPMS5YUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDxsIg/+OxkycTBtUtXLbsOTqWPbhAGLwNCc t2/urAIvRnakx895M4fH/JgrxooUIz3Ey2ETUlM/YuCJbjWZounvtva6HW2gMbo3 W8iJRJoQHdTM9Hb6E97q8euZKaEYB7x/RP4+BGE8tNHwWYJL/GDIdbjU+7b3fcke x8yN4SGVx9sZ3aaCkGdA96oZq4dS0YNzOAX6zKtYjuudfHO9+QW97sAdfJBIOzGw uihuL4VMXv97nyJu4O1KFw6Ww9OMzWCivqRJbQxbeD7EKbgyXY6yaRcg4B4T2LHA qQl4FdqWQb5lVQZYmI8Mr48T7U/6sWrb5oZXhC4+P4S8W1lO2c7ABEIqbk8w6w4Z
Bug#1016963: Please test u-boot for sopine_baseboard
Sorry for the delay in getting back! I can verify the following u-boot versions work with the sopine baseboard: 2022.04+dfsg-2 2023.01+dfsg-1 2023.01+dfsg-2 Thanks! On 2022-12-28 19:26, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: On 2022-12-22, Vagrant Cascadian wrote: On 2022-08-20, Vagrant Cascadian wrote: On 2022-08-10, Vagrant Cascadian wrote: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze approaches, this is getting to be... worrysome! If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... ...and if not successful, filing bugs against the relevent u-boot-* packages and marking them as blocking 1016963. sopine_baseboard live well, vagrant
Processed: python-configshell-fb: diff for NMU version 1:1.1.28-2.1
Processing control commands: > tags 1028996 + pending Bug #1028996 [src:python-configshell-fb] python-configshell-fb: (autopkgtest) needs update for Python 3.11 Added tag(s) pending. -- 1028996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028996: python-configshell-fb: diff for NMU version 1:1.1.28-2.1
Control: tags 1028996 + pending
Dear maintainer,
I've prepared an NMU for python-configshell-fb (versioned as 1:1.1.28-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru python-configshell-fb-1.1.28/debian/changelog python-configshell-fb-1.1.28/debian/changelog
--- python-configshell-fb-1.1.28/debian/changelog 2021-01-23 01:31:23.0 +0100
+++ python-configshell-fb-1.1.28/debian/changelog 2023-01-21 21:29:09.0 +0100
@@ -1,3 +1,12 @@
+python-configshell-fb (1:1.1.28-2.1) unstable; urgency=medium
+
+ [ Bas Couwenberg ]
+ * Non-maintainer upload.
+ * Add upstream patches to fix test failure with python3.11.
+(Closes: #1028996)
+
+ -- Sebastian Ramacher Sat, 21 Jan 2023 21:29:09 +0100
+
python-configshell-fb (1:1.1.28-2) unstable; urgency=medium
* d/t/control: Remove "Tests" header. Use "@" as "Depends".
diff -Nru python-configshell-fb-1.1.28/debian/patches/replace-getargspec-with-getfullargspec.patch python-configshell-fb-1.1.28/debian/patches/replace-getargspec-with-getfullargspec.patch
--- python-configshell-fb-1.1.28/debian/patches/replace-getargspec-with-getfullargspec.patch 1970-01-01 01:00:00.0 +0100
+++ python-configshell-fb-1.1.28/debian/patches/replace-getargspec-with-getfullargspec.patch 2023-01-21 21:29:07.0 +0100
@@ -0,0 +1,31 @@
+Description: replace getargspec() with getfullargspec()
+ inspect.getargspec() doesn't work anymore with Python3.11
+Author: Maurizio Lombardi
+Origin: https://github.com/open-iscsi/configshell-fb/commit/f3ac914861bd605e3d634aeeb5e706abdbd39259
+Forwarded: not-needed
+Bug-Debian: https://bugs.debian.org/1028996
+
+--- a/configshell/node.py
b/configshell/node.py
+@@ -1417,10 +1417,10 @@ class ConfigNode(object):
+ @type kparams: dict
+ @raise ExecutionError: When the check fails.
+ '''
+-spec = inspect.getargspec(method)
++spec = inspect.getfullargspec(method)
+ args = spec.args[1:]
+ pp = spec.varargs
+-kw = spec.keywords
++kw = spec.varkw
+
+ if spec.defaults is None:
+ nb_opt_params = 0
+@@ -1460,7 +1460,7 @@ class ConfigNode(object):
+ "Missing required parameters %s"
+ % ", ".join("'%s'" % missing for missing in missing_params))
+
+-if spec.keywords is None:
++if kw is None:
+ if len(unexpected_keywords) == 1:
+ raise ExecutionError(
+ "Unexpected keyword parameter '%s'."
diff -Nru python-configshell-fb-1.1.28/debian/patches/replace-more-occurrences-of-getargspec-with-getfullargspec.patch python-configshell-fb-1.1.28/debian/patches/replace-more-occurrences-of-getargspec-with-getfullargspec.patch
--- python-configshell-fb-1.1.28/debian/patches/replace-more-occurrences-of-getargspec-with-getfullargspec.patch 1970-01-01 01:00:00.0 +0100
+++ python-configshell-fb-1.1.28/debian/patches/replace-more-occurrences-of-getargspec-with-getfullargspec.patch 2023-01-21 21:29:07.0 +0100
@@ -0,0 +1,70 @@
+Description: Replace more occurrences of getargspec() with getfullargspec()
+ Follow up for f3ac914861bd605e3d634aeeb5e706abdbd39259, getargspec was used at two more places.
+Author: Vojtech Trefny
+Origin: https://github.com/open-iscsi/configshell-fb/commit/343e46cbbbed339c67fe969cdf443af4c979f43e
+Forwarded: not-needed
+Bug-Debian: https://bugs.debian.org/1028996
+
+--- a/configshell/node.py
b/configshell/node.py
+@@ -1575,12 +1575,12 @@ class ConfigNode(object):
+ @type command: str
+ '''
+ method = self.get_command_method(command)
+-parameters, args, kwargs, default = inspect.getargspec(method)
+-parameters = parameters[1:]
+-if default is None:
++spec = inspect.getfullargspec(method)
++parameters = spec.args[1:]
++if spec.defaults is None:
+ num_defaults = 0
+ else:
+-num_defaults = len(default)
++num_defaults = len(spec.defaults)
+
+ if num_defaults != 0:
+ required_parameters = parameters[:-num_defaults]
+@@ -1605,16 +1605,16 @@ class ConfigNode(object):
+ syntax += optional_parameters_str
+
+ comments = []
+-if args is not None:
+-syntax += "[%s...] " % args
+-if kwargs is not None:
+-syntax += "[%s=value...] " % (kwargs)
++if spec.varargs is not None:
++syntax += "[%s...] " % spec.varargs
++if spec.varkw is not None:
++syntax += "[%s=value...] " % (spec.varkw)
+
+ default_values = ''
+ if num_defaults > 0:
+ for index, param in enumerate(optional_parameters):
+-if default[index] is not None:
+-default_values += "%s=%s " % (param, str(default[index]))
++if spec.defaults[index] is not None:
++
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
Hi! I have been frantically trying to reproduce the issue you reported. Would you be able to describe more in detail what was the situation before and after you upgraded and what commands exactly did you do to execute the upgrade (apt upgrade, apt full-upgrade, apt-get, aptitude)? We might very well have a broken upgrade scenario but for me to be able to fix it I need to have a way to reproduce it so I can validate a potential fix.
Bug#1016963: Please test u-boot for dreamplug
On 2022-12-29, Ian Campbell wrote: > On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote: >> dreamplug > > booting u-boot and Debian both from external mmc > > testing: 2022.04+dfsg-2+b1 "FDT and ATAGS support not compiled in" then > resets and loops doing that > unstable: 2022.10+dfsg-2 ok > exp: 2023.01~rc4+dfsg-1 ok Any chance you could test 2023.01+dfsg-1 and/or 2023.01+dfsg-2 on the dreamplug? Someone had problems with sheevaplug, which I think is a fairly similar platform. live well, vagrant signature.asc Description: PGP signature
Bug#1028619: marked as pending in rich
Control: tag -1 pending Hello, Bug #1028619 in rich 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/rich/-/commit/694a0d14de73e9a48f3f5da0f97a21720b3c7689 Add patch for pygments 2.14.0 Closes: #1028619 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028619
Processed: Bug#1028619 marked as pending in rich
Processing control commands: > tag -1 pending Bug #1028619 [src:rich] rich: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1 Added tag(s) pending. -- 1028619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028882: marked as done (ufo2ft: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13)
Your message dated Sat, 21 Jan 2023 19:53:03 +
with message-id
and subject line Bug#1028882: fixed in ufo2ft 2.30.0-1
has caused the Debian Bug report #1028882,
regarding ufo2ft: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.11" 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.)
--
1028882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ufo2ft
Version: 2.28.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 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_test
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.10_ufo2ft/build;
> python3.10 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.10.9, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>, configfile: setup.cfg
> collected 655 items
>
> tests/featureCompiler_test.py . [
> 1%]
> tests/fontInfoData_test.py ... [
> 4%]
> tests/integration_test.py .s.s..F[
> 10%]
> tests/outlineCompiler_test.py .. [
> 16%]
> ... [
> 23%]
> tests/preProcessor_test.py s.s...[
> 27%]
> tests/featureWriters/cursFeatureWriter_test.py ... [
> 27%]
> tests/featureWriters/featureWriters_test.py [
> 28%]
> tests/featureWriters/gdefFeatureWriter_test.py ..[
> 30%]
> tests/featureWriters/kernFeatureWriter_test.py . [
> 34%]
> [
> 34%]
> tests/featureWriters/markFeatureWriter_test.py . [
> 38%]
> .[
> 38%]
> tests/filters/decomposeComponents_test.py .. [
> 38%]
> tests/filters/decomposeTransformedComponents_test.py ... [
> 38%]
> tests/filters/dottedCircle_test.py . [
> 39%]
> tests/filters/flattenComponents_test.py [
> 40%]
> tests/filters/propagateAnchors_test.py . [
> 42%]
> tests/filters/sortContours_test.py [
> 42%]
> tests/filters/transformations_test.py ...[
> 47%]
> tests/featureCompiler_test.py . [
> 49%]
> tests/fontInfoData_test.py ... [
> 51%]
> tests/integration_test.py .s.s..F[
> 57%]
> tests/outlineCompiler_test.py .. [
> 64%]
> ... [
> 71%]
> tests/preProcessor_test.py s.s...[
> 74%]
> tests/featureWriters/cursFeatureWriter_test.py ... [
> 75%]
> tests/featureWriters/featureWriters_test.py [
> 76%]
> tests/featureWriters/gdefFeatureWriter_test.py ..[
> 78%]
> tests/featureWriters/kernFeatureWriter_test.py . [
> 81%]
> [
> 81%]
> tests/featureWriters/markFeatureWriter_test.py . [
> 85%]
> .[
> 85%]
> tests/filters/decomposeComponents_test.py .. [
> 86%]
> tests/filters/decomposeTransformedComponents_test.py ... [
> 86%]
> tests/filters/dottedCircle_test.py . [
> 86%]
> tests/filters/flattenComponents_test.py [
> 87%]
> tests/filters/propagateAnchors_test.py . [
> 89%]
> tests/filters/sortContours_test.py [
> 90%]
> tests/filters/transformations_test.py ...[
> 95%]
> tests/fontInfoData_test.py ..
Bug#1020019: marked as done (spring: FTBFS: sdlstub.c:291:30: error: conflicting types for ‘SDL_SetTextInputRect’; have ‘void(SDL_Rect *)’)
Your message dated Sat, 21 Jan 2023 19:52:32 +
with message-id
and subject line Bug#1020019: fixed in spring 106.0+dfsg-1
has caused the Debian Bug report #1020019,
regarding spring: FTBFS: sdlstub.c:291:30: error: conflicting types for
‘SDL_SetTextInputRect’; have ‘void(SDL_Rect *)’
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.)
--
1020019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spring
Version: 105.0.1+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/rts/lib/streflop && /usr/bin/c++
> -DASIO_STANDALONE
> -DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSTREFLOP_SSE
> -DSYNCCHECK -DTHREADPOOL -D_GLIBCXX_USE_NANOSLEEP -D_RANDOM_TCC
> -I/<>/rts -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -std=c++17 -fdiagnostics-color=auto -march=x86-64 -msse
> -mfpmath=sse -mno-sse2 -mno-sse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-sse4
> -mno-sse4a -mno-avx -mno-fma -mno-fma4 -mno-xop -mno-lwp -mno-avx2
> -fsingle-precision-constant -frounding-math -mieee-fp -pipe
> -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden
> -pthread -O2 -Wformat -Wformat-security -DNDEBUG -g -fpic
> -DLIBM_COMPILING_FLT32 -I"/<>/rts/lib/streflop/libm/headers" -w
> -O3 -mfpmath=sse -msse -MD -MT
> rts/lib/streflop/CMakeFiles/streflop.dir/libm/flt-32/e_jnf.cpp.o -MF
> CMakeFiles/streflop.dir/libm/flt-32/e_jnf.cpp.o.d -o
> CMakeFiles/streflop.dir/libm/flt-32/e_jnf.cpp.o -c
> /<>/rts/lib/streflop/libm/flt-32/e_jnf.cpp
> /<>/rts/lib/headlessStubs/sdlstub.c:291:30: error: conflicting
> types for ‘SDL_SetTextInputRect’; have ‘void(SDL_Rect *)’
> 291 | extern DECLSPEC void SDLCALL SDL_SetTextInputRect(SDL_Rect *rect) {
> | ^~~~
> In file included from /usr/include/SDL2/SDL_events.h:34,
> from /usr/include/SDL2/SDL.h:41,
> from /<>/rts/lib/headlessStubs/sdlstub.c:8:
> /usr/include/SDL2/SDL_keyboard.h:318:30: note: previous declaration of
> ‘SDL_SetTextInputRect’ with type ‘void(const SDL_Rect *)’
> 318 | extern DECLSPEC void SDLCALL SDL_SetTextInputRect(const SDL_Rect
> *rect);
> | ^~~~
> make[4]: ***
> [rts/lib/headlessStubs/CMakeFiles/headlessStubs.dir/build.make:107:
> rts/lib/headlessStubs/CMakeFiles/headlessStubs.dir/sdlstub.c.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/09/17/spring_105.0.1+dfsg-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=lu...@debian.org=1=1=1=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 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 ---
Source: spring
Source-Version: 106.0+dfsg-1
Done: Markus Koschany
We believe that the bug you reported is fixed in the latest version of
spring, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Koschany (supplier of updated spring package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 21 Jan 2023 17:08:46 +0100
Source: spring
Architecture: source
Version: 106.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer:
Bug#1027059: marked as done (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))
Your message dated Sat, 21 Jan 2023 19:50:56 + with message-id and subject line Bug#1027059: fixed in ruby-rash-alt 0.4.12-1 has caused the Debian Bug report #1027059, regarding 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) 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.) -- 1027059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rash-alt Version: 0.4.3-1.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-hashie-5.0.0 Hi, After updating ruby-hashie to 5.0.0-1, ruby-rash-alt fails to build. Relevant part of the build log (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block > in activate_dependencies': Could not find 'hashie' (~> 3.4) among 98 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-rash-alt/usr/share/rubygems-integration/all:/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' > at: > /<>/debian/ruby-rash-alt/usr/share/rubygems-integration/all/specifications/rash_alt-0.4.3.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'hashie' (~> 3.4) - did find: [hashie-5.0.0] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-rash-alt/usr/share/rubygems-integration/all:/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' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > abbrev (default: 0.1.0) > base64 (default: 0.1.1) > benchmark (default: 0.2.0) > bigdecimal (default: 3.1.1) > bundler (default: 2.3.7) > cgi (default: 0.3.1) > csv (default: 3.2.2) > date (default: 3.2.2) > debug (1.4.0) > delegate (default: 0.2.0) > did_you_mean (default: 1.6.1) > diff-lcs (1.5.0) > digest (default: 3.1.0) > drb (default: 2.1.0) > english (default: 0.7.1) > erb (default: 2.2.3) > error_highlight (default: 0.3.0) > etc (default: 1.3.0) > fcntl (default: 1.0.1) > fiddle (default: 1.1.0) > fileutils (default: 1.6.0) > find (default: 0.1.1) > forwardable (default: 1.3.2) > getoptlong (default: 0.1.1) > hashie (5.0.0) > io-console (default: 0.5.11) > io-nonblock (default: 0.1.0) > io-wait (default: 0.2.1) > ipaddr (default: 1.2.4) > irb (default: 1.4.1) > json (default: 2.6.1) > logger (default: 1.5.0) > matrix (0.4.2) > minitest (5.15.0) > mutex_m (default: 0.1.1) > net-ftp (0.1.3) > net-http (default: 0.2.0) > net-imap (0.2.3) > net-pop (0.1.1) > net-protocol (default: 0.1.2) > net-smtp (0.3.1) > net-telnet (0.1.1) > nkf (default: 0.1.1) > observer (default: 0.1.1) > open-uri (default: 0.2.0) > open3 (default: 0.1.1) > openssl (default: 3.0.0) > optparse (default: 0.2.0) > ostruct
Bug#1029316: marked as done (r-cran-spatstat.core: autopkgtest regression in testing)
Your message dated Sat, 21 Jan 2023 19:49:02 + with message-id and subject line Bug#1029316: fixed in r-cran-spatstat.core 2.4-4-2 has caused the Debian Bug report #1029316, regarding r-cran-spatstat.core: autopkgtest regression in testing 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.) -- 1029316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-spatstat.core Version: 2.4-4-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Somehow, r-cran-spatstat.core has regressed its autopkgtests in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-spatstat.core/testing/amd64/ Loading required namespace: spatstat.model Failed with error: ‘there is no package called ‘spatstat.model’’ The package 'spatstat.model' is required Error in info$selfstart(X) : attempt to apply non-function Calls: local ... eval -> kppm -> kppm.ppp -> kppmMinCon -> clusterfit Execution halted autopkgtest [23:24:25]: test run-unit-test: ---] autopkgtest [23:24:25]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: r-cran-spatstat.core Source-Version: 2.4-4-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-spatstat.core, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-spatstat.core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 21 Jan 2023 17:57:23 +0100 Source: r-cran-spatstat.core Architecture: source Version: 2.4-4-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1029316 Changes: r-cran-spatstat.core (2.4-4-2) unstable; urgency=medium . * Sync Suggests with Test-Depends Closes: #1029316 * Versioned Build-Depends from non-broken dh-r (>= 20230121) Checksums-Sha1: a90c3f92fb4c62a7d56d0f16f6c7fea9706d7f84 2630 r-cran-spatstat.core_2.4-4-2.dsc 29568040845dee821475b14aa1cdf1465958c7e2 3988 r-cran-spatstat.core_2.4-4-2.debian.tar.xz 372d40d84b41f9bb0f0616a643e3458f3a16a257 11317 r-cran-spatstat.core_2.4-4-2_amd64.buildinfo Checksums-Sha256: 493662ad52507891941a3ecd57518951e2343be93b1f8a4d8b00f3f10c5426a9 2630 r-cran-spatstat.core_2.4-4-2.dsc 740a58dcb32291525f75038288bb93fda36fd790cc3cd66544496c783a98c777 3988 r-cran-spatstat.core_2.4-4-2.debian.tar.xz 57c660b57f7673c621c3b7b5e4d782d910b6b780d2d54fce796550171b289801 11317 r-cran-spatstat.core_2.4-4-2_amd64.buildinfo Files: 617510b6d7df04c8175ffea12ae5961d 2630 gnu-r optional r-cran-spatstat.core_2.4-4-2.dsc a312cca05c8a9d186b8410536bbfa969 3988 gnu-r optional r-cran-spatstat.core_2.4-4-2.debian.tar.xz 1d3fdd0f7fcddbb486c65c9b38af60f0 11317 gnu-r optional r-cran-spatstat.core_2.4-4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPMGroRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGwJQ/+JmPC+8CiLWKLYVisSBao0pBu1tvzwRG6 AjS/WKF3us1HBRKIeQN5ES7s0mtF0qWhfLV8fHjiW0NM1lV8ItWeUQgAoXnohjPa rvQWaVZpenrQkV1b1rDUNpIZLhk+94U25Al2av1+Otp+zhcjcm2zCf8tIHO7rD5l g2F4kNvyIi/6bAb9v5AUlQ0Yk/I/bkQL9UsGQxQe7sIZ3sORX90w9qjj7Fs/6jUm h5sd9An+vT6lTQh+i8o1mSLRUobwCTzyrJK8aTlmRLwOSfmMZJQKbb1VJKwZbmIG /xMh90qEf24Nb5AYUPEtO9z/t1DOhBAJLy0Ho5XEqQbM+xkaTuiOvBtWmlx2OIl/ QbR7Zsj5Z7B+rN9hMJD5q7cfMNmgIJ3VW/00CNs06ObaKAKfWTG3kXw75mowrpnT 2/9/bQiPlWxFwC7J9yfyn1oVCboV1wyOD4ziF3chWWXJmeENgKE3tHl8sLHAF4q+ 3np+DQILG4qQzU1EAqlOk07bgSuzmj1XshiDsspeWm+DF99+gk90zgbjv0Iw9CzU gc+uIy0zXiY6M94wVK3aFFmJla10q94vtgrFnAc0UrS1fRMnAXOQkaPEpP7d2jeY a7HmJaek9lawOmJEM5mLGe1Z4qMDwofrQ5Wi8H2E4VrP0wDvdgHrBlWbkNX5SYYk ONAA9/jbGXU= =uLAu -END PGP SIGNATURE End Message ---
Bug#1028837: marked as done (python-zstandard: FTBFS: ModuleNotFoundError: No module named 'exceptiongroup')
Your message dated Sat, 21 Jan 2023 19:44:15 + with message-id and subject line Bug#1028837: fixed in python-zstandard 0.19.0-2 has caused the Debian Bug report #1028837, regarding python-zstandard: FTBFS: ModuleNotFoundError: No module named 'exceptiongroup' 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.) -- 1028837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-zstandard Version: 0.19.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 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 '/<>' > cd docs; LC_ALL=C.UTF-8 LANGUAGE=C.UTF-8 sphinx-build -bhtml . _build/html > Running Sphinx v5.3.0 > making output directory... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 14 source files that are out of date > updating environment: [new config] 14 added, 0 changed, 0 removed > reading sources... [ 7%] api_usage > reading sources... [ 14%] buffer > reading sources... [ 21%] compression_parameters > reading sources... [ 28%] compressor > reading sources... [ 35%] concepts > reading sources... [ 42%] contributing > reading sources... [ 50%] decompressor > reading sources... [ 57%] dictionaries > reading sources... [ 64%] index > reading sources... [ 71%] installing > reading sources... [ 78%] misc_apis > reading sources... [ 85%] multithreaded > reading sources... [ 92%] news > reading sources... [100%] projectinfo > > WARNING: autodoc: failed to import class 'BufferSegment' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'BufferSegments' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'BufferWithSegments' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'BufferWithSegmentsCollection' from > module 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdCompressionParameters' from > module 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdCompressor' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdCompressionWriter' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdCompressionReader' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdCompressionObj' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdCompressionChunker' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdDecompressor' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdDecompressionWriter' from > module 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdDecompressionReader' from > module 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdDecompressionObj' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import class 'ZstdCompressionDict' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import function 'train_dictionary' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import function 'get_frame_parameters' from > module 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import function 'frame_header_size' from module > 'zstandard'; the following exception was raised: > No module named 'zstandard' > WARNING: autodoc: failed to import function
Bug#1029242: marked as done (pymca: FTBFS: AttributeError: module 'numpy' has no attribute 'float')
Your message dated Sat, 21 Jan 2023 19:43:40 +
with message-id
and subject line Bug#1029242: fixed in pymca 5.8.0+dfsg-2
has caused the Debian Bug report #1029242,
regarding pymca: FTBFS: AttributeError: module 'numpy' has no attribute 'float'
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.)
--
1029242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymca
Version: 5.8.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230120 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 '/<>'
> pybuild --test -s custom -p 3.11 --test-args="cd {build_dir} &&
> PYMCA_DATA_DIR=/<>/PyMca5/PyMcaData/
> PYMCA_DOC_DIR=/<>/PyMca5/PyMcaData/ xvfb-run -a
> --server-args=\"-screen 0 1024x768x24\" {interpreter} PyMca5/tests/TestAll.py"
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_pymca5/build
> && PYMCA_DATA_DIR=/<>/PyMca5/PyMcaData/
> PYMCA_DOC_DIR=/<>/PyMca5/PyMcaData/ xvfb-run -a
> --server-args="-screen 0 1024x768x24" python3.11 PyMca5/tests/TestAll.py
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user42'
> testEdfMap (XrfDataTest.testXrfData.testEdfMap) ... ok
> testHdf5Map (XrfDataTest.testXrfData.testHdf5Map) ... ok
> testSpecMesh (XrfDataTest.testXrfData.testSpecMesh) ... ok
> testNoSave (XRFBatchFitOutputTest.testXRFBatchFitOutput.testNoSave) ... ok
> testOutputFormats
> (XRFBatchFitOutputTest.testXRFBatchFitOutput.testOutputFormats) ... ok
> testOverwrite (XRFBatchFitOutputTest.testXRFBatchFitOutput.testOverwrite) ...
> ok
> testEdfFileImport (EdfFileTest.testEdfFile.testEdfFileImport) ... ok
> testEdfFileReadWrite (EdfFileTest.testEdfFile.testEdfFileReadWrite) ... ok
> testDataDirectoryPresence (DataTest.testData.testDataDirectoryPresence) ... ok
> testDataFilePresence (DataTest.testData.testDataFilePresence) ... ok
> testDocDirectoryPresence (DataTest.testData.testDocDirectoryPresence) ... ok
> testFisxDataDirectoryPresence
> (DataTest.testData.testFisxDataDirectoryPresence) ... ok
> testInteractionMpl
> (McaAdvancedFitWidgetTest.TestMcaAdvancedFitWidget.testInteractionMpl) ... ok
> testInteractionOpenGL
> (McaAdvancedFitWidgetTest.TestMcaAdvancedFitWidget.testInteractionOpenGL) ...
> skipped 'silx not installed'
> testInteractionSilxGL
> (McaAdvancedFitWidgetTest.TestMcaAdvancedFitWidget.testInteractionSilxGL) ...
> skipped 'silx and/or OpenGL disabled'
> testInteractionSilxMpl
> (McaAdvancedFitWidgetTest.TestMcaAdvancedFitWidget.testInteractionSilxMpl)
> ... skipped 'silx not installed'
> testSpecfilewrapperImport
> (specfilewrapperTest.testSpecfilewrapper.testSpecfilewrapperImport) ... ok
> testSpecfilewrapperReading
> (specfilewrapperTest.testSpecfilewrapper.testSpecfilewrapperReading) ... ok
> testSpecfilewrapperReadingCompatibleWithUserLocale
> (specfilewrapperTest.testSpecfilewrapper.testSpecfilewrapperReadingCompatibleWithUserLocale)
> ... ok
> testTrainingSpectrumReading
> (specfilewrapperTest.testSpecfilewrapper.testTrainingSpectrumReading) ... ok
> testPeakNegativeX (ROIBatchTest.testROIBatch.testPeakNegativeX) ... ERROR
> testPeakPositiveX (ROIBatchTest.testROIBatch.testPeakPositiveX) ... ERROR
> testSingleArrayExport
> (McaStackExportTest.testMcaStackExport.testSingleArrayExport) ... ok
> testSingleStackExport
> (McaStackExportTest.testMcaStackExport.testSingleStackExport) ... ok
> testGefitImport (GefitTest.testGefit.testGefitImport) ... ok
> testGefitLeastSquares (GefitTest.testGefit.testGefitLeastSquares) ... ok
> testConfigDictIO (ConfigDictTest.testConfigDict.testConfigDictIO) ... ok
> testConfigDictImport (ConfigDictTest.testConfigDict.testConfigDictImport) ...
> ok
> testHdf5Uri (ConfigDictTest.testConfigDict.testHdf5Uri) ... ok
> testDataDirectoryPresence
> (ElementsTest.testElements.testDataDirectoryPresence) ... ok
> testElementCrossSectionsCalculation
> (ElementsTest.testElements.testElementCrossSectionsCalculation) ... ok
> testElementCrossSectionsReadout
> (ElementsTest.testElements.testElementCrossSectionsReadout) ... ok
> testMaterialCompositionCalculation
> (ElementsTest.testElements.testMaterialCompositionCalculation) ... ok
> testMaterialCrossSectionsCalculation
> (ElementsTest.testElements.testMaterialCrossSectionsCalculation) ... ok
> testPeakIdentification (ElementsTest.testElements.testPeakIdentification) ...
> ok
> testNxData
Bug#1027240: marked as done (pymca: autopkgtest fail with numpy/1.24.1)
Your message dated Sat, 21 Jan 2023 19:43:40 + with message-id and subject line Bug#1027240: fixed in pymca 5.8.0+dfsg-2 has caused the Debian Bug report #1027240, regarding pymca: autopkgtest fail with numpy/1.24.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.) -- 1027240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pymca Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: pymca Source-Version: 5.8.0+dfsg-2 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of pymca, 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. Dmitry Shachnev (supplier of updated pymca package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 21:52:14 +0400 Source: pymca Architecture: source Version: 5.8.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian PaN Maintainers Changed-By: Dmitry Shachnev Closes: 1027240 1029242 Changes: pymca (5.8.0+dfsg-2) unstable; urgency=medium . * Team upload. . [ Bas Couwenberg ] * Add gbp.conf to use pristine-tar & --source-only-changes by default. * Add upstream patch to fix test failure with Numpy 1.24. (closes: #1027240, #1029242) Checksums-Sha1: 01504883bc515935f5b71e3ef148445e06045b0f 2710 pymca_5.8.0+dfsg-2.dsc 7dc5a7e7dcf169d1a31979b01daf0a71c32d50b7 11824 pymca_5.8.0+dfsg-2.debian.tar.xz 0d86f932237bd4d9d01d9a0238c69c5ce29abf4f 14403 pymca_5.8.0+dfsg-2_source.buildinfo Checksums-Sha256: 99713880fbab62ab1b40dcf215978669465f09f5bd8a6ab254e8599c2e9a675a 2710 pymca_5.8.0+dfsg-2.dsc c1466f44182d09621b5283f46f9f299ca341d60b6ed732baffbabd6151a2c9ad 11824 pymca_5.8.0+dfsg-2.debian.tar.xz 1e324d0b0e56730817cc9a5064700f8e4f8e4e0d28e33f354e631feacb14e76f 14403 pymca_5.8.0+dfsg-2_source.buildinfo Files: b91133e55839a5721f1e2bee4d40cf85 2710 science optional pymca_5.8.0+dfsg-2.dsc 3eed564048f666f159f6f0ee7b112e7b 11824 science optional pymca_5.8.0+dfsg-2.debian.tar.xz c0a85f96b75e8ee4a32687384d17679a 14403 science optional pymca_5.8.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmPMJq0THG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBmRiZbWGuDy5XLD/9A1c/k+QU7rLxCS+8nPF8em6JU7F3A WviWsaV0Fv5CfIbJ/+0zN/P3wHR4Q45ci5t2qT6Watah8kWnRKjvr+oHWWmg94lU Az1LVNk4LgeoRzLb+wTWLhYH18zZdnTbe8y7LVYJ1DgOfhGJ2xnGWsKeps6lvJ9S zipsvkusrdxeStLVE7BR+CTWhfJFDPvsjoYRIjIyZX0YuaP2xGKatBOqQLzSXN6c YZAzzim86Ne19szIlJUGiQ0/AW1+O/4IJgBklscAtGh47xPZslOycJ1EOixa/u6A 5aL8EXAj5JoWhObELNWGoIR4cezOxPLt+6MFv2IrBQHLvpz0Ls+EKmFmQ0tmDodg 3muz3qwizOuHghNW16cEpabmWoyefW28OV52AcpM8B3LAryTpC+n8CRC7Mr9agge q57Gc+Zr9sldt0eBktndjDe/ZM3tuSgERpPzekQ3IRLLN5q7FCkNyICQMoKK+NwA
Bug#1028478: marked as done (python-docutils: FTBFS with python 3.11: FAIL: test_local)
Your message dated Sat, 21 Jan 2023 19:43:55 + with message-id and subject line Bug#1028478: fixed in python-docutils 0.19+dfsg-3 has caused the Debian Bug report #1028478, regarding python-docutils: FTBFS with python 3.11: FAIL: test_local 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.) -- 1028478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-docutils Version: 0.19+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, python-docutils/experimental FTBFS with python 3.11: FAIL: test_local (__main__.BuildHtmlTests.test_local) -- Traceback (most recent call last): File "/build/python-docutils-0.19+dfsg/tools/test/test_buildhtml.py", line 105, in test_local self.assertEqual(len(dirs), 1) AssertionError: 2 != 1 Andreas python-docutils_0.19+dfsg-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-docutils Source-Version: 0.19+dfsg-3 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of python-docutils, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated python-docutils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 20:08:40 +0400 Source: python-docutils Architecture: source Version: 0.19+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Dmitry Shachnev Closes: 1018737 1028478 Changes: python-docutils (0.19+dfsg-3) unstable; urgency=medium . * Ignore DeprecationWarnings when running test_buildhtml.py (closes: #1028478). * Abort the build when getting --help of some command fails. * Add a patch to fix FileNotFoundError when generating manpages. * Break python3-m2r < 0.3 (see #1026288). * Break ruby-github-markup < 1.7.0+dfsg-5 (see #1013383). * Backport upstream patch to not pass empty "manual" argument to the .TH macro (closes: #1018737). * Bump Standards-Version to 4.6.2, no changes needed. * Upload to unstable. Checksums-Sha1: 461112dfbdfcdd662ca1b5e14c8332600dfa 2354 python-docutils_0.19+dfsg-3.dsc 1f9ea0e42f66f83aa46723dea96f48fd5d450fc6 32560 python-docutils_0.19+dfsg-3.debian.tar.xz cffada9a56b9e145e731bf1e297a036bd1eb3b05 5919 python-docutils_0.19+dfsg-3_source.buildinfo Checksums-Sha256: b6ef608e5f71264bd296c376327b5e5c809e638af35b493460cadfd91c4a072a 2354 python-docutils_0.19+dfsg-3.dsc b5c7720484ac74954a69018935a8ce8c262d4d10d356f3d9f6c778bf5aeb0ac6 32560 python-docutils_0.19+dfsg-3.debian.tar.xz 2cecf441a3205072c473f8a478e74bdba0eb08a6b0df5b2d686c0d2138b9a54c 5919 python-docutils_0.19+dfsg-3_source.buildinfo Files: 254ba87ec7717acd0f086d63ed85395e 2354 python optional python-docutils_0.19+dfsg-3.dsc 970e36c0908c7526c3c17f745f67f2ba 32560 python optional python-docutils_0.19+dfsg-3.debian.tar.xz c2f7db81d49f1295d85d69cfbdbcb181 5919 python optional python-docutils_0.19+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmPMFE0THG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBmRiZbWGuDy6c0D/9Dw++M12oyAuu20NTCfFQimHoIUcu/ RxGSeIzycw3bmEE1K7SAW5IejchdbDtvaqWrBxDLOGiH/01V38/+/+U+1t3oSo+w 1IPhOR0/v6xYs4fIAnrVnyWNF8akFBe3ZH2BeST3npLGuNQ/Eb2YAe6U9O7sslle 5AMnU2rdRM+lpdQ/mivGG31p7e5k4UdEiYfRSDxivAdGp5WU+p/sYWyNBuAS/cn+ kNuX1RIu/i5WsJBdAkPF1crWebyg6hxEh8aCbZozr/ptPnCLq1SbWvCvjU6KFKGC BbIhC+qx7ak4fULe0H2S9Ecqph/dvfOZTEVXTH+xAKef2VsIpge34l9xK1lio95T oxBsXEmcr/HTezIOCRgnX0DENyEsgzn+Fvaw9RQAkATjf6RHBaodB9qSxVZZhD8i cyZcSPP1PLP79hflbric8LxXWlsTynRIzVoyaWz4TjgTudyaJLyb5IEaEnnpnV3b x3FFHLokYT3/g9a1FruXwxJcgj2QHx6yEIArqci09f2l0AXZtPykf1KMZFBHqkEf pKpF51+6uyIxs3VsvE3aQvOtNA8GflAprxq7RLxyiX4K5+pn0cLXxjqk1I3YOkV+ qGgk7tNNql5evgfB6H3j6XRLFlGiZq+zC9Tv0qKdiQlaIWU2KaaRJJ2tkh3q4+kz Cnve9vW5oIlqzw== =Y4ap -END PGP SIGNATURE End Message ---
Bug#1027235: marked as done (python-pomegranate: autopkgtest fail with numpy/1.24.1)
Your message dated Sat, 21 Jan 2023 19:44:07 + with message-id and subject line Bug#1027235: fixed in python-pomegranate 0.14.8-3 has caused the Debian Bug report #1027235, regarding python-pomegranate: autopkgtest fail with numpy/1.24.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.) -- 1027235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pomegranate Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: python-pomegranate Source-Version: 0.14.8-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of python-pomegranate, 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. Nilesh Patra (supplier of updated python-pomegranate package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 21 Jan 2023 23:29:28 +0530 Source: python-pomegranate Architecture: source Version: 0.14.8-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Nilesh Patra Closes: 1027235 Changes: python-pomegranate (0.14.8-3) unstable; urgency=medium . [ Andreas Tille ] * Team upload. * Make sure watch file reports latest version * Standards-Version: 4.6.2 (routine-update) . [ Nilesh Patra ] * Add patch to make package compatible with np 1.24 (Closes: #1027235) Checksums-Sha1: e2f3f2a5432e6b1245e61f5f2e0014ff7a101985 1956 python-pomegranate_0.14.8-3.dsc 5106f926b075a097e14b9f058d3980fe98933072 38992 python-pomegranate_0.14.8-3.debian.tar.xz ff5c164b58a33429dd76faa78d02b54b588930ad 8172 python-pomegranate_0.14.8-3_amd64.buildinfo Checksums-Sha256: 92764996f55e084f00ec8a234a9fda54358152c59c06d65ad9b3157c0f1d5260 1956 python-pomegranate_0.14.8-3.dsc 88c06364c5d0b10131e6af8a99a588c5bd4af88e9e570a1b707aa126b45430db 38992 python-pomegranate_0.14.8-3.debian.tar.xz 0da3bfecea84115561d790869e9b12353162bfea03be11a6b4125613bc05ed7d 8172 python-pomegranate_0.14.8-3_amd64.buildinfo Files: f7b3dda780f169a0e6659d080e94b104 1956 science optional python-pomegranate_0.14.8-3.dsc cf001201c1255b472af3063b4bf05ea3 38992 science optional python-pomegranate_0.14.8-3.debian.tar.xz b401a3bd46016967100e7c3802352f01 8172 science optional python-pomegranate_0.14.8-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY8wtngAKCRAqJ5BL1yQ+ 2rxgAQCwAA+Kw8ZKh4W6WZLIKreXhqm3E22jX3j/UxKi89gaHQEA9NjMTituyzhL JTi9XIa5eo294ScH6Np9mwFTwAQzzA0= =4MMU -END PGP SIGNATURE End Message ---
Bug#1010095: marked as done (performous: FTBFS on ppc64el)
Your message dated Sat, 21 Jan 2023 19:42:44 + with message-id and subject line Bug#1010095: fixed in performous 1.1+git20181118-6 has caused the Debian Bug report #1010095, regarding performous: FTBFS on ppc64el 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.) -- 1010095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: performous Version: 1.1+git20181118-5 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org performous FTBFS on ppc64el: cd /<>/obj-powerpc64le-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/docs/man /<>/obj-powerpc64le-linux-gnu /<>/obj-powerpc64le-linux-gnu/docs/man /<>/obj-powerpc64le-linux-gnu/docs/man/CMakeFiles/gh_fsb_decrypt.1.dir/DependInfo.cmake --color= In file included from /usr/include/c++/11/bits/stl_algobase.h:63, from /usr/include/c++/11/memory:63, from /<>/ced/compact_enc_det/compact_enc_det.cc:24: /usr/include/c++/11/ext/numeric_traits.h:222:38: error: ‘__ieee128’ was not declared in this scope; did you mean ‘__int128’? 222 | struct __numeric_traits_floating<__ieee128> | ^ | __int128 154 translated messages, 20 fuzzy translations, 138 untranslated messages. /usr/include/c++/11/ext/numeric_traits.h:222:47: error: template argument 1 is invalid 222 | struct __numeric_traits_floating<__ieee128> | ^ make[3]: Leaving directory '/<>/obj-powerpc64le-linux-gnu' /usr/include/c++/11/ext/numeric_traits.h:230:29: error: ‘__ieee128’ was not declared in this scope; did you mean ‘__int128’? 230 | struct __numeric_traits<__ieee128> | ^ | __int128 /usr/include/c++/11/ext/numeric_traits.h:230:38: error: template argument 1 is invalid 230 | struct __numeric_traits<__ieee128> | ^ make[3]: Leaving directory '/<>/obj-powerpc64le-linux-gnu' make -f docs/man/CMakeFiles/ss_chc_decode.1.dir/build.make docs/man/CMakeFiles/ss_chc_decode.1.dir/build make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu' /usr/include/c++/11/ext/numeric_traits.h:231:40: error: ‘__ieee128’ was not declared in this scope; did you mean ‘__int128’? 231 | : public __numeric_traits_floating<__ieee128> |^ |__int128 /usr/include/c++/11/ext/numeric_traits.h:231:49: error: template argument 1 is invalid 231 | : public __numeric_traits_floating<__ieee128> | ^ make[3]: Leaving directory '/<>/obj-powerpc64le-linux-gnu' See https://buildd.debian.org/status/fetch.php?pkg=performous=ppc64el=1.1%2Bgit20181118-5%2Bb1=1650784603=0 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: performous Source-Version: 1.1+git20181118-6 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of performous, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated performous package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 19:20:54 +0100 Source: performous Architecture: source Version: 1.1+git20181118-6 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Closes: 1004616 1010095 Changes: performous (1.1+git20181118-6) unstable; urgency=medium . [ Frédéric Bonnard ] * Remove -mno-altivec on ppc64el as not needed anymore. (Closes: #1010095) . [ Markus Koschany ] * Fix FTBFS with ffmpeg 5. Thanks to Dan Bungert for the patch. (Closes: #1004616) * Declare compliance with Debian Policy 4.6.2. * Switch to
Bug#1004616: marked as done (performous: FTBFS with ffmpeg 5.0)
Your message dated Sat, 21 Jan 2023 19:42:44 + with message-id and subject line Bug#1004616: fixed in performous 1.1+git20181118-6 has caused the Debian Bug report #1004616, regarding performous: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1004616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: performous Version: 1.1+git20181118-5 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm ftbfs Usertags: ffmpeg5.0 performous FTBFS with ffmpeg 5.0 (available in experimental): | cd /<>/obj-x86_64-linux-gnu/game && /usr/lib/ccache/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOCALE_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DUSE_PORTMIDI -DUSE_WEBSERVER -I/<>/ced -I/usr/include/SDL2 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/libpng16 -I/usr/include/librsvg-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml++-2.6 -I/usr/include/libxml2 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/cpprest -I/<>/obj-x86_64-linux-gnu/game -DBOOST_NO_CXX11_SCOPED_ENUMS -std=c++14 -Wall -Wextra -fcx-limited-range -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -pthread -MD -MT game/CMakeFiles/performous.dir/fs.cc.o -MF CMakeFiles/performous.dir/fs.cc.o.d -o CMakeFiles/performous.dir/fs.cc.o -c /<>/game/fs.cc | /<>/game/ffmpeg.cc: In member function ‘void FFmpeg::open()’: | /<>/game/ffmpeg.cc:100:93: error: invalid conversion from ‘AVCodec**’ to ‘const AVCodec**’ [-fpermissive] | 100 | m_streamId = av_find_best_stream(m_formatContext, (AVMediaType)m_mediaType, -1, -1, , 0); | | ^~ | | | | | AVCodec** | In file included from /<>/game/ffmpeg.cc:15: | /usr/include/x86_64-linux-gnu/libavformat/avformat.h:2161:41: note: initializing argument 5 of ‘int av_find_best_stream(AVFormatContext*, AVMediaType, int, int, const AVCodec**, int)’ | 2161 | const AVCodec **decoder_ret, | | ^~~ | /<>/game/ffmpeg.cc:104:47: error: invalid conversion from ‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive] | 104 | AVCodec* pCodec = avcodec_find_decoder(m_formatContext->streams[m_streamId]->codecpar->codec_id); | | ^~ | | | | | const AVCodec* | make[3]: *** [game/CMakeFiles/performous.dir/build.make:289: game/CMakeFiles/performous.dir/ffmpeg.cc.o] Error 1 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: performous Source-Version: 1.1+git20181118-6 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of performous, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated performous package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 19:20:54 +0100 Source: performous
Bug#1026487: marked as done (libvigraimpex: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices)
Your message dated Sat, 21 Jan 2023 19:34:17 +
with message-id
and subject line Bug#1026487: fixed in libvigraimpex 1.11.1+dfsg-11
has caused the Debian Bug report #1026487,
regarding libvigraimpex: FTBFS: IndexError: only integers, slices (`:`),
ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are
valid indices
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.)
--
1026487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvigraimpex
Version: 1.11.1+dfsg-10
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[5]: Entering directory '/<>/obj.x86_64-linux-gnu'
> [ 34%] Building CXX object
> vigranumpy/test/CMakeFiles/vigranumpytest.dir/vigranumpytest.cxx.o
> cd /<>/obj.x86_64-linux-gnu/vigranumpy/test && /usr/bin/c++
> -DHasHDF5 -Dvigranumpytest_EXPORTS -I/<>/include
> -I/usr/include/OpenEXR -I/usr/include/Imath -isystem
> /usr/lib/python3/dist-packages/numpy/core/include -isystem
> /usr/include/python3.10 -isystem /usr/include/hdf5/serial -std=c++11 -pthread
> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD
> -MT vigranumpy/test/CMakeFiles/vigranumpytest.dir/vigranumpytest.cxx.o -MF
> CMakeFiles/vigranumpytest.dir/vigranumpytest.cxx.o.d -o
> CMakeFiles/vigranumpytest.dir/vigranumpytest.cxx.o -c
> /<>/vigranumpy/test/vigranumpytest.cxx
> In file included from
> /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
> from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
> from
> /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
> from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
> from
> /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
> from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
> from /usr/include/boost/shared_ptr.hpp:17,
> from
> /usr/include/boost/python/converter/shared_ptr_to_python.hpp:12,
> from
> /usr/include/boost/python/converter/arg_to_python.hpp:15,
> from /usr/include/boost/python/call.hpp:15,
> from /usr/include/boost/python/object_core.hpp:14,
> from /usr/include/boost/python/args.hpp:22,
> from /usr/include/boost/python.hpp:11,
> from /<>/vigranumpy/test/vigranumpytest.cxx:41:
> /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of
> declaring the Bind placeholders (_1, _2, ...) in the global namespace is
> deprecated. Please use + using namespace
> boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the
> current behavior.’
>36 | BOOST_PRAGMA_MESSAGE(
> | ^~~~
> /usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This
> header is deprecated. Use instead.’
>13 | BOOST_HEADER_DEPRECATED("")
> | ^~~
> In file included from /<>/include/vigra/tinyvector.hxx:57,
> from /<>/include/vigra/multi_array.hxx:43,
> from /<>/include/vigra/numpy_array.hxx:47,
> from /<>/vigranumpy/test/vigranumpytest.cxx:43:
> /<>/include/vigra/static_assert.hxx:87:22: warning: unnecessary
> parentheses in declaration of ‘assertImpl’ [-Wparentheses]
>87 | failure (Predicate::
> | ^~~~
>88 | assertImpl( void (*)(Predicate), typename Predicate::not_type )
> | ~~~
>89 | );
> | ~
> /<>/include/vigra/static_assert.hxx:87:22: note: remove
> parentheses
>87 | failure (Predicate::
> | ^~~~
> | -
>88 | assertImpl( void (*)(Predicate), typename Predicate::not_type )
> | ~~~
>89 | );
> | ~
> | -
> In file included from /<>/include/vigra/initimage.hxx:42,
> from /<>/include/vigra/basicimageview.hxx:40,
> from
Bug#1029253: marked as done (linphone: FTBFS: ValueError: invalid mode: 'rU')
Your message dated Sat, 21 Jan 2023 19:34:32 +
with message-id
and subject line Bug#1029253: fixed in linphone 5.1.65-3
has caused the Debian Bug report #1029253,
regarding linphone: FTBFS: ValueError: invalid mode: 'rU'
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.)
--
1029253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linphone
Version: 5.1.65-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230120 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 4%] Generating include/linphone++/linphone.hh, src/linphone++.cc
> cd /<>/obj-x86_64-linux-gnu/wrappers/cpp && /usr/bin/cmake -E
> remove_directory include
> cd /<>/obj-x86_64-linux-gnu/wrappers/cpp && /usr/bin/cmake -E
> remove_directory src
> cd /<>/obj-x86_64-linux-gnu/wrappers/cpp && /usr/bin/python3
> /<>/wrappers/cpp/genwrapper.py
> /<>/obj-x86_64-linux-gnu/coreapi/help/doc/doxygen/xml
> /<>/coreapi/chat.c: In function ‘LinphoneChatRoom*
> linphone_core_create_client_group_chat_room(LinphoneCore*, const char*,
> bool_t)’:
> /<>/coreapi/chat.c:69:61: warning: ‘LinphoneChatRoom*
> linphone_core_create_client_group_chat_room_2(LinphoneCore*, const char*,
> bool_t, bool_t)’ is deprecated [-Wdeprecated-declarations]
>69 | return linphone_core_create_client_group_chat_room_2(lc,
> subject, fallback, FALSE);
> |
> ~^~
> In file included from /<>/src/conference/conference.h:26,
> from
> /<>/src/conference/session/call-session.h:25,
> from /<>/src/conference/session/streams.h:28,
> from /<>/include/linphone/utils/utils.h:35,
> from /<>/coreapi/chat.c:25:
> /<>/include/linphone/core.h:7436:55: note: declared here
> 7436 | LINPHONE_PUBLIC LINPHONE_DEPRECATED LinphoneChatRoom
> *linphone_core_create_client_group_chat_room_2(LinphoneCore *core, const char
> *subject, bool_t fallback, bool_t encrypted);
> |
> ^
> /<>/coreapi/chat.c: In function ‘LinphoneChatRoom*
> linphone_core_get_chat_room(LinphoneCore*, const LinphoneAddress*)’:
> /<>/coreapi/chat.c:171:45: warning: ‘LinphoneChatRoom*
> linphone_core_get_chat_room_2(LinphoneCore*, const LinphoneAddress*, const
> LinphoneAddress*)’ is deprecated [-Wdeprecated-declarations]
> 171 | return linphone_core_get_chat_room_2(lc, peerAddr, NULL);
> |~^~~~
> /<>/include/linphone/core.h:7520:55: note: declared here
> 7520 | LINPHONE_PUBLIC LINPHONE_DEPRECATED LinphoneChatRoom
> *linphone_core_get_chat_room_2(
> |
> ^
> /<>/coreapi/chat.c: In function ‘LinphoneChatRoom*
> linphone_core_get_chat_room_from_uri(LinphoneCore*, const char*)’:
> /<>/coreapi/chat.c:196:61: warning: ‘LinphoneChatRoom*
> linphone_core_get_chat_room(LinphoneCore*, const LinphoneAddress*)’ is
> deprecated [-Wdeprecated-declarations]
> 196 | LinphoneChatRoom *room = linphone_core_get_chat_room(lc,
> addr);
> | ~~~^~
> /<>/coreapi/chat.c:170:19: note: declared here
> 170 | LinphoneChatRoom *linphone_core_get_chat_room (LinphoneCore *lc,
> const LinphoneAddress *peerAddr) {
> | ^~~
> [ 5%] Building CXX object
> coreapi/CMakeFiles/linphone-coreapi.dir/echo-tester.c.o
> cd /<>/obj-x86_64-linux-gnu/coreapi && /usr/bin/c++
> -DBCTBX_LOG_DOMAIN=\"liblinphone\" -DBCTBX_STATIC -DHAVE_CONFIG_H
> -DLDAP_ENABLED -DLDAP_LIBS_DYNAMIC -DLINPHONE_EXPORTS -DUSE_BELLESIP
> -DVCARD_ENABLED -DVIDEO_ENABLED -I/<>/coreapi
> -I/<>/include -I/<>/src
> -I/<>/obj-x86_64-linux-gnu
> -I/<>/obj-x86_64-linux-gnu/coreapi -I/usr/include/belle-sip
> -I/usr/include/OpenGL -I/usr/include/xsd -I/usr/include/libxml2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -DPACKAGE_SOUND_DIR="\"/usr/share/sounds/linphone\""
> -DPACKAGE_RING_DIR="\"/usr/share/sounds/linphone/rings\"" -Wdate-time
> -D_FORTIFY_SOURCE=2 -DDEBPATCH_LDAP_HOSTNAME_OVERRIDE=1 -fPIC -std=c++14
Bug#1026661: marked as done (haskell-stack: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25)
Your message dated Sat, 21 Jan 2023 19:21:25 +
with message-id
and subject line Bug#1026661: fixed in haskell-stack 2.7.5-2
has caused the Debian Bug report #1026661,
regarding haskell-stack: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] 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.)
--
1026661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-stack
Version: 2.7.5-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
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/mqMbKVMZdX -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> haskell-stack
> Running dh_listpackages
> haskell-stack
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/stack-2.7.5/ --datasubdir=stack
> --htmldir=/usr/share/doc/libghc-stack-doc/html/ -fdisable-git-info
> --enable-tests
> Using Parsec parser
> Configuring stack-2.7.5...
> Flags chosen: developer-mode=False, disable-git-info=True,
> hide-dependency-versions=False, integration-tests=False, static=False,
> supported-build=False
> Dependency Cabal >=3.2.1.0: using Cabal-3.4.1.0
> Dependency aeson >=1.5.6.0: using aeson-2.0.3.0
> Dependency annotated-wl-pprint >=0.7.0: using annotated-wl-pprint-0.7.0
> Dependency ansi-terminal >=0.10.3: using ansi-terminal-0.11.3
> Dependency array >=0.5.4.0: using array-0.5.4.0
> Dependency async >=2.2.3: using async-2.2.4
> Dependency attoparsec >=0.13.2.5: using attoparsec-0.14.4
> Dependency base >=4.10 && <5: using base-4.15.1.0
> Dependency base64-bytestring >=1.1.0.0: using base64-bytestring-1.2.1.0
> Dependency bytestring >=0.10.12.0: using bytestring-0.10.12.1
> Dependency casa-client >=0.0.1: using casa-client-0.0.1
> Dependency casa-types >=0.0.1: using casa-types-0.0.2
> Dependency colour >=2.3.5: using colour-2.3.6
> Dependency conduit >=1.3.4.1: using conduit-1.3.4.3
> Dependency conduit-extra >=1.3.5: using conduit-extra-1.3.6
> Dependency containers >=0.6.2.1: using containers-0.6.4.1
> Dependency cryptonite >=0.27: using cryptonite-0.29
> Dependency cryptonite-conduit >=0.2.2: using cryptonite-conduit-0.2.2
> Dependency deepseq >=1.4.4.0: using deepseq-1.4.5.0
> Dependency directory >=1.3.6.0: using directory-1.3.6.2
> Dependency echo >=0.1.4: using echo-0.1.4
> Dependency exceptions >=0.10.4: using exceptions-0.10.4
> Dependency extra >=1.7.9: using extra-1.7.12
> Dependency file-embed >=0.0.14.0: using file-embed-0.0.15.0
> Dependency filelock >=0.1.1.5: using filelock-0.1.1.5
> Dependency filepath >=1.4.2.1: using filepath-1.4.2.1
> Dependency fsnotify >=0.3.0.1: using fsnotify-0.3.0.1
> Dependency generic-deriving >=1.13.1: using generic-deriving-1.14.2
> Dependency hackage-security >=0.6.0.1: using hackage-security-0.6.2.2
> Dependency hashable >=1.3.0.0: using hashable-1.3.5.0
> Dependency hi-file-parser >=0.1.2.0: using hi-file-parser-0.1.3.0
> Dependency hpack >=0.34.4: using hpack-0.34.7
> Dependency hpc >=0.6.1.0: using hpc-0.6.1.0
> Dependency http-client >=0.6.4.1: using http-client-0.7.13.1
> Dependency http-client-tls >=0.3.5.3: using http-client-tls-0.3.6.1
> Dependency http-conduit >=2.3.8: using http-conduit-2.3.8
> Dependency http-download >=0.2.0.0: using http-download-0.2.0.0
> Dependency http-types >=0.12.3: using http-types-0.12.3
> Dependency memory >=0.15.0: using memory-0.16.0
> Dependency microlens >=0.4.11.2: using microlens-0.4.12.0
> Dependency mono-traversable >=1.0.15.1: using mono-traversable-1.0.15.3
> Dependency mtl
Bug#1022786: marked as done (glirc: unsatisfiable build-dependency libghc-attoparsec-dev (<< 0.14))
Your message dated Sat, 21 Jan 2023 19:18:28 + with message-id and subject line Bug#1022786: fixed in glirc 2.39.0.1-1 has caused the Debian Bug report #1022786, regarding glirc: unsatisfiable build-dependency libghc-attoparsec-dev (<< 0.14) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glirc Version: 2.36-3 Severity: serious Hi, glirc build-depends on libghc-attoparsec-dev (<< 0.14). However, the current version of that package in sid is 0.14.4-2+b1. -Ralf. --- End Message --- --- Begin Message --- Source: glirc Source-Version: 2.39.0.1-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of glirc, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated glirc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 18:51:10 +0200 Source: glirc Architecture: source Version: 2.39.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 1022786 Changes: glirc (2.39.0.1-1) unstable; urgency=medium . * New upstream release (Closes: #1022786) * Declare compliance with Debian policy 4.6.1 Checksums-Sha1: bf56e95c58887dce571b8d69cf0f3b3b8c415e13 3410 glirc_2.39.0.1-1.dsc 483b0fc56218b65c3257ca0180fe902e5157e821 186028 glirc_2.39.0.1.orig.tar.gz e4aa2b142f6f2c7515559918397c8496aa2ad60f 3752 glirc_2.39.0.1-1.debian.tar.xz 82117094c1fd4b1066e367f6b235e1e05e234a9b 10297 glirc_2.39.0.1-1_amd64.buildinfo Checksums-Sha256: 9ee05fe587a884128947a3e35145f97215929e55620d884050b42d37d8e72158 3410 glirc_2.39.0.1-1.dsc 99401ae7d75a5315848af3586818d481bfd6ab001390f2fd9f663b39c8e25e49 186028 glirc_2.39.0.1.orig.tar.gz 1b5b04a2c8bc4c2b0fde0df89b7471e87b93e285d465960069c48293609bc60b 3752 glirc_2.39.0.1-1.debian.tar.xz 1c520e2221cdade165f621cc74efa9552c35141e751fd045a780fecf1eb1 10297 glirc_2.39.0.1-1_amd64.buildinfo Files: f917b47d3149c664e418d7b63dd3f875 3410 haskell optional glirc_2.39.0.1-1.dsc 9e27f6190cba4a91b134314187a4724d 186028 haskell optional glirc_2.39.0.1.orig.tar.gz 8b3fd47f21bda8a11d77640880f27918 3752 haskell optional glirc_2.39.0.1-1.debian.tar.xz 2e8ab7c04417274215975d8a94d31348 10297 haskell optional glirc_2.39.0.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmPMHy0UHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDw83RAAp4v0SVOdjRozj2clizLuLNE3w1By gXtI33fKxInpnY/YjiMXaU64rOmgoYtH583yqJLWlVMES1YliVY1IRxntqTz5gjA A1XEXI0/d4sICchrRG4UIlynr//8XC8Yg1VQU3RnrYv3KK6WGA4m1WUl/3fJnKa5 Up0UnqVxgfa4xVXpvu31HhpFnTscx8u5D+PQAKAlug4vUVkYhqVKMx/+uGBGJNEZ gQQ4jVdf6ryBrk7KwwJ/yESitMAqS+1xdY3x7b8vZU0u9MFuCmYhIrHY37OrRTHc YPRzOGu+484pBzQhrYRV23cZWcDaytoxRyN0CMgAz/ju95lM4bJymwFwMFolckES 1DMZQw2XU5FercXRkOdRq2jffZLCZ03D9iTSNO9U5PqonTZfFKkURFkApPV1XTbX QcLHHbRGn0ppqW/5gq785rO6akbOmt+NJkzhBbJ/tijk/db8J8seknpTo74E6NZL rryoWotIVAB3KyHi3ZBfO72rHZ5JasFJRHI7x7q6wqXCDIA3bbBeM0P4iK4fcRlp JdO49Pa6TGhSLbzWq6bKpCTY6HhJEsosCMDU6BJKPmYpGbs9yLtwsMQr+sevC4DK yRvXmJ3GOqt4JVwszO8ezUk4vuVKwmyXjG6kRRirDXkoFxGqVRWuEr3vLezySn+j 2v6GrB+Xd738bYo= =PwOW -END PGP SIGNATURE End Message ---
Bug#1029351: marked as done (dh-r parsing of tests depends/suggests is faulty)
Your message dated Sat, 21 Jan 2023 19:09:11 +
with message-id
and subject line Bug#1029350: fixed in dh-r 20230121
has caused the Debian Bug report #1029350,
regarding dh-r parsing of tests depends/suggests is faulty
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.)
--
1029350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dh-r
Version: 20210816
Severity: serious
Control: retitle -1 dh-r parsing of tests depends/suggests is faulty
Hi Andreas,
On 1/21/23 19:17, Andreas Tille wrote:
Hi,
I'm just running into
dh_auto_install: warning: can't parse dependency spatstat (>= 2.3-3).linnet
(>= 2.0-0)
Can't call method "get_deps" on an undefined value at
/usr/share/perl5/Debian/Debhelper/Buildsystem/R.pm line 51.
when trying to build r-cran-spatstat.core[1]
I've never seen this strange substitution of dependencies before.
Any idea what's wrong here?
Congrats. Looks like you hit a case which catches a bug in dh-R.
The problem is in the code when you are trying to substitute test depends from
the ones in suggests[2]. The substitution
that you are trying to do is also replacing prefixes with versioned dep. Since
there is spatstat and spatstat.linnet both in
d/t/control test-depends, and as you could see spatstat is a common prefix, it
is replacing this with the one
written in DESCRIPTION file which is wrong.
As it seems to me that you only intend to replace non-versioned stuff with the
versioned stuff, maybe you don't have
to replace all strings that are prefix. So _maybe_ a patch like this would do
(it works in this case at least):
diff --git a/dh/R.pm b/dh/R.pm
index 18171ae..7d052b1 100644
--- a/dh/R.pm
+++ b/dh/R.pm
@@ -210,7 +210,7 @@ sub install {
$rsname =~ s/[\s(].*// ;
if ( grep(/^$rsname$/i, @testdeps) ) {
if ( $rs ne $rsname ) { # seems that is a versioned depends that
needs to be propagated to Recommends
- $testdepends =~ s/$rsname */$rs/ ;
+ $testdepends =~ s/$rsname$/$rs/ ;
}
} else {
$newsuggests = $newsuggests . ', ' . $rs ;
But that said, I do not know the essence of this code, and please _triple
check_ and ** do not blindly apply **
[1] https://salsa.debian.org/r-pkg-team/r-cran-spatstat.core/-/jobs/3830571
[2]: https://salsa.debian.org/r-pkg-team/dh-r/-/blob/master/dh/R.pm#L213
Hope that helps.
Thank you
Nilesh
--- End Message ---
--- Begin Message ---
Source: dh-r
Source-Version: 20230121
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
dh-r, 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 1029...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated dh-r package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 21 Jan 2023 17:49:29 +0100
Source: dh-r
Architecture: source
Version: 20230121
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1029350
Changes:
dh-r (20230121) unstable; urgency=medium
.
[ Steffen Moeller ]
* s/itp: Warn when executed from wrong directory
* substitute "which" with "command -v" if available
* more checks on runtime errors instead of silent exit
.
[ Andreas Tille ]
* Fix parsing of Test-Depends which are turned into Recommends
Closes: #1029350
* Standards-Version: 4.6.2
Checksums-Sha1:
e8d60eb78c0adf304f30e9910a78871707ea370e 1738 dh-r_20230121.dsc
f4416446d40e8a33184eed56da398ccc589bd11f 40892 dh-r_20230121.tar.xz
2232ac45c2b8b6c9b88de99c12eba8f7e9953b72 5934 dh-r_20230121_amd64.buildinfo
Checksums-Sha256:
b4e27ea895a795984f3675aeb3b17a18616fc75e4f4ae6e2282da03013648125 1738
dh-r_20230121.dsc
81c39e5e12c0a0451812c8c37245dc0456cc8c2b0b32e451bd414f31b5e5f02f 40892
dh-r_20230121.tar.xz
af42a36d3e77f5c62fdf38af0d975c3dc5fb8ad868cf854e5c7c4437be8a4509 5934
dh-r_20230121_amd64.buildinfo
Files:
5f20b846aa1deb8620c8a72dd2d3cd35 1738 science optional dh-r_20230121.d
Bug#1029350: marked as done (dh-r parsing of tests depends/suggests is faulty)
Your message dated Sat, 21 Jan 2023 19:09:11 +
with message-id
and subject line Bug#1029350: fixed in dh-r 20230121
has caused the Debian Bug report #1029350,
regarding dh-r parsing of tests depends/suggests is faulty
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.)
--
1029350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dh-r
Version: 20210816
Severity: serious
Control: retitle -1 dh-r parsing of tests depends/suggests is faulty
[ Looks like I has mistakenly submitted the report to control@ earlier, fixing
that, rest of the mail is copied as is ]
Hi Andreas,
On 1/21/23 19:17, Andreas Tille wrote:
Hi,
I'm just running into
dh_auto_install: warning: can't parse dependency spatstat (>= 2.3-3).linnet
(>= 2.0-0)
Can't call method "get_deps" on an undefined value at
/usr/share/perl5/Debian/Debhelper/Buildsystem/R.pm line 51.
when trying to build r-cran-spatstat.core[1]
I've never seen this strange substitution of dependencies before.
Any idea what's wrong here?
Congrats. Looks like you hit a case which catches a bug in dh-R.
The problem is in the code when you are trying to substitute test depends from
the ones in suggests[2]. The substitution
that you are trying to do is also replacing prefixes with versioned dep. Since
there is spatstat and spatstat.linnet both in
d/t/control test-depends, and as you could see spatstat is a common prefix, it
is replacing this with the one
written in DESCRIPTION file which is wrong.
As it seems to me that you only intend to replace non-versioned stuff with the
versioned stuff, maybe you don't have
to replace all strings that are prefix. So _maybe_ a patch like this would do
(it works in this case at least):
diff --git a/dh/R.pm b/dh/R.pm
index 18171ae..7d052b1 100644
--- a/dh/R.pm
+++ b/dh/R.pm
@@ -210,7 +210,7 @@ sub install {
$rsname =~ s/[\s(].*// ;
if ( grep(/^$rsname$/i, @testdeps) ) {
if ( $rs ne $rsname ) { # seems that is a versioned depends that
needs to be propagated to Recommends
- $testdepends =~ s/$rsname */$rs/ ;
+ $testdepends =~ s/$rsname$/$rs/ ;
}
} else {
$newsuggests = $newsuggests . ', ' . $rs ;
But that said, I do not know the essence of this code, and please _triple
check_ and ** do not blindly apply **
[1] https://salsa.debian.org/r-pkg-team/r-cran-spatstat.core/-/jobs/3830571
[2]: https://salsa.debian.org/r-pkg-team/dh-r/-/blob/master/dh/R.pm#L213
Hope that helps.
Thank you
Nilesh
--- End Message ---
--- Begin Message ---
Source: dh-r
Source-Version: 20230121
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
dh-r, 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 1029...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated dh-r package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 21 Jan 2023 17:49:29 +0100
Source: dh-r
Architecture: source
Version: 20230121
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1029350
Changes:
dh-r (20230121) unstable; urgency=medium
.
[ Steffen Moeller ]
* s/itp: Warn when executed from wrong directory
* substitute "which" with "command -v" if available
* more checks on runtime errors instead of silent exit
.
[ Andreas Tille ]
* Fix parsing of Test-Depends which are turned into Recommends
Closes: #1029350
* Standards-Version: 4.6.2
Checksums-Sha1:
e8d60eb78c0adf304f30e9910a78871707ea370e 1738 dh-r_20230121.dsc
f4416446d40e8a33184eed56da398ccc589bd11f 40892 dh-r_20230121.tar.xz
2232ac45c2b8b6c9b88de99c12eba8f7e9953b72 5934 dh-r_20230121_amd64.buildinfo
Checksums-Sha256:
b4e27ea895a795984f3675aeb3b17a18616fc75e4f4ae6e2282da03013648125 1738
dh-r_20230121.dsc
81c39e5e12c0a0451812c8c37245dc0456cc8c2b0b32e451bd414f31b5e5f02f 40892
dh-r_20230121.tar.xz
af42a36d3e77f5c62fdf38af0d975c3dc5fb8ad868cf854e5c7c44
Bug#1029232: marked as done (dask.distributed: broken by version mismatch with dask)
Your message dated Sat, 21 Jan 2023 19:09:04 + with message-id and subject line Bug#1029232: fixed in dask.distributed 2022.12.1+ds.1-1 has caused the Debian Bug report #1029232, regarding dask.distributed: broken by version mismatch with dask 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.) -- 1029232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-distributed Version: 2022.02.0+ds1-3 Severity: serious dask.distributed has been failing its autopkgtests since dask was upgraded to 2022.12.1. This is the expected result of upgrading one but not the other: I'd seen the same in my test PPA, and the upstream setup.py/requirements.txt require exactly matching upstream versions of dask and dask.distributed. Hence, it can probably be fixed by upgrading dask.distributed to 2022.12.1. (See also discussion in #1028667.) (Upgrading *both* dask.distributed and dask to 2023.1.0 probably also works, but I haven't tested that.) My PPA package of dask.distributed 2022.12 might be useful: https://launchpad.net/~rebecca-palmer/+archive/ubuntu/dask2022p12v2/+sourcepub/14427094/+listing-archive-extra (Don't upload that as-is: it tries to run more of the tests during the build because PPAs don't have autopkgtest, which doesn't work.) This and ulmo #1017573 (which has a patch) are the remaining blockers for pandas 1.5. --- End Message --- --- Begin Message --- Source: dask.distributed Source-Version: 2022.12.1+ds.1-1 Done: Diane Trout We believe that the bug you reported is fixed in the latest version of dask.distributed, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Diane Trout (supplier of updated dask.distributed package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 08:52:22 -0800 Source: dask.distributed Architecture: source Version: 2022.12.1+ds.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Diane Trout Closes: 1028691 1029232 Changes: dask.distributed (2022.12.1+ds.1-1) unstable; urgency=medium . * New upsream release. (Closes: #1029232) * Remove the following patches, resolved upstream - python-3.10-loop.patch - test_spillbuffer_remove_sizetest.patch - python3.11.patch - set-client-asynchronous-earlier.patch * Install tests to simplify running autopkgtests * add add-test-marks.patch to define some pytest test marks * add skip-pyarrow-tests.path as we don't have that dependency - consider reviewing this patch and focusing on the specific modules that are importing pyarrow. * Refresh patches * Add python3-jupyter-server to Build-Depends for tests * Add python3-aiohttp dependency to autopkgtests * Remove python3-keras autopkgtest dependency, it depends on an unmaintained package theano which breaks during the run. * Move autopkgtest script to it's own file run-tests * Remove python-numpy-doc dependency since it's not available. (closes: #1028691) * Update list of tests that don't run correctly during build * attempt to implement nocheck DEB_BUILD_OPTION in d/rules * adjust d/rules to prevent __pycache__ directory from being shipped in python-distributed-doc Checksums-Sha1: 5334e23eef7d3a0c1cd5c1676db76ecb0655c6f3 3214 dask.distributed_2022.12.1+ds.1-1.dsc d640d3efb8575bfd200eca1bcb0de713f6264d50 1463816 dask.distributed_2022.12.1+ds.1.orig.tar.xz bc5f1e6ebd70308f88f2c7025cf9aeac15b61dc4 2026168 dask.distributed_2022.12.1+ds.1-1.debian.tar.xz bbaded620f0c4a04651f4b59dfaa6542f4f8e8e9 11360 dask.distributed_2022.12.1+ds.1-1_amd64.buildinfo Checksums-Sha256: d6c1ca1dd11135f57f1a5e1e2302edbc8454a265ce3ade74d74853e59ede0666 3214 dask.distributed_2022.12.1+ds.1-1.dsc d6c27c6f2ebd4a26d78e08b47c499915d463eb0708046afca04f3d71030a410f 1463816 dask.distributed_2022.12.1+ds.1.orig.tar.xz 2983349aea7934c4bef634ab2e3eee118cb7c203e147fe9b23a6a826b5a797b9 2026168 dask.distributed_2022.12.1+ds.1-1.debian.tar.xz
Bug#1028691: marked as done (dask.distributed: FTBFS: unsatisfiable build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc)
Your message dated Sat, 21 Jan 2023 19:09:04 + with message-id and subject line Bug#1028691: fixed in dask.distributed 2022.12.1+ds.1-1 has caused the Debian Bug report #1028691, regarding dask.distributed: FTBFS: unsatisfiable build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc 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.) -- 1028691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dask.distributed Version: 2022.02.0+ds.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 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-compat (= 13), dh-python, python3-all, > python3-click (>= 6.6), python3-cloudpickle (>= 1.5.0), python3-cryptography, > python3-dask (>= 2022.02.0), python3-doc, python3-locket, python3-msgpack, > python3-numpy, python-numpy-doc, python3-numpydoc, python3-pandas, > python-pandas-doc, python3-psutil, python3-pytest, python3-pytest-asyncio, > python3-pytest-timeout, python3-setuptools, python3-six, > python3-sortedcollections, python3-sphinx, python3-sphinx-click, > python3-dask-sphinx-theme, python3-tblib, python3-toolz (>= 0.8.2), > python3-tornado (>= 5), python3-yaml, python3-zict (>= 0.1.3), uglifyjs, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3-all, > python3-click (>= 6.6), python3-cloudpickle (>= 1.5.0), python3-cryptography, > python3-dask (>= 2022.02.0), python3-doc, python3-locket, python3-msgpack, > python3-numpy, python-numpy-doc, python3-numpydoc, python3-pandas, > python-pandas-doc, python3-psutil, python3-pytest, python3-pytest-asyncio, > python3-pytest-timeout, python3-setuptools, python3-six, > python3-sortedcollections, python3-sphinx, python3-sphinx-click, > python3-dask-sphinx-theme, python3-tblib, python3-toolz (>= 0.8.2), > python3-tornado (>= 5), python3-yaml, python3-zict (>= 0.1.3), uglifyjs, > 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 [594 B] > Get:5 copy:/<>/apt_archive ./ Packages [666 B] > Fetched 2223 B in 0s (158 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: python3-dask (>= 2022.02.0) but > it is not going to be installed >Depends: python-numpy-doc 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/2023/01/13/dask.distributed_2022.02.0+ds.1-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=lu...@debian.org=1=1=1=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 --- ---
Processed: Bug#979955 marked as pending in ruby-rails-assets-jquery-fullscreen-plugin
Processing control commands: > tag -1 pending Bug #979955 [ruby-rails-assets-jquery-fullscreen-plugin] ruby-rails-assets-jquery-fullscreen-plugin: node-uglify is deprecated in favor of uglifyjs Added tag(s) pending. -- 979955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979955: marked as pending in ruby-rails-assets-jquery-fullscreen-plugin
Control: tag -1 pending Hello, Bug #979955 in ruby-rails-assets-jquery-fullscreen-plugin 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-rails-assets-jquery-fullscreen-plugin/-/commit/b607e78db32addb9abc59076b85a2f2aa5f8ed7c Switch build dependency to uglifyjs (from node-uglify) (Closes: #979955) (this message was generated automatically) -- Greetings https://bugs.debian.org/979955
Bug#1004963: CVE-2020-21598 CVE-2020-21600 CVE-2020-21602
Am 21. Januar 2023 18:14:28 UTC schrieb Salvatore Bonaccorso : >Hi Tobi, > >On Sat, Jan 21, 2023 at 06:21:19PM +0100, Tobias Frost wrote: >> On Fri, 04 Feb 2022 13:14:48 +0100 Moritz Muehlenhoff >> wrote: >> > Source: libde265 >> > Version: 1.0.8-1 >> > Severity: grave >> > Tags: security >> > X-Debbugs-Cc: Debian Security Team >> > >> > CVE-2020-21602: >> > https://github.com/strukturag/libde265/issues/242 >> > >> > CVE-2020-21600: >> > https://github.com/strukturag/libde265/issues/243 >> > >> > CVE-2020-21598: >> > https://github.com/strukturag/libde265/issues/237 >> > >> >> I cannot reproduce those three bugs with the pocs in the issues. (using the >> version currently in sid, >> built with address sanitizer) >> Possibly already fixed… Tagging unreproducible. > >if you suspect it's fixed upstream, can reproduce it with upstream's >mentioned affected but not with the newest HEAD, can you try to bisect >those to the fixing commits? > >Regards, >Salvatore yes, that's my plan - also for the ones in the other bugd (just ran out of time for today)
Bug#1004616: marked as pending in performous
Control: tag -1 pending Hello, Bug #1004616 in performous 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/games-team/performous/-/commit/ea2d7c1b45bca758a3bb717c1ab8b6119e52def2 Fix FTBFS with ffmpeg 5. Thanks: Dan Bungert for the patch. Closes: #1004616 (this message was generated automatically) -- Greetings https://bugs.debian.org/1004616
Processed: Bug#1004616 marked as pending in performous
Processing control commands: > tag -1 pending Bug #1004616 [src:performous] performous: FTBFS with ffmpeg 5.0 Added tag(s) pending. -- 1004616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027235: marked as pending in python-pomegranate
Control: tag -1 pending Hello, Bug #1027235 in python-pomegranate 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/python-pomegranate/-/commit/0dba7288e24f9a14b62c07206476096db2e0a37e Add patch to make package compatible with np 1.24 (Closes: #1027235) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027235
Processed: Bug#1027235 marked as pending in python-pomegranate
Processing control commands: > tag -1 pending Bug #1027235 [src:python-pomegranate] python-pomegranate: autopkgtest fail with numpy/1.24.1 Added tag(s) pending. -- 1027235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fix
Processing commands for cont...@bugs.debian.org:
> fixed 1028175 1.2.0.post0-4
Bug #1028175 {Done: Diane Trout } [python-ratelimiter]
snakemake rulename failes with asyncio has no attribute coroutine with
python3.11
There is no source info for the package 'python-ratelimiter' at version
'1.2.0.post0-4' with architecture ''
Unable to make a source version for version '1.2.0.post0-4'
Marked as fixed in versions 1.2.0.post0-4.
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1028175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010095: marked as pending in performous
Control: tag -1 pending Hello, Bug #1010095 in performous 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/games-team/performous/-/commit/9e9a43b1cbd50afdb22bb5a2a99fc356292c402b Remove -mno-altivec on ppc64el as not needed anymore (Closes: #1010095) (this message was generated automatically) -- Greetings https://bugs.debian.org/1010095
Processed: reassign
Processing commands for cont...@bugs.debian.org:
> reassign 1028175 python-ratelimiter 1.2.0.post0-3
Bug #1028175 {Done: Diane Trout } [snakemake] snakemake
rulename failes with asyncio has no attribute coroutine with python3.11
Bug reassigned from package 'snakemake' to 'python-ratelimiter'.
No longer marked as found in versions snakemake/7.12.1-1.
No longer marked as fixed in versions python-ratelimiter/1.2.0.post0-4.
Bug #1028175 {Done: Diane Trout } [python-ratelimiter]
snakemake rulename failes with asyncio has no attribute coroutine with
python3.11
There is no source info for the package 'python-ratelimiter' at version
'1.2.0.post0-3' with architecture ''
Unable to make a source version for version '1.2.0.post0-3'
Marked as found in versions 1.2.0.post0-3.
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1028175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1010095 marked as pending in performous
Processing control commands: > tag -1 pending Bug #1010095 [src:performous] performous: FTBFS on ppc64el Added tag(s) pending. -- 1010095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004963: CVE-2020-21598 CVE-2020-21600 CVE-2020-21602
Hi Tobi, On Sat, Jan 21, 2023 at 06:21:19PM +0100, Tobias Frost wrote: > On Fri, 04 Feb 2022 13:14:48 +0100 Moritz Muehlenhoff wrote: > > Source: libde265 > > Version: 1.0.8-1 > > Severity: grave > > Tags: security > > X-Debbugs-Cc: Debian Security Team > > > > CVE-2020-21602: > > https://github.com/strukturag/libde265/issues/242 > > > > CVE-2020-21600: > > https://github.com/strukturag/libde265/issues/243 > > > > CVE-2020-21598: > > https://github.com/strukturag/libde265/issues/237 > > > > I cannot reproduce those three bugs with the pocs in the issues. (using the > version currently in sid, > built with address sanitizer) > Possibly already fixed… Tagging unreproducible. if you suspect it's fixed upstream, can reproduce it with upstream's mentioned affected but not with the newest HEAD, can you try to bisect those to the fixing commits? Regards, Salvatore
Bug#1028192: gajim: Gajim 1.6.0-1 crashes on connect
Package: gajim Version: 1.6.1-2 Followup-For: Bug #1028192 X-Debbugs-Cc: n.vi...@gmail.com Dear Maintainer, I can also still reproduce this bug. It happens always when gajim tries to connect, including after I remove all its local settings/cache and enter my login information in a fresh setup. Thread 20 "pool-org.gajim." received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff59b276c0 (LWP 5488)] 0x730a81d0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x730a81d0 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x730a8511 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x730a8607 in __gxx_personality_v0 () at /lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x71508131 in __libunwind_Unwind_Resume () at /lib/x86_64-linux-gnu/libunwind.so.8 #4 0x7fffd089b34a in __gnu_cxx::new_allocator::~new_allocator() (this=, __in_chrg=) at /usr/include/c++/11/ext/new_allocator.h:89 #5 std::allocator::~allocator() (this=, __in_chrg=) at /usr/include/c++/11/bits/allocator.h:174 #6 std::_Vector_base >::_Vector_impl::~_Vector_impl() (this=, __in_chrg=) at /usr/include/c++/11/bits/stl_vector.h:128 #7 std::_Vector_base >::~_Vector_base() (this=, __in_chrg=) at /usr/include/c++/11/bits/stl_vector.h:337 #8 std::vector >::~vector() (this=, __in_chrg=) at /usr/include/c++/11/bits/stl_vector.h:683 #9 envvar_config_extension::get_config(libproxy::url const&) (this=, dst=) at ./libproxy/modules/config_envvar.cpp:60 #10 0x7fffd0891e52 in libproxy::proxy_factory::get_config(libproxy::url&, std::vector >&, std::__cxx11::basic_string, std::allocator >&) (this=0x2c8b070, realurl=..., config=std::vector of length 0, capacity 0, ignore="") at ./libproxy/proxy.cpp:265 #11 0x7fffd0892287 in libproxy::proxy_factory::get_proxies(std::__cxx11::basic_string, std::allocator > const&) (this=0x2c8b070, realurl="none://coaxion.net:5222") at ./libproxy/proxy.cpp:206 #12 0x7fffd0892751 in px_proxy_factory_get_proxies(pxProxyFactory_*, char const*) (self=0x2c8b070, url=url@entry=0x251b500 "none://coaxion.net:5222") at ./libproxy/proxy.cpp:465 #13 0x7fffd8cc061f in get_libproxy_proxies (task=0x2ac8190 [GTask], source_object=0x1872620, task_data=0x251b500, cancellable=) at ../proxy/libproxy/glibproxyresolver.c:153 #14 0x76a90793 in g_task_thread_pool_thread (thread_data=0x2ac8190, pool_data=) at ../../../gio/gtask.c:1454 #15 0x76d736ca in g_thread_pool_thread_proxy (data=) at ../../../glib/gthreadpool.c:352 #16 0x76d72cfd in g_thread_proxy (data=0x17f6300) at ../../../glib/gthread.c:831 #17 0x77d13fd4 in start_thread (arg=) at ./nptl/pthread_create.c:442 #18 0x77d9466c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 (gdb) -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gajim depends on: ii desktop-file-utils 0.26-1 ii gir1.2-gst-plugins-base-1.0 1.20.5-1 ii gir1.2-gtk-3.0 3.24.36-1 ii gir1.2-gtksource-4 4.8.4-4 ii python3 3.11.1-1 ii python3-cairo1.20.1-5 ii python3-cryptography 38.0.4-2 ii python3-css-parser 1.0.8-1 ii python3-gi 3.42.2-3 ii python3-gi-cairo 3.42.2-3 ii python3-idna 3.3-1 ii python3-keyring 23.9.3-2 ii python3-nbxmpp 4.0.1-1 ii python3-packaging23.0-1 ii python3-pil 9.4.0-1+b1 ii python3-precis-i18n 1.0.5-1 Versions of packages gajim recommends: ii alsa-utils 1.2.8-1 ii aspell-el [aspell-dictionary] 0.50-3-7 ii aspell-en [aspell-dictionary] 2018.04.16-0-1 ii ca-certificates 20211016 ii dbus1.14.4-1 ii fonts-noto-color-emoji 2.038-1 ii gajim-omemo 2.9.0-1 ii gajim-openpgp 1.5.0-1 ii gir1.2-farstream-0.20.2.9-1 ii gir1.2-geoclue-2.0 2.6.0-2 ii gir1.2-gsound-1.0 1.0.3-2 ii gir1.2-gspell-1 1.12.0-1+b1 ii gir1.2-gstreamer-1.01.20.5-1 ii gir1.2-gupnpigd-1.0 1.2.0-3 ii gir1.2-secret-1 0.20.5-3 ii gstreamer1.0-gl 1.20.5-1 ii gstreamer1.0-nice 0.1.18-2 ii
