Bug#780584: RFS: s3cmd/1.5.2-1 ITA
On Wed, Mar 18, 2015 at 7:34 PM, Gianfranco Costamagna wrote:
> I opened upstream issue 505
> https://github.com/s3tools/s3cmd/issues/505
Could you also suggest removing the manual page from git and tarballs
so it is always built from source?
> I see them here
> https://github.com/s3tools/s3cmd/releases
> is that enough? uscan seems to be missing some bits, because it doesn't pick up
> the key
Personally I'd suggest upstream upload tarballs for all the releases
to GitHub as well as SF.
That should be enough for uscan, the issue appears to be that you are
matching against the GitHub-auto-generated tarballs and not the ones
that upstream has created and uploaded next to them. Here is a fixed
watch file:
version=3
opts=pgpsigurlmangle=s/$/.asc/ \
https://github.com/s3tools/s3cmd/releases \
.*/s3cmd-(\d\S*)\.tar\.gz
> I checked the debian file and seems correct
> Depends: python-dateutil, python:any (>= 2.7.5-5~), python:any (<< 2.8), python, python-magic
Hmm, I didn't get python-magic in the Depends when I built it. Both
with the previous version and the one you just uploaded. The previous
version I built with debuild and the current one inside pbuilder. I
have python-magic installed in both.
> mmm I don't have an amazon service "free" to test... seems difficult to achieve
> (we use a private key)
Ok, I guess it would be hard.
> it is a command line tool, are them really necessary?
Not necessary, but useful for showing potential users what using it looks like
>>lintian:
>
> I restored the patches, they disappeared.
Please do use DEP-3 for patch headers and get patches upstreamed.
http://dep.debian.net/deps/dep3/
> can I just report them upstream?
> https://github.com/s3tools/s3cmd/issues/506
>
> I can fix them, but rewriting downstream is really bad in my opinion, I would like to help
> upstream fixing them and then wait for the next release.
Agreed, getting upstream to fix them and start using these tools is
the best option.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Reply to: