From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] file dates on system totally bodged
Date: Mon, 2 Jan 2006 09:45:25 +0000 [thread overview]
Message-ID: <20060102094525.09423f21@krikkit.digimed.co.uk> (raw)
In-Reply-To: <7bef1f890601011657xa050126n9e418ebb3a76d9cb@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Mon, 2 Jan 2006 10:57:00 +1000, Alan E. Davis wrote:
> Over a period of a week or so, while I was celebrating the holidays,
> my system experienced a hardware hiccough, causing system
> clock/hardware clock time to change to 2020. The upshot is that a
> bunch of merges, a kernel compile, and various other system components
> have files that are way out of date.
>
> I have experimentally touched some files with the current date and
> time.
Changing dates manually will confuse portage, which keeps track of the
datestamps of all files it installs. The upshot is that it will no
remove files where the dates have changed. The safest method of correcting
the dates would be to re-emerge the affected packages. Use genlop --list
--date XXX to see which you installed during the problem period, then
emerge them all with the --oneshot option.
--
Neil Bothwick
If at first you don't succeed, call it Windows NT.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-02 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 0:57 [gentoo-user] file dates on system totally bodged Alan E. Davis
2006-01-02 9:45 ` Neil Bothwick [this message]
2006-01-02 12:14 ` Alan E. Davis
[not found] ` <20060102133207.00a242e5@krikkit.digimed.co.uk>
2006-01-02 14:10 ` Alan E. Davis
2006-01-03 3:44 ` Alan E. Davis
2006-01-03 9:32 ` Neil Bothwick
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=20060102094525.09423f21@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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