DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8201E3851C05
Subject: Re: Current setup timestamp 1590343308
To: cygwin@cygwin.com
References: <AM6PR03MB52821DAA9328A9C455EBAFC3A4B30@AM6PR03MB5282.eurprd03.prod.outlook.com>
 <CAB8Xom9-MSd9PsrzQpGu=SZiPjxVYyx4rmTQa3QYdVGh3HtyRg@mail.gmail.com>
 <AM6PR03MB528242CB105256EB8A3E2EE1A4B30@AM6PR03MB5282.eurprd03.prod.outlook.com>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Autocrypt: addr=Brian.Inglis@SystematicSw.ab.ca; prefer-encrypt=mutual;
 keydata=
 mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0
 LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA
 PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW
 AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO
 WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB
 BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5
 /lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF
 IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5
 RSyTY8X+AQ==
Organization: Systematic Software
Message-ID: <f853383e-3dec-3f06-a40d-32ba600062c7@SystematicSw.ab.ca>
Date: Mon, 25 May 2020 07:12:22 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <AM6PR03MB528242CB105256EB8A3E2EE1A4B30@AM6PR03MB5282.eurprd03.prod.outlook.com>
Content-Language: en-CA
Precedence: list
Reply-To: cygwin@cygwin.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>


On 2020-05-25 06:26, Fergus Daly via Cygwin wrote:
> On 25 May 2020 13:13, marco atzeri wrote:
>> On Mon, May 25, 2020 at 2:08 PM Fergus Daly via Cygwin wrote:

>>> Current setup timestamp 1590343308
>>> does not seem to overwrite /etc/setup/timestamp accurately (or at all).
>>> I think /etc/setup/installed.db is seen to as it should be.

>> What exactly is your problem ?
>> Be verbose we can NOT guess your thoughts.
>> 
>> Unix time: seconds since Jan 01 1970. (UTC)
>> https://www.unixtimestamp.com/index.php

> Sorry for lack of clarity.
> Cygwin32.
> Current installed timestamp 1590341902 (got from /etc/setup/timestamp).
> I noticed there's a newer setup.ini with timestamp 1590343308.
> So I ran setup-x86.exe.
> After a (presumed) successful run I noticed however, that the file
> /etc/setup/timestamp had not altered.
> "Presumed successful run" because the file /etc/setup/installed.db had a
> new, current, timestamp.

> (I deleted /etc/setup/timestamp and re-running setup-x86.exe to see whether 
> any self-correcting behaviour would ensue. The file was not recovered.)
It looks to me that /etc/setup/timestamp is updated by the last successful setup
(upgrade?) run, and contains a copy of the selected mirror's setup.ini
setup_timestamp field as of the last successful setup (upgrade?) run, a few
hours earlier than the last successful setup (upgrade?) run.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple