Bug#1057071: bookworm-pu: package rust-sd/0.7.6-1+deb12u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: rust...@packages.debian.org

[ Reason ]
squeeze had a sd binary package built from (unrelated) src:sd at
version 0.74-1 which is higher than the 0.7.6-1 currently in bookworm
from src:rust-sd, violating version ordering contraints.
0.80 is a made up version higher than any src:sd version ever in the
archive and lower than src:rust-sd 1.0 in sid.

[ Impact ]
Upgrade failures in CI.

[ Tests ]
Local piuparts tests of (hopefully) all affected upgrade paths.

[ Risks ]
Low, the package has no rdepends that could be affectd by the changed
version number.

[ Checklist ]
  [*] *all* changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in (old)stable
  [*] the issue is verified as fixed in unstable

[ Changes ]
Add the '0.80.really.' prefix to the binary package, needs pkg-info.mk.

$ debdiff sd_0.7.6-1+b3_amd64.deb sd_0.80.really.0.7.6-1+deb12u1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/share/doc/sd/changelog.Debian.amd64.gz

Control files: lines which differ (wdiff format)

Installed-Size: [-1919-] {+1918+}
Source: rust-sd [-(0.7.6-1)-] {+(0.7.6-1+deb12u1)+}
Version: [-0.7.6-1+b3-] {+0.80.really.0.7.6-1+deb12u1+}
X-Cargo-Built-Using: rust-aho-corasick (= 0.7.19-1), rust-ansi-term (= 
0.12.1-1), rust-atty (= 0.2.14-2), rust-bitflags (= [-1.3.2-2),-] {+1.3.2-3),+} 
rust-cfg-if (= 1.0.0-1), rust-clap-2 (= 2.34.0-3), rust-crossbeam-channel (= 
0.5.6-1), rust-crossbeam-deque (= 0.8.1-1), rust-crossbeam-epoch (= 0.9.13-1), 
rust-crossbeam-utils (= 0.8.12-1), rust-either (= 1.6.1-1), rust-fastrand (= 
1.8.0-1), rust-lazy-static (= 1.4.0-2), rust-libc (= 0.2.139-1), rust-memchr (= 
2.5.0-1), rust-memmap (= 0.7.0-1), rust-memoffset (= 0.6.5-1), rust-num-cpus (= 
1.14.0-1), rust-rayon-core (= 1.10.1-1), rust-rayon (= 1.6.1-1), rust-regex (= 
[-1.7.0-1),-] {+1.7.1-1),+} rust-regex-syntax (= 0.6.27-1), rust-remove-dir-all 
(= 0.7.0-1), rust-scopeguard (= 1.1.0-1), rust-smawk (= 0.3.1-2), rust-strsim 
(= 0.10.0-1), rust-structopt (= 0.3.26-2), rust-tempfile (= 3.3.0-1), 
rust-textwrap (= 0.16.0-2), rust-thiserror (= [-1.0.37-1),-] {+1.0.38-1),+} 
rust-unescape (= 0.1.0-1), rust-unicode-linebreak (= 0.1.4-1), 
rust-unicode-width (= 0.1.10-1), rust-vec-map (= 0.8.1-2), rustc (= 
1.63.0+dfsg1-2)

[ Other info ]
n/a

Andreas
diff -Nru rust-sd-0.7.6/debian/changelog rust-sd-0.7.6/debian/changelog
--- rust-sd-0.7.6/debian/changelog  2022-10-09 03:54:37.0 +0200
+++ rust-sd-0.7.6/debian/changelog  2023-11-28 22:27:45.0 +0100
@@ -1,3 +1,12 @@
+rust-sd (0.7.6-1+deb12u1) bookworm; urgency=medium
+
+  * Non-maintainer upload.
+  * Prefix the version of the binary package with '0.80.really.' to sort
+between 0.74-1 in squeeze (from unrelated src:sd) and 1.0.0-1 in sid.
+(Closes: #1037192)
+
+ -- Andreas Beckmann   Tue, 28 Nov 2023 22:27:45 +0100
+
 rust-sd (0.7.6-1) unstable; urgency=medium
 
   * Package sd 0.7.6 from crates.io using debcargo 2.5.0
diff -Nru rust-sd-0.7.6/debian/rules rust-sd-0.7.6/debian/rules
--- rust-sd-0.7.6/debian/rules  2022-10-09 03:54:37.0 +0200
+++ rust-sd-0.7.6/debian/rules  2023-11-28 22:27:45.0 +0100
@@ -1,7 +1,13 @@
 #!/usr/bin/make -f
+
+include /usr/share/dpkg/pkg-info.mk
+
 %:
dh $@ --buildsystem cargo
 
 override_dh_installman:
cp $$(find . -name sd.1 | grep release) debian/sd.1
dh_installman -O--buildsystem=cargo
+
+override_dh_gencontrol:
+   dh_gencontrol -- -v0.80.really.$(DEB_VERSION)

Bug#756017: Partial packaging

[Andreas Tille]

Hi,

Am Tue, Sep 08, 2015 at 10:25:11PM -0700 schrieb Diane Trout:
> I have a packaging tree that I'm using at:
> https://github.com/detrout/python-bokeh
> 
> It can't be released to Debian until we find a solution for building BokehJS. 
> (And that it also needs a jquery 2.1.1).

It seems there is some common interest so packaging bokeh inside Debian
Python Team might make sense.  I've independently from this RFP (which
I was not aware about) createt a repository

   https://salsa.debian.org/python-team/packages/python-bokeh

and merged+updated the packaging code from Diane above.

As you can see in the build log[1] there is a failurein creating
bokeh.js which becomes obvious if you run the command in setup.py
manually:


$ node make build  
node:internal/modules/cjs/loader:1042
  throw err;
  ^

Error: Cannot find module '/build/python-bokeh-3.3.1/make'
at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
at Module._load (node:internal/modules/cjs/loader:885:27)
at Function.executeUserEntryPoint [as runMain] 
(node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.13.0


This is due to the missing JS packages[2] mentioned here in this bug
log.

While bokeh would be in fact very helpful for several interesting
scientific Python3 packages I personally do not have the power to dive
into JS packaging.

Kind regards
Andreas.


[1] https://salsa.debian.org/python-team/packages/python-bokeh/-/jobs/4978289
[2] https://wiki.debian.org/Javascript/Nodejs/Tasks/bokehjs

-- 
http://fam-tille.de

Bug#1057070: bookworm-pu: package adequate/0.15.9~deb12u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
This is a rebuild of the package from sid to fix the autopkgtests on
!amd64. The symbol-size-mismatch issue can only happen on amd64,
therefore it cannot be reproduced elsewhere. Skip the specific test on
!amd64 (in a generic way).

[ Impact ]
Only failing autopkgtests.

[ Tests ]
autopkgtests in sid passed.

[ Risks ]
Low, only autopkgtests affected.

[ Checklist ]
  [*] *all* changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in (old)stable
  [*] the issue is verified as fixed in unstable

[ Changes ]
Fix suppression of some perl warnings.
Add support for skipping the build of some test packages.
Skip generating the symbol-size-mismatch test package if the symbol to
be tested has a size of 0.

 adequate   |  3 ++-
 debian/changelog   | 27 +++
 tests/testpkg/debian/rules |  8 
 3 files changed, 37 insertions(+), 1 deletion(-)

[ Other info ]
n/a

Andreas
diff --git a/adequate b/adequate
index 0267a0e..dee5442 100755
--- a/adequate
+++ b/adequate
@@ -25,7 +25,8 @@ use warnings;
 
 use v5.14;
 no feature 'unicode_strings';
-no if $] >= 5.018, warnings => 'experimental::smartmatch';
+no if $] >= 5.017011, warnings => 'experimental::smartmatch';
+no if $] >= 5.037010, warnings => 'deprecated::smartmatch';
 
 use Attribute::Handlers;
 use Cwd;
