Bug#1003644: src:frr: fails to migrate to testing for too long: FTBFS on mips64el & non-migrating new dependency

[Paul Gevers]

Source: frr
Version: 7.5.1-1.1
Severity: serious
Control: close -1 8.1-1
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:frr has been trying to migrate for 61 days 
[2]. Hence, I am filing this bug. Your package fails to build from 
source on mips64el. Your package also grew a (build) dependency that's 
new, but that's not migrating [3].


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 immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also 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=frr
[3] https://qa.debian.org/excuses.php?package=libyang2


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003643: src:lintian: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: lintian
Version: 2.111.0
Severity: serious
Control: close -1 2.114.0
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 999768

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:lintian has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. You have an unresolved RC bug 
that applies to the unstable package but not to the testing package, 
hence blocking migration.


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 immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also 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=lintian



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003642: [INTL:es] Spanish translation of the debconf template

[Camaleón]

Package: ocsinventory-agent
Severity: wishlist
Tags: patch l10n

Hello,
You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.
Cheers,

-- 
Camaleón# ocsinventory-agent po-debconf translation to Spanish
# Copyright (C) 2010 Software in the Public Interest
# This file is distributed under the same license as the ocsinventory-server 
package.
#
# Changes:
# - Initial translation
# Maria Germana Oliveira Blazetic , 2018
#
# - Updates
# Camaleón , 2020, 2022
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid ""
msgstr ""
"Project-Id-Version: ocsinventory-agent\n"
"Report-Msgid-Bugs-To: ocsinventory-ag...@packages.debian.org\n"
"POT-Creation-Date: 2018-04-12 19:34+0200\n"
"PO-Revision-Date: 2022-01-13 08:35+0100\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=n!=1;\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: select
#. Choices
#: ../ocsinventory-agent.templates:2001
msgid "local"
msgstr "local"

#. Type: select
#. Choices
#: ../ocsinventory-agent.templates:2001
msgid "http"
msgstr "http"

#. Type: select
#. Description
#: ../ocsinventory-agent.templates:2002
msgid "Method used to generate the inventory:"
msgstr "Método usado para generar el inventario:"

#. Type: select
#. Description
#: ../ocsinventory-agent.templates:2002
msgid "Choose the 'local' method if you do not have a network connection."
msgstr "Seleccione el método «local» si no posee una conexión de red."

#. Type: select
#. Description
#: ../ocsinventory-agent.templates:2002
msgid "Choose the 'http' method if an OCS Inventory server is set up."
msgstr "Seleccione el método «http» si posee un servidor de inventario OCS."

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:3001
msgid "OCS Inventory server URL:"
msgstr "Dirección URL del servidor de inventario OCS:"

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:3001
msgid "Please enter the URL of the OCS inventory server."
msgstr "Introduzca la dirección URL del servidor de inventario OCS."

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:4001
msgid "Tag for the generated inventory:"
msgstr "Etiqueta del inventario generado:"

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:4001
msgid ""
"Each inventory can have an associated tag. Please enter the tag you would "
"like for the new inventory."
msgstr ""
"Cada inventario puede tener una etiqueta asociada. Introduzca la etiqueta a "
"utilizar con el nuevo inventario."

#. Type: string
#. Description
#: ../ocsinventory-agent.templates:4001
msgid ""
"This field can be left blank to continue without setting a new tag for the "
"inventory."
msgstr ""
"Puede dejar este campo en blanco para continuar sin asignar una nueva "
"etiqueta al inventario."

Bug#1003641: systemd-oomd.service already active, refusing

[Jérémy Lal]

Package: systemd-oomd
Version: 250.2-2
Severity: normal

Hi,

i've installed systemd-oomd 250.2-1 and on upgrade,
noticed this:

systemd-oomd.socket: Socket service systemd-oomd.service already active, 
refusing.
Failed to listen on Userspace Out-Of-Memory (OOM) Killer Socket.

I'm not sure what should be done. Stop the service, disable the socket ?



-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (101, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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 systemd-oomd depends on:
ii  libc62.33-2
ii  systemd  250.2-2

systemd-oomd recommends no packages.

systemd-oomd suggests no packages.

-- no debconf information

Bug#1003640: mtree-netbsd FTCBFS: fails running tests

[Helmut Grohne]

Source: mtree-netbsd
Version: 20180822-6
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

mtree-netbsd fails to cross build from source, because it fails running
tests despite having them disabled via DEB_BUILD_OPTIONS=nocheck. Please
consider applying the attached patch to fix that.

Helmut
diff -u mtree-netbsd-20180822/debian/changelog 
mtree-netbsd-20180822/debian/changelog
--- mtree-netbsd-20180822/debian/changelog
+++ mtree-netbsd-20180822/debian/changelog
@@ -1,3 +1,10 @@
+mtree-netbsd (20180822-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Support DEB_BUILD_OPTIONS=nocheck. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 12 Jan 2022 05:32:45 +0100
+
 mtree-netbsd (20180822-6) unstable; urgency=medium
 
   * Remove dependency on freebsd-buildutils for now, since it is
diff -u mtree-netbsd-20180822/debian/rules mtree-netbsd-20180822/debian/rules
--- mtree-netbsd-20180822/debian/rules
+++ mtree-netbsd-20180822/debian/rules
@@ -33,6 +33,7 @@
 
 # Add tests
 override_dh_auto_test:
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
# Removing the next two to avoid dependency on freebsd-buildutils,
# which is currently blocking transition of this package into testing,
# per #957230.
@@ -40,3 +41,4 @@
#./mtree -c -K $(MTREE_KEYWORDS) | sed -e 
's/\(md5\|sha1\|sha256\|sha384\|sha512\)=/\1digest=/' -e 
's/rmd160=/ripemd160digest=/' | fmtree
bsdtar -cf - --options 
'mtree:uname,gname,md5,sha1,sha256,sha384,sha512,device,flags,gid,link,mode,nlink,size,time,uid,type,uname'
 --format mtree . | ./mtree
./mtree -c -K $(MTREE_KEYWORDS) | ./mtree -C -K $(MTREE_KEYWORDS) |  
grep md5= | grep sha1= | grep sha256= | grep gname= | grep -q uname=
+endif

Bug#944439: closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#944439: fixed in libimagequant 2.17.0-1)

[Helmut Grohne]

Control: reopen -1

On Mon, Jan 10, 2022 at 03:51:05PM +, Debian Bug Tracking System wrote:
> #944439: libimagequant FTCBFS: uses the build architecture compiler
> 
> It has been closed by Debian FTP Masters  
> (reply to Andreas Tille ).

Unfortunately, not. default.mk does not imply buildtools.mk. Therefore
CC is not set up correctly. Please retry.

Helmut

Bug#1003477: [Pkg-samba-maint] Bug#1003477: talloc FTCBFS: it's difficult

[Helmut Grohne]

Hi Mathieu,

On Tue, Jan 11, 2022 at 04:25:29PM +0100, Mathieu Parent wrote:
> Alternatively, a patch to waf would help too...

I did attach a patch to make it work with waf. Unfortunately, there are
two aspects that make it cumbersome with waf:
 * There is no dh_auto_* integration for waf, so all the logic has to be
   written in debian/rules.
 * waf's architecture makes cross building difficult. That's what you
   see in the patch.

So if short on time, maybe just take the patch I attached.

Helmut

Bug#1003639: gdb sometimes doesn't set hardware breakpoint for no discernible reason

[Frank Heckenbach]

Package: gdb
Version: 10.1-1.7
Severity: normal

>From a coomplicated gdb session
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003638):

(gdb) p (float*)$2
$29 = (float *) 0x556e612bd530
(gdb) watch *(float*)$29
Hardware watchpoint 10: *(float*)$29
(gdb) d 10
[...]
(gdb) watch *(float*)$30
Watchpoint 21: *(float*)$30
(gdb) d 21
(gdb) p $30
$31 = (float *) 0x556e614692d0
(gdb) p $30==(float*)0x556e614692d0
$32 = 1
(gdb) watch *(float*)0x556e614692d0
Hardware watchpoint 22: *(float*)0x556e614692d0
(gdb) d 22

So watching a float at some address (*$2) creates a hardware
watchpoint, but at another one (*$30) only a software watchpoint
(which in this case was unusably slow).

But watching the same address typed explicitly (and verified with
"==" to rule out copy/paste error) gave a hardware watchpoint again
(which did help to find the other bug :).

Nothing in the docs or on the net I could find gives any explanation
when and why gdb uses hardware watchpoints (only an option to force
software watchpoints which is the opposite I want).

I don't see any reason here, so I suppose it's a bug. If not, it
would be useful to at least tell the user why it doesn't.

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

Kernel: Linux 5.10.0-9-amd64 (SMP w/24 CPU threads)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdb depends on:
ii  libbabeltrace1  1.5.8-1+b3
ii  libc6   2.31-13+deb11u2
ii  libdebuginfod1  0.183-1
ii  libexpat1   2.2.10-2
ii  libgcc-s1   10.2.1-6
ii  libipt2 2.0.3-1
ii  liblzma55.2.5-2
ii  libmpfr64.1.0-3
ii  libncursesw66.2+20201114-2
ii  libpython3.93.9.2-1
ii  libreadline88.1-1
ii  libsource-highlight4v5  3.1.9-3+b1
ii  libstdc++6  10.2.1-6
ii  libtinfo6   6.2+20201114-2
ii  libxxhash0  0.8.0-2
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages gdb recommends:
ii  libc6-dbg [libc-dbg]  2.31-13+deb11u2

Versions of packages gdb suggests:
pn  gdb-doc
pn  gdbserver  

-- no debconf information

Bug#983035: Missing dependency on dbus-x11

[Trent W. Buck]

Francesco,

Is dbus-user-session installed?
xfce4-session recommends dbus-user-session, so
it SHOULD already be installed.


Francesco P. Lovergine wrote:
> Package: xfce4
> Version: 4.16
> Severity: normal
> 
> I found a missing dependency on /usr/bin/dbus-launch (dbus-x11) in bullseye,
> somewhere. Not sure this is an xfce4 issue specifically, feel free to
> reassign to another proper package.
> 
> In order to replicate the problem: I just installed from scratch a bullseye
> current image (debian/testing64) in vagrant, with virtualbox provider, an
> upgraded it.  Then installed xfce4i (the metapackage) and started lightdm.
> After that, the user cannot login and start a session due to missing
> dbus-launch, with appropriate message at screen. Installing dbus-x11 solves
> the problem.

dbus-launch (from "dbus-x11") package is the Old Way,
which is still attempted as a fallback.

Most systemd linux systems will instead use libpam-systemd to set up the user 
dbus session.
In this case, dbus-launch is not used.

You can see this in the source code -- if there's already a dbus
session (usually created by systemd), it just returns immediately.


https://sources.debian.org/src/xfce4-session/4.16.0-1/xfce4-session/main.c/#L275-L278

This is encoded in the control file like this:

https://sources.debian.org/src/xfce4-session/4.16.0-1/debian/control/#L31

On a Debian GNU/Linux architecture, that
will default to the systemd path (dbus-user-session).
Where systemd isn't available (e.g. Debian GNU/kFreeBSD),
it falls back to dbus-x11 (dbus-launch).

See also


https://sources.debian.org/src/xfce4-session/4.16.0-1/debian/changelog/#L37-L38
https://bugs.debian.org/836062

Bug#1003638: mbeq: uninitialized field access corrupts output

[Frank Heckenbach]

Package: swh-plugins
Version: 0.4.17-2+fh1
Severity: important
Tags: upstream patch

mbeq_1197.xml:

float coefs[FFT_LENGTH / 2];

[...]

coefs[0] = 0.0f;
for (bin=1; bin < (FFT_LENGTH/2-1); bin++) {
coefs[bin] = ((1.0f-bin_delta[bin]) * gains[bin_base[bin]])
  + (bin_delta[bin] * gains[bin_base[bin]+1]);
}

[...]

for (i = 1; i < FFT_LENGTH/2; i++) {
comp[i] *= coefs[i];
comp[FFT_LENGTH-i] *= coefs[i];
}

The first loop leaves coefs[FFT_LENGTH/2-1] uninitialized because it
only runs while bin < FFT_LENGTH/2-1.

The second loop reads from coefs[FFT_LENGTH/2-1], boom!

With some bad luck (which I had, of course, and of course only in
hard to reproduce circumstances) the uninitialized value will be NaN
which due to the FFT poisons the whole output with NaN.

Fix (note the "-1" is not needed at all. Maybe someone thought so
because of the "+1" in the line below, but that doesn't apply to bin
at all):

--- mbeq_1197.xml
+++ mbeq_1197.xml
@@ -140,7 +140,7 @@
 
 // Calculate coefficients for each bin of FFT
 coefs[0] = 0.0f;
-for (bin=1; bin < (FFT_LENGTH/2-1); bin++) {
+for (bin=1; bin < (FFT_LENGTH/2); bin++) {
coefs[bin] = ((1.0f-bin_delta[bin]) * gains[bin_base[bin]])
  + (bin_delta[bin] * gains[bin_base[bin]+1]);
 }

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

Kernel: Linux 5.10.0-9-amd64 (SMP w/24 CPU threads)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages swh-plugins depends on:
ii  libc6 2.31-13+deb11u2
ii  libfftw3-single3  3.3.8-2
ii  libgsm1   1.0.18-2

swh-plugins recommends no packages.

swh-plugins suggests no packages.

-- no debconf information

Bug#1000717: supysonic: FTBFS on Python 3.10

[Louis-Philippe Véronneau]

forwarded 1000717 https://github.com/spl0k/supysonic/issues/229
thanks

Pony has been updated to a version that supports python3.10, but using
it, I get this testsuite error, so I can't build:

==
FAIL: test_add_nowait_stop (tests.base.test_watcher.AudioWatcherTestCase)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9/build/tests/base/test_watcher.py",
line 117, in test_add_nowait_stop
self.assertTrackCountEqual(1)
  File "", line 2, in assertTrackCountEqual
  File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 531, in
new_func
result = func(*args, **kwargs)
  File
"/<>/.pybuild/cpython3_3.9/build/tests/base/test_watcher.py",
line 106, in assertTrackCountEqual
self.assertEqual(Track.select().count(), expected)
AssertionError: 0 != 1


-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002614: no longer report source-is-missing for binary file in source

[Shengjing Zhu]

Hi,

On Wed, Jan 12, 2022 at 07:04:39PM -0800, Felix Lechner wrote:
> Hi,
> 
> On Sat, Dec 25, 2021 at 7:00 AM Shengjing Zhu  wrote:
> >
> > I got rejected by ftp-master
> 
> Is there a record of the rejection? Which of these excluded files [1]
> did the Archive Team find in your sources? Thanks!
> 
> Kind regards
> Felix Lechner
> 
> [1] 
> https://salsa.debian.org/zhsj/kata-containers/-/blob/debian/experimental/debian/copyright#L4-63

It's at line 60, which is added in 
https://salsa.debian.org/zhsj/kata-containers/-/commit/f0414a6
File name is src/runtime/virtcontainers/pkg/firecracker/swagger_linux_amd64.

In my previous email, I have included the rejected tarball, which was put at
https://people.debian.org/~zhsj/temp/lintian-bug/kata-containers_2.3.0~rc1+ds1.orig.tar.gz

For the record of the rejection, unfortunately it's not archived. But if you 
have
irc log on #debian-ftp, it was replied on UTC 2021-12-25 12:02.

Bug#1003634: texlive-latex-base: \fontseries broken: seems to be cumulative until {m} or so?

[Thorsten Glaser]

Norbert Preining dixit:

>Fontseries combines weight and width, and thus theoretically any
>combination of weight (ul,el,l,sl,m,sb,b,eb,ub) and width
>(uc,ec,c,sc,sx,x,ex,ux) are possible.
>
>So c = width, b = weight, can be combined.

Yes, they *can* be combined.

If I do \fontseries{bc}.

But not if I do \fontseries{b} even if the previous
paragraph used \fontseries{c}.

At least not according to both intuitive understanding
and any kind of documentation I could find.

If you find whatever official documentation says different,
please do share… I couldn’t find that.

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent

Bug#1003634: closed by Norbert Preining (Re: Bug#1003634: texlive-latex-base: \fontseries broken: seems to be cumulative until {m} or so?)

[Thorsten Glaser]

reopen 1003634
thanks

Hi Norbert,

>> \fontfamily{Roboto-TLF}\fontseries{c}\fontsize{12pt}{12pt}\selectfont%
>> This is \f@series{} and should be c.
>>
>> \fontfamily{Roboto-TLF}\fontseries{b}\fontsize{40pt}{40pt}\selectfont%
>> This is \f@series{} and should be b.
>
>Fontseries combines weight and width, and thus theoretically any
>combination of weight (ul,el,l,sl,m,sb,b,eb,ub) and width
>(uc,ec,c,sc,sx,x,ex,ux) are possible.
>
>So c = width, b = weight, can be combined.

I know that they can be combined.

>When you then switch to m = width this is reset.

This does not match the documentation.

>See
>https://tug.org/texinfohtml/latex2e.html#Low_002dlevel-font-commands

This says:

   \fontseries{series}
  Select the font series. A series combines a weight and a width. 
Typically, a font supports only a
  few of the possible combinations. Some common combined series values 
include:

This implies that \fontseries{series} assigns series to \f@series.
Nowhere does it mention concatenation, or that ‘m’ (alone? others?)
resets it; the only mention of ‘m’ is…

  When forming the series string from the weight and width, drop the m 
that stands for medium
  weight or medium width, unless both weight and width are m, in which 
case use just one (‘m’).

… which basically says that, if your combination includes ‘m’ and
other things, you can drop one ‘m’.

>https://tex.stackexchange.com/questions/68745/possible-values-for-fontseries-and
>-fontshape

I was there earlier! ;-)

The question, all answers and all comments also do *not* mention
that it’s cumulative and reset by ‘m’; they also indicate rather
the contrary (that it’s set to the value given as #1).

>Closing the bug

Respectfully disagree here. At least we have a severe documentation
bug, if not an implementation bug if the documentation is correct
in that it should not accumulate.

おやすみなさい,
//mirabilos
-- 
“The final straw, to be honest, was probably my amazement at the volume of
petty, peevish whingeing certain of your peers are prone to dish out on
d-devel, telling each other how to talk more like a pretty princess, as though
they were performing some kind of public service.” (someone to me, privately)

Bug#1002614: no longer report source-is-missing for binary file in source

[Felix Lechner]

Hi,

On Sat, Dec 25, 2021 at 7:00 AM Shengjing Zhu  wrote:
>
> I got rejected by ftp-master

Is there a record of the rejection? Which of these excluded files [1]
did the Archive Team find in your sources? Thanks!

Kind regards
Felix Lechner

[1] 
https://salsa.debian.org/zhsj/kata-containers/-/blob/debian/experimental/debian/copyright#L4-63

Bug#867529: thermald.service should be a conffile

[Paul Wise]

On Fri, 2017-07-07 at 14:45 +1200, Ben Caradoc-Davies wrote:

> thermald.service is the only place where options such as --poll-
> interval can be set, so this file should be considered a package
> conffile. Because thermald.service is not a conffile, local changes
> to the command line are silently lost on upgrade.

systemd includes an extensive override mechanism so this should not be
needed and I think this bug can be closed. You can start it like this:

   systemctl edit thermald.service

Then remove all the lines that you don't want to override,
but keep the section headers intact.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1003497: who-uploads don't show u...@debian.org email default

[肖盛文]

also send to debian-keyr...@packages.debian.org

在 2022/1/13 00:31, Mattia Rizzolo 写道:

On Wed, Jan 12, 2022 at 12:35:36PM +0800, xiao sheng wen wrote:

I think it's not a bug of who-uploads itself, but also the public key of DD.

If the public key of DD has not set one uid entry formated as:

Name 

who-uploads will not show u...@debian.org email.


Is need forward this bug to debian-keyring package?

If that's the case (note that I didn't look at this at all, besides
looking up where the relevant code was), then it's not something we can
fix at all, and debian-keyring also can't do anything about it.


I'm not know the process of make debian-keyring package.

If debian-keyring can do this check will also better.



The UIDs of a GPG key can only be changed by the key owner, so at most
you'd have to privately tell each people to add such UIDs, and in the
end it also remains that they might not agree.


Is there any rules about DD uploader's gpg public key used in 
keyring.debian.org?

It's only has  "Name " uid entry in  keyring.debian.org's key 
is enough.
It's not need upload this public key to other public keyserver.


Thanks!
--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_0x00186602339240CB.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003540: gsl-doc: please update to 2.7.1

[Dirk Eddelbuettel]

On 13 January 2022 at 02:29, Andreas Beckmann wrote:
| On 11/01/2022 17.54, Dirk Eddelbuettel wrote:
| > On 11 January 2022 at 17:31, Andreas Beckmann wrote:
| > | Package: gsl-doc
| > | Version: 2.6-2
| > | Severity: serious
| > 
| > Why would that be a serious bug rather normal or even minor?
| 
| Feel free to downgrade, but try to have the versions in sync for the 
| bookworm release.

I have a moment now so I'll probably just do it.

| > It's a bit of a manual process becuase of the dfsg dance and manual ops.  
And
| > there generally is not that much that changes between versions -- GSL is
| > fairly mature and stable at this point.
| 
| because of such manual processes the separate src:*-doc sometimes look 
| like bitrot (e.g. scalapack 2.1 vs scalapack-doc 1.5) ...

Yes. And I starting to think that it may almost be better to withdraw the
-doc package then.  When we started to package (esp html-based) documentation
back in the day (say 20 years ago) connectivity was way worse.  Today most
people reach for the browser first. I would suspect popcon number support this.

Anyway, thanks for the nag :)

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1003635: adequate: check dbus files for invalid users/groups

