Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323911 - Need a way to tell p2 to *really* look into the repository
Summary: Need a way to tell p2 to *really* look into the repository
Status: CLOSED DUPLICATE of bug 291230
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-29 13:03 EDT by Stephan Herrmann CLA
Modified: 2012-04-24 15:22 EDT (History)
1 user (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 Stephan Herrmann CLA 2010-08-29 13:03:56 EDT 
I've been annoyed time and again by p2 telling me "No repository found
containing: ..." right after I've uploaded these artifacts to the repo.
Usually just trying again and e.g. switching from Install New Software 
to Check for Updates makes p2 realize at some point that the artifacts
are indeed there and install succeeds. 

Given that this kind of situation seems to be difficult to debug
I propose to add some option in the UI so the user can say:
"No, you're wrong, please go back to the repository and really
try hard to find what you need, and only come back to me if you
have evidence that something is really missing, and by evidence
I mean something that I can use to fix the problem on the server."
Comment 1 Pascal Rapicault CLA 2010-08-29 20:33:32 EDT 

*** This bug has been marked as a duplicate of bug 291230 ***
Comment 2 Stephan Herrmann CLA 2012-04-24 15:22:06 EDT 
(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of bug 291230 ***

Now that bug 291230 has been closed as a dupe of bug 337022 (which is about avoiding network access - the opposite of what we need here!), this bug is no longer covered by any active bug, nor has it been fixed.

The situation isn't quite as bad as during the times when I filed this bug, but next time the bug hits me I should probably re-open ...