[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#856623: marked as done (unblock: libdatetime-timezone-perl/1:2.09-1+2017a)

Your message dated Fri, 03 Mar 2017 07:01:00 +0000
with message-id <7bd75c39-a5da-96b4-5d45-3f06d16d1095@thykier.net>
and subject line Re: Bug#856623: unblock: libdatetime-timezone-perl/1:2.09-1+2017a
has caused the Debian Bug report #856623,
regarding unblock: libdatetime-timezone-perl/1:2.09-1+2017a
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
856623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856623
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

unblock libdatetime-timezone-perl/1:2.09-1+2017a

Some days ago, a new tzdata release was made upstream (Olson DB
2017a): https://mm.icann.org/pipermail/tz-announce/2017-February/000045.html

I've updated the libdatetime-timezone-perl package in unstable,
following the usual (for stable updates and freeze times) procedure:
I've added a patch debian/patches/olson-2017a which contains the
changes to the perl data files in lib/DateTime representing the
timezone data; plus a fix for the test t/15catalog.t, cherry-picked
from upstream git/2.10 release (necessary because the test checks for
Chile's timezones which grew a new one).

Additionally I updated debian/tools/update-tzdata.sh, the helper
script to create those patches, to match a change in how the created
data files look nowadays. (This script is not contained in the binary
package and is not used during build.)

The result looks like the new upstream release, modulo metadata and
path changes there:
https://metacpan.org/diff/file?source=DROLSKY/DateTime-TimeZone-2.09&target=DROLSKY/DateTime-TimeZone-2.10


I'm attaching a manually stripped down debdiff which only contains
the changes to debian outside of the patch and some relevant parts of
the patch itself.


Thanks in advance,
gregor

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAli4rhlfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYwuw/+M1loHc43LcG+ESN4csgAUsp9o1+56J9MYSz9kc2LurVJtpaQZfAihujG
QCKKi24y8Sqx4eOwCOnJWmpdTrxHxKDzRv3iRjqO8E2SOmPL61rHd/lX5YLRFB6L
Og61mGPAxHjsHEsu3OmcQJsoyRw7tRUU7rh+M8lnUx/+a4/QTAseru8XN+9Sd4je
hQALQBb8T50pcqqw97boXeIvcq+RL0qMQd0jMnrvjwp2wa0U2oT7JzLH78bALI1A
MAkNKtn0Zt6gKX5Ey+T0oQ2M2VTGOaiEcPX2AIhikB3YtolMajsLaedtlD2ibKfp
cxKGpgRQgDE5Wz7J+OBhkQ0FLpOAzZL8MBHvq2de1A5oJA2I3feXl6AqKK57E6pD
AYJoVMIEG5+RCMNB2JiIIdcJaR10CkuRnO5dgwvfLvl9EJ8IJZaQC03MpI+GsET1
V84g8Gb9vyHLpOXqbmJfxDNXgqqturizVsAXevtAN8mm4XDlREkoAWt5o5OEQ4OP
/UGmNyeXF6qlzMhqIZdWf2eL9N+nnAWAVBnmhOTXNyMM/c/7fFNtU62WUbujCQ6s
BVYpcYJzuky2fV/nli3UgZrDlDxaY1GzxF2zdqCOpJOkEmPXpAZHvh4ySRhnxoNu
UpXm8LGCCygeOH1dM3BdS/tjOFgYpsmxR+GsxnQ6xVuNq2hMbA0=
=u7fy
-----END PGP SIGNATURE-----

Attachment: libdatetime-timezone-perl_2.09-1+2017a.diff.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
gregor herrmann:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> unblock libdatetime-timezone-perl/1:2.09-1+2017a
> 
> Some days ago, a new tzdata release was made upstream (Olson DB
> 2017a): https://mm.icann.org/pipermail/tz-announce/2017-February/000045.html
> 
> I've updated the libdatetime-timezone-perl package in unstable,
> following the usual (for stable updates and freeze times) procedure:
> [...]
> 
> 
> Thanks in advance,
> gregor
> 
> 

Unblocked, thanks.

~Niels

--- End Message ---
Reply to: