Marco d'Itri writes ("Bug#1127616: developers-reference: should document using
git-debpush to upload"):
> 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.
>
> 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.
Well, that argument doesn't prove that the tag2upload system wouldn't
act on that tag in a way that would "flip some switches" which would
somehow interfere with future dput-based uploads. After all the whole
point is that the uploader simply signs a tag and then the tag2upload
service does Much Complicated Stuff. The whole point is that the
(simple) signed tag causes Debian's official source code management
systems to change state (in a fairly complex way) - thereby moving
some of the complexity away from the user and helping make it more of
an implementation detail.
But knowing the system, I can reassure Marc on this point.
> (Which I still believe should have been the default, with the added
> benefit of making git-debupush much simpler to implement.)
We chose to make the usual use case the default. This may make the
functionality and behaviour less immediately obvious to the new
adopter, but we think it's the right tradeoff.
Most of the code in git-debpush is trying to spot user mistakes. We
have tried quite hard to have it detect what problems we can, within
certain constraints (for example, git-debpush contacts Salsa but not
other network services).
Soemthing that would just Do Exactly What I Told you would be very
simple to write indeed. You're welcome to write that tool - the
format is documented in tag2upload(5) :-). Or you can even write the
tag by hand if you like that kind of thing.
We think most users will prefer software that makes uploading a 1-step
process, but which tries to spot and query about potential problems.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