[Paul Wise]

Package: adequate
Version: 0.15.6
Severity: normal
Control: clone -1 -2 -3
Control: retitle -2 adequate: check systemd files for invalid users/groups
Control: retitle -3 adequate: check init scripts for invalid users/groups

dbus files, systemd units and init scripts can reference users or
groups. Sometimes those don't exist on the system, which breaks some
feature of some programs. An example of this is thermald #864502, where
using the 'power' group instead of the 'powerdev' group breaks the
ThermalMonitor GUI program that uses the thermald dbus interface.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1003540: gsl-doc: please update to 2.7.1

[Andreas Beckmann]

On 11/01/2022 17.54, Dirk Eddelbuettel wrote:

On 11 January 2022 at 17:31, Andreas Beckmann wrote:
| Package: gsl-doc
| Version: 2.6-2
| Severity: serious

Why would that be a serious bug rather normal or even minor?


Feel free to downgrade, but try to have the versions in sync for the 
bookworm release.



It's a bit of a manual process becuase of the dfsg dance and manual ops.  And
there generally is not that much that changes between versions -- GSL is
fairly mature and stable at this point.


because of such manual processes the separate src:*-doc sometimes look 
like bitrot (e.g. scalapack 2.1 vs scalapack-doc 1.5) ...



Andreas

Bug#1003464: RFS: kic/2.4c-1 [QA] [RC] -- Enhanced KIC layout editor

[Andreas Beckmann]

On Mon, 10 Jan 2022 14:45:31 -0300 Hugo Torres  
wrote:

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


Having done the previous QA upload of this package,
I'll sponsor your work.


 kic (2.4c-1) experimental; urgency=medium


Please directly target unstable, not experimental.

Please add
  XS-Autobuild: yes
to the source stanza in debian/control, I'll ask for getting
the package enabled for autobuilding.
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable

Please fix the FTBFS, this looks like the upstream build
system does not support DESTDIR:

   dh_auto_install --destdir=debian/kic/
make -j16 install DESTDIR=/build/kic-2.4c/debian/kic 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/build/kic-2.4c'
cd src/bin; make install
make[2]: Entering directory '/build/kic-2.4c/src/bin'
cd ../kic; make
cd ../cd; make
cd ../convert; make
cd ../help; make
cd ../ginterf; make
cd ../xmfb; make
make[3]: Entering directory '/build/kic-2.4c/src/cd'
make[3]: '../cd.a' is up to date.
make[3]: Leaving directory '/build/kic-2.4c/src/cd'
make[3]: Entering directory '/build/kic-2.4c/src/kic'
make[3]: '../kic.a' is up to date.
make[3]: Leaving directory '/build/kic-2.4c/src/kic'
make[3]: Entering directory '/build/kic-2.4c/src/convert'
make[3]: '../convert.a' is up to date.
make[3]: Leaving directory '/build/kic-2.4c/src/convert'
make[3]: Entering directory '/build/kic-2.4c/src/help'
make[3]: '../help.a' is up to date.
make[3]: Leaving directory '/build/kic-2.4c/src/help'
make[3]: Entering directory '/build/kic-2.4c/src/ginterf'
make[3]: '../ginterf.a' is up to date.
make[3]: Leaving directory '/build/kic-2.4c/src/ginterf'
make[3]: Entering directory '/build/kic-2.4c/src/xmfb'
make[3]: '../xmfb.a' is up to date.
make[3]: Leaving directory '/build/kic-2.4c/src/xmfb'
mkdir /usr/lib/kic
mkdir: cannot create directory '/usr/lib/kic': Permission denied
installing kic in /usr/bin
chmod: cannot access '/usr/lib/kic': No such file or directory
make[2]: *** [Makefile:149: /usr/lib/kic] Error 1
make[2]: *** Waiting for unfinished jobs
install: cannot create regular file '/usr/bin/kic': Permission denied
installing kichelp in /usr/bin
install: cannot create regular file '/usr/bin/kichelp': Permission denied
installing kictocif in /usr/bin
install: cannot create regular file '/usr/bin/kictocif': Permission denied
installing ciftokic in /usr/bin
install: cannot create regular file '/usr/bin/ciftokic': Permission denied
installing kictostr in /usr/bin
install: cannot create regular file '/usr/bin/kictostr': Permission denied
installing strtokic in /usr/bin
install: cannot create regular file '/usr/bin/strtokic': Permission denied
installing strmtext in /usr/bin
install: cannot create regular file '/usr/bin/strmtext': Permission denied
installing kicscale in /usr/bin
install: cannot create regular file '/usr/bin/kicscale': Permission denied
make[2]: *** [Makefile:138: /usr/bin] Error 1
make[2]: Leaving directory '/build/kic-2.4c/src/bin'
make[1]: *** [Makefile:6: install] Error 2
make[1]: Leaving directory '/build/kic-2.4c'
dh_auto_install: error: make -j16 install DESTDIR=/build/kic-2.4c/debian/kic 
AM_UPDATE_INFO_DIR=no returned exit code 2
make: *** [debian/rules:5: binary] Error 25


Andreas

Bug#1003634: texlive-latex-base: \fontseries broken: seems to be cumulative until {m} or so?

[Thorsten Glaser]

Package: texlive-latex-base
Version: 2020.20210202-3
Severity: important
X-Debbugs-Cc: t...@mirbsd.de

MWE:

-BEGIN cutting here may damage your screen surface-
\documentclass{article}
\usepackage[T1]{fontenc}

\begin{document}

\makeatletter%
\fontfamily{Roboto-TLF}\fontseries{c}\fontsize{12pt}{12pt}\selectfont%
This is \f@series{} and should be c.

\fontfamily{Roboto-TLF}\fontseries{b}\fontsize{40pt}{40pt}\selectfont%
This is \f@series{} and should be b.

\fontfamily{Roboto-TLF}\fontseries{m}\fontsize{14pt}{14pt}\selectfont%
This is \f@series{} and should be m.

\end{document}
-END cutting here may damage your screen surface-

Running “pdflatex fontseries-bug.tex” and “mupdf fontseries-bug.pdf”
displays:

This is c and should be c.
This is bc and should be b.
This is m and should be m.

For some reason, \fontseries seems to be SOMETIMES cumulative.
This is directly against any documentation I can find online‽


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-rw-r-- 1 root staff 80 Jan 15  2016 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 2384 Nov  2 23:40 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Feb 12  2021 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Feb 17  2021 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Feb 17  2021 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Feb 13  2021 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Feb 17  2021 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Feb 17  2021 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5116 Nov  2 23:38 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Jun 15  2013 mktex.cnf
-rw-r--r-- 1 root root 475 Feb 13  2021 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-latex-base depends on:
ii  fonts-lmodern 2.004.5-6.1
ii  tex-common6.16
ii  texlive-base  2020.20210202-3
ii  texlive-binaries  2020.20200327.54578-7

texlive-latex-base recommends no packages.

Versions of packages texlive-latex-base suggests:
ii  texlive-latex-base-doc  2020.20210202-3

Versions of packages tex-common depends on:
ii  dpkg  1.20.9
ii  ucf   3.0043

Versions of packages tex-common suggests:
ii  debhelper  13.3.4

Versions of packages texlive-latex-base is related to:
ii  tex-common6.16
ii  texlive-binar

Bug#1003633: ITP: php-roundcube-rtf-html-php -- RTF to HTML converter in PHP

[Guilhem Moulin]

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

* Package name: php-roundcube-rtf-html-php
  Version : 2.1
  Upstream Author : Alexander van Oostenrijk , 
Aleksander Machniak 
* URL : https://github.com/roundcube/rtf-html-php
* License : GPL-2
  Programming Lang: PHP
  Description : RTF to HTML converter in PHP

 Short RTF to HTML converter in PHP, implementing the subset of RTF tags one
 needs in HTML and ignoring the rest.

This package is a new dependency of Roundcube.  It will be maintained in
the Debian Roundcube packaging team.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1003632: firefox: For text input, Ctrl-A overrides my GTK-3 bindings, with the consequence of possible data loss

[Vincent Lefevre]

Package: firefox
Version: 96.0-1
Severity: important
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1749840

For text input (forms, address bar...), in my GTK-3 settings
~/.config/gtk-3.0/gtk.css (attached), I have Ctrl-A bound to the
beginning of a paragraph (the usual meaning in Emacs). But with the
upgrade to firefox 96.0-1, this is no longer taken into account,
and Ctrl-A does a "select all" instead. This is particularly
annoying, and worse, as I'm used to type text just after that,
all the selected data are lost!!!

Note that some of my other GTK-3 bindings, such as Ctrl-E, Ctrl-K
and Ctrl-U, are still honored, showing that this file is still
taken into account.

-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox depends on:
ii  debianutils  5.5-1
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-3
ii  libc62.33-2
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-3
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi8  3.4.2-3
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.11.1+dfsg-1
ii  libgcc-s111.2.0-13
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.2-1
ii  libgtk-3-0   3.24.31-1
ii  libnspr4 2:4.32-3
ii  libnss3  2:3.73.1-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libstdc++6   11.2.0-13
ii  libvpx7  1.11.0-2
ii  libx11-6 2:1.7.2-2+b1
ii  libx11-xcb1  2:1.7.2-2+b1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.2-1
ii  libxtst6 2:1.2.3-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.4.1-2+b1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-6.1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-8
ii  libgssapi-krb5-2   1.18.3-7
ii  pulseaudio 15.0+dfsg1-3

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
/* $Id: gtk.css 89798 2016-06-17 10:50:31Z vinc17/cventin $
 *
 * GTK 3 style - ~/.config/gtk-3.0/gtk.css
 * See .
 */

GtkScrollbar
{
  -GtkRange-slider-width: 10;
  -GtkScrollbar-has-secondary-backward-stepper: true;
  -GtkScrollbar-has-secondary-forward-stepper: true;
}

@binding-set text-entry
{
  bind "a"
  {
"move-cursor" (paragraph-ends, -1, 0)
  };
  bind "e"
  {
"move-cursor" (paragraph-ends, 1, 0)
  };
  bind "k"
  {
"delete-from-cursor" (paragraph-ends, 1)
  };
  bind "u"
  {
"move-cursor" (paragraph-ends, -1, 0)
"delete-from-cursor" (paragraph-ends, 1)
  };
  bind "w"
  {
"delete-from-cursor" (word-ends, -1)
  };
}

/* The property name -gtk-key-bindings is used as of GTK+ 3.19.3
 * (in previous versions, it was gtk-key-bindings).
 */

entry
{
  -gtk-key-bindings: text-entry;
}

textview
{
  -gtk-key-bindings: text-entry;
}

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Steve Langasek]

Control: tags -1 moreinfo unreproducible

On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote:
> Package: libpam-runtime
> Version: 1.4.0-11
> Severity: critical
> Justification: breaks the whole system

> Dear Maintainer,
> 
>* Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
>with 
>```
>auth[success=0 default=ignore]  pam_ssh.so use_first_pass
>```
>* Login then failed
>* I've modified "success=0" -> "success=1" to get back the login.

So where does this 'success=0' come from?  It doesn't come from
/usr/share/pam-configs/ssh.  Installing libpam-ssh in unstable does not
result in a config containing this line.  I'm not sure 'success=0' is valid,
and if it is, it means 'on success, process the next module' so your bug
report, by slicing your config file to only show the single pam_ssh line,
does not show what happens afterward that actually fails the stack.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#613605: patch -b and -V options, overwrites file.orig despite manpage description

[Bruce Momjian]

Sorry, but I disagree and think this is a bug in Debian 11, GNU patch 
2.7.6.  -b forces a backup file, and the manual says of "-V existing":


  Make numbered backups of files that already have them, otherwise 
simple backups.  This is the default.


This example shows that the first patch application creates a backup 
file, and the second patch application overwrites it and does not 
instead create a numbered file:


$ echo 1 > a
$ cp a b
$ echo 2 >> b
$ diff a b > diff1
$ patch -b -V existing a < diff1
patching file a
$ ls -C
a  a.orig  b  diff1  diff2
$ echo 3 >> b
$ diff a b > diff2
$ patch -b -V existing a < diff2
patching file a
$ ls -C
a  a.orig  b  diff1  diff2
$ cat a.orig
1
2

--
Bruce Momjian  http://momjian.us
EDB  http://enterprisedb.com

Bug#1003631: dlocate: update-dpkg-list can deadlock

[Aaron M. Ucko]

Package: dlocate
Version: 1.09
Severity: important

Long story short, update-dpkg-list's batched bidirectional pipe usage
wound up deadlocking on a system with 20,000+ provided virtual
packages, mostly from installed librust-*-dev packages.

Could you please take a look?

