<br><br><div><span class="gmail_quote">On 10/10/07, <b class="gmail_sendername">Stephen Worthington</b> <<a href="mailto:stephen_agent@jsw.gen.nz">stephen_agent@jsw.gen.nz</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, 09 Oct 2007 21:03:51 +1300, you wrote:<br><br>>Stephen Worthington wrote:<br>>> In the end, I waited for the official package update. I could have<br>>> downloaded the source files, once I had worked out what and where they
<br>>> were. But since the package update was promised for a few days later<br>>> I did not bother. But I do not like to be dependent on someone out<br>>> there preparing packages in a timely manner. I like to be able to do
<br>>> it myself. And all of this seems overkill compared to a TZ string,<br>>> which used to work fine for me. I am sure there were reasons for<br>>> doing all of this, but the big problem I had was the usual one with
<br>>> Linux - the detailed documentation is there, once you find it, but the<br>>> things that get you to finding it are usually either completely<br>>> missing or sadly lacking. I should be able to just look up the master
<br>>> help system and find a pointer to the timezone settings immediately.<br>>><br>>So which distro were you waiting for?<br>><br>>All of the distro's were kept waiting because of the size of NZ, and for
<br>>Debian the fixes are still only in Debian-volatile which is a real<br>>problem. AU has a change in April and it will be interesting to see if<br>>they react quicker for a bigger country.<br>><br>>Steve
<br><br>If the maintainers are committed to the timezone system they have at<br>present, then they have to ensure that the timezone updates are done<br>as soon as the new daylight saving setups become law. Our changes<br>
were officially announced on 30-Apr-07. Instead, they seem to wait<br>until there is little time left, perhaps thinking that there might be<br>further changes. So there ends up being little leeway for any of the<br>inevitable problems to be worked out. Microsoft seems to be just as
<br>bad - at work the IT people had real problems ensuring that the server<br>end of things worked properly, and they really only had less than a<br>month to work on it. I doubt it will be any better for AU changes,<br>unless the Aussies do it for themselves.
</blockquote><div><br><br>I agree that the maintainers should have fixed it, as indeed they did if you read the bug report pointed to by the later poster. Apparently debian's volatile repo is meant for volatile data like tzdata, and thats where you get it. Its well known that debian stable doesn't get changed except for security fixes.
<br><br>But this isn't the place to discuss it, i doubt you will change debian policy by discussing it here.<br><br>Also there have been fixes floating around various NZ Linux mailing lists for months. They worked for me.
<br><br><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">_______________________________________________<br>mythtvnz mailing list
<br><a href="mailto:mythtvnz@lists.linuxnut.co.nz">mythtvnz@lists.linuxnut.co.nz</a><br><a href="http://lists.ourshack.com/mailman/listinfo/mythtvnz">http://lists.ourshack.com/mailman/listinfo/mythtvnz</a><br>Archives <a href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/">
http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a><br></blockquote></div><br>