X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8CBE5385DC32
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=SystematicSw.ab.ca
Authentication-Results: sourceware.org;
 spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis: v=2.3 cv=ecemg4MH c=1 sm=1 tr=0
 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
 a=IkcTkHD0fZMA:10 a=yh-u-wC2zRQA:10 a=jChkm-x5hCMFubTIiR0A:9 a=QEXdDO2ut3YA:10
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Subject: Re: Current setup timestamp 1590343308
To: cygwin AT cygwin DOT com
References: <AM6PR03MB5282721443D5697079ED1A7CA4B30 AT AM6PR03MB5282 DOT eurprd03 DOT prod DOT outlook DOT com>
 <AM6PR03MB52829A197A09EEC21B735894A4B30 AT AM6PR03MB5282 DOT eurprd03 DOT prod DOT outlook DOT com>
Autocrypt: addr=Brian DOT Inglis AT SystematicSw DOT ab DOT 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: <1bf179b1-3490-53e9-4413-7379badb748c@SystematicSw.ab.ca>
Date: Mon, 25 May 2020 15:53:25 -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: <AM6PR03MB52829A197A09EEC21B735894A4B30@AM6PR03MB5282.eurprd03.prod.outlook.com>
Content-Language: en-CA
X-CMAE-Envelope: MS4wfIygPNkDhl6WzpTJSEbcdUU2728yWtlFH41Hqb3muMHyA/zlrUhXZIjAF950fi8IJIgEaApbaHsP57+Xq80zlnyaVRPG9rTZjr8pb8CJDC2+TIOMvGYV
 zZoCadpkRIa9jK713rInqcEtJLqWNrcVgPMCt2vAUOYVYil8Qn4cug9ZG5+cJLFWyIo7eYNT7KhwZA==
X-Spam-Status: No, score=-13.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,
 RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <http://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On 2020-05-25 14:14, Fergus Daly via Cygwin wrote:
> Fergus Daly said:
>>> What I have observed, twice now (earlier today using setup.ini incorporating timestamp 1590343308 and now using the latest setup.ini incorporating timestamp 1590407755) is that event (ii) is failing: the file /etc/setup/timestamp is not updated - and if it isn't there at all, it is not created.
> 
> Ken Brown said:
>>> I'm not seeing any change in behavior on my system.  I just deleted 
> /etc/setup/timestamp and ran setup.  A new /etc/setup/timestamp was created, 
> with contents 1590430423.  This matches the value in the downloaded setup.ini file:
>     setup-timestamp: 1590430423
> Do you see any error messages involving /etc/setup/timestamp in the setup log 
> files in /var/log?
> 
> And thank you for this. In a way I am encouraged that things remain as they should be for you and presumably for others, and that there's some kind of local glitch on my machine.
> It is trivially annoying, perplexing - and persistent! (I've just updated to 1590430423) with these consequences:
> Nothing at all relevant in /var/log/setup.log*:
> ~> grep timestamp /var/log/setup.log*
> ~>
> yields nothing. And
> ~> ls -altr /etc/setup/
> ends with
> ..
> ..
> -rw-r--r-- 1   404 May 22 09:39 perl-TimeDate.lst.gz
> -rw-r--r-- 1   629 May 22 09:39 mintty.lst.gz
> -rw-r--r-- 1    11 May 25 17:10 timestamp
> -rw-r--r-- 1 16283 May 25 20:45 installed.db
> -rw-r--r-- 1    64 May 25 20:45 setup.rc
> showing that the last update that actually altered my provision - not the full offering by any means - took place on May 22. The timestamp file at time 17:10 today is an artificial creation with the contents 1580000000 so that tracking is easy. The update to 1590430423 occurred at 20:45 today and revised only two of the three files that would normally be updated - /etc/setup/timestamp has not changed.
> .. .. ??!!
> As I say - perplexing.
> Fergus 
> (And /etc/setup/timestamp should update, even when there's no change to a user's provision. It always has, until today.)
> Thanks anyway.

Is the difference whether set-x86/_64 option "-g, --upgrade-also Upgrade
installed packages also" is specified or not?
That option is built into my setup script in case install dependencies need
upgraded, and as the default if no install is requested.
I only run setup manually to install downgrades, tests, or when version formats
change.

-- 
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.]

-- 
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