Den 05/31/2013 05:13 PM, skrev Milan Crha:
Oops, thinking of it, I believe any 3.8.x, not only 3.8.3 on which I
tested this, has this fixed, thus you can pick whichever 3.8.x you've
available.
Bye,
Milan
Hello Milan (and all of you who helped me).
I can confirm that Evolution 3
On 31 May 2013 08:17, David Woodhouse wrote:
> On Fri, 2013-05-31 at 06:47 -0430, Patrick O'Callaghan wrote:
> > On Fri, 2013-05-31 at 10:10 +0100, David Woodhouse wrote:
> > > > let's call it UTC, not GMT, to have same terminology as in RFC.
> > >
> > > I sometimes like to use 'GMT' just to rein
On Fri, 2013-05-31 at 16:50 +0200, Milan Crha wrote:
> On Fri, 2013-05-31 at 11:15 +0200, Vidar Evenrud Seeberg wrote:
> > Is it possible to get hold of 3.8.3 currently?
>
> The release is planned on June 10th (or around it, if anything urgent
> will rise). I would rather wait, than try to compile
On Fri, 2013-05-31 at 11:15 +0200, Vidar Evenrud Seeberg wrote:
> Is it possible to get hold of 3.8.3 currently?
The release is planned on June 10th (or around it, if anything urgent
will rise). I would rather wait, than try to compile from git.
Bye,
Milan
___
On Fri, 2013-05-31 at 06:47 -0430, Patrick O'Callaghan wrote:
> On Fri, 2013-05-31 at 10:10 +0100, David Woodhouse wrote:
> > > let's call it UTC, not GMT, to have same terminology as in RFC.
> >
> > I sometimes like to use 'GMT' just to reinforce the "GMT does *not*
> > mean UK time" message. :)
On Fri, 2013-05-31 at 10:10 +0100, David Woodhouse wrote:
> > let's call it UTC, not GMT, to have same terminology as in RFC.
>
> I sometimes like to use 'GMT' just to reinforce the "GMT does *not*
> mean UK time" message. :)
It's certainly true that GMT is not the same as UK time, but even GMT
Den 05/31/2013 10:46 AM, skrev Milan Crha:
Hi, I just tested this with to-be 3.8.3 and it works fine there, thus
I guess it got fixed "unintentionally", between your 3.4.4 and the
3.8.x. Once you get to 3.8.x evolution(-ews), and purge your local
cache of events, then they'll be redownloaded a
Den 05/31/2013 10:56 AM, skrev David Woodhouse:
Remember, times are meaningless without timezones. You should *always*
specify the timezone unless it's completely obvious.
The meeting was at 20:00 in *what* time zone? I thought it was at 20:00
in your local time zone, GMT+2. Which makes it 18:0
On Fri, 2013-05-31 at 09:27 +0200, Milan Crha wrote:
> On Thu, 2013-05-30 at 22:49 +0100, David Woodhouse wrote:
> > > DTSTART:20130602T18
> > > DTEND:20130602T19
> >
> > Hm, that's odd. Shouldn't those end with a 'Z' to indicate that they are
> > in GMT? Then they'd be correct, right? The
[cut]
> Trying to do it right this time... :)
[cut]
Well, it didn't work out. Like Pete Biggs wrote - you should delete all
irrelevant citations/quotations. This one which you are reading now, is
an example how it should look like.
--
Patryk "LeadMan" Benderz
Linux Registered User #377521
() asc
On Fri, 2013-05-31 at 09:09 +0200, Vidar Evenrud Seeberg wrote:
> Den 05/30/2013 11:49 PM, skrev David Woodhouse:
> > DTSTART:20130602T18
> > DTEND:20130602T19
> > Hm, that's odd. Shouldn't those end with a 'Z' to indicate that they are
> > in GMT? Then they'd be correct, right? The meeting
On Fri, 2013-05-31 at 09:51 +0200, Vidar Evenrud Seeberg wrote:
> Is it enough to say that evolution-ews doesn't
> recognize UTC and describe how I enter events in phone, sync to Exchange
> and starts Evolution?
Hi,
I just tested this with to-be 3.8.3 and it works fine there, thus I
gues
Den 05/31/2013 09:34 AM, skrev Milan Crha:
...while it knows about the other time zones. Nice, in that case discard
my note about lazy phone software, and make this an evolution-ews bug.
Thanks for all the investigation here.
No problem. I am the one to thank you, guys. I have learn't a lot abo
On Fri, 2013-05-31 at 09:09 +0200, Vidar Evenrud Seeberg wrote:
> UTC
Heh, so evolution-ews doesn't recognize UTC...
> (UTC+01.00) Brussel, København, Madrid, Paris
...while it knows about the other time zones. Nice, in that case discard
my note about lazy phone software, and make this an evol
On Thu, 2013-05-30 at 22:49 +0100, David Woodhouse wrote:
> > DTSTART:20130602T18
> > DTEND:20130602T19
>
> Hm, that's odd. Shouldn't those end with a 'Z' to indicate that they are
> in GMT? Then they'd be correct, right? The meeting was actually at 18:00
> GMT?
Hi,
let's call it
Den 05/30/2013 11:49 PM, skrev David Woodhouse:
Hope I am posting correctly now...
The EWS_DEBUG part worked, but searching for the event entered on the
phone gave no results. Here is the event, entered for 20:00 on the
phone, but drifted two hours to 18:00:
BEGIN:VCALENDAR
PRODID:-//Ximian//NON
On Thu, 2013-05-30 at 21:06 +0200, Vidar Evenrud Seeberg wrote:
> Den 05/30/2013 08:51 AM, skrev evolution-list-requ...@gnome.org:
> >
> > Hi,
> > it might be better to start with evolution itself, not with your admins.
> > I suggest to debug what the server returns to you. One UI way is to ope
Den 05/30/2013 08:51 AM, skrev evolution-list-requ...@gnome.org:
Hi,
it might be better to start with evolution itself, not with your admins.
I suggest to debug what the server returns to you. One UI way is to open
the event editor and turn on View->Time zone, then you'll see what time
On Thu, 2013-05-30 at 09:17 +0100, Tom Davies wrote:
> Annoyingly some email clients and all handheld devices make it
> impossible to bottom post so i usually either avoid posting or delete
> out all the previous stuff so that no-one has any context.
We have plenty of context. The In-Reply-To: an
On Thu, 2013-05-30 at 09:17 +0100, Tom Davies wrote:
> Hi :)
> Yes, Milan's advice is much better. I hadn't seen it before i posted :(
>
>
> Wrt mailing lists this one is quite strict and if you get used to this one it
> stands you in good stead with all the other projects. Annoyingly some e
Hi :)
Yes, Milan's advice is much better. I hadn't seen it before i posted :(
Wrt mailing lists this one is quite strict and if you get used to this one it
stands you in good stead with all the other projects. Annoyingly some email
clients and all handheld devices make it impossible to bott
On Thu, 2013-05-30 at 06:51 +, evolution-list-requ...@gnome.org
wrote:
> Message: 6
> Date: Wed, 29 May 2013 20:01:44 +0100 (BST)
> From: Tom Davies
> To: "evolution-list@gnome.org"
> Subject: Re: [Evolution] Time drifting using Android - Exchange 2010 -
>
On Thu, 2013-05-30 at 06:51 +, evolution-list-requ...@gnome.org
wrote:
> Message: 4
> Date: Wed, 29 May 2013 16:10:06 +0200
> From: Milan Crha
> To: evolution-list@gnome.org
> Subject: Re: [Evolution] Time drifting using Android - Exchange 2010 -
> Evol
Hi :)
I had a problem with all the Windows machines on the company network being 10
minutes off. Only booting machines into Ubuntu gave the correct time.
I think it turned out to be something to do with the Windows Server
authentication (Kerberos?) whereas all the Ubuntu machines only have l
On Wed, 2013-05-29 at 08:55 +0200, Vidar Evenrud Seeberg wrote:
> Den 05/29/2013 04:05 AM, skrev evolution-list-requ...@gnome.org:
> > Date: Tue, 28 May 2013 18:32:01 -0430
> > From: Patrick O'Callaghan
> > To: evolution-list@gnome.org
> > Subject: Re: [Evolut
On Wed, 2013-05-29 at 12:35 +0200, Vidar Evenrud Seeberg wrote:
> Thank you. Comforting to see that it is not just me Our Exchange
> server is 2010 and the timezone for the server is UTC+1 + summertime,
> which altogether should be summarized to my computers and my phone's +2
> timezone. I will
On Wed, 2013-05-29 at 09:48 +, evolution-list-requ...@gnome.org
wrote:
>
>
>
>
>
>
>
>
>
>
>
> Date: Wed, 29 May 2013 09:06:06 +0200
> From: Patryk Benderz
> To: evolution-list@gnome.org
> Subject: Re: [Evolution] Time drifting using
>
> When entering appointments/events on my phone (using either SPlanner
> or Touchdown) the appointments drift with two hours when picked up by
> Evolution. If entering an appointment from 10:00 to 11:00 on the
> phone, it shows up in Evolution from 8:00 to 9:00. This is how I do it
> (for repro
> Post looks great. Check differences between OS and BIOS time set on
> each machine, including phone, however last one may not be trivial.
> I do not know Evolution code handles setting appointment incoming from
> different sources, but I imagine some parts of code may check OS time,
> > When you say it "drifts" do you mean it's exactly 2 hours off, or that
> > it varies by up to 2 hours?
> It is always off by two hours (which is the "offset" from timezone 0.)
> >
> > Do all the various components agree on the timezone and the current
> > time? I.e. if the Windows machine says
[cut]
> Now, trying again!
[cut]
Post looks great. Check differences between OS and BIOS time set on
each machine, including phone, however last one may not be trivial.
I do not know Evolution code handles setting appointment incoming from
different sources, but I imagine some part
Den 05/29/2013 04:05 AM, skrev evolution-list-requ...@gnome.org:
Date: Tue, 28 May 2013 18:32:01 -0430
From: Patrick O'Callaghan
To: evolution-list@gnome.org
Subject: Re: [Evolution] Time drifting using Android - Exchange 2010 -
Evolution
Message-ID: <1369782121.5
On Tue, 2013-05-28 at 22:15 +0200, Vidar Evenrud Seeberg wrote:
> When entering appointments/events on my phone (using either SPlanner
> or Touchdown) the appointments drift with two hours when picked up by
> Evolution. If entering an appointment from 10:00 to 11:00 on the
> phone, it shows up in
Hello again!
I have posted this question before. However I was not used to
communicating using mailing lists, so I screwd up the whole issue. Now,
trying again!
My Linux computer:
Linux Mint DE, Update Pack 6 (latest)
TimeZone Europe/Oslo, which currently means +2, summer time
Time synchroniz
34 matches
Mail list logo
