The following commit has been merged in the master branch:
commit 9408c3ae5aab294fe869372af3a162a972c3b1cd
Author: Raphael Geissert <[email protected]>
Date:   Sun May 3 12:47:41 2009 -0500

    Reset the TZ env var to avoid producing different results on different 
setups
    
    This change mainly affects tar and its "implausibly old time stamp" 
warnings,
    which were timezone-dependent therefore breaking some of the tests when the
    user's timezone was not GMT -8.

diff --git a/frontend/lintian b/frontend/lintian
index 69bac31..ac4229c 100755
--- a/frontend/lintian
+++ b/frontend/lintian
@@ -109,6 +109,8 @@ $| = 1;
 
 # reset locale definition (necessary for tar)
 $ENV{'LC_ALL'} = 'C';
+# reset timezone definition (also for tar)
+$ENV{'TZ'}     = '';
 
 # }}}
 
diff --git a/t/debs/deb-format-ancient-file/tags 
b/t/debs/deb-format-ancient-file/tags
index fa732ab..83de2df 100644
--- a/t/debs/deb-format-ancient-file/tags
+++ b/t/debs/deb-format-ancient-file/tags
@@ -1,2 +1,2 @@
-E: deb-format-ancient-file: package-contains-ancient-file 
usr/share/doc/deb-format-ancient-file/changelog.gz 1969-12-31
-E: deb-format-ancient-file: tar-errors-from-control control: implausibly old 
time stamp 1969-12-31 16:00:00
+E: deb-format-ancient-file: package-contains-ancient-file 
usr/share/doc/deb-format-ancient-file/changelog.gz 1970-01-01
+E: deb-format-ancient-file: tar-errors-from-control control: implausibly old 
time stamp 1970-01-01 00:00:00
diff --git a/t/source/cruft-ancient-file/tags b/t/source/cruft-ancient-file/tags
index d4439d4..e5945ba 100644
--- a/t/source/cruft-ancient-file/tags
+++ b/t/source/cruft-ancient-file/tags
@@ -1 +1 @@
-I: cruft-ancient-file source: tar-errors-from-source 
cruft-ancient-file-1.0/README: implausibly old time stamp 1969-12-31 16:00:00
+I: cruft-ancient-file source: tar-errors-from-source 
cruft-ancient-file-1.0/README: implausibly old time stamp 1970-01-01 00:00:00

-- 
Debian package checker


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to