Bug#944785: pufferfish wants to link with twopaco and ntcard

[Andrius Merkys]

Hello,

twopaco has entered testing (yay!), thus I gave its reverse dependency,
pufferfish (ITP bug #944785), a look. pufferfish carries embedded copies
of twopaco and ntcard with a modified build system to create static (or
is it shared?) libraries for these two and then links pufferfish with
them. For Debian twopaco and ntcard have been un-embedded from
pufferfish and packaged as separate binary packages instead. However,
they do not build neither shared nor static libraries, just executables.

I think we can get around by patching twopaco and ntcard builds to
include static libraries in their binary packages. Does this sound right?

Best,
Andrius

Bug#1021032: (no subject)

[Rik Mills]

On Mon, 3 Oct 2022 07:46:54 +0100 Rik Mills  wrote:

Comment from the launchpad counterpart to this bug below:

https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1991418/comments/10

"So, hate to rain on your parade, but as I wrote yesterday, the problem 
doesn't occur with upstream (building manually) 3.0.17.4. So there are 
ostensibly no patches to backport from upstream 3.0.18-rc2. This is 
probably an issue in the Debian packaging or at least that is triggered 
by Debian packaging.


Since it seems to affect only the Qt UI, it is most probably a problem 
with the last Qt update. Again, please check with --no-embedded-video."


Running with --no-embedded-video does indeed work, but as expected is 
ugly with the video in a separate floating window.

Bug#1021160: simple-scan: Please bump libhandy-1-dev build-dependency

[Laurent Bigonville]

Source: simple-scan
Version: 42.0-1
Severity: important

Hello,

Currently, simple-scan package defines a build-dependency against
libhandy-1-dev (>= 1.1.90), but the meson files requires libhandy-1-dev >= 1.6.0

libhandy-1-dev >= 1.6.0 is not available on on all architectures and
it's probably a good idea to update the debian/control file and bump the
version of the libhandy-1-dev build-dependency.

Kind regards,
Laurent Bigonville


-- Package-specific info:

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

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Bug#1021161: RM: gwave -- ANAIS; Package depends on Guile 2.2

[Tommi Höynälänmaa]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: tommi.hoynalan...@iki.fi, deb...@alteholz.de, 
pkg-electronics-de...@lists.alioth.debian.org

Bug#1021162: ITA netkit-rusers

[Sydney Cripe]

Package: wnpp
Tags: newcomer
Control: owner -1 !
Control: retitle -1 "1020621 ITA netkit-rusers"

Hello Alberto, 
Thank you for your maintence on the package!
I'd like to adopt it.

Best, 
Sydney 

Bug#1021163: lomiri-indicator-network: binary-all FTBFS

[Adrian Bunk]

Source: lomiri-indicator-network
Version: 1.0.0~git20220718.2ca3619-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=lomiri-indicator-network&arch=all&ver=1.0.0~git20220718.2ca3619-2&stamp=1664719442&raw=0

...
   debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: warning: 
usr/libexec/lomiri-indicator-network/lomiri-indicator-network-secret-agent 
exists in debian/tmp but is not installed to anywhere 
dh_missing: warning: 
usr/libexec/lomiri-indicator-network/lomiri-indicator-network-service exists in 
debian/tmp but is not installed to anywhere 
dh_missing: warning: usr/share/unity/indicators/com.lomiri.indicator.network 
exists in debian/tmp but is not installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: liblomiri-connectivity-qt1-1 (1), 
liblomiri-connectivity-qt1-dev (3), lomiri-connectivity-doc (3), 
lomiri-indicator-network (4), qml-module-lomiri-connectivity (1)
 * dh_installdocs: liblomiri-connectivity-qt1-1 (0), 
liblomiri-connectivity-qt1-dev (0), lomiri-connectivity-doc (0), 
lomiri-indicator-network (3), qml-module-lomiri-connectivity (0)
 * dh_installexamples: liblomiri-connectivity-qt1-1 (0), 
liblomiri-connectivity-qt1-dev (3), lomiri-connectivity-doc (0), 
lomiri-indicator-network (0), qml-module-lomiri-connectivity (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make[1]: *** [debian/rules:31: override_dh_missing] Error 25

Bug#1021164: lomiri-indicator-network: binary-any FTBFS

[Adrian Bunk]

Source: lomiri-indicator-network
Version: 1.0.0~git20220718.2ca3619-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=lomiri-indicator-network&ver=1.0.0~git20220718.2ca3619-2

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
# drop upstart files
rm -Rfv debian/tmp/usr/share/upstart/
removed 
'debian/tmp/usr/share/upstart/xdg/autostart/lomiri-indicator-network.desktop'
removed directory 'debian/tmp/usr/share/upstart/xdg/autostart'
removed directory 'debian/tmp/usr/share/upstart/xdg'
removed 
'debian/tmp/usr/share/upstart/systemd-session/upstart/lomiri-indicator-network-secret-agent.override'
removed 
'debian/tmp/usr/share/upstart/systemd-session/upstart/lomiri-indicator-network.override'
removed directory 'debian/tmp/usr/share/upstart/systemd-session/upstart'
removed directory 'debian/tmp/usr/share/upstart/systemd-session'
removed 
'debian/tmp/usr/share/upstart/sessions/lomiri-indicator-network-secret-agent.conf'
removed 'debian/tmp/usr/share/upstart/sessions/lomiri-indicator-network.conf'
removed directory 'debian/tmp/usr/share/upstart/sessions'
removed directory 'debian/tmp/usr/share/upstart/'
# empty directory
rmdir debian/tmp/usr/share/doc/lomiri-connectivity-doc/qml/html/images/
dh_install
dh_install: warning: Cannot find (any matches for) 
"usr/share/ayatana/indicators/com.lomiri.indicator.network" (tried in ., 
debian/tmp)

dh_install: warning: lomiri-indicator-network missing files: 
usr/share/ayatana/indicators/com.lomiri.indicator.network
dh_install: warning: Cannot find (any matches for) 
"usr/lib/*/lomiri-indicator-network/*" (tried in ., debian/tmp)

dh_install: warning: lomiri-indicator-network missing files: 
usr/lib/*/lomiri-indicator-network/*
dh_install: error: missing files, aborting
make[1]: *** [debian/rules:28: override_dh_install] Error 25

Bug#1021047: gwave handled

[Tommi Höynälänmaa]

Control: tags -1 - moreinfo

Package gwave shall be removed, too. See

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021161

--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer

Bug#1021165: armhf: floatn-common.h:214:9: error: multiple types in one declaration

[Mathieu Malaterre]

Source: gcc-snapshot
Version: 1:20220920-1
Severity: grave

Per original reference:

--- Comment #1 from Andrew Pinski  ---
Is this a packaging issue?
> ignoring nonexistent directory 
> "/usr/lib/gcc-snapshot/lib/gcc/arm-linux-gnueabihf/13/include-fixed/arm-linux-gnueabihf"
ignoring nonexistent directory
"/usr/lib/gcc-snapshot/lib/gcc/arm-linux-gnueabihf/13/include-fixed"

Gcc 13 requires some (older) glibc headers to be fixed up .

See:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128

Bug#1021161: More information

[Tommi Höynälänmaa]

See

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991358

--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer

Bug#1021166: texlive-fonts-extra: sourceserifpro doesn't work with xeLaTeX

[Matthew Vernon]

Package: texlive-fonts-extra
Version: 2020.20210202-3
Severity: important
X-Debbugs-Cc: mver...@wikimedia.org

Hi,

The sourceserifpro package doesn't work properly with XeLaTeX - if I
compile the example document from the LaTeX font catalogue (
https://tug.org/FontCatalogue/sourceserifproregular/ ) with XeLaTeX, I
get computer modern rather than source serif pro.

Output includes:

LaTeX Font Warning: Font shape `T1/SourceSerifPro(0)/m/n' undefined
(Font)  using `T1/cmr/m/n' instead on input line 112.

(and also this, but this is the wrong flavour of source serif rather
than completely the wrong font):

LaTeX Font Warning: Font shape `T1/SourceSerifPro(0)/b/n' undefined
(Font)  using `T1/SourceSerifPro(0)/m/n' instead on input line 26.

It works fine with pdflatex.

I attach the xelatex-compiled version.

Thanks,

Matthew

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

https://tug.org/FontCatalogue/sourceserifproregular/sourceserifproregular.tex

##
other files

##
 List of ls-R files

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 10  2022 /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 3491 Sep 30 21:01 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Feb 12  2021 mktex.cnf
-rw-r--r-- 1 root root 475 Feb 10  2022 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Kernel: Linux 5.10.0-7-amd64 (SMP w/16 CPU threads)
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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages texlive-fonts-extra depends on:
ii  tex-common6.16
ii  texlive-base  2020.20210202-3

Versions of packages texlive-fonts-extra recommends:
ii  fonts-adf-accanthis0.20190904-2
ii  fonts-adf-berenis  0.20190904-2
ii  fonts-adf-gillius  0.20190904-2
ii  fonts-adf-universalis  0.20190904-2
ii  fonts-cabin1.5-3
ii  fonts-cantarell0.111-3
ii  fonts-comfortaa3.001-3
ii  fonts-croscore 20201225-1
ii  fonts-crosextra-caladea20130214-2.1
ii  fonts-crosextra-carlito20130920-1.1
ii  fonts-dejavu-core  2.37-2
ii  fonts-dejavu-extra 2.37-2
ii  fonts-ebgaramond   0.016-4
ii  fonts-ebgaramond-extra 0.016-4
ii  fonts-font-awesome 5.0.10+really4.7.0~dfsg-4.1
ii  fonts-freefont-otf 20120503-10
ii  fonts-freefont-ttf 20120503-10
ii  fonts-gfs-artemisia1.1-6
ii  fonts-gfs-complutum1.1-7
ii  fonts-gfs-didot 

Bug#1021167: fix building glibc on arc

[Matthias Klose]

Package: src:glibc
Version: 2.35-1
Severity: important
Tags: sid bookworm patch

Please fix building glibc on arc, both for 2.35 and 2.36.
--- a/debian/rules.d/control.mk
+++ b/debian/rules.d/control.mk
@@ -1,7 +1,7 @@
 libc_packages := libc6 libc6.1 libc0.1 libc0.3
 libc0_1_archs := kfreebsd-amd64 kfreebsd-i386
 libc0_3_archs := hurd-i386
-libc6_archs   := amd64 arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el \
+libc6_archs   := amd64 arc arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el \
  mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 \
  sparc sparc64 s390x sh3 sh4 x32
 libc6_1_archs := alpha ia64
--- a/debian/control
+++ b/debian/control
@@ -158,7 +158,7 @@
  slow services like LDAP, NIS or NIS+.
 
 Package: libc6
-Architecture: amd64 arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
+Architecture: amd64 arc arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
 Section: libs
 Priority: optional
 Multi-Arch: same
@@ -190,7 +190,7 @@
  and the standard math library, as well as many others.
 
 Package: libc6-dev
-Architecture: amd64 arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
+Architecture: amd64 arc arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
 Section: libdevel
 Priority: optional
 Multi-Arch: same
@@ -205,7 +205,7 @@
  and link programs which use the standard C library.
 
 Package: libc6-dbg
-Architecture: amd64 arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
+Architecture: amd64 arc arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
 Section: debug
 Priority: optional
 Multi-Arch: same
@@ -218,7 +218,7 @@
 
 Package: libc6-udeb
 Package-Type: udeb
-Architecture: amd64 arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
+Architecture: amd64 arc arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc ppc64 ppc64el riscv64 sparc sparc64 s390x sh3 sh4 x32
 Section: debian-installer
 Priority: optional
 Provides: libc6, libc-udeb, libnss-dns-udeb, libnss-files-udeb

Bug#1021165: Gcc 13 requires some (older) glibc headers to be fixed up .

[Mathieu Malaterre]

For reference:

malat@amdahl /tmp % apt-cache policy libc6-dev
libc6-dev:
  Installed: 2.35-1
  Candidate: 2.35-1
  Version table:
 *** 2.35-1 500
500 https://deb.debian.org/debian sid/main armhf Packages
100 /var/lib/dpkg/status

Bug#1021168: libgbm1: Extra \$ in libgbm.so.1.0.0

[Erik Larsson]

Package: libgbm1
Version: 20.3.5-1
Severity: important
File: /usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0

Dear Maintainer,

When testing version 2019.1 of the Schrödinger suite we found a bug in 3 of the 
packages belonging to Mesa; libgbm1, libglx-mesa0 and libegl-mesa0 (reported as 
separat bugs)

We got the following error message

libGL error: MESA-LOADER: failed to open swrast: 
/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or 
directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast

The '\$' preceding '${ORIGIN}' does not seem right.

After running a script that checked all files in /lib, /lib64, /usr/lib and 
/usr/libexec
we found 3 files containing the string '\$${ORIGIN}/dri'.

/usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0 (from libgbm1/now 20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0 (from libglx-mesa0/now 
20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0.0.0 (from libegl-mesa0/now 
20.3.5-1 amd64)

The string is compiled inte the lib itself, it is not found in the ELF-header.

The easiest way to check if the bug is present is with

grep -a '\\\$\$\{ORIGIN\}/dri' 

We have tested a binary patch as follows:
cd /usr/lib/x86_64-linux-gnu
cp -p libgbm.so.1.0.0 libgbm.so.1.0.0.ORIG
cat libgbm.so.1.0.0.ORIG | sed -e 's/:\\$${ORIGIN}\/dri:/:\/:${ORIGIN}\/dri:/' 
> libgbm.so.1.0.0

(and corresponding to the files from the two other packages).
With that patchs we can start the Schrödinger suite without any errors. Other 
software that we have tried and that use Mesa also work without complaint after 
we patched.

The occurrence of $$ is found in the newer version 22.2.0-1 as well.


-- System Information:
Debian Release: 11.1
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-0.deb11.4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libgbm1:amd64 depends on:
ii  libc6   2.31-13+deb11u4
ii  libdrm2 2.4.104-1
ii  libexpat1   2.2.10-2+deb11u4
ii  libwayland-server0  1.18.0-2~exp1.1

libgbm1:amd64 recommends no packages.

libgbm1:amd64 suggests no packages.

-- no debconf information

Bug#1021169: libglx-mesa0: Extra \$ in libGLX_mesa.so.0.0.0

[Erik Larsson]

Package: libglx-mesa0
Version: 20.3.5-1
Severity: important
File: /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0

Dear Maintainer,

When testing version 2019.1 of the Schrödinger suite we found a bug in 3 of the 
packages belonging to Mesa; libgbm1, libglx-mesa0 and libegl-mesa0 (reported as 
separat bugs)

We got the following error message

libGL error: MESA-LOADER: failed to open swrast: 
/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or 
directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast

The '\$' preceding '${ORIGIN}' does not seem right.

After running a script that checked all files in /lib, /lib64, /usr/lib and 
/usr/libexec
we found 3 files containing the string '\$${ORIGIN}/dri'.

/usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0 (from libgbm1/now 20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0 (from libglx-mesa0/now 
20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0.0.0 (from libegl-mesa0/now 
20.3.5-1 amd64)

The string is compiled inte the lib itself, it is not found in the ELF-header.

The easiest way to check if the bug is present is with

grep -a '\\\$\$\{ORIGIN\}/dri' 

We have tested a binary patch as follows:
cd /usr/lib/x86_64-linux-gnu
cp -p libGLX_mesa.so.0.0.0 libGLX_mesa.so.0.0.0.ORIG
cat libGLX_mesa.so.0.0.0.ORIG | sed -e 
's/:\\$${ORIGIN}\/dri:/:\/:${ORIGIN}\/dri:/' > libGLX_mesa.so.0.0.0

(and corresponding to the files from the two other packages).
With that patchs we can start the Schrödinger suite without any errors. Other 
software that we have tried and that use Mesa also work without complaint after 
we patched.

The occurrence of $$ is found in the newer version 22.2.0-1 as well.


-- System Information:
Debian Release: 11.1
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-0.deb11.4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libgbm1:amd64 depends on:
ii  libc6   2.31-13+deb11u4
ii  libdrm2 2.4.104-1
ii  libexpat1   2.2.10-2+deb11u4
ii  libwayland-server0  1.18.0-2~exp1.1

libgbm1:amd64 recommends no packages.

libgbm1:amd64 suggests no packages.

-- no debconf information

Bug#1021001: mirror-prg.webglobe.com: out-of-date

[Jiří Luňáček]

Hello.

We had some issues with storage provider software.
It should be fixed now and the mirror is in sync.

Thank you for the report.

Jiri Lunacek


> On 30. 9. 2022, at 12:36, Julien Cristau  wrote:
> 
> Package: mirrors
> User: mirr...@packages.debian.org
> Usertags: mirror-problem
> X-Debbugs-Cc: Jiri Lunacek 
> 
> Hi,
> 
> I was checking some things in the Debian mirror universe and noticed
> a problem with your mirror:
> 
> o It seems your mirror is not up to date, having last successfully
>  updated on Tue, 13 Sep 2022 14:10:44 +
> 
> It looks like there were later sync attempts but they seem to be failing
> (at least the trace file is not getting updated).  Can you check on it
> and report back?
> 
> Thanks,
> Julien - Debian mirrors team

Bug#1021170: libegl-mesa0: Extra \$ in libEGL_mesa.so.0.0.0

[Erik Larsson]

Package: libegl-mesa0
Version: 20.3.5-1
Severity: important
File: /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0.0.0

Dear Maintainer,

When testing version 2019.1 of the Schrödinger suite we found a bug in 3 of the 
packages belonging to Mesa; libgbm1, libglx-mesa0 and libegl-mesa0 (reported as 
separat bugs)

We got the following error message

libGL error: MESA-LOADER: failed to open swrast: 
/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or 
directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast

The '\$' preceding '${ORIGIN}' does not seem right.

After running a script that checked all files in /lib, /lib64, /usr/lib and 
/usr/libexec
we found 3 files containing the string '\$${ORIGIN}/dri'.

/usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0 (from libgbm1/now 20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0 (from libglx-mesa0/now 
20.3.5-1 amd64)
/usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0.0.0 (from libegl-mesa0/now 
20.3.5-1 amd64)

The string is compiled inte the lib itself, it is not found in the ELF-header.

The easiest way to check if the bug is present is with

grep -a '\\\$\$\{ORIGIN\}/dri' 

We have tested a binary patch as follows:
cd /usr/lib/x86_64-linux-gnu
cp -p libEGL_mesa.so.0.0.0 libEGL_mesa.so.0.0.0.ORIG
cat libEGL_mesa.so.0.0.0.ORIG | sed -e 
's/:\\$${ORIGIN}\/dri:/:\/:${ORIGIN}\/dri:/' > libEGL_mesa.so.0.0.0

(and corresponding to the files from the two other packages).
With that patchs we can start the Schrödinger suite without any errors. Other 
software that we have tried and that use Mesa also work without complaint after 
we patched.

The occurrence of $$ is found in the newer version 22.2.0-1 as well.


-- System Information:
Debian Release: 11.1
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-0.deb11.4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libgbm1:amd64 depends on:
ii  libc6   2.31-13+deb11u4
ii  libdrm2 2.4.104-1
ii  libexpat1   2.2.10-2+deb11u4
ii  libwayland-server0  1.18.0-2~exp1.1

libgbm1:amd64 recommends no packages.

libgbm1:amd64 suggests no packages.

-- no debconf information

Bug#1020945: thunderbird uses 100 % of CPU without responding

[Norbert Schulz]

Hello Carsten,

thanks for your help.

The problem for hanging of thunderbird was an old version of the 
calendarserver (3.2+dfsg-4+deb7u3) on the server which thunderbird wants 
to connect. The version of thunderbird before 102.3 did not lead to any 
problem.


I shut down the old calendarserver and thunderbird was working without 
problems. Now I could delete the calendar from thunderbird. I installed 
davical instead.


The only add-on I hat installed was Tbsync. The latest version of Tbsync 
does not work with thunderbird 102.3.



Norbert

Am 29.09.22 um 12:17 schrieb Carsten Schoenert:

Hello Norbert

Am 29.09.22 um 10:42 schrieb Norbert Schulz:

Dear Maintainer,

after upgrading thunderbird and starting it, it uses 100 % of a CPU 
without responding and does not stop doing something regarding
a timeout. What does thunderbird during this time? I can stop 
thunderbird only by killing it. Is there any log to see
what thunderbird does? How can I stop thunderbird doing things after 
starting?


We collected some hopefully useful steps and points within the Debian 
Wiki to narrow down problems.


https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues

If you look at similar bug reports you will see that in most of the 
such cases one  or more Add-on was making trouble so I think that can 
be the root of your issue too.

Bug#965502: dvi2ps: NMU 5.1j-1.5

[Bastian Germann]

Hi,

I have just uploaded a NMU which fixes this.
debdiff is attached.

Thanks,
Bastiandiff -Nru dvi2ps-5.1j/debian/changelog dvi2ps-5.1j/debian/changelog
--- dvi2ps-5.1j/debian/changelog2021-02-05 16:21:48.0 +0100
+++ dvi2ps-5.1j/debian/changelog2022-10-03 11:32:23.0 +0200
@@ -1,3 +1,10 @@
+dvi2ps (5.1j-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update to debhelper-compat 10 (Closes: #965502).
+
+ -- Bastian Germann   Mon, 03 Oct 2022 09:32:23 +
+
 dvi2ps (5.1j-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dvi2ps-5.1j/debian/compat dvi2ps-5.1j/debian/compat
--- dvi2ps-5.1j/debian/compat   2019-02-17 13:29:43.0 +0100
+++ dvi2ps-5.1j/debian/compat   1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-5
diff -Nru dvi2ps-5.1j/debian/control dvi2ps-5.1j/debian/control
--- dvi2ps-5.1j/debian/control  2019-02-17 13:29:43.0 +0100
+++ dvi2ps-5.1j/debian/control  2022-10-03 11:31:10.0 +0200
@@ -2,8 +2,8 @@
 Section: tex
 Priority: optional
 Maintainer: OHURA Makoto 
-Build-Depends: debhelper (>= 5.0.0), dh-autoreconf, nkf, libkpathsea-dev, 
vflib3-dev,
- libfreetype6-dev, autotools-dev, pkg-config, po-debconf
+Build-Depends: debhelper-compat (= 10), nkf, libkpathsea-dev, vflib3-dev,
+ libfreetype-dev, pkg-config, po-debconf
 Standards-Version: 3.8.4
 
 Package: dvi2ps

Bug#1021171: RFS: simple-scan/42.5-2 -- Simple Scanning Utility

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "simple-scan":

   Package name : simple-scan
   Version  : 42.5-2
   Upstream contact : Robert Ancell 
   URL  : https://gitlab.gnome.org/GNOME/simple-scan
   License  : GPL-3+
   Vcs  : https://jff.email/cgit/simple-scan.git
   Section  : gnome

The source builds the following binary packages:

  simple-scan - Simple Scanning Utility

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

  https://mentors.debian.net/package/simple-scan/

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

 dget -x 
https://mentors.debian.net/debian/pool/main/s/simple-scan/simple-scan_42.5-2.dsc

of from 

 git https://jff.email/cgit/simple-scan.git?h=release%2Fdebian%2F42.5-2



Changes since the last upload:

 simple-scan (42.5-2) unstable; urgency=medium
 .
   * debian/control: Bump Build-Depends libhandy-1-dev to >= 1.6.0
 (Closes:# 1021160).
   * Declare compliance with Debian Policy 4.6.0.1 (No changes needed).


CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#1020532: crash text ...

[Dr. Nikolaus Klepp]

Ok, after reinstallng gimp I  get the same bug, but this time with this crash 
text:




```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.1.0 (Debian 12.1.0-8) 

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.74.0 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.10 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Speicherzugriffsfehler

Stack trace:
```

# Stack traces obtained from PID 11067 - Thread 11067 #

[New LWP 11068]
[New LWP 11069]
[New LWP 11070]
[New LWP 11071]
[New LWP 11072]
[New LWP 11073]
[New LWP 11074]
[New LWP 11075]
[New LWP 11076]
[New LWP 11077]
[New LWP 11078]
[New LWP 11079]
[New LWP 11080]
[New LWP 11081]
[New LWP 11162]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7fff1aa79e70, fd=16) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7f4ce1a5d380 (LWP 11067) "gimp"__GI___libc_read 
(nbytes=256, buf=0x7fff1aa79e70, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f4ce0f22640 (LWP 11068) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f4ce0721640 (LWP 11069) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f4cdff20640 (LWP 11070) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f4cdf71f640 (LWP 11071) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f4cdef1e640 (LWP 11072) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f4cde71d640 (LWP 11073) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f4cddf1c640 (LWP 11074) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f4cdd71b640 (LWP 11075) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f4cdcf1a640 (LWP 11076) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f4cb640 (LWP 11077) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7f4cbf7fe640 (LWP 11078) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7f4cbe9ff640 (LWP 11079) "gmain"   0x7f4ce22fda3f in 
__GI___poll (fds=0x5623a95d3140, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  14   Thread 0x7f4cbe1fe640 (LWP 11080) "gdbus"   0x7f4ce22fda3f in 
__GI___poll (fds=0x5623a95e7510, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  15   Thread 0x7f4c9d3ff640 (LWP 11081) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  16   Thread 0x7f4c927fc640 (LWP 11162) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 16 (Thread

Bug#1021172: bullseye-pu: package x2gothinclient/1.5.0.1-6+deb11u1

[Mike Gabriel]

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

[ Reason ]
The x2gothinclient-minidesktop requires lightdm, but should not
pull-in any of the lightdm-greeters available in Debian.

With this update, x2gothinclient-minidesktop will provide lightdm-greeter
functionality package-dependency wise and it will be possible to cleanly
provide an x2gothinclient chroot based on Debian.

[ Impact ]
The user cannot remove the lightdm-gtk-greeter (or any other greeter
frontend) and LightDM config files from any of the greeter packages will
interfere with the way x2gothinclient-minidesktop is supposed to work
(i.e. auto-login into the x2gothinclient user session without greeter
dialog.

[ Tests ]
Manual tests on Debian Edu based X2Go Thinclient Environment.

Manual setup of an X2Go Thinclient via x2gothinclient-create command.

Also manual package installation tests in a chroot.

[ Risks ]
None.

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

[ Changes ]

```
+  * debian/control:
++ Add 'Provides: lightdm-greeter' to x2gothinclient-minidesktop bin:pkg.
+  The X2Go TCE minidesktop implementation utilizes lightdm via its 
autologin
+  feature. (Closes: #1003418).
```

[ Other info ]
diff -Nru x2gothinclient-1.5.0.1/debian/changelog 
x2gothinclient-1.5.0.1/debian/changelog
--- x2gothinclient-1.5.0.1/debian/changelog 2021-02-05 12:27:47.0 
+0100
+++ x2gothinclient-1.5.0.1/debian/changelog 2022-01-10 07:33:28.0 
+0100
@@ -1,3 +1,12 @@
+x2gothinclient (1.5.0.1-6+deb11u1) bullseye; urgency=medium
+
+  * debian/control:
++ Add 'Provides: lightdm-greeter' to x2gothinclient-minidesktop bin:pkg.
+ The X2Go TCE minidesktop implementation utilizes lightdm via its autologin
+ feature. (Closes: #1003418).
+
+ -- Mike Gabriel   Mon, 10 Jan 2022 07:33:28 +0100
+
 x2gothinclient (1.5.0.1-6) unstable; urgency=medium
 
   * debian/patches:
diff -Nru x2gothinclient-1.5.0.1/debian/control 
x2gothinclient-1.5.0.1/debian/control
--- x2gothinclient-1.5.0.1/debian/control   2020-04-18 23:57:11.0 
+0200
+++ x2gothinclient-1.5.0.1/debian/control   2022-01-10 07:33:11.0 
+0100
@@ -138,6 +138,8 @@
  x2gothinclient-minidesktop-mate,
 Conflicts:
  x2gothinclient,
+Provides:
+ lightdm-greeter,
 Description: Minimal desktop for X2Go Thin Client chroot (based on MATE)
  X2Go is a server based computing environment with
 - session resuming

Bug#1021173: RM: gourmet -- NVIU; Package renamed gourmand

[Christian Marillat]

Package: ftp.debian.org
Severity: normal

Hi,

,
| I'm not sure about the NVIU tag
`

gourmet has been renamed gourmand.

I've added a transition package in gourmand 1.1.0+rc3 so gourmet
*source* can now be removed from unstable.

Christian

Bug#1008735: base-files: /etc/os-release should contain VERSION variables for testing and unstable

[Sedat Dilek]

[ CC linux-kbuild folks (see [0] ]

Hi,

I am using Debian/unstable AMD64 and doing Linux-kernel upstream
development and testing.

People using bindeb-pkg (mkdebian) from Linux-kernel sources
(scripts/packages) to build and test their selfmade Debian kernels get
a now a "n/a" for distribution.

Background (see [1]):

[ scripts/package/mkdebian ]

# Try to determine distribution
if [ -n "$KDEB_CHANGELOG_DIST" ]; then
distribution=$KDEB_CHANGELOG_DIST
# In some cases lsb_release returns the codename as n/a, which breaks
dpkg-parsechangelog
elif distribution=$(lsb_release -cs 2>/dev/null) && [ -n
"$distribution" ] && [ "$distribution" != "n/a" ]; then
: # nothing to do in this case
else
distribution="unstable"
echo >&2 "Using default distribution of 'unstable' in the changelog"
echo >&2 "Install lsb-release or set \$KDEB_CHANGELOG_DIST explicitly"
fi

Personally, I set hardcoded in my kernel build-script as a workaround:

distribution="bookworm"

Gioele suggested me to enrich /etc/os-release with:

VERSION_ID=unstable <--- XXX: I prefer sid because of PRETTY_NAME and
it's shorter
VERSION_CODENAME=bookworm

In the end the file looks like:

PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
VERSION_ID=sid
VERSION_CODENAME=bookworm
HOME_URL="https://www.debian.org/";
SUPPORT_URL="https://www.debian.org/support";
BUG_REPORT_URL="https://bugs.debian.org/";

...and this seems to work:

# lsb_release -cs
No LSB modules are available.
bookworm

Please, provide a solution not to break workflows that were successful
for years.

Thanks.

Best regards,
-Sedat-

[0] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n11005
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/package/mkdebian#n123

Bug#1021174: unrar-free: non-source file in Debian tests

[Bastian Germann]

Source: unrar-free
Version: 1:0.0.2-0.1
Severity: important

unrar-free contains debian/tests/0001-smoketest which has a base64-encoded rar
file with a clam.exe in it that is not built from source.
Please replace that smoke test with a rar file that is more appropriate or drop 
it.

Bug#1016811: libwebkit2gtk-4.0-37: bullseye backport crashes a lot on arm64

[Alberto Garcia]

On Mon, Oct 03, 2022 at 01:07:09PM +0900, Dominique MARTINET wrote:
> Since gcc build appears to fix the issue I think that's the way to
> go for bullseye, at least until we understand where that makes a
> difference...

gcc is the default compiler that we use for WebKit in Debian, the only
reason why it wasn't being used in bullseye in this case it's because
of this bug:

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008098

I narrowed this one down as much as possible, we should probably
report it upstream but I didn't have the chance to do it yet.

Berto

Bug#1021175: calibre - content server only listen on IPv4

[Bastian Blank]

Package: calibre
Version: 6.6.1+dfsg-2
Severity: important
Tags: ipv6

The embedded only listens on 0.0.0.0, aka AF_INET, aka IPv4.  This makes
the content server quite unusable in the current internet, where IPv4
connectivity gets sparingly, either by CG-NAT used by the provider or by
IPv6-only environments.

Bastian

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

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

Versions of packages calibre depends on:
ii  calibre-bin6.6.1+dfsg-2
ii  fonts-liberation2  2.1.5-1
ii  libjpeg-turbo-progs1:2.1.2-1+b1
ii  libjxr-tools   1.2~git20170615.f752187-5
ii  libqt6webenginecore6-bin   6.3.1+dfsg2-13
ii  optipng0.7.7-2+b1
ii  poppler-utils  22.08.0-2.1
ii  python33.10.6-1
ii  python3-apsw   3.39.2.0-1
ii  python3-bs44.11.1-1
ii  python3-chm0.8.6-3+b2
ii  python3-css-parser 1.0.7-1
ii  python3-cssselect  1.1.0+ds-3
ii  python3-dateutil   2.8.1-6
ii  python3-feedparser 6.0.8-2
ii  python3-html2text  2020.1.16-2
ii  python3-html5-parser   0.4.10-5+b1
ii  python3-html5lib   1.1-3
ii  python3-jeepney0.8.0-1
ii  python3-lxml   4.9.1-1+b1
ii  python3-markdown   3.4.1-1
ii  python3-mechanize  1:0.4.8+pypi-4
ii  python3-msgpack1.0.3-1+b1
ii  python3-netifaces  0.11.0-1+b2
ii  python3-pil9.2.0-1+b1
ii  python3-pkg-resources  59.6.0-1.2
ii  python3-py7zr  0.11.3+dfsg-4
ii  python3-pycryptodome   3.11.0+dfsg1-3+b1
ii  python3-pygments   2.12.0+dfsg-2
ii  python3-pyparsing  3.0.7-2
ii  python3-pyqt6  6.3.1-1+b1
ii  python3-pyqt6.qtquick  6.3.1-1+b1
ii  python3-pyqt6.qtsvg6.3.1-1+b1
ii  python3-pyqt6.qtwebengine  6.3.1-2
ii  python3-pyqt6.sip  13.4.0-1+b1
ii  python3-regex  0.1.2020-1+b1
ii  python3-routes 2.5.1-3
ii  python3-speechd0.11.3-1
ii  python3-zeroconf   0.39.1-2
ii  python3.10 3.10.7-1
ii  qt6-qpa-plugins6.3.1+dfsg-9
ii  xdg-utils  1.1.3-4.1

Versions of packages calibre recommends:
ii  python3-dnspython  2.2.1-2
pn  python3-ipython
pn  qt6-wayland
ii  udisks22.9.4-3

Versions of packages calibre suggests:
ii  python3-openssl   21.0.0-1
pn  python3-unrardll  

-- no debconf information

Bug#991462: Please update etcd to 3.5.5

[Thomas Goirand]

Hi,

This issue is becoming more and more of a problem because upstream 
changed its path, and now rebuilding other projects is very annoying: 
one has to tweak/patch the imports. Also, even with such patch, some 
objects are simply not available in the current version.


Cheers,

Thomas Goirand (zigo)

Bug#1014810: owncloud-client: CVE-2021-44537

[Pierre-Elliott Bécue]

Hi,

Le mardi 12 juillet 2022 à 12:10:27+0200, Moritz Mühlenhoff a écrit :
> Source: owncloud-client
> X-Debbugs-CC: t...@security.debian.org
> Severity: important
> Tags: security
> 
> Hi,
> 
> The following vulnerability was published for owncloud-client.
> 
> CVE-2021-44537[0]:
> | ownCloud owncloud/client before 2.9.2 allows Resource Injection by a
> | server into the desktop client via a URL, leading to remote code
> | execution.
> 
> https://owncloud.com/security-advisories/cve-2021-44537/
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2021-44537
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44537
> 
> Please adjust the affected versions in the BTS as needed.

Sorry for not including this bug report and CVE in my 2.11.0.8354
release, I had it in mind in July and things fell off because of summer
holiday and then I forgot about it.

That being said, the 2.11.0.8354 version is not vulnerable which is at
least a good thing.

I added a fixed-in entry on the bug, if I can do something else to make
sure the security tracker is happy, please do tell.

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for principles than to live up to them.

Bug#1021176: bullseye-pu: package openvswitch/2.15.0+ds1-2+deb11u1

[Thomas Goirand]

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

Hi,

It appears that the command ovs-dpctl-top was wrongly patched
in the Bullseye version of OVS. Removing the wrong hunks fixes it.

[ Reason ]
The bug is due to me, who patched all to make OVS working under
Python 3. The rest of the patch is correct, BTW.

[ Impact ]
Calling ovs-dpctl-top just fails.

[ Tests ]
We tested reverting the wrong hunks, and it fixed it for us.

[ Risks ]
No other part of OVS are affected, and there's unit tests in OVS,
so risks are really minimum. Also, this is only a userland debug
tool, so nothing critical to a functionning OVS.

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

[ Changes ]
Only removing the 3 wrong hunks of the py3-compat.patch.

Please approve the upload before the next Bullseye point release.

Cheers,

Thomas Goirand (zigo)
diff -Nru openvswitch-2.15.0+ds1/debian/changelog 
openvswitch-2.15.0+ds1/debian/changelog
--- openvswitch-2.15.0+ds1/debian/changelog 2022-01-03 13:53:38.0 
+0100
+++ openvswitch-2.15.0+ds1/debian/changelog 2022-10-03 12:59:27.0 
+0200
@@ -1,3 +1,9 @@
+openvswitch (2.15.0+ds1-2+deb11u2) bullseye; urgency=medium
+
+  * Fix ovs-dpctl-top by removing 3 wrong hunks in py3-compat.patch.
+
+ -- Thomas Goirand   Mon, 03 Oct 2022 12:59:27 +0200
+
 openvswitch (2.15.0+ds1-2+deb11u1) bullseye; urgency=medium
 
   * CVE-2021-36980: use-after-free in decode_NXAST_RAW_ENCAPAdd. Add upstream
diff -Nru openvswitch-2.15.0+ds1/debian/patches/py3-compat.patch 
openvswitch-2.15.0+ds1/debian/patches/py3-compat.patch
--- openvswitch-2.15.0+ds1/debian/patches/py3-compat.patch  2022-01-03 
13:53:38.0 +0100
+++ openvswitch-2.15.0+ds1/debian/patches/py3-compat.patch  2022-10-03 
12:59:27.0 +0200
@@ -147,33 +147,6 @@
  import sys
  import os
  try:
-@@ -419,7 +421,7 @@ def flow_line_iter(line):
- rc.append(element)
- element = ""
- else:
--element += ch
-+element += str(ch)
- 
- if (paren_count):
- raise ValueError(line)
-@@ -468,7 +470,7 @@ def flow_line_split(line):
- 
- """
- 
--results = re.split(', ', line)
-+results = re.split(b', ', line)
- 
- (field, stats, action) = (results[0], results[1:-1], results[-1])
- 
-@@ -963,7 +965,7 @@ class FlowDB:
- if not isinstance(line, str):
-line = str(line)
- 
--line = line.rstrip("\n")
-+line = line.rstrip(b"\n")
- (fields, stats, _) = flow_line_split(line)
- 
- try:
 --- a/utilities/ovs-l3ping.in
 +++ b/utilities/ovs-l3ping.in
 @@ -18,8 +18,10 @@ opening holes in the firewall for the XM

Bug#1021177: RM: python-scandir -- RoM; obsolete; Python2-removal

[julien . puydt]

Package: ftp.debian.org
X-Debbugs-CC: debian-pyt...@lists.debian.org

I packaged this years ago when nice features of Python 3 needed a
backport to Python 2 ; those days are gone and we're moving away from
Python 2 with the next release of Debian, so this package should be
removed.

I checked with dak and it's ok to remove it:
$ ssh mirror.ftp-master.debian.org "dak rm -Rn python-scandir"
Will remove the following packages from unstable:

pypy-scandir |   1.10.0-4 | amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
python-scandir |   1.10.0-4 | source

Maintainer: Debian Python Team 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.

Cheers,

J.Puydt

Bug#1012250: gscan2pdf: flaky autopkgtest: regularly times out

[Jeff]

This morning, I see that for s390x in testing, there was a timeout and 
failure (both in 380_cancel_user_defined_with_pids), as well as two passes:


https://ci.debian.net/packages/g/gscan2pdf/testing/s390x/

armel had a failure that was unrelated to gscan2pdf:

https://ci.debian.net/data/autopkgtest/testing/armel/g/gscan2pdf/26567445/log.gz

I also see that all the other architectures have passes, but this is not 
reflected by the summary page:


https://ci.debian.net/packages/g/gscan2pdf/

Any idea why?

Given that gscan2pdf is a desktop app, I assume there are no users on 
s390x. Hence, I'm not sure of the value of debugging on s390x. According to:


https://www.debian.org/doc/debian-policy/ch-source.html

DEB_HOST_ARCH and DEB_TARGET_ARCH should be set. I'm tempted to test for 
s390x in the test target in debian/rules and skip accordingly. Objections?


Given that the packages in stable are, well, stable, and I made no 
changes to those parts of gscan2pdf, I wonder what happened in the rest 
of the environment between stable and testing. I'd be interested to 
confirm this by pushing the stable version of gscan2pdf through testing 
s390x a couple of times.


Regards

Jeff


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021178: gnome-software: does not properly render package description (-tags)

[Debian/GNU]

Package: gnome-software
Version: 43.0-1
Severity: minor

Dear Maintainer,


I recently tried out gnome-software, and noticed that there's a glitch with
rendering emphasis-tags.

E.g. the "puredata-gui" package contains an org.puredata.pd-gui.metainfo.xml
file, which has the following paragraph in its description:

```

 Think of Pd as a Modular Synthesizer that is also a programming
language.

```

for whatever reasons, gnome-software renders this paragraph without spaces
around the 'Modular Synthesizer' (see attached image).


other HTML-entities, like '"' leave spaces intact.


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

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

Versions of packages gnome-software depends on:
ii  appstream0.15.5-1
ii  apt-config-icons 0.15.5-1
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  gnome-software-common43.0-1
ii  gsettings-desktop-schemas43.0-1
ii  libadwaita-1-0   1.2.0-1
ii  libappstream40.15.5-1
ii  libc62.35-1
ii  libcairo21.16.0-6
iu  libfwupd21.8.5-1
it  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
iu  libglib2.0-0 2.74.0-2
ii  libgtk-4-1   4.8.1+ds-1
ii  libgtk3-perl 0.038-1
ii  libgudev-1.0-0   237-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmalcontent-0-00.11.0-3
ii  libpackagekit-glib2-18   1.2.5-3
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpolkit-gobject-1-00.105-33
ii  libsoup2.4-1 2.74.2-3
ii  libxmlb2 0.3.8-1
ii  packagekit   1.2.5-3
ii  software-properties-gtk  0.96.20.2-2.1

Versions of packages gnome-software recommends:
iu  fwupd  1.8.5-1

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-snap 

-- no debconf information

Bug#1021179: pipewire-pulse: KDE Plasma+ALC4080 onboard card: unable to select working profile

[Maurizio Avogadro]

Package: pipewire-pulse
Version: 0.3.59-1
Severity: important

Dear Maintainer,

while within Gnome I can make the audio subsystem work by manually selecting
the "Play HiFi quality Music" profile (defined in ALSA UCM) of my onboard
Realtek ALC4080 USB audio card, in KDE Plasma its only available profile is
"off", which means no sound output is possible. This started to be a problem
since pipewire-pulse became a dependency of gnome-core.

For the HDMI audio device, which I don't use and I keep on its default "off"
profile, a working profile can instead be selected in both Gnome and KDE
Plasma: this makes me suspect I'm facing an issue that is specific to my sound
card, possibly having something to do with its UCM configuration.

Disabling and masking the pipewire user units and enabling back pulseaudio
solves the issue; the pipewire-pulse daemon aims to be a drop-in replacement
for pulseaudio.

The involved hardware is a MSI MAG X570S TORPEDO MAX mainboard with a Realtek
ALC4080 USB audio card onboard.

Thanks!


-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates'), (500, 'unstable'), 
(500, 'stable'), (500, 'oldstable'), (1, 'experimental')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.12-xanmod1-x64v2+amdnative (SMP w/16 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pipewire-pulse depends on:
ii init-system-helpers 1.65.2
ii pipewire 0.3.59-1

pipewire-pulse recommends no packages.

Versions of packages pipewire-pulse suggests:
ii libspa-0.2-bluetooth 0.3.59-1
ii pulseaudio-utils 16.1+dfsg1-2

-- debconf-show failed

Bug#1020532: gimp: text element crashes gimp

[Simon McVittie]

On Mon, 03 Oct 2022 at 11:43:47 +0200, Dr. Nikolaus Klepp wrote:
> Ok, after reinstallng gimp I  get the same bug, but this time with this crash 
> text:

You don't need to reinstall gimp, but you do need to make sure the
libglib2.0-0 package is version 2.74.0-2 or later. It should migrate to
testing today, but it might take a day or two for your mirror to catch up.

libglib2.0-0 version 2.74.0-1 has the bug that causes this crash, and
reporting it again is not going to get it fixed any sooner.

libglib2.0-0 version 2.74.0-2 is believed to have a fix for this crash.

smcv

Bug#1021180: usrmerge may break user-mode-linux rootfs

[Ritesh Raj Sarraf]

Package: usrmerge
Version: 31
Severity: normal
X-Debbugs-Cc: r...@debian.org


Hello,

I'm just filing it as a report here as I'm not sure if this qualifies as
a valida bug. Nevertheless it does break the user's system.


```
Setting up perl (5.34.0-5) ...
Setting up libfile-find-rule-perl (0.34-2) ...
Selecting previously unselected package usrmerge.
(Reading database ... 22180 files and directories currently installed.)
Preparing to unpack .../archives/usrmerge_32_all.deb ...
Unpacking usrmerge (32) ...
Setting up usrmerge (32) ...
sched: RT throttling activated
mv: cannot move '/lib/modules' to '/usr/lib/modules': Device or resource busy

FATAL ERROR:
mv --no-clobber /lib/modules /usr/lib/modules: rc=1

You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.

E: usrmerge failed.
dpkg: error processing package usrmerge (--configure):
 installed usrmerge package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 usrmerge
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

The below occurred inside a Debian Unstable rootfs running
user-mode-linux.

And the reason this fails is because:

```
root@uml:~# cat /etc/fstab
# UNCONFIGURED FSTAB FOR BASE SYSTEM
hostfs  /lib/moduleshostfs  /usr/lib/uml/modules0   0
hostfs  /var/tmp/Debian-Build/containershostfs  
/var/tmp/Debian-Build/containers0   0
/swapfile   swapswapdefaults0   0
/dev/ubda   /   ext4discard,errors=remount-ro   0   1
```


The uml kernel is a modular kernel. The bare boot is built as the
monolithic kernel and everything else as modules, which are then mounted
from the host to the UML guest.

Now, going forward, I can manually fix it by mounting to
/usr/lib/modules and arranging the symlink to the old location in the
guest, something that usrmerge is trying to do.

But I report it here only to keep parties aware and if/whether they have
a better detection and handling of this scenario.



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

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages usrmerge depends on:
ii  libfile-find-rule-perl  0.34-2
ii  perl5.34.0-5

usrmerge recommends no packages.

usrmerge suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US",
LC_ALL = (unset),
LC_TIME = "en_IO.UTF-8",
LANG = "en_IN.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_IN.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory

Bug#1021181: RFS: dvdauthor/0.7.2-2 [RC] -- create DVD-Video file system

[Marc Leeman]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : dvdauthor
   Version  : 0.7.2-2
   Upstream contact : Lawrence D'Oliveiro 
 * URL  : https://dvdauthor.sourceforge.net
 * License  : GPL-2+
 * Vcs  : https://salsa.debian.org/den_erpel/dvdauthor/
   Section  : otherosfs

The source builds the following binary packages:

  dvdauthor - create DVD-Video file system

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/d/dvdauthor/dvdauthor_0.7.2-2.dsc

Changes since the last upload:

 dvdauthor (0.7.2-2) unstable; urgency=medium
 .
   [ Hugh McMaster ]
   * dvdauthor changes
 .
   * debian: no html install
   * debian: add watch file
   * debian: improve copyright
   * debian: update standards version
   * debian: standardise debian/rules
   * debian: use pkg-config for libxml2 (Closes: #949098)
   * autotools: remove generated files
   * debian: fix lintian warning dep on cdbs
   * d/control: add 2nd e-mail for upload
   * d/control: update Vcs tags

Regards,

Bug#1016903: tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

[Mathieu Malaterre]

Control: affects -1 src:jpeg-xl

Just a wild guess:

* 
https://buildd.debian.org/status/fetch.php?pkg=jpeg-xl&arch=armhf&ver=0.7.0-2&stamp=1664702466&raw=0

Bug#1021182: xserver-xorg-video-vmware: FTBFS against GCC-12

[Nathan Pratta Teodosio]

Package: xserver-xorg-video-vmware
Version: 1:13.3.0-3build1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: nathan.teodo...@canonical.com

Dear Maintainer,

I'm forwarding the upstream patch to fix FTBFS against GCC-12.

It was already committed to Ubuntu via LP: #1991117[1].

[1]: https://launchpad.net/bugs/1991117
Author: Rudi Heitbaum 
From: Nathan Pratta Teodosio 
Origin: 
https://gitlab.freedesktop.org/xorg/driver/xf86-video-vmware/-/commit/77b8183b
Date: Sun, 8 May 2022 03:00:10 +
Subject: [PATCH] vmwgfx: fix missing array notation
Applied-Upstream: commit: 77b8183b

 Fixes error identified by gcc-12.1.0 compiler

make
  CC   libvmwgfx_la-vmwgfx_tex_video.lo
vmwgfx_tex_video.c: In function 'stop_video':
vmwgfx_tex_video.c:240:20: error: the comparison will always evaluate as 'true' 
for the address of 'yuv' will never be NULL [-Werror=address]
  240 |if (priv->yuv[i]) {
  |^~~~
---
 vmwgfx/vmwgfx_tex_video.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vmwgfx/vmwgfx_tex_video.c b/vmwgfx/vmwgfx_tex_video.c
index acc2b56..480a5f1 100644
--- a/vmwgfx/vmwgfx_tex_video.c
+++ b/vmwgfx/vmwgfx_tex_video.c
@@ -237,7 +237,7 @@ stop_video(ScrnInfoPtr pScrn, pointer data, Bool shutdown)
 
for (i=0; i<3; ++i) {
   for (j=0; j<2; ++j) {
-  if (priv->yuv[i]) {
+  if (priv->yuv[j][i]) {
   xa_surface_destroy(priv->yuv[j][i]);
   priv->yuv[j][i] = NULL;
   }

Bug#1012885: abseil: Patch

[Nathan Pratta Teodosio]

Source: abseil
Version: 0~20210324.2-4.
Followup-For: Bug #1012885
X-Debbugs-Cc: nathan.teodo...@canonical.com

Dear Maintainer,

I'm forwarding the from upstream patch to fix this issue.

Already committed to Ubuntu Kinetic (LP: #1991253[1])

[1]: https://launchpad.net/bugs/1991253
From: Derek Mauro 
Date: Wed, 15 Jun 2022 07:42:49 -0700
Subject: [PATCH] any_test: expand the any emplace bug suppression, since it
 has gotten worse in GCC 12
Applied-Upstream: commit: a184bab83ffcffc2aaac49a3900361158ab3890f

PiperOrigin-RevId: 455128070
Change-Id: Ia866e59d4e2e810aea16afe492d58013c5661a2b
---
 absl/types/any_test.cc | 33 +++--
 1 file changed, 15 insertions(+), 18 deletions(-)

diff --git a/absl/types/any_test.cc b/absl/types/any_test.cc
index 70e4ba22b1..d382b927c2 100644
--- a/absl/types/any_test.cc
+++ b/absl/types/any_test.cc
@@ -754,26 +754,23 @@ TEST(AnyTest, FailedCopy) {
 
 // Test the guarantees regarding exceptions in emplace.
 TEST(AnyTest, FailedEmplace) {
-  {
-BadCopyable bad;
-absl::any target;
-ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
-  }
+  BadCopyable bad;
+  absl::any target;
+  ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
+}
 
-  {
-BadCopyable bad;
-absl::any target(absl::in_place_type);
-ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
-#if defined(ABSL_USES_STD_ANY) && defined(__GLIBCXX__)
-// libstdc++ std::any::emplace() implementation (as of 7.2) has a bug: if 
an
-// exception is thrown, *this contains a value.
-#define ABSL_GLIBCXX_ANY_EMPLACE_EXCEPTION_BUG 1
-#endif
-#if defined(ABSL_HAVE_EXCEPTIONS) && \
-!defined(ABSL_GLIBCXX_ANY_EMPLACE_EXCEPTION_BUG)
-EXPECT_FALSE(target.has_value());
+// GCC and Clang have a bug here.
+// Ine some cases, the exception seems to be thrown at the wrong time, and
+// target may contain a value.
+#ifdef __GNUC__
+TEST(AnyTest, DISABLED_FailedEmplaceInPlace) {
+#else
+TEST(AnyTest, FailedEmplaceInPlace) {
 #endif
-  }
+  BadCopyable bad;
+  absl::any target(absl::in_place_type);
+  ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
+  EXPECT_FALSE(target.has_value());
 }
 
 }  // namespace

Bug#1021183: opendkim: Opendkim complaining insecure keys by assumption

[Patrik Schindler]

Package: opendkim
Version: 2.11.0~beta2-4
Severity: normal

Each and every time, Opendkim wakes up by work from Postfix, it creates
a log entry:

key data is not secure: .private is in group 133 which has multiple
users (e.g., "postfix")

This issue has been existing since 2015 (when I added DKIM to my mailflow) and
the according Debian release.

Opendkim has its own group and for proper access rights from postfix, added
postfix to the opendkim group. If I don't set this, I get

Oct  3 14:17:33 myhost postfix/smtpd[123464]: warning: connect to Milter 
service unix:/var/run/opendkim/opendkim.sock: Permission denied

Setting RequireSafeKeys to "no" not prevent the message from appearing, but
just prevents Opendkim from exiting because of this condition.

I think that group rights should not trigger this behavior, but instead only
when "other" is allowed to read the private key.

-- System Information:
Debian Release: 11.5
  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-18-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages opendkim depends on:
ii  adduser  3.118
ii  dns-root-data2021011101
ii  init-system-helpers  1.60
ii  libbsd0  0.11.3-1
ii  libc62.31-13+deb11u4
ii  libdb5.3 5.3.28+dfsg1-0.8
ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
ii  liblua5.1-0  5.1.5-8.1+b3
ii  libmemcached11   1.0.18-4.2
ii  libmilter1.0.1   8.15.2-22
ii  libopendbx1  1.4.6-15
ii  libopendkim112.11.0~beta2-4
ii  librbl1  2.11.0~beta2-4
ii  libssl1.11.1.1n-0+deb11u3
ii  libunbound8  1.13.1-1
ii  libvbr2  2.11.0~beta2-4
ii  lsb-base 11.1.0

Versions of packages opendkim recommends:
ii  opendkim-tools  2.11.0~beta2-4

opendkim suggests no packages.

-- Configuration Files:
/etc/dkimkeys/README.PrivateKeys [Errno 13] Permission denied: 
'/etc/dkimkeys/README.PrivateKeys'
/etc/opendkim.conf changed [not included]

-- no debconf information

Bug#1021184: virt-manager: System tray icon not showed

[Echedey López Romero]

Package: virt-manager
Version: 1:3.2.0-3
Severity: normal
Tags: a11y

Dear Maintainer,

* What led up to the situation?

It is not possible to enable or configure a system tray icon in the application
in order to maintain it opened with the manager being closed.

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

In every case, I opened the application, checked if I was able to enable the
tray icon and restart it to know if it took any effect.

The cases were the following:
* Open the application by default, requiring root or user password with
privileges to proceed. It finished seeing the option disabled.
* Open the application with the user added to the libvirt group. No password
was requested but the option was still disabled.
* Open the application with superuser privileges from terminal. No additional
password was requested, the option was enabled but did nothing.

* What was the outcome of this action?

Not being able to setup tray icon for the application.

* What outcome did you expect instead?

Be able to setup tray icon.

* Is there some additional information?

I am using GNOME DE.

I also attach the logs of the default behavior, delimited in the begin and the
end by "---".

---

[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (cli:204) Launched with
command line: /usr/bin/virt-manager --no-fork --debug
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (virtmanager:163) virt-
manager version: 3.2.0
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (virtmanager:164)
virtManager import: /usr/share/virt-manager/virtManager
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (virtmanager:201)
PyGObject version: 3.38.0
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (virtmanager:205) GTK
version: 3.24.24
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (systray:463) Showing
systray: False
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (inspection:203) python
guestfs is installed
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (inspection:225)
libguestfs gsetting enabled=True
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (engine:113) Loading
stored URIs:
qemu:///system
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (engine:461) processing
cli command uri= show_window=manager domain=
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (engine:464) No cli
action requested, launching default window
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (manager:185) Showing
manager
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (engine:316) window
counter incremented to 1
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (engine:211) Initial
gtkapplication activated
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (connection:482)
conn=qemu:///system changed to state=Connecting
[Mon, 03 Oct 2022 13:38:50 virt-manager 164972] DEBUG (connection:902)
Scheduling background open thread for qemu:///system
[Mon, 03 Oct 2022 13:38:54 virt-manager 164972] DEBUG (connection:952) libvirt
version=700
[Mon, 03 Oct 2022 13:38:54 virt-manager 164972] DEBUG (connection:953) daemon
version=700
[Mon, 03 Oct 2022 13:38:54 virt-manager 164972] DEBUG (connection:954) conn
version=5002000
[Mon, 03 Oct 2022 13:38:54 virt-manager 164972] DEBUG (connection:955)
qemu:///system capabilities:


  
56ea415e-4d22-4ee0-a100-e30679c5bce6

  x86_64
  Broadwell-noTSX-IBRS
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  



  
  
tcp
rdma
  


  

  16182208
  4045552
  0
  0
  

  
  








  

  


  


  apparmor
  0


  dac
  0
  +64055:+64055
  +64055:+64055

  

  
hvm

  32
  /usr/bin/qemu-system-arm
  integratorcp
  ast2600-evb
  borzoi
  spitz
  virt-2.7
  nuri
  mcimx7d-sabre
  romulus-bmc
  virt-3.0
  virt-5.0
  npcm750-evb
  virt-2.10
  musca-b1
  virt-2.8
  realview-pbx-a9
  versatileab
  kzm
  musca-a
  virt-3.1
  mcimx6ul-evk
  virt-5.1
  smdkc210
  sx1
  virt-2.11
  imx25-pdk
  virt-2.9
  orangepi-pc
  z2
  virt-5.2
  virt
  xilinx-zynq-a9
  tosa
  mps2-an500
  virt-2.12
  mps2-an521
  sabrelite
  mps2-an511
  

Bug#515724: closed by Debian FTP Masters (reply to Bastian Germann ) (Bug#515724: fixed in vflib3 3.7.2+dfsg-0.1)

[Paul Wise]

Control: clone -1 -2
Control: reopen -2
Control: severity -2 wishlist
Control: retitle -2 vflib3: add Homepage field

On Fri, 2022-09-30 at 14:45 +, Bastian Germann wrote:

>    * Fix upstream source URL (Closes: #515724).

This missed the requested Homepage field addition, cloning.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1019403: gitlab: failed to fetch comments in issue (500 Internal Server Error)

[Antoine Le Gonidec]

On Thu, 08 Sep 2022 17:04:31 +0200 Maximilian Stein  wrote:

To me, this seemed like a typo, so I simply removed "h " in
labels_helper.rb:250. This fixed the issue for me, as far as I can
tell.


This might not be a typo. It has been added in the following upstream commit:
https://gitlab.com/gitlab-org/gitlab/-/commit/513066c360bcfaa8d5cd40795f7d98d46b9e1e44
(I could not find the original merge request discussion, its access might be 
restricted)

An alternative fix is to replace:
#{"style=\"background-color: #{h bg_color}\"" if bg_color}
with:
#{"style=\"background-color: #{html_escape bg_color}\"" if bg_color}

I think "h" is supposed to be a method alias for "html_escape", but is not 
loaded due to something missing in our setup.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021186: bullseye-pu: package debmirror/1:2.35+deb11u1

[Colin Watson]

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

[ Reason ]
Support mirroring of the new non-free-firmware section.  See
https://lists.debian.org/debian-boot/2022/10/msg00026.html.

[ Impact ]
The non-free-firmware section will be absent from debmirror-managed
mirrors, unless the list of sections is specified explicitly.

[ Tests ]
Nothing useful by way of automated tests, but I've tested manually that
it works for both suites that have the new section and suites that
don't.

[ Risks ]
The patch is pretty small and trivial.

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

[ Changes ]
diff --git a/debian/changelog b/debian/changelog
index 4e7877c..89053f9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+debmirror (1:2.35+deb11u1) UNRELEASED; urgency=medium
+
+  * Add non-free-firmware to the default sections.
+
+ -- Colin Watson   Mon, 03 Oct 2022 14:00:22 +0100
+
 debmirror (1:2.35) unstable; urgency=medium
 
   [ Kees Cook ]
diff --git a/debmirror b/debmirror
index 4512ad3..bd28250 100755
--- a/debmirror
+++ b/debmirror
@@ -147,7 +147,7 @@ suite in their F files.
 =item B<-s>, B<--section>=I
 
 Specify the section of Debian to mirror. Defaults to
-C.
+C.
 
 =item B<-a>, B<--arch>=I
 
@@ -816,7 +816,7 @@ $remoteroot =~ s%^[:/]%% unless downloads_via_file();
 @dists=split(/,/,join(',',@dists));
 @dists=qw(sid) unless @dists;
 @sections=split(/,/,join(',',@sections));
-@sections=qw(main contrib non-free main/debian-installer) unless @sections;
+@sections=qw(main contrib non-free non-free-firmware main/debian-installer) 
unless @sections;
 @arches=split(/,/,join(',',@arches));
 @arches=qw(i386) unless @arches;
 @arches=() if (join(',',@arches) eq "none");
diff --git a/examples/debmirror.conf b/examples/debmirror.conf
index d41d338..fc08bb9 100644
--- a/examples/debmirror.conf
+++ b/examples/debmirror.conf
@@ -26,7 +26,7 @@ $passwd="anonymous@";
 $remoteroot="debian";
 $download_method="ftp";
 @dists="sid";
-@sections="main,main/debian-installer,contrib,non-free";
+@sections="main,main/debian-installer,contrib,non-free,non-free-firmware";
 @arches="i386";
 # @ignores="";
 # @excludes="";

Thanks,

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1021187: gnome-keyring: /usr/bin/gnome-keyring-daemon --daemonize --login 100% CPU usage

[John Wong]

Package: gnome-keyring
Version: 42.1-1
Severity: normal

Dear Maintainer,
 I just noticed recently, the "/usr/bin/gnome-keyring-daemon --daemonize 
--login"
 running 100% (1 vcpu) CPU usage everytime when I login (until I
 kill it)
 Please help and thank you.

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

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

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


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

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

Versions of packages gnome-keyring depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.2-1
ii  dbus-x11 [dbus-session-bus]   1.14.2-1
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-3
ii  gcr   3.41.1-1
ii  init-system-helpers   1.65.2
ii  libc6 2.35-1
ii  libgck-1-03.41.1-1
ii  libgcr-base-3-1   3.41.1-1
ii  libgcrypt20   1.10.1-2
ii  libglib2.0-0  2.74.0-2
ii  libsystemd0   251.5-1
ii  p11-kit   0.24.1-1
ii  pinentry-gnome3   1.2.0-2

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  42.1-1
ii  libpam-gnome-keyring  42.1-1

gnome-keyring suggests no packages.

-- no debconf information

Bug#1020640: libglew2.2: Glew built without, wxwidgets with EGL support

[Alastair McKinstry]

Hi,


As maintainer would be open to changing Glew to EGL support, but need to 
understand better the consequences.


I have a test build of glew with egl (for Linux, not hurd or freebsd 
yet) and it builds fine.


Any pointers to docs on EGL/non-EGL builds, or opinions and evidence 
would be welcome.



Alastair


On 03/10/2022 03:42, Olly Betts wrote:

On Sat, Sep 24, 2022 at 09:50:10PM +0100, Olly Betts wrote:

On Sat, Sep 24, 2022 at 06:09:31PM +0200, Andreas Metzler wrote:

wxwidgets and glew disagree over EGL support, glew is built without,
wxwidgets (since 3.2) with.

That causes problems (crashes, "Unable to init glew library") in
software using glew and wxwidgets. Google finds multiple instances, I
know about hugin.

FWIW, these are the packages which seem to depend on both wx and glew
(just based on checking dependencies):

hugin
megaglest
qutemol
scorched3d
darkradiant
limesuite

The last two have already switched to wx3.2 in unstable and testing, but
I don't see reports in the BTS of glew-related problems, and didn't see
any issues from a quick test myself.  At least with darkradiant I did
get what looked like a GL rendered pane to appear - I'm not sure I
actually exercised any GL code with limesuite (it seems to need some
hardware I don't have to be useful).

Cheers,
 Olly


--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@sceal.ie, im: @sceal.ie:mckinstry

Bug#1021188: ITP: ovn-bgp-agent -- OpenStack virtual network service - OVN BGP agent

[Thomas Goirand]

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

* Package name: ovn-bgp-agent
  Version : 0.2.0
  Upstream Author : OpenStack Foundation 
* URL : https://opendev.org/x/ovn-bgp-agent
* License : Apache-2.0
  Programming Lang: Python
  Description : OpenStack virtual network service - OVN BGP agent

 Neutron provides an API to dynamically request and configure virtual networks.
 These networks connect "interfaces" from other OpenStack services (such as
 vNICs from Nova VMs). The Neutron API supports extensions to provide advanced
 network capabilities, including QoS, ACLs, and network monitoring.
 .
 This package provides the OVN BGP agent.

Bug#1021189: desktop-head-unit binary is underlinked

[Matthias Klose]

Package: google-android-extras-google-auto-installer
Version: 1659100756
Severity: important
Tags: sid bookworm

Installing libc++abi1-15 instead of libc++abi1-14 (making LLVM 15 the default)
breaks existing binaries, like

/usr/lib/android-sdk/extras/google/auto/desktop-head-unit: symbol lookup error:
/usr/lib/android-sdk/extras/google/auto/desktop-head-unit: undefined symbol:
__udivmodti4

found in the google-android-installers package.  The reason is that libc++abi.so
isn't linked anymore against libgcc_s, and just rebuilding the package using
LLVM 15 also doesn't link the binary against libgcc_s.


$ ldd /usr/lib/llvm-14/lib/libc++abi.so.1.0
linux-vdso.so.1 (0x7fff0233d000)
libunwind.so.1 => /lib/x86_64-linux-gnu/libunwind.so.1 
(0x7f4c18f64000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4c18d5f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f4c18c76000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f4c18c56000)
/lib64/ld-linux-x86-64.so.2 (0x7f4c18fb2000)


$ ldd /usr/lib/llvm-15/lib/libc++abi.so.1.0
linux-vdso.so.1 (0x7ffe8acaf000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f7ecdd09000)
libunwind.so.1 => /lib/x86_64-linux-gnu/libunwind.so.1 
(0x7f7ecdcfb000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f7ecdc12000)
/lib64/ld-linux-x86-64.so.2 (0x7f7ecdf51000)

However, the symbol above is referenced in the desktop-head-unit binary, so it's 
a bug in this package. If you cannot change that binary, maybe preload the 
missing library in a wrapper script.

Bug#1021183: opendkim: Opendkim complaining insecure keys by assumption

[David Bürgin]

Patrik Schindler:
> Each and every time, Opendkim wakes up by work from Postfix, it creates
> a log entry:
> 
> key data is not secure: .private is in group 133 which has multiple
> users (e.g., "postfix")
> 
> This issue has been existing since 2015 (when I added DKIM to my mailflow) and
> the according Debian release.
> 
> Opendkim has its own group and for proper access rights from postfix, added
> postfix to the opendkim group. If I don't set this, I get
> 
> Oct  3 14:17:33 myhost postfix/smtpd[123464]: warning: connect to Milter 
> service unix:/var/run/opendkim/opendkim.sock: Permission denied
> 
> Setting RequireSafeKeys to "no" not prevent the message from appearing, but
> just prevents Opendkim from exiting because of this condition.
> 
> I think that group rights should not trigger this behavior, but instead only
> when "other" is allowed to read the private key.

Can you include the steps to reproduce this? I don’t see this behaviour
on my installation (opendkim 2.11.0~beta2-5).

Some of my configuration bits below:

$ grep -i -e keyfile -e userid -e umask -e socket -e requiresafekeys 
/etc/opendkim.conf
KeyFile /etc/dkimkeys/2020.private
UserID  opendkim
UMask   007
Socket  local:/var/spool/postfix/opendkim/opendkim.sock

$ sudo ls -ld /etc/dkimkeys{,/2020.private}
drwx-- 2 opendkim opendkim 4096 Aug 25  2021 /etc/dkimkeys
-rw--- 1 opendkim opendkim 1679 Nov 20  2020 /etc/dkimkeys/2020.private

$ sudo ls -ld /var/spool/postfix/opendkim{,/opendkim.sock}
drwxr-x--- 2 opendkim opendkim 27 Sep 29 16:32 /var/spool/postfix/opendkim
srwxrwx--- 1 opendkim opendkim  0 Sep 29 16:32 
/var/spool/postfix/opendkim/opendkim.sock

$ groups postfix | grep -o opendkim
opendkim

Bug#1021190: ara-server: should require 'daemon'

[Peter Gervai]

Package: ara-server
Version: 1.5.8-1
Severity: important

Shall require the 'daemon' package:

Starting ARA Records Ansible: ara-server/etc/init.d/ara-server: 42: 
/lib/init/init-d-script: /usr/bin/daemon: not found 

/etc/init.d/ara-server: 43: /lib/init/init-d-script: /usr/bin/daemon: not found 

 failed! 
invoke-rc.d: initscript ara-server, action "start" failed.  


  

Bug#1021191: ITP: rust-fernet -- An implementation of fernet in Rust

[Timo Aaltonen]

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

* Package name: rust-fernet
  Version : 0.1.4
  Upstream Author : Alex Gaynor , Ben Bangert 

* URL : https://github.com/mozilla-services/fernet-rs/
* License : MPL-2.0
  Programming Lang: Rust
  Description : An implementation of fernet in Rust


Required by new 389-ds-base.

Bug#1021192: ara-server: Can't seem to be able to start: daemon --user doesn't change $HOME

[Peter Gervai]

Package: ara-server
Version: 1.5.8-1
Severity: normal

Since the server failed to start I tried to see what's going on:

# /usr/bin/daemon -f -v255 -d255 --name=ara-server 
--pidfile=/var/run/ara/ara-server.pid --user=ara -- /usr/bin/ara-manage 
runserver 0.0.0.0:8080
...
daemon: debug:  user = ara  
  
daemon: debug:  changing to user ara/111   
...
daemon: debug:HOME=/root
daemon: debug:USER=root
...
PermissionError: [Errno 13] Permission denied: '/root/.ara' 




I don't use daemon so I am clueless how this was intended to work.

(I'll use runit anyway, just wondered whether the package actually works out of 
the box.)

Bug#1021193: binutils-arm-none-eabi ftbfs

[Matthias Klose]

Package: src:binutils-arm-none-eabi
Version: 17
Severity: serious
Tags: sid bookworm

setting deb_upstream_version in debian/rules fails:

$ echo 2.39-1+17 | cut -d. -f1-3

2.39-1+17


That should work as well:

$ echo 2.39-1ubuntu1+17ubuntu1 | cut -d. -f1-3

2.39-1ubuntu1+17ubuntu1


using | sed 's/-.*$//' instead of the cut command should work in both cases.

Bug#1021110: whois.nic.fr is NOT a RIPE server

[Stephane Bortzmeyer]

On Sun, Oct 02, 2022 at 12:28:28PM +0200,
 Marco d'Itri  wrote 
 a message of 33 lines which said:

> Maybe AFNIC could accept again the parameter for a few years while we 
> wait for this change to percolate to the whole Linux world?

Yes. Awaiting deployment.

PS : whois -h whois.nic.fr. (dot at the end) works. It's great as a
workaround but it seems to indicate that the matching of names to the
list of RIPE-compatible servers is imperfect.

Bug#1021194: python-refurb: Typo in long description of binary packages

[Teemu Hukkanen]

Source: python-refurb
Version: 1.1.0-1
Severity: minor

Hi,

The binary packages from python-refurb: refurb and python3-refurb have a
typo in the long description, "It can hive hints" should be "It can give
hints".

Bug#1021195: ITP: rust-concread -- Concurrently readable datastructures for Rust

[Timo Aaltonen]

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

* Package name: rust-concread
  Version : 0.3.7
  Upstream Author : William Brown 
* URL : https://github.com/kanidm/concread/
* License : MPL-2.0
  Programming Lang: Rust
  Description : Concurrently readable datastructures for Rust


Required by new 389-ds-base.

Bug#1021196: sweethome3d: Fail to export plans as svg

[Christian Marillat]

Package: sweethome3d
Version: 7.0.2+dfsg-1
Severity: normal

Dear Maintainer,

I can't save a plan to SVG:

In top menu "Plan" go to the bottom and select "Export To SVG Format"
The file size is 0 (zero) byte.
And sweethome3d when launched from a terminal return these errors :

,
| Java 3D: implicit antialiasing enabled
| java.lang.NoClassDefFoundError: org/freehep/util/io/WriterOutputStream
|   at 
com.eteks.sweethome3d.swing.PlanComponent$SVGSupport.exportToSVG(Unknown Source)
|   at com.eteks.sweethome3d.swing.PlanComponent.exportToSVG(Unknown Source)
|   at com.eteks.sweethome3d.swing.PlanComponent.exportData(Unknown Source)
|   at 
com.eteks.sweethome3d.swing.MultipleLevelsPlanPanel.exportData(Unknown Source)
|   at com.eteks.sweethome3d.swing.HomePane.exportToSVG(Unknown Source)
|   at com.eteks.sweethome3d.viewcontroller.HomeController$38.call(Unknown 
Source)
|   at com.eteks.sweethome3d.viewcontroller.HomeController$38.call(Unknown 
Source)
|   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
|   at 
com.eteks.sweethome3d.viewcontroller.ThreadedTaskController$1.run(Unknown 
Source)
|   at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
|   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
|   at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
|   at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
|   at java.base/java.lang.Thread.run(Thread.java:829)
| Caused by: java.lang.ClassNotFoundException: 
org.freehep.util.io.WriterOutputStream
|   at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
|   at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
|   at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
|   ... 14 more
`

Christian


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

Kernel: Linux 5.19.12 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sweethome3d depends on:
ii  default-jre [java8-runtime] 2:1.11-72
ii  icedtea-netx1.8.8-1
ii  java-wrappers   0.3
ii  libbatik-java   1.15+dfsg-1
ii  libfreehep-graphics2d-java  2.4+dfsg-3
ii  libfreehep-graphicsbase-java2.4+dfsg-3
ii  libfreehep-graphicsio-java  2.4+dfsg-3
ii  libfreehep-graphicsio-svg-java  2.4+dfsg-3
ii  libitext-java   2.1.7-13
ii  libjava3d-java  1.5.2+dfsg-17
ii  libsunflow-java 0.07.2.svn396+dfsg-18
ii  openjdk-11-jre [java8-runtime]  11.0.16+8-1

Versions of packages sweethome3d recommends:
pn  sweethome3d-furniture  

sweethome3d suggests no packages.

-- no debconf information

Bug#1021180: usrmerge may break user-mode-linux rootfs

[Marco d'Itri]

On Oct 03, Ritesh Raj Sarraf  wrote:

> Now, going forward, I can manually fix it by mounting to
> /usr/lib/modules and arranging the symlink to the old location in the
> guest, something that usrmerge is trying to do.
Actually I think that it is much easier:
- unmount /usr/lib/modules
- complete the installation of usrmerge
- reboot

Can you confirm that after doing this everything will work as expected?

What is the canonical way to detect UML?
I am not sure if we want to unmount/remount stuff, but at least (and at 
least as a first step) the conversion program can bail out gracefully 
and explain what to do.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1021180: usrmerge may break user-mode-linux rootfs

[Ritesh Raj Sarraf]

Hello Marco,

On Mon, 2022-10-03 at 16:09 +0200, Marco d'Itri wrote:
> On Oct 03, Ritesh Raj Sarraf  wrote:
> 
> > Now, going forward, I can manually fix it by mounting to
> > /usr/lib/modules and arranging the symlink to the old location in
> > the
> > guest, something that usrmerge is trying to do.
> Actually I think that it is much easier:
> - unmount /usr/lib/modules
> - complete the installation of usrmerge
> - reboot
> 
> Can you confirm that after doing this everything will work as
> expected?
> 

There was nothing mounted onto /usr/lib/modules before. Instead, all
this time it was mounted on /lib/modules/ just like on the host. I
think it failed because usrmerge script was invoking mv command while
/lib/modules was independently mounted 'read-only'

After facing this error, I switched the fstab to /usr/lib/modules and
rebooted. I first rebooted because unmounting /lib/modules was not
possible as it was held by the linux process.

After the reboot, re-running the usrmerge script worked proper. 

> What is the canonical way to detect UML?

systemd does it nicely with:

root@uml:~# systemd-detect-virt 
uml
root@uml:~# 

> I am not sure if we want to unmount/remount stuff, but at least (and
> at 
> least as a first step) the conversion program can bail out gracefully
> and explain what to do.

Yes. Some careful instructions targeting novice users. I was able to
quickly work it out but something simple for general users would be
nice.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#778950: Fixed in Upstream

[Jeffrey Hawkins]

It appears the CVE-2013-4235 has been fixed in the upstream project,
Release:  4.11.  Is there any intent by Debian to backport the fix?
https://github.com/shadow-maint/shadow/releases/tag/v4.11

Jeff

-- 


*For more information on how and why we collect your personal 
information, please visit our Privacy Policy 
.*

Bug#1012196: buglist

[Bastian Germann]

Control: tags -1 moreinfo

On Sun,  2 Oct 2022 18:02:38 +  wrote:

Control: tags -1 -moreinfo

 > d/copyright
 > ===
 >
 > Some GPL-2+ licensed files have the following additional exception:
 > # The developers of the Exaile media player hereby grant permission
 > # for non-GPL compatible GStreamer and Exaile plugins to be used and
 > # distributed together with GStreamer and Exaile. This permission is
 > # above and beyond the permissions granted by the GPL license by which
 > # Exaile is covered. If you modify this code, you may extend this
 > # exception to your version of the code, but you are not obligated to
 > # do so. If you do not wish to do so, delete this exception statement
 > # from your version.

I reworked the copyright file based on 
https://sources.debian.org/src/exaile/3.4.0.2-1/debian/copyright/

Is the extension represented correct?


No. Please check the copyright format description for the "with" keyword.
Also, please try to present the copyright info in a more consice way. When two file groups have the same copyright 
holders please merge them (combining the years to a year enumeration or year range).


You can also use broader wildcards in Files: and override parts of the matches 
with a later Files: match.

I have already given you a hint that
"plugins/ipconsole/ipython_view.py by IBM Corporation is licensed under another 
variant of the BSD-3-Clause."
So, please do not use Michael Bostock's version for that file match but add a 
BSD-3-clause-IBM variant.
You should also remove his copyright line from the License: section because 
that is already in the Copyright: section.


 > d/rules
 > ===
 >
 > Please remove or explain the lines:
 >
 > dh_auto_clean
 > make manpage
 > make completion
 > ...
 > #override_dh_installdocs:
 > # dh_installdocs readme
 > override_dh_usrlocal:
 >
 > Please think of a different method instead of calling dh_auto_clean 
during install time to get rid of __pycache__ if
 > that is the reason for it. Maybe just copy the Makefile line '-find . 
-name "__pycache__" -exec rm -rf {} \;' ?


The point was to remove __pychache__.
Now I prevent dh_auto_build to do `make compile`



You have not explained "override_dh_usrlocal:".

Bug#1021197: fwupd: Blocked executable in the ESP, ensure grub and shim are up to date

[Alex Muntada]

Package: fwupd
Version: 1.5.7-4
Severity: normal
Tags: fixed-upstream

Dear Maintainer,
there's an issue in bullseye fwupd that seems to need an upgrade
or a backport from unstable for the following update to succeed
(see https://github.com/fwupd/fwupd/issues/5035 for details):

$ sudo fwupdmgr update
Devices with no available firmware updates:
 • ...
Upgrade available for UEFI dbx from 77 to 217
UEFI dbx and all connected devices may not be usable while updating. Continue 
with update? [Y|n]:
Downloading… [***]
Decompressing…   [***]
Authenticating…  [***]
Authenticating…  [***]
Updating UEFI dbx…   [***]
Verifying…   [***]
Blocked executable in the ESP, ensure grub and shim are up to date: 
/boot/efi/EFI/Boot/shimx64.efi Authenticode checksum 
[47b31a1c7867644b2ee8093b2d5fbe21e21f77c1617a2c08812f57ace0850e9f] is present 
in dbx



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

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

Versions of packages fwupd depends on:
ii  libc6  2.31-13+deb11u3
ii  libcurl3-gnutls7.74.0-1.3+deb11u2
ii  libefiboot137-6
ii  libelf10.183-1
ii  libflashrom1   1.2-5
ii  libfwupd2  1.5.7-4
ii  libfwupdplugin11.5.7-4
ii  libglib2.0-0   2.66.8-1
ii  libgnutls303.7.1-5+deb11u2
ii  libgudev-1.0-0 234-1
ii  libgusb2   0.3.5-1
ii  libjcat1   0.1.3-2
ii  libjson-glib-1.0-0 1.6.2-1
ii  libpolkit-gobject-1-0  0.105-31+deb11u1
ii  libsmbios-c2   2.4.3-1
ii  libsqlite3-0   3.34.1-3
ii  libsystemd0247.3-7
ii  libtss2-esys-3.0.2-0   3.0.3-2
ii  libxmlb1   0.1.15-2
ii  shared-mime-info   2.0-1

Versions of packages fwupd recommends:
ii  bolt   0.9.1-1
ii  dbus   1.12.20-2
ii  fwupd-amd64-signed [fwupd-signed]  1.5.7+4
ii  python33.9.2-3
pn  secureboot-db  
ii  udisks22.9.2-2+deb11u1

Versions of packages fwupd suggests:
pn  gir1.2-fwupd-2.0  

-- no debconf information

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer 🍥 log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#1021198: puppet-agent: please make the build reproducible

[Chris Lamb]

Source: puppet-agent
Version: 7.16.0-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
puppet-agent could not be built reproducibly.

This is because the domain name of the system is embedded in the
manual page.

A patch is attached, which is based on the parallel (if not identical)
patch attached to bug #1009799 in the "puppet" source package that was
authored by Vagrant Cascadian.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/lib/puppet/defaults.rb2022-10-03 07:24:21.733301222 -0700
--- b/lib/puppet/defaults.rb2022-10-03 07:35:15.654024548 -0700
@@ -1613,7 +1613,7 @@
   :desc   => "Whether the server will search for SRV records in DNS 
for the current domain.",
 },
 :srv_domain => {
-  :default=> lambda { Puppet::Settings.domain_fact },
+  :default=> lambda { ENV.has_key?('SOURCE_DATE_EPOCH') ? '(node\'s 
fully qualified domain name)' : Puppet::Settings.domain_fact },
   :desc   => "The domain which will be queried to find the SRV records 
of servers to use.",
 },
 :http_extra_headers => {

Bug#1009799: puppet: reproducible builds: domain name embedded in puppet.conf.5 man page

[Chris Lamb]

Vagrant Cascadian wrote:

> This patch appears to apply to puppet from experimental too, although I
> was unable to get that to build to confirm the fix.

See also bug #1021198, which is a parallel bug in the "puppet-agent"
source package.


Regards,

-- 
  o
⬋   ⬊  Chris Lamb
   o o reproducible-builds.org 💠
⬊   ⬋
  o

Bug#1021096: ITP: spaghetti -- Analysis of Network-constrained Spatial Data

[Bastian Germann]

On Sat, 01 Oct 2022 23:18:20 -0300 Josenilson Ferreira da Silva 
 wrote:
 Note: 
 Module needed for packaging: https://github.com/pysal/spot


You probably mean https://github.com/pysal/spopt.

When you are packaging dependencies for non-existing packages it is good 
practise to file a RFP/ITP
for those packages as well and let them be blocked by the dependency.

Bug#1021199: ITP: rust-lru -- A LRU cache implementation

[Timo Aaltonen]

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

* Package name: rust-lru
  Version : 0.7.8
  Upstream Author : Jerome Froelich
* URL : https://github.com/jeromefroe/lru-rs.git
* License : MIT
  Programming Lang: Rust
  Description : A LRU cache implementation


Required by rust-concread.

Bug#1021180: usrmerge may break user-mode-linux rootfs

[Marco d'Itri]

On Oct 03, Ritesh Raj Sarraf  wrote:

> There was nothing mounted onto /usr/lib/modules before. Instead, all
Sure, I meant /lib/modules/ .
Do you have another UML system where you can repeat this test?

> this time it was mounted on /lib/modules/ just like on the host. I
> think it failed because usrmerge script was invoking mv command while
> /lib/modules was independently mounted 'read-only'
It failed because it tried to move a mount point, which mv cannot do.

> After facing this error, I switched the fstab to /usr/lib/modules and
> rebooted. I first rebooted because unmounting /lib/modules was not
> possible as it was held by the linux process.
> 
> After the reboot, re-running the usrmerge script worked proper. 
This is a good solution as well.

> > What is the canonical way to detect UML?
> systemd does it nicely with:
I cannot have usrmerge depend on systemd.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1010957: status update? Re: Bug#1010957: man-db: unreproducible index.db: contents depend on directory read order

[Holger Levsen]

On Sun, Oct 02, 2022 at 04:00:58PM +0100, Colin Watson wrote:
> Control: tag -1 fixed-upstream
> Success!
>   https://gitlab.com/cjwatson/man-db/-/compare/5d2594d0a0...866c3571d3

awesome!

On Sun, Oct 02, 2022 at 05:56:19PM +0100, Colin Watson wrote:
> I thought I'd set SOURCE_DATE_EPOCH, but I'd failed to pass it through
> sudo.  After fixing that, I indeed get cmp-identical tarballs.

very nice! much cheers!


-- 
cheers,
Holger

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

Plastic bottles: made to last forever, designed to throw away.


signature.asc
Description: PGP signature

Bug#944785: pufferfish wants to link with twopaco and ntcard

[Andreas Tille]

Hi Andrius,

Am Mon, Oct 03, 2022 at 10:19:41AM +0300 schrieb Andrius Merkys:
> twopaco has entered testing (yay!), thus I gave its reverse dependency,
> pufferfish (ITP bug #944785), a look. pufferfish carries embedded copies
> of twopaco and ntcard with a modified build system to create static (or
> is it shared?) libraries for these two and then links pufferfish with
> them. For Debian twopaco and ntcard have been un-embedded from
> pufferfish and packaged as separate binary packages instead. However,
> they do not build neither shared nor static libraries, just executables.
> 
> I think we can get around by patching twopaco and ntcard builds to
> include static libraries in their binary packages. Does this sound right?

My main motivation to start ntcard and twopaco packages was to avoid
code duplication in pufferfish.  I admit it seems I faild in doing this
sensibly to forget creating a library package.  Simply do whatever
brings you forward with pufferfish and fix what I failed to do.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#976052: ITP: zola -- static site generator

[Mohd Bilal]

Hello,

On Mon, 02 May 2022 23:04:58 +0200 Jonas Smedegaard  wrote:
0.15.3 draft 2, needs embedding 107 crates (60 missing, 5 broken, 20 
outdated, 22 ahead); builds in ~25 minutes; runs except subcommand serve 
which needs web assets separately packaged.


Thanks for working on packaging zola. This is something that I use and 
would love to see in Debian. I would like to offer my help for making 
this happen (like packaging missing deps? ). I've had some experience 
packaging ruby gems.


Let me know if I can be of any help to you. I'm ready to learn some rust 
packaging if required.


Thanks
--
Mohammed Bilal
2D65 BC1E B966 5A6E 97F9 730A B3F5 9452 8521 9E1F


OpenPGP_0xB3F5945285219E1F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021200: wrong build-dependency libservlet-api-ava

[Pierre Gruet]

Package: groovy
Version: 2.4.21-3
Severity: important

Hello,

The version 2.4.21-3 of groovy that was uploaded yesterday wrongly includes
libservlet-api-ava
as a build-dependency. This mispelled package name has been introduced in an
attempt to solve Bug #1020429.

Build dependencies of groovy and of its rdeps cannot be satisfied.

Cheers,

-- 
Pierre

Bug#1021201: vulkan-loader: new upstream stable point release 1.3.224.1

[Simon McVittie]

Source: vulkan-loader
Version: 1.3.224.0-1
Severity: wishlist

vulkan-loader is currently at upstream version 1.3.224.0, but upstream's
sdk-1.3.224 stable branch now has a 1.3.224.1 point release with these
release notes:

> Enable layer interception of unknown functions
>
> Re-add previously reverted behavior that allows layers to setup
> dispatch chains for unknown physical device and device functions during
> vkCreateInstance. Previously, functions not known to the loader could
> not be queried by a layer during vkCreateInstance (when dispatch tables
> should be setup). The change adds support for unknown functions in the
> trampolines of vkGetInstanceProcAddr and vkGetPhysicalDeviceProcAddr.

If I'm reading correctly, this is a backport of part of
https://github.com/KhronosGroup/Vulkan-Loader/pull/999,
which seems to be a fix for bugs seen with the RenderDoc and
GFXReconstruct development tools.

smcv

Bug#1021200: wrong build-dependency libservlet-api-ava

[tony mancill]

On Mon, Oct 03, 2022 at 05:36:17PM +0200, Pierre Gruet wrote:
> Package: groovy
> Version: 2.4.21-3
> Severity: important
> 
> Hello,
> 
> The version 2.4.21-3 of groovy that was uploaded yesterday wrongly includes
> libservlet-api-ava
> as a build-dependency. This mispelled package name has been introduced in an
> attempt to solve Bug #1020429.
> 
> Build dependencies of groovy and of its rdeps cannot be satisfied.

:facepalm: !   Thank you Pierre.

I am uploading a new source package now.  It may require some manual
help given that the package won't build against unstable.


signature.asc
Description: PGP signature

Bug#1018232: closed by Debian FTP Masters (reply to Jörg Frings-Fürst ) (Bug#1018232: fixed in libunistring 1.0-2)

[Samuel Thibault]

Hello,

Thanks for uploading a fixed version. However,

Debian Bug Tracking System, le lun. 03 oct. 2022 09:24:06 +, a ecrit:
>* debian/libunistring2.symbols.hurd-i386:
>  - Refresh symbols (Closes: #1018232).

I don't understand why keeping such a file? The 

(arch=hurd-any)

qualifier allows to keep just one file that covers both cases.

Having two files only means that the updating problem will come up over
and over and over and over with each new libunistring release that
introduces a new function, while having one file means that the problem
will come up only when divergence appears, which is *way* more seldom.

The libunistring2.symbols file is already using an arch= qualifier, why
not using it with hurd-any?

Samuel

Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0

[Michael Prokop]

Hi!

* Antoine Beaupré [Tue Aug 30, 2022 at 05:15:58PM -0400]:
> On 2022-08-25 14:19:42, Antoine Beaupré wrote:
> 
> > For what it's worth, I have tested lavamind's Puppet 7 package from
> > experimental, on bookworm, and it works fine:
> >
> > https://tracker.debian.org/pkg/puppet-agent
> >
> > ... I am not sure how to express this in the BTS here, because it's a
> > different source package, so I can't mark it as fixed there without
> > first marking it as affecting that other package, but it never affected
> > it.
> 
> The correct way seems to be to move this bug report back to src:puppet
> where it belongs, which this message should do.

AFAICT (thanks to our daily Grml ISO builds) this RC bug caused
puppet to get removed from Debian/testing, so unless this gets fixed
we won't have puppet in bookworm? Is anyone taking care of this?

regards
-mika-


signature.asc
Description: PGP signature

Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0

[Antoine Beaupré]

On 2022-10-03 18:21:46, Michael Prokop wrote:
> AFAICT (thanks to our daily Grml ISO builds) this RC bug caused
> puppet to get removed from Debian/testing, so unless this gets fixed
> we won't have puppet in bookworm? Is anyone taking care of this?

Puppet 5 has been EOL for years. It's a good thing it's gone from
bookworm, and a deliberate act on part of the Puppet package
maintainers.

We've packaged puppet-agent 7 and uploaded to unstable, it should
trickle down in bookworm in a day or two if all goes well.

We're working on packaging puppetserver 7. You can follow that work and
more here:

https://wiki.debian.org/Teams/Puppet/Work

A.

-- 
Imagine a world in which every single person on the planet is given
free access to the sum of all human knowledge.
 - Jimmy Wales, co-founder of Wikipedia

Bug#1021202: RM: puppet -- ROM; EOL upstream

[Antoine Beaupre]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pkg-puppet-de...@alioth-lists.debian.net

Hi,

We've had many discussions about this in the past, but it seems the
time has come to remove src:puppet from Debian.

The 5.5 Puppet agent and "puppetmaster" code that is shipped by this
package has been EOL for almost two years now[1]. It is broken by the
Ruby 3.0 upgrade in Debian[2], and, generally, is just mostly dead code.

Multiple RC bugs have just kicked it out of testing:

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

We have been working on repackaging everything from scratch. Puppet
agent 7 has landed in unstable yesterday[3] and we're still trying to
figure out how to package the Puppet Server 7 code base. This is
currently blocked on jruby things, but we are confident this can be
solved before the bookworm freeze.

Therefore, we hope to ship Puppet Agent and Server 7 in bookworm. The
src:puppet codebase is just one of the blockers we have of course, but
it's a blocker and should therefore be removed from Debian for now.

Details and progress of our work can be seen here:

https://wiki.debian.org/Teams/Puppet/Work

A.

[3] 
https://tracker.debian.org/news/1368401/accepted-puppet-agent-7160-3-source-into-unstable/

Bug#976052: ITP: zola -- static site generator

[Jonas Smedegaard]

Quoting Mohd Bilal (2022-10-03 17:21:45)
> On Mon, 02 May 2022 23:04:58 +0200 Jonas Smedegaard  wrote:
> > 0.15.3 draft 2, needs embedding 107 crates (60 missing, 5 broken, 20 
> > outdated, 22 ahead); builds in ~25 minutes; runs except subcommand serve 
> > which needs web assets separately packaged.
> 
> Thanks for working on packaging zola. This is something that I use and 
> would love to see in Debian. I would like to offer my help for making 
> this happen (like packaging missing deps? ). I've had some experience 
> packaging ruby gems.
> 
> Let me know if I can be of any help to you. I'm ready to learn some rust 
> packaging if required.

That sounds lovely - yes, your help packaging dependencies would be much
appreciated!

I see two reasonable approaches to that:

 a) join the Rust team, and follow their packaging style
 b) package *outside* the Rust team using a more common Debian style

What I do personally is b) and I am happy to help guide you.
If you prefer to join the Rust team instead, then let them guide you.
There should be no problem in us using different styles, if only you
please file ITPs for each package that you decide to work on.

As mentioned earlier in this bugreport, I maintain a list of packages
needing packaging - feel free to work on any of those that you like:
https://salsa.debian.org/debian/zola/-/blob/debian/latest/debian/TODO


Kind regards,

 - 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#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0

[Michael Prokop]

* Antoine Beaupré [Mon Oct 03, 2022 at 12:28:06PM -0400]:
> On 2022-10-03 18:21:46, Michael Prokop wrote:
> > AFAICT (thanks to our daily Grml ISO builds) this RC bug caused
> > puppet to get removed from Debian/testing, so unless this gets fixed
> > we won't have puppet in bookworm? Is anyone taking care of this?
> 
> Puppet 5 has been EOL for years. It's a good thing it's gone from
> bookworm, and a deliberate act on part of the Puppet package
> maintainers.

ACK :)

> We've packaged puppet-agent 7 and uploaded to unstable, it should
> trickle down in bookworm in a day or two if all goes well.

Oh, that's great news! :)

> We're working on packaging puppetserver 7. You can follow that work and
> more here:
> https://wiki.debian.org/Teams/Puppet/Work

Thanks, both for your fast response as well as working on the puppet
packaging! \o/

regards
-mika-


signature.asc
Description: PGP signature

Bug#965135: probably fixed in 8.20201007

[Joey Hess]

This bug seems very similar to a known fixed git-annex bug.

commit 922621301ae750e9ee86807ae21709e2e5b2d352
Author: Joey Hess 
Date:   Thu Sep 17 17:27:42 2020 -0400

Serialize use of C magic library, which is not thread safe.

This fixes failures uploading to S3 when using -J.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#1021203: ITP: node-postcss-modules -- PostCSS plugin to use CSS Modules everywhere

[Yadd]

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

* Package name: node-postcss-modules
  Version : 5.0.0
  Upstream Author : Alexander Madyankin 
* URL : https://github.com/madyankin/postcss-modules
* License : Expat
  Programming Lang: JavaScript
  Description : PostCSS plugin to use CSS Modules everywhere

node-postcss-modules will provide a PostCSS plugin to use CSS Modules
everywhere. Not only at the browser side.

This package is needed at least to update vue.js (libjs-vue and
node-vue) to version 4.x

It will be maintained under JS Team umbrella

Bug#900173: probably fixed

[Joey Hess]

commit 947d2a10bcf80e74758f65b3cc3fd5ac1bff3fa8
Author: Joey Hess 
Date:   Wed May 12 15:08:03 2021 -0400

assistant: Fix a crash on startup by avoiding using forkProcess

ghc 8.8.4 seems to have changed something that broke code that has been
successfully using forkProcess since 2012. Likely a change to GC internals.

Since forkProcess has never had clear documentation about how to
use it safely, avoid using it at all. Instead, when git-annex needs to
daemonize itself, re-run the git-annex command, in a new process group
and session.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#1019974: uim: FTBFS on armhf: [Makefile:871: installed-modules.scm] Segmentation fault

[Adrian Bunk]

Control: tags -1 patch

On Sat, Sep 17, 2022 at 09:43:49PM +0300, Dmitry Shachnev wrote:
>...
> make  -C ../uim uim-module-manager && \
> LIBUIM_SYSTEM_SCM_FILES=/home/mitya57/uim-1.8.8/sigscheme/lib 
> LIBUIM_SCM_FILES=/home/mitya57/uim-1.8.8/scm 
> LIBUIM_PLUGIN_LIB_DIR=/home/mitya57/uim-1.8.8/uim/.libs UIM_DISABLE_NOTIFY=1 
> ../uim/uim-module-manager \
> --path ../scm --register "anthy" "anthy-utf8"  "skk" "tutcode" 
> "byeoru" "latin" "elatin" "m17nlib" "xmload" "pyload" "viqr" "ipa-x-sampa" 
> "look" "ajax-ime" "google-cgiapi-jp" "baidu-olime-jp" "yahoo-jp"
> make[3]: Entering directory '/home/mitya57/uim-1.8.8/uim'
> make[3]: 'uim-module-manager' is up to date.
> make[3]: Leaving directory '/home/mitya57/uim-1.8.8/uim'
> make[2]: *** [Makefile:871: installed-modules.scm] Segmentation fault
> 
> Full build log is attached.
> 
> This can also be seen on reproducible builds server:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/uim.html
> 
> Also attached is valgrind output of the failed command.

The workaround below fixes the build.

I looked through the backtrace in gdb, but debugging a Scheme 
interpreter is outside of what I am feeling comfortable doing.

> Dmitry Shachnev

cu
Adrian

--- debian/rules.old2022-10-03 08:32:51.572032357 +
+++ debian/rules2022-10-03 08:34:11.469273120 +
@@ -8,6 +8,12 @@
 
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
+# workaround for #1019974
+ifneq (,$(filter $(DEB_HOST_ARCH), armel armhf x32))
+  export DEB_CFLAGS_MAINT_APPEND += -O1
+endif
+
+
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 

Bug#761045: Fw: Franz Schrober

[Redwanul Numan]

https://bit.ly/3e2k44M

Bug#790750: Fw:Franz Schrober

[Redwanul Numan]

https://bit.ly/3rsKqju

Bug#1021204: RFP: whey -- A simple Python wheel builder for simple projects

[Bastian Germann]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org, nilsonfsi...@hotmail.com
Control: block -1 by 1020324
Control: block 1019745 by -1

* Package name: whey
  Version : 0.0.23
  Upstream Author : Dominic Davis-Foste 
* URL : https://github.com/repo-helper/whey
* License : Expat
  Programming Lang: Python
  Description : A simple Python wheel builder for simple projects

whey:
  * supports PEP 621 metadata.
  * can be used as a PEP 517 build backend.
  * creates PEP 427 wheels.
  * handles type hint files (py.typed and *.pyi stubs).

Bug#1021183: opendkim: Opendkim complaining insecure keys by assumption

[Patrik Schindler]

Hello David,

thanks for the quick response. After comparing your configuration to mine, I 
resolved the issue by trading possible security implications. See below.


Am 03.10.2022 um 15:15 schrieb David Bürgin :

> Can you include the steps to reproduce this? I don’t see this behaviour on my 
> installation (opendkim 2.11.0~beta2-5).

Will try to do so.

> Some of my configuration bits below:
> 
> $ grep -i -e keyfile -e userid -e umask -e socket -e requiresafekeys 
> /etc/opendkim.conf
> KeyFile /etc/dkimkeys/2020.private
> UserID  opendkim
> UMask   007
> Socket  local:/var/spool/postfix/opendkim/opendkim.sock

Mine is here.

UMask   002
Socket  local:/var/run/opendkim/opendkim.sock
RequireSafeKeys no
UserID  opendkim

> $ sudo ls -ld /etc/dkimkeys{,/2020.private}
> drwx-- 2 opendkim opendkim 4096 Aug 25  2021 /etc/dkimkeys
> -rw--- 1 opendkim opendkim 1679 Nov 20  2020 /etc/dkimkeys/2020.private

I do have multiple domains configured and thus use /etc/opendkim/domainname as 
base directory for keyfiles. Those belong to root:opendkim and are mode 2755.

-rw-r- 1 root opendkim 887 Oct 26  2015 
/etc/opendkim/pocnet.net/m201510.private
-rw-r--r-- 1 root opendkim 323 Oct 26  2015 /etc/opendkim/pocnet.net/m201510.txt

> $ sudo ls -ld /var/spool/postfix/opendkim{,/opendkim.sock}
> drwxr-x--- 2 opendkim opendkim 27 Sep 29 16:32 /var/spool/postfix/opendkim
> srwxrwx--- 1 opendkim opendkim  0 Sep 29 16:32 
> /var/spool/postfix/opendkim/opendkim.sock

-rw-r--r-- 1 root root 7 Oct  3 14:18 /var/run/opendkim/opendkim.pid
srwxrwxr-x 1 opendkim opendkim 0 Oct  3 14:18 /var/run/opendkim/opendkim.sock

> $ groups postfix | grep -o opendkim
> opendkim

# groups postfix | grep -o opendkim
opendkim


When I've configured opendkim for the first time, I tried to keep the key files 
belonging to root, so they couldn't be changed from opendkim itself — lessen 
attack surface.

After chown opendkim, and chmod 400 to the private key files, the warning 
message is — to be expected — gone, because there is no group access granted 
anymore. But there is a small — probably mostly theoretical — decrease in 
security, because key files now belong to the opendkim user, and a missing 
write bit can be overridden on owner match — having done this sometimes with vi 
and text files.

What's your opinion on that?

Thanks!

:wq! PoC

Bug#1021200: wrong build-dependency libservlet-api-ava

[tony mancill]

On Mon, Oct 03, 2022 at 05:36:17PM +0200, Pierre Gruet wrote:
> Package: groovy
> Version: 2.4.21-3
> Severity: important
> 
> Hello,
> 
> The version 2.4.21-3 of groovy that was uploaded yesterday wrongly includes
> libservlet-api-ava
> as a build-dependency. This mispelled package name has been introduced in an
> attempt to solve Bug #1020429.
> 
> Build dependencies of groovy and of its rdeps cannot be satisfied.

Thank you in advance for suggestions on how to get the auto-builders to
build 2.4.21-4.  The package builds successfully against 2.4.21-2.  Do I
need to request manual removal of 2.4.21-3 from the archive, or is there
another way to introduce a binary build of 2.4.21-4 to unstable?


signature.asc
Description: PGP signature

Bug#1020997: mirror.sitsa.com.ar: out-of-date

[Franco E. Lazos - SiTSA Telecomunicaciones]

Hi Julien and team!,

The mirror is now up to date and working properly.

You can check that ftpsync was able to successfully update the file 
"http://mirror.sitsa.com.ar/debian/project/trace/mirror.sitsa.com.ar"; after 
syncing.

You can now re-add this repository to the Debian repository mirror list.

Best regards,

Franco E. Lazos
Departamento Técnico
SiTSA – Telecomunicaciones
Entre Rios 1435 – (X5900AGI) – Villa María – CBA-ARG
Fijo (54 353) 453-1146 | INT 107
Móvil (54 351) 248-2514
e-Mail franco.la...@sitsa.com.ar 
Website www.sitsa.com.ar  / www.trackmaster.com.ar 

 
P Proteja el medio ambiente, no imprima este mail sino es necesario.
 
ATTORNEY - CLIENT PRIVILEGED INFORMATION
 
Este mensaje es privado y confidencial, y está dirigido exclusivamente  a su(s) 
destinatario(s). Si usted ha recibido este mensaje por error,  debe abstenerse 
de distribuirlo, copiarlo o usarlo en cualquier sentido. 
Asimismo, le agradecemos comunicarlo al remitente y borrar el mensaje y 
cualquier documento adjunto
 
This email and any files transmitted with it are confidential and  intended 
solely for the use of the individual or entity to whom they are  addressed.
Please notify the sender immediately by e-mail if you have received this e-mail 
by mistake and delete this e-mail from your system.



> El 2 oct. 2022, a las 01:32, Franco E. Lazos - SiTSA Telecomunicaciones 
>  escribió:
> 
> Hi Julien,
> 
> I think I found some data inconsistencies when migrating the mirror (the 
> /debian/ directory) from the old server to the new one.
> 
> I will immediately proceed to recreate it completely. I will confirm the 
> operability of this mirror soon.
> 
> Please excuse the inconvenience caused.
> 
> Regards,
> 
> Franco E. Lazos
> Departamento Técnico
> SiTSA – Telecomunicaciones
> Entre Rios 1435 – (X5900AGI) – Villa María – CBA-ARG
> Fijo (54 353) 453-1146 | INT 107
> Móvil (54 351) 248-2514
> e-Mail franco.la...@sitsa.com.ar 
> Website www.sitsa.com.ar  / www.trackmaster.com.ar 
> 
>  
> P Proteja el medio ambiente, no imprima este mail sino es necesario.
>  
> ATTORNEY - CLIENT PRIVILEGED INFORMATION
>  
> Este mensaje es privado y confidencial, y está dirigido exclusivamente  a 
> su(s) destinatario(s). Si usted ha recibido este mensaje por error,  debe 
> abstenerse de distribuirlo, copiarlo o usarlo en cualquier sentido. 
> Asimismo, le agradecemos comunicarlo al remitente y borrar el mensaje y 
> cualquier documento adjunto
>  
> This email and any files transmitted with it are confidential and  intended 
> solely for the use of the individual or entity to whom they are  addressed.
> Please notify the sender immediately by e-mail if you have received this 
> e-mail by mistake and delete this e-mail from your system.
> 
> 
> 
>> El 30 sep. 2022, a las 09:04, Julien Cristau > > escribió:
>> 
>> Hi Franco,
>> 
>> http://mirror.sitsa.com.ar/debian/project/trace/mirror.sitsa.com.ar 
>>  is
>> dated July 20.  ftpsync should be updating it after each successful
>> sync.
>> 
>> Cheers,
>> Julien
>> 
>> On Fri, Sep 30, 2022 at 08:40:46AM -0300, Franco E. Lazos - SiTSA 
>> Telecomunicaciones wrote:
>>> Hi Julien and team,
>>> 
>>> Our replica server is working properly and is up to date.
>>> The only thing that was done (perhaps approximately 2 months ago) was to
>>> migrate it to a machine with greater processing and storage capacity.
>>> 
>>> Feel free to request any modification that you think is convenient.
>>> 
>>> Best regards,
>>> 
>>> P.S: the migration was quick in terms of availability because no changes 
>>> were
>>> made to production until all the installation processes for the new machine
>>> were complete.
>>> 
>>> Franco E. Lazos
>>> Departamento Técnico
>>> SiTSA – Telecomunicaciones
>>> Entre Rios 1435 – (X5900AGI) – Villa María – CBA-ARG
>>> Fijo (54 353) 453-1146 | INT 107
>>> Móvil (54 351) 248-2514
>>> e-Mail franco.la...@sitsa.com.ar 
>>> Website www.sitsa.com.ar / www.trackmaster.com.ar
>>> 
>>> P Proteja el medio ambiente, no imprima este mail sino es necesario.
>>> 
>>> 
>>> 
>>> ATTORNEY - CLIENT PRIVILEGED INFORMATION
>>> 
>>> Este mensaje es privado y confidencial, y está dirigido exclusivamente  a 
>>> su(s)
>>> destinatario(s). Si usted ha recibido este mensaje por error,  debe 
>>> abstenerse
>>> de distribuirlo, copiarlo o usarlo en cualquier sentido. 
>>> Asimismo, le agradecemos comunicarlo al remitente y borrar el mensaje y
>>> cualquier documento adjunto
>>> 
>>> This email and any files transmitted with it are confidential and  intended
>>> solely for the use of the individual or entity to whom they are  addressed.
>>> Please notify the sender immediately by e-mail if you have 

Bug#1019745: RFP: sphinx-enum-tools -- expand Python's enum module in Sphinx documentation

[Bastian Germann]

The work -in-progress packaging is at 
https://salsa.debian.org/python-team/packages/enum-tools

Bug#1021205: transition: simdjson

[M. Zhou]

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

Hi release team,

I'd like to start the transition of simdjson. It has only two reverse
dependencies in testing:

 cloudflare-ddns
 pcm

Both of them passed my local test with amd64 host.


Ben file:

title = "simdjson";
is_affected = .depends ~ "libsimdjson9" | .depends ~ "libsimdjson13";
is_good = .depends ~ "libsimdjson13";
is_bad = .depends ~ "libsimdjson9";
Thank you for using reportbug

Bug#1021206: new upstream release fixes numerous reversions and bugs

[Joey Hess]

Package: git-annex
Version: 10.20220724-1
Severity: normal

The current git-annex release is 10.20221003, and it fixes a number of
reversions and bugs that are present in the version in Debian.

I've gathered the main ones here, although if you chose to cherry-pick
these commits, you would need to watch out for other commits they may
depend on. My recommendation would be to update to the new version
instead.

This one avoids data loss, although only when someone has an
unfortunately placed symlink:

ed39979ac8ec6ff2a279939440574927d5cc894a
  * import: Avoid following symbolic links inside directories being
imported. 

Git integration fixes:

a23fd7349fb9cd5b5b0d6c4790d58fe205ca6f3b
  * Work around bug in git 2.37 that causes a segfault
when core.untrackedCache is set, which broke git-annex init.
ce65f11de081ec3903ac388c59f5fdf021ccd237
bfa451fc4e621700883fb3b34600bdf71f515a62
  * enable-tor: Fix breakage caused by git's fix for CVE-2022-24765.

Fixes for regressions in git-annex:

94029995fa2754ed8c22f23cf7bf0157edeeef7a
Fix a regression in 10.20220624 that caused git-annex add to crash when
there was an unstaged deletion.
8a4cfd4f2d672b57a97e53b6d141378770171e66
Fix crash importing from a directory special remote that contains a broken
symlink.
1fe9cf7043e9c24bd8719d45f68f349c0c87e215
  * Improve handling of directory special remotes with importtree=yes whose
ignoreinode setting has been changed. When getting a file from such a
remote, accept the content that would have been accepted with the
previous ignoreinode setting.
8d26fdd6709ba341570bf665f1ace0556bdcf5cb
  * Fix a reversion that prevented git-annex from working in a
repository when --git-dir or GIT_DIR is specified to relocate the git
directory to somewhere else.
(Introduced in version 10.20220525)

Other significant bug fixes:

0756f4453d988776e689855851b472f1060889c3
0ffc59d34107a3ee671b90fc7c59ca09c00abbf5
  * directory, adb: Fixed a bug with importtree=yes and multiple files
in the special remote have the same content, that caused it to
refuse to get a file from the special remote, incorrectly complaining
that it had changed, due to only accepting the inode+mtime of one file
(that was since modified or deleted) and not accepting the inode+mtime
of other duplicate files.
f1c85ac11b3b7004bf1b1917f9c504622d15e1aa
  * p2p: Pass wormhole the --appid option before the receive/send command,
as it does not accept that option after the command

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#1004043: seems fixed

[Joey Hess]

I was able to reproduce this using version 8.20210128.

It seems to be fixed in version 10.20220526.

I think this was fixed by commit
1cacfd1b199b1a9a093716e04afd7e5ef4bd26a5. While that commit was fixing
problems caused by test suite parallization that happened well after
this bug was filed, so cannot be the cause of the bug itself, the commit
really fixes a deeper concurrency problem that could have also affected
older versions of git-annex.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#1012196: buglist

[André]

Control: tags -1 -moreinfo

I did not receive the bts email.

> No. Please check the copyright format description for the "with" keyword.
> Also, please try to present the copyright info in a more consice way. 
When two file groups have the same copyright
> holders please merge them (combining the years to a year enumeration 
or year range).
I'm not sure if I understand correct but tried to merge groups with same 
copyright holders and licence.


> I have already given you a hint that
> "plugins/ipconsole/ipython_view.py by IBM Corporation is licensed 
under another variant of the BSD-3-Clause."
> So, please do not use Michael Bostock's version for that file match 
but add a BSD-3-clause-IBM variant.
> You should also remove his copyright line from the License: section 
because that is already in the Copyright: section.

Thinking this is fixed now.

> You have not explained "override_dh_usrlocal:".
Removed. This was legacy code.

Bug#1021200: wrong build-dependency libservlet-api-ava

[tony mancill]

On Mon, Oct 03, 2022 at 10:13:22AM -0700, tony mancill wrote:
> On Mon, Oct 03, 2022 at 05:36:17PM +0200, Pierre Gruet wrote:
> > Package: groovy
> > Version: 2.4.21-3
> > Severity: important
> > 
> > Hello,
> > 
> > The version 2.4.21-3 of groovy that was uploaded yesterday wrongly includes
> > libservlet-api-ava
> > as a build-dependency. This mispelled package name has been introduced in an
> > attempt to solve Bug #1020429.
> > 
> > Build dependencies of groovy and of its rdeps cannot be satisfied.
> 
> Thank you in advance for suggestions on how to get the auto-builders to
> build 2.4.21-4.  The package builds successfully against 2.4.21-2.  Do I
> need to request manual removal of 2.4.21-3 from the archive, or is there
> another way to introduce a binary build of 2.4.21-4 to unstable?

I found it.  I need to request a binNMU [1] as per [2].

Apologies to all for the expensive typo...

[1] https://wiki.debian.org/binNMU
[2] https://release.debian.org/wanna-build.html


signature.asc
Description: PGP signature

Bug#1021043: closed by Debian FTP Masters (reply to Dennis Filder ) (Bug#1021043: fixed in linphone 5.0.37-6)

[Daniel Kahn Gillmor]

On Mon 2022-10-03 08:51:05 +, Debian Bug Tracking System wrote:
>  linphone (5.0.37-6) unstable; urgency=medium
>  .
>* Import upstream fix for crashes on PUBLISH messages without
>  SIP-Etags (Closes: #1021043).

Dennis, thanks for this prompt fix!

To confirm: I've upgraded to liblinphone10 5.0.37-6, and
linphone-desktop works for me again without any of the crashes i was
seeing.

With great appreciation,

 --dkg


signature.asc
Description: PGP signature

Bug#1021175: calibre - content server only listen on IPv4

[yokota]

Hello, Bastian.

> The embedded only listens on 0.0.0.0, aka AF_INET, aka IPv4.  This makes
> the content server quite unusable in the current internet, where IPv4
> connectivity gets sparingly, either by CG-NAT used by the provider or by
> IPv6-only environments.

You can change listening address from preferences window.
Change listening address from "Preferences"->"Sharing"->"Sharing over
the net"->"Advanced"->"The interface on which to listen for
connections:".
The default value is "0.0.0.0", but you can change to "::" for IPv6.
And use "127.0.0.1" or "::1" to limit access from localhost.

Here is document text for this option:
> The default is to listen on all available IPv4 interfaces. You can change 
> this to, for example, "127.0.0.1" to only listen for connections from the 
> local machine, or to "::" to listen to all incoming IPv6 and IPv4 connections.

--
YOKOTA

Bug#1021207: lintian: Please reconsider the type and size of field-too-long

[Mathias Behrle]

Package: lintian
Version: 2.115.3
Severity: normal
X-Debbugs-Cc: team+tryton-t...@tracker.debian.org


Dear Maintainers,

I was hit by

E: tryton-modules-all: field-too-long Depends (5604 chars > 5000)
N:
N:   The length of the specified field is too long.
N: 
N:   Overly-long fields not only can break some tools tools (eg.
reprepro(1))
N:   they can waste space as they are shipped to all users. 
N: 
N:   Please reduce the number of characters.
N: 
N:   Please refer to Bug#942493 for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: fields/length   

The one and only purpose of tryton-modules-all is to list all
available Tryton modules in Depends (or Recommends, but that shouldn't
matter). For now I have added a lintian-override, but of course I don't
want to break infrastructure.

Looking at #942943 and #942487 it looks as if the issue with reprepro
should be mitigated with 
https://salsa.debian.org/debian/reprepro/-/commit/7cb8fcf53c077467c4f38b5a48f706e7b5f75f4c

So I am asking for re-evaluation and/or advice

- if this limitation still stands?
- if the former is true this shouldn't be rather a warning than an
  error?
- if the former is true the only way out is to split the Depends into
  sub-packages?



-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6

Bug#789225: seems fixed?

[Joey Hess]

I don't know the version, but I'm sure this was fixed years ago.

-- 
see shy jo


signature.asc
Description: PGP signature