Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

Control: severity -1 normal

On Fri, May 17, 2024 at 08:58:34AM +0100, Mark Hindley wrote:
> On Wed, May 08, 2024 at 01:09:59PM +0100, Mark Hindley wrote:
> > Michael and Steve,
> > 
> > I would appreciate some help here.
> 
> Bump to reset autoremove timer.

Still no response. Downgrading severity to avoid the autoremove dance again.

Mark

Bug#1071140: gcc-14: internal compiler error: in find_or_generate_expression, at tree-ssa-pre.cc:2780 on riscv64

[Jiawei]

We had fixed this on gcc upstream —— 
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9842f99042454bef99fe82506c6dd50f34e283e


Thanks for your report.


BR,

Jiawei

Bug#966621: Make /tmp/ a tmpfs and cleanup /var/tmp/ on a timer by default [was: Re: systemd: tmpfiles.d not cleaning /var/tmp by default]

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Luca Boccassi (2024-05-28 01:54:08)
> Thanks for the useful input, the following has been done:
> 
> - existing installations pre-trixie will get an orphaned tmpfiles.d in
> /etc/ that keeps the existing behaviour unchanged (no cleanup of
> /var/tmp)
> - openssh and tmux have been fixed to provide a tmpfiles.d exception
> to retain their respective files
> - the /tmp/ description in debian-installer has been updated to note
> it is a tmpfs by default (via a commit in partman-basicfilesystems,
> will upload if nobody gets around to it before Trixie's freeze)
> - two paragraphs have been provided for the release notes ticket
> - the changes are also noted in NEWS, with instructions on how to
> override locally
> - as mentioned, the latest upload to unstable makes /tmp/ a tmpfs by
> default and for new installations 10+ days old files in /tmp/ and 30+ days
> old files in /var/tmp/ are cleaned up daily

thank you for having discussed this change on d-devel and for adding
documentation to NEWS and release notes to announce this change. I also think
it is sensible to roll this only out on new installations and to keep the
behaviour on existing setups. Thank you for implementing that as well.

That being said, maybe some Perl wizard knows how to do a flock on a directory
in Perl? I tried this:

use Fcntl qw(LOCK_EX);
opendir(my $handle, ".") or die "opendir: $!";
flock($handle, LOCK_EX) or die "flock: $!";

And got this:

flock() on unopened filehandle $handle at test.pl line 8.
(Are you trying to call flock() on dirhandle $handle?)
flock: Bad file descriptor at test.pl line 8.

Wrapping $handle in fileno() doesn't make a difference either. Perl sources
seem to indicate that directory handles are "evil_fh"?

https://sources.debian.org/src/perl/5.38.2-4/util.c/?hl=3783#L3783

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Yogeswaran Umasankar]

Hi Laszlo,

I am reaching out to you regarding a file conflict between the nanopb
package and the python3-proto-plus package. The conflict involves the
file /usr/lib/python3/dist-packages/proto/__init__.py, which is present
in both packages.

Module name "proto" is part of python3-proto-plus. Renaming proto in
python3-proto-plus will significantly impact the future depended
packages too.

It appears that the nanopb package’s usage of the module name "proto"
does not identify a Python module in the conventional sense. It might be
plausible to make this module private within the nanopb package, which
could resolve the conflict. Would you consider making the module
private? Alternatively, if you have any other suggestions to resolve
this conflict, I am glad to hear them.

Cheers!

Bug#1072203: O: filezilla -- Full-featured graphical FTP/FTPS/SFTP client

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: filezi...@packages.debian.org
Control: affects -1 + src:filezilla

I intend to orphan the filezilla package.

Description: Full-featured graphical FTP/FTPS/SFTP client
 FileZilla is a full-featured FTP client with an easy-to-use GUI.
 .
 It is written in C++ and uses the wxWidgets library.
 .
 FileZilla includes the following features:
   * Supports FTP, FTP over SSL/TLS (FTPS) and SSH File Transfer Protocol (SFTP)
   * IPv6 support
   * Available in more than 40 languages
   * Supports resume and transfer of large files >4GB
   * Easy to use Site Manager and transfer queue
   * Bookmarks
   * Drag & drop support (in application)
   * Speed limits
   * Filename filters
   * Directory comparison
   * Network configuration wizard
   * Remote file editing
   * Keep-alive
   * HTTP/1.1, SOCKS5 and FTP Proxy support
   * Logging to file
   * Synchronized directory browsing
   * Remote file search
   * Tabbed interface to connect to multiple servers

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072202: O: libfilezilla -- build high-performing platform-independent programs

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: libfilezi...@packages.debian.org
Control: affects -1 + src:libfilezilla

I intend to orphan the libfilezilla package.

Description: build high-performing platform-independent programs (development)
 Free, open source C++ library, offering some basic functionality to build
 high-performing, platform-independent programs. Some of the highlights include:
 .
  - A typesafe, multi-threaded event system that's very simple to use yet
extremely efficient
  - Timers for periodic events
  - A datetime class that not only tracks timestamp but also their accuracy,
which simplifies dealing with timestamps originating from different sources
  - Simple process handling for spawning child processes with redirected I/O

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072200: libllvm19: libLLVM.so.19.0 => not found

[Wentao Zhang]

Package: libllvm19
Version: 1:19~++20240529104944+a3f9066e99f3-1~exp1~20240529225109.743
Severity: normal

Hi,

Some library symlinks have changed and as a result:

$ ldd `which clang-19`
linux-vdso.so.1 (0x89cf)
libclang-cpp.so.19.0 => not found
libLLVM.so.19.0 => not found
libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 
(0x89a0)
libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x8996)
libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 
(0x89c4)
libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x897b)
/lib/ld-linux-aarch64.so.1 (0x89cb3000)

I guess for libLLVM we should port part of this commit [1] from branch "18" to
branch "snapshot". I'm still figuring out the needed changes for libclang-cpp.

Also, line #1 and line #3 in this file [2] seem conflicting? (only affecting
branch "18" though)

[1] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/f6c22777bc0687fc548343d3fa565656a1318a18
[2] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/d5a73bd2c9551571084ccecf4307ef94e0b75d96/debian/libllvmX.Y.links.in

Thanks,
Wentao


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

Kernel: Linux 6.7.12-orbstack-00201-g2ddb8f197a46 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libllvm19 depends on:
ii  libc6   2.36-9+deb12u7
ii  libedit23.1-20221030-2
ii  libffi8 3.4.4-1
ii  libgcc-s1   12.2.0-14
ii  libstdc++6  12.2.0-14
ii  libtinfo6   6.4-4
ii  libxml2 2.9.14+dfsg-1.3~deb12u1
ii  libz3-4 4.8.12-3.1
ii  libzstd11.5.4+dfsg2-5
ii  zlib1g  1:1.2.13.dfsg-1

libllvm19 recommends no packages.

libllvm19 suggests no packages.

-- no debconf information

Bug#1072201: rtags: autopkgtest failure due to missing depends on emacs

[Xiyue Deng]

Package: rtags
Version: 2.38-10
Severity: serious

Dear Maintainer,

rtags is now failing autopkgtest due to missing dependency on emacs.
See the autopkgtest regression test from flycheck[1].  It used to work
because it pulls in emacs through the dependency of flycheck.  The
recent upload of flycheck 34.1-1 has downgraded this dependency to
recommends (by me, actually) which triggered this failure.  As this is
causing build failure on rebuild, I'm using the serious severity.

I'll prepare a fix patch/MR soon.

[1] https://ci.debian.net/packages/r/rtags/testing/amd64/47083927/

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

Kernel: Linux 6.1.0-21-amd64 (SMP w/16 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

Bug#1072199: O: compton-- compositor for X11, based on xcompmgr

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: comp...@packages.debian.org
Control: affects -1 + src:compton

I intend to orphan the compton package.

Description: compositor for X11, based on xcompmgr
 compton is a compositor for
X11, based on xcompmgr. In addition to shadows,
 fading and translucency, compton
implements window frame opacity control,
 inactive window transparency, and
shadows on argb windows.

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1064196: tracker-extract: Repeatedly coredumps

[oliver]

This time a trace of tracker-extract from coredumpctl.

   PID: 8695 (tracker-extract)
   UID: 1000 (oliver)
   GID: 1000 (oliver)
Signal: 31 (SYS)
 Timestamp: Thu 2024-05-30 00:46:52 EDT (57min ago)
  Command Line: /usr/libexec/tracker-extract-3
Executable: /usr/libexec/tracker-extract-3
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/background.slice/tracker-extract-3.service

  Unit: user@1000.service
 User Unit: tracker-extract-3.service
 Slice: user-1000.slice
 Owner UID: 1000 (oliver)
   Boot ID: b155d2eaa24748068bc5ffb2a30031b3
Machine ID: 4113bca0c7624baa833583af51ac9106
  Hostname: localhost
   Storage: 
/var/lib/systemd/coredump/core.tracker-extract.1000.b155d2eaa24748068bc5ffb2a30031b3.8695.171704441200.zst 
(present)

  Size on Disk: 451.9K
   Message: Process 8695 (tracker-extract) of user 1000 dumped core.

Module libudev.so.1 from deb systemd-256~rc3-2.amd64
Module libmount.so.1 from deb util-linux-2.40.1-2.amd64
Module libblkid.so.1 from deb util-linux-2.40.1-2.amd64
Stack trace of thread 8697:
#0  0x7f602bc5fe06 epoll_wait (libc.so.6 + 0x10be06)
#1  0x7f602b1c7cba n/a (libmount.so.1 + 0x3bcba)
#2  0x7f602b1c924f mnt_monitor_get_fd 
(libmount.so.1 + 0x3d24f)

#3  0x7f602bfad118 n/a (libgio-2.0.so.0 + 0xd5118)
#4  0x7f602bf2d3c4 n/a (libgio-2.0.so.0 + 0x553c4)
#5  0x7f602c122e3f n/a (libglib-2.0.so.0 + 0x59e3f)
#6  0x7f602c124ec7 n/a (libglib-2.0.so.0 + 0x5bec7)
#7  0x7f602c1254e0 g_main_context_iteration 
(libglib-2.0.so.0 + 0x5c4e0)

#8  0x7f602c125531 n/a (libglib-2.0.so.0 + 0x5c531)
#9  0x7f602c152bb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#10 0x7f602bbdddbb n/a (libc.so.6 + 0x89dbb)
#11 0x7f602bc5f9f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 8699:
#0  0x7f602bbec267 n/a (libc.so.6 + 0x98267)
#1  0x7f602bbed7b9 malloc (libc.so.6 + 0x997b9)
#2  0x7f602c12bdd2 g_malloc (libglib-2.0.so.0 + 
0x62dd2)
#3  0x7f602c147af9 g_strconcat (libglib-2.0.so.0 + 
0x7eaf9)

#4  0x7f602bf49c5e n/a (libgio-2.0.so.0 + 0x71c5e)
#5  0x7f602bf49d70 n/a (libgio-2.0.so.0 + 0x71d70)
#6  0x7f602bf4a440 n/a (libgio-2.0.so.0 + 0x72440)
#7  0x7f602bf4c195 n/a (libgio-2.0.so.0 + 0x74195)
#8  0x7f602bf4e6e8 g_file_attribute_matcher_new 
(libgio-2.0.so.0 + 0x766e8)

#9  0x7f602c0151ea n/a (libgio-2.0.so.0 + 0x13d1ea)
#10 0x7f602bf3d287 n/a (libgio-2.0.so.0 + 0x65287)
#11 0x7f602bf8f4c1 n/a (libgio-2.0.so.0 + 0xb74c1)
#12 0x7f602c153712 n/a (libglib-2.0.so.0 + 0x8a712)
#13 0x7f602c152bb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#14 0x7f602bbdddbb n/a (libc.so.6 + 0x89dbb)
#15 0x7f602bc5f9f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 8695:
#0  0x7f602bc5d9f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7f602c181114 g_cond_wait (libglib-2.0.so.0 + 
0xb8114)

#2  0x7f602bf2d363 n/a (libgio-2.0.so.0 + 0x55363)
#3  0x7f602bf2d468 n/a (libgio-2.0.so.0 + 0x55468)
#4  0x7f602c265e93 n/a (libtracker-miner-3.0.so + 
0x24e93)
#5  0x7f602c266c3d 
tracker_content_identifier_cache_init (libtracker-miner-3.0.so + 0x25c3d)

#6  0x55d528caba49 main (tracker-extract-3 + 0xaa49)
#7  0x7f602bb7bc8a n/a (libc.so.6 + 0x27c8a)
#8  0x7f602bb7bd45 __libc_start_main (libc.so.6 + 
0x27d45)

#9  0x55d528cabeb1 _start (tracker-extract-3 + 0xaeb1)

Stack trace of thread 8698:
#0  0x7f602bc5247f __poll (libc.so.6 + 0xfe47f)
#1  0x7f602c124e15 n/a (libglib-2.0.so.0 + 0x5be15)
#2  0x7f602c1257cf g_main_loop_run 
(libglib-2.0.so.0 + 0x5c7cf)

#3  0x7f602bffca6a n/a (libgio-2.0.so.0 + 0x124a6a)
#4  0x7f602c152bb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#5  0x7f602bbdddbb n/a (libc.so.6 + 0x89dbb)
#6  0x7f602bc5f9f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 8696:
#0  0x7f602bc5d9f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7f602c181114 g_cond_wait (libglib-2.0.so.0 + 
0xb8114)

#2  0x7f602c0ed35b n/a (libglib-2.0.so.0 + 0x2435b)
#3  0x7f602c1533ea n/a (libglib-2.0.so.0 + 0x8a3e

Bug#1072198: xfce4-pulseaudio-plugin: [pipewire] Plugin terminates with signal SIGABRT during Xfce-user logout

[Dirk Lehmann]

Package: xfce4-pulseaudio-plugin
Version: 0.4.8-1+b2
Severity: normal

Dear Maintainer,

I am using the xfce4-pulseaudio-plugin in conjunction with Pipewire.
Since some days, if I'm logging out from Xfce desktop (or shutting
down the computer) the xfce4-pulseaudio-plugin terminates irregular
with signal SIGABRT.  I have GDB attached during that issue, here
follows the output:

**
*** shell ***
/home/user$> ps aux | grep 'wrapper-2.0.*PulseAudio'
user3609  0.0  0.2 453236 38784 ?Sl   07:07   0:00 
/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libpulseaudio-plugin.so 6 
16777239 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio 
sound system
user4259  0.0  0.0   6852  2240 pts/0S+   07:10   0:00 grep 
wrapper-2.0.*PulseAudio
/home/user$> gdb -p 3609
GNU gdb (Debian 13.2-1+b1) 13.2 
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 3609
[New LWP 3617]
[New LWP 3618]
[New LWP 3619]
[New LWP 3641]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f135837a47f in __GI___poll (fds=0x559d0b19def0, nfds=4, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) backtrace
#0  0x7f135837a47f in __GI___poll (fds=0x559d0b19def0, nfds=4, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f13584bce15 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f13584bd7cf in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f13589fd65d in gtk_main () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x559d0a7178d3 in main ()
(gdb) continue
Continuing.

Thread 1 "panel-6-pulseau" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6, 
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
(gdb) backtrace
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x7f1358307b7f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x7f13582b94e2 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#3  0x7f13582a24ed in __GI_abort () at ./stdlib/abort.c:79
#4  0x7f13584800a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f13584e8ffe in g_assertion_message_expr () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f13585eab06 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7f13585c92c3 in g_object_unref () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x559d0a717924 in main ()
(gdb) continue
Continuing.
[Thread 0x7f1354c006c0 (LWP 3641) exited]
[Thread 0x7f13560006c0 (LWP 3618) exited]
[Thread 0x7f1356a006c0 (LWP 3617) exited]
[Thread 0x7f135737da80 (LWP 3609) exited]
[Thread 0x7f13556006c0 (LWP 3619) exited]
[New process 3609]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) q
***
**

After the first `(gdb) continue` a logged off.  Then a `core` file was
written to my home directory in `/home/user`.  I backtraced it with
GDB, here is the output:

**
*** shell ***
/home/user$> gdb -c core 
GNU gdb (Debian 13.2-1+b1) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".

warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping 
note proce

Bug#1072197: O: bglibs-- This package contains a collection of libraries

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: bgl...@packages.debian.org
Control: affects -1 + src:bglibs

I intend to orphan the bglibs package.

Description: This package contains a collection of libraries (development)
 written by Bruce Guenter and put in use in various packages.

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072196: ppa-dev-tools: please remove dependency on old mock

[Alexandre Detiste]

Source: ppa-dev-tools
Version: 0.5.0-1
Severity: normal
X-Debbugs-Cc: Benjamin Drung 

Hi,

I pushed a "no-mock" branch on Salsa with a patch that
replaces the old & deprecated "mock" with
the newer one from the standard library.

I have no idea how Launchpad works so
I please ask you to forward it to the right persons.

Greetings

> https://github.com/testing-cabal/mock
>
> mock is now part of the Python standard library, available as unittest.mock 
> in Python 3.3 onwards.

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Yogeswaran Umasankar]

Hi,

I will reachout to the nanopb maintainer.

Thank you!

Bug#1072195: valgrind: add support for loong64

[Andrius Merkys]

Package: valgrind
Version: 1:3.20.0-2.1
Severity: wishlist
Control: block 1072148 by -1
X-Debbugs-CC: wuruil...@loongson.cn

Hello,

In #1072148 a patch to support loong64 has been proposed in epics-base. 
The proposed patch modifies valgrind header (valgrind/valgrind.h) 
embedded in epics-base source. I would like to un-embed this header in 
the upcoming upload. Therefore to be able to add support for loong64 in 
epics-base, valgrind should support it first.


Andrius

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Helmut Grohne]

Control: reassign -1 python3-proto-plus,nanopb
Control: affects -1 =

On Wed, May 29, 2024 at 08:40:03PM -0400, Yogeswaran Umasankar wrote:
> For now, I am planning to declare nanopb in Conflicts for
> 'python3-proto-plus' binary. Let me know if it might not be advisable.

Doing so violates Debian policy 10.1:

Two different packages must not install programs with different
functionality but with the same filenames.

Arguably, this extends to Python modules. Generally speaking, packages
should be coinstallable unless they fundamentally cannot and in this
case renaming either is a reasonable solution.

I recommend talking to the nanopb maintainer, because what their
package does is unusual. The affected module name "proto" is part of the
python3-proto package, but the nanopb package isn't even identifying a
Python module. It would be plausible to make their module private and
hence resolve the conflict. I very much expect a solution of this bug to
require changes in nanopb of some form.

So this bug likely involves more coordination than originally
anticipated. Keep in mind that every mail to this bug resets the
testing autoremover and the freeze is not exactly close.

Helmut

Bug#1072148: epics-base: please add support for loong64

[Andrius Merkys]

On 2024-05-30 05:17, wuruilong wrote:

I checked valgrind debian package is not supported loongarch architecture.


Thanks for checking. I would like to remove the embedded 
valgrind/valgrind.h and use the header from valgrind package. Thus I 
would suggest implementing loongarch support in valgrind before epics-base.


Andrius

Bug#1072194: O: librepfunc-- set of C++ classes and utilities for building multimedia tools

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: librepf...@packages.debian.org
Control: affects -1 + src:librepfunc

I intend to orphan the librepfunc package.

Description: set of C++ classes and utilities for building multimedia tools
 This
is a collection of utilities and functions used for example in w-scan-cpp
 .
 stri
ng related:
  * LowerCase and UpperCase
  * LeftTrim and RightTrim and Trim
  *
FrontFill and BackFill
  * ReplaceAll
 .
 vector of string related:
  * SplitStr
 .
 n
umber conversion to string or vice versa
  * IntToStr
  * FloatToStr
  * ExpToStr
 
* StrToInt
  * StrToFloat
 .
 print time
  * TimeStr
 .
 other conversions
  *
BCDtoDecimal
 .
 sleep threads
  * Sleep, mSleep, uSleep
 .
 print hex data
  *
HexDump
 .
 files and directories
  * FileExists
  * cFileList
  * ReadFileToStream
 
* ReadFile
  * WriteStreamToFile
  * WriteFile
 .
 start/stop threads from main
thread
  * ThreadBase

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072193: O: w-scan-cpp -- DVB channel scanner (successor of w_scan)

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: w-scan-...@packages.debian.org
Control: affects -1 + src:w-scan-cpp

I intend to orphan the w-scan-cpp package.

Description: DVB channel scanner (successor of w_scan)
 This is w_scan_cpp - a
dtv channel scanner based on VDR (www.tvdr.de)
 and its Plugins.
 .
 w_scan_cpp
supports
 .
DVB-T(2), DVB-C, DVB-S(2), ATSC(VSB && QAM)
SAT>IP
SCR
("Unicable") EN-50494 & EN-50607 (aka. "JESS")
DiSEqC switches
DiSEqC
rotors (Standard & USALS)
various output formats
VDR channels.conf

