On 07/07/2019 03:03, pkgoyq@neverbox.com wrote:
On Sat, Jul 6, 2019 at 6:18 PM Rebecca N. Palmer wrote:
What git repository are you running it in? It should be run in the
packaging repository, not the upstream one.
From the next post, it was being run in the right place.
(The package'
On Sat, Jul 6, 2019 at 9:55 PM Tong Sun
wrote:
> I only knew to use this previously:
>
> gbp import-orig --uscan
>
> Today I tried `gbp import-orig --uscan --pristine-tar`, after having
> done the above `gbp import-orig --uscan`
>
> > If so, it might
> > have failed after creating the 4.0.3 tag
On Sat, Jul 6, 2019 at 6:18 PM Rebecca N. Palmer wrote:
> What git repository are you running it in? It should be run in the
> packaging repository, not the upstream one. (The package's Vcs-Git
> field currently points to upstream, which is itself a bug.)
Please elaborate what you mean, Rebecca
On Sat, Jul 6, 2019 at 6:18 PM Rebecca N. Palmer wrote:
> gbp import-orig --uscan --pristine-tar is the same command as I normally
> use.
>
> Did it fail with something different the first time?
I only knew to use this previously:
gbp import-orig --uscan
Today I tried `gbp import-orig --uscan
gbp import-orig --uscan --pristine-tar is the same command as I normally
use.
Did it fail with something different the first time? If so, it might
have failed after creating the 4.0.3 tag, leaving it in the way of
future attempts.
What git repository are you running it in? It should be run
Hi,
I had been following these two articles for importing a new upstream version
http://marquiz.github.io/git-buildpackage-rpm/gbp.import.html
https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.new.upstream.html
by doing
gbp import-orig --uscan
But today, I learnt
6 matches
Mail list logo
