Re: ardour 5.4 released
On 10/12/2016 10:14 PM, Jaromír Mikeš wrote: > Can we be bitten by same old bug? > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558777 i played around with the watchfile, and i couldn't fix it. i *guess* this is really the bug you mentioned. > > BTW this workaround importing latest release (tested with simplified > watch file from Robin) ... Should we do it this way? yes, i think so. the little annoyance of having to specify the version number manually is in no relation to the time I (and you) have spent in trying to fix d/watch... gfrdsa IOhannes signature.asc Description: OpenPGP digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: ardour 5.4 released
2016-10-02 11:09 GMT+02:00 Jaromír Mikeš : > 2016-10-02 10:48 GMT+02:00 IOhannes m zmölnig (Debian/GNU) > : >> >> >> Am 01. Oktober 2016 22:49:01 MESZ, schrieb "Jaromír Mikeš" >> : >>>Hi, >>> >>>I have tried to get repacked ardour 5.4 source but get repacked >>>without dfsg suffix. >>>uscan >>>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? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558777 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 best mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: ardour 5.4 released
2016-10-02 10:48 GMT+02:00 IOhannes m zmölnig (Debian/GNU) : > > > Am 01. Oktober 2016 22:49:01 MESZ, schrieb "Jaromír Mikeš" > : >>Hi, >> >>I have tried to get repacked ardour 5.4 source but get repacked >>without dfsg suffix. >>uscan >>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 best regards mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers