Bug#1037357: flowblade: windows allways open off-center

[Gürkan Myczko]

Hi Martin

Thank you for the bug report.

The first time that Flowblade is run and asks for one's preferred 
editing mode, the window is maximized.


That is true. But the window is not maximized.


The next time that Flowblade is run, the window is the same size,


Yes, it is.


except that it's partially off-screen,


No, it is not. Can't reproduce.

so it has to be dragged back to the top edge of the desktop 
environment.


What DE or window manager are you using? It's possibly a bug there, and 
not in flowblade.


The window should always open maximized and remain completely within 
the visible screen area.


I disagree, the window should not always open maximized. But opening 
applications, I agree, should
always remain within the visible screen area, unless the user moves it 
out, and wants to keep it there.


Kind regards,

Bug#1030171: clamav-daemon: clamav-clamonacc.service fails to start

[Martin-Éric Racine]

Package: clamav-daemon
Version: 1.0.1+dfsg-2
Followup-For: Bug #1030171

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Syslog already suggests what the fix should be:

$ grep Clamonacc /var/log/syslog
2023-06-12T08:33:40.562184+03:00 p8h61 clamonacc[248359]: ERROR: Clamonacc: at 
least one of OnAccessExcludeUID, OnAccessExcludeUname, or 
OnAccessExcludeRootUID must be specified ... it is recommended you exclude the 
clamd instance UID or uname to prevent infinite event scanning loops

When will this get implemented?

Martin-Éric

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmSGr6kACgkQrh+Cd8S0
17a4zA/9FK57U30pAvn/cOV7gqsOU676lJaPBdyA7Ovrc5m7/xeIFnHIIG1krDfq
3r5VLSy4PQivA4i4ztIYH2p57fvUlVsDG3jLHzWdFjlEurjNWS0AKp0Zo5OxIwcv
lTbXnzfEcUEOu85tLBk3bEvPgqZvqearxnpbosSDM3Q0qsDrf/SM7MaNl+4cfq2h
q57SFGRsOfa3AGWftqc8nY+WzChaj1DWAxZyuEs/K5bbaB2uerOPs59f8zods3qh
nluhlbcH4x7P+n5e5QcDvONmj4LmUKdd1PNzerUoqiKsqs5Z1uJcIV9j39Vx26tF
uh3CsnjvkuN4k1Zp1Xc+9MmmahvufT+fLctcV9FnldOoaY95X5wbAAFZbeyyJ/8K
qkG2iMESRwFCkQpmISAp+lafpj1lcxaBTdz5JxF/SW3BPDRTf/f2QyMM7f0YkqBl
gzYWf1oIUu6y/klTCSBsNDDDd9CUOaVTt/83lt2hp4uk+UFyNRq2xsriD/lsFJxi
bCmMpQeKJIieFupk4Kc1+QG7Sqz1N9BlqBs6u1AJsmnxX4h0pxsY0Q2KKFPlfJeq
myqD+prIbQSlulvlRWTck26azjMca8Ieakutyd4V3xZ3uBZ/+9G7v0kOXlkgXyL1
npj247uI28XBC99JSI0HUTxNG+Nx0hVQ7twLqoEyNeeCtKxmJHM=
=DE++
-END PGP SIGNATURE-

Bug#1037333: libeconf: CVE-2023-32181 CVE-2023-22652

[Salvatore Bonaccorso]

Hi Andreas,

On Sun, Jun 11, 2023 at 10:16:22PM +0200, Andreas Henriksson wrote:
> Hello Salvatore,
> 
> On Sun, Jun 11, 2023 at 05:12:57PM +0200, Salvatore Bonaccorso wrote:
> > Source: libeconf
> > Version: 0.5.1+dfsg1-1
> > Severity: important
> > Tags: security upstream
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > 
> > 
> > Hi,
> > 
> > The following vulnerabilities were published for libeconf.
> [...]
> 
> Thanks for notifying me about this. I've prepared libeconf 0.5.2
> packages in git and just uploaded towards unstable.
> 
> IMHO I think uploading the same to stable would be fine (even though
> there's one "unrelated" change in new upstream version so maybe not
> strictly a security-only release), because libeconf has no reverse
> dependencies in the debian archive yet! The risk of regression should
> thus be almost non-existant.
> 
> If by chance you have the SRM dance in muscle memory, please feel free
> to take over getting 0.5.2 into stable! It's been a while for me and
> honestly since libeconf is still unused it's very low prio for me.

I do agree that this is low enough that it might be fixed in a point
release and does not require a security-update but it is not
particularly urgent.

Thanks for having it fixed for unstable (and so towards trixie). 

Regards,
Salvatore

Bug#1037358: mailman3-web: Upgrade from Debian 11 to Debian 12 broke mailman/mailman3-web

[Norbert Preining]

Package: mailman3-web
Version: 0+20200530-2.1
Severity: important

Dear Maintainer,

With the upgrade from Debian 11 to Debian 12 a lot of problems popped up
around mailman/web:

- /etc/mailman/mailman-web.py needs updates:

# Updates require this, should already be in Debian's package, but isn't
# See https://gitlab.com/mailman/hyperkitty/-/issues/401
DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
# /usr/lib/python3/dist-packages/django_q/conf.py contains
# conf.py:TIMEOUT = conf.get("timeout", None)
# conf.py:RETRY = conf.get("retry", 60)
# which is broken
Q_CLUSTER = {
'timeout': 300,
'save_limit': 100,
'orm': 'default',
'retry': 360,
}

since these values are not taken into the Debian packages, although they
are necessary


- /etc/cron.d/mailman3 contains a call to gatenews which triggers errors
  and probalby should not be called in the cron script


- even with the above changes, the hourly run job fails (that is actually
  a serious bug!)

/usr/lib/python3/dist-packages/whoosh/codec/whoosh3.py:1116: SyntaxWarning: 
"is" with a literal. Did you mean "=="?
  elif fixedsize is 0:
[ERROR/MainProcess] Failed indexing 1 - 1 (retry 5/5): no such column: 
hyperkitty_mailinglist.archive_rendering_mode (pid 4974): no such column:
hyperkitty_mailinglist.archive_rendering_mode
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 173, in __get__
rel_obj = self.field.get_cached_value(instance)
  ^
  File "/usr/lib/python3/dist-packages/django/db/models/fields/mixins.py", line 
15, in get_cached_value
return instance._state.fields_cache[cache_name]
   
KeyError: 'mailinglist'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, 
in _execute
return self.cursor.execute(sql, params)
   
  File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", 
line 423, in execute
return Database.Cursor.execute(self, query, params)
   
sqlite3.OperationalError: no such column: 
hyperkitty_mailinglist.archive_rendering_mode

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", 
line 119, in do_update
backend.update(index, current_qs, commit=commit)
  File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", 
line 258, in update
doc = index.full_prepare(obj)
  ^^^
  File "/usr/lib/python3/dist-packages/haystack/indexes.py", line 235, in 
full_prepare
self.prepared_data = self.prepare(obj)
 ^
  File "/usr/lib/python3/dist-packages/haystack/indexes.py", line 226, in 
prepare
self.prepared_data[field.index_fieldname] = field.prepare(obj)
^^
  File "/usr/lib/python3/dist-packages/haystack/fields.py", line 236, in prepare
return self.convert(super().prepare(obj))

  File "/usr/lib/python3/dist-packages/haystack/fields.py", line 105, in prepare
values = self.resolve_attributes_lookup(current_objects, attrs)
 ^^
  File "/usr/lib/python3/dist-packages/haystack/fields.py", line 125, in 
resolve_attributes_lookup
if not hasattr(current_object, attributes[0]):
   ^^
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 187, in __get__
rel_obj = self.get_object(instance)
  ^
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 154, in get_object
return qs.get(self.field.get_reverse_related_filter(instance))
   ^^^
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 431, in 
get
num = len(clone)
  ^^
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 262, in 
__len__
self._fetch_all()
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 1324, 
in _fetch_all
self._result_cache = list(self._iterable_class(self))
 
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 51, in 
__iter__
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, 
chunk_size=self.chunk_size)
  
^^
  File 

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 

Bug#1037357: flowblade: windows allways open off-center

[Martin-Éric Racine]

Package: flowblade
Version: 2.8.0.3-3
Severity: important

The first time that Flowblade is run and asks for one's preferred editing mode, 
the window is maximized.

The next time that Flowblade is run, the window is the same size, except that 
it's partially off-screen, so it has to be dragged back to the top edge of the 
desktop environment.

The window should always open maximized and remain completely within the 
visible screen area.

Martin-Éric

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flowblade depends on:
ii  frei0r-plugins1.8.0-1+b1
ii  gir1.2-gdkpixbuf-2.0  2.42.10+dfsg-1+b1
ii  gir1.2-glib-2.0   1.74.0-3
ii  gir1.2-gtk-3.03.24.37-2
ii  gir1.2-pango-1.0  1.50.12+ds-1
ii  gmic  2.9.4-4+b4
ii  libmlt-data   7.12.0-1
ii  librsvg2-common   2.54.5+dfsg-1
ii  python3   3.11.2-1+b1
ii  python3-cairo 1.20.1-5+b1
ii  python3-dbus  1.3.2-4+b1
ii  python3-distutils 3.11.2-3
ii  python3-gi3.42.2-3+b1
ii  python3-gi-cairo  3.42.2-3+b1
ii  python3-mlt   7.12.0-1+b1
ii  python3-numpy 1:1.24.2-1
ii  python3-opencv4.6.0+dfsg-12
ii  python3-pil   9.4.0-1.1+b1
ii  swh-plugins   0.4.17-2

flowblade recommends no packages.

flowblade suggests no packages.

-- no debconf information

Bug#1037356: generate-ui.sh fails

[Ian Kelling]

Package: prometheus-alertmanager
Version: 0.25.0-1

/usr/share/prometheus/alertmanager/generate-ui.sh fails with obvious
errors. Attached is a fixed version. I didn't bother generating a patch
since the script is so small.

#!/bin/bash

set -e

ELMDISTURL=https://github.com/elm/compiler/releases/download/0.19.1/binary-for-linux-64-bit.gz
SRCDIR=/usr/share/gocode/src/github.com/prometheus/alertmanager/ui/app
DSTDIR=/usr/share/prometheus/alertmanager/ui

echo "Installing dependencies..." >&2
apt install libjs-bootstrap4 fonts-font-awesome curl uglifyjs \
golang-github-prometheus-alertmanager-dev

#/usr/share/fonts-font-awesome/
TMPDIR=$(mktemp -d)

echo "Downloading Elm tools..." >&2
cd $TMPDIR
curl --location $ELMDISTURL | zcat >$TMPDIR/elm
chmod +x $TMPDIR/elm

echo "Compiling source code..." >&2
ln -s $SRCDIR/src $SRCDIR/elm.json $TMPDIR
(cd $TMPDIR; ./elm make src/Main.elm --optimize --output $TMPDIR/app.js)

echo "Optimising source code..." >&2
uglifyjs $TMPDIR/app.js \
--compress 'pure_funcs="F2,F3,F4,F5,F6,F7,F8,F9,A2,A3,A4,A5,A6,A7,A8,A9",pure_getters,keep_fargs=false,unsafe_comps,unsafe' \
--mangle --output $TMPDIR/script.js

echo "Installing in Alertmanager directory..." >&2
mkdir -p $DSTDIR
mkdir -p $DSTDIR/lib
cp $TMPDIR/script.js $DSTDIR
cp $SRCDIR/index.html $SRCDIR/favicon.ico $DSTDIR
ln -s /usr/share/fonts-font-awesome $DSTDIR/lib/font-awesome
ln -s /usr/share/nodejs/bootstrap/dist $DSTDIR/lib/bootstrap4

rm -rf $TMPDIR

echo "Finished! Please, restart prometheus-alertmanager to activate UI." >&2

Bug#1037355: packages.debian.org: wrong mapping codename <-> stable

[Holger Wansing]

Package: www.debian.org

In the search form, at packages.debian.org, bullseye is still stable.

Please update the suites (similar to 
https://salsa.debian.org/webmaster-team/packages/-/commit/4648ee328d98a903bb9212b7ffb1f42fa9db773d)

The old issue of hardcoded suitenames ... (?)


Holger



-- 
Sent from /e/ OS on Fairphone3

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() }

Bug#1037354: X.7: some formatting fixes for the manual

[Bjarni Ingi Gislason]

Package: xorg-docs-core
Version: 1:1.7.1-1.2
Severity: minor
Tags: patch

Dear Maintainer,

here are some remarks and fixes.

Input file is X.7

Output from "mandoc  -T lint X.7"
mandoc: X.7:39:2: WARNING: skipping paragraph macro: PP after SH
mandoc: X.7:100:93: STYLE: input text line longer than 80 bytes: a font server 
and re...
mandoc: X.7:101:82: STYLE: input text line longer than 80 bytes: a display 
server and...
mandoc: X.7:103:83: STYLE: input text line longer than 80 bytes: keyboard 
description...
mandoc: X.7:118:2: WARNING: skipping paragraph macro: PP after SH
mandoc: X.7:152:2: WARNING: skipping paragraph macro: PP after SH
mandoc: X.7:234:2: WARNING: skipping paragraph macro: PP empty
mandoc: X.7:356:2: WARNING: skipping paragraph macro: PP empty
mandoc: X.7:365:87: STYLE: input text line longer than 80 bytes: a variety of 
differe...
mandoc: X.7:595:2: WARNING: skipping paragraph macro: PP after SH
mandoc: X.7:695:4: WARNING: undefined escape, printing literally: \+
mandoc: X.7:898:2: WARNING: skipping paragraph macro: PP empty
mandoc: X.7:902:2: WARNING: skipping paragraph macro: PP empty
mandoc: X.7:906:2: WARNING: skipping paragraph macro: PP empty
mandoc: X.7:1197:2: WARNING: skipping paragraph macro: PP after SH
mandoc: X.7:1277:2: WARNING: skipping paragraph macro: PP after SH
mandoc: X.7:1280:2: WARNING: skipping paragraph macro: PP after SH

###

Reduce space between words.

740:name, but with  the first letter capitalized (e.g. \fIBitmap\fP or 
\fIEmacs\fP)

###

