dpkg - process_queue: Assertion 'dependtry <=4' failed. error

[danson]

[CODE]
 root@ubuntu:dpkg --configure -a
dpkg: ../../src/packages.c:191: process_queue: Assertion 'dependtry <=4' failed.
Aborted
[/CODE]

Happens every time i run the dpkg --configure -a command and I'm always told to run that command before running dpkg or synaptic.

However I only seem to need to run it once per session. Synaptic starts without error afterwards.

Details:
System is a fresh install of Badger that has been immediately upgraded via package system to Dapper
I am reasonably sure the error showed in Badger as well as Dapper.
It tends to show if I run any sort of dpkg/synaptic command. It refuses to run and says I need to run the dpkg --configure -a command first.

Machine is a Dell 500mhz poweredge 1300, 384mb RAM, onboard video (ATI RAGE 30 IIC)

Happy to give any more details/run tests if needed.

Ubuntu forum thread started at
http://ubuntuforums.org/showthread.php?s=91f42fe50a575fab57ca89c730e22508&p=1352047#post1352047

[Ian Jackson (ijackson)]

danson writes ("[Bug 55641] dpky - process_queue: Assertion 'dependtry <=4' failed. error"):
> root@ubuntu:dpkg --configure -a
> dpkg: ../../src/packages.c:191: process_queue: Assertion 'dependtry <=4' failed.
> Aborted

Can you please attach your /var/lib/dpkg/status to the bug report ?

Thanks,
Ian.

[Ian Jackson (ijackson)]

Ian Jackson writes ("[Bug 55641] Re: [Bug 55641] dpky - process_queue: Assertion 'dependtry <=4' failed. error"):
> Can you please attach your /var/lib/dpkg/status to the bug report ?

Oh, and any files in /var/lib/dpkg/updates too, please.

Ian.

[Don Leuenberger (dfleuen)]

Here is my copy of status and files in updates. Hope this helps. Any workaround or repair advice would be appreciated.

[Don Leuenberger (dfleuen)]

Here is only file in updates

[Don Leuenberger (dfleuen)]

In my case, the system is a running Dapper 6.06 system. The error seemed to happen after running the 'envy' script to update to the latest nvidia drivers.

Don

[Ian Jackson (ijackson)]

This was fixed in edgy's dpkg.

The problem is the weird and broken dependencies in python-subversion, which trigger a dpkg bug. You can probably work around it by removing the python-subversion package. Alternatively, if you feel brave, edit /var/lib/dpkg/status, search for the entry for python-subversion, and delete the mention of python2.4-subversion from Depends.