diff --git a/debian/changelog b/debian/changelog
index f049be2..09eb42b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,30 @@
+adequate (0.15.9~deb12u1) bookworm; urgency=medium
+
+  * QA upload.
+  * Rebuild for bookworm.
+
+ -- Andreas Beckmann   Wed, 29 Nov 2023 07:29:20 +0100
+
+adequate (0.15.9) unstable; urgency=medium
+
+  * QA upload.
+  * Skip symbol-size-mismatch test on architectures where array symbols don't
+include a specific length.  (Closes: #1050066)
+
+ -- Andreas Beckmann   Thu, 23 Nov 2023 10:06:17 +0100
+
+adequate (0.15.8) unstable; urgency=medium
+
+  * QA upload.
+  * Disable deprecation warnings about smartmatch, given, when in Perl
+5.38.
+This is only a band aid but it buys us time before the feature will be
+removed in perl 5.42 in roughly 2 years.
+Also fix version comparison for smartmatch being experimental warnings.
+(Closes: #1043228)
+
+ -- gregor herrmann   Tue, 08 Aug 2023 18:06:34 +0200
+
 adequate (0.15.7) unstable; urgency=medium
 
   * QA upload.
diff --git a/tests/testpkg/debian/rules b/tests/testpkg/debian/rules
index f2ad455..f21ebd2 100755
--- a/tests/testpkg/debian/rules
+++ b/tests/testpkg/debian/rules
@@ -35,6 +35,8 @@ override_dh_auto_install:
ln -sf lib$(at)-symsize.so.0 $(tmp)/lib$(at)-symsize.so
$(CC) symsize.c -L$(tmp) -o $(tmp)/$(at)-symsize -l$(at)-symsize
$(CC) -shared -Wl,--soname=lib$(at)-symsize.so.0 
-DADEQUATE_SYMBOL_SIZE=42 lib.c -o $(tmp)/lib$(at)-symsize.so.0
+   readelf --wide --symbols $(tmp)/$(at)-symsize | grep 
this_symbol_size_varies
+   test "$$(readelf --wide --symbols $(tmp)/$(at)-symsize | grep 
this_symbol_size_varies | head -n 1 | awk '{print $$3}')" != "0" || touch 
$(tmp)/skip-symbol-size-mismatch
# undefined-symbol
$(CC) -shared -Wl,--soname=lib$(at)-versioning.so.0 lib.c -o 
$(tmp)/lib$(at)-versioning.so.0
ln -sf lib$(at)-versioning.so.0 $(tmp)/lib$(at)-versioning.so
@@ -60,6 +62,12 @@ override_dh_strip:
 # we build binaries with missing symbols
 override_dh_shlibdeps:
 
+override_dh_gencontrol:
+   dh_gencontrol $(patsubst $(tmp)/skip-%,-N adequate-testpkg-%,$(wildcard 
$(tmp)/skip-*))
+
+override_dh_builddeb:
+   dh_builddeb $(patsubst $(tmp)/skip-%,-N adequate-testpkg-%,$(wildcard 
$(tmp)/skip-*))
+
 execute_after_dh_builddeb:
rm 
debian/adequate-testpkg-obsolete-conffile/etc/adequate/test-obsolete-conffile
sed -i -e '/test-obsolete/d' 
debian/adequate-testpkg-obsolete-conffile/DEBIAN/conffiles

Bug#1053681: bookworm-pu: package systemd/252.18-1~deb12u1

[Adam D. Barratt]

On Mon, 2023-11-13 at 21:44 +, Luca Boccassi wrote:
> It was noted that the diffstat is very large - that's because we now
> update hwdb.d in point releases, so it's 99.% new hardware
> identifiers being added. I've regenerated the debdiff to exclude
> files
> in the hwdb.d directory, so that it's easier to read.
> 

Thanks for the filtered diff.

While it does make the overall diff more tractable, it's not always
that simple (as an outsider to the systemd development process at
least) to identify what the actual changes are, in amongst the
documentation and test suite updates, and reformatting, and whether
they make sense for a Debian stable release.

Thankfully
https://github.com/systemd/systemd-stable/compare/v252.17...v252.19
isn't /too/ large.

Regards,

Adam

Bug#1057069: bookworm-pu: package midge/0.2.41+dfsg-1~deb12u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
This is a rebuild of the package from sid to remove some likely not
dfsg-free files.

[ Impact ]
Some possibly not dfsg-free files are installed.

[ Tests ]
none

[ Risks ]
Low, the removed files were only shipped as examples.

[ Checklist ]
  [*] *all* changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in (old)stable
  [*] the issue is verified as fixed in unstable

[ Changes ]
Modernized d/copyright in order to use files-Excluded for repacking.

 debian/changelog|  17 -
 debian/control  |   2 ++
 debian/copyright|  38 
+++---
 debian/gbp.conf |   2 ++
 debian/rules|   5 +
 debian/watch|   2 +-
 examples/covers/bobby_brown.mg  | 141 
-
 examples/covers/dont_fear_the_reaper.mg |  46 
--
 examples/covers/motorhead.mg|  60 

 examples/covers/one_drop.mg |  71 
---
 examples/covers/paranoid.mg |  38 
--
 examples/covers/stir_it_up.mg   | 105 
-
 examples/covers/too_much_to_dream.mg| 207 
---
 examples/covers/wieh.mg |  82 
--
 examples/covers/wish_you_were_here.mg   |  78 
--
 15 files changed, 49 insertions(+), 845 deletions(-)

$ debdiff midge_0.2.41-4_all.deb midge_0.2.41+dfsg-1~deb12u1_all.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/share/doc/midge/examples/covers/bobby_brown.mg
-rw-r--r--  root/root   
/usr/share/doc/midge/examples/covers/dont_fear_the_reaper.mg
-rw-r--r--  root/root   /usr/share/doc/midge/examples/covers/motorhead.mg
-rw-r--r--  root/root   /usr/share/doc/midge/examples/covers/one_drop.mg
-rw-r--r--  root/root   /usr/share/doc/midge/examples/covers/paranoid.mg
-rw-r--r--  root/root   /usr/share/doc/midge/examples/covers/stir_it_up.mg
-rw-r--r--  root/root   
/usr/share/doc/midge/examples/covers/too_much_to_dream.mg
-rw-r--r--  root/root   /usr/share/doc/midge/examples/covers/wieh.mg
-rw-r--r--  root/root   
/usr/share/doc/midge/examples/covers/wish_you_were_here.mg

Control files: lines which differ (wdiff format)

Installed-Size: [-356-] {+339+}
Version: [-0.2.41-4-] {+0.2.41+dfsg-1~deb12u1+}

[ Other info ]
n/a

Andreas
diff --git a/debian/changelog b/debian/changelog
index b1294a4..6023474 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+midge (0.2.41+dfsg-1~deb12u1) bookworm; urgency=medium
+
+  * QA upload.
+  * Rebuild for bookworm.
+
+ -- Andreas Beckmann   Wed, 29 Nov 2023 07:07:30 +0100
+
+midge (0.2.41+dfsg-1) unstable; urgency=medium
+
+  * QA upload.
+  * Switch to copyright-format 1.0.
+  * Repack without examples/covers/*.  (Closes: #1056147)
+  * Import package history into GIT.
+
+ -- Andreas Beckmann   Wed, 22 Nov 2023 14:07:43 +0100
+
 midge (0.2.41-4) unstable; urgency=medium
 
   * QA upload.
@@ -79,4 +95,3 @@ midge (0.2.33-1) unstable; urgency=low
   * Initial release.
 
  -- David Riley   Sat, 24 Aug 2002 22:02:22 +0100
-
diff --git a/debian/control b/debian/control
index b891d40..1df44bd 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,8 @@ Maintainer: Debian QA Group 
 Build-Depends: debhelper (>= 10)
 Standards-Version: 3.9.8
 Homepage: http://www.undef.org.uk/code/midge
+Vcs-Browser: https://salsa.debian.org/debian/midge
+Vcs-Git: https://salsa.debian.org/debian/midge.git
 
 Package: midge
 Architecture: all
diff --git a/debian/copyright b/debian/copyright
index a2e2cfd..a5ebdcc 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,13 +1,29 @@
-This package was debianized by David Riley  on Wed 
Jan 23 10:34:27 GMT 2002
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Source: 

Bug#1049319: ssldump: Fails to build source after successful build

[Peter Wienemann]

Control: tags -1 + patch

See https://lists.debian.org/debian-security-tools/2023/11/msg1.html

Bug#1057068: ITP: rust-bounded-static -- ToBoundedStatic and IntoBoundedStatic traits

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-bounded-static
  Version : 0.7.0
  Upstream Contact: FujiApple 
* URL : https://github.com/fujiapple852/bounded-static
* License : Apache-2.0
  Programming Lang: Rust
  Description : ToBoundedStatic and IntoBoundedStatic traits

 The bounded-static crate defines the ToBoundedStatic
 and IntoBoundedStatic traits,
 the ToStatic macro and provides implementations for common types.
 This crate has zero-dependencies, is no_std friendly
 and forbids unsafe code.

This package is needed for rust-imap-codec (bug#1057065).
It will be maintained in the collaborative section of salsa, at
https://salsa.debian.org/debian/rust-bounded-static
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVmu5MACgkQLHwxRsGg
ASEa7g//SbnWe8bEjVMRt4b8IKNiU6bcgTrUVd9zeXajrOON3b5JKlZm1VOFfZXO
TiNFFsMI/zxWxGE4dIkKf+96XqLlwOGaLtNWd0Z6CpQpJq0PSzGnOHrHFus9tE/A
52KxS7SU+0n7ZXACM/zp+dpjRC+ajxhvZwWNHb+IDlW4XXBHf/gsDVm7MZkxdulW
GcRB7rqKntoS/Bbn3YY8VCsUjzpJXc95sq4au0xLy+tYHMaZqQfHPbP984kYdLZD
iQ2OOmQ2FyQu/OOFobN3j6f2h3V8d2LYN9ncbr7eKTOD7T0MwOqHHEffEeXWC22A
8AnQRPJidS8x0qMnkkxQI6zA3yPWWFAimSWPuZzzveWrgWxZYVU4bfGni5mr1Jnm
7FQbjA1RWW9xR7xeZoG1tOUVdYi94HSyvpgGw7x+TOsVEwZdK3lEaa0jizf0LvXe
qmeX2hLqXqo8EmAygqeMRJWd1XnkpgkKPNsNIrEjzKU4XzzbW899F1RbSqJiNT5y
UCY3qTezs+9dOhia3Q1vxgNuKPsDJZJyLoWhNa2Mw/KpXy59n1cR2CYFcI3as102
TtDB0C7acYpbMIm2fjzrMk1KFHvSspD3mC6UGel7O9AK62nxuSN6hEpcwWJdn3d/
4WjBpJlruTHRZkb13sni7HXWMfpmMOwj9OX9k9VfpCQ605Gv56k=
=viSa
-END PGP SIGNATURE-

Bug#1057066: ITP: rust-abnf-core -- nom-based parser for ABNF core rules

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-abnf-core
  Version : 0.6.0
  Upstream Contact: Damian Poddebniak 
* URL : https://github.com/duesee/imap-codec
* License : Apache-2.0 or Expat
  Programming Lang: Rust
  Description : nom-based parser for ABNF core rules

 The abnf-core crate is a parser for ABNF core rules
 based on nom 7.
 It is primarily a building block for the ABNF parsing crate,
 but should also be useful in itself.

This package is needed for rust-imap-codec (bug#1057065).
It will be maintained in the collaborative section of salsa, at
https://salsa.debian.org/debian/rust-abnf-core
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVmtVwACgkQLHwxRsGg
ASGS1A/8DG0E01SiEQDr74R2CR34gcFbMqZKoFdui76YC5XkfgF7/MtcLNbP8XqD
AbOgtb+eOW1Uqgj12qzmmdadiU+bTYsp7+bm3jcNLOt2ziDf4J30iew5kaNhU+WM
23HAkpulF9RKyeVb42sdkyjkcdGKbMKax61sIOrQUK+C1fBb6dkPHyGYJx4UlQb5
d7Po+iS1875vwR5iuXaCwUG515KT1VigFrzk70TYD1Xz4jE0QX6J//F7Q7YqqoeM
Q3fPKJ3vsmLqOy0aXqcqz/V3FSIyOxj6sUzSo8qMlMlBWBbU8InXy/gMKm9+FFMj
rWSC3iwRfwuNyxQOFQLgwoDxE9TAgfZbFq37Xq7mGMt3evdvDBm+S0JJ+E7KOgik
natMzCH2jpjkSVnx+lLNeOJVFbOYbSwg7Vy9en4lYu+bMYLNL0/0NpYSZc9SJBOy
hxfRpYxRLbfWZ72Ua47Ilqf3XSypWaADTpZ03cm6GDX2Fn89UKeZaB4FdRS+IXtV
yxxaOoage51dLQXT66tUrOszD0SH2mFDiq7naSiG+9XIkhLBmMiXDeGBe352MhIh
pPGxdeMjfvCEcNqo/W7ovuR4WVuLTBTJQw8gZUUQAHbB21u9l2ytPhz+S1VWEarU
VrhV7BOez2cN0+VweNUeFyoEFZzqlRKiWudUaaqLORmmg8NKJZg=
=bBMd
-END PGP SIGNATURE-

Bug#1057067: new upstream release (1.65)

[Antoine Beaupre]

Source: rclone
Severity: critical

Debian is somewhat lagging behind upstream. Unstable currently has
1.60.1 (2022-11-17, uploaded to unstable on 2022-12-13) while upstream
is at 1.65.0 (released 2022-11-26).

It looks like upstream does a release roughly every two months, is
there a plan to follow that cadence here or what's the plan for
following upstream?

Open to help? :)

I'm asking because there's a bunch of bugfixes and major changes,
since 1.60, particularly new providers, multi-threaded transfers,
several improvements to the S3 backend (like support for empty
directories), and so on...

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

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

-- no debconf information

Bug#1057057: debian-policy: Please make Checksums-Sha1 optional

[Guillem Jover]

Hi!

On Tue, 2023-11-28 at 14:57:10 -0800, Russ Allbery wrote:
> Dimitri John Ledkov  writes:
> > Dak currently requires Checksums-Sha1, but I am happy to facilitate in
> > patching dak to make Checksums-Sha1 optional if this bug report is
> > accepted.
> 
> The field is documented as mandatory precisely because DAK requires it,
> which makes it mandatory for Debian packages.  As soon as DAK doesn't
> require it, I'm happy to make it optional (and indeed it would arguably be
> a bug in Policy if it's optional in the archive but Policy claims it's
> mandatory).

I'd like to drop those from .changes and .dsc (among other things),
but demoting these which are currently marked as required to me implies
a major format version bump. And I don't recall ever demoting required
fields, only promoting fields from optional to required.

For .changes, I've got this among other cleanups that would be nice to
do to the format:

  https://wiki.debian.org/Teams/Dpkg/Spec/ChangesFormat2.0

but there did not seem to be much enthusiasm when I proposed this some
time ago:

  https://lists.debian.org/debian-devel/2016/04/msg00326.html

For .dsc, there's the problem that, very confusingly the Format is used
not for the file format, but for the source format, which I think was
a mistake at the time, but here we are, see the .dsc section at:

  https://wiki.debian.org/Teams/Dpkg/TimeTravelFixes

Thanks,
Guillem

Bug#1057065: ITP: rust-imap-types -- misuse-resistant data structures for IMAP

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-imap-types
  Version : 1.0.0
  Upstream Contact: Damian Poddebniak 
* URL : https://github.com/duesee/imap-codec
* License : Apache-2.0 or Expat
  Programming Lang: Rust
  Description : misuse-resistant data structures for IMAP

 The imap-types crate provides
 a complete set of well-designed, misuse-resistant types
 for the IMAP4rev1 protocol and various extensions.
 Notably, it does *not* provide parsers, nor serializers,
 but tries to become the "standard library" for IMAP in Rust
 that is useful for a broad range of crates.

This package is needed for meli (bug#1001084).
It will be maintained in the collaborative Debian section of salsa, at
https://salsa.debian.org/debian/rust-imap-codec
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVmr6IACgkQLHwxRsGg
ASF97A//RItyoOZSJWXdVCjyzvEfyEzueEh3WhvwtOuT0D95h5ffKbl3apSJf1nx
G3uKqiebn0k8cxkUeQQ33t1aTSGGr6jC7p3uXbpDHbUsN/sVzoEk5i6N2O0lv3dg
1TG5jUpW6DTudGKbrE0/UHkIkM9Zf9G70ge6a3Ov4i4Dch2lvitnpJ4Nz7wd3M9T
df2ixE+RreMzJPBMYJKSHDkzl9GDaPcTor5RTHbPnU3WesUyZw/sscGoA2iVQpsI
jCYuYJDXF8rDSoYYjjDn0nJBT+poq6Jw6wSiOjcbyTPqCNo+S4miHIazJzMzBiZ2
PpbzPyIZN2mMJOMXhgSCcyjoyrQZFWgDg2e9ag8kKOU5Y9I4OBj7gsakx/bzxeSw
UeD1wnj6yI/9kzmBkc8opXrwLtYOGyntXW3En8UwQUiMPWIPfuSAQpZL+Y60AmTu
h5TYh91ZMIDcRtmjqzwaigl6kyDZNL9J+5+lw4ZnEySUJvwPYoc6YsYole7Lexto
zCWvBbXbKdqbtAyKVFsvj3d+hBU967EwYC0xAhmqyNpxNHVvn8gb/ffuFe9qwrWk
hX7iAs8sU7YeLEQkP5lrQY55tNj3U/7yMJDd9ce/keueoR5kW/e30zPi9EhUWXHb
2e/1/NREk8wXejGsb7O3gS1H10gi5jAAGvjkpF6fLehAd2GS5f4=
=a5C7
-END PGP SIGNATURE-

Bug#1057064: apache2: link in default index.html should be HTTPS

[Chris Murray]

Package: apache2
Version: 2.4.57-2
Severity: minor
X-Debbugs-Cc: chris.f.mur...@hotmail.co.uk

Dear Maintainer,

When running the Hardenize (https://www.hardenize.com) tool against my web 
server, it picked up that on the default Apache2 web page (located at 
/var/www/html/index.html) has an insecure link. Upon further investigation, 
it's the "Document Roots" section, where it says "By default, Ubuntu does not 
allow access through the web browser to any file outside of those located in 
/var/www, public_html directories (when enabled) and /usr/share (for web 
applications)."; public_html is a link to the apache docs page for mod_userdir 
(https://httpd.apache.org/docs/2.4/mod/mod_userdir.html) but it's being serverd 
as a http:// link. IMO this should be updated to be https.

To reproduce

* Start with a base install of ubuntu server
* run the following commands:
sudo apt-get update; sudo apt-get dist-upgrade; sudo apt-get install apache2
* optionally set up SSL
* browse to http(s):///index.html
* hover over the link on public_html & observe it begins with http://

All the best,

Chris 8-)

-- Package-specific info:

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

Kernel: Linux 6.1.0-13-amd64 (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apache2 depends on:
ii  apache2-bin2.4.57-2
ii  apache2-data   2.4.57-2
ii  apache2-utils  2.4.57-2
ii  init-system-helpers1.65.2
ii  media-types10.0.0
ii  perl   5.36.0-7
ii  procps 2:4.0.2-3
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.2

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  w3m [www-browser]0.5.3+git20230121-2

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.2-3
ii  libaprutil1  1.6.3-1
ii  libaprutil1-dbd-sqlite3  1.6.3-1
ii  libaprutil1-ldap 1.6.3-1
ii  libbrotli1   1.0.9-2+b6
ii  libc62.36-9+deb12u3
ii  libcrypt11:4.4.33-2
ii  libcurl4 7.88.1-10+deb12u4
ii  libjansson4  2.14-2
ii  libldap-2.5-02.5.13+dfsg-5
ii  liblua5.3-0  5.3.6-2
ii  libnghttp2-141.52.0-1
ii  libpcre2-8-0 10.42-1
ii  libssl3  3.0.11-1~deb12u2
ii  libxml2  2.9.14+dfsg-1.3~deb12u1
ii  perl 5.36.0-7
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  w3m [www-browser]0.5.3+git20230121-2

Versions of packages apache2 is related to:
ii  apache2  2.4.57-2
ii  apache2-bin  2.4.57-2

-- Configuration Files:
/etc/apache2/conf-available/security.conf changed
/etc/apache2/mods-available/dir.conf changed
/etc/apache2/sites-available/000-default.conf changed
/etc/apache2/sites-available/000-default-ssl.conf changed

-- no debconf information

-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com

Bug#1057063: ITP: rust-strfmt -- rust library for formatting dynamic strings

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-strfmt
  Version : 0.2.4
  Upstream Contact: Garrett Berg 
* URL : https://github.com/vitiral/strfmt
* License : Expat
  Programming Lang: Rust
  Description : rust library for formatting dynamic strings

 strfmt is a rust library for formatting dynamic strings.
 It is a library is for rust developers
 who want to bring rust-like formatting to non-static strings.

This package is needed for recent releases for btm.
It will be maintained in the Debian section of salsa, at
https://salsa.debian.org/debian/rust-strfmt
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVmnuQACgkQLHwxRsGg
ASHvbw//cezjOWl7N/r18kJSC+zX+BwhpOOQZQFj6cUWDF12nbTK2trTlkgmnlRv
tvdDO6yH0v+CQOIBsrqvIvM9oifYTl8eFHsuAC7KEIWHJ4ri+H5pduCosclIHO+4
m53/6QS40TLemWB3rissmL4QO2Bv5U5BzgcULk0TJ6CnMy50YaP5WOfhaL5/oPcC
vLWHA9vfvgydQkTcXsUuqRXEzbLcowvLA6T+wg6knpudPn/D5In9xuvNmK1UCUN6
okpc5npyCbv89qpQywZQRNandB7U3+6ZJbHQH4bEEpAq8FD6QzUNK1vOun/jioqU
1zM/clDR6wbq2ikGkkRrRwxHjmzhAEviCWaOhnValta2f1IUh0zDNhtEUbDFd6B3
fNQAutAwMt24xSU8o/z9Nch3Yopp2skeq1JPhTFav1/ERZjdZavBRq7fXiHkrfDQ
ECRdTVv4QGXmN5byyxUvuANdkc1RrOKU7GMFpyjWdwObkb5t6Ny0Pi+VVgFeMYRb
C2fg9lf5xwuDWCwu3AYesb1bPBnIXlodWKRJrADSifVnNLoZh3fyDie1D4gbhmOD
U/hGuSkx6dqh2gp2wWfm5IP/fVC9KoGLCVFY8NZ+iuAq+mZA2IFc/aN0DPRwgEjJ
I2RzvE7yxwp5FKzPcCUUMIr92wcpeqBjllZ7GWfPw+HBqNIX6jY=
=wN7u
-END PGP SIGNATURE-

Bug#1057061: The service roundcube-cleandb should depend on mariadb.service

[Guilhem Moulin]

Control: tag -1 moreinfo

On Wed, 29 Nov 2023 at 01:14:27 +0100, Dmitry Katsubo via 
Pkg-roundcube-maintainers wrote:
> The service roundcube-cleandb should be run after MySQL/MariaDB is started:
>
> === file /lib/systemd/system/roundcube-cleandb.service ===
>
> [Unit]
> After=mariadb.service
>
> === end ===

I don't think it's that simple: MariaDB is only one of several supported
RDBMS, and the server might be on a different system.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#919441: ITP: pyshacl -- A pure Python packages which allows for the validation of RDF graphs against Shapes Constraint Language (SHACL) files.

[Jonas Smedegaard]

Hi Ashley, Kartik and others,

Quoting Jonas Smedegaard (2020-07-02 13:22:12)
> Ashley Sommer wrote:
> > Jonathan told us he is happy to also sponsor pyshacl but we can't 
> > really start looking at undertaking packaging pyshacl until the 
> > process for OWL-RL has finished.
> 
> FYI it is possible to prepare and release to NEW queue packages which 
> depend on other packages still pending in NEW queue.
> 
> ...but I am sure Jonathan can help with that, in case you want that 
> faster parallelizing approach.
> 
> Looking forward to having pyshacl in Debian,

What is the status of packaging pySHACL officially for Debian?

Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1007982: ITP: popsicle -- A Linux utility for flashing multiple USB devices in parallel

[Jonas Smedegaard]

Quoting Matthias Geiger:
> Update on the dependencies:
>
> blocked by https://gitlab.com/pwoolcoc/pwd/-/issues/2 for pwd 

Looks like instead of trying to get pwd into acceptable licensing shape,
it might be better to avoid it and instead patch to instead use pwd-grp,
judging from the "Alternatives to this library" section of that crate:
https://lib.rs/crates/pwd-grp#readme-alternatives-to-this-library


> and
>
> iso9660 which looks packageable with this MR:
> https://github.com/ids1024/iso9660-rs/pull/6

Seems the MR was adopted and part of release v0.1.1:
https://lib.rs/crates/iso9660/versions


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1055440: libsfml-dev: Requesting libsfml-dev be upgraded to the latest release v2.6.1

[James Cowgill]

Control: tags -1 pending

Hi Chris,

On 06/11/2023 06:36, Chris Thrasher wrote:
> My name is Chris Thrasher and I help maintain SFML. I'm requesting
> libsfml-dev be upgraded to the latest release of SFML, version 2.6.1.
> It was just released a few days ago and includes 5+ years worth of
> improvements to SFML since 2.5.1 was released in 2018.
I've uploaded 2.6.1 to experimental and should appear once it's approved
by the ftp-masters.

As the libraries were renamed, there needs to be a "library transition"
before it can enter unstable and the main release. How long that takes
depends on whether the other packages in Debian that depend on SFML need
changing or not. The is the current list. I haven't tried them with
2.6.1 yet.

dolphin-emu
extremetuxracer
libcsfml
marsshooter
python-sfml
seriousproton

Thanks,
James

Bug#699661: debian-keyring: please ship a removed-keys keyring

[Dimitri John Ledkov]

On Sat, 2 Feb 2013 23:51:42 -0500 Michael Gilbert  wrote:
> package: debian-keyring
> version: 2012.11.15
> severity: important
>
> Signature verification currently fails on source packages that were
> signed by keys that are no longer present in the active keyrings.
> This can easily lead to the incorrect conclusion that those packages
> are not to be trusted or possibly malicious.  Many packages tend to
> remain in the archive far longer than the key used to sign them, so I
> think it would make a lot of sense to ship the removed-keys to be ably
> to easily verify them into the indefinite future.

I wonder if instead the bug report is with dak, that it should strip
signatures from .dsc files (like it strips them from .changes) and
instead replace signature with the verified/trusted gpg output at the
time (good signature from $UID $KEID $HASH $Algo).

Such that .dsc fetched from the archive years later, is only verified
via archive key signature of a future time, rather than relying on the
.dsc signature to remain trusted.

It would also make published .dsc smaller.

Basically the same reasoning as to why .deb files are not signed directly.

Because one is supposed to have received an already authenticated and
verified .dsc after running `apt source`.

Regards,

Dimitri.

Bug#1057061: The service roundcube-cleandb should depend on mariadb.service

[Dmitry Katsubo]

Package: roundcube-core
Version: 1.6.3+dfsg-1~deb12u1

The service roundcube-cleandb should be run after MySQL/MariaDB is started:

=== file /lib/systemd/system/roundcube-cleandb.service ===

[Unit]
After=mariadb.service

=== end ===

otherwise the following error may occur during the startup:

2023-11-29 00:12:13.677906 systemd[1]: roundcube-cleandb.service: Main process 
exited, code=exited, status=1/FAILURE
2023-11-29 00:12:13.678149 cleandb.sh[1034]: ERROR: SQLSTATE[HY000] [2002] No 
such file or directory
2023-11-29 00:12:13.680342 cleandb.sh[1034]: ERROR: Failed to connect to 
database

-- 
With best regards,
Dmitry

Bug#1057060: isight-firmware-tools: Installs udev rule into /lib

[Chris Hofstaedtler]

Package: isight-firmware-tools
Version: 1.6-4
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package ships an udev rule in /lib/udev/rules.d. For the ongoing
UsrMerge effort [1], the /lib directory needs to become "empty", IOW no
package should install files there. Instead they should go into
/usr/lib.

Attached is an _untested_ patch to implement this for your package.
Please test and apply at your earliest convenience.

Please also read [1] first.

Thanks,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru isight-firmware-tools-1.6/debian/changelog 
isight-firmware-tools-1.6/debian/changelog
--- isight-firmware-tools-1.6/debian/changelog  2019-01-29 04:12:57.0 
+0100
+++ isight-firmware-tools-1.6/debian/changelog  2023-11-29 01:42:34.0 
+0100
@@ -1,3 +1,10 @@
+isight-firmware-tools (1.6-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev rules into /usr (Closes: #-1) 
+
+ -- Chris Hofstaedtler   Wed, 29 Nov 2023 01:42:34 +0100
+
 isight-firmware-tools (1.6-4) unstable; urgency=medium
 
   * Add Danish debconf templates translation. (Closes: #767486)
diff -Nru isight-firmware-tools-1.6/debian/dirs 
isight-firmware-tools-1.6/debian/dirs
--- isight-firmware-tools-1.6/debian/dirs   2019-01-29 04:12:57.0 
+0100
+++ isight-firmware-tools-1.6/debian/dirs   2023-11-29 01:42:34.0 
+0100
@@ -1,2 +1,2 @@
 usr/bin
-lib/udev/rules.d
+usr/lib/udev/rules.d
diff -Nru isight-firmware-tools-1.6/debian/rules 
isight-firmware-tools-1.6/debian/rules
--- isight-firmware-tools-1.6/debian/rules  2019-01-29 04:12:57.0 
+0100
+++ isight-firmware-tools-1.6/debian/rules  2023-11-29 01:42:34.0 
+0100
@@ -5,7 +5,7 @@
 
 install/isight-firmware-tools::
mv debian/isight-firmware-tools/etc/udev/rules.d/isight.rules \
-   debian/isight-firmware-tools/lib/udev/rules.d/80_isight.rules
+   
debian/isight-firmware-tools/usr/lib/udev/rules.d/80_isight.rules
 
rm -rf $(CURDIR)/debian/isight-firmware-tools/etc
 

Bug#1057059: rust-serde-with: please update to v3.4.0

[Jonas Smedegaard]

Source: rust-serde-with
Version: 3.3.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to at least v3.4.0.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVmhhwACgkQLHwxRsGg
ASHqgQ/+NNuWkyaVxYs1H53QXeuA3nUtgQs22zm+BjY0q/oFSku7lMNVZEmjtKfF
Cx6MtoIgnnXe5UXqUOt61i/bc4GpOJmRfBhGRbca5kDpy+WCSmM4P3Zg2t9W2C4S
XfyPxMTQXiTKP5+XVKT9qeORv/+e48J3jNGBUmeypdkTdE3ZHMovNk/YWryVRbJ/
ly15eEyss/OkhINBtLj47PDMtox7IcjtUAFTyzUoPJZI9iVBxgAk4tZ2mS1e6exF
2zKXjB+jhm9kfC/R3Osjl3kZj0Ps1ElZwRd9OGR7NkUNzjqHXrQRAijOTFDzv01O
Fz0pHiHhHHBbjcXRrLo5TaeEM+IQDSystzsW7hpEQuXZEsrQh2BwuuXhq9JBBRzv
0+g4quH2qSkr28+IpN681WBN1gu9UIaHrpXotAweRt5HW/zF3X7dUPXo9x9n1tYi
ywdbc32hEmxrZQ3d/I2BMOfZIwuCKKVRDrTKnsR0xBeARzIhUqKcJ6vmrty9fbVV
m6+vrrF/bID9964oobmtKeKhPA6lfTdZzWRa/2eZ13UoJU4F+tb0HnVLLHK7RiZr
oXvTqjnwrqyPq/mW2xv/WCoerk1bslsY9EbVhYU+BduimJj0hUEjS4KVaE5OPF8Q
W+GeE1zeRqOX+Cn7soDEVfJn28y1aOQCvZDJcrsJONggVcNNNM8=
=ymTa
-END PGP SIGNATURE-

Bug#1057057: debian-policy: Please make Checksums-Sha1 optional

[Dimitri John Ledkov]

Hi,

On Wed, 29 Nov 2023 at 00:05, Holger Levsen  wrote:
>
> hi,
>
> snapshot.d.o also uses sha1 sums, at least internally, but I'd not
> surprised if also for external verification.

At the moment I am trying to focus on contents of .dsc and .changes
only, not the InReleases Packages etc files.
Does snapshot.d.o peak inside .dsc and .changes files? Does it use
sha1 for "by-hash" like content addressing? My understanding was that
"by-hash" lookups use sha256 only (at least launchpad's implementation
had code for sha1 but it never was in production proper)

-- 
okurrr,

Dimitri

Bug#1057057: debian-policy: Please make Checksums-Sha1 optional

[Holger Levsen]

hi,

snapshot.d.o also uses sha1 sums, at least internally, but I'd not
surprised if also for external verification. 


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Reporter: You're the first person ever to win two Olympic tennis gold medals.
That's an extraordinary feat, isn't it?
Andy Murray: I think Venus and Serena have won about four each.


signature.asc
Description: PGP signature

Bug#979688: Simplifying the list of image files for arm64 sunxi boards

[harry88]

On 28/11/2023 18:56, Vagrant Cascadian wrote:
> [...]
> I had managed to successfully build a bootable image doing it "the old
> way" that worked on both pinebook (allwinner A64) and pinebook pro
> (rockchip rk3399) at "alternate offsets" that required no changes to the
> u-boot binaries... but that was with older versions. [...]

Hi Vagrant,

OK, that's interesting... do you recall at what offsets you placed the
different sunxi parts? This is not meant to hold up closing the bug, it's
just for my enlightenment, because my reading of the code is that on
sunxi the SPL and U-Boot proper have to be adjacent.

Thanks a lot,
Harold.

Bug#1010273: Confirmation and workaround

[Marco Steinacher]

Hi,

I can confirm this problem. I think the following is happening:

After updating mailman3-web, the static files in 
/usr/share/python3-django-postorius/static/ (and 
python3-django-hyperkitty, and maybe others) have an older date than the 
collected files in /var/lib/mailman3/web/static from the previous version.


Because of that, "./manage collectstatic" skips the files with "not 
modified", and is not updating the static files, even though the files 
have been updated (but have an older modified date).


To fix this, you can touch the static files in 
/usr/share/python3-django-postorius/static/ (to set a newer modification 
date) and then run "./manage collectstatic". Then the files will be 
updated, since collectstatic seems to compare the file modification 
dates and not the actual file contents.


I'm not sure how the Debian package installer should avoid this problem. 
Probably it should either make sure that the updated files have a newer 
date before running collectstatic or delete the old files before doing that.


Below you find some additional notes that I wrote down while 
investigating the situation. Maybe that is helpful.


Marco

--- Additional notes: ---

I noticed strange CSS problems after upgrading from buster to bullseye. 
With the information from this bug report, I found the following issue:


- /var/lib/mailman3/web/static is used, but seems to contain old 
versions (e.g. Bootstrap v3.3.5 at 
postorius/libs/bootstrap/css/bootstrap.min.css)


- /usr/share/python3-django-postorius/static/ seems to contain the 
correct version (e.g. Bootstrap v4.0.0) but is not used.


Further digging into the issue, I found that 
/usr/lib/python3/dist-packages/postorius/static is a soft-link to the 
correct location at /usr/share/python3-django-postorius/static/. So that 
seems to be right.


Hence, I suspect that "./manage.py collectstatic" for some reason does 
not update the static files. Running "./manage.py collectstatic -v 3" 
skips all files with "not modified":


--
www-data@mail:/usr/share/mailman3-web$ ./manage.py collectstatic -v 3

You have requested to collect static files at the destination
location as specified in your settings:

/var/lib/mailman3/web/static

This will overwrite existing files!
Are you sure you want to do this?

Type 'yes' to continue, or 'no' to cancel: yes

[...]
Skipping 'postorius/libs/bootstrap/css/bootstrap.min.css' (not modified)
[...]
--

Removing the static files at /var/lib/mailman3/web/static before running 
collectstatic solves the problem:


--
www-data@mail:/usr/share/mailman3-web$ ./manage.py collectstatic -v 3

You have requested to collect static files at the destination
location as specified in your settings:

/var/lib/mailman3/web/static

This will overwrite existing files!
Are you sure you want to do this?

Type 'yes' to continue, or 'no' to cancel: yes
[...]
Copying 
'/usr/lib/python3/dist-packages/postorius/static/postorius/libs/bootstrap/css/bootstrap.min.css'

[...]
--

Now Bootstrap has the correct version (v4.0.0 in this case) and the CSS 
issues are gone!


So the workaround is to delete the static files in 
/var/lib/mailman3/web/static before collecting them with "./manage.py 
collectstatic" or to touch the files in 
/usr/share/python3-django-postorius/static/ so they have a newer 
modification date.




--
OpenPGP Key ID: 0x62937F7F

Bug#860470: libccrtp: please make the build reproducible

[Vagrant Cascadian]

On 2017-04-17, Chris Lamb wrote:
> This is due to it capturing the buildpath in some automatically
> generated documentation. It appears safe to simply delete the manpages
> in question as they are a) private APIs and b) kinda terse/useless
> anyway.
...
> --- a/debian/rules2017-04-17 13:16:14.337050334 +0100
> --- b/debian/rules2017-04-17 13:38:53.662578698 +0100
> @@ -15,3 +15,7 @@
>  override_dh_clean:
>   rm -f doc/latex/* doc/html/* doc/man/man3/* doc/doxy
>   dh_clean
> +
> +override_dh_installman:
> + dh_installman
> + rm -rf debian/libccrtp-doc/usr/share/man/man2

It seems exactly which directory these files are placed in is
non-deterministic; updated patch attached.

For example, libccrtp-doc_2.0.9-2.3_all.deb currently in the archive
contains these files:

  
usr/share/man/man9/_build_libccrtp-eppWJD_libccrtp-2.0.9_src_ccrtp_.9_src_ccrtp_.3.gz
  usr/share/man/man9/_build_libccrtp-eppWJD_libccrtp-2.0.9_src_.9_src_.3.gz

I intend to NMU this package in the near future to fix this issue if I
do not hear otherwise.

live well,
  vagrant
From ffa35c9ca2ac9dcc0c78b7d604011a2faee25db0 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 28 Nov 2023 15:31:58 -0800
Subject: [PATCH] debian/rules: Remove low-content manpages with filenames
 based on build path. (Closes: #860470)

Some manpage names are generated based on the build path, e.g. the
package built in the directory /build/libccrtp-eppWJD/libccrtp-2.0.9
produces the manpage filename
"_build_libccrtp-eppWJD_libccrtp-2.0.9_src_.9_src_.3.gz".

These manpages have very little meaningful content, so remove them.
---
 debian/rules | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/debian/rules b/debian/rules
index 5b7fd06..4622347 100755
--- a/debian/rules
+++ b/debian/rules
@@ -15,3 +15,9 @@ override_dh_install:
 override_dh_clean:
 	rm -f doc/latex/* doc/html/* doc/man/man3/* doc/doxy
 	dh_clean
+
+override_dh_installman:
+	dh_installman
+	# Remove files with low content and filenames based on the build path.
+	# https://bugs.debian.org/860470
+	rm -vf debian/libccrtp-doc/usr/share/man/man*/_*
-- 
2.39.2



signature.asc
Description: PGP signature

Bug#784675: /usr/libexec/gvfs-udisks2-volume-monitor: gvfs-udisks2-vo[1270]: segfault at 0 ip 00007f91b039de7b sp 00007ffdc0000a20 error 4 in libc.so.6[7f91b0309000+155000] likely on CPU 0 (core 0, so

[gr]

Package: gvfs-daemons
Followup-For: Bug #784675
X-Debbugs-Cc: graziano@virgilio.it

Dear Maintainer,

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

   * What led up to the situation?

root@orpo:~# systemctl status udisks2.service
● udisks2.service - Disk Manager
 Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: 
enabled)
 Active: active (running) since Tue 2023-11-28 22:41:35 CET; 1h 14min ago
   Docs: man:udisks(8)
   Main PID: 761 (udisksd)
  Tasks: 6 (limit: 3479)
 Memory: 21.5M
