From the tz-list: The files... ftp://elsie.nci.nih.gov/pub/tzdata2006b.tar.gz ...and... ftp://elsie.nci.nih.gov/pub/tz32code2006b.tar.gz ...and... ftp://elsie.nci.nih.gov/pub/tz64code2006b.tar.gz ...are now available. The files... ftp://elsie.nci.nih.gov/pub/classictzcode.tar.gz ...and... ftp://elsie.nci.nih.gov/pub/classictzdata.tar.gz ...have been removed. The 32-bit code is there for folks who may need it; with providence, there will be little or no need to update it. The 64-bit code reflects the changes circulated earlier on the time zone mailing list. Both the 32-bit code and the 64-bit code share the same data. All SCCS IDs were bumped to "8.1" for this release.
i dont get it ... whats the diff between tz32code2006b.tar.gz and tz64code2006b.tar.gz ? should we just use tz64code2006b.tar.gz on all hosts whether it be 32bit or 64bit ?
(In reply to comment #1) > i dont get it ... whats the diff between tz32code2006b.tar.gz and > tz64code2006b.tar.gz ? tz32 is the code that produces 32bit tz data and tz64 is the one that produces 64 bit tz data. Both work on the same tzdata2006b.tar.gz file. tz64 is the newer one (obviously). > should we just use tz64code2006b.tar.gz on all hosts > whether it be 32bit or 64bit ? Yeah. tz64 should be used everywhere (32 bit and 64 bit machines).
thanks for the info, 2006b ebuild now in portage
tz64code results in an install failure on my AthlonXP here. I've modded the ebuild to use tz32code and it installs fine now. So maybe tz64code is not valid for 32-bit machines? The error I was getting w/ tz64 was - >>> Install timezone-data-2006b into /var/tmp/portage/timezone-data-2006b/image/ category sys-libs ./zic -y ./yearistype -d /var/tmp/portage/timezone-data-2006b/image//usr/share/zoneinfo -L /dev/null africa antarctica asia australasia europe northamerica southamerica pacificnew etcetera factory backward systemv solar87 solar88 solar89 ./zic: wild compilation-time specification of zic_t make: *** [posix_only] Error 1 !!! ERROR: sys-libs/timezone-data-2006b failed. Call stack: ebuild.sh, line 1894: Called dyn_install ebuild.sh, line 1037: Called src_install !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant.
i doubt it ... fedora is using just the 64bit version for all their hosts
(In reply to comment #4) > tz64code results in an install failure on my AthlonXP here. I've modded the > ebuild to use tz32code and it installs fine now. > I'm getting the same error and am also using an AMD Athlon-XP. How do I "mod" the ebuild? Spanky ?? I've found several things that work on FC and not on Gentoo, and visa versa.
(In reply to comment #5) > i doubt it ... fedora is using just the 64bit version for all their hosts > Well, that was the only change I made, and it works, so... At first I thought it was the recent coreutils 5.94 /bin/expr problem again, but apparently not. Maybe then there is some other issue with this.
(In reply to comment #6) > (In reply to comment #4) > > tz64code results in an install failure on my AthlonXP here. I've modded the > > ebuild to use tz32code and it installs fine now. > > > > I'm getting the same error and am also using an AMD Athlon-XP. > > How do I "mod" the ebuild? > > Spanky ?? > I've found several things that work on FC and not on Gentoo, and visa versa. > cd /usr/portage/sys-libs/timezone-data edit timezone-data-2006b.ebuild change the file d/l in row 11 to tz32 instead of tz64 save changes ebuild timezone-data-2006b.ebuild digest It should d/l the tz32 file, then try emerge again.
file a new bug
(In reply to comment #9) > file a new bug > Done. http://bugs.gentoo.org/show_bug.cgi?id=123778
thanks
