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

[Franco E. Lazos - SiTSA Telecomunicaciones]

Hi Julien,

I think I found some data inconsistencies when migrating the mirror (the 
/debian/ directory) from the old server to the new one.

I will immediately proceed to recreate it completely. I will confirm the 
operability of this mirror soon.

Please excuse the inconvenience caused.

Regards,

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

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



> El 30 sep. 2022, a las 09:04, Julien Cristau  escribió:
> 
> Hi Franco,
> 
> http://mirror.sitsa.com.ar/debian/project/trace/mirror.sitsa.com.ar is
> dated July 20.  ftpsync should be updating it after each successful
> sync.
> 
> Cheers,
> Julien
> 
> On Fri, Sep 30, 2022 at 08:40:46AM -0300, Franco E. Lazos - SiTSA 
> Telecomunicaciones wrote:
>> Hi Julien and team,
>> 
>> Our replica server is working properly and is up to date.
>> The only thing that was done (perhaps approximately 2 months ago) was to
>> migrate it to a machine with greater processing and storage capacity.
>> 
>> Feel free to request any modification that you think is convenient.
>> 
>> Best regards,
>> 
>> P.S: the migration was quick in terms of availability because no changes were
>> made to production until all the installation processes for the new machine
>> were complete.
>> 
>> Franco E. Lazos
>> Departamento Técnico
>> SiTSA – Telecomunicaciones
>> Entre Rios 1435 – (X5900AGI) – Villa María – CBA-ARG
>> Fijo (54 353) 453-1146 | INT 107
>> Móvil (54 351) 248-2514
>> e-Mail franco.la...@sitsa.com.ar
>> Website www.sitsa.com.ar / www.trackmaster.com.ar
>> 
>> P Proteja el medio ambiente, no imprima este mail sino es necesario.
>> 
>> 
>> 
>> ATTORNEY - CLIENT PRIVILEGED INFORMATION
>> 
>> Este mensaje es privado y confidencial, y está dirigido exclusivamente  a 
>> su(s)
>> destinatario(s). Si usted ha recibido este mensaje por error,  debe 
>> abstenerse
>> de distribuirlo, copiarlo o usarlo en cualquier sentido. 
>> Asimismo, le agradecemos comunicarlo al remitente y borrar el mensaje y
>> cualquier documento adjunto
>> 
>> This email and any files transmitted with it are confidential and  intended
>> solely for the use of the individual or entity to whom they are  addressed.
>> Please notify the sender immediately by e-mail if you have received this 
>> e-mail
>> by mistake and delete this e-mail from your system.
>> 
>> 
>> 
>> 
>>El 30 sep. 2022, a las 07:13, Julien Cristau 
>>escribió:
>> 
>>Package: mirrors
>>Severity: normal
>>X-Debbugs-Cc: NOC SiTSA Telecomunicaciones 
>>User: mirr...@packages.debian.org
>>Usertags: mirror-problem
>> 
>>Hi,
>> 
>>Our monitoring shows[1] mirror.sitsa.com.ar/debian is 2 months out of
>>date.  Can you please let us know what's going on?
>> 
>>[1]: https://mirror-master.debian.org/status/mirror-info/
>>mirror.sitsa.com.ar.html
>> 
>>Thanks,
>>Julien - Debian mirrors team
>> 
>> 

Bug#1021097: reniced crashes when processing processes list from 'ps'

[Piotr H. Dabrowski]

Package: reniced
Version: 1.21-1
Severity: grave

reniced 1.21 expects processes list received from 'ps' command to have PID
of certain length.
With longer PIDs in the operating system, reniced crashes when processing
the list:

Argument " " isn't numeric in addition (+) at /usr/bin/reniced line 435,
 line 1.

This issue is FIXED UPSTREAM in reniced 1.22 (released 17 Jun 2020):
https://github.com/mmitch/reniced/releases/tag/v1.22
Please upgrade the package to the latest version (currently 1.23)

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

[Josenilson Ferreira da Silva]

Package: wnpp
Severity: wishlist
Owner: Josenilson Ferreira da Silva 
X-Debbugs-Cc: debian-de...@lists.debian.org, nilsonfsi...@hotmail.com

* Package name: spaghetti
  Version : 1.6.6
  Upstream Author : PySAL-spaghetti Developers
* URL : https://github.com/pysal/spaghetti
* License : BSD-3-Clause
  Programming Lang: Python
  Description : Analysis of Network-constrained Spatial Data


 Originating from the networkmodule in PySAL, the package provides specialized
 networking functionality that easily integrates with the rest of PySAL.
 .
 This allows users of the spaghetti network functionality the possibility of
 spatial analysis that complements the network analysis, such as spatial tools
 and integration with the main components of libpysal:
 - libpysal.weights (mentioned above)
 - lib accesspysal.cg (geometric computation and data structures)
 - libpysal .io(input-output)
 - libpysal.examples(integrated example data)
 .
 Note: 
 Module needed for packaging: https://github.com/pysal/spot

Bug#1021095: ueberzug doesn't work with terminals inside tabbed

[Edgar Yllescas]

Package: ueberzug
Version: 18.1.9-3
Severity: normal
Tags: patch

Just as the subject says, ueberzug doesn't work when a terminal is ran inside
of
suckless tabbed, a patch has existed since 2019 but it was never merged to
upstream, now that seebye locked the repo for pull requests that is even less
likely, anyway here is the most recent version of the patch confirmed to work
with the current release of ueberzug.

this patch was taken from https://github.com/gokberkgunes/ueberzug-tabbed



>From 6aafc5e2d12d23996e4c20f7f45ef12ce784c087 Mon Sep 17 00:00:00 2001
From: Gokberk Gunes 
Date: Wed, 2 Mar 2022 22:28:47 +0300
Subject: [PATCH] ueberzug now looks for window's pid and ID directly

---
 ueberzug/xutil.py | 5 +
 1 file changed, 5 insertions(+)

diff --git a/ueberzug/xutil.py b/ueberzug/xutil.py
index 19dc7c0..cd96e8e 100644
--- a/ueberzug/xutil.py
+++ b/ueberzug/xutil.py
@@ -1,6 +1,7 @@
 """This module contains x11 utils"""
 import functools
 import asyncio
+import os

 import ueberzug.tmux_util as tmux_util
 import ueberzug.terminal as terminal
@@ -126,6 +127,10 @@ def get_parent_window_infos():

 if client_pids:
 pid_window_id_map = get_pid_window_id_map()
+# Insert current window's PID & WID to the end of map to support
tabbed.
+# NOTE: Terminal (current window) must have WINDOWID as env. variable.
+if (os.environ.get('WINDOWID') != None):
+pid_window_id_map[os.getpid()] = int(os.environ.get('WINDOWID'))

 for pid in client_pids:
 ppids = get_parent_pids(pid)


-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ueberzug depends on:
ii  libc6   2.34-3
ii  libx11-62:1.8.1-2
ii  libxext62:1.3.4-1
ii  python3 3.10.5-3
ii  python3-attr21.2.0-1
ii  python3-docopt  0.6.2-4
ii  python3-pil 9.2.0-1+b1
ii  python3-xlib0.29-1

ueberzug recommends no packages.

ueberzug suggests no packages.

-- no debconf information

Bug#834724:

[john gobon]

Sent from Yahoo Mail on Android

Bug#1020971: usrmerge: Fails to install on Windows Subsystem for Linux (WSL) 1.0

[Sean Whalen]

On Oct 1, 2022, 3:34 PM, Luca Boccassi < bl...@debian.org> wrote:
> The Debian WSL maintainer uploaded a new version to the store, which is 
> merged-usr, so the issue will no longer happen for new installations.

I'm happy to confirm that this worked with a new install of the Debian 
application from the Microsoft Store under WSL 1.

I've also done some testing with WSL 2, and it turns out that unlike the last 
time I tried several years ago, Oracle VirtualBox and VMware Workstation/Player 
work fine as-is when the Windows Virtualization Platform is enabled for WSL 2.

So, the only scenario where WSL 1 must be used instead of WSL 2 is when the 
system doesn't support \[nested\] virtualization, such as virtual desktops, 
like AWS Workspaces or Citrix.


signature.asc
Description: OpenPGP digital signature

Bug#1020901: FTBFSes now

[Adam Borowski]

Control: severity -1 serious

This causes a FTBFS now, thanks to the testsuite.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ “Exegi monumentum aere perennius” -- “I made a monument more
⢿⡄⠘⠷⠚⠋⠀ durable than bronze”.
⠈⠳⣄   -- Horace (65-8 BC), leaving the loo, constipated

Bug#1021094: dnprogs: obsolete? time to remove?

[Chris Hofstaedtler]

Source: dnprogs

A while ago, it was suggested to remove the decnet kernel support,
here: 
https://lore.kernel.org/lkml/20220731190646.97039-1-step...@networkplumber.org/

No negative feedback was received, so maybe this will happen. When
it happens, dnprogs will be unusable in (stock) Debian.
(dnprogs upstream also appears abandonded.)

I would suggest removing dnprogs, if not for bookworm then in the
trixie cycle.

Chris

Bug#1021062: libc6: nonexistent locale crashes programs (for example, bash, gdb, ...)

[Kan-Ru Chen]

reassign 1021062 libreadline8
found 1021062 libreadline8/8.2-1
thanks

On Sun, Oct 2, 2022, at 1:56 AM, Aurelien Jarno wrote:
> control: reassign -1 bash
> control: found -1 bash/5.2-1
>
> Hi,
>
> On 2022-10-01 21:01, Kan-Ru Chen wrote:
>> Package: libc6
>> Version: 2.35-1
>> Severity: grave
>> Justification: renders package unusable
>> X-Debbugs-Cc: kos...@debian.org
>> 
>> Dear maintainer,
>> 
>> After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent 
>> locale setting
>> starts to crash the system.
>> 
>> This is dangerous because a remote system might not always have the same 
>> locale installed.
>> An auto update will soft-brick the system unless the sysadmin knows to set 
>> their LC_ALL=POSIX
>> before attempting to ssh.
>> 
>> Steps to reproduce:
>> 
>> >From a clean installed Debian sid, upgrade to libc6 2.35-1.
>> Only install C locale and en_US.UTF-8.
>> 
>> $ LC_ALL=ja_JP.UTF-8 bash
>> bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
>> Segmentation fault (core dumped)
>> 
>> $ LC_ALL=ja_JP.UTF-8 gdb bash
>> 
>> Fatal signal: Segmentation fault
>> - Backtrace -
>> 0x55ed3e1e8dcf ???
>> 0x55ed3e2df312 ???
>> 0x55ed3e2df488 ???
>> 0x7f0b4a39ba9f ???
>> 0x7f0b4b412204 _rl_init_locale
>> 0x7f0b4b4122f1 _rl_init_eightbit
>> 0x7f0b4b3f10f2 rl_initialize
>> ... snip ...
>
> FYI, this is the full backtrace with the debug packages installed:
>
> #0  0x7f8079d0ccc7 in __GI_kill () at 
> ../sysdeps/unix/syscall-template.S:120
> #1  0x559be26519c9 in termsig_handler (sig=11) at .././sig.c:625
> #2  0x559be2651c21 in termsig_handler (sig=) at 
> .././sig.c:492
> #3  termsig_sighandler (sig=) at .././sig.c:547
> #4  
> #5  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
> #6  0x559be26b8682 in _rl_init_locale () at 
> ../../.././lib/readline/nls.c:150
> #7  0x559be26b8772 in _rl_init_eightbit () at 
> ../../.././lib/readline/nls.c:227
> #8  0x559be269766e in readline_initialize_everything () at 
> ../../.././lib/readline/readline.c:1292
> #9  rl_initialize () at ../../.././lib/readline/readline.c:1183
> #10 0x559be2662b05 in initialize_readline () at .././bashline.c:522
> #11 0x559be26040a5 in yy_readline_get () at 
> /usr/local/src/chet/src/bash/src/parse.y:1514
> #12 0x559be2606aa1 in yy_getc () at 
> /usr/local/src/chet/src/bash/src/parse.y:1462
> #13 shell_getc (remove_quoted_newline=remove_quoted_newline@entry=1) at 
> /usr/local/src/chet/src/bash/src/parse.y:2393
> #14 0x559be2608eeb in read_token (command=0) at 
> /usr/local/src/chet/src/bash/src/parse.y:3400
> #15 0x559be260d05b in yylex () at 
> /usr/local/src/chet/src/bash/src/parse.y:2890
> #16 yyparse () at ./build-bash/y.tab.c:1854
> #17 0x559be2603586 in parse_command () at .././eval.c:348
> #18 0x559be2603714 in read_command () at .././eval.c:392
> #19 0x559be26038c6 in reader_loop () at .././eval.c:139
> #20 0x559be26023b5 in main (argc=1, argv=0x7ffe3da22078, 
> env=0x7ffe3da22088) at .././shell.c:833
>
> So the problem is that _rl_init_locale (from bash) calls strlen(NULL).
>
>> Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
>> state was invalidated when upgrading.
>
> This is because you upgraded other packages than glibc (here bash), and the 
> bug
> is not in glibc. Downgrading bash fixes the issue. Reassigning the bug.

Thanks!

That explains why not all programs crash like this. The common library they 
used is
libreadline and I confirmed downgrade libreadline8 to 8.2~rc2-2 fixed the issue.
Reassigning to libreadline8.

-- 
Kan-Ru Chen
Debian Developer

Bug#1021093: transition: ros2-rcutils

[Timo Röhling]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

I'd like to transition ros2-rcutils after a SONAME bump.
I could rebuild all reverse dependencies on amd64 successfully.

The Ben tracker at
https://release.debian.org/transitions/html/auto-ros2-rcutils.html
looks mostly fine, even though I would have expected ros-ros-comm in
dependency level 2.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmM4v40ACgkQ+C8H+466
LVlD2Qv/dVq3i6htTlnsWKjM3fmiAhGvQG2SE2u3tIU7Yajo3BTGBeiRNBto5QCm
yup2Z33g1VEGsOGNiwUwuxAhop8zsTQUwrgcqh8A8ZIHvSnKs2laTWe/V2JQzmwU
ehaDC2d8mI1lnK6oA68dU8kwYgxFfelTh4long3qS+SqnaTaRf7f/ACn+C+Vm0jk
gVQNLu3RFhAWD4SZ5ReU+UO0EeHbi/aAOsVlZhmhxQ5c/Qxa1EDxHRx4+rk7/jen
TeTI3yZ9qGrCygM7ivbxBQ7fGWFB3nEehgLcabsA0ywtugQ1T9Wcz8g3iEeBHPbi
UF4nA344L22rx6taWUi2on86a/BgZ2sNwuFNC++o4LM7y9kE1mx8vMz2tdQPMbpb
jSNPuW0F1RYCV0HRSaNXrKXZ9eD4ZAHc8m2bLqKIvRzkp1I90YOJDzJczKrWhASh
pjepRKgkEbE56qeGoDq1RO5K3+pt1O6/G5sdEBL6JLbIJ67lowkDUVMqmasbdUZ6
hYyn2Ow/
=BT9t
-END PGP SIGNATURE-

Bug#1021092: transition: libgit2

[Timo Röhling]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

I'd like to transition libgit2 after a SONAME bump.
I've rebuilt most of the reverse dependencies successfully, some
dependencies need special attention though:

python3-pygit2 needs to be updated to be compatible with libgit2 1.5;
as I am the maintainer I got this covered.

ruby-rugged also needs to be updated; I have filed bug #1020632 for
this.

The Rust toolchain looks a bit weird in the Ben tracker at
https://release.debian.org/transitions/html/auto-libgit2.html
and I've had some issues rebuilding stuff following the dependency
levels.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmM4vdoACgkQ+C8H+466
LVkwkwwA732Uf+Y/RX8Haou/QRcSA8kLFnKYANuoPATslY4ak5qbwC6b7JWTpaoj
6KB1oyHsWtOp4+52AHA3AQwEh+Ri5xZ2EkwMkxPgcGaV94YSaOfmFjt8TptXrUX9
WxPFkDAZGkvbKQL7ywzUAlDfQ0jOnEwOXDRL1gEmMtxWh29rBSmdPLYoYgUhQ3aC
Bbjh7fvXMfy1UY04aLdo8oVxkU8SnsRkj/bRygIBI3lAuf+Dr8k2QsKkyREEhmYg
nIlMVezZHXtkjqylxTfjKnE9Jl1aTCZhVn9neVqVz+5rNckiZWOxEwXxbPw4+IYa
mcvUhE4iuNpDZnCHOMYMtW6jJwI9T0vC1j2NIOC0a56OLzhI8U431dd+uA/nNQZk
/ib3y2Inx8c7SRlTJLd26RItEAOwmE5+y0hLXwZQvS4WgTQ0AwWy4nam0kngtZ7x
0C93cO6sqGzDye7I4LldTwLohQcc6AxlKq/EEmfuE/gtWuSBzBh4EJPdsoPHjGKB
XLN1qQj5
=lLrw
-END PGP SIGNATURE-

Bug#1020943: (no subject)

[Aurelien Jarno]

On 2022-10-01 22:36, Szilfai Balázs wrote:
> Core dump attached.

Thanks, could you please attach the following file instead of the text
output?

/var/lib/systemd/coredump/core.nscd.0.e89b6fce3d004f04b16f3e5a8f439a82.2560572.166465611000.zst

Regards
Aurelien

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

Bug#1020793: gmap: FTBFS on avx512 host in buster

[Étienne Mollier]

Hi Andreas,

Andreas Beckmann, on 2022-09-26:
> BTW, the package content should not depend on the build host cpu.
> The sid package currently has avx2 binaries, if I rebuild it it gets
> avx512 binaries, who knows what happens after a binNMU? This can easily
> lead to significant performance regressions for some users.
> 
> As there seems to be some kind of runtime cpu detection, perhaps a
> bigger list of cpu targets could be built and shipped (even targets
> not supported by the buildd cpu). For correctness validation,
> a separate package containing the tests (if any) could be provided...

Focusing on the sid distribution, configure options allow for
disabling simd entirely, enabling them depending on the build
machine, and enforcing a certain baseline with.  This is done by
playing with options --disable-simd, --enable-simd, and
--with-simd-level= (which takes said level as argument)
respectively.

