Path: csiph.com!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod
From: =?UTF-8?B?R3XDsGrDs24gR3XDsGrDs25zc29u?= <gudjon.i.gudjonsson@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Git, gbp blues
Date: Mon, 26 Aug 2019 08:30:01 +0200
Message-ID: <yzgFP-Jr-7@gated-at.bofh.it>
References: <yz6Gt-2Fh-3@gated-at.bofh.it> <yz6Qa-2IP-15@gated-at.bofh.it> <yz6ZQ-32C-3@gated-at.bofh.it> <yz79v-362-1@gated-at.bofh.it>
Old-Return-Path: <gudjon.i.gudjonsson@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 34
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:11671

Hi Dmitry and Anrdrey

On Sun, Aug 25, 2019 at 10:19 PM Dmitry Shachnev <mitya57@debian.org> wrote=
:
> The correct procedure is running =E2=80=9Cgbp pq import=E2=80=9D *before*=
 importing a new
> tarball. Then after importing you do =E2=80=9Cgbp pq rebase=E2=80=9D.
In fact I did do that.
>
> Sometimes I myself forget to run =E2=80=9Cgbp pq import=E2=80=9D. In this=
 case I do the
> following:
>
> - Remember the current commit SHA1;
> - git reset --hard origin/debian/master;  # or to previous tag
> - gbp pq import;  # this is the needed step
> - git checkout debian/master;  # back to debian/master branch
> - git merge COMMIT_ID;  # that you remembered before
Thanks, this is useful for me.
>
> > But fixing the patches with quilt before importing them the second
> > time seems to fix all my problems.
> If it does not break the patches metadata then it also works.
But what other way is possible?
The patch queue must apply cleanly in gbp pq import and
in general you can assume it doesn't with new upstream and
old patch queue.
I still don't understand how to edit the patches the correct way
after a new upstream release.

Regards
Gudjon

Ps. The package qscintilla2 is pushed, still a few lintian warnings to fix.