Lisi Reisz wrote: > Lisi Reisz wrote: > > Following Andrei's advice, I used dpkg --audit to sort out problems > > with network connections, which it did very successfully. Good advice. > > In the process, I discovered that there was quite a list of > > unconfigured packages. These I have been trying to configure. In > > the process I have unleashed a dependency hell, not only worse than > > I have ever seen, but worse than I ever imagined. It looks like you had a failed upgrade that you didn't notice had failed. > > Is there a trick? Other than trying one after another going > > backwards, and hoping that I will not either go round and round in > > circles, or meet a demand for a version that I can see no hope of > > installing. There is a trick that sometimes improves things. Include *both* the stable and oldstable sources in the sources.list file. In this case it would have been both squeeze and wheezy. Then update so both are known. Then try using 'apt-get install -f' to resolve the dependencies. It all depends upon the problem but sometimes that can get past some of them. After that then remove the oldstable sources and complete the upgrade to the new stable. For folks running Sid Unstable it is recommended to include Testing in the sources.list file for the same reason. Because Sid will sometimes need to be intentionally broken to bridge across transitions. For those cases it is useful to have the Testing sources available to help step across the transition. Bob
Attachment:
signature.asc
Description: Digital signature