Looking at gmap source code, there is support up to avx512bw
intrinsics, but for some reason the build fails when the
underlying CPU of the build machine does not support the host
target.  I don't have access to an avx512 capable host right
now, but I can reproduce the build failure with avx2 instead: it
builds fine on my machine, but when I attempt a build on a
generic virtual machine, the same build fails with similar
symptoms:

gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2   
-DTARGET=\"x86_64-pc-linux-gnu\" -DGMAPDB=\"/var/cache/gmap\" -mpopcnt 
-DHAVE_SSE2=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -DHAVE_SSE4_2=1 -DHAVE_AVX2=1  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o gmap_avx2-compress.o `test -f 'compress.c' || 
echo './'`compress.c
In file included from compress.c:41:
/usr/lib/gcc/x86_64-linux-gnu/12/include/tmmintrin.h: In function 
‘Compress_shift’:
/usr/lib/gcc/x86_64-linux-gnu/12/include/tmmintrin.h:185:1: error: 
inlining failed in call to ‘always_inline’ ‘_mm_alignr_epi8’: target specific 
option mismatch
  185 | _mm_alignr_epi8(__m128i __X, __m128i __Y, const int __N)
  | ^~~
compress.c:1261:22: note: called from here
 1261 |   leftpart = _mm_alignr_epi8(current,prev,12);
  |  ^~~~
/usr/lib/gcc/x86_64-linux-gnu/12/include/tmmintrin.h:185:1: error: 
inlining failed in call to ‘always_inline’ ‘_mm_alignr_epi8’: target specific 
option mismatch
  185 | _mm_alignr_epi8(__m128i __X, __m128i __Y, const int __N)
  | ^~~
compress.c:1266:23: note: called from here
 1266 |   rightpart = _mm_alignr_epi8(current,prev,12);
  |   ^~~~
/usr/lib/gcc/x86_64-linux-gnu/12/include/tmmintrin.h:185:1: error: 
inlining failed in call to ‘always_inline’ ‘_mm_alignr_epi8’: target specific 
option mismatch
  185 | _mm_alignr_epi8(__m128i __X, __m128i __Y, const int __N)
  | ^~~
compress.c:1265:22: note: called from here
 1265 |   leftpart = _mm_alignr_epi8(current,prev,8);
  |  ^~~
/usr/lib/gcc/x86_64-linux-gnu/12/include/tmmintrin.h:185:1: error: 
inlining failed in call to ‘always_inline’ ‘_mm_alignr_epi8’: target specific 
option mismatch
  185 | _mm_alignr_epi8(__m128i __X, __m128i __Y, const int __N)
  | ^~~
compress.c:1270:23: note: called from here
 1270 |   rightpart = _mm_alignr_epi8(current,prev,8);
  |   ^~~
/usr/lib/gcc/x86_64-linux-gnu/12/include/tmmintrin.h:185:1: error: 
inlining failed in call to ‘always_inline’ ‘_mm_alignr_epi8’: target specific 
option mismatch
  185 | _mm_alignr_epi8(__m128i __X, __m128i __Y, const int __N)
  | ^~~
compress.c:1269:22: note: called from here
 1269 |   leftpart = _mm_alignr_epi8(current,prev,4);
  |  ^~~
/usr/lib/gcc/x86_64-linux-gnu/12/include/tmmintrin.h:185:1: error: 
inlining failed in call to ‘always_inline’ ‘_mm_alignr_epi8’: target specific 
option mismatch
  185 | _mm_alignr_epi8(__m128i __X, __m128i __Y, const int __N)
  | ^~~
compress.c:1274:23: note: called from here
 1274 |   rightpart = _mm_alignr_epi8(current,prev,4);
  |   ^~~

Otherwise when running autopkgtest of build artifacts from my
host to the generic processor, there seems to be all the
branching needed for avoiding illegal instruction errors indeed,
so it is a shame not taking advantage of this.

Correct option would be to fix the build error without impeding
the runtime for 

Bug#1019982: exo-utils missing exo-csource

[Akbarkhon Variskhanov]

Control: severity -1 normal

Hello, Eric.

exo-csource was dropped upstream[1]. However, the package description
wasn't updated. Thanks for catching that and reporting.

[1] 
https://gitlab.xfce.org/xfce/exo/-/commit/b8533ad84da0d10ebb9674cad54195a2b1ab59c2

Regards,
Akbar.

Bug#1021091: dpkg: po: Update Swedish translation (main branch)

[Peter Krefting]

Package: dpkg
Severity: wishlist
Tags: l10n patch

Please find updated Swedish translation for the main branch (as of 
2022-10-01 23:25 CEST) here:


- git fetch https://github.com/nafmo/dpkg-l10n-sv.git main
- https://github.com/nafmo/dpkg-l10n-sv/tree/main

Direct download links:

- man/po/sv.po:
  https://github.com/nafmo/dpkg-l10n-sv/raw/main/man/po/sv.po
- dselect/po/sv.po: (not changed)
  https://github.com/nafmo/dpkg-l10n-sv/raw/main/dselect/po/sv.po
- scripts/po/sv.po:
  https://github.com/nafmo/dpkg-l10n-sv/raw/main/scripts/po/sv.po
- po/sv.po:
  https://github.com/nafmo/dpkg-l10n-sv/raw/main/po/sv.po

with the commit message:

  po: Update Swedish translation

  po/sv.po: 1177t0f0u.
  man/po/sv.po: 3251t0f0u.
  scripts/po/sv.po: 629t0f0u.

--
\\// Peter - http://www.softwolves.pp.se/

Bug#1009812: xfce4-panel-profiles: Missing functionality. Save/export not possible.

[Akbarkhon Variskhanov]

Control: severity -1 normal

Hi, Mark. Could you please provide more information? What happens if
you start it from the shell? Anything in ~/.xsession-errors?

Thanks.

Bug#1021043: linphone-desktop: linphone crashes and is unusable

[Dennis Filder]

Control: reassign -1 linphone 5.0.37-5
Control: retitle -1 linphone: std::logic_error in 
src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged()
X-Debbugs-Cc: Daniel Kahn Gillmor 

On Sat, Oct 01, 2022 at 03:15:10PM -0400, Daniel Kahn Gillmor wrote:

