Hi, Am Donnerstag, den 13.03.2014, 14:06 +0100 schrieb Andreas Tille: > > This would be quite annoying in my usual workflow. > > I hope you are aware that taring up two byte identical trees usually > does not lead to a byte identical tarball. Well, I was hoping that uscan would not simply create new tarballs, but rather removing it from the tarfile, which seems to be deterministic: $ zcat haskell-mtl_2.1.2.orig.tar.gz | md5sum - bac0c479109021b9d2b3696a0b001f5a - $ zcat haskell-mtl_2.1.2.orig.tar.gz | tar --delete mtl-2.1.2/mtl.cabal | md5sum - 0ef3b46f5e345521fd40bc634e0fc1d1 - $ zcat haskell-mtl_2.1.2.orig.tar.gz | tar --delete mtl-2.1.2/mtl.cabal | md5sum - 0ef3b46f5e345521fd40bc634e0fc1d1 - $ zcat haskell-mtl_2.1.2.orig.tar.gz | tar --delete mtl-2.1.2/mtl.cabal | gzip -n | md5sum - 909d962dacabbf1c5430df2ac1c20ef3 - $ zcat haskell-mtl_2.1.2.orig.tar.gz | tar --delete mtl-2.1.2/mtl.cabal | gzip -n | md5sum - 909d962dacabbf1c5430df2ac1c20ef3 - (This is probably equivalent to what Mike does in python.) Of course I could change my workflow to cope with a non-deterministic "uscan --download", so this is not very important. But then, this thread is all about what level of convenience we allow ourselves, and what we spend our time on. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part