Bug#1017075: #1017075 dask - autopkgtest regression on i386 and armhf
On Mon, 2022-08-22 at 08:37 +0200, Graham Inggs wrote: > Hi Drew > > On Sun, 21 Aug 2022 at 19:08, Drew Parsons > wrote: > > In regards to bug severity, the dask debci failures are now marked > > as > > "Not a regression" so they won't hold up migration of dask. > > Dask's autopkgtests are failing in testing since the removal of > scikit-learn. I raised the severity of this bug precisely to prevent > this accidental migration. > > > Graham, should the bug severity therefore be reduced from Serious > > back > > down to Important to enable migration of both dask and scipy? > > Please don't. Hopefully working around the 32-bit test failures is enough to resolve the problems for scipy?
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 1017499 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7117 Bug #1017499 [src:mesa] mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen on VirtIO Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mesa/mesa/-/issues/7117'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1017499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Upstream bug report
Processing commands for cont...@bugs.debian.org: > tags 1017499 + upstream Bug #1017499 [src:mesa] mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen on VirtIO Added tag(s) upstream. > -- Stopping processing here. Please contact me if you need assistance. -- 1017499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017499: Upstream bug report
tags 1017499 + upstream -- I was about to report the bug upstream, but it looks like Leandro beat me to it. https://gitlab.freedesktop.org/mesa/mesa/-/issues/7117 -- Ben Westover signature.asc Description: PGP signature
Bug#1017267: marked as done (golang-github-nkovacs-streamquote: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/nkovacs/streamquote returned exit code 1)
Your message dated Tue, 23 Aug 2022 23:03:52 + with message-id and subject line Bug#1017267: fixed in golang-github-nkovacs-streamquote 1.0.0-4 has caused the Debian Bug report #1017267, regarding golang-github-nkovacs-streamquote: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/nkovacs/streamquote 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.) -- 1017267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-nkovacs-streamquote Version: 1.0.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 8 github.com/nkovacs/streamquote > internal/goos > internal/goarch > internal/unsafeheader > runtime/internal/syscall > internal/goexperiment > internal/race > runtime/internal/atomic > internal/cpu > sync/atomic > math/bits > internal/abi > runtime/internal/math > runtime/internal/sys > unicode/utf8 > internal/bytealg > math > runtime > internal/reflectlite > sync > errors > io > strconv > github.com/nkovacs/streamquote >dh_auto_test -O--builddirectory=_build -O--buildsystem=golang > cd _build && go test -vet=off -v -p 8 github.com/nkovacs/streamquote > === RUN TestConverter > --- PASS: TestConverter (0.00s) > === RUN TestLargeString > streamquote_test.go:102: Large string does not match > --- FAIL: TestLargeString (0.69s) > FAIL > FAIL github.com/nkovacs/streamquote 0.700s > FAIL > dh_auto_test: error: cd _build && go test -vet=off -v -p 8 > github.com/nkovacs/streamquote returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/08/13/golang-github-nkovacs-streamquote_1.0.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: golang-github-nkovacs-streamquote Source-Version: 1.0.0-4 Done: Martina Ferrari We believe that the bug you reported is fixed in the latest version of golang-github-nkovacs-streamquote, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martina Ferrari (supplier of updated golang-github-nkovacs-streamquote package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 23 Aug 2022 15:36:46 + Source: golang-github-nkovacs-streamquote Architecture: source Version: 1.0.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Martina Ferrari Closes: 1017267 Changes: golang-github-nkovacs-streamquote (1.0.0-4) unstable; urgency=medium . * Team upload. * Add patch to Convert code to match changes in go 1.18. Closes: #1017267 Checksums-Sha1: 6e4600ac77ee51833064d20d722c42a4bffa5714 2308 golang-git
Bug#1017997: hdf5 ftbfs on s390x
Hi Steve, Steve Langasek a écrit le 23/08/2022 à 22:40 : Package: hdf5 Version: 1.10.8+repack-1 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Hi Gilles, hdf5 has been failing to build from source on s390x. In Ubuntu we have a patch to fix this build failure. Please consider including it in Debian as well. Thanks for this patch. However I can't reproduce the FTBFS on the s390x porterbox zelenka.debian.org. Would you mind sharing build logs? Best, _g.
Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.
On Tue, 23 Aug 2022 at 16:44:54 -0400, Jeffrey Walton wrote: > On Tue, Aug 23, 2022 at 4:40 PM Simon McVittie wrote: > > On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote: > > > The final link fails with multiple definitions of the various atomic > > > builtins: > > > > > > > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; > > > > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94: > > > > first defined here > > Also see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104248#c2 (and > more generally https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358). Those are related, but seem like the opposite issue: I'm getting a build failure because I somehow end up with two copies of __sync_fetch_and_add_4, whereas those bugs are about having zero copies of similar compiler-provided functions. We want exactly one copy :-) Or are you saying that I'm getting these multiple definitions *because*, unlike gcc-11, gcc-12 is automatically providing symbols like __sync_fetch_and_add_4 in order to resolve those gcc bug reports? In any case it seems to be possible to work around this by forcing gcc-11, which is not great (toolchain maintainers dislike uses of a non-default gcc) but arguably better than FTBFS. smcv
Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.
On Tue, Aug 23, 2022 at 4:40 PM Simon McVittie wrote: > > Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1786623 > Control: affects -1 + src:mozjs102 > > On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote: > > The final link fails with multiple definitions of the various atomic > > builtins: > > > > > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; > > > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94: > > > first defined here > > Reported upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1786623 Also see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104248#c2 (and more generally https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358). > > (For completeness: 91.10.0-1 and 91.12.0-1 have an additional failure > > reason involving undefined references to > > std::type_info::operator==(std::type_info const&) const, but I believe > > that was fixed in 91.12.0-2 by removing an obsolete patch.) > > Correction, it was fixed by a patch removing an obsolete workaround. > Reported as https://bugzilla.mozilla.org/show_bug.cgi?id=1786621 (but we > already have a patch for this, so it's an upstream bug but not a Debian bug) Jeff
Bug#1017997: hdf5 ftbfs on s390x
Package: hdf5
Version: 1.10.8+repack-1
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Hi Gilles,
hdf5 has been failing to build from source on s390x. In Ubuntu we have a
patch to fix this build failure. Please consider including it in Debian as
well.
I notice that the newer upstream version of hdf5 that's in experimental does
not fail to build anymore on s390x, so perhaps another solution would be to
upload that version to unstable.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru hdf5-1.10.8+repack/debian/patches/fix-signed_headers_dest.patch
hdf5-1.10.8+repack/debian/patches/fix-signed_headers_dest.patch
--- hdf5-1.10.8+repack/debian/patches/fix-signed_headers_dest.patch
1969-12-31 16:00:00.0 -0800
+++ hdf5-1.10.8+repack/debian/patches/fix-signed_headers_dest.patch
2021-11-07 18:21:41.0 -0800
@@ -0,0 +1,15 @@
+--- a/src/H5FDs3comms.c
b/src/H5FDs3comms.c
+@@ -1717,8 +1717,10 @@
+ node = node->next;
+ } /* end while node is not NULL */
+
+-/* remove trailing ';' from signed headers sequence */
+-signed_headers_dest[HDstrlen(signed_headers_dest) - 1] = '\0';
++if (*signed_headers_dest != '\0') {
++/* remove trailing ';' from signed headers sequence */
++signed_headers_dest[HDstrlen(signed_headers_dest) - 1] = '\0';
++}
+
+ /* append signed headers and payload hash
+ * NOTE: at present, no HTTP body is handled, per the nature of
diff -Nru hdf5-1.10.8+repack/debian/patches/series
hdf5-1.10.8+repack/debian/patches/series
--- hdf5-1.10.8+repack/debian/patches/series2022-04-29 08:47:00.0
-0700
+++ hdf5-1.10.8+repack/debian/patches/series2022-08-22 20:47:47.0
-0700
@@ -4,3 +4,4 @@
relax-version-check.patch
fix-unaligned-accesses.patch
reproducibility.patch
+fix-signed_headers_dest.patch
Processed: Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.
Processing control commands: > forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1786623 Bug #1017979 [src:mozjs91] mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc. Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1786623'. > affects -1 + src:mozjs102 Bug #1017979 [src:mozjs91] mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc. Added indication that 1017979 affects src:mozjs102 -- 1017979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1786623 Control: affects -1 + src:mozjs102 On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote: > The final link fails with multiple definitions of the various atomic > builtins: > > > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; > > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94: > > first defined here Reported upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1786623 > (For completeness: 91.10.0-1 and 91.12.0-1 have an additional failure > reason involving undefined references to > std::type_info::operator==(std::type_info const&) const, but I believe > that was fixed in 91.12.0-2 by removing an obsolete patch.) Correction, it was fixed by a patch removing an obsolete workaround. Reported as https://bugzilla.mozilla.org/show_bug.cgi?id=1786621 (but we already have a patch for this, so it's an upstream bug but not a Debian bug) smcv
Bug#1017952: marked as done (groupadd: invalid group ID '-1' when adding with --uid)
Your message dated Tue, 23 Aug 2022 20:34:34 + with message-id and subject line Bug#1017952: fixed in adduser 3.128 has caused the Debian Bug report #1017952, regarding groupadd: invalid group ID '-1' when adding with --uid 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.) -- 1017952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: adduser Version: 3.124 Severity: serious Justification: Makes creating chroots fail Hello, While creating a buildd chroot, I get: + sudo chroot /home/buildd/chroots/sid adduser --uid 1001 --disabled-password --gecos buildd buildd Adding user `buildd' ... Adding new group `buildd' (-1) ... groupadd: invalid group ID '-1' It seems that the new code for choosing a gid is broken in 3.124, while it was fine in 3.123. Samuel -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.19.0 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages adduser depends on: ii cdebconf [debconf-2.0] 0.263 ii debconf [debconf-2.0] 1.5.79 ii passwd 1:4.11.1+dfsg1-2 adduser recommends no packages. Versions of packages adduser suggests: ii cron3.0pl1-149 ii liblocale-gettext-perl 1.07-4+b2 ii perl5.34.0-5 -- debconf information excluded -- Samuel --- Pour une évaluation indépendante, transparente et rigoureuse ! Je soutiens la Commission d'Évaluation de l'Inria. --- End Message --- --- Begin Message --- Source: adduser Source-Version: 3.128 Done: Marc Haber We believe that the bug you reported is fixed in the latest version of adduser, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Haber (supplier of updated adduser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 23 Aug 2022 21:40:01 +0200 Source: adduser Architecture: source Version: 3.128 Distribution: unstable Urgency: medium Maintainer: Debian Adduser Developers Changed-By: Marc Haber Closes: 1017888 1017912 1017952 Changes: adduser (3.128) unstable; urgency=medium . [ Marc Haber ] * increase timeouts, reduce number of tests for delgroup_perf.t they have timed out in Debian infrastructure * even the legacy testsuite needs cron * Write defaults explicitly in configuration file templates. Thanks to Christoph Anton Mitterer (Closes: #1017888) * skip most of the version checks in preinst Thanks to Vincent Lefevre (Closes: #1017912) * document that the --ingroup group must exist * fix handling of explicitly set --uid and --gid. Thanks to Samuel Thibault (Closes: #1017952) . [ Benjamin Drung ] * Document parameter for checkname function Checksums-Sha1: 4e43a9e1e67be60fb8d8064bb4d5359d2cd7941f 1671 adduser_3.128.dsc c330f53ee9cab543988eccea9f26e889960d34f7 230008 adduser_3.128.tar.xz 52c7c2d95deaf17af1a5aefcde110a35ffa99bbc 6132 adduser_3.128_source.buildinfo Checksums-Sha256: 65864a975fc82d2d876774e16b06ae97f0545a526131772f914fb96542614af3 1671 adduser_3.128.dsc 5b6ec6a1884d785867563fd34e9e589dd25a0b5bf7689ba7c3434854ab47c73c 230008 adduser_3.128.tar.xz 26c63dc1b3c38e909aafb843813446a8dcda774cdbec74a9e02c0491ec993ac2 6132 adduser_3.128_source.buildinfo Files: 0e376a7a03560fa0b6cb436830977
Processed: bug 1017155 is forwarded to https://github.com/fuzzylite/fuzzylite/issues/94
Processing commands for cont...@bugs.debian.org: > forwarded 1017155 https://github.com/fuzzylite/fuzzylite/issues/94 Bug #1017155 [src:fuzzylite] fuzzylite: FTBFS: catch.hpp:6378:33: error: size of array ‘altStackMem’ is not an integral constant-expression Set Bug forwarded-to-address to 'https://github.com/fuzzylite/fuzzylite/issues/94'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017964: marked as done (rust-pleaser FTBFS/autopkgtest failure with nix 0.25)
Your message dated Tue, 23 Aug 2022 19:50:15 +
with message-id
and subject line Bug#1017964: fixed in rust-pleaser 0.5.3-1
has caused the Debian Bug report #1017964,
regarding rust-pleaser FTBFS/autopkgtest failure with nix 0.25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1017964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-pleaser
Version: 0.5.1-4
Severity: serious
rust-pleaser fails to build with the new version of rust-nix.
error[E0061]: this function takes 0 arguments but 1 argument was supplied
--> src/lib.rs:416:19
|
416 | ro.hostname = gethostname(&mut buf)
| ^^^ supplied 1 argument
| |
| expected 0 arguments
|
note: function defined here
--> /tmp/tmp.ADzPxvKlSH/registry/nix-0.25.0/src/unistd.rs:1020:8
|
1020 | pub fn gethostname() -> Result {
|^^^
The API of gethostname has changed. Now instead of taking a buffer
from the caller it retuns a Result
Adjusting the code was easy enough, but I notice that the buffer size
used by the new version of gethostname is about 4 times larger than
the one used previously in pleaser. I have not investigated whether
this increase in potential string length has any security implications
for pleaser.
Patch at
https://salsa.debian.org/rust-team/debcargo-conf/-/blob/master/src/pleaser/debian/patches/nix-0.25.patch
Review by someone who knows the codebase would be appreciated.
--- End Message ---
--- Begin Message ---
Source: rust-pleaser
Source-Version: 0.5.3-1
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
rust-pleaser, 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 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated rust-pleaser
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 23 Aug 2022 19:29:25 +
Source: rust-pleaser
Architecture: source
Version: 0.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Closes: 1017964
Changes:
rust-pleaser (0.5.3-1) unstable; urgency=medium
.
* Team upload.
* Package pleaser 0.5.3 from crates.io using debcargo 2.5.0
* Drop old patches, no longer needed/relavent.
* Add patch to fix build with nix 0.25. (Closes: #1017964)
Checksums-Sha1:
c9dbfa5b13fc30feefb7e0d5bd1e3cbbd340a9b4 2569 rust-pleaser_0.5.3-1.dsc
f729aca10afa70dccac42f6b1ef251544ed3ad46 55191 rust-pleaser_0.5.3.orig.tar.gz
78cfc43d2ca05a20dbd0120f04892fda6a37f4a5 3812
rust-pleaser_0.5.3-1.debian.tar.xz
104b06d36b7a3b4d6e01f11cc3df852c68d24854 10231
rust-pleaser_0.5.3-1_source.buildinfo
Checksums-Sha256:
08d4f8f5198e3f3c451b2dd3046f344a9b3e7279459ebba2a017d838d54688ad 2569
rust-pleaser_0.5.3-1.dsc
ac54c26a0db3a5b75702cb6bcfd10d07c40d0b067bc77d8e2669bfc0bae160d0 55191
rust-pleaser_0.5.3.orig.tar.gz
b570fab4dab1ff7928960a657ad55466c55407a5b01478befc2d220a11da6ced 3812
rust-pleaser_0.5.3-1.debian.tar.xz
db1ec60b7af5c9ee7e55ba9416be5cc8a0a87e13f73ae12d4223f21c0ec30a77 10231
rust-pleaser_0.5.3-1_source.buildinfo
Files:
4424a849787b62d389960605073be2a6 2569 utils optional rust-pleaser_0.5.3-1.dsc
660047910f8495d87ac2dcc4b9560f1d 55191 utils optional
rust-pleaser_0.5.3.orig.tar.gz
4414aba24f439a774d77141ef076ac33 3812 utils optional
rust-pleaser_0.5.3-1.debian.tar.xz
47d445e3bcd5b4937af65e8ec43896fb 10231 utils optional
rust-pleaser_0.5.3-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmMFKrMUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XugBhAAmPCKtVP6s0tlfmFQaO0pGLmAlRfA
GSNRaH+KRxd2Vl1XgxyarDboc2ULru0jhjZOVuJ5IrdTocNR5hIgeEvtj+PwSEE/
q1CxTefJsgHpijc9pfmG4vbr6Lw2P9rHg0Op5xch8GmLoZesrm3zr0IBzBqmWNZt
bhMTBCXAX4YgG7nzS2+X9IcfyYVhAM2zRYKYzTHh9XqNBVfJ8V/JcThiqc1xAdbc
6O+OD0I9CMhDaCqdn3Ta9TPAmSIU07w8V2QQ4KO9NHJ7HP3t/wQrnUgwcIIRroKK
xOWBHXeTSvrS9/u6YqEUhVNTnNO63PPuXlQJu1ZAm5P4BkRdXnTktSiufIYOJUyA
eLTn1S
Processed: Bug#1017952 marked as pending in adduser
Processing control commands: > tag -1 pending Bug #1017952 [adduser] groupadd: invalid group ID '-1' when adding with --uid Added tag(s) pending. -- 1017952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017952: marked as pending in adduser
Control: tag -1 pending Hello, Bug #1017952 in adduser 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/adduser/-/commit/3a714d732a14f3972a4a7af5849c52e11dd9a76d fix handling of explicitly set --uid and --gid This needed some logic changes in the code, hence the change is relatively big. Thanks: Samuel Thibault Closes: #1017952 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017952
Bug#1017840: debian-security-support: cannot create /var/lib/debian-security-support/security-support.semaphore: Permission
On Tue, 2022-08-23 at 16:23 +, Holger Levsen wrote: > users must not be cleaned up (=removed) on package removal Well perhaps not a must as per policy, but I think for debian-security- support it would still make sense to clean up the user, or do you expect anyone to create files under that user which would then have no valid user/group? :-) Cheers, Chris.
Bug#1017428: marked as done (src:libnanomsg-raw-perl: fails to migrate to testing for too long: FTBFS on s390x)
Your message dated Tue, 23 Aug 2022 19:06:30 + with message-id and subject line Bug#1017428: fixed in libnanomsg-raw-perl 0.10-3 has caused the Debian Bug report #1017428, regarding src:libnanomsg-raw-perl: fails to migrate to testing for too long: FTBFS on s390x 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.) -- 1017428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnanomsg-raw-perl Version: 0.10-1 Severity: serious X-Debbugs-CC: Jelmer Vernooij Control: close -1 0.10-2 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:libnanomsg-raw-perl has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on s390x where it built successfully in the past. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=libnanomsg-raw-perl OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libnanomsg-raw-perl Source-Version: 0.10-3 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libnanomsg-raw-perl, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libnanomsg-raw-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Aug 2022 20:37:51 +0200 Source: libnanomsg-raw-perl Architecture: source Version: 0.10-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1017428 Changes: libnanomsg-raw-perl (0.10-3) unstable; urgency=medium . * Team upload. * Mark fragile timeout tests as TODO. (Closes: #1017428) * Use uscan macros in debian/watch. * Update debian/upstream/metadata. * Update Upstream-Contact in debian/copyright. * Declare compliance with Debian Policy 4.6.1. * Set Rules-Requires-Root: no. * Annotate test-only build dependencies with . Checksums-Sha1: 3ec29968bb8a6d5d5be6a8577fdb9bff04e09616 2479 libnanomsg-raw-perl_0.10-3.dsc 21b7cd85abda21a81657941c20a95da26834a0e7 3396 libnanomsg-raw-perl_0.10-3.debian.tar.xz Checksums-Sha256: 6769012d76ada431963bab762dd39f32b1a209c8eaf37e18d4a8e904211fd6c7 2479 libnanomsg-raw-perl_0.10-3.dsc db78a8e706af08cc763378d576c482d68148746fd828665c7274a2644cd9b9f8 3396 libnanomsg-raw-perl_0.10-3.debian.tar.xz Files: 8423ca6b4e6c913aec45c9e9a3d854c1 2479 perl optional libnanomsg-raw-perl_0.10-3.dsc 540a157e54a85dbafcbde70ca4ff4d5b 3396 perl optional libnanomsg-raw-perl_0.10-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmMFHyJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBN
Bug#1016982: marked as done (rails: CVE-2022-27777)
Your message dated Tue, 23 Aug 2022 19:07:03 + with message-id and subject line Bug#1016982: fixed in rails 2:6.1.6.1+dfsg-1 has caused the Debian Bug report #1016982, regarding rails: CVE-2022-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rails X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for rails. CVE-2022-2[0]: | A XSS Vulnerability in Action View tag helpers >= 5.2.0 and < | 5.2.0 which would allow an attacker to inject content if able to | control input into specific attributes. Fixed by: https://github.com/rails/rails/commit/123f42a573f7fcbf391885c135ca809f21615180 (v6.1.5.1) Regression fix: https://github.com/rails/rails/commit/7c2da9e51c5c02643f30d83aaad3ed5062adcad8 (6.1.6) Fixed by: https://github.com/rails/rails/commit/36a6dad07d572a0098c29d6d96a226638a7caa38 (v6.0.4.8) Regression fix: https://github.com/rails/rails/commit/1b5df893d82a27da907e9b8b75deff13179d1df3 (v6.0.5) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-2 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: rails Source-Version: 2:6.1.6.1+dfsg-1 Done: Gabriela Pivetta We believe that the bug you reported is fixed in the latest version of rails, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gabriela Pivetta (supplier of updated rails 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: Thu, 18 Aug 2022 15:46:46 -0300 Source: rails Architecture: source Version: 2:6.1.6.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Gabriela Pivetta Closes: 1011941 1016140 1016982 Changes: rails (2:6.1.6.1+dfsg-1) unstable; urgency=medium . [ Pirate Praveen ] * Remove build profile from runtime dependencies. . [ Utkarsh Gupta ] * New upstream version 6.1.6.1+dfsg. (Fixes: CVE-2022-22577, CVE-2022-2, CVE-2022-32224) (Closes: #1011941, #1016982, #1016140) * d/control: Update minimum version of ruby-selenium-webdriver to 4.0.0 for autopkgtest. :) . [ Gabriela Pivetta ] * d/p/activerecord-add-missing-require-statements.patch: Drop patch that has been merged upstream. * d/patches: Refresh patches. Checksums-Sha1: f4dc127f282f34879bbcf2a5755668e0a72c586a 4798 rails_6.1.6.1+dfsg-1.dsc e715921994f93ed9f2cb4f4ce5925628e15d4519 8173652 rails_6.1.6.1+dfsg.orig.tar.xz 252352526d551285d44dbee7b4f4f69fa76fa058 101584 rails_6.1.6.1+dfsg-1.debian.tar.xz 5a5e0478cd61d571e5d11d90b07774066e94d89a 14728 rails_6.1.6.1+dfsg-1_source.buildinfo Checksums-Sha256: 8d507d77b39212eabc415e7d0598ae4d0412541dd207423cf824f1ab266678b9 4798 rails_6.1.6.1+dfsg-1.dsc 6d17ff42c877d7490a6e832f1dc540178bc9203083d7a487a2d6ce809adb1b10 8173652 rails_6.1.6.1+dfsg.orig.tar.xz 7967178486539c5c3105253bcdb9ffb0b11a6cf0abb0cf4e113073612bc0f7c1 101584 rails_6.1.6.1+dfsg-1.debian.tar.xz e99aa9f9aedccc59a88562a4af6f407dd4cc57730d082229832f0e56e394b242 14728 rails_6.1.6.1+dfsg-1_source.buildinfo Files: 837d10aac534854f5302931b68376a9a 4798 ruby optional rails_6.1.6.1+dfsg-1.dsc 8eb8019844e018cf1e1356c3fbab51c9 8173652 ruby optional rails_6.1.6.1+dfsg.orig.tar.xz 787e0c20b8d27ba0e5a24f7f98c87583 101584 ruby optional rails_6.1.6.1+dfsg-1.debian.tar.xz c325a6a49df70054ef8bda47c034ce1e 14728 ruby optional rails_6.1.6.1+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAmMFHdkACgkQgj6WdgbD S5YDiBAAxo9hLFbfh3mQJCRbFpuEXnMUfq584G/hyg6mRuE8rU2SkoTe0NvTNp8p 5rVeepxnFH+yUnb8Br8BTtTi6kaFf3yBUcJi29zLO5BeEFj6V1gZECa+DVztpGgN 1djhCDYKVB7lYXx5rCAVU8TurjPXhXnQ3XO6958UE
Bug#1016140: marked as done (rails: CVE-2022-32224)
Your message dated Tue, 23 Aug 2022 19:07:03 + with message-id and subject line Bug#1016140: fixed in rails 2:6.1.6.1+dfsg-1 has caused the Debian Bug report #1016140, regarding rails: CVE-2022-32224 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.) -- 1016140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rails X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for rails. CVE-2022-32224[0]: https://github.com/advisories/GHSA-3hhc-qp5v-9p2j If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-32224 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32224 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: rails Source-Version: 2:6.1.6.1+dfsg-1 Done: Gabriela Pivetta We believe that the bug you reported is fixed in the latest version of rails, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gabriela Pivetta (supplier of updated rails 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: Thu, 18 Aug 2022 15:46:46 -0300 Source: rails Architecture: source Version: 2:6.1.6.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Gabriela Pivetta Closes: 1011941 1016140 1016982 Changes: rails (2:6.1.6.1+dfsg-1) unstable; urgency=medium . [ Pirate Praveen ] * Remove build profile from runtime dependencies. . [ Utkarsh Gupta ] * New upstream version 6.1.6.1+dfsg. (Fixes: CVE-2022-22577, CVE-2022-2, CVE-2022-32224) (Closes: #1011941, #1016982, #1016140) * d/control: Update minimum version of ruby-selenium-webdriver to 4.0.0 for autopkgtest. :) . [ Gabriela Pivetta ] * d/p/activerecord-add-missing-require-statements.patch: Drop patch that has been merged upstream. * d/patches: Refresh patches. Checksums-Sha1: f4dc127f282f34879bbcf2a5755668e0a72c586a 4798 rails_6.1.6.1+dfsg-1.dsc e715921994f93ed9f2cb4f4ce5925628e15d4519 8173652 rails_6.1.6.1+dfsg.orig.tar.xz 252352526d551285d44dbee7b4f4f69fa76fa058 101584 rails_6.1.6.1+dfsg-1.debian.tar.xz 5a5e0478cd61d571e5d11d90b07774066e94d89a 14728 rails_6.1.6.1+dfsg-1_source.buildinfo Checksums-Sha256: 8d507d77b39212eabc415e7d0598ae4d0412541dd207423cf824f1ab266678b9 4798 rails_6.1.6.1+dfsg-1.dsc 6d17ff42c877d7490a6e832f1dc540178bc9203083d7a487a2d6ce809adb1b10 8173652 rails_6.1.6.1+dfsg.orig.tar.xz 7967178486539c5c3105253bcdb9ffb0b11a6cf0abb0cf4e113073612bc0f7c1 101584 rails_6.1.6.1+dfsg-1.debian.tar.xz e99aa9f9aedccc59a88562a4af6f407dd4cc57730d082229832f0e56e394b242 14728 rails_6.1.6.1+dfsg-1_source.buildinfo Files: 837d10aac534854f5302931b68376a9a 4798 ruby optional rails_6.1.6.1+dfsg-1.dsc 8eb8019844e018cf1e1356c3fbab51c9 8173652 ruby optional rails_6.1.6.1+dfsg.orig.tar.xz 787e0c20b8d27ba0e5a24f7f98c87583 101584 ruby optional rails_6.1.6.1+dfsg-1.debian.tar.xz c325a6a49df70054ef8bda47c034ce1e 14728 ruby optional rails_6.1.6.1+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAmMFHdkACgkQgj6WdgbD S5YDiBAAxo9hLFbfh3mQJCRbFpuEXnMUfq584G/hyg6mRuE8rU2SkoTe0NvTNp8p 5rVeepxnFH+yUnb8Br8BTtTi6kaFf3yBUcJi29zLO5BeEFj6V1gZECa+DVztpGgN 1djhCDYKVB7lYXx5rCAVU8TurjPXhXnQ3XO6958UE1renItAv/B3KHZY/gd8XzFw z2EYXV5Hd4vo9KSWGiaG/RWD8AJajICs/IqjDNHyNGepvhR+6o3Jtor/1ZHRTdIE IUqVtq8XQDvvuk+Z+NPqkEVXwLELg/H8nNyJGzSTrks4szG5ZyB7toziArV4Q0Dg t5bm7Fp9N1flyat2zLTgkH9yteEA56f91Z5wrZeRNMNvAUtGtXmOQGQsgpWriwWL jc+JsCWF+iMmJLmoJfEvNRY8uHp9wlh0xQ2U/CPE23Mu8xz3ZHJv67YPHs7Cxvb1 +BGuM/xVu7kd9iMiYpKImqoj54Rf1WVEOF5LDmQ3s7EomgAgte8Iy3p5zX/AK73o HbVPwJS5jKOS1b6cA2ejDX2mEnenv/mLFtjWHME4uaBHhn2F7j1/l5SRfPDINerO DX+xC1TkNAsHS/rdn8u0+iONcLPgonWhMl8spzgY7ZydA6YtdsOEIX+8oowlWLTo Kwv8dxj4+O3syXhb9qRP7M7xICyVeRP1DoGqD9Tc02ASnP9vrrY= =SPww --
Bug#1017802: marked as done (gr-funcube FTBFS witn fmtlib 9.0.0 (?))
Your message dated Tue, 23 Aug 2022 19:00:11 +
with message-id
and subject line Bug#1017802: fixed in gr-funcube 3.10.0~rc2-2
has caused the Debian Bug report #1017802,
regarding gr-funcube FTBFS witn fmtlib 9.0.0 (?)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1017802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-funcube
Version: 3.10.0~rc2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gr-funcube&ver=3.10.0~rc2-1%2Bb1
...
In file included from /usr/include/spdlog/fmt/fmt.h:27,
from /usr/include/spdlog/common.h:45,
from /usr/include/gnuradio/logger.h:36,
from /usr/include/gnuradio/custom_lock.h:15,
from /usr/include/gnuradio/buffer.h:15,
from /usr/include/gnuradio/buffer_double_mapped.h:15,
from /usr/include/gnuradio/io_signature.h:17,
from /usr/include/gnuradio/basic_block.h:15,
from /usr/include/gnuradio/block.h:17,
from /<>/lib/../include/funcube/fcd_control.h:11,
from /<>/lib/fcd_control_impl.h:11,
from /<>/lib/fcd_control_impl.cc:12:
/usr/include/fmt/core.h: In instantiation of ‘constexpr
fmt::v9::detail::value fmt::v9::detail::make_value(T&&) [with Context
= fmt::v9::basic_format_context; T = unsigned char*
const&]’:
/usr/include/fmt/core.h:1753:29: required from ‘constexpr
fmt::v9::detail::value fmt::v9::detail::make_arg(T&&) [with bool
IS_PACKED = true; Context = fmt::v9::basic_format_context; type = fmt::v9::detail::type::custom_type; T = unsigned
char* const&; typename std::enable_if::type = 0]’
/usr/include/fmt/core.h:1877:77: required from ‘constexpr
fmt::v9::format_arg_store::format_arg_store(T&& ...) [with T =
{unsigned char* const&}; Context =
fmt::v9::basic_format_context; Args = {unsigned
char*}]’
/usr/include/fmt/core.h:1894:38: required from ‘constexpr
fmt::v9::format_arg_store::type>::type ...> fmt::v9::make_format_args(Args&&
...) [with Context = basic_format_context; Args = {unsigned
char* const&}]’
/usr/include/spdlog/logger.h:370:68: required from ‘void
spdlog::logger::log_(spdlog::source_loc, spdlog::level::level_enum,
spdlog::string_view_t, Args&& ...) [with Args = {unsigned char* const&};
spdlog::string_view_t = fmt::v9::basic_string_view]’
/usr/include/spdlog/logger.h:90:13: required from ‘void
spdlog::logger::log(spdlog::source_loc, spdlog::level::level_enum,
fmt::v9::format_string, Args&& ...) [with Args = {unsigned char*
const&}; fmt::v9::format_string = fmt::v9::basic_format_string]’
/usr/include/spdlog/logger.h:96:12: required from ‘void
spdlog::logger::log(spdlog::level::level_enum, fmt::v9::format_string,
Args&& ...) [with Args = {unsigned char* const&}; fmt::v9::format_string
= fmt::v9::basic_format_string]’
/usr/include/spdlog/logger.h:158:12: required from ‘void
spdlog::logger::info(fmt::v9::format_string, Args&& ...) [with Args =
{unsigned char* const&}; fmt::v9::format_string =
fmt::v9::basic_format_string]’
/usr/include/gnuradio/logger.h:156:23: required from ‘void
gr::logger::info(const spdlog::string_view_t&, const Args& ...) [with Args =
{unsigned char*}; spdlog::string_view_t = fmt::v9::basic_string_view]’
/<>/lib/fcd_control_impl.cc:61:19: required from here
/usr/include/fmt/core.h:1727:17: error: static assertion failed: Formatting of
non-void pointers is disallowed.
1727 | static_assert(formattable_pointer,
| ^~~
/usr/include/fmt/core.h:1727:17: note: ‘formattable_pointer’ evaluates to false
In file included from /usr/include/spdlog/fmt/fmt.h:27,
from /usr/include/spdlog/common.h:45,
from /usr/include/gnuradio/logger.h:36,
from /usr/include/gnuradio/custom_lock.h:15,
from /usr/include/gnuradio/buffer.h:15,
from /usr/include/gnuradio/buffer_double_mapped.h:15,
from /usr/include/gnuradio/io_signature.h:17,
from /usr/include/gnuradio/basic_block.h:15,
from /usr/include/gnuradio/block.h:17,
from
/<>/lib/../include/funcube/fcdpp_control.h:11,
from /<>/lib/fcdpp_control_impl.h:12,
from /<>/lib/fcdpp_control_impl.cc:13:
/usr/include/fmt/core.h: In instantiation of ‘constexpr
fmt::v9::detail::value fmt::v9::detail::make_value(T&&) [with Context
= fmt::v9::basic_format_context;
Processed: reassign
Processing commands for cont...@bugs.debian.org: > reassign 1016625 nvidia-cuda-toolkit 11.4.3-4 Bug #1016625 [src:bart-cuda] Please update nvidia-cuda-toolkit to 11.5.1 or later Bug reassigned from package 'src:bart-cuda' to 'nvidia-cuda-toolkit'. No longer marked as found in versions bart-cuda/0.7.00-5. Ignoring request to alter fixed versions of bug #1016625 to the same values previously set Bug #1016625 [nvidia-cuda-toolkit] Please update nvidia-cuda-toolkit to 11.5.1 or later Marked as found in versions nvidia-cuda-toolkit/11.4.3-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1016625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1017428 marked as pending in libnanomsg-raw-perl
Processing control commands: > tag -1 pending Bug #1017428 [src:libnanomsg-raw-perl] src:libnanomsg-raw-perl: fails to migrate to testing for too long: FTBFS on s390x Added tag(s) pending. -- 1017428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017428: marked as pending in libnanomsg-raw-perl
Control: tag -1 pending Hello, Bug #1017428 in libnanomsg-raw-perl 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/perl-team/modules/packages/libnanomsg-raw-perl/-/commit/f2a641436e594c8c1b4acb87f7e39eb20f228c23 Mark fragile timeout tests as TODO. Closes: #1017428 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017428
Bug#1016625: bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'
Control: reassign -1 nvidia-cuda-toolkit/11.4.3-4 Control: retitle -1 Please update nvidia-cuda-toolkit to 11.5.1 or later On 8/23/22 23:58, Martin Uecker wrote: Am Dienstag, den 23.08.2022, 23:45 +0530 schrieb Nilesh Patra: On Tue, Aug 23, 2022 at 07:00:44PM +0200, Martin Uecker wrote: I think I fixed this. At least it compiles locally in a sid pbuilder environment, but I needed to build-depend on gcc-10. gcc-10 will be removed from the archive some day, so this cannot be a permanent fix. It is a workaround for another cuda problem, which apparently can not deal with newer glibc headers and which is fixed in 11.5.1 not yet in Debian. In that case, I am re-assigning this to nvidia-cuda-toolkit. There is 11.5.2 in exp but it needs to get to unstable. -- Best, Nilesh OpenPGP_signature Description: OpenPGP digital signature
Processed (with 1 error): Re: bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'
Processing control commands: > reassign -1 nvidia-cuda-toolkit/11.4.3-4 Unknown command or malformed arguments to command. > retitle -1 Please update nvidia-cuda-toolkit to 11.5.1 or later Bug #1016625 [src:bart-cuda] bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' Changed Bug title to 'Please update nvidia-cuda-toolkit to 11.5.1 or later' from 'bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value''. -- 1016625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Update bug
Processing commands for cont...@bugs.debian.org: > severity 1017083 normal Bug #1017083 [src:bibledit] bibledit: Some sources are not included in your package Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1017428 in 0.10-2
Processing commands for cont...@bugs.debian.org:
> found 1017428 0.10-2
Bug #1017428 {Done: Paul Gevers } [src:libnanomsg-raw-perl]
src:libnanomsg-raw-perl: fails to migrate to testing for too long: FTBFS on
s390x
Marked as found in versions libnanomsg-raw-perl/0.10-2; no longer marked as
fixed in versions libnanomsg-raw-perl/0.10-2 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1017428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016625: bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'
Am Dienstag, den 23.08.2022, 23:45 +0530 schrieb Nilesh Patra: > On Tue, Aug 23, 2022 at 07:00:44PM +0200, Martin Uecker wrote: > > I think I fixed this. At least it compiles locally in > > a sid pbuilder environment, but I needed to build-depend > > on gcc-10. > > gcc-10 will be removed from the archive some day, so this cannot > be a permanent fix. > It is a workaround for another cuda problem, which apparently can not deal with newer glibc headers and which is fixed in 11.5.1 not yet in Debian.
Processed (with 1 error): Update bug
Processing commands for cont...@bugs.debian.org: > severity 1017083 severity Severity level `severity' is not known. Recognized are: critical, grave, serious, important, normal, minor, wishlist, fixed. > tags 1017083 moreinfo unreproducible Bug #1017083 [src:bibledit] bibledit: Some sources are not included in your package Added tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017964: [Pkg-rust-maintainers] Bug#1017964: rust-pleaser FTBFS/autopkgtest failure with nix 0.25
On 2022-08-23 02:12+0100, Peter Green wrote: > The API of gethostname has changed. Now instead of taking a buffer > from the caller it retuns a Result > > Adjusting the code was easy enough, but I notice that the buffer size > used by the new version of gethostname is about 4 times larger than > the one used previously in pleaser. I have not investigated whether > this increase in potential string length has any security implications > for pleaser. > > Patch at > > https://salsa.debian.org/rust-team/debcargo-conf/-/blob/master/src/pleaser/debian/patches/nix-0.25.patch I don't see any issues from it, and thanks for keeping me in the loop. The patch looks good, thanks again and I'll merge it before the next upstream bump. Ed
Bug#1016625: bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'
On Tue, Aug 23, 2022 at 07:00:44PM +0200, Martin Uecker wrote: > > I think I fixed this. At least it compiles locally in > a sid pbuilder environment, but I needed to build-depend > on gcc-10. gcc-10 will be removed from the archive some day, so this cannot be a permanent fix. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1017278: marked as pending in libnet-sip-perl
Control: tag -1 pending Hello, Bug #1017278 in libnet-sip-perl 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/perl-team/modules/packages/libnet-sip-perl/-/commit/e50d5dc8a24639a3312e68d0323a2d28a9d3f079 Skip fragile test t/24_dtmf_audio.t during build and autopkgtests. Closes: #1017278 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017278
Processed: Bug#1017278 marked as pending in libnet-sip-perl
Processing control commands: > tag -1 pending Bug #1017278 [src:libnet-sip-perl] libnet-sip-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 1017278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016738: marked as done (dt-schema: autopkgtest failure: No module named 'libfdt')
Your message dated Tue, 23 Aug 2022 20:08:32 +0200 with message-id <63adf937-87f0-4a8b-e8d6-3fc8b0d08...@debian.org> and subject line Re: dt-schema: autopkgtest failure: No module named 'libfdt' has caused the Debian Bug report #1016738, regarding dt-schema: autopkgtest failure: No module named 'libfdt' 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.) -- 1016738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dt-schema Version: 2022.07-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package dt-schema, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. It seems you are missing a dependency. 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=dt-schema https://ci.debian.net/data/autopkgtest/testing/amd64/d/dt-schema/24372986/log.gz === python3.10 === Traceback (most recent call last): File "/tmp/autopkgtest-lxc.ard1nynt/downtmp/autopkgtest_tmp/test/test-dt-validate.py", line 20, in import dtschema File "/usr/lib/python3/dist-packages/dtschema/__init__.py", line 1, in from dtschema.lib import ( File "/usr/lib/python3/dist-packages/dtschema/lib.py", line 18, in import dtschema.dtb File "/usr/lib/python3/dist-packages/dtschema/dtb.py", line 9, in import libfdt ModuleNotFoundError: No module named 'libfdt' autopkgtest [08:11:46]: test unittests OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 2022.08.2-1--- End Message ---
Bug#1017990: src:pytango: fails to migrate to testing for too long: FTBFS on s390x
Source: pytango Version: 9.3.3-1 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:pytango has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build on s390x while it built there successfully in the past and you have two unresolved RC bugs. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=pytango OpenPGP_signature Description: OpenPGP digital signature
Processed: src:jellyfish: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 2.3.0-14
Bug #1017989 [src:jellyfish] src:jellyfish: fails to migrate to testing for too
long: unresolved RC bug
Marked as fixed in versions jellyfish/2.3.0-14.
Bug #1017989 [src:jellyfish] src:jellyfish: fails to migrate to testing for too
long: unresolved RC bug
Marked Bug as done
> block -1 by 1017261
Bug #1017989 {Done: Paul Gevers } [src:jellyfish]
src:jellyfish: fails to migrate to testing for too long: unresolved RC bug
1017989 was not blocked by any bugs.
1017989 was not blocking any bugs.
Added blocking bug(s) of 1017989: 1017261
--
1017989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017989: src:jellyfish: fails to migrate to testing for too long: unresolved RC bug
Source: jellyfish Version: 2.3.0-13 Severity: serious Control: close -1 2.3.0-14 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1017261 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:jellyfish has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Although your package built on all official architectures by now, it's reported to FTBFS in bug #1017261 and also reproducible-builds.org shows your package FTBFS in both unstable and bookworm. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=jellyfish OpenPGP_signature Description: OpenPGP digital signature
Bug#1015218: marked as done (consul: CVE-2021-37219 CVE-2021-38698)
Your message dated Tue, 23 Aug 2022 17:35:16 + with message-id and subject line Bug#1015218: fixed in consul 1.8.7+dfsg1-6 has caused the Debian Bug report #1015218, regarding consul: CVE-2021-37219 CVE-2021-38698 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.) -- 1015218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: consul X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for consul. CVE-2021-37219[0]: | HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows | non-server agents with a valid certificate signed by the same CA to | access server-only functionality, enabling privilege escalation. Fixed | in 1.8.15, 1.9.9 and 1.10.2. https://discuss.hashicorp.com/t/hcsec-2021-22-consul-raft-rpc-privilege-escalation/29024 CVE-2021-38698[1]: | HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint | allowed services to register proxies for other services, enabling | access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2. https://discuss.hashicorp.com/t/hcsec-2021-24-consul-missing-authorization-check-on-txn-apply-endpoint/29026 https://github.com/hashicorp/consul/commit/747844bad6410091f2c6e961216c0c5fc285a44d (v1.8.15) CVE-2022-29153[2]: | HashiCorp Consul and Consul Enterprise through 2022-04-12 allow SSRF. https://discuss.hashicorp.com/t/hcsec-2022-10-consul-s-http-health-check-may-allow-server-side-request-forgery/38393 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-37219 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37219 [1] https://security-tracker.debian.org/tracker/CVE-2021-38698 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38698 [2] https://security-tracker.debian.org/tracker/CVE-2022-29153 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29153 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: consul Source-Version: 1.8.7+dfsg1-6 Done: Martina Ferrari We believe that the bug you reported is fixed in the latest version of consul, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martina Ferrari (supplier of updated consul package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 23 Aug 2022 13:00:04 -0300 Source: consul Architecture: source Version: 1.8.7+dfsg1-6 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Martina Ferrari Closes: 1015218 Changes: consul (1.8.7+dfsg1-6) unstable; urgency=medium . [ vimerbf ] * Fix upstream url in uscan watch file. . [ Reinhard Tartler ] * Backport security patches - CVE-2021-37219 - CVE-2021-38698. Closes: #1015218 Checksums-Sha1: 3ecc395914407879583e23d7a0ff7368086b0655 5213 consul_1.8.7+dfsg1-6.dsc 1a7f5817d3d1ba203442435ab49b5101c0682c27 26352 consul_1.8.7+dfsg1-6.debian.tar.xz b9e9ff1033d336948e0bfeb901bab2e12bcdedd5 15360 consul_1.8.7+dfsg1-6_amd64.buildinfo Checksums-Sha256: 7986dfd42e747e882787ef22cd078ab6c18854b7e97b26f33c91ac5b18f6c067 5213 consul_1.8.7+dfsg1-6.dsc 2748cad2725dc54f6462bb6b2cc22bde6246f65cc2d4c3064723e2f901123ae0 26352 consul_1.8.7+dfsg1-6.debian.tar.xz e0a6aae1572d65eb4feb3ac24d09c6d61f6d48caf9dc60cf62b0be1dac3d4c80 15360 consul_1.8.7+dfsg1-6_amd64.buildinfo Files: f0346fd12a9b6cfd422e8b7122d82ff0 5213 admin optional consul_1.8.7+dfsg1-6.dsc 5477f0a11584a577607363028bad8046 26352 admin optional consul_1.8.7+dfsg1-6.debian.tar.xz 63eb47ecff2c81409434625e7f0ddb0d 15360 admin optional consul_1.8.7+dfsg1-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE2qbv8cYn6hwmsaaSqiMPxF+MJ7EFAmMFCn4ACgkQqiMPxF+M J7E1LxAAn1WweG2vt6kG9RAk5oasDZ/4yFia7FrYESsNXleAtndpnremFuzWnAJ3 s7k8slrJOjaW60b4oYrP9UkdMrSbcf0t5gUOdZ359Cum4dM3uq27wKgnDx/FqsIs 95lM9Cq2tp
Processed: Re: Forwarded to https://github.com/bibledit/cloud/issues/821
Processing commands for cont...@bugs.debian.org: > notforwarded 1017083 Bug #1017083 [src:bibledit] bibledit: Some sources are not included in your package Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 1017083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017083: All sources are included, the bug report is invalid
Hello, Thank you for looking into and reporting this issue. The bug lists a couple of minified Javascript code that is included in the package, and the bug report asserts that the original source, the non-minified source, is not included in the source package. I have checked all of the reported minified sources to find out whether the source is reported correctly in the bug report, or whether the original source is already included in the source code of the package. Here is a list of all the reported files in the bug report, together with my remarks on them. [jquery/jquery-3.5.1.min.js] The source is already included in this file: jquery/jquery-3.5.1.js [jquery/jquery.touchSwipe.min.js] The source is already included in this file: jquery/jquery.touchSwipe.js [nicedit/nicedit.min.js] The source is already included in this file: nicedit/nicedit.js [notifit/notifit.min.js] The source is already included in this file: notifit/notifit.js [quill/1.1.5/quill.core.js] The above is full source, not minified. [quill/1.1.5/quill.js] The above is full source, not minified. [quill/1.1.5/quill.min.js] The source is already included in this file: quill/1.1.5/quill.js [quill/1.3.6/quill.core.js] The above is full source, not minified. [quill/1.3.6/quill.js] The above is full source, not minified. [quill/1.3.6/quill.min.js] The source is already included in this file: quill/1.3.6/quill.js [quill/quill.core.js] The above is full source, not minified. [quill/quill.js] The above is full source, not minified. [quill/quill.min.js] The source is already included in this file: quill/quill.js [rangy13/rangy-classapplier.min.js] The source is already included in this file: rangy13/rangy-classapplier.js [rangy13/rangy-core.min.js] The source is already included in this file: rangy13/rangy-core.js [rangy13/rangy-highlighter.min.js] The source is already included in this file: rangy13/rangy-highlighter.js [rangy13/rangy-selectionsaverestore.min.js] The source is already included in this file: rangy13/rangy-selectionsaverestore.js [rangy13/rangy-serializer.min.js] The source is already included in this file: rangy13/rangy-serializer.js [rangy13/rangy-textrange.min.js] The source is already included in this file: rangy13/rangy-textrange.js Therefore my current impression is that all the items reported in this bug were reported in error, and that the bug report seems to be invalid. Please correct me if I'm wrong. If the bug report is invalid, could it be closed? The bug report, if it remains open, will cause the package to be removed from the testing distribution. Something I'd like not to happen, in particular as there seems to be no reason for that. Met vriendelijke groeten, With kind regards, Teus Benschop https://freesoftwareconsultants.nl https://bibledit.org
Bug#1016625: bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'
I think I fixed this. At least it compiles locally in a sid pbuilder environment, but I needed to build-depend on gcc-10. Martin Am Sonntag, den 07.08.2022, 13:06 +0530 schrieb Nilesh Patra: > Hi Martin, > > [CC'ing both your email addresses since I don't know which one you use] > > Since this is your package, could you consider taking a look please? > > On Thu, 04 Aug 2022 04:31:30 +0200 Andreas Beckmann wrote: > > Source: bart-cuda > > Version: 0.7.00-5 > > Severity: serious > > Tags: ftbfs > > Justification: fails to build from source > > > > Hi, > > > > bart-cuda recently started to FTBFS in sid, while it still succeeds in > > testing. > > > > /usr//bin/nvcc -DUSE_CUDA -Xcompiler -fPIC -Xcompiler -fopenmp -O3 > > -I/build/bart-cuda- > > 0.7.00/src/ -m64 -ccbin gcc -c > > /build/bart-cuda-0.7.00/src/wavelet/wl3-cuda.cu -o /build/bart- > > cuda-0.7.00/src/wavelet/wl3-cuda.o > > /usr/include/c++/10/type_traits:71:52: error: redefinition of 'constexpr > > const _Tp > > std::integral_constant<_Tp, __v>::value' > >71 | template > > |^ > > > > /usr/include/c++/10/type_traits:59:29: note: 'constexpr const _Tp value' > > previously declared > > here > >59 | static constexpr _Tp value = __v; > > | ^ > > make[2]: *** [Makefile:332: /build/bart-cuda-0.7.00/src/wavelet/wl3-cuda.o] > > Error 1 > > > > Andreas
Processed: Re: libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load
Processing control commands:
> reopen -1
Bug #1017356 {Done: Alastair McKinstry } [libpmix2]
libpmix2: symbol lookup error:
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined
symbol: pmix_value_load
'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 pmix/4.2.0-2.
> found 1017356 pmix/4.2.0-2
Bug #1017356 [libpmix2] libpmix2: symbol lookup error:
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined
symbol: pmix_value_load
Marked as found in versions pmix/4.2.0-2.
--
1017356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017840: debian-security-support: cannot create /var/lib/debian-security-support/security-support.semaphore: Permission
On Tue, Aug 23, 2022 at 05:41:22PM +0200, Christoph Anton Mitterer wrote: > It also seems as if neither that director or its files nor the created > user is ever cleaned up on purge, but left behind as cruft forever. users must not be cleaned up (=removed) on package removal, so the only thing purge should do is remove /var/lib/debian-security-support/ -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ figures don't lie, but liars figure. signature.asc Description: PGP signature
Bug#1017356: libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load
Source: pmix Followup-For: Bug #1017356 Control: reopen -1 Control: found 1017356 pmix/4.2.0-2 Adrian's last comments still apply all the same. The problem is still there. (tests of version 4.2.0-1 in experimental get run in unstable, see https://ci.debian.net/packages/m/mpi4py/unstable/amd64/ )
Bug#1017840: debian-security-support: cannot create /var/lib/debian-security-support/security-support.semaphore: Permission
Hey Holger. It also seems as if neither that director or its files nor the created user is ever cleaned up on purge, but left behind as cruft forever. Or did I oversee something in the posrm? Thanks, Chris.
Processed: forcibly merging 1017326 1017160
Processing commands for cont...@bugs.debian.org:
> forcemerge 1017326 1017160
Bug #1017326 {Done: Reiner Herrmann } [src:nethack]
nethack: FTBFS: cdefs.h:393:73: error: macro "__has_attribute" requires an
identifier
Bug #1017160 [src:nethack] nethack: FTBFS: cdefs.h:393:73: error: macro
"__has_attribute" requires an identifier
Marked Bug as done
Marked as fixed in versions nethack/3.6.6-3.
Marked as found in versions nethack/3.6.6-2.
Merged 1017160 1017326
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1017160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017160
1017326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017291: marked as done (mtail: FTBFS: tests failed)
Your message dated Tue, 23 Aug 2022 15:19:47 + with message-id and subject line Bug#1017291: fixed in mtail 3.0.0~rc50-1 has caused the Debian Bug report #1017291, regarding mtail: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mtail Version: 3.0.0~rc49-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- -timeout 100s > cd build && go test -vet=off -v -p 8 -timeout 100s > github.com/google/mtail/cmd/mfmt github.com/google/mtail/cmd/mtail > github.com/google/mtail/internal/exporter > github.com/google/mtail/internal/logline > github.com/google/mtail/internal/metrics > github.com/google/mtail/internal/metrics/datum > github.com/google/mtail/internal/mtail > github.com/google/mtail/internal/mtail/golden > github.com/google/mtail/internal/runtime > github.com/google/mtail/internal/runtime/code > github.com/google/mtail/internal/runtime/compiler > github.com/google/mtail/internal/runtime/compiler/ast > github.com/google/mtail/internal/runtime/compiler/checker > github.com/google/mtail/internal/runtime/compiler/codegen > github.com/google/mtail/internal/runtime/compiler/errors > github.com/google/mtail/internal/runtime/compiler/opt > github.com/google/mtail/internal/runtime/compiler/parser > github.com/google/mtail/internal/runtime/compiler/position > github.com/google/mtail/internal/runtime/compiler/symbol > github.com/google/mtail/internal/runtime/compiler/types > github.com/google/mtail/internal/runtime/vm > github.com/google/mtail/internal/tailer > github.com/google/mtail/internal/tailer/logstream > github.com/google/mtail/internal/testutil > github.com/google/mtail/internal/waker > ? github.com/google/mtail/cmd/mfmt[no test files] > ? github.com/google/mtail/cmd/mtail [no test files] > === RUN TestCreateExporter > --- PASS: TestCreateExporter (0.00s) > === RUN TestMetricToCollectd > --- PASS: TestMetricToCollectd (0.00s) > === RUN TestMetricToGraphite > --- PASS: TestMetricToGraphite (0.00s) > === RUN TestMetricToStatsd > --- PASS: TestMetricToStatsd (0.00s) > === RUN TestHandleGraphite > === RUN TestHandleGraphite/empty > === RUN TestHandleGraphite/single > --- PASS: TestHandleGraphite (0.00s) > --- PASS: TestHandleGraphite/empty (0.00s) > --- PASS: TestHandleGraphite/single (0.00s) > === RUN TestHandleJSON > === RUN TestHandleJSON/empty > === RUN TestHandleJSON/single > === RUN TestHandleJSON/dimensioned > === RUN TestHandleJSON/histogram > --- PASS: TestHandleJSON (0.00s) > --- PASS: TestHandleJSON/empty (0.00s) > --- PASS: TestHandleJSON/single (0.00s) > --- PASS: TestHandleJSON/dimensioned (0.00s) > --- PASS: TestHandleJSON/histogram (0.00s) > === RUN TestHandlePrometheus > === RUN TestHandlePrometheus/empty > === RUN TestHandlePrometheus/single > === RUN TestHandlePrometheus/with_prog_label > === RUN TestHandlePrometheus/dimensioned > === RUN TestHandlePrometheus/gauge > === RUN TestHandlePrometheus/timer > === RUN TestHandlePrometheus/text > === RUN TestHandlePrometheus/quotes > === RUN TestHandlePrometheus/help > === RUN TestHandlePrometheus/2_help_with_label > === RUN TestHandlePrometheus/histo > === RUN TestHandlePrometheus/histo-count-eq-inf > --- PASS: TestHandlePrometheus (0.00s) > --- PASS: TestHandlePrometheus/empty (0.00s) > --- PASS: TestHandlePrometheus/single (0.00s) > --- PASS: TestHandlePrometheus/with_prog_label (0.00s) > --- PASS: TestHandlePrometheus/dimensioned (0.00s) > --- PASS: TestHandlePrometheus/gauge (0.00s) > --- PASS: TestHandlePrometheus/timer (0.00s) > --- PASS: TestHandlePrometheus/text (0.00s) > --- PASS: TestHandlePrometheus/quotes (0.00s) > --- PASS: TestHandlePrometheus/help (0.00s) > --- PASS: TestHandlePrometheus/2_help_with_label (0.00s) > --- PASS: TestHandlePrometheus/histo (0.00s) > --- PASS: TestHandlePrometheus/histo-count-eq-inf (0.00s) > === RUN TestWritePrometheus > === RUN TestWritePrometheus/empty > === RUN TestWritePrometheus/single > === RUN TestWritePrometheus/multi > --- PASS: TestWritePrometheus (0.00s) > --- PASS: TestWritePrometheus/empty (0.00s) > ---
Bug#1017356: marked as done (libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load)
Your message dated Tue, 23 Aug 2022 15:07:43 + with message-id and subject line Bug#1017356: fixed in pmix 4.2.0-2 has caused the Debian Bug report #1017356, regarding libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load 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.) -- 1017356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpmix2 Version: 4.2.0~rc1-2 Severity: grave Justification: renders package unusable Starting with version 4.2.0~rc1-1, the mca_pmix_ext3x.so library lost the pmix_value_load symbols. This causes issues on depending packages: https://buildd.debian.org/status/fetch.php?pkg=dolfin&arch=amd64&ver=2019.2.0%7Egit20220407.d29e24d-5%2Bnmu1&stamp=1660479825&raw=0 https://ci.debian.net/data/autopkgtest/testing/amd64/m/mpi4py/24786981/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/o/openmpi/24786982/log.gz --- End Message --- --- Begin Message --- Source: pmix Source-Version: 4.2.0-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of pmix, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated pmix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 23 Aug 2022 15:03:08 +0100 Source: pmix Architecture: source Version: 4.2.0-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1017356 1017734 Changes: pmix (4.2.0-2) unstable; urgency=medium . * Ack old bugs. Closes: #1017356, #1017734 Checksums-Sha1: 09491c099a72d6d0f69d7789a21006cf08d890b1 2310 pmix_4.2.0-2.dsc eb8937b5f6220fd67f894e4f95d624ed632a2fb1 10548 pmix_4.2.0-2.debian.tar.xz Checksums-Sha256: 9dfdf97a0087c4e978cd6031cfe1f8c0a4137ac834a699a9d0bd49350049 2310 pmix_4.2.0-2.dsc 0f02d7a05dc6b6aa44ccb080afbcbab8c69958eaf6eb8672f26243a7615b44f3 10548 pmix_4.2.0-2.debian.tar.xz Files: 6e13b39dae869051d250208831d7f35b 2310 net optional pmix_4.2.0-2.dsc 1a15174c29693c4f5c5dee0acc87d26d 10548 net optional pmix_4.2.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmME5HcACgkQy+a7Tl2a 06W5xQ//Q6xDadd57Vc71b2OWhTqJxeebOieJ8oP5Vm88JV8P9GdnzFSfL7gb80h 25PeJzlZI/pFfHPyjtAkcmIDTzfuRDmCkQgicEZ/U/xcw7mZx4kIpw/ProazFINs r+XprmO6mBipvoxNBELWuCtirsePA28XS4d8q8OeZtFGjtu3ClkQf0mPY8v5peO9 IttTq499/j9vvkSWhKs0eX2P7DZdmElLopaYssvixrKCcwXHHRoV0PwP1k2U9Hoe Y4Gq0NF8qa3HJXlUKlCA2n4xu4nGkzWcHZURRXW0AFjT2x9XJSzA5132POv9q/FY Od+o4WT5ESL41yJN/HAjIIPdxCAesqMBE3C2xETn49ICVHRChW93ljhhzIgU6tK4 pnyzRxSRpZ9YoK4HZym0K52HppY/nEy/13cIh7qrY5FqAbTKZwhNZJ5ewMJUnKTq MngWLJNOrS94JcwLmWByVy6EOmOHo24oxFhHe6YwLqM8VQ1aiyVVINclMHqEzRIo jTG2xDGy4Fhg531TD/0d/Z7O2R/OtAiO7zBSVDuhqjUUeP986zyJaFilKxLqOhxB FBjMZBQAPf+qfJ2SmigVrtc8ml5087AvODfSRjurTWpXumcM9GAB0ZlfzX03ePBk H1wunaWovwgHz8Dbc/5FQ0GKHoBpiIFLGEJ7El8sBni2RY1YjAc= =Myjv -END PGP SIGNATURE End Message ---
Bug#1013939: marked as done (python-xarray: autopkgtest regression: Left and right DataArray objects are not close)
Your message dated Tue, 23 Aug 2022 15:07:55 +
with message-id
and subject line Bug#1013939: fixed in python-xarray 2022.06.0-4
has caused the Debian Bug report #1013939,
regarding python-xarray: autopkgtest regression: Left and right DataArray
objects are not close
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.)
--
1013939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 2022.06.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-xarray the autopkgtest of python-xarray
fails in testing when that autopkgtest is run with the binary packages
of python-xarray from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python-xarray from testing2022.06.0~rc1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-xarray
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/23134419/log.gz
=== FAILURES
===
___ test_weighted_operations_nonequal_coords
___
def test_weighted_operations_nonequal_coords():
# There are no weights for a == 4, so that data point is ignored.
weights = DataArray(np.random.randn(4), dims=("a",),
coords=dict(a=[0, 1, 2, 3]))
data = DataArray(np.random.randn(4), dims=("a",),
coords=dict(a=[1, 2, 3, 4]))
check_weighted_operations(data, weights, dim="a", skipna=None)
q = 0.5
result = data.weighted(weights).quantile(q, dim="a")
# Expected value computed using code from
https://aakinshin.net/posts/weighted-quantiles/ with values at a=1,2,3
expected = DataArray([0.9308707], coords={"quantile":
[q]}).squeeze()
assert_allclose(result, expected)
E AssertionError: Left and right DataArray objects are not close
E E Differing values:
E L
E array(-0.289754)
E R
E array(0.930871)
/usr/lib/python3/dist-packages/xarray/tests/test_weighted.py:667:
AssertionError
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-xarray
Source-Version: 2022.06.0-4
Done: Alastair McKinstry
We believe that the bug you reported is fixed in the latest version of
python-xarray, 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 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry (supplier of updated python-xarray
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 23 Aug 2022 15:10:22 +0100
Source: python-xarray
Architecture: source
Version: 2022.06.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Alastair McKinstry
Closes: 955015 1013939
Changes:
python-xarray (2022.06.0-4) unstable; urgency=medium
.
* Ack closed bug. Closes: #955015
* Ignore (xfail) on test that fails depending on random seed.
Closes: #1013939
Checksums-Sha1:
dc3be1b3982a588e0c362e3b57c993db86fa82b5 3358 python-xarray_2022.06.0-4.dsc
5c28bd16a4effd8222453bef66522e5c35f6fc45 14100
python-xarray_2022.06.0-4.debian.tar.xz
Checksums-Sha256:
bfc6c3d14b2b1acb401187aaf21a79099b3ddad5ec5f9a3e3d3dfa2a6ff68ec9 3358
python-xarray_2022.06.0-4.dsc
457912c06cd29eba9dad7824b5d6e283fa518d56301c7f2cff3937dce317b26e 14100
python-xarray_2022.06.0-4.debian.tar.xz
Files:
5f5f78f18e0626b5afc30f1bb15900e9 3358 python optional
python-xarray_2022.06.0-4.dsc
8f7998bdc82b9ff4126f9f9d7651b456 14100 python optional
python-xarra
Bug#1017291: marked as pending in mtail
Control: tag -1 pending Hello, Bug #1017291 in mtail reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/mtail/-/commit/41545649a1b835853ef09e1e7aed7a851c73c1a5 Add patch to fix build errors in go 1.18. Closes: #1017291 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017291
Processed: Bug#1017291 marked as pending in mtail
Processing control commands: > tag -1 pending Bug #1017291 [src:mtail] mtail: FTBFS: tests failed Added tag(s) pending. -- 1017291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004508: marked as done (ocrad: autopkgtest regression: undefined reference to `png_g*)
Your message dated Tue, 23 Aug 2022 14:40:42 + with message-id and subject line Bug#1004508: fixed in ocrad 0.28-3 has caused the Debian Bug report #1004508, regarding ocrad: autopkgtest regression: undefined reference to `png_g* 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.) -- 1004508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocrad Version: 0.28-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 ocrad the autopkgtest of ocrad fails in testing when that autopkgtest is run with the binary packages of ocrad from unstable. It passes when run with only packages from testing. In tabular form: passfail ocrad from testing0.28-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Looks like a missing test dependency to me. 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=ocrad https://ci.debian.net/data/autopkgtest/testing/amd64/o/ocrad/18793280/log.gz /usr/bin/ld: /tmp/ccFSvSEW.o: in function `main': /tmp/autopkgtest-lxc.gm2jjp8j/downtmp/build.Wry/src/ocradcheck.cc:85: undefined reference to `Arg_parser::Arg_parser(int, char const* const*, Arg_parser::Option const*, bool)' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libocrad.a(png_io.o): in function `read_check_png_sig8(_IO_FILE*, int)': (.text+0x7b): undefined reference to `png_sig_cmp' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libocrad.a(png_io.o): in function `Page_image::write_png(_IO_FILE*, unsigned int) const': (.text+0x1f3): undefined reference to `png_create_write_struct' /usr/bin/ld: (.text+0x209): undefined reference to `png_create_info_struct' /usr/bin/ld: (.text+0x22d): undefined reference to `png_set_longjmp_fn' /usr/bin/ld: (.text+0x24f): undefined reference to `png_destroy_write_struct' /usr/bin/ld: (.text+0x30b): undefined reference to `png_init_io' /usr/bin/ld: (.text+0x35b): undefined reference to `png_set_IHDR' /usr/bin/ld: (.text+0x376): undefined reference to `png_set_rows' /usr/bin/ld: (.text+0x38c): undefined reference to `png_write_png' /usr/bin/ld: (.text+0x39b): undefined reference to `png_destroy_write_struct' /usr/bin/ld: (.text+0x448): undefined reference to `png_destroy_write_struct' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libocrad.a(png_io.o): in function `show_png_info(_IO_FILE*, char const*, int)': (.text+0x4b6): undefined reference to `png_create_read_struct' /usr/bin/ld: (.text+0x4cc): undefined reference to `png_create_info_struct' /usr/bin/ld: (.text+0x4f0): undefined reference to `png_set_longjmp_fn' /usr/bin/ld: (.text+0x50e): undefined reference to `png_init_io' /usr/bin/ld: (.text+0x51c): undefined reference to `png_set_sig_bytes' /usr/bin/ld: (.text+0x52b): undefined reference to `png_read_info' /usr/bin/ld: (.text+0x53a): undefined reference to `png_get_image_height' /usr/bin/ld: (.text+0x54c): undefined reference to `png_get_image_width' /usr/bin/ld: (.text+0x565): undefined reference to `png_get_bit_depth' /usr/bin/ld: (.text+0x577): undefined reference to `png_get_color_type' /usr/bin/ld: (.text+0x589): undefined reference to `png_get_channels' /usr/bin/ld: (.text+0x59c): undefined reference to `png_get_interlace_type' /usr/bin/ld: (.text+0x630): undefined reference to `png_destroy_read_struct' /usr/bin/ld: (.text+0x6c6): undefined reference to `png_destroy_read_struct' /usr/bin/ld: (.text+0x6f9): undefined reference to `png_destroy_read_struct' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libocrad.a(png_io.o): in function `Page_image::read_png(_IO_FILE*, int, bool)': (.text+0x774): undefined reference to `png_create_read_struct' /usr/bin/ld: (.text+0x78d): undefined reference to `png_create_info_struct' /usr/bin/ld: (.text+0x7b7): undefined reference to `png_set_longjmp_fn' /usr/bin/ld: (.text+0x7e3): undefined reference to `png_init_io' /usr/bin/ld: (.text+0x7f4): undefined reference to `png_set_sig_bytes' /usr/bin/ld: (.text+0x810): undefined reference to `png_read_png' /usr/bin/ld:
Processed: falselogin: diff for NMU version 0.3-4.1
Processing control commands: > tags 965514 + patch pending Bug #965514 [src:falselogin] falselogin: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending and patch. > tags 999289 + patch pending Bug #999289 [src:falselogin] falselogin: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch and pending. -- 965514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965514 999289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: falselogin: diff for NMU version 0.3-4.1
Processing control commands: > tags 965514 + patch pending Bug #965514 [src:falselogin] falselogin: Removal of obsolete debhelper compat 5 and 6 in bookworm Ignoring request to alter tags of bug #965514 to the same tags previously set > tags 999289 + patch pending Bug #999289 [src:falselogin] falselogin: missing required debian/rules targets build-arch and/or build-indep Ignoring request to alter tags of bug #999289 to the same tags previously set -- 965514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965514 999289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016831: closed by Steven Robbins (Re: libminc: FTBFS on mipsel, mips64el)
On 2022-08-22 11:21:19 -0500, Steven Robbins wrote: > On Mon, 22 Aug 2022 09:24:41 +0200 Sebastian Ramacher > wrote: > > > > > I can't reproduce this. The main difference between the one that built > > > and > the > > > one that didn't is the new libc, so that's the most likely culprit. > > > > The 4th attempt on the buildds filed again: > > https://buildd.debian.org/status/ > fetch.php?pkg=libminc&arch=mips64el&ver=2.4.03-5+b1&stamp=1661136219&raw=0 > > > > Reopening. Please only close this bug when libminc is able to build on > > the buildds again. > > I can't debug this! It builds OK in both the mipsel and mips64el chroots on > porterbox eller. See https://lists.debian.org/debian-devel/2022/08/ > msg00200.html > > Is there something broken on the buildd? Maybe the mips porters have a better idea. You could try contacting them at debian-m...@lists.debian.org. If that also doesn't lead to a solution for this issue, we will have to get libmimc's binaries for mips64el removed. Cheers -- Sebastian Ramacher
Processed: Splitting bug report
Processing commands for cont...@bugs.debian.org: > clone 1015218 -2 Bug #1015218 [src:consul] consul: CVE-2021-37219 CVE-2021-38698 CVE-2022-29153 Bug 1015218 cloned as bug 1017982 > retitle 1015218 consul: CVE-2021-37219 CVE-2021-38698 Bug #1015218 [src:consul] consul: CVE-2021-37219 CVE-2021-38698 CVE-2022-29153 Changed Bug title to 'consul: CVE-2021-37219 CVE-2021-38698' from 'consul: CVE-2021-37219 CVE-2021-38698 CVE-2022-29153'. > retitle -2 consul: CVE-2022-29153 Bug #1017982 [src:consul] consul: CVE-2021-37219 CVE-2021-38698 CVE-2022-29153 Changed Bug title to 'consul: CVE-2022-29153' from 'consul: CVE-2021-37219 CVE-2021-38698 CVE-2022-29153'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015218 1017982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015218: Splitting bug report
clone 1015218 -2 retitle 1015218 consul: CVE-2021-37219 CVE-2021-38698 retitle -2 consul: CVE-2022-29153 thanks I am splitting this bug in two, as the fixes for these CVEs are in different release trees (1.8 vs 1.9) -- Martina Ferrari (Tina)
Bug#1017277: marked as done (golang-github-thedevsaddam-gojsonq: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/thedevsaddam/gojsonq returned exit code 1)
Your message dated Tue, 23 Aug 2022 13:49:05 + with message-id and subject line Bug#1017277: fixed in golang-github-thedevsaddam-gojsonq 2.5.2-3 has caused the Debian Bug report #1017277, regarding golang-github-thedevsaddam-gojsonq: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/thedevsaddam/gojsonq 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.) -- 1017277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-thedevsaddam-gojsonq Version: 2.5.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 8 > github.com/thedevsaddam/gojsonq > internal/goos > internal/goarch > internal/goexperiment > internal/unsafeheader > internal/race > internal/cpu > runtime/internal/atomic > runtime/internal/syscall > sync/atomic > internal/abi > runtime/internal/math > runtime/internal/sys > unicode > unicode/utf8 > encoding > math/bits > internal/itoa > unicode/utf16 > internal/bytealg > math > runtime > internal/reflectlite > sync > internal/testlog > errors > sort > io > internal/oserror > path > strconv > syscall > strings > bytes > reflect > internal/syscall/execenv > time > internal/syscall/unix > io/fs > internal/poll > encoding/binary > internal/fmtsort > os > encoding/base64 > io/ioutil > fmt > encoding/json > github.com/thedevsaddam/gojsonq >dh_auto_test -O--builddirectory=_build -O--buildsystem=golang > cd _build && go test -vet=off -v -p 8 github.com/thedevsaddam/gojsonq > === RUN Test_DefaultDecoder > --- PASS: Test_DefaultDecoder (0.00s) > === RUN Test_abs > --- PASS: Test_abs (0.00s) > === RUN Test_isIndex > --- PASS: Test_isIndex (0.00s) > === RUN Test_getIndex > --- PASS: Test_getIndex (0.00s) > === RUN Test_toString > --- PASS: Test_toString (0.00s) > === RUN Test_toFloat64 > --- PASS: Test_toFloat64 (0.00s) > === RUN Test_sorter > --- PASS: Test_sorter (0.00s) > === RUN Test_sortMap > --- PASS: Test_sortMap (0.00s) > === RUN Test_getNestedValue > --- PASS: Test_getNestedValue (0.00s) > === RUN Test_makeAlias > --- PASS: Test_makeAlias (0.00s) > === RUN Test_length > --- PASS: Test_length (0.00s) > === RUN TestNew > --- PASS: TestNew (0.00s) > === RUN TestJSONQ_String > --- PASS: TestJSONQ_String (0.00s) > === RUN TestJSONQ_decode > --- PASS: TestJSONQ_decode (0.00s) > === RUN TestJSONQ_Copy > --- PASS: TestJSONQ_Copy (0.00s) > === RUN TestJSONQ_File > --- PASS: TestJSONQ_File (0.00s) > === RUN TestJSONQ_JSONString > --- PASS: TestJSONQ_JSONString (0.00s) > === RUN TestJSONQ_FromString > --- PASS: TestJSONQ_FromString (0.00s) > === RUN TestJSONQ_Reader > --- PASS: TestJSONQ_Reader (0.00s) > === RUN TestJSONQ_Reader_expecting_error > --- PASS: TestJSONQ_Reader_expecting_error (0.00s) > === RUN TestJSONQ_Errors > --- PASS: TestJSONQ_Errors (0.00s) > === RUN TestJSONQ_Macro > --- PASS: TestJSONQ_Macro (0.00s) > === RUN TestJSONQ_From_Set > --- PASS: TestJSONQ_From_Set (0.00s) > === RUN TestJSONQ_Select > --- PASS: TestJSONQ_Select (0.00s) > === RUN TestJSONQ_Offset > --- PASS: TestJSONQ_Offset (0.00s) > === RUN TestJSONQ_Limit > --- PASS: TestJSONQ_Limit (0.00s) > === RUN TestJSONQ_reset > --- PASS: TestJSONQ_reset (0.00s) > === RUN TestJSONQ_Reset > --- PASS: TestJSONQ_Reset (0.00s) > === RUN TestJSONQ_From > --- PASS: TestJSONQ_From (0.00s) > === RUN TestJSONQ_FromInterface > --- PASS: TestJSONQ_FromInterface (0.00s) > === RUN TestJSONQ_Where_single_where > --- PASS: TestJSONQ_Where_single_where (0.00s) > === RUN TestJSONQ_Where_deep_nested_value > --- PASS: TestJSONQ_Where_deep_nested_value (0.00s) > === RUN TestJSONQ_Where_multiple_where_expecting_result > --- PASS: TestJSONQ_Where_multiple_where_expecting_result (0.00s) > === RUN TestJSONQ_Where_multiple_where_expecting_empty_result > --- PASS: TestJSONQ_Where_multiple_where_expecting_empty_result (0.00s) > === RUN T
Bug#1017952: groupadd: invalid group ID '-1' when adding with --uid
Marc Haber, le mar. 23 août 2022 15:02:04 +0200, a ecrit: > thanks for spotting this. It was both a bug in the code and a big > omission in our test suite. Both aspects are fixed now. > > On Mon, Aug 22, 2022 at 10:11:24PM +0200, Samuel Thibault wrote: > > Package: adduser > > Version: 3.124 > > Severity: serious > > Justification: Makes creating chroots fail > > Do have the time to check the code from > https://salsa.debian.org/debian/adduser/-/tree/debian-bug-1017952 ? I tried it in my test case and it seems to work, thanks! Samuel
Processed: Bug#1017277 marked as pending in golang-github-thedevsaddam-gojsonq
Processing control commands: > tag -1 pending Bug #1017277 [src:golang-github-thedevsaddam-gojsonq] golang-github-thedevsaddam-gojsonq: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/thedevsaddam/gojsonq returned exit code 1 Added tag(s) pending. -- 1017277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017277: marked as pending in golang-github-thedevsaddam-gojsonq
Control: tag -1 pending Hello, Bug #1017277 in golang-github-thedevsaddam-gojsonq reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-thedevsaddam-gojsonq/-/commit/6be953f0a793477e98a473b755cbecb7a994ed7e Use stable sorting for maps and adjust test. Closes: #1017277 (this message was generated automatically) -- Greetings https://bugs.debian.org/1017277
Processed: scipy: FTBFS on 32bit arches fixed
Processing commands for cont...@bugs.debian.org: > fixed 1017862 1.8.1-8 Bug #1017862 [src:scipy] scipy: FTBFS on 32 bit arches: TestMLS: Invalid call to pythranized function Marked as fixed in versions scipy/1.8.1-8. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017862: scipy: FTBFS on 32bit arches fixed
fixed 1017862 1.8.1-8 thanks Upload of 1.8.1-8 contained https://salsa.debian.org/python-team/packages/scipy/-/blob/master/debian/patches/pythran_type_PR16646.patch - which fixes this both according to the original failure report and my build of scipy for i386. Cheers, Sven
Bug#1017293: marked as done (moment-timezone.js: FTBFS: Fail the build if the tzdata package does not match TZVER.)
Your message dated Tue, 23 Aug 2022 13:05:56 + with message-id and subject line Bug#1017293: fixed in moment-timezone.js 0.5.34+dfsg-2+2022c has caused the Debian Bug report #1017293, regarding moment-timezone.js: FTBFS: Fail the build if the tzdata package does not match TZVER. 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.) -- 1017293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: moment-timezone.js Version: 0.5.34+dfsg-2+2022a Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/moment -> /usr/share/nodejs/moment >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > # Fail the build if the tzdata package does not match TZVER. > grep -q '^# version 2022a$' /usr/share/zoneinfo/tzdata.zi > make[1]: *** [debian/rules:12: data/meta/2022a.json] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/08/13/moment-timezone.js_0.5.34+dfsg-2+2022a_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: moment-timezone.js Source-Version: 0.5.34+dfsg-2+2022c Done: Martina Ferrari We believe that the bug you reported is fixed in the latest version of moment-timezone.js, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martina Ferrari (supplier of updated moment-timezone.js package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 23 Aug 2022 10:41:08 + Source: moment-timezone.js Architecture: source Version: 0.5.34+dfsg-2+2022c Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Martina Ferrari Closes: 1017293 Changes: moment-timezone.js (0.5.34+dfsg-2+2022c) unstable; urgency=medium . * Rebuild to support tzdata 2022c. Closes: #1017293. * Patch tests to match tzdata 2022c. * Update lintian overrides format. Checksums-Sha1: dd07a8e2610c0e4d419314f007b0f77594b140b6 2349 moment-timezone.js_0.5.34+dfsg-2+2022c.dsc 6a2480482debc1c4d7c8a45de343e2ef1b58d2d3 10748 moment-timezone.js_0.5.34+dfsg-2+2022c.debian.tar.xz 866cc55d8b9758b4348bca702f0574729c53b5ef 20796 moment-timezone.js_0.5.34+dfsg-2+2022c_amd64.buildinfo Checksums-Sha256: 44dac55ee378e1e57a76577fb9d61a737ab043e09209cd9c458428b45c39fb78 2349 moment-timezone.js_0.5.34+dfsg-2+2022c.dsc ab6b305ee37f18a64c74298e5105ff8a33b20a7cd28a0bcc997cf20142b007a6 10748 moment-timezone.js_0.5.34+dfsg-2+2022c.debian.tar.xz fbbee438819a5e6f415cc670d699668c9f29dd4e246e2f537fbe4c4ee2a86604 20796 moment-timezone.js_0.5.34+dfsg-2+2022c_amd64.buildinfo Files: 17768269584803108b1721df1c21d41b 2349 javascript optional moment-timezone.js_0.5.34+dfsg-2+2022c.dsc 5e7b218a3b912eeffac05fa06dd11444 10748 javascript optional moment-timezone.js_0.5.34+dfsg-2+2022c.debian.tar.xz 339d6956b0fbef23659010af76c52743 20796 javascript optional moment-timezone.js_0.5.34+dfsg-2+2022c_amd64.buildinfo -BEGIN PGP SIGNA
Processed: Re: yakuake FTBFS
Processing control commands: > tags -1 +upstream +patch +fixed-upstream Bug #1017130 [src:yakuake] yakuake: FTBFS: appearancesettings.cpp:19:10: fatal error: QtQuickDialogWrapper: No such file or directory Added tag(s) upstream. Bug #1017130 [src:yakuake] yakuake: FTBFS: appearancesettings.cpp:19:10: fatal error: QtQuickDialogWrapper: No such file or directory Added tag(s) patch. Bug #1017130 [src:yakuake] yakuake: FTBFS: appearancesettings.cpp:19:10: fatal error: QtQuickDialogWrapper: No such file or directory Added tag(s) fixed-upstream. -- 1017130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017130: yakuake FTBFS
Control: tags -1 +upstream +patch +fixed-upstream Hello, I can confirm this is fixed in 22.08 [0]. Specifically, the commits are as follows: - https://invent.kde.org/utilities/yakuake/-/commit/56c0b6f38968902765ffe706e2694eb50b0834f7 (not all of it) - https://invent.kde.org/utilities/yakuake/-/commit/9e691cfa077bb2e26efc14dd021da0836d70782d I'd be happy to join the yakuake maintenance team BTW. Best, OdyX [0] https://invent.kde.org/utilities/yakuake/-/commits/release/22.08/
Bug#1017952: groupadd: invalid group ID '-1' when adding with --uid
Hi, thanks for spotting this. It was both a bug in the code and a big omission in our test suite. Both aspects are fixed now. On Mon, Aug 22, 2022 at 10:11:24PM +0200, Samuel Thibault wrote: > Package: adduser > Version: 3.124 > Severity: serious > Justification: Makes creating chroots fail Do have the time to check the code from https://salsa.debian.org/debian/adduser/-/tree/debian-bug-1017952 ? The only file touched to fix the bug is the adduser executable, so you probably don't even need to build the package. Greetings Marc (MR is https://salsa.debian.org/debian/adduser/-/merge_requests/62 and still pending team review) -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1017293: marked as pending in moment-timezone.js
Control: tag -1 pending Hello, Bug #1017293 in moment-timezone.js 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/js-team/moment-timezone.js/-/commit/1681cbc293e11c0e201ef9290006fa8d4ef95eb6 Rebuild to support tzdata 2022c. Closes: #1017293. (this message was generated automatically) -- Greetings https://bugs.debian.org/1017293
Processed: Bug#1017293 marked as pending in moment-timezone.js
Processing control commands: > tag -1 pending Bug #1017293 [src:moment-timezone.js] moment-timezone.js: FTBFS: Fail the build if the tzdata package does not match TZVER. Added tag(s) pending. -- 1017293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016291: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Control: severity -1 important I cannot reproduce this. Which kernel version did you use?
Processed: Re: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Processing control commands:
> severity -1 important
Bug #1016291 [src:python-inotify] python-inotify: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Severity set to 'important' from 'serious'
--
1016291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.
Source: mozjs91 Version: 91.10.0-1 Severity: serious Tags: ftbfs help X-Debbugs-Cc: debian-...@lists.debian.org Control: block 1017961 by -1 Versions of mozjs91 newer than 91.10.0-1 failed to build on the armel buildds. I tried building 91.10.0-1 in an armel chroot on amdahl, and that also fails, which makes me think that the root cause for the build failure is the upgrade from gcc 11 to 12 as default compiler. The final link fails with multiple definitions of the various atomic builtins: > /usr/bin/arm-linux-gnueabi-g++ -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 > -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body > -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits > -Wunreachable-code -Wno-invalid-offsetof -Wc++2a-compat -Wduplicated-cond > -Wimplicit-fallthrough -Wno-error=maybe-uninitialized > -Wno-error=deprecated-declarations -Wno-error=array-bounds > -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object > -Wno-multistatement-macros -Wno-error=class-memaccess > -Wno-error=deprecated-copy -Wno-error=unused-but-set-variable -Wformat > -Wformat-overflow=2 -Wno-psabi -fno-sized-deallocation -fno-aligned-new -g > -O2 -ffile-prefix-map=/home/smcv/mozjs91-armel=. -fstack-protector-strong > -Wformat -Werror=format-security -fPIC -fno-rtti -ffunction-sections > -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -g > -freorder-blocks -O3 -fomit-frame-pointer -funwind-tables -shared > -Wl,-z,defs -Wl,--gc-sections -Wl,-h,libmozjs-91.so -o libmozjs-91.so > /home/smcv/mozjs91-armel/debian/build/js/src/build/libmozjs-91_so.list > -lpthread -Wl,-z,relro -Wl,-z,noexecstack -Wl,-z,text -Wl,-z,relro > -Wl,-z,nocopyreloc -Wl,-Bsymbolic-functions -Wl,--build-id=sha1 > -fstack-protector-strong > -Wl,-rpath-link,/home/smcv/mozjs91-armel/debian/build/dist/bin > -Wl,-rpath-link,/usr/lib > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a > -Wl,--version-script,symverscript -Wl,-soname,libmozjs-91.so.0 -lm > -latomic -lz -lm -ldl > /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/12/libgcc.a(linux-atomic.o): in > function `__sync_fetch_and_add_4': > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94: > first defined here > /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/12/libgcc.a(linux-atomic.o): in > function `__sync_fetch_and_sub_4': > (.text+0x38): multiple definition of `__sync_fetch_and_sub_4'; > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94: > first defined here (etc.) An example build log: https://buildd.debian.org/status/fetch.php?pkg=mozjs91&arch=armel&ver=91.13.0-1&stamp=1661218081&raw=0 The same failure mode occurred when I tried to build mozjs102 with ARMv7 inline assembler disabled for #1017961. (For completeness: 91.10.0-1 and 91.12.0-1 have an additional failure reason involving undefined references to std::type_info::operator==(std::type_info const&) const, but I believe that was fixed in 91.12.0-2 by removing an obsolete patch. The latest mozjs91 and mozjs102 do not have the obsolete patch and do not exhibit the std::type_info errors.) Assistance from fans of armel would be much appreciated. If we cannot get mozjs102 to compile on armel, then gjs and the GNOME stack in general will probably have to be removed from armel, similar to the way we temporarily removed them from s390x between mid 2019 and mid 2020. smcv
Processed: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.
Processing control commands: > block 1017961 by -1 Bug #1017961 [src:mozjs102] mozjs102: Fails to build on armel 1017961 was not blocked by any bugs. 1017961 was not blocking any bugs. Added blocking bug(s) of 1017961: 1017979 -- 1017961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017961 1017979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011215: marked as done (openvdb: FTBFS with onetbb/2021.5.0-8 in experimental)
Your message dated Tue, 23 Aug 2022 11:49:52 + with message-id and subject line Bug#1011215: fixed in openvdb 9.1.0-2 has caused the Debian Bug report #1011215, regarding openvdb: FTBFS with onetbb/2021.5.0-8 in experimental to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1011215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openvdb Version: 8.1.0-3 Severity: normal Tags: ftbfs Hello, tbb/onetbb transition (#1007222) is currently in the planning. During test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-8 in experimental, current source failed to build with the following: -- -- - Configuring OpenVDBCore -- -- -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found suitable version "1.74.0", minimum required is "1.61") found components: iostreams system -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") CMake Error at /usr/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find TBB (missing: Tbb_INCLUDE_DIR) (Required is at least version "2018.0") Call Stack (most recent call first): /usr/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) cmake/FindTBB.cmake:319 (find_package_handle_standard_args) openvdb/openvdb/CMakeLists.txt:123 (find_package) Andrius --- End Message --- --- Begin Message --- Source: openvdb Source-Version: 9.1.0-2 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of openvdb, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated openvdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Aug 2022 13:22:58 +0200 Source: openvdb Architecture: source Version: 9.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Mathieu Malaterre Closes: 1011215 Changes: openvdb (9.1.0-2) unstable; urgency=medium . * Upload to unstable. Closes: #1011215 Checksums-Sha1: 846f1f6b50f90fb6b4e215df0276cdd9ee98ad79 2712 openvdb_9.1.0-2.dsc 153b841033fa9779001bd70323a0cdc9a8295e78 14248 openvdb_9.1.0-2.debian.tar.xz b576c494c3e74ede45afe197a01a5bcfc39d62f1 10789 openvdb_9.1.0-2_source.buildinfo Checksums-Sha256: c31e43a1617fd2c5d3afadc83be6aaa1f2fa75753a527a4eb2b65c56436df6ae 2712 openvdb_9.1.0-2.dsc e5c69e0ed9d8535e58ed5ab0c73c658b92de10b519fe29312f62302453cf2d78 14248 openvdb_9.1.0-2.debian.tar.xz 06e8270a18fd67455eb3e3f508eb9a2348d2bfeb7c1d1c5ad91e8b6bcfd30e5d 10789 openvdb_9.1.0-2_source.buildinfo Files: d255fc91fe06b40cc6bf63ec305d543a 2712 libs optional openvdb_9.1.0-2.dsc 40723a10f8ff9ba80033d945069a4207 14248 libs optional openvdb_9.1.0-2.debian.tar.xz 86ff659ec812e6f632b53e42fee98959 10789 libs optional openvdb_9.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmMEuOkRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0UmghAAmdwdKtiRPJdUxZ6IgfvFKXRF2maXCHtI 7Hcs6MoIaIWAj35sofIborWc0Rd3CAmZoTTM1aKF/MaEvaLZVmsXaMb2FjvKoIED eIMaNpnRn2YH1OeAbg8l/2RaOXThBI7pVGt4HRXEcvwzuDxMiZg2PpaFspv/Qj5y bgROxl0xDa4G2/ht1fU3FQ02OwfdnD5bXsGWojo6xdEItib2ugs19k9ScB4uh4oU uatjdIWmM9r1wUXXv2pnJGnxb0EXqzBJavFDJa/n7hN7dNOthuPX6U/7UQhBMnK4 73OJ+cDj0+8Yz16K8SbfoIL33cMwiAl5WhO0VIxTiGrngPq+41CnoX/bn4ugZ+Nx pe4wNStRaP27I/epycG4CDdnkGcfn2/69wgl6GKBdB9b2647NBB8P+RrVXp/+BE8 3GLIdw6huj0XkgALvX6i5Ags8x+IU6Cobo/mLyVJlprZ+vtZXkzurfKWNRpVR0J9 foyH/B0jSrH4+A1rube0vCkvw5/bvldFQgeqWG19D5DuY16Kw/CwatWnlW1kwooJ S2S71C23xp3Tk/+BSsrRDHC6jPko+qG8lXpoLeMzBIx50kT2cnh8VtUL0bApr9Yf DeQyedZWFVVJ79hPTZqxlNQvF7hSo2zo5N2ANs+9bXVMdcHsICwYWSHqLNc37p+O +7zb2Z6zMJ8= =0e2y -END PGP SIGNATURE End Message ---
Bug#1017326: marked as done (nethack: FTBFS: cdefs.h:393:73: error: macro "__has_attribute" requires an identifier)
Your message dated Tue, 23 Aug 2022 10:34:30 + with message-id and subject line Bug#1017326: fixed in nethack 3.6.6-3 has caused the Debian Bug report #1017326, regarding nethack: FTBFS: cdefs.h:393:73: error: macro "__has_attribute" requires an identifier 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.) -- 1017326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nethack Version: 3.6.6-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I../include -Wall -DGCC_WARN -DNOTPARMDECL -c > ../src/objects.c -o ../src/objects.o > In file included from /usr/include/features.h:489, > from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from ../include/global.h:9, > from ../include/config.h:588, > from ../src/monst.c:6: > /usr/include/x86_64-linux-gnu/sys/cdefs.h:393:73: error: macro > "__has_attribute" requires an identifier > 393 | #if __GNUC_PREREQ (3,4) || __glibc_has_attribute > (__warn_unused_result__) > | > ^ > In file included from /usr/include/features.h:489, > from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from ../include/global.h:9, > from ../include/config.h:588, > from makedefs.c:10: > /usr/include/x86_64-linux-gnu/sys/cdefs.h:393:73: error: macro > "__has_attribute" requires an identifier > 393 | #if __GNUC_PREREQ (3,4) || __glibc_has_attribute > (__warn_unused_result__) > | > ^ > In file included from /usr/include/features.h:489, > from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from ../include/global.h:9, > from ../include/config.h:588, > from ../src/objects.c:35: > /usr/include/x86_64-linux-gnu/sys/cdefs.h:393:73: error: macro > "__has_attribute" requires an identifier > 393 | #if __GNUC_PREREQ (3,4) || __glibc_has_attribute > (__warn_unused_result__) > | > ^ > make[2]: *** [Makefile:478: ../src/monst.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/08/13/nethack_3.6.6-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: nethack Source-Version: 3.6.6-3 Done: Reiner Herrmann We believe that the bug you reported is fixed in the latest version of nethack, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated nethack 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: SH
Bug#1017134: marked as done (box2d: FTBFS: doctest.h:4021:47: error: size of array ‘altStackMem’ is not an integral constant-expression)
Your message dated Tue, 23 Aug 2022 10:33:56 + with message-id and subject line Bug#1017134: fixed in box2d 2.4.1-3 has caused the Debian Bug report #1017134, regarding box2d: FTBFS: doctest.h:4021:47: error: size of array ‘altStackMem’ is not an integral constant-expression 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.) -- 1017134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: box2d Version: 2.4.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/unit-test && /usr/bin/c++ > -DB2_SHARED -I/<>/src/../include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden > -fvisibility-inlines-hidden -std=c++11 -MD -MT > unit-test/CMakeFiles/unit_test.dir/joint_test.cpp.o -MF > CMakeFiles/unit_test.dir/joint_test.cpp.o.d -o > CMakeFiles/unit_test.dir/joint_test.cpp.o -c > /<>/unit-test/joint_test.cpp > In file included from /<>/unit-test/hello_world.cpp:25: > /<>/unit-test/doctest.h:4021:47: error: size of array > ‘altStackMem’ is not an integral constant-expression > 4021 | static char altStackMem[4 * SIGSTKSZ]; > | ^ > make[3]: *** [unit-test/CMakeFiles/unit_test.dir/build.make:79: > unit-test/CMakeFiles/unit_test.dir/hello_world.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/08/13/box2d_2.4.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: box2d Source-Version: 2.4.1-3 Done: Reiner Herrmann We believe that the bug you reported is fixed in the latest version of box2d, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated box2d 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 Aug 2022 17:10:21 +0200 Source: box2d Architecture: source Version: 2.4.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Reiner Herrmann Closes: 1017134 Changes: box2d (2.4.1-3) unstable; urgency=medium . * Team upload. * Use Debian's packaged doctest for building unit tests instead of the embedded one. (Closes: #1017134) * Actually run unit tests during build. * Support nocheck build profile. * Declare that d/rules does not require root. * Bump Standards-Version to 4.6.1. * Drop trailing whitespace in d/control. * Drop dh_installchangelogs override, as upstream changelog is detected automatically. * Update homepage to use https. * Tell doxygen to use relative paths in generated filenames to make build reproducible. Checksums-Sha1: 7dbc55a426775b10e8d75894734e28510faeba69 2265 box2d_2.4.1-3.dsc e23ee600d0f9c9482ddcc29feae9fa25bd894abd 5840 box2d_2.4.1-3.debian.tar.xz 339f0e2f6bd8c3f41900a8a7ad65248759dd81f6 8548 box2d_2.4.1-3_amd64.buildinfo Checksums-Sha256: d9937a4737cc75489094d5dece12f44de3f880191ab56381899a47a1de9fad6d 2265 box2d_2.4.1-3.dsc
Bug#1017356: libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load
On 2022-08-23 10:17, Alastair McKinstry wrote: Hi Drew Yes, this sounds sensible. pmix 4.2.0 is just released, i'm uploading to experimental. Thanks Alistair. At this point we can send 4.2.0 straight to unstable since pmix already got broken here, needs to be fixed. Would be good to send future major versions to experimental first though, i.e. 4.3.0rc1 when its time comes. Upstream seems to reliably break things every major release. Drew
Processed: Re: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Processing control commands: > unblock 997080 by 1001457 Bug #997080 [src:openvdb] openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view Bug #1001136 [src:openvdb] openvdb binary-any FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view 997080 was not blocked by any bugs. 997080 was not blocking any bugs. Removed blocking bug(s) of 997080: 1001457 1001136 was not blocked by any bugs. 1001136 was not blocking any bugs. Removed blocking bug(s) of 1001136: 1001457 -- 1001136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001136 997080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997080: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Control: unblock 997080 by 1001457 On Tue, 23 Aug 2022 10:11:17 +0200 Tobias Frost wrote: > Source: openvdb > Followup-For: Bug #997080 > Control: tags -1 +patch > > MR at https://salsa.debian.org/multimedia-team/openvdb/-/merge_requests/1 > fixes this FTBFS, > (MR made for the version currently in experimental) > > -- > tobi > > (For Documentation as the MR for #997080 was closed without merging) I was debugging into this, and IMHO this is not a compiler issue, but a packaging problem: It seems help2man is executed before dh_auto_install, so help2man just won't find the binary when it tries to create the manpages. I could confirm that in a local pbuilder environment. The patch (attached for references, as I wll delete my fork on salsa soon ) makes d/rules to look into cmake's build directory. With that patch, the package is built successfully. The attached build should be able to proof that. As this is NOT a libstd++ bug, I'm removing the indication that #1001457 blocks this bug. There might be another bug in openvdb triggered by #1001457, but it is not this one. -- tobi openvdb_9.1.0-1_amd64.build.xz Description: application/xz diff --git a/debian/rules b/debian/rules index fce647f9d8ea618722d1b88b8a4cc97375afa3c4..b4fa52e29c1631d0a6462ed17373424750a930e4 100755 --- a/debian/rules +++ b/debian/rules @@ -127,16 +127,16 @@ override_dh_clean: # man page cannot be automatically generated since we need to cleanup help2man output debian/vdb_print.1: debian/vdb_print.1.in - LD_PRELOAD= LD_LIBRARY_PATH=./debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH) help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./debian/tmp/usr/bin/vdb_print + help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./obj-$(DEB_HOST_MULTIARCH)/openvdb_cmd/vdb_print/vdb_print debian/vdb_view.1: debian/vdb_view.1.in - LD_PRELOAD= LD_LIBRARY_PATH=./debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH) help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./debian/tmp/usr/bin/vdb_view + help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./obj-$(DEB_HOST_MULTIARCH)/openvdb_cmd/vdb_view/vdb_view debian/vdb_render.1: debian/vdb_render.1.in - LD_PRELOAD= LD_LIBRARY_PATH=./debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH) help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./debian/tmp/usr/bin/vdb_render + help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./obj-$(DEB_HOST_MULTIARCH)/openvdb_cmd/vdb_render/vdb_render debian/vdb_lod.1: debian/vdb_lod.1.in - LD_PRELOAD= LD_LIBRARY_PATH=./debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH) help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./debian/tmp/usr/bin/vdb_lod + help2man --version-string=$(VER_FULL) --include=$< --output=$@ --no-info --no-discard-stderr ./obj-$(DEB_HOST_MULTIARCH)/openvdb_cmd/vdb_lod/vdb_lod .PHONY: manpages signature.asc Description: PGP signature
Processed: Re: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Processing control commands: > unblock 997080 by 1001457 Bug #997080 [src:openvdb] openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view Bug #1001136 [src:openvdb] openvdb binary-any FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view 997080 was blocked by: 1001457 997080 was not blocking any bugs. Removed blocking bug(s) of 997080: 1001457 1001136 was blocked by: 1001457 1001136 was not blocking any bugs. Removed blocking bug(s) of 1001136: 1001457 -- 1001136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001136 1001457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001457 997080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015053: marked as done (gcc-12-cross-ports: FTBFS: collect2: error: ld returned 1 exit status)
Your message dated Tue, 23 Aug 2022 12:00:17 +0200 with message-id <034adcac-c439-0ecb-86b4-f79b545ad...@debian.org> and subject line Fixed with glibc 2.34 has caused the Debian Bug report #1015053, regarding gcc-12-cross-ports: FTBFS: collect2: error: ld returned 1 exit status 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.) -- 1015053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-12-cross-ports Version: 2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile > /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ > -B/usr/x86_64-linux-gnux32/bin/ -B/usr/x86_64-linux-gnux32/lib64/ -isystem > /usr/x86_64-linux-gnux32/include -isystem > /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include -m64 -DHAVE_CONFIG_H -I. > -I../../../../../src/libphobos/libdruntime -I..-fcf-protection -mshstk -g > -O2 -m64 -c -o core/stdc/libgdruntime_convenience_la-errno_.lo `test -f > 'core/stdc/errno_.c' || echo > '../../../../../src/libphobos/libdruntime/'`core/stdc/errno_.c > libtool: compile: /<>/gcc/build/./gcc/xgcc > -B/<>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnux32/bin/ > -B/usr/x86_64-linux-gnux32/lib64/ -isystem /usr/x86_64-linux-gnux32/include > -isystem /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include -m64 -DHAVE_CONFIG_H -I. > -I../../../../../src/libphobos/libdruntime -I.. -fcf-protection -mshstk -g > -O2 -m64 -c ../../../../../src/libphobos/libdruntime/core/stdc/errno_.c > -fPIC -DPIC -o core/stdc/.libs/libgdruntime_convenience_la-errno_.o > libtool: compile: /<>/gcc/build/./gcc/xgcc > -B/<>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnux32/bin/ > -B/usr/x86_64-linux-gnux32/lib64/ -isystem /usr/x86_64-linux-gnux32/include > -isystem /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include -m64 -DHAVE_CONFIG_H -I. > -I../../../../../src/libphobos/libdruntime -I.. -fcf-protection -mshstk -g > -O2 -m64 -c ../../../../../src/libphobos/libdruntime/core/stdc/errno_.c -o > core/stdc/libgdruntime_convenience_la-errno_.o >/dev/null 2>&1 > /bin/bash ../libtool --tag=D --mode=compile > /<>/gcc/build/./gcc/gdc -B/<>/gcc/build/./gcc/ > -B/usr/x86_64-linux-gnux32/bin/ -B/usr/x86_64-linux-gnux32/lib64/ -isystem > /usr/x86_64-linux-gnux32/include -isystem > /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include-prefer-pic -fversion=Shared -Wall > -frelease -ffunction-sections -fdata-sections -fcf-protection -mshstk > -fversion=CET -O2 -g -m64 -m64 -fpreview=dip1000 -fpreview=fieldwise > -fpreview=dtorfields -nostdinc -I ../../../../../src/libphobos/libdruntime -I > . -c -o core/sys/posix/config.lo > ../../../../../src/libphobos/libdruntime/core/sys/posix/config.d > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/07/16/gcc-12-cross-ports_2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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 --- Fixed with glibc 2.34--- End Message ---
Bug#1017753: autopkgtest-virt-lxc regularly fails to start or return from reboot
On Mon, 22 Aug 2022 at 21:07:57 +0200, Paul Gevers wrote: > paul@mulciber ~ $ sudo lxc-start test && sudo lxc-attach test -- sh -ec "if > [ -d /run/systemd/system ]; then echo systemd ; exit 0 ; else echo unknown ; > exit 0 ; fi" ; echo $? && sudo lxc-stop test > [sudo] password for paul: > unknown > 0 > paul@mulciber ~ $ sudo lxc-start test && sudo lxc-attach test -- sh -ec "if > [ -d /run/systemd/system ]; then echo systemd ; exit 0 ; else echo unknown ; > exit 0 ; fi" ; echo $? && sudo lxc-stop test > systemd > 0 A theory for what might be going on here: as systemd starts up, it creates /run/systemd/system *almost* immediately; but if lxc-attach happens fast enough, then it can finish running the shell command before systemd has had a chance to create /run/systemd/system. So wait_booted() would think we're running sysvinit or some other non-systemd init, and run lib/await-sysv-boot instead of systemctl. However, that seems unlikely to be the root cause for the original bug you reported. Even if we mis-detect systemd as sysvinit, lib/await-sysv-boot is basically doing the same as the old implementation, polling until runlevel(8) indicates a suitable runlevel, but with the polling loop happening in the container instead of on the host. And I'd expect that to mostly work, either on systemd or sysvinit? The old implementation always just did the equivalent of this anyway, and systemd does have a working runlevel(8) (its use is discouraged, but it's there). The one part of lib/await-sysv-boot that is not systemd-friendly is that it unconditionally waits for /etc/init.d/rc to finish, and does not wait for network-online.target if systemd was detected. On podman with systemd, we'd ideally be waiting for boot by using `NOTIFY_SOCKET=... podman run --notify=container ...` - but that requires knowing in advance that the container is going to boot with systemd (or in principle some other init system that implements the sd_notify() protocol), and in general we don't know that in advance. Also, lxc doesn't implement that protocol, as far as I'm aware. >From the original bug report: > autopkgtest-virt-lxc [21:45:43]: ERROR: Waiting for boot to finish failed > autopkgtest-virt-lxc [21:45:43]: ERROR: Failed to connect to bus: No such > file or directory I think that error message is systemd failing to connect to the D-Bus system bus when we do the systemctl command to wait for boot to finish. This is a different race: we have successfully identified the container as running systemd as its init system, but there's no system bus socket yet, so systemctl fails. In the follow-up, instead we're hitting a timeout: > File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 262, in wait_booted > (rc, err, _) = execute_timeout( This is a 60 second timeout waiting for lib/await-sysv-boot to finish, and it looks as though lib/await-sysv-boot has not produced any output on its stdout/stderr (I should probably make it more verbose, since its output is only shown if it fails). smcv
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> affects 1017845 + gnuplot
Bug #1017845 [emacs-common] emacs-common: Endless fork loop at installation and
at run time: /usr/bin/emacs --batch -l
/tmp/emacs-int-comp-subr--trampoline-_{scroll_other_window,delete_frame}_0-.el
Bug #1017817 [emacs-common] emacs: new release seems to have funny ideas about
byte-compiling process
Added indication that 1017845 affects gnuplot
Added indication that 1017817 affects gnuplot
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1017817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017817
1017845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Processing control commands: > tags -1 +patch Bug #997080 [src:openvdb] openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view Bug #1001136 [src:openvdb] openvdb binary-any FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view Added tag(s) patch. Added tag(s) patch. -- 1001136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001136 997080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997080: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Source: openvdb Followup-For: Bug #997080 Control: tags -1 +patch MR at https://salsa.debian.org/multimedia-team/openvdb/-/merge_requests/1 fixes this FTBFS, (MR made for the version currently in experimental) -- tobi
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 1011215 9.0.0-1 Bug #1011215 [src:openvdb] openvdb: FTBFS with onetbb/2021.5.0-8 in experimental Marked as fixed in versions openvdb/9.0.0-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1011215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1017952
Processing commands for cont...@bugs.debian.org: > tags 1017952 + confirmed Bug #1017952 [adduser] groupadd: invalid group ID '-1' when adding with --uid Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017798: emacs-el
Hi, I had the same problem, and indeed installing emacs-el solved the issue. Best regards, Eugen