VLC channels.xspf
dtv scan tables for dvbv5-scan
channels.dat
for the SAT>IP "DVB Viewer Lite for Windows"
(..)
 .
 Some features are
more recent than those of w_scan, other outdated features
 were not ported.

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072192: O: vdr-plugin-wirbelscan -- Wirbelscan plugin for VDR

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: vdr-plugin-wirbels...@packages.debian.org
Control: affects -1 + src:vdr-plugin-wirbelscan

I intend to orphan the vdr-plugin-wirbelscan package.

Description: Wirbelscan plugin for VDR
 A plugin for the Video Disk Recorder (VDR) that scans for available Digital
 Television (DTV) on the following channels.
 .
   * Digital Video Broadcasting (DVB).
   * Vestigial Sideband (VSB).
   * Quadrature Amplitude Modulation (QAM).
   * SAT>IP, technology (SATIP).

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1059414: open-ath9k-htc-firmware: diff for NMU version 1.4.0-108-gd856466+dfsg1-1.5

[Oleksij Rempel]

Hi Chris,

I'm developer, not the package maintainer. On the source code side
didn't happened anything for some years, so there are no conflicts are
expected. From my perspective there is no need to wait.

Regards,

Oleksij

Bug#1064196: tracker-extract: Repeatedly coredumps

[oliver]

Recently I have been encountering this on trixie/sid.

Here are the error messages:

May 30 00:04:15 localhost systemd[1308]: Failed to start 
tracker-extract-3.service - Tracker metadata extractor.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Failed with result 'core-dump'.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Start request repeated too quickly.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Scheduled restart job, restart counter is at 5.
May 30 00:04:15 localhost systemd[1308]: Failed to start 
tracker-extract-3.service - Tracker metadata extractor.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Failed with result 'core-dump'.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: Main 
process exited, code=dumped, status=31/SYS


Here is the stack trace:

Process 4391 (tracker-extract) of user 1000 dumped core.

Module libudev.so.1 from deb systemd-256~rc3-2.amd64
Module libmount.so.1 from deb util-linux-2.40.1-2.amd64
Module libblkid.so.1 from deb util-linux-2.40.1-2.amd64
Stack trace of thread 4394:
#0  0x7eff31b28e06 epoll_wait (libc.so.6 + 0x10be06)
#1  0x7eff315adcba n/a (libmount.so.1 + 0x3bcba)
#2  0x7eff315af24f mnt_monitor_get_fd (libmount.so.1 + 0x3d24f)
#3  0x7eff31e76118 n/a (libgio-2.0.so.0 + 0xd5118)
#4  0x7eff31df63c4 n/a (libgio-2.0.so.0 + 0x553c4)
#5  0x7eff31febe3f n/a (libglib-2.0.so.0 + 0x59e3f)
#6  0x7eff31fedec7 n/a (libglib-2.0.so.0 + 0x5bec7)
#7  0x7eff31fee4e0 g_main_context_iteration (libglib-2.0.so.0 + 0x5c4e0)
#8  0x7eff31fee531 n/a (libglib-2.0.so.0 + 0x5c531)
#9  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#10 0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#11 0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 4396:
#0  0x7eff31fb62e0 n/a (libglib-2.0.so.0 + 0x242e0)
#1  0x7eff3201c76a n/a (libglib-2.0.so.0 + 0x8a76a)
#2  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#3  0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#4  0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 4391:
#0  0x7eff31b269f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7eff3204a114 g_cond_wait (libglib-2.0.so.0 + 0xb8114)
#2  0x7eff31df6363 n/a (libgio-2.0.so.0 + 0x55363)
#3  0x7eff31df6468 n/a (libgio-2.0.so.0 + 0x55468)
#4  0x7eff3212ee93 n/a (libtracker-miner-3.0.so + 0x24e93)
#5  0x7eff3212fc3d tracker_content_identifier_cache_init 
(libtracker-miner-3.0.so + 0x25c3d)

#6  0x55e5acdf1a49 main (tracker-extract-3 + 0xaa49)
#7  0x7eff31a44c8a n/a (libc.so.6 + 0x27c8a)
#8  0x7eff31a44d45 __libc_start_main (libc.so.6 + 0x27d45)
#9  0x55e5acdf1eb1 _start (tracker-extract-3 + 0xaeb1)

Stack trace of thread 4395:
#0  0x7eff31b1b47f __poll (libc.so.6 + 0xfe47f)
#1  0x7eff31fede15 n/a (libglib-2.0.so.0 + 0x5be15)
#2  0x7eff31fee7cf g_main_loop_run (libglib-2.0.so.0 + 0x5c7cf)
#3  0x7eff31ec5a6a n/a (libgio-2.0.so.0 + 0x124a6a)
#4  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#5  0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#6  0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 4393:
#0  0x7eff31b269f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7eff3204a114 g_cond_wait (libglib-2.0.so.0 + 0xb8114)
#2  0x7eff31fb635b n/a (libglib-2.0.so.0 + 0x2435b)
#3  0x7eff3201c3ea n/a (libglib-2.0.so.0 + 0x8a3ea)
#4  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#5  0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#6  0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)
ELF object binary architecture: AMD x86-64


OpenPGP_0x96B430AAF6F4B86F.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1060772: [Python-modules-team] Bug#1060772: python3-jupyterlab: Using node-corepack downloads yarnpkg from Internet

[Yadd]

Hi,

depending on the use of "jupyterlab build":
 - when used manually, may prefer to launch yarnpkg
 - when used under Debian build/test, may prefer to use
   pkgjs-install-minimal

So proposition:
 - drop the patch 0003-Use-system-provided-yarn.js.patch
 - build a custom yarn.js that calls yarnpks or pkg-install-minimal
   depending on an environment variable

Bug#1060011:

[Jaikumar Sharma]

I've also stumbled upon due to this bug , is there any workaround available?

Thanks.

Bug#1072148: epics-base: please add support for loong64

[wuruilong]

在 2024/5/29 下午9:30, Andrius Merkys 写道:

On 2024-05-29 11:32, wuruilong wrote:
Modify the valgrind header file because valgrind's code has gone too 
long without loongarch support.


Does the valgrind Debian package support loong64? If so, the embedded 
valgrind/valgrind.h can be replaced with the header from Debian package.


Andrius


I checked valgrind debian package is not supported loongarch architecture.

wuruilong

Bug#1059283: mate-settings-daemon: diff for NMU version 1.26.1-1.1

[Chris Hofstaedtler]

Control: tags 1059283 + pending


Dear maintainer,

