Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 25286 - incorect lithuanian time zone
Summary: incorect lithuanian time zone
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: Highest blocker (vote)
Assignee: Gentoo's Team for Core System packages
URL: http://www.b4net.lt/%7Emgedmin/ltz/in...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-25 16:15 UTC by roma1390
Modified: 2004-11-23 00:49 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
lithuanian timezone file and source (ltz2003.tar.gz,3.53 KB, application/gzip)
2003-08-18 12:00 UTC, Mindaugas Tamosevicius
Details

Note You need to log in before you can comment on or make changes to this bug.
Description roma1390 2003-07-25 16:15:11 UTC
Accordind http://www.b4net.lt/%7Emgedmin/ltz/index-en.html lithuanian time zone
must be EEST, but on last stable libc 2.3.2-r1 we have EET. 

Reproducible: Always
Steps to Reproduce:
1.install gentoo
2.ln -sf /usr/share/zoneinfo/Europe/Vilnius /etc/localtime
3.date

Actual Results:  
Sat Jul 26 02:13:59 EET 2003


Expected Results:  
Sat Jul 26 02:13:59 EEST 2003


none
Comment 1 Mindaugas Tamosevicius 2003-08-18 12:00:07 UTC
Created attachment 16289 [details]
lithuanian timezone file and source 

There is a correct lithuanian (Europe/Vilnius) timezone file with source and
description, shamessly copied from the given URL
(http://mg.b4net.lt/ltz/index-en.html).
Comment 2 Martin Holzer (RETIRED) gentoo-dev 2003-09-05 10:04:43 UTC
sorry this can't be a  blocker
Comment 3 roma1390 2003-09-09 00:50:35 UTC
It can be.

p.s.
simply situation:
reading gentoo install inctruction && instaling gentoo.
when user == local == lt -> system timezone && time is incorect.

Comment 4 roma1390 2003-12-07 10:39:02 UTC
if you have some interes on my gnump3d-1.0-r0.ebuild

# diff -Naur /usr/portage/media-sound/gnump3d/gnump3d-1.0.ebuild gnump3d/gnump3d-1.0-r0.ebuild

--- /usr/portage/media-sound/gnump3d/gnump3d-1.0.ebuild 2003-03-11 23:11:46.000000000 +0200
+++ gnump3d/gnump3d-1.0-r0.ebuild       2003-07-26 14:51:43.000000000 +0200
@@ -1,6 +1,6 @@
 # Copyright 1999-2003 Gentoo Technologies, Inc.
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /home/cvsroot/gentoo-x86/media-sound/gnump3d/gnump3d-1.0.ebuild,v 1.6 2003/03/11 21:11:46 seemant Exp $
+# $Header: /home/cvsroot/gentoo-x86/media-sound/gnump3d/gnump3d-1.0.ebuild,v 1.5 2003/02/14 08:52:13 vapier Exp $
 
 inherit eutils
 
@@ -14,13 +14,15 @@
 IUSE="oggvorbis"
 
 DEPEND="virtual/glibc"
-RDEPEND=">=dev-lang/perl-5.6.1
-       oggvorbis? ( media-libs/libvorbis )"
+#RDEPEND=">=sys-devel/perl-5.6.1
+#      oggvorbis? ( media-libs/libvorbis )"
+RDEPEND="oggvorbis? ( media-libs/libvorbis )"
 
 src_unpack() {
        unpack ${A}
        cd ${S}
        epatch ${FILESDIR}/${P}-gentoo.diff.bz2
+       epatch ${FILESDIR}/${P}-server.diff.bz2
 }
 
 src_compile() {
Comment 5 roma1390 2003-12-07 10:41:26 UTC
sorry wrong bug id
Comment 6 roma1390 2003-12-14 13:41:19 UTC
please do something
Comment 7 Ed Grimm 2004-01-30 00:30:12 UTC
If this is a blocker, then what bugids is it blocking?  They should be listed in the 'bug 25286 blocks' section, right above the additional comments block.  That is, unless gentoo is not using bugzilla in the manner in which it is intended to be used - normally, blocker is only for those bugs that block another bug, and frequently only if that other bug is either high priority or critical.

My experience is that bugs which are politically misclassified tend to be worked on at a much slower pace than they otherwise would be - the workers *know* that the bug isn't that important, and therefore they ignore it.  But when they get to working on stuff of the importance level that it is, they don't realize it; they've forgotten about it other than their subconscious block.

Note that it has apparently been fixed, as of the latest gentoo release.  This bug should probably be closed, so that those of us who are actually interested in helping out can find what bugs there actually are to work on.
Comment 8 SpanKY gentoo-dev 2004-01-30 02:31:09 UTC
the meaning of the severity differs widely from user/dev

it's more of a field that the developer may or may not use to prioritize their own workload

personally, i never use Priority or Severity ... never have looked at the things, never will ;)
Comment 9 SpanKY gentoo-dev 2004-01-30 02:31:35 UTC
could you define 'the latest gentoo release' ?
what version of glibc ?  does glibc-2.3.2-r9 fix it ?
Comment 10 Ed Grimm 2004-01-31 17:54:04 UTC
I am currently in the process of installing gentoo linux for the first time.  (Given that I'm a pedant, especially about my Linux installs, it's going to take a while.  It normally does.)  The files were most likely from the stage file, ftp://oss.redundant.com/pub/gentoo/releases/x86/1.4/stages/x86/stage1-x86-20030910.tar.bz2.  (I'm sure other locations have the same data.  I'm only giving the full url to be exacting in my specification of exactly what I'm using.  I am, after all, a pedant.)

glibc has nothing to do with it; if it did, then everyone would be complaining about daylight savings time not working.  It's the zoneinfo file (/usr/share/zoneinfo/EET); this is part of the stage file.

Actually, given that it is in the stage file, I don't know how this file would update for regular gentoo users, unless it's handled by the general update feature.
Comment 11 roma1390 2004-02-01 07:01:32 UTC
1. zone file is part of glibc

<shell># epm -qf /usr/share/zoneinfo/Europe/Vilnius 
glibc-2.3.2-r3

<shell># ls -l /etc/localtime 
lrwxrwxrwx    1 root     root           34 Mar  8  2026 /etc/localtime -> /usr/share/zoneinfo/Europe/Vilnius

2. upgrading glibc
<shell># emerge -p glibc

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild     U ] sys-libs/glibc-2.3.2-r9 [2.3.2-r3] 

<shell># emerge glibc
....

<shell># date --date 'jul 1 2003'
Tue Jul  1 00:00:00 EEST 2003

Every thing is ok. Problem is solved in 2.3.2-r3. Bug can be closed.