Hendrik Boom wrote: > Somehow, I seem to have a circular initscript dependency. > It seems to be complaining about the package mediatomb; furthemore, the > problem first appeared shortly after I installed mediatomb. > I tried uninstalling mediatomb, but it gets nowhere, because aptitude > balks upon detecting the circular dependency. Since Jonathan also said he had problems with mediatomb that would support it being a bug in that package. So uninstalling mediatomb does seem to be the right fix. Because the tools are in a confused state you will need to manually and forcibly unconfuse them. The lower level problem you are seeing is that 'insserv' is seeing a loop. Therefore I suggest breaking the loop in mediatomb's init script. I would do so by removing the init script. Or moving it aside if you like so that you can examine it. I didn't try it and so I might have made a typo here but here are the general steps. # mv /etc/init.d/mediatomb /tmp/ # update-rc.d mediatomb remove That update-rc.d command should also trigger insserv and without the problematic init script in place it should now be able to set a correct dependency order. You can verify this yourself by running insserv manually and looking at any output. # insserv ...no output is good output... Then try configuring all unconfigured packages. Might not be needed but safe to do. Then purge mediatomb. Purging will remove any /etc conffiles including the /etc/init.d/mediatomb that had to be removed manually. (Normally we might recommend "remove" but in this case "purge" is needed to completely clear all parts of it from the system.) # dpkg --configure -a # apt-get install -f # apt-get purge mediatomb Not all of this might be needed. It might simply be enough to purge mediatomb afterward. Bob
Attachment:
signature.asc
Description: Digital signature