Bug#616650: Info received (2011h is available)
On Sun, Sep 18, 2011 at 12:59:53AM -0400, Yaroslav Halchenko wrote: On Sat, 17 Sep 2011, Arnaud Fontaine wrote: While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). as far as I see it -- there is no code change between, only that 2011g more up-to-date and includes more zones (which is a good thing): $ diff -Naur pytz-2011g pytz-2011h | lsdiff pytz-2011g/PKG-INFO pytz-2011g/pytz/__init__.py pytz-2011g/pytz/tests/test_tzinfo.py pytz-2011g/pytz/zoneinfo/America/Kralendijk pytz-2011g/pytz/zoneinfo/America/Lower_Princes pytz-2011g/pytz/zoneinfo/Asia/Anadyr pytz-2011g/pytz/zoneinfo/Asia/Irkutsk pytz-2011g/pytz/zoneinfo/Asia/Kamchatka pytz-2011g/pytz/zoneinfo/Asia/Krasnoyarsk pytz-2011g/pytz/zoneinfo/Asia/Magadan pytz-2011g/pytz/zoneinfo/Asia/Novokuznetsk pytz-2011g/pytz/zoneinfo/Asia/Novosibirsk pytz-2011g/pytz/zoneinfo/Asia/Omsk pytz-2011g/pytz/zoneinfo/Asia/Sakhalin pytz-2011g/pytz/zoneinfo/Asia/Vladivostok pytz-2011g/pytz/zoneinfo/Asia/Yakutsk pytz-2011g/pytz/zoneinfo/Asia/Yekaterinburg pytz-2011g/pytz/zoneinfo/Europe/Kaliningrad pytz-2011g/pytz/zoneinfo/Europe/Moscow pytz-2011g/pytz/zoneinfo/Europe/Samara pytz-2011g/pytz/zoneinfo/Europe/Volgograd pytz-2011g/pytz/zoneinfo/iso3166.tab pytz-2011g/pytz/zoneinfo/W-SU pytz-2011g/pytz/zoneinfo/zone.tab pytz-2011g/pytz.egg-info/PKG-INFO pytz-2011g/pytz.egg-info/SOURCES.txt Just a FYI, the zoneinfo files should not matter. We remove them before installation and use the system ones from the tzdata package. You can see that they are not even included in the package: http://packages.debian.org/sid/all/python-tz/filelist The original bug report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416202 Moreover, after looking quickly at your package, it includes egg-info into the diff.gz... (maybe I'm just being too fuzzy ;)) I guess that one got corrected by setup.py clean ;-) --- python-tz-2011h.orig/pytz.egg-info/SOURCES.txt +++ python-tz-2011h/pytz.egg-info/SOURCES.txt @@ -2,6 +2,7 @@ LICENSE.txt MANIFEST.in README.txt +setup.cfg setup.py pytz/__init__.py pytz/exceptions.py If you build using svn-buildpackage you don't get this. It's a pity setuptools is makes a mess here. -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616650: Info received (2011h is available)
2011/9/17 Arnaud Fontaine ar...@debian.org: Hi, I have checked on difference of 2011h from 2010b: * API changes are minimal and seems to be backward compatible * primarily it is an update of timezones information I saw no harm of updating unstable with it, so I did a sloppy uupdate, cloned original bugreport to leave 3k compatibility on TODO list, tested the package (lintian warnings remained), and uploaded to 10-days delayed. (if you don't mind, I could re-upload to 0-delay ;) ) If rejected/objected, NMU and its backports for all recent Debian and Ubuntu releases could be found at neuro.debian.net Indeed, I was waiting for Gediminas to confirm that there is no problem with updating the packages in pkg-zope SVN repository (which includes pytz) to ZTK 1.1.2 before uploading these packages... Gediminas: have you had time to look at that? While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). I would like all the work that is already done uploaded first, and only then look what is not up-to-date with ZTK 1.1 pytz is not even part of ZTK, and should always be the latest, so this discussion did not need to happen. I can update the ZTK myself, and the bump of pytz version would be one I would worry the least about. It is best to match the tzdata version, because python-tz package uses that data instead of the included one. tzdata in sid is already at 2011j. -- Gediminas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616650: Info received (2011h is available)
On Wed, Sep 21, 2011 at 05:45:45PM +0300, Gediminas Paulauskas wrote: 2011/9/17 Arnaud Fontaine ar...@debian.org: Hi, I have checked on difference of 2011h from 2010b: * API changes are minimal and seems to be backward compatible * primarily it is an update of timezones information I saw no harm of updating unstable with it, so I did a sloppy uupdate, cloned original bugreport to leave 3k compatibility on TODO list, tested the package (lintian warnings remained), and uploaded to 10-days delayed. (if you don't mind, I could re-upload to 0-delay ;) ) If rejected/objected, NMU and its backports for all recent Debian and Ubuntu releases could be found at neuro.debian.net Indeed, I was waiting for Gediminas to confirm that there is no problem with updating the packages in pkg-zope SVN repository (which includes pytz) to ZTK 1.1.2 before uploading these packages... Gediminas: have you had time to look at that? While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). I would like all the work that is already done uploaded first, and only then look what is not up-to-date with ZTK 1.1 pytz is not even part of ZTK, and should always be the latest, so this discussion did not need to happen. I can update the ZTK myself, and the bump of pytz version would be one I would worry the least about. It is best to match the tzdata version, because python-tz package uses that data instead of the included one. tzdata in sid is already at 2011j. As I said in another e-mail, the python-tz package does not contain the zoneinfo data itself. It is patched to use the data from tzdata. So we only need to upload it when the code changes. We get data upgrades for free and we'll always be in-sync with tzdata. -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616650: Info received (2011h is available)
Hi, I have checked on difference of 2011h from 2010b: * API changes are minimal and seems to be backward compatible * primarily it is an update of timezones information I saw no harm of updating unstable with it, so I did a sloppy uupdate, cloned original bugreport to leave 3k compatibility on TODO list, tested the package (lintian warnings remained), and uploaded to 10-days delayed. (if you don't mind, I could re-upload to 0-delay ;) ) If rejected/objected, NMU and its backports for all recent Debian and Ubuntu releases could be found at neuro.debian.net Indeed, I was waiting for Gediminas to confirm that there is no problem with updating the packages in pkg-zope SVN repository (which includes pytz) to ZTK 1.1.2 before uploading these packages... Gediminas: have you had time to look at that? While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). Moreover, after looking quickly at your package, it includes egg-info into the diff.gz... (maybe I'm just being too fuzzy ;)) Cheers, -- Arnaud Fontaine pgpFDh1qqCR37.pgp Description: PGP signature
Bug#616650: Info received (2011h is available)
On Sat, 17 Sep 2011, Arnaud Fontaine wrote: While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). as far as I see it -- there is no code change between, only that 2011g more up-to-date and includes more zones (which is a good thing): $ diff -Naur pytz-2011g pytz-2011h | lsdiff pytz-2011g/PKG-INFO pytz-2011g/pytz/__init__.py pytz-2011g/pytz/tests/test_tzinfo.py pytz-2011g/pytz/zoneinfo/America/Kralendijk pytz-2011g/pytz/zoneinfo/America/Lower_Princes pytz-2011g/pytz/zoneinfo/Asia/Anadyr pytz-2011g/pytz/zoneinfo/Asia/Irkutsk pytz-2011g/pytz/zoneinfo/Asia/Kamchatka pytz-2011g/pytz/zoneinfo/Asia/Krasnoyarsk pytz-2011g/pytz/zoneinfo/Asia/Magadan pytz-2011g/pytz/zoneinfo/Asia/Novokuznetsk pytz-2011g/pytz/zoneinfo/Asia/Novosibirsk pytz-2011g/pytz/zoneinfo/Asia/Omsk pytz-2011g/pytz/zoneinfo/Asia/Sakhalin pytz-2011g/pytz/zoneinfo/Asia/Vladivostok pytz-2011g/pytz/zoneinfo/Asia/Yakutsk pytz-2011g/pytz/zoneinfo/Asia/Yekaterinburg pytz-2011g/pytz/zoneinfo/Europe/Kaliningrad pytz-2011g/pytz/zoneinfo/Europe/Moscow pytz-2011g/pytz/zoneinfo/Europe/Samara pytz-2011g/pytz/zoneinfo/Europe/Volgograd pytz-2011g/pytz/zoneinfo/iso3166.tab pytz-2011g/pytz/zoneinfo/W-SU pytz-2011g/pytz/zoneinfo/zone.tab pytz-2011g/pytz.egg-info/PKG-INFO pytz-2011g/pytz.egg-info/SOURCES.txt Moreover, after looking quickly at your package, it includes egg-info into the diff.gz... (maybe I'm just being too fuzzy ;)) I guess that one got corrected by setup.py clean ;-) --- python-tz-2011h.orig/pytz.egg-info/SOURCES.txt +++ python-tz-2011h/pytz.egg-info/SOURCES.txt @@ -2,6 +2,7 @@ LICENSE.txt MANIFEST.in README.txt +setup.cfg setup.py pytz/__init__.py pytz/exceptions.py -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616650: Info received (2011h is available)
I have checked on difference of 2011h from 2010b: * API changes are minimal and seems to be backward compatible * primarily it is an update of timezones information I saw no harm of updating unstable with it, so I did a sloppy uupdate, cloned original bugreport to leave 3k compatibility on TODO list, tested the package (lintian warnings remained), and uploaded to 10-days delayed. (if you don't mind, I could re-upload to 0-delay ;) ) If rejected/objected, NMU and its backports for all recent Debian and Ubuntu releases could be found at neuro.debian.net Cheers, -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
