Processed: severity
Processing commands for cont...@bugs.debian.org: > severity 996448 normal Bug #996448 [src:llvm-toolchain-13] llvm-toolchain-13 autopkgtest segfaults on armhf Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 996448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999507: [Pkg-rust-maintainers] Bug#999507: Bug#999507: rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.
On November 12, 2021 1:11 pm, Henry-Nicolas Tourneur wrote: > > > Le ven 12 nov 2021 à 10:18, Fabian Grünbichler > a écrit : >> On November 12, 2021 6:38 am, Peter Green wrote: >>> Package: rust-tokio-signal >>> Version: 0.2.7-2 >>> Severity: serious >>> >>> rust-tokio-signal (build-)depends on version 0.1 of rust-futures. >>> Upstream seems to >>> have abandoned the project, there was an alpha release supporting >>> futures 0.2, but >>> the code appears to have been removed from the tokio git >>> repository. So I presume >>> it is abandoned upstream. >>> >>> There are no reverse dependencies in testing, there is a single >>> reverse dependency >>> in unstable which is rc buggy and also appears to be abandoned >>> upstream. >>> >>> If there are no objections in a few weeks, I intend to file a >>> removal request. >> >> same here, tokio-signal is now tokio+signal ;) accordingly, it can be >> RMed with the rest of the legacy tokio 0.1 crates once tokio 1.0 has >> been uploaded >> > > I would not even wait for tokio 1.0 upload and request removal of > tokio-signal could be done right away. > > As it stands, it is broken due to unsastifiable build dependencies and > it has no reverse dependencies, as Peter explained. > > Fabian, I see no point in keeping tokio-signal in the archive in its > current state and the package is going away anyway as you mentionned it > being superseeded by tokio+signal. > > Do you see any reasons to keep it until tokio 1.0 upload? no, the RMs can be filed now as well of course, I just figured it's easier to see which ones (also third-party related crates) go into the RM pile once the successors are packaged, which means less effort for all involved parties. but doing the first batch (those part of the original tokio 0.1 release itself - see the tokio-process bug) now is fine as well, we can always do a second batch post-uploads for any remaining stuff.
Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
Hi,
is your system fully upgraded?
What’s libpcre2 version?
Ondřej
--
Ondřej Surý (He/Him)
> On 15. 11. 2021, at 2:51, Matthew Krauss wrote:
>
> Package: php8.1-common
> Version: 8.1.0~rc5-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: zeros0and1o...@yahoo.com
>
> Dear Maintainer,
>
> After installing php8.1 on testing, I found that most PHP packages are
> failing. For instance, composer, whether installed directly from
> getcomposer.org, or through the Debian package, is broken by this bug,
> as well as likely the vast majority of PHP based software.
>
> The problem seems to be in an underlying regexp library, I *think*,
> and seems to break most of the built in php regexp functions.
>
> Simple demonstration, with both php7.4 and php8.1 installed:
>
> $ php7.4 -r 'var_export(preg_replace("/foo/", "bar", "some foo here")); echo
> "\ndone\n";'
> 'some bar here'
> done
>
> $ php8.1 -r 'var_export(preg_replace("/foo/", "bar", "some foo here")); echo
> "\ndone\n";'
> PHP Warning: preg_replace(): Compilation failed: unrecognised compile-time
> option bit(s) at offset 0 in Command line code on line 1
> NULL
> done
>
> The php7.4 command runs correctly and is what I would expect. The php8.1
> command generates a warning, as well as incorrect output.
>
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages php8.1 depends on:
> ii libapache2-mod-php8.1 8.1.0~rc5-1
> ii php8.1-common 8.1.0~rc5-1
>
> php8.1 recommends no packages.
>
> php8.1 suggests no packages.
>
> Versions of packages php8.1-common depends on:
> ii libc6 2.31-17
> ii libffi8 3.4.2-3
> ii libssl1.1 1.1.1l-1
> ii php-common 2:76
> ii ucf 3.0043
>
> -- no debconf information
>
Bug#999651: marked as done (coq FTBFS on bytecode architectures)
Your message dated Mon, 15 Nov 2021 06:18:32 + with message-id and subject line Bug#999651: fixed in coq 8.14.0+dfsg-4 has caused the Debian Bug report #999651, regarding coq FTBFS on bytecode architectures 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.) -- 999651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coq Version: 8.14.0+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=coq=sid ... Error: Don't know how to build _build/default/user-contrib/Ltac2/ltac2_plugin.cmxs Hint: did you mean _build/default/user-contrib/Ltac2/ltac2_plugin.cma? make[3]: *** [Makefile.common:190: _build/default/user-contrib/Ltac2/ltac2_plugin.cmxs] Error 1 --- End Message --- --- Begin Message --- Source: coq Source-Version: 8.14.0+dfsg-4 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of coq, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated coq package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 Nov 2021 06:59:19 +0100 Source: coq Architecture: source Version: 8.14.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Closes: 999651 Changes: coq (8.14.0+dfsg-4) unstable; urgency=medium . * Strip libraries. * Build using dune directly. * Make the html doc point to a local logo file. * Make the html doc point to local css files. * Disable the bytecode-only architectures (Closes: #999651). Checksums-Sha1: 27a6dccf197abaee522ec6481bbc056cb4c8d10f 3021 coq_8.14.0+dfsg-4.dsc bcde7acb5f2e139ac4fe2479224e873de9424823 39800 coq_8.14.0+dfsg-4.debian.tar.xz a29c1751785fd064d87446abd668d4ebe59f0b8f 15505 coq_8.14.0+dfsg-4_source.buildinfo Checksums-Sha256: 7eb7ee3762717a896415c0addac5726f8fea60ebe47e805d93a5e1b4f781aed2 3021 coq_8.14.0+dfsg-4.dsc b7851ef824dff080e9c07e726546bfc683059b5c67d6703b8360fc0c7b35218d 39800 coq_8.14.0+dfsg-4.debian.tar.xz 5bb3272d18f2085f6ea3ab9ccd367a3c83ea53993cacf53fe2621b838c2d9179 15505 coq_8.14.0+dfsg-4_source.buildinfo Files: e1fe5a66acb281be35b80dc69ea390d3 3021 math optional coq_8.14.0+dfsg-4.dsc 53ea74659338ae05aef130981b31ab3a 39800 math optional coq_8.14.0+dfsg-4.debian.tar.xz ccdb159086a6848296cf63196940ad84 15505 math optional coq_8.14.0+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmGR94gSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRU2gQAJuiKWLKp0JbBFNw4g7YISfYMTrzHq0B VkIdzZYAWRlvb5WUJncYcIb9+lX9seff6hNRl0l7Wds1lscmHW3Azl0KrRCWRR6r yTF9v6dlFynI/rXeNk3wfJ0psAoIYm/aePCHFS1BJ0gtkCdy/PbFiTX3tJyFtllK HIq7iJmjZWTcQHsAKMN9cU5ADYnxUcm5cTgHJkFKWZ/XZk+NSuofKcxEgwiOK0vd 8W+msH1NyOZkCNlbO0BBFEGKLxwWWoC52vNdELnY2JYTRDOwt1cNZbvUBuOnArGL 25zhABHoGLj0baUOM/2GyySSDcmfw3iVBMA8kYi1j8M0LdAp1Hy4Yl49IUrNY3aa 9kuo4RwFU9PDYyCgZeMUC0U/0JHs5br5PahsMNtToQhlSyB7/8sWmv6xIk0FAF+T 8waCCDUQxQh2Hku7c4M/YjHoP8Yu4WUDjaGocHKjeqSqolRFeYfChS1OT2sZr6Y2 P3gRIwUI59zYadd/kBDTRM5NrViaC/k0mNP38rGCupFBGsRfHtG9Rx21pMInQ+na j5JTjRGf3UvepSM4Ajyz9Y7fP2y3M78fTd+fmW768MOnFe/83kkZ69m+BS8DZ/tJ 7cYIwLRt9AsaYdX0m+OBLZEwfEaorPJ4qk1qSaX7lMpqyCArWWJkbT/jxFvFFth1 cEIeOK4O+TkI =xWOw -END PGP SIGNATURE End Message ---
Bug#999651: marked as pending in coq
Control: tag -1 pending Hello, Bug #999651 in coq 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/ocaml-team/coq/-/commit/8f166a65fea73b7ee1d8b2de0acf309d29e9d2c9 Disable the bytecode-only architectures (Closes: #999651) (this message was generated automatically) -- Greetings https://bugs.debian.org/999651
Processed: Bug#999651 marked as pending in coq
Processing control commands: > tag -1 pending Bug #999651 [src:coq] coq FTBFS on bytecode architectures Added tag(s) pending. -- 999651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997189: liboping: FTBFS: oping.c:1159:25: error: format not a string literal and no format arguments [-Werror=format-security]
FYI: For the latter case, it seems that it has already submitted a fix as a PR.
See https://github.com/octo/liboping/pull/60/files
On Sat, 23 Oct 2021 21:06:58 +0200 Lucas Nussbaum wrote:
> > oping.c: In function ‘update_host_hook’:
> > oping.c:1640:38: error: too many arguments for format
> > [-Werror=format-extra-args]
> > 1640 | HOST_PRINTF ("%zu bytes from %s (%s):
> > icmp_seq=%u ttl=%i ",
> > |
> > ^
> > oping.c:1617:45: note: in definition of macro ‘HOST_PRINTF’
> > 1617 | # define HOST_PRINTF(...) wprintw(main_win, __VA_ARGS__)
> > | ^~~
> > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2
> > -Wall -Werror -g -O2 -ffile-prefix-map=/<>=.
> > -fstack-protector-strong -Wformat -Werror=format-security -c liboping.c -o
> > liboping_la-liboping.o >/dev/null 2>&1
> > cc1: all warnings being treated as errors
> > make[4]: *** [Makefile:598: noping-oping.o] Error 1
Bug#998565: Errors due to changes in iso-codes data
I looked at this a bit today and it looks like the test failures are due to updates in the iso-codes data used by the tests, not any real failures. I think disabling the failing tests for now would be a reasonable way to keep this in testing (I'm interested to avoid transitive removal of xml2rfc). Unless there's some objection to this, I will probably NMU later in the week. Scott K
Processed: Re: Bug#999353: gkrelluim: broken rebuild
Processing control commands: > severity -1 grave Bug #999353 [gkrelluim] gkrelluim: broken rebuild Severity set to 'grave' from 'normal' -- 999353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996206: marked as done (ruby-cocaine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: undef_method :exitstatus)
Your message dated Sun, 14 Nov 2021 23:48:27 +
with message-id
and subject line Bug#996206: fixed in ruby-cocaine 0.5.8-2
has caused the Debian Bug report #996206,
regarding ruby-cocaine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: undef_method :exitstatus
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.)
--
996206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-cocaine
Version: 0.5.8-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-cocaine was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: undef_method :exitstatus
>
> FrozenError:
>can't modify frozen object: pid 2351759 exit 0
> # ./spec/support/unsetting_exitstatus.rb:4:in `undef_method'
> # ./spec/support/unsetting_exitstatus.rb:4:in `singleton class'
> # ./spec/support/unsetting_exitstatus.rb:3:in
> `assuming_no_processes_have_been_run'
> # ./spec/cocaine/errors_spec.rb:55:in `block (2 levels) in (required)>'
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/cocaine/command_line/runners/backticks_runner_spec.rb:19:in
> `block (2 levels) in '.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 6.87 seconds (files took 2.68 seconds to load)
> 67 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/cocaine/errors_spec.rb:54 # When an error happens does not blow
> up if running the command errored before execution
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-cocaine/ruby-cocaine_0.5.8-1.1+rebuild1633376733_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-cocaine
Source-Version: 0.5.8-2
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-cocaine, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-cocaine package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 15 Nov 2021 00:33:16 +0100
Source: ruby-cocaine
Architecture: source
Version: 0.5.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996206
Changes:
ruby-cocaine (0.5.8-2) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Use secure URI in debian/watch.
* Bump debhelper from deprecated 9 to 13.
* Set debhelper-compat version in Build-Depends.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
* Update watch file format version to 4.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field and suggest ruby-posix-spawn.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Minor cleanup to fix
Bug#996206: marked as pending in ruby-cocaine
Control: tag -1 pending Hello, Bug #996206 in ruby-cocaine 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-cocaine/-/commit/79eb7ef7bbf8b3d912338c33bbf30340a93a4222 Add patches * d/patches/drop-git-in-gemspec.patch: Add patch. - Drop git usage in gemspec. * d/patches/dont-try-to-modify-frozen-Process-Status.patch: Add patch. - Don't modify frozen Process::Status (closes: #996206). * d/patches/series: Enable new patches. (this message was generated automatically) -- Greetings https://bugs.debian.org/996206
Processed: Bug#996206 marked as pending in ruby-cocaine
Processing control commands: > tag -1 pending Bug #996206 [src:ruby-cocaine] ruby-cocaine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: undef_method :exitstatus Added tag(s) pending. -- 996206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 966970
Processing commands for cont...@bugs.debian.org:
> close 966970 1.1.3-1
Bug #966970 [src:piexif] piexif: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 returned exit code 13
Marked as fixed in versions piexif/1.1.3-1.
Bug #966970 [src:piexif] piexif: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996514: marked as done (ruby-terrapin: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: undef_method :exitstatus)
Your message dated Sun, 14 Nov 2021 23:19:15 +
with message-id
and subject line Bug#996514: fixed in ruby-terrapin 0.6.0-3
has caused the Debian Bug report #996514,
regarding ruby-terrapin: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: undef_method :exitstatus
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.)
--
996514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-terrapin
Version: 0.6.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-terrapin was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: undef_method :exitstatus
>
> FrozenError:
>can't modify frozen object: pid 1724074 exit 0
> # ./spec/support/unsetting_exitstatus.rb:4:in `undef_method'
> # ./spec/support/unsetting_exitstatus.rb:4:in `singleton class'
> # ./spec/support/unsetting_exitstatus.rb:3:in
> `assuming_no_processes_have_been_run'
> # ./spec/terrapin/errors_spec.rb:55:in `block (2 levels) in (required)>'
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/terrapin/command_line/runners/backticks_runner_spec.rb:19:in
> `block (2 levels) in '.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 1.4 seconds (files took 0.51763 seconds to load)
> 67 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/terrapin/errors_spec.rb:54 # When an error happens does not blow
> up if running the command errored before execution
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-terrapin/ruby-terrapin_0.6.0-2+rebuild1633396815_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-terrapin
Source-Version: 0.6.0-3
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-terrapin, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-terrapin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 14 Nov 2021 23:59:09 +0100
Source: ruby-terrapin
Architecture: source
Version: 0.6.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996514
Changes:
ruby-terrapin (0.6.0-3) unstable; urgency=low
.
* Team upload.
.
[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ Daniel Leidert ]
* d/control (Standards-Version): Bump to 4.6.0.
(Build-Depends): Minor cleanup to fix redundant-control-relation.
(Depends): Use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
* d/rules: Use gem installation layout.
* d/patches/drop-git-in-gemspec.patch: Update patch.
- Fix patch to work with gem installation layout.
*
Processed: unarchiving 966970, reopening 966970
Processing commands for cont...@bugs.debian.org:
> # src:piexif was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 966970
Bug #966970 {Done: Debian FTP Masters }
[src:piexif] piexif: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 returned exit code 13
Unarchived Bug 966970
> reopen 966970
Bug #966970 {Done: Debian FTP Masters }
[src:piexif] piexif: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 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 1.0.13-3+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996514: marked as pending in ruby-terrapin
Control: tag -1 pending Hello, Bug #996514 in ruby-terrapin 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-terrapin/-/commit/f6db29dfa9614a4cfc4c3245a903c885907d2e0b Fix FTBFS in tests * d/patches/dont-try-to-modify-frozen-Process-Status.patch: Add patch. - Don't modify frozen Process::Status (closes: #996514). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996514
Processed: Bug#996514 marked as pending in ruby-terrapin
Processing control commands: > tag -1 pending Bug #996514 [src:ruby-terrapin] ruby-terrapin: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: undef_method :exitstatus Added tag(s) pending. -- 996514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 999680 is forwarded to https://github.com/checkpoint-restore/criu/issues/1653
Processing commands for cont...@bugs.debian.org: > forwarded 999680 https://github.com/checkpoint-restore/criu/issues/1653 Bug #999680 [src:criu] criu: FTBFS on armhf: cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU Set Bug forwarded-to-address to 'https://github.com/checkpoint-restore/criu/issues/1653'. > thanks Stopping processing here. Please contact me if you need assistance. -- 999680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999680: criu: FTBFS on armhf: cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU
Source: criu Version: 3.16.1-1 Severity: serious Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: car...@debian.org This is different from #918229, so filling a separate issue. criu on armhf FTBFS with gcc-11: dh clean --with python3 dh_auto_clean make -j4 clean make[1]: Entering directory '/<>' make[1]: git: No such file or directory /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. CLEANDocumentation CLEANtest/compel CLEANimages CLEANcriu/arch/arm CLEANcriu/pie CLEANcriu CLEANcriu/unittest CLEANcriu/pie CLEANcriu CLEANsoccr CLEANlib/c CLEANlib/py/images CLEANlib/py CLEANlib CLEANcompel CLEANcompel/plugins CLEANlib/c CLEANlib/py/images CLEANlib/py CLEANlib CLEANcrit make[1]: Leaving directory '/<>' dh_clean debian/rules binary-arch dh binary-arch --with python3 dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a dh_auto_build -a make -j4 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' Note: Building without setproctitle() and strlcpy() support. To enable these features, please install libbsd-devel (RPM) / libbsd-dev (DEB). Makefile.config:41: Warn: you have libnftables installed but it has incompatible API Makefile.config:42: Warn: Building without nftables support make[1]: git: No such file or directory /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. GEN .gitid GEN include/common/asm GEN compel/include/asm touch .config GEN compel/include/version.h GEN criu/include/version.h GEN include/common/config.h GEN compel/plugins/include/uapi/std/asm/syscall-types.h DEP compel/arch/arm/plugins/std/parasite-head.d GEN compel/arch/arm/plugins/std/syscalls/syscalls.S cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU GEN compel/plugins/include/uapi/std/syscall-codes.h DEP soccr/soccr.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU GEN compel/plugins/include/uapi/std/syscall.h CC soccr/soccr.o cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU make[2]: *** [/<>/scripts/nmk/scripts/build.mk:119: soccr/soccr.o] Error 1 make[1]: *** [Makefile:232: soccr/built-in.o] Error 2 make[1]: *** Waiting for unfinished jobs DEP compel/arch/arm/plugins/std/syscalls/syscalls.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU DEP compel/plugins/std/infect.d DEP compel/plugins/std/string.d DEP compel/plugins/std/log.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU DEP compel/plugins/std/fds.d DEP compel/plugins/std/std.d DEP compel/plugins/shmem/shmem.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU DEP compel/plugins/fds/fds.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU CC compel/plugins/std/fds.o CC compel/plugins/std/std.o CC compel/plugins/std/log.o cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU make[2]: *** [/<>/scripts/nmk/scripts/build.mk:214: compel/plugins/std/std.o] Error 1 make[2]: *** Waiting for unfinished jobs cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU make[2]: *** [/<>/scripts/nmk/scripts/build.mk:214: compel/plugins/std/fds.o] Error 1 make[2]: *** [/<>/scripts/nmk/scripts/build.mk:214: compel/plugins/std/log.o] Error 1 make[1]: *** [Makefile.compel:56: compel/plugins/std.lib.a] Error 2 PBCC images/apparmor.pb-c.c PBCC images/bpfmap-data.pb-c.c PBCC images/fown.pb-c.c PBCC images/google/protobuf/descriptor.pb-c.c PBCC images/img-streamer.pb-c.c PBCC images/timens.pb-c.c PBCC images/macvlan.pb-c.c PBCC images/autofs.pb-c.c PBCC images/sysctl.pb-c.c PBCC images/time.pb-c.c PBCC images/binfmt-misc.pb-c.c PBCC images/seccomp.pb-c.c PBCC images/pidns.pb-c.c PBCC images/userns.pb-c.c PBCC images/cgroup.pb-c.c PBCC images/ext-file.pb-c.c PBCC images/rpc.pb-c.c PBCC images/siginfo.pb-c.c PBCC images/rlimit.pb-c.c PBCC images/file-lock.pb-c.c PBCC images/creds.pb-c.c PBCC images/utsns.pb-c.c PBCC images/ipc-desc.pb-c.c PBCC images/ipc-var.pb-c.c PBCC images/sk-opts.pb-c.c PBCC images/timer.pb-c.c PBCC images/pipe-data.pb-c.c PBCC images/sk-packet.pb-c.c PBCC images/pstree.pb-c.c
Bug#995600: marked as done (FTBFS: error: format not a string literal and no format arguments)
Your message dated Sun, 14 Nov 2021 21:18:54 + with message-id and subject line Bug#995600: fixed in omega-rpg 1:0.90-pa9-17 has caused the Debian Bug report #995600, regarding FTBFS: error: format not a string literal and no format arguments 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.) -- 995600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: omega-rpg Version: 1:0.90-pa9-16 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid that your package fails to build with: scr.c: In function ‘print1’: scr.c:351:5: error: format not a string literal and no format arguments [-Werror=format-security] 351 | wprintw(Msg1w,s); | ^~~ scr.c: In function ‘nprint1’: scr.c:361:7: error: format not a string literal and no format arguments [-Werror=format-security] 361 | wprintw(Msg1w,s); | ^~~ scr.c: In function ‘print2’: scr.c:374:5: error: format not a string literal and no format arguments [-Werror=format-security] 374 | wprintw(Msg2w,s); | ^~~ (repeated elebenty times) Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-rc2-00041-g794e5d9c562d (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- Source: omega-rpg Source-Version: 1:0.90-pa9-17 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of omega-rpg, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated omega-rpg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 14 Nov 2021 22:57:15 +0200 Source: omega-rpg Architecture: source Version: 1:0.90-pa9-17 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 995600 Changes: omega-rpg (1:0.90-pa9-17) unstable; urgency=medium . * QA upload. * Set maintainer to Debian QA Group. (see #963928) * Disable format hardening to workaround FTBFS with newer ncurses. (Closes: #995600) Checksums-Sha1: 1ccad1e38b5b41378d23460f376e6dc63c808a10 1725 omega-rpg_0.90-pa9-17.dsc 29468d114af8407172e713b0745b2091953d9d5a 11352 omega-rpg_0.90-pa9-17.debian.tar.xz Checksums-Sha256: c75e856372ca3e624ef5e4d13e729ecf15e364f0984933e4fb188e1f22f9bd41 1725 omega-rpg_0.90-pa9-17.dsc 8282ba453b0168633bb7a513faa412f57e96b3ca9ef556df58d1db2fb799148e 11352 omega-rpg_0.90-pa9-17.debian.tar.xz Files: ef2797921fe60af50e13786545500605 1725 games optional omega-rpg_0.90-pa9-17.dsc 80e909e462d380221f8695cdeda25aa0 11352 games optional omega-rpg_0.90-pa9-17.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGReXcACgkQiNJCh6LY mLG5zA//dGme/zaAreM8D30A0yYR/yieDfOxYzn1ggPW8pwLth+Yg1Ah7bLA0+Oi mGGHeMUO18MzdtcmSTTGmhYwjfRTOoqFmnTXzKID2BeM7PSdl9TKq8M0c8RkAhV4 JF1pzChAk/v5fkVq+7s7MHMdnrGcfwHWYNSrvKqPOM9vYFSUskstEcQtjf9zDsZ8 cH4QZWiAZ450Lw+UR+GBkcKdLildSfJaLJiyNkVYvp+Q5awGrI+ns4b2sjZC/3ja rWtA9PxoWmTC4IpT5l41tyCovOlGvhyG49SynuHMbdqcLRJrxoBFhxcz8BY3nSPK qKhOpuabfHlHR6fdFpMMrHETq6+IOkVaTDLcbReAgGhDG2mwtHD9sfsjne/vsAjb n3Znc014ZjuT7MvRIqK3fidRFeoyjQdxWILrtbASdKQk3GbnXYo/wQgt6fWPomRt Kesh5qelqhdwSgCP7T7aICCa4uAdy4R77c4C9EtPr0UPJTGIQG+UhcEusVGJetvN BN8le6xqPHcy4C+WMySFluuhCJ6hWU2Ic6M5vPhcBNT5ntZpQY+GDhM/hncIaew6 n3qsBOa4CIC24pBBRvgx8t64cVtzJzmalKKMUrUw4oOsfYHhePVkv6Z+u2UWAqvc TKw4UfSpKLQ+ALxqZgJhdK7ukmyuM+NlMr7haXsr1LlJiAai4Cs= =Q+Nr -END PGP SIGNATURE End Message ---
Processed: Re: update version info
Processing commands for cont...@bugs.debian.org: > # let's hope three time is a charm > notfound 964138 2.9.0-1 Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long: maintainer built arch:all binary No longer marked as found in versions sec/2.9.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 964138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997402: marked as done (kst: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_L
Your message dated Sun, 14 Nov 2021 20:48:46 + with message-id and subject line Bug#997402: fixed in kst 2.0.8-5 has caused the Debian Bug report #997402, regarding kst: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -Dkst_install_prefix=/usr -Dkst_verbose=ON -Dkst_rpath=OFF -Dkst_svnversion=OFF -Dkst_qt5=ON .. returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kst Version: 2.0.8-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -Scmake -- -Dkst_install_prefix=/usr -Dkst_verbose=ON > -Dkst_rpath=OFF -Dkst_svnversion=OFF -Dkst_qt5=ON > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -Dkst_install_prefix=/usr -Dkst_verbose=ON -Dkst_rpath=OFF > -Dkst_svnversion=OFF -Dkst_qt5=ON .. > CMake Error at CMakeLists.txt:118 (else): > Flow control statements are not properly nested. > > > -- Configuring incomplete, errors occurred! > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //No help, variable specified on the command line. > CMAKE_BUILD_TYPE:UNINITIALIZED=None > > //No help, variable specified on the command line. > CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON > > //No help, variable specified on the command line. > CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON > > //No help, variable specified on the command line. > CMAKE_FIND_USE_PACKAGE_REGISTRY:UNINITIALIZED=OFF > > //No help, variable specified on the command line. > CMAKE_INSTALL_LIBDIR:UNINITIALIZED=lib/x86_64-linux-gnu > > //No help, variable specified on the command line. > CMAKE_INSTALL_LOCALSTATEDIR:UNINITIALIZED=/var > > //No help, variable specified on the command line. > CMAKE_INSTALL_PREFIX:UNINITIALIZED=/usr > > //No help, variable specified on the command line. > CMAKE_INSTALL_RUNSTATEDIR:UNINITIALIZED=/run > > //No help, variable specified on the command line. > CMAKE_INSTALL_SYSCONFDIR:UNINITIALIZED=/etc > > //No help, variable specified on the command line. > CMAKE_SKIP_INSTALL_ALL_DEPENDENCY:UNINITIALIZED=ON > > //No help, variable specified on the command line. > CMAKE_VERBOSE_MAKEFILE:UNINITIALIZED=ON > > //No help, variable specified on the command line. > kst_install_prefix:UNINITIALIZED=/usr > > //No help, variable specified on the command line. > kst_qt5:UNINITIALIZED=ON > > //No help, variable specified on the command line. > kst_rpath:UNINITIALIZED=OFF > > //No help, variable specified on the command line. > kst_svnversion:UNINITIALIZED=OFF > > //No help, variable specified on the command line. > kst_verbose:UNINITIALIZED=ON > > > > # INTERNAL cache entries > > > //This is the directory where this CMakeCache.txt was
Processed: tagging 995480
Processing commands for cont...@bugs.debian.org: > tags 995480 + fixed-upstream Bug #995480 [src:ytree] FTBFS: error: format not a string literal and no format arguments Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 995480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: update version info
Processing commands for cont...@bugs.debian.org: > # oops, did that wrong. > fixed 964138 2.9.0-1 Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long: maintainer built arch:all binary Marked as fixed in versions sec/2.9.0-1. > found 964138 2.8.3-2 Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long: maintainer built arch:all binary Marked as found in versions sec/2.8.3-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 964138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: update version info
Processing commands for cont...@bugs.debian.org: > notfound 964138 2.8.2-1.1 Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long: maintainer built arch:all binary No longer marked as found in versions sec/2.8.2-1.1. > found 964138 2.9.0-1 Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long: maintainer built arch:all binary Marked as found in versions sec/2.9.0-1. > tags 964138 - pending Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long: maintainer built arch:all binary Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 964138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995742: marked as done (ddnet armhf autopkgtest regression due to compiler warning)
Your message dated Sun, 14 Nov 2021 19:48:33 +
with message-id
and subject line Bug#995742: fixed in ddnet 15.6.2-1
has caused the Debian Bug report #995742,
regarding ddnet armhf autopkgtest regression due to compiler warning
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.)
--
995742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ddnet
Version: 15.5.4-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/armhf/d/ddnet/15770428/log.gz
...
[ 97%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/client/serverbrowser_http.cpp.o
In file included from /usr/include/c++/10/vector:72,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/graphics.h:13,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/textrender.h:8,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/game/client/ui.h:7,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/serverbrowser.h:8,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/client/serverbrowser_http.cpp:8:
/usr/include/c++/10/bits/vector.tcc: In member function ‘void std::vector<_Tp,
_Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...)
[with _Args = {CServerBrowserHttp::CEntry}; _Tp = CServerBrowserHttp::CEntry;
_Alloc = std::allocator]’:
/usr/include/c++/10/bits/vector.tcc:426:7: note: parameter passing for argument
of type ‘std::vector::iterator’ changed in GCC 7.1
426 | vector<_Tp, _Alloc>::
| ^~~
/usr/include/c++/10/bits/vector.tcc: In static member function ‘static bool
CServerBrowserHttp::Parse(json_value*,
std::vector*, std::vector*)’:
/usr/include/c++/10/bits/vector.tcc:121:21: note: parameter passing for
argument of type ‘__gnu_cxx::__normal_iterator >’ changed in GCC 7.1
121 |_M_realloc_insert(end(), std::forward<_Args>(__args)...);
|~^~~
...
[==] 105 tests from 26 test suites ran. (322 ms total)
[ PASSED ] 105 tests.
[100%] Built target run_tests
autopkgtest [12:14:12]: test unittest.sh: ---]
autopkgtest [12:14:12]: test unittest.sh: - - - - - - - - - - results - - - -
- - - - - -
unittest.sh FAIL stderr: In file included from
/usr/include/c++/10/vector:72,
autopkgtest [12:14:12]: test unittest.sh: - - - - - - - - - - stderr - - - - -
- - - - -
In file included from /usr/include/c++/10/vector:72,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/graphics.h:13,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/textrender.h:8,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/game/client/ui.h:7,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/serverbrowser.h:8,
from
/tmp/autopkgtest-lxc.4ns0slin/downtmp/build.RMJ/src/src/engine/client/serverbrowser_http.cpp:8:
/usr/include/c++/10/bits/vector.tcc: In member function ‘void std::vector<_Tp,
_Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...)
[with _Args = {CServerBrowserHttp::CEntry}; _Tp = CServerBrowserHttp::CEntry;
_Alloc = std::allocator]’:
/usr/include/c++/10/bits/vector.tcc:426:7: note: parameter passing for argument
of type ‘std::vector::iterator’ changed in GCC 7.1
426 | vector<_Tp, _Alloc>::
| ^~~
/usr/include/c++/10/bits/vector.tcc: In static member function ‘static bool
CServerBrowserHttp::Parse(json_value*,
std::vector*, std::vector*)’:
/usr/include/c++/10/bits/vector.tcc:121:21: note: parameter passing for
argument of type ‘__gnu_cxx::__normal_iterator >’ changed in GCC 7.1
121 |_M_realloc_insert(end(), std::forward<_Args>(__args)...);
|~^~~
autopkgtest [12:14:12]: summary
unittest.sh FAIL stderr: In file included from
/usr/include/c++/10/vector:72,
--- End Message ---
--- Begin Message ---
Source: ddnet
Source-Version: 15.6.2-1
Done: Yangfl
We believe that the bug you reported is fixed in the latest version of
ddnet, 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
Bug#997802: marked as done (ddnet: autopkgtest regression on armhf: output to stderr)
Your message dated Sun, 14 Nov 2021 19:48:33 +
with message-id
and subject line Bug#995742: fixed in ddnet 15.6.2-1
has caused the Debian Bug report #995742,
regarding ddnet: autopkgtest regression on armhf: output to stderr
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.)
--
995742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ddnet
Version: 15.5.4-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of ddnet the autopkgtest of ddnet fails in testing
when that autopkgtest is run with the binary packages of ddnet from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
ddnet from testing15.5.4-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. It seems that
the actual test passes, but there's output on stderr and the default
behavior of autopkgtest is to fail on output to stderr. If in general
output to stderr is harmless to your test, consider adding the
allow-stderr restriction. Otherwise, please fix your test.
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=ddnet
https://ci.debian.net/data/autopkgtest/testing/armhf/d/ddnet/16147062/log.gz
[ 91%] Building CXX object CMakeFiles/testrunner.dir/src/test/unix.cpp.o
[ 91%] Building CXX object CMakeFiles/testrunner.dir/src/test/uuid.cpp.o
[ 94%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/client/blocklist_driver.cpp.o
[ 94%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/client/http.cpp.o
[ 94%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/client/serverbrowser.cpp.o
[ 97%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/client/serverbrowser_http.cpp.o
In file included from /usr/include/c++/10/vector:72,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/engine/graphics.h:13,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/engine/textrender.h:8,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/game/client/ui.h:7,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/engine/serverbrowser.h:8,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/engine/client/serverbrowser_http.cpp:8:
/usr/include/c++/10/bits/vector.tcc: In member function ‘void
std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp,
_Alloc>::iterator, _Args&& ...) [with _Args =
{CServerBrowserHttp::CEntry}; _Tp = CServerBrowserHttp::CEntry; _Alloc =
std::allocator]’:
/usr/include/c++/10/bits/vector.tcc:426:7: note: parameter passing for
argument of type ‘std::vector::iterator’
changed in GCC 7.1
426 | vector<_Tp, _Alloc>::
| ^~~
/usr/include/c++/10/bits/vector.tcc: In static member function ‘static
bool CServerBrowserHttp::Parse(json_value*,
std::vector*, std::vector*)’:
/usr/include/c++/10/bits/vector.tcc:121:21: note: parameter passing for
argument of type
‘__gnu_cxx::__normal_iterator >’ changed in GCC 7.1
121 |_M_realloc_insert(end(), std::forward<_Args>(__args)...);
|~^~~
[ 97%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/client/serverbrowser_ping_cache.cpp.o
[ 97%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/client/sqlite.cpp.o
[100%] Building CXX object
CMakeFiles/testrunner.dir/src/engine/server/name_ban.cpp.o
[100%] Building CXX object
CMakeFiles/testrunner.dir/src/game/server/teehistorian.cpp.o
[100%] Linking CXX executable testrunner
[100%] Built target testrunner
[100%] tests
[...]
autopkgtest [18:23:02]: test unittest.sh: - - - - - - - - - - stderr -
- - - - - - - - -
In file included from /usr/include/c++/10/vector:72,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/engine/graphics.h:13,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/engine/textrender.h:8,
from
/tmp/autopkgtest-lxc.6korsrvz/downtmp/build.XVn/src/src/game/client/ui.h:7,
from
Bug#992676: scipy breaks python-skbio autopkgtest: Unsupported dtype object
On Thu, 7 Oct 2021 00:26:54 +0530 Nilesh Patra wrote: > Reported and pinged upstream here, pinging on the bug to delay > testing removal for a bit > > https://github.com/biocore/scikit-bio/issues/1757 Looks like it is fixed in upstream commits[1.2] @Andreas would you consider cherry-picking them and try? [1]: https://github.com/biocore/scikit-bio/pull/1786 [2]: https://github.com/biocore/scikit-bio/pull/1787 Nilesh signature.asc Description: PGP signature
Processed: scipy breaks python-skbio autopkgtest: Unsupported dtype object
Processing control commands: > fixed -1 upstream Bug #992676 [src:python-skbio] scipy breaks python-skbio autopkgtest: Unsupported dtype object The source 'python-skbio' and version 'upstream' do not appear to match any binary packages Marked as fixed in versions python-skbio/upstream. -- 992676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992676: scipy breaks python-skbio autopkgtest: Unsupported dtype object
control: fixed -1 upstream On Thu, 7 Oct 2021 00:26:54 +0530 Nilesh Patra wrote: > Reported and pinged upstream here, pinging on the bug to delay > testing removal for a bit > > https://github.com/biocore/scikit-bio/issues/1757 Looks like upstream has fixed this in[1.2] @Andreas, would you consider to cherry pick and try? [1]: https://github.com/biocore/scikit-bio/pull/1786 [2]: https://github.com/biocore/scikit-bio/pull/1787 Nilesh signature.asc Description: PGP signature
Bug#996807: marked as done (tinydns stops replying to queries after a few hours)
Your message dated Sun, 14 Nov 2021 19:03:29 + with message-id and subject line Bug#996807: fixed in djbdns 1:1.05-14 has caused the Debian Bug report #996807, regarding tinydns stops replying to queries after a few hours 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.) -- 996807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tinydns Version: 1:1.05-13 Severity: grave Justification: renders package unusable -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=ro_RO (charmap=ISO-8859-2), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages tinydns depends on: ii init-system-helpers 1.60 ii libc62.31-17 ii runit-helper 2.10.3 ii sysuser-helper 1.3.5.1 Versions of packages tinydns recommends: pn daemon pn runit tinydns suggests no packages. -- no debconf information None of the tinydns files have been changed when this bug started manifesting (nor the ELF or its data files). In fact it was an update of libc which caused this. Any version of libc6 2.32-* will cause tinydns to ignore queries after a while. dnscache runing on the same machine is not affected. tinydns doesn't crash and there is nothing unusual in its logfiles. If I kill the tinydns daemon then supervise will spawn another version and it starts working again for a while then stops replying to queries. Rolling back libc6 to version 2.31-17 makes tinydns working again. --- End Message --- --- Begin Message --- Source: djbdns Source-Version: 1:1.05-14 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of djbdns, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated djbdns package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 14 Nov 2021 20:41:31 +0200 Source: djbdns Architecture: source Version: 1:1.05-14 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Closes: 996373 996807 Changes: djbdns (1:1.05-14) unstable; urgency=medium . * Declare compliance with Policy 4.6.0 with no changes. * Override two Lintian diagnostics. * Drop leading slashes in the *.install destination. * Drop the version the dh-sysuser build dependency, satisfied even in oldstable. * Use debian/clean to clean up the sysvinit/conf directory. * Add the 0010-dnsroots.global patch. Closes: #996373 * Add the 0011-datalimit patch to catch up with recent versions of glibc generating larger executable files. Closes: #996807 * Several improvements to the Python tinytest autopkgtest tool: - use "with subprocess.Popen()" - simplify the command-line parsing a bit - minor import statement fixes - add a tox.ini file to make it easier to run static code checkers - turn a class into a dataclass - send a lot of queries to tinydns to make sure that the fix for #996807 actually works * Bump the debhelper compatibility level to 13 and drop the check for "nocheck" in DEB_BUILD_OPTIONS, since it is done automatically now. * Build and install systemd service files, too. * Use `execute_after_*` for one more target. * Fix a typo in the debian/manpages-README file. Checksums-Sha1: b6922cc70d698033240802a12db2a8eb97e9d72f 2417 djbdns_1.05-14.dsc 04a0dfc52e343b06b741321b8a1ef9a9ebd4112e 61572 djbdns_1.05-14.debian.tar.xz Checksums-Sha256: 82ddff9ac5d6a180df52fe92a78a81ac594c15a41df9d344df46ca18da0a3d3e 2417 djbdns_1.05-14.dsc 2d518d96c9757f9d319e602a77588d4e93044c193fefedd7206e44ed5fee5b95 61572 djbdns_1.05-14.debian.tar.xz Files: f3d2f052cdc8bea8d649bdf50b1cde2e 2417 net optional djbdns_1.05-14.dsc 126a3c2ea88e6acca050bdbdcc4b72f6 61572 net
Bug#999652: marked as done (units-filter: binary-all FTBFS)
Your message dated Sun, 14 Nov 2021 18:50:43 + with message-id and subject line Bug#999652: fixed in units-filter 4.2-3 has caused the Debian Bug report #999652, regarding units-filter: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: units-filter Version: 4.2-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=units-filter=all=4.2-2=1636821858=0 ... dh_fixperms # replace one directory by a symlink to sphinx rm -rf debian/units-filter/usr/share/doc/units-filter/html/_static ln -s ../../../sphinx/themes/basic/static \ debian/units-filter/usr/share/doc/units-filter/html/_static ln: failed to create symbolic link 'debian/units-filter/usr/share/doc/units-filter/html/_static': No such file or directory make[1]: *** [debian/rules:24: override_dh_fixperms] Error 1 --- End Message --- --- Begin Message --- Source: units-filter Source-Version: 4.2-3 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of units-filter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated units-filter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 14 Nov 2021 19:24:51 +0100 Source: units-filter Architecture: source Version: 4.2-3 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 999652 Changes: units-filter (4.2-3) unstable; urgency=medium . * fixed the missing path $(DESTDIR_TXT)/usr/share/doc/units-filter/html when a symlink to /usr/share/sphinx/themes/basic/static must be created. Closes: #999652 Checksums-Sha1: 604149e0a9273eb2006f6addee7342325bb01bfb 2047 units-filter_4.2-3.dsc 45809787d03e18eb3f714d904ca2cc010e5cc973 6140 units-filter_4.2-3.debian.tar.xz a990d8a54a14f63a9dbd54fbc2561356b30615a3 11253 units-filter_4.2-3_source.buildinfo Checksums-Sha256: dcd61242882b1643bfdb7dbdb3fae83e2fa8fca740e1859b4479a36f2cf90288 2047 units-filter_4.2-3.dsc 66d015172fcd6f1f98d35671f5563bdccca6121033358d9d23b741ac5d16609a 6140 units-filter_4.2-3.debian.tar.xz ce5d77be1fe5ab1be9975630f1a69a64ed09d03de0518f6f713a89726ada00df 11253 units-filter_4.2-3_source.buildinfo Files: 70f3d91ce22584bb7ffcbf451b04fb41 2047 science optional units-filter_4.2-3.dsc 8b718418592eb9d9aea2e962309933ee 6140 science optional units-filter_4.2-3.debian.tar.xz fe4a195b5cfc3d65fd202280074da4a8 11253 science optional units-filter_4.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmGRVzcUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjk0KxAAnmaI8AIAVpI0sgye/aEoQrU4WKxQ px7rg/93J0wYNsgniMyomZg+1tFaotJPZEjU6RPRx6U5PAqUOaX3AGzcey781W2A Aa7d6BU6xZPQzuh7fDc8dGg7S7kDDToqoWtHiDXpZa+Mwj6I6xzyo36NnUwiE0jx snQqBYBG2jUIYx+7FLYfRfcz0evkFFz1MHxKDA0fUFljaQXC4xvBt1nHX3afcs92 POSmd81dWQwvrEX5dZn2eXmJB5jC/YpHC3KUc8R68nV9pjfj4K0PrkDOHaSIOdLK R13PE0/4pGKaJr0uJ5P7fhAJ6uB+Pdu/MriUv2Bsz3Jme2zU9Tosb9Eg/74Az5BW qHRo+a6fxx0qy7IEhWulQZuJh4MceKfxNtJBCOF13UWpAN1X/2BLi0PDSozEXmQh l7sV39zTUGqV+2dxdkN1v73htw/ilo7pjzxMK469Ed7YPTvgGE/hqSgzWx1nX3Ln Ve7ZTRGcSneUDNnnRNwaNokHVWcSmJKxxLtNdTfU6G7MHnX+5/rgrwuQfzkazPl6 p4GopdCSwMIiSAeDWWhqT0xZPmiYt/TL8iuqS3Xrllntrqt4YfElstSZJpQJvc/0 CGNEuO4+xXDPf/TTFz7OBEIVXMbUykvOPNasjfFqcgpgxm6hlmPGK2p8Emxj3QKW TxdFOKMi1gaiGaQ= =+UX/ -END PGP SIGNATURE End Message ---
Processed: Bug#996807 marked as pending in djbdns
Processing control commands: > tag -1 pending Bug #996807 [tinydns] tinydns stops replying to queries after a few hours Added tag(s) pending. -- 996807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996807: marked as pending in djbdns
Control: tag -1 pending Hello, Bug #996807 in djbdns reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/djbdns/-/commit/d7e894e85b18ac0a791ecda1f7e080e70b2428fa Add the 0011-datalimit patch to raise the limit. Allow axfrdns, dnscache, and tinydns to consume some more memory, since it seems that recent versions of glibc produce larger executable files. Reflect this in the DATALIMIT files in the tinydns and dnscache service directories installed by default. Closes: #996807 (this message was generated automatically) -- Greetings https://bugs.debian.org/996807
Bug#998215: marked as done (h5py: FTBFS without network access)
Your message dated Sun, 14 Nov 2021 18:19:52 +
with message-id
and subject line Bug#998215: fixed in h5py 3.5.0-2
has caused the Debian Bug report #998215,
regarding h5py: FTBFS without network access
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
998215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: h5py
Version: 3.3.0-3
Severity: serious
Tags: ftbfs
Hi Maintainer
As can be seen on reproducible builds [1], h5py FTBFS without network
access during one of its tests. I've copied what I hope is the
relevant part of the log below.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/h5py.html
=== FAILURES ===
__ TestROS3.test_ros3 __
self =
@pytest.mark.skipif(h5py.version.hdf5_version_tuple < (1, 10, 6)
or not h5.get_config().ros3,
reason="ros3 file operations were added in
HDF5 1.10.6+")
def test_ros3(self):
""" ROS3 driver and options """
> with File("https://dandiarchive.s3.amazonaws.com/ros3test.hdf5;, 'r',
driver='ros3') as f:
build/h5py/_debian_h5py_serial/tests/test_file.py:826:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
build/h5py/_debian_h5py_serial/_hl/files.py:444: in __init__
fid = make_fid(name, mode, userblock_size,
build/h5py/_debian_h5py_serial/_hl/files.py:199: in make_fid
fid = h5f.open(name, flags, fapl=fapl)
h5py/_debian_h5py_serial/_objects.pyx:54: in
h5py._debian_h5py_serial._objects.with_phil.wrapper
???
h5py/_debian_h5py_serial/_objects.pyx:55: in
h5py._debian_h5py_serial._objects.with_phil.wrapper
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E OSError: Unable to open file (curl cannot perform request)
h5py/_debian_h5py_serial/h5f.pyx:100: OSError
--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 3.5.0-2
Done: Drew Parsons
We believe that the bug you reported is fixed in the latest version of
h5py, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons (supplier of updated h5py package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 14 Nov 2021 18:26:39 +0100
Source: h5py
Architecture: source
Version: 3.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Closes: 998215
Changes:
h5py (3.5.0-2) unstable; urgency=medium
.
* Team upload.
* update debian patch skip_ros_test_no_net.patch to skip ROS3 network
file tests if environment variable H5PY_NO_NETWORK_TEST is set.
Apply during debian build-time tests. Closes: #998215.
Checksums-Sha1:
03558364ad91a862908f6500dc4c3cdd872f91e3 2729 h5py_3.5.0-2.dsc
2db3bd9de935df841ae5e77e4a87dce610cb391b 18700 h5py_3.5.0-2.debian.tar.xz
Checksums-Sha256:
fd4717d930edbca4266cbe74d2b9a20960448eed444aa981a14a96bc4d9fdf81 2729
h5py_3.5.0-2.dsc
a61d0faf1b43c6f50a3b54a352689c7d1900278ebba401a01d2a6233b97ed9b6 18700
h5py_3.5.0-2.debian.tar.xz
Files:
bc7dc92dc6e79fe3932be813d5d1293c 2729 python optional h5py_3.5.0-2.dsc
64016da4aec30a4e64d3196698348159 18700 python optional
h5py_3.5.0-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmGRTikACgkQVz7x5L1a
Afr3whAAqBpyMo0jOyC/BZlmeHeRbCqDBc1UTuiiIPK42ZElOGLsxdaYzJbXxWSO
cS2lHh7CpR1ugychz5u4SV3/1TYg4HGTjsVqGRre5QSyO4PtE9bYWP2Vn5CLPmZL
dmPZWuSoEDwzyyNkvnN96bp8C7V9SixMM9nfrVxvm4vV3qqvsIlIpBZbxizdetXx
Ya802wrUBD6UHk2q5uo15ATzwquXrRh54wicG2qDypwS9gjjcpuRxhSoZt9KJzFE
pZuapyYY0nnj3WICuFCCxdpt1pxU97MMX5jJvny7Byum1ZzalMNPk4IPJP0HgtN5
mI6kpx5VnS2QdJPzlqNOI2XIq/q/u9ePTadu/8XdcY5gpCoT4k3AKr+J0Vt7ZM68
acW94c5Ks0RNn0Qly5JLZ1CSYTfjdQXz8osn4HhcgjGLpKFq6bgWMkYvC86gOIcs
9i2trrROb91w9nP7rcvrJ0OU7DKmQXdQ9pDFo31vCc3eg/h+17NYn+rhwsWbciQt
G27q0nuV/MQYQ73daHejPvlQ3kfz54yE9upitLeH2/Qvu02z3WXyjOgIMp8EGbrf
Bug#997140: marked as done (bwm-ng: FTBFS: output.c:154:13: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Sun, 14 Nov 2021 18:18:35 + with message-id and subject line Bug#997140: fixed in bwm-ng 0.6.3-2 has caused the Debian Bug report #997140, regarding bwm-ng: FTBFS: output.c:154:13: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bwm-ng Version: 0.6.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o options.o options.c > output.c: In function ‘print_header’: > output.c:154:13: error: format not a string literal and no format arguments > [-Werror=format-security] > 154 | wprintw(stdscr,show_all_if2str()); > | ^~~ > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o help.o help.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o curses_tools.o curses_tools.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o retrieve.o `test -f 'input/retrieve.c' || echo > './'`input/retrieve.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o proc_net_dev.o `test -f 'input/proc_net_dev.c' > || echo './'`input/proc_net_dev.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o proc_diskstats.o `test -f > 'input/proc_diskstats.c' || echo './'`input/proc_diskstats.c > cc1: some warnings being treated as errors > make[3]: *** [Makefile:390: output.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/bwm-ng_0.6.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: bwm-ng Source-Version: 0.6.3-2 Done: Samuel Henrique We believe that the bug you reported is fixed in the latest version of bwm-ng, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Henrique (supplier of updated bwm-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 14 Nov 2021 18:05:26 + Source: bwm-ng Architecture: source Version: 0.6.3-2 Distribution: unstable Urgency: medium Maintainer: Samuel Henrique Changed-By: Samuel Henrique Closes: 997140 Changes: bwm-ng (0.6.3-2) unstable; urgency=medium . * Bump Standards-Version to 4.6.0 * d/p/fix_format_string_literal.patch: New upstream patch to address FTBFS (closes: #997140) * d/watch: Remove filemangle in favor of lintian's suggestion 'prefer-uscan-symlink' Checksums-Sha1: f98b703e3997a29e496872fa0091130d119aa7c6 1828 bwm-ng_0.6.3-2.dsc 7365c0a1240c357005e3f50550976b18ba258a24 5132 bwm-ng_0.6.3-2.debian.tar.xz ec2cf4b14d230c4bcae73d8c2b94daa2f03c2fdb 6204 bwm-ng_0.6.3-2_amd64.buildinfo Checksums-Sha256: 5581275a63e02f66c46f9a4b936de555a2c85ca62cce6529db0551f9d110b40f 1828 bwm-ng_0.6.3-2.dsc
Processed: fixed 990000 in 0.4.6.8-1
Processing commands for cont...@bugs.debian.org:
> fixed 99 0.4.6.8-1
Bug #99 {Done: Peter Palfrader } [src:tor] tor:
CVE-2021-34548 CVE-2021-34549 CVE-2021-34550
Marked as fixed in versions tor/0.4.6.8-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 990000 in 0.4.6.5-1
Processing commands for cont...@bugs.debian.org:
> fixed 99 0.4.6.5-1
Bug #99 {Done: Peter Palfrader } [src:tor] tor:
CVE-2021-34548 CVE-2021-34549 CVE-2021-34550
The source 'tor' and version '0.4.6.5-1' do not appear to match any binary
packages
Marked as fixed in versions tor/0.4.6.5-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998502: marked as done (shairport-sync: FTBFS: configure.ac:296: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Sun, 14 Nov 2021 16:21:48 + with message-id and subject line Bug#998502: fixed in shairport-sync 3.3.8-1 has caused the Debian Bug report #998502, regarding shairport-sync: FTBFS: configure.ac:296: error: AM_INIT_AUTOMAKE expanded multiple times 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.) -- 998502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shairport-sync Version: 3.3.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_clean > rm -f man/shairport-sync.7 man/shairport-sync.html > make[1]: Leaving directory '/<>' >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building shairport-sync using existing > ./shairport-sync_3.3.7.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of file man/shairport-sync.7, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file man/shairport-sync.html, use > --include-removal to override > dpkg-source: info: building shairport-sync in > shairport-sync_3.3.7-1.debian.tar.xz > dpkg-source: info: building shairport-sync in shairport-sync_3.3.7-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf > configure.ac:296: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:6: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... > ./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from... > configure.ac:296: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:19: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/shairport-sync_3.3.7-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: shairport-sync Source-Version: 3.3.8-1 Done: Chris Boot We believe that the bug you reported is fixed in the latest version of shairport-sync, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Boot (supplier of updated shairport-sync package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Nov 2021 17:52:23 + Source: shairport-sync Architecture: source Version: 3.3.8-1 Distribution: unstable Urgency: medium Maintainer: Chris Boot Changed-By: Chris Boot Closes: 998502 Changes: shairport-sync (3.3.8-1) unstable; urgency=medium . * New upstream release. - d/patches/typo-fixes.patch: remove; included upstream. * d/patches/github-1314.patch: fix build with automake 1.16.5. (Closes: #998502) * d/control: build with libjack-jackd2-dev instead of libjack-dev. * d/control: bump standards version to 4.6.0; no other changes required. * d/shairport-sync.docs: add CAR INSTALL.md and MQTT.md. Checksums-Sha1: d6901c0b14f1eed4850213654f05cbb5ca336ac0 2364 shairport-sync_3.3.8-1.dsc f597caaefcac34b47423d523e335046b253b0e18 425524 shairport-sync_3.3.8.orig.tar.gz
Bug#996048: [Pkg-openssl-devel] Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt, it does not conta
Control: reassign -1 src:ca-certificates On Monday, 08 November 2021, 15:57 +0200, Adrian Bunk wrote: > On Tue, Oct 19, 2021 at 09:13:56AM +0200, Julien Cristau wrote: > > On Mon, Oct 18, 2021 at 11:05:14PM +0200, Kurt Roeckx wrote: > > > On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote: > > > > On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote: > > > > > Hi, > > > > > > > > > > I think the following change might be the relevant one: > > > > > > > > > > --- a/update-ca-certificates > > > > > +++ b/update-ca-certificates > > > > > @@ -164,8 +164,6 @@ > > > > >done > > > > > fi > > > > > > > > > > -rm -f "$CERTBUNDLE" > > > > > - > > > > > ADDED_CNT=$(wc -l < "$ADDED") > > > > > REMOVED_CNT=$(wc -l < "$REMOVED") > > > > > > > > > > It triggers this stderr output during openssl rehash (l. 184): > > > > > > > > > > rehash: warning: skipping ca-certificates.crt,it does not contain > > > > > exactly one certificate or CRL > > > > > > > > > Ah, that makes sense. Annoying... > > > > > > > > Kurt/Sebastian, do you think there's a chance openssl rehash could grow > > > > some sort of ignore option so update-ca-certificates could ask it to > > > > skip ca-certificates.crt, to avoid spitting out a warning for it? > > > > > > As in rehash all files in that directory, excluding a file? I > > > guess that's an option. I guess it's not an option to move the > > > file to a different location. > > > > > Exactly. /etc/ssl/certs/ca-certificates.crt is the package's main > > "interface" so I suspect it'd be quite painful to move. Likewise moving > > the certs and hash symlinks themselves would break packages/scripts > > looking them up that way. > > > > The other option for me would be to revert the fix for bug #920348. > > In any case, there is nothing happening here specific to > postfix-mta-sts-resolver, the same problem would happen with > any other package that does not permit stderr output in the > autopkgtest when upgrading ca-certificates is tested. > > The failing part of the autopkgtest is a testing->unstable upgrade of > ca-certificates. > > Any objections to reassigning this to ca-certificates? Sure! Kind regards, Benjamin
Processed: Re: Bug#996048: [Pkg-openssl-devel] Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt, it
Processing control commands: > reassign -1 src:ca-certificates Bug #996048 [src:postfix-mta-sts-resolver] postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL Bug reassigned from package 'src:postfix-mta-sts-resolver' to 'src:ca-certificates'. No longer marked as found in versions postfix-mta-sts-resolver/1.0.0-4. Ignoring request to alter fixed versions of bug #996048 to the same values previously set -- 996048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999624: marked as done (anbox: FTBFS with GCC 11: src/anbox/input/manager.h:38:8: error: 'uint32_t' in namespace 'std' does not name a type)
Your message dated Sun, 14 Nov 2021 16:03:38 +
with message-id
and subject line Bug#999624: fixed in anbox 0.0~git20211020-1
has caused the Debian Bug report #999624,
regarding anbox: FTBFS with GCC 11: src/anbox/input/manager.h:38:8: error:
'uint32_t' in namespace 'std' does not name a type
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: anbox
Version: 0.0~git20210625-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
anbox recently started to FTBFS in sid, I think that is correlated to
the swich of the default compiler to GCC 11 (and -std=c++17).
In file included from
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:18:
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:38:8: error: 'uint32_t'
in namespace 'std' does not name a type; did you mean 'wint_t'?
38 | std::uint32_t next_id();
|^~~~
|wint_t
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:39:44: error: 'uint32_t'
in namespace 'std' does not name a type; did you mean 'wint_t'?
39 | std::string build_device_path(const std::uint32_t );
|^~~~
|wint_t
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:42:17: error: 'uint32_t'
is not a member of 'std'; did you mean 'wint_t'?
42 | std::map> devices_;
| ^~~~
| wint_t
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:42:49: error: template
argument 1 is invalid
42 | std::map> devices_;
| ^~
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:42:49: error: template
argument 3 is invalid
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:42:49: error: template
argument 4 is invalid
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp: In member function
'std::shared_ptr anbox::input::Manager::create_device()':
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:39:19: error:
'next_id' was not declared in this scope
39 | const auto id = next_id();
| ^~~
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:42:12: error: request
for member 'insert' in
'((anbox::input::Manager*)this)->anbox::input::Manager::devices_', which is of
non-class type 'int'
42 | devices_.insert({id, device});
|^~
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp: At global scope:
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:46:15: error: no
declaration matches 'uint32_t anbox::input::Manager::next_id()'
46 | std::uint32_t Manager::next_id() {
| ^~~
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:46:15: note: no
functions named 'uint32_t anbox::input::Manager::next_id()'
In file included from
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:18:
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:30:7: note: 'class
anbox::input::Manager' defined here
30 | class Manager {
| ^~~
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:51:13: error: no
declaration matches 'std::string anbox::input::Manager::build_device_path(const
uint32_t&)'
51 | std::string Manager::build_device_path(const std::uint32_t ) {
| ^~~
In file included from
/build/anbox-0.0~git20210625/src/anbox/input/manager.cpp:18:
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:39:15: note: candidate
is: 'std::string anbox::input::Manager::build_device_path(const int&)'
39 | std::string build_device_path(const std::uint32_t );
| ^
/build/anbox-0.0~git20210625/src/anbox/input/manager.h:30:7: note: 'class
anbox::input::Manager' defined here
30 | class Manager {
| ^~~
make[3]: *** [src/CMakeFiles/anbox-core.dir/build.make:1005:
src/CMakeFiles/anbox-core.dir/anbox/input/manager.cpp.o] Error 1
Andreas
anbox_0.0~git20210625-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: anbox
Source-Version: 0.0~git20211020-1
Done: Shengjing Zhu
We believe that the bug you reported is fixed in the latest version of
anbox, 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
Processed: tagging 995220
Processing commands for cont...@bugs.debian.org: > tags 995220 + bookworm ftbfs Bug #995220 [ts-node] FTBFS: build broken by typescript update Added tag(s) bookworm and ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 995220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998547: ping to avoid autorm
pinging #998547 to avoid autorm of pdns, as #998816 is still awaiting ftpmaster processing, which would then allow pdns to migrate.
Processed: limit source to linux, tagging 996951
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 996951 + pending Bug #996951 [src:linux] linux-image-5.14.0-3-amd64: iouring looses requests Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 996951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998490: marked as done (libapache2-mod-rivet: FTBFS: configure.ac:57: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Sun, 14 Nov 2021 13:18:39 + with message-id and subject line Bug#998490: fixed in libapache2-mod-rivet 3.2.1-2 has caused the Debian Bug report #998490, regarding libapache2-mod-rivet: FTBFS: configure.ac:57: error: AM_INIT_AUTOMAKE expanded multiple times 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.) -- 998490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libapache2-mod-rivet Version: 3.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh_testdir > dh_autoreconf_clean > dh_autoreconf > configure.ac:57: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:32: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:57: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:47: configure-stamp] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/libapache2-mod-rivet_3.2.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libapache2-mod-rivet Source-Version: 3.2.1-2 Done: Sven Hoexter We believe that the bug you reported is fixed in the latest version of libapache2-mod-rivet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sven Hoexter (supplier of updated libapache2-mod-rivet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 14 Nov 2021 13:54:56 +0100 Source: libapache2-mod-rivet Architecture: source Version: 3.2.1-2 Distribution: unstable Urgency: medium Maintainer: Massimo Manghi Changed-By: Sven Hoexter Closes: 998490 Changes: libapache2-mod-rivet (3.2.1-2) unstable; urgency=medium . * Upload to unstable - the upload of 3.2.1-1 to stable was a mistake. . libapache2-mod-rivet (3.2.1-1) stable; urgency=medium . * New upstream release. * New rivet version addresses issue with multiple AM_AUTOMAKE_INIT expansion (Closes: #998490). * Correcting the name of the target directory where rivet library and Tcl scripts are moved into (it still had the old 3.1 version name) Checksums-Sha1: 728b333c0120f2a7ba25e915e1124c6e992e434e 1966 libapache2-mod-rivet_3.2.1-2.dsc 76021654114239b10f785126f289a27225890de8 24172 libapache2-mod-rivet_3.2.1-2.debian.tar.xz 42872f3fe45cac4cc2a7b772902b95bfc516bbbc 7627 libapache2-mod-rivet_3.2.1-2_amd64.buildinfo Checksums-Sha256: 668a142fcd4a0c9cd9c9b7d1a191c99f354f752df6d5457dfacc8e31d2820671 1966 libapache2-mod-rivet_3.2.1-2.dsc a60feec057a7c5b46a32d6f3401388bcc873af0c2dc9c7e29304f158a2eb8d93 24172 libapache2-mod-rivet_3.2.1-2.debian.tar.xz 91c7a88b62bc88d1e90ba2c783777ab4fc7f6283b792b34d0e0b31c8c3bb0231 7627 libapache2-mod-rivet_3.2.1-2_amd64.buildinfo Files: ba0f4c0e4f9f11512b723bf2d21c3af0 1966 httpd optional libapache2-mod-rivet_3.2.1-2.dsc 38850116e464c53280c0892c1f544b9b 24172 httpd optional libapache2-mod-rivet_3.2.1-2.debian.tar.xz f175e7e34423775c7c3520f014aabc0c 7627 httpd optional libapache2-mod-rivet_3.2.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#999663: zfs-linux: FTBFS with libabigail 2.0
Source: zfs-linux
Version: 2.0.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
zfs-linux recently started to FTBFS, I suspect this to be caused by the
upgrade of libabigail to 2.0:
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/zfs-linux-2.0.6'
# Upstream provides an ABI guarantee that we validate here
/usr/bin/make checkabi
make[2]: Entering directory '/build/zfs-linux-2.0.6'
/usr/bin/make -C lib checkabi
make[3]: Entering directory '/build/zfs-linux-2.0.6/lib'
set -e ; for dir in libnvpair libuutil libzfs_core libzfs libzfsbootenv ; do \
/usr/bin/make -C $dir checkabi ; \
done
make[4]: Entering directory '/build/zfs-linux-2.0.6/lib/libnvpair'
for lib in libnvpair.la ; do \
abidiff --no-unreferenced-symbols \
--headers-dir1 ../../include \
--suppressions ${lib%.la}.suppr \
${lib%.la}.abi .libs/${lib%.la}.so ; \
done
abidiff: incompatible format version between the two input files:
'libnvpair.abi'
and
'.libs/libnvpair.so'
make[4]: *** [Makefile:1089: checkabi] Error 1
make[4]: Leaving directory '/build/zfs-linux-2.0.6/lib/libnvpair'
make[3]: *** [Makefile:964: checkabi] Error 2
make[3]: Leaving directory '/build/zfs-linux-2.0.6/lib'
make[2]: *** [Makefile:1502: checkabi] Error 2
make[2]: Leaving directory '/build/zfs-linux-2.0.6'
make[1]: *** [debian/rules:83: override_dh_auto_test] Error 2
make[1]: Leaving directory '/build/zfs-linux-2.0.6'
make: *** [debian/rules:34: binary] Error 2
Andreas
zfs-linux_2.0.6-1.log.gz
Description: application/gzip
Bug#999659: perdition: failed to install, failed to uninstall (error in initscript)
Package: perdition Version: 2.2-3.1+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: s...@s73.work Dear Maintainer, The error happens only on first install of the perdition, see instructions below on how to reproduce it. First I get an error during # apt install perdition Failed to stop perdition.service: Unit perdition.service not loaded. invoke-rc.d: initscript perdition, action "stop" failed. That happens only if there was no perdition package installed before. If you had perdition package installed and deleted later then error is not happening, since the command "apt purge" does not delete one generated file. So, to reproduce, either take host where perdition was never installed (apt purge alone will not help here!), or # apt purge perdition then delete generated file: # rm /run/systemd/generator.late/perdition.service Now "apt install" will fail. After installation fails, you will also not be able to delete the package: # apt purge perdition ... Failed to stop perdition.service: Unit perdition.service not loaded. invoke-rc.d: initscript perdition, action "stop" failed. dpkg: error processing package perdition (--remove): installed perdition package pre-removal script subprocess returned error exit status 5 dpkg: too many errors, stopping Here fix is easy, just edit /var/lib/dpkg/info/perdition.prerm and replace the line invoke-rc.d perdition stop with invoke-rc.d perdition stop || true Something similar must be done for the preinstall script in order to fix the install error. Here is full apt install output: # LANG=C apt install perdition Reading package lists... Done Building dependency tree... Done Reading state information... Done perdition is already the newest version (2.2-3.1+b1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up perdition (2.2-3.1+b1) ... Failed to stop perdition.service: Unit perdition.service not loaded. invoke-rc.d: initscript perdition, action "stop" failed. dpkg: error processing package perdition (--configure): installed perdition package post-installation script subprocess returned error exit status 5 Processing triggers for libc-bin (2.31-13+deb11u2) ... Errors were encountered while processing: perdition needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Here is full apt purge output: # LANG=C apt purge perdition Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: perdition* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 468 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 19109 files and directories currently installed.) Removing perdition (2.2-3.1+b1) ... Failed to stop perdition.service: Unit perdition.service not loaded. invoke-rc.d: initscript perdition, action "stop" failed. dpkg: error processing package perdition (--remove): installed perdition package pre-removal script subprocess returned error exit status 5 dpkg: too many errors, stopping Errors were encountered while processing: perdition Processing was halted because there were too many errors. needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU:ru Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages perdition depends on: ii libc6 2.31-13+deb11u2 ii libdb5.35.3.28+dfsg1-0.8 ii libgdbm61.19-2 pn libidn11 ii libnsl2 1.3.0-2 ii libpam0g1.4.0-9+deb11u1 pn libpopt0 ii libssl1.1 1.1.1k-1+deb11u1 pn libvanessa-adt1 pn libvanessa-logger0 pn libvanessa-socket2 ii lsb-base11.1.0 perdition recommends no packages. Versions of packages perdition suggests: pn perdition-ldap pn perdition-mysql pn perdition-odbc pn perdition-postgresql -- no debconf information
Processed: tagging 984083
Processing commands for cont...@bugs.debian.org: > tags 984083 + pending Bug #984083 [src:lasi] lasi: ftbfs with GCC-11 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 984083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 903374
Processing commands for cont...@bugs.debian.org: > tags 903374 + bookworm sid Bug #903374 [src:tracker] tracker: autopkgtest regressed in September 2021 Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 903374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999620: pktanon: autopkgtest regression on armhf
Hi Paul, > With a recent upload of pktanon the autopkgtest of pktanon fails in > testing on armhf when that autopkgtest is run with the binary packages > of pktanon from unstable. [...] > Currently this regression is blocking the migration to testing [1]. Can > you please investigate the situation and fix it? I am puzzled. The recent upload only changed the watchfile and updated Standards-Version, compat level etc -- packaging things. Nothing touched the code or build rules. Also, I can't reproduce the bus error when running the offending command from the autopkgtest on a version I built on a porterbox: (sid_armhf-dchroot)satta@abel:~/pktanon-2~git20160407.0.2bde4f2+dfsg$ ../usr/bin/pktanon -c ../usr/share/doc/pktanon/examples/profiles/profile.xml profiles/sample.pcap ./out.pcap --- pktanon --- profile-based traffic anonymization --- initializing PktAnon, configuration = ../usr/share/doc/pktanon/examples/profiles/profile.xml unknown element: pktanon-config: 37 unknown element: anonymizations: 102 istream: opened file profiles/sample.pcap ostream: opened output file ./out.pcap initialized complete statistics for input file 'profiles/sample.pcap' processed packets: 9 errors in packets: 0 elapsed time: 639us Mpps: 0.0141 I must admit that being unfamiliar with these architectures and not really having an idea of where to start, I am tempted to just remove armhf from the list of supported architectures and have the version with the broken autopkgtest removed from unstable. Do you probably know someone who might be more knowledgeable with such architecture-specific issues? Cheers Sascha
Bug#999645: marked as done (keybase: Uninstallable in Debian 11)
Your message dated Sun, 14 Nov 2021 10:56:47 +0100 with message-id and subject line Re: Bug#999645: keybase: Uninstallable in Debian 11 has caused the Debian Bug report #999645, regarding keybase: Uninstallable in Debian 11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: keybase Version: 5.8.1-20210930160723.fefa22edc1 Severity: grave Tags: upstream Justification: renders package unusable Some of the dependencies are not available on Debian 11. The package is uninstallable. -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages keybase depends on: ii fuse3 [fuse] 3.10.3-2 pn libappindicator1 ii libasound21.2.4-1.1 pn libgconf-2-4 ii libgtk-3-03.24.24-4 ii libnss3 2:3.61-1 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii lsof 4.93.2+dfsg-1.1 ii procps2:3.3.17-5 ii psmisc23.4-2 keybase recommends no packages. keybase suggests no packages. --- End Message --- --- Begin Message --- On Sun, Nov 14, 2021 at 09:29:14AM +0100, Mattia Monga wrote: > Package: keybase > Version: 5.8.1-20210930160723.fefa22edc1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Some of the dependencies are not available on Debian 11. The package is > uninstallable. That package is not in the Debian archive, so take this to whoever is providing you with the package. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia ` End Message ---
Bug#999652: units-filter: binary-all FTBFS
Source: units-filter Version: 4.2-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=units-filter=all=4.2-2=1636821858=0 ... dh_fixperms # replace one directory by a symlink to sphinx rm -rf debian/units-filter/usr/share/doc/units-filter/html/_static ln -s ../../../sphinx/themes/basic/static \ debian/units-filter/usr/share/doc/units-filter/html/_static ln: failed to create symbolic link 'debian/units-filter/usr/share/doc/units-filter/html/_static': No such file or directory make[1]: *** [debian/rules:24: override_dh_fixperms] Error 1
Bug#999651: coq FTBFS on bytecode architectures
Source: coq Version: 8.14.0+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=coq=sid ... Error: Don't know how to build _build/default/user-contrib/Ltac2/ltac2_plugin.cmxs Hint: did you mean _build/default/user-contrib/Ltac2/ltac2_plugin.cma? make[3]: *** [Makefile.common:190: _build/default/user-contrib/Ltac2/ltac2_plugin.cmxs] Error 1
Bug#999650: ruby-oily-png FTBFS on 32bit
Source: ruby-oily-png Version: 1.2.1~dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=ruby-oily-png ... Failures: 1) OilyPNG::Color#compose_quick should use the background color as is when a fully transparent pixel is given as foreground color Failure/Error: expect(compose_quick(@fully_transparent, @white)).to be(@white) expected # => 4294967295 got # => 4294967295 Compared using equal?, which compares object identity, but expected and actual are not the same object. Use `expect(actual).to eq(expected)` if you don't care about object identity in this example. # ./spec/color_spec.rb:24:in `block (3 levels) in ' 2) OilyPNG::Color#compose_quick should compose pixels correctly Failure/Error: expect(compose_quick(@non_opaque, @white)).to be(0x9fc2d6ff) expected # => 2680346367 got # => 2680346367 Compared using equal?, which compares object identity, but expected and actual are not the same object. Use `expect(actual).to eq(expected)` if you don't care about object identity in this example. # ./spec/color_spec.rb:28:in `block (3 levels) in ' 3) OilyPNG::Color#compose_quick should compose colors exactly the same as ChunkyPNG Failure/Error: expect(compose_quick(fg, bg)).to be(ChunkyPNG::Color.compose_quick(fg, bg)) expected # => 2126858483 got # => 2126858483 Compared using equal?, which compares object identity, but expected and actual are not the same object. Use `expect(actual).to eq(expected)` if you don't care about object identity in this example. # ./spec/color_spec.rb:33:in `block (3 levels) in ' Finished in 0.36245 seconds (files took 0.22531 seconds to load) 146 examples, 3 failures, 18 pending Failed examples: rspec ./spec/color_spec.rb:23 # OilyPNG::Color#compose_quick should use the background color as is when a fully transparent pixel is given as foreground color rspec ./spec/color_spec.rb:27 # OilyPNG::Color#compose_quick should compose pixels correctly rspec ./spec/color_spec.rb:31 # OilyPNG::Color#compose_quick should compose colors exactly the same as ChunkyPNG /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed ERROR: Test "ruby2.7" failed. Exiting. dh_auto_install: error: dh_ruby --install /<>/ruby-oily-png-1.2.1\~dfsg/debian/ruby-oily-png returned exit code 1 make: *** [debian/rules:8: binary-arch] Error 25
Processed: Re: Bug#998215 closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#998215: fixed in h5py 3.3.0-4)
Processing control commands:
> reopen -1
Bug #998215 {Done: Drew Parsons } [src:h5py] h5py: FTBFS
without network access
'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 h5py/3.3.0-4.
--
998215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998215: closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#998215: fixed in h5py 3.3.0-4)
Control: reopen -1 On Thu, Nov 04, 2021 at 01:54:07AM +, Debian Bug Tracking System wrote: >... > h5py (3.3.0-4) unstable; urgency=medium >... > - skip_ros_test_no_net.patch skips test_ros3 (catches OSError) if >network is not available. Needed since libhdf5 is now built with >ROS (S3) support, but network access is not available on buildd >servers. Closes: #998215. >... This is not sufficient, policy says [1]: For packages in the main archive, required targets must not attempt network access Packages must not even *attempt* to call home and try to inform someone that the package is being built. cu Adrian [1] https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
Bug#999646: squid-deb-proxy-client: uncaptured python exception breaks client
Package: squid-deb-proxy-client
Version: 0.8.15+nmu1
Severity: grave
Justification: breaks the client.
Control: tags -1 patch fixed-upstream
Dear Michael,
The client currently breaks with exmitting an error message to stdout:
error: uncaptured python exception, closing channel ('', 3142, 0, 0): 9223372036854775807 (:[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel
('', 3142, 0, 0): 9223372036854775807 (:[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel
(':[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
error: uncaptured python exception, closing channel
('A_IPV4_IN_THE_LAN', 3142): 9223372036854775807 (:[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
http://https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1505670;
The fix upstream is
https://github.com/mvo5/squid-deb-proxy/commit/604ba3f98beff25a8fd51783d3ffc4db5e987dab
(attaching for reference)
--
tobi
-- System Information:
Debian Release: 11.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages squid-deb-proxy-client depends on:
ii apt 2.2.3
ii avahi-utils 0.8-5
ii python3 3.9.2-3
squid-deb-proxy-client recommends no packages.
squid-deb-proxy-client suggests no packages.
-- no debconf information
>From 604ba3f98beff25a8fd51783d3ffc4db5e987dab Mon Sep 17 00:00:00 2001
From: Michael Vogt
Date: Thu, 30 Sep 2021 10:06:00 +0200
Subject: [PATCH] apt-avahi-discover: use syslog for logging in AptAvahiClient
Patch from `jasonpe...@gmail.com` - thanks!
Fixes LP: #1505670
---
apt-avahi-discover | 6 ++
1 file changed, 6 insertions(+)
diff --git a/apt-avahi-discover b/apt-avahi-discover
index dfd579b..11cc25a 100755
--- a/apt-avahi-discover
+++ b/apt-avahi-discover
@@ -10,6 +10,7 @@ import socket
import sys
import time
from subprocessimport Popen, PIPE, call
+from syslog import syslog, LOG_INFO, LOG_USER
DEFAULT_CONNECT_TIMEOUT_SEC = 2
@@ -58,6 +59,11 @@ class AptAvahiClient(asyncore.dispatcher):
def __repr__(self):
return "<{}> {}: {}".format(
self.__class__.__name__, self.addr, self.time_to_connect)
+def log(self, message):
+syslog((LOG_INFO|LOG_USER), '%s\n' % str(message))
+def log_info(self, message, type='info'):
+if type not in self.ignore_log_types:
+self.log('%s: %s' % (type, message))
def is_ipv6(a):
Processed: squid-deb-proxy-client: uncaptured python exception breaks client
Processing control commands: > tags -1 patch fixed-upstream Bug #999646 [squid-deb-proxy-client] squid-deb-proxy-client: uncaptured python exception breaks client Added tag(s) fixed-upstream and patch. -- 999646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 996951 in 5.13.9-1~exp1
Processing commands for cont...@bugs.debian.org: > # regressed in 5.12-rc1 upstream > found 996951 5.13.9-1~exp1 Bug #996951 [src:linux] linux-image-5.14.0-3-amd64: iouring looses requests Marked as found in versions linux/5.13.9-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 996951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999645: keybase: Uninstallable in Debian 11
Package: keybase Version: 5.8.1-20210930160723.fefa22edc1 Severity: grave Tags: upstream Justification: renders package unusable Some of the dependencies are not available on Debian 11. The package is uninstallable. -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages keybase depends on: ii fuse3 [fuse] 3.10.3-2 pn libappindicator1 ii libasound21.2.4-1.1 pn libgconf-2-4 ii libgtk-3-03.24.24-4 ii libnss3 2:3.61-1 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii lsof 4.93.2+dfsg-1.1 ii procps2:3.3.17-5 ii psmisc23.4-2 keybase recommends no packages. keybase suggests no packages.
Processed: bug 996557 is forwarded to https://lore.kernel.org/all/ywgyiyxlriayy...@intel.com/
Processing commands for cont...@bugs.debian.org:
> forwarded 996557 https://lore.kernel.org/all/ywgyiyxlriayy...@intel.com/
Bug #996557 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.14.0-3-686-pae-unsigned: just about every sse2 program crashes
with a SIGFPE
Set Bug forwarded-to-address to
'https://lore.kernel.org/all/ywgyiyxlriayy...@intel.com/'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
