Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 373173 - corruption of pack200 artifacts is detected too late
Summary: corruption of pack200 artifacts is detected too late
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P2 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 271707 381882
Blocks:
  Show dependency tree
 
Reported: 2012-03-03 03:04 EST by Tobias Oberlies CLA
Modified: 2021-06-17 04:28 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Oberlies CLA 2012-03-03 03:04:36 EST 
I suspect that bug 356496 is caused by corrupted pack200 artifacts or corruption during download or unpacking. We should add more checks and/or debug output to hunt down this problem. Ideally, Tycho/p2 would detect the corruption straight away and re-attempt the download of the non-pack200 artifact...
Comment 1 Tobias Oberlies CLA 2012-03-03 03:08:38 EST 
Probably fixing bug 271707 would help...
Comment 2 Tobias Oberlies CLA 2012-03-23 09:04:37 EDT 
I have indications that the artifact is in fact corrupted during download, probably by a proxy server.
Comment 3 Tobias Oberlies CLA 2012-06-06 11:43:57 EDT 
In the common p2 repositories, pack200 artifacts do not have MD5 sums. This means that on download, p2 executes only the unpack200 processing step and the signature verifier.

We have tracked down a case where the output of the unpack200 step was corrupted, i.e. not a valid ZIP archive. (Probably the corruption happened on the network, but we don't know yet - the problem disappeared before we could check this.) The signature verifier does *not* detect this situation - if new ZipFile fails, it simply reports "no problems".
Comment 4 Mickael Istria CLA 2021-04-08 18:06:19 EDT 
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse/tycho/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.
Comment 5 Alexander Kurtakov CLA 2021-06-17 04:28:15 EDT 
pack200 is deprecated functionality https://www.eclipse.org/lists/cross-project-issues-dev/msg18273.html