Hello,
I would like to reach out to the decision-maker in the IT environment within
your company.
We are a well-established digital agency in the European market. Our solutions
eliminate the need to build and maintain in-house IT and programming
departments, hire interface designers, or employ
Hi,
I can work on packaging this if you're still interested, I'd need a sponsor.
I've already done some preliminary work on this, in particular I renamed
the bin to "rust-toml2json" but maybe you've got a better idea?
Best,
Facundo
Quoting Facundo Gaich (2024-02-22 17:12:22)
> I can work on packaging this if you're still interested, I'd need a sponsor.
>
> I've already done some preliminary work on this, in particular I renamed
> the bin to "rust-toml2json" but maybe you've got a better idea?
If the command-line tool does s
Package: wnpp
Severity: wishlist
Owner: Agathe Porte
X-Debbugs-Cc: debian-devel@lists.debian.org, gag...@debian.org
* Package name: fonts-sn-pro
Version : 1.0.0
Upstream Contact: Tobias https://tobias.so/
* URL : https://supernotes.app/open-source/sn-pro/
* License
Our current way of dealing with package relationship substvars such as
${misc:Depends} has been annoying me for a while. As it is, we are stuck
in this way setup where the "Depends" field in debian/control is de
facto mandatory. It is an RC bug (waiting to happen) if you omit
${misc:Depends} or
On Thu, 22 Feb 2024 at 19:32:21 +0100, Niels Thykier wrote:
> I think our package helper tooling should just automatically aggregate all
> provided substvars of the format ${*:Depends} and append it the Depends
> field. Rinse and repeat for other relationship fields.
I recently added ${gir:Provide
在 2024-02-22星期四的 19:32 +0100，Niels Thykier写道：
> I think our package helper tooling should just automatically aggregate
> all provided substvars of the format ${*:Depends} and append it the
> Depends field. Rinse and repeat for other relationship fields.
>
> The list of fields where this is appli
Simon McVittie:
On Thu, 22 Feb 2024 at 19:32:21 +0100, Niels Thykier wrote:
I think our package helper tooling should just automatically aggregate all
provided substvars of the format ${*:Depends} and append it the Depends
field. Rinse and repeat for other relationship fields.
I recently added
Boyuan Yang:
[...]
Can we also consider ${*:Built-Using} as typically seen in
${sphinxdoc:Built-Using}?
This is another field that people keep forget adding. While missing
this field is not severely harmful, having it automatically handled
would be beneficial.
Thanks,
Boyuan Yang
Personally,
Quoting Boyuan Yang (2024-02-22 20:25:32)
> 在 2024-02-22星期四的 19:32 +0100，Niels Thykier写道：
> > I think our package helper tooling should just automatically aggregate
> > all provided substvars of the format ${*:Depends} and append it the
> > Depends field. Rinse and repeat for other relationship f
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: taskflow
Version : 3.6.0+git20240218.9616467
Upstream Contact: Dr. Tsung-Wei Huang
* URL : https://taskflow.github.io/
* License : Expat
Program
On Thu, 22 Feb 2024 at 20:43:21 +0100, Niels Thykier wrote:
> Simon McVittie:
> > On Thu, 22 Feb 2024 at 19:32:21 +0100, Niels Thykier wrote:
> > > We could also make unused substvars a hard failure (FTBFS).
> >
> > I'd prefer not this
>
> Reminder: My proposal only covers ${foo:Depends} and simi
Am 22. Februar 2024 20:25:32 MEZ schrieb Boyuan Yang :
>在 2024-02-22星期四的 19:32 +0100，Niels Thykier写道：
>> I think our package helper tooling should just automatically aggregate
>> all provided substvars of the format ${*:Depends} and append it the
>> Depends field. Rinse and repeat for other relat
On Thu, Feb 22, 2024 at 08:52:36PM +0100, IOhannes m zmölnig wrote:
> Am 22. Februar 2024 20:25:32 MEZ schrieb Boyuan Yang :
> >在 2024-02-22星期四的 19:32 +0100，Niels Thykier写道：
> >> I am omitting Breaks, Conflicts, and Replaces because I am not aware of
> >> any users of these at the moment. I am ope
On 22.02.24 20:43, Niels Thykier wrote:
Simon McVittie:
We could also make unused substvars a hard failure (FTBFS).
I'd prefer not this, because this would be really painful if you're
using substvars for something other than a simple list of dependencies,
like gobject-introspection does:
[...
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: rust-rustls-pki-types
Version : 1.3.0
Upstream Contact: Dirkjan Ochtman
* URL : https://github.com/rus
> "Niels" == Niels Thykier writes:
Niels> # The proposal
Niels> I think our package helper tooling should just automatically
Niels> aggregate all provided substvars of the format ${*:Depends}
Niels> and append it the Depends field. Rinse and repeat for other
Niels> relati
On Thu, 22 Feb 2024 19:32:21 +0100, Niels Thykier wrote:
> I think our package helper tooling should just automatically aggregate all
> provided substvars of the format ${*:Depends} and append it the Depends
> field. Rinse and repeat for other relationship fields.
I very much like this proposal.
On 2024-02-22 12:32, Niels Thykier wrote:
I am omitting Breaks, Conflicts, and Replaces because I am not aware of
any users of these at the moment. I am open to adding them, if there is
a strong use-case.
I think you should include them (and Enhances as Sam Hartman mentioned)
for consistency.
Package: wnpp
Severity: wishlist
Owner: Arthur Diniz
* Package name: golang-github-liggitt-tabwriter
Version : 0.0~git20181228.89fcab3-1
Upstream Author : Jordan Liggitt
* URL : https://github.com/liggitt/tabwriter
* License : BSD-3-clause
Programming Lang: G
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: rust-self-encryption
Version : 0.29.1
Upstream Contact: MaidSafe.net limited
* URL : https://github.com
Hi!
On Thu, 2024-02-22 at 19:32:21 +0100, Niels Thykier wrote:
> Our current way of dealing with package relationship substvars such as
> ${misc:Depends} has been annoying me for a while. As it is, we are stuck in
> this way setup where the "Depends" field in debian/control is de facto
> mandatory
Hi!
On Thu, 2024-02-22 at 23:14:13 +0100, gregor herrmann wrote:
> On Thu, 22 Feb 2024 19:32:21 +0100, Niels Thykier wrote:
> > If you forget to add a susbtvars that you should added, it is a latent RC
> > bug with only a warning from dpkg-gencontrol that you might miss if you grab
> > a coffee wh
Simon McVittie:
On Thu, 22 Feb 2024 at 20:43:21 +0100, Niels Thykier wrote:
Simon McVittie:
On Thu, 22 Feb 2024 at 19:32:21 +0100, Niels Thykier wrote:
We could also make unused substvars a hard failure (FTBFS).
I'd prefer not this
Reminder: My proposal only covers ${foo:Depends} and simil
IOhannes m zmölnig:
[...]
While I like the idea in general, I wonder how I could override these automatic
additions.
I think there are some packages that even demote `${shlibs:Depends}` to
Recommends.
mfh.her.fsr
IOhannes
I had the same conceptual concern when I originally thought about t
Guillem Jover:
Hi!
On Thu, 2024-02-22 at 19:32:21 +0100, Niels Thykier wrote:
[...]
Right, this is annoying. This was actually brought up some time
ago (2010) in debian-devel as part of #597340. There was not much
reaction at the time (one good, a couple bad).
I reinvented a decade old ide
26 matches
Mail list logo
