[Mergebot-discuss] Consider using dgit instead of gbp
Ian Jackson
ijackson at chiark.greenend.org.uk
Tue Jul 19 09:57:57 UTC 2016
Sean Whitton writes ("Consider using dgit instead of gbp"):
> Consider using dgit instead of gbp. Since dgit is designed to abstract
> from packaging repository workflows, you would be able to drop all three
> of the things listed under "Assumptions" in your README.
Sean sent me a link to mergebot. Interesting idea.
> Something like this:
>
> 1. existing code to extract patch from the BTS
> 2. dgit clone package
> 3. cd package
> 4. git am < bts.patch or your existing commit code
> 5. gbp dch
> 6. dgit sbuild
>
> The user would, after verifying the package, do the following:
>
> 1. cd package
> 2. dgit push
>
> The only problem with this is that your non-dgit packaging repo isn't
> updated.
So the result is that the upload looks a bit like an NMU.
> You could do something like `git push --all vcs-git` in that
> case and maybe you could provide a helper. In a lot of cases that would
> depend on unreleased dgit functionality to handle patches-unapplied
> repositories.
That functionality is not just unreleased but only half-finished.
It's my top work item ATM.
Ian.
More information about the Mergebot-discuss
mailing list