DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 59244386F41D
Subject: Re: Current setup timestamp 1590343308
To: cygwin@cygwin.com
References: <AM6PR03MB5282721443D5697079ED1A7CA4B30@AM6PR03MB5282.eurprd03.prod.outlook.com>
Message-ID: <e50f08be-12fb-f4ca-d49d-df58d3310a23@cornell.edu>
Date: Mon, 25 May 2020 15:12:16 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
In-Reply-To: <AM6PR03MB5282721443D5697079ED1A7CA4B30@AM6PR03MB5282.eurprd03.prod.outlook.com>
Content-Language: en-US
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.0.17] (68.175.129.7) by
 BL1PR13CA0045.namprd13.prod.outlook.com (2603:10b6:208:257::20) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.13 via Frontend
 Transport; Mon, 25 May 2020 19:12:21 +0000
X-Originating-IP: [68.175.129.7]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: e20f368c-ce82-4e06-0af2-08d800df8d0b
X-MS-TrafficTypeDiagnostic: DM6PR04MB5659:
X-Microsoft-Antispam-PRVS: <DM6PR04MB56595AFA4B274E1A79244B46D8B30@DM6PR04MB5659.namprd04.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 0414DF926F
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: jvj6r26iwxuDIjzBRDyg644aUjDZHQF677YvwV5Sw8NKV1kew6Gmn/4RR0ZxmLcJ6bffYh60JDfWFWCbz+2pzfJilUrqq/HdUoY6l8Jh5b5ycx48+xxT8c5Xso1s69WAd+YdGIU9tEQmvQUk5tg0qLYcYzJQpYvg7oEhNMhbgFR/HFzLN9amslMnqdPKgo5aaZgKDIazcaKH0eWW88awlMucZKJ/0tLrcCFEn1aofZNQjKnWPhrW0x2ctbUiiLvVaJfsedu13pZOMCDnhX9yr6xYoJmoJ/8DkJ7QdayUuTy+0QsvXBo6oROh7jf6j2N4zYakPIKfGmN3yyXxyjgvEkqL/Vz/UG1o+ahmtQ//THjN3jp4CQGP//Hvn7+rfl/tsAwdTN7gxIUE4ErdqAOkrtoSPIoCIh1HWffTdYCM28c=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;
 IPV:NLI; SFV:NSPM; H:DM6PR04MB6075.namprd04.prod.outlook.com; PTR:; CAT:NONE;
 SFTY:;
 SFS:(4636009)(136003)(346002)(39860400002)(376002)(396003)(366004)(66946007)(66476007)(66556008)(31696002)(8936002)(31686004)(86362001)(6486002)(956004)(7116003)(2616005)(478600001)(26005)(6666004)(36756003)(6916009)(75432002)(5660300002)(16526019)(53546011)(16576012)(2906002)(316002)(8676002)(52116002)(186003)(786003)(43740500002)(460985005);
 DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: l9VefQMn4ABgn+hfKGyJxCSSwYKSJQY4dOsZp9EMbfJ9um0Y8hFSSlmLh8+hq2Ud4C+IAlagSd34mUuld+UaNXDFKUPNagda0uQuLkpgpPeDVgMXlTQfotYhoJS4zf6nCj98xb9+/5jiqeeubqb3PM77ThIssTmWn4u0y54Lg1HVNn06yCf7So6z5KjM3YeKm0y7O6nz+1kfsn7xiHUhM0Ulm1li/ouKEhgOh12f84KnkCkBnDRM7yoD9nqNJRHgUJPi8meueoS5tMcBfnK0YhBD3l12cwBfk1wqc+nia976p4zrtBdRCE5xUj7rh12y6+B8voGqMPlDZoNKpRiXgp3D02NDTXR7Ov3BIaPkckuKrSNdhotkiSzxBFTb0F42SAZ/Y0/0l3Rv2fKNPMR7pXGeLi0YWzqlsBCQv6lP0+93VwzGN41TZTvVecKi07mHlYpjOQWqMxitra37ltcC2+trthjrW5BJJqYcUfyN0Rw=
X-OriginatorOrg: cornell.edu
X-MS-Exchange-CrossTenant-Network-Message-Id: e20f368c-ce82-4e06-0af2-08d800df8d0b
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 May 2020 19:12:22.1630 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5d7e4366-1b9b-45cf-8e79-b14b27df46e1
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: sVqS0YEFeqn1P/8jnViLJnKr1R3BqYudJzF6LpJJ6gmXfWJrrff6J/Ancl6vT0deSBT/6wfnouvVbwLBU7Q+yQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR04MB5659
X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT,
 MSGID_FROM_MTA_HEADER, 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 <cygwin.cygwin.com>
List-Unsubscribe: <http://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Ken Brown via Cygwin <cygwin@cygwin.com>
Reply-To: Ken Brown <kbrown@cornell.edu>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

On 5/25/2020 12:47 PM, Fergus Daly via Cygwin wrote:
>>> 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.

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?

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