d-i alpha release?

2022-08-28 Thread Holger Wansing
Hi, we have less than 5 months until the planned beginning of bookworm's freeze. What about a d-i alpha/beta release? (there was no d-i release since the release of bullseye) Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076

Re: Current NEW review process saps developer motivation

2022-08-28 Thread Simon McVittie
On Sat, 27 Aug 2022 at 09:01:01 +0800, Paul Wise wrote: > > I don't think building from the least-derived form is always the > > right thing to do. > > Personally, I believe that instances of that represent bugs in how the > upstream source trees and build processes are organised. While I'm flatt

Re: Comments on proposing NEW queue improvement (Re: Current NEW review process saps developer motivation

2022-08-28 Thread Nilesh Patra
On Sat, Aug 27, 2022 at 09:50:41AM +0200, Gard Spreemann wrote: > > Strong motivations such as "I use this package, seriously" are not > > likely to wear out very easily through time. Packages maintained > > with a strong motivation are better cared among all packages in our > > archive. > > I hum

Bug#1018291: ITP: libcrypt-argon2-perl -- Perl interface to the Argon2 key derivation functions

2022-08-28 Thread Joenio Marques da Costa
Package: wnpp Severity: wishlist Owner: Joenio Marques da Costa X-Debbugs-Cc: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libcrypt-argon2-perl Version : 0.012 Upstream Author : Leon Timmermans * URL : https://metacpan.org/release/Crypt-

transition announcement: gsfonts + gsfonts-x11 -> fonts-urw-base35

2022-08-28 Thread Fabian Greffrath
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear fellow DDs, I'd like to announce a transition that I am going to kick off in about one week from today: I'd like to replace the gsfonts package with fonts-urw-base35 and, while at it, integrate the contents of gsfonts- x11 into the new package.

Bug#1018294: ITP: openfpgaloader -- Universal utility for programming FPGAs

2022-08-28 Thread Steffen Moeller
Package: wnpp Severity: wishlist Owner: Steffen Moeller X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: openfpgaloader Version : 0.9 * URL : https://github.com/trabucayre/openFPGALoader * License : Apache-2.0 Programming Lang: C/C++ Description

Re: Current NEW review process saps developer motivation

2022-08-28 Thread Russ Allbery
Paul Wise writes: > On Fri, 2022-08-26 at 11:58 +0100, Simon McVittie wrote: >> For instance, take rust-glib-sys, a package of Rust bindings for the >> GLib library, which is one of the libraries whose handling prompted >> this thread. > I feel like the right way to organise this upstream is for

Re: Idea: autopkgtest on big-endian for 'Architecture: all' packages to catch endian bugs

2022-08-28 Thread Thorsten Glaser
Didier 'OdyX' Raboud dixit: >If these tests are run at build-time, errors halt the build and that provides That may not be enough, though; there are cases where the build architecture determines artefact endianness (e.g. with PCF bitmap fonts), and that may even be enough (X servers can load PCFs

Re: d-i alpha release?

2022-08-28 Thread Cyril Brulebois
Hi Holger, Holger Wansing (2022-08-28): > we have less than 5 months until the planned beginning of bookworm's freeze. > > What about a d-i alpha/beta release? > (there was no d-i release since the release of bullseye) Yes, I could have sent a mail to -boot@ as not everyone is on IRC: we had a

Bug#1018300: ITP: gcloud-aio -- (Asyncio OR Threadsafe) Google Cloud Client Library for Python

2022-08-28 Thread Jelmer Vernooij
Package: wnpp Severity: wishlist Owner: Jelmer Vernooij X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: gcloud-aio Version : 7.0.1 Upstream Author : Vi Engineering * URL : https://github.com/talkiq/gcloud-aio/ * License : MIT Programming Lang: Pyt

Re: General resolution: non-free firmware

2022-08-28 Thread Thorsten Glaser
Thorsten Glaser dixit: >PS: Please do Cc me on replies. Phil Morrell dixit: >> Is there support for something like A but not enabled by default? >> That is, you have to actively select a nōn-default option > >I don't believe so, because that doesn't solve the problem at hand. How >exactly do yo

Re: Comments on proposing NEW queue improvement (Re: Current NEW review process saps developer motivation

2022-08-28 Thread Sean Whitton
Hello, On Sun 28 Aug 2022 at 07:45AM +02, Andreas Tille wrote: > > Am Sat, Aug 27, 2022 at 09:53:40AM -0400 schrieb M. Zhou: >> In my fuzzy memory, the last discussion on NEW queue improvement >> involves the disadvantages by allowing SOVERSION bump to directly >> pass the NEW queue. I'm not goin

Re: Comments on proposing NEW queue improvement (Re: Current NEW review process saps developer motivation

2022-08-28 Thread Scott Kitterman
On August 28, 2022 8:58:24 PM UTC, Sean Whitton wrote: >Hello, > >On Sun 28 Aug 2022 at 07:45AM +02, Andreas Tille wrote: > >> >> Am Sat, Aug 27, 2022 at 09:53:40AM -0400 schrieb M. Zhou: >>> In my fuzzy memory, the last discussion on NEW queue improvement >>> involves the disadvantages by all

Bug#1018681: ITP: spnavcfg -- GUI to configure 3Dconnexion devices

2022-08-28 Thread Steffen Moeller
Package: wnpp Severity: wishlist Owner: Steffen Moeller X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: spnavcfg Version : 1.0 * URL : https://github.com/FreeSpacenav/spnavcfg * License : GPL Description : GUI to configure 3Dconnexion devices T

Re: Need a buildd build after trip through NEW -- best practice?

2022-08-28 Thread Steven Robbins
On Tuesday, August 23, 2022 6:56:32 P.M. CDT Nilesh Patra wrote: > On 24 August 2022 3:29:10 am IST, Steven Robbins wrote: > >The binary upload cannot transition to testing -- a buildd binary build is > >required. So far as I know -- assuming [1] is still up-to-date, this means > >a nuisance uplo

Re: Idea: autopkgtest on big-endian for 'Architecture: all' packages to catch endian bugs

2022-08-28 Thread Adam Borowski
On Sun, Aug 28, 2022 at 04:56:26PM +, Thorsten Glaser wrote: > Didier 'OdyX' Raboud dixit: > >If these tests are run at build-time, errors halt the build and that provides > > That may not be enough, though; there are cases where the build > architecture determines artefact endianness (e.g. wi

Re: Need a buildd build after trip through NEW -- best practice?

2022-08-28 Thread Paul Wise
On Sun, 2022-08-28 at 17:54 -0500, Steven Robbins wrote: > Specficially: in the case of a NEW binary upload, could a manual request be > implemented (pick a different name if "give back" is not suitable) such that > it > is thrown away and replaced by a buildd build? The dak software already h

Re: Comments on proposing NEW queue improvement (Re: Current NEW review process saps developer motivation

2022-08-28 Thread Russ Allbery
Scott Kitterman writes: > Sean Whitton wrote: >> I think we still want the binary package namespace checking? >> I.e., a GR just saying "ftpteam should not do a full >> licensing/copyright check for packages in binNEW". >> Then no software changes are required. > I think that a GR to prohibit

Re: Comments on proposing NEW queue improvement (Re: Current NEW review process saps developer motivation

2022-08-28 Thread Scott Kitterman
On Sunday, August 28, 2022 11:53:50 PM EDT Russ Allbery wrote: > Scott Kitterman writes: > > Sean Whitton wrote: > >> I think we still want the binary package namespace checking? > >> > >> I.e., a GR just saying "ftpteam should not do a full > >> licensing/copyright check for packages in binNEW"

Re: Comments on proposing NEW queue improvement (Re: Current NEW review process saps developer motivation

2022-08-28 Thread Russ Allbery
Scott Kitterman writes: > If I look at a package and determine it's only in New due to a new > binary package name and that means the project has prohibited me from > looking for other issues in the package until some time later when it's > not in New, then I feel pretty precisely like I'm prohib

Re: Need a buildd build after trip through NEW -- best practice?

2022-08-28 Thread Andrey Rahmatullin
On Sun, Aug 28, 2022 at 05:54:36PM -0500, Steven Robbins wrote: > I understand that the current state is that one can only "give back" a failed > build. I'm asking whether this must necessarily be the case. Yes, by definition. > Specficially: in the case of a NEW binary upload, could a manual