Hi Jeremy, hi Michael,
On So 12 Dez 2021 20:24:11 CET, Michael Biebl wrote:
On 12.12.21 19:22, Jeremy Bicha wrote:
Therefore, it seems pretty easy to me for you to just bump the
upstream version in its next release from 0.9.0 to 13.11.0 (or 14.0 or
14.9.0 or whatever higher number). Blame Ubu
Package: wnpp
Severity: wishlist
Owner: Gürkan Myczko
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: groops
Version : 0+git20210906
Upstream Authors: Torsten Mayer-Guerr,
Annette Eicker,
Daniel Rieser,
Norbe
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-devel@lists.debian.org, Debian Python Team
* Package name: pytest-order
Version : 1.1.0
Upstream Author : Frank Tobia
* URL : https://github.com/pytest-dev/pytest-order
* License : MI
Hello,
TL;DR Please consider reopening the following request for packaging :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818180
Skia library is monolithic, comparable to Cairo, and has become quite
central
in 2D graphics :
it is used in Firefox, Chromium, so it ends up in Chrome,
Electro
On Mon, Dec 13, 2021 at 02:51:55PM +0100, maxzor wrote:
> TL;DR Please consider reopening the following request for packaging :
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818180
You could that yourself. On the other hand, having an RFP doesn't mean
anything so reopening it is not useful. I
Hi,
I do not known if this is the right list to address this, if it has been already
discussed and so it can be considered as noise. ;-)
Packages may provide a NEWS (or any other name, compressed or not, etc.) file
that may be part of the «main» package (like in hwloc vs. libhwloc15 for
src:hwloc
> If foo.pc in libfoo-dev references bar.pc [...]
That is the problem: If 'bar.pc' is referenced just because for static
libraries, why does it create a dependency for me as a user, who is
a) not using pkg-config at all
and/or
b) linking dynamically?
Let us assume 'bar.pc' creates a dependency
On Sun, Dec 12, 2021 at 08:11:00PM -0500, Andres Salomon wrote:
> On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote:
> > Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
> > Exactly that.
> >
> > I'd suggest anyone who's interested in seeing Chromium supported to first
> > update it in unst
On Mon, 13 Dec 2021 at 22:46:43 +0100, Alexander Traud wrote:
> Let us assume 'bar.pc' would create a dependency in Debian, then the
> question arises: Why does the Debian maintainer not transform it to
> 'Libs.private', not upstream but via a Debian patch? That would avoid
> such .pc-file*only*
Simon McVittie writes:
> If you're linking statically, you need to be able to satisfy the
> recursive dependencies of libunbound (regardless of whether you are
> using pkg-config or not), so, no, you will need nettle-dev and
> libevent-dev either way.
And, specifically, I think we should say as
Package: wnpp
Severity: wishlist
Owner: Stephen Gelman
* Package name: certinfo
Version : 1.0.6-1
Upstream Author : Peter Reisinger
* URL : https://github.com/pete911/certinfo
* License : Expat
Programming Lang: Go
Description : Print x509 certificate i
Package: wnpp
Severity: wishlist
Owner: Stephen Gelman
* Package name: golang-github-icza-gox
Version : 0.0~git20210726.cd40a3f-1
Upstream Author : András Belicza
* URL : https://github.com/icza/gox
* License : Apache-2.0
Programming Lang: Go
Description
Thanks for the pointer to https://wiki.debian.org/
ArchitectureSpecificsMemo#Architecture_baselines.
I read there that "Each Debian architecture has a baseline indicating the
oldest or least capable CPU on which the architecture can be used. The
baseline can change between Debian releases. The b
On Mon, 2021-12-13 at 19:55 +0100, Patrice Duroux wrote:
> Packages may provide a NEWS (or any other name, compressed or not, etc.) file
Since that is an upstream file, it is not standard across all Debian
package upstreams, including the name, file type and contents.
Different subsets of packag
14 matches
Mail list logo
