Hello,
On Sun 16 Feb 2025 at 06:18am -06, rhys wrote:
> The potential for additional function is not relevant.
>
> If the upstream intends to distribute it with a tarball, that's the "golden"
> package that downstream should base code upon.
The Debian project officially disagrees with you.
The
Package: wnpp
Severity: wishlist
Owner: Francesco Ballarin
X-Debbugs-Cc: debian-devel@lists.debian.org, francesco.balla...@unicatt.it
* Package name: python-nbstripout
Version : 0.8.1
Upstream Contact: Florian Rathgeber
* URL : https://github.com/kynan/nbstripout
* Li
Hello fellow Debian people,
[Please keep me in CC as I'm not subscribed to -devel]
As the primary maintainer of a header-only C/C++ package, I'm really happy to
see the progress in formalizing the use of 'Static-Built-Using' [0] to aid in
determining when packages that use header-only librarie
On Sun, Feb 16, 2025 at 10:39:59AM +0800, Sean Whitton wrote:
> I think that basing our work on upstream Git makes our source packages
> more useful, and more accurately reflects our commitment to providing
> the preferred form of modification for everything in our archive.
>
> If our work is base
Am Sun, Feb 16, 2025 at 05:53:37PM +0100 schrieb Chris Hofstaedtler:
> On Sun, Feb 16, 2025 at 05:44:34PM +0100, наб wrote:
> > On Sun, Feb 16, 2025 at 05:29:26PM +0100, Chris Hofstaedtler wrote:
> > > On Sun, Feb 16, 2025 at 05:18:39PM +0100, наб wrote:
> > > > Quoting the relevant:
> > > > > It i
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: libggml
* Version : 0.0+git
* Upstream Contact: The ggml authors
* URL : https://github.com/ggml-org/ggml
* License : M
Package: wnpp
Severity: wishlist
Owner: Martina Ferrari
* Package name: golang-github-code-hex-go-generics-cache
Version : 1.5.1-1
Upstream Author : Kei Kamikawa
* URL : https://github.com/Code-Hex/go-generics-cache
* License : Expat
Programming Lang: Go
De
Package: wnpp
Severity: wishlist
Owner: Nicolas Peugnet
* Package name: golang-github-r3labs-sse
Version : 2.10.0-1
Upstream Author : R3 Labs
* URL : https://github.com/r3labs/sse
* License : MPL-2.0
Programming Lang: Go
Description : Server Sent Events
On Sun, Feb 16, 2025 at 05:44:34PM +0100, наб wrote:
> On Sun, Feb 16, 2025 at 05:29:26PM +0100, Chris Hofstaedtler wrote:
> > On Sun, Feb 16, 2025 at 05:18:39PM +0100, наб wrote:
> > > Quoting the relevant:
> > > > It is recommended to choose between one of the two following schemes:
> > > > 2. Pu
Hi,
Le 2025-02-16 17:00, Julien Puydt a écrit :
I have always considered the true way to know if you have the source of
a package is: imagine you're stuck somewhere with a Debian mirror and
no external link. Could you take over the development of the package at
hand?
Written like that it look
Julien Puydt writes:
> If you use autotools, you start with configure.ac and .in files. If
> upstream prepared the tree (as they generally do), you also get a
> libtool/configure, etc. From this, you can run ./configure && make &&
> make install ; that will do substitutions in the .in files. And
Le dimanche 16 février 2025 à 06:18 -0600, rhys a écrit :
>
> If the upstream intends to distribute it with a tarball, that's the
> "golden" package that downstream should base code upon.
>
> Going around that decision means subjecting all of Debian to code
> pulled from their repo outside of the
Le dimanche 16 février 2025 à 14:51 +, Colin Watson a écrit :
>
> This is a false dichotomy, though. It's perfectly possible to use
> both
> in conjunction with each other, by importing a tarball on top of an
> upstream git tag so that the differences between them are represented
> by
> a git
Hello,
Le lundi 12 août 2019, 00 h 04 min 37 s UTC+1 Nicholas D Steeves a écrit :
> LXD is going to eventually be packaged for Debian, so bin:fuidshift
> from src:lxd makes sense to me.
I see that fuidshift is now part of the lxd-tools packages, so I think that
this RFP can be closed.
Regards,
Package: wnpp
Severity: wishlist
Owner: Simon Josefsson
* Package name: golang-github-landlock-lsm-go-landlock
Version : 0.0~git20241014.479ddab-1
Upstream Author : Landlock
* URL : https://github.com/landlock-lsm/go-landlock
* License : Expat
Programming Lan
Package: wnpp
Severity: wishlist
Owner: Maximilian Engelhardt
X-Debbugs-Cc: debian-devel@lists.debian.org, m...@daemonizer.de
* Package name: python-pyramid-retry
Version : 2.1.1
Upstream Contact: Pylons Project
* URL : https://github.com/Pylons/pyramid_retry
* Licens
Package: wnpp
Severity: wishlist
Owner: Maximilian Engelhardt
X-Debbugs-Cc: debian-devel@lists.debian.org, m...@daemonizer.de
* Package name: python-pylons-sphinx-themes
Version : 1.0.13
Upstream Contact: Pylons Project
* URL : https://github.com/Pylons/pylons-sphinx-
On Feb 14, Colin Watson wrote:
> But it doesn't. Santiago's using the data from the security tracker to
> determine whether CVEs are open.
And in the case of one of my own packages these CVEs have not yet been
fixed upstream, not even in an unreleased branch.
--
ciao,
Marco
signature.asc
De
Le dimanche 16 février 2025 à 19:50 +0100, Julien Plissonneau Duquène a
écrit :
> Hi,
>
> Le 2025-02-16 17:00, Julien Puydt a écrit :
>
> > I have always considered the true way to know if you have the
> > source of
> > a package is: imagine you're stuck somewhere with a Debian mirror
> > and
> >
Package: wnpp
Severity: wishlist
Owner: Alexander Fomin
X-Debbugs-Cc: debian-devel@lists.debian.org, fomin_a...@yahoo.com
* Package name: forwords
Version : 1.0.2
Upstream Contact: Alexander Fomin
* URL : https://salsa.debian.org/AlexFomin/forwords
* License :
Package: wnpp
Severity: wishlist
Owner: Josenilson Ferreira da Silva
X-Debbugs-Cc: debian-devel@lists.debian.org, nilsonfsi...@hotmail.com
* Package name: python-briefcase
Version : 0.3.22
Upstream Contact: Russell Keith-Magee
* URL : https://github.com/beeware/briefc
21 matches
Mail list logo
