Re: volatile.debian.org: Does Debian still support it?
2007/10/1, Peter Samuelson [EMAIL PROTECTED]: What upstream does, and whether the upstream license requires source, are not valid arguments for whether we're meeting the DFSG. There are many packages in Debian that have to be altered to comply with the DFSG. I don't know any example of package which has included some additional sources because the upstream didn't provide real-sources for its sources. What about sources for i.e. gifs and jpegs (wallpapers, icons, menus)? The fact is they have a source as Photoshop or GIMP project and we distribute precompiled files or just exported from original tool. Even Debian logo has own source file: Photoshop project which uses Adobe Photoshop's brush pattern and propertiary font. So it means that Debian logo is not DFSG! I.e. ICU C++ library also doesn't ship Olson database as its original format and it is stored as precompiled C++ source files. You're right. I'll file bugs on both packages when I get a moment. The updating DateTime::TimeZone is not so easy. It is not guaranteed that new Olson DB is compatible with library API. I.e. after updating sarge's version of libdatetime-timezone-perl I had to fix some function because there was serious changes in Olson DB - some of timezone aliases was replaced by special timezones and had to be handled in other way. Even simple changes require to fix test units because these tests relay on actual version of Olson DB. If enough packages need to do this same thing, it would make sense for tzdata to ship a tzdata-source binary package to be build-depended on. For all that, I like the idea about tzdata-source binary package. I really don't want to make a build-dep on other source package. I'll just fill the wishlist for tzdate package and modify my source package so it will use tzdata-source at build time. It will simplify updates in future. I don't want to modify current packages from volatile (sarge and etch). First, I need to test the new build method and then I'll decide if it is a good direction. Thank you for your suggestion. -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Monday 01 October 2007 11:01, Piotr Roszatycki wrote: I don't know any example of package which has included some additional sources because the upstream didn't provide real-sources for its sources. typo3-src is an example. Upstream doesn't provide the source for a font it ships. Search for *debian.orig.tar.gz regards, Holger pgpuXu6kyaiU4.pgp Description: PGP signature
Re: volatile.debian.org: Does Debian still support it?
2007/10/1, Holger Levsen [EMAIL PROTECTED]: I don't know any example of package which has included some additional sources because the upstream didn't provide real-sources for its sources. typo3-src is an example. Upstream doesn't provide the source for a font it ships. Search for *debian.orig.tar.gz I think it is because the nimbus font is released on GPL license, so the source code is required. The Olson DB is public domain so its license does not exact the shipping of source form. -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
On Mon, Oct 01, 2007 at 03:11:05PM +0200, Piotr Roszatycki wrote: I think it is because the nimbus font is released on GPL license, so the source code is required. The Olson DB is public domain so its license does not exact the shipping of source form. The DFSG requires us to ship the source though. Clause 2. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
2007/10/1, Hamish Moffatt [EMAIL PROTECTED]: I think it is because the nimbus font is released on GPL license, so the source code is required. The Olson DB is public domain so its license does not exact the shipping of source form. The DFSG requires us to ship the source though. Clause 2. I read: 2. The program must include source code. The Olson DB is the data, not the source code. The source code is provided as a Perl module. -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
On Mon, 01 Oct 2007, Piotr Roszatycki wrote: 2007/10/1, Hamish Moffatt [EMAIL PROTECTED]: I think it is because the nimbus font is released on GPL license, so the source code is required. The Olson DB is public domain so its license does not exact the shipping of source form. The DFSG requires us to ship the source though. Clause 2. I read: 2. The program must include source code. The Olson DB is the data, not the source code. The source code is provided as a Perl module. Considering that the data is what is used to generate the source code; this seems to be a rather strained argument to me. [And even then, data is clearly a superset of sourcecode.] When the only sane way to generate and/or modify things like DateTime/TimeZone/America/Los_Angeles.pm is to modify northamerica from the Olson database, and then rebuild, it's clear that the Olson database, even if it is merely a compendium of fact, is the source code used to generate the perl module. [That said, I personally don't particularly care whether this perl module includes the source itself, so long as there's a clear dependency on the olson database so that whenever we distribute it we're also distributing the olson database.] Don Armstrong -- The question of whether computers can think is like the question of whether submarines can swim. -- Edsgar Dijkstra http://www.donarmstrong.com http://rzlab.ucr.edu
Re: volatile.debian.org: Does Debian still support it?
2007/9/29, Peter Samuelson [EMAIL PROTECTED]: I just downloaded the source package for libdatetime-timezone-perl, and I don't see the Olson database in there anywhere. Where is it? It looks to me as though you aren't shipping the real source for your package, neither directly nor via Build-Depends. Perhaps your upstream isn't shipping it either, but that isn't an excuse. Even upstream don't ship the Olson database. I'm not conviced that we should ship Olson database. It makes a packaging more complicated and in result we will ship different Perl modules than upstream version. The Olson database is public domain and it doesn't require to be distributed as real source. I.e. ICU C++ library also doesn't ship Olson database as its original format and it is stored as precompiled C++ source files. -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
[Piotr Roszatycki] Even upstream don't ship the Olson database. I'm not conviced that we should ship Olson database. [...] The Olson database is public domain and it doesn't require to be distributed as real source. What upstream does, and whether the upstream license requires source, are not valid arguments for whether we're meeting the DFSG. There are many packages in Debian that have to be altered to comply with the DFSG. I.e. ICU C++ library also doesn't ship Olson database as its original format and it is stored as precompiled C++ source files. You're right. I'll file bugs on both packages when I get a moment. It makes a packaging more complicated and in result we will ship different Perl modules than upstream version. Since we do actually ship the database in the tzdata package, I think what you should do is provide clear instructions for how to rebuild your package from source - starting with 'apt-get source tzdata', then running 'tools/parse_olson' and so forth. Then add a note to your copyright file that part of your source code is actually in the tzdata source package. If enough packages need to do this same thing, it would make sense for tzdata to ship a tzdata-source binary package to be build-depended on. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ signature.asc Description: Digital signature
Re: volatile.debian.org: Does Debian still support it?
On Oct 01, Peter Samuelson [EMAIL PROTECTED] wrote: If enough packages need to do this same thing, it would make sense for tzdata to ship a tzdata-source binary package to be build-depended on. It looks like you may have missed the arm firmware thread of yesterday... -- ciao, Marco signature.asc Description: Digital signature
Re: volatile.debian.org: Does Debian still support it?
[Marco d'Itri] If enough packages need to do this same thing, it would make sense for tzdata to ship a tzdata-source binary package to be build-depended on. It looks like you may have missed the arm firmware thread of yesterday... No, I caught that thread, but thanks for your concern. It doesn't seem to be particularly related to this thread, though. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ signature.asc Description: Digital signature
Re: volatile.debian.org: Does Debian still support it?
[Piotr Roszatycki] 2007/9/26, Martin Zobel-Helas [EMAIL PROTECTED]: will that cause dfsg problems? Not at all. The packages was built with pbuilder. It still is not fully understandable, so I'll try explain: I just downloaded the source package for libdatetime-timezone-perl, and I don't see the Olson database in there anywhere. Where is it? It looks to me as though you aren't shipping the real source for your package, neither directly nor via Build-Depends. Perhaps your upstream isn't shipping it either, but that isn't an excuse. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ signature.asc Description: Digital signature
Re: volatile.debian.org: Does Debian still support it?
Hi, On Wed Sep 26, 2007 at 00:20:10 +0200, Piotr Roszatycki wrote: You made a subtle mistake. You checked the source package for tzdata and the changes are really small. Then you checked the differences for libdatetime-timezone-perl package, but this source package is already compiled. You should check the difference between binary packages for tzdata. The real source data for DateTime::TimeZone is the same as for tzdata source package. Then, the data is precompiled into Perl source. It makes a Debian source package. Accepted now. For the future: i would have been much easier, if you would have said: be warned, the patch is huge, but if you don't look at the compiled version of it, it is these number of lines... Both of us would have had much less trouble. Greetings Martin PS: It might take me a day or so to prepare a VUA, unless someone drafts one for me. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
2007/9/26, Martin Zobel-Helas [EMAIL PROTECTED]: Accepted now. Thank you very much. For the future: i would have been much easier, if you would have said: be warned, the patch is huge, but if you don't look at the compiled version of it, it is these number of lines... Both of us would have had much less trouble. I think we could communicate better if you read the patch, not just statistics about it. By the way, the patch itself does not contain the real source data - the Olson database. I understand that it might be not clear for someone who didn't use this library and know nothing about complexity of timezones support in computing systems. It is really hard piece of technology. Thanks a lot and greetings. -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Piotr Roszatycki wrote: 2007/9/26, Martin Zobel-Helas [EMAIL PROTECTED]: Accepted now. Thank you very much. For the future: i would have been much easier, if you would have said: be warned, the patch is huge, but if you don't look at the compiled version of it, it is these number of lines... Both of us would have had much less trouble. I think we could communicate better if you read the patch, not just statistics about it. By the way, the patch itself does not contain the real source data - the Olson database. I understand that it might be not clear for someone who didn't use this library and know nothing about complexity of timezones support in computing systems. It is really hard piece of technology. It's only logical to NOT start reading a patch of more than 38K lines, so it's far easier if one would explain beforehand why it's that huge... Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Wed Sep 26, 2007 at 14:46:16 +0200, Piotr Roszatycki wrote: 2007/9/26, Martin Zobel-Helas [EMAIL PROTECTED]: Accepted now. Thank you very much. For the future: i would have been much easier, if you would have said: be warned, the patch is huge, but if you don't look at the compiled version of it, it is these number of lines... Both of us would have had much less trouble. I think we could communicate better if you read the patch, not just statistics about it. By the way, the patch itself does not contain the real source data - the Olson database. I understand that it might be will that cause dfsg problems? not clear for someone who didn't use this library and know nothing about complexity of timezones support in computing systems. It is really hard piece of technology. -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
2007/9/26, Martin Zobel-Helas [EMAIL PROTECTED]: I think we could communicate better if you read the patch, not just statistics about it. By the way, the patch itself does not contain the real source data - the Olson database. I understand that it might be will that cause dfsg problems? Not at all. The packages was built with pbuilder. It still is not fully understandable, so I'll try explain: olson db = tzdata source package upstream olson db + time zone compiler (zic) = tzdata binary package olson db + parse_olsen translator = DateTime::TimeZone official CPAN source package = Debian source package Debian source package + pbuilder = Debian binary package The Debian source package is based on official CPAN package and contains already parsed database which is provided by original author. I did the same work as upstream author, so I called parse_olsen translator and I've got the path for new Debian source package. Of course it builds our Debian binary package correctly. -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
volatile.debian.org: Does Debian still support it?
The Debian volatile archive is the place for packages that expires before new Debian release. The description perfectly fits for my package libdatetime-timezone-perl. I prepared a few weeks ago new releases for sarge and etch. The release is based on old packages which have refreshed just timezone data, based on Olson Database. The API is not change so it fits to Debian's philosophy of backporting changes to prevent breaking compability. I uploaded them a week ago and... nothing. After 30th of September the timezone data for New Zealand will be not correct (Bug#440258). The users who rely on Debian package will notice that something goes wrong. Please, tell me what should I do so I could see my package in volatile archive? I'm a little disappointed that I was just ignored. My packages are also available at http://people.debian.org/~dexter/volatile/ -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi Piotr, On Tue Sep 25, 2007 at 14:10:58 +0200, Piotr Roszatycki wrote: The Debian volatile archive is the place for packages that expires before new Debian release. The description perfectly fits for my package libdatetime-timezone-perl. I prepared a few weeks ago new releases for sarge and etch. The release is based on old packages which have refreshed just timezone data, based on Olson Database. The API is not change so it fits to Debian's philosophy of backporting changes to prevent breaking compability. I uploaded them a week ago and... nothing. how about answering to my mail[1]? Greetings Martin [1] http://lists.debian.org/debian-volatile/2007/09/msg5.html [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Ah... Do you mean this mail? am I missing something completely here? [EMAIL PROTECTED]:~/debian/packages$ diff -rNu libdatetime-timezone-perl-0.42-before-dv/ libdatetime-timezone-perl-0.42 | diffstat changelog|9 control |4 packages |2 patches/001-AKST9AKDT_timezone.patch | 11 patches/010-tzdata2007g.patch|38814 +++ patches/012-tzdata2007g-tests.patch | 21 patches/020-AKST9AKDT_timezone.patch | 11 rules|4 update-tzdata.sh | 30 9 files changed, 38890 insertions(+), 16 deletions(-) What is your question exactly? Do you mean, the patch is too large or what? Can you clarify, what do you really want to ask? The package is perfectly correct and the only difference is updated timezone database plus the shell script debian/update-tzdata.sh which I used for updating plus updated test units for new database. 2007/9/25, Martin Zobel-Helas [EMAIL PROTECTED]: Hi Piotr, On Tue Sep 25, 2007 at 14:10:58 +0200, Piotr Roszatycki wrote: The Debian volatile archive is the place for packages that expires before new Debian release. The description perfectly fits for my package libdatetime-timezone-perl. I prepared a few weeks ago new releases for sarge and etch. The release is based on old packages which have refreshed just timezone data, based on Olson Database. The API is not change so it fits to Debian's philosophy of backporting changes to prevent breaking compability. I uploaded them a week ago and... nothing. how about answering to my mail[1]? Greetings Martin [1] http://lists.debian.org/debian-volatile/2007/09/msg5.html [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Piotr Roszatycki wrote: After 30th of September the timezone data for New Zealand will be not correct (Bug#440258). The users who rely on Debian package will notice that something goes wrong. Based on the description (and not the patch) it seems to me that this kind of change should be in the next etch point release. SRMs? Regards, Faidon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Tue Sep 25, 2007 at 14:55:47 +0200, Piotr Roszatycki wrote: Ah... Do you mean this mail? am I missing something completely here? [EMAIL PROTECTED]:~/debian/packages$ diff -rNu libdatetime-timezone-perl-0.42-before-dv/ libdatetime-timezone-perl-0.42 | diffstat changelog|9 control |4 packages |2 patches/001-AKST9AKDT_timezone.patch | 11 patches/010-tzdata2007g.patch|38814 +++ patches/012-tzdata2007g-tests.patch | 21 patches/020-AKST9AKDT_timezone.patch | 11 rules|4 update-tzdata.sh | 30 9 files changed, 38890 insertions(+), 16 deletions(-) What is your question exactly? Do you mean, the patch is too large or what? Can you clarify, what do you really want to ask? The package is perfectly correct and the only difference is updated timezone database plus the shell script debian/update-tzdata.sh which I used for updating plus updated test units for new database. I don't understand why there is a patch of 38k lines needed to fix ONE SINGE timezone. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
It's not about one timezone. The new release refresh all available timezones. The whole package was synced with the latest Olson database. It is simple analogy for tzdata package. You should also ask, why the tzdata package has so many changes and why don't simply update only one timezone? 2007/9/25, Martin Zobel-Helas [EMAIL PROTECTED]: Hi, On Tue Sep 25, 2007 at 14:55:47 +0200, Piotr Roszatycki wrote: Ah... Do you mean this mail? am I missing something completely here? [EMAIL PROTECTED]:~/debian/packages$ diff -rNu libdatetime-timezone-perl-0.42-before-dv/ libdatetime-timezone-perl-0.42 | diffstat changelog|9 control |4 packages |2 patches/001-AKST9AKDT_timezone.patch | 11 patches/010-tzdata2007g.patch|38814 +++ patches/012-tzdata2007g-tests.patch | 21 patches/020-AKST9AKDT_timezone.patch | 11 rules|4 update-tzdata.sh | 30 9 files changed, 38890 insertions(+), 16 deletions(-) What is your question exactly? Do you mean, the patch is too large or what? Can you clarify, what do you really want to ask? The package is perfectly correct and the only difference is updated timezone database plus the shell script debian/update-tzdata.sh which I used for updating plus updated test units for new database. I don't understand why there is a patch of 38k lines needed to fix ONE SINGE timezone. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
On Tue, Sep 25, 2007 at 05:36:03PM +0200, Piotr Roszatycki wrote: It's not about one timezone. The new release refresh all available timezones. The whole package was synced with the latest Olson database. It would be good if you fixed #416206, and used tzdata yourself. So that we only need to update 1 package in volatile. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
It is almost impossible. The DateTime::TimeZone is pure Perl library and can't use binary data from tzdata package. In fact, this library can be used on systems without libc6 and tzdata at all! You wrongly assume that tzdata package is more important than libdatetime-timezone-perl package. It can be true only for glibc based systems. Even tzdata package is compiled from the source data - the same data which is used for refreshing libdatetime-timezone-perl! 2007/9/25, Kurt Roeckx [EMAIL PROTECTED]: On Tue, Sep 25, 2007 at 05:36:03PM +0200, Piotr Roszatycki wrote: It's not about one timezone. The new release refresh all available timezones. The whole package was synced with the latest Olson database. It would be good if you fixed #416206, and used tzdata yourself. So that we only need to update 1 package in volatile. Kurt -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
On Tue, Sep 25, 2007 at 09:48:19PM +0200, Piotr Roszatycki wrote: It is almost impossible. The DateTime::TimeZone is pure Perl library and can't use binary data from tzdata package. In fact, this library can be used on systems without libc6 and tzdata at all! You wrongly assume that tzdata package is more important than libdatetime-timezone-perl package. It can be true only for glibc based systems. Even tzdata package is compiled from the source data - the same data which is used for refreshing libdatetime-timezone-perl! That it can be used on other systems that don't have tzdata doesn't mean it shouldn't try and use tzdata if it's available on Debian. The binary data in the tzdata should be easy to parse. See man tzfile(5). 2007/9/25, Kurt Roeckx [EMAIL PROTECTED]: On Tue, Sep 25, 2007 at 05:36:03PM +0200, Piotr Roszatycki wrote: It's not about one timezone. The new release refresh all available timezones. The whole package was synced with the latest Olson database. It would be good if you fixed #416206, and used tzdata yourself. So that we only need to update 1 package in volatile. Kurt -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
It is already such library called DateTime::TimeZone::Tzfile. It is not packaged yet, but... It is different story. We still talk about DateTime::TimeZone. Even if it should be replaced with newer, better and faster libraray, it is ALREADY in etch and sarge. The Debian supports the packages which do not really work for the full time of a stable release. The Volatile archive keeps them functional. The libdatetime-timezone-perl is one of such packages. I explained what changed in this package, why the changes are necessary and how I made this update. It perfectly fits to stable policy. It is backward compatible and only data are changed. Of course, the Perl code can also be a data, and this module is an adequate example. Users of my package would like to see the updated package which is supported by Debian. One of them even tested it before I uploaded it to Volatile incoming queue. I don't understand what is the point? Why do you think this package shouldn't go to Volatile? What do you propose as alternative? 2007/9/25, Kurt Roeckx [EMAIL PROTECTED]: On Tue, Sep 25, 2007 at 09:48:19PM +0200, Piotr Roszatycki wrote: It is almost impossible. The DateTime::TimeZone is pure Perl library and can't use binary data from tzdata package. In fact, this library can be used on systems without libc6 and tzdata at all! You wrongly assume that tzdata package is more important than libdatetime-timezone-perl package. It can be true only for glibc based systems. Even tzdata package is compiled from the source data - the same data which is used for refreshing libdatetime-timezone-perl! That it can be used on other systems that don't have tzdata doesn't mean it shouldn't try and use tzdata if it's available on Debian. The binary data in the tzdata should be easy to parse. See man tzfile(5). -- .''`.Piotr Roszatycki : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
Hi, On Tue Sep 25, 2007 at 17:36:03 +0200, Piotr Roszatycki wrote: It is simple analogy for tzdata package. You should also ask, why the tzdata package has so many changes and why don't simply update only one timezone? [EMAIL PROTECTED]:~% diff -rNu tzdata-2007b tzdata-2007f | diffstat africa | 16 asia | 56 +--- australasia| 24 +-- debian/changelog |9 ++ europe | 62 ++ leapseconds| 16 ++-- northamerica | 177 ++--- southamerica | 17 +++-- zone.tab | 10 +- 9 files changed, 289 insertions(+), 98 deletions(-) So where are 38k lines here, which changed? In general i have no problem to accept a package into volatile, if one can give me GOOD reasons, why all these changes are necessary. What i do not understand is, why tzdata has about 300 lines changed, while your package needs 38k lines changed to achive the same effect. Greetings Martin -- [EMAIL PROTECTED] /root]# man real-life No manual entry for real-life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volatile.debian.org: Does Debian still support it?
You made a subtle mistake. You checked the source package for tzdata
and the changes are really small. Then you checked the differences for
libdatetime-timezone-perl package, but this source package is already
compiled. You should check the difference between binary packages for
tzdata.
The real source data for DateTime::TimeZone is the same as for tzdata
source package. Then, the data is precompiled into Perl source. It
makes a Debian source package.
Did you really read this patch?
It contains the series of such differences:
diff -Nru DateTime-TimeZone-0.42/lib/DateTime/TimeZone/Africa/Addis_Ababa.pm
DateTime-TimeZone-0.42
--- DateTime-TimeZone-0.42/lib/DateTime/TimeZone/Africa/Addis_Ababa.pm
2006-02-20 16:45:58.000
+++ DateTime-TimeZone-0.42.2007g/lib/DateTime/TimeZone/Africa/Addis_Ababa.pm
2007-09-05 14:29:11
@@ -3,7 +3,7 @@
# DateTime::TimeZone module distribution in the tools/ directory
#
-# Generated from /tmp/3PactztUqR/africa. Olson data version 1
+# Generated from tzdata/africa. Olson data version 2007g
#
# Do not edit this file directly.
#
@@ -50,7 +50,7 @@
sub has_dst_changes { 0 }
-sub _max_year { 2016 }
+sub _max_year { 2017 }
sub _new_instance
{
If you multiply this chunk by 400 timezones, you can get 40K of patch.
Another patch changes test units so make test can be passed with new
data. Also I provided a shell script which precompiles tzdata source
into Perl source so updating is quite simplier.
As I sad previously, the timezones data are precompiled into Perl
source because this library runs on non-Linux platforms, too, and in
this case it has a meaning.
You just compared an apples with oranges.
I understand, it's not comfortable situation with updates, but this
library already exists, and is used by many Perl projects. I see you
proposed to replace this library with other, which doesn't provide own
timezone data, but it is too late and not possible just now.
2007/9/25, Martin Zobel-Helas [EMAIL PROTECTED]:
So where are 38k lines here, which changed?
In general i have no problem to accept a package into volatile, if one can
give
me GOOD reasons, why all these changes are necessary. What i do not understand
is, why tzdata has about 300 lines changed, while your package needs 38k lines
changed to achive the same effect.
--
.''`.Piotr Roszatycki
: :' :mailto:[EMAIL PROTECTED]
`. `' mailto:[EMAIL PROTECTED]
`-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
