Bug#1031892: marked as done (openjdk-21 should not be in stable releases for now)
Your message dated Tue, 13 Jun 2023 07:40:10 +0200 with message-id and subject line openjdk-21 should not be in stable releases for now has caused the Debian Bug report #1031892, regarding openjdk-21 should not be in stable releases for now 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.) -- 1031892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openjdk-21 Version: 21~7ea-1 Severity: serious openjdk-21 should not be in stable releases for now, this bug should keep it out of testing. --- End Message --- --- Begin Message --- closing, OpenJDK 21 will be another LTS release.--- End Message ---
Bug#1031892: openjdk-21 should not be in stable releases for now
closing, OpenJDK 21 will be another LTS release.
Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
Hi Andreas, On Mon, Jun 12, 2023 at 07:40:32PM +0200, Andreas Beckmann wrote: > > It's a 12 byte difference. That's not 9base's entries. What you see here > > is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it. > > Thus force-merging. > > No, it's "/usr/bin/rc\n". Huh! I stand corrected. > # cat /usr/share/debianutils/shells.d/plan9 > /bin/rc > /usr/lib/plan9/bin/rc > > If I install 9base in an unmerged-/usr sid chroot, I get > > # /etc/shells: valid login shells > /bin/sh > /bin/bash > /bin/rbash > /bin/dash > /bin/rc > /usr/lib/plan9/bin/rc > /usr/lib/plan9/bin/rc > > who is responsible for the duplicate entry? This is caused by update-shells and the code it carries to support /usr-merge. When it encounters /bin/rc, it canonicalizes it using dpkg-realpath and adds it as well. So the first duplicate is the canonicalization of /bin/rc and the second one is the actual entry. In essence, the /usr-merge implementation in update-shells assumes that any kind of symlinking for shells happens due to /usr-merge. This assumption is false and violated by the use of update-alternatives. In update-shells, we should not resolve the final link, but only directory components as those are the ones that may lead to aliasing effects. Instead of realshell=$(dirname "$(dpkg-realpath --root "$ROOT" "$line")")/$(basename "$line") we probably should have said realshell="$(dpkg-realpath --root "$ROOT" "$(dirname "$line")")/$(basename "$line")" and with that, we'd pass /bin rather than /bin/rc to dpkg-realpath and avoid resolving the alternative. > If I reconfigure usrmerge afterwards, I get > > # /etc/shells: valid login shells > /bin/sh > /bin/bash > /usr/bin/bash > /bin/rbash > /usr/bin/rbash > /bin/dash > /usr/bin/dash > /usr/bin/sh > /bin/rc > /usr/lib/plan9/bin/rc > /usr/lib/plan9/bin/rc > /usr/bin/rc > > Now we got the additional /usr/bin/rc entry 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. Thank you Andreas for your persistence on this. Helmut
Bug#973850: marked as done (lilo: Should not be included in bullseye)
Your message dated Tue, 13 Jun 2023 04:48:16 + with message-id and subject line Bug#1037326: Removed package(s) from unstable has caused the Debian Bug report #973850, regarding lilo: Should not be included in bullseye 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.) -- 973850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lilo Severity: critical Version: 1:24.2-5 I plan to orphan this package. It should not be included into next stable release (bullseye). I am maintainer and developer of lilo, but have closed development with version 24.2 in year 2016. Since this time some people wanted to overtake development, but didn't do it after all. Since some years the successor grub2 is stable enough to replace lilo. And lilo code is very old and would have to be rewritten. The popularity of lilo going down for many years (Vote: 87, Recent: 24) Because of this items, I register a RC bug on the package to ensure it stay out of bullseye. The Debian release team is informed. --- Have a nice day. Joachim (Germany) pgpc_UllCdAzF.pgp Description: Digitale Signatur von OpenPGP --- End Message --- --- Begin Message --- Version: 1:24.2-5.1+rm Dear submitter, as the package lilo 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/1037326 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#995854: marked as done (freebirth: crashes at startup)
Your message dated Tue, 13 Jun 2023 04:49:30 + with message-id and subject line Bug#1037421: Removed package(s) from unstable has caused the Debian Bug report #995854, regarding freebirth: crashes at startup 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.) -- 995854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freebirth Version: 0.3.2-9.3 Severity: normal Dear Maintainer, Starting freebirth crashes before rendering anything. I got the backtrace: #0 0x564775b71afe in init_sps (node=0x7fcfe755d1d0) at freebirth.c:158 #1 0x564775b71b65 in init_sps (node=) at freebirth.c:165 #2 init_sps (node=0x56477629a3b0) at freebirth.c:161 #3 0x564775b71b65 in init_sps (node=) at freebirth.c:165 #4 init_sps (node=0x564776293690) at freebirth.c:161 #5 0x564775b71b65 in init_sps (node=) at freebirth.c:165 #6 init_sps (node=0x56477629dd30) at freebirth.c:161 #7 0x564775b71b65 in init_sps (node=) at freebirth.c:165 #8 init_sps (node=0x5647762ebd80) at freebirth.c:161 #9 0x564775b69754 in main (argc=1, argv=0x7ffcc3c5ab08) at freebirth.c:172 Thank you. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-1-amd64 (SMP w/12 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) LSM: AppArmor: enabled Versions of packages freebirth depends on: ii alsa-oss1.1.8-1 ii freebirth-data 0.3.2-9.3 ii libc6 2.32-4 ii libglib2.0-02.70.0-1+b1 ii libgtk2.0-0 2.24.33-2 freebirth recommends no packages. freebirth suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.3.2-9.3+rm Dear submitter, as the package freebirth 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/1037421 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#1037453: libmail-dmarc-perl: FTBFS with test failures when there's no network
Package: libmail-dmarc-perl
Version: 1.20211209-4
Severity: serious
Tags: patch
Justification: Policy 4.9
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
Hi Noah,
libmail-dmarc-perl has yet to be included in an Ubuntu release because its
build-time tests depend on network access. This is a fairly reasonable
thing to want to do in this package, to validate real-world DNS entries.
However, it falls afoul of Launchpad's network policy, and is also AIUI a
violation of Policy 4.9. It also represents an external dependency for the
package, which can result in regressions in buildability if in the future
the referenced domains change their DNS settings.
I've applied the attached (very dirty) patch to libmail-dmarc-perl in
Ubuntu, which is sufficient to let the package build in Launchpad. Having
looked at some of the surrounding tests, I'm not sure this would let the
package build in a completely offline environment - I think Launchpad
provides name resolution of a limited subset of domains, so some tests which
pass in Launchpad may also fail when offline.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libmail-dmarc-perl-1.20211209/debian/patches/series
libmail-dmarc-perl-1.20211209/debian/patches/series
--- libmail-dmarc-perl-1.20211209/debian/patches/series 2023-01-28
20:45:01.0 -0800
+++ libmail-dmarc-perl-1.20211209/debian/patches/series 2023-06-12
18:30:18.0 -0700
@@ -1,2 +1,3 @@
0001-pod-Fix-missing-and-malformed-NAME-headings.patch
0005-recommend-system-psl.patch
+skip_network_tests.patch
diff -Nru libmail-dmarc-perl-1.20211209/debian/patches/skip_network_tests.patch
libmail-dmarc-perl-1.20211209/debian/patches/skip_network_tests.patch
--- libmail-dmarc-perl-1.20211209/debian/patches/skip_network_tests.patch
1969-12-31 16:00:00.0 -0800
+++ libmail-dmarc-perl-1.20211209/debian/patches/skip_network_tests.patch
2023-06-12 18:43:32.0 -0700
@@ -0,0 +1,127 @@
+Description: skip tests that depend on network access
+Author: Steve Langasek
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/2023606
+Last-Update: 2023-06-12
+Forwarded: no
+
+Index: libmail-dmarc-perl-1.20211209/t/04.PurePerl.t
+===
+--- libmail-dmarc-perl-1.20211209.orig/t/04.PurePerl.t
libmail-dmarc-perl-1.20211209/t/04.PurePerl.t
+@@ -31,20 +31,20 @@
+ isa_ok( $dmarc, 'Mail::DMARC::PurePerl' );
+
+ test_get_from_dom();
+-test_fetch_dmarc_record();
++#test_fetch_dmarc_record();
+ test_get_organizational_domain();
+-test_exists_in_dns();
++#test_exists_in_dns();
+ test_is_spf_aligned();
+ test_is_dkim_aligned();
+ test_is_aligned();
+ test_is_whitelisted();
+-test_discover_policy();
++#test_discover_policy();
+ test_validate();
+-test_has_valid_reporting_uri();
++#test_has_valid_reporting_uri();
+ test_external_report();
+-test_verify_external_reporting( 'tnpi.net','theartfarm.com', 1 );
+-test_verify_external_reporting( 'cadillac.net','theartfarm.com', 1 );
+-test_verify_external_reporting( 'mail-dmarc.tnpi.net', 'theartfarm.com', 1 );
++#test_verify_external_reporting( 'tnpi.net','theartfarm.com', 1 );
++#test_verify_external_reporting( 'cadillac.net','theartfarm.com', 1 );
++#test_verify_external_reporting( 'mail-dmarc.tnpi.net', 'theartfarm.com', 1 );
+ _test_reason();
+
+ done_testing();
+@@ -77,11 +77,8 @@
+ ]);
+
+ my $policy = $dmarc->discover_policy;
+-ok( $policy, "discover_policy" );
+ my $result = $dmarc->validate($policy);
+ ok( ref $result, "result is a ref");
+-ok( $result->{result} eq 'pass', "result=pass");
+-ok( $result->{spf} eq 'pass', "spf=pass");
+ ok( $result->{disposition} eq 'none', "disposition=none");
+
+ $result->disposition('reject');
+@@ -91,7 +88,6 @@
+ ok( $result->reason( type => 'local_policy', comment => 'testing' ),
"added reason 2" );
+ #warn Data::Dumper::Dumper($result->reason);
+
+-ok( $dmarc->save_aggregate(), "save aggregate");
+ }
+
+ sub test_verify_external_reporting {
+Index: libmail-dmarc-perl-1.20211209/t/06.Result.t
+===
+--- libmail-dmarc-perl-1.20211209.orig/t/06.Result.t
libmail-dmarc-perl-1.20211209/t/06.Result.t
+@@ -17,7 +17,7 @@
+ isa_ok( $result, 'Mail::DMARC::Result' );
+
+ my $test_dom = 'tnpi.net';
+-test_published();
++#test_published();
+ test_no_policy();
+ test_disposition();
+ test_dkim();
+@@ -203,9 +203,7 @@
+ $pp->validate();
+
+ my $skip_reason;
+-if ( !$pp->result->reason ) {# typically a DNS failure,
+-$skip_reason = "look like DNS is not working";
+-
Bug#1030129: ca-certificates-java - Fails to install with OpenJDK 21: Error loading java.security file
On 6/13/23 05:22, tony mancill wrote: I am not able to reproduce the failure in a clean unstable schroot with either openjdk-17 or openjdk-21 yet - for example: I also had trouble reproducing the issue in a sid cowbuilder chroot. This worked for me: apt install ca-certificates-java default-jdk openjdk-21-jdk Just building osmpbf also triggered the issue yesterday, but now apt build-dep osmpbf succeeds like it does for other Java packages. This suggests a race condition or apt package ordering issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1030129: ca-certificates-java - Fails to install with OpenJDK 21: Error loading java.security file
On Mon, Jun 12, 2023 at 06:55:49AM +0200, Sebastiaan Couwenberg wrote: > On Tue, 31 Jan 2023 13:56:42 +0100 Bastian Blank wrote: > > | dpkg: error processing package openjdk-21-jdk:arm64 (--configure): > > | dependency problems - leaving unconfigured > > It also fails to install with openjdk-17: > > Setting up ca-certificates-java (20230103) ... > Exception in thread "main" java.lang.InternalError: Error loading > java.security file > at java.base/java.security.Security.initialize(Security.java:106) > at java.base/java.security.Security$1.run(Security.java:84) > at java.base/java.security.Security$1.run(Security.java:82) > at > java.base/java.security.AccessController.doPrivileged(AccessController.java:318) > at java.base/java.security.Security.(Security.java:82) > at > java.base/sun.security.jca.ProviderList.(ProviderList.java:178) > at > java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96) > at > java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94) > at > java.base/java.security.AccessController.doPrivileged(AccessController.java:318) > at > java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93) > at java.base/sun.security.jca.Providers.(Providers.java:55) > at > java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156) > at > java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193) > at > org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50) > at > org.debian.security.UpdateCertificates.(UpdateCertificates.java:65) > at > org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51) I am not able to reproduce the failure in a clean unstable schroot with either openjdk-17 or openjdk-21 yet - for example: $ sudo sbuild-createchroot --no-deb-src --chroot-mode=schroot --chroot-prefix=test --include=default-jdk unstable /data/chroot/test-amd64-sbuild $ schroot -c test-amd64-sbuild -u root --directory /tmp /bin/bash (test-amd64-sbuild)root@lark:/tmp# dpkg -l | grep -E 'openjdk|ca-cert|default-jdk' ii ca-certificates 20230311 all Common CA certificates ii ca-certificates-java 20230103 all Common CA certificates (JKS keystore) ii default-jdk 2:1.17-74 amd64Standard Java or Java compatible Development Kit ii default-jdk-headless 2:1.17-74 amd64Standard Java or Java compatible Development Kit (headless) ii openjdk-17-jdk:amd64 17.0.7+7-1 amd64OpenJDK Development Kit (JDK) ii openjdk-17-jdk-headless:amd64 17.0.7+7-1 amd64OpenJDK Development Kit (JDK) (headless) ii openjdk-17-jre:amd64 17.0.7+7-1 amd64OpenJDK Java runtime, using Hotspot JIT ii openjdk-17-jre-headless:amd64 17.0.7+7-1 amd64OpenJDK Java runtime, using Hotspot JIT (headless) Maybe some environmental difference is causing the failure. Could it be that the java.security file has been modified on the systems where the failure is occurring? (Just a guess...) If so, could someone share the file from a system where the bug manifests? Thanks, tony
Bug#1037415: marked as done (librust-grep-printer-dev: impossible to install: depends on gone package librust-base64-0.13+default-dev)
Your message dated Mon, 12 Jun 2023 23:19:44 + with message-id and subject line Bug#1037415: fixed in rust-grep-printer 0.1.7-1 has caused the Debian Bug report #1037415, regarding librust-grep-printer-dev: impossible to install: depends on gone package librust-base64-0.13+default-dev 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.) -- 1037415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-grep-printer-dev Version: 0.1.6-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 librust-grep-printer-dev depends on librust-base64-0.13+default-dev which is gone. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSHKHAACgkQLHwxRsGg ASGMJRAArH4HaVhzJXG99ayt8E9iZ6NSdECmqVndJSfUFNgrjXpy7cImi394cK94 0aA3yq8MdcMYh23gJEcW975YU7cjKT8WFHKsGvkYUZ51RDbEKAJly6tGp+mMHKA6 k2MGNJNejJlyNEL7Zd62Mq3wNUD//mz4aYn75MPkF3ucgSkw3l7/rh+jHbrLwiUu mXFRt0ZJkTR93UmpNcZDYmfjmaZ6/IFQ1sOwaCjZkP4NtPBtc4W97bdBNtcypNMr WiuPtTpUDArauX/MGu4v4KiY+EZa7AYdfdzqRHXkolH3nHOrjOL8QDwWdXXjBQ2V iuoaFIrQPUHNx1l93rotFUQYCuIabszdTutIuZgRTOxCgnsmqg88JqIifqFK8RHj zf7/LdahBDP8G0VV72LgB+VrLIT4nJNZNYciATKMnMn5zh9ref1FIOlfEio0KVgJ 9NrrwD9PPujEVVTe55b0lIKd24O57qs4SF5o51skLEshAqDS7ymCL95zWv/mPC76 yOgZhdW6ttfWgmrmLLqNiCgPJ9l6ydLzprU+dHyBx1hqo3iFVsvsAoLzseZdVWAM nO7Tfo1x4cuVTb62AC0hFja05/b4HkuP6+bwVX6AHllvlKu7Uo601HUtHbFzhVmT 4htlWV+7Wp8qeE95IWZkYxWJXyXSe2xXLG8QRb1wOJGqCZL/JtE= =3JpT -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-grep-printer Source-Version: 0.1.7-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-grep-printer, 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. Peter Michael Green (supplier of updated rust-grep-printer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 Jun 2023 20:55:29 + Source: rust-grep-printer Architecture: source Version: 0.1.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1037415 Changes: rust-grep-printer (0.1.7-1) unstable; urgency=medium . * Team upload. * Package grep-printer 0.1.7 from crates.io using debcargo 2.6.0 (Closes: #1037415) * Drop timestamp workaround . [ Fabian Grünbichler ] * Bump base64 to 0.21 Checksums-Sha1: 8a63f35c8c02c273d3e3fbdc4a5c41b0fccdaec6 2754 rust-grep-printer_0.1.7-1.dsc d2117688abfabb8b2de1dce2419395d72c011abe 46958 rust-grep-printer_0.1.7.orig.tar.gz b46a61f89aeb8c635ccbe60670085e0eba69c123 3656 rust-grep-printer_0.1.7-1.debian.tar.xz 68ded30147c9f7d9beacbcb4dc899bb5eaab4219 10335 rust-grep-printer_0.1.7-1_source.buildinfo Checksums-Sha256: 4cc8e5c75b1b5d5c0203c99955ed8ffa08f7fbfd8e785fbae7bd10301fa2f55b 2754 rust-grep-printer_0.1.7-1.dsc e14551578f49da1f774b70da5bd1b8c20bbbead01620c426cb0a217536d95a6a 46958 rust-grep-printer_0.1.7.orig.tar.gz 0281cf5fc1157316046741a42508d716364c8894d9e7b14d00da381ef8d10ae8 3656 rust-grep-printer_0.1.7-1.debian.tar.xz cf644f6568f268da3c654a3317d061b38b2ac2b9643addb93286a14af0b799dc 10335 rust-grep-printer_0.1.7-1_source.buildinfo Files: 6dcf786dea2b20733fbbc11644b39cef 2754 rust optional rust-grep-printer_0.1.7-1.dsc ae39aa352c261b0d30928da62af4880b 46958 rust optional rust-grep-printer_0.1.7.orig.tar.gz 08bd99d19c0fa61079a1943b8c79b121 3656 rust optional rust-grep-printer_0.1.7-1.debian.tar.xz c24014fc77ceee93b3198def1bcebd3c 10335 rust optional rust-grep-printer_0.1.7-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmSHjDUUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsIRw//YxD734hgewtu2rYoXJFwNPiSLrWa DDmVIbOGZCSRy6ITcfmRytxtGz8YqjHvrbQWlDcWAzpiz8h8b8UFlEiNKtj62TPC oTeKBlvKwd8QyT8W7fZIeFYXmrXeMaFlaaZV9NgSdBcxyRj3TwMxHjm68V+5xpyC c2t+OvarQUROQrTxIquM4Upzleu6YFmHaWDhxj4YW30qM/4+fb/CTKJjuQ4hjo90 vmGn3IzB85LF4UVRtG/wiNffL/zTeZKTmYpImCVM9NIztnnCaLdk317Lg6EATsOc 7iBDfl0kQCgv04N
Bug#1036263: Package can be built just fine
Hi, At least as of 1.50.1-1, the pacakge builds just fine, cf. https://buildd.debian.org/status/fetch.php?pkg=guestfs-tools&arch=amd64&ver=1.50.1-1&stamp=1686585170&raw=0 Cheers, -Hilko
Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
Now I'm really confused: I start with an unmerged sid chroot, install 9base there. Then I remove /etc/unsupported-skip-usrmerge-conversion and install usrmerge. Now /etc/shells contains # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc /usr/bin/sh /usr/bin/bash /usr/bin/rbash /usr/bin/dash /usr/bin/rc and /var/lib/shells.state /bin/bash /bin/rbash /bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc Then I run update-shells which does not modify /etc/shells, but the statefile now contains /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc So the /bin entries for bash/rbash/dash get their /usr counterparts added, but /bin/rc does not. OK, back to the minimal unmerged sid chroot, without 9base this time. After installation of usrmerge and successful conversio /etc/shells contains # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /usr/bin/sh /usr/bin/bash /usr/bin/rbash /usr/bin/dash and /var/lib/shells.state contains /bin/bash /bin/rbash /bin/dash Then I delete all /usr/bin entries from /etc/shells (sed -i /usr/d /etc/shells) and run update-shells, resulting in /etc/shells containing # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /usr/bin/bash /usr/bin/rbash /usr/bin/dash (i.e. only /usr/bin/sh is missing compared to the file made by usrmerge) and the statefile contains /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash This seems to imply that usrmerge could call update-shells to perform most of the changes it does to /etc/shells. (And to update /var/lib/shells.state at the same time) ... later ... much later ... After reading update-shells several times (and still not fully getting how it works (or at least should work)), I think its behavior is not well defined in the context of alternatives as used by 9base. At least this line seems to be wrong: realshell=$(dirname "$(dpkg-realpath --root "$ROOT" "$line")")/$(basename "$line") It resolves e.g. /usr/bin/clang++-14 to non-existant /usr/lib/llvm-14/bin/clang++-14 Shouldn't that rather be realshell=$(dpkg-realpath --root "$ROOT" "$(dirname "$line")")/$(basename "$line") Andreas
Bug#983874: marked as done (gitaly: fails to install: Could not find gem 'rugged (~> 0.28)')
Your message dated Tue, 13 Jun 2023 02:01:48 +0530 with message-id <0dq5wr.yq7trji8k...@onenetbeyond.org> and subject line Re: gitaly: fails to install: Could not find gem 'rugged (~> 0.28)' has caused the Debian Bug report #983874, regarding gitaly: fails to install: Could not find gem 'rugged (~> 0.28)' 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.) -- 983874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gitaly Version: 13.4.6+dfsg1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up gitaly (13.4.6+dfsg1-2) ... [ESC][31mCould not find gem 'rugged (~> 0.28)' in any of the gem sources listed in your Gemfile.[ESC][0m dpkg: error processing package gitaly (--configure): installed gitaly package post-installation script subprocess returned error exit status 7 Processing triggers for ca-certificates (20210119) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: gitaly cheers, Andreas gitaly_13.4.6+dfsg1-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- On Tue, 02 Mar 2021 16:07:21 +0100 Andreas Beckmann wrote: > Setting up gitaly (13.4.6+dfsg1-2) ... > [ESC][31mCould not find gem 'rugged (~> 0.28)' in any of the gem sources listed in your > Gemfile.[ESC][0m Fixed long back. Closing the bug.--- End Message ---
Bug#983617: marked as done (gitaly: fails to install: Could not find gem 'grpc (~> 1.30, >= 1.30.2)')
Your message dated Tue, 13 Jun 2023 02:00:08 +0530 with message-id <8aq5wr.gtmjix63s4...@onenetbeyond.org> and subject line Re: gitaly: fails to install: Could not find gem 'grpc (~> 1.30, >= 1.30.2)' has caused the Debian Bug report #983617, regarding gitaly: fails to install: Could not find gem 'grpc (~> 1.30, >= 1.30.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.) -- 983617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gitaly Version: 13.7.5+dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up gitaly (13.7.5+dfsg-3) ... [ESC][31mCould not find gem 'grpc (~> 1.30, >= 1.30.2)' in any of the gem sources listed in your Gemfile.[ESC][0m dpkg: error processing package gitaly (--configure): installed gitaly package post-installation script subprocess returned error exit status 7 Processing triggers for ca-certificates (20210119) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: gitaly cheers, Andreas gitaly_13.7.5+dfsg-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- On Sat, 27 Feb 2021 12:03:36 +0100 Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed to install. As > per definition of the release team this makes the package too buggy for > a release, thus the severity. > > From the attached log (scroll to the bottom...): > > Setting up gitaly (13.7.5+dfsg-3) ... > [ESC][31mCould not find gem 'grpc (~> 1.30, >= 1.30.2)' in any of the gem sources listed > in your Gemfile.[ESC][0m This was fixed long back. Closing the bug.--- End Message ---
Bug#976820: marked as done (gitaly: use golang-gopkg-libgit2-git2go.v30)
Your message dated Tue, 13 Jun 2023 01:58:49 +0530 with message-id <28q5wr.zgsudifg2v...@onenetbeyond.org> and subject line Re: gitaly: use golang-gopkg-libgit2-git2go.v30 has caused the Debian Bug report #976820, regarding gitaly: use golang-gopkg-libgit2-git2go.v30 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.) -- 976820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gitaly Version: 13.3.0+dfsg-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org golang-gopkg-libgit2-git2go.v28 will be removed as part of the libgit2 transition. So please switch to golang-gopkg-libgit2-git2go.v30-dev. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Tue, 8 Dec 2020 10:55:52 +0100 Sebastian Ramacher wrote: > Source: gitaly > Version: 13.3.0+dfsg-2 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > > golang-gopkg-libgit2-git2go.v28 will be removed as part of the libgit2 > transition. So please switch to golang-gopkg-libgit2-git2go.v30-dev. This is fixed long back. Closing.--- End Message ---
Bug#1014580: marked as done (Gitaly: ... Exception: EVP_PKEY_new_mac_key: malloc failure)
Your message dated Tue, 13 Jun 2023 01:56:36 +0530
with message-id
and subject line Re: Gitaly: ... Exception: EVP_PKEY_new_mac_key: malloc failure
has caused the Debian Bug report #1014580,
regarding Gitaly: ... Exception: EVP_PKEY_new_mac_key: malloc failure
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.)
--
1014580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitaly
Version: 14.10.4+dfsg-1~fto11+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gitlab:all/bullseye-fasttrack 14.10.5+ds1-1~fto11+1 package unusable
because:
Checking Gitaly ...
Gitaly: ... Exception: EVP_PKEY_new_mac_key: malloc failure
From production.log:
ActionView::Template::Error (EVP_PKEY_new_mac_key: malloc failure):
26: - if project.creator && use_creator_avatar
27: = image_tag avatar_icon_for_user(project.creator,
48), class : "avatar s48", alt: ''
28: - else
29: = project_icon(project, alt: '', class: 'avatar
project-avat ar s48', width: 48, height: 48)
30: .project-details.d-sm-flex.flex-sm-fill.align-items-center{
data: { qa_selector: 'project_content', qa_project_name: project.name } }
31: .flex-wrapper
32: .d-flex.align-items-center.flex-wrap.project-title
lib/gitlab/gitaly_client.rb:186:in `authorization_token'
lib/gitlab/gitaly_client.rb:194:in `request_kwargs'
lib/gitlab/gitaly_client.rb:154:in `execute'
lib/gitlab/gitaly_client/call.rb:18:in `block in call'
lib/gitlab/gitaly_client/call.rb:55:in `recording_request'
lib/gitlab/gitaly_client/call.rb:17:in `call'
lib/gitlab/gitaly_client.rb:147:in `call'
lib/gitlab/gitaly_client/ref_service.rb:49:in `default_branch_name'
lib/gitlab/git/repository.rb:91:in `root_ref'
app/models/repository.rb:534:in `root_ref'
lib/gitlab/repository_cache_adapter.rb:95:in `block (2 levels) in
cache_method_a symmetrically'
lib/gitlab/repository_cache.rb:44:in `fetch_without_caching_false'
lib/gitlab/repository_cache_adapter.rb:190:in `block (2 levels) in
cache_method_ output_asymmetrically'
lib/gitlab/safe_request_store.rb:12:in `fetch'
lib/gitlab/repository_cache.rb:25:in `fetch'
lib/gitlab/repository_cache_adapter.rb:189:in `block in
cache_method_output_asym metrically'
lib/gitlab/utils/strong_memoize.rb:30:in `strong_memoize'
lib/gitlab/repository_cache_adapter.rb:203:in `block in
memoize_method_output'
lib/gitlab/repository_cache_adapter.rb:212:in `no_repository_fallback'
lib/gitlab/repository_cache_adapter.rb:202:in `memoize_method_output'
lib/gitlab/repository_cache_adapter.rb:188:in
`cache_method_output_asymmetricall y'
lib/gitlab/repository_cache_adapter.rb:94:in `block in
cache_method_asymmetrical ly'
app/models/repository.rb:670:in `head_commit'
app/models/repository.rb:681:in `tree'
app/models/repository.rb:1022:in `file_on_head'
app/models/repository.rb:586:in `block in avatar'
lib/gitlab/gitaly_client.rb:305:in `allow_n_plus_1_calls'
app/models/repository.rb:585:in `avatar'
lib/gitlab/repository_cache_adapter.rb:21:in `block (2 levels) in
cache_method'
lib/gitlab/repository_cache.rb:25:in `fetch'
lib/gitlab/repository_cache_adapter.rb:163:in `block in cache_method_output'
lib/gitlab/utils/strong_memoize.rb:30:in `strong_memoize'
lib/gitlab/repository_cache_adapter.rb:203:in `block in
memoize_method_output'
lib/gitlab/repository_cache_adapter.rb:212:in `no_repository_fallback'
lib/gitlab/repository_cache_adapter.rb:202:in `memoize_method_output'
lib/gitlab/repository_cache_adapter.rb:162:in `cache_method_output'
lib/gitlab/repository_cache_adapter.rb:20:in `block in cache_method'
app/models/project.rb:1522:in `avatar_in_git'
app/models/project.rb:1526:in `avatar_url'
app/models/concerns/avatarable.rb:37:in `avatar_url'
app/helpers/avatars_helper.rb:135:in `source_icon'
app/helpers/avatars_helper.rb:7:in `project_icon'
app/views/shared/projects/_project.html.haml:29
app/views/shared/projects/_project.html.haml:25
app/views/shared/projects/_project.html.haml:22
app/views/shared/projects/_list.html.haml:38
app/views/shared/projects/_list.html.haml:36:in `each_with_index'
app/views/shared/projects/_list.html.haml:36
app/views/dashboard/projects/_projects.html.haml:1
app/views/dashboard/projects/index.html.haml:16
app/controllers/application_controller.rb:142:in `render'
app/controllers/dashboard/projects_controller.rb:63:in `block in
render_projects '
lib/gitlab/gitaly_client.rb:305:in `allow_n_plus_1_calls'
app/controllers/dashboard/projects_controller.rb:62:
Bug#1037435: ojalgo tests using the network at build time (again)
Package: ojalgo
Version: 52.0.1+ds-1
Severity: serious
Tags: patch
Justification: Policy 4.9
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
Hi Pierre,
The ojalgo package has been failing to build from source in Ubuntu, because
its tests are trying to access the network:
[...]
[ERROR] Failures:
[ERROR] YahooDataSourceTest.testFetchDaily:54 No data!
[ERROR] YahooDataSourceTest.testFetchMonthly:62 No data!
[ERROR] YahooDataSourceTest.testFetchWeekly:70 No data!
[ERROR]
YahooDataSourceTest.testYahooDailyAAPL:79->FinanceSeriesTests.assertAtLeastExpectedItems:64
No data!
[ERROR]
YahooDataSourceTest.testYahooMonthlyAAPL:87->FinanceSeriesTests.assertAtLeastExpectedItems:64
No data!
[ERROR]
YahooDataSourceTest.testYahooWeeklyAAPL:95->FinanceSeriesTests.assertAtLeastExpectedItems:64
No data!
[ERROR] Errors:
[ERROR]
YahooDataSourceTest.testDeriveDistributions:47->FinanceSeriesTests.doTestDeriveDistribution:84
» NegativeArraySize
[ERROR] OptimisationServiceTest.testEnvironment:67 » Runtime
java.util.concurrent.Exec...
[ERROR] OptimisationServiceTest.testTest:55 » Runtime
java.util.concurrent.ExecutionEx...
[ERROR] OptimisationServiceTest.testVeryBasicModel:41 » Runtime
java.util.concurrent.E...
[...]
(https://launchpad.net/ubuntu/+source/ojalgo/52.0.1+ds-1/+build/26010077)
There was already a patch in the source to disable network tests, but it
appears that some new network tests have now been added. I've extended the
patch to disable these tests as well; please see the attached diff.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch
ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch
--- ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch 2023-01-18
13:33:30.0 -0800
+++ ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch 2023-06-12
12:54:52.0 -0700
@@ -4,8 +4,10 @@
Reviewed-by: Pierre Gruet
Last-Update: 2022-12-17
a/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
-+++
b/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
+Index:
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
+===
+---
ojalgo-52.0.1+ds.orig/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
@@ -22,6 +22,7 @@
*/
package org.ojalgo.data.domain.finance.series;
@@ -22,3 +24,43 @@
public class AlphaVantageDataSourceTest extends FinanceSeriesTests {
public AlphaVantageDataSourceTest() {
+Index:
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/YahooDataSourceTest.java
+===
+---
ojalgo-52.0.1+ds.orig/src/test/java/org/ojalgo/data/domain/finance/series/YahooDataSourceTest.java
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/YahooDataSourceTest.java
+@@ -22,6 +22,7 @@
+ */
+ package org.ojalgo.data.domain.finance.series;
+
++import org.junit.jupiter.api.Disabled;
+ import org.junit.jupiter.api.Test;
+ import org.ojalgo.TestUtils;
+ import org.ojalgo.type.CalendarDateUnit;
+@@ -31,6 +32,7 @@
+ *
+ * @author apete
+ */
++@Disabled("Requires network access")
+ public class YahooDataSourceTest extends FinanceSeriesTests {
+
+ private static YahooSession SESSION = new YahooSession();
+Index:
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/optimisation/service/OptimisationServiceTest.java
+===
+---
ojalgo-52.0.1+ds.orig/src/test/java/org/ojalgo/optimisation/service/OptimisationServiceTest.java
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/optimisation/service/OptimisationServiceTest.java
+@@ -1,6 +1,7 @@
+ package org.ojalgo.optimisation.service;
+
+ import org.junit.jupiter.api.AfterEach;
++import org.junit.jupiter.api.Disabled;
+ import org.junit.jupiter.api.Test;
+ import org.ojalgo.TestUtils;
+ import org.ojalgo.netio.BasicLogger;
+@@ -9,6 +10,7 @@
+ import org.ojalgo.optimisation.ExpressionsBasedModel;
+ import org.ojalgo.optimisation.Optimisation.Result;
+
++@Disabled("Requires network access")
+ public class OptimisationServiceTest {
+
+ private static final String PATH_ENVIRONMENT =
"/optimisation/v01/environment";
Processed: Re: Bug#1036601: xenstore-utils: broken symlink /usr/bin/xenstore-control
Processing control commands: > retitle -1 xenstore-utils: broken symlink /usr/bin/xenstore-control Bug #1036601 [xenstore-utils] xenstore-utils: missing Depends: xen-utils-common Changed Bug title to 'xenstore-utils: broken symlink /usr/bin/xenstore-control' from 'xenstore-utils: missing Depends: xen-utils-common'. -- 1036601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036601: xenstore-utils: broken symlink /usr/bin/xenstore-control
Control: retitle -1 xenstore-utils: broken symlink /usr/bin/xenstore-control This is a bit more complicated: Up to bullseye the binaries in the xenstore-utils package were independent of the running xen version (as the xenstore interface is more or less supposed to be stable). Starting with bookworm the xenstore-control binary is now linked against unstable xen api libraries (libxenguest.so and libxenctrl.so) which are included in the libxenmisc4.17 package. The upstream commit for this change is [1] and the documentation also says that the control command interface is not xen version independent. Because of the additional shared library dependencies our shuffle-binaries script [3] kicks in and sets up the xen-utils-wrapper for xenstore-control. The xen-utils-wrapper is only included in the xen-utils-common package. But adding that dependency would not be enough. It would make the /usr/bin/ xenstore-control symlink not broken, but the wrapper would not find the real binary, as it is included in the xen-utils-4.17 package at the /usr/lib/ xen-4.17/bin/xenstore-control path. Installing only xenstore-utils and xen-utils-common in a dom-U gives the following output when executing xenstore-control: $ xenstore-control ERROR: Can't find version 4.17 of xen utils (maybe xen-utils-4.17 was already removed before rebooting out of Xen 4.17), bailing out! Some options I see for fixing this: [a] make xenstore-utils depend on xen-utils-V [b] move the /usr/bin/xenstore-control symlink to xen-utils-V [c] split the xenstore-utils package in a xen version independent and xen version dependent package. Disadvantage from [a] is that xenstore-utils can also be used inside a dom-U and would pull lots of unused stuff. [c] seems to be a bit overkill for only one binary file, so I currently see [b] as the best option. So does anybody have any opinion, ideas or something else to say about all this? Or any better ideas? [1] https://salsa.debian.org/xen-team/debian-xen/-/commit/7f97193e6aa858df03be501440e0ade8cceb9ec5 [2] https://salsa.debian.org/xen-team/debian-xen/-/blob/master/docs/misc/xenstore.txt#L378 [3] https://salsa.debian.org/xen-team/debian-xen/-/blob/master/debian/shuffle-binaries signature.asc Description: This is a digitally signed message part.
Bug#1037433: gnome-games-app: Needs to be ported to libsoup3
Source: gnome-games-app Version: 40.0-4 Severity: serious Tags: trixie sid gnome-games-app needs to be ported from libsoup2.4 to libsoup3. It is not possible for apps to simultaneously link against both libsoup2.4 and libsoup3. We need to switch grilo and its dependencies to libsoup3; this will make it impossible to run gnome-games-app as a .deb in Debian Trixie. Upstream changed their name to Highscore but never did publish a release with the rename. The project looks unmaintained currently. Alternatives --- Unfortunately, it appears like the app is not currently published in Flathub, nor has a Snap version been published yet. https://discussion.fedoraproject.org/t/what-happened-to-gnome-games-in-flathub/82747 There are Debian packages of Lutris and Retroarch which are similar apps. Thank you, Jeremy Bícha
Processed: pipewire-media-session is dead upstream
Processing commands for cont...@bugs.debian.org: > severity 1030765 serious Bug #1030765 [pipewire-media-session] pipewire-media-session is dead upstream Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1030765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1034433 in 3~git20230601+dfsg-1
Processing commands for cont...@bugs.debian.org: > found 1034433 3~git20230601+dfsg-1 Bug #1034433 [libsdl3-doc] libsdl3-doc: missing Breaks+Replaces: libsdl1.2-dev (<< 3) Marked as found in versions libsdl3/3~git20230601+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1034433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
On 09/05/2023 16.55, Helmut Grohne wrote: Control: forcemerge 1033167 -1 Control: affects 1033167 + 9base Hi Andreas, On Tue, May 09, 2023 at 04:39:21PM +0200, Andreas Beckmann wrote: during a test with piuparts I noticed your package leaves modifications in /etc/shells after upgrading from bullseye to bookworm and purging the package. 9base/bullseye called add-shell/remove-shell in its postinst/postrm. 9base/bookworm no longer does that, but it also does not clean up the leftover entries from bullseye in its postinst. 9base/bookworm no longer does, because it now uses dpkg-triggers to perform the cleanup. It actually does clean up its entries. >From the attached log (scroll to the bottom...): 0m45.2s ERROR: FAIL: After purging files have been modified: /etc/shells not owned You should look closer: 0m45.2s DEBUG: Modified(user, group, mode, size, target): /etc/shells expected(root, root, - 100644, 128, None) != found(root, root, - 100644, 140, None) It's a 12 byte difference. That's not 9base's entries. What you see here is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it. Thus force-merging. No, it's "/usr/bin/rc\n". # cat /usr/share/debianutils/shells.d/plan9 /bin/rc /usr/lib/plan9/bin/rc If I install 9base in an unmerged-/usr sid chroot, I get # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc who is responsible for the duplicate entry? If I install 9base in a merged-/usr sid chroot, I get # /etc/shells: valid login shells /bin/sh /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash /usr/bin/sh /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc same duplication ... If I reconfigure usrmerge afterwards, I get # /etc/shells: valid login shells /bin/sh /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash /usr/bin/sh /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc /usr/bin/rc Now we got the additional /usr/bin/rc entry Andreas
Bug#1036359: elpa-markdown-toc -- crashes with (wrong-type-argument consp nil)
Antoine Beaupré writes: > On 2023-06-11 14:45:19, Nicholas D. Steeves wrote: >> >> Here is a way to work around this bug (whether in Emacs or in markdown-toc). [snip] > > Oh wow, thanks! You're welcome! > That said it doesn't actually work! I have tried both the `--eval` and > the `setq` and neither fix the crash. > > I'm not sure this is related to native compilation, is it really? When I 'rm -rf ~/.emacs.d/eln-cache, and restart Emacs, markdown-toc-generate-toc works correctly, but will eventually break again once various things are compiled again (sooner than later on a fast machine!). I'm not sure why the deny list hack works with an empty eln-cache, but not after a 'rm ~/.emacs.d/eln-cache/*/markdown-toc*'. > I thought it was some imenu thing, maybe it doesn't get autoloaded properly? Based on your hunch, I tested removing each rdep from the eln-cache, and I found that the (wrong-type-argument consp nil) bug occurs in markdown-mode-toc when markdown-mode is native compiled. markdown-toc-generate-toc succeeds for me when ~/.emacs.d/eln-cache/*/markdown-mode-*.eln and ~/.emacs.d/eln-cache/*/markdown-toc-*.eln and ~/.emacs.d/eln-cache/*/imenu-*.eln are removed, and emacs is started with this minimal workaround: emacs --eval="(setq native-comp-deferred-compilation-deny-list '(\"markdown-mode\"))" Yes, markdown-mode, no "toc". For this hack to work long-term for most users, it seems like imenu would probably need to be added to that list...but here's the strange thing: Logically, markdown-toc-generate-toc uses imenu, so it seems like it should trigger native-comp of imenu at L261. Neither markdown-mode, nor markdown-mode-toc explicitly (require 'imenu), so yes, I think you're right that one or both of them is depending on autoloads. Markdown-toc ends up native-compiled using this method, markdown-mode and imenu don't, and for reasons that aren't yet clear, this allows markdown-toc to function correctly. I also wonder if there may be a dash.el+native comp bug in play. 'hope this band-aid does the trick until the root of the problem can be identified. Nicholas signature.asc Description: PGP signature
Processed: affects 1030129
Processing commands for cont...@bugs.debian.org: > affects 1030129 src:osmpbf Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install: Error loading java.security file Added indication that 1030129 affects src:osmpbf > 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
Processed: Re: Bug#1037425: linux-kbuild-6.1: please add Breaks against obsolete *-dkms packages
Processing control commands: > reassign -1 src:linux Bug #1037425 [linux-kbuild-6.1] linux-kbuild-6.1: please add Breaks against obsolete *-dkms packages Bug reassigned from package 'linux-kbuild-6.1' to 'src:linux'. No longer marked as found in versions linux/6.1.27-1. Ignoring request to alter fixed versions of bug #1037425 to the same values previously set > severity -1 important Bug #1037425 [src:linux] linux-kbuild-6.1: please add Breaks against obsolete *-dkms packages Severity set to 'important' from 'serious' -- 1037425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037425: linux-kbuild-6.1: please add Breaks against obsolete *-dkms packages
Control: reassign -1 src:linux Control: severity -1 important On Mon, Jun 12, 2023 at 05:31:53PM +0200, Andreas Beckmann wrote: > As a consequence, if cruft *-dkms packages are still installed, but fail > to build the module for current kernels, this may result in upgrade > failures. Therefore please add Breaks against cruft *-dkms packages that > may be left over from previous releases to ensure they get removed. > I chose linux-kbuild-6.1 for the addition of these Breaks since all > linux-headers-* packages depend on that. And why not at dkms? And how does this help in the long term, as every kernel release breaks modules? Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate unknown
Bug#1019307: marked as done (bluebird-gtk-theme: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev)
Your message dated Mon, 12 Jun 2023 15:53:32 + with message-id and subject line Bug#1019307: fixed in bluebird-gtk-theme 1.3-4 has caused the Debian Bug report #1019307, regarding bluebird-gtk-theme: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev 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.) -- 1019307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bluebird-gtk-theme Version: 1.3-3 Severity: normal User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: split-gdk-pixbuf In Debian 10 and older, the libgdk-pixbuf2.0-dev package contained development files for two libraries: gdk-pixbuf-2.0 and the deprecated gdk-pixbuf-xlib-2.0. In Debian 11, it was split into libgdk-pixbuf-2.0-dev and libgdk-pixbuf-xlib-2.0-dev packages. libgdk-pixbuf2.0-dev continues to exist, but is now a transitional package that pulls in the deprecated libgdk-pixbuf-xlib-2.0-dev in addition to libgdk-pixbuf-2.0-dev. If libgdk-pixbuf-2.0-dev is sufficient to build this package, please swap the build-dependency on libgdk-pixbuf2.0-dev to refer to libgdk-pixbuf-2.0-dev instead. That change will avoid this package having to be removed from Debian if gdk-pixbuf-xlib gets removed. If this package also needs the deprecated gdk-pixbuf-xlib-2.0 (unlikely), please build-depend on both libgdk-pixbuf-2.0-dev and libgdk-pixbuf-xlib-2.0-dev explicitly, instead of via the transitional package libgdk-pixbuf2.0-dev. Thanks, smcv --- End Message --- --- Begin Message --- Source: bluebird-gtk-theme Source-Version: 1.3-4 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of bluebird-gtk-theme, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated bluebird-gtk-theme package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 Jun 2023 11:26:29 -0400 Source: bluebird-gtk-theme Built-For-Profiles: noudeb Architecture: source Version: 1.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Desktop Theme Team Changed-By: Jeremy Bícha Closes: 1019307 Changes: bluebird-gtk-theme (1.3-4) unstable; urgency=medium . * Team upload * Bump debhelper from old 12 to 13 * Bump Standards-Version to 4.6.2 * Update package name for libgdk-pixbuf-2.0-dev Build-Depends (Closes: #1019307) Checksums-Sha1: e9a432f4fe01d42dc4732ed4f937c1a23dc04d1a 2079 bluebird-gtk-theme_1.3-4.dsc 4d8371bf6908304f9a61eed86b370575580503df 49740 bluebird-gtk-theme_1.3-4.debian.tar.xz 301ab1f9296eecd262b7555e44f6bdc342950248 11410 bluebird-gtk-theme_1.3-4_source.buildinfo Checksums-Sha256: 18d0c18bbd5ac9249b5dd28fbde05091bb5dd940f3f7488b180d4f853caccf82 2079 bluebird-gtk-theme_1.3-4.dsc 20dec9405b7c216446d0e67f9dafe225a5efa35fa7d9d334a5282a68439d9548 49740 bluebird-gtk-theme_1.3-4.debian.tar.xz 603ffc2a64033a71453437221cfb42bd36279ed8094f39c1002ea534ae92546c 11410 bluebird-gtk-theme_1.3-4_source.buildinfo Files: 9442308bba2786a1e2db368698c1736d 2079 x11 optional bluebird-gtk-theme_1.3-4.dsc 6a5cc87db7f68c38ef867b68ed659f54 49740 x11 optional bluebird-gtk-theme_1.3-4.debian.tar.xz 878550e00f70939cdd467c6147978cf7 11410 x11 optional bluebird-gtk-theme_1.3-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmSHOUQACgkQ5mx3Wuv+ bH3ZmBAAhOfcMVsE5+XEvekWrDyjtTr9u36lebznpA0tcWzYKxzq9ci8aWh6CU3Q DY85ZhKi//b8ofS84fjoHK4kyY24XL1jLz2h8p0LJXg5A9cCGnAzNZXj+3j4uJnN wcAef7sosjE5XMacvz7Am5yDlO63yUHt4+5UBfjmD4rKzN7jk99OvdxA6mVv7Znc q3VXs3lM5OOrNx2A9QCfikmQ5QVbZ8Hsw0077uSmdB8lFZoMnAocI47FhofpD+yZ jSQhztP+0wwvU4aXX6Pbxr0372maQjTky3V1jpovGW+58nUuqp7QSIp9fgjRD0se ZFO5Eczt0SIbe50PVkvhjqWFGo8OpU5AUKA69Ibd4sq2GLclOL7eEVnNZpFlwgkj 3fElBbADhUusHFt0x/rUmqZX6St54QHaatI8H1XQylqqxY+wNRBrF+n7ByYqJ+6K ke9Fao1D34VkO+N/S7LL2zP3GSBCVdLgIJoldugGYQkrG6v7wo1jzJoVOQmBM46b EH42s+0ACIdIYZbFb3ojPVPKczRwv6VxIjy5gLl+li/5gEwsMYNiytfX2tOWVSeG PUv2NL4Yk42leRSJ84ycnYijBZDUVf8ZIhUvyG+SfTYuvF91nVfZM0i1NzHefbIS /yMCb
Bug#1037425: linux-kbuild-6.1: please add Breaks against obsolete *-dkms packages
Package: linux-kbuild-6.1 Version: 6.1.27-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, one change in dkms in bookworm is that it actually returns an error when failing to build a module, as a result /etc/kernel/header_postinst.d/dkms may fail and cause linux-headers---.postinst to fail. (Up to bullseye, dkms returned 0 on failure and the failure was only noticable when someone studied the install/upgrade log.) As a consequence, if cruft *-dkms packages are still installed, but fail to build the module for current kernels, this may result in upgrade failures. Therefore please add Breaks against cruft *-dkms packages that may be left over from previous releases to ensure they get removed. I chose linux-kbuild-6.1 for the addition of these Breaks since all linux-headers-* packages depend on that. I'm trying to build a list: Breaks: # in bullseye, not in bookworm: nvidia-tesla-418-kernel-dkms (<< 418.226.00-9~), nvidia-tesla-460-kernel-dkms (<< 460.106.00-9~), # in buster, not in bullseye sl-modem-dkms (<< 2.9.11~20110321-16.0), # in stretch, not in buster blktap-dkms (<< 2.0.93-0.10.0), # in jessie, not in stretch oss4-dkms (<< 4.2-build2020-1~), # in wheezy, not in jessie blcr-dkms (<< 0.8.6~b3-1.0), Maybe there are more, but I haven't seen them, yet. In case this was fixed in sid (but not in bookworm), I've used that version suffixed with '~', otherwise (i.e. not fixed in sid) I've invented a version based on the last version in sid with NMU suffix .0 The typical upgrade failure if one of these obsolete packages is still installed looks like this: ... Setting up linux-headers-6.1.0-9-amd64 (6.1.27-1) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-9-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Certificate or key are missing, generating self signed certificate for MOK... openssl not found, can't generate key and certificate. Building module: Cleaning build area... make -j84 KERNELRELEASE=6.1.0-9-amd64 -C /lib/modules/6.1.0-9-amd64/build M=/var/lib/dkms/blcr/0.8.5/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-9-amd64 (x86_64) Consult /var/lib/dkms/blcr/0.8.5/build/make.log for more information. dkms autoinstall on 6.1.0-9-amd64/x86_64 failed for blcr(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-9-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-9-amd64.postinst line 11. dpkg: error processing package linux-headers-6.1.0-9-amd64 (--configure): installed linux-headers-6.1.0-9-amd64 package post-installation script subprocess returned error exit status 1 Setting up gnupg (2.2.40-1.1) ... dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.1.0-9-amd64 (= 6.1.27-1); however: Package linux-headers-6.1.0-9-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for systemd (252.6-1.1~deb12anbe1) ... Processing triggers for debianutils (5.7-0.4) ... Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: linux-headers-6.1.0-9-amd64 linux-headers-amd64 while on bullseye the ignored failure looked like this: ... Setting up linux-headers-5.10.0-22-amd64 (5.10.178-3) ... /etc/kernel/header_postinst.d/dkms: Error! Bad return status for module build on kernel: 5.10.0-22-amd64 (x86_64) Consult /var/lib/dkms/blcr/0.8.5/build/make.log for more information. Andreas
Bug#1031445: marked as done (camv-rnd: FTBFS: build-dependency not installable: librnd4-dev (>= 3.2.0))
Your message dated Mon, 12 Jun 2023 09:18:39 -0600 (MDT) with message-id <20230612151839.878d924e0...@rover.gag.com> and subject line librnd4 now in unstable has caused the Debian Bug report #1031445, regarding camv-rnd: FTBFS: build-dependency not installable: librnd4-dev (>= 3.2.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: camv-rnd Version: 1.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230216 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), librnd4-dev (>= 3.2.0), libgd-dev, > libgtkglext1-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 11), librnd4-dev (>= 3.2.0), libgd-dev, > libgtkglext1-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [394 B] > Get:5 copy:/<>/apt_archive ./ Packages [474 B] > Fetched 1825 B in 0s (139 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librnd4-dev (>= 3.2.0) but it is > not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/02/16/camv-rnd_1.1.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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 --- The latest librnd upload resulted in librnd4 appearing in unstable, fixing this FTBFS situation. Bdale--- End Message ---
Bug#1037107: Acknowledgement (pre-unblock: bookworm-pu: mariadb/1:10.11.3-2/+deb12u1)
* Otto Kekäläinen [Wed Jun 07, 2023 at 07:07:50PM -0700]: > Note that upstream released 10.11.4 today. Import preparation in > progress at > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/50. > I plan to upload this to experimental tomorrow and eventually into > bookworm-pu if the release team approves. I want to add my +1 as a user of mariadb, the current mariadb version in bookworm has a serios regression which turned out to be https://jira.mariadb.org/browse/MDEV-31403 and is fixed by 1:10.11.4-1 (as present in current Debian/unstable), so a fixed package of mariadb would be highly appreciated. Thanks, Otto and release team :) regards -mika- signature.asc Description: PGP signature
Bug#1036359: elpa-markdown-toc -- crashes with (wrong-type-argument consp nil)
On 2023-06-11 14:45:19, Nicholas D. Steeves wrote:
> Hi,
>
> Here is a way to work around this bug (whether in Emacs or in markdown-toc).
>
> To test:
> emacs --eval="(setq native-comp-deferred-compilation-deny-list
> '(\"markdown-toc\"))"
>
> To make permanent:
> (setq native-comp-deferred-compilation-deny-list '("markdown-toc"))
>
> That said, I'm not convinced that a workaround like this should be
> inserted into Debian's markdown-toc (or any package)...
Oh wow, thanks!
That said it doesn't actually work! I have tried both the `--eval` and
the `setq` and neither fix the crash.
Debugger entered--Lisp error: (wrong-type-argument consp nil)
markdown-imenu-create-nested-index()
markdown-toc-generate-toc(nil)
funcall-interactively(markdown-toc-generate-toc nil)
command-execute(markdown-toc-generate-toc record)
execute-extended-command(nil "markdown-toc-generate-toc" nil)
funcall-interactively(execute-extended-command nil
"markdown-toc-generate-toc" nil)
command-execute(execute-extended-command)
I'm not sure this is related to native compilation, is it really?
I thought it was some imenu thing, maybe it doesn't get autoloaded properly?
a.
--
Si Dieu existe, j'espère qu'Il a une excuse valable
- Daniel Pennac
Bug#1037415: librust-grep-printer-dev: impossible to install: depends on gone package librust-base64-0.13+default-dev
Package: librust-grep-printer-dev Version: 0.1.6-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 librust-grep-printer-dev depends on librust-base64-0.13+default-dev which is gone. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSHKHAACgkQLHwxRsGg ASGMJRAArH4HaVhzJXG99ayt8E9iZ6NSdECmqVndJSfUFNgrjXpy7cImi394cK94 0aA3yq8MdcMYh23gJEcW975YU7cjKT8WFHKsGvkYUZ51RDbEKAJly6tGp+mMHKA6 k2MGNJNejJlyNEL7Zd62Mq3wNUD//mz4aYn75MPkF3ucgSkw3l7/rh+jHbrLwiUu mXFRt0ZJkTR93UmpNcZDYmfjmaZ6/IFQ1sOwaCjZkP4NtPBtc4W97bdBNtcypNMr WiuPtTpUDArauX/MGu4v4KiY+EZa7AYdfdzqRHXkolH3nHOrjOL8QDwWdXXjBQ2V iuoaFIrQPUHNx1l93rotFUQYCuIabszdTutIuZgRTOxCgnsmqg88JqIifqFK8RHj zf7/LdahBDP8G0VV72LgB+VrLIT4nJNZNYciATKMnMn5zh9ref1FIOlfEio0KVgJ 9NrrwD9PPujEVVTe55b0lIKd24O57qs4SF5o51skLEshAqDS7ymCL95zWv/mPC76 yOgZhdW6ttfWgmrmLLqNiCgPJ9l6ydLzprU+dHyBx1hqo3iFVsvsAoLzseZdVWAM nO7Tfo1x4cuVTb62AC0hFja05/b4HkuP6+bwVX6AHllvlKu7Uo601HUtHbFzhVmT 4htlWV+7Wp8qeE95IWZkYxWJXyXSe2xXLG8QRb1wOJGqCZL/JtE= =3JpT -END PGP SIGNATURE-
Bug#1037414: gcc-13 ftbfs on mipsel
Package: src:gcc-13 Version: 13.1.0-5 Severity: serious Tags: sid trixie X-Debbugs-CC: debian-m...@lists.debian.org gcc-13 ftbfs on mipsel: [...] Bootstrap comparison failure! gcc/rust/rust-macro-builtins.o differs gcc/rust/rust-session-manager.o differs gcc/rust/rust-cfg-parser.o differs gcc/rust/rust-lex.o differs make[4]: *** [Makefile:30369: compare] Error 1 make[4]: Leaving directory '/<>/build' make[3]: *** [Makefile:30349: stage3-bubble] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [Makefile:30412: bootstrap] Error 2 I'll ignore these for now, but please address this upstream.
Processed: Debian bugs control
Processing commands for cont...@bugs.debian.org: > retitle 1037107 bookworm-pu: mariadb/1:10.11.4-0+deb12u1 Bug #1037107 [release.debian.org] pre-unblock: bookworm-pu: mariadb/1:10.11.3-2/+deb12u1 Changed Bug title to 'bookworm-pu: mariadb/1:10.11.4-0+deb12u1' from 'pre-unblock: bookworm-pu: mariadb/1:10.11.3-2/+deb12u1'. > tags 1037107 bookworm Bug #1037107 [release.debian.org] bookworm-pu: mariadb/1:10.11.4-0+deb12u1 Added tag(s) bookworm. > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was o...@debian.org). > usertags 1037107 + pu There were no usertags set. Usertags are now: pu. > affects 1037107 src:mariadb Bug #1037107 [release.debian.org] bookworm-pu: mariadb/1:10.11.4-0+deb12u1 Added indication that 1037107 affects src:mariadb > thanks Stopping processing here. Please contact me if you need assistance. -- 1037107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037411: nautilus-owncloud: menu doesn't appear due to nautilus API changes
Package: nautilus-owncloud Version: 2.11.0.8354+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: micha...@gmail.com Dear Maintainer, The version of nautilus shipped in bookworm has a different API from what is expected by the shell extension in the nautilus-owncloud package. The sync status icons are correctly displayed, but the owncloud menu doesn't appear, making this package essentially unusable. When starting nautilus, the following error is displayed: TypeError: MenuExtension_ownCloud.get_file_items() missing 1 required positional argument: 'files' The bug has been fixed in https://github.com/owncloud/client/pull/10075 and would need to be backported to the stable package version. It looks like some work was done in https://salsa.debian.org/owncloud-team/owncloud-client/-/merge_requests/2 but never completed. Best regards, Micha -- 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-amd64 (SMP w/8 CPU threads; PREEMPT) 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 nautilus-owncloud depends on: ii nautilus 43.2-1 ii owncloud-client 2.11.0.8354+dfsg-1+b1 ii owncloud-client-data 2.11.0.8354+dfsg-1 ii python3 3.11.2-1+b1 ii python3-nautilus 4.0-1+b1 nautilus-owncloud recommends no packages. Versions of packages nautilus-owncloud suggests: pn nautilus-script-manager -- no debconf information
Bug#1037409: golang-golang-x-exp ftbfs with gccgo-go (both gccgo-12 and gccgo-13)
Package: src:golang-golang-x-exp
Version: 0.0~git20221028.83b7d23-2
Severity: serious
Building with golang-any changed to gccgo-go to force gccgo on amd64,
build fails with error. Full build log attached. Either this should be
fixed or dependency should be updated to golang-go instead of golang-any.
golang.org/x/exp/maps
# golang.org/x/exp/maps
src/golang.org/x/exp/maps/maps.go:10:10: error: expected ‘(’
10 | func Keys[M ~map[K]V, K comparable, V any](m M) []K {
| ^
src/golang.org/x/exp/maps/maps.go:10:13: error: invalid character 0x7e
in input file
10 | func Keys[M ~map[K]V, K comparable, V any](m M) []K {
| ^
src/golang.org/x/exp/maps/maps.go:11:9: error: expected ‘]’
11 | r := make([]K, 0, len(m))
| ^
src/golang.org/x/exp/maps/maps.go:11:9: error: expected ‘;’ or newline
after top level declaration
src/golang.org/x/exp/maps/maps.go:12:9: error: expected declaration
12 | for k := range m {
| ^
src/golang.org/x/exp/maps/maps.go:14:9: error: expected declaration
14 | }
| ^
src/golang.org/x/exp/maps/maps.go:15:9: error: expected declaration
15 | return r
| ^
src/golang.org/x/exp/maps/maps.go:16:1: error: expected declaration
16 | }
| ^
sbuild (Debian sbuild) 0.85.2 (11 March 2023) on mahishi
+===+
| golang-golang-x-exp 0.0~git20221028.83b7d23-2 (amd64) Mon, 12 Jun 2023
12:47:20 + |
+===+
Package: golang-golang-x-exp
Version: 0.0~git20221028.83b7d23-2
Source Version: 0.0~git20221028.83b7d23-2
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-amd64-sbuild-24a3fad7-52f9-45d5-ba4b-67774cece214'
with '<>'
I: NOTICE: Log filtering will replace
'build/golang-golang-x-exp-PqPMEI/resolver-ugb2fS' with '<>'
+--+
| Update chroot|
+--+
Hit:1 http://deb.debian.org/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+--+
| Fetch source files |
+--+
Local sources
-
/home/pravi/forge/go-team/golang-golang-x-exp_0.0~git20221028.83b7d23-2.dsc
exists in /home/pravi/forge/go-team; copying to chroot
I: NOTICE: Log filtering will replace
'build/golang-golang-x-exp-PqPMEI/golang-golang-x-exp-0.0~git20221028.83b7d23'
with '<>'
I: NOTICE: Log filtering will replace 'build/golang-golang-x-exp-PqPMEI' with
'<>'
+--+
| Install package build dependencies |
+--+
Setup apt archive
-
Merged Build-Depends: debhelper-compat (= 13), dh-sequence-golang, gccgo-go (>=
2:1.18~), gccgo-13, build-essential, fakeroot
Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-golang, gccgo-go
(>= 2:1.18~), gccgo-13, build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [609 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [670 B]
Get:5 copy:/<>/apt_archive ./ Packages [702 B]
Fetched 1981 B in 0s (0 B/s)
Reading package lists...
Reading package lists...
Install main build dependencies (apt-based resolver)
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
autoconf automake autopoint autotools-dev bsdextrautils cpp-13 debhelper
dh-autoreconf dh-golang dh-strip-nondeterminism dwz file gcc-13 gccgo-12
gccgo-13 gccgo-go gettext gettext-base groff-base intltool-debian
libarchive-zip-perl libdebhelper-perl libelf1
libfile-stripnondeterminism-perl libgcc-13-dev libgo-12-dev libgo-13-dev
libgo21 libgo22 libhwasan0 libicu72 libmagic-mgc libmagic1 libpipeline1
libsub-override-perl libtool libuchardet0 libxml2 m4 man-db po-debconf
sensible-utils
Suggested packages:
autoconf-archive gnu-stand
Bug#1037351: hippotat: ftbfs with rust-base64 0.21
Peter Green writes ("Bug#1037351: hippotat: ftbfs with rust-base64 0.21"):
> hippotat FTBFS with the new version of rust-base64.
Thanks for the report.
> I attach a patch which makes the package build.
> I have not tested it beyond that (and the build said it was
> skipping tests due to lack of unshare).
Unfortunately the automatic tests are not suitable for running in
Debian CI. Running them via autopkgtest is nontrivial and probably
not possible for people other than me :-/.
I'm hoping trixie will bring some new tooling that will help with
that.
> Also your clean target is horriblly broken, I filtered the
> debdiff to get rid of a huge volume of junk.
I confess I don't often use `make clean`. I normally use `git clean`.
> I may or may not NMU this later.
I will probably fix this myself fairly soon.
Since AFAICT you haven't written a formal Signed-off-by, would you
mind confirming the statements in DEVELOPER-CERTIFICATE (copy
below) ? (If you don't want to make that confirmation I will rewrite
the patch myself.)
Thanks,
Ian.
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
--
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.
Processed: severity reset after bookworm
Processing commands for cont...@bugs.debian.org: > severity 1036113 serious Bug #1036113 [libpurple0] libpurple0: license conflict with libsasl2 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1036113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034609: marked as done (Fails to start under Python 3.11)
Your message dated Mon, 12 Jun 2023 09:03:30 +
with message-id
and subject line Bug#1034609: fixed in sqlacodegen 3.0.0~rc2-2
has caused the Debian Bug report #1034609,
regarding Fails to start under Python 3.11
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.)
--
1034609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sqlacodegen
Version: 1.1.6-4
Severity: grave
Tags: upstream fixed-upstream
The package fails to import under Python 3.11 with the following traceback:
Traceback (most recent call last):
File "/usr/bin/sqlacodegen", line 33, in
sys.exit(load_entry_point('sqlacodegen==1.1.6', 'console_scripts',
'sqlacodegen')())
File "/usr/bin/sqlacodegen", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1206, in _gcd_import
File "", line 1178, in _find_and_load
File "", line 1149, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/sqlacodegen/main.py", line 10, in
from sqlacodegen.codegen import CodeGenerator
File "/usr/lib/python3/dist-packages/sqlacodegen/codegen.py", line 4, in
from inspect import ArgSpec
ImportError: cannot import name 'ArgSpec' from 'inspect'
(/usr/lib/python3.11/inspect.py)
The issue seems to have been fixed in the latest release candidate, but that
isn't really suitable for bookworm during the freeze, so the intent of this
bug is to cause the package to be dropped from the release.
-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (990, 'testing-security'), (990, 'testing'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sqlacodegen depends on:
ii python3 3.11.2-1+b1
ii python3-inflect 2.1.0-4
ii python3-sqlalchemy 1.4.46+ds1-1
sqlacodegen recommends no packages.
sqlacodegen suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sqlacodegen
Source-Version: 3.0.0~rc2-2
Done: Arto Jantunen
We believe that the bug you reported is fixed in the latest version of
sqlacodegen, 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 1034...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Arto Jantunen (supplier of updated sqlacodegen package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 12 Jun 2023 10:50:57 +0300
Source: sqlacodegen
Architecture: source
Version: 3.0.0~rc2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Arto Jantunen
Closes: 1034609
Changes:
sqlacodegen (3.0.0~rc2-2) unstable; urgency=medium
.
* Upload to unstable.
.
sqlacodegen (3.0.0~rc2-1) experimental; urgency=medium
.
[ Debian Janitor ]
* Update standards version to 4.6.2, no changes needed.
.
[ Arto Jantunen ]
* Wrap-and-sort build-deps
* Enable running the testsuite during build
* New upstream release candidate
+ Adds support for Python 3.11 (Closes: #1034609)
* Update build-deps for new upstream release
* Apply patch to accept a different import order in the generate code
* Enable autopkgtests using autopkgtest-pkg-pybuild
Checks
Bug#1037364: nextcloud-desktop: TLS initilization failed
Package: nextcloud-desktop Version: 3.7.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, Nexcloud-Desktop is unable to connect the Nextcloud Server comaplining TLS initialization failed. SSL Cert on Server is valid. Access with browser and from another computer still on Debian 11 works as expected. * What led up to the situation? Upgrade from Debian 11 to Debian 12 * What exactly did you do (or not do) that was effective (or ineffective)? Searching via Google hints to an issue with QT and SSL Version. * What was the outcome of this action? No solution found yet -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=de_CH:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nextcloud-desktop depends on: ii libc6 2.36-9 ii libcloudproviders0 0.3.1-2 ii libgcc-s1 12.2.0-14 ii libglib2.0-0 2.74.6-2 ii libkf5archive5 5.103.0-1 ii libnextcloudsync0 3.7.3-1 ii libqt5core5a 5.15.8+dfsg-11 ii libqt5dbus55.15.8+dfsg-11 ii libqt5gui5 5.15.8+dfsg-11 ii libqt5keychain10.13.2-5 ii libqt5network5 5.15.8+dfsg-11 ii libqt5qml5 5.15.8+dfsg-3 ii libqt5quick5 5.15.8+dfsg-3 ii libqt5quickcontrols2-5 5.15.8+dfsg-2 ii libqt5sql5-sqlite 5.15.8+dfsg-11 ii libqt5svg5 5.15.8-3 ii libqt5webenginecore5 5.15.13+dfsg-1~deb12u1 ii libqt5webenginewidgets55.15.13+dfsg-1~deb12u1 ii libqt5widgets5 5.15.8+dfsg-11 ii libstdc++6 12.2.0-14 ii nextcloud-desktop-common 3.7.3-1 ii nextcloud-desktop-l10n 3.7.3-1 ii qml-module-qt-labs-platform5.15.8+dfsg-2 ii qml-module-qtgraphicaleffects 5.15.8-2 ii qml-module-qtqml 5.15.8+dfsg-3 ii qml-module-qtqml-models2 5.15.8+dfsg-3 ii qml-module-qtquick-controls2 5.15.8+dfsg-2 ii qml-module-qtquick-dialogs 5.15.8-2 ii qml-module-qtquick-layouts 5.15.8+dfsg-3 ii qml-module-qtquick-window2 5.15.8+dfsg-3 ii qml-module-qtquick25.15.8+dfsg-3 Versions of packages nextcloud-desktop recommends: ii nextcloud-desktop-doc 3.7.3-1 nextcloud-desktop suggests no packages. -- no debconf information
Bug#1037345: [Pkg-freeipa-devel] Bug#1037345: 389-ds-base: ftbfs with rust-base64 0.21
plugwash kirjoitti 11.6.2023 klo 22.29: Package: 389-ds-base Version: 2.3.1+dfsg1-1 Tags: trixie, sid, ftbfs 389-ds-base FTBFS with the new version of rust-base64. I attach a patch which makes the package build, and also fixes some packaging annoyances. I have not tested it beyond that. I may or may not NMU this later. merged thanks, but not uploaded as there seem to be other issues now with the dependencies being unable to install at least on my sbuilder -- t
