Current timestamp

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Current timestamp

Fergus Daly-5
Looked at several mirror sites just this minute (1435 GMT Aug 16).
All showing setup.ini with setup-timestamp 1502381207 (Aug 10) whereas
most recent update seems to have been stamped 1502735714 (Aug 14).

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: Current timestamp

David Stacey
On 16/08/17 15:35, Ugly Leper wrote:
> Looked at several mirror sites just this minute (1435 GMT Aug 16).
> All showing setup.ini with setup-timestamp 1502381207 (Aug 10) whereas
> most recent update seems to have been stamped 1502735714 (Aug 14).

This appears to be affecting x86 only, where setup.ini is timestamped
2017-08-10. For x86_64, setup.ini is dated 2017-08-14.

This isn't a mirroring issue, as I'm seeing this on sourceware.

Jon: Is calm running correctly for x86?

Dave.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: Current timestamp

Jon TURNEY
On 16/08/2017 19:26, David Stacey wrote:

> On 16/08/17 15:35, Ugly Leper wrote:
>> Looked at several mirror sites just this minute (1435 GMT Aug 16).
>> All showing setup.ini with setup-timestamp 1502381207 (Aug 10) whereas
>> most recent update seems to have been stamped 1502735714 (Aug 14).
>
> This appears to be affecting x86 only, where setup.ini is timestamped
> 2017-08-10. For x86_64, setup.ini is dated 2017-08-14.
>
> This isn't a mirroring issue, as I'm seeing this on sourceware.
>
> Jon: Is calm running correctly for x86?

sourceware.org is having some fallout from a hardware upgrade (see [1]).

Some things got restored from backup.  Work is ongoing.

[1] https://www.sourceware.org/ml/overseers/2017-q3/msg00060.html

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: Current timestamp

cyg Simple
On 8/16/2017 3:38 PM, Jon Turney wrote:

> On 16/08/2017 19:26, David Stacey wrote:
>> On 16/08/17 15:35, Ugly Leper wrote:
>>> Looked at several mirror sites just this minute (1435 GMT Aug 16).
>>> All showing setup.ini with setup-timestamp 1502381207 (Aug 10) whereas
>>> most recent update seems to have been stamped 1502735714 (Aug 14).
>>
>> This appears to be affecting x86 only, where setup.ini is timestamped
>> 2017-08-10. For x86_64, setup.ini is dated 2017-08-14.
>>
>> This isn't a mirroring issue, as I'm seeing this on sourceware.
>>
>> Jon: Is calm running correctly for x86?
>
> sourceware.org is having some fallout from a hardware upgrade (see [1]).
>
> Some things got restored from backup.  Work is ongoing.
>
> [1] https://www.sourceware.org/ml/overseers/2017-q3/msg00060.html
>

Oh here is the original announcement!  This should have been a bigger
announce with its own subject and thread.

--
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple