Hi Guido,
(Replying also to the according clone http://bugs.debian.org/733639 in
addition to the original report at http://bugs.debian.org/733470 -- I
suggest to continue this thread in #733639.)
Guido Günther wrote:
> > Push the branch configured as debian-branch, the branch configured as
> > upstream-branch, the pristine-tar branch, and all tags matching
> > upstream-tag and debian-tag, to the remote origin.
>
> Maybe
>
> /usr/share/doc/git-buildpackage/examples/gbp-posttag-push
>
> is what you're (partially) after? (I'm reading this offline so I can't
> check your references yet). This posthook is intended to push up to the
> newly created tag (including the upstream branch).
Partially the code maybe, but I don't need such functionality in a
hook. Using a hook would rather hinder my workflow.
Not sure about the rest of the Debian Perl Group (who mostly knows
about and uses "dpt push"), but my workflow usually looks like this:
* Maybe import (and hence tag) a new upstream release using
git-import-orig.
* Push at least upstream and pristine-tar branches and tags, using
"dpt push"
* modify the package until I think I'm finished, but stay at
UNRELEASED. Run "debuild" and "debdiff ../….deb" after each change
which may have some bigger impact.
* Maybe merge fixups via "git rebase -i"
* Push all changes so far (usually doesn't matter if I do "git push"
or "dpt push")
* Replace the UNRELEASED, bump the changelog entry's date stamp.
* Run pdebuild
* Run lintian on the changes file
* Review the changes file manually
* Install the resulted packages and test them
* Run "git-buildpackage --git-tag-only" to set the tags
* Run dput on the changes file
* If the upload succeeds, then run "dpt push", i.e. push all relevant
branches and tags.
I'm mostly picky about when to do stuff which can't be reverted,
especially uploads and pushing, so I do them last after I've verified
that everything else is fine. Hence a hook wouldn't work for me. (And
yes, both, the push and the dput could fail, but due to commit
notifications on IRC I can be quite sure that nobody else pushed stuff
in the meantime.)
But it would be nice to do the pushing of branches and tags in one
short DWIM command instead of two short commands or one long command
(git push + git push --tags or listing all refs manually), like "dpt
push" does. So I extended "dpt push" to parse gbp.conf files, so that
I can use it outside the Debian Perl Group, too, e.g. for the Debian
Zsh Maintainers.
So "dpt push" already does what I want. I just think that such generic
functionality probably better belongs to gbp itself than into a
team-specific package. And I suspect that gbp already contains all the
relevant functionality as proven code, just not gathered in a push
command, while "dpt push" is (at least since my gbp.conf parser in
shell code :-) a rather hackish script which likely does not cover all
corner cases properly.
I hope the reason for this feature request is now more clear.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
