On Wed, Feb 11, 2026 at 06:08:02PM +0100, Marc Haber wrote:
On Wed, Feb 11, 2026 at 06:04:23PM +0100, Marco d'Itri wrote:
On Feb 11, Marc Haber <[email protected]> wrote:
I am especially concerned about this action flipping some switches
either in my repository or in the archive that might prevent me
from switching back to the classical workflow in the case I don't
like the result.
I understand the caution, but as a "git debpush" user I really think
this is very unlikely. It doesn't even change the working tree state;
all it does is make a specially-formatted tag and push it. It is
definitely not any kind of one-way switch.
Come on, it's just a tag: to see what happens you can run "git
debpush --tag-only" and then check that the repository has not been
maimed.
And if you want to rollback then you can just delete the tag.
(Which I still believe should have been the default, with the added
benefit of making git-debupush much simpler to implement.)
So nothing happens in the archive when I run git debpush?
Why are we doing it then?
Reading what Marco said a little more closely:
"git debpush --tag-only" is documented in git-debpush(1) as "Just tag,
don't push". That means you can try it out, look at the git state, and
roll back locally if you don't like it.
Normally, though, you wouldn't use the --tag-only option and it would
push the tag to Salsa, which will cause the tag2upload service to upload
your changes to the archive.
--
Colin Watson (he/him) [[email protected]]
