[Bug 3600] New: "hg archive" creates "zip" archives with unexpected timestamp for users in non-zero offset timezone areas

[bugzilla-daemon at bz.selenic.com]

http://bz.selenic.com/show_bug.cgi?id=3600

          Priority: normal
            Bug ID: 3600
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: "hg archive" creates "zip" archives with unexpected
                    timestamp for users in non-zero offset timezone areas
          Severity: bug
    Classification: Unclassified
                OS: All
          Reporter: foozy at lares.dti.ne.jp
          Hardware: All
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

"hg archive" creates archive files with timestamp in GMT.

"tar" archives seem to be extracted by "tar" command with local
timezone offset of the environment where archive files are
EXTRACTED.

But "zip" archives seem to be extracted without local timezone
offset: at least, "unzip" on Linux and Explorer on Windows 7
extract in such manner.

For example, the zip file archiving the changeset commited at
"2012-08-27 19:44 +0900" creates files with "2012-08-27 10:44"
timestamp.

In one of the most usual usecase, commiting changesets, archiving
files in one of them and extracting archived files are done in
the same timezone area. So, files with GMT timestamp look strange
in such case.

Of course, each actions (commiting/archiving/extracting) may be
done in different timezone areas. But in such case, many of users
seem not to mind about timestamp of extracted files.

So, "zip" archives should be created with not GMT but localtime
of the environment where archive files are CREATED.

Or, should they be choosable as archive type ?

- "zip" for localtime, and "gmtzip" for GMT, or
- "zip" for GMT, and "ltzip" for localtime

-- 
You are receiving this mail because:
You are on the CC list for the bug.