From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR06-VI1-obe.outbound.protection.outlook.com (mail-vi1eur06olkn2090.outbound.protection.outlook.com [40.92.17.90]) by sourceware.org (Postfix) with ESMTPS id 7D929385DC32 for ; Mon, 25 May 2020 20:14:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7D929385DC32 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WG4+9vOJ/XKAdvHXSc1SMuodXjogC/+r3cylPVRipIgpTADVWxQHaUm32BAeqrTmGaTmA4rbpGAnsVnVj5rAX9SPluR7gdF/H/0VWY63tvBOTg/hLf4CQuDfSR9txRzT2rteTCaTITVhdIzg9Q5eIwFHzJR4v5fSXiE2qKqJdSE2u2XCUK3vb1QKlBx5DRdnnCznyccnNWYdXMOx4DpaY/lMd/WrATcQ3jVz6wbGHXNqnYuj9kGz65GrQKd7zFYQjUH4IKJ23xH7KDINTE7MfBHXoosrD9cHYUOuF4Eu38iCFvqg+xVthb7N7eYnBpWQUgPkto/8U44wq1DwiJLPNw== 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=R/MKwFPDX33qhuHYPR0lB2tZ1LosQsHsq30VOpVowVs=; b=MkjqouY3l1cHgVLR/awjyAx4R3Fg4CJiLOgxm1XZtirnBmaW7r3EDmrYNY1SoEzZei84deMlhTixpL9dyj7SS6Spfmi9YWoLzPsvNpj/Y2xASY+m1vKeJ8etNbInHJ1OjlP5cJvHcEryfIm4ZJN0GUPwVj9/yeTHtqv3q+cObnvn289/ZfILLpq/UhyG88jRT5jnqox8sWUCvwCFbNLtnb+k69QAoZkUAlI7cLpb3vTLsNwQSjKGITDFsNHT4jXuA89DqHt/ul+xHHQiQgscAUNDiouILq58WBmUv0emyxVgTsz3SuTojK2e6qk5emU/kSILEhZeEM0A59nAtjVEjw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none Received: from VI1EUR06FT047.eop-eur06.prod.protection.outlook.com (2a01:111:e400:fc37::46) by VI1EUR06HT048.eop-eur06.prod.protection.outlook.com (2a01:111:e400:fc37::258) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23; Mon, 25 May 2020 20:14:21 +0000 Received: from AM6PR03MB5282.eurprd03.prod.outlook.com (2a01:111:e400:fc37::52) by VI1EUR06FT047.mail.protection.outlook.com (2a01:111:e400:fc37::271) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23 via Frontend Transport; Mon, 25 May 2020 20:14:21 +0000 Received: from AM6PR03MB5282.eurprd03.prod.outlook.com ([fe80::309d:77fb:eb7d:4637]) by AM6PR03MB5282.eurprd03.prod.outlook.com ([fe80::309d:77fb:eb7d:4637%5]) with mapi id 15.20.3021.029; Mon, 25 May 2020 20:14:21 +0000 From: Fergus Daly To: "cygwin@cygwin.com" Subject: RE: Re: Current setup timestamp 1590343308 Thread-Topic: Re: Current setup timestamp 1590343308 Thread-Index: AdYys9UFxPgPF0ICSw2Vo7c/1+kz4wAGiEPw Date: Mon, 25 May 2020 20:14:20 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:34419D04A79CEE17E1CECB9A8A7EAE66E734B69C0160D7E228CB5763F76EDAE5; UpperCasedChecksum:F8A11B08F31B9CF07267DF13C7099D2F780F64DDFC27048B07F6F69CA05C7B93; SizeAsReceived:6871; Count:44 x-tmn: [At9SRQkU/1yNmY6IvsCzujLslp5pJBCh] x-ms-publictraffictype: Email x-incomingheadercount: 44 x-eopattributedmessage: 0 x-ms-office365-filtering-correlation-id: e7c52439-b9dd-4a24-acfb-08d800e83610 x-ms-traffictypediagnostic: VI1EUR06HT048: x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 96YWywBh/dXxdUNAGkdZM31VysCus68WA/XS1Wb6RP4vVxQk9bjg3nCe3Pl7qz2wAtGA+OXi0O1QparA9IHUa73JoJaXKfkhN3B8axNbQRO6BUCOjY6x5z9xvxMSbZQmxklwUnEnKNAeiAKVTiO9ZDsTi1UHGSB2tIZWlVzhkcuRR0MDVHiKj869ZG+vSnp1kjtw2wyr0FmUOnSYOVItaw== 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: UNj50rXxE5JEq56JcDQwFXc51xIQTv9q3QQScdKGFVHdRmw8NZwIeyBov2wjIv7owntV+/B+nVjxk6HN4Qius4DtnKG5wC5zeYnQlsVrvS+HXeVgdQyyYCrkNpPs0VASP1ds+FxUU+FfWroNeTklIg== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: e7c52439-b9dd-4a24-acfb-08d800e83610 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 25 May 2020 20:14:21.2070 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1EUR06HT048 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2020 20:14:24 -0000 Fergus Daly said: >> What I have observed, twice now (earlier today using setup.ini incorpora= ting timestamp 1590343308 and now using the latest setup.ini incorporating = timestamp 1590407755) is that event (ii) is failing: the file /etc/setup/ti= mestamp 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=20 /etc/setup/timestamp and ran setup. A new /etc/setup/timestamp was created= ,=20 with contents 1590430423. This matches the value in the downloaded setup.i= ni file: setup-timestamp: 1590430423 Do you see any error messages involving /etc/setup/timestamp in the setup l= og=20 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 t= o 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 f= ull offering by any means - took place on May 22. The timestamp file at tim= e 17:10 today is an artificial creation with the contents 1580000000 so tha= t tracking is easy. The update to 1590430423 occurred at 20:45 today and re= vised only two of the three files that would normally be updated - /etc/set= up/timestamp has not changed. .. .. ??!! As I say - perplexing. Fergus=20 (And /etc/setup/timestamp should update, even when there's no change to a u= ser's provision. It always has, until today.) Thanks anyway.