Processed: retitle 1030129 to ca-certificates-java - Fails to install: Error loading java.security file

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1030129 ca-certificates-java - Fails to install: Error loading 
> java.security file
Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install 
with OpenJDK 21: Error loading java.security file
Changed Bug title to 'ca-certificates-java - Fails to install: Error loading 
java.security file' from 'ca-certificates-java - Fails to install with OpenJDK 
21: Error loading java.security file'.
> 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#1030129: ca-certificates-java - Fails to install with OpenJDK 21: Error loading java.security file

[Sebastiaan Couwenberg]

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)

dpkg: error processing package ca-certificates-java (--configure):
 installed ca-certificates-java package post-installation script 
subprocess returned error exit status 1

Setting up liblwp-protocol-https-perl (6.10-1) ...
Setting up default-jre-headless (2:1.17-74) ...
Setting up libwww-perl (6.70-1) ...
Setting up ant (1.10.13-1) ...
dpkg: dependency problems prevent configuration of 
openjdk-17-jre-headless:amd64:
 openjdk-17-jre-headless:amd64 depends on ca-certificates-java (>= 
20190405~); however:

  Package ca-certificates-java is not configured yet.

dpkg: error processing package openjdk-17-jre-headless:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libxml-parser-perl (2.46-4) ...
dpkg: dependency problems prevent configuration of openjdk-17-jre:amd64:
 openjdk-17-jre:amd64 depends on openjdk-17-jre-headless (= 
17.0.7+7-1); however:

  Package openjdk-17-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-17-jre:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of default-jre:
 default-jre depends on openjdk-17-jre; however:
  Package openjdk-17-jre:amd64 is not configured yet.

