[Debian-med-packaging] Issue when updating q2cli

[Andreas Tille]

Hi Liubov,

On Sun, Dec 15, 2019 at 12:51:04PM +0100, Liubov Chuprikova wrote:
> 
> This is not a code copy! You accidentally uploaded q2cli's upstream tarball
> into q2templates. Oh, it's happened for all of us, not only once. It would
> be nice to have something to avoid this! Probably, --overwrite-download of
> uscan may be useful. Although, the ideal option would be to overwrite only
> if *not up-to-date*, and otherwise -- do nothing. What do you think?

Argh, I guess this is since uscan simply downloads a tarball
2019.10.0.tar.gz and uses a symlink for the source tarball orig.tar.gz.
When using uscan for the next project it detects:  "Oh, there is just a
file 2019.10.0.tar.gz so there is no need to download it - just do a
symlink."  Voila, we end up with the same tarball for different projects.
This obviously needs some extra care.  May be its a good idea to use the
rename option in d/watch to make sure there are no remainings with the
same name.  Would you like to test and implement it in all q2* packages
once you are touching these?
 
> > which is featuring the same minimized JS as we just dealt with in
> > q2templates.  I've added this into d/changelog as todo.  I did not dived
> > into q2 as deeply as you - so what do you think how to sensibly deal
> > with this (assumed q2templates will be accepted quickly by ftpmaster).
> 
> I have updated qiime and q2cli, they are ready for upload!

Uploaded after some automatic changes by routine-upload --force.

Thank you for your work on this, Andreas.


-- 
http://fam-tille.de