Re: End of Saga: Re: Dependency hell following dpkg --audit
On Sunday 17 November 2013 21:32:49 Bob Proulx wrote: > It looks like you had a failed upgrade that you didn't notice had > failed. Indeed! Since I last posted I have checked and discovered this. I hadn't even thought of it as possible, so hadn't checked. It would happen on this one. :-( I have since reinstalled. And now have to restore all the non-hidden files, and set it all up as the owner had it before. :-(. Thanks for the input, Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311172336.52041.lisi.re...@gmail.com
Re: End of Saga: Re: Dependency hell following dpkg --audit
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 signature.asc Description: Digital signature
Re: Dependency hell following dpkg --audit
On Sunday 17 November 2013 14:57:29 Curt wrote: > On 2013-11-17, Robin wrote: > > To start I'd > > > > apt-get install --reinstall binutils module-init-tools > > > > then try > > > > apt-get -f install > > > > which will try to fix problem or will provide some error messages > > Is "dpkg --configure -a" helpful, or would that just leave her with > the hellish list she's already posted? Thanks, Robin and Curt. It is kind of you to consider the problem - and on Sunday afternoon too! - Well, a Sunday anyway. :-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311171519.07749.lisi.re...@gmail.com
End of Saga: Re: Dependency hell following dpkg --audit
On Sunday 17 November 2013 12:08:05 Lisi Reisz wrote: > Following Andrei's advice, I used dpkg --audit to sort out problems > with network connections, which it did very successfully. > > 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. > > 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. > > Here is the list as it currently stands. Help! > http://paste.ubuntu.com/6431514/ > > In fact, is this sensibly soluble, or should I give up on upgrading > and reinstall? To answer my own question, no, it is not sensibly soluble, and I should certainly reinstall. I have explored some more. It did not, and would not, upgrade to Wheezy. According to uname -a it was 6.0.8, not 7 at all. So I checked the sources.list, all correctly identified as wheezy, ran update again, and tried to run apt-get upgrade. Got told that there were lots of broken dependencies, and to run -f install, which then refused to run. So I gave up and have now started a reinstallation. I apologise for the lack of verbatim error mesages. I didn't think to keep them, and as I said, it is already reinstalling. :-( Sorry, archives, Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311171515.25652.lisi.re...@gmail.com
Re: Dependency hell following dpkg --audit
On 2013-11-17, Robin wrote: > > To start I'd > > apt-get install --reinstall binutils module-init-tools > > then try > > apt-get -f install > > which will try to fix problem or will provide some error messages > Is "dpkg --configure -a" helpful, or would that just leave her with the hellish list she's already posted? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnl8hmbd.1uv.cu...@einstein.electron.org
Re: Dependency hell following dpkg --audit
To start I'd apt-get install --reinstall binutils module-init-tools then try apt-get -f install which will try to fix problem or will provide some error messages rob On 17 November 2013 12:08, Lisi Reisz wrote: > Following Andrei's advice, I used dpkg --audit to sort out problems > with network connections, which it did very successfully. > > 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. > > 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. > > Here is the list as it currently stands. Help! > http://paste.ubuntu.com/6431514/ > > In fact, is this sensibly soluble, or should I give up on upgrading > and reinstall? > > Thanks! > Lisi > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/201311171208.05033.lisi.re...@gmail.com > > -- *rob*
Dependency hell following dpkg --audit
Following Andrei's advice, I used dpkg --audit to sort out problems with network connections, which it did very successfully. 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. 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. Here is the list as it currently stands. Help! http://paste.ubuntu.com/6431514/ In fact, is this sensibly soluble, or should I give up on upgrading and reinstall? Thanks! Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311171208.05033.lisi.re...@gmail.com