CPU: 1.590s
 CGroup: /system.slice/udisks2.service
 └─761 /usr/libexec/udisks2/udisksd

nov 28 22:41:18 orpo systemd[1]: Starting udisks2.service - Disk Manager...
nov 28 22:41:20 orpo udisksd[761]: udisks daemon version 2.10.1 starting
nov 28 22:41:35 orpo systemd[1]: Started udisks2.service - Disk Manager.
nov 28 22:41:35 orpo udisksd[761]: Acquired the name org.freedesktop.UDisks2 on 
the system message bus
nov 28 22:42:54 orpo udisksd[761]: Error probing device: Error sending ATA 
command IDENTIFY DEVICE to '/dev/sdb': Unexpected >
   : 00 00 00 00  00 00 00 00  00 00 00 00  
00 00 00 00
   0010: 00 00 00 00  00 00 00 00  00 00 00 00  
00 00 00 00
(g-io-error-quark, 0)
nov 28 22:42:55 orpo udisksd[761]: Mounted /dev/sdb1 at /media/gr/Intenso_1979 
on behalf of uid 1000
lines 1-20/20 (END)




root@orpo:~# journalctl -fn
...
nov 28 19:36:41 orpo kernel: usb 7-4.3: new SuperSpeed USB device number 4 
using xhci_hcd
nov 28 19:36:41 orpo kernel: usb 7-4.3: New USB device found, idVendor=152d, 
idProduct=0579, bcdDevice= 1.00
nov 28 19:36:41 orpo kernel: usb 7-4.3: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
nov 28 19:36:41 orpo kernel: usb 7-4.3: Product: External USB 3.0
nov 28 19:36:41 orpo kernel: usb 7-4.3: Manufacturer: Intenso
nov 28 19:36:41 orpo kernel: usb 7-4.3: SerialNumber: 
nov 28 19:36:41 orpo mtp-probe[1267]: checking bus 7, device 4: 
"/sys/devices/pci:00/:00:1c.0/:03:00.0/usb7/7-4/7-4.3"
nov 28 19:36:41 orpo mtp-probe[1267]: bus: 7, device: 4 was not an MTP device
nov 28 19:36:41 orpo kernel: usbcore: registered new interface driver 
usb-storage
nov 28 19:36:41 orpo kernel: scsi host4: uas
nov 28 19:36:41 orpo kernel: usbcore: registered new interface driver uas
nov 28 19:36:41 orpo kernel: scsi 4:0:0:0: Direct-Access Intenso  External 
USB 3.0 1201 PQ: 0 ANSI: 6
nov 28 19:36:41 orpo kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] 3907029168 512-byte logical 
blocks: (2.00 TB/1.82 TiB)
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] 4096-byte physical blocks
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] Write Protect is off
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] Mode Sense: 53 00 00 08
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read 
cache: enabled, doesn't support DPO or FUA
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] Preferred minimum I/O size 4096 
bytes
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] Optimal transfer size 33553920 
bytes not a multiple of preferred minimum block size (4096 bytes)
nov 28 19:36:46 orpo kernel:  sdb: sdb1
nov 28 19:36:46 orpo kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
nov 28 19:36:46 orpo mtp-probe[1277]: checking bus 7, device 4: 
"/sys/devices/pci:00/:00:1c.0/:03:00.0/usb7/7-4/7-4.3"
nov 28 19:36:46 orpo mtp-probe[1277]: bus: 7, device: 4 was not an MTP device
nov 28 19:36:46 orpo udisksd[737]: Error probing device: Error sending ATA 
command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
   : 00 00 00 00  00 00 00 00  00 00 00 00  
00 00 00 00
   0010: 00 00 00 00  00 00 00 00  00 00 00 00  
00 00 00 00
(g-io-error-quark, 0)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action? DE Mate doesn't realize that a new 
volume was inserted.
   * What outcome did you expect instead? An icon of external usb hd on desktop.

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


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

Kernel: Linux 6.5.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 gvfs-daemons depends on:
ii  gvfs-common 1.52.1-1
ii  gvfs-libs   1.52.1-1
ii  libbluray2  1:1.3.4-1
ii  libc6   2.37-12
ii  libglib2.0-02.78.1-4
ii  

Bug#1057057: debian-policy: Please make Checksums-Sha1 optional

[Russ Allbery]

Dimitri John Ledkov  writes:

> Dak currently requires Checksums-Sha1, but I am happy to facilitate in
> patching dak to make Checksums-Sha1 optional if this bug report is
> accepted.

The field is documented as mandatory precisely because DAK requires it,
which makes it mandatory for Debian packages.  As soon as DAK doesn't
require it, I'm happy to make it optional (and indeed it would arguably be
a bug in Policy if it's optional in the archive but Policy claims it's
mandatory).

-- 
Russ Allbery (r...@debian.org)  

Bug#1057058: liquidsoap-doc: missing Breaks+Replaces: liquidsoap (<< 2.2.2)

[Andreas Beckmann]

Package: liquidsoap-doc
Version: 2.2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../liquidsoap-doc_2.2.2-1_all.deb ...
  Unpacking liquidsoap-doc (2.2.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liquidsoap-doc_2.2.2-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/liquidsoap/html/beets.html', which is 
also in package liquidsoap 2.1.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/liquidsoap-doc_2.2.2-1_all.deb


cheers,

Andreas


liquidsoap=2.1.3-2_liquidsoap-doc=2.2.2-1.log.gz
Description: application/gzip

Bug#1057044: xymon: ntpdate no longer supports the -p option

[Carsten Leonhardt]

Hi Axel,

>> If you prefer, I can also commit directly to salsa.
>
> Fine for me, thanks!

I just realized that I messed it up, I'll fix it (the change is in upstream
code...)

Regards

Carsten

Bug#985397: /usr/share/texlive/texmf-dist/tex/latex/tikzposter/tikzposter.cls: tikzposter.cls: licensed under non-existing version 2.0 of LPPL

[Preuße]

Control: forwarded -1 https://bitbucket.org/surmann/tikzposter/issues/44

On 17.03.2021 11:15, Braun Gábor wrote:


Package: texlive-pictures
Version: 2018.20190227-2
Severity: normal
File: /usr/share/texlive/texmf-dist/tex/latex/tikzposter/tikzposter.cls

Dear Maintainer,



Forwarded.

H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057057: debian-policy: Please make Checksums-Sha1 optional

[Dimitri John Ledkov]

Package: debian-policy
Version: 4.6.2.0
Severity: wishlist
Tags: patch

Dear Maintainer,

SHA1 is an obsolete checksum method. For example NIST recommends to
phase out all usage of SHA1 by 2030. Currently it is generated in .dsc
and .changes files and validated. It does not bring any additional
security measures over SHA256 that is already present. Unlike
Files/Md5 it is in fact optional and is trivial to drop.

Please consider making Checksums-Sha1 optional in .dsc and .changes.

All basic tooling handles lack of Checksums-Sha1 gracefully, as they
are already not treated as trusted.

Launchpad accepts uploads without Checksums-Sha1.

Dak currently requires Checksums-Sha1, but I am happy to facilitate in
patching dak to make Checksums-Sha1 optional if this bug report is
accepted.

I have not checked other tools like Open Build Service, Artifactory,
etc.

Example files:

https://ppa.launchpadcontent.net/yolo4k/kernels/ubuntu/pool/main/h/hello/hello_2.10-2ubuntu5.dsc

https://launchpadlibrarian.net/699972411/hello_2.10-2ubuntu5_source.changes

Regards,

Dimitri.
>From 95a090af0ced9c04a79da7c006655388fd41a188 Mon Sep 17 00:00:00 2001
From: Dimitri John Ledkov 
Date: Tue, 28 Nov 2023 17:00:20 +
Subject: [PATCH] policy: Make Checksums-Sha1 optional

Make Checksums-Sha1 optional as it is redundant compared to Sha256,
and Sha1 usage should be phased out by 2030. Making Checksums-Sha1
optional is relatively easy and backwards compatible with many
tools. dak will require a change to allow uploads without
Checksums-Sha1, prior to releasing policy & dpkg update.

Signed-off-by: Dimitri John Ledkov 
---
 policy/ch-controlfields.rst| 19 +++
 policy/upgrading-checklist.rst |  9 +
 2 files changed, 20 insertions(+), 8 deletions(-)

diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 2871658f57..d125994b0b 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -243,8 +243,9 @@ is described above, in :ref:`s-controlsyntax`.
 
 -  :ref:`Package-List ` (recommended)
 
--  :ref:`Checksums-Sha1 and Checksums-Sha256 `
-   (mandatory)
+-  :ref:`Checksums-Sha1 ` (optional)
+
+-  :ref:`Checksums-Sha256 ` (mandatory)
 
 -  :ref:`Files ` (mandatory)
 
@@ -297,8 +298,9 @@ The fields in this file are:
 
 -  :ref:`Changes ` (mandatory)
 
--  :ref:`Checksums-Sha1 and Checksums-Sha256 `
-   (mandatory)
+-  :ref:`Checksums-Sha1 ` (optional)
+
+-  :ref:`Checksums-Sha256 ` (mandatory)
 
 -  :ref:`Files ` (mandatory)
 
@@ -1026,10 +1028,11 @@ such as ``<>``.
 ``Checksums-Sha1`` and ``Checksums-Sha256``
 ~~~
 
