Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Soren Stoutner
On Wednesday, November 6, 2024 10:41:46 PM MST Aaron Rainbolt wrote: > Again, this isn't a problem limited to a derivative distribution. I > respect that your opinion of how Recommends should work differs from > mine. That doesn't change the policy though, and it doesn't change that > neglecting or

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Sune Vuorela
On 2024-11-06, Colin Watson wrote: > In some ways I think what we're missing is really a way to do the > equivalent of "extras" in Python packages > (https://peps.python.org/pep-0508/#extras): effectively groups of > additional dependencies to enable some kind of feature that you can opt > into if

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Aaron Rainbolt
On Wed, 06 Nov 2024 21:41:43 -0700 Soren Stoutner wrote: > On Wednesday, November 6, 2024 8:12:29 PM MST Aaron Rainbolt wrote: > > At this point, we have two options. We can either explicitly remove > > all of the extra packages that get installed, or we can skip > > installing recommends at all.

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Soren Stoutner
On Wednesday, November 6, 2024 8:12:29 PM MST Aaron Rainbolt wrote: > At this point, we have two options. We can either explicitly remove all > of the extra packages that get installed, or we can skip installing > recommends at all. Both of these come with their own severe > disadvantages. If we ma

Bug#1086882: ITP: gtk-meshtastic-client -- A GTK GUI for meshtastic Devices

