Bug#1066225: Bug#1069722: RFS: libtranscript/0.3.3-1.1 [NMU] [RC] -- Character set conversion library
Hi! Thanks for NMUing this! On Thu, Apr 25, 2024 at 4:29 AM Salvo Tomaselli wrote: > > Hello, > > tilde is going to be autoremoved very soon because of libt3key. > > I'd say that if the maintainer hasn't taken any action about this for over a > months, it's possible to contact the MIA team right away. Yeah, this is my consideration also. > > If you don't want tilde to be dropped, you have to fix also libt3key and get > it > sponsored, because just this one won't help basically. I have uploaded it to mentor[0]. Thanks again. BR, Bo [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069801 >
Bug#1053334: galera-4: FTBFS because of expired certificates
Bullseye oldstable update request filed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069802 You can +1 it if you want to show support.
Processed: bug 1060938 is forwarded to https://github.com/ashmanix/obs-plugin-countdown/issues/61
Processing commands for cont...@bugs.debian.org: > forwarded 1060938 https://github.com/ashmanix/obs-plugin-countdown/issues/61 Bug #1060938 [src:obs-ashmanix-countdown] obs-ashmanix-countdown: FTBFS: plugin-main.cpp:41:30: error: ‘void* obs_frontend_add_dock(void*)’ is deprecated [-Werror=deprecated-declarations] Set Bug forwarded-to-address to 'https://github.com/ashmanix/obs-plugin-countdown/issues/61'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009804: marked as done (pytest-salt-factories: autopkgtest failure with python3.10)
Your message dated Thu, 25 Apr 2024 04:36:27 + with message-id and subject line Bug#1069723: Removed package(s) from unstable has caused the Debian Bug report #1009804, regarding pytest-salt-factories: autopkgtest failure with python3.10 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.) -- 1009804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-salt-factories Version: 0.907.0-4 Severity: serious Tags: sid bookworm pytest-salt-factories' autopkgtests fail with python3.10: === 229 passed, 2 skipped, 60 warnings in 133.67s (0:02:13) autopkgtest [03:46:37]: test pytest: ---] autopkgtest [03:46:37]: test pytest: - - - - - - - - - - results - - - - - - - - - - pytest FAIL stderr: :914: ImportWarning: TornadoImporter.find_spec() not found; falling back to find_module() autopkgtest [03:46:38]: test pytest: - - - - - - - - - - stderr - - - - - - - - - - :914: ImportWarning: TornadoImporter.find_spec() not found; falling back to find_module() :914: ImportWarning: SixRedirectImporter.find_spec() not found; falling back to find_module() autopkgtest [03:46:38]: summary pytest FAIL stderr: :914: ImportWarning: TornadoImporter.find_spec() not found; falling back to find_module() See https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-salt-factories/20956632/log.gz Please add the restriction to not fail on stderr output or fix the warnings. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 0.907.0-4+rm Dear submitter, as the package pytest-salt-factories has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069723 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1066618: RFS: libt3key/0.2.10-1.1 [NMU] [RC] -- Utilities for working with libt3key terminal descriptions
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "libt3key":
* Package name : libt3key
Version : 0.2.10-1.1
Upstream contact : Gertjan Halkes
* URL : https://os.ghalkes.nl/t3/libt3key.html
* License : GPL-3
* Vcs : [fill in URL of packaging vcs]
Section : libs
The source builds the following binary packages:
libt3key-dev - Development files for libt3key
libt3key1 - Terminal key sequence database library
libt3key-bin - Utilities for working with libt3key terminal descriptions
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/libt3key/
Alternatively, you can download the package with 'dget' using this command:
dget -x
https://mentors.debian.net/debian/pool/main/libt/libt3key/libt3key_0.2.10-1.1.dsc
Changes since the last upload:
libt3key (0.2.10-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue.
(Closes: #1066618)
--
Regards,
--
Bo YU
diff -Nru libt3key-0.2.10/debian/changelog libt3key-0.2.10/debian/changelog
--- libt3key-0.2.10/debian/changelog2019-11-30 21:16:41.0 +0800
+++ libt3key-0.2.10/debian/changelog2024-04-25 10:54:51.0 +0800
@@ -1,3 +1,11 @@
+libt3key (0.2.10-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue.
+(Closes: #1066618)
+
+ -- Bo YU Thu, 25 Apr 2024 10:54:51 +0800
+
libt3key (0.2.10-1) unstable; urgency=medium
* New upstream release.
diff -Nru libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch
libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch
--- libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch
1970-01-01 07:30:00.0 +0730
+++ libt3key-0.2.10/debian/patches/00-fix-impfuncdef-issue.patch
2024-04-25 10:53:18.0 +0800
@@ -0,0 +1,17 @@
+Description: fix impfuncdef issue
+Author: Bo YU
+Bug: https://bugs.debian.org/1066618
+Forwarded: Forward this patch to the author of upstream
+Last-Update: 2024-04-25
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/config.pkg
b/config.pkg
+@@ -144,6 +144,7 @@
+ #include
+ #include
+ #include
++#include
+
+ int main(int argc, char *argv[]) {
+ int args[9], error, fd;
diff -Nru libt3key-0.2.10/debian/patches/series
libt3key-0.2.10/debian/patches/series
--- libt3key-0.2.10/debian/patches/series 1970-01-01 07:30:00.0
+0730
+++ libt3key-0.2.10/debian/patches/series 2024-04-25 10:02:49.0
+0800
@@ -0,0 +1 @@
+00-fix-impfuncdef-issue.patch
signature.asc
Description: PGP signature
Bug#1063743: marked as done (gloo-cuda: required rebuilds for libhiredis transition)
Your message dated Thu, 25 Apr 2024 03:19:20 + with message-id and subject line Bug#1063743: fixed in gloo-cuda 0.0~git20230519.597accf-3 has caused the Debian Bug report #1063743, regarding gloo-cuda: required rebuilds for libhiredis transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1063743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gloo-cuda Version: 0.0~git20230117.1090929-2 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sramac...@debian.org gloo-cuda is involved in the libhiredis transition. But since the package cannot be built on the buildds, uploads of builds against the new libhiredis version are required. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: gloo-cuda Source-Version: 0.0~git20230519.597accf-3 Done: Mo Zhou We believe that the bug you reported is fixed in the latest version of gloo-cuda, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated gloo-cuda 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: Wed, 24 Apr 2024 22:18:04 -0400 Source: gloo-cuda Binary: libgloo-cuda-0 libgloo-cuda-0-dbgsym libgloo-cuda-dev Architecture: source amd64 Version: 0.0~git20230519.597accf-3 Distribution: unstable Urgency: medium Maintainer: Debian Deep Learning Team Changed-By: Mo Zhou Description: libgloo-cuda-0 - Collective communications library (shared object) libgloo-cuda-dev - Collective communications library (development files) Closes: 1063743 Changes: gloo-cuda (0.0~git20230519.597accf-3) unstable; urgency=medium . * Rebuild src:gloo with CUDA (non-free) enabled. (Closes: #1063743) Due to non-free B-D, section is changed from main to contrib. * Automatically generated by src:gloo :: debian/cudabuild.sh Please always merge the changes to the cuda variant back to src:gloo, thanks. Checksums-Sha1: ee39f9952243ed6c6a81a5f52e333d2edc4c5f9e 2309 gloo-cuda_0.0~git20230519.597accf-3.dsc 51ae99710ba07479b488552f55bf8817ec02987e 185100 gloo-cuda_0.0~git20230519.597accf.orig.tar.xz 182bb941688ac7660ea8b7ef524dec3acb8d8ee1 5288 gloo-cuda_0.0~git20230519.597accf-3.debian.tar.xz 8db8eed9b16b8f09327b1b4fa741a3ae1248bfc7 12525 gloo-cuda_0.0~git20230519.597accf-3_amd64.buildinfo 9210f5538eb7d21d14630ce24c78bdc5340c7c2d 11122140 libgloo-cuda-0-dbgsym_0.0~git20230519.597accf-3_amd64.deb d87762bda0087bd0c5369aa5c4dfece24d3b3501 463180 libgloo-cuda-0_0.0~git20230519.597accf-3_amd64.deb ee0077cfd60d17f3894dc5f43032e17bb262d6fe 60092 libgloo-cuda-dev_0.0~git20230519.597accf-3_amd64.deb Checksums-Sha256: 136c8cdaa51a777b03282074e375007d13610398bb3b56e066d46cb9f7f933d0 2309 gloo-cuda_0.0~git20230519.597accf-3.dsc 68f7bb91c706808d653cb4c9f81537f7c8a732544f76f992bf4e8d7be29c803a 185100 gloo-cuda_0.0~git20230519.597accf.orig.tar.xz c66c6060d5fd77752693116d624a2707e92a054d7b67a2c687666e862923 5288 gloo-cuda_0.0~git20230519.597accf-3.debian.tar.xz 2793f7bf733161afc1b40a2f91e2e6a38c5fee43ef510aa7cede26355b5c18df 12525 gloo-cuda_0.0~git20230519.597accf-3_amd64.buildinfo 9deadf8110e207f35efef304915e8083284188b2d56cdaa64e93bbe19c30da22 11122140 libgloo-cuda-0-dbgsym_0.0~git20230519.597accf-3_amd64.deb 683424ffcadd41ecfa576c4583591b899c54cd609ade19765141f1fae6f610d2 463180 libgloo-cuda-0_0.0~git20230519.597accf-3_amd64.deb 2fa1371be2c43f4666ae2d99ac6d9eb50f62d1d8952b74f6d5a1015cb93710d0 60092 libgloo-cuda-dev_0.0~git20230519.597accf-3_amd64.deb Files: 50cfacdb94513d880c00e7de3268cec5 2309 contrib/science optional gloo-cuda_0.0~git20230519.597accf-3.dsc 2d40f88b9eb80e06ee9d880c519e1427 185100 contrib/science optional gloo-cuda_0.0~git20230519.597accf.orig.tar.xz efa2beb68e85dd9cd4006a1838930425 5288 contrib/science optional gloo-cuda_0.0~git20230519.597accf-3.debian.tar.xz 86d3b5abe3e2ae504882c17c77b8793c 12525 contrib/science optional gloo-cuda_0.0~git20230519.597accf-3_amd64.buildinfo 2d0d2e389e970610cdc07861e0f2df06
Processed: notfound 1069800 in 24.1.1-2
Processing commands for cont...@bugs.debian.org: > notfound 1069800 24.1.1-2 Bug #1069800 [src:cloud-init] FTBFS: test failures in buildd environment Ignoring request to alter found versions of bug #1069800 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1069800 is forwarded to https://github.com/canonical/cloud-init/issues/5211
Processing commands for cont...@bugs.debian.org: > forwarded 1069800 https://github.com/canonical/cloud-init/issues/5211 Bug #1069800 [src:cloud-init] FTBFS: test failures in buildd environment Set Bug forwarded-to-address to 'https://github.com/canonical/cloud-init/issues/5211'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069800: FTBFS: test failures in buildd environment
Source: cloud-init Version: 21.1.4-1 Severity: serious Tags: ftbfs upstream Justification: fails to build from source Cloud-init's test fails in a non-networked build environment, as visible in recent buildd logs, e.g. https://buildd.debian.org/status/fetch.php?pkg=cloud-init=all=24.1.4-1=1714007718=0 This appears to be an upstream issue, as it occurs in pristine upstream source tree. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-20-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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
Bug#1069799: rust-multihash-derive-impl - (build-)depends unsatisfiable.
Package: rust-multihash-derive-impl Version: 0.7.0-1 Severity: serious rust-synstructure was recently updated to version 0.13.1 I tried bumping the dependency but that caused failures due to mismatched versions of syn. Bumping the dependency on syn as well resulted in. error[E0609]: no field `tokens` on type `` --> src/multihash.rs:100:74 | 100 | let attr: Result, _> = syn::parse2(attr.tokens.clone()); | ^^ unknown field | = note: available fields are: `pound_token`, `style`, `bracket_token`, `meta` error[E0609]: no field `tokens` on type `` --> src/multihash.rs:141:82 | 141 | let derive_attrs: Result, _> = syn::parse2(attr.tokens.clone()); | ^^ unknown field | = note: available fields are: `pound_token`, `style`, `bracket_token`, `meta` error[E0061]: this method takes 2 arguments but 1 argument was supplied --> src/utils.rs:25:29 | 25 | let attrs = content.parse_terminated(A::parse)?; | -- an argument is missing | I'm also going to report this upstream.
Bug#1069798: rust-failure-derive - (build-)depends unsatisfiable.
Package: rust-failure-derive
Version: 0.1
Tags: trixie, sid
Severity: serious
rust-synstructure was recently updated to version 0.13.1
I tried bumping the dependency but that caused failures due to
mismatched versions of syn. Bumping the dependency on syn as well
resulted in.
error[E0433]: failed to resolve: could not find `NestedMeta` in `syn`
--> src/lib.rs:129:18
|
129 | syn::NestedMeta::Meta(syn::Meta::NameValue(ref nv)) if
nv.path.is_ident("display") => {
| ^^ could not find `NestedMeta` in `syn`
error[E0433]: failed to resolve: could not find `NestedMeta` in `syn`
--> src/lib.rs:140:18
|
140 | syn::NestedMeta::Lit(syn::Lit::Int(ref i)) => {
| ^^ could not find `NestedMeta` in `syn`
error[E0433]: failed to resolve: could not find `NestedMeta` in `syn`
--> src/lib.rs:144:18
|
144 | syn::NestedMeta::Meta(syn::Meta::Path(ref path)) => {
| ^^ could not find `NestedMeta` in `syn`
error[E0433]: failed to resolve: could not find `NestedMeta` in `syn`
--> src/lib.rs:252:39
|
252 | if let
&::NestedMeta::Meta(syn::Meta::Path(ref path)) = pair {
| ^^ could not find
`NestedMeta` in `syn`
error[E0609]: no field `nested` on type `MetaList`
--> src/lib.rs:121:16
|
121 | if msg.nested.is_empty() {
| ^^ unknown field
|
= note: available fields are: `path`, `delimiter`, `tokens`
error[E0609]: no field `nested` on type `MetaList`
--> src/lib.rs:128:39
|
128 | let format_string = match msg.nested[0] {
| ^^ unknown field
|
= note: available fields are: `path`, `delimiter`, `tokens`
error[E0609]: no field `lit` on type ``
--> src/lib.rs:130:20
|
130 | nv.lit.clone()
| ^^^ unknown field
|
= note: available fields are: `path`, `eq_token`, `value`
error[E0609]: no field `nested` on type `MetaList`
--> src/lib.rs:139:24
|
139 | let args = msg.nested.iter().skip(1).map(|arg| match *arg {
| ^^ unknown field
|
= note: available fields are: `path`, `delimiter`, `tokens`
error[E0599]: no method named `parse_meta` found for reference `` in
the current scope
--> src/lib.rs:202:32
|
202 | if let Ok(meta) = attr.parse_meta() {
| ^^ help: there is a method with a
similar name: `parse_nested_meta`
error[E0599]: no method named `parse_meta` found for reference `` in
the current scope
--> src/lib.rs:242:32
|
242 | if let Ok(meta) = attr.parse_meta() {
| ^^ help: there is a method with a
similar name: `parse_nested_meta`
error[E0609]: no field `nested` on type ``
--> src/lib.rs:251:50
|
251 | if let Some(ref pair) = list.nested.first() {
| ^^ unknown field
|
= note: available fields are: `path`, `delimiter`, `tokens`
rust-failure has long been deprecated upstream, and rdeps have been gradually
migrating away.
Looking at the remaining list of rdeps I see.
rust-assert-cli - no rdeps
rust-bendy - no rdeps
rust-coreutils - already broken and scheduled for autoremoval from testing soon
rust-distro-info - upstream has a patch switching to anyhow but hasn't yet
included it in a release, only rdep is lintian-brush which is not in testing
and already has a FTBFS bug.
rust-exitfailure - no rdeps
rust-include-dir-impl - no rdeps
rust-mdl - no rdeps
rust-rspotify - already broken and not in testing
rust-rustc-cfg - I have uploaded a new version of this that no longer depends
on failure, and updated the rdeps to use it.
Bug#1069796: rust-abscissa-derive - (build-)depends unsatisfiable.
Package: rust-abscissa-derive
Version: 0.7.0-1
Severity: serious
rust-synstructure was recently updated to version 0.13.1
I tried bumping the dependency but that caused failures due to
mismatched versions of syn. Bumping the dependency on syn as well
resulted in.
error[E0432]: unresolved import `syn::NestedMeta`
--> src/component.rs:5:60
|
5 | use syn::{DeriveInput, Lit, Meta, MetaList, MetaNameValue, NestedMeta};
|^^ no
`NestedMeta` in the root
error[E0615]: attempted to take value of method `path` on type ``
--> src/component.rs:56:22
|
56 | if !attr.path.is_ident("component") {
| method, not a field
|
help: use parentheses to call the method
|
56 | if !attr.path().is_ident("component") {
| ++
error[E0599]: no method named `parse_meta` found for reference `` in
the current scope
--> src/component.rs:60:24
|
60 | match attr.parse_meta().expect("error parsing meta") {
|^^ help: there is a method with a similar
name: `parse_nested_meta`
error[E0026]: struct `MetaList` does not have a field named `nested`
--> src/component.rs:61:39
|
61 | Meta::List(MetaList { nested, .. }) => {
| ^^ struct `MetaList` does not
have this field
error[E0026]: struct `MetaNameValue` does not have a field named `lit`
--> src/component.rs:135:17
|
135 | lit: Lit::Str(lit_str),
| ^^^ struct `MetaNameValue` does not have this field
Some errors have detailed explanations: E0026, E0432, E0599, E0615.
Since rust-abscissa-derive has no reverse dependencies I did not investigate
further.
Bug#1066753: marked as pending in python-django-extensions
Control: tag -1 pending Hello, Bug #1066753 in python-django-extensions 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/python-team/packages/python-django-extensions/-/commit/921fe3d3ee85af32d7183155bd90d78a93a232a9 d/p/0004: Disable dumpscript tests as a temporary solution Closes: #1066753 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066753
Processed: Bug#1066753 marked as pending in python-django-extensions
Processing control commands:
> tag -1 pending
Bug #1066753 [src:python-django-extensions] python-django-extensions: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12
3.11" returned exit code 13
Added tag(s) pending.
--
1066753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: dqlite: FTBFS on arm64: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2
Processing control commands: > forwarded -1 https://github.com/canonical/dqlite/issues/643 Bug #1069400 [src:dqlite] dqlite: FTBFS on arm64: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/canonical/dqlite/issues/643'. -- 1069400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069400: dqlite: FTBFS on arm64: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2
Control: forwarded -1 https://github.com/canonical/dqlite/issues/643 Looks like a flaky test, and unrelated to the time_t transition. Mathias signature.asc Description: This is a digitally signed message part
Bug#1068185: llvm-toolchain-16: FTBFS on armel: cxa_guard.cpp:(.text.unlikely.__cxa_guard_acquire+0xc): undefined reference to `__atomic_load_1'
Looking at the changelog, I see Build with --as-needed. I suspect this is responsible for the build failure on armel
Bug#1068730: marked as done (Fails to build from source since removal of liblz4-tool)
Your message dated Wed, 24 Apr 2024 22:54:12 + with message-id and subject line Bug#1068730: fixed in systemd 255.5-1 has caused the Debian Bug report #1068730, regarding Fails to build from source since removal of liblz4-tool 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.) -- 1068730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: systemd Severity: serious Tags: patch X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de Greetings, systemd build-depends on liblz4-tool but that package is no longer build from src:lz4 (since 1.9.4-2, uploaded about a week ago). Just replacing the dependency with lz4 seems to fix this problem (build passes, didn't check further). Cheers, Christoph -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.23 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: systemd Source-Version: 255.5-1 Done: Luca Boccassi We believe that the bug you reported is fixed in the latest version of systemd, 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. Luca Boccassi (supplier of updated systemd 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: Wed, 24 Apr 2024 16:34:40 +0100 Source: systemd Architecture: source Version: 255.5-1 Distribution: sid Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Luca Boccassi Closes: 1063391 1068730 Changes: systemd (255.5-1) sid; urgency=medium . [ Michael Biebl ] * autopkgtest: depend on pkgconf rather than pkg-config * Stop setting default-hierarchy to unified explicitly. It is already the default and the meson option has been deprecated and is expected to be removed in a future release. See https://github.com/systemd/syst emd/commit/31323f21bb0ae7c712f43500c42997c91a6d20bf * Replace Skip-flaky-test_resolved_domain_restricted_dns-in- network.patch with a proper upstream fix. * Remove myself from Uploaders . [ Luca Boccassi ] * autopkgtest: add dhcpcd5 as alternative dependency to dhcpcd-base dhcpcd-base is not available in Jammy * d/e/checkout-upstream: stop overriding sshconfdir. It actually works after some upstream test fixes, and it is necessary for TEST-46-HOMED to work * autopkgtest: install systemd-resolved for all suites. Necessary to avoid breaking the network on Ubuntu, in the upstream jammy-based CI jobs. Can be dropped once jammy is no longer tested. * autopkgtest: add breaks-testbed to more tests. Given resolved is installed, the testbed needs to be reset to switch back to the default network stack, otherwise installing packages in the salsa-ci autopkgtest job fails * autopkgtest: restrict systemd-boot-efi to architectures where it's built * Enable libpwquality support. Suggest it from systemd (used by firstboot and cryptenroll) and depend on it from homed (user creation is a core part of it). It's a dlopen() dependency. (Closes: #1063391) * d/e/checkout-upstream: do not initialize submodules. They are used by mkosi, not needed for CI builds * Autopkgtest: add dependency on libkmod-dev to upstream suite. * Switch build-depend form liblz4-tool to lz4. The former is deprecated and now dropped, the latter is available since buster. (Closes: #1068730) * initramfs hooks: pull in libkmod manually udev now opens it with dlopen, so the ldd-based resolver will not see it, pull it in the initramfs manually * New upstream version 255.5 * Drop resolve-skip-IP_UNICAST_IF-for-local-sockets.patch, merged upstream * Refresh patches for v255.5 * Bump Standards-Version to 4.7.0, no changes . [ Daan De Meyer ] * Build in
Bug#1037902: Bug#999922: xneur: depends on obsolete pcre3 library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! I intend to nmu xneur shortly, fixing the two RC bugs (#22, #1037902, which has been open 7 months and 2,5 years) using the fixes that have been posted to the bugs, to help the progress of the time_t transition. See the attached debdiff for the full list of changes. If you want me to hold, please let me know. Thanks to Bastian Germann, Jonathan Bergh and Yavor Doganov for the fixes! best /Andreas Rönnquist gus...@debian.org -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETq74h7WfgJdjc9ALCHsqoZ75O8IFAmYpjLwACgkQCHsqoZ75 O8IhWw/9GKdSRYKdXwUT/YA0GBLET0zrBpb46Y8VBjlSUiMooQO72yZEj6DcLfjc fpr8ZiMBggsS93MGK825zUQhFCQpOFYBbMr5eRUKh8vD3slzP1FCgGZNFcnTZzJf zTmdoFnAWG9qMY+VZ+6Wqe28pYzPrIKDCP9qKX3c0wiZpGhdGsrufqIKmymInltN Pd1BtBBEBvXbpaJqpKrN3puoBo31sg2pWktIhxSxIAVokMkXFBAZuBg5l9bsVRKV 8EZ/1Hdml2HaCKaKTOCeRiH06jHBSE+17W+DuyHfuIvx9FM0ToZuuDWnUNrItImq YhdUFEycES8NUrJtW0OGGCwMFSU1xjKFGsWiox/DUiua350pIEjoJB8Ic5vZ4F9e U+W+sCFWOLQpNNzjqtS2RpSVezD1phdrJIYVMKCvmwRErTY2dy0IU/3HyS1E9pUr DBGCagvUrmOnxerLrkwljHnWgX6FmbkMBcJcO2xQjOPZlDOToBB08Yvit9FOEcmP qwzj4sgqe3DHU2rFftmDddthjBvRnXOExc8PdCFmgb3ZmX/hyG6ckKpxKmmoi8WY ePKJBrryIqN9tW7vQaxiSa7VcxcR87QTe2HpL/nX/Ptljolx2QyAlv4fYyFBFlbo yfrxy5kuRzrGA78glph6gB7xauhjP/fUMlrk1aFO+h/6hdlk1NY= =27s+ -END PGP SIGNATURE- xneur_nmu.debdiff Description: Binary data
Bug#1069655: marked as done (libkf6userfeedback-data: missing Breaks+Replaces: libkuserfeedbackcoreqt6-1 (<< 6))
Your message dated Wed, 24 Apr 2024 22:19:40 + with message-id and subject line Bug#1069655: fixed in kf6-kuserfeedback 6.0.0-2 has caused the Debian Bug report #1069655, regarding libkf6userfeedback-data: missing Breaks+Replaces: libkuserfeedbackcoreqt6-1 (<< 6) 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.) -- 1069655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libkf6userfeedback-data Version: 6.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid' installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libkf6userfeedback-data_6.0.0-1_all.deb ... Unpacking libkf6userfeedback-data (6.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libkf6userfeedback-data_6.0.0-1_all.deb (--unpack): trying to overwrite '/usr/share/qlogging-categories6/org_kde_UserFeedback.categories', which is also in package libkuserfeedbackcoreqt6-1:amd64 1.3.0-3+b2 Errors were encountered while processing: /var/cache/apt/archives/libkf6userfeedback-data_6.0.0-1_all.deb cheers, Andreas libkuserfeedbackcoreqt6-1=1.3.0-3+b2_libkf6userfeedback-data=6.0.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: kf6-kuserfeedback Source-Version: 6.0.0-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of kf6-kuserfeedback, 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. Aurélien COUDERC (supplier of updated kf6-kuserfeedback 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: Wed, 24 Apr 2024 23:42:05 +0200 Source: kf6-kuserfeedback Architecture: source Version: 6.0.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 1069655 Changes: kf6-kuserfeedback (6.0.0-2) experimental; urgency=medium . [ Aurélien COUDERC ] * Add Breaks+Replaces for libkf6userfeedback-data against libkuserfeedbackcoreqt6-1 which was also shipping the qt6 logging categories file. (Closes: #1069655) Checksums-Sha1: 5f9f24738e5718313dbd1655f201e8c6e0b49220 3309 kf6-kuserfeedback_6.0.0-2.dsc f403b048ad45fe2c1b1b4e812930129f58d200d1 17988 kf6-kuserfeedback_6.0.0-2.debian.tar.xz 2225bbe3a38aa98d0c8a959ea87ce83934eae8cc 16547 kf6-kuserfeedback_6.0.0-2_amd64.buildinfo Checksums-Sha256: d6bcca7a38accc95e78d38f05a98c4f7efed3cc0abee85279a28bb21ff4ad13e 3309 kf6-kuserfeedback_6.0.0-2.dsc 19d37e3feecef4dc6cf94d2133a9212083188aa39c466c96d299dfbca7b2cbfe 17988 kf6-kuserfeedback_6.0.0-2.debian.tar.xz 970211387ee59f5272905b109f9611ee4cfc2eb55e8ff78fd27607456bdb8a7d 16547 kf6-kuserfeedback_6.0.0-2_amd64.buildinfo Files: e79f65bdaa71665f0e7ae3ad02f44c6d 3309 libs optional kf6-kuserfeedback_6.0.0-2.dsc fdfa36d8d2dc5a28ab3667c3edb1deb7 17988 libs optional kf6-kuserfeedback_6.0.0-2.debian.tar.xz 3af181411a309cecd4a1c17080a4bced 16547 libs optional kf6-kuserfeedback_6.0.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmYpfTsTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJJdBD/46MDX2M9goIj5Y7lN787MYE4Pq7Yw5 /tZ4VQU+U4EtFV6dWGBSwuf2JXL2hj6owp9j5z7kJYnIdG5GaWOegsR6zomYcFcd kxw69qCo2jl4MojoaOJnGyKvufJogTSkFZQcOoqVFrGkWWb8Qd01k/hj/1CpFUNu sTAotJy5OYWfTgumCRetTkpa5VYSFm1hQ1suJ3Tdt2AxyeH4u1+185tBk/4rGT9G WKE+BNMKPL/SXSMf69KQhS79eW21J1Wc/Dmdmrpw7PNY0uV7Vql18iyzg6e4hGD8
Bug#1000041: marked as done (ganglia: depends on obsolete pcre3 library)
Your message dated Wed, 24 Apr 2024 22:19:21 + with message-id and subject line Bug#141: fixed in ganglia 3.7.2-7 has caused the Debian Bug report #141, regarding ganglia: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ganglia Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: ganglia Source-Version: 3.7.2-7 Done: Marcos Fouces We believe that the bug you reported is fixed in the latest version of ganglia, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcos Fouces (supplier of updated ganglia 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: Wed, 24 Apr 2024 23:40:14 +0200 Source: ganglia Architecture: source Version: 3.7.2-7 Distribution: unstable Urgency: medium Maintainer: Marcos Fouces Changed-By: Marcos Fouces Closes: 141 1011995 Changes: ganglia (3.7.2-7) unstable; urgency=medium . * Remove Stuart from uploaders as he changed to the Emeritus status. (Closes: #1011995). * Replace libpcre3-dev with libpcre2-dev. (Thanks to Yavor Doganov). (Closes: #141) * Bump to Standards-Version 4.6.2 (no changes required). * Update copyright file. * Remove lsb-base from Depends as it is no longer needed. * Change obsolete pkg name (pkg-config => pkgconf). * Fix mismatched Lintian override. Checksums-Sha1: fba241e8d6798b8b869541937bdacbda6698abd4 2237 ganglia_3.7.2-7.dsc 8619e051783cca34607e40357ab6b60e6785192a 15256 ganglia_3.7.2-7.debian.tar.xz 63e03db6a15f02ffc16305f33bde57eeebcbb519 9614 ganglia_3.7.2-7_source.buildinfo Checksums-Sha256: 1ef01cb0d66f0be9e8c352850724f0764bebbe6c6e8d1c73fd6a09bcf87332c7 2237 ganglia_3.7.2-7.dsc 83ce11b2e2b1343c628da6505fbec0f8fb5279c213fca2f7e047d2763c833a68 15256 ganglia_3.7.2-7.debian.tar.xz 5f2485e28a47be9dbb6f0e0e175ecfc106588d018324f805f4c1f5152f5b0be9 9614 ganglia_3.7.2-7_source.buildinfo Files: 2032f39bda3c1c1131d5b3f9c40746f0 2237 net optional ganglia_3.7.2-7.dsc aaf056ae1f26e6c024930f5c2ce63661 15256 net optional ganglia_3.7.2-7.debian.tar.xz 37964de3c34e7b31f6ffb78db078a0d1 9614 net optional ganglia_3.7.2-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfLiv/VYDL+NaNH0uasy9D6O3RHwFAmYpfLYACgkQasy9D6O3 RHwVPw/+J/c3S0PAXr1T19w6vf3IzVd1ssJMdeXUEkGzPQLPwfRXPcptXJyYF+ZB hsrxCCs6GkYZ6oF/2xmHUdrKzf1EjOMl9hN23bT1ADAzb2ebYS+MXZqIsR+m/RUD Zpq6lCnLHTiGf+SUhSFKksgfzklIXL04TRwlYLPh2AaSIWOXQ7V3ziIllIfp5aGJ +xZwM0ME5wv0dCogmvoBjlRbbxJXKv6kqv741wDAUJUSm9rMOwmm6pH2iYiw9Yyj ZJHCpn7255jy3h/2vzQMWZbOhujFjwvzND4rgvGDhremYyhL0R/0oGeN0AeG9EXP 5QUphOQV7g29Qlz48ovPXiwwu/49bPh0xt0WyyHO8IY2I4mt5dhIkq2i9XsJSOI7 L0jwXHwTKHK1gQhZnLrM+cgKcNbXYcgNN2kOjefP3HAyts+liXKyiVrfk6L9/lRO 196A3yzpnvEHtGlkowI+po8LNsIL1BK1Lss0Vd3i2XWhoB947Gi87cJBLSz3ddz/ qvejqTeWQl29TO6rEH6gpFqZWrla/r1UmOkPSFeNcU8jmSpm4BEo0r6gEq+IPatt pwzpK/JCbBijUYu2cqQuYEe5RjkKcgeoDqGV1HZT3G3AReMjaVgglJh+fRNbMqTW
Processed: forcibly merging 1060789 1069351, tagging 1060789 ...
Processing commands for cont...@bugs.debian.org: > forcemerge 1060789 1069351 Bug #1060789 [src:strace] strace FTBFS with linux-libc-dev >= 6.6 Bug #1060789 [src:strace] strace FTBFS with linux-libc-dev >= 6.6 Added tag(s) trixie and sid. Bug #1069351 [src:strace] strace: FTBFS on arm64: ../../src/xlat/btrfs_key_types.h:167:37: error: ‘BTRFS_EXTENT_REF_V0_KEY’ undeclared here (not in a function); did you mean ‘BTRFS_EXTENT_DATA_KEY’? Merged 1060789 1069351 > tags 1060789 + fixed-upstream Bug #1060789 [src:strace] strace FTBFS with linux-libc-dev >= 6.6 Bug #1069351 [src:strace] strace: FTBFS on arm64: ../../src/xlat/btrfs_key_types.h:167:37: error: ‘BTRFS_EXTENT_REF_V0_KEY’ undeclared here (not in a function); did you mean ‘BTRFS_EXTENT_DATA_KEY’? Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > forwarded 1060789 > https://github.com/strace/strace/commit/4eda6d7b61f46d81f7f87afa6fa802dcbe136ca1 Bug #1060789 [src:strace] strace FTBFS with linux-libc-dev >= 6.6 Bug #1069351 [src:strace] strace: FTBFS on arm64: ../../src/xlat/btrfs_key_types.h:167:37: error: ‘BTRFS_EXTENT_REF_V0_KEY’ undeclared here (not in a function); did you mean ‘BTRFS_EXTENT_DATA_KEY’? Set Bug forwarded-to-address to 'https://github.com/strace/strace/commit/4eda6d7b61f46d81f7f87afa6fa802dcbe136ca1'. Set Bug forwarded-to-address to 'https://github.com/strace/strace/commit/4eda6d7b61f46d81f7f87afa6fa802dcbe136ca1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060789 1069351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1042886 is normal, tagging 1042886
Processing commands for cont...@bugs.debian.org: > severity 1042886 normal Bug #1042886 [zstd] zstd libzstd1 breaks boot mkinitramfs update-initramfs-u initramfs-tools Severity set to 'normal' from 'critical' > tags 1042886 + moreinfo Bug #1042886 [zstd] zstd libzstd1 breaks boot mkinitramfs update-initramfs-u initramfs-tools Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064311: rdkit: NMU diff for 64-bit time_t transition
On Wed, Apr 24, 2024 at 09:25:29AM +0300, Andrius Merkys wrote: > Hi, > > On Mon, 19 Feb 2024 21:35:16 + Steve Langasek > wrote:> Since turning on 64-bit time_t is being handled centrally through a > change > > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is > > important that libraries affected by this ABI change all be uploaded close > > together in time. Therefore I have prepared a 0-day NMU for rdkit > > which will initially be uploaded to experimental if possible, then to > > unstable after packages have cleared binary NEW. > > > > Please find the patch for this NMU attached. > > It is most likely my fault this has not been resolved yet - by uploading > 202309.3-3 I trashed 202309.3-2.1~exp1. Am I right that I should reupload > rdkit with t64 binaries to experimental now? t64 is already in unstable and making its way to testing. So you are a bit late with getting rdkit fixed for t64. 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. Chris
Processed: fixed 1069793 in 0.1.0-3
Processing commands for cont...@bugs.debian.org: > fixed 1069793 0.1.0-3 Bug #1069793 [reform-setup-wizard] wrong package name mnt-reform-setup-wizard -- should be reform-setup-wizard Marked as fixed in versions reform-setup-wizard/0.1.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069793: wrong package name mnt-reform-setup-wizard -- should be reform-setup-wizard
Package: reform-setup-wizard Version: 0.1.0-1 Severity: serious As it says in subject.
Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 29
On Wed, Apr 24, 2024 at 5:04 PM Santiago Vila wrote: > > Jeremy Bícha wrote: > > It was also marked as severity important instead of RC because it does not > > affect official buildds. > > Not true: > > https://buildd.debian.org/status/logs.php?pkg=libsoup2.4=all > > See also: > > https://buildd.debian.org/status/logs.php?pkg=gcr=all > > and also: > > https://buildd.debian.org/status/logs.php?pkg=gcr4=amd64 > > And regardless of the severity of the day, you were *explicitly* asked > by Sebastian Ramacher to disable *or* fix the flaky tests: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562#17 > > Note that it's "or", nobody is asking you to act heroically and spend a time > that you don't have. We just want to build the packages without random > failures, > and for that it's enough to disable the tests that we know to be broken. > It can't be so much difficult. I believe you are thinking about https://bugs.debian.org/1057562 The issue I am talking about now is https://bugs.debian.org/1064744 which is different and one I that I don't recall you or Sebastian interacting with me on. Also, whatever affects libsoup2.4/all on those builds is different as its test failures are different that what was reported here or at 1064744. There isn't currently a Debian bug for that issue. Thank you, Jeremy Bícha
Bug#1066225: marked as done (libtranscript: FTBFS: .config.c:12:9: error: implicit declaration of function ‘puts’ [-Werror=implicit-function-declaration])
Your message dated Wed, 24 Apr 2024 21:06:41 + with message-id and subject line Bug#1066225: fixed in libtranscript 0.3.3-1.1 has caused the Debian Bug report #1066225, regarding libtranscript: FTBFS: .config.c:12:9: error: implicit declaration of function ‘puts’ [-Werror=implicit-function-declaration] 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.) -- 1066225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtranscript Version: 0.3.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o .config.o .config.c > .config.c: In function ‘main’: > .config.c:12:9: error: implicit declaration of function ‘puts’ > [-Werror=implicit-function-declaration] >12 | puts(entry->d_name[0]); > | ^~~~ > .config.c:4:1: note: include ‘’ or provide a declaration of ‘puts’ > 3 | #include > +++ |+#include > 4 | > .config.c:12:27: warning: passing argument 1 of ‘puts’ makes pointer from > integer without a cast [-Wint-conversion] >12 | puts(entry->d_name[0]); > | ~^~~ > | | > | char > .config.c:12:27: note: expected ‘const char *’ but argument is of type ‘char’ > cc1: some warnings being treated as errors > make[1]: *** [.Makefile:19: .config.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libtranscript_0.3.3-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libtranscript Source-Version: 0.3.3-1.1 Done: Bo YU We believe that the bug you reported is fixed in the latest version of libtranscript, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bo YU (supplier of updated libtranscript 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: Wed, 24 Apr 2024 00:14:00 +0800 Source: libtranscript Architecture: source Version: 0.3.3-1.1 Distribution: unstable Urgency: medium Maintainer: Gertjan Halkes Changed-By: Bo YU Closes: 1066225 Changes: libtranscript (0.3.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add 00-fix-impfuncdef-issue.patch to fix ftbfs issue. (Closes: #1066225) Checksums-Sha1: 858932d558fdd9cc1d083e3d72150640119750da 1878 libtranscript_0.3.3-1.1.dsc b9ed11939bca771ab623fcc99f5ae5789375bdc5 2376 libtranscript_0.3.3-1.1.debian.tar.xz fa21748ea62cc8f33df2ff92ff7850a1b9b2398b 6841 libtranscript_0.3.3-1.1_amd64.buildinfo Checksums-Sha256: aa0183079b9b9c02f4473637b49a8c017bb5cdcc047f6735ebde6a81b18c1209 1878 libtranscript_0.3.3-1.1.dsc 4eb16f612c90e1620c78320b0143e85405d85be3b0efeb349b91fc2374d22ccc 2376 libtranscript_0.3.3-1.1.debian.tar.xz
Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 29
Jeremy Bícha wrote: It was also marked as severity important instead of RC because it does not affect official buildds. Not true: https://buildd.debian.org/status/logs.php?pkg=libsoup2.4=all See also: https://buildd.debian.org/status/logs.php?pkg=gcr=all and also: https://buildd.debian.org/status/logs.php?pkg=gcr4=amd64 And regardless of the severity of the day, you were *explicitly* asked by Sebastian Ramacher to disable *or* fix the flaky tests: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562#17 Note that it's "or", nobody is asking you to act heroically and spend a time that you don't have. We just want to build the packages without random failures, and for that it's enough to disable the tests that we know to be broken. It can't be so much difficult.
Bug#1066372: marked as done (baycomepp: FTBFS: eppfpga.c:240:63: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration])
Your message dated Wed, 24 Apr 2024 20:36:14 + with message-id and subject line Bug#1066372: fixed in baycomepp 0.10-18 has caused the Debian Bug report #1066372, regarding baycomepp: FTBFS: eppfpga.c:240:63: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration] 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.) -- 1066372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: baycomepp Version: 0.10-17 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DCONFIGDIR=\"/usr/etc\" > -DLOCALSTATEDIR=\"/usr/var\" -I../directx/include > -I../directx/include/directx6 -I.. -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wl,-z,defs -Wall -MT snprintpkt.o -MD -MP -MF .deps/snprintpkt.Tpo -c -o > snprintpkt.o snprintpkt.c > rm -f libresident2.a > rm -f libmisc.a > ar cru libresident2.a > ar cru libmisc.a > ar: `u' modifier ignored since `D' is the default (see `U') > ranlib libresident2.a > ar: `u' modifier ignored since `D' is the default (see `U') > ranlib libmisc.a > ppdirectinit.c: In function ‘parport_ecp’: > ppdirectinit.c:393:45: warning: variable ‘readIntrThreshold’ set but not used > [-Wunused-but-set-variable] > 393 | int fifo_depth, writeIntrThreshold, readIntrThreshold; > | ^ > ppdirectinit.c:393:25: warning: variable ‘writeIntrThreshold’ set but not > used [-Wunused-but-set-variable] > 393 | int fifo_depth, writeIntrThreshold, readIntrThreshold; > | ^~ > eppfpga.c: In function ‘main’: > eppfpga.c:240:63: error: implicit declaration of function ‘strcmp’ > [-Werror=implicit-function-declaration] > 240 | for (tst = eppfpgatests; tst->name && > strcmp(optarg, tst->name); tst++); > | ^~ > eppfpga.c:52:1: note: include ‘’ or provide a declaration of > ‘strcmp’ >51 | #include "fpga.h" > +++ |+#include >52 | > eppfpga.c:139:53: warning: variable ‘ppdev’ set but not used > [-Wunused-but-set-variable] > 139 | const char *ppuser = NULL, *ppkdrv = NULL, *ppdev = NULL; > | ^ > eppfpga.c:139:37: warning: variable ‘ppkdrv’ set but not used > [-Wunused-but-set-variable] > 139 | const char *ppuser = NULL, *ppkdrv = NULL, *ppdev = NULL; > | ^~ > eppfpga.c:139:21: warning: variable ‘ppuser’ set but not used > [-Wunused-but-set-variable] > 139 | const char *ppuser = NULL, *ppkdrv = NULL, *ppdev = NULL; > | ^~ > eppfpga.c:138:67: warning: variable ‘w9xring0’ set but not used > [-Wunused-but-set-variable] > 138 | unsigned int iobase = 0x378, ntddkgenport = 0, ntdrv = 0, > w9xring0 = 0, ppflags = 0; > | > ^~~~ > eppfpga.c:138:56: warning: variable ‘ntdrv’ set but not used > [-Wunused-but-set-variable] > 138 | unsigned int iobase = 0x378, ntddkgenport = 0, ntdrv = 0, > w9xring0 = 0, ppflags = 0; > |^ > eppfpga.c:138:38: warning: variable ‘ntddkgenport’ set but not used > [-Wunused-but-set-variable] > 138 | unsigned int iobase = 0x378, ntddkgenport = 0, ntdrv = 0, > w9xring0 = 0, ppflags = 0; > | ^~~~ > fpgatests.c: In function ‘ledtest’: > fpgatests.c:319:21: warning: operation on ‘led’ may be undefined > [-Wsequence-point] > 319 | led = (++led) & 3; > | ^ > fpgatests.c: In function ‘chkledtest’: > fpgatests.c:579:21: warning: operation on ‘led’ may be undefined >
Bug#1066286: marked as done (das-watchdog: FTBFS: test_rt.c:32:33: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration])
Your message dated Wed, 24 Apr 2024 20:36:25 +
with message-id
and subject line Bug#1066286: fixed in das-watchdog 0.9.0-5
has caused the Debian Bug report #1066286,
regarding das-watchdog: FTBFS: test_rt.c:32:33: error: implicit declaration of
function ‘getpid’ [-Werror=implicit-function-declaration]
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.)
--
1066286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: das-watchdog
Version: 0.9.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -Wl,-z,relro -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 test_rt.c -o test_rt
> test_rt.c: In function ‘main’:
> test_rt.c:32:33: error: implicit declaration of function ‘getpid’
> [-Werror=implicit-function-declaration]
>32 | printf("My pid is %d\n",getpid());
> | ^~
> test_rt.c:33:9: error: implicit declaration of function ‘sleep’
> [-Werror=implicit-function-declaration]
>33 | sleep(1);
> | ^
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:14: all] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/das-watchdog_0.9.0-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: das-watchdog
Source-Version: 0.9.0-5
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
das-watchdog, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated das-watchdog
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: Wed, 24 Apr 2024 22:21:36 +0200
Source: das-watchdog
Architecture: source
Version: 0.9.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 1066286
Changes:
das-watchdog (0.9.0-5) unstable; urgency=medium
.
* Team upload
* debian/patches: Fix build with -Werror=implicit-functon-declaration
(Closes: #1066286)
Checksums-Sha1:
7f55017501647c5bf4c5b9d13d6f2283fc5f971a 1332 das-watchdog_0.9.0-5.dsc
f6d966326402a6c8ab706be2ea4423c2380e1ee2 6020
das-watchdog_0.9.0-5.debian.tar.xz
8b34eea837b92fe2a5511c21bdf22eb9d656f403 8967
das-watchdog_0.9.0-5_amd64.buildinfo
Checksums-Sha256:
f8b09bcce274d0de2d730df63bdaf96f422a2473988150578cc457bcf2a0adf2 1332
das-watchdog_0.9.0-5.dsc
b658ea4c1db8179c5659cc7e01730005441a041f766100e44d9c7a749d141c13 6020
das-watchdog_0.9.0-5.debian.tar.xz
a7d7f30aae3b88fe3aa67103d3167cbceb215f467794441ae6029c92152996bd 8967
das-watchdog_0.9.0-5_amd64.buildinfo
Files:
b22e27d8c99e5ee3d548c048893eac25 1332 admin optional das-watchdog_0.9.0-5.dsc
1922ff05e4fa234e1975369925e498f0 6020
Bug#1069379: marked as done (uhttpmock: FTBFS on arm64: Failed to load TLS database: System trust contains zero trusted certificates)
Your message dated Wed, 24 Apr 2024 16:31:37 -0400 with message-id and subject line Re: Bug#1069379: uhttpmock: FTBFS on arm64: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory has caused the Debian Bug report #1069379, regarding uhttpmock: FTBFS on arm64: Failed to load TLS database: System trust contains zero trusted certificates 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.) -- 1069379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uhttpmock Version: 0.10.0-2 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[1]: Entering directory '/<>' > dh_auto_configure -- -Dauto_features=enabled > cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb > LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain > --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --libdir=lib/aarch64-linux-gnu -Dpython.bytecompile=-1 -Dauto_features=enabled > The Meson build system > Version: 1.4.0 > Source dir: /<> > Build dir: /<>/obj-aarch64-linux-gnu > Build type: native build > Project name: uhttpmock > Project version: 0.10.0 > C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-23) > 13.2.0") > C linker for the host machine: cc ld.bfd 2.42 > Host machine cpu family: aarch64 > Host machine cpu: aarch64 > Configuring uhm-version.h using configuration > Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 > Run-time dependency glib-2.0 found: YES 2.78.4 > Run-time dependency gio-2.0 found: YES 2.78.4 > Run-time dependency libsoup-3.0 found: YES 3.4.4 > Compiler for C supports link arguments > -Wl,--version-script,/<>/libuhttpmock/libuhttpmock.map: YES > Run-time dependency gobject-introspection-1.0 found: YES 1.78.1 > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/aarch64-linux-gnu-g-ir-scanner found: YES > (/usr/bin/aarch64-linux-gnu-g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached) > Program /usr/bin/aarch64-linux-gnu-g-ir-compiler found: YES > (/usr/bin/aarch64-linux-gnu-g-ir-compiler) > Program vapigen found: YES (/usr/bin/vapigen) > Program vapigen found: YES (/usr/bin/vapigen) > Configuring version.xml using configuration > Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) > Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj) > Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb) > Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml) > Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref) > Build targets in project: 8 > > uhttpmock 0.10.0 > > User defined options > auto_features : enabled > buildtype : plain > libdir: lib/aarch64-linux-gnu > localstatedir : /var > prefix: /usr > sysconfdir: /etc > wrap_mode : nodownload > python.bytecompile: -1 > > Found ninja-1.11.1 at /usr/bin/ninja > make[1]: Leaving directory '/<>' >dh_auto_build > cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v > [1/12] cc -Ilibuhttpmock/libuhttpmock-1.0.so.1.2.3.p -Ilibuhttpmock > -I../libuhttpmock -I/usr/include/glib-2.0 > -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/libsoup-3.0 -I/usr/include/sysprof-6 > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -mbranch-protection=standard -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -pthread '-DG_LOG_DOMAIN="libuhttpmock"' -MD -MQ > libuhttpmock/libuhttpmock-1.0.so.1.2.3.p/uhm-message.c.o -MF > libuhttpmock/libuhttpmock-1.0.so.1.2.3.p/uhm-message.c.o.d -o > libuhttpmock/libuhttpmock-1.0.so.1.2.3.p/uhm-message.c.o -c > ../libuhttpmock/uhm-message.c > [2/12] cc -Ilibuhttpmock/libuhttpmock-1.0.so.1.2.3.p -Ilibuhttpmock > -I../libuhttpmock -I/usr/include/glib-2.0 > -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/libsoup-3.0 -I/usr/include/sysprof-6 > -fdiagnostics-color=always
Bug#1066286: marked as pending in das-watchdog
Control: tag -1 pending Hello, Bug #1066286 in das-watchdog 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/multimedia-team/das-watchdog/-/commit/68dd9fd14892b651b185c11e05bb485f204dfb92 Fix build Closes: #1066286 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066286
Processed: Bug#1066286 marked as pending in das-watchdog
Processing control commands: > tag -1 pending Bug #1066286 [src:das-watchdog] das-watchdog: FTBFS: test_rt.c:32:33: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069790: librust-err-derive-dev: impossible to install
Package: librust-err-derive-dev Version: 0.3.1-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package is impossible to install: Depends on missing package librust-synstructure-0.12+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYpaNIACgkQLHwxRsGg ASEESg/+POdwe0xl1jXHdABhugoBy9kUpja/kNUmFwOhT5eU+VfHjet7qRzjxqEd SDBKQMHTFzE7d2UMK0fHKurIBcCIkjRZhfB+pA88v40ko6i9c06+S2MIYMcXHMX9 rLquG7Gz4by8N9Yh3AiOqc/ljveNfchn/pjSwkxitc2HFvv7LmL9wxxRFykZ1KvX YaU8T+JH5kZ/eB4WOS+5bYLDG/QCrklN1tzXcT7U9OWKo1dFa9wGK/SWvpNTprb5 xptqFMhpNg/ibbz5w1RM7+qmTCsMCAGSqYr3xre2/ypbzBL/IjHI20weayMX+XgO O5/QpZj1ISnqYHc7eRoNYDLVdpCmmsYZ4tmC2bYhmEh+u/ch6Q+i4CGRKEULACL4 uUAEX0+lhMSkMHoAK0tgL8/5CqWBAel37cav+naoHhswiVzjtfUISlTJF0qy4C7t XQEXo3Wnwscf9UYQh3343WzQhK6Qnh4/pMMyGDHemAE78DMLiCGJH0T2Z3JKf0wY JYTDe1G2D/M8iIBzb2WXAgTayuME3UR0OeD1vmFaU6lmcLBY1TvRzddsAcB5wvNL jWeAQQWkDXBJDBReW4//YHaRYuUKgi/zeXA64v+4ctybFa7vYMhiHWWpf3gpjzCZ H5NzZmRMXEWWohLwFucWYJbuWtW9A8sgJApsIZN1S+KqASukEz4= =ZqUd -END PGP SIGNATURE-
Bug#1069554: [Pkg-pascal-devel] Bug#1069554: this is no bug in the package, bug in the script doing the rebuild?
On 24/04/2024 20:38, Rene Engelhard wrote: My point is that you don't need the alternative. Hi Rene, but it would surely be needed if someone wanted to build winff from source on armel? Even though that case is perhaps unlikely. I can't see how the alternative is doing any harm. Regards, Peter
Bug#1069554: [Pkg-pascal-devel] Bug#1069554: this is no bug in the package, bug in the script doing the rebuild?
Hi, Am 24.04.24 um 21:35 schrieb Peter B: Why is it bad? The nogui's are lighter dependencies than the gui packages. Exactly. That#s why they should be used in package building for converting stuff. One or the other is needed. Surely better to use the nogui if its available? It is available. As indep builds are not done on armel that it's not available on armel does not really matter :) My point is that you don't need the alternative. Regards, Rene
Bug#1067379: marked as done (python-measurement: FTBFS: make: *** [debian/rules:9: build] Error 25)
Your message dated Wed, 24 Apr 2024 19:36:26 +
with message-id
and subject line Bug#1067379: fixed in python-measurement 3.2.2-2
has caused the Debian Bug report #1067379,
regarding python-measurement: FTBFS: make: *** [debian/rules:9: build] 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.)
--
1067379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-measurement
Version: 3.2.2-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):
> debian/rules build
> dh build --with sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> E: pybuild pybuild:389: configure: plugin pyproject failed with: PEP517
> plugin dependencies are not available. Please Build-Depend on
> pybuild-plugin-pyproject.
> dh_auto_configure: error: pybuild --configure -i python{version} -p "3.12
> 3.11" returned exit code 13
> make: *** [debian/rules:9: build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2024/03/19/python-measurement_3.2.2-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-measurement
Source-Version: 3.2.2-2
Done: Alexandre Detiste
We believe that the bug you reported is fixed in the latest version of
python-measurement, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alexandre Detiste (supplier of updated python-measurement
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: Wed, 24 Apr 2024 20:51:04 +0200
Source: python-measurement
Architecture: source
Version: 3.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Alexandre Detiste
Closes: 1067379
Changes:
python-measurement (3.2.2-2) unstable; urgency=medium
.
* Team upload.
* add dependency on pybuild-plugin-pyproject (Closes: #1067379)
* set Rules-Requires-Root: no
Checksums-Sha1:
bb8e4bc8d8a70a59a269902d7569402df5b96245 2329 python-measurement_3.2.2-2.dsc
f34e480437dcb850fec937c4b3ab83a317a8e59c 4500
python-measurement_3.2.2-2.debian.tar.xz
7a653ff0308544143954e18016a6c2fd683f7904 8581
python-measurement_3.2.2-2_source.buildinfo
Checksums-Sha256:
4cf22cd84efcb0c063d45027a09d98f7c662e4864d293165d58fc76dfa020099 2329
python-measurement_3.2.2-2.dsc
8c7f3329cf450b18dc7397965958f54d565f4409789b5f6225cce3d540914a44 4500
python-measurement_3.2.2-2.debian.tar.xz
7bb7ccda3c2fa7a50e83dd9222691354ccc58a056d179f9695a0763a34cf2442 8581
python-measurement_3.2.2-2_source.buildinfo
Files:
1db08a1b1cc6fd930e31db74c66dd5bd 2329 python optional
python-measurement_3.2.2-2.dsc
ce6cd41eb7e481c8e3f89b058574d536 4500 python optional
python-measurement_3.2.2-2.debian.tar.xz
1532509c4f4474259439b83df601db99 8581 python optional
python-measurement_3.2.2-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmYpWvwRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBriGw/9E3YGiEbObXl5UlefL9C39LH1vYpvxnKr
hJFBtVB+h7x+GLbLIJRlwWUeWWKwEymimKT+rfRX9FteHBgyrzDMM/ivzs1jdqul
Bug#1069554: [Pkg-pascal-devel] Bug#1069554: this is no bug in the package, bug in the script doing the rebuild?
On 24/04/2024 20:02, Rene Engelhard wrote: This bugreport now caused the following "fix" in winff: Build-Depends-Indep: faketime, libreoffice-draw-nogui | libreoffice-draw, libreoffice-writer-nogui | libreoffice-writer, which I consider bad... Hi Rene, Why is it bad? The nogui's are lighter dependencies than the gui packages. One or the other is needed. Surely better to use the nogui if its available? Regards, Peter P.S. Relates to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065447
Bug#1061015: marked as done (pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept')
Your message dated Wed, 24 Apr 2024 19:07:16 +
with message-id
and subject line Bug#1061015: fixed in pygame-sdl2 8.2.1-1
has caused the Debian Bug report #1061015,
regarding pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) except?
-1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'
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.)
--
1061015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygame-sdl2
Version: 8.1.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> /<>/setuplib.py:269: SyntaxWarning: invalid escape sequence '\('
> ccode = re.sub('Py_InitModule4\("([^"]+)"', 'Py_InitModule4("' +
> parent_module + '.\\1"', ccode) # Py2
>
> Error compiling Cython file:
>
> ...
> sf.base = base
> sf.length = length
> sf.tell = 0
>
> rv = SDL_AllocRW()
> rv.size = subfile_size
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:336:22: Cannot assign type 'Sint64 (SDL_RWops *)
> except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'. Exception values are
> incompatible. Suggest adding 'noexcept' to type 'Sint64 (SDL_RWops *) except?
> -1 nogil'.
>
> Error compiling Cython file:
>
> ...
> sf.length = length
> sf.tell = 0
>
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:337:22: Cannot assign type 'Sint64 (SDL_RWops *,
> Sint64, int) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *, Sint64, int)
> noexcept'. Exception values are incompatible. Suggest adding 'noexcept' to
> type 'Sint64 (SDL_RWops *, Sint64, int) except? -1 nogil'.
>
> Error compiling Cython file:
>
> ...
> sf.tell = 0
>
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> rv.read = subfile_read
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:338:22: Cannot assign type 'size_t (SDL_RWops *,
> void *, size_t, size_t) except? -1 nogil' to 'size_t (*)(SDL_RWops *, void *,
> size_t, size_t) noexcept'. Exception values are incompatible. Suggest adding
> 'noexcept' to type 'size_t (SDL_RWops *, void *, size_t, size_t) except? -1
> nogil'.
>
> Error compiling Cython file:
>
> ...
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> rv.read = subfile_read
> rv.write = NULL
> rv.close = subfile_close
>^
>
>
> src/pygame_sdl2/rwobject.pyx:340:23: Cannot assign type 'int (SDL_RWops *)
> except? -1 nogil' to 'int (*)(SDL_RWops *) noexcept'. Exception values are
> incompatible. Suggest adding 'noexcept' to type 'int (SDL_RWops *) except? -1
> nogil'.
>
> Error compiling Cython file:
>
> ...
> raise IOError("{!r} is not a filename or file-like
> object.".format(filelike))
>
> Py_INCREF(filelike)
>
> rv = SDL_AllocRW()
> rv.size = python_size
> ^
>
>
> src/pygame_sdl2/rwobject.pyx:367:14: Cannot assign type 'Sint64 (SDL_RWops *)
> except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'. Exception values are
> incompatible. Suggest adding 'noexcept' to type 'Sint64 (SDL_RWops *) except?
> -1 nogil'.
>
> Error compiling Cython file:
>
> ...
>
> Py_INCREF(filelike)
>
> rv =
Bug#1069554: this is no bug in the package, bug in the script doing the rebuild?
Hi Lucas, this is no bug in the package AFAICS. libreoffice-draw-nogui is clearly only in Build-Depends-Indep: Build-Depends: debhelper-compat (= 13), fpc, libgtk2.0-dev, lcl, lcl-qt5, Build-Depends-Indep: libreoffice-draw-nogui, libreoffice-writer, So it's only needed for _all builds. So why would the build-deps be uninstallable on armel? Or do your scripts do full builds and not --binary-arch/-B or whatever applicable? (And yes, that nogui is not available on armel is a deliberate decision. It's dead, and nooone will hopefully want to use it for document conversion. And I don't want to force a full double build on armel.) This bugreport now caused the following "fix" in winff: Build-Depends-Indep: faketime, libreoffice-draw-nogui | libreoffice-draw, libreoffice-writer-nogui | libreoffice-writer, which I consider bad... Regards, Rene
Bug#1067379: marked as pending in python-measurement
Control: tag -1 pending Hello, Bug #1067379 in python-measurement 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/python-team/packages/python-measurement/-/commit/1ac4764cf3bcaab1292a59b4d564d51881803982 add dependency on pybuild-plugin-pyproject (Closes: #1067379) (this message was generated automatically) -- Greetings https://bugs.debian.org/1067379
Processed: Bug#1067379 marked as pending in python-measurement
Processing control commands: > tag -1 pending Bug #1067379 [src:python-measurement] python-measurement: FTBFS: make: *** [debian/rules:9: build] Error 25 Added tag(s) pending. -- 1067379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069789: test_bluetooth_hidpp_mouse autopkgtest fails
Package: upower Version: 1.90.3-1 Severity: serious Control: forwarded -1 https://gitlab.freedesktop.org/upower/upower/-/issues/228 Control: tags -1 + upstream https://ci.debian.net/packages/u/upower/unstable/amd64/45053064/ 217s == 217s ERROR: test_bluetooth_hidpp_mouse (__main__.Tests.test_bluetooth_hidpp_mouse) 217s Logitech Bluetooth LE mouse with HID++ kernel support 217s -- 217s Traceback (most recent call last): 217s File "/usr/libexec/upower/integration-test.py", line 2337, in test_bluetooth_hidpp_mouse 217s self.assertEqual(self.get_dbus_dev_property(bat0_up, 'Model'), alias) 217s 217s File "/usr/libexec/upower/integration-test.py", line 273, in get_dbus_dev_property 217s return self.dbus.call_sync(UP, device, 217s^^^ 217s gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/freedesktop/UPower/devices/mouse_dev_11_22_33_44_AA_BB” (19) -- 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/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages upower depends on: ii dbus 1.14.10-4+b1 ii libc6 2.37-18 ii libglib2.0-0t642.78.4-7 ii libgudev-1.0-0 238-5 ii libimobiledevice6 1.3.0-7.1+b1 ii libplist3 2.2.0-7+b1 ii libupower-glib31.90.3-1 ii udev 255.4-1+b1 Versions of packages upower recommends: ii polkitd 124-2 upower suggests no packages. -- debconf-show failed
Bug#1055847: Please check python-sparse issue at Github
On Wed, 2024-04-24 at 15:53 +0200, Andreas Tille wrote: > Hi Diane and Ghislain, > > you are listed as Uploaders of python-sparse. Since I now have other > tasks than maintaining team maintained packages I would be really > happy > if you could subscribe upstream issue > > https://github.com/pydata/sparse/issues/628 > > and continue what I have started. > > Thanks a lot > Andreas. > I subscribed, though I'm still fighting with updating numba. Also I know there are many ways that numba can fail, so odds are sparse's problems are caused by numba. There are definitely problems with numba on arm64. https://github.com/numba/numba/issues/9109 (Also congratulations on your election, I have respect your organizational skills on the med team) Diane
Processed: Re: [Debian-med-packaging] Bug#1069691: libmaus2: FTBFS on arm64: what(): AutoArray failed to allocate 1398102 elements (11184816 bytes)
Processing control commands: > found -1 2.0.813+ds-3 Bug #1069691 [src:libmaus2] libmaus2: FTBFS on arm64: what(): AutoArray failed to allocate 1398102 elements (11184816 bytes) Marked as found in versions libmaus2/2.0.813+ds-3. -- 1069691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069691: [Debian-med-packaging] Bug#1069691: libmaus2: FTBFS on arm64: what(): AutoArray failed to allocate 1398102 elements (11184816 bytes)
Control: found -1 2.0.813+ds-3 Hmn, this is annoying. I do not manage to reproduce the error with qemu-user. The test error is reproducible on buildd's real hardware in the meantime[1], or at least on two of the Arm build machines hosted by Conova. There could be something hardware specific. I'd have to check how things go on porterbox next. [1]: https://buildd.debian.org/status/fetch.php?pkg=libmaus2=arm64=2.0.813%2Bds-3=1713977128=0 Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/0, please excuse my verbosity `- signature.asc Description: PGP signature
Bug#1025655: marked as done (hovercraft: requires python3-setuptools)
Your message dated Wed, 24 Apr 2024 18:02:34 +
with message-id
and subject line Bug#1025655: fixed in hovercraft 2.7-2+deb11u1
has caused the Debian Bug report #1025655,
regarding hovercraft: requires python3-setuptools
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.)
--
1025655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hovercraft
Version: 2.7-2
Severity: important
X-Debbugs-Cc: bms.deb...@barwap.com
Dear Maintainer,
fresh install, running hovercraft
$ hovercraft planning_presentation.rst html
Traceback (most recent call last):
File "/usr/bin/hovercraft", line 33, in
sys.exit(load_entry_point('hovercraft==2.7', 'console_scripts',
'console_script')())
File "/usr/bin/hovercraft", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/share/hovercraft/hovercraft/__init__.py", line 6, in
import pkg_resources
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3243,
in
def _initialize_master_working_set():
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3226,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3255,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 886, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 772, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'setuptools' distribution was not found
and is required by hovercraft
* What outcome did you expect instead?
$ hovercraft planning_presentation.rst html
(No errors - what did happen after apt-get install python3-setuptools)
-- System Information:
Debian Release: 11.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-19-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages hovercraft depends on:
ii libjs-impress 1.0.0-1
ii libjs-sphinxdoc3.4.3-2
ii python33.9.2-3
ii python3-docutils 0.16+dfsg-4
ii python3-lxml 4.6.3+dfsg-0.1+deb11u1
ii python3-pkg-resources 52.0.0-4
ii python3-pygments 2.7.1+dfsg-2.1
ii python3-svg.path 3.0-2
ii python3-watchdog 1.0.2-2
hovercraft recommends no packages.
hovercraft suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: hovercraft
Source-Version: 2.7-2+deb11u1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
hovercraft, 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 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated hovercraft 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: Wed, 24 Apr 2024 06:11:30 +0200
Source: hovercraft
Architecture: source
Version: 2.7-2+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Beckmann
Closes: 1025655
Changes:
Processed: zeroc-ice FTBFS on armel out-of-memory condition
Processing commands for cont...@bugs.debian.org: > tags 1069538 + moreinfo Bug #1069538 [src:zeroc-ice] zeroc-ice: FTBFS on armel: make[3]: *** [Makefile:29: tests] Error 1 Ignoring request to alter tags of bug #1069538 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code
Processing commands for cont...@bugs.debian.org: > # A better title, based on the one by smcv > retitle 1069415 libsoup2.4: FTBFS Failed to load TLS database: System trust > contains zero trusted certificates Bug #1069415 [src:libsoup2.4] libsoup2.4: FTBFS: failing tests Changed Bug title to 'libsoup2.4: FTBFS Failed to load TLS database: System trust contains zero trusted certificates' from 'libsoup2.4: FTBFS: failing tests'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code
Processing commands for cont...@bugs.debian.org: > retitle 1069415 libsoup2.4: FTBFS: failing tests Bug #1069415 [src:libsoup2.4] libsoup2.4: FTBFS on arm64: Failed to load TLS database: System trust contains zero trusted certificates Changed Bug title to 'libsoup2.4: FTBFS: failing tests' from 'libsoup2.4: FTBFS on arm64: Failed to load TLS database: System trust contains zero trusted certificates'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 29
retitle 1069415 libsoup2.4: FTBFS: failing tests
thanks
El 24/4/24 a las 18:26, Andreas Metzler escribió:
On 2024-04-20 Lucas Nussbaum wrote:
Source: libsoup2.4
Version: 2.74.3-7
Severity: serious
Justification: FTBFS
[...]
(hsts-test:547071): GLib-Net-WARNING **: 04:03:06.247: Failed to load TLS
database: System trust contains zero trusted certificates; please investigate
your GnuTLS configuration
FWIW I could not reproduce this on amdahl.debian.org, the build
succeeded.
This is not arm64-specific. It also happens on amd64:
See how the autobuilder for Arch:all had to try 3 times to build the package:
https://buildd.debian.org/status/logs.php?pkg=libsoup2.4=2.74.3-7=all
If you want to debug it or just verify that the test fails very easily on
certain
machines, contact me privately and I will gladly give you access to a machine
where it happens all the time.
In my opinion, the test has a very low quality, so if there is not willingness,
capacity, or just time to fix it (which is fine), then it should be disabled,
because in its current state it is a waste of time for everybody.
No, I don't buy the theory that this is a good way to "remind" that there
is a flaky test. A Release Manager made a similar request ("fix it or disable
it")
in Bug #1057562 but the bug was downgraded again and the request from the
Release
Manager continues to be ignored.
Thanks.
Bug#1065100: efingerd: Depends on libident, which is NBS
Control: reassign -1 release.debian.org Control: retitle -1 nmu: efingerd_1.6.7-1 Control: severity -1 normal On Thu, Feb 29, 2024 at 02:41:54PM -0500, Boyuan Yang wrote: > Severity: serious > Justification: Policy 2.2.1 > > Package efingerd depends on binary package libident, but this package has > been renamed to libident0 due to time64 transition. ... > You may need to rebuild the package. This should just have been filed as a binNMU request to release.debian.org. There was no need to remove the package from testing. A local no-change rebuild shows that it picks up the new libident0 name just fine. Release team, please schedule binNMU for this package. Chris
Processed: Re: Bug#1065100: efingerd: Depends on libident, which is NBS
Processing control commands: > reassign -1 release.debian.org Bug #1065100 [efingerd] efingerd: Depends on libident, which is NBS Bug reassigned from package 'efingerd' to 'release.debian.org'. No longer marked as found in versions efingerd/1.6.7-1. Ignoring request to alter fixed versions of bug #1065100 to the same values previously set > retitle -1 nmu: efingerd_1.6.7-1 Bug #1065100 [release.debian.org] efingerd: Depends on libident, which is NBS Changed Bug title to 'nmu: efingerd_1.6.7-1' from 'efingerd: Depends on libident, which is NBS'. > severity -1 normal Bug #1065100 [release.debian.org] nmu: efingerd_1.6.7-1 Severity set to 'normal' from 'serious' -- 1065100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1064920: FTBFS on 32-bit architectures
Processing commands for cont...@bugs.debian.org:
> reopen 1064920
Bug #1064920 {Done: Taihsiang Ho (tai271828) }
[src:rshim-user-space] FTBFS on 32-bit architectures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions rshim-user-space/2.0.20+debian-2.
> quit
Stopping processing here.
Please contact me if you need assistance.
--
1064920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 29
On 2024-04-20 Lucas Nussbaum wrote: > Source: libsoup2.4 > Version: 2.74.3-7 > Severity: serious > Justification: FTBFS [...] > > (hsts-test:547071): GLib-Net-WARNING **: 04:03:06.247: Failed to load TLS > > database: System trust contains zero trusted certificates; please > > investigate your GnuTLS configuration FWIW I could not reproduce this on amdahl.debian.org, the build succeeded. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1066355: marked as done (spotlighter: FTBFS: spotlighter.c:105:3: error: implicit declaration of function ‘on_window_screen_changed’ [-Werror=implicit-function-declaration])
Your message dated Wed, 24 Apr 2024 16:05:34 + with message-id and subject line Bug#1066355: fixed in spotlighter 0.3-1.2 has caused the Debian Bug report #1066355, regarding spotlighter: FTBFS: spotlighter.c:105:3: error: implicit declaration of function ‘on_window_screen_changed’ [-Werror=implicit-function-declaration] 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.) -- 1066355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spotlighter Version: 0.3-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" > -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" > -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz > -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/webp > -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/webp > -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o spotlighter-spotlighter.o `test > -f 'spotlighter.c' || echo './'`spotlighter.c > spotlighter.c: In function ‘create_window’: > spotlighter.c:102:3: warning: ‘gtk_widget_set_double_buffered’ is deprecated > [-Wdeprecated-declarations] > 102 | gtk_widget_set_double_buffered (window, FALSE); > | ^~ > In file included from /usr/include/gtk-3.0/gtk/gtkapplication.h:27, > from /usr/include/gtk-3.0/gtk/gtkwindow.h:33, > from /usr/include/gtk-3.0/gtk/gtkdialog.h:32, > from /usr/include/gtk-3.0/gtk/gtkaboutdialog.h:30, > from /usr/include/gtk-3.0/gtk/gtk.h:31, > from spotlighter.h:27, > from spotlighter.c:23: > /usr/include/gtk-3.0/gtk/gtkwidget.h:883:23: note: declared here > 883 | void gtk_widget_set_double_buffered(GtkWidget > *widget, > | ^~ > spotlighter.c:105:3: error: implicit declaration of function > ‘on_window_screen_changed’ [-Werror=implicit-function-declaration] > 105 | on_window_screen_changed (window, NULL, NULL); > | ^~~~ > spotlighter.c:108:3: warning: ‘gtk_window_set_opacity’ is deprecated: Use > 'gtk_widget_set_opacity' instead [-Wdeprecated-declarations] > 108 | gtk_window_set_opacity (GTK_WINDOW (window), 0); > | ^~ > /usr/include/gtk-3.0/gtk/gtkwindow.h:200:12: note: declared here > 200 | void gtk_window_set_opacity (GtkWindow > *window, > |^~ > spotlighter.c:110:3: warning: ‘gdk_screen_width’ is deprecated > [-Wdeprecated-declarations] > 110 | int width = gdk_screen_width (); > | ^~~ > In file included from /usr/include/gtk-3.0/gdk/gdk.h:50, > from /usr/include/gtk-3.0/gtk/gtk.h:30: >
Bug#1064920: FTBFS on 32-bit architectures
Status update: the previous pull request would create version
2.0.20+debian-2 but it only includes the fix for armhf. i386 needs to
be fixed as well
https://buildd.debian.org/status/logs.php?pkg=rshim-user-space=i386
. I will make another merge request to include the fix for i386. -tai
On Mon, Apr 22, 2024 at 8:00 PM Taihsiang Ho (tai271828)
wrote:
>
> I created a pull request to fix the build issue. Please review
> https://salsa.debian.org/bluefield-team/rshim-user-space/-/merge_requests/11
> -tai
>
> On Tue, Feb 27, 2024 at 7:27 PM dann frazier wrote:
> >
> > Source: rshim-user-space
> > Version: 2.0.12+debian-1
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the
> > past)
> >
> > The switch to fuse3 appears to have introduced a build issue for 32-bit
> > architectures such as armhf:
> >
> > From
> > https://buildd.debian.org/status/fetch.php?pkg=rshim-user-space=armhf=2.0.20%2Bdebian-1=1709056732=0
> > :
> >
> > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -DHAVE_RSHIM_NET
> > -I/usr/include/libusb-1.0 -DHAVE_RSHIM_USB
> > -I/usr/include/arm-linux-gnueabihf -DHAVE_RSHIM_PCIE -I/usr/include/fuse3
> > -DHAVE_RSHIM_FUSE -Wdate-time -D_FORTIFY_SOURCE=2 -DFUSE_USE_VERSION=30
> > -DDEFAULT_RSHIM_CONFIG_FILE='"/etc/rshim.conf"' -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong
> > -fstack-clash-protection -Wformat -Werror=format-security -c -o
> > rshim-rshim_fuse.o `test -f 'rshim_fuse.c' || echo './'`rshim_fuse.c
> > In file included from /usr/include/fuse3/fuse_lowlevel.h:25,
> > from /usr/include/fuse3/cuse_lowlevel.h:19,
> > from rshim_fuse.c:23:
> > /usr/include/fuse3/fuse_common.h:928:1: error: static assertion failed:
> > "fuse: off_t must be 64bit"
> > 928 | _Static_assert(sizeof(off_t) == 8, "fuse: off_t must be 64bit");
> > | ^~
> > rshim_pcie.c: In function ‘rshim_pcie_mmap_vfio’:
> > rshim_pcie.c:52:37: warning: overflow in conversion from ‘long long
> > unsigned int’ to ‘__off_t’ {aka ‘long int’} changes value from
> > ‘7696581394436’ to ‘4’ [-Woverflow]
> >52 | #define VFIO_GET_REGION_ADDR(x) ((uint64_t) x << 40ULL)
> > | ^
> > rshim_pcie.c:634:18: note: in expansion of macro ‘VFIO_GET_REGION_ADDR’
> > 634 | VFIO_GET_REGION_ADDR(VFIO_PCI_CONFIG_REGION_INDEX)
> > +
> > | ^~~~
> > rshim_pcie.c:52:37: warning: overflow in conversion from ‘long long
> > unsigned int’ to ‘__off_t’ {aka ‘long int’} changes value from
> > ‘7696581394436’ to ‘4’ [-Woverflow]
> >52 | #define VFIO_GET_REGION_ADDR(x) ((uint64_t) x << 40ULL)
> > | ^
> > rshim_pcie.c:643:19: note: in expansion of macro ‘VFIO_GET_REGION_ADDR’
> > 643 |
> > VFIO_GET_REGION_ADDR(VFIO_PCI_CONFIG_REGION_INDEX) +
> > | ^~~~
> > rshim_fuse.c: In function ‘rshim_fuse_misc_read’:
> > rshim_fuse.c:713:36: warning: format ‘%ld’ expects argument of type ‘long
> > int’, but argument 5 has type ‘uint64_t’ {aka ‘long long unsigned int’}
> > [-Wformat=]
> > 713 | n = snprintf(p, len, "%-16s%ld(s)\n", "UP_TIME",
> > value/BF3_REF_CLK_IN_HZ);
> > | ~~^
> > ||
> > |long int
> > | %lld
> > rshim_fuse.c: In function ‘rshim_fuse_misc_write’:
> > rshim_fuse.c:954:25: warning: format ‘%lx’ expects argument of type ‘long
> > unsigned int *’, but argument 3 has type ‘uint64_t *’ {aka ‘long long
> > unsigned int *’} [-Wformat=]
> > 954 | if (sscanf(p, " 0x%lx", ) != 1)
> > | ~~^ ~~
> > | | |
> > | | uint64_t * {aka long long unsigned int
> > *}
> > | long unsigned int *
> > | %llx
> > make[3]: *** [Makefile:524: rshim-rshim_fuse.o] Error 1
> >
> >
> > -- System Information:
> > Debian Release: trixie/sid
> > APT prefers unstable-debug
> > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'),
> > (1, 'experimental-debug'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
> > Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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
Processed: affects 1041415
Processing commands for cont...@bugs.debian.org: > affects 1041415 emacs Bug #1041415 [libc6] libc6: fchmodat emulation fails in the absence of /proc Added indication that 1041415 affects emacs > thanks Stopping processing here. Please contact me if you need assistance. -- 1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041415: details
control: tag -1 + fixed-upstream On 2024-04-23 16:22, David Edmondson wrote: > tag 1041415 - upstream > thanks > > Ultimately this fails because /proc is not available in the chroot. > > The version of libc in use *emulates* fchmodat() using /proc/self/fd > rather than using the fchmodat system call. It is emulated, because support for flags != 0 is something new, and requires the fchmodat2 syscall that has been added in Linux kernel version 6.6. On the glibc side, support has been added in glibc 2.39, which is available in git [1], but unfortunately not yet in sid due to binutils/valgrind bug [2] and time_t transition [3] blocking things. Regards Aurelien [1] https://salsa.debian.org/glibc-team/glibc/-/tree/glibc-2.39 [2] https://bugs.debian.org/1057693 [3] https://bugs.debian.org/1059852 -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Processed: Re: Bug#1041415: details
Processing control commands: > tag -1 + fixed-upstream Bug #1041415 [libc6] libc6: fchmodat emulation fails in the absence of /proc Added tag(s) fixed-upstream. -- 1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1069247
Processing commands for cont...@bugs.debian.org: > close 1069247 Bug #1069247 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Bug #1069246 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1069246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069246 1069247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069247: libconfig-model-dpkg-perl: test failures
Processing control commands: > reassign 1069247 apt 2.9.0 Bug #1069247 [src:libconfig-model-dpkg-perl] libconfig-model-dpkg-perl: test failures Bug reassigned from package 'src:libconfig-model-dpkg-perl' to 'apt'. No longer marked as found in versions libconfig-model-dpkg-perl/3.004. Ignoring request to alter fixed versions of bug #1069247 to the same values previously set Bug #1069247 [apt] libconfig-model-dpkg-perl: test failures Marked as found in versions apt/2.9.0. > reassign 1069246 apt 2.9.0 Bug #1069246 [src:dh-make-perl] dh-make-perl: test failure in t/AptContents.t Bug reassigned from package 'src:dh-make-perl' to 'apt'. No longer marked as found in versions dh-make-perl/0.124. Ignoring request to alter fixed versions of bug #1069246 to the same values previously set Bug #1069246 [apt] dh-make-perl: test failure in t/AptContents.t Marked as found in versions apt/2.9.0. > forcemerge 1069247 1069246 Bug #1069247 [apt] libconfig-model-dpkg-perl: test failures Bug #1069247 [apt] libconfig-model-dpkg-perl: test failures Added tag(s) help. Bug #1069246 [apt] dh-make-perl: test failure in t/AptContents.t Merged 1069246 1069247 > retitle 1069247 apt: apt 2.9.0's output breaks libapt-pkg-perl Bug #1069247 [apt] libconfig-model-dpkg-perl: test failures Bug #1069246 [apt] dh-make-perl: test failure in t/AptContents.t Changed Bug title to 'apt: apt 2.9.0's output breaks libapt-pkg-perl' from 'libconfig-model-dpkg-perl: test failures'. Changed Bug title to 'apt: apt 2.9.0's output breaks libapt-pkg-perl' from 'dh-make-perl: test failure in t/AptContents.t'. > affects 1069247 + libapt-pkg-perl libconfig-model-dpkg-perl dh-make-perl Bug #1069247 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Bug #1069246 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Added indication that 1069247 affects libapt-pkg-perl, libconfig-model-dpkg-perl, and dh-make-perl Added indication that 1069246 affects libapt-pkg-perl, libconfig-model-dpkg-perl, and dh-make-perl > tag 1069247 = sid Bug #1069247 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Bug #1069246 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Added tag(s) sid; removed tag(s) help and ftbfs. Added tag(s) sid; removed tag(s) ftbfs and help. > fixed 1069247 2.9.2 Bug #1069247 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Bug #1069246 [apt] apt: apt 2.9.0's output breaks libapt-pkg-perl Marked as fixed in versions apt/2.9.2. Marked as fixed in versions apt/2.9.2. -- 1069246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069246 1069247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069247: libconfig-model-dpkg-perl: test failures
Control: reassign 1069247 apt 2.9.0 Control: reassign 1069246 apt 2.9.0 Control: forcemerge 1069247 1069246 Control: retitle 1069247 apt: apt 2.9.0's output breaks libapt-pkg-perl Control: affects 1069247 + libapt-pkg-perl libconfig-model-dpkg-perl dh-make-perl Control: tag 1069247 = sid Control: fixed 1069247 2.9.2 On Mon, 22 Apr 2024 19:44:38 +0200, Julian Andres Klode wrote: > On Mon, Apr 22, 2024 at 07:41:42PM +0200, Dominique Dumont wrote: > > On Sunday, 21 April 2024 18:07:00 CEST Julian Andres Klode wrote: > > > This should be fixed in apt git already, just needs an upload, > > > which is waiting-ish for some more merges > > Given [1], I need to ask... > > Is this a definitive fix or will this feature come back with apt 3.0 ? … > This should be fixed in apt side on 2.9.2 I just uploaded, but > either way it's a weird thing to break because we change progress > messages for interactive output, maybe run with -q instead or don't > pretend to be a tty. I can confirm that the issues in dh-make-perl's and libconfig-model-dpkg-perl's test suites (via libapt-pkg-perl) are gone with apt 2.9.2. Thanks! (Further change requests should probably go to libapt-pkg-perl, if necessary.) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: Re: Bug#1066788: gyoto: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 check-lorene returned exit code 2
Processing control commands: > tag -1 patch Bug #1066788 [src:gyoto] gyoto: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 check-lorene returned exit code 2 Added tag(s) patch. -- 1066788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066788: gyoto: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 check-lorene returned exit code 2
Control: tag -1 patch On Wed, Mar 13, 2024 at 03:56:54PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[3]: Entering directory '/<>/yorick' > > Makefile:136: warning: overriding recipe for target 'check-dll' > > ../yorick/Makepkg:158: warning: ignoring old recipe for target 'check-dll' > > make[3]: 'check-lorene' is up to date. > > make[3]: Leaving directory '/<>/yorick' > > make[2]: Leaving directory '/<>' > > dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" > > VERBOSE=1 check-lorene returned exit code 2 A more relevant part was: ImportError: /<>/python/gyoto/_std.cpython-311-x86_64-linux-gnu.so: undefined symbol: _ZN5Gyoto7AstrobjlsERSoRKNS0_14PolishDoughnutE I sent a patch for this upstream as https://github.com/gyoto/Gyoto/pull/17. Here's a patch to fix the Debian package in the meantime. -- Colin Watson (he/him) [cjwat...@debian.org] >From 19e6f4bcdc33cbd7995027bf56ec3b5a7125ea5f Mon Sep 17 00:00:00 2001 From: Colin Watson Date: Wed, 24 Apr 2024 15:25:19 +0100 Subject: [PATCH] Remove undefined operator<< declaration for PolishDoughnut Closes: #1066788 --- debian/changelog | 7 ++ .../patches/remove-polish-doughnut-operator | 25 +++ debian/patches/series | 1 + 3 files changed, 33 insertions(+) create mode 100644 debian/patches/remove-polish-doughnut-operator diff --git a/debian/changelog b/debian/changelog index 8f74908..0188483 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +gyoto (2.0.2-1.2) UNRELEASED; urgency=medium + + * Remove undefined operator<< declaration for PolishDoughnut (closes: +#1066788). + + -- Colin Watson Wed, 24 Apr 2024 14:32:29 +0100 + gyoto (2.0.2-1.1) unstable; urgency=medium * Non-maintainer upload. diff --git a/debian/patches/remove-polish-doughnut-operator b/debian/patches/remove-polish-doughnut-operator new file mode 100644 index 000..ead15f5 --- /dev/null +++ b/debian/patches/remove-polish-doughnut-operator @@ -0,0 +1,25 @@ +Description: Remove undefined operator<< declaration for PolishDoughnut + On current Debian systems this resulted in `undefined symbol: + _ZN5Gyoto7AstrobjlsERSoRKNS0_14PolishDoughnutE` while running tests. +Bug-Debian: https://bugs.debian.org/1066788 +Forwarded: https://github.com/gyoto/Gyoto/pull/17 +Last-Update: 2024-04-24 + +Index: b/include/GyotoPolishDoughnut.h +=== +--- a/include/GyotoPolishDoughnut.h b/include/GyotoPolishDoughnut.h +@@ -262,13 +262,6 @@ + // Outputs + // --- + public: +- +- /// Display +- friend std::ostream& operator<<(std::ostream& , const PolishDoughnut& ) ; +- +- public: +- +- + }; + + #endif diff --git a/debian/patches/series b/debian/patches/series index b9e8f3b..b8e9081 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,3 +1,4 @@ interpreter-path +remove-polish-doughnut-operator # This patch is conditionally applied by debian/rules: # no-fp-ilogb0 -- 2.43.0
Bug#1055847: Please check python-sparse issue at Github
Hi Diane and Ghislain, you are listed as Uploaders of python-sparse. Since I now have other tasks than maintaining team maintained packages I would be really happy if you could subscribe upstream issue https://github.com/pydata/sparse/issues/628 and continue what I have started. Thanks a lot Andreas. -- https://fam-tille.de
Processed: severity 1068420
Processing commands for cont...@bugs.debian.org:
> severity 1068420 normal
Bug #1068420 {Done: Luca Boccassi } [pidgin-gnome-keyring]
pidgin-gnome-keyring - still depends on old libpurple after binnmu
Severity set to 'normal' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1068420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069520: sbcl: FTBFS on armhf: make[1]: *** [debian/rules:53: override_dh_auto_build] Error 1
Hi, Tested this and it’s due to the 64t transition. The grovelled data changed: (sid_armhf-dchroot)pvaneynd@abel:~/sbcl-2.3.7$ diff -u ./crossbuild-runner/backends/arm/stuff-groveled-from-headers.lisp output/stuff-groveled-from-headers.lisp --- ./crossbuild-runner/backends/arm/stuff-groveled-from-headers.lisp 2023-07-29 07:59:39.0 + +++ output/stuff-groveled-from-headers.lisp 2023-07-29 07:59:39.0 + @@ -30,7 +30,7 @@ (define-alien-type off-t (signed 64)) (define-alien-type size-t (unsigned 32)) (define-alien-type ssize-t (signed 32)) -(define-alien-type time-t (signed 32)) +(define-alien-type time-t (signed 64)) (define-alien-type suseconds-t (signed 32)) (define-alien-type uid-t (unsigned 32)) ;; Types in src/runtime/wrap.h. See that file for explantion. @@ -141,6 +141,7 @@ (defconstant clock-process-cputime-id 2) ; #x2 (defconstant clock-realtime-alarm 8) ; #x8 (defconstant clock-realtime-coarse 5) ; #x5 +(defconstant clock-tai 11) ; #xb (defconstant clock-monotonic-coarse 6) ; #x6 (defconstant clock-monotonic-raw 4) ; #x4 (defconstant clock-boottime 7) ; #x7 @@ -149,11 +150,11 @@ ;;; structures (define-alien-type nil (struct timeval - (tv-sec (signed 32)) - (tv-usec (signed 32 + (tv-sec (signed 64)) + (tv-usec (signed 64 (define-alien-type nil (struct timespec - (tv-sec (signed 32)) + (tv-sec (signed 64)) (tv-nsec (signed 32 I honestly don’t understand how to use 64-bit values on this arch, so I created https://bugs.launchpad.net/sbcl/+bug/2063340 Best regards, Peter
Bug#1069762: marked as done (pdns-recursor: CVE-2024-25583)
Your message dated Wed, 24 Apr 2024 13:19:36 + with message-id and subject line Bug#1069762: fixed in pdns-recursor 4.9.5-1 has caused the Debian Bug report #1069762, regarding pdns-recursor: CVE-2024-25583 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.) -- 1069762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdns-recursor X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for pdns-recursor. CVE-2024-25583[0]: PowerDNS Security Advisory 2024-02: if recursive forwarding is configured, crafted responses can lead to a denial of service in Recursor https://www.openwall.com/lists/oss-security/2024/04/24/1 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-25583 https://www.cve.org/CVERecord?id=CVE-2024-25583 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: pdns-recursor Source-Version: 4.9.5-1 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of pdns-recursor, 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. Chris Hofstaedtler (supplier of updated pdns-recursor 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: Wed, 24 Apr 2024 14:19:26 +0200 Source: pdns-recursor Architecture: source Version: 4.9.5-1 Distribution: unstable Urgency: medium Maintainer: pdns-recursor packagers Changed-By: Chris Hofstaedtler Closes: 1069762 Changes: pdns-recursor (4.9.5-1) unstable; urgency=medium . * New upstream version 4.9.5, including fix for CVE-2024-25583 (Closes: #1069762) Checksums-Sha1: 1324089baae0d3ad5dcc1331d3f8c5cff8c9ecd5 2871 pdns-recursor_4.9.5-1.dsc da8bc013ee0fef9e4e18a2e023c26cc10648d574 1556147 pdns-recursor_4.9.5.orig.tar.bz2 04271a59919ac5f9084a73384beae7b8e3eced0d 488 pdns-recursor_4.9.5.orig.tar.bz2.asc d33467707919ef469741a7aa4e47de8784277cb9 23728 pdns-recursor_4.9.5-1.debian.tar.xz e11dae70c571471e9b7f8034b161926a2d7d6980 9647 pdns-recursor_4.9.5-1_arm64.buildinfo Checksums-Sha256: 284ce1b6af758bee617a38a3e893c357d0c82e3a2a15f17d6fdad49fcaf17a70 2871 pdns-recursor_4.9.5-1.dsc 1d062be88c70c27200821c1c6154ee68e4efec395eff588ee1e73c4e81e4f51e 1556147 pdns-recursor_4.9.5.orig.tar.bz2 dfd0d2e16b9a304da858c6dd01abf465fb759ddd83db4e0dcad53a2a4fa13087 488 pdns-recursor_4.9.5.orig.tar.bz2.asc df65b867c04cc6b91736705a2cb64d6d85e58bd63c000f744963c5cad4248a86 23728 pdns-recursor_4.9.5-1.debian.tar.xz 067255269eb32eada41904154c2fe995bd559f97747f9d8e44086c2d27e7 9647 pdns-recursor_4.9.5-1_arm64.buildinfo Files: f122f2cfe183c33ed4e3bde8aaa59472 2871 net optional pdns-recursor_4.9.5-1.dsc ffb6a13c94a32f21780df601d56bd970 1556147 net optional pdns-recursor_4.9.5.orig.tar.bz2 9e4360c9a06d4744b164867ce7be67c1 488 net optional pdns-recursor_4.9.5.orig.tar.bz2.asc af3414311b44df3acd1b5ea494a6be07 23728 net optional pdns-recursor_4.9.5-1.debian.tar.xz f4b94c5a60e93003dfda463889a96523 9647 net optional pdns-recursor_4.9.5-1_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmYpA78ACgkQXBPW25MF LgNySxAAnEkSmj5PY4FswwPFioesg8Qk6AUXKIddWh375WFy9ef0fYxm6C3a094I ty5pMMsmWXnHGxR5L+ctOnS8RO5ZDtD3FPyYvs2SDDdMG0yAwoP8mc3uJUuja9/J LoeFdWpvtc9do0gstB4X+TiI62iuQol4iqu3DcPf8n+UEfsICIijnV+5rQ3jgt+q WTJvBjNWckFr7k+5R3lQPVc42kMv/gqrdNOT0MPponsiRWVFGC3vPUddzO1yz7BH yu9GWoljB3vG+N1o2v187xhjdmBZLYWVzl8K79rkyjtktwNXcsn/CQ3ND1XE26Ym K0POiF5ihL2+wdNu0t45C9Y9hiY0vvewMSHZDzXVAvuCZ5f/WV1lT89KGKLobg1a 9Ww2IWNy88n/8BOFEA44vDtwot1PzzC0Gm09XRbcMiIQHcJnbE2DLzS4uQxC0Oa8 Gl8M6lHLUC2yiCTwosRftRuX94L9PsTOnW+yVFTsQ29SjN6Vi2Yi/ugAN4WnsbFu 8/sKxet3g0dDrxymLan3M+8oQcTmHBV5rac8tfK4bRHFGLgw3uwV9kx9ZD3QGt/o mKselbvZgoi8DsYUTv+txADo64nP5nto1ZXpP4CJ0rAOJcdDSqMZePigLzGVQ57o
Processed: Re: Bug#1058888: pyferret FTBSF on several architectures: dh_install: error: missing files, aborting
Processing control commands: > retitle -1 pyferret FTBFS on several architectures: dh_install: error: > missing files, aborting Bug #105 [src:pyferret] pyferret FTBSF on several architectures: dh_install: error: missing files, aborting Changed Bug title to 'pyferret FTBFS on several architectures: dh_install: error: missing files, aborting' from 'pyferret FTBSF on several architectures: dh_install: error: missing files, aborting'. > tag -1 patch Bug #105 [src:pyferret] pyferret FTBFS on several architectures: dh_install: error: missing files, aborting Added tag(s) patch. -- 105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058888: pyferret FTBSF on several architectures: dh_install: error: missing files, aborting
Control: retitle -1 pyferret FTBFS on several architectures: dh_install: error: missing files, aborting Control: tag -1 patch On Sun, Dec 17, 2023 at 08:24:07PM +0200, Adrian Bunk wrote: > https://buildd.debian.org/status/logs.php?pkg=pyferret=7.6.5-5 > > ... >dh_install -a > dh_install: warning: Cannot find (any matches for) > "debian/tmp/ext_func/pylibs" (tried in ., debian/tmp) > > dh_install: warning: python3-ferret missing files: debian/tmp/ext_func/pylibs > install -m0755 -d debian/python3-ferret//usr/bin > cp --reflink=auto -a ./debian/pyferret3 debian/python3-ferret//usr/bin/ > install -m0755 -d debian/python3-ferret//usr/lib/python3/dist-packages > cp --reflink=auto -a > ./debian/tmp/lib/python3.11/libpyferret.cpython-311-powerpc64le-linux-gnu.so > ./debian/tmp/lib/python3.12/libpyferret.cpython-312-powerpc64le-linux-gnu.so > ./install/local/lib/python3.11/dist-packages/__pycache__ > ./install/local/lib/python3.11/dist-packages/gcircle-7.65-py3.11.egg-info > ./install/local/lib/python3.11/dist-packages/gcircle.py > ./install/local/lib/python3.11/dist-packages/pipedviewer > ./install/local/lib/python3.11/dist-packages/pipedviewer-7.65-py3.11.egg-info > ./install/local/lib/python3.11/dist-packages/pyferret > ./install/local/lib/python3.11/dist-packages/pyferret-7.65-py3.11.egg-info > debian/python3-ferret//usr/lib/python3/dist-packages/ > install -m0755 -d > debian/python3-ferret//usr/share/bash-completion/completions/ > cp --reflink=auto -a ./debian/bash_completion.d/pyferret3 > debian/python3-ferret//usr/share/bash-completion/completions// > dh_install: error: missing files, aborting > make: *** [debian/rules:8: binary-arch] Error 25 I've proposed https://salsa.debian.org/science-team/pyferret/-/merge_requests/3 to fix this. -- Colin Watson (he/him) [cjwat...@debian.org]
Processed: found 1069762 in pdns-recursor/4.9.4-1, notfound 1069762 in pdns-recursor/4.9.3-1 ...
Processing commands for cont...@bugs.debian.org: > found 1069762 pdns-recursor/4.9.4-1 Bug #1069762 [src:pdns-recursor] pdns-recursor: CVE-2024-25583 Marked as found in versions pdns-recursor/4.9.4-1. > notfound 1069762 pdns-recursor/4.9.3-1 Bug #1069762 [src:pdns-recursor] pdns-recursor: CVE-2024-25583 Ignoring request to alter found versions of bug #1069762 to the same values previously set > found 1069762 pdns-recursor/4.8.7-1 Bug #1069762 [src:pdns-recursor] pdns-recursor: CVE-2024-25583 Marked as found in versions pdns-recursor/4.8.7-1. > notfound 1069762 pdns-recursor/4.8.4-1 Bug #1069762 [src:pdns-recursor] pdns-recursor: CVE-2024-25583 Ignoring request to alter found versions of bug #1069762 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069524: marked as done (rl-renderpm: FTBFS on armhf: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Wed, 24 Apr 2024 12:06:53 + with message-id and subject line Bug#1069524: fixed in rl-renderpm 4.0.3+repack-1 has caused the Debian Bug report #1069524, regarding rl-renderpm: FTBFS on armhf: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rl-renderpm Version: 4.0.3-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[1]: Entering directory '/<>' > rm -f src/libart_lgpl/art_config.h # this file is generated > dh_auto_clean > I: pybuild base:311: python3.12 setup.py clean > === > Attempting build of _renderPM > extension from '/<>/src' > === > will use package libart 2.3.12 > installing with freetype version 2.13.2 > FT_LIB_DIR=[] FT_INC_DIR=['/usr/include', '/usr/include/freetype2'] > running clean > removing '/<>/.pybuild/cpython3_3.12_rl-renderpm/build' (and > everything under it) > 'build/bdist.linux-armv7l' does not exist -- can't clean it > 'build/scripts-3.12' does not exist -- can't clean it > I: pybuild base:311: python3.11 setup.py clean > === > Attempting build of _renderPM > extension from '/<>/src' > === > will use package libart 2.3.12 > installing with freetype version 2.13.2 > FT_LIB_DIR=[] FT_INC_DIR=['/usr/include', '/usr/include/freetype2'] > running clean > removing '/<>/.pybuild/cpython3_3.11_rl-renderpm/build' (and > everything under it) > 'build/bdist.linux-armv7l' does not exist -- can't clean it > 'build/scripts-3.11' does not exist -- can't clean it > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using options from > rl-renderpm-4.0.3/debian/source/options: > --extend-diff-ignore=^[^/]*[.]egg-info/ > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building rl-renderpm using existing > ./rl-renderpm_4.0.3.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > rl-renderpm-4.0.3/src/libart_lgpl/art_config.h > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/rl-renderpm_4.0.3-2.diff.sGNO_O > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2024-04-20T02:35:17Z The full build log is available from: http://qa-logs.debian.net/2024/04/20/rl-renderpm_4.0.3-2_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rl-renderpm Source-Version: 4.0.3+repack-1 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of rl-renderpm, 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. Georges Khaznadar (supplier of updated rl-renderpm package) (This message was generated
Processed: closing 1069348
Processing commands for cont...@bugs.debian.org: > close 1069348 0.16.0-2 Bug #1069348 [src:ruby-ethon] ruby-ethon: FTBFS Marked as fixed in versions ruby-ethon/0.16.0-2. Bug #1069348 [src:ruby-ethon] ruby-ethon: FTBFS Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1069348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069348: closing 1069348
close 1069348 0.16.0-2 thanks
Bug#1069763: matrix-synapse: CVE-2024-31208
Source: matrix-synapse X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for matrix-synapse. CVE-2024-31208[0]: | Synapse is an open-source Matrix homeserver. A remote Matrix user | with malicious intent, sharing a room with Synapse instances before | 1.105.1, can dispatch specially crafted events to exploit a weakness | in the V2 state resolution algorithm. This can induce high CPU | consumption and accumulate excessive data in the database of such | instances, resulting in a denial of service. Servers in private | federations, or those that do not federate, are not affected. Server | administrators should upgrade to 1.105.1 or later. Some workarounds | are available. One can ban the malicious users or ACL block servers | from the rooms and/or leave the room and purge the room using the | admin API. https://github.com/element-hq/synapse/security/advisories/GHSA-3h7q-rfh9-xm4v https://github.com/element-hq/synapse/commit/55b0aa847a61774b6a3acdc4b177a20dc019f01a (v1.105.1) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-31208 https://www.cve.org/CVERecord?id=CVE-2024-31208 Please adjust the affected versions in the BTS as needed.
Bug#1069762: pdns-recursor: CVE-2024-25583
Source: pdns-recursor X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for pdns-recursor. CVE-2024-25583[0]: PowerDNS Security Advisory 2024-02: if recursive forwarding is configured, crafted responses can lead to a denial of service in Recursor https://www.openwall.com/lists/oss-security/2024/04/24/1 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-25583 https://www.cve.org/CVERecord?id=CVE-2024-25583 Please adjust the affected versions in the BTS as needed.
Processed: reassign emacs bug to libc
Processing commands for cont...@bugs.debian.org: > reassign 1041415 libc6 Bug #1041415 [emacs] emacs: fails to install: post-installation script subprocess returned error exit status 1 Bug reassigned from package 'emacs' to 'libc6'. No longer marked as found in versions emacs/1:28.2+1-15. Ignoring request to alter fixed versions of bug #1041415 to the same values previously set > retitle 1041415 libc6: fchmodat emulation fails in the absence of /proc Bug #1041415 [libc6] emacs: fails to install: post-installation script subprocess returned error exit status 1 Changed Bug title to 'libc6: fchmodat emulation fails in the absence of /proc' from 'emacs: fails to install: post-installation script subprocess returned error exit status 1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068189: marked as done (debhelper: --link-doc checking for known packages makes linux-signed build FTBFS)
Your message dated Wed, 24 Apr 2024 11:00:10 +
with message-id
and subject line Bug#1068189: fixed in linux 6.7.12-1
has caused the Debian Bug report #1068189,
regarding debhelper: --link-doc checking for known packages makes linux-signed
build FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1068189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debhelper
Version: 13.15
Severity: serious
Tags: ftbfs
Justification: Regression for other package builds, FTBFS
X-Debbugs-Cc: car...@debian.org,debian-ker...@lists.debian.org
Control: affects -1 + src:linux,src:linux-signed-amd64,src:linux-signed-arm64
Hi Niels,
Not fully investigated, but starting to fill a bugreport. I noticed
that the src:linux pipeline on salsa started to fail for the
jobs in th build-signed stage (in the build-signed job).
https://salsa.debian.org/carnil/linux/-/jobs/5527774
(and for saving the output):
dh_installdocs --link-doc=linux-headers-6.7+unreleased-cloud-amd64
dh_installdocs: error: Requested unknown package
linux-headers-6.7+unreleased-cloud-amd64 via --link-doc, expected one of:
linux-image-6.7+unreleased-amd64 linux-image-amd64 linux-headers-amd64
linux-image-6.7+unreleased-cloud-amd64 linux-image-cloud-amd64
linux-headers-cloud-amd64 linux-image-6.7+unreleased-rt-amd64
linux-image-rt-amd64 linux-headers-rt-amd64
make[2]: *** [debian/rules.real:81: binary_meta] Error 25
make[1]: *** [debian/rules.gen:21: binary-arch_amd64_none_cloud-amd64_meta]
Error 2
make: *** [debian/rules:19: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
(attached as well the raw log)
I'm not 100% sure yet, this might be a problem in our packaging in
which case we can re-eassign. But it only got triggered with the
change recently in debhelper:
https://salsa.debian.org/debian/debhelper/-/commit/dec5cfad00e2abd9ee3594f90c93f3fa42bb73ff
Regards,
Salvatore
5527774.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.7.12-1
Done: Salvatore Bonaccorso
We believe that the bug you reported is fixed in the latest version of
linux, 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.
Salvatore Bonaccorso (supplier of updated linux 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: Wed, 24 Apr 2024 09:42:56 +0200
Source: linux
Architecture: source
Version: 6.7.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 1068189
Changes:
linux (6.7.12-1) unstable; urgency=medium
.
* New upstream stable update:
https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.10
- [arm64] dmaengine: fsl-edma: utilize common dt-binding header file
- [arm64] dmaengine: fsl-edma: correct max_segment_size setting
- xfrm: Clear low order bits of ->flowi4_tos in decode_session4().
- xfrm: Pass UDP encapsulation in TX packet offload
- net: lan78xx: fix runtime PM count underflow on link stop
- ixgbe: {dis, en}able irqs in ixgbe_txrx_ring_{dis, en}able
- i40e: disable NAPI right after disabling irqs when handling xsk_pool
- ice: reorder disabling IRQ and NAPI in ice_qp_dis
- ice: replace ice_vf_recreate_vsi() with ice_vf_reconfig_vsi()
- ice: reconfig host after changing MSI-X on VF
- Revert "net/mlx5: Block entering switchdev mode with ns inconsistency"
- Revert "net/mlx5e: Check the number of elements before walk TC
rhashtable"
- net/mlx5: E-switch, Change flow rule destination checking
- net/mlx5: Fix fw reporter diagnose output
- net/mlx5: Check capability for fw_reset
- net/mlx5e: Change the warning when ignore_flow_level is not supported
- net/mlx5e: Fix MACsec state loss upon state update in offload path
- net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission
tracking
occurs after populating the metadata_map
- net/mlx5e: Switch to
Processed: Re: Re: spotlighter: FTBFS: spotlighter.c:105:3: error: implicit declaration of function ‘on_window_screen_changed’ [-Werror=implicit-function-declaration]
Processing control commands: > tags -1 pending Bug #1066355 [src:spotlighter] spotlighter: FTBFS: spotlighter.c:105:3: error: implicit declaration of function ‘on_window_screen_changed’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066355: Re: spotlighter: FTBFS: spotlighter.c:105:3: error: implicit declaration of function ‘on_window_screen_changed’ [-Werror=implicit-function-declaration]
Control: tags -1 pending On Mon, 15 Apr 2024 13:47:04 +1200 Vladimir Petko wrote: > Dear Maintainer, > > Would it be possible to consider the attached patch as the solution for the > issue? > > In Ubuntu, the attached patch was applied to achieve the following: > > * d/p/2_ftbfs_implicit_declaration.patch: declare callback to > resolve -Werror=implicit-function-declaration ftbfs (LP: #2061331). > > > Thanks for considering the patch. > Thank you very much for the patch! I intend to 0-day nmu this later today to help with the time_t transition, debdiff attached. best /Andreas Rönnquist gus...@debian.org spotlighter_nmu.debdiff Description: Binary data pgpmGUPSSukH6.pgp Description: OpenPGP digital signatur
Bug#1065934: marked as done (hashcat: contains non-free unrar)
Your message dated Wed, 24 Apr 2024 10:36:57 + with message-id and subject line Bug#1065934: fixed in hashcat 6.2.6+ds2-1 has caused the Debian Bug report #1065934, regarding hashcat: contains non-free unrar 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.) -- 1065934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hashcat Version: 6.2.5+ds1-1 Severity: serious Your Source package contains the non-free unrar sources. I Gruss it ist also included in a binary pkg but I habe not verified that. --- End Message --- --- Begin Message --- Source: hashcat Source-Version: 6.2.6+ds2-1 Done: Sophie Brun We believe that the bug you reported is fixed in the latest version of hashcat, 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. Sophie Brun (supplier of updated hashcat 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: Wed, 24 Apr 2024 12:01:32 +0200 Source: hashcat Architecture: source Version: 6.2.6+ds2-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Sophie Brun Closes: 1065934 Changes: hashcat (6.2.6+ds2-1) unstable; urgency=medium . * Team Upload. . [ Debian Janitor ] * Remove constraints unnecessary since buster (oldstable) * Apply multi-arch hints. + hashcat-data: Add :any qualifier for python3 dependency. . [ Sophie Brun ] * Remove non-free code (Closes: #1065934) and disable build with unrar * New upstream version 6.2.6+ds2 * Add missing copyright for deps/* Checksums-Sha1: 0375c96f78f99452290bafd768468efedac9f3e1 2160 hashcat_6.2.6+ds2-1.dsc c3e038b7501894f0cdc011f2536d11ca91619c7a 9643512 hashcat_6.2.6+ds2.orig.tar.xz 26803c26b1c57d5fe853d136708af0a0feef35de 14720 hashcat_6.2.6+ds2-1.debian.tar.xz 76e67fd0f7bd48ba8daff4ae640210c981c1dff3 7643 hashcat_6.2.6+ds2-1_source.buildinfo Checksums-Sha256: 6e5f753ee56d74d24999e68747e3b756aa29be6556af85a37507672c7151a06d 2160 hashcat_6.2.6+ds2-1.dsc 5247a3a723794ff07f60fc540160849b6ea87ec003d681239b732d1c20cda16a 9643512 hashcat_6.2.6+ds2.orig.tar.xz 9c25895fd3e5e046f9409f03402484899152db075ac3b9e2aa2783b00f357751 14720 hashcat_6.2.6+ds2-1.debian.tar.xz 7064b6205adfd7a66a02b9a1c7ac5a57e5b22ac590e4fbfb4a8f9610bcd768bc 7643 hashcat_6.2.6+ds2-1_source.buildinfo Files: 267846e099bf9d5c5b17e561ceaa17e1 2160 net optional hashcat_6.2.6+ds2-1.dsc ef780bb4320f91fb1408e2feaa42799f 9643512 net optional hashcat_6.2.6+ds2.orig.tar.xz 693de301d848a5eeb738998c5cca65b5 14720 net optional hashcat_6.2.6+ds2-1.debian.tar.xz 60d9050516c677caeca1ddf96e92c631 7643 net optional hashcat_6.2.6+ds2-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Sophie Brun iQIzBAEBCgAdFiEEOyG45orlwW+H9TItV5J4OyBv7jAFAmYo2U0ACgkQV5J4OyBv 7jDW0A//QpkpsCFoU7W6j4l5OX9qMRnSwb/+2CpwbPEEXwbUY+k1VsBV6E5AGevj HcIbOVrYuEjbIQRjqDlV207aZ8WX9MEyTom6DoVndCB4eIUnnZ8nRkzSQQrQZJWK VmLaIP0o8wlFAGE3n9eFytQAfRoYdxRMPZ9iVcMD7y/lxwkj90U3LCjbD2ySBPEk xikyNGwlwAeZKmxiLD1IKIo9IUMkckbg9Gb0BCPVMQADpp8CTQJKUAdOAeCiDWtb qq1pxrN/1KFL8MvEw+4AfDY9f7lek83XEeo8TunDHQgjgxpBHgUAOYyxK4jinSJ1 Wbws0KAuq7gmWNpUQK0R/ynDqaXGVyLW60v8MDeduxhz8cbdfgZrnknb1vKnTndN tKxMA/eJX4FNiTCqaHouS7WguZ8laQ/W3mJumrmxmRVAnxcai531TLXAQK2D2RHl UJWcVViFr347knOhJiZPu0fnE2EjMIvKVpvwdTZCQ06GsnXPsdFfujoFGP2ax3Mi sA0lWKY/ABMpCop+s1WMoTa+sRZ1u5D7sv4IBO6pR4ApOuu6Syx9mFwHexn1Ifa9 prmxpXWdr0bhFpQMS9Lx5RlqLELtXo1fqg8mTr3iFDlXa4WvlYOHFeuWgr66o0oK uqWwhoZb9hYer8CzGPDgGLmIJ49Wegc/Lxfzhl/61+o/+0niU+w= =yGeu -END PGP SIGNATURE- pgpVIP9_3b6iF.pgp Description: PGP signature --- End Message ---
Bug#1067139: marked as done (matplotlib: missing depend on python3-all for autopkgtest)
Your message dated Wed, 24 Apr 2024 10:20:40 + with message-id and subject line Bug#1067139: fixed in matplotlib 3.6.3-2 has caused the Debian Bug report #1067139, regarding matplotlib: missing depend on python3-all for autopkgtest 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.) -- 1067139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: matplotlib Version: 3.6.3-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package has an autopkgtest regression due to changes in NumPy. The python3-numpy package no longer depends on all supported Python versions. You need to depend on python3-all if you want to run your tests against all supported Python releases. Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmX5ZB4ACgkQ+C8H+466 LVlCRgv/dZZtG62N0OQPyMHnR7lIi8RhSqcGrYswTt1KXEsG203iutNYsWKTsE28 VZPllUoH22bdXZIGVWDs+HcjlY++TIuGBPw3zT95A7hSRzRrXMC9QhHKy1QWTLk9 gHddmCoFPQho4zBhxcdaCfpi2O3d0+lmTrYOtAya6LvlEd2lZzyGxRH3JMD94tzW uyVI+YqTFQHoAfSiCQPVlVZHlSTYN5Xm8krEP/QfzuMt7T05lmW6doRAW0UY6Sk7 x8ss/bHcRPzkYU4JJc9+p5xqbnSEp6f3l/KPawc7ieorGuDy61L/I9Cq9Pz5SOCG jYqqiBk0KaO3dfIAMbV71m89VLxZePCqmlKbsYmbaGk9Gy5Swss0QJPfaUx+QRix 6CjPJJGt22WtMbJfzfrNUqENpJmHNdeJ6H/s8iucbhJXCTnIUHjsFrZpgnwYRVZB NP3FG597GI7+DrwXXQGJelqpKRVtqn1THRuBQxQ45zpfg3amESJRJyUsXl+GYHfa +cJn+pfP =Bf9+ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: matplotlib Source-Version: 3.6.3-2 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of matplotlib, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated matplotlib 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: Wed, 24 Apr 2024 11:57:19 +0200 Source: matplotlib Architecture: source Version: 3.6.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team , Changed-By: Timo Röhling Closes: 1067139 Changes: matplotlib (3.6.3-2) unstable; urgency=medium . * Team upload. * Add missing autopkgtest depend on python3-all (Closes: #1067139) Checksums-Sha1: 59f31fea468b2af136e485ecd7c92ae953f233c6 3302 matplotlib_3.6.3-2.dsc 3a7b78acdf16885d7a9d5fa967f215aa47a430c5 33464 matplotlib_3.6.3-2.debian.tar.xz 0e450bb6cea02732b64ddd0303d645b5da6ed109 24079 matplotlib_3.6.3-2_amd64.buildinfo Checksums-Sha256: 3ab4b450c2c88b61edd986aaef745710e85511ae237a3f205764923722bc411d 3302 matplotlib_3.6.3-2.dsc c71113cbaf52a2fa8dad4f601ab189a2842386771e02c92735dea427511ab92c 33464 matplotlib_3.6.3-2.debian.tar.xz f821fdcc823f7bf109638942663e00734bb9e5408544dd2c75aa6a611387c067 24079 matplotlib_3.6.3-2_amd64.buildinfo Files: 2d43c8fb353c725f7105f9ad9f4aa785 3302 python optional matplotlib_3.6.3-2.dsc 6c9b3d79049836e8163835b6da3667fc 33464 python optional matplotlib_3.6.3-2.debian.tar.xz 894fedb76e39fd622b3236b60ae1633d 24079 python optional matplotlib_3.6.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmYo2msUHHJvZWhsaW5n QGRlYmlhbi5vcmcACgkQzIxr3RQD9MpVsA//QIcqXPjEQp6gR2kKZ+Gp+XGtUKDk 02OSkABEfC3TwpJ+Qj/bmXJ8rZ4IclHS2jGDHcccAxQR9kSyPCSW1Sbolkv+Cy5x AasUF2LupIn7iiDlHGEr+U1VxVOiAmAo3PwxAsvHKdhKYvT7rgUc/zKy98XrMO3E z/h10DQHF+slEV9SoBeii0ZwdBnM/TacmQLFCE1rt8RpDf3jddXnfbByHIfqKEDm GtN67AUb/eVtvg2z7jzcUnCj9J6P3tryE+ZfrSrWd3GBwdFkphM8PsMZfUGkuVdC cpzDoIdmgMYxAumm3Su2SFxn3ZWzqYJX7HePLmjn2Jyq1EzkZY5r5xI3Ttz0u/eh eyV9dWAGg0fzyUdcF/ZqbwZv/0rK+68UGPi24TKec0D+Ph1Gu9QMGnqFlFM+xp1y u/uPa5U/zi7+BzhRnqQ7zQDKGHDOdvS7W7fHkypPTj49xcOTIiRb9IsN+IwanFMj Z5xhZhR22W+YDgKbOfVBAocqLgYGoMeD929aJ0zkY6puUgSn2IVvwAwct5q7pp5g be1f2tiF4S9rQqmVidWA+e7UDv2rSjQUtPP9cgYHHo1gpRYBXX5cGCP3sGPe3XbU OlPlpERy3CIn5D+wJ+zhMGxUF8AdmxMtFTQ+j9dq0nHZNrk8gbo1h5hQrWKgpIYo sba0i74eakVSbOE= =bsjs -END PGP SIGNATURE- pgpRKmXvzKBt7.pgp Description: PGP signature --- End Message ---
Bug#1067139: marked as pending in matplotlib
Control: tag -1 pending Hello, Bug #1067139 in matplotlib 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/python-team/packages/matplotlib/-/commit/849803aa62550b234e2c3b590fceca5fb573f4cc Add missing autopkgtest depend on python3-all Closes: #1067139 (this message was generated automatically) -- Greetings https://bugs.debian.org/1067139
Processed: Bug#1067139 marked as pending in matplotlib
Processing control commands: > tag -1 pending Bug #1067139 [src:matplotlib] matplotlib: missing depend on python3-all for autopkgtest Added tag(s) pending. -- 1067139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1065934 marked as pending in hashcat
Processing control commands: > tag -1 pending Bug #1065934 [src:hashcat] hashcat: contains non-free unrar Added tag(s) pending. -- 1065934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065934: marked as pending in hashcat
Control: tag -1 pending Hello, Bug #1065934 in hashcat 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/pkg-security-team/hashcat/-/commit/faabd9db60b2372ce7974a9e40af424d94942084 Remove non-free code (Closes: #1065934) and disable build with unrar (this message was generated automatically) -- Greetings https://bugs.debian.org/1065934
Bug#1068502: Dead upstream and broken, remove or switch to a fork?
Hi, I have uploaded a patch that fixes the FTBFS bug with flake8 >= 7, so we have a bit of breathing room for now. The pytest-flake8 fork has been archived already; the author states [1]: I am no longer invested into the flake8 as a tool, as I have moved to using ruff. And I strongly recommend running QC tools as a separate step. Integrating flake8 into the unittest framework looks like a false economy to me nowdays. I tend to agree and think we should work towards removing this package. There are only five reverse dependencies anyway: $ build-rdeps python3-pytest-flake8 Reverse Build-depends in unstable/main: --- cvise pytest-pylint python-cssselect2 python-tinycss2 rpmlint Found a total of 5 reverse build-depend(s) for python3-pytest-flake8. Cheers Timo [1] https://github.com/VRGhost/pytest-flake8 -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1069352: marked as done (r-cran-seuratobject: FTBFS on arm64: dpkg-gencontrol: error: parsing package 'r-cran-seuratobject' Depends field: r-api-4.0, r-base-core (>= ii r-base-core 4.3.3-3+b1
Your message dated Wed, 24 Apr 2024 09:21:13 +
with message-id
and subject line Bug#1069352: fixed in r-cran-seuratobject 5.0.1-2
has caused the Debian Bug report #1069352,
regarding r-cran-seuratobject: FTBFS on arm64: dpkg-gencontrol: error: parsing
package 'r-cran-seuratobject' Depends field: r-api-4.0, r-base-core (>= ii
r-base-core4.3.3-3+b1 arm64GNU R core of statistical computation
and graphics system) , , r-cran-sp (>= 1.5.0), r-cran-future,
r-cran-future.apply, r-cran-matrix (>= 1.6-5-1), r-cran-progressr, r-cran-rcpp
(>= 1.0.5), r-cran-rlang (>= 0.4.7), r-cran-spam, r-cran-lifecycle,
r-cran-generics, r-cran-rcpp, r-cran-rcppeigen,
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.)
--
1069352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-seuratobject
Version: 5.0.1-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[1]: Entering directory '/<>'
> rmbversion=`dpkg -l r-cran-matrix | grep 'ii' | sed
> 's/^.*r-cran-matrix[[:space:]]\+\([0-9.-]\+\)[[:space:]]\+.*/\1/'`; \
> sed -i "s/r-cran-matrix[^,]*/r-cran-matrix (>= ${rmbversion})/"
> debian/*substvars
> rversion=`dpkg -l r-base-core | grep 'ii' | sed
> 's/^.*r-base-core[[:space:]]\+\([0-9.-]\+\)-[0-9]\+[[:space:]]\+.*/\1/'`; \
> sed -i "s/\(r-api-[0-9.]\+\),/& r-base-core (>= ${rversion})/"
> debian/*substvars
> dh_gencontrol
> dpkg-gencontrol: warning: can't parse dependency r-base-core (>= ii
> r-base-core4.3.3-3+b1 arm64GNU R core of statistical
> computation and graphics system)
> dpkg-gencontrol: error: parsing package 'r-cran-seuratobject' Depends field:
> r-api-4.0, r-base-core (>= ii r-base-core4.3.3-3+b1 arm64GNU R
> core of statistical computation and graphics system) , , r-cran-sp (>=
> 1.5.0), r-cran-future, r-cran-future.apply, r-cran-matrix (>= 1.6-5-1),
> r-cran-progressr, r-cran-rcpp (>= 1.0.5), r-cran-rlang (>= 0.4.7),
> r-cran-spam, r-cran-lifecycle, r-cran-generics, r-cran-rcpp, r-cran-rcppeigen,
> libc6 (>= 2.17), libgcc-s1 (>= 3.0), libstdc++6 (>= 13.1),
>
> dh_gencontrol: error: dh_gencontrol: error: dpkg-gencontrol
> -pr-cran-seuratobject -ldebian/changelog
> -Tdebian/r-cran-seuratobject.substvars -cdebian/control
> -Pdebian/.debhelper/r-cran-seuratobject/dbgsym-root -UPre-Depends
> -URecommends -USuggests -UEnhances -UProvides -UEssential -UConflicts
> -DPriority=optional -UHomepage -UImportant -DAuto-Built-Package=debug-symbols
> -UProtected -UBuilt-Using -UStatic-Built-Using
> -DPackage=r-cran-seuratobject-dbgsym "-DDepends=r-cran-seuratobject (=
> \${binary:Version})" "-DDescription=debug symbols for r-cran-seuratobject"
> -DBuild-Ids=4f1c07f630f9d500c3cba6813ed40318efbe3d1c -DSection=debug
> -UMulti-Arch -UReplaces -UBreaks returned exit code 25
>
> dh_gencontrol: error: Aborting due to earlier error
> make[1]: *** [debian/rules:9: override_dh_gencontrol] Error 25
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/r-cran-seuratobject_5.0.1-1_unstable-arm64.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: r-cran-seuratobject
Source-Version: 5.0.1-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-seuratobject, 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
Bug#1069756: readability: build time test error: lxml.html.clean module is now a separate project lxml_html_clean
Source: readability Version: 0.8.1+dfsg1-3 Severity: serious Tags: ftbfs Justification: ftbfs Dear Maintainer, Attempt to run readability tests at build time results in the following error: == ERROR: readability (unittest.loader._FailedTest.readability) -- ImportError: Failed to import test module: readability Traceback (most recent call last): File "/usr/lib/python3.11/unittest/loader.py", line 452, in _find_test_path package = self._get_module_from_name(name) File "/usr/lib/python3.11/unittest/loader.py", line 362, in _get_module_from_name __import__(name) File "/<>/.pybuild/cpython3_3.11/build/readability/__init__.py", line 3, in from .readability import Document File "/<>/.pybuild/cpython3_3.11/build/readability/readability.py", line 11, in from .cleaners import clean_attributes File "/<>/.pybuild/cpython3_3.11/build/readability/cleaners.py", line 3, in from lxml.html.clean import Cleaner File "/usr/lib/python3/dist-packages/lxml/html/clean.py", line 18, in raise ImportError( ImportError: lxml.html.clean module is now a separate project lxml_html_clean. Install lxml[html_clean] or lxml_html_clean directly. As far as I could witness, replacing the python3-lxml build dependency by python3-lxml-html-clean resolved the issue at least for the bulid time test. The package is subject to autodep8 python3 test, which raises that the binary package will also need it dependencies adjusted; this suggests the setup.py would probably need patching so this is addressed appropriately at a larger scale than Debian's. The missing dependency on python3-lxml-html-clean is also causing a regression in offpunk autopkgtest[1], although that could be easily worked around by pulling the missing dependency there. [1]: https://ci.debian.net/packages/o/offpunk/unstable/amd64/44684161/ Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/4, please excuse my verbosity `-on air: Mike Oldfield - Lion signature.asc Description: PGP signature
Bug#1069338: marked as done (Not installable due to a bad dh_makeshlibs override)
Your message dated Wed, 24 Apr 2024 09:08:27 + with message-id and subject line Bug#1069338: fixed in ui-gxmlcpp 1.4.6-2 has caused the Debian Bug report #1069338, regarding Not installable due to a bad dh_makeshlibs override 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.) -- 1069338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libui-gxmlcpp5t64 Version: 1.4.6-1.1+b1 Severity: grave Unsatisfied dependencies: libui-gxmlcpp5t64 : Depends: libui-gxmlcpp5v5 (>= 1.4.3) but it is not installable This is because override_dh_makeshlibs generates a dep on the pre-t64 name. -- 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/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libui-gxmlcpp5t64 depends on: pn libboost-test1.83.0 ii libc62.37-18 ii libgcc-s114-20240330-1 ii libstdc++6 14-20240330-1 pn libui-utilcpp9t64 ii libxml2 2.9.14+dfsg-1.3+b2 ii libxslt1.1 1.1.35-1 libui-gxmlcpp5t64 recommends no packages. libui-gxmlcpp5t64 suggests no packages. --- End Message --- --- Begin Message --- Source: ui-gxmlcpp Source-Version: 1.4.6-2 Done: Stephan Sürken We believe that the bug you reported is fixed in the latest version of ui-gxmlcpp, 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. Stephan Sürken (supplier of updated ui-gxmlcpp 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: Wed, 24 Apr 2024 10:34:21 +0200 Source: ui-gxmlcpp Architecture: source Version: 1.4.6-2 Distribution: unstable Urgency: medium Maintainer: Stephan Sürken Changed-By: Stephan Sürken Closes: 1069338 Changes: ui-gxmlcpp (1.4.6-2) unstable; urgency=medium . * [8d3d2b6] Ack NMU 1.4.6-1.1 (t64 transition). Thanks Steve Langasek! * [1ad0a1c] debian/rules (%): Drop 'dbgsym migration' support (migration is long over) * [f7fcae3] debian/libui-gxmlcpp5t64.lintian-overrides: Fixup after t64 transition * [7daf705] debian/rules: Drop outdated shlibs override (t64 transition) (Closes: 1069338) * [ecefddc] debian/libui-gxmlcpp5t64.install: Sync name of example installs (t64 transition) * [2b7b7c9] debian/control (Build-Depends): Update to debhelper 13 (needs dh_missing override) * [3e758e4] debian/*.install: Update from 'dh-exec' to 'debhelper 13 substitution' style * [b8a610a] debian/control (Standards-Version): Update to 4.7 (no changes needed) Checksums-Sha1: 55122fec49d5e60e2efa2c7f4051f81ce617cda4 2154 ui-gxmlcpp_1.4.6-2.dsc 50eea2a9184f69e6bf7a82ace156bee55cc00fba 7700 ui-gxmlcpp_1.4.6-2.debian.tar.xz b22a898b0afb7ed311322d69f6ba97628d5b4c77 16824 ui-gxmlcpp_1.4.6-2_source.buildinfo Checksums-Sha256: b9e7de3140a1ab776b0e3ad0cb3043449f2c5fa28466d1dc40a18b5afe3b7ccc 2154 ui-gxmlcpp_1.4.6-2.dsc 409f26ae49a06a21f3dcd77e5421cd55a0ecd10f81402e875072bd1e75503567 7700 ui-gxmlcpp_1.4.6-2.debian.tar.xz 7fc949392ebc79a7b0b0fa3fcddab7da92d77c61b70176b2c8cdf9e568ed6b49 16824 ui-gxmlcpp_1.4.6-2_source.buildinfo Files: aaa091821f97541f156753000c3f20c5 2154 libs optional ui-gxmlcpp_1.4.6-2.dsc 4f45a486125f540f9e122be57b31c0c8 7700 libs optional ui-gxmlcpp_1.4.6-2.debian.tar.xz eb837f8a2147e3690a99adab6eb94b5a 16824 libs optional ui-gxmlcpp_1.4.6-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEVOttCJ+jfBmmRZCzBm3oAX4rYdkFAmYoxFsSHGFic3VyZEBk ZWJpYW4ub3JnAAoJEAZt6AF+K2HZCFEP/1k+3gT2YbuN1yCmOHDezhqalhXpHNMg
Processed: tagging 1069551
Processing commands for cont...@bugs.debian.org:
> tags 1069551 + moreinfo
Bug #1069551 [src:numpy] numpy: FTBFS on armel: dh_auto_test: error: pybuild
--test -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069414: marked as done (r-cran-irlba: FTBFS on arm64: dpkg-gencontrol: error: parsing package 'r-cran-irlba' Depends field: r-api-4.0, r-base-core (>= ii r-base-core 4.3.3-3+b1 arm64
Your message dated Wed, 24 Apr 2024 08:43:43 +
with message-id
and subject line Bug#1069414: fixed in r-cran-irlba 2.3.5.1-3
has caused the Debian Bug report #1069414,
regarding r-cran-irlba: FTBFS on arm64: dpkg-gencontrol: error: parsing package
'r-cran-irlba' Depends field: r-api-4.0, r-base-core (>= ii r-base-core
4.3.3-3+b1 arm64GNU R core of statistical computation and graphics
system) , , r-cran-matrix (>= 1.6-5-1), , r-cran-matrix,
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.)
--
1069414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-irlba
Version: 2.3.5.1-2
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[1]: Entering directory '/<>'
> rmbversion=`dpkg -l r-cran-matrix | grep 'ii' | sed
> 's/^.*r-cran-matrix[[:space:]]\+\([0-9.-]\+\)[[:space:]]\+.*/\1/'`; \
> sed -i "s/r-cran-matrix[^,]*/r-cran-matrix (>= ${rmbversion})/"
> debian/*substvars
> rversion=`dpkg -l r-base-core | grep 'ii' | sed
> 's/^.*r-base-core[[:space:]]\+\([0-9.-]\+\)-[0-9]\+[[:space:]]\+.*/\1/'`; \
> sed -i "s/\(r-api-[0-9.]\+\),/& r-base-core (>= ${rversion})/"
> debian/*substvars
> dh_gencontrol
> dpkg-gencontrol: warning: can't parse dependency r-base-core (>= ii
> r-base-core4.3.3-3+b1 arm64GNU R core of statistical
> computation and graphics system)
> dpkg-gencontrol: error: parsing package 'r-cran-irlba' Depends field:
> r-api-4.0, r-base-core (>= ii r-base-core4.3.3-3+b1 arm64GNU R
> core of statistical computation and graphics system) , , r-cran-matrix (>=
> 1.6-5-1), , r-cran-matrix,
> libblas3 | libblas.so.3, libc6 (>= 2.17), liblapack3 | liblapack.so.3,
>
> dh_gencontrol: error: dh_gencontrol: error: dpkg-gencontrol -pr-cran-irlba
> -ldebian/changelog -Tdebian/r-cran-irlba.substvars -cdebian/control
> -Pdebian/.debhelper/r-cran-irlba/dbgsym-root -UPre-Depends -URecommends
> -USuggests -UEnhances -UProvides -UEssential -UConflicts -DPriority=optional
> -UHomepage -UImportant -DAuto-Built-Package=debug-symbols -UProtected
> -UBuilt-Using -UStatic-Built-Using -DPackage=r-cran-irlba-dbgsym
> "-DDepends=r-cran-irlba (= \${binary:Version})" "-DDescription=debug symbols
> for r-cran-irlba" -DBuild-Ids=7457c6efa05433cb1b2a5ca96c35719f6075c862
> -DSection=debug -UMulti-Arch -UReplaces -UBreaks returned exit code 25
>
> dh_gencontrol: error: Aborting due to earlier error
> make[1]: *** [debian/rules:9: override_dh_gencontrol] Error 25
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/r-cran-irlba_2.3.5.1-2_unstable-arm64.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: r-cran-irlba
Source-Version: 2.3.5.1-3
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-irlba, 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.
Andreas Tille (supplier of updated r-cran-irlba 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: Wed, 24 Apr 2024 09:33:25 +0200
Source: r-cran-irlba
Architecture: source
Version: 2.3.5.1-3
Distribution: unstable
Bug#1069388: marked as done (r-cran-openmx: FTBFS on arm64: dpkg-gencontrol: error: parsing package 'r-cran-openmx' Depends field: r-api-4.0, r-base-core (>= ii r-base-core 4.3.3-3+b1 arm64
Your message dated Wed, 24 Apr 2024 08:44:03 +
with message-id
and subject line Bug#1069388: fixed in r-cran-openmx 2.21.11+dfsg-3
has caused the Debian Bug report #1069388,
regarding r-cran-openmx: FTBFS on arm64: dpkg-gencontrol: error: parsing
package 'r-cran-openmx' Depends field: r-api-4.0, r-base-core (>= ii
r-base-core4.3.3-3+b1 arm64GNU R core of statistical computation
and graphics system) , , , r-cran-digest, r-cran-mass, r-cran-matrix (>=
1.6-5-1), r-cran-rcpp, r-cran-rcppparallel, r-cran-lifecycle, r-cran-rcpp,
r-cran-rcppeigen (>= 0.3.3.9.4), r-cran-rcppparallel, r-cran-stanheaders (>=
2.10.0.2), r-cran-bh (>= 1.69.0-1), r-cran-rpf (>= 0.45), r-cran-matrix,
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.)
--
1069388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-openmx
Version: 2.21.11+dfsg-2
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[1]: Entering directory '/<>'
> rmbversion=`dpkg -l r-cran-matrix | grep 'ii' | sed
> 's/^.*r-cran-matrix[[:space:]]\+\([0-9.-]\+\)[[:space:]]\+.*/\1/'`; \
> sed -i "s/r-cran-matrix ([^)]\+)/r-cran-matrix (>= ${rmbversion})/"
> debian/*substvars
> rversion=`dpkg -l r-base-core | grep 'ii' | sed
> 's/^.*r-base-core[[:space:]]\+\([0-9.-]\+\)-[0-9]\+[[:space:]]\+.*/\1/'`; \
> sed -i "s/\(r-api-[0-9.]\+\),/& r-base-core (>= ${rversion})/"
> debian/*substvars
> dh_gencontrol
> dpkg-gencontrol: warning: can't parse dependency r-base-core (>= ii
> r-base-core4.3.3-3+b1 arm64GNU R core of statistical
> computation and graphics system)
> dpkg-gencontrol: error: parsing package 'r-cran-openmx' Depends field:
> r-api-4.0, r-base-core (>= ii r-base-core4.3.3-3+b1 arm64GNU R
> core of statistical computation and graphics system) , , , r-cran-digest,
> r-cran-mass, r-cran-matrix (>= 1.6-5-1), r-cran-rcpp, r-cran-rcppparallel,
> r-cran-lifecycle, r-cran-rcpp, r-cran-rcppeigen (>= 0.3.3.9.4),
> r-cran-rcppparallel, r-cran-stanheaders (>= 2.10.0.2), r-cran-bh (>=
> 1.69.0-1), r-cran-rpf (>= 0.45), r-cran-matrix,
> libc6 (>= 2.29), libgcc-s1 (>= 4.5), libgomp1 (>= 6), libstdc++6 (>=
> 13.1), libtbb12 (>= 2021.11.0),
> ,
> python3
> dh_gencontrol: error: dh_gencontrol: error: dpkg-gencontrol -pr-cran-openmx
> -ldebian/changelog -Tdebian/r-cran-openmx.substvars -cdebian/control
> -Pdebian/.debhelper/r-cran-openmx/dbgsym-root -UPre-Depends -URecommends
> -USuggests -UEnhances -UProvides -UEssential -UConflicts -DPriority=optional
> -UHomepage -UImportant -DAuto-Built-Package=debug-symbols -UProtected
> -UBuilt-Using -UStatic-Built-Using -DPackage=r-cran-openmx-dbgsym
> "-DDepends=r-cran-openmx (= \${binary:Version})" "-DDescription=debug symbols
> for r-cran-openmx" -DBuild-Ids=8d8ed9441edac6c9940ee30161095fc842b45369
> -DSection=debug -UMulti-Arch -UReplaces -UBreaks returned exit code 25
>
> dh_gencontrol: error: Aborting due to earlier error
> make[1]: *** [debian/rules:13: override_dh_gencontrol] Error 25
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/r-cran-openmx_2.21.11+dfsg-2_unstable-arm64.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: r-cran-openmx
Source-Version: 2.21.11+dfsg-3
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-openmx, 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
Bug#1069364: marked as done (r-cran-tmb: FTBFS on arm64: dpkg-gencontrol: error: parsing package 'r-cran-tmb' Depends field: r-api-4.0, r-base-core (>= ii r-base-core 4.3.3-3+b1 arm64 GNU R
Your message dated Wed, 24 Apr 2024 07:34:29 +
with message-id
and subject line Bug#1069364: fixed in r-cran-tmb 1.9.11-1
has caused the Debian Bug report #1069364,
regarding r-cran-tmb: FTBFS on arm64: dpkg-gencontrol: error: parsing package
'r-cran-tmb' Depends field: r-api-4.0, r-base-core (>= ii r-base-core
4.3.3-3+b1 arm64GNU R core of statistical computation and graphics
system) , , , r-cran-matrix (>= 1.6-5-1), r-cran-matrix, r-cran-rcppeigen,
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.)
--
1069364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-tmb
Version: 1.9.10-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[1]: Entering directory '/<>'
> rmbversion=`dpkg -l r-cran-matrix | grep 'ii' | sed
> 's/^.*r-cran-matrix[[:space:]]\+\([0-9.-]\+\)[[:space:]]\+.*/\1/'`; \
> sed -i "s/r-cran-matrix ([^)]\+)/r-cran-matrix (>= ${rmbversion})/"
> debian/*substvars
> rversion=`dpkg -l r-base-core | grep 'ii' | sed
> 's/^.*r-base-core[[:space:]]\+\([0-9.-]\+\)-[0-9]\+[[:space:]]\+.*/\1/'`; \
> sed -i "s/\(r-api-[0-9.]\+\),/& r-base-core (>= ${rversion})/"
> debian/*substvars
> dh_gencontrol
> dpkg-gencontrol: warning: can't parse dependency r-base-core (>= ii
> r-base-core4.3.3-3+b1 arm64GNU R core of statistical
> computation and graphics system)
> dpkg-gencontrol: error: parsing package 'r-cran-tmb' Depends field:
> r-api-4.0, r-base-core (>= ii r-base-core4.3.3-3+b1 arm64GNU R
> core of statistical computation and graphics system) , , , r-cran-matrix (>=
> 1.6-5-1), r-cran-matrix, r-cran-rcppeigen,
> libblas3 | libblas.so.3, libc6 (>= 2.29), libgcc-s1 (>= 3.0),
> libgomp1 (>= 4.2.1), liblapack3 | liblapack.so.3, libstdc++6 (>= 13.1),
>
> dh_gencontrol: error: dh_gencontrol: error: dpkg-gencontrol -pr-cran-tmb
> -ldebian/changelog -Tdebian/r-cran-tmb.substvars -cdebian/control
> -Pdebian/.debhelper/r-cran-tmb/dbgsym-root -UPre-Depends -URecommends
> -USuggests -UEnhances -UProvides -UEssential -UConflicts -DPriority=optional
> -UHomepage -UImportant -DAuto-Built-Package=debug-symbols -UProtected
> -UBuilt-Using -UStatic-Built-Using -DPackage=r-cran-tmb-dbgsym
> "-DDepends=r-cran-tmb (= \${binary:Version})" "-DDescription=debug symbols
> for r-cran-tmb" "-DBuild-Ids=45f8347a3aceaa2983340c98d6ce0fdab6f9600c
> 6d4001263cb1b2176ede846cecc1f76938d2694e" -DSection=debug -UMulti-Arch
> -UReplaces -UBreaks returned exit code 25
>
> dh_gencontrol: error: Aborting due to earlier error
> make[1]: *** [debian/rules:13: override_dh_gencontrol] Error 25
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/r-cran-tmb_1.9.10-1_unstable-arm64.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: r-cran-tmb
Source-Version: 1.9.11-1
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-tmb, 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.
Andreas Tille (supplier of updated r-cran-tmb 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: Wed,
Bug#1069747: reassign 1069747 to src:linux, closing 1069747
reassign 1069747 src:linux close 1069747 thanks The missing pre-requisite backport was specific to the 6.1.y series.
Processed: reassign 1069747 to src:linux, closing 1069747
Processing commands for cont...@bugs.debian.org: > reassign 1069747 src:linux Bug #1069747 [linux-image-6.6.13+bpo-amd64] ext4 data loss issue in backport kernels still unfixed? Bug reassigned from package 'linux-image-6.6.13+bpo-amd64' to 'src:linux'. No longer marked as found in versions 6.6.13. Ignoring request to alter fixed versions of bug #1069747 to the same values previously set > close 1069747 Bug #1069747 [src:linux] ext4 data loss issue in backport kernels still unfixed? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1069747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069332: marked as done (Not installable due to hardcoded pre-t64 library deps)
Your message dated Wed, 24 Apr 2024 07:19:25 + with message-id and subject line Bug#1069332: fixed in gvmd 23.5.2-1 has caused the Debian Bug report #1069332, regarding Not installable due to hardcoded pre-t64 library deps 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.) -- 1069332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gvmd Version: 23.1.0-1+b4 Severity: grave gvmd explicitly Depends: libgvm22. It should be changed to the t64 name if it's really needed. -- 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/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gvmd depends on: ii adduser 3.137 pn doc-base pn greenbone-feed-sync pn gvmd-common ii libbsd0 0.12.2-1 ii libc62.37-18 ii libglib2.0-0t64 2.78.4-6 ii libgnutls30t64 3.8.5-2 ii libgpgme11t641.18.0-4.1+b1 pn libgvm22 pn libgvm22t64 ii libical3t64 3.0.17-1.1+b1 pn libpq5 pn notus-scanner pn ospd-openvas pn pg-gvm pn postgresql-16 pn xml-twig-tools Versions of packages gvmd recommends: pn nsis pn rpm gvmd suggests no packages. --- End Message --- --- Begin Message --- Source: gvmd Source-Version: 23.5.2-1 Done: Sophie Brun We believe that the bug you reported is fixed in the latest version of gvmd, 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. Sophie Brun (supplier of updated gvmd 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: Wed, 24 Apr 2024 08:58:35 +0200 Source: gvmd Architecture: source Version: 23.5.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Sophie Brun Closes: 1069332 Changes: gvmd (23.5.2-1) unstable; urgency=medium . * New upstream version 23.5.2 * Update minimal version of libgvm-dev * Replace build-dep pkg-config with pkgconf * Refresh patches * Remove hard-coded lib (Closes: #1069332) * Depends on correct package postgresql-VERSION-pg-gvm * Update minimal required version of greenbone-feed-sync Checksums-Sha1: 609151204870b8140a82811d705e7d215d494254 2208 gvmd_23.5.2-1.dsc ccdc4475945e49bce471fae5d3ba781152c8bd5e 1064064 gvmd_23.5.2.orig.tar.gz 85f286d8b326a2e9d3cf85b65d45136d46835c9a 26072 gvmd_23.5.2-1.debian.tar.xz 4fe2e18799124381f2bee6b1367a99ef7ba9dc69 11070 gvmd_23.5.2-1_source.buildinfo Checksums-Sha256: c278054187fbd2fe725383dd2c633142da43ce670f0b2953fb1fa3bbd1dace11 2208 gvmd_23.5.2-1.dsc 9ac3e58ef191259c0f047794f83b36bd5bba61f6c6ebe6d5a63d067707131899 1064064 gvmd_23.5.2.orig.tar.gz ce5921589ddded12c824be5d77e56963c2729e6280f70db6d36d8a926ff25836 26072 gvmd_23.5.2-1.debian.tar.xz 9601ba1d8ef7ceb68a1dbae5af6613e442e4c3632cd77959ce01648ab4285c56 11070 gvmd_23.5.2-1_source.buildinfo Files: 056a8f7f7e549f9c8aa6764b9c2a5399 2208 admin optional gvmd_23.5.2-1.dsc 9c8cd278833de618a8de080cce4e5401 1064064 admin optional gvmd_23.5.2.orig.tar.gz 9ae69e8c035d09854028881feca19e7a 26072 admin optional gvmd_23.5.2-1.debian.tar.xz 7842ee68ef27d3277d94250fa7696453 11070 admin optional gvmd_23.5.2-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Sophie Brun iQIzBAEBCgAdFiEEOyG45orlwW+H9TItV5J4OyBv7jAFAmYorbcACgkQV5J4OyBv 7jA0aA//fP9g8/WkLZ//mfp7Eu3UCtS6CIOWTX4fz7WtFuLIy+Z/oHe//JZpf3mi PwjaBbCUo3VLFwEKV+BLF3u/XDIUrcYRdh/Unn/yDHdbMOjnpG9nTj/Y1xByVdih
Bug#1069747: ext4 data loss issue in backport kernels still unfixed?
Package: linux-image-6.6.13+bpo-amd64
Version: 6.6.13
Severity: grave
The issue was fixed already in the 6.1 kernels, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
From that bug report I read that all kernels are safe if both commits are
present:
91562895f803 ("ext4: properly sync file size update after O_SYNC direct IO")
936e114a245b ("iomap: update ki_pos a little later in iomap_dio_complete")
This is true for the changelog of the default 6.1 kernels:
https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_6.1.85+1_changelog
so in those everything is fine.
But in the changelog of the backport kernels the second line (iomap: update
ki_pos a little later in iomap_dio_complete) is missing. See:
https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_6.6.13+1~bpo12+1_changelog
This is the line which fixes the issue induced by the first line.
So, if I'm not mistaken, this means that in the current debian backport kernels
linux-image-6.5.0-0.deb12.4-amd64 and linux-image-6.6.13+bpo-amd64 the ext4
data loss issue is still unfixed. Both kernels are currently distributed via
apt from the debian repos.