dpkg: error processing package default-jre (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-17-jdk:amd64:
 openjdk-17-jdk:amd64 depends on openjdk-17-jre (= 17.0.7+7-1); however:
  Package openjdk-17-jre:amd64 is not configured yet.

dpkg: error processing package openjdk-17-jdk:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of 
openjdk-17-jdk-headless:amd64:
 openjdk-17-jdk-headless:amd64 depends on openjdk-17-jre-headless (= 
17.0.7+7-1); however:

  Package openjdk-17-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-17-jdk-headless:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libxml-sax-expat-perl (0.51-2) ...
update-perl-sax-parsers: Registering Perl SAX parser XML::SAX::Expat 
with priority 50...
update-perl-sax-parsers: Updating overall Perl SAX parser modules info 
file...

Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
dpkg: dependency problems prevent configuration of default-jdk:
 default-jdk depends on default-jre (= 2:1.17-74); however:
  Package default-jre is not configured yet.
 default-jdk depends on openjdk-17-jdk; however:
  Package openjdk-17-jdk:amd64 is not configured yet.

dpkg: error processing package default-jdk (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of default-jdk-headless:
 default-jdk-headless depends on openjdk-17-jdk-headless; however:
  Package openjdk-17-jdk-headless:amd64 is not configured yet.

dpkg: error processing package default-jdk-headless (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9) ...
Processing triggers for sgml-base (1.31) ...
Setting up docbook-xsl (1.79.2+dfsg-2) ...
Setting up sgml-data (2.0.11+nmu1) ...
Setting up docbook2x (0.8.8-17+b1) ...
Processing triggers for sgml-base (1.31) ...
Setting up docbook-xml (4.5-12) ...
Processing triggers for ca-certificates (20230311) ...
Updating certificates 

Processed: affects 1030129

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1030129 src:mapserver
Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install 
with OpenJDK 21: Error loading java.security file
Added indication that 1030129 affects src:mapserver
> 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#1037351: hippotat: ftbfs with rust-base64 0.21

[Peter Green]

sorry i over-filtered the debdiff, I think this one is correctly filtered.
diff -Nru hippotat-1.1.7/Cargo.toml hippotat-1.1.7+nmu1/Cargo.toml
--- hippotat-1.1.7/Cargo.toml   2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/Cargo.toml  2023-06-11 19:36:36.0 +
@@ -30,7 +30,7 @@
 # versions specified here are mostly just guesses at what is needed
 # (or currently available):
 backtrace = "0.3"
-base64 = "0.13" # 0.20 has substantially incompatible API (there's no 0.14)
+base64 = "0.21" # 0.20 has substantially incompatible API (there's no 0.14)
 clap = { version = "3", features = ["derive"] }
 easy-ext = "1"
 educe = "0.4"
diff -Nru hippotat-1.1.7/client/client.rs hippotat-1.1.7+nmu1/client/client.rs
--- hippotat-1.1.7/client/client.rs 2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/client/client.rs2023-06-11 19:36:38.0 
+
@@ -71,7 +71,7 @@
   //dbg!(DumpHex());
   let mut token = time_t;
   write!(token, " ").unwrap();
-  base64::encode_config_buf(hmac, BASE64_CONFIG,  token);
+  BASE64_CONFIG.encode_string(hmac,  token);
 
   let req_num = { *req_num += 1; *req_num };
 
diff -Nru hippotat-1.1.7/debian/changelog hippotat-1.1.7+nmu1/debian/changelog
--- hippotat-1.1.7/debian/changelog 2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/debian/changelog2023-06-11 19:36:38.0 
+
@@ -1,3 +1,11 @@
+hippotat (1.1.7+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump base64 dependency to 0.21 and fix code to build with it.
+  * Make debian dependency on base64 match the versioing in Cargo.toml.
+
+ -- Peter Michael Green   Sun, 11 Jun 2023 19:36:38 +
+
 hippotat (1.1.7) unstable; urgency=medium
 
   Build system:
diff -Nru hippotat-1.1.7/debian/control hippotat-1.1.7+nmu1/debian/control
--- hippotat-1.1.7/debian/control   2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/debian/control  2023-06-11 19:36:29.0 +
@@ -9,7 +9,7 @@
moreutils, libssl-dev (>= 1.1), pkg-config,
 # debian/update-build-deps manages these:
 librust-backtrace-dev ,
-librust-base64-dev ,
+librust-base64-0.21-dev ,
 librust-clap-3+derive-dev ,
 librust-easy-ext-dev ,
 librust-educe-dev ,
diff -Nru hippotat-1.1.7/server/sweb.rs hippotat-1.1.7+nmu1/server/sweb.rs
--- hippotat-1.1.7/server/sweb.rs   2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/server/sweb.rs  2023-06-11 19:36:38.0 +
@@ -121,7 +121,7 @@
   let time_t = u64::from_str_radix(time_t, 16).context("parse time_t")?;
   let l = io::copy(
  base64::read::DecoderReader::new( hmac_b64.as_bytes(),
-  BASE64_CONFIG),
+  _CONFIG),
   hmac_got[..]
   ).context("parse b64 token")?;
   let l = l.try_into()?;
diff -Nru hippotat-1.1.7/src/prelude.rs hippotat-1.1.7+nmu1/src/prelude.rs
--- hippotat-1.1.7/src/prelude.rs   2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/src/prelude.rs  2023-06-11 19:36:38.0 +
@@ -83,6 +83,7 @@
 
 pub const MAX_OVERHEAD: usize = 2_000;
 
-pub use base64::STANDARD as BASE64_CONFIG;
+pub use base64::engine::Engine;
+pub use base64::engine::general_purpose::STANDARD as BASE64_CONFIG;
 
 pub fn default() -> T { Default::default() }

Processed: fix severity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1037345 serious
Bug #1037345 [389-ds-base] 389-ds-base: ftbfs with rust-base64 0.21
Severity set to 'serious' from 'normal'
> severity 1037351 serious
Bug #1037351 [hippotat] hippotat: ftbfs with rust-base64 0.21
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037345
1037351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037352: pushpin: ftbfs with rust-base64 0.21

[Peter Green]

Package: pushpin
Version: 1.36.0-2
Severity: serious
Tags: trixie, sid, ftbfs, patch

pushpin FTBFS with the new version of rust-base64 due to an upper limit
on the dependency in Cargo.toml. If I remove the upper limit then the code
builds fine.

(I prepared a debdiff, but it ended up with a bunch of noise left behind
from the build process, so I haven't bothered including it).

Bug#1036706: marked as done (xerial-sqlite-jdbc: CVE-2023-32697)

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 22:29:09 +
with message-id 
and subject line Bug#1036706: fixed in xerial-sqlite-jdbc 3.42.0.0+dfsg-1
has caused the Debian Bug report #1036706,
regarding xerial-sqlite-jdbc: CVE-2023-32697
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.)


-- 
1036706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xerial-sqlite-jdbc
Version: 3.40.1.0+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for xerial-sqlite-jdbc.

CVE-2023-32697[0]:
| SQLite JDBC is a library for accessing and creating SQLite database
| files in Java. Sqlite-jdbc addresses a remote code execution
| vulnerability via JDBC URL. This issue impacting versions 3.6.14.1
| through 3.41.2.1 and has been fixed in version 3.41.2.2.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-32697
https://www.cve.org/CVERecord?id=CVE-2023-32697
[1] 
https://github.com/xerial/sqlite-jdbc/security/advisories/GHSA-6phf-6h5g-97j2

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xerial-sqlite-jdbc
Source-Version: 3.42.0.0+dfsg-1
Done: Pierre Gruet 

We believe that the bug you reported is fixed in the latest version of
xerial-sqlite-jdbc, 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 1036...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated xerial-sqlite-jdbc 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: Sun, 11 Jun 2023 23:16:54 +0200
Source: xerial-sqlite-jdbc
Architecture: source
Version: 3.42.0.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Pierre Gruet 
Closes: 1036706
Changes:
 xerial-sqlite-jdbc (3.42.0.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 3.42.0.0+dfsg:
 - Fixes CVE-2023-32697 (Closes: #1036706)
   * Refreshing patches
   * Stopping shipping the removed README.md file
   * Building without graal-sdk, which is unpackaged
   * Updating d/maven.ignoreRules for plugins to skip
   * Set upstream metadata fields: Security-Contact.
   * Removing unused Lintian override
Checksums-Sha1:
 2828e75f70d7896328175b14e3a5a8399487ce8c 2475 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1.dsc
 2068c02b46e4d76c12d20f032d240661a9d0b34b 172908 
xerial-sqlite-jdbc_3.42.0.0+dfsg.orig.tar.xz
 a533a5a71b91670063ae6c36514206ba4b7400e0 10380 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1.debian.tar.xz
 950ea2e1a69d24eafa0fd4fc330527e091f877d1 14771 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 6d01359ac5a1318a28cbb8da018c3437d4cd4bd3f733751e97170411a0e359de 2475 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1.dsc
 8521c97faf3358c004bb99a36ec5d11e4b3b95cf33cbeaa6897bbb81ab545790 172908 
xerial-sqlite-jdbc_3.42.0.0+dfsg.orig.tar.xz
 e39cb3d2967472702efa31302beef9378bfffcff2c37f63de2ae689f1f4d2c81 10380 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1.debian.tar.xz
 dabea8a699bb3bc181e7c33a8086f8daece8d99ad0d3c9f6074c22b3387b00dd 14771 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1_amd64.buildinfo
Files:
 083f4f8e21e4ab66073dfed7e96cc5e7 2475 java optional 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1.dsc
 67d7b4ae247698bce6b278bec4015cf8 172908 java optional 
xerial-sqlite-jdbc_3.42.0.0+dfsg.orig.tar.xz
 f5a1556820e02bf788490853a5ed04ee 10380 java optional 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1.debian.tar.xz
 3e4a5eb24acaaf6bee4ec162f96ba808 14771 java optional 
xerial-sqlite-jdbc_3.42.0.0+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmSGPdAACgkQYAMWptwn
dHYIFRAAtaC325q3WQtnMutw0G63qJvbZbGQu+z0WkZUOphsqUrj4IZ7CcLni2mI
TFxq2qsvscF352ynUHe107aqf1pxr/kEY8EX9Hl0COCXq4uLx+AhK0Mct1W6D3TR
BbyZgXNXiuCNCuw4R3Do5BGWu4LxjSuJFa2p/8+jhyJ3zEXDcOKNaILCSkNZUelU
KForb6fxx0SCFPfG48GEAuHSNhGUc/XqCRIA+cnRkjFmvq+sHAQklJD9UUHdPodf

Bug#1033832: marked as done (php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt])

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 21:15:36 +
with message-id 
and subject line Bug#1033832: fixed in php-db 1.11.0-1
has caused the Debian Bug report #1033832,
regarding php-db: autopkgtest regression: FAIL 
DB::DB_Error[DB-1.11.0/tests/db_error.phpt]
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.)


-- 
1033832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: php-db
Version: 1.11.0-0.2
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since January 
2022. Can you please investigate the situation and fix it? I copied some 
of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-db/32099485/log.gz

autopkgtest [19:15:43]: test command1: [---
Running 5 tests
FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt]
FAIL DB::Error 2[DB-1.11.0/tests/db_error2.phpt]
PASS DB::factory[DB-1.11.0/tests/db_factory.phpt]
PASS DB::isManip[DB-1.11.0/tests/db_ismanip.phpt]
PASS DB::parseDSN[DB-1.11.0/tests/db_parsedsn.phpt]
wrote log to 
"/tmp/autopkgtest-lxc.6vbl_673/downtmp/build.SoM/src/run-tests.log"

TOTAL TIME: 00:00
3 PASSED TESTS
0 SKIPPED TESTS
2 FAILED TESTS:
/tmp/autopkgtest-lxc.6vbl_673/downtmp/build.SoM/src/DB-1.11.0/tests/db_error.phpt
/tmp/autopkgtest-lxc.6vbl_673/downtmp/build.SoM/src/DB-1.11.0/tests/db_error2.phpt
Some tests failed
autopkgtest [19:15:44]: test command1: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: php-db
Source-Version: 1.11.0-1
Done: James Valleroy 

We believe that the bug you reported is fixed in the latest version of
php-db, 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.
James Valleroy  (supplier of updated php-db 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: Sun, 11 Jun 2023 15:45:06 -0400
Source: php-db
Architecture: source
Version: 1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: James Valleroy 
Closes: 1033832
Changes:
 php-db (1.11.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ William Desportes ]
   * Add a patch to fix test failures
   * Add a patch for PHP 8.2 dynamic properties (Closes: #1033832)
Checksums-Sha1:
 989e1b139e54b125326716ad33af6b6d3cecb62e 2040 php-db_1.11.0-1.dsc
 17276f669127449ab1eef1683020543980d8f6f7 7116 php-db_1.11.0-1.debian.tar.xz
 b6419ffdd573ba29470e7f2edc11f4c369d63574 7695 php-db_1.11.0-1_amd64.buildinfo
Checksums-Sha256:
 e77167c1e8fe6b40b86cb9e47f6748014bcf93e99eff321c3b49853c539000e9 2040 
php-db_1.11.0-1.dsc
 e2233424a6465f5315b64d1bc1f0fc111bd0bc1654c18f4637450c8a0bcb6d2f 7116 
php-db_1.11.0-1.debian.tar.xz
 07d9e5fd8a19841d2cac4644c52b04f23a0dd585bc385229b5016c8e4c4f00c8 7695 
php-db_1.11.0-1_amd64.buildinfo
Files:
 05127fca87f457688b29b1f45f429a22 2040 php optional php-db_1.11.0-1.dsc
 7b9918a40d773576fed18dbdfb8db1c1 7116 php optional 
php-db_1.11.0-1.debian.tar.xz
 7eba80db18254e70f437e720934c4dc3 7695 php optional 
php-db_1.11.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmSGJ+AWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICOMTEACsj5LUFq/kOup7NyfaifJtjIeU
J6gXCFsn6x2uOril6p/nbHQAyBtz6FWb7Xp1KnlxFmrZr1Vnr0tPt02qAVU176m8
IWDrMIy1PtNJ5yJfTwtde24b98kMZIRQ13kss5kpHUUhDXDxxbhHreKyu1CWh0xV

Processed: [bts-link] source package src:frr

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:frr
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1036061 (http://bugs.debian.org/1036061)
> # Bug title: frr: CVE-2023-31489
> #  * https://github.com/FRRouting/frr/issues/13098
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1036061 + fixed-upstream
Bug #1036061 [src:frr] frr: CVE-2023-31489
Added tag(s) fixed-upstream.
> usertags 1036061 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1036062 (http://bugs.debian.org/1036062)
> # Bug title: frr: CVE-2023-31490
> #  * https://github.com/FRRouting/frr/issues/13099
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1036062 + fixed-upstream
Bug #1036062 [src:frr] frr: CVE-2023-31490
Added tag(s) fixed-upstream.
> usertags 1036062 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036061
1036062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package python-flanker

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package python-flanker
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1033714 (http://bugs.debian.org/1033714)
> # Bug title: at runtime, flanker tries to create files under /usr
> #  * https://github.com/mailgun/flanker/pull/250
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1033714 + fixed-upstream
Bug #1033714 [python3-flanker] at runtime, flanker tries to create files under 
/usr
Added tag(s) fixed-upstream.
> usertags 1033714 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1033714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package odoo

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package odoo
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1032300 (http://bugs.debian.org/1032300)
> # Bug title: odoo-14: Not functional with pypdf2 2.x
> #  * https://github.com/odoo/odoo/pull/112611
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1032300 + fixed-upstream
Bug #1032300 [odoo-14] odoo-14: Not functional with pypdf2 2.x
Added tag(s) fixed-upstream.
> usertags 1032300 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:xdg-desktop-portal-gnome

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package 
> src:xdg-desktop-portal-gnome
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1032584 (http://bugs.debian.org/1032584)
> # Bug title: xdg-desktop-portal-gnome: 44 causes long delay in portal apps 
> for non-GNOME desktops
> #  * https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/74
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1032584 + fixed-upstream
Bug #1032584 [src:xdg-desktop-portal-gnome] xdg-desktop-portal-gnome: 44 causes 
long delay in portal apps for non-GNOME desktops
Added tag(s) fixed-upstream.
> usertags 1032584 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:eztrace-contrib

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:eztrace-contrib
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #968312 (http://bugs.debian.org/968312)
> # Bug title: eztrace-contrib: FTBFS with CUDA 11: cuda_runtime.cu(92): error: 
> function "cudaMalloc(void **, size_t)" has already been defined
> #  * https://gitlab.com/eztrace/eztrace/-/issues/22
> #  * remote status changed: opened -> closed
> #  * closed upstream
> tags 968312 + fixed-upstream
Bug #968312 [src:eztrace-contrib] eztrace-contrib: FTBFS with CUDA 11: 
cuda_runtime.cu(92): error: function "cudaMalloc(void **, size_t)" has already 
been defined
Added tag(s) fixed-upstream.
> usertags 968312 - status-opened
Usertags were: status-opened.
There are now no usertags set.
> usertags 968312 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
968312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package procps

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package procps
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1001689 (http://bugs.debian.org/1001689)
> # Bug title: /usr/bin/free: misaligned columns in localized output
> #  * https://gitlab.com/procps-ng/procps/-/issues/229
> #  * remote status changed: opened -> closed
> #  * closed upstream
> tags 1001689 + fixed-upstream
Bug #1001689 [procps] /usr/bin/free: misaligned columns in localized output
Added tag(s) fixed-upstream.
> usertags 1001689 - status-opened
Usertags were: status-opened.
There are now no usertags set.
> usertags 1001689 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1031765 (http://bugs.debian.org/1031765)
> # Bug title: pgrep: signal handler matching breaks argument parsing
> #  * https://github.com/ganeti/ganeti/issues/1691
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1031765 + fixed-upstream
Bug #1031765 [procps] pgrep: signal handler matching breaks argument parsing
Added tag(s) fixed-upstream.
> usertags 1031765 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1001689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001689
1031765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:jamm

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:jamm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1011775 (http://bugs.debian.org/1011775)
> # Bug title: jamm: FTBFS with OpenJDK 17 due to an illegal reflective access 
> during the tests
> #  * https://github.com/jbellis/jamm/issues/48
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1011775 + fixed-upstream
Bug #1011775 [src:jamm] jamm: FTBFS with OpenJDK 17 due to an illegal 
reflective access during the tests
Added tag(s) fixed-upstream.
> usertags 1011775 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1011775 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:ccextractor

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:ccextractor
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1004581 (http://bugs.debian.org/1004581)
> # Bug title: ccextractor: FTBFS with ffmpeg 5.0
> #  * https://github.com/CCExtractor/ccextractor/issues/1418
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1004581 + fixed-upstream
Bug #1004581 [src:ccextractor] ccextractor: FTBFS with ffmpeg 5.0
Added tag(s) fixed-upstream.
> usertags 1004581 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1004581 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1004581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:pybdsf

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:pybdsf
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1024499 (http://bugs.debian.org/1024499)
> # Bug title: pybdsf: FTBFS with Python 3.11 as a supported version
> #  * https://github.com/lofar-astron/PyBDSF/issues/189
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1024499 + fixed-upstream
Bug #1024499 [src:pybdsf] pybdsf: FTBFS with Python 3.11 as a supported version
Added tag(s) fixed-upstream.
> usertags 1024499 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1024499 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1024499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:numba

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:numba
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1020445 (http://bugs.debian.org/1020445)
> # Bug title: numba: autopkgtest regression on ppc64el: inf != 0.625
> #  * https://github.com/numba/numba/issues/8489
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1020445 + fixed-upstream
Bug #1020445 [src:numba] numba: autopkgtest regression on ppc64el: inf != 0.625
Added tag(s) fixed-upstream.
> usertags 1020445 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1020445 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1036280: marked as done (openjdk-11: CVE-2023-21930 CVE-2023-21937 CVE-2023-21938 CVE-2023-21939 CVE-2023-21954 CVE-2023-21967 CVE-2023-21968)

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 21:11:04 +0200
with message-id 
and subject line [ftpmas...@ftp-master.debian.org: Accepted openjdk-11 
11.0.19+7-1 (source) into unstable]
has caused the Debian Bug report #1036280,
regarding openjdk-11: CVE-2023-21930 CVE-2023-21937 CVE-2023-21938 
CVE-2023-21939 CVE-2023-21954 CVE-2023-21967 CVE-2023-21968
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.)


-- 
1036280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-11
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for openjdk-11.

CVE-2023-21930[0]:
| Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition
| product of Oracle Java SE (component: JSSE). Supported versions that
| are affected are Oracle Java SE: 8u361, 8u361-perf, 11.0.18, 17.0.6,
| 20; Oracle GraalVM Enterprise Edition: 20.3.9, 21.3.5 and 22.3.1.
| Difficult to exploit vulnerability allows unauthenticated attacker
| with network access via TLS to compromise Oracle Java SE, Oracle
| GraalVM Enterprise Edition. Successful attacks of this vulnerability
| can result in unauthorized creation, deletion or modification access
| to critical data or all Oracle Java SE, Oracle GraalVM Enterprise
| Edition accessible data as well as unauthorized access to critical
| data or complete access to all Oracle Java SE, Oracle GraalVM
| Enterprise Edition accessible data. Note: This vulnerability applies
| to Java deployments, typically in clients running sandboxed Java Web
| Start applications or sandboxed Java applets, that load and run
| untrusted code (e.g., code that comes from the internet) and rely on
| the Java sandbox for security. This vulnerability can also be
| exploited by using APIs in the specified Component, e.g., through a
| web service which supplies data to the APIs. CVSS 3.1 Base Score 7.4
| (Confidentiality and Integrity impacts). CVSS Vector:
| (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).


CVE-2023-21937[1]:
| Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition
| product of Oracle Java SE (component: Networking). Supported versions
| that are affected are Oracle Java SE: 8u361, 8u361-perf, 11.0.18,
| 17.0.6, 20; Oracle GraalVM Enterprise Edition: 20.3.9, 21.3.5 and
| 22.3.1. Difficult to exploit vulnerability allows unauthenticated
| attacker with network access via multiple protocols to compromise
| Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks
| of this vulnerability can result in unauthorized update, insert or
| delete access to some of Oracle Java SE, Oracle GraalVM Enterprise
| Edition accessible data. Note: This vulnerability applies to Java
| deployments, typically in clients running sandboxed Java Web Start
| applications or sandboxed Java applets, that load and run untrusted
| code (e.g., code that comes from the internet) and rely on the Java
| sandbox for security. This vulnerability can also be exploited by
| using APIs in the specified Component, e.g., through a web service
| which supplies data to the APIs. CVSS 3.1 Base Score 3.7 (Integrity
| impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).


CVE-2023-21938[2]:
| Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition
| product of Oracle Java SE (component: Libraries). Supported versions
| that are affected are Oracle Java SE: 8u361, 8u361-perf, 11.0.18,
| 17.0.6, 20; Oracle GraalVM Enterprise Edition: 20.3.8, 21.3.4 and
| 22.3.0. Difficult to exploit vulnerability allows unauthenticated
| attacker with network access via multiple protocols to compromise
| Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks
| of this vulnerability can result in unauthorized update, insert or
| delete access to some of Oracle Java SE, Oracle GraalVM Enterprise
| Edition accessible data. Note: This vulnerability applies to Java
| deployments, typically in clients running sandboxed Java Web Start
| applications or sandboxed Java applets, that load and run untrusted
| code (e.g., code that comes from the internet) and rely on the Java
| sandbox for security. This vulnerability does not apply to Java
| deployments, typically in servers, that load and run only trusted code
| (e.g., code installed by an administrator). CVSS 3.1 Base Score 3.7
| (Integrity impacts). CVSS Vector:
| (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).


CVE-2023-21939[3]:
| Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition
| product of 

Bug#1036280: [ftpmas...@ftp-master.debian.org: Accepted openjdk-11 11.0.19+7-1 (source) into unstable]

[Salvatore Bonaccorso]

Source: openjdk-11
Source-Version: 11.0.19+7-1

Fixes as well #1036280, so closing manually:

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 Jun 2023 12:55:28 +0200
Source: openjdk-11
Architecture: source
Version: 11.0.19+7-1
Distribution: unstable
Urgency: high
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Changes:
 openjdk-11 (11.0.19+7-1) unstable; urgency=high
 .
   * OpenJDK 11.0.19 release, build 7.
 - CVE-2023-21930, CVE-2023-21937, CVE-2023-21938, CVE-2023-21939,
   CVE-2023-21954, CVE-2023-21967, CVE-2023-21968.
 - Release notes:
   https://mail.openjdk.org/pipermail/jdk-updates-dev/2023-April/021900.html
 - d/p/*: refresh patches.
 .
   [ Vladimir Petko ]
   * debian/JB-jre-headless.postinst.in: trigger ca-certificates-java after jre
 is set up.
   * d/p: drop obsolete patches (LP: #2011653).
 - workaround_expand_exec_shield_cs_limit.diff: obsoleted by
   hotspot-disable-exec-shield-workaround.diff.
 - generated-headers.patch: include is already added by openjdk makefile.
 - parallel-build-fix.diff: include is not necessary.
   * d/copyright, d/watch: implement uscan repackaging (LP: #2011749).
   * d/rules: use --with-debug-symbols=none (LP: #2003820).
   * d/control: add jtreg6 dependencies, regenerate control.
   * d/t/{jdk,hotspot,jaxp,langtools}: run tier1 and tier2 jtreg tests only,
 add test options from OpenJDK makefile.
   * d/t/*: fix test environment: add missing -nativepath (LP: #2001563).
   * d/t/jdk: provide dbus session for the window manager (LP: #2001576).
   * d/p/*: add patches for jtreg tests:
 - disable-thumb-assertion.patch: fix JDK-8305481.
 - update-assertion-for-armhf.patch: fix JDK-8305480.
 - log-generated-classes-test.patch: workaround JDK-8166162.
 - update-permission-test.patch: add security permissions for testng 7.
 - ldap-timeout-test-use-ip.patch, test-use-ip-address.patch: 
Ubuntu-specific
   patches to workaround missing DNS resolver on the build machines.
 - exclude_broken_tests.patch: quarantine failing tests.
   * d/rules: package external debug symbols (LP: #2015835).
   * drop d/p/{jaw-classpath.diff, jaw-optional.diff}: the atk wrapper is 
disabled
 and these patches cause class data sharing tests to fail (LP: #2016194).
   * d/p/exclude-broken-tests.patch: add OpenJDK 11 failures.
   * d/t/jtreg-autopkgtest.in: pass JTREG home to locate junit.jar, regenerate
 d/t/jtreg-autopkgtest.sh (LP: #2016206).
   * d/t/control.in: disable jtreg autopkgtests in line with openjdk 17,
 regenerate control (LP: #2016438).
   * d/rules: pack external debug symbols with build-id, do not pack duplicate
 symbols, do not strip JVM shared libraries (LP: #2012326, LP: #2016739).
   * d/rules: always use jtreg6.
 .
   [ Matthias Klose ]
   * d/rules: Fix using CC/CXX for recent releases.
Checksums-Sha1:
 38ed90cfba304561c4aedb5231cec209040eabd0 4600 openjdk-11_11.0.19+7-1.dsc
 bf2ecbb084c3ae6b51fdcff3bf6403b9c09d58fd 78706772 
openjdk-11_11.0.19+7.orig.tar.xz
 ca228c0ee6838c9c4a76a75ced8f33948bf7c6f6 160416 
openjdk-11_11.0.19+7-1.debian.tar.xz
 4c62e92c386a6e432d892a901b112a2390938bcd 15430 
openjdk-11_11.0.19+7-1_source.buildinfo
Checksums-Sha256:
 da3f0f2f788576285f11c250e0cbfd913a9773a655e7cbb30394b93475a98d9c 4600 
openjdk-11_11.0.19+7-1.dsc
 8aeb8c865b11b102268bcea4e0e9d1dc39c1b0596b8ec0fb184dd2deed5b8b61 78706772 
openjdk-11_11.0.19+7.orig.tar.xz
 490efad4888f606a82e1021983d0f1aa44c12132357797aa5147fca27a890b62 160416 
openjdk-11_11.0.19+7-1.debian.tar.xz
 7c20e50d71bd1d4e22b5637da89db5e00d2a5ad4c1a93dbc17c6fbe7334257f3 15430 
openjdk-11_11.0.19+7-1_source.buildinfo
Files:
 9ac81a9ef773773ccc4dc28dd7d34553 4600 java optional openjdk-11_11.0.19+7-1.dsc
 ff2769235b5aae5c116e19a104d26397 78706772 java optional 
openjdk-11_11.0.19+7.orig.tar.xz
 9cc4c03e13388e480a52c9158ae04ff2 160416 java optional 
openjdk-11_11.0.19+7-1.debian.tar.xz
 1351e8f6e9266f524f15c88a789ea7a2 15430 java optional 
openjdk-11_11.0.19+7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmSFqD8QHGRva29AdWJ1
bnR1LmNvbQAKCRC9fqpgd4+m9WT8EAC8d7IgQiUTMHdVInW83J/sjB04b4WVXAxJ
zTcv28VTGnLvraGNqTkXNZxhz4iFEDxjzXUNrXImpongto2Vn/rIPa7VJWm204Vq
9u1r+ZlcfkmQYb1zdvNI2M/gulZJZTMnj91bN2WEJz7Vwtm+49otmwzcp3f50smo
jejmI4h/IVA6U8qyMLNHDAd+Na26ySjUyBTDF5GpUajczpmIRBROZveWn+qL3xfY
5xqG0rOv5077df8EpSPzzUqldKh7RRTMRsMR2YOBXe3RR0BVC0vT8ccFTtRzpxL5
LNO1yKEJhjiaARzWZYUUzUGxMBHVnUKRBmcRNjMO2uQ6KrrgENBC7MWpAKqVsqxc
qpeUkz1tPp3gO1xLIBoE14rSgulcQ/ZJf6cRaopkkaDgWFw8wbdy45F2pEUF693J
hBVuWbQB7+TNYutr8tFcod/1v9L5Uq6TQj/Vf0LWWpKt58fFEdc4INAZFXvKy6lP
EHlXFfk52WgJk55j3QDBq9hKdHp+c9aQItAlB2uh/venZq5qXQ2xtLmEg9Ph8xKt
ioAOfjo04Ks/xTPAEaDzEIXWhkKKWZdLjyXvisvBgsUZSjDm4KdEGsaDdu5n3iEN
7SEbf/7Er7K5aPCZTpH23uTvq962R5UKNK3s3VIpyRGRxFTEFRcvbhpnvMWHcX+u
Vl8bkjhM9g==
=YQZK
-END PGP SIGNATURE-


- End forwarded 

Processed: found 1036280 in 11.0.18+10-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1036280 11.0.18+10-1
Bug #1036280 [src:openjdk-11] openjdk-11: CVE-2023-21930 CVE-2023-21937 
CVE-2023-21938 CVE-2023-21939 CVE-2023-21954 CVE-2023-21967 CVE-2023-21968
Marked as found in versions openjdk-11/11.0.18+10-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: cpl-plugin-visir-calib: visir-kit-4.3.10*.tar.gz is no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.3.11+dfsg-1
Bug #1037339 [cpl-plugin-visir-calib] cpl-plugin-visir-calib: 
visir-kit-4.3.10*.tar.gz is no longer downloadable
Marked as fixed in versions cpl-plugin-visir/4.3.11+dfsg-1.

-- 
1037339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037339: cpl-plugin-visir-calib: visir-kit-4.3.10*.tar.gz is no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-visir-calib
Version: 4.3.10+dfsg-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 4.3.11+dfsg-1

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 cpl-plugin-visir-calib (4.3.10+dfsg-5) ...
  --2023-06-10 15:07:45--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:45 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:45--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-1.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:45 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:45--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-2.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:46 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:46--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-3.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:46 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:46--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-4.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:47 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:47--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-5.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:47 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:47--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-6.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:48 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:48--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-7.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:48 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:48--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-8.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:49 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2023-06-10 15:07:49--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-9.tar.gz
  Connecting to 10.99.30.1:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2023-06-10 15:07:49 ERROR 404: Not Found.


  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  dpkg: error processing package cpl-plugin-visir-calib (--configure):
   installed cpl-plugin-visir-calib package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.31-13+deb11u6) ...
  Errors were encountered while processing:
   cpl-plugin-visir-calib


cheers,

Andreas


cpl-plugin-visir-calib_4.3.10+dfsg-5.log.gz
Description: application/gzip

Bug#1036359: elpa-markdown-toc -- crashes with (wrong-type-argument consp nil)

[Nicholas D Steeves]

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)...

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#1036986: boost1.81: diff for NMU version 1.81.0-5.1

[Sebastian Ramacher]

Control: tags 1036986 + patch
Control: tags 1036986 + pending

Dear maintainer,

I've prepared an NMU for boost1.81 (versioned as 1.81.0-5.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru boost1.81-1.81.0/debian/changelog boost1.81-1.81.0/debian/changelog
--- boost1.81-1.81.0/debian/changelog	2023-05-14 22:52:13.0 +0200
+++ boost1.81-1.81.0/debian/changelog	2023-06-11 19:35:53.0 +0200
@@ -1,3 +1,11 @@
+boost1.81 (1.81.0-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Add dependency on libboost-json1.81.0 for
+libboost-json1.81-dev (Closes: #1036986)
+
+ -- Sebastian Ramacher   Sun, 11 Jun 2023 19:35:53 +0200
+
 boost1.81 (1.81.0-5) unstable; urgency=medium
 
   * [0330664] Better handling of the upstream version number
diff -Nru boost1.81-1.81.0/debian/control boost1.81-1.81.0/debian/control
--- boost1.81-1.81.0/debian/control	2023-05-14 22:51:28.0 +0200
+++ boost1.81-1.81.0/debian/control	2023-06-11 19:35:12.0 +0200
@@ -1502,6 +1502,7 @@
 Depends: ${misc:Depends},
  libboost1.81-dev (= ${binary:Version}),
  libboost-container1.81-dev (= ${binary:Version}),
+ libboost-json1.81.0 (= ${binary:Version}),
  libboost-system1.81-dev (= ${binary:Version})
 Conflicts: libboost-json1.80-dev
 Description: C++ containers and algorithms that implement JSON

Processed: boost1.81: diff for NMU version 1.81.0-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1036986 + patch
Bug #1036986 [libboost-json1.81-dev] libboost-json1.81-dev: missing Depends: 
libboost-json1.81.0 (= ${binary:Version})
Added tag(s) patch.
> tags 1036986 + pending
Bug #1036986 [libboost-json1.81-dev] libboost-json1.81-dev: missing Depends: 
libboost-json1.81.0 (= ${binary:Version})
Added tag(s) pending.

-- 
1036986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Downgrade #1031726 severity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1031726 important
Bug #1031726 [src:hdf5] hdf5: CVE-2022-26061 CVE-2022-25972 CVE-2022-25942
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1031726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034128:

[Andreas Hasenack]

Quick MP at 
https://salsa.debian.org/python-team/packages/cachelib/-/merge_requests/1

Bug#1021583: marked as done (golang-gitlab-gitlab-org-labkit: FTBFS (test failure): gitlab.com/gitlab-org/labkit/metrics/http_round_tripper)

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 18:49:45 +0530
with message-id 
and subject line Re: golang-gitlab-gitlab-org-labkit: FTBFS (test failure): 
gitlab.com/gitlab-org/labkit/metrics/http_round_tripper
has caused the Debian Bug report #1021583,
regarding golang-gitlab-gitlab-org-labkit: FTBFS (test failure): 
gitlab.com/gitlab-org/labkit/metrics/http_round_tripper
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.)


-- 
1021583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gitlab-gitlab-org-labkit
Version: 1.16.0-1
Severity: serious
Justification: FTBFS

Hi,

While preparing an update for the golang-github-gin-gonic-gin package,
I noticed golang-gitlab-gitlab-org-labkit FTBFSes within unstable
(with or without the updated golang-github-gin-gonic-gin package).

There's apparently a single test failing:

=== RUN   TestNewFactory
http_round_tripper_test.go:57: 
Error Trace:
/build/golang-gitlab-gitlab-org-labkit-1.16.0/_build/src/gitlab.com/gitlab-org/labkit/metrics/http_round_tripper/http_round_tripper_test.go:57
Error:  Received unexpected error:


Diff:
--- metric output does not match expectation; 
want
+++ got:
@@ -5,3 +5,3 @@
 # TYPE namespace_http_requests_total counter

-namespace_http_requests_total{code="200",label1="1",label2="1",method="get"} 1

+namespace_http_requests_total{code="200",label1="1",label2="1",method="get"} 2
 
Test:   TestNewFactory
--- FAIL: TestNewFactory (0.00s)
FAIL
FAILgitlab.com/gitlab-org/labkit/metrics/http_round_tripper 0.005s

I'm attaching a full build log (under pbuilder), best viewed with -R
due to ANSI sequences…


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.430463
I: forking: cp -al /var/cache/pbuilder/base.cow 
/var/cache/pbuilder/build/cow.430463
I: removed stale ilistfile /var/cache/pbuilder/build/cow.430463/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.430463 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --buildplace /var/cache/pbuilder/build/cow.430463 
--buildresult /var/cache/pbuilder/result/ --mirror http://debian.home/debian 
--distribution sid --no-targz --internal-chrootexec 'chroot 
/var/cache/pbuilder/build/cow.430463 cow-shell' 
/home/kibi/work/clients/crowdsec/git/salsa/golang-gitlab-gitlab-org-labkit_1.16.0-1.dsc
W: /root/.pbuilderrc does not exist
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Tue Oct 11 11:22:53 UTC 2022
I: pbuilder-time-stamp: 1665487373
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying 
[/home/kibi/work/clients/crowdsec/git/salsa/golang-gitlab-gitlab-org-labkit_1.16.0-1.dsc]
I: copying 
[/home/kibi/work/clients/crowdsec/git/salsa/golang-gitlab-gitlab-org-labkit_1.16.0.orig.tar.gz]
I: copying 
[/home/kibi/work/clients/crowdsec/git/salsa/golang-gitlab-gitlab-org-labkit_1.16.0-1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package 
(golang-gitlab-gitlab-org-labkit_1.16.0-1.dsc)
dpkg-source: info: extracting golang-gitlab-gitlab-org-labkit in 
golang-gitlab-gitlab-org-labkit-1.16.0
dpkg-source: info: unpacking golang-gitlab-gitlab-org-labkit_1.16.0.orig.tar.gz
dpkg-source: info: unpacking 
golang-gitlab-gitlab-org-labkit_1.16.0-1.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating 

Processed: Re: golang-gitlab-gitlab-org-labkit: FTBFS (test failure): gitlab.com/gitlab-org/labkit/metrics/http_round_tripper

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.17.0-1
Bug #1021583 [src:golang-gitlab-gitlab-org-labkit] 
golang-gitlab-gitlab-org-labkit: FTBFS (test failure): 
gitlab.com/gitlab-org/labkit/metrics/http_round_tripper
Marked as fixed in versions golang-gitlab-gitlab-org-labkit/1.17.0-1.

-- 
1021583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1021583: golang-gitlab-gitlab-org-labkit: FTBFS (test failure): gitlab.com/gitlab-org/labkit/metrics/http_round_tripper

[Pirate Praveen]

Control: fixed -1 1.17.0-1

On Tue, 11 Oct 2022 13:24:32 +0200 Cyril Brulebois  
wrote:

> Source: golang-gitlab-gitlab-org-labkit
> Version: 1.16.0-1
> Severity: serious
> Justification: FTBFS
>
> Hi,
>
> While preparing an update for the golang-github-gin-gonic-gin 
package,

> I noticed golang-gitlab-gitlab-org-labkit FTBFSes within unstable
> (with or without the updated golang-github-gin-gonic-gin package).
>

1.17.0-1 in experimental builds fine. I'm reuploading it to unstable.

Bug#1033822: marked as done (oscrypto: autopkgtest regression: certificate expired 2023-01-01 00:00:00Z)

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 13:09:50 +
with message-id 
and subject line Bug#1033822: fixed in oscrypto 1.3.0-2
has caused the Debian Bug report #1033822,
regarding oscrypto: autopkgtest regression: certificate expired 2023-01-01 
00:00:00Z
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.)


-- 
1033822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: oscrypto
Version: 1.3.0-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it started to fail on 
2023-01-01. Can you please investigate the situation and fix it? I 
copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/o/oscrypto/32095523/log.gz

==
ERROR: test_tls_connect_dh1024 
(tests.test_tls.TLSTests.test_tls_connect_dh1024)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.a4kfr24h/downtmp/autopkgtest_tmp/tests/unittest_data.py", 
line 51, in generated_test_function

original_function(self, *params)
  File 
"/tmp/autopkgtest-lxc.a4kfr24h/downtmp/autopkgtest_tmp/tests/test_tls.py", 
line 75, in wrapped

f(*args)
  File 
"/tmp/autopkgtest-lxc.a4kfr24h/downtmp/autopkgtest_tmp/tests/test_tls.py", 
line 102, in tls_connect

connection = tls.TLSSocket(hostname, port, session=session)
 ^^
  File "/usr/lib/python3/dist-packages/oscrypto/_openssl/tls.py", line 
456, in __init__

self._handshake()
  File "/usr/lib/python3/dist-packages/oscrypto/_openssl/tls.py", line 
674, in _handshake

raise_expired_not_yet_valid(cert)
  File "/usr/lib/python3/dist-packages/oscrypto/_tls.py", line 509, in 
raise_expired_not_yet_valid

raise TLSVerificationError(message, certificate)
oscrypto.errors.TLSVerificationError: Server certificate verification 
failed - certificate expired 2023-01-01 00:00:00Z


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: oscrypto
Source-Version: 1.3.0-2
Done: Jochen Sprickerhof 

We believe that the bug you reported is fixed in the latest version of
oscrypto, 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.
Jochen Sprickerhof  (supplier of updated oscrypto 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: Sun, 11 Jun 2023 14:29:25 +0200
Source: oscrypto
Architecture: source
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jochen Sprickerhof 
Closes: 1033822
Changes:
 oscrypto (1.3.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Switch to autopkgtest-pkg-pybuild (Closes: #1033822)
   * Bump policy version (no changes)
Checksums-Sha1:
 f22a0891a93ab0f1e5f0580e0c605615f8ddf995 2151 oscrypto_1.3.0-2.dsc
 884f8032ef7a4f2193392cfdfd232e066c5033b8 3312 oscrypto_1.3.0-2.debian.tar.xz
 d1d2ca2c39ccb67963d68699eabe825fbc2fa0ff 6714 oscrypto_1.3.0-2_source.buildinfo
Checksums-Sha256:
 fa8d1cedf9da6f1eb8da04dd9948ea1d868eaafdcf05a1d72b51574488470ff4 2151 
oscrypto_1.3.0-2.dsc
 b0df54d7095ecd60869fa63eb337976eaf8ef2cfcdee99400cef0f1ca0aa6ab1 3312 
oscrypto_1.3.0-2.debian.tar.xz
 85dda1ab61a4d55a3516c9c4f862202c907ffdb9c7bfe47d9e5642843f95d746 6714 
oscrypto_1.3.0-2_source.buildinfo
Files:
 

Processed: Re: gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother upgrades from bullseye

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #1036641 [gcc-12-base] gcc-12-base: please bump the Breaks: gnat (<< 12) 
for smoother upgrades from bullseye
Added tag(s) patch.

-- 
1036641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1036641: gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother upgrades from bullseye

[Andreas Beckmann]

Followup-For: Bug #1036641
Control: tag -1 patch

I've been running bullseye->bookworm upgrade tests with the following
change applied to src:gcc-12, this had the best results w.r.t. upgrading
gnat related packages:

--- gcc-12-12.2.0/debian/rules.conf 2023-01-02 14:06:37.0 +0100
+++ gcc-12-12.2.0/debian/rules.conf 2023-05-24 09:42:40.0 +0200
@@ -615,7 +615,7 @@
   arch_gnutype_map = $(DEB_TARGET_ARCH)=$(TARGET_ALIAS)
 endif # cross compiler

-BASE_BREAKS := gnat (<< 7)
+BASE_BREAKS := gnat (<< 12), gnat-10 (<< 10.3)
 # these would need proper updates, and are only needed for upgrades
 ifneq (,$(filter $(distrelease),stretch jessie trusty xenial bionic))
   BASE_BREAKS :=

The Breaks against gnat-10 is versioned in a way that gnat-10/sid stays
installable in sid.


Andreas

Bug#1033822: marked as pending in oscrypto

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #1033822 in oscrypto reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/oscrypto/-/commit/2785beddf7f492fb728df9fdfa53724ee3192bdc


Switch to autopkgtest-pkg-pybuild

This has also the effect that test_tls.py is no longer executed which
fails due to expired certificates.

Closes: #1033822


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1033822

Processed: Bug#1033822 marked as pending in oscrypto

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1033822 [src:oscrypto] oscrypto: autopkgtest regression: certificate 
expired 2023-01-01 00:00:00Z
Added tag(s) pending.

-- 
1033822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1019307: bluebird-gtk-theme: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1019307 [src:bluebird-gtk-theme] bluebird-gtk-theme: Please build-depend 
on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'normal'
> tags -1 + trixie sid
Bug #1019307 [src:bluebird-gtk-theme] bluebird-gtk-theme: Please build-depend 
on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev
Added tag(s) trixie and sid.

-- 
1019307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1019305: anjuta: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1019305 [src:anjuta] anjuta: Please build-depend on libgdk-pixbuf-2.0-dev 
instead of libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'normal'
> tags -1 + trixie sid
Bug #1019305 [src:anjuta] anjuta: Please build-depend on libgdk-pixbuf-2.0-dev 
instead of libgdk-pixbuf2.0-dev
Added tag(s) trixie and sid.

-- 
1019305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#976034: ukwm: Please depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #976034 [src:ukwm] ukwm: Please depend on libgdk-pixbuf-2.0-dev instead of 
libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'normal'
> tags -1 + trixie sid
Bug #976034 [src:ukwm] ukwm: Please depend on libgdk-pixbuf-2.0-dev instead of 
libgdk-pixbuf2.0-dev
Added tag(s) sid and trixie.

-- 
976034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1019304: adapta-gtk-theme: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1019304 [src:adapta-gtk-theme] adapta-gtk-theme: Please build-depend on 
libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev
Severity set to 'serious' from 'normal'
> tags -1 + trixie sid
Bug #1019304 [src:adapta-gtk-theme] adapta-gtk-theme: Please build-depend on 
libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev
Added tag(s) sid and trixie.

-- 
1019304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1036682 is serious, severity of 1036681 is serious, severity of 1036684 is serious ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1036682 serious
Bug #1036682 [src:slurm-wlm-contrib] slurm-wlm-contrib: FTBFS with CUDA 12: 
dh_install: warning: Cannot find "usr/lib/*/slurm-wlm/gpu_nvml.so"
Severity set to 'serious' from 'important'
> severity 1036681 serious
Bug #1036681 [src:relion-cuda] relion-cuda: FTBFS with CUDA 12: nvcc fatal   : 
Value 'sm_35' is not defined for option 'gpu-architecture'
Severity set to 'serious' from 'important'
> severity 1036684 serious
Bug #1036684 [src:tomopy] tomopy: FTBFS with CUDA 12: nvcc fatal   : 
Unsupported gpu architecture 'compute_35'
Severity set to 'serious' from 'important'
> severity 1036677 serious
Bug #1036677 [src:astra-toolbox] astra-toolbox: FTBFS with CUDA 12: 
../build/linux/../../cuda/2d/par_bp.cu(36): error: texture is not a template
Severity set to 'serious' from 'important'
> severity 1036679 serious
Bug #1036679 [src:magma] magma: FTBFS with CUDA 12: error: 'csrsm2Info_t' does 
not name a type
Severity set to 'serious' from 'important'
> severity 1036680 serious
Bug #1036680 [src:pyhst2] pyhst2: FTBFS with CUDA 12: error: texture is not a 
template
Severity set to 'serious' from 'important'
> severity 1036683 serious
Bug #1036683 {Done: Samuel Thibault } 
[src:starpu-contrib] starpu-contrib: FTBFS with CUDA 12: "It is an error to 
include both cublas.h and cublas_v2.h"
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036677
1036679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036679
1036680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036680
1036681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036681
1036682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036682
1036683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036683
1036684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973850: lilo: Should not be included in bullseye

[Simon McVittie]

On Sun, 11 Jun 2023 at 08:25:16 +0200, Helge Kreutzmann wrote:
> On Mon, Sep 13, 2021 at 09:35:08PM +0200, Joachim Wiedorn wrote:
> > Simon McVittie wrote on 2021-09-12 22:43:
> > 
> > > Now that bullseye has been released, should lilo be removed from unstable
> > > so that it will not be in any future Debian release either?
...
> maybe the time has come?

I've opened a "request of QA" bug asking the ftp team to remove lilo.
Please see , and reply there or close
that bug if you disagree with the request for removal.

#973850 should remain open until the removal is done, to avoid lilo
accidentally migrating into testing.

smcv

Bug#1037324: d.o/CD/live refers to images no longer built

[Laura Arjona Reina]

Thanks for the patch.
I have applied the update to the description, since the tags were 
already updated.


Kind regards,

--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Processed: Re: Bug#1037324: d.o/CD/live refers to images no longer built

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #1037324 [www.debian.org] d.o/CD/live refers to images no longer built
Added tag(s) patch.

-- 
1037324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037324: d.o/CD/live refers to images no longer built

[Jonathan Wiltshire]

Control: tag -1 patch

Patch attached.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

>From 7fd580c2f2e72bc5f0910216dfebf8b71e7ae9db Mon Sep 17 00:00:00 2001
From: Jonathan Wiltshire 
Date: Sun, 11 Jun 2023 10:51:10 +
Subject: [PATCH] Do not advertise i386 live images

---
 english/CD/live/index.wml  |  4 ++--
 english/template/debian/release_images.wml | 10 +-
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/english/CD/live/index.wml b/english/CD/live/index.wml
index fcd145815fc..6de2ab6e2b6 100644
--- a/english/CD/live/index.wml
+++ b/english/CD/live/index.wml
@@ -16,8 +16,8 @@ providing a choice of desktop environments (GNOME, KDE, LXDE, Xfce,
 Cinnamon and MATE). Many users will find these initial package
 selections suitable, installing any additional packages they need from
 the network afterwards.
-Architecture: Only images for the two most popular architectures,
-32-bit PC (i386) and 64-bit PC (amd64), are currently provided.
+Architecture: Only images for the most popular architecture,
+64-bit PC (amd64), are currently provided.
 Size: Each image is much smaller than the full set of
 DVD images, but larger than the network install media.
 Languages: The images do not contain a complete set of language
diff --git a/english/template/debian/release_images.wml b/english/template/debian/release_images.wml
index d016bbbcfba..adb73f77e6c 100644
--- a/english/template/debian/release_images.wml
+++ b/english/template/debian/release_images.wml
@@ -51,19 +51,19 @@
 https://cdimage.debian.org/debian-cd/-live
 
 
-
+
 
 
-
+
 
 
-
+
 
 
-
+
 
 
-
+
 
 
 # this needs to link a debian/ mirror rather than cdimage.d.o
-- 
GitLab

Bug#1037324: d.o/CD/live refers to images no longer built

[Laura Arjona Reina]

Hello

El 11/6/23 a las 12:42, Jonathan Wiltshire escribió:

Package: www.debian.org
Severity: serious
X-Debbugs-Cc: debian...@lists.debian.org, j...@debian.org

i386 live images are no longer built as of bookworm, but the download
page still refers to them. It needs a bit of a rewrite because the only
architecture now is amd64.

I became aware because of direct user reports.


Thanks for reporting.

I have updated our files in commit
https://salsa.debian.org/webmaster-team/webwml/-/commit/eccd7980c97d0e9c1c5580045cadbc68e6ca719e

(below the diff), it will be online in the next hours.

Please let me know if this fix is not enough, if I get no news I will 
close this bug reports in a few days.


Kind regards,

diff --git a/english/template/debian/release_images.wml 
b/english/template/debian/release_images.wml
index 
52c8be6dafee11dc1d3638d92a2f9eca97f1b8d9..ffdb0b8f041c2a5fe269998c7f69e0aac61cf405 
100644

--- a/english/template/debian/release_images.wml
+++ b/english/template/debian/release_images.wml
@@ -51,19 +51,19 @@
 live-images-url>https://cdimage.debian.org/debian-cd/-live


 
-

+
 
 
-

+
 
 
-
+
 
 
-
+
 
 
-
+
 

 # this needs to link a debian/ mirror rather than cdimage.d.o
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#1037324: d.o/CD/live refers to images no longer built

[Jonathan Wiltshire]

Package: www.debian.org
Severity: serious
X-Debbugs-Cc: debian...@lists.debian.org, j...@debian.org

i386 live images are no longer built as of bookworm, but the download
page still refers to them. It needs a bit of a rewrite because the only
architecture now is amd64.

I became aware because of direct user reports.

Bug#1037322: amqp-tools: Process leaks authentication data

[Christian Kastner]

Package: amqp-tools
Version: 0.11.0-1
Severity: grave
Tags: security
Forwarded: https://github.com/alanxz/rabbitmq-c/issues/575

When passing authentication data with either --password or --url, the
data is exposed in the process list, where it can be seen by any user.

Example:
  $ pgrep -a ampq-consume
  62287 amqp-consume --url amqp://user:pass@192.168.0.1 --queue=myqueue

This is an upstream issue. I've filed a pull request upstream that adds
an option --authfile with which authentication data can be read from a file.

Best,
Christian

Processed: Re: nomad ftbfs with newer golang-github-hashicorp-yamux-dev in experimental

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1037319 [nomad] nomad ftbfs with newer golang-github-hashicorp-yamux-dev 
in experimental
Severity set to 'serious' from 'important'

-- 
1037319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037007: marked as done (libopenmpt: failing autopkgtests with 0.7.0)

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 09:21:32 +
with message-id 
and subject line Bug#1037007: fixed in libopenmpt 0.7.1-1
has caused the Debian Bug report #1037007,
regarding libopenmpt: failing autopkgtests with 0.7.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.)


-- 
1037007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libopenmpt
Version: 0.7.0-1
Severity: serious
Tags: experimental

libopenmpt 0.7.0-1 in experimental has failing autopkgtests because of
errors emitted because of a deprecation warning.

pattern-dump-c.c: In function ‘main’:
pattern-dump-c.c:25:13: warning: ‘openmpt_stream_get_file_callbacks’
is deprecated [-Wdeprecated-declarations]
   25 | openmpt_stream_get_file_callbacks(),

https://release.debian.org/britney/pseudo-excuses-experimental.html#libopenmpt

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: libopenmpt
Source-Version: 0.7.1-1
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
libopenmpt, 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.
Sebastian Ramacher  (supplier of updated libopenmpt 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 02 Jun 2023 21:16:45 +0200
Source: libopenmpt
Architecture: source
Version: 0.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1037007
Changes:
 libopenmpt (0.7.1-1) unstable; urgency=medium
 .
   * Upload to unstable
   * New upstream version 0.7.1
   * debian/tests/: Allow output on stderr (Closes: #1037007)
Checksums-Sha1:
 b047337998147a13fa89f884d94e6f4a40c529af 1807 libopenmpt_0.7.1-1.dsc
 089a9b2dc31b65d695e96de4fd6ab1a9da194961 1650178 libopenmpt_0.7.1.orig.tar.gz
 707431f616698fc7cbef1ab25605020c70f83985 11472 libopenmpt_0.7.1-1.debian.tar.xz
Checksums-Sha256:
 218915a561de59728459c38d18a8c6faa88936fafce9df6ed5e98c0acc52b79b 1807 
libopenmpt_0.7.1-1.dsc
 bf175d26448bb133f74714f3a8859e7000b93522fb3577559dffc037161910f9 1650178 
libopenmpt_0.7.1.orig.tar.gz
 3fa8a6dbdb95c913dcd96cccba56e940745afe5201e1ac82d21fca920c306012 11472 
libopenmpt_0.7.1-1.debian.tar.xz
Files:
 490a7bd462a0bb0cab8e4693889fc0e9 1807 libs optional libopenmpt_0.7.1-1.dsc
 82268ef9f79a6b99c7229f7486054ad2 1650178 libs optional 
libopenmpt_0.7.1.orig.tar.gz
 42867d708b4fff38e9bae6c27c2ece0c 11472 libs optional 
libopenmpt_0.7.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZHpAQQAKCRAhk2s2YA/N
iZc2AP4pWguLYCS1bbGwE2bNeco+LhiZqN+iG17bmLi+SMJHrgEAtNxQ/OO7JnjQ
kfT1g8jJ2n74exM7NNUtoMVFUvbNMgo=
=L1ZR
-END PGP SIGNATURE End Message ---

Bug#1028222: marked as done (Don't release for bookworm)

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 17:00:18 +0800
with message-id 

and subject line Re: Bug#1028222: Don't release for bookworm
has caused the Debian Bug report #1028222,
regarding Don't release for bookworm
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.)


-- 
1028222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-1.20
Version: 1.20~rc2-1
Severity: serious
X-Debbugs-Cc: z...@debian.org
Control: clone -1 -2
Control: reassign -2 src:golang-1.18 1.18.9-1

Usually we only keep one go compiler in stable. For bookworm it should be
golang-1.19.
--- End Message ---
--- Begin Message ---
bookworm is released.

-- 
Shengjing Zhu--- End Message ---

Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed

[Otto Kekäläinen]

Hi!

I did a bunch of reproducible experiments using Salsa-CI in
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/536587
testing:

## upgrade to Bookworm

* cacti and Bullseye upgrade
- apt install -qq --yes cacti
   ->  - apt full-upgrade -qq --yes
* default-mysql-server and Bullseye upgrade
- apt install -qq --yes default-mysql-server
   ->  - apt full-upgrade -qq --yes
* mariadb-server and Bullseye upgrade
- apt install -qq --yes mariadb-server
* zoph and Bullseye upgrade
- apt install -qq --yes zoph
   ->  - apt full-upgrade -qq --yes
* zoph and Bullseye upgrade with mariadb-server explicitly
- apt install -qq --yes zoph mariadb-server
   ->  - apt install -qq --yes mariadb-server + apt full-upgrade -qq --yes
* zoph with mariadb-server and Bullseye upgrade
- apt install -qq --yes zoph mariadb-server
   ->  - apt full-upgrade -qq --yes

Only the last scenario failed.

This suggests that perhaps users hit this issue only when having
indirect dependency on default-mysql-server (via e.g. zoph), and
upgrading only it or doing a full-upgrade.


## Recommendation how to avoid this issue

I would recommend this as the best way as of today to update MariaDB
10.5.19/20 in Buster to 10.11.3 in Debian 12 "Bookworm":

# Ensure Bullseye was running latest of everything, makes upgrade smoother
$ sudo apt upgrade --yes
# Ensure clean and safe shutdown before doing major version upgrade -
this may take several minutes on large and busy database
$ sudo systemctl stop mariadb || sudo /etc/init.d/mariadb stop
# Enable new release
$ sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list
$ sudo apt update
# Just upgrade MariaDB first so it can be brought back online as fast
as possible
$ sudo apt install mariadb-server
# Then upgrade everything else
$ sudo apt full-upgrade


## Recommendation how to recover if suffered this issue


If you did not prepare along the lines of above and just upgraded, and
if failed with error message:

dpkg: mariadb-server-10.5: dependency problems, but removing anyway as
you requested:
 zoph depends on default-mysql-server | virtual-mysql-server; however:
  Package default-mysql-server is not configured yet.
  Package virtual-mysql-server is not installed.
  Package mariadb-server-10.5 which provides virtual-mysql-server is
to be removed.

(Reading database ... 16559 files and directories currently installed.)
Removing mariadb-server-10.5 (1:10.5.19-0+deb11u2) ...
Stopping MariaDB database server: mariadbd failed!
invoke-rc.d: initscript mariadb, action "stop" failed.
dpkg: error processing package mariadb-server-10.5 (--remove):
 installed mariadb-server-10.5 package pre-removal script subprocess
returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 mariadb-server-10.5
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

..in that case the easiest way to recover is simply to manually stop
the server and continue upgrade:

$ sudo pkill -ef mariadbd || sudo pkill -ef mysqld
$ sudo apt --fix-broken install
$ sudo apt full-upgrade


Workaround suggested to be included in Bookworm release notes at
https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/197

Bug#973850: lilo: Should not be included in bullseye

[Helge Kreutzmann]

Hello Joachim,
hello Simon,
On Mon, Sep 13, 2021 at 09:35:08PM +0200, Joachim Wiedorn wrote:
> Simon McVittie wrote on 2021-09-12 22:43:
> 
> > Now that bullseye has been released, should lilo be removed from unstable
> > so that it will not be in any future Debian release either?
> 
> I think the package should stay for a time in unstable, say 12 months?
> There a some people managing many server and still use lilo as boot
> manager. They should find it for a longer time.

More than 12 months have passed, bookworm (bullsye+1) has been released.

> > If so, the way to do that is to report a RM bug against the ftp.debian.org
> > pseudo-package. I can help with this if you would like.
> 
> I think I will do it in the autumn of 2022.

And summer 2023 (at least in Germany) is now in force.

So maybe the time has come?

At least I will disable the translation for the lilo man pages, so
Trixie will no longer ship those …

Greetings

   Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1037258: curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance

[Sergio Durigan Junior]

On Saturday, June 10 2023, Samuel Henrique wrote:

> Hello,
>
> I'm not able to reproduce the issue on Bookworm with a HTTP2 localhost
> apache server.
[...]

Hey,

I was able to find another URL that triggers the same issue.  This one:

  
https://chinarising.puntopress.com/wp-content/uploads/2023/04/Press-TV-KSA-Iran.mp3

(I found it while reading https://github.com/curl/curl/issues/9526)

Annoyingly, I still can't determine how to reliably reproduce the
problem by configuring a local webserver...  Anyway, this new URL
allowed me to continue the investigation, and I found that the following
commit seems to have introduced the problem:

8c762f59983a3e9e2b80fdb34aa5e08f1d9a1c7d is the first bad commit
commit 8c762f59983a3e9e2b80fdb34aa5e08f1d9a1c7d
Author: Stefan Eissing 
Date:   Wed Feb 8 15:56:57 2023 +0100

http2: minor buffer and error path fixes

It's a much smaller commit, and if we focus only on the lib/http2.c
changes, we notice that they are directly related to the handling HTTP2
stream closures.

By comparing the two commits (the one that introduces the failure and
the other that fixes it), it's pretty hard to say what exactly could be
the fix here because the code changed so much between them.

With my mad scientist hat on, I decided to experiment with something I'd
noticed: the "bad" commit indiscriminately treats "stream->reset" and
"stream->error" the same way, while the "good" commit doesn't.  I
applied the following change to the code:

diff --git a/lib/http2.c b/lib/http2.c
index d5eed385e..2dc8ee348 100644
--- a/lib/http2.c
+++ b/lib/http2.c
@@ -1919,7 +1919,7 @@ static ssize_t cf_h2_recv(struct Curl_cfilter *cf, struct 
Curl_easy *data,
   Curl_expire(data, 0, EXPIRE_RUN_NOW);
 }
 else if(stream->closed) {
-  if(stream->reset || stream->error) {
+  if(stream->reset) {
 nread = http2_handle_stream_close(cf, data, stream, err);
 goto out;
   }

... and it seemed to "work".  Of course, I don't claim the change above
to be correct, but it does seem to confirm the suspicion that
"stream->error" shouldn't be handled as a stream closure.

Things to investigate:

- Why are we getting "stream->error" here?  Maybe "--trace" can help us.

- How to reliably reproduce the problem locally?  It'd be really nice to
  have a testcase for this.

Ah, I forgot to mention: initially I had the suspicion that this might
be related to the openssl 3 transition, but I was able to reproduce the
problem using bullseye, so I think that proves my hypothesis wrong.

It's late here now so I'm calling it "a day", but I'll try to get back
to this investigation in the following days.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/