Bug#1037977: rust-ureq - update for base64 0.21
Package: rust-ureq
Version: 2.6.2-3
Severity: serious
Tags: trixie, sid, patch, ftbfs
rust-base64 was recently updated to 0.21 making rust-ureq unbuildable and
uninstallable.
Upstream already has a fix, I grabbed it and added it to the Debian package and
it
built and passed autopkgtests fine.
Debdiff attached, I may or may not NMU this later.diff -Nru rust-ureq-2.6.2/debian/changelog rust-ureq-2.6.2/debian/changelog
--- rust-ureq-2.6.2/debian/changelog2023-02-12 16:16:54.0 +
+++ rust-ureq-2.6.2/debian/changelog2023-06-15 02:17:59.0 +
@@ -1,3 +1,10 @@
+rust-ureq (2.6.2-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply upstream patch for base64 0.21.
+
+ -- Peter Michael Green Thu, 15 Jun 2023 02:17:59 +
+
rust-ureq (2.6.2-3) unstable; urgency=medium
* avoid initial dash in autopkgtest test name;
diff -Nru rust-ureq-2.6.2/debian/control rust-ureq-2.6.2/debian/control
--- rust-ureq-2.6.2/debian/control 2023-01-26 16:13:56.0 +
+++ rust-ureq-2.6.2/debian/control 2023-06-15 02:17:57.0 +
@@ -4,7 +4,7 @@
Build-Depends:
debhelper-compat (= 13),
dh-cargo (>= 25),
- librust-base64-0.13+default-dev ,
+ librust-base64-0.21+default-dev ,
librust-brotli-decompressor-2+default-dev ,
librust-chunked-transfer-1+default-dev ,
librust-cookie-0.16-dev ,
@@ -37,7 +37,7 @@
Architecture: all
Multi-Arch: foreign
Depends:
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
librust-brotli-decompressor-2+default-dev,
librust-chunked-transfer-1+default-dev,
librust-cookie-0.16-dev,
diff -Nru rust-ureq-2.6.2/debian/patches/0001_base64.patch
rust-ureq-2.6.2/debian/patches/0001_base64.patch
--- rust-ureq-2.6.2/debian/patches/0001_base64.patch1970-01-01
00:00:00.0 +
+++ rust-ureq-2.6.2/debian/patches/0001_base64.patch2023-06-15
02:16:54.0 +
@@ -0,0 +1,59 @@
+commit abda74c4d8d1235c6eddccafd3c4bd690dc10ea7
+Author: Martin Algesten
+Date: Mon Jan 30 23:39:55 2023 +0100
+
+Upgrade deps
+
+diff --git a/Cargo.toml b/Cargo.toml
+index 00dc9f0ea..418ae582b 100644
+--- a/Cargo.toml
b/Cargo.toml
+@@ -26,7 +26,7 @@ gzip = ["flate2"]
+ brotli = ["brotli-decompressor"]
+
+ [dependencies]
+-base64 = "0.13"
++base64 = "0.21"
+ cookie = { version = "0.16", default-features = false, optional = true}
+ once_cell = "1"
+ url = "2"
+diff --git a/src/proxy.rs b/src/proxy.rs
+index ff9413917..0148904a1 100644
+--- a/src/proxy.rs
b/src/proxy.rs
+@@ -1,3 +1,5 @@
++use base64::{prelude::BASE64_STANDARD, Engine};
++
+ use crate::error::{Error, ErrorKind};
+
+ /// Proxy protocol
+@@ -131,7 +133,7 @@ impl Proxy {
+
+ pub(crate) fn connect>(, host: S, port: u16) -> String
{
+ let authorization = if self.use_authorization() {
+-let creds = base64::encode(format!(
++let creds = BASE64_STANDARD.encode(format!(
+ "{}:{}",
+ self.user.clone().unwrap_or_default(),
+ self.password.clone().unwrap_or_default()
+diff --git a/src/unit.rs b/src/unit.rs
+index 895067ff0..2011bb673 100644
+--- a/src/unit.rs
b/src/unit.rs
+@@ -3,6 +3,7 @@ use std::io::{self, Write};
+ use std::ops::Range;
+ use std::time;
+
++use base64::{prelude::BASE64_STANDARD, Engine};
+ use log::debug;
+ use url::Url;
+
+@@ -87,7 +88,7 @@ impl Unit {
+ if (!username.is_empty() || !password.is_empty())
+ && get_header(, "authorization").is_none()
+ {
+-let encoded = base64::encode(format!("{}:{}", username,
password));
++let encoded = BASE64_STANDARD.encode(format!("{}:{}",
username, password));
+ extra.push(Header::new("Authorization", !("Basic {}",
encoded)));
+ }
+
diff -Nru rust-ureq-2.6.2/debian/patches/series
rust-ureq-2.6.2/debian/patches/series
--- rust-ureq-2.6.2/debian/patches/series 2023-01-26 16:08:45.0
+
+++ rust-ureq-2.6.2/debian/patches/series 2023-06-15 02:17:14.0
+
@@ -1,3 +1,4 @@
+0001_base64.patch
2001_native_certs.patch
2002_env_logger.patch
2003_cookie-store.patch
Bug#1037961: marked as done (picolibc: autopkgtest regression: truncated to fit: R_RISCV_HI20 against `.LC0')
Your message dated Thu, 15 Jun 2023 04:19:26 + with message-id and subject line Bug#1037961: fixed in picolibc 1.8.2-2 has caused the Debian Bug report #1037961, regarding picolibc: autopkgtest regression: truncated to fit: R_RISCV_HI20 against `.LC0' 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.) -- 1037961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: picolibc Version: 1.8.1-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of picolibc the autopkgtest of picolibc fails in testing when that autopkgtest is run with the binary packages of picolibc from unstable on amd64 and i386. It passes when run with only packages from testing. In tabular form: passfail picolibc from testing1.8.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=picolibc https://ci.debian.net/data/autopkgtest/testing/amd64/p/picolibc/34189996/log.gz /tmp/ccppXFby.o: in function `main': touch.c:(.text+0x2e): relocation truncated to fit: R_RISCV_HI20 against `.LC0' collect2: error: ld returned 1 exit status autopkgtest [17:11:55]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: picolibc Source-Version: 1.8.2-2 Done: Keith Packard We believe that the bug you reported is fixed in the latest version of picolibc, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Keith Packard (supplier of updated picolibc 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, 14 Jun 2023 16:12:55 -0700 Source: picolibc Architecture: source Version: 1.8.2-2 Distribution: unstable Urgency: medium Maintainer: Keith Packard Changed-By: Keith Packard Closes: 1037961 Changes: picolibc (1.8.2-2) unstable; urgency=medium . * Adjust compile flags for riscv autopkgtest. Closes: #1037961. Checksums-Sha1: f9575cc49278e35f3808d6b7cfa2ad267e663ce9 2297 picolibc_1.8.2-2.dsc 37d50dab8105f930f855753a8f68fcc827fb9b05 32116 picolibc_1.8.2-2.debian.tar.xz 6be7d766916a3b4c3910fd8086bbd0ad3e1babb2 10907 picolibc_1.8.2-2_amd64.buildinfo Checksums-Sha256: 96270fdd4423db4955d41e0dbe7fadf6b2aaebc331027adb7a206678c19c4f52 2297 picolibc_1.8.2-2.dsc de9b788dbe40636bb16ad667e179929c67fd9103ad993910f90f4c3f98c27d9b 32116 picolibc_1.8.2-2.debian.tar.xz 80f821915900de0cd92027b0b5bc1cfe4beeb9a46db4d73cd2321e21d0661516 10907 picolibc_1.8.2-2_amd64.buildinfo Files: d77744f413908821e292e2af1c4b2460 2297 devel optional picolibc_1.8.2-2.dsc 722aaf134df63a00f77db478bab62b78 32116 devel optional picolibc_1.8.2-2.debian.tar.xz caa4b5a0f518dad53bbdade007c7cf23 10907 devel optional picolibc_1.8.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmSKjQYACgkQ2yIaaQAA ABH9yxAAjUyw1MT7lttg5Kz8yvgd3dMxf4/92K+9BIOPsnGD/1fBddIKTSHBUrW/ +n3Ii5z56VZ7A0QCqwRv1Ig5kBjvpYnTQBRNB96EC+bC/rZjhHBxo+0LXPRtQMgx 2CNqEsV14S7c5XWzw2+x9zovdgM43hPATVMLY78wXhPPa0PsOBt7LiVemV6gP53Z b0F93lZFHxFl1pBvEiWTDf4D51vh5uote0WJ7T4d/93JFULc1O1KUecocYHNLfMy to3WsLcW9UTZbTin1a6wS4MahSaQ2+Q5j4OMzLRa3vdQjYlKAfGaZnVX46c6wywO 6WN1CD7RzHUYFxQVzB87zX3q9LdPL0VKvvmxSvO6qK8sVw48jlRw+O9CcgTEZDaV xDBHR/HTv+dTP0fzScoJB2oQ8tuv2U0Zw6svl23nd/bTxbZFoC3XLqA3pDv8/qKX gBbIG3GQDDiTUyHzXGyeMg4lzFxp4UCeiao1nP9KS/rd935syFbyO2EU8+z0enYG xwbwQC8IHyfxi8vHz8MTbJ+YK89U+Ok5PdQEZma9VaB2ZbqsZOGeL7AVrs2QWVeV z97gTwdRLrCBJ76xBwCcsLkn77plwWvx1Tny8Y02tGa58//AhgonH0nf6mVOS4mC aDDqAMYVbB9spwIP1jE7UX2Eg8bm3Pt82V22A3bf8dO4ER86rgM= =umQh -END PGP SIGNATURE End Message ---
Processed: affects 1030129
Processing commands for cont...@bugs.debian.org: > affects 1030129 src:opencv Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install: Error loading java.security file Added indication that 1030129 affects src:opencv > thanks Stopping processing here. Please contact me if you need assistance. -- 1030129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037974: ddcci-dkms: code fails to build and package fails to install with Linux 6.3 headers
Package: ddcci-dkms
Version: 0.4.2-4
Severity: serious
When I try to install ddcci-dkms with the Linux 6.3 headers installed,
the build of the code fails and then the install of the package fails.
I think there are two problems here:
* The code needs to be adapted to the latest Linux kernel version.
* The package should not fail to install when the module build fails.
This might be a problem in dkms itself, or in ddcci's integration.
I note that the combination of these issues also will break
installation of Linux 6.3 when ddcci-dkms is installed.
$ sudo apt install ddcci-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
ddcci-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.7 kB of archives.
After this operation, 95.2 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian testing/main amd64 ddcci-dkms all
0.4.2-4 [21.7 kB]
Fetched 21.7 kB in 1s (17.0 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously unselected package ddcci-dkms.
(Reading database ... 730615 files and directories currently installed.)
Preparing to unpack .../ddcci-dkms_0.4.2-4_all.deb ...
Unpacking ddcci-dkms (0.4.2-4) ...
Setting up ddcci-dkms (0.4.2-4) ...
Loading new ddcci-0.4.2 DKMS files...
Building for 6.3.0-1-amd64
Building initial module for 6.3.0-1-amd64
Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64)
Consult /var/lib/dkms/ddcci/0.4.2/build/make.log for more information.
dpkg: error processing package ddcci-dkms (--configure):
installed ddcci-dkms package post-installation script subprocess returned
error exit status 10
Errors were encountered while processing:
ddcci-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ cat /var/lib/dkms/ddcci/0.4.2/build/make.log
DKMS make.log for ddcci-0.4.2 for kernel 6.3.0-1-amd64 (x86_64)
Thu 15 Jun 2023 10:23:01 AWST
make: Entering directory '/var/lib/dkms/ddcci/0.4.2/build'
make -C "ddcci"
make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.2/build/ddcci'
make -C "/lib/modules/6.3.0-1-amd64/build"
M="/var/lib/dkms/ddcci/0.4.2/build/ddcci" modules
make[2]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
CC [M] /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.o
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: error: initialization
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’
[-Werror=incompatible-pointer-types]
1053 | .uevent = ddcci_device_uevent,
| ^~~
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: note: (near
initialization for ‘ddcci_device_type.uevent’)
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: error: initialization
of ‘char * (*)(const struct device *, umode_t *, kuid_t *, kgid_t *)’ {aka
‘char * (*)(const struct device *, short unsigned int *, kuid_t *, kgid_t *)’}
from incompatible pointer type ‘char * (*)(struct device *, umode_t *, kuid_t
*, kgid_t *)’ {aka ‘char * (*)(struct device *, short unsigned int *, kuid_t *,
kgid_t *)’} [-Werror=incompatible-pointer-types]
1056 | .devnode = ddcci_devnode
| ^
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: note: (near
initialization for ‘ddcci_device_type.devnode’)
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: error: initialization
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’
[-Werror=incompatible-pointer-types]
1062 | .uevent = ddcci_device_uevent,
| ^~~
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: note: (near
initialization for ‘ddcci_dependent_type.uevent’)
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1065:27: error: initialization
of ‘char * (*)(const struct device *, umode_t *, kuid_t *, kgid_t *)’ {aka
‘char * (*)(const struct device *, short unsigned int *, kuid_t *, kgid_t *)’}
from incompatible pointer type ‘char * (*)(struct device *, umode_t *, kuid_t
*, kgid_t *)’ {aka ‘char * (*)(struct device *, short unsigned int *, kuid_t *,
kgid_t *)’} [-Werror=incompatible-pointer-types]
1065 | .devnode = ddcci_dependent_devnode
| ^~~
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1065:27: note: (near
initialization for ‘ddcci_dependent_type.devnode’)
In file included from
/usr/src/linux-headers-6.3.0-1-common/include/linux/build_bug.h:5,
from
Bug#1033503: marked as done (dgit autopkgtests broken by git 2.40)
Your message dated Thu, 15 Jun 2023 00:19:51 +
with message-id
and subject line Bug#1033503: fixed in dgit 11.0
has caused the Debian Bug report #1033503,
regarding dgit autopkgtests broken by git 2.40
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.)
--
1033503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 10.7
Control: affects -1 git
Some of dgit's tests create strange git objects, to test error
handling. For example, to avoid a repetition of #849041.
git 2.40, just uploaded to unstable, has this change:
| * "git hash-object" now checks that the resulting object is well
| formed with the same code as "git fsck".
| (merge 8e4309038f jk/hash-object-fsck later to maint).
This was probably a good idea. So, dgit's tests need to be updated.
Normally I would file this bug as RC and make the necessary changes.
However, we are currently in the freeze for bookworm. Information on
tracker.d.o suggests that git is not going to migrate to bookworm
anyway, without an unblock from the release team. I don't see an
unblock request in https://bugs.debian.org/release.debian.org .
Release team: do you think we (dgit maintainers) should update the
test suite now, for bookworm ? The changes would be limited to tests,
but the new checks in git mean we'll need to take a different approach
for some of them, which might be complex or messy.
Unhelpfully, there is also #1032826, which prevents "dgit import-dsc"
working for the current git.dsc in bookworm. I think this situation
is RC. I haven't filed a bug against src:git because I think we can
fix this just by changing the infrastructure - I'm talking to DSA
about this - but if that turns out to be impossible, we may need to
upload a no-source-changes src:git :-/.
Thanks for everyone's attention and advice/opinions.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 11.0
Done: Ian Jackson
We believe that the bug you reported is fixed in the latest version of
dgit, 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 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ian Jackson (supplier of updated dgit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 15 Jun 2023 00:53:22 +0100
Source: dgit
Architecture: source
Version: 11.0
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson
Changed-By: Ian Jackson
Closes: 904969 959760 1033503
Changes:
dgit (11.0) unstable; urgency=medium
.
Bugfix with compatibility implications:
* Pass --no-source-only-changes to sbuild (when building binaries).
Fixes operation with SOURCE_ONLY_CHANGES locally overridden.
(Incompatible with sbuild <0.78; to work around, say
dgit --sbuild!:--no-source-only-changes.).
[Report from Sean Whitton] Closes: #904969.
.
Documentation:
* dgit-maint-{merge,rebase}(7): Cross-reference to gitrevisions(7).
[Sean Whitton, Ian Jackson] Closes: #959760.
.
Removal:
* Abolish dgit-badcommit-fixup (the remedial script for #849041).
If ancient repositories are found which need fixing, install
dgit.deb 10.7 or earlier (eg from Debian bookworm and earlier).
.
Testing;
* Tests: work around git changes in 2.40 relating to commit verification.
Skipping tests involving now-uncreatable objects. Closes: #1033503.
Checksums-Sha1:
532975d4af908f4286b1ffa2a0fa1d250b1c2b2a 1856 dgit_11.0.dsc
9e4280c679be31334acf0c6d511ce8f113fc69b2 681195 dgit_11.0.tar.gz
Checksums-Sha256:
47cf0ec76095bd3c0ef4c338ecd5d4244103a6e0149144638e1f92749d1b57ce 1856
dgit_11.0.dsc
8f995919904e1f2a124cb30fdbdaa9fc3dc1e3b351b61e734e56932944e874e3 681195
dgit_11.0.tar.gz
Files:
8e1c04d85f2ca3708edb662a1337aeb3 1856 devel optional dgit_11.0.dsc
0b7900588b805ff31406ef013ffc8272 681195 devel optional dgit_11.0.tar.gz
-BEGIN PGP
Bug#1037968: marked as done (unauthorised background updates)
Your message dated Wed, 14 Jun 2023 23:55:39 + with message-id and subject line Re: Bug#1037968: unauthorised background updates has caused the Debian Bug report #1037968, regarding unauthorised background updates 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.) -- 1037968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: serious X-Debbugs-Cc: slimshad...@zohomail.eu without my approval the latest kernel update was applied and the most surprising thing is that no downloaded files are present in the cache folder. all happens in the background without my knowledge. only found out during reboot. same for all the other updates like firefox but they not that serious. again updates set to manual. --- End Message --- --- Begin Message --- On Thu, Jun 15, 2023 at 02:46:38AM +0530, slimshady wrote: > without my approval the latest kernel update was applied and the most > surprising thing is that no downloaded files are present in the cache folder. > all happens in the background without my knowledge. only found out during > reboot. same for all the other updates like firefox but they not that serious. > again updates set to manual. closing. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Why Did We Ban Smoking Indoors When We Could Have Just All Washed Our Hands More? (@TheVertlartnic) signature.asc Description: PGP signature --- End Message ---
Bug#1031459: closing 1031459
close 1031459 thanks
Processed: tagging 1031459
Processing commands for cont...@bugs.debian.org: > tags 1031459 - bookworm Bug #1031459 [src:pcb-rnd] pcb-rnd: FTBFS: unsatisfiable build-dependencies: librnd4-dev, librnd4-cloud, librnd4-lib-gui Removed tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1031459
Processing commands for cont...@bugs.debian.org: > close 1031459 Bug #1031459 [src:pcb-rnd] pcb-rnd: FTBFS: unsatisfiable build-dependencies: librnd4-dev, librnd4-cloud, librnd4-lib-gui Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1031459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to dgit, tagging 959760, tagging 904969, tagging 1033503
Processing commands for cont...@bugs.debian.org:
> limit source dgit
Limiting to bugs with field 'source' containing at least one of 'dgit'
Limit currently set to 'source':'dgit'
> tags 959760 + pending
Bug #959760 [dgit] dgit-maint-{merge,rebase}(7): See also git-revisions(7)
Added tag(s) pending.
> tags 904969 + pending
Bug #904969 [dgit] dgit: should pass --no-source-only-changes to sbuild
Ignoring request to alter tags of bug #904969 to the same tags previously set
> tags 1033503 + pending
Bug #1033503 [dgit] dgit autopkgtests broken by git 2.40
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1033503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033503
904969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904969
959760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: affects 1030129
Processing commands for cont...@bugs.debian.org: > affects 1030129 src:gromacs Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install: Error loading java.security file Added indication that 1030129 affects src:gromacs > thanks Stopping processing here. Please contact me if you need assistance. -- 1030129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037364: nextcloud-desktop: TLS initilization failed
Control: tags -1 moreinfo Control: severity -1 important Hey, I never had issues with using Nextcloud desktop to connect to my server, that's why I downgrade the serverity, as it has something to do with your specific setup. I expect that the issue is that your server only accepts TLS < 1.3. The last years a lot of ciphers are not trusted anymore by default. You can check your servers certificate with online tools e.g. https://www.ssllabs.com/ssltest/. regards, hefee signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1037364: nextcloud-desktop: TLS initilization failed
Processing control commands: > tags -1 moreinfo Bug #1037364 [nextcloud-desktop] nextcloud-desktop: TLS initilization failed Ignoring request to alter tags of bug #1037364 to the same tags previously set > severity -1 important Bug #1037364 [nextcloud-desktop] nextcloud-desktop: TLS initilization failed Severity set to 'important' from 'grave' -- 1037364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037968: unauthorised background updates
Package: general Severity: serious X-Debbugs-Cc: slimshad...@zohomail.eu without my approval the latest kernel update was applied and the most surprising thing is that no downloaded files are present in the cache folder. all happens in the background without my knowledge. only found out during reboot. same for all the other updates like firefox but they not that serious. again updates set to manual.
Bug#1036881: whitedune: segfaults
control: tags -1 - bookworm-ignore Hi, On 28-05-2023 21:28, Paul Gevers wrote: I'll try to remember to remove the bookworm-ignore tag after the release. I did. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1036881: whitedune: segfaults
Processing control commands: > tags -1 - bookworm-ignore Bug #1036881 [whitedune] whitedune: segfaults Removed tag(s) bookworm-ignore. -- 1036881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037962: chaos-marmosets: autopkgtest failure on arm64 and ppc64el
Source: chaos-marmosets Version: 0.1.2-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package chaos-marmosets, great. However, it fails on arm64 and ppc64el. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=chaos-marmosets https://ci.debian.net/data/autopkgtest/testing/arm64/c/chaos-marmosets/32979373/log.gz I: Test that divide-by-zero crashes... Trace/breakpoint trap I: divide-by-zero exit code: 133 (expected: 128 + 4 for SIGILL) autopkgtest [21:14:22]: test crashes OpenPGP_signature Description: OpenPGP digital signature
Bug#1037961: picolibc: autopkgtest regression: truncated to fit: R_RISCV_HI20 against `.LC0'
Source: picolibc Version: 1.8.1-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of picolibc the autopkgtest of picolibc fails in testing when that autopkgtest is run with the binary packages of picolibc from unstable on amd64 and i386. It passes when run with only packages from testing. In tabular form: passfail picolibc from testing1.8.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=picolibc https://ci.debian.net/data/autopkgtest/testing/amd64/p/picolibc/34189996/log.gz /tmp/ccppXFby.o: in function `main': touch.c:(.text+0x2e): relocation truncated to fit: R_RISCV_HI20 against `.LC0' collect2: error: ld returned 1 exit status autopkgtest [17:11:55]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1037954: marked as done (please ship upstream themes/)
Your message dated Wed, 14 Jun 2023 14:25:56 -0400 with message-id <87sfatlx3f@angela.anarc.at> and subject line Re: Bug#1037954: please ship upstream themes/ has caused the Debian Bug report #1037954, regarding please ship upstream themes/ 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.) -- 1037954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: foot Version: 1.13.1-2 Severity: critical X-Debbugs-Cc: please ship upstream themes Upstream has a bunch of themes in the source tree. Those can be included with a simple, say: [main] include=/usr/share/foot/themes/gruvbox-light.ini yet we don't ship those themes! Wouldn't it be great to have those around? I'm not sure about /usr/share/foot, but i'm pretty sure it's a good idea to ship them. :) -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages foot depends on: ii foot-terminfo 1.13.1-2 ii libc6 2.36-9 ii libfcft43.1.5-3 ii libfontconfig1 2.14.1-4 ii libpixman-1-0 0.42.2-1 ii libutf8proc22.8.0-1 ii libwayland-client0 1.21.0-1 ii libwayland-cursor0 1.21.0-1 ii libxkbcommon0 1.5.0-1 foot recommends no packages. Versions of packages foot suggests: pn foot-themes -- no debconf information --- End Message --- --- Begin Message --- Control: severity -1 wishlist On 2023-06-14 20:24:28, Birger Schacht wrote: > See https://packages.debian.org/unstable/foot-themes ;) > > PS: severity "critical"? oh my, what a double fuckup. i meant wishlist of course. in any case, total garbage, sorry for the noise.--- End Message ---
Bug#1037954: please ship upstream themes/
See https://packages.debian.org/unstable/foot-themes ;) PS: severity "critical"? On 6/14/23 20:09, Antoine Beaupre wrote: Package: foot Version: 1.13.1-2 Severity: critical X-Debbugs-Cc: please ship upstream themes Upstream has a bunch of themes in the source tree. Those can be included with a simple, say: [main] include=/usr/share/foot/themes/gruvbox-light.ini yet we don't ship those themes! Wouldn't it be great to have those around? I'm not sure about /usr/share/foot, but i'm pretty sure it's a good idea to ship them. :) -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages foot depends on: ii foot-terminfo 1.13.1-2 ii libc6 2.36-9 ii libfcft43.1.5-3 ii libfontconfig1 2.14.1-4 ii libpixman-1-0 0.42.2-1 ii libutf8proc22.8.0-1 ii libwayland-client0 1.21.0-1 ii libwayland-cursor0 1.21.0-1 ii libxkbcommon0 1.5.0-1 foot recommends no packages. Versions of packages foot suggests: pn foot-themes -- no debconf information
Processed: Re: dgit autopkgtests broken by git 2.40 [and 2 more messages]
Processing control commands: > severity -1 serious Bug #1033503 [dgit] dgit autopkgtests broken by git 2.40 Severity set to 'serious' from 'normal' -- 1033503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037954: please ship upstream themes/
Package: foot Version: 1.13.1-2 Severity: critical X-Debbugs-Cc: please ship upstream themes Upstream has a bunch of themes in the source tree. Those can be included with a simple, say: [main] include=/usr/share/foot/themes/gruvbox-light.ini yet we don't ship those themes! Wouldn't it be great to have those around? I'm not sure about /usr/share/foot, but i'm pretty sure it's a good idea to ship them. :) -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages foot depends on: ii foot-terminfo 1.13.1-2 ii libc6 2.36-9 ii libfcft43.1.5-3 ii libfontconfig1 2.14.1-4 ii libpixman-1-0 0.42.2-1 ii libutf8proc22.8.0-1 ii libwayland-client0 1.21.0-1 ii libwayland-cursor0 1.21.0-1 ii libxkbcommon0 1.5.0-1 foot recommends no packages. Versions of packages foot suggests: pn foot-themes -- no debconf information
Processed: Re: Bug#1037932: transition: python-resolvelib
Processing control commands: > reassign -1 src:ansible-core 2.14.3-1 Bug #1037932 [release.debian.org] transition: python-resolvelib Bug reassigned from package 'release.debian.org' to 'src:ansible-core'. Ignoring request to alter found versions of bug #1037932 to the same values previously set Ignoring request to alter fixed versions of bug #1037932 to the same values previously set Bug #1037932 [src:ansible-core] transition: python-resolvelib Marked as found in versions ansible-core/2.14.3-1. > severity -1 serious Bug #1037932 [src:ansible-core] transition: python-resolvelib Severity set to 'serious' from 'normal' > tags -1 sid trixie Bug #1037932 [src:ansible-core] transition: python-resolvelib Added tag(s) sid and trixie. > retitle -1 ansible-core: requires update for python3-resolvelib 1.x Bug #1037932 [src:ansible-core] transition: python-resolvelib Changed Bug title to 'ansible-core: requires update for python3-resolvelib 1.x' from 'transition: python-resolvelib'. -- 1037932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
Processing control commands: > unmerge -1 Bug #1035820 [usrmerge] 9base: leaves entries in /etc/shells after upgrade from bullseye Bug #1033167 [usrmerge] usrmerge: messes with /etc/shells Disconnected #1035820 from all other report(s). > reassign -1 debianutils 5.7-0.4 Bug #1035820 [usrmerge] 9base: leaves entries in /etc/shells after upgrade from bullseye Bug reassigned from package 'usrmerge' to 'debianutils'. No longer marked as found in versions usrmerge/25. Ignoring request to alter fixed versions of bug #1035820 to the same values previously set Bug #1035820 [debianutils] 9base: leaves entries in /etc/shells after upgrade from bullseye Marked as found in versions debianutils/5.7-0.4. > affects -1 + src:9base Bug #1035820 [debianutils] 9base: leaves entries in /etc/shells after upgrade from bullseye Added indication that 1035820 affects src:9base > tag -1 patch pending Bug #1035820 [debianutils] 9base: leaves entries in /etc/shells after upgrade from bullseye Added tag(s) patch and pending. -- 1033167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033167 1035820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
Control: unmerge -1 Control: reassign -1 debianutils 5.7-0.4 Control: affects -1 + src:9base Control: tag -1 patch pending On 13/06/2023 07.26, Helmut Grohne wrote: The entry is added by /usr/lib/usrmerge/convert-etc-shells (which is the policy violation this bug has been merged into). The merging strategy there is based on a knowledge of the symlinks that should exist rather than looking them up in the filesystem. So this is two distinct bugs actually. We also need to fix update-shells to properly deal with update-alternatives using the patch above. Let's use this bug for the debianutils side. I've prepared a NMU with three changes: https://salsa.debian.org/anbe/debianutils/-/commits/fix-update-shells * avoid creating duplicate entries in /etc/shells * handle /bin/sh as defined in the template file * fix canonicalization of shells that are symlinks Especially with the /bin/sh change in place, update-shells and convert-etc-shells should produce similar results. convert-etc-shells needs to call update-shells (before manipulating /etc/shells on its own, s.t. the statefile gets updated), and maybe it can be replaced entirely by update-shells. Andreas
Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server
Control: found -1 3.8.0+git20230413-1 On 2023-06-14 Andreas Beckmann wrote: > Source: gnutls28 > Version: 3.8.0+git20230529-1 > Severity: serious > Hi, > after building gnutls28/experimental with pbuilder, there are a lot of > gnutls-serv and a few openssl s_server processes running, preventing > pbuilder to cleanup the chroot. Hello, This was caused by the changes related to fixing #1031553 (supporting either datefudge or faketime. I think tests/ocsp-tests/ocsp-tls-connection.sh or tests/ocsp-tests/ocsp-must-staple-connection.sh triggers this. 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'
Processed: Re: Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server
Processing control commands: > found -1 3.8.0+git20230413-1 Bug #1037917 [src:gnutls28] gnutls28: leaves processes running after build: gnutls-serv, openssl s_server Marked as found in versions gnutls28/3.8.0+git20230413-1. -- 1037917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031132: marked as done (godot FTBFS on arm64, armel, ppc64el and s390x)
Your message dated Wed, 14 Jun 2023 15:19:47 + with message-id and subject line Bug#1031132: fixed in godot 3.5.1-stable-2 has caused the Debian Bug report #1031132, regarding godot FTBFS on arm64, armel, ppc64el and s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: godot Version: 3.5.1-stable-1 Severity: serious Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: car...@debian.org Hi the recent upload of godot/3.5.1-stable-1 FTBFS on arm64, armel, ppc64el and s390x: https://buildd.debian.org/status/fetch.php?pkg=godot=arm64=3.5.1-stable-1=1675605516=0 https://buildd.debian.org/status/fetch.php?pkg=godot=armel=3.5.1-stable-1=1675605696=0 https://buildd.debian.org/status/fetch.php?pkg=godot=ppc64el=3.5.1-stable-1=1675623981=0 https://buildd.debian.org/status/fetch.php?pkg=godot=s390x=3.5.1-stable-1=1675605014=0 Regards, Salvatore --- End Message --- --- Begin Message --- Source: godot Source-Version: 3.5.1-stable-2 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of godot, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated godot 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, 14 Jun 2023 15:36:52 +0200 Source: godot Architecture: source Version: 3.5.1-stable-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Petter Reinholdtsen Closes: 1019868 1031132 Changes: godot (3.5.1-stable-2) unstable; urgency=medium . * Team upload. . * Adjusted build rules to link with libatomic on armel and riscv64. (Closes: #1019868) * Disabled building denoise module on platforms where OIDN fail to build. (Closes: #1031132) * Updated build dependencies based on feedback from lintian. * Adjusted d/copyright to list CC0 license for appstream metadata XML file. * Adjusted install rules to install both appstream metadata and XSD MIME rules. * Updated Standards-Version from 4.6.0 to 4.6.2. Checksums-Sha1: 91df892c2f2ad79bb665d0c07bb214ba0a856ec4 2589 godot_3.5.1-stable-2.dsc 673e4ad0be8a4f60cd7a4cc4754179be0b257dcf 17512 godot_3.5.1-stable-2.debian.tar.xz 45ac57bbb37b0651f938e8e3f846de8ba36eb2eb 12286 godot_3.5.1-stable-2_source.buildinfo Checksums-Sha256: 426a8c8927de8a20b95a5a91eea54f949ba550e8a81191b253d60be21c041b7d 2589 godot_3.5.1-stable-2.dsc 03a52c1a0530e7c1587b9f609fc4fe6a4d13fd1c2ea9c2b9808df975c6f4f9f5 17512 godot_3.5.1-stable-2.debian.tar.xz 20018139056676cf7f2566edc826eaba85cc8020efe79083b53b23daae1ba950 12286 godot_3.5.1-stable-2_source.buildinfo Files: d826059beaea1aa949a10edfa7103ea6 2589 devel optional godot_3.5.1-stable-2.dsc 9aefd2184a98dfec52878f2283bf04b4 17512 devel optional godot_3.5.1-stable-2.debian.tar.xz 64310a051093853293ba8caae4442ac6 12286 devel optional godot_3.5.1-stable-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmSJ1hcACgkQgSgKoIe6 +w4DshAAiG5YVBGdDmEvKVSIJM0oCEhxRoyQNYKVknX8HV6WoBlSlZ04RJEfKl6H BMXbjGuHejTQ7/neZe1iD4BrVOaksCPIdWAV7qMP0vfUCGlwIWOP3HuPRAMaSKwt e0HvieYv97LVh3bJ2VH/Z6PUlNn++ZjeZ8LnZUdtZlrPKIXW17FTo+2gkzZWWetF 6tdE5j97K90BrhZwvNB0jv3uQ0weHl8CG48vHVRStuqo2yBw3A50ozTbZ3zT0lSJ Jsbc34Uqnfl4N+H9Z1iZbf6PRITOGMIQbuHhKPy/Kllx1rtKs3kbG9nGwI+zfDlJ W2Vofc4nr517f0PNmHww/4mY0TaCfvQwzG2Vl+5zz+GJ36qIXBK4css9bGu0SEU5 mh0MaVkY5Q+gbOvna7CinRWpIBE1rcQ85/IGnrucWtsBunC82mv/b/bjL8z8rsac G3YbQe3RytEmr0m0lFE9rjQfoebHkUBFtYOvPiViREAaZtipfSyk7MFt2526ZVZi zeeV8dTNSrycuZz4DrbS/9I9rBha6/YShIS8xKBG5vZKxSzjrP5b+zA0qIt5o8A3 a+qF9outI7tDBRLKuleqhZPN1EMmDkMx3zBpG8yIYyTW3RTvkaLQ204RM/EfDJVl ztnu6TIf78HV4hHn09ubRfjAmwFWkHeBvfhOBtiV5LiS4k2c4Xs= =hAgr -END PGP SIGNATURE End Message ---
Bug#1037171: marked as done (aide: fresh aide package install fails to add the requried _aide user to system)
Your message dated Wed, 14 Jun 2023 15:18:54 + with message-id and subject line Bug#1037171: fixed in aide 0.18.3-2 has caused the Debian Bug report #1037171, regarding aide: fresh aide package install fails to add the requried _aide user to system 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.) -- 1037171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: aide Version: 0.18.3-1 Severity: serious Justification: 5.d Dear Maintainer, A fresh aide package install on debina buster fails to add the requried _aide user to system. This block the ability to run 'aideinit' script. While this is mentioned in /usr/share/doc/aide-common/README.Debian.gz there are no clear instrucntions as to whar range of UID/GID to give the _aide user when cerating them manually. Pleas resolve as this blocks upgarde on most of my systems as I use aide across all of them. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages aide depends on: ii libacl1 2.3.1-3 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libcap2 1:2.66-4 ii libext2fs21.47.0-2 ii libmhash2 0.9.9.9-9 ii libpcre2-8-0 10.42-1 ii libselinux1 3.4-1+b6 ii zlib1g1:1.2.13.dfsg-1 Versions of packages aide recommends: ii aide-common 0.18.3-1 Versions of packages aide suggests: pn figlet -- no debconf information --- End Message --- --- Begin Message --- Source: aide Source-Version: 0.18.3-2 Done: Marc Haber We believe that the bug you reported is fixed in the latest version of aide, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Haber (supplier of updated aide 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, 14 Jun 2023 16:48:04 +0200 Source: aide Architecture: source Version: 0.18.3-2 Distribution: unstable Urgency: medium Maintainer: Aide Maintainers Changed-By: Marc Haber Closes: 1037171 1037436 Changes: aide (0.18.3-2) unstable; urgency=medium . * improve 31_aide_atop rule * call dh_installsysusers manually in debian/rules Thanks to Tomasz Ciolek (Closes: #1037171) * Fix handling of extended attributes on symlinks. (Closes: #1037436) Checksums-Sha1: 6a5314b58033d46a94d1797753dc529d992b73d3 2579 aide_0.18.3-2.dsc b0dfda1f3917973dae9e750939c06b00b398f004 108084 aide_0.18.3-2.debian.tar.xz 7ba41950401bad0de82867c43d601d6b4afb452e 6597 aide_0.18.3-2_source.buildinfo Checksums-Sha256: 570d2ad75dc06a04e0d6b116cb7569b8dfed083765a07e2ee4556e331c55184c 2579 aide_0.18.3-2.dsc 86401bcbed3d641d796d6b82e9a4e832e52fd5ffe67d0f4882e2a44934f356dc 108084 aide_0.18.3-2.debian.tar.xz f4b81d3a9d8b5a0953d78c1f7dd7c82303cb1fcbae8b5604fad13632378dd994 6597 aide_0.18.3-2_source.buildinfo Files: 3fdbd356c0d39f386a7b81e6ba9e1ccd 2579 admin optional aide_0.18.3-2.dsc daf26d959ea0d8959b7baa0503afde1c 108084 admin optional aide_0.18.3-2.debian.tar.xz 11e957852ae8f61b674f7309ab02b8b6 6597 admin optional aide_0.18.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmSJ1aoACgkQj3cgEwEy BEJEog//XkGntXQvUVZ5mjAlF+Nl5C+thgQnH5SJeiUeI5RYc1sjWkS2slePIqHH pQpaq4bgAQgtDNie7wzNYW/KksonYBQrWwSjfMzbtYg6FUYWU3qY9aS398KiJe4V hZ5KdOwOzmmBYRI6Ewgfy+0ktnCWarXWdiPB5vuMZkzWf15oCCj+sBsgCMRcKYy5 oMLgmiKdBegTvNkplD39kth0jvA6c+I1T38zWwWjrqmxBfp4ddaC8ai2m/ZO5E/x S9UfRzGNP3djqKspk6WjbfH1YjGA6ReiEaEgNNfACAtB9a1md45M7ztfZAns3d6f fJSi8DdTD4BHBSxsbwqtqi+inKY0ai8JxR1UCuiUsG6JHtqypL8GuVG1vgT7gqNr quxWg27xPf0PBKwVUU8NIL4gO+kQOaqwIf1hG4T2dsTsracox9/Pgj2QXuK/rghE cwIz5Frwi8ZmSqsk4G62NUShlBfY6dDGo3yNwM3+UR9IXpveZhUW/6npzPyG/dzV
Bug#1037171: marked as pending in aide
Control: tag -1 pending Hello, Bug #1037171 in aide reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/aide/-/commit/45048312727f711753e7cc7eb54f6b973c0d3a39 call dh_installsysusers manually in debian/rules Thanks: Tomasz Ciolek Closes: #1037171 dh_installsysusers is not called in the normal dh calling sequence in dh compat level 13. This resulted in the account not being created in new installs and probably also during upgrades from bullseye. Thix fixes the issue by calling dh_installsysusers explicitly in override_dh_auto_install. (this message was generated automatically) -- Greetings https://bugs.debian.org/1037171
Processed: Bug#1037171 marked as pending in aide
Processing control commands: > tag -1 pending Bug #1037171 [aide] aide: fresh aide package install fails to add the requried _aide user to system Added tag(s) pending. -- 1037171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037926: Bug 1037926
This is on me. Wike needs indeed libadwaita 1.3; I had the version from experimental installed on my machine. This should get sorted out once libadwaita 1.3 lands in trixie. regards, --- Matthias Geiger (werdahias) -BEGIN PGP PUBLIC KEY BLOCK- mQINBGJGNsQBEADCVylaCtYtBQW4NmDrZOIizSrVlv5ZJ5WJ128MAblWk3fRFPya Cs/klkTT58ehBSr61sXVP+NpkF7MWOBu2CNg66U40a/Eb+v4poxNaIjXKvQtf51S y5yGwmTc7IJg8HuohT7K3/pcsEt0jvYSwvvDFUIz5WdOR5RmB7WkDRGh8Zaior3z tzx6AKhx/aXmAc/i4BDavDxZeFC0d79H3S1+TvFsvhyIZXIFTB0sTzWreZZxSOjk Mz6xxgWGdc27lsbZbKU7N+c+GnWrRlTjimU1AfPLJQgehIejR9pSyZ2Y5BAqB7Qr f8Tvc8jc1kDx473sUUla6ELEuJMIISK1qam/B7buxZ1r/ngWRiQsqAHznm7OYk69 ttXBeHxS1b+HrcJMWfROkzsTuG6G//axMCb6x0MuyOgLXk87aDnDx1fPn62R+tq7 T4JvW51TSnlNNh75zA+8w3UzDHy2By0H6NSfiLerNnF7LGCXk7AiwQsaplrEjo/1 /4NraAqy1eO69SyozSiRuuA5KemlyPwJokpp2HMJX3cry2J7lV0+wnaaorQzz5Fi 7gRRlqXrOGwEcEG6i62VbIv2VW3Zy+qjaD3HRWXfKXXjpXske41Trv2qPI2/kGtJ TRWSWdTQ42oYOaEg/KUh0GnEoZerj50JC1qGmwElKYgd+2XQ8qR7uIB5qQARAQAB tDFNYXR0aGlhcyBHZWlnZXIgPG1hdHRoaWFzLmdlaWdlcjEwMjRAdHV0YW5vdGEu ZGU+iQJUBBMBCgA+FiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmJGNsQCGwMFCQPC ZwAFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQGL0QaztsVHVMxQ/+M5JEQ5wk DDblHGUlK8IBnPM5peuDrMdQAsOQ5nSv90gl4z4HkRgomS70xMpvoS+g/8hPym4G PXpSFJsZWjFevACWMzZO84pqJhPaFnmjh3utkkiblNf8Wi350K+luAlRvT1FVD6i HM6kOxU0P9t9+PU38FH299oRw2qEqDw5Wx+Hrnp4gaGv1mssvAMiXeaaPGx4KSz8 sNXADHJDo78U6RGJM/rSng/8M7zd3c6E8MIH958mlWjUb8T10AZ/otH3nFSRIfds 5MdnnrsKAK3DMW4RanRWHPvTsICDDkuRvigd32waQRdZeA3dNbPxM6tKDL9GEH8Q AnkShJ7VmTXP9CV20vj15mleoeDMgqhX5KEOsc3DMnKcVqdb9CzHj6jNSFUverk1 bBNaJpIiWwtwjueR4Hgdof80AAgRin4YnWaOaPTSusrKyN8dCRVcRIbauVooWLil q2OrWftDVmmNciwoHr5/WDPNgkv9DAgY+DX8Y8LMWAkXgpB0KniiQaLzrW34zjnP ALTLTIvNid6YX8KOY6KhAVWfVdMC5j6GEGfbfyMLz63YPxA9Q1Af6oXS8MbdHyBw JV8ns2xm5fD2vZVw6JI1e8AMMDjH2fAqmH23MG0fN0zd2NUToHmvhX9APSzJIbET doFPn/mI/az4Oh24WHf3Ozr+XEDyWcyy1y+5Ag0EYkY2xAEQANL26Ixtq1QMUM+5 MHl2FK4foRODoKHe4ZzdOAumUBPJE/pxGVlVxCqzC+LUeFvA8LTYCt1B60yRveYR 4mmPTA7nAerG2m4aQPeIfzz6HXWkiu9mzgxqjhPxitiMR5f1du1rAWGPZxSkhdW6 fDWT4PkHoY78jbQXWYEnV85rwtZIZIduHGKWzyxln3qjrefmB04QkPJ2BDOsRTtD YeNddHAvcgZtyepqZka9lpowQTY6TXwM8uYArEa7Hll/4r9rcvkVQUxf8jqYpZ3v PLSzvvaDouH7WAg5nUaTeWAQdSq108rNRSTgScLZWjwmhFBA46RneRpij2OJ0lW4 QqFTlldjWXzgGj6u4nbXrSERGaPwyLGIkHoKbnTAm7791d/Y5UQImuPb1tIg5Pf7 OhtyWw3bstVDa5MvIUuGpi5yKPirhrtAfdZ3H2/HR814JuL2BYdjyCuR/Sj/lZTx +gJ0bm+Llr0KZDhjKMeWaqVqsD4bybgEe4d3zE4sj9GZ0tNUvXfPaRGY6tgh9sgT Iy28vnyYpFX+oSIZXRreDpfzyjDhvNbB+AFsPN5OXqaBpmu/378T5nRpUj/qbqEZ EsloCbAmgHfvIysQWYdJ+63S3ZqpbEQRa4Y7DeybaLi8xTMfdWa19T7vQY3mVWn5 ZooycK4fkbedu19+5l8zfhR7oWyBABEBAAGJAjwEGAEKACYWIQTC4abL/ezlEaik F20YvRBrO2xUdQUCYkY2xAIbDAUJA8JnAAAKCRAYvRBrO2xUdRuPD/4tdAf8nxsA upo5O99E4AS59OTXPQuVgt1U2Z7ssDvZ3O6qbZvIBWQ0NqnCsprCt71M6cWC2dkq WUs3oRRu4IzuB4LErcTr597k+iltJ60rhDL/hxSumToH6FSX1w8EWJVg3xgP4U39 HSx6QOlZ3bTgd9dS5S46jOptIYzX5wYkNzyMj1hbmTg0lVyMtWjqfCLNmF3EzGGC BLR3tMOxZURrxx8tL48iJlFyxJG3XahoyxDSNepo5HZ+AUnNq2TJPoPJQfb1/GB/ /LycKSXWgblyWuGRlgoCE1JcdwuRM5hI2xugZQrhgZaPUBch1MSoiIqwgR1A8NPL iypUPnwG4vEaVbMtem7OUghsx+fYwuGq0T7/ezjyVRv86U2gU1bmbxojct1AXSCT FCCR3Y8QAHV9o8U/eZ1XzcEZsXFd6siO5nEBl9HaTHh5gWDrk/molP85S7Y9JIBP wZygBjWOPCCkFlIuiPQlXsJezVu93ydz7uCNIJfHv30oVedcYHN1Wr7B/1j8wXMy wqW4Nw54yZ8zaJIo01Khym6cFFVXoAUZa+5QRvSmjnm1Go+ZwZA9i7zo/6LLSpeR 04+4a1Daysk0fTf+DscrxQbUBZX17e1n/EtLS8/pp+Xb/k1JK1iiNcdpfLJ7RNik GX00szhWs5riRMzIibFDsE/FyYVNX2VHQg== =onWA -END PGP PUBLIC KEY BLOCK-
Bug#1037926: wike: version 2.0.1-2 failed to start
On Wed, Jun 14, 2023 at 8:33 AM Ernesto Domato wrote: > Package: wike > Version: 2.0.1-2 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: edo...@gmail.com > > Hi, after upgrading the package from wike:amd64 1.8.2-1 -> 2.0.1-2 it doesn't > work anymore. > > Starting it from a terminal throws the error: > > - > (wike:456499): Gtk-CRITICAL **: 09:14:42.409: Error building template class > 'Window' for an instance of type 'Window': .:0:0 Invalid object type > 'AdwTabOverview' > Traceback (most recent call last): > File "/usr/share/wike/wike/application.py", line 105, in do_activate > self._window = Window(self, self._launch_uri) >^^ > File "/usr/share/wike/wike/window.py", line 57, in __init__ > tabpage = self.tabview.append(self.page) > ^^^ > AttributeError: 'NoneType' object has no attribute 'append' > - > > And hangs there, you need to kill the process. > > Downgrading back to 1.8.2-1 using snapshot.debian.org make it work again so > the > problem is with the new version or some dependency. I'm not used to Python, > but > seems to try to use a class that doesn't exists in the new version of some > dependency?. > > Thanks for all and let me know if you need anything else to help solving this > issue. > Ernesto > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) > Kernel taint flags: TAINT_WARN > Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), > LANGUAGE=es_AR:es > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages wike depends on: > ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 > ii gir1.2-adw-1 1.2.4-1 > ii gir1.2-webkit-6.02.40.2-1 > ii python3 3.11.2-1+b1 > ii python3-requests 2.28.1+dfsg-1 Maybe the new version of wike needs libadwaita 1.3? Thank you, Jeremy Bícha
Bug#1037926: flatpak version works fine
Just a little comment, Flatpak version 2.0.1 works fine, I didn't do the analyze of dependencies versions used in there so I can't tell what's the difference is with Debian version. Greetings. Ernesto
Processed: Re: [Pkg-nagios-devel] Bug#1037925: icingacli: Icinga is not compatible with php8.2
Processing control commands: > severity -1 important Bug #1037925 [icingacli] icingacli: Icinga is not compatible with php8.2 Severity set to 'important' from 'grave' -- 1037925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037925: [Pkg-nagios-devel] Bug#1037925: icingacli: Icinga is not compatible with php8.2
Control: severity -1 important On 6/14/23 14:19, Frederic Danel wrote: Icingacli module enable --> crash with deprecated print. Making impossible to use module if you start from scratch, or if you'r comming from bullseye and want to enable a new custom module. I cannot reproduce the crash. icingacli just shows a bunch of deprecation warning that were not caught while testing the php8.2 compatibility. Also icingaweb2 print a lot of deprecated print on the website. I also cannot reproduce this. Only the downtime form shows deprecation warnings which were likewise missed while testing the php8.2 compatibility. Also Bullseye --> Bookworm migration shutdown mariadb before migrating sql. The package upgrade doesn't touch the database, you need to apply the schema changes yourself. https://icinga.com/docs/icinga-2/latest/doc/16-upgrading-icinga-2/ https://icinga.com/docs/icinga-web/latest/doc/80-Upgrading/ Probably other issues, solution for now is to use php8.1 package from sury repo. You need check your environment for third party packages or icingaweb2-module packages maintained outside the Nagios team, I have only patched the packages maintained in the team fix the php8.2 deprecations encountered while testing. issue for php8.2 : https://github.com/Icinga/icingaweb2/issues/4918 I forwarded all the changes for php8.2 applied to the packages in Debian to that issue. If they didn't have a CLA they could be forwarded as PRs. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1037928: libmsgpack-c-dev: missing Breaks+Replaces: libmsgpack-dev (<< 6)
Package: libmsgpack-c-dev Version: 6.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../libmsgpack-c-dev_6.0.0-1_amd64.deb ... Unpacking libmsgpack-c-dev:amd64 (6.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libmsgpack-c-dev_6.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/include/msgpack/fbuffer.h', which is also in package libmsgpack-dev:amd64 4.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/libmsgpack-c-dev_6.0.0-1_amd64.deb cheers, Andreas libmsgpack-dev=4.0.0-3_libmsgpack-c-dev=6.0.0-1.log.gz Description: application/gzip
Bug#1037926: wike: version 2.0.1-2 failed to start
Package: wike Version: 2.0.1-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: edo...@gmail.com Hi, after upgrading the package from wike:amd64 1.8.2-1 -> 2.0.1-2 it doesn't work anymore. Starting it from a terminal throws the error: - (wike:456499): Gtk-CRITICAL **: 09:14:42.409: Error building template class 'Window' for an instance of type 'Window': .:0:0 Invalid object type 'AdwTabOverview' Traceback (most recent call last): File "/usr/share/wike/wike/application.py", line 105, in do_activate self._window = Window(self, self._launch_uri) ^^ File "/usr/share/wike/wike/window.py", line 57, in __init__ tabpage = self.tabview.append(self.page) ^^^ AttributeError: 'NoneType' object has no attribute 'append' - And hangs there, you need to kill the process. Downgrading back to 1.8.2-1 using snapshot.debian.org make it work again so the problem is with the new version or some dependency. I'm not used to Python, but seems to try to use a class that doesn't exists in the new version of some dependency?. Thanks for all and let me know if you need anything else to help solving this issue. Ernesto -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wike depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gir1.2-adw-1 1.2.4-1 ii gir1.2-webkit-6.02.40.2-1 ii python3 3.11.2-1+b1 ii python3-requests 2.28.1+dfsg-1 wike recommends no packages. wike suggests no packages. -- no debconf information
Bug#1037915: linux-image-6.1.0-9-amd64: Known kernel issue makes Debian 12 unusable for Android firmware builds
#1024149 seems to be about the contents of the area returned by mmap, and so doesn't seem related.#1036755 looks a very similar, but whether they're similar symptoms with different, or the same, root cause seems difficult to determine.I have a spare Android build machine I can leave on Debian 12 + sid if it would help test any resolution.On 14 Jun 2023, at 11:40, Diederik de Haas wrote:On Wednesday, 14 June 2023 11:40:55 CEST Al Sutton wrote:Debain 12 has been released with a known bug which causes Android firmwarebuilds to fail (https://lkml.org/lkml/2023/3/2/797) which makes bookworkunusable for the Android firmware community.Is this possibly the same issue as reported in #1036755 or #1024149 ?For ppl preferring 'lore' links, start of the discussion is here:https://lore.kernel.org/all/cb8dc31a-fef2-1d09-f133-e9f7b9f9e...@sony.com/
Bug#1037925: icingacli: Icinga is not compatible with php8.2
Package: icingacli Version: 2.11.4-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: frederic.da...@boxis.ch Dear Maintainer, Icingacli module enable --> crash with deprecated print. Making impossible to use module if you start from scratch, or if you'r comming from bullseye and want to enable a new custom module. Also icingaweb2 print a lot of deprecated print on the website. Also Bullseye --> Bookworm migration shutdown mariadb before migrating sql. Probably other issues, solution for now is to use php8.1 package from sury repo. issue for php8.2 : https://github.com/Icinga/icingaweb2/issues/4918 Best regards. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-cloud-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.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 icingacli depends on: ii adduser3.134 ii icingaweb2-common 2.11.4-2 Versions of packages icingacli recommends: ii php8.2-cli [php-cli] 8.2.7-1~deb12u1 Versions of packages icingacli suggests: ii icingaweb2-module-monitoring 2.11.4-2 -- no debconf information
Bug#1037924: systemd-dev: missing Breaks+Replaces: udev (<< 253-2~)
On Wed, 14 Jun 2023 13:36:19 +0200 Andreas Beckmann wrote: > Package: systemd-dev > Version: 253-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. D'oh, forgot about it, fix is queued in git. We'll move this to unstable soon enough, so it will be uploaded as part of that. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1037924: systemd-dev: missing Breaks+Replaces: udev (<< 253-2~)
Package: systemd-dev Version: 253-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../systemd-dev_253-2_all.deb ... Unpacking systemd-dev (253-2) ... dpkg: error processing archive /var/cache/apt/archives/systemd-dev_253-2_all.deb (--unpack): trying to overwrite '/usr/share/pkgconfig/udev.pc', which is also in package udev 252.11-1 Errors were encountered while processing: /var/cache/apt/archives/systemd-dev_253-2_all.deb cheers, Andreas udev=252.11-1_systemd-dev=253-2.log.gz Description: application/gzip
Bug#1037541: libguestfs: FTBFS: supermin: error: lstat: Value too large for defined data type: /var/tmp/supermin2b73c8.tmpdir/base.d/init
[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037541] I think what's happening here is we are using the 31/32 bit lstat functions in OCaml: https://github.com/ocaml/ocaml/blob/3d50c168062e9fdbacf739a73738b10108ff3628/otherlibs/unix/unix.mli#L500 (I guess st_size which is signed 31 bits on armv7, but 63 bits on 64 bit platforms). We ought to be using the 64 bit version instead: https://github.com/ocaml/ocaml/blob/3d50c168062e9fdbacf739a73738b10108ff3628/otherlibs/unix/unix.mli#L544 The specific problem will be that the size of some file has grown larger than 1GB resulting in this runtime error, although that seems unusual. Now we *ought* to be using those functions already because we should always be doing: open Unix open Unix.LargeFile to use the "LargeFile" (64 bit) versions of the functions. I had a quick look through the code to see where we are using 'open Unix' without 'open Unix.LargeFile' but I couldn't find the place, leaving me confused. (Of course the other problem is that Fedora has abandoned all 32 bit platforms long ago so we never test this ...) Practically my recommendation is to exclude the whole virt stack on armv7 since it has been years since we tested it. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org
Processed: Re: sylpheed: replying to an email you sent doesn't set account accordingly
Processing control commands: > tags -1 +unreproducible Bug #1036424 [sylpheed] sylpheed: replying to an email you sent doesn't set account accordingly Added tag(s) unreproducible. -- 1036424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036424: sylpheed: replying to an email you sent doesn't set account accordingly
control: tags -1 +unreproducible Hi, As I wrote in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036388, please describe your environment and reproducible way step by step. -- Hideki Yamane
Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received
Hi, Please describe reproduce way step by step, and describe your environment at detail. I cannot see such issue until now. On Sat, 20 May 2023 12:00:16 +0200 =?ISO-8859-1?Q?Jos=E9?= Luis =?ISO-8859-1?Q?Gonz=E1lez?= wrote: > If a new mail arrives to an account other than the current one it is > changed without permission nor warning to the one receiving the email, > which means all activity from then on is done unadvertingly on the > switched-to account. > > Considering the consequences of sending email from an account different > from the one intended, like sending from a private one to a public > forum (like a mailing list available on the web, or the DBTS), or using > an account that is not permitted for what was unwantedly done, this > makes the package mostly unusable since the consequences of can't be > usually undone and can be very grave, which renders the program > unusable for any serious user. > > -- Hideki Yamane
Bug#1037920: python-django: FTBFS due to test failures (ValueError: '::1:2::3' does not appear to be an IPv4 or IPv6 address)
Source: python-django
Version: 3:3.2.19-1
Severity: serious
Tags: upstream ftbfs
Dear Maintainer,
Your package FTBFS in unstable due to test failures:
==
ERROR: test_validators (validators.tests.TestValidators.test_validators)
[URLValidator] (value='http://[::1:2::3]:8080/')
--
Traceback (most recent call last):
File "/usr/lib/python3.11/unittest/case.py", line 57, in testPartExecutor
yield
File "/usr/lib/python3.11/unittest/case.py", line 538, in subTest
yield
File "/build/python-django-3.2.19/tests/validators/tests.py", line 354, in
test_validators
validator(value)
File "/build/python-django-3.2.19/django/core/validators.py", line 132, in
__call__
host_match = re.search(r'^\[(.+)\](?::\d{2,5})?$', urlsplit(value).netloc)
^
File "/usr/lib/python3.11/urllib/parse.py", line 500, in urlsplit
_check_bracketed_host(bracketed_host)
^
File "/usr/lib/python3.11/urllib/parse.py", line 446, in
_check_bracketed_host
ip = ipaddress.ip_address(hostname) # Throws Value Error if not IPv6 or
IPv4
^
File "/usr/lib/python3.11/ipaddress.py", line 54, in ip_address
raise ValueError(f'{address!r} does not appear to be an IPv4 or IPv6
address')
^
ValueError: '::1:2::3' does not appear to be an IPv4 or IPv6 address
==
ERROR: test_value_placeholder_with_char_field
(forms_tests.tests.test_validators.ValidatorCustomMessageTests.test_value_placeholder_with_char_field)
[URLValidator] (value='http://[::1:2::3]/')
--
Traceback (most recent call last):
File "/usr/lib/python3.11/unittest/case.py", line 57, in testPartExecutor
yield
File "/usr/lib/python3.11/unittest/case.py", line 538, in subTest
yield
File
"/build/python-django-3.2.19/tests/forms_tests/tests/test_validators.py", line
108, in test_value_placeholder_with_char_field
self.assertIs(form.is_valid(), False)
^
File "/build/python-django-3.2.19/django/forms/forms.py", line 175, in
is_valid
return self.is_bound and not self.errors
^
File "/build/python-django-3.2.19/django/forms/forms.py", line 170, in errors
self.full_clean()
File "/build/python-django-3.2.19/django/forms/forms.py", line 372, in
full_clean
self._clean_fields()
^
File "/build/python-django-3.2.19/django/forms/forms.py", line 390, in
_clean_fields
value = field.clean(value)
^
File "/build/python-django-3.2.19/django/forms/fields.py", line 151, in clean
self.run_validators(value)
^
File "/build/python-django-3.2.19/django/forms/fields.py", line 136, in
run_validators
v(value)
File "/build/python-django-3.2.19/django/core/validators.py", line 132, in
__call__
host_match = re.search(r'^\[(.+)\](?::\d{2,5})?$', urlsplit(value).netloc)
^
File "/usr/lib/python3.11/urllib/parse.py", line 500, in urlsplit
_check_bracketed_host(bracketed_host)
^
File "/usr/lib/python3.11/urllib/parse.py", line 446, in
_check_bracketed_host
ip = ipaddress.ip_address(hostname) # Throws Value Error if not IPv6 or
IPv4
^
File "/usr/lib/python3.11/ipaddress.py", line 54, in ip_address
raise ValueError(f'{address!r} does not appear to be an IPv4 or IPv6
address')
^
ValueError: '::1:2::3' does not appear to be an IPv4 or IPv6 address
--
Ran 14681 tests in 310.476s
FAILED (errors=2, skipped=1141, expected failures=4)
Kind Regards,
Bas
Bug#1037915: linux-image-6.1.0-9-amd64: Known kernel issue makes Debian 12 unusable for Android firmware builds
On Wednesday, 14 June 2023 11:40:55 CEST Al Sutton wrote: > Debain 12 has been released with a known bug which causes Android firmware > builds to fail (https://lkml.org/lkml/2023/3/2/797) which makes bookwork > unusable for the Android firmware community. Is this possibly the same issue as reported in #1036755 or #1024149 ? For ppl preferring 'lore' links, start of the discussion is here: https://lore.kernel.org/all/cb8dc31a-fef2-1d09-f133-e9f7b9f9e...@sony.com/ signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1037915: linux-image-6.1.0-9-amd64: Known kernel issue makes Debian 12 unusable for Android firmware builds
Processing control commands:
> forcemerge 1036755 -1
Bug #1036755 {Done: Salvatore Bonaccorso } [src:linux]
linux: 6.1.26 <= x < 6.1.30 breaks applications using mmap(MAP_32BIT)
Bug #1037041 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-6.1.0-9-amd64: Spurious failures from mmap(MAP_32BIT)
Bug #1037915 [src:linux] linux-image-6.1.0-9-amd64: Known kernel issue makes
Debian 12 unusable for Android firmware builds
Set Bug forwarded-to-address to
'https://lore.kernel.org/linux-mm/32f156ba80010fd97dbaf0a0cdfc84366608624d.ca...@intel.com/
https://lore.kernel.org/linux-mm/e6108286ac025c268964a7ead3aab9899f9bc6e9.ca...@spotco.us/'.
Severity set to 'critical' from 'important'
Marked Bug as done
Added indication that 1037915 affects ganeti
Marked as fixed in versions linux/6.3.4-1~exp1.
Marked as found in versions linux/6.3.1-1~exp1.
Added tag(s) upstream, confirmed, and fixed-upstream.
Bug #1037041 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-6.1.0-9-amd64: Spurious failures from mmap(MAP_32BIT)
Merged 1036755 1037041 1037915
--
1036755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036755
1037041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037041
1037915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server
Source: gnutls28 Version: 3.8.0+git20230529-1 Severity: serious Hi, after building gnutls28/experimental with pbuilder, there are a lot of gnutls-serv and a few openssl s_server processes running, preventing pbuilder to cleanup the chroot. Andreas
Bug#1037547: rpmdb
The fapolicyd.conf file contains trust = rpmdb,file Since debian doesn't, by default, have an rpm database. Even when you install rpm on debian the database doesn't include most OS executables.
Processed: Re: Bug#1037535: libnet-twitter-perl: "Could not authenticate you." errors since 2023-06-13
Processing control commands: > retitle -1 libnet-twitter-perl: Does not support Twitter API v2 Bug #1037535 [libnet-twitter-perl] libnet-twitter-perl: "Could not authenticate you." errors since 2023-06-13 Changed Bug title to 'libnet-twitter-perl: Does not support Twitter API v2' from 'libnet-twitter-perl: "Could not authenticate you." errors since 2023-06-13'. > severity -1 important Bug #1037535 [libnet-twitter-perl] libnet-twitter-perl: Does not support Twitter API v2 Severity set to 'important' from 'grave' > found -1 4.01043-1 Bug #1037535 [libnet-twitter-perl] libnet-twitter-perl: Does not support Twitter API v2 Marked as found in versions libnet-twitter-perl/4.01043-1. > clone -1 -2 Bug #1037535 [libnet-twitter-perl] libnet-twitter-perl: Does not support Twitter API v2 Bug 1037535 cloned as bug 1037561 > reassign -2 libnet-twitter-lite-perl Bug #1037561 [libnet-twitter-perl] libnet-twitter-perl: Does not support Twitter API v2 Bug reassigned from package 'libnet-twitter-perl' to 'libnet-twitter-lite-perl'. No longer marked as found in versions libnet-twitter-perl/4.01043-2 and libnet-twitter-perl/4.01043-1. Ignoring request to alter fixed versions of bug #1037561 to the same values previously set > retitle -2 libnet-twitter-lite-perl: Does not support Twitter API v2 Bug #1037561 [libnet-twitter-lite-perl] libnet-twitter-perl: Does not support Twitter API v2 Changed Bug title to 'libnet-twitter-lite-perl: Does not support Twitter API v2' from 'libnet-twitter-perl: Does not support Twitter API v2'. > found -2 0.12008-1 Bug #1037561 [libnet-twitter-lite-perl] libnet-twitter-lite-perl: Does not support Twitter API v2 Marked as found in versions libnet-twitter-lite-perl/0.12008-1. -- 1037535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037535 1037561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037535: libnet-twitter-perl: "Could not authenticate you." errors since 2023-06-13
Control: retitle -1 libnet-twitter-perl: Does not support Twitter API v2
Control: severity -1 important
Control: found -1 4.01043-1
Control: clone -1 -2
Control: reassign -2 libnet-twitter-lite-perl
Control: retitle -2 libnet-twitter-lite-perl: Does not support Twitter API v2
Control: found -2 0.12008-1
On Tue, 13 Jun 2023 23:54:23 +0200, Vincent Lefevre wrote:
> On 2023-06-13 23:18:47 +0200, Vincent Lefevre wrote:
> > It seems that something changed on Twitter, which yields the
> > "Could not authenticate you." error with Net::Twitter. This
> > started to happen a few hours ago.
Funny coincidence: I also had an "app" suspended yesterday and hit
the same issue (with clients in perl, python, and C).
> I think that's it:
> https://twitter.com/TwitterDev/status/1621026986784337922
> "Starting February 9, we will no longer support free access to the
> Twitter API, both v2 and v1.1. A paid basic tier will be available
> instead"
Which is also not true anymore, AFAIK. My current understanding is:
- Twitter is over time suspending old "apps" (happened to me already
earlier this year, and again yesterday).
- It's possible to create a "project" and move the old "app" there,
thereby reactivating it -- but by the new rules:
* There are paid and unpaid plans with different features.
* Twitter API v1.1 is quite limited (for all plans).
Cf.
https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api
So the problem is not that Net::Twitter and Net::Twitter::Lite are
broken per se but that they don't support the Twitter API v2 which is
a pain as the API v1.1 is very limited by now (except for still
working old "apps") -- but I can confirm that uploading images with
Net::Twitter::Lite still works.
Apparently Twitter::API has some support for the Twitter API v2 [0]
which I still have to try.
Cheers,
gregor
[0]
https://metacpan.org/pod/Twitter::API
#v+
my $client = Twitter::API->new_with_traits(
api_version => '2',
api_ext => '',
%oauth_credentials,
);
my $user = $client->get("users/by/username/$username");
#v-
--
.''`. 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
`- BOFH excuse #189: SCSI's too wide.
Bug#1037541: libguestfs: FTBFS: supermin: error: lstat: Value too large for defined data type: /var/tmp/supermin2b73c8.tmpdir/base.d/init
* Sebastian Ramacher: > Source: libguestfs > Version: 1:1.50.1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org … and it also fails to build on armhf. Likely a 32bit-arch-specific issue. My guess is that somewhere within supermin, off_t is still at a 32bit value and the filesystem image generated during the tests is larger than that. Cheers, -Hilko
Processed: Bug#1030129 marked as pending in ca-certificates-java
Processing control commands: > tag -1 pending Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install: Error loading java.security file Added tag(s) pending. -- 1030129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030129: marked as pending in ca-certificates-java
Control: tag -1 pending Hello, Bug #1030129 in ca-certificates-java 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/java-team/ca-certificates-java/-/commit/8c64d971b85d3d46120804b6ccee29dd97595fd7 [ Vladimir Petko ] * Resolve circular JRE dependency (LP: #2003750, LP: #1999103, LP: #2004061) Closes: #1030129, #1037478, #1023748. - debian/ca-certificates-java.postinst: remove setup_path from "configure" stage. - debian/ca-certificates-java.postinst: do "fresh" update if cacerts file is not found. Certificates are refreshed only in response to the trigger activated by OpenJDK packages. - debian/ca-certificates-java.postinst: fix cacert enumeration command for Java 8. Closes: #1015771. - debian/control: remove JRE dependency. - debian/control: add Breaks condition. - debian/tests: add smoke tests. - debian/ca-certificates-java.triggers: remove file trigger /usr/jvm, explicitly declare triggers as -await. (this message was generated automatically) -- Greetings https://bugs.debian.org/1030129
Bug#1037547: More info
pilgrim:/etc/fapolicyd/rules.d# ls 90-deny-execute.rules pilgrim:/etc/fapolicyd/rules.d# cat 90-deny-execute.rules # Deny execution for anything untrusted deny_audit perm=execute all : all pilgrim:/etc/fapolicyd# cat fapolicyd.conf # # This file controls the configuration of the file access policy daemon. # See the fapolicyd.conf man page for explanation. # permissive = 0 nice_val = 14 q_size = 640 uid = fapolicyd gid = fapolicyd do_stat_report = 1 detailed_report = 1 db_max_size = 50 subj_cache_size = 1549 obj_cache_size = 8191 watch_fs = ext2,ext3,ext4,tmpfs,xfs,vfat,iso9660,btrfs trust = rpmdb,file integrity = none syslog_format = rule,dec,perm,auid,pid,exe,:,path,ftype,trust rpm_sha256_only = 0 allow_filesystem_mark = 0 Looks like the shipped policy is to deny all execute and with permissive=0 this is enforced.
Processed: severity of 1037548 is normal
Processing commands for cont...@bugs.debian.org: > severity 1037548 normal Bug #1037548 [qbittorrent-nox] qbittorrent-nox: web interface doesn't display content, browsers download html instead Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1037548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: For some reason reportbug only let me set this as high as important.
Processing commands for cont...@bugs.debian.org: > severity 1037547 critical Bug #1037547 [fapolicyd] fapolicyd: Installation of fapolicyd via apt caused everything to immediately become non-executable. Severity set to 'critical' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1037547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037548: qbittorrent-nox: web interface doesn't display content, browsers download html instead
1037548 severity normal 1037548 tags unreproducible thanks On 13 juin 2023 19:26, allan grossman wrote: > Package: qbittorrent-nox > Version: 4.5.3-2 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: wizard10...@gmail.com [...] > * What was the outcome of this action? > > No change. Browsers still download html code instead of displaying html > content. > > * What outcome did you expect instead? > > I expected the web interface to display in a browser window. Work fine for me with firefox. Maybe the problem come from your browser ? Christian
