Bug#1004125: Screen flickering with 2.4.109

[Philipp Marek]

ion because the issue is closed.
If you can still reproduce this with the latest kernel and libdrm 
packages,

can you open a new issue upstream? And mention that in this bug?


Well, right now with 6.5.0-1-amd64 I can't reproduce.
(Yeah, that's not the latest, I know)

Bug#1055624: viking: Segmentation fault when quitting viking

[Paul Gevers]

Control: forwarded -1 https://github.com/viking-gps/viking/issues/202

Hi,

Thanks. I have forwarded the issue upstream.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1037410: libfuse3-3: always warns "Ignoring invalid max threads value 4294967295 > max (100000)." by default

[Sergio Gelato]

control: tags -1 + fixed-upstream

This was fixed in upstream commit 2da03e389866835e29b78a4546c6f1f87aab8fe1 , 
first released in version 3.14.1.

Bug#1055628: neomutt crashes in send dialogue

[Jörg Sommer]

Package: neomutt
Version: 20220429+dfsg1-4.1
Severity: normal

Hello,

steps to reproduce:

1. open neomutt and compose a mail to someone
2. after the editor closes, select signing of the mail and hit send
3. enter the wrong password or cancel the signing
4. neomutt's send dialogue opens again
5. now, hit `f` to change the fcc field and enter something new
6. when hitting enter, neomutt crashes

This is the backtrace:

```
   PID: 2093 (neomutt)
   UID: 1000 (joerg)
   GID: 1000 (joerg)
Signal: 11 (SEGV)
 Timestamp: Thu 2023-11-09 07:29:04 CET (28s ago)
  Command Line: /usr/bin/neomutt
Executable: /usr/bin/neomutt
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
  Unit: user@1000.service
 User Unit: org.gnome.Shell@wayland.service
 Slice: user-1000.slice
 Owner UID: 1000 (joerg)
   Boot ID: fe8f45791ffb41f89b0d9c8032028a98
Machine ID: 523cb54753234ed08c13ec497d0d3b64
  Hostname: zenbook
   Storage: 
/var/lib/systemd/coredump/core.neomutt.1000.fe8f45791ffb41f89b0d9c8032028a98.2093.169951134400.zst
 (present)
  Size on Disk: 6.4M
   Message: Process 2093 (neomutt) of user 1000 dumped core.

Downloading separate debug info for /usr/bin/neomutt...
[New LWP 2093]
Downloading separate debug info for /lib/x86_64-linux-gnu/libncursesw.so.6...
Downloading separate debug info for /lib/x86_64-linux-gnu/libsqlite3.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libnotmuch.so.5...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgpgme.so.11...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgsasl.so.18...
Downloading separate debug info for /lib/x86_64-linux-gnu/liblua5.4.so.0...
Downloading separate debug info for 
/home/joerg/.cache/debuginfod_client/97fdbe62499f5fc49a4177e431c55d6b363daa6c/debuginfo...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgnutls.so.30...
Downloading separate debug info for /lib/x86_64-linux-gnu/libidn.so.12...
Downloading separate debug info for 
/lib/x86_64-linux-gnu/libtokyocabinet.so.9...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgmime-3.0.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libtalloc.so.2...
Downloading separate debug info for /lib/x86_64-linux-gnu/libxapian.so.30...
Downloading separate debug info for /lib/x86_64-linux-gnu/libsexp.so.2...
Downloading separate debug info for /lib/x86_64-linux-gnu/libassuan.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libntlm.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgssglue.so.1...
Downloading separate debug info for /lib/x86_64-linux-gnu/libp11-kit.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libidn2.so.0...
Downloading separate debug info for /lib/x86_64-linux-gnu/libunistring.so.5...
Downloading separate debug info for /lib/x86_64-linux-gnu/libtasn1.so.6...
Downloading separate debug info for /lib/x86_64-linux-gnu/libnettle.so.8...
Downloading separate debug info for /lib/x86_64-linux-gnu/libhogweed.so.6...
Downloading separate debug info for /lib/x86_64-linux-gnu/libgmp.so.10...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/neomutt'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  pattern_exec (pat=pat@entry=0x5795a62bac00, flags=flags@entry=0 '\000', 
m=m@entry=0x2074726f62413a71, e=e@entry=0x6320206f543a7420, msg=0x0, 
cache=cache@entry=0x7ffd05a71fb0) at ../pattern/exec.c:899
Download failed: Invalid argument.  Continuing without source file 
./obj-x86_64-linux-gnu/../pattern/exec.c.
899 ../pattern/exec.c: Inappropriate ioctl for device.
#0  pattern_exec (pat=pat@entry=0x5795a62bac00, flags=flags@entry=0 '\000', 
m=m@entry=0x2074726f62413a71, e=e@entry=0x6320206f543a7420, msg=0x0, 
cache=cache@entry=0x7ffd05a71fb0) at ../pattern/exec.c:899
__func__ = "pattern_exec"
#1  0x5795a430b79c in mutt_pattern_exec (pat=0x5795a62bac00, 
flags=flags@entry=0 '\000', m=m@entry=0x2074726f62413a71, 
e=e@entry=0x6320206f543a7420, cache=cache@entry=0x7ffd05a71fb0) at 
../pattern/exec.c:1116
needs_msg = 
msg = 0x0
matched = 
#2  0x5795a4293415 in mutt_message_hook (m=0x2074726f62413a71, 
e=0x6320206f543a7420, type=type@entry=2048) at ../hook.c:646
hook = 0x5795a62bb320
cache = {list_all = 0, list_one = 0, sub_all = 0, sub_one = 0, 
pers_recip_all = 0, pers_recip_one = 0, pers_from_all = 0, pers_from_one = 0}
err = 0x5795a6214b90
__func__ = "mutt_message_hook"
#3  0x5795a42f2a96 in compose_email_observer (nc=) at 
../compose/compose.c:173
shared = 
#4  0x5795a4384699 in send (source=0x5795a673c6c0, current=0x5795a673c6c0, 
event_type=event_type@entry=NT_ENVELOPE, event_subtype=event_subtype@entry=3, 

Bug#1055510: Best way to coordinate this fix

[Helmut Grohne]

Hi Francois,

On Wed, Nov 08, 2023 at 01:00:33PM -0800, Francois Marier wrote:
> If anybody would like to double-check (or test) the package I've prepared,
> it's in salsa right now.

Thank you. I suggest going via experimental first.
https://wiki.debian.org/UsrMerge recommends uploading to experimental
when moving files from / to /usr. This allows some qa already and in
particular dumat will have a second look at it. That look is fairly
limited at this time, because systemd conflicts with molly-guard now,
but I can locally make it pretend it would not and feed back the result
to you. Alternatively, Luca can perform another experimental upload of
systemd adding a version constraint to the conflict for molly-guard.
Does that extra detour make sense to you?

Helmut

Bug#1055592: systemd: suspend and hibernate does not longer work

[Michael Ott]

This patch fixed the problem. Thanks to Mike Yuan


On Wed, 2023-11-08 at 16:10 +, Luca Boccassi wrote:
> On Wed, 08 Nov 2023 16:50:12 +0100 Michael Ott 
> wrote:
> > Package: systemd
> > Version: 255~rc1-3
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > Since yesterday hibernate and suspend does not longer work.
> journalctl
> > show me this:
> > 
> > systemctl status systemd-suspend.service
> > × systemd-suspend.service - System Suspend
> >   Loaded: loaded (/usr/lib/systemd/system/systemd-
> > suspend.service;
> static)
> >   Active: failed (Result: signal) since Wed 2023-11-08 16:31:01
> CET; 12min ago
> >     Docs: man:systemd-suspend.service(8)
> >  Process: 7133 ExecStart=/usr/lib/systemd/systemd-sleep suspend
> (code=killed, signal=ABRT)
> >     Main PID: 7133 (code=killed, signal=ABRT)
> >  CPU: 44ms
> > 
> > Nov 08 16:31:01 k-c13 systemd[1]: Starting systemd-suspend.service
> > -
> System Suspend...
> > Nov 08 16:31:01 k-c13 systemd-sleep[7133]: Failed to lock home
> directories: Unknown object '/org/freedesktop/home1'.
> > Nov 08 16:31:01 k-c13 systemd-sleep[7133]: Performing sleep
> > operation
> 'suspend'...
> > Nov 08 16:31:01 k-c13 systemd-sleep[7133]: *** invalid open64 call:
> O_CREAT or O_TMPFILE without mode ***: terminated
> > Nov 08 16:31:01 k-c13 systemd[1]: systemd-suspend.service: Main
> process exited, code=killed, status=6/ABRT
> > Nov 08 16:31:01 k-c13 systemd[1]: systemd-suspend.service: Failed
> with result 'signal'.
> > Nov 08 16:31:01 k-c13 systemd[1]: Failed to start systemd-
> suspend.service - System Suspend.
> > 
> > I also got this output:
> > 
> > systemctl list-units --type=mount --all | grep home
> > ●
> home.mount   
>   
>     not-found inactive dead    home.mount
> > 
> > My home directory looks like that:
> > ls -l /home
> > total 0
> > lrwxrwxrwx 1 root root 18 Nov 24  2018 michael ->
> > /srv/home/michael/
> > 
> > What is the problem? Since yesterday it works
> 
> Please open an issue upstream on Github:
> 
> https://github.com/systemd/systemd/issues/new
> 

-- 
CU  
 
  Michael
  
-- 
    ,''`.   
   : :' :   Michael Ott 
   `. `'    e-mail: michael at k-c13 dot org
 `-

Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich derNutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Description: 
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 systemd (255~rc1-3.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * test patch #29939 https://github.com/systemd/systemd/pull/29939
Author: Michael Ott 

---
The information above should follow the Patch Tagging Guidelines, please
checkout https://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: (upstream|backport|vendor|other), (|commit:)
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: (no|not-needed|)
Applied-Upstream: , (|commit:)
Reviewed-By: 
Last-Update: 2023-11-09

--- systemd-255~rc1.orig/src/basic/fd-util.c
+++ systemd-255~rc1/src/basic/fd-util.c
@@ -761,9 +761,10 @@ finish:
 }
 
 int fd_reopen(int fd, int flags) {
-int new_fd, r;
+int r;
 
 assert(fd >= 0 || fd == AT_FDCWD);
+assert(!FLAGS_SET(flags, O_CREAT));
 
 /* Reopens the specified fd with new flags. This is useful for convert an O_PATH fd into a regular one, or to
  * turn O_RDWR fds into O_RDONLY fds.
@@ -787,19 +788,12 @@ int fd_reopen(int fd, int flags) {
  * the same way as the non-O_DIRECTORY case. */
 return -ELOOP;
 
-if (FLAGS_SET(flags, O_DIRECTORY) || fd == AT_FDCWD) {
+if (FLAGS_SET(flags, O_DIRECTORY) || fd == AT_FDCWD)
 /* If we shall reopen the fd as directory we can just go via "." and thus bypass the whole
  * magic /proc/ directory, and make ourselves independent of that being mounted. */
-new_fd = openat(fd, ".", flags | O_DIRECTORY);
-if (new_fd < 0)
-return -errno;
-
-return new_fd;
-}
-
-assert(fd >= 0);
+return RET_NERRNO(openat(fd, ".", flags | O_DIRECTORY));
 
-new_fd = open(FORMAT_PROC_FD_PATH(fd), flags);
+int new_fd = open(FORMAT_PROC_FD_PATH(fd), flags);
 if (new_fd < 0) {
 if (errno != ENOENT)
 return -errno;
@@ -825,6 +819,7 @@ int fd_reopen_condition(
 int r, new_fd;
 
 assert(fd >= 0);
+assert(!FLAGS_SET(flags, O_CREAT));
 

Bug#1055627: gnome-shell: Display never turns off at lock screen when running SDL2 (GNOME on Xorg)

[Eric Li]

Package: gnome-shell
Version: 43.6-1~deb12u2
Severity: normal
X-Debbugs-Cc: lixiaoyi13691419...@gmail.com

I am using GNOME on Xorg. Normally, when I lock the screen, the display will
be turned off. Only when I move the mouse / press the keyboard, the display
will turn back on.

However, when I am running a SDL2 application and lock the screen, the display
turns off at first. However, after less than 1 minute, the display turns on by
itself. The display stays on even after waiting for a few minutes.

Way to reproduce (demo video: ):

1. Switch to "GNOME on Xorg", the default for Debian is Wayland.
2. Open an SDL2 application. For example this bug is reproducible using
. Can also reproduce this problem
using PPSSPP. My SDL version is 2.26.5.
3. Lock the screen using Super+L. See that the display is turned off.
4. Wait for a few minutes, notice that the display is turned on, even without
any user input. The display stays on forever.

Expected behavior:

4. The display should be off when there is no user input. (This is the behavior
of GNOME on Wayland).

Workaround: Use SDL_VIDEO_ALLOW_SCREENSAVER=1 to prevent SDL2 from disabling
screensaver.

Note: this bug is previously reported to SDL at , but is considered likely a bug of GNOME.


-- System Information:
Debian Release: 12.2
  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)
Foreign Architectures: i386

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN:zh
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-accountsservice-1.0   22.08.8-6
ii  gir1.2-adw-1 1.2.2-1
ii  gir1.2-atk-1.0   2.46.0-5
ii  gir1.2-atspi-2.0 2.46.0-5
ii  gir1.2-freedesktop   1.74.0-3
ii  gir1.2-gcr-3 3.41.1-1+b1
ii  gir1.2-gdesktopenums-3.0 43.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii  gir1.2-gdm-1.0   43.0-3
ii  gir1.2-geoclue-2.0   2.6.0-2
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gnomebluetooth-3.042.5-3
ii  gir1.2-gnomedesktop-3.0  43.2-2
ii  gir1.2-graphene-1.0  1.10.8-1
ii  gir1.2-gstreamer-1.0 1.22.0-2
ii  gir1.2-gtk-3.0   3.24.38-2~deb12u1
ii  gir1.2-gtk-4.0   4.8.3+ds-2+deb12u1
ii  gir1.2-gweather-4.0  4.2.0-2
ii  gir1.2-ibus-1.0  1.5.27-5
ii  gir1.2-mutter-11 43.6-1~deb12u1
ii  gir1.2-nm-1.01.42.4-1
ii  gir1.2-nma-1.0   1.10.6-1
ii  gir1.2-pango-1.0 1.50.12+ds-1
ii  gir1.2-polkit-1.0122-3
ii  gir1.2-rsvg-2.0  2.54.7+dfsg-1~deb12u1
ii  gir1.2-soup-3.0  3.2.2-2
ii  gir1.2-upowerglib-1.00.99.20-2
ii  gir1.2-webkit2-4.1   2.42.1-1~deb12u1
ii  gnome-backgrounds43.1-1
ii  gnome-settings-daemon43.0-4
ii  gnome-shell-common   43.6-1~deb12u2
ii  gsettings-desktop-schemas43.0-1
ii  gstreamer1.0-pipewire0.3.65-3
ii  libatk-bridge2.0-0   2.46.0-5
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9+deb12u3
ii  libcairo21.16.0-7
ii  libecal-2.0-23.46.4-2
ii  libedataserver-1.2-273.46.4-2
ii  libgcr-base-3-1  3.41.1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgirepository-1.0-11.74.0-3
ii  libgjs0g 1.74.2-1+deb12u1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.74.6-2
ii  libglib2.0-bin   2.74.6-2
ii  libgnome-autoar-0-0  0.4.3-1
ii  libgnome-desktop-3-2043.2-2
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-3-0   

Bug#1055626: cabal-install: pkg-config package gtk4-any, not found in the pkg-config database

[Elizaveta L.]

Package: cabal-install
Version: 3.8.1.0-1
Severity: normal

Dear Maintainer,

When I try to install gi-gtk-4.0.8 I get the following error

```
Resolving dependencies...
Error: cabal: Could not resolve dependencies:
[__0] next goal: gi-gtk (user goal)
[__0] rejecting: gi-gtk-4.0.8 (conflict: pkg-config package gtk4-any, not
found in the pkg-config database)
[__0] rejecting: gi-gtk-4.0.6, gi-gtk-4.0.5, gi-gtk-4.0.4, gi-gtk-4.0.3,
gi-gtk-4.0.2, gi-gtk-4.0.1, gi-gtk-3.0.41, gi-gtk-3.0.39, gi-gtk-3.0.38,
gi-gtk-3.0.37, gi-gtk-3.0.36, gi-gtk-3.0.35, gi-gtk-3.0.34, gi-gtk-3.0.33,
gi-gtk-3.0.32, gi-gtk-3.0.31, gi-gtk-3.0.30, gi-gtk-3.0.29, gi-gtk-3.0.28,
gi-gtk-3.0.27, gi-gtk-3.0.26, gi-gtk-3.0.25, gi-gtk-3.0.24, gi-gtk-3.0.23,
gi-gtk-3.0.22, gi-gtk-3.0.21, gi-gtk-3.0.20, gi-gtk-3.0.19, gi-gtk-3.0.18,
gi-gtk-3.0.17, gi-gtk-3.0.16, gi-gtk-3.0.15, gi-gtk-3.0.14, gi-gtk-3.0.13,
gi-gtk-3.0.12, gi-gtk-3.0.11, gi-gtk-3.0.10, gi-gtk-3.0.9, gi-gtk-3.0.8,
gi-gtk-3.0.7, gi-gtk-3.0.6, gi-gtk-3.0.5, gi-gtk-3.0.4, gi-gtk-3.0.3,
gi-gtk-3.0.2, gi-gtk-3.0.1, gi-gtk-0.3.18.15, gi-gtk-0.3.18.14,
gi-gtk-0.3.18.13, gi-gtk-0.3.18.12, gi-gtk-0.3.16.12, gi-gtk-0.3.18.10,
gi-gtk-0.3.16.11, gi-gtk-0.3.16.10, gi-gtk-0.3.16.9, gi-gtk-0.3.16.8
(constraint from user target requires ==4.0.8)
[__0] fail (backjumping, conflict set: gi-gtk)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: gi-gtk
```

Apt says that `libgtk-4-dev is already the newest version (4.12.3+ds-2)`. 


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

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

Versions of packages cabal-install depends on:
ii  ghc   9.4.7-1
ii  libc6 2.37-12
ii  libffi8   3.4.4-1
ii  libgmp10  2:6.3.0+dfsg-2
ii  zlib1g1:1.2.13.dfsg-3

Versions of packages cabal-install recommends:
ii  curl  8.4.0-2
ii  wget  1.21.4-1+b1

cabal-install suggests no packages.

-- no debconf information

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

[Wookey]

On 2023-11-08 20:10 +0100, Martin Budaj wrote:
> On Tue, Nov 7, 2023 at 4:25 PM Wookey  wrote:
> 
> > It looks like moving to catch3 and adding:
> > target_link_libraries(test PRIVATE Catch2::Catch2WithMain)
> > in the test targets should do the trick.
> >
> 
> Hi,
> 
> as we still need to maintain Catch2 v2 API compatibility to run CI tests
> and builds on older Ubuntu images, we can't simply migrate to v3.

Who is building 'latest' Therion on old Ubuntu? And are they getting
their sources from the Debian unstable package? Or from Upstream?

> For now, I'll just enable using the bundled Catch2 instead of v3 installed
> in the system.

That's not the right approach for the Debian package, and this bug is about the 
debian package.
Debian unstable has catch 3 in it. We should use it, not an old bundled catch2 
copy.

Upstream builds and Ubuntu builds can do something different if need
be but that's not a good reason for the Debian package not to
DTRT. And in general I'd expect current Ubuntu to have catch3 too so
using the system version will be appropriate there too.

Wookey
-- 
Principal hats:  Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#1054919: kaccounts-providers: google authentication hang after username entry

[Nicholas D Steeves]

Hi,

I received a report from sney (in #debian-qt-kde on OFTC) that a
workaround is no longer necessary in either kaccounts-providers or
signon-ui.

Thus it sounds like this was a case #1 problem
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054919#24)

1. Google refuses to talk to Qt webkit/QtWebEngine that identifies
itself accurately.

and it appears that they've reverted the action that broke everyone's
access to their Google accounts.  This is the most correct solution and
the best possible outcome.

Alexis and Peter, would you please confirm that the workaround is no
longer necessary?  And please leave the bug open even if Google accounts
are working again, because the frequency of this breakage has been
mounting.

To everyone reading this: If user spoofing doesn't solve the next
incidence of breakage then that would indicate a separate issue, and
please file a separate bug in this case!

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#1015936: notmuch-vim: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1)

[James McCoy]

Control: tags -1 + patch

On Sun, Jul 24, 2022 at 02:43:29PM +0300, guriev...@ya.ru wrote:
> The Vim team decided to declare vim-addon-manager(1) deprecated. Please
> remove the vim-addon-manager package from the Depends list. We advise to
> switch to modern dh_vim-addon(1) if you use Debhelper.

Attached patch implements this.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
>From e036a14aea3a4da8e254779cf85a9accfe275a59 Mon Sep 17 00:00:00 2001
From: James McCoy 
Date: Wed, 8 Nov 2023 18:29:00 -0500
Subject: [PATCH] Convert notmuch-vim to Vim addon policy 2.0

The new Vim addon policy relies on Vim's native package functionality,
rather than the Debian-specific vim-addons tool.  This allows the addon
to be immediately available when the package is installed, rather than
requiring extra setup by the user.

* Install notmuch-vim to its own /usr/share/notmuch-vim directory, so
  the files are self-contained.
* Remove vim-addon-manager from notmuch-vim Depends
* Add ${vim-addon:Depends} to notmuch-vim Depends to ensure it has the
  required relationships on Vim/Neovim.
* Build-Depend on dh-sequence-vim-addon to automatically setup the
  required symlinks for Vim and Neovim to see the addon.

Signed-off-by: James McCoy 
---
 debian/control  | 3 ++-
 debian/notmuch-vim.dirs | 4 
 debian/notmuch-vim.install  | 5 +
 debian/notmuch-vim.neovim-addon | 1 +
 debian/notmuch-vim.vim-addon| 1 +
 debian/rules| 1 +
 6 files changed, 6 insertions(+), 9 deletions(-)
 delete mode 100644 debian/notmuch-vim.dirs
 create mode 12 debian/notmuch-vim.neovim-addon
 create mode 100644 debian/notmuch-vim.vim-addon

diff --git a/debian/control b/debian/control
index 135eb7ce..1866247a 100644
--- a/debian/control
+++ b/debian/control
@@ -14,6 +14,7 @@ Build-Depends:
  debhelper-compat (= 13),
  dh-elpa (>= 1.3),
  dh-python,
+ dh-sequence-vim-addon,
  desktop-file-utils,
  doxygen,
  dpkg-dev (>= 1.17.14),
@@ -208,9 +209,9 @@ Replaces:
 Depends:
  notmuch,
  ruby-notmuch,
- vim-addon-manager,
  vim-ruby,
  ${misc:Depends},
+ ${vim-addon:Depends},
 Recommends:
  ruby-mail,
 Description: thread-based email index, search and tagging (vim interface)
diff --git a/debian/notmuch-vim.dirs b/debian/notmuch-vim.dirs
deleted file mode 100644
index 2b531314..
--- a/debian/notmuch-vim.dirs
+++ /dev/null
@@ -1,4 +0,0 @@
-usr/share/vim/addons/doc
-usr/share/vim/addons/plugin
-usr/share/vim/addons/syntax
-usr/share/vim/registry
diff --git a/debian/notmuch-vim.install b/debian/notmuch-vim.install
index cf898738..08096d37 100644
--- a/debian/notmuch-vim.install
+++ b/debian/notmuch-vim.install
@@ -1,4 +1 @@
-vim/notmuch.txt usr/share/vim/addons/doc
-vim/notmuch.vim usr/share/vim/addons/plugin
-vim/notmuch.yaml usr/share/vim/registry
-vim/syntax/notmuch-*.vim usr/share/vim/addons/syntax
+/usr/share/notmuch-vim
diff --git a/debian/notmuch-vim.neovim-addon b/debian/notmuch-vim.neovim-addon
new file mode 12
index ..a576db7c
--- /dev/null
+++ b/debian/notmuch-vim.neovim-addon
@@ -0,0 +1 @@
+notmuch-vim.vim-addon
\ No newline at end of file
diff --git a/debian/notmuch-vim.vim-addon b/debian/notmuch-vim.vim-addon
new file mode 100644
index ..9c23ba18
--- /dev/null
+++ b/debian/notmuch-vim.vim-addon
@@ -0,0 +1 @@
+/usr/share/notmuch-vim notmuch
diff --git a/debian/rules b/debian/rules
index a77ffa15..ecf09abc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -37,4 +37,5 @@ override_dh_auto_install:
 	PYBUILD_NAME=notmuch dh_auto_install --buildsystem=pybuild --sourcedirectory bindings/python
 	PYBUILD_NAME=notmuch2 dh_auto_install --buildsystem=pybuild --sourcedirectory bindings/python-cffi
 	$(MAKE) -C contrib/notmuch-mutt DESTDIR=$(CURDIR)/debian/tmp install
+	$(MAKE) -C vim prefix=/usr/share/notmuch-vim DESTDIR=$(CURDIR)/debian/tmp install
 	dh_auto_install --sourcedirectory bindings/ruby
-- 
2.42.0

Bug#1055625: pyzoltan: FTBFS (not enough slots available)

[Santiago Vila]

Package: src:pyzoltan
Version: 1.0.1-5
Severity: important
Tags: ftbfs

Dear maintainer:

During a mass-rebuild of all packages in bookworm, this
package failed to build in this way:

[...]

  raise RuntimeError(msg)

E   RuntimeError: test geometric_partitioner.py failed with returncode 1

pyzoltan/tools/run_parallel_script.py:54: RuntimeError
- Captured stdout call -
running test: ['mpiexec', '-n', '2', '/usr/bin/python3.11', 
'/<>/.pybuild/cpython3_3.11_pyzoltan/build/pyzoltan/core/tests/geometric_partitioner.py']

--
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:

  /usr/bin/python3.11

Either request fewer slots for your application, or make more slots
available for use.
[...]

Apparently the package is assuming I have at least 2 CPUs,
but I have only one, and build-essential does not imply multi-core.


I tried to fix this by honoring parallel=n in DEB_BUILD_OPTIONS,
since that's the recommended way to support parallelism
when building Debian packages.

The result is in the attached patches, but they don't work.

When I use those patches, build with a single-cpu now works,
but build in my desktop PC, which has 6 cores (12 threads)
fails in this way:

---

pyzoltan/tools/run_parallel_script.py:56: RuntimeError
- Captured stdout call -
running test: ['mpiexec', '-n', '12', '/usr/bin/python3.11', 
'/<>/.pybuild/cpython3_3.11_pyzoltan/build/pyzoltan/core/tests/geometric_partitioner.py']

--
There are not enough slots available in the system to satisfy the 12
slots that were requested by the application:

---


Considering that the package takes less than one minute to build,
my proposal to fix this (for everybody) would be to just disable
parallelism. Honoring parallel=n in DEB_BUILD_OPTIONS makes
sense for big packages (or even medium-sized). For small packages
like this one, there is not a great saving.

To reproduce the problem please try GRUB_CMDLINE_LINUX="nr_cpus=1",
that's an extremely easy way to test it in a machine with a single CPU.

[ Note: I'd like to fix this in stable, and I will gladly care
about the stable upload, but once we know how to fix this properly
in trixie/sid ].

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,11 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 export USE_TRILINOS=1
 export ZOLTAN_INCLUDE=/usr/include/trilinos
 export ZOLTAN_LIBRARY=/usr/lib
-NPROCS?=2
+
+NPROCS = 1
+ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+  NPROCS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+endif
 export NPROCS
 
 export PYBUILD_NAME=pyzoltan
--- /dev/null
+++ b/debian/patches/0004-fix-nprocs.patch
@@ -0,0 +1,20 @@
+--- pyzoltan-1.0.1.orig/pyzoltan/tools/run_parallel_script.py
 pyzoltan-1.0.1/pyzoltan/tools/run_parallel_script.py
+@@ -4,6 +4,8 @@ from subprocess import Popen, PIPE
+ import sys
+ from threading import Timer
+ 
++import os
++nprocs = int(os.environ.get('NPROCS', '1'))
+ 
+ def get_directory(file):
+ return dirname(abspath(file))
+@@ -14,7 +16,7 @@ def kill_process(process):
+ process.kill()
+ 
+ 
+-def run(filename, args=None, nprocs=2, timeout=30.0, path=None):
++def run(filename, args=None, nprocs=nprocs, timeout=30.0, path=None):
+ """Run a python script with MPI or in serial (if nprocs=1).  Kill process
+ if it takes longer than the specified timeout.
+ 
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 0001-Fix-nprocs.patch
 0002-Package-data.patch
 0003-Spelling.patch
+0004-fix-nprocs.patch

Bug#967328: emu8051: depends on deprecated GTK 2

[Bastian Germann]

I have uploaded the suggestion as part of
https://salsa.debian.org/electronics-team/emu8051/-/tags/debian%2F2.0.1-3

Bug#1011317: dkms: spurious messages "Module build for kernel ... was skipped" for non-installed kernels

[Thorsten Glaser]

Package: dkms
Version: 2.8.4-3
Followup-For: Bug #1011317
X-Debbugs-Cc: t...@mirbsd.de

I’m also running into this:

Building for 4.19.0-18-amd64, 5.10.0-25-amd64 and 5.10.0-26-amd64
Module build for kernel 4.19.0-18-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.

This box was originally a buster and is now a bullseye; dkms seems
to have forgotten all but one of the previously installed buster
kernels. They have been properly purged on apt/dpkg level:

tglase@tglase-edge:~ $ dpkg -l | fgrep linux- | cut -c 1-$COLUMNS
ii  binutils-x86-64-linux-gnu   2.35.2-2
 amd64GNU
ii  linux-base  4.6 
 all  Lin
ii  linux-compiler-gcc-10-x86   5.10.197-1  
 amd64Com
ii  linux-headers-5.10.0-25-amd64   5.10.191-1  
 amd64Hea
ii  linux-headers-5.10.0-25-common  5.10.191-1  
 all  Com
ii  linux-headers-5.10.0-26-amd64   5.10.197-1  
 amd64Hea
ii  linux-headers-5.10.0-26-common  5.10.197-1  
 all  Com
ii  linux-headers-amd64 5.10.197-1  
 amd64Hea
ii  linux-image-5.10.0-25-amd64 5.10.191-1  
 amd64Lin
ii  linux-image-5.10.0-26-amd64 5.10.197-1  
 amd64Lin
ii  linux-image-amd64   5.10.197-1  
 amd64Lin
ii  linux-kbuild-5.10   5.10.197-1  
 amd64Kbu
ii  linux-libc-dev:amd645.10.197-1  
 amd64Lin
ii  linux-source-5.10   5.10.197-1  
 all  Lin



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

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

Versions of packages dkms depends on:
ii  build-essential  12.9
ii  coreutils8.32-4+b1
ii  dctrl-tools  2.24-3+b1
ii  dpkg-dev 1.20.13
ii  gcc [c-compiler] 4:10.2.1-1
ii  gcc-10 [c-compiler]  10.2.1-6
ii  kmod 28-1
ii  lsb-release  11.1.0
ii  make 4.3-4.1
ii  patch2.7.6-7

Versions of packages dkms recommends:
ii  fakeroot 1.25.3-1.1
ii  linux-headers-amd64 [linux-headers-generic]  5.10.197-1
ii  sudo 1.9.5p2-3+deb11u1

Versions of packages dkms suggests:
ii  e2fsprogs  1.46.2-2
ii  menu   2.1.48

-- Configuration Files:
/etc/dkms/framework.conf changed:
autoinstall_all_kernels=1


-- no debconf information

Bug#1055624: viking: Segmentation fault when quitting viking

[Vincent Lefevre]

Package: viking
Version: 1.10-2
Severity: important

I got a segmentation fault when I quit viking:

[...]
(viking:45727): GLib-GObject-WARNING **: 00:24:41.116: invalid unclassed 
pointer in cast to 'VikLayer'

(viking:45727): GLib-GObject-WARNING **: 00:24:41.116: invalid unclassed 
pointer in cast to 'GtkWidget'

(viking:45727): Gtk-CRITICAL **: 00:24:41.116: gtk_widget_get_toplevel: 
assertion 'GTK_IS_WIDGET (widget)' failed
zsh: segmentation fault (core dumped)  viking velov-7008-7031-8.gpx

In gdb:

[...]
Core was generated by `viking velov-7008-7031-8.gpx'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  unlink_chunk (p=p@entry=0x55e7b438b860, av=0x7f011f06fc60 )
at ./malloc/malloc.c:1628
1628./malloc/malloc.c: No such file or directory.
[Current thread is 1 (Thread 0x7f011c3d5180 (LWP 45727))]

I'ved attached the full backtrace.

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

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

Versions of packages viking depends on:
ii  gpsbabel 1.8.0+ds-5
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.36-9+deb12u3
ii  libcairo21.16.0-7
ii  libcurl3-gnutls  7.88.1-10+deb12u4
ii  libexpat12.5.0-1
ii  libgcc-s113.2.0-6
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgeoclue-2-0   2.6.0-2
ii  libgexiv2-2  0.14.0-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgps28 3.22-4.1+b1
ii  libgtk-3-0   3.24.38-2~deb12u1
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmagic11:5.44-3
ii  libmapnik3.1 3.1.0+ds-3+b1
ii  libnettle8   3.8.1-2
ii  liboauth01.0.3-5
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libsqlite3-0 3.40.1-2
ii  libstdc++6   13.2.0-6
ii  libx11-6 2:1.8.7-1
ii  libzip4  1.7.3-1+b1
ii  yelp 42.2-1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages viking recommends:
ii  expect [expect-dev]  5.45.4-2+b1

Versions of packages viking suggests:
pn  gpsd  

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Thread 5 (Thread 0x7f010b1fe6c0 (LWP 45764)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f0120fe67ec in g_mutex_lock_slowpath (mutex=0x55e7b438b870) at 
../../../glib/gthread-posix.c:1494
#2  0x55e7b393d515 in  ()
#3  0x55e7b393fac1 in  ()
#4  0x55e7b3937dcc in  ()
#5  0x7f0120fbd6ca in g_thread_pool_thread_proxy (data=) at 
../../../glib/gthreadpool.c:352
task = 0x55e7b477aed0
pool = 0x55e7b4371430
#6  0x7f0120fbccfd in g_thread_proxy (data=0x55e7b44cacc0) at 
../../../glib/gthread.c:831
thread = 0x55e7b44cacc0
__func__ = "g_thread_proxy"
#7  0x7f011ef26044 in start_thread (arg=) at 
./nptl/pthread_create.c:442
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139642458334912, 
-6213794846092949282, -216, 11, 140730138625536, 139642449944576, 
6324809512385120478, 6324768457031682270}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
#8  0x7f011efa661c in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 4 (Thread 0x7f0119a116c0 (LWP 45729)):
#0  0x7f011ef9905f in __GI___poll (fds=0x55e7b42bfa50, nfds=2, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1  0x7f0120f929ae in g_main_context_poll (priority=, 
n_fds=2, fds=0x55e7b42bfa50, timeout=, context=0x55e7b42bdc00) 
at ../../../glib/gmain.c:4553
ret = 
errsv = 
poll_func = 0x7f0120fa2150 
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 2
allocated_nfds = 2
fds = 0x55e7b42bfa50
#2  g_main_context_iterate (context=0x55e7b42bdc00, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4243
max_priority = 2147483647
timeout = -1
some_ready = 
nfds = 2
allocated_nfds = 2
fds = 0x55e7b42bfa50
#3  0x7f0120f92cef in g_main_loop_run (loop=0x55e7b42bdcf0) at 
../../../glib/gmain.c:4448
__func__ = "g_main_loop_run"
#4  0x7f01211ed8f6 in gdbus_shared_thread_func (user_data=0x55e7b42bdbd0) 
at 

