Processed: affects 1027416
Processing commands for cont...@bugs.debian.org: > affects 1027416 src:qgis Bug #1027416 [src:qscintilla2] qscintilla2: python3-pyqt5.qsci : Depends: python3-pyqt6 but it is not installable Added indication that 1027416 affects src:qgis > thanks Stopping processing here. Please contact me if you need assistance. -- 1027416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027271: open-vm-tools doesn't need libprocps
Hi I checked the source code, build logs and current binaries, open-vm-tools doesn't use libprocps or link to it. A simple removal of libprocps-dev from debian/control will fix this. - Craig
Bug#1027270: guymager doesn't require libprocps
Hi, I checked the build logs, the source code and even the current binary packages. guymager does not need libprocps. A simple removal of libprocps-dev from debian/control is all that is needed. - Craig
Bug#1027098: marked as done (vagrant: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: [31mFailure/Error: expect(env).to receive(:[]=).with(:machine_ssh_info, host: "ADDRESS")[0m)
Your message dated Sat, 31 Dec 2022 03:35:52 +
with message-id
and subject line Bug#1027098: fixed in vagrant 2.3.4+dfsg-1
has caused the Debian Bug report #1027098,
regarding vagrant: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed:
[31mFailure/Error: expect(env).to receive(:[]=).with(:machine_ssh_info,
host: "ADDRESS")[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.)
--
1027098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vagrant
Version: 2.2.19+dfsg-3
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
vagrant failed to build.
Relevant part of the build log (hopefully):
> [31mFailure/Error: expect(env).to receive(:[]=).with(:machine_ssh_info,
> host: "ADDRESS")[0m
> [31m[0m
> [31m {:ui=># @logger=# @fullname="vagrant::ui::interface", @outputters=[], @additive=true,
> @name="interface", @path="vagrant::ui",
> @parent=#,
> @level=0, @trace=false>, @opts={}, @stdin=#>,
> @stdout=#>, @stderr=#>>, :machine=># "machine">} received :[]= with unexpected arguments[0m
> [31mexpected: (:machine_ssh_info, {:host=>"ADDRESS"}) (keyword
> arguments)[0m
> [31m got: (:machine_ssh_info, {:host=>"ADDRESS"}) (options
> hash)[0m
> [36m#
> /<>/test/unit/plugins/providers/hyperv/action/read_guest_ip_test.rb:34:in
> `block (3 levels) in '[0m
>
> Finished in 4 minutes 58.9 seconds (files took 1.27 seconds to load)
> [31m2940 examples, 3 failures, 9 pending[0m
>
> Failed examples:
>
> [31mrspec
> /<>/test/unit/plugins/commands/package/command_test.rb:65[0m
> [36m# VagrantPlugins::CommandPackage::Command#execute with single argument
> with --output option packages default machine inside specified folder[0m
> [31mrspec
> /<>/test/unit/plugins/commands/package/command_test.rb:98[0m
> [36m# VagrantPlugins::CommandPackage::Command#execute with --base option and
> option value packages vm defined within virtualbox[0m
> [31mrspec
> /<>/test/unit/plugins/providers/hyperv/action/read_guest_ip_test.rb:33[0m
> [36m# VagrantPlugins::HyperV::Action::ReadGuestIP with machine ID set
> should set the host information into the env[0m
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern test/unit/\{plugins\}/\*\*/\*_test.rb --exclude-pattern
> \{test/unit/vagrant/action/builtin/box_add_test.rb,test/unit/plugins/communicators/winrm/\*_test.rb,test/unit/plugins/pushes/ftp/\*_test.rb\}
> -I/<>/debian/lib failed
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
vagrant.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.3.4+dfsg-1
Done: Antonio Terceiro
We believe that the bug you reported is fixed in the latest version of
vagrant, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Terceiro (supplier of updated vagrant 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: Fri, 30 Dec 2022 21:47:34 -0300
Source: vagrant
Architecture: source
Version: 2.3.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Antonio Terceiro
Closes: 1027098
Changes:
vagrant (2.3.4+dfsg-1) unstable; urgency=medium
.
* New upstream version 2.3.4+dfsg
- Passes its tests with rspec 3.12 (Closes: #1027098)
* debian/control: update with dh-make-ruby
* Refresh patches.
Drop patch for VirtualBox 7.0 support as it is already present upstream.
*
Bug#1027347: marked as done (ruby-specinfra: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find
Your message dated Sat, 31 Dec 2022 03:19:12 + with message-id and subject line Bug#1027347: fixed in ruby-specinfra 2.83.4-2 has caused the Debian Bug report #1027347, regarding ruby-specinfra: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'net-telnet' (= 0.1.1) among 103 total gem(s) (Gem::MissingSpecError) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-specinfra Version: 2.83.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221230 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block > in activate_dependencies': Could not find 'net-telnet' (= 0.1.1) among 103 > total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-specinfra/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > at: > /<>/debian/ruby-specinfra/usr/share/rubygems-integration/all/specifications/specinfra-2.83.4.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'net-telnet' (= 0.1.1) - did find: [net-telnet-0.2.0] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-specinfra/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > abbrev (default: 0.1.0) > base64 (default: 0.1.1) > bcrypt_pbkdf (1.1.0) > benchmark (default: 0.2.0) > bigdecimal (default: 3.1.1) > bundler (2.3.15, default: 2.3.7) > cgi (default: 0.3.1) > csv (default: 3.2.2) > date (default: 3.2.2) > debug (1.4.0) > delegate (default: 0.2.0) > did_you_mean (default: 1.6.1) > diff-lcs (1.5.0) > digest (default: 3.1.0) > drb (default: 2.1.0) > ed25519 (1.3.0) > english (default: 0.7.1) > erb (default: 2.2.3) > error_highlight (default: 0.3.0) > etc (default: 1.3.0) > fcntl (default: 1.0.1) > fiddle (default: 1.1.0) > fileutils (default: 1.6.0) > find (default: 0.1.1) > forwardable (default: 1.3.2) > getoptlong (default: 0.1.1) > io-console (default: 0.5.11) &g
Bug#1027361: e2tools: FTBFS in bullseye (missing build-depends on e2fsprogs)
Hi Santiago, Thanks for your report. I'd fix this bug and uploaded the new package to mentors. Would you help to upload it ? https://mentors.debian.net/package/e2tools/ Thanks! xiao sheng wen 在 2022/12/31 02:00, Santiago Vila 写道: Package: src:e2tools Version: 0.1.0-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: ... make check-TESTS make[4]: Entering directory '/<>' make[5]: Entering directory '/<>' /bin/mkdir -p tests /bin/sed -e 's|[@]HAVE_EXT2FS_XATTRS_FALSE@||g' -e 's|[@]HAVE_EXT2FS_XATTRS_TRUE@|# |g' -e 's|[@]top_builddir@|.|g' -e 's|[@]top_srcdir@|.|g' -e 's|[@]DD@|/bin/dd|g' -e 's|[@]MKE2FS@||g' < tests/simple-test.shin > tests/simple-test.sh /bin/chmod +x tests/simple-test.sh FAIL: tests/simple-test.sh = e2tools 0.1.0: ./test-suite.log = # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: tests/simple-test.sh == + testimg=test-1M.img + trap EXIT + rm -f test-1M.img + /bin/dd if=/dev/null of=test-1M.img bs=1 count=1 seek=1M 0+0 records in 0+0 records out 0 bytes copied, 5.5729e-05 s, 0.0 kB/s + -F test-1M.img ./tests/simple-test.sh: 30: -F: not found FAIL tests/simple-test.sh (exit status: 127) ... Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa: https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB OpenPGP_signature Description: OpenPGP digital signature
Bug#1027347: marked as pending in ruby-specinfra
Control: tag -1 pending Hello, Bug #1027347 in ruby-specinfra reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-specinfra/-/commit/cbd71325cccdd43e93a41b84c5e6b46b4a68a27d Relax ruby-net-telnet version (Closes: #1027347) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027347
Processed: Bug#1027347 marked as pending in ruby-specinfra
Processing control commands: > tag -1 pending Bug #1027347 [src:ruby-specinfra] ruby-specinfra: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'net-telnet' (= 0.1.1) among 103 total gem(s) (Gem::MissingSpecError) Added tag(s) pending. -- 1027347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027353:
Control: block -1 by 1027347 It is caused by ruby-specinfra's ruby-net-telnet dependency that ruby-serverspec depends. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E signature.asc Description: PGP signature
Processed: Re:
Processing control commands: > block -1 by 1027347 Bug #1027353 [src:ruby-serverspec] ruby-serverspec: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'net-telnet' (= 0.1.1) among 104 total gem(s) (Gem::MissingSpecError) 1027353 was not blocked by any bugs. 1027353 was not blocking any bugs. Added blocking bug(s) of 1027353: 1027347 -- 1027353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1026671 marked as pending in python-mox3
Processing control commands: > tag -1 pending Bug #1026671 [src:python-mox3] python-mox3: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec' Added tag(s) pending. -- 1026671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026671: marked as pending in python-mox3
Control: tag -1 pending Hello, Bug #1026671 in python-mox3 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-mox3/-/commit/d64909ddfb3b88ef37a8013c5e334c794ed0786c * Fix FTBFS (Closes: #1026671): - use-getfullargspec-not-getargspec.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1026671
Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp
Control: tag -1 + pending On Fri, Dec 30, 2022 at 08:08:50PM -0300, Antonio Terceiro wrote: > Control: reassign -1 dhelp > Control: severity -1 serious > Control: retitle: dhelp: depends on module removed from the Ruby stdlib (dbm) > > On Fri, Dec 30, 2022 at 06:09:03PM +0100, Drew Parsons wrote: > > Package: ruby-rubygems > > Version: 3.3.15-1 > > Severity: important > > > > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb from > > ruby-rubygems causes a LoadError which prevents dhelp from updating > > succcessfully (when packages register a doc-base entry). > > > > This affects all other packages (unrelated to ruby) registering with > > doc-base, hence marking Severity: important > > > > The error message (when installing any packing using doc-base, in this > > case python-lmfit-doc) is > > > > Setting up python-lmfit-doc (1.1.0-1) ... > > Processing triggers for doc-base (0.11.1) ... > > Processing 1 added doc-base file... > > Registering documents with dhelp... > > :85:in > > `require': cannot load such file -- dbm (LoadError) > > from > > :85:in > > `require' > > from /usr/lib/ruby/vendor_ruby/dhelp.rb:21:in `' > > from > > :85:in > > `require' > > from > > :85:in > > `require' > > from /usr/sbin/dhelp_parse:32:in `' > > The issue is that dhelp depends on a module that has been removed from > the Ruby standard library (dbm). I imagine the dhelp database is just a > cache and can be rebuilt from scratch on upgrades, so one way to fix > this would be to migrate to a similar module that is available and > probably has a similar enough API, like sdbm (ruby-sdbm). Actually this would invalidate existing databases, creating extra complications. I have just uploaded a ruby-dbm package to NEW, and made the necessary adjustments to the dhelp git repository to use it. I will make an upload when the new package is accepted. signature.asc Description: PGP signature
Processed: Re: Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp
Processing control commands: > tag -1 + pending Bug #1027407 [dhelp] ruby-rubygems: kernel_require.rb LoadError breaks dhelp Added tag(s) pending. -- 1027407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026610: Maybe an issue in the Py 3.11 interpreter?
Hi, As per this commit: https://github.com/python/cpython/commit/92a6abf72e7a8274f96edbb5297119d4ff055be7 it looks like this is an error that should only be a warning, and that looks like problem in the interpreter rather than in Horizon. Downgrading the issue as "important" then, and will skip the tests. Cheers, Thomas Goirand (zigo)
Bug#1026718: lazpaint: FTBFS: /usr/bin/ld.bfd: cannot find -lpangocairo-1.0: No such file or directory
Hello Lucas, Just to check, are you building using debuild or a similar tool, not calling make directly? Normally all needed packages determined by the build tool or are specified in the control file. Regards, -- Juliette aka Johann ELSASS
Processed: golang-golang-x-net: FTBFS in bullseye (text offset 32797 is too large, or nodeBitsTextOffset is too small)
Processing commands for cont...@bugs.debian.org:
> retitle 1020161 golang-golang-x-net: FTBFS in bullseye (text offset 32797 is
> too large, or nodeBitsTextOffset is too small)
Bug #1020161 {Done: Anthony Fok } [src:golang-golang-x-net]
golang-golang-x-net: FTBFS: make: *** [debian/rules:11: binary] Error 25
Changed Bug title to 'golang-golang-x-net: FTBFS in bullseye (text offset 32797
is too large, or nodeBitsTextOffset is too small)' from 'golang-golang-x-net:
FTBFS: make: *** [debian/rules:11: binary] Error 25'.
> reopen 1020161
Bug #1020161 {Done: Anthony Fok } [src:golang-golang-x-net]
golang-golang-x-net: FTBFS in bullseye (text offset 32797 is too large, or
nodeBitsTextOffset is too small)
'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
golang-golang-x-net/1:0.0+git20221012.0b7e1fb+dfsg-1.
> found 1020161 1:0.0+git20210119.5f4716e+dfsg-4
Bug #1020161 [src:golang-golang-x-net] golang-golang-x-net: FTBFS in bullseye
(text offset 32797 is too large, or nodeBitsTextOffset is too small)
Marked as found in versions
golang-golang-x-net/1:0.0+git20210119.5f4716e+dfsg-4.
> found 1020161 1:0.0+git20220728.c7608f3+dfsg-2
Bug #1020161 [src:golang-golang-x-net] golang-golang-x-net: FTBFS in bullseye
(text offset 32797 is too large, or nodeBitsTextOffset is too small)
Ignoring request to alter found versions of bug #1020161 to the same values
previously set
> fixed 1020161 1:0.0+git20221012.0b7e1fb+dfsg-1
Bug #1020161 [src:golang-golang-x-net] golang-golang-x-net: FTBFS in bullseye
(text offset 32797 is too large, or nodeBitsTextOffset is too small)
Marked as fixed in versions
golang-golang-x-net/1:0.0+git20221012.0b7e1fb+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1020161: golang-golang-x-net: FTBFS in bullseye (text offset 32797 is too large, or nodeBitsTextOffset is too small)
retitle 1020161 golang-golang-x-net: FTBFS in bullseye (text offset 32797 is too large, or nodeBitsTextOffset is too small) reopen 1020161 found 1020161 1:0.0+git20210119.5f4716e+dfsg-4 found 1020161 1:0.0+git20220728.c7608f3+dfsg-2 fixed 1020161 1:0.0+git20221012.0b7e1fb+dfsg-1 thanks Hi. I'm reopening this because it's happening in bullseye and packages in stable must build in stable. The build log I get is like the one sent by Lucas (I've put the relevant line in the bug subject). Unfortunately I can'r propose a fix. I tried applying upstream commit 8021a29435afef042814c3ad3b702ff04b240bc7 from Damien Neil to the stable version but the patch does not apply cleanly. Thanks.
Bug#1026664: misspell-fixer: FTBFS: grep: work/R.txt: Permission denied
Could you please send me a few examples? Hi. I've just put my build logs here: https://people.debian.org/~sanvila/build-logs/misspell-fixer/
Bug#1026519: marked as done (termit: FTBFS: termit.h:24:10: fatal error: vte/vte.h: No such file or directory)
Your message dated Fri, 30 Dec 2022 23:09:51 + with message-id and subject line Bug#1026519: fixed in termit 3.1-3 has caused the Debian Bug report #1026519, regarding termit: FTBFS: termit.h:24:10: fatal error: vte/vte.h: 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.) -- 1026519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: termit Version: 3.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 39%] Language: de > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/de.po termit.pot > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<>/obj-x86_64-linux-gnu/po/de.gmo /<>/po/de.po > [ 43%] Language: es > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/es.po termit.pot > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<>/obj-x86_64-linux-gnu/po/es.gmo /<>/po/es.po > [ 47%] Language: fr > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/fr.po termit.pot > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<>/obj-x86_64-linux-gnu/po/fr.gmo /<>/po/fr.po > [ 52%] Language: hu > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/hu.po termit.pot > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<>/obj-x86_64-linux-gnu/po/hu.gmo /<>/po/hu.po > [ 56%] Language: ja > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/ja.po termit.pot > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<>/obj-x86_64-linux-gnu/po/ja.gmo /<>/po/ja.po > [ 60%] Language: ko > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/ko.po termit.pot > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<>/obj-x86_64-linux-gnu/po/ko.gmo /<>/po/ko.po > [ 65%] Language: pl > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/pl.po termit.pot > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o > /<>/obj-x86_64-linux-gnu/po/pl.gmo /<>/po/pl.po > [ 69%] Language: ru > cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgmerge --quiet > --update -s /<>/po/ru.po termit.pot > In file included from /<>/src/termit_core_api.c:20: > /<>/src/termit.h:24:10: fatal error: vte/vte.h: No such file or > directory >24 | #include > | ^~~ > compilation terminated. > make[3]: *** [src/CMakeFiles/termit.dir/build.make:93: > src/CMakeFiles/termit.dir/termit_core_api.c.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/termit_3.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: termit Source-Version: 3.1-3 Done: Marcos Fouces We believe that the bug you reported is fixed in the latest version of termit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcos Fouces (supplier of updated termit 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: Fri, 30 Dec 2022 23:31:00 +0100 Source: termit Architecture: source Version: 3.1-3
Processed (with 1 error): Re: Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp
Processing control commands: > reassign -1 dhelp Bug #1027407 [ruby-rubygems] ruby-rubygems: kernel_require.rb LoadError breaks dhelp Bug reassigned from package 'ruby-rubygems' to 'dhelp'. No longer marked as found in versions rubygems/3.3.15-1. Ignoring request to alter fixed versions of bug #1027407 to the same values previously set > severity -1 serious Bug #1027407 [dhelp] ruby-rubygems: kernel_require.rb LoadError breaks dhelp Severity set to 'serious' from 'important' > retitle: dhelp: depends on module removed from the Ruby stdlib (dbm) Unknown command or malformed arguments to command. -- 1027407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchive for bullseye
Processing commands for cont...@bugs.debian.org:
> unarchive 1020161
Bug #1020161 {Done: Anthony Fok } [src:golang-golang-x-net]
golang-golang-x-net: FTBFS: make: *** [debian/rules:11: binary] Error 25
Unarchived Bug 1020161
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976506: conda-package-handling: FTBFS in bullseye (failing tests)
Forgot the patch. Here it is.
--- a/tests/test_api.py
+++ b/tests/test_api.py
@@ -183,7 +183,7 @@ def
test_create_package_with_uncommon_conditions_captures_all_content(testing_wo
assert stat.st_nlink == 1
-@pytest.mark.skipif(datetime.now() <= datetime(2021, 12, 1), reason="Don't
understand why this doesn't behave. Punt.")
+@pytest.mark.skip(reason="Don't understand why this doesn't behave. Punt.")
def test_secure_refusal_to_extract_abs_paths(testing_workdir):
with tarfile.open('pinkie.tar.bz2', 'w:bz2') as tf:
open('thebrain', 'w').close()
Processed: found 1027355 in 2.17-1, found 1013190 in 0.0.35+git20190103.6a75e98+dfsg.1-3.1 ..., tagging 1027169 ...
Processing commands for cont...@bugs.debian.org:
> found 1027355 2.17-1
Bug #1027355 [src:libapreq2] src:libapreq2: Should not migrate to testing.
Marked as found in versions libapreq2/2.17-1.
> found 1013190 0.0.35+git20190103.6a75e98+dfsg.1-3.1
Bug #1013190 [openems] openems: Migration from vtk7 to vtk9
Marked as found in versions openems/0.0.35+git20190103.6a75e98+dfsg.1-3.1.
> found 1027169 0.6.0+dfsg-5
Bug #1027169 {Done: Nilesh Patra } [src:poretools]
poretools: autopkgtest fail with matplotlib/3.6.2
Marked as found in versions poretools/0.6.0+dfsg-5.
> tags 1027169 + sid bookworm
Bug #1027169 {Done: Nilesh Patra } [src:poretools]
poretools: autopkgtest fail with matplotlib/3.6.2
Added tag(s) sid and bookworm.
> tags 1027112 + experimental
Bug #1027112 [src:bazel-bootstrap] bazel-bootstrap:
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to
'absl::debian3::Mutex::Unlock()'
Added tag(s) experimental.
> tags 1027114 + experimental
Bug #1027114 [src:docker.io] docker.io: FTBFS:
daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined
(type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced)
Added tag(s) experimental.
> tags 1027117 + experimental
Bug #1027117 [src:iem-plugin-suite] iem-plugin-suite: FTBFS: error: ‘class
juce::AudioProcessorPlayer’ has no member named ‘audioDeviceIOCallback’; did
you mean ‘AudioIODeviceCallback’?
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013190
1027112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027112
1027114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027114
1027117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027117
1027169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027169
1027355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026664: misspell-fixer: FTBFS: grep: work/R.txt: Permission denied
Hi, Thank you both. Could you please send me a few examples? With shunit 2.1.8 I could reproduce the issue if I put significant load to my computer in the same time as I run the tests. (Twice failures from around 10 attempts.) Without load, or with shunit 2.1.7, it looks quite stable. Regarding race conditions: So far I could not find any non-sequencial parts in the misspell-fixer's codebase. (Apart from using xargs with -P 4.) But I have not given up... :) Does sbuild do exactly the same as the live test agents? I am just wondering if that is a good enough test or I need something more if I find a fix. I suppose as a worst case, I could just disable the tests. But ideally I would like to fix them. Thank you. Best regards, Lajos On Thu, 29 Dec 2022, Lucas Nussbaum wrote: > Hi, > > Yes, every time. > > Maybe share your build log, and diff it with mine? -- Lajos Veres vla...@gmail.com 07927 460 778
Bug#1026488: marked as done (puppetdb: FTBFS: Cannot access snapshots (https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/) in offline mode and the artifact org.cloj
Your message dated Fri, 30 Dec 2022 17:23:03 -0500 with message-id and subject line Fwd: Fwd: close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026488, regarding puppetdb: FTBFS: Cannot access snapshots (https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetdb Version: 7.11.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > puppetserver test dependency unconfigured (ignoring) > Wrote /<>/debian/pom.xml > lein jar > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > puppetserver test dependency unconfigured (ignoring) > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access releases > (https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-releases__local/) > in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been > downloaded from it before. > Cannot access snapshots > (https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/) > in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been > downloaded from it before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/puppetdb_7.11.2-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, Thus bug has been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1026540: marked as done (trapperkeeper-scheduler-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been down
Your message dated Fri, 30 Dec 2022 17:15:14 -0500 with message-id and subject line Fwd: close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026540, regarding trapperkeeper-scheduler-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-scheduler-clojure Version: 1.1.3-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Wrote /<>/debian/pom.xml > lein i18n make > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Running 'make i18n' > lein jar > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/trapperkeeper-scheduler-clojure_1.1.3-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, These bugs have been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1026486: marked as done (leiningen-clojure: FTBFS: Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the
Your message dated Fri, 30 Dec 2022 17:15:14 -0500
with message-id
and subject line Fwd: close clojure bugs for missing 1.10.x
has caused the Debian Bug report #1026486,
regarding leiningen-clojure: FTBFS: Caused by:
org.eclipse.aether.transfer.ArtifactNotFoundException: Cannot access central
(https://repo1.maven.org/maven2/) in offline mode and the artifact
org.clojure:clojure:jar:1.10.x has not been downloaded from it before.
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.)
--
1026486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leiningen-clojure
Version: 2.9.1-9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd leiningen-core && lein bootstrap
> Leiningen's classpath: :/usr/share/java/leiningen-2.9.1.jar
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were
> deprecated in JDK 13 and will likely be removed in a future release.
> Applying task [with-profile base do install, classpath .lein-bootstrap] to []
> Applying task do to (install, classpath .lein-bootstrap)
> Applying task install to []
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and
> the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it
> before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the
> artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it
> before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and
> the artifact nrepl:nrepl:jar:0.9.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the
> artifact nrepl:nrepl:jar:0.9.0 has not been downloaded from it before.
> This could be due to a typo in :dependencies, file system permissions, or
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> Error encountered performing task 'do' with profile(s): 'base'
> clojure.lang.ExceptionInfo: Could not resolve dependencies {:suppress-msg
> true, :exit-code 1}
> at
> leiningen.core.classpath$get_dependencies_STAR_.invokeStatic(classpath.clj:312)
> at
> leiningen.core.classpath$get_dependencies_STAR_.invoke(classpath.clj:266)
> at clojure.lang.AFn.applyToHelper(AFn.java:165)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invokeStatic(core.clj:667)
> at clojure.core$memoize$fn__6894.doInvoke(core.clj:6342)
> at clojure.lang.RestFn.invoke(RestFn.java:457)
> at
> leiningen.core.classpath$get_dependencies$fn__6448.invoke(classpath.clj:333)
> at
> leiningen.core.classpath$get_dependencies.invokeStatic(classpath.clj:331)
> at leiningen.core.classpath$get_dependencies.doInvoke(classpath.clj:325)
> at clojure.lang.RestFn.invoke(RestFn.java:445)
> at clojure.lang.AFn.applyToHelper(AFn.java:160)
> at clojure.lang.RestFn.applyTo(RestFn.java:132)
> at clojure.core$apply.invokeStatic(core.clj:673)
> at clojure.core$apply.invoke(core.clj:662)
> at
> leiningen.core.classpath$resolve_managed_dependencies.invokeStatic(classpath.clj:444)
> at
> leiningen.core.classpath$resolve_managed_dependencies.doInvoke(classpath.clj:431)
> at clojure.lang.RestFn.invoke(RestFn.java:445)
> at leiningen.core.eval$prep.invokeStatic(eval.clj:85)
> at leiningen.core.eval$prep.invoke(eval.clj:73)
> at leiningen.jar$build_jar.invokeStatic(jar.clj:286)
> at leiningen.jar$build_jar.invoke(jar.clj:283)
> at leiningen.jar$main_jar.invokeStatic(jar.clj:295)
> at leiningen.jar$main_jar.invoke(jar.clj:291)
> at leiningen.jar$jar.invokeStatic(jar.clj:346)
> at leiningen.jar$jar.invoke(jar.clj:328)
> at leiningen.jar$jar.invokeStatic(jar.clj:348)
> at leiningen.jar$jar.invoke(jar.clj:328)
> at leiningen.install$install.invokeStatic(install.clj:21)
> at leiningen.install$install.invoke(install.clj:12)
> at clojure.lang.AFn.applyToHelper(AFn.java:154)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.lang.Var.applyTo(Var.java:705)
> at clojure.core$apply.invokeStatic(core.clj:669)
> at clojure.core$apply.invoke(core.clj:662)
> at
Bug#1026522: marked as done (core-async-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from i
Your message dated Fri, 30 Dec 2022 17:15:14 -0500 with message-id and subject line Fwd: close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026522, regarding core-async-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: core-async-clojure Version: 1.5.648-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein jar > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/core-async-clojure_1.5.648-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, These bugs have been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1026749: marked as done (clj-digest-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from i
Your message dated Fri, 30 Dec 2022 17:10:26 -0500 with message-id and subject line close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026749, regarding clj-digest-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clj-digest-clojure Version: 1.4.9+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Wrote /<>/debian/pom.xml > lein jar > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:20: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/clj-digest-clojure_1.4.9+dfsg-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, These bugs have been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1026641: marked as done (clj-time-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it
Your message dated Fri, 30 Dec 2022 17:10:26 -0500 with message-id and subject line close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026641, regarding clj-time-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clj-time-clojure Version: 0.15.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Wrote /<>/debian/pom.xml > lein jar > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/clj-time-clojure_0.15.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, These bugs have been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1027394: marked as done (librdf-linkeddata-perl: autopkgtest regression: Can't do script: No such file or directory)
Your message dated Fri, 30 Dec 2022 23:10:21 +0100 with message-id and subject line Re: librdf-linkeddata-perl: autopkgtest regression: Can't do script: No such file or directory has caused the Debian Bug report #1027394, regarding librdf-linkeddata-perl: autopkgtest regression: Can't do script: 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.) -- 1027394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librdf-linkeddata-perl Version: 1.940-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of librdf-linkeddata-perl the autopkgtest of librdf-linkeddata-perl fails in testing when that autopkgtest is run with the binary packages of librdf-linkeddata-perl from unstable. It passes when run with only packages from testing. In tabular form: passfail librdf-linkeddata-perl from testing1.940-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=librdf-linkeddata-perl https://ci.debian.net/data/autopkgtest/testing/amd64/libr/librdf-linkeddata-perl/29791982/log.gz t/19_config_file.t skipped: (no reason given) Bailout called. Further testing stopped: Can't do script: No such file or directory t/20-psgi-basic.t . Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run Test Summary Report --- t/19_config_file.t (Wstat: 65280 (exited 255) Tests: 0 Failed: 0) Non-zero exit status: 255 t/20-psgi-basic.t (Wstat: 65280 (exited 255) Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output Files=9, Tests=226, 8 wallclock secs ( 0.10 usr 0.00 sys + 8.32 cusr 0.52 csys = 8.94 CPU) Result: FAIL FAILED--Further testing stopped: Can't do script: No such file or directory autopkgtest [16:34:35]: test autodep8-perl-build-deps OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1.940-3 On Fri, 30 Dec 2022 21:58:23 +0100, Paul Gevers wrote: > t/19_config_file.t skipped: (no reason given) > Bailout called. Further testing stopped: Can't do script: No such file or > directory > t/20-psgi-basic.t . Dubious, test returned 255 (wstat 65280, 0xff00) > No subtests run > Test Summary Report > --- > t/19_config_file.t (Wstat: 65280 (exited 255) Tests: 0 Failed: 0) > Non-zero exit status: 255 > t/20-psgi-basic.t (Wstat: 65280 (exited 255) Tests: 0 Failed: 0) > Non-zero exit status: 255 > Parse errors: No plan found in TAP output > Files=9, Tests=226, 8 wallclock secs ( 0.10 usr 0.00 sys + 8.32 cusr 0.52 > csys = 8.94 CPU) > Result: FAIL > FAILED--Further testing stopped: Can't do script: No such file or directory > autopkgtest [16:34:35]: test autodep8-perl-build-deps This was fixed earlier today in Jonas' upload of 1.940-3, hence closing the bug. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature --- End Message ---
Bug#1026727: marked as done (core-match-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from i
Your message dated Fri, 30 Dec 2022 17:10:26 -0500 with message-id and subject line close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026727, regarding core-match-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: core-match-clojure Version: 1.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein jar > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/core-match-clojure_1.0.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, These bugs have been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1026708: marked as done (beckon-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it be
Your message dated Fri, 30 Dec 2022 17:10:26 -0500 with message-id and subject line close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026708, regarding beckon-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: beckon-clojure Version: 0.1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Wrote /<>/debian/pom.xml > lein jar > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/beckon-clojure_0.1.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, These bugs have been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1026662: marked as done (bidi-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it befo
Your message dated Fri, 30 Dec 2022 17:10:26 -0500 with message-id and subject line close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026662, regarding bidi-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. 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.) -- 1026662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bidi-clojure Version: 2.1.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein test > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact nrepl:nrepl:jar:0.9.0 has not been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact nrepl:nrepl:jar:0.9.0 has not been downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/bidi-clojure_2.1.6-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, These bugs have been fixed with the upload of clojure 1.11.1-2. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1026637: marked as done (core-specs-alpha-clojure: FTBFS: [ERROR] Failed to execute goal on project core.specs.alpha: Could not resolve dependencies for project org.clojure:core.specs.alpha:jar:0.
Your message dated Fri, 30 Dec 2022 17:10:26 -0500 with message-id and subject line close clojure bugs for missing 1.10.x has caused the Debian Bug report #1026637, regarding core-specs-alpha-clojure: FTBFS: [ERROR] Failed to execute goal on project core.specs.alpha: Could not resolve dependencies for project org.clojure:core.specs.alpha:jar:0.2.56: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it before. -> [Help 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.) -- 1026637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: core-specs-alpha-clojure Version: 0.2.56-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibcore-specs-alpha-clojure --debian-build > --keep-pom-version --maven-repo=/<>/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [0m[0m[INFO] Scanning for projects... > [INFO] > [INFO] < org.clojure:core.specs.alpha > > > [INFO] Building core.specs.alpha 0.2.56 > [INFO] [ jar > ]- > [WARNING] The artifact > org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to > org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0 > [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 > has been relocated to org.apache.maven.plugins:maven-compiler-plugin:jar:3.8.1 > [WARNING] The artifact > org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated > to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3 > [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has > been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0 > [WARNING] The POM for org.clojure:clojure:jar:1.10.x is missing, no > dependency information available > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.170 s > [INFO] Finished at: 2022-12-20T09:45:11Z > [INFO] > > [ERROR] Failed to execute goal on project core.specs.alpha: Could not resolve > dependencies for project org.clojure:core.specs.alpha:jar:0.2.56: Cannot > access central (https://repo.maven.apache.org/maven2) in offline mode and the > artifact org.clojure:clojure:jar:1.10.x has not been downloaded from it > before. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [0m[0mdh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify > -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 > make: *** [debian/rules:4: build] Error 25 The full build log is available from:
Processed: conda-package-handling: FTBFS in bullseye (failing tests)
Processing commands for cont...@bugs.debian.org:
> reopen 976506
Bug #976506 {Done: Nilesh Patra }
[src:conda-package-handling] conda-package-handling: FTBFS on arm64:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
'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 conda-package-handling/1.7.2-2.
> found 976506 1.7.2-1
Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS on
arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.9 returned exit code 13
Ignoring request to alter found versions of bug #976506 to the same values
previously set
> found 976506 1.7.2-2
Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS on
arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.9 returned exit code 13
Marked as found in versions conda-package-handling/1.7.2-2.
> retitle 976506 conda-package-handling: FTBFS in bullseye (failing tests)
Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS on
arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.9 returned exit code 13
Changed Bug title to 'conda-package-handling: FTBFS in bullseye (failing
tests)' from 'conda-package-handling: FTBFS on arm64: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13'.
> tags 976506 + patch
Bug #976506 [src:conda-package-handling] conda-package-handling: FTBFS in
bullseye (failing tests)
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976506: conda-package-handling: FTBFS in bullseye (failing tests)
reopen 976506 found 976506 1.7.2-1 found 976506 1.7.2-2 retitle 976506 conda-package-handling: FTBFS in bullseye (failing tests) tags 976506 + patch thanks Hi. The test suite had a time-bomb, and version 1.7.2-2 just extended the time of the bomb, but not deactivated it. Now this package FTBFS in bullseye all the time in bullseye: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/conda-package-handling.html (and also in my own autobuilders). I attach a patch in which the failing test is properly deactivated for good. (The patch is to be applied over version 1.7.2-2, but you might want to merge it with debian/patches/extend-test-datetime-to-dec-2021.patch instead). Thanks.
Bug#1027403: metalfinder: flaky autopkgtest (host dependent?): tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' is not a valid FLAC file
Source: metalfinder
Version: 2.1.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails. The failures seem related on the host that runs
the test. ci-worker13 is a beefy machine [1], while the other amd64
workers are much more moderate [2]. It's also flaky on ppc64el, but
those hosts are (or should be) all the same.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Paul
[1] https://metal.equinix.com/product/servers/m3-large/
[2] https://aws.amazon.com/ec2/instance-types/m5/
https://ci.debian.net/data/autopkgtest/testing/amd64/m/metalfinder/29786825/log.gz
=== FAILURES
===
_ test_issue28
_
cachedir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/cache')
musicdir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/music')
caplog = <_pytest.logging.LogCaptureFixture object at 0x7f705a5efad0>
def test_issue28(cachedir, musicdir, caplog):
"""Test metalfinder continues running if a file passed through
get_artist()
raises an exception"""
caplog.set_level(logging.WARNING)
for filename in ['no_header.flac', 'no_artist.flac',
'arch_enemy.flac']:
_ = move_testfile(filename, musicdir)
artist_list = mfs.scan_wrapper(str(musicdir), str(cachedir))
assert artist_list == {'Arch Enemy'}
> assert NO_ARTIST_ERROR in caplog.records[0].args[1]
E assert ": 'artist'" in "'mutagen.flac.FLACNoHeaderError'>:
'/tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' is
not a valid FLAC file"
tests/test_scan.py:170: AssertionError
https://ci.debian.net/data/autopkgtest/testing/ppc64el/m/metalfinder/29794715/log.gz
=== FAILURES
===
_ test_issue28
_
cachedir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/cache')
musicdir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/music')
caplog = <_pytest.logging.LogCaptureFixture object at 0x7fff8e0ec4d0>
def test_issue28(cachedir, musicdir, caplog):
"""Test metalfinder continues running if a file passed through
get_artist()
raises an exception"""
caplog.set_level(logging.WARNING)
for filename in ['no_header.flac', 'no_artist.flac',
'arch_enemy.flac']:
_ = move_testfile(filename, musicdir)
artist_list = mfs.scan_wrapper(str(musicdir), str(cachedir))
assert artist_list == {'Arch Enemy'}
> assert NO_ARTIST_ERROR in caplog.records[0].args[1]
E assert ": 'artist'" in "'mutagen.flac.FLACNoHeaderError'>:
'/tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' is
not a valid FLAC file"
tests/test_scan.py:170: AssertionError
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1027402: overwrites file from libsundials-nvecparallel-mpi4 without declaring proper relationship
Package: libsundials-nvecparallel-mpi6 Version: 6.4.1+dfsg1-2 Severity: serious Dear Maintainer, When upgrading, I got the following dpkg error: Preparing to unpack .../libsundials-nvecparallel-mpi6_6.4.1+dfsg1-2+b1_amd64.deb ... Unpacking libsundials-nvecparallel-mpi6:amd64 (6.4.1+dfsg1-2+b1) ... dpkg: error processing archive /var/cache/apt/archives/libsundials-nvecparallel-mpi6_6.4.1+dfsg1-2+b1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libsundials_fnvecmpimanyvector_mod.so.6.4.1', which is also in package libsundials-nvecparallel-mpi4:amd64 6.4.1+dfsg1-1 Errors were encountered while processing: /var/cache/apt/archives/libsundials-nvecparallel-mpi6_6.4.1+dfsg1-2+b1_amd64.deb I guess a Breaks+Replaces relationship is missing. Thanks for your work, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org
Bug#1027398: gavodachs: autopkgtest needs update for new version of python-cryptography: fails to install
Source: gavodachs Version: 2.7+dfsg-1 Severity: serious X-Debbugs-CC: python-cryptogra...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python-cryptography Dear maintainer(s), With a recent upload of python-cryptography the autopkgtest of gavodachs fails in testing when that autopkgtest is run with the binary packages of python-cryptography from unstable. It passes when run with only packages from testing. In tabular form: passfail python-cryptographyfrom testing38.0.4-1 gavodachs from testing2.7+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. gavodachs2-server fails to install. Currently this regression is blocking the migration of python-cryptography to testing [1]. Of course, python-cryptography shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in python-cryptography 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 python-cryptography 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=python-cryptography https://ci.debian.net/data/autopkgtest/testing/amd64/g/gavodachs/29784808/log.gz Setting up python3-docutils (0.17.1+dfsg-3) ... Setting up python3-gavo-utils (2.7+dfsg-1) ... Setting up python3-gavo-stc (2.7+dfsg-1) ... Setting up python3-gavo-votable (2.7+dfsg-1) ... Setting up python3-gavo (2.7+dfsg-1) ... Setting up gavodachs2-server (2.7+dfsg-1) ... Created symlink /etc/systemd/system/multi-user.target.wants/dachs.service → /lib/systemd/system/dachs.service. Adding group `gavo' (GID 1001) ... Done. adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory Adding system user `gavo' (UID 103) ... Adding new user `gavo' (UID 103) with group `gavo' ... Not creating home directory `/nonexistent'. Adding user `dachsroot' ... Adding new user `dachsroot' (1002) with group `gavo (1001)' ... Creating home directory `/home/dachsroot' ... Copying files from `/etc/skel' ... Adding new user `dachsroot' to supplemental / extra groups `users' ... Adding user `dachsroot' to group `users' ... *** Error: Oops. Unhandled exception AttributeError. Exception payload: module 'lib' has no attribute 'SSL_CTX_set_ecdh_auto' dpkg: error processing package gavodachs2-server (--configure): installed gavodachs2-server package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of autopkgtest-satdep: autopkgtest-satdep depends on gavodachs2-server; however: Package gavodachs2-server is not configured yet. dpkg: error processing package autopkgtest-satdep (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: gavodachs2-server autopkgtest-satdep E: Sub-process /usr/bin/dpkg returned an error code (1) OpenPGP_signature Description: OpenPGP digital signature
Processed: gavodachs: autopkgtest needs update for new version of python-cryptography: fails to install
Processing control commands: > affects -1 src:python-cryptography Bug #1027398 [src:gavodachs] gavodachs: autopkgtest needs update for new version of python-cryptography: fails to install Added indication that 1027398 affects src:python-cryptography -- 1027398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019824: marked as done (3depict: Please transition to wxwidgets3.2)
Your message dated Fri, 30 Dec 2022 21:04:28 + with message-id and subject line Bug#1019824: fixed in 3depict 0.0.23-2 has caused the Debian Bug report #1019824, regarding 3depict: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: 3depict Severity: normal Control: block 1019416 by -1 Hi, Please transition 3depict from wxwidgets3.0 to wxwidgets3.2. wxWidgets 3.2 (a new API/ABI stable release) has been released a few months ago and is now packaged in unstable as wxwidgets3.2. Upstream has stopped supporting wxWidgets 3.0, so the Debian wx team would like to migrate all wx package users to wxwidgets3.2 for bullseye, with the plan to remove wxwidgets3.0 before release. For most packages, the transition should be as simple as changing Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some packages may require small patches; I'm happy to help with those (and I have some already from working on this transition in Fedora already). Thanks, Scott --- End Message --- --- Begin Message --- Source: 3depict Source-Version: 0.0.23-2 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of 3depict, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated 3depict 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: Fri, 30 Dec 2022 15:14:32 -0500 Source: 3depict Architecture: source Version: 0.0.23-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Scott Talbert Closes: 1019824 Changes: 3depict (0.0.23-2) unstable; urgency=medium . * Team upload. * Transition to wxWidgets 3.2 (Closes: #1019824) Checksums-Sha1: 187c54c607ecc6d6e28956f8a43ff77c70ede2df 2125 3depict_0.0.23-2.dsc 86b9fa4dfb0554325b67ec671e1b6255d4233ecc 18956 3depict_0.0.23-2.debian.tar.xz ad79c9def11fe7b82f826ad6d09fff36fa769ae8 15289 3depict_0.0.23-2_amd64.buildinfo Checksums-Sha256: df8a32ee7cf344ae4e9e0f71ab3bad536f0602f600e8723b350a5bbf1a6b6ecb 2125 3depict_0.0.23-2.dsc eda0ef2f482a61e0ec2a70f800fddb1b70bc4d8fa1aae06592db60af44c38fe6 18956 3depict_0.0.23-2.debian.tar.xz ab104b3d2462d10faab1afb47a9fd403587036848c217e4fed344834d3e5f8a0 15289 3depict_0.0.23-2_amd64.buildinfo Files: dc1d98cce0c3b67062cb42a5e8a698bf 2125 science optional 3depict_0.0.23-2.dsc c41550ae71e29d5dc4e29144d1cd36ef 18956 science optional 3depict_0.0.23-2.debian.tar.xz 4bf8b002990b24a8a2f648997817609c 15289 science optional 3depict_0.0.23-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmOvSSgPHHN3dEB0ZWNo aWUubmV0AAoJEFPVvGS1I3iiW7gP/ApsZ8LS1gIgKhD32N3LbVY4c/vrEQEOWNNa YyT+JkJxX+HskizLMsvL9ZA2RKUnCjWfdAj4rK4ZfmSgZAgEbEgwroT1YEpN7v/Z kq3d1pMDQwkHmJZYr7yY4rKg6Gu5x2COzHkw5S5VzezQ8YVDA6Uft4tj1TZdOdbz OYgzNQ6zSUAxwf/pk+WuLnSoNAkJWb2hpilk6IckljlWf1Wb1flTx/cl/WDY5vvC f2fZdsb/nWNSiz4V4oRBoBojMt6WDuMgooNuCOUsYZRfR2Pvw6rrBDnyDNnKX1RV FesRmHNSGnzBh5wkZfOc9C7eisn4UCI2LQCcQz5Zp6cmw+bcjx5qI1r8JsZydyIX vW9fG9z2YBk2hEu0HGFda/q+7lfchYprC2v0iALKjDuHtVpEx8V8wQxgGcwl2epH dex+zJ2h7wXfFsCaFuJvi9mkdhHVTsSN1UXwezBW+qFrnj71QSjCI+zXF1dNLPup P0+Qw0y2A8al6jyCDzJITanBc5ff+uxX+qi0gnnNzl+4wrk+66nMjbhLRHumsfYo AhTkZ9sWIY+AVkjHlL0X1bxjXD6+jXIl1n5kuQ3CPRgWFMeBZMEmxWsnMDFOLnba a1a7orbeR/bqo4XK56sWOl+PTzxQHY/tGu26LYCvRP/iBSAgA5oCk6faW8RAqF/O hn27EJnS =GMat -END PGP SIGNATURE End Message ---
Bug#1027397: ognibuild: autopkgtest regression: No module named 'ognibuild.tests'
Source: ognibuild Version: 0.0.16-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of ognibuild the autopkgtest of ognibuild fails in testing when that autopkgtest is run with the binary packages of ognibuild from unstable. It passes when run with only packages from testing. In tabular form: passfail ognibuild from testing0.0.16-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=ognibuild https://ci.debian.net/data/autopkgtest/testing/amd64/o/ognibuild/29784768/log.gz E == ERROR: tests (unittest.loader._FailedTest) -- ImportError: Failed to import test module: tests Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) ModuleNotFoundError: No module named 'ognibuild.tests' -- Ran 1 test in 0.000s FAILED (errors=1) autopkgtest [03:19:17]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Processed: Unarchive for bullseye, where it's happening again
Processing commands for cont...@bugs.debian.org:
> unarchive 976506
Bug #976506 {Done: Nilesh Patra }
[src:conda-package-handling] conda-package-handling: FTBFS on arm64:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Unarchived Bug 976506
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: astropy breaks spectral-cube autopkgtest: AssertionError
Processing control commands: > found -1 astropy/5.2-1 Bug #1027396 [src:astropy, src:spectral-cube] astropy breaks spectral-cube autopkgtest: AssertionError Marked as found in versions astropy/5.2-1. > found -1 spectral-cube/0.6.0-1 Bug #1027396 [src:astropy, src:spectral-cube] astropy breaks spectral-cube autopkgtest: AssertionError Marked as found in versions spectral-cube/0.6.0-1. -- 1027396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027396: astropy breaks spectral-cube autopkgtest: AssertionError
Source: astropy, spectral-cube
Control: found -1 astropy/5.2-1
Control: found -1 spectral-cube/0.6.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of astropy the autopkgtest of spectral-cube fails
in testing when that autopkgtest is run with the binary packages of
astropy from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
astropyfrom testing5.2-1
spectral-cube from testing0.6.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 astropy 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=astropy
https://ci.debian.net/data/autopkgtest/testing/amd64/s/spectral-cube/29791507/log.gz
=== FAILURES
===
_ test_spectral_smooth[False]
__
data_522_delta =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_spectral_smooth_False_0/522_delta.fits')
use_dask = False
def test_spectral_smooth(data_522_delta, use_dask):
cube, data = cube_and_raw(data_522_delta, use_dask=use_dask)
result =
cube.spectral_smooth(kernel=convolution.Gaussian1DKernel(1.0),
use_memmap=False)
> np.testing.assert_almost_equal(result[:,0,0].value,
convolution.Gaussian1DKernel(1.0,
x_size=5).array,
4)
E AssertionError: E Arrays are not almost equal to 4 decimals
E E Mismatched elements: 5 / 5 (100%)
E Max absolute difference: 0.00367648
E Max relative difference: 0.00913138
Ex: array([0.054 , 0.242 , 0.3989, 0.242 , 0.054 ])
Ey: array([0.0545, 0.2442, 0.4026, 0.2442, 0.0545])
/usr/lib/python3/dist-packages/spectral_cube/tests/test_regrid.py:131:
AssertionError
__ test_spectral_smooth[True]
__
data_522_delta =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_spectral_smooth_True_0/522_delta.fits')
use_dask = True
def test_spectral_smooth(data_522_delta, use_dask):
cube, data = cube_and_raw(data_522_delta, use_dask=use_dask)
result =
cube.spectral_smooth(kernel=convolution.Gaussian1DKernel(1.0),
use_memmap=False)
> np.testing.assert_almost_equal(result[:,0,0].value,
convolution.Gaussian1DKernel(1.0,
x_size=5).array,
4)
E AssertionError: E Arrays are not almost equal to 4 decimals
E E Mismatched elements: 5 / 5 (100%)
E Max absolute difference: 0.00367648
E Max relative difference: 0.00913138
Ex: array([0.054 , 0.242 , 0.3989, 0.242 , 0.054 ])
Ey: array([0.0545, 0.2442, 0.4026, 0.2442, 0.0545])
/usr/lib/python3/dist-packages/spectral_cube/tests/test_regrid.py:131:
AssertionError
_ test_spectral_smooth_4cores
__
data_522_delta =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_spectral_smooth_4cores0/522_delta.fits')
@pytest.mark.skipif('WINDOWS')
def test_spectral_smooth_4cores(data_522_delta):
pytest.importorskip('joblib')
cube, data = cube_and_raw(data_522_delta, use_dask=False)
result =
cube.spectral_smooth(kernel=convolution.Gaussian1DKernel(1.0),
num_cores=4, use_memmap=True)
> np.testing.assert_almost_equal(result[:,0,0].value,
convolution.Gaussian1DKernel(1.0,
x_size=5).array,
4)
E AssertionError: E Arrays are not almost equal to 4 decimals
E E Mismatched elements: 5 / 5 (100%)
E Max absolute difference: 0.00367648
E Max relative difference: 0.00913138
Ex: array([0.054 , 0.242 , 0.3989, 0.242 , 0.054 ])
Ey: array([0.0545, 0.2442, 0.4026, 0.2442, 0.0545])
/usr/lib/python3/dist-packages/spectral_cube/tests/test_regrid.py:163:
AssertionError
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1027395: astropy breaks imexam autopkgtest: AssertionError
Source: astropy, imexam Control: found -1 astropy/5.2-1 Control: found -1 imexam/0.9.1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of astropy the autopkgtest of imexam fails in testing when that autopkgtest is run with the binary packages of astropy from unstable. It passes when run with only packages from testing. In tabular form: passfail astropyfrom testing5.2-1 imexam from testing0.9.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of astropy 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=astropy https://ci.debian.net/data/autopkgtest/testing/amd64/i/imexam/29791506/log.gz === FAILURES === __ test_gauss_center ___ def test_gauss_center(): """Check the gaussian center fitting.""" from astropy.convolution import Gaussian2DKernel # This creates a 2D normalized gaussian kernal with # a set amplitude. Guess off-center amp = 0.0015915494309189533 size = 81.0 sigma = 10.0 gaussian_2D_kernel = Gaussian2DKernel(sigma, x_size=size, y_size=size) plots = Imexamine() plots.set_data(gaussian_2D_kernel.array) a, xx, yy, xs, ys = plots.gauss_center(37, 37) > assert_allclose(amp, a, 1e-6) E AssertionError: E Not equal to tolerance rtol=1e-06, atol=0 E E Mismatched elements: 1 / 1 (100%) E Max absolute difference: 1.61872075e-07 E Max relative difference: 0.0001017 Ex: array(0.001592) Ey: array(0.001592) /usr/lib/python3/dist-packages/imexam/tests/test_imexamine.py:128: AssertionError - Captured stdout call - xc=40. yc=40. -- Captured log call --- INFO imexam.util:imexamine.py:1015 xc=40. yc=40. OpenPGP_signature Description: OpenPGP digital signature
Processed: astropy breaks imexam autopkgtest: AssertionError
Processing control commands: > found -1 astropy/5.2-1 Bug #1027395 [src:astropy, src:imexam] astropy breaks imexam autopkgtest: AssertionError Marked as found in versions astropy/5.2-1. > found -1 imexam/0.9.1-2 Bug #1027395 [src:astropy, src:imexam] astropy breaks imexam autopkgtest: AssertionError Marked as found in versions imexam/0.9.1-2. -- 1027395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027394: librdf-linkeddata-perl: autopkgtest regression: Can't do script: No such file or directory
Source: librdf-linkeddata-perl Version: 1.940-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of librdf-linkeddata-perl the autopkgtest of librdf-linkeddata-perl fails in testing when that autopkgtest is run with the binary packages of librdf-linkeddata-perl from unstable. It passes when run with only packages from testing. In tabular form: passfail librdf-linkeddata-perl from testing1.940-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=librdf-linkeddata-perl https://ci.debian.net/data/autopkgtest/testing/amd64/libr/librdf-linkeddata-perl/29791982/log.gz t/19_config_file.t skipped: (no reason given) Bailout called. Further testing stopped: Can't do script: No such file or directory t/20-psgi-basic.t . Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run Test Summary Report --- t/19_config_file.t (Wstat: 65280 (exited 255) Tests: 0 Failed: 0) Non-zero exit status: 255 t/20-psgi-basic.t (Wstat: 65280 (exited 255) Tests: 0 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output Files=9, Tests=226, 8 wallclock secs ( 0.10 usr 0.00 sys + 8.32 cusr 0.52 csys = 8.94 CPU) Result: FAIL FAILED--Further testing stopped: Can't do script: No such file or directory autopkgtest [16:34:35]: test autodep8-perl-build-deps OpenPGP_signature Description: OpenPGP digital signature
Bug#1027393: test-chuck-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Source: test-chuck-clojure
Version: 0.2.13-2
Severity: serious
X-Debbugs-CC: cloj...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:clojure
Dear maintainer(s),
With a recent upload of clojure the autopkgtest of test-chuck-clojure
fails in testing when that autopkgtest is run with the binary packages
of clojure from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
clojurefrom testing1.11.1-2
test-chuck-clojure from testing0.2.13-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. The test
passes but there's a warning on stderr. autopkgtest fails on that unless
the allow-stderr restriction is enabled.
Currently this regression is blocking the migration of clojure to
testing [1]. Of course, clojure shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
clojure 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 clojure 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=clojure
https://ci.debian.net/data/autopkgtest/testing/amd64/t/test-chuck-clojure/29779593/log.gz
#'user/all-tests
WARNING: abs already refers to: #'clojure.core/abs in namespace:
clojure.test.check.generators, being replaced by:
#'clojure.test.check.generators/abs
(nil nil nil nil nil nil nil nil)
Testing com.gfredericks.test.chuck.generators-test
{:result true, :num-tests 500, :seed 1672337569924, :time-elapsed-ms 48,
:test-var "bounded-int-generates-bounded-ints"}
{:result true, :num-tests 100, :seed 1672337569981, :time-elapsed-ms
196, :test-var "sub-map-spec"}
{:result true, :num-tests 100, :seed 1672337570179, :time-elapsed-ms 5,
:test-var "double-generates-doubles"}
{:result true, :num-tests 100, :seed 1672337570185, :time-elapsed-ms 10,
:test-var "subsequence-spec"}
{:result true, :num-tests 100, :seed 1672337570196, :time-elapsed-ms 6,
:test-var "parallel-as-second-clause-spec"}
{:result true, :num-tests 100, :seed 1672337570203, :time-elapsed-ms 3,
:test-var "for-works-correctly"}
{:result true, :num-tests 100, :seed 1672337570207, :time-elapsed-ms 12,
:test-var "complex-for-works-correctly"}
{:result true, :num-tests 100, :seed 1672337570220, :time-elapsed-ms 0,
:test-var "for-accepts-empty-bindings"}
{:result true, :num-tests 10, :seed 1672337570221, :time-elapsed-ms
1229, :test-var "datetime-spec"}
{:result true, :num-tests 100, :seed 1672337571452, :time-elapsed-ms 1,
:test-var "parallel-usage-spec"}
{:result true, :num-tests 100, :seed 1672337571453, :time-elapsed-ms 4,
:test-var "destructuring-usage-spec"}
{:result true, :num-tests 100, :seed 1672337571457, :time-elapsed-ms 3,
:test-var "subset-in-set"}
{:result true, :num-tests 100, :seed 1672337571461, :time-elapsed-ms
356, :test-var "bounded-recursive-gen-spec"}
Testing com.gfredericks.test.chuck.regexes-test
{:result true, :num-tests 1000, :seed 1672337571953, :time-elapsed-ms
7825, :test-var "generator-spec"}
{:result true, :num-tests 100, :seed 1672337579779, :time-elapsed-ms
176, :test-var "parses-regexes"}
{:result true, :num-tests 1000, :seed 1672337579955, :time-elapsed-ms
6200, :test-var "parser-spec"}
{:result true, :num-tests 1000, :seed 1672337586156, :time-elapsed-ms
822, :test-var "generator-regression-spec"}
Testing com.gfredericks.test.chuck.clojure-test-output-test
Testing com.gfredericks.test.chuck.regexes.charsets-test
{:result true, :num-tests 100, :seed 1672337587094, :time-elapsed-ms 26,
:test-var "union-is-commutative"}
Testing com.gfredericks.test.chuck.clojure-test
Testing com.gfredericks.test.chuck.clojure-test-test
Testing com.gfredericks.test.chuck.properties-test
{:result true, :num-tests 10, :seed 1672337587143, :time-elapsed-ms 0,
:test-var "for-all-destructured-args-work-correctly"}
{:result true, :num-tests 100, :seed 1672337587143, :time-elapsed-ms 1,
:test-var "allows-empty-bindings"}
Testing com.gfredericks.test.chuck.exception-handling-test
Ran 32 tests containing 120 assertions.
0 failures, 0 errors.
autopkgtest [18:13:07]: test upstream
OpenPGP_signature
Description: OpenPGP digital signature
Processed: test-chuck-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Processing control commands: > affects -1 src:clojure Bug #1027393 [src:test-chuck-clojure] test-chuck-clojure: autopkgtest needs update for new version of clojure: warning on stderr Added indication that 1027393 affects src:clojure -- 1027393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027392: test-check-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Source: test-check-clojure
Version: 1.1.0-1
Severity: serious
X-Debbugs-CC: cloj...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:clojure
Dear maintainer(s),
With a recent upload of clojure the autopkgtest of test-check-clojure
fails in testing when that autopkgtest is run with the binary packages
of clojure from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
clojurefrom testing1.11.1-2
test-check-clojure from testing1.1.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. There's a
warning on stderr which is interpreted as failure by autopkgtest. You
can add the allow-stderr restriction if you can't/won't fix the
underlying issue.
Currently this regression is blocking the migration of clojure to
testing [1]. Of course, clojure shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
clojure 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 clojure 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=clojure
https://ci.debian.net/data/autopkgtest/testing/amd64/t/test-check-clojure/29779592/log.gz
WARNING: abs already refers to: #'clojure.core/abs in namespace:
clojure.test.check.generators, being replaced by:
#'clojure.test.check.generators/abs
WARNING: infinite? already refers to: #'clojure.core/infinite? in
namespace: clojure.test.check.test, being replaced by:
#'clojure.test.check.test/infinite?
Testing clojure.test.check.clojure-test-test
Testing clojure.test.check.random-test
{:result true, :num-tests 100, :seed 1672337569342, :time-elapsed-ms 14,
:test-var "determinism-spec"}
{:result true, :num-tests 100, :seed 1672337569357, :time-elapsed-ms 21,
:test-var "different-states-spec"}
{:result true, :num-tests 100, :seed 1672337569379, :time-elapsed-ms 6,
:test-var "java-util-splittable-random-spec"}
{:result true, :num-tests 100, :seed 1672337569386, :time-elapsed-ms 5,
:test-var "java-util-splittable-random-spec-double"}
{:result true, :num-tests 40, :seed 1672337569392, :time-elapsed-ms 1,
:test-var "split-n-spec"}
Testing clojure.test.check.rose-tree-test
{:result true, :num-tests 100, :seed 1672337569395, :time-elapsed-ms 11,
:test-var "test-collapse-rose"}
Testing clojure.test.check.test
{:result true, :num-tests 20, :seed 1672337569409, :time-elapsed-ms 6,
:test-var "distinct-by-collections-are-distinct-by"}
{:result true, :num-tests 1000, :seed 1672337569416, :time-elapsed-ms
29, :test-var "gen-int-with-double-size"}
{:result true, :num-tests 50, :seed 1672337569447, :time-elapsed-ms 323,
:test-var "merge-is-idempotent-and-this-spec-doesn't-OOM"}
{:result true, :num-tests 100, :seed 1672337569771, :time-elapsed-ms 6,
:test-var "generate-with-seed-test"}
{:result true, :num-tests 20, :seed 1672337569778, :time-elapsed-ms 1,
:test-var "let-as-bind-spec"}
{:result true, :num-tests 100, :seed 1672337569864, :time-elapsed-ms 2,
:test-var "uuid-generates-uuids"}
{:result true, :num-tests 500, :seed 1672337569866, :time-elapsed-ms 6,
:test-var "large-integer-spec"}
{:result true, :num-tests 20, :seed 1672337569873, :time-elapsed-ms 0,
:test-var "let-with-multiple-clauses-spec"}
{:result true, :num-tests 1000, :seed 1672337569943, :time-elapsed-ms
25, :test-var "size-bounded-bigint-generates-integers"}
{:result true, :num-tests 100, :seed 1672337569969, :time-elapsed-ms 0,
:test-var "run-with-no-options"}
{:result true, :num-tests 6, :seed 1672337569970, :time-elapsed-ms 844,
:test-var "size-bounded-bigint-distribution-test"}
{:result true, :num-tests 100, :seed 1672337570818, :time-elapsed-ms 97,
:test-var "distinct-collections-are-distinct"}
{:result true, :num-tests 100, :seed 1672337571243, :time-elapsed-ms 22,
:test-var "shuffled-vector-is-a-permutation-of-original"}
{:result true, :num-tests 5, :seed 1672337571269, :time-elapsed-ms 54,
:test-var "distinct-collections-are-not-biased-in-their-ordering"}
{:result true, :num-tests 100, :seed 1672337571324, :time-elapsed-ms 8,
:test-var "choose-respects-bounds-during-shrinking"}
{:result true, :num-tests 100, :seed 1672337571332, :time-elapsed-ms 73,
:test-var "map-honors-size-opts"}
{:result true, :num-tests 20, :seed 1672337571408, :time-elapsed-ms 151,
:test-var
Processed: test-check-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Processing control commands: > affects -1 src:clojure Bug #1027392 [src:test-check-clojure] test-check-clojure: autopkgtest needs update for new version of clojure: warning on stderr Added indication that 1027392 affects src:clojure -- 1027392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027391: puppetlabs-ring-middleware-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Source: puppetlabs-ring-middleware-clojure
Version: 1.3.1-1
Severity: serious
X-Debbugs-CC: cloj...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:clojure
Dear maintainer(s),
With a recent upload of clojure the autopkgtest of
puppetlabs-ring-middleware-clojure fails in testing when that
autopkgtest is run with the binary packages of clojure from unstable. It
passes when run with only packages from testing. In tabular form:
passfail
clojurefrom testing1.11.1-2
puppetlabs-ring-middleware-clojure from testing1.3.1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. There's a
warning on stderr which is interpreted as failure by autopkgtest. If you
can't work around the warning, you can make autopkgtest ignore it by
adding the allow-stderr restriction.
Currently this regression is blocking the migration of clojure to
testing [1]. Of course, clojure shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
clojure 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 clojure 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=clojure
https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppetlabs-ring-middleware-clojure/29779591/log.gz
#'user/all-tests
WARNING: abs already refers to: #'clojure.core/abs in namespace:
medley.core, being replaced by: #'medley.core/abs
2022-12-29 18:13:02,909 INFO [o.e.j.u.log] Logging initialized @4853ms
to org.eclipse.jetty.util.log.Slf4jLog
2022-12-29 18:13:03,109 INFO [p.t.s.w.jetty9-core] Removing buggy
security provider SunPKCS11 version 17
WARNING: update-vals already refers to: #'clojure.core/update-vals in
namespace: clojure.tools.analyzer.utils, being replaced by:
#'clojure.tools.analyzer.utils/update-vals
WARNING: update-keys already refers to: #'clojure.core/update-keys in
namespace: clojure.tools.analyzer.utils, being replaced by:
#'clojure.tools.analyzer.utils/update-keys
WARNING: update-vals already refers to: #'clojure.core/update-vals in
namespace: clojure.tools.analyzer, being replaced by:
#'clojure.tools.analyzer.utils/update-vals
WARNING: update-keys already refers to: #'clojure.core/update-keys in
namespace: clojure.tools.analyzer, being replaced by:
#'clojure.tools.analyzer.utils/update-keys
WARNING: update-vals already refers to: #'clojure.core/update-vals in
namespace: clojure.tools.analyzer.passes, being replaced by:
#'clojure.tools.analyzer.utils/update-vals
WARNING: update-vals already refers to: #'clojure.core/update-vals in
namespace: clojure.tools.analyzer.passes.uniquify, being replaced by:
#'clojure.tools.analyzer.utils/update-vals
(nil nil nil)
Testing puppetlabs.ring-middleware.core-test
2022-12-29 18:13:07,045 INFO [p.t.s.w.jetty9-service] Initializing web
server(s).
2022-12-29 18:13:07,052 INFO [p.t.s.w.jetty9-service] Starting web
server(s).
2022-12-29 18:13:07,173 INFO [p.t.s.w.jetty9-core] Starting web server.
2022-12-29 18:13:07,175 INFO [o.e.j.s.Server] jetty-9.4.50.v20221107;
built: unknown; git: unknown; jvm 17.0.5+8-Debian-2
2022-12-29 18:13:07,257 INFO [o.e.j.s.AbstractConnector] Started
ServerConnector@142a0473{HTTP/1.1, (http/1.1)}{0.0.0.0:9000}
2022-12-29 18:13:07,258 INFO [o.e.j.s.Server] Started @9202ms
2022-12-29 18:13:07,268 INFO [o.e.j.s.h.ContextHandler] Started
o.e.j.s.h.ContextHandler@44c5830b{/hello,null,AVAILABLE}
2022-12-29 18:13:07,269 INFO [o.e.j.s.h.ContextHandler] Started
o.e.j.s.h.ContextHandler@7ce46a58{/different,null,AVAILABLE}
2022-12-29 18:13:07,269 INFO [o.e.j.s.h.ContextHandler] Started
o.e.j.s.h.ContextHandler@42428c94{/hello/post,null,AVAILABLE}
2022-12-29 18:13:07,285 INFO [p.t.s.w.jetty9-service] Initializing web
server(s).
2022-12-29 18:13:07,287 INFO [p.t.s.w.jetty9-service] Starting web
server(s).
2022-12-29 18:13:07,297 INFO [p.t.s.w.jetty9-core] Starting web server.
2022-12-29 18:13:07,297 INFO [o.e.j.s.Server] jetty-9.4.50.v20221107;
built: unknown; git: unknown; jvm 17.0.5+8-Debian-2
2022-12-29 18:13:07,307 INFO [o.e.j.s.AbstractConnector] Started
ServerConnector@5089b229{HTTP/1.1, (http/1.1)}{0.0.0.0:1}
2022-12-29 18:13:07,308 INFO [o.e.j.s.Server] Started @9252ms
2022-12-29 18:13:07,310 INFO [o.e.j.s.h.ContextHandler] Started
Processed: puppetlabs-ring-middleware-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Processing control commands: > affects -1 src:clojure Bug #1027391 [src:puppetlabs-ring-middleware-clojure] puppetlabs-ring-middleware-clojure: autopkgtest needs update for new version of clojure: warning on stderr Added indication that 1027391 affects src:clojure -- 1027391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027388: data-json-clojure: autopkgtest needs update for new version of clojure: fails due to warning on stderr
Source: data-json-clojure Version: 2.4.0-1 Severity: serious X-Debbugs-CC: cloj...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:clojure Dear maintainer(s), With a recent upload of clojure the autopkgtest of data-json-clojure fails in testing when that autopkgtest is run with the binary packages of clojure from unstable. It passes when run with only packages from testing. In tabular form: passfail clojurefrom testing1.11.1-2 data-json-clojure from testing2.4.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The test itself passes, but the autopkgtest fails because there is output on stderr and by default, without the allow-stderr restriction, that is interpreted as failure. Currently this regression is blocking the migration of clojure to testing [1]. Of course, clojure shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in clojure 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 clojure 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=clojure https://ci.debian.net/data/autopkgtest/testing/amd64/d/data-json-clojure/29779588/log.gz #'user/all-tests (nil nil nil nil) Testing clojure.data.json-compat-0-1-test Testing clojure.data.json-gen-test WARNING: abs already refers to: #'clojure.core/abs in namespace: clojure.test.check.generators, being replaced by: #'clojure.test.check.generators/abs Testing clojure.data.json-test-suite-test Testing clojure.data.json-test Ran 237 tests containing 288 assertions. 0 failures, 0 errors. autopkgtest [18:13:13]: test unittests OpenPGP_signature Description: OpenPGP digital signature
Bug#1027390: prismatic-schema-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Source: prismatic-schema-clojure
Version: 1.2.0-1
Severity: serious
X-Debbugs-CC: cloj...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:clojure
Dear maintainer(s),
With a recent upload of clojure the autopkgtest of
prismatic-schema-clojure fails in testing when that autopkgtest is run
with the binary packages of clojure from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
clojurefrom testing1.11.1-2
prismatic-schema-clojure from testing1.2.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. The test
itself passes, but there's output on stderr. autopkgtest interprets
stderr output as failure unless the allow-stderr restriction is declared.
Currently this regression is blocking the migration of clojure to
testing [1]. Of course, clojure shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
clojure 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 clojure 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=clojure
https://ci.debian.net/data/autopkgtest/testing/amd64/p/prismatic-schema-clojure/29779590/log.gz
#'user/all-tests
WARNING: parse-long already refers to: #'clojure.core/parse-long in
namespace: schema.core-test, being replaced by:
#'schema.core-test/parse-long
WARNING: abs already refers to: #'clojure.core/abs in namespace:
clojure.test.check.generators, being replaced by:
#'clojure.test.check.generators/abs
(nil nil nil nil nil nil nil nil nil nil)
Testing schema.test-test
Testing schema.experimental.generators-test
{:result true, :num-tests 100, :seed 1672337573453, :time-elapsed-ms
375, :test-var "spec-test"}
Testing schema.macros-test
Testing schema.experimental.abstract-map-test
Testing schema.experimental.complete-test
Testing schema.core-test
Testing schema.coerce-test
Testing schema.utils-test
Ran 126 tests containing 716 assertions.
0 failures, 0 errors.
autopkgtest [18:12:55]: test unittests
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1027389: prismatic-plumbing-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Source: prismatic-plumbing-clojure Version: 0.6.0-2 Severity: serious X-Debbugs-CC: cloj...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:clojure Dear maintainer(s), With a recent upload of clojure the autopkgtest of prismatic-plumbing-clojure fails in testing when that autopkgtest is run with the binary packages of clojure from unstable. It passes when run with only packages from testing. In tabular form: passfail clojurefrom testing1.11.1-2 prismatic-plumbing-clojure from testing0.6.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. The test itself passes, but the autopkgtest fails because of warnings on stderr. Without the allow-stderr restriction, output on stderr is interpreted as failure. Currently this regression is blocking the migration of clojure to testing [1]. Of course, clojure shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in clojure 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 clojure 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=clojure https://ci.debian.net/data/autopkgtest/testing/amd64/p/prismatic-plumbing-clojure/29779589/log.gz #'user/all-tests WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer.utils, being replaced by: #'clojure.tools.analyzer.utils/update-vals WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: clojure.tools.analyzer.utils, being replaced by: #'clojure.tools.analyzer.utils/update-keys WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer, being replaced by: #'clojure.tools.analyzer.utils/update-vals WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: clojure.tools.analyzer, being replaced by: #'clojure.tools.analyzer.utils/update-keys WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer.passes, being replaced by: #'clojure.tools.analyzer.utils/update-vals WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer.passes.uniquify, being replaced by: #'clojure.tools.analyzer.utils/update-vals (nil nil nil nil nil nil nil nil nil nil) Testing plumbing.graph-perf-test Testing plumbing.fnk.pfnk-test Testing plumbing.core-test Testing plumbing.lazymap-test Testing plumbing.fnk.fnk-examples-test Testing plumbing.map-test Testing plumbing.graph-async-test Testing plumbing.graph-examples-test Testing plumbing.fnk.schema-test Testing plumbing.graph-test Ran 129 tests containing 581 assertions. 0 failures, 0 errors. autopkgtest [18:13:03]: test upstream OpenPGP_signature Description: OpenPGP digital signature
Processed: prismatic-schema-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Processing control commands: > affects -1 src:clojure Bug #1027390 [src:prismatic-schema-clojure] prismatic-schema-clojure: autopkgtest needs update for new version of clojure: warning on stderr Added indication that 1027390 affects src:clojure -- 1027390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: prismatic-plumbing-clojure: autopkgtest needs update for new version of clojure: warning on stderr
Processing control commands: > affects -1 src:clojure Bug #1027389 [src:prismatic-plumbing-clojure] prismatic-plumbing-clojure: autopkgtest needs update for new version of clojure: warning on stderr Added indication that 1027389 affects src:clojure -- 1027389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: data-json-clojure: autopkgtest needs update for new version of clojure: fails due to warning on stderr
Processing control commands: > affects -1 src:clojure Bug #1027388 [src:data-json-clojure] data-json-clojure: autopkgtest needs update for new version of clojure: fails due to warning on stderr Added indication that 1027388 affects src:clojure -- 1027388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1008313: lxpolkit: no authentication dialog can't use it
Processing control commands: > tags -1 help Bug #1008313 [lxpolkit] lxpolkit: no authentication dialog can't use it Added tag(s) help. -- 1008313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008313: lxpolkit: no authentication dialog can't use it
Control: tags -1 help On 30-12-2022 20:33, Andriy Grytsenko wrote: It would be good to get some help with this issue actually. So, let's tag the bug accordingly. And yet I use LXDE myself each day, I cannot say it's *nearly useless* but many people use it and rarely have problems. Good to know. I'll not try to remove LXDE based on this bug report then ;). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1019828: marked as done (megaglest: Please transition to wxwidgets3.2)
Your message dated Fri, 30 Dec 2022 19:50:04 + with message-id and subject line Bug#1019828: fixed in megaglest 3.13.0-8 has caused the Debian Bug report #1019828, regarding megaglest: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: megaglest Severity: normal Control: block 1019416 by -1 Hi, Please transition megaglest from wxwidgets3.0 to wxwidgets3.2. wxWidgets 3.2 (a new API/ABI stable release) has been released a few months ago and is now packaged in unstable as wxwidgets3.2. Upstream has stopped supporting wxWidgets 3.0, so the Debian wx team would like to migrate all wx package users to wxwidgets3.2 for bullseye, with the plan to remove wxwidgets3.0 before release. For most packages, the transition should be as simple as changing Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some packages may require small patches; I'm happy to help with those (and I have some already from working on this transition in Fedora already). Thanks, Scott --- End Message --- --- Begin Message --- Source: megaglest Source-Version: 3.13.0-8 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of megaglest, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated megaglest 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: Fri, 30 Dec 2022 14:21:20 -0500 Source: megaglest Architecture: source Version: 3.13.0-8 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Scott Talbert Closes: 1019828 Changes: megaglest (3.13.0-8) unstable; urgency=medium . * Team upload. * Transition to wxWidgets 3.2 (Closes: #1019828) Checksums-Sha1: 1dd11babbd48fef0a852d5554034c3e1e45f7192 2296 megaglest_3.13.0-8.dsc 193891a7a412e152624b50da59d815bf2f20ac15 23152 megaglest_3.13.0-8.debian.tar.xz 9f666036c4cee41e9dfa60934a065d52409d9042 15836 megaglest_3.13.0-8_amd64.buildinfo Checksums-Sha256: 8c544fb4034cff7681fdc616f5e00e237c5e684016c6f55d31a12cff2952d103 2296 megaglest_3.13.0-8.dsc d06d47cbbef24844915964b290ac8e6c2f5fda599f7cc8fe610c06b32bfaa937 23152 megaglest_3.13.0-8.debian.tar.xz f984a1cac51df2ae05155a45273c46aed14cbe6f4d6b11825bb41fb5f25bbf03 15836 megaglest_3.13.0-8_amd64.buildinfo Files: 83e1e2bd15bbc8afc2d9d685b1853a3c 2296 games optional megaglest_3.13.0-8.dsc 052af179cb8a49e8278fc5571a5c2f62 23152 games optional megaglest_3.13.0-8.debian.tar.xz aaad8a78d54d37a9025e6309963cc4e1 15836 games optional megaglest_3.13.0-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmOvPfcPHHN3dEB0ZWNo aWUubmV0AAoJEFPVvGS1I3iiHzcP/2+aOHSOSG+gPb5EWv8pac1zNqsUXpfNhh83 afmTCmVwca+Cfi2Qy96KFWPdLuOlhK7FKjEgKouIwv/EnNNoQUU4j5YvbrKNI3zO hbtae7LoRXm4xOYdapEVrhnueh/Yj1xDgXHnuid62p+dHJRd7n2df+YcYCLPLWiQ N8PUQiKW0C0lezAd7SsFoHwiuntTQVp8juD2aMaEWDkrrBaW3PzFbVZVjAC3I6aX v2AemzYnvFcujLG2Hdd2b34miFT5NbNyTH12Lno7bftWo4XOOO0Wb2+61v5ckQHQ zUyEa98dvc8s7XBcpgNp9lLCMyAys6KZ/3KqAG4dZ9+rXmzH6xejil9cuWj+v2pJ TXKhNKxsLLysudSgaTky/4uC9Cu3zE+88DOrH2Z4ui2cWQwX5kXIHjWGFkIZxXjo q+5S5toVc9G32hxoV3C1R0kpRWgmjV/OeohLIpNCNscaM/rcdCPz1N5LuGgv07u1 Zm93GvVIgzt8y+HlBdl9e/F2HeaOZq0+F85ws6FBxZZZB6aoLC6j3v6U7SpdhjfH m0dgm3Xt6zW3DGOtzlGnxuJ80LcwIkCCBRc1JdXuTJtSGpWAE4YHYasj+td29NsO bYtonwHaWywfHuumlcoiB4+VkAHQn8Tx5ucLm7rq/0vFVS5REMAFoIYJlcLsg6xn K3OImsmH =BOPj -END PGP SIGNATURE End Message ---
Bug#1008313: lxpolkit: no authentication dialog can't use it
Hello dear Paul and all Release Team! >Can you at least please comment on this bug? Do you recognize it? Can >you reproduce it (I would guess not, seems like this would make lxde >nearly useless for everybody)? *If* lxde is nearly useless for >everybody, I'd like to know, then I think we shouldn't ship it with >bookworm. Actually I did not managed yet to reproduce this bug although I have a bit of problems with electricity (you know, there is a war ongoing in Ukraine) so it's a bit hard right now to create a clean environment for testing. It would be good to get some help with this issue actually. I hope I can make some testing in the nearest future but cannot promise anything yet. I'm sorry. And yet I use LXDE myself each day, I cannot say it's *nearly useless* but many people use it and rarely have problems.
Bug#1019828: marked as pending in megaglest
Control: tag -1 pending Hello, Bug #1019828 in megaglest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/games-team/megaglest/-/commit/b8d9bd377b86afa78b06d13047d396eeb58dda5b Transition to wxWidgets 3.2 (Closes: #1019828) (this message was generated automatically) -- Greetings https://bugs.debian.org/1019828
Processed: Bug#1019828 marked as pending in megaglest
Processing control commands: > tag -1 pending Bug #1019828 [src:megaglest] megaglest: Please transition to wxwidgets3.2 Added tag(s) pending. -- 1019828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027335: pairtools -- FTBFS in unstable
Control: severity -1 normal
Control: retitle -1 pairtools -- current repo in salsa FTBFS
Control: clone -1 -2
Control: reassign -2 python3-pysam 0.20.0+ds-2
Control: retitle -2 pysam -- no definition for bam_dup1
On Fri, Dec 30, 2022 at 08:24:42PM +0530, Nilesh Patra wrote:
> On Fri, 30 Dec 2022 20:05:32 +0530 Nilesh Patra wrote:
> > Source: pairtools
> > Version: 0.3.0-3.2
> > Severity: serious
> >
> > Pairtools FTBFS with pysam related error. Looks like
> > something is off.
> >
> > dh_auto_clean
> > I: pybuild base:240: python3.11 setup.py clean
> > Traceback (most recent call last):
> >
> >
> > File "/<>/setup.py", line 130, in
> > ext_modules=get_ext_modules(),
> > ^
> > File "/<>/setup.py", line 81, in get_ext_modules
> > extra_link_args=pysam.get_libraries(),
> > ^
> > File "/usr/lib/python3/dist-packages/pysam/__init__.py", line 100, in
> > get_libraries
> > return [os.path.join(dirname, x + so) for x in pysam_libs]
> >^^^
> > File "/usr/lib/python3/dist-packages/pysam/__init__.py", line 100, in
> >
> > return [os.path.join(dirname, x + so) for x in pysam_libs]
> > ~~^~~~
> > TypeError: can only concatenate str (not "NoneType") to str
>
> This patch in pysam gets the build in pairtools going beyond this point, but
> now the build chokes with:
>
> | pairtools.cli (unittest.loader._FailedTest.pairtools.cli) ... ERROR
>
>
> | pairtools.lib (unittest.loader._FailedTest.pairtools.lib) ... ERROR
> |
> | ==
> | ERROR: pairtools.cli (unittest.loader._FailedTest.pairtools.cli)
> | --
> | ImportError: Failed to import test module: pairtools.cli
> | Traceback (most recent call last):
> | File "/usr/lib/python3.11/unittest/loader.py", line 440, in _find_test_path
> |package = self._get_module_from_name(name)
> |
> | File "/usr/lib/python3.11/unittest/loader.py", line 350, in
> _get_module_from_name
> |__import__(name)
> | File
> "/<>/.pybuild/cpython3_3.11/build/pairtools/cli/__init__.py",
> line 188, in
> |from . import (
> | File
> "/<>/.pybuild/cpython3_3.11/build/pairtools/cli/dedup.py", line
> 12, in
> |from ..lib import fileio, pairsam_format, headerops
> | File
> "/<>/.pybuild/cpython3_3.11/build/pairtools/lib/__init__.py",
> line 7, in
> |from . import parse
> | File
> "/<>/.pybuild/cpython3_3.11/build/pairtools/lib/parse.py", line
> 38, in
> |from .parse_pysam import get_mismatches_c
> | ImportError:
> /<>/.pybuild/cpython3_3.11/build/pairtools/lib/parse_pysam.cpython-311-x86_64-linux-gnu.so:
> undefined symbol: bam_dup1
Turns out this is because there is just a function "declaration" in
pysam/libchtslib.pxd for bam_dup1.
But the headers imported do not even have the function.
I patched the current package in salsa to get the ball rolling. But this needs
bioframe.
Also, the below patch still needs to be applied to pysam. pushed to salsa.
> Description: Add patch to return proper sysconf so for current python
> Author: Nilesh Patra
> Last-Update: 2022-12-30
> --- a/pysam/__init__.py
> +++ b/pysam/__init__.py
> @@ -96,5 +96,7 @@
> if pysam.config.HTSLIB == "builtin":
> pysam_libs.append('libchtslib')
>
> -so = sysconfig.get_config_var('SO')
> +so = sysconfig.get_config_var('EXT_SUFFIX')
> +if not so:
> +so = sysconfig.get_config_var('SO')
> return [os.path.join(dirname, x + so) for x in pysam_libs]
>
--
Best,
Nilesh
signature.asc
Description: PGP signature
Processed: Re: pairtools -- FTBFS in unstable
Processing control commands: > severity -1 normal Bug #1027335 [src:python-pysam] pairtools -- FTBFS in unstable Severity set to 'normal' from 'serious' > retitle -1 pairtools -- current repo in salsa FTBFS Bug #1027335 [src:python-pysam] pairtools -- FTBFS in unstable Changed Bug title to 'pairtools -- current repo in salsa FTBFS' from 'pairtools -- FTBFS in unstable'. > clone -1 -2 Bug #1027335 [src:python-pysam] pairtools -- current repo in salsa FTBFS Bug 1027335 cloned as bug 1027386 > reassign -2 python3-pysam 0.20.0+ds-2 Bug #1027386 [src:python-pysam] pairtools -- current repo in salsa FTBFS Bug reassigned from package 'src:python-pysam' to 'python3-pysam'. No longer marked as found in versions python-pysam/0.20.0+ds-2. Ignoring request to alter fixed versions of bug #1027386 to the same values previously set Bug #1027386 [python3-pysam] pairtools -- current repo in salsa FTBFS Marked as found in versions python-pysam/0.20.0+ds-2. > retitle -2 pysam -- no definition for bam_dup1 Bug #1027386 [python3-pysam] pairtools -- current repo in salsa FTBFS Changed Bug title to 'pysam -- no definition for bam_dup1' from 'pairtools -- current repo in salsa FTBFS'. -- 1027335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027335 1027386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026672: marked as done (python-congressclient: FTBFS: TypeError: load_all() missing 1 required positional argument: 'Loader')
Your message dated Fri, 30 Dec 2022 18:27:17 + with message-id and subject line Bug#1027281: Removed package(s) from unstable has caused the Debian Bug report #1026672, regarding python-congressclient: FTBFS: TypeError: load_all() missing 1 required positional argument: 'Loader' 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.) -- 1026672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-congressclient Version: 2.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_test --no-py2 > + PKGOS_TEST_PARALLEL=yes > + PKGOS_TEST_SERIAL=no > + PYTHONS=disabled > + PYTHON3S=disabled > + TEST_PARALLEL_OPT=--parallel > + TEST_SERIAL_OPT= > + echo WARNING: --no-py2 is deprecated, and always on. > WARNING: --no-py2 is deprecated, and always on. > + shift > + py3versions -vr > + PYTHON3S=3.11 3.10 > + [ yes = no ] > + [ no = yes ] > + [ 3.11 = disabled ] > + echo 3.11 > + cut -d. -f1 > + PYMAJOR=3 > + echo ===> Testing with python (python3) > ===> Testing with python (python3) > + pwd > + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ] > + [ -e .stestr.conf ] > + [ -x /usr/bin/python3-stestr ] > + STESTR=stestr > + rm -rf .stestr > + PYTHON=python3.11 stestr run --parallel --subunit > + subunit2pyunit > congressclient.tests.v1.test_datasource.TestDeleteDatasourceDriver.test_delete_datasource > congressclient.tests.v1.test_datasource.TestDeleteDatasourceDriver.test_delete_datasource > ... ok > congressclient.tests.v1.test_datasource.TestListDatasourceStatus.test_list_datasource_status > congressclient.tests.v1.test_datasource.TestListDatasourceStatus.test_list_datasource_status > ... ok > congressclient.tests.v1.test_datasource.TestCreateDatasource.test_create_datasource > congressclient.tests.v1.test_datasource.TestCreateDatasource.test_create_datasource > ... ok > congressclient.tests.v1.test_datasource.TestShowDatasourceActions.test_show_datasource_actions > congressclient.tests.v1.test_datasource.TestShowDatasourceActions.test_show_datasource_actions > ... ok > congressclient.tests.v1.test_datasource.TestShowDatasourceTableSchema.test_show_datasource_table_schema > congressclient.tests.v1.test_datasource.TestShowDatasourceTableSchema.test_show_datasource_table_schema > ... ok > congressclient.tests.v1.test_datasource.TestDatasourceRequestRefresh.test_datasource_request_refresh > congressclient.tests.v1.test_datasource.TestDatasourceRequestRefresh.test_datasource_request_refresh > ... ok > congressclient.tests.v1.test_policy.TestDeletePolicyRule.test_delete_policy_rule > congressclient.tests.v1.test_policy.TestDeletePolicyRule.test_delete_policy_rule > ... ok > congressclient.tests.v1.test_policy.TestCreatePolicyRule.test_create_policy_rule > congressclient.tests.v1.test_policy.TestCreatePolicyRule.test_create_policy_rule > ... ok > congressclient.tests.v1.test_policy.TestCreatePolicyRule.test_create_policy_rule_with_name > congressclient.tests.v1.test_policy.TestCreatePolicyRule.test_create_policy_rule_with_name > ... ok > congressclient.tests.v1.test_drivers.TestListDrivers.test_list_drivers > congressclient.tests.v1.test_drivers.TestListDrivers.test_list_drivers ... ok > congressclient.tests.v1.test_datasource.TestListDatasourceRows.test_list_datasource_row > congressclient.tests.v1.test_datasource.TestListDatasourceRows.test_list_datasource_row > ... ok > congressclient.tests.v1.test_api_versions.TestAPIVersions.test_list_api_versions > congressclient.tests.v1.test_api_versions.TestAPIVersions.test_list_api_versions > ... ok > congressclient.tests.v1.test_policy.TestListPolicy.test_list_policy_rules > congressclient.tests.v1.test_policy.TestListPolicy.test_list_policy_rules ... > ok > congressclient.tests.v1.test_drivers.TestShowDriverConfig.test_show_driver_config > congressclient.tests.v1.test_drivers.TestShowDriverConfig.test_show_driver_config > ... ok > congressclient.tests.v1.test_policy.TestListPolicyRows.test_list_policy_rules > congressclient.tests.v1.test_policy.TestListPolicyRows.test_list_policy_rules > ... ok > congressclient.tests.v1.test_datasource.TestListDatasourceTables.test_list_datasource_tables >
Bug#1018191: libapreq2: CVE-2022-22728: multipart form parse memory corruption
Hi,
On Fri, Dec 30, 2022 at 05:25:41PM +0100, Tobias Frost wrote:
> On Fri, Dec 30, 2022 at 04:14:25PM +0100, Salvatore Bonaccorso wrote:
> > Hi Steinar, hi Tobias,
> >
> > On Fri, Dec 30, 2022 at 12:04:29PM +0100, Tobias Frost wrote:
> > > On Fri, Dec 30, 2022 at 11:18:14AM +0100, Steinar H. Gunderson wrote:
> > > > On Fri, Dec 30, 2022 at 11:04:46AM +0100, Tobias Frost wrote:
> > > > > I was trying to triage this CVE and *maybe* those revisions are
> > > > > related:
> > > > >
> > > > > r1894937 ("apreq_parse_headers: Discard CRLF of folded values.")
> > > > > r1894940 ("reindent (no functional change).")
> > > > > r1894977 ("Follow up to r1894937: Fix setting of empty value.")
> > > > > r1895054 ("Follow up to r1894937: Always eat CRLF at the end of
> > > > > header value.")
> > > >
> > > > Perhaps it's best to remove libapreq2 entirely? I don't use nor
> > > > maintain it
> > > > anymore, it's been out of testing for a while, and there's this CVE.
> > >
> > > #ssh mirror.ftp-master.debian.org "dak rm -Rn libapreq2"
> > >
> > > Will remove the following packages from unstable:
> > >
> > > libapache2-mod-apreq2 | 2.13-7+b4 | amd64, arm64, armel, armhf, i386,
> > > mips64el, mipsel, ppc64el, s390x
> > > libapache2-request-perl | 2.13-7+b4 | amd64, arm64, armel, armhf,
> > > i386, mips64el, mipsel, ppc64el, s390x
> > >libapreq2 | 2.13-7 | source
> > > libapreq2-3 | 2.13-7+b4 | amd64, arm64, armel, armhf, i386, mips64el,
> > > mipsel, ppc64el, s390x
> > > libapreq2-dev | 2.13-7+b4 | amd64, arm64, armel, armhf, i386,
> > > mips64el, mipsel, ppc64el, s390x
> > > libapreq2-doc | 2.13-7 | all
> > >
> > > Maintainer: Steinar H. Gunderson
> > >
> > > --- Reason ---
> > >
> > > --
> > >
> > > Checking reverse dependencies...
> > > # Broken Depends:
> > > libapache2-authcassimple-perl: libapache2-authcassimple-perl
> > > libapache2-sitecontrol-perl: libapache2-sitecontrol-perl
> > > lua-apr: lua-apr
> > > rapache: libapache2-mod-r-base
> > >
> > > # Broken Build-Depends:
> > > libapache2-sitecontrol-perl: libapache2-request-perl
> > > lua-apr: libapreq2-dev
> > > rapache: libapreq2-dev
> > >
> > > Dependency problem found.
> > >
> > > ... and still theres a need to fix the CVE for stable (and also for
> > > (E)LTS)
> > >
> > > (I'm currently take a look at 2.17, to see if I can get it packages, if
> > > I'm succeeding,
> > > there will be an NMU announcement :))
> >
> > Upstream has still not clarified on
> > https://www.openwall.com/lists/oss-security/2022/08/26/4 and given it
> > was now out of bookworm, it might be wise that we actually sunset it
> > for bookworm (including having the above reverse dependencies out of
> > bookworm).
> >
> > Fixing stable and oldstable is then another story, and I still hope we
> > get feedback from upstream on pinpointing the fixes.
>
> ACK, I will file a "not suitable for bookworm" bug, so that the new package
> and r-depends won't migrate.
Thank you Tobi!
> Lets hope that upstream answers…
Regards,
Salvatore
Bug#1027382: weresync: FTBFS in bullseye (missing build-depends on e2fsprogs)
Package: src:weresync Version: 1.0.9-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules build-indep dh build-indep --with python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:232: python3.9 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:232: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.9/build/weresync copying src/weresync/gui.py -> /<>/.pybuild/cpython3_3.9/build/weresync copying src/weresync/__init__.py -> /<>/.pybuild/cpython3_3.9/build/weresync copying src/weresync/exception.py -> /<>/.pybuild/cpython3_3.9/build/weresync copying src/weresync/interface.py -> /<>/.pybuild/cpython3_3.9/build/weresync copying src/weresync/utils.py -> /<>/.pybuild/cpython3_3.9/build/weresync copying src/weresync/device.py -> /<>/.pybuild/cpython3_3.9/build/weresync creating /<>/.pybuild/cpython3_3.9/build/weresync/plugins copying src/weresync/plugins/weresync_syslinux.py -> /<>/.pybuild/cpython3_3.9/build/weresync/plugins copying src/weresync/plugins/__init__.py -> /<>/.pybuild/cpython3_3.9/build/weresync/plugins copying src/weresync/plugins/weresync_uuid_copy.py -> /<>/.pybuild/cpython3_3.9/build/weresync/plugins copying src/weresync/plugins/weresync_grub2.py -> /<>/.pybuild/cpython3_3.9/build/weresync/plugins creating /<>/.pybuild/cpython3_3.9/build/weresync/resources copying src/weresync/resources/__init__.py -> /<>/.pybuild/cpython3_3.9/build/weresync/resources copying src/weresync/resources/weresync.svg -> /<>/.pybuild/cpython3_3.9/build/weresync/resources creating /<>/.pybuild/cpython3_3.9/build/weresync/resources/locale creating /<>/.pybuild/cpython3_3.9/build/weresync/resources/locale/en creating /<>/.pybuild/cpython3_3.9/build/weresync/resources/locale/en/LC_MESSAGES copying src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo -> /<>/.pybuild/cpython3_3.9/build/weresync/resources/locale/en/LC_MESSAGES debian/rules execute_after_dh_auto_build make[1]: Entering directory '/<>' https_proxy=127.0.0.1:9 http_proxy=127.0.0.1:9 PYTHONPATH=. python3 `which sphinx-build` -N -bhtml docs/source build/html # HTML generator Running Sphinx v3.4.3 loading translations [en]... done making output directory... done WARNING: html_static_path entry '_static' does not exist building [mo]: targets for 0 po files that are out of date building [html]: targets for 8 source files that are out of date updating environment: [new config] 8 added, 0 changed, 0 removed reading sources... [ 12%] api reading sources... [ 25%] bootloader reading sources... [ 37%] gui reading sources... [ 50%] index reading sources... [ 62%] installation reading sources... [ 75%] issues reading sources... [ 87%] translation reading sources... [100%] weresync looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done writing output... [ 12%] api writing output... [ 25%] bootloader writing output... [ 37%] gui writing output... [ 50%] index writing output... [ 62%] installation writing output... [ 75%] issues writing output... [ 87%] translation writing output... [100%] weresync generating indices... genindex py-modindex done highlighting module code... [ 25%] weresync.device highlighting module code... [ 50%] weresync.exception highlighting module code... [ 75%] weresync.interface highlighting module code... [100%] weresync.plugins writing additional pages... search done copying images... [ 50%] img/gui-example.png copying images... [100%] img/weresync-logo.png copying static files... done copying extra files... done dumping search index in English (code: en)... done dumping object inventory... done build succeeded, 1 warning. The HTML pages are in build/html. make[1]: Leaving directory '/<>' dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build; python3.9 -m pytest tests = test session starts == platform linux -- Python 3.9.2, pytest-6.0.2, py-1.10.0, pluggy-0.13.0 rootdir: /<>, configfile: setup.cfg, testpaths: tests collected 57 items tests/test_device.py ..F [ 89%] .. [100%] === FAILURES === test_get_partition_file_system monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f5928f91550> def test_get_partition_file_system(monkeypatch): generateStandardMock(monkeypatch, b"ext4", b"", 0)
Bug#1027383: xen-tools: FTBFS in bullseye (missing build-depends on mount)
Package: src:xen-tools Version: 4.9-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>' /usr/bin/make non-author-test make[2]: Entering directory '/<>' make[3]: Entering directory '/<>/t' ./modules.sh > modules.t chmod 750 modules.t make[3]: Leaving directory '/<>/t' prove --shuffle t/ t/xt-create-xen-config.t .. ok t/hook-hostname.t . ok t/pod.t ... ok t/plugin-checks.t . ok t/shell-syntax.t .. ok t/hook-inittab.t .. ok t/hooks.t . ok t/hook-apt.t .. ok t/xen-lists-images.t .. ok t/hook-daemons.t .. ok # Failed test 'Required binary installed: /bin/mount' # at t/programs.t line 32. # Looks like you failed 1 test of 6. t/programs.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/6 subtests t/modules.t ... ok Couldn't determine Xen toolstack, skipping check for running DomUs. t/xen-delete-image.t .. ok t/pod-check.t . ok t/perl-syntax.t ... ok t/hook-tls.t .. skipped: This test will fail upon 64 bit systems Test Summary Report --- t/programs.t(Wstat: 256 Tests: 6 Failed: 1) Failed test: 3 Non-zero exit status: 1 Files=16, Tests=1542, 8 wallclock secs ( 0.31 usr 0.04 sys + 6.66 cusr 1.46 csys = 8.47 CPU) Result: FAIL make[2]: *** [Makefile:302: non-author-test] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:10: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: binary-indep] Error 2 dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#1027381: siridb-server: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:siridb-server Version: 2.0.43-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-arch dh binary-arch dh_update_autotools_config -a dh_autoreconf -a debian/rules override_dh_auto_build-arch make[1]: Entering directory '/<>' dh_auto_build --sourcedirectory=Release cd Release && make -j2 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>/Release' Building file: ../src/xpath/xpath.c Building file: ../src/base64/base64.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xpath/xpath.d" -MT"src/xpath/xpath.o" -o "src/xpath/xpath.o" "../src/xpath/xpath.c" Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/base64/base64.d" -MT"src/base64/base64.o" -o "src/base64/base64.o" "../src/base64/base64.c" Finished building: ../src/base64/base64.c Building file: ../src/xmath/xmath.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xmath/xmath.d" -MT"src/xmath/xmath.o" -o "src/xmath/xmath.o" "../src/xmath/xmath.c" Finished building: ../src/xpath/xpath.c Building file: ../src/timeit/timeit.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/timeit/timeit.d" -MT"src/timeit/timeit.o" -o "src/timeit/timeit.o" "../src/timeit/timeit.c" Finished building: ../src/xmath/xmath.c Finished building: ../src/timeit/timeit.c Building file: ../src/xstr/xstr.c Building file: ../src/vec/vec.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xstr/xstr.d" -MT"src/xstr/xstr.o" -o "src/xstr/xstr.o" "../src/xstr/xstr.c" Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/vec/vec.d" -MT"src/vec/vec.o" -o "src/vec/vec.o" "../src/vec/vec.c" Finished building: ../src/vec/vec.c Building file: ../src/siri/service/account.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/account.d" -MT"src/siri/service/account.o" -o "src/siri/service/account.o" "../src/siri/service/account.c" Finished building: ../src/xstr/xstr.c Building file: ../src/siri/service/client.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/client.d" -MT"src/siri/service/client.o" -o "src/siri/service/client.o" "../src/siri/service/client.c" Finished building: ../src/siri/service/account.c Building file: ../src/siri/service/request.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/request.d" -MT"src/siri/service/request.o" -o "src/siri/service/request.o" "../src/siri/service/request.c" Finished building: ../src/siri/service/client.c Building file: ../src/siri/net/bserver.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/net/bserver.d" -MT"src/siri/net/bserver.o" -o "src/siri/net/bserver.o" "../src/siri/net/bserver.c" Finished building: ../src/siri/service/request.c Building file: ../src/siri/net/clserver.c Invoking: GCC C Compiler cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/net/clserver.d" -MT"src/siri/net/clserver.o" -o "src/siri/net/clserver.o"
Bug#1027380: safeclib: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:safeclib Version: 3.5-3 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a [...] FAIL: t_gmtime_s FAIL: t_localtime_s PASS: t_getenv_s PASS: t_bsearch_s PASS: t_qsort_s = Safe C Library 04062019.0-ga99a05: tests/test-suite.log = # TOTAL: 124 # PASS: 122 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: t_gmtime_s FAIL t_gmtime_s (exit status: 1) FAIL: t_localtime_s === FAIL t_localtime_s (exit status: 1) [...] make[3]: *** [Makefile:4324: check-am] Error 2 make[3]: Leaving directory '/<>/tests' make[2]: *** [Makefile:1188: check-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:1492: check] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j2 check VERBOSE=1 returned exit code 2 make: *** [debian/rules:9: build-arch] Error 25 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#1027378: mu-editor: FTBFS in bullseye (missing build-depends on mount)
Package: src:mu-editor
Version: 1.0.3+dfsg-2
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary-indep
dh binary-indep --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
install -d
/<>/mu-editor-1.0.3\+dfsg/debian/.debhelper/generated/_source/home
pybuild --configure -i python{version} -p 3.9
D: pybuild pybuild:568: version: 4.20201102+nmu1
D: pybuild pybuild:569: ['/usr/bin/pybuild', '--configure', '-i',
'python{version}', '-p', '3.9']
D: pybuild pybuild:36: cfg: Namespace(verbose=True, quiet=False, really_quiet=False,
detect_only=False, clean_only=False, configure_only=True, build_only=False,
install_only=False, test_only=False, list_systems=False, print_args=None,
before_clean=None, clean_args=None, after_clean=None, before_configure=None,
configure_args=None, after_configure=None, before_build=None, build_args=None,
after_build=None, before_install=None, install_args=None, after_install=None,
before_test=None, test_args=None, after_test=None, test_nose=False, test_nose2=False,
test_pytest=True, test_tox=False, dir='/<>', destdir='debian/tmp',
ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', ext_sub_pattern=None, ext_sub_repl=None,
install_dir=None, name='mu-editor', system=None, versions=['3.9'],
interpreter=['python{version}'], disable=None, custom_tests=True)
D: pybuild __init__:36: cannot initialize 'cmake' plugin
Traceback (most recent call last):
File "/usr/share/dh-python/dhpython/build/__init__.py", line 32, in
module.BuildSystem.is_usable()
File "/usr/share/dh-python/dhpython/build/base.py", line 122, in is_usable
raise Exception("missing command: %s" % command)
Exception: missing command: cmake
D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
D: pybuild pybuild:131: detected build system: distutils (certainty: 51%)
D: pybuild plugin_distutils:54: pydistutils config file:
[clean]
all=1
[build]
build-lib=/<>/.pybuild/cpython3_3.9_mu-editor/build
[install]
force=1
install-layout=deb
install-scripts=$base/bin
install-lib=/usr/lib/python3.9/dist-packages
prefix=/usr
I: pybuild base:232: python3.9 setup.py config
D: pybuild tools:232: invoking: python3.9 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
pybuild --build -i python{version} -p 3.9
D: pybuild pybuild:568: version: 4.20201102+nmu1
D: pybuild pybuild:569: ['/usr/bin/pybuild', '--build', '-i',
'python{version}', '-p', '3.9']
D: pybuild pybuild:36: cfg: Namespace(verbose=True, quiet=False, really_quiet=False,
detect_only=False, clean_only=False, configure_only=False, build_only=True,
install_only=False, test_only=False, list_systems=False, print_args=None,
before_clean=None, clean_args=None, after_clean=None, before_configure=None,
configure_args=None, after_configure=None, before_build=None, build_args=None,
after_build=None, before_install=None, install_args=None, after_install=None,
before_test=None, test_args=None, after_test=None, test_nose=False, test_nose2=False,
test_pytest=True, test_tox=False, dir='/<>', destdir='debian/tmp',
ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', ext_sub_pattern=None, ext_sub_repl=None,
install_dir=None, name='mu-editor', system=None, versions=['3.9'],
interpreter=['python{version}'], disable=None, custom_tests=True)
D: pybuild __init__:36: cannot initialize 'cmake' plugin
Traceback (most recent call last):
File "/usr/share/dh-python/dhpython/build/__init__.py", line 32, in
module.BuildSystem.is_usable()
File "/usr/share/dh-python/dhpython/build/base.py", line 122, in is_usable
raise Exception("missing command: %s" % command)
Exception: missing command: cmake
D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
D: pybuild pybuild:131: detected build system: distutils (certainty: 51%)
I: pybuild base:232: /usr/bin/python3 setup.py build
D: pybuild tools:232: invoking: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.9_mu-editor/build/mu
copying mu/mu-debug.py ->
/<>/.pybuild/cpython3_3.9_mu-editor/build/mu
copying mu/__init__.py ->
/<>/.pybuild/cpython3_3.9_mu-editor/build/mu
copying mu/__main__.py ->
/<>/.pybuild/cpython3_3.9_mu-editor/build/mu
copying mu/logic.py -> /<>/.pybuild/cpython3_3.9_mu-editor/build/mu
copying mu/localedetect.py ->
/<>/.pybuild/cpython3_3.9_mu-editor/build/mu
copying mu/app.py -> /<>/.pybuild/cpython3_3.9_mu-editor/build/mu
creating /<>/.pybuild/cpython3_3.9_mu-editor/build/mu/contrib
copying mu/contrib/microfs.py ->
/<>/.pybuild/cpython3_3.9_mu-editor/build/mu/contrib
copying mu/contrib/__init__.py ->
Bug#1027379: nfdump: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:nfdump Version: 1.6.22-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-arch dh binary-arch dh_update_autotools_config -a dh_autoreconf -a [...] --- test1.out 2022-07-15 11:53:20.623099184 + +++ nfdump.test.out 2020-11-21 11:59:46.0 + @@ -4,8 +4,8 @@ label= export sysid = 1 size = 172 - first=1089541800 [2004-07-11 10:30:00] - last =1089541810 [2004-07-11 10:30:10] + first=1089534600 [2004-07-11 10:30:00] + last =1089534610 [2004-07-11 10:30:10] msec_first =10 msec_last=20 src addr = 172.16.1.66 @@ -59,8 +59,8 @@ label= export sysid = 1 size = 172 - first=1089541810 [2004-07-11 10:30:10] - last =1089541830 [2004-07-11 10:30:30] + first=1089534610 [2004-07-11 10:30:10] + last =1089534630 [2004-07-11 10:30:30] msec_first = 110 msec_last= 120 src addr = 172.16.2.66 @@ -114,8 +114,8 @@ label= export sysid = 1 size = 172 - first=1089541820 [2004-07-11 10:30:20] - last =1089541850 [2004-07-11 10:30:50] + first=1089534620 [2004-07-11 10:30:20] + last =1089534650 [2004-07-11 10:30:50] msec_first = 210 msec_last= 220 src addr = 172.16.2.66 @@ -169,8 +169,8 @@ label= export sysid = 1 size = 172 - first=1089541830 [2004-07-11 10:30:30] - last =1089541870 [2004-07-11 10:31:10] + first=1089534630 [2004-07-11 10:30:30] + last =1089534670 [2004-07-11 10:31:10] msec_first = 310 msec_last= 320 src addr = 172.16.3.66 @@ -224,8 +224,8 @@ label= export sysid = 1 size = 172 - first=1089541840 [2004-07-11 10:30:40] - last =1089541890 [2004-07-11 10:31:30] + first=1089534640 [2004-07-11 10:30:40] + last =1089534690 [2004-07-11 10:31:30] msec_first = 410 msec_last= 420 src addr = 172.16.4.66 @@ -279,8 +279,8 @@ label= export sysid = 1 size = 172 - first=1089541850 [2004-07-11 10:30:50] - last =1089541910 [2004-07-11 10:31:50] + first=1089534650 [2004-07-11 10:30:50] + last =1089534710 [2004-07-11 10:31:50] msec_first = 510 msec_last= 520 src addr = 172.16.5.66 @@ -334,8 +334,8 @@ label= export sysid = 1 size = 172 - first=1089541860 [2004-07-11 10:31:00] - last =1089541930 [2004-07-11 10:32:10] + first=1089534660 [2004-07-11 10:31:00] + last =1089534730 [2004-07-11 10:32:10] msec_first = 610 msec_last= 620 src addr = 172.16.6.66 @@ -389,8 +389,8 @@ label= export sysid = 1 size = 172 - first=1089541870 [2004-07-11 10:31:10] - last =1089541950 [2004-07-11 10:32:30] + first=1089534670 [2004-07-11 10:31:10] + last =1089534750 [2004-07-11 10:32:30] msec_first = 710 msec_last= 720 src addr = 172.16.7.66 @@ -444,8 +444,8 @@ label= export sysid = 1 size = 172 - first=1089541880 [2004-07-11 10:31:20] - last =1089541970 [2004-07-11 10:32:50] + first=1089534680 [2004-07-11 10:31:20] + last =1089534770 [2004-07-11 10:32:50] msec_first = 810 msec_last= 820 src addr = 172.16.8.66 @@ -499,8 +499,8 @@ label= export sysid = 1 size = 172 - first=1089541890 [2004-07-11 10:31:30] - last =1089541990 [2004-07-11 10:33:10] + first=1089534690 [2004-07-11 10:31:30] + last =1089534790 [2004-07-11 10:33:10] msec_first =
Bug#1027377: miller: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:miller Version: 5.10.0-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-arch dh binary-arch dh_update_autotools_config -a dh_autoreconf -a [...] Differences between ./expected/out and /<>/c/reg_test/output-regtest/out: *** ./expected/out 2020-11-29 20:56:56.0 + --- /<>/c/reg_test/output-regtest/out 2022-07-15 11:48:14.641689838 + *** *** 24879,24942 DSL LOCAL DATE/TIME FUNCTIONS mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b) a b c d ! 2017-02-18 23:00:00 1487469600.00 2017-02-18 23:00:00 2017-02-18 ! 2017-02-18 23:59:59 1487473199.00 2017-02-18 23:59:59 2017-02-18 ! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00 2017-02-19 ! 2017-02-19 00:30:00 1487475000.00 2017-02-19 00:30:00 2017-02-19 ! 2017-02-19 01:00:00 1487476800.00 2017-02-19 01:00:00 2017-02-19 ! 2017-10-14 23:00:00 1508032800.00 2017-10-14 23:00:00 2017-10-14 ! 2017-10-14 23:59:59 1508036399.00 2017-10-14 23:59:59 2017-10-14 ! 2017-10-15 00:00:00 1508036400.00 2017-10-15 01:00:00 2017-10-15 ! 2017-10-15 00:30:00 1508038200.00 2017-10-15 01:30:00 2017-10-15 ! 2017-10-15 01:00:00 150804.00 2017-10-15 02:00:00 2017-10-15 mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b) a b c d ! 2017-02-14 00:00:00 1487041200.00 2017-02-14 01:00:00 2017-02-14 ! 2017-02-15 00:00:00 1487127600.00 2017-02-15 01:00:00 2017-02-15 ! 2017-02-16 00:00:00 1487214000.00 2017-02-16 01:00:00 2017-02-16 ! 2017-02-17 00:00:00 1487300400.00 2017-02-17 01:00:00 2017-02-17 ! 2017-02-18 00:00:00 1487386800.00 2017-02-18 01:00:00 2017-02-18 ! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00 2017-02-19 ! 2017-02-20 00:00:00 1487559600.00 2017-02-20 00:00:00 2017-02-20 ! 2017-10-12 00:00:00 150200.00 2017-10-12 00:00:00 2017-10-12 ! 2017-10-13 00:00:00 1507863600.00 2017-10-13 00:00:00 2017-10-13 ! 2017-10-14 00:00:00 150795.00 2017-10-14 00:00:00 2017-10-14 ! 2017-10-15 00:00:00 1508036400.00 2017-10-15 01:00:00 2017-10-15 ! 2017-10-16 00:00:00 1508122800.00 2017-10-16 01:00:00 2017-10-16 ! 2017-10-17 00:00:00 1508209200.00 2017-10-17 01:00:00 2017-10-17 ! 2017-10-18 00:00:00 1508295600.00 2017-10-18 01:00:00 2017-10-18 ! 2017-10-19 00:00:00 1508382000.00 2017-10-19 01:00:00 2017-10-19 mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S") a b c ! 2017-02-18 23:00:00 1487469600.00 2017-02-18 23:00:00 ! 2017-02-18 23:59:59 1487473199.00 2017-02-18 23:59:59 ! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00 ! 2017-02-19 00:30:00 1487475000.00 2017-02-19 00:30:00 ! 2017-02-19 01:00:00 1487476800.00 2017-02-19 01:00:00 ! 2017-10-14 23:00:00 1508032800.00 2017-10-14 23:00:00 ! 2017-10-14 23:59:59 1508036399.00 2017-10-14 23:59:59 ! 2017-10-15 00:00:00 1508036400.00 2017-10-15 01:00:00 ! 2017-10-15 00:30:00 1508038200.00 2017-10-15 01:30:00 ! 2017-10-15 01:00:00 150804.00 2017-10-15 02:00:00 mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S") a b c ! 2017-02-18 23:00:00 1487469600.00 2017-02-18 23:00:00 ! 2017-02-18 23:59:59 1487473199.00 2017-02-18 23:59:59 ! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00 ! 2017-02-19 00:30:00 1487475000.00 2017-02-19 00:30:00 ! 2017-02-19 01:00:00 1487476800.00 2017-02-19 01:00:00 ! 2017-10-14 23:00:00 1508032800.00 2017-10-14 23:00:00 ! 2017-10-14 23:59:59 1508036399.00 2017-10-14 23:59:59 ! 2017-10-15 00:00:00 1508036400.00 2017-10-15 01:00:00 ! 2017-10-15 00:30:00 1508038200.00 2017-10-15 01:30:00 ! 2017-10-15 01:00:00 150804.00 2017-10-15 02:00:00 DSL SUB/GSUB/REGEX_EXTRACT --- 24879,24942 DSL LOCAL DATE/TIME FUNCTIONS mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b) a b c d ! 2017-02-18 23:00:00 1487458800.00 2017-02-18 23:00:00 2017-02-18 ! 2017-02-18 23:59:59 1487462399.00 2017-02-18 23:59:59 2017-02-18 ! 2017-02-19 00:00:00 1487462400.00 2017-02-19 00:00:00 2017-02-19 ! 2017-02-19 00:30:00 1487464200.00 2017-02-19
Bug#1027376: hugo: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:hugo Version: 0.80.0-6 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-arch dh binary-arch --builddirectory=_build --buildsystem=golang --with bash-completion,golang dh_update_autotools_config -a -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -a -O--builddirectory=_build -O--buildsystem=golang [...] === CONT TestTimeLocation time_test.go:49: [1] AsTime failed: unknown time zone America/New_York time_test.go:49: [2] AsTime failed: unknown time zone America/New_York time_test.go:49: [4] AsTime failed: unknown time zone America/New_York time_test.go:49: [6] AsTime failed: unknown time zone America/New_York --- FAIL: TestTimeLocation (0.00s) FAIL FAILgithub.com/gohugoio/hugo/tpl/time 0.026s [...] PASS ok github.com/gohugoio/hugo/transform/urlreplacers 0.030s ? github.com/gohugoio/hugo/watcher[no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 -test.short -timeout 120m github.com/gohugoio/hugo github.com/gohugoio/hugo/bufferpool github.com/gohugoio/hugo/cache/filecache github.com/gohugoio/hugo/cache/namedmemcache github.com/gohugoio/hugo/codegen github.com/gohugoio/hugo/commands github.com/gohugoio/hugo/common/collections github.com/gohugoio/hugo/common/constants github.com/gohugoio/hugo/common/herrors github.com/gohugoio/hugo/common/hexec github.com/gohugoio/hugo/common/hreflect github.com/gohugoio/hugo/common/hugio github.com/gohugoio/hugo/common/hugo github.com/gohugoio/hugo/common/loggers github.com/gohugoio/hugo/common/maps github.com/gohugoio/hugo/common/math github.com/gohugoio/hugo/common/para github.com/gohugoio/hugo/common/terminal github.com/gohugoio/hugo/common/text github.com/gohugoio/hugo/common/types github.com/gohugoio/hugo/common/urls github.com/gohugoio/hugo/compare github.com/gohugoio/hugo/config github.com/gohugoio/hugo/config/privacy github.com/gohugoio/hugo/config/services github.com/gohugoio/hugo/create github.com/gohugoio/hugo/deploy github.com/gohugoio/hugo/deps github.com/gohugoio/hugo/docshelper github.com/gohugoio/hugo/helpers github.com/gohugoio/hugo/htesting github.com/gohugoio/hugo/htesting/hqt github.com/gohugoio/hugo/hugofs github.com/gohugoio/hugo/hugofs/files github.com/gohugoio/hugo/hugofs/glob github.com/gohugoio/hugo/hugolib github.com/gohugoio/hugo/hugolib/filesystems github.com/gohugoio/hugo/hugolib/paths github.com/gohugoio/hugo/identity github.com/gohugoio/hugo/langs github.com/gohugoio/hugo/langs/i18n github.com/gohugoio/hugo/lazy github.com/gohugoio/hugo/livereload github.com/gohugoio/hugo/markup github.com/gohugoio/hugo/markup/asciidocext github.com/gohugoio/hugo/markup/asciidocext/asciidocext_config github.com/gohugoio/hugo/markup/blackfriday github.com/gohugoio/hugo/markup/blackfriday/blackfriday_config github.com/gohugoio/hugo/markup/converter github.com/gohugoio/hugo/markup/converter/hooks github.com/gohugoio/hugo/markup/goldmark github.com/gohugoio/hugo/markup/goldmark/goldmark_config github.com/gohugoio/hugo/markup/highlight github.com/gohugoio/hugo/markup/internal github.com/gohugoio/hugo/markup/markup_config github.com/gohugoio/hugo/markup/mmark github.com/gohugoio/hugo/markup/org github.com/gohugoio/hugo/markup/pandoc github.com/gohugoio/hugo/markup/rst github.com/gohugoio/hugo/markup/tableofcontents github.com/gohugoio/hugo/media github.com/gohugoio/hugo/metrics github.com/gohugoio/hugo/minifiers github.com/gohugoio/hugo/modules github.com/gohugoio/hugo/modules/npm github.com/gohugoio/hugo/navigation github.com/gohugoio/hugo/output github.com/gohugoio/hugo/parser github.com/gohugoio/hugo/parser/metadecoders github.com/gohugoio/hugo/parser/pageparser github.com/gohugoio/hugo/publisher github.com/gohugoio/hugo/related github.com/gohugoio/hugo/releaser github.com/gohugoio/hugo/resources github.com/gohugoio/hugo/resources/images github.com/gohugoio/hugo/resources/images/exif github.com/gohugoio/hugo/resources/internal github.com/gohugoio/hugo/resources/jsconfig github.com/gohugoio/hugo/resources/page github.com/gohugoio/hugo/resources/page/page_generate github.com/gohugoio/hugo/resources/page/pagemeta github.com/gohugoio/hugo/resources/postpub github.com/gohugoio/hugo/resources/resource github.com/gohugoio/hugo/resources/resource_factories/bundler github.com/gohugoio/hugo/resources/resource_factories/create github.com/gohugoio/hugo/resources/resource_transformers/babel github.com/gohugoio/hugo/resources/resource_transformers/htesting github.com/gohugoio/hugo/resources/resource_transformers/integrity github.com/gohugoio/hugo/resources/resource_transformers/js github.com/gohugoio/hugo/resources/resource_transformers/minifier github.com/gohugoio/hugo/resources/resource_transformers/postcss
Bug#1027375: golang-gopkg-libgit2-git2go.v31: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-gopkg-libgit2-git2go.v31 Version: 31.4.3-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang install -d /<>/debian/.debhelper/generated/_source/home install -d obj-x86_64-linux-gnu Copy status.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/status.go Copy difflinetype_string.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/difflinetype_string.go Copy git_system_dynamic.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/git_system_dynamic.go Copy revparse_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/revparse_test.go Copy diff_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/diff_test.go Copy clone.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/clone.go Copy reference_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/reference_test.go Copy mempack_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/mempack_test.go Copy odb_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/odb_test.go Copy diff.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/diff.go Copy wrapper.c -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/wrapper.c Copy note_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/note_test.go Copy object.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/object.go Copy tag_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/tag_test.go Copy clone_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/clone_test.go Copy push_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/push_test.go Copy config_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/config_test.go Copy blob_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/blob_test.go Copy branch_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/branch_test.go Copy index_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/index_test.go Copy tree.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/tree.go Copy describe_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/describe_test.go Copy packbuilder.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/packbuilder.go Copy message_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/message_test.go Copy cherrypick_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/cherrypick_test.go Copy patch.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/patch.go Copy index.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/index.go Copy merge.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/merge.go Copy ignore.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/ignore.go Copy rebase.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/rebase.go Copy handles.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/handles.go Copy settings_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/settings_test.go Copy indexer_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/indexer_test.go Copy reference.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/reference.go Copy signature.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/signature.go Copy remote_test.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/remote_test.go Copy odb.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/odb.go Copy delta_string.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/delta_string.go Copy git.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/git.go Copy reset.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/reset.go Copy graph.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/graph.go Copy branch.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/branch.go Copy repository.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/repository.go Copy refdb.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/refdb.go Copy errorcode_string.go -> obj-x86_64-linux-gnu/src/gopkg.in/libgit2/git2go.v31/errorcode_string.go Copy checkout.go ->
Bug#1027373: golang-github-viant-toolbox: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-viant-toolbox Version: 0.33.2-3 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2 github.com/viant/toolbox github.com/viant/toolbox/bridge github.com/viant/toolbox/cred github.com/viant/toolbox/data github.com/viant/toolbox/data/udf github.com/viant/toolbox/kms github.com/viant/toolbox/kms/aws github.com/viant/toolbox/kms/gcp github.com/viant/toolbox/sampler github.com/viant/toolbox/secret github.com/viant/toolbox/ssh github.com/viant/toolbox/storage github.com/viant/toolbox/storage/gs github.com/viant/toolbox/storage/s3 github.com/viant/toolbox/storage/scp github.com/viant/toolbox/test/fileset_info github.com/viant/toolbox/url internal/unsafeheader internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math internal/race sync/atomic runtime unicode unicode/utf8 math/bits math internal/testlog encoding unicode/utf16 internal/nettrace runtime/cgo container/list crypto/internal/subtle crypto/subtle vendor/golang.org/x/crypto/cryptobyte/asn1 vendor/golang.org/x/crypto/internal/subtle golang.org/x/crypto/internal/subtle github.com/aws/aws-sdk-go/aws/client/metadata github.com/aws/aws-sdk-go/internal/sdkmath google.golang.org/grpc/serviceconfig golang.org/x/sys/internal/unsafeheader github.com/golang/groupcache/lru go.opencensus.io go.opencensus.io/trace/internal go.opencensus.io/internal/tagencoding internal/reflectlite sync math/rand internal/singleflight github.com/aws/aws-sdk-go/internal/sync/singleflight errors sort io strconv bytes strings reflect bufio internal/oserror syscall internal/syscall/unix time internal/fmtsort internal/syscall/execenv encoding/binary encoding/base64 path container/heap regexp/syntax internal/poll os regexp fmt path/filepath io/ioutil encoding/csv encoding/json github.com/go-errors/errors github.com/pkg/errors go/token go/scanner go/ast math/big go/parser gopkg.in/yaml.v2 go/constant go/types log context vendor/golang.org/x/net/dns/dnsmessage net compress/flate hash hash/crc32 compress/gzip crypto/cipher crypto/aes crypto/rand crypto crypto/des crypto/elliptic crypto/internal/randutil crypto/sha512 encoding/asn1 vendor/golang.org/x/crypto/cryptobyte crypto/ecdsa crypto/ed25519/internal/edwards25519 crypto/ed25519 crypto/hmac crypto/md5 crypto/rc4 crypto/rsa crypto/sha1 crypto/sha256 crypto/dsa encoding/hex crypto/x509/pkix encoding/pem net/url vendor/golang.org/x/crypto/chacha20 vendor/golang.org/x/crypto/poly1305 crypto/x509 vendor/golang.org/x/sys/cpu vendor/golang.org/x/crypto/chacha20poly1305 vendor/golang.org/x/crypto/curve25519 vendor/golang.org/x/crypto/hkdf vendor/golang.org/x/text/transform crypto/tls vendor/golang.org/x/text/unicode/bidi vendor/golang.org/x/text/secure/bidirule vendor/golang.org/x/text/unicode/norm vendor/golang.org/x/net/idna net/textproto vendor/golang.org/x/net/http/httpguts vendor/golang.org/x/net/http/httpproxy vendor/golang.org/x/net/http2/hpack mime mime/quotedprintable net/http/httptrace net/http/internal mime/multipart os/signal golang.org/x/crypto/blowfish golang.org/x/crypto/chacha20 net/http golang.org/x/crypto/curve25519 golang.org/x/crypto/ed25519 golang.org/x/crypto/poly1305 golang.org/x/crypto/ssh/internal/bcrypt_pbkdf golang.org/x/crypto/ssh golang.org/x/oauth2/jws os/user net/http/httputil github.com/viant/toolbox cloud.google.com/go/compute/metadata golang.org/x/net/context/ctxhttp golang.org/x/oauth2/internal golang.org/x/oauth2 golang.org/x/oauth2/jwt golang.org/x/oauth2/google github.com/aws/aws-sdk-go/aws/awserr github.com/aws/aws-sdk-go/internal/ini github.com/aws/aws-sdk-go/internal/shareddefaults github.com/aws/aws-sdk-go/aws/credentials github.com/aws/aws-sdk-go/aws/endpoints github.com/viant/toolbox/bridge github.com/viant/toolbox/cred github.com/viant/toolbox/data github.com/viant/toolbox/data/udf github.com/viant/toolbox/kms github.com/aws/aws-sdk-go/internal/sdkio github.com/jmespath/go-jmespath github.com/aws/aws-sdk-go/aws/awsutil github.com/aws/aws-sdk-go/internal/sdkrand os/exec github.com/aws/aws-sdk-go/aws/credentials/processcreds github.com/aws/aws-sdk-go/internal/strings encoding/xml github.com/aws/aws-sdk-go/internal/sdkuri archive/tar archive/zip github.com/aws/aws-sdk-go/aws github.com/aws/aws-sdk-go/aws/request github.com/viant/toolbox/storage github.com/viant/toolbox/url github.com/aws/aws-sdk-go/aws/client github.com/aws/aws-sdk-go/aws/corehandlers github.com/aws/aws-sdk-go/private/protocol github.com/aws/aws-sdk-go/aws/csm
Bug#1027374: golang-github-xenolf-lego: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-xenolf-lego Version: 3.2.0-3.1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --buildsystem=golang --with=golang --builddirectory=_build dh_update_autotools_config -i -O--buildsystem=golang -O--builddirectory=_build dh_autoreconf -i -O--buildsystem=golang -O--builddirectory=_build [...] === RUN TestChangeResourceRecordSets client_test.go:40: Error Trace:client_test.go:40 Error: Received unexpected error: an error occurred during the creation of the signature: unknown time zone GMT Test: TestChangeResourceRecordSets --- FAIL: TestChangeResourceRecordSets (0.00s) === RUN TestChangeResourceRecordSetsErrors === RUN TestChangeResourceRecordSetsErrors/API_error client_test.go:94: Error Trace:client_test.go:94 Error: Error message not equal: expected: "an error occurred: The request signature we calculated does not match the signature you provided." actual : "an error occurred during the creation of the signature: unknown time zone GMT" Test: TestChangeResourceRecordSetsErrors/API_error === RUN TestChangeResourceRecordSetsErrors/response_body_error client_test.go:94: Error Trace:client_test.go:94 Error: Error message not equal: expected: "an error occurred while unmarshaling the response body to XML: EOF" actual : "an error occurred during the creation of the signature: unknown time zone GMT" Test: TestChangeResourceRecordSetsErrors/response_body_error === RUN TestChangeResourceRecordSetsErrors/error_message_error client_test.go:94: Error Trace:client_test.go:94 Error: Error message not equal: expected: "an error occurred while unmarshaling the error body to XML: EOF" actual : "an error occurred during the creation of the signature: unknown time zone GMT" Test: TestChangeResourceRecordSetsErrors/error_message_error --- FAIL: TestChangeResourceRecordSetsErrors (0.00s) --- FAIL: TestChangeResourceRecordSetsErrors/API_error (0.00s) --- FAIL: TestChangeResourceRecordSetsErrors/response_body_error (0.00s) --- FAIL: TestChangeResourceRecordSetsErrors/error_message_error (0.00s) === RUN TestGetChange client_test.go:119: Error Trace:client_test.go:119 Error: Received unexpected error: an error occurred during the creation of the signature: unknown time zone GMT Test: TestGetChange --- FAIL: TestGetChange (0.00s) [...] === RUN TestRegistrar_ResolveAccountByKey 2022/07/15 11:56:30 [INFO] acme: Trying to resolve account by key --- PASS: TestRegistrar_ResolveAccountByKey (0.01s) PASS ok github.com/go-acme/lego/registration0.014s FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 github.com/go-acme/lego/acme github.com/go-acme/lego/acme/api github.com/go-acme/lego/acme/api/internal/nonces github.com/go-acme/lego/acme/api/internal/secure github.com/go-acme/lego/acme/api/internal/sender github.com/go-acme/lego/certcrypto github.com/go-acme/lego/certificate github.com/go-acme/lego/challenge github.com/go-acme/lego/challenge/dns01 github.com/go-acme/lego/challenge/http01 github.com/go-acme/lego/challenge/resolver github.com/go-acme/lego/challenge/tlsalpn01 github.com/go-acme/lego/cmd github.com/go-acme/lego/cmd/lego github.com/go-acme/lego/internal github.com/go-acme/lego/lego github.com/go-acme/lego/log github.com/go-acme/lego/platform/config/env github.com/go-acme/lego/platform/tester github.com/go-acme/lego/platform/wait github.com/go-acme/lego/providers/dns github.com/go-acme/lego/providers/dns/autodns github.com/go-acme/lego/providers/dns/bluecat github.com/go-acme/lego/providers/dns/cloudns github.com/go-acme/lego/providers/dns/cloudns/internal github.com/go-acme/lego/providers/dns/cloudxns github.com/go-acme/lego/providers/dns/cloudxns/internal github.com/go-acme/lego/providers/dns/conoha github.com/go-acme/lego/providers/dns/conoha/internal github.com/go-acme/lego/providers/dns/digitalocean github.com/go-acme/lego/providers/dns/dnsmadeeasy github.com/go-acme/lego/providers/dns/dnsmadeeasy/internal github.com/go-acme/lego/providers/dns/dode github.com/go-acme/lego/providers/dns/dreamhost github.com/go-acme/lego/providers/dns/duckdns
Bug#1027372: golang-github-teambition-rrule-go: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-teambition-rrule-go Version: 1.6.0-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/teambition/rrule-go internal/unsafeheader internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math math/bits math runtime unicode/utf8 internal/race sync/atomic unicode internal/testlog internal/reflectlite sync errors sort strconv io internal/oserror syscall reflect internal/syscall/unix time internal/poll internal/fmtsort internal/syscall/execenv strings os fmt github.com/teambition/rrule-go dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/teambition/rrule-go === RUN TestNoDtstart --- PASS: TestNoDtstart (0.00s) === RUN TestBadBySetPos --- PASS: TestBadBySetPos (0.00s) === RUN TestBadBySetPosMany --- PASS: TestBadBySetPosMany (0.00s) === RUN TestByNegativeMonthDay --- PASS: TestByNegativeMonthDay (0.00s) === RUN TestMonthlyMaxYear --- PASS: TestMonthlyMaxYear (0.00s) === RUN TestWeeklyMaxYear --- PASS: TestWeeklyMaxYear (0.70s) === RUN TestInvalidRRules === RUN TestInvalidRRules/Bysecond_under === RUN TestInvalidRRules/Bysecond_over === RUN TestInvalidRRules/Byminute_under === RUN TestInvalidRRules/Byminute_over === RUN TestInvalidRRules/Byhour_under === RUN TestInvalidRRules/Byhour_over === RUN TestInvalidRRules/Bymonthday_under === RUN TestInvalidRRules/Bymonthday_over === RUN TestInvalidRRules/Bymonthday_under_negative === RUN TestInvalidRRules/Byyearday_under === RUN TestInvalidRRules/Byyearday_over === RUN TestInvalidRRules/Byyearday_under_negative === RUN TestInvalidRRules/Byweekno_under === RUN TestInvalidRRules/Byweekno_over === RUN TestInvalidRRules/Byweekno_under_negative === RUN TestInvalidRRules/Bymonth_under === RUN TestInvalidRRules/Bymonth_over === RUN TestInvalidRRules/Bysetpos_under === RUN TestInvalidRRules/Bysetpos_over === RUN TestInvalidRRules/Bysetpos_under_negative === RUN TestInvalidRRules/Byday_under === RUN TestInvalidRRules/Byday_over === RUN TestInvalidRRules/Interval_under --- PASS: TestInvalidRRules (0.00s) --- PASS: TestInvalidRRules/Bysecond_under (0.00s) --- PASS: TestInvalidRRules/Bysecond_over (0.00s) --- PASS: TestInvalidRRules/Byminute_under (0.00s) --- PASS: TestInvalidRRules/Byminute_over (0.00s) --- PASS: TestInvalidRRules/Byhour_under (0.00s) --- PASS: TestInvalidRRules/Byhour_over (0.00s) --- PASS: TestInvalidRRules/Bymonthday_under (0.00s) --- PASS: TestInvalidRRules/Bymonthday_over (0.00s) --- PASS: TestInvalidRRules/Bymonthday_under_negative (0.00s) --- PASS: TestInvalidRRules/Byyearday_under (0.00s) --- PASS: TestInvalidRRules/Byyearday_over (0.00s) --- PASS: TestInvalidRRules/Byyearday_under_negative (0.00s) --- PASS: TestInvalidRRules/Byweekno_under (0.00s) --- PASS: TestInvalidRRules/Byweekno_over (0.00s) --- PASS: TestInvalidRRules/Byweekno_under_negative (0.00s) --- PASS: TestInvalidRRules/Bymonth_under (0.00s) --- PASS: TestInvalidRRules/Bymonth_over (0.00s) --- PASS: TestInvalidRRules/Bysetpos_under (0.00s) --- PASS: TestInvalidRRules/Bysetpos_over (0.00s) --- PASS: TestInvalidRRules/Bysetpos_under_negative (0.00s) --- PASS: TestInvalidRRules/Byday_under (0.00s) --- PASS: TestInvalidRRules/Byday_over (0.00s) --- PASS: TestInvalidRRules/Interval_under (0.00s) === RUN TestHourlyInvalidAndRepeatedBysetpos --- PASS: TestHourlyInvalidAndRepeatedBysetpos (0.00s) === RUN TestNoAfter --- PASS: TestNoAfter (0.00s) === RUN TestYearly --- PASS: TestYearly (0.00s) === RUN TestYearlyInterval --- PASS: TestYearlyInterval (0.00s) === RUN TestYearlyIntervalLarge --- PASS: TestYearlyIntervalLarge (0.00s) === RUN TestYearlyByMonth --- PASS: TestYearlyByMonth (0.00s) === RUN TestYearlyByMonthDay --- PASS: TestYearlyByMonthDay (0.00s) === RUN TestYearlyByMonthAndMonthDay --- PASS: TestYearlyByMonthAndMonthDay (0.00s) === RUN TestYearlyByWeekDay --- PASS: TestYearlyByWeekDay (0.00s) === RUN TestYearlyByNWeekDay --- PASS: TestYearlyByNWeekDay (0.00s) === RUN TestYearlyByNWeekDayLarge --- PASS: TestYearlyByNWeekDayLarge (0.00s) === RUN TestYearlyByMonthAndWeekDay --- PASS: TestYearlyByMonthAndWeekDay (0.00s) === RUN TestYearlyByMonthAndNWeekDay --- PASS:
Bug#1027371: golang-github-tealeg-xlsx: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-tealeg-xlsx
Version: 1.0.3+git20181024.dbf71b6-1.1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
dh_update_autotools_config -i -O--buildsystem=golang
dh_autoreconf -i -O--buildsystem=golang
dh_auto_configure -i -O--buildsystem=golang
dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2
github.com/tealeg/xlsx
internal/unsafeheader
internal/cpu
runtime/internal/atomic
internal/bytealg
runtime/internal/sys
runtime/internal/math
internal/race
sync/atomic
unicode
runtime
unicode/utf8
math/bits
math
internal/testlog
encoding
image/color
internal/reflectlite
sync
errors
sort
io
strconv
bytes
strings
reflect
bufio
internal/oserror
syscall
internal/syscall/unix
time
internal/fmtsort
internal/syscall/execenv
encoding/binary
hash
hash/crc32
internal/poll
path
os
fmt
path/filepath
io/ioutil
compress/flate
encoding/xml
archive/zip
github.com/tealeg/xlsx
dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2
github.com/tealeg/xlsx
=== RUN Test
--
FAIL: cell_test.go:740: CellSuite.TestSetDateWithOptions
cell_test.go:754:
c.Assert(err, IsNil)
... value *errors.errorString = {s:"unknown time zone
America/New_York"} ("unknown time zone America/New_York")
OOPS: 173 passed, 1 FAILED
--- FAIL: Test (1.36s)
=== RUN TestFuzzCrashers
--- PASS: TestFuzzCrashers (0.00s)
FAIL
FAILgithub.com/tealeg/xlsx 1.362s
FAIL
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2
github.com/tealeg/xlsx returned exit code 1
make: *** [debian/rules:4: build-indep] Error 25
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)
Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).
About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
Bug#1027370: golang-github-powerman-check: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-powerman-check Version: 1.2.1-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/powerman/check internal/unsafeheader internal/cpu runtime/internal/atomic internal/bytealg runtime/internal/sys runtime/internal/math internal/race runtime sync/atomic unicode unicode/utf8 encoding math/bits math internal/testlog unicode/utf16 golang.org/x/sys/internal/unsafeheader internal/reflectlite sync errors sort io strconv bytes internal/oserror syscall reflect internal/syscall/unix time encoding/binary internal/fmtsort internal/poll encoding/base64 internal/syscall/execenv strings os regexp/syntax fmt regexp encoding/json flag encoding/hex github.com/davecgh/go-spew/spew path github.com/pkg/errors bufio github.com/smartystreets/goconvey/convey/gotest github.com/smartystreets/goconvey/convey/reporting github.com/pmezard/go-difflib/difflib path/filepath golang.org/x/sys/unix io/ioutil runtime/debug context runtime/trace testing github.com/powerman/check dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/powerman/check panic: time: missing Location in call to Time.In goroutine 1 [running]: time.Time.In(0xc0ac7376985035d0, 0xa8c01, 0x715b20, 0x0, 0x6f93a0, 0xcd1f18, 0x1) /usr/lib/go-1.15/src/time/time.go:1099 +0xb2 github.com/powerman/check_test.init() /<>/_build/src/github.com/powerman/check/check_test.go:150 +0x236 FAILgithub.com/powerman/check 0.007s FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 github.com/powerman/check returned exit code 1 make: *** [debian/rules:4: binary-indep] Error 25 dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#1027368: golang-github-mitch000001-go-hbci: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-mitch01-go-hbci Version: 0.3.2-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2 github.com/mitch01/go-hbci github.com/mitch01/go-hbci/bankinfo github.com/mitch01/go-hbci/charset github.com/mitch01/go-hbci/client github.com/mitch01/go-hbci/cmd/bankdata_parser github.com/mitch01/go-hbci/cmd/banking github.com/mitch01/go-hbci/cmd/unmarshaler github.com/mitch01/go-hbci/crypto github.com/mitch01/go-hbci/dialog github.com/mitch01/go-hbci/domain github.com/mitch01/go-hbci/element github.com/mitch01/go-hbci/generator github.com/mitch01/go-hbci/generator/test_files github.com/mitch01/go-hbci/iban github.com/mitch01/go-hbci/internal github.com/mitch01/go-hbci/message github.com/mitch01/go-hbci/segment github.com/mitch01/go-hbci/swift github.com/mitch01/go-hbci/token github.com/mitch01/go-hbci/transport github.com/mitch01/go-hbci/transport/https github.com/mitch01/go-hbci/transport/middleware internal/unsafeheader internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math math/bits math runtime unicode/utf8 internal/race sync/atomic unicode internal/testlog encoding unicode/utf16 github.com/wildducktheories/go-csv/utils golang.org/x/text/encoding/internal/identifier crypto/internal/subtle crypto/subtle container/list vendor/golang.org/x/crypto/cryptobyte/asn1 internal/nettrace runtime/cgo vendor/golang.org/x/crypto/internal/subtle golang.org/x/sys/internal/unsafeheader internal/reflectlite sync math/rand internal/singleflight errors sort strconv io internal/oserror syscall reflect internal/syscall/unix time internal/poll internal/fmtsort internal/syscall/execenv strings os bytes fmt bufio path hash crypto flag log encoding/csv github.com/mitch01/go-hbci/internal github.com/mitch01/go-hbci github.com/pkg/errors encoding/binary regexp/syntax crypto/md5 encoding/base64 encoding/json regexp golang.org/x/text/transform github.com/wildducktheories/go-csv golang.org/x/text/encoding golang.org/x/text/encoding/internal golang.org/x/text/encoding/charmap github.com/mitch01/go-hbci/bankinfo crypto/cipher github.com/mitch01/go-hbci/charset math/big crypto/des crypto/aes crypto/internal/randutil net/url text/tabwriter github.com/mitch01/go-hbci/token golang.org/x/crypto/ripemd160 hash/crc32 path/filepath crypto/rand crypto/rsa io/ioutil compress/flate github.com/mitch01/go-hbci/domain github.com/mitch01/go-hbci/swift compress/gzip context crypto/elliptic github.com/mitch01/go-hbci/element crypto/sha512 encoding/asn1 github.com/mitch01/go-hbci/segment vendor/golang.org/x/crypto/cryptobyte crypto/ecdsa crypto/ed25519/internal/edwards25519 crypto/ed25519 crypto/hmac crypto/rc4 crypto/sha1 crypto/sha256 crypto/dsa encoding/hex crypto/x509/pkix github.com/mitch01/go-hbci/message encoding/pem vendor/golang.org/x/net/dns/dnsmessage github.com/mitch01/go-hbci/transport vendor/golang.org/x/crypto/chacha20 net vendor/golang.org/x/crypto/poly1305 vendor/golang.org/x/sys/cpu vendor/golang.org/x/crypto/chacha20poly1305 vendor/golang.org/x/crypto/curve25519 vendor/golang.org/x/crypto/hkdf vendor/golang.org/x/text/transform vendor/golang.org/x/text/unicode/bidi vendor/golang.org/x/text/secure/bidirule vendor/golang.org/x/text/unicode/norm vendor/golang.org/x/net/idna vendor/golang.org/x/net/http2/hpack mime mime/quotedprintable net/http/internal github.com/mitch01/go-hbci/transport/middleware go/token go/scanner go/ast crypto/x509 net/textproto vendor/golang.org/x/net/http/httpguts vendor/golang.org/x/net/http/httpproxy mime/multipart go/parser crypto/tls go/printer go/format text/template/parse text/template net/http/httptrace net/http github.com/mitch01/go-hbci/cmd/bankdata_parser github.com/mitch01/go-hbci/iban os/exec github.com/mitchellh/go-homedir github.com/spf13/pflag github.com/spf13/cobra golang.org/x/sys/unix github.com/mitch01/go-hbci/transport/https github.com/mitch01/go-hbci/dialog github.com/mitch01/go-hbci/client github.com/fsnotify/fsnotify github.com/hashicorp/hcl/hcl/strconv github.com/hashicorp/hcl/hcl/token github.com/magiconair/properties github.com/hashicorp/hcl/hcl/ast github.com/hashicorp/hcl/hcl/scanner github.com/hashicorp/hcl/hcl/parser github.com/hashicorp/hcl/json/token github.com/hashicorp/hcl/hcl/printer github.com/hashicorp/hcl/json/scanner github.com/hashicorp/hcl/json/parser
Bug#1027367: golang-github-jinzhu-gorm: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-jinzhu-gorm Version: 1.9.6-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2 github.com/jinzhu/gorm github.com/jinzhu/gorm/dialects/mssql github.com/jinzhu/gorm/dialects/mysql github.com/jinzhu/gorm/dialects/postgres github.com/jinzhu/gorm/dialects/sqlite internal/unsafeheader internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math internal/race sync/atomic unicode runtime unicode/utf8 math/bits math internal/testlog encoding unicode/utf16 crypto/internal/subtle crypto/subtle container/list vendor/golang.org/x/crypto/cryptobyte/asn1 internal/nettrace runtime/cgo vendor/golang.org/x/crypto/internal/subtle github.com/lib/pq/oid sync internal/reflectlite math/rand internal/singleflight errors sort io internal/oserror syscall bytes hash strconv crypto reflect time context internal/syscall/unix internal/poll internal/syscall/execenv os encoding/binary crypto/sha1 internal/fmtsort fmt encoding/base64 strings regexp/syntax database/sql/driver database/sql encoding/json regexp github.com/jinzhu/inflection go/token path/filepath log go/scanner crypto/cipher go/ast crypto/des crypto/md5 bufio github.com/jinzhu/gorm crypto/aes math/big crypto/rand crypto/elliptic crypto/internal/randutil crypto/sha512 encoding/asn1 crypto/ed25519/internal/edwards25519 vendor/golang.org/x/crypto/cryptobyte crypto/ed25519 crypto/hmac crypto/rc4 crypto/ecdsa crypto/rsa crypto/sha256 crypto/dsa encoding/hex encoding/pem crypto/x509/pkix io/ioutil vendor/golang.org/x/net/dns/dnsmessage net/url vendor/golang.org/x/crypto/chacha20 vendor/golang.org/x/crypto/poly1305 net vendor/golang.org/x/sys/cpu vendor/golang.org/x/crypto/chacha20poly1305 vendor/golang.org/x/crypto/curve25519 vendor/golang.org/x/crypto/hkdf golang.org/x/crypto/md4 golang.org/x/net/context github.com/lib/pq/scram os/user path github.com/lib/pq/hstore github.com/mattn/go-sqlite3 crypto/x509 crypto/tls github.com/denisenkom/go-mssqldb github.com/go-sql-driver/mysql github.com/jinzhu/gorm/dialects/mysql github.com/lib/pq github.com/jinzhu/gorm/dialects/mssql github.com/jinzhu/gorm/dialects/sqlite github.com/jinzhu/gorm/dialects/postgres dh_auto_test -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 github.com/jinzhu/gorm github.com/jinzhu/gorm/dialects/mssql github.com/jinzhu/gorm/dialects/mysql github.com/jinzhu/gorm/dialects/postgres github.com/jinzhu/gorm/dialects/sqlite testing sqlite3... [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:292)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: animals [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:292)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: user_languages [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: shorts [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: really_long_thing_that_references_shorts [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: really_long_table_name_to_test_my_sql_name_length_limits [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: not_so_long_table_names [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: products [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: emails [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: addresses [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: credit_cards [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: companies [0m [35m(/<>/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/migration_test.go:297)[0m [33m[2022-11-30 15:52:24][0m [31;1m no such table: roles [0m
Bug#1027369: golang-github-mohae-deepcopy: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-mohae-deepcopy Version: 0.0~git20170929.c48cc78-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/mohae/deepcopy internal/unsafeheader math/bits internal/cpu runtime/internal/atomic math internal/bytealg runtime/internal/sys runtime/internal/math runtime unicode/utf8 internal/race sync/atomic unicode internal/reflectlite sync errors strconv internal/oserror syscall reflect time github.com/mohae/deepcopy dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/mohae/deepcopy === RUN TestSimple --- PASS: TestSimple (0.00s) === RUN TestMostTypes --- PASS: TestMostTypes (0.00s) === RUN TestComplexSlices --- PASS: TestComplexSlices (0.00s) === RUN TestStructA --- PASS: TestStructA (0.00s) === RUN TestUnexportedFields --- PASS: TestUnexportedFields (0.00s) === RUN TestTimeCopy deepcopy_test.go:876: 0: unexpected error: unknown time zone America/New_York deepcopy_test.go:876: 2: unexpected error: unknown time zone Europe/Prague --- FAIL: TestTimeCopy (0.00s) === RUN TestPointerToStruct --- PASS: TestPointerToStruct (0.00s) === RUN TestIssue9 --- PASS: TestIssue9 (0.00s) === RUN TestInterface --- PASS: TestInterface (0.00s) FAIL FAILgithub.com/mohae/deepcopy 0.004s FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 github.com/mohae/deepcopy returned exit code 1 make: *** [debian/rules:4: binary-indep] Error 25 dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#1027366: golang-github-go-playground-validator-v10: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-go-playground-validator-v10 Version: 10.4.1-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/go-playground/validator/v10 github.com/go-playground/validator/v10/non-standard/validators github.com/go-playground/validator/v10/translations/en github.com/go-playground/validator/v10/translations/es github.com/go-playground/validator/v10/translations/fr github.com/go-playground/validator/v10/translations/id github.com/go-playground/validator/v10/translations/ja github.com/go-playground/validator/v10/translations/nl github.com/go-playground/validator/v10/translations/pt github.com/go-playground/validator/v10/translations/pt_BR github.com/go-playground/validator/v10/translations/ru github.com/go-playground/validator/v10/translations/tr github.com/go-playground/validator/v10/translations/zh github.com/go-playground/validator/v10/translations/zh_tw internal/unsafeheader internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math internal/race sync/atomic unicode runtime unicode/utf8 math/bits math internal/testlog encoding unicode/utf16 github.com/go-playground/locales/currency internal/nettrace runtime/cgo internal/reflectlite sync internal/singleflight math/rand errors sort io bytes internal/oserror syscall hash strconv crypto time reflect context internal/syscall/unix internal/poll internal/syscall/execenv os encoding/binary internal/fmtsort crypto/sha256 fmt strings encoding/base64 encoding/hex encoding/json github.com/go-playground/locales path/filepath io/ioutil golang.org/x/crypto/sha3 vendor/golang.org/x/net/dns/dnsmessage github.com/go-playground/universal-translator github.com/leodido/go-urn net/url net regexp/syntax regexp log github.com/go-playground/validator/v10 github.com/go-playground/validator/v10/non-standard/validators github.com/go-playground/validator/v10/translations/en github.com/go-playground/validator/v10/translations/es github.com/go-playground/validator/v10/translations/fr github.com/go-playground/validator/v10/translations/id github.com/go-playground/validator/v10/translations/ja github.com/go-playground/validator/v10/translations/nl github.com/go-playground/validator/v10/translations/pt github.com/go-playground/validator/v10/translations/pt_BR github.com/go-playground/validator/v10/translations/ru github.com/go-playground/validator/v10/translations/tr github.com/go-playground/validator/v10/translations/zh github.com/go-playground/validator/v10/translations/zh_tw dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/go-playground/validator/v10 github.com/go-playground/validator/v10/non-standard/validators github.com/go-playground/validator/v10/translations/en github.com/go-playground/validator/v10/translations/es github.com/go-playground/validator/v10/translations/fr github.com/go-playground/validator/v10/translations/id github.com/go-playground/validator/v10/translations/ja github.com/go-playground/validator/v10/translations/nl github.com/go-playground/validator/v10/translations/pt github.com/go-playground/validator/v10/translations/pt_BR github.com/go-playground/validator/v10/translations/ru github.com/go-playground/validator/v10/translations/tr github.com/go-playground/validator/v10/translations/zh github.com/go-playground/validator/v10/translations/zh_tw === RUN TestStructLevelInvalidError --- PASS: TestStructLevelInvalidError (0.00s) === RUN TestNameNamespace --- PASS: TestNameNamespace (0.00s) === RUN TestAnonymous --- PASS: TestAnonymous (0.00s) === RUN TestAnonymousSameStructDifferentTags --- PASS: TestAnonymousSameStructDifferentTags (0.00s) === RUN TestStructLevelReturnValidationErrors --- PASS: TestStructLevelReturnValidationErrors (0.00s) === RUN TestStructLevelReturnValidationErrorsWithJSON --- PASS: TestStructLevelReturnValidationErrorsWithJSON (0.00s) === RUN TestStructLevelValidations --- PASS: TestStructLevelValidations (0.00s) === RUN TestAliasTags --- PASS: TestAliasTags (0.00s) === RUN TestNilValidator --- PASS: TestNilValidator (0.00s) === RUN TestStructPartial --- PASS: TestStructPartial (0.00s) === RUN TestCrossStructLteFieldValidation --- PASS: TestCrossStructLteFieldValidation (0.00s) === RUN TestCrossStructLtFieldValidation --- PASS:
Bug#1027365: golang-github-go-playground-locales: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-go-playground-locales Version: 0.13.0-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang [...] === RUN TestFmtTimeFull en_test.go:673: Expected '' Got 'unknown time zone America/Toronto' --- FAIL: TestFmtTimeFull (0.00s) panic: time: missing Location in call to Date [recovered] panic: time: missing Location in call to Date goroutine 32 [running]: testing.tRunner.func1.1(0x52e540, 0x583590) /usr/lib/go-1.15/src/testing/testing.go:1072 +0x30d testing.tRunner.func1(0xc83c80) /usr/lib/go-1.15/src/testing/testing.go:1075 +0x41a panic(0x52e540, 0x583590) /usr/lib/go-1.15/src/runtime/panic.go:969 +0x1b9 time.Date(0x7e0, 0x2, 0x3, 0x9, 0x5, 0x1, 0x0, 0x0, 0x0, 0x4cf700, ...) /usr/lib/go-1.15/src/time/time.go:1344 +0x636 github.com/go-playground/locales/en.TestFmtTimeFull(0xc83c80) /<>/_build/src/github.com/go-playground/locales/en/en_test.go:683 +0x23a testing.tRunner(0xc83c80, 0x5637f0) /usr/lib/go-1.15/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/lib/go-1.15/src/testing/testing.go:1168 +0x2b3 FAILgithub.com/go-playground/locales/en 0.006s [...] --- PASS: TestFmtAccounting (0.00s) === RUN TestFmtPercent --- PASS: TestFmtPercent (0.00s) PASS ok github.com/go-playground/locales/zu_ZA 0.003s FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 github.com/go-playground/locales github.com/go-playground/locales/af github.com/go-playground/locales/af_NA github.com/go-playground/locales/af_ZA github.com/go-playground/locales/agq github.com/go-playground/locales/agq_CM github.com/go-playground/locales/ak github.com/go-playground/locales/ak_GH github.com/go-playground/locales/am github.com/go-playground/locales/am_ET github.com/go-playground/locales/ar github.com/go-playground/locales/ar_001 github.com/go-playground/locales/ar_AE github.com/go-playground/locales/ar_BH github.com/go-playground/locales/ar_DJ github.com/go-playground/locales/ar_DZ github.com/go-playground/locales/ar_EG github.com/go-playground/locales/ar_EH github.com/go-playground/locales/ar_ER github.com/go-playground/locales/ar_IL github.com/go-playground/locales/ar_IQ github.com/go-playground/locales/ar_JO github.com/go-playground/locales/ar_KM github.com/go-playground/locales/ar_KW github.com/go-playground/locales/ar_LB github.com/go-playground/locales/ar_LY github.com/go-playground/locales/ar_MA github.com/go-playground/locales/ar_MR github.com/go-playground/locales/ar_OM github.com/go-playground/locales/ar_PS github.com/go-playground/locales/ar_QA github.com/go-playground/locales/ar_SA github.com/go-playground/locales/ar_SD github.com/go-playground/locales/ar_SO github.com/go-playground/locales/ar_SS github.com/go-playground/locales/ar_SY github.com/go-playground/locales/ar_TD github.com/go-playground/locales/ar_TN github.com/go-playground/locales/ar_YE github.com/go-playground/locales/as github.com/go-playground/locales/as_IN github.com/go-playground/locales/asa github.com/go-playground/locales/asa_TZ github.com/go-playground/locales/ast github.com/go-playground/locales/ast_ES github.com/go-playground/locales/az github.com/go-playground/locales/az_Cyrl github.com/go-playground/locales/az_Cyrl_AZ github.com/go-playground/locales/az_Latn github.com/go-playground/locales/az_Latn_AZ github.com/go-playground/locales/bas github.com/go-playground/locales/bas_CM github.com/go-playground/locales/be github.com/go-playground/locales/be_BY github.com/go-playground/locales/bem github.com/go-playground/locales/bem_ZM github.com/go-playground/locales/bez github.com/go-playground/locales/bez_TZ github.com/go-playground/locales/bg github.com/go-playground/locales/bg_BG github.com/go-playground/locales/bm github.com/go-playground/locales/bm_ML github.com/go-playground/locales/bn github.com/go-playground/locales/bn_BD github.com/go-playground/locales/bn_IN github.com/go-playground/locales/bo github.com/go-playground/locales/bo_CN github.com/go-playground/locales/bo_IN github.com/go-playground/locales/br github.com/go-playground/locales/br_FR github.com/go-playground/locales/brx github.com/go-playground/locales/brx_IN github.com/go-playground/locales/bs github.com/go-playground/locales/bs_Cyrl github.com/go-playground/locales/bs_Cyrl_BA github.com/go-playground/locales/bs_Latn github.com/go-playground/locales/bs_Latn_BA github.com/go-playground/locales/ca github.com/go-playground/locales/ca_AD github.com/go-playground/locales/ca_ES
Bug#1027362: ganeti-instance-debootstrap: FTBFS in bullseye (missing build-depends on mount)
Package: src:ganeti-instance-debootstrap
Version: 0.16-6.1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
configure.ac:7: installing 'autotools/install-sh'
configure.ac:7: installing 'autotools/missing'
parallel-tests: installing 'autotools/test-driver'
dh_auto_configure -i
./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
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '924' is supported by ustar format... yes
checking whether GID '924' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether ln -s works... yes
checking for kpartx... /sbin/kpartx
checking for losetup... no
configure: error: losetup command not found
tail -v -n \+0 config.log
==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by ganeti-instance-debootstrap configure 0.16, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./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
--libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
## - ##
## Platform. ##
## - ##
hostname = hh1657834
uname -m = x86_64
uname -r = 5.10.0-16-amd64
uname -s = Linux
uname -v = #1 SMP Debian 5.10.127-1 (2022-06-30)
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
## --- ##
## Core tests. ##
## --- ##
configure:1798: checking for a BSD-compatible install
configure:1866: result: /usr/bin/install -c
configure:1877: checking whether build environment is sane
configure:1932: result: yes
configure:2078: checking for a thread-safe mkdir -p
configure:2117: result: /bin/mkdir -p
configure:2124: checking for gawk
configure:2154: result: no
configure:2124: checking for mawk
configure:2140: found /usr/bin/mawk
configure:2151: result: mawk
configure:2162: checking whether make sets $(MAKE)
configure:2184: result: yes
configure:2213: checking whether make supports nested variables
configure:2230: result: yes
configure:2319: checking whether UID '924' is supported by ustar format
configure:2322: result: yes
configure:2329: checking whether GID '924' is supported by ustar format
configure:2332: result: yes
configure:2340: checking how to create a ustar tar archive
configure:2351: tar --version
tar (GNU tar) 1.34
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
configure:2354: $? = 0
configure:2394: tardir=conftest.dir && eval tar --format=ustar -chf - "$tardir"
>conftest.tar
configure:2397: $? = 0
configure:2401: tar -xf - >/autotools/missing'\'' aclocal-1.16'
AMTAR='$${TAR-tar}'
AM_BACKSLASH='\'
AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
AM_DEFAULT_VERBOSITY='1'
AM_V='$(V)'
AUTOCONF='${SHELL} '\''/<>/autotools/missing'\'' autoconf'
AUTOHEADER='${SHELL} '\''/<>/autotools/missing'\'' autoheader'
AUTOMAKE='${SHELL} '\''/<>/autotools/missing'\'' automake-1.16'
AWK='mawk'
CYGPATH_W='echo'
DEBOOTSTRAP=''
DEFS=''
DUMP=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
KPARTX='/sbin/kpartx'
LIBOBJS=''
LIBS=''
LN_S='ln -s'
LOSETUP=''
LTLIBOBJS=''
MAKEINFO='${SHELL}
Bug#1027364: golang-github-go-co-op-gocron: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-go-co-op-gocron Version: 0.5.0-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/go-co-op/gocron internal/unsafeheader internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math internal/race sync/atomic math/bits runtime math unicode/utf8 unicode internal/testlog internal/reflectlite sync errors sort io strconv hash internal/oserror syscall crypto reflect internal/syscall/unix time encoding/binary internal/fmtsort internal/poll crypto/sha256 internal/syscall/execenv os bytes strings fmt regexp/syntax regexp github.com/go-co-op/gocron dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/go-co-op/gocron === RUN TestParseTime === RUN TestParseTime/normal === RUN TestParseTime/normal_-_no_leading_hour_zeros === RUN TestParseTime/normal_with_second === RUN TestParseTime/normal_with_second_-_no_leading_hour_zeros === RUN TestParseTime/not_a_number === RUN TestParseTime/out_of_range_hour === RUN TestParseTime/out_of_range_minute === RUN TestParseTime/wrong_format === RUN TestParseTime/wrong_minute === RUN TestParseTime/wrong_hour --- PASS: TestParseTime (0.00s) --- PASS: TestParseTime/normal (0.00s) --- PASS: TestParseTime/normal_-_no_leading_hour_zeros (0.00s) --- PASS: TestParseTime/normal_with_second (0.00s) --- PASS: TestParseTime/normal_with_second_-_no_leading_hour_zeros (0.00s) --- PASS: TestParseTime/not_a_number (0.00s) --- PASS: TestParseTime/out_of_range_hour (0.00s) --- PASS: TestParseTime/out_of_range_minute (0.00s) --- PASS: TestParseTime/wrong_format (0.00s) --- PASS: TestParseTime/wrong_minute (0.00s) --- PASS: TestParseTime/wrong_hour (0.00s) === RUN TestTags --- PASS: TestTags (0.00s) === RUN TestGetScheduledTime --- PASS: TestGetScheduledTime (0.00s) === RUN TestGetWeekday === RUN TestGetWeekday/success === RUN TestGetWeekday/fail_-_not_set_for_weekday --- PASS: TestGetWeekday (0.00s) --- PASS: TestGetWeekday/success (0.00s) --- PASS: TestGetWeekday/fail_-_not_set_for_weekday (0.00s) === RUN TestJob_shouldRunAgain === RUN TestJob_shouldRunAgain/should_run_again_(infinite) === RUN TestJob_shouldRunAgain/should_run_again_(finite) === RUN TestJob_shouldRunAgain/shouldn't_run_again_#1 === RUN TestJob_shouldRunAgain/shouldn't_run_again_#2 --- PASS: TestJob_shouldRunAgain (0.00s) --- PASS: TestJob_shouldRunAgain/should_run_again_(infinite) (0.00s) --- PASS: TestJob_shouldRunAgain/should_run_again_(finite) (0.00s) --- PASS: TestJob_shouldRunAgain/shouldn't_run_again_#1 (0.00s) --- PASS: TestJob_shouldRunAgain/shouldn't_run_again_#2 (0.00s) === RUN TestJob_LimitRunsTo --- PASS: TestJob_LimitRunsTo (0.00s) === RUN TestJob_CommonExports --- PASS: TestJob_CommonExports (0.00s) === RUN TestImmediateExecution --- PASS: TestImmediateExecution (0.00s) === RUN TestExecutionSeconds --- PASS: TestExecutionSeconds (6.00s) === RUN TestScheduled --- PASS: TestScheduled (0.00s) === RUN TestScheduledWithTag --- PASS: TestScheduledWithTag (0.00s) === RUN TestAtFuture === RUN TestAtFuture/calls_to_.At()_should_parse_time_correctly === RUN TestAtFuture/error_due_to_bad_time_format --- PASS: TestAtFuture (0.00s) --- PASS: TestAtFuture/calls_to_.At()_should_parse_time_correctly (0.00s) --- PASS: TestAtFuture/error_due_to_bad_time_format (0.00s) === RUN TestWeekdayBeforeToday --- PASS: TestWeekdayBeforeToday (0.00s) === RUN TestWeekdayAt === RUN TestWeekdayAt/asserts_weekday_scheduling_starts_at_the_current_week --- PASS: TestWeekdayAt (0.00s) --- PASS: TestWeekdayAt/asserts_weekday_scheduling_starts_at_the_current_week (0.00s) === RUN TestRemove --- PASS: TestRemove (0.00s) === RUN TestRemoveByRef --- PASS: TestRemoveByRef (0.00s) === RUN TestRemoveByTag --- PASS: TestRemoveByTag (0.00s) === RUN TestJobs --- PASS: TestJobs (0.00s) === RUN TestLen --- PASS: TestLen (0.00s) === RUN TestSwap --- PASS: TestSwap (0.00s) === RUN TestLess --- PASS: TestLess (0.00s) === RUN TestSetLocation --- PASS: TestSetLocation (0.00s) === RUN TestClear --- PASS: TestClear (0.00s) === RUN TestSetUnit === RUN TestSetUnit/seconds === RUN TestSetUnit/minutes === RUN TestSetUnit/hours === RUN TestSetUnit/days === RUN
Bug#1027363: golang-github-araddon-dateparse: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:golang-github-araddon-dateparse
Version: 0.0~git20210207.0eec95c-1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary-indep
dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang
dh_update_autotools_config -i -O--builddirectory=_build
-O--buildsystem=golang
dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang
dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang
dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 2 github.com/araddon/dateparse
internal/unsafeheader
internal/cpu
runtime/internal/atomic
runtime/internal/sys
runtime/internal/math
internal/bytealg
math/bits
math
runtime
unicode/utf8
internal/race
sync/atomic
unicode
internal/testlog
internal/reflectlite
sync
errors
sort
strconv
io
internal/oserror
syscall
reflect
internal/syscall/unix
time
internal/poll
internal/fmtsort
internal/syscall/execenv
strings
os
fmt
github.com/araddon/dateparse
dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 2 github.com/araddon/dateparse
=== RUN TestOne
--- PASS: TestOne (0.00s)
=== RUN TestParse
parseany_test.go:441: Expected to load location "America/Los_Angeles" but
got unknown time zone America/Los_Angeles
--- FAIL: TestParse (0.00s)
=== RUN TestPStruct
parseany_test.go:489:
Error Trace:parseany_test.go:489
Error: Not equal:
expected: ()
actual :
*errors.errorString({s:"unknown time zone America/Denver"})
Test: TestPStruct
--- FAIL: TestPStruct (0.00s)
=== RUN TestParseErrors
--- PASS: TestParseErrors (0.00s)
=== RUN TestParseLayout
--- PASS: TestParseLayout (0.00s)
=== RUN TestParseStrict
--- PASS: TestParseStrict (0.00s)
=== RUN TestInLocation
parseany_test.go:619:
Error Trace:parseany_test.go:619
Error: Not equal:
expected: ()
actual :
*errors.errorString({s:"unknown time zone America/Denver"})
Test: TestInLocation
parseany_test.go:649:
Error Trace:parseany_test.go:649
Error: Not equal:
expected: -25200
actual : 0
Test: TestInLocation
Messages: Should have found offset = -25200 0 UTC
parseany_test.go:650:
Error Trace:parseany_test.go:650
Error: Not equal:
expected: "MST"
actual : "UTC"
Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-MST
+UTC
Test: TestInLocation
Messages: Should have found zone = MST UTC
parseany_test.go:651:
Error Trace:parseany_test.go:651
Error: Not equal:
expected: "2013-02-01 07:00:00 + UTC"
actual : "2013-02-01 00:00:00 + UTC"
Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-2013-02-01 07:00:00 + UTC
+2013-02-01 00:00:00 + UTC
Test: TestInLocation
parseany_test.go:656:
Error Trace:parseany_test.go:656
Error: Not equal:
expected: -25200
actual : 0
Test: TestInLocation
Messages: Should have found offset = 0 0
parseany_test.go:657:
Error Trace:parseany_test.go:657
Error: Not equal:
expected: "MST"
actual : "UTC"
Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-MST
+UTC
Test: TestInLocation
Messages: Should have found zone = UTC UTC
parseany_test.go:658:
Bug#1027361: e2tools: FTBFS in bullseye (missing build-depends on e2fsprogs)
Package: src:e2tools
Version: 0.1.0-1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary-arch
dh binary-arch
dh_update_autotools_config -a
dh_autoreconf -a
dh_auto_configure -a
./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
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for Minix Amsterdam compiler... no
checking for ar... ar
checking for ranlib... ranlib
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking whether make sets $(MAKE)... (cached) yes
checking for chmod... /bin/chmod
checking for dd... /bin/dd
checking for mkfs.ext2... no
checking for unsigned long long int... yes
checking for long long int... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdint.h... (cached) yes
checking for inttypes.h... (cached) yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking whether the preprocessor supports include_next... yes
checking whether system header files limit the line length... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether stdint.h conforms to C99... yes
checking whether imaxabs is declared without a macro... yes
checking whether imaxdiv is declared without a macro... yes
checking whether strtoimax is declared without a macro... yes
checking whether strtoumax is declared without a macro... yes
checking for inttypes.h... (cached) yes
checking whether the inttypes.h PRIxNN macros are broken... no
checking for pid_t... yes
checking for mode_t... yes
checking whether INT32_MAX < INTMAX_MAX... yes
checking whether INT64_MAX == LONG_MAX... yes
checking whether UINT32_MAX < UINTMAX_MAX... yes
checking whether UINT64_MAX == ULONG_MAX... yes
checking for ssize_t... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for EXT2FS... yes
checking for COM_ERR... yes
checking for ANSI C header files... (cached) yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for mode_t... (cached) yes
checking for off_t... yes
checking for uint8_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for int8_t... yes
checking for int16_t... yes
checking for int32_t... yes
checking for int64_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking whether utime
Bug#1027360: calcurse: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:calcurse
Version: 4.6.0-2
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
dh_auto_configure -a
./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
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) none
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for sys/types.h... (cached) yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for unistd.h... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking for initscr... no
checking for initscr in -lncursesw... yes
checking ncursesw/ncurses.h usability... yes
checking ncursesw/ncurses.h presence... yes
checking for ncursesw/ncurses.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for pthread_create in -lpthread... yes
checking for math.h... (cached) yes
checking for exp in -lm... yes
checking whether to include documentation... yes
checking for asciidoc... no
configure: WARNING:
Bug#1027359: arduino-builder: FTBFS in bullseye (missing build-depends on tzdata)
Package: src:arduino-builder Version: 1.3.25-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary-arch dh binary-arch --buildsystem=golang --with=golang dh_update_autotools_config -a -O--buildsystem=golang dh_autoreconf -a -O--buildsystem=golang debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure rm -rf obj-*/src/arduino.cc cp -r -t obj-*/src/ src/* make[1]: Leaving directory '/<>' dh_auto_build -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2 arduino.cc/arduino-builder internal/unsafeheader arduino.cc/builder/constants internal/cpu runtime/internal/atomic runtime/internal/sys internal/bytealg runtime/internal/math math/bits math runtime unicode/utf8 internal/race sync/atomic unicode internal/testlog encoding unicode/utf16 internal/reflectlite sync errors sort strconv io internal/oserror syscall reflect internal/syscall/unix time internal/fmtsort internal/syscall/execenv bytes internal/poll strings os bufio regexp/syntax fmt regexp github.com/go-errors/errors net/url path/filepath arduino.cc/builder/i18n io/ioutil hash arduino.cc/builder/gohasissues arduino.cc/properties crypto encoding/binary arduino.cc/builder/types encoding/hex context crypto/md5 os/exec arduino.cc/builder/ctags arduino.cc/timeutils encoding/base64 arduino.cc/builder/utils encoding/json arduino.cc/builder/builder_utils arduino.cc/builder/phases flag arduino.cc/builder arduino.cc/arduino-builder debian/rules override_dh_auto_test make[1]: Entering directory '/<>' # Remove tests which download stuff: removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/add_build_board_property_if_missing_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/builder_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/ctags_runner_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/hardware_loader_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/includes_to_include_folders_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/libraries_loader_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/load_vid_pid_specific_properties_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/merge_sketch_with_bootloader_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/prototypes_adder_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/setup_build_properties_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/target_board_resolver_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/tools_loader_test.go' removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/try_build_of_problematic_sketch_test.go' # Execute the rest of the tests cd obj-* &&\ export GOPATH=$(pwd) &&\ go test -v -timeout 30m arduino.cc/... warning: ignoring symlink /<>/obj-x86_64-linux-gnu/src/arduino.cc/builder/test/user_hardware/my_symlinked_avr_platform ? arduino.cc/arduino-builder [no test files] === RUN TestFindBestLibraryWithHeader --- PASS: TestFindBestLibraryWithHeader (0.00s) PASS ok arduino.cc/builder 0.005s ? arduino.cc/builder/builder_utils[no test files] ? arduino.cc/builder/constants[no test files] === RUN TestCTagsParserShouldListPrototypes --- PASS: TestCTagsParserShouldListPrototypes (0.00s) === RUN TestCTagsParserShouldListTemplates --- PASS: TestCTagsParserShouldListTemplates (0.00s) === RUN TestCTagsParserShouldListTemplates2 --- PASS: TestCTagsParserShouldListTemplates2 (0.00s) === RUN TestCTagsParserShouldDealWithClasses --- PASS: TestCTagsParserShouldDealWithClasses (0.00s) === RUN TestCTagsParserShouldDealWithStructs --- PASS: TestCTagsParserShouldDealWithStructs (0.00s) === RUN TestCTagsParserShouldDealWithMacros --- PASS: TestCTagsParserShouldDealWithMacros (0.00s) === RUN TestCTagsParserShouldDealFunctionWithDifferentSignatures --- PASS: TestCTagsParserShouldDealFunctionWithDifferentSignatures (0.00s) === RUN TestCTagsParserClassMembersAreFilteredOut --- PASS: TestCTagsParserClassMembersAreFilteredOut (0.00s) === RUN TestCTagsParserStructWithFunctions --- PASS: TestCTagsParserStructWithFunctions (0.00s) === RUN TestCTagsParserDefaultArguments --- PASS: TestCTagsParserDefaultArguments (0.00s) === RUN TestCTagsParserNamespace --- PASS: TestCTagsParserNamespace (0.00s) === RUN TestCTagsParserStatic --- PASS: TestCTagsParserStatic (0.00s) === RUN TestCTagsParserFunctionPointer --- PASS: TestCTagsParserFunctionPointer (0.00s) === RUN TestCTagsParserFunctionPointers --- PASS: TestCTagsParserFunctionPointers (0.00s) === RUN TestCTagsToPrototypesShouldListPrototypes --- PASS: TestCTagsToPrototypesShouldListPrototypes (0.00s) === RUN
Bug#1026537: python-certbot: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Hi Harlan (2022.12.20_14:24:23_-0400) > This error stems from the .egg-info file being shipped as part of > python3-cffi, but the python3-cryptography lib only having Depends on the > cffi backend lib. I suspect the best thing to do here is to patch out that dependency. It doesn't need python3-cffi at runtime (I assume). This is just pkg_resources being annoying. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1026737: marked as done (lmfit-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Fri, 30 Dec 2022 17:38:17 +
with message-id
and subject line Bug#1026737: fixed in lmfit-py 1.1.0-1
has caused the Debian Bug report #1026737,
regarding lmfit-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lmfit-py
Version: 1.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> pybuild --configure -i python{version} -p "3.11 3.10"
> I: pybuild base:240: python3.11 setup.py config
> running config
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> pybuild --build -i python{version} -p "3.11 3.10"
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/jsonutils.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/__init__.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/models.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/minimizer.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/model.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/printfuncs.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/lineshapes.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/confidence.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/_ampgo.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/parameter.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> copying lmfit/_version.py ->
> /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit
> UPDATING /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit/_version.py
> set /<>/.pybuild/cpython3_3.11_lmfit/build/lmfit/_version.py to
> '1.0.2'
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/jsonutils.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/__init__.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/models.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/minimizer.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/model.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/printfuncs.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/lineshapes.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/confidence.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/_ampgo.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/parameter.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> copying lmfit/_version.py ->
> /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit
> UPDATING /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit/_version.py
> set /<>/.pybuild/cpython3_3.10_lmfit/build/lmfit/_version.py to
> '1.0.2'
>dh_auto_test -O--buildsystem=pybuild
> pybuild --test --test-pytest -i python{version} -p "3.11 3.10"
> I: pybuild pybuild:307: cp -r NIST_STRD examples
> /<>/.pybuild/cpython3_3.11_lmfit/build
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_lmfit/build;
> python3.11 -m pytest -k 'not speed and not test_model_nan_policy'
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>
> collected 578 items / 3 deselected / 575 selected
>
> tests/test_1variable.py .[
> 0%]
> tests/test_NIST_Strd.py ... [
> 4%]
> tests/test_algebraic_constraint.py [
> 5%]
> tests/test_ampgo.py [
> 7%]
> tests/test_basicfit.py . [
> 7%]
>
Bug#1027172: marked as done (lmfit-py: autopkgtest fail with matplotlib/3.6.2)
Your message dated Fri, 30 Dec 2022 17:38:17 + with message-id and subject line Bug#1027172: fixed in lmfit-py 1.1.0-1 has caused the Debian Bug report #1027172, regarding lmfit-py: autopkgtest fail with matplotlib/3.6.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lmfit-py Severity: serious User: debian-pyt...@lists.debian.org Usertags: matplotlib3.6 Hello, recently matplotlib/3.6.2 has been uploaded to unstable and this package fails autopkgtest. A link to the logs is available at: https://qa.debian.org/excuses.php?package=matplotlib some details on the changes introduced with matplotlib 3.6.x series are at: https://matplotlib.org/stable/users/prev_whats_new/whats_new_3.6.0.html Please check with upstream if a fix is already available, or a Debian patch may be necessary to let this package and matplotlib be released with bookworm. Thanks, Sandro --- End Message --- --- Begin Message --- Source: lmfit-py Source-Version: 1.1.0-1 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of lmfit-py, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated lmfit-py 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: Fri, 30 Dec 2022 17:46:34 +0100 Source: lmfit-py Architecture: source Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 1026737 1027172 1027226 Changes: lmfit-py (1.1.0-1) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Remove constraints unnecessary since buster (oldstable): + Build-Depends: Drop versioned constraint on python3-uncertainties. . [ Drew Parsons ] * New upstream release. Closes: #1026737, #1027172, #1027226. * Build-Depends: pybuild-plugin-pyproject to use pyproject.toml * drop debian patches - 0003-upstream-fix-for-scipy-1.7.0.patch applied upstream - exclude_failing_test.patch, example_emcee_Model_interface.py is an example not a test (needs corner module to run, which is not packaged for debian) * add debian patch preserve_version.patch to prevent setuptools-scm from corrupting version.py * dh_installdocs override: prefix example_emcee_Model_interface.py with nodoc_ to prevent processing by sphinx (corner module is not available) * override_dh_installdocs-indep copies extensions.py manually when building docs (following doc/Makefile). extensions.py is longer shipped in upstream source tarball * Build-Depends: python3-pytest-cov - execute_before_dh_python3: delete coverage (htmlcov) files from installation dirs (they were generated by build-time tests) * register html docs with doc-base * Standards-Version: 4.6.2 Checksums-Sha1: c5bdefc629a31ae0db6d52af01142d6c4c73bda1 2593 lmfit-py_1.1.0-1.dsc f5bc0966d9bdd559b18ac44acc4d1fe8fc05ad1b 308634 lmfit-py_1.1.0.orig.tar.gz 93ed8543fb5215aa9c9e07369cb2fc93c6c147e3 7128 lmfit-py_1.1.0-1.debian.tar.xz Checksums-Sha256: 2e24d1c57abdf244e83bfe6bfa87068aab6dd3b4d53d8cdc6c16d0d8250b31b2 2593 lmfit-py_1.1.0-1.dsc a2755b708ad7bad010178da28f082f55cbee7a084a625b452632e2d77b5391fb 308634 lmfit-py_1.1.0.orig.tar.gz 8f0dbde8cbe66f543441ba724d8dbc3bb360b72c6851ba9681ad1f1d1ff2cdff 7128 lmfit-py_1.1.0-1.debian.tar.xz Files: 72286d00fbf37126b1b058a20dc16124 2593 science optional lmfit-py_1.1.0-1.dsc 66d6e65f51b4b250f1ee23cb4c647d5f 308634 science optional lmfit-py_1.1.0.orig.tar.gz 671c428360b19cdb9d8421573971491b 7128 science optional lmfit-py_1.1.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmOvGcoACgkQVz7x5L1a AfpN/RAApIYuWeT+uF1bj4DK3DbZ3GkimwraT4m7U64JjnwQTnYNWnVSheynT7/N FQr0IzOpko02hkDOn8Cx9+2o1KW+tJpMt4wS6iiw2w2lQ9crfQqVKJsYt8jw5svO OVWlrkiQwuTYS2Q9nkaBHqk8y6dlUnqu0YZnzjWz25PdBF2qppSkvIFftu4yNfT0
