X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D7ED8389200A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1590425244;
	bh=Py7qXhSAkSL1pC/td0591nqhrFk08AXhNcOQfzL+nuk=;
	h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post:
	 List-Help:List-Subscribe:From:Reply-To:From;
	b=vNJhYhpsfYupn+SUlapY6LCfxFrdbb8qcvq5XMIlawLUv3zkX4lrb1xYg7Ae/CQv0
	 KjqG9dUdwp+LFp3CXGnMEa1pe3XOXkFGdazxuOFam3LTFTkK5sb9WzFtxTtSwB5QLG
	 ILZwDYcyxJDdV0YYLS6UxhD3iqgsX16gk320dp5E=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2DFDA388A824
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=mwjPstlptgLsThPVgBLOwC0TNLLv+TyoKuE7wTKsxL8auhNO4Yf9CAs3eZM2+KunESUSq0EX+bgAwc4+reX39kUzR4xdK0xcS1HCKKH2Z1fKDcHKZxkm882lJrQdUX4jOe2oY3gywTwwYdRdzSgM5qFxZVoRfk7xpmQokp+Z6ItL8V0sEbKQd3Po/ln3XmOhD4bPnxRrCHQEDkGM2tR+JFLfLyIiA30drf9/FtY9SPD2qOgpnmvnaBR0XoOlyaMhvAWXR3lzAAdqdDAhso+lNfTm+OjNEg/l2pRKh5S1+sf/iN89xZdS54GdJeLLEOtvGtZOKAP7PTt2JqyXCq9jwg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; 
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=SQIrTmfTZwGBppYOU1QVnj9U06f4FGFnRGFwNqej4+k=;
 b=XSzVnWITIimjJC4fhr3Ohwot0oSm/dLPih9AQ3XqqpmDNl/TTT19f770qsrl29mcvEtxzjotA8UqBLqBD95G6TAsuP6so825CB+IgLvdiX3+kw/txxN8tiFHVVUZFBjRIuko7JwYQsmaUGxOh0U2QSiETcJuczsCoIM02PwxMKKNLVCHCppAhxawI0z+CjIYsH0jhFi7tLar5YeS1CLkNkcsaG77TJE4SoXj5dr6uWjvQLfN501OXArjHPtFHiq+tjrtmdgfQCVZX8tUTX/qqSn7hfv8hiT6NQpnNjYAwJiVu3KfNpMfw42PhMEPLl2kW+3ax7O6lmH11rtXNdr5sg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none;
 dkim=none; arc=none
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Re: Current setup timestamp 1590343308
Thread-Topic: Re: Current setup timestamp 1590343308
Thread-Index: AdYys9UFxPgPF0ICSw2Vo7c/1+kz4w==
Date: Mon, 25 May 2020 16:47:18 +0000
Message-ID: <AM6PR03MB5282721443D5697079ED1A7CA4B30@AM6PR03MB5282.eurprd03.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:2F2FC3AA0F733EAFD929A2FC2EEF19568EA9FFE7C65B2D66B9328707D05875D6;
 UpperCasedChecksum:8940EC299635E25E9BCB884E4B53D30081DE146974CDF6CEA001A92A153C2C8D;
 SizeAsReceived:6680; Count:42
x-tmn: [EOpsb5dK2syAuhf1soyofL9Omh89nNz0]
x-ms-publictraffictype: Email
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 378b5fff-e45f-43cb-6914-08d800cb49a1
x-ms-traffictypediagnostic: DB3EUR04HT055:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Np6sv/NLX8YGgll+5eYAEfiWpv1Ad2EegS1tcoUZMUXu0N6CyAeL1cUFOus7ia0hEBzfKTzhNBxOZ4Zxm4rjpX+0a3xbyg1oV9HEnGTfi33XZra8CRq7xXwviImdibbBxdn/hVtc8Ql6SLrNw973rQp0XbhzMA4wkrCkxmjjQOpUxAY5SFXeSPNwxT9kniQGoYYnKp4ebiJklHl9WIwc/Q==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:0; SRV:;
 IPV:NLI; SFV:NSPM; H:AM6PR03MB5282.eurprd03.prod.outlook.com; PTR:; CAT:NONE;
 SFTY:; SFS:; DIR:OUT; SFP:1901; 
x-ms-exchange-antispam-messagedata: ReqRCyscV42vSmCngDpPlb4nWVUgbn/fCaxn7GcNpsGorKYqvwtZBboDEBU81gqz3bxnzOoekWCh7/mUueLArS5+9fZe95UYpni4d+m/SDJr22ew2to8zYQDHs6xijP3hswCqwEfMQ+//zIVVittMg==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 378b5fff-e45f-43cb-6914-08d800cb49a1
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 May 2020 16:47:18.5491 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3EUR04HT055
X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT,
 FREEMAIL_FROM, KAM_NUMSUBJECT, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,
 SPF_HELO_PASS, SPF_PASS, 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
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
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>
From: Fergus Daly via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Fergus Daly <fergusd84 AT outlook DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

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

Thank you for this.
I can't really think of anything to say other than repeat my observation, today, of altered practice.
Since as long as I can remember (and I mean - a matter of years) a successful upgrade of Cygwin32
(implementing the current version of setup-x86.exe currently 2.904
and pulling in the latest version of setup.ini found at {source}/Cygwin/x86/)
has concluded with
(i) a glitch-free accounting in /var/log/setup.log(.full), together with
(ii) a revision of the file /etc/setup/timestamp
which reflects the timestamp line in the aforementioned setup.ini file.
(And other things too, quite apart from any updates to the Cygwin provision - e.g. an updated /etc/setup/installed.db file.)

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.

Maybe this does not matter. The file is not referred to during any upgrade session  (or not obviously - I think the contents of /etc/setup/installed.db are what dictate any necessary upgrades to an individual user's Cygwin provision) but it has been, for me at least, a useful rapid check of whether "what I've got" matches "what is now available". 

All I was trying to do was draw attention to (what I perceive to be) suddenly altered practice, with no change to the setup executable that might have explained it or caused it. So (a) is it a real change? (easily confirmed, or not, by anybody with /etc/setup/timestamp reporting < 1590407755 then running an upgrade, and seeing what happens to /etc/setup/timestamp); and (b) if so, is it intended? or is it a trivial glitch introduced goodness-knows-how that can be corrected; and (c) if intended, to provide what improvement? because it seems to me a bad move.

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