Bug#967386: gexec: depends on deprecated GTK 2

[Bastian Germann]

Hi Seunghun,

I see you have ported gexec to GTK3. Will you release and import it to Debian 
soon?

Thanks,
Bastian

Bug#1055510: Best way to coordinate this fix

[Simó Albert i Beltran]

On Thu, Nov 9 2023 at 12:13:25 AM +01:00:00, Simó Albert i Beltran 
 wrote:
Please take a look at 
https://salsa.debian.org/debian/molly-guard/-/commit/c1120c0c3602955abe02d4d810985ad13d02cdba




Sorry, I meant 
https://salsa.debian.org/debian/molly-guard/-/commit/c1120c0c3602955abe02d4d810985ad13d02cdba#note_440065

Bug#1055623: ruby-neovim: Please Provide vim-ruby

[James McCoy]

Package: ruby-neovim
Version: 0.9.1-2
Severity: wishlist

Vim has various language interfaces and Provides a vim- for the
binary packages that support the respective languages.

Since neovim externalized that to providers, it's helpful for neovim
users if the external providers Provide the vim- name (c.f,
python3-pynvim Provides: vim-python3).


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

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

Versions of packages ruby-neovim depends on:
ii  neovim   0.7.2-8
ii  ruby 1:3.1
pn  ruby-msgpack 
pn  ruby-multi-json  

ruby-neovim recommends no packages.

ruby-neovim suggests no packages.

Bug#1055510: Best way to coordinate this fix

[Simó Albert i Beltran]

Please take a look at 
https://salsa.debian.org/debian/molly-guard/-/commit/c1120c0c3602955abe02d4d810985ad13d02cdba

Bug#1055622: rust-gdk-pixbuf-sys: FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory

[Simon McVittie]

Source: rust-gdk-pixbuf-sys
Version: 0.18.0-2
Severity: important

While testing a proposed update for gobject-introspection I found that
rust-gdk-pixbuf-sys FTBFS when built in sbuild with the nocheck build
profile:

> Command: dpkg-buildpackage --sanitize-env -Pnocheck -us -uc -B -rfakeroot
...
>debian/rules execute_before_dh_auto_build
> make[1]: Entering directory '/<>'
> cp /usr/share/gir-1.0/GLib-2.0.gir /<>
> cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory

Either libgirepository1.0-dev should not be , or that cp command
needs to be skipped when built with nocheck.

