Bug#1070001: marked as done (rust-net2 FTBFS on 32bit with 64bit time_t)
Your message dated Tue, 30 Apr 2024 05:37:16 + with message-id and subject line Bug#1070001: fixed in rust-net2 0.2.39-1 has caused the Debian Bug report #1070001, regarding rust-net2 FTBFS on 32bit with 64bit time_t 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.) -- 1070001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-net2 Version: 0.2.37-1 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=rust-net2=armhf=0.2.37-1%2Bb1=1714277125=0 ... error[E0308]: mismatched types --> src/ext.rs:902:22 | 902 | tv_usec: (d % 1000) as suseconds_t, | ^ expected `i64`, found `i32` For more information about this error, try `rustc --explain E0308`. error: could not compile `net2` due to previous error ... --- End Message --- --- Begin Message --- Source: rust-net2 Source-Version: 0.2.39-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-net2, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-net2 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, 30 Apr 2024 04:57:12 + Source: rust-net2 Architecture: source Version: 0.2.39-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1070001 Changes: rust-net2 (0.2.39-1) unstable; urgency=medium . * Team upload. * Package net2 0.2.39 from crates.io using debcargo 2.6.1 * Add patch to workaround glibc time64 suseconds_t inconsitency (Closes: #1070001) Checksums-Sha1: b97880979b53c0f6862797b66f4ef18c83433ce5 2515 rust-net2_0.2.39-1.dsc 4993c647104afd55bd5a9966b327b2eb28f9c40c 20696 rust-net2_0.2.39.orig.tar.gz f80f8f8bc08bd3e7e57ee835553bf2de2c514d6e 3488 rust-net2_0.2.39-1.debian.tar.xz d3debdd4bdd9dcfd38597a472f102210fb80ebdc 8331 rust-net2_0.2.39-1_source.buildinfo Checksums-Sha256: 96c6286e26070cdeaaf5474a0f7fb9c0f894134d647561ffa91feca23dd78db7 2515 rust-net2_0.2.39-1.dsc b13b648036a2339d06de780866fbdfda0dde886de7b3af2ddeba8b14f4ee34ac 20696 rust-net2_0.2.39.orig.tar.gz dfd0f8c988430a907c65718be7685a979ea652aeb8d7cbe5016e20ea3353a2fe 3488 rust-net2_0.2.39-1.debian.tar.xz 304730c86ef32c8219f1b82842b848e00837f612632c0f41983b44fc70030bdc 8331 rust-net2_0.2.39-1_source.buildinfo Files: 688fd57bad854f6d83e6bd686534cda7 2515 rust optional rust-net2_0.2.39-1.dsc 02f29fb17eeacc1ca623f6c9a980f2c1 20696 rust optional rust-net2_0.2.39.orig.tar.gz 0223195c9dadb99c2caf083db9a63ccf 3488 rust optional rust-net2_0.2.39-1.debian.tar.xz 7cc7c34f4aca7425909ac4327f0b3812 8331 rust optional rust-net2_0.2.39-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmYwfzgUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xsqxw//RgtNgopjA/KUgF9/R2aNdMSFp7c7 Xp8eGW5fRXywpr7youuowki8jRxnvCYfjgT89KOfj3Fp18Rjoo2Vl77jX5nR5KL+ is0UjJnZLuNKcI+jm/vypb48Vf3QqFlK7FHknuES2W0Kxy2GHPHs0kRUSBnO5qC3 ICKW+5CAcOzpgzcD6JwX0IlrMVvHhmDM8O/hdDfwIuRZsKJ58tjRtO5nr7CzsXWn mOpKDaVqL8lZF/rL19KkNdJFDEQzK3Ogq0RBUUkw6FwI/c7WS84KlrVn39BpZlpk 59wjZkZLNImqTJ3uDmS7M6kKcdI+stLafa4fbrbFHI//ZAbSNLoaRt5FfzGNWpuX R1ldBepCPPBxDzhOqIMjgiTImBzdJKf1he2Ep6evendBeUxFgEXuayB8dHB/QZjU 2ULrSMbgIzPF0EjPSElapkpJFJ8QNjO2YKbqeEgq5eAt0ryWVwikh3scHjjPcP20 VE+JH02ma0CA8gp+ZG/naUMPJez6VQyTYgxhz7nfZd4zIofadNv0JuY1o1r5vE5V dtJOGLPRwve5Ik1Qz6t85rFGPStyJXI4oq26WmD1EHo5OTGtbp20myUgqBymsLvK oBkKAQjYKwpGi8izYSOH4rkqtJXI80Rn0arLpNulkvZxQQA8Q/fD72NDn90kcZT9 l9DagaWlxSrlS1M= =gpem -END PGP SIGNATURE- pgp9WabeTopkw.pgp Description: PGP signature --- End Message ---
Bug#1070000: marked as done (rust-time-0.1 FTBFS on 32bit with 64bit time_t)
Your message dated Tue, 30 Apr 2024 05:06:42 +
with message-id
and subject line Bug#107: fixed in rust-time-0.1 0.1.45-1
has caused the Debian Bug report #107,
regarding rust-time-0.1 FTBFS on 32bit with 64bit time_t
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.)
--
107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-time-0.1
Version: 0.1.44-2
Severity: serious
Tags: ftbfs trixie sid
https://buildd.debian.org/status/fetch.php?pkg=rust-time-0.1=armhf=0.1.44-2%2Bb1=1714295931=0
...
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/sys.rs:521:26
|
521 | let mut tv = libc::timespec { tv_sec: 0, tv_nsec: 0 };
| ^^
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/sys.rs:527:26
|
527 | let mut ts = libc::timespec { tv_sec: 0, tv_nsec: 0 };
| ^^
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/sys.rs:555:24
|
555 | t: libc::timespec {
|^^
|
= note: ... and other private field `__pad` that was not provided
error: could not compile `time` due to 3 previous errors
...
--- End Message ---
--- Begin Message ---
Source: rust-time-0.1
Source-Version: 0.1.45-1
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
rust-time-0.1, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated rust-time-0.1
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, 30 Apr 2024 04:41:54 +
Source: rust-time-0.1
Architecture: source
Version: 0.1.45-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Closes: 107
Changes:
rust-time-0.1 (0.1.45-1) unstable; urgency=medium
.
* Package time 0.1.45 from crates.io using debcargo 2.6.1 (Closes: #107)
* Update remove-wasi.patch for new upstream.
Checksums-Sha1:
86a96aeb82a5149c539af1ef0adc1976cd1df07a 2771 rust-time-0.1_0.1.45-1.dsc
030b098f07c3cf9bd023153bc2a3d532d313 28911 rust-time-0.1_0.1.45.orig.tar.gz
498b774fb9b3aa9e15ee5889db8f62714eaf2261 3208
rust-time-0.1_0.1.45-1.debian.tar.xz
712a85cce2681ffccb9f485e81a49e07e2984530 8309
rust-time-0.1_0.1.45-1_source.buildinfo
Checksums-Sha256:
4c1f80f56048c38c2bd6857d132180005b4fda44f5d955b0791a66368108577a 2771
rust-time-0.1_0.1.45-1.dsc
1b797afad3f312d1c66a56d11d0316f916356d11bd158fbc6ca6389ff6bf805a 28911
rust-time-0.1_0.1.45.orig.tar.gz
133d57e2464b9193f247135a6330c2b66e2788474321851f5e4cd1daac0b211b 3208
rust-time-0.1_0.1.45-1.debian.tar.xz
36820d94fb1c1e290c644a8000e4b54c4db2fee9f88df17c5dd5f1c368bdff1c 8309
rust-time-0.1_0.1.45-1_source.buildinfo
Files:
5279b2b1394424e31d9b9d6f6daebae3 2771 rust optional rust-time-0.1_0.1.45-1.dsc
dc9491aba5e393b587f4bbffab58ed52 28911 rust optional
rust-time-0.1_0.1.45.orig.tar.gz
5fdc533146352b0ee4702e186ddc410f 3208 rust optional
rust-time-0.1_0.1.45-1.debian.tar.xz
b9e087e791b1128a353f8947f49453c9 8309 rust optional
rust-time-0.1_0.1.45-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmYweUwUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsLPw//ULcN6alE6CacJe4WK2UIaXBT9fDS
lWPB39SouLZSzJjwHBm/GC+abCTje29TOrh0mRq+aBQPUVpzMthhhfQxFWnzWY/9
dG00+pYjJBk8l0yKAd2lzdEMQWcP55YlolIk3J0Ia5CdouipH4tvN8c0lVHT6mbW
1STuSOcTvKanfpE3JxQ4PQjSftWNf6oorivPwOeGRUrspapb5Dl92tZHiSPf9F2A
kYNPWDgp5nu+cPUYbuxUQQmqjkqccX+1H7nimBBFlSvT1MJJYRrmR0G1sMgLKZ94
3cIAeKGfP5fbDaRcJ1elWGIbyaUy/gMVDidk4DIw2Fo9lNqExh3xgrMIxl5/jK1C
03KRLLiI0/7+QtzSjDdVp4VDIz5x87Gdzqx4mTrLMvC0uzYB0x9NOVaUUosufPcR
Bug#1069998: marked as done (rust-datetime FTBFS on 32bit with 64bit time_t)
Your message dated Tue, 30 Apr 2024 03:53:02 +
with message-id
and subject line Bug#1069998: fixed in rust-datetime 0.5.2-6
has caused the Debian Bug report #1069998,
regarding rust-datetime FTBFS on 32bit with 64bit time_t
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.)
--
1069998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-datetime
Version: 0.5.2-5
Severity: serious
Tags: ftbfs trixie sid
Control: affects -1 src:rust-zoneinfo-compiled
https://buildd.debian.org/status/fetch.php?pkg=rust-datetime=armhf=0.5.2-5%2Bb1=1714252645=0
...
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/system.rs:74:18
|
74 | let mut tv = libc::timespec { tv_sec: 0, tv_nsec: 0 };
| ^^
|
= note: ... and other private field `__pad` that was not provided
...
--- End Message ---
--- Begin Message ---
Source: rust-datetime
Source-Version: 0.5.2-6
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
rust-datetime, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated rust-datetime
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 29 Apr 2024 02:28:10 +
Source: rust-datetime
Architecture: source
Version: 0.5.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Closes: 1069998
Changes:
rust-datetime (0.5.2-6) unstable; urgency=medium
.
* Team upload.
* Package datetime 0.5.2 from crates.io using debcargo 2.6.1
* Handle padding in struct timespec introduced by time64 patches (Closes:
#1069998).
Checksums-Sha1:
9b2126e3257598328b561c6ce4012bd971bac4b3 2359 rust-datetime_0.5.2-6.dsc
4589998947a7a910f3fd939aca410ebaa7d8fbcf 4028
rust-datetime_0.5.2-6.debian.tar.xz
891135e238821b905a57d049d09ce96646389be1 8155
rust-datetime_0.5.2-6_source.buildinfo
Checksums-Sha256:
5e5fcc556017f0d2de0eeb6523ee982b26afe9123c4b252a6a1e6416aa264b0b 2359
rust-datetime_0.5.2-6.dsc
61a5a2712bce6032e89a13b2db1beb56090581bb258cdec1777aedabf5fb9f37 4028
rust-datetime_0.5.2-6.debian.tar.xz
c9eb1172064114ac5865e436cf99a2cf66ec601f4e413b47c2892d8519a122d4 8155
rust-datetime_0.5.2-6_source.buildinfo
Files:
f01fd0582ae265b96f13daf0ad3773cf 2359 rust optional rust-datetime_0.5.2-6.dsc
38b8ddfd00c3b1eb20cf900299e8e3be 4028 rust optional
rust-datetime_0.5.2-6.debian.tar.xz
74b53315a38100e92e4a8286c038ac3b 8155 rust optional
rust-datetime_0.5.2-6_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmYwZUMUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsvNw/+O/sMy911O3/gHt9lXg1GvXiSJGdb
+aVXTjGFqd939UeVqxsy1dewyY9t+TZ6PY2Pt9CIm9bqh77/xCYk4b/YiomBJUGp
WJUVrYmYdKHA1PWXdThSRsrCNAXk1qRaRAiqKoplKLKt6O/eje5umQ4nUEsTtqJb
wxdnqcLm9+ClQE/6MJ3o0XT5oPCk3ao1Vsiv2yE4GNkAWdyfuhiGEd6+MueMpa+c
iXHUgUT6paw6YXfOrxAXZ5OqQyzkEPOj1gW8hNK/YBhBHTUeg76qYlX//HV8LyfO
oPP4KFTUqW1UWmK2zyJHHyJGDmr+TFGMgAsuVSYwbtU3Kvy3Kf8HrsIdkoc54LrT
X8qGyUK64EOHrpCR3DIiG0KjyEmOYHRFDE2317HmSCfnUWE3BKufjm0sS6AVMv4W
euB47sL5xFIlljAX3/t65nlUPFKinCcAlv6+1xRUxwZQJbRCIxO364gqBg91l8b0
6sGt1V8E4V96hADcW37n3OOhs0dGa6OnFwVF3IMXxOVvUuP+tPSx7O95fWhzVymx
hlEK005F88TVnSG9BQf0hzMAJ0d1FrV/R3mF91Ytdh6JXx0h6JqZZ/Omke0trj1e
YYsRwZ4NYP1a0xLoc1rO+/ZIcabUpSbro3iE+6QUbvkX825o4csJVs+jzSraml94
dFMTl83R0bTVU1Q=
=T7uv
-END PGP SIGNATURE-
pgpqbZwvLQ_p6.pgp
Description: PGP signature
--- End Message ---
Bug#1069953: marked as done (libgstreamer-plugins-bad1.0-dev: not installable on i386)
Your message dated Tue, 30 Apr 2024 01:19:25 + with message-id and subject line Bug#1069953: fixed in gst-plugins-bad1.0 1.24.2-4 has caused the Debian Bug report #1069953, regarding libgstreamer-plugins-bad1.0-dev: not installable on i386 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.) -- 1069953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgstreamer-plugins-bad1.0-dev Version: 1.24.2-3 Severity: grave X-Debbugs-Cc: sramac...@debian.org $ apt install --no-install-recommends libgstreamer-plugins-bad1.0-dev Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: libgstreamer-plugins-bad1.0-dev : Depends: libgstreamer-opencv1.0-0 (= 1.24.2-3) but it is not going to be installed This issues makes at least cheese BD-Uninstallable on i386 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: gst-plugins-bad1.0 Source-Version: 1.24.2-4 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of gst-plugins-bad1.0, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated gst-plugins-bad1.0 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, 29 Apr 2024 21:09:14 -0400 Source: gst-plugins-bad1.0 Built-For-Profiles: noudeb Architecture: source Version: 1.24.2-4 Distribution: unstable Urgency: high Maintainer: Maintainers of GStreamer packages Changed-By: Jeremy Bícha Closes: 1069953 Changes: gst-plugins-bad1.0 (1.24.2-4) unstable; urgency=high . * Fix opencv dependency architectures (Closes: #1069953) Checksums-Sha1: 20a2423de638e7f6d4797c93b7b4bb0b9610b3ac 6016 gst-plugins-bad1.0_1.24.2-4.dsc b971180598377026ba48d74ef6f5816ce38768c9 38684 gst-plugins-bad1.0_1.24.2-4.debian.tar.xz 84b5744622130f7e67e1494e9a5230083791781e 20386 gst-plugins-bad1.0_1.24.2-4_source.buildinfo Checksums-Sha256: 9e6095223686db234ecda145fe6ae8efef0731ab8fee4aa4bc28ec50556de695 6016 gst-plugins-bad1.0_1.24.2-4.dsc 0a2f586103b28bb3cb3d1fe8cf4445b85e09e84324256ac990b65c3b166f9128 38684 gst-plugins-bad1.0_1.24.2-4.debian.tar.xz 38df729c961cca2e08c84b68e2a20f2b09f6c1e69d2ccf7b25e02c2294a0a313 20386 gst-plugins-bad1.0_1.24.2-4_source.buildinfo Files: c77af3cdd240afd73e9da0d56468fe5b 6016 libs optional gst-plugins-bad1.0_1.24.2-4.dsc 53cdfb277e3df625bc36a2a6f28d5439 38684 libs optional gst-plugins-bad1.0_1.24.2-4.debian.tar.xz 879191c3859d25b3347f5463c2db99c3 20386 libs optional gst-plugins-bad1.0_1.24.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYwRQwACgkQ5mx3Wuv+ bH2OUQ//ScktVTWCSfZ7s40j//hi0htd6Cdngb/ONxeG5RqqBW6HtriTyeRelvr2 vP5icXtu21tIxLOd4yT+9BmgBB8lRgvrL4s0qvRY/ZCbzhYlxMjo+qQvCyZ6aLjW +YCP9Xwq8ob3cnKmrNjQdV7keeeIwZ6w9id+Rpuoca47v+/Y1MrkU7bhlbRQDNvY 6+m4oKNGaOkJB/nvs/fsLBWKmi5OR0QLxCkKTA/0d3n0SS1BV7u9hEhG9l2JGKUF 0vmPqKINUGuLy0oJ3k3HGixMShJ6DhZpVqNAVo/fLbFBw2+gdwKV9eouG4dNgyHF /5skxrtDQuJq29AY3IHqMqIWezqg9gfa6u9O/8v00jp/8S3/scLrr1E+2C+WF5Yt 0i6MoaUP3KGUpyzlI70XGlXJV2PSEjf0UwIKwYX+kuWH/R6BgYDv497wWdDnt+Zp 889JgTVlQigBsH5PSmYpHiBfpQkOxTN/fDExs6WRGxe90LdbVIMAhG8/ieX/evMI uo2yIOY6INHV0YRzrhlkio57BlfTm92so052Atnuro6+QUIKCUvxNTHYSeyKRYqB ModIIreaP+tv/2j0mFA/y2wcjFqDG/eRkKxv5/A6zN+x6CVlc3cCIlVUeNKOgpD8 O0wdd8B1irqdVgy2GDrv0EydEVjXZjnNgxWcLgoLdtAcq8hYWv8= =ZWg8 -END PGP SIGNATURE- pgprMYNFIzOMa.pgp Description: PGP signature --- End Message ---
Processed: bug 1069426 is forwarded to https://github.com/Feh/nocache/issues/54
Processing commands for cont...@bugs.debian.org: > forwarded 1069426 https://github.com/Feh/nocache/issues/54 Bug #1069426 [src:nocache] nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined Set Bug forwarded-to-address to 'https://github.com/Feh/nocache/issues/54'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1069426
Processing commands for cont...@bugs.debian.org: > tags 1069426 + upstream Bug #1069426 [src:nocache] nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory
Processing commands for cont...@bugs.debian.org:
> found 1063498 0.18.1-1
Bug #1063498 {Done: Helmut Grohne } [src:rust-glib-sys]
rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat
'/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory
Marked as found in versions rust-glib-sys/0.18.1-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1063498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: RM: rust-gtk-sys -- RoM; unmaintained library
Processing control commands: > affects -1 src:rust-gtk-sys Bug #1070086 [ftp.debian.org] RM: rust-gtk-sys -- RoM; unmaintained library Added indication that 1070086 affects src:rust-gtk-sys > block -1 by 1064373 Bug #1070086 [ftp.debian.org] RM: rust-gtk-sys -- RoM; unmaintained library 1070086 was not blocked by any bugs. 1070086 was not blocking any bugs. Added blocking bug(s) of 1070086: 1064373 -- 1070086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069876: marked as done (libsbml: autopkgtest regression)
Your message dated Mon, 29 Apr 2024 22:12:37 + with message-id and subject line Bug#1069876: fixed in libsbml 5.20.2+dfsg-4 has caused the Debian Bug report #1069876, regarding libsbml: autopkgtest regression 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.) -- 1069876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsbml Version: 5.20.2+dfsg-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org https://ci.debian.net/packages/libs/libsbml/testing/amd64/45907226/ 95s autopkgtest [21:29:51]: test autodep8-python3: [--- 95s Testing with python3.12: 95s Traceback (most recent call last): 95s File "", line 1, in 95s File "/usr/lib/python3/dist-packages/libsbml/libsbml.py", line 27, in 95s import _libsbml 95s ModuleNotFoundError: No module named '_libsbml' 95s autopkgtest [21:29:51]: test autodep8-python3: ---] 96s autodep8-python3 FAIL non-zero exit status 1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: libsbml Source-Version: 5.20.2+dfsg-4 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of libsbml, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated libsbml 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, 29 Apr 2024 16:19:36 +0200 Source: libsbml Architecture: source Version: 5.20.2+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 1067961 1069876 Changes: libsbml (5.20.2+dfsg-4) unstable; urgency=medium . * Team upload. * Hand write the autopkgtest to only test against the default version of Python. Closes: #1069876 * d/control: skip building mono packages for mips64el and riscv64, as mono-runtime is not available for those archs. * d/control: remove dep on swig by python3-sbml5. Closes: #1067961 * d/rules & d/cmake_opts: set Python include and binary paths dynamically. * d/rules: Stop setting JDK_PATH & JAVA_INCLUDE_PATH, they aren't used. * d/rules: unify references to the build directory; use dh_auto_configure and dh_auto_make. This also helps with build hardening and enables parallel building. * d/upstream/metadata: Update for their GitHub repository. * d/rules: build and run the tests. Checksums-Sha1: bbd8d7dc3b9652a0e11999703422b5c7b8bccd75 3904 libsbml_5.20.2+dfsg-4.dsc 3fc4c34a4f5ab779984109e3f67959771af199c4 24380 libsbml_5.20.2+dfsg-4.debian.tar.xz 3088ed728279348c59658b75d0a9516b2f14dc11 22455 libsbml_5.20.2+dfsg-4_source.buildinfo Checksums-Sha256: d63d81c5e4cdffeecc8c7520cb92136ee7f3d25ea69f407211b553416fa9bd80 3904 libsbml_5.20.2+dfsg-4.dsc 7e9914d8d7f58521ed21cb50f495cbb10181e208f11ff44a51af59d6d43d428a 24380 libsbml_5.20.2+dfsg-4.debian.tar.xz c65638ad0437f9ce1efb8e356488c42da3a5538e692c3e7bd49314089d5d530d 22455 libsbml_5.20.2+dfsg-4_source.buildinfo Files: a08954a0cfd064a2258cd23e429228dc 3904 science optional libsbml_5.20.2+dfsg-4.dsc 5dadbd893e6b448640b5bef5e74ab712 24380 science optional libsbml_5.20.2+dfsg-4.debian.tar.xz fd27dff59e28ff7f596c75d0bf9b964b 22455 science optional libsbml_5.20.2+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmYv9aMACgkQPCZ2P2xn 5uJaaQ/9G1YsLyxGOjVBIDLO5WlcizMV2LXQrkyYqWsZIPqQsFfbsK+3DT2vPpa3 YE6Tkdcw06HLyhyAfuwTf9qSK+QbPHW95EWXic6mqMGYJnqfRLZpIkMAKYdCiGI8 jkHXLH8anhifRdQCoV7/ddpJx8u1VstlK0qbbWYwPUHjlx0jK/4YZ+5oNBGR/jp0 qF5y9N/b+NtKYvJ5l6ND7XOQoquu4VaU75/sQeU5/hibV910LRw6Z8x7Yi48xKWI kTzS6ra5f9VvogkmqoDjaO0+KluvjXE75oMbHo9SoiF+ubaiHiNqzPBHVG2WK9jq 2uMA4s3KFShhFBZ3zYaCMyVb7FcbkqW6B6Dloea44jF4/PQchuU4BfDcVh4hIIeC oIr5jAJ+z4H3ogSkEIE1IMp73DapQfVenXurLo/Kbw/KlxkC8RycEN1dnvc/YUc9 gv3TxAlE9JPZ2IoMsZwcc1MZ5UkTt6efRvBTQIIAYbNpqBh+PEu60C5ZnLBtmqW0 LSTCvbqMgDWhoS6GySpf1dOlJZMMjdGImNYvUEgywoXLHLjCzG49Tp2xu8GB6BhI
Bug#997441: squirrel3: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
Hi, Thanks for the patch. Fabian, I uploaded the NMU with a 7 days delay. Reach out if you see a good reason to either cancel or delay further this NMU. Bests, -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. From e054c7aa6fdd402ab63709e15103aab1f50e6119 Mon Sep 17 00:00:00 2001 From: Matthias Geiger Date: Mon, 29 Apr 2024 23:38:16 +0200 Subject: [PATCH 1/2] Fix watch file to look for Github tags instead of releases --- debian/changelog | 7 +++ debian/watch | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 592b24f..c303908 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +squirrel3 (3.1-8.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix watch file to look for Github tags instead of releases + + -- Matthias Geiger Fri, 16 Feb 2024 17:46:43 +0100 + squirrel3 (3.1-8) unstable; urgency=medium * Change build dependency from texlive-generic-extra to diff --git a/debian/watch b/debian/watch index c174a72..e3733e4 100644 --- a/debian/watch +++ b/debian/watch @@ -1,4 +1,4 @@ version=4 opts="filenamemangle=s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%squirrel-$1.tar.gz%" \ - https://github.com/albertodemichelis/squirrel/releases \ + https://github.com/albertodemichelis/squirrel/tags \ (?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate -- 2.43.0 From fd3d4b9b6014eef4691759b264491a1a370b78c3 Mon Sep 17 00:00:00 2001 From: Matthias Geiger Date: Mon, 29 Apr 2024 23:39:24 +0200 Subject: [PATCH 2/2] Build-depend on tex-gyre Closes: #997441 --- debian/changelog | 5 +++-- debian/control | 3 ++- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/debian/changelog b/debian/changelog index c303908..b2aacdd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,9 +1,10 @@ -squirrel3 (3.1-8.1) UNRELEASED; urgency=medium +squirrel3 (3.1-8.1) unstable; urgency=medium * Non-maintainer upload. * Fix watch file to look for Github tags instead of releases + * Build-depend on tex-gyre (Closes: #997441) - -- Matthias Geiger Fri, 16 Feb 2024 17:46:43 +0100 + -- Matthias Geiger Mon, 29 Apr 2024 23:39:09 +0200 squirrel3 (3.1-8) unstable; urgency=medium diff --git a/debian/control b/debian/control index c504be7..43afebb 100644 --- a/debian/control +++ b/debian/control @@ -8,7 +8,8 @@ Build-Depends: debhelper-compat (= 12), texlive, texlive-latex-extra, texlive-plain-generic, - latexmk + latexmk, + tex-gyre, Standards-Version: 4.4.0 Homepage: http://squirrel-lang.org/ Vcs-Git: https://salsa.debian.org/wolff-guest/squirrel3.git/ -- 2.43.0 signature.asc Description: PGP signature
Bug#1070069: marked as done (fossil: CVE-2024-24795 unreleated breakage)
Your message dated Mon, 29 Apr 2024 21:05:09 + with message-id and subject line Bug#1070069: fixed in fossil 1:2.24-5 has caused the Debian Bug report #1070069, regarding fossil: CVE-2024-24795 unreleated breakage 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.) -- 1070069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fossil Severity: serious Justification: break unreleated package affects: apache2 Dear Maintainer, CVE-2024-24795 is fixed in apache2. However it break fossil You need to apply https://fossil-scm.org/home/info/f4ffefe708793b03 See bug here: https://bz.apache.org/bugzilla/show_bug.cgi?id=68905 I can help here and do proposed update We also need to use breaks relationship in apache2, in order to allow smooth upgrade Bastien signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: fossil Source-Version: 1:2.24-5 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of fossil, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated fossil 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, 29 Apr 2024 21:11:22 +0100 Source: fossil Architecture: source Version: 1:2.24-5 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 1070069 Changes: fossil (1:2.24-5) unstable; urgency=medium . * Cherry-pick fix f4ffefe708793b03 for CVE-2024-24795 and add "Breaks: apache2 (<< 2.4.59-1~)" to stage fix; see https://bz.apache.org/bugzilla/show_bug.cgi?id=68905 (closes: #1070069) Checksums-Sha1: c7aa6358589af04c58500169ee7a58ffeae31e2d 1896 fossil_2.24-5.dsc 033c4186306d7cf0004d01f6eba1e96bddc032b7 17308 fossil_2.24-5.debian.tar.xz ee66368a1edad3fc6f29c6a0a476c80f24626e20 7720 fossil_2.24-5_source.buildinfo Checksums-Sha256: a978178ebb30c7ee6796ebcb9e59afddc0d2949ac1ee28339df44394bd0aab0c 1896 fossil_2.24-5.dsc 5b7e79c1ebbc30af3ba5d3812f53b2b56f5982d4ab3ecf2f230d19af4d785ccf 17308 fossil_2.24-5.debian.tar.xz c62faedff4ef8a0219f363edc797090c363396688b6c97b854696b4f456346c6 7720 fossil_2.24-5_source.buildinfo Files: 4ce791f37bb59ba514d075f1cd8490f9 1896 vcs optional fossil_2.24-5.dsc 8fa2e3b6f6e13d22a0f1cabf5572981f 17308 vcs optional fossil_2.24-5.debian.tar.xz e3fd99a90da4da68bfc7f56757c192c8 7720 vcs optional fossil_2.24-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAmYwAj0PHGJhcEBkZWJp YW4ub3JnAAoJEJnrHqTSM3uIH1sP/2AxplxK+cDV9LUL4AFylDu+6utC1SIHGWBp GF6xoCkzkIAZPYZAJqlanL5zDVSR482RuRrIeT3oh3nLdungY1yytKhoS3stdFKa Zeh0pkxmoWiXxqh9mgdnymibZSlQZN4xWQye7PvyMLmY2VA27qCchKSMDJHEKRGA qUMLK4ijigKpJos0jt99ySs8FLpWXWPLtO2lJvWwUZBx2bSXSGGNADLp+0+vLNWE BlFO7gBw8kBi+hO7zf+0vyimXVTG539+z3NxRyqBCg0mKPt2/+F8leuhZr+IZPXZ 2wJTLLGX9m5rLCLYk+B6aP1ZSieKjn2sBveSkKannuh52OjNuT5DfmXS3rDVxYvn N83H/9Ml05Mk+NAn577LKLVs+XTrSqeQeYfjj8PzGy2kP7EoViUcB5xMfpDGcZgV sEOY0c/37B+nADZvl9wATF7SK3gHIC4Kh1lcijzrWQDCvea11O297mzDxdv0a3N2 qiZXILu4sDqv0e4TiADunJSAfJUepoBgc4t/+HZar1JdfexY04+5fw+eRFP2OqaR z6OXnCRHa3grYg/OtzjUavD21yDBp7Cfuk3YFJGMV7IgQckFkmYuI/q3Zy6shOf0 uT7YnaOH9XJnrWD2i9OlC7rSOXcxr9mZMaBHZsUyhjCTbiD/2DxjfMfWwLXjLHjx uKTa5ZIH =6GWb -END PGP SIGNATURE- pgpyUG5IiACgI.pgp Description: PGP signature --- End Message ---
Processed: tags
Processing commands for cont...@bugs.debian.org:
> tags 1027827 + bullseye
Bug #1027827 {Done: Dmitry Smirnov } [src:litecoin]
litecoin: FTBFS in bullseye (expired certificates in test suite)
Added tag(s) bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: metadata
Processing commands for cont...@bugs.debian.org:
> found 1051924 2.21.3+deb11u1
Bug #1051924 {Done: Bas Couwenberg } [devscripts]
devscripts: FTBFS fails in test test/test_debchange
Bug #1038389 {Done: Bas Couwenberg } [devscripts]
devscripts: dch --bpo should reference bpo12 and bookworm-backports, not
bullseye
Marked as found in versions devscripts/2.21.3+deb11u1.
Marked as found in versions devscripts/2.21.3+deb11u1.
> tags 1051924 + bullseye
Bug #1051924 {Done: Bas Couwenberg } [devscripts]
devscripts: FTBFS fails in test test/test_debchange
Bug #1038389 {Done: Bas Couwenberg } [devscripts]
devscripts: dch --bpo should reference bpo12 and bookworm-backports, not
bullseye
Added tag(s) bullseye.
Added tag(s) bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1038389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038389
1051924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070069: fossil: CVE-2024-24795 unreleated breakage
uploaded
Bug#1051924: metadata
found 1051924 2.21.3+deb11u1 tags 1051924 + bullseye thanks Hello. The version in bullseye also fails in test test/test_debchange. Thanks.
Processed: unarchive
Processing commands for cont...@bugs.debian.org:
> unarchive 1051924
Bug #1051924 {Done: Bas Couwenberg } [devscripts]
devscripts: FTBFS fails in test test/test_debchange
Bug #1038389 {Done: Bas Couwenberg } [devscripts]
devscripts: dch --bpo should reference bpo12 and bookworm-backports, not
bullseye
Unarchived Bug 1051924
Unarchived Bug 1038389
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1038389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038389
1051924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070077: ships files directly in /usr/onionprobe
Package: onionprobe Version: 1.0.0+ds-2.1+deb12u1 Severity: serious The Debian package shipped in bookworm right now changed the path to the examples/ directory. It used to be: /usr/lib/python3/dist-packages/onionprobe/examples/tpo.py and now seems to be: /usr/onionprobe/examples/tpo.py Apart from the gratuitous change, this seems to be a violation of the FHS policy, packages shouldn't ship their own stuff directly under /usr like this... I haven't checked in unstable to see if this is fixed. A. -- System Information: Debian Release: 12.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13+bpo-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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 onionprobe depends on: ii adduser3.134 ii init-system-helpers1.65.2 ii python33.11.2-1+b1 ii python3-cryptography 38.0.4-3 pn python3-prometheus-client ii python3-requests 2.28.1+dfsg-1 ii python3-socks 1.7.1+dfsg-1 ii python3-stem 1.8.1-2.1 ii python3-yaml 6.0-3+b2 ii tor0.4.7.16-1 onionprobe recommends no packages. Versions of packages onionprobe suggests: pn prometheus
Processed: tags
Processing commands for cont...@bugs.debian.org:
> # also happens in bullseye
> tags 1064676 + bullseye
Bug #1064676 {Done: Hans-Christoph Steiner }
[src:android-platform-tools-apksig] android-platform-tools-apksig: FTBFS:
dh_auto_test: error: gradle --info --console plain --offline --stacktrace
--no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=.
-Duser.name=debian -Ddebian.package=android-platform-tools-apksig
-Dfile.encoding=UTF-8 --parallel --max-workers=8 test returned exit code 1
Added tag(s) bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1064676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tags
Processing commands for cont...@bugs.debian.org:
> # this was fixed in time for bookworm
> tags 1028163 - trixie sid
Bug #1028163 {Done: Daniel Baumann }
[src:sshfs-fuse] sshfs-fuse: FTBFS (tries to use the ssh service from the host
machine)
Removed tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070069: fossil: CVE-2024-24795 unreleated breakage
will do
Bug#1056496: marked as done (python-pyknon's autopkg tests fail with Python 3.12)
Your message dated Mon, 29 Apr 2024 16:27:53 -0300
with message-id
and subject line python-pyknon's autopkg tests fail with Python 3.12
has caused the Debian Bug report #1056496,
regarding python-pyknon'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.)
--
1056496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pyknon
Version: 1.2-5
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-pyknon's autopkg tests fail with Python 3.12:
[...]
151s === FAILURES
===
151s __ TestMIDIUtils.testAddNote
___
151s
151s self =
151s
151s def testAddNote(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addNote(0, 0, 100,0,1,100)
151s > self.assertEquals(MyMIDI.tracks[0].eventList[0].type, "note")
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:45: AttributeError
151s _ TestMIDIUtils.testDeinterleaveNotes
__
151s
151s self =
151s
151s def testDeinterleaveNotes(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addNote(0, 0, 100, 0, 2, 100)
151s MyMIDI.addNote(0, 0, 100, 1, 2, 100)
151s MyMIDI.close()
151s > self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type,
'NoteOn')
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:56: AttributeError
151s _ TestMIDIUtils.testFrequency
__
151s
151s self =
151s
151s def testFrequency(self):
151s freq = frequencyTransform(8.1758)
151s > self.assertEquals(freq[0], 0x00)
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:116: AttributeError
151s ___ TestMIDIUtils.testSysEx
151s
151s self =
151s
151s def testSysEx(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addSysEx(0,0, 0, struct.pack('>B', 0x01))
151s MyMIDI.close()
151s > self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type,
'SysEx')
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:192: AttributeError
151s _ TestMIDIUtils.testTimeShift
__
151s
151s self =
151s
151s def testTimeShift(self):
151s
151s # With one track
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addNote(0, 0, 100, 5, 1, 100)
151s MyMIDI.close()
151s > self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type,
'NoteOn')
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:71: AttributeError
151s ___ TestMIDIUtils.testTuning
___
151s
151s self =
151s
151s def testTuning(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.changeNoteTuning(0, [(1, 440), (2, 880)])
151s MyMIDI.close()
151s > self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type,
'UniversalSysEx')
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:219: AttributeError
151s ___ TestMIDIUtils.testUniversalSysEx
___
151s
151s self =
151s
151s def testUniversalSysEx(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addUniversalSysEx(0,0, 1, 2, struct.pack('>B', 0x01))
151s MyMIDI.close()
151s > self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type,
'UniversalSysEx')
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:204: AttributeError
151s ___ TestMIDIUtils.testWriteVarLength
___
151s
151s self =
151s
151s def testWriteVarLength(self):
151s > self.assertEquals(writeVarLength(0x70), [0x70])
151s E AttributeError: 'TestMIDIUtils' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
151s
151s test_midi.py:37: AttributeError
151s
Bug#1070069: fossil: CVE-2024-24795 unreleated breakage
Le lundi 29 avril 2024, 18:40:39 UTC Barak A. Pearlmutter a écrit : > Bastien, > > Okay, got it. Thanks for letting me know. > > I can cherry-pick that fossil commit, but you know the right magic for > a versioned apache2 breakage and how to deal with proposed-updates. > So I think it would make sense for you to do all of this in a > coordinated fashion? Yes except for unstable where you could go without coordination Fixed apache is 2.4.59-1 So I think a breaks: apache2 (<<2.4.59-1~) is safe on your side (transition will be blocked) When done I will upload a apache2 version with breaks: fossil ( << 2.4.59-2~) I will do the bpu when done with release team Bastien > If that's okay with you, please feel free to just do a regular upload > if you want, or an NMU, as you please. > I will push your changes into the debian fossil branch, unless you'd > like write access to my fossil packaging repo > https://people.debian.org/~bap/fossil.fsl > which I'd be happy to set up. > > Cheers, > > --Barak. > signature.asc Description: This is a digitally signed message part.
Processed: found 1064061 in 2:2.10-21, found 1064061 in 2:2.10-12, found 1064061 in 2:2.9.0-21
Processing commands for cont...@bugs.debian.org:
> found 1064061 2:2.10-21
Bug #1064061 {Done: Bastien Roucariès } [src:wpa] wpa:
CVE-2023-52160
Marked as found in versions wpa/2:2.10-21.
> found 1064061 2:2.10-12
Bug #1064061 {Done: Bastien Roucariès } [src:wpa] wpa:
CVE-2023-52160
Marked as found in versions wpa/2:2.10-12.
> found 1064061 2:2.9.0-21
Bug #1064061 {Done: Bastien Roucariès } [src:wpa] wpa:
CVE-2023-52160
Marked as found in versions wpa/2:2.9.0-21.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1064061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070069: fossil: CVE-2024-24795 unreleated breakage
Bastien, Okay, got it. Thanks for letting me know. I can cherry-pick that fossil commit, but you know the right magic for a versioned apache2 breakage and how to deal with proposed-updates. So I think it would make sense for you to do all of this in a coordinated fashion? If that's okay with you, please feel free to just do a regular upload if you want, or an NMU, as you please. I will push your changes into the debian fossil branch, unless you'd like write access to my fossil packaging repo https://people.debian.org/~bap/fossil.fsl which I'd be happy to set up. Cheers, --Barak.
Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read
Hello all, > These messages with "only only (n)/(n+1) of needed bytes read" seem to > be characteristic. As well as being a FTBFS, this is also an autopkgtest > regression when upgrading curl, which is one of several factors preventing > curl from migrating; that, in turn, blocks elfutils, which blocks GLib, > which will likely be blocking a significant chunk of the 64-bit time_t > transition. I believe this is an issue on ruby-curb and not on curl, check the following thread on curl-library for details and possible solutions: https://curl.se/mail/lib-2024-03/0054.html Cheers, -- Samuel Henrique
Bug#1070055: marked as done (toil: FTBFS: ModuleNotFoundError: No module named 'pytz')
Your message dated Mon, 29 Apr 2024 17:50:32 + with message-id and subject line Bug#1070055: fixed in toil 6.1.0-4 has caused the Debian Bug report #1070055, regarding toil: FTBFS: ModuleNotFoundError: No module named 'pytz' 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.) -- 1070055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:toil Version: 6.1.0-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config I: pybuild base:311: python3.11 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build I: pybuild base:311: /usr/bin/python3.12 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/exceptions.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/deferred.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/serviceManager.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/realtimeLogger.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/leader.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/toilState.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/bus.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/job.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/worker.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/resource.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/version.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/statsAndLogging.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/common.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil creating /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/utils.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/fileJobStore.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/conftest.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/abstractJobStore.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/googleJobStore.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores creating /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/ec2nodes.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/exceptions.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/resources.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/docker.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/threading.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/objects.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/throttle.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/expando.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/memoize.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/accelerators.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/retry.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/humanize.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/iterables.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/generatedEC2Lists.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/compatibility.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/bioio.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/misc.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/io.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib
Bug#1070019: [Pkg-utopia-maintainers] Bug#1070019: udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev
* Chris Hofstaedtler [240429 15:24]:
> > udisks2's autopkgtest fails when tried together with util-linux 2.40. An
> > example can be seen here:
> > https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/
> >
> > 537s ==
> > 537s FAIL: test_ext4 (__main__.FS.test_ext4)
> > 537s fs: ext4
> > 537s --
> > 537s Traceback (most recent call last):
> > 537s File
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line
> > 1107, in _do_udisks_check
> > 537s cd_fs.call_mount_sync(ro_options, None)
> > 537s gi.repository.GLib.GError: udisks-error-quark:
> > GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1
> > at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call
> > failed: /dev/sr1: Can't open blockdev (0)
> > 537s
> > 537s During handling of the above exception, another exception occurred:
> > 537s
> > 537s Traceback (most recent call last):
> > 537s File
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line
> > 725, in test_ext4
> > 537s self._do_fs_check('ext4')
> > 537s File
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line
> > 894, in _do_fs_check
> > 537s self._do_udisks_check(fs_type)
> > 537s File
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line
> > 1112, in _do_udisks_check
> > 537s self.fail('Mounting read-only device with \'rw\' option failed'
> > 537s AssertionError: Mounting read-only device with 'rw' option failedwith
> > an unexpected error.
> > 537s Got: udisks-error-quark:
> > GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1
> > at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call
> > failed: /dev/sr1: Can't open blockdev (0)
> > 537s Expected: 'is write-protected but explicit read-write mode requested'
> > or 'is write-protected but `rw' option given'
> I won't get to it this week (also re: stable v2.40.1), but maybe
> someone else has seen this failure already?
Having said that, it seems likely the test was broken by this
change in util-linux:
libmount: report kernel message from new API
https://github.com/util-linux/util-linux/commit/9da5644e414cdc318f0311260dabc6035c85b58e
I don't know if the error messages are supposed to be stable or not,
but it looks like a very intentional change :-)
Orthogonally, "/dev/sr1: Can't open blockdev" seems not very
informative if it's supposed to mean "write-protected but `rw'
option given".
Chris
Processed: Retitle
Processing commands for cont...@bugs.debian.org: > retitle 1069378 picom: FTBFS: Package xcb-dri3 was not found in the > pkg-config search path Bug #1069378 [src:picom] picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option' Changed Bug title to 'picom: FTBFS: Package xcb-dri3 was not found in the pkg-config search path' from 'picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option''. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Blocks
Processing commands for cont...@bugs.debian.org: > block 1069378 by 1069408 Bug #1069378 [src:picom] picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option' 1069378 was not blocked by any bugs. 1069378 was not blocking any bugs. Added blocking bug(s) of 1069378: 1069408 > thanks Stopping processing here. Please contact me if you need assistance. -- 1069378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069378: picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option'
block -1 by 1069408 thanks Hi, The title of this bug is not a compilation error, it's a feature test. This is actually failing because of 1069408. >> Pkg-config error with 'xcb-present': Could not generate cflags for >> xcb-present: >> Package xcb-dri3 was not found in the pkg-config search path. >> Perhaps you should add the directory containing `xcb-dri3.pc' >> to the PKG_CONFIG_PATH environment variable >> Package 'xcb-dri3', required by 'xcb-present', not found >> >> Dependency lookup for xcb-present with method 'pkgconfig' failed: Could not >> generate cflags for xcb-present: >> Package xcb-dri3 was not found in the pkg-config search path. >> Perhaps you should add the directory containing `xcb-dri3.pc' >> to the PKG_CONFIG_PATH environment variable >> Package 'xcb-dri3', required by 'xcb-present', not found >> >> CMake binary for host machine is cached as not found >> Dependency lookup for xcb-present with method 'cmake' failed: CMake binary >> for machine host machine not found. Giving up. >> Run-time dependency xcb-present found: NO >> >> ../src/meson.build:31:15: ERROR: Dependency lookup for xcb-present with >> method 'pkgconfig' failed: Could not generate cflags for xcb-present: >> Package xcb-dri3 was not found in the pkg-config search path. >> Perhaps you should add the directory containing `xcb-dri3.pc' >> to the PKG_CONFIG_PATH environment variable >> Package 'xcb-dri3', required by 'xcb-present', not found Cheers, Nikos
Processed: severity of 1067837 is important
Processing commands for cont...@bugs.debian.org:
> severity 1067837 important
Bug #1067837 {Done: Antoine Beaupré } [src:tremotesf]
tremotesf: FTBFS on armel (dh_auto_build: error: ninja -j8 -v returned exit
code 1)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068027: marked as done (FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘time_t’ {aka ‘long long int’})
Your message dated Mon, 29 Apr 2024 16:54:52 +
with message-id
and subject line Bug#1068027: fixed in tcptrack 1.4.3-2
has caused the Debian Bug report #1068027,
regarding FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘time_t’ {aka ‘long long int’}
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.)
--
1068027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcptrack
Version: 1.4.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=tcptrack=armhf=1.4.3-1%2Bb2=1711727713=0
TextUI.cc: In member function ‘void TextUI::drawui()’:
TextUI.cc:312:35: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
312 | printw("%lds",ic->getIdleSeconds());
| ~~^
| | |
| long int time_t {aka
long long int}
| %lld
TextUI.cc:314:35: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
314 | printw("%ldm",ic->getIdleSeconds()/60);
| ~~^ ~~~
| | |
| long inttime_t {aka
long long int}
| %lld
TextUI.cc:316:35: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
316 | printw("%ldh",ic->getIdleSeconds()/3600);
| ~~^ ~
| | |
| long inttime_t {aka
long long int}
| %lld
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: tcptrack
Source-Version: 1.4.3-2
Done: Chow Loong Jin
We believe that the bug you reported is fixed in the latest version of
tcptrack, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chow Loong Jin (supplier of updated tcptrack 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, 30 Apr 2024 00:24:17 +0800
Source: tcptrack
Built-For-Profiles: noudeb
Architecture: source
Version: 1.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Chow Loong Jin
Changed-By: Chow Loong Jin
Closes: 1068027
Changes:
tcptrack (1.4.3-2) unstable; urgency=medium
.
* [70f0e36] Update printf format patch for new time_t size (Closes: #1068027)
* [749d073] Update outdated libncurses5-dev build-dep
Checksums-Sha1:
c4d690d253fb07c126d14f3a220fc48aa2716f3e 1883 tcptrack_1.4.3-2.dsc
8928f841dfaf7e8617c5b4257c59338ac3b071cf 3668 tcptrack_1.4.3-2.debian.tar.xz
21405797abd6d8325ed3764fdff5880fa195c752 7675 tcptrack_1.4.3-2_source.buildinfo
Checksums-Sha256:
c43052e6eb23c3ec1c094e280dc05830ce9bd4aeed50db3060855038c5235284 1883
tcptrack_1.4.3-2.dsc
ac1b79cb191c74b6efe966ed76deb24bb870a94bf0c007ac5f83b0e755947715 3668
tcptrack_1.4.3-2.debian.tar.xz
Processed: tagging 1069074 ...
Processing commands for cont...@bugs.debian.org: > tags 1069074 + upstream Bug #1069074 [src:totalopenstation] totalopenstation: FTBFS: failing tests Added tag(s) upstream. > forwarded 1069074 > https://github.com/totalopenstation/totalopenstation/issues/173 Bug #1069074 [src:totalopenstation] totalopenstation: FTBFS: failing tests Set Bug forwarded-to-address to 'https://github.com/totalopenstation/totalopenstation/issues/173'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070016: quake4: hard-coded dependencies on pre-t64 libraries
On Mon, 29 Apr 2024 at 17:12:05 +0200, Sebastian Ramacher wrote: > It will also help dak to decruft the pre-t64 from unstable and render > game-data-packages as good on the transition trackers. OK. Would it be OK to make these dependencies be of the form "libasound2t64 | libasound2" and so on, or is it a requirement that we use only the new name? The version of game-data-packager in testing/unstable has generally remained installable on older suites like stable, and I'd prefer that to remain true if possible (but if that's a problem for the transition, then we can sacrifice that desirable property to simplify things). game-data-packager generates non-distributable .deb packages which can be installed onto end-user systems, and some of those have dependencies too, of which at least libsmpeg-0.4.so.0 has been affected by this transition. To avoid needing to know the target Debian release when generating those packages, I'd prefer to turn that into a dependency on libsmpeg0t64 | libsmpeg0 rather than just libsmpeg0t64 if that isn't going to be disruptive. I believe libasound2t64 is the only one of these dependencies that will affect the packages in contrib. smcv
Processed: Re: frr: FTBFS on armel: /usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to `__atomic_store_8'
Processing commands for cont...@bugs.debian.org: > tag 1067077 +pending Bug #1067077 [src:frr] frr: FTBFS on armel: /usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to `__atomic_store_8' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067077: frr: FTBFS on armel: /usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to `__atomic_store_8'
tag 1067077 +pending thanks Hi, my initial attempt in 10.0-0.2 to link with libatomic didn't work, I've fixed that locally but a build to confirming on an armel porterbox is runnning before uploading 10.0-0.3 in some minutes.. Regards, Daniel
Bug#1067837: marked as done (tremotesf: FTBFS on armel (dh_auto_build: error: ninja -j8 -v returned exit code 1))
Your message dated Mon, 29 Apr 2024 11:09:59 -0400
with message-id <87le4wfbnc@angela.anarc.at>
and subject line Re: Bug#1067837: tremotesf: FTBFS on armel (dh_auto_build:
error: ninja -j8 -v returned exit code 1)
has caused the Debian Bug report #1067837,
regarding tremotesf: FTBFS on armel (dh_auto_build: error: ninja -j8 -v
returned exit code 1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1067837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tremotesf
Severity: serious
Tags: ftbfs
Control: found -1 2.6.0-1
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
tremotesf fails to build on armel.
FYI:
https://buildd.debian.org/status/fetch.php?pkg=tremotesf=armel=2.6.0-1=1705039418=0
[96/131] /usr/bin/c++ -DFMT_SHARED -DQT_CORE_LIB -DQT_DBUS_LIB
-DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050e00
-DQT_GUI_LIB -DQT_MESSAGELOGCONTEXT -DQT_NETWORK_LIB -DQT_NO_DEBUG
-DQT_WIDGETS_LIB -DTREMOTESF_APP_ID=\"org.equeim.Tremotesf\"
-DTREMOTESF_APP_NAME=\"T remotesf\"
-DTREMOTESF_EXECUTABLE_NAME=\"tremotesf\"
-DTREMOTESF_UNIX_FREEDESKTOP -DTREMOTESF_VERSION=\"2.6.0\"
-I/home/kenhys/work/tremotes f-2.6.0/obj-arm-linux-gnueabi/src
-I/home/kenhys/work/tremotesf-2.6.0/src
-I/home/kenhys/work/tremotesf-2.6.0/obj-arm-linux-gnueabi/src/trem
otesf_objects_autogen/include
-I/usr/include/arm-linux-gnueabi/qt5/QtConcurrent -isystem
/usr/include/arm-linux-gnueabi/qt5 -isystem /usr/in
clude/arm-linux-gnueabi/qt5/QtCore -isystem
/usr/lib/arm-linux-gnueabi/qt5/mkspecs/linux-g++ -isystem
/usr/include/arm-linux-gnueabi/qt5/QtN etwork -isystem
/usr/include/arm-linux-gnueabi/qt5/QtWidgets -isystem
/usr/include/arm-linux-gnueabi/qt5/QtGui -isystem
/usr/include/KF5/KWi dgetsAddons -isystem /usr/include/KF5 -isystem
/usr/include/arm-linux-gnueabi/qt5/QtDBus -isystem
/usr/include/KF5/KWindowSystem -g -O2 -ffi
le-prefix-map=/home/kenhys/work/tremotesf-2.6.0=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARG EFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++20 -Wall
-Wextra -Wpedantic -Wcast-align -Woverl oaded-virtual -Wconversion
-Wsign-conversion -Wdouble-promotion -Wformat=2 -Werror=format
-Werror=non-virtual-dtor -Werror=return-type -Wlog ical-op -fPIC -MD
-MT
src/CMakeFiles/tremotesf_objects.dir/ui/notificationscontroller_freedesktop.cpp.o
-MF src/CMakeFiles/tremotesf_objects
.dir/ui/notificationscontroller_freedesktop.cpp.o.d -o
src/CMakeFiles/tremotesf_objects.dir/ui/notificationscontroller_freedesktop.cpp.o
-c
/home/kenhys/work/tremotesf-2.6.0/src/ui/notificationscontroller_freedesktop.cpp
ninja: build stopped: subcommand failed. dh_auto_build: error: cd
obj-arm-linux-gnueabi && LC_ALL=C.UTF-8 ninja -j8 -v returned exit
code 1 Traceback (most recent call last): File
"/usr/bin/dh_ctest_build", line 33, in
sys.exit(load_entry_point('dh-cmake==0.6.2', 'console_scripts',
'dh_ctest_build')())
^^
File "/usr/lib/python3/dist-packages/dhcmake/ctest.py", line 229, in
build dhctest.build() File
"/usr/lib/python3/dist-packages/dhcmake/common.py", line 50, in
wrapped return func(self, *args, **kargs) ^^
File "/usr/lib/python3/dist-packages/dhcmake/ctest.py", line 174, in
build self.do_ctest_step("build", "dh_auto_build") File
"/usr/lib/python3/dist-packages/dhcmake/ctest.py", line 99, in
do_ctest_step self.do_cmd([cmd, *self.parsed_args]) File
"/usr/lib/python3/dist-packages/dhcmake/common.py", line 187, in
do_cmd subprocess.run(args, stdout=self.stdout, stderr=self.stderr,
File "/usr/lib/python3.11/subprocess.py", line 571, in run raise
CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['dh_auto_build',
'-O--buildsystem=cmake+ninja']' returned non-zero exit status 25.
make: *** [debian/rules:4: build] Error 1
Regards,
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: armel (armv8l)
Kernel: Linux 6.1.0-18-arm64 (SMP w/8 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Control: severity -1 important
Hi,
It looks like this package, upstream, just cannot compile on armel at
all.
Bug#1070069: fossil: CVE-2024-24795 unreleated breakage
Package: fossil Severity: serious Justification: break unreleated package affects: apache2 Dear Maintainer, CVE-2024-24795 is fixed in apache2. However it break fossil You need to apply https://fossil-scm.org/home/info/f4ffefe708793b03 See bug here: https://bz.apache.org/bugzilla/show_bug.cgi?id=68905 I can help here and do proposed update We also need to use breaks relationship in apache2, in order to allow smooth upgrade Bastien signature.asc Description: This is a digitally signed message part.
Bug#1070016: quake4: hard-coded dependencies on pre-t64 libraries
On 2024-04-28 18:39:22 +0100, Simon McVittie wrote: > On Sun, 28 Apr 2024 at 17:27:21 +0200, Sebastian Ramacher wrote: > > quake4 has hard-coded dependencies on shared libraries (at least > > libasound2) that were renamed as part of the t64 transition. Please > > update the dependencies accordingly. > > quake4 is i386-only, and i386 has Provides for the old names and no real > ABI break, so I don't think this is necessarily RC - although updating > quake4 in src:game-data-packager might help apt to choose better upgrade > paths, so it's a valid bug. > > (The i386 binaries referenced by quake4 - really in the quake4-bin package > produced by game-data-packager - are proprietary and non-modifiable, > and target the pre-t64 ABI.) It will also help dak to decruft the pre-t64 from unstable and render game-data-packages as good on the transition trackers. Cheer -- Sebastian Ramacher
Bug#1067077: atomic operations on 64-bit time_t
On 2024-04-29 16:45:16 +0200, David Lamparter wrote: > On Mon, Mar 18, 2024 at 12:42:56AM +0100, Sebastian Ramacher wrote: > > Source: frr > > Version: 9.1-0.1 > > Justification: fails to build from source (but built successfully in the > > past) > [...] > > https://buildd.debian.org/status/fetch.php?pkg=frr=armel=9.1-0.1=1710631814=0 > [...] > > ./build/../bgpd/bgp_vty.c:13678:(.text+0x1d934): undefined reference to > > `__atomic_load_8' > [...] > > This is due to FRR using "_Atomic time_t", which ... with the 64-bit > time_t transition is now 8 bytes, and armel, hppa, m68k, powerpc and sh4 > can't do 64-bit atomic ops... Linking with -latomic fixes that. Cheers > > I'm not sure what the best fix for this is, I looked at > https://wiki.debian.org/ReleaseGoals/64bit-time but there is no mention > of atomic ops on time_t. Googling didn't yield anything either. Is frr > the only package using "_Atomic time_t"? > > Input appreciated... > > > -equi (David) -- Sebastian Ramacher
Bug#1069254: nwipe: FTBFS: configure: error: libconfig library not found
Hi, On 2024-04-29 10:28, Bo YU wrote: Tags: patch hi, On Thu, Apr 18, 2024 at 10:00:30PM +0200, Sebastian Ramacher wrote: checking for libconfig... no checking for main in -llibconfig... no configure: error: libconfig library not found It seems it shuold use libconfig-dev. Thanks didn't have the time to test/verify this yet. Will test/fix and upload in a few days. Kind regards, Martijn van Brummelen Cheers -- Sebastian Ramacher
Bug#1067077: atomic operations on 64-bit time_t
On Mon, Mar 18, 2024 at 12:42:56AM +0100, Sebastian Ramacher wrote: > Source: frr > Version: 9.1-0.1 > Justification: fails to build from source (but built successfully in the past) [...] > https://buildd.debian.org/status/fetch.php?pkg=frr=armel=9.1-0.1=1710631814=0 [...] > ./build/../bgpd/bgp_vty.c:13678:(.text+0x1d934): undefined reference to > `__atomic_load_8' [...] This is due to FRR using "_Atomic time_t", which ... with the 64-bit time_t transition is now 8 bytes, and armel, hppa, m68k, powerpc and sh4 can't do 64-bit atomic ops... I'm not sure what the best fix for this is, I looked at https://wiki.debian.org/ReleaseGoals/64bit-time but there is no mention of atomic ops on time_t. Googling didn't yield anything either. Is frr the only package using "_Atomic time_t"? Input appreciated... -equi (David)
Bug#1069438: marked as done (cbmc: FTBFS on armhf: make[4]: *** [Makefile:13: test] Error 1)
Your message dated Mon, 29 Apr 2024 14:36:56 + with message-id and subject line Bug#1069438: fixed in cbmc 5.95.1-5 has caused the Debian Bug report #1069438, regarding cbmc: FTBFS on armhf: make[4]: *** [Makefile:13: test] Error 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.) -- 1069438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cbmc Version: 5.95.1-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[4]: Entering directory '/<>/regression/cbmc' > Makefile:40: warning: overriding recipe for target 'clean' > ../../src/common:246: warning: ignoring old recipe for target 'clean' > Loading > 1114 tests found > > Running tests > Running ACSL/operators.desc [[32mOK[0m] in 0 seconds > Running ACSL/quantifier-precedence.desc [[32mOK[0m] in 0 seconds > Running ASHR1/test.desc [[32mOK[0m] in 0 seconds > Running Address_of1/test.desc [[32mOK[0m] in 0 seconds > Running Address_of2/test.desc [[32mOK[0m] in 0 seconds > Running Anonymous_Struct1/test.desc [[32mOK[0m] in 1 seconds > Running Anonymous_Struct2/test.desc [[32mOK[0m] in 0 seconds > Running Anonymous_Struct3/test.desc [[32mOK[0m] in 0 seconds > Running Array_Access1/test.desc [[32mOK[0m] in 0 seconds > Running Array_Access2/test.desc [[32mOK[0m] in 0 seconds > Running Array_Access3/test.desc [[32mOK[0m] in 0 seconds > Running Array_Initialization1/test.desc [[32mOK[0m] in 0 seconds > Running Array_Initialization2/test.desc [[32mOK[0m] in 0 seconds > Running Array_Initialization3/test.desc [[32mOK[0m] in 0 seconds > Running Array_Pointer1/test.desc [[32mOK[0m] in 0 seconds > Running Array_Pointer2/test.desc [[32mOK[0m] in 0 seconds > Running Array_Pointer3/test.desc [[32mOK[0m] in 0 seconds > Running Array_Pointer4/test.desc [[32mOK[0m] in 0 seconds > Running Array_Pointer5/test.desc [[32mOK[0m] in 0 seconds > Running Array_Pointer6/test.desc [[32mOK[0m] in 0 seconds > Running Array_Pointer7/test.desc [[32mOK[0m] in 0 seconds > Running Array_Propagation1/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF1/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF10/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF11/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF12/test.desc [[32mOK[0m] in 1 seconds > Running Array_UF13/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF14/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF15/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF16/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF17/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF18/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF19/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF2/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF20/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF21/test.desc [[32mOK[0m] in 1 seconds > Running Array_UF22/test.desc [SKIPPED] > Running Array_UF3/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF4/test.desc [SKIPPED] > Running Array_UF5/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF6/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF7/test.desc [[32mOK[0m] in 0 seconds > Running Array_UF8/test.desc [SKIPPED] > Running Array_UF9/test.desc [[32mOK[0m] in 0 seconds > Running Array_operations1/full-slice.desc [[32mOK[0m] in 0 seconds > Running Array_operations1/test.desc [[32mOK[0m] in 0 seconds > Running Array_operations2/test.desc [[32mOK[0m] in 0 seconds > Running Associativity1/test.desc [[32mOK[0m] in 0 seconds > Running Assumption1/test.desc [[32mOK[0m] in 0 seconds > Running BV_Arithmetic1/test.desc [[32mOK[0m] in 1 seconds > Running BV_Arithmetic2/test.desc [[32mOK[0m] in 0 seconds > Running BV_Arithmetic3/test.desc [[32mOK[0m] in 0 seconds > Running BV_Arithmetic4/test.desc [[32mOK[0m] in 0 seconds > Running BV_Arithmetic5/test.desc [[32mOK[0m] in 0 seconds > Running BV_Arithmetic6/test.desc [[32mOK[0m] in 0 seconds > Running Bitfields1/test.desc [[32mOK[0m] in 0 seconds > Running Bitfields2/test.desc [[32mOK[0m] in 0 seconds > Running Bitfields3/paths.desc [[32mOK[0m] in 1 seconds >
Bug#1069427: macaulay2: FTBFS on armhf: make[4]: *** [Makefile:50: check-ForeignFunctions] Error 1
Control: tags -1 unreproducible Control: severity -1 important On Sat 20 Apr 2024 08:57:46 AM -04, Lucas Nussbaum wrote: --no-preload --stop --silent -e "needsPackage(\"ForeignFunctions\",LoadDocumentation=>true,DebuggingMode=>true)" -e "debug Core; argumentMode = defaultMode - SetUlimit" -e "check(ForeignFunctions,UserMode=>false,Verbose=>true); exit 0" -- capturing check(0, "ForeignFunctions")-- SIGSEGV -* stack trace, pid: 2593432 0# stack_trace(std::ostream&, bool) at ./M2/Macaulay2/d/main.cpp:119 1# segv_handler at ./M2/Macaulay2/d/main.cpp:235 2# 0xF64686C0 in /lib/arm-linux-gnueabihf/libc.so.6 -- end stack trace *- make[4]: *** [Makefile:50: check-ForeignFunctions] Error 1 I haven't been able to reproduce this build error after several attempts on armhf machines, so I'm dropping the severity of this bug to "important". signature.asc Description: PGP signature
Processed: Re: Bug#1069427: macaulay2: FTBFS on armhf: make[4]: *** [Makefile:50: check-ForeignFunctions] Error 1
Processing control commands: > tags -1 unreproducible Bug #1069427 [src:macaulay2] macaulay2: FTBFS on armhf: make[4]: *** [Makefile:50: check-ForeignFunctions] Error 1 Added tag(s) unreproducible. > severity -1 important Bug #1069427 [src:macaulay2] macaulay2: FTBFS on armhf: make[4]: *** [Makefile:50: check-ForeignFunctions] Error 1 Severity set to 'important' from 'serious' -- 1069427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070063: Remmina fails to connect with Windows systems: Protocol Security Negotiation Failure (older release works)
Package: remmina Version: 1.4.35+dfsg-1+b1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, when I try to connect to a windows (11) system, I get errors saying something like "check security protocol negotiation". When I set it the security protocol negotiation to automatic detection, there is a connection attempt, but the credentials are not accepted. As I haven't changed anything in the RDP setup, I tried downgrading to version 1.4.34, and everything works now as expected again. I'm not quite sure if this issue is related to https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2062177 and/or https://gitlab.com/Remmina/Remmina/-/issues/3090, or if this is a complete different issue. Regards, Daniel - -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE 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 remmina depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-4+b1 ii libavahi-client3 0.8-13+b2 ii libavahi-common3 0.8-13+b2 ii libavahi-ui-gtk3-00.8-13+b2 ii libayatana-appindicator3-10.5.93-1+b1 ii libc6 2.37-19 ii libcairo2 1.18.0-3+b1 ii libcurl4t64 [libcurl4]8.7.1-4 ii libgcrypt20 1.10.3-2+b1 ii libglib2.0-0t64 [libglib2.0-0]2.78.4-7 ii libgtk-3-0t64 [libgtk-3-0]3.24.41-4 ii libjson-glib-1.0-01.8.0-2+b1 ii libpango-1.0-01.52.1+ds-1 ii libsodium23 1.0.18-1+b1 ii libssh-4 0.10.6-2+b1 ii libssl3t64 [libssl3] 3.2.1-3 ii libvte-2.91-0 0.75.92-1 ii remmina-common1.4.34+dfsg-1 Versions of packages remmina recommends: ii remmina-plugin-rdp 1.4.34+dfsg-1 ii remmina-plugin-secret 1.4.34+dfsg-1 ii remmina-plugin-vnc 1.4.34+dfsg-1 Versions of packages remmina suggests: ii remmina-plugin-exec 1.4.34+dfsg-1 pn remmina-plugin-kwallet pn remmina-plugin-python ii remmina-plugin-spice1.4.34+dfsg-1 ii remmina-plugin-www 1.4.34+dfsg-1 pn remmina-plugin-x2go - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmYvo20ACgkQS80FZ8KW 0F019w/+L5a7P2ISCuVfYN0TDIXNvW97noLHv0798jJ3cX2zX1DJ0CSyF5oLXLbt ctVCobfZitMax1mUCpxgQYbEody6bZVRMdnb1SQEbiue+sx5iqsd+tYDmfwNThV9 FpLs203BuFg2CmjblhxpJ2AWlpCxQJUv39EVNtYFDnCHFW0hFbtdtIx48d6n7Byt N4Ys0d5z9c+BeTpSMgT26DeVoxE0dIGaL2/tC1X4/mjlf23NMZyweKHS1YSo8/v7 Or6Z0tAFhdSF49320LNCqu6Y/jLwW9/gcJuzkRT6QBc6kBThOJvtSiLvREdlfytm Ou421mvqU7nG3FKM0g987wgCZw/3ZmizsZESh4J1b2yrXc/Lr+T+XmEA8v3u5e+j XMy7rJ7a5mWZt3iaikCxuq3RHQJM4eAhtfp1Obp5gyS06+65SB2vppWPHIjIcOfh X6uqULCcSITwesyOWvd0w/iPmVrGaSjJCp6VrzWVXngKOdYWnyU+cV+yPVcP+GKE T/iSDmssoeoFE1AjF8O+fSu/qP2E0VnsJ+cYpkU4LrcZ+RiLpNolTlws0Jgw1Q/n 4x3pDc01KH7aSdEqZU8DB4/CXgiPsvxEWqcTX3gTX33Q5LXXtOmZOsSnfD7X3OqG 9CQsUosvRuEQyaxFG4KGgiwnllJHcSvn1Moa1uaIGBqeJuxBgvI= =2ZY6 -END PGP SIGNATURE-
Bug#1070062: waylandpp: Missing build-depends libwayland-egl1-mesa
Source: waylandpp Version: 1.0.0-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The libwayland-egl1-mesa package was a transitional package for libegl1 and libwayland-egl1 and has been removed. You will need to update your build-depends appropriately. Scott K
Bug#1069549: racket: FTBFS on armel: dh_install: error: missing files, aborting
Control: severity -1 important > Source: racket > Version: 8.12+dfsg1-7 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel OK, I figured out why this doesn't show up on the buildd's: they don't build the arch all packages on armel. For many years, armel hasn't been able to build the documentation for racket, and it has been disabled there. After some informal consultation with the release team I'm downgrading this bug to non-RC. I'll work on having more clear diagnostics for the build failure. I don't know how common this scenario is, but it might make sense to restrict such rebuilds to arch:any on armel (and armhf), depending on your goals of course.
Processed: Re: Bug#1069549: racket: FTBFS on armel: dh_install: error: missing files, aborting
Processing control commands: > severity -1 important Bug #1069549 [src:racket] racket: FTBFS on armel: dh_install: error: missing files, aborting Severity set to 'important' from 'serious' -- 1069549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070019: [Pkg-utopia-maintainers] Bug#1070019: udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev
Dear util-linux@,
in Debian, udisks2 2.10.1-6 (autopkg-)tests fail with util-linux
2.40, but passed with 2.39. We are not yet sure if this is directly
caused by util-linux, but it seems somewhat likely.
I won't get to it this week (also re: stable v2.40.1), but maybe
someone else has seen this failure already?
> udisks2's autopkgtest fails when tried together with util-linux 2.40. An
> example can be seen here:
> https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/
>
> 537s ==
> 537s FAIL: test_ext4 (__main__.FS.test_ext4)
> 537s fs: ext4
> 537s --
> 537s Traceback (most recent call last):
> 537s File
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line
> 1107, in _do_udisks_check
> 537s cd_fs.call_mount_sync(ro_options, None)
> 537s gi.repository.GLib.GError: udisks-error-quark:
> GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at
> /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call
> failed: /dev/sr1: Can't open blockdev (0)
> 537s
> 537s During handling of the above exception, another exception occurred:
> 537s
> 537s Traceback (most recent call last):
> 537s File
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 725,
> in test_ext4
> 537s self._do_fs_check('ext4')
> 537s File
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 894,
> in _do_fs_check
> 537s self._do_udisks_check(fs_type)
> 537s File
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line
> 1112, in _do_udisks_check
> 537s self.fail('Mounting read-only device with \'rw\' option failed'
> 537s AssertionError: Mounting read-only device with 'rw' option failedwith an
> unexpected error.
> 537s Got: udisks-error-quark:
> GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at
> /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call
> failed: /dev/sr1: Can't open blockdev (0)
> 537s Expected: 'is write-protected but explicit read-write mode requested' or
> 'is write-protected but `rw' option given'
>
> I do not understand what this error means, or what the underlying problem is.
> Please investigate.
For context, Debian's util-linux 2.40-7 should have everything from
2.40 stable up to a8aa0b5f154a44557f5bae5a4027bdbfe42b0323.
Chris
Bug#1069406: marked as done (openvswitch: FTBFS on arm64: | ./_debian/./_debian/conftest.c:48:(.text.startup+0xc): undefined reference to `pow')
Your message dated Mon, 29 Apr 2024 12:53:15 +
with message-id
and subject line Bug#1069406: fixed in openvswitch 3.3.0-2
has caused the Debian Bug report #1069406,
regarding openvswitch: FTBFS on arm64: |
./_debian/./_debian/conftest.c:48:(.text.startup+0xc): undefined reference to
`pow'
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.)
--
1069406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvswitch
Version: 3.3.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/_debian'
> set /bin/bash '../tests/testsuite' -C tests
> AUTOTEST_PATH=utilities:vswitchd:ovsdb:vtep:tests:ipsec::; \
> "$@" --recheck || \
> (test -z "$(find /<>/_debian/tests/testsuite.dir -name
> 'sanitizers.*')" && \
> test X'' = Xyes && "$@" --recheck)
> :4: DeprecationWarning: pkg_resources is deprecated as an API. See
> https://setuptools.pypa.io/en/latest/pkg_resources.html
> ## - ##
> ## openvswitch 3.3.0 test suite. ##
> ## - ##
>
> ovsdb-server miscellaneous features
>
> 1890: SSL db: implementation FAILED
> (ovsdb-server.at:939)
>
> vlog
>
> 2531: vlog - Python3 FAILED (vlog.at:9)
>
> ## - ##
> ## Test results. ##
> ## - ##
>
> ERROR: All 2 tests were run,
> 2 failed unexpectedly.
> ## -- ##
> ## testsuite.log was created. ##
> ## -- ##
>
> Please send `tests/testsuite.log' and all information you think might help:
>
>To:
>Subject: [openvswitch 3.3.0] testsuite: 1890 2531 failed
>
> You may investigate any problem if you feel able to do so, in which
> case the test suite provides a good starting point. Its output may
> be found below `tests/testsuite.dir'.
>
> make[4]: *** [Makefile:6967: check-local] Error 1
> make[4]: Leaving directory '/<>/_debian'
> make[3]: *** [Makefile:5700: check-am] Error 2
> make[3]: Leaving directory '/<>/_debian'
> make[2]: *** [Makefile:5702: check] Error 2
> make[2]: Leaving directory '/<>/_debian'
> ## - ##
> ## openvswitch 3.3.0 test suite. ##
> ## - ##
>
> testsuite: command line was:
> $ ../tests/testsuite -C tests
> AUTOTEST_PATH=utilities:vswitchd:ovsdb:vtep:tests:ipsec:: --recheck
>
> ## - ##
> ## Platform. ##
> ## - ##
>
> hostname = ip-10-84-234-149
> uname -m = aarch64
> uname -r = 6.1.0-15-cloud-arm64
> uname -s = Linux
> uname -v = #1 SMP Debian 6.1.66-1 (2023-12-09)
>
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
>
> /bin/arch = aarch64
> /usr/bin/arch -k = unknown
> /usr/convex/getsysinfo = unknown
> /usr/bin/hostinfo = unknown
> /bin/machine = unknown
> /usr/bin/oslevel = unknown
> /bin/universe = unknown
>
> PATH: /<>/_debian/utilities/
> PATH: /<>/utilities/
> PATH: /<>/_debian/vswitchd/
> PATH: /<>/vswitchd/
> PATH: /<>/_debian/ovsdb/
> PATH: /<>/ovsdb/
> PATH: /<>/_debian/vtep/
> PATH: /<>/vtep/
> PATH: /<>/_debian/tests/
> PATH: /<>/tests/
> PATH: /<>/_debian/ipsec/
> PATH: /<>/ipsec/
> PATH: /<>/_debian/
> PATH: /<>/
> PATH: /usr/local/sbin/
> PATH: /usr/local/bin/
> PATH: /usr/sbin/
> PATH: /usr/bin/
> PATH: /sbin/
> PATH: /bin/
> PATH: /usr/games/
>
> testsuite: atconfig:
> | # Configurable variable values for building test suites.
> | # Generated by ./config.status.
> | # Copyright (C) 2021 Free Software Foundation, Inc.
> |
> | # The test suite will define top_srcdir=/../.. etc.
> | at_testdir='tests'
> | abs_builddir='/<>/_debian/tests'
> | at_srcdir='../../tests'
> | abs_srcdir='/<>/_debian/../tests'
> | at_top_srcdir='../..'
> | abs_top_srcdir='/<>/_debian/..'
> | at_top_build_prefix='../'
> | abs_top_builddir='/<>/_debian'
> |
> | # Backward compatibility with Autotest <= 2.59b:
> | at_top_builddir=$at_top_build_prefix
> |
> |
> | EXEEXT=''
> | AUTOTEST_PATH='tests'
> |
> | SHELL=${CONFIG_SHELL-'/bin/bash'}
>
> testsuite: atlocal:
> | # -*- shell-script -*-
> | HAVE_OPENSSL='yes'
> | OPENSSL_SUPPORTS_SNI='yes'
> | HAVE_UNBOUND='yes'
> | HAVE_BACKTRACE='yes'
> | HAVE_UNWIND='no'
> | EGREP='/usr/bin/grep -E'
> | PYTHON3='/usr/bin/python3'
> | CFLAGS='-g -O2
Processed: Bug#1069876 marked as pending in libsbml
Processing control commands: > tag -1 pending Bug #1069876 [src:libsbml] libsbml: autopkgtest regression Added tag(s) pending. -- 1069876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069876: marked as pending in libsbml
Control: tag -1 pending Hello, Bug #1069876 in libsbml 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/med-team/libsbml/-/commit/6d99ea552c92139739788a722d9303c127e17c9a Hand write the autopkgtest to only test against the default version of Python. Closes: #1069876 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069876
Processed: Bug#1069406 marked as pending in openvswitch
Processing control commands: > tag -1 pending Bug #1069406 [src:openvswitch] openvswitch: FTBFS on arm64: | ./_debian/./_debian/conftest.c:48:(.text.startup+0xc): undefined reference to `pow' Added tag(s) pending. -- 1069406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064311: rdkit: NMU diff for 64-bit time_t transition
Hi, On Wed, 24 Apr 2024 23:57:17 +0200 Chris Hofstaedtler wrote:> An upload with t64 binaries is required as soon as possible. Given the packages have to go to binary-NEW, you must upload with binaries, and then probably follow up with a source-only upload once they are ACCEPTed. t64 binaries for rdkit got accepted to experimental. Should I upload it to unstable, or should I wait for someone else to do that? Best, Andrius
Bug#1069406: marked as pending in openvswitch
Control: tag -1 pending Hello, Bug #1069406 in openvswitch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/openvswitch/-/commit/2ffb373c11bd059e3e64ece23f45146a8756280d Add fix-in-ssl-handshake-failure-test.patch (Closes: #1069406). (this message was generated automatically) -- Greetings https://bugs.debian.org/1069406
Bug#1069803: marked as done (php-codeigniter-framework tries pip install during build)
Your message dated Mon, 29 Apr 2024 12:37:47 +
with message-id
and subject line Bug#1069803: fixed in php-codeigniter-framework 3.1.13+dfsg1-4
has caused the Debian Bug report #1069803,
regarding php-codeigniter-framework tries pip install during build
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.)
--
1069803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-codeigniter-framework
Version: 3.1.13+dfsg1-3
Severity: serious
Tags: sid trixie ftbfs
php-codeigniter-framework accesses network resources during the build:
python3 -m venv --system-site-packages --without-pip debian/build-doc/pythonvenv
if ! debian/build-doc/pythonvenv/bin/python -m pip show pycilexer; then \
echo "Installing pycilexer" && \
cd user_guide_src/cilexer && \
../../debian/build-doc/pythonvenv/bin/python -m pip install .; \
fi
WARNING: Package(s) not found: pycilexer
Installing pycilexer
Processing /build/package/package/user_guide_src/cilexer
Installing build dependencies: started
Installing build dependencies: finished with status 'error'
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [7 lines of output]
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
ERROR: Could not find a version that satisfies the requirement
setuptools>=40.8.0 (from versions: none)
ERROR: No matching distribution found for setuptools>=40.8.0
[end of output]
note: This error originates from a subprocess, and is likely not a problem
with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with
pip.
--- End Message ---
--- Begin Message ---
Source: php-codeigniter-framework
Source-Version: 3.1.13+dfsg1-4
Done: Fab Stz
We believe that the bug you reported is fixed in the latest version of
php-codeigniter-framework, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fab Stz (supplier of updated php-codeigniter-framework
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, 27 Apr 2024 07:45:07 +0200
Source: php-codeigniter-framework
Architecture: source
Version: 3.1.13+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers
Changed-By: Fab Stz
Closes: 1069803
Changes:
php-codeigniter-framework (3.1.13+dfsg1-4) unstable; urgency=medium
.
* d/control: add build-dep to python3-setuptools (Closes: #1069803)
Checksums-Sha1:
a22b2fef685971ea9a8e26421f4a13f299541c35 2654
php-codeigniter-framework_3.1.13+dfsg1-4.dsc
048ab59e7c177e61e5df53a45847ff3480800f09 16892
Bug#1070019: [Pkg-utopia-maintainers] Bug#1070019: Bug#1070019: udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev
Am 29.04.24 um 14:03 schrieb Michael Biebl:
It appears that this is a regression introduced in util-linux 2.40-7.
The udisks2 test suite passes with 2.40-6.
So I assume it's one of the upstream changes from
"""
* Import upstream stable/v2.40 up to
a8aa0b5f154a44557f5bae5a4027bdbfe42b0323
* lsns: fix netns use
* libmount: fix comment typo for mnt_fs_get_comment()
* libmount: Fix access check for utab in context
* lsblk: simplify SOURCES code
* findmnt: always zero-terminate SOURCES data
* agetty: Don't override TERM passed by the user
* libsmartcols: reset wrap after calculation
* lslocks: remove a unused local variable
* lslocks: don't abort gathering per-process information even if
opening a /proc/[0-9]* fails
* lsns: tolerate lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failing
with ENOSYS
* lsns: report with warnx if a namespace related ioctl fails with
ENOSYS
* Fix misplaced else in mnt_update_already_done
* findmnt: revise the code for -I and -D option (Closes: #1069634)
* libblkid: topology/ioctl: simplify ioctl handling
* libblkid: topology/ioctl: correctly handle kernel types
* pam_lastlog2: link against liblastlog
* libblkid: Fix segfault when blkid.conf doesn't exist (Closes:
#1069634)
"""
that broke udisks2.
Please disregard what I wrote above. I made a mistake when testing with
a trixie qemu VM and the util-linux packages weren't actually upgraded
but stayed on 2.39
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1070019: [Pkg-utopia-maintainers] Bug#1070019: udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev
Am 28.04.24 um 18:20 schrieb Chris Hofstaedtler:
Source: udisks2
Version: 2.10.1-6
Severity: serious
Hi,
udisks2's autopkgtest fails when tried together with util-linux 2.40. An
example can be seen here:
https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/
537s ==
537s FAIL: test_ext4 (__main__.FS.test_ext4)
537s fs: ext4
537s --
537s Traceback (most recent call last):
537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test",
line 1107, in _do_udisks_check
537s cd_fs.call_mount_sync(ro_options, None)
537s gi.repository.GLib.GError: udisks-error-quark:
GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at
/media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call failed:
/dev/sr1: Can't open blockdev (0)
537s
537s During handling of the above exception, another exception occurred:
537s
537s Traceback (most recent call last):
537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test",
line 725, in test_ext4
537s self._do_fs_check('ext4')
537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test",
line 894, in _do_fs_check
537s self._do_udisks_check(fs_type)
537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test",
line 1112, in _do_udisks_check
537s self.fail('Mounting read-only device with \'rw\' option failed'
537s AssertionError: Mounting read-only device with 'rw' option failedwith an
unexpected error.
537s Got: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed:
Error mounting /dev/sr1 at /media/root/41b1acb1-744c-422a-9071-2dba5368a683:
fsconfig system call failed: /dev/sr1: Can't open blockdev (0)
537s Expected: 'is write-protected but explicit read-write mode requested' or
'is write-protected but `rw' option given'
I do not understand what this error means, or what the underlying problem is.
Please investigate.
It appears that this is a regression introduced in util-linux 2.40-7.
The udisks2 test suite passes with 2.40-6.
So I assume it's one of the upstream changes from
"""
* Import upstream stable/v2.40 up to
a8aa0b5f154a44557f5bae5a4027bdbfe42b0323
* lsns: fix netns use
* libmount: fix comment typo for mnt_fs_get_comment()
* libmount: Fix access check for utab in context
* lsblk: simplify SOURCES code
* findmnt: always zero-terminate SOURCES data
* agetty: Don't override TERM passed by the user
* libsmartcols: reset wrap after calculation
* lslocks: remove a unused local variable
* lslocks: don't abort gathering per-process information even if
opening a /proc/[0-9]* fails
* lsns: tolerate lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failing
with ENOSYS
* lsns: report with warnx if a namespace related ioctl fails with
ENOSYS
* Fix misplaced else in mnt_update_already_done
* findmnt: revise the code for -I and -D option (Closes: #1069634)
* libblkid: topology/ioctl: simplify ioctl handling
* libblkid: topology/ioctl: correctly handle kernel types
* pam_lastlog2: link against liblastlog
* libblkid: Fix segfault when blkid.conf doesn't exist (Closes:
#1069634)
"""
that broke udisks2.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processed: Re: Bug#1066797: gstreamer1.0: FTBFS: tests/check/libs/gstharness.c: Received signal 11 (Segmentation fault)
Processing control commands: > severity -1 important Bug #1066797 [src:gstreamer1.0] gstreamer1.0: FTBFS: tests/check/libs/gstharness.c: Received signal 11 (Segmentation fault) Severity set to 'important' from 'serious' -- 1066797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066797: gstreamer1.0: FTBFS: tests/check/libs/gstharness.c: Received signal 11 (Segmentation fault)
Control: severity -1 important This build failure does not appear to be reproducible on the official buildds and this RC bug is blocking big parts of the t64 transitions so I'm lowering the severity. Thank you, Jeremy Bícha
Bug#1070055: toil: FTBFS: ModuleNotFoundError: No module named 'pytz'
Package: src:toil Version: 6.1.0-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config I: pybuild base:311: python3.11 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build I: pybuild base:311: /usr/bin/python3.12 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/exceptions.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/deferred.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/serviceManager.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/realtimeLogger.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/leader.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/toilState.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/bus.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/job.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/worker.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/resource.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/version.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/statsAndLogging.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil copying src/toil/common.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil creating /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/utils.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/fileJobStore.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/conftest.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/abstractJobStore.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores copying src/toil/jobStores/googleJobStore.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/jobStores creating /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/ec2nodes.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/exceptions.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/resources.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/docker.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/threading.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/objects.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/throttle.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/expando.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/memoize.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/accelerators.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/retry.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/humanize.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/iterables.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/generatedEC2Lists.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/compatibility.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/bioio.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/misc.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/io.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/ec2.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib copying src/toil/lib/conversions.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/lib creating /<>/.pybuild/cpython3_3.12_toil/build/toil/cwl copying src/toil/cwl/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/cwl copying src/toil/cwl/utils.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/cwl copying src/toil/cwl/cwltoil.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/cwl copying src/toil/cwl/conftest.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/cwl creating /<>/.pybuild/cpython3_3.12_toil/build/toil/batchSystems copying src/toil/batchSystems/__init__.py -> /<>/.pybuild/cpython3_3.12_toil/build/toil/batchSystems copying src/toil/batchSystems/abstractGridEngineBatchSystem.py ->
Processed: found 1064516 in 2.0.6-3
Processing commands for cont...@bugs.debian.org: > found 1064516 2.0.6-3 Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 Marked as found in versions ruby-rack/2.0.6-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070053: prometheus-process-exporter: FTBFS: cannot use status.UIDs[1] (variable of type uint64) as string value in argument to strconv.ParseInt
Package: src:prometheus-process-exporter Version: 0.7.10-4 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=golang --builddirectory=/<>/build dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=/<>/build dh_autoreconf -O--buildsystem=golang -O--builddirectory=/<>/build dh_auto_configure -O--buildsystem=golang -O--builddirectory=/<>/build debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- -tags "" -ldflags " -X github.com/prometheus/common/version.Version=0.7.10 -X github.com/prometheus/common/version.Revision=0.7.10-4 -X github.com/prometheus/common/version.Branch=debian/sid -X github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org -X github.com/prometheus/common/version.BuildDate=20240321-15:19:54 -X github.com/prometheus/common/version.GoVersion=go1.22.2" cd build && go install -trimpath -v -p 2 -tags -ldflags " -X github.com/prometheus/common/version.Version=0.7.10 -X github.com/prometheus/common/version.Revision=0.7.10-4 -X github.com/prometheus/common/version.Branch=debian/sid -X github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org -X github.com/prometheus/common/version.BuildDate=20240321-15:19:54 -X github.com/prometheus/common/version.GoVersion=go1.22.2" github.com/ncabatoff/process-exporter github.com/ncabatoff/process-exporter/cmd/process-exporter github.com/ncabatoff/process-exporter/collector github.com/ncabatoff/process-exporter/config github.com/ncabatoff/process-exporter/proc internal/goarch internal/unsafeheader internal/cpu internal/abi internal/bytealg internal/chacha8rand internal/coverage/rtcov internal/godebugs internal/goexperiment internal/goos runtime/internal/atomic runtime/internal/math runtime/internal/sys runtime/internal/syscall internal/itoa math/bits runtime math unicode/utf8 internal/race sync/atomic unicode cmp slices encoding internal/nettrace log/internal unicode/utf16 container/list crypto/internal/alias crypto/subtle crypto/internal/boring/sig vendor/golang.org/x/crypto/cryptobyte/asn1 vendor/golang.org/x/crypto/internal/alias google.golang.org/protobuf/internal/flags google.golang.org/protobuf/internal/set internal/reflectlite sync internal/testlog internal/bisect errors sort strconv io internal/oserror reflect syscall internal/syscall/unix time internal/poll internal/fmtsort internal/safefilepath internal/syscall/execenv path strings io/fs os bytes bufio encoding/binary fmt path/filepath github.com/prometheus/procfs/internal/util golang.org/x/sys/unix github.com/ncabatoff/process-exporter flag github.com/ncabatoff/go-seq/seq encoding/hex github.com/prometheus/procfs/internal/fs context vendor/golang.org/x/net/dns/dnsmessage internal/godebug internal/singleflight internal/intern net/netip runtime/cgo regexp/syntax regexp log encoding/base64 encoding/json net os/user compress/flate hash hash/crc32 compress/gzip crypto crypto/cipher crypto/internal/boring crypto/internal/randutil math/rand math/big crypto/rand crypto/aes crypto/des crypto/internal/edwards25519/field crypto/internal/nistec/fiat github.com/prometheus/procfs embed crypto/internal/nistec crypto/ecdh crypto/elliptic crypto/internal/bigmod crypto/internal/boring/bbig crypto/sha512 encoding/asn1 github.com/ncabatoff/process-exporter/proc # github.com/ncabatoff/process-exporter/proc src/github.com/ncabatoff/process-exporter/proc/read.go:397:40: cannot use status.UIDs[1] (variable of type uint64) as string value in argument to strconv.ParseInt crypto/internal/edwards25519 vendor/golang.org/x/crypto/cryptobyte crypto/ed25519 crypto/hmac crypto/md5 crypto/ecdsa crypto/rc4 crypto/rsa crypto/sha1 crypto/sha256 crypto/dsa crypto/x509/pkix encoding/pem net/url vendor/golang.org/x/crypto/chacha20 vendor/golang.org/x/crypto/internal/poly1305 crypto/x509 vendor/golang.org/x/sys/cpu vendor/golang.org/x/crypto/chacha20poly1305 vendor/golang.org/x/crypto/hkdf vendor/golang.org/x/text/transform vendor/golang.org/x/text/unicode/bidi vendor/golang.org/x/text/secure/bidirule vendor/golang.org/x/text/unicode/norm crypto/tls vendor/golang.org/x/net/idna net/textproto vendor/golang.org/x/net/http/httpguts vendor/golang.org/x/net/http/httpproxy vendor/golang.org/x/net/http2/hpack mime mime/quotedprintable mime/multipart net/http/internal net/http/internal/ascii github.com/beorn7/perks/quantile github.com/cespare/xxhash hash/fnv net/http/httptrace google.golang.org/protobuf/internal/detrand google.golang.org/protobuf/internal/errors net/http google.golang.org/protobuf/encoding/protowire google.golang.org/protobuf/internal/pragma google.golang.org/protobuf/reflect/protoreflect google.golang.org/protobuf/internal/descfmt google.golang.org/protobuf/internal/descopts
Bug#1069819: marked as done (FTBFS: tests failed)
Your message dated Mon, 29 Apr 2024 13:21:54 +0200 with message-id and subject line Fixed has caused the Debian Bug report #1069819, regarding FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-tooz Version: 4.2.0-2 Severity: serious Tags: ftbfs == FAIL: tooz.tests.test_mysql.TestMySQLDriver.test_parsing_blocking_settings tooz.tests.test_mysql.TestMySQLDriver.test_parsing_blocking_settings -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/usr/lib/python3.12/unittest/mock.py", line 1390, in patched return func(*newargs, **newkeywargs) ^ File "/<>/tooz/tests/test_mysql.py", line 113, in test_parsing_blocking_settings with lock(blocking_value): File "/<>/tooz/locking.py", line 29, in __enter__ return self.lock.__enter__(*self.args, **self.kwargs) ^^ File "/<>/tooz/locking.py", line 49, in __enter__ acquired = self.acquire(*args, **kwargs) ^ File "", line 3, in acquire File "/usr/lib/python3.12/unittest/mock.py", line 1134, in __call__ return self._mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1138, in _mock_call return self._execute_mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1211, in _execute_mock_call return self._mock_wraps(*args, **kwargs) ^ TypeError: 'bool' object is not callable == FAIL: tooz.tests.test_mysql.TestMySQLDriver.test_parsing_timeout_settings tooz.tests.test_mysql.TestMySQLDriver.test_parsing_timeout_settings -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/usr/lib/python3.12/unittest/mock.py", line 1390, in patched return func(*newargs, **newkeywargs) ^ File "/<>/tooz/tests/test_mysql.py", line 100, in test_parsing_timeout_settings with lock(blocking_value, timeout): File "/<>/tooz/locking.py", line 29, in __enter__ return self.lock.__enter__(*self.args, **self.kwargs) ^^ File "/<>/tooz/locking.py", line 49, in __enter__ acquired = self.acquire(*args, **kwargs) ^ File "", line 3, in acquire File "/usr/lib/python3.12/unittest/mock.py", line 1134, in __call__ return self._mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1138, in _mock_call return self._execute_mock_call(*args, **kwargs) File "/usr/lib/python3.12/unittest/mock.py", line 1211, in _execute_mock_call return self._mock_wraps(*args, **kwargs) ^ TypeError: 'bool' object is not callable == FAIL: tooz.tests.test_coordination.TestAPI.test_lock_context_manager_acquire_argument tooz.tests.test_coordination.TestAPI.test_lock_context_manager_acquire_argument -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/<>/tooz/tests/__init__.py", line 35, in skip_if_not_implemented return func(*args, **kwargs) ^ File "/<>/tooz/tests/test_coordination.py", line 928, in test_lock_context_manager_acquire_argument with lock(blocking_value): File "/<>/tooz/locking.py", line 29, in __enter__ return self.lock.__enter__(*self.args, **self.kwargs) ^^ File "/<>/tooz/locking.py", line 49, in __enter__ acquired = self.acquire(*args, **kwargs) ^ File "", line 3, in acquire File "/usr/lib/python3.12/unittest/mock.py", line 1134, in __call__ return self._mock_call(*args, **kwargs)
Processed: Re: Bug#1070047: python3-django-pipeline: installs files into aliased locations
Processing control commands: > tags -1 - patch Bug #1070047 [python3-django-pipeline] python3-django-pipeline: installs files into aliased locations Removed tag(s) patch. -- 1070047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070047: python3-django-pipeline: installs files into aliased locations
Control: tags -1 - patch Hi Alexandre, On Mon, Apr 29, 2024 at 12:35:02PM +0200, Alexandre Detiste wrote: > If I revert the NAME change autodep8 breaks on Salsa Dang. I was looking for what I could have broken and didn't see this. > Is there an easy way to have one name for pybuild and another one for > autodep8 ... ? I ll search. I looked at man pybuild and https://wiki.debian.org/Python/Pybuild and neither was particularly enlightening to me. Possibly setting PYBUILD_NAME=pipeline and PYBUILD_DESTDIR=debian/python3-django-pipeline works? Helmut
Bug#1070047: python3-django-pipeline: installs files into aliased locations
Thanks a lot for noticing this. If I revert the NAME change autodep8 breaks on Salsa Is there an easy way to have one name for pybuild and another one for autodep8 ... ? I ll search. The hard way is to define a real test suite. Greetings Le lun. 29 avr. 2024, 12:27, Helmut Grohne a écrit : > Package: python3-django-pipeline > Version: 3.0.0-1 > Severity: serious > Justification: introduces new aliasing > Tags: patch > Control: affects -1 + python3-distutils > User: helm...@debian.org > Usertags: dep17p6 > > The last upload of python3-django-pipeline moved all of its files from > /usr/lib to /lib. Whils this works somewhat on a /usr-merged > installations, it causes subtle bugs due to dpkg not being prepared with > aliasing. In DEP17, we're resolving this by moving all files out of > aliased locations and python3-django-pipelines has just introduced new. > Hence, I'm filing this at RC severity. I think the move was accidental > and can be fixed by dropping the faulty "mv" command in favour of > setting PYBUILD_NAME to the package name rather than the module name. > I'm attaching a patch for your convenience. > > Helmut >
Processed: retitle
Processing commands for cont...@bugs.debian.org: > # not really arm64-specific, dropping arm64 from title > retitle 1069359 python-cooler: FTBFS: FileNotFoundError: [Errno 2] No such > file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool' Bug #1069359 [src:python-cooler] python-cooler: FTBFS on arm64: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool' Changed Bug title to 'python-cooler: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool'' from 'python-cooler: FTBFS on arm64: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool''. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle
Processing commands for cont...@bugs.debian.org: > # not really arm64-specific, dropping arm64 from title > retitle 1069358 font-manager: FTBFS: > ../src/font-manager/ArchiveManager.vala:26.97-26.106: error: internal: > invalid array_length for given dimension Bug #1069358 [src:font-manager] font-manager: FTBFS on arm64: ../src/font-manager/ArchiveManager.vala:26.97-26.106: error: internal: invalid array_length for given dimension Changed Bug title to 'font-manager: FTBFS: ../src/font-manager/ArchiveManager.vala:26.97-26.106: error: internal: invalid array_length for given dimension' from 'font-manager: FTBFS on arm64: ../src/font-manager/ArchiveManager.vala:26.97-26.106: error: internal: invalid array_length for given dimension'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-django-pipeline: installs files into aliased locations
Processing control commands: > affects -1 + python3-distutils Bug #1070047 [python3-django-pipeline] python3-django-pipeline: installs files into aliased locations Added indication that 1070047 affects python3-distutils -- 1070047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070047: python3-django-pipeline: installs files into aliased locations
Package: python3-django-pipeline
Version: 3.0.0-1
Severity: serious
Justification: introduces new aliasing
Tags: patch
Control: affects -1 + python3-distutils
User: helm...@debian.org
Usertags: dep17p6
The last upload of python3-django-pipeline moved all of its files from
/usr/lib to /lib. Whils this works somewhat on a /usr-merged
installations, it causes subtle bugs due to dpkg not being prepared with
aliasing. In DEP17, we're resolving this by moving all files out of
aliased locations and python3-django-pipelines has just introduced new.
Hence, I'm filing this at RC severity. I think the move was accidental
and can be fixed by dropping the faulty "mv" command in favour of
setting PYBUILD_NAME to the package name rather than the module name.
I'm attaching a patch for your convenience.
Helmut
diff --minimal -Nru django-pipeline-3.0.0/debian/changelog
django-pipeline-3.0.0/debian/changelog
--- django-pipeline-3.0.0/debian/changelog 2024-04-28 19:35:05.0
+0200
+++ django-pipeline-3.0.0/debian/changelog 2024-04-29 10:17:13.0
+0200
@@ -1,3 +1,10 @@
+django-pipeline (3.0.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Do not install into /lib. (Closes: #-1)
+
+ -- Helmut Grohne Mon, 29 Apr 2024 10:17:13 +0200
+
django-pipeline (3.0.0-1) unstable; urgency=medium
* Team Upload
diff --minimal -Nru django-pipeline-3.0.0/debian/rules
django-pipeline-3.0.0/debian/rules
--- django-pipeline-3.0.0/debian/rules 2024-04-28 19:35:05.0 +0200
+++ django-pipeline-3.0.0/debian/rules 2024-04-29 10:17:13.0 +0200
@@ -4,7 +4,7 @@
include /usr/share/dpkg/pkg-info.mk
export SETUPTOOLS_SCM_PRETEND_VERSION=${DEB_VERSION_UPSTREAM}
-export PYBUILD_NAME=pipeline
+export PYBUILD_NAME=django-pipeline
export PYBUILD_AFTER_BUILD_python3=PYTHONPATH=. sphinx-build -b html -d
docs/.build/.doctrees -N docs docs/.build/html
# Uncomment this to turn on verbose mode.
@@ -25,6 +25,5 @@
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. python{version}
/usr/bin/django-admin test --settings=tests.settings" dh_auto_test
execute_after_dh_auto_install:
- mv debian/python3-pipeline/* debian/python3-django-pipeline/
find -type f -name '*.pyc' -delete
find -type d -name __pycache__ -empty -delete
Bug#1067364: marked as done (libnginx-mod-http-modsecurity: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25)
Your message dated Mon, 29 Apr 2024 09:19:05 + with message-id and subject line Bug#1067364: fixed in libnginx-mod-http-modsecurity 1.0.3-2 has caused the Debian Bug report #1067364, regarding libnginx-mod-http-modsecurity: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_configure] 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.) -- 1067364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnginx-mod-http-modsecurity Version: 1.0.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 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_configure --buildsystem=nginx_mod -- > --add-module=/usr/share/nginx-ndk/src > checking for OS > + Linux 6.1.0-13-cloud-amd64 x86_64 > checking for C compiler ... found > + using GNU C compiler > checking for --with-ld-opt="-Wl,-z,relro -Wl,-z,now -fPIC" ... found > checking for -Wl,-E switch ... found > checking for gcc builtin atomic operations ... found > checking for C99 variadic macros ... found > checking for gcc variadic macros ... found > checking for gcc builtin 64 bit byteswap ... found > checking for unistd.h ... found > checking for inttypes.h ... found > checking for limits.h ... found > checking for sys/filio.h ... not found > checking for sys/param.h ... found > checking for sys/mount.h ... found > checking for sys/statvfs.h ... found > checking for crypt.h ... found > checking for Linux specific features > checking for epoll ... found > checking for EPOLLRDHUP ... found > checking for EPOLLEXCLUSIVE ... found > checking for eventfd() ... found > checking for O_PATH ... found > checking for sendfile() ... found > checking for sendfile64() ... found > checking for sys/prctl.h ... found > checking for prctl(PR_SET_DUMPABLE) ... found > checking for prctl(PR_SET_KEEPCAPS) ... found > checking for capabilities ... found > checking for crypt_r() ... found > checking for sys/vfs.h ... found > checking for UDP_SEGMENT ... found > checking for nobody group ... not found > checking for nogroup group ... found > checking for poll() ... found > checking for /dev/poll ... not found > checking for kqueue ... not found > checking for crypt() ... not found > checking for crypt() in libcrypt ... found > checking for F_READAHEAD ... not found > checking for posix_fadvise() ... found > checking for O_DIRECT ... found > checking for F_NOCACHE ... not found > checking for directio() ... not found > checking for statfs() ... found > checking for statvfs() ... found > checking for dlopen() ... found > checking for sched_yield() ... found > checking for sched_setaffinity() ... found > checking for SO_SETFIB ... not found > checking for SO_REUSEPORT ... found > checking for SO_ACCEPTFILTER ... not found > checking for SO_BINDANY ... not found > checking for IP_TRANSPARENT ... found > checking for IP_BINDANY ... not found > checking for IP_BIND_ADDRESS_NO_PORT ... found > checking for IP_RECVDSTADDR ... not found > checking for IP_SENDSRCADDR ... not found > checking for IP_PKTINFO ... found > checking for IPV6_RECVPKTINFO ... found > checking for TCP_DEFER_ACCEPT ... found > checking for TCP_KEEPIDLE ... found > checking for TCP_FASTOPEN ... found > checking for TCP_INFO ... found > checking for accept4() ... found > checking for int size ... 4 bytes > checking for long size ... 8 bytes > checking for long long size ... 8 bytes > checking for void * size ... 8 bytes > checking for uint32_t ... found > checking for uint64_t ... found > checking for sig_atomic_t ... found > checking for sig_atomic_t size ... 4 bytes > checking for socklen_t ... found > checking for in_addr_t ... found > checking for in_port_t ... found > checking for rlim_t ... found > checking for uintptr_t ... uintptr_t found > checking for system byte ordering ... little endian > checking for size_t size ... 8 bytes > checking for off_t size ... 8 bytes > checking for time_t size ... 8 bytes > checking for AF_INET6 ... found > checking for setproctitle() ... not found > checking for pread() ... found > checking for pwrite() ... found > checking for pwritev() ... found > checking for strerrordesc_np() ... found > checking for localtime_r() ... found > checking for clock_gettime(CLOCK_MONOTONIC) ... found > checking for posix_memalign() ... found > checking for memalign() ... found > checking for mmap(MAP_ANON|MAP_SHARED) ... found >
Processed: reassign 1069889 to gpg-sq, found 1070017 in 1710437545-4, tagging 1069985, tagging 1069984 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1069889 gpg-sq 0.8.0-4
Bug #1069889 [gpg-sq-dbgsym] gpg-sq-dbgsym: missing auto-load script
Warning: Unknown package 'gpg-sq-dbgsym'
Bug reassigned from package 'gpg-sq-dbgsym' to 'gpg-sq'.
No longer marked as found in versions rust-sequoia-chameleon-gnupg/0.8.0-4.
Ignoring request to alter fixed versions of bug #1069889 to the same values
previously set
Bug #1069889 [gpg-sq] gpg-sq-dbgsym: missing auto-load script
Marked as found in versions rust-sequoia-chameleon-gnupg/0.8.0-4.
> found 1070017 1710437545-4
Bug #1070017 [src:google-android-installers] google-android-installers: depends
on pre-64 libraries
Marked as found in versions google-android-installers/1710437545-4.
> tags 1069985 + sid trixie
Bug #1069985 {Done: Andreas Tille } [src:python-cobra]
python-cobra: Manual build-depends on NBS package libsbml5
Added tag(s) sid and trixie.
> tags 1069984 + sid trixie
Bug #1069984 [src:alire] alire: Build-depends on NBS package libgnatcoll21-dev
Added tag(s) sid and trixie.
> tags 1069983 + sid trixie
Bug #1069983 [src:dwarf-fortress] dwarf-fortress: Manual build-depends on NBS
package libgtk2.0-0
Added tag(s) trixie and sid.
> tags 1069982 + sid trixie
Bug #1069982 [src:theli] theli: Manual build-depends on NBS package libcurl4
Added tag(s) sid and trixie.
> tags 1069986 + sid trixie
Bug #1069986 {Done: Federico Ceratto }
[src:dublin-traceroute] dublin-traceroute: Manual build-depends on NBS package
libtins4.0
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069889
1069982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069982
1069983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069983
1069984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069984
1069985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069985
1069986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069986
1070017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bookworm-pu: package dm-writeboost/???
Processing control commands: > block 1069878 with -1 Bug #1069878 [dm-writeboost-dkms] dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: error: too few arguments to function ‘dm_io’ 1069878 was not blocked by any bugs. 1069878 was not blocking any bugs. Added blocking bug(s) of 1069878: 1070040 > affects -1 + src:dm-writeboost Bug #1070040 [release.debian.org] bookworm-pu: package dm-writeboost/??? Added indication that 1070040 affects src:dm-writeboost -- 1069878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069878 1070040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069254: nwipe: FTBFS: configure: error: libconfig library not found
Tags: patch hi, On Thu, Apr 18, 2024 at 10:00:30PM +0200, Sebastian Ramacher wrote: checking for libconfig... no checking for main in -llibconfig... no configure: error: libconfig library not found It seems it shuold use libconfig-dev. Cheers -- Sebastian Ramacher -- Regards, -- Bo YU diff -Nru nwipe-0.36/debian/changelog nwipe-0.36/debian/changelog --- nwipe-0.36/debian/changelog 2024-04-17 01:37:21.0 +0800 +++ nwipe-0.36/debian/changelog 2024-04-29 14:28:41.0 +0800 @@ -1,3 +1,11 @@ +nwipe (0.36-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Use libconfig-dev instead of pkgconf on debian/control. +(Closes: #1069254) + + -- Bo YU Mon, 29 Apr 2024 14:28:41 +0800 + nwipe (0.36-1) unstable; urgency=medium * New upstream release(closes: #1069072, #1034262 ). diff -Nru nwipe-0.36/debian/control nwipe-0.36/debian/control --- nwipe-0.36/debian/control 2024-04-17 01:37:21.0 +0800 +++ nwipe-0.36/debian/control 2024-04-29 14:28:41.0 +0800 @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Martijn van Brummelen -Build-Depends: debhelper-compat (=13), libparted-dev, libncurses-dev, dpkg-dev (>= 1.16.1~), pkgconf +Build-Depends: debhelper-compat (=13), libparted-dev, libncurses-dev, dpkg-dev (>= 1.16.1~), libconfig-dev Standards-Version: 4.7.0 Homepage: https://github.com/martijnvanbrummelen/nwipe Vcs-Browser: https://salsa.debian.org/mvb/nwipe signature.asc Description: PGP signature
Processed: decrease severity
Processing commands for cont...@bugs.debian.org: > severity 1017729 important Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1070019 is forwarded to https://github.com/storaged-project/udisks/issues/1273
Processing commands for cont...@bugs.debian.org: > forwarded 1070019 https://github.com/storaged-project/udisks/issues/1273 Bug #1070019 [src:udisks2] udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev Set Bug forwarded-to-address to 'https://github.com/storaged-project/udisks/issues/1273'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069458: marked as done (dune-uggrid: FTBFS on armhf: tests fail)
Your message dated Mon, 29 Apr 2024 09:53:21 +0200 with message-id and subject line OpenMPI bug resolved has caused the Debian Bug report #1069458, regarding dune-uggrid: FTBFS on armhf: 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.) -- 1069458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dune-uggrid Version: 2.9.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > make[5]: Nothing to be done for 'CMakeFiles/build_tests.dir/build'. > make[5]: Leaving directory '/<>/build' > [100%] Built target build_tests > make[4]: Leaving directory '/<>/build' > /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0 > make[3]: Leaving directory '/<>/build' > make[2]: Leaving directory '/<>/build' > cd build; PATH=/<>/debian/tmp-test:$PATH /usr/bin/dune-ctest >Site: ip-10-84-234-180 >Build name: Linux-c++ > Create new tag: 20240420-0421 - Experimental > Test project /<>/build > Start 1: rm3-tetrahedron-rules-test > 1/3 Test #1: rm3-tetrahedron-rules-test ...***Failed0.02 sec > -- > Sorry! You were supposed to get help about: > pmix_init:startup:internal-failure > But I couldn't open the help file: > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! > -- > [ip-10-84-234-180:3635872] PMIX ERROR: NOT-FOUND in file > ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at > line 237 > [ip-10-84-234-180:3635871] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to > start a daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716 > [ip-10-84-234-180:3635871] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to > start a daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > orte_ess_init failed > --> Returned value Unable to start a daemon on the local node (-127) > instead of ORTE_SUCCESS > -- > -- > It looks like MPI_INIT failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during MPI_INIT; some of which are due to configuration or environment > problems. This failure appears to be an internal failure; here's some > additional information (which may only be relevant to an Open MPI > developer): > > ompi_mpi_init: ompi_rte_init failed > --> Returned "Unable to start a daemon on the local node" (-127) instead of > "Success" (0) > -- > *** An error occurred in MPI_Init > *** on a NULL communicator > *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, > ***and potentially your MPI job) > [ip-10-84-234-180:3635871] Local abort before MPI_INIT completed completed > successfully, but am not able to aggregate error messages, and not able to > guarantee that all other processes were killed! > > Start 2: test-fifo > 2/3 Test #2: test-fifo Passed0.00 sec > Start 3: testbtree > 3/3 Test #3: testbtree Passed0.00 sec > > 67% tests passed, 1 tests failed out of 3 > > Total Test time (real) = 0.03 sec > > The following tests FAILED: > 1 - rm3-tetrahedron-rules-test (Failed) > Errors while running CTest > == > Name: rm3-tetrahedron-rules-test > FullName: ./dune/uggrid/gm/rm3-tetrahedron-rules-test > Status:FAILED > > JUnit report for CTest
Processed: found 1070019 in 2.10.1-5
Processing commands for cont...@bugs.debian.org: > found 1070019 2.10.1-5 Bug #1070019 [src:udisks2] udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev Marked as found in versions udisks2/2.10.1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069945: Acknowledgement (rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io')
A possible solution (which also handles all kernels that got the patch backported) could be adapted from my pull request for dm-writeboost: https://github.com/anbe42/dm-writeboost/commit/6af8e67052c970e85943429011588976f3f9423a Andreas
Bug#1069492: marked as done (dune-common: FTBFS on armhf: tests fail)
Your message dated Mon, 29 Apr 2024 09:49:22 +0200 with message-id and subject line OpenMPI bug resolved has caused the Debian Bug report #1069492, regarding dune-common: FTBFS on armhf: 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.) -- 1069492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dune-common Version: 2.9.0-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > make[5]: Nothing to be done for 'CMakeFiles/build_tests.dir/build'. > make[5]: Leaving directory '/<>/build' > [100%] Built target build_tests > make[4]: Leaving directory '/<>/build' > /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0 > make[3]: Leaving directory '/<>/build' > make[2]: Leaving directory '/<>/build' > cd build; PATH=/<>/debian/tmp-test:$PATH > /<>/bin/dune-ctest >Site: ip-10-84-234-171 >Build name: Linux-c++ > Create new tag: 20240420-0332 - Experimental > Test project /<>/build > Start 1: communicationtest > 1/115 Test #1: communicationtest ..***Failed0.02 > sec > -- > Sorry! You were supposed to get help about: > pmix_init:startup:internal-failure > But I couldn't open the help file: > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! > -- > [ip-10-84-234-171:1976535] PMIX ERROR: NOT-FOUND in file > ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at > line 237 > [ip-10-84-234-171:1976534] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to > start a daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716 > [ip-10-84-234-171:1976534] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to > start a daemon on the local node in file > ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172 > -- > It looks like orte_init failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during orte_init; some of which are due to configuration or > environment problems. This failure appears to be an internal failure; > here's some additional information (which may only be relevant to an > Open MPI developer): > > orte_ess_init failed > --> Returned value Unable to start a daemon on the local node (-127) > instead of ORTE_SUCCESS > -- > -- > It looks like MPI_INIT failed for some reason; your parallel process is > likely to abort. There are many reasons that a parallel process can > fail during MPI_INIT; some of which are due to configuration or environment > problems. This failure appears to be an internal failure; here's some > additional information (which may only be relevant to an Open MPI > developer): > > ompi_mpi_init: ompi_rte_init failed > --> Returned "Unable to start a daemon on the local node" (-127) instead of > "Success" (0) > -- > *** An error occurred in MPI_Init > *** on a NULL communicator > *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, > ***and potentially your MPI job) > [ip-10-84-234-171:1976534] Local abort before MPI_INIT completed completed > successfully, but am not able to aggregate error messages, and not able to > guarantee that all other processes were killed! > > Start 2: communicationtest-mpi-2 > 2/115 Test #2: communicationtest-mpi-2 ***Failed0.02 > sec > -- > Sorry! You were supposed to get help about: > pmix_init:startup:internal-failure > But I couldn't open the help file: > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry! > -- > [ip-10-84-234-171:1976536] PMIX ERROR: NOT-FOUND in file >
Bug#1065993: marked as done (xwiimote: FTBFS on arm{el,hf}:)
Your message dated Mon, 29 Apr 2024 07:36:00 +
with message-id
and subject line Bug#1065993: fixed in xwiimote 2-4.2
has caused the Debian Bug report #1065993,
regarding xwiimote: FTBFS on arm{el,hf}:
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.)
--
1065993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xwiimote
Version: 2-4.1
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=xwiimote=armhf=2-4.1=1709538546=0
libtool: compile: gcc -DHAVE_CONFIG_H -I. -include ./config.h -I ./lib
"-DXWII__EXPORT=__attribute__((visibility(\"default\")))" -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
-pipe -fno-common -ffast-math -fdiagnostics-show-option -fno-strict-aliasing
-fvisibility=hidden -ffunction-sections -fdata-sections -fstack-protector -O2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -c lib/core.c -fPIC
-DPIC -o lib/.libs/libxwiimote_la-core.o
/bin/bash ./libtool --tag=CC --mode=link gcc -Wall -pipe -fno-common
-ffast-math -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden
-ffunction-sections -fdata-sections -fstack-protector -O2 -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -Wall -Wl,--as-needed -Wl,--gc-sections -Wl,-z,relro
-Wl,-z,now -Wl,-z,relro -Wl,-z,now -Wl,--no-undefined -Wl,--as-needed -o
xwiidump tools/xwiidump-xwiidump.o
lib/core.c: In function ‘read_core’:
lib/core.c:815:33: error: ‘struct input_event’ has no member named ‘time’
815 | memcpy(>time, , sizeof(struct timeval));
| ^
lib/core.c: In function ‘read_accel’:
lib/core.c:845:41: error: ‘struct input_event’ has no member named ‘time’
845 | memcpy(>time, , sizeof(struct timeval));
| ^
lib/core.c: In function ‘read_ir’:
lib/core.c:887:41: error: ‘struct input_event’ has no member named ‘time’
887 | memcpy(>time, , sizeof(struct timeval));
| ^
lib/core.c: In function ‘read_mp’:
lib/core.c:939:41: error: ‘struct input_event’ has no member named ‘time’
939 | memcpy(>time, , sizeof(struct timeval));
| ^
lib/core.c: In function ‘read_bboard’:
lib/core.c:991:41: error: ‘struct input_event’ has no member named ‘time’
991 | memcpy(>time, , sizeof(struct timeval));
| ^
lib/core.c: In function ‘read_pro’:
lib/core.c:1120:41: error: ‘struct input_event’ has no member named ‘time’
1120 | memcpy(>time, , sizeof(struct timeval));
| ^
lib/core.c:1136:41: error: ‘struct input_event’ has no member named ‘time’
1136 | memcpy(>time, , sizeof(struct timeval));
| ^
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: xwiimote
Source-Version: 2-4.2
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
xwiimote, 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 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated xwiimote 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: Sat, 27 Apr 2024 09:09:48 +0200
Source: xwiimote
Architecture: source
Version: 2-4.2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu
Changed-By: Andreas Beckmann
Closes: 1045999 1065993
Changes:
xwiimote (2-4.2) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Non-maintainer upload.
* Fixup Breaks+Replaces unrelated to
Bug#1069948: marked as done (python3-pydevd: cannot be installed on Debian testing, unsatisfied dependency on gdb)
Your message dated Mon, 29 Apr 2024 06:17:54 + with message-id <845243f1d12f156ad70f814446e59889dba22ba9.ca...@hotmail.com> and subject line Re: python3-pydevd: cannot be installed on Debian testing, unsatisfied dependency on gdb has caused the Debian Bug report #1069948, regarding python3-pydevd: cannot be installed on Debian testing, unsatisfied dependency on gdb 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.) -- 1069948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pydevd Version: 2.10.0+ds-10 Severity: grave Justification: renders package unusable Dear Maintainer, On an up-to-date Debian testing, python3-pydevd cannot be installed because of an unsatisfied dependency on gdb. Best, Amr -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) 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 python3-pydevd depends on: pn gdb ii libc6 2.37-18 ii libgcc-s1 14-20240330-1 ii libstdc++614-20240330-1 ii python3 3.11.6-1 pn python3-bytecode pn python3-coverage python3-pydevd recommends no packages. Versions of packages python3-pydevd suggests: pn pydevd --- End Message --- --- Begin Message --- On Sat, 27 Apr 2024 14:22:59 +0200 Amr Ibrahim wrote: > On an up-to-date Debian testing, python3-pydevd cannot be installed because of > an unsatisfied dependency on gdb. Sorry, this is a false bug, python3-pydevd can be installed now. Maybe it was a transitional thing. --- End Message ---
