HCoop / ntk / apt.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 59df9e2) | patch
if Resolver fails, do not continue even if not broken
authorDavid Kalnischkies <david@kalnischkies.de>
Fri, 30 May 2014 11:42:36 +0000 (13:42 +0200)
committerDavid Kalnischkies <david@kalnischkies.de>
Fri, 30 May 2014 11:42:36 +0000 (13:42 +0200)
commit58377ceb4b62e8f50ddae8f17ce1511e4bf79a18
tree5d5af36b2875ee2e8e1a5bd2c2ca0805092a8a90tree | snapshot (tar.gz zip)
parent59df9e241d035c9e5ea0859d1b9b0abf70ab1596commit | diff
if Resolver fails, do not continue even if not broken

This can happen if the request is already a well-formed request all by
itself (e.g. the package has no dependencies), but the resolver found
a reason to not accept it as solution. Our edsp 'dump' solver e.g.
shouldn't be able to trigger install, which it does otherwise.
apt-private/private-install.cc diff | blob | blame | history
ntk's bugfix for apt