Increase size of ~ (tilde) to make it more visible
with "troff" by using character \(ti.

407:% cp newfont.pcf ~/myfonts
408:% mkfontdir ~/myfonts
576:CIEuvY:\fI//\fP(~.6, ~.6, 1)
577:CIExyY:\fI//\fP(~.75, ~.85, 1)

#

Use "\e" to print the escape character instead of "\\" (which gets
interpreted in copy mode).

785:the two-character sequence ``\\\^\fIspace\fP'' (backslash followed by space)
787:and the two-character sequence ``\\\^\fItab\fP''
791:the two-character sequence ``\\\^n'' is recognized and replaced by a
794:the two-character sequence ``\\\^\fInewline\fP''
798:the four-character sequence ``\\\^\fInnn\fP'',
802:Finally, the two-character sequence ``'' is recognized

#

Move a full stop (period) and a comma outside of a quoted text, if it is
at the end of the quote and does not end a quoted sentence.

635:This modifier is called the ``group modifier.''

Test nr. 26:

Find a repeated word

! 627 --> the
! 868 --> for

#

Use \(en for a dash (en-dash) between space characters, not a minus
(\-) or a hyphen (-), except in the NAME section.

X.7:75:the \fIXlib - C Language X Interface\fP manual,
X.7:77:the \fIX Toolkit Intrinsics - C Language Interface\fP manual,
X.7:871:See the \fIX Toolkit Intrinsics - C Language Interface\fP manual for

#

an.tmac:X.7:1091: style: 1 leading space(s) on input line

#

--- X.7 2023-05-26 19:01:03.0 +
+++ X.7.new 2023-06-12 02:33:35.0 +
@@ -36,7 +36,6 @@
 .SH NAME
 X \- a portable, network-transparent window system
 .SH OVERVIEW
-.PP
 The X Window System is a network transparent window system which runs
 on a wide range of computing and graphics machines.  It should be
 relatively straightforward to build the X.Org Foundation software
@@ -72,9 +71,9 @@ X supports overlapping hierarchical subw
 graphics operations, on both monochrome and color
 displays.
 For a full explanation of the functions that are available, see
-the \fIXlib - C Language X Interface\fP manual,
+the \fIXlib \(en C Language X Interface\fP manual,
 the \fIX Window System Protocol\fP specification,
-the \fIX Toolkit Intrinsics - C Language Interface\fP manual,
+the \fIX Toolkit Intrinsics \(en C Language Interface\fP manual,
 and various toolkit documents.
 .PP
 The number of programs that use \fIX\fP is quite large.
@@ -115,7 +114,6 @@ as user-contributed software in the X.Or
 available on the Internet.
 See your site administrator for details.
 .SH "STARTING UP"
-.PP
 There are two main ways of getting the X server and an initial set of
 client applications started.  The particular method used depends on what
 operating system you are running and whether or not you use other window
@@ -149,7 +147,6 @@ finish.  Since either or both of the use
 script, this gives substantial flexibility at the expense of a
 nice interface.  For this reason, \fIxinit\fP is not intended for end users.
 .SH "DISPLAY NAMES"
-.PP
 From the user's perspective, every X server has a \fIdisplay name\fP of the
 form:
 .sp
@@ -231,7 +228,6 @@ hostname or IP address.  Full Internet n
 addresses, and IPv6 addresses are all allowed.  For example:
 \fIx.org:0\fP, \fIexpo:0\fP, \fI[::1]:0\fP,
 \fI198.112.45.11:0\fP, \fIbigmachine:1\fP, and \fIhydra:0.1\fP.
-.PP
 .SH "ACCESS CONTROL"
 An X server can use several types of access control.  Mechanisms provided
 in Release 7 are:
@@ -353,7 +349,6 @@ hand corner:
 xload \-geometry 48x48\-96+0 &
 xbiff \-geometry 

Bug#1037353: lynx.1: a few formatting fixes for the manual

[Bjarni Ingi Gislason]

Package: lynx
Version: 2.9.0dev.12-1
Severity: minor
Tags: patch

Dear Maintainer,

here are some fixes.

Input file is lynx.1

Output from "mandoc -T lint lynx.1"
mandoc: lynx.1:27:2: WARNING: missing date, using "": TH
mandoc: lynx.1:109:2: WARNING: unknown font, skipping request: ft C 

mandoc: lynx.1:317:2: WARNING: unknown font, skipping request: ft C 

mandoc: lynx.1:366:2: WARNING: unknown font, skipping request: ft C 

mandoc: lynx.1:831:2: WARNING: unknown font, skipping request: ft C 

mandoc: lynx.1:838:2: WARNING: unknown font, skipping request: ft C 

mandoc: lynx.1:1131:2: WARNING: unknown font, skipping request: ft C


###

Increase size of ~ (tilde) to make it more visible
with "troff" by using character \(ti.

264:If none is specified, the default value is ~/.lynx_cookies
265:for most systems, but ~/cookies for MS-DOS.

#

  The following issue is not in the patch:

an.tmac:lynx.1:27: style: .TH missing third argument; suggest document 
modification date in ISO 8601 format (-MM-DD)
an.tmac:lynx.1:27: style: .TH missing fourth argument; suggest package/project 
name and version (e.g., "lynx ...")

#

--- lynx.1  2023-06-05 16:20:24.0 +
+++ lynx.1.new  2023-06-12 01:32:27.0 +
@@ -15,7 +15,7 @@
 .ie n  .in +4
 .el.in +2
 .nf
-.ft C  \" Courier
+.ft CR \" Courier
 ..
 .de NE
 .fi
@@ -261,8 +261,8 @@ Sets the connection timeout, where N is
 .TP
 .B \-cookie_file\fR=\fIFILENAME
 specifies a file to use to read cookies.
-If none is specified, the default value is ~/.lynx_cookies
-for most systems, but ~/cookies for MS-DOS.
+If none is specified, the default value is \(ti/.lynx_cookies
+for most systems, but \(ti/cookies for MS-DOS.
 .TP
 .B \-cookie_save_file\fR=\fIFILENAME
 specifies a file to use to store cookies.


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.27-1 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lynx depends on:
ii  libbsd0   0.11.7-2
ii  libbz2-1.01.0.8-5+b1
ii  libc6 2.36-9
ii  libgnutls30   3.7.9-2
ii  libidn2-0 2.3.3-1+b1
ii  libncursesw6  6.4-4
ii  libtinfo6 6.4-4
ii  lynx-common   2.9.0dev.12-1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages lynx recommends:
ii  mailcap  3.70+nmu1

lynx suggests no packages.

-- no debconf information

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#1037351: hippotat: ftbfs with rust-base64 0.21

[Peter Green]

Package: hippotat
Version: 1.1.7
Tags: trixie, sid, ftbfs, patch

hippotat FTBFS with the new version of rust-base64.

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

Also your clean target is horriblly broken, I filtered the
debdiff to get rid of a huge volume of junk.

I may or may not NMU this later.
diff -Nru hippotat-1.1.7/debian/cargo_home/config 
hippotat-1.1.7+nmu1/debian/cargo_home/config
--- hippotat-1.1.7/debian/cargo_home/config 1970-01-01 00:00:00.0 
+
+++ hippotat-1.1.7+nmu1/debian/cargo_home/config2023-06-11 
19:36:38.0 +
@@ -0,0 +1,8 @@
+[source.crates-io]
+replace-with = "dh-cargo-registry"
+
+[source.dh-cargo-registry]
+directory = "/usr/share/cargo/registry"
+
+[build]
+rustflags = ['-C', 'debuginfo=2', '--cap-lints', 'warn', '-C', 
'linker=x86_64-linux-gnu-gcc', '-C', 'link-arg=-Wl,-z,relro']
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 ,

Bug#1037275: dd: regression - posix expression syntax no longer supported

[Pádraig Brady]

On 11/06/2023 18:29, Jim Meyering wrote:

Thanks. The patch looks fine.
My only suggestion would be a stylistic one, to change the ">"
comparison to be the equivalent "<" one, i.e., change this:

+  && *suffix == 'B' && (suffix > str && suffix[-1] != 'B'))

to this (also dropping the unnecessary parentheses):

+  && *suffix == 'B' && str < suffix && suffix[-1] != 'B')

Why? Because of the increasing-to-right number-line argument, where
smaller things are visually on the left of larger ones.

Currently, in src/, the uses of space-delimited < and <= outnumber
uses of > and >= by four to one, 1678 to 428.


Pushed with that adjustment.

thanks
Pádraig

Bug#940960: ITP: linenoise -- Minimal replacement for readline

[Jeremy Sowden]

On 2023-05-21, at 18:00:45 +0800, Blair Noctis wrote:
> On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden  wrote:
> > It occurs to me that it might make more sense for you to take the lead
> > in packaging linenoise since you have an interest in getting it into
> > Debian.  Would you like me to transfer ownership of the ITP bug to you?
> > Happy to lend a hand if you need one.
> 
> Hmm, can I ask for a review while I upload to mentors.d.n? Wanna make
> sure I did it right.

Yes, absolutely.  Apologies for taking three weeks to reply.

J.


signature.asc
Description: PGP signature

Bug#1037327: MariaDB upgrade fails if page compressed tables exist already due to plugin dependency

[Otto Kekäläinen]

Hello!

It seems the issue is with dpkg not making the new config files
available using the correct name:

# apt install mariadb-plugin-provider-lz4
Setting up mariadb-server (1:10.11.4-1) ...
Stopping MariaDB database server: mariadbd.
Starting MariaDB database server: mariadbd . . . . .
Running '/etc/init.d/mariadb start' failed with error log:
230611 20:15:15 mysqld_safe Starting mariadbd daemon with databases
from /var/lib/mysql
2023-06-11 20:15:15 0 [Note] Starting MariaDB 10.11.4-MariaDB-1 source
revision  as process 4570
2023-06-11 20:15:15 0 [ERROR] mariadbd: InnoDB: compression algorithm
lz4 (2) is not available. Please, load the corresponding provider
plugin.
2023-06-11 20:15:15 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-06-11 20:15:15 0 [ERROR] Plugin 'InnoDB' registration as a
STORAGE ENGINE failed.
2023-06-11 20:15:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-06-11 20:15:15 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-06-11 20:15:15 0 [ERROR] Aborting

# ls -la /usr/lib/mysql/plugin/provider_lz4.so
-rw-r--r-- 1 root root 14192 Jun  4 18:22 /usr/lib/mysql/plugin/provider_lz4.so

# find /etc/mysql/mariadb.conf.d
/etc/mysql/mariadb.conf.d/50-client.cnf
/etc/mysql/mariadb.conf.d/50-mysql-clients.cnf
/etc/mysql/mariadb.conf.d/60-galera.cnf
/etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf
/etc/mysql/mariadb.conf.d/innodb-lz-compression.cnf
/etc/mysql/mariadb.conf.d/provider_bzip2.cnf.dpkg-new
/etc/mysql/mariadb.conf.d/provider_lz4.cnf.dpkg-new
/etc/mysql/mariadb.conf.d/provider_lzma.cnf.dpkg-new
/etc/mysql/mariadb.conf.d/provider_lzo.cnf.dpkg-new
/etc/mysql/mariadb.conf.d/provider_snappy.cnf.dpkg-new
/etc/mysql/mariadb.conf.d/50-server.cnf

# cat /etc/mysql/mariadb.conf.d/provider_lz4.cnf.dpkg-new
[server]
plugin_load_add=provider_lz4
provider_lz4=force_plus_permanent

# cp -a /etc/mysql/mariadb.conf.d/provider_lz4.cnf.dpkg-new
/etc/mysql/mariadb.conf.d/provider_lz4.cnf

# apt install mariadb-plugin-provider-lz4
mariadb-plugin-provider-lz4 is already the newest version (1:10.11.4-1).
Setting up mariadb-server (1:10.11.4-1) ...
Stopping MariaDB database server: mariadbd.
Starting MariaDB database server: mariadbd.
Setting up mariadb-plugin-provider-lz4 (1:10.11.4-1) ...
Setting up mariadb-server-10.5 (1:10.11.4-1) ...
Processing triggers for mariadb-server (1:10.11.4-1) ...
Stopping MariaDB database server: mariadbdERROR 2002 (HY000): Can't
connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Starting MariaDB database server: mariadbd.

# find /etc/mysql/mariadb.conf.d
/etc/mysql/mariadb.conf.d
/etc/mysql/mariadb.conf.d/50-client.cnf
/etc/mysql/mariadb.conf.d/50-mysql-clients.cnf
/etc/mysql/mariadb.conf.d/60-galera.cnf
/etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf
/etc/mysql/mariadb.conf.d/innodb-lz-compression.cnf
/etc/mysql/mariadb.conf.d/50-server.cnf
/etc/mysql/mariadb.conf.d/provider_lz4.cnf
/etc/mysql/mariadb.conf.d/provider_bzip2.cnf
/etc/mysql/mariadb.conf.d/provider_lzma.cnf
/etc/mysql/mariadb.conf.d/provider_lzo.cnf
/etc/mysql/mariadb.conf.d/provider_snappy.cnf

The are renamed from *.cnf.dpkg-new to *.cnf only after the
installation completes.

Perhaps the solution involves adjusting the time when the
restart/reload is triggered and somehow force it to happen as late as
possible, to ensure the 'Setting up mariadb-plugin-provider-lz4' has
happened before server restarts
(https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/rules#L239-243).


I added a test case for this in
https://salsa.debian.org/otto/mariadb-server/-/commits/bugfix/1037327-upgrades-need-provider-plugin-lz
and it fails (as expected) in
https://salsa.debian.org/otto/mariadb-server/-/jobs/4297516 but if we
come up with a solution, at least we have now a test to validate it.

Bug#1037341: qemu-system-x86: USB device attach to XEN not work

[Michael Tokarev]

Control: reassign -1 qemu-system-xen

11.06.2023 22:12, Gabor Droszler пишет:

Package: qemu-system-x86
Version: 1:7.2+dfsg-7
Severity: important
X-Debbugs-Cc: drosz...@datatrans.hu

Dear Maintainer,

The new XEN + QEMU don't enable to attach USB device. This works the past 
Debian version.

..> xl usbdev-attach dtrdp hostbus=1 hostaddr=2

libxl: error: libxl_qmp.c:1837:qmp_ev_parse_error_messages: Domain 
21:'usb-host' is not a valid device model name


Starting in bookworm, we use separate build of qemu for xen, to de-couple 
xen-specific
features and dependencies from regular qemu usage and non-xen features and deps 
from
xen qemu usage.

It turns out I haven't enabled all features in qemu which are used by xen, usb 
obviously
being one of them.  Indeed, usb isn't enabled for the xen build of qemu.  
Unfortunately
it's difficult to find out which parts are being used and which aren't, - xen 
HVM mode
with qemu is a very rare configuration these days, not used by developers.

I'll enable USB for the xen build of qemu.  Maybe there's something else 
missing in there
too, I don't know yet.  It is unlikely to happen before the first bookworm 
point release
though.  Maybe it will be possible to use bookworm-backports meanwhile (with 
qemu 8.0)
when this one will be available.

Thanks,

/mjt

Bug#1037350: Package: installation-reports

[Peter Ehlert]

Package: installation-reports

Boot method: USB
Image version: debian-12.0.0-amd64-netinst.iso
Date: 2023-06-11 9-16-23

Machine: Type: Desktop System: Hewlett-Packard product: HP Z820 Workstation
Processor: CPU: 2x 8-core Intel Xeon E5-2687W 0 (-MT MCP SMP-)
Memory: Mem: 1310.8/48189.1 MiB (2.7%) Storage: 9.32 TiB (3.2% used)
Partitions: 

$ df -Tl
Filesystem Type 1K-blocks    Used Available Use% Mounted on
udev   devtmpfs  24639364   0  24639364   0% /dev
tmpfs  tmpfs  4934568    2036   4932532   1% /run
/dev/sdb24 ext4  28660644 4437152  22742276  17% /
tmpfs  tmpfs 24672828   0  24672828   0% /dev/shm
tmpfs  tmpfs 5120  12  5108   1% /run/lock
/dev/sdb26 ext4  19046484    1228  18052388   1% /home
tmpfs  tmpfs  4934564  80   4934484   1% /run/user/1000



Output of lspci -knn (or lspci -nn):

$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E5/Core i7 DMI2 
[8086:3c00] (rev 07)

    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 DMI2 [103c:158b]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 1a [8086:3c02] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 1a [103c:158b]

    Kernel driver in use: pcieport
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 1b [8086:3c03] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 1b [103c:158b]

    Kernel driver in use: pcieport
00:02.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 2a [8086:3c04] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 2a [103c:158b]

    Kernel driver in use: pcieport
00:03.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 3a in PCI Express Mode [8086:3c08] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 3a in PCI Express Mode [103c:158b]

    Kernel driver in use: pcieport
00:05.0 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 
Address Map, VTd_Misc, System Management [8086:3c28] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 Address Map, 
VTd_Misc, System Management [103c:158b]
00:05.2 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 
Control Status and Global Errors [8086:3c2a] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 Control Status 
and Global Errors [103c:158b]
00:05.4 PIC [0800]: Intel Corporation Xeon E5/Core i7 I/O APIC 
[8086:3c2c] (rev 07)

    Subsystem: Intel Corporation Xeon E5/Core i7 I/O APIC [8086:3c2c]
00:11.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI 
Express Virtual Root Port [8086:1d3e] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset PCI 
Express Virtual Root Port [103c:158b]

    Kernel driver in use: pcieport
00:16.0 Communication controller [0780]: Intel Corporation C600/X79 
series chipset MEI Controller #1 [8086:1d3a] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset MEI 
Controller [103c:158b]

    Kernel driver in use: mei_me
    Kernel modules: mei_me
00:16.2 IDE interface [0101]: Intel Corporation C600/X79 series chipset 
IDE-r Controller [8086:1d3c] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset IDE-r 
Controller [103c:158b]

    Kernel driver in use: ata_generic
    Kernel modules: ata_generic
00:16.3 Serial controller [0700]: Intel Corporation C600/X79 series 
chipset KT Controller [8086:1d3d] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset KT 
Controller [103c:158b]

    Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit 
Network Connection (Lewisville) [8086:1502] (rev 05)

    DeviceName: Onboard LAN
    Subsystem: Hewlett-Packard Company 82579LM Gigabit Network 
Connection (Lewisville) [103c:158b]

    Kernel driver in use: e1000e
    Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset 
USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset USB2 
Enhanced Host Controller [103c:158b]

    Kernel driver in use: ehci-pci
    Kernel modules: ehci_pci
00:1b.0 Audio device [0403]: Intel Corporation C600/X79 series chipset 
High Definition Audio Controller [8086:1d20] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset High 
Definition Audio Controller [103c:158b]

    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 2 [8086:1d12] (rev b5)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset PCI 
Express Root Port 2 [103c:158b]

    Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation 

Bug#1028511: A workaround

[Jinesh Choksi]

I found that when installing the base system, when you are prompted whether to 
install a generic kernel or a targetted kernel, if you choose to install the 
targetted kernel then the issue described in this bug report will not occur. I 
can enter the luks password in a Gen2 hyper-v VM without any issues. With a 
generic kernel, I can't.

Bug#1037349: pulseaudio: PulseAudio daemon does not start after upgrade to Debian 12

[Eric Chassande-Mottin]

Package: pulseaudio
Version: 16.1+dfsg1-2+b1
Severity: normal
X-Debbugs-Cc: echassandemot...@gmail.com

Dear Maintainer,

I upgraded my system (Dell XPS 13 laptop) to Debian 12 today.
The Pulseaudio daemon does not start automatically at start up.
I can fix the problem by issuing:

systemctl --user stop pulseaudio.socket
systemctl --user stop pulseaudio.service
systemctl --user start pulseaudio.socket
systemctl --user start pulseaudio.service
sudo pulseaudio --system

I'd like to know how to fix the issue cleanly.
Could you please help?

You'll find below some information to help debugging.
Feel free to ask more.

Best,
Eric CM

$ pacmd info
No PulseAudio daemon running, or not running as session daemon.
$ pacmd list-sinks
No PulseAudio daemon running, or not running as session daemon.

$ fuser -v /dev/snd/*
$ fuser -v /dev/dsp
Specified filename /dev/dsp does not exist.

$ loginctl show-session $XDG_SESSION_ID
[stalls]

$ pulseaudio -v
I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not 
permitted
I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not 
permitted
I: [pulseaudio] core-util.c: Successfully gained nice level -11.
I: [pulseaudio] main.c: This is PulseAudio 16.1
I: [pulseaudio] main.c: Page size is 4096 bytes
[...]
D: [pulseaudio] module.c: Checking for existence of 
'/usr/lib/pulse-16.1+dfsg1/modules/module-esound-protocol-unix.so': failure
E: [pulseaudio] socket-server.c: bind(): Address already in use
E: [pulseaudio] module.c: Failed to load module "module-native-protocol-unix" 
(argument: ""): initialization failed.
[...]
I: [pulseaudio] module.c: Loaded "module-filter-apply" (index: #19; argument: 
"").
E: [pulseaudio] main.c: D-Bus name org.pulseaudio.Server already taken.
I: [pulseaudio] main.c: Daemon startup complete.
[...]
I: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1f.3.analog-stereo idle for too long, suspending ...
I: [alsa-sink-ALC3246 Analog] alsa-sink.c: Device suspended...

$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 39
Tile Size: 65472
User Name: ecm
Host Name: tchao
Server Name: PulseAudio (on PipeWire 0.3.65)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: @DEFAULT_SINK@
Default Source: @DEFAULT_SOURCE@
Cookie: 4c9b:a38b

$ pactl list modules short
1   libpipewire-module-rt   {
nice.level= -11
#rt.prio  = 88
#rt.time.soft = -1
#rt.time.hard = -1
}   
2   libpipewire-module-protocol-native  
3   libpipewire-module-profiler 
5   libpipewire-module-metadata 
7   libpipewire-module-spa-device-factory   
9   libpipewire-module-spa-node-factory 
11  libpipewire-module-client-node  
13  libpipewire-module-client-device
15  libpipewire-module-portal   
16  libpipewire-module-access   {
# access.allowed to list an array of paths of allowed
# apps.
#access.allowed = [
#/usr/bin/pipewire-media-session
#]

# An array of rejected paths.
#access.rejected = [ ]

# An array of paths with restricted access.
#access.restricted = [ ]

# Anything not in the above lists gets assigned the
# access.force permission.
#access.force = flatpak
}   
17  libpipewire-module-adapter  
19  libpipewire-module-link-factory 
21  libpipewire-module-session-manager  
536870912   module-always-sink  



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 12.0
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-security')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser 3.134
ii  init-system-helpers 1.65.2
ii  libasound2  1.2.8-1+b1
ii  libasound2-plugins  1.2.7.1-1
ii  libc6   2.36-9
ii  libcap2 1:2.66-4
ii  libdbus-1-3 1.14.6-1
ii  libfftw3-single33.3.10-1
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-2
ii  libgstreamer-plugins-base1.0-0  1.22.0-3
ii  libgstreamer1.0-0   1.22.0-2
ii  libice6 2:1.0.10-1
ii  libltdl72.4.7-5
ii  liborc-0.4-0

Bug#1037308: php8.2-fpm: Fails to start when /run/php doesn't exist.

[Mike Hommey]

On Sun, Jun 11, 2023 at 08:27:57AM +0200, Ondřej Surý wrote:
> Control: severity -1 minor
> Control: tags -1 +wontfix
> 
> The package needs systemd-tmpfiles script to work. It has been explicitly 
> requested to not enforce the dependency on systemd because of “containers”, 
> so I’ve removed it.
> 
> So, I am not going to fix this.

apt install systemd-tmpfiles says:
Package systemd-tmpfiles is a virtual package provided by:
  systemd-standalone-tmpfiles 252.6-1 (= 252.6-1)
  systemd 252.6-1 (= 252.6-1)

and systemd is installed...

Mike

Bug#1037348: ITP: fcitx5-quwei -- Fcitx Input Method Framework v5 (Qu Wei input method)

[Boyuan Yang]

Package: wnpp
Severity: wishlist
Owner: Boyuan Yang 

* Package name: fcitx5-quwei
  Version : 0.0~git20220225.aa4cf7c
  Upstream Author : CSSlayer
* URL : https://github.com/fcitx/fcitx5-quwei
* License : BSD-3-Clause
  Programming Lang: C++
  Description : Fcitx Input Method Framework v5 (Qu Wei input method)

 Fcitx5 is the next generation of fcitx input method framework. It
 provides pleasant and modern input experience with intuitive graphical
 configuration tools. The framework is highly extensible with support
 for GTK+ and Qt toolkits, DBus interfaces, a large variety of desktop
 environments and a developer-friendly API.
 .
 Some of its new features include support of both Wayland and Xorg
 and the ability to mimic IBus Input Method Framework in order to
 provide better compatibility across different Linux distributions
 and desktop environments.
 .
 This package provides the Qu Wei ("区位") input method compatible with
 fcitx5.

This package will be team-maintained in Debian Input Method Team.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#633849: Processed: [bts-link] source package xorg

[Vincent Lefevre]

[I should have Cc'd this to the bug. Sending a copy now.]

tags 633849 wontfix - fixed-upstream
thanks

The upstream bug was closed because "there isn't enough maintainer
time (or motivation) to ever fix this", not because it was fixed.

IMHO, this limitation should be documented (probably in the man pages
of the concerned commands).

I'm also wondering whether the suspend/resume system allows the user
to run scripts to save the current config and restore it.

On 2023-06-11 19:43:03 +, Debian Bug Tracking System wrote:
[...]
> > # remote status report for #633849 (http://bugs.debian.org/633849)
> > # Bug title: xserver-xorg: XKB settings lost after suspend (hibernate) / 
> > resume or USB keyboard plugged in
> > #  * https://gitlab.freedesktop.org/xorg/xserver/issues/266
> > #  * remote status changed: opened -> closed
> > #  * closed upstream
[...]

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1037333: libeconf: CVE-2023-32181 CVE-2023-22652

[Andreas Henriksson]

Hello Salvatore,

On Sun, Jun 11, 2023 at 05:12:57PM +0200, Salvatore Bonaccorso wrote:
> Source: libeconf
> Version: 0.5.1+dfsg1-1
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 
> 
> Hi,
> 
> The following vulnerabilities were published for libeconf.
[...]

Thanks for notifying me about this. I've prepared libeconf 0.5.2
packages in git and just uploaded towards unstable.

IMHO I think uploading the same to stable would be fine (even though
there's one "unrelated" change in new upstream version so maybe not
strictly a security-only release), because libeconf has no reverse
dependencies in the debian archive yet! The risk of regression should
thus be almost non-existant.

If by chance you have the SRM dance in muscle memory, please feel free
to take over getting 0.5.2 into stable! It's been a while for me and
honestly since libeconf is still unused it's very low prio for me.

Regards,
Andreas Henriksson

Bug#1037347: unblock: pssh/2.3.5-2, dvisvgm/3.0.4-1, latexmk/1:4.80-1

[Hilmar Preuße]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Unfortunately I've uploaded pssh, dvisvgm & latexmk to unstable, a while ago,
although the packages were not intended for bookworm. I expected that they will
migrate to testing, once bookworm is released.
All packages still report that they are blocked. Please unblock so they can
migrate to testing now. Many thanks!

Hilmar

unblock pssh/2.3.5-2
unblock dvisvgm/3.0.4-1
unblock latexmk/1:4.80-1

Bug#1037346: cyrus-imapd: all emails disappeared after upgrading from bullseye to bookworm (similar to #1007965)

[Kai Lindenberg]

Package: cyrus-imapd
Version: 3.6.1-4
Severity: important

Dear Maintainer,

today I upgraded our famliy+friends email server system from bullseye to
bookworm including the cyrus-imapd upgrade to v3.6.1-4.

Unfortunately, all mails of all users disappeared and new inboxes were
autocreated when users logged in:

--syslog-
Jun 11 12:27:15 xxx cyrus/imaps[1730301]: autocreateinbox: User x, INBOX
was successfully created
-

The emails were still in the non-uuid directory of the cyrus spool dir. I did
not figure out how this happened, but I solved it by

1. extracting a list of all sub-mailboxes of all users from the filesystem
structure,
2. re-creating the same sub-mailboxes with the cm command of cyradm,
3. and hard-linking all directory content to the new uuid dirs (with the help
of mbpath)

The issue is now solved for me, but I can provide additional system
information and logs if needed.

(same report goes to https://github.com/cyrusimap/cyrus-imapd/issues/4035)

-Kai



-- System Information:
Debian Release: 12.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cyrus-imapd depends on:
ii  cyrus-common  3.6.1-4
ii  libc6 2.36-9
ii  libcom-err2   1.47.0-2
ii  libsasl2-22.1.28+dfsg-10
ii  libssl3   3.0.9-1
ii  libwrap0  7.6.q-32
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages cyrus-imapd recommends:
ii  rsync  3.2.7-1

cyrus-imapd suggests no packages.

-- no debconf information

Bug#1031332: transition: librnd

[Sebastian Ramacher]

Control: tags -1 = confirmed

On 2023-02-14 22:54:12 -0700, Bdale Garbee wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: lib...@packages.debian.org
> Control: affects -1 + src:librnd
> 
> This is a fairly trivial transition due to upstream rolling to a new ABI 
> version.  I originally uploaded this straight to unstabe, but Thorsten asked 
> me to follow the "via experimental" process.
> 
> Because I didn't previously know about this process, all application packages 
> that depend on this new library version (all of which come from the same 
> upstream) have already been uploaded and accepted into unstable with build
> dependencies on the binary packages delivered by source package librnd.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1037344: libavcodec59: library load error: undefined symbol: vaSyncBuffer

[Sebastian Ramacher]

Control: reassign -1 1037343 libavcodec59 7:5.1.3-1
Control: reassign -1 1037340 libavcodec59 7:5.1.3-1
Control: forcemerge -1 1037343 1037340

On 2023-06-11 22:28:00 +0300, alexcon wrote:
> Package: libavcodec59
> Version: 7:5.1.3-1
> Severity: normal
> X-Debbugs-Cc: alexcon...@gmail.com
> 
> Dear Maintainer,
> 
> VLC, MPV video players produce error 'undefined symbol: vaSyncBuffer'

One bug report is enough.

Cheers
-- 
Sebastian Ramacher

Bug#1037345: 389-ds-base: ftbfs with rust-base64 0.21

[plugwash]

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.
diff -Nru 389-ds-base-2.3.1+dfsg1/debian/changelog 
389-ds-base-2.3.1+dfsg1/debian/changelog
--- 389-ds-base-2.3.1+dfsg1/debian/changelog2023-01-24 11:21:19.0 
+
+++ 389-ds-base-2.3.1+dfsg1/debian/changelog2023-06-11 13:22:07.0 
+
@@ -1,3 +1,13 @@
+389-ds-base (2.3.1+dfsg1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch for base64 0.21
+  * Make Debian dependency on base64 match cargo dependency.
+  * Improve clean target.
+  * Use ln -fs instead of ln -s to allow resuming build after fixing errors.
+
+ -- Peter Michael Green   Sun, 11 Jun 2023 13:22:07 +
+
 389-ds-base (2.3.1+dfsg1-1) unstable; urgency=medium
 
   * Repackage the source, filter vendored crates and allow building with
diff -Nru 389-ds-base-2.3.1+dfsg1/debian/control 
389-ds-base-2.3.1+dfsg1/debian/control
--- 389-ds-base-2.3.1+dfsg1/debian/control  2023-01-24 11:21:16.0 
+
+++ 389-ds-base-2.3.1+dfsg1/debian/control  2023-06-11 13:22:07.0 
+
@@ -27,7 +27,7 @@
  libpci-dev,
  libpcre2-dev,
  libperl-dev,
- librust-base64-dev,
+ librust-base64-0.21-dev,
  librust-cbindgen-dev,
  librust-cc-dev,
  librust-crossbeam-dev,
diff -Nru 389-ds-base-2.3.1+dfsg1/debian/patches/base64-0.21.diff 
389-ds-base-2.3.1+dfsg1/debian/patches/base64-0.21.diff
--- 389-ds-base-2.3.1+dfsg1/debian/patches/base64-0.21.diff 1970-01-01 
00:00:00.0 +
+++ 389-ds-base-2.3.1+dfsg1/debian/patches/base64-0.21.diff 2023-06-11 
13:22:07.0 +
@@ -0,0 +1,65 @@
+Description: update for base64 0.21
+Author: Peter Michael Green 
+
+Index: 389-ds-base-2.3.1+dfsg1.new/src/plugins/pwdchan/src/lib.rs
+===
+--- 389-ds-base-2.3.1+dfsg1.new.orig/src/plugins/pwdchan/src/lib.rs
 389-ds-base-2.3.1+dfsg1.new/src/plugins/pwdchan/src/lib.rs
+@@ -42,6 +42,12 @@ macro_rules! ab64_to_b64 {
+ }};
+ }
+ 
++use base64::engine::GeneralPurpose;
++use base64::engine::GeneralPurposeConfig;
++use base64::Engine;
++use base64::alphabet;
++static BASE64CONFIG: GeneralPurposeConfig = 
GeneralPurposeConfig::new().with_decode_allow_trailing_bits(true);
++static BASE64ENGINE: GeneralPurpose = 
GeneralPurpose::new(::STANDARD,BASE64CONFIG);
+ impl PwdChanCrypto {
+ #[inline(always)]
+ fn pbkdf2_decompose(encrypted: ) -> Result<(usize, Vec, Vec), 
PluginError> {
+@@ -62,7 +68,7 @@ impl PwdChanCrypto {
+ .ok_or(PluginError::MissingValue)
+ .and_then(|ab64| {
+ let s = ab64_to_b64!(ab64);
+-base64::decode_config(, 
base64::STANDARD.decode_allow_trailing_bits(true))
++BASE64ENGINE.decode()
+ .map_err(|e| {
+ log_error!(ErrorLevel::Error, "Invalid Base 64 {} -> 
{:?}", s, e);
+ PluginError::InvalidBase64
+@@ -74,7 +80,7 @@ impl PwdChanCrypto {
+ .ok_or(PluginError::MissingValue)
+ .and_then(|ab64| {
+ let s = ab64_to_b64!(ab64);
+-base64::decode_config(, 
base64::STANDARD.decode_allow_trailing_bits(true))
++BASE64ENGINE.decode()
+ .map_err(|e| {
+ log_error!(ErrorLevel::Error, "Invalid Base 64 {} -> 
{:?}", s, e);
+ PluginError::InvalidBase64
+@@ -152,11 +158,11 @@ impl PwdChanCrypto {
+ PluginError::Format
+ })?;
+ // the base64 salt
+-base64::encode_config_buf(, base64::STANDARD,  output);
++BASE64ENGINE.encode_string(,  output);
+ // Push the delim
+ output.push_str("$");
+ // Finally the base64 hash
+-base64::encode_config_buf(_input, base64::STANDARD,  output);
++BASE64ENGINE.encode_string(_input,  output);
+ // Return it
+ Ok(output)
+ }
+Index: 389-ds-base-2.3.1+dfsg1.new/src/plugins/pwdchan/Cargo.toml
+===
+--- 389-ds-base-2.3.1+dfsg1.new.orig/src/plugins/pwdchan/Cargo.toml
 389-ds-base-2.3.1+dfsg1.new/src/plugins/pwdchan/Cargo.toml
+@@ -17,7 +17,7 @@ paste = "1.*"
+ slapi_r_plugin = { path="../../slapi_r_plugin" }
+ uuid = { version = "0.8", features = [ "v4" ] }
+ openssl = { version = "0.10" }
+-base64 = "0.13"
++base64 = "0.21"
+ 
+ [build-dependencies]
+ cc = { version = "1.0", features = ["parallel"] }
diff -Nru 389-ds-base-2.3.1+dfsg1/debian/patches/series 
389-ds-base-2.3.1+dfsg1/debian/patches/series
--- 389-ds-base-2.3.1+dfsg1/debian/patches/series   2023-01-24 
11:21:16.0 +
+++ 389-ds-base-2.3.1+dfsg1/debian/patches/series   2023-06-11 

Bug#1037340: /usr/bin/mpv produce error 'mpv: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer'

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2023-06-11 21:59:48 +0300, alexcon wrote:
> Package: mpv
> Version: 0.35.1-4
> Severity: normal
> X-Debbugs-Cc: alexcon...@gmail.com
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***

Please run ldd -r /lib/x86_64-linux-gnu/libavcodec.so.59 and let us know
the output. I suspect that you have an old version of libva.so.2
somewhere on your LD_LIBRARY_PATH.

Cheers

> 
> -- 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/16 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:ru
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages mpv depends on:
> ii  libarchive13  3.6.2-1
> ii  libasound21.2.8-1+b1
> ii  libass9   1:0.17.1-1
> ii  libavcodec59  7:5.1.3-1
> ii  libavdevice59 7:5.1.3-1
> ii  libavfilter8  7:5.1.3-1
> ii  libavformat59 7:5.1.3-1
> ii  libavutil57   7:5.1.3-1
> ii  libbluray21:1.3.4-1
> ii  libc6 2.36-9
> ii  libcaca0  0.99.beta20-3
> ii  libcdio-cdda2 10.2+2.0.1-1
> ii  libcdio-paranoia2 10.2+2.0.1-1
> ii  libcdio19 2.1.0-4
> ii  libdrm2   2.4.114-1+b1
> ii  libdvdnav46.1.1-1
> ii  libegl1   1.6.0-1
> ii  libgbm1   22.3.6-1+deb12u1
> ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3
> ii  libjpeg62-turbo   1:2.1.5-2
> ii  liblcms2-22.14-2
> ii  liblua5.2-0   5.2.4-3
> ii  libmujs2  1.3.2-1
> ii  libpipewire-0.3-0 0.3.65-3
> ii  libplacebo208 4.208.0-3
> ii  libpulse0 16.1+dfsg1-2+b1
> ii  librubberband23.1.2+dfsg0-1
> ii  libsdl2-2.0-0 2.26.5+dfsg-1
> ii  libsixel1 1.10.3-3
> ii  libswresample47:5.1.3-1
> ii  libswscale6   7:5.1.3-1
> ii  libuchardet0  0.0.7-1
> ii  libva-drm22.17.0-1
> ii  libva-wayland22.17.0-1
> ii  libva-x11-2   2.17.0-1
> ii  libva22.17.0-1
> ii  libvdpau1 1.5-2
> ii  libvulkan11.3.239.0-1
> ii  libwayland-client01.21.0-1
> ii  libwayland-cursor01.21.0-1
> ii  libwayland-egl1   1.21.0-1
> ii  libx11-6  2:1.8.4-2
> ii  libxext6  2:1.3.4-1+b1
> ii  libxinerama1  2:1.1.4-3
> ii  libxkbcommon0 1.5.0-1
> ii  libxpresent1  1.0.0-2+b10
> ii  libxrandr22:1.5.2-2+b1
> ii  libxss1   1:1.2.3-1
> ii  libxv12:1.0.11-1.1
> ii  libzimg2  3.0.4+ds1-1
> ii  zlib1g1:1.2.13.dfsg-1
> 
> Versions of packages mpv recommends:
> ii  xdg-utils  1.1.3-4.1
> ii  yt-dlp 2023.03.04-1
> 
> Versions of packages mpv suggests:
> ii  libcuda1  525.105.17-1
> 
> -- no debconf information
> 

-- 
Sebastian Ramacher

Bug#1037344: libavcodec59: library load error: undefined symbol: vaSyncBuffer

[alexcon]

Package: libavcodec59
Version: 7:5.1.3-1
Severity: normal
X-Debbugs-Cc: alexcon...@gmail.com

Dear Maintainer,

VLC, MPV video players produce error 'undefined symbol: vaSyncBuffer'

-- 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/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libavcodec59 depends on:
ii  libaom3 3.6.0-1
ii  libavutil57 7:5.1.3-1
ii  libc6   2.36-9
ii  libcairo2   1.16.0-7
ii  libcodec2-1.0   1.0.5-1
ii  libdav1d6   1.0.0-2
ii  libglib2.0-02.74.6-2
ii  libgsm1 1.0.22-1
ii  libjxl0.7   0.7.0-10
ii  liblzma55.4.1-0.2
ii  libmfx1 22.5.4-1
ii  libmp3lame0 3.100-6
ii  libopenjp2-72.5.0-2
ii  libopus01.3.1-3
ii  librav1e0   0.5.1-6
ii  librsvg2-2  2.54.5+dfsg-1
ii  libshine3   3.1.1-2
ii  libsnappy1v51.1.9-3
ii  libspeex1   1.2.1-2
ii  libsvtav1enc1   1.4.1+dfsg-1
ii  libswresample4  7:5.1.3-1
ii  libtheora0  1.1.1+dfsg.1-16.1+b1
ii  libtwolame0 0.4.0-2
ii  libva2  2.17.0-1
ii  libvorbis0a 1.3.7-1
ii  libvorbisenc2   1.3.7-1
ii  libvpx7 1.12.0-1
ii  libwebp71.2.4-0.2
ii  libwebpmux3 1.2.4-0.2
ii  libx264-164 2:0.164.3095+gitbaee400-3
ii  libx265-199 3.5-2+b1
ii  libxvidcore42:1.3.7-1
ii  libzvbi00.2.41-1
ii  zlib1g  1:1.2.13.dfsg-1

libavcodec59 recommends no packages.

Versions of packages libavcodec59 suggests:
ii  libcuda1   525.105.17-1
ii  libnvcuvid1525.105.17-1
ii  libnvidia-encode1  525.105.17-1

-- no debconf information

Bug#1037343: vlc produce error: Codec `h264' (H264 - MPEG-4 AVC (part 10)) is not supported.

[alexcon]

Package: vlc
Version: 3.0.18-2
Severity: normal
X-Debbugs-Cc: alexcon...@gmail.com

Dear Maintainer,

full log:

```
vlc -vvv ~/vod/1280_720.mp4
VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2)
[55e8cb0cc550] main libvlc debug: VLC media player - 3.0.18 Vetinari
[55e8cb0cc550] main libvlc debug: Copyright © 1996-2022 the VideoLAN team
[55e8cb0cc550] main libvlc debug: revision 3.0.13-8-g41878ff4f2
[55e8cb0cc550] main libvlc debug: configured with ./configure  
'--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' 
'--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' 
'--sysconfdir=/etc' '--localstatedir=/var' '--disable-option-checking' 
'--disable-silent-rules' '--libdir=${prefix}/lib/x86_64-linux-gnu' 
'--runstatedir=/run' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--disable-debug' '--config-cache' 
'--disable-update-check' '--enable-fast-install' '--docdir=/usr/share/doc/vlc' 
'--with-binary-version=3.0.18-2' '--enable-a52' '--enable-aa' 
'--enable-aribsub' '--enable-avahi' '--enable-bluray' '--enable-caca' 
'--enable-chromaprint' '--enable-chromecast' '--enable-dav1d' '--enable-dbus' 
'--enable-dca' '--enable-dvbpsi' '--enable-dvdnav' '--enable-faad' 
'--enable-flac' '--enable-fluidsynth' '--enable-freetype' '--enable-fribidi' 
'--enable-gles2' '--enable-gnutls' '--enable-harfbuzz' '--enable-jack' 
'--enable-kate' '--enable-libass' '--enable-libmpeg2' '--enable-libxml2' 
'--enable-lirc' '--enable-mad' '--enable-matroska' '--enable-mod' 
'--enable-mpc' '--enable-mpg123' '--enable-mtp' '--enable-ncurses' 
'--enable-notify' '--enable-ogg' '--enable-opus' '--enable-pulse' '--enable-qt' 
'--enable-realrtsp' '--enable-samplerate' '--enable-sdl-image' '--enable-sftp' 
'--enable-shine' '--enable-shout' '--enable-skins2' '--enable-soxr' 
'--enable-spatialaudio' '--enable-speex' '--enable-srt' '--enable-svg' 
'--enable-svgdec' '--enable-taglib' '--enable-theora' '--enable-twolame' 
'--enable-upnp' '--enable-vdpau' '--enable-vnc' '--enable-vorbis' 
'--enable-x264' '--enable-x265' '--enable-zvbi' 
'--with-kde-solid=/usr/share/solid/actions/' '--disable-aom' 
'--disable-crystalhd' '--disable-d3d11va' '--disable-decklink' 
'--disable-directx' '--disable-dsm' '--disable-dxva2' '--disable-fdkaac' 
'--disable-fluidlite' '--disable-freerdp' '--disable-goom' 
'--disable-gst-decode' '--disable-libtar' '--disable-live555' 
'--disable-macosx' '--disable-macosx-avfoundation' '--disable-macosx-qtkit' 
'--disable-mfx' '--disable-microdns' '--disable-opencv' '--disable-projectm' 
'--disable-schroedinger' '--disable-sndio' '--disable-sparkle' '--disable-telx' 
'--disable-vpx' '--disable-vsxu' '--disable-wasapi' '--enable-alsa' 
'--enable-dc1394' '--enable-dv1394' '--enable-libplacebo' '--enable-linsys' 
'--enable-nfs' '--enable-udev' '--enable-v4l2' '--enable-wayland' 
'--enable-vcd' '--enable-smbclient' '--disable-oss' '--enable-mmx' 
'--enable-sse' '--disable-neon' '--disable-altivec' '--disable-omxil' 
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-ffile-prefix-map=/build/vlc-WcXCHF/vlc-3.0.18=. -fstack-protector-strong 
-Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' 'CXXFLAGS=-g -O2 
-ffile-prefix-map=/build/vlc-WcXCHF/vlc-3.0.18=. -fstack-protector-strong 
-Wformat -Werror=format-security ' 'OBJCFLAGS=-g -O2 
-ffile-prefix-map=/build/vlc-WcXCHF/vlc-3.0.18=. -fstack-protector-strong 
-Wformat -Werror=format-security'
[55e8cb0cc550] main libvlc debug: searching plug-in modules
[55e8cb0cc550] main libvlc debug: loading plugins cache file 
/usr/lib/x86_64-linux-gnu/vlc/plugins/plugins.dat
[55e8cb0cc550] main libvlc debug: recursively browsing 
`/usr/lib/x86_64-linux-gnu/vlc/plugins'
[55e8cb0cc550] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/packetizer/libpacketizer_avparser_plugin.so'
 (/lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer)
[55e8cb0cc550] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/demux/libavformat_plugin.so' 
(/lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer)
[55e8cb0cc550] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/access/libavio_plugin.so' 
(/lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer)
[55e8cb0cc550] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/codec/libavcodec_plugin.so' 
(/lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer)
[55e8cb0cc550] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/vdpau/libvdpau_avcodec_plugin.so' 
(/lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer)
[55e8cb0cc550] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/stream_out/libstream_out_chromaprint_plugin.so'
 

Bug#1037342: python3-pyfuse3: should Recommends fuse3

[Geoffrey Thomas]

Package: python3-pyfuse3
Version: 3.2.1-2+b2
Severity: wishlist

Hi!

I tried running a sample filesystem with pyfuse3 on a fresh VM and got
"fuse: failed to exec fusermount3: No such file or directory".

I think the package should have Recommends: fuse3.

-- 
Geoffrey Thomas
geo...@ldpreload.com

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 

Bug#1037341: qemu-system-x86: USB device attach to XEN not work

[Gabor Droszler]

Package: qemu-system-x86
Version: 1:7.2+dfsg-7
Severity: important
X-Debbugs-Cc: drosz...@datatrans.hu

Dear Maintainer,

The new XEN + QEMU don't enable to attach USB device. This works the past 
Debian version.


xl usb-list dtrdp
Devid  Type BE  state usb-ver ports
0  devicemodel  0   0 1   2
  Port 1:
  Port 2:

lsusb
...
Bus 001 Device 002: ID 08e6:3438 Gemalto (was Gemplus) GemPC Key SmartCard 
Reader
...

xl usbdev-attach dtrdp hostbus=1 hostaddr=2
libxl: error: libxl_qmp.c:1837:qmp_ev_parse_error_messages: Domain 
21:'usb-host' is not a valid device model name
libxl: error: libxl_device.c:1468:device_addrm_aocomplete: unable to add device
libxl_device_usbdev_add failed.



-- 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/16 CPU threads; PREEMPT)
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.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 qemu-system-x86 depends on:
ii  ipxe-qemu   1.0.0+git-20190125.36a4c85-5.1
ii  libaio1 0.3.113-4
ii  libbpf1 1:1.1.0-1
ii  libc6   2.36-9
ii  libcapstone44.0.2-5
ii  libfdt1 1.6.1-4+b1
ii  libfuse3-3  3.14.0-4
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-2
ii  libgmp102:6.2.1+dfsg1-1.1
ii  libgnutls30 3.7.9-2
ii  libhogweed6 3.8.1-2
ii  libibverbs1 44.0-2
ii  libjpeg62-turbo 1:2.1.5-2
ii  libnettle8  3.8.1-2
ii  libnuma12.0.16-1
ii  libpixman-1-0   0.42.2-1
ii  libpmem11.12.1-2
ii  libpng16-16 1.6.39-2
ii  librdmacm1  44.0-2
ii  libsasl2-2  2.1.28+dfsg-10
ii  libseccomp2 2.5.4-1+b3
ii  libslirp0   4.7.0-1
ii  libudev1252.6-1
ii  liburing2   2.3-3
ii  libvdeplug2 4.0.1-4
ii  libzstd11.5.4+dfsg2-5
ii  qemu-system-common  1:7.2+dfsg-7
ii  qemu-system-data1:7.2+dfsg-7
ii  seabios 1.16.2-1
ii  zlib1g  1:1.2.13.dfsg-1

Versions of packages qemu-system-x86 recommends:
ii  ovmf  2022.11-6
ii  qemu-block-extra  1:7.2+dfsg-7
pn  qemu-system-gui   
ii  qemu-utils1:7.2+dfsg-7

Versions of packages qemu-system-x86 suggests:
pn  samba  
pn  vde2   

-- no debconf information

Bug#1037340: /usr/bin/mpv produce error 'mpv: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer'

[alexcon]

Package: mpv
Version: 0.35.1-4
Severity: normal
X-Debbugs-Cc: alexcon...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- 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/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mpv depends on:
ii  libarchive13  3.6.2-1
ii  libasound21.2.8-1+b1
ii  libass9   1:0.17.1-1
ii  libavcodec59  7:5.1.3-1
ii  libavdevice59 7:5.1.3-1
ii  libavfilter8  7:5.1.3-1
ii  libavformat59 7:5.1.3-1
ii  libavutil57   7:5.1.3-1
ii  libbluray21:1.3.4-1
ii  libc6 2.36-9
ii  libcaca0  0.99.beta20-3
ii  libcdio-cdda2 10.2+2.0.1-1
ii  libcdio-paranoia2 10.2+2.0.1-1
ii  libcdio19 2.1.0-4
ii  libdrm2   2.4.114-1+b1
ii  libdvdnav46.1.1-1
ii  libegl1   1.6.0-1
ii  libgbm1   22.3.6-1+deb12u1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3
ii  libjpeg62-turbo   1:2.1.5-2
ii  liblcms2-22.14-2
ii  liblua5.2-0   5.2.4-3
ii  libmujs2  1.3.2-1
ii  libpipewire-0.3-0 0.3.65-3
ii  libplacebo208 4.208.0-3
ii  libpulse0 16.1+dfsg1-2+b1
ii  librubberband23.1.2+dfsg0-1
ii  libsdl2-2.0-0 2.26.5+dfsg-1
ii  libsixel1 1.10.3-3
ii  libswresample47:5.1.3-1
ii  libswscale6   7:5.1.3-1
ii  libuchardet0  0.0.7-1
ii  libva-drm22.17.0-1
ii  libva-wayland22.17.0-1
ii  libva-x11-2   2.17.0-1
ii  libva22.17.0-1
ii  libvdpau1 1.5-2
ii  libvulkan11.3.239.0-1
ii  libwayland-client01.21.0-1
ii  libwayland-cursor01.21.0-1
ii  libwayland-egl1   1.21.0-1
ii  libx11-6  2:1.8.4-2
ii  libxext6  2:1.3.4-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxkbcommon0 1.5.0-1
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1.1
ii  libzimg2  3.0.4+ds1-1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages mpv recommends:
ii  xdg-utils  1.1.3-4.1
ii  yt-dlp 2023.03.04-1

Versions of packages mpv suggests:
ii  libcuda1  525.105.17-1

-- no debconf information

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#1020495: Patch to build network-manager-strongswan against GTK 4, too

[Ian Jackson]

Harald Dunkel writes ("Re: Patch to build network-manager-strongswan against 
GTK 4, too"):
> this is intended as a bug fix for both Bookworm and Trixie. N-m-s is
> severely restricted for Gnome desktop without this fix. There is no
> newer upstream version yet.

OK, I will review it for trixie.

Would you check the stable release policy for the update to bookworm ?

Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1017361: ITA: postsrsd -- Sender Rewriting Scheme (SRS) lookup table for Postfix

[Abhijith PA]

Hello,

I would like to adopt this package. I maintain a mailing list server 
where I am already using postsrsd.


--abhijith

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

Bug#1037275: dd: regression - posix expression syntax no longer supported

[Jim Meyering]

On Sat, Jun 10, 2023 at 6:50 AM Pádraig Brady  wrote:
> On 10/06/2023 02:45, Marc Lehmann wrote:
> > Package: coreutils
> > Version: 9.1-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I have a script that was used for some decades on multiple
> > unices. Beginning with bookworm, it stopped working because dd no longer
> > understands POSIX expression syntax for bs=:
> >
> > $ dd if=... bs=1024x1024x32
> > dd: invalid number: ‘1024x1024x32’
> >
> > This should be valid syntax according to POSIX, and was understood on
> > older versions of Debian GNU/Linux:
> >
> > Two or more positive decimal numbers (with or without k or b) separated 
> > by x, specifying the product of the indicated values
>
> Yes this was a regression in coreutils 9.1
> The patch attached is the proposed upstream fix.

Thanks. The patch looks fine.
My only suggestion would be a stylistic one, to change the ">"
comparison to be the equivalent "<" one, i.e., change this:

+  && *suffix == 'B' && (suffix > str && suffix[-1] != 'B'))

to this (also dropping the unnecessary parentheses):

+  && *suffix == 'B' && str < suffix && suffix[-1] != 'B')

Why? Because of the increasing-to-right number-line argument, where
smaller things are visually on the left of larger ones.

Currently, in src/, the uses of space-delimited < and <= outnumber
uses of > and >= by four to one, 1678 to 428.

Bug#1037337: Acknowledgement (mod_dirindex header/footer displayed only at first request during stat cache period)

[Harald Welte]

I've reported this upstream as I couldn't find the problem fixed even
in git master of today.

upstream bug report is at https://redmine.lighttpd.net/issues/3211

I'm attaching my trivial patch fixing the problem.  Given this is a regression
during distribution upgrade, it would be good to get the package updated with
this fix - before other Debian users fall into the same trap during their 
upgrade.

-- 
- Harald Welte   https://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)
>From 40d2ec1a65fe4d6621ee28d8250380846adced57 Mon Sep 17 00:00:00 2001
From: Harald Welte 
Date: Sun, 11 Jun 2023 18:27:56 +0200
Subject: [PATCH] [mod_dirindex] fix unreliable rendering of readme/header
 (closes: #3211)

If the stat_cache keeps the file open after we render a readme/header
file for the first time, we must re-wind the file cursor back to the
start.

This fixes a bug where only the first rendering of the readme/header
works, and subsequent HTTP responses are lacking it as long as the
stat_cache entry lives.
---
 src/mod_dirlisting.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/mod_dirlisting.c b/src/mod_dirlisting.c
index fdfdcdd5..7b152aba 100644
--- a/src/mod_dirlisting.c
+++ b/src/mod_dirlisting.c
@@ -644,6 +644,9 @@ static void http_list_directory_include_file(request_st * const r, const handler
 buffer_clear(out);
 }
 }
+/* rewind the file pointer, as the stat_cache may keep the fd open, resulting
+ * in this function trying to read again */
+lseek(fd, 0, SEEK_SET);
 if (out != tb)
 chunkqueue_append_buffer_commit(cq);
 
-- 
2.40.1

Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed

[Andreas Beckmann]

Control: tag -1 - moreinfo + upstream
Control: retitle -1 dkms: throws up after digesting an empty "$arch"
Control: forwarded -1 https://github.com/dell/dkms/pull/334

to reproduce in a sid chroot:

# ln -s /bin/true /usr/bin/rpm
# apt-get install dkms linux-headers-amd64
...
# apt-get install dkms-test-dkms
...

# apt-get install --reinstall dkms-test-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded.
Need to get 0 B/9484 B of archives.
After this operation, 0 B of additional disk space will be used.
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend 
cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78, <> line 
1.)
debconf: falling back to frontend: Readline
(Reading database ... 31482 files and directories currently installed.)
Preparing to unpack .../dkms-test-dkms_3.0.11-1_all.deb ...
Unpacking dkms-test-dkms (3.0.11-1) over (3.0.11-1) ...
Setting up dkms-test-dkms (3.0.11-1) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
78.)
debconf: falling back to frontend: Readline
Removing old dkms_test-1.0 DKMS files...
Loading new dkms_test-1.0 DKMS files...
Error! DKMS tree already contains: dkms_test-1.0
You cannot add the same module/version combo more than once.
dpkg: error processing package dkms-test-dkms (--configure):
 installed dkms-test-dkms package post-installation script subprocess returned 
error exit status 3
Errors were encountered while processing:
 dkms-test-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

# apt-get install --reinstall dkms-test-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for dkms-test-dkms:amd64

# apt-get remove dkms-test-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  dkms-test-dkms
0 upgraded, 0 newly installed, 1 to remove and 8 not upgraded.
1 not fully installed or removed.
After this operation, 22.5 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 31650 files and directories currently installed.)
Removing dkms-test-dkms (3.0.11-1) ...

# apt-get install dkms-test-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  dkms-test-dkms
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 0 B/9484 B of archives.
After this operation, 22.5 kB of additional disk space will be used.
Selecting previously unselected package dkms-test-dkms.
(Reading database ... 31643 files and directories currently installed.)
Preparing to unpack .../dkms-test-dkms_3.0.11-1_all.deb ...
Unpacking dkms-test-dkms (3.0.11-1) ...
Setting up dkms-test-dkms (3.0.11-1) ...
Removing old dkms_test-1.0 DKMS files...
Loading new dkms_test-1.0 DKMS files...
Error! DKMS tree already contains: dkms_test-1.0
You cannot add the same module/version combo more than once.
dpkg: error processing package dkms-test-dkms (--configure):
 installed dkms-test-dkms package post-installation script subprocess returned 
error exit status 3
Errors were encountered while processing:
 dkms-test-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

In the end I had to clean up with
  rm -rf /var/lib/dkms/dkms_test
to get back to a sane state


Andreas

Bug#1007923: maven-debian-helper: comply to java policy and fix W: bad-jar-name

[tony mancill]

Hello Debian Java,

On Fri, Mar 18, 2022 at 04:34:42PM +0100, Alexandre Rossi wrote:
> Package: maven-debian-helper
> Version: 2.6
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> When I build a package, for instance libhtmlcleaner-java, with 
> maven-debian-helper,
> I get in my lintian output:
> 
> W: bad-jar-name usr/share/java/htmlcleaner.jar
> 
> Debian Java packaging policy states (§ 2.4):
> 
> Their classes must be in jar archive(s) in the directory /usr/share/java,
> with the name packagename[-extraname]-fullversion.jar. The extraname
> is optional and used internally within the package to separate the
> different jars provided by the package. The fullversion is the version
> of that jar file. In some cases that is not the same as the package
> version.
> 
> Some package must also provide a symbolic link from
> packagename-extraname.jar to the most compatible version of the available
> packagename-extraname-version.jar files. 

The change to comply with the Java packaging policy has been uploaded to
unstable for the trixie release cycle.  If we see wide-scale breakage,
we can revisit the issue (and modify policy if needed).  Otherwise, I
intend to address any minor breakage on a package-by-package basis to
comply with policy, and invite others to as well.

Thank you to all for the discussion and help on this long-standing
issue.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#1037338: mtools.1: some formatting fixes for the manual

[Bjarni Ingi Gislason]

Package: mtools
Version: 4.0.33-1+really4.0.32-1
Severity: minor
Tags: patch

Dear Maintainer,

here are some fixes.

Input file is mtools.1

Output from "mandoc.loc  -T lint mtools.1"
mandoc: mtools.1:16:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:27:82: STYLE: input text line longer than 80 bytes: instance, 
commands s...
mandoc: mtools.1:31:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:33:2: WARNING: skipping paragraph macro: PP after SH
mandoc: mtools.1:44:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:60:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:62:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:92:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:94:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:119:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:138:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:143:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:145:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:151:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:153:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:161:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:176:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:210:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:223:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:236:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:248:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:259:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:261:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:334:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:336:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:354:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:356:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:374:1: WARNING: skipping paragraph macro: sp after PP
mandoc: mtools.1:380:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:382:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:398:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:411:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:413:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:433:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:435:2: WARNING: skipping paragraph macro: PP after SS
mandoc: mtools.1:442:86: STYLE: input text line longer than 80 bytes: 
configuration file. ...
mandoc: mtools.1:457:2: WARNING: skipping paragraph macro: PP empty
mandoc: mtools.1:470:55: STYLE: whitespace at end of input line
mandoc: mtools.1:476:2: WARNING: skipping paragraph macro: PP empty

###

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

470:from the device driver.  These can be safely ignored.  

#

Reduce space between words.

103:changes using a configuration file (see section  Configuration).
466:(see section  global variables)

#

Increase size of ~ (tilde) to make it more visible
with "troff" by using character \(ti.

167:thisisatest THISIS~1filename too long
168:alain.knaff ALAIN~1.KNA extension too long
169:prn.txt PRN~1.TXT   PRN is a device name
170:\&\&.abcABC~1   null filename
171:hot+coldHOT_CO~1illegal character

#

Use the word (in)valid instead of (il)legal if not related to legal
matters.
See "www.gnu.org/prep/standards".
Think about translations into other languages!

mtools.1:171:hot+coldHOT_CO~1illegal character
mtools.1:183:Illegal characters are replaced by underscores. The illegal 
characters
mtools.1:232:that are not acceptable, even in VFAT. There are still some illegal
mtools.1:243:ab:cab_c-1  illegal character
mtools.1:252:illegal:
mtools.1:255:Illegal characters are replaces by underscores,

#

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

114: mcopy -i my-image-file.bin ::file1 ::file2 .
133: mcopy -i my-image-file.bin@@1M ::file1 ::file2 .

#

Use \(en for a dash (en-dash) between space characters, not a minus
(\-) or a hyphen (-), except in the NAME section.

mtools.1:4:mtools - utilities to access DOS disks in Unix.

#

"\fR" might be redundant, use "\fP" or remove.

45:\&\fR
120:\&\fR
177:\&\fR
249:\&\fR
375:\&\fR

#

--- mtools.12023-06-06 00:35:33.0 +
+++ mtools.1.new2023-06-11 16:06:28.0 +
@@ -1,7 +1,7 @@
 '\" t
 .TH mtools 1 "10Jul21" mtools-4.0.32
 .SH Name
-mtools - utilities to access DOS disks in Unix.
+mtools \- utilities to access DOS disks 

Bug#1037337: mod_dirindex header/footer displayed only at first request during stat cache period

[Harald Welte]

Package: lighttpd
Version: 1.69-1
Severity: normal

I noticed the following regresion after  upgrading to Debian 12 today:

When mod_dirindex is configured to include a header and/or readme into
the directory index (using the dir-listing.show-header or
dir-listing.show-readme options), said header/readme files are not
included reliably into the HTTP response.

Specifically, it looks as if the first request after a pause (or
restart) gets the header/readme included, but any subsequent requests
inside a certain period are rendered without the header/readme.

I tried different stat-cache implementations: "disable", "inotify" and
"simple" - they all could reproduce the same behaviour.

When strace()ing lighttpd, one can clearly see that the README.txt file
(I use dir-listing.show-readme = "README.txt") access pattern changes:

Working case:
newfstatat(AT_FDCWD, "/data/www/user_dir/HEADER.txt"...
openat(AT_FDCWD, "/data/www/user_dir/HEADER.txt"...

non-working case:
newfstatat(AT_FDCWD, "/data/www/user_dir/HEADER.txt"...

so somehow the file is not opened on the second request.

Some debugging and instrumentation later, it seems that the file is
opened on first access, and then kept open by the stat_cache (even when
"disable" is used, which probably is a separate bug).

However, the mod_dirlisting.c code read()s the file *without rewinding
back after reading it*.  This explains why on first read after open it
succeeds, and subsequent reads then return no data as the read cursor
is already at EOF.

I've so far looked only at debians 1.69-1 sources.  Will check upstream
next and see if there's a fix already available.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lighttpd depends on:
ii  init-system-helpers1.65.2
ii  libc6  2.36-9
ii  libcrypt1  1:4.4.33-2
ii  libnettle8 3.8.1-2
ii  libpcre2-8-0   10.42-1
ii  libxxhash0 0.8.1-1
ii  lsb-base   11.6
ii  media-types10.0.0
ii  mime-support   3.66
ii  systemd-sysv   252.6-1
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages lighttpd recommends:
pn  lighttpd-mod-deflate  
pn  lighttpd-mod-openssl  
ii  perl  5.36.0-7
pn  spawn-fcgi

Versions of packages lighttpd suggests:
ii  apache2-utils 2.4.57-2
pn  lighttpd-doc  
pn  lighttpd-mod-webdav   
pn  lighttpd-modules-dbi  
pn  lighttpd-modules-lua  
ii  openssl   3.0.9-1
pn  php-cgi   
pn  php-fpm   

Bug#1037327: MariaDB upgrade fails if page compressed tables exist already due to plugin dependency

[Otto Kekäläinen]

Thanks for the report!

We have gone back-and-forth on if the server should have 'depends' or
'recommends' or the compression plugins (eg.
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/36)
but actually have not considered that the provider plugins indeed could
also have adjusted if they depend or just weakly recommend the server.

I will do some testing on this.

Bug#1037336: devscripts: Script /usr/bin/debchange doesn't contain the current distro name "bookworm" among ones hardcoded in that script

[VSYakovetsky]

Package: devscripts
Version: 2.23.4
Severity: minor
X-Debbugs-Cc: vsyakovet...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
  trying to build a custom package on the debian12

   * What exactly did you do (or not do) that was effective (or ineffective)?
  dch --create -c debian/changelog.tmp --package=PKGNAME -v REV -D bookworm 
-u low -M PKGDESCRIPTION

   * What was the outcome of this action?
  dch warning: Recognised distributions are: 
  experimental, unstable, testing, stable, oldstable, oldoldstable,
  {bullseye,buster,stretch,jessie,wheezy}-proposed-updates,
  {testing,stable,oldstable,oldoldstable}-proposed-updates,
  {bullseye,buster,stretch,jessie,wheezy}-security,
  {testing,stable,oldstable,oldoldstable}}-security, bullseye-backports, 
bookworm-backports and UNRELEASED.
  Using your request anyway.
  dch: fatal error at line 784:

   * What outcome did you expect instead?
  the same outcome as with previous distributions of debian

*** End of the template - remove these template lines ***


-- Package-specific info:

--- /etc/devscripts.conf ---
Empty.

--- ~/.devscripts ---
Not present

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages devscripts depends on:
ii  dpkg-dev  1.21.22
ii  fakeroot  1.31-1.2
ii  file  1:5.44-3
ii  gnupg 2.2.40-1.1
ii  gpgv  2.2.40-1.1
ii  libc6 2.36-9
ii  libfile-dirlist-perl  0.05-3
ii  libfile-homedir-perl  1.006-2
ii  libfile-touch-perl0.12-2
ii  libfile-which-perl1.27-2
ii  libipc-run-perl   20220807.0-1
ii  libmoo-perl   2.005005-1
ii  libwww-perl   6.68-1
ii  patchutils0.4.2-1
ii  perl  5.36.0-7
ii  python3   3.11.2-1+b1
ii  sensible-utils0.0.17+nmu1
ii  wdiff 1.2.2-5

Versions of packages devscripts recommends:
ii  apt 2.6.1
ii  curl7.88.1-10
ii  dctrl-tools 2.24-3+b1
ii  debian-keyring  2022.12.24
ii  dput1.1.3
ii  equivs  2.3.1
ii  libdistro-info-perl 1.5
ii  libdpkg-perl1.21.22
ii  libencode-locale-perl   1.05-3
ii  libgit-wrapper-perl 0.048-2
ii  libgitlab-api-v4-perl   0.26-3
ii  liblist-compare-perl0.55-2
ii  liblwp-protocol-https-perl  6.10-1
ii  libsoap-lite-perl   1.27-3
ii  libstring-shellquote-perl   1.04-3
ii  libtry-tiny-perl0.31-2
ii  liburi-perl 5.17-1
ii  licensecheck3.3.5-1
ii  lintian 2.116.3
ii  man-db  2.11.2-2
ii  patch   2.7.6-7
ii  pristine-tar1.50
ii  python3-apt 2.6.0
ii  python3-debian  0.1.49
ii  python3-magic   2:0.4.26-3
ii  python3-requests2.28.1+dfsg-1
ii  python3-unidiff 0.7.3-1
ii  python3-xdg 0.28-2
ii  strace  6.1-0.1
ii  unzip   6.0-28
ii  wget1.21.3-1+b2
ii  xz-utils5.4.1-0.2

Versions of packages devscripts suggests:
pn  adequate 
pn  at   
pn  autopkgtest  
pn  bls-standalone   
pn  bsd-mailx | mailx
ii  build-essential  12.9
pn  check-all-the-things 
pn  cvs-buildpackage 
ii  debhelper13.11.4
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
pn  elpa-devscripts  
pn  faketime 
pn  gnuplot  
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-3
pn  libdbd-pg-perl   
ii  libfile-desktopentry-perl0.22-3
pn  libterm-size-perl
ii  libtimedate-perl 2.3300-2
pn  libyaml-syck-perl
pn  mmdebstrap   
pn  mozilla-devscripts   
pn  mutt 
ii  openssh-client [ssh-client]  1:9.2p1-2
pn  piuparts 
pn  postgresql-client
pn  pristine-lfs 
pn  quilt
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
pn  w3m  

-- no debconf information

Bug#1037335: linux-image-6.1.0-9-amd64: fans don't work after resuming from sleep mod

[tuquilo]

Package: src:linux
Version: 6.1.27-1
Severity: normal
X-Debbugs-Cc: moilo...@gmail.com

Dear Maintainer,

   * Waking from sleep mod causes this bug
   * I tried on other distro
   * It doesn't work

After waking from sleeping mod the fans work for 1 sec and after it stops until
I restart my laptop


-- Package-specific info:
** Version:
Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64 
root=UUID=60f0aab7-2d00-4ddf-8f9d-af7316bd504b ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: E402SA
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: E402SA.300
board_vendor: ASUSTeK COMPUTER INC.
board_name: E402SA
board_version: 1.0   

** Loaded modules:
rfcomm
cmac
algif_hash
ecb
algif_skcipher
af_alg
bnep
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
ccm
ath3k
btusb
btrtl
btbcm
btintel
btmtk
bluetooth
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
videodev
jitterentropy_rng
mc
ctr
qrtr
drbg
ansi_cprng
ecdh_generic
ecc
intel_powerclamp
coretemp
kvm_intel
kvm
binfmt_misc
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
nls_ascii
snd_hda_intel
irqbypass
nls_cp437
snd_intel_dspcfg
snd_intel_sdw_acpi
vfat
snd_hda_codec
mei_hdcp
intel_rapl_msr
fat
joydev
snd_hda_core
snd_hwdep
ath9k
snd_pcm
ghash_clmulni_intel
cryptd
ath9k_common
asus_nb_wmi
ath9k_hw
asus_wmi
ath
sha512_ssse3
platform_profile
sha512_generic
mac80211
processor_thermal_device_pci_legacy
sparse_keymap
snd_timer
processor_thermal_device
libarc4
intel_cstate
ledtrig_audio
processor_thermal_rfim
cfg80211
mei_txe
iTCO_wdt
pcspkr
processor_thermal_mbox
intel_pmc_bxt
snd
processor_thermal_rapl
iTCO_vendor_support
intel_rapl_common
intel_xhci_usb_role_switch
mei
watchdog
rfkill
roles
soundcore
intel_soc_dts_iosf
elan_i2c
pwm_lpss_platform
pwm_lpss
int3400_thermal
acpi_thermal_rel
ac
int3403_thermal
int340x_thermal_zone
asus_wireless
intel_int0002_vgpio
serio_raw
evdev
msr
parport_pc
ppdev
lp
parport
fuse
loop
efi_pstore
dm_mod
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
i915
xhci_pci
drm_buddy
i2c_algo_bit
xhci_hcd
drm_display_helper
r8169
rtsx_pci_sdmmc
cec
rc_core
ttm
realtek
mdio_devres
crct10dif_pclmul
drm_kms_helper
crct10dif_common
crc32_pclmul
mmc_block
usbcore
drm
crc32c_intel
i2c_i801
rtsx_pci
lpc_ich
libphy
i2c_smbus
i2c_hid_acpi
usb_common
fan
battery
video
i2c_hid
sdhci_acpi
sdhci
dw_dmac
wmi
dw_dmac_core
mmc_core
hid
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 35)
Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [1043:1d5d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:0b.0 Signal processing controller [1180]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management 
Controller [8086:22dc] (rev 35)
Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series Power Management Controller [1043:1d5d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 35) (prog-if 
30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [1043:1d5d]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:1a.0 Encryption controller [1080]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:2298] (rev 
35)
Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [1043:1d5d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+

Bug#1037334: Synaptic GUI icons not appearing in KDE desktop on Debian Sid

[Edward]

Package: synaptic
Version: 0.91.3

The GUI for Synaptic in Debian Sid, KDE desktop (in both X11 and Wayland) 
is not displaying any icons, except for Apply. 

Software - KDE Plasma Version: 5.27.5, KDE Frameworks Version: 5.103.0, Qt 
Version: 5.15.8, Kernel: 6.1.0-9-amd64


A screenshot is attached.

Bug#1021911: mailto:sub...@bugs.debian.org

[Toralf Förster]

On Tue, 15 Nov 2022 10:11:25 +0100 =?UTF-8?Q?Toralf_F=c3=b6rster?=
 wrote:

On 11/15/22 01:08, Paul Wise wrote:
> One workaround would be for you to add an apt hook for this:
>
> /etc/apt/apt.conf.d/99-obfs4proxy-capability:
>
> DPkg::Post-Invoke { "setcap cap_net_bind_service=+ep 
/usr/bin/obfs4proxy"; };

This is a good work around - thx.

--
Toralf


Today I upgraded from bullseye to bookworm. For some reason however
after that Tor gave the well-known warning:

"(obfs4 listen tcp 0.0.0.0:443: bind: permission denied)"

I fixed it with an Ansible role but was wondering, why it was needed.

--
Toralf

Bug#1037333: libeconf: CVE-2023-32181 CVE-2023-22652

[Salvatore Bonaccorso]

Source: libeconf
Version: 0.5.1+dfsg1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for libeconf.

CVE-2023-32181[0]:
| A Buffer Copy without Checking Size of Input ('Classic Buffer
| Overflow') vulnerability in openSUSE libeconf allows for DoS via
| malformed configuration files This issue affects libeconf: before
| 0.5.2.


CVE-2023-22652[1]:
| A Buffer Copy without Checking Size of Input ('Classic Buffer
| Overflow') vulnerability in openSUSE libeconf leads to DoS via
| malformed config files. This issue affects libeconf: before 0.5.2.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-32181
https://www.cve.org/CVERecord?id=CVE-2023-32181
https://github.com/openSUSE/libeconf/issues/178
[1] https://security-tracker.debian.org/tracker/CVE-2023-22652
https://www.cve.org/CVERecord?id=CVE-2023-22652
https://github.com/openSUSE/libeconf/issues/177
[3] 
https://github.com/openSUSE/libeconf/commit/8d086dfc69d4299e55e4844e3573b3a4cf420f19

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1037332: libva: obsolete Homepage URL

[Vincent Lefevre]

Source: libva
Version: 2.17.0-1
Severity: normal

The control file has

Homepage: https://01.org/linuxmedia/vaapi

but this URL gives "You are not authorized to access this page."

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1037331: vainfo: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

[Vincent Lefevre]

Package: vainfo
Version: 2.12.0+ds1-1
Severity: important

I get the following error:

zira:~> vainfo
libva info: VA-API version 1.17.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, 
driver_name = (null)
vaInitialize failed with error code -1 (unknown libva error),exit

This error is rather meaningless. In case an error is expected,
one should get a clear error message.

Note that I'm using the Nvidia drivers.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vainfo depends on:
ii  libc6   2.36-9
ii  libva-drm2  2.17.0-1
ii  libva-wayland2  2.17.0-1
ii  libva-x11-2 2.17.0-1
ii  libva2  2.17.0-1
ii  libwayland-client0  1.21.0-1
ii  libx11-62:1.8.4-2

vainfo recommends no packages.

vainfo suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1037330: ayatana-indicator-datetime: Impossible to play custom alarm sounds set up via lomiri-clock-app

[Mike Gabriel]

Package: ayatana-indicator-datetime
Severity: important
Version: 22.9.1-1
Tags: patch

When configuring an alarm via lomiri-clock-app,  
ayatana-indicator-datetime is responsible for playing the alarm sound  
once the alarm time is reached.


With 22.9.1 of ayatana-indicator-datetime, only the default alarm  
sound gets played, even if a custom alarm sound is configured via  
lomiri-clock-app.


Upstream provided a patch to fix this:
https://github.com/AyatanaIndicators/ayatana-indicator-datetime/commit/e089a84b306ef09667752b910d87538043140042

This change should be provided in bookworm via a propose-update.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpMDXDyO1cIp.pgp
Description: Digitale PGP-Signatur

Bug#1037329: IP address gets lost

[Thomas Lange]

Package: fai-client
Version: 6.0
Severity: important

A FAI client booting via network get it's IP address from a DHCP
server and the kernel holds this IP only for the lease time. Since we
do not run dhclient on the client, it looses its IP address after some
time and the network installation hangs. You cannot log into the
machine any more.
Error message on the console:

nfs: server 192.168.33.250 not responding, timed out



The code that sets the lifetime for IP addresses to forever was
removed in aa429361806091b1f2abed8b31f15f6a30eec6e2, because we wanted
to solve a problem by starting dhclient. But that code was removed in
55df9af456e0fc3048d3fefb490fe4c47fe271ae, so we must use the old code.


-- 
regaards Thomas

Bug#1034128:

[Andreas Hasenack]

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

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#1020495: Patch to build network-manager-strongswan against GTK 4, too

[Harald Dunkel]

Hi Ian,

this is intended as a bug fix for both Bookworm and Trixie. N-m-s is
severely restricted for Gnome desktop without this fix. There is no
newer upstream version yet.

The git commit is 9af28ccd2176633d95a3c15edee2518ce4e7e0c6 on
https://salsa.debian.org/debian/network-manager-strongswan, tagged
debian/1.6.0-2.


Thank you very much

Harri



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009027: mesa: Please enable panfrost vulkan driver

[Diederik de Haas]

On Fri, 8 Apr 2022 07:16:25 +0300 Timo Aaltonen  wrote:
> Emma Anholt kirjoitti 7.4.2022 klo 22.41:
> >>> VULKAN_DRIVERS
> >>> - panfrost (there is already a gallium driver for this)
> >>
> >> ok
> > 
> > panvk is very much not ready for use and shouldn't be packaged.
> 
> thanks, won't add it then

A year has passed, Bookworm has been released and I'm seeing quite some 
activity in the upstream repo wrt panfrost vulkan driver:
https://gitlab.freedesktop.org/mesa/mesa/-/commits/main/src/panfrost/vulkan

Would now be a good time to enable vulkan for panfrost?

signature.asc
Description: This is a digitally signed message part.

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#1019307: bluebird-gtk-theme: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev

[Simon McVittie]

Control: severity -1 serious
Control: tags -1 + trixie sid

On Wed, 07 Sep 2022 at 10:10:27 +0100, Simon McVittie wrote:
> 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.

I intend to remove libgdk-pixbuf2.0-dev during the trixie cycle (it should
really have been removed already during bookworm, but we never got there)
so I'm raising this to serious.

smcv

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

[Simon McVittie]

Control: severity -1 serious
Control: tags -1 + trixie sid

On Wed, 07 Sep 2022 at 10:08:55 +0100, Simon McVittie wrote:
> 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.

I intend to remove libgdk-pixbuf2.0-dev during the trixie cycle (it should
really have been removed already during bookworm, but we never got there)
so I'm raising this to serious.

smcv

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

[Simon McVittie]

Control: severity -1 serious
Control: tags -1 + trixie sid

On Wed, 07 Sep 2022 at 10:07:54 +0100, Simon McVittie wrote:
> 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.

I intend to remove libgdk-pixbuf2.0-dev during the trixie cycle (it should
really have been removed already during bookworm, but we never got there)
so I'm raising this to serious.

smcv

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

[Simon McVittie]

Control: severity -1 serious
Control: tags -1 + trixie sid

On Sat, 28 Nov 2020 at 15:57:54 +, Simon McVittie wrote:
> In Debian 10 and older, the libgdk-pixbuf2.0-dev package contains
> development files for two libraries: gdk-pixbuf-2.0 and the deprecated
> gdk-pixbuf-xlib-2.0.
> 
> In testing/unstable, it has been split into libgdk-pixbuf-2.0-dev
> and libgdk-pixbuf-xlib-2.0-dev packages, in preparation for a new
> upstream release of gdk-pixbuf-2.0 that moves gdk-pixbuf-xlib-2.0
> into a separate source package. 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.
> 
> It looks as though ukwm only requires the main gdk-pixbuf-2.0
> library. Please update the -dev Depends so that it only pulls in that
> part, as in the attached patch.

I intend to remove libgdk-pixbuf2.0-dev during the trixie cycle (it should
really have been removed already during bookworm, but we never got there)
so I'm raising this to serious.

smcv

Bug#1025561: packages with dependencies on transitional policykit-1 package

[Michael Terry]

Good news! You can simply drop the Depends entirely for Deja Dup. It used to 
used pkexec, but no longer user policykit at all, since version 42.0 I believe.

Bug#1037328: Bug on Debian 12 Bookworm - Installation-reports - EFI partition installation

[pham...@bluewin.ch]

Package: Installation-reports - EFI partition installation
Severity: High

Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with 
Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI 
partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI 
partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of 
the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost 
full, I have no possibility of installing other OSes ;-( This 100 MB partition 
being ridiculously small and not expandable, it does not also cannot benefit 
from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe

Bug#1037316: www.debian.org: Download links on www.debian.org after release = no iso images, only BT

[Holger Wansing]

Hi,

Holger Wansing  wrote (Sun, 11 Jun 2023 13:54:43 +0200):
> That's correct, there are some things to update:
> - netinst images are now much larger due to included firmware, 
>   150-300 MB is no longer correct.
> - multi-arch netinst images are no longer being built

Now done with
https://salsa.debian.org/webmaster-team/webwml/-/commit/c64bdf15d82617c46942470ac0846ed7ec8b0f74

Affects
CD/http-ftp/index.wml
CD/netinst/index.wml 



Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1025545: packages with dependencies on transitional policykit-1 package

[Simon McVittie]

Control: severity -1 important
Control: tags -1 + trixie sid

On Tue, 06 Dec 2022 at 13:09:22 +, Simon McVittie wrote:
> This package has a Depends on the transitional package policykit-1, which
> has been separated into polkitd, pkexec and (deprecated) polkitd-pkla
> packages.

Now that bookworm has been released, I'm intending to remove the
policykit-1 transitional package during the trixie cycle, so I'm raising
the severity of depends/recommends on the transitional package to
important. The severity will increase to serious later on.

(I'm doing this for packages with only a Recommends too, even though those
don't technically prevent removal of policykit-1, because a Recommends
on a package that no longer exists is not allowed under Policy §2.2.1.)

smcv

Bug#1020495: Patch to build network-manager-strongswan against GTK 4, too

[Ian Jackson]

Harald Dunkel writes ("Re: Patch to build network-manager-strongswan against 
GTK 4, too"):
> I have to appologize for not checking my bug reports. There is no
> excuse for that. I am very sorry.
> 
> I have applied Moritz' patch to the source repository on Salsa and
> verified the GUI using Gnome on Bookworm. The error message is
> gone now.
> 
> @Ian, if you have some spare minutes, would you mind to upload the
> fixed version 1.6.0-2, if it looks OK to you? There are no source
> code changes, just a modified configure command line and some
> additional dependencies. Janitor made changes to the debian directory
> on Salsa as well. Included.

FTAOD you intend this for trixie ?

AFAICT from the mails on d-d-a I could upload now and it will be
processed "in due course".

Can you confirm the precise git commit hash you intend to release?

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1037316: www.debian.org: Download links on www.debian.org after release = no iso images, only BT

[Holger Wansing]

Hi,

"Andrew M.A. Cater"  wrote (Sun, 11 Jun 2023 11:26:16 
+):
> https://www.debian.org/download links to https://www.debian.org/distrib/
> 
> This page is missing links to larger images like DVD and the only links
> are the links to torrents.
> 
> Debian Live links are also only torrents

https://www.debian.org/distrib/ is like this for ages, nothing has changed.
I guess this is to save bandwidth on cdimage mirrors? (it's only DVD and BT
images, which are BT-only; there are direct download links for netinst images)

> https://www.debian.org/CD/ still has suggestions for 11.7

This is fixed in the meantime; I guess you watched a cached version of the
page or the page rebuild wasn't ready at that time (I encountered similar this
morning).

> https://www.debian.org/CD/http-ftp/ then needs rewrite

That's correct, there are some things to update:
- netinst images are now much larger due to included firmware, 
  150-300 MB is no longer correct.
- multi-arch netinst images are no longer being built



Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

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#1037327: MariaDB upgrade fails if page compressed tables exist already due to plugin dependency

[Laurence Parry]

Package: mariadb-server
Version: 1:10.11.3-1

Dear Maintainer,

When trying to upgrade a (sysvinit) Debian Bullseye[-backports] server with
MariaDB 10.5 to Bookworm, I ran into the following issue:

Setting up mariadb-server (1:10.11.3-1) ...
Stopping MariaDB database server: mariadbd.
Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mariadb, action "start" failed.
dpkg: error processing package mariadb-server (--configure):
 installed mariadb-server package post-installation script subprocess
returned error exit status 1
[...]
dpkg: dependency problems prevent configuration of
mariadb-plugin-provider-lz4:
 mariadb-plugin-provider-lz4 depends on mariadb-server (>= 1:10.11.1-1);
however:
  Package mariadb-server is not configured yet.

dpkg: error processing package mariadb-plugin-provider-lz4 (--configure):
 dependency problems - leaving unconfigured

This occurred because the piwik/matamo database already contained
lz4-compressed tables. MariaDB complained about lacking the plugin, and
mariadb-server could not complete config. mariadb-plugin-provider-lz4 could
not be installed as it depended on mariadb-server.

My my.cnf has (from https://mariadb.com/kb/en/innodb-page-compression/ ):
innodb_compression_algorithm=lz4
innodb_compression_default=ON

I ended up having to manually download from:
https://packages.debian.org/bookworm/amd64/mariadb-plugin-provider-lz4/download
and force it to ignore the dependency:
dpkg -i --force-depends mariadb-plugin-provider-lz4_10.11.3-1_amd64.deb

After this I could fix the installation and the server started. Removing
the plugin package predictably breaks the server again - this also
reproduces the "not available" error I got after trying to run the server
manually, which wasn't surfaced during the install:

2023-06-11 13:08:58 0 [Note] Starting MariaDB 10.11.3-MariaDB-1 source
revision  as process 16188
2023-06-11 13:08:58 0 [ERROR] mysqld: Can't open shared library
'/usr/lib/mysql/plugin/provider_lz4.so' (errno: 2, cannot open shared
object file: No such file or directory)
2023-06-11 13:08:58 0 [ERROR] Couldn't load plugins from 'provider_lz4.so'.
2023-06-11 13:08:58 0 [ERROR] mysqld: InnoDB: compression algorithm lz4 (2)
is not available. Please, load the corresponding provider plugin.
2023-06-11 13:08:58 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-06-11 13:08:58 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE
ENGINE failed.
2023-06-11 13:08:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-06-11 13:08:58 0 [ERROR] mysqld: unknown variable
'provider_lz4=force_plus_permanent'
2023-06-11 13:08:58 0 [ERROR] Aborting

I can appreciate that the plugins may rely on mariadb-server to be
installed to an extent. However it does not have to be installed the whole
way otherwise dpkg wouldn't have worked. Perhaps the plugins could be
installed despite mariadb-server not being fully configured, and in this
case it should trigger the server to be reconfigured after the plugins are
installed.

Sample table structure shows "PAGE_COMPRESSED":
| piwik_log_action | CREATE TABLE `piwik_log_action` (
  `idaction` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(4096) DEFAULT NULL,
  `hash` int(10) unsigned NOT NULL,
  `type` tinyint(3) unsigned DEFAULT NULL,
  `url_prefix` tinyint(2) DEFAULT NULL,
  PRIMARY KEY (`idaction`),
  KEY `index_type_hash` (`type`,`hash`)
) ENGINE=InnoDB AUTO_INCREMENT=116404687 DEFAULT CHARSET=utf8mb4
COLLATE=utf8mb4_general_ci `PAGE_COMPRESSED`=1 |

# uname -a
Linux acedia 6.1.27 #1 SMP Thu Jun  8 16:12:46 CEST 2023 x86_64 GNU/Linux
Libc: Version: 2.36-9

Best regards,
-- 
Laurence "GreenReaper" Parry
https://www.greenreaper.co.uk

Bug#1037316: www.debian.org: Download links on www.debian.org after release = no iso images, only BT

[Andrew M.A. Cater]

On Sun, Jun 11, 2023 at 12:54:43PM +0200, Holger Wansing wrote:
> Hi,
> 
> Am 11. Juni 2023 11:29:54 MESZ schrieb "Andrew M.A. Cater" 
> :
> >Package: www.debian.org
> >Severity: important
> >
> >Dear Maintainer,
> >
> >*** Reporter, please consider answering these questions, where appropriate 
> >***
> >
> >   * What led up to the situation?
> >
> >Following Bookworm release and new layout: download links missing on 
> >www.debian.org for live CDs and some other images. Only BT links are there.
> >
> >   * What exactly did you do (or not do) that was effective (or
> > ineffective)?
> >
> >Followed download link on front page https://www.debian.org

https://www.debian.org/download links to https://www.debian.org/distrib/

This page is missing links to larger images like DVD and the only links
are the links to torrents.

Debian Live links are also only torrents

https://www.debian.org/CD/ still has suggestions for 11.7

https://www.debian.org/CD/http-ftp/ then needs rewrite

Most of these are in progress somewhere, I know, and stuff is busy, busy

Thanks, Andy
> >
> >   * What was the outcome of this action?
> >
> >Redirect to appropriate page but links missing.
> >
> >   * What outcome did you expect instead?
> >
> >Download links to full CD/DVD/debian-live DVD images
> >
> 
> Please report the exact link of the page where you encounter this!
> 
> Holger
> 
> 
> 
> -- 
> Sent from /e/ OS on Fairphone3

Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed

[Andreas Beckmann]

Control: reassign -1 dkms
Control: severity -1 important

Hi Tim,

thanks for tracking this down and the detailed description.
I already have a fix to not use rpm at all on Debian based systems 
(mainly because it creates an empty unused rpm database), but that was a 
bit too late for being included in bookworm (right now available in 
experimental).
I'll try to reproduce your issue and make dkms fail with a meaningful 
error message on empty $arch.


Andreas

Bug#1037326: RM: lilo -- RoQA; no longer maintained, not included in (old)stable

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: l...@packages.debian.org
Control: affects -1 + src:lilo

Joachim Wiedorn announced on #973850 that lilo development was closed
in 2016, and as a result it was not included in bullseye or bookworm.
Back in 2021, I wrote:

> If [lilo should be removed from unstable], 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.

and Joachim replied:

> I think I will do it in the autumn of 2022.

Now that bookworm has also been released without lilo, I think it's time
to remove this package from unstable.

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

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#1037316: www.debian.org: Download links on www.debian.org after release = no iso images, only BT

[Holger Wansing]

Hi,

Am 11. Juni 2023 11:29:54 MESZ schrieb "Andrew M.A. Cater" 
:
>Package: www.debian.org
>Severity: important
>
>Dear Maintainer,
>
>*** Reporter, please consider answering these questions, where appropriate ***
>
>   * What led up to the situation?
>
>Following Bookworm release and new layout: download links missing on 
>www.debian.org for live CDs and some other images. Only BT links are there.
>
>   * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
>Followed download link on front page
>
>   * What was the outcome of this action?
>
>Redirect to appropriate page but links missing.
>
>   * What outcome did you expect instead?
>
>Download links to full CD/DVD/debian-live DVD images
>

Please report the exact link of the page where you encounter this!

Holger



-- 
Sent from /e/ OS on Fairphone3

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#1037325: Bug on Debian 11 Bookworm - Installation-reports - EFI partition installation

[pham...@bluewin.ch]

Package: Installation-reports - EFI partition installation
Severity: Hight

Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with 
Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI 
partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI 
partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of 
the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost 
full, I have no possibility of installing other OSes ;-( This 100 MB partition 
being ridiculously small and not expandable, it does not also cannot benefit 
from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe

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#1037323: [FR] Add documentation about bug report metadata

[Ihor Radchenko]

X-Debbugs-CC: Eli Zaretskii , Michael Albinus 

Package: bugs.debian.org

Hello,

This bug report is originated from a discussion in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61490

The web page displays the following metadata about the bug report:

GNU bug report logs - #61490
[PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵
Previous Next
Package: emacs;
Reported by: Konstantin Kharlamov  yandex.ru>
Date: Mon, 13 Feb 2023 20:01:02 UTC
Severity: normal
Tags: patch
Merged with 61489
Done: Eli Zaretskii  gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 61490 in the body.
You can then email your comments to 61490 AT debbugs.gnu.org in the normal 
way.
Toggle the display of automated, internal messages from the tracker.
View this report as an mbox folder, status mbox, maintainer mbox

However, The meaning of 

Merged with 61489
Done: Eli Zaretskii  gnu.org>
Bug is archived. No further changes may be made.

is rather specific to debbugs and may need to be clarified for new
users.

In particular, it is not very clear if the bug is "Done", archived, or
merged - three different states in popular forges.

Now, after some input from more experienced users, I do know that
"merged" implies that several bugs share their state. But it is not
obvious at all without reading the documentation.

Would it be possible to add a link to documentation explaining the bug
status workflow somewhere near the bug summary web page?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Bug#1033100: Please update gnome-shell-extension-dashtodock to 82

[Amr Ibrahim]

Hello,

Please update gnome-shell-extension-dashtodock to 82. It's compatible with both
gnome-shell 43 and 44.

Best,
Amr

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

Bug#1037319: nomad ftbfs with newer golang-github-hashicorp-yamux-dev in experimental

[Pirate Praveen]

Control: severity -1 serious

On Sun, 11 Jun 2023 15:33:56 +0530 Pirate Praveen 
 wrote:

> I'd like to upload this version to unstable soon. Though this package
> seems to not in a good shape otherwise, not in testing and last 
upload

> in 2021-07-10.
>
Since all other reverse dependencies are working, this is now uploaded 
to unstable.

Bug#1037321: yaru-theme-icon: Update to 23.04.4

[Amr Ibrahim]

Package: yaru-theme-icon
Version: 22.10.3-1
Severity: normal

Dear Maintainer,

Please update yaru-theme to 23.04.4.

Best,
Amr


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#1037268: kwin-x11: resource leak: the number of threads increases over time, boundlessly

[Julien Muchembled]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=470898

I added more information upstream.

Le 10/06/2023 à 20:22, Nicholas D Steeves a écrit :

I could find that such leak happens when viewing videos fullscreen e.g. with 
mpv. Can anyone reproduce it ? More precisely:
1. start mpv without --fs -> thread count does not change
2. switch to fullscreen -> usually -2 threads
3. leaves fullscreen -> usually +17 threads
4. exit mpv -> thread count does not change


I was able to reproduce (with mpv 0.35.1-4), but going fullscreen didn't
increase the kwin thread count on my system; however, exiting fullscreen
consistently increased kwin's thread count by exactly two threads each
time mpv leaves fullscreen.


That's actually what I wrote.


The good news is that one doesn't need to restart KDE.  Try this:

   kwin --replace&


Oh thanks!

But I finally decided to switch to Wayland, and now new issues :(


Version 4:5.27.2-2 was affected too. I previously had 4:5.24.4-1 and I'm almost 
sure it had no leak.


That's not a terrible range to bisect, if it comes to that.


Really? I first checked my setup by successfully building kwin 4:5.27.5-3 and 
then tried 4:5.26.5-1 from from snapshot.debian.org:
- without downgrading any build-depends (and without forcing -d), compilation 
error;
- the executable inside the binary package depends on libraries that aren't 
there anymore.
I gave up.


- I use mpv from deb-multimedia.


For reference, please note that bugs must be reproducible with Debian
alone, otherwise they may be marked invalid.


Sure.


- mpv conf: vo = gpu


Actually, there's also a leak with --vo=x11

Julien

Bug#1037320: xpenguins: Messes the background with XFCE

[Nicolas Patrois]

Package: xpenguins
Version: 2.2-11
Severity: important
Tags: upstream

Dear Maintainer,

xpenguins messes XFCE’s background: the moving sprites are not deleted, they
remain shown after having moved, even when xpenguins is stopped.
Changing the background solves the issue.

Yours,
n.


-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xpenguins depends on:
ii  libc6 2.36-9
ii  libx11-6  2:1.8.4-2
ii  libxext6  2:1.3.4-1+b1
ii  libxpm4   1:3.5.12-1.1

xpenguins recommends no packages.

xpenguins suggests no packages.

-- no debconf information

Bug#1020495: Patch to build network-manager-strongswan against GTK 4, too

[Harald Dunkel]

Hi folks,

I have to appologize for not checking my bug reports. There is no
excuse for that. I am very sorry.

I have applied Moritz' patch to the source repository on Salsa and
verified the GUI using Gnome on Bookworm. The error message is
gone now.

@Ian, if you have some spare minutes, would you mind to upload the
fixed version 1.6.0-2, if it looks OK to you? There are no source
code changes, just a modified configure command line and some
additional dependencies. Janitor made changes to the debian directory
on Salsa as well. Included.


Thank you very much

Harri

Bug#1037318: ben: Quiet mode does not suppress read_global_config output

[Bas Couwenberg]

Source: ben
Version: 0.10.1
Severity: normal

Dear Maintainer,

The -q/--quiet option does not suppress the read_global_config output:

 $ ben tracker -q --global-conf config/global.conf
 read_global_config config/global.conf

Quite mode should suppress this output too.

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams

[Daniel Gröber]

Hi Simon,

On Sun, Jun 11, 2023 at 10:58:12AM +0900, Simon Richter wrote:
> > We need this to enable nextpnr support for Gowin FPGAs in Debian. I'm
> > intending to maintain this within the Debian Electronics Team like the
> > similar fpga-icestorm package.
> 
> I'd be interested in sponsoring nextpnr related packages.

Excellent.

The package is up on mentors and the git repo is in the electronics-team salsa 
team:

https://mentors.debian.net/package/apycula/
https://salsa.debian.org/electronics-team/apycula

have a look.

There is one thing with this package I'm not quite sure about. The Apicula
project builds the "chipdb" bitstream structure information automatically
using the (proprietary) vendor toolchain with a fuzzing based approach. The
output of this is then published as the apycula pypi package (what I'm
packaging here) which embeds this information in (binary) pickel files.

I'm not sure what the DFSG implications of this are. Is it acceptable to
use the pypi package as the starting point?

Thanks,
--Daniel

Bug#1037317: RFS: libfilezilla/0.43.0-1 -- build high-performing platform-independent programs (runtime lib)

[Philip Wyett]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libfilezilla":

 * Package name : libfilezilla
   Version  : 0.43.0-1
   Upstream contact : Tim Kosse 
 * URL  : https://lib.filezilla-project.org/
 * License  : GPL-2+
 * Vcs  : https://salsa.debian.org/debian/libfilezilla
   Section  : libs

The source builds the following binary packages:

  libfilezilla-dev - build high-performing platform-independent programs 
(development)
  libfilezilla-common - build high-performing platform-independent programs 
(translations)
  libfilezilla39 - build high-performing platform-independent programs (runtime 
lib)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libfilezilla/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/libf/libfilezilla/libfilezilla_0.43.0-1.dsc

Changes since the last upload:

 libfilezilla (0.43.0-1) unstable; urgency=medium
 .
   * New upstream version 0.43.0
   * Soname bump rename package to libfilezilla39

Regards

Phil

-- 
*** Playing the game for the games own sake. ***


Associations:

* Debian Maintainer (DM)
* Fedora/EPEL Maintainer.
* Contributor member of the AlmaLinux foundation.

WWW: https://kathenas.org

Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg

Twitter: @kathenasorg

Instagram: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


signature.asc
Description: This is a digitally signed message part

Bug#1037289: reportbug: EMAIL environment variable does not work

[Stephane Bortzmeyer]

On Sun, Jun 11, 2023 at 01:44:57AM -0400,
 Sandro Tosi  wrote 
 a message of 31 lines which said:

> your reportbug configuration file contains the address
> steph...@sources.org, which reportbug diligently uses. If you want to
> have use a different email address, either remove that config line or
> update it.
> 
> Working as intended, closing.

It does not seem that the man page explains that --email on the
command-line overrides ~/.reportbugrc but environment variables do
not.

May be a word about these priorities, somewhere?

Bug#1037316: www.debian.org: Download links on www.debian.org after release = no iso images, only BT

[Andrew M.A. Cater]

Package: www.debian.org
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Following Bookworm release and new layout: download links missing on 
www.debian.org for live CDs and some other images. Only BT links are there.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Followed download link on front page

   * What was the outcome of this action?

Redirect to appropriate page but links missing.

   * What outcome did you expect instead?

Download links to full CD/DVD/debian-live DVD images

Bug#1037315: linux-image-6.1.0-9-amd64 LUKS encryption for / doesn't work

[Marco Moock]

Package: src:linux
Version: 6.1.27-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

Hello!
If I try to boot linux-image-6.1.0-9-amd64, the encryption of my LUKS container 
doesn't work. I don't even get the password prompt.
It tries to run /scripts/local-block many times, but fails to find the / 
partition /because it is still encrypted).
Older kernels work fine.


m@ryz:~$ dpkg -l |grep initram
ii  cryptsetup-initramfs 2:2.6.1-4  
  all  disk encryption support - initramfs integration
ii  initramfs-tools  0.142  
  all  generic modular initramfs generator (automation)
ii  initramfs-tools-core 0.142  
  all  generic modular initramfs generator (core tools)
ii  libklibc:amd64   2.0.12-1   
  amd64minimal libc subset for use with initramfs
m@ryz:~$ 

m@ryz:~$ dpkg -l |grep grub
ii  grub-common  2.06-13
  amd64GRand Unified Bootloader (common files)
ii  grub-efi-amd64   2.06-13
  amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii  grub-efi-amd64-bin   2.06-13
  amd64GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii  grub-efi-amd64-signed1+2.06+13  
  amd64GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian)
ii  grub2-common 2.06-13
  amd64GRand Unified Bootloader (common files for version 2)
m@ryz:~$ 

*** End of the template - remove these template lines ***


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: P1.60
board_vendor: ASRock
board_name: J4125M
board_version: 

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Gemini Lake Host Bridge 
[8086:31f0] (rev 06)
DeviceName: Onboard - Other
Subsystem: ASRock Incorporation Gemini Lake Host Bridge [1849:]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:02.0 VGA compatible controller [0300]: Intel Corporation GeminiLake [UHD 
Graphics 600] [8086:3185] (rev 06) (prog-if 00 [VGA controller])
DeviceName: Onboard - Video
Subsystem: ASRock Incorporation GeminiLake [UHD Graphics 600] 
[1849:2212]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:0e.0 Audio device [0403]: Intel Corporation Celeron/Pentium Silver Processor 
High Definition Audio [8086:3198] (rev 06)
DeviceName: Onboard - Sound
Subsystem: ASRock Incorporation Celeron/Pentium Silver Processor High 
Definition Audio [1849:d887]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci_intel_apl

00:0f.0 Communication controller [0780]: Intel Corporation Celeron/Pentium 
Silver Processor Trusted Execution Engine Interface [8086:319a] (rev 06)
DeviceName: Onboard - Other
Subsystem: ASRock Incorporation Celeron/Pentium Silver Processor 
Trusted Execution Engine Interface [1849:319a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:12.0 SATA controller [0106]: Intel Corporation Celeron/Pentium Silver 
Processor SATA Controller [8086:31e3] (rev 06) (prog-if 01 [AHCI 1.0])
DeviceName: Onboard - SATA
Subsystem: ASRock Incorporation Celeron/Pentium Silver Processor SATA 
Controller [1849:31e3]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci

Bug#1037314: geary: you can't read emails using orca

[jordan]

Package: geary
Version: 43.0-1+b1
Severity: important
X-Debbugs-Cc: jordanlives...@gmail.com

Dear Maintainer,
it is impossible for visually impaired users to use this package with orca as 
it doesn't read emails when you use the arrow keys
*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
I tried to read emails by scrolling with the down arrow keys, when tutorial and 
child posission messeges are turned on in orca, orca correctly states the 
number and how many items there are, for instance, 3 of 19 when you scroll to 
email number 3 in a list of 19 emails
*** End of the template - remove these template lines ***


-- 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/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 geary depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gnome-keyring42.1-1+b2
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libenchant-2-2   2.3.3-2
ii  libfolks26   0.15.5-2+b1
ii  libgck-1-0   3.41.1-1+b1
ii  libgcr-base-3-1  3.41.1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgee-0.8-2 0.20.6-1
ii  libglib2.0-0 2.74.6-2
ii  libgmime-3.0-0   3.2.13+dfsg-2
ii  libgoa-1.0-0b3.46.0-1
ii  libgsound0   1.0.3-2
ii  libgspell-1-21.12.0-1+b2
ii  libgtk-3-0   3.24.37-2
ii  libhandy-1-0 1.8.1-1
ii  libicu72 72.1-3
ii  libjavascriptcoregtk-4.1-0   2.40.1-1
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmessaging-menu0   22.9.0-1+b1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpeas-1.0-01.34.0-1+b1
ii  libsecret-1-00.20.5-3
ii  libsoup-3.0-03.2.2-2
ii  libsqlite3-0 3.40.1-2
ii  libstemmer0d 2.2.0-2
ii  libunwind8   1.6.2-3
ii  libwebkit2gtk-4.1-0  2.40.1-1
ii  libxml2  2.9.14+dfsg-1.2
ii  libytnef02.0-1+b1

geary recommends no packages.

geary suggests no packages.

-- no debconf information

Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed

[Tim Small]

This took a while to track down - sorry for the delay.

The machine which was being upgraded had a non-functional shim in place 
instead of rpm.  This had been done to satisfy a hardware-vendor 
provided firmware upgrade, which would not work unless an rpm executable 
was found on the system (despite the fact that the firmware upgrade did 
not use rpm).


dkms preferentially uses rpm (even on Debian) to try and determine the 
architecture of the running system (instead of other methods such as 
`uname -m` or `dpkg --print-architecture`).


dkms uses the architecture which it has determined to store compiled 
modules at /var/lib/dkms/$module/$version/$kernelver/$arch/modules/


This use of a non-functional rpm resulted in dkms setting its internal 
architecture to the empty string.  This made dkms work correctly whilst 
installing modules (storing the resulting modules without the $arch path 
componenent) e.g. to 
/var/lib/dkms/ddcci/0.3.3/5.10.0-14-amd64/module/ddcci.ko  and also 
detect the presence of already installed modules, but also resulted in 
it silently failing when asked to remove modules.


If this is considered a bug, then it would seem reasonable for dkms to 
treat it's internal architecture variable being set to the empty string 
to be an error condition, and to exit and/or to fall back to using other 
methods of determining the architecture (which it does on Debian systems 
which don't have an rpm binary installed).

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