Ticket #1117 (new defect)
Can't resolve repositories on which installed repositories depend.
| Reported by: | eric225125 | Owned by: | |
|---|---|---|---|
| Priority: | Sometime | Milestone: | |
| Component: | clients/cave | Version: | 0.58.2 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Distribution: | N/A |
Description
I came across this problem after I synced ::SuperHeron?-misc, which had just added a dependency on ::virtualization, which I did not yet have installed. It appears impossible for me to install ::virtualization without first uninstalling ::SuperHeron?-misc:
% sudo cave resolve repository/virtualization Error:
- In program cave resolve repository/virtualization:
- When making environment from specification :
- When loading paludis configuration:
- Repository 'SuperHeron?-misc' requires repository 'virtualization', which is
not configured (paludis::ConfigurationError?)
% sudo cave resolve --no-complete -z repository/virtualization Error:
- In program cave resolve --no-complete -z repository/virtualization:
- When making environment from specification :
- When loading paludis configuration:
- Repository 'SuperHeron?-misc' requires repository 'virtualization', which is
not configured (paludis::ConfigurationError?)
Note: See
TracTickets for help on using
tickets.

The issue's more general than that: a repository isn't usable at all unless its masters are all there.
It's not entirely clear how we can handle this elegantly. One option is to make a repository 'empty' rather than in error if some of its masters are missing. But I'm not entirely sure that that won't cause something even weirder to happen...