Bugzilla – Full Text Bug Listing
| Summary: | two bundles have pack.gz problems in latest R build | ||
|---|---|---|---|
| Product: | [Tools] Orbit | Reporter: | David Williams <david_williams> |
| Component: | releng | Assignee: | Project Inbox <orbit.releng-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Project Inbox <orbit.releng-inbox> |
| Severity: | normal | ||
| Priority: | P3 | CC: | gunnar |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Gunnar, any thoughts? FYI, we use "Java 5" to do the -repack/pack and I use that to "verify" the jars and pack.gz files. This was an issue in last M build (at least), which makes sense, since should be same thing ... though where were other problems there, as well. I really need to automate this test! (opened bug 370005) FYI, the latest S build does not have this problem (S20120123151124) ... though appears the bundles have changed? Based on their qualifier: http://www.eclipse.org/downloads/download.php?r=1&file=/tools/orbit/downloads/drops/S20120123151124/repository/plugins/com.google.gwt.servlet_2.1.0.v201111291940.jar http://www.eclipse.org/downloads/download.php?r=1&file=/tools/orbit/downloads/drops/R20120119162704/repository/plugins/com.google.gwt.servlet_2.1.0.v20101206-1430.jar Maybe they were changed to avoid packing? :\ Found the bug where these _where_ fixed in Juno. Guess we "dropped the ball" on fixing for Indigo SR2. At this point, I don't plan to do anything (for Indigo) unless it causes someone problems. *** This bug has been marked as a duplicate of bug 364785 *** |
In previous R-builds, we never did produce the "pack.gz" version of the jars, in our orbit repo. Now we do (when we promote a build). I was just getting ready to announce R20120119162704 and thought I'd check my usual "verify" script, to make sure all were signed. All were signed ... but ... seems to be a problem with two pack.gz files. (log from script below). I think, in theory, p2 should handle this, and just use the jar instead ... but ... not good to have "bad data" in our repo. I am inclined to "release" anyway, and if we need to, we can always go back and surgically remove those two pack.gz files. But ... even if we do that, this sort of problem is usually caused by a pack200 -repack ("condidtioning") problem, so anyone would still have a problem using pack200 with the jar, and, perhaps, this is a case where the jars should not be packed200'd? (just signed?). I'll check some of our other repos (M and I) and see if a problem there ... or, if sunspots. = = = = = = com.google.gwt.servlet_2.1.0.v20101206-1430.jar.pack.gz: jarsigner: java.lang.SecurityException: SHA1 digest error for com/google/gwt/editor/ui/client/adapters/HasTextEditor.class exitcode: 1: com.google.gwt.servlet_2.1.0.v20101206-1430.jar.pack.gz com.google.gwt.user_2.0.4.v20100709-0658.jar.pack.gz: jarsigner: java.lang.SecurityException: SHA1 digest error for com/google/gwt/user/client/ui/FocusPanel.class exitcode: 1: com.google.gwt.user_2.0.4.v20100709-0658.jar.pack.gz