2024-11-06 Thread Chris Talbot
Package: wnpp X-Debbugs-Cc: debian-devel@lists.debian.org Owner: Christopher Talbot Severity: wishlist * Package name: gtk-meshtastic-client Version : 0.1.0 Upstream Contact: Christopher Talbot * URL : https://www.example.org/ * License : GPL 3.0 Programming

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Aaron Rainbolt
On Wed, 06 Nov 2024 15:59:22 -0700 Soren Stoutner wrote: > On Wednesday, November 6, 2024 3:06:59 PM MST Aaron Rainbolt wrote: > > And this brings us back to the original idea of creating a > > Weak-Depends field. From my viewpoint, policy states that > > Recommends is for declaring a strong (hea

Re: Bug#1086878: python-catalogue: 2.1.0 was yanked - what version scheme should we use for 2.0.10?

2024-11-06 Thread Colin Watson
On Thu, Nov 07, 2024 at 02:42:08AM +0100, Guillem Jover wrote: > On Thu, 2024-11-07 at 01:15:08 +, Colin Watson wrote: > > https://pypi.org/project/catalogue/#history shows that 2.1.0 was yanked > > from PyPI, but it's what we currently have in Debian. Some of the more > > recent releases (whi

Re: Rebuilds to enable PAC and BTI support on arm64

2024-11-06 Thread Guillem Jover
Hi! On Wed, 2024-11-06 at 17:28:38 +0500, Andrey Rakhmatullin wrote: > On Wed, Nov 06, 2024 at 10:43:07AM +0100, Emanuele Rocca wrote: > > As a final thought, given that new toolchain versions bring multiple > > improvements over the years it's perhaps worth thinking about rebuilding > > the archi

Re: Bug#1086878: python-catalogue: 2.1.0 was yanked - what version scheme should we use for 2.0.10?

2024-11-06 Thread Guillem Jover
Hi! On Thu, 2024-11-07 at 01:15:08 +, Colin Watson wrote: > Source: python-catalogue > Version: 2.1.0-6 > Severity: normal > X-Debbugs-Cc: Andreas Tille , debian-devel@lists.debian.org > https://pypi.org/project/catalogue/#history shows that 2.1.0 was yanked > from PyPI, but it's what we curr

Bug#1086878: python-catalogue: 2.1.0 was yanked - what version scheme should we use for 2.0.10?

2024-11-06 Thread Colin Watson
Source: python-catalogue Version: 2.1.0-6 Severity: normal X-Debbugs-Cc: Andreas Tille , debian-devel@lists.debian.org https://pypi.org/project/catalogue/#history shows that 2.1.0 was yanked from PyPI, but it's what we currently have in Debian. Some of the more recent releases (which I think are

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Charles Plessy
Hello Aaron and everybody, the R package ecosystem uses control fields inspired by ours. But there the Suggests field is used in a stronger way: packages listed in Suggests usually provide functionality that is directly leveraged by packaged code, and the usual pattern is that if the suggested pa

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Aaron Rainbolt
On Wed, 6 Nov 2024 22:55:43 + Colin Watson wrote: > On Wed, Nov 06, 2024 at 04:06:59PM -0600, Aaron Rainbolt wrote: > > (Side note, I wonder if there's a way to implement Weak-Depends that > > *doesn't* require modifying all of the tons of packages Johannes > > mentioned. Maybe some way of an

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Soren Stoutner
On Wednesday, November 6, 2024 3:06:59 PM MST Aaron Rainbolt wrote: > And this brings us back to the original idea of creating a Weak-Depends > field. From my viewpoint, policy states that Recommends is for > declaring a strong (heavy emphasis on "strong" here), but not absolute, > dependency. Aft

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Colin Watson
On Wed, Nov 06, 2024 at 04:06:59PM -0600, Aaron Rainbolt wrote: > (Side note, I wonder if there's a way to implement Weak-Depends that > *doesn't* require modifying all of the tons of packages Johannes > mentioned. Maybe some way of annotating packages in Recommends as > "important" would permit a

Bug#1086876: ITP: rust-hstr -- string type optimized for hash operations

2024-11-06 Thread Jonas Smedegaard
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-hstr Version : 0.2.12 Upstream Contact: 강동윤 * URL : https://github.com/dudykr/ddbase * License

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Aaron Rainbolt
On Wed, 06 Nov 2024 14:21:30 -0700 Soren Stoutner wrote: > On Wednesday, November 6, 2024 12:08:07 PM MST Aaron Rainbolt wrote: > >For instance, gwenview currently > > recommends kamera. gwenview is an image viewer, kamera is a tool for > > working with digital cameras. Now it is true that kamera

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Soren Stoutner
On Wednesday, November 6, 2024 12:08:07 PM MST Aaron Rainbolt wrote: >For instance, gwenview currently > recommends kamera. gwenview is an image viewer, kamera is a tool for > working with digital cameras. Now it is true that kamera enhances > gwenview's functionality by allowing it to see pictures

Bug#1086871: ITP: rust-auto-impl -- auto-traits for pointers and closures

2024-11-06 Thread Jonas Smedegaard
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-auto-impl Version : 1.2.0 Upstream Contact: https://github.com/auto-impl-rs/auto_impl/issues * URL

Re: diffoscope dependency granularity [was RFC: "Recommended bloat", and how to possibly fix it]

2024-11-06 Thread Richard Lewis
Fay Stegerman writes: > [Added diffosc...@lists.reproducible-builds.org to Cc] > > * Fay Stegerman [2024-11-06 17:43]: >> * Johannes Schauer Marin Rodrigues [2024-11-06 02:28]: >> [...] >> > Have one package diffoscope and one package diffoscope-full and you could >> > even >> > have a package

Re: RFC: "Recommended bloat", and how to possibly fix ito

2024-11-06 Thread Bill Allombert
Le Tue, Nov 05, 2024 at 05:35:59PM -0600, Aaron Rainbolt a écrit : > Hello, and thanks for your time. > > I've been a Debian user and contributor for a while, and have noticed a > rather frustrating issue that I'm interested in potentially > contributing code to fix. The issue is what I call "Reco

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Aaron Rainbolt
On Wed, 6 Nov 2024 18:03:07 + Holger Levsen wrote: > On Wed, Nov 06, 2024 at 06:03:45PM +0100, IOhannes m zmölnig wrote: > > Afaict, the problem is that we have 3 options to pick from, and > > it's hard for people to decide which is the "right one". I do not > > see how adding a 4th option wi

Bug#1086863: ITP: rust-swc-core -- speedy web compiler - Rust source code

2024-11-06 Thread Jonas Smedegaard
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: rust-swc-core Version : 5.0.2 Upstream Contact: 강동윤 * URL : https://github.com/swc-project/swc * Licen

Re: Rebuilds to enable PAC and BTI support on arm64

2024-11-06 Thread Andrey Rakhmatullin
On Wed, Nov 06, 2024 at 10:43:07AM +0100, Emanuele Rocca wrote: > As a final thought, given that new toolchain versions bring multiple > improvements over the years it's perhaps worth thinking about rebuilding > the archive on some sort of regular basis to make sure we get the > benefits? "Let's a

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Holger Levsen
On Wed, Nov 06, 2024 at 06:03:45PM +0100, IOhannes m zmölnig wrote: > Afaict, the problem is that we have 3 options to pick from, and it's hard for > people to decide which is the "right one". > I do not see how adding a 4th option will make this decision any easier (esp. > since that new option

diffoscope dependency granularity [was RFC: "Recommended bloat", and how to possibly fix it]

2024-11-06 Thread Fay Stegerman
[Added diffosc...@lists.reproducible-builds.org to Cc] * Fay Stegerman [2024-11-06 17:43]: > * Johannes Schauer Marin Rodrigues [2024-11-06 02:28]: > [...] > > Have one package diffoscope and one package diffoscope-full and you could > > even > > have a package diffoscope-minimal and there you

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread IOhannes m zmölnig
Am 6. November 2024 00:35:59 MEZ schrieb Aaron Rainbolt : > > >* Add a "Weak-Depends" field to the list of binary dependency control > fields in the Debian Policy Manual section 7.2, with a definition > very similar to the existing definition for "Recommends". >* Change the definition of the "Rec

Bug#1086859: ITP: swaysome -- swaysome allows better multi-output management for sway

2024-11-06 Thread Florent 'Skia' Jacquet
Package: wnpp Severity: wishlist Owner: Florent 'Skia' Jacquet X-Debbugs-Cc: debian-devel@lists.debian.org, s...@hya.sk * Package name: swaysome Version : 2.1.2 Upstream Contact: Florent 'Skia' Jacquet * URL : https://gitlab.com/hyask/swaysome * License : MIT

Re: RFC: "Recommended bloat", and how to possibly fix it

2024-11-06 Thread Fay Stegerman
* Johannes Schauer Marin Rodrigues [2024-11-06 02:28]: [...] > Have one package diffoscope and one package diffoscope-full and you could even > have a package diffoscope-minimal and there you have user-selectable > granularity. We already have two diffoscope packages for exactly this reason (I wo

Re: Rebuilds to enable PAC and BTI support on arm64

2024-11-06 Thread Andreas Tille
Am Wed, Nov 06, 2024 at 01:16:57PM + schrieb Holger Levsen: > On Wed, Nov 06, 2024 at 05:28:38PM +0500, Andrey Rakhmatullin wrote: > > "Let's at least force rebuilds all packages not rebuilt since stable > > before every freeze starts" is a popular opinion. > > true. and "let's not do that" is

Re: Rebuilds to enable PAC and BTI support on arm64

2024-11-06 Thread Andrey Rakhmatullin
On Wed, Nov 06, 2024 at 01:16:57PM +, Holger Levsen wrote: > On Wed, Nov 06, 2024 at 05:28:38PM +0500, Andrey Rakhmatullin wrote: > > "Let's at least force rebuilds all packages not rebuilt since stable > > before every freeze starts" is a popular opinion. > > true. and "let's not do that" is

Re: Rebuilds to enable PAC and BTI support on arm64

2024-11-06 Thread Holger Levsen
On Wed, Nov 06, 2024 at 05:28:38PM +0500, Andrey Rakhmatullin wrote: > "Let's at least force rebuilds all packages not rebuilt since stable > before every freeze starts" is a popular opinion. true. and "let's not do that" is even more popular, else why haven't we done this in three decades? --

Re: Rebuilds to enable PAC and BTI support on arm64

2024-11-06 Thread Emanuele Rocca
On 2024-10-28 10:55, Sebastian Ramacher wrote: > since dpkg 1.22.0 the additional hardening flags to enable Pointer > Authentication (PAC) and Branch Target Identification (BTI) > on arm64 are enabled by default. Some more background and an update on this. Both PAC and BTI are enabled by adding -