[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Question about Build ID's

 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=280906
 
Apparently at least one mirror of /releases/staging is not updating its bits when
the timestamp / contents changes but the file name remains the same -- most
likely even after 8 days (!).
 
What I need now is some p2 tracing / logging that would allow me to identify
what mirror exactly provided the offending bundles such that we can then
understand why it doesn't update (and either fix the problem or exclude it
from mirroring).
 
Does such a logging / tracing facility exist?
 
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
 
 


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Donnerstag, 18. Juni 2009 16:39
To: Cross project issues
Subject: RE: [cross-project-issues-dev] Question about Build ID's

> I do favor a "clean build" of /staging ...

We do that each time.

To be exact, every "build" is completely clean. And whenever we promote to staging, the old content is deleted first.
And when we promote to /releases/galileo the old content is deleted first. If anyone sees anything to contradict this, please open a bug ... since it would be a bug.

I know we all look forward to the day we can be more incremental ... but, I don't think we are there yet.