Thanks!

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 
'testing'), (300, 'unstable-debug'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

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

Versions of packages dlocate depends on:
ii  dctrl-tools [grep-dctrl]  2.24-3+b1
ii  dpkg  1.21.1
ii  perl  5.32.1-6

Versions of packages dlocate recommends:
ii  supercat  0.5.7-1

dlocate suggests no packages.

-- debconf-show failed

Bug#1003002: autopkgtest-virt-qemu: Console setup issue on armhf

[Christian Kastner]

On 2022-01-12 20:14, Christian Kastner wrote:
> Addendum: I'm now occasionally also seeing this with arm64 when using
> sbuild with --chroot-mode=autopkgtest. I'd say it's 50/50 between
> success and failure.

Yet another data point: by reducing the CPU count to 1, it seems that
the success rate climbs to 100% on arm64.

No idea why this would have an effect on the communication with the VM.

That didn't work for armhf, though.

> $ sbuild --arch arm64 --dist unstable \
>   --bd-uninstallable-explainer apt \
>   --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu \
>   --autopkgtest-virt-server-opt --overlay-dir=/tmp \
>   --autopkgtest-virt-server-opt --qemu-architecture=aarch64 \
>   --autopkgtest-virt-server-opt --ram-size=2048 \
>   --autopkgtest-virt-server-opt --cpus=1 \
^^^
>   --autopkgtest-virt-server-opt=--debug \
>   --autopkgtest-virt-server-opt IMAGEFILE src.dsc

Bug#1003590: Due to python-debian bug

[Jelmer Vernooij]

reassign 1003590 python3-debmutate
fixed 1003590 0.47
thanks

This is due to a bug in the new python-debian deb822 parser/formatter.
The relevant bug for that is #996785.

I've switched debmutate back to the original parser, which should
address this issue.


signature.asc
Description: PGP signature

Bug#1003563: aide: autopkgtest regression: unexpected character: '@' in /etc/aide/aide.conf.d/31_aide_spamassassin

[Marc Haber]

tags #1003563 confirmed pending
thanks

On Tue, Jan 11, 2022 at 10:29:55PM +0100, Paul Gevers wrote:
> With a recent upload of aide the autopkgtest of aide fails in testing when
> that autopkgtest is run with the binary packages of aide from unstable.

I somehow forgot to upload the fixed package I prepared to fix this. I
apologize but it will be next week until the fix, which is:

commit 1500412bacbde4c362744e7ca516778a80b04ef1 (tag: debian/0.17.3-6)
Author: Marc Haber 
Date:   Thu Dec 30 22:25:08 2021 +0100

fix broken 31_aide_spamassassinrule

diff --git a/debian/aide.conf.d/31_aide_spamassassin 
b/debian/aide.conf.d/31_aide_spamassassin
index b8fc83c..73528e5 100644
--- a/debian/aide.conf.d/31_aide_spamassassin
+++ b/debian/aide.conf.d/31_aide_spamassassin
@@ -1,6 +1,6 @@
 @@ifndef SAVERSION
 @@define SAVERSION 3.004006
-@endif
+@@endif
 
 /@@{RUN}/spamd\\.pid$ f VarFile
 /var/spool/spamassassin/bayes$ d VarDir

which can be applied manualy since it's a conffile. This won't help with
autopkgtests, but it makes the package useable where it is installed.

Marc
Greetings

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

Bug#1003629: Updated debdiff

[Scott Kitterman]

Attached the wrong debdiff.  The only difference is the debian/changelog entry:

+python-dnslib (0.9.18-0deb11u1) bullseye; urgency=medium
+
+  * Remove d/patches/0001-Only-run-tests-for-python3.patch and set test
+versions in d/rules instead
+  * New upstream security release (CVE-2022-22846)
+
+ -- Scott Kitterman   Wed, 12 Jan 2022 15:41:12 -0500

Correct one attached.

Scott Kdiff -Nru python-dnslib-0.9.16/debian/changelog python-dnslib-0.9.18/debian/changelog
--- python-dnslib-0.9.16/debian/changelog	2021-12-05 15:05:46.0 -0500
+++ python-dnslib-0.9.18/debian/changelog	2022-01-12 15:41:12.0 -0500
@@ -1,3 +1,11 @@
+python-dnslib (0.9.18-0deb11u1) bullseye; urgency=medium
+
+  * Remove d/patches/0001-Only-run-tests-for-python3.patch and set test
+versions in d/rules instead
+  * New upstream security release (CVE-2022-22846)
+
+ -- Scott Kitterman   Wed, 12 Jan 2022 15:41:12 -0500
+
 python-dnslib (0.9.16-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru python-dnslib-0.9.16/debian/patches/0001-Only-run-tests-for-python3.patch python-dnslib-0.9.18/debian/patches/0001-Only-run-tests-for-python3.patch
--- python-dnslib-0.9.16/debian/patches/0001-Only-run-tests-for-python3.patch	2021-12-05 14:52:29.0 -0500
+++ python-dnslib-0.9.18/debian/patches/0001-Only-run-tests-for-python3.patch	1969-12-31 19:00:00.0 -0500
@@ -1,21 +0,0 @@
-From: Scott Kitterman 
-Date: Mon, 6 Jan 2020 02:40:47 -0500
-Subject: Only run tests for python3
-

- run_tests.sh | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/run_tests.sh b/run_tests.sh
-index 16bc398..3e22f06 100755
 a/run_tests.sh
-+++ b/run_tests.sh
-@@ -2,7 +2,7 @@
- 
- export PYTHONPATH=$(pwd)
- 
--: ${VERSIONS:="python python3"}
-+: ${VERSIONS:="python3"}
- 
- for src in __init__.py bimap.py bit.py buffer.py label.py dns.py lex.py server.py digparser.py ranges.py test_decode.py
- do
diff -Nru python-dnslib-0.9.16/debian/patches/series python-dnslib-0.9.18/debian/patches/series
--- python-dnslib-0.9.16/debian/patches/series	2021-12-05 14:52:29.0 -0500
+++ python-dnslib-0.9.18/debian/patches/series	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-0001-Only-run-tests-for-python3.patch
diff -Nru python-dnslib-0.9.16/debian/rules python-dnslib-0.9.18/debian/rules
--- python-dnslib-0.9.16/debian/rules	2021-12-05 14:45:18.0 -0500
+++ python-dnslib-0.9.18/debian/rules	2022-01-12 15:37:44.0 -0500
@@ -6,4 +6,4 @@
 	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_test:
-	./run_tests.sh
+	VERSIONS="python3" ./run_tests.sh
diff -Nru python-dnslib-0.9.16/dnslib/client.py python-dnslib-0.9.18/dnslib/client.py
--- python-dnslib-0.9.16/dnslib/client.py	2020-06-09 04:01:28.0 -0400
+++ python-dnslib-0.9.18/dnslib/client.py	2022-01-09 18:07:12.0 -0500
@@ -76,6 +76,9 @@
 a_pkt = q.send(address,port,tcp=args.tcp)
 a = DNSRecord.parse(a_pkt)
 
+if q.header.id != a.header.id:
+raise DNSError('Response transaction id does not match query transaction id')
+
 if a.header.tc and args.noretry == False:
 # Truncated - retry in TCP mode
 a_pkt = q.send(address,port,tcp=True)
diff -Nru python-dnslib-0.9.16/dnslib/__init__.py python-dnslib-0.9.18/dnslib/__init__.py
--- python-dnslib-0.9.16/dnslib/__init__.py	2021-05-07 12:08:33.0 -0400
+++ python-dnslib-0.9.18/dnslib/__init__.py	2022-01-09 18:17:03.0 -0500
@@ -274,6 +274,14 @@
 ;; OPT PSEUDOSECTION
 ; EDNS: version: 0, flags: do; udp: 4096
 
+Note that when using the library you should always validate the received TXID 
+
+q = DNSRecord.question("abc.com")
+a_pkt = q.send(address,port,tcp=args.tcp)
+a = DNSRecord.parse(a_pkt)
+if q.header.id != a.header.id:
+raise DNSError('Response transaction id does not match query transaction id')
+
 The library also includes a simple framework for generating custom DNS
 resolvers in dnslib.server (see module docs). In most cases this just
 requires implementing a custom 'resolve' method which receives a question
@@ -359,6 +367,8 @@
 Add support for all RR types to NSEC type bitmap
  Merge pull request #17 from sunds/issue_16
 Issue 16: uncaught exceptions leak open sockets
+ *   0.9.18  2022-01-09  Validate TXID in client.py (Issue #30 - thanks to @daniel4x)
+   
 
 License:
 
@@ -381,7 +391,7 @@
 
 from dnslib.dns import *
 
-version = "0.9.16"
+version = "0.9.18"
 
 if __name__ == '__main__':
 import doctest,sys,textwrap
diff -Nru python-dnslib-0.9.16/dnslib/server.py python-dnslib-0.9.18/dnslib/server.py
--- python-dnslib-0.9.16/dnslib/server.py	2021-05-07 11:20:19.0 -0400
+++ python-dnslib-0.9.18/dnslib/server.py	2022-01-09 18:05:47.0 -0500
@@ -302,7 +302,7 @@
 print("\n",dnsobj.toZone(""),"\n",sep="")
 
 
-class UDPServer(so

Bug#999074: iec16022: missing required debian/rules targets build-arch and/or build-indep

[Jakob Haufe]

Debdiff attached


-- 
ceterum censeo microsoftem esse delendam.


iec16022_0.2.4-1.3.debdiff
Description: Binary data


pgpOOIv0YySy9.pgp
Description: OpenPGP digital signature

Bug#1003629: bullseye-pu: package python-dnslib/0.9.16-1

[Scott Kitterman]

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

Security issue was evaluated as no-dsa, so following up as a regular
stable update:

https://security-tracker.debian.org/tracker/CVE-2022-22846

The dnslib package through 0.9.16 for Python does not verify that the ID value
in a DNS reply matches an ID value in a query.

The only change in the new upstream release is the fix for this issue,
so it seems better to bump to the new release.  Package is ready for
upload.  Both package and autopkgtest tests pass.  There is a minor
change from how the tests were called bullseye to better match with how
it was done with this version in unstable.

Most of the change is documentation changes driven by tooling changes in
the upstream build system.  The code changes are very minor.

bullseye debdiff attached.

Scott K
diff -Nru python-dnslib-0.9.16/debian/changelog 
python-dnslib-0.9.18/debian/changelog
--- python-dnslib-0.9.16/debian/changelog   2021-12-05 15:05:46.0 
-0500
+++ python-dnslib-0.9.18/debian/changelog   2022-01-12 10:19:36.0 
-0500
@@ -1,3 +1,13 @@
+python-dnslib (0.9.18-1) unstable; urgency=medium
+
+  * Remove d/patches/0001-Only-run-tests-for-python3.patch and set test
+versions in d/rules instead
+  * Iterate over supported python3 versions during build test
+  * Update dh_auto_test override to check DEB_BUILD_OPTIONS
+  * New upstream release
+
+ -- Scott Kitterman   Wed, 12 Jan 2022 10:19:36 -0500
+
 python-dnslib (0.9.16-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru 
python-dnslib-0.9.16/debian/patches/0001-Only-run-tests-for-python3.patch 
python-dnslib-0.9.18/debian/patches/0001-Only-run-tests-for-python3.patch
--- python-dnslib-0.9.16/debian/patches/0001-Only-run-tests-for-python3.patch   
2021-12-05 14:52:29.0 -0500
+++ python-dnslib-0.9.18/debian/patches/0001-Only-run-tests-for-python3.patch   
1969-12-31 19:00:00.0 -0500
@@ -1,21 +0,0 @@
-From: Scott Kitterman 
-Date: Mon, 6 Jan 2020 02:40:47 -0500
-Subject: Only run tests for python3
-

- run_tests.sh | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/run_tests.sh b/run_tests.sh
-index 16bc398..3e22f06 100755
 a/run_tests.sh
-+++ b/run_tests.sh
-@@ -2,7 +2,7 @@
- 
- export PYTHONPATH=$(pwd)
- 
--: ${VERSIONS:="python python3"}
-+: ${VERSIONS:="python3"}
- 
- for src in __init__.py bimap.py bit.py buffer.py label.py dns.py lex.py 
server.py digparser.py ranges.py test_decode.py
- do
diff -Nru python-dnslib-0.9.16/debian/patches/series 
python-dnslib-0.9.18/debian/patches/series
--- python-dnslib-0.9.16/debian/patches/series  2021-12-05 14:52:29.0 
-0500
+++ python-dnslib-0.9.18/debian/patches/series  1969-12-31 19:00:00.0 
-0500
@@ -1 +0,0 @@
-0001-Only-run-tests-for-python3.patch
diff -Nru python-dnslib-0.9.16/debian/rules python-dnslib-0.9.18/debian/rules
--- python-dnslib-0.9.16/debian/rules   2021-12-05 14:45:18.0 -0500
+++ python-dnslib-0.9.18/debian/rules   2022-01-12 10:12:33.0 -0500
@@ -6,4 +6,6 @@
dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_test:
-   ./run_tests.sh
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
+   VERSIONS="$(shell py3versions -s)" ./run_tests.sh
+endif
diff -Nru python-dnslib-0.9.16/dnslib/client.py 
python-dnslib-0.9.18/dnslib/client.py
--- python-dnslib-0.9.16/dnslib/client.py   2020-06-09 04:01:28.0 
-0400
+++ python-dnslib-0.9.18/dnslib/client.py   2022-01-09 18:07:12.0 
-0500
@@ -76,6 +76,9 @@
 a_pkt = q.send(address,port,tcp=args.tcp)
 a = DNSRecord.parse(a_pkt)
 
+if q.header.id != a.header.id:
+raise DNSError('Response transaction id does not match query 
transaction id')
+
 if a.header.tc and args.noretry == False:
 # Truncated - retry in TCP mode
 a_pkt = q.send(address,port,tcp=True)
diff -Nru python-dnslib-0.9.16/dnslib/__init__.py 
python-dnslib-0.9.18/dnslib/__init__.py
--- python-dnslib-0.9.16/dnslib/__init__.py 2021-05-07 12:08:33.0 
-0400
+++ python-dnslib-0.9.18/dnslib/__init__.py 2022-01-09 18:17:03.0 
-0500
@@ -274,6 +274,14 @@
 ;; OPT PSEUDOSECTION
 ; EDNS: version: 0, flags: do; udp: 4096
 
+Note that when using the library you should always validate the received TXID 
+
+q = DNSRecord.question("abc.com")
+a_pkt = q.send(address,port,tcp=args.tcp)
+a = DNSRecord.parse(a_pkt)
+if q.header.id != a.header.id:
+raise DNSError('Response transaction id does not match query 
transaction id')
+
 The library also includes a simple framework for generating custom DNS
 resolvers in dnslib.server (see module docs). In most cases this just
 requires implementing a custom 'resolve' method which receives a question
@@ -359,6 +367,8 @@
 Add support for all RR types to NSEC type bitmap
  Merge p

Bug#1003619: skimage: autopkgtest usually fails on armhf - out of memory

[Paul Gevers]

Control: reassign -1 src:skimage
Control: severity -1 important
Control: found -1 0.18.1-1

Hi,

On 12-01-2022 19:25, Rebecca N. Palmer wrote:
The skimage autopkgtest usually, but not always, fails on armhf with 
several out-of-memory errors:

https://ci.debian.net/packages/s/skimage/testing/armhf/


Flaky test are normally RC (but see below). Please fix the test (or 
disable it on armhf via the "Architecture" field in the d/t/control file 
[1]).


It currently happens that the last migration-reference passed and the 
last few non-references failed, so this counts as an autopkgtest 
regression.  I consider it more likely that the server just happened to 
have more RAM free when it ran the reference, but I don't have proof of 
that.


Our host that runs armhf tests has 255 GB RAM, so I doubt it's free RAM 
(we never come close to full use: 
https://ci.debian.net/munin/ci-worker-armel-01/ci-worker-armel-01/memory.html) 
This looks more like it's reaching the limits of the *reachable* memory 
on 32 bits architectures. See e.g. the discussion we had in 
https://github.com/pytroll/satpy/issues/1883 (near the end)


That said, it seems that version 0.18.1-1 was most of the time passing 
until 2021-06-13. I think that's about the time that we switched hosts 
for our arm64 tests. The new host is *more* powerful and has *more* 
memory; 140 cores and as said 255 GB. As the maintainer of ci.d.n I 
offer my help to debug the issue. I can run the test on our host, is 
there something I can run or collect in the testbed that would help you 
debug the issue?


Paul

[1] 
https://salsa.debian.org/ci-team/autopkgtest/-/raw/master/doc/README.package-tests.rst


OpenPGP_signature
Description: OpenPGP digital signature

Bug#892058: Thanks for the reminder

[Dima Kogan]

Thanks for the annual ping. You helped me avoid pain several years in a
row now.

Bug#1003622: chromium: microphone stopped working after upgrade

[Andres Salomon]

On Wed, 12 Jan 2022 20:19:04 +0100 "Francesco Poli (wintermute)" wrote:
> Package: chromium
> Version: 97.0.4692.71-0.1
> Severity: important
>
> Hello,
> just after upgrading chromium to the latest version in sid
> (97.0.4692.71-0.1), I was no longer able to use the microphone
> on videoconferencing platforms.
> Trying to enable my mic resulted in it being immediately disabled
> again. Trying one more time, and it was immediately disabled again.
> And again. And again.
>

Hi,

Thanks for the bug report. Can you please start chromium from a terminal 
and then go to your videoconferencing site and see if there are any 
error messages that it outputs?


Also, is it multiple videoconferencing sites, or just one? I just tried 
https://meet.jit.si with the new chromium version, and the mic worked 
for me. So we need to narrow down what's causing this.


Thanks,

Andres

Bug#1003606: python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4)

[Martina Ferrari]

Argh, this was removed by `cme fix dpkg` and I trusted it.. :-/

Thanks for the report!

On 12/01/2022 14:15, Andreas Beckmann wrote:

Package: python3-flask-httpauth
Version: 4.5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

   Preparing to unpack .../python3-flask-httpauth_4.5.0-1_all.deb ...
   Unpacking python3-flask-httpauth (4.5.0-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man1/flask-httpauth.1.gz', which is 
also in package python-flask-httpauth-doc 3.2.4-3.1
   Errors were encountered while processing:
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb

Obviously the manpage was moved between the packages.


cheers,

Andreas



--
Martina Ferrari (Tina)

Bug#1003628: imdbpy: autopkgtest failure on arm64: AssertionError: assert '' == 'Mandariinid'

[Paul Gevers]

Source: imdbpy
Version: 2021.04.18-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package imdbpy, great. 
However, it fails. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it?


I copied some of the output at the bottom of this report.

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

Paul

[1] https://qa.debian.org/excuses.php?package=imdbpy

https://ci.debian.net/data/autopkgtest/testing/arm64/i/imdbpy/18081764/log.gz

=== FAILURES 
===
___ test_movie_original_title[http] 



ia = 

def test_movie_original_title(ia):
movie = ia.get_movie('2991224', info=['main'])
title = movie.get('original title', '')

  assert title == 'Mandariinid'

E   AssertionError: assert '' == 'Mandariinid'
E - Mandariinid

tests/test_http_movie_titles.py:13: AssertionError
=== short test summary info 

FAILED tests/test_http_movie_titles.py::test_movie_original_title[http] 
- Ass...
 1 failed, 342 passed, 19 skipped in 308.55s (0:05:08) 
=

autopkgtest [11:35:41]: test unittests



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976811: [pkg-php-pear] Bug#976811: transition: php8.1

[Paul Gevers]

Hi,

On 12-01-2022 15:56, David Prévot wrote:
In unstable (thanks for that), but it fails to migrate to testing, due 
to the 'PHPUnit requires the "dom" extension.' issue.


Can’t find this issue. Did it go away by itself, or did you make any 
change?


https://ci.debian.net/packages/p/php-doctrine-cache/testing/amd64/ shows 
that it's "fixed" by the new upload of src:php-defaults. php-common has 
a whole bunch of Breaks, which cause the test to be run with:

src:php-defaults from unstable
src:php-amqp from unstable
src:php-apcu from unstable
src:php-doctrine-cache-bundle from un...
src:php-doctrine-cache from unstable
src:php-gnupg from unstable
src:php-memcache from unstable
src:php-memcached from unstable
src:php-pcov from unstable
src:php-redis from unstable
src:php-uopz from unstable
src:php-uploadprogress from unstable
src:xdebug from unstable


symfony: php-apcu-bc


There seems to be a new (unrelated?) FTBFS, so we need to figure it 
out (or drop symfony from testing until then).


Found a fix, version 5.4.2+dfsg-2 uploaded.


Thanks.

It seems like we're getting somewhere. Some packages still need a 
source-only upload. And we need to weed through the regressions listed 
here: https://qa.debian.org/excuses.php?package=php-defaults. Priority 
may lay with the mediawiki* regression on i386: "Internal Server Error" 
doesn't sound great, and other non-horde package.


I nearly reached the php-defaults set with my bug filing campaign for 
autopgktest regressions, so I'll weed through it. Once all bugs are 
filed, I'll ignore all deprecation warning only tests.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003627: fpc: autopkgtest regression on ppc64el:

[Paul Gevers]

Source: fpc
Version: 3.2.2+dfsg-5
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of fpc the autopkgtest of fpc fails in testing when 
that autopkgtest is run with the binary packages of fpc from unstable on 
ppc64el. It passes when run with only packages from testing. In tabular 
form:


   passfail
fpcfrom testing3.2.2+dfsg-5
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=fpc

https://ci.debian.net/data/autopkgtest/testing/ppc64el/f/fpc/18260761/log.gz

Total = 7734 (55:7679)
Total number of compilations = 4753 (17:4736)
Successfully compiled = 3605
Successfully failed = 1131
Compilation failures = 14
Compilation that did not fail while they should = 3
Total number of runs = 2981 (38:2943)
Successful runs = 2943
Failed runs = 38
Number units compiled = 152
Number program that should not be run = 468
Number of skipped tests = 632
Number of skipped graph tests = 10
Number of skipped interactive tests = 31
Number of skipped known bug tests = 7
Number of skipped tests for other versions = 5
Number of skipped tests for other cpus = 397
Number of skipped tests for other targets = 182
make: Leaving directory 
'/tmp/autopkgtest-lxc.ims6woux/downtmp/build.IH3/src/fpcsrc/tests'

Let's save some of the output
Compare the new results with known results if we have them

Difference between expected failures and current failures:
--- debian/tests/ref_fail_powerpc64-linux	2021-12-30 13:48:26.0 
+
+++ fpcsrc/tests/output/powerpc64-linux/faillist	2022-01-12 
08:26:51.116689429 +

@@ -39,6 +39,7 @@
 webtbs/tw3157
 webtbs/tw36179
 webtbs/tw36863
+webtbs/tw36934a
 webtbs/tw3930
 webtbs/tw3964b
 webtbs/tw4809

Checking (and fail if so) for new failures:
Unexpected failures
autopkgtest [08:26:51]: test run-upstream-testsuite



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003626: binutils-doc: --as-needed default is wrongly documented

[Dave Love]

Package: binutils-doc
Version: 2.35.2-2
Severity: normal
X-Debbugs-Cc: none, Dave Love 

The Info and man pages for ld say "--no-as-needed restores the default
behaviour", but the default changed at some stage to --as-needed.

  $ cc -shared -lm -o x.so
  $ lddtree x.so
  x.so => ./x.so (interpreter => none)
  $ cc -shared -Wl,--no-as-needed -lm -o x.so
  $ lddtree x.so
  x.so => ./x.so (interpreter => none)
  libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
  ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6

-- 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.10.0-9-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

binutils-doc depends on no packages.

binutils-doc recommends no packages.

Versions of packages binutils-doc suggests:
ii  binutils  2.35.2-2

-- no debconf information

Bug#1003625: lsb-release: still ships python2 package file

[Julian Gilbey]

Package: lsb-release
Version: 11.1.0
Severity: normal

This package still ships the file
/usr/lib/python2.7/dist-packages/lsb_release.py
despite /usr/bin/lsb_release having /usr/bin/python3 in the header.
This file should simply be removed from the package.

Best wishes,

   Julian

Bug#1003609: readlink: invalid option -- 'b' in /lib/lsb/init-functions.d/40-systemd

[Christoph Berg]

Re: Michael Biebl
> 
> Control: reassign -1 systemd, slony1-2-bin
> 
> I'm rather convinced this should be addressed in slony1-2-bin (by ideally
> providing native .service units).
> Or at least by avoiding the use a root shell and sourcing
> /lib/lsb/init-functions, but instead using something like start-stop-daemon
> -u

I hate init scripts, and one of the reasons for that is that I have
inherited too many packages with weird init scripts like the slony
one.

I'll supply a .service unit instead.

Christoph

Bug#1002298: bullseye-pu: package clamav/0.103.4+dfsg-0+deb11u1

[Sebastian Andrzej Siewior]

On 2022-01-11 21:17:54 [+], Adam D. Barratt wrote:
> Now that the equivalent update made it to stretch, this seems as good a
> time as any - I'm assuming that no major issues have ben reported in
> unstable in the meantime?

correct.

> I wasn't really sure which of the changes made sense to mention, but
> had a go at an initial draft for an announcement. Tweaks, updates or
> complete rewrites welcome:
> 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> ClamAV is an AntiVirus toolkit for Unix.
> 
> Upstream published version 0.103.4.
> 
> This is a bug-fix release and an upstream LTS release. The changes are not
> currently required for operation, but upstream strongly recommends that users
> update.

Maybe adding something like
  ", but upstream strongly recommends that users update for continued
  support."

Upstream asks to use latest patch level version for support which
includes access to the signature database.

Speaking of latest patch version: Upstream released today .5. Would you
prefer to wait with this until I upload .5 to unstable and
stable/oldstable for this (and avoiding a second announcement)?

> Changes since 0.103.3 currently in buster and bullseye include fixes for
> several possible crashes, corrected handling of 0-byte incremental database
> updates and the renaming of several heuristic-based alerts.
> 
> If you use clamav, we recommend that you install this update.
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 
> Regards,
> 
> Adam

Sebastian

Bug#1003446: bugs.debian.org: bugspam.cgi fails with 7-digit bug numbers

[gregor herrmann]

On Tue, 11 Jan 2022 21:28:03 -0800, Don Armstrong wrote:

> Thanks for the report and the patch; I've applied it, and it should be
> replicating out shortly. Let me know if it's still not working.

Thanks for fixing this issue so quickly.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#984049: enblend-enfuse: ftbfs with GCC-11

[Andreas Tille]

Control: tags -1 help

Hi,

Am Tue, Dec 14, 2021 at 06:27:47PM +0100 schrieb Heinz Repp:
> > /usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17 does 
> > not allow dynamic exception specifications
> > /usr/include/vigra/stdconvolution.hxx:796:13: error: ISO C++17 does not 
> > allow dynamic exception specifications
> 
> For those two errors I propose the first patch (c++17conf, in
> include/vigra): The original code had conditional compilation in place: all
> non Microsoft compilers got a pre-C++11 and C++17-forbidden construct, and
> Microsoft Visual C++ 2014 and up got a C++11-introduced and C++17-conformant
> construct. I removed the condition and left only the latter - this means you
> need at least GCC 4.8.1 to compile this (or MSC 2014/201).

I applied this patch in Git and it seems that it helps to build this
package.
 
> 
> Then I found another syntax error in Python code - Python 3.10 requires
> parentheses around multiple except-clauses (pythonexcept, in vigranumpy).

This patch does not apply (the ',' was replaced by 'as' which is also
valid).
 
> With those two patches it compiles, but then 22 tests fail, all with the
> same error in C++ template syntax I am not familiar with. They all fail
> because of a single discrepancy between Python and C++ representation of the
> constructArrayFromAxistags function:
> 
> > Boost.Python.ArgumentError: Python argument types in
> > vigra.vigranumpycore.constructArrayFromAxistags(type, tuple, 
> > numpy.dtype[float32], AxisTags, bool)
> > did not match C++ signature:
> > constructArrayFromAxistags(boost::python::api::object, 
> > vigra::ArrayVector >, NPY_TYPES, 
> > vigra::AxisTags, bool)

I can confirm these test issues.  Any help would be welcome.
 
Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#1003002: autopkgtest-virt-qemu: Console setup issue on armhf

[Christian Kastner]

On 2022-01-02 16:21, Christian Kastner wrote:
> It looks as if one of the necessary consoles is not set up properly on
> armhf (it worked fine for me on arm64):

Addendum: I'm now occasionally also seeing this with arm64 when using
sbuild with --chroot-mode=autopkgtest. I'd say it's 50/50 between
success and failure.

>   | host login: autopkgtest-virt-qemu: DBG: expect: found "'login prompt on 
> serial console'"
>   | autopkgtest-virt-qemu: DBG: expect: b'ok'
>   | autopkgtest-virt-qemu: DBG: setup_shell(): no default shell on hvc1 or 
> ttyS1
>   | qemu-system-arm: terminating on signal 15 from pid 1316826 
> (/usr/bin/python3)
>   | autopkgtest-virt-qemu: DBG: cleanup...
>   | : failure: The VM does not start a root shell on ttyS1 or 
> hvc1 already. The only other supported login mechanism is through --user and 
> --password on the guest ttyS0


With just autopkgtest, so far it's been 100% success with arm64 and 100%
failure with armhf.

I have no idea why success or failure isn't deterministic with
sbuild+autopkgtest; the invocation is always the same. The failure seems
to happen in check_root_shell() of /usr/bin/autopkgtest-virt-qemu.
There's a 1s timeout in there, I increased it to 10s but that didn't
change anything.

This is what I see with a successful execution:

> autopkgtest-virt-qemu: DBG: expect: b' login: '
> autopkgtest-virt-qemu: DBG: expect: found "'login prompt on serial console'"
> autopkgtest-virt-qemu: DBG: expect: b'ok'
> autopkgtest-virt-qemu: DBG: expect: found "b'ok'"
> autopkgtest-virt-qemu: DBG: setup_shell(): there already is a shell on hvc1

This is what I see when execution fails:

> autopkgtest-virt-qemu: DBG: expect: b' login: '
> autopkgtest-virt-qemu: DBG: expect: found "'login prompt on serial console'"
> autopkgtest-virt-qemu: DBG: expect: b'ok'
> autopkgtest-virt-qemu: DBG: setup_shell(): no default shell on hvc1 or ttyS1
> qemu-system-aarch64: terminating on signal 15 from pid 2939437 
> (/usr/bin/python3)
> autopkgtest-virt-qemu: DBG: cleanup...
> : failure: The VM does not start a root shell on ttyS1 or hvc1 
> already. The only other supported login mechanism is through --user and 
> --password on the guest ttyS0
> Undefined return value after 'open'

This is how I invoke sbuild with autopkgtest chroot mode:

$ sbuild --arch arm64 --dist unstable \
--bd-uninstallable-explainer apt \
--chroot-mode=autopkgtest --autopkgtest-virt-server=qemu \
--autopkgtest-virt-server-opt --overlay-dir=/tmp \
--autopkgtest-virt-server-opt --qemu-architecture=aarch64 \
--autopkgtest-virt-server-opt --ram-size=2048 \
--autopkgtest-virt-server-opt --cpus=4 \
--autopkgtest-virt-server-opt=--debug \
--autopkgtest-virt-server-opt IMAGEFILE src.dsc

Bug#1003624: softether-vpncmd: SoftEther does not like default OpenSSL CipherString

[Clint Adams]

Package: softether-vpncmd
Version: 5.01.9674+git20200806+8181039+dfsg2-2

With an unmodified /etc/ssl/openssl.cnf, the 'Network system' check fails:

% vpncmd /Tools
vpncmd command - SoftEther VPN Command Line Management Utility Developer Edition
SoftEther VPN Command Line Management Utility (vpncmd command)
Developer Edition
Version 5.01 Build 9674   (English)
Compiled 2020/12/03 09:35:09 by Unknown at Unknown
Copyright (c) all contributors on SoftEther VPN project in GitHub.
Copyright (c) Daiyuu Nobori, SoftEther Project at University of Tsukuba, and 
SoftEther Corporation.
All rights reserved.

VPN Tools has been launched. By inputting HELP, you can view a list of the 
commands that can be used.

VPN Tools>Check
Check command - Check whether SoftEther VPN Operation is Possible
---
SoftEther VPN Operation Environment Check Tool
Developer Edition

Copyright (c) SoftEther VPN Project.
All Rights Reserved.

If this operation environment check tool is run on a system and that system 
passes, it is most likely that SoftEther VPN software can operate on that 
system. This check may take a while. Please wait...

Checking 'Kernel System'... 
  Pass
Checking 'Memory Operation System'... 
  Pass
Checking 'ANSI / Unicode string processing system'... 
  Pass
Checking 'File system'... 
  Pass
Checking 'Thread processing system'... 
  Pass
Checking 'Network system'... 
Connect Failed. (0)
  Fail

Some checks failed. Please check the operation environment of this system. If 
SoftEther VPN Server / Bridge were to be executed on this system, troubles may 
occur.

The command completed successfully.

Bug#1001545: [Pkg-opencl-devel] Bug#1001545: pyopencl, build-depends on package that is no longer in testing

[Drew Parsons]

On 2022-01-12 20:00, Rebecca N. Palmer wrote:

On 12/01/2022 12:50, Drew Parsons wrote:
mesa-opencl-icd is running and passing its own tests on these arches. 
What is pyopencl doing in build and tests that's different from what 
mesa-opencl-icd itself does?


Probably that pyopencl's tests actually run OpenCL code and mesa's (at
least the ones that get run on a buildd) don't.

pyopencl is a package that uses OpenCL, so it makes sense to run its
tests via whatever OpenCL driver works on that hardware, which on the
buildds means pocl-opencl-icd.

mesa-opencl-icd is an OpenCL driver that requires a GPU, so if it has
tests that run OpenCL code, it probably doesn't run them on the
buildd.  (It might run them on a maintainer's local machine where the
right GPU is available, like beignet-opencl-icd does.)


Thanks Rebecca.

Do we know what pyopencl would do on, say, ppc64el with mesa-opencl-icd 
installed?  At the moment it not even trying. Would it fail to build? If 
it's only tests that would fail, then they could be skipped.


Another way to put the question, does OpenCL make any sense at all on 
the failing architectures like ppc64el? (and are GPUs potentially 
available for ppc64el etc, even if not available on buildds?)


What I'm wondering is whether we might want

  Build-Depends: pocl-opencl-icd [amd64 arm64 armel armhf i386 
hurd-i386], mesa-opencl-icd [!amd64 !arm64 !armel !armhf !i386 
!hurd-i386]

Bug#1003621: [Pkg-javascript-devel] Bug#1003621: emscripten: test_icu and test_pthread_icu attempt to download files from github

[Jonas Smedegaard]

Quoting Mike Gerow (2022-01-12 19:40:33)
> The test_icu and test_pthread_icu tests both attempt to download the
> file 
> .
> This leads to an error like this on builders where access to the
> network is restricted:

Thanks!

Should be fixed within few hours...

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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

signature.asc
Description: signature

Bug#1003609: readlink: invalid option -- 'b' in /lib/lsb/init-functions.d/40-systemd

[Michael Biebl]

Control: reassign -1 systemd, slony1-2-bin

I'm rather convinced this should be addressed in slony1-2-bin (by 
ideally providing native .service units).
Or at least by avoiding the use a root shell and sourcing 
/lib/lsb/init-functions, but instead using something like 
start-stop-daemon -u


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003623: ITP: angelfish -- Web browser for Plasma Mobile

[Nilesh Patra]

Package: wnpp
Severity: wishlist

Subject: ITP: angelfish -- Web browser for Plasma Mobile
Package: wnpp
Owner: Nilesh Patra 
Severity: wishlist

* Package name: angelfish
  Version : 21.06
  Upstream Author : Rinigus 
* URL : https://apps.kde.org/angelfish/
* License : GPL-2+
  Programming Lang: C++
  Description : Web browser for Plasma Mobile
 This is a webbrowser designed to
 - be used on small mobile devices,
 - integrate well in Plasma workspaces
 .
 This use QtWebEngine as backend and supports webrtc.

Remark: This package is maintained by Pirate Praveen at
   https://salsa.debian.org/debian/angelfish

Bug#1003614: sudo: New sudo asks for a password on a Docker container

[Marc Haber]

tags #1003614 moreinfo
thanks

On Wed, Jan 12, 2022 at 06:36:38PM +0200, Timo Aaltonen wrote:
> I'm using an Azure pipeline for running tests on a Docker image, and some 
> steps require running
> sudo. The new version prompts for a password while there is only root user 
> with no
> password set.

Sudo in default configuration asks for a password. Does not sound like a
bug.

Greetings
Marc

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

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Michael Biebl]

Am 12.01.22 um 19:34 schrieb Christian Weeks:

I have attached the journal from the 10 minutes prior. I was trying to mount a
CD in an external CD rom drive at the time. It seems that something went wrong
and killed systemd. I apparently didn't notice for another 10 days. /facepalm

I have the core file, if you want me to analyze it somehow, just tell me what to
do.


To get a useful backtrace, you'll probably need a chroot, where you 
install systemd 249.7-1 + dbgsym packages.

Then run gdb /lib/systemd/systemd 

Then run "bt full" to get a backtrace.





OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Christian Weeks]

I have attached the journal from the 10 minutes prior. I was trying to mount a
CD in an external CD rom drive at the time. It seems that something went wrong
and killed systemd. I apparently didn't notice for another 10 days. /facepalm

I have the core file, if you want me to analyze it somehow, just tell me what to
do.

Christian

On Wed, 2022-01-12 at 19:21 +0100, Michael Biebl wrote:
> 
> Am 12.01.22 um 18:20 schrieb Christian Weeks:
> > I don't see anything in the journal, I've had a fairly long look. I do not
> > have
> > the coredump utility installed.
> > As I have mentioned, rebooting fixed whatever caused the problem during the
> > upgrade, so I have no idea how I can help you further.
> > 
> > In looking at my running system since, I notice that systemd isn't
> > defaulting to
> > running, so I guess the problem was actually that dbus was failing to
> > activate
> > systemd properly, during the upgrade.
> 
> Once PID 1 has been frozen, you can't reactivate it. dbus tried to talk 
> to it but eventually timed out. dbus is not supposed to "start" PID1.
> 
> The only option to recover from such a scenario is to reboot 
> (forcefully) as you did.
> 
> > I have found a core file, but it's dated from 10 days ago, not today, which
> > is
> > weird. There was no activity on the computer at the time, I believe, and
> > this
> > went unnoticed, perhaps for 10 days?!
> 
> I'd say this observation is correct.
> 
> If you still have the journal, maybe attach the preceeding 10 mins 
> before the crash, i.e. all log messages from
> Jan  2 10:00:00 until  Jan  2 10:14:48

Jan 02 10:05:01 cheesypuffs CRON[1425173]: pam_unix(cron:session): session 
opened for user root(uid=0) by (uid=0)
Jan 02 10:05:01 cheesypuffs CRON[1425174]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
Jan 02 10:05:01 cheesypuffs CRON[1425173]: pam_unix(cron:session): session 
closed for user root
Jan 02 10:06:59 cheesypuffs NetworkManager[958]:   [1641136019.2397] 
device (wlp41s0): set-hw-addr: set MAC address to 36:F4:36:8B:48:E4 (scanning)
Jan 02 10:06:59 cheesypuffs NetworkManager[958]:   [1641136019.2890] 
device (wlp41s0): supplicant interface state: inactive -> disconnected
Jan 02 10:06:59 cheesypuffs NetworkManager[958]:   [1641136019.2890] 
device (p2p-dev-wlp41s0): supplicant management interface state: inactive -> 
disconnected
Jan 02 10:06:59 cheesypuffs NetworkManager[958]:   [1641136019.2941] 
device (wlp41s0): supplicant interface state: disconnected -> inactive
Jan 02 10:06:59 cheesypuffs NetworkManager[958]:   [1641136019.2941] 
device (p2p-dev-wlp41s0): supplicant management interface state: disconnected 
-> inactive
Jan 02 10:07:41 cheesypuffs kernel: usb 1-2: USB disconnect, device number 3
Jan 02 10:07:41 cheesypuffs kernel: usb 1-2.4: USB disconnect, device number 9
Jan 02 10:07:41 cheesypuffs kernel: usb 1-2.4.4: USB disconnect, device number 
12
Jan 02 10:07:41 cheesypuffs kernel: usb 1-2.4.4.2: USB disconnect, device 
number 13
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2: USB disconnect, device number 3
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2.4: USB disconnect, device number 4
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2.4.4: USB disconnect, device number 5
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2: new SuperSpeed USB device number 6 
using xhci_hcd
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2: New USB device found, 
idVendor=2109, idProduct=0817, bcdDevice= 3.64
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2: New USB device strings: Mfr=1, 
Product=2, SerialNumber=0
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2: Product: USB3.0 Hub
Jan 02 10:07:42 cheesypuffs kernel: usb 2-2: Manufacturer: VIA Labs, Inc.
Jan 02 10:07:42 cheesypuffs kernel: hub 2-2:1.0: USB hub found
Jan 02 10:07:42 cheesypuffs kernel: hub 2-2:1.0: 4 ports detected
Jan 02 10:07:42 cheesypuffs upowerd[1429]: treating change event as add on 
/sys/devices/pci:00/:00:01.2/:20:00.0/:21:08.0/:2a:00.1/usb2/2-2
Jan 02 10:07:43 cheesypuffs kernel: usb 1-2: new high-speed USB device number 
14 using xhci_hcd
Jan 02 10:07:43 cheesypuffs kernel: usb 1-2: New USB device found, 
idVendor=2109, idProduct=2817, bcdDevice= 3.64
Jan 02 10:07:43 cheesypuffs kernel: usb 1-2: New USB device strings: Mfr=1, 
Product=2, SerialNumber=0
Jan 02 10:07:43 cheesypuffs kernel: usb 1-2: Product: USB2.0 Hub
Jan 02 10:07:43 cheesypuffs kernel: usb 1-2: Manufacturer: VIA Labs, Inc.
Jan 02 10:07:43 cheesypuffs kernel: hub 1-2:1.0: USB hub found
Jan 02 10:07:43 cheesypuffs kernel: hub 1-2:1.0: 4 ports detected
Jan 02 10:07:43 cheesypuffs upowerd[1429]: treating change event as add on 
/sys/devices/pci:00/:00:01.2/:20:00.0/:21:08.0/:2a:00.1/usb1/1-2
Jan 02 10:07:43 cheesypuffs kernel: usb 2-2.4: new SuperSpeed USB device number 
7 using xhci_hcd
Jan 02 10:07:43 cheesypuffs kernel: usb 2-2.4: New USB device found, 
idVendor=2109, idProduct=0817, bcdDevice=90.23
Jan 02 10:07:43 cheesypuffs kernel: usb 2-2.4: New USB device strings

Bug#1003620: realmd: don't explicitly enable services

[Andreas Hasenack]

Package: realmd
Version: 0.17.0-1
Severity: normal

Dear Maintainer,

in Debian and Ubuntu, sssd uses socket activation to start other
daemons as needed.

When realmd is used to join an Active Directory domain, by default
sssd is used. realmd will configure sssd with the following:
[sssd]
services = nss, pam

This services line tells sssd to also start the services for nss and
pam, but these are socket activated:
/lib/systemd/system/sssd-nss.socket
/lib/systemd/system/sssd-pam-priv.socket
/lib/systemd/system/sssd-pam.socket

When realmd finishes the join, and restarts sssd, we get these
warnings in the logs.
For NSS:
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2445]: [sssd] [main] (0x0070):
Misconfiguration found for the nss responder.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2445]: The nss responder has
been configured to be socket-activated but it's still mentioned in the
services' line in /etc/sssd/sssd.conf.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2445]: Please, consider either
adjusting your services' line in /etc/sssd/sssd.conf or disabling the
nss's socket by calling:
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2445]: "systemctl disable
sssd-nss.socket"
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-nss.socket: Control
process exited, code=exited, status=17/n/a
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-nss.socket: Failed with
result 'exit-code'.
Jan 12 18:08:19 sid-realmd systemd[1]: Failed to listen on SSSD NSS
Service responder socket.

For PAM:
Jan 12 18:08:19 sid-realmd systemd[1]: Starting SSSD PAM Service
responder socket...
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2446]: [sssd] [main] (0x0070):
Misconfiguration found for the pam responder.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2446]: The pam responder has
been configured to be socket-activated but it's still mentioned in the
services' line in /etc/sssd/sssd.conf.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2446]: Please, consider either
adjusting your services' line in /etc/sssd/sssd.conf or disabling the
pam's socket by calling:
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2446]: "systemctl disable
sssd-pam.socket"
Jan 12 18:08:19 sid-realmd systemd[1]: Starting SSSD SSH Service
responder socket...
Jan 12 18:08:19 sid-realmd systemd[1]: Starting SSSD Sudo Service
responder socket...
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-pam-priv.socket: Control
process exited, code=exited, status=17/n/a
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-pam-priv.socket: Failed
with result 'exit-code'.
Jan 12 18:08:19 sid-realmd systemd[1]: Failed to listen on SSSD PAM
Service responder private socket.
Jan 12 18:08:19 sid-realmd systemd[1]: Dependency failed for SSSD PAM
Service responder socket.
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-pam.socket: Job
sssd-pam.socket/start failed with result 'dependency'.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2449]: [sssd] [main] (0x0070):
Misconfiguration found for the pam responder.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2449]: The pam responder has
been configured to be socket-activated but it's still mentioned in the
services' line in /etc/sssd/sssd.conf.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2449]: Please, consider either
adjusting your services' line in /etc/sssd/sssd.conf or disabling the
pam's socket by calling:
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-pam.socket: Killing
process 2449 (sssd_check_sock) with signal SIGKILL.
Jan 12 18:08:19 sid-realmd
sssd_check_socket_activated_responders[2449]: "systemctl disable
sssd-pam.socket"
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-pam.socket: Control
process exited, code=exited, status=17/n/a
Jan 12 18:08:19 sid-realmd systemd[1]: sssd-pam.socket: Failed with
result 'exit-code'.
Jan 12 18:08:19 sid-realmd systemd[1]: Closed SSSD PAM Service responder socket.

