Date: Mon, 12 May 2025 17:47:15 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 286740] ports-mgmt/pkg: 2.1.2 Cannot solve problem using SAT solver, trying another plan Message-ID: <bug-286740-32340-fYnvyPy7a5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-286740-32340@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286740 --- Comment #6 from p5B2EA84B3@t-online.de --- Thank you Baptiste, Mark for your contribution. To me this is still not satisfactory. I still do not know what purpose that sentence has: “Cannot solve problem using SAT solver, trying another plan.” Is is it an error, a warning, an info or something else? If you start reading such text on a box and it looks that you have a persisting problem. This is nothing that can be ignored and you start trying to make this problem go away. But if that is only a info that the solver just needs a little more time, a subsequent “solved” or “successfully completed” needs to be printed also. And if that takes only a few seconds I probably won’t want to see such message at all, maybe in verbose mode. Now the most important is: Was the pkg sqlite database ever in a critical state, that would have needed an action? To me it looked like this, finally resulting in a pkg delete -a. How else could this have been solved without touching a single package and avoiding mass downloading, just for getting a sane order of packages? Something like reinstall all in a dry mode but writing new tables or indexes to the database could have done it. I still do not know what kind of beast this was. Was my action necessary, appropriate? >From an admin’s or user’s view you should not need to lookup what a propositional satisfiability problem is and guess if this might bite you at some time later. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-286740-32340-fYnvyPy7a5>