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

Holger Levsen <[email protected]> Tue, 10 Feb 2026 15:11:21 +0000

Newsgroups	gmane.linux.debian.devel.policy
Message-ID	<aYtKmeYk3DP9YsNJ__7520.29918819375$1770736414$gmane$org@layer-acht.org>

control: severity -1 normal
thanks

On Tue, Feb 10, 2026 at 02:52:12PM +0000, Sean Whitton wrote:
> I made the following change to dev-ref, but it was reverted.  So with
> this bug I request review from the Developer's Reference maintainers.
> I didn't think there is anything controversial about this, but please
> let me know what you think needs changing.

as I said on the thread on -devel, there are at least two annoying bugs in
tag2upload which make me not want to use it yet and which I think also 
prevent suggesting to use it to everyone in all cases.

(to repeat: a.) impossible to do -1 uploads while preserving existing signed
upstream tarballs and b.) loosing the information that an upload was sponsored.)

and there are more limitations to tag2upload as you've described in your patch,
which I think are additional reasons not to suggest tag2upload by default for
everyone, but rather as a special workflow for people who want to experiment
(and/or use) it.

> +To perform a source-only upload, use the ``git debpush`` program. 
[...]
> +package maintainers perform.  However, there are some cases in which a
> +source-only upload is possible but ``git debpush`` cannot be used: 

^^ this is what I ment in my last paragraph.

-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Bottled water companies don't produce water, they produce plastic bottles.

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