Hi Jeremy,
> This is likely to write tar members in the order of the filesystem which
> may vary accross builds.
Excellent point. Updated patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad mauve.orig/mauve-20140821/debian/rules
mauve/mauve-20140821/debian/rules
--- mauve.orig/mauve-20140821/debian/rules 2015-02-19 00:23:42.974708347
+0000
+++ mauve/mauve-20140821/debian/rules 2015-02-19 00:46:19.635028566 +0000
@@ -30,8 +30,13 @@
mkdir -p debian/mauve/usr/src/mauve
cp -a $(filter-out debian, $(wildcard .??* *)) \
debian/mauve/usr/src/mauve/
- GZIP="-9n" tar -c --gzip -f $(CURDIR)/debian/mauve/usr/src/mauve.tar.gz
\
- -C debian/mauve/usr/src --mtime="$(BUILD_DATE)" mauve
+ cd debian/mauve/usr/src && \
+ # Don't try and include ourselves in our own tarball \
+ find -not -name mauve.tar.gz -and -not -type d -print0 | \
+ LC_ALL="C" sort --zero-terminated | \
+ GZIP="-9n" tar --create --gzip --null --files-from=- \
+ --file $(CURDIR)/debian/mauve/usr/src/mauve.tar.gz \
+ --mtime="$(BUILD_DATE)"
rm -rf debian/mauve/usr/src/mauve
# Build architecture-independent files here.
