Marc Haber writes:
> How would I quote backslashes in a manual page correctly?
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966803#14:
if you want to *emit* a backslash, use \e.
> Currently I have the source:
>
> with '"' around each argument, each '"'
> in the string converted to '\\"
Marc Haber writes:
> I have a package which source tarball containst two examples
> directories:
>
> src/examples
> src/c++/examples
>
> Since both directories contain a Makefile, I would like to install
> src/examples to /usr/share/doc/package/examples and src/c++/examples to
> /usr/share/doc/pa
Seunghun Han writes:
>>> swtpm - Libtpms-based TPM emulator
>>> swtpm-dev - Include files for the TPM emulator's CUSE interface
>>> swtpm-libs - Common libraries for TPM emulators
>>
>> Why do you deviate from the usual libswtpm-dev/libswtpm0 package names?
>> Including the SO version in th
Seunghun Han writes:
> * Package name: swtpm
>Version : 0.7.0-rc2-1
Hi,
The upstream version number should be 0.7.0~rc2 with a tilde instead of
a hyphen to ensure proper ordering (as Lintian warns about). To do such
transformations automatically, put something like this in the
Ryan McClue writes:
> override_dh_auto_install:
> cp program /usr/local/bin
Unrelated to your actual question, but this won't work well. You need
to install into debian/PACKAGENAME as if it was the filesystem root,
that is: cp program debian/PACKAGENAME/usr/bin (after ensuring the
directory
John Scott writes:
> binutils/libiberty/configure: line 2911: syntax error near unexpected token
> `PLUGIN_OPTION'
> binutils/libiberty/configure: line 2911: `GCC_PLUGIN_OPTION(PLUGIN_OPTION)'
>
> This seems bizarre. Why would autoreconf produce a script with a syntax
> error, or is dash not rob
Marc Haber writes:
> I would like to deliver a YAML config file with the package and have the
> old file still supported if an old file is still there (optimally
> printing a warning when starting up with old format). I would prefer to
> avoid a wrapper script.
>
> My idea would be to have two di
Lajos Veres writes:
> I am wondering to move the debian folder to a dedicated github
> repository to have it version tracked. Or is there any more Debian
> friendly place for these debian packaging repositories?
Szia Lajos!
I prefer Debian packaging branches to separate packaging repositories.
Hilmar Preuße writes:
> the installation/compilation instructions for some proftp modules [1] say:
> "To install mod_proxy, go to the third-party module area in the proftpd
> source code and unpack the mod_proxy source tarball: [...]
> This works fine. How do I do that for a Debian package?
Afte
Andre Noll writes:
> I also had to override dh_autoreconf for reasons explained in the
> commit message.
It isn't a packaging issue, I just wonder: why do you wrap configure?
The usual approach to making it available is distributing it (and not
requiring Autoconf to build the software from the d
deb...@lewenberg.com writes:
> Looking at DEP-14 I might have these Git branches:
>
> master
> debian/master
> debian/stretch
> upstream/latest
>
> I understand that the Debian packaging files in debian/ will appear in
> the "debian/*" branch, but my general question is: what is the
> work
Hi,
Is the g++ dependency of the main game binary intentional?
I built the game for stretch, it went OK (after reducing the debhelper
compatibility level to 11, but that isn't a problem). The game starts,
but I'm unable to select a map: the presented list is empty, though
strace shows it finds t
Hi,
Could somebody please explain me the meaning of the "Checking
build-dependency (indep) on amd64" migration excuse as seen on
https://qa.debian.org/excuses.php?package=pacemaker?
I think I understand the rest, although I don't know whether the
autopkgtest regression blocks migration indefinite
13 matches
Mail list logo
