On Tue, May 21, 2019 at 12:42 AM Sergio Durigan Junior wrote: > > On Saturday, May 18 2019, Geert Stappers wrote: > > > On Sat, May 18, 2019 at 11:53:13AM -0400, Tong Sun wrote: > >> Hi, > >> > >> How to fix this? > >> > >> $ gbp import-orig --uscan --verbose > >> gbp:debug: ['git', 'rev-parse', '--show-cdup'] > >> gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] > >> gbp:debug: ['git', 'rev-parse', '--git-dir'] > >> gbp:debug: ['git', 'for-each-ref', '--format=%(refname:short)', > >> 'refs/heads/'] > >> gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/upstream'] > >> gbp:debug: ['git', 'status', '--porcelain'] > >> gbp:info: Launching uscan... > >> gbp:error: Uscan failed - debug by running 'uscan --verbose' > >> > >> It's within a dir that I get from > >> > >> gbp clone -v --pristine-tar g...@salsa.debian.org:debian/shc.git > > > > <screenshot> > > stappers@paddy:~/src/mentor > > $ cd shc/ > > stappers@paddy:~/src/mentor/shc > > $ gbp import-orig --uscan --verbose > > gbp:debug: ['git', 'rev-parse', '--show-cdup'] > > gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] > > gbp:debug: ['git', 'rev-parse', '--git-dir'] > > gbp:debug: ['git', 'for-each-ref', '--format=%(refname:short)', > > 'refs/heads/'] > > gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/upstream'] > > gbp:debug: ['git', 'status', '--porcelain'] > > gbp:info: Launching uscan... > > gbp:error: Uscan failed - debug by running 'uscan --verbose' > [...] > > FWIW, I can't reproduce it here: > > $ gbp import-orig --uscan --verbose > gbp:debug: ['git', 'rev-parse', '--show-cdup'] > gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] > gbp:debug: ['git', 'rev-parse', '--git-dir'] > gbp:debug: ['git', 'for-each-ref', '--format=%(refname:short)', 'refs/heads/'] > gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/upstream'] > gbp:debug: ['git', 'status', '--porcelain'] > gbp:info: Launching uscan... > gbp:info: package is up to date, nothing to do.
Thanks for checking for me, Sergio. > Maybe this has been fixed recently. I'm using: > > gbp 0.9.13 Indeed, I just did some pushing just yesterday, after a new release in upstream. my gbp was the latest several weeks ago, btw. More on to the cause -- the situation was that there has been some fixes (push) after the last tag in upstream. That's maybe why uscan didn't find the latest to download, but knows package is _not_ up to date either.
