# HG changeset patch
# User Hal Wine <hwine@mozilla.com>
# Date 1360200908 28800
# Node ID a3c3b8077cbeec7c381a4b312d722d575a738610
# Parent  ce6ad4c0cba74f2771c54774537d0263e72e22e6
Add test to show dulwich fault on invalid timezone data

A recent real world occurrence - user hand edited the timezone field in
an hg export to provide a unique value (from prior export). Hg imported
the export okay, but dulwich threw an exception.

This test shows the fault.

diff -r ce6ad4c0cba7 -r a3c3b8077cbe tests/test-timezone.t
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tests/test-timezone.t	Wed Feb 06 17:35:08 2013 -0800
@@ -0,0 +1,32 @@
+This test shows how dulwich fails to convert a commit accepted by hg.
+
+In the real world case, it was a hand edit by the user to change the
+timezone field in an export. However, if it is good enough for hg, we
+have to make it good enough for git.
+
+Load commonly used test logic
+  $ . "$TESTDIR/testutil"
+
+  $ hg init hgrepo
+  $ cd hgrepo
+  $ touch beta
+  $ hg add beta
+  $ fn_hg_commit -m "test commit"
+  $ cat >patch2 <<EOF
+  > # HG changeset patch
+  > # User J. User <juser@example.com>
+  > # Date 1337962044 25201
+  > # Node ID 1111111111111111111111111111111111111111
+  > # Parent  0000000000000000000000000000000000000000
+  > Patch with sub-minute time zone
+  >
+  > diff --git a/alpha b/alpha
+  > new file mode 100644
+  > --- /dev/null
+  > +++ b/alpha
+  > @@ -0,0 +1,1 @@
+  > +alpha
+  > EOF
+  $ hg import patch2
+  applying patch2
+  $ hg gexport