zdump --version reports "unknown" on OpenSuse 15.1 [2020a]
Hi all, when checking the timezone database version on my OpenSuse 15.1 Linux, I do not get the expected result. hayo@computer:~> sudo zdump --version zdump (tzcode) unknown Installed package: timezone - Time Zone Descriptions Is this a defect of the OpenSuse package or of the IANA code distribution? Regards, Hayo More Details ------------ Technical data: Installierte Version 2020a-lp151.2.9.1 Mo 18 Mai 2020 10:13:45 CEST Sa 23 Mai 2020 20:03:30 CEST System/Base BSD-3-Clause AND SUSE-Public-Domain 1,1 MiB 0 B openSUSE Leap 15.1 openSUSE http://bugs.opensuse.org x86_64 http://www.iana.org/time-zones timezone-2020a-lp151.2.9.1 0 File list: /etc/localtime /usr/bin/tzselect /usr/sbin/zdump /usr/sbin/zic /usr/share/zoneinfo ... Change log: Fr 24 Apr 2020 14:00:00 CEST Marketa Calabkova <mcalabkova@suse.com> - timezone update 2020a (bsc#1169582) * Morocco springs forward on 2020-05-31, not 2020-05-24. * Canada's Yukon advanced to -07 year-round on 2020-03-08. * America/Nuuk renamed from America/Godthab. * zic now supports expiration dates for leap second lists.
On 5/24/20 4:38 AM, listclient@hayo.de wrote:
sudo zdump --version zdump (tzcode) unknown
Installed package: timezone - Time Zone Descriptions
Is this a defect of the OpenSuse package or of the IANA code distribution?
If you aren't sure, then the answer is "OpenSuse". :-) I suggest filing a bug report with the OpenSuse folks. For what it's worth, on Ubuntu 18.04.4 'zdump --version' outputs "zdump (Ubuntu GLIBC 2.27-3ubuntu1) 2.27" and on Fedora 31 it outputs "zdump (GNU libc) 2.30".
Am 24.05.20 um 19:19 schrieb Paul Eggert:
On 5/24/20 4:38 AM, listclient@hayo.de wrote:
sudo zdump --version zdump (tzcode) unknown
Installed package: timezone - Time Zone Descriptions
Is this a defect of the OpenSuse package or of the IANA code distribution?
If you aren't sure, then the answer is "OpenSuse". :-)
I suggest filing a bug report with the OpenSuse folks.
opensuse.org and new suse.com both are currently migrating user accounts. In short: I cannot log in to the Suse-Bugzilla. That is why the maintainer from Suse was and is addressed by this thread. M. Calabkova, please take care of this bug.
For what it's worth, on Ubuntu 18.04.4 'zdump --version' outputs "zdump (Ubuntu GLIBC 2.27-3ubuntu1) 2.27" and on Fedora 31 it outputs >"zdump (GNU libc) 2.30".
I expected this result. Thanks for your support. Regards, Hayo
On 2020-05-24 19:19, Paul Eggert wrote:
On 5/24/20 4:38 AM, listclient@hayo.de wrote:
sudo zdump --version zdump (tzcode) unknown
Installed package: timezone - Time Zone Descriptions
Is this a defect of the OpenSuse package or of the IANA code distribution?
If you aren't sure, then the answer is "OpenSuse". :-)
indeed :) I found out we were re-making a 'version' file (because of patches)
I suggest filing a bug report with the OpenSuse folks. For what it's worth, on Ubuntu 18.04.4 'zdump --version' outputs "zdump (Ubuntu GLIBC 2.27-3ubuntu1) 2.27" and on Fedora 31 it outputs "zdump (GNU libc) 2.30".
after fixing the issue above on my computer I get: $ sudo zdump --version zdump (tzcode) 2020a This is different from other distros. Is there any other bug in openSUSE? It looks like the other distros take version info from the last used compiler... Is this correct? Greetings, Marketa
On 2020-05-25 17:22:05 (+0800), mcalabkova wrote:
On 2020-05-24 19:19, Paul Eggert wrote:
On 5/24/20 4:38 AM, listclient@hayo.de wrote:
sudo zdump --version zdump (tzcode) unknown
Installed package: timezone - Time Zone Descriptions
Is this a defect of the OpenSuse package or of the IANA code distribution?
If you aren't sure, then the answer is "OpenSuse". :-)
indeed :) I found out we were re-making a 'version' file (because of patches)
I suggest filing a bug report with the OpenSuse folks. For what it's worth, on Ubuntu 18.04.4 'zdump --version' outputs "zdump (Ubuntu GLIBC 2.27-3ubuntu1) 2.27" and on Fedora 31 it outputs "zdump (GNU libc) 2.30".
after fixing the issue above on my computer I get:
$ sudo zdump --version zdump (tzcode) 2020a
This is different from other distros. Is there any other bug in openSUSE? It looks like the other distros take version info from the last used compiler... Is this correct?
On FreeBSD and macOS, `zdump --version` returns the version of the zdump program, respectively: zdump: @(#)zdump.c 8.10 (FreeBSD) zdump: @(#)zdump.c 7.31 (macOS) Arguably, your update to OpenSUSE is more useful! Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Date: Mon, 25 May 2020 17:31:27 +0800 From: "Philip Paeps" <philip@trouble.is> Message-ID: <56C8137B-FD4F-4F58-B5AF-E7A0AB4FC549@trouble.is> | On FreeBSD and macOS, `zdump --version` returns [...] On NetBSD (-current) netbsd# zdump --version zdump (tzcode) 2019b (we don't update tzcode all that frequently, tzdata on the other hand is 2020a) kre
On Mai 25 2020, mcalabkova wrote:
after fixing the issue above on my computer I get:
$ sudo zdump --version zdump (tzcode) 2020a
This is different from other distros. Is there any other bug in openSUSE? It looks like the other distros take version info from the last used compiler...
You could set PACKAGE from %distribution, similar to what binutils and gdb do. Also, it would be good to set BUGEMAIL. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
On 2020-05-25 11:50, Andreas Schwab wrote:
On Mai 25 2020, mcalabkova wrote:
after fixing the issue above on my computer I get:
$ sudo zdump --version zdump (tzcode) 2020a
This is different from other distros. Is there any other bug in openSUSE? It looks like the other distros take version info from the last used compiler...
You could set PACKAGE from %distribution, similar to what binutils and gdb do. Also, it would be good to set BUGEMAIL.
I have tried it (I have also set it to print a real package name) and I got: $ sudo zdump --version zdump (timezone; Base:System) 2020a (Base:System is the repository in which I locally build the package.) I personally dislike it, after reading the discussion I would stay with simple tzcode (the previous result). I will set BUGEMAIL to opensuse-support@opensuse.org, thanks. Hayo, are you satisfied with this solution? Greetings, Marketa
Am 25.05.20 um 14:20 schrieb mcalabkova:
On 2020-05-25 11:50, Andreas Schwab wrote:
On Mai 25 2020, mcalabkova wrote:
after fixing the issue above on my computer I get:
$ sudo zdump --version zdump (tzcode) 2020a
This is different from other distros. Is there any other bug in openSUSE? It looks like the other distros take version info from the last used compiler...
You could set PACKAGE from %distribution, similar to what binutils and gdb do. Also, it would be good to set BUGEMAIL.
I have tried it (I have also set it to print a real package name) and I got:
$ sudo zdump --version zdump (timezone; Base:System) 2020a
(Base:System is the repository in which I locally build the package.)
I personally dislike it, after reading the discussion I would stay with simple tzcode (the previous result).
I will set BUGEMAIL to opensuse-support@opensuse.org, thanks.
Hayo, are you satisfied with this solution?
Marketa, from the perspective of the OpenSuse user I am fully satisfied with the solution. In fact I expected 'sudo zdump --version' to return the database version. But the man page is unspecific in its description.
From the perspective of the zdump user, the current situation is not that good. I think all distributions should return similar output. And the output should contain the tzdata version. Only that way it is possible to evaluate the output in portable scripts.
Proposal (for a future version >2020a): $ sudo zdump --version zdump (GLIBC 2.28) - tzdata 2020c
Greetings, Marketa
Greetings, Hayo
On 5/25/20 5:49 AM, listclient@hayo.de wrote:
From the perspective of the zdump user, the current situation is not that good. I think all distributions should return similar output. And the output should contain the tzdata version.
That's not what the --version flag is for. --version is supposed to output the version number of the program, not of any data. This is the common meaning of "--version" across a wide variety of programs. Many distributions update tzcode (the source code for zdump) more rarely than tzdata, and it's helpful to keep the two version numbers distinct in that case. zdump is intended to be portable to any system that conforms to POSIX, and since there's no POSIX-portable way to find out the tzdata version, zdump doesn't do that. There might not be any tzdata at all, and zdump is still supposed to work. Though perhaps this zdump design goal should change at some point....
On May 28, 2020, at 12:23 AM, Paul Eggert <eggert@cs.ucla.edu> wrote:
That's not what the --version flag is for. --version is supposed to output the version number of the program, not of any data. This is the common meaning of "--version" across a wide variety of programs.
Yes. For example, the GNU coding standard says of --version: https://www.gnu.org/prep/standards/standards.html#g_t_002d_002dversion "The standard --version option should direct the program to print information about its name, version, origin and legal status, all on standard output, and then exit successfully."
zdump is intended to be portable to any system that conforms to POSIX, and since there's no POSIX-portable way to find out the tzdata version, zdump doesn't do that. There might not be any tzdata at all, and zdump is still supposed to work. Though perhaps this zdump design goal should change at some point....
And if there *were* a POSIX-portable way to find out the tzdata version, zdump should, *if* there's tzdata from which to find the version using the POSIX-portable way in question, have a *different* flag, e.g. --tzdata-version, to tell it to report that version.
On 2020-05-25 03:22, mcalabkova wrote:
On 2020-05-24 19:19, Paul Eggert wrote:
On 5/24/20 4:38 AM, listclient@hayo.de wrote:
sudo zdump --version zdump (tzcode) unknown
Installed package: timezone - Time Zone Descriptions
Is this a defect of the OpenSuse package or of the IANA code distribution?
If you aren't sure, then the answer is "OpenSuse". :-)
indeed :) I found out we were re-making a 'version' file (because of patches)
I suggest filing a bug report with the OpenSuse folks. For what it's worth, on Ubuntu 18.04.4 'zdump --version' outputs "zdump (Ubuntu GLIBC 2.27-3ubuntu1) 2.27" and on Fedora 31 it outputs "zdump (GNU libc) 2.30".
after fixing the issue above on my computer I get:
$ sudo zdump --version zdump (tzcode) 2020a
This is different from other distros. Is there any other bug in openSUSE? It looks like the other distros take version info from the last used compiler... Is this correct?
A number of distros do not use tzcode directly, but have their own release, based on their libc TZ and locale handling, applying patches based on tzcode patches, or based on BSD to allow use and inclusion in commercial or proprietary products, often RT or embedded systems for microcontrollers, with tailored support for data, functionality, size. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in IEC units and prefixes, physical quantities in SI.]
participants (8)
-
Andreas Schwab -
Brian Inglis -
Guy Harris -
listclient＠hayo.de -
mcalabkova -
Paul Eggert -
Philip Paeps -
Robert Elz