Bug#996221: marked as done (ruby-ethon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mFailure/Error: require 'rack/handler/webrick'[0m)
Your message dated Mon, 29 Nov 2021 07:49:39 +
with message-id
and subject line Bug#996221: fixed in ruby-ethon 0.15.0-1
has caused the Debian Bug report #996221,
regarding ruby-ethon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
[31mFailure/Error: require 'rack/handler/webrick'[0m
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.)
--
996221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ethon
Version: 0.9.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-ethon was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> [31mFailure/Error: require 'rack/handler/webrick'[0m
> [31m[0m
> [31mLoadError:[0m
> [31m cannot load such file -- webrick[0m
> [36m# ./spec/support/localhost_server.rb:2:in `'[0m
> [36m# ./spec/spec_helper.rb:10:in `require_relative'[0m
> [36m# ./spec/spec_helper.rb:10:in `'[0m
> [36m# ./spec/ethon/multi_spec.rb:1:in `'[0m
> No examples found.
>
> Finished in 0.6 seconds (files took 0.76538 seconds to load)
> [31m0 examples, 0 failures, 29 errors occurred outside of examples[0m
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
Note that webrick has been removed from the standard library. It's
already been packaged and is currently in NEW, but this package now
needs an explicit dependency on it.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-ethon/ruby-ethon_0.9.0-2+rebuild1633379123_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-ethon
Source-Version: 0.15.0-1
Done: Cédric Boutillier
We believe that the bug you reported is fixed in the latest version of
ruby-ethon, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Cédric Boutillier (supplier of updated ruby-ethon package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Nov 2021 11:33:35 +0100
Source: ruby-ethon
Architecture: source
Version: 0.15.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Cédric Boutillier
Closes: 996221
Changes:
ruby-ethon (0.15.0-1) unstable; urgency=medium
.
* Team upload
.
[ Utkarsh Gupta ]
* Add salsa-ci.yml
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Repository, Repository-
Browse.
* Update watch file format version to 4.
* Set upstream metadata fields: Bug-Submit.
* Remove constraints unnecessary since buster
.
[ Cédric Boutillier ]
* Update team name
* Add .gitattributes to keep unwanted files out of the source package
* New upstream version 0.15.0
* Update packaging files with dh-ruby-make -w
+ add build-dependency on ruby-webrick (Closes: #996221)
+ use gem install layout
+ refresh patch
+ add no-git-in-gemspec.patch to drop usage of git in gemspec file
+ debhelper-compat level set to 13
+ explicitly state that rules file does not require root
+ drop explicit dependency on ruby interpreter
+ Use ${ruby:Depends} to manage (some) dependencies through gemspec file
Checksums-Sha1:
30003ea249aebbf8f8171d0258c0bc6d8ba4f128 1524 ruby-ethon_0.15.0-1.dsc
11eac492d8ed747c9b3e1a2a760086c36621d2f7 56636 ruby-ethon_0.15.0.orig.tar.gz
399eb42c99c4f51ea
Bug#1000783: marked as done (finalcut: binary-any FTBFS)
Your message dated Mon, 29 Nov 2021 07:48:35 + with message-id and subject line Bug#1000783: fixed in finalcut 0.8.0-2 has caused the Debian Bug report #1000783, regarding finalcut: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: finalcut Version: 0.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=finalcut&ver=0.8.0-1 ... debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' test -f final/font/xfonts-finalcut-newfont.alias && rm final/font/xfonts-finalcut-newfont.alias make[1]: *** [debian/rules:25: override_dh_auto_clean] Error 1 --- End Message --- --- Begin Message --- Source: finalcut Source-Version: 0.8.0-2 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of finalcut, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated finalcut 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: Mon, 29 Nov 2021 08:17:15 +0100 Source: finalcut Binary: fonts-libfinal libfinal-dev libfinal-examples libfinal0 libfinal0-dbgsym Architecture: source all amd64 Version: 0.8.0-2 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Description: fonts-libfinal - X11 bitmap font for FINAL CUT libfinal-dev - Developer's library for the final cut widget toolkit libfinal-examples - Test and example programs for the final cut widget toolkit libfinal0 - Shared library for the final cut widget toolkit Closes: 1000783 Changes: finalcut (0.8.0-2) unstable; urgency=medium . * d/copyright: add separate debian/* entry. * d/rules: fix FTBFS. (Closes: 1000783) Checksums-Sha1: a780b5d08d0d1d6419f101ccc897e5b792f24bd7 2033 finalcut_0.8.0-2.dsc c73e8433a18db2007a43a37325ea8f9947f0ef1c 3588 finalcut_0.8.0-2.debian.tar.xz 9e13f77ab0a62f8e0fac50aecafaa141899fbe9b 8586 finalcut_0.8.0-2_amd64.buildinfo 073a168f0984b6c9be09f0bad43ec517a62a335b 55652 fonts-libfinal_0.8.0-2_all.deb 1859f9dc76f3d4b7dc7d6a2f36e9d81aa68d1479 673556 libfinal-dev_0.8.0-2_amd64.deb 5383daa3002a3e9c50e977967f764d3521e72dd4 4894640 libfinal-examples_0.8.0-2_all.deb b4406f17470242c5942fdc0911b24838ae2c73d3 6571320 libfinal0-dbgsym_0.8.0-2_amd64.deb 894d155e94ea0b58fb5b758493ceaa0761224719 487288 libfinal0_0.8.0-2_amd64.deb Checksums-Sha256: 5841d53235787513447054d52cf646c805b890d91e18e2b848be16b1b3a7885a 2033 finalcut_0.8.0-2.dsc 26faf60fb32108e4a8dc64a947260712f85a0ca815b9ef51980cb5946bd789da 3588 finalcut_0.8.0-2.debian.tar.xz 51b472a0d123c775410cbd894e628bc4ccf730decd475bfced5000df54168a60 8586 finalcut_0.8.0-2_amd64.buildinfo 0aaa14edf31ff77cd2147db394ad515a67d904814a511b10935987b1de7883e2 55652 fonts-libfinal_0.8.0-2_all.deb ae4e91819abd3ca1e7b136ab84edb2e03870a94de9f5222f3f79036bd847dc3c 673556 libfinal-dev_0.8.0-2_amd64.deb cff1eeadf52c0d57fe6997b8bf74e98ea005c985a44371e70aed8eb28b5e9386 4894640 libfinal-examples_0.8.0-2_all.deb ea72c1bfc1cd3e4cf179873bfa837e8ab606d67d17ae0e0c00b857f8e408e45a 6571320 libfinal0-dbgsym_0.8.0-2_amd64.deb 0d934608fed5a68b10d06d7e4bf4cdd8cdf6751a518918c1d05fd115e8bba43b 487288 libfinal0_0.8.0-2_amd64.deb Files: 7a6e3568f68513bd3d6f88cb41eaf309 2033 libs optional finalcut_0.8.0-2.dsc f3c39e316b2f3049b14d74253854fc79 3588 libs optional finalcut_0.8.0-2.debian.tar.xz 18a41a0b2b26cabbd280856bf0d59e54 8586 libs optional finalcut_0.8.0-2_amd64.buildinfo f65490c7a273d8bbe1944679edc80df9 55652 fonts optional fonts-libfinal_0.8.0-2_all.deb 739ad2be29721bd0b2b547ff34be665e 673556 libdevel optional libfinal-dev_0.8.0-2_amd64.deb a1de3b9ebe55b4e07e60ee1545ee9040 4894640 misc optional libfinal-examples_0.8.0-2_all.deb e7681738325b6af85fd57127128d22c8 6571320 debug optional libfinal0-dbgsym_0.8.0-2_amd64.deb c56c111ab1758f187099c01ef6d28cc3 487288 libs optional libfinal0_0.8.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAd
Processed: closing 875215
Processing commands for cont...@bugs.debian.org: > close 875215 2.0.0-1 Bug #875215 [src:syncevolution] [syncevolution] Future Qt4 removal from Buster Marked as fixed in versions syncevolution/2.0.0-1. Bug #875215 [src:syncevolution] [syncevolution] Future Qt4 removal from Buster Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 875215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 947857
Processing commands for cont...@bugs.debian.org: > close 947857 0.0~git20210324.18c50b0-1 Bug #947857 [golang-github-juju-testing] golang-github-juju-testing: Remove depends/build-depends on src:mongodb There is no source info for the package 'golang-github-juju-testing' at version '0.0~git20210324.18c50b0-1' with architecture '' Unable to make a source version for version '0.0~git20210324.18c50b0-1' Marked as fixed in versions 0.0~git20210324.18c50b0-1. Bug #947857 [golang-github-juju-testing] golang-github-juju-testing: Remove depends/build-depends on src:mongodb Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 947857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 919089
Processing commands for cont...@bugs.debian.org: > close 919089 0.0~git20210324.18c50b0-1 Bug #919089 [golang-github-juju-testing] Please remove (build-)dependency on mongodb for buster There is no source info for the package 'golang-github-juju-testing' at version '0.0~git20210324.18c50b0-1' with architecture '' Unable to make a source version for version '0.0~git20210324.18c50b0-1' Marked as fixed in versions 0.0~git20210324.18c50b0-1. Bug #919089 [golang-github-juju-testing] Please remove (build-)dependency on mongodb for buster Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 919089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 936723 is normal
Processing commands for cont...@bugs.debian.org: > # the Python deps were removed, leaving open as a reminder to add Python 3 > support when it is ready > severity 936723 normal Bug #936723 [src:ifeffit] ifeffit: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 936723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 917703
Processing commands for cont...@bugs.debian.org: > close 917703 2.1.0-1 Bug #917703 [src:golang-gopkg-macaroon.v2] golang-gopkg-macaroon.v2: FTBFS: build-dependency not installable: golang-github-juju-testing-dev Marked as fixed in versions golang-gopkg-macaroon.v2/2.1.0-1. Bug #917703 [src:golang-gopkg-macaroon.v2] golang-gopkg-macaroon.v2: FTBFS: build-dependency not installable: golang-github-juju-testing-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 917703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 875215, reopening 875215, unarchiving 617320, reopening 617320, unarchiving 890170 ...
Processing commands for cont...@bugs.debian.org:
> # src:syncevolution was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 875215
Bug #875215 {Done: Debian FTP Masters }
[src:syncevolution] [syncevolution] Future Qt4 removal from Buster
Unarchived Bug 875215
> reopen 875215
Bug #875215 {Done: Debian FTP Masters }
[src:syncevolution] [syncevolution] Future Qt4 removal from Buster
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.3-2+rm.
> unarchive 617320
Bug #617320 {Done: Debian FTP Masters }
[syncevolution] syncevolution: Fails to sync with evolution "Cannot get cal
from factory: Invalid source"
Unarchived Bug 617320
> reopen 617320
Bug #617320 {Done: Debian FTP Masters }
[syncevolution] syncevolution: Fails to sync with evolution "Cannot get cal
from factory: Invalid source"
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.3-2+rm.
> unarchive 890170
Bug #890170 {Done: Debian FTP Masters }
[src:syncevolution] syncevolution: Please switch to python-gobject-2/python-gi
Unarchived Bug 890170
> reopen 890170
Bug #890170 {Done: Debian FTP Masters }
[src:syncevolution] syncevolution: Please switch to python-gobject-2/python-gi
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.3-2+rm.
> unarchive 599247
Bug #599247 {Done: Debian FTP Masters }
[syncevolution] syncevolution: Syncing with horde3 - always only slow-sync
possible
Unarchived Bug 599247
> reopen 599247
Bug #599247 {Done: Debian FTP Masters }
[syncevolution] syncevolution: Syncing with horde3 - always only slow-sync
possible
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.0+ds1~beta2a-2 and 1.5.3-2+rm.
> unarchive 645102
Bug #645102 {Done: Debian FTP Masters }
[syncevolution] syncevolution: time of recurring events changes
Unarchived Bug 645102
> reopen 645102
Bug #645102 {Done: Debian FTP Masters }
[syncevolution] syncevolution: time of recurring events changes
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.3-2+rm.
> unarchive 682688
Bug #682688 {Done: Debian FTP Masters }
[syncevolution] syncevolution: doesn't stop syncing
Unarchived Bug 682688
> reopen 682688
Bug #682688 {Done: Debian FTP Masters }
[syncevolution] syncevolution: doesn't stop syncing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.3-2+rm.
> unarchive 836399
Bug #836399 {Done: Debian FTP Masters }
[src:syncevolution] syncevolution: please check for XDG_RUNTIME_DIR/bus before
running dbus-launch
Unarchived Bug 836399
> reopen 836399
Bug #836399 {Done: Debian FTP Masters }
[src:syncevolution] syncevolution: please check for XDG_RUNTIME_DIR/bus before
running dbus-launch
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.3-2+rm.
> unarchive 934693
Bug #934693 {Done: Debian FTP Masters }
[syncevolution] Doesn't build against libecal-2.0
Unarchived Bug 934693
> reopen 934693
Bug #934693 {Done: Debian FTP Masters }
[syncevolution] Doesn't build against libecal-2.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.3-2+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
599247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599247
617320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617320
645102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645102
682688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682688
836399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836399
875215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215
890170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890170
934693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 913254
Processing commands for cont...@bugs.debian.org: > close 913254 1.0.0-1 Bug #913254 [src:golang-gopkg-juju-environschema.v1] golang-gopkg-juju-environschema.v1 build depends on golang-github-juju-schema-dev but it is not installable Marked as fixed in versions golang-gopkg-juju-environschema.v1/1.0.0-1. Bug #913254 [src:golang-gopkg-juju-environschema.v1] golang-gopkg-juju-environschema.v1 build depends on golang-github-juju-schema-dev but it is not installable Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 913254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 919089, reopening 919089, unarchiving 947857, reopening 947857, unarchiving 895623 ...
Processing commands for cont...@bugs.debian.org:
> # src:golang-github-juju-testing was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 919089
Bug #919089 {Done: Debian FTP Masters }
[golang-github-juju-testing] Please remove (build-)dependency on mongodb for
buster
Unarchived Bug 919089
> reopen 919089
Bug #919089 {Done: Debian FTP Masters }
[golang-github-juju-testing] Please remove (build-)dependency on mongodb for
buster
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.0~git20170608.2fe0e88-3+rm.
> unarchive 947857
Bug #947857 {Done: Debian FTP Masters }
[golang-github-juju-testing] golang-github-juju-testing: Remove
depends/build-depends on src:mongodb
Unarchived Bug 947857
> reopen 947857
Bug #947857 {Done: Debian FTP Masters }
[golang-github-juju-testing] golang-github-juju-testing: Remove
depends/build-depends on src:mongodb
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.0~git20170608.2fe0e88-3+rm.
> unarchive 895623
Bug #895623 {Done: Debian FTP Masters }
[golang-github-juju-testing] golang-github-juju-testing: dep8 test failure with
mongodb 3.6
Unarchived Bug 895623
> reopen 895623
Bug #895623 {Done: Debian FTP Masters }
[golang-github-juju-testing] golang-github-juju-testing: dep8 test failure with
mongodb 3.6
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.0~git20170608.2fe0e88-3+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
895623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895623
919089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919089
947857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 936723, reopening 936723
Processing commands for cont...@bugs.debian.org:
> # src:ifeffit was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 936723
Bug #936723 {Done: Stuart Prescott } [src:ifeffit] ifeffit:
Python2 removal in sid/bullseye
Unarchived Bug 936723
> reopen 936723
Bug #936723 {Done: Stuart Prescott } [src:ifeffit] ifeffit:
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2:1.2.11d-10.2+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000772: macaulay2: autopkgtest regression on i386: out of memory
Control: forwarded -1 https://github.com/Macaulay2/M2/issues/2319 Control: tags -1 pending On Sun 28 Nov 2021 02:57:24 PM EST, Paul Gevers wrote: Source: macaulay2 Version: 1.19+ds-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of macaulay2 the autopkgtest of macaulay2 fails in testing when that autopkgtest is run with the binary packages of macaulay2 from unstable. It passes when run with only packages from testing. In tabular form: passfail macaulay2 from testing1.19+ds-3 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from macaulay2/1.19+ds-3. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=macaulay2 https://ci.debian.net/data/autopkgtest/testing/i386/m/macaulay2/17068663/log.gz K3Surfaces ** -- capturing check(0, "K3Surfaces")-- 15.155 seconds elapsed -- capturing check(1, "K3Surfaces")-- 3.51379 seconds elapsed -- capturing check(2, "K3Surfaces")-- 14.3303 seconds elapsed -- capturing check(3, "K3Surfaces")-- 27.3209 seconds elapsed -- capturing check(4, "K3Surfaces")-- 1.92744 seconds elapsed -- capturing check(5, "K3Surfaces")-- 9.5648 seconds elapsed -- skipping check(6, "K3Surfaces")-- 0.00011649 seconds elapsed -- skipping check(7, "K3Surfaces")-- 0.7854 seconds elapsed -- capturing check(8, "K3Surfaces") *** out of memory trying to allocate 131108 bytes, exiting *** cd /tmp/M2-2812-0/171-rundir/; GC_MAXIMUM_HEAP_SIZE=400M "/usr/bin/M2-binary" -q --int --no-randomize --no-readline --silent --stop --print-width 77 <"/tmp/M2-2812-0/170.m2" >>"/tmp/M2-2812-0/170.tmp" /tmp/M2-2812-0/170.tmp:0:1: (output file) error: Macaulay2 exited with status code 1 /tmp/M2-2812-0/170.m2:0:1: (input file) M2: *** Error 1 Thanks for the report! I've reported this upstream and have pushed a band-aid fix to git skipping this test. It should be fixed on the next upload. Doug signature.asc Description: PGP signature
Processed: Re: Bug#1000772: macaulay2: autopkgtest regression on i386: out of memory
Processing control commands: > forwarded -1 https://github.com/Macaulay2/M2/issues/2319 Bug #1000772 [src:macaulay2] macaulay2: autopkgtest regression on i386: out of memory Set Bug forwarded-to-address to 'https://github.com/Macaulay2/M2/issues/2319'. > tags -1 pending Bug #1000772 [src:macaulay2] macaulay2: autopkgtest regression on i386: out of memory Added tag(s) pending. -- 1000772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 917703, reopening 917703
Processing commands for cont...@bugs.debian.org:
> # src:golang-gopkg-macaroon.v2 was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 917703
Bug #917703 {Done: Debian FTP Masters }
[src:golang-gopkg-macaroon.v2] golang-gopkg-macaroon.v2: FTBFS:
build-dependency not installable: golang-github-juju-testing-dev
Unarchived Bug 917703
> reopen 917703
Bug #917703 {Done: Debian FTP Masters }
[src:golang-gopkg-macaroon.v2] golang-gopkg-macaroon.v2: FTBFS:
build-dependency not installable: golang-github-juju-testing-dev
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.0~git20171017.bed2a42-3+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 948075, reopening 948075
Processing commands for cont...@bugs.debian.org:
> # src:php-smbclient was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 948075
Bug #948075 {Done: Debian FTP Masters }
[php-smbclient] possible licensing issues
Unarchived Bug 948075
> reopen 948075
Bug #948075 {Done: Debian FTP Masters }
[php-smbclient] possible licensing issues
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.0.0-1+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
948075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 913254, reopening 913254
Processing commands for cont...@bugs.debian.org:
> # src:golang-gopkg-juju-environschema.v1 was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 913254
Bug #913254 {Done: Debian FTP Masters }
[src:golang-gopkg-juju-environschema.v1] golang-gopkg-juju-environschema.v1
build depends on golang-github-juju-schema-dev but it is not installable
Unarchived Bug 913254
> reopen 913254
Bug #913254 {Done: Debian FTP Masters }
[src:golang-gopkg-juju-environschema.v1] golang-gopkg-juju-environschema.v1
build depends on golang-github-juju-schema-dev but it is not installable
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.0~git20151104.7359fc7-4+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
913254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 1000187 in 4.0.7-1
Processing commands for cont...@bugs.debian.org: > fixed 1000187 4.0.7-1 Bug #1000187 [yubikey-manager] yubikey-manager: Exception when trying to add an oath account Marked as fixed in versions yubikey-manager/4.0.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1000187 is important
Processing commands for cont...@bugs.debian.org: > severity 1000187 important Bug #1000187 [yubikey-manager] yubikey-manager: Exception when trying to add an oath account Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000799: django-rules: Duplicate package of python-django-rules
Source: django-rules Severity: serious django-rules is already in Debian. The source package is python-django-rules. I will file a removal bug for the new django-rules source package since it is a violation of Debian Policy to have 2 different source packages provide the same binary package name. Thanks, Jeremy Bicha
Bug#1000798: vde2: Provides the same binary package as another source package
Source: vde2 Severity: serious The binary package libvdeplug2 is built by both source packages vde2 and vdeplug4. This violates Debian Policy. Thanks, Jeremy Bicha
Bug#1000797: vdeplug4: Provides the same binary package as another source package
Source: vdeplug4 Severity: serious The binary package libvdeplug2 is built by both source packages vde2 and vdeplug4. This violates Debian Policy. Thanks, Jeremy Bicha
Processed: bug 1000435 is forwarded to https://github.com/matplotlib/matplotlib/issues/21789 ...
Processing commands for cont...@bugs.debian.org: > forwarded 1000435 https://github.com/matplotlib/matplotlib/issues/21789 Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py Set Bug forwarded-to-address to 'https://github.com/matplotlib/matplotlib/issues/21789'. > forwarded 1000774 https://github.com/matplotlib/matplotlib/issues/21789 Bug #1000774 [python3-matplotlib] python3-matplotlib: Segfault on mips64el in draw Set Bug forwarded-to-address to 'https://github.com/matplotlib/matplotlib/issues/21789'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435 1000774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000796: update-passwd only remove item one time
Package: base-passwd Version: 3.5.51 Severity: critical update-passwd only removes once and exits even more than one items need to be removed. Root cause is walk is set to walk->next after remove_node(), in which the walk has been cleaned, so the while(walk) is terminated. $update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) 25 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group Adding user works well, but removing user just run one time. I attached a fix, with which, it works as $sudo update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Removing group "bin" (2) Removing group "lp" (7) Removing group "man" (12) Removing group "audio" (29) Removing group "video" (44) Removing group "games" (60) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) Removing user "bin" (2) Removing user "games" (5) Removing user "lp" (7) Removing user "mail" (8) 35 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group Thanks, ytao >From a2a96fa28fe132e34185ab1646b1f1ea4baf4942 Mon Sep 17 00:00:00 2001 From: Yue Tao Date: Thu, 25 Nov 2021 10:14:45 +0800 Subject: [PATCH] update-passwd.c: set walk to walk->next before removing update-passwd only removes once and exits even more than one items need to be removed. Root cause is walk is set to walk->next after remove_node(), in which the walk has been cleaned, so the while(walk) is terminated. Without the fix, the output of update-passwd $update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) 25 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group With the fix: $sudo update-passwd --verbose Adding group "postgres" (120) Adding group "nova" (162) Adding group "barbican" (978) Adding group "keystone" (42424) Adding group "neutron" (164) Adding group "ceilometer" (166) Adding group "sysinv" (168) Adding group "snmpd" (169) Adding group "fm" (195) Adding group "libvirt" (991) Adding group "ironic" (1874) Adding group "www" (1877) Removing group "daemon" (1) Removing group "bin" (2) Removing group "lp" (7) Removing group "man" (12) Removing group "audio" (29) Removing group "video" (44) Removing group "games" (60) Adding user "postgres" (120) Adding user "neutron" (164) Adding user "sysinv" (168) Adding user "snmpd" (169) Adding user "fm" (195) Adding user "barbican" (982) Adding user "ceilometer" (991) Adding user "keystone" (42424) Adding user "nova" (994) Adding user "ironic" (1874) Adding user "www" (1877) Removing user "daemon" (1) Removing user "bin" (2) Removing user "games" (5) Removing user "lp" (7) Removing user "mail" (8) 35 changes have been made, rewriting files Writing passwd-file to /etc/passwd Writing shadow-file to /etc/shadow Writing group-file to /etc/group Signed-off-by: Yue Tao --- update-passwd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upda
Bug#997567: marked as done (golang-github-yuin-goldmark-highlighting: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/yuin/goldmark-highlighting returned exi
Your message dated Mon, 29 Nov 2021 00:48:46 + with message-id and subject line Bug#997567: fixed in golang-github-yuin-goldmark-highlighting 0.0~git20210516.9216f9c-1 has caused the Debian Bug report #997567, regarding golang-github-yuin-goldmark-highlighting: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/yuin/goldmark-highlighting returned exit code 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.) -- 997567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-yuin-goldmark-highlighting Version: 0.0~git20200218.d1af22c-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package > golang-github-yuin-goldmark-highlighting > dpkg-buildpackage: info: source version 0.0~git20200218.d1af22c-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Anthony Fok > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem=golang --with golang >dh_auto_clean -O--buildsystem=golang >dh_autoreconf_clean -O--buildsystem=golang >dh_clean -O--buildsystem=golang > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building golang-github-yuin-goldmark-highlighting using > existing > ./golang-github-yuin-goldmark-highlighting_0.0~git20200218.d1af22c.orig.tar.xz > dpkg-source: info: building golang-github-yuin-goldmark-highlighting in > golang-github-yuin-goldmark-highlighting_0.0~git20200218.d1af22c-1.debian.tar.xz > dpkg-source: info: building golang-github-yuin-goldmark-highlighting in > golang-github-yuin-goldmark-highlighting_0.0~git20200218.d1af22c-1.dsc > debian/rules binary > dh binary --buildsystem=golang --with golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 > github.com/yuin/goldmark-highlighting > internal/goexperiment > internal/cpu > internal/unsafeheader > internal/abi > runtime/internal/atomic > runtime/internal/sys > internal/race > internal/bytealg > runtime/internal/math > sync/atomic > unicode > unicode/utf8 > encoding > math/bits > internal/itoa > math > unicode/utf16 > runtime > github.com/danwakefield/fnmatch > internal/reflectlite > sync > internal/testlog > errors > sort > internal/oserror > io > strconv > syscall > path > bytes > strings > reflect > html > regexp/syntax > bufio > internal/syscall/unix > time > internal/syscall/execenv > regexp > internal/poll > io/fs > os > encoding/binary > internal/fmtsort > encoding/base64 > path/filepath > fmt > net/url > encoding/json > github.com/dlclark/regexp2/syntax > github.com/yuin/goldmark/util > github.com/dlclark/regexp2 > github.com/alecthomas/chroma > github.com/alecthomas/chroma/formatters/html > github.com/alecthomas/chroma/lexers/internal > github.com/alecthomas/chroma/styles > github.com/alecthomas/chroma/lexers/a > github.com/alecthomas/chroma/lexers/b > github.com/alecthomas/chroma/lexers/p > github.com/alecthomas/chroma/lexers/j > github.com/alecthomas/chroma/lexers/e > github.com/alecthomas/chroma/lexers/d > github.com/alecthomas/chroma/lexers/f > github.com/alecthomas/chroma/lexers/c > github.com/alecthomas/chroma/lexers/i > github.com/alecthomas/chroma/lexers/k > github.com/alecthomas/chroma/lexers/l > github.com/alecthomas/chroma/lexers/n > github.com/alecthomas/chroma/lexers/o > github.com/alecthomas/chroma/lexers/q > github.com/alecthomas/chroma/lexers/r > github.com/alecthomas/chroma/lexers/t > github.com/alecthomas/chroma/lexers/h > github.com/alecthomas/chroma/lexers/v > github.com/alecthomas/chroma/lexers/w > github.com/alecthomas/chroma/lexers/x > github.com/alecthomas/chroma/lexers/circular > github.com/alecthomas/chroma/lexers/g > github.com/alecthomas/chroma/lexers/m > github.com/alecthomas/chroma/lexers/s > github.com/alecthomas/chroma/lexers/y > github.com/alecthomas/chroma/lexers/z > github.com/alecthomas/chroma/lexers > github.com/yuin/goldmark/text > github.com/yuin/goldmark/ast > github
Processed: bug 998364 is forwarded to https://github.com/socketry/async-rspec/issues/16
Processing commands for cont...@bugs.debian.org: > forwarded 998364 https://github.com/socketry/async-rspec/issues/16 Bug #998364 [src:ruby-async-rspec] ruby-async-rspec: autopkgtest failures on armhf and i386 Set Bug forwarded-to-address to 'https://github.com/socketry/async-rspec/issues/16'. > thanks Stopping processing here. Please contact me if you need assistance. -- 998364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997567: marked as pending in golang-github-yuin-goldmark-highlighting
Control: tag -1 pending Hello, Bug #997567 in golang-github-yuin-goldmark-highlighting 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/go-team/packages/golang-github-yuin-goldmark-highlighting/-/commit/61ef0ed855d7c6fdc277454f6d1fb192c63dedbf Patch highlighting_test.go to allow for tabindex="0" in wrapper This fixes FTBFS with chroma v0.9.2 and up while maintaining backward compatibility with older chroma. Closes: #997567 (this message was generated automatically) -- Greetings https://bugs.debian.org/997567
Processed: Bug#997567 marked as pending in golang-github-yuin-goldmark-highlighting
Processing control commands: > tag -1 pending Bug #997567 [src:golang-github-yuin-goldmark-highlighting] golang-github-yuin-goldmark-highlighting: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/yuin/goldmark-highlighting returned exit code 1 Added tag(s) pending. -- 997567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ptl 996553
Processing commands for cont...@bugs.debian.org: > fixed 996553 2.0.0-2 Bug #996553 [src:ptl] ptl: autopkgtest failure on armhf Marked as fixed in versions ptl/2.0.0-2. > tags 996553 - fixed-upstream Bug #996553 [src:ptl] ptl: autopkgtest failure on armhf Removed tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 996553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996116: marked as done (r10k: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Mon, 29 Nov 2021 00:06:48 + with message-id and subject line Bug#996116: fixed in r10k 3.7.0-2.1 has caused the Debian Bug report #996116, regarding r10k: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: 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.) -- 996116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r10k Version: 3.7.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, r10k was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 2, expected 0..1) > Shared Example Group: "a git working repository" called from > ./spec/integration/git/rugged/working_repository_spec.rb:12 > # > /usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in > `fetch' > # > /usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in > `fetch' > # ./lib/r10k/git/rugged/working_repository.rb:96:in `block (2 levels) > in fetch' > # ./lib/r10k/git/rugged/base_repository.rb:67:in `with_repo' > # ./lib/r10k/git/rugged/working_repository.rb:139:in `with_repo' > # ./lib/r10k/git/rugged/working_repository.rb:96:in `block in fetch' > # ./lib/r10k/git.rb:188:in `with_proxy' > # ./lib/r10k/git/rugged/working_repository.rb:95:in `fetch' > # ./spec/shared-examples/git/working_repository.rb:136:in `block (4 > levels) in ' > > Finished in 3.67 seconds (files took 0.61891 seconds to load) > 784 examples, 24 failures, 3 pending > > Failed examples: > > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:2:1]' # > R10K::Git::Rugged::BareRepository behaves like a git repository listing tags > lists all tags in alphabetical order > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:1]' # > R10K::Git::Rugged::BareRepository behaves like a git repository resolving > refs can resolve branches > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:2]' # > R10K::Git::Rugged::BareRepository behaves like a git repository resolving > refs can resolve tags > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:3]' # > R10K::Git::Rugged::BareRepository behaves like a git repository resolving > refs can resolve commits > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:4]' # > R10K::Git::Rugged::BareRepository behaves like a git repository resolving > refs returns nil when the object cannot be resolved > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:1:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository checking > for the presence of the repo exists if the repo is present > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:2:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository cloning > the repo creates the repo at the expected location > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:2:2:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository cloning > the repo without a proxy does not change proxy ENV > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:2:3:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository cloning > the repo with a proxy manages proxy-related ENV vars > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:3:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository updating > the repo fetches objects from the remote > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:3:2:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository updating > the repo without a proxy does not change proxy ENV > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:3:3:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository updating > the repo with a proxy manages proxy-related ENV vars > rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:4:1]' # > R10K::Git::Rugged::BareRepository behaves like a git bare repository listing > branches lists all branches in
Bug#1000792: gnuradio: unsatisfiable Build-Depends(-Arch) on s390x: libunwind-dev
Source: gnuradio Version: 3.9.4.0-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org libunwind-dev does not exist on s390x. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#1000791: uhd: FTBFS on mipsel:
Source: uhd Version: 4.1.0.4-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org uhd fails to build on mipsel: | FAILED: python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o | /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_STD_EXPERIMENTAL_STRING_VIEW -DBOOST_ASIO_DISABLE_STD_STRING_VIEW -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DHAVE_CONFIG_H -DUHD_LOG_CONSOLE_COLOR -DUHD_LOG_CONSOLE_LEVEL=2 -DUHD_LOG_FILE_LEVEL=2 -DUHD_LOG_MIN_LEVEL=1 -Dpyuhd_EXPORTS -I/<>/obj-mipsel-linux-gnu/include -I/<>/host/include -I/usr/include/python3.9 -I/<>/host/lib/deps/pybind11/include -I/usr/lib/python3/dist-packages/numpy/core/include -I/<>/host/lib -I/<>/obj-mipsel-linux-gnu/_cmrc/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden -O2 -g -DNDEBUG -fPIC -Wall -Wextra -Wsign-compare -std=gnu++14 -MD -MT python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o -MF python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o.d -o python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o -c /<>/host/python/pyuhd.cpp | | cc1plus: out of memory allocating 2217812 bytes after a total of 59752448 bytes | ninja: build stopped: subcommand failed. See https://buildd.debian.org/status/fetch.php?pkg=uhd&arch=mipsel&ver=4.1.0.4-2&stamp=1638083831&raw=0 If you start an uncoordinated transition, please ensure at least that the package builds everywhere. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#1000790: uhd: FTBFS on ppc64el: c++: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’?
Source: uhd Version: 4.1.0.4-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org uhd fails to build on ppc64el: | FAILED: lib/CMakeFiles/uhd.dir/transport/uhd-dpdk/dpdk_common.cpp.o | /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_STD_EXPERIMENTAL_STRING_VIEW -DBOOST_ASIO_DISABLE_STD_STRING_VIEW -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DHAVE_CONFIG_H -DHAVE_DPDK -DUHD_DLL_EXPORTS -DUHD_LOG_CONSOLE_COLOR -DUHD_LOG_CONSOLE_LEVEL=2 -DUHD_LOG_FILE_LEVEL=2 -DUHD_LOG_MIN_LEVEL=1 -I/<>/obj-powerpc64le-linux-gnu/include -I/<>/host/include -I/<>/host/lib/include -I/<>/obj-powerpc64le-linux-gnu/lib/include -I/<>/host/lib/deps/flatbuffers/include -I/<>/obj-powerpc64le-linux-gnu/lib/ic_reg_maps -I/<>/host/lib/convert -I/<>/obj-powerpc64le-linux-gnu/lib/convert -I/<>/host/lib/usrp -I/<>/host/lib/usrp/common/ad9361_driver -I/<>/host/lib/usrp/common -I/usr/include/dpdk -I/usr/include/libnl3 -I/usr/include/dpdk/../powerpc64le-linux-gnu/dpdk -I/usr/include/powerpc64le-linux-gnu/dpdk -I/<>/obj-powerpc64le-linux-gnu/lib/transport/nirio/lvbitx -I/usr/include/libusb-1.0 -I/<>/host/lib/transport/uhd-dpdk -I/<>/host/lib/deps/rpclib/include -I/usr/include/python3.9 -I/<>/host/lib/deps/pybind11/include -I/<>/obj-powerpc64le-linux-gnu/_cmrc/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden -O2 -g -DNDEBUG -fPIC -Wall -Wextra -Wsign-compare -std=gnu++14 -march=native -D_GNU_SOURCE -MD -MT lib/CMakeFiles/uhd.dir/transport/uhd-dpdk/dpdk_common.cpp.o -MF lib/CMakeFiles/uhd.dir/transport/uhd-dpdk/dpdk_common.cpp.o.d -o lib/CMakeFiles/uhd.dir/transport/uhd-dpdk/dpdk_common.cpp.o -c /<>/host/lib/transport/uhd-dpdk/dpdk_common.cpp | c++: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’? See https://buildd.debian.org/status/fetch.php?pkg=uhd&arch=ppc64el&ver=4.1.0.4-2&stamp=1638057565&raw=0 If you start an uncoordinated transition, please at least ensure that the package builds everywhere. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#999873: marked as done (python3-eventlet: Eventlet greendns incompatible with dnspython 2.1.0)
Your message dated Sun, 28 Nov 2021 23:33:39 + with message-id and subject line Bug#999873: fixed in python-eventlet 0.30.2-5 has caused the Debian Bug report #999873, regarding python3-eventlet: Eventlet greendns incompatible with dnspython 2.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-eventlet Version: 0.30.2-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Once again, eventlet is incompatible with dnspython and needs fixing. The specific test that is failing is tests.socket_test.test_dns_methods_are_green. I attempted to trouble shoot it a bit and determined that there is a socket error: [Errno -2] Name or service not known. Note: Used the FTBFS tag since that's the closest thing we have to a autopkgttest regression. Scott K --- End Message --- --- Begin Message --- Source: python-eventlet Source-Version: 0.30.2-5 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-eventlet, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-eventlet 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: Mon, 29 Nov 2021 00:02:15 +0100 Source: python-eventlet Architecture: source Version: 0.30.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Thomas Goirand Closes: 999873 Changes: python-eventlet (0.30.2-5) unstable; urgency=medium . * Add greendns-with-dnspython-2.10.patch (Closes: #999873). Checksums-Sha1: ebbfafcf2ec9c3ff681a157cfa9c553971ffd157 2506 python-eventlet_0.30.2-5.dsc f52190595491cdfe5b3bbce3309b4071b83ebc87 24948 python-eventlet_0.30.2-5.debian.tar.xz be2e3dc8ecb68566fb2f456f87c5bfb1b7b4 8377 python-eventlet_0.30.2-5_amd64.buildinfo Checksums-Sha256: 1deb698f3d610952dc11f40f4177ee58d44f3b78a47c3c8628de6561f1d678e3 2506 python-eventlet_0.30.2-5.dsc 651549025bcb0a066f97e84431c06226fc26b25e4ae65fae51c6bcd1044d90c8 24948 python-eventlet_0.30.2-5.debian.tar.xz bfbb1ac0bd87c2636f4ecae190f19c50cadd18cda75f9632d54a3486a3ed498e 8377 python-eventlet_0.30.2-5_amd64.buildinfo Files: ddaf35d4ae46df85d8f3137ef2caeabb 2506 python optional python-eventlet_0.30.2-5.dsc 3ffbf29177bb24acef6a7111b90fb15a 24948 python optional python-eventlet_0.30.2-5.debian.tar.xz c980c77edaed82fb370706b4ea0adf8b 8377 python optional python-eventlet_0.30.2-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmGkDcEACgkQ1BatFaxr Q/7DBQ/8DyvxGzm57CSSoxd90F4+DCRN9ekisBhKXKGzvP9Npi2ev7skRt7WLVXG znPRiZz+e/GO0I7eldR8FzsABgKfMHYZM25Hl5gUzWCJEKsRZGNh6UfbTCxHGFzU yb5QLH9GzWFMJXx92vY9JcI3eGMwA+v8fu3QQk4HClzoGpGpjXn3RXsPWGjyOdEr W61/Csa2YodNaOU9Vh/KhUK477WOs9sxiOt42NnD4Vv7JsCwyW1ZlZgMWgbofpkX k522G3KTDd0Qdt/yFOA3lDhn41lo3WwOF4+DCZf+eiVF5ht+sUFe6t4uMIbPMA9o A4U/umfoBog+5xS9BnSUlXn0SyxoEsSjv00IrGTASwXfTuQ+K0r5MF51l+WruWXx nY5uRcsUEq8RK9q4JgChL8HDMHcmwKEetVJVYSKkaBpebrcyonvhq/IZe64tfYHB YdSXr1Ai8dPiP5tE55tjOCSPxIiF/NIzPwYI5bULMt9yPxXVkGhmf94+wt9X2YsU LfI2E9Cd0IY7VMgQiwverGeP8Cgq/yE0YfW3ykK/eHAKT1bzUPeCFUmlbTOKH/eM nu1tk9CzmS1En+sskEPeI14A/ReiehRfMkoamJ1zD109B2O8RoUDymZ+elosEhwJ jJi7Dic8lbvqQhp+sJ3E5HXVPdeW1CZVU/1NtPVPUxYJt8mvwrA= =ZquE -END PGP SIGNATURE End Message ---
Processed: Bug#999873 marked as pending in python-eventlet
Processing control commands: > tag -1 pending Bug #999873 [python3-eventlet] python3-eventlet: Eventlet greendns incompatible with dnspython 2.1.0 Added tag(s) pending. -- 999873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999873: marked as pending in python-eventlet
Control: tag -1 pending Hello, Bug #999873 in python-eventlet 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-eventlet/-/commit/2d3e649bcd20d42f03dd85ab8e9e47b1205eae8f Add greendns-with-dnspython-2.10.patch (Closes: #999873). (this message was generated automatically) -- Greetings https://bugs.debian.org/999873
Bug#1000746: marked as done (vtk9 FTBFS: error: ‘vtkFreeTypeToolsFaceRequester’ was not declared in this scope)
Your message dated Sun, 28 Nov 2021 22:52:11 + with message-id and subject line Bug#1000746: fixed in vtk9 9.1.0+really9.0.3+dfsg1-4 has caused the Debian Bug report #1000746, regarding vtk9 FTBFS: error: ‘vtkFreeTypeToolsFaceRequester’ was not declared in this scope 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.) -- 1000746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vtk9 Version: 9.1.0+really9.0.3+dfsg1-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=vtk9&ver=9.1.0%2Breally9.0.3%2Bdfsg1-3 ... /<>/Rendering/FreeType/vtkFreeTypeTools.cxx:382:1: error: expected constructor, destructor, or type conversion before ‘vtkFreeTypeToolsFaceRequester’ 382 | vtkFreeTypeToolsFaceRequester( | ^ /<>/Rendering/FreeType/vtkFreeTypeTools.cxx: In member function ‘virtual FT_Error vtkFreeTypeTools::CreateFTCManager()’: /<>/Rendering/FreeType/vtkFreeTypeTools.cxx:1154:61: error: ‘vtkFreeTypeToolsFaceRequester’ was not declared in this scope; did you mean ‘vtkFreeTypeToolsCleanupCounter’? 1154 | this->MaximumNumberOfSizes, this->MaximumNumberOfBytes, vtkFreeTypeToolsFaceRequester, | ^ | vtkFreeTypeToolsCleanupCounter ... --- End Message --- --- Begin Message --- Source: vtk9 Source-Version: 9.1.0+really9.0.3+dfsg1-4 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of vtk9, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated vtk9 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, 28 Nov 2021 23:34:47 +0100 Source: vtk9 Architecture: source Version: 9.1.0+really9.0.3+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Anton Gladky Closes: 1000746 Changes: vtk9 (9.1.0+really9.0.3+dfsg1-4) unstable; urgency=medium . * [90cbc11] vtkFreeTypeTools: avoid using an internal macro. (Closes: #1000746) * [9e418ba] Use python3-dev in BD Checksums-Sha1: 21dc59b7454c60c0825e575b73bca828388fa0c3 3762 vtk9_9.1.0+really9.0.3+dfsg1-4.dsc a947ecfdaa061850205ea73f1e7e258248b4423c 22280 vtk9_9.1.0+really9.0.3+dfsg1-4.debian.tar.xz 5108a20e6541b9750203c9dcd5c2ea9a43297d2b 27047 vtk9_9.1.0+really9.0.3+dfsg1-4_source.buildinfo Checksums-Sha256: d4e22bde4e98db0317a0c606e9665a325d9e64aea6b2134185258afbb2d84bf9 3762 vtk9_9.1.0+really9.0.3+dfsg1-4.dsc 02203e2da0b90f7af3ff185bdedfdf91a5b2dccf5c9fe188f64fc296b5cd85c0 22280 vtk9_9.1.0+really9.0.3+dfsg1-4.debian.tar.xz 73a3d6bf6db75b1f0f3d059857b99a08f6f035eaffbb297811154c990aa56e56 27047 vtk9_9.1.0+really9.0.3+dfsg1-4_source.buildinfo Files: 37ca95f5ac1dc4d8565f90d0db49a470 3762 graphics optional vtk9_9.1.0+really9.0.3+dfsg1-4.dsc 777d23ed20de1106c5828797f6b8b4b7 22280 graphics optional vtk9_9.1.0+really9.0.3+dfsg1-4.debian.tar.xz 516506c936bdb4fa4f3845395275ef2a 27047 graphics optional vtk9_9.1.0+really9.0.3+dfsg1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmGkBLMACgkQ0+Fzg8+n /wbPRw/9G1sgJX7IOIoC85K7umr2+FCwqFmleshW5RLK9IlwOPfSdeJKEUzPsliw AQhzk/DKb38TK/1aOtCLepCwjYaaIoNCLv1tLoUNQmDCzi28MFIIW+SNLaip2gFR PI5apgDBfXwpDgNyIUMLilXCY9pBQs3ZdjQRPf3S99UT+YYIvAKNA4tUNIxGCFwm Vfy55z1zsQ2TPGHi6VFJlfZi9pKHn7QydtRv25lHsa+jrhibiF8LzHy0L74I82o2 7xWP5wiwb58qRYpwXBm9QO3tDWX+jom1WYQTnY8IRwq/w9XHue4o+YoNPNCAcmE2 pnGonSLeIIQy4QGl+PDcGrgvb2KqGdAOmdU6zltITuhHKXJwL3009xfnEAiW4Azx krfDuWwkbA0dEeXFqIhRFXIN9meu3+DNsNAXrVJi5UwGJnsAWzDPzPyXZMEqOOnB L3l4klMuzUB7k0DKTukRn0TwufJd+lket6ndBKiLs7CorfoNEWDEPmKTnUDhtUDy B1NWjNZpjJ67CUgPRJLaJaQ6csW37jn3rFrePsirvS1Fu2ARoA7Im7v3bryNvGKC LHckDhDsfAfXKc5460/kQqZzWGpxhPxJrnjAFNy3G9RbmnRGUweenrqRiofsbp11 UX2kTOp6OhCgg0Tf23UGUs9O8n+IhJ7yHedXZUjKP0XCrVL+Aug= =xjaI -END PGP SIGNATURE End Message ---
Bug#997334: marked as done (postgresql-13: FTBFS: configure: error: unrecognized option: `--runstatedir=/run')
Your message dated Sun, 28 Nov 2021 22:35:50 +
with message-id
and subject line Bug#1000590: Removed package(s) from unstable
has caused the Debian Bug report #997334,
regarding postgresql-13: FTBFS: configure: error: unrecognized option:
`--runstatedir=/run'
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.)
--
997334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-13
Version: 13.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>--with-libxslt \
>PYTHON=/usr/bin/python3 \
>--mandir=/usr/share/postgresql/13/man
> --docdir=/usr/share/doc/postgresql-doc-13 --sysconfdir=/etc/postgresql-common
> --datarootdir=/usr/share/ --datadir=/usr/share/postgresql/13
> --bindir=/usr/lib/postgresql/13/bin --libdir=/usr/lib/x86_64-linux-gnu/
> --libexecdir=/usr/lib/postgresql/ --includedir=/usr/include/postgresql/
> --with-extra-version=" (Debian 13.4-3)" --enable-nls --enable-thread-safety
> --enable-tap-tests --enable-debug --enable-dtrace --disable-rpath
> --with-uuid=e2fs --with-gnu-ld --with-pgport=5432
> --with-system-tzdata=/usr/share/zoneinfo --with-llvm
> LLVM_CONFIG=/usr/bin/llvm-config-11 CLANG=/usr/bin/clang-11 --with-systemd
> --with-selinux AWK=mawk MKDIR_P='/bin/mkdir -p' PROVE='/usr/bin/prove'
> TAR='/bin/tar' XSLTPROC='xsltproc --nonet' CFLAGS='-g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fno-omit-frame-pointer' LDFLAGS='-Wl,-z,relro
> -Wl,-z,now' \
>--with-gssapi --with-ldap
> cd build && ../configure --build=x86_64-linux-gnu --prefix=/usr
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
> --disable-option-checking --disable-silent-rules
> --libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
> --disable-maintainer-mode --disable-dependency-tracking --with-icu --with-tcl
> --with-perl --with-python --with-pam --with-openssl --with-libxml
> --with-libxslt PYTHON=/usr/bin/python3 --mandir=/usr/share/postgresql/13/man
> --docdir=/usr/share/doc/postgresql-doc-13 --sysconfdir=/etc/postgresql-common
> --datarootdir=/usr/share/ --datadir=/usr/share/postgresql/13
> --bindir=/usr/lib/postgresql/13/bin --libdir=/usr/lib/x86_64-linux-gnu/
> --libexecdir=/usr/lib/postgresql/ --includedir=/usr/include/postgresql/
> "--with-extra-version= (Debian 13.4-3)" --enable-nls --enable-thread-safety
> --enable-tap-tests --enable-debug --enable-dtrace --disable-rpath
> --with-uuid=e2fs --with-gnu-ld --with-pgport=5432
> --with-system-tzdata=/usr/share/zoneinfo --with-llvm
> LLVM_CONFIG=/usr/bin/llvm-config-11 CLANG=/usr/bin/clang-11 --with-systemd
> --with-selinux AWK=mawk "MKDIR_P=/bin/mkdir -p" PROVE=/usr/bin/prove
> TAR=/bin/tar "XSLTPROC=xsltproc --nonet" "CFLAGS=-g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fno-omit-frame-pointer" "LDFLAGS=-Wl,-z,relro
> -Wl,-z,now" --with-gssapi --with-ldap
> configure: error: unrecognized option: `--runstatedir=/run'
> Try `../configure --help' for more information
> dh_auto_configure: error: cd build && ../configure --build=x86_64-linux-gnu
> --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
> --disable-option-checking --disable-silent-rules
> --libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
> --disable-maintainer-mode --disable-dependency-tracking --with-icu --with-tcl
> --with-perl --with-python --with-pam --with-openssl --with-libxml
> --with-libxslt PYTHON=/usr/bin/python3 --mandir=/usr/share/postgresql/13/man
> --docdir=/usr/share/doc/postgresql-doc-13 --sysconfdir=/etc/postgresql-common
> --datarootdir=/usr/share/ --datadir=/usr/share/postgresql/13
> --bindir=/usr/lib/postgresql/13/bin --libdir=/usr/lib/x86_64-linux-gnu/
> --libexecdir=/usr/lib/postgresql/ --includedir=/usr/include/postgresql/
> "--with-extra-version= (Debian 13.4-3)" --enable-nls --enable-thread-safety
> --enable-tap-tests --enable-debug --enable-dtrace --disable-rpath
> --with-uuid=e2fs --with-gnu-ld --with-pgport=5432
> --with-system-tzdata=/usr/share/zoneinfo --with-llvm
> LLVM_CONFIG=/usr/bin/llvm-config-11 CLANG=/usr/bin/clang-11 --with-systemd
> --with-selinux AWK=mawk "MKDIR_P=/b
Bug#924816: marked as done (mingw-ocaml: FTBFS: hasgot.c:(.text+0x13): undefined reference to `tgetent')
Your message dated Sun, 28 Nov 2021 22:32:13 + with message-id and subject line Bug#1000569: Removed package(s) from unstable has caused the Debian Bug report #924816, regarding mingw-ocaml: FTBFS: hasgot.c:(.text+0x13): undefined reference to `tgetent' 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.) -- 924816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mingw-ocaml Version: 4.01.0~20140328-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccLq4zil.o: in function `main': > hasgot.c:(.text+0x13): undefined reference to `tgetent' > /usr/bin/ld: hasgot.c:(.text+0x18): undefined reference to `tgetstr' > /usr/bin/ld: hasgot.c:(.text+0x1d): undefined reference to `tgetnum' > /usr/bin/ld: hasgot.c:(.text+0x22): undefined reference to `tputs' > collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/2019/03/15/mingw-ocaml_4.01.0~20140328-1_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 4.01.0~20140328-1+rm Dear submitter, as the package mingw-ocaml 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/1000569 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#972259: marked as done (FTBFS with OCaml 4.11.1 (-unsafe-string is not available))
Your message dated Sun, 28 Nov 2021 22:34:04 + with message-id and subject line Bug#1000570: Removed package(s) from unstable has caused the Debian Bug report #972259, regarding FTBFS with OCaml 4.11.1 (-unsafe-string is not available) 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.) -- 972259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:galax Version: 1.1-16 Severity: serious Tags: ftbfs Dear Maintainer, Your package galax FTBFS with OCaml 4.11.1 because -unsafe-string is no longer available. Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 1.1-16+rm Dear submitter, as the package galax 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/1000570 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#924764: marked as done (mingw-ocaml: FTBFS (cp: cannot stat 'objinfo_helper': No such file or directory))
Your message dated Sun, 28 Nov 2021 22:32:13 + with message-id and subject line Bug#1000569: Removed package(s) from unstable has caused the Debian Bug report #924764, regarding mingw-ocaml: FTBFS (cp: cannot stat 'objinfo_helper': No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 924764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mingw-ocaml Version: 4.01.0~20140328-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_update_autotools_config -i dh_auto_configure -i dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use) debian/rules override_dh_auto_build make[1]: Entering directory '/<>' rm -rf .pc build patches stamp-* mkdir -p /<>/bindir make BINARY_DIR=/<>/bindir MINGW_HOST=i686-w64-mingw32 make[2]: Entering directory '/<>' mkdir -p patches find patches.in | grep '.patch' | while read i; do \ [... snipped ...] cp libbigarray.a /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/ cd /<>/bindir/usr/i686-w64-mingw32/lib/ocaml; i686-w64-mingw32-ranlib libbigarray.a cp bigarray.cma bigarray.cmi bigarray.mli /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/ if test -n "bigarray.h"; then cp bigarray.h /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/caml/; fi make[3]: Leaving directory '/<>/build/ocaml/otherlibs/bigarray' make[3]: Entering directory '/<>/build/ocaml/otherlibs/systhreads' cp dllthreads.dll /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/stublibs/dllthreads.dll cp libthreads.a /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/libthreads.a cd /<>/bindir/usr/i686-w64-mingw32/lib/ocaml; i686-w64-mingw32-ranlib libthreads.a mkdir -p /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/threads cp thread.cmi mutex.cmi condition.cmi event.cmi threadUnix.cmi threads.cma /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/threads rm -f /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/threads/stdlib.cma cp threads.h /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/caml/threads.h make[3]: Leaving directory '/<>/build/ocaml/otherlibs/systhreads' make[3]: Entering directory '/<>/build/ocaml/otherlibs/win32graph' if test -f dllgraphics.dll; then \ cp dllgraphics.dll /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/stublibs/; fi cp libgraphics.a /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/ cd /<>/bindir/usr/i686-w64-mingw32/lib/ocaml; i686-w64-mingw32-ranlib libgraphics.a cp graphics.cma graphics.cmi graphics.mli /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/ if test -n ""; then cp /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/caml/; fi make[3]: Leaving directory '/<>/build/ocaml/otherlibs/win32graph' cd build/ocaml && make BINDIR=/<>/bindir/usr/i686-w64-mingw32/bin \ LIBDIR=/<>/bindir/usr/i686-w64-mingw32/lib/ocaml \ -C tools install make[3]: Entering directory '/<>/build/ocaml/tools' cp ocamldep /<>/bindir/usr/i686-w64-mingw32/bin/ocamldep if test -f ocamldep.opt; \ then cp ocamldep.opt /<>/bindir/usr/i686-w64-mingw32/bin/ocamldep.opt; else :; fi cp ocamlprof /<>/bindir/usr/i686-w64-mingw32/bin/ocamlprof cp ocamlcp /<>/bindir/usr/i686-w64-mingw32/bin/ocamlcp cp ocamloptp /<>/bindir/usr/i686-w64-mingw32/bin/ocamloptp cp profiling.cmi profiling.cmo /<>/bindir/usr/i686-w64-mingw32/lib/ocaml cp ocamlmklib /<>/bindir/usr/i686-w64-mingw32/bin/ocamlmklib cp objinfo /<>/bindir/usr/i686-w64-mingw32/bin/ocamlobjinfo cp objinfo_helper /<>/bindir/usr/i686-w64-mingw32/lib/ocaml/objinfo_helper cp: cannot stat 'objinfo_helper': No such file or directory make[3]: *** [Makefile.shared:295: install] Error 1 make[3]: Leaving directory '/<>/build/ocaml/tools' make[2]: *** [Makefile:153: stamp-binary-mingw-ocaml] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:29: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mingw-ocaml.h
Bug#994310: marked as done (meliae: Removal of the python3-*-dbg packages in sid/bookworm)
Your message dated Sun, 28 Nov 2021 22:25:25 + with message-id and subject line Bug#1000548: Removed package(s) from unstable has caused the Debian Bug report #994310, regarding meliae: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 994310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:meliae Version: 0.5.1+bzr231-3 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https://lists.debian.org/debian-python/2021/09/msg4.html Stop building the python3-*-dbg package, but be careful that all the reverse dependencies are also removed. Please check for dependencies, build dependencies AND autopkg tests. If help is needed, please ask on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.5.1+bzr231-3+rm Dear submitter, as the package meliae 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/1000548 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#972011: marked as done (meliae's autopkg tests fail, and package ftbfs with python3.9)
Your message dated Sun, 28 Nov 2021 22:25:25 +
with message-id
and subject line Bug#1000548: Removed package(s) from unstable
has caused the Debian Bug report #972011,
regarding meliae's autopkg tests fail, and package ftbfs with python3.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
972011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:meliae
Version: 0.5.1+bzr231-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
[...]
Setting up autopkgtest-satdep (0) ...
Processing triggers for libc-bin (2.30-8) ...
(Reading database ... 12964 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [04:15:08]: test testsuite: [---
Traceback (most recent call last):
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/lib/python3.8/unittest/__main__.py", line 18, in
main(module=None)
File "/usr/lib/python3.8/unittest/main.py", line 100, in __init__
self.parseArgs(argv)
File "/usr/lib/python3.8/unittest/main.py", line 147, in parseArgs
self.createTests()
File "/usr/lib/python3.8/unittest/main.py", line 158, in createTests
self.test = self.testLoader.loadTestsFromNames(self.testNames,
File "/usr/lib/python3.8/unittest/loader.py", line 220, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python3.8/unittest/loader.py", line 220, in
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python3.8/unittest/loader.py", line 205, in loadTestsFromName
test = obj()
File
"/tmp/autopkgtest-lxc.yomruset/downtmp/build.29e/src/meliae/tests/__init__.py",
line 47, in test_suite
module = __import__(full_name, {}, {}, [None])
File
"/tmp/autopkgtest-lxc.yomruset/downtmp/build.29e/src/meliae/tests/test__intset.py",
line 21, in
from meliae import (
ImportError: cannot import name '_intset' from 'meliae'
(/tmp/autopkgtest-lxc.yomruset/downtmp/build.29e/src/meliae/__init__.py)
[...]
building 'meliae._scanner' extension
creating build
creating build/temp.linux-x86_64-3.9
creating build/temp.linux-x86_64-3.9/meliae
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>/meliae-0.5.1+bzr231=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.9 -c meliae/_scanner.c -o
build/temp.linux-x86_64-3.9/meliae/_scanner.o
meliae/_scanner.c: In function ‘__pyx_pymod_exec__scanner’:
meliae/_scanner.c:3435:46: error: ‘PyGC_Head’ undeclared (first use in this
function)
3435 | __pyx_t_1 = __Pyx_PyInt_FromSize_t((sizeof(PyGC_Head))); if
(unlikely(!__pyx_t_1)) __PYX_ERR(0, 52, __pyx_L1_error)
| ^
meliae/_scanner.c:3435:46: note: each undeclared identifier is reported only
once for each function it appears in
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
--- End Message ---
--- Begin Message ---
Version: 0.5.1+bzr231-3+rm
Dear submitter,
as the package meliae 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/1000548
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#973128: marked as done (celery-batches: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Sun, 28 Nov 2021 22:23:33 +
with message-id
and subject line Bug#1000547: Removed package(s) from unstable
has caused the Debian Bug report #973128,
regarding celery-batches: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.9 3.8" 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.)
--
973128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: celery-batches
Version: 0.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package celery-batches
> dpkg-buildpackage: info: source version 0.2-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Martin
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.8/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building celery-batches using existing
> ./celery-batches_0.2.orig.tar.gz
> dpkg-source: info: building celery-batches in
> celery-batches_0.2-2.debian.tar.xz
> dpkg-source: info: building celery-batches in celery-batches_0.2-2.dsc
> 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:217: python3.9 setup.py config
> running config
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/t
> copying t/__init__.py -> /<>/.pybuild/cpython3_3.9/build/t
> creating /<>/.pybuild/cpython3_3.9/build/celery_batches
> copying celery_batches/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/celery_batches
> creating /<>/.pybuild/cpython3_3.9/build/t/integration
> copying t/integration/test_batches.py ->
> /<>/.pybuild/cpython3_3.9/build/t/integration
> copying t/integration/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/t/integration
> copying t/integration/tasks.py ->
> /<>/.pybuild/cpython3_3.9/build/t/integration
> copying t/integration/conftest.py ->
> /<>/.pybuild/cpython3_3.9/build/t/integration
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/t
> copying t/__init__.py -> /<>/.pybuild/cpython3_3.8/build/t
> creating /<>/.pybuild/cpython3_3.8/build/celery_batches
> copying celery_batches/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/celery_batches
> creating /<>/.pybuild/cpython3_3.8/build/t/integration
> copying t/integration/test_batches.py ->
> /<>/.pybuild/cpython3_3.8/build/t/integration
> copying t/integration/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/t/integration
> copying t/integration/tasks.py ->
> /<>/.pybuild/cpython3_3.8/build/t/integration
> copying t/integration/conftest.py ->
> /<>/.pybuild/cpython3_3.8/build/t/integration
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m unittest discover -v
> celery_batches (unittest.loader._FailedTest) ... ERROR
> t.integration.test_batches (unittest.loader._FailedTest) ... ERROR
>
> ==
> ERROR: celery_batches (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test m
Bug#973183: marked as done (doublex: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Sun, 28 Nov 2021 22:22:03 +
with message-id
and subject line Bug#1000545: Removed package(s) from unstable
has caused the Debian Bug report #973183,
regarding doublex: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i
python{version} -p "3.9 3.8" 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.)
--
973183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doublex
Version: 1.9.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --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:217: python3.9 setup.py config
> running config
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/proxy.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/__init__.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/matchers.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/safeunicode.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/doubles.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/py27_backports.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/tracer.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> copying doublex/internal.py ->
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/proxy.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/__init__.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/matchers.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/safeunicode.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/doubles.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/py27_backports.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/tracer.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
> copying doublex/internal.py ->
> /<>/.pybuild/cpython3_3.8_doublex/build/doublex
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:284: cp -r /<>/doublex/test*
> /<>/.pybuild/cpython3_3.9_doublex/build/doublex
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_doublex/build;
> python3.9 -m nose -v doublex.test3
> test_wrong_try_to_test_an_async_invocation
> (doublex.test3.test.async_race_condition_test.AsyncTests) ... ok
> test_chain_default_behavior (doublex.test3.test.chain_tests.ChainTests) ... ok
> test_ANY_arg_method_returning_none
> (doublex.test3.test.report_tests.InvocationReportTests) ... ok
> test_int_arg_method_returning_int
> (doublex.test3.test.report_tests.InvocationReportTests) ... ok
> test_except_method_with_2_kwargs_returning_dict_but_nothing_called
> (doublex.test3.test.report_tests.MockReportTest) ... ok
> test_except_method_with_2_str_args_returning_str_but_nothing_called
> (doublex.test3.test.report_tests.MockReportTest) ... ok
> test_expect_1_void_method_but_nothing_called
> (doublex.test3.test.report_tests.MockReportTest) ... ok
> test_expect_2_void_methods_but_nothing_called
> (doublex.test3.test.report_tests.MockReportTest) ... ok
> test_expect_4_calls_but_only_2_called
> (doublex.test3.test.report_tests.MockReportTest) ... ok
> test_expect_method_with_2_int_args_returning_int_but_nothing_called
> (doublex.test3.test.report_tests.MockReportTest) ... ok
> test_expect_none_but_someting_unexpected_called
> (doublex.test3.test.report_tests.MockReportTest) ... ok
> test_expected_get (doublex.test3.test.report_tests.PropertyReportTests) ... ok
> test_expected_set (doublex.test3.test.report_tests.PropertyReportTests) ... ok
> test_unexpected_get (doublex.test3.test.report_tests.PropertyReportTests) ...
> ok
> test_unexpected_set (doublex.test3.test.report_tests.PropertyReportTests) ...
> ok
> test__hamcre
Bug#973059: marked as done (logging-tree: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Sun, 28 Nov 2021 22:22:57 +
with message-id
and subject line Bug#1000546: Removed package(s) from unstable
has caused the Debian Bug report #973059,
regarding logging-tree: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.9 3.8" 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.)
--
973059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: logging-tree
Version: 1.8.1-0.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> pybuild --configure -i python{version} -p "3.9 3.8"
> I: pybuild base:217: python3.9 setup.py config
> running config
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> pybuild --build -i python{version} -p "3.9 3.8"
> I: pybuild base:217: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> copying logging_tree/__init__.py ->
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> copying logging_tree/nodes.py ->
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> copying logging_tree/format.py ->
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> creating
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/case.py ->
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_format.py ->
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_node.py ->
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> copying logging_tree/__init__.py ->
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> copying logging_tree/nodes.py ->
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> copying logging_tree/format.py ->
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> creating
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/case.py ->
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_format.py ->
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_node.py ->
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
>dh_auto_test -O--buildsystem=pybuild
> pybuild --test -i python{version} -p "3.9 3.8"
> I: pybuild base:217: cd
> /<>/.pybuild/cpython3_3.9_logging_tree/build; python3.9 -m
> unittest discover -v
> test_2_dot_5_handlers (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_2_dot_6_handlers (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_fancy_tree (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_formatter_that_is_not_a_Formatter_instance
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_formatter_with_no_fmt_attributes
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_handler_with_parent_attribute_that_is_none
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_handler_with_wrong_parent_attribute
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_most_handlers (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_nested_handlers (logging_tree.tests.test_format.FormatTests) ... ok
> test_printout (logging_tree.tests.test_format.FormatTests) ... ok
> test_simple_tree (logging_tree.tests.test_format.FormatTests) ... ok
> test_default_tree (logging_tree.tests.test_node.NodeTests) ... ok
> test_one_level_tree (logging_tree.tests.test_node.NodeTests) ... ok
> test_two_level_tree (logging_tree.tests.test_node.NodeTests) ... ok
> test_two_level_tree_with_placeholder (
Bug#973086: marked as done (celery-haystack: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Sun, 28 Nov 2021 22:14:19 +
with message-id
and subject line Bug#1000542: Removed package(s) from unstable
has caused the Debian Bug report #973086,
regarding celery-haystack: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.9 3.8" 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.)
--
973086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: celery-haystack
Version: 0.10-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. HAYSTACK=v2 python3
> /usr/bin/django-admin test --settings=celery_haystack.test_settings"
> dh_auto_test
> I: pybuild base:217: PYTHONPATH=. HAYSTACK=v2 python3 /usr/bin/django-admin
> test --settings=celery_haystack.test_settings
> Creating test database for alias 'default'...
> EEE
> ==
> ERROR: test_complex (celery_haystack.tests.tests.QueuedSearchIndexTestCase)
> --
> Traceback (most recent call last):
> File "/<>/celery_haystack/utils.py", line 17, in
> get_update_task
> mod = import_module(module)
> File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1014, in _gcd_import
> File "", line 991, in _find_and_load
> File "", line 975, in _find_and_load_unlocked
> File "", line 671, in _load_unlocked
> File "", line 783, in exec_module
> File "", line 219, in _call_with_frames_removed
> File "/<>/celery_haystack/tasks.py", line 11, in
> from celery.task import Task # noqa
> ModuleNotFoundError: No module named 'celery.task'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/<>/celery_haystack/tests/tests.py", line 58, in
> test_complex
> note1 = Note.objects.create(content='Because everyone loves test.')
> File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82,
> in manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 422,
> in create
> obj.save(force_insert=True, using=self.db)
> File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743,
> in save
> self.save_base(using=using, force_insert=force_insert,
> File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 791,
> in save_base
> post_save.send(
> File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line
> 173, in send
> return [
> File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line
> 174, in
> (receiver, receiver(signal=self, sender=sender, **named))
> File "/<>/celery_haystack/signals.py", line 21, in enqueue_save
> return self.enqueue('update', instance, sender, **kwargs)
> File "/<>/celery_haystack/signals.py", line 44, in enqueue
> enqueue_task(action, instance)
> File "/<>/celery_haystack/utils.py", line 41, in enqueue_task
> task = get_update_task()
> File "/<>/celery_haystack/utils.py", line 19, in
> get_update_task
> raise ImproperlyConfigured('Error importing module %s: "%s"' %
> django.core.exceptions.ImproperlyConfigured: Error importing module
> celery_haystack.tasks: "No module named 'celery.task'"
>
> ==
> ERROR: test_delete (celery_haystack.tests.tests.QueuedSearchIndexTestCase)
> --
> Traceback (most recent call last):
> File "/<>/celery_haystack/utils.py", line 17, in
> get_update_task
> mod = import_module(module)
> File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1014, in _gcd_import
> File "", line 991, in _find_and_load
> File "", line 975, in _find_and_load_unlocked
> File "", line 671, in _load_unlocked
> File "", line 783, in exec_module
> File "", line 219, in _call_with_frames_removed
> File "/<>/celery_haystack/tasks.py", line 11, in
> from ce
Bug#972910: marked as done (lasagne ftbfs with python3.9)
Your message dated Sun, 28 Nov 2021 22:15:25 + with message-id and subject line Bug#1000544: Removed package(s) from unstable has caused the Debian Bug report #972910, regarding lasagne ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lasagne Version: 0.1+git20200419.5d3c63c+ds-1 Severity: serious Tags: sid bullseye ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.9 lasagne ftbfs with python3.9; to reproduce, you can use the repositories found at: deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./ deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./ see https://people.debian.org/~ginggs/python3.9-default/lasagne_0.1+git20200419.5d3c63c+ds-1build1_amd64-2020-10-24T09:30:12Z.build [...] ERRORS _ ERROR at setup of TestGetOutput_MergeLayer.test_get_output_without_arguments _ self = @pytest.fixture def layers(self): from lasagne.layers.base import Layer, MergeLayer from lasagne.layers.input import InputLayer # create two mocks of the same attributes as an InputLayer instance l1 = [Mock(InputLayer((None,)), output_shape=(None,), get_output_kwargs=[]), Mock(InputLayer((None,)), output_shape=(None,), get_output_kwargs=[])] # create two mocks of the same attributes as a Layer instance l2 = [Mock(Layer(l1[0]), output_shape=(None,), get_output_kwargs=[]), Mock(Layer(l1[1]), output_shape=(None,), get_output_kwargs=[])] # link them to the InputLayer mocks l2[0].input_layer = l1[0] l2[1].input_layer = l1[1] # create a mock that has the same attributes as a MergeLayer > l3 = Mock(MergeLayer(l2), get_output_kwargs=['kwarg']) lasagne/tests/layers/test_helper.py:306: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3/dist-packages/mock/mock.py:1082: in __init__ _safe_super(CallableMixin, self).__init__( /usr/lib/python3/dist-packages/mock/mock.py:439: in __init__ self._mock_add_spec(spec, spec_set, _spec_as_instance, _eat_self) /usr/lib/python3/dist-packages/mock/mock.py:494: in _mock_add_spec if iscoroutinefunction(getattr(spec, attr, None)): lasagne/layers/base.py:269: in output_shape shape = self.get_output_shape_for(self.input_shapes) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = input_shapes = [(None,), (None,)] def get_output_shape_for(self, input_shapes): """ Computes the output shape of this layer, given a list of input shapes. Parameters -- input_shape : list of tuple A list of tuples, with each tuple representing the shape of one of the inputs (in the correct order). These tuples should have as many elements as there are input dimensions, and the elements should be integers or `None`. Returns --- tuple A tuple representing the shape of the output of this layer. The tuple has as many elements as there are output dimensions, and the elements are all either integers or `None`. Notes - This method must be overridden when implementing a new :class:`Layer` class with multiple inputs. By default it raises `NotImplementedError`. """ > raise NotImplementedError E NotImplementedError --- End Message --- --- Begin Message --- Version: 0.1+git20200419.5d3c63c+ds-1+rm Dear submitter, as the package lasagne 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/1000544 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance
Bug#962938: marked as done (lasagne: autopkgtest fails with newer python-mock)
Your message dated Sun, 28 Nov 2021 22:15:25 + with message-id and subject line Bug#1000544: Removed package(s) from unstable has caused the Debian Bug report #962938, regarding lasagne: autopkgtest fails with newer python-mock 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.) -- 962938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lasagne Version: 0.1+git20200419.5d3c63c+ds-1 Severity: serious lasagne's autopkgtest fails with newer python-mock 4.0.2-1. Fails are in layers/test_helper.py, see: https://ci.debian.net/data/autopkgtest/testing/amd64/l/lasagne/5909523/log.gz Thanks for fixing. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 0.1+git20200419.5d3c63c+ds-1+rm Dear submitter, as the package lasagne 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/1000544 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#972023: marked as done (python-enable ftbfs with python3.9 as supported python3 version)
Your message dated Sun, 28 Nov 2021 22:14:56 +
with message-id
and subject line Bug#1000543: Removed package(s) from unstable
has caused the Debian Bug report #951888,
regarding python-enable ftbfs with python3.9 as supported python3 version
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
951888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-enable
Version: 4.8.1-1
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
[...]
test_vertical_mouse_wheel_without_pixel_delta
(enable.tests.qt4.mouse_wheel_test_case.MouseWheelTestCase) ... ok
test_minimum_vertical (enable.tests.qt4.scrollbar_test.ScrollBarTest) ...
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.9_enable/build/enable/qt4/base_window.py",
line 213, in paintEvent
self.handler.paintEvent(event)
File
"/<>/.pybuild/cpython3_3.9_enable/build/enable/qt4/base_window.py",
line 65, in paintEvent
self._enable_window._paint(event)
File
"/<>/.pybuild/cpython3_3.9_enable/build/enable/abstract_window.py",
line 462, in _paint
self._gc = self._create_gc(size)
File
"/<>/.pybuild/cpython3_3.9_enable/build/enable/qt4/image.py", line
20, in _create_gc
gc = GraphicsContext((size[0]+1, size[1]+1), pix_format=pix_format,
File
"/<>/.pybuild/cpython3_3.9_enable/build/kiva/agg/__init__.py", line
38, in __init__
GraphicsContextArray.__init__(self, pixel_map.bmp_array,
File "/<>/.pybuild/cpython3_3.9_enable/build/kiva/agg/agg.py",
line 859, in __init__
_swig_setattr(self, GraphicsContextArray, 'this', obj)
NameError: name '_swig_setattr' is not defined
Aborted (core dumped)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=134: cd
/<>/.pybuild/cpython3_3.9_enable/build; python3.9 -m nose -v
dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8"
returned exit code 13
--- End Message ---
--- Begin Message ---
Version: 4.8.1-1+rm
Dear submitter,
as the package python-enable 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/1000543
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#951888: marked as done (python-enable FTBFS with swig 4.0.1)
Your message dated Sun, 28 Nov 2021 22:14:56 +
with message-id
and subject line Bug#1000543: Removed package(s) from unstable
has caused the Debian Bug report #951888,
regarding python-enable FTBFS with swig 4.0.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.)
--
951888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-enable
Version: 4.8.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-enable.html
...
test_minimum_vertical (enable.tests.qt4.scrollbar_test.ScrollBarTest) ...
Traceback (most recent call last):
File
"/build/1st/python-enable-4.8.1/.pybuild/cpython3_3.8_enable/build/enable/qt4/base_window.py",
line 213, in paintEvent
self.handler.paintEvent(event)
File
"/build/1st/python-enable-4.8.1/.pybuild/cpython3_3.8_enable/build/enable/qt4/base_window.py",
line 65, in paintEvent
self._enable_window._paint(event)
File
"/build/1st/python-enable-4.8.1/.pybuild/cpython3_3.8_enable/build/enable/abstract_window.py",
line 462, in _paint
self._gc = self._create_gc(size)
File
"/build/1st/python-enable-4.8.1/.pybuild/cpython3_3.8_enable/build/enable/qt4/image.py",
line 20, in _create_gc
gc = GraphicsContext((size[0]+1, size[1]+1), pix_format=pix_format,
File
"/build/1st/python-enable-4.8.1/.pybuild/cpython3_3.8_enable/build/kiva/agg/__init__.py",
line 38, in __init__
GraphicsContextArray.__init__(self, pixel_map.bmp_array,
File
"/build/1st/python-enable-4.8.1/.pybuild/cpython3_3.8_enable/build/kiva/agg/agg.py",
line 859, in __init__
_swig_setattr(self, GraphicsContextArray, 'this', obj)
NameError: name '_swig_setattr' is not defined
Aborted
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=134: cd
/build/1st/python-enable-4.8.1/.pybuild/cpython3_3.8_enable/build; python3.8 -m
nose -v
dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.8 3.7"
returned exit code 13
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Version: 4.8.1-1+rm
Dear submitter,
as the package python-enable 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/1000543
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#973124: marked as done (unison-2.48: FTBFS: ocamlc: OCaml has been configured with -force-safe-string: -unsafe-string is not available.)
Your message dated Sun, 28 Nov 2021 22:12:15 +
with message-id
and subject line Bug#1000520: Removed package(s) from unstable
has caused the Debian Bug report #973124,
regarding unison-2.48: FTBFS: ocamlc: OCaml has been configured with
-force-safe-string: -unsafe-string is not available.
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.)
--
973124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unison-2.48
Version: 2.48.4-8
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> ocamlc -o mkProjectInfo unix.cma str.cma mkProjectInfo.ml
> ./mkProjectInfo > Makefile.ProjectInfo
> UISTYLE = text
> Building for Unix
> NATIVE = false
> THREADS = false
> STATIC = false
> OSTYPE =
> OSARCH = Linux
> ocamlc: ubase/rx.mli ---> ubase/rx.cmi
> ocamlc -g -unsafe-string -I lwt -I ubase -I system -I fsmonitor -I
> fsmonitor/linux -I fsmonitor/windows -I system/generic -I lwt/generic -custom
> -g -c /<>/ubase/rx.mli
> ocamlc: OCaml has been configured with -force-safe-string: -unsafe-string is
> not available.
> Usage: ocamlc
> Options are:
> -a Build a library
> -alert Enable or disable alerts according to :
> + enable alert
> - disable alert
> ++ treat as fatal error
> -- treat as non-fatal
> @ enable and treat it as fatal error
> can be 'all' to refer to all alert names
> -absname Show absolute filenames in error messages
> -annot (deprecated) Save information in .annot
> -bin-annot Save typedtree in .cmt
> -c Compile only (do not link)
> -cc Use as the C compiler and linker
> -cclib Pass option to the C linker
> -ccopt Pass option to the C compiler and linker
> -color {auto|always|never} Enable or disable colors in compiler messages
> The following settings are supported:
> autouse heuristics to enable colors only if supported
> always enable colors
> never disable colors
> The default setting is 'auto', and the current heuristic
> checks that the TERM environment variable exists and is
> not empty or "dumb", and that isatty(stderr) holds.
> If the option is not specified, these setting can alternatively
> be set through the OCAML_COLOR environment variable.
> -error-style {contextual|short} Control the way error messages and
> warnings are printed
> The following settings are supported:
> short only print the error and its location
> contextual like "short", but also display the source code
> snippet corresponding to the location of the error
> The default setting is 'contextual'.
> If the option is not specified, these setting can alternatively
> be set through the OCAML_ERROR_STYLE environment variable.
> -compat-32 Check that generated bytecode can run on 32-bit platforms
> -config Print configuration values and exit
> -config-var Print the value of a configuration variable, a newline, and
> exit
> (print nothing and exit with error value if the variable does not exist)
> -custom Link in custom mode
> -dllib Use the dynamically-loaded library
> -dllpath Add to the run-time search path for shared libraries
> -dtypes (deprecated) same as -annot
> -for-pack Generate code that can later be `packed' with
> ocamlc -pack -o .cmo
> -g Save debugging information
> -stop-after {parsing|typing} Stop after the given compilation pass.
> -i Print inferred interface
> -I Add to the list of include directories
> -impl Compile as a .ml file
> -intf Compile as a .mli file
> -intf-suffix Suffix for interface files (default: .mli)
> -intf_suffix (deprecated) same as -intf-suffix
> -keep-docs Keep documentation strings in .cmi files
> -no-keep-docs Do not keep documentation strings in .cmi files (default)
> -keep-locs Keep locations in .cmi files (default)
> -no-keep-locs Do not keep locations in .cmi files
> -labels Use commuting label mode
> -linkall Link all modules, even unused ones
> -make-runtime Build a runtime system with given C objects and libraries
> -make_runtime (deprecated) same as -make-runtime
> -modern (deprecated) same as -labels
> -alias-deps Do record dependencies for module aliases
> -no-alias-deps Do not record dependencies for mo
Processed: Re: Processed (with 1 error): Re: ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1
Processing commands for cont...@bugs.debian.org: > forwarded 1000781 https://bugs.ghostscript.com/show_bug.cgi?id=704737 Bug #1000781 [ghostscript] ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 Set Bug forwarded-to-address to 'https://bugs.ghostscript.com/show_bug.cgi?id=704737'. > merge 1000781 1000710 Bug #1000781 [ghostscript] ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 Bug #1000781 [ghostscript] ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 Marked as found in versions ghostscript/9.55.0~dfsg-1. Bug #1000710 [ghostscript] ghostscript: Fails to convert EPS file using -sDEVICE=pngalpha Added tag(s) sid and bookworm. Merged 1000710 1000781 > stop Stopping processing here. Please contact me if you need assistance. -- 1000710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000710 1000781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942064: marked as done (profphd: autopkgtest failure)
Your message dated Sun, 28 Nov 2021 22:05:35 + with message-id and subject line Bug#1000470: Removed package(s) from unstable has caused the Debian Bug report #942064, regarding profphd: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: profphd Version: 1.0.42-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 profphd fails its autopkgtests: autopkgtest [01:06:02]: test installation-test: [--- Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/prof.pl line 15. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Assigning non-zero to $[ is no longer possible at /usr/share/profphd/prof/prof.pl line 139. autopkgtest [01:06:03]: test installation-test: ---] from: https://ci.debian.net/data/autopkgtest/testing/amd64/p/profphd/3106658/log.gz This is with perl 5.30, older tests passed with autopkgtest [11:24:16]: test profphd-install-test: [--- Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/prof.pl line 15. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/embl/phd.pl line 16. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/prof.pl line 15. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/embl/phd.pl line 16. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/prof.pl line 15. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/embl/phd.pl line 16. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/prof.pl line 15. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/embl/phd.pl line 16. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/prof.pl line 15. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/embl/phd.pl line 16. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Can't exec "pp_popcon_cnt": No such file or directory at /usr/share/profphd/prof/prof.pl line 15. The Rost Lab recommends you install the pp-popularity-contest package that provides pp_popcon_cnt: sudo apt-get install pp-popularity-contest Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536. Redundant argument in printf at /usr/share/perl5/RG/Uti
Processed (with 2 errors): Re: Processed (with 1 error): Re: ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1
Processing commands for cont...@bugs.debian.org: > fowarded 1000781 https://bugs.ghostscript.com/show_bug.cgi?id=704737 Unknown command or malformed arguments to command. > merge 1000781 1000710 Bug #1000781 [ghostscript] ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 Unable to merge bugs because: forwarded of #1000710 is 'https://bugs.ghostscript.com/show_bug.cgi?id=704737' not '' Failed to merge 1000781: Did not alter merged bugs. > stop Stopping processing here. Please contact me if you need assistance. -- 1000710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000710 1000781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996223: marked as done (ruby-factory-girl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Sun, 28 Nov 2021 22:00:59 + with message-id and subject line Bug#1000346: Removed package(s) from unstable has caused the Debian Bug report #996223, regarding ruby-factory-girl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: 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.) -- 996223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-factory-girl Version: 4.7.0-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-factory-girl was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: >no receiver given > # ./lib/factory_girl/attribute/dynamic.rb:16:in `instance_exec' > # ./lib/factory_girl/attribute/dynamic.rb:16:in `block in to_proc' > # ./lib/factory_girl/evaluator.rb:75:in `instance_exec' > # ./lib/factory_girl/evaluator.rb:75:in `block in define_attribute' > # ./lib/factory_girl/attribute_assigner.rb:56:in `get' > # ./lib/factory_girl/attribute_assigner.rb:16:in `block (2 levels) in > object' > # ./lib/factory_girl/attribute_assigner.rb:15:in `each' > # ./lib/factory_girl/attribute_assigner.rb:15:in `block in object' > # :90:in `tap' > # ./lib/factory_girl/attribute_assigner.rb:14:in `object' > # ./lib/factory_girl/evaluation.rb:12:in `object' > # ./lib/factory_girl/strategy/build.rb:9:in `result' > # ./lib/factory_girl/factory.rb:42:in `run' > # ./lib/factory_girl/factory_runner.rb:29:in `block in run' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/notifications.rb:182:in > `instrument' > # ./lib/factory_girl/factory_runner.rb:28:in `run' > # ./lib/factory_girl/strategy_syntax_method_registrar.rb:20:in `block in > define_singular_strategy_method' > # ./spec/acceptance/definition_spec.rb:42:in `block (2 levels) in (required)>' > > Finished in 8.59 seconds (files took 1.14 seconds to load) > 537 examples, 3 failures > > Failed examples: > > rspec ./spec/acceptance/callbacks_spec.rb:68 # callbacks using Symbol#to_proc > runs the callback correctly > rspec ./spec/acceptance/definition_spec.rb:34 # attributes defined using > Symbol#to_proc assigns values correctly > rspec ./spec/acceptance/definition_spec.rb:41 # attributes defined using > Symbol#to_proc assigns value with override correctly > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-factory-girl/ruby-factory-girl_4.7.0-2.1+rebuild1633379420_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 4.7.0-2.1+rm Dear submitter, as the package ruby-factory-girl 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/1000346 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed (with 1 error): Re: ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1
Processing control commands: > reassign -1 ghostscript Bug #1000781 [src:ghostscript, src:asymptote] ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 Bug reassigned from package 'src:ghostscript, src:asymptote' to 'ghostscript'. No longer marked as found in versions ghostscript/9.55.0~dfsg-1 and asymptote/2.70+ds-2. Ignoring request to alter fixed versions of bug #1000781 to the same values previously set > severity 1000710 serious Bug #1000710 [ghostscript] ghostscript: Fails to convert EPS file using -sDEVICE=pngalpha Severity set to 'serious' from 'important' > merge 1000710 -1 Bug #1000710 [ghostscript] ghostscript: Fails to convert EPS file using -sDEVICE=pngalpha Unable to merge bugs because: forwarded of #1000781 is '' not 'https://bugs.ghostscript.com/show_bug.cgi?id=704737' Failed to merge 1000710: Did not alter merged bugs. -- 1000710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000710 1000781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000781: ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1
Control: reassign -1 ghostscript Control: severity 1000710 serious Control: merge 1000710 -1 Am 28.11.2021 um 21:29 teilte Paul Gevers mit: Hi Paul, Dear maintainer(s), With a recent upload of ghostscript the autopkgtest of asymptote fails in testing when that autopkgtest is run with the binary packages of ghostscript from unstable. It passes when run with only packages from testing. In tabular form: We are already on it and I forwarded the issue to upstream: https://bugs.ghostscript.com/show_bug.cgi?id=704737 Last statement we got from there was: "This appear to be fixed already, I will narrow down the relevant commit tomorrow." So chances are good to have a fix soon. Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#1000221: marked as done (ginkgocadx: error: ‘OFIterator’ was not declared in this scope; did you mean ‘OF_error’?)
Your message dated Sun, 28 Nov 2021 21:58:31 +
with message-id
and subject line Bug#1000320: Removed package(s) from unstable
has caused the Debian Bug report #1000221,
regarding ginkgocadx: error: ‘OFIterator’ was not declared in this scope; did
you mean ‘OF_error’?
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.)
--
1000221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ginkgocadx
Version: 3.8.8-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
| cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++ -DAPIEXPORT
-DCURL_STATICLIB -DDCMTK_POST_20170228 -DGINKGO_ARCH_x86_64
-DGINKGO_CODENAME=\"\" -DGINKGO_VERSION=\"3.8.8\" -DHAVE_CONFIG_H
-DINTERNET_DIST -DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC
-DUSE_SYSTEM_SQLITE -DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64
-D__WXGTK__ -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)"
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)"
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)"
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)"
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)"
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKFactoryRegistration
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/libmount -I/usr/include/blkid
-I/<>/cadxcore/CADxCore -I/<>/cadxcore
-I/<>/cadxcore/vtk -I/<>/cadxcore/itk
-I/<>/cadxcore/wx -I/<>/cadxcore/wx/VTK
-I/<>/cadxcore/VTKInria3D
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0
-I/usr/include/vtk-6.3 -I/usr/lib/x86_64-linux-gnu/openmpi/include
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/include/hdf5/openmpi
-I/usr/include/libxml2 -isystem /usr/include/gdcm-3.0 -isystem
/usr/include/ITK-4.13 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC -MD -MT
cadxcore/CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomstoreassociation.cpp.o
-MF
CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomstoreassociation.cpp.o.d -o
CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomstoreassociation.cpp.o -c
/<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp
| /<>/cadxcore/main/controllers/dcmtk/dicomprintassociation.cpp:
In function ‘void DIMSE_printNStatusString(std::ostream&, int)’:
|
/<>/cadxcore/main/controllers/dcmtk/dicomprintassociation.cpp:160:14:
error: ‘STATUS_N_PRINT_BSB_Fail_PrintQueueFull’ was not declared in this
scope; did you mean ‘STATUS_N_PRINT_BFB_Fail_PrintQueueFull’?
| 160 | case STATUS_N_PRINT_BSB_Fail_PrintQueueFull:
| | ^~
| | STATUS_N_PRINT_BFB_Fail_PrintQueueFull
| make[3]: *** [cadxcore/CMakeFiles/CADxCore.dir/build.make:3873:
cadxcore/CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomprintassociation.cpp.o]
Error 1
| make[3]: *** Waiting for unfinished jobs
| /<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp:
In member function ‘void
GIL::DICOM::DicomStoreAssociation::Store(GIL::DICOM::DicomStoreAssociation::ListaRutas,
const GNC::GCS::Ptr&, std::string,
GNC::IProxyNotificadorProgreso*, GIL::DICOM::TipoTransferSyntaxEnvio)’:
|
/<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp:1047:38:
error: ‘OFIterator’ was not declared in this scope; did you mean ‘OF_error’?
| 1047 | for (OFIterator itsc
=sopClassUIDList.begin(); itsc != sopClassUIDList.end(); ++itsc) {
| | ^~
| | OF_error
|
/<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp:1047:57:
error: expected primary-expression before ‘>’ token
| 1047 | for (OFIt
Bug#964404: marked as done (quagga is replaced by frr)
Your message dated Sun, 28 Nov 2021 21:54:36 + with message-id and subject line Bug#1000216: Removed package(s) from unstable has caused the Debian Bug report #964404, regarding quagga is replaced by frr 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.) -- 964404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: quagga Version: 1.2.4-4 Severity: serious The maintained fork from quagga that continues the zebra codebase is frr, which is already in buster: https://tracker.debian.org/pkg/frr Additionally shipping quagga in bullseye might bring more confusion than benefits. --- End Message --- --- Begin Message --- Version: 1.2.4-4+rm Dear submitter, as the package quagga 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/1000216 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#957737: marked as done (quagga: ftbfs with GCC-10)
Your message dated Sun, 28 Nov 2021 21:54:36 + with message-id and subject line Bug#1000216: Removed package(s) from unstable has caused the Debian Bug report #957737, regarding quagga: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:quagga Version: 1.2.4-4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/quagga_1.2.4-4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] libtool: compile: gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c smux.c -o smux.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o agentx.lo agentx.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o snmp.lo snmp.c libtool: compile: gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c agentx.c -fPIC -DPIC -o .libs/agentx.o /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o md5.lo md5.c libtool: compile: gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c snmp.c -fPIC -DPIC -o .libs/snmp.o libtool: compile: gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c md5.c -fPIC -DPIC -o .libs/md5.o libtool: compile: gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c agentx.c -o agentx.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c snmp.c -o snmp.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o if_rmap.lo if_rmap.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -I. -I.. -I.. -I.. -I../lib -I../lib -Wdate-time -D_FORT
Bug#947878: marked as done (gnome-mime-data: unmaintained upstream for over a decade)
Your message dated Sun, 28 Nov 2021 21:56:01 + with message-id and subject line Bug#1000259: Removed package(s) from unstable has caused the Debian Bug report #947878, regarding gnome-mime-data: unmaintained upstream for over a decade 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.) -- 947878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-mime-data Version: 2.18.0-2 Severity: important Tags: upstream wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs unmaintained-upstream gnome-mime-data gnome-mime-data was most recently released in 2007. From its contents it appears to be related to gnome-vfs, which was removed from Debian last year. Modern versions of GNOME (and all other major desktop environments) use the freedesktop.org shared-mime-info package for MIME type information. Only one package depends on gnome-mime-data, namely chemical-mime-data. smcv --- End Message --- --- Begin Message --- Version: 2.18.0-2.1+rm Dear submitter, as the package gnome-mime-data 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/1000259 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#998529: marked as done (rust-cargo: FTBFS: unsatisfiable build-dependencies: librust-cargo-util-0.1+default-dev (>= 0.1.1-~~), librust-im-rc-15+default-dev)
Your message dated Sun, 28 Nov 2021 21:49:12 + with message-id and subject line re: rust-cargo: FTBFS: unsatisfiable build-dependencies: librust-cargo-util-0.1+default-dev (>= 0.1.1-~~), librust-im-rc-15+default-dev has caused the Debian Bug report #998529, regarding rust-cargo: FTBFS: unsatisfiable build-dependencies: librust-cargo-util-0.1+default-dev (>= 0.1.1-~~), librust-im-rc-15+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-cargo Version: 0.57.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 24), cargo, rustc, > libstd-rust-dev, librust-anyhow-1+default-dev, librust-atty-0.2+default-dev, > librust-bytesize-1+default-dev, librust-cargo-platform-0.1+default-dev (>= > 0.1.2-~~), librust-cargo-util-0.1+default-dev (>= 0.1.1-~~), > librust-clap-2+default-dev (>= 2.31.2-~~), > librust-crates-io-0.33+default-dev, librust-crossbeam-utils-0.8+default-dev, > librust-curl-0.4+default-dev (>= 0.4.38-~~), librust-curl-0.4+http2-dev (>= > 0.4.38-~~), librust-curl-sys-0.4+default-dev (>= 0.4.48-~~), > librust-env-logger-0.9+default-dev, librust-filetime-0.2+default-dev (>= > 0.2.9-~~), librust-flate2-1+zlib-dev (>= 1.0.3-~~), > librust-fwdansi-1+default-dev (>= 1.1.0-~~), librust-git2-0.13+default-dev > (>= 0.13.16-~~), librust-git2-curl-0.14+default-dev (>= 0.14.1-~~), > librust-glob-0.3+default-dev, librust-hex-0.4+default-dev, > librust-home-0.5+default-dev, librust-humantime-2+default-dev, > librust-ignore-0.4+default-dev (>= 0.4.7-~~), librust-im-rc-15+default-dev, > librust-itertools-0.10+default-dev, librust-jobserver-0.1+default-dev (>= > 0.1.24-~~), librust-lazy-static-1+default-dev (>= 1.2.0-~~), > librust-lazycell-1+default-dev (>= 1.2.0-~~), librust-libc-0.2+default-dev, > librust-libgit2-sys-0.12+default-dev (>= 0.12.18-~~), > librust-log-0.4+default-dev (>= 0.4.6-~~), librust-memchr-2+default-dev (>= > 2.1.3-~~), librust-num-cpus-1+default-dev, librust-opener-0.5+default-dev, > librust-percent-encoding-2+default-dev, > librust-rustc-workspace-hack-1+default-dev, librust-rustfix-0.6+default-dev, > librust-semver-1+default-dev (>= 1.0.3-~~), librust-semver-1+serde-dev (>= > 1.0.3-~~), librust-serde-1+default-dev (>= 1.0.123-~~), > librust-serde-1+derive-dev (>= 1.0.123-~~), > librust-serde-ignored-0.1+default-dev, librust-serde-json-1+default-dev (>= > 1.0.30-~~), librust-serde-json-1+raw-value-dev (>= 1.0.30-~~), > librust-shell-escape-0.1+default-dev (>= 0.1.4-~~), > librust-strip-ansi-escapes-0.1+default-dev, librust-tar-0.4-dev (>= > 0.4.35-~~), librust-tempfile-3+default-dev, librust-termcolor-1+default-dev > (>= 1.1-~~), librust-toml-0.5+default-dev (>= 0.5.7-~~), > librust-unicode-width-0.1+default-dev (>= 0.1.5-~~), > librust-unicode-xid-0.2+default-dev, librust-url-2+default-dev (>= 2.2.2-~~), > librust-walkdir-2+default-dev (>= 2.2-~~), librust-winapi-0.3+basetsd-dev, > librust-winapi-0.3+default-dev, librust-winapi-0.3+handleapi-dev, > librust-winapi-0.3+jobapi-dev, librust-winapi-0.3+jobapi2-dev, > librust-winapi-0.3+memoryapi-dev, librust-winapi-0.3+minwindef-dev, > librust-winapi-0.3+ntdef-dev, librust-winapi-0.3+ntstatus-dev, > librust-winapi-0.3+processenv-dev, librust-winapi-0.3+processthreadsapi-dev, > librust-winapi-0.3+psapi-dev, librust-winapi-0.3+synchapi-dev, > librust-winapi-0.3+winbase-dev, librust-winapi-0.3+wincon-dev, > librust-winapi-0.3+winerror-dev, librust-winapi-0.3+winnt-dev, > build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 24), cargo, rustc, > libstd-rust-dev, librust-anyhow-1+default-dev, librust-atty-0.2+default-dev, > librust-bytesize-1+default-dev, librust-cargo-platform-0.1+default-dev (>= > 0.1.2-~~), librust-cargo-util-0.1+default-dev (>= 0.1.1-~~), > librust-clap-2+default-dev (>= 2.31.2-~~), > librust-crates-io-0.33+default-dev, librust-crossbeam-utils-0.8+default-dev,
Processed: found 1000768 in 1.18.3-7, tagging 977340, tagging 978457, tagging 977385, tagging 977658 ...
Processing commands for cont...@bugs.debian.org:
> found 1000768 1.18.3-7
Bug #1000768 [src:krb5] krb5: FTBFS due to missing dependency on tex-gyre
Marked as found in versions krb5/1.18.3-7.
> tags 977340 + sid bookworm
Bug #977340 [spip] spip: Not compatible with php8.0
Added tag(s) bookworm and sid.
> tags 978457 + sid bookworm
Bug #978457 [phing] phing: Not compatible with php8.0
Added tag(s) sid and bookworm.
> tags 977385 + sid bookworm
Bug #977385 [php-seclib] php-seclib: Not compatible with php8.0
Added tag(s) bookworm and sid.
> tags 977658 + sid bookworm
Bug #977658 {Done: Bas Couwenberg } [src:mapserver]
mapserver: FTBFS with php8.0
Added tag(s) sid and bookworm.
> found 1000716 0.7.14-1
Bug #1000716 [src:ponyorm] ponyorm: FTBFS on Python 3.10
Marked as found in versions ponyorm/0.7.14-1.
> tags 1000716 + sid bookworm
Bug #1000716 [src:ponyorm] ponyorm: FTBFS on Python 3.10
Added tag(s) sid and bookworm.
> tags 1000773 + experimental
Bug #1000773 [src:ruby-gitlab-sidekiq-fetcher] ruby-gitlab-sidekiq-fetcher:
autopkgtest needs update for new version of ruby-sidekiq: Could not find
'sidekiq' (>= 5, < 6.1)
Added tag(s) experimental.
> tags 1000756 + experimental
Bug #1000756 [src:freedv] freedv: FTBFS: varicode.h: No such file or directory
Added tag(s) experimental.
> tags 997552 + experimental
Bug #997552 {Done: Shengjing Zhu }
[src:golang-github-prometheus-common] golang-github-prometheus-common: FTBFS:
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4
github.com/prometheus/common/config github.com/prometheus/common/expfmt
github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
github.com/prometheus/common/log github.com/prometheus/common/model
github.com/prometheus/common/promlog github.com/prometheus/common/promlog/flag
github.com/prometheus/common/route github.com/prometheus/common/server returned
exit code 1
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000716
1000756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000756
1000768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000768
1000773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000773
977340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977340
977385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977385
977658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977658
978457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978457
997552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000784: php8.1: does not trap errors from dtrace
Source: php8.1 Version: 8.1.0-1 Severity: serious Tags: patch Justification: policy 4.6 When dtrace fails, the build system continues anyway. Such behaviour is in violation with policy section 4.6 and thus justifies a release-critical bug report. The actual issue resides in build/php.m4 line 2391 and following: | $ac_bdir[$]ac_hdrobj: $abs_srcdir/$ac_provsrc | CFLAGS="\$(CFLAGS_CLEAN)" dtrace -h -C -s $ac_srcdir[$]ac_provsrc -o \$[]@.bak && \$(SED) -e 's,PHP_,DTRACE_,g' \$[]@.bak > \$[]@ The dtrace call is separated from the sed invocation using &&. While the combination of "false && true" results in a non-zero exit, this does not terminate the shell even with -e set. See the following example: $ sh -c "set -e; false && true; echo huh" huh $ As such, a dtrace failures is swallowed and this causes the policy violation. To fix this, one can invoke the two commands separately: | $ac_bdir[$]ac_hdrobj: $abs_srcdir/$ac_provsrc | CFLAGS="\$(CFLAGS_CLEAN)" dtrace -h -C -s $ac_srcdir[$]ac_provsrc -o \$[]@.bak | \$(SED) -e 's,PHP_,DTRACE_,g' \$[]@.bak > \$[]@ I'm attaching a patch for your convenience. Helmut --- php8.1-8.1.0.orig/build/php.m4 +++ php8.1-8.1.0/build/php.m4 @@ -2389,7 +2389,8 @@ $abs_srcdir/$ac_provsrc:; $ac_bdir[$]ac_hdrobj: $abs_srcdir/$ac_provsrc - CFLAGS="\$(CFLAGS_CLEAN)" dtrace -h -C -s $ac_srcdir[$]ac_provsrc -o \$[]@.bak && \$(SED) -e 's,PHP_,DTRACE_,g' \$[]@.bak > \$[]@ + CFLAGS="\$(CFLAGS_CLEAN)" dtrace -h -C -s $ac_srcdir[$]ac_provsrc -o \$[]@.bak + \$(SED) -e 's,PHP_,DTRACE_,g' \$[]@.bak > \$[]@ \$(PHP_DTRACE_OBJS): $ac_bdir[$]ac_hdrobj
Bug#1000783: finalcut: binary-any FTBFS
Source: finalcut Version: 0.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=finalcut&ver=0.8.0-1 ... debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' test -f final/font/xfonts-finalcut-newfont.alias && rm final/font/xfonts-finalcut-newfont.alias make[1]: *** [debian/rules:25: override_dh_auto_clean] Error 1
Bug#1000782: plink2: autopkgtest regression: Segmentation fault
Source: plink2
Version: 2.00~a3-211011+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of plink2 the autopkgtest of plink2 fails in
testing when that autopkgtest is run with the binary packages of plink2
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
plink2 from testing2.00~a3-211011+dfsg-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=plink2
https://ci.debian.net/data/autopkgtest/testing/amd64/p/plink2/17088127/log.gz
PLINK v2.00a3 SSE4.2 (11 Oct 2021)
www.cog-genomics.org/plink/2.0/
(C) 2005-2021 Shaun Purcell, Christopher Chang GNU General Public
License v3
Logging to tmp_data.log.
Options in effect:
--dummy 33 65537 0.1 dosage-freq=0.1
--out tmp_data
Start time: Sun Nov 28 11:11:17 2021
257840 MiB RAM detected; reserving 128920 MiB for main workspace.
Using up to 48 threads (change this with --threads).
--dummy: 65k variants written.
Dummy data (33 samples, 65537 SNPs) written to tmp_data.pgen +
tmp_data.pvar +
tmp_data.psam .
End time: Sun Nov 28 11:11:17 2021
/usr/bin/plink2: line 8: 1566 Segmentation fault "${cmd}" "$@"
autopkgtest [11:11:17]: test run-sample-analysis
OpenPGP_signature
Description: OpenPGP digital signature
Processed: ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1
Processing control commands: > found -1 ghostscript/9.55.0~dfsg-1 Bug #1000781 [src:ghostscript, src:asymptote] ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 Marked as found in versions ghostscript/9.55.0~dfsg-1. > found -1 asymptote/2.70+ds-2 Bug #1000781 [src:ghostscript, src:asymptote] ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 Marked as found in versions asymptote/2.70+ds-2. -- 1000781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000781: ghostscript breaks asymptote autopkgtest: build fails: GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1
Source: ghostscript, asymptote Control: found -1 ghostscript/9.55.0~dfsg-1 Control: found -1 asymptote/2.70+ds-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of ghostscript the autopkgtest of asymptote fails in testing when that autopkgtest is run with the binary packages of ghostscript from unstable. It passes when run with only packages from testing. In tabular form: passfail ghostscriptfrom testing9.55.0~dfsg-1 asymptote from testing2.70+ds-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ghostscript to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ghostscript https://ci.debian.net/data/autopkgtest/testing/amd64/a/asymptote/17088116/log.gz cd png && make all make[4]: Entering directory '/tmp/autopkgtest-lxc.9yct2tpe/downtmp/build.gii/src/doc/png' cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ axis3.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ bezier2.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ bezier.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ beziercurve.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ bigdiagonal.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ binarytreetest.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ Bode.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ brokenaxis.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ CAD1.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ CDlabel.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ colons.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ colors.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ cube.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ cylinderskeleton.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ datagraph.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ diagonal.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ diatom.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ dots.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ eetomumu.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ elliptic.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ errorbars.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ exp.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ filegraph.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ flow.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ flowchartdemo.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ GaussianSurface.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ generalaxis3.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ generalaxis.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ graphmarkers.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ grid3xyz.asy cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ hatch.asy Error: /rangecheck in --stroke-- Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1990 1 3 %oparray_pop 1989 1 3 %oparray_pop 1988 1 3 %oparray_pop --nostringval-- 1977 1 3 %oparray_pop 1833 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- fill (NULL) (gs_pattern1_instance_t) (pattern accumulator) 0 %pattern_paint_finish --nostringval-- Dictionary stack: --dict:767/1123(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- Current allocation mode is local Last OS error: No such file or directory Current file position is 2701 GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 _shipout(prefix,f,currentpatterns,format,wait,view,t); ^ ../base/plain_shipout.asy: 104.11: runtime: shipout failed make[4]: *** [Makefile:14: hatch.png] Error 1 make[4]: Leaving direct
Processed: eigen3 breaks pybind11 autopkgtest on ppc64el: inlining failed in call to ‘always_inline’
Processing control commands: > found -1 eigen3/3.4.0-1 Bug #1000780 [src:eigen3, src:pybind11] eigen3 breaks pybind11 autopkgtest on ppc64el: inlining failed in call to ‘always_inline’ Marked as found in versions eigen3/3.4.0-1. > found -1 pybind11/2.7.1-1 Bug #1000780 [src:eigen3, src:pybind11] eigen3 breaks pybind11 autopkgtest on ppc64el: inlining failed in call to ‘always_inline’ Marked as found in versions pybind11/2.7.1-1. -- 1000780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000780: eigen3 breaks pybind11 autopkgtest on ppc64el: inlining failed in call to ‘always_inline’
Source: eigen3, pybind11
Control: found -1 eigen3/3.4.0-1
Control: found -1 pybind11/2.7.1-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of eigen3 the autopkgtest of pybind11 fails in
testing when that autopkgtest is run with the binary packages of eigen3
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
eigen3 from testing3.4.0-1
pybind11 from testing2.7.1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of eigen3 to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=eigen3
https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/pybind11/17068686/log.gz
-- The CXX compiler identification is GNU 11.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Python: /usr/bin/python3.9 (found suitable exact version
"3.9.9") found components: Interpreter Development Development.Module
Development.Embed -- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- Found pybind11: /usr/include (found version "2.7.1" )
-- Setting tests build type to MinSizeRel as none was specified
-- Building tests with Eigen v3.4.0
-- Found Boost:
/usr/lib/powerpc64le-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake
(found suitable version "1.74.0", minimum required is "1.56") -- Found
pytest 6.2.5
-- Configuring done
-- Generating done
-- Build files have been written to:
/tmp/autopkgtest-lxc.xeav8k1t/downtmp/autopkgtest_tmp/tests-python3.9
[ 2%] Building CXX object
CMakeFiles/pybind11_tests.dir/pybind11_tests.cpp.o
[ 4%] Building CXX object CMakeFiles/pybind11_tests.dir/test_async.cpp.o
[ 6%] Building CXX object CMakeFiles/pybind11_tests.dir/test_buffers.cpp.o
[ 9%] Building CXX object
CMakeFiles/pybind11_tests.dir/test_builtin_casters.cpp.o
[ 11%] Building CXX object
CMakeFiles/pybind11_tests.dir/test_call_policies.cpp.o
[ 13%] Building CXX object
CMakeFiles/pybind11_tests.dir/test_callbacks.cpp.o
[ 16%] Building CXX object CMakeFiles/pybind11_tests.dir/test_chrono.cpp.o
[ 18%] Building CXX object CMakeFiles/pybind11_tests.dir/test_class.cpp.o
[ 20%] Building CXX object
CMakeFiles/pybind11_tests.dir/test_constants_and_functions.cpp.o
[ 23%] Building CXX object
CMakeFiles/pybind11_tests.dir/test_copy_move.cpp.o
[ 25%] Building CXX object
CMakeFiles/pybind11_tests.dir/test_custom_type_casters.cpp.o
[ 27%] Building CXX object
CMakeFiles/pybind11_tests.dir/test_docstring_options.cpp.o
[ 30%] Building CXX object CMakeFiles/pybind11_tests.dir/test_eigen.cpp.o
In file included from /usr/include/eigen3/Eigen/Core:286,
from /usr/include/pybind11/eigen.h:36,
from
/tmp/autopkgtest-lxc.xeav8k1t/downtmp/autopkgtest_tmp/tests-python3.9/test_eigen.cpp:12:
/usr/include/eigen3/Eigen/src/Core/arch/AltiVec/MatrixProductMMA.h: In
function
‘Eigen::internal::storeAccumulatorlong, 0, 0, 1>, long, double __vector(2), 2l>(long, long,
Eigen::internal::blas_data_mapper const&, double
__vector(2) const&, __vector_quad*)void’:
/usr/include/eigen3/Eigen/src/Core/util/BlasUtil.h:227:46: error:
inlining failed in call to ‘always_inline’
‘Eigen::internal::blas_data_mapper1>::storePacketBlock(long, long,
Eigen::internal::PacketBlock const&) constvoid’:
target specific option mismatch
227 | EIGEN_DEVICE_FUNC EIGEN_ALWAYS_INLINE void
storePacketBlock(Index i, Index j, const PacketBlock
&block) const {
| ^~~~
In file included from
/usr/include/eigen3/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:38,
from /usr/include/eigen3/Eigen/Core:350,
from /usr/include/pybind11/eigen.h:36,
from
/tmp/autopkgtest-lxc.xeav8k1t/downtmp/autopkgtest_tmp/tests-python3.9/test_eigen.cpp:12:
/usr/include/eigen3/Eigen/src/Core/arch/AltiVec/MatrixProductMMA.h:43:44: note:
called from here
43 | data.template storePacketBlock(i, j, tRes);
| ~^~~~
In file included from /usr/include/eigen3/Eigen/Core:350,
from /usr/include/pybind11/eigen.h:36,
from
/tmp/autopkgtest-lxc.xeav8k1t/downtmp/autopkgtest_tmp/tests-python3.9/test_eigen.cpp:12:
/us
Bug#1000779: eigen3: autopkgtest regression on armhf: output to stderr
Source: eigen3 Version: 3.4.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of eigen3 the autopkgtest of eigen3 fails in testing when that autopkgtest is run with the binary packages of eigen3 from unstable on armhf. It passes when run with only packages from testing. In tabular form: passfail eigen3 from testing3.4.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The test itself passes, the autopkgtest fails on output to stderr. One can make an autopkgtest not fail on stderr by adding the "allow-stderr" restriction if that's appropriate. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=eigen3 https://ci.debian.net/data/autopkgtest/testing/armhf/e/eigen3/17091576/log.gz In file included from /usr/include/eigen3/Eigen/Core:330, from /usr/include/eigen3/Eigen/Dense:1, from demo.cpp:8: /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h: In member function ‘void Eigen::internal::lhs_process_one_packetLhsProgress, RhsProgress, LhsScalar, RhsScalar, ResScalar, AccPacket, LhsPacket, RhsPacket, ResPacket, GEBPTraits, LinearMapper, DataMapper>::operator()(const DataMapper&, const LhsScalar*, const RhsScalar*, ResScalar, Eigen::Index, Eigen::Index, Eigen::Index, Eigen::Index, Eigen::Index, Eigen::Index, int, Eigen::Index, Eigen::Index, Eigen::Index, Eigen::Index, Eigen::Index) [with int nr = 4; int LhsProgress = 1; int RhsProgress = 1; LhsScalar = double; RhsScalar = double; ResScalar = double; AccPacket = double; LhsPacket = double; RhsPacket = double; ResPacket = double; GEBPTraits = Eigen::internal::gebp_traits; LinearMapper = Eigen::internal::BlasLinearMapper; DataMapper = Eigen::internal::blas_data_mapper]’: /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1269:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1269 | peeled_kc_onestep(0, blA, blB, traits, &A0, &rhs_panel, &T0, &C0, &C1, &C2, &C3); | ~^~~ /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1270:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1270 | peeled_kc_onestep(1, blA, blB, traits, &A1, &rhs_panel, &T0, &D0, &D1, &D2, &D3); | ~^~~ /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1271:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1271 | peeled_kc_onestep(2, blA, blB, traits, &A0, &rhs_panel, &T0, &C0, &C1, &C2, &C3); | ~^~~ /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1272:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1272 | peeled_kc_onestep(3, blA, blB, traits, &A1, &rhs_panel, &T0, &D0, &D1, &D2, &D3); | ~^~~ /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1274:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1274 | peeled_kc_onestep(4, blA, blB, traits, &A0, &rhs_panel, &T0, &C0, &C1, &C2, &C3); | ~^~~ /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1275:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1275 | peeled_kc_onestep(5, blA, blB, traits, &A1, &rhs_panel, &T0, &D0, &D1, &D2, &D3); | ~^~~ /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1276:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1276 | peeled_kc_onestep(6, blA, blB, traits, &A0, &rhs_panel, &T0, &C0, &C1, &C2, &C3); | ~^~~ /usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h:1277:28: note: parameter passing for argument of type ‘Eigen::internal::gebp_traits’ changed in GCC 7.1 1277 | peeled_k
Bug#1000777: numpy breaks python-xarray autopkgtest on i386: numerical deltas
Source: numpy, python-xarray
Control: found -1 numpy/1:1.21.4-2
Control: found -1 python-xarray/0.19.0-6
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of numpy the autopkgtest of python-xarray fails in
testing when that autopkgtest is run with the binary packages of numpy
from unstable on i386. It passes when run with only packages from
testing. In tabular form:
passfail
numpy from testing1:1.21.4-2
python-xarray from testing0.19.0-6
versioned deps [0] from testingfrom unstable
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of numpy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
numpy/1:1.21.4-2. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=numpy
https://ci.debian.net/data/autopkgtest/testing/i386/p/python-xarray/17095751/log.gz
=== FAILURES
===
___ test_interpolate_chunk_advanced[linear]
method = 'linear'
@requires_scipy
@requires_dask
@pytest.mark.parametrize("method", ["linear", "nearest"])
@pytest.mark.filterwarnings("ignore:Increasing number of chunks")
def test_interpolate_chunk_advanced(method):
"""Interpolate nd array with an nd indexer sharing coordinates."""
# Create original array
x = np.linspace(-1, 1, 5)
y = np.linspace(-1, 1, 7)
z = np.linspace(-1, 1, 11)
t = np.linspace(0, 1, 13)
q = np.linspace(0, 1, 17)
da = xr.DataArray(
data=np.sin(x[:, np.newaxis, np.newaxis, np.newaxis,
np.newaxis])
* np.cos(y[:, np.newaxis, np.newaxis, np.newaxis])
* np.exp(z[:, np.newaxis, np.newaxis])
* t[:, np.newaxis]
+ q,
dims=("x", "y", "z", "t", "q"),
coords={"x": x, "y": y, "z": z, "t": t, "q": q, "label":
"dummy_attr"},
)
# Create indexer into `da` with shared coordinate
("full-twist" Möbius strip)
theta = np.linspace(0, 2 * np.pi, 5)
w = np.linspace(-0.25, 0.25, 7)
r = xr.DataArray(
data=1 + w[:, np.newaxis] * np.cos(theta),
coords=[("w", w), ("theta", theta)],
)
x = r * np.cos(theta)
y = r * np.sin(theta)
z = xr.DataArray(
data=w[:, np.newaxis] * np.sin(theta),
coords=[("w", w), ("theta", theta)],
)
kwargs = {"fill_value": None}
expected = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs,
method=method)
da = da.chunk(2)
x = x.chunk(1)
z = z.chunk(3)
actual = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs,
method=method)
assert_identical(actual, expected)
E AssertionError: Left and right DataArray objects are not identical
E E Differing values:
E L
E array([[[ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00],
E [ 1.239764e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-5.560517e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00]],
E E [[ 3.603946e-01, 4.228946e-01, ...,
1.297895e+00, 1.360395e+00],
E [ 1.346533e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-5.109700e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 3.603946e-01, 4.228946e-01, ..., 1.297895e+00,
1.360395e+00]],
E E ...,
E E [[ 4.810764e-01, 5.435764e-01, ...,
1.418576e+00, 1.481076e+00],
E [ 1.878775e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-3.662163e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 4.810764e-01, 5.435764e-01, ..., 1.418576e+00,
1.481076e+00]],
E E [[ 5.112469e-01, 5.737469e-01, ...,
1.448747e+00, 1.511247e+00],
E [
Processed: numpy breaks python-xarray autopkgtest on i386: numerical deltas
Processing control commands: > found -1 numpy/1:1.21.4-2 Bug #1000777 [src:numpy, src:python-xarray] numpy breaks python-xarray autopkgtest on i386: numerical deltas Marked as found in versions numpy/1:1.21.4-2. > found -1 python-xarray/0.19.0-6 Bug #1000777 [src:numpy, src:python-xarray] numpy breaks python-xarray autopkgtest on i386: numerical deltas Marked as found in versions python-xarray/0.19.0-6. -- 1000777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: golang-github-go-openapi-errors breaks golang-github-go-openapi-runtime autopkgtest: not enough arguments in call to "github.com/go-openapi/errors"
Processing control commands: > found -1 golang-github-go-openapi-errors/0.20.1-1 Bug #1000776 [src:golang-github-go-openapi-errors, src:golang-github-go-openapi-runtime] golang-github-go-openapi-errors breaks golang-github-go-openapi-runtime autopkgtest: not enough arguments in call to "github.com/go-openapi/errors" Marked as found in versions golang-github-go-openapi-errors/0.20.1-1. > found -1 golang-github-go-openapi-runtime/0.15.0-1 Bug #1000776 [src:golang-github-go-openapi-errors, src:golang-github-go-openapi-runtime] golang-github-go-openapi-errors breaks golang-github-go-openapi-runtime autopkgtest: not enough arguments in call to "github.com/go-openapi/errors" Marked as found in versions golang-github-go-openapi-runtime/0.15.0-1. -- 1000776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000776: golang-github-go-openapi-errors breaks golang-github-go-openapi-runtime autopkgtest: not enough arguments in call to "github.com/go-openapi/errors"
Source: golang-github-go-openapi-errors, golang-github-go-openapi-runtime Control: found -1 golang-github-go-openapi-errors/0.20.1-1 Control: found -1 golang-github-go-openapi-runtime/0.15.0-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of golang-github-go-openapi-errors the autopkgtest of golang-github-go-openapi-runtime fails in testing when that autopkgtest is run with the binary packages of golang-github-go-openapi-errors from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-go-openapi-errors from testing0.20.1-1 golang-github-go-openapi-runtime from testing0.15.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of golang-github-go-openapi-errors to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=golang-github-go-openapi-errors https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-go-openapi-runtime/17090239/log.gz [info] Testing github.com/go-openapi/runtime... [info] Source code installed by binary package, overriding dh_auto_configure... dh build --buildsystem=golang --with=golang dh_update_autotools_config -O--buildsystem=golang dh_autoreconf -O--buildsystem=golang debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest-lxc.te2evu81/downtmp/autopkgtest_tmp' mkdir -p "obj-x86_64-linux-gnu" cp -a /usr/share/gocode/src "obj-x86_64-linux-gnu" make[1]: Leaving directory '/tmp/autopkgtest-lxc.te2evu81/downtmp/autopkgtest_tmp' dh_auto_build -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -trimpath -v -p 48 github.com/go-openapi/runtime github.com/go-openapi/runtime/client github.com/go-openapi/runtime/flagext github.com/go-openapi/runtime/internal/testing github.com/go-openapi/runtime/internal/testing/petstore github.com/go-openapi/runtime/internal/testing/simplepetstore github.com/go-openapi/runtime/logger github.com/go-openapi/runtime/middleware github.com/go-openapi/runtime/middleware/denco github.com/go-openapi/runtime/middleware/header github.com/go-openapi/runtime/middleware/untyped github.com/go-openapi/runtime/security github.com/go-openapi/runtime/yamlpc internal/goexperiment internal/race unicode/utf16 unicode internal/unsafeheader encoding unicode/utf8 runtime/internal/sys vendor/golang.org/x/crypto/cryptobyte/asn1 internal/itoa crypto/internal/subtle vendor/golang.org/x/crypto/internal/subtle crypto/subtle internal/cpu runtime/internal/atomic math/bits internal/nettrace container/list internal/abi sync/atomic runtime/internal/math internal/bytealg math runtime internal/reflectlite sync internal/testlog internal/singleflight internal/sysinfo github.com/josharian/intern math/rand runtime/cgo errors sort internal/oserror path vendor/golang.org/x/net/dns/dnsmessage io crypto/elliptic/internal/fiat strconv syscall crypto/internal/randutil hash bytes strings crypto/hmac hash/crc32 vendor/golang.org/x/crypto/hkdf crypto/rc4 crypto reflect vendor/golang.org/x/text/transform golang.org/x/text/transform net/http/internal/ascii net/http/internal/testcert bufio html regexp/syntax golang.org/x/text/width internal/syscall/execenv internal/syscall/unix time regexp context io/fs internal/poll golang.org/x/net/context os internal/fmtsort encoding/binary encoding/base64 crypto/md5 crypto/ed25519/internal/edwards25519/field crypto/sha512 crypto/cipher crypto/sha1 crypto/sha256 vendor/golang.org/x/crypto/poly1305 io/ioutil path/filepath fmt runtime/debug net encoding/pem vendor/golang.org/x/sys/cpu crypto/ed25519/internal/edwards25519 crypto/des vendor/golang.org/x/crypto/chacha20 crypto/aes vendor/golang.org/x/crypto/chacha20poly1305 encoding/hex log net/url encoding/xml net/http/internal mime/quotedprintable vendor/golang.org/x/crypto/curve25519 github.com/go-openapi/runtime/logger mime github.com/docker/go-units encoding/json vendor/golang.org/x/net/http2/hpack github.com/pmezard/go-difflib/difflib text/template/parse database/sql/driver compress/flate runtime/trace flag gopkg.in/mgo.v2/internal/json encoding/gob golang.org/x/text/unicode/norm vendor/golang.org/x/text/unicode/norm gopkg.in/yaml.v2 math/big gopkg.in/yaml.v3 github.com/go-openapi/runtime/flagext github.com/davecgh/go-spew/spew github.com/go-openapi/analysis/internal/debug golang.org/x/text/unicode/bidi vendor/golang.org/x/text/unicode/bidi github.com
Bug#1000775: golang-github-go-openapi-errors breaks prometheus-alertmanager autopkgtest: not enough arguments in call to "github.com/go-openapi/errors"
Source: golang-github-go-openapi-errors, prometheus-alertmanager Control: found -1 golang-github-go-openapi-errors/0.20.1-1 Control: found -1 prometheus-alertmanager/0.21.0+ds-4 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of golang-github-go-openapi-errors the autopkgtest of prometheus-alertmanager fails in testing when that autopkgtest is run with the binary packages of golang-github-go-openapi-errors from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-go-openapi-errors from testing0.20.1-1 prometheus-alertmanager from testing0.21.0+ds-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of golang-github-go-openapi-errors to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=golang-github-go-openapi-errors https://ci.debian.net/data/autopkgtest/testing/amd64/p/prometheus-alertmanager/17090240/log.gz [info] Testing github.com/prometheus/alertmanager... [info] Source code installed by binary package, overriding dh_auto_configure... dh build --buildsystem=golang --with=golang \ --builddirectory=/tmp/autopkgtest-lxc.g1act3hi/downtmp/autopkgtest_tmp/build dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=/tmp/autopkgtest-lxc.g1act3hi/downtmp/autopkgtest_tmp/build dh_autoreconf -O--buildsystem=golang -O--builddirectory=/tmp/autopkgtest-lxc.g1act3hi/downtmp/autopkgtest_tmp/build debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest-lxc.g1act3hi/downtmp/autopkgtest_tmp' mkdir -p "build" cp -a /usr/share/gocode/src "build" make[1]: Leaving directory '/tmp/autopkgtest-lxc.g1act3hi/downtmp/autopkgtest_tmp' debian/rules override_dh_auto_build make[1]: Entering directory '/tmp/autopkgtest-lxc.g1act3hi/downtmp/autopkgtest_tmp' dh_auto_build -- -ldflags " -X github.com/prometheus/common/version.Version=0.21.0+ds -X github.com/prometheus/common/version.Revision=0.21.0+ds-4 -X github.com/prometheus/common/version.Branch=debian/sid -X github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org -X github.com/prometheus/common/version.BuildDate=20210129-00:48:05 -X github.com/prometheus/common/version.GoVersion=go1.17.3" cd build && go install -trimpath -v -p 2 -ldflags " -X github.com/prometheus/common/version.Version=0.21.0+ds -X github.com/prometheus/common/version.Revision=0.21.0+ds-4 -X github.com/prometheus/common/version.Branch=debian/sid -X github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org -X github.com/prometheus/common/version.BuildDate=20210129-00:48:05 -X github.com/prometheus/common/version.GoVersion=go1.17.3" github.com/prometheus/alertmanager/api github.com/prometheus/alertmanager/api/metrics github.com/prometheus/alertmanager/api/v1 github.com/prometheus/alertmanager/api/v2 github.com/prometheus/alertmanager/api/v2/client github.com/prometheus/alertmanager/api/v2/client/alert github.com/prometheus/alertmanager/api/v2/client/alertgroup github.com/prometheus/alertmanager/api/v2/client/general github.com/prometheus/alertmanager/api/v2/client/receiver github.com/prometheus/alertmanager/api/v2/client/silence github.com/prometheus/alertmanager/api/v2/models github.com/prometheus/alertmanager/api/v2/restapi github.com/prometheus/alertmanager/api/v2/restapi/operations github.com/prometheus/alertmanager/api/v2/restapi/operations/alert github.com/prometheus/alertmanager/api/v2/restapi/operations/alertgroup github.com/prometheus/alertmanager/api/v2/restapi/operations/general github.com/prometheus/alertmanager/api/v2/restapi/operations/receiver github.com/prometheus/alertmanager/api/v2/restapi/operations/silence github.com/prometheus/alertmanager/cli github.com/prometheus/alertmanager/cli/config github.com/prometheus/alertmanager/cli/format github.com/prometheus/alertmanager/client github.com/prometheus/alertmanager/cluster github.com/prometheus/alertmanager/cluster/clusterpb github.com/prometheus/alertmanager/cmd/alertmanager github.com/prometheus/alertmanager/cmd/amtool github.com/prometheus/alertmanager/config github.com/prometheus/alertmanager/dispatch github.com/prometheus/alertmanager/inhibit github.com/prometheus/alertmanager/nflog github.com/prometheus/alertmanager/nflog/nflogpb github.com/prometheus/alertmanager/notify github.com/prometheus/
Processed: golang-github-go-openapi-errors breaks prometheus-alertmanager autopkgtest: not enough arguments in call to "github.com/go-openapi/errors"
Processing control commands: > found -1 golang-github-go-openapi-errors/0.20.1-1 Bug #1000775 [src:golang-github-go-openapi-errors, src:prometheus-alertmanager] golang-github-go-openapi-errors breaks prometheus-alertmanager autopkgtest: not enough arguments in call to "github.com/go-openapi/errors" Marked as found in versions golang-github-go-openapi-errors/0.20.1-1. > found -1 prometheus-alertmanager/0.21.0+ds-4 Bug #1000775 [src:golang-github-go-openapi-errors, src:prometheus-alertmanager] golang-github-go-openapi-errors breaks prometheus-alertmanager autopkgtest: not enough arguments in call to "github.com/go-openapi/errors" Marked as found in versions prometheus-alertmanager/0.21.0+ds-4. -- 1000775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000774: python3-matplotlib: Segfault on mips64el in draw
Package: python3-matplotlib Version: 3.5.0-2 Severity: serious Justification: FTBFS Affects: deap deap FTBFS on mips64el, in matplotlib, I'd assume this is a matploptlib regression on mips64el: Current thread 0x00fff7382010 (most recent call first): File "/usr/lib/python3/dist-packages/matplotlib/collections.py", line 422 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/collections.py", line 989 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/mpl_toolkits/mplot3d/art3d.py", line 532 in draw File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositin g_images File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line 3082 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/mpl_toolkits/mplot3d/axes3d.py", line 469 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositin g_images File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", line 436 in draw File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", line 540 in print_ png File "/usr/lib/python3/dist-packages/matplotlib/_api/deprecation.py", line 412 in wrapper File "/usr/lib/python3/dist-packages/matplotlib/backend_bases.py", line 1643 in wrapper File "/usr/lib/python3/dist-packages/matplotlib/backend_bases.py", line 2314 in print_figure File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 3012 in savefig File "/usr/lib/python3/dist-packages/matplotlib/sphinxext/plot_directive.py", line 647 in re nder_figures File "/usr/lib/python3/dist-packages/matplotlib/sphinxext/plot_directive.py", line 789 in ru n File "/usr/lib/python3/dist-packages/matplotlib/sphinxext/plot_directive.py", line 259 in ru n File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2147 in run_directive File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2097 in directive File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2355 in explicit_construct File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2343 in explicit_markup File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 451 in check_line File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 239 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 197 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 282 in nested_parse File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 394 in new_subsection File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 328 in section File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2770 in underline File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 451 in check_line File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 239 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 197 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 282 in nested_parse File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 394 in new_subsection File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 328 in section File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 3009 in text File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 451 in check_line File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 239 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 171 in run File "/usr/lib/python3/dist-packages/sphinx/parsers.py", line 101 in parse File "/usr/lib/python3/dist-packages/docutils/readers/__init__.py", line 78 in parse File "/usr/lib/python3/dist-packages/sphinx/io.py", line 109 in read File "/usr/lib/python3/dist-packages/docutils/core.py", line 217 in publish File "/usr/lib/python3/dist-packages/sphinx/io.py", line 189 in read_doc File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 476 in read_doc File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 436 in _read_serial File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 415 in read File "/usr/l
Processed: ruby-gitlab-sidekiq-fetcher: autopkgtest needs update for new version of ruby-sidekiq: Could not find 'sidekiq' (>= 5, < 6.1)
Processing control commands: > affects -1 src:ruby-sidekiq Bug #1000773 [src:ruby-gitlab-sidekiq-fetcher] ruby-gitlab-sidekiq-fetcher: autopkgtest needs update for new version of ruby-sidekiq: Could not find 'sidekiq' (>= 5, < 6.1) Added indication that 1000773 affects src:ruby-sidekiq -- 1000773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000773: ruby-gitlab-sidekiq-fetcher: autopkgtest needs update for new version of ruby-sidekiq: Could not find 'sidekiq' (>= 5, < 6.1)
Source: ruby-gitlab-sidekiq-fetcher Version: 0.6.1-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-sidekiq [X-Debbugs-CC: debian...@lists.debian.org, ruby-side...@packages.debian.org] Dear maintainer(s), With a recent upload of ruby-sidekiq the autopkgtest of ruby-gitlab-sidekiq-fetcher fails in testing when that autopkgtest is run with the binary packages of ruby-sidekiq from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-sidekiqfrom testing6.3.1+dfsg-1 ruby-gitlab-sidekiq-fetcher from testing0.6.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby-sidekiq to testing [1]. Of course, ruby-sidekiq shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-sidekiq was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-sidekiq should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-sidekiq https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-gitlab-sidekiq-fetcher/17076745/log.gz ┌──┐ │ Checking Rubygems dependency resolution on ruby2.7 │ └──┘ GEM_PATH= ruby2.7 -e gem\ \"gitlab-sidekiq-fetcher\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'sidekiq' (>= 5, < 6.1) among 61 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' at: /usr/share/rubygems-integration/all/specifications/gitlab-sidekiq-fetcher-0.6.1.gemspec, execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372: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 'sidekiq' (>= 5, < 6.1) - did find: [sidekiq-6.3.1] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' , execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372: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 `' benchmark (default: 0.1.0) bigdecimal (default: 2.0.0) bundler (default: 2.1.4) cgi (default: 0.1.0) connection_pool (2.2.5) csv (default: 3.1.2) date (default: 3.0.0) dbm (default: 1.1.0) delegate (default: 0.1.0) did_you_mean (default: 1.4.0) etc (default: 1.1.0) fcntl (default: 1.0.0) fiddle (default: 1.0.0) fileutils (default: 1.4.1) forwardable (default: 1.3.1) gdbm (default: 2.1.0) getoptlong (default: 0.1.0) gitlab-sidekiq-fetcher (0.6.1) io-console (default
Bug#1000680: python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str"
[Boyuan Yang, 2021-11-28] > Thanks for the info and sorry for the breakage; obviously I should have > uploaded it into Experimental first. I am looking into fixing the issue > (ideally through upgrade of all related packages) but this may take some time. > If you already have a solution, it would be even better. I already fixed it by upgrading aiohttp. It needs 2 NEW packages that I packaged and uploaded, one of them is already accepted, second it waiting for review. Unfortunately I uploaded my previous build (tagged 1~exp1 in the git repo, but uploaded -1 so version in unstable needs aiosignal ASAP - I asked one of the ftp-masters if it's possible to check it sooner and hopefully unstable will be fixed soon)
Bug#1000772: macaulay2: autopkgtest regression on i386: out of memory
Source: macaulay2 Version: 1.19+ds-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of macaulay2 the autopkgtest of macaulay2 fails in testing when that autopkgtest is run with the binary packages of macaulay2 from unstable. It passes when run with only packages from testing. In tabular form: passfail macaulay2 from testing1.19+ds-3 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from macaulay2/1.19+ds-3. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=macaulay2 https://ci.debian.net/data/autopkgtest/testing/i386/m/macaulay2/17068663/log.gz K3Surfaces ** -- capturing check(0, "K3Surfaces") -- 15.155 seconds elapsed -- capturing check(1, "K3Surfaces") -- 3.51379 seconds elapsed -- capturing check(2, "K3Surfaces") -- 14.3303 seconds elapsed -- capturing check(3, "K3Surfaces") -- 27.3209 seconds elapsed -- capturing check(4, "K3Surfaces") -- 1.92744 seconds elapsed -- capturing check(5, "K3Surfaces") -- 9.5648 seconds elapsed -- skipping check(6, "K3Surfaces") -- 0.00011649 seconds elapsed -- skipping check(7, "K3Surfaces") -- 0.7854 seconds elapsed -- capturing check(8, "K3Surfaces") *** out of memory trying to allocate 131108 bytes, exiting *** cd /tmp/M2-2812-0/171-rundir/; GC_MAXIMUM_HEAP_SIZE=400M "/usr/bin/M2-binary" -q --int --no-randomize --no-readline --silent --stop --print-width 77 <"/tmp/M2-2812-0/170.m2" >>"/tmp/M2-2812-0/170.tmp" /tmp/M2-2812-0/170.tmp:0:1: (output file) error: Macaulay2 exited with status code 1 /tmp/M2-2812-0/170.m2:0:1: (input file) M2: *** Error 1 OpenPGP_signature Description: OpenPGP digital signature
Bug#998521: marked as done (libmediaart: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "image_Library")
Your message dated Sun, 28 Nov 2021 19:50:19 + with message-id and subject line Bug#998521: fixed in libmediaart 1.9.5-2 has caused the Debian Bug report #998521, regarding libmediaart: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "image_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.) -- 998521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmediaart Version: 1.9.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- \ > -Dimage_Library=gdk-pixbuf \ > -Dgtk_doc=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dimage_Library=gdk-pixbuf > -Dgtk_doc=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "image_Library" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:56:54.077852 > Main binary: /usr/bin/python3 > Build Options: -Dimage_Library=gdk-pixbuf -Dgtk_doc=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "image_Library" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dimage_Library=gdk-pixbuf > -Dgtk_doc=true returned exit code 1 > make[1]: *** [debian/rules:7: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/libmediaart_1.9.5-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libmediaart Source-Version: 1.9.5-2 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of libmediaart, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated libmediaart 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, 28 Nov 2021 14:33:43 -0500 Source: libmediaart Built-For-Profiles: noudeb Architecture: source Version: 1.9.5-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 998521 Changes: libmediaart (1.9.5-2) unstable; urgency=medium . * debian/rules: fix build option typo (Closes: #998521) Checksums-Sha1: 77214d2fbee7f27e7cda4c848ad5a535a9c58443 2420 libmediaart_1.9.5-2.dsc 4132151e154efc3396f9fb49af6c0e567540efae 4280 libmediaart_1.9.5-2.debian.tar.xz ca66577877e9672c6e7aa24ab5417a6bbd615533 9413 libmediaart_1.9.5-2_source.buildinfo Checksums-Sha256: 4e4b5292d8446e645a621826b19794417b036d50860b8a97ab5ae6bb9b7c2079 2420 libmediaart_1.9.5-2.dsc 2f20c75e56d50773d53365a22400871092f3607153456afdba07861a31c54565 4280 libmediaart_1.9.5-2.debian.tar.xz 1c407b0532ee4cf5e65b341
Bug#1000680: python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str"
Hi, 在 2021-11-27星期六的 23:23 -0500，Sandro Tosi写道： > > root@zion:/# python3.9 -c "import aiohttp" > > Traceback (most recent call last): > > File "", line 1, in > > File "/usr/lib/python3/dist-packages/aiohttp/__init__.py", line 6, in > > > > from .client import ( > > File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 35, in > > > > from . import hdrs, http, payload > > File "/usr/lib/python3/dist-packages/aiohttp/http.py", line 7, in > > > > from .http_parser import ( > > File "/usr/lib/python3/dist-packages/aiohttp/http_parser.py", line 15, > > in > > from .helpers import NO_EXTENSIONS, BaseTimerContext > > File "/usr/lib/python3/dist-packages/aiohttp/helpers.py", line 667, in > > > > class CeilTimeout(async_timeout.timeout): > > TypeError: function() argument 'code' must be code, not str > > > > > > root@zion:/# python3.10 -c "import aiohttp" > > Traceback (most recent call last): > > File "", line 1, in > > File "/usr/lib/python3/dist-packages/aiohttp/__init__.py", line 6, in > > > > from .client import ( > > File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 35, in > > > > from . import hdrs, http, payload > > File "/usr/lib/python3/dist-packages/aiohttp/http.py", line 7, in > > > > from .http_parser import ( > > File "/usr/lib/python3/dist-packages/aiohttp/http_parser.py", line 15, > > in > > from .helpers import NO_EXTENSIONS, BaseTimerContext > > File "/usr/lib/python3/dist-packages/aiohttp/helpers.py", line 667, in > > > > class CeilTimeout(async_timeout.timeout): > > TypeError: function() argument 'code' must be code, not str > > Boyuan, > you caused this by uploading python-async-timeout 4.x > > https://tracker.debian.org/news/1280914/accepted-python-async-timeout-401-1-source-into-unstable/ > > while aiohttp is incompatible with it. > > Apparently the latest version of aiohttp supports async-timeout > 4.0 > > https://github.com/aio-libs/aiohttp/blob/v3.8.1/setup.cfg#L54 > > are you going to handle this upgrade? Thanks for the info and sorry for the breakage; obviously I should have uploaded it into Experimental first. I am looking into fixing the issue (ideally through upgrade of all related packages) but this may take some time. If you already have a solution, it would be even better. Thanks, Boyuan Yang
Bug#1000768: krb5: FTBFS due to missing dependency on tex-gyre
Source: krb5
Severity: serious
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Between September and October, something changed in krb5's build
dependencies that triggers a build failure:
https://tests.reproducible-builds.org/debian/history/amd64/krb5.html
You can pick from a few failing build logs at:
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/krb5.html
Except from a failing build:
(/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
(/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
! LaTeX Error: File `tgtermes.sty' not found.
Type X to quit or to proceed,
or enter new name. (Default extension: sty)
Enter file name:
! Emergency stop.
l.37 \usepackage
{tgheros}^^M
! ==> Fatal error occurred, no output PDF file produced!
I'm not sure the exact cause of the changes, but adding tex-gyre to
Build-Depends-Indep appears to fix this issue.
Thanks for maintaining krb5!
live well,
vagrant
From ba098c18c519c9275eafeac18983e5974a8714af Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Sun, 28 Nov 2021 18:56:56 +
Subject: [PATCH] debian/control: Add Build-Depends-Indep on tex-gyre.
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index bd78bbe11..973f11b64 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Build-Depends: debhelper-compat (= 13), byacc | bison,
libkeyutils-dev [linux-any], libldap2-dev , libsasl2-dev ,
libssl-dev, ss-dev,
libverto-dev (>= 0.2.4), pkg-config
-Build-Depends-Indep: python3, python3-cheetah, python3-lxml, python3-sphinx, doxygen, doxygen-latex
+Build-Depends-Indep: python3, python3-cheetah, python3-lxml, python3-sphinx, doxygen, doxygen-latex, tex-gyre
Standards-Version: 4.5.0
Maintainer: Sam Hartman
Uploaders: Russ Allbery , Benjamin Kaduk
--
2.30.2
signature.asc
Description: PGP signature
Bug#997081: marked as done (statsmodels: FTBFS: tests fail)
Your message dated Sun, 28 Nov 2021 19:22:40 +
with message-id
and subject line Bug#997081: fixed in statsmodels 0.13.1+dfsg-1
has caused the Debian Bug report #997081,
regarding statsmodels: FTBFS: tests fail
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.)
--
997081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: statsmodels
Version: 0.12.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> === FAILURES
> ===
> TestMICE.test_combine
> _
>
> self = 0x7f18160740d0>
>
> @pytest.mark.slow
> def test_combine(self):
>
> np.random.seed(3897)
> x1 = np.random.normal(size=300)
> x2 = np.random.normal(size=300)
> y = x1 + x2 + np.random.normal(size=300)
> x1[0:100] = np.nan
> x2[250:] = np.nan
> df = pd.DataFrame({"x1": x1, "x2": x2, "y": y})
> idata = mice.MICEData(df)
> mi = mice.MICE("y ~ x1 + x2", sm.OLS, idata, n_skip=20)
> result = mi.fit(10, 20)
>
> fmi = np.asarray([0.1778143, 0.11057262, 0.29626521])
> > assert_allclose(result.frac_miss_info, fmi, atol=1e-5)
> E AssertionError:
> E Not equal to tolerance rtol=1e-07, atol=1e-05
> E
> E Mismatched elements: 3 / 3 (100%)
> E Max absolute difference: 0.17686937
> E Max relative difference: 1.59957657
> Ex: array([0.230217, 0.287442, 0.322124])
> Ey: array([0.177814, 0.110573, 0.296265])
>
> ../.pybuild/cpython3_3.9_statsmodels/build/statsmodels/imputation/tests/test_mice.py:366:
> AssertionError
> __ test_corrpsd_threshold[0]
> ___
>
> threshold = 0
>
> @pytest.mark.parametrize('threshold', [0, 1e-15, 1e-10, 1e-6])
> def test_corrpsd_threshold(threshold):
> x = np.array([[1, -0.9, -0.9], [-0.9, 1, -0.9], [-0.9, -0.9, 1]])
>
> y = corr_nearest(x, n_fact=100, threshold=threshold)
> evals = np.linalg.eigvalsh(y)
> > assert_allclose(evals[0], threshold, rtol=1e-6, atol=1e-15)
> E AssertionError:
> E Not equal to tolerance rtol=1e-06, atol=1e-15
> E
> E Mismatched elements: 1 / 1 (100%)
> E Max absolute difference: 1.05471187e-15
> E Max relative difference: inf
> Ex: array(1.054712e-15)
> Ey: array(0)
>
> ../.pybuild/cpython3_3.9_statsmodels/build/statsmodels/stats/tests/test_corrpsd.py:196:
> AssertionError
> _ test_mixedlm
> _
>
> def test_mixedlm():
>
> np.random.seed(3424)
>
> n = 200
>
> # The exposure (not time varying)
> x = np.random.normal(size=n)
> xv = np.outer(x, np.ones(3))
>
> # The mediator (with random intercept)
> mx = np.asarray([4., 4, 1])
> mx /= np.sqrt(np.sum(mx**2))
> med = mx[0] * np.outer(x, np.ones(3))
> med += mx[1] * np.outer(np.random.normal(size=n), np.ones(3))
> med += mx[2] * np.random.normal(size=(n, 3))
>
> # The outcome (exposure and mediator effects)
> ey = np.outer(x, np.r_[0, 0.5, 1]) + med
>
> # Random structure of the outcome (random intercept and slope)
> ex = np.asarray([5., 2, 2])
> ex /= np.sqrt(np.sum(ex**2))
> e = ex[0] * np.outer(np.random.normal(size=n), np.ones(3))
> e += ex[1] * np.outer(np.random.normal(size=n), np.r_[-1, 0, 1])
> e += ex[2] * np.random.normal(size=(n, 3))
> y = ey + e
>
> # Group membership
> idx = np.outer(np.arange(n), np.ones(3))
>
> # Time
> tim = np.outer(np.ones(n), np.r_[-1, 0, 1])
>
> df = pd.DataFrame({"y": y.flatten(), "x": xv.flatten(),
>"id": idx.flatten(), "time": tim.flatten(),
>"med": med.flatten()})
>
> mediator_model = sm.MixedLM.from_formula("med ~ x", groups="id",
> data=df)
> outcome_model = sm.MixedLM.from_formula("y ~ med + x", groups="id",
> data=df)
> me = Mediation(outcome_model, mediator_model, "x", "med")
> mr = me.fit(n_rep=2)
> st = mr.summary(
Bug#995202: horst: diff for NMU version 5.1-2.1
Dear maintainer,
I've prepared an NMU for horst (versioned as 5.1-2.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru horst-5.1/debian/changelog horst-5.1/debian/changelog
--- horst-5.1/debian/changelog 2019-02-01 17:29:06.0 +0200
+++ horst-5.1/debian/changelog 2021-11-28 20:51:58.0 +0200
@@ -1,3 +1,11 @@
+horst (5.1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch from Sven Joachim to fix FTBFS with new ncurses.
+(Closes: #995202)
+
+ -- Adrian Bunk Sun, 28 Nov 2021 20:51:58 +0200
+
horst (5.1-2) unstable; urgency=medium
* Bug fix: "horst FTCBFS: upstream Makefile hard codes build
diff -Nru horst-5.1/debian/patches/0001-Fix-string-format-errors-with-recent-ncurses.patch horst-5.1/debian/patches/0001-Fix-string-format-errors-with-recent-ncurses.patch
--- horst-5.1/debian/patches/0001-Fix-string-format-errors-with-recent-ncurses.patch 1970-01-01 02:00:00.0 +0200
+++ horst-5.1/debian/patches/0001-Fix-string-format-errors-with-recent-ncurses.patch 2021-11-28 20:51:36.0 +0200
@@ -0,0 +1,39 @@
+From 8110d832bd6502b7caed75b6504bd6d24d30d36b Mon Sep 17 00:00:00 2001
+From: Sven Joachim
+Date: Thu, 14 Oct 2021 20:06:26 +0200
+Subject: [PATCH] Fix string format errors with recent ncurses
+
+---
+ display-main.c | 2 +-
+ display.c | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/display-main.c b/display-main.c
+index b613291..6519895 100644
+--- a/display-main.c
b/display-main.c
+@@ -53,7 +53,7 @@ static struct ewma bpsn_avg;
+ void print_dump_win(const char *str, int refresh)
+ {
+ wattron(dump_win, RED);
+- wprintw(dump_win, str);
++ wprintw(dump_win, "%s", str);
+ wattroff(dump_win, RED);
+ if (refresh)
+ wrefresh(dump_win);
+diff --git a/display.c b/display.c
+index 777c7a2..e0755f4 100644
+--- a/display.c
b/display.c
+@@ -86,7 +86,7 @@ print_centered(WINDOW* win, int line, int cols, const char *fmt, ...)
+ vsnprintf(buf, cols, fmt, ap);
+ va_end(ap);
+
+- mvwprintw(win, line, cols / 2 - strlen(buf) / 2, buf);
++ mvwprintw(win, line, cols / 2 - strlen(buf) / 2, "%s", buf);
+ free(buf);
+ }
+
+--
+2.33.0
+
diff -Nru horst-5.1/debian/patches/series horst-5.1/debian/patches/series
--- horst-5.1/debian/patches/series 2019-02-01 17:29:06.0 +0200
+++ horst-5.1/debian/patches/series 2021-11-28 20:51:57.0 +0200
@@ -1,3 +1,4 @@
cross.patch
0001-add-support-for-PREFIX.patch
0001-install-manpages-in-share-properly-Closes-91.patch
+0001-Fix-string-format-errors-with-recent-ncurses.patch
Bug#995769: dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1)
Hi, Getting package autoremoved from testing is not end-of-the-world -- once the bug is fixed, it can get back to Debian Testing at any time. Meanwhile, the previous bug is real and will need to be fixed sooner or later. I may get back to look into the bug later, bug I don't have enough time recently. Feel free to find help from others, or I may get involved when I have enough time. Thanks, Boyuan Yang 在 2021-11-28星期日的 11:35 -0500，Tong Sun写道： > Hi Boyuan, please please help. > > -- Forwarded message - > From: Tong Sun > Date: Sun, Nov 28, 2021 at 11:33 AM > Subject: Re: Bug#995769: dbab: v1.5.7 package fail to upgrade from > bullseye (1.5.01-1) > To: Boyuan Yang , <995...@bugs.debian.org> > > > To Boyuan, or any mentors reading this issue. > > I've been trying to fix it myself, but all my previous attempts > failed, because I don't understand what breaks and why, from the > output of the package upgrade log. > > I've sent a help request to debian-mentors a few days ago, but nobody > answers yet. > > My package is now marked for autoremoval from testing, with a wrong > reason, and I don't know how to stop my package being autoremed from > testing, and I got no answers/help on that either. > > Since I don't know how to fix it myself, and all my previous attempts > failed, if nobody helps me by next weekend, I'll do the only thing > that I know -- to change the severity of this bug to minor, because > there is a simple solution to it as explained below. This will solve > everything and win me the time it takes for me to do further > investigation/testing. > > Really hope it won't be the case. > Somebody help please. > Thanks > > On Thu, Oct 7, 2021 at 9:31 PM Tong Sun wrote: > > > > On Tue, Oct 5, 2021 at 7:27 AM Boyuan Yang wrote: > > > > > Package dbab/1.5.7-1 has broken maintscript and cannot be properly > > > upgraded > > > from dbab/1.5.01-1 to dbab/1.5.7-1: > > > > Thanks for reporting. I'll try to fix it ASAP. > > > > In the meantime, for anyone who doesn't want to wait for the fix to be > > published -- > > do not do an upgrade -- remove the package completely, then do a fresh > > install. > > > > thx
Bug#1000732: marked as pending in python-click-threading
Control: tag -1 pending Hello, Bug #1000732 in python-click-threading 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-click-threading/-/commit/aaaee62067b52199ea3f56fad6033b8ad720ad50 New upstream release. Closes: #996337, #997480, #1000732 Compatible with python3-click version 8.0 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000732
Processed: Bug#1000732 marked as pending in python-click-threading
Processing control commands: > tag -1 pending Bug #1000732 [python3-click-threading] python3-click-threading: broken monkeypatching Added tag(s) pending. -- 1000732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000186: marked as done (ecflow: silently fails to build python extension if boost is missing)
Your message dated Sun, 28 Nov 2021 18:33:31 + with message-id and subject line Bug#1000186: fixed in ecflow 5.7.2-2 has caused the Debian Bug report #1000186, regarding ecflow: silently fails to build python extension if boost is missing 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.) -- 1000186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ecflow Version: 5.7.2-1 Severity: normal Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Hi Maintainer ecflow build-depends on python3-all-dev and normally builds for all supported python versions correctly. However, in a recent rebuild [1] for python 3.10, boost had not yet been rebuilt and ecflow built only for python 3.9. I would have expected a failure here. I've copied what I think is the relevant part of the log below. I will schedule another rebuild once boost is available. Regards Graham [1] https://buildd.debian.org/status/fetch.php?pkg=ecflow&arch=amd64&ver=5.7.2-1%2Bb1&stamp=1637180180&raw=0 [ 68%] Building CXX object Viewer/ecflowUI/src/CMakeFiles/ecflow_ui.x.dir/NodeExpression.cpp.o cd /<>/debian/build-python3.10/Viewer/ecflowUI/src && /usr/bin/c++ -DECFLOW_LOGVIEW -DECFLOW_QT5 -DECFLOW_SHARED_DIR=\"/usr/share/ecflow\" -DECF_OPENSSL -DQT_CHARTS_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_KEYWORDS -DQT_SVG_LIB -DQT_WIDGETS_LIB -I/<>/cereal/include -I/<>/Viewer/ecflowUI/src/. -I/<>/Viewer/ecflowUI/src/../../libViewer/src -I/<>/Viewer/ecflowUI/src/../../../ACore/src -I/<>/Viewer/ecflowUI/src/../../../ANattr/src -I/<>/Viewer/ecflowUI/src/../../../ANode/src -I/<>/Viewer/ecflowUI/src/../../../ANode/test -I/<>/Viewer/ecflowUI/src/../../../Base/src -I/<>/Viewer/ecflowUI/src/../../../Base/src/cts -I/<>/Viewer/ecflowUI/src/../../../Base/src/stc -I/<>/Viewer/ecflowUI/src/../../../Client/src -I/<>/Viewer/ecflowUI/src/TextPager -I/<>/debian/build-python3.10/Viewer/ecflowUI/src -I/<>/ACore/src -I/<>/debian/build-python3.10 -I/<>/ANattr/src -I/<>/ANattr/../ACore/src -I/<>/ANode/../ACore/src -I/<>/ANode/../ANattr/src -I/<>/ANode/src -I/<>/ANode/parser/src -I/<>/Base/src -I/<>/Base/../ACore/src -I/<>/Base/../ANattr/src -I/<>/Base/../ANode/src -I/<>/Base/../Base/src -I/<>/Base/../Base/src/cts -I/<>/Base/../Base/src/stc -I/<>/Client/src -I/<>/Client/../ACore/src -I/<>/Client/../ANattr/src -I/<>/Client/../ANode/src -I/<>/Client/../Base/src -I/<>/Client/../Base/src/cts -I/<>/Client/../Base/src/stc -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork -I/usr/include/x86_64-linux-gnu/qt5/QtSvg -I/usr/include/x86_64-linux-gnu/qt5/QtCharts -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fPIE -fPIC -std=gnu++14 -MD -MT Viewer/ecflowUI/src/CMakeFiles/ecflow_ui.x.dir/NodeExpression.cpp.o -MF CMakeFiles/ecflow_ui.x.dir/NodeExpression.cpp.o.d -o CMakeFiles/ecflow_ui.x.dir/NodeExpression.cpp.o -c /<>/Viewer/ecflowUI/src/NodeExpression.cpp make[4]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libboost_python310.so', needed by 'Pyext/python3/ecflow.so'. Stop. make[4]: *** Waiting for unfinished jobs --- End Message --- --- Begin Message --- Source: ecflow Source-Version: 5.7.2-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of ecflow, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated ecflow 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, 28 Nov 2021 14:28:45 + Source: ecflow Architecture: source Version: 5.7.2-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1000186 Changes: ecflow (5.7.2-2) unstable; urgency=medium
Bug#1000421: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32
Guillem Jover: > Bug #1000421 in package dpkg reported by you has been fixed in > the dpkg/dpkg.git Git repository Thanks for the investigation. What a nuisance. Joachim Reichel (cppcheck maintainer): > I'll upload a new version cppcheck with a workaround shortly Would you mind both prioritising this fix ? FTAOD it's not just cppcheck that is scheduled for autoremoval. Any package which transitively [build-]depends on any package whose .debs are affected will be scheduled for autoremoval (assuming some bug has been filed). I noticed this problem because my own package `dgit` is scheduled for autoremoval due to this bug and I don't even know what the dependency chain is that links dgit to cppcheck. When this happens to me it usually involves git-buildpackage, so perhaps gbp is scheduled for autoremoval too. I also think that when the fixed dpkg-shlibdeps is in unstable: 1. We should consider backporting the dpkg-shlibdeps fix in a stable point release, since it seems people might have new binutils (via a Debian backports suite or from upsteam) 2. We should consider trying to detect this situation in existing .debs and requesting .deb rebuilds or something. Do we have a plausible way of doing that ? Possibly we could look for the combination of new binutils and old dpkg-dev, in buildinfo files. Thanks, Ian. -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#990224: marked as done (lazarus-src-2.0: leaves diversion after upgrade from sid to experimental)
Your message dated Sun, 28 Nov 2021 18:19:22 + with message-id and subject line Bug#990224: fixed in lazarus 2.0.12+dfsg-3 has caused the Debian Bug report #990224, regarding lazarus-src-2.0: leaves diversion after upgrade from sid to experimental to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 990224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lazarus-src-2.0 Version: 2.0.12+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove some diversions after upgrading from sid to experimental and removing the package afterwards. >From the attached log (scroll to the bottom...): 0m35.4s ERROR: FAIL: Installed diversions (dpkg-divert) not removed by purge: diversion of /usr/lib/lazarus/2.0.10/examples/pascalstream/CopyAsPasPkg/copyformaspascaldemopkg.lpk to /usr/lib/lazarus/2.0.10/examples/pascalstream/CopyAsPasPkg/copyformaspascaldemopkg.lpk.orig by lazarus-src-2.0 diversion of /usr/lib/lazarus/2.0.10/components/datetimectrls/datetimectrls.lpk to /usr/lib/lazarus/2.0.10/components/datetimectrls/datetimectrls.lpk.orig by lazarus-src-2.0 diversion of /usr/lib/lazarus/2.0.10/components/mrumenu/lazmrumenu.lpk to /usr/lib/lazarus/2.0.10/components/mrumenu/lazmrumenu.lpk.orig by lazarus-src-2.0 diversion of /usr/lib/lazarus/2.0.10/lcl/interfaces/lcl.lpk to /usr/lib/lazarus/2.0.10/lcl/interfaces/lcl.lpk.orig by lazarus-src-2.0 ... diversion of /usr/lib/lazarus/2.0.10/components/debuggerintf/debuggerintf.lpk to /usr/lib/lazarus/2.0.10/components/debuggerintf/debuggerintf.lpk.orig by lazarus-src-2.0 diversion of /usr/lib/lazarus/2.0.10/components/IdeLazLogger/idelazlogger.lpk to /usr/lib/lazarus/2.0.10/components/IdeLazLogger/idelazlogger.lpk.orig by lazarus-src-2.0 diversion of /usr/lib/lazarus/2.0.10/components/pochecker/pochecker.lpk to /usr/lib/lazarus/2.0.10/components/pochecker/pochecker.lpk.orig by lazarus-src-2.0 cheers, Andreas lazarus-src-2.0_2.0.12+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: lazarus Source-Version: 2.0.12+dfsg-3 Done: Abou Al Montacir We believe that the bug you reported is fixed in the latest version of lazarus, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Abou Al Montacir (supplier of updated lazarus 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, 28 Nov 2021 16:43:45 +0100 Source: lazarus Architecture: source Version: 2.0.12+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Abou Al Montacir Closes: 956956 990224 Changes: lazarus (2.0.12+dfsg-3) unstable; urgency=medium . * Ensure no diversion is left after removal or upgrade. (Closes: Bug#990224) * Removed flaky flag on tests. * Fix unexpected failure building IDE inspector package test. (Closes: Bug#956956) * Updated time stamp for package IdeInspector. * Fixed typos introduced in 5141e596467ce187e707bffa704d00e0f8a0f6c4. Checksums-Sha1: 48457eae8969f5c916cc20a6898d9b2a50d21004 2883 lazarus_2.0.12+dfsg-3.dsc f39342f9e6289eb4ce4c50c08513da1b1d90d528 72244 lazarus_2.0.12+dfsg-3.debian.tar.xz d30019b742bf8e73819679b99ed5647ed5048d4b 19372 lazarus_2.0.12+dfsg-3_amd64.buildinfo Checksums-Sha256: d4c7107c201b1c707a72a4d3f9d4d36cfadcb6a46c2fc9c3a0d2def9feb3408f 2883 lazarus_2.0.12+dfsg-3.dsc 8173a981e0268c551dcc409eac5f54c9f32e87d5bfbc75fdb68239deaeec14cd 72244 lazarus_2.0.12+dfsg-3.debian.tar.xz c73a93fd43ce9d9197d31dcc8874d0fd23078065866c611cdbc8fa59da8a18e8 19372 lazarus_2.0.12+dfsg-3_amd64.buildinfo Files: 98bdf2bd37b92e5cd2728bbe022d45b6 2883 devel optional lazarus_2.0.12+dfsg-3.dsc e3cdcad2fda108764f0a2172ab61e37e 72244 devel optional lazarus_2.0.12+dfsg-3.debian.tar.xz e38beb9c27f05244be32ade34721ddae 19372 devel optional lazarus_2.0.12+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iI0EAREKADUWIQS69sZENhB4UNQicQazJVxtVYe
Bug#995769: dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1)
To Boyuan, or any mentors reading this issue. I've been trying to fix it myself, but all my previous attempts failed, because I don't understand what breaks and why, from the output of the package upgrade log. I've sent a help request to debian-mentors a few days ago, but nobody answers yet. My package is now marked for autoremoval from testing, with a wrong reason, and I don't know how to stop my package being autoremed from testing, and I got no answers/help on that either. Since I don't know how to fix it myself, and all my previous attempts failed, if nobody helps me by next weekend, I'll do the only thing that I know -- to change the severity of this bug to minor, because there is a simple solution to it as explained below. This will solve everything and win me the time it takes for me to do further investigation/testing. Really hope it won't be the case. Somebody help please. Thanks On Thu, Oct 7, 2021 at 9:31 PM Tong Sun wrote: > > On Tue, Oct 5, 2021 at 7:27 AM Boyuan Yang wrote: > > > Package dbab/1.5.7-1 has broken maintscript and cannot be properly upgraded > > from dbab/1.5.01-1 to dbab/1.5.7-1: > > Thanks for reporting. I'll try to fix it ASAP. > > In the meantime, for anyone who doesn't want to wait for the fix to be > published -- > do not do an upgrade -- remove the package completely, then do a fresh > install. > > thx
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 1000680 + python3-slixmpp poezio Bug #1000680 [python3-aiohttp] python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str" Added indication that 1000680 affects python3-slixmpp and poezio > End of message, stopping processing here. Please contact me if you need assistance. -- 1000680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996640: powertop FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
Control: tags -1 + fixed-upstream Am 16.10.2021 um 17:44 schrieb Helmut Grohne: > Source: powertop > Version: 2.13-2 > Severity: serious > Tags: ftbfs > > powertop fails to build from source in unstable, because ncurses added > format string annotations. A non-parallel build now ends as follows: > > | g++ -std=c++11 -DHAVE_CONFIG_H -I. -I.. -DLOCALEDIR=\"/usr/share/locale\" > -I/usr/include/libnl3 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 > -I/usr/include/x86_64-linux-gnu -pthread -Wdate-time -D_FORTIFY_SOURCE=2 > -Wall -Wformat -Wshadow -fno-omit-frame-pointer -fstack-protector > -I/usr/include/libnl3 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 > -I/usr/include/x86_64-linux-gnu -pthread -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o powertop-display.o `test -f 'display.cpp' || > echo './'`display.cpp > | display.cpp: In function ‘void show_tab(unsigned int)’: > | display.cpp:128:26: error: format not a string literal and no format > arguments [-Werror=format-security] > | 128 | mvwprintw(bottom_line, 0,0, c); > | | ~^ > | cc1plus: some warnings being treated as errors > | make[4]: *** [Makefile:1107: powertop-display.o] Error 1 > | make[4]: Leaving directory '/<>/src' > | make[3]: *** [Makefile:657: all] Error 2 > | make[3]: Leaving directory '/<>/src' > | make[2]: *** [Makefile:461: all-recursive] Error 1 > | make[2]: Leaving directory '/<>' > | make[1]: *** [Makefile:391: all] Error 2 > | make[1]: Leaving directory '/<>' > | dh_auto_build: error: make -j1 returned exit code 2 > | make: *** [debian/rules:9: binary] Error 25 > | dpkg-buildpackage: error: debian/rules binary subprocess returned exit > status 2 The upstream git repository contains a fix for that problem: https://github.com/fenrus75/powertop/commit/9ef1559a1582f23d599c149601c3a8e06809296c It looks correct to me, but I have not tested it. Cheers, Sven
Processed: Re: Bug#996640: powertop FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
Processing control commands: > tags -1 + fixed-upstream Bug #996640 [src:powertop] powertop FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) fixed-upstream. -- 996640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000756: freedv: FTBFS: varicode.h: No such file or directory
Source: freedv Version: 1.4.3~1gdc71a1c-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | cd "/<>/Build/src" && /usr/bin/c++ -DDEB_VERSION="\"1.4.3~1gdc71a1c-1+b2\"" -DHAVE_LINUX_HIDRAW_H -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I"/<>/src" -I"/<>/Build/src" -I"/<>/Build" -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem /usr/include/wx-3.0 -isystem /usr/include/codec2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pthread -g -MD -MT src/CMakeFiles/freedv.dir/dlg_ptt.cpp.o -MF CMakeFiles/freedv.dir/dlg_ptt.cpp.o.d -o CMakeFiles/freedv.dir/dlg_ptt.cpp.o -c "/<>/src/dlg_ptt.cpp" | In file included from /<>/src/dlg_ptt.h:25, | from /<>/src/dlg_ptt.cpp:22: | /<>/src/fdmdv2_main.h:101:10: fatal error: varicode.h: No such file or directory | 101 | #include "varicode.h" | | ^~~~ | compilation terminated. | make[3]: *** [src/CMakeFiles/freedv.dir/build.make:121: src/CMakeFiles/freedv.dir/dlg_ptt.cpp.o] Error 1 | make[3]: *** Waiting for unfinished jobs | In file included from /<>/src/dlg_filter.h:25, | from /<>/src/dlg_filter.cpp:21: | /<>/src/fdmdv2_main.h:101:10: fatal error: varicode.h: No such file or directory | 101 | #include "varicode.h" | | ^~~~ | In file included from /<>/src/dlg_options.h:25, | from /<>/src/dlg_options.cpp:22: | /<>/src/fdmdv2_main.h:101:10: fatal error: varicode.h: No such file or directory | 101 | #include "varicode.h" | | ^~~~ | compilation terminated. | compilation terminated. | make[3]: *** [src/CMakeFiles/freedv.dir/build.make:93: src/CMakeFiles/freedv.dir/dlg_filter.cpp.o] Error 1 | make[3]: *** [src/CMakeFiles/freedv.dir/build.make:107: src/CMakeFiles/freedv.dir/dlg_options.cpp.o] Error 1 | In file included from /<>/src/dlg_audiooptions.cpp:22: | /<>/src/fdmdv2_main.h:101:10: fatal error: varicode.h: No such file or directory | 101 | #include "varicode.h" | | ^~~~ | compilation terminated. See https://buildd.debian.org/status/fetch.php?pkg=freedv&arch=amd64&ver=1.4.3%7E1gdc71a1c-1%2Bb2&stamp=1638113993&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#997194: mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security]
Processing control commands: > tags -1 + fixed-upstream Bug #997194 [src:mtr] mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) fixed-upstream. -- 997194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997194: mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security]
Control: tags -1 + fixed-upstream On 2021-10-24 05:56 -0700, Robert Woodcock wrote: > On 10/24/21 4:36 AM, Rogier Wolff wrote: >> >> I think this is perfectly legal C code and your compiler doesn't like >> it. It doesn't just warn, but gives an error. >> >> Roger. > Rogier, that is a 100% true statement, but Debian (and most other > distributions) have started using the -Werror=format-security build flag for > everything everywhere because leaving all of these calls as-is means, in > certain cases, leaving vulnerabilities in. Sure, you can prove that mtr's > code introduces no such vulnerabilities because none of the format specs are > user-supplied, but it's probably not reasonable to expect that that would be > a one-time effort, whereas changing the code would be. In the meantime upstream has accepted a pull request (not tested by me): https://github.com/traviscross/mtr/commit/aeb493e08eabcb4e6178bda0bb84e9cd01c9f213 Cheers, Sven