There are not fatal, and the join process succeeds:
root@sid-realmd:~# kinit Administrator
Password for administra...@internal.example.fake:

root@sid-realmd:~# realm join -v internal.example.fake
 * Resolving: _ldap._tcp.internal.example.fake
 * Performing LDAP DSE lookup on: 10.0.16.5
 * Successfully discovered: internal.example.fake
 (...)
 * Checking host/SID-REALMD
 *Added host/SID-REALMD
 * Discovered which keytab salt to use
 * Added the entries to the keytab: SID-REALMD$@INTERNAL.EXAMPLE.FAKE:
FILE:/etc/krb5.keytab
 * Added the entries to the keytab:
host/sid-rea...@internal.example.fake: FILE:/etc/krb5.keytab
 * Added the entries to the keytab:
RestrictedKrbHost/sid-rea...@internal.example.fake:
FILE:/etc/krb5.keytab
 ! Failed to update Kerberos configuration, not fatal, please check
manually: Setting attribute standard::type not supported
 * /usr/sbin/update-rc.d sssd enable
 * /usr/sbin/service sssd restart
 * Successfully enrolled 

Bug#1003609: readlink: invalid option -- 'b' in /lib/lsb/init-functions.d/40-systemd

[Michael Biebl]

Am 12.01.22 um 18:31 schrieb Peter Palfrader:

