Processed: Docker.io breaks libvirt/qemu bridge network
Processing control commands: > severity -1 minor Bug #1058795 [docker.io] installing docker.io makes all qemu guests lose internet connection Severity set to 'minor' from 'critical' > tag -1 wontfix Bug #1058795 [docker.io] installing docker.io makes all qemu guests lose internet connection Added tag(s) wontfix. > retitle -1 Docker.io breaks libvirt/qemu bridge network Bug #1058795 [docker.io] installing docker.io makes all qemu guests lose internet connection Changed Bug title to 'Docker.io breaks libvirt/qemu bridge network' from 'installing docker.io makes all qemu guests lose internet connection'. -- 1058795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058795: Docker.io breaks libvirt/qemu bridge network
Control: severity -1 minor Control: tag -1 wontfix Control: retitle -1 Docker.io breaks libvirt/qemu bridge network Please review the package's postinst script to convince yourself that the Debian docker.io package does not ship any firewall rules: https://salsa.debian.org/go-team/packages/docker/-/blob/master/debian/docker.io.postinst?ref_type=heads However, the docker.io package does indeed manipulate iptables rules to provide container isolation. This is a well-known and documented feature at https://docs.docker.com/network/packet-filtering-firewalls/ The particular issue that you are experiencing is probably described best at https://serverfault.com/questions/963759/docker-breaks-libvirt-bridge-network. That article also container an detailed description on why this is actually a feature and how to work around it. On a personal note, consider installing the 'podman-docker' package instead of the 'docker.io' package, this might be sufficient depending on your use-case. I'm leaving this bug open as I'm not the regular maintainer of the docker.io package. Probably this should be documented in the README.md file or similar. Happy Holidays, -rt
Processed: found 1040901 in 6.1.67-1, found 1040901 in 6.1.55-1, found 1040901 in 5.10.197-1 ...
Processing commands for cont...@bugs.debian.org:
> found 1040901 6.1.67-1
Bug #1040901 {Done: Bastian Blank } [src:linux] linux modules
must not be signed with CA key, bump ABI every upload
Marked as found in versions linux/6.1.67-1.
> found 1040901 6.1.55-1
Bug #1040901 {Done: Bastian Blank } [src:linux] linux modules
must not be signed with CA key, bump ABI every upload
Marked as found in versions linux/6.1.55-1.
> found 1040901 5.10.197-1
Bug #1040901 {Done: Bastian Blank } [src:linux] linux modules
must not be signed with CA key, bump ABI every upload
Marked as found in versions linux/5.10.197-1.
> found 1040901 5.10.178-3
Bug #1040901 {Done: Bastian Blank } [src:linux] linux modules
must not be signed with CA key, bump ABI every upload
Marked as found in versions linux/5.10.178-3.
> found 1040901 4.19.235-1
Bug #1040901 {Done: Bastian Blank } [src:linux] linux modules
must not be signed with CA key, bump ABI every upload
Marked as found in versions linux/4.19.235-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057452: marked as done (zfs-dkms: module build fails for Linux 6.6: zfs_ctldir.c:523:13: error: 'struct inode' has no member named 'i_ctime')
Your message dated Wed, 27 Dec 2023 13:09:20 +0800 with message-id and subject line fixed in zfs-linux/2.2.2-1 has caused the Debian Bug report #1057452, regarding zfs-dkms: module build fails for Linux 6.6: zfs_ctldir.c:523:13: error: 'struct inode' has no member named 'i_ctime' 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.) -- 1057452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zfs-dkms Version: 2.1.14-1 Severity: important Control: close -1 2.2.2-1~exp1 Hi, zfs-dkms fails to build a module for Linux 6.6 that was just uploaded to experimental: ... CC [M] /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_ctldir.o CC [M] /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_debug.o CC [M] /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_dir.o CC [M] /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_file_os.o CC [M] /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_ioctl_os.o CC [M] /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_racct.o CC [M] /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_sysfs.o /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_ctldir.c: In function 'zfsctl_inode_alloc': /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_ctldir.c:523:13: error: 'struct inode' has no member named 'i_ctime'; did you mean 'i_atime'? 523 | ip->i_ctime = now; | ^~~ | i_atime make[6]: *** [/usr/src/linux-headers-6.6-common/scripts/Makefile.build:248: /var/lib/dkms/zfs/2.1.14/build/module/zfs/../os/linux/zfs/zfs_ctldir.o] Error 1 ... Andreas --- End Message --- --- Begin Message --- Souce: zfs-linux Source-Version: 2.2.2-1 This issue has been fixed since 2.2.2-1 land in unstable, closing the report. Thanks, Aron--- End Message ---
Bug#1057451: rust-ahash: autopkgtests failing
tags 1057451 +patch
thanks
I just looked at the remaining autopkgtest failures in rust-ahash, I found and
fixed two issues and after doing so the autopkgtests passed.
The first issue was some arithmetic overflows in summations in tests/bench.rs
these cause panics if built/run in Debug mode (as "cargo test --all-targets"
does by default). The results of the summations were not used for anything.
I'm not sure what the original intent of the summations was, perhaps it was
just to shut compiler warnings up, perhaps it was an attempt to stop the
compiler optimizing stuff away. I just commented out the summations, another
possibility would be to replace them with calls to std::hint::black_box
The second issue was some tests that failed to build when the std feature
was enabled but none of the rng features (runtime-rng, compile-time-rng
or no-rng) were enabled. I added/adjusted feature gaurds to fix this
issue.
Debdiff attached, if I get no response I will likely NMU this in a week
or so.diff -Nru rust-ahash-0.8.5/debian/changelog rust-ahash-0.8.5/debian/changelog
--- rust-ahash-0.8.5/debian/changelog 2023-12-10 23:06:48.0 +
+++ rust-ahash-0.8.5/debian/changelog 2023-12-26 10:08:52.0 +
@@ -1,3 +1,13 @@
+rust-ahash (0.8.5-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix autopkgtest. (Closes: #1057451)
++ Disable overflowing additions whose results are not used in
tests/bench.rs
++ Add/Adjust feature gaurds to fix build of tests when the std feature is
+ enabled but no rng feature is enabled.
+
+ -- Peter Michael Green Tue, 26 Dec 2023 10:08:52 +
+
rust-ahash (0.8.5-3) unstable; urgency=medium
* update patch;
diff -Nru rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch
rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch
--- rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch 1970-01-01
00:00:00.0 +
+++ rust-ahash-0.8.5/debian/patches/1001_bench_overflow.patch 2023-12-26
10:08:52.0 +
@@ -0,0 +1,84 @@
+Description: Disable overflowing additions whose results are not used in
tests/bench.rs
+Author: Peter Michael Green
+Bug-Debian: https://bugs.debian.org/1057451
+
+--- rust-ahash-0.8.5.orig/tests/bench.rs
rust-ahash-0.8.5/tests/bench.rs
+@@ -118,10 +118,10 @@ fn bench_map(c: Criterion) {
+ group.bench_function("aHash-alias", |b| {
+ b.iter(|| {
+ let hm: ahash::HashMap = (0..1_000_000).map(|i| (i,
i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get() {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -129,10 +129,10 @@ fn bench_map(c: Criterion) {
+ group.bench_function("aHash-hashBrown", |b| {
+ b.iter(|| {
+ let hm: hashbrown::HashMap = (0..1_000_000).map(|i|
(i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get() {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -140,10 +140,10 @@ fn bench_map(c: Criterion) {
+ group.bench_function("aHash-hashBrown-explicit", |b| {
+ b.iter(|| {
+ let hm: hashbrown::HashMap =
(0..1_000_000).map(|i| (i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get() {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -151,10 +151,10 @@ fn bench_map(c: Criterion) {
+ group.bench_function("aHash-wrapper", |b| {
+ b.iter(|| {
+ let hm: ahash::AHashMap = (0..1_000_000).map(|i|
(i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get() {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -162,10 +162,10 @@ fn bench_map(c: Criterion) {
+ group.bench_function("aHash-rand", |b| {
+ b.iter(|| {
+ let hm: std::collections::HashMap =
(0..1_000_000).map(|i| (i, i)).collect();
+-let mut sum = 0;
++//let mut sum = 0;
+ for i in 0..1_000_000 {
+ if let Some(x) = hm.get() {
+-sum += x;
++//sum += x;
+ }
+ }
+ })
+@@ -174,10 +174,10 @@ fn bench_map(c: Criterion) {
+ b.iter(||
Processed: re: rust-ahash: autopkgtests failing
Processing commands for cont...@bugs.debian.org: > tags 1057451 +patch Bug #1057451 [src:rust-ahash] rust-ahash: autopkgtests failing Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057149: marked as done (gimp: Please add Conflicts+Replaces: gimp-dds)
Your message dated Tue, 26 Dec 2023 21:32:41 + with message-id and subject line Bug#1057149: fixed in gimp 2.10.22-4+deb11u2 has caused the Debian Bug report #1057149, regarding gimp: Please add Conflicts+Replaces: gimp-dds 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.) -- 1057149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gimp Version: 2.10.12-1 Severity: serious gimp-dds was included in 2.10.10, and the old version of the plugin in gimp-dds is also vulnerable to CVE-2023-1. Please add[1] Conflicts: gimp-dds Replaces: gimp-dds to get rid of the stale version of this plugin. A fast upload would be appreciated so that I can also submit this change for the next bookworm (and bullseye) point releases. Thanks in advance [1] https://lists.debian.org/deity/2023/11/msg00037.html --- End Message --- --- Begin Message --- Source: gimp Source-Version: 2.10.22-4+deb11u2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of gimp, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated gimp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 Dec 2023 16:47:53 +0200 Source: gimp Architecture: source Version: 2.10.22-4+deb11u2 Distribution: bullseye Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Adrian Bunk Closes: 1057149 Changes: gimp (2.10.22-4+deb11u2) bullseye; urgency=medium . * Non-maintainer upload. * Add Conflicts+Replaces: gimp-dds to remove old versions of this plugin shipped by gimp itself since 2.10.10. (Closes: #1057149) Checksums-Sha1: 8ac4a0683a70a47b3b74e547699f9964211e5af7 3470 gimp_2.10.22-4+deb11u2.dsc a4c93cedf3e9671159eb2aeb2ff2b6b1041d8f29 61464 gimp_2.10.22-4+deb11u2.debian.tar.xz Checksums-Sha256: 47b97b36c54fba4bf79a13d2dafd304eef153d85f08592ad1df07d8397d9a962 3470 gimp_2.10.22-4+deb11u2.dsc e966ddc89013efdd64f317aca558b42d63f0c98e6f83b4cf06e6be378568fe95 61464 gimp_2.10.22-4+deb11u2.debian.tar.xz Files: 12c2a0e6e70e9495e7e5302eca4319b7 3470 graphics optional gimp_2.10.22-4+deb11u2.dsc e729195b5df88cc3232e867c3c37c234 61464 graphics optional gimp_2.10.22-4+deb11u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmVrUbQACgkQiNJCh6LY mLFnbA//Wye5LTUSt3VqMzteiRFzJp62QtyMkKBADoO1e57cz/MOs28T2mohh4v2 IBVpTcAYacNDQJcYLVbbKEF3ZliXCmmdGJe1sUIKB0viCvc6rWX8c8VWwLaAg4bA Zvo2uCpipwFLDJlUMe2M8E8UFg7AFs1tT87BggxvhMw60/3poNo5jbe+iGyTo7vB jkJ5CahF3/bnY5RXpIdCm+ETcX1cuSx9KVY6fUQv7Qqb7kAPrch0jPOBiOhlmqMC BBqyXhsMoJxxbv12jgpos4PzY2xSBviwOpyZrHA0toAJAp0Zgcr40vYZal/209K0 5t5lVFL7Pr6sX24k8RIYl7Gxl1PPHQA/VeEvCzOQx5LERTBzoevZ/eveTGWF4MDn ZzWwG3J8WOFGwtncmJ5m4skGT4bXmzlr+nw7l491HaYocNqmNeoX4339qWpgD2wg zGHxeUVst1fzcHmpY6wmvNa9fYo6ylklzKFNgmDtVxNDjeZApufnRHjhZ6DzpJr9 EYePev6/Zvihcy2PkHpUSn+E4Jsvsk8O3YYMtlVCHmjPtqA+H17AO3RoCqSonN// /xiPMBGLlfkz6ecfHE6XvXaDnflAdbyFXjwk+Dhrdqjmzszpu5EJksbbpGv3eBVT KoNI0LzVXgGt/leVyha4QRW6vcsH64vOw1GCt2TFHHKu0E1kZuE= =aKhK -END PGP SIGNATURE End Message ---
Bug#1058088: marked as done (python-pathtools: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Tue, 26 Dec 2023 21:22:51 +
with message-id
and subject line Bug#1058088: fixed in python-pathtools 0.1.2-6
has caused the Debian Bug report #1058088,
regarding python-pathtools: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)
--
1058088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pathtools
Version: 0.1.2-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --buildsystem=pybuild --with python3,sphinxdoc
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 25, in
> import imp
> ModuleNotFoundError: No module named 'imp'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-pathtools_0.1.2-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-pathtools
Source-Version: 0.1.2-6
Done: gustavo panizzo
We believe that the bug you reported is fixed in the latest version of
python-pathtools, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gustavo panizzo (supplier of updated python-pathtools
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, 26 Dec 2023 21:45:20 +0100
Source: python-pathtools
Architecture: source
Version: 0.1.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: gustavo panizzo
Closes: 1058088
Changes:
python-pathtools (0.1.2-6) unstable; urgency=medium
.
[ Debian Janitor ]
* Update watch file format version to 4.
* Bump debhelper from old 12 to 13.
* Set field Upstream-Contact in debian/copyright.
* Remove obsolete fields Contact, Name from debian/upstream/metadata (already
present in machine-readable debian/copyright).
* Update standards version to 4.6.1, no changes needed.
.
[ gustavo panizzo ]
* [b1cdb5] Add support for python 3.12 (Closes: 1058088)
* [8a4bab] Bump Standards-Version to 4.6.2
* [e34246] Build the package as non-root user
* [fbc222] Depend on sphinxdoc since it is used for cleanup
* [1d190b] Update copyright years
* [eec61c] Override a lintian warning
Checksums-Sha1:
facc1ccb69b6f32801627919f7d427d7dff1829c 1511 python-pathtools_0.1.2-6.dsc
1d8a9e677b17603fbe6bed0dd962b1ffe2abd5b4 6440
python-pathtools_0.1.2-6.debian.tar.xz
8e915046de3ae5194cae7988ff1064d07d553220 7096
python-pathtools_0.1.2-6_amd64.buildinfo
Checksums-Sha256:
1fe76a2fa730b4dcd7594bb73e30255f997aee075c4eb34e045a8dae7bff6b33 1511
python-pathtools_0.1.2-6.dsc
d3721928220d044f6c209c8c98ca003ea86f3dfa5aaa0415e7b86beac17edc07 6440
python-pathtools_0.1.2-6.debian.tar.xz
2bd57d5d57c9176625ecde76a5b024b44e8dfca35e15fbe2725313da3d10f3fc 7096
python-pathtools_0.1.2-6_amd64.buildinfo
Files:
Bug#1058532: golang-google-api: FTBFS: tests failed
This is blocking migration https://tracker.debian.org/pkg/golang-golang-x-oauth2 > Migration status for golang-golang-x-oauth2 (0.4.0-1 to 0.15.0-1): BLOCKED: > Rejected/violates migration policy/introduces a regression > Issues preventing migration: > ∙ ∙ autopkgtest for golang-golang-x-oauth2/0.15.0-1: amd64: Pass, arm64: > Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass > ∙ ∙ autopkgtest for golang-google-api/0.61.0-1: amd64: Regression or new test > ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed > (not a regression), armhf: Failed (not a > regression), i386: Failed (not a > regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: > Regression or new test ♻ (reference ♻)
Bug#1052801: marked as done (pytest-flask: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Tue, 26 Dec 2023 20:36:53 +
with message-id
and subject line Bug#1052801: fixed in pytest-flask 1.3.0-1
has caused the Debian Bug report #1052801,
regarding pytest-flask: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-flask
Version: 0.15.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=/<> PYBUILD_SYSTEM=custom
> PYBUILD_TEST_ARGS="{interpreter} -m pytest -x -v tests" dh_auto_test
> I: pybuild base:291: python3.11 -m pytest -x -v tests
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0 --
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>
> configfile: tox.ini
> collecting ... collected 30 items
>
> tests/test_fixtures.py::TestFixtures::test_config_access ERROR [
> 3%]
>
> ERRORS
>
> __ ERROR at setup of TestFixtures.test_config_access
> ___
> file /<>/tests/test_fixtures.py, line 10
> def test_config_access(self, config):
> E fixture 'config' not found
> > available fixtures: LineMatcher, _config_for_test, _pytest,
> > _sys_snapshot, app, appdir, cache, capfd, capfdbinary, caplog, capsys,
> > capsysbinary, doctest_namespace, linecomp, monkeypatch, pytestconfig,
> > pytester, record_property, record_testsuite_property, record_xml_attribute,
> > recwarn, testdir, tmp_path, tmp_path_factory, tmpdir, tmpdir_factory
> > use 'pytest --fixtures [testpath]' for help on them.
>
> /<>/tests/test_fixtures.py:10
> === warnings summary
> ===
> ../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1373
> /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1373:
> PytestConfigWarning: Unknown config option: pep8ignore
>
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
>
> ../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1373
> /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1373:
> PytestConfigWarning: Unknown config option: pep8maxlinelength
>
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
>
> tests/test_live_server.py:41
> /<>/tests/test_live_server.py:41: PytestUnknownMarkWarning:
> Unknown pytest.mark.options - is this a typo? You can register custom marks
> to avoid this warning - for details, see
> https://docs.pytest.org/en/stable/how-to/mark.html
> @pytest.mark.options(server_name='example.com:5000')
>
> tests/test_markers.py:17
> /<>/tests/test_markers.py:17: PytestUnknownMarkWarning:
> Unknown pytest.mark.options - is this a typo? You can register custom marks
> to avoid this warning - for details, see
> https://docs.pytest.org/en/stable/how-to/mark.html
> @pytest.mark.options(debug=False)
>
> tests/test_markers.py:21
> /<>/tests/test_markers.py:21: PytestUnknownMarkWarning:
> Unknown pytest.mark.options - is this a typo? You can register custom marks
> to avoid this warning - for details, see
> https://docs.pytest.org/en/stable/how-to/mark.html
> @pytest.mark.options(foo=42)
>
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> === short test summary info
>
> ERROR tests/test_fixtures.py::TestFixtures::test_config_access
> !! stopping after 1 failures
> !!!
> = 5 warnings, 1 error in 0.04s
> =
> E: pybuild pybuild:395: test: plugin custom failed with: exit code=1:
> python3.11 -m pytest -x -v tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/pytest-flask_0.15.1-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
Bug#1042299: marked as done (libfirefox-marionette-perl: FTBFS: tests fail)
Your message dated Tue, 26 Dec 2023 20:32:08 +
with message-id
and subject line Bug#1042299: fixed in libfirefox-marionette-perl 1.35-1+deb12u1
has caused the Debian Bug report #1042299,
regarding libfirefox-marionette-perl: FTBFS: tests fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfirefox-marionette-perl
Version: 1.35-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib',
> 'blib/arch')" t/*.t
> # Testing Firefox::Marionette 1.35
> t/00.load.t
> 1..1
> ok 1 - use Firefox::Marionette;
> ok
> # Version is Mozilla Firefox 115.0.2esr
> # XAUTHORITY is /tmp/xvfb-run.UybmK6/Xauthority
> # DISPLAY is :99
> # D-Bus is working
> # Debian Version is trixie/sid
> # Xvfb deb version is 2:21.1.7-3
> # grep -r Mem /proc/meminfo
> # MemTotal: 32522708 kB
> # MemFree:27782096 kB
> # MemAvailable: 31741224 kB
> # ulimit -a | grep -i mem
> # memory(kbytes) unlimited
> # locked memory(kbytes) 4065338
> # vmemory(kbytes) unlimited
> # This firefox installation has 0 existing profiles
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> # Initial tests
> # Testing has been running for 2 seconds at t/01-marionette.t line 714
> ** firefox --version
> ** firefox -marionette -safe-mode -headless -profile
> /tmp/firefox_marionette_local_J2HxYCzFDvj/profile --no-remote --new-instance
> *** You are running in headless mode.
> << 50:{"applicationType":"gecko","marionetteProtocol":3}
> >> 73:[0,1,"WebDriver:NewSession",{"capabilities":{"requiredCapabilities":{}}}]
> <<
> 721:[1,1,null,{"sessionId":"da1bdff4-017f-47b8-b199-bcbe91185eb9","capabilities":{"browserName":"firefox","browserVersion":"115.0.2","platformName":"linux","acceptInsecureCerts":false,"pageLoadStrategy":"normal","setWindowRect":true,"timeouts":{"implicit":0,"pageLoad":30,"script":3},"strictFileInteractability":false,"unhandledPromptBehavior":"dismiss
> and
> notify","moz:accessibilityChecks":false,"moz:buildID":"20230710180319","moz:headless":true,"moz:platformVersion":"5.10.0-23-cloud-amd64","moz:processID":84703,"moz:profile":"/tmp/firefox_marionette_local_J2HxYCzFDvj/profile","moz:shutdownTimeout":6,"moz:useNonSpecCompliantPointerOrigin":false,"moz:webdriverClick":true,"moz:windowless":false,"proxy":{}}}]
> >> 33:[0,2,"WebDriver:GetCapabilities"]
> <<
> 680:[1,2,null,{"value":{"capabilities":{"browserName":"firefox","browserVersion":"115.0.2","platformName":"linux","acceptInsecureCerts":false,"pageLoadStrategy":"normal","setWindowRect":true,"timeouts":{"implicit":0,"pageLoad":30,"script":3},"strictFileInteractability":false,"unhandledPromptBehavior":"dismiss
> and
> notify","moz:accessibilityChecks":false,"moz:buildID":"20230710180319","moz:headless":true,"moz:platformVersion":"5.10.0-23-cloud-amd64","moz:processID":84703,"moz:profile":"/tmp/firefox_marionette_local_J2HxYCzFDvj/profile","moz:shutdownTimeout":6,"moz:useNonSpecCompliantPointerOrigin":false,"moz:webdriverClick":true,"moz:windowless":false,"proxy":{]
> Use of uninitialized value in concatenation (.) or string at
> t/01-marionette.t line 733.
> # Browser version is
> Use of uninitialized value in split at t/01-marionette.t line 740.
> # Operating System is Unknown Unknown
> # Profile Directory is /tmp/firefox_marionette_local_J2HxYCzFDvj/profile
> # Mozilla PID is Unknown
> # Firefox BuildID is Unknown
> # Addons are disabled
> Use of uninitialized value $major_version in numeric gt (>) at
> t/01-marionette.t line 753.
> >> 32:[0,3,"Marionette:GetWindowType"]
> <<
Bug#1054417: marked as done (weborf: Denial of service when executing cgi executables)
Your message dated Tue, 26 Dec 2023 20:32:29 +
with message-id
and subject line Bug#1054417: fixed in weborf 0.17-3+deb11u1
has caused the Debian Bug report #1054417,
regarding weborf: Denial of service when executing cgi executables
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.)
--
1054417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: weborf
Version: 0.20
Severity: grave
Tags: patch upstream security
X-Debbugs-Cc: tipos...@tiscali.it
Dear Maintainer,
there is an error in the code to execute cgi.
Best
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages weborf depends on:
ii libc6 2.37-12
ii libmagic1 1:5.45-2
ii libssl33.0.11-1
weborf recommends no packages.
Versions of packages weborf suggests:
pn php-cgi
-- no debconf information
commit 49824204add55aab0568d90a6b1e7c822d32120d
Author: Salvo 'LtWorf' Tomaselli
Date: Wed Oct 11 23:48:19 2023 +0200
Solve issue with unterminated buffer
diff --git a/cgi.c b/cgi.c
index 08d664d..f8276b1 100644
--- a/cgi.c
+++ b/cgi.c
@@ -233,8 +233,7 @@ static inline void cgi_execute_child(connection_t*
connection_prop,string_t* pos
environ = NULL; //Clear env vars
if (strlen(executor) == 0) {
-executor = malloc(connection_prop->strfile_len + 1);
-strncpy(executor, connection_prop->strfile,
connection_prop->strfile_len);
+executor = connection_prop->strfile;
}
cgi_set_http_env_vars(connection_prop->http_param);
--- End Message ---
--- Begin Message ---
Source: weborf
Source-Version: 0.17-3+deb11u1
Done: Salvo 'LtWorf' Tomaselli
We believe that the bug you reported is fixed in the latest version of
weborf, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Salvo 'LtWorf' Tomaselli (supplier of updated weborf
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 22 Dec 2023 09:47:49 +0100
Source: weborf
Architecture: source
Version: 0.17-3+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Salvo 'LtWorf' Tomaselli
Changed-By: Salvo 'LtWorf' Tomaselli
Closes: 1054417
Changes:
weborf (0.17-3+deb11u1) bullseye; urgency=medium
.
* Backport patch from upstream to fix denial of service (Closes: 1054417)
Checksums-Sha1:
51f2514e2a84a874d1308b8e826e8169d4ad2677 2188 weborf_0.17-3+deb11u1.dsc
b333a2c78b84f59dc70e835f84fd7b7e9f6e6d6a 17072
weborf_0.17-3+deb11u1.debian.tar.xz
3ea35f1d2bfd214b951b638e853f07616860d57f 11748
weborf_0.17-3+deb11u1_amd64.buildinfo
Checksums-Sha256:
37b0231f753e70db8819fd19025e4f927b62db63bb8cb0c706662fefa42b3644 2188
weborf_0.17-3+deb11u1.dsc
db05d3d9e2a0692cc0b27c7deb7ac1c3ae68a1b8612959e92037678c114424f1 17072
weborf_0.17-3+deb11u1.debian.tar.xz
dce4b9349b62404b72d0ccf25717fdd066f1cc9a9d011f90708c104e3367b457 11748
weborf_0.17-3+deb11u1_amd64.buildinfo
Files:
f18abb2d1f8f19728e8c79e28e5b34d0 2188 httpd optional weborf_0.17-3+deb11u1.dsc
c9c2130cb32f6272db2041525c116a09 17072 httpd optional
weborf_0.17-3+deb11u1.debian.tar.xz
81a6b3203f6b3de2a502b3d14736d650 11748 httpd optional
weborf_0.17-3+deb11u1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmWFTYgACgkQs6fPDIAY
hs/nHhAAlV2/C6UZ5adX6AC4VxJ6PizKX5Nbxe+NqqvnKy67YIcKY/+csdVhSWzr
9RNECDVqcW1mypmj8GovUU1fWjp+f+k+L0aUeDmrOjWY6+WKQfmNIK+IAZqxrv5v
m8S8Rv1388py6/grliLpgHIYZH+4au6BD7fyHwF2uJwmu/u3htDFLT8LMOuFRzFV
Rh0NlyLVur1q8bm8nXiX3KId/zC1c0yNvAiwEK1/eA0IkW8k9kePC5ZpaxQJqpbd
tF06mWoRTBOo8c3xvOfM03N1uATgLqN+z8201wML/2NmU6mOrW+u31wM4RGaUO5x
5vWj6rQKH77lyDl1+Wkn8241udAWRSds9sE8XJ7L/QthW4EfkrzuOuR0Bn6oOh0W
Bug#1056953: marked as done (gdcm: ABI broke in last version 3.0.22-1)
Your message dated Tue, 26 Dec 2023 19:00:12 + with message-id and subject line Bug#1056953: fixed in libargparse 3.0-1 has caused the Debian Bug report #1056953, regarding gdcm: ABI broke in last version 3.0.22-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.) -- 1056953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdcm Version: 3.0.22-1 Severity: serious Hello, as seen, gdcm is not migrating because of camitk test regression. Looking at the failure, looks like the fault is not in camitk, but in gdcm itself, changing the ABI without a SONAME bump quoting https://ci.debian.net/data/autopkgtest/testing/amd64/c/camitk/40209513/log.gz 159s 2023-11-26 13:11:35.182 [ERROR ] Extension manager error: 159s Loading component extension failed after 10 tries. 159s 159s Plugin: 159s "/usr/lib/x86_64-linux-gnu/camitk-5.1/components/libitkimage.so.5.1.0" 159s 159s Error: 159s Cannot load library : (/lib/x86_64-linux-gnu/libITKIOGDCM-5.3.so.1: undefined symbol: _ZN4gdcm16DirectionCosinesD1Ev 159s 159s List of library paths: 159s - /usr/lib/x86_64-linux-gnu/camitk-5.1/viewers 159s - /usr/lib/x86_64-linux-gnu/camitk-5.1/components 159s - /usr/lib/x86_64-linux-gnu/camitk-5.1/actions 159s - /usr/lib/x86_64-linux-gnu/camitk-5.1 159s - /usr/lib/x86_64-linux-gnu/qt5/plugins 159s - /usr/bin 159s $ echo _ZN4gdcm16DirectionCosinesD1Ev |c++filt gdcm::DirectionCosines::~DirectionCosines() Checking the changes in header files for new release I see -DirectionCosines::~DirectionCosines() = default; and - ~DirectionCosines(); + ~DirectionCosines() = default; But this object is used in external packages, so it can't change signature or be dropped. G. OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libargparse Source-Version: 3.0-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of libargparse, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libargparse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Nov 2023 12:17:36 +0100 Source: libargparse Binary: libargparse-dev Architecture: source amd64 Version: 3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libargparse-dev - parsing command-line arguments in C++ Closes: 1056953 Changes: libargparse (3.0-1) unstable; urgency=medium . * Initial release (Closes: #1056953) Checksums-Sha1: 29b818c45b715022826fcae1b420ceed30763e82 1984 libargparse_3.0-1.dsc cc2cb74e9d8d57034dccda36a6e7808630967f6b 116171 libargparse_3.0.orig.tar.gz 9732e19520c6cb96855e8fef69c0f2b18a3cfcb6 2112 libargparse_3.0-1.debian.tar.xz 499b68905fa943c31bff72306732e9003bf6 17872 libargparse-dev_3.0-1_amd64.deb 6be252a64a87a30a24cb932b78f43263bd7f0ea0 6816 libargparse_3.0-1_amd64.buildinfo Checksums-Sha256: b3f874477b57086011c84a8c59d3c7526ef811714900f6a57c1430e47daec89e 1984 libargparse_3.0-1.dsc ba7b465759bb01069d57302855eaf4d1f7d677f21ad7b0b00b92939645c30f47 116171 libargparse_3.0.orig.tar.gz 8edfd9eb31d3b2712f973ab54e1f144137372d432466ef112b449cab524b40ff 2112 libargparse_3.0-1.debian.tar.xz 563751f0a0f87e161af17bf82eab934277c45fb5198ae4e7bf72d8e89479b124 17872 libargparse-dev_3.0-1_amd64.deb 452df693a9d9f6284c05f52ef51edccc34ec10ab9c93f3363a0cae0773b1b912 6816 libargparse_3.0-1_amd64.buildinfo Files: 607198ea352915cd944cc5222820d568 1984 libdevel optional libargparse_3.0-1.dsc cda6aa415ca13319d3975ebaa75750a5 116171 libdevel optional libargparse_3.0.orig.tar.gz fd3d8682f2a1906a1603f9c6a64cb8c2 2112 libdevel optional libargparse_3.0-1.debian.tar.xz 18c4aea06f2f013655047d16ef7c5d5d 17872 libdevel optional libargparse-dev_3.0-1_amd64.deb 6a780562c68a9bcd72ba579c701ea1c2 6816 libdevel optional libargparse_3.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1059495: src:corectrl: unsatisfied build dependency in testing: libtrompeloeil-cpp-dev
Source: corectrl Version: 1.3.8+ds-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059494: src:python-refurb: unsatisfied build dependency in testing: python3-fastapi
Source: python-refurb Version: 1.24.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059493: src:python-docx: unsatisfied build dependency in testing: python3-behave
Source: python-docx Version: 1.1.0+dfsg-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059487: src:django-oauth-toolkit: fails to migrate to testing for too long: uploader built arch:all binaries
Source: django-oauth-toolkit Version: 2.3.0-1 Severity: serious Control: close -1 2.3.0-2 Tags: sid trixie pending 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 30 days as having a Release Critical bug in testing [1]. Your package src:django-oauth-toolkit has been trying to migrate for 34 days [2]. Hence, I am filing this bug. 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 trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=django-oauth-toolkit OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:django-oauth-toolkit: fails to migrate to testing for too long: uploader built arch:all binaries
Processing control commands: > close -1 2.3.0-2 Bug #1059487 [src:django-oauth-toolkit] src:django-oauth-toolkit: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions django-oauth-toolkit/2.3.0-2. Bug #1059487 [src:django-oauth-toolkit] src:django-oauth-toolkit: fails to migrate to testing for too long: uploader built arch:all binaries Marked Bug as done -- 1059487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059484: rasdaemon: autopkgtest failure: cannot access '/var/lib/rasdaemon/ras-mc_event.db'
Source: rasdaemon Version: 0.8.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package rasdaemon, 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. 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=rasdaemon https://ci.debian.net/data/autopkgtest/testing/amd64/r/rasdaemon/40156577/log.gz 34s ls: cannot access '/var/lib/rasdaemon/ras-mc_event.db': No such file or directory 34s autopkgtest [11:52:08]: test ras-mc-ctl OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059028: marked as done (elogind FTBFS with nocheck: missing mount dependency)
Your message dated Tue, 26 Dec 2023 18:04:15 + with message-id and subject line Bug#1059028: fixed in elogind 252.9-1debian3 has caused the Debian Bug report #1059028, regarding elogind FTBFS with nocheck: missing mount dependency 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.) -- 1059028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: elogind Version: 252.9-1debian2 Severity: serious Tags: ftbfs trixie sid elogind fails to build from source with the nocheck build profile. Note that since trixie such a failure is considered release critical by the release team. The relevant part of the build log is: | Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 | Run-time dependency libcap found: YES 2.66 | Did not find CMake 'cmake' | Found CMake: NO | Run-time dependency mount found: NO (tried pkgconfig) | | ../meson.build:1335:11: ERROR: Dependency "mount" not found, tried pkgconfig | | A full log can be found at /<>/build/meson-logs/meson-log.txt | cd build && tail -v -n \+0 meson-logs/meson-log.txt I suspect that libmount-dev is pulled via some dependency that happens to be tagged and therefore a regular build succeeds. You should add an explicit build dependency on libmount-dev anyhow. Helmut --- End Message --- --- Begin Message --- Source: elogind Source-Version: 252.9-1debian3 Done: Mark Hindley We believe that the bug you reported is fixed in the latest version of elogind, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Hindley (supplier of updated elogind 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, 26 Dec 2023 17:26:30 + Source: elogind Architecture: source Version: 252.9-1debian3 Distribution: unstable Urgency: medium Maintainer: Debian Ecosystem Init Diversity Team Changed-By: Mark Hindley Closes: 1059028 Changes: elogind (252.9-1debian3) unstable; urgency=medium . * d/control: add Build-Depends: libmount-dev to fix nocheck build. (Closes: #1059028) Checksums-Sha1: 7ed1270eaa5660b8e0712cf2171eeddb2d8bfe9f 2667 elogind_252.9-1debian3.dsc de72ed3a6466902f92e865a6daa3fa405831817b 14424 elogind_252.9-1debian3.debian.tar.xz 3d34285a3a1d892f0f9b6d3bbbee22832e2bc26e 10323 elogind_252.9-1debian3_amd64.buildinfo Checksums-Sha256: 2b345c06927dbdfda8c4e9c7a38598fa0ac0ee14055687d46ca6f4b0426ed1f7 2667 elogind_252.9-1debian3.dsc db29643db95cca0095d6629a9c2c7b15126d7a3e5b1b495f3c528d1f52bd6c21 14424 elogind_252.9-1debian3.debian.tar.xz 96ab9dbd142a07ace13774abdaee9e1b02d4f332a30a12c1c91ae43d619b0871 10323 elogind_252.9-1debian3_amd64.buildinfo Files: 27ebab607d8e7366baf2ed0da59dc2ba 2667 admin optional elogind_252.9-1debian3.dsc e617e9d0365bed3bd8701ffa1278f8ff 14424 admin optional elogind_252.9-1debian3.debian.tar.xz 6222b7d4dfa955d8f18581cf2b4fbefa 10323 admin optional elogind_252.9-1debian3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUGwVpCsK9aCoVCPu0opFvzKH1kkFAmWLEMoACgkQ0opFvzKH 1kmFJBAAltaAMfi+7Udb1uDOnxoITzUiIXM6nrvBeDAyU1KoLCYmbB8PudredHIp po+hFwKc7f5CDBO3VyVSu0juMw7wSYdKsrvONPN39GZLGMQ1WesOZyTdwEQk3JbV IIuX5WVl2eiKhq7DWzEzQwT5N02/V+vJ9y61HScIMSmGFnJTToYVZRSfstWsOz8+ ZdrkYj/kTDHc1zfcZC5isurSb7TUogdeaJOF01pe43cGl2hD+wxaCPh8/QgW3hLs 7Z5mY4aSvQR60xRb2tyy/Kc/fwYNvi8Rhm1W4eAxjY5FzhRUp6+QGRrXeC0gw9kT pC1nUD3dfu04s6BiGDsZRYx9+XuCOKfKBuUGPtOyPcqinLBLRmObflc2GB9gIMfn GnSUv/GG7UHhHAuoXIaDP8Y384h0jVQQO0AtL51+oApyFymDBG8q6w4WMJQv5GyF NM6ce9CIdGJCHs77LBz2vKmkDVk49wWsHmel63ysHjPpIHD7+jksINGoNNZtfP5j RIDRbNq2zW4xwvcqjw6L9xeeg9a0+yjPd94UecJfX8hfE/GrXSBWYSetng0E6aqQ aF756DR/HGFLsJpXPPIHFr0XtjEQMhKBcH7FV+hRC4b8lArRZJcYO5nZeiL3AsTH qw0YBHPSBv8meDIcUZiOk4ucaiwPz/Ex6EDKF0yEM7jx/4LtPvM= =bdUC -END PGP SIGNATURE End Message ---
Bug#1054799: marked as done (razercfg: FTBFS: dh_install: error: missing files, aborting)
Your message dated Tue, 26 Dec 2023 17:34:17 +
with message-id
and subject line Bug#1054799: fixed in razercfg 0.42+ds-4
has caused the Debian Bug report #1054799,
regarding razercfg: FTBFS: dh_install: error: missing files, aborting
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.)
--
1054799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: razercfg
Version: 0.42+ds-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install --exclude=librazer.a
> install -m0755 -d debian/razercfg//etc
> cp --reflink=auto -a ./razer.conf debian/razercfg//etc/
> install -m0755 -d debian/razercfg//etc/pm/sleep.d
> cp --reflink=auto -a debian/tmp/etc/pm/sleep.d/50-razer
> debian/razercfg//etc/pm/sleep.d/
> install -m0755 -d debian/razercfg//lib/systemd
> cd 'debian/tmp/lib/systemd/system/..' && find 'system' ! \( -regex
> .\*librazer\\.a.\* \) \( -type f -or -type l \) -print0 | LC_ALL=C sort -z |
> xargs -0 -I {} cp --reflink=auto --parents -dp {}
> /<>/debian/razercfg//lib/systemd/
> cd 'debian/tmp/lib/systemd/system/..' && find 'system' ! \( -regex
> .\*librazer\\.a.\* \) \( -type d -and -empty \) -print0 | LC_ALL=C sort -z |
> xargs -0 -I {} cp --reflink=auto --parents -a {}
> /<>/debian/razercfg//lib/systemd/
> install -m0755 -d debian/razercfg//lib
> cd 'debian/tmp/lib/udev/..' && find 'udev' ! \( -regex
> .\*librazer\\.a.\* \) \( -type f -or -type l \) -print0 | LC_ALL=C sort -z |
> xargs -0 -I {} cp --reflink=auto --parents -dp {}
> /<>/debian/razercfg//lib/
> cd 'debian/tmp/lib/udev/..' && find 'udev' ! \( -regex
> .\*librazer\\.a.\* \) \( -type d -and -empty \) -print0 | LC_ALL=C sort -z |
> xargs -0 -I {} cp --reflink=auto --parents -a {}
> /<>/debian/razercfg//lib/
> dh_install: warning: Cannot find (any matches for)
> "usr/lib/python3*/site-packages/*" (tried in ., debian/tmp)
>
> dh_install: warning: razercfg missing files: usr/lib/python3*/site-packages/*
> dh_install: warning: Cannot find (any matches for) "usr/bin/razercfg" (tried
> in ., debian/tmp)
>
> dh_install: warning: razercfg missing files: usr/bin/razercfg
> dh_install: warning: Cannot find (any matches for) "usr/bin/qrazercfg" (tried
> in ., debian/tmp)
>
> dh_install: warning: qrazercfg missing files: usr/bin/qrazercfg
> dh_install: warning: Cannot find (any matches for) "usr/bin/qrazercfg-applet"
> (tried in ., debian/tmp)
>
> dh_install: warning: qrazercfg-applet missing files: usr/bin/qrazercfg-applet
> dh_install: error: missing files, aborting
> make[1]: *** [debian/rules:16: override_dh_install] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/razercfg_0.42+ds-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: razercfg
Source-Version: 0.42+ds-4
Done: Luca Boccassi
We believe that the bug you reported is fixed in the latest version of
razercfg, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luca Boccassi (supplier of updated razercfg 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
Processed: src:vectorscan: fails to migrate to testing for too long: autopkgtest regression on ppc64el
Processing control commands: > close -1 5.4.11-1 Bug #1059478 [src:vectorscan] src:vectorscan: fails to migrate to testing for too long: autopkgtest regression on ppc64el Marked as fixed in versions vectorscan/5.4.11-1. Bug #1059478 [src:vectorscan] src:vectorscan: fails to migrate to testing for too long: autopkgtest regression on ppc64el Marked Bug as done -- 1059478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059478: src:vectorscan: fails to migrate to testing for too long: autopkgtest regression on ppc64el
Source: vectorscan Version: 5.4.10.1-1 Severity: serious Control: close -1 5.4.11-1 Tags: sid trixie 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 30 days as having a Release Critical bug in testing [1]. Your package src:vectorscan has been trying to migrate for 35 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest on ppc64el. https://ci.debian.net/packages/v/vectorscan/testing/ppc64el/41340940/ """ 40s build: OK 40s Illegal instruction """ 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 trixie, 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/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=vectorscan OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058817: marked as done (picom: depends on obsolete pcre3 library)
Your message dated Tue, 26 Dec 2023 16:19:12 + with message-id and subject line Bug#1058817: fixed in picom 10.2-2 has caused the Debian Bug report #1058817, regarding picom: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: picom Version: 10.2-1 Severity: serious Tags: sid trixie fixed-upstream User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, During the mass bug filing for the pcre3->pcre2 transition [*], this package was left out somehow. I am filing this (edited copy) post-factum. Fortunately this bug has been fixed upstream. [*] https://release.debian.org/transitions/html/pcre3-to-pcre2.html Your package still depends on the old, obsolete PCRE3 libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, we would like to remove the pcre3 libraries from Debian. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html --- End Message --- --- Begin Message --- Source: picom Source-Version: 10.2-2 Done: Nikos Tsipinakis We believe that the bug you reported is fixed in the latest version of picom, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nikos Tsipinakis (supplier of updated picom 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, 26 Dec 2023 16:52:00 +0100 Source: picom Architecture: source Version: 10.2-2 Distribution: unstable Urgency: medium Maintainer: Nikos Tsipinakis Changed-By: Nikos Tsipinakis Closes: 1040988 1058817 Changes: picom (10.2-2) unstable; urgency=medium . * Remove deprecated pcre3 (Closes: #1058817) * Fix infinite loop with GNOME (Closes: #1040988) Checksums-Sha1: a16dbdfd7ef1be1a4645574e952c78edfa842a11 2251 picom_10.2-2.dsc 42b931d1696c78c9a9dc6c6c6e385995a3f9f091 6028 picom_10.2-2.debian.tar.xz 41263319914859bd8d33c64a7a7089663a27b6f4 7471 picom_10.2-2_source.buildinfo Checksums-Sha256: 664ad6f08b81ed48872840bf676ebfec23fcb8c72eebfc5b2c8d7c364f7a5251 2251 picom_10.2-2.dsc aa2946e81f71cba71f3ed695d251ee1f620a0d37ea13f1e4066aad2887e08b77 6028 picom_10.2-2.debian.tar.xz e7b0a64962460ebbbac62e7ae3b684af2a8dbe7759c12927dead843c10982c28 7471 picom_10.2-2_source.buildinfo Files: 54b7c560fa7ada161baf4833639cb0c8 2251 x11 optional picom_10.2-2.dsc 4c6bf366efe1300e828730747cb76650 6028 x11 optional picom_10.2-2.debian.tar.xz 6db551d89258f86016ac8ca32299dbee 7471 x11 optional picom_10.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEye1RZ5B4Szxh/YOSqhW2JKn4YZkFAmWK9+EVHG5pa29zQHRz aXBpbmFraXMuY29tAAoJEKoVtiSp+GGZVZAP/2udtxsxWgiUBTTjFsNeaXGOAmts evoP/xsCFrvZjNMwgoRmHmG0Sxah83pCTbLgii70qjztL0/HXbz+j6rO3ga8Cc3v wWd7i3HmAHRHHrFPzW/tnVRw6VP/EDhue1j1Ji4Q/WoGfdNBKmlvSq43t7YQpYED oesk8M70a9BHR1Dp6P/lrysqYxeSInLsPOjsP4qqXpOcvhYHujc+7gk+znzcHhZM sO3FXkOltQibuTPaxpK2T89G2TzpcfvUjbvEtE3cgkiNzd7iE89mBWu2q44ntVwe fsQOVdtzq2cWple4Mi4xRbfum1mI4eDiuJMX/mIDxK9cjLkZ4UtA/3oCAuC4o3Vj vn3UAx1WnpLccZB3bp1LqqrdanmSs2UWpZHW8YXBLeBDMWjKyGL80O9NSiz4W0fq mAmVK91Rv/RM3mD4rkq6lUALVJHM1qwIafIHyKlDtbsoLKjCAe8/GqBhL0sq7CQB wmgiG3rXbdWanrZtaL0WcAbQq4umaNDZxbi2MgyLxQPeH5GodQ6/Lh7eXPgcJWPG VX3/U6XDFpC2FxIFxx4J74lFGMQCHTENybhrNBhjq+SwiGdn4JMmOaeFxoiouSp0 gRXJL/XSrvnmCMOVG6tOV06i1ToL24Nappz5Bq/8aubrwFps4EQDsE8YMo3VRxTK A+ErJOAPylPUIypw =EfH2 -END PGP SIGNATURE End Message ---
Bug#1040988: marked as done (Clashes with existing composite manager)
Your message dated Tue, 26 Dec 2023 16:19:12 + with message-id and subject line Bug#1040988: fixed in picom 10.2-2 has caused the Debian Bug report #1040988, regarding Clashes with existing composite manager 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.) -- 1040988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: picom Version: 10.2-1 Severity: serious picom adds an autostart file which makes it automatically start on session login. Today I noticed that journald/rsyslog ran while and my logs were flodded with the following messages (I was logged into a GNOME session at that time): Jul 13 19:18:11 pluto picom.desktop[2236]: [ 13.07.2023 19:18:11.510 redirect_start FATAL ERROR ] Another composite manager is already running (and does not handle _NET_WM_CM_Sn correctly) Jul 13 19:18:11 pluto picom.desktop[2236]: [ 13.07.2023 19:18:11.510 redirect_start FATAL ERROR ] Another composite manager is already running (and does not handle _NET_WM_CM_Sn correctly) Jul 13 19:18:11 pluto picom.desktop[2236]: [ 13.07.2023 19:18:11.510 redirect_start FATAL ERROR ] Another composite manager is already running (and does not handle _NET_WM_CM_Sn correctly) Within minutes, my disk was filled with hundreds of megabytes of log data (/var/log/syslog was over 1GB), before I killed the rogue picom process. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 picom depends on: ii libc62.37-5 ii libconfig9 1.5-0.4 ii libdbus-1-3 1.14.8-2 ii libegl1 1.6.0-1 pn libev4 ii libgl1 1.6.0-1 ii libpcre3 2:8.39-15 ii libpixman-1-00.42.2-1 ii libx11-6 2:1.8.6-1 ii libx11-xcb1 2:1.8.6-1 ii libxcb-composite01.15-1 ii libxcb-damage0 1.15-1 ii libxcb-glx0 1.15-1 ii libxcb-image00.4.0-2 ii libxcb-present0 1.15-1 ii libxcb-randr01.15-1 ii libxcb-render-util0 0.3.9-1+b1 ii libxcb-render0 1.15-1 ii libxcb-shape01.15-1 ii libxcb-sync1 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb-xinerama0 1.15-1 ii libxcb1 1.15-1 ii python3 3.11.4-5 picom recommends no packages. picom suggests no packages. --- End Message --- --- Begin Message --- Source: picom Source-Version: 10.2-2 Done: Nikos Tsipinakis We believe that the bug you reported is fixed in the latest version of picom, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nikos Tsipinakis (supplier of updated picom 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, 26 Dec 2023 16:52:00 +0100 Source: picom Architecture: source Version: 10.2-2 Distribution: unstable Urgency: medium Maintainer: Nikos Tsipinakis Changed-By: Nikos Tsipinakis Closes: 1040988 1058817 Changes: picom (10.2-2) unstable; urgency=medium . * Remove deprecated pcre3 (Closes: #1058817) * Fix infinite loop with GNOME (Closes: #1040988) Checksums-Sha1: a16dbdfd7ef1be1a4645574e952c78edfa842a11 2251 picom_10.2-2.dsc 42b931d1696c78c9a9dc6c6c6e385995a3f9f091 6028 picom_10.2-2.debian.tar.xz 41263319914859bd8d33c64a7a7089663a27b6f4 7471 picom_10.2-2_source.buildinfo Checksums-Sha256: 664ad6f08b81ed48872840bf676ebfec23fcb8c72eebfc5b2c8d7c364f7a5251 2251 picom_10.2-2.dsc aa2946e81f71cba71f3ed695d251ee1f620a0d37ea13f1e4066aad2887e08b77 6028 picom_10.2-2.debian.tar.xz e7b0a64962460ebbbac62e7ae3b684af2a8dbe7759c12927dead843c10982c28 7471 picom_10.2-2_source.buildinfo Files: 54b7c560fa7ada161baf4833639cb0c8
Processed: src:patool: fails to migrate to testing for too long: new test depends on amd64/i386 only binary
Processing control commands: > close -1 2.0.0-1 Bug #1059477 [src:patool] src:patool: fails to migrate to testing for too long: new test depends on amd64/i386 only binary Marked as fixed in versions patool/2.0.0-1. Bug #1059477 [src:patool] src:patool: fails to migrate to testing for too long: new test depends on amd64/i386 only binary Marked Bug as done -- 1059477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059477: src:patool: fails to migrate to testing for too long: new test depends on amd64/i386 only binary
Source: patool Version: 1.12-5 Severity: serious Control: close -1 2.0.0-1 Tags: sid trixie 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 30 days as having a Release Critical bug in testing [1]. Your package src:patool has been trying to migrate for 33 days [2]. Hence, I am filing this bug. If I read the history correctly, the version in unstable added a test to the list of autopkgtest which Depends on rar. rar is only available on amd64 and i386, hence the test fails on other architectures to install its dependencies. Non-installability of test dependencies can't really be handled correctly automatically (is the non-installability OK, or actually showing a problem), so you'll have to deal with it. I recommend to add an "Architecture" line to the second test stanza containing amd64 and i386. There is also the option to use the skip-not-installable restriction, but I don't recommend using that (I regret I added that to autopkgtest because too often it hides real problems). On top of that, the upload included the binary, which means that the migration is blocked as we don't allow uploader built binaries in testing, but we can't meaningful binNMU arch:all binaries yet. Normally I would NMU with no-change version, but given the autopkgtest failure, I leave it to you. 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 trixie, 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/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=patool OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058113: marked as done (pytest-qt: FTBFS: RuntimeError: event processed)
Your message dated Tue, 26 Dec 2023 15:50:45 + with message-id and subject line Bug#1058113: fixed in pytest-qt 4.3.1-1 has caused the Debian Bug report #1058113, regarding pytest-qt: FTBFS: RuntimeError: event processed 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.) -- 1058113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-qt Version: 4.2.0+repack-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/docs' > sphinx-build -b html -d _build/doctrees . _build/html > Running Sphinx v7.2.6 > loading pickled environment... done > building [mo]: targets for 0 po files that are out of date > writing output... > building [html]: targets for 0 source files that are out of date > updating environment: 0 added, 0 changed, 0 removed > reading sources... > looking for now-outdated files... none found > no targets are out of date. > build succeeded. > > The HTML pages are in _build/html. > > Build finished. The HTML pages are in _build/html. > make[1]: Leaving directory '/<>/docs' >dh_auto_test -O--buildsystem=pybuild > I: pybuild pybuild:314: python3.12 setup.py egg_info -e > /<>/.pybuild/cpython3_3.12_pytestqt/build > /usr/lib/python3/dist-packages/setuptools/__init__.py:84: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > dist.fetch_build_eggs(dist.setup_requires) > WARNING: The wheel package is not available. > running egg_info > creating > /<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info > writing > /<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/PKG-INFO > writing dependency_links to > /<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/dependency_links.txt > writing entry points to > /<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/entry_points.txt > writing requirements to > /<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/requires.txt > writing top-level names to > /<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/top_level.txt > writing manifest file > '/<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/SOURCES.txt' > reading manifest file > '/<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/SOURCES.txt' > adding license file 'LICENSE' > writing manifest file > '/<>/.pybuild/cpython3_3.12_pytestqt/build/pytest_qt.egg-info/SOURCES.txt' > I: pybuild base:310: cd > /<>/.pybuild/cpython3_3.12_pytestqt/build; python3.12 -m pytest > tests > = test session starts > == > platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 > PyQt5 5.15.10 -- Qt runtime 5.15.10 -- Qt compiled 5.15.10 > rootdir: /<> > configfile: setup.cfg > plugins: qt-4.2.0+repack, xvfb-3.0.0 > collected 378 items > > tests/test_basics.py . [ > 11%] > tests/test_exceptions.py ..F [ > 15%] > tests/test_logging.py [ > 24%] > tests/test_modeltest.py [ > 32%] > tests/test_qtbot_pep8_aliases.py ... [ > 35%] > tests/test_qtest_proxies.py .. [ > 39%] > tests/test_screenshot.py . [ > 42%] > tests/test_wait_signal.py .. [ > 55%] > [ > 74%] > ...s [ > 93%] > ...s [ > 98%] > tests/test_wait_until.py .. > [100%] > > === FAILURES > === > __ test_exceptions_dont_leak >
Bug#1058739: marked as done (lyskom-elisp-client: fails to install with Emacs 29: lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack)
Your message dated Tue, 26 Dec 2023 15:35:37 + with message-id and subject line Bug#1058739: fixed in lyskom-elisp-client 0.48+git.20231226.364902c3-1 has caused the Debian Bug report #1058739, regarding lyskom-elisp-client: fails to install with Emacs 29: lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack 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.) -- 1058739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lyskom-elisp-client Version: 0.48+git.20200923.ec349ff4-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up emacs-gtk (1:29.1+1-5) ... update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs (emacs) in auto mode update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) in auto mode Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install lyskom-elisp-client for emacs install/lyskom-elisp-client: Handling install of emacsen flavor emacs install/lyskom-elisp-client: byte-compiling for emacs Please wait... In toplevel form: lyskom-elisp-client.el:1119:2: Warning: defvar `kom-pick-text-no-strategy-alist' docstring wider than 80 characters lyskom-elisp-client.el:3039:2: Warning: defvar `lyskom-text-buttons' docstring wider than 80 characters lyskom-elisp-client.el:4385:2: Warning: defconst `lyskom-server-features' docstring has wrong usage of unescaped single quotes (use \= or different quoting) lyskom-elisp-client.el:6158:2: Warning: `string-make-unibyte' is an obsolete function (as of 26.1); use `encode-coding-string'. lyskom-elisp-client.el:6333:2: Warning: More than one doc string In lyskom-get-menu-string: lyskom-elisp-client.el:6919:2: Warning: docstring has wrong usage of unescaped single quotes (use \= or different quoting) lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack ERROR: install script from lyskom-elisp-client package failed dpkg: error processing package emacs-gtk (--configure): installed emacs-gtk package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of emacs: emacs depends on emacs-gtk (>= 1:27.1) | emacs-pgtk (>= 1:27.1) | emacs-lucid (>= 1:27.1) | emacs-nox (>= 1:27.1); however: Package emacs-gtk is not configured yet. Package emacs-pgtk is not installed. Package emacs-lucid is not installed. Package emacs-nox is not installed. dpkg: error processing package emacs (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of lyskom-elisp-client: lyskom-elisp-client depends on emacs; however: Package emacs is not configured yet. Package emacs-gtk which provides emacs is not configured yet. dpkg: error processing package lyskom-elisp-client (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-13) ... Processing triggers for install-info (7.1-2) ... Errors were encountered while processing: emacs-gtk emacs lyskom-elisp-client cheers, Andreas lyskom-elisp-client_0.48+git.20200923.ec349ff4-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: lyskom-elisp-client Source-Version: 0.48+git.20231226.364902c3-1 Done: Joel Rosdahl We believe that the bug you reported is fixed in the latest version of lyskom-elisp-client, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joel Rosdahl (supplier of updated lyskom-elisp-client 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, 26 Dec 2023 16:05:18 +0100 Source: lyskom-elisp-client
Bug#1056478: marked as done (python-launchpadlib's autopkg tests fail with Python 3.12)
Your message dated Tue, 26 Dec 2023 10:53:48 -0400
with message-id
<3xnqleglfeawyoxrptwbyb24ya4mtiyshusxsb2ic6vn5zxyzx@q2r46knhmyqa>
and subject line Re: Bug#1056478: python-launchpadlib's autopkg tests fail with
Python 3.12
has caused the Debian Bug report #1056478,
regarding python-launchpadlib's autopkg tests fail with Python 3.12
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.)
--
1056478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-launchpadlib
Version: 1.11.0-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-launchpadlib's autopkg tests fail with Python 3.12:
[...]
177s autopkgtest [20:13:00]: test unittests: [---
177s === python3.12 ===
178s = test session starts
==
178s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
178s rootdir: /usr/lib/python3/dist-packages/launchpadlib
178s collected 115 items
178s
178s
../../../usr/lib/python3/dist-packages/launchpadlib/tests/test_credential_store.py
. [ 0%]
178s .FFF..F
[ 10%]
178s
../../../usr/lib/python3/dist-packages/launchpadlib/tests/test_http.py .
[ 11%]
178s .
[ 19%]
178s
../../../usr/lib/python3/dist-packages/launchpadlib/tests/test_launchpad.py
. [ 20%]
178s ...F.
[ 59%]
178s
../../../usr/lib/python3/dist-packages/launchpadlib/testing/tests/test_launchpad.py
. [ 60%]
179s ..
[100%]
179s
179s === FAILURES
===
179s __
TestUnencryptedFileCredentialStore.test_file_only_contains_one_credential
___
179s
179s self =
testMethod=test_file_only_contains_one_credential>
179s
179s def test_file_only_contains_one_credential(self):
179s # A credential file may contain only one credential. If you
179s # write two credentials with different unique IDs to the same
179s # file, the first credential will be overwritten with the
179s # second.
179s credential1 = self.make_credential("consumer key")
179s credential2 = self.make_credential("consumer key2")
179s self.store.save(credential1, "unique key 1")
179s self.store.save(credential1, "unique key 2")
179s > loaded = self.store.load("unique key 1")
179s
179s
/usr/lib/python3/dist-packages/launchpadlib/tests/test_credential_store.py:110:
179s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
179s /usr/lib/python3/dist-packages/launchpadlib/credentials.py:345: in load
179s return self.do_load(unique_key)
179s /usr/lib/python3/dist-packages/launchpadlib/credentials.py:486: in
do_load
179s return Credentials.load_from_path(self.filename)
179s
/usr/lib/python3/dist-packages/lazr/restfulclient/authorize/oauth.py:226:
in load_from_path
179s credentials.load(credentials_file)
179s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
179s
179s self =
179s readable_file = <_io.TextIOWrapper name='/tmp/tmps9udu7rw' mode='r'
encoding='UTF-8'>
179s
179s def load(self, readable_file):
179s """Load credentials from a file-like object.
179s
179s This overrides the consumer and access token given in the
constructor
179s and replaces them with the values read from the file.
179s
179s :param readable_file: A file-like object to read the
credentials from
179s :type readable_file: Any object supporting the file-like
`read()`
179s method
179s """
179s # Attempt to load the access token from the file.
179s parser = SafeConfigParser()
179s > reader = getattr(parser, "read_file", parser.readfp)
179s E AttributeError: 'ConfigParser' object has no attribute
'readfp'. Did you mean: 'read'?
179s
179s
/usr/lib/python3/dist-packages/lazr/restfulclient/authorize/oauth.py:194:
AttributeError
179s TestUnencryptedFileCredentialStore.test_save_and_load
_
179s
179s self =
testMethod=test_save_and_load>
179s
179s def test_save_and_load(self):
179s # Make sure you can save and load credentials to a file.
179s credential = self.make_credential("consumer key")
179s self.store.save(credential, "unique key")
179s > credential2 = self.store.load("unique key")
179s
179s
Bug#1058215: marked as done (foolscap: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)
Your message dated Tue, 26 Dec 2023 14:34:26 +
with message-id
and subject line Bug#1058215: fixed in foolscap 23.11.0-1
has caused the Debian Bug report #1058215,
regarding foolscap: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)
--
1058215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: foolscap
Version: 21.7.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # remove pyc's from testsuite
> find . -name "*.pyc" | xargs rm -f
> rm -rf _trial_temp
> rm -rf build
> rm -rf src/foolscap.egg-info
> dh_auto_clean
> I: pybuild base:310: python3.12 setup.py clean
> /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence
> '\s'
> LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
> File "/<>/setup.py", line 47, in
> "version": versioneer.get_version(),
>
> File "/<>/versioneer.py", line 1480, in get_version
> return get_versions()["version"]
>^^
> File "/<>/versioneer.py", line 1412, in get_versions
> cfg = get_config_from_root(root)
> ^^
> File "/<>/versioneer.py", line 342, in get_config_from_root
> parser = configparser.SafeConfigParser()
> ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'.
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make[1]: *** [debian/rules:24: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/foolscap_21.7.0-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: foolscap
Source-Version: 23.11.0-1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
foolscap, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated foolscap 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, 26 Dec 2023 09:46:11 -0400
Source: foolscap
Architecture: source
Version: 23.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Stefano Rivera
Closes: 1058215
Changes:
foolscap (23.11.0-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
- Supports Python 3.12 (Closes: #1058215)
* Refresh patches.
* Drop patch 0004-Use-getfullargspec-for-Python-3.patch, superseded
upstream.
* Build-Depend on python3-txi2p-tahoe and drop 2001-drop-i2p-tests.patch.
* Bump watch file version to 4.
* Declare Rules-Requires-Root: no.
* Bump Standards-Version to 4.6.2, no changes needed.
* Run the autopkgtest on all supported python 3 versions, outside the source
tree, with trial.
Checksums-Sha1:
Bug#1052037: marked as done (fasttext: Can't be imported on armel)
Your message dated Tue, 26 Dec 2023 14:34:16 + with message-id and subject line Bug#1052037: fixed in fasttext 0.9.2+ds-6 has caused the Debian Bug report #1052037, regarding fasttext: Can't be imported on armel 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.) -- 1052037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-fasttext Version: 0.9.2+ds-4 Severity: serious Found in dateparser autopkgtest logs and confirmed on the armel porterbox: >>> import fasttext_pybind Traceback (most recent call last): File "", line 1, in ImportError: /usr/lib/python3/dist-packages/fasttext_pybind.cpython-311-arm- linux-gnueabi.so: undefined symbol: __atomic_load_8 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU:ru Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-fasttext depends on: ii libc6 2.37-8 ii libgcc-s1 13.2.0-3 ii libstdc++6 13.2.0-3 ii python33.11.4-5+b1 ii python3-numpy 1:1.24.2-1 ii python3-pkg-resources 68.1.2-1 pn python3-pybind11 python3-fasttext recommends no packages. python3-fasttext suggests no packages. --- End Message --- --- Begin Message --- Source: fasttext Source-Version: 0.9.2+ds-6 Done: Kentaro Hayashi We believe that the bug you reported is fixed in the latest version of fasttext, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kentaro Hayashi (supplier of updated fasttext 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, 26 Dec 2023 22:09:23 +0900 Source: fasttext Architecture: source Version: 0.9.2+ds-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kentaro Hayashi Closes: 1052037 Changes: fasttext (0.9.2+ds-6) unstable; urgency=medium . [ Bastian Germann ] * Drop unnecessary B-D quilt . [ Kentaro Hayashi ] * debian/patches/explicitly-link-libatomic.patch - Fix import error on armel (Closes: #1052037) Checksums-Sha1: bdabab09b56a56ca08d376de03665b2c5b4763f5 2359 fasttext_0.9.2+ds-6.dsc d8c106aa299ff52ff8eb416be2b226714f1b1193 8468 fasttext_0.9.2+ds-6.debian.tar.xz b8a2d851b3a3d4a6c23731c4b0c76120d4cbce43 9803 fasttext_0.9.2+ds-6_amd64.buildinfo Checksums-Sha256: b1b061c1445deb3d73e702644b591888255ab47fa5027647af6e9b31168975f3 2359 fasttext_0.9.2+ds-6.dsc 22ca309b1de5aadc75fb75287613522dbbdde2c209525719f105f82382ddc965 8468 fasttext_0.9.2+ds-6.debian.tar.xz 13884dce9c7fbf14d1040d1b2d69f76b5fa9e58f90e4255003a1b465d3705468 9803 fasttext_0.9.2+ds-6_amd64.buildinfo Files: 753d465037f995572f3cbc6ddbd4c250 2359 science optional fasttext_0.9.2+ds-6.dsc 4ecd5b2803127d2837368f7509e25288 8468 science optional fasttext_0.9.2+ds-6.debian.tar.xz 34347fd1b2ac6ba116a5746975b1b8b3 9803 science optional fasttext_0.9.2+ds-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEcZ6y2T2+nE0h+6Bk9/t1xWbtIOMFAmWK2dAACgkQ9/t1xWbt IOMRRhAAwlTgt/bSDHFCwo6gWFhaeYEmnZi991Hbidj8Wh9zEJrI3VeL/72gLO1A 8PuXeEpj6p+ynzgKnfziW9O/iCrxtChSsshbmHI4MYKeRITPcQJWEdYOBBCSu7I3 VQ4KSDkBY4SMsmS115fCK/pFdgOUigPwOXHxxxdTvo0n23DEor+ZBJ7XbVczHMfk vny1YMwQuj8xgh9JSlxCo/Rai4F2SLjIv68hz0O5y0AlPKqpcssJ2TJ0U6nUxOQG mnPa1kz4yRyumjbl6iFBrOwHAfroJ6DAaY5zLChn/Lo6ez0hra2nqFIDdjXYNp6H M/q4i7BUHP16ayB7nObkQjzdUrrdFhlvIatgvlozRvpPkgaaAbQb2pp2w1JwAhY0 DnZ0Vh5mGAQJdd0wl8s6zL5/s6AGJgn2h3Z3XvAzrIGLzvVuwucw43eF47fb2ELn HqmRQ4LozYPXeAv/GaBaMrrOpRlv9rLdRQ8HvqoeIEVnuf5itIAeiHPWSrRB+FN8 8WHVTIY9n5uUNH2SdKuWn7WRHb43qvJbctbP9FDjS2KRgPLtjzNvTfnu+uKUNmxr
Processed: bug 1058245 is forwarded to https://github.com/flatpak/libportal/issues/136
Processing commands for cont...@bugs.debian.org: > forwarded 1058245 https://github.com/flatpak/libportal/issues/136 Bug #1058245 [src:libportal] libportal: FTBFS: dh_auto_test regression with python3-dbusmock (>= 0.30.0-2) Set Bug forwarded-to-address to 'https://github.com/flatpak/libportal/issues/136'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059245: gdm3: GDM3 fails to start on Wayland, maybe due to org.freedesktop.systemd1 failing to activate
Package: gdm3 Version: 45.0.1-2 Followup-For: Bug #1059245 Thanks for the reply, Simon. I have done some more investigation, comparing to a freshly installed VM, and see this difference in the debug logs of gdm-wayland-session, which seems to be what misbehaves in my previous logs. $ sudo journalctl -t gdm-wayland-session Dec 26 14:01:56 desktop gdm-wayland-session[1469]: Gdm: Enabling debugging Dec 26 14:01:56 desktop gdm-wayland-session[1469]: Gdm: Running session message bus Dec 26 14:01:56 desktop gdm-wayland-session[1469]: GLib: g_unix_open_pipe() called with FD_CLOEXEC; please migrate to using O_CLOEXEC instead Dec 26 14:01:56 desktop gdm-wayland-session[1469]: GLib: g_unix_open_pipe() called with FD_CLOEXEC; please migrate to using O_CLOEXEC instead Dec 26 14:01:56 desktop gdm-wayland-session[1469]: Gdm: could not fetch environment: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Dec 26 14:01:56 desktop gdm-wayland-session[1469]: Gdm: Running wayland session Dec 26 14:01:56 desktop gdm-wayland-session[1469]: GLib: g_unix_open_pipe() called with FD_CLOEXEC; please migrate to using O_CLOEXEC instead Dec 26 14:01:56 desktop gdm-wayland-session[1469]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) Dec 26 14:01:56 desktop gdm-wayland-session[1469]: Gdm: Could not register display: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Aucun affichage disponible This compared to a healthier test VM $ sudo journalctl -t gdm-wayland-session Dec 26 07:29:00 test-vm gdm-wayland-session[2232]: Gdm: Enabling debugging Dec 26 07:29:00 test-vm gdm-wayland-session[2232]: Gdm: Running session message bus Dec 26 07:29:00 test-vm gdm-wayland-session[2232]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) Dec 26 07:29:00 test-vm gdm-wayland-session[2232]: Gdm: session message bus already running, not starting another one Dec 26 07:29:00 test-vm gdm-wayland-session[2232]: Gdm: Running wayland session Dec 26 07:29:00 test-vm gdm-wayland-session[2232]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) Dec 26 07:29:00 test-vm gdm-wayland-session[2232]: Gdm: gdm-wayland-session: Session will register itself So the error seems to be that “Aucun affichange disponible” (No display available), so this would confirm the permission issue somewhere. I indeed can't see a running Xwayland on the impacted system. -- System Information: Debian Release: 12.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-15-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=en_AU (charmap=UTF-8) (ignored: LC_ALL set to en_AU.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 gdm3 depends on: ii accountsservice 22.08.8-6 ii adduser 3.134 ii dbus [default-dbus-system-bus]1.14.10-1~deb12u1 ii dbus-bin 1.14.10-1~deb12u1 ii dbus-daemon 1.14.10-1~deb12u1 ii dconf-cli 0.40.0-4 ii dconf-gsettings-backend 0.40.0-4 ii debconf [debconf-2.0] 1.5.82 ii gir1.2-gdm-1.045.0.1-2 ii gnome-session [x-session-manager] 43.0-1+deb12u1 ii gnome-session-bin 43.0-1+deb12u1 ii gnome-session-common 43.0-1+deb12u1 ii gnome-settings-daemon 43.0-4 ii gnome-shell 43.9-0+deb12u1 ii gnome-terminal [x-terminal-emulator] 3.46.8-1 ii gsettings-desktop-schemas 43.0-1 ii libaccountsservice0 22.08.8-6 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9+deb12u3 ii libcanberra-gtk3-00.30-10 ii libcanberra0 0.30-10 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgdm1 45.0.1-2 ii libglib2.0-0 2.78.3-1 ii libglib2.0-bin2.78.3-1 ii libgtk-3-03.24.38-2~deb12u1 ii libgudev-1.0-0237-2 ii libkeyutils1 1.6.3-2 ii libpam-modules1.5.2-6+deb12u1 ii libpam-runtime1.5.2-6+deb12u1 ii libpam-systemd [logind] 252.19-1~deb12u1 ii libpam0g 1.5.2-6+deb12u1 ii librsvg2-common 2.54.7+dfsg-1~deb12u1 ii libselinux1 3.4-1+b6 ii libsystemd0
Bug#1058739: lyskom-elisp-client: fails to install with Emacs 29: lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack
This looks like an Emacs bug. Reduced reproducer: $ cat repro.el (defsubst bar (a b) nil) (defun foo () (bar 1 2 3 4)) $ emacs -Q --batch -f batch-byte-compile repro.el In toplevel form: repro.el:2:2: Error: Optimizer error: too much on the stack I'll see if I can make some workaround. -- Joel
Bug#1059467: python-dbusmock: new version 0.30.1-1 causes upower's autopkgtest to fail
Source: python-dbusmock Version: 0.30.1-1 Severity: serious Affects: upower Hi, Not sure whether it was a legitimate change and upower's tests need an update, or if it is a new bug, but 0.30.1-1 causes src:upower autopkgtest to fail and stops migration of a bunch of unrelated packages from unstable to testing as debci bundles new packages together when testing for regressions, and everything is held back. You can see the first failure in upower when python-dbusmock was uploaded, without any other new packages being in the same test, on 2023-12-24: https://ci.debian.net/packages/u/upower/testing/amd64/ -- Kind regards, Luca Boccassi
Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)
On 2023-12-26 12:31, Drew Parsons wrote: ... It's not just adios2 and sundials though. openmpi's own arm64 tests are failing on debci with a reference to x86_64-linux-gnu ... openmpi's compile_run_mpif90 test doesn't use pkgconfig anyway. It builds directly with mpif90. Could the problem be inside the mpif90.openmpi binary? That would be strange though. arm64's mpif90.openmpi oughtn't be referring to x86_64 any more than the pkgconfig file. I can manually reproduce the error trivially on an arm64 chroot (amdahl.debian.org). Copying hello.f90 from openmpi's debian/tests and manually running mpif90 -o hello hello.f90 reproduces the error reference to the x86_64 include path on the arm64 machine. `mpif90.openmpi -print-search-dirs` only shows aarch64 paths though.
Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)
On 2023-12-26 11:00, Alastair McKinstry wrote: On 24/12/2023 10:50, Drew Parsons wrote: reopen 1058876 block 1058944 by 1058876 thanks Alas, the fix in openmpi 4.1.6-3 for the include path to the openmpi fortran modules has hardcoded x86_64-linux-gnu This is preventing builds and tests on other architectures, e.g. rebuilding sundials for the petsc transition. I think openmpi's debian/tests will also need Depends: pkg-config for the new compile_run_cc_pkgconfig test. The problem appears to be the heuristics in upstream/FindMPI.cmake in adios2 (and sundials). It happens in sid tests but not my arm64 devel environment. Debugging slowly. It's not just adios2 and sundials though. openmpi's own arm64 tests are failing on debci with a reference to x86_64-linux-gnu e.g. 79s Setting up libopenmpi-dev:arm64 (4.1.6-3) ... 79s update-alternatives: using /usr/lib/aarch64-linux-gnu/openmpi/include to provide /usr/include/aarch64-linux-gnu/mpi (mpi-aarch64-linux-gnu) in auto mode 79s Setting up autopkgtest-satdep (0) ... 79s Processing triggers for libc-bin (2.37-12) ... 83s (Reading database ... 17753 files and directories currently installed.) 83s Removing autopkgtest-satdep (0) ... 86s autopkgtest [03:14:37]: test compile_run_mpif90: [--- 86s f951: Warning: Nonexistent include directory ‘/usr/include/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi’ [-Wmissing-include-dirs] 86s hello.f90:3:11: 86s 86s 3 | use mpi 86s | 1 86s Fatal Error: Cannot open module file ‘mpi.mod’ for reading at (1): No such file or directory It's a strange error to be sure. From that error message, I thought x86_64-linux-gnu might have gotten hardcoded into the include path in ompi-f90.pc for arm64. But downloading libopenmpi-dev_4.1.6-3_arm64.deb and inspecting manually, I can see that arm64's ompi-f90.pc contains -I/usr/include/aarch64-linux-gnu/fortran/gfortran-mod-15/openmpi which would be the correct path. I unpacked libopenmpi-dev_4.1.6-3_arm64.deb manually, but I can't find any reference to include/x86_64 inside its files. openmpi's compile_run_mpif90 test doesn't use pkgconfig anyway. It builds directly with mpif90. Could the problem be inside the mpif90.openmpi binary? That would be strange though. arm64's mpif90.openmpi oughtn't be referring to x86_64 any more than the pkgconfig file. Best of luck with debugging. Drew
Bug#1059465: llvm-toolchain-16: FTBFS on mips64el:
Source: llvm-toolchain-16
Version: 1:16.0.6-19
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-16=mips64el=1%3A16.0.6-19=1702901352=0
llvm-lit: /<>/llvm/utils/lit/lit/llvm/config.py:459: note: using
wasm-ld: /<>/build-llvm/tools/clang/stage2-bins/bin/wasm-ld
-- Testing: 45660 tests, 4 workers --
Testing:
FAIL: LLVM :: Analysis/CostModel/ARM/add-cast-vect.ll (258 of 45660)
TEST 'LLVM :: Analysis/CostModel/ARM/add-cast-vect.ll'
FAILED
Script:
--
: 'RUN: at line 1';
/<>/build-llvm/tools/clang/stage2-bins/bin/opt <
/<>/llvm/test/Analysis/CostModel/ARM/add-cast-vect.ll
-passes="print" 2>&1 -disable-output -mtriple=armv7-linux-gnueabihf
-mcpu=cortex-a9 |
/<>/build-llvm/tools/clang/stage2-bins/bin/FileCheck
--check-prefix=COST
/<>/llvm/test/Analysis/CostModel/ARM/add-cast-vect.ll
--
Exit Code: 1
Command Output (stderr):
--
/<>/llvm/test/Analysis/CostModel/ARM/add-cast-vect.ll:24:9: error:
COST: expected string not found in input
; COST: cost of 1 for instruction: {{.*}} add <4 x i32>
^
:1:62: note: scanning from here
Printing analysis 'Cost Model Analysis' for function 'direct':
^
:4:32: note: possible intended match here
Cost Model: Found an estimated cost of 4 for instruction: %r3 = add <4 x i32>
%v0, %v1
Cheers
--
Sebastian Ramacher
Bug#1058232: marked as done (pytest-httpbin: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Tue, 26 Dec 2023 10:50:24 + with message-id and subject line Bug#1058232: fixed in pytest-httpbin 2.0.0-1 has caused the Debian Bug report #1058232, regarding pytest-httpbin: FTBFS: ModuleNotFoundError: No module named 'imp' 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.) -- 1058232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-httpbin Version: 1.0.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie 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_install > I: pybuild base:310: /usr/bin/python3.12 setup.py install --root > /<>/debian/python3-pytest-httpbin > running install > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running build > running build_py > running egg_info > writing pytest_httpbin.egg-info/PKG-INFO > writing dependency_links to pytest_httpbin.egg-info/dependency_links.txt > writing entry points to pytest_httpbin.egg-info/entry_points.txt > writing requirements to pytest_httpbin.egg-info/requires.txt > writing top-level names to pytest_httpbin.egg-info/top_level.txt > reading manifest file 'pytest_httpbin.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > writing manifest file 'pytest_httpbin.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: > Package 'pytest_httpbin.certs' is absent from the `packages` configuration. > !! > > > > > # Package would be ignored # > > Python recognizes 'pytest_httpbin.certs' as an importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'pytest_httpbin.certs' is explicitly > added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'pytest_httpbin.certs' to be distributed and are > already explicitly excluding 'pytest_httpbin.certs' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > > > !! > check.warn(importable) > running install_lib > creating /<>/debian/python3-pytest-httpbin/usr > creating /<>/debian/python3-pytest-httpbin/usr/lib > creating /<>/debian/python3-pytest-httpbin/usr/lib/python3.12 > creating > /<>/debian/python3-pytest-httpbin/usr/lib/python3.12/dist-packages > creating > /<>/debian/python3-pytest-httpbin/usr/lib/python3.12/dist-packages/pytest_httpbin > copying >
Bug#1056803: marked as done (grpc: ftbfs with cython 3.0.x)
Your message dated Tue, 26 Dec 2023 10:49:58 + with message-id and subject line Bug#1056803: fixed in grpc 1.51.1-4 has caused the Debian Bug report #1056803, regarding grpc: ftbfs with cython 3.0.x 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.) -- 1056803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:grpc Version: 1.51.1-3 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: grpc Source-Version: 1.51.1-4 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of grpc, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated grpc 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, 26 Dec 2023 07:49:37 +0100 Source: grpc Architecture: source Version: 1.51.1-4 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1056803 Changes: grpc (1.51.1-4) unstable; urgency=medium . [ Pirate Praveen ] * Update minimum version of googletest to 1.12~. * Add libgrpc22 to Breaks/Replaces. . [ Bas Couwenberg ] * Switch to cython3-legacy (closes: #1056803). Checksums-Sha1: 9bd630d3ad13d9c604a5ecb1935395ebfbf5f048 2829 grpc_1.51.1-4.dsc 4ab7b1a77a36ea254041d952fa61deec2e1c03ba 20788 grpc_1.51.1-4.debian.tar.xz Checksums-Sha256: 414df1f7370c6d9375bf09d031840a13b44b5db20653d18edcff8a8dc93bfa81 2829 grpc_1.51.1-4.dsc 915b756f90a5c33c3d6a6bdb3f6cb1f28c31bf1d8db75af9410b9c2fa34f15e5 20788 grpc_1.51.1-4.debian.tar.xz Files: 3faa42bbe15fb740befc816e007f9a47 2829 libs optional grpc_1.51.1-4.dsc dcf3747e91030fe00cc09adf801c204c 20788 libs optional grpc_1.51.1-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmWKqv8ACgkQ3OMQ54ZM yL86rg//eCZ21G+qygv9wDltB9Sp5XKRYsp/AIYL7kONuRUlDqdgNQYr3khVrH9L fUEc/WG6ks2mGBkvQ/VDiqiTp09BJty96zyLmlbRRMrxQ6bNYxM8kUKh4WnryTdB DDBiBVeS8cCd1sVaD3w55HFR6SSLhm3XZiTDH9il2WtSmKw4mPCmy04ajxMp6FLM lvHnOVPEenVt0OShS+7yLovRZMLJEjrLd5O79M52VejBT8nnljENGxA0mbU4akoC BtjjTIJELXcH1PaV5PBTVFLk8IZPI+Wv8S+VP91BQE83m8BZmxOxHYnebR32s0zA RqcSgqBFoTH2Fvc3gpy7p2pMrFHMlCHYHnHqS3A3xPwpHcN3ARZcIRzIdm8w+5Qq cgWkOvT6UL0oELkCVob156Cy8TyeSRrawGtPx5JWNVB6G/z+Hmca67dtLUDKRFkO 2hUjV8yozffQzXpPsMpVVOd1oJMQ8OfInehP7eEfr1STFlgjPo4VHFYFLF0Y7lUO B1si4PQm0Lmj/g6gdvYSNjdoOtMtQ6fGtDyPja+kV9sEpHVCl1vCj1jBtqUSGMKP i48fXTE/rIHmRW3n95C/yEmk5PteSptOSda+kwqAUQJf+n7J/hOUPqL6sV1PCCZt fbCkaBVzv63FUZDymxkMRGQTsXllCQCf64epJFyyW2Exfc5AVSY= =L+D5 -END PGP SIGNATURE End Message ---
Bug#1056017: marked as done (rlvm: FTBFS: boost1.83 transition)
Your message dated Tue, 26 Dec 2023 10:50:37 + with message-id and subject line Bug#1056017: fixed in rlvm 0.14-5.2 has caused the Debian Bug report #1056017, regarding rlvm: FTBFS: boost1.83 transition 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.) -- 1056017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rlvm Version: 0.14-5.1 Severity: normal User: gl...@debian.org Usertags: boost183 ftbfs-boost183-transition Hi, we are preparing the transition of all libs on the new boost 1.83. During the rebuild of packages against this library it was identified that probably your package fails to build. Relevant part (hopefully): - In file included from src/platforms/gtk/gtk_rlvm_instance.cc:33: src/utilities/file.h:49:24: error: 'std::unique_ptr' has not been declared 49 | std::unique_ptr& fileData, |^~ src/utilities/file.h:49:34: error: expected ',' or '...' before '<' token 49 | std::unique_ptr& fileData, | ^ - To reproduce this behavior, you can install -dev Boost packages from the experimental repository, as shown in the following command: apt install libboost-dev -t experimental The full build log is available from: http://qa-logs.debian.net/2023/10/27/rlvm_0.14-5.1_unstable_boost181.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-boost183-transition;users=gl...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-boost183-transition=gl...@debian.org=1=1=1=1#results If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you are unable to reproduce this, please provide a build log and diff it so that we can identify any relevant changes that may have occurred in the meantime. --- End Message --- --- Begin Message --- Source: rlvm Source-Version: 0.14-5.2 Done: Bo YU We believe that the bug you reported is fixed in the latest version of rlvm, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bo YU (supplier of updated rlvm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Dec 2023 20:40:29 +0800 Source: rlvm Architecture: source Version: 0.14-5.2 Distribution: unstable Urgency: medium Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Bo YU Closes: 1056017 Changes: rlvm (0.14-5.2) unstable; urgency=medium . * Non-maintainer upload. * Fix ftbfs on boost1.83. (Closes: #1056017) * Use libboost-timer-dev instead of libboost-date-time-dev. Checksums-Sha1: 8da94f54623fffd5e40d625d1b4c2463aea849f6 2165 rlvm_0.14-5.2.dsc 2f2d546cb47b2f4b3ac755f20c0e88c128e2dc43 15324 rlvm_0.14-5.2.debian.tar.xz 9ab6499149292939d2a57402efc6d8fbb4461372 18671 rlvm_0.14-5.2_source.buildinfo Checksums-Sha256: fc95299152987579b928daad416b33c8773c6df2c18c1a5344340b8292990eda 2165 rlvm_0.14-5.2.dsc f46e433693d0863696d956791dd35ee1016168a620ba9bbae6b3cb6d0c49bcde 15324 rlvm_0.14-5.2.debian.tar.xz af1e68282bbd7d430adcaa8b8ea47963206863c0c17dc582dd5e5fde09d5 18671 rlvm_0.14-5.2_source.buildinfo Files: fdcbed2fb187c0c0736f66cb57fdc5e3 2165 games optional rlvm_0.14-5.2.dsc 816ce5cc8b112fb2b87d143f700d0788 15324 games optional rlvm_0.14-5.2.debian.tar.xz 3b1fec182c209d595eea4be9308d35e2 18671 games optional rlvm_0.14-5.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmWKq2MACgkQRBc/oT0F iIhWqQ//d63FDYbIAX3mycVjBFVPcv21g4hOCNpRNY9LxujUyFLC5s/RcX6XdeqC QlBdD8BTcsReng/xc44+YrEY30TgcdcGlE0dcSjJUq1gzqYtXd73JGAg6uvqi37P DnhsS+t6ekJW14J/76bA9vQA/XobfzGki6BBOTZz3z4lWHNNcnHAcB2G1KRQRB7w awMDfFHDbOVG9WFKtbPRp4yRA1R1WG4D75xeIFOl5c6azZ5VGcqT2ABExv1AJueU YP8L9ySIFLAicmZ816NbhPR18cyWO16vjklQg5P6vVg+jqcAPhhq8uhp/ch1SWpa iduuWwBsJfW8wZG66yMFs6JPDUtaig68XWGcd4F7ipypR//9B9vTtshooa6FYKtp
Bug#1054791: marked as done (mate-hud: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25)
Your message dated Tue, 26 Dec 2023 10:34:21 +
with message-id
and subject line Bug#1054791: fixed in mate-hud 22.10.3-2
has caused the Debian Bug report #1054791,
regarding mate-hud: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_clean] Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mate-hud
Version: 22.10.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -Rf mate_hud.egg-info/
> # dh_auto_clean with pybuild/distutils only works if setup.py is
> # present
> if [ -f setup.py ]; then \
> dh_auto_clean; \
> fi
> I: pybuild base:310: python3.11 setup.py clean
> running clean
> error: error in /<>/.pybuild/cpython3_3.11/.pydistutils.cfg:
> command 'clean_i18n' has no such option 'all'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/mate-hud_22.10.3-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mate-hud
Source-Version: 22.10.3-2
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
mate-hud, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated mate-hud 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, 26 Dec 2023 11:13:09 +0100
Source: mate-hud
Architecture: source
Version: 22.10.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team
Changed-By: Mike Gabriel
Closes: 1054791
Changes:
mate-hud (22.10.3-2) unstable; urgency=medium
.
* d/changelog:
+ Post-upload correct attributions of changes for the prev upload to
myself.
* debian/patches:
+ Add 1001_setup-py-drop-clean.patch. Fix FTBFS against Python 3.11 and
newer (no i18n files included in this project, so dropping all i18n
capabilities). (Closes: #1054791).
Checksums-Sha1:
1593e925c2976c62fc8612f39cd3dadbbdb2dedc 2081 mate-hud_22.10.3-2.dsc
9e5c96457611d4d133d7ec5931938503e20a0f6e 4360 mate-hud_22.10.3-2.debian.tar.xz
5e6efad65b168a41e1750c708ab656f59c9da9d3 8319
mate-hud_22.10.3-2_source.buildinfo
Checksums-Sha256:
f2d11dd7c4d3d95e7149ac3b5030538800225d051ece316ec0045eaab742309d 2081
mate-hud_22.10.3-2.dsc
391c0cf5f53c3dcd688d2c30a1e84dd669fd4f80e5dbebb50cb3433f612126a5 4360
mate-hud_22.10.3-2.debian.tar.xz
ec96acfa2f3cf8e30fbaf3562f999df71ba007025a774e2c5b5bf8ec59835cf3 8319
mate-hud_22.10.3-2_source.buildinfo
Files:
b9cf90b989b8daca3d3b27ee497f5dde 2081 x11 optional mate-hud_22.10.3-2.dsc
c4f319340184c694751c268e4736bfe6 4360 x11 optional
mate-hud_22.10.3-2.debian.tar.xz
cb60e3902f4c263c2eebd5680e87ad00 8319 x11 optional
mate-hud_22.10.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmWKp7IVHHN1bndlYXZl
Bug#1054796: marked as done (mate-tweak: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 25)
Your message dated Tue, 26 Dec 2023 10:19:28 +
with message-id
and subject line Bug#1054796: fixed in mate-tweak 22.10.0-3
has caused the Debian Bug report #1054796,
regarding mate-tweak: FTBFS: make[1]: *** [debian/rules:16:
override_dh_auto_clean] Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mate-tweak
Version: 22.10.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -Rf mate_tweak.egg-info/
> # dh_auto_clean with pybuild/distutils only works if setup.py is
> # present
> if [ -f setup.py ]; then \
> dh_auto_clean; \
> fi
> I: pybuild base:310: python3.11 setup.py clean
> running clean
> error: error in /<>/.pybuild/cpython3_3.11/.pydistutils.cfg:
> command 'clean_i18n' has no such option 'all'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/mate-tweak_22.10.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mate-tweak
Source-Version: 22.10.0-3
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
mate-tweak, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated mate-tweak 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, 26 Dec 2023 10:46:13 +0100
Source: mate-tweak
Architecture: source
Version: 22.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team
Changed-By: Mike Gabriel
Closes: 1048570 1054796
Changes:
mate-tweak (22.10.0-3) unstable; urgency=medium
.
* debian/patches:
+ Add 1001_fix-clean-i18n.patch. The clean_i18n command is not compatible
anymore with distutils's clean command. (Closes: #1054796).
* debian/rules:
+ Call 'setup.py clean_i18n' manually.
+ Create backup copy of original po/mate-tweak.pot file. Allows rebuilding
the src:pkg multiple times. (Closes: #1048570).
* debian/mate-tweak.lintian-overrides:
+ Update syntax of desktop-command-not-in-package override.
* debian/copyright:
+ Update copyright attribution for debian/.
Checksums-Sha1:
f09bc1b0aca56ed65639aa30df5d4a334853ae27 2138 mate-tweak_22.10.0-3.dsc
e845ab99d6c0c476ec419e0b4214c2b68ad8b1e2 7808
mate-tweak_22.10.0-3.debian.tar.xz
c8a890a888247ab04416c3a8b59455e7bb39ae81 8327
mate-tweak_22.10.0-3_source.buildinfo
Checksums-Sha256:
9d00fdb5a32e691de41dece32e7a9fa55c1818d776b6db363a2cd0dec3784676 2138
mate-tweak_22.10.0-3.dsc
c71d2311974cda41ae126c5b1868e7da40fdb9989098e46dcd54540856a57ab5 7808
mate-tweak_22.10.0-3.debian.tar.xz
e49096d8aaf731e312aecb5597574cd3b2656022511b16b766bfcfa6eb24eebf 8327
mate-tweak_22.10.0-3_source.buildinfo
Files:
0103cf7debf1fa6f6dec65e562cf6548 2138 admin optional mate-tweak_22.10.0-3.dsc
Processed: Bug#1054791 marked as pending in mate-hud
Processing control commands: > tag -1 pending Bug #1054791 [src:mate-hud] mate-hud: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25 Added tag(s) pending. -- 1054791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054791: marked as pending in mate-hud
Control: tag -1 pending Hello, Bug #1054791 in mate-hud 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-mate-team/mate-hud/-/commit/f52ee776bfdde76670cf6b930f07037bb58b550a debian/patches: Add 1001_setup-py-drop-clean.patch. Fix FTBFS against Python 3.11 and newer (no i18n files included in this project, so dropping all i18n capabilities). (Closes: #1054791). (this message was generated automatically) -- Greetings https://bugs.debian.org/1054791
Bug#1054796: marked as pending in mate-tweak
Control: tag -1 pending Hello, Bug #1054796 in mate-tweak 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-mate-team/mate-tweak/-/commit/fbf20b49ed86898494957f327291e78e0a831db3 debian/patches: Add 1001_fix-clean-i18n.patch. The clean_i18n command is not compatible anymore with distutils's clean command. (Closes: #1054796). (this message was generated automatically) -- Greetings https://bugs.debian.org/1054796
Processed: Bug#1054796 marked as pending in mate-tweak
Processing control commands: > tag -1 pending Bug #1054796 [src:mate-tweak] mate-tweak: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 25 Added tag(s) pending. -- 1054796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035719: mdns-reflector: missing Depends: libcap2-bin
Control: tags -1 + patch
Here is a patch to solve the issue.
diff --git a/debian/control b/debian/control
index 4d6ef8c..36be614 100644
--- a/debian/control
+++ b/debian/control
@@ -17,6 +17,7 @@ Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
adduser,
+ libcap2-bin,
Description: lightweight and performant multicast DNS (mDNS) reflector
mDNS Reflector (mdns-reflector) is a lightweight and performant
multicast DNS (mDNS) reflector with a modern design. It reflects mDNS
--
Happy hacking
Petter Reinholdtsen
Processed: Re: mdns-reflector: missing Depends: libcap2-bin
Processing control commands: > tags -1 + patch Bug #1035719 [mdns-reflector] mdns-reflector: missing Depends: libcap2-bin Added tag(s) patch. -- 1035719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)
On 24/12/2023 10:50, Drew Parsons wrote: reopen 1058876 block 1058944 by 1058876 thanks Alas, the fix in openmpi 4.1.6-3 for the include path to the openmpi fortran modules has hardcoded x86_64-linux-gnu This is preventing builds and tests on other architectures, e.g. rebuilding sundials for the petsc transition. I think openmpi's debian/tests will also need Depends: pkg-config for the new compile_run_cc_pkgconfig test. The problem appears to be the heuristics in upstream/FindMPI.cmake in adios2 (and sundials). It happens in sid tests but not my arm64 devel environment. Debugging slowly. -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie
