Re: releasing major library change to unstable without coordination

2021-12-23 Thread Paul Gevers
Hi, [I've read the rest of the thread so far, answering the transition question]. On 23-12-2021 00:45, Jonas Smedegaard wrote: Is it normal and ok to upload a new major release of a library to unstable, without either a) testing that reverse dependencies do not break, or b) coordinating with

Re: releasing major library change to unstable without coordination

2021-12-23 Thread Timo Röhling
Hi Sandro! * Sandro Tosi [2021-12-22 19:24]: there's also a problem of resources: let's take the example of numpy, which has 500+ rdeps. am i expected to: * rebuild all its reverse dependencies with the new version * evaluate which packages failed, and if that failures is due to the new versio

Re: releasing major library change to unstable without coordination

2021-12-23 Thread Rene Engelhard
Hi, Am 23.12.21 um 10:44 schrieb Timo Röhling: > That's true. However, I think it is reasonable to expect a > maintainer to > * look at the release notes for documented API breakage, > * rebuild a few reverse dependencies (ideally the ones which >   exercise the most functionality, but a random pi

Re: releasing major library change to unstable without coordination

2021-12-23 Thread Rene Engelhard
Hi, Am 23.12.21 um 01:24 schrieb Sandro Tosi: > there's also a problem of resources: let's take the example of numpy, > which has 500+ rdeps. am i expected to: > > * rebuild all its reverse dependencies with the new version > * evaluate which packages failed, and if that failures is due to the > n

Re: Porter roll call for Debian Bookworm

2021-12-23 Thread Graham Inggs
Hi A friendly reminder about the porter roll call for bookworm. On Sat, 2 Oct 2021 at 11:57, Graham Inggs wrote: > We are doing a roll call for porters of all prospective release > architectures. If you are an active porter behind one of these > architectures [1] and intend to continue for the

Re: releasing major library change to unstable without coordination

2021-12-23 Thread Stéphane Blondon
Le jeu. 23 déc. 2021 à 01:25, Sandro Tosi a écrit : > > rebuild 500 packages takes hardware resources not > every dd is expected to have at hand (or pay for, like a cloud > account), so until there's a ratt-as-as-service > (https://github.com/Debian/ratt) kinda solution available to every DD If

Re: releasing major library change to unstable without coordination

2021-12-23 Thread Alexis Murzeau
Hi, Le 23/12/2021 à 14:51, Stéphane Blondon a écrit : > Le jeu. 23 déc. 2021 à 01:25, Sandro Tosi a écrit : > >>> rebuild 500 packages takes hardware resources not >> every dd is expected to have at hand (or pay for, like a cloud >> account), so until there's a ratt-as-as-service >> (https://git

Re: releasing major library change to unstable without coordination

2021-12-23 Thread Paul Gevers
Hi, On 23-12-2021 15:03, Alexis Murzeau wrote: Isn't ci.debian.net doing automated builds with experimental version of dependencies ? ci.debian.net doesn't do builds except for autopkgtest that have the "needs-build" restriction, which we discourage unless really needed. Paul OpenPGP_sign

Work-needing packages report for Dec 24, 2021

2021-12-23 Thread wnpp
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1244 (new: 0) Total number of packages offered up for adoption: 184 (new: 1) Total number of packages reques