Bugzilla – Full Text Bug Listing
| Summary: | i can't use the update (mile stones update site) anymore since M6->M7 and now M7->M8 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Johan Compagner <jcompagner> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | pascal |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Johan Compagner
Sounds like a duplicate of bug 340165. Does it always stop at the same plug-in? Are you able to tell which mirror it is trying to get the plug-in from? that really sounds like the same thing. They tell also over there that the disabled mirrors, how can i do that? But it seems to download now over and over again this: http://download.eclipse.org/eclipse/updates/3.7milestones/S-3.7M7-201104280848/plugins/org.eclipse.equinox.p2.publisher.eclipse_1.0.0.v20110419-0147.jar.pack.gz if i download that file my self, then unpack it: D:\download>unpack200 org.eclipse.equinox.p2.publisher.eclipse_1.0.0.v20110419-0147.jar.pack.gz org.eclipse.equinox.p2.p ublisher.eclipse_1.0.0.v20110419-0147.jar then verify it: D:\download>jarsigner -verify org.eclipse.equinox.p2.publisher.eclipse_1.0.0.v20110419-0147.jar jar verified. Warning: This jar contains unsigned entries which have not been integrity-checked. This jar contains entries whose certificate chain is not validated. Re-run with the -verbose and -certs options for more details. D:\download>jarsigner -verbose -verify org.eclipse.equinox.p2.publisher.eclipse_1.0.0.v20110419-0147.jar s 3664 Tue Apr 19 11:24:18 CEST 2011 META-INF/MANIFEST.MF 606 Tue Apr 19 11:24:18 CEST 2011 META-INF/ECLIPSEF.SF 5638 Tue Apr 19 11:24:18 CEST 2011 META-INF/ECLIPSEF.RSA 0 Tue Apr 19 10:42:24 CEST 2011 META-INF/ sm 76 Tue Apr 19 11:24:16 CEST 2011 META-INF/eclipse.inf sm 2090 Thu Mar 31 15:10:02 CEST 2011 plugin.xml sm 1432 Wed Apr 06 09:01:42 CEST 2011 about.html sm 687 Thu Mar 31 15:10:02 CEST 2011 plugin.properties 0 Tue Apr 19 10:41:20 CEST 2011 ant_tasks/ 9767 Tue Apr 19 10:41:20 CEST 2011 ant_tasks/pdepublishing-ant.jar.pack.gz 73547 Tue Apr 19 10:41:20 CEST 2011 pdepublishing.jar.pack.gz s = signature was verified m = entry is listed in manifest k = at least one certificate was found in keystore i = at least one certificate was found in identity scope jar verified. Warning: This jar contains unsigned entries which have not been integrity-checked. This jar contains entries whose certificate chain is not validated. Re-run with the -verbose and -certs options for more details. It seems to be ok, except for those warnings. can i somehow have a little bit more loging/tracing in eclipse so that the updater tells me what it is doing and why it seems to fail/validate the specific pack/jar file? Hi Johan, there was a variety of issues that should now have been fixed. I'm closing as fixed but please don't hesitate to reopen if you ran into problems again. Thx. should i be able to update to 3.7RC1 from this build: Version: 3.7.0 Build id: I20110310-1119 ? so is it fixed in code? or is it just a server side thing? because i am trying to update now and the: org.eclipse.platform_3.7.0.v201105122000.jar.pack.gz file is now downloaded over and over again. i see it constantly climbing up to 309.73KB and then start over. This was a problem with the client. If you get M7 or RC1 and update to I builds this should be fixed. i don't think this is fixed or it is reintroduced. i am on this build: Version: 3.7.0 Build id: I20110526-1708 which is i believe RC3 and now today i did a check for updates and it wanted me to update to: 3.7.0.I20110613-1736 (on this update url: http://download.eclipse.org/eclipse/updates/3.7milestones ) and again the platform plugin: 3.7.0.v201106131736 thats 309KB is going over and over again. Do you use Java 7? yes i use that currently throughout my system to also test our own products (a ide based on eclipse and the runtime portion which is webstart) to be sure when we release our product that it runs also on Java7 which will be released i guess almost at the same time. Is java 7 the problem? Is the pack not validating? Did they change the pack format again (just as they did between 5 and 6) We use pack a lot in our webstart client and currently i have no problem starting our client in 7. Then I think you are being hit by bug #317785 *** This bug has been marked as a duplicate of bug 317785 *** |