From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: Current setup timestamp 1590343308
Date: Mon, 25 May 2020 12:26:41 +0000 [thread overview]
Message-ID: <AM6PR03MB528242CB105256EB8A3E2EE1A4B30@AM6PR03MB5282.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <CAB8Xom9-MSd9PsrzQpGu=SZiPjxVYyx4rmTQa3QYdVGh3HtyRg@mail.gmail.com>
-----Original Message-----
From: marco atzeri [mailto:marco.atzeri@gmail.com]
Sent: 25 May 2020 13:13
To: Fergus Daly
Cc: cygwin@cygwin.com
Subject: Re: Current setup timestamp 1590343308
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.
> Fergus
> --
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.
Fergus
(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.)
next prev parent reply other threads:[~2020-05-25 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 12:02 Fergus Daly
2020-05-25 12:13 ` marco atzeri
2020-05-25 12:26 ` Fergus Daly [this message]
2020-05-25 13:12 ` Brian Inglis
2020-05-25 16:47 Fergus Daly
2020-05-25 19:12 ` Ken Brown
2020-05-25 20:14 ` Fergus Daly
2020-05-25 21:52 ` Brian Inglis
2020-05-25 21:53 ` Brian Inglis
2020-05-27 9:10 Fergus Daly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM6PR03MB528242CB105256EB8A3E2EE1A4B30@AM6PR03MB5282.eurprd03.prod.outlook.com \
--to=fergusd84@outlook.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).