Soren Stoutner <[email protected]> writes:

>> Any idea why gbp would fail to parse this?
>
> My guess is that when changing the release version, it created a mismatch 
> between the upstream/pristine-tar tree name and what gbp is now expecting.  
> You might need work with a clean gbp and do a fresh gbp import.

Thanks; I realized I just needed a specific tag for the import I did
instead of just having an "upstream/latest+dfsg" branch.

Once I created that tag I did another attempt and it looks good now!
The only thing it's complaining about is "missing-dep-for-interpreter"
which is actually a bug in lintian, not a problem in my package.

-Phil

Attachment: signature.asc
Description: PGP signature

Reply via email to