On Wed, 12 Jan 2022, Michael Biebl wrote:


Am 12.01.22 um 16:04 schrieb Peter Palfrader:

/lib/lsb/init-functions.d/40-systemd calls
readlink -f "$executable"
which causes warnings if an executable starts with -, like in "-bash" when
/lib/lsb/init-functions is sourced from a login shell.

] root@yukon:~# . /lib/lsb/init-functions
] readlink: invalid option -- 'b'
] Try 'readlink --help' for more information.
] root@yukon:~#

This happens for instance with the slony init script:

| adns002:~# grep 'init-functions ' /etc/init.d/slony1
| su -c ". /lib/lsb/init-functions ; umask 027 ; start_daemon -p $(pidfile $1) $DAEMON 
-f $(conffile $1) -p $(pidfile $1) >>$(logfile $1) 2>&1 

Oh my, not the prettiest way to start a daemon.
Christoph, maybe this is actually better addressed on the slony1-2 side.


I completely agree that it should /also/ be addressed there, but
nevertheless, init-functions should be sourceable from login shells.


I see it as a helper library for init scripts, not so much a general 
purpose shell library that can be sourced from arbitrary contexts. It 
wasn't really written with that in mind.
To this day, I wasn't actually aware that anyone was using 
/lib/lsb/init-functions outside of an init script context. I don't think 
anyone is actually testing that it works for that.



Regards,
Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Michael Biebl]

Am 12.01.22 um 18:20 schrieb Christian Weeks:

I don't see anything in the journal, I've had a fairly long look. I do not have
the coredump utility installed.
As I have mentioned, rebooting fixed whatever caused the problem during the
upgrade, so I have no idea how I can help you further.

In looking at my running system since, I notice that systemd isn't defaulting to
running, so I guess the problem was actually that dbus was failing to activate
systemd properly, during the upgrade.


Once PID 1 has been frozen, you can't reactivate it. dbus tried to talk 
to it but eventually timed out. dbus is not supposed to "start" PID1.


The only option to recover from such a scenario is to reboot 
(forcefully) as you did.



I have found a core file, but it's dated from 10 days ago, not today, which is
weird. There was no activity on the computer at the time, I believe, and this
went unnoticed, perhaps for 10 days?!


I'd say this observation is correct.

If you still have the journal, maybe attach the preceeding 10 mins 
before the crash, i.e. all log messages from

Jan  2 10:00:00 until  Jan  2 10:14:48


OpenPGP_signature
Description: OpenPGP digital signature

Bug#942190: closed by Brian Potkin (Re: Bug#942190: cups: Memory leak for WIFI enabled printer.)

[Brian Potkin]

On Tue 11 Jan 2022 at 02:06:22 +0100, Mladen Mijatov wrote:

> I've been notified in the meantime by a developer on the project that
> my particular printer doesn't require HP's drivers and that open
> source ones will suffice. After removing HP's drivers and relying on
> open source drivers all of my issues with this printer went away,
> including memory leaks on CUPS. 

Good to know.

> Sorry for not replying, email must have gotten lost.

Not to worry. Thank you again for your report and for engaging with
the issue.

Regards,

Brian.

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Michael Biebl]

Control: found -1 249.7-1
Control: severity -1 important

Am 12.01.22 um 18:20 schrieb Christian Weeks:

I don't see anything in the journal, I've had a fairly long look. I do not have
the coredump utility installed.
As I have mentioned, rebooting fixed whatever caused the problem during the
upgrade, so I have no idea how I can help you further.

In looking at my running system since, I notice that systemd isn't defaulting to
running, so I guess the problem was actually that dbus was failing to activate
systemd properly, during the upgrade.

I have found a core file, but it's dated from 10 days ago, not today, which is
weird. There was no activity on the computer at the time, I believe, and this
went unnoticed, perhaps for 10 days?!


As said, systemd freezes execution when it crashes.
If PID 1 actually crashed, the kernel would panic and you'd notice :-)


Jan  2 10:14:48 cheesypuffs kernel: [336844.954825] systemd[1]: segfault at 18
ip 55bd29c926ea sp 7ffdcd0c56c8 error 4 in systemd[55bd29c38000+d9000]


ls -l /core
-rw--- 1 root root 22482944 Jan  2 10:14 /core

I can share this core file with you if you wish (how?), though perhaps it's not
so related to the upgrade anymore?


Given the timestamps match, it's pretty certain, that the core file 
belongs to the segfault.
It also shows that PID 1 crashing is not actually affecting the running 
services. As long as you don't interact with systemd (e.g. via 
systemctl), your system should continue to run fine.

I'm thus downgrading the severity.
As it is not actually related to the upgrade, I'm marking it as found in 
249.7-1.


You can attach the core file to the bug report (gzipped) or mail it to 
me directly. I will try to see if a backtrace reveals something.


Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003615: ITP: php-bacon-bacon-qr-code -- QR code generator for PHP

[Guilhem Moulin]

On Wed, 12 Jan 2022 at 18:10:18 +0100, Guilhem Moulin wrote:
> * Package name: php-bacon-bacon-qr-code
>  Version : 2.0.4
>  Upstream Author : Ben Scholzen 'DASPRiD' 
> * URL : https://github.com/Bacon/BaconQrCode
> * License : BSD-2-Clause
>  Programming Lang: PHP
>  Description : QR code generator for PHP

Gah I mixed things up, that one is already in Debian…  That's the old
library which was missing.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#884648: mate-panel occasionally crashes with segfault

[yg2709]

Package: mate-panel
Version: 1.26.1-2
Followup-For: Bug #884648
X-Debbugs-Cc: yg2...@hotmail.com

Dear Maintainer,

>From debian testing, after upgrading from 1.24.1-1+b1 to 1.26.1-2, I randomly 
>get the message in the /var/log/messages file saying that wnck-applet segfault 
>error in libgdk-3.so.0.2404.27:

$  sudo grep -e '^2022-01-12' /var/log/messages | grep -e 'wnck-applet' -e 
'Code:'

2022-01-12T12:35:13.273151+01:00 wnck-applet[1561]: Negative content width -1 
(allocation 1, extents 1x1) while allocating gadget (node button, owner 
WnckButton)
2022-01-12T12:35:13.273796+01:00 wnck-applet[1561]: Negative content width -1 
(allocation 1, extents 1x1) while allocating gadget (node button, owner 
WnckButton)

2022-01-12T12:52:21.081341+01:00 wnck-applet[1561]: XID collision, trouble ahead
2022-01-12T12:52:58.563991+01:00 wnck-applet[1561]: XID collision, trouble ahead
2022-01-12T12:55:38.871346+01:00 wnck-applet[1561]: XID collision, trouble ahead

2022-01-12T12:59:35.492112+01:00 kernel: [ 1599.687299] wnck-applet[1561]: 
segfault at 44 ip 7ff4e0586510 sp 7ffe7f09c2f0 error 4 in 
libgdk-3.so.0.2404.27[7ff4e0552000+7f000]
2022-01-12T12:59:35.492129+01:00 kernel: [ 1599.687313] Code: 8b bc 24 b8 00 00 
00 e8 9e cc fc ff 48 83 7c 24 48 00 74 28 4d 85 e4 0f 84 81 00 00 00 f2 0f 10 
84 24 a0 00 00 00 66 0f ef c9  0f 2a 4b 44 f2 0f 5e c1 48 8b 44 24 48 f2 0f 
11 00 48 83 7c 24

(20220112 125950 window message and "[Reload]" selected, three times)

2022-01-12T12:59:56.627920+01:00 wnck-applet[2695]: gtk_widget_queue_draw_area: 
assertion 'width >= 0' failed
2022-01-12T12:59:56.628034+01:00 wnck-applet[2695]: gtk_widget_queue_draw_area: 
assertion 'width >= 0' failed
2022-01-12T12:59:56.628105+01:00 wnck-applet[2695]: gtk_widget_queue_draw_area: 
assertion 'width >= 0' failed


$ sudo apt-file search wnck-applet
mate-panel: /usr/lib/mate-panel/wnck-applet


Thank you very much.


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-2
ii  libatk1.0-0  2.36.0-3
ii  libc62.33-1
ii  libcairo21.16.0-5
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.2-1
ii  libgtk-3-0   3.24.31-1
ii  libgtk-layer-shell0  0.6.0-1
ii  libice6  2:1.0.10-1
ii  libmate-desktop-2-17 1.26.0-1
ii  libmate-menu21.26.0-1
ii  libmate-panel-applet-4-1 1.26.1-2
ii  libmateweather1  1.26.0-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  librda0  0.0.5-1.1
ii  libsm6   2:1.2.3-1
ii  libwayland-client0   1.19.0-2+b1
ii  libwnck-3-0  40.0-2
ii  libx11-6 2:1.7.2-2+b1
ii  libxrandr2   2:1.5.2-1
ii  mate-desktop 1.26.0-1
ii  mate-menus   1.26.0-1
ii  mate-panel-common1.26.1-2
ii  mate-polkit  1.26.0-1

mate-panel recommends no packages.

mate-panel suggests no packages.

-- debconf-show failed

Bug#1003583: e2fsprogs and libext2fs2 in bullseye-backports missing dependency

[Theodore Ts'o]

found 1003583 e2fsprogs/1.46.5-2~bpo11+1
notfound 1003583 e2fsprogs/1.46.2-2
thanks

> Dear Maintainer,
> 
>* e2fsprogs and libext2fs2 version 1.46.5-2~bpo11+1 are in the
> bullseye-backports repository
>* both depend on libc6 (>= 2.33) for amd64
>* libc6 versions 2.33 and higher do not exist in bullseye or
> bullseye-backports repositories
>* Result:
> cannot upgrade to the version of either that are in the backports

Thanks for the bug report.  Apparently dgit let me down, in that "dgit
gbp-build" failed to use the proper build chroot, while "gbp
buildpackage" *does* use the correct build chroot.

I had tested first using "gbp buildpackage", and then got taken
surprised when "dgit --quilt=nofix gbp-build" did *not* use the proper
schroot.  At a guess, dgit is somehow invoking gbp buildpackage in a
way that causes the debian/gbp.conf is ignored.

In any case, no matter how it happened, the version of e2fsprogs that
dgit uploaded to bullseye-backport was built without a chroot, using
my Debian testing environment.  I've tested this and it's quite
reproducible.   

I've rebuilt using "gbp buildpackage" directly, which does DTRT, so
I'll reupload without uding dgit, and that should fix the problem.
When have a free day or two, I'll try figure out why dgit surprised
the heck out of me, but until then I'll stop using dgit as an
unreliable/incrutable tool.  :-(

   - Ted

Bug#998803: marked as pending in busybox

[Christoph Anton Mitterer]

On Wed, 2022-01-12 at 16:55 +, Chris Boot wrote:
> I was going to vimdiff the configs 
> to see what we might need to change and harmonise between them.

That sounds like a good idea... and I guess it would be reasonable to
keep everything identical, and for the cases where this is really not
desired, properly document why exactly this isn't done, so that in the
future one would know why.

Thanks,
Chris.

Bug#1003573: setuptools: diff for NMU version 59.6.0-1.1

[Stefano Rivera]

Dear maintainer,

Let's try that again...

I've prepared an NMU for setuptools (versioned as 59.6.0-1.1). The diff
is attached to this message.

Regards.

SR
diff -Nru setuptools-59.6.0/debian/changelog setuptools-59.6.0/debian/changelog
--- setuptools-59.6.0/debian/changelog	2021-12-15 21:16:07.0 -0400
+++ setuptools-59.6.0/debian/changelog	2022-01-12 13:21:21.0 -0400
@@ -1,3 +1,10 @@
+setuptools (59.6.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build a python3-setuptools-whl package. Closes: #1003573.
+
+ -- Stefano Rivera   Wed, 12 Jan 2022 13:21:21 -0400
+
 setuptools (59.6.0-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru setuptools-59.6.0/debian/control setuptools-59.6.0/debian/control
--- setuptools-59.6.0/debian/control	2020-12-23 08:13:42.0 -0400
+++ setuptools-59.6.0/debian/control	2022-01-12 13:21:21.0 -0400
@@ -48,6 +48,17 @@
 Description: Python3 Distutils Enhancements
  Extensions to the python-distutils for large or complex distributions.
 
+Package: python3-setuptools-whl
+Architecture: all
+Depends: ${misc:Depends}
+Breaks: python-pip-whl (<< 21.3.1+dfsg-2~)
+Replaces: python-pip-whl (<< 21.3.1+dfsg-2~)
+Description: Python Distutils Enhancements (wheel package)
+ Extensions to the python-distutils for large or complex distributions.
+ .
+ This is the support package for the PEP 427 wheel version of the package,
+ required for using setuptools inside a virtual environment.
+
 #Package: pypy-pkg-resources
 #Suggests: pypy-setuptools
 #Architecture: all
@@ -72,11 +83,3 @@
 #Suggests: python-setuptools-doc
 #Description: PyPy Distutils Enhancements
 # Extensions to the python-distutils for large or complex distributions.
-
-#Package: python-setuptools-whl
-#Architecture: all
-#Depends: ${misc:Depends}
-#Description: Python Distutils Enhancements (wheel package)
-# Extensions to the python-distutils for large or complex distributions.
-# .
-# This package provides setuptools in PEP 427 wheel format.
diff -Nru setuptools-59.6.0/debian/rules setuptools-59.6.0/debian/rules
--- setuptools-59.6.0/debian/rules	2021-06-29 06:55:24.0 -0400
+++ setuptools-59.6.0/debian/rules	2022-01-12 13:21:21.0 -0400
@@ -10,9 +10,9 @@
 
 	PYTHONPATH=$(CURDIR) $(MAKE) -C docs html
 
-#	mkdir -p debian/python-setuptools-whl/usr/share/python-wheels
-#	python3 setup.py bdist_wheel --universal \
-#	-d debian/python-setuptools-whl/usr/share/python-wheels
+	mkdir -p debian/python3-setuptools-whl/usr/share/python-wheels
+	python3 setup.py bdist_wheel \
+	-d debian/python3-setuptools-whl/usr/share/python-wheels
 
 	# dh_pypy from dh-python < 1.20150705-1 falls over requires.txt
 	# and our requires.txt aren't useful

Bug#1003591: lxc : the lxc-top command is missing in debian package

[Antonio Terceiro]

Control: tag -1 + pending

On Wed, Jan 12, 2022 at 10:19:15AM +0100, gerbier wrote:
> Package: lxc
> Version: 1:4.0.6-2
> Severity: normal
> X-Debbugs-Cc: eric.gerb...@free.fr
> 
> Dear Maintainer,
> 
> the lxc-top command is an important tool for lxc containers. It is
> available in ubuntu/fedora/mageia/ packages, but not in debian lxc package

This is fixed in git by commit b24eebc


signature.asc
Description: PGP signature

Bug#1003609: readlink: invalid option -- 'b' in /lib/lsb/init-functions.d/40-systemd

[Peter Palfrader]

On Wed, 12 Jan 2022, Michael Biebl wrote:

> Am 12.01.22 um 16:04 schrieb Peter Palfrader:
> > /lib/lsb/init-functions.d/40-systemd calls
> >readlink -f "$executable"
> > which causes warnings if an executable starts with -, like in "-bash" when
> > /lib/lsb/init-functions is sourced from a login shell.
> > 
> > ] root@yukon:~# . /lib/lsb/init-functions
> > ] readlink: invalid option -- 'b'
> > ] Try 'readlink --help' for more information.
> > ] root@yukon:~#
> > 
> > This happens for instance with the slony init script:
> > 
> > | adns002:~# grep 'init-functions ' /etc/init.d/slony1
> > | su -c ". /lib/lsb/init-functions ; umask 027 ; 
> > start_daemon -p $(pidfile $1) $DAEMON -f $(conffile $1) -p $(pidfile $1) 
> > >>$(logfile $1) 2>&1  
> Oh my, not the prettiest way to start a daemon.
> Christoph, maybe this is actually better addressed on the slony1-2 side.

