Bug#1127616: developers-reference: should document using git-debpush to upload

Timo Röhling <[email protected]> Thu, 12 Feb 2026 13:56:01 +0100

Newsgroups	gmane.linux.debian.devel.policy
Organization	The Debian Project
Message-ID	<d1a075c2-f6a6-4677-82bd-2655e2c8b724__19225.4769544647$1770901168$gmane$org@mail.gaussglocke.de>

* Sean Whitton <[email protected]> [2026-02-12 12:00]:
>Back when I worked NEW: I very often wanted to see the list of files
>installed by the package, and the full, expanded list of binary package
>relationships.  Rarely, I would actually look inside the .deb.
>
>These are real needs for NEW review.
 From personal experience, both as sponsor and packager, I'd like to add 
that these are things that you can easily get wrong by accident, so I'm 
very much in favor of these sanity checks for NEW.

>I think one source of opposition for autobuilding packages before they
>go into NEW is that the DFSG team won't yet has asserted/confirmed that
>the license permits autobuilding.  But, well, we already have Salsa CI,
>so I think that is not worth blocking on.
I sometimes upload a new package together with one or more new 
dependencies, which means it might not be immediately autobuildable from 
the archive alone. Certainly not an unsolvable problem, but it shows 
that there are edge cases to be considered.


Cheers
Timo

-- 
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

signature.asc (application/pgp-signature, 833 B)