Remove pre-devscripts 2.10.70 compat code#86
Conversation
|
Thanks! I've added to nits inline. Can you make the commit message a bit more catchy (I had to look up what this was about in the first place). E.g. like |
We can rely on the <target> element being present in dehs output. The output it looks for from uscan no longer matches anyway. This will allow for gbp import-orig --uscan to adhere to uscan configuration of not using symlinks, if the user has such defined.
|
Oh yes, that's a bit cryptic if one doesn't look at the actual changes. It's not too interesting of a change really, but a little explaining will help. Hopefully you like what I just pushed, if not I'm not really attached to what's written anyway. |
|
@Unit193 thanks. Your commit still tries to squeeze a behaviour change (dropping I'm fine to apply the symlink bit as well but please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914314 - did you test that scenario? If so let me know and I'll push that out as well (keeping your authorship). Alternative would be to pass |
|
I figured they were related, my main goal was to remove --symlink so that I could finally make use of the --uscan option. Importing seemed to work fine but I didn't really have any exotic configuration. I'd be more than willing to test anything that'll help get rid of --symlink though. |
That's why we really want that as a separate commit. Did you check |
|
I haven't, but is something else you get from DEHS out of uscan. Maybe that could be utilized at some point. |
|
Checking |
|
I'm not very well versed in python so beyond basic changes, and writing tests, I'm out of luck. For the time being I have a trigger that strips --symlink out of /usr/lib/python3/dist-packages/gbp/deb/uscan.py, so it works. Thanks for following up! |
Remove pre-devscripts 2.10.70 compat code, no longer matches current output anyway.
This also allows uscan to adhere to the users configuration.