(Other GObject-Introspection-adjacent Rust libraries might have the same
issue, I haven't attempted to rebuild all of them.)

Thanks,
smcv

Bug#1055621: RFA: pyjunitxml -- PyUnit extension for reporting in JUnit compatible XML

[Bastian Germann]

Package: wnpp

Hereby, I request a new maintainer to take over pyjunitxml.
The package is in a good state, low-maintenance and I do no longer use it.

Bug#1055620: RFA: pytest-dependency -- Manages dependencies of pytest test cases

[Bastian Germann]

Package: wnpp

Hereby, I request a new maintainer to take over pytest-dependency.
The package is in a good state, low-maintenance and I do no longer use it.

Bug#1055619: RFA: python-inotify -- Python inotify bindings

[Bastian Germann]

Package: wnpp

Hereby, I request a new maintainer to take over python-inotify.
The package is in a good state, very low-maintenance and I do no longer use it.

Bug#1055601: darktable: Segfault in first run after system hang

[David Bremner]

Control: tag -1 wontfix

Greg Schmidt  writes:

> Package: darktable
> Version: 4.4.2-1+b1
> Severity: normal
> X-Debbugs-Cc: g...@desk1.attlocal.net
>
> Dear Maintainer,
>
> I was using darktable when my system hung. I had to reboot to recover. After 
> the reboot I started darktable and 
> it segfaulted. A backtrace was created which implicated dlopen. It was 
> attempting to load "libMesaOpenCL.so.1".
> A subsequent start of darktable was normal. 

Hi Greg;

This looks OpenCL related. I don't have a working OpenCL setup, so I
can't help you there (even if the problem was reproducible). If you find
a way to reproduce it, feel free to report a bug to upstream darktable
on github including the output of darktable -d common.

Bug#1055618: RFA: python-libconf -- Python libconfig implementation

[Bastian Germann]

Package: wnpp

Hereby, I request a new maintainer to take over python-libconf.
The package is in a good state, very low-maintenance and I do no longer use it.

Bug#1055531: apt-listbugs: Fails with Input/output error when current working directory is not available

[Francesco Poli]

Control: affects -1 apt-listbugs

[...]
> On Wed, 8 Nov 2023 23:07:41 +0100 Francesco Poli wrote:
[...]
> The above command should merge the two bug reports.

I forgot to re-add the affects tag...

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpQfznx_cuaG.pgp
Description: PGP signature

Bug#1055531: apt-listbugs: Fails with Input/output error when current working directory is not available

[Francesco Poli]

Control: forcemerge 943714 -1


On Wed, 8 Nov 2023 23:07:41 +0100 Francesco Poli wrote:

[...]
> It's probably reasonable to merge these two bug reports...

The above command should merge the two bug reports.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpFaVdxrV10_.pgp
Description: PGP signature

Bug#1055617: RFA: python-vlc -- VLC Python bindings

[Bastian Germann]

Package: wnpp

Hereby, I request a new maintainer to take over python-vlc.
The package is in a good state, very low-maintenance and I do no longer use it.

Bug#1055531: apt-listbugs: Fails with Input/output error when current working directory is not available

[Francesco Poli]

Control: reassign -1 ruby-gettext 3.3.3-2
Control: affects -1 apt-listbugs


On Tue, 07 Nov 2023 20:49:03 +0100 Jochen Spieker wrote:

> Package: apt-listbugs
> Version: 0.1.41
> Severity: minor
> 
> Dear Maintainer,

Hello Jochen,
thanks for your bug report.

>
> on my laptop running sid I am often using an NFS mount that is only available
> when I am at home.
> 
> Today I had the NFS filesystem mounted when I suspended my laptop, moved it
> somewhere else and woke it up again. My shell still had the NFS (unavailable)
> mount as the current working directory. Then I ran 'apt upgrade'.

An unusual use case, although an interesting one...

> The upgrade failed like this:
[...]
> :220:in `glob': Input/output error - ./locale (Errno::EIO)
> from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:64:in `block in 
> default_path_rules'
> from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:63:in `select'
> from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:63:in 
> `default_path_rules'
> from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:80:in 
> `initialize'
> from /usr/lib/ruby/vendor_ruby/gettext/text_domain.rb:52:in `new'
> from /usr/lib/ruby/vendor_ruby/gettext/text_domain.rb:52:in 
> `initialize'
> from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:226:in 
> `new'
> from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:226:in 
> `create_or_find_text_domain'
> from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:71:in 
> `bind_to'
> from /usr/lib/ruby/vendor_ruby/gettext.rb:73:in `bindtextdomain_to'
> from /usr/lib/ruby/vendor_ruby/gettext.rb:54:in `bindtextdomain'
> from /usr/bin/apt-listbugs:428:in `'
> E: Sub-process /usr/bin/apt-listbugs apt returned an error code (1)
> E: Failure running script /usr/bin/apt-listbugs apt

It seems that a simple call to  GetText::bindtextdomain()  caused a
search inside a ./locale directory, from within the ruby-gettext
library, but ./ was not accessible, since it belonged to a
non-responding NFS mount.
Hence the I/O error.

> 
> 
> It would be great if a problem with the current working directory could be
> handled more gracefully. It took me a few minutes to find out what the 
> problem was.

I agree that this kind of problems could be handled better, even though
we are talking about a quite unusual situation.

However, apt-listbugs is just making ruby-gettext library calls in the
correct manner (or in what I believe is the correct manner).
I think it is the responsibility of the library to make sure that
unforeseen filesystem accessibility issues are handled gracefully.

I am therefore reassigning your bug report to package 'ruby-gettext': I
hope it will be handled there, possibly by forwarding it upstream.
Actually, I see that there's already another bug report about the same
issue: [#943714]

[#943714]: 

It's probably reasonable to merge these two bug reports...

> 
> Thanks,
> Jochen

Thanks to you, bye!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpd7_3gPP8s6.pgp
Description: PGP signature

Bug#1042521: polymake: FTBFS with Perl 5.38: ‘Perl_ck_fun’ was not declared in this scope

[David Bremner]

David Bremner  writes:

> Benjamin Lorenz  writes:
> Dear Benjamin;
>
> Thanks for letting me know. I will try to update the Debian package
> within a week or so.
>
> David

I didn't have a chance to investigate so far, but I am seeing a test
failure with Polymake 4.11 building with Perl 5.36. I will try to build
with 5.38 and report a proper build log.

*** Failed tests ***

/<>/apps/polytope/rules/slack_ideal.rules:29: testcase 1
expected: regular return
 got: EXCEPTION: no more rules available to compute 'GENERATORS

Bug#1007465: vanessa-socket: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru vanessa-socket-0.0.13/debian/changelog 
vanessa-socket-0.0.13/debian/changelog
--- vanessa-socket-0.0.13/debian/changelog  2015-06-14 06:53:27.0 
+0200
+++ vanessa-socket-0.0.13/debian/changelog  2023-11-08 22:53:54.0 
+0100
@@ -1,3 +1,14 @@
+vanessa-socket (0.0.13-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Convert to source format 3.0 (Closes: #953993, #1007465)
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Don't configure via autogen.sh,
+let dh_auto_configure do it (Closes: #990438)
+
+ -- Bastian Germann   Wed, 08 Nov 2023 22:53:54 +0100
+
 vanessa-socket (0.0.13-1) unstable; urgency=medium
 
   * New Upstream
diff -Nru vanessa-socket-0.0.13/debian/patches/auotogen.patch 
vanessa-socket-0.0.13/debian/patches/auotogen.patch
--- vanessa-socket-0.0.13/debian/patches/auotogen.patch 1970-01-01 
01:00:00.0 +0100
+++ vanessa-socket-0.0.13/debian/patches/auotogen.patch 2023-11-08 
22:53:54.0 +0100
@@ -0,0 +1,15 @@
+Description: autogen: Test for NO_CONFIGURE variable
+Author: Helmut Grohne 
+Bug-Debian: https://bugs.debian.org/990438
+---
+--- vanessa-socket-0.0.13.orig/autogen.sh
 vanessa-socket-0.0.13/autogen.sh
+@@ -55,6 +55,8 @@ libtoolize --ltdl
+ automake --add-missing $am_opt
+ cd $THEDIR
+ 
++test -n "$NO_CONFIGURE" && exit 0
++
+ $srcdir/configure "$@" || exit $?
+ 
+ echo 
diff -Nru vanessa-socket-0.0.13/debian/patches/series 
vanessa-socket-0.0.13/debian/patches/series
--- vanessa-socket-0.0.13/debian/patches/series 1970-01-01 01:00:00.0 
+0100
+++ vanessa-socket-0.0.13/debian/patches/series 2023-11-08 22:53:54.0 
+0100
@@ -0,0 +1 @@
+auotogen.patch
diff -Nru vanessa-socket-0.0.13/debian/rules vanessa-socket-0.0.13/debian/rules
--- vanessa-socket-0.0.13/debian/rules  2014-09-11 03:37:45.0 +0200
+++ vanessa-socket-0.0.13/debian/rules  2023-11-08 22:53:54.0 +0100
@@ -3,7 +3,6 @@
 # GNU copyright 1997 to 1999 by Joey Hess.
 
 pwd:=$(shell pwd)
-cfg:=--prefix=/usr --mandir=/usr/share/man
 
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
@@ -15,7 +14,8 @@
dh_testdir
dh_autoreconf
 
-   test -x autogen.sh && ./autogen.sh $(cfg) || ./configure $(cfg)
+   test -x autogen.sh && NO_CONFIGURE=1 ./autogen.sh
+   dh_auto_configure
$(MAKE) V=1
touch build-stamp
 
diff -Nru vanessa-socket-0.0.13/debian/source/format 
vanessa-socket-0.0.13/debian/source/format
--- vanessa-socket-0.0.13/debian/source/format  1970-01-01 01:00:00.0 
+0100
+++ vanessa-socket-0.0.13/debian/source/format  2023-11-08 22:53:54.0 
+0100
@@ -0,0 +1 @@
+3.0 (quilt)

Bug#1055534: sq-wot should stay a bit longer

[Holger Levsen]

hi,

in https://gitlab.com/sequoia-pgp/sequoia-wot/-/issues/50
Neal H. Walfield wrote 5 days ago:

begin quote
I think that long term, we should drop sq-wot, the CLI. Right now, it has one 
advance over the sq CLI: it implements gpg's trust model (--gpg-ownertrust). 
It's unclear whether we want to add that functionality to sq, and if so how to 
expose it. One possibility would be to add a gpg variant to the web of trust 
library (see #49) , and then have an option in sq to use an ownertrust db. But, 
I'm not so excited about that.
 end  quote


-- 
cheers,
Holger

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

It ain't no revolution, just because you can dance to it.


signature.asc
Description: PGP signature

Bug#1055616: ansible-core: ansible.builtin.setup does not include facts from facter.

[andrew bezella]

Package: ansible-core
Version: 2.14.3-1
Severity: normal

Dear Maintainer,

i installed ansible-core and facter 4.3.0-2 in bookworm.  when testing
i found that the facts from facter were not being included by the
setup module:

% ansible -b localhost -m ansible.builtin.setup -a 'filter=facter_*'
[WARNING]: No inventory was parsed, only implicit localhost is available
localhost | SUCCESS => {
"ansible_facts": {},
"changed": false
}

this issue has appeared upstream and was resolved by:
setup module, retry facter to handle --puppet errors by bcoca · Pull Request 
#80645 · ansible/ansible · GitHub
https://github.com/ansible/ansible/pull/80645

i was eventually able to build an updated version of bookworm's
ansible-core .deb including commit id 4b0d014.  this task was made
more difficult by the current FTBFS status of ansible-core but the
patch allowed ansible.builtin.setup to include facts from facter:

% ansible -b localhost -m ansible.builtin.setup -a 'filter=facter_*'
[WARNING]: No inventory was parsed, only implicit localhost is available
localhost | SUCCESS => {
"ansible_facts": {
"facter_disks": {
"sda": {
[...]
"facter_timezone": "UTC",
"facter_virtual": "physical"
},
"changed": false
}

thanks in advance for addressing this.

andy


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

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

Versions of packages ansible-core depends on:
ii  openssh-client1:9.2p1-2+deb12u1
ii  python3   3.11.2-1+b1
ii  python3-cryptography  38.0.4-3
ii  python3-distutils 3.11.2-3
ii  python3-dnspython 2.3.0-1
ii  python3-httplib2  0.20.4-3
ii  python3-jinja23.1.2-1
ii  python3-netaddr   0.8.0-2
ii  python3-packaging 23.0-1
ii  python3-paramiko  2.12.0-2
ii  python3-pycryptodome  3.11.0+dfsg1-4
ii  python3-resolvelib0.9.0-2
ii  python3-yaml  6.0-3+b2

Versions of packages ansible-core recommends:
ii  ansible  7.3.0+dfsg-1
pn  python3-argcomplete  
pn  python3-jmespath 
pn  python3-kerberos 
pn  python3-libcloud 
ii  python3-selinux  3.4-1+b6
pn  python3-winrm
pn  python3-xmltodict

Versions of packages ansible-core suggests:
pn  cowsay   
pn  sshpass  

-- no debconf information
>From 4b0d014d5840333457bd118c5fae5cf58325a877 Mon Sep 17 00:00:00 2001
From: Brian Coca 
Date: Mon, 8 May 2023 16:53:53 -0400
Subject: [PATCH] setup module, retry facter to handle --puppet errors (#80645)

* setup module, retry facter to handle --puppet errors

facter versions have changed how they deal with the --puppet flag
when puppet is not present, most versions will just ignore it and not error,
but initial versions of facter 4 changed the behaviour (later reverted).

fixes #80496
---
 changelogs/fragments/setup_facter_fix.yml |  2 ++
 .../module_utils/facts/other/facter.py| 23 +++
 2 files changed, 10 insertions(+), 15 deletions(-)
 create mode 100644 changelogs/fragments/setup_facter_fix.yml

diff --git a/changelogs/fragments/setup_facter_fix.yml 
b/changelogs/fragments/setup_facter_fix.yml
new file mode 100644
index 00..78a6b005a4abf2
--- /dev/null
+++ b/changelogs/fragments/setup_facter_fix.yml
@@ -0,0 +1,2 @@
+bugfixes:
+  - setup module (fact gathering) will now try to be smarter about different 
versions of facter emitting error when --puppet flag is used w/o puppet.
diff --git a/lib/ansible/module_utils/facts/other/facter.py 
b/lib/ansible/module_utils/facts/other/facter.py
index 3f83999d419d5c..063065251dd36e 100644
--- a/lib/ansible/module_utils/facts/other/facter.py
+++ b/lib/ansible/module_utils/facts/other/facter.py
@@ -1,17 +1,5 @@
-# This file is part of Ansible
-#
-# Ansible is free software: you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation, either version 3 of the License, or
-# (at your option) any later version.
-#
-# Ansible is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with Ansible.  If not, see .
+# Copyright (c) 2023 Ansible Project
+# GNU General Public License v3.0+ (see COPYING or 
https://www.gnu.org/licenses/gpl-3.0.txt)
 
 from __future__ import (absolute_import, division, print_function)
 

Bug#1055615: RFP: system76-ectool -- System76 Open Source Embedded Controller tool

[Simon Josefsson]

Package: wnpp
Severity: wishlist

* Package name: system76-ectool
  Upstream Author : System76 / Jeremy Soller
* URL : https://github.com/system76/ec
* License : MIT
  Programming Lang: Rust
  Description : firmware tool for System76 Open Source Embedded Controller

The system76_ectool is used to interact with the System76 Open Source
Embedded Controller firmware.  The firmware can be used on laptops
from several vendors including System76, Clevo, NovaCustom, etc.

I tried to package it, but I don't know rust.  Following the packaging
tutorial ended when it depended on the hidapi-1 crate, where Debian only
has hidapi-2.  I opened an upstream bug about upgrading to hidapi 2 at
https://github.com/system76/ec/issues/419 and I also tried to package
hidapi-1 but I never managed to get it to build due to some
libusb-related problem.  I'm sure someone with more rust packaging
skills could work this out more easily, and I'm happy to test resulting
binaries since my laptop has this EC firwmare.

/Simon


signature.asc
Description: PGP signature

Bug#1055614: whereami: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: whereami
Version: 0.3.34-0.5
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1007418: xtide-coastline: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru xtide-coastline-20020202/debian/changelog 
xtide-coastline-20020202/debian/changelog
--- xtide-coastline-20020202/debian/changelog   2023-11-08 22:24:23.0 
+0100
+++ xtide-coastline-20020202/debian/changelog   2023-11-08 22:20:38.0 
+0100
@@ -1,3 +1,10 @@
+xtide-coastline (20020202-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. (Closes: #1007418)
+
+ -- Bastian Germann   Wed, 08 Nov 2023 22:20:38 +0100
+
 xtide-coastline (20020202-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xtide-coastline-20020202/debian/source/format 
xtide-coastline-20020202/debian/source/format
--- xtide-coastline-20020202/debian/source/format   1970-01-01 
01:00:00.0 +0100
+++ xtide-coastline-20020202/debian/source/format   2023-11-08 
22:20:30.0 +0100
@@ -0,0 +1 @@
+3.0 (quilt)

Bug#1053457: Looks like BIOS vs UEFI boot

[Roland Clobus]

Hello Emanuele,

On 08/11/2023 22:00, Emanuele Rocca wrote:

Yeah 20230502 is the version I'm using too.

I can reproduce on all systems I have available, including my amd64
workstation and my arm64 Macbook M1. However, the issue is *not*
reproducible on a VM created with debvm-create.

One of the differences seem to be efivars support. Are you by any chance
running the commands in a VM or more in general on a system without
efivars? What's the output of the following?

  sudo dmesg | grep efivars:


You may have found the crucial difference. I'm running on a sid system 
which is booted via BIOS, not via UEFI. So I don't have efivars mounted 
on the host system, and therefore there are no attempts inside the 
chroot to mount or unmount efivarsfs.


With kind regards,
Roland Clobus


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055613: Configuration files hidden in /usr/lib/

[Nathael Pajani]

Package: cron-daemon-common
Version: 3.0pl1-178

This package (among others, I just discovered) places configuration files in /usr/lib, 
which is a place for "binary libraries", not configuration text files.

Configuration text files should be in /etc/, and non binary files in /usr/share/

Concerned files are :
/usr/lib/sysusers.d/cron-daemon-common.conf
/usr/lib/tmpfiles.d/cron-daemon-common.conf

Thanks.

--
Nathaël PAJANI - ED3L - Techno-Innov
Internet : http://www.ed3l.fr - http://www.techno-innov.fr

Bug#1055611: bookworm-pu: package oscrypto/1.3.0-1+deb12u1

[Santiago Vila]

Note: I should also include some changes in debian/salsa-ci.yml and gbp.conf.
The final debdiff may differ slightly in that minor detail only.

Thanks.

Bug#1055612: libjs-bootbox: CVE-2023-46998

[Salvatore Bonaccorso]

Source: libjs-bootbox
Version: 5.5.3~ds-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/bootboxjs/bootbox/issues/661
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libjs-bootbox.

CVE-2023-46998[0]:
| Cross Site Scripting vulnerability in BootBox Bootbox.js v.3.2
| through 6.0 allows a remote attacker to execute arbitrary code via a
| crafted payload to alert(), confirm(), prompt() functions.

At time of writing, there is no upstream fix for this issue. Cf. as
well [1].

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-46998
https://www.cve.org/CVERecord?id=CVE-2023-46998
[1] https://github.com/bootboxjs/bootbox/issues/661

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1055611: bookworm-pu: package oscrypto/1.3.0-1+deb12u1

[Santiago Vila]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: oscry...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:oscrypto

[ Reason ]
This upload fixes FTBFS bug #1033822 in stable.
It fixes also the autopkgtests, which are currently broken in stable.

[ Impact ]
The package currently fails to build in stable.

[ Tests ]
I've verified that the package builds again with the changes.
The fixed autopkgtests are already working ok in trixie/sid.

[ Risks ]
Risk is low, the patches are taken from upstream.

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

[ Changes ]
Fix OpenSSL version parsing.
Fix autopkgtests by switching to autopkgtest-pkg-pybuild.

[ Other info ]
- I'll await for approval before upload.
- These changes would actually make 1.3.0-1+deb12u1
identical to version 1.3.0-4 currently in trixie/sid,
except for the Standards-Version control field.diff -Nru oscrypto-1.3.0/debian/changelog oscrypto-1.3.0/debian/changelog
--- oscrypto-1.3.0/debian/changelog 2022-07-04 08:53:23.0 +0200
+++ oscrypto-1.3.0/debian/changelog 2023-11-08 21:38:44.0 +0100
@@ -1,3 +1,15 @@
+oscrypto (1.3.0-1+deb12u1) bookworm; urgency=medium
+
+  * Team upload.
+  [ Jochen Sprickerhof ]
+  * Fix autopkgtest by switching to autopkgtest-pkg-pybuild. Closes: #1033822.
+  [ Bastian Germann ]
+  * Fix OpenSSL version parsing, take 1.
+  [ Arnaud Rebillout ]
+  * Fix OpenSSL version parsing, take 2. Closes: #1055598.
+
+ -- Santiago Vila   Wed, 08 Nov 2023 21:38:44 +0100
+
 oscrypto (1.3.0-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru oscrypto-1.3.0/debian/control oscrypto-1.3.0/debian/control
--- oscrypto-1.3.0/debian/control   2022-07-04 08:53:23.0 +0200
+++ oscrypto-1.3.0/debian/control   2023-11-08 21:36:27.0 +0100
@@ -17,6 +17,7 @@
 Vcs-Browser: https://salsa.debian.org/python-team/packages/oscrypto
 Vcs-Git: https://salsa.debian.org/python-team/packages/oscrypto.git
 Rules-Requires-Root: no
+Testsuite: autopkgtest-pkg-pybuild
 
 Package: python3-oscrypto
 Architecture: all
diff -Nru oscrypto-1.3.0/debian/patches/libcrypto_ctypes_regex.patch 
oscrypto-1.3.0/debian/patches/libcrypto_ctypes_regex.patch
--- oscrypto-1.3.0/debian/patches/libcrypto_ctypes_regex.patch  1970-01-01 
01:00:00.0 +0100
+++ oscrypto-1.3.0/debian/patches/libcrypto_ctypes_regex.patch  2023-11-08 
21:36:39.0 +0100
@@ -0,0 +1,22 @@
+Origin: https://github.com/wbond/oscrypto/pull/76
+From: Martin Journois 
+Date: Thu, 10 Aug 2023 13:58:14 +0200
+Subject: MJ: Add fix suggested by @vcunat on _libcrypto_ctypes regex
+
+---
+ oscrypto/_openssl/_libcrypto_ctypes.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/oscrypto/_openssl/_libcrypto_ctypes.py 
b/oscrypto/_openssl/_libcrypto_ctypes.py
+index e33ebbc..9cb294a 100644
+--- a/oscrypto/_openssl/_libcrypto_ctypes.py
 b/oscrypto/_openssl/_libcrypto_ctypes.py
+@@ -40,7 +40,7 @@
+ 
+ is_libressl = 'LibreSSL' in version_string
+ 
+-version_match = re.search('\\b(\\d\\.\\d\\.\\d[a-z]*)\\b', version_string)
++version_match = re.search('\\b(\\d\\.\\d\\.\\d+[a-z]*)\\b', version_string)
+ if not version_match:
+ version_match = re.search('(?<=LibreSSL )(\\d\\.\\d(\\.\\d)?)\\b', 
version_string)
+ if not version_match:
diff -Nru 
oscrypto-1.3.0/debian/patches/Make_OpenSSL_version_regexes_more_robust.patch 
oscrypto-1.3.0/debian/patches/Make_OpenSSL_version_regexes_more_robust.patch
--- 
oscrypto-1.3.0/debian/patches/Make_OpenSSL_version_regexes_more_robust.patch
1970-01-01 01:00:00.0 +0100
+++ 
oscrypto-1.3.0/debian/patches/Make_OpenSSL_version_regexes_more_robust.patch
2023-11-08 21:36:39.0 +0100
@@ -0,0 +1,52 @@
+Origin: 
https://github.com/wbond/oscrypto/commit/d5f3437ed24257895ae1edd9e503cfb352e635a8
+From: wbond 
+Date: Thu, 17 Aug 2023 07:06:19 -0400
+Subject: Make OpenSSL version regexes more robust
+
+---
+ oscrypto/_openssl/_libcrypto_cffi.py   | 6 +++---
+ oscrypto/_openssl/_libcrypto_ctypes.py | 6 +++---
+ 2 files changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/oscrypto/_openssl/_libcrypto_cffi.py 
b/oscrypto/_openssl/_libcrypto_cffi.py
+index 14eb576..6f901ea 100644
+--- a/oscrypto/_openssl/_libcrypto_cffi.py
 b/oscrypto/_openssl/_libcrypto_cffi.py
+@@ -37,13 +37,13 @@
+ 
+ is_libressl = 'LibreSSL' in version_string
+ 
+-version_match = re.search('\\b(\\d\\.\\d\\.\\d+[a-z]*)\\b', version_string)
++version_match = re.search('\\b(\\d+\\.\\d+\\.\\d+[a-z]*)\\b', version_string)
+ if not version_match:
+-version_match = re.search('(?<=LibreSSL )(\\d\\.\\d(\\.\\d)?)\\b', 
version_string)
++version_match = re.search('(?<=LibreSSL )(\\d+\\.\\d+(\\.\\d+)?)\\b', 
version_string)
+ if not version_match:

Bug#1055510: Best way to coordinate this fix

[Francois Marier]

If anybody would like to double-check (or test) the package I've prepared,
it's in salsa right now.

Francois

Bug#1053457: More info needed, cannot reproduce

[Emanuele Rocca]

Hi Roland!

On 2023-11-08 06:50, Roland Clobus wrote:
> I've run the commands that you have provided, and am unable to reproduce
> your case.
> 
> lb config --distribution sid --updates false --archive-areas 'main
> non-free-firmware' --bootloaders grub-efi
> echo live-task-lxde > config/package-lists/desktop.list.chroot
> lb build --debug
> 
> My last line in the output is:
> P: Build completed successfully
> 
> I'm running (lb --version) 20230502 on sid, all commands have run as root.

Yeah 20230502 is the version I'm using too.

I can reproduce on all systems I have available, including my amd64
workstation and my arm64 Macbook M1. However, the issue is *not*
reproducible on a VM created with debvm-create.

One of the differences seem to be efivars support. Are you by any chance
running the commands in a VM or more in general on a system without
efivars? What's the output of the following?

 sudo dmesg | grep efivars:

I can reproduce on systems where the output looks like:

[0.035071] efivars: Registered efivars operations

Whereas on the VM (issue NOT reproducible) the command does not give any
output.

  Emanuele

Bug#967779: tome: depends on deprecated GTK 2

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.diff -Nru tome-2.41-ah~0.git.20200131/CMakeLists.txt 
tome-2.41-ah~0.git.20200131/CMakeLists.txt
--- tome-2.41-ah~0.git.20200131/CMakeLists.txt  2023-11-08 21:43:48.0 
+0100
+++ tome-2.41-ah~0.git.20200131/CMakeLists.txt  2020-02-02 13:00:22.0 
+0100
@@ -28,7 +28,7 @@
 #
 SET(CMAKE_C_FLAGS   "${CMAKE_C_FLAGS} ${COMMON_COMPILER_FLAGS}")
 SET(CMAKE_C_FLAGS_RELEASE   "-O2")
-SET(CMAKE_C_FLAGS_DEBUG "-O0 -g")
+SET(CMAKE_C_FLAGS_DEBUG "-O0 -g ${SANITIZER_FLAGS}")
 
 #
 # C++ Compiler Flags
@@ -36,7 +36,7 @@
 SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${COMMON_COMPILER_FLAGS}")
 SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DJSONCONS_NO_DEPRECATED")
 SET(CMAKE_CXX_FLAGS_RELEASE "-O2")
-SET(CMAKE_CXX_FLAGS_DEBUG   "-O0 -g -D_GLIBCXX_DEBUG 
-D_GLIBCXX_DEBUG_PEDANTIC")
+SET(CMAKE_CXX_FLAGS_DEBUG   "-O0 -g ${SANITIZER_FLAGS} -D_GLIBCXX_DEBUG 
-D_GLIBCXX_DEBUG_PEDANTIC")
 
 #
 # GCC Flags
@@ -100,7 +100,7 @@
 # Set the path for loading the library bits.
 #
 IF(SYSTEM_INSTALL)
-  SET(DEFAULT_PATH "/var/games/tome")
+  SET(DEFAULT_PATH "${CMAKE_INSTALL_PREFIX}/lib/tome")
 ELSE()
   SET(DEFAULT_PATH "./lib")
 ENDIF()
diff -Nru tome-2.41-ah~0.git.20200131/debian/changelog 
tome-2.41-ah~0.git.20200131/debian/changelog
--- tome-2.41-ah~0.git.20200131/debian/changelog2023-11-08 
21:43:48.0 +0100
+++ tome-2.41-ah~0.git.20200131/debian/changelog2023-11-08 
21:30:58.0 +0100
@@ -1,3 +1,11 @@
+tome (2.41-ah~0.git.20200131-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop GTK 2 binary (Closes: #967779).
+  * Convert to source format 3.0 (Closes: #1055609).
+
+ -- Bastian Germann   Wed, 08 Nov 2023 21:30:58 +0100
+
 tome (2.41-ah~0.git.20200131-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru tome-2.41-ah~0.git.20200131/debian/control 
tome-2.41-ah~0.git.20200131/debian/control
--- tome-2.41-ah~0.git.20200131/debian/control  2023-11-08 21:43:48.0 
+0100
+++ tome-2.41-ah~0.git.20200131/debian/control  2023-11-08 21:30:43.0 
+0100
@@ -7,7 +7,7 @@
 Homepage: https://github.com/tome2/tome2
 Build-Depends: debhelper-compat (= 12), libjansson-dev, cmake,
  libncurses5-dev | libncurses-dev | ncurses-dev, libboost-all-dev,
- libx11-dev, libgtk2.0-dev, dpkg-dev (>= 1.16.0)
+ libx11-dev, dpkg-dev (>= 1.16.0)
 XS-Autobuild: yes
 Standards-Version: 4.3.0
 
diff -Nru tome-2.41-ah~0.git.20200131/debian/patches/debian.patch 
tome-2.41-ah~0.git.20200131/debian/patches/debian.patch
--- tome-2.41-ah~0.git.20200131/debian/patches/debian.patch 1970-01-01 
01:00:00.0 +0100
+++ tome-2.41-ah~0.git.20200131/debian/patches/debian.patch 2023-11-08 
21:30:58.0 +0100
@@ -0,0 +1,126 @@
+--- tome-2.41-ah~0.git.20200131.orig/CMakeLists.txt
 tome-2.41-ah~0.git.20200131/CMakeLists.txt
+@@ -28,7 +28,7 @@ SET(SANITIZER_FLAGS "-fsanitize=undefine
+ #
+ SET(CMAKE_C_FLAGS   "${CMAKE_C_FLAGS} ${COMMON_COMPILER_FLAGS}")
+ SET(CMAKE_C_FLAGS_RELEASE   "-O2")
+-SET(CMAKE_C_FLAGS_DEBUG "-O0 -g ${SANITIZER_FLAGS}")
++SET(CMAKE_C_FLAGS_DEBUG "-O0 -g")
+ 
+ #
+ # C++ Compiler Flags
+@@ -36,7 +36,7 @@ SET(CMAKE_C_FLAGS_DEBUG "-O0 -g ${SA
+ SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${COMMON_COMPILER_FLAGS}")
+ SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DJSONCONS_NO_DEPRECATED")
+ SET(CMAKE_CXX_FLAGS_RELEASE "-O2")
+-SET(CMAKE_CXX_FLAGS_DEBUG   "-O0 -g ${SANITIZER_FLAGS} -D_GLIBCXX_DEBUG 
-D_GLIBCXX_DEBUG_PEDANTIC")
++SET(CMAKE_CXX_FLAGS_DEBUG   "-O0 -g -D_GLIBCXX_DEBUG 
-D_GLIBCXX_DEBUG_PEDANTIC")
+ 
+ #
+ # GCC Flags
+@@ -100,7 +100,7 @@ endif(WIN32)
+ # Set the path for loading the library bits.
+ #
+ IF(SYSTEM_INSTALL)
+-  SET(DEFAULT_PATH "${CMAKE_INSTALL_PREFIX}/lib/tome")
++  SET(DEFAULT_PATH "/var/games/tome")
+ ELSE()
+   SET(DEFAULT_PATH "./lib")
+ ENDIF()
+--- tome-2.41-ah~0.git.20200131.orig/src/CMakeLists.txt
 tome-2.41-ah~0.git.20200131/src/CMakeLists.txt
+@@ -166,21 +166,21 @@ IF(X11_FOUND)
+   INCLUDE_DIRECTORIES(${X11_INCLUDE_DIR})
+   ADD_EXECUTABLE(tome-x11 main-x11.cc)
+   TARGET_LINK_LIBRARIES(tome-x11 game_main game squelch ${LIBS} 
${X11_LIBRARIES})
+-  INSTALL(TARGETS tome-x11 RUNTIME DESTINATION bin)
++  INSTALL(TARGETS tome-x11 RUNTIME DESTINATION games)
+ ENDIF()
+ 
+ IF(CURSES_FOUND)
+   INCLUDE_DIRECTORIES(${CURSES_INCLUDE_DIR})
+   ADD_EXECUTABLE(tome-gcu main-gcu.cc)
+   TARGET_LINK_LIBRARIES(tome-gcu game_main game squelch ${LIBS} 
${CURSES_LIBRARIES})
+-  INSTALL(TARGETS tome-gcu RUNTIME DESTINATION bin)
++  INSTALL(TARGETS tome-gcu RUNTIME DESTINATION games)
+ ENDIF()
+ 
+ IF(GTK2_FOUND)
+   INCLUDE_DIRECTORIES(${GTK2_INCLUDE_DIRS})
+   ADD_EXECUTABLE(tome-gtk2 main-gtk2.cc)
+   TARGET_LINK_LIBRARIES(tome-gtk2 game_main game squelch ${LIBS} 
${GTK2_LIBRARIES})
+-  INSTALL(TARGETS tome-gtk2 RUNTIME DESTINATION bin)
++  INSTALL(TARGETS tome-gtk2 RUNTIME DESTINATION games)
+ ENDIF()
+ 
+ # test harness 

Bug#1055609: tome: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: tome
Version: 2.41-ah~0.git.20200131-1.2
Severity: wishlist

Dear maintainer,

This package is among the few that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Thanks,
Bastian

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

[Olly Betts]

On Wed, Nov 08, 2023 at 08:10:26PM +0100, Martin Budaj wrote:
> On Tue, Nov 7, 2023 at 4:25 PM Wookey  wrote:
> 
> > It looks like moving to catch3 and adding:
> > target_link_libraries(test PRIVATE Catch2::Catch2WithMain)
> > in the test targets should do the trick.

> as we still need to maintain Catch2 v2 API compatibility to run CI tests
> and builds on older Ubuntu images, we can't simply migrate to v3.
> 
> For now, I'll just enable using the bundled Catch2 instead of v3 installed
> in the system.

Note that doing so violates a "should" in Debian Policy:

4.13. Embedded code copies
==

Some software packages include in their distribution convenience
copies of code from other software packages, generally so that users
compiling from source don’t have to download multiple packages. Debian
packages should not make use of these convenience copies unless the
included package is explicitly intended to be used in this way.  [17]
If the included code is already in the Debian archive in the form of a
library, the Debian packaging should ensure that binary packages
reference the libraries already in Debian and the convenience copy is
not used. If the included code is not already in Debian, it should be
packaged separately as a prerequisite if possible.  [18]

If you (as upstream) are going to have a bundled code copy of catch, you
could just bundle catch3 instead.

Cheers,
Olly

Bug#1055608: RFA: kconfiglib -- Python Kconfig implementation

[Bastian Germann]

Package: wnpp

Hereby, I request a new maintainer to take over kconfiglib, which is a Kconfig 
implementation.
The package is in a good state, very low-maintenance and I do no longer need it.
Origninally, I introduced the package as a kas dependency.

Bug#1055509: bfh-container: diversions need to be updated to deal with DEP17 P3

[Helmut Grohne]

On Tue, Nov 07, 2023 at 03:37:46PM +, Luca Boccassi wrote:
> systemd-sysv 255~rc1-3, currently in experimental, moves
> halt/poweroff/reboot/shutdown from /sbin/ to /usr/sbin/, and thus
> diversions employed by this package fall afoul of DEP17 P3. Please
> update the diversions as needed. For now, systemd-sysv has an
> unversioned conflict to avoid data losses. This will be uploaded to
> unstable this week. As soon as a fixed version of this package is
> uploaded, the conflict will be changed to versioned.

I'm proposing the attached patch to implement DEP17 mitigation M18. I
caution that the patch is untested, because piuparts failed for
unrelated reasons. open-infrastructure-compute-tools.postinst and
sudo.prerm fail inside piuparts. So consider this a starting point.

Helmut
diff --minimal -Nru bfh-metapackages-20211009/debian/bfh-container.postrm 
bfh-metapackages-20211009/debian/bfh-container.postrm
--- bfh-metapackages-20211009/debian/bfh-container.postrm   2023-08-14 
09:07:46.0 +0200
+++ bfh-metapackages-20211009/debian/bfh-container.postrm   2023-11-08 
16:43:38.0 +0100
@@ -6,12 +6,13 @@
remove)
for FILE in halt poweroff reboot shutdown coldreboot
do
-   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert /lib/container/divert/${FILE}.orig /sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert "/usr/lib/container/divert/${FILE}.orig" "/usr/sbin/${FILE}"
+   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert "/lib/container/divert/${FILE}.orig" /sbin/${FILE}
done
 
for FILE in pm-hibernate pm-suspend pm-suspend-hybrid
do
-   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert /lib/container/divert/${FILE}.orig /usr/sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert "/usr/lib/container/divert/${FILE}.orig" "/usr/sbin/${FILE}"
done
;;
 
diff --minimal -Nru bfh-metapackages-20211009/debian/bfh-container.preinst 
bfh-metapackages-20211009/debian/bfh-container.preinst
--- bfh-metapackages-20211009/debian/bfh-container.preinst  2023-08-14 
09:07:46.0 +0200
+++ bfh-metapackages-20211009/debian/bfh-container.preinst  2023-11-08 
16:48:30.0 +0100
@@ -4,16 +4,26 @@
 
 case "${1}" in
install|upgrade)
-   mkdir -p /lib/container/divert
+   mkdir -p /usr/lib/container/divert /lib/container/divert
 
for FILE in halt poweroff reboot shutdown coldreboot
do
-   dpkg-divert --package bfh-container --quiet --add 
--rename --divert /lib/container/divert/${FILE}.orig /sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet --add 
--rename --divert "/usr/lib/container/divert/${FILE}.orig" "/usr/sbin/${FILE}"
+   # DEP17 M18 duplicated diversion. Can be removed after 
trixie.
+   dpkg-divert --package bfh-container --quiet --add 
--rename --divert "/lib/container/divert/${FILE}.orig" "/sbin/${FILE}"
done
 
for FILE in pm-hibernate pm-suspend pm-suspend-hybrid
do
-   dpkg-divert --package bfh-container --quiet --add 
--rename --divert /lib/container/divert/${FILE}.orig /usr/sbin/${FILE}
+   if test "$(dpkg-divert --truename "/usr/sbin/${FILE}")" 
= "/lib/container/divert/${FILE}.orig"; then
+   dpkg-divert --package bfh-container --quiet 
--remove --no-rename --divert /lib/container/divert/${FILE}.orig 
/usr/sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet 
--add --no-rename --divert /usr/lib/container/divert/${FILE}.orig 
/usr/sbin/${FILE}
+   if test -e "/lib/container/divert/${FILE}.orig" 
&& ! test -e "/usr/lib/container/divert/${FILE}.orig"; then
+   mv "/lib/container/divert/${FILE}.orig" 
"/usr/lib/container/divert/${FILE}.orig"
+   fi
+   else
+   dpkg-divert --package bfh-container --quiet 
--add --rename --divert /usr/lib/container/divert/${FILE}.orig /usr/sbin/${FILE}
+   fi
done
;;
 
diff --minimal -Nru bfh-metapackages-20211009/debian/changelog 
bfh-metapackages-20211009/debian/changelog
--- bfh-metapackages-20211009/debian/changelog  2023-10-11 11:26:46.0 
+0200
+++ bfh-metapackages-20211009/debian/changelog  2023-11-08 16:49:07.0 
+0100
@@ -1,3 +1,11 @@
+bfh-metapackages (20211009-21.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Duplicate diversions for DEP17 M18. (Closes: #-1)
+  * 

Bug#1055511: progress-linux-container: diversions need to be updated to deal with DEP17 P3

[Helmut Grohne]

On Tue, Nov 07, 2023 at 03:38:56PM +, Luca Boccassi wrote:
> systemd-sysv 255~rc1-3, currently in experimental, moves
> halt/poweroff/reboot/shutdown from /sbin/ to /usr/sbin/, and thus
> diversions employed by this package fall afoul of DEP17 P3. Please
> update the diversions as needed. For now, systemd-sysv has an
> unversioned conflict to avoid data losses. This will be uploaded to
> unstable this week. As soon as a fixed version of this package is
> uploaded, the conflict will be changed to versioned.

I'm attaching a patch. I don't have high confidence, because it fails
piuparts with left-over files. Given the mess in piuparts, I have no
intentions to further test this. You may use the patch as a starting
point.

Helmut

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

[Paul Gevers]

Hi,

On 08-11-2023 18:02, Santiago Vila wrote:

Question for Paul Gevers:

When we make an upload for bookworm to fix a FTBFS bug,
should we also try to fix autopkgtests when they fail in stable?


You are welcome to fix autopkgtest issues in stable, provided that the 
upload meets the requirements for stable. In other words (I'm not a 
Stable Release Manager), if the changes are targeted, reviewable and 
worth the risk, time and effort, than they are appreciated. But in the 
way we use "should" in documentation, the word "should" is (still, may 
change in the future) too strong for "fix autopkgtest if they fail in 
stable".


See for an example: https://bugs.debian.org/1054488

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055607: gmemusage crashes immediately

[André Offringa]

Package: gmemusage
Version: 0.2-11+b2
Severity: important

Dear Maintainer,

When starting gmemusage, it immediately crashes:

$ gmemusage
realloc(): invalid next size
Aborted


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

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

Versions of packages gmemusage depends on:
ii  libc6 2.37-12
ii  libx11-6  2:1.8.7-1

gmemusage recommends no packages.

gmemusage suggests no packages.

-- no debconf information

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

[Martin Budaj]

On Tue, Nov 7, 2023 at 4:25 PM Wookey  wrote:

> It looks like moving to catch3 and adding:
> target_link_libraries(test PRIVATE Catch2::Catch2WithMain)
> in the test targets should do the trick.
>

Hi,

as we still need to maintain Catch2 v2 API compatibility to run CI tests
and builds on older Ubuntu images, we can't simply migrate to v3.

For now, I'll just enable using the bundled Catch2 instead of v3 installed
in the system.

Martin

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

[Bastian Germann]

Am 08.11.23 um 17:47 schrieb Santiago Vila:

Note: I joined the Python team recently to fix bugs
like this in stable, so I'd just need the confirmation
that the above is actually what we need to do.


Confirmed.

Bug#1055347: ITA: kitty -- fast, featureful, GPU based terminal

[Nilesh Patra]

On Wed, Nov 08, 2023 at 05:52:05PM +0800, Maytham Alsudany wrote:
> On the contrary, avoiding the use of dh-golang as done in this repo[3] causes
> all the tests to pass without problem, and I'm unsure to why that is.

This was due to some caveats with the build system and also how
dh_golang works. We added in a patch that'd skip running gen-go-code.py
and this was being used at more than one place.

I've fixed up the build and the tests and the package seems to
build/work. I suppose we should be pushing it to debian experimental for
now since this introduces some completely new things. Let me know if you
disagree.

I've pushed all my changes to the debian/experimental branch on the
existing salsa repo[5] and also added your access to it so you could
push directly.

> We may have to take the approach Fedora has taken, where they've skipped any
> continuously failing tests[4].

For now I disabled two tests in the go code that tries to fiddle with
proc/devfs and can potentially fail in a chroot. Python tests probably
also try to do some non-standard stuff and we could disable it later if
it goes flaky on the buildd machines.

That said, I want to discuss/ask a few things:
* Can you take a look at my commits and let me know if you have any
  comments?
* Can you please clean up some of the lintian stuff? And then we could
  upload the new release.
* Since we both are interested in kitty's packaging, I think we have two
  options:
  - Either you or me would be in the "Maintainer" field and the other one would
be in "Uploader" field.
  - Add ki...@packages.debian.org as the maintainer and add both of us
as uploaders (that means we subscribe to the package email
ofcourse).
  Which one do you think we should do?
* I suppose the maintenance of this package will keep getting messy due
  to upstream mixing up two language build systems in a fairly non-standard way.
  I suppose it makes sense to ask upstream if they'd consider to switch
  to something that eases maintenance burden on us (Debian). WDYT?

> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037440#37
> [2]: https://salsa.debian.org/Maytha8/kitty-dh-golang
> [3]: https://salsa.debian.org/Maytha8/kitty
> [4]: https://src.fedoraproject.org/rpms/kitty/blob/rawhide/f/kitty.spec#_268
[5]: 
https://salsa.debian.org/debian/kitty/-/tree/debian/experimental?ref_type=heads

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1055590: r-cran-sf: FTBFS with GDAL 3.8.0

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/r-spatial/sf/issues/2252


-- 
http://fam-tille.de

Bug#1055606: RM: r-cran-rgdal -- ROM; Unmaintained upstream, fails with gdal in experimental leading to RC bug once this migrates to unstable

[Andreas Tille]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: r-cran-rg...@packages.debian.org, 1050...@bugs.debian.org, 
1055...@bugs.debian.org, 1049...@bugs.debian.org, debia...@lists.debian.org
Control: affects -1 + src:r-cran-rgdal

Hi,

as explained by upstream as response in our bug report[1] r-cran-rgdal
is not supported upstream any more.  In bug #1055589 a conflict to the
upcoming GDAL 3.8.0 is stated.  So for the moment r-cran-rgdal is
blocking the GDAL migration from experimental to unstable and even if
this problem is ignored bug #1055589 will become RC with no hope to get
it fixed.

For the moment there is a single reference inside the package pool to
this package.  R-cran-rgdal is suggested by r-cran-satellite which is
due to the automatic generation of dependencies by dh-r.  I'd prefer to
wait until r-cran-rgdal is removed and than regenerate the
r-cran-satellite to get this dependency fixed over fiddling around
manually with the control file.

So I consider it save to remove r-cran-rgdal from unstable.

Kind regards and thanks for your work as ftpmaster
Andreas.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049438#31

Bug#1041695: chromium: Crash when starting with --incognito option

[Maxime Silvier]

Recent updates solved my issue. I can confirm that Chromium 
119.0.6045.105-1~deb12u1 is no longer affected by a crash; the --incognito 
option works as intended. The last affected version that I did use was 
117.0.5938.62-1~deb12u1. I did not test the 118 release.
In brief, the bug is resolved. Thank you for your patience and attention.
Bests regards.

Bug#1004125: Screen flickering with 2.4.109

[Diederik de Haas]

Control: tag -1 moreinfo

On 21 Jan 2022 12:23:33 +0100 Philipp Marek  wrote:
> See also https://gitlab.freedesktop.org/drm/intel/-/issues/1512

It's great that you participated in that upstream issue, but my guess is that 
it's not getting attention because the issue is closed.
If you can still reproduce this with the latest kernel and libdrm packages, 
can you open a new issue upstream? And mention that in this bug?

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

Bug#1053457: More info needed, cannot reproduce

[Roland Clobus]

tags +unreproducible
thanks

Hello Emanuele,

I've seen your (now aborted) merge request, and your additional info in 
this bug ticket. Sorry for not replying sooner.


I've run the commands that you have provided, and am unable to reproduce 
your case.


lb config --distribution sid --updates false --archive-areas 'main 
non-free-firmware' --bootloaders grub-efi

echo live-task-lxde > config/package-lists/desktop.list.chroot
lb build --debug

My last line in the output is:
P: Build completed successfully

I'm running (lb --version) 20230502 on sid, all commands have run as root.

1) Can you provide more information about the system that you are using 
to build the image on?

2) Could you also try to run the latest git version (see [1])

With kind regards,
Roland Clobus

[1] https://wiki.debian.org/ReproducibleInstalls/LiveImages


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#929130: falkon: Falkon crash at start

[Diederik de Haas]

Control: tag -1 moreinfo

On 30 May 2019 14:37:26 +0200 Bardot Jérôme  wrote:
> Le 29/05/2019 à 21:14, Bernhard Übelacker a écrit :
> > You might also want to look through "dmesg -T" output
> > if there is anything related to nouveau in the given time.
> > That might also be helpful for the maintainer.
> I add the output for previous execution (there is 2 minutes between
> falkon log and dmesg log because first time i didn’t had LC_ALL=C ) and
> re add previous log for libdrm-nouveau

This bug is quite old and it would be useful to know whether the issue
still exists.

I looked at your dmesg log and I'd recommend to update your BIOS and
make sure you have the latest intel-microcode package installed.

- BIOS A19 05/17/2016
You were running BIOS A19 (2016-05-27) and according to [1] there's now
an A28 version from 2019-07-15.

Once you've done that you can check the 'health' of your system with
the following commands:
- dmesg --level emerg,alert,crit
- dmesg --level emerg,alert,crit,err
- dmesg --level emerg,alert,crit,err,warn

Doing it in that sequence allows you to focus on the most important issues
first before looking into the 'minor' ones. 
Getting results on the 1st command is pretty bad. On the last one is to
some extend expected, but may be worth looking into nonetheless.

HTH

[1] 
https://www.dell.com/support/home/en-us/product-support/product/precision-t1700-workstation/drivers

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

Bug#1055567: Error: gscan2pdf fails to compile

[Jeff]

How are you starting gscan2pdf?

What does the following return?

apt list libimage-sane-perl

Regards

Jeff


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055409: /usr/bin/dpkg-deb: dpkg-deb goes defunct and has to be killed during apt dist-upgrade

[Simon John]

and again today, although recovered after 2mins it still went defunct:

ps auxw|grep dpkg
root 2838842 99.0  0.2 150244 10 pts/1   Rs+  17:58   3:38 
/usr/bin/dpkg --status-fd 25 --no-triggers --unpack --auto-deconfigure 
--recursive /tmp/apt-dpkg-install-aJ3NZb


root 2838973  0.0  0.0   7364  2304 pts/1S+   17:58   0:00 
dpkg-deb --fsys-tarfile 
/tmp/apt-dpkg-install-aJ3NZb/05-golang-1.21-src_1.21.4-1_all.deb


root 2838974  0.0  0.0  0 0 pts/1Z+   17:58   0:00 
[dpkg-deb] 


root 2838975  0.9  0.2 244672 147964 pts/1   Sl+  17:58   0:01 
dpkg-deb --fsys-tarfile 
/tmp/apt-dpkg-install-aJ3NZb/05-golang-1.21-src_1.21.4-1_all.deb


--
Simon John

Bug#1055605: fstack-clash-protection hardening change breaks building packages with clang on arm64

[Hugo Melder]

Package: dpkg-dev
Version: 1.22.0
Severity: important

Hi,

The recent change (https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=11efff1bf) 
breaks building Debian packages with clang on arm64. LLVM does not have 
-fstack-clash-protection enabled on aarch64 (https://reviews.llvm.org/D96007).

Here is the original bug report for adding clash protection: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918914

The GNUstep Objective-C 2.0 toolchain depends on Clang as GCC does not have 
newer Objective-C features such as ARC, properties, and blocks.

Fedora enables stack-clash-protection based on the toolchain 
(https://src.fedoraproject.org/fork/tstellar/rpms/redhat-rpm-config/blob/c0bad810b4b47086f58e7537e258333b14c92c45/f/rpmrc#_77),
 and omits the flag when the compiler is not gcc.

I would suggest either checking for the compiler (if possible), or disabling it 
for aarch64 until Clang has support for it as well. Right now, projects like 
Grand Central Dispatch (libdispatch) or other projects with -Werror turned on, 
refuse to build.

Bug#1055604: osmcoastline: FTBFS with GDAL 3.8.0

[Bas Couwenberg]

Source: osmcoastline
Version: 2.4.0-2
Severity: important
Tags: ftbfs upstream
User: debian-...@lists.debian.org
Usertags: gdal-3.8

Dear Maintainer,

Your package FTBFS with GDAL 3.8.0 from experimental:

 In file included from /usr/include/gdal/ogr_geometry.h:36,
  from /build/osmcoastline-2.4.0/src/coastline_polygons.hpp:25,
  from 
/build/osmcoastline-2.4.0/src/coastline_ring_collection.cpp:22:
 /usr/include/gdal/cpl_json.h:97:36: error: expected ')' before 'nVal'
97 | explicit CPLJSONObject(uint64_t nVal);
   |   ~^
   |)
 /usr/include/gdal/cpl_json.h:119:41: error: 'uint64_t' has not been declared
   119 | void Add(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:119:10: error: 'void CPLJSONObject::Add(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Add(const 
std::string&, int)'
   119 | void Add(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:117:10: note: previous declaration 'void 
CPLJSONObject::Add(const std::string&, int)'
   117 | void Add(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:131:41: error: 'uint64_t' has not been declared
   131 | void Set(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:131:10: error: 'void CPLJSONObject::Set(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Set(const 
std::string&, int)'
   131 | void Set(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:129:10: note: previous declaration 'void 
CPLJSONObject::Set(const std::string&, int)'
   129 | void Set(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:245:14: error: 'uint64_t' has not been declared
   245 | void Add(uint64_t nValue);
   |  ^~~~
 /usr/include/gdal/cpl_json.h:245:10: error: 'void CPLJSONArray::Add(int)' 
cannot be overloaded with 'void CPLJSONArray::Add(int)'
   245 | void Add(uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:243:10: note: previous declaration 'void 
CPLJSONArray::Add(int)'
   243 | void Add(int nValue);
   |  ^~~

The full buildlog is attached.

Kind Regards,

Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: libgdal-dev libgeos++-dev 
libosmium2-dev (>= 2.16.0) libgdalcpp-dev pandoc spatialite-bin
W: Unmet build-dependency in source
dh clean --buildsystem cmake
   dh_auto_clean -O--buildsystem=cmake
   dh_autoreconf_clean -O--buildsystem=cmake
   dh_clean -O--buildsystem=cmake
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building osmcoastline using existing 
./osmcoastline_2.4.0.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building osmcoastline in osmcoastline_2.4.0-3.debian.tar.xz
dpkg-source: info: building osmcoastline in osmcoastline_2.4.0-3.dsc
I: Generating source changes file for original dsc
dpkg-genchanges: info: not including original source code in upload
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.3789300
I: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow 
/var/cache/pbuilder/build/cow.3789300
I: removed stale ilistfile /var/cache/pbuilder/build/cow.3789300/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.3789300 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.3789300 --buildresult /var/cache/pbuilder/result/ 
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.3789300 cow-shell' 
/home/bas/tmp/debian/osmcoastline_2.4.0-3.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Wed Nov  8 18:49:58 CET 2023
I: pbuilder-time-stamp: 1699465798
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/home/bas/tmp/debian/osmcoastline_2.4.0-3.dsc]
I: copying [/home/bas/tmp/debian/osmcoastline_2.4.0.orig.tar.gz]
I: copying 

Bug#1053511: Problem found

[Debian]

Am 08.11.23 um 18:14 schrieb Thorsten Alteholz:


But this looks rather like a local problem. If your /var/*/cups is not 
at the default location, you should adapt your apparmor files on your 
own, shouldn't you?


  Thorsten


Oh yes - that's true. Embarrassing ...

There was already an alias defined for apparmor, but the content of the 
partition has moved.
It has been forgotten that this has to be altered and the problem has 
been searched at a wrong place.
The directory /var is only a symbolic link, because the SSD should not 
get so many write operations for it.


Then this bug will be closed. Thanks!

karsten

Bug#1055603: tre: [L10N,DE] tre_0.8.0-7: german translation

[Christoph Brinkhaus]

Source: tre
Version: 0.8.0-7
Severity: wishlist

Dear Maintainer,

please find attached the po file with the german translation.
It is an update to the current po template.
Please consider to apply it to the package.

Thank you very much!

Kind regards,
Christoph Brinkhaus

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

Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
# Translation of tre to German
# Copyright (C) 2006 Ville Laurikari
# This file is distributed under the same license as the tre package.
# Chris Leick , 2009.
# Christoph Brinkhaus , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: tre_0.8.0-7\n"
"Report-Msgid-Bugs-To: tre-gene...@lists.laurikari.net\n"
"POT-Creation-Date: 2006-12-09 22:48+0200\n"
"PO-Revision-Date: 2023-11-06 12:15+0100\n"
"Last-Translator: Christoph Brinkhaus \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"


#: lib/regerror.c:43
msgid "No error"
msgstr "Kein Fehler"

#: lib/regerror.c:44
msgid "No match"
msgstr "Kein Treffer"

#: lib/regerror.c:45
msgid "Invalid regexp"
msgstr "Falscher regulärer Ausdruck"

#: lib/regerror.c:46
msgid "Unknown collating element"
msgstr "Unbekanntes Ordnungselement"

#: lib/regerror.c:47
msgid "Unknown character class name"
msgstr "Unbekannter Zeichenklassenname"

#: lib/regerror.c:48
msgid "Trailing backslash"
msgstr "Angehängter Backslash"

#: lib/regerror.c:49
msgid "Invalid back reference"
msgstr "Ungültiger Rückwärtsbezug"

#: lib/regerror.c:50
msgid "Missing ']'"
msgstr "Fehlende »]«"

#: lib/regerror.c:51
msgid "Missing ')'"
msgstr "Fehlende »)«"

#: lib/regerror.c:52
msgid "Missing '}'"
msgstr "Fehlende »}«"

#: lib/regerror.c:53
msgid "Invalid contents of {}"
msgstr "Ungültige Inhalte von {}"

#: lib/regerror.c:54
msgid "Invalid character range"
msgstr "Ungültiger Schriftzeichenbereich"

#: lib/regerror.c:55 src/agrep.c:230 src/agrep.c:300 src/agrep.c:325
#: src/agrep.c:674 src/agrep.c:713
msgid "Out of memory"
msgstr "Platz im Hauptspeicher reicht nicht aus"

#: lib/regerror.c:56
msgid "Invalid use of repetition operators"
msgstr "Falsche Benutzung von Wiederholungsoperatoren"

#: lib/regerror.c:69
msgid "Unknown error"
msgstr "Unbekannter Fehler"

#: src/agrep.c:97 src/agrep.c:104
#, c-format
msgid "Usage: %s [OPTION]... PATTERN [FILE]...\n"
msgstr "Aufruf: %s [OPTION]... MUSTER [DATEI]...\n"

#: src/agrep.c:99
#, c-format
msgid "Try `%s --help' for more information.\n"
msgstr "Versuchen Sie »%s --help« um weitere Informationen zu erhalten.\n"

#: src/agrep.c:105
#, c-format
msgid ""
"Searches for approximate matches of PATTERN in each FILE or standard input.\n"
"Example: `%s -2 optimize foo.txt' outputs all lines in file `foo.txt' that\n"
"match \"optimize\" within two errors.  E.g. lines which contain \"optimise"
"\",\n"
"\"optmise\", and \"opitmize\" all match.\n"
msgstr ""
"Sucht nach ungefähren Treffern von MUSTER in jeder DATEI oder der\n"
"Standardeingabe.\n"
"Beispiel: »%s -2 optimize foo.txt« gibt alle Zeilen in der Datei\n"
"»foo.txt« aus, die in zwei Fehlern »optimize« gleichen. Z.B. Zeilen, die\n"
"»optimise«,»optmise« und »opitmize« enthalten passen alle.\n"

#: src/agrep.c:111
#, c-format
msgid ""
"Regexp selection and interpretation:\n"
"  -e, --regexp=PATTERN\tuse PATTERN as a regular expression\n"
"  -i, --ignore-case\tignore case distinctions\n"
"  -k, --literal\t\tPATTERN is a literal string\n"
"  -w, --word-regexp\tforce PATTERN to match only whole words\n"
"\n"
"Approximate matching settings:\n"
"  -D, --delete-cost=NUM\tset cost of missing characters\n"
"  -I, --insert-cost=NUM\tset cost of extra characters\n"
"  -S, --substitute-cost=NUM set cost of wrong characters\n"
"  -E, --max-errors=NUM\tselect records that have at most NUM errors\n"
"  -#\t\t\tselect records that have at most # errors (# is a\n"
"\t\t\tdigit between 0 and 9)\n"
"\n"
"Miscellaneous:\n"
"  -d, --delimiter=PATTERN   set the record delimiter regular expression\n"
"  -v, --invert-match\tselect non-matching records\n"
"  -V, --version\t\tprint version information and exit\n"
"  -y, --nothing\t\tdoes nothing (for compatibility with the non-free\n"
"\t\t\tagrep program)\n"
"  --help\t\tdisplay this help and exit\n"
"\n"
"Output control:\n"
"  -B, --best-match\tonly output records with least errors\n"
"  -c, --count\t\tonly print a count of matching records per FILE\n"
"  -h, --no-filename\tsuppress the prefixing 

Bug#1055602: libgdal-grass: FTBFS with GDAL 3.8.0

[Bas Couwenberg]

Source: libgdal-grass
Version: 1.0.2-6
Severity: important
Tags: ftbfs upstream
User: debian-...@lists.debian.org
Usertags: gdal-3.8

Dear Maintainer,

Your package FTBFS with GDAL 3.8.0 from experimental:

 g++ -Wall -fPIC -DUSE_CPL -DGRASS_GISBASE=\"/usr/lib/grass83\" 
-I/usr/include/gdal -I/usr/lib/grass83/include -I/usr/include/postgresql 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/build/libgdal-grass-1.0.2=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o 
ogrgrasslayer.o ogrgrasslayer.cpp
 In file included from /usr/include/gdal/ogr_geometry.h:36,
  from /usr/include/gdal/ogr_feature.h:36,
  from /usr/include/gdal/ogrsf_frmts.h:35,
  from ogrgrass.h:33,
  from ogrgrassdriver.cpp:29:
 /usr/include/gdal/cpl_json.h:97:36: error: expected ')' before 'nVal'
97 | explicit CPLJSONObject(uint64_t nVal);
   |   ~^
   |)
 /usr/include/gdal/cpl_json.h:119:41: error: 'uint64_t' has not been declared
   119 | void Add(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:119:10: error: 'void CPLJSONObject::Add(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Add(const 
std::string&, int)'
   119 | void Add(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:117:10: note: previous declaration 'void 
CPLJSONObject::Add(const std::string&, int)'
   117 | void Add(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:131:41: error: 'uint64_t' has not been declared
   131 | void Set(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:131:10: error: 'void CPLJSONObject::Set(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Set(const 
std::string&, int)'
   131 | void Set(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:129:10: note: previous declaration 'void 
CPLJSONObject::Set(const std::string&, int)'
   129 | void Set(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:245:14: error: 'uint64_t' has not been declared
   245 | void Add(uint64_t nValue);
   |  ^~~~
 /usr/include/gdal/cpl_json.h:245:10: error: 'void CPLJSONArray::Add(int)' 
cannot be overloaded with 'void CPLJSONArray::Add(int)'
   245 | void Add(uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:243:10: note: previous declaration 'void 
CPLJSONArray::Add(int)'
   243 | void Add(int nValue);
   |  ^~~
 In file included from /usr/include/gdal/ogr_geometry.h:36,
  from /usr/include/gdal/ogr_feature.h:36,
  from /usr/include/gdal/ogrsf_frmts.h:35,
  from ogrgrass.h:33,
  from ogrgrassdatasource.cpp:30:
 /usr/include/gdal/cpl_json.h:97:36: error: expected ')' before 'nVal'
97 | explicit CPLJSONObject(uint64_t nVal);
   |   ~^
   |)
 /usr/include/gdal/cpl_json.h:119:41: error: 'uint64_t' has not been declared
   119 | void Add(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:119:10: error: 'void CPLJSONObject::Add(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Add(const 
std::string&, int)'
   119 | void Add(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:117:10: note: previous declaration 'void 
CPLJSONObject::Add(const std::string&, int)'
   117 | void Add(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:131:41: error: 'uint64_t' has not been declared
   131 | void Set(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:131:10: error: 'void CPLJSONObject::Set(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Set(const 
std::string&, int)'
   131 | void Set(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:129:10: note: previous declaration 'void 
CPLJSONObject::Set(const std::string&, int)'
   129 | void Set(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:245:14: error: 'uint64_t' has not been declared
   245 | void Add(uint64_t nValue);
   |  ^~~~
 /usr/include/gdal/cpl_json.h:245:10: error: 'void CPLJSONArray::Add(int)' 
cannot be overloaded with 'void CPLJSONArray::Add(int)'
   245 | void Add(uint64_t nValue);
   |  ^~~
 

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

[Santiago Vila]

Note: I've asked Paul Gevers if it's desirable/recommended to fix
autopkgtests in stable when fixing FTBFS bugs in stable.
If yes, we should include the changes in -2 too.

Thanks.

Bug#1055401: [in-toto-dev] Bug#1055401: in-toto: recommends transition package gnupg2

[Holger Levsen]

On Wed, Nov 08, 2023 at 05:53:30PM +0100, Lukas Pühringer wrote:
> @Holger, would you kindly upload?

yes, ASAP!

> ps: debian/* files changes can be found in 
> https://github.com/in-toto/in-toto/pull/646

I saw you also uploaded to mentors! :thumbsup:


-- 
cheers,
Holger

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

Segregation was legal. Slavery was legal. Don't use legality as a guide to
morality. Outlaw profits from fossil fuel.


signature.asc
Description: PGP signature

Bug#1053511: Problem found

[Thorsten Alteholz]

On 08.11.23 15:27, Debian wrote:
Nov 08 14:24:04 PC audit[9568]: AVC apparmor="DENIED" 
operation="chown" profile="/usr/sbin/cupsd" 
name="/srv/ssd1/var/spool/cups/" pid=95>
Nov 08 14:24:04 PC audit[9568]: AVC apparmor="DENIED" 
operation="mkdir" profile="/usr/sbin/cupsd" 
name="/srv/ssd1/var/log/cups/" pid=9568> 



But this looks rather like a local problem. If your /var/*/cups is not 
at the default location, you should adapt your apparmor files on your 
own, shouldn't you?


  Thorsten

Bug#1055407: python3-securesystemslib: recommends transition package gnupg2

[Lukas Pühringer]

Fixed in 0.28.0-1 available on mentors:
https://mentors.debian.net/package/python-securesystemslib/

@Holger, would you kindly upload?

Cheers,
Lukas

ps: debian/* files changes can be found in 
https://github.com/secure-systems-lab/securesystemslib/pull/672


> On 05.11.2023, at 14:19, Andreas Metzler  wrote:
> 
> Package: python3-securesystemslib
> Version: 0.26.0-1
> Severity: normal
> User: pkg-gnupg-ma...@lists.alioth.debian.org
> Usertags: gnupg2-rdep
> 
> Hello,
> 
> this package recommends gnupg2 which has been a transitional package
> depending on gnupg since 2016. Please refer to gnupg instead.
> 
> cu Andreas
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "securesystemslib-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to securesystemslib-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_securesystemslib-2Ddev_ZUeWSYQBhKj-2D2-5FQ-5F-2540argenau.bebt.de=DwIBaQ=slrrB7dE8n7gBJbeO0g-IQ=2YMLsMLCML1EOEAeVc1Mhx6J99vqRVHSnZUnatehIDg=8vr8KM1HQP4To_m0AVumAKR8lFO5UPFISvjfZsYDuG6yFZrHiIY34yZnFA6R23gQ=_N_Ohgv20Vyk0H-2W0fWCVM2fp_WGxxzsbsShq_sIFA=
>  .

Bug#1055601: darktable: Segfault in first run after system hang

[Greg Schmidt]

Package: darktable
Version: 4.4.2-1+b1
Severity: normal
X-Debbugs-Cc: g...@desk1.attlocal.net

Dear Maintainer,

I was using darktable when my system hung. I had to reboot to recover. After 
the reboot I started darktable and 
it segfaulted. A backtrace was created which implicated dlopen. It was 
attempting to load "libMesaOpenCL.so.1".
A subsequent start of darktable was normal. 

Content of /tmp/darktable_bt_T7K9D2.txt follows:

this is darktable 4.4.2 reporting a segfault:

warning: Currently logging to /tmp/darktable_bt_T7K9D2.txt.  Turn the logging 
off and on to make the new setting effective.
#0  0x7f83a54f11b7 in __GI___wait4 (pid=5442, stat_loc=0x0, options=0, 
usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30
#1  0x7f83a57a28d0 in  () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#2  0x7f83a545a510 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#3  0x7f833fd6bd52 in LLVMCreateTargetMachine () at 
/lib/x86_64-linux-gnu/libLLVM-15.so.1
#4  0x7f8351455e0e in  () at 
/usr/lib/x86_64-linux-gnu/gallium-pipe/pipe_radeonsi.so
#5  0x7f83514561c5 in  () at 
/usr/lib/x86_64-linux-gnu/gallium-pipe/pipe_radeonsi.so
#6  0x7f83513654eb in  () at 
/usr/lib/x86_64-linux-gnu/gallium-pipe/pipe_radeonsi.so
#7  0x7f8351365943 in  () at 
/usr/lib/x86_64-linux-gnu/gallium-pipe/pipe_radeonsi.so
#8  0x7f8395331720 in amdgpu_winsys_create () at 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#9  0x7f8351366616 in  () at 
/usr/lib/x86_64-linux-gnu/gallium-pipe/pipe_radeonsi.so
#10 0x7f835123b50a in  () at 
/usr/lib/x86_64-linux-gnu/gallium-pipe/pipe_radeonsi.so
#11 0x7f8351eb4fa8 in  () at /lib/x86_64-linux-gnu/libMesaOpenCL.so.1
#12 0x7f8351ea0bd8 in  () at /lib/x86_64-linux-gnu/libMesaOpenCL.so.1
#13 0x7f8351eafae2 in  () at /lib/x86_64-linux-gnu/libMesaOpenCL.so.1
#14 0x7f8351e737d9 in  () at /lib/x86_64-linux-gnu/libMesaOpenCL.so.1
#15 0x7f83a5dfad2e in call_init (env=0x5568250ba0e0, argv=0x7ffd910bebe8, 
argc=7, l=) at ./elf/dl-init.c:90
#16 call_init (l=, argc=7, argv=0x7ffd910bebe8, 
env=0x5568250ba0e0) at ./elf/dl-init.c:27
#17 0x7f83a5dfae14 in _dl_init (main_map=0x556825573a60, argc=7, 
argv=0x7ffd910bebe8, env=0x5568250ba0e0) at ./elf/dl-init.c:137
#18 0x7f83a5df7516 in __GI__dl_catch_exception 
(exception=exception@entry=0x0, operate=operate@entry=0x7f83a5e01570 
, args=args@entry=0x7ffd910ba280) at ./elf/dl-catch.c:211
#19 0x7f83a5e0150e in dl_open_worker (a=a@entry=0x7ffd910ba420) at 
./elf/dl-open.c:808
#20 0x7f83a5df7489 in __GI__dl_catch_exception 
(exception=exception@entry=0x7ffd910ba400, operate=operate@entry=0x7f83a5e01480 
, args=args@entry=0x7ffd910ba420) at ./elf/dl-catch.c:237
#21 0x7f83a5e018a8 in _dl_open (file=0x556825096160 "libMesaOpenCL.so.1", 
mode=, caller_dlopen=0x7f839c0238bd, nsid=, 
argc=7, argv=0x7ffd910bebe8, env=0x5568250ba0e0) at ./elf/dl-open.c:884
#22 0x7f83a54a26f8 in dlopen_doit (a=a@entry=0x7ffd910ba690) at 
./dlfcn/dlopen.c:56
#23 0x7f83a5df7489 in __GI__dl_catch_exception 
(exception=exception@entry=0x7ffd910ba5f0, operate=0x7f83a54a26a0 
, args=0x7ffd910ba690) at ./elf/dl-catch.c:237
#24 0x7f83a5df75af in _dl_catch_error (objname=0x7ffd910ba648, 
errstring=0x7ffd910ba650, mallocedp=0x7ffd910ba647, operate=, 
args=) at ./elf/dl-catch.c:256
#25 0x7f83a54a21e7 in _dlerror_run (operate=operate@entry=0x7f83a54a26a0 
, args=args@entry=0x7ffd910ba690) at ./dlfcn/dlerror.c:138
#26 0x7f83a54a27a9 in dlopen_implementation (dl_caller=, 
mode=, file=) at ./dlfcn/dlopen.c:71
#27 ___dlopen (file=, mode=) at 
./dlfcn/dlopen.c:81
#28 0x7f839c0238bd in  () at /lib/x86_64-linux-gnu/libOpenCL.so.1
#29 0x7f839c023aa3 in  () at /lib/x86_64-linux-gnu/libOpenCL.so.1
#30 0x7f839c0249e3 in clGetPlatformIDs () at 
/lib/x86_64-linux-gnu/libOpenCL.so.1
#31 0x7f83a578aabb in dt_opencl_init () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#32 0x7f83a56efbf3 in dt_init () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#33 0x556823a7a08c in  ()
#34 0x7f83a54456ca in __libc_start_call_main 
(main=main@entry=0x556823a7a070, argc=argc@entry=7, 
argv=argv@entry=0x7ffd910bebe8) at ../sysdeps/nptl/libc_start_call_main.h:58
#35 0x7f83a5445785 in __libc_start_main_impl (main=0x556823a7a070, argc=7, 
argv=0x7ffd910bebe8, init=, fini=, 
rtld_fini=, stack_end=0x7ffd910bebd8) at ../csu/libc-start.c:360
#36 0x556823a7a0f1 in  ()

=

  Id   Target Id Frame 
* 1Thread 0x7f839dc860c0 (LWP 5423) "darktable"  0x7f83a54f11b7 in 
__GI___wait4 (pid=5442, stat_loc=0x0, options=0, usage=0x0) at 
../sysdeps/unix/sysv/linux/wait4.c:30
  2Thread 0x7f839d7ff6c0 (LWP 5425) "pool-spawner"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f839cffe6c0 (LWP 5426) "gmain"  0x7f83a5519a1f in 
__GI___poll (fds=0x556825096e50, nfds=1, timeout=-1) at 

Bug#1055401: [in-toto-dev] Bug#1055401: in-toto: recommends transition package gnupg2

[Lukas Pühringer]

Fixed in 2.0.0-1 available on mentors:
https://mentors.debian.net/package/in-toto/

@Holger, would you kindly upload?

Cheers,
Lukas

ps: debian/* files changes can be found in 
https://github.com/in-toto/in-toto/pull/646

> On 05.11.2023, at 14:13, Andreas Metzler  wrote:
> 
> Package: in-toto
> Version: 1.3.1-1
> Severity: normal
> User: pkg-gnupg-ma...@lists.alioth.debian.org
> Usertags: gnupg2-rdep
> 
> Hello,
> 
> this package recommends gnupg2 which has been a transitional package
> depending on gnupg since 2016. Please refer to gnupg instead.
> 
> cu Andreas
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "in-toto-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to in-toto-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_in-2Dtoto-2Ddev_ZUeU5bEWH3koQLOm-2540argenau.bebt.de=DwIBaQ=slrrB7dE8n7gBJbeO0g-IQ=2YMLsMLCML1EOEAeVc1Mhx6J99vqRVHSnZUnatehIDg=tHNQVAFjZOXpvWlLhFVBrg2beIgGm1F_VrGxKp-HN9I425j1f1Hg2a3l88k-5kgr=u-IYCWcfcnSfk-qHaxbAQqQ3AsCNpQG1boK2qGqIfws=
>  .

Bug#1055592: systemd: suspend and hibernate does not longer work

[Michael Ott]

Hi!

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

CU
  Michael

On Wed, 2023-11-08 at 16:10 +, Luca Boccassi wrote:
> On Wed, 08 Nov 2023 16:50:12 +0100 Michael Ott 
> wrote:
> > Package: systemd
> > Version: 255~rc1-3
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > Since yesterday hibernate and suspend does not longer work.
> journalctl
> > show me this:
> > 
> > systemctl status systemd-suspend.service
> > × systemd-suspend.service - System Suspend
> >   Loaded: loaded (/usr/lib/systemd/system/systemd-
> > suspend.service;
> static)
> >   Active: failed (Result: signal) since Wed 2023-11-08 16:31:01
> CET; 12min ago
> >     Docs: man:systemd-suspend.service(8)
> >  Process: 7133 ExecStart=/usr/lib/systemd/systemd-sleep suspend
> (code=killed, signal=ABRT)
> >     Main PID: 7133 (code=killed, signal=ABRT)
> >  CPU: 44ms
> > 
> > Nov 08 16:31:01 k-c13 systemd[1]: Starting systemd-suspend.service
> > -
> System Suspend...
> > Nov 08 16:31:01 k-c13 systemd-sleep[7133]: Failed to lock home
> directories: Unknown object '/org/freedesktop/home1'.
> > Nov 08 16:31:01 k-c13 systemd-sleep[7133]: Performing sleep
> > operation
> 'suspend'...
> > Nov 08 16:31:01 k-c13 systemd-sleep[7133]: *** invalid open64 call:
> O_CREAT or O_TMPFILE without mode ***: terminated
> > Nov 08 16:31:01 k-c13 systemd[1]: systemd-suspend.service: Main
> process exited, code=killed, status=6/ABRT
> > Nov 08 16:31:01 k-c13 systemd[1]: systemd-suspend.service: Failed
> with result 'signal'.
> > Nov 08 16:31:01 k-c13 systemd[1]: Failed to start systemd-
> suspend.service - System Suspend.
> > 
> > I also got this output:
> > 
> > systemctl list-units --type=mount --all | grep home
> > ●
> home.mount   
>   
>     not-found inactive dead    home.mount
> > 
> > My home directory looks like that:
> > ls -l /home
> > total 0
> > lrwxrwxrwx 1 root root 18 Nov 24  2018 michael ->
> > /srv/home/michael/
> > 
> > What is the problem? Since yesterday it works
> 
> Please open an issue upstream on Github:
> 
> https://github.com/systemd/systemd/issues/new
> 

-- 
CU  
 
  Michael
  
-- 
    ,''`.   
   : :' :   Michael Ott 
   `. `'    e-mail: michael at k-c13 dot org
 `-

Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich derNutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

Bug#1055397: [in-toto-dev] Bug#1055397: apt-transport-in-toto: Depends on transition package gnupg2

[Lukas Pühringer]

Fixed in 0.1.1-4 available on mentors:
https://mentors.debian.net/package/apt-transport-in-toto/

@Holger, would you kindly upload?

Cheers,
Lukas

ps: debian/* files changes can be found in 
https://github.com/in-toto/apt-transport-in-toto/pull/41

> On 05.11.2023, at 14:07, Andreas Metzler  wrote:
> 
> Package: apt-transport-in-toto
> Version: 0.1.1-3
> Severity: normal
> User: pkg-gnupg-ma...@lists.alioth.debian.org
> Usertags: gnupg2-rdep
> 
> Hello,
> 
> this package depends on gnupg2 which has been a transitional package
> depending on gnupg since 2016. Please depend on gnupg instead.
> 
> cu Andreas
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "in-toto-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to in-toto-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_in-2Dtoto-2Ddev_ZUeTdYfzUhPgXHJ-2D-2540argenau.bebt.de=DwIBaQ=slrrB7dE8n7gBJbeO0g-IQ=2YMLsMLCML1EOEAeVc1Mhx6J99vqRVHSnZUnatehIDg=8p0kklITfxxXTTvOX9ymQabZ8ggWQQzD7-PEWwLXvF8Wd2b3dWKkyY2Y6rMpcFdD=VemmlfsWGv6HzEzQRjXERlXPPy490ce1GfeWrZoBUH8=
>  .

Bug#1055600: transition: suitesparse-7.3

[Sébastien Villemot]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-suitesparse.html

Dear Release Team,

Please schedule a transition for suitesparse 7.3, which currently sits in
experimental.

One the shared libraries got a SOVERSION bump (libcholmod4 → libcholmod5). The
ABI change is minor and I’m therefore fairly confident that there won’t be any
issue.

Thanks for your work,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org

Bug#1017577: sqlcipher: new upstream version available

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> The sqlcipher package is now orphaned.  Daniel, perhaps you can have a
> look at updating it?

I had a look, but discovered that the symbol set in the libsqlcipher0
package has change so much between version 3.4.1 and 4.5.5 that the
build fail.  I suspect this mean a soname transition is needed.  I have
too little experience with maintaining a shared library to feel
comfortable to do this without further research.  Perhaps you can help?

I upgraded to version 3.4.2 in git, and this did not break the build.  A
small set of symbols were added to the library, and I updated
debian/libsqlcipher0.symbols with the list.  Not sure if any of them
should be optional, so I have not uploaded this new version yet.
Perhaps it should go to experimental, or is it better to just move
directly to 4.5.5?  Note, several of the patches did not apply in 4.5.5,
so that will require some investigation too.

On the positive side, I tested a non-Debian build of 4.5.5 and was able
to read messages from the encrypted Signal database, so I now know a
newer version will solve my problem.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1055599: dh_installsystemd tries to start static unit which deb-systemd-invoke rejects

[Daniel Carpenter]

Package: debhelper
Version: 13.11.4

If I include this static (i.e. no [Install] section) systemd service:

# debian/debhelper-example.service
[Service]
Type=oneshot
ExecStart=true

then dh_installsystemd will insert this snippet in postinst:

if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'debhelper-example.service' >/dev/null ||
true

When I install the package, deb-systemd-invoke issues a warning:

debhelper-example.service is a disabled or a static unit, not starting it.

Indeed, such a unit should not be started on package installation (but
rather by a path, socket or timer unit). I notice that dh_installsystemd
produces another snippet which enables the unit if it contains an [Install]
section. I think both snippets should be omitted for static units.

On upgrades, the restart part makes more sense, but for type=oneshot I
think that's only relevant if RemainAfterExit=true.

As a workaround, I can write:

override_dh_installsystemd:
dh_installsystemd --no-start

in debian/rules, but that prevents any units from being started, not just
the static ones. I assume you have to list the static units with
--no-start, and the others without it, but that's more error prone than
letting debhelper handle it.

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

[Santiago Vila]

Package: src:oscrypto
Version: 1.3.0-1
Severity: serious
Tags: ftbfs
Control: close -1 1.3.0-4

Hello. This package currently FTBFS in bookworm:

[...]
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
[...]

Full log here:

https://tests.reproducible-builds.org/debian/rbuild/bookworm/amd64/oscrypto_1.3.0-1.rbuild.log.gz

but I see that the source package in unstable builds ok in bookworm.

Since packages in stable must build in stable, we should
make an upload for bookworm to fix this.

I believe the relevant changes are all that show
when we do this:

git diff debian/1.3.0-2 debian/1.3.0-4

i.e. these three additional patches:

--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,4 @@
 do_not_put_LICENSE_in_egg_info.patch
+libcrypto_ctypes_regex.patch
+openssl_3.0.10.patch
+Make_OpenSSL_version_regexes_more_robust.patch

Note: I joined the Python team recently to fix bugs
like this in stable, so I'd just need the confirmation
that the above is actually what we need to do.

(Unless somebody else wants to take care of this, of course)

Thanks.

Bug#1055597: FTBFS: test failure with Mail-Message 3.014

[gregor herrmann]

Source: libmail-box-perl
Version: 3.010-1
Severity: serious
Tags: upstream ftbfs trixie sid
Justification: fails to build from source
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=150141

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on ci.debian.net, e.g.
https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmail-box-perl/39681951/log.gz
and also upstream at https://rt.cpan.org/Public/Bug/Display.html?id=150141
- --> 
https://www.cpantesters.org/cpan/report/4063279a-6e7d-11ee-a059-85ce9d387f07
libmail-box-perl's t/505parser-bodymp.t fails with
libmail-message-perl_3.014-1

#   Failed test '1 lines 0'
#   at t/505parser-bodymp.t line 68.
#  got: 22
# expected: 21
   
#   Failed test '1 lines 1'
#   at t/505parser-bodymp.t line 68.
#  got: 83
# expected: 82

#   Failed test '1 lines 2'
#   at t/505parser-bodymp.t line 68.
#  got: 35
# expected: 34
# Looks like you failed 3 tests of 313.
t/505parser-bodymp.t .
1..313
ok 1 - creation of parser
ok 2 - 1 from 0
ok 3 - 1 head count
ok 4 - 1 from 0
ok 5 - 1 head count
ok 6 - 1 from 0
ok 7 - 1 head count
ok 8 - 1 from 0
ok 9 - 1 head count
ok 10 - 1 from 0
ok 11 - 1 head count
ok 12 - 1 from 0
ok 13 - 1 head count
ok 14 - 1 from 0
ok 15 - 1 head count
ok 16 - 1 from 0
ok 17 - 1 head count
ok 18 - 1 from 0
ok 19 - 1 head count
ok 20 - 1 from 0
ok 21 - 1 head count
ok 22 - 1 from 0
ok 23 - 1 head count
ok 24 - 1 from 0
ok 25 - 1 head count
ok 26 - 1 from 0
ok 27 - 1 head count
ok 28 - 1 from 0
ok 29 - 1 head count
ok 30 - 1 from 0
ok 31 - 1 head count
ok 32 - 1 from 0
ok 33 - 1 head count
ok 34 - 1 from 0
ok 35 - 1 head count
ok 36 - 1 from 0
ok 37 - 1 head count
ok 38 - 1 from 0
ok 39 - 1 head count
ok 40 - 1 from 0
ok 41 - 1 head count
ok 42 - 1 from 0
ok 43 - 1 head count
ok 44 - 1 body 0
not ok 45 - 1 lines 0
ok 46 - 1 size 0
ok 47 - 1 from 1
ok 48 - 1 head count
ok 49 - 1 from 1
ok 50 - 1 head count
ok 51 - 1 from 1
ok 52 - 1 head count
ok 53 - 1 from 1
ok 54 - 1 head count
ok 55 - 1 from 1
ok 56 - 1 head count
ok 57 - 1 body 1
not ok 58 - 1 lines 1
ok 59 - 1 size 1
ok 60 - 1 from 2
ok 61 - 1 head count
ok 62 - 1 from 2
ok 63 - 1 head count
ok 64 - 1 body 2
not ok 65 - 1 lines 2
ok 66 - 1 size 2
ok 67 - 1 from 3
ok 68 - 1 head count
ok 69 - 1 from 3
ok 70 - 1 head count
ok 71 - 1 from 3
ok 72 - 1 head count
ok 73 - 1 from 3
ok 74 - 1 head count
ok 75 - 1 from 3
ok 76 - 1 head count
ok 77 - 1 from 3
ok 78 - 1 head count
ok 79 - 1 from 3
ok 80 - 1 head count
ok 81 - 1 from 3
ok 82 - 1 head count
ok 83 - 1 from 3
ok 84 - 1 head count
ok 85 - 1 from 3
ok 86 - 1 head count
ok 87 - 1 from 3
ok 88 - 1 head count
ok 89 - 1 from 3
ok 90 - 1 head count
ok 91 - 1 from 3
ok 92 - 1 head count
ok 93 - 1 from 3
ok 94 - 1 head count
ok 95 - 1 from 3
ok 96 - 1 head count
ok 97 - 1 from 3
ok 98 - 1 head count
ok 99 - 1 from 3
ok 100 - 1 head count
ok 101
ok 102 - 2 from 0
ok 103 - 2 head 0
ok 104 - 2 from 0
ok 105 - 2 head 0
ok 106 - 2 from 0
ok 107 - 2 head 0
ok 108 - 2 from 0
ok 109 - 2 head 0
ok 110 - 2 from 0
ok 111 - 2 head 0
ok 112 - 2 from 0
ok 113 - 2 head 0
ok 114 - 2 from 0
ok 115 - 2 head 0
ok 116 - 2 from 0
ok 117 - 2 head 0
ok 118 - 2 from 0
ok 119 - 2 head 0
ok 120 - 2 from 0
ok 121 - 2 head 0
ok 122 - 2 from 0
ok 123 - 2 head 0
ok 124 - 2 from 0
ok 125 - 2 head 0
ok 126 - 2 from 0
ok 127 - 2 head 0
ok 128 - 2 from 0
ok 129 - 2 head 0
ok 130 - 2 from 0
ok 131 - 2 head 0
ok 132 - 2 from 0
ok 133 - 2 head 0
ok 134 - 2 from 0
ok 135 - 2 head 0
ok 136 - 2 from 0
ok 137 - 2 head 0
ok 138 - 2 from 0
ok 139 - 2 head 0
ok 140 - 2 from 0
ok 141 - 2 head 0
ok 142 - 2 from 0
ok 143 - 2 head 0
ok 144 - 2 body 0
ok 145 - 2 size 0
ok 146 - 2 lines 0
ok 147 - 2 names 0
ok 148 - 2 sep 0
ok 149 - 2 from 1
ok 150 - 2 head 1
ok 151 - 2 from 1
ok 152 - 2 head 1
ok 153 - 2 from 1
ok 154 - 2 head 1
ok 155 - 2 from 1
ok 156 - 2 head 1
ok 157 - 2 from 1
ok 158 - 2 head 1
ok 159 - 2 body 1
ok 160 - 2 size 1
ok 161 - 2 lines 1
ok 162 - 2 subject 1
ok 163 - 2 names 1
ok 164 - 2 sep 1
ok 165 - 2 from 2
ok 166 - 2 head 2
ok 167 - 2 from 2
ok 168 - 2 head 2
ok 169 - 2 body 2
ok 170 - 2 size 2
ok 171 - 2 lines 2
ok 172 - 2 names 2
ok 173 - 2 sep 2
ok 174 - 2 from 3
ok 175 - 2 head 3
ok 176 - 2 from 3
ok 177 - 2 head 3
ok 178 - 2 from 3
ok 179 - 2 head 3
ok 180 - 2 from 3
ok 181 - 2 head 3
ok 182 - 2 from 3
ok 183 - 2 head 3
ok 184 - 2 from 3
ok 185 - 2 head 3
ok 186 - 2 from 3
ok 187 - 2 head 3
ok 188 - 2 from 3
ok 189 - 2 head 3
ok 190 - 2 from 3
ok 191 - 2 head 3
ok 192 - 2 from 3
ok 193 - 2 head 3
ok 194 - 2 from 3
ok 195 - 2 head 3
ok 196 - 2 from 3
ok 197 - 2 head 3
ok 198 - 2 from 3
ok 199 - 2 head 3
ok 200 - 2 from 3
ok 201 - 2 head 3
ok 202 - 2 from 3
ok 203 - 2 head 3
ok 204 - 2 from 3
ok 205 - 2 head 3
ok 206 - 2 from 3
ok 207 - 2 head 3
ok 208 - 3 From 0
ok 209 - 3 Head 0
ok 210 - 3 From 0
ok 211 - 3 Head 0
ok 212 - 3 From 0
ok 213 - 3 Head 0
ok 214 - 3 From 0
ok 215 - 3 Head 0
ok 216 - 3 From 0
ok 217 - 3 Head 0

Bug#1032391: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Salvatore Bonaccorso]

Hi Jose,

On Wed, Nov 08, 2023 at 03:48:04PM +, Jose M Calhariz wrote:
> Hi,
> 
> I have been searching for a problem on a 4 new file servers I have
> received, my first idea was an HW problem.  As I have progressed into
> new kernels the pattern was on XFS.  Meanwhile I opened #1040416 so
> this bug can be closed or merge into the new one.

Thanks for confirmation. So let's continue in #1040416, I have closed
#1032391.

Regards,
Salvatore

Bug#1055596: base-files: VERSION_CODENAME is trixie for sid

[sergio]

Package: base-files
Version: 13
Severity: normal

Dear Maintainer,

% grep VERSION_CODENAME /etc/os-release
VERSION_CODENAME=trixie

% apt policy base-files 
base-files:
  Installed: 13
  Candidate: 13
  Version table:
 *** 13 600
600 https://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Bug#1055595: libmfx-gen1.2: New upstream release 23.4.0 available

[Michael Fladischer]

Package: libmfx-gen1.2
Version: 23.2.3-1
Severity: wishlist

Dear Maintainer,

I'm testing video encoding capabilities for AV1 on an Intel ARC770 and the
av1_qsv encoder currently seems to be broken. May a newer release of
onevpl-intel-gpu can fix this.

Thanks,
Michael


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

Kernel: Linux 6.5.0-4-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.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 libmfx-gen1.2 depends on:
ii  libc6   2.37-12
ii  libdrm2 2.4.117-1
ii  libgcc-s1   13.2.0-6
ii  libstdc++6  13.2.0-6
ii  libva-drm2  2.20.0-2
ii  libva2  2.20.0-2

libmfx-gen1.2 recommends no packages.

libmfx-gen1.2 suggests no packages.

-- no debconf information

Bug#1055592: systemd: suspend and hibernate does not longer work

[Luca Boccassi]

On Wed, 08 Nov 2023 16:50:12 +0100 Michael Ott 
wrote:
> Package: systemd
> Version: 255~rc1-3
> Severity: important
> 
> Dear Maintainer,
> 
> Since yesterday hibernate and suspend does not longer work.
journalctl
> show me this:
> 
> systemctl status systemd-suspend.service
> × systemd-suspend.service - System Suspend
>  Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service;
static)
>  Active: failed (Result: signal) since Wed 2023-11-08 16:31:01
CET; 12min ago
>    Docs: man:systemd-suspend.service(8)
> Process: 7133 ExecStart=/usr/lib/systemd/systemd-sleep suspend
(code=killed, signal=ABRT)
>    Main PID: 7133 (code=killed, signal=ABRT)
> CPU: 44ms
> 
> Nov 08 16:31:01 k-c13 systemd[1]: Starting systemd-suspend.service -
System Suspend...
> Nov 08 16:31:01 k-c13 systemd-sleep[7133]: Failed to lock home
directories: Unknown object '/org/freedesktop/home1'.
> Nov 08 16:31:01 k-c13 systemd-sleep[7133]: Performing sleep operation
'suspend'...
> Nov 08 16:31:01 k-c13 systemd-sleep[7133]: *** invalid open64 call:
O_CREAT or O_TMPFILE without mode ***: terminated
> Nov 08 16:31:01 k-c13 systemd[1]: systemd-suspend.service: Main
process exited, code=killed, status=6/ABRT
> Nov 08 16:31:01 k-c13 systemd[1]: systemd-suspend.service: Failed
with result 'signal'.
> Nov 08 16:31:01 k-c13 systemd[1]: Failed to start systemd-
suspend.service - System Suspend.
> 
> I also got this output:
> 
> systemctl list-units --type=mount --all | grep home
> ●
home.mount 
    not-found inactive dead    home.mount
> 
> My home directory looks like that:
> ls -l /home
> total 0
> lrwxrwxrwx 1 root root 18 Nov 24  2018 michael -> /srv/home/michael/
> 
> What is the problem? Since yesterday it works

Please open an issue upstream on Github:

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

-- 
Kind regards,
Luca Boccassi


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

Bug#1055370: Important for a few package: add security support

[Bastien Roucariès]

Hi,

I have one package that fail actually due to this.

A CVE was fixed by coordinating a fix between rmagick and imagemagick and I 
test that the CVE is closed using an autopkgtest

I believe also it is important from a security point of view to add fix for 
security issue

Bastien

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

Bug#1055593: ITP: bifrost -- parallel construction, indexing and querying of de Bruijn graphs

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: bifrost -- parallel construction, indexing and querying of de 
Bruijn graphs
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: bifrost
  Version : 1.3.0
  Upstream Author : Pall Melsted, Guillaume Holley
* URL : https://github.com/pmelsted/bifrost
* License : BSD-2-clause
  Programming Lang: C
  Description : parallel construction, indexing and querying of de Bruijn 
graphs
 Bifrost is a command-line tool for sequencing that features a broad
 range of functions, such as indexing, editing, and querying the graph,
 and includes a graph coloring method that maps each k-mer of the graph
 to the genomes it occurs in.
 .
  * Build, index, color and query the compacted de Bruijn graph
  * No need to build the uncompacted de Bruijn graph
  * Reads or assembled genomes as input
  * Output graph in GFA (can be visualized with Bandage), FASTA or binary
  * Graph cleaning: short tip clipping, etc.
  * Multi-threaded
  * No parameters to estimate with other tools
  * Exact or approximate k-mer search of queries

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/bifrost

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

Hi

On Tue, Nov 07, 2023 at 08:33:58PM +0100, Diederik de Haas wrote:
> Control: found -1 6.1~rc3-1~exp1
> Control: found -1 6.1.55-1
> 
> On Saturday, 4 November 2023 20:35:43 CET Jose M Calhariz wrote:
> > > Ok. Please test (when you have time) 6.1.55-1.
> > 
> > Fail : Linux afs31 6.1.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> > 6.1~rc3-1~exp1 (2022-11-02) x86_64 GNU/Linux
> > 
> > Fail : Linux afs31 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1
> > (2023-09-29) x86_64 GNU/Linux
> > 
> > Done.  I tested even the first 6.1 on Debian.  Both of them failed.
> 
> Thanks, updated metadata accordingly.
> So now we know it's indeed present in the whole 6.1 series.
> 
> > > Unfortunately there isn't a 6.2 kernel uploaded to the Debian archive and
> > > thus not available on snapshot.d.o, but testing 6.3.1-1~exp1 should be
> > > useful.
> 
> Please test with with 6.3.1-1~exp1 to make sure it was fixed then (too).
> 
> Unfortunately, the commit list between 6.1 and 6.3.1 is quite large:
> me@pc:~/dev/kernel.org/linux$ git log --oneline v6.1..v6.3.1 -- fs/xfs | wc -l
> 159
> 
> If that list was small, I could've suggested to try 'backporting' a couple of 
> patches, but that avenue seems rather pointless in this case.
> 
> It's probably also useful to verify whether it's also present in the whole 
> 5.10 series, which should give (even) more data points.
> 
> I think the next step should be to 'forward' this bug report to the upstream 
> mailing list at linux-...@vger.kernel.org

I do not follow closely linux-xfs mailing list, but I think other
people already reported problems with 6.1 and are trying to do the
effort of delimiting the patch and test a backport to 6.1.

Kind regards
Jose M Calhariz

-- 
--
Egoista, s. m. Um sujeito mais interessado em si próprio que
em mim.
-- Ambrose Bierce


signature.asc
Description: PGP signature

Bug#1055591: maintainer-script-lacks-home-in-adduser erroneously raised

[Daniel Carpenter]

Package: lintian
Version: 2.116.3

If my postinst contains:

adduser --system --home=/var/lib/myuser myuser

Then lintian complains:

E: lintian-adduser-bug: maintainer-script-lacks-home-in-adduser "adduser
--system --home=/var/lib/myuser myuser" [postinst:2]

As a workaround, I can wrap adduser or --system in quotes, or remove the
equals sign between --home and the directory. Then lintian does not
complain, even though those variations have the same meaning.

Bug#1055590: r-cran-sf: FTBFS with GDAL 3.8.0

[Bas Couwenberg]

Source: r-cran-sf
Version: 1.0-14+dfsg-1
Severity: important
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: gdal-3.8

Dear Maintainer,


Your package FTBFS with GDAL 3.8.0 from experimental:

 g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG 
-I/usr/include/x86_64-linux-gnu -I/usr/include/webp  -DHAVE_PROJ_H 
-I/usr/include/gdal -I/usr/include -I'/usr/lib/R/site-library/Rcpp/include' 
-fpic  -g -O2 -ffile-prefix-map=/build/reproducible-path/r-base-4.3.2=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -c 
gdal_read.cpp -o gdal_read.o
 In file included from /usr/include/gdal/ogr_geometry.h:36,
  from /usr/include/gdal/ogr_feature.h:36,
  from /usr/include/gdal/ogrsf_frmts.h:35,
  from gdal_read.cpp:4:
 /usr/include/gdal/cpl_json.h:97:36: error: expected ')' before 'nVal'
97 | explicit CPLJSONObject(uint64_t nVal);
   |   ~^
   |)
 /usr/include/gdal/cpl_json.h:119:41: error: 'uint64_t' has not been declared
   119 | void Add(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:119:10: error: 'void CPLJSONObject::Add(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Add(const 
std::string&, int)'
   119 | void Add(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:117:10: note: previous declaration 'void 
CPLJSONObject::Add(const std::string&, int)'
   117 | void Add(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:131:41: error: 'uint64_t' has not been declared
   131 | void Set(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:131:10: error: 'void CPLJSONObject::Set(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Set(const 
std::string&, int)'
   131 | void Set(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:129:10: note: previous declaration 'void 
CPLJSONObject::Set(const std::string&, int)'
   129 | void Set(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:245:14: error: 'uint64_t' has not been declared
   245 | void Add(uint64_t nValue);
   |  ^~~~
 /usr/include/gdal/cpl_json.h:245:10: error: 'void CPLJSONArray::Add(int)' 
cannot be overloaded with 'void CPLJSONArray::Add(int)'
   245 | void Add(uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:243:10: note: previous declaration 'void 
CPLJSONArray::Add(int)'
   243 | void Add(int nValue);
   |  ^~~

The full buildlog is attached.

Kind Regards,

Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: r-cran-classint 
r-cran-dbi r-cran-magrittr r-cran-rcpp r-cran-s2 (>= 1.1.0) r-cran-units (>= 
0.7-0) libgdal-dev
W: Unmet build-dependency in source
dh clean --buildsystem R
   dh_auto_clean -O--buildsystem=R
   dh_autoreconf_clean -O--buildsystem=R
   dh_clean -O--buildsystem=R
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building r-cran-sf using existing 
./r-cran-sf_1.0-14+dfsg.orig.tar.xz
dpkg-source: info: building r-cran-sf in r-cran-sf_1.0-14+dfsg-1.1.debian.tar.xz
dpkg-source: info: building r-cran-sf in r-cran-sf_1.0-14+dfsg-1.1.dsc
I: Generating source changes file for original dsc
dpkg-genchanges: info: not including original source code in upload
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.3062380
I: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow 
/var/cache/pbuilder/build/cow.3062380
I: removed stale ilistfile /var/cache/pbuilder/build/cow.3062380/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.3062380 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.3062380 --buildresult /var/cache/pbuilder/result/ 
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.3062380 cow-shell' 
/home/bas/tmp/debian/r-cran-sf_1.0-14+dfsg-1.1.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Wed Nov  8 16:42:36 CET 2023
I: pbuilder-time-stamp: 1699458156
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting 

Bug#1055589: r-cran-rgdal: FTBFS with GDAL 3.8.0

[Bas Couwenberg]

Source: r-cran-rgdal
Version: 1.6-7+dfsg-1
Severity: important
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: gdal-3.8

Dear Maintainer,

Your package FTBFS with GDAL 3.8.0 from experimental:

 g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -I/usr/include/gdal 
-I/usr/include/x86_64-linux-gnu -I/usr/include/webp  -DPROJ_H_API 
-I'/usr/lib/R/site-library/sp/include' -fpic  -g -O2 
-ffile-prefix-map=/build/reproducible-path/r-base-4.3.2=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -c 
OGR_write.cpp -o OGR_write.o
 In file included from /usr/include/gdal/ogr_geometry.h:36,
  from /usr/include/gdal/ogr_feature.h:36,
  from /usr/include/gdal/ogrsf_frmts.h:35,
  from OGR_write.cpp:2:
 /usr/include/gdal/cpl_json.h:97:36: error: expected ')' before 'nVal'
97 | explicit CPLJSONObject(uint64_t nVal);
   |   ~^
   |)
 /usr/include/gdal/cpl_json.h:119:41: error: 'uint64_t' has not been declared
   119 | void Add(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:119:10: error: 'void CPLJSONObject::Add(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Add(const 
std::string&, int)'
   119 | void Add(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:117:10: note: previous declaration 'void 
CPLJSONObject::Add(const std::string&, int)'
   117 | void Add(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:131:41: error: 'uint64_t' has not been declared
   131 | void Set(const std::string , uint64_t nValue);
   | ^~~~
 /usr/include/gdal/cpl_json.h:131:10: error: 'void CPLJSONObject::Set(const 
std::string&, int)' cannot be overloaded with 'void CPLJSONObject::Set(const 
std::string&, int)'
   131 | void Set(const std::string , uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:129:10: note: previous declaration 'void 
CPLJSONObject::Set(const std::string&, int)'
   129 | void Set(const std::string , int nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:245:14: error: 'uint64_t' has not been declared
   245 | void Add(uint64_t nValue);
   |  ^~~~
 /usr/include/gdal/cpl_json.h:245:10: error: 'void CPLJSONArray::Add(int)' 
cannot be overloaded with 'void CPLJSONArray::Add(int)'
   245 | void Add(uint64_t nValue);
   |  ^~~
 /usr/include/gdal/cpl_json.h:243:10: note: previous declaration 'void 
CPLJSONArray::Add(int)'
   243 | void Add(int nValue);
   |  ^~~

The full buildlog is attached.

Kind Regards,

Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: r-cran-sp libgdal-dev
W: Unmet build-dependency in source
dh clean --buildsystem R
   dh_auto_clean -O--buildsystem=R
   dh_autoreconf_clean -O--buildsystem=R
   dh_clean -O--buildsystem=R
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building r-cran-rgdal using existing 
./r-cran-rgdal_1.6-7+dfsg.orig.tar.xz
dpkg-source: info: building r-cran-rgdal in 
r-cran-rgdal_1.6-7+dfsg-1.1.debian.tar.xz
dpkg-source: info: building r-cran-rgdal in r-cran-rgdal_1.6-7+dfsg-1.1.dsc
I: Generating source changes file for original dsc
dpkg-genchanges: info: not including original source code in upload
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.3036531
I: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow 
/var/cache/pbuilder/build/cow.3036531
I: removed stale ilistfile /var/cache/pbuilder/build/cow.3036531/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.3036531 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.3036531 --buildresult /var/cache/pbuilder/result/ 
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.3036531 cow-shell' 
/home/bas/tmp/debian/r-cran-rgdal_1.6-7+dfsg-1.1.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Wed Nov  8 16:37:33 CET 2023
I: pbuilder-time-stamp: 1699457853
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d 

Bug#1055588: bookworm-pu: package jdupes/1.21.3-1+deb12u1

[Joao Eriberto Mota Filho]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: jdu...@packages.debian.org
Control: affects -1 + src:jdupes

[ Reason ]
jdupes is a fork from fdupes. A bug was introduced by the initial fork some
years ago. The current fdupes on Debian is already fixed. A warning about this
bug was sent by the jdupes upstream (Jody Bruchon) for me via email message.

The help option for jdupes says:
  -d --delete: prompt user for files to preserve and delete all
   others; [...]

Using the command 'jdupes -d .', a prompt will appear:

  Set 1 of 1: keep which files? (1 - 5, [a]ll, [n]one, [l]ink all, [s]ymlink 
all):

It is a mistake to set 2-4 because the jdupes considers one file only. Setting
'2-4', the file 2 will be kept and the files 3 and 4 will be deleted. The
sentence 'keep which files? (1 - 5' induces the users to use a range and it is
not valid. Currently, jdupes is not denying this behaviour and it is generating
a data loss.

[ Impact ]
If the update isn't approved, the users can be induced to select a range of
files and it will cause a possible data loss.

[ Tests ]
Some manual tests have been done over jdupes with a patch created by the
upstream. I also tested fdupes to verify if it would be necessary to open a bug
against this package. The current fdupes has no issues.

[ Risks ]
There are no risks, because the patch to fix the issue is trivial, making a
check for data inputs and generating better messages for the users.

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

[ Changes ]
A patch, created by the upstream, will improve the messages to be shown to
users and will add checks for inputs.

[ Other info ]
No more info.
diff -Nru jdupes-1.21.3/debian/changelog jdupes-1.21.3/debian/changelog
--- jdupes-1.21.3/debian/changelog  2023-02-20 06:51:57.0 -0300
+++ jdupes-1.21.3/debian/changelog  2023-11-08 11:24:57.0 -0300
@@ -1,3 +1,12 @@
+jdupes (1.21.3-1+deb12u1) bookworm; urgency=medium
+
+  * debian/patches/010_fix-data-loss.patch: created to avoid a potential data
+loss caused by a wrong message that induces the users to use a range of
+values with -d option. Currently, the -d option doesn't understand ranges.
+(Closes: #1054237)
+
+ -- Joao Eriberto Mota Filho   Wed, 08 Nov 2023 11:24:57 
-0300
+
 jdupes (1.21.3-1) unstable; urgency=medium
 
   * New upstream version 1.21.3.
diff -Nru jdupes-1.21.3/debian/patches/010_fix-data-loss.patch 
jdupes-1.21.3/debian/patches/010_fix-data-loss.patch
--- jdupes-1.21.3/debian/patches/010_fix-data-loss.patch1969-12-31 
21:00:00.0 -0300
+++ jdupes-1.21.3/debian/patches/010_fix-data-loss.patch2023-11-08 
11:24:57.0 -0300
@@ -0,0 +1,78 @@
+Description: fix potential data loss
+ The help option for jdupes says:
+   -d --delete: prompt user for files to preserve and delete all
+others; [...]
+ .
+ Using the command 'jdupes -d .', a prompt will appear:
+   Set 1 of 1: keep which files? (1 - 5, [a]ll, [n]one, [l]ink 
all, [s]ymlink all):
+ It is a mistake to set 2-4 because the jdupes considers one file
+ only. Setting '2-4', the file 2 will be kept and the files 3 and 4
+ will be deleted. The sentence 'keep which files? (1 - 5' induces
+ the users to use a range and it is not valid. Currently, jdupes is
+ not denying this behaviour and it is generating a data loss.
+ .
+ This patch fixes this issue.
+Author: Jody Bruchon 
+Origin: https://codeberg.org/jbruchon/jdupes/commit/4888e85
+Bug-Debian: https://bugs.debian.org/1054237
+Last-Update: 2023-10-19
+Index: jdupes/act_deletefiles.c
+===
+--- jdupes.orig/act_deletefiles.c
 jdupes/act_deletefiles.c
+@@ -101,8 +101,8 @@ void deletefiles(file_t *files, int prom
+ for (x = 2; x <= counter; x++) preserve[x] = 0;
+   } else do {
+ /* Prompt for files to preserve */
+-printf("Set %u of %u: keep which files? (1 - %u, [a]ll, [n]one",
+-  curgroup, groups, counter);
++printf("Specify multiple files with commas like this: 1,2,4,6\n");
++printf("Set %u of %u: keep which files? (1 - %u, [a]ll, [n]one", 
curgroup, groups, counter);
+ #ifndef NO_HARDLINKS
+printf(", [l]ink all");
+ #endif
+@@ -139,6 +139,33 @@ void deletefiles(file_t *files, int prom
+ 
+ for (x = 1; x <= counter; x++) preserve[x] = 0;
+ 
++  /* Catch attempts to use invalid characters and block them */
++for (char *pscheck = preservestr; *pscheck != '\0'; pscheck++) {
++  switch (*pscheck) {
++case ',':
++   

Bug#1053864: libdrm-amdgpu1: gpu crash on graphics start with Radeon 760M (both sway and gdm3)

[Diederik de Haas]

Control: tag -1 moreinfo

On Fri, 13 Oct 2023 00:47:57 -0400 Simon Heath  wrote:
> Package: libdrm-amdgpu1
> Version: 2.4.115-1
> 
> When GDM3 starts, or when I turn it off and log into the console by hand
> and then start sway or another WM, often the graphics mode switch will
> hang for a few seconds on an unresponsive black screen, then go back to
> a text console for an instant and try again.  This seems to repeat 0-3
> times until eventually it works successfully.  Sometimes it works on the
> first try, often on the second try, etc.
> 
> Once Sway or GDM3 and Xorg have actually started, it *seems* perfectly
> stable, as far as I've seen so far.
> 
> I also see the following errors in dmesg associated with the
> apparent-crash-and-restart:
> 
> [   26.625039] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, 
> signaled seq=23, emitted seq=25
> [   26.625482] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
> information: process  pid 0 thread  pid 0
> [   26.625820] amdgpu :c1:00.0: amdgpu: GPU reset begin!
> [   26.810595] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 
> [amdgpu]] *ERROR* MES failed to response msg=3
> [   26.810761] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to 
> unmap legacy queue
> ...
> Kernel: Linux 6.5.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)

Those messages are actually from the kernel driver.
Can you test whether the issue is still present with kernel 6.5.8-1 (Testing)
and if so, also try it with 6.5.10-1 from Unstable?

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

Bug#1055585: ITP: node-envinfo -- Generate reports of the common details used by Node.js packages

[Bastien Roucariès]

Package: wnpp
Severity: important
Owner: Bastien Roucariès 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-envinfo
  Version : 7.11.0+~cs13.4.1
  Upstream Contact: https://github.com/tabrindle/envinfo#readme
https://github.com/sindresorhus/os-name/tags
https://github.com/sindresorhus/macos-release/tags
https://github.com/sindresorhus/windows-release/tags
https://registry.npmjs.org/yamlify-object
* URL : https://github.com/tabrindle/envinfo#readme
https://github.com/sindresorhus/os-name/tags
https://github.com/sindresorhus/macos-release/tags
https://github.com/sindresorhus/windows-release/tags
https://registry.npmjs.org/yamlify-object
* License : Expat
  Programming Lang: Typescript/javascript
  Description : Generate reports of the common details used by Node.js
packages

Generate reports of the common details used by Node.js packages
 This package generate reports of common software installed on our computer,
 including browser version, Node.js version, Operating System and programming
 language support.
 .
 This is used by webpack a javascript module bundler, for generating build
 time report.
 .
 Node.js is an event-based server-side JavaScript engine.

This package is needed for rebuild from source webpack that is an essential
package of javascript team

Bug#1055586: python-scrypt: Enable tests

[Corey Bryant]

Package: python-scrypt
Version: 0.8.20
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  [ Steve Langasek ]
  * d/rules: re-enable build-time tests, which have been made to pass in
Ubuntu.

  [ James Page ]
  * d/rules: Add some extra cleaning of .so files to dh_auto_clean.
  * d/source/options: Set a sensible exclusion for .egg-info/*
mutations.


Thanks for considering the patch.


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

Kernel: Linux 6.2.0-34-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_WARN, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-scrypt-0.8.20/debian/rules python-scrypt-0.8.20/debian/rules
--- python-scrypt-0.8.20/debian/rules   2022-10-16 16:16:02.0 -0400
+++ python-scrypt-0.8.20/debian/rules   2023-11-08 09:36:25.0 -0500
@@ -9,5 +9,6 @@
 %:
dh $@ --buildsystem=pybuild
 
-override_dh_auto_test:
-   :  # TODO: skip tests, they were never run before anyway
+override_dh_auto_clean:
+   dh_auto_clean --buildsystem=pybuild
+   rm -f *.so
diff -Nru python-scrypt-0.8.20/debian/source/options 
python-scrypt-0.8.20/debian/source/options
--- python-scrypt-0.8.20/debian/source/options  1969-12-31 18:00:00.0 
-0600
+++ python-scrypt-0.8.20/debian/source/options  2023-11-08 09:36:25.0 
-0500
@@ -0,0 +1 @@
+extend-diff-ignore = "^[^/]*[.]egg-info/"

Bug#808425: firefox: hover status becomes false when the mouse pointer is invisible

[Vincent Lefevre]

Control: reassign -1 firefox 119.0-1
Control: retitle -1 firefox: tooltips automatically disappear and hover status 
becomes false when the mouse pointer becomes invisible, e.g. with unclutter
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1863710

I've noticed this bug on my new machine because Debian installs
unclutter by default!

The problem disappears after I kill unclutter.

On 2015-12-20 00:40:38 +0100, Vincent Lefevre wrote:
> Package: iceweasel
> Version: 43.0-1
> Severity: important
> 
> The hover status becomes false when the mouse pointer is invisible.
> To reproduce the bug:
> 
> 1. Install the unclutter package configured with the "-idle 1 -root"
>extra options.
> 
> 2. Start Iceweasel.
> 
> 3. Open https://www.vinc17.net/cijml/index.fr.html
> 
> 4. Put the mouse pointer over "Menu", then move it downwward over
>the menu.
> 
> 5. No longer move the mouse pointer.
> 
> After 1 second, the mouse pointer becomes invisible (this is what
> unclutter does). But the menu disappears (this is a purely CSS menu,
> based on hover). This makes some CSS menus nearly impossible to use
> because the mouse pointer disappears before one can read the menu
> and determine what to do.
> 
> This bug is reproducible in safe mode.
> 
> Firefox Nightly does not have this bug. So, either it is Iceweasel
> specific or it has been fixed upstream.

Well, it seems that it wasn't fixed after all. I don't know why
I couldn't reproduce it with Firefox Nightly at that time.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1055583: base-files: EFI System Partition should mount on /efi not /boot/efi

[Santiago Vila]

El 8/11/23 a las 14:42, kyriah.picc...@easymailer.live escribió:

Package: base-files
Severity: normal

Dear Maintainer,

/efi is a replacement for the historical and now discouraged ESP (EFI System 
Partition) mountpoint /boot/efi.

Systemd upstream agrees: 
https://github.com/systemd/systemd/pull/3757#issuecomment-234290236


I see a few contradictory comments in such thread. Some people saying FHS is 
dead,
others saying it's not.


Using /boot/efi means that /boot must always be mounted in order to mount the 
ESP, but those two partitions are independent so making /boot a prerequisite 
for ESP is needless.

/efi is already documented in debian-stable under `man file-hierarchy`, quoting:

"""
/efi/
If the boot partition /boot/ is maintained separately from the EFI System 
Partition (ESP), the latter is mounted here. Tools that need to operate on the 
EFI system partition should look for it at this mount point first, and fall 
back to /boot/ — if the former doesn't qualify (for example if it is not a 
mount point or does not have the correct file system type MSDOS_SUPER_MAGIC).
"""


Well, please note that base-files currently does not include /boot/efi:

dpkg -S /boot/efi
dpkg-query: no path found matching pattern /boot/efi

Maybe I should ask debian-installer people about this.

Thanks.

Bug#1055573: dh_makeshlibs: time64 compatibility is wrong for some architectures

[Helmut Grohne]

On Wed, Nov 08, 2023 at 10:43:32AM +0100, Helmut Grohne wrote:
> So I think rather than evaluating the bits here, I think we should
> enumerate all architectures that currently are time32 and assume that
> all others (and future ones) will be time64. That list would be:
> 
>  * arm<- I know it's dead. Completeness.
>  * arm64ilp32
>  * armel
>  * armhf
>  * hppa
>  * i386   <- You want to delete this.
>  * m68k
>  * mips
>  * mips32r6
>  * mips32r6el
>  * mipsel
>  * mipsn32
>  * mipsn32el
>  * powerpc
>  * s390
>  * sh3
>  * sh4
>  * sparc

Guillem curated a list in /usr/share/perl5/Dpkg/Vendor/Debian.pm:

 * arm
 * armeb
 * armel
 * armhf
 * hppa
 * i386
 * hurd-i386
 * kfreebsd-i386
 * m68k
 * mips
 * mipsel
 * mipsn32
 * mipsn32el
 * mipsn32r6
 * mipsn32r6el
 * mipsr6
 * mipsr6el
 * nios2
 * powerpc
 * powerpcel
 * powerpcspe
 * s390
 * sh3
 * sh3eb
 * sh4
 * sh4eb
 * sparc

This looks more complete, but it misses arm64ilp32.

Maybe instead of duplicating this, debhelper can access it?

Helmut

Bug#1055510: Best way to coordinate this fix

[Helmut Grohne]

Control: tags -1 + patch

On Tue, Nov 07, 2023 at 09:35:54PM +0100, Helmut Grohne wrote:
> On Tue, Nov 07, 2023 at 08:11:19PM +, Luca Boccassi wrote:
> > On Tue, 7 Nov 2023 at 20:04, Francois Marier  wrote:
> > > What's the best way to coordinate a fix for this?
> > >
> > > I assume that we shouldn't upload a new molly-guard packages until the 
> > > files
> > > have actually moved in the systemd package?
> > >
> > > Should we wait until systemd is in unstable to push a new molly-guard out?
> 
> If the workaround is correctly implemented, it can go to unstable
> directly. Note that it's not simply changing the diversions from the old
> location to the new location. The workaround is duplicating them. At
> that point, you can no longer use --rename and have to do the renaming
> by hand. I'm happy to review a patch. For opensysusers I sent one, but I
> haven't gotten down to molly-guard yet.

Proposed patch attached.

Helmut
diff --minimal -Nru molly-guard-0.7.2/Makefile molly-guard-0.7.2+nmu1/Makefile
--- molly-guard-0.7.2/Makefile  2019-07-09 18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/Makefile 2023-11-08 14:16:52.0 +0100
@@ -1,7 +1,7 @@
 PREFIX?=/usr
 cfgdir?=/etc/molly-guard
-libdir?=/lib
-sbindir?=/sbin
+libdir?=$(PREFIX)/lib
+sbindir?=$(PREFIX)/sbin
 REALPATH?=$(libdir)/molly-guard
 
 all: molly-guard.8 shutdown
diff --minimal -Nru molly-guard-0.7.2/debian/changelog 
molly-guard-0.7.2+nmu1/debian/changelog
--- molly-guard-0.7.2/debian/changelog  2019-07-09 18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/debian/changelog 2023-11-08 14:47:40.0 
+0100
@@ -1,3 +1,11 @@
+molly-guard (0.7.2+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Duplicate aliased diversions for DEP17 M18. (Closes: #-1)
+  * Move all files to /usr.
+
+ -- Helmut Grohne   Wed, 08 Nov 2023 14:47:40 +0100
+
 molly-guard (0.7.2) unstable; urgency=medium
 
   * upload to unstable
diff --minimal -Nru molly-guard-0.7.2/debian/molly-guard.lintian-overrides 
molly-guard-0.7.2+nmu1/debian/molly-guard.lintian-overrides
--- molly-guard-0.7.2/debian/molly-guard.lintian-overrides  2019-07-09 
18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/debian/molly-guard.lintian-overrides 2023-11-08 
14:47:40.0 +0100
@@ -1,9 +1,9 @@
-molly-guard: binary-without-manpage sbin/coldreboot
-molly-guard: binary-without-manpage sbin/halt
-molly-guard: binary-without-manpage sbin/pm-hibernate
-molly-guard: binary-without-manpage sbin/pm-suspend
-molly-guard: binary-without-manpage sbin/pm-suspend-hybrid
-molly-guard: binary-without-manpage sbin/poweroff
-molly-guard: binary-without-manpage sbin/reboot
-molly-guard: binary-without-manpage sbin/shutdown
-molly-guard: diversion-for-unknown-file usr/sbin/* preinst:29
+molly-guard: no-manual-page [usr/sbin/coldreboot]
+molly-guard: no-manual-page [usr/sbin/halt]
+molly-guard: no-manual-page [usr/sbin/pm-hibernate]
+molly-guard: no-manual-page [usr/sbin/pm-suspend]
+molly-guard: no-manual-page [usr/sbin/pm-suspend-hybrid]
+molly-guard: no-manual-page [usr/sbin/poweroff]
+molly-guard: no-manual-page [usr/sbin/reboot]
+molly-guard: no-manual-page [usr/sbin/shutdown]
+molly-guard: diversion-for-unknown-file sbin/* preinst:*
diff --minimal -Nru molly-guard-0.7.2/debian/molly-guard.postrm 
molly-guard-0.7.2+nmu1/debian/molly-guard.postrm
--- molly-guard-0.7.2/debian/molly-guard.postrm 2019-07-09 18:50:53.0 
+0200
+++ molly-guard-0.7.2+nmu1/debian/molly-guard.postrm2023-11-08 
14:47:40.0 +0100
@@ -20,7 +20,11 @@
 case "$1" in
 remove)
 for cmd in halt poweroff reboot shutdown coldreboot ; do
-dpkg-divert --package molly-guard --rename --remove /sbin/$cmd
+dpkg-divert --package molly-guard --no-rename --remove /sbin/$cmd
+dpkg-divert --package molly-guard --no-rename --remove 
"/usr/sbin/$cmd"
+   if test -e "/usr/lib/molly-guard/$cmd"; then
+mv "/usr/lib/molly-guard/$cmd" "/usr/sbin/$cmd"
+fi
 done
 
 for cmd in pm-hibernate pm-suspend pm-suspend-hybrid ; do
diff --minimal -Nru molly-guard-0.7.2/debian/molly-guard.preinst 
molly-guard-0.7.2+nmu1/debian/molly-guard.preinst
--- molly-guard-0.7.2/debian/molly-guard.preinst2019-07-09 
18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/debian/molly-guard.preinst   2023-11-08 
14:47:40.0 +0100
@@ -14,7 +14,7 @@
 
 case "$1" in
 install|upgrade)
-mkdir -p /lib/molly-guard
+mkdir -p /usr/lib/molly-guard
 
 # Cleanup erroneous diversions added in 0.6.0
 for cmd in pm-hibernate pm-suspend pm-suspend-hybrid ; do
@@ -22,11 +22,27 @@
 done
 
 for cmd in halt poweroff reboot shutdown coldreboot ; do
-dpkg-divert --package molly-guard --divert /lib/molly-guard/$cmd 
--rename /sbin/$cmd
+dpkg-divert --package molly-guard --divert 
"/usr/lib/molly-guard/$cmd" --no-rename --add "/usr/sbin/$cmd"
+# 

Bug#981618: libdrm: reduce Build-Depends

[Diederik de Haas]

On Tuesday, 7 November 2023 11:35:28 CET Diederik de Haas wrote:
> I did add the removal of the 2 B-Ds in that MR, but as it doesn't include
> all the items of this bug report, I won't close this bug with those
> changes.

FTR: https://salsa.debian.org/xorg-team/lib/libdrm/-/merge_requests/5

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

Bug#1052474: Merge request for 1052474

[Pushkar Kulkarni]

Submitted
https://salsa.debian.org/java-team/checker-framework-java/-/merge_requests/2