[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-releng-dev] request for rebuild of 4.2.1/3.8.1
|
This seems like a good idea.
While these changes are safe, the auto-tagging will result in new qualifiers for all bundles (which were affected by this changes). From a p2 standpoint, we may suddenly need to download bundles that otherwise haven't changed. Moreover, if these were the only changes since SR0, the service segment may not have been updated to reflect this change and that might be more problematic (We have a new release with a new qualifier and the same major, minor, service numbers). This might be overly pedantic since the content should otherwise be the same.
+1 for commenting out if that will indeed lock the tags.
Cheers,
Ian
On Fri, Sep 14, 2012 at 11:50 AM, David M Williams
<david_williams@xxxxxxxxxx> wrote:
Good question. Previous in week, we all
said for emergency rebuild teams would have to provide an "respin
branch" that was exactly equal to what was in previous build.
But ... now that I think about it ...
I think I can "comment out" lines in repositories.txt and it
will simply use exactly what was in the map files previously?
Sounds easier/safer?
Date:
09/14/2012 02:43 PM
Subject:
Re: [platform-releng-dev]
request for rebuild of 4.2.1/3.8.1
Sent by:
platform-releng-dev-bounces@xxxxxxxxxxx
The p2 team (and I assume others, since we were all asked
to do this) have pushed several CBI changes to the R3_8 branch. These
should be "safe" changes since they were isolated to POM files
which are not used by the current releng infrastructure. However, these
are changes to the input repository. Do we plan on re-spinning the
build based off the last tags (with the exception of SWT), or are we ok
with these changes?
Cheers,
Ian
On Fri, Sep 14, 2012 at 11:31 AM, Grant Gayed <Grant_Gayed@xxxxxxxxxx>
wrote:
SWT is requesting a rebuild of 4.2.1/3.8.1
in order to address the two bugs below. These were previously targeted
for 4.2.2 but are needed sooner.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=381407
: reproducible crash in Debug's Variables view
https://bugs.eclipse.org/bugs/show_bug.cgi?id=383890:
JVM (Eclipse) crash with SIGSEGV in ld-linux-x86-64.so.2
The changes have been pushed, we're ready to go.
Grant
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com |
http://twitter.com/eclipsesource
