Re: gbp:error: Uscan failed

On Sat, May 18, 2019 at 01:30:39PM -0400, Tong Sun wrote: > On Sat, May 18, 2019 at 1:26 PM Geert Stappers wrote: > > > In other words:uscan tries to express there is NO new upstream version > > Ha! > > > Why `uscan` returns a non-zero value for "no new version" > > is unclear to me. > > Ye

Re: gbp:error: Uscan failed

On Tue, May 21, 2019 at 12:42:26AM -0400, 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:info: Launc

Re: gbp:error: Uscan failed

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:

Re: scilab: FTBFS on all

Control: found -1 6.0.1-10 (I suggest opening a new bug for the 6.0.2 issues: as noted above, that probably won't be accepted for buster even if we do get it to build.) Running what I think is the relevant step in a debugger: * Go to the top level directory of a _built_ source tree (i.e. one t

Bug#928892: RFS: heimdall-flash/1.4.2-1

Hello, On Sun, May 12, 2019 at 07:03:44PM +0200, etche...@tutanota.com wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, I am looking for a sponsor for my package "heimdall-flash" it is wrong to file a RFS in your situation. The package heimdal-flash already exists in

Re: Bug#928099: RFS: shc/4.0.1 new upstream release

On Mon, Apr 29, 2019 at 9:16 AM Tong Sun wrote: > > The RFS fixes all the following action items in the bug tracker > (https://tracker.debian.org/pkg/shc): > > A new upstream version is available: 4.0.1 high > Failed to analyze the VCS repository. Please troubleshoot and fix the > issue. high >