#683 RFE: fail compose when comps require non-existing package
Closed: Fixed 6 years ago Opened 6 years ago by lsedlar.

Currently when comps mentions a package that does not exist an error is reported in the depsolving log.

It should be possible to turn this into a fatal error based on a config option.

if not matches:
    self.logger.warn('Could not find a match for %s in any configured repo' % pattern)
    continue

Split out from #676.


We actually already have this issue as #50.

Given there is no way today to mark packages are architecture specific this is not trivially solvable

Indeed, someone will need to go through the log and find out why the package is missing. It could be arch, or the package is retired, or maybe a subpackage is no longer created. There's no way to determine this automatically.

Metadata Update from @lsedlar:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @lsedlar:
- Issue tagged with: 4.1.18

6 years ago

Login to comment on this ticket.

Metadata