On 19 August 2014 13:22, Tianon Gravi <admwig...@gmail.com> wrote: > Have you tried comparing the existing orig tarball from the archive to > the corresponding tarball downloaded via uscan? > > $ curl -sSL ' > http://http.debian.net/debian/pool/main/libr/librabbitmq/librabbitmq_0.5.0.orig.tar.gz > ' > | sha1sum > 826286c3f04695bdc231d8e7b0541f871975cdcc - > > $ curl -sSL 'https://github.com/alanxz/rabbitmq-c/archive/v0.5.0.tar.gz' > | sha1sum > 826286c3f04695bdc231d8e7b0541f871975cdcc - >
Howe very odd. Oh, I see, that is different to the following file: $ curl -sSL ' https://github.com/alanxz/rabbitmq-c/releases/download/v0.5.0/rabbitmq-c-0.5.0.tar.gz' | sha1sum 35910a2d66a2ec1d11403e6a79ca50e31db719da - I thought github didn't allow file releases any more. Also, looking in Git, it would appear that Michael is currently working > on packaging 0.5.1. ;) > Seems like I missed those changes. Not sure how. Might be better off spending my time on django-guardian instead. -- Brian May <br...@microcomaustralia.com.au>
