Re: git-dpm -> gbp conversion (mass-change)
On 08/08/2018 09:19 PM, Nikolaus Rath wrote:
> On Aug 08 2018, Thomas Goirand <zigo@debian.org> wrote:
>> On 08/08/2018 01:38 PM, Nikolaus Rath wrote:
>>> That doesn't make sense to me. git-dpm maintains (and rebases) Debian
>>> patches separately, so upgrading to a new upgrade release can
>>> principally not be any harder than with gbp.
>>
>> It is a nightmare when patches are conflicting.
>
> Could you give an example where this is handled differently by git-dpm
> than by gbp? As I said, the problem is exactly the same.
Here's a few cases where it gets nasty.
Let's say a patch has been applied upstream. In such case, I just do a
few "quilt push" to check, then I see one is already applied (by running
"patch --dry-run -P1 <debian/patches/foo.patch"), then I just remove the
patch from the series file, and I'm done. In case of using git with the
rebase thing, then I get into useless trouble.
Another case is if upstream moved sources from one directory to another.
In such case, I just edit the patch directly to fix the path. With a git
rebase, you'd probably have to rewrite all the patch by hand. Here
again, that's useless trouble.
Now, if all goes well, and if the above cases are fixed, them I'm fine
using "gbp pq", but it's not any better than fixing by hand using quilt.
Cheers,
Thomas Goirand (zigo)
Reply to: