Bug#914314: git-buildpackage: import-orig --uscan passes --symlink unconditionally

Hi Ian! > I read this report and I don't see any explanation for the RC status. > As far as I can tell this is not a regression ? And it doesn't seem > likely that it causes unrecoverable data loss or the upload of badly > corrupted packsges ? And it only affects one aspect of gbp's >

Bug#914314: git-buildpackage: import-orig --uscan passes --symlink unconditionally

Control: severity -1 normal Hi. This bug came to my attention because I maintain a package with a dependency on git-buildpackage. This bug, which is flagged RC, is causing the testing autoremoval system to want to remove my package, presumably so that it can eventually remove gbp. I read this

Bug#914314: git-buildpackage: import-orig --uscan passes --symlink unconditionally

Package: git-buildpackage Version: 0.9.21 Followup-For: Bug #914314 Control: severity -1 serious Dear colleagues, I have to remove the offending '--symlink' arg here: /usr/lib/python3/dist-packages/gbp/deb/uscan.py: cmd = ['uscan', '--symlink', '--destdir=%s' % destdir, '--dehs'] to avoid

Bug#914314: git-buildpackage: import-orig --uscan passes --symlink unconditionally

Package: git-buildpackage Version: 0.9.10+nmu1 Severity: normal Hi, As per the title. This is annoying because it overrides the setting in ~/.devscripts.conf. Moreover, it can create conflicts when tarballs from separate projects are named the same. For example, csound publishes the manual in a