Bug#1006702:

[Daniel Black]

They won't crash, because the CPU features are tested before any call
to the optimized code is made.

https://github.com/MariaDB/server/blob/10.6/mysys/crc32/crc32c.cc#L542-L564

As the Debian CI undoubtedly runs the basic unit tests that cover
crc32 on the minimum hardware, and succeeds, it proves the
autodetection is correct.

Bug#1006457: Chromium fails to start on aarch64 systems

[Andres Salomon]

On Fri, 25 Feb 2022 20:45:55 +0100 MichaIng wrote:
>
> Package: chromium
> Version: 98.0.4758.102-1~deb11u1
>
> Latest Chromium on Debian Bullseye fails to start on aarch64/arm64
> systems. Different ones with different kernels were tested, though all

> Linux 5.10 variants, using (and generally supporting) modesetting DDX.


Which boards did you test with?


>
> Only v98 from security repo is affected, v90 from "regular" Bullseye
> repo starts fine.
>
> ---
> [2380:2380:0220/184034.039483:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.122230:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.167681:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.198424:ERROR:system_web_app_manager.cc(320)]
> Exceeded SWA install retry attempts. Skipping installation, will retry
> on next OS update or when locale changes.
> [2380:2380:0220/184034.200305:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.225990:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.240862:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> 
[2380:2380:0220/184034.240968:FATAL:gpu_data_manager_impl_private.cc(448)]

> GPU process isn't usable. Goodbye.
> ---
>
> The X server itself works well, any other X application starts fine, X
> server logs show no errors, but a regular exit like when you exit the X

> client. It's hence definitely Chromium itself which fails. We tried all


What desktops were you using? Was this under X or wayland? Does it make 
a difference if you run chromium with --ozone-platform=x11 or 
--ozone-platform=wayland ?  What about --use-gl=desktop ?



> kind of GPU related flags, like "--disable-gpu", changing renderer,
> disabling GPU rasterization and all such, any combination or skipping
> all of them, even the ones shipped by default with the package
> (/etc/chromium.d) makes no difference. Starting with xinit (as root),
> startx or from desktop doesn't make a difference either.
>
> Best regards,
>
> Micha
>
>

Bug#1006676: Null pointer reference vulnerability in Agentxtrap

[Craig Small]

Hi,
  My understanding of this issue is you are starting agentxtrap on the
command line and then doing something to it to make argv[0] = NULL ?
I can see how this is possible in a debugger, but is there any way of doing
this outside a debugger or something that is directly writing to the
process memory?

Assuming argv[0] is some value is a reasonable assumption I would have
thought.

 - Craig


On Wed, 2 Mar 2022 at 17:39, bi bi  wrote:

> Package: snmp
> Version: 5.9.1 (Previous versions should also have these vulnerabilities)
>
>   We found one bug in snmp by fuzzing. Here is the vulnerability info and 
> poc. Please assist us to get the cve number, it is very important to us.
>
>   Discover: Yingchao Yu, Shibin Zhao, Chiheng Wang
>
>   If argv[0] is NULL when agentxtrap is started, it will cause a null pointer 
> reference vulnerability in strrchr() when the main function of agentxtrap 
> starts parsing the parameters.
>
> [image: image.png]
>
>
> poc:
>
>

Bug#976307: sudo: reproducible builds: different binaries when built on usrmerge system

[Vagrant Cascadian]

Control: notfixed 976307 1.9.9-1
Control: tags 976307 +patch

This was apparently re-introduced when switching to dh in commit:

308501390171e0afd1f2ce729cb3719388696b0f first half of dh conversion

And included in 1.9.8p2...

Updated patch attached.


live well,
  vagrant
From 41bb07920ecb10832935b1b0f8a42b5565f92326 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 6 Mar 2022 01:22:07 +
Subject: [PATCH] debian/rules: Pass MVPROG=/bin/mv to configure to ensure
 reproducible build.

When built on a system with usrmerge enabled, and a system without
usrmerge enabled, the visudo binary embeds different paths for the
"mv" program.

Passing the /bin location to configure ensures using the most
compatible path, as a usrmerge system should have compatibility
symlinks available for /bin, while a non-usrmerge system is unlikely
to have compatibility symlinks for the /usr/bin location.
---
 debian/rules | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian/rules b/debian/rules
index 88f0a53..b93a6ba 100755
--- a/debian/rules
+++ b/debian/rules
@@ -33,6 +33,10 @@ ifeq ($(DEB_HOST_ARCH_OS),linux)
 CONFIGURE_ARGS += --with-selinux --with-linux-audit --enable-tmpfiles.d=yes
 endif
 
+# Consistently use /bin/mv to ensure reproducible builds regardless of
+# building on a usrmerge or non-usrmerge system.
+CONFIGURE_ARGS += MVPROG=/bin/mv
+
 %:
 		dh $@
 
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#978015: Add "image/webp webp" to /etc/mime.types ?

[Charles Plessy]

Le Mon, Dec 28, 2020 at 08:16:24AM +0900, Charles Plessy a écrit :
> 
> I see on the upstream mailing list that it is being discussed.
> 
> https://groups.google.com/a/webmproject.org/g/webp-discuss/c/gklBC0vn7NI/m/_bmsFb05AwAJ
> 
> In my opinion, it is unfair to call IANA's registration "paperwork",
> "administrative work" or "time investment" (as in the thread linked
> above).
> 
> Registration is done through a simple web form, without the need to
> create an account.
> 
> https://www.iana.org/form/media-types

Hi Trent and VA,

would one of you be intereted to ping Google to register the media type
to the IANA ?

Have a nice day,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from work,   https://mastodon.technology/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy

Bug#1006822: chromium: Chromium doesn't start on sway after latest securty update

[Andres Salomon]

On Sat, 05 Mar 2022 21:34:29 +0100 Andreas Juch wrote:
> Package: chromium
> Version: 99.0.4844.51-1~deb11u1
> Severity: important
> X-Debbugs-Cc: t...@security.debian.org
>
> Dear Maintainer,
>
> After the latest security update of chromium from 98 to 99 chromium
> doesn't start any more. I'm using wayland with the sway window manager.
>
> The messages in the terminal are:
>
> [6788:6788:0305/212730.897589:ERROR:gpu_init.cc(440)] Passthrough is 
not supported, GL is egl, ANGLE is
> [6788:6788:0305/212730.900388:ERROR:sandbox_linux.cc(377)] 
InitializeSandbox() called with multiple threads in process gpu-process.
> [6742:6742:0305/212730.912434:ERROR:cursor_loader.cc(116)] Failed to 
load a platform cursor of type kNull
> [6742:6838:0305/212731.190121:ERROR:wayland_event_watcher.cc(301)] 
Fatal Wayland communication error Broken pipe.

>
> I already commented out all CHROMIUM_FLAGS and moved away
> .config/chromium, but it still doesn't start.
>
> With WAYLAND_DEBUG=1 there is more output, but I don't know if its

> relevant:


Please try running chromium the following ways, and let me know which 
does and doesn't work:



chromium --ozone-platform=wayland

chromium --ozone-platform=x11

chromium --no-sandbox


Also, I don't know how you cleared CHROMIUM_FLAGS, but if you didn't 
already: try moving /etc/chromium* out of the way and reinstalling the 
package to make sure that you don't have any random flags set.

Bug#1006831: newsboat: diff for NMU version 2.21-1.2 (nom transition)

[James McCoy]

Package: newsboat
Version: 2.21-1.1
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for newsboat (versioned as 2.21-1.2) to adapt it
for the transition of rust-nom 5 -> 7.  I'll upload it to DELAYED/7.
Please feel free to tell me if I should delay it longer.

Regards.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
diffstat for newsboat-2.21 newsboat-2.21

 changelog  |8 +++
 control|2 
 patches/nom-ContextError.patch |   93 +
 patches/relax-deps.diff|8 ++-
 patches/series |1 
 5 files changed, 108 insertions(+), 4 deletions(-)

diff -Nru newsboat-2.21/debian/changelog newsboat-2.21/debian/changelog
--- newsboat-2.21/debian/changelog	2022-01-23 09:28:08.0 -0500
+++ newsboat-2.21/debian/changelog	2022-03-05 19:26:54.0 -0500
@@ -1,3 +1,11 @@
+newsboat (2.21-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update to nom 7
+  * Backport patch from upstream to build properly with nom-7
+
+ -- James McCoy   Sat, 05 Mar 2022 19:26:54 -0500
+
 newsboat (2.21-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru newsboat-2.21/debian/control newsboat-2.21/debian/control
--- newsboat-2.21/debian/control	2022-01-23 09:28:08.0 -0500
+++ newsboat-2.21/debian/control	2022-03-05 16:46:48.0 -0500
@@ -23,7 +23,7 @@
librust-backtrace-0.3-dev,
librust-backtrace-sys-0.1-dev,
librust-unicode-width-0.1-dev,
-   librust-nom-5+lexical-core-dev,
+   librust-nom-7-dev,
librust-curl-sys-0.4+ssl-dev,
librust-libc-0.2-dev,
librust-gettext-rs-0.4-dev,
diff -Nru newsboat-2.21/debian/patches/nom-ContextError.patch newsboat-2.21/debian/patches/nom-ContextError.patch
--- newsboat-2.21/debian/patches/nom-ContextError.patch	1969-12-31 19:00:00.0 -0500
+++ newsboat-2.21/debian/patches/nom-ContextError.patch	2022-03-05 16:59:33.0 -0500
@@ -0,0 +1,93 @@
+From 5fb3d1fcabefa740547d1a5ebe2fd5b825624029 Mon Sep 17 00:00:00 2001
+From: David Brito <39559632+davbr...@users.noreply.github.com>
+Date: Sat, 7 Nov 2020 11:53:01 -0400
+Subject: [PATCH] Add ContextError trait
+
+---
+ rust/libnewsboat/src/filterparser.rs  | 24 +--
+ .../libnewsboat/src/fmtstrformatter/parser.rs |  2 +-
+ 2 files changed, 18 insertions(+), 8 deletions(-)
+
+diff --git a/rust/libnewsboat/src/filterparser.rs b/rust/libnewsboat/src/filterparser.rs
+index 2c0bffe38..a27128c30 100644
+--- a/rust/libnewsboat/src/filterparser.rs
 b/rust/libnewsboat/src/filterparser.rs
+@@ -7,7 +7,7 @@ use nom::{
+ bytes::complete::{escaped, is_not, tag, take, take_while, take_while1},
+ character::{is_alphanumeric, is_digit},
+ combinator::{complete, map, opt, peek, recognize, value},
+-error::{context, ParseError, VerboseError, VerboseErrorKind},
++error::{context, ContextError, ParseError, VerboseError, VerboseErrorKind},
+ sequence::{delimited, separated_pair, terminated, tuple},
+ IResult, Offset,
+ };
+@@ -96,7 +96,9 @@ fn expected_to_i18n_msg(expected_id: &'static str) -> &'static str {
+ .unwrap_or("")
+ }
+ 
+-fn operators<'a, E: ParseError<&'a str>>(input: &'a str) -> IResult<&'a str, Operator, E> {
++fn operators<'a, E: ParseError<&'a str> + ContextError<&'a str>>(
++input: &'a str,
++) -> IResult<&'a str, Operator, E> {
+ context(
+ EXPECTED_OPERATORS,
+ alt((
+@@ -154,8 +156,10 @@ fn space1<'a, E: ParseError<&'a str>>(input: &'a str) -> IResult<&'a str, &'a st
+ take_while1(|c| c == ' ')(input)
+ }
+ 
+-fn comparison<'a, E: ParseError<&'a str>>(input: &'a str) -> IResult<&'a str, Expression, E> {
+-let attribute_name = context(
++fn comparison<'a, E: ParseError<&'a str> + ContextError<&'a str>>(
++input: &'a str,
++) -> IResult<&'a str, Expression, E> {
++let mut attribute_name = context(
+ EXPECTED_ATTRIBUTE_NAME,
+ take_while1(|c| is_alphanumeric(c as u8) || c == '_' || c == '-' || c == '.'),
+ );
+@@ -180,7 +184,9 @@ fn comparison<'a, E: ParseError<&'a str>>(input: &'a str) -> IResult<&'a str, Ex
+ ))
+ }
+ 
+-fn parens<'a, E: ParseError<&'a str>>(input: &'a str) -> IResult<&'a str, Expression, E> {
++fn parens<'a, E: ParseError<&'a str> + ContextError<&'a str>>(
++input: &'a str,
++) -> IResult<&'a str, Expression, E> {
+ let (input, _) = tag("(")(input)?;
+ let (input, _) = space0(input)?;
+ let (input, result) = alt((expression, parens, comparison))(input)?;
+@@ -208,7 +214,9 @@ fn space_after_logop<'a, E: ParseError<&'a str>>(input: &'a str) -> IResult<&'a
+ peek(parser)(input)
+ }
+ 
+-fn expression<'a, E: ParseError<&'a str>>(input: &'a str) -> IResult<&'a str, Expression, E> {
++fn expression<'a, E: ParseError<&'a str> + ContextError<&'a str>>(
++ 

Bug#989604: [Pkg-openssl-devel] Bug#989604: libssl1.1: segfault on arm64 (M1) with some ciphers e.g. curl https://dl.yarnpkg.com

[Anders Kaseorg]

On 1/26/22 11:56, Sebastian Andrzej Siewior wrote:

On 2022-01-25 22:10:00 [-0500], Anders Kaseorg wrote:

The fix is trivial, swapping two lines of assembly.  I’ve attached it as a
debdiff, and tested it in a Debian 10 container on an M1 MacBook.  Can it
be considered for oldstable?


Yes. My plan is to get m into o-stable and oo-stable. The o-stable
update is tracked in #1003484.


Any progress on this fix, via either my targeted debdiff or a full 
update to ≥ 1.1.1i?


I see that https://bugs.debian.org/1003484 is for 1.1.1k → 1.1.1m in 
bullseye (stable); that’s not directly relevant here as neither version 
is affected.  There’s https://bugs.debian.org/959469 for 1.1.1d → 1.1.1k 
in buster (oldstable), which would resolve this, but it’s seen no 
activity in a year.  Perhaps the intention is to wait for 1.1.1m in 
stable before updating the oldstable backport to 1.1.1m as well?  I’m 
just concerned that if we keep blocking this on newer and newer openssl 
versions, it will be delayed for infinite time…


Anders

Bug#1006697: inkscape: Inkscape doesn't open GUI unless option -g is added

[Krzysztof Sobiecki]

On Sat, 05 Mar 2022 22:56:47 +0100 Krzysztof Sobiecki
 wrote:
> On Wed, 2 Mar 2022 19:20:14 +0100 Mattia Rizzolo 
> wrote:
> > Control: tag -1 moreinfo unreproducible
> > 
> > On Wed, Mar 02, 2022 at 06:21:20PM +0100, Krzysztof Sobiecki wrote:
> > > I have installed Inkscape. But when tried to run it, nothing
shows
> up.
> > > Including right-click on svg file and choosing Inkscape,
> > > using Inkscape icon in Gnome, running Inkscape from command line.
> > > Only thing that helped was adding -g in command line(or to
> .desktop).
> > > I have deleted Inkscape configuration(.config/.local) but it
didn't
> help.
> > 
> > Interesting.
> > 
> > I don't see that, so I'd like to ask you:
> > 
> > 1) if you just run `inkscape`, what's the output?
>  There is no output, it just exits with 0
> > 2) if you see an actual crash, please run that under gdb (with the
-
> dbgsym installed)
>  It exits with 0, so there is no crash
> > 3) can you also reproduce this with version 1.1.1-3 ?
>  I'm going to do it a bit later
> 
> What I have found is that when I start Inkscape it just quits.
> So I decided to trace places where _with_gui is set to false.
> In file inkscape-application.cpp line 1306(big GUI and Shell comment)
> there is a big if of command line options that turns off gui.
> So I checked what options are used that cause gui to be turned off:
> https://paste.debian.net/1233131/ (1 signals that option is present)
> As you can see there are a few of them.
> But I didn't set any command line options. It looks like they just
> appear out of nowhere. I even created dummy user and logged in as it.
> It produced same results. So I don't think it's problem with user
> configuration.
> 
Now list with actual values of options:
https://paste.debian.net/1233151/
Fact that they are all 0 is even stranger.

-- 
Krzysztof Sobiecki
sob...@gmail.com

Bug#1006707: python3.10 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip

[Anders Kaseorg]

tags 1006707 + patch
thanks

sysconfig-debian-schemes.patch uses an incorrect test for a virtual 
environment:

if 'real_prefix' in sys.__dict__ or 'VIRTUAL_ENV' in os.environ:

Both sys.real_prefix and VIRTUAL_ENV are only set by virtualenv, not venv, 
and then only when the virtualenv is activated by VENV_ROOT/bin/activate, 
not when VENV_ROOT/bin/python is launched directly by its path.

This patch corrects the test to

if sys.base_prefix != sys.prefix:

which works on Python ≥ 3.3.

Andersdiff -Nru python3.10-3.10.2/debian/changelog python3.10-3.10.2/debian/changelog
--- python3.10-3.10.2/debian/changelog  2022-02-26 08:21:15.0 +
+++ python3.10-3.10.2/debian/changelog  2022-03-05 23:50:26.0 +
@@ -1,3 +1,10 @@
+python3.10 (3.10.2-6) unstable; urgency=medium
+
+  * debian/patches/sysconfig-debian-schemes.patch: Correct the test for
+virtual environments.  (Closes: #1006707, LP: #1962791)
+
+ -- Anders Kaseorg   Sat, 05 Mar 2022 23:50:26 +
+
 python3.10 (3.10.2-5) unstable; urgency=medium
 
   * Fix the marshal test after applying the fix for #1004558.
diff -Nru python3.10-3.10.2/debian/patches/sysconfig-debian-schemes.diff 
python3.10-3.10.2/debian/patches/sysconfig-debian-schemes.diff
--- python3.10-3.10.2/debian/patches/sysconfig-debian-schemes.diff  
2022-02-14 16:46:56.0 +
+++ python3.10-3.10.2/debian/patches/sysconfig-debian-schemes.diff  
2022-03-05 23:50:26.0 +
@@ -45,7 +45,7 @@
  'user': 'osx_framework_user',
  }
 +
-+if 'real_prefix' in sys.__dict__ or 'VIRTUAL_ENV' in os.environ:
++if sys.base_prefix != sys.prefix:
 +# virtual environments
 +prefix_scheme = 'posix_prefix'
 +else:

Bug#1006795: Withdraw this bug report, I solved it

[David Calman]

So if you press Tab that hides the docks. I must have done that
accidentally.

Bug#1000229: binary package is missing /usr/sbin/memlockd

[Paul Wise]

Control: tags -1 + patch pending

On Fri, 19 Nov 2021 23:02:53 +0100 Sven Hartge wrote:

> The subject says it all: The package is missing the binary:

This is caused by the install target in debian/rules doing things
manually instead of leaving everything to dh_* scripts and
configuration files for them, which means that an arch-any build with
dpkg-buildpackage -B does not run the debian/rules install target.

I've attached a patch for a minimal NMU that fixes the issue and I have
uploaded that NMU to Debian with a 7 days delay. Please either
incorporate the patch into your next upload or reschedule the NMU to
occur as soon as possible. Note that after applying the patch you will
need to delete debian/memlockd-default, since the debdiff doesn't seem
to include removal of the file somehow.

I note this package needs a lot of polish. There are a lot of low
priority but trivial to fix lintian warnings. There are a lot of
unnecessary comments in the debian/ directory. The debian/docs file is
empty and can be deleted. The debian/dirs file can be deleted,
debhelper creates dirs as needed. The debian/copyright looks very out
of date. `wrap-and-sort -sabt` needs running. autopkgtests are needed.
debian/watch needs updating, memlockd 1.3 needs uploading upstream, the
upstream website needs links converting to https. The upstream project
should really get imported into git, from the Debian tarballs on
snapshot.debian.org if there isn't anything better.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
diff -u memlockd-1.3/debian/changelog memlockd-1.3/debian/changelog
--- memlockd-1.3/debian/changelog
+++ memlockd-1.3/debian/changelog
@@ -1,3 +1,10 @@
+memlockd (1.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix package when building only arch-any packages (Closes: #1000229)
+
+ -- Paul Wise   Sun, 06 Mar 2022 07:24:13 +0800
+
 memlockd (1.3-2) unstable; urgency=medium
 
   * Made it install correctly when systemctl isn't installed, closes: ##999587
only in patch2:
unchanged:
--- memlockd-1.3.orig/debian/memlockd.default
+++ memlockd-1.3/debian/memlockd.default
@@ -0,0 +1,10 @@
+# Defaults for memlockd initscript
+# sourced by /etc/init.d/memlockd
+# installed at /etc/default/memlockd
+
+#
+# This is a POSIX shell fragment
+#
+
+# Additional options that are passed to the Daemon.
+DAEMON_OPTS="-u memlockd"
only in patch2:
unchanged:
--- memlockd-1.3.orig/debian/memlockd.install
+++ memlockd-1.3/debian/memlockd.install
@@ -0,0 +1,2 @@
+memlockd usr/sbin
+memlockd.cfg etc
only in patch2:
unchanged:
--- memlockd-1.3.orig/debian/memlockd.manpages
+++ memlockd-1.3/debian/memlockd.manpages
@@ -0,0 +1 @@
+memlockd.8
only in patch2:
unchanged:
--- memlockd-1.3.orig/debian/rules
+++ memlockd-1.3/debian/rules
@@ -17,19 +17,8 @@
 %:
 	dh $@
 
-install: build
-	dh_installdirs
-	cp memlockd debian/memlockd/usr/sbin
-	cp memlockd.cfg debian/memlockd/etc
-	cp debian/memlockd-default debian/memlockd/etc/default/memlockd
-	dh_installsystemd --restart-after-upgrade memlockd.service
+override_dh_installchangelogs:
 	dh_installchangelogs -X changes.txt
-	dh_installdocs
-	dh_installinit
-	dh_installman memlockd.8
-	dh_installdeb
-	dh_strip
-	dh_compress
 
 # dh_make generated override targets
 # This is example for Cmake (See https://bugs.debian.org/641051 )


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

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Diederik de Haas]

Hi Petra,

On Saturday, 5 March 2022 21:12:12 CET Petra R.-P. wrote:
> On Sat 05 Mar 2022 at 18:23:52 +0100  Diederik de Haas
>  wrote:
> > On Monday, 21 February 2022 17:25:33 CET Petra Rübe-Pugliese wrote:
>  [...]
> 
> > So if you remove the 'quiet' word there and do an update-grub, then the
> > boot will be 'noisier' by default (on every boot).
> 
> This is what I have done, for the time being.
> 
> As a result, there was a lot of output on the screen.
> I am attaching a foto of the final state, where it stopped.

I didn't see an obvious clue as to why it didn't continue ...

> However, I cannot find any trace of this in /var/log/kern.log.
> Whereas "grep 5.15.0  /var/log/kern.log" gives loads of output,
> "grep 5.16.0  /var/log/kern.log" does not produce anything at
> all. 

How about in /var/log/kern.log.1 (f.e.) ? Because on my system the very first 
message of a boot in that file begins with:
[0.00] Linux version 5.16.0-3-amd64 ...

> Also manual inspection of the file does not show any relevant passage.

So far, *I* haven't found a direct clue as to why things fail, so if you do 
have _a_ log of a boot with the 5.16 kernel, then having that could help.
Especially if you could provide a similar log of a boot with the 5.15 kernel. 
Doesn't need to be the whole log, but knowing a couple of lines which happen 
thereafter on 5.15 but not on 5.16 could provide a clue.

I saw that the 5.16.11-1 kernel transitioned to testing and it is useful to 
know if the issue is still present with that version.
In the upstream kernel in drivers/gpu/drm/amd I saw a number of commits since 
version 5.16.7 (and also several other commits which are part of 5.16.12 which 
is present in salsa, but not yet released).

When I look at the photo from https://bugs.debian.org/1006149#44 (from Axel), 
I do notice an important difference:
He has various [drm] messages, whereas I see none of those with you.
Do you have [drm] messages when booting with the 5.15 kernel?

That bug message also has the following which is different from yours:
ii  firmware-amd-graphics 20210818-1
...
ii  firmware-linux-nonfree20210818-1
ii  firmware-misc-nonfree 20210818-1

So it would be interesting to know whether installing any of those packages 
makes a difference. I'd suggest first installing the firmware-amd-graphics 
package.

HTH,
  Diederik

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

Bug#1006830: elpa-mailscripts: notmuch-slurp-debbugs misses messages

[Vagrant Cascadian]

Package: elpa-mailscripts
Version: 0.24-1
Severity: normal
X-Debbugs-Cc: Vagrant Cascadian 

I've noticed recently some messages do not get downloaded when I run
from emacs:

  M-x notmuch-slurp-debbugs

I've noticed this in the recent past on other bugs, but didn't get a
chance to file a bug. This time I noticed it with:

  https://bugs.debian.org/1004939

Where it simply doesn't download message #10 with message id
ltfe7r.ccn2zwkm4w...@pappacoda.it

I manually downloaded the mbox for that specific message, and used
mbox2maildir to move it into one of my folders and the message appeared
just fine...



live well,
  vagrant

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.16.0-3-arm64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_CRAP
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 elpa-mailscripts depends on:
ii  dh-elpa-helper  2.0.10
ii  elpa-notmuch0.35-1
ii  emacsen-common  3.0.4
ii  mailscripts 0.24-1

Versions of packages elpa-mailscripts recommends:
ii  emacs  1:27.1+1-3.1
ii  emacs-nox [emacs]  1:27.1+1-3.1+b1

elpa-mailscripts suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1004939: debhelper: Drop -DCMAKE_SKIP_RPATH=on in compat v14

[Vagrant Cascadian]

On 2022-02-16, Andrea Pappacoda wrote:
> Hi, I think that CMAKE_SKIP_RPATH a bit extreme too. Also, setting both 
> options doesn't make much sense, as CMAKE_SKIP_RPATH completely avoids 
> setting the rpath, so CMAKE_BUILD_RPATH_USE_ORIGIN does nothing :/

Well, it makes it "easy" to fallback to CMAKE_BUILD_RPATH_USE_ORIGIN,
but I think in this case that CMAKE_BUILD_RPATH_USE_ORIGIN should be the
default...


> If you really want to avoid having an rpath in the installed package 
> you could set the CMAKE_SKIP_INSTALL_RPATH option, that strips the 
> rpath on install (it may be enabled by default, I'm not sure) but keeps 
> it in the build tree so that you can run tests without having to mess 
> with env vars.

Using CMAKE_SKIP_INSTALL_RPATH still results in a different BuildId
embedded in the binary when built under a different build path. Even
though the build path is eventually removed, the BuildId is calculated
before it is removed...


> But if what you are trying to solve is a reproducibility issue then
> CMAKE_BUILD_RPATH_USE_ORIGIN should be enough, and shouldn't even
> break existing workflows.

That's been my experience so far, I've confirmed this with buidl testing
for many of the ~160 packages documented at:

  
https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1006829: freeipa-client missing dependency on libnss-myhostname

[Gabriel Smolnycki]

Package: freeipa-client
Version: 4.9.8-1~bpo11+1
Severity: important
X-Debbugs-Cc: gabr...@ifrtech.net

Dear Maintainer,

freeipa-client depends on the libnss-myhostname package to properly
enroll a host. On a minimal install of Debian Bullseye, with
the bullseye-backports repository enabled, this is not a dependency.
This causes an error in ipa-client-install, as shown below.

Steps to reproduce:

* Install Debian Bullseye from ISO. Selected options were BIOS boot,
guided partitioning (all in one root), and "standard system
utilites" selected for software.
* Login as root. Run the following:
- apt update
- apt install software-properties-common
- add-apt-repository "deb http://deb.debian.org/debian
  bullseye-backports main contrib non-free"
- apt update
- apt install realmd
- hostnamectl set-hostname debian.ipa.example.com
- realm join -U jdoe ipa.example.com

Expected result:

Debian machine will be joined to realm.

Actual result:

Realm operation fails. journalctl shows [identifying information
redacted]:

```
Mar 05 17:40:41 debian.ipa.example.com realmd[1851]:  * Resolving:
_ldap._tcp.ipa.example.com
Mar 05 17:40:41 debian.ipa.example.com realmd[1851]:  * Performing LDAP
DSE lookup on: 1.2.3.4
Mar 05 17:40:41 debian.ipa.example.com realmd[1851]:  * Successfully
discovered: ipa.example.com
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:  * Unconditionally
checking packages
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:  * Resolving
required packages
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:  * LANG=C
/usr/sbin/ipa-client-install --domain ipa.example.com --realm
IPA.EXAMPLE.COM --mkhomedir --enable-dns-updates --unattended
--force-join --principal jdoe -W --force-ntpd
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: Traceback (most
recent call last):
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/sbin/ipa-client-install", line 22, in 
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from
ipaclient.install import ipa_client_install
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipaclient/install/ipa_client_install.py",
line 7, in 
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from
ipaclient.install import client
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipaclient/install/client.py", line 37,
in 
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from ipalib
import api, errors, x509
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipalib/__init__.py", line 919, in

Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from ipalib
import plugable
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipalib/plugable.py", line 42, in

Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from ipalib
import errors
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipalib/errors.py", line 109, in 
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from
ipalib.text import ngettext as ungettext
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipalib/text.py", line 139, in 
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from
ipalib.request import context
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipalib/request.py", line 28, in 
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from
ipalib.base import ReadOnly, lock
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipalib/base.py", line 26, in 
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: from
ipalib.constants import NAME_REGEX, NAME_ERROR
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipalib/constants.py", line 34, in

Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: FQDN =
gethostfqdn()
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3/dist-packages/ipapython/fqdn.py", line 21, in
gethostfqdn
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: gai =
socket.getaddrinfo(
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:   File
"/usr/lib/python3.9/socket.py", line 953, in getaddrinfo
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: for res in
_socket.getaddrinfo(host, port, family, type, proto, flags):
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]: socket.gaierror:
[Errno -2] Name or service not known
Mar 05 17:40:44 debian.ipa.example.com realmd[1851]:  ! Running
ipa-client-install failed
```

Resolution:

* Install libnss-myhostname
- apt install libnss-myhostname
* Retry joining realm
- realm join -U jdoe ipa.example.com
* Realm join succeeds.


-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), 

Bug#1006828: cname from same domain fails to resolve if target is an dhcp host

[Frank Liu]

Package: dnsmasq
Version: 2.85-1

Here is the relevant dnsmasq config on Debian 11.2:

domain=test.example.com
cname=alias.test.example.com,client1.test.example.com
cname=alias.dummy.example.com,client1.test.example.com

"client1" is a dhcp client, and the dnsmasq server IP is 192.168.0.253

The problem is we can't resolve the name "alias.test.example.com",
though we can resolve the name "alias.dummy.example.com" which is out
of the domain "test.example.com".

$ dig -v
DiG 9.16.22-Debian

$ dig @192.168.0.253 alias.dummy.example.com alias.test.example.com
client1.test.example.com

; <<>> DiG 9.16.22-Debian <<>> @192.168.0.253 alias.dummy.example.com
alias.test.example.com client1.test.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29718
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;alias.dummy.example.com. IN A

;; ANSWER SECTION:
alias.dummy.example.com. 0 IN CNAME client1.test.example.com.
client1.test.example.com. 0 IN A 192.168.0.70

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 114

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62870
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;alias.test.example.com. IN A

;; ANSWER SECTION:
alias.test.example.com. 5 IN CNAME client1.test.example.com.

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 96

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40301
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;client1.test.example.com. IN A

;; ANSWER SECTION:
client1.test.example.com. 5 IN A 192.168.0.70

;; Query time: 16 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:27 UTC 2022
;; MSG SIZE  rcvd: 75

$ dig -t any @192.168.0.253 alias.dummy.example.com
alias.test.example.com client1.test.example.com

; <<>> DiG 9.16.22-Debian <<>> -t any @192.168.0.253
alias.dummy.example.com alias.test.example.com
client1.test.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24227
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;alias.dummy.example.com. IN ANY

;; ANSWER SECTION:
alias.dummy.example.com. 0 IN CNAME client1.test.example.com.
client1.test.example.com. 0 IN A 192.168.0.70

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:41 UTC 2022
;; MSG SIZE  rcvd: 114

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12433
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;alias.test.example.com. IN ANY

;; ANSWER SECTION:
alias.test.example.com. 5 IN CNAME client1.test.example.com.

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:41 UTC 2022
;; MSG SIZE  rcvd: 96

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31132
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;client1.test.example.com. IN ANY

;; Query time: 20 msec
;; SERVER: 192.168.0.253#53(192.168.0.253)
;; WHEN: Wed Mar 02 17:34:41 UTC 2022
;; MSG SIZE  rcvd: 59

Bug#940329:

[Andreas Noteng]

Hi, i was having trouble finding a sponsor as the sponsor i had was having
health issues (I'm only dm, not dd). This software seems to have died
upstream, but a fork is in progress so switching upstream sources might be
in order. I'll have a look at it next week.

Andreas

lør. 5. mar. 2022, 18:21 skrev Gregor Riepl :

> Any progress?
>
> This MR addresses the build errors and should make the package fit for
> inclusion on Debian:
>
> https://salsa.debian.org/debian/scantailor-advanced/-/merge_requests/12
>

Bug#1006704: nmu: memlockd_1.3-2: rebuild to fix missing binary issue (Closes: #1000229)

[Paul Wise]

Control: close -1

On Sat, 2022-03-05 at 18:13 +0100, Sebastian Ramacher wrote:

> How did that happen? I'd prefer that memlockd is fixed so that this
> cannot happen again.

Looks like it builds correctly with debuild -b but not -B due to the
install target in debian/rules not getting used for arch-only builds,
so this binNMU will not actually fix the issue.

The install target can easily be replaced by dh_* so I'll report that
to bug #1000229 and submit an NMU to fix the issue. 

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1006827: wine32 and win64 broken if wine is not installed.

[Peter Michael Green]

Source: wine
Version: 6.0.2~repack-3

Between the version of wine in testing and the version in unstable the 
file l_intl.nls
was moved from the "libwine" package to the wine package. This is 
causing failures
in tests that install the "wine32" and/or "wine64" packages but do not 
install the

wine package.


err:environ:read_nls_file failed to load 10/0
wine: created the configuration directory '/home/debci/.wine'
wineserver: failed to load l_intl.nls
wine client error:0: recvmsg: Connection reset by peer

https://ci.debian.net/data/autopkgtest/testing/i386/g/gnupg2/19758116/log.gz

https://ci.debian.net/data/autopkgtest/testing/amd64/liba/libassuan/19760082/log.gz

https://ci.debian.net/data/autopkgtest/testing/i386/liba/libassuan/19758117/log.gz

https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgpg-error/19757268/log.gz

https://ci.debian.net/data/autopkgtest/testing/i386/libg/libgpg-error/19758118/log.gz

Bug#1005218: spip 3.2.4-1+deb10u6 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005218 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: spip
Version: 3.2.4-1+deb10u6

Explanation: fix cross-site scripting issue

Bug#1006525: mailman 2.1.29-1+deb10u5 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1006525 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: mailman
Version: 2.1.29-1+deb10u5

Explanation: fix regressions in fixes for CVE-2021-42097 and CVE-2021-44227

Bug#1004267: libpcap 1.8.1-6+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004267 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libpcap
Version: 1.8.1-6+deb10u1

Explanation: check PHB header length before using it to allocate memory 
[CVE-2019-15165]

Bug#1004268: libextractor 1.8-2+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004268 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libextractor
Version: 1.8-2+deb10u1

Explanation: fix invalid read issue [CVE-2019-15531]

Bug#1004265: rsyslog 8.1901.0-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004265 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: rsyslog
Version: 8.1901.0-1+deb10u1

Explanation: fix heap overflow issues [CVE-2019-17041 CVE-2019-17042]

Bug#1004261: opensc 0.19.0-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004261 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: opensc
Version: 0.19.0-1+deb10u1

Explanation: fix out-of-bounds access issues [CVE-2019-15945 CVE-2019-15946], 
crash due to read of unknown memory [CVE-2019-19479], double free issue 
[CVE-2019-20792], buffer overflow issues [CVE-2020-26570 CVE-2020-26571 
CVE-2020-26572]

Bug#1004055: raptor2 2.0.14-1.1~deb10u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004055 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: raptor2
Version: 2.0.14-1.1~deb10u2

Explanation: fix out of bounds array access issue [CVE-2020-25713]

Bug#1004249: weechat 2.3-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004249 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: weechat
Version: 2.3-1+deb10u1

Explanation: fix several denial of service issues [CVE-2020-8955 CVE-2020-9759 
CVE-2020-9760 CVE-2021-40516]

Bug#1004049: zziplib 0.13.62-3.2+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004049 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: zziplib
Version: 0.13.62-3.2+deb10u1

Explanation: fix denial of service issue [CVE-2020-18442]

Bug#1003842: flac 1.3.2-3+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003842 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: flac
Version: 1.3.2-3+deb10u1

Explanation: fix out of bounds read issue [CVE-2020-0499]

Bug#1003841: cimg 2.4.5+dfsg-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003841 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: cimg
Version: 2.4.5+dfsg-1+deb10u1

Explanation: fix heap buffer overflow issues [CVE-2020-25693]

Bug#1003827: wireshark 2.6.20-0+deb10u3 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003827 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: wireshark
Version: 2.6.20-0+deb10u3

Explanation: fix several security issues in dissectors [CVE-2021-22207 
CVE-2021-22235 CVE-2021-39921 CVE-2021-39922 CVE-2021-39923 CVE-2021-39924 
CVE-2021-39928 CVE-2021-39929]

Bug#1003826: libjackson-json-java 1.9.13-2~deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003826 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libjackson-json-java
Version: 1.9.13-2~deb10u1

Explanation: fix code execution issues [CVE-2017-15095 CVE-2017-7525], XML 
external entity issues [CVE-2019-10172]

Bug#1003795: evolution-data-server 3.30.5-1+deb10u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003795 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: evolution-data-server
Version: 3.30.5-1+deb10u2

Explanation: fix crash on malformed server reponse [CVE-2020-16117]

Bug#1003825: libetpan 1.9.3-2+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003825 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libetpan
Version: 1.9.3-2+deb10u1

Explanation: fix STARTTLS response injection issue [CVE-2020-15953]

Bug#1001454: privoxy 3.0.28-2+deb10u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1001454 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: privoxy
Version: 3.0.28-2+deb10u2

Explanation: fix memory leak [CVE-2021-44540] and cross-site scripting issue 
[CVE-2021-44543]

Bug#1006825: RFS: streamlink/3.2.0-1 -- CLI for extracting video streams from various websites to a video player

[Alexis Murzeau]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "streamlink" for a new
upstream version 3.2.0.

 * Package name: streamlink
   Version : 3.2.0-1
   Upstream Author : Streamlink Team
 * URL : https://streamlink.github.io/
 * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
   Section : python

It builds those binary packages:

  python3-streamlink - Python module for extracting video streams from
various websites
  python3-streamlink-doc - CLI for extracting video streams from various
websites (documentation)
  streamlink - CLI for extracting video streams from various websites to
a video player

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/streamlink


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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_3.2.0-1.dsc

Changes since the last upload to unstable:
streamlink (3.2.0-1) unstable; urgency=medium

  * d/README.source: update with basic instructions
  * d/README.source: fix gbp tag and add push to remote
  * d/rules: add LANG var to have reproducible builds (See #998059)
  * New upstream version 3.2.0
  * d/patches: update patches
  * lintian-overrides: adjust filter for changelogs

 -- Alexis Murzeau   Sat, 05 Mar 2022 22:55:24 +0100


There is a lintian info tag: built-using-field-on-arch-all-package
I have chosen to leave everything as-is until this related bug is sorted out:
#999785 - built-using-field-on-arch-all-package emitted for non-Go packages
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999785

Regards,
-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F

















signature.asc
Description: OpenPGP digital signature

Bug#1006537: dask: autopkgtest failure on 32 bit, mismatch in size of data structure.

[Diane Trout]

Hi,

I had some time to work on this and worked around the test case that
was failing, since it was failing because it was assuming it was
running in a 64-bit environment.

I submitted my comments to upstream here
https://github.com/dask/dask/issues/8169#issuecomment-1059839906

I tested in a 32-bit chroot, and it seems like this should work.

Though dask's autopkgtests will still fail because of python3-unicode2
is still in NEW.

Diane



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

Bug#1006807: chromium: No access yahoo and gmail

[Leandro Cunha]

Hi,

On Sat, Mar 5, 2022 at 2:21 PM Andres Salomon  wrote:
>
> On Sat, 05 Mar 2022 10:06:44 -0500 bw wrote:
> > Package: chromium
> > Version: 99.0.4844.51-1~deb11u1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I appreciate you trying to keep up with all the changes.
> >
> > Since the last ver, unable to login to gmail or yahoo mail. Tried clearing 
> > cookies
> > and poked around a little, but not able to spend much time on an app that 
> > changes
> > every week.
>
>
> Please try running chromium from a terminal, and let me know if there are any 
> error messages that occur when you try to log into gmail and yahoo.

I've been using chromium in unstable since Andres has uploaded it and
it's ok with that.
Strange...

-- 
Cheers,
Leandro Cunha
Software Engineer and Debian Contributor

Bug#1006697: inkscape: Inkscape doesn't open GUI unless option -g is added

[Krzysztof Sobiecki]

On Wed, 2 Mar 2022 19:20:14 +0100 Mattia Rizzolo 
wrote:
> Control: tag -1 moreinfo unreproducible
> 
> On Wed, Mar 02, 2022 at 06:21:20PM +0100, Krzysztof Sobiecki wrote:
> > I have installed Inkscape. But when tried to run it, nothing shows
up.
> > Including right-click on svg file and choosing Inkscape,
> > using Inkscape icon in Gnome, running Inkscape from command line.
> > Only thing that helped was adding -g in command line(or to
.desktop).
> > I have deleted Inkscape configuration(.config/.local) but it didn't
help.
> 
> Interesting.
> 
> I don't see that, so I'd like to ask you:
> 
> 1) if you just run `inkscape`, what's the output?
 There is no output, it just exits with 0
> 2) if you see an actual crash, please run that under gdb (with the -
dbgsym installed)
 It exits with 0, so there is no crash
> 3) can you also reproduce this with version 1.1.1-3 ?
 I'm going to do it a bit later

What I have found is that when I start Inkscape it just quits.
So I decided to trace places where _with_gui is set to false.
In file inkscape-application.cpp line 1306(big GUI and Shell comment)
there is a big if of command line options that turns off gui.
So I checked what options are used that cause gui to be turned off:
https://paste.debian.net/1233131/ (1 signals that option is present)
As you can see there are a few of them.
But I didn't set any command line options. It looks like they just
appear out of nowhere. I even created dummy user and logged in as it.
It produced same results. So I don't think it's problem with user
configuration.

-- 
Krzysztof Sobiecki
sob...@gmail.com

Bug#1006824: RM: vim-toml -- ROM; Provided natively in (neo)vim

[James McCoy]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: ma...@marvil07.net


This was originally packaged to provide support for toml files in
(neo)vim, but those files then started getting distributed with
(neo)vim.  As such, the package is no longer needed.

Bug#1006823: patch to prevent debos example adduser waits for password

[Geert Stappers]

Control: tag -1 patch


The hang is caused by `adduser` waiting for password (and password
confirmation)

Providing two password strings can be done with a bash subshell.
Creating the subshell is done by wrapping in parentheses.

So the 

adduser --gecos User user

should be

(echo user ; echo user ) | adduser --gecos User user



The complete patch:

--- a/doc/examples/setup-user.sh
+++ b/doc/examples/setup-user.sh
@@ -1,10 +1,8 @@
-#!/bin/sh
+#!/bin/bash
 
 set -e
 
 echo "I: create user"
-adduser --gecos User user
+(echo user ; echo user ) | adduser --gecos User user
 
-echo "I: set user password"
-echo "user:user" | chpasswd
 adduser user sudo




Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1006823: debos example has adduser waiting for password

[Geert Stappers]

Package: debos
Version: 1.0.0+git20210707.c66a48d-2
Severity: minor

Hello debos maintainers,


Doing

  debos /usr/share/doc/debos/examples/example.yaml

got me a waiting / hanging  debos.

But the provide example should just work ...

(a patch is work in progress)


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1006822: chromium: Chromium doesn't start on sway after latest securty update

[Andreas Juch]

Package: chromium
Version: 99.0.4844.51-1~deb11u1
Severity: important
X-Debbugs-Cc: t...@security.debian.org

Dear Maintainer,

After the latest security update of chromium from 98 to 99 chromium
doesn't start any more. I'm using wayland with the sway window manager.

The messages in the terminal are:

[6788:6788:0305/212730.897589:ERROR:gpu_init.cc(440)] Passthrough is not 
supported, GL is egl, ANGLE is
[6788:6788:0305/212730.900388:ERROR:sandbox_linux.cc(377)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[6742:6742:0305/212730.912434:ERROR:cursor_loader.cc(116)] Failed to load a 
platform cursor of type kNull
[6742:6838:0305/212731.190121:ERROR:wayland_event_watcher.cc(301)] Fatal 
Wayland communication error Broken pipe.

I already commented out all CHROMIUM_FLAGS and moved away
.config/chromium, but it still doesn't start.

With WAYLAND_DEBUG=1 there is more output, but I don't know if its
relevant:

[1000778.947]  -> wl_display@1.get_registry(new id wl_registry@2)
[1000778.967]  -> wl_disp...@1.sync(new id wl_callback@3)
[1000779.037] wl_display@1.delete_id(3)
[1000779.052] wl_registry@2.global(1, "wl_shm", 1)
[1000779.065]  -> wl_regis...@2.bind(1, "wl_shm", 1, new id [unknown]@4)
[1000779.085] wl_registry@2.global(2, "wl_drm", 2)
[1000779.091]  -> wl_regis...@2.bind(2, "wl_drm", 2, new id [unknown]@5)
[1000779.100]  -> wl_disp...@1.sync(new id wl_callback@6)
[1000779.103] wl_registry@2.global(3, "zwp_linux_dmabuf_v1", 3)
[1000779.108]  -> wl_regis...@2.bind(3, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@7)
[1000779.117]  -> wl_disp...@1.sync(new id wl_callback@8)
[1000779.121] wl_registry@2.global(4, "wl_compositor", 4)
[1000779.127]  -> wl_regis...@2.bind(4, "wl_compositor", 4, new id [unknown]@9)
[1000779.133] wl_registry@2.global(5, "wl_subcompositor", 1)
[1000779.138]  -> wl_regis...@2.bind(5, "wl_subcompositor", 1, new id 
[unknown]@10)
[1000779.144] wl_registry@2.global(6, "wl_data_device_manager", 3)
[1000779.149]  -> wl_regis...@2.bind(6, "wl_data_device_manager", 3, new id 
[unknown]@11)
[1000779.156] wl_registry@2.global(7, "zwlr_gamma_control_manager_v1", 1)
[1000779.162] wl_registry@2.global(8, "gtk_primary_selection_device_manager", 1)
[1000779.167]  -> wl_regis...@2.bind(8, "gtk_primary_selection_device_manager", 
1, new id [unknown]@12)
[1000779.174] wl_registry@2.global(9, "zxdg_output_manager_v1", 3)
[1000779.179]  -> wl_regis...@2.bind(9, "zxdg_output_manager_v1", 3, new id 
[unknown]@13)
[1000779.187] wl_registry@2.global(10, "org_kde_kwin_idle", 1)
[1000779.191]  -> wl_regis...@2.bind(10, "org_kde_kwin_idle", 1, new id 
[unknown]@14)
[1000779.200] wl_registry@2.global(11, "zwp_idle_inhibit_manager_v1", 1)
[1000779.205]  -> wl_regis...@2.bind(11, "zwp_idle_inhibit_manager_v1", 1, new 
id [unknown]@15)
[1000779.210] wl_registry@2.global(12, "zwlr_layer_shell_v1", 2)
[1000779.229] wl_registry@2.global(13, "xdg_wm_base", 2)
[1000779.233]  -> wl_regis...@2.bind(13, "xdg_wm_base", 2, new id [unknown]@16)
[1000779.238] wl_registry@2.global(14, "zwp_tablet_manager_v2", 1)
[1000779.242] wl_registry@2.global(15, 
"org_kde_kwin_server_decoration_manager", 1)
[1000779.246] wl_registry@2.global(16, "zxdg_decoration_manager_v1", 1)
[1000779.251]  -> wl_regis...@2.bind(16, "zxdg_decoration_manager_v1", 1, new 
id [unknown]@17)
[1000779.257] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
[1000779.261]  -> wl_regis...@2.bind(17, "zwp_relative_pointer_manager_v1", 1, 
new id [unknown]@18)
[1000779.266] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
[1000779.270]  -> wl_regis...@2.bind(18, "zwp_pointer_constraints_v1", 1, new 
id [unknown]@19)
[1000779.275] wl_registry@2.global(19, "wp_presentation", 1)
[1000779.281]  -> wl_regis...@2.bind(19, "wp_presentation", 1, new id 
[unknown]@20)
[1000779.288] wl_registry@2.global(20, "zwlr_output_manager_v1", 1)
[1000779.293] wl_registry@2.global(21, "zwlr_output_power_manager_v1", 1)
[1000779.297] wl_registry@2.global(22, "zwp_input_method_manager_v2", 1)
[1000779.302] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
[1000779.307] wl_registry@2.global(24, "zwlr_foreign_toplevel_manager_v1", 2)
[1000779.313] wl_registry@2.global(25, "zwlr_export_dmabuf_manager_v1", 1)
[1000779.317] wl_registry@2.global(26, "zwlr_screencopy_manager_v1", 3)
[1000779.321] wl_registry@2.global(27, "zwlr_data_control_manager_v1", 2)
[1000779.325] wl_registry@2.global(28, 
"zwp_primary_selection_device_manager_v1", 1)
[1000779.330]  -> wl_regis...@2.bind(28, 
"zwp_primary_selection_device_manager_v1", 1, new id [unknown]@21)
[1000779.336] wl_registry@2.global(29, "wp_viewporter", 1)
[1000779.341]  -> wl_regis...@2.bind(29, "wp_viewporter", 1, new id 
[unknown]@22)
[1000779.348] wl_registry@2.global(30, "zwp_virtual_keyboard_manager_v1", 1)
[1000779.352] wl_registry@2.global(31, "zwlr_virtual_pointer_manager_v1", 2)
[1000779.356] wl_registry@2.global(32, "zwlr_input_inhibit_manager_v1", 1)
[1000779.360] 

Bug#1006821: adequate reports broken symlink for tor

[shirish शिरीष]

Package: tor
Version: 0.4.6.10-1
Severity: normal

User : debian...@lists.debian.org
Usertags : broken-symlink adequate

Dear Maintainer,
While upgrading was hit by broken symlinks of tor. On further
investigation, got this info. Please see and fix the same.

$ adequate tor
tor: broken-symlink /etc/sv/tor/log/supervise -> /run/runit/supervise/tor.log
tor: broken-symlink /etc/sv/tor/supervise -> /run/runit/supervise/tor


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-debug'), (100,
'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50,
'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-3-amd64 (SMP w/4 CPU threads; 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 tor depends on:
ii  adduser 3.118
ii  libc6   2.33-7
ii  libcap2 1:2.44-1
ii  libevent-2.1-7  2.1.12-stable-1
ii  liblzma55.2.5-2
ii  libseccomp2 2.5.3-2
ii  libssl1.1   1.1.1m-1
ii  libsystemd0 250.3-2
ii  libzstd11.4.8+dfsg-3
ii  lsb-base11.1.0
ii  runit-helper2.10.3
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages tor recommends:
ii  logrotate3.19.0-2
ii  tor-geoipdb  0.4.6.10-1
ii  torsocks 2.3.0-3

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
pn  nyx  
ii  obfs4proxy   0.0.13-1
ii  socat1.7.4.1-3
ii  torbrowser-launcher  0.3.5-2

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
https://creativecommons.org/licenses/by-nc/3.0/
https://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#1006820: src:cryfs: fails to migrate to testing for too long: FTBFS on armel and armhf

[Paul Gevers]

Source: cryfs
Version: 0.10.2-5
Severity: serious
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:cryfs has been trying to migrate for 62 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source on armel and armhf, and built successfully on those architectures 
in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have tagged this bug to only affect sid and bookworm, so it doesn't 
affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=cryfs



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)

[Paul Gevers]

Hi Lev,

On 04-03-2022 11:42, dogs...@riseup.net wrote:

Do you confirm that this ABI change doesn't effect the other reverse
build dependencies of src:swi-prolog? If that's the case I'm fine with
removing the block. But I'm afraid (without checking from my side)
that the other package don't have the right virtual ABI package in
their dependencies. If they do, wouldn't they need a rebuild too?


New upstream version of eye was uploaded the same day as new version
of swi-prolog (in fact, after swi-prolog), and its autopkgtests pass
with swi-prolog in unstable (on amd64, and these are "not a regression"
on other architectures; they never were successful since at least Nov
2019, as I can see).

And eye already does this:

Package: eye
Depends:
  swi-prolog-nox,
  swi-prolog-abi-${prolog:ABI},
  ${misc:Depends}


I already mentioned `eye` explicitly in my earlier messages, I wasn't 
worried about it. Please comment on the other reverse build dependencies 
(apart from eye and logol).



Also, if logol is already doing the right thing, shouldn't you as the
uploader of swi-prolog request a binNMU for logol to enable your
package to migrate at all? I mean, I would expect the migration to
become blocked by uninstallability of logol in testing without a
rebuild.


Hmmm... I'm not quite sure what would be the better option for logol
and swi-prolog. If logol depends on swi-prolog-abi-binary-68, then
change of ABI will require changing dependencies by hand. If logol
depends on swi-prolog-abi-binary-$(prolog:ABI) as eye does (prolog:ABI
should be handled in d/rules) and _not_ build-depend on it (but
just build-depend on swi-prolog without version), then binNMU is
possible. I think the latter is the easier way. What do you think,
guys?


As eye does seems like the way to go to me.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1000618: ruby-gtk2: crashes with openssl: superclass mismatch for class Socket (TypeError)

[Peter Michael Green]

I noticed this bug while working on a derivative and decided to take a look.
Note though that I am NOT a ruby guy.

Upstream hasn't fixed the underlying issue, but has suggested it can be 
worked around by reordering

requires/imports and has closed the bug.

I took upstreams suggestion and turned it into a patch that could be 
applied to origami-pdf, unfortunately

when I tried to build origami-pdf it failed with.

ArgumentError: wrong number of arguments (given 1, expected 0; required 
keyword: year)

    /origami-pdf-2.0.0/lib/origami/string.rb:383:in `initialize'
    /origami-pdf-2.0.0/lib/origami/string.rb:453:in `new'
    /origami-pdf-2.0.0/lib/origami/string.rb:453:in `now'
    /origami-pdf-2.0.0/lib/origami/signature.rb:517:in `pre_build'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:798:in `block in physicalize'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:808:in `block (2 levels) in 
physicalize'

    /origami-pdf-2.0.0/lib/origami/dictionary.rb:137:in `block in map!'
    /origami-pdf-2.0.0/lib/origami/dictionary.rb:136:in `each_pair'
    /origami-pdf-2.0.0/lib/origami/dictionary.rb:136:in `map!'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:802:in `block in physicalize'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:808:in `block (2 levels) in 
physicalize'

    /origami-pdf-2.0.0/lib/origami/pdf.rb:802:in `map!'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:802:in `block in physicalize'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:817:in `block (2 levels) in 
physicalize'

    /origami-pdf-2.0.0/lib/origami/pdf.rb:816:in `each_value'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:816:in `block in physicalize'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:808:in `block (2 levels) in 
physicalize'

    /origami-pdf-2.0.0/lib/origami/dictionary.rb:137:in `block in map!'
    /origami-pdf-2.0.0/lib/origami/dictionary.rb:136:in `each_pair'
    /origami-pdf-2.0.0/lib/origami/dictionary.rb:136:in `map!'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:802:in `block in physicalize'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:828:in `block in physicalize'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:827:in `each'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:827:in `physicalize'
    /origami-pdf-2.0.0/lib/origami/pdf.rb:722:in `compile'
    /origami-pdf-2.0.0/lib/origami/signature.rb:200:in `sign'
    /origami-pdf-2.0.0/test/test_pdf_sign.rb:43:in `test_sign'

I beleive this is related to changes in ruby 3.0, 
https://rubyreferences.github.io/rubychanges/3.0.html#keyword-arguments-are-now-fully-separated-from-positional-arguments 
I fixed the

code according to the information on that page and did another build.

After installing that, I tested that pdfwalker now crashes with an 
apparently unrelated error,

so the workaround appears to be effective.

/usr/share/origami/gui/treeview.rb:54:in `': 
'Pango::WEIGHT_NORMAL' has been deprecated. Use 
'Pango::Weight::NORMAL' or ':normal'.
/usr/share/origami/gui/treeview.rb:54:in `': 
'Pango::STYLE_NORMAL' has been deprecated. Use 'Pango::Style::NORMAL' 
or ':normal'.
/usr/share/origami/gui/treeview.rb:376:in `reset_appearance': 
'Pango::WEIGHT_BOLD' has been deprecated. Use 'Pango::Weight::BOLD' or 
':bold'.
/usr/share/origami/gui/treeview.rb:385:in `reset_appearance': 
'Pango::STYLE_ITALIC' has been deprecated. Use 'Pango::Style::ITALIC' 
or ':italic'.
/usr/share/origami/gui/treeview.rb:390:in `reset_appearance': 
'Pango::STYLE_OBLIQUE' has been deprecated. Use 
'Pango::Style::OBLIQUE' or ':oblique'.
/usr/lib/ruby/vendor_ruby/glib2/deprecatable.rb:112:in 
`const_missing': uninitialized constant Pango::FontDescription::Weight 
(NameError)

Did you mean?  Pango::Weight
    from /usr/share/origami/gui/treeview.rb:63:in `initialize'
    from /usr/share/origami/gui/treeview.rb:28:in `new'
    from /usr/share/origami/gui/treeview.rb:28:in `create_treeview'
    from /usr/share/origami/gui/walker.rb:94:in `initialize'
    from /usr/share/origami/gui/walker.rb:60:in `new'
    from /usr/share/origami/gui/walker.rb:60:in `start'
    from /usr/bin/pdfwalker:6:in `'


IMO bug 1000618 should be downgraded. Given that there is a known workaround
and given that only one of the three reverse dependencies seems to be 
affected,
I don't think the bug can reasonably be regarded as rendering ruby-gtk2 
unusable.


origami-pdf clearly needs more work though, by someone with more ruby 
knowlege
than me if it is to get back into testing, I've attached a debdiff of 
what I have done

so far anyway.

diff -Nru origami-pdf-2.0.0/debian/changelog origami-pdf-2.0.0/debian/changelog
--- origami-pdf-2.0.0/debian/changelog  2016-10-28 19:21:34.0 +
+++ origami-pdf-2.0.0/debian/changelog  2022-03-05 19:11:29.0 +
@@ -1,3 +1,10 @@
+origami-pdf (2.0.0-1+rpi1) bookworm-staging; urgency=medium
+
+  * Apply workaround for ruby gtk2/openssl conflict.
+  * Fix tests with ruby 3.0.
+
+ -- Peter Michael Green   Sat, 05 Mar 2022 19:11:29 
+
+
 origami-pdf (2.0.0-1) unstable; urgency=medium
 
   

Bug#1006818: eye: (autopkgtest) failure on non-amd64

[Paul Gevers]

Source: eye
Version: 19.0221.2026~ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You package has an autopkgtest, great. However, it fails on all 
architectures but amd64. Can you please investigate the situation and 
fix it?


I copied some of the output at the bottom of this report. It seems that 
eye is expecting the run on amd64 exclusively. If that can't be 
reasonably be fixed, then please mark your test for amd64 exclusively 
(with the relatively new "Architecture" field in d/t/control).


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

Paul

[1] https://ci.debian.net/packages/e/eye/

https://ci.debian.net/data/autopkgtest/testing/arm64/e/eye/19245228/log.gz

autopkgtest [11:10:11]: test command1: prove debian/tests/*.t
autopkgtest [11:10:11]: test command1: [---

#   Failed test 'Check return from 'eye.pvm' is 0'
#   at debian/tests/eye.pvm.t line 9.
#  got: '127'
# expected: '0'

#   Failed test 'bare command, stderr'
#   at debian/tests/eye.pvm.t line 11.
#   '/usr/bin/eye.pvm: 3: exec: 
/usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found

# '
# doesn't match '(?^:Usage: eye.pvm)'

#   Failed test 'Check return from 'eye.pvm --help' is 0'
#   at debian/tests/eye.pvm.t line 13.
#  got: '127'
# expected: '0'

#   Failed test 'help, stderr'
#   at debian/tests/eye.pvm.t line 15.
#   '/usr/bin/eye.pvm: 3: exec: 
/usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found

# '
# doesn't match '(?^:Usage: eye.pvm)'

#   Failed test 'Check return from 'eye.pvm --n3 
reasoning/socrates/socrates.n3 --query 
reasoning/socrates/socrates-query.n3' is 0'

#   at debian/tests/eye.pvm.t line 17.
#  got: '127'
# expected: '0'

#   Failed test 'help, stderr'
#   at debian/tests/eye.pvm.t line 18.
#   ''
# doesn't match '(?^:r:because)'

#   Failed test 'help, stderr'
#   at debian/tests/eye.pvm.t line 19.
#   '/usr/bin/eye.pvm: 3: exec: 
/usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found

# '
# doesn't match '(?^s:starting .*\nGET .*\nnetworking .*\nreasoning)'
# Looks like you failed 7 tests of 15.
debian/tests/eye.pvm.t ..
Dubious, test returned 7 (wstat 1792, 0x700)
Failed 7/15 subtests

Test Summary Report
---
debian/tests/eye.pvm.t (Wstat: 1792 Tests: 15 Failed: 7)
  Failed tests:  3, 5, 8, 10, 13-15
  Non-zero exit status: 7
Files=1, Tests=15,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.06 cusr 
0.02 csys =  0.10 CPU)

Result: FAIL
autopkgtest [11:10:11]: test command1: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006819: thermald: Undocumented Options

[dirdi]

Package: thermald
Version: 2.4.7-2
Severity: minor
X-Debbugs-Cc: deb...@dirdi.name

At least the following options have not been documented at the man page:
--systemd
--test-mode
--adaptive

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
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=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thermald depends on:
ii  libc6 2.33-7
ii  libdbus-1-3   1.14.0-1
ii  libdbus-glib-1-2  0.112-2
ii  libevdev2 1.12.0+dfsg-1
ii  libgcc-s1 11.2.0-16
ii  libglib2.0-0  2.70.4-1
ii  liblzma5  5.2.5-2
ii  libstdc++611.2.0-16
ii  libupower-glib3   0.99.16-2
ii  libxml2   2.9.13+dfsg-1
ii  lsb-base  11.1.0

thermald recommends no packages.

thermald suggests no packages.

-- no debconf information

Bug#1006817: ifupdown-ng: ExecRestart systemd option does not exist

[Alexandre Iooss]

Package: ifupdown-ng
Version: 0.11.4~rc1-1
Severity: normal

networking.service is setting `ExecRestart` to
`/usr/share/ifupdown-ng/sbin/networking restart`. This does not seem to
be a supported or documented option of systemd.
Could it be removed?

ifupdown and ifupdown2 also provides networking.service, but without
`ExecRestart` option. This bug seems specific to ifupdown-ng.

-- System Information:
Architecture: amd64 (x86_64)

Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1006816: python-anyio: FTBFS in Ubuntu and local pbuilder (ipv6?)

[Gianfranco Costamagna]

Source: python-anyio
Version: 3.5.0-2
Severity: serious

Hello, in Ubuntu (where internet is really disabled your package FTBFS.
Looks like some ipv6 translation is not really working, but what worries me 
more is:

tests/test_sockets.py:1144: in test_getaddrinfo
correct = await getaddrinfo('faß.de', 0)
anyio/_core/_sockets.py:419: in getaddrinfo
gai_res = await get_asynclib().getaddrinfo(encoded_host, port, 
family=family, type=type,
anyio/_backends/_asyncio.py:1570: in getaddrinfo
result = await get_running_loop().getaddrinfo(
/usr/lib/python3.10/asyncio/base_events.py:855: in getaddrinfo
return await self.run_in_executor(
/usr/lib/python3.10/concurrent/futures/thread.py:58: in run
result = self.fn(*self.args, **self.kwargs)


Looks like an attempt to go over internet to me.

the following "patch" disables failing tests and makes the package go in Ubuntu 
release

--- python-anyio-3.5.0/debian/rules 2022-02-05 16:18:10.0 +
+++ python-anyio-3.5.0/debian/rules 2022-03-05 12:56:45.0 +
@@ -15,4 +15,4 @@
  dh_auto_test -- \
  --before-test '{interpreter} {dir}/setup.py egg_info 
--egg-base={dir}/.pybuild/egg' \
  --test-pytest \
- --test-args '--verbose -W ignore -k "not test_is_block_device"'
+ --test-args '--verbose -W ignore -k "not test_is_block_device and not 
test_happy_eyeballs and not test_getaddrinfo and not test_connection_refused"'



https://launchpadlibrarian.net/588853244/buildlog_ubuntu-jammy-amd64.python-anyio_3.5.0-2_BUILDING.txt.gz


= test session starts ==
platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
/usr/bin/python3.10
cachedir: .pytest_cache
hypothesis profile 'default' -> 
database=DirectoryBasedExampleDatabase('/<>/.pybuild/cpython3_3.10/build/.hypothesis/examples')
rootdir: /<>, configfile: pyproject.toml
plugins: anyio-3.5.0, hypothesis-6.36.0, mock-3.6.1
collecting ... collected 759 items / 2 deselected / 1 skipped / 756 selected

tests/test_compat.py::TestMaybeAsync::test_cancel_scope[asyncio] PASSED  [  0%]
tests/test_compat.py::TestMaybeAsync::test_cancel_scope[asyncio+uvloop] PASSED 
[  0%]
tests/test_compat.py::TestMaybeAsync::test_current_time[asyncio] PASSED  [  0%]
tests/test_compat.py::TestMaybeAsync::test_current_time[asyncio+uvloop] PASSED 
[  0%]
tests/test_compat.py::TestMaybeAsync::test_current_effective_deadline[asyncio] 
PASSED [  0%]
tests/test_compat.py::TestMaybeAsync::test_current_effective_deadline[asyncio+uvloop]
 PASSED [  0%]
tests/test_compat.py::TestMaybeAsync::test_get_running_tasks[asyncio] PASSED [  
0%]
tests/test_compat.py::TestMaybeAsync::test_get_running_tasks[asyncio+uvloop] 
PASSED [  1%]
tests/test_compat.py::TestMaybeAsync::test_get_current_task[asyncio] PASSED [  
1%]
tests/test_compat.py::TestMaybeAsync::test_get_current_task[asyncio+uvloop] 
PASSED [  1%]
tests/test_compat.py::test_maybe_async_cm[asyncio] PASSED[  1%]
tests/test_compat.py::test_maybe_async_cm[asyncio+uvloop] PASSED [  1%]
tests/test_compat.py::TestDeprecations::test_current_effective_deadlinee[asyncio]
 PASSED [  1%]
tests/test_compat.py::TestDeprecations::test_current_effective_deadlinee[asyncio+uvloop]
 PASSED [  1%]
tests/test_compat.py::TestDeprecations::test_current_time[asyncio] PASSED [  1%]
tests/test_compat.py::TestDeprecations::test_current_time[asyncio+uvloop] 
PASSED [  2%]
tests/test_compat.py::TestDeprecations::test_get_current_task[asyncio] PASSED [ 
 2%]
tests/test_compat.py::TestDeprecations::test_get_current_task[asyncio+uvloop] 
PASSED [  2%]
tests/test_compat.py::TestDeprecations::test_running_tasks[asyncio] PASSED [  
2%]
tests/test_compat.py::TestDeprecations::test_running_tasks[asyncio+uvloop] 
PASSED [  2%]
tests/test_compat.py::TestDeprecations::test_open_signal_receiver[asyncio] 
PASSED [  2%]
tests/test_compat.py::TestDeprecations::test_open_signal_receiver[asyncio+uvloop]
 PASSED [  2%]
tests/test_compat.py::TestDeprecations::test_cancelscope_cancel[asyncio] PASSED 
[  3%]
tests/test_compat.py::TestDeprecations::test_cancelscope_cancel[asyncio+uvloop] 
PASSED [  3%]
tests/test_compat.py::TestDeprecations::test_taskgroup_cancel[asyncio] PASSED [ 
 3%]
tests/test_compat.py::TestDeprecations::test_taskgroup_cancel[asyncio+uvloop] 
PASSED [  3%]
tests/test_compat.py::TestDeprecations::test_capacitylimiter_acquire_nowait[asyncio]
 PASSED [  3%]
tests/test_compat.py::TestDeprecations::test_capacitylimiter_acquire_nowait[asyncio+uvloop]
 PASSED [  3%]
tests/test_compat.py::TestDeprecations::test_capacitylimiter_acquire_on_behalf_of_nowait[asyncio]
 PASSED [  3%]
tests/test_compat.py::TestDeprecations::test_capacitylimiter_acquire_on_behalf_of_nowait[asyncio+uvloop]
 PASSED [  3%]
tests/test_compat.py::TestDeprecations::test_capacitylimiter_set_total_tokens[asyncio]
 PASSED [  4%]

Bug#1006768: golang-1.15 1.15.15-1~deb11u3 flagged for acceptance

[Adam D. Barratt]

Control: tags 1005340 + pending
Control: tags 1006768 - pending

On Sun, 2022-03-06 at 02:36 +0800, Shengjing Zhu wrote:
> Hi
> 
> On Sun, Mar 6, 2022 at 1:55 AM Adam D Barratt <
> a...@adam-barratt.org.uk> wrote:
> > package release.debian.org
> > tags 1006768 = bullseye pending
> > thanks
> > 
> 
> It should be 1005340 (1.15.15-1~deb11u3).
> 
> 1006768 is for another CVE, thus 1.15.15-1~deb11u4. Sorry for
> requesting a new version for golang-1.15 again.

Oops! Thanks for the note; fixing.

Regards,

Adam

Bug#1006815: xmoto: autopkgtest often fails: Failed to connect to X-Moto: Connection refused

[Simon McVittie]

Source: xmoto
Version: 0.6.1+repack-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

The superficial autopkgtest for xmoto seems to be failing intermittently,
especially on ppc64el (for whatever reason), which is likely to block
other packages' migration to testing.

In particular, I'm looking at this because of sdl12-compat: xmoto
currently uses libsdl1.2debian, which is the legacy SDL 1.2 package
(unmaintained upstream), but the long-term plan is for sdl12-compat
(a reimplementation of the SDL 1.2 API using SDL 2) to take over the
binary package name libsdl1.2debian.

It looks as though the test is waiting for an arbitrary 3 seconds for
the server to start listening, which is not always going to be enough.
It would be better if the test was something like this (using
approximately Python syntax here, but only as pseudocode):

start_time = time now
TIMEOUT = 60 seconds (or some other arbitrary semi-long time)

while True:
if server process has exited:
fail the test

if time now > start_time + TIMEOUT:
fail the test

try:
connect to socket
except ECONNREFUSED:
sleep(1)
except any other error:
fail the test
else:
break out of this loop

continue with the test

Or, as a stopgap, an alternative would be to mark the test as flaky
(which means its result will be ignored) and reduce the severity of this
bug report to non-RC.

Thanks,
smcv

Bug#1006468: cups: misleading documentation regarding root login credentials

[Brian Potkin]

tags 1006468 patch
thanks



On Fri 25 Feb 2022 at 17:02:06 -0500, Celejar wrote:

> Package: cups
> Version: 2.4.1op1-1
> Severity: normal
> 
> Hello,

Thank you for your report, Celejar.
 
> On a fresh CUPS install, I logged into the web interface as root to add
> a printer, and was denied with a 401 Forbidden error. The problem seems
> to be that root is not a member of a group in @SYSTEM (which by default
> only includes lpadmin). I understand that Debian has decided that this
> is not a bug:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616718
> 
> but Debian's documentation seems quite misleading and inconsistent on
> this point.
> 
> README.Debian states:
> 
> 'Administration' is where you need to be to set up a local print queue.
> At some point you will be required to authenticate. A User Name of 'root'
> and root's password is always acceptable. Any other user must be a member
> of the lpadmin group.
> 
> This clearly indicates that root does *not* need to be a member of the
> lpadmin group.

This is an accurate reflection of the situation for Debian distributions
up to and including bullseye. It is not the case on bookworm with cups
2.4.1op1-1. Please see #1006727:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006727
 
> OTOH, 'man cupsd.conf' is more accurate:
> 
> Note: The 'root'  user  is  not special and must be granted privileges
> like any other user account.
> 
> I suggest that the language of the README be modified to resemble that
> of the man page.

The thrust of the README is to point out that a user needs to be a
member of the lpadmin group, so a possible documentation change is:

  'Administration' is where a user needs to be to set up a local print
   queue. At some point authentication will be required. For this to
   be successful the user must be a member of the lpadmin group.

The assumption here is that "SystemGroup root lpadmin" is implemented.

Regards,

Brian.

Bug#1006768: golang-1.15 1.15.15-1~deb11u3 flagged for acceptance

[Shengjing Zhu]

Hi

On Sun, Mar 6, 2022 at 1:55 AM Adam D Barratt  wrote:
>
> package release.debian.org
> tags 1006768 = bullseye pending
> thanks
>

It should be 1005340 (1.15.15-1~deb11u3).

1006768 is for another CVE, thus 1.15.15-1~deb11u4. Sorry for
requesting a new version for golang-1.15 again.

-- 
Shengjing Zhu

Bug#1006299: capnproto: FTBFS with OpenSSL 3.0

[tony mancill]

On Sat, Mar 05, 2022 at 07:21:14PM +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-05 08:46:56 [-0800], tony mancill wrote:
> > 
> > This should be addressed by the upload of 0.9.1-3 to unstable.  The
> > package is building fine against experimental for me in a chroot.  Once it
> > transitions to testing, I'll update the fixed version and close the bug.
> 
> Didn't work for me:
>https://people.debian.org/~bigeasy/capnproto_0.9.1-3_amd64.txt.xz

Okay, there must be something amiss with my experimental sbuild setup.
Thank you for the correction.

Bug#1006299: capnproto: FTBFS with OpenSSL 3.0

[Sebastian Andrzej Siewior]

On 2022-03-05 08:46:56 [-0800], tony mancill wrote:
> 
> This should be addressed by the upload of 0.9.1-3 to unstable.  The
> package is building fine against experimental for me in a chroot.  Once it
> transitions to testing, I'll update the fixed version and close the bug.

Didn't work for me:
   https://people.debian.org/~bigeasy/capnproto_0.9.1-3_amd64.txt.xz

> Thanks,
> tony

Sebastian

Bug#1006137: fixed in golang-github-containers-common 0.33.4+ds1-1+deb11u1

[Adam D. Barratt]

Control: reopen -1
Control: tags -1 + pending

On Sat, 2022-03-05 at 18:02 +, Debian FTP Masters wrote:
[...]
> Date: Sun, 26 Sep 2021 18:29:08 -0400
> Source: golang-github-containers-common
> Architecture: source
> Version: 0.33.4+ds1-1+deb11u1
> Distribution: bullseye
> Urgency: medium
> Maintainer: Debian Go Packaging Team 
> Changed-By: Reinhard Tartler 
> Closes: 994451 1006137
> Changes:
>  golang-github-containers-common (0.33.4+ds1-1+deb11u1) bullseye;
> urgency=medium
>  .
>* Backport seccomp patches from upstream to allow execution of
> newer
>  syscalls. Closes: #994451, #1006137


Please don't close release.debian.org bugs in your changelog (for p-u
uploads or anything else).

For p-u requests, the bug should remain open until the change is
actually in (old)stable after a point release, at which point the
Release Team will close it.

Regards,

Adam

Bug#1004533: fixed in golang-github-opencontainers-specs 1.0.2.41.g7413a7f-1+deb11u1

[Adam D. Barratt]

Control: reopen -1
Control: tags -1 + pending

On Sat, 2022-03-05 at 18:02 +, Debian FTP Masters wrote:
[...]
> Date: Mon, 27 Sep 2021 12:12:47 -0400
> Source: golang-github-opencontainers-specs
> Architecture: source
> Version: 1.0.2.41.g7413a7f-1+deb11u1
> Distribution: bullseye
> Urgency: medium
> Maintainer: Debian Go Packaging Team 
> Changed-By: Reinhard Tartler 
> Closes: 994451 1004533
> Changes:
>  golang-github-opencontainers-specs (1.0.2.41.g7413a7f-1+deb11u1)
> bullseye; urgency=medium
>  .
>* Backport seccomp patches from upstream to allow execution of
> newer
>  syscalls, Closes: #994451, #1004533
> 

Please don't close release.debian.org bugs in your changelog (for p-u
uploads or anything else).

For p-u requests, the bug should remain open until the change is
actually in (old)stable after a point release, at which point the
Release Team will close it.

Regards,

Adam

Bug#1006814: transition: astc-encoder

[Timo Röhling]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

I'd like to transition astc-encoder after some backwards-incompatible
changes to a user-visible struct. I verified that filament, the only
reverse dependency, still builds on amd64.

The ben tracker at
https://release.debian.org/transitions/html/auto-astc-encoder.html
is fine.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmIjpgYACgkQ+C8H+466
LVmTaAv/dz08edid89bdSTXYokXlE5KDItHVfzZvj6OQ3G2fBje5yavaeD75ISMK
TnMO5HS5eMoSCrHSjDY7nNyB1tfOg2zjSf0/ZXTIiPtJmREohklv6+qIx7BD8oUL
8uP5fqKkWD8vsfqgZOO17Cn3jH84U0sj/MHQPAbEyhA9OsXNFmKD6ZOzRkYWqDZk
38HA8V4k4F8+W0mk4s1Fl0KyQB5Iraql0ahUGS61M0WOqc0FcLG2xl6IhbpisOs/
MQtcZmb66VuBMXp81Yd1XUPMrblu74MqacgWcvrWWlcAbs3Qme8Bn/sEApc6RzwU
TGCSSN5jg2m4RmMOC3BPx63vJaxe7VSDl7qMYyxMlN4z6ckQP7GEdWEWSdmJp/2b
jJ/1oqDPXVmRhZWujdkpKuXQflQ1jugYntDkz0IHy0Ox97ZEsCHD4Q34aD1LDclP
tzpQGkbRoJPvhikIAKOK4Ja32b5vL5wRTtvbl+btbW9C06cpqkjDd+2DsgiWwj+I
jvcXD96X
=Tpkl
-END PGP SIGNATURE-

Bug#1006342: usb.ids 2022.02.15-0+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1006342 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: usb.ids
Version: 2022.02.15-0+deb11u1

Explanation: update included data

Bug#1005288: sphinx-bootstrap-theme 0.7.1-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005288 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: sphinx-bootstrap-theme
Version: 0.7.1-1+deb11u1

Explanation: fix search functionality

Bug#1004247: weechat 3.0-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004247 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: weechat
Version: 3.0-1+deb11u1

Explanation: fix denial of service issue [CVE-2021-40516]

Bug#1005217: spip 3.2.11-3+deb11u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005217 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: spip
Version: 3.2.11-3+deb11u2

Explanation: fix several cross-site scripting issues

Bug#1004050: zziplib 0.13.62-3.3+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004050 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: zziplib
Version: 0.13.62-3.3+deb11u1

Explanation: fix denial of service issue [CVE-2020-18442]

Bug#1006768: golang-1.15 1.15.15-1~deb11u3 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1006768 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: golang-1.15
Version: 1.15.15-1~deb11u3

Explanation: fix IsOnCurve for big.Int values that are not valid coordinates 
[CVE-2022-23806]; math/big: prevent large memory consumption in Rat.SetString 
[CVE-2022-23772]; cmd/go: prevent branches from materializing into versions 
[CVE-2022-23773]

Bug#1006402: debian-ports-archive-keyring 2022.02.15~deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1006402 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: debian-ports-archive-keyring
Version: 2022.02.15~deb11u1

Explanation: add "Debian Ports Archive Automatic Signing Key (2023)"; move the 
2021 signing key to the removed keyring

Bug#1006138: libpod 3.0.1+dfsg1-3+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1006138 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libpod
Version: 3.0.1+dfsg1-3+deb11u1

Explanation: update seccomp support to enable use of newer kernel versions

Bug#1006222: openboard 1.5.4+dfsg1-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1006222 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: openboard
Version: 1.5.4+dfsg1-2+deb11u1

Explanation: fix application icon

Bug#1006137: golang-github-containers-common 0.33.4+ds1-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1006137 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: golang-github-containers-common
Version: 0.33.4+ds1-1+deb11u1

Explanation: update seccomp support to enable use of newer kernel versions

Bug#1005372: apache-log4j1.2 1.2.17-10+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005372 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: apache-log4j1.2
Version: 1.2.17-10+deb11u1

Explanation: resolve security issues [CVE-2021-4104 CVE-2022-23302 
CVE-2022-23305 CVE-2022-23307], by removing support for the JMSSink, 
JDBCAppender, JMSAppender and Apache Chainsaw modules

Bug#1005861: pdb2pqr 2.1.1+dfsg-7+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005861 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: pdb2pqr
Version: 2.1.1+dfsg-7+deb11u1

Explanation: fix complatibility of propka with Python 3.8 or above

Bug#1005052: installation-guide 20220129~deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005052 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: installation-guide
Version: 20220129~deb11u1

Explanation: update documentation and translations

Bug#1005010: node-nth-check 2.0.0-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005010 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-nth-check
Version: 2.0.0-1+deb11u1

Explanation: fix regular expression-based denial of service issue 
[CVE-2021-3803]

Bug#1005013: cinnamon 4.8.6-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005013 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: cinnamon
Version: 4.8.6-2+deb11u1

Explanation: fix crash when adding an online account with login

Bug#1005007: node-trim-newlines 3.0.0-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1005007 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-trim-newlines
Version: 3.0.0-1+deb11u1

Explanation: fix regular expression-based denial of service issue 
[CVE-2021-33623]

Bug#1004575: mutter 3.38.6-2~deb11u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004575 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: mutter
Version: 3.38.6-2~deb11u2

Explanation: backport various fixes from upstream's stable branch

Bug#1004533: golang-github-opencontainers-specs 1.0.2.41.g7413a7f-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004533 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: golang-github-opencontainers-specs
Version: 1.0.2.41.g7413a7f-1+deb11u1

Explanation: update seccomp support to enable use of newer kernel versions

Bug#1004384: node-cached-path-relative 1.0.2-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004384 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-cached-path-relative
Version: 1.0.2-1+deb11u1

Explanation: fix prototype pollution issue [CVE-2021-23518]

Bug#1004192: django-allauth 0.44.0+ds-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004192 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: django-allauth
Version: 0.44.0+ds-1+deb11u1

Explanation: fix OpenID support

Bug#1004033: node-fetch 2.6.1-5+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1004033 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-fetch
Version: 2.6.1-5+deb11u1

Explanation: don't forward secure headers to third party domains [CVE-2022-0235]

Bug#1003765: node-markdown-it 10.0.0+dfsg-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003765 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-markdown-it
Version: 10.0.0+dfsg-2+deb11u1

Explanation: fix regular expression-based denial of service issue 
[CVE-2022-21670]

Bug#1003058: openvswitch 2.15.0+ds1-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003058 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: openvswitch
Version: 2.15.0+ds1-2+deb11u1

Explanation: fix use-after-free issue [CVE-2021-36980]; fix installation of 
libofproto

Bug#1002703: libarchive 3.4.3-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1002703 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libarchive
Version: 3.4.3-2+deb11u1

Explanation: fix extracting hardlinks to symlinks; fix handling of symlink ACLs 
[CVE-2021-23177]; never follow symlinks when setting file flags [CVE-2021-31566]

Bug#1003018: php-laravel-framework 6.20.14+dfsg-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1003018 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: php-laravel-framework
Version: 6.20.14+dfsg-2+deb11u1

Explanation: fix cross-site scripting issue [CVE-2021-43808], missing blocking 
of executable content upload [CVE-2021-43617]

Bug#1002685: prips 1.1.1-3+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1002685 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: prips
Version: 1.1.1-3+deb11u1

Explanation: fix infinite wrapping if a range reaches 255.255.255.255; fix CIDR 
output with addresses that differ in their first bit

Bug#1002010: find-completion: don't look for -exec etc command if completing before it

[Frank Loeffler]

Package: bash-completion
Version: 1:2.11-2

Hi,

the same happens with Debian stable (bash-completion version 2.11-2). 
The same patch applies, cleanly, to that version too, and fixes the 
issue there as well.


As the fix is that simple and prevents a rather annoying crash, I hope 
this could be pushed into stable.


cheers,

Frank Löffler

Bug#1002652: schleuder 3.6.0-3+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1002652 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: schleuder
Version: 3.6.0-3+deb11u1

Explanation: migrate boolean values to integers, if the ActiveRecord SQLite3 
connection adapter is in use, restoring functionality

Bug#1001740: fcitx5-chinese-addons 5.0.4-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1001740 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: fcitx5-chinese-addons
Version: 5.0.4-1+deb11u1

Explanation: fcitx5-table: add missing dependencies on 
fcitx5-module-pinyinhelper and fcitx5-module-punctuation

Bug#1002051: heartbeat 3.0.6-11+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1002051 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: heartbeat
Version: 3.0.6-11+deb11u1

Explanation: fix creation of /run/heartbeat on systems using systemd

Bug#1006800: debian-installer: kernel mismatch for bookworm and sid installer. New release needed?

[Cyril Brulebois]

Roland Clobus  (2022-03-05):
> On 05/03/2022 12:40, Cyril Brulebois wrote:
> > We could, and should, release a new d-i and possibly an Alpha 1 at some
> > point, but I don't have a specific timeline for that.
> 
> Understood. I assume that an Alpha 1 release will be made somewhere
> near the release date of bookworm.

In the past I've tried to have an Alpha 1 released after a few months
into the new release cycle, then aim for something like a release every
1-2 months.

But the archive can disagree from time to time, and lately, I'm rather
busy with other things…

> Indeed. A new debian-installer upload would need to happen in
> lock-step with every new ABI in src:linux, to guarantee a consistent
> state of d-i. This could mean quite some work on your side.

Uploading more often could be doable; the current approach has been to
upload whenever we were getting close to wanting a new release of the
installer, following up with 1-2 more uploads if things didn't work out
immediately.

> I'm looking at possible solutions here (that's why I've added the
> rb-general mailing list):
> * (Manually) do official releases of debian-installer more often

Doable, as stated above.

>   (as I wrote, openQA will soon have some tests that detect when the
>   kernel version got out-of-sync)

Well, I do follow kernel uploads and ABI bumps closely, so that's a
problem that's already solved (git says since 2013).

FWIW we're seeing mutiple hours to multiple days of delay for some
architectures (we need the *-signed packages to get processed).

> * Automatically release git snapshots to deb.d.o instead of d-i.d.o

Uploading untested stuff to the archive, automatically? No, thanks.

> * Extend snapshot.d.o and/or snapshot.notset.fr to cover d-i.d.o in
>   addition to deb.d.o

Maybe avoidable if we go for more frequent uploads.

> * No changes, and accept that older images cannot be recreated (this
>   option is not preferred by me)
> * Other ...
> 
> > How long do you need to go back / how long do you need to keep a given
> > build? Maybe we could just keep (some) builds for a longer while there,
> > but that's at 90 days already.
> 
> Looking at https://d-i.debian.org/daily-images/amd64/, the current
> history I can see is about 15 days.

Right, ISTR that was around 30 days, glanced at the graph before hitting
the sack and didn't check thoroughly: we indeed clean more frequently
than showed on the graph.

> While investigating reproducible issues I personally tend to pick some
> timestamp and work on that for a longer period of time. 90 days would
> suffice completely for my purpose.

At the moment, daily-images is 42G, 6.8G of it being amd64. If we
estimate a ×6 in size for just that architecture, that's nearly doubling
that size, and it's only covering that one architecture. The machine is
shared across various services, but has 121G free at the moment, so we
could probably try something like that (maybe some middleground like 45
days for starters) if that helped in the very short term? Or would you
need to look at more architectures immediately?


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


signature.asc
Description: PGP signature

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Diederik de Haas]

On Monday, 21 February 2022 17:25:33 CET Petra Rübe-Pugliese wrote:
> > if yes, can you remote if from the kernel command line and see
> > if you get more information on the screen?
> 
> How would that be done?

If you do "cat /proc/cmdline" and see the word 'quiet' in there, then it's not 
as verbose as it could be on screen.

If you're using GRUB and the system boots up and you see the GRUB menu, press 
'e' to edit the line and remove the 'quiet' word. That way it will not be 
quiet for that boot.

If you want to remove it by default, look in /etc/default/grub and there you 
should see (f.e.):
GRUB_CMDLINE_LINUX_DEFAULT="quiet"

So if you remove the 'quiet' word there and do an update-grub, then the boot 
will be 'noisier' by default (on every boot).

HTH,
  Diederik

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

Bug#1006813: reportbug: lm-sensors.service executes sensors twice

[Armin Wolf]

Package: lm-sensors
Version: 1:3.6.0-7
Severity: normal

In lm-sensors.service, the sensors program is executed twice.
The second execution happens without the -s flag, causing
sensors to read all sensors and print the results to the
system log.
On a Dell Inspiron 3505 however, this results in a freeze for
~4 seconds during boot, caused by the second (and pointless)
execution of sensors coupled with very slow sensor reads.

In order to fix this issue, the second (and pointless) execution
of sensors should be omited.

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

Kernel: Linux 5.17.0-rc6-hwmon-next+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lm-sensors depends on:
ii  libc62.31-13+deb11u2
ii  libsensors5  1:3.6.0-7
ii  lsb-base 11.1.0
ii  perl 5.32.1-4+deb11u2
ii  sed  4.7-1

lm-sensors recommends no packages.

Versions of packages lm-sensors suggests:
pn  fancontrol  
ii  i2c-tools   4.2-1+b1
ii  read-edid   3.0.2-1.1

-- no debconf information

Bug#940329:

[Gregor Riepl]

Any progress?

This MR addresses the build errors and should make the package fit for
inclusion on Debian:

https://salsa.debian.org/debian/scantailor-advanced/-/merge_requests/12

Bug#1006807: chromium: No access yahoo and gmail

[Andres Salomon]

On Sat, 05 Mar 2022 10:06:44 -0500 bw wrote:
> Package: chromium
> Version: 99.0.4844.51-1~deb11u1
> Severity: normal
>
> Dear Maintainer,
>
> I appreciate you trying to keep up with all the changes.
>
> Since the last ver, unable to login to gmail or yahoo mail. Tried 
clearing cookies
> and poked around a little, but not able to spend much time on an app 
that changes

> every week.


Please try running chromium from a terminal, and let me know if there 
are any error messages that occur when you try to log into gmail and yahoo.

Bug#916016: qbittorrent: No search plugins available

[bruno zanetti]

Might be caused by a search plugin which doesn't play well with the
installed Python version.
There's an open upstream issue about it (
https://github.com/qbittorrent/qBittorrent/issues/13122). A workaround is
also reported there.

The qbittorrent version currently in sid (4.4.1) seems not broken as the
search plugin list shows ten items.

Regards

BZ

Bug#1006704: nmu: memlockd_1.3-2: rebuild to fix missing binary issue (Closes: #1000229)

[Sebastian Ramacher]

On 2022-03-03 08:13:29 +0800, Paul Wise wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> The current memlockd .deb does not contain /usr/sbin/memlockd, but
> simply rebuilding the package fixes the issue. This was reported in 
> #1000229 and confirmed by me using debuild and pbuilder. Please rebuild
> the package using a binNMU in order to fix the issue and close the bug.
> 
> nmu memlockd_1.3-2 . ANY . unstable . -m "rebuild to fix missing binary issue 
> (Closes: #1000229)"

How did that happen? I'd prefer that memlockd is fixed so that this
cannot happen again.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1006812: kodi: Kodi Fails to Start

[Vasyl Gello]

Hi Stephen,

19.4 is out and I am preparing the release.

This might take some time because I left all my infrastructure in Kharkiv, 
Ukraine
and relevant Debian RT ticket is not yet processed. Once I get access to
the beefy build machine I will upload everything.


-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#1006812: kodi: Kodi Fails to Start

[Sebastian Ramacher]

Control: reassign -1 src:waylandpp 0.2.9-1
Control: affects -1 kodi

On 2022-03-05 11:50:48 -0500, SDA wrote:
> Package: kodi
> Version: 2:19.3+dfsg1-1+b1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: marathon.duran...@gmail.com
> 
> Dear Maintainer,
> 
> Since system update on Thursday or Friday. Starting from the command line 
> throughs this output:
> 
> failed to open zone.tab
> /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: symbol lookup error: 
> /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: undefined symbol: 
> _ZN7wayland9display_t12create_queueEv

waylandpp broke its ABI:

-event_queue_t create_queue();
+event_queue_t create_queue() const;

Reassigning accordingly.

Cheers

> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.16.12-xanmod1 (SMP w/16 CPU threads)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_CA:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages kodi depends on:
> ii  kodi-bin   2:19.3+dfsg1-1+b1
> ii  kodi-data  2:19.3+dfsg1-1
> 
> Versions of packages kodi recommends:
> ii  kodi-repository-kodi [kodi-repository]  2:19.3+dfsg1-1
> ii  kodi-visualization-spectrum 19.0.0+ds1-2
> 
> kodi suggests no packages.
> 
> -- no debconf information
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature