Re: How to get aptitude to ignore broken dependency

2009-04-08 Thread Boyd Stephen Smith Jr.
In <20090409012257.ga18...@emurlahn.burrows.local>, Daniel Burrows wrote: >On Thu, Apr 09, 2009 at 01:08:50AM +0100, Alan Chandler was heard to say: >> How can I get around this and force aptitude to ignore this broken >> dependency > > You can't. You can force the install with dpkg, but aptitu

Re: How to get aptitude to ignore broken dependency

2009-04-08 Thread Daniel Burrows
On Thu, Apr 09, 2009 at 01:08:50AM +0100, Alan Chandler was heard to say: > How can I get around this and force aptitude to ignore this broken > dependency You can't. You could try removing gitk, upgrading, then installing it again. Daniel -- To UNSUBSCRIBE, email to debian-user-requ..

How to get aptitude to ignore broken dependency

2009-04-08 Thread Alan Chandler
I have a problem For some reason - not sure what - git-core is stuck at 1.6.2.1 whilst the remainder of the git utilities (such as gitk) have been upgraded to 1.6.2.2 Because I need both git-core and gitk, but had accidentally deleted gitk when this issue arose, I manually installed gitk using