On Thu, Feb 26, 2009 at 06:20:17PM +0100, Vincent Lefevre vinc...@vinc17.org
was heard to say:
On 2009-02-26 07:25:43 -0800, Daniel Burrows wrote:
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.
I
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
On Thu, Feb 26, 2009 at 11:11:09AM +0100, Vincent Lefevre vinc...@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.
On 2009-02-26 07:25:43 -0800, Daniel Burrows wrote:
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.
I still don't understand why apt-get -f install doesn't see the new
version of coq (which lead to the
Package: aptitude
Version: 0.4.11.11-1
Severity: grave
Justification: renders package unusable
(Well, it makes some packages unusable.)
aptitude installed coq with unmet dependencies. Here's the output:
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
On Wed, Feb 25, 2009 at 05:50:44PM +0100, Vincent Lefevre vinc...@vinc17.org
was heard to say:
Unpacking replacement coq ...
dpkg: error processing /var/cache/apt/archives/coq_8.2~rc2+dfsg-3_amd64.deb
(--unpack):
trying to overwrite `/usr/lib/coq/contrib/interface/vernacrc', which is also
6 matches
Mail list logo
