Bug#1036041: upgrade-reports: Dell XPS 9550 fails to boot after bullseye to bookworm upgrade - grub/bios interaction bug?

[Jens Yllman]

Hi,

This seems to have happened to me too. But I just upgraded my Debian 
unstable around the 5th of May and got a grub update. After the upgrade 
I could not boot into Debian again. When I tried it just failed into 
memory check and reboot.


I have an Dell XPS 15 9560.

Setting GRUB_TERMINAL=console and running grub-install and update-grub 
got the system up and running again.


Jens

Bug#1035450: mcpl: diff for NMU version 1.3.2-3.1

[Andreas Metzler]

Control: tags 1035450 + patch
Control: tags 1035450 + pending

Dear maintainer,

I've prepared an NMU for mcpl (versioned as 1.3.2-3.1) and
uploaded it to DELAYED/1.
kind regards

Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru mcpl-1.3.2/debian/changelog mcpl-1.3.2/debian/changelog
--- mcpl-1.3.2/debian/changelog	2022-02-16 20:32:02.0 +0100
+++ mcpl-1.3.2/debian/changelog	2023-05-20 06:57:53.0 +0200
@@ -1,3 +1,11 @@
+mcpl (1.3.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libmcpl-dev: missing Depends on runtime library packages.
+Closes: #1035450
+
+ -- Andreas Metzler   Sat, 20 May 2023 06:57:53 +0200
+
 mcpl (1.3.2-3) unstable; urgency=medium
 
   * Source-only upload for migration to testing.
diff -Nru mcpl-1.3.2/debian/control mcpl-1.3.2/debian/control
--- mcpl-1.3.2/debian/control	2022-02-01 17:32:55.0 +0100
+++ mcpl-1.3.2/debian/control	2023-05-20 06:57:26.0 +0200
@@ -21,7 +21,10 @@
 
 Package: libmcpl-dev
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: libmcpl1 (= ${binary:Version}),
+ libphitsmcpl1 (= ${binary:Version}),
+ libsswmcpl1 (= ${binary:Version}),
+ ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
 Description: Monte Carlo Particle Lists - development files
  This package includes the shared library for reading and writing
  *.mcpl files, a binary format with lists of particle state


signature.asc
Description: PGP signature

Bug#1036369: ruby-rest-client: network-dependent tests fail

[Vignesh Raman]

Package: ruby-rest-client
Version: 2.1.0-3
Severity: normal
Tags: patch
X-Debbugs-Cc: vignesh.ra...@collabora.com

Dear Maintainer,

ruby-rest-client is failing to build because its test suite
depends on access to the internet,

Failures:
RestClient::Request timeouts raises OpenTimeout when it hits an open timeout
   Failure/Error:
 expect { request.execute }.to(
   raise_error(RestClient::Exceptions::OpenTimeout))
 expected RestClient::Exceptions::OpenTimeout, got # with backtrace:

Already some network tests are disabled. Disable the other network
tests which requires access to internet.

Please find the patch for this issue. Thanks.

Regards,
Vignesh

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

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

Versions of packages ruby-rest-client depends on:
ii  ruby  1:3.1
ii  ruby-http-accept  2.2.0-1
ii  ruby-http-cookie  1.0.5-1
ii  ruby-mime-types   3.4.1-2
ii  ruby-netrc0.11.0-4

ruby-rest-client recommends no packages.

ruby-rest-client suggests no packages.

-- no debconf information
>From 6e93dafa17821dde2f7ae5971bbd6d4597304251 Mon Sep 17 00:00:00 2001
From: Vignesh Raman 
Date: Fri, 5 May 2023 17:56:16 +0530
Subject: [PATCH] Disable network-dependent tests

ruby-rest-client is failing to build because its test suite
depends on access to the internet,

Failures:
RestClient::Request timeouts raises OpenTimeout when it hits an open timeout
   Failure/Error:
 expect { request.execute }.to(
   raise_error(RestClient::Exceptions::OpenTimeout))
 expected RestClient::Exceptions::OpenTimeout, got # with backtrace:

Already some network tests are disabled. Disable the other network
tests which requires access to internet.

Signed-off-by: Vignesh Raman 
---
 spec/integration/request_spec.rb | 11 +--
 1 file changed, 1 insertion(+), 10 deletions(-)

diff --git a/spec/integration/request_spec.rb b/spec/integration/request_spec.rb
index 35552fd..3f0aa54 100644
--- a/spec/integration/request_spec.rb
+++ b/spec/integration/request_spec.rb
@@ -14,16 +14,7 @@ describe RestClient::Request do
   end
 
   describe "timeouts" do
-it "raises OpenTimeout when it hits an open timeout" do
-  request = RestClient::Request.new(
-:method => :get,
-:url => 'http://www.mozilla.org',
-:open_timeout => 1e-10,
-  )
-  expect { request.execute }.to(
-raise_error(RestClient::Exceptions::OpenTimeout))
-end
-
+# all removed; accessing the network
   end
 
 end
-- 
2.30.2

Bug#1036368: ITP: libjs-elasticlunr-js -- Lightweight full-text search engine written in JavaScript

[Zixing Liu]

Package: wnpp
Severity: wishlist
Owner: Zixing Liu 
X-Debbugs-Cc: debian-de...@lists.debian.org, zixing@canonical.com

* Package name: libjs-elasticlunr-js
  Version : 1.0.1
  Upstream Contact: Robert Isaac 
* URL : https://www.npmjs.com/package/elasticlunrjs
* License : MIT
  Programming Lang: JavaScript
  Description : Lightweight full-text search engine written in JavaScript

This package will be needed for rustc where the documentation have a
web-browser-based search system to effectively search through the
documentation.

In Debian, currently the search script is stripped (see:
https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/patches/d-0002-mdbook-strip-embedded-libs.patch#L322).
By packaging the missing packages, we could restore the searching system
and providing a better documentation reading/searching experience for the Rust
developers who use Debian.

The package may be maintained by the Debian Javascript Maintainers.
The sponsorship is needed for the initial upload.

Bug#1036304: guix: /etc/profile.d/guix.sh not updated for 1.4.0

[Philip McGrath]

On Friday, May 19, 2023 5:58:06 PM EDT Vagrant Cascadian wrote:
> On 2023-05-18, Philip McGrath wrote:
> > Among other changes upstream, I changed it in
> > 23aafc800c9e678662766440916449ec5bbce830 to initialize various XDG
> > environment variables, fixing a bug that can prevent KDE Plasma sessions
> > from starting properly, instead leaving the user with a black screen. I
> > encountered that bug again today when I logged back in after running
> > `guix home reconfigure` for the first time on a new Bookworm
> > installation. I described the problem in more detail upstream in
> > https://issues.guix.gnu.org/56050 and the linked mailing- list thread.
> 
> This sounds suspiciously similar to a long outstanding debian bug:
> 
>   https://bugs.debian.org/988260
> 
> So if updating this would solve that, that is really promising!
> 

I saw that debian bug when reporting this, and I haven't read it very closely, 
but it reminded me of a problem I had caused by an unnecessarily propagated 
input to emacs-next-pgtk: https://issues.guix.gnu.org/57421 My patch hasn't 
been merged upstream, but I make the same change to in my home-
configuration.scm.

> > Note also that the file was renamed to zzz-guix.sh in
> > 93be56a3ab28ed0a482f354b7f536681c99b6999.
> 
> Hrm. that will be a little bit trickier to change...
> 

IMO that change seems less important, since at least my bookworm system 
doesn't have the /etc/profile.d/xdg_dirs_desktop_session.sh mentioned in the 
commit message. Updating guix.sh without renaming was enough to fix things for 
me.

> 
> It is, unfortunately, very late in the bookworm release cycle... might
> have to wait till bookworm's first point release... will see how
> invasive the changes are.
> 

Understandable—late enough that I'm installing it on my desktop! Thanks for 
taking a look.
Philip




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

Bug#1035458: libtorch-dev: broken symlinks: /usr/lib/x86_64-linux-gnu/libcaffe2_*.so -> libcaffe2_*.so.1.13

[M. Zhou]

Control: severity -1 important
Control: fixed -1 1.13.1+dfsg-5

I believe these symlinks were deprecated already. These symlinks are removed in 
1.13.1+dfsg-5 (experimental).
I'm not able to prepare a 1.13.1+dfsg-4.1 release to only remove these symlinks 
within a short time... too busy lately.
So just downgrading the severity as it is not expected to harm any 
functionality.

Bug#1023585: lists.debian.org: create debian-loongarch: for new port loong64 (LoongArch 64 bits little-endian)

[sense M]

Dear Maintainer:


 Thank you for reading, Have a nice day.
 I'm a 10-year Debian user，and Debian is so stable, and supports
multiple architectures。As a hobbyist, I currently have a
Loongson-3A5000 machine running loongnix which derived from debian 10,
I feels very convenient. I've also been following loongarch's debian
port progress . I really very much hope you can help open the mailing
list, thank you!

Bug#965236: libreoffice: PDF export fails to embed © notices and licence terms of embedded subset fonts

[Thorsten Glaser]

Package: libreoffice-writer
Version: 1:7.0.4-4+deb11u6
Followup-For: Bug #965236
X-Debbugs-Cc: t...@mirbsd.de

This is still pertinent (tested by extracting the font with
mutool then loading the resulting .pfa in FontForge).


-- Package-specific info:

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

Kernel: Linux 5.10.0-22-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libreoffice-writer depends on:
ii  libabw-0.1-1 0.1.3-1
ii  libc62.31-13+deb11u6
ii  libe-book-0.1-1  0.1.3-2
ii  libepubgen-0.1-1 0.1.1-1
ii  libetonyek-0.1-1 0.1.9-4
ii  libgcc-s110.2.1-6
ii  libicu67 67.1-7
ii  libmwaw-0.3-30.3.17-1
ii  libodfgen-0.1-1  0.1.8-2
ii  libreoffice-base-core1:7.0.4-4+deb11u6
ii  libreoffice-common   1:7.0.4-4+deb11u6
ii  libreoffice-core 1:7.0.4-4+deb11u6
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.7-1
ii  libstdc++6   10.2.1-6
ii  libuno-cppu3 1:7.0.4-4+deb11u6
ii  libuno-cppuhelpergcc3-3  1:7.0.4-4+deb11u6
ii  libuno-sal3  1:7.0.4-4+deb11u6
ii  libuno-salhelpergcc3-3   1:7.0.4-4+deb11u6
ii  libwpd-0.10-10   0.10.3-1
ii  libwpg-0.3-3 0.3.3-1
ii  libwps-0.4-4 0.4.12-1
ii  libxml2  2.9.10+dfsg-6.7+deb11u4
ii  ucf  3.0043
ii  uno-libs-private 1:7.0.4-4+deb11u6
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages libreoffice-writer recommends:
pn  libreoffice-math  

Versions of packages libreoffice-writer suggests:
pn  default-jre | java8-runtime | jre  
pn  fonts-crosextra-caladea
pn  fonts-crosextra-carlito
pn  libreoffice-base   
pn  libreoffice-java-common

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-4.2
ii  fonts-opensymbol2:102.11+LibO7.0.4-4+deb11u6
ii  libboost-locale1.74.0   1.74.0-9
ii  libc6   2.31-13+deb11u6
ii  libcairo2   1.16.0-5
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1+b1
ii  libclucene-core1v5  2.3.3.4+dfsg-1+b1
ii  libcmis-0.5-5v5 0.5.2-3
ii  libcups22.3.3op2-3+deb11u2
ii  libcurl3-gnutls 7.74.0-1.3+deb11u7
ii  libdbus-1-3 1.12.24-0+deb11u1
ii  libdconf1   0.38.0-2
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.5-1
ii  libexpat1   2.2.10-2+deb11u5
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1+deb11u1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libgpgmepp6 1.14.0-1+b2
ii  libgraphite2-3  1.3.14-1
ii  libgstreamer-plugins-base1.0-0  1.18.4-2
ii  libgstreamer1.0-0   1.18.4-2.1
ii  libharfbuzz-icu02.7.4-1
ii  libharfbuzz0b   2.7.4-1
ii  libhunspell-1.7-0   1.7.0-3
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.10-1
ii  libicu6767.1-7
ii  libjpeg62-turbo 1:2.0.6-4
ii  liblcms2-2  2.12~rc1-2
ii  libldap-2.4-2   2.4.57+dfsg-3+deb11u1
ii  libmythes-1.2-0 2:1.2.4-3+b1
ii  libneon27-gnutls0.31.2-1
ii  libnspr42:4.29-1
ii  libnss3 2:3.61-1+deb11u3
ii  libnumbertext-1.0-0 1.0.7-1
ii  liborcus-0.16-0 0.16.1-3+b2
ii  liborcus-parser-0.16-0  0.16.1-3+b2
ii  libpng16-16 1.6.37-3
ii  libpoppler102   20.09.0-3.1+deb11u1
ii  libqrcodegencpp11.6.0-1
ii  libraptor2-02.0.14-1.2
ii  librdf0 1.0.17-1.1+b1
ii  libreoffice-common  1:7.0.4-4+deb11u6
ii  librevenge-0.0-00.0.4-6+b1
ii  libsm6  2:1.2.3-1
ii  libstdc++6  10.2.1-6
ii  libuno-cppu31:7.0.4-4+deb11u6
ii  libuno-cppuhelpergcc3-3 1:7.0.4-4+deb11u6
ii  libuno-sal3 1:7.0.4-4+deb11u6
ii  libuno-salhelpergcc3-3  1:7.0.4-4+deb11u6
ii  libx11-62:1.7.2-1
ii  libx11-xcb1 2:1.7.2-1
ii  libxext62:1.3.3-1.1
ii  libxinerama12:1.1.4-2
ii  libxml2  

Bug#1036367: gcc-13: reproducible builds: build date and timestamps embedded in documentation

[Vagrant Cascadian]

Source: gcc-13
Version: 13.1.0-2
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build dates and timestamps are embedded in various files shipped in
documentation.

The attached patches fix this by adding SOURCE_DATE_EPOCH support to the
doxygen scripts used to generate the libstdc++ documentation, and by
adjusting debian/rules2 to remove the leftover _formulas.log files from
the generated package.

According to my local tests, applying these patches should allow gcc-13
to build reproducibly with stable build paths and
DEB_BUILD_OPTIONS="nocheck nolto nopgo".


Thanks for maintaining gcc-13!


live well,
  vagrant
From 41780dfa54abbc7a1d6a1acd744d725b3799eb50 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 30 Apr 2023 14:37:31 -0700
Subject: [PATCH 1/2] Patch libstdc++ to support SOURCE_DATE_EPOCH in
 documentation.

https://reproducible-builds.org/docs/source-date-epoch/
---
 ...ripts-run_doxygen-support-SOURCE_DATE_EPOCH.diff | 13 +
 debian/rules.patch  |  1 +
 2 files changed, 14 insertions(+)
 create mode 100644 debian/patches/libstdc++-scripts-run_doxygen-support-SOURCE_DATE_EPOCH.diff

diff --git a/debian/patches/libstdc++-scripts-run_doxygen-support-SOURCE_DATE_EPOCH.diff b/debian/patches/libstdc++-scripts-run_doxygen-support-SOURCE_DATE_EPOCH.diff
new file mode 100644
index 000..1636c08
--- /dev/null
+++ b/debian/patches/libstdc++-scripts-run_doxygen-support-SOURCE_DATE_EPOCH.diff
@@ -0,0 +1,13 @@
+--- gcc-13.1.0/src/libstdc++-v3/scripts/run_doxygen	2023-04-26 00:09:43.0 -0700
 gcc-13.1.0/src/libstdc++-v3/scripts/run_doxygen.new	2023-04-30 14:34:47.513318389 -0700
+@@ -130,7 +130,9 @@
+ latex_cmd=
+ enabled_sections=
+ generate_tagfile=
+-DATEtext=`date '+%Y-%m-%d'`
++DATE_FMT="+%Y-%m-%d"
++SOURCE_DATE_EPOCH="${SOURCE_DATE_EPOCH:-$(date +%s)}"
++DATEtext=`date -u -d "@$SOURCE_DATE_EPOCH" "$DATE_FMT" 2>/dev/null || date -u -r "$SOURCE_DATE_EPOCH" "$DATE_FMT" 2>/dev/null || date -u "$DATE_FMT"`
+ 
+ # Show how this script is called.
+ echo run_doxygen $*
diff --git a/debian/rules.patch b/debian/rules.patch
index 89ecbe2..274514d 100644
--- a/debian/rules.patch
+++ b/debian/rules.patch
@@ -39,6 +39,7 @@ debian_patches += \
 	libstdc++-doclink \
 	libstdc++-man-3cxx \
 	libstdc++-test-installed \
+	libstdc++-scripts-run_doxygen-support-SOURCE_DATE_EPOCH \
 	alpha-no-ev4-directive \
 	note-gnu-stack \
 	libgomp-omp_h-multilib \
-- 
2.39.2

From cd27050d2ff32b1ce1f065d8e7ee0c6abffbf8d5 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 30 Apr 2023 14:38:34 -0700
Subject: [PATCH 2/2] debian/rules2: Remove _formulas.log files.

These files are artifacts from the documentation creation process and
may embed build dates.
---
 debian/rules2 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules2 b/debian/rules2
index 1b431e2..43c077f 100644
--- a/debian/rules2
+++ b/debian/rules2
@@ -2930,6 +2930,7 @@ debian/indep_binaries.all: $(foreach i,$(indep_binaries),$(binary_stamp)-$(i))
 	cat debian/indep_binaries debian/indep_binaries.epoch > debian/indep_binaries.all
 
 binary-indep: $(foreach i,$(indep_binaries),$(binary_stamp)-$(i)) debian/indep_binaries.all
+	find debian -name _formulas.log -delete -print
 	dh_compress $(foreach p,$(shell echo `cat debian/indep_binaries.all`),-p$(p)) \
 	  -X.log.xz -X.sum.xz -X.c -X.txt -X.tag -X.map -XREADME.Bugs
 	dh_fixperms $(foreach p,$(shell echo `cat debian/indep_binaries.all`),-p$(p))
-- 
2.39.2



signature.asc
Description: PGP signature

Bug#1036366: libreoffice: fails to embed font subset, PDF not printable, no option to disable subsetting nor embedding

[Thorsten Glaser]

Package: libreoffice-writer
Version: 1:7.0.4-4+deb11u6
Severity: normal
Tags: upstream
X-Debbugs-Cc: t...@mirbsd.de

Using the attached font (yes, libre licences) in a document
then either exporting that to PDF or printing it to a file
results in output that cannot directly be printed.

To add insult to injury, as the font is both subset and
embedded (knobs to disable either, separately, would be
VERY welcome), I cannot even use Ghostscript to add the
OS’ copy of the font with e.g. ps2pdf.

The problem here seems to be that the font is subset as
a stream that neither my girlfriend’s printer nor
GhostScript understand: the printer just drops it, and:

$ gs -dNOPAUSE -dBATCH '-sDEVICE=pdfwrite' '-sOutputFile=/tmp/x.pdf' -dSAFER 
'-dSubsetFonts=true' '-dEmbedAllFonts=true' '-dCompatibilityLevel=1.4' -f 
bla.pdf
[…]
    Error: can't process embedded font stream,
attempting to load the font using its name.
   Output may be incorrect.
[…]

The embedded font name is: BA+Inconsolatazi4[varl,varqu]Regular

I think something goes wrong with at least the name.
The font name is actually: Inconsolatazi4varl_qu

Its “human display name” is: Inconsolata zi4[varl,varqu] Regular

However, LibreOffice uses *that* instead of the proper psname
as base for the embedded font name, and at *least* that seems
to choke consumers of the resulting PDF.

And, yeah, output is incorrect — the ps2pdf output drops the
glyphs from the font.

$ pdffonts bla.pdf 
name type  encoding emb sub 
uni object ID
 -  --- --- 
--- -
BA+Inconsolatazi4[varl,varqu]Regular Type 1Builtin  yes 
yes yes  9  0


Other applications, such as Mu͒seScore, can use that font just fine,
although it does not subset it.


Oh, and I noticed #965236 is also still open, meaning PDF files
generated by LibreOffice aren’t legal to distribute…

-- Package-specific info:

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

Kernel: Linux 5.10.0-22-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libreoffice-writer depends on:
ii  libabw-0.1-1 0.1.3-1
ii  libc62.31-13+deb11u6
ii  libe-book-0.1-1  0.1.3-2
ii  libepubgen-0.1-1 0.1.1-1
ii  libetonyek-0.1-1 0.1.9-4
ii  libgcc-s110.2.1-6
ii  libicu67 67.1-7
ii  libmwaw-0.3-30.3.17-1
ii  libodfgen-0.1-1  0.1.8-2
ii  libreoffice-base-core1:7.0.4-4+deb11u6
ii  libreoffice-common   1:7.0.4-4+deb11u6
ii  libreoffice-core 1:7.0.4-4+deb11u6
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.7-1
ii  libstdc++6   10.2.1-6
ii  libuno-cppu3 1:7.0.4-4+deb11u6
ii  libuno-cppuhelpergcc3-3  1:7.0.4-4+deb11u6
ii  libuno-sal3  1:7.0.4-4+deb11u6
ii  libuno-salhelpergcc3-3   1:7.0.4-4+deb11u6
ii  libwpd-0.10-10   0.10.3-1
ii  libwpg-0.3-3 0.3.3-1
ii  libwps-0.4-4 0.4.12-1
ii  libxml2  2.9.10+dfsg-6.7+deb11u4
ii  ucf  3.0043
ii  uno-libs-private 1:7.0.4-4+deb11u6
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages libreoffice-writer recommends:
pn  libreoffice-math  

Versions of packages libreoffice-writer suggests:
pn  default-jre | java8-runtime | jre  
pn  fonts-crosextra-caladea
pn  fonts-crosextra-carlito
pn  libreoffice-base   
pn  libreoffice-java-common

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-4.2
ii  fonts-opensymbol2:102.11+LibO7.0.4-4+deb11u6
ii  libboost-locale1.74.0   1.74.0-9
ii  libc6   2.31-13+deb11u6
ii  libcairo2   1.16.0-5
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1+b1
ii  libclucene-core1v5  2.3.3.4+dfsg-1+b1
ii  libcmis-0.5-5v5 0.5.2-3
ii  libcups22.3.3op2-3+deb11u2
ii  libcurl3-gnutls 7.74.0-1.3+deb11u7
ii  libdbus-1-3 1.12.24-0+deb11u1
ii  libdconf1   0.38.0-2
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.5-1
ii  libexpat1   2.2.10-2+deb11u5
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1+deb11u1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libgpgmepp6 

Bug#1033958: binutils: reproducible builds: files in source tarball in arbitrary order

[Vagrant Cascadian]

On 2023-04-04, Vagrant Cascadian wrote:
> The files in the binutils tarball appear to be in arbitrary order,
> possibly affected by locale or filesystem differences:
>
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/armhf/diffoscope-results/binutils.html
>
>   /usr/src/binutils/binutils-2.40.tar.xz
>
>   e.g. the first file in the bfd directory listed in these two builds are:
>
>   
> hrw-r--r--···0000·2023-01-14·00:00:00.00·binutils-2.40/bfd/elf32-m68hc1x.h
>   vs.
>   
> hrw-r--r--···0000·2023-01-14·00:00:00.00·binutils-2.40/bfd/elf32-score7.c
>
>
> The attached patch to debian/rules fixes this by passing the --sort=name
> argument to tar.

Thanks for applying the fix for #1033959: binutils: reproducible builds: build 
paths embedded in debug symbols

Any chance we could get this patch applied too?

I think we are quite close to a place where binutils can at least build
reproducibly with DEB_BUILD_OPTIONS="nocheck nopgo nolto" ... which is a
good start!

live well,
  vagrant

> From 6dce3b6b223419c31fb1aaa59b658652b0fe953d Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian 
> Date: Tue, 4 Apr 2023 16:10:53 -0700
> Subject: [PATCH 1/2] debian/rules: Pass argument to tar to sort the files in
>  the binutils source tarball.
>
> Locale or filesystem differences may result in the generated tarball
> embedding files in arbitrary order.
>
> https://reproducible-builds.org/docs/archives/
> https://tests.reproducible-builds.org/debian/issues/unstable/random_order_in_tarball_issue.html
> ---
>  debian/rules | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/debian/rules b/debian/rules
> index 0a3ff6ec..a697df43 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -1484,7 +1484,7 @@ endif # ifndef BACKPORT
>   xargs -0r touch --no-dereference --date='$(BUILD_DATE)' && \
>   find $(source_files) -type f -print0 | LC_ALL=C sort -z | \
>   XZ_OPT=-9 tar --null -T - -c --xz --mode=go=rX,u+rw,a-s \
> - --owner=0 --group=0 --numeric-owner \
> + --owner=0 --group=0 --numeric-owner --sort=name \
>   --xform='s=^[^/]*\/=binutils-$(VERSION)/=' \
>   -f 
> $(pwd)/$(d_src)/$(PF)/src/binutils/binutils-$(VERSION).tar.xz \
>   $(source_files)
> -- 
> 2.39.2


signature.asc
Description: PGP signature

Bug#1036365: live-build: config --architecture[s] or config -a gives "not found"

[Tom Sullivan]

Package: live-build
Version: 1:20210407
Severity: normal
X-Debbugs-Cc: t...@sullivaninusa.com

Dear Maintainer,

as root or using sudo:
#config appears to work fine.
#config -a i386 OR #config --architecture/architectures i386 gives error:
--a not found  OR  --architecture OR architectures not found.

The problem is the same for amd64

Expected it take it without error so long as the name of the architecture was
valid.

Searched the bug list via web and only one bug had "architecture" in it and it
was not related to this.

Using debian Bullseye, system up to date.

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



-- Package-specific info:

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

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

Versions of packages live-build depends on:
ii  debootstrap  1.0.123+deb11u1

Versions of packages live-build recommends:
ii  apt-utils   2.2.4
ii  bzip2   1.0.8-4
ii  cpio2.13+dfsg-4
ii  file1:5.39-3
ii  live-boot-doc   1:20210208
ii  live-config-doc 11.0.3
ii  live-manual-html [live-manual]  2:20151217.1
ii  rsync   3.2.3-4+deb11u1
ii  systemd-container   247.3-7+deb11u2
ii  wget1.21-1+deb11u1
ii  xz-utils5.2.5-2.1~deb11u1

Versions of packages live-build suggests:
ii  e2fsprogs  1.46.2-2
pn  mtd-utils  
ii  parted 3.4-1

-- no debconf information

Bug#1036364: zfsutils-linux: please remove GPT creation bug

[Elliott Mitchell]

Package: zfsutils-linux
Version: 2.0.3-9+deb11u1

Would the Debian ZFS maintainers be so kind as to remove the GPT creation
bug from zfsutils-linux?

Full details are at: https://github.com/openzfs/zfs/issues/94

The issue is simply zpool's create/replace and other subcommands try to
unconditionally create GPT labels on anything resembling a whole device.
Unfortunately whatever algorithm is used for detecting whole devices is
poor and generates almost as many false positives and false negatives as
true positives and true negatives.

Attempts to get the OpenZFS project to address this seem to have met with
deaf ears.  Notably this was reported as a bug a decade ago, but nothing
has happened (notice the dates on the upstream bug report).

At this point I hope the Debian maintainers are willing to patch out this
bug.  Hopefully maintainers of other projects will follow and upstream
might notice they're approaching the losing end of a fork.

This has been a problem for so long that the workarounds are headed
towards being well-established techniques.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#932957: Please migrate Release Notes to reStructuredText

[James Addison]

Followup-For: Bug #932957
X-Debbugs-Cc: hwans...@mailbox.org

Hi Holger,

> Please note the  in the URL!
> I could not get this working with sphinx (if someone knows better, please
> contact me!)

Could the 'extlinks' feature[1] of Sphinx be helpful to migrate those?

(it allows defining URL pattern aliases, so for example :oldreleasenotes: could
map to https://www.debian.org/releases/bullseye/releasenotes and :releasenotes:
could map to https://www.debian.org/releases/bookworm/releasenotes for D12)

Parameters are supported too, and that could be useful for package-or-filepath
refs (re: grep -r '`.*<' source |grep -o '' | sort | uniq -c |sort -n)

> Beside this, I need help to adapt the buildchain, to get the possibility of
> building the release-notes for the different architectures.
> I have no python knowledge, so I will most likely not get this running myself.

I'll try to take a look into that soon to see what I can find out.  Do you
know how the current docbook-based build varies by architecture?

Perhaps we can borrow some build scripting from developers-reference and/or
debian-policy.. but I suppose those don't have per-architecture output.

> And the last point is the integration into the debhelper tools: I don't know
> if it is required, to have the release-notes fit for building as a whole
> package with sbuild or debuild or similar. Salsa tries to build it via CI
> at every push, but currently fails.

It's possible I've misunderstood, but would be the goals here to be to get
the release-notes documentation built by CI, and also for it to be distributed
as a Debian package itself?

(someone who knows more may correct me, but I think it would be great to have
the package available for install using apt in addition to the website)

Cheers,
James

[1] -  https://www.sphinx-doc.org/en/master/usage/extensions/extlinks.html

Bug#1036304: guix: /etc/profile.d/guix.sh not updated for 1.4.0

[Vagrant Cascadian]

On 2023-05-18, Philip McGrath wrote:
> The /etc/profile.d/guix.sh script was not updated for 1.4.0, or indeed 
> seemingly since it was first added to the Debian package to address #985916.

Oh wow, you are absolutely right! Thanks for catching this!

The fact that this is shipped as a function of guix-install.sh ... makes
it a little trickier to update...  I will raise a thread upstream about
how to make that easier in the future; coming up with a way to split
that out into a separate file would greatly simplify the process (at
least for downstream packaging)...


> Among other changes upstream, I changed it in 
> 23aafc800c9e678662766440916449ec5bbce830 to initialize various XDG 
> environment 
> variables, fixing a bug that can prevent KDE Plasma sessions from starting 
> properly, instead leaving the user with a black screen. I encountered that 
> bug 
> again today when I logged back in after running `guix home reconfigure` for 
> the 
> first time on a new Bookworm installation. I described the problem in more 
> detail upstream in https://issues.guix.gnu.org/56050 and the linked mailing-
> list thread.

This sounds suspiciously similar to a long outstanding debian bug:

  https://bugs.debian.org/988260

So if updating this would solve that, that is really promising!


> Note also that the file was renamed to zzz-guix.sh in 
> 93be56a3ab28ed0a482f354b7f536681c99b6999.

Hrm. that will be a little bit trickier to change...


It is, unfortunately, very late in the bookworm release cycle... might
have to wait till bookworm's first point release... will see how
invasive the changes are.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1036158: gcc-13: Please raise baseline for alpha to EV56

[Michael Cree]

On Wed, May 17, 2023 at 11:27:43AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Michael!
> 
> On Tue, 2023-05-16 at 20:25 +1200, Michael Cree wrote:
> > On Tue, May 16, 2023 at 09:38:56AM +0200, John Paul Adrian Glaubitz wrote:
> > > After a long discussion on IRC and the mailing list, we have agreed to 
> > > raise the
> > > baseline for the alpha architecture to EV56 to improve the generated code 
> > > and fix
> > > a number of issues. The change is already being implemented in the glibc 
> > > packages
> > > which switches to EV56 [1] since hwcaps are no longer available with 
> > > glibc 2.37 [2].
> > > 
> > > Could you raise the baseline for gcc on alpha to EV56?
> > > 
> > > I assume, it should be "--with-cpu=ev56" or "--with-arch=ev56".
> > 
> > Yes, please!
> > 
> > I suggest the following in debian/rules2:
> > 
> > ifneq (,$(findstring alpha,$(DEB_TARGET_ARCH)))
> >   CONFARGS += --with-cpu=ev56 --with-tune=ev6
> > endif
> > 
> > (the --with-tune only affects instruction scheduling and better tunes
> > code for ev6 and more recent machines, but allows execution down to
> > ev56.)  I have tested this in the past with a rebuild of most packages
> > that are in the base essential chroot in the past and it works well.
> 
> Doesn't that come with a speed penalty for EV56 machines? I'm asking because 
> EV56 is
> currently the baseline for QEMU when emulating Alpha.

I was under the impression that qemu was ev6/ev67 being machine type
clipper which emulates an ES40.  Am I mistaken?

With regards instruction scheduling EV56 is in-order two-instructions
[1] executed per cycle.  EV6 and EV67 are out-of-order [2]
four-instructions executed per cycle. Hence, for ev6/ev67 it can be
advantageous to bring forward instructions that are data (operand)
ready and delaying by four cpu-instructions those that depend on a
result of a previous instruction instead of placing them immediately
after the previous instruction to guarantee they don't waste an
instruction slot in the same cpu cycle. [3]

The deleterious impact on ev56 of doing this will be very small to
utterly negligible.  It is not worth worrying about.

Regards,
Michael.

[1] Here I am talking about most integer register/register operate
instructions.  Memory, integer multiply and floating-point instructions
have longer latencies.

[2] Note that out-of-order does not mean the cpu can bring forward
data ready instructions that have not yet been seen in the instruction
pipeline.  That is why we ask the compiler to place them earlier.

[3] Even more advantageous on ev6/ev67 is to loop unroll and evaluate
two iterations of the loop in parallel, i.e., intertwine the two
computational pathways.  When I did tests some time ago with gcc (4.6
and earlier versions) the compiler did not do this well, whereas my
manually optimised machine code was getting better than three
instructions executed per cpu cyle on certain code.

Bug#1035537: split -n k/N gives incorrect data on blocks after the first

[Chris Frey]

Severity: grave

Updating severity as suggested on the debian-lts mailing list.

Do you think this bug warrants a security-related fix in stable,
due to the potential for data corruption?

Thanks,
- Chris

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035537

Bug#1035537: split -n k/N gives incorrect data on blocks after the first

[Salvatore Bonaccorso]

Control: fixed -1 9.1-1

Hi,

On Thu, May 04, 2023 at 10:55:59PM -0400, Chris Frey wrote:
> Package: coreutils
> Version: 8.32-4+b1
> 
> This bug exists in both Debian Buster and Debian Bullseye.
> 
> It has been fixed in upstream.
> 
> It can be reproduced by splitting a file such that size of each
> chunk produced by split is larger than the block size used to read
> the files (io_blksize(), bufsize, in split.c).
> 
> Example:
> 
>   # create source file
>   dd if=/dev/urandom of=/tmp/datafile bs=317634560 count=1
> 
>   # create known good chunks
>   split -n 635 /tmp/datafile /tmp/datafile.
> 
>   # attempt to extract one of the chunks using -n
>   split -n 4/635 /tmp/datafile > /tmp/chunk4
> 
>   # compare - this will fail
>   cmp /tmp/datafile.ad /tmp/chunk4
> 
> The reason is that when bytes_chunk_extract() is called, the previous
> call to input_file_size() has already read bufsize bytes and left
> the file pointer there.  Then bytes_chunk_extract() performs an
> lseek(fd, start, SEEK_CUR) using its calculated offset "start",
> and seeks past the real start point.
> 
> Here's the fix against Debian Buster, but the same can be done on Bullseye.
> Upstream has an extra if statement, but is unnecessary since it is already
> handled by the surrounding if(start < initial_read) check.  We are
> in the else statement, so we know start >= initial_read.
> 
> 
> diff -ru coreutils-8.30/src/split.c coreutils-8.30-chunk-fix/src/split.c
> --- coreutils-8.30/src/split.c2018-05-14 00:20:24.0 -0400
> +++ coreutils-8.30-chunk-fix/src/split.c  2023-05-04 22:31:29.521398067 
> -0400
> @@ -1000,7 +1000,7 @@
>  }
>else
>  {
> -  if (lseek (STDIN_FILENO, start, SEEK_CUR) < 0)
> +  if (lseek (STDIN_FILENO, start - initial_read, SEEK_CUR) < 0)
>  die (EXIT_FAILURE, errno, "%s", quotef (infile));
>initial_read = SIZE_MAX;
>  }

For completeness replicating what was discussed on the debian-lts
list, the fix is upstream at
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=bb21daa125aeb4e32546309d370918ca47e612db
in v9.0, and first included in Debian so with the 9.1-1 upload.

Updating the medatadata accordingly.

Regards,
Salvatore

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

[Nicholas D Steeves]

Control: tag -1 -pending

Nicholas D Steeves  writes:

> David Bremner  writes:
>>
>> I agree that markdown file looks innocuous, but do you know if it is
>> just this file or any markdown file?
>
> This bug appears to be native-comp related.  After cherry picking three
> commits from upstream, I was able to generate a toc for the md snippet
> in the initial but report.  In the time it took to reply to this bug,
> native-comp occurred, and generate-toc began to fail again.  I purged
> the eln cache and tried again, and it succeeded...

I also confirmed that both the patched version (in the staging branch)
and unpatched version (in bookworm) work correctly with

 
https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-36-gitolite-gitweb-retirement.md

when one loads markdown-toc and generates the toc before native comp
kicks in.


signature.asc
Description: PGP signature

Bug#1036363: unblock: chromium/113.0.5672.126-1

[Andres Salomon]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: chrom...@packages.debian.org
Control: affects -1 + src:chromium


chromium has built
there are six new C V Es
let fixes migrate

Bug#1011669: ITP: gnucobol -- COBOL compiler

[Petter Reinholdtsen]

[Bart Martens]
> * Package name: gnucobol
>   Version : 3.1.2
>   Upstream Author : Roger While, Keisuke Nishida
> * URL : https://www.gnu.org/software/gnucobol/
> * License : GPL, LGPL
>   Programming Lang: C
>   Description : COBOL compiler

According to https://tracker.debian.org/pkg/gnucobol >, version
5 is already in unstable and experimental.  Perhaps you should get in
touch with the maintainer and offer your assistance?

Or is this ITP for version 3 as opposed to version 5?

-- 
Happy hacking
Petter Reinholdtsen

Bug#1036362: unblock: libwebp/1.2.4-0.2

[Salvatore Bonaccorso]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: libw...@packages.debian.org, j...@debian.org, car...@debian.org
Control: affects -1 + src:libwebp

Hi release team,

Please unblock package libwebp

[ Reason ]
libwebp is affected by CVE-2023-1999, #1035371 which is going to be
fixed as well by Moritz in a DSA.

[ Impact ]
If unfixed in bookworm, we will have a security regression from
bullseye to bookworm (until as well fixed via an upload there). To
avoid this situation, I uploaded to unstable the fix pending for
bullseye-security.

[ Tests ]
Unfortunately none specific to CVE-2023-1999. The original bugreport
are not public.

[ Risks ]
The patch is isolated for the changes and clears the result-bw on
error plus the return value of VP8BitWriterInit() get newly checked.
So there is no complex code change.

[ 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 testing

[ Other info ]
Nothing, special. DSA should go out in the next few days.

unblock libwebp/1.2.4-0.2

Regards,
Salvatore
diff -Nru libwebp-1.2.4/debian/changelog libwebp-1.2.4/debian/changelog
--- libwebp-1.2.4/debian/changelog  2023-01-23 14:28:25.0 +0100
+++ libwebp-1.2.4/debian/changelog  2023-05-19 14:50:58.0 +0200
@@ -1,3 +1,11 @@
+libwebp (1.2.4-0.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * EncodeAlphaInternal: clear result->bw on error (CVE-2023-1999)
+(Closes: #1035371)
+
+ -- Salvatore Bonaccorso   Fri, 19 May 2023 14:50:58 +0200
+
 libwebp (1.2.4-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch 
libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch
--- 
libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch 
1970-01-01 01:00:00.0 +0100
+++ 
libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch 
2023-05-19 14:50:58.0 +0200
@@ -0,0 +1,57 @@
+From: James Zern 
+Date: Wed, 22 Feb 2023 22:15:47 -0800
+Subject: EncodeAlphaInternal: clear result->bw on error
+Origin: 
https://github.com/webmproject/libwebp/commit/a486d800b60d0af4cc0836bf7ed8f21e12974129
+Bug-Debian: https://bugs.debian.org/1035371
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2023-1999
+
+This avoids a double free should the function fail prior to
+VP8BitWriterInit() and a previous trial result's buffer carried over.
+Previously in ApplyFiltersAndEncode() trial.bw (with a previous
+iteration's buffer) would be freed, followed by best.bw pointing to the
+same buffer.
+
+Since:
+187d379d add a fallback to ALPHA_NO_COMPRESSION
+
+In addition, check the return value of VP8BitWriterInit() in this
+function.
+
+Bug: webp:603
+Change-Id: Ic258381ee26c8c16bc211d157c8153831c8c6910
+---
+ src/enc/alpha_enc.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/src/enc/alpha_enc.c b/src/enc/alpha_enc.c
+index f7c02690e3cf..7d205586fe77 100644
+--- a/src/enc/alpha_enc.c
 b/src/enc/alpha_enc.c
+@@ -13,6 +13,7 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ #include "src/enc/vp8i_enc.h"
+ #include "src/dsp/dsp.h"
+@@ -148,6 +149,7 @@ static int EncodeAlphaInternal(const uint8_t* const data, 
int width, int height,
+   }
+ } else {
+   VP8LBitWriterWipeOut(_bw);
++  memset(>bw, 0, sizeof(result->bw));
+   return 0;
+ }
+   }
+@@ -162,7 +164,7 @@ static int EncodeAlphaInternal(const uint8_t* const data, 
int width, int height,
+   header = method | (filter << 2);
+   if (reduce_levels) header |= ALPHA_PREPROCESSED_LEVELS << 4;
+ 
+-  VP8BitWriterInit(>bw, ALPHA_HEADER_LEN + output_size);
++  if (!VP8BitWriterInit(>bw, ALPHA_HEADER_LEN + output_size)) ok = 0;
+   ok = ok && VP8BitWriterAppend(>bw, , ALPHA_HEADER_LEN);
+   ok = ok && VP8BitWriterAppend(>bw, output, output_size);
+ 
+-- 
+2.40.1
+
diff -Nru libwebp-1.2.4/debian/patches/series 
libwebp-1.2.4/debian/patches/series
--- libwebp-1.2.4/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libwebp-1.2.4/debian/patches/series 2023-05-19 14:50:58.0 +0200
@@ -0,0 +1 @@
+EncodeAlphaInternal-clear-result-bw-on-error.patch

Bug#1036250: trapperkeeper-webserver-jetty9-clojure: FTBFS in testing: MDCAccessLogConverter.java:54: error: cannot access HttpServletRequest

[Jérôme Charaoui]

Hi Markus,

Thank you, your patch does indeed fix the build problem for this 
package, however, the test failure is not insignificant.


I did further tests with puppetserver, which is a downstream dependency 
of trapperkeeper-webserver-jetty9-clojure and unfortunately, the web 
requests (access) logging remains broken. There are no warnings or error 
messages anywhere: as you can imagine, the logging events are simply 
lost in the ether.


I think these logs are a critical feature for debugging and security and 
it would be very unfortunate for bookworm to ship with logging crippled 
in this way for puppetserver.


Although I did not test this specifically, I strongly suspect puppetdb 
is also affected in a similar way because they share many of the same 
components.


Do you think it might be possible to backport the accessEvent variable 
fix from a later version of Logback?


-- Jérôme


Le 2023-05-19 à 09 h 53, Markus Koschany a écrit :

Control: tags -1 patch

Hi,

I am attaching a patch for this issue. Somehow your package fell through the
cracks because it has no dependency on logback. Logback is pulled in by Jetty
though. While Logback and Jetty use the Jakarta servlet API now, your package
still depends on libservlet-api-java. The fix for that was trivial. However the
test failure is caused by my tomcat10-migration.patch

https://salsa.debian.org/java-team/logback/-/blob/master/debian/patches/tomcat10-migration.patch#L91

Back then I thought it was acceptable to work around a build failure by setting
the accessEvent variable to null since it seemed no package existed in Debian
which would be affected by it. The Logback developers fixed that problem in
newer versions, but a new upstream release of logback would have been too
intrusive. Long story short: please double-check my patch and if we can ignore
the logging problem

Regards,

Markus

Bug#689062: ITP: dh-builtusing -- debhelper tool generating the Built-Using field for Debian packages

[Nicolas Boulenguez]

Hello.

I have written a tool inspired by this bug report.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035888
A full description is available at
https://salsa.debian.org/debian/dh-builtusing/-/blob/master/dh_builtusing.pod

This is a proof of concept, any suggestion or critic is welcome
(especially before anyone starts depending on it :-).

A separate debhelper tool avoids extending the dpkg interface. It
should be easier to maintain and document.
The price is some redundancy.  The tool parses debian/control twice,
via Dh_Lib and Dpkg perl modules.

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

[Nicholas D Steeves]

Antoine Beaupré  writes:

> On 2023-05-19 14:39:14, Nicholas D Steeves wrote:
>> Control: tag -1 confirmed upstream fixed-upstream pending
>> Antoine Beaupre  writes:
>>
>>> Package: elpa-markdown-toc
>>> Version: 0.1.5-2
>>> Severity: grave
>>
>>> markdown-toc-generate-toc crashes with:
>>>
>>> Debugger entered--Lisp error: (wrong-type-argument consp nil)
>>
>> Thanks for reporting; fix pending!
>
> Oh interesting! Where can I see it? is there a patch?
>

git clone g...@salsa.debian.org:emacsen-team/markdown-toc-el.git
git checkout for-testing-before-upload

> -- 
> Je n'ai fait celle-ci plus longue que parce que je n'ai pas eu le
> loisir de la faire plus courte.
> - Blaise Pascal

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

[Nicholas D Steeves]

David Bremner  writes:

> Antoine Beaupre  writes:
>
>> Package: elpa-markdown-toc
>> Version: 0.1.5-2
>> Severity: grave
>>
>> In Debian bookworm, markdown-toc is currently unusable.
>>
>> Given the following markdown buffer:
>>
>
> Hi Antoine;
>
> I agree that markdown file looks innocuous, but do you know if it is
> just this file or any markdown file?

This bug appears to be native-comp related.  After cherry picking three
commits from upstream, I was able to generate a toc for the md snippet
in the initial but report.  In the time it took to reply to this bug,
native-comp occurred, and generate-toc began to fail again.  I purged
the eln cache and tried again, and it succeeded...


signature.asc
Description: PGP signature

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

[Antoine Beaupré]

On 2023-05-19 14:39:14, Nicholas D Steeves wrote:
> Control: tag -1 confirmed upstream fixed-upstream pending
> Antoine Beaupre  writes:
>
>> Package: elpa-markdown-toc
>> Version: 0.1.5-2
>> Severity: grave
>
>> markdown-toc-generate-toc crashes with:
>>
>> Debugger entered--Lisp error: (wrong-type-argument consp nil)
>
> Thanks for reporting; fix pending!

Oh interesting! Where can I see it? is there a patch?

-- 
Je n'ai fait celle-ci plus longue que parce que je n'ai pas eu le
loisir de la faire plus courte.
- Blaise Pascal

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

[Nicholas D Steeves]

Control: tag -1 confirmed upstream fixed-upstream pending
Antoine Beaupre  writes:

> Package: elpa-markdown-toc
> Version: 0.1.5-2
> Severity: grave

> markdown-toc-generate-toc crashes with:
>
> Debugger entered--Lisp error: (wrong-type-argument consp nil)

Thanks for reporting; fix pending!


signature.asc
Description: PGP signature

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

[Antoine Beaupré]

On 2023-05-19 15:02:34, David Bremner wrote:
> Hi Antoine;
>
> I agree that markdown file looks innocuous, but do you know if it is
> just this file or any markdown file?

I managed to have it generate a TOC with a simple:

# a

# b

## c

But it also crashed (ultimately) on:

https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-36-gitolite-gitweb-retirement.md

a.

-- 
La perfection est atteinte, non pas lorsqu'il n'y a plus rien à
ajouter, mais lorsqu'il n'y a plus rien à retirer.
- Antoine de Saint-Exupéry

Bug#1036361: Akonadi floods log file .local/share/akonadi/db_data/mysql.err after upgrade to debian 12

[Ralf E-Mail]

package: akonadi-server
version: 4:22.12.3-1
severity: minor

I upgrade my system from debian 11 to debian 12.
After that the log files
.local/share/akonadi/db_data/mysql.err
.local/share/akonadi/db_data/mysql.err.old
swelled incredibly fast with 2 constantly repeating error messages.

Searching the in the internet I found the page
https://forums.opensuse.org/t/akonadi-floods-its-mysql-err-with-an-error-message/153196

The command
mysql_upgrade --defaults-file=/home/username/.local/share/akonadi/mysql.conf
--socket=/run/user/1000/akonadi/mysql.socket

solved the issue for me.
Still I consider it a bug that should be fixed.

Thanks for all your efforts!

Ralf

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

[David Bremner]

Antoine Beaupre  writes:

> Package: elpa-markdown-toc
> Version: 0.1.5-2
> Severity: grave
>
> In Debian bookworm, markdown-toc is currently unusable.
>
> Given the following markdown buffer:
>

Hi Antoine;

I agree that markdown file looks innocuous, but do you know if it is
just this file or any markdown file?

d

Bug#1023585: A 20-year Debian user has applied to activate the mailing list for loongarch64

[Chen Tao]

Dear Maintainer:
 Have a nice day！
 I'm a A 20-year Debian user，Debian is so elegant, robust, stable, and 
supports multiple architectures .  Loongson 3A5000  is a high-performance 
general-purpose CPU designed by loongson, which absorbs the advantages of MIPS 
and RISC-V, and represents the highest level of independently designed CPUs in 
China. I've run LFS, Gentoo, ArchLinux on my 3A5000 computer and they all work 
fine. Right now I'm working on a Debian 12 port. I really hope you can help 
open the mailing list, thank you!

Best Regard
Chen Tao

Bug#1028290: libreoffice-impress-nogui cannot convert to PNG

[Rene Engelhard]

Hi,

Am 01.05.23 um 00:41 schrieb Rene Engelhard:

It *seems* to be this in your nogui-strace:

94919 21:08:29.439478 openat(AT_FDCWD, 
"/usr/lib/libreoffice/share/config/soffice.cfg/modules/simpress/ui/tabviewbar.ui", O_RDONLY) = -1 ENOENT (No such file or directory)
94919 21:08:29.439573 --- SIGSEGV {si_signo=SIGSEGV, 
si_code=SEGV_MAPERR, si_addr=NULL} ---
94919 21:08:29.439478 openat(AT_FDCWD, 
"/usr/lib/libreoffice/share/config/soffice.cfg/modules/simpress/ui/tabviewbar.ui", O_RDONLY) = -1 ENOENT (No such file or directory)
94919 21:08:29.439573 --- SIGSEGV {si_signo=SIGSEGV, 
si_code=SEGV_MAPERR, si_addr=NULL} ---

[...]

Yes, it's definitely tabviewbar.ui which suffices and makes it work:

rene@debianunstable:~$ soffice --convert-to A.png A.pptx
Warning: failed to launch javaldx - java may not function correctly
Unspecified Application Error
rene@debianunstable:~$ su -
Passwort:
root@debianunstable:~# cd /home/rene/
root@debianunstable:/home/rene# mkdir -p 
/usr/lib/libreoffice/share/config/soffice.cfg/modules/simpress/ui
root@debianunstable:/home/rene# cp 
usr/lib/libreoffice/share/config/soffice.cfg/modules/simpress/ui/tabviewbar.ui 
/usr/lib/libreoffice/share/config/soffice.cfg/modules/simpress/ui

[from libreoffice-impress deb dpkg-deb -x'ed]
root@debianunstable:/home/rene#
Abgemeldet
rene@debianunstable:~$ soffice --convert-to A.png A.pptx
Warning: failed to launch javaldx - java may not function correctly
convert /home/rene/A.pptx as a Impress document -> /home/rene/A.A.png 
using filter : impress_png_Export

Overwriting: /home/rene/A.A.png
rene@debianunstable:~$

Forwarded upstream.
No idea whether it'll be acted on (and how), maybe we really need to 
split those files into a -uiconfig-impress or somesuch and make 
-impress-nogui Recommend or even Depend on it


Regards,

Rene

Bug#1036321: rootskel-gtk: Include metadata about the banner

[Cyril Brulebois]

Control: tag -1 patch pending

Hi,

Cyril Brulebois  (2023-05-19):
> Maybe something like logo_debian.properties (or whatever name) with:
> 
> labelPosition=right
> bannerExpands=right

I settled for a logo_installer.ini (logo_debian.ini for us, plus a
symlink via the Makefile, as it is done for the logo files themselves):

[banner]
# supported values: left, right
label-position = right
# supported values: left, right, both
expand-direction = both

See: https://salsa.debian.org/installer-team/rootskel-gtk/-/commit/306e00e96b

I'm not entirely the current expand-direction is the best for Bookworm:
 - Setting it to “right” would accentuate the strange rendering on the
   right (since repeating the last 1-px column hadn't been anticipated).
 - Setting it to “both” pushes “debian 12” towards the center without
   really centering it, so it could be considered less appealing than
   keeping in on the left.

> and having cdebconf-gtk deal with default settings (e.g. right for
> both). I'm not yet sure about whether it would make sense to support
> bannerExpands=both (probably doesn't cost much more, but would that
> look OK?).

cdebconf-gtk now defaults to right and both (respectively). This is
totally arbitrary, and as noted in the changelog: the theme should
provide an up-to-date metadata file so that we never have to touch
cdebconf's code (or default banner settings) again.

> I'm tempted to try and get that squeezed in finally (#745359 was
> almost 10 years ago, and the scaling trick was better than nothing,
> but clearly not ideal); we can always refine the format later on.

I'd call that mergeable at it is. I've pushed the cdebconf side directly
to master. Since rootskel-gtk's master branch contains old changes that
have never been uploaded to the archive, and since I don't feel like
taking responsibility for them at this stage, I've forked a bookworm
branch from the last tag, and plan on uploading to unstable from it.

Aurélien, please work within that branch if you have a chance to look
into #1036315 and #1036317. Feel free to tweak logo_installer.ini, I'm
happy to let you pick whatever you feel is best!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1036213: apache2: frequent SIGSEGV in mod_http2.so (purge_consumed_buckets)

[Bastien Durel]

Le 19/05/2023 à 18:11, Stefan Eissing a écrit :

Hi Bastien,


Hello


I am looking into the failures of mod_proxy_http2 and seeing an issue with 
connection reuse and subsequent handling of requests.

Going back to the original issue, do you still see those with mod_h2 v2.0.15? 
That would be interesting to know.

No, I had only 2 segfaults since I upgraded to 2.0.15, and none is in 
purge_consumed_buckets :


- proxy_pass_brigade
- ap_save_brigade


I do not know if just relying on mod_proxy_http in your setup would be 
possible. But it could help us isolating issues.


I don't think so ... The knot-resolver I forward DOH requests to seems 
to only support HTTP/2 ; if I change it to https://, dog fails to 
resolve on it :


Error [http]: Nameserver returned HTTP 502 (Proxy Error)

Regards,

--
Bastien Durel

Bug#1034915: Going to reschedule NMU

[Andreas Metzler]

Hello,

having read up on the current NMU timing guidance in developers
reference I will reschedule these to 1-day.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


signature.asc
Description: PGP signature

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

[Antoine Beaupre]

Package: elpa-markdown-toc
Version: 0.1.5-2
Severity: grave

In Debian bookworm, markdown-toc is currently unusable.

Given the following markdown buffer:

```


# Background


## Why migrate?


## Gitolite and GitWeb inventory


# Proposal
```

markdown-toc-generate-toc crashes with:

Debugger entered--Lisp error: (wrong-type-argument consp nil)
  markdown-imenu-create-nested-index()
  funcall(markdown-imenu-create-nested-index)
  (markdown-toc--compute-toc-structure (funcall imenu-create-index-function))
  (funcall markdown-toc-user-toc-structure-manipulation-fn 
(markdown-toc--compute-toc-structure (funcall imenu-create-index-function)))
  (markdown-toc--generate-toc (funcall 
markdown-toc-user-toc-structure-manipulation-fn 
(markdown-toc--compute-toc-structure (funcall imenu-create-index-function
  (insert (markdown-toc--generate-toc (funcall 
markdown-toc-user-toc-structure-manipulation-fn 
(markdown-toc--compute-toc-structure (funcall imenu-create-index-function)
  (save-excursion (if (markdown-toc--toc-already-present-p) (progn 
(markdown-toc--delete-toc t))) (insert (markdown-toc--generate-toc (funcall 
markdown-toc-user-toc-structure-manipulation-fn 
(markdown-toc--compute-toc-structure (funcall imenu-create-index-function))
  markdown-toc-generate-toc(nil)
  funcall-interactively(markdown-toc-generate-toc nil)
  command-execute(markdown-toc-generate-toc record)
  execute-extended-command(nil "markdown-toc-generate-toc" nil)
  funcall-interactively(execute-extended-command nil 
"markdown-toc-generate-toc" nil)
  command-execute(execute-extended-command)



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

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

Versions of packages elpa-markdown-toc depends on:
ii  dh-elpa-helper  2.0.16
ii  elpa-dash   2.19.1+git20220608.1.0ac1ecf+dfsg-1
ii  elpa-markdown-mode  2.5-1
ii  elpa-s  1.12.0-5
ii  emacsen-common  3.0.5

Versions of packages elpa-markdown-toc recommends:
ii  emacs  1:28.2+1-14
ii  emacs-gtk [emacs]  1:28.2+1-14

elpa-markdown-toc suggests no packages.

-- no debconf information

Bug#1036213: apache2: frequent SIGSEGV in mod_http2.so (purge_consumed_buckets)

[Stefan Eissing]

Hi Bastien,

I am looking into the failures of mod_proxy_http2 and seeing an issue with 
connection reuse and subsequent handling of requests.

Going back to the original issue, do you still see those with mod_h2 v2.0.15? 
That would be interesting to know.

I do not know if just relying on mod_proxy_http in your setup would be 
possible. But it could help us isolating issues.

Kind Regards,
Stefan

> Am 19.05.2023 um 15:04 schrieb Bastien Durel :
> 
> Le jeudi 18 mai 2023 à 15:04 +0200, Bastien Durel a écrit :
>> Le 18/05/2023 à 14:41, Stefan Eissing a écrit :
>>> Did you have an warning message like "AH03516: unexpected NN
>>> streams in hold" at that time in out error log?
>> 
>> No (grepping AH03516 in *.log returns nothing (nor does "streams in
>> hold"))
>> 
> Hello. I got another one in ap_save_brigade()
> 
> -- 
> Bastien
> 

Bug#977037: Add timestamp to logs

[Tim Andersson]

Hi Paul,

I've added an upstream MR here implementing the addition of relative
timestamps in seconds
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/229

Please give me any feedback you have on the implementation and I'll amend
it as you see fit!

Tim

Bug#1035522: debian-security-support 11+2023.05.04 flagged for acceptance

[Holger Levsen]

On Fri, May 19, 2023 at 02:38:37PM +0100, Adam D. Barratt wrote:
> > thanks! how/when will it moved/be moved to bullseye-updates?
> As I mentioned in a previous reply, the _how_ is by a member of SRM
> asking dak to do so. (And it will be copied, not moved. The package
> stays in p-u as well, in order to be added to bullseye in the next
> point release.)

ic, thanks.
 
> As to when, it needs to be when someone (which in practice is likely to
> be me) has had time to write an announcement and be around just after a
> dinstall to send out said announcement. As you can probably imagine,
> some people get worried when an update appears that they can't find a
> corresponding announcement for.
> 
> I'm hoping to find time to look at it over the weekend, but that
> depends a little on what life thinks of the idea.

cool, thank you.

> I'm sure it's not intended to be, but fwiw it does /feel/ a bit chasy.
> :-)
 
sigh, i'm sorry! (I do see the smiley however, but still.) 

My intentions were absolutly not chasing, but rather a.) making sure most people
will have it installed (on bullseye) before they upgrade to bookworm b.) 
probably
also help with what's left to do, though now I'm not sure there's much I can 
help
with.

Thank you!


-- 
cheers,
Holger

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

If a monkey hoarded more bananas than it could eat, while most of the other
monkeys starved, scientists would study that monkey to figure out what the
heck was wrong with it. When humans do it, we put them on the cover of Forbes.


signature.asc
Description: PGP signature

Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386

[Ansgar]

Package: release-notes
X-Debbugs-Cc: Steve McIntyre , debian-de...@lists.debian.org

On Fri, 2023-05-19 at 15:03 +0100, Steve McIntyre wrote:
> I had been thinking about doing similar for installer images too, but
> with other work going on too I think it got too late in the cycle to
> make that change. My plan is therefore to ship i386 installer images
> for bookworm as normal (including bookworm point releases going
> forwards), but to disable those builds for testing/trixie
> ~immediately after the release.

I suggest to already document this in the release notes for bookworm,
possibly in Section 2.1 (Supported architectures) or a subsection in
Section 5 (Issues to be aware of for bookworm).

Maybe something along these lines:

+---
| Debian 12 is expected to be the last Debian release providing
| full support for i386.  Debian 13 will only partially support
| i386 and no longer provide installation media for i386.
|
| We recommend hosts still running the i386 port to be upgraded
| to amd64.  Legacy i386 software can be run using multi-arch,
| chroot environments or containers.
+---

Ansgar

Bug#1036357: use C.UTF8 as default locale

[Johannes Schauer Marin Rodrigues]

Package: help2man
Version: 1.49.3
Severity: normal
Tags: patch

Hi,

the current default locale is C. This means that any non-ascii character
will show up as "??" in the resulting man page. By letting the default
locale be "C.UTF8", unicode characters will be treated correctly.
Attached is a patch.

Thanks!

cheers, josch

--- help2man2023-05-19 17:22:30.716019650 +0200
+++ help2man.new2023-05-19 17:22:44.087768889 +0200
@@ -78,7 +78,7 @@
 sub configure_locale
 {
delete @ENV{qw(LANGUAGE LC_MESSAGES LANG)};
-   setlocale LC_ALL, $ENV{LC_ALL} = shift || 'C';
+   setlocale LC_ALL, $ENV{LC_ALL} = shift || 'C.UTF8';
my $encoding = langinfo CODESET;
$encoder = (find_encoding $encoding) || fallback->new($encoding);
 }

Bug#1036356: stress-ng: autopkgtest failures on 32 bit architectures

[Benjamin Drung]

Package: stress-ng
Version: 0.15.07-1
Severity: serious
Tags: patch
Justification: autopkgtest failures
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

The autopkg tests on 32 bit architectures fail. In Ubuntu, the attached
patch was applied to fix the autopkgtest:

  * Cherry-pick upstream commit "stress-pthread: use 64 bit tid_addr to fix
stack clobbering on 32 bit platforms" and "stress-pthread: fix big endian
tid addr for 32 bit systems" to fix test failures on 32 bit architectures
(LP: #2019079)


Thanks for considering the patch.

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru stress-ng-0.15.07/debian/patches/series 
stress-ng-0.15.07/debian/patches/series
--- stress-ng-0.15.07/debian/patches/series 1970-01-01 01:00:00.0 
+0100
+++ stress-ng-0.15.07/debian/patches/series 2023-05-17 18:45:53.0 
+0200
@@ -0,0 +1,2 @@
+stress-pthread_use_64_bit_tid_addr.patch
+stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
diff -Nru 
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
 
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
--- 
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
1970-01-01 01:00:00.0 +0100
+++ 
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
2023-05-17 18:45:53.0 +0200
@@ -0,0 +1,46 @@
+From 63c0b414f6ec70dbd0498d59ca34fffbf2642b61 Mon Sep 17 00:00:00 2001
+From: Colin Ian King 
+Date: Wed, 10 May 2023 20:39:13 +0100
+Subject: [PATCH] stress-pthread: fix big endian tid addr for 32 bit systems
+
+The PR_GET_TID_ADDR does not have 32 bit compat, so it always returns
+a 64 bit tid addr. For 32 bit systems this needs to be either truncated
+for 32 little endian or shifted down to the bottom 32 bits for big endian
+systems such as big endian HPPA or MIPS32.
+
+Signed-off-by: Colin Ian King 
+Origin: upstream, 
https://github.com/ColinIanKing/stress-ng/commit/63c0b414f6ec70dbd0498d59ca34fffbf2642b61
+---
+ stress-pthread.c | 13 +++--
+ 1 file changed, 11 insertions(+), 2 deletions(-)
+
+diff --git a/stress-pthread.c b/stress-pthread.c
+index 5c0ee9e4..2190c333 100644
+--- a/stress-pthread.c
 b/stress-pthread.c
+@@ -177,14 +177,23 @@ static void OPTIMIZE3 stress_pthread_tid_address(const 
stress_args_t *args)
+   uint64_t tid_addr = 0;
+ 
+   if (LIKELY(prctl(PR_GET_TID_ADDRESS, _addr, 0, 0, 0) == 0)) {
+-  if (tid_addr) {
++  unsigned long set_tid_addr;
++
++  if (sizeof(void *) == 4)  {
++  set_tid_addr = stress_little_endian() ?
++  (tid_addr & 0x) : (tid_addr >> 32);
++  } else {
++  set_tid_addr = (unsigned long)tid_addr;
++  }
++
++  if (set_tid_addr) {
+   pid_t tid1, tid2;
+ 
+   /* Nullify */
+   VOID_RET(pid_t, (pid_t)syscall(__NR_set_tid_address, 
NULL));
+ 
+   /* This always succeeds */
+-  tid1 = (pid_t)syscall(__NR_set_tid_address, tid_addr);
++  tid1 = (pid_t)syscall(__NR_set_tid_address, 
set_tid_addr);
+ 
+   errno = 0;
+   tid2 = shim_gettid();
diff -Nru 
stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch 
stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch
--- stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch   
1970-01-01 01:00:00.0 +0100
+++ stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch   
2023-05-17 16:07:26.0 +0200
@@ -0,0 +1,37 @@
+From 637662d92865fbf5f3469d7754584f6d810fb902 Mon Sep 17 00:00:00 2001
+From: Colin Ian King 
+Date: Wed, 19 Apr 2023 08:46:17 +0100
+Subject: [PATCH] stress-pthread: use 64 bit tid_addr to fix stack clobbering
+ on 32 bit platforms
+
+Closes: https://github.com/ColinIanKing/stress-ng/issues/283
+
+Signed-off-by: Colin Ian King 
+Origin: upstream, 
https://github.com/ColinIanKing/stress-ng/commit/637662d92865fbf5f3469d7754584f6d810fb902
+---
+ stress-pthread.c | 12 +++-
+ 1 file changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/stress-pthread.c b/stress-pthread.c
+index 24431869b..a568f8167 100644
+--- a/stress-pthread.c
 b/stress-pthread.c
+@@ -163,7 +163,17 @@ static void OPTIMIZE3 stress_pthread_tid_address(const 
stress_args_t *args)
+ defined(__NR_set_tid_address) &&  \
+ defined(HAVE_KERNEL_ULONG_T) &&   \
+ defined(HAVE_SYSCALL)
+-  __kernel_ulong_t tid_addr = 0;
++  /*
++   *   prctl(2) states:
++   *"Note that since the prctl() system call does not have a compat
++   * implementation for the AMD64 

Bug#1036355: unblock: adduser/3.133

[Johannes Schauer Marin Rodrigues]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: addu...@packages.debian.org, mh+debian-packa...@zugschlus.de
Control: affects -1 + src:adduser

Please unblock package adduser

[ Reason ]

After apt dropped its dependency on adduser, we want to make sure that
all packages requiring adduser in their purge removal maintainer scripts
can still be purged. Instead of adding adduser to the Essential:yes set,
we add the Protected:yes field to make harder to remove it once it is
installed. In the past, apt's dependency on adduser made it hard to
remove. Only five packages in testing still rely on adduser to purge.
More context can be found in #1035654

[ Impact ]

Then it could happen that a user upgrading to bookworm first upgrades
apt, then removes adduser and then is unable to purge packages they had
removed earlier.

[ Tests ]

piuparts correctly concluded that adduser cannot be removed anymore
(without supplying the --allow-remove-essential flag).

[ Risks ]

adduser is a central package but the change is small (see debdiff
below). The mmdebstrap autopkgtest heavily tests the pseudo-essential
set and none of its test cases broke by the addition of the
Protected:yes field.

What did break is the adduser piuparts result. So it is not sufficient
to just reduce the required age for adduser but to also force its
transition despite its piuparts failure. The piuparts failure is an
intended result from this change. The failure shows that the change has
the desired effect. To solve this, changes have to happen on the
piuparts side. See #1035654 for more discussion around this.

[ 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 testing

[ Other info ]

Do not forget to add an additional hint that makes adduser migrate despite its
piuparts failure.

unblock adduser/3.133


diff -Nru adduser-3.132/debian/changelog adduser-3.133/debian/changelog
--- adduser-3.132/debian/changelog  2023-03-08 21:45:42.0 +0100
+++ adduser-3.133/debian/changelog  2023-05-16 23:27:12.0 +0200
@@ -1,3 +1,10 @@
+adduser (3.133) unstable; urgency=medium
+
+  [ Johannes Schauer Marin Rodrigues ]
+  * mark adduser as Protected:yes. This is a temporary fix for #1035694
+
+ -- Marc Haber   Tue, 16 May 2023 23:27:12 
+0200
+
 adduser (3.132) unstable; urgency=medium
 
   * This is a translation/documentation only release
diff -Nru adduser-3.132/debian/control adduser-3.133/debian/control
--- adduser-3.132/debian/control2023-03-08 21:45:42.0 +0100
+++ adduser-3.133/debian/control2023-05-16 23:27:12.0 +0200
@@ -15,6 +15,7 @@
 Multi-Arch: foreign
 Pre-Depends: ${misc:Pre-Depends}
 Depends: passwd, ${misc:Depends}
+Protected: yes
 Suggests: liblocale-gettext-perl, perl, cron, quota
 Description: add and remove users and groups
  This package includes the 'adduser' and 'deluser' commands for creating
diff -Nru adduser-3.132/doc/po4a/po/adduser.pot 
adduser-3.133/doc/po4a/po/adduser.pot
--- adduser-3.132/doc/po4a/po/adduser.pot   2023-03-08 21:45:42.0 
+0100
+++ adduser-3.133/doc/po4a/po/adduser.pot   2023-05-16 23:27:12.0 
+0200
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2023-03-17 12:15+0100\n"
+"POT-Creation-Date: 2023-05-17 12:17+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME \n"
 "Language-Team: LANGUAGE \n"
diff -Nru adduser-3.132/doc/po4a/po/fr.po adduser-3.133/doc/po4a/po/fr.po
--- adduser-3.132/doc/po4a/po/fr.po 2023-03-08 21:45:42.0 +0100
+++ adduser-3.133/doc/po4a/po/fr.po 2023-05-16 23:27:12.0 +0200
@@ -8,7 +8,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: adduser 3.115\n"
-"POT-Creation-Date: 2023-03-17 12:15+0100\n"
+"POT-Creation-Date: 2023-05-17 12:17+0200\n"
 "PO-Revision-Date: 2023-01-18 08:09+0100\n"
 "Last-Translator: Jean-Paul Guillonneau \n"
 "Language-Team: French \n"
diff -Nru adduser-3.132/doc/po4a/po/pt.po adduser-3.133/doc/po4a/po/pt.po
--- adduser-3.132/doc/po4a/po/pt.po 2023-03-08 21:45:42.0 +0100
+++ adduser-3.133/doc/po4a/po/pt.po 2023-05-16 23:27:12.0 +0200
@@ -5,7 +5,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: adduser 3.130\n"
-"POT-Creation-Date: 2023-03-17 12:15+0100\n"
+"POT-Creation-Date: 2023-05-17 12:17+0200\n"
 "PO-Revision-Date: 2023-01-06 23:30+\n"
 "Last-Translator: Américo Monteiro \n"
 "Language-Team: Portuguese <>\n"

Bug#1036354: unblock: iptables-persistent/1.0.20

[gustavo panizzo]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: bl...@debian.org

Please unblock package iptables-persistent

(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

[ Reason ]
The package is using alternatives to manage (systemd) aliases,
this is not recommended by the systemd maintainers.

See bug report #1036147


I've added alternatives to this package back in 2019 to solve #926927
as a point of coordination with other firewall managers in Debian
(see https://lists.debian.org/debian-firewall/2019/08/msg0.html) but
the initiative never took off


[ Impact ]
This is (was) the only package in Debian which uses alternatives to
manage aliases, which makes it different from what admins expect

[ Tests ]
This version of the package is clean in lintian and piuparts,
I've upgraded my systems and found no problems


[ Risks ]
I see no risks, if an admin locally have changed the override files,
we'll keep them as dpkg-bak


[ 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 testing


unblock iptables-persistent/1.0.20
diff -Nru iptables-persistent-1.0.19/debian/changelog 
iptables-persistent-1.0.20/debian/changelog
--- iptables-persistent-1.0.19/debian/changelog 2023-02-28 08:02:38.0 
+0100
+++ iptables-persistent-1.0.20/debian/changelog 2023-05-19 13:27:33.0 
+0200
@@ -1,3 +1,16 @@
+iptables-persistent (1.0.20) unstable; urgency=medium
+
+  [ Luca Boccassi ]
+  * [3d8a9b] Use aliases instead of overrides for alternative names
+(Closes: #1036147)
+  * [418c74] Install drop-ins in /lib/ instead of /etc/ (Closes: #1036147)
+
+  [ gustavo panizzo ]
+  * [06509f] Handle obsolete conffile removal
+  * [633371] Remove obsolete dependency (lsb-base)
+
+ -- gustavo panizzo   Fri, 19 May 2023 13:27:33 +0200
+
 iptables-persistent (1.0.19) unstable; urgency=medium
 
   * [49d9ca] Debconf templates translation to Romanian.
diff -Nru iptables-persistent-1.0.19/debian/control 
iptables-persistent-1.0.20/debian/control
--- iptables-persistent-1.0.19/debian/control   2023-02-28 08:02:01.0 
+0100
+++ iptables-persistent-1.0.20/debian/control   2023-05-19 13:26:46.0 
+0200
@@ -7,10 +7,11 @@
 Vcs-Browser: https://salsa.debian.org/debian/iptables-persistent
 Vcs-Git: https://salsa.debian.org/debian/iptables-persistent.git
 Rules-Requires-Root: no
+Pre-Depends: dpkg (>= 1.15.7.2)
 
 Package: netfilter-persistent
 Architecture: all
-Depends: lsb-base, ${misc:Depends}
+Depends: ${misc:Depends}
 Suggests: iptables-persistent
 Pre-Depends: ${misc:Pre-Depends}
 Description: boot-time loader for netfilter configuration
diff -Nru iptables-persistent-1.0.19/debian/ipset.override 
iptables-persistent-1.0.20/debian/ipset.override
--- iptables-persistent-1.0.19/debian/ipset.override2021-11-17 
08:58:54.0 +0100
+++ iptables-persistent-1.0.20/debian/ipset.override2023-05-19 
12:12:44.0 +0200
@@ -1,2 +1,2 @@
-[Unit]
-Conflicts=ipset.service
+[Install]
+Alias=ipset.service
diff -Nru iptables-persistent-1.0.19/debian/ipset-persistent.install 
iptables-persistent-1.0.20/debian/ipset-persistent.install
--- iptables-persistent-1.0.19/debian/ipset-persistent.install  2021-11-17 
08:58:54.0 +0100
+++ iptables-persistent-1.0.20/debian/ipset-persistent.install  2023-05-19 
12:12:44.0 +0200
@@ -1,4 +1,4 @@
 #! /usr/bin/dh-exec
 plugins/10-ipset usr/share/netfilter-persistent/plugins.d/
 plugins/40-ipset usr/share/netfilter-persistent/plugins.d/
-debian/ipset.override => 
etc/systemd/system/netfilter-persistent.service.d/ipset.conf
+debian/ipset.override => 
lib/systemd/system/netfilter-persistent.service.d/ipset.conf
diff -Nru iptables-persistent-1.0.19/debian/ipset-persistent.maintscript 
iptables-persistent-1.0.20/debian/ipset-persistent.maintscript
--- iptables-persistent-1.0.19/debian/ipset-persistent.maintscript  
1970-01-01 01:00:00.0 +0100
+++ iptables-persistent-1.0.20/debian/ipset-persistent.maintscript  
2023-05-19 13:26:46.0 +0200
@@ -0,0 +1 @@
+rm_conffile /etc/systemd/system/netfilter-persistent.service.d/ipset.conf
diff -Nru iptables-persistent-1.0.19/debian/ipset-persistent.postinst 
iptables-persistent-1.0.20/debian/ipset-persistent.postinst
--- iptables-persistent-1.0.19/debian/ipset-persistent.postinst 2021-11-17 
08:58:54.0 +0100
+++ iptables-persistent-1.0.20/debian/ipset-persistent.postinst 2023-05-19 
13:26:46.0 +0200
@@ -2,8 +2,10 @@
 
 set -e
 
-# Setup alternatives
-update-alternatives --install /lib/systemd/system/ipset.service ipset.service 
/lib/systemd/system/netfilter-persistent.service 40
+# Can be dropped in Trixie
+if update-alternatives --query ipset.service 2>/dev/null; then
+update-alternatives --remove-all 

Bug#1035904: dpkg currently warning about merged-usr systems (revisited)

[Ansgar]

Hi,

On Fri, 2023-05-19 at 07:09 -0700, Sean Whitton wrote:
> On Thu 18 May 2023 at 07:55PM +02, Ansgar wrote:
> 
> > Why not?
> 
> We will not move that fast.

So there is no real reason?

As there doesn't seem to be anything you think need to be talked about
that is missing to get to a decision (given you ignored all other
questions multiple times).

Do you expect this to take longer than 2-3 months? I would suggest to
just use a GR in that case: it seems quicker and less painful than a
multi-month long process for a simple(!) question.

Ansgar

Bug#1035371: libwebp: diff for NMU version 1.2.4-0.2

[Salvatore Bonaccorso]

Control: tags 1035371 + patch


Dear maintainer,

I've prepared an NMU for libwebp (versioned as 1.2.4-0.2). The diff
is attached to this message. Due to the bookworm release plan and the
fact Moritz is going to release a DSA for libwebp for bullseye, I did
straight upload the diff without further delay. Hope this is okay for
you.

Regards,
Salvatore
diff -Nru libwebp-1.2.4/debian/changelog libwebp-1.2.4/debian/changelog
--- libwebp-1.2.4/debian/changelog	2023-01-23 14:28:25.0 +0100
+++ libwebp-1.2.4/debian/changelog	2023-05-19 14:50:58.0 +0200
@@ -1,3 +1,11 @@
+libwebp (1.2.4-0.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * EncodeAlphaInternal: clear result->bw on error (CVE-2023-1999)
+(Closes: #1035371)
+
+ -- Salvatore Bonaccorso   Fri, 19 May 2023 14:50:58 +0200
+
 libwebp (1.2.4-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch
--- libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch	1970-01-01 01:00:00.0 +0100
+++ libwebp-1.2.4/debian/patches/EncodeAlphaInternal-clear-result-bw-on-error.patch	2023-05-19 14:50:58.0 +0200
@@ -0,0 +1,57 @@
+From: James Zern 
+Date: Wed, 22 Feb 2023 22:15:47 -0800
+Subject: EncodeAlphaInternal: clear result->bw on error
+Origin: https://github.com/webmproject/libwebp/commit/a486d800b60d0af4cc0836bf7ed8f21e12974129
+Bug-Debian: https://bugs.debian.org/1035371
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2023-1999
+
+This avoids a double free should the function fail prior to
+VP8BitWriterInit() and a previous trial result's buffer carried over.
+Previously in ApplyFiltersAndEncode() trial.bw (with a previous
+iteration's buffer) would be freed, followed by best.bw pointing to the
+same buffer.
+
+Since:
+187d379d add a fallback to ALPHA_NO_COMPRESSION
+
+In addition, check the return value of VP8BitWriterInit() in this
+function.
+
+Bug: webp:603
+Change-Id: Ic258381ee26c8c16bc211d157c8153831c8c6910
+---
+ src/enc/alpha_enc.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/src/enc/alpha_enc.c b/src/enc/alpha_enc.c
+index f7c02690e3cf..7d205586fe77 100644
+--- a/src/enc/alpha_enc.c
 b/src/enc/alpha_enc.c
+@@ -13,6 +13,7 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ #include "src/enc/vp8i_enc.h"
+ #include "src/dsp/dsp.h"
+@@ -148,6 +149,7 @@ static int EncodeAlphaInternal(const uint8_t* const data, int width, int height,
+   }
+ } else {
+   VP8LBitWriterWipeOut(_bw);
++  memset(>bw, 0, sizeof(result->bw));
+   return 0;
+ }
+   }
+@@ -162,7 +164,7 @@ static int EncodeAlphaInternal(const uint8_t* const data, int width, int height,
+   header = method | (filter << 2);
+   if (reduce_levels) header |= ALPHA_PREPROCESSED_LEVELS << 4;
+ 
+-  VP8BitWriterInit(>bw, ALPHA_HEADER_LEN + output_size);
++  if (!VP8BitWriterInit(>bw, ALPHA_HEADER_LEN + output_size)) ok = 0;
+   ok = ok && VP8BitWriterAppend(>bw, , ALPHA_HEADER_LEN);
+   ok = ok && VP8BitWriterAppend(>bw, output, output_size);
+ 
+-- 
+2.40.1
+
diff -Nru libwebp-1.2.4/debian/patches/series libwebp-1.2.4/debian/patches/series
--- libwebp-1.2.4/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ libwebp-1.2.4/debian/patches/series	2023-05-19 14:50:58.0 +0200
@@ -0,0 +1 @@
+EncodeAlphaInternal-clear-result-bw-on-error.patch

Bug#1035904: dpkg currently warning about merged-usr systems (revisited)

[Sean Whitton]

Hello,

On Thu 18 May 2023 at 07:55PM +02, Ansgar wrote:

> Why not?

We will not move that fast.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1035522: bullseye-pu: package debian-security-support/1:11+2023.05.04

[Holger Levsen]

On Thu, May 18, 2023 at 02:44:01PM +0100, Adam D. Barratt wrote:
> The relevant section of dev-ref implies this, fwiw. I think some
> combination of you and I wrote it. :-)

https://www.debian.org/doc/manuals/developers-reference/developers-reference.en.html#special-case-the-stable-updates-suite
just got this change:

Author: Holger Levsen 
Date:   Fri May 19 16:04:35 2023 +0200

pkgs: explicitly state that $suite should be used in d/changelog for 
uploads to stable-updates.

Signed-off-by: Holger Levsen 

diff --git a/source/pkgs.rst b/source/pkgs.rst
+- Uploads to ``stable-updates`` should target their suite name in
+  the changelog as usual, e.g. ``bullseye``.
 

-- 
cheers,
Holger

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

In a world where you can be anything, be kind.


signature.asc
Description: PGP signature

Bug#1031858: prometheus-node-exporter-collectors: locale issue leads to an unparseable ipmitool_sensor textfile

[Daniel Swarbrick]

On Fri, 24 Feb 2023 11:30:10 +0100 Florian Schlichting 
 wrote:


> The hotfix is a
> 
/etc/systemd/system/prometheus-node-exporter-ipmitool-sensor.service.d/override.conf 


> file setting
>
> [Service]
> Environment=LC_NUMERIC=C
>
> but this should preferably be set in
> /lib/systemd/system/prometheus-node-exporter-ipmitool-sensor.service or
> even fixed in the ipmitools awk script upstream..

Setting LC_NUMERIC in the upstream awk script is not viable, since the 
awk script does not actually _execute_ the ipmitool command. It merely 
expects the output of the ipmitool command to be piped to the awk script.


So, setting the environment in the systemd service file is the best that 
we can do.




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035522: bullseye-pu: package debian-security-support/1:11+2023.05.04

[Holger Levsen]

On Thu, May 18, 2023 at 02:44:01PM +0100, Adam D. Barratt wrote:
> > ic. so I should have uploaded to bullseye-proposed-updates instead?
> Any upload goes to p-u first, yeah. So the target should always be
> simply "bullseye", by preference. dak will accept a bunch of other
> things, including "stable", "bullseye-proposed-updates", "proposed-
> updates" and, as you've demonstrated, "bullseye-updates" and DTRT, but
> it's cleaner and less potentially confusing if everything uses the
> same.

ok, thanks. that does make sense.
 
> The relevant section of dev-ref implies this, fwiw. I think some
> combination of you and I wrote it. :-)

oh dear. however upon re-reading 5.5.1 and 5.5.2 I've noticed that 5.5.2
says nothing about the suite in d/changelog and I think I'm going to fix
that now :)

https://www.debian.org/doc/manuals/developers-reference/developers-reference.en.html#special-case-the-stable-updates-suite


-- 
cheers,
Holger

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

If a monkey hoarded more bananas than it could eat, while most of the other
monkeys starved, scientists would study that monkey to figure out what the
heck was wrong with it. When humans do it, we put them on the cover of Forbes.


signature.asc
Description: PGP signature

Bug#1036250: trapperkeeper-webserver-jetty9-clojure: FTBFS in testing: MDCAccessLogConverter.java:54: error: cannot access HttpServletRequest

[Markus Koschany]

Control: tags -1 patch

Hi,

I am attaching a patch for this issue. Somehow your package fell through the
cracks because it has no dependency on logback. Logback is pulled in by Jetty
though. While Logback and Jetty use the Jakarta servlet API now, your package
still depends on libservlet-api-java. The fix for that was trivial. However the
test failure is caused by my tomcat10-migration.patch 

https://salsa.debian.org/java-team/logback/-/blob/master/debian/patches/tomcat10-migration.patch#L91

Back then I thought it was acceptable to work around a build failure by setting
the accessEvent variable to null since it seemed no package existed in Debian
which would be affected by it. The Logback developers fixed that problem in
newer versions, but a new upstream release of logback would have been too
intrusive. Long story short: please double-check my patch and if we can ignore
the logging problem

Regards,

Markus


diff -Nru trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/changelog trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/changelog
--- trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/changelog	2023-02-10 23:15:30.0 +0100
+++ trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/changelog	2023-05-19 15:19:10.0 +0200
@@ -1,3 +1,14 @@
+trapperkeeper-webserver-jetty9-clojure (4.4.1-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace libservlet-api-java with libjakarta-servlet-api-java.
+  * Add jakarta.servlet.patch to fix FTBFS with latest Jetty and Logback
+versions in Debian. (Closes: #1036250)
+  * Work around a test failure by disabling request-logging-test.
+(Closes: #1034855)
+
+ -- Markus Koschany   Fri, 19 May 2023 15:19:10 +0200
+
 trapperkeeper-webserver-jetty9-clojure (4.4.1-5) unstable; urgency=medium
 
   * d/control: bump Breaks: on puppetserver
diff -Nru trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/control trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/control
--- trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/control	2023-02-10 23:15:30.0 +0100
+++ trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/control	2023-05-19 15:19:10.0 +0200
@@ -15,7 +15,7 @@
  libtools-logging-clojure,
  libjanino-java,
  libordered-clojure,
- libservlet-api-java,
+ libjakarta-servlet-api-java,
  libjetty9-java,
  libjetty9-extra-java,
  libprismatic-schema-clojure (>= 1.1.12),
diff -Nru trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/libtrapperkeeper-webserver-jetty9-clojure.classpath trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/libtrapperkeeper-webserver-jetty9-clojure.classpath
--- trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/libtrapperkeeper-webserver-jetty9-clojure.classpath	2023-02-10 23:15:30.0 +0100
+++ trapperkeeper-webserver-jetty9-clojure-4.4.1/debian/libtrapperkeeper-webserver-jetty9-clojure.classpath	2023-05-19 15:19:10.0 +0200
@@ -1 +1 @@
-usr/share/java/trapperkeeper-webserver-jetty9.jar /usr/share/java/clojure.jar /usr/share/java/java.jmx.jar /usr/share/java/tools.logging.jar /usr/share/java/janino.jar /usr/share/java/servlet-api.jar /usr/share/java/jetty9-server.jar /usr/share/java/jetty9-io.jar /usr/share/java/jetty9-security.jar /usr/share/java/jetty9-client.jar /usr/share/java/jetty9-servlet.jar /usr/share/java/jetty9-http.jar /usr/share/java/jetty9-util.jar /usr/share/java/jetty9-servlets.jar /usr/share/java/jetty9-webapp.jar /usr/share/java/jetty9-proxy.jar /usr/share/java/jetty9-jmx.jar /usr/share/java/jetty9-websocket-server.jar /usr/share/java/jetty9-websocket-api.jar /usr/share/java/jetty9-websocket-servlet.jar /usr/share/java/schema.jar /usr/share/java/ring-servlet.jar /usr/share/java/ring-codec.jar /usr/share/java/ssl-utils.jar /usr/share/java/kitchensink.jar /usr/share/java/trapperkeeper.jar /usr/share/java/puppetlabs-i18n.jar /usr/share/java/trapperkeeper-filesystem-watcher.jar /usr/share/java/jul-to-slf4j.jar
+usr/share/java/trapperkeeper-webserver-jetty9.jar /usr/share/java/clojure.jar /usr/share/java/java.jmx.jar /usr/share/java/tools.logging.jar /usr/share/java/janino.jar /usr/share/java/jakarta-servlet-api.jar /usr/share/java/jetty9-server.jar /usr/share/java/jetty9-io.jar /usr/share/java/jetty9-security.jar /usr/share/java/jetty9-client.jar /usr/share/java/jetty9-servlet.jar /usr/share/java/jetty9-http.jar /usr/share/java/jetty9-util.jar /usr/share/java/jetty9-servlets.jar /usr/share/java/jetty9-webapp.jar /usr/share/java/jetty9-proxy.jar /usr/share/java/jetty9-jmx.jar /usr/share/java/jetty9-websocket-server.jar /usr/share/java/jetty9-websocket-api.jar /usr/share/java/jetty9-websocket-servlet.jar /usr/share/java/schema.jar /usr/share/java/ring-servlet.jar /usr/share/java/ring-codec.jar /usr/share/java/ssl-utils.jar /usr/share/java/kitchensink.jar /usr/share/java/trapperkeeper.jar /usr/share/java/puppetlabs-i18n.jar /usr/share/java/trapperkeeper-filesystem-watcher.jar /usr/share/java/jul-to-slf4j.jar
diff -Nru 

Bug#1004755: Please update to source format 3.0 (quilt)

[Bastian Germann]

Control: retitle -1 Please update to source format 3.0 (quilt)

Most of this was done with -8.1. However, the 3.0 (quilt) conversion is missing.

Bug#1035522: debian-security-support 11+2023.05.04 flagged for acceptance

[Adam D. Barratt]

On Fri, 2023-05-19 at 13:11 +, Holger Levsen wrote:
> On Thu, May 18, 2023 at 07:51:36PM +, Adam D Barratt wrote:
> > The upload referenced by this bug report has been flagged for
> > acceptance into the proposed-updates queue for Debian bullseye.
>  
> thanks! how/when will it moved/be moved to bullseye-updates?

As I mentioned in a previous reply, the _how_ is by a member of SRM
asking dak to do so. (And it will be copied, not moved. The package
stays in p-u as well, in order to be added to bullseye in the next
point release.)

As to when, it needs to be when someone (which in practice is likely to
be me) has had time to write an announcement and be around just after a
dinstall to send out said announcement. As you can probably imagine,
some people get worried when an update appears that they can't find a
corresponding announcement for.

I'm hoping to find time to look at it over the weekend, but that
depends a little on what life thinks of the idea.

I'm sure it's not intended to be, but fwiw it does /feel/ a bit chasy.
:-)

Regards,

Adam

Bug#1036353: modsecurity-crs: also include the "plugins"

[Mattia Rizzolo]

Source: modsecurity-crs
Version: 3.3.4-1
Severity: wishlist

Hi maintainers,

so this package is packing up https://github.com/coreruleset/coreruleset

However, to properly run those rules for some website one would also
need to run so-called "plugins" of the crs.

For example, https://github.com/coreruleset/wordpress-rule-exclusions-plugin/
for wordpress (the one that interests me here for my use case, but there
are plenty of others).

I wonder what are your thoughts of bundling those up in the package,
possibly in separate binary packages, so that they can be installed only
on hosts that actually run those CMSs?  They don't seem to have actual
"releases", so at best they would need to be snapshot of whenever you
bundle them, but I think that would already be quite good.

If you would be opposed to including these, why? :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1036349: O: gdb-msp430 -- The GNU debugger for MSP430

[Bastian Germann]

Package: wnpp

The gdb-msp430 package is obviously not maintained anymore.
I hereby orphan it. Please only consider adopting it if you can afford the time 
and have the skills to maintain it.

Bug#1036352: O: msp430-libc -- Standard C library for TI MSP430 development

[Bastian Germann]

Package: wnpp

The msp430-libc package is obviously not maintained anymore.
I hereby orphan it. Please only consider adopting it if you can afford the time 
and have the skills to maintain it.

Bug#1036350: O: gcc-msp430 -- GNU C compiler (cross compiler for MSP430)

[Bastian Germann]

Package: wnpp

The gcc-msp430 package is obviously not maintained anymore.
I hereby orphan it. Please only consider adopting it if you can afford the time 
and have the skills to maintain it.

Bug#1036351: O: binutils-msp430 -- Binary utilities supporting TI's MSP430 targets

[Bastian Germann]

Package: wnpp

The binutils-msp430 package is obviously not maintained anymore.
I hereby orphan it. Please only consider adopting it if you can afford the time 
and have the skills to maintain it.

Bug#1036348: unblock: php-horde-mime-viewer/2.2.4+debian0-2

[Mike Gabriel]

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

Please unblock package php-horde-mime-viewer

It was discovered that some of the Javascript files were not properly
included into the php-horde-mime-viewer bin:pkg.

[ Reason ]

+  * d/control: Bump Standards-Version: to 4.6.2. No changes needed.
+  * d/rules: Make sure syntaxhighlighter src-files end up in bin:pkg. (Closes:
+#1035429).

We now simply copy those files into the bin:pkg by a cp statement in
d/rules.

[ Impact ]
Syntax highlighting in Horde components (such as whups, the Horde
bugtracker) should now be fixed.

[ Tests ]
Checking the package after installation, only symlinked files now do exist.

[ Risks ]
Syntax highlighting in Horde might be broken.

[ 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 testing

[ Other info ]
None.

unblock php-horde-mime-viewer/2.2.4+debian0-2
diff -Nru php-horde-mime-viewer-2.2.4+debian0/debian/changelog 
php-horde-mime-viewer-2.2.4+debian0/debian/changelog
--- php-horde-mime-viewer-2.2.4+debian0/debian/changelog2022-03-08 
21:12:22.0 +0100
+++ php-horde-mime-viewer-2.2.4+debian0/debian/changelog2023-05-16 
23:25:26.0 +0200
@@ -1,3 +1,11 @@
+php-horde-mime-viewer (2.2.4+debian0-2) unstable; urgency=medium
+
+  * d/control: Bump Standards-Version: to 4.6.2. No changes needed.
+  * d/rules: Make sure syntaxhighlighter src-files end up in bin:pkg. (Closes:
+#1035429).
+
+ -- Mike Gabriel   Tue, 16 May 2023 23:25:26 +0200
+
 php-horde-mime-viewer (2.2.4+debian0-1) unstable; urgency=medium
 
   * New upstream version 2.2.4+debian0
diff -Nru php-horde-mime-viewer-2.2.4+debian0/debian/rules 
php-horde-mime-viewer-2.2.4+debian0/debian/rules
--- php-horde-mime-viewer-2.2.4+debian0/debian/rules2020-07-01 
09:45:24.0 +0200
+++ php-horde-mime-viewer-2.2.4+debian0/debian/rules2023-05-16 
23:24:43.0 +0200
@@ -7,3 +7,4 @@
# Remove extra license files
rm 
debian/php-horde-mime-viewer/usr/share/horde/js/syntaxhighlighter/LGPL-LICENSE
rm 
debian/php-horde-mime-viewer/usr/share/horde/js/syntaxhighlighter/MIT-LICENSE
+   cp Horde_Mime_Viewer-*/js/syntaxhighlighter/src/*.js 
debian/php-horde-mime-viewer/usr/share/horde/js/syntaxhighlighter/src/

Bug#1036347: debian-installer: missing support for RAID+LUKS+LVM via preseed

[Cyril Brulebois]

Package: partman-auto-raid
Severity: important
Tags: patch

Hi,

I'm not a preseed expert but it seems to me we're currently lacking
support for one rather common layout that's achievable via the
interactive installer, which is RAID+LUKS+LVM.

As far as I understand we support a few methods, but only *one* of
them can be chosen via partman-auto/method. The partman-auto package
intercepts “regular” and deals with it on its own, but also delegates
to partman-auto- if a different method is specified:
 - partman-auto-crypto: sets up LUKS+LVM.
 - partman-auto-lvm: sets up LVM.
 - partman-auto-raid: sets up RAID, but can also do RAID+LVM if the
   RAID specification includes the “lvm” keyword.

The fact we're supposed to be choosing one and only one method is
confirmed by looking at the implementation of each method, which
suggests they were never meant to be combined (i.e. stacked on top of
each other):
 - partman-auto-lvm ships an auto-lvm.sh library, defining functions
   like auto_lvm_prepare() and auto_lvm_perform(), which it obviously
   uses itself to implement LVM support.
 - partman-auto-crypto leverages that auto-lvm.sh library, using
   both functions directly in its autopartition-crypto script, to
   implement LUKS+LVM support.
 - partman-auto-raid also leverages that auto-lvm.sh library, but not
   as directly as partman-auto-crypto does: since auto_lvm_prepare()
   wants to create partitions, it was partially copied/adjusted in its
   initial_auto_raid_lvm script; that being said, it calls
   auto_lvm_perform() in the end; that's how it implements RAID+LVM.

Since partman-auto-raid already knows how to deal with RAID and with
RAID+LVM when the “lvm” keyword is detected, I looked into making it
support RAID+LUKS+LVM by adding support for the “crypto-lvm” keyword,
reusing the logic of the initial_auto_raid_lvm script, inserting parts
of the logic of the autopartition-crypto script in there.

Tests confirm this seems to be working fine, but I wouldn't call this
bulletproof just yet. That being said, it cannot really break existing
use cases, so I'm tempted to include this feature right away.

  
https://salsa.debian.org/installer-team/partman-auto-raid/-/commits/lvm-on-luks-on-raid

While looking at the implementation, I noticed that partman-auto-raid
doesn't declare partman-auto-lvm in its Depends despite using its
auto-lvm.sh, so I didn't add partman-crypto to Depends despite using
its crypto-base.sh. This seems to be working fine anyway, using either
a netboot-gtk build or a full-blown netinst build.

Example usage with two disks, having only /dev/sda partitioned, and
the entirety of /dev/sdb added to the RAID 0 array, alongside the 4th
partition of the first disk:

d-i partman-auto/disk string /dev/sda
d-i partman-auto/method string raid
d-i partman-auto-raid/recipe string 0 2 0 crypto-lvm - /dev/sda4#/dev/sdb .

complemented with partman-auto/{choose,expert}_recipe regarding the
actual partitioning of /dev/sda using those methods:
 - biosgrub
 - efi (fat32, /boot/efi)
 - format (ext2, /boot)
 - raid

and of course LV definitions.

This approach means that all existing settings are still considered as
usual, like those for LUKS:

d-i partman-crypto/confirm boolean true
d-i partman-crypto/passphrase string password
d-i partman-crypto/passphrase-again string password
d-i partman-crypto/weak_passphrase boolean true
d-i partman-auto-crypto/erase_disks boolean false

(I decided to also reuse the partman-auto-crypto one despite doing the
work from partman-auto-raid, but it's trivial to adjust if desired;
that's only meant to be preseeded anyway, no strings attached. That
being said, the existing RAID+LVM support is very similar, since
partman-auto-lvm/* settings are considered even if partman-auto/method
is set to “raid” and partman-auto-raid is doing the heavy lifting, see
below.)

That also applies for LVM:

d-i partman-auto-lvm/guided_size string max
d-i partman-auto-lvm/new_vg_name string main
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true
d-i partman-lvm/device_remove_lvm boolean true

I plan on polishing and sharing some complete preseed example later
on, and possibly adding a pointer from the example preseed that's
published in the installation guide (and therefore on the website).


That partman request was submitted to me a while back but I've chosen
to prioritize other topics until now, since those were beneficial to
virtually everyone and needed to be worked on in a timely fashion:
non-free-firmware, Alpha and RC releases, also trying to get a greater
autonomy with debian-cd and debian-ftp so that we could accommodate
whatever might be needed or preferred by the kernel team and the
release team as far as timings go (which seems pretty important the
closer we get to the tentative release date).

Since we've spent quite some time fixing and improving LUKS support, I
would hate it if we didn't consider 

Bug#1035005: [pkg-uWSGI-devel] Bug#1035005: [PATCH] Add Replaces on uwsgi-plugin-jvm-openjdk-11 (Closes: #1035005)

[Jonas Smedegaard]

Hi James,

Quoting James Valleroy (2023-05-19 12:33:50)
> tags 1035005 patch
> thanks
> 
> The attached patch fixes this issue. I tested by unpacking the package into a 
> Debian bullseye VM where uwsgi-plugin-jvm-openjdk-11 was already installed.

Thanks a lot.

You are quite welcome to release this as a 0-day NMU.

Otherwise I will try to find time for it (I am currently studying and in
exam season, so pretty busy...)

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

Bug#1035522: debian-security-support 11+2023.05.04 flagged for acceptance

[Holger Levsen]

On Thu, May 18, 2023 at 07:51:36PM +, Adam D Barratt wrote:
> The upload referenced by this bug report has been flagged for acceptance into 
> the proposed-updates queue for Debian bullseye.
 
thanks! how/when will it moved/be moved to bullseye-updates?


-- 
cheers,
Holger

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

 - this is fine.


signature.asc
Description: PGP signature

Bug#1036346: unblock: gosa-plugins-systems/2.8~git20211027.5741b8f-4

[Mike Gabriel]

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

Please unblock package gosa-plugins-systems

This upload fixes piuparts upgrade tests + PHP 8.2 deprecation warnings.

[ Reason ]

+  * debian/control:
++ Add more B:/R: relations to old GOsa² 2.7.x packages which this package
+  replaces. (Closes: #1034967).

-> Fix upgrade path from src:gosa 2.7 to src:gosa 2.8 (see referenced bug 
report with
installation problems that have been resolved in this upload).

+  * debian/patches:
++ Add 1001_php8.2-deprecations.patch. Amend various PHP 8.2 deprecations.

-> While at it, include various PHP 8.2 deprecation warnings that have
been spotted over the past weeks.


[ Impact ]
Resolves piupart upgrade test, fixes PHP warnings being displayed on
screen with previous versions of this package.

[ Tests ]
Manual tests, piuparts seems to be happy now.

[ Risks ]
Problems introduced by this upload will only affect GOsa² (src:pkg gosa).

[ 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 testing

[ Other info ]
There are likely more PHP 8.2 issues which I might only be able to
address as 12.x point release update.

unblock gosa-plugins-systems/2.8~git20211027.5741b8f-4
diff -Nru gosa-plugins-systems-2.8~git20211027.5741b8f/debian/changelog 
gosa-plugins-systems-2.8~git20211027.5741b8f/debian/changelog
--- gosa-plugins-systems-2.8~git20211027.5741b8f/debian/changelog   
2023-02-06 20:56:57.0 +0100
+++ gosa-plugins-systems-2.8~git20211027.5741b8f/debian/changelog   
2023-05-16 23:10:07.0 +0200
@@ -1,3 +1,13 @@
+gosa-plugins-systems (2.8~git20211027.5741b8f-4) unstable; urgency=medium
+
+  * debian/control:
++ Add more B:/R: relations to old GOsa² 2.7.x packages which this package
+  replaces. (Closes: #1034967).
+  * debian/patches:
++ Add 1001_php8.2-deprecations.patch. Amend various PHP 8.2 deprecations.
+
+ -- Mike Gabriel   Tue, 16 May 2023 23:10:07 +0200
+
 gosa-plugins-systems (2.8~git20211027.5741b8f-3) unstable; urgency=medium
 
   [ Daniel Teichmann ]
diff -Nru gosa-plugins-systems-2.8~git20211027.5741b8f/debian/control 
gosa-plugins-systems-2.8~git20211027.5741b8f/debian/control
--- gosa-plugins-systems-2.8~git20211027.5741b8f/debian/control 2023-02-06 
20:55:55.0 +0100
+++ gosa-plugins-systems-2.8~git20211027.5741b8f/debian/control 2023-05-16 
23:08:28.0 +0200
@@ -22,13 +22,19 @@
  gosa-plugin-systems (<< 2.8~),
  gosa-plugin-dns (<< 2.8~),
  gosa-plugin-dhcp (<< 2.8~),
+ gosa-plugin-gofax (<< 2.8~),
  gosa-plugin-goto (<< 2.8~),
+ gosa-plugin-mail (<< 2.8~),
+ gosa-plugin-rsyslog (<< 2.8~),
  gosa-plugins-goto,
 Replaces:
  gosa-plugin-systems (<< 2.8~),
  gosa-plugin-dns (<< 2.8~),
  gosa-plugin-dhcp (<< 2.8~),
+ gosa-plugin-gofax (<< 2.8~),
  gosa-plugin-goto (<< 2.8~),
+ gosa-plugin-mail (<< 2.8~),
+ gosa-plugin-rsyslog (<< 2.8~),
  gosa-plugins-goto,
 Provides:
  gosa-plugin-systems,
diff -Nru 
gosa-plugins-systems-2.8~git20211027.5741b8f/debian/patches/1001_php8.2-deprecations.patch
 
gosa-plugins-systems-2.8~git20211027.5741b8f/debian/patches/1001_php8.2-deprecations.patch
--- 
gosa-plugins-systems-2.8~git20211027.5741b8f/debian/patches/1001_php8.2-deprecations.patch
  1970-01-01 01:00:00.0 +0100
+++ 
gosa-plugins-systems-2.8~git20211027.5741b8f/debian/patches/1001_php8.2-deprecations.patch
  2023-03-17 12:05:45.0 +0100
@@ -0,0 +1,99 @@
+--- a/admin/systems/services/dhcp/class_servDHCP.inc
 b/admin/systems/services/dhcp/class_servDHCP.inc
+@@ -1,5 +1,6 @@
+ RecordTypes = DNS::getDnsRecordTypes(true); 
+ 
++$attrs = is_null($attrs) ? array() : $attrs;
++
+ if(!count($attrs)){
+ $this->OldZoneName= "";
+ $this->OldReverseZone = "";
+--- a/admin/systems/services/kolab/class_servKolab.inc
 b/admin/systems/services/kolab/class_servKolab.inc
+@@ -1,5 +1,6 @@
+ dn= $dn;
+ $this->config= $config;
+--- a/admin/systems/services/dns/class_servDNS.inc
 b/admin/systems/services/dns/class_servDNS.inc
+@@ -1,5 +1,6 @@
+ 

Bug#1036213: apache2: frequent SIGSEGV in mod_http2.so (purge_consumed_buckets)

[Bastien Durel]

Le jeudi 18 mai 2023 à 15:04 +0200, Bastien Durel a écrit :
> Le 18/05/2023 à 14:41, Stefan Eissing a écrit :
> > Did you have an warning message like "AH03516: unexpected NN
> > streams in hold" at that time in out error log?
> 
> No (grepping AH03516 in *.log returns nothing (nor does "streams in
> hold"))
> 
Hello. I got another one in ap_save_brigade()

-- 
Bastien


output.log.bz2
Description: application/bzip

Bug#1036345: unblock: autofs/5.1.8-2

[Mike Gabriel]

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

Please unblock package autofs

It was discovered by upstream that a previous patch introduced a
regression that leads to autofs connecting to rpcbind for NFSv4-only NFS
mounts. Upstream's fix for that has now been cherry-picked into autofs
5.1.8-2.

[ Reason ]

+  [ Mike Gabriel ]
+  * debian/patches:
++ Add fix-nfs4-only-mounts-should-not-use-rpcbind.patch. Don't let NFSv4-
+  only mounts use rpcbind portmapper service. (Closes: #1034261).

-> This is the cherry-pick patch. Encouraged by Salvatore from the
security team (though not with security team's hat on).

+  * debian/control:
++ Bump Standards-Version: to 4.6.2. No changes needed.

-> This change was already in Git (with 4.6.1, but well...). So, I kept/updated 
it.

+  * lintian:
++ Adjust syntax of various overrides.

-> Make lintian happy again, add square brackets around path names.

[ Impact ]
Impact on NFSv4-mounts in autofs.

[ Tests ]
Code review. Upstream-sanctioned patch.

[ Risks ]
Breaking of autofs with NFS.

[ 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 testing

[ Other info ]
None

unblock autofs/5.1.8-2
diff -Nru autofs-5.1.8/debian/autofs.lintian-overrides 
autofs-5.1.8/debian/autofs.lintian-overrides
--- autofs-5.1.8/debian/autofs.lintian-overrides2021-02-04 
13:31:22.0 +0100
+++ autofs-5.1.8/debian/autofs.lintian-overrides2023-05-19 
10:25:31.0 +0200
@@ -1,5 +1,5 @@
 # autofs 5.1.7 introduces autofs.a as a shared library, but we will ignore 
this for now
-sharedobject-in-library-directory-missing-soname 
usr/lib/x86_64-linux-gnu/libautofs.so
+sharedobject-in-library-directory-missing-soname 
[usr/lib/x86_64-linux-gnu/libautofs.so]
 
 # autofs.8 man page explains the overall concept of autofs
-spare-manual-page usr/share/man/man8/autofs.8.gz
+spare-manual-page [usr/share/man/man8/autofs.8.gz]
diff -Nru autofs-5.1.8/debian/changelog autofs-5.1.8/debian/changelog
--- autofs-5.1.8/debian/changelog   2021-12-01 23:52:49.0 +0100
+++ autofs-5.1.8/debian/changelog   2023-05-19 10:25:31.0 +0200
@@ -1,3 +1,16 @@
+autofs (5.1.8-2) unstable; urgency=medium
+
+  [ Mike Gabriel ]
+  * debian/patches:
++ Add fix-nfs4-only-mounts-should-not-use-rpcbind.patch. Don't let NFSv4-
+  only mounts use rpcbind portmapper service. (Closes: #1034261).
+  * debian/control:
++ Bump Standards-Version: to 4.6.2. No changes needed.
+  * lintian:
++ Adjust syntax of various overrides.
+
+ -- Mike Gabriel   Fri, 19 May 2023 10:25:31 +0200
+
 autofs (5.1.8-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru autofs-5.1.8/debian/control autofs-5.1.8/debian/control
--- autofs-5.1.8/debian/control 2021-12-01 23:52:23.0 +0100
+++ autofs-5.1.8/debian/control 2023-05-19 10:24:47.0 +0200
@@ -20,7 +20,7 @@
  sssd-common,
  libtirpc-dev,
 Rules-Requires-Root: no
-Standards-Version: 4.6.0
+Standards-Version: 4.6.2
 Homepage: https://www.kernel.org/pub/linux/daemons/autofs/v5/
 Vcs-Browser: https://salsa.debian.org/debian/autofs/
 Vcs-Git: https://salsa.debian.org/debian/autofs.git
diff -Nru 
autofs-5.1.8/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch 
autofs-5.1.8/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch
--- 
autofs-5.1.8/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch   
1970-01-01 01:00:00.0 +0100
+++ 
autofs-5.1.8/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch   
2023-05-19 10:21:20.0 +0200
@@ -0,0 +1,106 @@
+From 80845bbcbc264f19c6c6a81d680e1f2b1ea6d3cc Mon Sep 17 00:00:00 2001
+From: Ian Kent 
+Date: Sun, 31 Oct 2021 07:36:16 +0800
+Subject: autofs-5.1.8 - fix nfsv4 only mounts should not use rpcbind
+
+Commit 606795ecfaa1 ("autofs-5.1.7 - also require TCP_REQUESTED when
+setting NFS port" together with commit 26fb6b5408be) caused NFSv4 only
+mounts to also use rpcbind to probe availability which breaks the
+requirememt that this type of mount not use rpcbind at all.
+
+Fix this by treating fstype=nfs4 mounts as a special case which doesn't
+use rpcbind.
+
+Signed-off-by: Ian Kent 
+---
+# CHANGELOG|  1 +
+ include/replicated.h |  2 ++
+ modules/mount_nfs.c  | 13 +++--
+ modules/replicated.c |  4 ++--
+ 4 files changed, 12 insertions(+), 8 deletions(-)
+
+#diff --git a/CHANGELOG b/CHANGELOG
+#index 575f186..4e5e82d 100644
+#--- a/CHANGELOG
+#+++ b/CHANGELOG
+#@@ -8,6 +8,7 @@
+# - dont fail on duplicate offset entry tree add.
+# - fix loop under run in cache_get_offset_parent().
+# - bailout on rpc systemerror.
+#+- fix nfsv4 only mounts should not use rpcbind.
+# 
+# 19/10/2021 autofs-5.1.8
+# - add xdr_exports().
+diff --git a/include/replicated.h b/include/replicated.h
+index 95ff1f0..f889a56 100644
+--- 

Bug#1036343: unblock: mate-terminal/1.26.0-2

[Mike Gabriel]

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

Please unblock package mate-terminal

[ Reason ]

+  [ Martin Wimpress ]
+  * debian/patches:
++ Add 1002_fix_context_menu_font.patch (LP: #1955505, closes: #998856,
+  #1001793).

-> context menus in MATE Terminal are currently rendered with a monospace
font, but they should be rendered with the font that is configured for
menu items. The above patch (cherry-picked from upstream) fixes that.

[ Impact ]
Context menu fonts in mate-terminal fixed.

[ Tests ]
Manually, runtime test.

[ Risks ]
MATE Terminal could break.

[ 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 testing

[ Other info ]
None

unblock mate-terminal/1.26.0-2
diff -Nru mate-terminal-1.26.0/debian/changelog 
mate-terminal-1.26.0/debian/changelog
--- mate-terminal-1.26.0/debian/changelog   2021-12-13 01:28:05.0 
+0100
+++ mate-terminal-1.26.0/debian/changelog   2023-04-25 16:19:04.0 
+0200
@@ -1,3 +1,12 @@
+mate-terminal (1.26.0-2) unstable; urgency=medium
+
+  [ Martin Wimpress ]
+  * debian/patches:
++ Add 1002_fix_context_menu_font.patch (LP: #1955505, closes: #998856,
+  #1001793).
+
+ -- Mike Gabriel   Tue, 25 Apr 2023 16:19:04 +0200
+
 mate-terminal (1.26.0-1) unstable; urgency=medium
 
   [ Martin Wimpress ]
diff -Nru mate-terminal-1.26.0/debian/patches/1002_fix_context_menu_font.patch 
mate-terminal-1.26.0/debian/patches/1002_fix_context_menu_font.patch
--- mate-terminal-1.26.0/debian/patches/1002_fix_context_menu_font.patch
1970-01-01 01:00:00.0 +0100
+++ mate-terminal-1.26.0/debian/patches/1002_fix_context_menu_font.patch
2023-04-25 16:18:32.0 +0200
@@ -0,0 +1,14 @@
+Description: Add GTK Style Class to context menu
+Author: grover92000
+
+--- a/src/terminal-window.c2021-08-05 12:25:06.0 -0400
 b/src/terminal-window.c2022-02-10 12:52:40.388572997 -0500
+@@ -1554,6 +1554,8 @@ popup_clipboard_targets_received_cb (Gtk
+ NULL, NULL,
+ info->button,
+ info->timestamp);
++gtk_style_context_add_class(gtk_widget_get_style_context (popup_menu),
++GTK_STYLE_CLASS_CONTEXT_MENU);
+ }
+ 
+ static void
diff -Nru mate-terminal-1.26.0/debian/patches/series 
mate-terminal-1.26.0/debian/patches/series
--- mate-terminal-1.26.0/debian/patches/series  2021-12-13 01:28:05.0 
+0100
+++ mate-terminal-1.26.0/debian/patches/series  2023-04-25 16:18:32.0 
+0200
@@ -1 +1,2 @@
 1001_desktop-file-lacks-keywords-entry.patch
+1002_fix_context_menu_font.patch

Bug#1036344: RM: cowbell -- RoQA; RC-buggy; low popcon; dead upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove cowbell. It is RC-buggy and its upstream is dead.
The package has a low popcon and no reverse dependencies.

Bug#1036342: firefox-esr: error displaying in persepective

[Paul Pscholka]

Package: firefox-esr
Version: 102.11.0esr-1~deb11u1
Severity: normal
X-Debbugs-Cc: p...@friendlyframeworks.com

Dear Maintainer,

this is a perpective error.  must see to understand.  go to www.mallinclouds.com
/index_zeta.htm.  click the Mall Central link to see the bug.  This only shows
up on i386 version.  AMD  firefox-esr does not have this bug and chrome works
good too.

-- Package-specific info:

-- Extensions information
Name: Add-ons Search Detection
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: DoH Roll-Out
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: eBay
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: System theme — auto theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled

Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: WebCompat Reporter
Location: 
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled


-- Addons package information
ii  firefox-esr102.11.0esr-1~deb11u1 i386 Mozilla Firefox web 
browser - Extended Support Release (ESR)

-- System Information:
Debian Release: 11.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-23-686-pae (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox-esr depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libasound2   1.2.4-1.1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-13+deb11u6
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.24-0+deb11u1
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1+deb11u1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1+deb11u1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4+deb11u3
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libx11-6 2:1.7.2-1
ii  libx11-xcb1  2:1.7.2-1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.1-1
ii  libxtst6 2:1.2.3-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.3.6-0+deb11u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.18.3-6+deb11u3
ii  pulseaudio 14.2-2

-- no debconf information

Bug#1036341: unblock: mate-desktop/1.26.0-2

[Mike Gabriel]

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

Please unblock package mate-desktop

The change fixes two memleaks and one use-after-free issue in
mate-desktop, one of the core libraries of MATE Desktop Environment.

[ Reason ]

+  * debian/patches:
++ Trivial rebase of 001_prefer-x-terminal-emulator.patch.
++ Add patches 0001 and 0002. Fix two memory leaks.
++ Add patch 0003 fix use-after-free issue. (Closes: #1033719).

-> Self-explaining.

+  * debian/control:
++ In bin:pkg libmate-desktop-dev switch from libgdk-pixbuf2.0-dev
+  (deprecated) to libgdk-pixbuf-2.0-dev. Thanks, lintian.

-> libgdk-pixbuf2.0-dev deprecation, hinted by lintian.

+  * debian/copyright:
++ Update copyright attribution for debian/ folder.

-> update copyright attributions.

[ Impact ]
Minimal. MATE Desktop Environment will be affected by this change, ideally to 
the better.

[ Tests ]
Manual package test. Patch review. Patches already applied in new
upstream release 1.26.1.

[ Risks ]
If patches are bad or introduce regressions, MATE Desktop might break /
suffer from the change.

[ 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 testing

[ Other info ]
None

unblock mate-desktop/1.26.0-2
diff -Nru mate-desktop-1.26.0/debian/changelog 
mate-desktop-1.26.0/debian/changelog
--- mate-desktop-1.26.0/debian/changelog2021-12-10 20:59:48.0 
+0100
+++ mate-desktop-1.26.0/debian/changelog2023-04-25 16:35:44.0 
+0200
@@ -1,3 +1,17 @@
+mate-desktop (1.26.0-2) unstable; urgency=medium
+
+  * debian/patches:
++ Trivial rebase of 001_prefer-x-terminal-emulator.patch.
++ Add patches 0001 and 0002. Fix two memory leaks.
++ Add patch 0003 fix use-after-free issue. (Closes: #1033719).
+  * debian/control:
++ In bin:pkg libmate-desktop-dev switch from libgdk-pixbuf2.0-dev
+  (deprecated) to libgdk-pixbuf-2.0-dev. Thanks, lintian.
+  * debian/copyright:
++ Update copyright attribution for debian/ folder.
+
+ -- Mike Gabriel   Tue, 25 Apr 2023 16:35:44 +0200
+
 mate-desktop (1.26.0-1) unstable; urgency=medium
 
   [ Martin Wimpress ]
diff -Nru mate-desktop-1.26.0/debian/control mate-desktop-1.26.0/debian/control
--- mate-desktop-1.26.0/debian/control  2021-12-10 20:59:48.0 +0100
+++ mate-desktop-1.26.0/debian/control  2023-04-25 16:35:44.0 +0200
@@ -100,7 +100,7 @@
 Architecture: any
 Multi-Arch: same
 Depends: libdconf-dev,
- libgdk-pixbuf2.0-dev,
+ libgdk-pixbuf-2.0-dev,
  libgtk-3-dev,
  libmate-desktop-2-17 (= ${binary:Version}),
  libstartup-notification0-dev,
diff -Nru mate-desktop-1.26.0/debian/copyright 
mate-desktop-1.26.0/debian/copyright
--- mate-desktop-1.26.0/debian/copyright2021-12-10 20:59:48.0 
+0100
+++ mate-desktop-1.26.0/debian/copyright2023-04-25 16:35:44.0 
+0200
@@ -232,7 +232,7 @@
 
 Files: debian/*
 Copyright: 2011-2013, Stefano Karapetsas 
-   2013-2015, Mike Gabriel 
+   2013-2023, Mike Gabriel 
 License: GPL-2+ or LGPL-2+ or Expat
 
 License: GPL-2+
diff -Nru mate-desktop-1.26.0/debian/patches/0001_mate-bg-fix-memory-leak.patch 
mate-desktop-1.26.0/debian/patches/0001_mate-bg-fix-memory-leak.patch
--- mate-desktop-1.26.0/debian/patches/0001_mate-bg-fix-memory-leak.patch   
1970-01-01 01:00:00.0 +0100
+++ mate-desktop-1.26.0/debian/patches/0001_mate-bg-fix-memory-leak.patch   
2023-04-25 16:30:40.0 +0200
@@ -0,0 +1,30 @@
+From 2fbe25e7ad9c7678db2f3e34f76c9ee4e37d80d9 Mon Sep 17 00:00:00 2001
+From: rbuj 
+Date: Mon, 8 Nov 2021 12:44:21 +0100
+Subject: [PATCH] mate-bg: fix memory leak
+
+---
+ libmate-desktop/mate-bg.c | 10 +++---
+ 1 file changed, 7 insertions(+), 3 deletions(-)
+
+diff --git a/libmate-desktop/mate-bg.c b/libmate-desktop/mate-bg.c
+index e5119759e..62cc5e59e 100644
+--- a/libmate-desktop/mate-bg.c
 b/libmate-desktop/mate-bg.c
+@@ -3197,9 +3197,13 @@ mate_bg_changes_with_time (MateBG *bg)
+   if (!bg->filename)
+   return FALSE;
+ 
+-  show = get_as_slideshow (bg, bg->filename);
+-  if (show)
+-  return g_queue_get_length (show->slides) > 1;
++  if ((show = get_as_slideshow (bg, bg->filename)) != NULL) {
++  gboolean result;
++
++  result = (g_queue_get_length (show->slides) > 1) ? TRUE : FALSE;
++  slideshow_unref (show);
++  return result;
++  }
+ 
+   return FALSE;
+ }
diff -Nru 
mate-desktop-1.26.0/debian/patches/0002_mate-desktop-thumbnail-fix-memory-leak.patch
 
mate-desktop-1.26.0/debian/patches/0002_mate-desktop-thumbnail-fix-memory-leak.patch
--- 
mate-desktop-1.26.0/debian/patches/0002_mate-desktop-thumbnail-fix-memory-leak.patch
1970-01-01 01:00:00.0 +0100
+++ 

Bug#1036340: unblock: mate-polkit/1.26.1-3

[Mike Gabriel]

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

Please unblock package mate-polkit

The mate-polkit XDG autostart launcher would not execute properly on
non-amd64 architectures due to the executable being installed into a
multi-arch path while the XDG autostart .desktop file would always
reference the amd64 path. Also, the .desktop file gets installed via the
mate-polkit-common package which makes the situation more complex.

The solution was to install the mate-polkit executable into /usr/libexec
for all architectures and adjust the multi-arch tags in the bin:pkgs.


[ Reason ]
+  [ Thomas Uhle ]
+  * debian/:
++ Move polkit-agent executable to /usr/libexec directory. Move man page
+  into mate-polkit-bin bin:pkg. (Closes: #1006996). Re-adjust inter-package
+  relations and bin:pkg architecture declarations. Remove remnants of this
+  package being a shared library once (i.e. drop Multi-Arch: fields).

-> This change tackles the above mention architecture problem on non-amd64.

+  * debian/rules:
++ Drop duplicate --disable-silent-rules from configure run.

-> Cleaning up d/rules dh_configure override.

+  [ Mike Gabriel ]
+  * debian/control:
++ Switch from D: policykit-1 (deprecated) to polkitd. (Closes: #1025598).

-> policykit-1 deprecation fix.

+  * debian/copyright:
++ Update copyright attributions for debian/.

-> Adjust copyright attributions.

[ Impact ]
MATE can be used out-of-the-box on other architectures except from amd64.

[ Tests ]
Manual installation on amd64 and arm64.

[ Risks ]
MATE on amd64 might break, but manual tests do not hint that.

[ 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 testing

[ Other info ]
None.

unblock mate-polkit/1.26.1-3
diff -Nru mate-polkit-1.26.1/debian/bin/mate-polkit 
mate-polkit-1.26.1/debian/bin/mate-polkit
--- mate-polkit-1.26.1/debian/bin/mate-polkit   1970-01-01 01:00:00.0 
+0100
+++ mate-polkit-1.26.1/debian/bin/mate-polkit   2023-04-25 14:57:11.0 
+0200
@@ -0,0 +1,3 @@
+#!/bin/sh
+
+/usr/libexec/polkit-mate-authentication-agent-1 &
diff -Nru mate-polkit-1.26.1/debian/bin/mate-polkit.in 
mate-polkit-1.26.1/debian/bin/mate-polkit.in
--- mate-polkit-1.26.1/debian/bin/mate-polkit.in2019-02-02 
01:45:22.0 +0100
+++ mate-polkit-1.26.1/debian/bin/mate-polkit.in1970-01-01 
01:00:00.0 +0100
@@ -1,3 +0,0 @@
-#!/bin/sh
-
-/usr/lib/@DEB_HOST_MULTIARCH@/polkit-mate/polkit-mate-authentication-agent-1 &
diff -Nru mate-polkit-1.26.1/debian/changelog 
mate-polkit-1.26.1/debian/changelog
--- mate-polkit-1.26.1/debian/changelog 2022-10-16 22:15:12.0 +0200
+++ mate-polkit-1.26.1/debian/changelog 2023-04-25 16:12:33.0 +0200
@@ -1,3 +1,28 @@
+mate-polkit (1.26.1-3) unstable; urgency=medium
+
+  * Re-upload source-only. (By mistake, previous upload was src+amd64 upload).
+
+ -- Mike Gabriel   Tue, 25 Apr 2023 16:12:33 +0200
+
+mate-polkit (1.26.1-2) unstable; urgency=medium
+
+  [ Thomas Uhle ]
+  * debian/:
++ Move polkit-agent executable to /usr/libexec directory. Move man page
+  into mate-polkit-bin bin:pkg. (Closes: #1006996). Re-adjust inter-package
+  relations and bin:pkg architecture declarations. Remove remnants of this
+  package being a shared library once (i.e. drop Multi-Arch: fields).
+  * debian/rules:
++ Drop duplicate --disable-silent-rules from configure run.
+
+  [ Mike Gabriel ]
+  * debian/control:
++ Switch from D: policykit-1 (deprecated) to polkitd. (Closes: #1025598).
+  * debian/copyright:
++ Update copyright attributions for debian/.
+
+ -- Mike Gabriel   Tue, 25 Apr 2023 13:15:11 +
+
 mate-polkit (1.26.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mate-polkit-1.26.1/debian/control mate-polkit-1.26.1/debian/control
--- mate-polkit-1.26.1/debian/control   2022-10-16 22:14:50.0 +0200
+++ mate-polkit-1.26.1/debian/control   2023-04-25 15:12:24.0 +0200
@@ -26,7 +26,8 @@
 Architecture: all
 Depends: mate-polkit (>= ${source:Version}),
  ${misc:Depends},
-Breaks: mate-polkit (<< 1.12.0-3~),
+Breaks: mate-polkit (<< 1.26.1-2~),
+Replaces: mate-polkit (<< 1.26.1-2~),
 Description: MATE authentication agent for PolicyKit-1 (executable wrapper 
script)
  The mate-polkit package provides a D-Bus session bus service that is used to
  bring up authentication dialogs used for obtaining privileges.
@@ -40,10 +41,9 @@
 
 Package: mate-polkit
 Architecture: any
-Multi-Arch: same
 Depends: accountsservice,
- mate-polkit-common (= ${binary:Version}),
- policykit-1,
+ mate-polkit-common (>= ${source:Version}),
+ polkitd,
  ${misc:Depends},
  ${shlibs:Depends},
 Provides: polkit-1-auth-agent,
@@ -54,10 +54,8 @@
  This package contains the MATE policy kit authentication agent.
 
 

Bug#1036339: O: grub-splashimages -- collection of GRUB splashimages

[Bastian Germann]

Package: wnpp
X-Debbugs-Cc: pkg-grub-de...@alioth-lists.debian.net

The grub-splashimages package is obviously not maintained by the grub team 
anymore.
I hereby orphan it. Please only consider adopting it if you can afford the time.

Bug#1036338: O: grub2-splashimages -- collection of GRUB2 splashimages

[Bastian Germann]

Package: wnpp
X-Debbugs-Cc: pkg-grub-de...@alioth-lists.debian.net

The grub2-splashimages package is obviously not maintained by the grub team 
anymore.
I hereby orphan it. Please only consider adopting it if you can afford the time.

Bug#1032969: mdadm initrd scripts reference command not present in initrd

[Daniel Baumann]

close 1032969 4.2+20230508-1
thanks

Hi,

this has been fixed by newer mdadm, at least above version, thus closing
the bug.

Regards,
Daniel

Bug#1035999: Debian 12 rc2 error: 'mdadm: No arrays found in config file or automatically'

[Daniel Baumann]

tag 1035999 + moreinfo
thanks

Hi Bill,

thank you for your report. In order to reproduce it, I've got some
questions for you:

  * you were using a live image, did you install with 'debian-installer'
(the "Install" item in the boot menu) or 'calamares' (an installer
application you can start in KDE)?

  * encrypted LVM: which "order" did you use, encrypted partition and
LVM in it, or LVM and then encrypted partitions in it?

Regards,
Daniel

Bug#1036337: RM: sgml2x -- RoQA; RC-buggy; low popcon; dead upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove sgml2x. It is RC-buggy and its upstream is dead.
The package has a low popcon and no reverse dependencies.

Bug#1036336: RM: sqsh -- RoQA; RC-buggy; low popcon; inactive upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove sqsh. It is RC-buggy and upstream is inactive since 2014.
The package has a low popcon and no reverse dependencies. Last release to 
contain the package was buster.

Bug#965823: socket: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru socket-1.1/BLURB socket-1.1/BLURB
--- socket-1.1/BLURB2023-05-19 14:02:02.0 +0200
+++ socket-1.1/BLURB1996-02-08 23:53:39.0 +0100
@@ -1,6 +1,6 @@
 This is release 1.1 of the Socket(1) program.
 
-Socket(1) implements an interface to TCP and UNIX sockets at shell level.
+Socket(1) implements an interface to TCP sockets at shell level.
 Client and server sockets can be used from shell scripts or
 interactively.  Socket can also run a program with stdin, stdout, and
 stderr connected to the socket connection.  Sample shell scripts
diff -Nru socket-1.1/CHANGES socket-1.1/CHANGES
--- socket-1.1/CHANGES  2023-05-19 14:02:02.0 +0200
+++ socket-1.1/CHANGES  1996-02-08 23:53:39.0 +0100
@@ -17,5 +17,3 @@
 message
 
   - slightly more adequate signal handling and messages
-
-  - support of UNIX domain sockets
diff -Nru socket-1.1/debian/changelog socket-1.1/debian/changelog
--- socket-1.1/debian/changelog 2023-05-19 14:02:02.0 +0200
+++ socket-1.1/debian/changelog 2023-05-19 13:56:24.0 +0200
@@ -1,3 +1,13 @@
+socket (1.1-10.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update debhelper compat to 7. (closes: #965823)
+  * Add missing rules targets. (closes: #999271)
+  * Enable cross build. (closes: #922373)
+  * Convert to source format 3.0 (quilt).
+
+ -- Bastian Germann   Fri, 19 May 2023 13:56:24 +0200
+
 socket (1.1-10) unstable; urgency=low
 
   * (Re-) Adopting the package. (closes: #487341)
diff -Nru socket-1.1/debian/compat socket-1.1/debian/compat
--- socket-1.1/debian/compat2023-05-19 14:02:02.0 +0200
+++ socket-1.1/debian/compat2023-05-19 13:54:14.0 +0200
@@ -1 +1 @@
-5
+7
diff -Nru socket-1.1/debian/control socket-1.1/debian/control
--- socket-1.1/debian/control   2023-05-19 14:02:02.0 +0200
+++ socket-1.1/debian/control   2023-05-19 13:54:09.0 +0200
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: LENART Janos 
-Build-Depends: debhelper (>> 5.0.0)
+Build-Depends: debhelper (>= 7)
 Standards-Version: 3.8.1
 
 Package: socket
diff -Nru socket-1.1/debian/patches/debian.patch 
socket-1.1/debian/patches/debian.patch
--- socket-1.1/debian/patches/debian.patch  1970-01-01 01:00:00.0 
+0100
+++ socket-1.1/debian/patches/debian.patch  2023-05-19 13:56:24.0 
+0200
@@ -0,0 +1,1061 @@
+--- socket-1.1.orig/BLURB
 socket-1.1/BLURB
+@@ -1,6 +1,6 @@
+ This is release 1.1 of the Socket(1) program.
+ 
+-Socket(1) implements an interface to TCP sockets at shell level.
++Socket(1) implements an interface to TCP and UNIX sockets at shell level.
+ Client and server sockets can be used from shell scripts or
+ interactively.  Socket can also run a program with stdin, stdout, and
+ stderr connected to the socket connection.  Sample shell scripts
+--- socket-1.1.orig/CHANGES
 socket-1.1/CHANGES
+@@ -17,3 +17,5 @@ User-visible changes in Socket version 1
+ message
+ 
+   - slightly more adequate signal handling and messages
++
++  - support of UNIX domain sockets
+--- socket-1.1.orig/Makefile
 socket-1.1/Makefile
+@@ -8,13 +8,13 @@
+ ### socket.1 in /usr/local/man/man1/socket.1
+ ### Make sure the target directories exist before doing a "make install".
+ 
+-INSTALLBASE = /usr/local
++INSTALLBASE = $(DESTDIR)/usr
+ INSTALLBINPATH = $(INSTALLBASE)/bin
+ INSTALLBINMODE = 755
+ INSTALLMANPATH = $(INSTALLBASE)/man
+-INSTALLMANMODE = 444
++INSTALLMANMODE = 644
+ CC = cc
+-CFLAGS  = $(SWITCHES) -O
++CFLAGS  = $(SWITCHES) -O2
+ LDFLAGS = $(SWITCHES) -s
+ 
+ ### You may need to uncomment some lines below for your operating
+@@ -78,7 +78,7 @@ tags: TAGS
+ TAGS: $(PROGSOURCES) $(HEADERS)
+   etags $(PROGSOURCES) $(HEADERS)
+ 
+-installtargets: $(INSTALLBINPATH)/$(TARGET) installmanuals
++installtargets: $(INSTALLBINPATH)/$(TARGET)
+ 
+ $(INSTALLBINPATH)/$(TARGET): $(TARGET)
+   @-echo "installing $(TARGET) in $(INSTALLBINPATH)"; \
+--- socket-1.1.orig/README
 socket-1.1/README
+@@ -9,7 +9,7 @@ this program is licensed to you.
+ 
+ What is it?
+ 
+-The program Socket implements access to TCP sockets from shell level.
++The program Socket implements access to TCP or UNIX sockets from shell level.
+ First written for the need to open a server socket and read and write
+ to the socket interactively for testing purposes, it quickly evolved
+ into a generic tool providing the socket interface for shell script
+@@ -19,7 +19,8 @@ and interactive use.
+ Client mode
+ 
+ In client mode (which is the default) it connects to a given port at a
+-given host.  Data read from the socket is written to stdout, data read
++given host or to a given UNIX domain socket specified by a pathname on the
++local filesystem(s). Data read from the socket is written to stdout, data read
+ from stdin is written to the socket.  When the peer closes the
+ connection or a signal is received, the program terminates.  An
+ 

Bug#1035976: aptitude dies with SEGV

[Harald Dunkel]

Any news? Could you read something from the strace output?


Regards

Harri

Bug#1033696: mdadm: dangling link to mdadm-shutdown.service

[Daniel Baumann]

close 1033696
thanks

Hi Christoph,

thank you for your report.

The problem you're describing sounds like #1031695 from
dh_installsystemd. However, when looking at the mdadm 4.2-5 .deb file,
it's not affected by that.

Installing it on a clean system (with and without merged-usr) works both
as expected (no dangling symlinks; all systemd files in /lib/systemd,
not /usr/lib/systemd).

Also I can't think of anything that would triggered that within the mdadm.

Given all of the above, I think it must have been a transient problem
that was caused by something outside of mdadm (and which I can't
influence on the mdadm side). In any way, nothing I can do something
about in mdadm, hence closing this bug.

Regards,
Daniel

Bug#1036335: coreutils: "who returns an id instead of a datetime"

[DorianCoding]

Package: coreutils
Version: 9.1-1
Severity: normal
X-Debbugs-Cc: b...@securemyvpn.com

Dear Maintainer,

When I do who, I get the following :

frederic pts/03243058749271606713 (192.168.1.45)

However, doing a utmpdump on the /var/run/utmp does return a valid datetime.
This number does not seem to correspond to a UNIX timestamp as it can increase 
and decrease.

How can I solve this?



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

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

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


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux bookworm/sid
Release:n/a
Codename:   bookworm
Architecture: armv7l

Kernel: Linux 6.1.21-v7+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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)

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-8+rpi1
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b2

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information

Bug#1036334: bugz.1: Missing SEE ALSO

[Alejandro Colomar]

Package: bugz
Version: 0.13-3
Severity: normal
Tags: upstream
X-Debbugs-Cc: Alastair Tse , Markus Meier 
, Dylan Baker , William Hubbs 
, a...@kernel.org


Hi!

The manual page doesn't have a SEE ALSO section, so it's hard to find
the documentation for the config file.  I see that the master branch has
this issue fixed, but there hasn't been a release since then (2017).

Is the upstream project still maintained?

Cheers,
Alex

-- System Information:
Debian Release: 12.0
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages bugz depends on:
ii  python3  3.11.2-1+b1

bugz recommends no packages.

bugz suggests no packages.

-- no debconf information

Bug#1036333: RM: snmpkit -- RoQA; RC-buggy; low popcon; inaccurate upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove snmpkit. It is RC-buggy (including empty package) and the documented upstream is inactive (but the Debian 
version 0.9 is from an undocumented place). The package has a low popcon and no reverse dependencies.

Bug#1036332: RM: smbc -- RoQA; RC-buggy; low popcon; inactive upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove smbc. It is RC-buggy (with patch) and upstream is inactive.
The package has a low popcon and no reverse dependencies. Last release to 
contain the package was buster.

Bug#999274: datapacker: missing required debian/rules targets build-arch and/or build-indep

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru datapacker-1.0.3/debian/changelog 
datapacker-1.0.3+nmu1/debian/changelog
--- datapacker-1.0.3/debian/changelog   2021-01-13 07:08:09.0 +0100
+++ datapacker-1.0.3+nmu1/debian/changelog  2023-05-19 12:43:26.0 
+0200
@@ -1,3 +1,11 @@
+datapacker (1.0.3+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing debian/rules targets build-indep, build-arch.  Closes: #999274
+  * Remove unused Build-Depends: gtk-doc-tools, sgml2x.
+
+ -- Bastian Germann   Fri, 19 May 2023 12:43:26 +0200
+
 datapacker (1.0.3) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru datapacker-1.0.3/debian/control datapacker-1.0.3+nmu1/debian/control
--- datapacker-1.0.3/debian/control 2021-01-13 07:08:09.0 +0100
+++ datapacker-1.0.3+nmu1/debian/control2023-05-19 12:43:26.0 
+0200
@@ -3,7 +3,6 @@
 Priority: optional
 Maintainer: John Goerzen 
 Build-Depends: debhelper-compat (= 12), groff, docbook-utils, man-db, 
ghostscript,
- gtk-doc-tools, sgml2x,
  ghc (>= 6.8), haskell-devscripts (>= 0.6.6), libghc-missingh-dev (>= 1.0.1),
  libghc-unix-dev, libghc-mtl-dev, libghc-filepath-dev, libghc-hslogger-dev
 Build-Conflicts: docbook-ebnf
diff -Nru datapacker-1.0.3/debian/rules datapacker-1.0.3+nmu1/debian/rules
--- datapacker-1.0.3/debian/rules   2021-01-13 07:08:09.0 +0100
+++ datapacker-1.0.3+nmu1/debian/rules  2023-05-19 12:41:41.0 +0200
@@ -89,4 +89,8 @@
dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+.PHONY: build clean binary-indep binary-arch binary install configure 
build-indep build-arch
+
+build-indep:
+
+build-arch: build

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

[Martin Hostettler]

On Fri, May 19, 2023 at 11:09:41AM +0200, Helmut Grohne wrote:
> On Fri, May 19, 2023 at 10:27:46AM +0200, Martin Hostettler wrote:
> 
> Do I understand correctly that all we have to do here is ship the file
> in its "canonical" path after resolving the symbolic link from
> python3-notebook? In other words, a simple file move in the data.tar?

If dpkg can handle that even with the symlink, then i think, yes.

> 
> > I have no clue how the correct way to make this switch in the debian
> > packaging is, but i hope this messages helps to confirm what is happening
> > in this situation and someone with more solid clue about these kind of
> > problems in packaging can resolve this.
> 
> It is as simple as adding a mv invocation to an
> appropriate override_dh_something to debian/rules. That's something that
> easily passes an unblock request with the release team.
> 
> Probably, appending to override_dh_auto_install is sufficient:
> 
> mv 
> debian/cadabra2/usr/lib/python3/dist-packages/notebook/static/components 
> debian/cadabra2/usr/lib/share/javascript
> rmdir debian/cadabra2/usr/lib/python3/dist-packages/notebook/static
> rmdir debian/cadabra2/usr/lib/python3/dist-packages/notebook
> 

It seems what is needed is this:

   mv 
debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components 
debian/cadabra2/usr/share/javascript
   rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
   rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook

(The wildcards are used to avoid hard coding the current debian default
python version)

That results in a debdiff like this:
 
Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/share/javascript/codemirror/mode/cadabra/cadabra.js

Files in first .deb but not in second
-
-rw-r--r--  root/root   
/usr/lib/python3/dist-packages/notebook/static/components/codemirror/mode/cadabra/cadabra.js


Which looks ok.

both before the patch and after the following file exists when
python3-notebook was installed before installing cadabra:

/usr/share/javascript/codemirror/mode/cadabra/cadabra.js


I just noticed that the override_dh_auto_install also contains a line not
yet updated to python 3.11

> sed -i s,python3.10,python3,g debian/cadabra2/usr/bin/cadabra2

Updateing that might be a good idea too. Switching that to 3.11 results in
the further debdiff:

Control files: lines which differ (wdiff format)

Depends: fonts-cmu, python3 (<< 3.12), python3 (>= 3.11~), [-python3.11:any,-] 
python3:any (>= 3.6~)

Which seems ok too.

@G�rkan Myczko

Could you see if that seems sane and if it is do an upload with the moved
file? (I'm not a DD, so i can't help out with that)

 - Martin

Bug#1036331: unblock: squidguard/1.6.0-4

[Joachim Wiedorn]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: squidgu...@packages.debian.org
Control: affects -1 + src:squid

Please unblock package squid

This fixes RC bug #1036028 which could affect users upgrading from
bullseye to bookworm.

unblock squidguard/1.6.0-4


diff -Nru squidguard-1.6.0/debian/changelog squidguard-1.6.0/debian/changelog
--- squidguard-1.6.0/debian/changelog   2022-03-18 08:38:18.0 +0100
+++ squidguard-1.6.0/debian/changelog   2023-05-16 16:22:49.0 +0200
@@ -1,3 +1,9 @@
+squidguard (1.6.0-4) unstable; urgency=medium
+
+  * Fix dependency to squid-openssl | squid. Closes: #1036028
+
+ -- Joachim Wiedorn   Tue, 16 May 2023 16:22:49 +0200
+
 squidguard (1.6.0-3) unstable; urgency=medium
 
   * Recompiling with newer libc.
diff -Nru squidguard-1.6.0/debian/control squidguard-1.6.0/debian/control
--- squidguard-1.6.0/debian/control 2022-03-18 08:38:18.0 +0100
+++ squidguard-1.6.0/debian/control 2023-05-16 16:21:06.0 +0200
@@ -13,7 +13,7 @@
 Package: squidguard
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: squid (>= 3.4.0), liburi-perl, libwww-perl
+Recommends: squid-openssl | squid, liburi-perl, libwww-perl
 Suggests: ldap-utils, squidguard-doc
 Description: filter and redirector plugin for Squid
  squidGuard is a free, flexible and ultra fast filter, redirector
diff -Nru squidguard-1.6.0/debian/copyright squidguard-1.6.0/debian/copyright
--- squidguard-1.6.0/debian/copyright   2022-03-18 08:38:18.0 +0100
+++ squidguard-1.6.0/debian/copyright   2023-05-16 16:19:47.0 +0200
@@ -19,7 +19,7 @@
 License: W3C-Software
 
 Files: debian/*
-Copyright: 2010-2022, Joachim Wiedorn 
+Copyright: 2010-2023, Joachim Wiedorn 
 License: GPL-2
 
 



squidguard_160-4.debdiff
Description: Binary data


pgp1JqJSbnBV_.pgp
Description: Digitale Signatur von OpenPGP

Bug#1035005: [PATCH] Add Replaces on uwsgi-plugin-jvm-openjdk-11 (Closes: #1035005)

[James Valleroy]

tags 1035005 patch
thanks

The attached patch fixes this issue. I tested by unpacking the package into a 
Debian bullseye VM where uwsgi-plugin-jvm-openjdk-11 was already installed.

--
James
From 84fe0c6bbf87399eb651b3768f6599bc08a83a78 Mon Sep 17 00:00:00 2001
From: James Valleroy 
Date: Thu, 18 May 2023 08:28:17 -0400
Subject: [PATCH] Add Replaces on uwsgi-plugin-jvm-openjdk-11 (Closes:
 #1035005)

---
 debian/control | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/control b/debian/control
index 2abd38b3..fad8a587 100644
--- a/debian/control
+++ b/debian/control
@@ -616,6 +616,8 @@ Depends:
  uwsgi-core (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends},
+Replaces: uwsgi-plugin-jvm-openjdk-11 (<< 2.0.21-1)
+Breaks: uwsgi-plugin-jvm-openjdk-11 (<< 2.0.21-1)
 Description: Java plugin for uWSGI (OpenJDK 17)
  uWSGI presents a complete stack for networked/clustered web applications,
  implementing message/object passing, caching, RPC and process management.
-- 
2.39.2



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1036330: RM: sac -- RoQA; RC-buggy; low popcon; dead upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove sac. It is RC-buggy and upstream is dead.
The package has a low popcon and no reverse dependencies.

Bug#1036329: RM: resample -- RoQA; RC-buggy; low popcon; dead upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove resample. It is RC-buggy and upstream is dead.
The package has a low popcon and no reverse dependencies.

Bug#1036328: RM: remem -- RoQA; RC-buggy; low popcon; dead upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove remem. It is RC-buggy and upstream is dead.
The package has a low popcon and no reverse dependencies.

Bug#1036327: RM: portreserve -- RoQA; RC-buggy; low popcon; inactive upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove portreserve. It is RC-buggy and upstream is inactive since 2011.
The package has a low popcon and no reverse dependencies.

Bug#1036326: RM: mkelfimage -- RoQA; RC-buggy; low popcon; dead upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove mkelfimage. It is RC-buggy and upstream is dead (was removed from 
coreboot 4.1).
The package has a low popcon and no reverse dependencies.

Bug#1036325: RM: drac -- RoQA; RC-buggy; orphaned; low popcon; dead upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove drac. It has long-standing, trivial RC bugs and is orphaned.
The package has no reverse dependencies and upstream is dead.

Bug#1036324: RM: aiscm -- RoQA; RC-buggy; orphaned; low popcon; llvm-13 dependency

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove aiscm. It has an RC bug that upstream is not interested in fixing.
The package is orphaned has no reverse dependencies.
It also depends on llvm 13 which is requested to be removed.

Bug#1023739: sipsak: Message mode causes segmentation fault

[Tech]

Package: sipsak
Version: 0.9.8.1-1
Followup-For: Bug #1023739

Dear Maintainer,

This problem is still existing in Bullseye as well as in the next stable 
Bookworm

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

Kernel: Linux 5.10.0-23-amd64 (SMP w/2 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sipsak depends on:
ii  libc-ares2   1.17.1-1+deb11u2
ii  libc62.31-13+deb11u6
ii  libgnutls30  3.7.1-5+deb11u3

sipsak recommends no packages.

sipsak suggests no packages.

-- no debconf information

Bug#1036323: RM: bit-babbler -- RoQA; RC-buggy; orphaned; low popcon

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove bit-babbler. It has long-standing, trivial RC bugs and is 
orphaned.
The package has no reverse dependencies.

Bug#1036322: RM: swac-get -- RoQA; RC-buggy; low popcon; inactive upstream

[Bastian Germann]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove swac-get. It is RC-buggy and upstream is inactive.
The package has a low popcon and no reverse dependencies.

Bug#1036321: rootskel-gtk: Include metadata about the banner

[Cyril Brulebois]

Package: rootskel-gtk
Version: 12.0.1
Severity: normal

Hi,

Until now, we've always been favoring one side of the banner, and that's
been encoded in cdebconf-gtk: starting the installer in “Rescue” will
result in a (translated) label being printed on top of the banner,
either on the left or on the right. That's currently hardcoded in
cdebconf-gtk and that needs to be adjusted depending on where the Debian
name, logo, version number etc. end up for a given banner.

It would probably make sense to have a small metadata file that could be
picked up by cdebconf-gtk.

Maybe something like logo_debian.properties (or whatever name) with:

labelPosition=right
bannerExpands=right

and having cdebconf-gtk deal with default settings (e.g. right for
both). I'm not yet sure about whether it would make sense to support
bannerExpands=both (probably doesn't cost much more, but would that look
OK?).

I'm tempted to try and get that squeezed in finally (#745359 was almost
10 years ago, and the scaling trick was better than nothing, but clearly
not ideal); we can always refine the format later on.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#977037:

[Tim Andersson]

Hi Paul,

We've been discussing this amongst ourselves recently, and decided to open
up some communication about this bug/feature request. We looked at trying
to add timestamps in the way we wrap the autopkgtest runner, but ultimately
decided it made more sense and was cleaner to try and do something upstream
in autopkgtest.

I have a couple of questions regarding implementation. We thought it best
to get your feedback before creating an upstream MR.

I think it'd be possible to alter the tee command in the setup_trace
function in the autopkgtest executable to incorporate `ts`:
```
out_tee = subprocess.Popen(['tee', fifo_log],
stdin=subprocess.PIPE)
err_tee = subprocess.Popen(['tee', fifo_log, '-a', '/dev/stderr'],
stdin=subprocess.PIPE,
stdout=open('/dev/null', 'wb'))
```
But this'd make autopkgtest depend on the `moreutils` package.

Another option would be to have a different longer command which
essentially does the same as ts, but this removes the need for `moreutils`
as a dependency. Something like this:
```

exec &> >(stdbuf -o0 sed 's/%/%%/g' | xargs -d '\n' -I {} date '+%F %T
{}' | tee -a "/tmp/std.log" >/dev/null )

```
Another option to explore would be to add a similar option to the various
subprocesses in the runner executable. I worry by adding ts (or another
option) directly to the setup_trace function, we would get duplicate
timestamps, given that the autopkgtest runner uses adtlog, which already
has timestamps. So the main process has appropriate logs, but the
subprocesses do not.

Please let me know any feedback you have on the above ideas.

Regards,
Tim