Bug#517107: aptitude installed coq with unmet dependencies
On Thu, Feb 26, 2009 at 11:11:09AM +0100, Vincent Lefevre <vincent@vinc17.org> was heard to say:
> On 2009-02-25 19:34:02 -0800, Daniel Burrows wrote:
> > The problem is that the new version of coq that you were trying to
> > install has an undeclared conflict with coq-libs. I'll reassign the
> > bug.
>
> This is strange because in aptitude, coq-libs was really marked for
> removal (because of the conflict with coq-theories, in fact), so that
> aptitude could have known that coq-libs would be removed. But perhaps
> aptitude isn't smart enough to see beyond undeclared conflicts.
The problem is that if conflicts aren't properly marked, aptitude
and dpkg can't calculate the correct order in which to install
packages. So, in this case, aptitude thinks it's just fine to
temporarily install the new coq alongside the old coq-libs, because
there's nothing that would tell it otherwise. When dpkg tries that, it
fails because of the file conflict, so aptitude aborts the install.
But of course the dependencies of the new coq are already installed,
and apparently these don't supply what's needed for the old coq to run.
Daniel
Reply to: