@Lauren Because of an earlier post by you, I assume you prepare a package
which eventually requires a sponsorship by a DD. If this were true, the upload
to https://mentors.debian.net/ would allow you to share an intermediate version
to document your current progress -- both to replicate
Hello,
I recommend the following two-fold approach.
- For one, if `nsis` refers to this entry in the package tracker
https://tracker.debian.org/pkg/nsis
prepare a new version of the package to enter branch testing (i.e. Debian
13/trixie) with as few as possible warnings e.g., by lintian and no
Hello,
I would like to add an observation tangential to your points A), explanation
to new contributors, and B) potentially advise against the use of Proton Mail
for Debian work to yield a «no, Proton Mail can be useful for some Debian
work».
In December 2022/January 2023, I found a sponsor for
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
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
Hello,
I seek a maintained Debian package which provides multiple binaries sharing one
man page in common -- do you know an example?
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
6 matches
Mail list logo
