2016-10-02 11:09 GMT+02:00 Jaromír Mikeš <mira.mi...@gmail.com>:
> 2016-10-02 10:48 GMT+02:00 IOhannes m zmölnig (Debian/GNU)
> <umlae...@debian.org>:
>> Am 01. Oktober 2016 22:49:01 MESZ, schrieb "Jaromír Mikeš" 
>> <mira.mi...@gmail.com>:
>>>I have tried to get repacked ardour 5.4 source but get repacked
>>>without dfsg suffix.
>>>uscan --repack
>>>What is right way?
>> I usually do:
>> $ gbp import-orig --uscan
>> and manually add the dfsg suffix when being asked for the version.
> With little fix in watch file is dfsg suffix now added on uscan.
> But gbp import-orig fail ... :( no idea why
> ardour$ gbp import-orig --pristine-tar --uscan
> gbp:info: Launching uscan...
> uscan: Newest version of ardour on remote site is 5.4, local version is 
> 5.3~dfsg
>  (mangled local version is 5.3)
> uscan:    => Newer package available from
>       http://community.ardour.org/srctar
> No files matched excluded pattern as the last matching glob: .gitignore
> No files matched excluded pattern as the last matching glob: icons/win32/*
> gbp:info: using ../ardour_5.4~dfsg.orig.tar.bz2
> What is the upstream version? [5.4~dfsg]
> gbp:error: Cannot symlink '../ardour_5.4~dfsg.orig.gbp.tar.bz2' to
> '../ardour_5.4~dfsg.orig.tar.bz2': File exists

Can we be bitten by same old bug?

BTW this workaround importing latest release (tested with simplified
watch file from Robin) ... Should we do it this way?
$ gbp import-orig --uscan --upstream-version=5.4.0~dfsg



pkg-multimedia-maintainers mailing list

Reply via email to