From: Rick Pasotto on 30 Apr 2010 09:40 Today's run of 'aptitude -s safe-upgrade' had been running for over an hour and was using half my memory when I killed it. The status line was: open: 107756; closed: 119093; defer: 107181; conflict: 167 There's evidently some situation it can't resolve. How can I figure out what package(s) cause the problem? -- If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy. -- James Madison Rick Pasotto rick(a)niof.net http://www.niof.net -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100430133128.GA30106(a)niof.net
From: Daniel Burrows on 30 Apr 2010 10:10 On Fri, Apr 30, 2010 at 09:31:28AM -0400, Rick Pasotto <rick(a)niof.net> was heard to say: > Today's run of 'aptitude -s safe-upgrade' had been running for over an > hour and was using half my memory when I killed it. The status line was: > > open: 107756; closed: 119093; defer: 107181; conflict: 167 > > There's evidently some situation it can't resolve. How can I figure out > what package(s) cause the problem? Which version of aptitude do you have? You could add "--log-resolver --file-file=aptitude.log" and send me the first few megabytes of output. Also, can you add "-o aptitude::cmdline::resolver-dump=aptitude-resolver.dump" to the command-line and then send me the file 'aptitude-resolver.dump'? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100430140721.GC22310(a)emurlahn.burrows.local
From: Rick Pasotto on 3 May 2010 13:30 On Fri, Apr 30, 2010 at 07:07:21AM -0700, Daniel Burrows wrote: > On Fri, Apr 30, 2010 at 09:31:28AM -0400, Rick Pasotto <rick(a)niof.net> was heard to say: > > Today's run of 'aptitude -s safe-upgrade' had been running for over an > > hour and was using half my memory when I killed it. The status line was: > > > > open: 107756; closed: 119093; defer: 107181; conflict: 167 > > > > There's evidently some situation it can't resolve. How can I figure out > > what package(s) cause the problem? > > Which version of aptitude do you have? > > You could add "--log-resolver --file-file=aptitude.log" and send me the > first few megabytes of output. > > Also, can you add "-o aptitude::cmdline::resolver-dump=aptitude-resolver.dump" > to the command-line and then send me the file 'aptitude-resolver.dump'? I did send this to you but have not heard back. Just checking if I need to resend it. In the meantime, I'm using "apt-get -s upgrade" to generate a list of potential upgrade packages and then updating them with aptitude. -- "Words are, of course, the most powerful drug used by mankind." -- Rudyard Kipling Rick Pasotto rick(a)niof.net http://www.niof.net -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100503172355.GR30106(a)niof.net
From: Daniel Burrows on 4 May 2010 09:50 On Mon, May 03, 2010 at 01:24:23PM -0400, Rick Pasotto <rick(a)niof.net> was heard to say: > I did send this to you but have not heard back. Just checking if I need > to resend it. No, I just haven't had time to analyze it. Daniel -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100504134018.GA22604(a)emurlahn.burrows.local
|
Pages: 1 Prev: invisible console (solved) Next: Aptitude status output meaning |