I completely agree that it should /also/ be addressed there, but
nevertheless, init-functions should be sourceable from login shells.

Cheers!

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#1003618: python-setuptools: diff for NMU version 44.1.1-1.1

[Stefano Rivera]

Package: python-setuptools
Version: 44.1.1-1
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for python-setuptools (versioned as 44.1.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

SR
diff -Nru python-setuptools-44.1.1/debian/changelog python-setuptools-44.1.1/debian/changelog
--- python-setuptools-44.1.1/debian/changelog	2020-08-02 08:20:55.0 -0400
+++ python-setuptools-44.1.1/debian/changelog	2022-01-12 13:33:15.0 -0400
@@ -1,3 +1,12 @@
+python-setuptools (44.1.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build a python2-setuptools-whl package. Closes: #1003573.
+  * Patch: Handle the removal of bdist_wininst from distutils.
+Closes: #1002444
+
+ -- Stefano Rivera   Wed, 12 Jan 2022 13:33:15 -0400
+
 python-setuptools (44.1.1-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru python-setuptools-44.1.1/debian/control python-setuptools-44.1.1/debian/control
--- python-setuptools-44.1.1/debian/control	2020-08-02 08:20:55.0 -0400
+++ python-setuptools-44.1.1/debian/control	2022-01-12 13:33:15.0 -0400
@@ -65,10 +65,13 @@
 Description: PyPy Distutils Enhancements
  Extensions to the python-distutils for large or complex distributions.
 
-#Package: python-setuptools-whl
-#Architecture: all
-#Depends: ${misc:Depends}
-#Description: Python Distutils Enhancements (wheel package)
-# Extensions to the python-distutils for large or complex distributions.
-# .
-# This package provides setuptools in PEP 427 wheel format.
+Package: python2-setuptools-whl
+Architecture: all
+Depends: ${misc:Depends}
+Breaks: python-pip-whl (<< 21)
+Replaces: python-pip-whl (<< 21)
+Description: Python Distutils Enhancements (python 2.7 wheel package)
+ Extensions to the python-distutils for large or complex distributions.
+ .
+ This is the support package for the PEP 427 wheel version of the package,
+ required for using setuptools inside a Python 2.7 virtual environment.
diff -Nru python-setuptools-44.1.1/debian/patches/removed-bdist_wininst.patch python-setuptools-44.1.1/debian/patches/removed-bdist_wininst.patch
--- python-setuptools-44.1.1/debian/patches/removed-bdist_wininst.patch	1969-12-31 20:00:00.0 -0400
+++ python-setuptools-44.1.1/debian/patches/removed-bdist_wininst.patch	2022-01-12 13:33:15.0 -0400
@@ -0,0 +1,28 @@
+From: "Jason R. Coombs" 
+Date: Tue, 11 Jan 2022 18:04:05 -0400
+Subject: Fix install_scripts() if bdist_wininst is missing
+
+Bug-Debian: https://bugs.debian.org/1002444
+Origin: upstream, https://github.com/pypa/setuptools/pull/1986
+---
+ setuptools/command/install_scripts.py | 7 +--
+ 1 file changed, 5 insertions(+), 2 deletions(-)
+
+diff --git a/setuptools/command/install_scripts.py b/setuptools/command/install_scripts.py
+index 1623427..8c9a15e 100644
+--- a/setuptools/command/install_scripts.py
 b/setuptools/command/install_scripts.py
+@@ -32,8 +32,11 @@ class install_scripts(orig.install_scripts):
+ )
+ bs_cmd = self.get_finalized_command('build_scripts')
+ exec_param = getattr(bs_cmd, 'executable', None)
+-bw_cmd = self.get_finalized_command("bdist_wininst")
+-is_wininst = getattr(bw_cmd, '_is_running', False)
++try:
++bw_cmd = self.get_finalized_command("bdist_wininst")
++is_wininst = getattr(bw_cmd, '_is_running', False)
++except ImportError:
++is_wininst = False
+ writer = ei.ScriptWriter
+ if is_wininst:
+ exec_param = "python.exe"
diff -Nru python-setuptools-44.1.1/debian/patches/series python-setuptools-44.1.1/debian/patches/series
--- python-setuptools-44.1.1/debian/patches/series	2018-08-31 06:14:53.0 -0400
+++ python-setuptools-44.1.1/debian/patches/series	2022-01-12 13:33:15.0 -0400
@@ -7,3 +7,4 @@
 reproducible.diff
 sorted-requires.diff
 PKG-INFO-output-reproducible.diff
+removed-bdist_wininst.patch
diff -Nru python-setuptools-44.1.1/debian/rules python-setuptools-44.1.1/debian/rules
--- python-setuptools-44.1.1/debian/rules	2020-02-25 08:47:07.0 -0400
+++ python-setuptools-44.1.1/debian/rules	2022-01-12 13:33:15.0 -0400
@@ -16,9 +16,9 @@
 
 	PYTHONPATH=$(CURDIR) $(MAKE) -C docs html
 
-#	mkdir -p debian/python-setuptools-whl/usr/share/python-wheels
-#	python3 setup.py bdist_wheel --universal \
-#	-d debian/python-setuptools-whl/usr/share/python-wheels
+	mkdir -p debian/python2-setuptools-whl/usr/share/python-wheels
+	python3 setup.py bdist_wheel --universal \
+	-d debian/python2-setuptools-whl/usr/share/python-wheels
 
 	# dh_pypy from dh-python < 1.20150705-1 falls over requires.txt
 	# and our requires.txt aren't useful

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Vincent-Xavier JUMEL]

Package: libpam-runtime
Version: 1.4.0-11
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
   with 
   ```
   auth[success=0 default=ignore]  pam_ssh.so use_first_pass
   ```
   * Login then failed
   * I've modified "success=0" -> "success=1" to get back the login.



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500, 
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'buster-fasttrack'), 
(100, 'buster-backports'), (100, 'bullseye-fasttrack'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libpam-runtime depends on:
ii  debconf [debconf-2.0]  1.5.79
ii  libpam-modules 1.4.0-11

libpam-runtime recommends no packages.

libpam-runtime suggests no packages.

-- debconf information:
  libpam-runtime/conflicts:
  libpam-runtime/override: false
* libpam-runtime/profiles: passwdqc, unix, ssh-pwd, tmpdir, systemd
  libpam-runtime/no_profiles_chosen:
  libpam-runtime/title:

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org

Bug#1003573: setuptools: diff for NMU version 58.2.0-1.1

[Stefano Rivera]

Control: tags 1003573 + patch

Dear maintainer,

As discussed on IRC, I've prepared an NMU for setuptools (versioned as
58.2.0-1.1). The diff is attached to this message.

Regards.

SR
diff -Nru setuptools-58.2.0/debian/changelog setuptools-58.2.0/debian/changelog
--- setuptools-58.2.0/debian/changelog	2021-10-11 07:44:59.0 -0400
+++ setuptools-58.2.0/debian/changelog	2022-01-12 13:21:21.0 -0400
@@ -1,3 +1,10 @@
+setuptools (58.2.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build a python3-setuptools-whl package. Closes: #1003573.
+
+ -- Stefano Rivera   Wed, 12 Jan 2022 13:21:21 -0400
+
 setuptools (58.2.0-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru setuptools-58.2.0/debian/control setuptools-58.2.0/debian/control
--- setuptools-58.2.0/debian/control	2020-12-23 08:13:42.0 -0400
+++ setuptools-58.2.0/debian/control	2022-01-12 13:21:21.0 -0400
@@ -48,6 +48,17 @@
 Description: Python3 Distutils Enhancements
  Extensions to the python-distutils for large or complex distributions.
 
+Package: python3-setuptools-whl
+Architecture: all
+Depends: ${misc:Depends}
+Breaks: python-pip-whl (<< 21.3.1+dfsg-2~)
+Replaces: python-pip-whl (<< 21.3.1+dfsg-2~)
+Description: Python Distutils Enhancements (wheel package)
+ Extensions to the python-distutils for large or complex distributions.
+ .
+ This is the support package for the PEP 427 wheel version of the package,
+ required for using setuptools inside a virtual environment.
+
 #Package: pypy-pkg-resources
 #Suggests: pypy-setuptools
 #Architecture: all
@@ -72,11 +83,3 @@
 #Suggests: python-setuptools-doc
 #Description: PyPy Distutils Enhancements
 # Extensions to the python-distutils for large or complex distributions.
-
-#Package: python-setuptools-whl
-#Architecture: all
-#Depends: ${misc:Depends}
-#Description: Python Distutils Enhancements (wheel package)
-# Extensions to the python-distutils for large or complex distributions.
-# .
-# This package provides setuptools in PEP 427 wheel format.
diff -Nru setuptools-58.2.0/debian/rules setuptools-58.2.0/debian/rules
--- setuptools-58.2.0/debian/rules	2021-06-29 06:55:24.0 -0400
+++ setuptools-58.2.0/debian/rules	2022-01-12 13:21:21.0 -0400
@@ -10,9 +10,9 @@
 
 	PYTHONPATH=$(CURDIR) $(MAKE) -C docs html
 
-#	mkdir -p debian/python-setuptools-whl/usr/share/python-wheels
-#	python3 setup.py bdist_wheel --universal \
-#	-d debian/python-setuptools-whl/usr/share/python-wheels
+	mkdir -p debian/python3-setuptools-whl/usr/share/python-wheels
+	python3 setup.py bdist_wheel \
+	-d debian/python3-setuptools-whl/usr/share/python-wheels
 
 	# dh_pypy from dh-python < 1.20150705-1 falls over requires.txt
 	# and our requires.txt aren't useful

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Christian Weeks]

I don't see anything in the journal, I've had a fairly long look. I do not have
the coredump utility installed.
As I have mentioned, rebooting fixed whatever caused the problem during the
upgrade, so I have no idea how I can help you further.

In looking at my running system since, I notice that systemd isn't defaulting to
running, so I guess the problem was actually that dbus was failing to activate
systemd properly, during the upgrade.

I have found a core file, but it's dated from 10 days ago, not today, which is
weird. There was no activity on the computer at the time, I believe, and this
went unnoticed, perhaps for 10 days?!

Jan  2 10:14:48 cheesypuffs kernel: [336844.954825] systemd[1]: segfault at 18
ip 55bd29c926ea sp 7ffdcd0c56c8 error 4 in systemd[55bd29c38000+d9000]


ls -l /core
-rw--- 1 root root 22482944 Jan  2 10:14 /core

I can share this core file with you if you wish (how?), though perhaps it's not
so related to the upgrade anymore?

Christian
On Wed, 2022-01-12 at 18:01 +0100, Michael Biebl wrote:
> Control: tags -1 + moreinfo
> 
> Hello,
> 
> systemd freezes execution when it crashes (you should see a 
> corresponding log message in the journal).
> 
> For this bug report to be actionable, we will need at the very least a 
> backtrace of the crash.
> In case you had systemd-coredump installed, coredumpctl should show you.
> Or maybe you still have a core file in /.
> 
> 
> Regards,
> Michael
> 

Bug#1003609: readlink: invalid option -- 'b' in /lib/lsb/init-functions.d/40-systemd

[Michael Biebl]

Am 12.01.22 um 16:04 schrieb Peter Palfrader:

/lib/lsb/init-functions.d/40-systemd calls
   readlink -f "$executable"
which causes warnings if an executable starts with -, like in "-bash" when
/lib/lsb/init-functions is sourced from a login shell.

] root@yukon:~# . /lib/lsb/init-functions
] readlink: invalid option -- 'b'
] Try 'readlink --help' for more information.
] root@yukon:~#

This happens for instance with the slony init script:

| adns002:~# grep 'init-functions ' /etc/init.d/slony1
| su -c ". /lib/lsb/init-functions ; umask 027 ; start_daemon -p $(pidfile $1) $DAEMON 
-f $(conffile $1) -p $(pidfile $1) >>$(logfile $1) 2>&1 

Oh my, not the prettiest way to start a daemon.
Christoph, maybe this is actually better addressed on the slony1-2 side.

Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003616: tpm2-abrmd: systemd complains about syslog

[Dave Love]

Package: tpm2-abrmd
Version: 2.3.3-1+b2
Severity: normal
X-Debbugs-Cc: none, Dave Love 

I see this noise in my logs which might be worth cleaning up:

  /lib/systemd/system/tpm2-abrmd.service:12: Standard output type syslog
  is obsolete, automatically updating to journal. Please update your
  unit file, and consider removing the setting altogether.

-- 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.10.0-9-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tpm2-abrmd depends on:
ii  init-system-helpers  1.60
ii  libc62.31-13+deb11u2
ii  libglib2.0-0 2.66.8-1
ii  libtss2-mu0  3.0.3-2
ii  libtss2-rc0  3.0.3-2
ii  libtss2-sys1 3.0.3-2
ii  libtss2-tctildr0 3.0.3-2

tpm2-abrmd recommends no packages.

tpm2-abrmd suggests no packages.

-- no debconf information

Bug#1003615: ITP: php-bacon-bacon-qr-code -- QR code generator for PHP

[Guilhem Moulin]

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

* Package name: php-bacon-bacon-qr-code
  Version : 2.0.4
  Upstream Author : Ben Scholzen 'DASPRiD' 
* URL : https://github.com/Bacon/BaconQrCode
* License : BSD-2-Clause
  Programming Lang: PHP
  Description : QR code generator for PHP

 BaconQrCode is a port of QR code portion of the ZXing library. It
 currently only features the encoder part, but could later receive the
 decoder part as well.

 BaconQrCode comes with multiple back ends for rendering images.
 Currently included are the following:

  * ImagickImageBackEnd: renders raster images using the Imagick library
  * SvgImageBackEnd: renders SVG files using XMLWriter
  * EpsImageBackEnd: renders EPS files

This package is a new dependency of Roundcube v1.6.  It will be
maintained in the Debian PHP PEAR Maintainers team.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#998803: marked as pending in busybox

[Chris Boot]

On 12/01/2022 16:40, Christoph Anton Mitterer wrote:

Hey Chris.

Shouldn't this also done in at least the config for the static
busybox... and likely also the udeb?
(I can of course make a PR if that helps.)


Similarly, udeb doesn't set CONFIG_DESKTOP=y which affects POSIX
correctness (see #995833).


Yes, we probably do want to do that. I was going to vimdiff the configs 
to see what we might need to change and harmonise between them. And 
thanks for pointing out CONFIG_DESKTOP, though, I wasn't aware of it.


Cheers,
Chris

--
Chris Boot
bo...@debian.org

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Michael Biebl]

Control: tags -1 + moreinfo

Hello,

systemd freezes execution when it crashes (you should see a 
corresponding log message in the journal).


For this bug report to be actionable, we will need at the very least a 
backtrace of the crash.

In case you had systemd-coredump installed, coredumpctl should show you.
Or maybe you still have a core file in /.


Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998803: marked as pending in busybox

[Christoph Anton Mitterer]

Hey Chris.

Shouldn't this also done in at least the config for the static
busybox... and likely also the udeb?
(I can of course make a PR if that helps.)


Similarly, udeb doesn't set CONFIG_DESKTOP=y which affects POSIX
correctness (see #995833).


Cheers,
Chris.

Bug#1003614: sudo: New sudo asks for a password on a Docker container

[Timo Aaltonen]

Package: sudo
Version: 1.9.8p2-1
Severity: normal

  Hi

I'm using an Azure pipeline for running tests on a Docker image, and some steps 
require running
sudo. The new version prompts for a password while there is only root user with 
no
password set.

Bug#1003497: who-uploads don't show u...@debian.org email default

[Mattia Rizzolo]

On Wed, Jan 12, 2022 at 12:35:36PM +0800, xiao sheng wen wrote:
> I think it's not a bug of who-uploads itself, but also the public key of DD.
> 
> If the public key of DD has not set one uid entry formated as:
> 
> Name 
> 
> who-uploads will not show u...@debian.org email.
> 
> 
> Is need forward this bug to debian-keyring package?

If that's the case (note that I didn't look at this at all, besides
looking up where the relevant code was), then it's not something we can
fix at all, and debian-keyring also can't do anything about it.

The UIDs of a GPG key can only be changed by the key owner, so at most
you'd have to privately tell each people to add such UIDs, and in the
end it also remains that they might not agree.

-- 
regards,
Mattia Rizzolo

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

Bug#1003613: python3-notebook: javascript errors on loading notebooks

[Thomas Viehmann]

Package: python3-notebook
Severity: important
Version: 6.5.4-3

A recent sid upgrade with the new notebook version appears to have 
broken it due to javascript incompatibilities.


One is in libjs-marked, I filed #1003600 for it.
But after fixing that locally, showing directories works, but opening 
notebooks gets an error


Uncaught TypeError: this.pager_element.resizable is not a function
Pager pager.js:26
 main.js:118
execCb require.js:1696
check require.js:883
enable require.js:1139
bind require.js:134
emit require.js:1189
each require.js:59
emit require.js:1188
check require.js:938
enable require.js:1176
init require.js:788
callGetModule require.js:1203
completeLoad require.js:1590
onScriptLoad require.js:1717


I haven't really found what to do. Apparently some dependency is either 
missing or has the wrong version, but I don't know which one.


