emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#26039: closed (libical / tzdata substitution not w


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#26039: closed (libical / tzdata substitution not working)
Date: Mon, 13 Mar 2017 00:55:02 +0000

Your message dated Sun, 12 Mar 2017 20:53:58 -0400
with message-id <address@hidden>
and subject line Re: libical / tzdata substitution not working
has caused the debbugs.gnu.org bug report #26039,
regarding libical / tzdata substitution not working
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
26039: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26039
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: libical / tzdata substitution not working Date: Thu, 9 Mar 2017 13:46:38 -0500 User-agent: Mutt/1.8.0 (2017-02-23)
Since libical was updated to 2.0.0, the tzdata path substition has had
no effect due to changes in the upstream source code. [0]

So, libical probably can't find the time zone file, and it doesn't keep
a reference to tzdata.

I assume it needs to be fixed? But what is the impact, if we never
noticed? :)

[0] Commit 2b193389d243c469e159d0ab5dfc86b5867db05d, only two days after
the substitution was added.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: libical / tzdata substitution not working Date: Sun, 12 Mar 2017 20:53:58 -0400 User-agent: Mutt/1.8.0 (2017-02-23)
On Thu, Mar 09, 2017 at 01:46:38PM -0500, Leo Famulari wrote:
> Since libical was updated to 2.0.0, the tzdata path substition has had
> no effect due to changes in the upstream source code. [0]
> 
> So, libical probably can't find the time zone file, and it doesn't keep
> a reference to tzdata.
> 
> I assume it needs to be fixed? But what is the impact, if we never
> noticed? :)
> 
> [0] Commit 2b193389d243c469e159d0ab5dfc86b5867db05d, only two days after
> the substitution was added.

Fixed in be81133a13932bc83b0697d73581a47674ef6987, although I'd still
like to investigate the impact of this bug.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]