Hi Thomas, On Tue, Jul 03, 2018 at 10:18:19AM +0200, Thomas Schiex wrote: > Thanks a lot, the uscan worked fine! Excited with this, I did this: > > - I integrated your commit in our upstream git repo (with thanks :-)
Why? Its fully sufficient in https://salsa.debian.org/science-team/toulbar2 since this is definitely no upstream change > - prepared a new GitHub release file including it I do not understand this. Do you want to strip those files *generally* from the upstream tarball? Than in turn you do not need the Files-Exclude in debian/copyright since nothing needs exclusion any more. > - gbp imported the tarball in an empty git repo and pushed it to salsa. Why are you using an empty git repository? The workflow would have been as follows: gbp clone [email protected]:science-team/toulbar2.git cd toulbar2 uscan --verbose --force-download gbp import-orig --pristine-tar ../toulbar2_1.0.0+dfsg.orig.tar.xz Your action seems to have messed up the Git repository on Salsa. If I try $ gbp pull gbp:info: Fetching from default remote for each branch gbp:warning: Skipping non-fast forward of 'master' - use --force or update manually gbp:warning: Skipping non-fast forward of 'pristine-tar' - use --force or update manually gbp:warning: Skipping non-fast forward of 'upstream' - use --force or update manually Whatever you did - you are doing something very different than others. Sorry, I have no time to check further but your usage of empty git repositories sounds very suspicious. I have currently no time to track this down further. Hope this helps so far / somebody else will be able to help Andreas. -- http://fam-tille.de
