New Essential package procps-base

2023-11-13 Thread Craig Small
Hello, For quite some time (since 2006!) there has been a discussion at[1] about changing from the sysvinit-utils version of pidof to the procps one. A quick scan of the various distributions shows that only Debian and Ubuntu (and I assume most other downstreams) use the sysvinit-utils version.

Re: Linking coreutils against OpenSSL

2023-11-13 Thread Pierre-Elliott Bécue
Luca Boccassi wrote on 10/11/2023 at 16:08:30+0100: > On Fri, 10 Nov 2023 at 14:22, Pierre-Elliott Bécue wrote: >> >> Luca Boccassi wrote on 10/11/2023 at 15:00:24+0100: >> >> > On Fri, 10 Nov 2023 at 13:45, Bjørn Mork wrote: >> >> >> >> Luca Boccassi writes: >> >> >> >> > If we want to start

Re: reference Debian package of multiple binaries sharing one man page

2023-11-13 Thread Norwid Behrnd
On Mon, 13 Nov 2023 09:41:12 -0800 Russ Allbery wrote: > > Oh, indeed, you're right and I misread that. So I think you can just use > symlinks, period, and not worry about .so (although you have to handle > nodoc builds correctly). > Well, one file with a list like ```debian/markdownlint.man

Bug#1055897: ITP: speakersafetyd -- speaker protection daemon for embedded Linux systems

2023-11-13 Thread Andreas Henriksson
Package: wnpp Severity: wishlist Owner: Andreas Henriksson X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: speakersafetyd Version : 0.1.4 Upstream Contact: https://github.com/AsahiLinux/speakersafetyd/issues * URL : https://github.com/AsahiLinux/speakersafe

Re: Linking coreutils against OpenSSL

2023-11-13 Thread Florian Weimer
* Theodore Ts'o: > If you can get upstream a patch so that coreutils could try to dlopen > OpenSSL and use it if it is available, but skip it if it is not, that > might be one way to avoid OpenSSL going into essential. The challenge > is that OpenSSL is not known for its ability to maintain a sta

Re: reference Debian package of multiple binaries sharing one man page

2023-11-13 Thread Russ Allbery
Andrey Rakhmatullin writes: > On Fri, Nov 10, 2023 at 11:44:06AM -0800, Russ Allbery wrote: >> The good news is that if you're using debhelper, you don't have to care >> about how man handles these indirections and can just use a symlink. >> Install the man page into usr/share/man/man1 under what

Re: reference Debian package of multiple binaries sharing one man page

2023-11-13 Thread Andrey Rakhmatullin
On Fri, Nov 10, 2023 at 11:44:06AM -0800, Russ Allbery wrote: > The good news is that if you're using debhelper, you don't have to care > about how man handles these indirections and can just use a symlink. > Install the man page into usr/share/man/man1 under whatever name is > canonical (possibly

Re: reference Debian package of multiple binaries sharing one man page

2023-11-13 Thread Russ Allbery
Norwid Behrnd writes: > Recently, I started to upgrade the Debian package about > `markdownlint`,[1] a syntax checker. The initially packaged version > 0.12.0 provided a binary of name `ruby-mdl` which now becomes a > transition dummy package in favour of the functionally updated > `markdownlint

Re: reference Debian package of multiple binaries sharing one man page

2023-11-13 Thread Norwid Behrnd
Hello, On Sat, 11 Nov 2023 14:08:49 +0100 Alexander Sulfrian wrote: > > You will need a file mdl.1 with the following content: > > .so man1/markdownlint.1 > > and markdownlint.1 should be the normal manpage without a .so line. > This logic provides exactly the relay I sought out. Thanks a