Bug#1014272: src:linux: sign-file: correct error handling

[Salvatore Bonaccorso]

Hi Ansgar,

On Sun, Jul 03, 2022 at 11:47:51AM +0200, Ansgar wrote:
> Source: linux
> Version: 5.18.5-1
> Severity: normal
> Tags: upstream
> Control: found -1 4.19.208-1 5.10.84-1
> 
> The functions CMS_final, i2d_CMS_bio_stream, i2d_PKCS7_bio and
> BIO_free all return 1 for success or 0 for failure. The old check
> for a value less than 0 would never catch an error.
> 
> I tried signing a kernel module with the patched sign-file and that
> still worked.

Can you forward your patch to upstream?

Regards,
Salvatore

Bug#1014438: mark zstd Multi-Arch: foreign

[Helmut Grohne]

Package: zstd
Version: 1.5.2+dfsg-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

The zstd package provides command line utilities only. Like any other
compressor, it's behaviour does not depend on the architecture used to
run it. As such, it should be marked Multi-Arch: foreign. The lack of
this marking currently causes zstd to be cross graded when a foreign
architecture package depends on it, which happens to break rebootstrap
(due to suboptimal design choices there). Please consider applying the
attached patch to ease the present situation.

Helmut
diff --minimal -Nru libzstd-1.5.2+dfsg/debian/changelog 
libzstd-1.5.2+dfsg/debian/changelog
--- libzstd-1.5.2+dfsg/debian/changelog 2022-04-11 16:50:14.0 +0200
+++ libzstd-1.5.2+dfsg/debian/changelog 2022-07-06 06:59:04.0 +0200
@@ -1,3 +1,10 @@
+libzstd (1.5.2+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark zstd Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 06 Jul 2022 06:59:04 +0200
+
 libzstd (1.5.2+dfsg-1) unstable; urgency=medium
 
   * New upstream release (Closes: #1008165):
diff --minimal -Nru libzstd-1.5.2+dfsg/debian/control 
libzstd-1.5.2+dfsg/debian/control
--- libzstd-1.5.2+dfsg/debian/control   2022-03-30 15:13:12.0 +0200
+++ libzstd-1.5.2+dfsg/debian/control   2022-07-06 06:58:54.0 +0200
@@ -41,6 +41,7 @@
 
 Package: zstd
 Architecture: any
+Multi-Arch: foreign
 Section: utils
 Depends: ${misc:Depends},
  ${shlibs:Depends}

Bug#1014437: kmod: annotate zstd build dependency

[Helmut Grohne]

Source: kmod
Version: 30+20220630-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Hi Marco,

the addition of zstd happens to break rebootstrap, due to suboptimal
design choices in rebootstrap. zstd (wrongly) isn't Multi-Arch: foreign,
so kmod's dependncy cross grades zstd, which is bad. While the issue
also is elsewhere, I'd appreciate if you could fix this in the simplest
possible way: Annotate the dependency  as it really is only
used for testing. I'll also look into addressing the issue elsewhere.

Thanks

Helmut
diff --minimal -Nru kmod-30+20220630/debian/changelog 
kmod-30+20220630/debian/changelog
--- kmod-30+20220630/debian/changelog   2022-07-03 13:28:18.0 +0200
+++ kmod-30+20220630/debian/changelog   2022-07-06 06:51:27.0 +0200
@@ -1,3 +1,10 @@
+kmod (30+20220630-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Annotate zstd dependency with . (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 06 Jul 2022 06:51:27 +0200
+
 kmod (30+20220630-1) unstable; urgency=medium
 
   * New upstream snapshot.
diff --minimal -Nru kmod-30+20220630/debian/control 
kmod-30+20220630/debian/control
--- kmod-30+20220630/debian/control 2022-07-03 13:28:07.0 +0200
+++ kmod-30+20220630/debian/control 2022-07-06 06:51:27.0 +0200
@@ -6,7 +6,7 @@
   autoconf, automake, libtool,
   liblzma-dev,
   libssl-dev,
-  libzstd-dev, zstd,
+  libzstd-dev, zstd ,
   gtk-doc-tools, xsltproc,
 Standards-Version: 4.6.1.0
 Rules-Requires-Root: no

Bug#950307: YAML syntax highlight is broken on multiline blocks

[Pavel Shumskii]

On Fri, 31 Jan 2020 11:14:34 +0300 Vladimir K  wrote:
> Package: mc
> Version: 3:4.8.24-2
> Severity: normal
> Tags: upstream
>
> Dear Maintainer, in the newest version of mcedit syntax highlight for YAML
> inline block highlight is started after '>' or '|' directives, but does
not end
> until EOF.
>
> Instead it should end after encountering any of:
>   - an empty line
>   - a line with the same indent as the key of current value
>   - a line with less indent than the first line of inline block
>
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (900, 'testing'), (400, 'unstable'), (300, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_USER
> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8),
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages mc depends on:
> ii  libc6 2.29-9
> ii  libext2fs21.45.5-2
> ii  libglib2.0-0  2.62.4-1+b1
> ii  libgpm2   1.20.7-5+b1
> ii  libslang2 2.3.2-4
> ii  libssh2-1 1.8.0-2.1
> ii  mc-data   3:4.8.24-2
>
> Versions of packages mc recommends:
> ii  mime-support  3.64
> ii  perl  5.30.0-9
> ii  unzip 6.0-25
>
> Versions of packages mc suggests:
> ii  arj  3.10.22-23
> ii  bzip21.0.8-2
> pn  dbview   
> pn  djvulibre-bin
> pn  epub-utils   
> ii  evince [pdf-viewer]  3.34.1-1+b1
> ii  file 1:5.38-4
> ii  genisoimage  9:1.1.11-3.1
> pn  gv   
> ii  imagemagick  8:6.9.10.23+dfsg-2.1+b2
> ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+b2
> pn  libaspell-dev
> ii  lynx 2.9.0dev.4-1
> ii  mupdf [pdf-viewer]   1.15.0+ds1-1+b1
> pn  odt2txt  
> ii  poppler-utils0.71.0-6
> ii  python   2.7.17-2

Hello.

I am trying to fix yaml syntax highliting for multiline blocks.
There is the process:
https://github.com/kran0/mc/blob/improve-mcedit-yaml.syntax/misc/syntax/yaml.syntax

Please, test this variant and write what you think about it. To test it,
just place yaml.syntax to ~/.local/share/mc/mcedit/yaml.syntax

Thanks a lot.

PS.
My PR is: https://github.com/MidnightCommander/mc/pull/170
And i have commented the bug entry:
https://midnight-commander.org/ticket/4059

Bug#1014436: coreutils: date +%ON doesn't use alternate representation when available, always writes Arabic digits

[наб]

Package: coreutils
Version: 8.32-4.1
Severity: normal
Tags: l10n

Dear Maintainer,

Given
  $ localedef -i fa_IR -c -f UTF-8 "${locdir}fa_IR.UTF-8"
the Farsi date is mostly as-expected, except %ON is /not/ Arabic-Indic,
instead falling to the %N-equivalent format:
  $ LOCPATH="${locdir}" LC_ALL=fa_IR.UTF-8 date +"%EX.%ON"
  ۰۵:۵۰:۰۷.268457738
whereas I'd (naively, admittedly, but this holds for /all/ other
 %O-accepting (so, like, numeric) format specifiers)
expect it to be
  $ LOCPATH="${locdir}" LC_ALL=fa_IR.UTF-8 /bin/printf \
'۰۵:۵۰:۰۷.%Id\n' 268457738
  ۰۵:۵۰:۰۷.۲۶۸۴۵۷۷۳۸
right?

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.2.53-10
ii  libattr1 1:2.4.48-6
ii  libc62.31-13+deb11u3
ii  libgmp10 2:6.2.1+dfsg-1+deb11u1
ii  libselinux1  3.1-3

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1014392: mingw-w64: ftbfs on riscv64(error: #error Unknown CPU architecture!)

[Paul Wise]

On Wed, 2022-07-06 at 09:27 +0800, Bo YU wrote:

> To my surprise this definition doesn't seem to take effect,
> Either define or undef can build riscv64 package here.

Probably the code that uses the definition is not adequately tested
during the package build, if it was then there should be failure.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1013082: wine: CombineZP doesn't display a picture

[Michael Gilbert]

control: tag -1 moreinfo

Günter Frenz wrote:
> I'm using CombineZP (https://combinezp.software.informer.com/1.0/) with wine. 
> Since the
> latest update the pictures are no longer displayed.

Are you saying it worked correctly with wine 6.0.3~repack-1?

If so, are you able to test the 6.x wine-development packages from
snapshot.debian.org [0] to
determine when the regression began?

Best wishes,
Mike

[0] https://snapshot.debian.org/package/wine-development/

Bug#1014259: sscg: ftbfs on riscv64: (create_csr_test TIMEOUT 30.10s killed by signal 15 SIGTERM)

[肖盛文]

Hi,

    This question is not about of run parallel test in dh_auto_test.

I build the sscg package in my riscv machine[1], it build successed.

   dh_auto_test
    cd obj-riscv64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 
ninja test

[0/1] Running all tests.
 1/10 generate_serial_test  OK    0.07s
 2/10 init_bignum_test  OK    0.05s
 3/10 dhparams_test_512_2   OK    2.98s
 4/10 dhparams_test_512_5   OK    7.75s
 5/10 generate_rsa_key_test OK   15.90s
 6/10 create_csr_test   OK   22.32s
 7/10 dhparams_test_1024_2  OK   14.68s
 8/10 create_ca_test    OK   32.33s
 9/10 named_dhparams_test   OK   10.70s
10/10 dhparams_test_1024_5  OK   18.90s

Ok: 10
Expected Fail:  0
Fail:   0
Unexpected Pass:    0
Skipped:    0
Timeout:    0

Then I do a manual dh_auto_test in the build dir, use top to watch cpu:

top - 08:12:21 up 5 days, 20:18,  3 users,  load average: 0.23, 0.18, 0.18
任务: 112 total,   2 running, 110 sleeping,   0 stopped,   0 zombie
%Cpu0  :  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi, 0.0 si,  
0.0 st
%Cpu1  :  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi, 0.0 si,  
0.0 st
%Cpu2  :100.0 us,  0.0 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi, 0.0 si,  
0.0 st
%Cpu3  :  0.0 us,  0.7 sy,  0.0 ni, 99.3 id,  0.0 wa,  0.0 hi, 0.0 si,  
0.0 st

MiB Mem :  15986.5 total,  14316.6 free,    267.5 used,   1402.5 buff/cache
MiB Swap:  0.0 total,  0.0 free,  0.0 used.  15482.0 avail Mem

 进程号 USER  PR  NI    VIRT    RES    SHR    %CPU  %MEM TIME+ COMMAND
  31066 atzlinux  20   0    5080   4148   3516 R 100.0   0.0 0:08.46 
/home/atzlinux/sscg/obj-riscv64-linux-gnu/create_ca_test

  31068 root  20   0    8764   2988   2460 R   1.0   0.0 0:00.10 top
 12 root  20   0   0  0  0 I   0.3   0.0 0:04.10 
[rcu_sched]


The test process only use one CPU core in the whole test,

so this dh_auto_test is not run in parallel mode.


I suggest to trigger one rebuild on buildd to see what happened:

https://buildd.debian.org/auth/giveback.cgi?pkg=sscg=riscv64=sid


If it still has "create_csr_test TIMEOUT", I also agree:

" (2) patch mason.build to add longer timeout for failed tests."


diff --git a/meson.build b/meson.build
index 3b2a634..c42ee28 100644
--- a/meson.build
+++ b/meson.build
@@ -142,7 +142,7 @@ create_csr_test = executable(
 dependencies: [ crypto ],
 install:false,
 )
-test('create_csr_test', create_csr_test)
+test('create_csr_test', create_csr_test, timeout: 60)

 generate_rsa_key_test = executable(
 'generate_rsa_key_test',


在 2022/7/6 03:19, Boyuan Yang 写道:

Yes, but we need another package upload anyway.

Thanks,
Boyuan


[1] https://linux-hardware.org/?probe=7b1c72c3e7

Thanks,

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014392: mingw-w64: ftbfs on riscv64(error: #error Unknown CPU architecture!)

[Bo YU]

Hi,
On Tue, Jul 05, 2022 at 10:47:26PM +0800, Paul Wise wrote:

On Tue, 2022-07-05 at 17:42 +0800, Bo YU wrote:


The patch attached is to fix the issue and I can build the package
on my locally real riscv64 hardware(Unmatched board) with it.

...

+#elif defined(__riscv) && __riscv_xlen == 64
+# define WORDS_BIGENDIAN


I don't think this patch is correct, riscv64 is little-endian.


Aha, yeah, sorry my bad.

To my surprise this definition doesn't seem to take effect,
Either define or undef can build riscv64 package here.

Bo


--
bye,
pabs

https://wiki.debian.org/PaulWise




--
Best Regards,

--- a/mingw-w64-tools/widl/include/basetsd.h
+++ b/mingw-w64-tools/widl/include/basetsd.h
@@ -36,7 +36,7 @@
  * 64-bit.
  */
 
-#if (defined(__x86_64__) || defined(__powerpc64__) || defined(__aarch64__) || defined(__sparc64__) || defined(__ia64__) || defined(__s390x__)) && !defined(_WIN64)
+#if (defined(__x86_64__) || defined(__powerpc64__) || defined(__aarch64__) || defined(__sparc64__) || defined(__ia64__) || defined(__s390x__) || defined(__riscv) && __riscv_xlen == 64) && !defined(_WIN64)
 #define _WIN64
 #endif
 
@@ -299,6 +299,8 @@
 # undef  WORDS_BIGENDIAN
 #elif defined(__s390__) || defined(__s390x__)
 # define WORDS_BIGENDIAN
+#elif defined(__riscv) && __riscv_xlen == 64
+# undef WORDS_BIGENDIAN
 #elif defined(__hppa__)
 # undef  WORDS_BIGENDIAN
 #elif !defined(RC_INVOKED) && !defined(__WIDL__) && !defined(__midl)


signature.asc
Description: PGP signature

Bug#1014432: instaloader: Please import new upstream release

[Nilson Silva]

Hello Bastian!

It's already in salsa:
https://salsa.debian.org/debian/instaloader

Thanks in advance!


Nilson F. Silva


De: Bastian Germann 
Enviado: terça-feira, 5 de julho de 2022 19:47
Para: sub...@bugs.debian.org 
Assunto: Bug#1014432: instaloader: Please import new upstream release

Source: instaloader
Version: 4.9+0+ds-1

Version 4.9.2 is available. Please import it into Debian.

Bug#1014435: libvirt-daemon-system-systemd: virbr0 default fails to connect

[Tim McConnell]

Package: libvirt-daemon-system-systemd
Version: 8.4.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

Virbr0 won't connect to external network.It did once, I was able to install
Debian from a net install image. Now it tells me the Virtual Machine can't
connect.
It shows as active in Virt-manager. IP ADDR shows the connection and NFTables
has a table for it. All the documentation I can find states the connection to
Virbr0 is supposed to work, what am I missing?


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

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

Versions of packages libvirt-daemon-system-systemd depends on:
ii  systemd-container  251.2-7
ii  systemd-sysv   251.2-7

libvirt-daemon-system-systemd recommends no packages.

libvirt-daemon-system-systemd suggests no packages.

-- no debconf information

Bug#844688: Firefox - compile with jack audio output support

[riveravaldez]

Any chance of this happening?

Or should we _abandon all hope_ ?

Thanks a lot!

Bug#1014434: gitbrute: strange build failure on ppc64el with gccgo

[Steve Langasek]

Package: gitbrute
Version: 0~14-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear maintainer,

The gitbrute package is failing to build in Ubuntu kinetic on ppc64el with a
strange error about a binary with a non-standard build ID length:

[...]
   dh_strip -a
debugedit: Cannot handle 83-byte build ID
dh_strip: error: debugedit --build-id --build-id-seed=gitbrute/0\~14-1 
debian/gitbrute/usr/bin/gitbrute returned exit code 1
[...]

  (https://launchpad.net/ubuntu/+source/gitbrute/0~14-1/+build/23574308)

Looking at the package I see that it is build-depending on gccgo-go.  Almost
all go packages in the archive are built using golang-go, not gccgo-go; the
latter is not a default in the golang ecosystem, and not as well-supported. 
I'm not sure if there's a specific reason you are using gccgo-go, but
switching the build-dependency to golang-go fixes this build failure.

I have not reproduced this specific build failure on Debian, only Ubuntu. 
However, I see that the current build failures in Ubuntu are with gccgo-go
11.3.0-3, whereas the previous successful build in Debian was with gccgo-go
11.2.0-10.  So it is likely that the build failure now also occurs in
unstable, in which case this bug should be considered severity: serious.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gitbrute-0~14/debian/control gitbrute-0~14/debian/control
--- gitbrute-0~14/debian/control2021-09-29 14:08:52.0 -0700
+++ gitbrute-0~14/debian/control2022-07-05 16:06:49.0 -0700
@@ -2,7 +2,7 @@
 Section: vcs
 Priority: optional
 Maintainer: Adam Borowski 
-Build-Depends: debhelper-compat (=13), gccgo-go
+Build-Depends: debhelper-compat (=13), golang-go
 Standards-Version: 4.6.0
 Homepage: https://github.com/bradfitz/gitbrute
 Vcs-Git: https://github.com/kilobyte/gitbrute -b debian

Bug#1012741: Reproduced

[Matthias Maier]

Dear all,

I think this is an issue with the Hardware token and not with the
userland libraries and tools.

More specifically, I am able to reproduce this bug with

Device type: YubiKey 4
Firmware version: 4.3.7

on a Gentoo system, whereas "reproduce.sh" succeeds with
a newer Yubikey:

Device type: YubiKey 5 NFC
Firmware version: 5.4.3

Software and versions:

openssl-1.1.1o
yubico-piv-tool-2.3.0

Best,
Matthias

Bug#1014424: exim4-config: recieve warnings about messages being delayed by Smarthost

[tmcconnell168]

On Tue, 2022-07-05 at 21:53 +0200, Marc Haber wrote:
> On Tue, Jul 05, 2022 at 02:46:25PM -0500,
> tmcconnell...@gmail.com wrote:
> > Not sure if it resolves, I use dww and it opens the help files
> > using
> > the DebianTim.midcoip.net part but if I put that
> > (mail.DebianTim.midcoip.net) into a browser that address does not.
> > But
> > I didn't configure it, Debian did when I installed it? 
> 
> Debian asks for the smarthost and suggests a default. That default is
> wrong for you. Please fix that with dpkg-reconfigure -plow exim4-
> config.
> 
> Greetings
> Marc
> 
> 
Well now the message is frozen? 
Message 1o8Jxl-007SqX-3Q has been frozen.
The sender is .

The following address(es) have yet to be delivered:
  sur...@popcon.debian.org: remote host address is the local host

Bug#1014432: instaloader: Please import new upstream release

[Bastian Germann]

Source: instaloader
Version: 4.9+0+ds-1

Version 4.9.2 is available. Please import it into Debian.

Bug#834724:

[Roma Gabo]

1000261835642

Get Outlook for Android

Bug#1004587: closed by Debian FTP Masters (reply to Timo Röhling ) (Bug#1004587: fixed in pyglet 1.5.26+ds-1)

[Sebastian Ramacher]

Control: reopen -1

As the dependencies are hard-coded in Depends, the dependencies also
need to be updated.

Cheers

On 2022-07-01 17:21:06 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:pyglet package:
> 
> #1004587: pyglet: FTBFS with ffmpeg 5.0
> 
> It has been closed by Debian FTP Masters  
> (reply to Timo Röhling ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Timo Röhling 
> ) by
> replying to this email.
> 
> 
> -- 
> 1004587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004587
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Fri, 01 Jul 2022 17:19:42 +
> From: Debian FTP Masters 
> To: 1004587-cl...@bugs.debian.org
> Subject: Bug#1004587: fixed in pyglet 1.5.26+ds-1
> Reply-To: Timo Röhling 
> Message-Id: 
> 

> Date: Sun, 30 Jan 2022 20:35:53 +0100
> From: Sebastian Ramacher 
> To: Debian Bug Tracking System 
> Subject: pyglet: FTBFS with ffmpeg 5.0
> Message-ID: 
> 
> Source: pyglet
> Version: 1.5.14-2
> Severity: important
> X-Debbugs-Cc: sramac...@debian.org
> Tags: sid bookworm ftbfs
> Usertags: ffmpeg5.0
> 
> pyglet FTBFS with ffmpeg 5.0 (available in experimental):
> |dh_auto_test -O--buildsystem=pybuild
> | I: pybuild base:237: cd 
> /<>/.pybuild/cpython3_3.10_pyglet/build; python3.10 -m pytest 
> >/dev/null 2>&1; cd /<>/.pybuild/cpython3_3.10_pyglet/build; 
> xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac 
> +extension GLX +render -noreset" python3.10 -m pytest -v -k "not interactive 
> and not PulseAudio and not test_pulse and not test_player_play and not 
> test_player_play_multiple and not test_player_silent_audio_driver and not 
> test_freetype_face and not test_fontconfig and not test_linux_fontconfig and 
> not test_driver and not test_openal and not ClockTimingTestCase" 
> --ignore=tests/interactive
> | = test session starts 
> ==
> | platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
> /usr/bin/python3.10
> | cachedir: .pytest_cache
> | rootdir: /<>
> | collecting ... collected 400 items / 5 errors / 87 deselected / 308 selected
> 
> |  ERRORS 
> 
> | _ ERROR collecting 
> .pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_directsound.py
>  _
> | tests/integration/media/test_directsound.py:11: in 
> | from pyglet.media.codecs import AudioFormat
> | pyglet/media/__init__.py:143: in 
> | add_default_media_codecs()
> | pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
> | if have_ffmpeg():
> | pyglet/media/codecs/__init__.py:118: in have_ffmpeg
> | from . import ffmpeg_lib
> | pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
> | from .libavcodec import *
> | pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
> | from . import libavutil
> | pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in 
> | avutil.av_frame_get_best_effort_timestamp.restype = c_int64
> | /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__
> | func = self.__getitem__(name)
> | /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__
> | func = self._FuncPtr((name_or_ordinal, self))
> | E   AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined 
> symbol: av_frame_get_best_effort_timestamp
> | _ ERROR collecting 
> .pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_player.py _
> | tests/integration/media/test_player.py:11: in 
> | from pyglet.media import Player
> | pyglet/media/__init__.py:143: in 
> | add_default_media_codecs()
> | pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
> | if have_ffmpeg():
> | pyglet/media/codecs/__init__.py:118: in have_ffmpeg
> | from . import ffmpeg_lib
> | pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
> | from .libavcodec import *
> | pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
> | from . import libavutil
> | pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in 
> | avutil.av_frame_get_best_effort_timestamp.restype = c_int64
> | /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__
> | func = self.__getitem__(name)
> | /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__
> | func = self._FuncPtr((name_or_ordinal, self))
> | E   AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined 
> symbol: av_frame_get_best_effort_timestamp
> | _ ERROR collecting 
> .pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_pulse.py _
> | tests/integration/media/test_pulse.py:12: in 
> | from pyglet.media.drivers.pulse import interface
> | pyglet/media/drivers/pulse/__init__.py:36: in 
> | from 

Bug#1014431: popularity-contest: automatically create hostid if not specified in popularity-contest.conf

[Ansgar]

Package: popularity-contest
Version: 1.73
Severity: wishlist

It would be nice if it was not required to have host-specific data in
the configuration file (MY_HOSTID).

If no MY_HOSTID is specified, popularity-contest could for example
generate an application-specific MY_HOSTID from the machine-id as
described for libsystemd's `sd_id128_get_machine_app_specific`
function (i.e., HMAC-SHA256 of a application ID for
popularity-contents keyed by the machine-id).

Ansgar

Bug#1014430: openssl-ibmca: Import new upstream version

[Bastian Germann]

Package: openssl-ibmca
Version: 1.4.0-1

Please update the package to a later version to make the OpenSSL 3.0 provider 
available.

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Diederik de Haas]

On Tuesday, 5 July 2022 21:55:54 CEST Michael wrote:
> and for your request:

Sorry I wasn't clear in my request.

> > and eventually guest processes start to randomly crash, e.g.:
> > 
> > Jun 30 20:17:01 vmguest kernel: traps: sh[250946] general protection fault
> > ip:7fb0c341708e sp:7ffec3154378 error:0 in
> > libc-2.31.so[7fb0c33a6000+14b000]
> > Jul 01 00:00:02 vmguest kernel: traps: hostname[253617] general protection
> > fault ip:7f905f2b24a6 sp:7fff44a30e30 error:0 in
> > libc-2.31.so[7f905f299000+14b000]
> > Jul 01 00:53:01 vmguest kernel: traps: wget[254290] general protection
> > fault ip:7f934bc23fda sp:7ffd716954d0 error:0 in
> > libtasn1.so.6.6.0[7f934bc1a000+c000]

I assumed these errors occurred in 1 boot session and having the FULL dmesg/
kern.log from *that* session would be useful.
Don't 'grep' the messages which you think are relevant. Often times there are 
other messages which give important clues to experts (which I am not), which 
seem irrelevant/harmless to you and me.
I'm guessing this bug should be sent upstream and they will (highly) likely 
ask for a full dmesg/kernel log.
(I'm merely trying to collect as much useful information as possible)

HTH,
  Diederik

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

Bug#1014429:

[Andreas Hasenack]

Ok, my current theory is this, please poke holes:

autofs and nfs-common are both unpacked. Then the setup begins.

If autofs is setup first, it means systemctl daemon-reload will be
called at the end, and that will run all the generators. Since
nfs-common is already unpacked, it's generator is on disk, and will be
run.

But /etc/nfs.conf doesn't exist yet: it's produced by ucf in
nfs-common's postinst. That means the generator will not be able to
fetch the pipefs-directory config, and will just exit silently. But
autofs is being started, and it requires rpc_pipefs.target, but at
this time, that target unit is the one from the nfs-common package
that will trigger the var-lib-nfs-rpc_pipefs.mount unit.

Then nfs-common is setup. This time, it will produce /etc/nfs.conf,
and when systemctl daemon-reload is called and the generator run, it
will find /etc/nfs.conf, and the pipefs-directory setting, and see
it's different from the default, and produce the generated target and
mount files, which will mount rpc_pipefs in /run/rpc_pipefs now.

Bug#1011443: faker,ruby-faker: error when trying to install together

[Antonio Terceiro]

On Tue, Jul 05, 2022 at 06:44:15PM +0200, Timo Röhling wrote:
> On Mon, 23 May 2022 01:58:56 +0200 Andreas Beckmann  wrote:
> > Package: faker,ruby-faker
> > Severity: serious
> > Tags: sid bookworm
> > User: trei...@debian.org
> > Usertags: edos-file-overwrite
> > Control: found -1 0.9.3-0.1
> > Control: found -1 2.20.0-1
> > 
> > [...]
> > Here is a list of files that are known to be shared by both packages
> > (according to the Contents file for sid/amd64, which may be
> > slightly out of sync):
> > 
> >   /usr/bin/faker
> > 
> > This bug is assigned to both packages. If you, the maintainers of
> > the two packages in question, have agreed on which of the packages will
> > resolve the problem please reassign the bug to that package.
> I'm posting to d-devel because I failed to make contact with the
> Ruby Team directly:
> 
> ruby-faker primarily ships a Ruby module while faker's sole purpose
> is the faker executable, so I believe ruby-faker should yield.
> There are two reverse dependencies:
> 
> - ruby-devise-two-factor builds fine without /usr/bin/faker in
>   ruby-faker
> 
> - ruby-omniauth-openid-connect FTBFS for unrelated reasons with and
>   wihout /usr/bin/faker
> 
> If the Ruby Team agrees with my analysis, I'd appreciate it if
> someone could upload a fixed version (I am not a team member).

I just did that. Remember that you need to add Breaks:/Replaces: on your
package for upgrades to work.


signature.asc
Description: PGP signature

Bug#1014429: nfs-utils: rpc_pipefs mounted twice

[Andreas Hasenack]

Package: nfs-utils
Version: 1:2.6.1-2
Severity: normal

Dear Maintainer,

on a fresh debian sid VM, if I "apt install autofs -y", at the end I
will have rpc_pipefs mounted in two places:

root@sid-autofs-nfs-common:~# mount -t rpc_pipefs

root@sid-autofs-nfs-common:~# apt install autofs -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  keyutils libevent-core-2.1-7 libldap-2.5-0 libldap-common
libnfsidmap1 libsasl2-2 libsasl2-modules libsasl2-modules-db
nfs-common rpcbind
Suggested packages:
  libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimdal
libsasl2-modules-ldap libsasl2-modules-otp libsasl2-modules-sql
open-iscsi watchdog
The following NEW packages will be installed:
  autofs keyutils libevent-core-2.1-7 libldap-2.5-0 libldap-common
libnfsidmap1 libsasl2-2 libsasl2-modules libsasl2-modules-db
nfs-common rpcbind
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,408 kB of archives.
After this operation, 4,306 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 autofs amd64
5.1.8-1+b1 [292 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 libevent-core-2.1-7
amd64 2.1.12-stable-5+b1 [137 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libsasl2-modules-db
amd64 2.1.28+dfsg-6 [38.4 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 libsasl2-2 amd64
2.1.28+dfsg-6 [77.3 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libldap-2.5-0 amd64
2.5.12+dfsg-2 [227 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 libnfsidmap1 amd64
1:2.6.1-2 [85.0 kB]
Get:7 http://deb.debian.org/debian sid/main amd64 rpcbind amd64
1.2.6-3 [52.0 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 keyutils amd64
1.6.3-1 [61.4 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 nfs-common amd64
1:2.6.1-2 [282 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 libldap-common all
2.5.12+dfsg-2 [72.2 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 libsasl2-modules
amd64 2.1.28+dfsg-6 [84.2 kB]
Fetched 1,408 kB in 1s (2,215 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package autofs.
(Reading database ... 23161 files and directories currently installed.)
Preparing to unpack .../00-autofs_5.1.8-1+b1_amd64.deb ...
Unpacking autofs (5.1.8-1+b1) ...
Selecting previously unselected package libevent-core-2.1-7:amd64.
Preparing to unpack .../01-libevent-core-2.1-7_2.1.12-stable-5+b1_amd64.deb ...
Unpacking libevent-core-2.1-7:amd64 (2.1.12-stable-5+b1) ...
Selecting previously unselected package libsasl2-modules-db:amd64.
Preparing to unpack .../02-libsasl2-modules-db_2.1.28+dfsg-6_amd64.deb ...
Unpacking libsasl2-modules-db:amd64 (2.1.28+dfsg-6) ...
Selecting previously unselected package libsasl2-2:amd64.
Preparing to unpack .../03-libsasl2-2_2.1.28+dfsg-6_amd64.deb ...
Unpacking libsasl2-2:amd64 (2.1.28+dfsg-6) ...
Selecting previously unselected package libldap-2.5-0:amd64.
Preparing to unpack .../04-libldap-2.5-0_2.5.12+dfsg-2_amd64.deb ...
Unpacking libldap-2.5-0:amd64 (2.5.12+dfsg-2) ...
Selecting previously unselected package libnfsidmap1:amd64.
Preparing to unpack .../05-libnfsidmap1_1%3a2.6.1-2_amd64.deb ...
Unpacking libnfsidmap1:amd64 (1:2.6.1-2) ...
Selecting previously unselected package rpcbind.
Preparing to unpack .../06-rpcbind_1.2.6-3_amd64.deb ...
Unpacking rpcbind (1.2.6-3) ...
Selecting previously unselected package keyutils.
Preparing to unpack .../07-keyutils_1.6.3-1_amd64.deb ...
Unpacking keyutils (1.6.3-1) ...
Selecting previously unselected package nfs-common.
Preparing to unpack .../08-nfs-common_1%3a2.6.1-2_amd64.deb ...
Unpacking nfs-common (1:2.6.1-2) ...
Selecting previously unselected package libldap-common.
Preparing to unpack .../09-libldap-common_2.5.12+dfsg-2_all.deb ...
Unpacking libldap-common (2.5.12+dfsg-2) ...
Selecting previously unselected package libsasl2-modules:amd64.
Preparing to unpack .../10-libsasl2-modules_2.1.28+dfsg-6_amd64.deb ...
Unpacking libsasl2-modules:amd64 (2.1.28+dfsg-6) ...
Setting up libsasl2-modules:amd64 (2.1.28+dfsg-6) ...
Setting up rpcbind (1.2.6-3) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/rpcbind.service →
/lib/systemd/system/rpcbind.service.
Created symlink
/etc/systemd/system/sockets.target.wants/rpcbind.socket →
/lib/systemd/system/rpcbind.socket.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
Setting up libldap-common (2.5.12+dfsg-2) ...
Setting up libsasl2-modules-db:amd64 (2.1.28+dfsg-6) ...
Setting up libevent-core-2.1-7:amd64 (2.1.12-stable-5+b1) ...
Setting up libsasl2-2:amd64 (2.1.28+dfsg-6) ...
Setting up keyutils (1.6.3-1) ...
Setting up autofs (5.1.8-1+b1) ...

Creating config file /etc/auto.master with new version

Creating config file /etc/auto.net with new version

Creating config file /etc/auto.misc with new version

Creating config 

Bug#1014425: rkhunter: rkunter is unable to find config file for 'syslog' daemon

[Francois Marier]

Hi Tim,

> I'm getting these emails Daily:
> Warning: The 'syslog' daemon is running, but no configuration file can be
> found.

I'm not sure why you're getting that message, I've never seen it myself.

Are you using rsyslog or syslog-ng?

Francois

-- 
https://fmarier.org/

Bug#1014425: rkhunter: rkunter is unable to find config file for 'syslog' daemon

[tmcconnell168]

I'm using busybox-syslogd, it's supposed to do syslogd and klogd 

On Tue, 2022-07-05 at 13:44 -0700, Francois Marier wrote:
> Hi Tim,
> 
> > I'm getting these emails Daily:
> > Warning: The 'syslog' daemon is running, but no configuration file
> > can be
> > found.
> 
> I'm not sure why you're getting that message, I've never seen it
> myself.
> 
> Are you using rsyslog or syslog-ng?
> 
> Francois
> 

Bug#1012845: pdftoipe: Patch for compatibility with Poppler >22.03

[Jeremy Bicha]

Control: severity -1 important

I am bumping the severity because a patch is included and we have
basically finished the transition in Ubuntu.

Thank you,
Jeremy Bicha

Bug#1014428: xmacro: reproducible-builds: embedded build paths in /usr/bin/xmacro*

[Vagrant Cascadian]

Source: xmacro
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build path is embedded in various binaries in /usr/bin:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/xmacro.html

  /usr/bin/xmacroplay

  /build/1st/xmacro-0.3pre-2911/xmacroplay.cpp:472
  vs.
  /build/2/xmacro-0.3pre-2911/2nd/xmacroplay.cpp:472

The attached patch fixes this by switching to using the debhelper's "dh"
command, which passes compiler flags to avoid embedding the build path
(e.g. -ffile-prefix-map).


With this patch applied, xmacro should build reproducibly on
tests.reproducible-builds.org!


live well,
  vagrant
From f28f53bb5658ada0bc921617dd9ae143a55c97d1 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 5 Jul 2022 20:18:58 +
Subject: [PATCH] debian/rules: Switch to "dh".

---
 debian/rules | 83 
 1 file changed, 5 insertions(+), 78 deletions(-)

diff --git a/debian/rules b/debian/rules
index 70c157f..751682a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,85 +1,12 @@
 #!/usr/bin/make -f
-# Sample debian/rules that uses debhelper.
-# GNU copyright 1997 to 1999 by Joey Hess.
 
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
+%:
+	dh $@
 
-ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
-	CFLAGS += -g
-endif
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-	INSTALL_PROGRAM += -s
-endif
-
-CXXFLAGS=-g -O2
-export CXXFLAGS
-
-configure: configure-stamp
-configure-stamp:
-	dh_testdir
-	# Add here commands to configure the package.
-
-	touch configure-stamp
-
-
-build: build-stamp
-
-build-stamp: configure-stamp
-	dh_testdir
-	dh_auto_build
-	#/usr/bin/docbook-to-man debian/xmacro-0.3pre.sgml > xmacro-0.3pre.1
-
-	touch build-stamp
-
-clean:
-	dh_testdir
-	dh_testroot
-	rm -f build-stamp configure-stamp
-
-	# Add here commands to clean up after the build process.
-	$(MAKE) clean
-
-	dh_clean
-
-install: build
-	dh_testdir
-	dh_testroot
-	dh_prep
-	dh_installdirs
-
-	# Add here commands to install the package into debian/xmacro-0.3pre.
+override_dh_auto_install:
+	dh_auto_install
 	install -Dpv xmacroplay-keys xmacroplay xmacrorec xmacrorec2 $(CURDIR)/debian/xmacro/usr/bin
 
-build-arch: build
-
-build-indep: build
-
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
-# Build architecture-dependent files here.
-binary-arch: build install
-	dh_testdir
-	dh_testroot
-	dh_installdocs
-	dh_installexamples
-	dh_installmenu
-	dh_installcron
-	dh_installman
-	dh_installinfo
-	dh_installchangelogs
-	dh_link
-	dh_strip
-	dh_compress
+override_dh_fixperms:
 	dh_fixperms
 	chmod -x $(CURDIR)/debian/xmacro/usr/share/doc/xmacro/examples/*
-	dh_installdeb
-	dh_shlibdeps
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
-- 
2.36.1



signature.asc
Description: PGP signature

Bug#1014424: exim4-config: recieve warnings about messages being delayed by Smarthost

[tmcconnell168]

okay ran the command you gave, accepted the defaults and took
mail. out of the configuration. Now, how do verify that mail was
sent and my local settings are correct? 
-Tim

On Tue, 2022-07-05 at 21:53 +0200, Marc Haber wrote:
> On Tue, Jul 05, 2022 at 02:46:25PM -0500,
> tmcconnell...@gmail.com wrote:
> > Not sure if it resolves, I use dww and it opens the help files
> > using
> > the DebianTim.midcoip.net part but if I put that
> > (mail.DebianTim.midcoip.net) into a browser that address does not.
> > But
> > I didn't configure it, Debian did when I installed it? 
> 
> Debian asks for the smarthost and suggests a default. That default is
> wrong for you. Please fix that with dpkg-reconfigure -plow exim4-
> config.
> 
> Greetings
> Marc
> 
> 

Bug#1014427: gitlab-ci-multi-runner: undeclared go -dev build-dependencies

[Steve Langasek]

Package: gitlab-ci-multi-runner
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Hi Dmitry,

The gitlab-ci-multi-runner package fails to build from source in Ubuntu
because unlike in Debian, certain -dev packages required to build don't
happen to be pulled in as indirect build-dependencies:

[...]
src/gitlab.com/gitlab-org/gitlab-runner/helpers/container/services/services.go:8
:2: cannot find package "github.com/docker/distribution/reference" in any of:
/<>/_build/src/gitlab.com/gitlab-org/gitlab-runner/vendor/g
ithub.com/docker/distribution/reference (vendor tree)
/usr/lib/go-1.18/src/github.com/docker/distribution/reference (from $GOR
OOT)
/<>/_build/src/github.com/docker/distribution/reference (fr
om $GOPATH)
src/gitlab.com/gitlab-org/gitlab-runner/vendor/k8s.io/api/core/v1/generated.pb.g
o:230:2: cannot find package "github.com/gogo/protobuf/proto" in any of:

/<>/_build/src/gitlab.com/gitlab-org/gitlab-runner/vendor/github.com/gogo/protobuf/proto
 (vendor tree)
/usr/lib/go-1.18/src/github.com/gogo/protobuf/proto (from $GOROOT)
/<>/_build/src/github.com/gogo/protobuf/proto (from 
$GOPATH)
src/gitlab.com/gitlab-org/gitlab-runner/vendor/k8s.io/api/core/v1/generated.pb.go:242:2:
 cannot find package "github.com/gogo/protobuf/sortkeys" in any of:

/<>/_build/src/gitlab.com/gitlab-org/gitlab-runner/vendor/github.com/gogo/protobuf/sortkeys
 (vendor tree)
/usr/lib/go-1.18/src/github.com/gogo/protobuf/sortkeys (from $GOROOT)
/<>/_build/src/github.com/gogo/protobuf/sortkeys (from 
$GOPATH)
src/gitlab.com/gitlab-org/gitlab-runner/session/session.go:9:2: cannot find 
package "github.com/gorilla/websocket" in any of:

/<>/_build/src/gitlab.com/gitlab-org/gitlab-runner/vendor/github.com/gorilla/websocket
 (vendor tree)
/usr/lib/go-1.18/src/github.com/gorilla/websocket (from $GOROOT)
/<>/_build/src/github.com/gorilla/websocket (from $GOPATH)
[...]

   
(https://launchpad.net/ubuntu/+source/gitlab-ci-multi-runner/13.3.1+dfsg-4/+build/23574022)

It is correct for gitlab-ci-multi-runner to declare build-dependencies on
each of these go modules since its source code uses them directly.

Please see the attached patch.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gitlab-ci-multi-runner-13.3.1+dfsg/debian/control 
gitlab-ci-multi-runner-13.3.1+dfsg/debian/control
--- gitlab-ci-multi-runner-13.3.1+dfsg/debian/control   2021-01-17 
03:52:33.0 -0800
+++ gitlab-ci-multi-runner-13.3.1+dfsg/debian/control   2022-07-05 
13:10:33.0 -0700
@@ -13,7 +13,7 @@
 ,golang-github-burntsushi-toml-dev
 ,golang-github-docker-docker-credential-helpers-dev (>= 0.5.0~)
 ,golang-github-docker-docker-dev (>= 20.10.0~beta1)
-#   ,golang-github-docker-distribution-dev
+,golang-github-docker-distribution-dev
 ,golang-github-docker-go-connections-dev (>= 0.4.0~)
 ,golang-github-docker-go-units-dev
 ,golang-github-docker-spdystream-dev
@@ -24,12 +24,14 @@
 ,golang-github-ghodss-yaml-dev
 ,golang-github-gofrs-flock-dev
 ,golang-github-go-ini-ini-dev
+,golang-github-gogo-protobuf-dev
 ,golang-github-googleapis-gnostic-dev
 ,golang-github-google-gofuzz-dev
 ,golang-github-gophercloud-gophercloud-dev
 ,golang-github-gorhill-cronexpr-dev
 ,golang-github-gorilla-context-dev
 ,golang-github-gorilla-mux-dev
+,golang-github-gorilla-websocket-dev
 ,golang-github-hashicorp-go-version-dev
 ,golang-github-howeyc-gopass-dev
 ,golang-github-imdario-mergo-dev

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Michael]

on the host's /var/log/apt/term.log:

Log started: 2022-06-12  10:57:30
...
Preparing to unpack .../08-linux-image-5.10.0-15-amd64_5.10.120-1_amd64.deb 
...

Unpacking linux-image-5.10.0-15-amd64 (5.10.120-1) ...
Preparing to unpack .../09-linux-image-amd64_5.10.120-1_amd64.deb ...
Unpacking linux-image-amd64 (5.10.120-1) over (5.10.113-1) ...
...
Setting up linux-image-5.10.0-15-amd64 (5.10.120-1) ...
...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-14-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-14-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-15-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-15-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-15-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-15-amd64
Found initrd image: /boot/initrd.img-5.10.0-15-amd64
Found linux image: /boot/vmlinuz-5.10.0-14-amd64
Found initrd image: /boot/initrd.img-5.10.0-14-amd64
Adding boot menu entry for EFI firmware configuration
done
...
Setting up linux-image-amd64 (5.10.120-1) ...
...
Log ended: 2022-06-12  10:58:50


so, the kernel was installed on 2022-06-12.


and for your request:

# cat <(gunzip -c /var/log/kern.log.{4,3,2}.gz) /var/log/kern.log{.1,} | 
grep -B5 -E "hrtimer|clocksource|traps:|Code:|general|segfault"


Apr 18 22:24:41 vmguest kernel: [1669500.364257] clocksource: timekeeping 
watchdog on CPU1: kvm-clock wd-wd read-back delay of 64914ns
Apr 18 22:24:41 vmguest kernel: [1669500.364328] clocksource: wd-tsc-wd 
read-back delay of 314448ns, clock-skew test skipped!

--
Apr 19 13:42:46 vmguest kernel: [0.00] DMI: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006

Apr 19 13:42:46 vmguest kernel: [0.00] Hypervisor detected: KVM
Apr 19 13:42:46 vmguest kernel: [0.00] kvm-clock: Using msrs 
4b564d01 and 4b564d00
Apr 19 13:42:46 vmguest kernel: [0.00] kvm-clock: cpu 0, msr 
236b8001, primary cpu clock
Apr 19 13:42:46 vmguest kernel: [0.02] kvm-clock: using sched 
offset of 5303526299 cycles
Apr 19 13:42:46 vmguest kernel: [0.07] clocksource: kvm-clock: 
mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 
881590591483 ns

--
Apr 19 13:42:46 vmguest kernel: [0.180275] PM: hibernation: Registered 
nosave memory: [mem 0x0009f000-0x0009]
Apr 19 13:42:46 vmguest kernel: [0.180276] PM: hibernation: Registered 
nosave memory: [mem 0x000a-0x000e]
Apr 19 13:42:46 vmguest kernel: [0.180277] PM: hibernation: Registered 
nosave memory: [mem 0x000f-0x000f]
Apr 19 13:42:46 vmguest kernel: [0.180280] [mem 0x4000-0xfebf] 
available for PCI devices
Apr 19 13:42:46 vmguest kernel: [0.180282] Booting paravirtualized 
kernel on KVM
Apr 19 13:42:46 vmguest kernel: [0.180288] clocksource: 
refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 
7645519600211568 ns

--
Apr 19 13:42:46 vmguest kernel: [0.216877] ACPI: Core revision 20200925
Apr 19 13:42:46 vmguest kernel: [0.217175] APIC: Switch to symmetric 
I/O mode setup

Apr 19 13:42:46 vmguest kernel: [0.217795] x2apic enabled
Apr 19 13:42:46 vmguest kernel: [0.218367] Switched APIC routing to 
physical x2apic.
Apr 19 13:42:46 vmguest kernel: [0.221130] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
Apr 19 13:42:46 vmguest kernel: [0.221204] clocksource: tsc-early: 
mask: 0x max_cycles: 0x1598c7dcb76, max_idle_ns: 
440795222846 ns

--
Apr 19 13:42:46 vmguest kernel: [0.349407] smpboot: Max logical 
packages: 1
Apr 19 13:42:46 vmguest kernel: [0.349411] smpboot: Total of 4 
processors activated (11986.22 BogoMIPS)
Apr 19 13:42:46 vmguest kernel: [0.355058] node 0 deferred pages 
initialised in 4ms

Apr 19 13:42:46 vmguest kernel: [0.355163] devtmpfs: initialized
Apr 19 13:42:46 vmguest kernel: [0.355163] x86/mm: Memory block size: 
128MB
Apr 19 13:42:46 vmguest kernel: [0.357525] clocksource: jiffies: mask: 
0x max_cycles: 0x, max_idle_ns: 764504178510 ns

--
Apr 19 13:42:46 vmguest kernel: [0.709892] NetLabel:  unlabeled traffic 
allowed by default
Apr 19 13:42:46 vmguest kernel: [0.709892] PCI: Using ACPI for IRQ 
routing
Apr 19 13:42:46 vmguest kernel: [0.709892] PCI: pci_cache_line_size set 
to 64 bytes
Apr 19 13:42:46 vmguest kernel: [0.710019] e820: reserve RAM buffer 
[mem 0x0009fc00-0x0009]
Apr 19 13:42:46 vmguest kernel: [0.710030] e820: reserve RAM buffer 
[mem 0x3fff-0x3fff]
Apr 19 13:42:46 vmguest kernel: [0.715223] clocksource: Switched to 
clocksource kvm-clock

--
Apr 19 13:42:46 vmguest kernel: [0.736766] AppArmor: AppArmor 
Filesystem Enabled

Apr 19 13:42:46 vmguest kernel: [0.736806] pnp: PnP ACPI init
Apr 19 13:42:46 vmguest kernel: [0.736937] pnp 00:00: Plug and Play 
ACPI device, IDs PNP0303 

Bug#1014424: exim4-config: recieve warnings about messages being delayed by Smarthost

[Marc Haber]

On Tue, Jul 05, 2022 at 02:46:25PM -0500, tmcconnell...@gmail.com wrote:
> Not sure if it resolves, I use dww and it opens the help files using
> the DebianTim.midcoip.net part but if I put that
> (mail.DebianTim.midcoip.net) into a browser that address does not. But
> I didn't configure it, Debian did when I installed it? 

Debian asks for the smarthost and suggests a default. That default is
wrong for you. Please fix that with dpkg-reconfigure -plow exim4-config.

Greetings
Marc


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

Bug#1014426: cldump: reproducible-builds: embedded build paths in /usr/bin/cldump

[Vagrant Cascadian]

Source: cldump
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build path is embedded in /usr/bin/cldump:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/cldump.html

  /build/1st/cldump-0.11~dfsg/src/cldump.c:180
  vs.
  /build/2/cldump-0.11~dfsg/2nd/src/cldump.c:180

The attached patch fixes this by explicitly passing CFLAGS to
dh_auto_build in debian/rules, which includes flags to avoid embedding
the build path.


With this patch applied, cldump should build reproducibly on
tests.reproducible-builds.org!


live well,
  vagrant
From e65c0a4b1a6bb623feddd15e7ec0fda53dbd7422 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 5 Jul 2022 19:46:11 +
Subject: [PATCH] debian/rules: Pass CFLAGS via dh_auto_build override.

src/Makefile sets CFLAGS explicitly, ignoring CFLAGS from the
environment. This means various default flags are otherwise ignored,
e.g. -ffile-prefix-map which is used to avoid embedding build paths
for reproducible builds.
---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index 5b70f17..f12e8a3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,3 +6,6 @@
 
 %:
 	dh $@ --sourcedirectory=src --buildsystem=makefile
+
+override_dh_auto_build:
+	dh_auto_build --sourcedirectory=src --buildsystem=makefile -- CFLAGS="$(CFLAGS)"
-- 
2.36.1



signature.asc
Description: PGP signature

Bug#1014424: exim4-config: recieve warnings about messages being delayed by Smarthost

[tmcconnell168]

On Tue, 2022-07-05 at 21:37 +0200, Marc Haber wrote:
> On Tue, Jul 05, 2022 at 09:25:55PM +0200, Marc Haber wrote:
> > On Tue, Jul 05, 2022 at 02:16:26PM -0500, Tim McConnell wrote:
> > >     Delay reason: lookup failed for all hosts in smarthost
> > > router:
> > >     host_find_failed=ignore host_all_ignored=defer
> > > 
> > > dc_other_hostnames='DebianTim.midcoip.net; localhost'
> > 
> > That host name doesnt resolve here. Does it resolve at your place?
> 
> My mistake. I wanted to paste this line:
> 
> dc_smarthost='mail.DebianTim.midcoip.net'
> 
> and that's the host name that doesn't seem to resolve.
> 
> Greetings
> Marc
> 

Not sure if it resolves, I use dww and it opens the help files using
the DebianTim.midcoip.net part but if I put that
(mail.DebianTim.midcoip.net) into a browser that address does not. But
I didn't configure it, Debian did when I installed it? 

Bug#1014424: exim4-config: recieve warnings about messages being delayed by Smarthost

[Marc Haber]

On Tue, Jul 05, 2022 at 09:25:55PM +0200, Marc Haber wrote:
> On Tue, Jul 05, 2022 at 02:16:26PM -0500, Tim McConnell wrote:
> > Delay reason: lookup failed for all hosts in smarthost router:
> > host_find_failed=ignore host_all_ignored=defer
> > 
> > dc_other_hostnames='DebianTim.midcoip.net; localhost'
> 
> That host name doesnt resolve here. Does it resolve at your place?

My mistake. I wanted to paste this line:

dc_smarthost='mail.DebianTim.midcoip.net'

and that's the host name that doesn't seem to resolve.

Greetings
Marc

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

Bug#1014394: Stable Proposed Updates Kernel

[Richard Laysell]

Hello,

I have installed the Stable-Proposed-Updates kernel on the virtual host
(linux-image-5.10.0-16-amd64 - 5.10.127-1) and I am still seeing
Firefox crashing frequently in a virtual guest running on this host.

I do not see any messages logged in kern.log when the whole of Firefox
crashes, but I do see the following messages when individual tabs in
Firefox crash (these tab crashes also happened with 5.10.0-15-amd64 -
5.10.120.1 but not with 5.10.0-14-amd64 - 5.10.113-1).

These are from the virtual guest however, not the host.  I do not see
any errors logged to kern.log on the host (even though that is the
system running the problematic kernel).

Jul  5 20:10:23 vwbbase kernel: [  342.977899] DOM Worker[4222]:
segfault at 7fd700942000 ip 7fd72ba9a307 sp 7fd71ce03cd0 error
4 in libxul.so[7fd7278dd000+5559000]
Jul  5 20:10:23 vwbbase kernel: [  342.977907] Code: c7 0f 84 48 ff ff
ff 4c 8d 77 38 4c 8d 6f 60 48 8d 6c 24 04 0f 1f 80 00 00 00 00 8b 53 38
49 63 c7 48 03 43 28 44 89 7c 24 04 <44> 8b 38 48 89 ee 4c 89 ef 89 10
4c 89 f2 e8 e6 9a ff ff 45 85 ff
Jul  5 20:13:52 vwbbase kernel: [  552.210131] traps: Web Content[4872]
general protection fault ip:7f0fa8c39426 sp:7ffe80eff5c0 error:0 in
libxul.so[7f0fa490e000+5559000]
Jul  5 20:13:54 vwbbase kernel: [  554.146579] traps: Web Content[5025]
general protection fault ip:7f7cf735b068 sp:7fffaffe93c0 error:0 in
libxul.so[7f7cf350e000+5559000]

Happy to do more testing and send more logs if it helps.

Regards,

Richard

Bug#1014425: rkhunter: rkunter is unable to find config file for 'syslog' daemon

[Tim McConnell]

Package: rkhunter
Version: 1.4.6-10
Severity: normal
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

I'm getting these emails Daily:
Warning: The 'syslog' daemon is running, but no configuration file can be
found.

This has been going on for about the last 3 upgrade releases of Debian Testing.
Now I'm unsure if any of the scans are working like they are supposed to. This
is done by a daily Cron job. so these emails and the ones stating: "Please
inspect this machine, because it may be infected." shouldn't be happening?
How do I fix both?



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

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

Versions of packages rkhunter depends on:
ii  binutils   2.38-4
ii  debconf [debconf-2.0]  1.5.79
ii  file   1:5.41-4
ii  lsof   4.95.0-1
ii  net-tools  1.60+git20181103.0eebece-1
ii  perl   5.34.0-4
ii  ucf3.0043

Versions of packages rkhunter recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20220412cvs-1
ii  curl   7.83.1-2
ii  e2fsprogs  1.46.5-2
ii  exim4-daemon-light [mail-transport-agent]  4.95-6
ii  iproute2   5.18.0-1
ii  mailutils [mailx]  1:3.15-2+b1
ii  unhide 20210124-2
ii  unhide.rb  22-6
ii  wget   1.21.3-1+b2

Versions of packages rkhunter suggests:
ii  liburi-perl 5.10-1
ii  libwww-perl 6.67-1
ii  powermgmt-base  1.36

-- Configuration Files:
/etc/logcheck/ignore.d.server/rkhunter [Errno 13] Permission denied: 
'/etc/logcheck/ignore.d.server/rkhunter'
/etc/rkhunter.conf changed:
UPDATE_MIRRORS=1
MIRRORS_MODE=0
MAIL-ON-WARNING='root'
MAIL_CMD=mail -s "[rkhunter] Warnings found for ${HOST_NAME}"
TMPDIR=/var/lib/rkhunter/tmp
DBDIR=/var/lib/rkhunter/db
SCRIPTDIR=/usr/share/rkhunter/scripts
UPDATE_LANG="en"
LOGFILE=/var/log/rkhunter.log
COPY_LOG_ON_ERROR=1
USE_SYSLOG=authpriv.warning
AUTO_X_DETECT=1
ALLOW_SSH_PROT_V1=2
ENABLE_TESTS=ALL
DISABLE_TESTS=suspscan hidden_ports hidden_procs deleted_files packet_cap_apps 
apps
PKGMGR=DPKG
SCRIPTWHITELIST=/usr/bin/egrep
SCRIPTWHITELIST=/usr/bin/fgrep
SCRIPTWHITELIST=/usr/bin/which
SCRIPTWHITELIST=/usr/bin/ldd
SCRIPTWHITELIST=/usr/bin/which.debianutils
SCRIPTWHITELIST=/usr/sbin/adduser
ALLOWHIDDENDIR=/etc/.java
ALLOWPROCLISTEN=/usr/sbin/tcpdump
ALLOWPROCLISTEN=/usr/sbin/snort-plain
ALLOWDEVFILE=/dev/shm/pulse-shm-*
ALLOWDEVFILE=/dev/shm/sem.ADBE_*
ALLOWDEVFILE=/dev/shm/u1000-Shm_*
ALLOWDEVFILE=/dev/shm/u1000-ValveIPCSharedObj-Steam*
ALLOWDEVFILE=/dev/shm/jack_db-1000/*
ALLOWIPCPROC=/usr/bin/firefox
ALLOWIPCPROC=/usr/lib/firefox-esr/firefox-esr
WEB_CMD=wget
INSTALLDIR=/usr
ALLOWPROCDELFILE=/usr/sbin/cron
ALLOWPROCDELFILE=/usr/bin/dash
ALLOWPROCDELFILE=/usr/bin/run-parts
SCRIPTWHITELIST=/usr/bin/egrep
SCRIPTWHITELIST=/usr/bin/fgrep
SCRIPTWHITELIST=/usr/bin/which
PORT_PATH_WHITELIST=/usr/sbin/portsentry
ALLOW_SSH_ROOT_USER=prohibit-password


-- debconf information:
  rkhunter/cron_daily_run: true
  rkhunter/cron_db_update: true
  rkhunter/apt_autogen: true

-- debsums errors found:
debsums: changed file /var/lib/rkhunter/db/mirrors.dat (from rkhunter package)

Bug#1014424: exim4-config: recieve warnings about messages being delayed by Smarthost

[Marc Haber]

On Tue, Jul 05, 2022 at 02:16:26PM -0500, Tim McConnell wrote:
> Delay reason: lookup failed for all hosts in smarthost router:
> host_find_failed=ignore host_all_ignored=defer
> 
> dc_other_hostnames='DebianTim.midcoip.net; localhost'

That host name doesnt resolve here. Does it resolve at your place?

Greetings
Marc

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

Bug#1014259: sscg: ftbfs on riscv64: (create_csr_test TIMEOUT 30.10s killed by signal 15 SIGTERM)

[Boyuan Yang]

On Mon, 4 Jul 2022 08:32:10 +0800 xiao sheng wen(肖盛文) 
wrote:
> 在 2022/7/3 16:00, Boyuan Yang 写道:
> 
> > Hi all,
> >
> > Martin: is it possible to patch the package to get around the timeout for
slow
> > archs such as riscv64? My current thoughts include (1) force non-parallel
test
> > (override_dh_auto_test: dh_auto_test --no-parallel), and/or (2) patch
> 
> Is there a way to only do " --no-parallel" test under riscv arch?

Yes, but we need another package upload anyway.

Thanks,
Boyuan


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

Bug#1012853: fixed in 2.38.50.20220615-3

[Paul Gevers]

Control: fixed -1 2.38.50.20220615-4

On Thu, 16 Jun 2022 11:54:31 +0200 Matthias Klose  wrote:

Version: 2.38.50.20220615-3

fixed


But version -3 isn't mentioned in the changelog in unstable, so the bts 
doesn't know that unstable has a fixed version. Adding the current 
unstable version too, assuming that was what this message intended.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014424: exim4-config: recieve warnings about messages being delayed by Smarthost

[Tim McConnell]

Package: exim4-config
Version: 4.95-6
Severity: important
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,
I'm unsure what lead to this, I've been having issues with Mail delivery on
localhost for a while now. I'm starting to get mails from Mail Delivery system
with the subject line of "Warning: Message 'Blah'delayed for 24 hours"
The body reads:
This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its
recipients after more than 24 hours on the queue on localhost.

The message identifier is: 1o8Jxl-007SqX-3Q
The subject of the message is: popularity-contest submission
The date of the message is:Mon, 04 Jul 2022 06:09:57 -0500

The address to which the message has not yet been delivered is:

  sur...@popcon.debian.org
Delay reason: lookup failed for all hosts in smarthost router:
host_find_failed=ignore host_all_ignored=defer

No action is required on your part. Delivery attempts will continue for
some time, and this warning may be repeated at intervals if the message
remains undelivered. Eventually the mail delivery software will give up,
and when that happens, the message will be returned to you.

The mail Delivery report attachment reads:
Reporting-MTA: dns; localhost

Action: delayed
Final-Recipient: rfc822;sur...@popcon.debian.org
Status: 4.0.0

email headers attachment reads:
From:   root 
To: sur...@popcon.debian.org
Subject:popularity-contest submission
Date:   Mon, 04 Jul 2022 06:09:57 -0500

I don't have anything other than what Debian installs by Default for mail
programs, DNS. DHCP or anything else like that.

I have been having another issue where reading local mail in Evolution (version
3.44.2-1 )->On this Computer->Inbox causes my CPU to go to 100%.
I can't help but to wonder if the two are related?
Let me know what logs you need and how to get them and I'll be happy to send
them.
Thanks!


-- Package-specific info:
Exim version 4.95 #2 built 20-May-2022 17:37:43
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2020
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS TLS_resume move_frozen_messages DANE 
DKIM DNSSEC Event I18N OCSP PIPE_CONNECT PRDR Experimental_Queue_Ramp SOCKS SRS 
TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 external plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='smarthost'
dc_other_hostnames='DebianTim.midcoip.net; localhost'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.DebianTim.midcoip.net'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='false'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:DebianTim.midcoip.net
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP 

Bug#1014423: gnome-books: unmaintained, depends on gnome-online-miners

[Jeremy Bicha]

Source: gnome-books
Version: 40.0-3
Severity: serious

gnome-books has been archived. That means that bug reports, bug fixes,
translations, etc. are no longer being accepted for it.

https://gitlab.gnome.org/GNOME/gnome-books

We will likely need to remove gnome-books from Debian soon because its
dependency, gnome-online-miners, is interfering with completing the
libsoup3 transition for evolution-data-server and friends. That
transition is required to package GNOME 43.

The recommended replacement app is foliate which is already available
in Debian Unstable.

Thank you,
Jeremy Bicha

Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0

[Paul Cercueil]

Le mar., juil. 5 2022 at 20:46:44 +0200, Michel Dänzer 
 a écrit :

On 2022-07-05 18:28, Paul Cercueil wrote:
 Le mar., juil. 5 2022 at 15:51:08 +0200, Michel Dänzer 
 a écrit :

 On 2022-07-05 14:48, Paul Cercueil wrote:


  Is there a way I can provide more information?


 Come to think of it, capturing the journal output after trying to 
start an X11 client might be interesting:


  journalctl --user -b0


 This was giving me zero results so I ran 'journalctl -b0' and some 
things happened when trying to run 'xterm':


 [...]

 juil. 05 17:24:03 frank gsd-xsettings[3959]: Impossible d’ouvrir 
l’affichage :
 juil. 05 17:24:03 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
code=exited, status=1/FAILURE
 juil. 05 17:24:03 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Failed with result 
'exit-code'.
 juil. 05 17:24:03 frank systemd[2111]: Failed to start GNOME 
XSettings service.
 juil. 05 17:24:03 frank gnome-shell[2215]: Window manager warning: 
L’initialisation de GDK a échoué
 juil. 05 17:24:03 frank gnome-shell[2215]: Failed to initialize X11 
display: Failed to initialize GDK


Looks like the problem is either that gsd-xsettings fails to start, 
or that gnome-shell fails to initialize GDK.


On the former, does

 journalctl --user-unit=org.gnome.SettingsDaemon.XSettings.service -b0


or

 systemctl --user status org.gnome.SettingsDaemon.XSettings.service

provide more information about the failure?


journalctl gives me this:

juil. 05 19:58:04 frank systemd[2014]: Starting GNOME XSettings 
service...

juil. 05 19:58:05 frank systemd[2014]: Started GNOME XSettings service.
juil. 05 19:58:40 frank systemd[2014]: Dependency failed for GNOME 
XSettings service.
juil. 05 19:58:40 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Job 
org.gnome.SettingsDaemon.XSettings.service/start failed with result 
'dependency'.
juil. 05 19:58:55 frank systemd[2014]: Starting GNOME XSettings 
service...
juil. 05 19:58:55 frank gsd-xsettings[4159]: Impossible d’ouvrir 
l’affichage :
juil. 05 19:58:55 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
code=exited, status=1/FAILURE
juil. 05 19:58:55 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Failed with result 
'exit-code'.
juil. 05 19:58:55 frank systemd[2014]: Failed to start GNOME XSettings 
service.
juil. 05 19:58:55 frank systemd[2014]: 
org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, 
restart counter is at 1.


The message in french from gsd-xsettings is "Cannot open display:"


 Also, does setting DISPLAY=:1 (or whatever is the default number + 
1) work better?


 It does not seem to change anything, running 'DISPLAY=:1 xterm' 
just hangs (doesn't open a window), the only difference I can see is 
that no Xwayland process is started.


What value does $DISPLAY contain after logging in?

What if you try DISPLAY=:1 once Xwayland is running? If that works, 
maybe try


 DISPLAY=:1 /usr/libexec/gsd-xsettings -v

to see if that gives more information about the failure.


$DISPLAY is :0 after logging in. Using DISPLAY=:1 does not seem to 
change anything.


I tried:

DISPLAY=:0 /usr/libexec/gsd-xsettings -v
DISPLAY=:1 /usr/libexec/gsd-xsettings -v

Both print the exact same error message as above, and nothing else.

I tried as well:

/usr/libexec/gsd-xsettings -v --display=:0
/usr/libexec/gsd-xsettings -v --display=:1

I get the same error message, but this time it did print back the 
display on the error message: "Cannot open display: :1"



On 2022-07-05 18:26, Paul Cercueil wrote:
 Le mar., juil. 5 2022 at 15:31:25 +0200, Michel Dänzer 
 a écrit :

 On 2022-07-05 14:48, Paul Cercueil wrote:



  I end up having to work under Windows, ugh.


 Surely you can use a GNOME on Xorg session in the worst case.


 Is that still a thing? I can't select Gnome on X11 anymore since 
the last few releases of Gnome. GDM simply doesn't give me the 
option.


That's unexpected, I can still choose "GNOME on Xorg" on my machines.

Do you have xserver-xorg installed?


Ha, good point. I re-installed the "xserver-xorg" package and now I do 
have the "GNOME on Xorg" option back.


Cheers,
-Paul

Bug#1014422: src:zynaddsubfx: fails to migrate to testing for too long: ftbfs on arm64, ppc64el and s390x

[Paul Gevers]

Source: zynaddsubfx
Version: 3.0.5-2
Severity: serious
Control: close -1 3.0.6-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:zynaddsubfx has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package failed to build 
from source on arm64, ppc64el and s390x while it built there 
successfully in the past.


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


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


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014421: false \' alert in '\\'

[Marc Haber]

Package: lintian
Version: 2.115.2
Severity: normal

Hi,

this line:

(space), '@' and '\\' (backslash) (e.g. '\\ ' or '\\@'). To literally match a 
'\fB\\\fR'

in a man page triggers

I: aide: acute-accent-in-manual-page [usr/share/man/man5/aide.conf.5.gz:16]

I think this is caused by the '\\', and I think that's a false alert.

Greetings
Marc


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

Kernel: Linux 5.18.8-zgws1 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils2.38.50.20220627-1
ii  bzip2   1.0.8-5
ii  diffstat1.64-1
ii  dpkg1.21.8
ii  dpkg-dev1.21.8
ii  file1:5.41-4
ii  gettext 0.21-6
ii  gpg 2.2.35-2
ii  intltool-debian 0.35.0+20060710.5
ii  iso-codes   4.10.0-1
ii  libapt-pkg-perl 0.1.40+b1
ii  libarchive-zip-perl 1.68-1
ii  libberkeleydb-perl  0.64-1+b2
ii  libcapture-tiny-perl0.48-1
ii  libclass-xsaccessor-perl1.19-3+b8
ii  libclone-perl   0.45-1+b2
ii  libconfig-tiny-perl 2.28-1
ii  libconst-fast-perl  0.014-2
ii  libcpanel-json-xs-perl  4.30-1
ii  libdata-dpath-perl  0.58-1
ii  libdata-validate-domain-perl0.10-1.1
ii  libdata-validate-uri-perl   0.07-2
ii  libdevel-size-perl  0.83-1+b3
pn  libdigest-sha-perl  
ii  libdpkg-perl1.21.8
ii  libemail-address-xs-perl1.04-1+b4
ii  libfile-basedir-perl0.09-1
ii  libfile-find-rule-perl  0.34-1.1
ii  libfont-ttf-perl1.06-2
ii  libhtml-html5-entities-perl 0.004-2
ii  libhtml-tokeparser-simple-perl  3.16-4
ii  libio-interactive-perl  1.023-1
ii  libipc-run3-perl0.048-2
ii  libjson-maybexs-perl1.004003-1
ii  liblist-compare-perl0.55-1
ii  liblist-someutils-perl  0.58-1
ii  liblist-utilsby-perl0.12-1
ii  libmldbm-perl   2.05-3
ii  libmoo-perl 2.005004-3
ii  libmoox-aliases-perl0.001006-2
ii  libnamespace-clean-perl 0.27-2
ii  libpath-tiny-perl   0.122-1
ii  libperlio-gzip-perl 0.20-1
ii  libperlio-utf8-strict-perl  0.009-1+b1
ii  libproc-processtable-perl   0.634-1+b1
ii  libregexp-wildcards-perl1.05-2
ii  libsereal-decoder-perl  4.023+ds-1
ii  libsereal-encoder-perl  4.023+ds-1
ii  libsort-versions-perl   1.62-2
ii  libsyntax-keyword-try-perl  0.27-1
ii  libterm-readkey-perl2.38-1+b3
ii  libtext-levenshteinxs-perl  0.03-5
ii  libtext-markdown-discount-perl  0.13-1+b1
ii  libtext-xslate-perl 3.5.9-1+b1
ii  libtime-duration-perl   1.21-1
ii  libtime-moment-perl 0.44-1+b4
ii  libtimedate-perl2.3300-2
ii  libunicode-utf8-perl0.62-1+b3
ii  liburi-perl 5.10-1
ii  libwww-mechanize-perl   2.09-1
ii  libwww-perl 6.67-1
ii  libxml-libxml-perl  2.0207+dfsg+really+2.0134-1
ii  libyaml-libyaml-perl0.83+ds-1+b1
ii  lzip [lzip-decompressor]1.23-3
ii  lzop1.04-2
ii  man-db  2.10.2-1
ii  patchutils  0.4.2-1
ii  perl [libencode-perl]   5.34.0-4
ii  t1utils 1.41-4
ii  unzip   6.0-26
ii  xz-utils5.2.5-2.1

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libtext-template-perl  1.61-1

-- no debconf information

Bug#1004831: transition: ffmpeg

[Moritz Mühlenhoff]

Am Tue, Jul 05, 2022 at 10:13:20AM +0200 schrieb Sebastian Ramacher:
> ffmpeg has a bad history of security issues including RCEs. It requires
> too many DSAs for both stable and oldstable. So I am only
> going to maintain one ffmpeg version for a specific Debian release.
> Anything else needs coordination with the security team.

Yeah, no way we're going to have two ffmpeg branches in a stable
release...

Cheers,
Moritz

Bug#1014420: gimp: Missing gir dependencies

[Jeremy Bicha]

Source: gimp
Version: 2.99.10-1
Severity: serious
X-Debbugs-CC: jo...@debian.org

gimp won't start if gir1.2-gimp-3.0 and gir1.2-gegl-0.4 aren't
installed. They are needed by the Python plugins.

Do you think it makes sense to move these plugins to gimp-python like
we used to do?

https://buildd.debian.org/status/fetch.php?pkg=gimp=amd64=2.10.8-2%2Bb1=1567518763=0

Thank you,
Jeremy Bicha

Bug#976190: systemd: LXC memory limits messed up after some time

[Michael Biebl]

On Tue, 1 Dec 2020 14:54:38 +0100 Michael Biebl  wrote:

Am 01.12.20 um 14:29 schrieb Paul Slootman:
> Hi,
> 
> On Tue 01 Dec 2020, Michael Biebl wrote:

>>>
>>> root@dns:~# free
>>> totalusedfree  shared  buff/cache   
available
>>> Mem:1048576   41660 1006784   48124 132 
1006784
>>> Swap: 0   0   0
>>>
>>>
>>> After some time, I have noticed that they are no longer correct; in fact
>>> they are wildly wrong:
>>>
>>> root@dns:~# free
>>> totalusedfree  shared  buff/cache   
available
>>> Mem:9007199254740991  598372 9007199254108535   85652   
34084 9007199254108535
>>> Swap: 01692   -1692
>>>
>>
>> I suppose, this is from within the container?
> 
> Yes, correct
> 
>> How do you apply/setup the limits?
> 
> This is in the libvirt container definition:
> 
> 

>dns
>32bd6117-0082-49eb-b622-87e1de716c88
>1048576
>1048576
>
>  1048576
>  1048576
>  1048576
>
>1

Let's loop in the the libvirt maintainers.
If I understand Paul correctly (and read the journal log correctly), the 
memory limits applied by libvirt are lost once a `systemctl 
daemon-reload` is happening. I'm not really familiar how libvirt 
interacts with lxc/systemd, so your input would be welcome here.


Please let us know, if this is still reproducible with a recent version 
of systemd. If so, please file this issue upstream at

https://github.com/systemd/systemd/issues




OpenPGP_signature
Description: OpenPGP digital signature

Bug#859092: systemd-resolved : does not return fully qualified host name for local host name

[Michael Biebl]

Control: tags -1 + moreinfo upstream

On Thu, 30 Mar 2017 10:38:45 +0200 Laurent Bonnaud 
 wrote:

Package: systemd
Version: 233-5


Dear maintainer,

here are 2 DNS queries that illustrate the problem:

 - when I query a "real" DNS server (bind) I get the expected answer 
"irancy.iut2.upmf-grenoble.fr"

 - when I query systemd-resolved I get the short answer "irancy"

root@irancy:~# host 192.168.141.13 193.55.51.34
Using domain server:
Name: 193.55.51.34
Address: 193.55.51.34#53
Aliases:

13.141.168.192.in-addr.arpa domain name pointer irancy.iut2.upmf-grenoble.fr.

root@irancy:~# host 192.168.141.13 127.0.0.53
Using domain server:
Name: 127.0.0.53
Address: 127.0.0.53#53
Aliases:

13.141.168.192.in-addr.arpa domain name pointer irancy.


This a problem for apache who complains about its ServerName.




In case you can still reproduce the issue with an up-to-date version of 
systemd (i.e. v250 or v251), please report this upstream at

https://github.com/systemd/systemd/issues


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014419: [Pkg-nagios-devel] Bug#1014419: icinga2: recommends non-existing package libreadline7

[Sebastiaan Couwenberg]

Control: tags -1 pendiong

On 7/5/22 19:57, Ansgar wrote:

icinga2 Recommends: libreadline7 which is no longer part of Debian
(only in oldstable and older).


Thanks for reporting this issue, it's fixed in git by updating it to 
libreadline8.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1009712: sv: fails to control the service on Hurd

[Samuel Thibault]

João Pedro Malhado, le mar. 05 juil. 2022 19:37:16 +0200, a ecrit:
> However errnno is already 1073741902 before the function call, so does not
> really change after the function call.

Perhaps change the source code to set it to 0, just to be sure.

> open64 (__oflag=10, __path=0x803caa0 "supervise/ok")
> at /usr/include/i386-gnu/bits/fcntl2.h:53
> 53  return __open_alias (__path, __oflag, __va_arg_pack ());
> __GI___libc_open (file=0x803caa0 "supervise/ok", oflag=10)
> at ../sysdeps/mach/hurd/open.c:35
> 35../sysdeps/mach/hurd/open.c: No such file or directory.
> 45in ../sysdeps/mach/hurd/open.c
> 46in ../sysdeps/mach/hurd/open.c
> 47in ../sysdeps/mach/hurd/open.c
> 49in ../sysdeps/mach/hurd/open.c

What you can do is step into functions, and use 'finish' to get their
returned value, to determine at which point -1 is returned.

Samuel

Bug#1014419: icinga2: recommends non-existing package libreadline7

[Ansgar]

Package: icinga2
Version: 2.13.4-1
Severity: normal

icinga2 Recommends: libreadline7 which is no longer part of Debian
(only in oldstable and older).

Ansgar

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Diederik de Haas]

Control: reassign -1 src:linux 5.10.120-1
Control: tag -1 upstream moreinfo

On Tuesday, 5 July 2022 12:09:00 CEST Michael wrote:
> package: linux-image-5.10.0-15-arm64
> version: 5.10.120-1
> 
> i am running virtualbox 6.1.34 from the virtualbox.org repo on a debian
> 11.3 host. the guest also runs debian 11.3.
> 
> when both host and guest run the latest stable kernel 5.10.0-15
> (5.10.120-1) i get random process crashes in the guest when having
> significant i/o for longer than a few seconds on the host.
> 
> and eventually guest processes start to randomly crash, e.g.:
> 
> Jun 30 20:17:01 vmguest kernel: traps: sh[250946] general protection fault
> ip:7fb0c341708e sp:7ffec3154378 error:0 in
> libc-2.31.so[7fb0c33a6000+14b000]
> Jul 01 00:00:02 vmguest kernel: traps: hostname[253617] general protection
> fault ip:7f905f2b24a6 sp:7fff44a30e30 error:0 in
> libc-2.31.so[7f905f299000+14b000]
> Jul 01 00:53:01 vmguest kernel: traps: wget[254290] general protection
> fault ip:7f934bc23fda sp:7ffd716954d0 error:0 in
> libtasn1.so.6.6.0[7f934bc1a000+c000]
> 
> if i switch to kernel 5.10.0-14 (5.10.113-1) on the host (the guest kernel
> remains 5.10.0-15), then the random process crashes in the guest disappear,
> although the complaints from hrtimer and clocksource still remain, but
> significantly less often.

This indeed looks like an upstream regression between 5.10.113 and 5.10.120.

What surprises me are the time gaps between those GPF messages, ~3.5h and 50m, 
but not within the same second/minute. What happens between those time stamps?

If there are more messages around those GPF messages, it would be useful to 
share those as well.

In Stable-Proposed-Updates there is a 5.10.127-1 version and it would be 
useful to test whether the issue happens with that version too.

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

Bug#966621: systemd: tmpfiles.d not cleaning /var/tmp by default

[Michael Biebl]

Hi Eric

On Fri, 31 Jul 2020 15:12:48 + Eric Desrochers 
 wrote:

Package: systemd
Version: 245.7-1
Severity: normal

Dear Maintainer,

Debian systemd implementation does not clean
/var/tmp by default.

* quilt patch:
d/p/debian/Bring-tmpfiles.d-tmp.conf-in-line-with-Debian-defaul.patch

* systemd-245.7/tmpfiles.d/tmp.conf:
#q /var/tmp 1777 root root 30d

The patch exist in Debian since 2012.

The topic has been discussed and a few suggestion has been put on the
table in the following Ubuntu bug: https://launchpad.net/bugs/1870585

I fill this bug today to start a conversation.


I haven't received any further input from your side.
Are you still interested in this issue or not?
I wonder where to go from here and what to do about this bug report.

Regards,
Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009712: sv: fails to control the service on Hurd

[João Pedro Malhado]

Hello Samuel,

As you suggested the open64() function being used seems to be that defined in
sysdeps/mach/hurd/open.c

However errnno is already 1073741902 before the function call, so does not
really change after the function call. On the other hand the variable fd that
stores the value returned from open() flips from 0 to -1. I attach a brief gdb
log.

So I don't know what to look for at the moment.

Best regards,
João
Breakpoint 1 at 0x17b0: control. (2 locations)
Starting program: /usr/bin/sv start cron
[New Thread 829.5]

Thread 4 hit Breakpoint 1, control (a=0x803cbe0 "u")
at ./runit-2.1.2/src/sv.c:253
253 ./runit-2.1.2/src/sv.c: No such file or directory.
svstatus_get () at ./runit-2.1.2/src/sv.c:94
94  in ./runit-2.1.2/src/sv.c
open_write (fn=0x803caa0 "supervise/ok") at ./runit-2.1.2/src/open_write.c:8
8   ./runit-2.1.2/src/open_write.c: No such file or directory.
$1 = 0
$2 = 1073741902
open64 (__oflag=10, __path=0x803caa0 "supervise/ok")
at /usr/include/i386-gnu/bits/fcntl2.h:53
53return __open_alias (__path, __oflag, __va_arg_pack ());
__GI___libc_open (file=0x803caa0 "supervise/ok", oflag=10)
at ../sysdeps/mach/hurd/open.c:35
35  ../sysdeps/mach/hurd/open.c: No such file or directory.
45  in ../sysdeps/mach/hurd/open.c
46  in ../sysdeps/mach/hurd/open.c
47  in ../sysdeps/mach/hurd/open.c
49  in ../sysdeps/mach/hurd/open.c
svstatus_get () at ./runit-2.1.2/src/sv.c:95
95  ./runit-2.1.2/src/sv.c: No such file or directory.
$3 = -1
$4 = 1073741902
Continuing.
[Inferior 1 (bogus thread id 0) exited with code 01]

Bug#1014417: meson: test changes causes FTBFS

[Jeremy Bicha]

Source: meson
Version: 0.63.0-1
Severity: serious
Tags: patch
Control: affects -1 src:gjs

gjs fails to build from source with the new meson.
https://gitlab.gnome.org/GNOME/gjs/-/issues/490

The test output was overhauled in the new meson version so maybe that's related.

Thank you,
Jeremy Bicha

Bug#1014418: ITP: libelas -- Library for Efficient Large-scale Stereo Matching

[Dima Kogan]

Package: wnpp
Owner: Dima Kogan 
Severity: wishlist

* Package name: libelas
  Version : 20153006
  Upstream Author : Andreas Geiger
* URL or Web page : http://www.cvlibs.net/software/libelas/
* License : GPL
  Description :  Library for Efficient Large-scale Stereo Matching

Bug#890824: Container: unsets cgroup memory limit on user login

[Michael Biebl]

On Mon, 29 Mar 2021 07:49:24 +0200 Maximilian Philipps 
 wrote:

hi Michael,

I currently can't test that. Given that bullseye isn't released yet, I 
don't have a test environment here.


When bullseye is released I will try to test it again, for time being I 
have moved all libvirt-lxc container to use lxc.


Any updates here?
Ideally, if you run bullseye and you still encounter the problem, 
install systemd v250 from bullseye-backports and if the problem 
persists, file it upstream at https://github.com/systemd/systemd/issues/

and report back with the issue number

Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004687: systemd: When NFS filesystems are mounted, systemctl actions (ex: daemon-reload) are exceedingly slow

[Michael Biebl]

On Mon, 31 Jan 2022 19:03:49 -0500 Brandon Applegate  
wrote:

Mounting as rw didn’t seem to help.  Shortly after that - a random try of 
“systemctl reload-daemon” resulted in the same hang/delay.  I noticed again 
that the systed fstab generator was running.  I managed to strace it (missed 
the beginning of course) - and it was hanging.  Eventually I got this:

strace: Process 56818 attached
--- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=56808, si_uid=0} ---
+++ killed by SIGTERM +++

I’m guessing it wasn’t responding so systemd killed it ?

Is there anything else I can do to try to troubleshoot this ?


Brandon,

this doesn't appear to be a Debian specific issue.
Could you please install systemd v250 from bullseye-backports and test 
if the problem is still reproducible.


If so, I would kindly ask you to file the issue upstream at 
https://github.com/systemd/systemd/issues/new


Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013342: systemd - Please backport support for Hyper-V on arm64 to stable

[Michael Biebl]

On Wed, 22 Jun 2022 10:58:43 +0200 Bastian Blank  wrote:

Package: systemd
Version: 247.3-7
Severity: important

Hi

Please backport support for detecting Microsoft Hyper-V on arm64 to
stable.

Commits are:
- 506bbc8569014253ea8614b680ccbc4fc2513a87
- 76eec0649936d9ae2f9087769f463feaf0cf5cb4

This adds new hardware support, which makes it suitable for a stable
update, thus reported with severity "important".

Patches I used are attached.


Ok. I guess we can consider these patches for the next stable upload.


For me, systemd failed to build on stable, due to missmatch between
/usr/include/linux/if_arp.h and ./src/basic/linux/if_arp.h.  This needs
to be fixed as well.


Are you using a newer kernel from backports/self compiled?
I can not reproduce a build failure with a "clean" bullseye environment.

Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012829: Updates -

[Troy Telford]

I have built a vanilla kernel 5.17.6 to replicate the issue, but before I was 
able to test it (to reproduce it and send a report to kernel.org 
’s bugzilla), I became very ill with COVID-19, which put 
everything on hold for a while.

Now that I’ve largely recovered, I have been able run a system apt upgrade - 
and noticed that the zfs modules have been updated to support kernel 5.18, so I 
am now able to test against `linux-image-5.18.0-2` - it seemed to make sense to 
see if I could reproduce against that first, if only to see if a newer kernel 
resolved the issue.

It appears that was the correct move:

- I’ve been able to boot the Debian 5.18.0-2 linux-image package,
- After about nine days of uptime, I’ve been unable to reproduce the issue.
- There are none of the `DMAR: DRHD: handling fault` messages in the kernel log.

I believe this bug can be closed, as it does not appear to be an issue with the 
current kernels.


signature.asc
Description: Message signed with OpenPGP

Bug#1014394: Also Affected - linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Richard Laysell]

Hello,

I am also affected by this same bug.

I run Firefox in a virtual machine and if I am running the
5.10.0-15-amd64 kernel on the virtual host, then Firefox crashes
regularly in the virtual guest.

However, if I run the 5.10.0-14-amd64 kernel on the virtual host, then
I see no crashes.

In both cases the virtual guest is running the 5.10.0-15-amd64 kernel

This is on Debian Bullseye

VirtualBox packages are from Fasttrack
virtualbox   6.1.34-dfsg-3~fto11+1amd64
virtualbox-dkms  6.1.34-dfsg-3~fto11+1amd64
virtualbox-qt6.1.34-dfsg-3~fto11+1amd64

Kernels are the standard Debian kernels from stable (both host and
guest)
linux-image-5.10.0-14-amd64  5.10.113-1   amd64
linux-image-5.10.0-15-amd64  5.10.120-1   amd64

I have seen this issue on two separate systems, so I do not think it is
hardware related.

Happy to do any testing or provide any logs you can suggest.

Regards,

Richard

Bug#1014416: mp3fs: Files with brackets "[]" not readable in 64bit version of Raspbian (mp3fs version 1.1.0)

[Benjamin]

Package: mp3fs
Version: 1.1.0
Severity: important
X-Debbugs-Cc: deb...@bviertel.de

Dear Maintainer,

Bullseye comes with mp3fs v1.1.0 which contains a bug where files with brackets 
"[]" are not readable. 

This is known. 

The maintainer of mp3fs suggests using version 1.1.1 which fixes this problem. 
1.1.1 is included in other versions already. See also: 
https://github.com/khenriks/mp3fs/issues/73

The bug report might be missing data because I removed the package from my 
system and instead build from source version 1.1.1.

I use Raspian 64bit.

Thanks for considering patching this nice tool!

Ben


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.52-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 mp3fs depends on:
ii  libc6   2.31-13+rpt2+rpi1+deb11u2
ii  libflac++6v51.3.3-2+deb11u1
ii  libflac81.3.3-2+deb11u1
ii  libfuse22.9.9-5
ii  libgcc-s1   10.2.1-6
ii  libid3tag0  0.15.1b-14
ii  libmp3lame0 3.100-3
ii  libstdc++6  10.2.1-6
ii  libvorbis0a 1.3.7-1
ii  libvorbisfile3  1.3.7-1

mp3fs recommends no packages.

mp3fs suggests no packages.

Bug#1011443: faker,ruby-faker: error when trying to install together

[Timo Röhling]

On Mon, 23 May 2022 01:58:56 +0200 Andreas Beckmann  wrote:

Package: faker,ruby-faker
Severity: serious
Tags: sid bookworm
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.9.3-0.1
Control: found -1 2.20.0-1

[...]
Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/faker

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package.

I'm posting to d-devel because I failed to make contact with the
Ruby Team directly:

ruby-faker primarily ships a Ruby module while faker's sole purpose
is the faker executable, so I believe ruby-faker should yield.
There are two reverse dependencies:

- ruby-devise-two-factor builds fine without /usr/bin/faker in
  ruby-faker

- ruby-omniauth-openid-connect FTBFS for unrelated reasons with and
  wihout /usr/bin/faker

If the Ruby Team agrees with my analysis, I'd appreciate it if
someone could upload a fixed version (I am not a team member).


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1014115: uninstall does not properly remove enablement symlinks

[Michael Biebl]

Am 04.07.22 um 13:13 schrieb Luca Boccassi:

On Mon, 4 Jul 2022 at 11:55, Michael Biebl  wrote:



Am 04.07.22 um 12:36 schrieb Luca Boccassi:

I have uploaded i-s-h, should we close this one now?


I've seen the upload. Thanks!

I was debating with myself whether systemd-homed should get a tightened,
versioned Depends on i-s-h to prevent this issue from happening.

This would make a backport a bit harder, but maybe a stable upload of
i-s-h with this fix is a good idea anyway?

Regards,
Michael


It's a new package and optional, so maybe it's not worth it - but up
to you, if you want to add that and a backport to be safer, I don't
have any objection.


Ok, I'll add the versioned Depends on i-s-h then and also make a 
corresponding backports upload. That's the least I can do.


I'm currently working on a systemd v251 backport and would include this 
change there as well.


Regards and thanks again for the i-s-h fix,

Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0

[Paul Cercueil]

Le mar., juil. 5 2022 at 15:51:08 +0200, Michel Dänzer 
 a écrit :

On 2022-07-05 14:48, Paul Cercueil wrote:


 Is there a way I can provide more information?


Come to think of it, capturing the journal output after trying to 
start an X11 client might be interesting:


 journalctl --user -b0


This was giving me zero results so I ran 'journalctl -b0' and some 
things happened when trying to run 'xterm':


juil. 05 17:24:02 frank gnome-shell[3952]: (WW) Option "-listen" for 
file descriptors is deprecated
juil. 05 17:24:02 frank gnome-shell[3952]: Please use "-listenfd" 
instead.
juil. 05 17:24:02 frank gnome-shell[3952]: (WW) Option "-listen" for 
file descriptors is deprecated
juil. 05 17:24:02 frank gnome-shell[3952]: Please use "-listenfd" 
instead.
juil. 05 17:24:03 frank kernel: nouveau :01:00.0: Enabling HDA 
controller
juil. 05 17:24:03 frank kernel: nouveau :01:00.0: bus: MMIO write 
of e56bf91f FAULT at 6013d4 [ PRIVRING ]
juil. 05 17:24:03 frank gnome-shell[3952]: libEGL warning: DRI2: failed 
to create dri screen
juil. 05 17:24:03 frank gnome-shell[3952]: libEGL warning: DRI2: failed 
to create dri screen
juil. 05 17:24:03 frank gnome-shell[3957]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
juil. 05 17:24:03 frank gnome-shell[3957]: > Warning:  Could 
not resolve keysym XF86EmojiPicker
juil. 05 17:24:03 frank gnome-shell[3957]: Errors from xkbcomp are not 
fatal to the X server
juil. 05 17:24:03 frank systemd[2111]: Starting GNOME XSettings 
service...
juil. 05 17:24:03 frank gnome-shell[3960]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
juil. 05 17:24:03 frank gnome-shell[3960]: > Warning:  
Unsupported maximum keycode 708, clipping.
juil. 05 17:24:03 frank gnome-shell[3960]: >   X11 
cannot support keycodes above 255.
juil. 05 17:24:03 frank gnome-shell[3960]: Errors from xkbcomp are not 
fatal to the X server
juil. 05 17:24:03 frank gsd-xsettings[3959]: Impossible d’ouvrir 
l’affichage :
juil. 05 17:24:03 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
code=exited, status=1/FAILURE
juil. 05 17:24:03 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Failed with result 
'exit-code'.
juil. 05 17:24:03 frank systemd[2111]: Failed to start GNOME XSettings 
service.
juil. 05 17:24:03 frank gnome-shell[2215]: Window manager warning: 
L’initialisation de GDK a échoué
juil. 05 17:24:03 frank gnome-shell[2215]: Failed to initialize X11 
display: Failed to initialize GDK
juil. 05 17:24:03 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, 
restart counter is at 1.

juil. 05 17:24:03 frank systemd[2111]: Stopped GNOME XSettings service.
juil. 05 17:24:03 frank systemd[2111]: Starting GNOME XSettings 
service...
juil. 05 17:24:03 frank gsd-xsettings[3962]: Impossible d’ouvrir 
l’affichage :
juil. 05 17:24:03 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
code=exited, status=1/FAILURE
juil. 05 17:24:03 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Failed with result 
'exit-code'.
juil. 05 17:24:03 frank systemd[2111]: Failed to start GNOME XSettings 
service.
juil. 05 17:24:04 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, 
restart counter is at 2.

juil. 05 17:24:04 frank systemd[2111]: Stopped GNOME XSettings service.
juil. 05 17:24:04 frank systemd[2111]: Starting GNOME XSettings 
service...
juil. 05 17:24:04 frank gsd-xsettings[3964]: Impossible d’ouvrir 
l’affichage :
juil. 05 17:24:04 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
code=exited, status=1/FAILURE
juil. 05 17:24:04 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Failed with result 
'exit-code'.
juil. 05 17:24:04 frank systemd[2111]: Failed to start GNOME XSettings 
service.
juil. 05 17:24:04 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, 
restart counter is at 3.

juil. 05 17:24:04 frank systemd[2111]: Stopped GNOME XSettings service.
juil. 05 17:24:04 frank systemd[2111]: Starting GNOME XSettings 
service...
juil. 05 17:24:04 frank gsd-xsettings[3966]: Impossible d’ouvrir 
l’affichage :
juil. 05 17:24:04 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Main process exited, 
code=exited, status=1/FAILURE
juil. 05 17:24:04 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Failed with result 
'exit-code'.
juil. 05 17:24:04 frank systemd[2111]: Failed to start GNOME XSettings 
service.
juil. 05 17:24:04 frank systemd[2111]: 
org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, 
restart counter is at 4.

juil. 05 17:24:04 frank systemd[2111]: Stopped GNOME XSettings service.
juil. 05 17:24:04 frank systemd[2111]: Starting GNOME XSettings 
service...
juil. 05 17:24:04 frank gsd-xsettings[3968]: Impossible d’ouvrir 
l’affichage :
juil. 05 

Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0

[Paul Cercueil]

Le mar., juil. 5 2022 at 15:31:25 +0200, Michel Dänzer 
 a écrit :

On 2022-07-05 14:48, Paul Cercueil wrote:

 Hi Michel,

 I hate to bump bug reports, but this one is pretty crippling - lots 
of applications I use every day end up not booting.


Is that all the X11 ones, or only some of them?


All of them. Even the simple ones like 'xterm' fail to start.


 I end up having to work under Windows, ugh.


Surely you can use a GNOME on Xorg session in the worst case.


Is that still a thing? I can't select Gnome on X11 anymore since the 
last few releases of Gnome. GDM simply doesn't give me the option.


-Paul


 Is there a way I can provide more information?


I have no clue what's going on here, nor what to look for. :(


--
Earthling Michel Dänzer|  
https://redhat.com
Libre software enthusiast  | Mesa and Xwayland 
developer

Bug#1014380: vagrant: Unable to activate net-sftp-3.0.0, because net-ssh-7.0.1 conflicts with net-ssh (>= 5.0.0, < 7.0.0)

[Antonio Terceiro]

Control: reassign -1 ruby-net-ssh
Control: notfound -1 1:7.0.0~beta1-2
Control: found -1 1:7.0.1-1
Control: retitle -1 ruby-net-ssh: breaks version expectations of ruby-net-sftp
Control: affects -1 vagrant

On Tue, Jul 05, 2022 at 10:31:09AM +0200, Kyle Robbertze wrote:
> Package: vagrant
> Version: 2.2.19+dfsg-1
> Severity: important
> 
> Dear Maintainer,
> 
> Vagrant currently fails to start due to the following error:
> 
> $ vagrant up focal
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in 
> `raise_if_conflicts': Unable to activate net-sftp-3.0.0, because 
> net-ssh-7.0.1 conflicts with net-ssh (>= 5.0.0, < 7.0.0) (Gem::ConflictError)
> from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1379:in 
> `activate'
> from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1417:in 
> `block in activate_dependencies'
> from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `each'
> from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
> from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
> from /usr/lib/ruby/vendor_ruby/rubygems.rb:286:in `block in 
> activate_bin_path'
> from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize'
> from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path'
> from /usr/bin/vagrant:25:in `'

This is a problem between ruby-net-ssh and ruby-net-sftp. Downgrading
ruby-net-ssh to the version in testing should work around this before
ruby-net-sftp is either upgraded or patched to relax the dependency on
ruby-net-ssh.


signature.asc
Description: PGP signature

Bug#906752: sudo, pam_keyinit, what to do?

[Andreas Henriksson]

Hello Marc, Chris,

Sorry for my late (and possibly pretty lame) reply.

On Tue, Jul 05, 2022 at 03:17:19PM +0200, Marc Haber wrote:
> 
> On Sun, Feb 06, 2022 at 05:09:10PM +0100, Chris Hofstaedtler wrote:
> > * Marc Haber  [220206 12:36]:
[...]
> > > May I ask for you rationale to do things the way you did them for su and
> > > pam_keyinit? Your insights might help us to take a wise decision for
> > > sudo.
> > 
> > I do not know why this was done for su-l and not su. My speculation
> > would be that we have inherited the su-l PAM config from Fedora, and
> > the su PAM config from src:shadow before 2018. Maybe the distinction
> > is an accident.
> > 
> > Andreas, you worked on the su takeover from src:shadow. Do you have
> > insights to share?
> 
> Andreas, did you read this?
[...]

I have a very bad memory which is why I try to write down as much as
possible in bug reports, commit messages, etc to leave hints for my
future self. I need to dig to figure things out myself, but I think the
above description is basically correct.

(If there's any message from me that you have a problem with
interpretting what it means, please point me to it and I can try to
interpret my own bad grammar to figure out what I tried to write.)

Regards,
Andreas Henriksson

Bug#1014413: ITS: zeal. I would like to help packaging zeal to revive it

[陳昌倬]

On Tue, Jul 05, 2022 at 05:45:12PM +0200, Martin Quinson wrote:
> Package: zeal
> Version: 1:0.6.1-1.2
> Severity: important
> 
> Hello,
> 
> I think that the packaging of Zeal stalled somehow in the recent years. The
> last maintainer upload was back in 2018, and there were 2 NMU since then. 
> There
> is a MR on salsa, but no answer from the maintainer.
> 
> I'm not blaming anyone here, it's just that I do have interest in this package
> and I intend to help if I can. Please ChangZhuo tell me how I can help you.
> 
> If you don't answer before July 26., I will upload a new version adding myself
> as a co-maintainer. My dream would be to go for co-maintenance here, and I
> would love to hear from you so that I can start working on the update before
> end-July if possible.
> 
> Thanks for all the good work you've done so far, and for your future answer.
> Mt

Hi Martin,

Please process, thanks for the help.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1014415: ITP: dispatch -- incident management tool

[Jelmer Vernooij]

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

* Package name: dispatch
  Version : 20220607
  Upstream Author : Netflix
* URL : https://github.com/netflix/dispatch
* License : Apachev2
  Programming Lang: Python
  Description : incident management tool

Dispatch helps effectively manage (security) incidents by deeply integrating
with existing tools used throughout an organization (Slack, GSuite, Jira,
etc.,) Dispatch is able to leverage the existing familiarity of these tools to
provide orchestration instead of introducing another tool.

This means you can let Dispatch focus on creating resources, assembling
participants, sending out notifications, tracking tasks, and assisting with
post-incident reviews; allowing you to focus on actually fixing the issue!

Bug#1014413: ITS: zeal. I would like to help packaging zeal to revive it

[Martin Quinson]

Package: zeal
Version: 1:0.6.1-1.2
Severity: important

Hello,

I think that the packaging of Zeal stalled somehow in the recent years. The
last maintainer upload was back in 2018, and there were 2 NMU since then. There
is a MR on salsa, but no answer from the maintainer.

I'm not blaming anyone here, it's just that I do have interest in this package
and I intend to help if I can. Please ChangZhuo tell me how I can help you.

If you don't answer before July 26., I will upload a new version adding myself
as a co-maintainer. My dream would be to go for co-maintenance here, and I
would love to hear from you so that I can start working on the update before
end-July if possible.

Thanks for all the good work you've done so far, and for your future answer.
Mt


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

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

Versions of packages zeal depends on:
ii  libarchive13   3.6.0-1
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-2
ii  libqt5concurrent5  5.15.2+dfsg-16+b2
ii  libqt5core5a   5.15.2+dfsg-16+b2
ii  libqt5gui5 5.15.2+dfsg-16+b2
ii  libqt5network5 5.15.2+dfsg-16+b2
ii  libqt5sql5-sqlite  5.15.2+dfsg-16+b2
ii  libqt5webkit5  5.212.0~alpha4-16
ii  libqt5widgets5 5.15.2+dfsg-16+b2
ii  libqt5x11extras5   5.15.2-2
ii  libsqlite3-0   3.38.5-1
ii  libstdc++6 12.1.0-2
ii  libx11-6   2:1.7.5-1
ii  libxcb-keysyms1    0.4.0-1+b2
ii  libxcb1    1.14-3

zeal recommends no packages.

zeal suggests no packages.

-- no debconf information



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

Bug#1014412: RFS: kmscon/9.0.0-2 -- Simple terminal emulator based on Kernel Mode Setting

[Victor Westerhuis]

Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear mentors,

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

 * Package name: kmscon
   Version : 9.0.0-2
   Upstream Author : https://github.com/Aetf/kmscon/issues
 * URL : https://github.com/Aetf/kmscon
 * License : LGPL-2.1+, public-domain, GPL-2 with Font exception, Expat 
and HPND, Expat
 * Vcs : https://salsa.debian.org/viccie30/kmscon
   Section : utils

The source builds the following binary packages:

  kmscon - Simple terminal emulator based on Kernel Mode Setting

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/k/kmscon/kmscon_9.0.0-2.dsc

Changes since the last upload:

 kmscon (9.0.0-2) unstable; urgency=medium
 .
   * Run agetty instead of login (Closes: #1014316)
   * Bump Standards-Version to 4.6.1

Regards,
- -- 
  Victor Westerhuis


-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmLES4wTHHZpY3RvckB3
ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+7V9EACM+eM1xA1IKNv+Qw7mXKBYfUmRRTzu
tdnndbzo27WEoBUVHGJOHvX+FpZ/Je1nDvW+ZMmqI9MQDnyTwzc0eP60UQYZVc4L
po2oMZPtcmbaC4wLpiebgx/iTAvlC68ks1cmC/eBPrRwgk1PsMuhaVHsei1dQj5W
PA4HJJEeWC2QLU7jHiTjn2Z9852xD56H6LF9ucyaj/lZLZEn5Mr8s2PaBu1w0Zly
x4haPY6zZ4GRLJa/QJtLSzxBDhlS2KMhB2LL2c4PaqU3shG9RpavGmtcZ0aM5M4p
ou6BVMVSnu3ijfIBW/1LBAm1mGVoR9p/tvqWnKVnAppJY3Ge7E56YssnbEaM5Z1O
5Jom1afWJZJWE81ifRBfEN4qGSQKgrPnUYMPDst7+32GDxH3z/9kE8uu3v895CCx
HY6bK6m+GoWQeZQ+WtRHXxaEDMECwyCrAfxrGOpNw7gLJjg6rnG5IwPHxAXZZ/Fr
J2r8PmdUafRvqZmChJ/OlzSM95cwFUIgDy5u7XLHHclfuOD3LY7mYoq0hvlMCyGs
1apLSzy0PTkGU8eZnVKNq6kbms4Lhj2uM3LCBDxv5f582nS7UZNCBfQqJgY45s4i
c2Rb2OYMUHurWHprIhn5eKxj9sNIWnSIV0LdlzjxulZHRzUk0tj7I35iO1D7vA4R
RdBF0sXtNIJneQ==
=TxBa
-END PGP SIGNATURE-

Bug#1014411: dvcs-autosync: Should we remove this package?

[Boyuan Yang]

Source: dvcs-autosync
Version: 0.5+nmu1
Severity: important
Tags: sid
X-Debbugs-CC: rm...@debian.org

Dear Debian dvcs-autosync package maintainer,

I checked the condition of package dvcs-autosync in Debian
at https://tracker.debian.org/pkg/dvcs-autosync , and it looks like it
received no maintainer uploads in the past 12 years. Also, it is affected by
python2 removal and missed last Stable release. As a result, I believe it is
time to have this package removed from Debian archive.

Please let me know if you have any comments on the removal proposal. If
there is no objections in the next 14 days, I will proceed and submit a
package removal request against Debian FTP Masters. If you have any
questions, please feel free to let me know.

Regards,
Boyuan Yang


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

Bug#1014410: xnecview: No longer correctly displays antenna geometry

[Ralf Schlatterbeck]

Package: xnecview
Version: 1.37-1
Severity: normal

xnecview can
- Display the antenna geometry if given a .nec file as input
- Display the antenna pattern and other graphs if given the output of
  nec2c

The latter still works. The display of the antenna geometry no longer
works, I'm including an example .nec file and the corresponding output
as well as the expected output. This is a regression from Debian Buster.


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

Kernel: Linux 5.10.0-10-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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 xnecview depends on:
ii  libc6 2.31-13+deb11u3
ii  libglib2.0-0  2.66.8-1
ii  libgtk2.0-0   2.24.33-2
ii  libpng16-16   1.6.37-3

xnecview recommends no packages.

xnecview suggests no packages.

-- no debconf information
CM -r 0.0291 -d 0.0424 -l 0.1712 -4 0.1174
CM FRQ: 430.00 fw: 6.85 bw: -2.58
CM FRQ: 435.00 fw: 6.62 bw: -4.50
CM FRQ: 440.00 fw: 6.35 bw: -5.41
CM SWR: 1.79 1.11 1.81
CE
GA 1 17 0.0291 -90 90 0.00075
GM 0 0 0 0 0 0.1174 0 0 1
GA 2 17 0.0291 90 270 0.00075
GM 0 0 0 0 0 -0.1174 0 0 2
GW 3 19 0 0 0.0291 -0.1174 0 0.0291 0.00075
GW 4 19 0 0 -0.0291 -0.1174 0 -0.0291 0.00075
GW 5 19 0 0 0.0291 0.1174 0 0.0291 0.00075
GW 6 19 0 0 -0.0291 0.1174 0 -0.0291 0.00075
GW 7 5 0 0 0.0291 0 0 -0.0291 0.00075
GW 8 5 0 0 -0.0291 0 0 -0.0715 0.00075
GW 9 57 0.1712 0 -0.0715 0 0 -0.0715 0.00075
GW 10 57 -0.1712 0 -0.0715 0 0 -0.0715 0.00075
GM 0 0 0 270 0 0 0 0.1712 0
GE 0
EK 1
LD 5 0 0 0 3.77358e+07 0 0
EX 0 6 1 0 1 0 0 0 0 0
FR 0 21 0 0 430 0.5
RP 0 37 73 0 0 0 5 5 0 0
EN

Bug#986765: AMD SEV guest crash after "Loading initial ramdisk ..."

[Olivier Desenfans]

Hi!


I stumbled upon the exact same issue with bullseye. Turns out, upgrading 
the kernel to Linux 5.18 fixes the issue. I have not pinpointed the 
exact bug/patch that resolves this.


More precisely, I upgraded the kernel image to 
5.18.0-0.bpo.1-cloud-amd64 using the 
debian-11-nocloud-amd64-20220613-1045.qcow2 image as a base. Tested on 
Qemu 7.0.


Best regards,

Olivier

On Sun, 11 Apr 2021 20:12:20 +0200 =?utf-8?B?SsOhbiBNw6F0w6k=?= 
 wrote:


> Package: qemu-system-x86
> Version: 1:5.2+dfsg-9
>
> When I try to boot an AMD SEV enabled guest OS it crashes immediately 
after the "Loading initial ramdisk ..." message (the result is infinite 
reboot loop). Here is my libvirt XML which works fine without the 
"..." XML element (which enables the 
AMD SEV):

>
> 
> test
> 4dea22b3-1d52-d8f3-2516-782e98ab3fa0
> ab826c0a-a349-4470-bbb9-d2b6ee23e8c3
> Test Server
> 8388608
> 8388608
> 
> 9437184
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 4
> 1
> 
> hvm
> 
> /var/lib/libvirt/qemu/nvram/test_VARS.fd
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> destroy
> restart
> coredump-restart

Bug#1014401: libburn: Add symbol file

[Thomas Schmitt]

Hi,

like with bug #1014400 i see problems between the purpose of .symbols
and the expectations of upstream code.
Upstream code of libisoburn knows what it demands as minimum version.
Any contrary decision by a Debian packaging program can only lead to
intentional failure at compile time or at run time.

See also:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014400#10

(Additionally to the scruples expressed there, it comes to me that
the goal of .symbols does not care for important bug fixes. A symbol
may exist longer than the version where such bugs are fixed.)


Have a nice day :)

Thomas

Bug#1014392: mingw-w64: ftbfs on riscv64(error: #error Unknown CPU architecture!)

[Paul Wise]

On Tue, 2022-07-05 at 17:42 +0800, Bo YU wrote:

> The patch attached is to fix the issue and I can build the package 
> on my locally real riscv64 hardware(Unmatched board) with it.
...
> +#elif defined(__riscv) && __riscv_xlen == 64
> +# define WORDS_BIGENDIAN

I don't think this patch is correct, riscv64 is little-endian.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1013984: r-cran-v8: configure assumes V8_COMPRESS_POINTERS=true but it is not

[Nilesh Patra]

Control: severity -1 important

On Tue, 28 Jun 2022 15:23:08 +0200 =?utf-8?b?SsOpcsOpbXkgTGFs?= 
 wrote:
> Source: r-cran-v8
> Version: 4.2.0+dfsg-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> When building r-cran-v8 against nodejs 18.4.0 in experimental,
> this happened:
> # Fatal error in , line 0
> # Embedder-vs-V8 build configuration mismatch. On embedder side pointer 
> compression is ENABLED while on V8 side it's DISABLED.

Since nodejs 18 is in exp and not unstable, the severity should be important 
instead.
It will be serious only when nodejs 18 is in unstable/testing.

> It is true that nodejs is built with V8_COMPRESS_POINTERS=false,
> so r-cran-v8 detection has a problem.
> 
> This will prevent migration of nodejs 18 to testing,
> so I'll gladly make a quick patch to fix the build.

Thanks.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1014400: libisofs: Add symbol file

[Thomas Schmitt]

Hi,

do i get it right that the format is specified by
  https://wiki.debian.org/Projects/ImprovedDpkgShlibdeps
?

If so, then the goal of having the file

  "In many cases, the dependency generated is too strict as the
   application doesn't necessarily use the newly-added symbols which
   justify the dependency bump in the shlibs file."

collides with the upstream version check of libisoburn towards libisofs.
libisoburn will not work with a libisofs version that is older than
seen at compile time.
The minimum version at compile time is defined in libisoburn.h (i.e.
part of the API):

  /** The minimum version of libisofs to be used with this version of libisoburn
  at compile time.
  @since 0.1.0
  */
  #define isoburn_libisofs_req_major  1
  #define isoburn_libisofs_req_minor  5
  #define isoburn_libisofs_req_micro  4

So if the Debian packaging software decides on its own that libisofs-1.5.2
is enough at package build time, then compilation will fail.
If the package manager decides that libisofs-1.5.2 is good enough at
run time, then the start-up of libisoburn will fail.
Both failures are intentional and make function isoburn_initialize()
as ugly as paranoid.
  https://sources.debian.org/src/libisoburn/1.5.4-2/libisoburn/burn_wrap.c/#L74

In general i don't think it is worthwhile to offer old versions of
libisofs to programs which get installed on a system where a newer
version is available.

-

The .symbols file looks like maintainance effort, if it shall express
more than the existing .ver file (i.e. the list of ABI symbols of
the current version).

Google is not overly helpful with search test ".symbols".
Is that file format specific to Debian and its derivatives or does it
play a role in more generic build facilities ?

The API description in libisofs.h contains information about the version
where a symbol appeared first (IIRC starting with 0.6.2 of 2008). So it
would be possible to create a more differenciated .symbols file than
attributing any symbol to version 1.5.4.

But if it is only to tell the Debian package build software that really,
really 1.5.4 is the version to use, then i'd propose to generate the
.symbols file freshly in the course of package generation.

(Bystanding DDs please tell me where in ./debian this can be done.
I would use a shell script that creates .symbols from .ver.
In this case it would be nice if that script could learn the upstream
version automatically, so that it has not to be changed with each version.
Of course, some dh_ magic would be welcome too.)


Have a nice day :)

Thomas

Bug#1014408: RFP: echarts -- powerful, interactive charting and data visualization library for browser

[Joseph Nahmias]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: j...@nahmias.net, d...@echarts.apache.org, 
pkg-javascript-de...@lists.alioth.debian.org

* Package name: echarts
  Version : 5.3.3
  Upstream Author : d...@echarts.apache.org
* URL : https://echarts.apache.org/
* License : Apache 2.0
  Programming Lang: JS / Typescript
  Description : powerful, interactive charting and data visualization 
library for browser

Apache ECharts is a free, powerful charting and visualization library offering
an easy way of adding intuitive, interactive, and highly customizable charts to
your commercial products. It is written in pure JavaScript and based on
zrender, which is a whole new lightweight canvas library.

Apache EChartsTM is an open-sourced JavaScript visualization tool, which can
run fluently on PC and mobile devices. It is compatible with most modern Web
Browsers, e.g., IE9/10/11, Chrome, Firefox, Safari and so on. ECharts depends
on ZRender, a graphic rendering engine, to create intuitive, interactive, and
highly-customizable charts.

Bug#1014409: ftp.debian.org: please import libscram-java into bullseye-security

[Markus Koschany]

Package: ftp.debian.org
Severity: important
X-Debbugs-Cc: a...@debian.org

Dear ftp-team,

please import libscram-java into bullseye-security. A security upload
of libpgjava was rejected with the following error message:

libpostgresql-jdbc-java_42.2.15-1+deb11u1_all.deb: Built-Using refers
to non-existing source package libscram-java (= 1.0.0~beta.2-3)

I'm hereby responding to the email as requested.

Thank you

Markus

Bug#1014407: update lintian overrides to new format

[Jelmer Vernooij]

Package: lintian-brush
Version: 0.126
Severity: wishlist

See https://lists.debian.org/debian-devel/2022/06/msg00184.html for background, 
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007002

Paraphrasing a request from Helmut:

in essence, lintian now flags a combination of "?: something [somearg]" + "W: 
mismatched-override something somearg [location]" and the fix is adding square 
braces. 

This might come in the form of fixing:

https://lintian.debian.org/tags/mismatched-override

We may need a database of formats for the lintian tags, so we know where to add 
the [].


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
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 lintian-brush depends on:
ii  devscripts   2.22.2
ii  python3  3.10.4-1+b1
ii  python3-breezy   3.2.2-2
ii  python3-debian   0.1.44
ii  python3-debmutate0.53
ii  python3-distro-info  1.1
ii  python3-dulwich  0.20.44-1
ii  python3-iniparse 0.5-1
ii  python3-iso8601  1.0.2-1
ii  python3-ruamel.yaml  0.17.16-1
ii  python3-tqdm 4.64.0-2
ii  python3-upstream-ontologist  0.1.25-2

Versions of packages lintian-brush recommends:
ii  debhelper13.8
ii  decopy   0.2.4.6-0.1
ii  dos2unix 7.4.3-1
ii  gpg  2.2.35-3
ii  lintian  2.115.2
ii  ognibuild0.0.13-1
ii  python3-asyncpg  0.25.0-2
ii  python3-bs4  4.11.1-1
ii  python3-docutils 0.17.1+dfsg-2
ii  python3-levenshtein  0.12.2-2+b1
ii  python3-lxml 4.8.0-1
ii  python3-markdown 3.3.7-1
ii  python3-pyinotify0.9.6-2
ii  python3-tomlkit  0.9.2-1

Versions of packages lintian-brush suggests:
ii  brz-debian 2.8.68
ii  git-buildpackage   0.9.27
pn  gnome-pkg-tools
ii  po-debconf 1.0.21+nmu1
ii  postgresql-common  241

-- debconf-show failed

Bug#428770: sudo ptrace vulnerability (BugTraq ID: 24287)

[Marc Haber]

Control: outlook -1 close 2022-12-31
thanks

On Thu, Jun 14, 2007 at 02:18:25AM +0200, Norbert Buchmuller wrote:
> As described in http://www.securityfocus.com/bid/24287 sudo is vulnerable
> to an exploit where the executed command can be altered/replaced using
> ptrace(). (Permission in the /etc/sudoers file to run the altered command
> is still needed, but this vulnerability IMO has high security impact still.)

I have readched out to the security team if they're ok with this bug
report being closed. If they don't reply, I plan to close this anyway by
the end of 2022. Consider filing an upstream report and marking this bug
a forwarded; this one is going to stay open then as long as upstream's
report is open.

Debian is not going to make changes to upstream code for this unless the
security team says that we should.

Greetings
Marc

Bug#377136: sudo: visudo editor

[Marc Haber]

Control: outlook -1 close 2022-12-31 if not forwarded

On Thu, Aug 10, 2006 at 10:07:37AM -0600, Bdale Garbee wrote:
> So, that was sort of cute, but from a practical standpoint, it appears
> that /usr/bin/vi isn't guaranteed to exist, so this isn't as trivial to
> change as one might wish.
> 
> If I can figure out how to make sudo use /usr/bin/vi if present and fall
> back to /usr/bin/editor if not, that probably makes sense.  Feel free to
> figure it out for me and provide a patch...

I am not sure whether debian should divert from upstream's behavior in
this regard. if you still care about this after 15 years, please open an
upstream bug report and mark this issue as forwarded. Otherwise, if this
bug is not marked as forwarded by the end of 2022, I'm going to close
this.

Greetings
Marc

Bug#1014186: blueman: leaves stray "Connected" and "Disconnected" popup windows

[Celejar]

On Mon, 4 Jul 2022 17:18:33 +0200
Christopher Schramm  wrote:

> Those popup windows are a fallback for when the required 
> notification-daemon does not work. blueman is intended to be used with a 
> running notification-daemon.

I have no problem with such popups - but they should be *somehow*
dismissable! I currently have six of them on my desktop, they have been
there for days, and I have no idea how to make them go away! Shouldn't
there be some sort of "Okay" button, or some window decoration that
allows them to be closed?

-- 
Celejar

Bug#678615: "users" group is empty

[Matt Barry]

On Tue, 2022-07-05 at 15:34 +0200, Marc Haber wrote:
> On Tue, Jul 05, 2022 at 09:07:11AM -0400, Matt Barry wrote:
> > On Tue, 2022-07-05 at 12:46 +0200, Marc Haber wrote:
> > > (1) Augment the USERS_GID with a USERS_GROUP setting, throwing a
> > > warning
> > >     if both are set.
> > > (2) Set the primary group of a new non-system user created with
> > >     USERGROUPS=no to the USERS_GID or the GID of the USERS_GROUP
> > > (3) Set USERS_GROUP or the Group that has USERS_GID as
> > > supplementary
> > >     group of newly created non-system users with USERGROUPS=yes
> > 
> > if USERS_GID and USERS_GROUP are empty, and USERGROUPS is no... the
> > user gets the "users" group as before?
> 
> If USERGROUPS is no, then currently the new user gets group 100,
> which
> is "users" as per base-passwd. USERS_GID is documented as having 100
> as
> default.

Yup, sounds good.

Bug#678615: "users" group is empty

[Marc Haber]

On Tue, Jul 05, 2022 at 09:07:11AM -0400, Matt Barry wrote:
> On Tue, 2022-07-05 at 12:46 +0200, Marc Haber wrote:
> > (1) Augment the USERS_GID with a USERS_GROUP setting, throwing a
> > warning
> >     if both are set.
> > (2) Set the primary group of a new non-system user created with
> >     USERGROUPS=no to the USERS_GID or the GID of the USERS_GROUP
> > (3) Set USERS_GROUP or the Group that has USERS_GID as supplementary
> >     group of newly created non-system users with USERGROUPS=yes
> 
> if USERS_GID and USERS_GROUP are empty, and USERGROUPS is no... the
> user gets the "users" group as before?

If USERGROUPS is no, then currently the new user gets group 100, which
is "users" as per base-passwd. USERS_GID is documented as having 100 as
default.

Am I missing something?

Greetings
Marc

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

Bug#1014406: ITP: oci-seccomp-bpf-hook -- OCI hook to trace syscalls and generate a seccomp profile

[Domenico Andreoli]

Package: wnpp
Severity: wishlist
Owner: Domenico Andreoli 

* Package name: oci-seccomp-bpf-hook
  Version : 1.2.5-1
  Upstream Author : Valentin Rothberg, Daniel J. Walsh, et al.
* URL : https://github.com/containers/oci-seccomp-bpf-hook
* License : Apache-2.0
  Programming Lang: Go
  Description : OCI hook to trace syscalls and generate a seccomp profile

 This project provides an OCI hook to generate seccomp profiles by
 tracing the syscalls made by the container. The generated profile
 would allow all the syscalls made and deny every other syscall.

-- 
rsa4096: 3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA  356E CC79 2832 ED38 CB05

Bug#1014316: Unexpected behavior at login prompt

[Victor Westerhuis]

On 04/07/2022 02:47, Joseph Carter wrote:

I recently wound up with an ulltrawide monitor that is effectively a 4k
screen with a haircut at 1600 lines … and I'm legally blind. So let me
say that I greatly appreciate this package and the ease with which I
specified a custom DPI to get readable fonts at the console—thank you
for packaging it.

I also appreciate the standard getty fallback. The other distribution
thus far that seems to have kmscon as an option is arch (because of
course it does) and … they describe configuring a specific tty for getty
in case kmscon fails. An automatic fallback seems more elegant.

Thank you for your praise.

 > That said, it behaves a bit strangely prior to logging in, and these
things cause minor usability issues. Chief among these is that backspace
doesn't work. My password is deliberately not short (as in xkcd 936 not
short), and I sometimes mistype it. I've learned that the backspace key
does not work at this login prompt.

This is indeed an error. I will try to get this fixed.


It also doesn't display /etc/issue which might be a symptom of the same
issue, being a different login process than is typically used by Debian
at the console? There might be a workaround, in that case, to run the
more traditional login process under kmscon, but I haven't really
researched that yet and that wouldn't change the default anyway, so a
report is still warranted IMO.
It is caused by running /bin/login directly instead of using (a)getty. 
I'll see what the best solution is, but the fastest solution is to 
update the shipped systemd unit file to use agetty. In some quick 
testing on my own computer, this fixes both issues.


I'll see if I can get a new version uploaded today.

--
Victor Westerhuis 


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013180:

[Alexandr Podgorniy]

Sorry, i registered in your system as sacled, not scaled, and i didn't 
got any responce to email =D


I tried 5.18.0-2-amd64 kernel recently and noticed that it doesn't go to 
sleep when Bluetooth mouse connected. Otherwise it's fine. Not tried 
5.18.5 yet.

Bug#1012547: linux: disable user namespaces per default

[Philippe Cerfon]

On Thu, Jun 16, 2022 at 6:19 PM Philippe Cerfon  wrote:
> Well I guess the 6 or so root security holes, and counting

And here we go already, faster than even I'd have expected:

Say welcome to CVE-2022-32250, the next root security hole which would
apparently have been mitigated if Debian were to ship sane defaults.

Shall we guess how many systems are going to be compromised because of
that?! I guess, none, because attackers surely understand that they
should abuse something that's needed for some containers and flatpaks
:-)

Bug#906752: sudo, pam_keyinit, what to do?

[Marc Haber]

Hi Chris,

thanks for trying to help back in February.

I'm coming back to this after being busy with other things.

On Sun, Feb 06, 2022 at 05:09:10PM +0100, Chris Hofstaedtler wrote:
> * Marc Haber  [220206 12:36]:
> > in sudo, we have currently the situation whether to add calls to
> > pam_keyinit in our pam configuration files. There is quite a number of
> > packages doing this, but the pam_keyinit documentation advises "programs
> > like su" against doing so. However, in Debian, /etc/pam.d/su-l
> > references pam_keyinit, while /etc/pam.d/su doesn't. On the other hand,
> > doas doesnt seem to reference pam_keyinit at all.
> > 
> > If sudo goes the way to mimic what su does, we would reference
> > pam_keyinit in /etc/pam.d/sudo-i which is our form of giving the caller
> > an interactive session, but not in /etc/pam.d/sudo.
> > 
> > May I ask for you rationale to do things the way you did them for su and
> > pam_keyinit? Your insights might help us to take a wise decision for
> > sudo.
> 
> I do not know why this was done for su-l and not su. My speculation
> would be that we have inherited the su-l PAM config from Fedora, and
> the su PAM config from src:shadow before 2018. Maybe the distinction
> is an accident.
> 
> Andreas, you worked on the su takeover from src:shadow. Do you have
> insights to share?

Andreas, did you read this?

> It would appear to me that keyutils and pam_keyinit, and most of the
> util-linux PAM config originate in Fedora(/RH). The Fedora folks
> are probably the ones to ask how all of this is supposed to work.

Chris,
Can you give me a pointer to whom in Fedora I'm supposed to reach out?

Greetings
Marc

Bug#1014404: rust-futures: please update to v0.3.21

[Jonas Smedegaard]

Source: rust-futures
Version: 0.3.17-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to newer upstream release v0.3.21, needed by projects I
am preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLEOIkACgkQLHwxRsGg
ASGRTw/+NcyfiUhN+8eLBnNcR3NVEDNNqNO421mED1hqAcu1Fc4fkd+189MMEEZm
yqhfKsF5xoptP6AUd1dMx0T7I/gyytnqDF3B4dmoIpeRs7FCdivZvnve6uPqFUpw
iHYiIEwSPZhGvxv6HZ/HKmWVqFmFsrGD37YTbTzeIlocvKXcH5uQT7OVP3+3d5xW
5LAiPWRoM0bHNzSkFH7SnqGIG1OC/zTWARVDVh/0rAGXbQIoxDovq3LndElaGdbE
c3Z876dRTFMI9alj1Y6w75wXn/2RSiXVtGq1ybUMrjGG7ZVw+C5kr6Gl/JeY0bbj
iDm8WkVPkT7xKzP51IeTpo06S2aSiEcoic1ZBrXXQDuYS2LFnC6FXKwlgiG+6rcQ
75ykgyrus7V3sEZumZ96wyWhdhz/NEP92BxXrMcUdYgYb9kRTwUGE1qvOIEQnd6I
eGrD/4ay4UOE3r+kw3zt0scXOF0JkmUaD06tP/XRRlkpTpqmSS2fItkm4BNd0Ltz
O1+jr07/LuDtJzUVI2RnAdcmsrWfqnadGnkLbhQaQjuaRVSoEiB5k1VmmmYmF6KB
mDF9VsjUhPA0S6uxcS3nDm1KZXWnpJgdggcYSXBmHfnSYImwYVufIoWfxRTI02dP
81mclFWJreBiXEPIOXhvxaBWFdJY2OGLT9uNRExrpDarrNAa6Pg=
=Guhp
-END PGP SIGNATURE-

Bug#678615: "users" group is empty

[Matt Barry]

On Tue, 2022-07-05 at 12:46 +0200, Marc Haber wrote:
> (1) Augment the USERS_GID with a USERS_GROUP setting, throwing a
> warning
>     if both are set.
> (2) Set the primary group of a new non-system user created with
>     USERGROUPS=no to the USERS_GID or the GID of the USERS_GROUP
> (3) Set USERS_GROUP or the Group that has USERS_GID as supplementary
>     group of newly created non-system users with USERGROUPS=yes

if USERS_GID and USERS_GROUP are empty, and USERGROUPS is no... the
user gets the "users" group as before?

> 
> (The suggestion for USERS_GROUP comes from the fact that the primary
> group is set via GID and supplementary group is set via name. Don't
> we
> all love those twisted UNIX traditions?)

:)

mb

Bug#1014355: adduser: ADD_EXTRA_GROUPS does not work

[Matt Barry]

On Tue, 2022-07-05 at 12:34 +0200, Marc Haber wrote:
> The body of the bug report was empty, and I can not confirm the non
> working of the option.
> 

Apologies, this was filed in error, can be rejected.

Bug#1014403: RFH: slony1-2 -- replication system for PostgreSQL

[Christoph Berg]

Package: wnpp
Severity: normal
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian PostgreSQL Maintainers 

Control: affects -1 src:slony1-2

I request assistance with maintaining the slony1-2 package.

The package is in maintenance mode upstream with very little activity,
but the Debian integration needs work, especially #1003609 and
possibly a deeper look on how to run the testsuite(s).

The package description is:
 Slony-I is an asynchronous master-to-multiple-slaves replication system
 for PostgreSQL with cascading and slave promotion.
 .
 This package contains the support functions that are loaded into the
 PostgreSQL database server.  It needs to be installed on the hosts where
 the database server nodes are running.  This package works with version
 14 of the PostgreSQL server; you need the package that corresponds to
 the version of your database server.
 .
 The actual replication daemon and the administration tools are in the
 package slony1-2-bin.  This package is useless without slony1-2-bin installed
 somewhere in the network.

Christoph

Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0

[Paul Cercueil]

Hi Michel,

I hate to bump bug reports, but this one is pretty crippling - lots of 
applications I use every day end up not booting. I end up having to 
work under Windows, ugh.


Is there a way I can provide more information? I know Xwayland has a 
-verbose option, but I don't even know how to set it, as Xwayland is 
executed by gnome-shell directly.


Cheers,
-Paul

Bug#1014401: libburn: Add symbol file

[Alexandre Ghiti]

Package: libburn
Version: 1.5.4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

The attached patch adds a symbol file for the libburn library.

Thanks for considering the patch.


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

Kernel: Linux 5.15.0-30-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libburn-1.5.4/debian/libburn4.symbols 
libburn-1.5.4/debian/libburn4.symbols
--- libburn-1.5.4/debian/libburn4.symbols   1970-01-01 01:00:00.0 
+0100
+++ libburn-1.5.4/debian/libburn4.symbols   2022-06-22 11:44:16.0 
+0200
@@ -0,0 +1,212 @@
+libburn.so.4 libburn4 #MINVER#
+ LIBBURN4@LIBBURN4 1.5.4
+ burn_abort@LIBBURN4 1.5.4
+ burn_abort_pacifier@LIBBURN4 1.5.4
+ burn_allow_drive_role_4@LIBBURN4 1.5.4
+ burn_allow_untested_profiles@LIBBURN4 1.5.4
+ burn_cdtext_from_packfile@LIBBURN4 1.5.4
+ burn_cdtext_from_session@LIBBURN4 1.5.4
+ burn_disc_add_session@LIBBURN4 1.5.4
+ burn_disc_available_space@LIBBURN4 1.5.4
+ burn_disc_close_damaged@LIBBURN4 1.5.4
+ burn_disc_create@LIBBURN4 1.5.4
+ burn_disc_erasable@LIBBURN4 1.5.4
+ burn_disc_erase@LIBBURN4 1.5.4
+ burn_disc_format@LIBBURN4 1.5.4
+ burn_disc_free@LIBBURN4 1.5.4
+ burn_disc_free_multi_caps@LIBBURN4 1.5.4
+ burn_disc_get_bd_spare_info@LIBBURN4 1.5.4
+ burn_disc_get_cd_info@LIBBURN4 1.5.4
+ burn_disc_get_format_descr@LIBBURN4 1.5.4
+ burn_disc_get_formats@LIBBURN4 1.5.4
+ burn_disc_get_incomplete_sessions@LIBBURN4 1.5.4
+ burn_disc_get_leadin_text@LIBBURN4 1.5.4
+ burn_disc_get_media_id@LIBBURN4 1.5.4
+ burn_disc_get_msc1@LIBBURN4 1.5.4
+ burn_disc_get_multi_caps@LIBBURN4 1.5.4
+ burn_disc_get_phys_format_info@LIBBURN4 1.5.4
+ burn_disc_get_profile@LIBBURN4 1.5.4
+ burn_disc_get_sectors@LIBBURN4 1.5.4
+ burn_disc_get_sessions@LIBBURN4 1.5.4
+ burn_disc_get_status@LIBBURN4 1.5.4
+ burn_disc_next_track_is_damaged@LIBBURN4 1.5.4
+ burn_disc_pretend_blank@LIBBURN4 1.5.4
+ burn_disc_pretend_full@LIBBURN4 1.5.4
+ burn_disc_pretend_full_uncond@LIBBURN4 1.5.4
+ burn_disc_read@LIBBURN4 1.5.4
+ burn_disc_read_atip@LIBBURN4 1.5.4
+ burn_disc_remove_session@LIBBURN4 1.5.4
+ burn_disc_track_lba_nwa@LIBBURN4 1.5.4
+ burn_disc_write@LIBBURN4 1.5.4
+ burn_drive_add_whitelist@LIBBURN4 1.5.4
+ burn_drive_cancel@LIBBURN4 1.5.4
+ burn_drive_clear_whitelist@LIBBURN4 1.5.4
+ burn_drive_convert_fs_adr@LIBBURN4 1.5.4
+ burn_drive_convert_scsi_adr@LIBBURN4 1.5.4
+ burn_drive_d_get_adr@LIBBURN4 1.5.4
+ burn_drive_equals_adr@LIBBURN4 1.5.4
+ burn_drive_extract_audio@LIBBURN4 1.5.4
+ burn_drive_extract_audio_track@LIBBURN4 1.5.4
+ burn_drive_free_speedlist@LIBBURN4 1.5.4
+ burn_drive_get_adr@LIBBURN4 1.5.4
+ burn_drive_get_all_profiles@LIBBURN4 1.5.4
+ burn_drive_get_bd_r_pow@LIBBURN4 1.5.4
+ burn_drive_get_best_speed@LIBBURN4 1.5.4
+ burn_drive_get_disc@LIBBURN4 1.5.4
+ burn_drive_get_drive_role@LIBBURN4 1.5.4
+ burn_drive_get_feature@LIBBURN4 1.5.4
+ burn_drive_get_feature_codes@LIBBURN4 1.5.4
+ burn_drive_get_immed@LIBBURN4 1.5.4
+ burn_drive_get_media_sno@LIBBURN4 1.5.4
+ burn_drive_get_min_write_speed@LIBBURN4 1.5.4
+ burn_drive_get_read_speed@LIBBURN4 1.5.4
+ burn_drive_get_serial_no@LIBBURN4 1.5.4
+ burn_drive_get_speedlist@LIBBURN4 1.5.4
+ burn_drive_get_start_end_lba@LIBBURN4 1.5.4
+ burn_drive_get_status@LIBBURN4 1.5.4
+ burn_drive_get_write_speed@LIBBURN4 1.5.4
+ burn_drive_grab@LIBBURN4 1.5.4
+ burn_drive_info_forget@LIBBURN4 1.5.4
+ burn_drive_info_free@LIBBURN4 1.5.4
+ burn_drive_is_enumerable_adr@LIBBURN4 1.5.4
+ burn_drive_leave_locked@LIBBURN4 1.5.4
+ burn_drive_obtain_scsi_adr@LIBBURN4 1.5.4
+ burn_drive_probe_cd_write_modes@LIBBURN4 1.5.4
+ burn_drive_re_assess@LIBBURN4 1.5.4
+ burn_drive_release@LIBBURN4 1.5.4
+ burn_drive_reset_simulate@LIBBURN4 1.5.4
+ burn_drive_scan@LIBBURN4 1.5.4
+ burn_drive_scan_and_grab@LIBBURN4 1.5.4
+ burn_drive_set_buffer_waiting@LIBBURN4 1.5.4
+ burn_drive_set_immed@LIBBURN4 1.5.4
+ burn_drive_set_speed@LIBBURN4 1.5.4
+ burn_drive_set_speed_exact@LIBBURN4 1.5.4
+ burn_drive_set_stream_recording@LIBBURN4 1.5.4
+ burn_drive_snooze@LIBBURN4 1.5.4
+ burn_drive_was_feat21_failure@LIBBURN4 1.5.4
+ burn_drive_wrote_well@LIBBURN4 1.5.4
+ burn_fd_source_new@LIBBURN4 1.5.4
+ burn_fifo_fill@LIBBURN4 1.5.4
+ burn_fifo_get_statistics@LIBBURN4 1.5.4
+ burn_fifo_inquire_status@LIBBURN4 1.5.4
+ burn_fifo_next_interval@LIBBURN4 1.5.4
+ burn_fifo_peek_data@LIBBURN4 1.5.4
+ burn_fifo_source_new@LIBBURN4 1.5.4
+ burn_file_source_new@LIBBURN4 1.5.4
+ burn_finish@LIBBURN4 1.5.4
+ 

Bug#1014400: libisofs: Add symbol file

[Alexandre Ghiti]

Package: libisofs
Version: 1.5.4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

The attached patch adds a symbol file for the libisofs library.

Thanks for considering the patch.


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

Kernel: Linux 5.15.0-30-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libisofs-1.5.4/debian/libisofs6.symbols 
libisofs-1.5.4/debian/libisofs6.symbols
--- libisofs-1.5.4/debian/libisofs6.symbols 1970-01-01 01:00:00.0 
+0100
+++ libisofs-1.5.4/debian/libisofs6.symbols 2022-06-22 11:54:43.0 
+0200
@@ -0,0 +1,379 @@
+libisofs.so.6 libisofs6 #MINVER#
+ LIBISOFS6@LIBISOFS6 1.5.4
+ aaip_xinfo_cloner@LIBISOFS6 1.5.4
+ aaip_xinfo_func@LIBISOFS6 1.5.4
+ el_torito_get_boot_media_type@LIBISOFS6 1.5.4
+ el_torito_get_boot_platform_id@LIBISOFS6 1.5.4
+ el_torito_get_bootable@LIBISOFS6 1.5.4
+ el_torito_get_full_load@LIBISOFS6 1.5.4
+ el_torito_get_id_string@LIBISOFS6 1.5.4
+ el_torito_get_isolinux_options@LIBISOFS6 1.5.4
+ el_torito_get_load_seg@LIBISOFS6 1.5.4
+ el_torito_get_load_size@LIBISOFS6 1.5.4
+ el_torito_get_selection_crit@LIBISOFS6 1.5.4
+ el_torito_patch_isolinux_image@LIBISOFS6 1.5.4
+ el_torito_seems_boot_info_table@LIBISOFS6 1.5.4
+ el_torito_set_boot_platform_id@LIBISOFS6 1.5.4
+ el_torito_set_full_load@LIBISOFS6 1.5.4
+ el_torito_set_id_string@LIBISOFS6 1.5.4
+ el_torito_set_isolinux_options@LIBISOFS6 1.5.4
+ el_torito_set_load_seg@LIBISOFS6 1.5.4
+ el_torito_set_load_size@LIBISOFS6 1.5.4
+ el_torito_set_no_bootable@LIBISOFS6 1.5.4
+ el_torito_set_selection_crit@LIBISOFS6 1.5.4
+ iso_conv_name_chars@LIBISOFS6 1.5.4
+ iso_crc32_gpt@LIBISOFS6 1.5.4
+ iso_data_source_new_from_file@LIBISOFS6 1.5.4
+ iso_data_source_ref@LIBISOFS6 1.5.4
+ iso_data_source_unref@LIBISOFS6 1.5.4
+ iso_dir_add_node@LIBISOFS6 1.5.4
+ iso_dir_find_children@LIBISOFS6 1.5.4
+ iso_dir_get_children@LIBISOFS6 1.5.4
+ iso_dir_get_children_count@LIBISOFS6 1.5.4
+ iso_dir_get_node@LIBISOFS6 1.5.4
+ iso_dir_iter_free@LIBISOFS6 1.5.4
+ iso_dir_iter_has_next@LIBISOFS6 1.5.4
+ iso_dir_iter_next@LIBISOFS6 1.5.4
+ iso_dir_iter_remove@LIBISOFS6 1.5.4
+ iso_dir_iter_take@LIBISOFS6 1.5.4
+ iso_error_get_code@LIBISOFS6 1.5.4
+ iso_error_get_priority@LIBISOFS6 1.5.4
+ iso_error_get_severity@LIBISOFS6 1.5.4
+ iso_error_to_msg@LIBISOFS6 1.5.4
+ iso_file_add_external_filter@LIBISOFS6 1.5.4
+ iso_file_add_gzip_filter@LIBISOFS6 1.5.4
+ iso_file_add_zisofs_filter@LIBISOFS6 1.5.4
+ iso_file_get_md5@LIBISOFS6 1.5.4
+ iso_file_get_old_image_lba@LIBISOFS6 1.5.4
+ iso_file_get_old_image_sections@LIBISOFS6 1.5.4
+ iso_file_get_size@LIBISOFS6 1.5.4
+ iso_file_get_sort_weight@LIBISOFS6 1.5.4
+ iso_file_get_stream@LIBISOFS6 1.5.4
+ iso_file_make_md5@LIBISOFS6 1.5.4
+ iso_file_remove_filter@LIBISOFS6 1.5.4
+ iso_file_source_access@LIBISOFS6 1.5.4
+ iso_file_source_close@LIBISOFS6 1.5.4
+ iso_file_source_get_aa_string@LIBISOFS6 1.5.4
+ iso_file_source_get_filesystem@LIBISOFS6 1.5.4
+ iso_file_source_get_name@LIBISOFS6 1.5.4
+ iso_file_source_get_path@LIBISOFS6 1.5.4
+ iso_file_source_lseek@LIBISOFS6 1.5.4
+ iso_file_source_lstat@LIBISOFS6 1.5.4
+ iso_file_source_open@LIBISOFS6 1.5.4
+ iso_file_source_read@LIBISOFS6 1.5.4
+ iso_file_source_readdir@LIBISOFS6 1.5.4
+ iso_file_source_readlink@LIBISOFS6 1.5.4
+ iso_file_source_ref@LIBISOFS6 1.5.4
+ iso_file_source_stat@LIBISOFS6 1.5.4
+ iso_file_source_unref@LIBISOFS6 1.5.4
+ iso_filesystem_ref@LIBISOFS6 1.5.4
+ iso_filesystem_unref@LIBISOFS6 1.5.4
+ iso_finish@LIBISOFS6 1.5.4
+ iso_fs_global_id@LIBISOFS6 1.5.4
+ iso_generate_gpt_guid@LIBISOFS6 1.5.4
+ iso_get_local_charset@LIBISOFS6 1.5.4
+ iso_get_messenger@LIBISOFS6 1.5.4
+ iso_gzip_get_refcounts@LIBISOFS6 1.5.4
+ iso_hfsplus_xinfo_func@LIBISOFS6 1.5.4
+ iso_hfsplus_xinfo_new@LIBISOFS6 1.5.4
+ iso_image_add_boot_image@LIBISOFS6 1.5.4
+ iso_image_add_mips_boot_file@LIBISOFS6 1.5.4
+ iso_image_add_new_dir@LIBISOFS6 1.5.4
+ iso_image_add_new_file@LIBISOFS6 1.5.4
+ iso_image_add_new_special@LIBISOFS6 1.5.4
+ iso_image_add_new_symlink@LIBISOFS6 1.5.4
+ iso_image_attach_data@LIBISOFS6 1.5.4
+ iso_image_create_burn_source@LIBISOFS6 1.5.4
+ iso_image_dir_get_node@LIBISOFS6 1.5.4
+ iso_image_filesystem_new@LIBISOFS6 1.5.4
+ iso_image_fs_get_abstract_file_id@LIBISOFS6 1.5.4
+ iso_image_fs_get_application_id@LIBISOFS6 1.5.4
+ iso_image_fs_get_biblio_file_id@LIBISOFS6 1.5.4
+ iso_image_fs_get_copyright_file_id@LIBISOFS6 1.5.4
+ iso_image_fs_get_data_preparer_id@LIBISOFS6