On Wed, Nov 28, 2012 at 11:32:51AM -0800, Christoph Egger wrote: > Hi! > > Christoph Egger <christ...@debian.org> writes: > > Daniel Hartwig <mand...@gmail.com> writes: > >> On 22 November 2012 03:36, Christoph Egger <christ...@debian.org> wrote:
> It's also easily reproducible with a `mk-build-dep` in > empathy/experimental and isntalling aptitude in a minimal chroot, dpkg > -i the build-dep and have aptitude [1] resolve it > > [1] aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o > Aptitude::CmdLine::Ignore-Trust-Violations=false -o > Aptitude::ProblemResolver::StepScore=100 -o > Aptitude::ProblemResolver::SolutionCost="safety, priority, > non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject > empathy-build-deps :UNINST" -o > Aptitude::ProblemResolver::Keep-All-Level=55000 -o > Aptitude::ProblemResolver::Remove-Essential-Level=maximum install > empathy-build-deps I used this method to reproduce the issue for current gnome-shell/experimental. The trigger seems to be the usage of non-default-versions in the SolutionCost, using the default ("safety, priority") like e.g. pbuilder does results in aptitude successfully finding a solution. -- Information is the inverse of entropy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org