> However, after restoring my configuration, and trying to place a single
> call (to myself, which of course i didn't expect to work) the app
> crashed again.
>
> now, even with libsoci* from bullseye, it is crashing again at startup,
> with this stderr log and backtrace:
>
> ...
> #9  0x77868d34 in 
> LinphonePrivate::Account::notifyPublishStateChanged(_LinphonePublishState) () 
> at /lib/x86_64-linux-gnu/liblinphone.so.10
> ...

Yeah, this is a different issue.  Upstream commit
a6ca93ec62b66dfcc0fe41783beeab4a471c95dc looks like it fixed this.
I'll look into preparing an update.  That should then also take care
of the soci breakage.

Regards.

Bug#895636: meson: more tools missing from debcrossgen

[Helmut Grohne]

Control: affects -1 - src:systemd

Hi Michael,

On Sat, Oct 01, 2022 at 09:53:46PM +0200, Michael Biebl wrote:
> this issue still shows up on the systemd bug tracker.
> Is it still valid and still something that only affects src:systemd so would
> warrant the affects

debcrossgen now includes ld and objcopy (which this bug explicitly asked
not to add and rather fix it via a tool prefix). As such, systemd cross
builds just fine now. While it no longer affects systemd, the issue
remains.

Helmut

Bug#1020943: (no subject)

[Szilfai Balázs]

Core dump attached.

--
Balazs Szilfai
   PID: 2560572 (nscd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 6 (ABRT)
 Timestamp: Sat 2022-10-01 22:28:30 CEST (4min 28s ago)
  Command Line: /usr/sbin/nscd
Executable: /usr/sbin/nscd
 Control Group: /system.slice/nscd.service
  Unit: nscd.service
 Slice: system.slice
   Boot ID: e89b6fce3d004f04b16f3e5a8f439a82
Machine ID: 6281f2bd2c1c58eb7848829248106cc6
  Hostname: www
   Storage: 
/var/lib/systemd/coredump/core.nscd.0.e89b6fce3d004f04b16f3e5a8f439a82.2560572.166465611000.zst
 (present)
 Disk Size: 156.5K
   Message: Process 2560572 (nscd) of user 0 dumped core.

Module linux-vdso.so.1 with build-id 
666daae2012a328cd919217d994125e1ed871b2f
Module libtirpc.so.3 with build-id 
89d6760d8f004a33b2ad80e7277842ef8f3c4a43
Module libnsl.so.2 with build-id 
d7e4e187c5d3d36dc8386646d8d02910f2664a85
Module libnss_nis.so.2 with build-id 
da6295367de4844c0493a7d7b77d5e979ecc733b
Module libm.so.6 with build-id 
840fd8e1653b9fbc906a4af5405a6f59965d36b7
Module libnss_systemd.so.2 with build-id 
00e564b38edfa8893a50714d79de330045ff3188
Metadata for module libnss_systemd.so.2 owned by FDO found: {
"type" : "deb",
"os" : "debian",
"name" : "systemd",
"architecture" : "amd64",
"version" : "251.4-3",
"debugInfoUrl" : "https://debuginfod.debian.net;
}

Module libffi.so.8 with build-id 
bb0fa5371874ba431e7cd9dc2df93922de436fa9
Module libdl.so.2 with build-id 
0e02f550c7e69ddb870d32d0b012731abd38c6ce
Module libkeyutils.so.1 with build-id 
58715c0085b108b4060ef6c42feb8b33dbb7acb7
Module libgmp.so.10 with build-id 
25c73b398493c695a013a6d9d493a8316aac0fa0
Module libhogweed.so.6 with build-id 
568595f2db0c8a2a59fc8aeb153db78ca51d0168
Module libnettle.so.8 with build-id 
df9d509c9055db57df09603aab0fc4c66ad2837c
Module libtasn1.so.6 with build-id 
1d312752ce136a80ebceeb73404c90fbd4e4f78d
Module libunistring.so.2 with build-id 
7d2c9a24ad8e7cb72befdc06cd45cbddd5ee7f48
Module libidn2.so.0 with build-id 
ddba28970641f1f110f7585d57dc5867e2ee4ffd
Module libp11-kit.so.0 with build-id 
97832cbdb52c48f1422b9e70802112b0cc6587f3
Module libkrb5support.so.0 with build-id 
0db7b73d1aa611e567cbd11a12e0d5772297f0dd
Module libcom_err.so.2 with build-id 
fd7d5e74b171eb70aef1e490b0d39a34855d6272
Module libk5crypto.so.3 with build-id 
33306e3a67c4c2822256708bf7d56f275d769d43
Module libkrb5.so.3 with build-id 
99b080454d2a271374eea4f485e54f79e35cff92
Module libgnutls.so.30 with build-id 
333e23f509b65dbbd4c3f4c2dbbd1fe1296d358a
Module libsasl2.so.2 with build-id 
219485904088876b46f5790ecaa6d204c6aef6f3
Module libresolv.so.2 with build-id 
451d346f2df8ed37030cbe431632a955424c9562
Module libgssapi_krb5.so.2 with build-id 
f5ed686118c8d310382814da15fb570f1164a17c
Module liblber-2.5.so.0 with build-id 
d49303b94e9652136fa5c8f4ee83b7e9f4fef2a8
Module libldap-2.5.so.0 with build-id 
19951fdb1f798f0a068deddb786885cf2e2f328c
Module libnss_ldap.so.2 with build-id 
52ec90e743c29ce22cceca5927e8ed93615e7c68
Module libnss_compat.so.2 with build-id 
329cca90777665b39099add8e1f6ca7a4babf74e
Module libpthread.so.0 with build-id 
276b8e391d0c4cbf4ea22611a8c0ef078248c4dc
Module libcap-ng.so.0 with build-id 
ebf0e882db263bfb4ccf6af882585c5e52145112
Module libpcre2-8.so.0 with build-id 
5aa43e3778622f4b95261331e97a45be5b87481d
Module libc.so.6 with build-id 
e1e37d95dd7227113534a1bfeb2dfa9176f14449
Module libcap.so.2 with build-id 
a6034f7fc277ee9d9714c2b288b419498225156f
Module libaudit.so.1 with build-id 
591ea1717d114afaba5f4ea763f56a27af74357a
Module libselinux.so.1 with build-id 
827b23e6391a3374fa79e36bca36c41c8e6d29e4
Module nscd with build-id 
6393cb05a18407fd4856fd7eeccb87a8471155ab
Stack trace of thread 2560575:
#0  0x7f05dfb0457c n/a (libc.so.6 + 0x8957c)
#1  0x7f05dfab8a02 raise (libc.so.6 + 0x3da02)
#2  0x7f05dfaa3469 abort (libc.so.6 + 0x28469)
#3  0x7f05dfaa3395 n/a (libc.so.6 + 0x28395)
#4  0x7f05dfab1ab2 __assert_fail (libc.so.6 + 0x36ab2)
#5  0x5629b6c87116 n/a (nscd + 0x13116)
#6  0x5629b6c7c02e n/a (nscd + 0x802e)
#7 

Bug#1020943: (no subject)

[Szilfai Balázs]

Package: nscd
Version: 2.35-1

kern.log:
Oct  1 16:07:02 www kernel: [1041475.994914] nscd[119940]: segfault at 0 ip 
7f6427012b59 sp 7f641b54e928 error 4 in libc.so.6[7f6426ee3000+17]
Oct  1 16:07:02 www kernel: [1041475.994920] Code: fe 7f 5c 17 e1 c5 f8 77 c3 0f 1f 
84 00 00 00 00 00 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 37 
01 00 00  fd 74 0f c5 fd d7 c1 85 c0 74 5b f3 0f bc c0 c5 f8 77 c3 0f 1f

syslog:
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/passwd` (1)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/group` (3)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/hosts` (4)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/resolv.conf` (5)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/services` (6)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 disabled inotify-based monitoring for file 
`/etc/netgroup': No such file or directory
Oct  1 16:07:02 www nscd: 119933 stat failed for file `/etc/netgroup'; will try 
again later: No such file or directory
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/nsswitch.conf` (7)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/nsswitch.conf` (7)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/nsswitch.conf` (7)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/nsswitch.conf` (7)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 monitoring file `/etc/nsswitch.conf` (7)
Oct  1 16:07:02 www nscd: 119933 monitoring directory `/etc` (2)
Oct  1 16:07:02 www nscd: 119933 Access Vector Cache (AVC) started
Oct  1 16:07:02 www kernel: [1041475.994914] nscd[119940]: segfault at 0 ip 
7f6427012b59 sp 7f641b54e928 error 4 in libc.so.6[7f6426ee3000+17]
Oct  1 16:07:02 www systemd[1]: nscd.service: Main process exited, code=killed, 
status=11/SEGV
Oct  1 16:07:02 www systemd[1]: nscd.service: Failed with result 'signal'.
Oct  1 16:07:02 www systemd[1]: nscd.service: Scheduled restart job, restart 
counter is at 504.
Oct  1 16:07:02 www systemd[1]: nscd.service: Start request repeated too 
quickly.
Oct  1 16:07:02 www systemd[1]: nscd.service: Failed with result 'signal'.

Package default /etc/nscd.conf file.

--
Balazs Szilfai

Bug#1020436: giac FTBFS with PARI 2.15.0

[Bill Allombert]

On Wed, Sep 21, 2022 at 09:01:51PM +0300, Adrian Bunk wrote:
> Source: giac
> Version: 1.9.0.19+dfsg2-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/logs.php?pkg=giac=1.9.0.19%2Bdfsg2-1%2Bb1
> 
> ...
> pari.cc: At global scope:
> pari.cc:752:17: error: typedef ‘giac::PFGEN’ is initialized (use ‘decltype’ 
> instead)
>   752 |   typedef GEN (*PFGEN)(ANYARG);
>   | ^
> pari.cc:752:24: error: ‘ANYARG’ was not declared in this scope

This is my comment on this bug:

PARI used to define ANYARG as
#ifdef __cplusplus
#  define ANYARG ...
#else
#  define ANYARG
#endif

This definition was removed because newer gcc/clang do not like to call
function without prototype and it was not particularly
useful.

So you can replace this by

typedef GEN (*PFGEN)();

if you like, but recent gcc 12 will issue warning.
In PARI we changed EVAL_f to cast the pointer to the right prototype
before calling it.

Sorry for the trouble.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

[Bill Allombert]

On Wed, Sep 21, 2022 at 11:57:40PM +0300, Adrian Bunk wrote:
> Source: cypari2
> Version: 2.1.2-2
> Severity: serious
> Tags: ftbfs bookworm sid
> 
> https://buildd.debian.org/status/logs.php?pkg=cypari2=2.1.2-2%2Bb3
> 
> Differences (ndiff with -expected +actual):
>   Traceback (most recent call last):
> - ...
> - PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC 
> (1 elts)
> +   File "/usr/lib/python3.10/doctest.py", line 1350, in __run
> + exec(compile(example.source, filename, "single",
> +   File " 145)[18]>", line 1, in 
> + mul([1], [2])
> +   File "cypari2/gen.pyx", line 4107, in cypari2.gen.Gen.__call__
> + sig_on()
> +   File "cypari2/handle_error.pyx", line 213, in 
> cypari2.handle_error._pari_err_handle
> + raise PariError(errnum, pari_error_string, clone_gen_noclear(E))
> + PariError: call_python: incorrect type in qfbcomp (t_VEC)
a

Some explanation for the failure.

PARI has merged t_QFI and t_QFR to a new type t_QFB. This explains this error.
This might requires some actual fix in cpari2.

> **
> File 
> "/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/closure.cpython-310-x86_64-linux-gnu.so",
>  line ?, in cypari2.closure.objtoclosure
> Failed example:
> mul([1], [2])
> Differences (ndiff with -expected +actual):
>   Traceback (most recent call last):
> - ...
> - PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC 
> (1 elts)
> +   File "/usr/lib/python3.10/doctest.py", line 1350, in __run
> + exec(compile(example.source, filename, "single",
> +   File "", line 1, in 
> + mul([1], [2])
> +   File "cypari2/gen.pyx", line 4107, in cypari2.gen.Gen.__call__
> + sig_on()
> +   File "cypari2/handle_error.pyx", line 213, in 
> cypari2.handle_error._pari_err_handle
> + raise PariError(errnum, pari_error_string, clone_gen_noclear(E))
> + PariError: call_python: incorrect type in qfbcomp (t_VEC)

Idem

> **
> 2 items had failures:
>1 of  19 in cypari2.closure.__test__.objtoclosure (line 145)
>1 of  19 in cypari2.closure.objtoclosure
> ***Test Failed*** 2 failures.
> 
> Testing cypari2.convert
> 
> Testing cypari2.gen
> **
> File 
> "/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/gen.cpython-310-x86_64-linux-gnu.so",
>  line ?, in cypari2.gen.Gen.__complex__
> Failed example:
> complex(g)
> Differences (ndiff with -expected +actual):
> - (2.2847006554165614+0j)
> + (1.118033988749895+0j)
> **
> File 
> "/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/gen.cpython-310-x86_64-linux-gnu.so",
>  line ?, in cypari2.gen.__test__.Gen.__complex__ (line 2006)
> Failed example:
> complex(g)
> Differences (ndiff with -expected +actual):
> - (2.2847006554165614+0j)
> + (1.118033988749895+0j)
> **
> 2 items had failures:
>1 of  13 in cypari2.gen.Gen.__complex__
>1 of  13 in cypari2.gen.__test__.Gen.__complex__ (line 2006)
> ***Test Failed*** 2 failures.
> 
> Testing cypari2.handle_error
> **
> File 
> "/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/handle_error.cpython-310-x86_64-linux-gnu.so",
>  line ?, in cypari2.handle_error.__test__.PariError.__str__ (line 104)
> Failed example:
> pari('!@#$%^&*()')
> Differences (ndiff with -expected +actual):
>   Traceback (most recent call last):
> - ...
> +   File "/usr/lib/python3.10/doctest.py", line 1350, in __run
> + exec(compile(example.source, filename, "single",
> +   File " 104)[3]>", line 1, in 
> + pari('!@#$%^&*()')
> +   File "cypari2/pari_instance.pyx", line 832, in 
> cypari2.pari_instance.Pari.__call__
> + cdef Gen g = objtogen(s)
> +   File "cypari2/gen.pyx", line 4810, in cypari2.gen.objtogen
> + cdef GEN g = PyObject_AsGEN(s)
> +   File "cypari2/convert.pyx", line 557, in 
> cypari2.convert.PyObject_AsGEN
> + sig_on()
> +   File "cypari2/handle_error.pyx", line 213, in 
> cypari2.handle_error._pari_err_handle
> + raise PariError(errnum, pari_error_string, clone_gen_noclear(E))
> - PariError: syntax error, unexpected $undefined
> ? --   ^
> + PariError: syntax error, unexpected invalid token
> ?   + ^

This is actually a 

Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound

[Pedro Lopez-Cabanillas]

upstream ticket: https://sourceforge.net/p/drumstick/bugs/46/
fixed and closed in release 2.7.2

Regards,
Pedro

Bug#1021090: transition: coq-hierarchy-builder

[julien . puydt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: jpu...@debian.org
X-Debbugs-Cc: Debian OCaml Maintainers


Hi,

there is a new version of coq-hierarchy-builder ; it requires
rebuilding another package:

 nmu mathcomp-analysis_0.5.4-1+b2 . ANY . -m 'Rebuild because of upload
of coq-hierarchy-builder=1.4.0-1'
 dw mathcomp-analysis_0.5.4-1+b2 . ANY . -m 'coq-hierarchy-builder >=
1.4.0-1'


I'm waiting for your approval to upload coq-hierarchy-builder 1.4.0-1.

Cheers,

J.Puydt

Bug#1021089: RFP: qr-backup -- paper backups of files using QR codes

[Zachary Vance]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: z...@za3k.com

* Package name: qr-backup
  Version : 1.1.2
  Upstream Author : Zachary Vance 
* URL : https://github.com/za3k/qr-backup
* License : Creative Commons Zero / Public Domain
  Programming Lang: Python
  Description : paper backups of files using QR codes

qr-backup takes file(s), and outputs a "paper backup": a printable 
black-and-white pdf full of QR codes. To back up your file, print the PDF. The 
pile of paper in your hand is now a backup of the file.

If your file is lost, corrupted, deleted, etc, you can restore from your paper 
backup. qr-backup reads the QR barcodes using your computer's webcam (or 
scanner) to get your file back.

- I am the author of this package. I do use this program, and believe an easy 
install would benefit others.
- Packaging should be easy (standard makefile, no compilation), for someone 
experience with debian.
- An example package which may help (for Arch linux) is at 
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=qr-backup

Bug#895636: meson: more tools missing from debcrossgen

[Michael Biebl]

Hi Helmut,

this issue still shows up on the systemd bug tracker.
Is it still valid and still something that only affects src:systemd so 
would warrant the affects


Regards,
Michael


On Fri, 13 Apr 2018 21:17:54 +0200 Helmut Grohne  wrote:

Package: meson
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:systemd

systemd fails to cross build from source for uefi architectures (e.g.
arm64), because the generated cross file does not include all relevant
tools. In particular, systemd needs ld and objcopy, both of which are
presently missing from debcrossgen.

Rather than adding them, let me propose a more generic solution. Add a
new field to cross files. I'll call it "tool_prefix" for now, but you
can choose a better name of course. When tool_prefix is empty or not
set, meson behaves as before. When it is set however, find_program
behaves differently. When find_program is instructed to look for foo
(with native=False), it first looks whether foo is assigned in the cross
file (as before). If it isn't assigned, it searches $PATH for the
concatenation of tool_prefix and foo. If it finds something, that one is
used. In case nothing is found, it proceeds searching $PATH for simply
foo.

For Debian systems, most architecture-dependent tools carry the GNU
triplet as prefix. Thus we can assign "${DEB_HOST_GNU_TYPE}-" as the
tool_prefix and solve most of missing entries.

Please consider implementing the proposed tool_prefix rather than just
adding ld and objcopy to debcrossgen.

Helmut




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021012: marked as done (linux-image-amd64 depends on linux-image-4.19.0-22-amd64, but this package is not available)

[Bastian Blank]

On Sat, Oct 01, 2022 at 09:29:10PM +0200, Ben Hutchings wrote:
> In buster, the metapackages are still built from linux-latest.  This
> has a fake build-dependency on linux-headers--all to ensure it
> waits for linux to be built, but it doesn't have any such relation to
> linux-signed-*.

Ah, damn.  Forgot about that split.

Bastian

-- 
A Vulcan can no sooner be disloyal than he can exist without breathing.
-- Kirk, "The Menagerie", stardate 3012.4

Bug#1020943: nscd: Segmention fault when trying to launch on Debian/testing

[Aurelien Jarno]

Hi,

On 2022-09-29 09:37, Adrian Immanuel Kiess wrote:
> Package: nscd
> Version: 2.35-1
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>  Upgrading nscd on Debian/testing
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  apt -u dist-upgrade
>* What was the outcome of this action?
>  nscd segfaults when trying to launch
>* What outcome did you expect instead?
>  Working nscd
> 
> currently on Debian/testing, nscd crashes when trying to launch.

Unfortunately I am not able to reproduce this issue locally, I will
therefore need some help to diagnose the problem:

- Can you please share your /etc/nscd.conf?
- Do you have any related message available in dmesg?

> >From logwatch:
> 
>  WARNING:  Segmentation Faults in these executables
> nscd :  2461 Time(s)
> 
> Here is the journalctl output:
> 
> sept. 29 09:12:13 g6.lan.dac systemd[1]: Started Name Service Cache Daemon.
> sept. 29 09:12:15 g6.lan.dac systemd[1]: nscd.service: Main process exited,
> code=killed, status=11/SEGV

Would it be possible to share the corresponding core dump file? Sharing
it privately is also fine if you prefer.

Regards
Aurelien

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

Bug#1016047:

[Andres Salomon]

On Thu, 4 Aug 2022 08:07:09 -0500 (CDT) Timothy Pearson 
 wrote:
> The areas I'm specifically interested in helping with are the 
security updates and the ungoogled Chromium patchset -- I'm already 
maintaining the ungoogled patches on top of the ppc64el patches, and 
I'd like to get both of those in Debian proper.

>
>

Sorry, I just saw these messages (debian's bug tracking system is.. not 
great). I'd love the help. I'm fine with you working towards ppc64el 
support. Getting you set up with a https://salsa.debian.org/ account 
and added to the chromium team is probably the first step.

Bug#1020971: usrmerge: Fails to install on Windows Subsystem for Linux (WSL) 1.0

[Luca Boccassi]

On Fri, 2022-09-30 at 16:15 +0100, Luca Boccassi wrote:
> Control: forwarded -1 https://github.com/microsoft/WSL/issues/8927
> 
> On Thu, 29 Sep 2022 21:44:29 + Sean Whalen  wrote:
> > I just created a bug report in the official Microsoft WSL project
> > on
> > GitHub to track the issue there as well, and maybe get some
> > eyeballs
> > from Microsoft.
> > 
> > https://github.com/microsoft/WSL/issues/8927
> 
> I've talked with both the internal team and the Debian maintainer of
> the WSL image. This is a WSL 1.0 specific issue, and there's not much
> we can do in usrmerge about it, as it's related to the underlying
> filesystem that we can't touch anyway.
> 
> The Debian stable WSL image in the store will be updated shortly to
> be
> merged-usr out of the box, so this won't happen again for new
> installations, and on upgrade to bookworm it will be a no-op. Older
> installations on WSL 1.0 will have to remove and reinstall, unless a
> workaround is found, but for that please use the upstream bug tracker
> as here we really can't figure out what the problem is.
> 
> Also please note that it would be a good idea to just move to WSL 2.0
> for all use cases at this point.
> 
> Hence, setting the forwarded address and closing.

The Debian WSL maintainer uploaded a new version to the store, which is
merged-usr, so the issue will no longer happen for new installations.

-- 
Kind regards,
Luca Boccassi


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

Bug#1021012: marked as done (linux-image-amd64 depends on linux-image-4.19.0-22-amd64, but this package is not available)

[Ben Hutchings]

On Sat, 2022-10-01 at 12:23 +0200, Bastian Blank wrote:
> On Sat, Oct 01, 2022 at 06:45:03AM +, Debian Bug Tracking System wrote:
> > This will resolve itself automatically once the signed packages are
> > available as well (they are in progress of beeing dealt with but needs
> > a manual interaction of ftp-masters).
> 
> Looks like we need to backport the changes that moved the meta package
> into linux-signed-*.  This now also affects the build of the cloud
> images and breaks them.

In buster, the metapackages are still built from linux-latest.  This
has a fake build-dependency on linux-headers--all to ensure it
waits for linux to be built, but it doesn't have any such relation to
linux-signed-*.

I don't think I should try to move binary packages around post-release,
so probably the best approach is to wait to upload linux-latest in
future.

(This wasn't a problem with stretch LTS because we didn't do code
signing, and it wasn't a problem with buster prior to LTS because
security updates and point releases would release all related packages
at once.)

Ben

-- 
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding
stump of a severed limb. - me, 29 June 1999


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

Bug#1021043: linphone-desktop: linphone crashes and is unusable

[Daniel Kahn Gillmor]

Hi Dennis--

Thank you very much for the prompt response!

On Sat 2022-10-01 09:15:39 +0200, Dennis Filder wrote:
> It would help a lot to know the exact time when those crashes started.
> Can you try narrowing it down, e.g. by looking at the ctime of
> files/directories you created in reaction to the crashes?

unfortunately, i saw crashes several days ago when i was in the middle
of dealing with other problems and i didn't get around to doing actual
debugging until much yesterday.

Looking in my backups of ~/.local/share/linphone, it looks like
september 21 was the most recent time that linphone.db and
zrtp-secrets.db were changed.

according to my dpkg logs, i had:

2022-09-27 17:03:49 upgrade libsoci-core4.0:amd64 4.0.1-5 4.0.3-1

so maybe libsoci is the issue?

> I also saw one segfault that was not handled by __GI_abort() -- maybe
> you had one, too, so it might show up as a message in
> /var/log/message* somewhere.

i'm using journald, so /var/log/message hasn't been touched in years on
my system, but i don't see anything suspicious in the output of
"journalctl -k --since '15 days ago'" either.

> Also, do you have the impression that
> the crashes suddenly became more frequent somehow?  If so: When?  What
> is the output of?:
>
> stat /usr/share/doc/linphone-desktop/changelog.Debian.gz


0 dkg@alice:~$ stat /usr/share/doc/linphone-desktop/changelog.Debian.gz 
  File: /usr/share/doc/linphone-desktop/changelog.Debian.gz
  Size: 938 Blocks: 8  IO Block: 4096   regular file
Device: fe01h/65025dInode: 523131  Links: 1
Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (0/root)
Access: 2022-09-19 11:30:17.0 -0400
Modify: 2022-09-12 14:41:04.0 -0400
Change: 2022-09-19 11:32:11.285343797 -0400
 Birth: 2022-09-19 11:32:11.273343755 -0400
0 dkg@alice:~$ 

> My current suspicion is that soci 4.0.3-1 had an ABI break from
> upstream commit 1b1b5621f5abc40bd76a54a779455e8b9c0892ff (adding the
> private backendRef_ member changed the layouts of the classes
> soci::connection_parameters and soci::session and liblinphone.so.10
> instantiates the latter).

Yes, good call!  I've installed libsoci-core4.0 and libsoci-sqlite3-4.0
from bullseye, and i was able to start up linphone without an immediate
crash.

However, after restoring my configuration, and trying to place a single
call (to myself, which of course i didn't expect to work) the app
crashed again.

now, even with libsoci* from bullseye, it is crashing again at startup,
with this stderr log and backtrace:

[15:11:03:325][0x55d195f0][Info]"Registering shared types..."
[15:11:03:325][0x55d195f0][Info]"Registering tool types..."
[15:11:03:325][0x55d195f0][Info]"Registering shared tool types..."
[15:11:03:546][0x55d195f0][Info]"Loading main view..."
[New Thread 0x7fffb79ff640 (LWP 310193)]
[Thread 0x7fffb79ff640 (LWP 310193) exited]
[15:11:03:673][0x55d195f0][Info]"Launch async core creation."
[New Thread 0x7fffb79ff640 (LWP 310194)]
[New Thread 0x7fffb71fe640 (LWP 310195)]
[Thread 0x7fffb71fe640 (LWP 310195) exited]
[New Thread 0x7fffb71fe640 (LWP 310196)]
[Thread 0x7fffb71fe640 (LWP 310196) exited]
[15:11:04:375][0x55d195f0][Info]Core is starting  "Starting up"
[15:11:04:424][0x55d195f0][Info]Core is running  "On"
[15:11:04:424][0x55d195f0][Info]"Set `Friends` path: 
`/home/dkg/.local/share/linphone/friends.db`"
[15:11:04:436][0x55d195f0][Info]"Set `CallLogs` path: 
`/home/dkg/.local/share/linphone/call-history.db`"
[15:11:04:441][0x55d195f0][Info]Using ZrtpSecrets path :  
"/home/dkg/.local/share/linphone/zidcache"
[15:11:04:442][0x55d195f0][Info]Using UserCertificate path :  
"/home/dkg/.local/share/linphone/usr-crt/"
[15:11:04:442][0x55d195f0][Info]Using RootCa path :  
"/usr/share/linphone/rootca.pem"
[15:11:04:442][0x55d195f0][Info]"Start iterate"
[15:11:04:473][0x55d195f0][Info]Sip addresses model from Chats : 30 ms.
[15:11:04:484][0x55d195f0][Info]Sip addresses model from Calls : 10 ms.
[15:11:04:484][0x55d195f0][Info]Sip addresses model from Refs : 0 ms.
[15:11:04:484][0x55d195f0][Info]Sip addresses model from Contacts : 0 ms.
[15:11:04:484][0x55d195f0][Info]Sip addresses model initialized in: 41 ms.
[15:11:04:528][0x55d195f0][Info]"Notify event count: 0."
[15:11:04:528][0x55d195f0][Info]"CoreManager initialized"
[New Thread 0x7fffb71fe640 (LWP 310197)]
[New Thread 0x7fffb69fd640 (LWP 310198)]
[Thread 0x7fffb69fd640 (LWP 310198) exited]
[15:11:04:738][0x55d195f0][Info]"Open Linphone app."
[15:11:04:738][0x55d195f0][Info]"Creating subwindow: 
`qrc:/ui/views/App/Calls/CallsWindow.qml`."
[15:11:04:813][0x55d195f0][Info]"Subwindow status: `1`."
[15:11:04:852][0x55d195f0][Info]"Creating subwindow: 
`qrc:/ui/views/App/Settings/SettingsWindow.qml`."
[15:11:04:921][0x55d195f0][Info]"Subwindow status: `1`."
[New Thread 0x7fffb69fd640 (LWP 310199)]
[New Thread 0x7fffb5dfc640 (LWP 310200)]

Bug#1018061: pads: segfault at 3a ip

[Tim McConnell]

Hi Bernhard, 
I guess there was an upgrade that resolved the issue. I no longer see
any errors for PADS. I guess it could be called an "undocumented
feature" of the upgrade? 
Anyway this can be closed as resolved. 
Thanks! 

-- 
Tim McConnell 


On Tue, 2022-09-27 at 10:32 +0200, Bernhard Übelacker wrote:
> Hello Tim,
> I tried to have a look at those two dmesg lines and it seems
> they point to the function print_arp_asset_screen, line 115 [1],
> where parameter rec is dereferenced unconditionally.
> 
> However, if it would be possible to install systemd-coredump then
> a backtrace of those crashes should be printed to the journal.
> This would give a way better information as the two dmesg lines
> alone,
> as it would also show the functions calling print_arp_asset_screen
> and therefore leading to the crash.
> 
> The link [2] might give some more hints to collect
> more information for the maintainer.
> 
> Kind regards,
> Bernhard
> 
> 
> [1]
> https://sources.debian.org/src/pads/1.2-13/src/output/output-screen.c/#L115
>  112 print_arp_asset_screen (ArpAsset *rec)
>  113 {
>  114 /* Print to Screen */
>  115 if(rec->mac_resolved != NULL) {
>  116fprintf(stdout, "[*] Asset Found:  IP Address - %s /
> MAC Address - %s (%s)\n",
> 
> [2] https://wiki.debian.org/HowToGetABacktrace

Bug#1021085: mksh: ignored test making the build unreproducible

[Thorsten Glaser]

Hi Chris,

>  -| FAIL ../../check.t:heredoc-tmpfile-8 (ignored)
>  -| Total failed: 1 (1 ignored)

this test is unfortunately fragile. It occasionally fails depending
on system “load” (but not load average), and I haven’t found a way to
make the fragility go away. (If someone does, by all means, tell me.)

>This is because the test summary is printed in README.Debian, and if
>any of the tests are "ignored" this is recorded as well.

OK, ouch.

>To be clear, that mksh includes test info is not necessarily a bug,
>and nor is it necessarily a bug in mksh that some test is failing in
>some weird environment. But the combination of the two is
>unfortunately causing a reproducibility regression and I thought you
>may have more context.

For the test, see above.

I wanted to include the test info somewhere so we can see whether
everything passed; initially, I didn’t fail the build when there
were testsuite failures, but that was in 2008 or so. I also wanted
to be able to gather this information, but nowadays I just use
https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=useful-scripts/useful-scripts.git;a=blob;f=debian/mksh-status;hb=HEAD
which downloads the logs from buildd.d.o and then does the same as
debian/blscan (in the package) does locally to the logs.

I also do a chmod -x on the binaries that build but fail to test,
so we still have them for debugging purposes (especially if, say,
they fail on an emulator but work natively, so we can see that),
and if the build with the system libc fails, abort.

So I don’t, strictly speaking, need this info in the binary pak-
kages any more. At least not for Debian itself; derivates may be
an issue but I don’t actively monitor any at the moment. So, I
*think* I don’t _need_ the entire…

Regression test results:
| FAIL ../../check.t:heredoc-tmpfile-8 (ignored)
| Total failed: 1 (1 ignored)
| Total passed: 578

… block, in either README.Debian in the binary package or the
build log (as the latter has this info inline anyway, even if
it *was* nice-to-have, for quickly seeing this info for all
shell binaries built in one place).

Access to build logs for derivatives is also an issue, but, as
said earlier, currently I’m not monitoring any of these anyway.

I guess I’ll drop this in the next upload, which will be coming
soon since klibc is currently broken on 32-bit platforms; bwh
knows and said he’ll most likely do a release soon.

bye,
//mirabilos
-- 
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so
reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~
(as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)

Bug#1021088: debhelper testsuite fails when run in LC_ALL=de_DE.UTF-8

[Gioele Barabucci]

Package: debhelper
Version: 13.9.1
Severity: important

When the debhelper's testsuite is run in an environment where `LC_ALL` 
is not `C.UTF-8`, various warnings are printed and some tests fail (for 
example those of dh_installchangelogs).


The solution is probably to set `LC_ALL=C.UTF-8`, but where should it be 
set? In debian/rules? In the testsuite? In the single tests?


Log of failures (run with `LC_ALL=de_DE.UTF-8`):

``` 

make[1]: Verzeichnis „/home/michael/debian/build-area/debhelper-13.9.1“ 
wird betreten

printf "package Debian::Debhelper::Dh_Version;\n\$version='13.9.1';\n1"
> lib/Debian/Debhelper/Dh_Version.pm
MAKEFLAGS= prove -lrj4 --timer t
[16:30:36] t/buildsystems/01-build-system-basic-api.t ... ok
[16:30:36] t/Dh_Lib/control-parsing.t ... ok
[16:30:36] t/Dh_Lib/00-use.t  ok
[16:30:36] t/Dh_Lib/path.t .. ok
[16:30:36] t/buildsystems/02-make-jobserver-makeflags.t . ok
[16:30:36] t/buildsystems/06-buildsystem-mkdir-rmdir.t .. ok
[16:30:36] t/buildsystems/03-bs-auto-buildable.t  ok
[16:30:37] t/buildsystems/05-load-build-system.t  ok
[16:30:37] t/debhelper-compat/syntax.t .. ok
[16:30:37] t/dh-sequencer.t . ok
[16:30:37] t/dh-lib.t ... ok
[16:30:38] t/buildsystems/04-dh_auto_do_autoconf.t .. ok
[16:30:39] t/dh_install/01-basics.t . ok
[16:30:40] t/dh_install/03-866570-dont-install-from-host.t .. ok
[16:30:42] t/dh_install/02-bugs-53.t  ok
dh_installchangelogs: Warnung: debian/changelog(l5): ungültiger
Wochentag »Di« wird ignoriert
LINE:  -- Test   Di, 06 Jul 2021 00:00:00 +
dh_installchangelogs: warning: Could not parse timestamp '06 Okt 2020
00:00:00 +'. debian/changelog will not be trimmed.
[...]
dh_installchangelogs: warning: debian/changelog could not be trimmed.
The full changelog will be installed.
dh_installchangelogs: Warnung: debian/changelog(l5): ungültiger
Wochentag »Di« wird ignoriert
LINE:  -- Test   Di, 06 Jul 2021 00:00:00 +
dh_installchangelogs: warning: Could not parse timestamp '06 Okt 2020
00:00:00 +'. debian/changelog will not be trimmed.
dh_installchangelogs: warning: debian/changelog could not be trimmed.
The full changelog will be installed.
Error parsing time at /usr/lib/x86_64-linux-gnu/perl/5.34/Time/Piece.pm
line 598.
# Looks like your test exited with 25 just after 2.
[16:30:44] t/dh_installchangelogs/dh_installchangelogs.t 
Dubious, test returned 25 (wstat 6400, 0x1900)
Failed 6/8 subtests
```

Regards,

--
Gioele Barabucci 

Bug#1020969: buildd.debian.org: Dell XPS 15 9520 - Boot hangs

[Aurelien Jarno]

control: reassign -1 installation-reports

Hi,

On 2022-09-29 20:58, Waido wrote:
> Package: buildd.debian.org
> Severity: important
> X-Debbugs-Cc: waidoshor...@protonmail.com
> 
> Dear Maintainer,
> 
> I'm trying to install Debian 11.5 (Bullseye) on a notebook Dell XPS 15 9520.
> The installation finished successfully but from the first boot of the 
> notebook on the screen appears the message
> 
> dell_smm_hwmon: unable to get SMM Dell signature
> 
> and the notebook hangs. I can't get to the shell prompt.
> From a live distro, inside installed distro, I created the file 
> /etc/modprobe.d/blacklist.conf with the content
> 
> blacklist dell-smm-hwmon
> 
> Now the notebook boots ... and hangs without showing the previous message, 
> without showing any error or interesting message.

The buildd.debian.org pseudo package is for bugs concerning the build
daemons infrastructure, which is responsible for building packages from
source for all architectures. It has nothing to do with the installer.

I am therefore reassigning this to the installation-reports package, for
you to get more chances to find people helping you.

Regards
Aurelien

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

Bug#991936: openssh-server: seccomp filter defaults to SIGSYS, could break any libc or kernel upgrade

[Colin Watson]

Control: severity -1 important
Control: tag -1 upstream
Control: forwarded -1 https://bugzilla.mindrot.org/show_bug.cgi?id=3478

On Fri, Aug 06, 2021 at 11:29:15AM +0200, Julian Andres Klode wrote:
> seccomp filters are currently setup to kill the process
> 
> #define SECCOMP_FILTER_FAIL SECCOMP_RET_KILL
> 
> /* Default deny */
> BPF_STMT(BPF_RET+BPF_K, SECCOMP_FILTER_FAIL),
> 
> this means every new libc or kernel release can cause openssh
> to break, requiring breaks from them on openssh, which does not
> scale, and is currently breaking SSH during upgrades.
> 
> This also means openssh might fail to work inside containers
> because the host kernel is newer.
> 
> The default policy needs to be changed to return ENOSYS instead,
> such that libc can fallback to other syscalls for its wrappers.
> With the caveat that umask is a bit broken, if you don't want to
> allow it, block it explicitly with RET_KILL:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1724098
> 
> This should be fixed for bullseye+1, and fixed in a point release
> IMO, it might be a tad too late right now for the release itself.

I agree this is at least a problem waiting to happen and a noticeable
inconvenience for stable release maintenance, so I've (belatedly)
forwarded it upstream with a suggested patch.  The sandbox is
security-critical enough that I don't want to patch fundamental things
about its behaviour without upstream's consent, so we'll see what they
make of my suggestion.

I don't think this needs to be release-critical.  It's a significant
problem and I'd definitely like it to be fixed, but mostly this change
would protect us against specific manifestations of syscall filtering
problems that would be grave bugs, rather than being intrinsically RC.
As such I'm downgrading it a step for now.

Thanks,

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

Bug#1016521: ristretto can't open .webp image file

[Akbarkhon Variskhanov]

Control: forwarded -1 https://gitlab.xfce.org/apps/ristretto/-/issues/50

As suggested in upstream[1], the `webp-pixbuf-loader` package enables
WebP support.

[1] https://gitlab.xfce.org/apps/ristretto/-/issues/50

Bug#1021087: [syscom] Bug#1020998: mirror.csclub.uwaterloo.ca: syncscript

[Max Erenberg]

Package: mirrors
X-Debbugs-Cc: David Bartley 
User: mirr...@packages.debian.org
Usertags: mirror-problem

Hello Julian,

> I was checking some things in the Debian mirror universe and noticed
> a problem with your mirror:
>
> o The tracefile
>   
> http://mirror.csclub.uwaterloo.ca/debian/project/trace/mirror.csclub.uwaterloo.ca
>   suggests that you are not using ftpsync.
>
>   Please use our ftpsync script to mirror Debian.
>
>   It should produce better trace files, and do the mirroring in a way that
>   ensures the mirror is in a consistent state even during updates.
>
>   
> http://mirror.csclub.uwaterloo.ca/debian/project/ftpsync/ftpsync-current.tar.gz

Thank you for bringing this to our attention. We are using ftpsync now.

--
Max Erenberg
Systems Committee
Computer Science Club of the University of Waterloo

Bug#1020998: [syscom] Bug#1020998: mirror.csclub.uwaterloo.ca: syncscript

[Max Erenberg]

Hello Julian,

> I was checking some things in the Debian mirror universe and noticed
> a problem with your mirror:
>
> o The tracefile
>   
> http://mirror.csclub.uwaterloo.ca/debian/project/trace/mirror.csclub.uwaterloo.ca
>   suggests that you are not using ftpsync.
>
>   Please use our ftpsync script to mirror Debian.

Thank you for bringing this to our attention. We are using ftpsync now.

--
Max Erenberg
Systems Committee
Computer Science Club of the University of Waterloo

Bug#1017944: Availability in Debian Stable?

[Steve McIntyre]

Hi Sebastien,

On Sat, Oct 01, 2022 at 11:18:31AM +0200, Sebastien KOECHLIN wrote:
>
>Thanks a lot for the correction.
>
>The 2.06-3~deb11u2 is now out for two weeks, but not available in Debian
>Stable.  Any new XEN installation will not be functionnal since Sept-10
>(publication of Debian 11.5).  Rollback is paintfull.
>
>https://packages.debian.org/source/bullseye/grub2 -> 2.06-3~deb11u1
>
>Will it be push into Bullseye? Or do we have to wait for 11.6?

It will go into bullseye in 11.6 as part of that point release. But
before then I'd strongly recommend adding the bullseye-updates suite
to your sources list. That suite is there specifically for this kind
of change, and *should* be automatically included when a system is
installed (using d-i at least).

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
“Changing random stuff until your program works is bad coding
 practice, but if you do it fast enough it’s Machine Learning.”
   -- https://twitter.com/manisha72617183

Bug#1021086: python3-libiio: Module is installed to a folder which is not in PYTHONPATH

[Paul Saunders]

Package: python3-libiio
Version: 0.24-2
Severity: important

Dear Maintainer,

With python3-libiio, version 0.24-2, the module is not found by python,
even after installation. The problem appears to be a simple packaging
error, because the module is installed one-level deeper than python can
see.


❯ sudo apt install python3-libiio
Place your right index finger on the fingerprint reader
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-libiio is already the newest version (0.24-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
❯ python -m iio
/usr/bin/python: No module named iio
❯ python -c "import sys;print(sys.path)"
['', '/usr/lib/python310.zip', '/usr/lib/python3.10', 
'/usr/lib/python3.10/lib-dynload', 
'/home/ipa/darac/.local/lib/python3.10/site-packages', 
'/usr/local/lib/python3.10/dist-packages', '/usr/lib/python3/dist-packages']
❯ dpkg -L python3-libiio
/.
/usr
/usr/lib
/usr/lib/python3
/usr/lib/python3/dist-packages
/usr/lib/python3/dist-packages/dist-packages
/usr/lib/python3/dist-packages/dist-packages/iio.py
/usr/lib/python3/dist-packages/dist-packages/pylibiio-0.24-py3.10.egg-info
/usr/lib/python3/dist-packages/dist-packages/pylibiio-0.24-py3.10.egg-info/PKG-INFO
/usr/lib/python3/dist-packages/dist-packages/pylibiio-0.24-py3.10.egg-info/dependency_links.txt
/usr/lib/python3/dist-packages/dist-packages/pylibiio-0.24-py3.10.egg-info/top_level.txt
/usr/share
/usr/share/doc
/usr/share/doc/python3-libiio
/usr/share/doc/python3-libiio/changelog.Debian.gz
/usr/share/doc/python3-libiio/copyright

Notice that the module is installed at
.../dist-packages/dist-packages/..., which appears to be a simple error.

For the record, running 
`PYTHONPATH=/usr/lib/python3/dist-packages/dist-packages python3 -m iio` does 
work.

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

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, 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 python3-libiio depends on:
ii  libiio0  0.24-2
ii  python3  3.10.6-1

python3-libiio recommends no packages.

python3-libiio suggests no packages.

-- no debconf information

Bug#976626: Similar package

[Francois Marier]

On 2022-10-01 at 09:57:35, Antoine Beaupré (anar...@debian.org) wrote:
> Yeah, so tldr is similar, but cheat has a number of improvements, from
> my perspective.

Thanks for those details. I had not looked into cheat all that much, but now
I'm curious to check it out!

Francois

-- 
https://fmarier.org/

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

[Witold Baryluk]

Package: base-files
Version: 12.2
Followup-For: Bug #1008735
X-Debbugs-Cc: witold.bary...@gmail.com

I also noticed the issue today.

For the context I use it for compiling mesa by outside script:

https://gist.github.com/baryluk/1041204eff4cc4fad6f1508afe67b562/5771c245a55760b7f25b05dc0b397789b27ac0b7#file-mesa-build-sh-L421-L454

as depending on a version of Debian / Ubuntu, I must manually specify
some LLVM related packages with specific version explicitly, and which
compilers to invoke exactly.

And while for testing and unstable, it requires sporadic update to the
script, it is still only relable and easy way to do this using
lsb_release info.

-- 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 6.0.0-rc5 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages base-files depends on:
ii  gawk [awk]  1:5.1.0-1
ii  mawk [awk]  1.3.4.20200120-3.1

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information

Bug#1020199: libqtxdg: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2

[Dmitry Shachnev]

Control: reassign -1 lxqt-build-tools 0.11.0-0.1
Control: affects -1 src:libqtxdg
Control: fixed -1 lxqt-build-tools/0.11.0-1
Control: close -1
Control: merge 1020151 -1

On Sun, Sep 18, 2022 at 08:55:04AM +0200, Lucas Nussbaum wrote:
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > -- Checking for module 'gio-unix-2.0'
> > --   Found gio-unix-2.0, version 2.73.3
> > CMake Error at 
> > /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 
> > (message):
> >   Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable
> >   version "2.73.3", minimum required is "2.41.0")
> > Call Stack (most recent call first):
> >   /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 
> > (_FPHSA_FAILURE_MESSAGE)
> >   /usr/share/cmake/lxqt-build-tools/find-modules/FindGLIB.cmake:113 
> > (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
> >   CMakeLists.txt:26 (find_package)

It is the same bug as #1020151, fixed in lxqt-build-tools 0.11.0-1.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1021085: mksh: ignored test making the build unreproducible

[Chris Lamb]

Source: mksh
Version: 59c-18
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort we noticed that
mksh could not be built reproducibly anymore.

This is because the test summary is printed in README.Debian, and if
any of the tests are "ignored" this is recorded as well.

However, if the number of ignored tests is different between two
specimen builds, then the package is rendered unreproducible. For
example:

   Regression test results:
  -| FAIL ../../check.t:heredoc-tmpfile-8 (ignored)
  -| Total failed: 1 (1 ignored)
  -| Total passed: 576
  +| Total failed: 0
  +| Total passed: 577

To be clear, that mksh includes test info is not necessarily a bug,
and nor is it necessarily a bug in mksh that some test is failing in
some weird environment. But the combination of the two is
unfortunately causing a reproducibility regression and I thought you
may have more context.



Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#1020893: /usr/bin/lsb_release: Re: lsb_release does not show version info in unstable

[Witold Baryluk]

Package: lsb-release
Followup-For: Bug #1020893
X-Debbugs-Cc: witold.bary...@gmail.com

Started seeing this issue today on my system:

user@debian:~$ lsb_release -r
No LSB modules are available.
Release:n/a
user@debian:~$ lsb_release -sr
No LSB modules are available.
n/a
user@debian:~$ 


user@debian:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;
user@debian:~$ 


user@debian:~$ dpkg -l base-files lsb-release
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
ii  base-files 12.2 amd64Debian base system miscellaneous 
files
ii  lsb-release12.0-1   all  Linux Standard Base version 
reporting utility (minimal implementation)


-- 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 6.0.0-rc5 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#734790:

[Janoko Famili]

Bug#1013326: Tests: please add isolation-machine restriction for smoke-tests

[Reiner Herrmann]

Hi Paride,

On Wed, Jun 22, 2022 at 12:03:50PM +0200, Paride Legovini wrote:
> I'll take care of merging 0.9.70-1 in Ubuntu, keeping the aforementioned
> delta. If you end up adding skip-not-installable (or any other
> workaround for the lack of firefox package on some Ubuntu archs) feel
> free to ping me and I'll bring the package back in sync, so it will also
> auto-sync in the future.

I have just uploaded firejail 0.9.70-2 to unstable, which has the
architecture restriction in the autopkgtest from the Ubuntu diff.

Can you please enable syncing again?

Thanks and kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#976626: Similar package

[Antoine Beaupré]

On 2022-08-08 14:47:49, Francois Marier wrote:
> This seems very similar to the tldr package:
>
>   https://packages.debian.org/stable/tldr
>
> See https://tldr.sh/ for examples.

Yeah, so tldr is similar, but cheat has a number of improvements, from
my perspective.

 1. it supports multiple collections of cheats, so you can have your own
set for your site-specific scripts

 2. the storage format is YAML instead of markdown (depends on the taste
i guess)

 3. that enables support for tags and other niceties that harder to do
in markdown

Overall, cheat doesn't try to replace manpages, it seems like a
different thing. I find the project quite interesting and wonder if we
could use it at work to document stuff quickly that would otherwise be
lost in our wiki.

(because, of course, we don't write man pages for our own tools, which
is probably the problem in the first place here...)

(also, one of the things i find silly with tldr is exactly that: it's
basically rewriting the EXAMPLES section of manpages. instead of working
on tldr, people should contribute EXAMPLES to the manpages!)

(I guess the same argument could be made for cheat as well, of course,
but it feels like it serves a different purpose.)

ymmv
-- 
Be the change you want to see happen.
- Arleen Lorrance, 1974

Bug#1021062: libc6: nonexistent locale crashes programs (for example, bash, gdb, ...)

[Aurelien Jarno]

control: reassign -1 bash
control: found -1 bash/5.2-1

Hi,

On 2022-10-01 21:01, Kan-Ru Chen wrote:
> Package: libc6
> Version: 2.35-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: kos...@debian.org
> 
> Dear maintainer,
> 
> After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent 
> locale setting
> starts to crash the system.
> 
> This is dangerous because a remote system might not always have the same 
> locale installed.
> An auto update will soft-brick the system unless the sysadmin knows to set 
> their LC_ALL=POSIX
> before attempting to ssh.
> 
> Steps to reproduce:
> 
> >From a clean installed Debian sid, upgrade to libc6 2.35-1.
> Only install C locale and en_US.UTF-8.
> 
> $ LC_ALL=ja_JP.UTF-8 bash
> bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
> Segmentation fault (core dumped)
> 
> $ LC_ALL=ja_JP.UTF-8 gdb bash
> 
> Fatal signal: Segmentation fault
> - Backtrace -
> 0x55ed3e1e8dcf ???
> 0x55ed3e2df312 ???
> 0x55ed3e2df488 ???
> 0x7f0b4a39ba9f ???
> 0x7f0b4b412204 _rl_init_locale
> 0x7f0b4b4122f1 _rl_init_eightbit
> 0x7f0b4b3f10f2 rl_initialize
> ... snip ...

FYI, this is the full backtrace with the debug packages installed:

#0  0x7f8079d0ccc7 in __GI_kill () at ../sysdeps/unix/syscall-template.S:120
#1  0x559be26519c9 in termsig_handler (sig=11) at .././sig.c:625
#2  0x559be2651c21 in termsig_handler (sig=) at 
.././sig.c:492
#3  termsig_sighandler (sig=) at .././sig.c:547
#4  
#5  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
#6  0x559be26b8682 in _rl_init_locale () at 
../../.././lib/readline/nls.c:150
#7  0x559be26b8772 in _rl_init_eightbit () at 
../../.././lib/readline/nls.c:227
#8  0x559be269766e in readline_initialize_everything () at 
../../.././lib/readline/readline.c:1292
#9  rl_initialize () at ../../.././lib/readline/readline.c:1183
#10 0x559be2662b05 in initialize_readline () at .././bashline.c:522
#11 0x559be26040a5 in yy_readline_get () at 
/usr/local/src/chet/src/bash/src/parse.y:1514
#12 0x559be2606aa1 in yy_getc () at 
/usr/local/src/chet/src/bash/src/parse.y:1462
#13 shell_getc (remove_quoted_newline=remove_quoted_newline@entry=1) at 
/usr/local/src/chet/src/bash/src/parse.y:2393
#14 0x559be2608eeb in read_token (command=0) at 
/usr/local/src/chet/src/bash/src/parse.y:3400
#15 0x559be260d05b in yylex () at 
/usr/local/src/chet/src/bash/src/parse.y:2890
#16 yyparse () at ./build-bash/y.tab.c:1854
#17 0x559be2603586 in parse_command () at .././eval.c:348
#18 0x559be2603714 in read_command () at .././eval.c:392
#19 0x559be26038c6 in reader_loop () at .././eval.c:139
#20 0x559be26023b5 in main (argc=1, argv=0x7ffe3da22078, 
env=0x7ffe3da22088) at .././shell.c:833

So the problem is that _rl_init_locale (from bash) calls strlen(NULL).

> Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
> state was invalidated when upgrading.

This is because you upgraded other packages than glibc (here bash), and the bug
is not in glibc. Downgrading bash fixes the issue. Reassigning the bug.

Regards
Aurelien

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

Bug#734790:

[Janoko Famili]

Bug#989333: xfce4-panel: does not start without --disable-wm-check

[Akbarkhon Variskhanov]

Control: severity -1 wishlist
Control: retitle -1 xfce4-panel: problem loading with bspwm

On Tue, 01 Jun 2021 08:32:27 -0300 Daniel D
 wrote:
> Package: xfce4-panel
> Version: 4.16.2-1
> Severity: important
> X-Debbugs-Cc: danidantur+report...@gmail.com
>
> Dear Maintainer,
>
> I use xfce4 replacing xfwm with bspwm in all my computers (all Debian). It 
> works great with Buster(stable) but today I've upgrade it to 
> Bullseye(testing) and then panel won't start.
>
> Tried to run xfce4-panel from terminal and I got the following output:
> xfce4-panel: No window manager registered on screen 0. To start the panel 
> without this check, run with --disable-wm-check.
> I did run it with --disable-wm-check and the panel showed up in place.
>
> Now xfce4-panel seems to work as expected.
>
> I was expecting xfce4-panel to work with bspwm out of the box as usual.
This is not an xfce4-panel bug per se. It seems that bspwm doesn't
even bother owning the WN_Sn (where n is the screen number) selection
at all. This is not compliant with ICCCM[1]. This window manager is
implemented in a very different way.

Regardless, xfce4-panel is designed to run even without a proper
window manager. The log messages are a false alarm.
panel_application_load_real() is called irrespective of whether a WM
was found or not.

After testing on unstable, I can attest that both xfce4-panel and
bspwm run without issues. Make sure to:
1) Set bspwm as your WM: `xfconf-query -c xfce4-session -p
/sessions/Failsafe/Client0_Command -n -a -t string -s bspwm`
2) Have configured both bspwm and sxhkd (God, those names!)

If that doesn't do the trick, run the following command:
`xfconf-query -c xfce4-session -p /sessions/Failsafe/Client2_Command
-n -a -t string -s "xfce4-panel" -t string -s "--disable-wm-check"`
This will start the panel skipping the check.

[1] 
https://x.org/releases/X11R7.6/doc/xorg-docs/specs/ICCCM/icccm.html#communication_with_the_window_manager_by_means_of_selections

Bug#1021084: ITP: python-semantic-release -- Automatic Semantic Versioning for Python projects

[Edward Betts]

Package: wnpp
Severity: wishlist
Owner: Edward Betts 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: python-semantic-release
  Version : 7.31.4
  Upstream Author : Rolf Erik Lekang 
* URL : https://github.com/relekang/python-semantic-release
* License : MIT
  Programming Lang: Python
  Description : Automatic Semantic Versioning for Python projects

  Python implementation of semantic-release for JS by Stephan Bönnemann.
  .
  Detect what the next version of the project should be based on the commits.
  Use the detected version to automate the release, upload to an artifact
  repository and post changelogs to GitHub.
 
I plan to maintain this package as part of the Python team.

Bug#1020463: usrmerge: breaks Hurd systems

[Michael Biebl]

On Thu, 29 Sep 2022 04:53:32 +0200 Marco d'Itri  wrote:

On Sep 22, Samuel Thibault  wrote:

> On usr merge attempt on a hurd-i386 system, things go really bad:
I am quite disappointed that it took 7 years to find out that the 
package does not work at all on Hurd.
You are requesting major changes to an algorithm which has been in use 
since ~2015, and I do not want to risk introducing bugs now that the 
package is installed by default on all existing systems.
I am not opposed to fixing this, but we need to find a way to make sure 
that it will not introduce new bugs.


Could this code be made conditional on the architecture so it doesn't 
affect linux-any ? Or would you consider this too ugly?


Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021083: securefs: autopkgtest regression: output on stderr

[Paul Gevers]

Source: securefs
Version: 0.13.0+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
securefs   from testing0.13.0+ds-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Your test 
passes, but it produces output on stderr. By default autopkgtest fails 
with output on stderr, except with the allow-stderr restriction set. 
Please fix the output or use the restriction.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/securefs/26558003/log.gz

[Info] [0x7fe804337b80] [2022-09-30 23:33:11.845448233 UTC] 
[get_random_number_engine()::Initializer::Initializer():27]Random 
seed: 
4442d8b9ef6c4bc430fada81e389a29ad79c47afb559160982b60423af6b298f1d6ee0a97c1306ab182097d3ab9ef2ad87bbc21c68bb0264a7fc783d03d493e7df41cbff77ddc3c8bc1a447461aba5fab11832b6826f61d3546ca685124469afbe924e829203b17d68f8d9e5426a529cf55c0a8c85487c95282ea8e535ee1adb377961bc68a42c9e544a63c8de4fa04dff5aea9e5ccfeaafb6ad6558af250298a30a0d27c229022979c5fba4112e2dba7fd40bf5f8ea7679662727a11b363f378d259dc5dea3953bbc1d8b9de9c1edc2013d9aa58fdf1992efcb90566744ec48cd3579c29c3e19b376d70a4cc878af4a317b42838cd97b41b55305198565733d
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.251601986 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.255596070 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.259687939 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.268763279 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 0
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.277214124 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 7
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.285512300 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 7
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.293644781 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 1
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.297981264 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 1
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.302177492 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:296]Actual padding size: 30
[Info] [0x7fe804337b80] [2022-09-30 23:33:12.306428162 UTC] 
[C_A_T_C_HT_E_S_T1()::unsigned int)>:308]Actual padding size: 30

===
All tests passed (901865 assertions in 19 test cases)

autopkgtest [23:33:12]: test command2



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021082: bash: missing BINDNOW build hardening

[Christian Göttsche]

Source: bash
Version: 5.2-1

Bash is not build with the hardening option BINDNOW[1], i.e. the
linker flag `-z now` is missing.

[1]: 
https://wiki.debian.org/Hardening#DEB_BUILD_HARDENING_BINDNOW_.28ld_-z_now.29

Bug#1021081: ITP: libdbix-admin-createtable-perl -- a module to create and drop tables, primary indexes, and sequences

[mtj]

Package: wnpp
Owner: Mason James 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libdbix-admin-createtable-perl
  Version : 2.11
  Upstream Author : Ron Savage (r...@savage.net.au)
* URL : https://metacpan.org/release/DBIx-Admin-CreateTable
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : a module to create and drop tables, primary indexes, and 
sequences



The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.

Bug#1021080: pkg-js-tools breaks node-ava autopkgtest on armel: Timed out while running tests

[Paul Gevers]

Control: reassign -1 node-ava
Control: retitle -1 flaky autopgktest on armel: Timed out while running

Hi,

I'm sorry for the noise, timing and the inner workings of my script 
picked up a failure from 10 days ago.


On Sat, 1 Oct 2022 17:57:52 +0200 Paul Gevers  wrote:
With a recent upload of pkg-js-tools the autopkgtest of node-ava fails 
in testing when that autopkgtest is run with the binary packages of 
pkg-js-tools from unstable. It passes when run with only packages from 
testing. In tabular form:


This seems to be a case of flaky behavior.

https://ci.debian.net/packages/n/node-ava/testing/armel/

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021080: pkg-js-tools breaks node-ava autopkgtest on armel: Timed out while running tests

[Paul Gevers]

Source: pkg-js-tools, node-ava
Control: found -1 pkg-js-tools/0.15.3
Control: found -1 node-ava/4.3.3+dfsg+~cs43.2.10-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of pkg-js-tools the autopkgtest of node-ava fails 
in testing when that autopkgtest is run with the binary packages of 
pkg-js-tools from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
pkg-js-tools   from testing0.15.3
node-ava   from testing4.3.3+dfsg+~cs43.2.10-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of pkg-js-tools to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=pkg-js-tools

https://ci.debian.net/data/autopkgtest/testing/armel/n/node-ava/26252424/log.gz


  ✔ base › bails when negotiating protocol returns `null`
  ✔ protocol-ava-3.2 › negotiates ava-3.2 protocol (281ms)
  ✔ protocol-ava-3.2 › main() config validation: throw when config is 
not a plain object (189ms)
  ✔ protocol-ava-3.2 › main() config validation: throw when config 
contains keys other than 'extensions', 'rewritePaths' or 'compile'
  ✔ protocol-ava-3.2 › main() config validation: throw when 
config.extensions contains empty strings
  ✔ protocol-ava-3.2 › main() config validation: throw when 
config.extensions contains non-strings
  ✔ protocol-ava-3.2 › main() config validation: throw when 
config.extensions contains duplicates
  ✔ protocol-ava-3.2 › main() config validation: config may not be an 
empty object
  ✔ protocol-ava-3.2 › main() config validation: throw when 
config.compile is invalid
  ✔ protocol-ava-3.2 › main() config validation: rewrite paths must end 
in a /

  ✔ protocol-ava-3.2 › main() extensions: defaults to ['ts']
  ✔ protocol-ava-3.2 › main() extensions: returns configured extensions
  ✔ protocol-ava-3.2 › main() extensions: always returns new arrays
  ✔ protocol-ava-3.2 › main() ignoreChange()
  ✔ protocol-ava-3.2 › main() resolveTestfile()
  ✔ protocol-ava-3.2 › main() updateGlobs()
compilation › deleting compiled files
ℹ []
ℹ []
  ✔ esm › worker(): import ESM (10.9s)

  ✖ Timed out while running tests

  3 tests were pending in test/compilation.js

  ◌ compilation › worker(): load rewritten paths files
  ◌ compilation › worker(): runs compiled files
  ◌ compilation › compile() error

  ─

  17 tests passed
  3 tests remained pending after a timeout
autopkgtest [08:35:42]: test ava-typescript



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021079: vectorscan: autopkgtest regression on ppc64el: Match for pattern "ba" at offset

[Paul Gevers]

Source: vectorscan
Version: 5.4.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
vectorscan from testing5.4.8-2
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/ppc64el/v/vectorscan/26572417/log.gz

build: OK
1a2,3

Match for pattern "ba" at offset 2
Match for pattern "ba" at offset 5

autopkgtest [11:21:38]: test build-lib



OpenPGP_signature
Description: OpenPGP digital signature

Bug#925591: grub-install fails on raid1+efi setup

[Vladimir K]

A script that syncs EFI volume data to mountpoints with numbered suffixes '.N' 
and adds boot entries via efibootmgr#!/bin/sh

if [ "$1" = "--write" ]
then
	COMMAND_PREFIX=''
	RSYNC_N=''
elif [ "$1" = "--dry-run" ]
then
	COMMAND_PREFIX='echo will run:'
	RSYNC_N='n'
else
	echo "Usage: $(basename "$0") [--dry-run|--write|--help]"
	exit 0
fi

EFI_MNT=/boot/efi
NEWLINE='
'

BOOT_CONFIG=$(
	efibootmgr -v
)

# get primary debian boot entry
PRIMARY_BOOT=$(
	echo "${BOOT_CONFIG}" | grep -E '^Boot[0-9]+\*?[[:space:]]+debian[[:space:]]+'
)

BOOT_ORDER=$(
	echo "${BOOT_CONFIG}" | grep -E '^BootOrder:[[:space:]]*' | grep -oE '[0-9]+(,[0-9]+)*' | sed -r 's/(0*?)([0-9]+(,|$))/\2/g'
)

[ -n "${PRIMARY_BOOT}" ] || { echo "Could not determine primary boot entry" >&2 ; exit 1 ; }

# get primary efi path
PRIMARY_BOOT_PATH=$(
	echo "${PRIMARY_BOOT}" | grep -Eo 'File\([^)]+\)'
)
PRIMARY_BOOT_PATH="${PRIMARY_BOOT_PATH%)}"
PRIMARY_BOOT_PATH="${PRIMARY_BOOT_PATH#File(}"

echo "${PRIMARY_BOOT_PATH}" | grep -qE '\\[a-zA-Z0-9\\._-]+\.(efi|EFI)$' || { echo "Could not determine primary boot entry efi path" >&2 ; exit 1 ; }

# get primary boot entry number
PRIMARY_BOOT_NUM=$(
	echo "${PRIMARY_BOOT}" | grep -Eo '^Boot[0-9]+' | sed -r 's/^(Boot)(0*?)([0-9]+$)/\3/'
)

echo "${PRIMARY_BOOT_NUM}" | grep -qE '^[0-9]+$' || { echo "Could not determine primary boot entry number, got: ${PRIMARY_BOOT_NUM}" >&2 ; exit 1 ; }

OCCUPIED_BOOTS=$(
	echo "${BOOT_CONFIG}" | grep -E '^Boot[0-9]+' | grep -vE '^Boot[0-9]+\*?[[:space:]]+debian(\.([0-9]|bak)+)?[[:space:]]+'
)

DUPLICATE_BOOTS=$(
	echo "${BOOT_CONFIG}" | grep -E '^Boot[0-9]+' | grep -E '^Boot[0-9]+\*?[[:space:]]+debian\.([0-9]|bak)+[[:space:]]+'
)

echo "Primary boot entry: #${PRIMARY_BOOT_NUM}: ${PRIMARY_BOOT_PATH}"
echo
echo "Duplicate boot entries:
${DUPLICATE_BOOTS}"
echo
echo "Occupied boot entries:
${OCCUPIED_BOOTS}"

EFI_DUP_MNTS=$(
	find "$(dirname "${EFI_MNT}")" -xdev -mindepth 1 -maxdepth 1 -type d -regex "${EFI_MNT}\.[0-9]+"
)

BOOT_NUM=$(( ${PRIMARY_BOOT_NUM} + 1 ))
DUPLICATE_BOOT_NUMS=''
OIFS=$IFS
for MOUNT in ${EFI_DUP_MNTS}
do
	IFS=$OIFS
	BLOCKDEV_PART=$(
		findmnt -no SOURCE "${MOUNT}"
	)
	[ ! -b "${BLOCKDEV_PART}" ] && { echo "${BLOCKDEV_PART} is not a block device" >&2 ; exit 1 ; }
	BLOCKDEV_PART_NUM=$(
		echo "${BLOCKDEV_PART}" | grep -oE '[0-9]+$'
	)
	echo "${BLOCKDEV_PART_NUM}" | grep -qE '^[0-9]+$' || { echo "Could not determine number of partition ${BLOCKDEV_PART}" >&2 ; exit 1 ; }
	BLOCKDEV=$(
		lsblk -ndo PKNAME "${BLOCKDEV_PART}"
	)
	BLOCKDEV="/dev/${BLOCKDEV}"
	[ ! -b "${BLOCKDEV}" ] && { echo "${BLOCKDEV} is not a block device" >&2 ; exit 1 ; }

	echo
	echo "Duplicate ${MOUNT}: partition ${BLOCKDEV_PART} on device ${BLOCKDEV}"
	while echo "${OCCUPIED_BOOTS}" | grep -qE "^Boot0*${BOOT_NUM}\*?[[:space:]]"
	do
		BOOT_NUM=$(( $BOOT_NUM + 1 ))
	done
	INDEX=$(echo "${MOUNT}" | grep -oE '\.[0-9]+$')
	[ -n "$COMMAND_PREFIX" ] && $COMMAND_PREFIX rsync -acAX --modify-window=1 "${EFI_MNT%/}/" "${MOUNT%/}/"
	rsync -acAX${RSYNC_N} --modify-window=1 "${EFI_MNT%/}/" "${MOUNT%/}/"
	if echo "${DUPLICATE_BOOTS}" | grep -q "^Boot0*${BOOT_NUM}"
	then
		echo "Removing existing duplicate boot entry ${BOOT_NUM}"
		$COMMAND_PREFIX efibootmgr -q -b ${BOOT_NUM} -B
		DUPLICATE_BOOTS=$(
			echo "${DUPLICATE_BOOTS}" | grep -v "^Boot0*${BOOT_NUM}"
		)
	fi
	echo "Placing duplicate boot entry ${BOOT_NUM} for debian${INDEX}"
	$COMMAND_PREFIX efibootmgr -q -c -d "${BLOCKDEV}" -p ${BLOCKDEV_PART_NUM} -L debian${INDEX} -b ${BOOT_NUM} -l "${PRIMARY_BOOT_PATH}"
	DUPLICATE_BOOT_NUMS="${DUPLICATE_BOOT_NUMS}${DUPLICATE_BOOT_NUMS:+,}${BOOT_NUM}"
done
IFS=$OIFS

[ -n "${DUPLICATE_BOOTS}" ] && echo
IFS=''
for BOOT_NUM in $(
	echo "${DUPLICATE_BOOTS}" | grep -Eo '^Boot0*[0-9]+' | sed -r 's/^(Boot)(0*?)([0-9]+$)/\3/'
)
do
	IFS=$OIFS
	echo "Removing leftover duplicate entry ${BOOT_NUM}"
	$COMMAND_PREFIX efibootmgr -q -b ${BOOT_NUM} -B
done
IFS=$OIFS

FINAL_BOOT_ORDER=$(
	echo "${PRIMARY_BOOT_NUM},${DUPLICATE_BOOT_NUMS},${BOOT_ORDER}" \
	| tr -d '\n\t ' | tr -s ','
)

echo
echo "Putting primary and duplicates to the front of boot order"
$COMMAND_PREFIX efibootmgr -q -o ${FINAL_BOOT_ORDER}
echo
echo "Removing duplicates in boot order"
$COMMAND_PREFIX efibootmgr -D -v

Bug#1021078: billiard breaks celery autopkgtest: 48 failed

[Paul Gevers]

Source: billiard, celery
Control: found -1 billiard/4.0.2-1
Control: found -1 celery/5.2.6-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
billiard   from testing4.0.2-1
celery from testing5.2.6-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of billiard to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/celery/26573246/log.gz

=== FAILURES 
===
__ test_EagerResult.test_wait_raises 
___


self = 

def test_wait_raises(self):
res = self.raising.apply(args=[3, 3])
with pytest.raises(KeyError):

  res.wait()


t/unit/tasks/test_result.py:946: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = , timeout = None
propagate = True, disable_sync_subtasks = True, kwargs = {}

def get(self, timeout=None, propagate=True,
disable_sync_subtasks=True, **kwargs):
if disable_sync_subtasks:
assert_will_not_block()
if self.successful():
return self.result
elif self.state in states.PROPAGATE_STATES:
if propagate:

  raise self.result if isinstance(

self.result, Exception) else Exception(self.result)
E   billiard.einfo.ExceptionWithTraceback: E   """
E   Traceback (most recent call last):
E File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/celery/app/trace.py", 
line 451, in trace_task

E   R = retval = fun(*args, **kwargs)
E File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/t/unit/tasks/test_result.py", 
line 940, in raising

E   raise KeyError(x, y)
E   KeyError: (3, 3)
E   """

celery/result.py:1005: ExceptionWithTraceback
-- Captured log call 
---
ERRORcelery.app.trace:trace.py:265 Task 
t.unit.tasks.test_result.raising[09b01603-8e3c-4417-8c1c-0c906d383510] 
raised unexpected: ExceptionWithTraceback()

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/celery/app/trace.py", 
line 451, in trace_task

R = retval = fun(*args, **kwargs)
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/t/unit/tasks/test_result.py", 
line 940, in raising

raise KeyError(x, y)
billiard.einfo.ExceptionWithTraceback: """
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/celery/app/trace.py", 
line 451, in trace_task

R = retval = fun(*args, **kwargs)
  File 
"/tmp/autopkgtest-lxc.fu6f9zq_/downtmp/build.87O/src/t/unit/tasks/test_result.py", 
line 940, in raising

raise KeyError(x, y)
KeyError: (3, 3)
"""
_ test_task_retries.test_retry 
_


self = 

def test_retry(self):
self.retry_task.max_retries = 3
self.retry_task.iterations = 0
self.retry_task.apply([0xFF, 0x])

  assert self.retry_task.iterations == 4

E   assert 1 == 4
E+  where 1 = <@task: t.unit.tasks.test_tasks.retry_task of 
celery.tests at 0x7fbc36762350>.iterations
E+where <@task: t.unit.tasks.test_tasks.retry_task of 
celery.tests at 0x7fbc36762350> = 
0x7fbc3f337220>.retry_task


t/unit/tasks/test_tasks.py:380: AssertionError
_ test_task_retries.test_retry_no_args 
_


self = 

def test_retry_no_args(self):
self.retry_task_noargs.max_retries = 3
self.retry_task_noargs.iterations = 0
self.retry_task_noargs.apply(propagate=True).get()

  assert self.retry_task_noargs.iterations == 4

E   assert 1 == 4
E+  where 1 = <@task: t.unit.tasks.test_tasks.retry_task_noargs 
of celery.tests at 0x7fbc36760640>.iterations
E+where <@task: t.unit.tasks.test_tasks.retry_task_noargs of 
celery.tests at 0x7fbc36760640> = 
0x7fbc3f3369e0>.retry_task_noargs


t/unit/tasks/test_tasks.py:407: AssertionError
___ 

Bug#1021077: ITP: libcache-memcached-fast-safe-perl -- Cache::Memcached::Fast with sanitizing keys and fork-safe

[mtj]

Package: wnpp
Owner: Mason James 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcache-memcached-fast-safe-perl
  Version : 0.06
  Upstream Author : Masahiro Nagano 
* URL : https://metacpan.org/release/Cache-Memcached-Fast-Safe
* License : Artistic or GPL-1
  Programming Lang: Perl
  Description : Cache::Memcached::Fast with sanitizing keys and fork-safe

Cache::Memcached::Fast::Safe is subclass of Cache::Memcached::Fast.
Cache::Memcached::Fast::Safe sanitizes all requested keys for against
memcached injection problem. and call disconnect_all automatically after fork
for fork-safe.

This description was automagically extracted from the module by dh-make-perl.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.

Bug#1021076: pdfarranger: version 1.8.2 incompatible with pikepdf 6 - please upgrade

[Jérémy Lal]

Package: pdfarranger
Version: 1.8.2-1
Severity: important


Hi,

when trying to save the pdf, it shows:

"Use pikepdf.pdf.pages interface to copy pages from one PDF to another"

This is already known:
https://github.com/pdfarranger/pdfarranger/issues/716

and latest pdfarranger version has fixed it.

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

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

Versions of packages pdfarranger depends on:
ii  gir1.2-glib-2.01.74.0-2
ii  gir1.2-gtk-3.0 3.24.34-3
ii  gir1.2-poppler-0.1822.08.0-2.1
ii  python33.10.6-1
ii  python3-cairo  1.20.1-3+b1
ii  python3-dateutil   2.8.1-6
ii  python3-gi 3.42.2-2
ii  python3-gi-cairo   3.42.2-2
ii  python3-pikepdf6.0.0+dfsg-1
ii  python3-pkg-resources  65.3.0-1.1

Versions of packages pdfarranger recommends:
ii  python3-img2pdf  0.4.4-2

pdfarranger suggests no packages.

-- no debconf information

Bug#987255: puppet: needs an extra systemd config line to use the right SE Linux context

[Jérôme Charaoui]

Control: notfound 987255 7.16.0-2
Control: reassign 987255 src:puppet

Hello,

With Puppet 7.x and later, the server and agent binaries are not the 
same anymore.


Thus, this problem only affects the 5.x series when using the deprecated 
puppet-master, and this patch is obsolete.


-- Jerome

Bug#1021075: uim: New upstream version (1.8.9) available

[Boyuan Yang]

Source: uim
Severity: normal
Version: 1:1.8.8-9.1
Tags: sid
X-Debbugs-CC: k...@daionet.gr.jp k...@debian.org

Dear Debian uim package maintainer,

A new upstream release is now available at
https://github.com/uim/uim/releases/tag/1.8.9 . Please consider packaging it
in Debian.

Thanks,
Boyuan Yang


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

Bug#1021072: RFS: streamlink/5.0.1-1~bpo11+1 -- CLI for extracting video streams from various websites to a video player

[Boyuan Yang]

Hi,

在 2022-10-01星期六的 14:48 +0200，Alexis Murzeau写道：
> Package: sponsorship-requests
> Severity: wishlist
> X-Debbugs-CC: debian-backpo...@lists.debian.org
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "streamlink" into Debian
> bullseye-backports repository.
> 
>  * Package name    : streamlink
>    Version : 5.0.1-1~bpo11+1
>    Upstream Author : Streamlink Team
>  * URL : https://streamlink.github.io/
>  * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
>    Section : python

This is now uploaded.

Cheers,
Boyuan Yang


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

Bug#1020857: libc6: 2.35-1 breaks gdb on hppa

[John David Anglin]

More info is here:
https://sourceware.org/bugzilla/show_bug.cgi?id=29635

Bug breaks glibc build (gdb attach tests fail) and probably binutils build 
(test regressions).

The problem is the dp register is sometimes not initialized for the main 
application before
initializers are run.

The attached patch fixes issue.  It restores code removed in the fix for the 
tst-audit2 failure
some months ago.  I will commit upstream as soon as more testing completes.  
I'm currently
building a +b1 version of 2.35-1 with change.

Regards,
Dave Anglin

--
John David Anglin  dave.ang...@bell.net
diff --git a/sysdeps/hppa/dl-machine.h b/sysdeps/hppa/dl-machine.h
index c865713be1..1d51948566 100644
--- a/sysdeps/hppa/dl-machine.h
+++ b/sysdeps/hppa/dl-machine.h
@@ -347,6 +347,16 @@ elf_machine_runtime_setup (struct link_map *l, struct 
r_scope_elem *scope[],
its return value is the user program's entry point.  */
 
 #define RTLD_START \
+/* Set up dp for any non-PIC lib constructors that may be called.  */  \
+static struct link_map * __attribute__((used)) \
+set_dp (struct link_map *map)  \
+{  \
+  register Elf32_Addr dp asm ("%r27"); \
+  dp = D_PTR (map, l_info[DT_PLTGOT]); \
+  asm volatile ("" : : "r" (dp));  \
+  return map;  \
+}  \
+   \
 asm (  \
 "  .text\n"\
 "  .globl _start\n"\
@@ -426,6 +436,13 @@ asm (  
\
   direct loader invocation.  Thus, argc and argv must be   \
   reloaded from from _dl_argc and _dl_argv.  */\
\
+   /* Load main_map from _rtld_local and setup dp. */  \
+"  addil   LT'_rtld_local,%r19\n"  \
+"  ldw RT'_rtld_local(%r1),%r26\n" \
+"  bl  set_dp, %r2\n"  \
+"  ldw 0(%r26),%r26\n" \
+"  copy%ret0,%r26\n"   \
+   \
/* Load argc from _dl_argc.  */ \
 "  addil   LT'_dl_argc,%r19\n" \
 "  ldw RT'_dl_argc(%r1),%r20\n"\
@@ -438,13 +455,10 @@ asm ( 
\
 "  ldw 0(%r20),%r24\n" \
 "  stw %r24,-44(%sp)\n"\
\
-   /* Call _dl_init(main_map, argc, argv, envp). */\
-"  addil   LT'_rtld_local,%r19\n"  \
-"  ldw RT'_rtld_local(%r1),%r26\n" \
-"  ldw 0(%r26),%r26\n" \
-   \
/* envp = argv + argc + 1 */\
 "  sh2add  %r25,%r24,%r23\n"   \
+   \
+   /* Call _dl_init(main_map, argc, argv, envp). */\
 "  bl  _dl_init,%r2\n" \
 "  ldo 4(%r23),%r23\n" /* delay slot */\
\

Bug#1021074: postgresql-15: collation version mismatch warnings on upgrading to 15-rc1

[Diederik de Haas]

Package: postgresql-15
Version: 15~rc1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I upgraded postgresql-15 from 15~beta4 to 15~rc1 and got a whole bunch
of warnings, which surprised me and I don't know what to do with it.

I've done the following on this database:
- - Installed psql 14
- - Created a quassel DB+role and imported data into it
- - Upgraded to psql 15 beta3
- - Dropped the quassel DB and recreated it (but it holds no data)
- - Now the upgrade to psql 15 rc1

I have NOT done any configuration (changes) to the standard DBs
I did have a libc6 upgrade from 2.34 to 2.35 in between and those
versions match the details of the warnings. That may be a coincidence.

The main part of the warnings, is this:
WARNING:  database "template1" has a collation version mismatch
DETAIL:  The database was created using collation version 2.34, but the 
operating system provides version 2.35.
HINT:  Rebuild all objects in this database that use the default collation and 
run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL 
with the right library version.

Full upgrade log:
root@cs21:~# aptitude safe-upgrade
...
Preparing to unpack .../20-postgresql-client-15_15~rc1-1_arm64.deb ...
Unpacking postgresql-client-15 (15~rc1-1) over (15~beta4-1) ...
Preparing to unpack .../21-postgresql-15_15~rc1-1_arm64.deb ...
PostgreSQL 15 catalog version number changed from 202209011 to 202209061, 
checking for clusters using the old version ...
Cluster 15/main is using catalog version 202209011
Saving binaries for PostgreSQL 15 catalog version 202209011 in 
/var/tmp/postgresql-15-202209011 ...
Unpacking postgresql-15 (15~rc1-1) over (15~beta4-1) ...
...
Setting up postgresql-15 (15~rc1-1) ...
Cluster 15 main needs upgrading due to catalog version change:
  pg_renamecluster 15 main main.old
  pg_upgradecluster 15 main.old --rename main -m upgrade 
--old-bindir=/var/tmp/postgresql-15-202209011/bin
  pg_dropcluster 15 main.old
  rm -rf /var/tmp/postgresql-15-202209011
Setting up libqt5sql5-sqlite:arm64 (5.15.6+dfsg-2) ...
Processing triggers for man-db (2.10.2-3) ...
Processing triggers for postgresql-common (243) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
Processing triggers for debianutils (5.7-0.3) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for libc-bin (2.35-1) ...
root@cs21:~# pg_renamecluster 15 main main.old
root@cs21:~# pg_upgradecluster 15 main.old --rename main -m upgrade 
--old-bindir=/var/tmp/postgresql-15-202209011/bin
Restarting old cluster with restricted connections...
Notice: extra pg_ctl/postgres options given, bypassing systemctl for start 
operation
WARNING:  database "template1" has a collation version mismatch
DETAIL:  The database was created using collation version 2.34, but the 
operating system provides version 2.35.
HINT:  Rebuild all objects in this database that use the default collation and 
run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL 
with the right library version.
WARNING:  database "template1" has a collation version mismatch
DETAIL:  The database was created using collation version 2.34, but the 
operating system provides version 2.35.
HINT:  Rebuild all objects in this database that use the default collation and 
run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL 
with the right library version.
WARNING:  database "template1" has a collation version mismatch
DETAIL:  The database was created using collation version 2.34, but the 
operating system provides version 2.35.
HINT:  Rebuild all objects in this database that use the default collation and 
run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL 
with the right library version.
Stopping old cluster...
Creating new PostgreSQL cluster 15/main ...
/usr/lib/postgresql/15/bin/initdb -D /var/lib/postgresql/15/main --auth-local 
peer --auth-host scram-sha-256 --no-instructions --encoding UTF8 --lc-collate 
en_US.utf8 --lc-ctype en_US.utf8
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with this locale configuration:
  provider:libc
  LC_COLLATE:  en_US.utf8
  LC_CTYPE:en_US.utf8
  LC_MESSAGES: en_US.UTF-8
  LC_MONETARY: en_US.UTF-8
  LC_NUMERIC:  en_US.UTF-8
  LC_TIME: en_US.UTF-8
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/15/main ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Europe/Amsterdam
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data 

Bug#1021060: apt-clone fails when the lsb_release Python module is not available

[Rann Bar-On]

This patch works for me!

--
--
Rann Bar-On
he/him/his

Bug#1021073: ITP: tkcalendar -- tkcalendar is a python module that provides the Calendar and DateEntry widgets for Tkinter

[Bo YU]

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

* Package name: tkcalendar
  Version : x.y.z
  Upstream Author : Juliette Monsel 
* URL : https://github.com/j4321/tkcalendar
* License : GPL-3.0
  Programming Lang: Python
  Description : tkcalendar is a python module that provides the Calendar 
and DateEntry widgets for Tkinter

tkcalendar is a python module that provides the Calendar and DateEntry 
widgets for Tkinter. The DateEntry widget is similar to a Combobox, 
but the drop-down is not a list but a Calendar to select a date. 
Events can be displayed in the Calendar with custom colors and a 
tooltip displays the event list for a given day. tkcalendar is 
compatible with both Python 2 and Python 3. It supports many 
locale settings (e.g. 'fr_FR', 'en_US', ..) and the colors are 
customizable.

This package is depended on by pygubu and I will maintain it under 
Python team.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1019164: Uninstalling thunar bug report

[Akbarkhon Variskhanov]

On Sun, 04 Sep 2022 16:43:11 -0400 Fellow Proghead
 wrote:
> Package: thunar
> Version: 4.16.8
>
> When I try to uninstall thunar "sudo apt autoremove thunar" it wants to
> remove the desktop environment.

This is not a bug in Thunar. Moreover, this is how APT and
specifically `autoremove` is intended to work. Please refer to apt(8)

Control: tags -1 wontfix

Bug#1020041: zope.testrunner: FTBFS: AttributeError: 're.Pattern' object has no attribute 'replace'

[Stefano Rivera]

Hi Nilesh (2022.10.01_09:48:50_+)
> > >   File "/usr/share/dh-python/dhpython/depends.py", line 228, in parse
> > > args += " -X '%s'" % pattern.replace("'", r"'\''")
> > > AttributeError: 're.Pattern' object has no attribute 'replace'
> > > make[1]: *** [debian/rules:20: override_dh_python3] Error 1
> 
> This looks like a bug with dh-python itself. Maybe this needs to be "sub" 
> instead of "replace", similar
> string regex replaces at a couple more places.

That looks like fallout from my migration of dh_python* to argparse. I
changed the objects used to represent regexes, but clearly didn't test
-X.

I'll upload a fix, now.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1021072: RFS: streamlink/5.0.1-1~bpo11+1 -- CLI for extracting video streams from various websites to a video player

[Alexis Murzeau]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-backpo...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "streamlink" into Debian
bullseye-backports repository.

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

It builds those binary packages:

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_5.0.1-1~bpo11+1.dsc

Changes since the last upload to bullseye-backports:
streamlink (5.0.1-1~bpo11+1) bullseye-backports; urgency=medium

  * Rebuild for bullseye-backports.

 -- Alexis Murzeau   Sat, 24 Sep 2022 20:10:28 +0200

streamlink (5.0.1-1) unstable; urgency=medium

  * New upstream version 5.0.1
  * d/patches: update patches

 -- Alexis Murzeau   Sat, 24 Sep 2022 18:58:43 +0200

streamlink (5.0.0-1) unstable; urgency=medium

  * d/watch: fix uscan with github
  * New upstream version 5.0.0
  * d/patches: update patches
  * d/rules: disable internet access when building package

 -- Alexis Murzeau   Sun, 18 Sep 2022 16:22:45 +0200

streamlink (4.3.0-1) unstable; urgency=medium

  * New upstream version 4.3.0
  * Update patches

 -- Alexis Murzeau   Wed, 24 Aug 2022 00:50:27 +0200



Differences from testing package (5.0.1-1):
  * d/patches,d/control: fix build with older dependencies

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









signature.asc
Description: OpenPGP digital signature

Bug#1021071: switching upstream to cgit-pink?

[Daniel Baumann]

Package: cgit

Hi,

cgit does not really keep up anymore with newer git versions, as well as
patches from the community.

it would be nice if you could switch to cgit-pink, an actively
maintained continuation of cgit:

  https://git.causal.agency/cgit-pink/about/

Regards,
Daniel

Bug#1019554: Stamp files are not updated

[Helge Kreutzmann]

Hello Lance,
On Fri, Sep 30, 2022 at 05:10:01PM +0200, Helge Kreutzmann wrote:
> On Fri, Sep 30, 2022 at 12:53:09PM +, Lance Lin wrote:
> > Thank you for your help in tracking this down. I apologize that the -35 
> > revision didn't fix it.
> > 
> > > So the check in the cron file is wrong! It should be
> > > if [ -d /run/systemd/system ]; then …
> > > 
> > 
> > > Is this the solution? Or is there a downside in changing this? And I
> > > definitely did not configure this manually. And if I log at old log
> > > entries (when anacron was still working fine), the call is the same:
> > > Jul 16 20:30:01 twentytwo CRON[15482]: (root) CMD ([ -x 
> > > /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then 
> > > /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
> > 
> > It could be. I have not changed d/cron.d at all. The only changes I made 
> > were to the service file (d/anacron.service) and that 
> > 
> > was after input from another user saying the timeout 
> > (TimeoutStopSec=infinity). Perhaps this caused the problem? Maybe this is 
> > something
> > we could both test (e.g. deleting this line)? The user said the change was 
> > just strictly better and suited their needs as well as the typical 
> > functionality.
> > See Bug#915379. 
> 
> I just deleted this line in /usr/lib/systemd/system/anacron.service
> and then run
> systemctl restart anacron
> (Hope this is right)
> 
> > If anacron was working before, this is now the only change since -32. If 
> > this breaks anacron, I am happy to remove the TimeoutStopSec line.
> 
> I'll report the outcome.

I made two reboots today, but the stamp file did not get updated. So
no need to revert the change from #915379.

So it might be some coincidental change, but where? Systemd?

> P.S. Is there some explanation about the check of 
>  "! -d /run/systemd/system"
>  ?

This is obviously not working. So I checked on a stable system, which
has seen many upgrades over the years. There this directory also
exists, anacron runs, but:

In the logs, I see 
… anacron.service: Suceeded
and 
… Started Trigger anacron every hour

I now checked old logs, and there I also see the messages about the
triggers.

So somehow the trigger is no longer executed. 

The anacron config files are the same as on my stable system (after
the above change).

# systemctl status timers.target
• timers.target - Timer Units
 Loaded: loaded (/lib/systemd/system/timers.target; static)
 Active: active since Sat 2022-10-01 09:14:51 CEST; 4h 57min ago
  Until: Sat 2022-10-01 09:14:51 CEST; 4h 57min ago
   Docs: man:systemd.special(7)

Okt 01 09:14:51 twentytwo systemd[1]: Reached target Timer Units.

So timers should be there.

I see this in the logs until 2022-09-05.

According to /var/log/apt/history.log, the following packages were updated then:
Upgrade: josm-l10n:amd64 (0.0.svn18531+dfsg-1, 0.0.svn18543+dfsg-1), josm:amd64 
(0.0.svn18531+dfsg-1, 0.0.svn18543+dfsg-1), node-write-file-atomic:amd64 
(4.0.1+~4.0.0-2, 4.0.2+~4.0.0-1), libsoup-3.0-0:amd64 (3.1.3-2, 3.1.4-1), 
bash:amd64 (5.1-6.1+b1, 5.2~rc2-2), anacron:amd64 (2.3-33, 2.3-34), 
libsoup-3.0-common:amd64 (3.1.3-2, 3.1.4-1)

All the other packages look unrelated. 

So I now remove anacron, and install 2.3-33.

dpkg -i anacron_2.3-33_amd64.deb
Vormals nicht ausgewähltes Paket anacron wird gewählt.
(Lese Datenbank ... 775863 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von anacron_2.3-33_amd64.deb ...
Entpacken von anacron (2.3-33) ...
anacron (2.3-33) wird eingerichtet ...
anacron.service is a disabled or a static unit not running, not starting it.
anacron.timer is a disabled or a static unit not running, not starting it.
Trigger für man-db (2.10.2-3) werden verarbeitet ...

And indeed:
root@twentytwo:/var/log# systemctl status anacron.service
◈ anacron.service - Run anacron jobs
 Loaded: loaded (/lib/systemd/system/anacron.service; disabled; preset: 
enabled)
 Active: inactive (dead)
   Docs: man:anacron
 man:anacrontab
root@twentytwo:/var/log# systemctl status anacron.timer
◈ anacron.timer - Trigger anacron every hour
 Loaded: loaded (/lib/systemd/system/anacron.timer; disabled; preset: 
enabled)
 Active: inactive (dead)
Trigger: n/a
   Triggers: • anacron.service


Do you have any idea what both anacron.service and anacron.timer are
disabled?

So somehow anacron -34 disabled both the service and the timer. 

Anything you want me to look at? 

Next step would be how to properly enable them again…

Thanks!

Greetings

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


signature.asc
Description: PGP signature

Bug#1021070: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-descriptive
Version: 0.9.5-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It is unmaintained
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#912924: classy-prelude-yesod: not worth maintenance burden?

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-classy-prelude-yesod -- ROM; obsolete
Control: severity -2 normal

On Sun, Nov 04, 2018 at 11:38PM, Clint Adams wrote:
> Package: classy-prelude-yesod
> Version: 1.4.0-1
> Severity: serious
> 
> classy-prelude-yesod is not currently needed and may not be
> worth the maintenance burden.  Please close this bug if you
> disagree.

Dear FTP masters, please remove haskell-classy-prelude-yesod from unstable.

-- 
Ilias

Bug#1021068: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-crypto-pubkey
Version: 0.2.8-10
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS
  * Deprecated in favor of cryptonite

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1021067: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-crypto-numbers
Version: 0.2.7-10
Severity: serious

I intend to remove this package:

  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1020649: 0ad: New upstream release - version 0.0.26

[Ludovic Rousseau]

On Sat, 24 Sep 2022 14:53:32 -0500 "David W. Kennedy"  
wrote:

Package: 0ad
Version: 0.0.25b-2+b2
Severity: wishlist

Dear Maintainer,


Hello,


Version 0.0.26 of 0ad was just released.

New Features in version 0.0.26.

  * A new civilization: The Han.
  * New campaign maps: Tarim basin and Yangtze.
  * Now units have acceleration.
  * Twenty-six new music tracks.
  * New and updated art.
  * Bug fixes for newer hardware
  * More improvements.

Source is available at
https://play0ad.com/download/source/

Build instructions are available at
https://trac.wildfiregames.com/wiki/BuildInstructions



I am on it.

The build works fine (on AMD64). Then I get an error during the auto tests:
[...]
# Note: Avoid running tests from root dir of build, otherwise certain
# tests (i.e. in testsuite MeshManager) may not work as intended and
# create spurious directories above root dir (../data/mods).
cd binaries/system/ && LD_LIBRARY_PATH=. ./test -libdir .
Running cxxtest tests (391 tests)...Skipping map generator tests (can't 
find binaries/data/mods/public/maps/random/tests/)
.
In TestCGUIText::test_regression_rP26522:
./source/gui/tests/test_CGUIText.h:319: Error: Expected ((g_VFS->Mount(L"", DataDir() / "mods" / 
"mod" / "", VFS_MOUNT_MUST_EXIST)) == INFO::OK), found (-110100 != 0)
ERROR: Failed to open font file fonts/sans-bold-13.fnt
ERROR: Failed to open font file fonts/sans-10.fnt
./source/gui/tests/test_CGUIText.h:332: Error: Expected (text.GetSize().Height 
== 14 + 9 + 8 * 2), found (22. != 39)
.Skipping
 globalscripts tests (can't find binaries/data/mods/public/globalscripts/tests/)
.Skipping component scripts tests (can't find 
binaries/data/mods/public/simulation/components/tests/setup.js)

Failed 1 and Skipped 0 of 391 tests
Success rate: 99%
make[1]: *** [debian/rules:51: override_dh_auto_test] Error 1


The complete log is available at 
https://people.debian.org/~rousseau/0ad_0.0.26-1_amd64.build

I am in contact with upstream to solve the problem.

Bye

--
Dr. Ludovic Rousseau

Bug#1017019: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-bytestring-mmap -- ROM; obsolete
Control: severity -2 normal

On Thu, Aug 11, 2022 at 04:42PM, Ilias Tsitsimpis wrote:
> Source: haskell-bytestring-mmap
> Version: 0.2.2-13
> Severity: serious
> 
> I intend to remove this package:
> 
>   * It has no rev dependencies
>   * Seems unmaintained; Home page doesn't work
>   * Seems unmaintained; Last upload more than 5 years ago
> 
> If you believe we should keep this package in Debian, please close this
> bug report.

Dear FTP masters, please remove haskell-bytestring-mmap from unstable.

-- 
Ilias

Bug#1017014: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-bindings-uname -- ROM; obsolete
Control: severity -2 normal

On Thu, Aug 11, 2022 at 04:15PM, Ilias Tsitsimpis wrote:
> Source: haskell-bindings-uname
> Version: 0.1-4
> Severity: serious
> 
> I intend to remove this package:
> 
>   * It has no rev dependencies
>   * Seems unmaintained; Last upload more than 5 years ago
> 
> If you believe we should keep this package in Debian, please close this
> bug report.

Dear FTP masters, please remove haskell-bindings-uname from unstable.

-- 
Ilias

Bug#1017013: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-bindings-sane -- ROM; obsolete
Control: severity -2 normal

On Thu, Aug 11, 2022 at 04:12PM, Ilias Tsitsimpis wrote:
> Source: haskell-bindings-sane
> Version: 0.0.1-13
> Severity: serious
> 
> I intend to remove this package:
> 
>   * It has no rev dependencies
>   * Seems unmaintained; Home page doesn't work
>   * It's not part of the latest Stackage LTS
> 
> If you believe we should keep this package in Debian, please close this
> bug report.

Dear FTP masters, please remove haskell-bindings-sane from unstable.

-- 
Ilias

Bug#1017012: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-bindings-nettle -- ROM; obsolete
Control: severity -2 normal

On Thu, Aug 11, 2022 at 03:42PM, Ilias Tsitsimpis wrote:
> Source: haskell-bindings-nettle
> Version: 0.4-3
> Severity: serious
> 
> I intend to remove this package:
> 
>   * It has no rev dependencies
>   * Seems unmaintained; Home page doesn't work
>   * It's not part of the latest Stackage LTS
> 
> If you believe we should keep this package in Debian, please close this
> bug report.

Dear FTP masters, please remove haskell-bindings-nettle from unstable.

-- 
Ilias

Bug#1021062: libc6: nonexistent locale crashes programs (for example, bash, gdb, ...)

[Kan-Ru Chen]

Package: libc6
Version: 2.35-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kos...@debian.org

Dear maintainer,

After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent locale 
setting
starts to crash the system.

This is dangerous because a remote system might not always have the same locale 
installed.
An auto update will soft-brick the system unless the sysadmin knows to set 
their LC_ALL=POSIX
before attempting to ssh.

Steps to reproduce:

>From a clean installed Debian sid, upgrade to libc6 2.35-1.
Only install C locale and en_US.UTF-8.

$ LC_ALL=ja_JP.UTF-8 bash
bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
Segmentation fault (core dumped)

$ LC_ALL=ja_JP.UTF-8 gdb bash

Fatal signal: Segmentation fault
- Backtrace -
0x55ed3e1e8dcf ???
0x55ed3e2df312 ???
0x55ed3e2df488 ???
0x7f0b4a39ba9f ???
0x7f0b4b412204 _rl_init_locale
0x7f0b4b4122f1 _rl_init_eightbit
0x7f0b4b3f10f2 rl_initialize
... snip ...

Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
state was invalidated when upgrading.

Thanks,
Kan-Ru


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

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

Versions of packages libc6 depends on:
ii  libgcc-s1  12.2.0-3

Versions of packages libc6 recommends:
ii  libidn2-0  2.3.3-1+b1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.79
pn  glibc-doc  
ii  libc-l10n  2.35-1
pn  libnss-nis 
pn  libnss-nisplus 
ii  locales2.35-1

-- debconf information:
  glibc/kernel-too-old:
  glibc/restart-failed:
  glibc/disable-screensaver:
  glibc/upgrade: true
* libraries/restart-without-asking: false
* glibc/restart-services: cron
  glibc/kernel-not-supported:

Bug#1021061: RM: haskell-exceptions -- ROM; This library is now part of GHC

[Ilias Tsitsimpis]

Package: ftp.debian.org
Severity: normal

Dear FTP master,

Please remove haskell-exceptions from unstable. This library is now part
of GHC, and provided by the ghc package.

Thanks,

Bug#1021060: apt-clone fails when the lsb_release Python module is not available

[Gioele Barabucci]

Package: apt-clone
Version: 0.4.3+nmu1
Severity: serious
Tags: patch

apt-clone currently fails when the `lsb_release` Python module is not 
available, as it is the case since 2022-09-26 in Debian unstable.


The attached patch (tested via autopkgtest) makes `apt-clone` use the 
`lsb_release` command when the namesake Python module is not available.


Regards,

--
Gioele BarabucciFrom 994c8d7149f688eeab7b89b1797ec15b3b5d Mon Sep 17 00:00:00 2001
From: Gioele Barabucci 
Date: Sat, 1 Oct 2022 13:11:38 +0200
Subject: [PATCH] Run lsb_release as command if the Python modules is not
 available

apt-clone currently fails when the `lsb_release` Python module
is not available, as it is the case since 2022-09-26 in Debian unstable.

The attached patch makes `apt-clone` use the `lsb_release` command
when the namesake Python module is not available.
---
 apt-clone|  9 +++--
 apt_clone.py | 14 +++---
 2 files changed, 18 insertions(+), 5 deletions(-)

diff --git a/apt-clone b/apt-clone
index 20b2f60..4633a8f 100755
--- a/apt-clone
+++ b/apt-clone
@@ -21,6 +21,7 @@ from __future__ import print_function
 
 import argparse
 import os
+import subprocess
 import sys
 
 from apt_clone import AptClone
@@ -132,8 +133,12 @@ if __name__ == "__main__":
 # packages because they are probably new defaults pkgs. If however
 # we are not yet on the new release its fine to remove installed
 # pkgs as part of the upgrade
-import lsb_release
-codename = lsb_release.get_os_release()["CODENAME"]
+try:
+import lsb_release
+codename = lsb_release.get_os_release()["CODENAME"]
+except ImportError:
+codename = subprocess.getoutput("lsb_release --codename --short")
+
 if (args.new_distro_codename and args.new_distro_codename == codename):
 protect_installed = True
 else:
diff --git a/apt_clone.py b/apt_clone.py
index 0598d2a..0351f2c 100644
--- a/apt_clone.py
+++ b/apt_clone.py
@@ -26,7 +26,10 @@ import fnmatch
 import glob
 import hashlib
 import logging
-import lsb_release
+try:
+import lsb_release
+except ImportError:
+lsb_release = None
 import os
 import re
 import shutil
@@ -71,8 +74,10 @@ class LowLevelCommands(object):
 return (ret == 0)
 
 def debootstrap(self, targetdir, distro=None):
-if distro is None:
+if distro is None and lsb_release:
 distro = lsb_release.get_distro_information()['CODENAME']
+if distro is None:
+distro = subprocess.getoutput("lsb_release --codename --short")
 ret = subprocess.call(["debootstrap", distro, targetdir])
 return (ret == 0)
 
@@ -187,7 +192,10 @@ class AptClone(object):
 cache = self._cache_cls(rootdir=sourcedir)
 s = ""
 foreign = ""
-distro_id = lsb_release.get_distro_information()['ID']
+if lsb_release:
+distro_id = lsb_release.get_distro_information()['ID']
+else:
+distro_id = subprocess.getoutput("lsb_release --id --short")
 for pkg in cache:
 if pkg.is_installed:
 # a version identifies the pacakge
-- 
2.35.1

Bug#1021059: RM: python-types-toml -- ROM; Package taken over by python3-typeshed

[Michael R. Crusoe]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: cru...@debian.org

The contents of python3-types-toml is now provided by python3-typeshed.

Thanks,

Bug#1021058: RM: python-types-typed-ast -- ROM; Taken over by python3-typeshed

[Michael R. Crusoe]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: cru...@debian.org

The contents of python3-types-typed-ast is now provided by
python3-typeshed,

Thanks,

Bug#1021027: dh_installsystemd: do not mask/unmask any unit files besides services

[Michael Biebl]

Am 30.09.22 um 19:05 schrieb Luca Boccassi:

On Fri, 2022-09-30 at 18:56 +0200, Michael Biebl wrote:

Am 30.09.22 um 18:45 schrieb Michael Biebl:

Package: debhelper
Version: 13.9.1
Severity: normal
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org

dh_installsystemd currently creates a maintscript code to mask/unmask any
type of unit files (.service, .socket, .timer, etc) if a package is
removed/(re)installed.

The masking/unmasking is currently done as packages unfortunately still
ship SysV init scripts along side native unit files and as SysV init
scripts are typically conffiles, they are not removed on uninstall.
So unless the package is purged systemd-sysv-generator will now see a
SysV init script and generate a corresponding runtime unit for it.

Ideally, we would not have to manually create those masks.
At least we shouldn't do it for non-service units as this can lead to
failures e.g. when socket units that are used in a service are still
masked.

Example:
# apt install -y systemd-oomd; apt remove -y systemd-oomd; apt install -y 
systemd-oomd
...
Setting up systemd-oomd (251.4-3) ...
Failed to restart systemd-oomd.service: Unit systemd-oomd.socket is masked.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.


dh_installsystemd should probably create two lists:
#UNITFILES# and #SERVICEFILES#
and the autoscripts for systemd doing the mask/unmask should only
operate on #SERVICEFILES#

There's the problem of existing masks, so we will probably need to
create the unmask code in postinst for #UNITFILES# at least for a while
longer.


Another idea how we could drop the need for the masks is to let
dh_installinit generate a "chmod -x /etc/init.d/foo" upon package
removal (and running a corresponding chmod +x on reinstall).
systemd-sysv-generator already helpfully ignores any non-executable
files in /etc/init.d

What do others think about this idea?

Getting rid of the mask/unmask bandaid would be really beneficial.


I like that, sounds simple, low-risk and effective



https://salsa.debian.org/debian/debhelper/-/merge_requests/90

Comments welcome.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021012: marked as done (linux-image-amd64 depends on linux-image-4.19.0-22-amd64, but this package is not available)

[Bastian Blank]

On Sat, Oct 01, 2022 at 06:45:03AM +, Debian Bug Tracking System wrote:
> This will resolve itself automatically once the signed packages are
> available as well (they are in progress of beeing dealt with but needs
> a manual interaction of ftp-masters).

Looks like we need to backport the changes that moved the meta package
into linux-signed-*.  This now also affects the build of the cloud
images and breaks them.

Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown

Bug#1021057: cp2k autopkgtest times outs on armel

[Paul Gevers]

Source: cp2k
Version: 6.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails on armel. 
What's worse, it fails because it seems to hang and eventually times out 
due to autopkgtest. Can you please investigate the situation and fix it? 
I copied some of the output at the bottom of this report.


Tests that time out (while normally running in much less time) are bad 
for our infrastructure. I have added your package to our reject_list on 
armel and will remove it once this bug is closed.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/packages/c/cp2k/

https://ci.debian.net/data/autopkgtest/testing/armel/c/cp2k/26510840/log.gz


Running MC_QS_cluster.inp
>>> 
/tmp/autopkgtest-lxc._uoweqoc/downtmp/build.l8C/src/tools/regtesting/../..//TEST-Linux-armv8l-gfortran-psmp-2022-09-28_01-25-33/tests/MC/regtest
MC_QS.inp 
-51.34794469 OK (  31.92 sec)
MC_QS_restart.inp 
-51.34909000 OK (  38.61 sec)
GEMC_NpT_box1.inp 
0.49826574 OK (   5.68 sec)
GEMC_NVT_box1.inp 
0.49803069 OK (   5.25 sec)
GEMC_swap_box1.inp 
0.55872200 OK (   9.25 sec)
canonical.inp 
0.55333815 OK (   0.94 sec)
canonical_bias.inp 
0.38566238 OK (   3.88 sec)
virial.inp 
-.723498E+03 OK (   3.35 sec)
hmc.inp 
   KILLED
MC_QS_cluster.inp 
-123.50157228768187   KILLED
<<< 
/tmp/autopkgtest-lxc._uoweqoc/downtmp/build.l8C/src/tools/regtesting/../..//TEST-Linux-armv8l-gfortran-psmp-2022-09-28_01-25-33/tests/MC/regtest 
(9 of 53) done in 551.00 sec
Starting regression tests in 
/tmp/autopkgtest-lxc._uoweqoc/downtmp/build.l8C/src/tools/regtesting/../..//TEST-Linux-armv8l-gfortran-psmp-2022-09-28_01-25-33/tests/QS/regtest-ri-mp2 
(10 of 53)

Running RI_MP2_H2O.inp
autopkgtest [04:12:14]: ERROR: timed out on command [...]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020041: zope.testrunner: FTBFS: AttributeError: 're.Pattern' object has no attribute 'replace'

[Nilesh Patra]

reassign -1 dh-python 5.20220924
stop

Hi,

On Sun, 18 Sep 2022 08:02:58 +0200 Lucas Nussbaum  wrote:
> Source: zope.testrunner
> > make[1]: Entering directory '/<>'
> > dh_python3 --shebang=/usr/bin/python3 -X tests
> > I: dh_python3 tools:114: replacing shebang in 
> > debian/python3-zope.testrunner/usr/bin/zope-testrunner3
> > I: dh_python3 tools:114: replacing shebang in 
> > debian/python3-zope.testrunner/usr/bin/zope-testrunner
> > Traceback (most recent call last):
> >   File "/usr/bin/dh_python3", line 284, in 
> > main()
> >   File "/usr/bin/dh_python3", line 214, in main
> > dependencies.parse(stats, options)
> >   File "/usr/share/dh-python/dhpython/depends.py", line 228, in parse
> > args += " -X '%s'" % pattern.replace("'", r"'\''")
> > AttributeError: 're.Pattern' object has no attribute 'replace'
> > make[1]: *** [debian/rules:20: override_dh_python3] Error 1

This looks like a bug with dh-python itself. Maybe this needs to be "sub" 
instead of "replace", similar
string regex replaces at a couple more places.

Please let me know if I made a mistake here and this is not a bug in dh-python.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1021056: free(): invalid pointer and double free or corruption (!prev) when taking screenshot of 540x360 video

[Bagas Sanjaya]

Package: vlc
Version: 3.0.17.4-0+deb11u1
Severity: normal

I discovered this bug when I tried to take the screenshot of "I Died
in a Car Crash" contemporary dance video by Ana Zimhart ([1]), which
have been downloaded to my computer. The video resolution was 540x360.

When the video was played at position 1:53 (when Ana did arc penché
trick at 90 degrees leg position), I took a snapshot. Instead of
vlcsnap-* image on ~/Pictures be generated, VLC exited with invalid
pointer error on free(). The tail from "vlc -vvv" was:

```
[56b17d80] main filter debug: Filter 'VAAPI filters' (0x56b184f0) 
appended to chain
[56b1c9d0] main filter debug: looking for video converter module 
matching "any": 23 candidates
[56b1c9d0] swscale filter debug: 540x360 (544x368) chroma: I420 -> 
540x360 (544x368) chroma: RV24 with scaling using Bicubic (good quality)
[56b1c9d0] main filter debug: using video converter module "swscale"
[56b17d80] main filter debug: Filter 'Swscale' (0x56b1c9d0) 
appended to chain
[56b17d80] main filter debug: using video converter module "chain"
[56b16560] main filter debug: Filter 'chain' (0x56b17d80) appended 
to chain
[56b2f2f0] main filter debug: looking for video converter module 
matching "any": 23 candidates
[swscaler @ 0x56b31e40] Forcing full internal H chroma due to input having 
non subsampled chroma
[56b2f2f0] swscale filter debug: 540x360 (544x368) chroma: RV24 -> 
540x360 (540x360) chroma: RV24 with scaling using Bicubic (good quality)
[56b2f2f0] main filter debug: using video converter module "swscale"
[56b16560] main filter debug: Filter 'Swscale' (0x56b2f2f0) 
appended to chain
[56b16560] main filter debug: using video converter module "chain"
[56b0ee00] main encoder debug: removing module "png"
[56b16560] main filter debug: removing module "chain"
[56b17d80] main filter debug: removing module "chain"
[56b184f0] main filter debug: removing module "vaapi_filters"
free(): invalid pointer
```

The log above was from gdb session. When vlc was invoked outside gdb with the
reproducer above, I got double free or corruption (!prev) error. The tail log
for that case was:

```
[7efe3044dcb0] main filter debug: Filter 'VAAPI filters' (0x7efe300d5d30) 
appended to chain
[7efe300d0f70] main filter debug: looking for video converter module 
matching "any": 23 candidates
[7efe300d0f70] swscale filter debug: 540x360 (544x368) chroma: I420 -> 
540x360 (544x368) chroma: RV24 with scaling using Bicubic (good quality)
[7efe300d0f70] main filter debug: using video converter module "swscale"
[7efe3044dcb0] main filter debug: Filter 'Swscale' (0x7efe300d0f70) 
appended to chain
[7efe3044dcb0] main filter debug: using video converter module "chain"
[7efe306b3d00] main filter debug: Filter 'chain' (0x7efe3044dcb0) appended 
to chain
[7efe300d0700] main filter debug: looking for video converter module 
matching "any": 23 candidates
[swscaler @ 0x7efe309eac80] Forcing full internal H chroma due to input having 
non subsampled chroma
[7efe300d0700] swscale filter debug: 540x360 (544x368) chroma: RV24 -> 
540x360 (540x360) chroma: RV24 with scaling using Bicubic (good quality)
[7efe300d0700] main filter debug: using video converter module "swscale"
[7efe306b3d00] main filter debug: Filter 'Swscale' (0x7efe300d0700) 
appended to chain
[7efe306b3d00] main filter debug: using video converter module "chain"
[7efe3010] main encoder debug: removing module "png"
[7efe306b3d00] main filter debug: removing module "chain"
[7efe3044dcb0] main filter debug: removing module "chain"
[7efe300d5d30] main filter debug: removing module "vaapi_filters"
double free or corruption (!prev)
```

The bug didn't occur on 640x360 and 1280x720 videos.

The similar bug have been reported on Ubuntu ([2]) with older VLC
version.

[1]: https://www.youtube.com/watch?v=eoocJ3euHy8
[2]: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1894968

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

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

Versions of packages vlc depends on:
ii  vlc-bin  3.0.17.4-0+deb11u1
ii  vlc-plugin-base  3.0.17.4-0+deb11u1
ii  vlc-plugin-qt3.0.17.4-0+deb11u1
ii  vlc-plugin-video-output  3.0.17.4-0+deb11u1

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.17.4-0+deb11u1
ii  vlc-plugin-access-extra3.0.17.4-0+deb11u1
ii  

Bug#1021055: asmjit autopkgtest times out

[Paul Gevers]

Source: asmjit
Version: 0.0~git20211214.2a706fd-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. What's worse, 
it fails because it seems to hang since recently and eventually times 
out due to autopkgtest. Can you please investigate the situation and fix 
it? I copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. Also tests that time out (while 
normally running in much less time) are bad for our infrastructure. I 
have added your package to our reject_list and will remove it once this 
bug is closed.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/packages/a/asmjit/

[ 97%] Built target asmjit_test_instinfo
[ 98%] Building CXX object 
CMakeFiles/asmjit_test_compiler.dir/test/asmjit_test_compiler.cpp.o
[ 99%] Building CXX object 
CMakeFiles/asmjit_test_compiler.dir/test/asmjit_test_compiler_x86.cpp.o

[100%] Linking CXX executable asmjit_test_compiler
[100%] Built target asmjit_test_compiler
Running tests...
Test project /tmp/autopkgtest-lxc.zi7__ym3/downtmp/build.EGf/src/build
Start 1: asmjit_test_unit
autopkgtest [08:30:54]: ERROR: timed out on command


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021054: nextcloud-desktop: Depends on: qtbase-abi-5-15-4 but is not installable

[greg]

Package: nextcloud-desktop
Version: 3.6.0-2
Severity: normal
X-Debbugs-Cc: gre...@gmx.de

Dear Maintainer,

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

   * What led up to the situation?
Use of nextcloud with debian sid
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages nextcloud-desktop depends on:
ii  libc6  2.35-1
ii  libcloudproviders0 0.3.1-2
ii  libgcc-s1  12.2.0-3
ii  libglib2.0-0   2.74.0-2
pn  libnextcloudsync0  
ii  libqt5core5a   5.15.6+dfsg-2
ii  libqt5dbus55.15.6+dfsg-2
ii  libqt5gui5 5.15.6+dfsg-2
pn  libqt5keychain1
ii  libqt5network5 5.15.6+dfsg-2
ii  libqt5qml5 5.15.6+dfsg-2
ii  libqt5quick5   5.15.6+dfsg-2
pn  libqt5quickcontrols2-5 
pn  libqt5sql5-sqlite  
ii  libqt5svg5 5.15.6-2
pn  libqt5webenginecore5   
pn  libqt5webenginewidgets5
ii  libqt5widgets5 5.15.6+dfsg-2
ii  libstdc++6 12.2.0-3
pn  nextcloud-desktop-common   
pn  nextcloud-desktop-l10n 
pn  qml-module-qt-labs-platform
pn  qml-module-qtgraphicaleffects  
pn  qml-module-qtqml-models2   
pn  qml-module-qtquick-controls2   
pn  qml-module-qtquick-dialogs 
pn  qml-module-qtquick-layouts 
pn  qml-module-qtquick-window2 
pn  qml-module-qtquick2

Versions of packages nextcloud-desktop recommends:
pn  nextcloud-desktop-doc  

nextcloud-desktop suggests no packages.

Bug#1017944: Availability in Debian Stable?

[Sebastien KOECHLIN]

Hello,

Thanks a lot for the correction.

The 2.06-3~deb11u2 is now out for two weeks, but not available in Debian
Stable.  Any new XEN installation will not be functionnal since Sept-10
(publication of Debian 11.5).  Rollback is paintfull.

https://packages.debian.org/source/bullseye/grub2 -> 2.06-3~deb11u1

Will it be push into Bullseye? Or do we have to wait for 11.6?

Bug#1012250: Fixing CI bugs for a package on the REJECT list

[Jeff]

Hi Paul,

On 01/10/2022 11:06, Paul Gevers wrote:
I have triggered several runs (about 15 or so) and they all passed. I 
have removed the block and am lowering the severity of this bug for now.


What bothers me about this is that these flaky tests do not occur with 
the buildd hosts:


Well, the failure didn't happen that often, so maybe it just didn't 
happen on the buildd. Also, maybe it's something relatively new (and you 
only had X chances on the buildds).


We'll keep monitoring.


Thanks for this. I'll keep looking at the CI builds and will try to 
diagnose the timeouts when they happen.


Regards

Jeff


OpenPGP_signature
Description: OpenPGP digital signature