Best regards

Thomas

Bug#968093: libinput10: confirmation (using bumblebee as well)

[Wim Bertels]

wim schreef op wo 12-01-2022 om 15:57 [+0100]:
> but my system does indeed lag noticeabily, both mouse and keyboard as
> the screen,

this can probably be safely ignored,
as i forgot that cuda was the reason for using this setup,
without cuda processes running the lag or slow respons is gone

hth,
Wim

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Christian Weeks]

The reboot fixed the issue - I now have a working computer again, though getting
to a reboot was a bit painful.

> systemctl reboot
Failed to reboot system via logind: Connection timed out
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
It is possible to perform action directly, see discussion of --force --force in
man:systemctl(1).
> systemctl reboot --force
Failed to execute operation: Failed to activate service
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
It is possible to perform action directly, see discussion of --force --force in
man:systemctl(1).
> systemctl reboot --force --force 



On Wed, 2022-01-12 at 15:36 +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 1003611:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003611.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian systemd Maintainers 
> 
> If you wish to submit further information on this problem, please
> send it to 1003...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Bug#1003610: libc6 crashes with VIA C7 and VIA Eden processors starting with 2.33

[Aurelien Jarno]

On 2022-01-12 16:14, Wolfgang Walter wrote:
> Package: libc6
> Version: 2.33-2
> Severity: important
> 
> After upgrading from libc6 2.32 to 2.33 all machines with a VIA C7 or VIA
> Eden show segfaults in libc (i.e. hostname fails to work, or rebooting
> fails). Machines with VIA Nehemiah work fine.

Could you please provide more details? At least the content of dmesg
when it happens or ideally a core dump or a backtrace.

Thanks,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1003611: systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable

[Christian Weeks]

Package: systemd
Version: 250.2-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?
I upgraded my local sid installation, which was about a week out of date.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Nothing
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

I have just performed an upgrade of sid, which included the 250.2 systemd 
update. It seems that during that update the root systemd
process has died, and now every request of systemd is timing out, causing 
packages to fail to install and who knows what other issues.
I'm reluctant to reboot, but I will have to I guess, and hope that systemd 
manages to load itself properly afterwards.

Some relevant snippets from the upgrade in flight:

...
Unpacking xserver-xorg-core (2:1.20.14-1) over (2:1.20.13-3) ...
Preparing to unpack .../15-systemd-timesyncd_250.2-1_amd64.deb ...
Unpacking systemd-timesyncd (250.2-1) over (249.7-1) ...
Preparing to unpack .../16-libpam-systemd_250.2-1_amd64.deb ...
Unpacking libpam-systemd:amd64 (250.2-1) over (249.7-1) ...
Setting up libc6:amd64 (2.33-2) ...
(Reading database ... 639000 files and directories currently installed.)
Preparing to unpack .../systemd_250.2-1_amd64.deb ...
Unpacking systemd (250.2-1) over (249.7-1) ...
Setting up libc6:i386 (2.33-2) ...
(Reading database ... 639034 files and directories currently installed.)
Preparing to unpack .../00-libsystemd0_250.2-1_amd64.deb ...
De-configuring libsystemd0:i386 (249.7-1), to allow configuration of 
libsystemd0:amd64 (249.7-1) ...
Unpacking libsystemd0:amd64 (250.2-1) over (249.7-1) ...
Preparing to unpack .../01-libsystemd0_250.2-1_i386.deb ...
Unpacking libsystemd0:i386 (250.2-1) over (249.7-1) ...
Preparing to unpack .../02-libudev-dev_250.2-1_i386.deb ...
De-configuring libudev-dev:amd64 (249.7-1), to allow configuration of 
libudev-dev:i386 (249.7-1) ...
Unpacking libudev-dev:i386 (250.2-1) over (249.7-1) ...
Preparing to unpack .../03-libudev-dev_250.2-1_amd64.deb ...
Unpacking libudev-dev:amd64 (250.2-1) over (249.7-1) ...
Preparing to unpack .../04-udev_250.2-1_amd64.deb ...
Unpacking udev (250.2-1) over (249.7-1) ...
Preparing to unpack .../05-libudev1_250.2-1_amd64.deb ...
De-configuring libudev1:i386 (249.7-1), to allow configuration of 
libudev1:amd64 (249.7-1) ...
Unpacking libudev1:amd64 (250.2-1) over (249.7-1) ...
Preparing to unpack .../06-libudev1_250.2-1_i386.deb ...
Unpacking libudev1:i386 (250.2-1) over (249.7-1) ...
Preparing to unpack .../07-libglx-dev_1.4.0-1_i386.deb ...
De-configuring libglx-dev:amd64 (1.3.4-2+b1), to allow configuration of 
libglx-dev:i386 (1.3.4-2+b1) ...
...
De-configuring libglvnd0:i386 (1.3.4-2+b1), to allow configuration of 
libglvnd0:amd64 (1.3.4-2+b1) ...
Unpacking libglvnd0:amd64 (1.4.0-1) over (1.3.4-2+b1) ...
Preparing to unpack .../53-libglvnd0_1.4.0-1_i386.deb ...
Unpacking libglvnd0:i386 (1.4.0-1) over (1.3.4-2+b1) ...
Setting up libsystemd0:amd64 (250.2-1) ...
Setting up systemd (250.2-1) ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Failed to try-restart systemd-networkd.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status systemd-networkd.service' for details.
Failed to try-restart systemd-resolved.service: Connection timed out
See system logs and 'systemctl status systemd-resolved.service' for details.
Failed to try-restart systemd-journald.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status systemd-journald.service' for details.
(Reading database ... 639016 files and directories currently installed.)
Preparing to unpack .../00-systemd-sysv_250.2-1_amd64.deb ...
Unpacking systemd-sysv (250.2-1) over (249.7-1) ...
Preparing to unpack .../01-libgnutls28-dev_3.7.2-5_amd64.deb ...
De-configuring libgnutls28-dev:i386 (3.7.2-4), to allow configuration of 
libgnutls28-dev:amd64 (3.7.2-4) ...
...
Setting up udev (250.2-1) ...
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to restart udev.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status udev.service' for details.
invoke-rc.d: initscript udev, action "restart" failed.
Failed to get properties: Connection timed out
dpkg: error processing package udev (--configure):
 installed udev package post-installation script subprocess returned error exit 
status 1
Setting up libss2:amd64 (1.46.5-2) ...
...
Errors were encountered while processing:
 udev
 ed

Bug#984244: mpqc: ftbfs with GCC-11

[Andreas Tille]

Control: forwarded -1 https://github.com/ValeevGroup/mpqc/issues/60

Bug#1003610: libc6 crashes with VIA C7 and VIA Eden processors starting with 2.33

[Wolfgang Walter]

Package: libc6
Version: 2.33-2
Severity: important

After upgrading from libc6 2.32 to 2.33 all machines with a VIA C7 or 
VIA Eden show segfaults in libc (i.e. hostname fails to work, or 
rebooting fails). Machines with VIA Nehemiah work fine.


I tested again starting with an older version of sid, upgrading all 
packages but libc6 (pinned to 2.32) (some other packaages could not been 
updated because they already depend on 2.33). This works fine.



Regards,
--
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#1003609: readlink: invalid option -- 'b' in /lib/lsb/init-functions.d/40-systemd

[Peter Palfrader]

Package: systemd
Version: 247.3-6
Severity: normal
Tags: patch

Hi!

/lib/lsb/init-functions.d/40-systemd calls
  readlink -f "$executable"
which causes warnings if an executable starts with -, like in "-bash" when
/lib/lsb/init-functions is sourced from a login shell.

] root@yukon:~# . /lib/lsb/init-functions
] readlink: invalid option -- 'b'
] Try 'readlink --help' for more information.
] root@yukon:~#

This happens for instance with the slony init script:

| adns002:~# grep 'init-functions ' /etc/init.d/slony1
| su -c ". /lib/lsb/init-functions ; umask 027 ; start_daemon 
-p $(pidfile $1) $DAEMON -f $(conffile $1) -p $(pidfile $1) >>$(logfile $1) 
2>&1 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#1002286: Acknowledgement (transition: Gazebo + Ignition libraries)

[Jose Luis Rivero]

On Mon, Jan 10, 2022 at 6:15 PM Sebastian Ramacher 
wrote:

> Control: tags -1 confirmed
>
> On 2022-01-10 17:41:17, Jose Luis Rivero wrote:
> > I have received no negative feedback or blockers in the last 20 days, I'm
> > afraid that we can not wait
> > much longer since this bug is blocking others (like Dartsim transition).
> My
> > plan would be to proceed
> > with the plan in the next few days unless feedback appears in the next 48
> > hours.
>
> These transitions are self-contained and gazebo is not in testing. I
> think you can just go ahead with the uploads.
>

Thanks Sebastian for double checking. I proceeded yesterday with the upload
of the whole set of 10 packages to unstable. As far as I can tell nothing
is
broken as of now.

I'll close the bug in a few days if no problems appear.


>
> Cheers
>
> >
> > Thanks!
>
> --
> Sebastian Ramacher
>

Bug#984121: fbreader: ftbfs with GCC-11

[Ying-Chun Liu (PaulLiu)]

Hi,


this patches fixes the bug. I'll do QA uploads soon.

Yours,
Paul

Description: Fix FTBFS for gcc 11
 Comparator operator() have to be const in gcc 11.
Bug-Debian: http://bugs.debian.org/984121
Author: Ying-Chun Liu (PaulLiu) 
Index: fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.cpp
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/library/Comparators.cpp
+++ fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.cpp
@@ -25,7 +25,7 @@
 bool BookComparator::operator() (
 	const shared_ptr book0,
 	const shared_ptr book1
-) {
+) const {
 	const std::string &seriesTitle0 = book0->seriesTitle();
 	const std::string &seriesTitle1 = book1->seriesTitle();
 	int comp = seriesTitle0.compare(seriesTitle1);
@@ -50,14 +50,14 @@ bool BookComparator::operator() (
 bool BookByFileNameComparator::operator() (
 	const shared_ptr book0,
 	const shared_ptr book1
-) {
+) const {
 	return book0->filePath() < book1->filePath();
 }
 
 bool AuthorComparator::operator() (
 	const shared_ptr author0,
 	const shared_ptr author1
-) {
+) const {
 	if (author0.isNull()) {
 		return !author1.isNull();
 	}
@@ -72,7 +72,7 @@ bool AuthorComparator::operator() (
 bool TagComparator::operator() (
 	shared_ptr tag0,
 	shared_ptr tag1
-) {
+) const {
 	if (tag0.isNull()) {
 		return !tag1.isNull();
 	}
Index: fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.h
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/library/Comparators.h
+++ fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.h
@@ -32,7 +32,7 @@ public:
 	bool operator () (
 		const shared_ptr book0,
 		const shared_ptr book1
-	);
+	) const;
 };
 
 class BookByFileNameComparator {
@@ -41,7 +41,7 @@ public:
 	bool operator () (
 		const shared_ptr book0,
 		const shared_ptr book1
-	);
+	) const;
 };
 
 class AuthorComparator {
@@ -50,7 +50,7 @@ public:
 	bool operator () (
 		const shared_ptr author0,
 		const shared_ptr author1
-	);
+	) const;
 };
 
 class TagComparator {
@@ -59,7 +59,7 @@ public:
 	bool operator () (
 		shared_ptr tag0,
 		shared_ptr tag1
-	);
+	) const;
 };
 
 #endif /* __COMPARATORS_H__ */
Index: fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.cpp
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/network/NetworkComparators.cpp
+++ fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.cpp
@@ -19,7 +19,7 @@
 
 #include "NetworkComparators.h"
 
