Bug#552747: aptitude: Internal error: unexpected null solution.

2012-01-22 Thread Daniel Hartwig
tags 552747 + patch pending thanks On 22 January 2012 18:14, Hristo Hristov wrote: > Hi Daniel, > > I found the root cause of this bug: > http://anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=commitdiff;h=36164657896b16a079f2e52d57ebdfcef3c61178#patch15 > > The correct change should have be

Bug#552747: aptitude: Internal error: unexpected null solution.

2012-01-22 Thread Hristo Hristov
Hi Daniel, I found the root cause of this bug: http://anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=commitdiff;h=36164657896b16a079f2e52d57ebdfcef3c61178#patch15 The correct change should have been: -if(sol.get_actions().empty()) +if(sol.get_choices().size() == 0) Cheers, Hristo H

Bug#552747: aptitude: Internal error: unexpected null solution.

2010-03-09 Thread Marc Haber
On Tue, Mar 09, 2010 at 12:13:40AM +0100, Gunter Ohrner wrote: > Am Sonntag, 7. März 2010 schrieb Marc Haber: > > I haven't seen a single correctly displayed conflict solution from > > aptitude in months. > > Actually aptitude does chose a sensible conflict resolution if I just > proceed, ignorin

Bug#552747: aptitude: Internal error: unexpected null solution.

2010-03-08 Thread Gunter Ohrner
Am Sonntag, 7. März 2010 schrieb Marc Haber: > I haven't seen a single correctly displayed conflict solution from > aptitude in months. Actually aptitude does chose a sensible conflict resolution if I just proceed, ignoring the message. (See me previous mails to this bug.) It just does never dis

Bug#552747: aptitude: Internal error: unexpected null solution.

2009-11-21 Thread Hristo Hristov
Hello, I'm also affected by this bug. If you need any information I'd be happy to send it. Best regards, Hristo signature.asc Description: PGP signature

Bug#552747: aptitude: Internal error: unexpected null solution.

2009-11-11 Thread Gunter Ohrner
Am Mittwoch, 11. November 2009 schrieb Daniel Burrows: > I can't reproduce this from the bundle you sent. Could you run the > program like this: > $ aptitude --log-file=aptitude.log --log-level=info > reproduce the problem, and attach aptitude.log to the report? Of course, see the attachmen

Bug#552747: aptitude: Internal error: unexpected null solution.

2009-11-10 Thread Daniel Burrows
I can't reproduce this from the bundle you sent. Could you run the program like this: $ aptitude --log-file=aptitude.log --log-level=info reproduce the problem, and attach aptitude.log to the report? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debia

Bug#552747: aptitude: Internal error: unexpected null solution.

2009-11-10 Thread Gunter Ohrner
Am Dienstag, 10. November 2009 schrieb Gunter Ohrner: > The file created using aptitude-create-state-bundle? I'll try to create > it and will upload it somewhere if its not too big. # aptitude-create-state-bundle --print-inputs /root/.aptitude /var/lib/aptitude /var/lib/apt /var/cache/apt/pkgcach

Bug#552747: aptitude: Internal error: unexpected null solution.

2009-11-10 Thread Gunter Ohrner
Am Dienstag, 10. November 2009 schrieb Daniel Burrows: > > Internal error: unexpected null solution. > > when trying to upgrade my SID system. > Could you describe how you were trying to upgrade the system? Is > this with "aptitude full-upgrade", interactively, etc. It was interactively, ie

Bug#552747: aptitude: Internal error: unexpected null solution.

2009-11-10 Thread Daniel Burrows
On Wed, Oct 28, 2009 at 11:39:18PM +0100, Gunter Ohrner was heard to say: > Since upgrading aptitude from 0.4.x to 0.6.0.1, I just get the message > > Internal error: unexpected null solution. > > when trying to upgrade my SID system. Could you describe how you were trying to upgrade the s

Bug#552747: aptitude: Internal error: unexpected null solution.

2009-10-28 Thread Gunter Ohrner
Package: aptitude Version: 0.6.0.1-1 Severity: important Since upgrading aptitude from 0.4.x to 0.6.0.1, I just get the message Internal error: unexpected null solution. when trying to upgrade my SID system. My system is in a state which also required problem resolving before, as not all pac