From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sstate.bbclass: preserve time when unstaging files
Date: Mon, 29 Oct 2012 20:00:00 +0100 [thread overview]
Message-ID: <lymwz5gl3j.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1351534747.2828.34.camel@ted> (Richard Purdie's message of "Mon, 29 Oct 2012 18:19:07 +0000")
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
>> >> But the real bug is the time mismatch in the autobuilders, isn't it?
>> >> And this can/should be solved by synchronizing time by ntp on them
>> >> instead of applying dirty hacks like resetting file dates.
>> ...
>> > Worse, when this does happen the failures are extremely unpredictable
>> > and hard to debug. It causes things to repeatedly recompile for example,
>> > even during do_install.
> ...
> Set the date stamp of some headers in the target sysroot of some key
> system components (say glib) to a date about a day in the future,
Are there really packages which create files dated in the future?
Perhaps a sanity check should be written which rejects files which are
newer than their containing directory and/or the time-of-day?
> then clean and rebuild some software that uses glib.
How will 'tar -m' fix this? It makes things just worse because the
files generated with -m are always newer than without -m (in practice,
time offset between hosts served by ntp is far below 100ms. which is
enough for the build stages doing the sstage file extraction).
Enrico
next prev parent reply other threads:[~2012-10-29 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 15:11 [PATCH] sstate.bbclass: preserve time when unstaging files Enrico Scholz
2012-10-29 16:11 ` Richard Purdie
2012-10-29 16:24 ` Enrico Scholz
2012-10-29 17:22 ` Richard Purdie
2012-10-29 17:59 ` Enrico Scholz
2012-10-29 18:19 ` Richard Purdie
2012-10-29 19:00 ` Enrico Scholz [this message]
2012-10-29 21:20 ` Richard Purdie
2012-10-29 21:41 ` Enrico Scholz
2012-10-29 21:55 ` Richard Purdie
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=lymwz5gl3j.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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