On Fri, May 30, 2014 at 5:22 PM, Felipe Sateler <fsate...@debian.org> wrote: > Package: apt > Version: 1.0.3 > Followup-For: Bug #726174 > >> If a package is pinned to prevent an upgrade, but the candidate version >> has new dependencies, apt will install those even though the depending >> package isn't being upgraded. > > The same thing happens when a package cannot be upgraded due to > dependency issues. For example: > > Attached is a test case I managed to come up with. Note that liba2 is > installed even though a ends up not being upgraded. > > Note also that the problem is not exhibited if the conflicts is moved > from package a to liba2, or only added to liba2.
I'll add that the bug is gone if APT::Get::AutomaticRemove=true is set. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
