Hello, On Sun 09 Mar 2025 at 12:38pm +01, Simon Josefsson wrote:
> What should I do if NEW+unstable becomes uninstallable during the NEW > review period? > > Do you want maintainers to re-upload a newly built binary? I've never > done that, but doing so would make sense if you really want maintainers > to ensure that NEW+unstable is installable. > > A binary Go package can have 500+ build dependencies transitively, and > the chance of all of those packages staying at the same version in > unstable during NEW review period is pretty slim. I guess that you > already work around this, because I have only very rarely gotten REJECTS > because of this reason (guessing max 3 times), and I know the situation > must have occured for several packages that I did get ACCEPT on. Hmm, your answer makes me think that I didn't understand the question correctly. So, a more general answer: we mostly care about individual packages and rely on maintainers and britney to care about how they interact. But if we see something which seems obviously like introducing breakage we'll probably ask you about it, and if you tell us it's fine, we'll probably go ahead. -- Sean Whitton
signature.asc
Description: PGP signature