-bool NetworkBookItemComparator::operator () (const shared_ptr &bookPtr0, const shared_ptr &bookPtr1) {
+bool NetworkBookItemComparator::operator () (const shared_ptr &bookPtr0, const shared_ptr &bookPtr1) const {
 	const bool book0isABook =
 		bookPtr0->isInstanceOf(NetworkBookItem::TYPE_ID);
 	const bool book1isABook =
@@ -81,7 +81,7 @@ bool NetworkBookItemComparator::operator
 NetworkAuthorComparator::NetworkAuthorComparator(const std::map &rates) : myRates(rates) {
 }
 
-bool NetworkAuthorComparator::operator () (const NetworkBookItem::AuthorData &author0, const NetworkBookItem::AuthorData &author1) {
+bool NetworkAuthorComparator::operator () (const NetworkBookItem::AuthorData &author0, const NetworkBookItem::AuthorData &author1) const {
 	std::map::const_iterator it1 = myRates.find(author0);
 	std::map::const_iterator it2 = myRates.find(author1);
 	if (it1 == myRates.end() && it2 == myRates.end()) {
Index: fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.h
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/network/NetworkComparators.h
+++ fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.h
@@ -29,7 +29,7 @@
 class NetworkBookItemComparator {
 
 public:
-	bool operator () (const shared_ptr &bookPtr0, const shared_ptr &bookPtr1);
+	bool operator () (const shared_ptr &bookPtr0, const shared_ptr &bookPtr1) const;
 };
 
 
@@ -38,7 +38,7 @@ class NetworkAuthorComparator {
 public:
 	NetworkAuthorComparator(const std::map &rates);
 
-	bool operator () (const NetworkBookItem::AuthorData &author0, const NetworkBookItem::AuthorData &author1);
+	bool operator () (const NetworkBookItem::AuthorData &author0, const NetworkBookItem::AuthorData &author1) const;
 
 private:
 	const std::map &myRates;


OpenPGP_signature
Description: OpenPGP digital signature

Bug#976811: [pkg-php-pear] Bug#976811: transition: php8.1

[David Prévot]

Hi Paul,

Le 11/01/2022 à 15:52, Paul Gevers a écrit :

On 10-01-2022 23:43, David Prévot wrote:

Le 10/01/2022 à 16:44, Paul Gevers a écrit :

On 10-01-2022 21:13, Ondřej Surý wrote:
I thought I filled RM bugs for all of them, but I found only 
#1003055 for php-apcu-bc, something must went wrong.


Neither of these support PHP 8.x, and those packages should be 
removed.



Seems like that needs more work:

elbrus@coccia:~$ dak rm --no-action -R --suite testing php-apcu-bc
[...]
Checking reverse dependencies...
# Broken Build-Depends:
php-doctrine-cache: php-apcu-bc


That on[e] is gone.


In unstable (thanks for that), but it fails to migrate to testing, due 
to the 'PHPUnit requires the "dom" extension.' issue.


Can’t find this issue. Did it go away by itself, or did you make any change?


symfony: php-apcu-bc


There seems to be a new (unrelated?) FTBFS, so we need to figure it 
out (or drop symfony from testing until then).


Found a fix, version 5.4.2+dfsg-2 uploaded.

If that's OK with you/the team, I can check how much needs to be 
removed doesn't seems like a lot of fun yet:


Right, that’s probably why it used to be a key package.

Regards

David


OpenPGP_signature
Description: OpenPGP digital signature

Bug#968093: libinput10: confirmation (using bumblebee as well)

[wim]

Package: libinput10
Version: 1.16.4-3
Followup-For: Bug #968093
X-Debbugs-Cc: wim.bert...@ucll.be

Hello,

i don't know libinput10 is responsible for this behaviour,
but my system does indeed lag noticeabily, both mouse and keyboard as the 
screen,
but since the behaviour is the same

setup:
* laptop + two different screens via dockingstation
* bumblebee with intel and nvidia

hth, suggestions welcome

more info:
$ xrandr
Screen 0: minimum 8 x 8, current 4740 x 1600, maximum 32767 x 32767
eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 340mm x 
190mm
   3840x2160 60.00*+  40.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 connected primary 1920x1080+1920+0 (normal left inverted right x axis 
y axis) 0mm x 0mm
   VIRTUAL1.542-1920x1080  60.00* 
   VIRTUAL1.543-1920x1080  59.94  
   VIRTUAL1.544-1920x1080  50.00  
   VIRTUAL1.545-1680x1050  59.95  
   VIRTUAL1.546-1600x900  60.00  
   VIRTUAL1.547-1440x900  59.89  
   VIRTUAL1.548-1280x1024  60.02  
   VIRTUAL1.549-1280x800  59.81  
   VIRTUAL1.550-1280x720  60.00  
   VIRTUAL1.551-1280x720  59.94  
   VIRTUAL1.552-1280x720  50.00  
   VIRTUAL1.553-1024x768  60.00  
   VIRTUAL1.554-800x600  60.32  
   VIRTUAL1.555-720x576  50.00  
   VIRTUAL1.556-720x480  59.94  
   VIRTUAL1.557-640x480  59.94  
   VIRTUAL1.558-640x480  59.93  
VIRTUAL2 connected 900x1600+3840+0 left (normal left inverted right x axis y 
axis) 0mm x 0mm
   VIRTUAL2.560-1600x900  59.98* 
   VIRTUAL1.546-1600x900  60.00  
   VIRTUAL2.561-1280x1024  75.02  
   VIRTUAL1.548-1280x1024  60.02  
   VIRTUAL2.562-1152x864  75.00  
   VIRTUAL2.563-1024x768  75.03  
   VIRTUAL1.553-1024x768  60.00  
   VIRTUAL2.564-800x600  75.00  
   VIRTUAL1.554-800x600  60.32  
   VIRTUAL2.565-640x480  75.00  
   VIRTUAL1.557-640x480  59.94

$ lspci -nn | grep -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-H GT2 
[UHD Graphics 630] [8086:3e9b] (rev 02)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117GLM [Quadro 
T2000 Mobile / Max-Q] [10de:1fb8] (rev a1)

$ lshw -C Display
  *-display 
   description: VGA compatible controller
   product: TU117GLM [Quadro T2000 Mobile / Max-Q]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: vga_controller bus_master cap_list rom
   configuration: driver=nvidia latency=0
   resources: irq:209 memory:e500-e5ff memory:8000-8fff 
memory:9000-91ff ioport:4000(size=128) memory:e608-e60f
  *-display
   description: VGA compatible controller
   product: CoffeeLake-H GT2 [UHD Graphics 630]
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 02
   width: 64 bits
   clock: 33MHz
   capabilities: vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:191 memory:e400-e4ff memory:a000-afff 
ioport:5000(size=64) memory:c-d

$ dpkg -l | grep nouv
ii  libdrm-nouveau2:amd64   2.4.104-1   
   amd64Userspace interface to nouveau-specific 
kernel DRM services -- runtime
ii  xserver-xorg-video-nouveau  1:1.0.17-1  
   amd64X.Org X server -- Nouveau display driver

$ dpkg -l | grep nvidia
ii  bumblebee-nvidia3.2.1-27
   amd64NVIDIA Optimus support using the 
proprietary NVIDIA driver
ii  glx-alternative-nvidia  1.2.0   
   amd64allows the selection of NVIDIA as GLX 
provider
ii  libegl-nvidia0:amd64460.91.03-1 
   amd64NVIDIA binary EGL library
ii  libgl1-nvidia-glvnd-glx:amd64   460.91.03-1 
   amd64NVIDIA binary OpenGL/GLX library (GLVND 
variant)
ii  libgles-nvidia1:amd64   460.91.03-1 
   amd64NVIDIA binary OpenGL|ES 1.x library
ii  libgles-nvidia2:amd64   460.91.03-1 
   amd64NVIDIA binary OpenGL|ES 2.x library
ii  libglx-nvidia0:amd64460.91.03-1 
   amd64NVIDIA binary GLX library
ii  libnvidia-cbl:amd64 460.91.03-1 
   amd64NVIDIA binary Vulkan r

Bug#1003608: gnome: lower dependency on gnome-documents to "recommends" or "suggests"

[Johannes Rohr]

Package: gnome
Version: 1:41+1
Severity: normal

Dear Maintainer,

gnome-documents had its latest release in 2014, so it is likely orphaned
upstream. At the same time, I have often seen it causing excessive CPU load
without discernible benefit.

I thing, the dependency should be lowered to recommends or suggests.

Thanks!


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome depends on:
ii avahi-daemon 0.8-5
ii cheese 41.1-1
ii cups-pk-helper 0.2.6-1+b1
ii desktop-base 11.0.3
ii evolution 3.42.2-1
ii evolution-plugins 3.42.2-1
ii file-roller 3.40.0-3
ii gedit-plugins 40.1-2
ii gnome-calendar 41.1-1
ii gnome-clocks 41.0-1
ii gnome-color-manager 3.36.0-1+b1
ii gnome-core 1:41+1
ii gnome-documents 3.34.0-4
ii gnome-maps 41.2-1
ii gnome-music 41.0-1
ii gnome-screenshot 41.0-1
ii gnome-sound-recorder 40.0-2
ii gnome-todo 3.28.1-6+b1
ii gnome-tweaks 40.0-4
ii gnome-weather 41.0-1
ii gstreamer1.0-libav 1:1.18.5-dmo1
ii gstreamer1.0-plugins-ugly 1:1.18.5-dmo1
ii libgsf-bin 1.14.47-1+b1
ii libproxy1-plugin-networkmanager 0.4.17-1
ii libreoffice-calc 1:7.2.5-1
ii libreoffice-gnome 1:7.2.5-1
ii libreoffice-impress 1:7.2.5-1
ii libreoffice-writer 1:7.2.5-1
ii network-manager-gnome 1.24.0-1
ii orca 41.1-1+0
ii rhythmbox 3.4.4-4+b1
ii rhythmbox-plugin-cdrecorder 3.4.4-4+b1
ii rhythmbox-plugins 3.4.4-4+b1
ii rygel-playbin 0.40.2-1+b1
ii rygel-tracker 0.40.2-1+b1
ii seahorse 41.0-1
ii shotwell 0.30.14-2
ii simple-scan 40.6-1
ii totem-plugins 3.38.2-1
ii xdg-user-dirs-gtk 0.10-3

Versions of packages gnome recommends:
ii gnome-games 1:41+1
ii gnome-remote-desktop 41.1-3
ii nautilus-extension-brasero 3.12.3-1
ii transmission-gtk 3.00-2

Versions of packages gnome suggests:
pn alacarte 
pn empathy 
pn firefox-esr-l10n-all | firefox-l10n-all 
pn polari 
ii sound-juicer 3.38.0-1
pn vinagre 
pn webext-ublock-origin 

Versions of packages gnome-core depends on:
ii adwaita-icon-theme 41.0-1
ii at-spi2-core 2.42.0-2
ii baobab 41.0-1
ii caribou 0.4.21-7.2
ii dconf-cli 0.40.0-2
ii dconf-gsettings-backend 0.40.0-2
ii eog 41.1-1
ii evince 41.3-1
ii evolution-data-server 3.42.2-1
ii firefox 96.0-1
ii fonts-cantarell 0.303-2
ii gdm3 41.0-3
ii gedit 40.1-3
ii gkbd-capplet 3.26.1-1+b1
ii glib-networking 2.70.1-1
ii gnome-backgrounds 41.0-1
ii gnome-bluetooth 3.34.5-4
ii gnome-calculator 1:41.1-1
ii gnome-characters 41.0-1
ii gnome-contacts 41.0-1
ii gnome-control-center 1:41.2-1
ii gnome-disk-utility 41.0-1
ii gnome-font-viewer 41.0-1
ii gnome-keyring 40.0-3
ii gnome-logs 3.36.0-3
ii gnome-menus 3.36.0-1
ii gnome-online-accounts 3.40.1-2
ii gnome-online-miners 3.34.0-4
ii gnome-session 40.1.1-3
ii gnome-settings-daemon 41.0-3
ii gnome-shell 41.2-1
ii gnome-shell-extensions 41.1-1
ii gnome-software 41.2-1
ii gnome-sushi 41.0-2
ii gnome-system-monitor 41.0-1
ii gnome-terminal 3.42.2-1
ii gnome-themes-extra 3.28-1
ii gnome-user-docs 41.1-1
ii gnome-user-share 3.34.0-3+b1
ii gsettings-desktop-schemas 41.0-2
ii gstreamer1.0-packagekit 1.2.4-1
ii gstreamer1.0-plugins-base 1.18.5-dmo1
ii gstreamer1.0-plugins-good 1.18.5-dmo3
ii gvfs-backends 1.48.1-2
ii gvfs-fuse 1.48.1-2
ii libatk-adaptor 2.38.0-2
ii libcanberra-pulse 0.30-8
ii libglib2.0-bin 2.70.2-1
ii libpam-gnome-keyring 40.0-3
ii libproxy1-plugin-gsettings 0.4.17-1
ii libproxy1-plugin-webkit 0.4.17-1
ii librsvg2-common 2.50.7+dfsg-2
ii nautilus 41.1-1
ii pulseaudio 15.0+dfsg1-3
ii pulseaudio-module-bluetooth 15.0+dfsg1-3
ii sound-theme-freedesktop 0.8-2
ii system-config-printer-common 1.5.14-1
ii system-config-printer-udev 1.5.14-1
ii totem 3.38.2-1
ii tracker 3.1.2-3
ii xdg-desktop-portal-gnome 41.1-1
ii yelp 41.2-1
ii zenity 3.41.0-2

Versions of packages gnome-core recommends:
ii libproxy1-plugin-networkmanager 0.4.17-1
ii network-manager-gnome 1.24.0-1

gnome-core suggests no packages.

-- no debconf information

Bug#998937: aspell-cs: missing required debian/rules targets build-arch and/or build-indep

[Andreas Beckmann]

Followup-For: Bug #998937
Control: tag -1 patch pending

Hi,

I've just uploaded a NMU to DELAYED/10 to fix this issue.
Please let me know if I should delay it longer.


Andreas
diff -Nru aspell-cs-0.51.0/debian/changelog aspell-cs-0.51.0/debian/changelog
--- aspell-cs-0.51.0/debian/changelog   2021-02-22 15:45:32.0 +0100
+++ aspell-cs-0.51.0/debian/changelog   2022-01-12 15:25:42.0 +0100
@@ -1,3 +1,10 @@
+aspell-cs (0.51.0-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/rules: Add build-arch and build-indep targets.  (Closes: #998937)
+
+ -- Andreas Beckmann   Wed, 12 Jan 2022 15:25:42 +0100
+
 aspell-cs (0.51.0-1.2) unstable; urgency=medium
 
   [ Andreas Beckmann ]
diff -Nru aspell-cs-0.51.0/debian/rules aspell-cs-0.51.0/debian/rules
--- aspell-cs-0.51.0/debian/rules   2021-02-22 15:30:48.0 +0100
+++ aspell-cs-0.51.0/debian/rules   2022-01-12 15:23:33.0 +0100
@@ -12,6 +12,8 @@
dh_testdir
 
 build: build-stamp
+build-arch: build-stamp
+build-indep: build-stamp
 
 build-stamp:  config.status
dh_testdir

Bug#1003607: luminance-hdr 2.6.0 almost always crashes on startup on files that worked with 2.4.0

[Tim Connors]

Package: luminance-hdr
Version: 2.6.0+dfsg-2+b8
Severity: important

On bullseye, luminance-hdr almost always crashes on startup on my
machine with the following failure (but does succeed in starting up on
the occasional old .exr file I still have lying around):


37317,2> luminance-hdr *exr
libpng warning: iCCP: known incorrect sRGB profile
Min Luminance:  1e-06
Max Luminance:  2.33984
Mapping method:  3
fromLDRPFStoQImage() = 272.595 msec
resizeFrame() = 5.021 msec
pfscopy() = 0.163 msec
pfscopy() = 0.153 msec
pfstmo_mantiuk06 (Mode: Contrast Mapping, scaleFactor: 0.1, saturationFactor: 
0.8, detailFactor: 0.8)

tmo_mantiuk06 = 29.889 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 0.482 msec
Black in = 0, Black out = 0, White in = 0.960784, White out = 1, Gamma = 1
gamma_levels() = 1.142 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 1.771 msec
pfscopy() = 0.059 msec
pfscopy() = 0.049 msec
transformColorSpace: Found right match for colorspace conversion
transformRGB2XYZ() = 0.564 msec
pfstmo_mantiuk08 (saturation factor: 1, contrast enhancement factor: 1, 
white_y: -2, setluminance: 0)
Display function: gamma-gain-black-ambient
   gamma = 2.2   L_max = 200 L_black = 0.8
   E_amb = 60k = 0.01
Display size paramaters:
   pixels per visual degree = 30
   viewing distance = 0.5 [meters]
transformColorSpace: Found right match for colorspace conversion
transformXYZ2RGB() = 0.476 msec
transformColorSpace: Found right match for colorspace conversion
transformRGB2XYZ() = 1.667 msec

tmo_mantiuk08 = 76.152 msec
transformColorSpace: Found right match for colorspace conversion
transformXYZ2RGB() = 0.143 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 1.033 msec
Black in = 0, Black out = 0, White in = 0.980392, White out = 1, Gamma = 1
gamma_levels() = 0.595 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 0.323 msec
pfscopy() = 0.063 msec
pfscopy() = 0.185 msec
pfstmo_fattal02 (alpha: 1, beta: 0.9. saturation: 1, noise: 0.01, fftsolver: 1)

pde residual error: -nan

tmo_fattal02 = 551.336 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 5.318 msec
Black in = 0, Black out = 0, White in = 0.0196078, White out = 1, Gamma = 1
gamma_levels() = 5.143 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 1.46 msec
pfscopy() = 0.187 msec
pfscopy() = 0.061 msec
pfstmo_ferradans11 (rho: -2, inv_alpha: 5)

tmo_ferradans11 = 1017.3 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 1.231 msec
Black in = 0.0156863, Black out = 0, White in = 1, White out = 1, Gamma = 1
gamma_levels() = 7.543 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
fromLDRPFStoQImage() = 7.46 msec
pfscopy() = 0.092 msec
pfscopy() = 0.055 msec
pfstmo_drago03 (bias: 0.85)

tmo_drago03 = 8.034 msec
Min Luminance:  0
Max Luminance:  1
Mapping method:  0
luminance-hdr: ./src/Libpfs/colorspace/rgbremapper.h:95: uint8_t 
Remapper::operator()(float) const: Assertion `sample >= 0.f' 
failed.
luminance-hdr: ./src/Libpfs/colorspace/rgbremapper.h:95: uint8_t 
Remapper::operator()(float) const: Assertion `sample >= 0.f' 
failed.
Aborted






Whereas if I rebuild 2.4 in a docker image, it loads that image just
fine:


37295,32> docker run -ti --rm -e DISPLAY=$DISPLAY -e CWD="$PWD" -v 
/tmp/.X11-unix/:/tmp/.X11-unix -v /home/tconnors:/home/tconnors luminance-hdr 
luminance-hdr *exr
/
/home/tconnors/photos/uncategorised/Tasmania 2021/qiv-2
I18NDIR:  /usr/share/luminance-hdr/i18n
QLibraryInfo::location(QLibraryInfo::TranslationsPath)):  
"/usr/share/qt5/translations"
Database opened
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: unable to load driver: amdgpu_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: amdgpu
libGL error: failed to open drm device: No such file or directory
libGL error: failed to load driver: radeonsi
HdrViewer::mapFrameToImage() [NEW]= 1630.49 msec
MainWindow::updateActions( 0 )
resizeFrame() = 5.516 msec
pfstmo_mantiuk06 (Mode: Contrast Mapping, scaleFactor: 0.1, saturationFactor: 
0.8, detailFactor: 0.8)
fromLDRPFStoQImage() = 0.05 msec
transformColorSpace: Found right match for colorspace conversion
transformRGB2XYZ() = 2.482 msec
pfstmo_mantiuk08 (saturation factor: 1, contrast enhancement factor: 1, 
white_y: -2, setluminance: 0)
Display function: gamma-gain-black-ambient
   gamma = 2.2   L_max = 200 L_black = 0.8
   E_amb = 60k = 0.01
Display size paramaters:
   pixels per visual degree = 30
   viewing distance = 0.5 [meters]
transformColorSpace: Found right match for colorspace conversion
transformXYZ2RGB() = 4.528 msec
pfstmo_ma

Bug#963594: ITP: golang-github-jsimonetti-rtnetlink -- low-level access to the Linux rtnetlink API

[Leo "Costela" Antunes]

Hi Benjamin,

sorry for not answering your pings before! Thanks for taking this on!
It was indeed a bit stalled on my side :(

Cheers,
Leo

On Tue, Jan 11, 2022 at 2:23 PM Benjamin Drung  wrote:
>
> Hi,
>
> On Wed, 24 Jun 2020 09:49:04 +0200 "Leo Antunes" 
> wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Leo Antunes 
> > Control: block 963592 by -1
> >
> > * Package name: golang-github-jsimonetti-rtnetlink
> >   Version : 0.0~git20200505.3ee32e7-1
> >   Upstream Author : Jeroen Simonetti
> > * URL : https://github.com/jsimonetti/rtnetlink
> > * License : Expat
> >   Programming Lang: Go
> >   Description : Package rtnetlink provides low-level access to
> the Linux rtnetlink API.
> >
> >  Package rtnetlink allows the kernel's routing tables to be read and
> >  altered. Network routes, IP addresses, Link parameters, Neighbor
> setups,
> >  Queueing disciplines, Traffic classes and Packet classifiers may all
> be
> >  controlled. It is based on netlink messages.
> >  .
> >  A convenient, high-level API wrapper is available using package rtnl
> >  (https://godoc.org/github.com/jsimonetti/rtnetlink/rtnl).
> >  .
> >  The base rtnetlink library explicitly only exposes a limited low-
> level
> >  API to rtnetlink. It is not the intention (nor wish) to create an
> >  iproute2 replacement.
>
> Since there were no progress on this ticket, I just high-jacked it (to
> be able to drop the vendored libs in prometheus-node-exporter).
> rtnetlink is uploaded to the NEW queue and published on
> https://salsa.debian.org/go-team/packages/golang-github-jsimonetti-rtnetlink
> Please add yourself to the Uploaders.
>
> --
> Benjamin Drung
>
> Senior DevOps Engineer and Debian & Ubuntu Developer
> Compute Platform Operations Cloud
>
> IONOS SE | Revaler Str. 30 | 10245 Berlin | Deutschland
> E-Mail: benjamin.dr...@ionos.com | Web: www.ionos.de
>
> Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 24498
>
> Vorstand: Hüseyin Dogan, Dr. Martin Endreß, Claudia Frese, Henning
> Kettler, Arthur Mai, Britta Schmidt, Achim Weiß
> Aufsichtsratsvorsitzender: Markus Kadelke
>
>
> Member of United Internet
>

Bug#1003606: python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4)

[Andreas Beckmann]

Package: python3-flask-httpauth
Version: 4.5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../python3-flask-httpauth_4.5.0-1_all.deb ...
  Unpacking python3-flask-httpauth (4.5.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/flask-httpauth.1.gz', which is also 
in package python-flask-httpauth-doc 3.2.4-3.1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb

Obviously the manpage was moved between the packages.


cheers,

Andreas


python-flask-httpauth-doc=3.2.4-3.1_python3-flask-httpauth=4.5.0-1.log.gz
Description: application/gzip

Bug#1003605: ITP: streamdeck-ui -- GUI for the Elgato Stream Deck

[Paulo Roberto Alves de Oliveira (aka kretcheu)]

Package: wnpp
Severity: wishlist
Owner: "Paulo Roberto Alves de Oliveira (aka kretcheu)" 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: streamdeck-ui
  Version : 1.1.2
  Upstream Author : Timothy Crosley 
* URL : https://timothycrosley.github.io/streamdeck-ui/
* License : GPL-2+
  Programming Lang: Python
  Description : GUI for the Elgato Stream Deck

 Key Features:
 Linux Compatible:
 Enables usage of all Stream Deck devices on Linux without needing to code.

 Multi-device:
 Enables connecting and configuring multiple Stream Deck devices on one
 computer.

 Brightness Control:
 Supports controlling the brightness from both the configuration UI and buttons
 on the device itself.

 Configurable Button Display:
 Icons + Text, Icon Only, and Text Only configurable per button on the Stream
 Deck.

 Multi-Action Support:
 Run commands, write text and press hotkey combinations at the press of a single
 button on your Stream Deck.

 Button Pages:
 streamdeck_ui supports multiple pages of buttons and dynamically setting up
 buttons to switch between those pages.

 Auto Reconnect:
 Automatically and gracefully reconnects, in the case the device is unplugged
 and replugged in.

 Import/Export:
 Supports saving and restoring Stream Deck configuration.

Bug#1003604: security.debian.org: Link to packges.debian.org does not work

[Helge Kreutzmann]

Package: security.debian.org
Severity: normal

(I'm not sure if you are the right recipient, please reassign)

I'm working on a script to determine the latest version for stable for
a package automatically (more details on request). For the "plain"
stable version, the following can be used:
https://packages.debian.org/bullseye/amd64/manpages-de/download

(I use a package with a backport as example).

Now the backport can be retrived accordingly:
https://packages.debian.org/bullseye-backports/amd64/manpages-de/download

Whats missing are security updates. Using (as an example) Firefox-esr
I see on
https://tracker.debian.org/pkg/firefox-esr

a link called "stable security" to 
https://packages.debian.org/source/stable-security/firefox-esr

However, this link says "Error".

and in yellow "two or more packages specified (firefox-esr
stable-security)"

So either the link, p.d.o or both are currently broken.

(Changing source → amd64 in the last link does not help either)

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


signature.asc
Description: PGP signature

Bug#1003603: ITP: hcxbtdumptool -- Small tool to capture packets from Bluetooth devices

[Paulo Roberto Alves de Oliveira (aka kretcheu)]

Package: wnpp
Severity: wishlist
Owner: "Paulo Roberto Alves de Oliveira (aka kretcheu)" 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: hcxbtdumptool
  Version : 0.0.1
  Upstream Author : ZeroBeat 
* URL : https://github.com/ZerBea/hcxbtdumptool
* License : MIT
  Programming Lang: C
  Description : Small tool to capture packets from Bluetooth devices

Only help and version menu and Bluetooth device information available.

This is a playground to get some knowledge about coding Bluetooth.

Everything is high experimental.

Similar to hcxdumptool (Wi-Fi) use ioctl() system calls to control the device.

Bug#1003274: ITP: sentrypeer -- SIP peer to peer honeypot for VoIP

[Gavin Henry]

What's the best way to do an update for libosip2?

Just do one on salsa and email the VoIP packaging group?

Thanks.