-These multiline fields contain a list of files with a checksum and size
-for each one. Both ``Checksums-Sha1`` and ``Checksums-Sha256`` have the
-same syntax and differ only in the checksum algorithm used: SHA-1 for
-``Checksums-Sha1`` and SHA-256 for ``Checksums-Sha256``.
+These multiline fields contain a list of files with a checksum and
+size for each one. Both ``Checksums-Sha1`` (optional) and
+``Checksums-Sha256`` (mandatory) have the same syntax and differ only
+in the checksum algorithm used: SHA-1 for ``Checksums-Sha1`` and
+SHA-256 for ``Checksums-Sha256``.
 
 ``Checksums-Sha1`` and ``Checksums-Sha256`` are multiline fields. The
 first line of the field value (the part on the same line as
diff --git a/policy/upgrading-checklist.rst b/policy/upgrading-checklist.rst
index c772b7e178..4cb37cf624 100644
--- a/policy/upgrading-checklist.rst
+++ b/policy/upgrading-checklist.rst
@@ -39,6 +39,15 @@ The sections in this checklist match the values for the
 except in the two anomalous historical cases where normative
 requirements were changed in a minor patch release.
 
+Version 4.6.3
+-
+
+UNRELEASED
+
+
+5.4 & 5.5
+Checksums-Sha1 are now optional.
+
 Version 4.6.2
 -
 
-- 
2.34.1

Bug#1057056: rust-comrak: Unsatisfiable dependency on rust-emojis

[Jeremy Bícha]

Source: rust-comrak
Version: 0.18.0-1
Severity: serious
X-Debbugs-CC: sylves...@debian.org, aferra...@debian.org

librust-comrak-dev depends on librust-emojis-0.5+default-dev but that
is not packaged in Debian.

Thank you,
Jeremy Bícha

Bug#1057055: base-passwd: Fix non-linux cross-build

[Samuel Thibault]

Package: base-passwd
Version: 3.6.2
Severity: normal
Tags: patch

Hello,

Thanks for adding the --disable-selinux option for non-linux ports. To
properly support cross-builds, the condition however needs to be on
DEB_HOST_ARCH_OS rather than BUILD, as the attached patch fixes.

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'), 
(500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 base-passwd depends on:
ii  libc6  2.37-12+b1
ii  libdebconfclient0  0.271
ii  libselinux13.5-1

Versions of packages base-passwd recommends:
ii  cdebconf [debconf-2.0]  0.271
ii  debconf [debconf-2.0]   1.5.82

base-passwd suggests no packages.

-- debconf information excluded

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/rules.original   2023-11-28 23:06:15.392860494 +0100
+++ debian/rules2023-11-28 23:06:25.336910903 +0100
@@ -11,7 +11,7 @@
 confflags += --disable-docs
 endif
 
-ifneq ($(DEB_BUILD_ARCH_OS),linux)
+ifneq ($(DEB_HOST_ARCH_OS),linux)
 confflags += --disable-selinux
 endif
 

Bug#1053069: openhft-chronicle-threads: FTBFS with default Java 21

[Vladimir Petko]

Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this
issue?

Best Regards,
 Vladimir.

[1]
https://salsa.debian.org/java-team/openhft-chronicle-threads/-/merge_requests/2

Bug#1056597: ffmpeg: drawtext filter missing from ffmpeg binaries

[Leo Butler]

The original bug-report expresses doubt about the solution proposed.

As documented here:
https://ffmpeg.org/ffmpeg-all.html#drawtext-1

the build must be configured with both --enable-libfreetype and
--enable-libharfbuzz.

I can confirm that is correct, when building ffmpeg against current git
head.

Leo

ffmpeg started on 2023-11-28 at 15:32:08
Report written to "ffmpeg-20231128-153208.log"
Log level: 48
Command line:
./ffmpeg -y -report -f lavfi -i "testsrc=duration=5:size=hd720:rate=10" -filter_complex "drawtext=fontsize=30:fontfile=/usr/share/fonts/truetype/freefont/FreeSerif.ttf:text=\"hello world\":x=(w-text_w)/2:y=(h-text_h)/2" -f mpegts /tmp/out.ts
ffmpeg version N-112875-g47e214245b-3 Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 13 (Debian 13.2.0-5)
  configuration: --enable-libfreetype --enable-libharfbuzz --enable-libx264 --enable-gpl --prefix=/usr --extra-version=3 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls
  libavutil  58. 32.100 / 58. 32.100
  libavcodec 60. 35.100 / 60. 35.100
  libavformat60. 18.100 / 60. 18.100
  libavdevice60.  4.100 / 60.  4.100
  libavfilter 9. 14.100 /  9. 14.100
  libswscale  7.  6.100 /  7.  6.100
  libswresample   4. 13.100 /  4. 13.100
  libpostproc57.  4.100 / 57.  4.100
Splitting the commandline.
Reading option '-y' ... matched as option 'y' (overwrite output files) with argument '1'.
Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'lavfi'.
Reading option '-i' ... matched as output url with argument 'testsrc=duration=5:size=hd720:rate=10'.
Reading option '-filter_complex' ... matched as option 'filter_complex' (create a complex filtergraph) with argument 'drawtext=fontsize=30:fontfile=/usr/share/fonts/truetype/freefont/FreeSerif.ttf:text="hello world":x=(w-text_w)/2:y=(h-text_h)/2'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'mpegts'.
Reading option '/tmp/out.ts' ... matched as output url.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option y (overwrite output files) with argument 1.
Applying option report (generate a report) with argument 1.
Applying option filter_complex (create a complex filtergraph) with argument drawtext=fontsize=30:fontfile=/usr/share/fonts/truetype/freefont/FreeSerif.ttf:text="hello world":x=(w-text_w)/2:y=(h-text_h)/2.
[AVFilterGraph @ 0x55677bdf0580] Setting 'fontsize' to value '30'
[AVFilterGraph @ 0x55677bdf0580] Setting 'fontfile' to value '/usr/share/fonts/truetype/freefont/FreeSerif.ttf'
[AVFilterGraph @ 0x55677bdf0580] Setting 'text' to value '"hello world"'
[AVFilterGraph @ 0x55677bdf0580] Setting 'x' to value '(w-text_w)/2'
[AVFilterGraph @ 0x55677bdf0580] Setting 'y' to value '(h-text_h)/2'
Successfully parsed a group of options.
Parsing a group of options: input url testsrc=duration=5:size=hd720:rate=10.
Applying option f (force format) with argument lavfi.
Successfully parsed a group of options.
Opening an input file: testsrc=duration=5:size=hd720:rate=10.
[AVFilterGraph @ 0x55677bdf5040] Setting 'duration' to value '5'
[AVFilterGraph @ 0x55677bdf5040] Setting 'size' to value 'hd720'
[AVFilterGraph @ 0x55677bdf5040] Setting 'rate' to value '10'
detected 8 logical cores
[Parsed_testsrc_0 @ 0x55677bdf2240] size:1280x720 rate:10/1 duration:5.00 sar:1/1
[AVFilterGraph @ 0x55677bdf5040] query_formats: 2 queried, 1 merged, 0 already done, 0 delayed
[lavfi @ 0x55677bdf4940] All info found
Input #0, lavfi, from 'testsrc=duration=5:size=hd720:rate=10':
  Duration: N/A, start: 0.00, bitrate: N/A
  Stream #0:0, 1, 1/10: Video: wrapped_avframe, rgb24, 1280x720 [SAR 1:1 DAR 16:9], 10 fps, 10 tbr, 10 tbn
Successfully opened the file.
Parsing a group of options: output url /tmp/out.ts.
Applying option f (force format) with argument mpegts.
Successfully parsed a group of options.
Opening an output file: /tmp/out.ts.
[out#0/mpegts @ 0x55677bdfac40] Creating output stream from unlabeled output of complex filtergraph 0. This overrides automatic video mapping.
[vost#0:0/mpeg2video @ 0x55677bdfbe00] Created video stream from complex filtergraph 0:[drawtext:default]
[vost#0:0/mpeg2video @ 0x55677bdfbe00] 
[out#0/mpegts @ 0x55677bdfac40] No explicit maps, mapping streams automatically...
[file @ 0x55677bdfef80] Setting default whitelist 'file,crypto,data'
Successfully opened the file.
Stream mapping:
  Stream #0:0 (wrapped_avframe) -> drawtext:default
  drawtext:default -> Stream #0:0 (mpeg2video)
Press [q] to stop, [?] for help
[AVFilterGraph @ 0x55677bdff640] Setting 'fontsize' to value '30'
[AVFilterGraph @ 0x55677bdff640] Setting 'fontfile' to value '/usr/share/fonts/truetype/freefont/FreeSerif.ttf'
[AVFilterGr

Bug#1057054: findutils: Support for build profile

[Gioele Barabucci]

Package: src:findutils
Version: 4.9.0-5
Tags: patch

Dear findutils maintainers,

even when the  build profile is used, `texinfo` remains a
required build dependency.

A MR that fixes this issue is available at:

https://salsa.debian.org/debian/findutils/-/merge_requests/2

Regards,

--
Gioele Barabucci

Bug#1056151: reason

[Thomas Lange]

The comment in lib/updatebase explains why the diversion for
/sbin/init was added:

# if libc is upgraded init u is called in chroot environment and
# then init will eat up much cpu time

This was a rare case in the past and maybe we can remove this
diversion? What do you think?

-- 
 Thomas

Bug#1057053: Blank video when playing AV1 encoded videos

[Andreas Messer]

Package: vlc
Version: 3.0.20-0+deb12u1

When playing an AV1 encoded video from webm file, video display is blank
and only audio is working. It seems to me that vlc tries hw acceleration
via VDPAU although my card does not support AV1 hardware decoding. VLC
should fall back to software decoding in this case. (It works properly if
I disable hardware acceleration entirely in vlc)

Please find command line output below:

$ vlc Optimistic\ Delay.webm
VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b)
[5578b3e71520] main libvlc: VLC wird mit dem Standard-Interface ausgeführt. 
Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden.
[7f3408004930] gl gl: Initialized libplacebo v4.208.0 (API v208)
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
[7f34082550e0] gl gl: Initialized libplacebo v4.208.0 (API v208)
[7f3404c1b580] avcodec decoder: Using G3DVL VDPAU Driver Shared Library 
version 1.0 for hardware decoding
[7f3404c1b580] main decoder error: buffer deadlock prevented

$ vdpauinfo | grep AV1
AV1_MAIN   --- not supported ---
AV1_HIGH   --- not supported ---
AV1_PROFESSIONAL   --- not supported ---

Best regards,
Andreas Messer

-- 
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51


signature.asc
Description: PGP signature

Bug#1057052: amd64 install DVD 1 puts "contrib" component on target's sources.list

[Adonay Felipe Nogueira]

Package: debian-cd
Source: debian-cd
Version: 3.1.17
Severity: important

# How to reproduce?

Do as follows:

1. get the installation DVD 1 from [1];

2. use it to install Debian, optionally selecting a mirror;

3. notice that the target's "/etc/apt/sources.list" has both "security"
and "updates" distributions/repositories for the "contrib" component. If
no mirror was selected, only "security" distribution/repository is enabled.

# How often it is reproduced?

For "security" distribution/repository, it is always reproducible. In
the case of "updates" distribution/repository, it applies only if a
mirror was selected.

# Other information

No test was made for other architectures, download methods (e.g.:
jiglo), or media types/variants (e.g.: CD, netinstall).

These assume that you did `git clone --recursive
"https://salsa.debian.org/images-team/debian-cd.git; && cd "debian-cd" `.

## Commits related to "contrib" component

The following procedure was used to find what implemented "contrib"
component:

1. use `git grep -Ei 'contrib' | sed -E '/(^|\/)(doc|info|man)|\.pot?:/d' `;

2. for each file, do a `git blame`, and look for related lines and
corresponding commits that implemented "contrib" component;

3. checkout the previous from that commit (`git checkout hash~1`);

4. repeat from step 1 until there is no other match for that path;

5. do `git checkout master` and repeat from step 1 until there are no
more paths matching the search for implementations of "contrib" component.

This led to the following possibly problematic commits:

Commit: e83ef58217c4f830ed12ecb314517818417c984d
Date: 1999-11-11T17:10:37+
Note: "contrib" added for the first time.

Commit: 916440cf9a265370facae13776213aefaa8a28d6
Date: 2002-12-07T10:22:40+
Note: makes the usage of "contrib" an opt-out.

## Commits related to popcon/popularity-contest

The following procedure was used to find what added
popcon/popularity-contest:

1. do `git log -p tasks/{,*/}popularity-contest* | less -I '+/contrib'
+GN `, and take the coomit hash of the nearest line from above, to do
so, type “?^commit”, Enter;

2. checkout the previous from that commit (`git checkout hash~1`);

3. repeat from step 1 until there is no other match for contrib on popcon.

This results in the following list of possibly problematic commits:

Commit: 8e74984498ffaff1d64fe125a5d09ca6d521c035
Date: 1999-12-27T23:11:18+
Note: adds popcon/popularity-contest which by default takes the most
used packages, which as of today takes stuff from "main" and "contrib".

# Possible list of affected paths

The possibly related files, across all iterations of the steps from the
procedures described earlier are as follows:

tasks/*/popularity-contest
tasks/popularity-contest*
tasks/README
CONF.sh
tools/apt-selection
tools/create_control
tools/generate_di_list
tools/grab_source_list
tools/make_disc_trees.pl
tools/sort_deps
tools/start_new_disc
tools/which_deb
update-cd

# Possible affected versions

Based on the fact that the commits found date back to 1999, version tag
3.1.17, from 2015, was selected, since it is the oldest one which is
still present in the pool ([2]).

# Rationale and suggestions

All in all, due to the way that which the DVD/CD process is done as of
today, the inclusion of the packages that came from "contrib" also
inserts this repository on the target's "/etc/apt/sources.list" since
the apt-setup source package sees the list of sources.

The reasoning for reporting this is that, according to the Debian Policy
Manual, only the "main" component is part of Debian distribution ([3],
[4]), while "contrib" is not ([5]), so the target's
"/etc/apt/sources.list" should reflect that.

Possible solutions include:

a) make "contrib" an opt-in (instead of the current opt-out), and use
opt-in for the Debian-provided media;

b) move this bug to Debian Policy team so that the "contrib" component
is also considered as part of the Debian distribution;

c) since the only package that is currently fetched is "iucode-tool",
find a way to detect which processors would need "iucode-tool", and ask
for the user themselves to insert an extra media with the firmware, and
only use that during install;

d) remove "contrib" from popcon/popularity-contest.

# References

[1]:
https://get.debian.org/images/release/current/amd64/bt-dvd/debian-11.0.0-amd64-DVD-1.iso.torrent
.

[2]: https://deb.debian.org/debian/pool/main/d/debian-cd/ .

[3]: https://www.debian.org/social_contract#guidelines , search for
“Works that do not meet our free software standards”.

[4]:
https://www.debian.org/doc/debian-policy/ch-archive#the-main-archive-area .

[5]:
https://www.debian.org/doc/debian-policy/ch-archive#the-contrib-archive-area
.

--
* https://libreplanet.org/wiki/User:Adfeno
* Ativista não advogado, nem técnico de informática
* Compre dos vendedores locais
* Use e contribua ao software livre (diferente do gratuito)
* Enviando docs.? Use OpenDocument. Outros tipos: vide endereço anterior
* Use XMPP 

Bug#1053068: openhft-affinity: FTBFS with default Java 21

[Vladimir Petko]

Dear Maintainers,

 Due to ThreadGroup API changes it is no longer possible to keep the
current version of the package in the working state with Java 21.
 Would it be possible to consider a merge request upgrading the package to
3.23.3[1]?

Best regards,
 Vladimir.

[1] https://salsa.debian.org/java-team/openhft-affinity/-/merge_requests/2

Bug#1057051: python-lesscpy: diff for NMU version 0.15.1-0.1

[Boyuan Yang]

Package: python-lesscpy
Version: 0.15.0+ds-0.1
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for python-lesscpy (versioned as 0.15.1-0.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru python-lesscpy-0.15.0+ds/PKG-INFO python-lesscpy-0.15.1/PKG-INFO
--- python-lesscpy-0.15.0+ds/PKG-INFO   2021-07-15 02:55:01.007032000 -0400
+++ python-lesscpy-0.15.1/PKG-INFO  2022-10-21 07:38:03.252287400 -0400
@@ -1,12 +1,11 @@
 Metadata-Version: 2.1
 Name: lesscpy
-Version: 0.15.0
+Version: 0.15.1
 Summary: Python LESS compiler
 Home-page: https://github.com/lesscpy/lesscpy
 Author: Jóhann T Maríusson
 Author-email: j...@robot.is
 License: MIT
-Platform: UNKNOWN
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Environment :: Console
 Classifier: Intended Audience :: End Users/Desktop
@@ -16,12 +15,12 @@
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.4
-Classifier: Programming Language :: Python :: 3.5
 Classifier: Programming Language :: Python :: 3.6
 Classifier: Programming Language :: Python :: 3.7
 Classifier: Programming Language :: Python :: 3.8
 Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
 Classifier: Topic :: Software Development :: Code Generators
@@ -104,9 +103,8 @@
 Requirements
 
 
-- Python 3.4 - 3.9,
+- Python 3.7 - 3.11,
 - ply (Python Lex-Yacc) (check requirements.txt)
-- six
 
 Installation
 
@@ -185,7 +183,6 @@
 .. code-block:: python
 
 import lesscpy
-from six import StringIO
 
 print(lesscpy.compile(StringIO(u"a { border-width: 2px * 3; }"),
minify=True))
 
@@ -202,5 +199,3 @@
 
 
 .. _`Python Package Index`: https://pypi.python.org/pypi/lesscpy
-
-
diff -Nru python-lesscpy-0.15.0+ds/README.rst python-lesscpy-0.15.1/README.rst
--- python-lesscpy-0.15.0+ds/README.rst 2021-07-15 02:36:54.0 -0400
+++ python-lesscpy-0.15.1/README.rst2022-10-21 07:32:56.0 -0400
@@ -73,9 +73,8 @@
 Requirements
 
 
-- Python 3.4 - 3.9,
+- Python 3.7 - 3.11,
 - ply (Python Lex-Yacc) (check requirements.txt)
-- six
 
 Installation
 
@@ -154,7 +153,6 @@
 .. code-block:: python
 
 import lesscpy
-from six import StringIO
 
 print(lesscpy.compile(StringIO(u"a { border-width: 2px * 3; }"),
minify=True))
 
diff -Nru python-lesscpy-0.15.0+ds/debian/changelog python-lesscpy-
0.15.1/debian/changelog
--- python-lesscpy-0.15.0+ds/debian/changelog   2022-08-09 21:29:18.0
-0400
+++ python-lesscpy-0.15.1/debian/changelog  2023-11-28 15:13:04.0
-0500
@@ -1,3 +1,13 @@
+python-lesscpy (0.15.1-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release.
++ Declare compatibility with python 3.11.
+  * Bump Standards-Version to 4.6.2.
+  * Bump debhelper compat to v13.
+
+ -- Boyuan Yang   Tue, 28 Nov 2023 15:13:04 -0500
+
 python-lesscpy (0.15.0+ds-0.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru python-lesscpy-0.15.0+ds/debian/control python-lesscpy-
0.15.1/debian/control
--- python-lesscpy-0.15.0+ds/debian/control 2022-08-09 21:28:00.0
-0400
+++ python-lesscpy-0.15.1/debian/control2023-11-28 15:11:15.0
-0500
@@ -3,12 +3,12 @@
 Priority: optional
 Maintainer: Thomas Andrejak 
 Rules-Requires-Root: no
-Build-Depends: debhelper-compat (= 12),
+Build-Depends: debhelper-compat (= 13),
dh-python,
python3-all,
python3-ply,
python3-setuptools,
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/totol-guest/python-lesscpy
 Vcs-Git: https://salsa.debian.org/totol-guest/python-lesscpy.git
 Homepage: https://pypi.python.org/pypi/lesscpy
diff -Nru python-lesscpy-0.15.0+ds/lesscpy/__init__.py python-lesscpy-
0.15.1/lesscpy/__init__.py
--- python-lesscpy-0.15.0+ds/lesscpy/__init__.py2021-07-15
02:45:16.0 -0400
+++ python-lesscpy-0.15.1/lesscpy/__init__.py   2022-10-21 07:26:04.0
-0400
@@ -1,4 +1,4 @@
-__version_info__ = ('0', '15', '0')
+__version_info__ = ('0', '15', '1')
 __version__ = '.'.join(__version_info__)
 
 
diff -Nru python-lesscpy-0.15.0+ds/lesscpy.egg-info/PKG-INFO python-lesscpy-
0.15.1/lesscpy.egg-info/PKG-INFO
--- python-lesscpy-0.15.0+ds/lesscpy.egg-info/PKG-INFO  2021-07-15
02:55:00.0 -0400
+++ python-lesscpy-0.15.1/lesscpy.egg-info/PKG-INFO 2022-10-21
07:38:03.0 -0400
@@ -1,12 +1,11 @@
 Metadata-Version: 2.1
 Name: lesscpy
-Version: 0.15.0
+Version: 0.15.1
 Summary: Python LESS compiler
 Home-page: 

Bug#1033894: lintian: bad-distribution-in-changes-file bookworm

[Otto Kekäläinen]

The fix for this issue is still only in git at
https://salsa.debian.org/lintian/lintian/-/commit/ebb739d102d55797516c0f10452e4e4c2502644d
and there has not been any new Lintian uploads since Lintian 2.116.3
in February 2023.

Anybody maintaining packages in Bookworm and using Salsa-CI is bound
to hit on hard failure as Lintian will error on this one. Example
https://salsa.debian.org/otto/mariadb-server/-/jobs/4976386:

E: mariadb changes: bad-distribution-in-changes-file bookworm

Bug#1026898: deprecate QUOTAUSER post-bookworm

[Marc Haber]

On Mon, Nov 27, 2023 at 09:57:22AM +0100, Sylvain Beucler wrote:
> On 26/11/2023 11:32, Marc Haber wrote:
> > On Sun, Nov 26, 2023 at 10:00:27AM +0100, Sylvain Beucler wrote:
> > > I use QUOTAUSER on a multi-user remote system, for a non-profit, where
> > > people tend to forget about disk space, to ensure any new 'adduser' sets a
> > > reasonable quota.
> > > 
> > > If there's an alternative please let me know.
> > 
> > The alternative would be to use edquota -p (quota) (username) after
> > creating the user. At least that's what adduser does when the quotauser
> > configuration option is set.
> 
> I use QUOTAUSER so I can be sure that when me or a co-admin creates a user,
> the quota is set, and there's no way to forget about it (iow I know how to
> do it manually).  By alternative, I mean a way to ensure that the quota is
> always set for new users :)

How about having a wrapper around adduser? Or a cronjob that iterates
through the users and installs the quota even for users that had it
removed?

This could also be an application for #36019, hooks.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1057050: qt6-multimedia: Please build with EIGEN_DONT_VECTORIZE on powerpc to fix FTBFS

[John Paul Adrian Glaubitz]

Source: qt6-multimedia
Version: 6.4.2-11
Severity: normal
User: debian-powe...@lists.debian.org
Usertags: powerpc
X-Debbugs-Cc: debian-powe...@lists.debian.org

Hello!

The package src:qt6-multimedia fails to build from source on powerpc since 
version
6.4.0-1 due to the use of some AltiVec instrisics that are not supported on 
32-bit
PowerPC:

/usr/bin/c++ -DEIGEN_MPL2_ONLY -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
-DQT_NO_JAVA_STYLE_ITERATORS \
(...)
In file included from /usr/include/eigen3/Eigen/Core:210,
 from /usr/include/eigen3/Eigen/Dense:1,
 from 
/<>/src/resonance-audio/../3rdparty/resonance-audio/platforms/common/utils.h:20,
 from 
/<>/src/3rdparty/resonance-audio/platforms/common/utils.cc:17:
/usr/include/eigen3/Eigen/src/Core/arch/AltiVec/PacketMath.h: In function \
‘Packet Eigen::internal::pblend(const Selector::size>&, 
const Packet&, const Packet&) [with Packet = __vector(2) double]’:
/usr/include/eigen3/Eigen/src/Core/arch/AltiVec/PacketMath.h:2702:17: error: 
invalid parameter combination for AltiVec intrinsic ‘__builtin_vec_sel’
 2702 |   return vec_sel(elsePacket, thenPacket, mask);
  | ^

This can be fixed by switching off vectorization in the »eigen« using the 
preprocessor
macro EIGEN_DONT_VECTORIZE which can be defined on the cmake command line using 
the
cmake variable COMPILE_DEFINITIONS:

--- qt6-multimedia-6.4.2/debian/rules.orig  2023-07-26 17:52:13.0 
+0200
+++ qt6-multimedia-6.4.2/debian/rules   2023-11-28 18:26:47.950137854 +0100
@@ -9,6 +9,10 @@
cmake_extra_args += -DQT_HOST_PATH=/usr
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH),powerpc))
+   cmake_extra_args += -DCOMPILE_DEFINITIONS="EIGEN_DONT_VECTORIZE"
+endif
+
 %:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
 
With the above change, cmake defines the preprocessor macro 
EIGEN_DONT_VECTORIZE and
the build succeeds on powerpc.

Could you apply this change for the next upload in order to fix the build on 
powerpc?

Attaching a patch for a convenience.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- qt6-multimedia-6.4.2/debian/rules.orig  2023-07-26 17:52:13.0 
+0200
+++ qt6-multimedia-6.4.2/debian/rules   2023-11-28 18:26:47.950137854 +0100
@@ -9,6 +9,10 @@
cmake_extra_args += -DQT_HOST_PATH=/usr
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH),powerpc))
+   cmake_extra_args += -DCOMPILE_DEFINITIONS="EIGEN_DONT_VECTORIZE"
+endif
+
 %:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
 

Bug#1057013: Regression: addgroup user group no longer works and should have been documented instead of removed

[Marc Haber]

Control: severity -1 wishlist
Control: tags -1 wontfix
thanks

On Mon, Nov 27, 2023 at 05:27:11PM -0500, theofficialgman wrote:
> A regression was caused with the unnecessary commit
> https://salsa.debian.org/debian/adduser/-/commit/8d42193438f6c1500fb36cd5c24bf682888a611c
> to close https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664869
> 
> This undocumented syntax was known in use in scripting (such as nvidia
> tegra debian based distros). Instead of disabling two argument syntax
> this should instead be reverted and the manpage should be fixed to
> advertise this syntax since it is functional and in use.

#664869 was open undisputed for ten years, nobody cared.

I am tagging this bug wontfix and will close it with the trixie+1
release. Please point me to the place where this accidental misfeature
was ever documented, I might revisit my decision then.

If this actually was never documented, please refer this issue to the
technical committee.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#979688: Simplifying the list of image files for arm64 sunxi boards

[Vagrant Cascadian]

On 2023-11-28, harr...@gmx.ph wrote:
> On 27/11/2023 20:12, Vagrant Cascadian (@vagrant) wrote on salsa:
>>Thanks! Looks good to me, could you add (Closes: #XXX) on the first line of 
>>the commit?
...
> Thanks for agreeing to the merge request. I've added the Closes: note.

Thanks!


> I just wanted to note while the bug is still open, that I was originally
> aiming to simplify the list of files for each arm64 sunxi board in targets.mk,
> and from my point of view u-boot-sunxi-with-spl.bin is the only one still 
> needed.

Understood.


> I know that you said earlier (on 25/07/2023 17:39 in the bug report):
>
>> I am also a bit inclined to adding u-boot-sunxi-with-spl.bin rather than
>> replacing all the other parts, as there are some use-cases (e.g. an
>> image capable of booting both sunxi and rockchip systems at different
>> offsets) where the individual parts are still needed.
>
> but I'm not sure that's right, because I believe sunxi-spl.bin and
> u-boot-sunxi-with-spl.fit.itb always need to be concatenated to work,
> because the SPL is hard-coded to look for U-Boot proper immediately after
> itself, as determined by spl_mmc_get_uboot_raw_sector() in
> arch/arm/mach-sunxi/board.c. So I think any "One image to rule them all"
> that arranged the parts differently would need a custom build, not the
> files currently in the Debian u-boot binary packages.

I had managed to successfully build a bootable image doing it "the old
way" that worked on both pinebook (allwinner A64) and pinebook pro
(rockchip rk3399) at "alternate offsets" that required no changes to the
u-boot binaries... but that was with older versions. I would hate to
break that ability, although it would be reasonable to test it sometime
to make sure it still works!

In the meantime, I would like to leave the builds shipping more than
strictly necessary for booting each board.


> That said, I'm happy to see u-boot-sunxi-with-spl.bin included, so thank you
> very much for doing that and all the other things that came up in this
> sprawling bug report.

Likewise!


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1057048: gstreamer1.0: please enable libunwind support on riscv64

[Aurelien Jarno]

Source: gstreamer1.0
Version: 1.22.6-1
Severity: wishlist
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear maintainer,

During the initial bootstrap of the riscv64 port, libunwind support was
not available and thus it was not enabled in gstreamer1.0. In the
meantime libunwind got ported to riscv64 and the package is available
in the archive.

Therefore could you please enable libunwind support in gstreamer1.0 on
riscv64? In addition to improving the package, having similar
dependencies than other architectures prevents some FTBFS (e.g. recent
pipewire FTBFS). For the record, this has been tested with the patch
below.

Thanks,
Aurelien


--- gstreamer1.0-1.22.6/debian/control
+++ gstreamer1.0-1.22.6/debian/control
@@ -14,8 +14,8 @@
libglib2.0-dev (>= 2.62.0),
libgmp-dev  | libgmp3-dev ,
libgsl-dev  | libgsl0-dev ,
-   libunwind-dev [i386 amd64 armel armhf arm64 powerpc ppc64 
ppc64el mipsel mips64el],
-   libdw-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el 
mipsel mips64el],
+   libunwind-dev [i386 amd64 armel armhf arm64 powerpc ppc64 
ppc64el mipsel mips64el riscv64],
+   libdw-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el 
mipsel mips64el riscv64],
bison (>= 1:2.4),
flex (>= 2.5.34),
libgirepository1.0-dev (>= 0.9.12-4~),
@@ -59,8 +59,8 @@
  libc6-dev | libc-dev,
  pkg-config,
  libglib2.0-dev,
- libunwind-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el 
mipsel mips64el],
- libdw-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el mipsel 
mips64el],
+ libunwind-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el 
mipsel mips64el riscv64],
+ libdw-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el mipsel 
mips64el riscv64],
  ${shlibs:Depends},
  ${misc:Depends},
  gir1.2-gstreamer-1.0 (= ${binary:Version})
diff -Nru gstreamer1.0-1.22.6/debian/rules
--- gstreamer1.0-1.22.6/debian/rules
+++ gstreamer1.0-1.22.6/debian/rules
@@ -40,7 +40,7 @@
-Dptp-helper-setuid-user=nobody -Dptp-helper-setuid-group=nobody
 endif
 
-ifeq (,$(filter $(DEB_HOST_ARCH),i386 amd64 armel armhf arm64 powerpc ppc64 
ppc64el mipsel mips64el))
+ifeq (,$(filter $(DEB_HOST_ARCH),i386 amd64 armel armhf arm64 powerpc ppc64 
ppc64el mipsel mips64el riscv64))
 conf_flags += -Dlibunwind=disabled -Dlibdw=disabled
 endif
 

Bug#1055364: rust-rayon: please update to v1.8.0

[Peter Green]

Please update to (at least) newer upstream release v1.8.0.

I just looked at this, the new version of rayon requires
a new version of rayon-core, unfortunately when updating
rayon-core I ran into a test failure that looks like it
may indicate an unintentional API break. I'm not
comfortable uploading this until I get feedback
from upstream.

Bug#1056998: cdrom: Installation media changes after booting it

[Ram Reddy]

Hello,
Thomas Schmitt wrote:
>
> I'd say that corruption of ISO image or USB is quite unlikely.
>[ . . . ]
>It would be interesting to check whether any errors get reported if the
> ISO is presented on a read-only CD or DVD instead of a writable USB stick.

Thank you for the suggestion for trying a CD / DVD read only installation
media. Unfortunately I don't have one at hand, and there are none in
the stores here. The only option seems to be to order one online, which will
take a few days to ship.

When I get the disks, I'll test using the installer with them.
Thanks for the help!

Have a great day;
Ram

Bug#1056992: freerdp2: Please package version 3

[Mike Gabriel]

Hi Jeremy,

On  Mo 27 Nov 2023 18:19:55 CET, Jeremy Bícha wrote:


Source: freerdp2
Version: 2.11.2+dfsg1-1
Severity: wishlist
X-Debbugs-CC: sunwea...@debian.org

FreeRDP 3.0.0 RC0 was just released. We should begin thinking about
how we will handle its packaging. I believe it would require a major
transition if we aim to keep only one version of FreeRDP in Debian.

gnome-remote-desktop 46 is expected to be released in March  
requiring FreeRDP 3.


Thank you,
Jeremy Bícha


my overall idea would be to upload a new freerdp3 src:pkg like we did  
for freerdp(1) -> freerd2.


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



pgp_jxtjYGs9I.pgp
Description: Digitale PGP-Signatur

Bug#1057044: xymon: ntpdate no longer supports the -p option

[Axel Beckert]

Hi Carsten,

Carsten Leonhardt wrote:
> ntpdate emits a warning when called with the -p option. I've attached a
> patch to drop that option from xymonserver.cfg.

Thanks. Sounds kinda familiar.

> If you prefer, I can also commit directly to salsa.

Fine for me, thanks!

> Subject: [PATCH] xymon: update xymonserver.cfg: ntpdate no longer
>  supports the "-p" option (cf. #926877).

Oh, #926877 was my bug report. Maybe that's why it sounds familiar.
%-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1057031: nvme-stas: autopkgtest hanging on s390x

[Olivier Gayot]

Hello,

nvme-stas v2.3.1 is out now :)

https://github.com/linux-nvme/nvme-stas/releases/tag/v2.3.1

Best regards,
Olivier

Bug#1056556: Debugging techniques

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Dima Kogan (2023-11-28 17:25:01)
> I sorta expected that there was extra complexity here that made
> debugging difficult. It's unfortunate.

to be fair, I have yet to see a problem involving apt pinning that was not
difficult. If the wrong package that got installed did not make you immediately
think of apt pinning, then this would've also happened without mmdebstrap on
any regular system.

> > mmdebstrap ... --variant=apt --chrooted-customize-hook=bash unstable 
> > /dev/null
> 
> Would that work, though?

Yes. Did you try it and it did not work? What was the error message?

>   --chrooted-customize-hook isn't in the manpage

Correct. That's on purpose.

>   --customize-hook runs after everything was installed (so past where
> the failure was happening here)

That's why I suggested *not* to put your packages into --include but running
"apt-get install" manually once you have bash inside the chroot.

>   --essential-hook was running at the right time, but the "apt-get"
> executable wasn't available

Yes, because apt is not essential. That's why I recommended using
--variant=apt.

> In any case, I figured out my specific problem by creating a similar
> scenario on a native arm64 box. I was naming the pinning file .conf
> instead of .pref which apparently matters.

Yes, in the man page of apt_preferences it says: "The files have either no or
"pref" as filename extension". In one of my last mails to you I also suggested
you add:

--setup-hook='{ echo "Package: XXX"; echo "Pin: origin \"YYY\""; echo 
"Pin-Priority: 1"; } > "$1"/etc/apt/preferences.d/mypinnings.pref'

Notice that I used the correct filename extension.

> On the arm64 box this produced a clear error message ("apt" told me to
> rename the file). But with mmdebstrap there was no specific error at all, as
> you saw. Any idea why?

Which apt command produced the error? I also don't think it was an error. It
was only a warning, right? Did you get it for "apt-get update" or for "apt-get
install"?

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1057047: tomcat10-common: Tomcat 10 helper script doesn't look for temurin based jdk installs

[Joan]

Package: tomcat10-common
Version: 10.1.15-1
Severity: normal
X-Debbugs-Cc: aseq...@gmail.com

Dear Maintainer,

   * What led up to the situation?
I am trying to use debian's tomcat 10 with java 21, since it's not present on 
debian I used the one from 
https://adoptium.net/installation/linux/ that has a repository.
When starting tomcat I see this error message on the logs: 
  " [crit] No JDK or JRE found - Please set the JAVA_HOME variable or install 
the default-jdk package"
I traced the message to the helper script 
/usr/libexec/tomcat10/tomcat-locate-java.sh, there adding the
 temurin naming scheme made the helper found the proper java

from:.
for jvmdir in /usr/lib/jvm/java-${java_version}-openjdk-* \
  /usr/lib/jvm/jdk-${java_version}-oracle-* \
  /usr/lib/jvm/jre-${java_version}-oracle-* \
  /usr/lib/jvm/java-${java_version}-oracle \
  /usr/lib/jvm/oracle-java${java_version}-jdk-* \
  /usr/lib/jvm/oracle-java${java_version}-jre-*
do

to:...
for jvmdir in /usr/lib/jvm/java-${java_version}-openjdk-* \
  /usr/lib/jvm/jdk-${java_version}-oracle-* \
  /usr/lib/jvm/jre-${java_version}-oracle-* \
  /usr/lib/jvm/java-${java_version}-oracle \
  /usr/lib/jvm/oracle-java${java_version}-jdk-* \
  /usr/lib/jvm/oracle-java${java_version}-jre-* \
  /usr/lib/jvm/temurin-${java_version}-jre-* \
  /usr/lib/jvm/temurin-${java_version}-jdk-*
do


Since currently the temurin path is quite a popular way to install recent 
jdk/jre version without
having to rely on oracle, supporting it on debian would be nice and without 
collateral issues


-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-89-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1029202: Could some SnpEff user from the community please ping authors

[Andreas Tille]

Hi,

we tried to package snippy which has uncovered a bug in SnpEff which we
have reported upstream[1] with some easily verificable data set and
command line.  Unfortunately we did not had any response from upstream.
We even would consider to revert SnpEff version to a working one without
this regression (like 5.0e).  However, we would like to have the correct
code base for this release but even asking for proper tagging of the
code was ignored inside the issue.

I wonder whether some people from the community might be able to join
our attempt to get this issue fixed and raise their voice inside the
Github issue (or use other channels) to get this finally fixed.  I guess
the problem does not only occure in snippy test suite but also in other
pipelines so the community might be affected by this issue.

Kind regards and thanks for your support
Andreas.

[1] https://github.com/pcingola/SnpEff/issues/455

-- 
http://fam-tille.de

Bug#1057033: nemo: Several MIME types not recognized on GVFS mounted volumes

[Fabio Fantoni]

Control: fixed -1 5.8.5-2

Hi, thanks for the report.

Problem reproduced immediately when seeing a .doc file on share smb, on 
Sid with nemo 5.8.5 is not present so was fixed but from a fast search I 
don't found the possible commit of fix, only one related to video 
thumbnails from network shares 
(https://github.com/linuxmint/nemo/pull/3265) but should not be related FWIK


Even if the fix commit were found, however, it is not a bug important 
enough to propose a stable update.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1029202: snippy: Error when using snpeff 5.1

[Andreas Tille]

Hi,

since version 5.2.b is not worse than 5.1 (= upstream upgrade with
the very same problematic output as version 5.1) I decided to update
to the latest upstream version and pinged upstream again[1].

Kind regards
 Andreas.

[1] https://github.com/pcingola/SnpEff/issues/455

-- 
http://fam-tille.de

Bug#1057046: RM: autoconf2.64 -- obsolete version

[Matthias Klose]

Package: ftp.debian.org

Please remove autoconf2.64, that was needed for gcc-8, which isn't in 
Debian anymore.

Bug#1056556: Debugging techniques

[Dima Kogan]

Hi josch.

I sorta expected that there was extra complexity here that made
debugging difficult. It's unfortunate.


> mmdebstrap ... --variant=apt --chrooted-customize-hook=bash unstable /dev/null

Would that work, though?

  --chrooted-customize-hook isn't in the manpage

  --customize-hook runs after everything was installed (so past where
the failure was happening here)

  --essential-hook was running at the right time, but the "apt-get"
executable wasn't available

In any case, I figured out my specific problem by creating a similar
scenario on a native arm64 box. I was naming the pinning file .conf
instead of .pref which apparently matters. On the arm64 box this
produced a clear error message ("apt" told me to rename the file). But
with mmdebstrap there was no specific error at all, as you saw. Any idea
why?

Thanks for all the help.

Bug#1055646: gdb: extremely slow response to basic commands

[tomazzi]

Hello Héctor,

On Tue, 28 Nov 2023 13:37:40 +0100 
=?UTF-8?B?SMOpY3RvciBPcsOzbiBNYXJ0w61uZXo=?=  wrote:


> I wanted to drop a link to addr2line bug[1], could that be related?
>
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=29785

Thanks for this link.
It looks like it can be related, but I can't confirm this at the moment.

 > > I thought that this BUG should be easy to eliminate - but it turns out

> > that there are several serious BUGs in the gdb, and the only way to
> > eliminate them is to debug the gdb first ;)
>
> Which several serious bugs? I understand you mean in the upstream GNU
> GDB, instead of the Debian GNU GDB package. Are those reported
> upstream?

Well, I think that at least 2 problems are obvious:
- huge memory consumption (can be related to the upstream bug or just a 
memory leak)
- creation of useless threads: I would expect that "enable-threading" 
really enables SMP for searching symbol tables, memory ranges, etc.


I haven't reported this yet, because first I want to fully understand 
whats going on.

And yes, I mean upstream GNU GDB bugs.

Regards.

Bug#1057045: picom frequent SIGABRT

[Mihai Hanor]

Package: picom
Version: 10.2-1
Severity: normal
X-Debbugs-Cc: quake2i...@gmail.com

Dear Maintainer,


   * What led up to the situation?
I'm not sure what is the context of the crash, my impression is that picom
crashes after the PC is resuming from S3 sleep.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
N/A
   * What was the outcome of this action?
N/A
   * What outcome did you expect instead?
No crash.


Crash call stack:
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x7f9e460a815f in __pthread_kill_internal (signo=6,
threadid=) at ./nptl/pthread_kill.c:78
#2  0x7f9e4605a472 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7f9e460444b2 in __GI_abort () at ./stdlib/abort.c:79
#4  0x7f9e460443d5 in __assert_fail_base (fmt=0x7f9e461b8dc8
"%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x55edf0673703
"!w->mask_image",
file=file@entry=0x55edf06736ba "../src/win.c", line=line@entry=349,
function=function@entry=0x55edf0674ca0 <__PRETTY_FUNCTION__.68>
"win_bind_mask") at ./assert/assert.c:92
#5  0x7f9e460533a2 in __assert_fail
(assertion=assertion@entry=0x55edf0673703
"!w->mask_image", file=file@entry=0x55edf06736ba "../src/win.c",
line=line@entry=349,
function=function@entry=0x55edf0674ca0 <__PRETTY_FUNCTION__.68>
"win_bind_mask") at ./assert/assert.c:101
#6  0x55edf0635118 in win_bind_mask (b=b@entry=0x55edf1b2b110,
w=w@entry=0x55edf199e200)
at ../src/win.c:349
#7  0x55edf0637148 in win_bind_shadow (b=0x55edf1b2b110,
w=w@entry=0x55edf199e200,
c=..., sctx=0x55edf17903f0) at ../src/win.c:372
#8  0x55edf0638936 in win_process_image_flags (ps=ps@entry=0x55edf1235c70,
w=w@entry=0x55edf199e200) at ../src/win.c:579
#9  0x55edf0633211 in refresh_images (ps=) at
../src/picom.c:1391
#10 handle_pending_updates (ps=, loop=0x7f9e46b40720
) at ../src/picom.c:1445
#11 draw_callback_impl (revents=, ps=,
loop=0x7f9e46b40720 ) at ../src/picom.c:1460
#12 draw_callback (loop=0x7f9e46b40720 , w=, revents=) at ../src/picom.c:1550
#13 0x7f9e46b34633 in ev_invoke_pending (loop=0x7f9e46b40720
) at ./ev.c:3770
#14 0x7f9e46b38177 in ev_run (flags=0, loop=0x7f9e46b40720
) at ./ev.c:4190
#15 ev_run (loop=0x7f9e46b40720 , flags=flags@entry=0)
at ./ev.c:4021
#16 0x55edf062e49e in session_run (ps=0x55edf1235c70) at
../src/picom.c:2465
#17 main (argc=, argv=) at ../src/picom.c:2567


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-debug'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 picom depends on:
ii  libc62.37-12
ii  libconfig9   1.5-0.4
ii  libdbus-1-3  1.14.10-3
ii  libegl1  1.7.0-1
ii  libev4   1:4.33-2
ii  libgl1   1.7.0-1
ii  libpcre3 2:8.39-15
ii  libpixman-1-00.42.2-1
ii  libx11-6 2:1.8.7-1
ii  libx11-xcb1  2:1.8.7-1
ii  libxcb-composite01.15-1
ii  libxcb-damage0   1.15-1
ii  libxcb-glx0  1.15-1
ii  libxcb-image00.4.0-2
ii  libxcb-present0  1.15-1
ii  libxcb-randr01.15-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.15-1
ii  libxcb-shape01.15-1
ii  libxcb-sync1 1.15-1
ii  libxcb-xfixes0   1.15-1
ii  libxcb-xinerama0 1.15-1
ii  libxcb1  1.15-1
ii  python3  3.11.4-5+b1

picom recommends no packages.

picom suggests no packages.

-- no debconf information
(gdb) thread apply all bt full

Thread 10 (Thread 0x7f9e36dfe6c0 (LWP 3455)):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, 
op=393, expected=0, futex_word=0x55edf13c37f0) at ./nptl/futex-internal.c:57
sc_cancel_oldtype = 0
__arg6 = 
__arg3 = 
_a5 = 
_a2 = 
sc_ret = 
__arg4 = 
__arg1 = 
_a6 = 
_a3 = 
resultvar = 
__arg5 = 
__arg2 = 
_a4 = 
_a1 = 
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55edf13c37f0, 
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, 
private=private@entry=0, cancel=cancel@entry=true) at ./nptl/futex-internal.c:87
err = 
clockbit = 256
op = 393
#2  0x7f9e460a31bb in __GI___futex_abstimed_wait_cancelable64 
(futex_word=futex_word@entry=0x55edf13c37f0, expected=expected@entry=0, 
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at 
./nptl/futex-internal.c:139
No locals.
#3  

Bug#1055711: gcc-13: Please build gcc with -mbranch-protection=standard to fix PAC/BTI support on arm64

[Emanuele Rocca]

Hi Matthias,

On 2023-11-24 02:29, Matthias Klose wrote:
> please send a test patch, that doesn't turn off this flag by default.

I'm not sure if I understand the question, but with the attached patch
all .o and .a files shipped by libgcc-13-dev have the right BTI, PAC
properties according to readelf -n.

Build logs here for reference:
https://people.debian.org/~ema/gcc-13_13.2.0-7.1_arm64.build

Let me know if this is what you were looking for.

Note that of all files without BTI in the notes section mentioned in
https://bugs.debian.org/1055711#5, libgcc-13-dev ships crtbeginS.o and
crtendS.o. Those are fixed with the proposed patch. The remaining files
(Scrt1.o, crti.o, and crtn.o) are instead installed by libc6-dev. We'll
need to fix them separately in glibc.

Thanks,
  Emanuele
diff -Nru gcc-13-13.2.0/debian/changelog gcc-13-13.2.0/debian/changelog
--- gcc-13-13.2.0/debian/changelog  2023-11-24 11:53:24.0 +0100
+++ gcc-13-13.2.0/debian/changelog  2023-11-27 17:22:11.0 +0100
@@ -1,3 +1,11 @@
+gcc-13 (13.2.0-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add -mbranch-protection=standard to CFLAGS and CXXFLAGS on arm64
+(Closes: #1055711)
+
+ -- Emanuele Rocca   Mon, 27 Nov 2023 17:22:11 +0100
+
 gcc-13 (13.2.0-7) unstable; urgency=medium
 
   * Update to git 20231124 from the gcc-13 branch.
diff -Nru gcc-13-13.2.0/debian/rules2 gcc-13-13.2.0/debian/rules2
--- gcc-13-13.2.0/debian/rules2 2023-10-24 14:39:05.0 +0200
+++ gcc-13-13.2.0/debian/rules2 2023-11-27 17:22:11.0 +0100
@@ -195,6 +195,11 @@
   STAGE1_LDFLAGS   =
 endif
 
+ifeq ($(DEB_TARGET_ARCH),arm64)
+  CFLAGS += -mbranch-protection=standard
+  CXXFLAGS += -mbranch-protection=standard
+endif
+
 # set CFLAGS/LDFLAGS for the configure step only, maybe be modifed for some 
target
 # all other flags are passed to the make step.
 pass_vars = $(foreach v,$(1),$(if $($(v)),$(v)="$($(v))"))

Bug#1057044: xymon: ntpdate no longer supports the -p option

[Carsten Leonhardt]

Package: xymon
Version: 4.3.30-1
Severity: normal
Tags: patch

Dear maintainers,

ntpdate emits a warning when called with the -p option. I've attached a
patch to drop that option from xymonserver.cfg.

If you prefer, I can also commit directly to salsa.

Regards

Carsten

>From 6df3ff8215dd4c3d848f9ec22de3f94d84767a95 Mon Sep 17 00:00:00 2001
From: Carsten Leonhardt 
Date: Tue, 28 Nov 2023 16:15:16 +0100
Subject: [PATCH] xymon: update xymonserver.cfg: ntpdate no longer supports the
 "-p" option (cf. #926877).

---
 debian/changelog | 2 ++
 xymond/etcfiles/xymonserver.cfg.DIST | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index b83b5d6..c440bc8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -34,6 +34,8 @@ xymon (4.3.30-2) UNRELEASED; urgency=medium
   [ Carsten Leonhardt ]
   * Update xymon-client.init: add "reload" to usage message as that is
 supported, too.
+  * xymon: update xymonserver.cfg: ntpdate no longer supports the "-p"
+option.
 
  -- Axel Beckert   Mon, 10 Aug 2020 04:39:28 +0200
 
diff --git a/xymond/etcfiles/xymonserver.cfg.DIST b/xymond/etcfiles/xymonserver.cfg.DIST
index 53ff592..3a9229b 100644
--- a/xymond/etcfiles/xymonserver.cfg.DIST
+++ b/xymond/etcfiles/xymonserver.cfg.DIST
@@ -134,7 +134,7 @@ NONETPAGE=""	# Network tests that go YELLOW upon failure
 FPING="@FPING@"	# Path and options for the ping program.
 FPINGOPTS="-Ae"	# Standard options to fping/xymonping
 NTPDATE="ntpdate"# Path to the 'ntpdate' program
-NTPDATEOPTS="-u -q -p 1"			# Standard options to ntpdate
+NTPDATEOPTS="-u -q"# Standard options to ntpdate
 TRACEROUTE="traceroute" # How to do traceroute on failing ping tests. Requires "trace" in hosts.cfg .
 TRACEROUTEOPTS="-n -q 2 -w 2 -m 15"		# Standard options to traceroute
 XYMONROUTERTEXT="router"			# What to call a failing intermediate network device.
-- 
2.39.2

Bug#1056348: FTBFS: tests fail in clean environment

[Steve McIntyre]

Hey Nicolas!

On Fri, Nov 24, 2023 at 11:26:25AM -0500, Nicolas Mora wrote:
>Hello,
>
>I've forwarded the bug upstream [1] and they made a patch [2].
>
>Can you test their patch on your package, to check if the problem is fixed on
>your CI?
>
>Also, if this works, I suggest to apply their patch rather than yours to make
>the code more consistent with upstream, do you agree?
>
>[1] https://github.com/libssh2/libssh2/issues/1240
>[2] https://github.com/libssh2/libssh2/pull/1241

Thanks, that looks sane enough here! :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"War does not determine who is right - only who is left."
   -- Bertrand Russell

Bug#1057043: RFS: goauthing/2.2.1-1 [ITP] -- CLI authentication utility for srun4000 systems

[陈 晟祺]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian...@lists.debian.org

Dear mentors,

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

* Package name : goauthing
Version : 2.2.1-1
Upstream contact : Yuxiang Zhang 
* URL : https://github.com/z4yx/GoAuthing
* License : GPL-3.0
* Vcs : https://salsa.debian.org/go-team/packages/goauthing
Section : golang

The source builds the following binary packages:

goauthing - CLI authentication utility for srun4000 systems

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

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

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

dget -x 
https://mentors.debian.net/debian/pool/main/g/goauthing/goauthing_2.2.1-1.dsc

Changes for the initial release:

goauthing (2.2.1-1) UNRELEASED; urgency=medium
.
* Initial release (Closes: #1057029)

Regards,
-- 
Shengqi Chen

Bug#1057042: libclojure-java: Please remove dependency on libjsr166y-java

[Miguel Landaeta]

Package: libclojure-java
Severity: normal
User: nomad...@debian.org
Usertags: cleanup

Dear Maintainer,

I think the dependency on libjsr166y-java should be dropped:

https://salsa.debian.org/clojure-team/clojure/-/blob/1c17628638ddee0073c7dfbfa911cd913f708ce1/debian/control#L53

clojure.parallel has been deprecated since several years ago:

https://groups.google.com/g/clojure-dev/c/zjm4eHy9vDE?pli=1

https://github.com/clojure/clojure/blob/master/src/clj/clojure/parallel.clj#L9

The code also provide instructions for anyone who still relies
on that deprecated feature on how to make it work.

I'd like to be able to ask for libjsr166y-java for removal from the
archive at some point in the future, if possible.

Thanks,


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages libclojure-java depends on:
pn  libcore-specs-alpha-clojure  
pn  libjsr166y-java  
pn  libspec-alpha-clojure

libclojure-java recommends no packages.

libclojure-java suggests no packages.

Bug#1054657: Transition issue for r-cran-rstanarm (Was: Bug#1055922: rmatrix: ABI change in Matrix 1.6-2)

[Andreas Tille]

Hi Graham,

Am Tue, Nov 28, 2023 at 09:29:41AM -0100 schrieb Graham Inggs:
> > for tests that run successfully on all architectures where they are
> > triggered (as in, where at least some of the binaries build by the
> > source are installable). As the failure isn't a regression, the
> > migration isn't blocked, though.
> 
> I noticed this today, and added an age hint for r-cran-seurat so it
> should migrate soon.

Thanks a lot for this.
 
> On Mon, 27 Nov 2023 at 23:22, Charles Plessy  wrote:
> > would it be possible to have an estimation about when we can expect to
> > start the Bioconductor transition ?
> 
> We recently announced that britney now considers mips64el to be an
> out-of-sync architecture [1].  We are finding other systems; e.g. UDD
> and BTS, also need changes to accommodate this.  We hope to have this
> resolved and for you to be able to start your transition within the
> next few days.  We don't want to start a big transition and have it
> blocked on missing builds or installability issues on mips64el.

Perfectly understandable.

> On Sun, 26 Nov 2023 at 15:20, Andreas Tille  wrote:
> > I've asked ftpmaster for removal (see bug #1056913) of some architecture
> > builds for r-cran-rstan which is preventing the migration of this
> > package.
> 
> It seems the armel build was retried by someone and it succeeded [2].
> Fixing the riscv64 build (where it built previously) would be nice, as
> riscv64 is aiming to be a release architecture for trixie, but I do
> not see that being a blocker for this transition.

I confirm having all achitectures building would be great, specifically
all 64bit architectures which are potentially used architectures,
thought.  As a general statement I'm personally lacking knowledge and
time to resolve issues like this but try to inform upstream at least.
Actually risc64 is not affected by #1056913 which seems to have resolved
now for all architectures except mips64el which is to be expected.  Thus
I will close the said bug.
 
> > There is another issue for r-cran-rstan which affects a regression
> > for r-cran-projpred for ppc64el architecture[1] which boils down to:
> > ...
> > It seems something on this architecture is broken I can't do anything
> > about.  Could you provide help here?
> 
> It looks like this was also retried and succeeded [3].

Looks good.  So if I understood correctly we are now rather waiting for
some infrastructure issues to start the transition and we should simply
sit-n-wait for the green light, right?

Kind regards
Andreas.
 
> [1] https://lists.debian.org/debian-devel-announce/2023/11/msg5.html
> [2] https://buildd.debian.org/status/package.php?p=r-cran-rstanarm
> [3] https://ci.debian.net/packages/r/r-cran-projpred/testing/ppc64el/
> 
> 

-- 
http://fam-tille.de

Bug#1055112: closed by Debian FTP Masters (reply to Mike Hommey ) (Bug#1055112: fixed in nss 2:3.95-1)

[Simo Sorce]

I can confirm 3.95-1 does fix this specific problem.

On Tue, 2023-11-28 at 04:51 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libnss3 package:
> 
> #1055112: Please backport patch for malformed ECC keys stored permanently in 
> NSSDB (3.94 only)
> 
> It has been closed by Debian FTP Masters  
> (reply to Mike Hommey ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Mike Hommey 
> ) by
> replying to this email.
> 
> 

-- 
Simo Sorce,
DE @ RHEL Crypto Team,
Red Hat, Inc

Bug#1057031: nvme-stas: autopkgtest hanging on s390x

[Olivier Gayot]

Thanks Daniel!

FYI Martin Bélanger (from nvme-stas upstream) will be preparing a 2.3.1
release of nvme-stas. It should contain some of the patches needed so if
we are not in a hurry, we might as well wait for 2.3.1 to be out.

Thanks,
Olivier

On 11/28/23 11:38, Daniel Baumann wrote:
> Hi Olivier,
> 
> thanks you, that is much apperciated. I've been mostly away/VAC the last
> two weeks, but I'll take care about this and the other patch later today.
> 
> Regards,
> Daniel

Bug#1056976: wpasupplicant: after upgrade to 2:2.10-16, wireless connection fails

[Dimitris]

Στις 28/11/23 14:24, ο/η Andrej Shadura έγραψε:

I guess your system hasn’t been usrmerged?
Anyway, this will be fixed in the next upload, thanks for reporting, and sorry 
for the disruption.


yes, you're right, system wasn't usrmerged at the time of the bug 
report, but did usrmerge a few hours later, since more of those 
"usrmerge" bugs started hitting this system yesterday.


not against usrmerge or anything, just it wasn't required by any other 
package i use for decade+, so never thought such a change would break 
things...


anyway,
thanks for your work and the very fast reply/action...

d.

Bug#1029185: AW: Bug#1029185: moreinfo

[Schulz, Reiner]

Hallo Thomas,

yes, we use "alien" to make it and it works.
But ist a manual task we have to watch for, not an magically Repository ;-)

Reiner 


-Ursprüngliche Nachricht-
Von: Thomas Lange  
Gesendet: Dienstag, 28. November 2023 14:16
An: 1029...@bugs.debian.org; 1029185-submit...@bugs.debian.org
Betreff: Bug#1029185: moreinfo

Hi Reiner,

did you tried to convert the .deb to .rpm? Does it work for you?
-- 
 Thomas

Bug#1057041: qtpositioning5-dev_5.15.8%2bdfsg-3_amd64.deb 404 Not Found

[Jason Weisberger]

Package: mirrors

While attempting to install packages to compile a QT5 program on Debian
12, I get the following package error:

#sudo apt update
#sudo apt install qtpositioning5-dev

Err:3 http://deb.debian.org/debian bookworm/main amd64 qtpositioning5-
dev amd64 5.15.8+dfsg-3
  404  Not Found [IP: 199.232.30.132 80]
Fetched 2,896 kB in 0s (6,285 kB/s)
E: Failed to fetch
http://deb.debian.org/debian/pool/main/q/qtlocation-opensource-src/qtpositioning5-dev_5.15.8%2bdfsg-3_amd64.deb
 404  Not Found [IP: 199.232.30.132 80]
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?

I see other versions in the repository, but the version that is
supposedly the most updated one doesn't exist on the server.

Using Linux debian-main 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.1.52-1 (2023-09-07) x86_64 GNU/Linux, libc6 2.36-9+deb12u3

Bug#1033040: AW: Bug#1033040: very simple to create a different format

[Schulz, Reiner]

Hi Thomas,

ok, this is so  simple that I didnt expect it

Reiner


-Ursprüngliche Nachricht-
Von: Thomas Lange  
Gesendet: Dienstag, 28. November 2023 14:05
An: 1033...@bugs.debian.org; 1033040-submit...@bugs.debian.org
Betreff: Bug#1033040: very simple to create a different format

Hi,

if you want to create a .vdi image just call

# fai-diskimage . image.vdi

What else is needed as an example?

-- 
regards Thomas

Bug#1057040: firmware-qcom-soc: please add qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and symlink

[Emanuele Rocca]

Package: firmware-qcom-soc
Version: 20230515-3
Severity: wishlist

Dear Maintainer,

The file qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and its symlink
qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin are needed by the Lenovo
Thinkpad X13s. Please consider adding them to firmware-qcom-soc.

File: qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin
Link: qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin -> 
LENOVO/21BX/audioreach-tplg.bin

Thanks!
  Emanuele

Bug#1029185: moreinfo

[Thomas Lange]

Hi Reiner,

did you tried to convert the .deb to .rpm? Does it work for you?
-- 
 Thomas

Bug#1057034: (no subject)

[William Desportes]

Thank you for opening this bug, this change is already done but not yet 
released.
I marked this as forwarded and will try to send a version soon

--
William

Bug#1057039: firmware-atheros: please ship qca/hpbtfw21.tlv and qca/hpnv21.bin

[Emanuele Rocca]

Package: firmware-atheros
Version: 20230515-3
Severity: wishlist

Dear Maintainer,

The files qca/hpbtfw21.tlv and qca/hpnv21.bin are needed by the Lenovo
Thinkpad X13s. Please consider adding them to firmware-atheros.

Thanks,
  Emanuele

Bug#1057038: bookworm-pu: package php-phpseclib3/3.0.19-1+deb12u1

[David Prévot]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: php-phpsecl...@packages.debian.org, t...@security.debian.org
Control: affects -1 + src:php-phpseclib3

Hi,

Please allow to fix CVE-2023-49316 (#1057008) in the next point release.
I assume from the bug report wording that it isn’t worth a DSA (security
team X-Debbugs-Cced in case I misunderstood).

The changelog refers to a trivial change (gbp.conf and control) for the
build process, and the three line upstream patch (+comments +test) to
fix the issue.

  * Track bookworm
  * Math/BinaryField: fix for excessively large degrees [CVE-2023-49316]
(Closes: #1057008)

It passes its (updated) testsuite, but I didn’t have time to test this
update thoroughly.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

Thanks in advance for your consideration.

Regards,

taffit
diff -Nru php-phpseclib3-3.0.19/debian/changelog php-phpseclib3-3.0.19/debian/changelog
--- php-phpseclib3-3.0.19/debian/changelog	2023-03-06 08:00:12.0 +0100
+++ php-phpseclib3-3.0.19/debian/changelog	2023-11-28 08:33:28.0 +0100
@@ -1,3 +1,11 @@
+php-phpseclib3 (3.0.19-1+deb12u1) bookworm; urgency=medium
+
+  * Track bookworm
+  * Math/BinaryField: fix for excessively large degrees [CVE-2023-49316]
+(Closes: #1057008)
+
+ -- David Prévot   Tue, 28 Nov 2023 08:33:28 +0100
+
 php-phpseclib3 (3.0.19-1) unstable; urgency=medium
 
   [ Alexander Vlasov ]
diff -Nru php-phpseclib3-3.0.19/debian/control php-phpseclib3-3.0.19/debian/control
--- php-phpseclib3-3.0.19/debian/control	2023-03-06 08:00:12.0 +0100
+++ php-phpseclib3-3.0.19/debian/control	2023-11-28 08:32:24.0 +0100
@@ -13,7 +13,7 @@
pkg-php-tools (>= 1.41~)
 Standards-Version: 4.6.2
 Homepage: https://phpseclib.sourceforge.net/
-Vcs-Git: https://salsa.debian.org/php-team/pear/phpseclib.git -b debian/latest
+Vcs-Git: https://salsa.debian.org/php-team/pear/phpseclib.git -b debian/bookworm
 Vcs-Browser: https://salsa.debian.org/php-team/pear/phpseclib
 Rules-Requires-Root: no
 
diff -Nru php-phpseclib3-3.0.19/debian/gbp.conf php-phpseclib3-3.0.19/debian/gbp.conf
--- php-phpseclib3-3.0.19/debian/gbp.conf	2023-03-06 07:51:57.0 +0100
+++ php-phpseclib3-3.0.19/debian/gbp.conf	2023-11-28 08:32:24.0 +0100
@@ -1,5 +1,5 @@
 [DEFAULT]
-debian-branch = debian/latest
+debian-branch = debian/bookworm
 pristine-tar = True
 filter = [ '.gitattributes' ]
 upstream-vcs-tag = %(version%~%-)s
diff -Nru php-phpseclib3-3.0.19/debian/patches/0007-Math-BinaryField-fix-for-excessively-large-degrees.patch php-phpseclib3-3.0.19/debian/patches/0007-Math-BinaryField-fix-for-excessively-large-degrees.patch
--- php-phpseclib3-3.0.19/debian/patches/0007-Math-BinaryField-fix-for-excessively-large-degrees.patch	1970-01-01 01:00:00.0 +0100
+++ php-phpseclib3-3.0.19/debian/patches/0007-Math-BinaryField-fix-for-excessively-large-degrees.patch	2023-11-28 08:32:28.0 +0100
@@ -0,0 +1,56 @@
+From: terrafrost 
+Date: Tue, 21 Nov 2023 19:10:46 -0600
+Subject: Math/BinaryField: fix for excessively large degrees
+
+Origin: backport, https://github.com/phpseclib/phpseclib/commit/964d78101a70305df33f442f5490f0adb3b7e77f
+Bug-Debian: https://bugs.debian.org/1057008
+---
+ phpseclib/Math/BinaryField.php  |  9 +
+ tests/Unit/Crypt/EC/KeyTest.php | 16 
+ 2 files changed, 25 insertions(+)
+
+diff --git a/phpseclib/Math/BinaryField.php b/phpseclib/Math/BinaryField.php
+index 3e21a67..5da8c93 100644
+--- a/phpseclib/Math/BinaryField.php
 b/phpseclib/Math/BinaryField.php
+@@ -48,6 +48,15 @@ class BinaryField extends FiniteField
+ public function __construct(...$indices)
+ {
+ $m = array_shift($indices);
++if ($m > 571) {
++/* sect571r1 and sect571k1 are the largest binary curves that https://www.secg.org/sec2-v2.pdf defines
++   altho theoretically there may be legit reasons to use binary finite fields with larger degrees
++   imposing a limit on the maximum size is both reasonable and precedented. in particular,
++   http://tools.ietf.org/html/rfc4253#section-6.1 (The Secure Shell (SSH) Transport Layer Protocol) says
++   "implementations SHOULD check that the packet length is reasonable in order for the implementation to
++avoid denial of service and/or buffer overflow attacks" */
++throw new \OutOfBoundsException('Degrees larger than 571 are not supported');
++}
+ $val = str_repeat('0', $m) . '1';
+ foreach ($indices as $index) {
+ $val[$index] = '1';
+diff --git a/tests/Unit/Crypt/EC/KeyTest.php b/tests/Unit/Crypt/EC/KeyTest.php
+index f0069a3..f423845 100644
+--- 

Bug#1033040: very simple to create a different format

[Thomas Lange]

Hi,

if you want to create a .vdi image just call

# fai-diskimage . image.vdi

What else is needed as an example?

-- 
regards Thomas

Bug#1039194: not needed

[Thomas Lange]

FYI: Since the next FAI version will move to systemd I will not add an
override.

-- 
 Thomas

Bug#1057036: Lots of embedded copies, including many that are already packaged in Debian

[David Prévot]

Source: ldap-account-manager
Version: 8.5-1
Severity: important
Tags: security
X-Debbugs-Cc: Debian PHP PEAR Maintainers 
, Debian Security Team 


Hi,

Just noticed via #1057008 and especially [CVE-2023-49316] notes, that
ldap-account-manager includes an insane amount of third party package in
(but not only) lib/3rdParty/composer. Many of those are already packaged
and maintained in Debian.

Please consider using (and, if needed, introducing) the proper
dependencies.

CVE-2023-49316: https://security-tracker.debian.org/tracker/CVE-2023-49316

Regards,

taffit


signature.asc
Description: PGP signature

Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

[Vincent Lefevre]

On 2023-11-28 00:17:08 +0100, Preuße, Hilmar wrote:
> The specific file (glyphtounicode.tex) is only read during format
> generation AFAICT.

No, not in the past (before TeX Live 2021 -- my setting was predating
this version). For instance, see

  
https://superuser.com/questions/165073/is-it-possible-to-remove-ligatures-from-copied-text/325396#325396

  https://github.com/latex3/latex2e/issues/465

> So, if we unset the TEXINPUTS variable the fmtutil will again read
> the default and you will loose your custom file.

The custom file was read when pdflatex was run. Things have changed,
both on the TeX Live side and on the Ghostscript side (where bugs
related to the ToUnicode CMap have eventually been fixed -- only
in Debian/unstable for one of them, though, and perhaps backports),
so that I could eventually get rid of glyphtounicode.tex completely.

In any case, package installation must give the same result whether
it comes from of a new installation or a later installation, where
environment variables could be set in /etc/profile or whatever
(this is not specific to TEXINPUTS, but applies to other arbitrary
environment variables as well).

Any config or workaround to bugs must occur at use time (e.g. when
running pdflatex on a .tex file), or by patching & rebuilding a
package.

Note: One may assume that a user would also like to test a local
TeX Live in /opt (possibly with an updated glyphtounicode.tex file),
and TEXINPUTS could be set on purpose in this context. This should
affect only the local installation, not Debian package installation.

Note also that the environment may also affect the build of packages,
and that's why tools like debuild sanitizes the environment. This
should be the case even more for the installation of packages when
needed.

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

Bug#1050383: fix applied

[Thomas Lange]

I've check with the upcoming FAI version, and there the md device
names do start with md0.

I've already added your fix to the git repo.
-- 
regards Thomas

Bug#1056056: linux-image-6.1.0-13-amd64: After a 'warm' reboot the disk is missing (not detected by the bios) on a HP t640

[Ben Mesman | Spark Narrowcasting]

Some searching and some trial and error later I find that adding a "reboot=p" 
to the kernel command line will result in en rebootable system. It looks like 
this system ("HP t640 Thin Client") should be added to the list of boot quirks 
in 'arch/x86/kernel/reboot.c'?

For the record, "c,p", "g,p" and "p" work, all other combinations fail to do a 
functional reboot.

Bug#1055646: gdb: extremely slow response to basic commands

[Héctor Orón Martínez]

Hello tomazzi,

On Sun, 26 Nov 2023 at 19:45, tomazzi  wrote:

> I have found the root cause of this problem:

Thanks very much! This is a very valuable investigation.
I wanted to drop a link to addr2line bug[1], could that be related?

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=29785

> I thought that this BUG should be easy to eliminate - but it turns out
> that there are several serious BUGs in the gdb, and the only way to
> eliminate them is to debug the gdb first ;)

Which several serious bugs? I understand you mean in the upstream GNU
GDB, instead of the Debian GNU GDB package. Are those reported
upstream?

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1056976: wpasupplicant: after upgrade to 2:2.10-16, wireless connection fails

[Andrej Shadura]

Hi,

On Mon, 27 Nov 2023, at 13:52, Dimitris wrote:
> after upgrading to latest version, device wlan0 seems unmanageable by 
> Network-Manager and wireless connection is unusable.

I guess your system hasn’t been usrmerged?
Anyway, this will be fixed in the next upload, thanks for reporting, and sorry 
for the disruption.

-- 
Cheers,
  Andrej

Bug#1029125: Please!

[Barak A. Pearlmutter]

I'm the gmailieer, aka lieer, maintainer.

Yes, please upgrade this!

Lieer is assuming the 2.x version (well, 1.8 or above) of the python
google auth library, with the to_json method. There isn't much I can
do to fix lieer until this package is upgraded.

(See also #1053227)

Bug#1055808: fsck at boot always skipped due to APM_EMULATION kernel option

[hristoph Biedl]

Theodore Ts'o wrote...

> This was behaviour that was requested per Debian bug #205177[1], and
> note that it doesn't skip the checks forever.  It just doubles the
> check interval (so if check interval is 14 days, it will make it be 28
> days), and if the max_mount_count was 20, it will not wait until the
> 40th mount.   So it's not "always skipped"; it's rather deferred.

My perception was otherwise but I shouldn't argue without solid proof.

And yes, I am enabling periodic fsck checks, having experienced
corrupted file systems a few times in the past (rather caused by failure
in the underlying block device than by ext4 itself). Migrating to
e2scrub still is something to consider where possible.

Still, I find an "on battery" message disturbing if there isn't any. So,
if I do (some output stripped):

# fallocate --length 128M /tmp/blob
# mkfs.ext4 /tmp/blob
# tune2fs -c 36 -C 35 /tmp/blob

# cat /proc/apm
1.13 1.2 0x02 0xff 0xff 0xff -1% -1 ?

# e2fsck 1.47.2 (5-Feb-2023)
/tmp/blob: clean, 11/32768 files, 13883/131072 blocks (check deferred; on 
battery)
   
^^

That's why I'd prefer to derive "on battery" from that APM line only if
and only if APM's "AC line status" is "off-line", and otherwise not. But
I'll leave that to you to decide.

All the best,

Christoph


signature.asc
Description: PGP signature

Bug#1054571: devscripts: debootsnap: Missing Recommends on python3-pycurl

[Michael Prokop]

Hi,

* David (Plasma) Paul [Wed Oct 25, 2023 at 11:36:48PM -0500]:
> Package: devscripts
> Version: 2.21.6
> Severity: normal
> 
> Dear Maintainer,
> 
> The devscripts binary package is missing a Recommends on python3-pycurl
> which is a dependency of the debootsnap script.

So in devscripts v2.23.6 we have:

| Depends: dpkg-dev (>= 1.18.19), fakeroot, file, gnupg | gnupg2, gpgv | gpgv2, 
libfile-dirlist-perl, libfile-homedir-perl, libfile-touch-perl, 
libfile-which-perl, libipc-run-perl, libmoo-perl, libwww-perl, patchutils, 
sensible-utils, wdiff, perl:any, python3:any
| Recommends: apt (>= 1.3~pre3), dctrl-tools, dput | dupload, 
libdistro-info-perl, libdpkg-perl, libencode-locale-perl, libgit-wrapper-perl, 
libgitlab-api-v4-perl, libjson-perl, liblist-compare-perl, 
libstring-shellquote-perl, libtry-tiny-perl, liburi-perl, licensecheck, 
lintian, man-db, patch, python3-apt, python3-debian (>= 0.1.15), python3-magic, 
python3-requests, python3-unidiff, python3-xdg, strace, unzip, wget | curl, 
xz-utils, debian-keyring, equivs, liblwp-protocol-https-perl, 
libsoap-lite-perl, pristine-tar
| Suggests: adequate, at, autopkgtest, bls-standalone, bsd-mailx | mailx, 
build-essential, check-all-the-things, cvs-buildpackage, debhelper, diffoscope, 
disorderfs, dose-extra (>= 4.0), duck, elpa-devscripts, faketime, gnuplot, 
how-can-i-help, libauthen-sasl-perl, libdbd-pg-perl, libfile-desktopentry-perl, 
libterm-size-perl, libtimedate-perl, libyaml-syck-perl, mmdebstrap, 
mozilla-devscripts, mutt, piuparts, postgresql-client, pristine-lfs, quilt, 
ratt, reprotest, ssh-client, svn-buildpackage, w3m

And the package description for says:

| - debootsnap: Combines debootstrap and snapshot.debian.org to create a chroot
|   containing exactly the requested selection of packages. This can be used
|   to re-create a chroot from the past, for example to reproduce a bug. The
|   tool is also used by debrebuild to build a package in a chroot with build
|   dependencies in the same version as recorded in the buildinfo file.
|   [apt-utils, dpkg-dev, equivs, mmdebstrap, python3-pycurl]

I can confirm that apt-utils, equivs, mmdebstrap and python3-pycurl,
but also python3-debian and python3-requests seem to be required.

Given that e.g. `equivs` is listed in both Recommends, but also in
the `[...]` section of the debootsnap's description, maybe the list
should be updated to:

  [apt-utils equivs mmdebstrap python3-debian python3-pycurl python3-requests]

?

regards
-mika-


signature.asc
Description: PGP signature

Bug#1057035: Missing Breaks/Replaces / file conflict with ubuntu-cloud-keyring

[Michael Biebl]

Package: ubuntu-keyring
Version: 2023.11.28.1-0.1
Severity: serious


Preparing to unpack .../ubuntu-keyring_2023.11.28.1-0.1_all.deb ...
Unpacking ubuntu-keyring (2023.11.28.1-0.1) over (2020.06.17.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/ubuntu-keyring_2023.11.28.1-0.1_all.deb (--unpack):
 trying to overwrite '/usr/share/keyrings/ubuntu-cloud-keyring.gpg', which is 
also in package ubuntu-cloud-keyring 2020.06.17.1-1
Errors were encountered while processing:
 /var/cache/apt/archives/ubuntu-keyring_2023.11.28.1-0.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



It appears a file was moved without a proper Breaks/Replaces.

Bug#1057034: shunit2: Please mark the package Multi-Arch:foreign, as it's architecture independent

[Lukas Märdian]

Package: shunit2
Version: 2.1.8-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com

Dear Maintainer,

In Ubuntu we have a partial i386 distribution. Autopkgtests of procps:i386
started failing due to the new shunit2 test dependency not being available
on the i386 port.

It turned out shunit2 is actually architecture independent, so should be marked
"Multi-Arch: foreign". This way the shunit2:amd64 binary can be used on the
i386 port (or others).

In Ubuntu, the attached patch was applied to achieve the following:


  * Set 'Multi-Arch: foreign' to satisfy procps:i386 test dependency


Thanks for considering the patch.

Cheers,
  Lukas


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-10-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
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
diff -Nru shunit2-2.1.8/debian/control shunit2-2.1.8/debian/control
--- shunit2-2.1.8/debian/control2022-11-24 13:01:04.0 +0100
+++ shunit2-2.1.8/debian/control2023-11-28 12:32:02.0 +0100
@@ -12,6 +12,7 @@
 
 Package: shunit2
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}
 Description: unit test framework for Bourne based shell scripts
  shUnit2 was originally developed to provide a consistent testing

Bug#1055737: gpodder don't start , claim abandon

[Grand T]

Hello
I Give another try with the two versions available, below what I found in logs

journalctl -xb | grep gpodder
nov. 28 12:20:05 debian sudo[6011]:  guy : TTY=pts/0 ; PWD=/home/guy ; 
USER=root ; COMMAND=/usr/bin/apt install gpodder
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:20:56 debian kernel: __vm_enough_memory: pid: 6721, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:21:22 debian sudo[6743]:  guy : TTY=pts/0 ; PWD=/home/guy ; 
USER=root ; COMMAND=/usr/bin/apt purge gpodder
nov. 28 12:21:55 debian sudo[7708]:  guy : TTY=pts/0 ; PWD=/home/guy ; 
USER=root ; COMMAND=/usr/bin/apt install gpodder/stable
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:31 debian kernel: __vm_enough_memory: pid: 8403, comm: gpodder, 
no enough memory for the allocation
nov. 28 12:22:37 debian sudo[8424]:  guy : TTY=pts/0 ; PWD=/home/guy ; 
USER=root ; COMMAND=/usr/bin/apt purge gpodder


it remains 1,5 G in my home:

df -hT
Sys. de fichiers Type Taille Utilisé Dispo Uti% Monté sur
udev devtmpfs   1,8G   0  1,8G   0% /dev
tmpfstmpfs  366M2,1M  364M   1% /run
/dev/sda1ext419G 15G  3,3G  82% /
tmpfstmpfs  1,8G 75M  1,8G   5% /dev/shm
tmpfstmpfs  5,0M8,0K  5,0M   1% /run/lock
tmpfstmpfs  1,1G 57M  1,1G   6% /tmp
/dev/sda6ext4   268G253G  1,5G 100% /home
tmpfstmpfs  366M 84K  366M   1% /run/user/1001

free -mht
   total   utilisé  libre partagé tamp/cache   
disponible
Mem:   3,6Gi   1,8Gi   493Mi   145Mi   1,6Gi   1,7Gi
Échange:   7,7Gi   256Ki   7,7Gi
Total:  11Gi   1,8Gi   8,2Gi




By the way everything else is working on this Pc

Bug#1056151: systemd will be used in the future

[Thomas Lange]

Hi Mika,

the additional test before calling fai-divert was added because in
the next FAI release, we will move from sysv to systemd by default.

I think I will not drop the code for sysv support immediately.

-- 
viele Grüße Thomas

Bug#1057033: nemo: Several MIME types not recognized on GVFS mounted volumes

[Andreas Heinlein]

Package: nemo
Version: 4.8.6-2
Severity: normal
X-Debbugs-Cc: aheinl...@gmx.com

Nemo fails to recognize several MIME types, namely *.pgp 
(application/pgp-encrypted) and *.doc (application/msword) when the files
reside on a network drive mounted with GVFS (SMB share on NAS). Instead it
shows "application/octet-stream" and doesn't know how to open it when
double-clicking it. When copying the files over to a local drive,
the MIME type is recognized correctly. Other files types, e.g. PDF or ODT,
work as expected.

Problem also occurs in Debian bookworm, but does not occur in latest Linux
Mint with Nemo 5.8.4. Problem does *not* occur with nautilus, so I guess it
is not a GNOME thing.


-- System Information:
Debian Release: 11.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-26-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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

Versions of packages nemo depends on:
ii  cinnamon-desktop-data  4.8.1-2
ii  desktop-file-utils 0.26-1
ii  gsettings-desktop-schemas  3.38.0-2
ii  gvfs   1.46.2-1
ii  libatk1.0-02.36.0-2
ii  libc6  2.31-13+deb11u7
ii  libcairo-gobject2  1.16.0-5
ii  libcairo2  1.16.0-5
ii  libcinnamon-desktop4   4.8.1-2
ii  libexempi8 2.5.2-1
ii  libexif12  0.6.22-3
ii  libgail-3-03.24.24-4+deb11u3
ii  libgdk-pixbuf-2.0-02.42.2+dfsg-1+deb11u1
ii  libglib2.0-0   2.66.8-1
ii  libglib2.0-data2.66.8-1
ii  libgtk-3-0 3.24.24-4+deb11u3
ii  libnemo-extension1 4.8.6-2
ii  libnotify4 0.7.9-3
ii  libpango-1.0-0 1.46.2-3
ii  libpangocairo-1.0-01.46.2-3
ii  libselinux13.1-3
ii  libx11-6   2:1.7.2-1+deb11u2
ii  libxapp1   2.0.7-1
ii  libxml22.9.10+dfsg-6.7+deb11u4
ii  nemo-data  4.8.6-2
ii  shared-mime-info   2.0-1

Versions of packages nemo recommends:
ii  cinnamon-l10n4.8.3-1
ii  gvfs-backends1.46.2-1
ii  gvfs-fuse1.46.2-1
ii  librsvg2-common  2.50.3+dfsg-1+deb11u1
ii  nemo-fileroller  4.8.0-1

Versions of packages nemo suggests:
ii  eog  3.38.2-1
ii  evince [pdf-viewer]  3.38.2-1
ii  okular [pdf-viewer]  4:20.12.3-2
ii  totem3.38.0-2
ii  vlc [mp3-decoder]3.0.20-0+deb11u1
ii  xdg-user-dirs0.17-2

-- no debconf information

Bug#1056957: [INTL:sv] Swedish strings for glibc debconf

[Anders Jonsson]

Hi Martin,
this fixes a typo (Debain->Debian). Furthermore poedit errored out when 
opening the file, I've changed the language code to sv (from "Swedish") 
which seems to do the trick.



Regards,
Anders# Translation of glibc debconf template to Swedish
# Copyright (C) 2023 Martin Bagge 
# This file is distributed under the same license as the glibc package.
#
# Martin Bagge , 2008, 2011, 2014, 2023
msgid ""
msgstr ""
"Project-Id-Version: glibc_2.7-11_sv\n"
"Report-Msgid-Bugs-To: gl...@packages.debian.org\n"
"POT-Creation-Date: 2023-01-03 21:34+0100\n"
"PO-Revision-Date: 2023-11-27 09:01+0100\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: multiselect
#. Choices
#: ../debhelper.in/locales.templates:1001
msgid "All locales"
msgstr "Alla lokalanpassningar"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid "Locales to be generated:"
msgstr "Lokalanpassningar att generera:"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Locales are a framework to switch between multiple languages and allow users "
"to use their language, country, characters, collation order, etc."
msgstr ""
"Lokalanpassning (locale) är ett ramverk för att växla mellan flera språk för "
"att låta användare använda sitt språk, land, tecken och sorteringsordning, "
"etc."

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Please choose which locales to generate. UTF-8 locales should be chosen by "
"default, particularly for new installations. Other character sets may be "
"useful for backwards compatibility with older systems and software."
msgstr ""
"Välj vilka lokalanpassningar som ska genereras. UTF-8-lokaler bör väljas som "
"standard, speciellt för nya installationer. Andra teckenuppsättningar kan "
"vara användbara för bakåtkompatibilitet med äldre system och programvara."

#. Type: select
#. Choices
#: ../debhelper.in/locales.templates:2001
msgid "None"
msgstr "Ingen"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid "Default locale for the system environment:"
msgstr "Välj lokalanpassning som ska vara standard i systemet:"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"Many packages in Debian use locales to display text in the correct language "
"for the user. You can choose a default locale for the system from the "
"generated locales."
msgstr ""
"Många paket i Debian använder lokalanpassningar för att visa text i det "
"korrekta språket för användaren. Du kan välja en standardlokal för systemet "
"från de genererade lokalerna."

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"This will select the default language for the entire system. If this system "
"is a multi-user system where not all users are able to speak the default "
"language, they will experience difficulties."
msgstr ""
"Detta kommer att välja standardspråket för hela systemet. Om du kör ett "
"system med flera användare där inte alla talar det valda språket, kan de få "
"problem."

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid "Do you want to upgrade glibc now?"
msgstr "Vill du uppgradera glibc nu?"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"Running services and programs that are using NSS need to be restarted, "
"otherwise they might not be able to do lookup or authentication any more. "
"The installation process is able to restart some services (such as ssh or "
"telnetd), but other programs cannot be restarted automatically. One such "
"program that needs manual stopping and restart after the glibc upgrade by "
"yourself is xdm - because automatic restart might disconnect your active X11 "
"sessions."
msgstr ""
"Körande tjänster och program som använder NSS behöver startas om, annars "
"kanske de inte kan köra uppslag eller autentisering längre. Installationen "
"kan starta om några tjänster (ex. ssh och telnetd), andra program kan inte "
"startas om automatiskt - xdm är ett sådant program som du måste starta om "
"själv eftersom det skulle starta om din X-session."

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"This script detected the following installed services which must be stopped "
"before the upgrade: ${services}"
msgstr ""
"Skriptet hittade följande installerade tjänster som måste stoppas före "
"uppgraderingen: ${services}"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"If you want to interrupt the upgrade now and continue later, please answer "
"No to the question below."
msgstr ""
"Om du vill avbryta uppgraderingen nu och fortsätta senare anger du Nej på "
"frågan nedan."

#. Type: string
#. Description
#: ../debhelper.in/libc.templates:2001
msgid 

Bug#1056957: [INTL:sv] Swedish strings for openldap debconf

[Anders Jonsson]

Hi Martin,
I did one small typo fix (instllationen->installationen).

Regards,
Anders# Translation of openldap debconf template to Swedish
# Copyright (C) 2023 Martin Bagge 
# This file is distributed under the same license as the openldap package.
#
# Martin Ågren , 2008.
# Martin Bagge , 2010, 2017, 2023
msgid ""
msgstr ""
"Project-Id-Version: openldap_2.4.10-2_sv\n"
"Report-Msgid-Bugs-To: openl...@packages.debian.org\n"
"POT-Creation-Date: 2021-08-16 01:12+\n"
"PO-Revision-Date: 2023-11-27 09:37+0100\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: boolean
#. Description
#: ../slapd.templates:1001
msgid "Omit OpenLDAP server configuration?"
msgstr "Utelämna konfiguration av OpenLDAP-servern?"

#. Type: boolean
#. Description
#: ../slapd.templates:1001
msgid ""
"If you enable this option, no initial configuration or database will be "
"created for you."
msgstr ""
"Om du aktiverar det här alternativet kommer ingen initial konfiguration "
"eller databas att skapas åt dig."

#. Type: select
#. Choices
#: ../slapd.templates:2001
msgid "always"
msgstr "alltid "

#. Type: select
#. Choices
#: ../slapd.templates:2001
msgid "when needed"
msgstr "vid behov"

#. Type: select
#. Choices
#: ../slapd.templates:2001
msgid "never"
msgstr "aldrig"

#. Type: select
#. Description
#: ../slapd.templates:2002
msgid "Dump databases to file on upgrade:"
msgstr "Dumpa databaser till fil vid uppgradering:"

#. Type: select
#. Description
#: ../slapd.templates:2002
msgid ""
"Before upgrading to a new version of the OpenLDAP server, the data from your "
"LDAP directories can be dumped into plain text files in the standard LDAP "
"Data Interchange Format."
msgstr ""
"Innan du uppgraderar till en ny version av OpenLDAP-servern, kan datat från "
"dina LDAP-kataloger dumpas till klartextfiler i standardformatet LDAP Data "
"Interchange Format."

#. Type: select
#. Description
#: ../slapd.templates:2002
msgid ""
"Selecting \"always\" will cause the databases to be dumped unconditionally "
"before an upgrade. Selecting \"when needed\" will only dump the database if "
"the new version is incompatible with the old database format and it needs to "
"be reimported. If you select \"never\", no dump will be done."
msgstr ""
"Väljer du \"alltid\" kommer databaserna alltid att dumpas före en "
"uppgradering. Väljer du \"vid behov\" kommer databasen bara dumpas om den "
"nya versionen är inkompatibel med det gamla databasformatet och måste "
"återimporteras. Om du väljer \"aldrig\", kommer ingen dump göras."

#. Type: string
#. Description
#: ../slapd.templates:3001
msgid "Directory to use for dumped databases:"
msgstr "Katalog att dumpa databaser i:"

#. Type: string
#. Description
#: ../slapd.templates:3001
msgid ""
"Please specify the directory where the LDAP databases will be exported. In "
"this directory, several LDIF files will be created which correspond to the "
"search bases located on the server. Make sure you have enough free space on "
"the partition where the directory is located. The first occurrence of the "
"string \"VERSION\" is replaced with the server version you are upgrading "
"from."
msgstr ""
"Ange den katalog dit LDAP-databaser ska exporteras. I denna katalog kommer "
"flera LDIF-filer att skapas som svarar mot sökbaserna på servern. Se till "
"att du har tillräckligt med ledigt utrymme på den partition där katalogen "
"finns. Den första förekomsten av strängen \"VERSION\" ersätts med den "
"serverversion du uppgraderar från."

#. Type: boolean
#. Description
#: ../slapd.templates:4001
msgid "Move old database?"
msgstr "Flytta gammal databas?"

#. Type: boolean
#. Description
#: ../slapd.templates:4001
msgid ""
"There are still files in /var/lib/ldap which will probably break the "
"configuration process. If you enable this option, the maintainer scripts "
"will move the old database files out of the way before creating a new "
"database."
msgstr ""
"Det finns fortfarande filer i /var/lib/ldap/ som troligen kommer göra att "
"konfigurationsprocessen inte fungerar. Om du aktiverar detta val, kommer "
"administrationsskripten att flytta den gamla databasfilen ur vägen innan en "
"ny databas skapas."

#. Type: boolean
#. Description
#: ../slapd.templates:5001
msgid "Retry configuration?"
msgstr "Försöka konfigurera igen?"

#. Type: boolean
#. Description
#: ../slapd.templates:5001
msgid ""
"The configuration you entered is invalid. Make sure that the DNS domain name "
"is syntactically valid, the field for the organization is not left empty and "
"the admin passwords match. If you decide not to retry the configuration the "
"LDAP server will not be set up. Run 'dpkg-reconfigure slapd' if you want to "
"retry later."
msgstr ""
"Konfigurationen du angav är ogiltig. Säkerställ att DNS-domännamnet är "
"syntaktiskt 

Bug#1056956: [INTL:sv] Swedish strings for msmtp debconf

[Anders Jonsson]

Hi Martin,
this fixes some typos (itne -> inte), (onte-> inte).

Regards,
Anders# Translation of msmtp debconf template to Swedish
# Copyright (C) 2023 Martin Bagge 
# This file is distributed under the same license as the msmtp package.
#
# Martin Bagge , 2008, 2023
msgid ""
msgstr ""
"Project-Id-Version: msmtp\n"
"Report-Msgid-Bugs-To: ms...@packages.debian.org\n"
"POT-Creation-Date: 2022-10-27 23:33+\n"
"PO-Revision-Date: 2023-11-27 09:27+0100\n"
"Last-Translator: Martin Bagge \n"
"Language-Team: swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../msmtp.templates:1001
msgid "Enable AppArmor support?"
msgstr "Aktivera AppArmor-stöd?"

#. Type: boolean
#. Description
#: ../msmtp.templates:1001
msgid ""
" Apparmor is a kernel security mechanism to restrict programs capabilities\n"
" with per-program profiles.\n"
" .\n"
" The AppArmor profile for msmtp covers a lot of common usecases but there "
"are\n"
" still corner cases with some options which breaks msmtp with "
"incomprehensible\n"
" permissions denied errors."
msgstr ""
"AppArmor är en säkerhetsfunktion i kärnan som begränsar programmens "
"möjligheter genom att sätta unika profiler för att beskriva vad varje "
"program får göra och inte göra.\n"
"\n"
"AppArmor-profilen för msmtp omfattar de flesta vanliga användningsområdena "
"men det finns områden där msmtp kan verkar trasigt genom att visa oväntade "
"eller märkliga felmeddelanden i och med detta."

#. Type: error
#. Description
#: ../msmtp.templates:2001
msgid "Remove SetGID bit on msmtp"
msgstr "SetGID-biten borttagen från msmtp"

#. Type: error
#. Description
#: ../msmtp.templates:2001
msgid ""
" Starting from version 1.8.22, msmtp will no longer be SetGID. Hence the\n"
" creation of the system-wide configuration (/etc/msmtprc) using debconf is\n"
" removed.\n"
" .\n"
" From one side, using the system wide configuration implied msmtp to be "
"SetGID\n"
" but recent security hardening changes in GLib prevent SetGID binaries "
"built\n"
" against libsecret to talk to the D-Bus session, and therefore prevent it "
"from\n"
" being able to retrieve passwords from gnome-keyring or KWallet.\n"
" .\n"
" On another side, it was easy for a local user to obtain the credentials\n"
" stored in /etc/msmtprc even if the file was not readable for this user "
"when\n"
" msmtp was SetGid.\n"
" .\n"
" More information in the following bug reports:\n"
"   - https://bugs.debian.org/944188\n;
"   - https://bugs.debian.org/995012;
msgstr ""
"Från och med version 1.8.22 av msmtp så är inte längre SetGID-biten aktiv. "
"Detta innebär att den systemomfattande inställningsfilen (/etc/msmtprc) inte "
"kan redigeras med debconf och därmed tas bort.\n"
"\n"
"Å ena sidan betyder systemomfattande inställningsfil att SetGID borde vara "
"aktivt men säkerhetsarbetet i GLib har lett till att binärer med SetGID inte "
"kan byggas som beroenden mot libsecret för att därigenom prata med D-bus-"
"sessioner. Och detta leder i sin tur att de inte kan läsa lösenord från "
"gnome-keyring och KWallet.\n"
"\n"
"Å andra sidan var det väldigt enkelt för en lokal användare att hämta "
"lösenord från /etc/msmtprc även om den inte kunde läsa filen när msmtp hade "
"SetGID-biten satt.\n"
"\n"
"Närmare information denna ändring finns i felspårningssystemet:\n"
" - https://bugs.debian.org/944188\n;
" - https://bugs.debian.org/995012;

Bug#1057031: nvme-stas: autopkgtest hanging on s390x

[Daniel Baumann]

Hi Olivier,

thanks you, that is much apperciated. I've been mostly away/VAC the last
two weeks, but I'll take care about this and the other patch later today.

Regards,
Daniel

Bug#960062:

[Miriam Espana Acebal]

Hi,

I'm working on this package on Ubuntu, to promote it from universe to main.
I saw this bug, and it could be a blocker for that process. Reading the
changes files,
the following entry seems to be related (per the comments on
upstream's issue [1] too):

 1.947 2020-05-09 14:30:06-04:00 America/New_York (TRIAL RELEASE)
- add $Email::MIME::MAX_DEPTH and refuse to parse deeper than that
many
  parts; current default: 10

Do you know, as maintainers, if this bug is fixed with that?  One of the
reviewers already asked upstream [1] to see if we can get a confirmation
from there.

Any clue is highly appreciated... thanks in advance.

Miriam (mirespace)

[1] *https://github.com/rjbs/Email-MIME/issues/66
 *
-- 
Miriam España Acebal
Software Engineer II - Ubuntu PublicCloud/Server
Canonical Ltd.