I've prepared an NMU for mate-settings-daemon (versioned as 1.26.1-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru mate-settings-daemon-1.26.1/debian/changelog mate-settings-daemon-1.26.1/debian/changelog
--- mate-settings-daemon-1.26.1/debian/changelog	2024-01-06 08:00:22.0 +0100
+++ mate-settings-daemon-1.26.1/debian/changelog	2024-05-30 03:21:29.0 +0200
@@ -1,3 +1,10 @@
+mate-settings-daemon (1.26.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #1059283)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:21:29 +0200
+
 mate-settings-daemon (1.26.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mate-settings-daemon-1.26.1/debian/control mate-settings-daemon-1.26.1/debian/control
--- mate-settings-daemon-1.26.1/debian/control	2024-01-06 08:00:14.0 +0100
+++ mate-settings-daemon-1.26.1/debian/control	2024-05-30 03:21:26.0 +0200
@@ -33,6 +33,8 @@
libxrandr-dev,
libxt-dev,
mate-common (>= 1.18),
+   pkgconf,
+   systemd-dev,
x11proto-kb-dev,
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
diff -Nru mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install
--- mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install	2019-08-11 13:32:02.0 +0200
+++ mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install	2024-05-30 03:21:26.0 +0200
@@ -1,6 +1,6 @@
 #! /usr/bin/dh-exec
 
-[linux-any] usr/lib/udev/rules.d/ lib/udev
+[linux-any] usr/lib/udev/rules.d/ ${deb_udevdir}
 usr/share/glib-2.0/
 usr/share/icons/
 usr/share/locale/
diff -Nru mate-settings-daemon-1.26.1/debian/rules mate-settings-daemon-1.26.1/debian/rules
--- mate-settings-daemon-1.26.1/debian/rules	2024-01-06 08:00:22.0 +0100
+++ mate-settings-daemon-1.26.1/debian/rules	2024-05-30 03:21:26.0 +0200
@@ -9,8 +9,10 @@
 DEB_HOST_ARCH_OS?=$(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
 ifeq (,$(filter linux, $(DEB_HOST_ARCH_OS)))
 WITHOUT_RFKILL = "--disable-rfkill"
+export deb_udevdir =
 else
 WITHOUT_RFKILL = ""
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
 endif
 
 

Bug#1054013: dnssec-trigger: diff for NMU version 0.17+repack-5.2

[Chris Hofstaedtler]

Control: tags 1054013 + pending


Dear maintainer,

I've prepared an NMU for dnssec-trigger (versioned as 0.17+repack-5.2) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru dnssec-trigger-0.17+repack/debian/changelog dnssec-trigger-0.17+repack/debian/changelog
--- dnssec-trigger-0.17+repack/debian/changelog	2023-05-11 19:40:04.0 +0200
+++ dnssec-trigger-0.17+repack/debian/changelog	2024-05-30 03:23:48.0 +0200
@@ -1,3 +1,12 @@
+dnssec-trigger (0.17+repack-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Defer placement of systemd units to systemd.pc. (Closes: #1054013)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:23:48 +0200
+
 dnssec-trigger (0.17+repack-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dnssec-trigger-0.17+repack/debian/control dnssec-trigger-0.17+repack/debian/control
--- dnssec-trigger-0.17+repack/debian/control	2023-05-11 19:39:30.0 +0200
+++ dnssec-trigger-0.17+repack/debian/control	2024-05-30 03:23:45.0 +0200
@@ -11,8 +11,10 @@
 	   libgtk2.0-dev,
 	   libldns-dev (>= 1.6.14-1~),
 	   lsb-base,
+	   pkgconf,
 	   python3,
-   sensible-utils
+	   sensible-utils,
+	   systemd-dev,
 Standards-Version: 4.3.0
 Homepage: https://www.nlnetlabs.nl/projects/dnssec-trigger/
 Vcs-Git: https://salsa.debian.org/dns-team/dnssec-trigger.git
diff -Nru dnssec-trigger-0.17+repack/debian/rules dnssec-trigger-0.17+repack/debian/rules
--- dnssec-trigger-0.17+repack/debian/rules	2020-08-24 20:24:56.0 +0200
+++ dnssec-trigger-0.17+repack/debian/rules	2024-05-30 03:23:45.0 +0200
@@ -21,7 +21,7 @@
 		--with-python=/usr/bin/python3 \
 		--with-hooks=networkmanager \
 		--with-gui=gtk \
-		--with-unitdir=/lib/systemd/system \
+		--with-unitdir=$(shell pkgconf --variable=systemdsystemunitdir systemd) \
 		--with-rundir=/run \
 		--with-keydir=/etc/dnssec-trigger \
 		--with-pidfile=/run/dnssec-triggerd.pid \

Bug#1063693: xdm: diff for NMU version 1:1.1.11-3.1

[Chris Hofstaedtler]

Control: tags 1063693 + pending


Dear maintainer,

I've prepared an NMU for xdm (versioned as 1:1.1.11-3.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u xdm-1.1.11/debian/changelog xdm-1.1.11/debian/changelog
--- xdm-1.1.11/debian/changelog
+++ xdm-1.1.11/debian/changelog
@@ -1,3 +1,12 @@
+xdm (1:1.1.11-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Let systemd.pc determine the location of systemd units. (Closes: #1063693)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:12:21 +0200
+
 xdm (1:1.1.11-3) unstable; urgency=medium
 
   * Team upload.
diff -u xdm-1.1.11/debian/control xdm-1.1.11/debian/control
--- xdm-1.1.11/debian/control
+++ xdm-1.1.11/debian/control
@@ -5,8 +5,9 @@
 Uploaders: Cyril Brulebois 
 Build-Depends:
  debhelper (>= 9),
+ dh-exec,
  dpkg-dev (>= 1.16.1),
- pkg-config,
+ pkgconf,
  libxmu-dev (>= 1:1.0.1),
  libx11-dev (>= 2:1.0.0),
  libxau-dev (>= 1:1.0.0),
@@ -18,6 +19,7 @@
  quilt,
  automake,
  libtool,
+ systemd-dev,
  xutils-dev,
 Standards-Version: 3.9.6
 Vcs-Git: git://anonscm.debian.org/pkg-xorg/app/xdm
diff -u xdm-1.1.11/debian/rules xdm-1.1.11/debian/rules
--- xdm-1.1.11/debian/rules
+++ xdm-1.1.11/debian/rules
@@ -13,6 +13,8 @@
 
 include debian/xsfbs/xsfbs.mk
 
+export deb_systemdsystemunitdir := $(shell pkgconf --variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 confflags += \
 	--prefix=/usr \
 	--mandir=\$${prefix}/share/man \
@@ -24,7 +26,7 @@
 	--with-pixmapdir=/usr/share/X11/xdm/pixmaps \
 	--with-color-pixmap=debian.xpm \
 	--with-bw-pixmap=debianbw.xpm \
-	--with-systemdsystemunitdir=/lib/systemd/system \
+	--with-systemdsystemunitdir \
 	--disable-xdm-auth \
 	--with-xft \
 	--disable-silent-rules \
@@ -126,6 +128,7 @@
 	dh_testroot
 
 	dh_installdocs
+	chmod +x debian/xdm.install
 	dh_install --sourcedir=debian/tmp --list-missing
 	dh_installchangelogs ChangeLog
 	dh_installinit --noscripts
diff -u xdm-1.1.11/debian/xdm.install xdm-1.1.11/debian/xdm.install
--- xdm-1.1.11/debian/xdm.install
+++ xdm-1.1.11/debian/xdm.install
@@ -1,3 +1,4 @@
+#!/usr/bin/dh-exec
 etc/X11/app-defaults/Chooser
 etc/X11/xdm/Xaccess
 etc/X11/xdm/Xreset
@@ -10,7 +11,7 @@
 etc/X11/xdm/xdm-config
 etc/X11/xdm/xdm.options
 etc/insserv.conf.d/xdm
-lib/systemd/system/xdm.service
+${deb_systemdsystemunitdir}/xdm.service
 usr/bin/xdm
 usr/lib/X11/xdm/chooser
 usr/lib/X11/xdm/libXdmGreet.so

Bug#1072190: ITS: psensor

[xiao sheng wen]

Package: psensor
Version: 1.1.5-1.4
Severity: important
X-Debbugs-Cc: mo...@debian.org, sudipm.mukher...@gmail.com, b...@debian.org, 
locutusofb...@debian.org, m...@qa.debian.org, atzli...@sina.com

Hi,

psensor is in clear need of some love and care.

It has many NMU and many bugs not fix.

The current maintainers also agree to somebody adopt it in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953896#27

Regards,

-- System Information:
Release:12.5.2
Codename:   bookworm
Architecture: x86_64

Kernel: Linux 6.8.11-amd64 (SMP w/16 CPU threads; PREEMPT)
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 psensor depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libatasmart4 0.19-5
ii  libayatana-appindicator3-1   0.5.92-1
ii  libc62.36-9+deb12u7
ii  libcairo21.16.0-7
ii  libcurl3-gnutls  7.88.1-10+deb12u5
ii  libglib2.0-0 2.74.6-2+deb12u2
ii  libgtk-3-0   3.24.38-2~deb12u1
ii  libgtop-2.0-11   2.40.0-2
ii  libjson-c5   0.16-2
ii  libnotify4   0.8.1-1
ii  libsensors5  1:3.6.0-7.1
ii  libudisks2-0 2.9.4-4
ii  libx11-6 2:1.8.4-2+deb12u2
ii  libxnvctrl0  525.85.05-3~deb12u1
ii  psensor-common   1.1.5-1.4

psensor recommends no packages.

psensor suggests no packages.

-- no debconf information

Bug#1063572: jfsutils: diff for NMU version 1.1.15-5.1

[Chris Hofstaedtler]

Control: tags 1063572 + pending


Dear maintainer,

I've prepared an NMU for jfsutils (versioned as 1.1.15-5.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru jfsutils-1.1.15/debian/changelog jfsutils-1.1.15/debian/changelog
--- jfsutils-1.1.15/debian/changelog	2020-06-23 22:31:15.0 +0200
+++ jfsutils-1.1.15/debian/changelog	2024-05-30 03:10:37.0 +0200
@@ -1,3 +1,12 @@
+jfsutils (1.1.15-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Move files to /usr for DEP17 (closes: #1063572).
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:10:37 +0200
+
 jfsutils (1.1.15-5) unstable; urgency=medium
 
   * Update Standards-Version to 4.5.0 .
diff -Nru jfsutils-1.1.15/debian/jfsutils.install jfsutils-1.1.15/debian/jfsutils.install
--- jfsutils-1.1.15/debian/jfsutils.install	2016-11-07 18:39:06.0 +0100
+++ jfsutils-1.1.15/debian/jfsutils.install	2024-05-30 03:10:36.0 +0200
@@ -1 +1 @@
-debian/tmp/sbin
+debian/tmp/usr/sbin
diff -Nru jfsutils-1.1.15/debian/jfsutils-udeb.install jfsutils-1.1.15/debian/jfsutils-udeb.install
--- jfsutils-1.1.15/debian/jfsutils-udeb.install	2016-11-07 18:39:06.0 +0100
+++ jfsutils-1.1.15/debian/jfsutils-udeb.install	2024-05-30 03:10:36.0 +0200
@@ -1 +1 @@
-debian/tmp/sbin
\ No newline at end of file
+debian/tmp/usr/sbin
diff -Nru jfsutils-1.1.15/debian/rules jfsutils-1.1.15/debian/rules
--- jfsutils-1.1.15/debian/rules	2016-11-07 18:39:29.0 +0100
+++ jfsutils-1.1.15/debian/rules	2024-05-30 03:10:36.0 +0200
@@ -25,5 +25,4 @@
 	LDFLAGS += -Wl,--no-relax
 endif
 
-DEB_CONFIGURE_USER_FLAGS := --sbindir=/sbin
 DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(CURDIR)/debian/tmp

Bug#1054088: sanoid: let dh_installsystemd choose the location of units

[Chris Hofstaedtler]

Hi,

On Tue, Oct 17, 2023 at 11:08:24AM -0400, Michael Jeanson wrote:
> On 2023-10-16 15:38, Helmut Grohne wrote:
> > Source: sanoid
> > Version: 2.2.0-1
> > Tags: patch
> > User: helm...@debian.org
> > Usertags: dep17m2
> > 
> > We want to move all aliased files from / to /usr to finalize the
> > /usr-merge transition via DEP17
[..]
> 
> Thanks for the patch, it will be included in the next upload.

Please make sure this lands in trixie before the transition freeze.
Now would be a great time.

Chris

Bug#1071911: debiman: diff for NMU version 0.0~git20220907.a582536-1.1

[Chris Hofstaedtler]

Control: tags 1071911 + patch
Control: tags 1071911 + pending


Dear maintainer,

I've prepared an NMU for debiman (versioned as 0.0~git20220907.a582536-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru debiman-0.0~git20220907.a582536/debian/changelog debiman-0.0~git20220907.a582536/debian/changelog
--- debiman-0.0~git20220907.a582536/debian/changelog	2022-10-22 10:38:42.0 +0200
+++ debiman-0.0~git20220907.a582536/debian/changelog	2024-05-30 03:07:49.0 +0200
@@ -1,3 +1,10 @@
+debiman (0.0~git20220907.a582536-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd unit into /usr/lib. (Closes: #1071911)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:07:49 +0200
+
 debiman (0.0~git20220907.a582536-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru debiman-0.0~git20220907.a582536/debian/install debiman-0.0~git20220907.a582536/debian/install
--- debiman-0.0~git20220907.a582536/debian/install	2022-10-22 09:34:00.0 +0200
+++ debiman-0.0~git20220907.a582536/debian/install	2024-05-30 03:07:48.0 +0200
@@ -1 +1 @@
-debiman-auxserver.service lib/systemd/system
+debiman-auxserver.service usr/lib/systemd/system

Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Chris Hofstaedtler]

On Wed, May 29, 2024 at 12:57:21PM -0300, Lucas Castro wrote:
> I would like the NMU be canceled.

> cancel lsm_1.0.4-2.1_source.changes
Files removed from 3-day: lsm_1.0.4-2.1_source.changes lsm_1.0.4-2.1.dsc 
lsm_1.0.4-2.1.debian.tar.xz lsm_1.0.4-2.1_arm64.buildinfo

I'm looking forward to your fix landing before the trixie transition
freeze.

Chris

Bug#1051460: crowdsec-custom-bouncer: move systemd units to /usr

[Chris Hofstaedtler]

On Tue, Dec 19, 2023 at 04:36:16AM +0100, Cyril Brulebois wrote:
> Chris Hofstaedtler  (2023-12-19):
> > If you can reasonably expect that the package in question will not
> > change name, or split out or move the systemd unit files in any
> > other way, than strictly from /lib to /usr/lib, then this is safe to
> > do now.
> 
> That's very safe to assume, yes. If that's enough to guarantee that I
> won't actually be generating another problem down the line, I'm happy to
> implement this change.

Yes, having migrated enough packages I (we) believe this is safe.

Please land this in trixie before the transition freeze.

Thanks,
Chris

Bug#1054093: monit: diff for NMU version 1:5.33.0-2.1

[Chris Hofstaedtler]

Control: tags 1054093 + pending


Dear maintainer,

I've prepared an NMU for monit (versioned as 1:5.33.0-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru monit-5.33.0/debian/changelog monit-5.33.0/debian/changelog
--- monit-5.33.0/debian/changelog	2023-08-20 22:27:26.0 +0200
+++ monit-5.33.0/debian/changelog	2024-05-30 02:57:21.0 +0200
@@ -1,3 +1,12 @@
+monit (1:5.33.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Let dh_installsystemd choose the location of units (Closes: #1054093)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:57:21 +0200
+
 monit (1:5.33.0-2) unstable; urgency=medium
 
   * debian/conf-available/:
diff -Nru monit-5.33.0/debian/monit.install monit-5.33.0/debian/monit.install
--- monit-5.33.0/debian/monit.install	2023-08-20 22:26:59.0 +0200
+++ monit-5.33.0/debian/monit.install	2024-05-30 02:57:07.0 +0200
@@ -2,4 +2,3 @@
 debian/conf-available/* etc/monit/conf-available/
 debian/templates/* etc/monit/templates/
 system/bash/monit usr/share/bash-completion/completions/
-system/startup/monit.service lib/systemd/system/
diff -Nru monit-5.33.0/debian/monit.service monit-5.33.0/debian/monit.service
--- monit-5.33.0/debian/monit.service	1970-01-01 01:00:00.0 +0100
+++ monit-5.33.0/debian/monit.service	2023-02-11 11:29:19.0 +0100
@@ -0,0 +1,33 @@
+# This file is systemd template for monit service. To
+# register monit with systemd, place the monit.service file
+# to the /lib/systemd/system/ directory and then start it
+# using systemctl (see bellow).
+#
+# Enable monit to start on boot:
+# systemctl enable monit.service
+#
+# Start monit immediately:
+# systemctl start monit.service
+#
+# Stop monit:
+# systemctl stop monit.service
+#
+# Status:
+# systemctl status monit.service
+
+[Unit]
+Description=Pro-active monitoring utility for unix systems
+After=network-online.target
+Documentation=man:monit(1) https://mmonit.com/wiki/Monit/HowTo
+
+[Service]
+Type=simple
+KillMode=process
+ExecStart=/usr/local/bin/monit -I
+ExecStop=/usr/local/bin/monit quit
+ExecReload=/usr/local/bin/monit reload
+Restart=on-abnormal
+StandardOutput=null
+
+[Install]
+WantedBy=multi-user.target

Bug#1054089: php-defaults: diff for NMU version 93+nmu1

[Chris Hofstaedtler]

Control: tags 1054089 + pending


Dear maintainer,

I've prepared an NMU for php-defaults (versioned as 93+nmu1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru php-defaults-93/debian/changelog php-defaults-93+nmu1/debian/changelog
--- php-defaults-93/debian/changelog	2022-07-13 10:19:37.0 +0200
+++ php-defaults-93+nmu1/debian/changelog	2024-05-30 02:53:37.0 +0200
@@ -1,3 +1,12 @@
+php-defaults (93+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Install systemd units using dh helpers. (Closes: #1054089)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:53:37 +0200
+
 php-defaults (93) unstable; urgency=medium
 
   * Bump the default and supported version to PHP 8.2
diff -Nru php-defaults-93/debian/php-common.install php-defaults-93+nmu1/debian/php-common.install
--- php-defaults-93/debian/php-common.install	2022-07-13 10:19:37.0 +0200
+++ php-defaults-93+nmu1/debian/php-common.install	2024-05-30 02:53:37.0 +0200
@@ -3,6 +3,4 @@
 php-maintscript-helper /usr/lib/php/
 phpenmod /usr/sbin/
 phpquery /usr/sbin/
-phpsessionclean.service /lib/systemd/system/
-phpsessionclean.timer /lib/systemd/system/
 sessionclean /usr/lib/php/
diff -Nru php-defaults-93/debian/php-common.phpsessionclean.service php-defaults-93+nmu1/debian/php-common.phpsessionclean.service
--- php-defaults-93/debian/php-common.phpsessionclean.service	1970-01-01 01:00:00.0 +0100
+++ php-defaults-93+nmu1/debian/php-common.phpsessionclean.service	2022-07-13 10:19:37.0 +0200
@@ -0,0 +1,9 @@
+[Unit]
+Description=Clean php session files
+
+[Service]
+Type=oneshot
+ExecStart=/usr/lib/php/sessionclean
+ProtectHome=true
+ProtectSystem=true
+PrivateTmp=true
diff -Nru php-defaults-93/debian/php-common.phpsessionclean.timer php-defaults-93+nmu1/debian/php-common.phpsessionclean.timer
--- php-defaults-93/debian/php-common.phpsessionclean.timer	1970-01-01 01:00:00.0 +0100
+++ php-defaults-93+nmu1/debian/php-common.phpsessionclean.timer	2022-07-13 10:19:37.0 +0200
@@ -0,0 +1,9 @@
+[Unit]
+Description=Clean PHP session files every 30 mins
+
+[Timer]
+OnCalendar=*-*-* *:09,39:00
+Persistent=true
+
+[Install]
+WantedBy=timers.target
diff -Nru php-defaults-93/debian/rules php-defaults-93+nmu1/debian/rules
--- php-defaults-93/debian/rules	2022-07-13 10:19:37.0 +0200
+++ php-defaults-93+nmu1/debian/rules	2024-05-30 02:53:37.0 +0200
@@ -86,7 +86,8 @@
 	dh_gencontrol --remaining-packages -- -v$(PHP_DEB_VERSION)
 
 override_dh_systemd_enable:
-	dh_systemd_enable --package=php-common phpsessionclean.timer
+	dh_systemd_enable --package=php-common --name phpsessionclean phpsessionclean.timer
+	dh_systemd_enable --package=php-common --name phpsessionclean --no-enable phpsessionclean.service
 
 override_dh_systemd_start:
 	dh_systemd_start --package=php-common phpsessionclean.timer

Bug#1054191: memlockd: diff for NMU version 1.3.1-1.1

[Chris Hofstaedtler]

Control: tags 1054191 + pending


Dear maintainer,

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

Regards.

diff -Nru memlockd-1.3.1/changes.txt memlockd-1.3.1/changes.txt
--- memlockd-1.3.1/changes.txt	2023-09-30 03:49:17.0 +0200
+++ memlockd-1.3.1/changes.txt	2024-05-30 02:50:10.0 +0200
@@ -1,3 +1,12 @@
+memlockd (1.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Do not install a possibly empty /lib/systemd/system. (Closes: #1054191)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:50:10 +0200
+
 memlockd (1.3.1-1) unstable; urgency=medium
 
   * Convert to source format 3.0, closes: #1043214
diff -Nru memlockd-1.3.1/debian/changelog memlockd-1.3.1/debian/changelog
--- memlockd-1.3.1/debian/changelog	2023-09-30 03:49:17.0 +0200
+++ memlockd-1.3.1/debian/changelog	2024-05-30 02:50:10.0 +0200
@@ -1,3 +1,12 @@
+memlockd (1.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Do not install a possibly empty /lib/systemd/system. (Closes: #1054191)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:50:10 +0200
+
 memlockd (1.3.1-1) unstable; urgency=medium
 
   * Convert to source format 3.0, closes: #1043214
diff -Nru memlockd-1.3.1/debian/dirs memlockd-1.3.1/debian/dirs
--- memlockd-1.3.1/debian/dirs	2012-06-16 07:33:33.0 +0200
+++ memlockd-1.3.1/debian/dirs	2024-05-30 02:49:57.0 +0200
@@ -2,4 +2,3 @@
 etc/default
 etc/memlockd.d
 usr/share/man/man8
-lib/systemd/system

Bug#1054090: zram-tools: diff for NMU version 0.3.3.1-1.2

[Chris Hofstaedtler]

Control: tags 1054090 + pending


Dear maintainer,

I've prepared an NMU for zram-tools (versioned as 0.3.3.1-1.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru zram-tools-0.3.3.1/debian/changelog zram-tools-0.3.3.1/debian/changelog
--- zram-tools-0.3.3.1/debian/changelog	2022-10-15 12:59:52.0 +0200
+++ zram-tools-0.3.3.1/debian/changelog	2024-05-30 02:51:05.0 +0200
@@ -1,3 +1,12 @@
+zram-tools (0.3.3.1-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Let dh_installsystemd choose the location of the unit (Closes: #1054090)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:51:05 +0200
+
 zram-tools (0.3.3.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru zram-tools-0.3.3.1/debian/install zram-tools-0.3.3.1/debian/install
--- zram-tools-0.3.3.1/debian/install	2018-10-11 12:44:12.0 +0200
+++ zram-tools-0.3.3.1/debian/install	2024-05-30 02:51:01.0 +0200
@@ -1,3 +1,2 @@
 zramswap usr/sbin
 conf/zramswap etc/default
-zramswap.service lib/systemd/system
diff -Nru zram-tools-0.3.3.1/debian/rules zram-tools-0.3.3.1/debian/rules
--- zram-tools-0.3.3.1/debian/rules	2018-09-12 11:49:53.0 +0200
+++ zram-tools-0.3.3.1/debian/rules	2024-05-30 02:51:01.0 +0200
@@ -2,3 +2,6 @@
 
 %:
 	dh $@
+
+override_dh_installsystemd:
+	dh_installsystemd --name=zramswap
diff -Nru zram-tools-0.3.3.1/debian/zram-tools.zramswap.service zram-tools-0.3.3.1/debian/zram-tools.zramswap.service
--- zram-tools-0.3.3.1/debian/zram-tools.zramswap.service	1970-01-01 01:00:00.0 +0100
+++ zram-tools-0.3.3.1/debian/zram-tools.zramswap.service	2020-11-02 15:19:01.0 +0100
@@ -0,0 +1,14 @@
+[Unit]
+Description=Linux zramswap setup
+Documentation=man:zramswap(8)
+
+[Service]
+EnvironmentFile=-/etc/default/zramswap
+ExecStart=/usr/sbin/zramswap start
+ExecStop=/usr/sbin/zramswap stop
+ExecReload=/usr/sbin/zramswap restart
+Type=oneshot
+RemainAfterExit=true
+
+[Install]
+WantedBy=multi-user.target

Bug#1063458: open-infrastructure-storage-tools: diff for NMU version 20190301-lts1-5.1

[Chris Hofstaedtler]

Control: tags 1063458 + pending


Dear maintainer,

I've prepared an NMU for open-infrastructure-storage-tools (versioned as 
20190301-lts1-5.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru open-infrastructure-storage-tools-20190301-lts1/debian/changelog open-infrastructure-storage-tools-20190301-lts1/debian/changelog
--- open-infrastructure-storage-tools-20190301-lts1/debian/changelog	2023-02-07 15:31:53.0 +0100
+++ open-infrastructure-storage-tools-20190301-lts1/debian/changelog	2024-05-30 02:44:06.0 +0200
@@ -1,3 +1,12 @@
+open-infrastructure-storage-tools (20190301-lts1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Move files to /usr for DEP17. (Closes: #1063458)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:44:06 +0200
+
 open-infrastructure-storage-tools (20190301-lts1-5) sid; urgency=high
 
   * Uploading to sid, with bumped urgency due to upcoming freeze deadline.
diff -Nru open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch
--- open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch	1970-01-01 01:00:00.0 +0100
+++ open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch	2024-05-30 02:43:52.0 +0200
@@ -0,0 +1,13 @@
+--- open-infrastructure-storage-tools-20190301-lts1.orig/Makefile
 open-infrastructure-storage-tools-20190301-lts1/Makefile
+@@ -72,8 +72,8 @@
+ 	mkdir -p $(DESTDIR)/etc/logrotate.d
+ 	cp -r share/logrotate/* $(DESTDIR)/etc/logrotate.d
+ 
+-	mkdir -p $(DESTDIR)/lib/systemd/system
+-	cp -r share/systemd/* $(DESTDIR)/lib/systemd/system
++	mkdir -p $(DESTDIR)/usr/lib/systemd/system
++	cp -r share/systemd/* $(DESTDIR)/usr/lib/systemd/system
+ 
+ 	mkdir -p $(DESTDIR)/usr/share/$(PROJECT)/$(PROGRAM)
+ 	cp -r share/ceph-info $(DESTDIR)/usr/share/$(PROJECT)
diff -Nru open-infrastructure-storage-tools-20190301-lts1/debian/patches/series open-infrastructure-storage-tools-20190301-lts1/debian/patches/series
--- open-infrastructure-storage-tools-20190301-lts1/debian/patches/series	2023-02-07 15:31:22.0 +0100
+++ open-infrastructure-storage-tools-20190301-lts1/debian/patches/series	2024-05-30 02:44:02.0 +0200
@@ -1 +1,2 @@
 upstream/0001-ftbfs-asciidoc.patch
+dep17.patch

Bug#1063455: open-infrastructure-compute-tools: diff for NMU version 20221223-3.1

[Chris Hofstaedtler]

Control: tags 1063455 + pending


Dear maintainer,

I've prepared an NMU for open-infrastructure-compute-tools (versioned as 
20221223-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru open-infrastructure-compute-tools-20221223/debian/changelog open-infrastructure-compute-tools-20221223/debian/changelog
--- open-infrastructure-compute-tools-20221223/debian/changelog	2023-02-05 16:42:42.0 +0100
+++ open-infrastructure-compute-tools-20221223/debian/changelog	2024-05-30 02:45:16.0 +0200
@@ -1,3 +1,12 @@
+open-infrastructure-compute-tools (20221223-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Move files to /usr for DEP17. (Closes: #1063455)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:45:16 +0200
+
 open-infrastructure-compute-tools (20221223-3) sid; urgency=medium
 
   * Uploading to sid.
diff -Nru open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch
--- open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch	1970-01-01 01:00:00.0 +0100
+++ open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch	2024-05-30 02:45:04.0 +0200
@@ -0,0 +1,13 @@
+--- open-infrastructure-compute-tools-20221223.orig/Makefile
 open-infrastructure-compute-tools-20221223/Makefile
+@@ -142,8 +142,8 @@
+ 	ln -sf stop $(DESTDIR)/usr/libexec/$(PROGRAM)/t
+ 	ln -sf update $(DESTDIR)/usr/libexec/$(PROGRAM)/u
+ 
+-	mkdir -p $(DESTDIR)/lib/systemd/system
+-	cp -r share/systemd/* $(DESTDIR)/lib/systemd/system
++	mkdir -p $(DESTDIR)/usr/lib/systemd/system
++	cp -r share/systemd/* $(DESTDIR)/usr/lib/systemd/system
+ 
+ 	mkdir -p $(DESTDIR)/var/log/$(SOFTWARE)
+ 
diff -Nru open-infrastructure-compute-tools-20221223/debian/patches/series open-infrastructure-compute-tools-20221223/debian/patches/series
--- open-infrastructure-compute-tools-20221223/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ open-infrastructure-compute-tools-20221223/debian/patches/series	2024-05-30 02:45:07.0 +0200
@@ -0,0 +1 @@
+dep17.patch

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Yogeswaran Umasankar]

Hi,

Thank you for noticing. Looks like proto module in nanopb is very
specific to nanopb.

For now, I am planning to declare nanopb in Conflicts for
'python3-proto-plus' binary. Let me know if it might not be advisable.

Cheers!

Bug#1068229: login: remove lastlog, remove pam_lastlog.so from PAM config [patch]

[Chris Hofstaedtler]

Control: tags 1068229 + patch

Hi,

here's a patch to achieve the requested changes.

When this is uploaded, we can have lastlog2 take over.

Please let me know about your plan on uploading.

Chris

diff -Nru shadow-4.13+dfsg1/debian/changelog shadow-4.13+dfsg1/debian/changelog
--- shadow-4.13+dfsg1/debian/changelog	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/changelog	2024-05-30 02:23:58.0 +0200
@@ -1,3 +1,11 @@
+shadow (1:4.13+dfsg1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop pam_lastlog.so from config. (Closes: #1068229)
+  * Stop installing lastlog binary.
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:23:58 +0200
+
 shadow (1:4.13+dfsg1-4) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru shadow-4.13+dfsg1/debian/login.install shadow-4.13+dfsg1/debian/login.install
--- shadow-4.13+dfsg1/debian/login.install	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/login.install	2024-05-30 02:23:58.0 +0200
@@ -2,6 +2,5 @@
 usr/share/locale/*/LC_MESSAGES/shadow.mo
 sbin/nologin usr/sbin
 usr/bin/faillog
-usr/bin/lastlog
 usr/bin/newgrp
 bin/login usr/bin
diff -Nru shadow-4.13+dfsg1/debian/login.manpages shadow-4.13+dfsg1/debian/login.manpages
--- shadow-4.13+dfsg1/debian/login.manpages	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/login.manpages	2024-05-30 02:23:58.0 +0200
@@ -4,7 +4,6 @@
 usr/share/man/*/man5/faillog.5
 usr/share/man/*/man5/login.defs.5
 usr/share/man/*/man8/faillog.8
-usr/share/man/*/man8/lastlog.8
 usr/share/man/*/man8/nologin.8
 usr/share/man/man1/login.1
 usr/share/man/man1/newgrp.1
@@ -12,5 +11,4 @@
 usr/share/man/man5/faillog.5
 usr/share/man/man5/login.defs.5
 usr/share/man/man8/faillog.8
-usr/share/man/man8/lastlog.8
 usr/share/man/man8/nologin.8
diff -Nru shadow-4.13+dfsg1/debian/login.pam shadow-4.13+dfsg1/debian/login.pam
--- shadow-4.13+dfsg1/debian/login.pam	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/login.pam	2024-05-30 02:23:58.0 +0200
@@ -77,10 +77,6 @@
 # (Replaces the use of /etc/limits in old login)
 sessionrequired   pam_limits.so
 
-# Prints the last login info upon successful login
-# (Replaces the `LASTLOG_ENAB' option from login.defs)
-sessionoptional   pam_lastlog.so
-
 # Prints the status of the user's mailbox upon successful login
 # (Replaces the `MAIL_CHECK_ENAB' option from login.defs). 
 #
diff -Nru shadow-4.13+dfsg1/debian/not-installed shadow-4.13+dfsg1/debian/not-installed
--- shadow-4.13+dfsg1/debian/not-installed	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/not-installed	2024-05-30 02:23:58.0 +0200
@@ -15,6 +15,7 @@
 etc/pam.d/useradd
 etc/pam.d/userdel
 etc/pam.d/usermod
+usr/bin/lastlog
 usr/bin/sg
 usr/lib/*/libsubid.la
 usr/sbin/logoutd
@@ -25,6 +26,7 @@
 usr/share/man/*/man3/getspnam.3
 usr/share/man/*/man3/shadow.3
 usr/share/man/*/man5/suauth.5
+usr/share/man/*/man8/lastlog.8
 usr/share/man/*/man8/logoutd.8
 usr/share/man/man1/groups.1
 usr/share/man/man1/logoutd.1
@@ -32,5 +34,6 @@
 usr/share/man/man3/getspnam.3
 usr/share/man/man3/shadow.3
 usr/share/man/man5/suauth.5
+usr/share/man/man8/lastlog.8
 usr/share/man/man8/logoutd.8
 

Bug#1064238: fuse-umfuse-ext2: diff for NMU version 0.4-1.5

[Chris Hofstaedtler]

Control: tags 1064238 + pending


Dear maintainer,

I've prepared an NMU for fuse-umfuse-ext2 (versioned as 0.4-1.5) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru fuse-umfuse-ext2-0.4/debian/changelog fuse-umfuse-ext2-0.4/debian/changelog
--- fuse-umfuse-ext2-0.4/debian/changelog	2023-09-29 01:48:00.0 +0200
+++ fuse-umfuse-ext2-0.4/debian/changelog	2024-05-30 02:19:03.0 +0200
@@ -1,3 +1,12 @@
+fuse-umfuse-ext2 (0.4-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * DEP17: Move files to /usr. (Closes: #1064238)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:19:03 +0200
+
 fuse-umfuse-ext2 (0.4-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fuse-umfuse-ext2-0.4/debian/patches/series fuse-umfuse-ext2-0.4/debian/patches/series
--- fuse-umfuse-ext2-0.4/debian/patches/series	2023-09-29 01:48:00.0 +0200
+++ fuse-umfuse-ext2-0.4/debian/patches/series	2024-05-30 02:18:57.0 +0200
@@ -1 +1,2 @@
 fuse-ext2.h.patch
+usrmove.patch
diff -Nru fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch
--- fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch	1970-01-01 01:00:00.0 +0100
+++ fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch	2024-05-30 02:18:57.0 +0200
@@ -0,0 +1,22 @@
+--- fuse-umfuse-ext2-0.4.orig/fuse-ext2/Makefile.am
 fuse-umfuse-ext2-0.4/fuse-ext2/Makefile.am
+@@ -283,7 +283,7 @@
+ if LINUX
+ install-exec-local:
+ 	$(INSTALL) -d "$(DESTDIR)/usr/sbin"
+-	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/sbin/mount.fuse-ext2"
++	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/$(sbindir)/mount.fuse-ext2"
+ endif
+ 
+ dist_man1_MANS = fuse-ext2.1
+--- fuse-umfuse-ext2-0.4.orig/fuse-ext2/Makefile.in
 fuse-umfuse-ext2-0.4/fuse-ext2/Makefile.in
+@@ -1884,7 +1884,7 @@
+ #endif
+ @LINUX_TRUE@install-exec-local:
+ @LINUX_TRUE@	$(INSTALL) -d "$(DESTDIR)/usr/sbin"
+-@LINUX_TRUE@	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/sbin/mount.fuse-ext2"
++@LINUX_TRUE@	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/$(sbindir)/mount.fuse-ext2"
+ 
+ # Tell versions [3.59,3.63) of GNU make to not export all variables.
+ # Otherwise a system limit (for SysV at least) may be exceeded.
diff -Nru fuse-umfuse-ext2-0.4/debian/rules fuse-umfuse-ext2-0.4/debian/rules
--- fuse-umfuse-ext2-0.4/debian/rules	2023-09-29 01:47:05.0 +0200
+++ fuse-umfuse-ext2-0.4/debian/rules	2024-05-30 02:18:57.0 +0200
@@ -3,15 +3,17 @@
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
 
+DEB_CONFIGURE_EXTRA_FLAGS=--exec-prefix='$${prefix}'
+
 common-install-prehook-arch common-install-prehook-indep::
-	mkdir -p debian/tmp/sbin
+	mkdir -p debian/tmp/usr/sbin
 
 install/fuseext2::
 	dh_link -pfuseext2 /usr/share/man/man1/fuse-ext2.1 /usr/share/man/man8/mount.fuse-ext2.8
-	dh_link -pfuseext2 /usr/bin/fuse-ext2 /sbin/mount.fuse-ext2
+	dh_link -pfuseext2 /usr/bin/fuse-ext2 /usr/sbin/mount.fuse-ext2
 	# Compatibility symlinks for versions up to 0.3.
 	dh_link -pfuseext2 /usr/bin/fuse-ext2 /usr/bin/fuseext2
-	dh_link -pfuseext2 /sbin/mount.fuse-ext2 /sbin/mount.fuseext2
+	dh_link -pfuseext2 /usr/sbin/mount.fuse-ext2 /usr/sbin/mount.fuseext2
 	dh_link -pfuseext2 /usr/share/man/man1/fuse-ext2.1 /usr/share/man/man1/fuseext2.1
 	dh_link -pfuseext2 /usr/share/man/man8/mount.fuse-ext2.8 /usr/share/man/man8/mount.fuseext2.8
 	dh_compress -pfuseext2

Bug#1068229: Bug#1066060: libpam-modules: pam_lastlog.so missing

[Chris Hofstaedtler]

Control: retitle -1 login: remove lastlog, remove pam_lastlog.so from PAM config
Control: severity -1 important

Dear shadow maintainers,

as originally requested, please drop pam_lastlog.so from the PAM
config.

Please also drop the lastlog binary, which isn't very useful when
the data it is reading is not updated anymore.

Chris

Bug#1066060: libpam-modules: pam_lastlog.so missing

[Chris Hofstaedtler]

Control: retitle -1 libpam-modules: pam_lastlog.so missing

Apologies, this was the wrong half of the bug.

I think in src:pam not much is to be done, except the NEWS.Debian
entry?

Chris

Bug#1061489: libpam-ccreds: diff for NMU version 10-8.1

[Chris Hofstaedtler]

Control: tags 1061489 + pending


Dear maintainer,

I've prepared an NMU for libpam-ccreds (versioned as 10-8.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru libpam-ccreds-10/debian/changelog libpam-ccreds-10/debian/changelog
--- libpam-ccreds-10/debian/changelog	2019-10-26 00:28:29.0 +0200
+++ libpam-ccreds-10/debian/changelog	2024-05-30 02:15:58.0 +0200
@@ -1,3 +1,12 @@
+libpam-ccreds (10-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Michael Biebl ]
+  * Install PAM modules and binaries into /usr (Closes: #1061489)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:15:58 +0200
+
 libpam-ccreds (10-8) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru libpam-ccreds-10/debian/dirs libpam-ccreds-10/debian/dirs
--- libpam-ccreds-10/debian/dirs	2009-08-01 19:57:03.0 +0200
+++ libpam-ccreds-10/debian/dirs	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-usr/sbin
-lib/security
diff -Nru libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides
--- libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides	2009-08-01 19:57:03.0 +0200
+++ libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides	2024-05-30 02:15:54.0 +0200
@@ -1,2 +1,2 @@
 # yes, we know it's suid, that's the whole point...
-libpam-ccreds: setuid-binary sbin/ccreds_chkpwd 4755 root/root
+libpam-ccreds: setuid-binary usr/sbin/ccreds_chkpwd 4755 root/root
diff -Nru libpam-ccreds-10/debian/rules libpam-ccreds-10/debian/rules
--- libpam-ccreds-10/debian/rules	2019-10-26 00:27:03.0 +0200
+++ libpam-ccreds-10/debian/rules	2024-05-30 02:15:54.0 +0200
@@ -4,8 +4,6 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 DEB_CONFIGURE_EXTRA_ARGS := \
-	--libdir=/lib/$(DEB_HOST_GNU_TYPE) \
-	--sbindir=/sbin \
 	--enable-gcrypt \
 	$(NULL)
 
@@ -17,16 +15,15 @@
 
 override_dh_auto_install:
 	dh_auto_install
-	chown root:root debian/libpam-ccreds/sbin/ccreds_chkpwd
-	chmod 4755 debian/libpam-ccreds/sbin/ccreds_chkpwd
+	chown root:root debian/libpam-ccreds/usr/sbin/ccreds_chkpwd
+	chmod 4755 debian/libpam-ccreds/usr/sbin/ccreds_chkpwd
 
 	mkdir -p debian/libpam-ccreds/usr/share/pam-configs
 	install -m 0644 debian/libpam-ccreds.pam-auth-update.ccreds-save \
 		debian/libpam-ccreds/usr/share/pam-configs/ccreds-save
 	install -m 0644 debian/libpam-ccreds.pam-auth-update.ccreds-check \
 		debian/libpam-ccreds/usr/share/pam-configs/ccreds-check
-	rmdir debian/libpam-ccreds/lib/security
 
 override_dh_fixperms:
-	dh_fixperms -X/sbin/ccreds_chkpwd
+	dh_fixperms -X/usr/sbin/ccreds_chkpwd
 

Bug#1058859: teensy-loader-cli: diff for NMU version 2.2-1.1

[Chris Hofstaedtler]

Control: tags 1058859 + pending


Dear maintainer,

I've prepared an NMU for teensy-loader-cli (versioned as 2.2-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru teensy-loader-cli-2.2/debian/49-teensy.rules teensy-loader-cli-2.2/debian/49-teensy.rules
--- teensy-loader-cli-2.2/debian/49-teensy.rules	2022-01-11 14:30:43.0 +0100
+++ teensy-loader-cli-2.2/debian/49-teensy.rules	1970-01-01 01:00:00.0 +0100
@@ -1,38 +0,0 @@
-# UDEV Rules for Teensy boards, http://www.pjrc.com/teensy/
-#
-# The latest version of this file may be found at:
-#   http://www.pjrc.com/teensy/49-teensy.rules
-#
-# This file must be placed at:
-#
-# /etc/udev/rules.d/49-teensy.rules(preferred location)
-#   or
-# /lib/udev/rules.d/49-teensy.rules(req'd on some broken systems)
-#
-# To install, type this command in a terminal:
-#   sudo cp 49-teensy.rules /etc/udev/rules.d/49-teensy.rules
-#
-# Or use the alternate way (from this forum message) to download and install:
-#   https://forum.pjrc.com/threads/45595?p=150445&viewfull=1#post150445
-#
-# After this file is installed, physically unplug and reconnect Teensy.
-#
-ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", ENV{ID_MM_DEVICE_IGNORE}="1"
-ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789A]?", ENV{MTP_NO_PROBE}="1"
-SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789ABCD]?", TAG+="uaccess", TAG+="udev-acl"
-KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", TAG+="uaccess", TAG+="udev-acl"
-#
-# If you share your linux system with other users, or just don't like the
-# idea of write permission for everybody, you can replace MODE:="0666" with
-# OWNER:="yourusername" to create the device owned by you, or with
-# GROUP:="somegroupname" and mange access using standard unix groups.
-#
-#
-# If using USB Serial you get a new device each time (Ubuntu 9.10)
-# eg: /dev/ttyACM0, ttyACM1, ttyACM2, ttyACM3, ttyACM4, etc
-#apt-get remove --purge modemmanager (reboot may be necessary)
-#
-# Older modem proding (eg, Ubuntu 9.04) caused very slow serial device detection.
-# To fix, add this near top of /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules
-#   SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789]?", GOTO="nm_modem_probe_end" 
-#
diff -Nru teensy-loader-cli-2.2/debian/changelog teensy-loader-cli-2.2/debian/changelog
--- teensy-loader-cli-2.2/debian/changelog	2022-01-15 21:59:54.0 +0100
+++ teensy-loader-cli-2.2/debian/changelog	2024-05-30 02:13:46.0 +0200
@@ -1,3 +1,10 @@
+teensy-loader-cli (2.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Let dh_installudev install udev rules. (Closes: #1058859)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:13:46 +0200
+
 teensy-loader-cli (2.2-1) unstable; urgency=medium
 
   * New upstream release, contained all debian patches
diff -Nru teensy-loader-cli-2.2/debian/install teensy-loader-cli-2.2/debian/install
--- teensy-loader-cli-2.2/debian/install	2022-01-11 14:30:43.0 +0100
+++ teensy-loader-cli-2.2/debian/install	2024-05-30 02:13:43.0 +0200
@@ -1,2 +1 @@
 teensy_loader_cli /usr/bin/
-debian/49-teensy.rules /lib/udev/rules.d/
diff -Nru teensy-loader-cli-2.2/debian/rules teensy-loader-cli-2.2/debian/rules
--- teensy-loader-cli-2.2/debian/rules	2022-01-11 14:30:43.0 +0100
+++ teensy-loader-cli-2.2/debian/rules	2024-05-30 02:13:43.0 +0200
@@ -12,3 +12,6 @@
 
 %:
 	dh $@
+
+override_dh_installudev:
+	dh_installudev --priority=49 --name=teensy
diff -Nru teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev
--- teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev	1970-01-01 01:00:00.0 +0100
+++ teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev	2024-05-30 02:13:43.0 +0200
@@ -0,0 +1,38 @@
+# UDEV Rules for Teensy boards, http://www.pjrc.com/teensy/
+#
+# The latest version of this file may be found at:
+#   http://www.pjrc.com/teensy/49-teensy.rules
+#
+# This file must be placed at:
+#
+# /etc/udev/rules.d/49-teensy.rules(preferred location)
+#   or
+# /lib/udev/rules.d/49-teensy.rules(req'd on some broken systems)
+#
+# To install, type this command in a terminal:
+#   sudo cp 49-teensy.rules /etc/udev/rules.d/49-teensy.rules
+#
+# Or use the alternate way (from this forum message) to download and install:
+#   https://forum.pjrc.com/threads/45595?p=150445&viewfull=1#post150445
+#
+# After this file is installed, physically unplug and reconnect Teensy.
+#
+ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", ENV{ID_MM_DEVICE_IGNORE}="1"
+ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789A]?", ENV{MTP_NO_PROBE}="1"
+SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789ABCD]?", TAG+="uaccess", TAG+="udev-acl"
+KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", TAG+="uacces

Bug#1059379: f2fs-tools: diff for NMU version 1.16.0-1.1

[Chris Hofstaedtler]

Control: tags 1059379 + pending


Dear maintainer,

I've prepared an NMU for f2fs-tools (versioned as 1.16.0-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru f2fs-tools-1.16.0/debian/changelog f2fs-tools-1.16.0/debian/changelog
--- f2fs-tools-1.16.0/debian/changelog	2023-07-17 06:03:45.0 +0200
+++ f2fs-tools-1.16.0/debian/changelog	2024-05-30 02:10:23.0 +0200
@@ -1,3 +1,10 @@
+f2fs-tools (1.16.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install files into /usr instead of /. (Closes: #1059379)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:10:23 +0200
+
 f2fs-tools (1.16.0-1) unstable; urgency=medium
 
   [ Vincent Cheng ]
diff -Nru f2fs-tools-1.16.0/debian/f2fs-tools.install f2fs-tools-1.16.0/debian/f2fs-tools.install
--- f2fs-tools-1.16.0/debian/f2fs-tools.install	2023-07-17 06:02:17.0 +0200
+++ f2fs-tools-1.16.0/debian/f2fs-tools.install	2024-05-30 02:10:20.0 +0200
@@ -1,4 +1,4 @@
 # All but sbin/sg_write_buffer
-sbin/*f2fs*
+usr/sbin/*f2fs*
 
 usr/share/man/man8/*.8
diff -Nru f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install
--- f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install	2023-07-17 06:02:17.0 +0200
+++ f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install	2024-05-30 02:10:20.0 +0200
@@ -1,2 +1,2 @@
 # All but sbin/sg_write_buffer
-sbin/*f2fs*
+usr/sbin/*f2fs*
diff -Nru f2fs-tools-1.16.0/debian/rules f2fs-tools-1.16.0/debian/rules
--- f2fs-tools-1.16.0/debian/rules	2023-07-17 06:02:17.0 +0200
+++ f2fs-tools-1.16.0/debian/rules	2024-05-30 02:10:20.0 +0200
@@ -10,8 +10,8 @@
 	dh $@
 
 override_dh_auto_configure:
-	dh_auto_configure -- --sbindir=/sbin --disable-shared \
-		--with-root-libdir=/lib/$(DEB_HOST_MULTIARCH)
+	dh_auto_configure -- --sbindir=/usr/sbin --disable-shared \
+		--with-root-libdir=/usr/lib/$(DEB_HOST_MULTIARCH)
 
 # dh_dwz when run on f2fs-tools-udeb ends up installing the
 # /usr/lib/debug/.dwz files into the udeb.  I think that's a bug,

Bug#1072189: Acknowledgement (apt: typo in apt.conf(5))

[Noah Meyerhans]

Control: tags -1 + patch

Fix is at https://salsa.debian.org/apt-team/apt/-/merge_requests/353

Bug#1058857: alsa-tools: diff for NMU version 1.2.11-1.1

[Chris Hofstaedtler]

Control: tags 1058857 + pending


Dear maintainer,

I've prepared an NMU for alsa-tools (versioned as 1.2.11-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs
--- alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs	2019-11-07 00:42:01.0 +0100
+++ alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-/lib/udev/rules.d
diff -Nru alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev
--- alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev	2021-09-09 02:44:36.0 +0200
+++ alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev	2024-05-30 01:51:59.0 +0200
@@ -1,18 +1,18 @@
 ###
 # Description:   udev rule to load TASCAM US-122 usb sound card.
 # Created:   Wed, 12 Sep 2007 17:05:25 +0200
-# Last modified: Thu, 21 Jan 2010 21:21:12 +0100
+# Last modified: Sun, 17 Dec 2023 01:35:53 +0100
 # File:  /etc/udev/alsa-firmware-loaders.rules
 ###
 
 # TASCAM US-428 usb sound card.
-SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8000", RUN+="/lib/udev/tascam_fw"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8000", RUN+="tascam_fw"
 # TASCAM US-224 usb sound card.
-SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8004", RUN+="/lib/udev/tascam_fw"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8004", RUN+="tascam_fw"
 # TASCAM US-112 usb sound card.
-SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8006", RUN+="/lib/udev/tascam_fw"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8006", RUN+="tascam_fw"
 
-SUBSYSTEM=="usb", ACTION=="add", ATTR{id}=="USX2Y", RUN+="/lib/udev/tascam_fpga"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{id}=="USX2Y", RUN+="tascam_fpga"
 
 # vim:tw=160:syntax=udevrules
 
diff -Nru alsa-tools-1.2.11/debian/changelog alsa-tools-1.2.11/debian/changelog
--- alsa-tools-1.2.11/debian/changelog	2024-03-04 23:13:35.0 +0100
+++ alsa-tools-1.2.11/debian/changelog	2024-05-30 01:58:32.0 +0200
@@ -1,3 +1,13 @@
+alsa-tools (1.2.11-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #1058857)
+  * Avoid hard-coding path to udev helpers in udev rules, as it will
+change.
+  * Update firmware path to /usr/lib/firmware.
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:58:32 +0200
+
 alsa-tools (1.2.11-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru alsa-tools-1.2.11/debian/control alsa-tools-1.2.11/debian/control
--- alsa-tools-1.2.11/debian/control	2023-05-05 00:30:53.0 +0200
+++ alsa-tools-1.2.11/debian/control	2024-05-30 01:51:59.0 +0200
@@ -10,7 +10,9 @@
libasound2-dev (>= 1.0.24.1),
libfltk1.3-dev,
libgtk-3-dev,
-   libgtk2.0-dev
+   libgtk2.0-dev,
+   pkgconf,
+   systemd-dev,
 Standards-Version: 4.6.0
 Homepage: https://www.alsa-project.org/
 Vcs-Git: https://salsa.debian.org/alsa-team/alsa-tools.git
diff -Nru alsa-tools-1.2.11/debian/patches/firmware_locations.patch alsa-tools-1.2.11/debian/patches/firmware_locations.patch
--- alsa-tools-1.2.11/debian/patches/firmware_locations.patch	2021-09-09 02:44:36.0 +0200
+++ alsa-tools-1.2.11/debian/patches/firmware_locations.patch	2024-05-30 01:51:59.0 +0200
@@ -1,5 +1,5 @@
 Author: Elimar Riesebieter 
-Description: Set firmware location to /lib/firmware, as expected in Debian.
+Description: Set firmware location to /usr/lib/firmware, as expected in Debian.
 Forwarded: no
 
 Index: alsa-tools/hdsploader/Makefile.in
@@ -11,7 +11,7 @@
  # # Process this file with automake to produce Makefile.in.
  MYNAME = hdsploader
 -AM_CFLAGS = -DDATAPATH=\"$(datadir)/alsa/firmware/$(MYNAME)\"
-+AM_CFLAGS = -DDATAPATH=\"/lib/firmware/$(MYNAME)\"
++AM_CFLAGS = -DDATAPATH=\"/usr/lib/firmware/$(MYNAME)\"
  hdsploader_SOURCES = hdsploader.c
  EXTRA_DIST = gitcompile depcomp
  all: all-am
@@ -24,7 +24,7 @@
  AUTOMAKE_OPTIONS = 1.3 foreign
  MYNAME = mixartloader
 -AM_CFLAGS = -DDATAPATH=\"$(datadir)/alsa/firmware/$(MYNAME)\"
-+AM_CFLAGS = -DDATAPATH=\"/lib/firmware/$(MYNAME)\"
++AM_CFLAGS = -DDATAPATH=\"/usr/lib/firmware/$(MYNAME)\"
  mixartloader_SOURCES = mixartloader.c
  EXTRA_DIST = gitcompile depcomp
  all: all-am
@@ -37,7 +37,7 @@
  AUTOMAKE_OPTIONS = 1.3 foreign
  MYNAME = pcxhrloader
 -AM_CFLAGS = -DDATAPATH=\"$(datadir)/alsa/firmware/$(MYNAME)\"
-+AM_CFLAGS = -DDATAPATH=\"/lib/firmware/$(MYNAME)\"
++AM_CFLAGS = -DDATAPATH=\"/usr/lib

Bug#1072189: apt: typo in apt.conf(5)

[Noah Meyerhans]

Package: apt
Version: 2.9.4
Severity: minor

The Snapshots::URI scope documentation in apt.conf(5) has a minor typo in which
the @SNAPSHOTID@ placeholder is missing the trailing '@'.

Bug#1057804: libguestfs: diff for NMU version 1:1.52.0-6.1

[Chris Hofstaedtler]

Control: tags 1057804 + patch
Control: tags 1057804 + pending


Dear maintainer,

I've prepared an NMU for libguestfs (versioned as 1:1.52.0-6.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru libguestfs-1.52.0/debian/changelog libguestfs-1.52.0/debian/changelog
--- libguestfs-1.52.0/debian/changelog	2024-05-18 22:26:51.0 +0200
+++ libguestfs-1.52.0/debian/changelog	2024-05-30 01:35:29.0 +0200
@@ -1,3 +1,11 @@
+libguestfs (1:1.52.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install 99-guestfs-serial.rules into /usr/lib/udev/rules.d (Closes:
+#1057804)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:35:29 +0200
+
 libguestfs (1:1.52.0-6) unstable; urgency=medium
 
   * Add util-linux-extra to appliance list (Closes: #1071313)
diff -Nru libguestfs-1.52.0/debian/guestfsd.install libguestfs-1.52.0/debian/guestfsd.install
--- libguestfs-1.52.0/debian/guestfsd.install	2023-07-23 13:30:56.0 +0200
+++ libguestfs-1.52.0/debian/guestfsd.install	2024-05-30 01:34:40.0 +0200
@@ -1,3 +1,3 @@
 usr/sbin/guestfsd
 usr/share/man/man8/guestfsd.8*
-lib/udev/rules.d/99-guestfs-serial.rules
+usr/lib/udev/rules.d/99-guestfs-serial.rules
diff -Nru libguestfs-1.52.0/debian/patches/series libguestfs-1.52.0/debian/patches/series
--- libguestfs-1.52.0/debian/patches/series	2024-05-18 22:26:51.0 +0200
+++ libguestfs-1.52.0/debian/patches/series	2024-05-30 01:35:09.0 +0200
@@ -20,3 +20,4 @@
 Only-set-rtc-driftfix-slew-on-x86-architectures.patch
 Add-dhcpcd-to-Debian-package-list.patch
 Add-util-linux-extra-to-appliance-list.patch
+udev-rules-path.patch
diff -Nru libguestfs-1.52.0/debian/patches/udev-rules-path.patch libguestfs-1.52.0/debian/patches/udev-rules-path.patch
--- libguestfs-1.52.0/debian/patches/udev-rules-path.patch	1970-01-01 01:00:00.0 +0100
+++ libguestfs-1.52.0/debian/patches/udev-rules-path.patch	2024-05-30 01:35:22.0 +0200
@@ -0,0 +1,13 @@
+Index: libguestfs-1.52.0/appliance/Makefile.am
+===
+--- libguestfs-1.52.0.orig/appliance/Makefile.am
 libguestfs-1.52.0/appliance/Makefile.am
+@@ -157,7 +157,7 @@ supermin.d/udev-rules.tar.gz: 99-guestfs
+ # If installing the daemon, install the udev rules too.
+ 
+ if INSTALL_DAEMON
+-udevrulesdir = /lib/udev/rules.d
++udevrulesdir = /usr/lib/udev/rules.d
+ udevrules_DATA = 99-guestfs-serial.rules
+ endif
+ 

Bug#1072188: Package error

[Peter Carter]

Package: installation-reports

Boot method: 
Image version: 
Date: 

Machine: Dell 7020
Processor:Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
Memory: 16G
Partitions:
filesystem Type 1K-blocks Used Available Use% Mounted on 
udev   devtmpfs   8108416    0   8108416   0% /dev tmpfs 
 tmpfs  1628976 1552   1627424   1% /run /dev/sda3 
 btrfs    468253696 32781716 430568940   8% / tmpfs  tmpfs 
 8144876    0   8144876   0% /dev/shm tmpfs  tmpfs 
5120   16  5104   1% /run/lock efivarfs   efivarfs 
  128   96    28  78% /sys/firmware/efi/efivars /dev/sdb1 
 btrfs    976761560 5920 974597824   1% /data /dev/sda1 
 vfat    497684 4480    493204   1% /boot/efi overlay 
   overlay  468253696 32781716 430568940   8% 
/var/lib/docker/overlay2/afa24d7e3210883370c5732 
914467d97f210df47b7a7635495e899928a72/merged tmpfs  tmpfs 
 1628972  232   1628740   1% /run/user/1000


Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor 
DRAM Controller [8086:0c00] (rev 06)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: hsw_uncore 00:02.0 VGA 
compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 
   DeviceName:  Onboard IGD    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i915    Kernel modules: 
i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor HD Audio Controller [808 6:0c0c] (rev 06) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
snd_hda_intel    Kernel modules: snd_hda_intel 00:14.0 USB 
controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI [8086:8c31] (rev 04)    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: xhci_hcd    Kernel modules: xhci_pci 
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
mei_me    Kernel modules: mei_me 00:19.0 Ethernet controller [0200]: 
Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04) 
   DeviceName:  Onboard LAN    Subsystem: Dell Device 
[1028:05a4]    Kernel driver in use: e1000e    Kernel modules: 
e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 
Series Chipset Family USB EHCI #2 [8086:8c2d] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: 
Intel Corporation 8 Series/C220 Series Chipset High Definition Audio 
Controller [ 8086:8c20] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: snd_hda_intel    Kernel 
modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #1 [808 6:8c10] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #5 [808 6:8c18] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 8 
Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1f.0 ISA bridge [0601]: 
Intel Corporation Q87 Express LPC Controller [8086:8c4e] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
lpc_ich    Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: 
Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA 
Controller 1 [AHCI mode] [8086:8c02] (rev 04)    DeviceName: 
 Onboard SATA controller #1    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: ahci    Kernel modules: ahci 00:1f.3 
SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family 
SMBus Controller [8086:8c22] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i801_smbus    Kernel 
modules: i2c_i801 02:00.0 Network controller [0280]: Intel Corporation 
Wireless 7265 [8086:095a] (rev 59)    Subsystem: Intel Corporation 
Dual Band Wireless-AC 7265 [Stone Peak 2 AC] [8086:5010]    Kernel 
driver in use: iwlwifi    Kernel modules: iwlwifi


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [

Bug#1061342: gridengine: diff for NMU version 8.1.9+dfsg-11.1

[Chris Hofstaedtler]

Control: tags 1061342 + pending


Dear maintainer,

I've prepared an NMU for gridengine (versioned as 8.1.9+dfsg-11.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru gridengine-8.1.9+dfsg/debian/changelog gridengine-8.1.9+dfsg/debian/changelog
--- gridengine-8.1.9+dfsg/debian/changelog	2023-08-13 17:56:03.0 +0200
+++ gridengine-8.1.9+dfsg/debian/changelog	2024-05-30 01:41:12.0 +0200
@@ -1,3 +1,12 @@
+gridengine (8.1.9+dfsg-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Michael Biebl ]
+  * Install PAM modules into /usr (DEP 17 M2). (Closes: #1061342)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:41:12 +0200
+
 gridengine (8.1.9+dfsg-11) unstable; urgency=medium
 
   * Team upload.
diff -Nru gridengine-8.1.9+dfsg/debian/gridengine-exec.install gridengine-8.1.9+dfsg/debian/gridengine-exec.install
--- gridengine-8.1.9+dfsg/debian/gridengine-exec.install	2023-08-13 17:40:33.0 +0200
+++ gridengine-8.1.9+dfsg/debian/gridengine-exec.install	2024-05-30 01:41:11.0 +0200
@@ -1,3 +1,3 @@
 debian/tmp/usr/bin/*/sge_execd		usr/lib/gridengine
 debian/tmp/usr/bin/*/sge_*shepherd	usr/lib/gridengine
-/lib/*/security/*.so
+usr/lib/*/security/*.so
diff -Nru gridengine-8.1.9+dfsg/debian/rules gridengine-8.1.9+dfsg/debian/rules
--- gridengine-8.1.9+dfsg/debian/rules	2023-08-13 17:40:33.0 +0200
+++ gridengine-8.1.9+dfsg/debian/rules	2024-05-30 01:41:11.0 +0200
@@ -66,7 +66,7 @@
 override_dh_auto_install:
 	install -d debian/tmp/usr
 	install -d debian/tmp/usr/share
-	install -d debian/tmp/lib/$(DEB_HOST_GNU_TYPE)/security
+	install -d debian/tmp/usr/lib/$(DEB_HOST_GNU_TYPE)/security
 	cd source && /usr/bin/yes | ${PRECMD} scripts/distinst \
 	-basedir ${CURDIR}/debian \
 	-vdir tmp/usr \
@@ -102,7 +102,7 @@
 	mandb -u -c debian/tmp/usr/share/man
 	chmod 755 debian/scripts/init_cluster debian/gridengine-wrapper
 	cp source/clients/qmon/qmon.desktop debian
-	mv debian/tmp/usr/lib/*/pam_sge* debian/tmp/lib/$(DEB_HOST_GNU_TYPE)/security
+	mv debian/tmp/usr/lib/*/pam_sge* debian/tmp/usr/lib/$(DEB_HOST_GNU_TYPE)/security
 
 override_dh_installinit:
 	dh_installinit -p gridengine-master

Bug#1061359: not fixed in unstable

[Chris Hofstaedtler]

Hi,

are you working on this?
Please make sure fixed packages are in trixie before the transition
freeze.

Chris

On Sat, Mar 02, 2024 at 09:58:35PM +0100, Chris Hofstaedtler wrote:
> Control: reopen -1
> Control: found -1 zfs-linux/2.2.3-1
> 
> Hi,
> 
> 2.2.3-1 in unstable still installs a lot of files outside of /usr.
> 
> /srv/debian-mirror/mirror/pool/contrib/z/zfs-linux/libnvpair3linux_2.2.3-1_amd64.deb
> drwxr-xr-x root/root 0 2024-02-23 14:28 ./lib/
> drwxr-xr-x root/root 0 2024-02-23 14:28 ./lib/x86_64-linux-gnu/
> -rw-r--r-- root/root104400 2024-02-23 14:28 
> ./lib/x86_64-linux-gnu/libnvpair.so.3.0.0
> lrwxrwxrwx root/root 0 2024-02-23 14:28 
> ./lib/x86_64-linux-gnu/libnvpair.so.3 -> libnvpair.so.3.0.0
[..]

Bug#1065307: r4d: diff for NMU version 1.7-4.1

[Chris Hofstaedtler]

Control: tags 1065307 + patch
Control: tags 1065307 + pending


Dear maintainer,

I've prepared an NMU for r4d (versioned as 1.7-4.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru r4d-1.7/debian/changelog r4d-1.7/debian/changelog
--- r4d-1.7/debian/changelog	2023-05-17 17:21:39.0 +0200
+++ r4d-1.7/debian/changelog	2024-05-30 01:29:57.0 +0200
@@ -1,3 +1,10 @@
+r4d (1.7-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd unit into /usr/lib. (Closes: #1065307)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:29:57 +0200
+
 r4d (1.7-4) unstable; urgency=medium
 
   * Change bage's email address
diff -Nru r4d-1.7/debian/patches/series r4d-1.7/debian/patches/series
--- r4d-1.7/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ r4d-1.7/debian/patches/series	2024-05-30 01:29:51.0 +0200
@@ -0,0 +1 @@
+systemd-unit-usrmerge.patch
diff -Nru r4d-1.7/debian/patches/systemd-unit-usrmerge.patch r4d-1.7/debian/patches/systemd-unit-usrmerge.patch
--- r4d-1.7/debian/patches/systemd-unit-usrmerge.patch	1970-01-01 01:00:00.0 +0100
+++ r4d-1.7/debian/patches/systemd-unit-usrmerge.patch	2024-05-30 01:29:39.0 +0200
@@ -0,0 +1,13 @@
+Index: r4d-1.7/setup.py
+===
+--- r4d-1.7.orig/setup.py
 r4d-1.7/setup.py
+@@ -25,7 +25,7 @@ setup(name='r4d',
+   scripts=['r4dd', 'r4dcfg'],
+   data_files= [
+   ('/etc/',glob("r4d.cfg")),
+-  ('/lib/systemd/system',  glob("r4dd.service"))],
++  ('/usr/lib/systemd/system',  glob("r4dd.service"))],
+   classifiers=[
+   'License :: OSI Approved :: GNU General Public License v3 or later (GPLv3+)',
+   ],

Bug#1060799: libunwind: diff for NMU version 1.6.2-3.1

[Chris Hofstaedtler]

Control: tags 1060799 + patch
Control: tags 1060799 + pending


Dear maintainer,

I've prepared an NMU for libunwind (versioned as 1.6.2-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru libunwind-1.6.2/debian/changelog libunwind-1.6.2/debian/changelog
--- libunwind-1.6.2/debian/changelog	2022-12-16 22:50:28.0 +0100
+++ libunwind-1.6.2/debian/changelog	2024-05-30 01:17:49.0 +0200
@@ -1,3 +1,10 @@
+libunwind (1.6.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop installing empty /lib directory. (Closes: #1060799)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:17:49 +0200
+
 libunwind (1.6.2-3) unstable; urgency=low
 
   * Add upstream change to determine the page size dynamically,
diff -Nru libunwind-1.6.2/debian/libunwind8.dirs libunwind-1.6.2/debian/libunwind8.dirs
--- libunwind-1.6.2/debian/libunwind8.dirs	2015-07-04 07:02:00.0 +0200
+++ libunwind-1.6.2/debian/libunwind8.dirs	2024-05-30 01:17:43.0 +0200
@@ -1,2 +1 @@
-lib
 usr/lib

Bug#1059757: firmware-sof: diff for NMU version 2023.12.1-1.1

[Chris Hofstaedtler]

Control: tags 1059757 + patch
Control: tags 1059757 + pending


Dear maintainer,

I've prepared an NMU for firmware-sof (versioned as 2023.12.1-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru firmware-sof-2023.12.1/debian/changelog firmware-sof-2023.12.1/debian/changelog
--- firmware-sof-2023.12.1/debian/changelog	2024-03-05 15:52:23.0 +0100
+++ firmware-sof-2023.12.1/debian/changelog	2024-05-30 01:19:39.0 +0200
@@ -1,3 +1,10 @@
+firmware-sof (2023.12.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install into /usr/lib instead of /lib. (Closes: #1059757)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:19:39 +0200
+
 firmware-sof (2023.12.1-1) unstable; urgency=medium
 
   * Update to upstream version 2023-12.1
diff -Nru firmware-sof-2023.12.1/debian/rules firmware-sof-2023.12.1/debian/rules
--- firmware-sof-2023.12.1/debian/rules	2024-03-05 15:52:23.0 +0100
+++ firmware-sof-2023.12.1/debian/rules	2024-05-30 01:19:39.0 +0200
@@ -4,7 +4,7 @@
 
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
-export SOF_INSTALL_DIR=debian/firmware-sof-signed/lib/firmware/intel
+export SOF_INSTALL_DIR=debian/firmware-sof-signed/usr/lib/firmware/intel
 %:
 	dh $@
 

Bug#1057290: bpftool: please build from https://github.com/libbpf/bpftool

[Sudip Mukherjee]

On Wed, 29 May 2024 at 23:27, Luca Boccassi  wrote:
>
> On Wed, 29 May 2024 19:00:59 +0100 Ben Hutchings 
> wrote:
> > On Sat, 2023-12-02 at 20:04 +, Sudip Mukherjee wrote:
> > > And so, it will be great if kernel team will like to package and
> > > maintain it, if not, then I will be happy to do it. Please
> > > reject this bug report if you think bpftool should not be done
> > > separately and should live inside kernel source package.
> >
> > Since you are already maintaining libbpf I would be happy to hand
> over
> > bpftool to you.  I will try to discuss this at this evening's team
> > meeting.
>
> What about moving libbpf and bpftool to the kernel team area under
> Salsa? That way more people can help, and it can use salsa-ci too

bpftool is already with the kernel team and being built from kernel
source. And I anticipated that bpftool will move to github like
upstream libbpf did and also mentioned that at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948041#83. So, its
upto the kernel team what they want to do with bpftool -
1. continue to build from kernel source and we can just close this bug
2. Split bpftool from kernel source and package it from github. The
kernel team can maintain if they want to maintain an userspace
package. If the kernel team does not want to maintain it, I can do
that.

About libbpf, I am confused with your message. What kind of help? Are
you seeing that libbpf is not maintained properly?


-- 
Regards
Sudip

Bug#1059414: open-ath9k-htc-firmware: diff for NMU version 1.4.0-108-gd856466+dfsg1-1.5

[Chris Hofstaedtler]

Control: tags 1059414 + pending


Dear maintainer,

I've prepared an NMU for open-ath9k-htc-firmware (versioned as 
1.4.0-108-gd856466+dfsg1-1.5) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog
--- open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog	2023-07-26 21:09:48.0 +0200
+++ open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog	2024-05-30 01:01:56.0 +0200
@@ -1,3 +1,10 @@
+open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install all files below /usr. (Closes: #1059414)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:01:56 +0200
+
 open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install
--- open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install	2023-07-26 21:09:18.0 +0200
+++ open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install	2024-05-30 01:01:52.0 +0200
@@ -1,2 +1,2 @@
-target_firmware/htc_*.fw lib/firmware/ath9k_htc/
+target_firmware/htc_*.fw usr/lib/firmware/ath9k_htc/
 debian/firmware-ath9k-htc.metainfo.xml usr/share/metainfo

Bug#1072185: farpd: Missing licenses

[Bastian Germann]

I am uploading a NMU to fix this and other issues.
The debdiff is attached.diff -Nru farpd-0.2/debian/changelog farpd-0.2/debian/changelog
--- farpd-0.2/debian/changelog  2023-09-05 20:05:19.0 +
+++ farpd-0.2/debian/changelog  2024-05-29 22:34:32.0 +
@@ -1,3 +1,15 @@
+farpd (0.2-11.4) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Send response to unicast instead of broadcast address (Closes: #698842)
+  * d/copyright: Convert to machine-readable format and add missing licenses
+(Closes: #1072185)
+  * d/control: Correct Standards-Version
+  * d/control: Add missing comma
+  * d/rules: Add missing dh_autoreconf_clean call
+
+ -- Bastian Germann   Wed, 29 May 2024 22:34:32 +
+
 farpd (0.2-11.3) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru farpd-0.2/debian/control farpd-0.2/debian/control
--- farpd-0.2/debian/control2023-08-17 22:18:37.0 +
+++ farpd-0.2/debian/control2024-05-29 22:34:32.0 +
@@ -3,11 +3,11 @@
 Priority: optional
 Maintainer: Javier Fernández-Sanguino Peña 
 Build-Depends: debhelper (>> 4.0.0), libdumbnet-dev, libpcap0.8-dev | 
libpcap-dev, libevent-dev, dh-autoreconf
-Standards-Version: 3.6.0.1
+Standards-Version: 3.6.0
 
 Package: farpd
 Architecture: any
-Depends: ${shlibs:Depends} ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Fake ARP user space daemon
  This ARP daemon replies to any ARP request for a set of IP addresses
  with the hardware MAC address of one of the interfaces of the
diff -Nru farpd-0.2/debian/copyright farpd-0.2/debian/copyright
--- farpd-0.2/debian/copyright  2023-08-17 22:18:27.0 +
+++ farpd-0.2/debian/copyright  2024-05-29 22:34:32.0 +
@@ -1,21 +1,23 @@
-This package was debianized by Javier Fernandez-Sanguino  on
-Thu, 27 Mar 2003 10:25:02 +0100.
-
-It was downloaded from http://www.citi.umich.edu/u/provos/honeyd/
-
-Upstream Authors: Dug Song and Niels Provos
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This package was debianized by Javier Fernandez-Sanguino  
on
+ Thu, 27 Mar 2003 10:25:02 +0100.
+Source:
+ http://www.citi.umich.edu/u/provos/honeyd/
+Upstream-Contact:
+ Dug Song 
+ Niels Provos 
 
+Files: *
 Copyright:
-
-  
   Copyright (c) 2000, 2001, 2002 Dug Song 
   Copyright (c) 2002 Niels Provos 
   All rights reserved, all wrongs reversed.
-
+License: BSD-3-clause
   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:
-
+ .
   1. Redistributions of source code must retain the above copyright
  notice, this list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright
@@ -24,7 +26,7 @@
   3. The names of the authors and copyright holders may not be used to
  endorse or promote products derived from this software without
  specific prior written permission.
-
+ .
   THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
   INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
   AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
@@ -36,3 +38,59 @@
   OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+Files: tree.h
+Copyright:
+ Copyright 2002 Niels Provos 
+ All rights reserved.
+License: BSD-2-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+ IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+ IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+ NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Files:
+ daemon.c
+ err.h
+Copyright:
+ Copyright (c) 2000 Dug Song 
+ Copyright (c) 1990, 1993
+  The Regents of the University of California.  All rights reserved.
+License: BSD-4-clause-UC
+ Redistribution and use in source and binary forms, with or without
+ modific

Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

[Pascal Hambourg]

On 26/05/2024 at 22:29, Roland Clobus wrote:


Your patch series works fine, the firmware is correctly identified and 
loaded. Unfortunately for me, it still needs a reconnect cycle.

See the attached syslog for their effect. (I've used sid)


Thank you for testing my patches but I did not expect them to solve the 
reattachment issue, only to identify the right module.


After the r8712u module is first loaded without the firmware then 
unloaded and reloaded, what is the output of


ls -d /sys/bus/usb/drivers/r8712u/1-3*
ls -d /sys/bus/usb/devices/1-3/1-3*

assuming the wireless adapter is identified as 1-3 ?

Bug#1060333: atmel-firmware: diff for NMU version 1.3-7.1

[Chris Hofstaedtler]

Control: tags 1060333 + pending


Dear maintainer,

I've prepared an NMU for atmel-firmware (versioned as 1.3-7.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru atmel-firmware-1.3/debian/changelog atmel-firmware-1.3/debian/changelog
--- atmel-firmware-1.3/debian/changelog	2023-01-18 01:51:47.0 +0100
+++ atmel-firmware-1.3/debian/changelog	2024-05-30 01:05:26.0 +0200
@@ -1,3 +1,10 @@
+atmel-firmware (1.3-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install files into /usr (DEP17 M2) (Closes: #1060333)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:05:26 +0200
+
 atmel-firmware (1.3-7) unstable; urgency=medium
 
   [ Cyril Brulebois ]
diff -Nru atmel-firmware-1.3/debian/rules atmel-firmware-1.3/debian/rules
--- atmel-firmware-1.3/debian/rules	2021-12-29 07:06:04.0 +0100
+++ atmel-firmware-1.3/debian/rules	2024-05-30 01:04:59.0 +0200
@@ -5,9 +5,9 @@
 
 override_dh_auto_install:
 	dh_auto_install
-	install -d -m 0755 debian/atmel-firmware/lib/firmware
-	install -m 0644 images/*.bin debian/atmel-firmware/lib/firmware
-	install -m 0644 images.usb/*.bin debian/atmel-firmware/lib/firmware
+	install -d -m 0755 debian/atmel-firmware/usr/lib/firmware
+	install -m 0644 images/*.bin debian/atmel-firmware/usr/lib/firmware
+	install -m 0644 images.usb/*.bin debian/atmel-firmware/usr/lib/firmware
 	install -D -m 0755 atmel_fwl.pl debian/atmel-firmware/usr/sbin/atmel_fwl
 	install -D -m 0644 atmel_fwl.8 debian/atmel-firmware/usr/share/man/man8/atmel_fwl.8
 	install -D -m 0644 atmel.conf debian/atmel-firmware/etc/pcmcia/atmel.conf

Bug#1072187: systemd: root fs read only if /tmp is in fstab

[David Burrows]

Package: systemd
Version: 256~rc3-5
Severity: important
X-Debbugs-Cc: burrows...@gmail.com

Dear Maintainer,

Installing this update led to my system booting with root (btrfs)
mounted as read only.

In my fstab I have the following:
tmpfs /tmp   tmpfs   
defaults,noatime,mode=1777 0 0

Commenting this out allowed the system to boot again with read/write.

In order to restore tmpfs I had to do the following (as root):
cp /usr/lib/systemd/system/tmp.mount /usr/share/systemd/tmp.mount

The is optional if you wish to have /tmp on root.

Prior to doing this it appears there is a broken symlink:
$ ls -l /etc/systemd/system/tmp.mount
lrwxrwxrwx 1 root root 28 Dec 30  2022 /etc/systemd/system/tmp.mount -> 
/usr/share/systemd/tmp.mount

I'm guessing that tmp in fstab is no longer default, but I didn't put it
there and it must be left over from an older install. This is consistent with
another 3 systems of mine.


-- Package-specific info:

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

Kernel: Linux 6.8.10-1-siduction-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 systemd depends on:
ii  libacl12.3.2-2
ii  libapparmor1   3.0.13-2
ii  libaudit1  1:3.1.2-2.1
ii  libblkid1  2.40.1-2
ii  libc6  2.38-11
ii  libcap21:2.66-5
ii  libcryptsetup122:2.7.2-2
ii  libfdisk1  2.40.1-2
ii  libmount1  2.40.1-2
ii  libpam0t64 [libpam0g]  1.5.3-4
ii  libseccomp22.5.5-1
ii  libselinux13.5-2+b2
ii  libssl3t64 3.2.1-3
ii  libsystemd-shared  256~rc3-5
ii  libsystemd0256~rc3-5
ii  mount  2.40.1-2

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.14.10-4+b1
ii  libzstd1 1.5.5+dfsg2-2
ii  systemd-timesyncd [time-daemon]  256~rc3-5

Versions of packages systemd suggests:
ii  libgcrypt20 1.10.3-3
ii  libidn2-0   2.3.7-2
ii  liblz4-11.9.4-2
ii  liblzma55.6.1+really5.4.5-1
ii  libtss2-rc0t64  4.1.0-1
ii  libtss2-tcti-device0t64 [libtss2-tcti-device0]  4.1.0-1
ii  polkitd 124-2
pn  systemd-boot
ii  systemd-container   256~rc3-5
pn  systemd-homed   
ii  systemd-resolved256~rc3-5
pn  systemd-userdbd 

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.10-4+b1
pn  dracut 
ii  initramfs-tools0.142
ii  libnss-systemd 256~rc3-5
ii  libpam-systemd 256~rc3-5
ii  udev   256~rc3-5

-- no debconf information

Bug#1006655: [PATCH] Implement rm_conffile_if_unmodified

[Guillem Jover]

Control: forcemerge 330256 -1

Hi,

On Tue, 2024-05-28 at 14:28:49 -0700, Josh Triplett wrote:
> tags 1006655 + patch
> thanks
> 
> I've attached a patch implementing an rm_conffile_if_unmodifed command
> for dpkg-maintscript-helper, as well as a declarative version for
> debian/conffiles.
> 
> I've included documentation and tests for both.
> 
> Using this has the same effect as rm_conffile if the file is unmodified.
> However, if the file is modified, this leaves the file in place under
> the existing name (treating it as an obsolete conffile so that it still
> gets removed if purging the package).
> 
> Thus, unlike rm_conffile, this version is useful for packages that still
> support reading the configuration file if present, and thus don't want
> to move existing modified configuration aside with a .dpkg-bak suffix,
> because that'll prevent the modified configuration from being used.

As I mentioned in #822462, I think the default should be changed instead
to do this. I sat yesterday to see how much this would imply code wise
and ended up with a smallish patch, which then required adapting few test
cases. I also added a new --assert-unmodified-obsolete-conffile-removal
(although I'm not entirely happy with such a long name). I'd still need
to add a few more tests for downgrades, but otherwise it seems to work
fine.

Being this such a behavior change, although it seems pretty safe to
me, I think it would still deserve to be discussed in debian-dpkg and
debian-devel. The only problematic thing that comes to mind, is that
it will be harder to spot conffiles that need to be marked as
remove-on-upgrade, as test systems would automatically get rid of
unmodified conffiles.

Will try to add the missing tests and push this into a branch tomorrow,
and then try to start a thread on the mailing lists during the week or so.

Regards,
Guillem

Bug#1059378: dahdi-firmware: diff for NMU version 2.11.1.0.20170917-2.1

[Chris Hofstaedtler]

Control: tags 1059378 + pending


Dear maintainer,

I've prepared an NMU for dahdi-firmware (versioned as 2.11.1.0.20170917-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru dahdi-firmware-2.11.1.0.20170917/debian/changelog dahdi-firmware-2.11.1.0.20170917/debian/changelog
--- dahdi-firmware-2.11.1.0.20170917/debian/changelog	2023-01-28 02:07:36.0 +0100
+++ dahdi-firmware-2.11.1.0.20170917/debian/changelog	2024-05-30 00:58:10.0 +0200
@@ -1,3 +1,10 @@
+dahdi-firmware (2.11.1.0.20170917-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install files into /usr instead of /. (Closes: #1059378)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 00:58:10 +0200
+
 dahdi-firmware (2.11.1.0.20170917-2) unstable; urgency=medium
 
   * Move source and binary from non-free/comm to non-free-firmware/comm
diff -Nru dahdi-firmware-2.11.1.0.20170917/debian/install dahdi-firmware-2.11.1.0.20170917/debian/install
--- dahdi-firmware-2.11.1.0.20170917/debian/install	2016-04-19 21:43:39.0 +0200
+++ dahdi-firmware-2.11.1.0.20170917/debian/install	2024-05-30 00:58:08.0 +0200
@@ -3,4 +3,4 @@
 debian/get-digium-firmware		usr/share/dahdi
 debian/OCT6104E-256D.ima		usr/share/dahdi
 build_tools/install_firmware		usr/share/dahdi
-drivers/dahdi/dahdi-fw-*.bin		lib/firmware/ 
+drivers/dahdi/dahdi-fw-*.bin		usr/lib/firmware/ 

Bug#1060358: rpcbind: diff for NMU version 1.2.6-8.1

[Chris Hofstaedtler]

Control: tags 1060358 + pending


Dear maintainer,

I've prepared an NMU for rpcbind (versioned as 1.2.6-8.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru rpcbind-1.2.6/debian/changelog rpcbind-1.2.6/debian/changelog
--- rpcbind-1.2.6/debian/changelog	2024-04-15 02:31:00.0 +0200
+++ rpcbind-1.2.6/debian/changelog	2024-05-30 00:53:15.0 +0200
@@ -1,3 +1,11 @@
+rpcbind (1.2.6-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install rpcbind into /usr/sbin (DEP17 M2). (Closes: #1060358)
+Update path in init script, systemd unit, et al.
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 00:53:15 +0200
+
 rpcbind (1.2.6-8) unstable; urgency=medium
 
   * Bump libtirpc-dev dependency to 1.3.4+ds-1.1. Closes: #1066880.
diff -Nru rpcbind-1.2.6/debian/init.d rpcbind-1.2.6/debian/init.d
--- rpcbind-1.2.6/debian/init.d	2024-04-15 02:31:00.0 +0200
+++ rpcbind-1.2.6/debian/init.d	2024-05-30 00:53:13.0 +0200
@@ -16,7 +16,7 @@
 #RPC include NFS and NIS.
 ### END INIT INFO
 
-test -f /sbin/rpcbind || exit 0
+test -f /usr/sbin/rpcbind || exit 0
 
 . /lib/lsb/init-functions
 
@@ -45,15 +45,15 @@
 exit 1
 fi
 [ -x /sbin/restorecon ] && /sbin/restorecon $STATEDIR
-pid=$( pidofproc /sbin/rpcbind )
+pid=$( pidofproc /usr/sbin/rpcbind )
 if [ -n "$pid" ]
 then
 log_action_msg "Already running: rpcbind"
 exit 0
 fi
 log_daemon_msg "Starting RPC port mapper daemon" "rpcbind"
-start-stop-daemon --start --quiet --oknodo --exec /sbin/rpcbind -- "$@"
-pid=$( pidofproc /sbin/rpcbind )
+start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/rpcbind -- "$@"
+pid=$( pidofproc /usr/sbin/rpcbind )
 echo -n "$pid" >"$PIDFILE"
 # /run/sendsigs.omit.d is created by /etc/init.d/mountkernfs.sh
 ln -sf "$PIDFILE" /run/sendsigs.omit.d/rpcbind
@@ -64,7 +64,7 @@
 stop ()
 {
 log_daemon_msg "Stopping RPC port mapper daemon" "rpcbind"
-start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --oknodo --exec /sbin/rpcbind
+start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --oknodo --exec /usr/sbin/rpcbind
 rm -f "$PIDFILE"
 log_end_msg $?
 }
@@ -90,7 +90,7 @@
 start $OPTIONS
 ;;
 status)
-status_of_proc /sbin/rpcbind rpcbind && exit 0 || exit $?
+status_of_proc /usr/sbin/rpcbind rpcbind && exit 0 || exit $?
 ;;
 *)
 log_success_msg "Usage: /etc/init.d/rpcbind {start|stop|force-reload|restart|status}"
diff -Nru rpcbind-1.2.6/debian/rpcbind.service rpcbind-1.2.6/debian/rpcbind.service
--- rpcbind-1.2.6/debian/rpcbind.service	2024-04-15 02:31:00.0 +0200
+++ rpcbind-1.2.6/debian/rpcbind.service	2024-05-30 00:53:13.0 +0200
@@ -13,7 +13,7 @@
 
 [Service]
 Environment="OPTIONS=-w"
-ExecStart=/sbin/rpcbind -f $OPTIONS
+ExecStart=/usr/sbin/rpcbind -f $OPTIONS
 EnvironmentFile=-/etc/rpcbind.conf
 EnvironmentFile=-/etc/default/rpcbind
 Type=notify
diff -Nru rpcbind-1.2.6/debian/rules rpcbind-1.2.6/debian/rules
--- rpcbind-1.2.6/debian/rules	2024-04-15 02:31:00.0 +0200
+++ rpcbind-1.2.6/debian/rules	2024-05-30 00:53:13.0 +0200
@@ -17,7 +17,7 @@
 	dh $@
 
 override_dh_auto_configure:
-	dh_auto_configure -- --sbindir=/sbin --enable-warmstarts --enable-libwrap --with-statedir=/run/rpcbind --with-rpcuser=_rpc --enable-debug $(CONFIGURE_EXTRA_FLAGS)
+	dh_auto_configure -- --enable-warmstarts --enable-libwrap --with-statedir=/run/rpcbind --with-rpcuser=_rpc --enable-debug $(CONFIGURE_EXTRA_FLAGS)
 
 execute_after_dh_auto_install:
 	rm -Rf debian/rpcbind/unused
diff -Nru rpcbind-1.2.6/debian/tests/check-if-installed rpcbind-1.2.6/debian/tests/check-if-installed
--- rpcbind-1.2.6/debian/tests/check-if-installed	2024-04-15 02:31:00.0 +0200
+++ rpcbind-1.2.6/debian/tests/check-if-installed	2024-05-30 00:53:13.0 +0200
@@ -1,5 +1,5 @@
 #!/bin/bash
 
-if [ ! -f "/sbin/rpcbind" ]; then
+if [ ! -f "/usr/sbin/rpcbind" ]; then
 >&2 echo "rpcbind is not installed"
 fi

Bug#1072172: ltsp-server: ltsp-build-client fails

[Jim Mintha]

Hi Vagrant,

My apologies, I guess I still had it in my sources or something.  I will use
the new package and follow the ltsp.org docs.

You can close the bug.

Jim

- On May 29, 2024, at 11:50 AM, Vagrant Cascadian vagr...@debian.org wrote:

> On 2024-05-29, Jim Mintha wrote:
>> Package: ltsp-server
>> Version: 5.18.12-3
>> Severity: normal
>>
>> After installing the ltsp-server (and -standalone) packages I ran:
>> ltsp-build-client.
>> First time it failed with:
> 
> ltsp-server, ltsp-build-client, and all ltsp 5.x components were last
> present two stable releases ago and are no longer part of Debian.  While
> you *might* be able to get it to work by adding buster
> (a.k.a. oldoldstable) sources and various manual tweaks, I would not
> recommend it at this point... it receives no real attention or
> maintenance upstream or in any distro.
> 
> The current LTSP support is available in Debian as the "ltsp" package,
> see:
> 
>  https://ltsp.org/docs/
> 
> live well,
>   vagrant

-- 
Jim Mintha   Email: j...@popdata.bc.ca
Systems & Security ManagerWork: +1 604 827-3378
Population Data BCHome: +1 604 730-4648
University of British Columbia
_There are always Possibilities_  http://www.mintha.com

Bug#1060344: ecryptfs-utils: diff for NMU version 111-6.1

[Chris Hofstaedtler]

Control: tags 1060344 + patch
Control: tags 1060344 + pending


Dear maintainer,

I've prepared an NMU for ecryptfs-utils (versioned as 111-6.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru ecryptfs-utils-111/debian/changelog ecryptfs-utils-111/debian/changelog
--- ecryptfs-utils-111/debian/changelog	2022-12-19 19:46:40.0 +0100
+++ ecryptfs-utils-111/debian/changelog	2024-05-30 00:48:02.0 +0200
@@ -1,3 +1,10 @@
+ecryptfs-utils (111-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install aliases files into /usr (DEP17 M2) (Closes: #1060344)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 00:48:02 +0200
+
 ecryptfs-utils (111-6) unstable; urgency=medium
 
   [ Andreas Metzler  ]
diff -Nru ecryptfs-utils-111/debian/ecryptfs-utils.install ecryptfs-utils-111/debian/ecryptfs-utils.install
--- ecryptfs-utils-111/debian/ecryptfs-utils.install	2013-02-09 08:05:28.0 +0100
+++ ecryptfs-utils-111/debian/ecryptfs-utils.install	2024-05-30 00:47:57.0 +0200
@@ -1,7 +1,7 @@
-lib/*/security
-sbin
+sbin/* usr/sbin/
 usr/bin
 usr/lib/*/ecryptfs
+usr/lib/*/security
 usr/share/doc
 usr/share/ecryptfs-utils
 usr/share/locale
diff -Nru ecryptfs-utils-111/debian/ecryptfs-utils.lintian-overrides ecryptfs-utils-111/debian/ecryptfs-utils.lintian-overrides
--- ecryptfs-utils-111/debian/ecryptfs-utils.lintian-overrides	2022-12-19 19:46:40.0 +0100
+++ ecryptfs-utils-111/debian/ecryptfs-utils.lintian-overrides	2024-05-30 00:47:57.0 +0200
@@ -1,3 +1,3 @@
 # false positives
-ecryptfs-utils: elevated-privileges 4755 root/root [sbin/mount.ecryptfs_private]
+ecryptfs-utils: elevated-privileges 4755 root/root [usr/sbin/mount.ecryptfs_private]
 ecryptfs-utils: executable-not-elf-or-script [usr/share/ecryptfs-utils/ecryptfs-record-passphrase]
diff -Nru ecryptfs-utils-111/debian/rules ecryptfs-utils-111/debian/rules
--- ecryptfs-utils-111/debian/rules	2020-06-16 21:31:59.0 +0200
+++ ecryptfs-utils-111/debian/rules	2024-05-30 00:47:57.0 +0200
@@ -21,7 +21,7 @@
 	dh_auto_configure -- \
 		--enable-gpg --enable-pam --enable-static --enable-tspi \
 		--disable-gui --disable-openssl --disable-pkcs11-helper \
-		--disable-pywrap \
+		--disable-pywrap --with-pamdir=/usr/lib/$(DEB_HOST_MULTIARCH)/security \
 		CFLAGS="$(CFLAGS)"
 
 override_dh_auto_install:
@@ -30,7 +30,7 @@
 	install -D -m 0644 debian/local/ecryptfs-utils.pam-auth-update debian/ecryptfs-utils/usr/share/pam-configs/ecryptfs-utils
 
 	# Adding kmod integration
-	install -D -m 0644 debian/local/ecryptfs-utils.kmod debian/ecryptfs-utils/lib/modules-load.d/ecryptfs.conf
+	install -D -m 0644 debian/local/ecryptfs-utils.kmod debian/ecryptfs-utils/usr/lib/modules-load.d/ecryptfs.conf
 
 	# Removing useless files
 	rm -f debian/tmp/usr/lib/*/*.la
@@ -38,7 +38,7 @@
 override_dh_fixperms:
 	dh_fixperms
 
-	chmod 4755 debian/ecryptfs-utils/sbin/mount.ecryptfs_private
+	chmod 4755 debian/ecryptfs-utils/usr/sbin/mount.ecryptfs_private
 
 override_dh_install:
 	dh_install --fail-missing

Bug#1058821: x2gothinclient: diff for NMU version 1.5.0.1-10.1

[Chris Hofstaedtler]

Control: tags 1058821 + patch
Control: tags 1058821 + pending


Dear maintainer,

I've prepared an NMU for x2gothinclient (versioned as 1.5.0.1-10.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru x2gothinclient-1.5.0.1/debian/changelog x2gothinclient-1.5.0.1/debian/changelog
--- x2gothinclient-1.5.0.1/debian/changelog	2023-05-19 10:59:29.0 +0200
+++ x2gothinclient-1.5.0.1/debian/changelog	2024-05-30 00:43:28.0 +0200
@@ -1,3 +1,10 @@
+x2gothinclient (1.5.0.1-10.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #1058821)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 00:43:28 +0200
+
 x2gothinclient (1.5.0.1-10) unstable; urgency=medium
 
   * debian/changelog:
diff -Nru x2gothinclient-1.5.0.1/debian/control x2gothinclient-1.5.0.1/debian/control
--- x2gothinclient-1.5.0.1/debian/control	2023-05-16 22:14:12.0 +0200
+++ x2gothinclient-1.5.0.1/debian/control	2024-05-30 00:43:25.0 +0200
@@ -8,7 +8,9 @@
 Build-Depends:
  debhelper-compat (= 13),
  qtbase5-dev,
+ pkgconf,
  po-debconf,
+ systemd-dev,
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Homepage: https://code.x2go.org/releases/source/x2gothinclient
diff -Nru x2gothinclient-1.5.0.1/debian/rules x2gothinclient-1.5.0.1/debian/rules
--- x2gothinclient-1.5.0.1/debian/rules	2022-10-03 11:48:15.0 +0200
+++ x2gothinclient-1.5.0.1/debian/rules	2024-05-30 00:43:25.0 +0200
@@ -4,6 +4,8 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 export QT_SELECT=qt5
 
 DHFLAGS=--parallel
diff -Nru x2gothinclient-1.5.0.1/debian/x2gothinclient-smartcardrules.install x2gothinclient-1.5.0.1/debian/x2gothinclient-smartcardrules.install
--- x2gothinclient-1.5.0.1/debian/x2gothinclient-smartcardrules.install	2019-12-13 12:28:30.0 +0100
+++ x2gothinclient-1.5.0.1/debian/x2gothinclient-smartcardrules.install	2024-05-30 00:43:25.0 +0200
@@ -1,3 +1,3 @@
-smartcardrules/21-x2gognupgccid.ruleslib/udev/rules.d/
+smartcardrules/21-x2gognupgccid.rules${env:deb_udevdir}/rules.d/
 smartcardrules/x2gognupgccid usr/lib/x2go/tce/
 
diff -Nru x2gothinclient-1.5.0.1/debian/x2gothinclient-usbmount.install x2gothinclient-1.5.0.1/debian/x2gothinclient-usbmount.install
--- x2gothinclient-1.5.0.1/debian/x2gothinclient-usbmount.install	2019-12-13 12:28:29.0 +0100
+++ x2gothinclient-1.5.0.1/debian/x2gothinclient-usbmount.install	2024-05-30 00:43:25.0 +0200
@@ -1,3 +1,3 @@
-usbmount/61-x2gousbmount.ruleslib/udev/rules.d/
+usbmount/61-x2gousbmount.rules${env:deb_udevdir}/rules.d/
 usbmount/x2gousbmount usr/lib/x2go/tce/
 

Bug#1072186: ITP: veristat -- Tool to load, verify and debug BPF object files

[Sudip Mukherjee]

Package: wnpp
Severity: wishlist
Owner: Sudip Mukherjee 
X-Debbugs-Cc: debian-de...@lists.debian.org, sudipm.mukher...@gmail.com

* Package name: veristat
  Version : 0.3.1
  Upstream Contact: many
* URL : https://github.com/libbpf/veristat
* License : GPL-2.0-only OR BSD-2-Clause
  Programming Lang: C
  Description : Tool to load, verify and debug BPF object files

veristat is the tool for loading, verifying, and debugging BPF object files.
It allows to work with BPF object files convenient and quickly, without having
to use or modify corresponding user-space parts of an application.


I can maintain this package.

-- 
Regards
Sudip

Bug#1072185: farpd: Missing licenses

[Bastian Germann]

Source: farpd
Version: 0.2-11
Severity: serious

The package includes more licenses than those that are listed in d/copyright.
A BSD-2-clause is in tree.h. BSD-4-clause-UC (copyright amendment allows
dropping the advertisement clause) is in daemon.c and err.h.

Bug#1065247: new lighttpd servers mangled file names

[gs-bugs . debian . org]

FYI, I submitted a patch to Debian on 19 March, over two months ago.

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

It has taken Debian developers (volunteers) over 10 weeks (!!!)
to pick up a simple patch that I packaged for them and signed on
salsa.debian.org. :(

Bug#1057290: bpftool: please build from https://github.com/libbpf/bpftool

[Luca Boccassi]

On Wed, 29 May 2024 19:00:59 +0100 Ben Hutchings 
wrote:
> On Sat, 2023-12-02 at 20:04 +, Sudip Mukherjee wrote:
> > And so, it will be great if kernel team will like to package and
> > maintain it, if not, then I will be happy to do it. Please
> > reject this bug report if you think bpftool should not be done
> > separately and should live inside kernel source package.
> 
> Since you are already maintaining libbpf I would be happy to hand
over
> bpftool to you.  I will try to discuss this at this evening's team
> meeting.

What about moving libbpf and bpftool to the kernel team area under
Salsa? That way more people can help, and it can use salsa-ci too

-- 
Kind regards,
Luca Boccassi


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

Bug#1072184: openssh-server: Please stop writing /var/log/btmp

[Chris Hofstaedtler]

Package: openssh-server
Severity: normal

Hi Colin,

util-linux 2.40.1-3 will, as part of moving last to src:wtmpdb, also
stop installing lastb(1).
wtmpdb provides no replacement for lastb.

Please disable writing /var/log/btmp.

While openssh-server can continue writing that file, AFAIK nothing will
be left to read it.

I didn't understand this was part of the upstream changes until now,
sorry.

Thanks,
Chris

Bug#1072092: piuparts: switch default tmpdir to /var/tmp/

[Luca Boccassi]

Control: affects -1 - piuparts debos vmdb2
Control: reassign -1 piuparts

On Tue, 28 May 2024 13:14:00 +0200 Helmut Grohne 
wrote:
> Control: reassign -1 debootstrap
> Control: affects -1 + piuparts debos vmdb2
> 
> On Tue, May 28, 2024 at 12:08:37PM +0100, Luca Boccassi wrote:
> > When piuparts runs debootstrap, it is pointed to the default --
tmpdir,
> > which absent any configuration or env var is /tmp/, which is now
(since
> > systemd 256~rc3-3) a tmpfs, which as it is expected it is mounted
with
> > noudev for security reasons, but debootstrap doesn't like that as
it
> > wants to create fresh node files.
> 
> This is a problem in debootstrap. debootstrap should refrain from
> creating device nodes when doing so is not possible. Most consumers
of
> debootstrap bind mount /dev already. Reassigning.

Feel free to work on that if you like, but it is unrelated

> > Please make piuparts --tmpdir default to /var/tmp if nothing is
set, to
> > avoid this issue.
> 
> Please don't as that would make reduce piuparts performance to crap.

Currently /tmp is on the same filesystem as /var/tmp, so there are zero
performance differences. It's just a default, you can change it as you
see fit if you have some special local setup.

-- 
Kind regards,
Luca Boccassi


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

Bug#1066060: libpam-modules: pam_lastlog.so missing

[Chris Hofstaedtler]

Control: retitle -1 login: remove lastlog, remove pam_lastlog.so from PAM config
Control: severity -1 important

Dear shadow maintainers,

as originally requested, please drop pam_lastlog.so from the PAM
config.

Please also drop the lastlog binary, which isn't very useful when
the data it is reading is not updated anymore.

Chris

Bug#1072183: fenics-dolfinx: FTBFS with nanobind 2.0

[Timo Röhling]

Source: fenics-dolfinx
Version: 1:0.8.0-6
Severity: serious
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

upgrading to nanobind 2.0 made your package FTBFS. I am sorry that I did not 
check this before uploading to unstable, that is on me. I have seen that 
Francesco has already fixed the issue upstream [1]. Depending on how far away 
the next upstream release is, maybe you can backport that fix?


Cheers
Timo

[1] 
https://github.com/FEniCS/dolfinx/commit/42c43485e81ada306f0b3f1dc735d95539174cbc


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmZXnqYACgkQzIxr3RQD
9MoXDQ/8DwVCja0oy6uOKmPj6O4OO87042AQMVEzcFKWvn88I+ORD1eSdUFvesgE
88ocsjLmR2YiUNN7vgEzobe/BGuFYizuKvHITpTVAG3Iwmnoh5UBzh2AMhGXEubO
TpuX84DG2k6nQjp5qTJrxCIOCgmzjy8iHjyN70csoX6Mjj5lAN+HSmMmBVym8Tmn
EIbAFCRB1qJwmMyGXlAN9pCqQg5SmV6ikpyIfcB+T4XBdGS5F8LSF4T6qsWpHtyq
HrEgZoubY9DQxEHMUsS+UPzZBj509box1ldl7DuaPJ7JG0/PvEOuzpmuNhOmivPy
69SNnbWjVI/Y7xDH9vYaBNW2H78kybjB6oOKdEw9t/S+yN1gaLK+Jjj1Ifec1iI/
5XZ5vBo8yqF5ORpJ/dDd9LQrEukqiE+89xCa0/i6jcDSmMWwsymk11HsqDs9SxBv
+y1fINhM9C0LtvUXCJbkhFwnYoRF6q5g/GmZ7XNAJHJZTaSJfF3skLYY+5tWLv0o
h+XlcS/zyApl9dMR/uE6Az7DqpcQi0rJNseyd17j69svjChyJSSw9wAjaYYtrwrA
0aRzR58oIEfW1NVJObAlWwgmukOlGQJeZ2yRJgO8Utx1hKKbl5D3cCx4LyBEFGuH
k1ShEvxa0LPDPsrVtotY6UeGIrVKBMzfXSjXkxLbVWsPPHth8wY=
=+PF7
-END PGP SIGNATURE-

Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

[Emanuele Rocca]

Hello Thorsten,

On 2024-05-27 02:31, Thorsten Leemhuis wrote:
> Would also help a lot to know if this is a 6.8.y only thing, or happens
> with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.

I could reproduce the issue with 6.9.2 too, will try mainline tomorrow.

FTR the procedure is quite simple. To build a sid qemu testbed:

 autopkgtest-build-qemu unstable /tmp/sid.img

Run the autopkgtest:

 autopkgtest -ddd -B dpdk -- autopkgtest-virt-qemu --debug --show-boot 
/tmp/sid.img

After a while the test hangs with:

 autopkgtest-virt-qemu: DBG: executing copydown /tmp/alog/tests-tree/ 
/tmp/autopkgtest.uG6tsJ/build.6QA/src/
 [...]
 autopkgtest-virt-qemu: DBG:  +>?

Then one can build a new kernel with:

 make oldconfig
 scripts/config --disable DEBUG_INFO
 scripts/config --disable DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT
 make -j`nproc` bindeb-pkg

Boot the QCOW image:

 qemu-system-x86_64 -cpu host -machine accel=kvm -drive 
file=sid.img,format=qcow2 -m 4G -smp `nproc`

Upgrade the kernel, and run the autopkgtest again as above.

  Emanuele

Bug#1005961: nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4

[Bastian Germann]

I suggest fq renames the binary because it was introduced over 4 years later 
and has only been in one release so far.

Bug#1070322: marked as pending in kio

[Andreas B. Mundt]

Hi,

I started testing the patched kio. Unfortunatelly, it seems to not fix
all issues.  To ease testing, I export and mount from localhost and
run the following (note the link counter in ls -l):  

andi@kde:/media/samba$ ls -l test.tar.gz
ls: cannot access 'test.tar.gz': No such file or directory
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 1 andi andi 147 May 29 21:59 test.tar.gz
   ^
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 0 andi andi 147 May 29 21:59 test.tar.gz
   ^
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 1 andi andi 147 May 29 22:00 test.tar.gz
   ^
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 0 andi andi 147 May 29 22:00 test.tar.gz
   ^
andi@kde:/media/samba$ ls -l test.tar.gz
ls: cannot access 'test.tar.gz': No such file or directory

So if the archive exists, it is removed, if newly generated, it works.
No idea why the file shows up with link counter 0 if the file is
listed immediately after running ark.  It's gone if listed seperately.

Find below some more information about the setup, perhaps this gives
someone some ideas.  I'll continue tomorrow.

Best regards,

  Andi


andi@kdedaily:/media/samba$ grep -vE "^(#|;|$)" /etc/samba/smb.conf 
[global]
   workgroup = WORKGROUP
   log file = /var/log/samba/log.%m
   max log size = 1000
   logging = file
   panic action = /usr/share/samba/panic-action %d
   server role = standalone server
   obey pam restrictions = yes
   unix password sync = yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* 
%n\n *password\supdated\ssuccessfully* .
   pam password change = yes
   map to guest = bad user
   usershare allow guests = yes
[homes]
   comment = Home Directories
   browseable = no
   read only = no
   create mask = 0700
   directory mask = 0700
   valid users = %S
[printers]
   comment = All Printers
   browseable = no
   path = /var/tmp
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no

mount:
//localhost/homes/ on /media/samba type cifs 
(rw,nosuid,nodev,relatime,vers=3.1.1,cache=strict,username=andi,uid=1000,noforceuid,gid=1000,noforcegid,addr=:::::::0001,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,nobrl,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1,user=andi)

fstab:
//localhost/homes/ /media/samba cifs  user,nobrl,user=andi,password=123 0 0

apt list "libkf5kio*" "kio*" | grep install
kio-extras-data/stable,stable,now 4:22.12.3-1 all [installed,automatic]
kio-extras/stable,now 4:22.12.3-1 amd64 [installed,automatic]
kio-ldap/stable,now 22.12.3-1 amd64 [installed,automatic]
kio/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiocore5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiofilewidgets5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiogui5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiontlm5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiowidgets5/now 5.103.0-1+deb12u1 amd64 [installed,local]

Bug#1071501: [PATCH] NFS: add barriers when testing for NFS_FSDATA_BLOCKED

[NeilBrown]

On Wed, 29 May 2024, Trond Myklebust wrote:
> On Tue, 2024-05-28 at 11:19 +1000, NeilBrown wrote:
> > On Tue, 28 May 2024, Trond Myklebust wrote:
> > > On Mon, 2024-05-27 at 13:04 +1000, NeilBrown wrote:
> > > > 
> > > > dentry->d_fsdata is set to NFS_FSDATA_BLOCKED while unlinking or
> > > > renaming-over a file to ensure that no open succeeds while the
> > > > NFS
> > > > operation progressed on the server.
> > > > 
> > > > Setting dentry->d_fsdata to NFS_FSDATA_BLOCKED is done under -
> > > > >d_lock
> > > > after checking the refcount is not elevated.  Any attempt to open
> > > > the
> > > > file (through that name) will go through lookp_open() which will
> > > > take
> > > > ->d_lock while incrementing the refcount, we can be sure that
> > > > once
> > > > the
> > > > new value is set, __nfs_lookup_revalidate() *will* see the new
> > > > value
> > > > and
> > > > will block.
> > > > 
> > > > We don't have any locking guarantee that when we set ->d_fsdata
> > > > to
> > > > NULL,
> > > > the wait_var_event() in __nfs_lookup_revalidate() will notice.
> > > > wait/wake primitives do NOT provide barriers to guarantee order. 
> > > > We
> > > > must use smp_load_acquire() in wait_var_event() to ensure we look
> > > > at
> > > > an
> > > > up-to-date value, and must use smp_store_release() before
> > > > wake_up_var().
> > > > 
> > > > This patch adds those barrier functions and factors out
> > > > block_revalidate() and unblock_revalidate() far clarity.
> > > > 
> > > > There is also a hypothetical bug in that if memory allocation
> > > > fails
> > > > (which never happens in practice) we might leave ->d_fsdata
> > > > locked.
> > > > This patch adds the missing call to unblock_revalidate().
> > > > 
> > > > Reported-and-tested-by: Richard Kojedzinszky
> > > > 
> > > > Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071501
> > > > Fixes: 3c59366c207e ("NFS: don't unhash dentry during
> > > > unlink/rename")
> > > > Signed-off-by: NeilBrown 
> > > > ---
> > > >  fs/nfs/dir.c | 44 +---
> > > >  1 file changed, 29 insertions(+), 15 deletions(-)
> > > > 
> > > > diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
> > > > index ac505671efbd..c91dc36d41cc 100644
> > > > --- a/fs/nfs/dir.c
> > > > +++ b/fs/nfs/dir.c
> > > > @@ -1802,9 +1802,10 @@ __nfs_lookup_revalidate(struct dentry
> > > > *dentry,
> > > > unsigned int flags,
> > > >     if (parent != READ_ONCE(dentry->d_parent))
> > > >     return -ECHILD;
> > > >     } else {
> > > > -   /* Wait for unlink to complete */
> > > > +   /* Wait for unlink to complete - see
> > > > unblock_revalidate() */
> > > >     wait_var_event(&dentry->d_fsdata,
> > > > -      dentry->d_fsdata !=
> > > > NFS_FSDATA_BLOCKED);
> > > > +      smp_load_acquire(&dentry-
> > > > >d_fsdata)
> > > > +      != NFS_FSDATA_BLOCKED);
> > > 
> > > Doesn't this end up being a reversed ACQUIRE+RELEASE as described
> > > in
> > > the "LOCK ACQUISITION FUNCTIONS" section of Documentation/memory-
> > > barriers.txt?
> > 
> > I don't think so.  That section is talking about STORE operations
> > which
> > can move backwards through ACQUIRE and forwards through RELEASE.
> > 
> > Above we have a LOAD operation which mustn't move backwards through
> > ACQUIRE.  Below there is a STORE operation which mustn't move
> > forwards
> > through a RELEASE.  Both of those are guaranteed.
> 
> It isn't necessary for the LOAD to move backwards through the ACQUIRE.
> As I understand it, the point is that the ACQUIRE can move through the
> RELEASE as per the following paragraph in that document:
> 
> Similarly, the reverse case of a RELEASE followed by an ACQUIRE 
> does
> not imply a full memory barrier.  Therefore, the CPU's execution 
> of the
> critical sections corresponding to the RELEASE and the ACQUIRE 
> can cross,
> so that:
> 
> *A = a;
> RELEASE M
> ACQUIRE N
> *B = b;
> 
> could occur as:
> 
> ACQUIRE N, STORE *B, STORE *A, RELEASE M

On the wakeup side we have:

  STORE ->d_fsdata
  RELEASE
  spin_lock
  LOAD: check is waitq is empty

and on the wait side we have

  STORE: add to waitq
  spin_unlock
  ACQUIRE
  LOAD ->d_fsdata

I believe that spin_lock is an ACQUIRE operation and spin_unlock is a
RELEASE operation.  So both of these have "ACQUIRE ; RELEASE" which
creates a full barrier.

> 
> This would presumably be why the function clear_and_wake_up_bit() needs
> a full memory barrier on most architectures, instead of being just an
> smp_wmb(). Is my understanding of this wrong?

clear_and_wake_up_bit() calls __wake_up_bit() which calls
waitqueue_active() without taking a lock.  So there is no ACQUIRE after
the RELEASE in c

Bug#1071432: /recent no longer working for debian-devel-changes

[Alexander Wirt]

On Thu, May 23, 2024 at 02:04:38PM +0200, di dit wrote:
> The original bug seems to me to be fixed but there is another issue
> which as far as I know affects only:
>   https://lists.debian.org/debian-devel-changes/recent
> The message is:
>  name 'cmp' is not defined
> 
> I didn't open a new bug report becauseit is related to "cmp" too but
> maybe it is unrelated.
> 
Oh man, fixed. Thanks

Alex


signature.asc
Description: PGP signature

Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11

[Niko Tyni]

On Wed, May 29, 2024 at 02:16:47PM +0800, Aron Xu wrote:
> On Wed, May 29, 2024 at 12:16 AM gregor herrmann  wrote:

> > Warning: program compiled against libxml 212 using older 209
> >
> > and this comes from libxml:
> >
> > https://sources.debian.org/src/libxml2/2.12.7+dfsg-2/parserInternals.c/?hl=79#L79
> >
> > if ((myversion / 100) < (version / 100)) {
> > xmlGenericError(xmlGenericErrorContext,
> > "Warning: program compiled against libxml %d using older 
> > %d\n",
> > (version / 100), (myversion / 100));
> > }
> >
> >
> > Not sure if this is should be fixed in libxml2 or if we should add an
> > artifical dependency on a newer libxml2 (to avoid testing against the
> > version in testing). The former sounds more logic to me.
> >
> 
> Although it looks trivial to remove the warning from libxml2, I'm
> reluctant since this piece of code existed for a very long time, a
> random check shows that version 2.2.3 (in 2000) has the logic:
> https://gitlab.gnome.org/GNOME/libxml2/-/blob/04698d9e1c56467007fcbb9472e5db67cf5938f5/parserInternals.c#L66

I'm a bit surprised that we haven't suffered from this before.  We've been
patching away similar things on the libxml-libxml-perl side.

But I see it only triggers with libxml2 "middle version" changes (2.x -> 2.y), 
and 
the last time that happened in Debian was in 2013. The autopkgtest checks were
not a thing back then, and I guess we've just tolerated the stderr warnings
or requested a rebuild of libxml-libxml-perl.

I suppose rebuilding on these "middle version" libxml2 changes is okay if
you want to keep the warning, even if the rebuild is strictly speaking
unnecessary. It's even conceivable that XML::LibXML might pick up new
features with the rebuild (for better or worse.)

But I think we should add dependency metadata so that the release team,
britney, debci etc. can see the need for a rebuild when we have a
"broken" combination, and then hint the "correct" versions for testing
migration together.  Updating libxml2 "middle version" would then mean
a mini-transition.

At the moment that would mean having libxml-libxml-perl
  Depends: libxml2 (>> 2.12), libxml2 (<< 2.13~)
or something like that, with the numbers automatically generated during
the build of course.

And libxml2 would need a one-time
  Breaks: libxml-libxml-perl (<<  2.0207+dfsg+really+2.0134-3)
or whichever version introduces the above dependencies.

Does that make sense or sound overkill?
-- 
Niko

Bug#1055619: Interested to be new maintainer

[Mwadime Makokha]

I am interested in being a new maintainer of the python-inotify package. I
would like your guidance.

-- 
*Mwadime Makokha*

Bug#1063754: fat-modules: SD corruption upon opening file on Linux desktop

[Ben Hutchings]

Control: tag -1 unreproducible moreinfo

Hi Bud,

Please understand that when I aksed you to carry out a specific test, I
had a good reason for doing exactly that.  The tests that you have
carried out so far, while useful, don't provide the same information.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.



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

Bug#1071706: Acknowledgement (networkctl.1: some remarks and editorial changes for this man page)

[Bjarni Ingi Gislason]

  All generated man pages MUST have a comment telling:

what is generating them

its version

from what file is it done.

  This should be in the Debian policy!

Bug#1072172: ltsp-server: ltsp-build-client fails

[Vagrant Cascadian]

On 2024-05-29, Jim Mintha wrote:
> Package: ltsp-server
> Version: 5.18.12-3
> Severity: normal
>
> After installing the ltsp-server (and -standalone) packages I ran: 
> ltsp-build-client.  
> First time it failed with:

ltsp-server, ltsp-build-client, and all ltsp 5.x components were last
present two stable releases ago and are no longer part of Debian.  While
you *might* be able to get it to work by adding buster
(a.k.a. oldoldstable) sources and various manual tweaks, I would not
recommend it at this point... it receives no real attention or
maintenance upstream or in any distro.

The current LTSP support is available in Debian as the "ltsp" package,
see:

  https://ltsp.org/docs/

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1071629: Acknowledgement (loginctl.1: some remarks and editorial changes for this man page)

[Bjarni Ingi Gislason]

  All generated man pages MUST have a comment telling:

what is generating them

what is its version

from what file is it done.

  This should be in the Debian policy!

Bug#966621: Make /tmp/ a tmpfs and cleanup /var/tmp/ on a timer by default [was: Re: systemd: tmpfiles.d not cleaning /var/tmp by default]

[Lyndon Brown]

On Wed, 2024-05-29 at 18:58 +0200, Andreas Metzler wrote:
> Hello,
> 
> That is false dichotomy. data-loss will occur when people use /tmp or
> /var/tmp for persistent data-storage because "This has (for a couple
> of
> years) worked on Debian systems" not because "This has (for a couple
> of
> years) worked on *this* *specific* Debian system.".
> 
> cu Andreas

I think you might be missing the point that this is the *DEFAULT*
behaviour. You're free to override it. If you personally have no
precious data in tmp storage to worry about then after upgrade you can
simply tweak the config to enable the new behaviour, as I have done.

I'm using Sid and after doing a little reading up on the topic
yesterday after the upgrade I believe all that needed doing was to
delete the /etc/tmpfiles.d/tmp.conf file, which as I understand it
contains a simple override of the new behaviour defined in
/usr/lib/tmpfiles.d/tmp.conf.

FWIW I think Luca made a perfectly sensible choice here.

Bug#1057290: bpftool: please build from https://github.com/libbpf/bpftool

[Ben Hutchings]

On Sat, 2023-12-02 at 20:04 +, Sudip Mukherjee wrote:
> Package: bpftool
> Severity: wishlist
> X-Debbugs-Cc: sudipm.mukher...@gmail.com, debian-ker...@lists.debian.org, 
> debian-de...@lists.debian.org
> 
> The official home for bpftool is now the github repo [1] but
> keeps the kernel as the authoritative source code of bpftool and
> is developed as part of the bpf-next Linux source tree.

I don't really understand the distinction they're trying to make
between "official" and "authoritative"...

> The Maintainers have said "Please use this Github repository for
> building and packaging bpftool" at [2] The announcement was at [3].
>
> imho, packaging it from the github instead of the kernel source
> will fix three issues:
> 1. bpftool will use libbpf available in Debian, whereas now it is
> building a libbpf.a from the development codes of libbpf in the
> kernel source and using that.

That's certainly a good reason.

> 2. The official releases of bpftool is done in the github repo
> when the bpf maintainers decides the code is ready for a release.
> But the Debian bpftool package is done from the kernel source and
> so follows the kernel releases. And as a result, when a new
> kernel is released which Debian kernel team will then pickup may
> not have a bpftool release worthy code. For example, bpftool v7.3
> was released on 23/11/2023,

So bpftool does not get stabilised in the kernel?  I don't really
understand why it's still in the kernel tree at all then!

> 3. bpftool package in Debian is from the kernel v6.5.13 and so
> looking at the source and git commits I can see the that the
> Debian package is missing 25 commits which is in the bpftool v7.3
> release.

Right.

> Do we package bpftool from their github repo independent of the
> kernel update? Then we will need to remove the bpftool building
> bits from the Debian kernel source and create a separate package
> for bpftool.
> 
> And so, it will be great if kernel team will like to package and
> maintain it, if not, then I will be happy to do it. Please
> reject this bug report if you think bpftool should not be done
> separately and should live inside kernel source package.

Since you are already maintaining libbpf I would be happy to hand over
bpftool to you.  I will try to discuss this at this evening's team
meeting.

Ben.

> 
> [1]. https://github.com/libbpf/bpftool
> [2]. https://github.com/libbpf/bpftool/blob/main/README.md?plain=1#L18
> [3]. 
> https://lore.kernel.org/bpf/267a35a6-a045-c025-c2d9-78afbf6fc...@isovalent.com/
> 

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.



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

Bug#1072105: /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring.

[Luca Boccassi]

Control: close -1

On Wed, 29 May 2024 20:15:36 +0200 Michael Biebl 
wrote:
> Control: reopen -1
> 
> On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi 
wrote:
> > Control: tags -1 wontfix
> > Control: close -1
> > 
> > On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl 
> > wrote:
> > > Package: systemd
> > > Version: 256~rc3-4
> > > Severity: normal
> > > 
> > > 
> > > Please do not not ship conflicting configuration for /run/lock
> > > 
> > > /usr/lib/tmpfiles.d/debian.conf:d /run/lock    1777 root root -  
-
> > > /usr/lib/tmpfiles.d/legacy.conf:d /run/lock 0755 root root -
> > > 
> > > triggering unnecessary warnings.
> > 
> > This is needed to apply debian-specific changes, just ignore it,
it's
> > harmless
> 
> Besides the obvious warning message, shipping conflicting tmpfiles 
> configuration snippets also has the problem, that depending on which 
> file you override, one or the other becomes active.
> 
> Say you create a /etc/tmpfiles.d/debian.conf, then the configuration
in 
> legacy.conf becomes active and vise versa.
> This is highly confusing.

Yes, that is normal - if you change something, you need to check what's
there and what's not. This is not a new problem.

> tmpfiles entries are not easily overridable, as the mechanism is per 
> file and not per entry.
> 
> So, either legacy.conf gets split up so individual entries can be 
> overridden or your patch legacy.conf.
> 
> The current approach is not sufficient.

No. The current approach is just fine. If you don't like seeing the
harmless notice-level log, just add a local override in /etc/.

> Btw, please don't close bug reports without CCing the bug submitter. 
> That's rude.

Please stop playing ping pong with the BTS, this is staying as it is.

-- 
Kind regards,
Luca Boccassi


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

Bug#1072177: systemd: some software crash at system start-up

[Luca Boccassi]

Control: tags -1 moreinfo

On Wed, 29 May 2024 19:08:02 +0200 Grzegorz  wrote:
> Package: systemd
> Version: 256~rc3-2
> Severity: minor
> X-Debbugs-Cc: grzeg...@gmail.com
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
appropriate ***
> 
>    * What led up to the situation?
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
>    * What was the outcome of this action?
>    * What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***

"some software crash at system start-up" is not an actionable bug
report. Please provide details - what, where, how, decoded backtraces,
etc.

-- 
Kind regards,
Luca Boccassi


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

Bug#1072105: /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring.

[Michael Biebl]

Control: reopen -1

On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi  wrote:

Control: tags -1 wontfix
Control: close -1

On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl 
wrote:
> Package: systemd
> Version: 256~rc3-4
> Severity: normal
> 
> 
> Please do not not ship conflicting configuration for /run/lock
> 
> /usr/lib/tmpfiles.d/debian.conf:d /run/lock    1777 root root -   -

> /usr/lib/tmpfiles.d/legacy.conf:d /run/lock 0755 root root -
> 
> triggering unnecessary warnings.


This is needed to apply debian-specific changes, just ignore it, it's
harmless


Besides the obvious warning message, shipping conflicting tmpfiles 
configuration snippets also has the problem, that depending on which 
file you override, one or the other becomes active.


Say you create a /etc/tmpfiles.d/debian.conf, then the configuration in 
legacy.conf becomes active and vise versa.

This is highly confusing.

tmpfiles entries are not easily overridable, as the mechanism is per 
file and not per entry.


So, either legacy.conf gets split up so individual entries can be 
overridden or your patch legacy.conf.


The current approach is not sufficient.


Btw, please don't close bug reports without CCing the bug submitter. 
That's rude.


Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071531: RFS: fvwm3/1.1.0+ds-1 -- F(?) Virtual Window Manager

[Phil Wyett]

Hi Jaimos,

Many thanks for taking the time to package this application.

Package builds perfect, the only issues I see is with 'debian/copyright'.
Running 'lrc' against the tree we get the below output.

Parsing Source Tree  
Reading copyright
Running licensecheck 

d/copyright | licensecheck

GPL-2   | GPL-2+   bin/fvwm-convert-2.6.in
GPL-2   | GPL-2+   bin/fvwm-menu-directory.in
GPL-2   | GPL-2+   bin/fvwm-menu-xlock.in
GPL-2   | GPL-2+   bin/fvwm-perllib.in
GPL-2   | GPL-2+   bin/fvwm-root.c
GPL-2   | GPL  doc/fvwm3_manpage_source.adoc
GPL-2   | GPL-2+   fvwm/add_window.c
GPL-2   | GPL-2+   fvwm/bindings.c
GPL-2   | GPL-2+   fvwm/borders.c
GPL-2   | GPL-2+   fvwm/builtins.c
GPL-2   | GPL-2+   fvwm/cmdparser_old.c
GPL-2   | GPL-2+   fvwm/colormaps.c
GPL-2   | GPL-2+   fvwm/colormaps.h
GPL-2   | GPL-2+   fvwm/colorset.c
GPL-2   | GPL-2+   fvwm/conditional.c
GPL-2   | GPL-2+   fvwm/condrc.c
GPL-2   | GPL-2+   fvwm/cursor.c
GPL-2   | GPL-2+   fvwm/decorations.c
GPL-2   | GPL-2+   fvwm/events.c
GPL-2   | GPL-2+   fvwm/ewmh.c
GPL-2   | GPL-2+   fvwm/ewmh_conf.c
GPL-2   | GPL-2+   fvwm/ewmh_events.c
GPL-2   | GPL-2+   fvwm/ewmh_icons.c
GPL-2   | GPL-2+   fvwm/ewmh_names.c
GPL-2   | GPL-2+   fvwm/execcontext.c
GPL-2   | GPL-2+   fvwm/expand.c
GPL-2   | GPL-2+   fvwm/focus.c
GPL-2   | GPL-2+   fvwm/focus_policy.c
GPL-2   | GPL-2+   fvwm/frame.c
GPL-2   | GPL-2+   fvwm/functable.c
GPL-2   | GPL-2+   fvwm/functable_complex.c
GPL-2   | GPL-2+   fvwm/functions.c
GPL-2   | GPL-2+   fvwm/fvwm3.c
GPL-2   | GPL-2+   fvwm/geometry.c
GPL-2   | GPL-2+   fvwm/icccm2.c
GPL-2   | GPL-2+   fvwm/icons.c
GPL-2   | GPL-2+   fvwm/infostore.c
GPL-2   | GPL-2+   fvwm/menubindings.c
GPL-2   | GPL-2+   fvwm/menucmd.c
GPL-2   | GPL-2+   fvwm/menudim.c
GPL-2   | GPL-2+   fvwm/menugeometry.c
GPL-2   | GPL-2+   fvwm/menuitem.c
GPL-2   | GPL-2+   fvwm/menus.c
GPL-2   | GPL-2+   fvwm/menustyle.c
GPL-2   | GPL-2+   fvwm/misc.c
GPL-2   | GPL-2+   fvwm/modconf.c
GPL-2   | GPL-2+   fvwm/module_interface.c
GPL-2   | GPL-2+   fvwm/module_list.c
GPL-2   | GPL-2+   fvwm/move_resize.c
GPL-2   | GPL-2+   fvwm/placement.c
GPL-2   | GPL-2+   fvwm/read.c
GPL-2   | GPL-2+   fvwm/schedule.c
GPL-2   | NTP~disclaimer   fvwm/screen.h
GPL-2   | GPL-2+   fvwm/session.c
GPL-2   | GPL-2+   fvwm/stack.c
GPL-2   | GPL-2+   fvwm/style.c
GPL-2   | GPL-2+   fvwm/update.c
GPL-2   | GPL-2+   fvwm/virtual.c
GPL-2   | GPL-2+   fvwm/windowlist.c
GPL-2   | GPL-2+   fvwm/windowshade.c
GPL-2   | ISC  libs/asprintf.c
GPL-2   | GPL-2+   libs/BidiJoin.c
GPL-2   | GPL-2+   libs/Bindings.c
GPL-2   | GPL-2+   libs/charmap.c
GPL-2   | Expatlibs/cJSON.c
GPL-2   | Expatlibs/cJSON.h
GPL-2   | GPL-2+   libs/ClientMsg.c
GPL-2   | GPL-2+   libs/Colorset.c
GPL-2   | LGPL-2+  libs/ColorUtils.c
GPL-2   | GPL-2+   libs/CombineChars.c
GPL-2   | GPL-2+   libs/Cursor.c
GPL-2   | GPL-2+   libs/envvar.c
GPL-2   | GPL-2+   libs/Event.c
GPL-2   | GPL-2+   libs/FBidi.c
GPL-2   | GPL-2+   libs/FEvent.c
GPL-2   | GPL-2+   libs/Fft.c
GPL-2   | GPL-2+   libs/FGettext.c
GPL-2   | GPL-2+   libs/Ficonv.c
GPL-2   | GPL-2+   libs/FImage.c
GPL-2   | GPL-2+   libs/fio.c
GPL-2   | GPL-2+   libs/flist.c
GPL-2   | GPL-2+ and/or NTP libs/Flocale.c
GPL-2   | GPL-2+   libs/FlocaleCharset.c
GPL-2   | GPL-2+   libs/fqueue.c
GPL-2   | GPL-2+   libs/FRender.c
GPL-2   | GPL-2+   libs/FRenderInit.c
GPL-2   | GPL-2+   libs/FScreen.c
GPL-2   | GPL-2+   libs/FShape.c
GPL-2   | GPL-2+   libs/fsm.c
GPL-2   | GPL-2+   libs/FTips.c
GPL-2   | GPL-2+   libs/fvwmlib3.c
GPL-2 

Bug#1072182: delta: upstream location and 2020-06-22 release

[Matt Taggart]

Package: delta
Version: 2006.08.03-13

Maybe the upstream for delta is now

https://github.com/dsw/delta

There was a release on 2020-06-22 which is newer than what the package 
is using, although looking at the commits it's mostly just documentation 
changes.


popcon doesn't show many people using this, but if you care about it 
please adopt it!


--
Matt Taggart
m...@lackof.org

Bug#1072110: glslang breaks shaderc autopkgtest: undefined reference: ABI breakage?? -- not the case

[Philippe SWARTVAGHER]

Hello,

Well, this issue is "normal".

Currently, shaderc 2023.2-1 is in testing. This version suffers from an
"undefined symbol" bug
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070983). This bug is
fixed in version 2023.8-1 which is now in unstable. However, this
version never migrated to testing due to a blocking bug in glslang
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062799). This bug in
glslang is now fixed with the last upload.

I'm a beginner regarding this kind transition / blocking bug / CI, so I
don't know how this bug can be solved...

I don't know if it helps, but I have a RFS
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072181) for a new
version of shaderc (which changes nothing about this bug). You can see
on Salsa that autopkgtests pass with the version of glslang available in
unstable: https://salsa.debian.org/debian/shaderc/-/pipelines/683648.


Philippe.

Bug#1072181: RFS: shaderc/2024.1-1 -- Library API for accessing glslc functionality - shared libraries

[Philippe SWARTVAGHER]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : shaderc
   Version  : 2024.1-1
   Upstream contact : David Neto 
 * URL  : https://github.com/google/shaderc/
 * License  : Apache-2.0, BSD-3-clause
 * Vcs  : https://salsa.debian.org/debian/shaderc
   Section  : libs

The source builds the following binary packages:

  glslc - Command line compiler for GLSL/HLSL to SPIR-V
  libshaderc-dev - Library API for accessing glslc functionality -
static libraries and headers
  libshaderc1 - Library API for accessing glslc functionality - shared
libraries

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/s/shaderc/shaderc_2024.1-1.dsc

Changes since the last upload:

 shaderc (2024.1-1) unstable; urgency=medium
 .
   * New upstream release
 - Refresh patch use-system-thirdparties.patch and drop patches applied
   upstream
   * Add "Forwarded: not-needed" to d/patches/rename-libshaderc.patch
   * Bump Standards-Version to 4.7.0: no change needed
   * Refresh d/copyright

Regards,
--
  Philippe

Bug#966621: Make /tmp/ a tmpfs and cleanup /var/tmp/ on a timer by default [was: Re: systemd: tmpfiles.d not cleaning /var/tmp by default]

[Noah Meyerhans]

On Wed, May 29, 2024 at 06:58:32PM +0200, Andreas Metzler wrote:
> >> I think it is bad choice to deliberately have different behavior for
> >> freshly installed and upgraded systems. Offering upgrades has always
> >> been one of the major selling points of Debian, and imho this
> >> implicitely includes that you do not get a worse or second class Debian
> >> installation when you upgrade it than if you installed from scratch.
> 
> > I strongly disagree: it is a bad choice to change on upgrades a default 
> > which may cause data loss.
> 
> That is false dichotomy. data-loss will occur when people use /tmp or
> /var/tmp for persistent data-storage because "This has (for a couple of
> years) worked on Debian systems" not because "This has (for a couple of
> years) worked on *this* *specific* Debian system.".

Both perspectives are valid, and that is part of why this change is
concerning to me.  Transitioning the filesystem configuration of an
existing system is inherently dangerous and can lead to data loss, as
Marco points out.  But leaving a system to diverge from the default
Debian base configuration leads to configurtion drift that may trigger
obscure bugs, untested configuration, difficult upgrades, etc.  I'm not
convinced the change is worth the risk.

noah

Bug#1072180: golang-github-lucas-clemente-quic-go: CVE-2024-22189

[Moritz Mühlenhoff]

Source: golang-github-lucas-clemente-quic-go
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for 
golang-github-lucas-clemente-quic-go.

CVE-2024-22189[0]:
| quic-go is an implementation of the QUIC protocol in Go. Prior to
| version 0.42.0, an attacker can cause its peer to run out of memory
| sending a large number of `NEW_CONNECTION_ID` frames that retire old
| connection IDs. The receiver is supposed to respond to each
| retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker
| can prevent the receiver from sending out (the vast majority of)
| these `RETIRE_CONNECTION_ID` frames by collapsing the peers
| congestion window (by selectively acknowledging received packets)
| and by manipulating the peer's RTT estimate. Version 0.42.0 contains
| a patch for the issue. No known workarounds are available.

https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a
 (v0.42.0)
https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management


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-2024-22189
https://www.cve.org/CVERecord?id=CVE-2024-22189

Please adjust the affected versions in the BTS as needed.