Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: mpv-mpris
Version : 0.6
Upstream Author : Ho-Yon Mak
* URL : https://github.com/hoyon/mpv-mpris
* License : MIT
Programming Lang: C
Description
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: rime-stroke
Version : 0.0~git20191221.ea8576d-1
Upstream Author : Gong Chen
* URL : https://github.com/rime/rime-stroke
* License : LGPL-3.0
Programming Lang: N/A
D
On Fri, 2021-12-17 at 11:28 +0100, Moritz Mühlenhoff wrote:
> Could anyone who's using Chromium on Debian please create a page on
> wiki.debian.org which lists the alternative options to use a current
> Chromium (Flatpak, ungoogled Chromium from elsewhere, snap, whatever
> else there is)?
The exi
The Python world has developed new standards for building and
distributing modules. The previous approach of running setup.py has been
replaced by a build API described in PEP517 (and some associated
documents).
An increasing number of projects now use this approach to building -
there is no setup
Package: wnpp
Severity: wishlist
Owner: Anthony Fok
* Package name: golang-github-charmbracelet-bubbletea
Version : 0.19.1-1
Upstream Author : Charmbracelet, Inc.
* URL : https://github.com/charmbracelet/bubbletea
* License : Expat
Programming Lang: Go
Desc
Hi Thomas,
On 17-12-2021 13:38, Thomas Goirand wrote:
It's been a long time I wanted to write this kind of message, but I'm
unsure against which package I should report the bug.
release.debian.org
Would it be possible that instead, I get a single message on each AUTORM
run, telling me about
Simon McVittie writes:
> For some libraries, the only maintainer-supported way to consume the
> library is via pkg-config. If that's the case, then a dependency on
> pkg-config can be appropriate - although we don't add a dependency on
> cc or binutils, which is equally necessary.
Well, cc and b
Hi,
It's been a long time I wanted to write this kind of message, but I'm
unsure against which package I should report the bug.
My issue is that I maintain a lot of packages that all depend on the
same (more or less) packages. Whenever a high profile (build-)dependency
enter the AUTORM phrase, my
On Thu, 09 Dec 2021 at 15:24:27 +0100, Alexander Traud wrote:
> if the header included another header,
> and that header included further headers but was not in the root but in
> a subfolder, an -I flag *might* be required. For example, the package
> 'libopusfile-dev' has its header file in '/us
On Fri, 17 Dec 2021 at 10:05:39 +0100, Alexander Traud wrote:
> I do not understand why:
> a) pkg-config itself is *not* a dependency as well
Sometimes it is appropriate for it to be, and sometimes it is not.
For some libraries, the only maintainer-supported way to consume the
library is via pkg-
The problem of "Requires.private", for C/C++ libraries, it (might)
contain two different things: Libraries used for static linking *and*
Cflags to preprocess the header files.
If the position of Debian is that each reference in "Requires.private"
translates into a required dependency in Debian/
11 matches
Mail list logo
