On Tue, Jun 17, 2014 at 08:26:30AM +0200, Pietro Abate wrote: > Running apt-get today to upgrade my machine I get this fatal error : > > $sudo apt-get --solver aspcud dist-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Execute external solver... Done > Done > Execute external solver... Error! This hints actually at a refactoring problem created in d8a8f9d7 … The solver is run twice in upgrade/dist-upgrade cases. It works the first time, but the second one fails. Maybe a problem if a solver has nothing to do? I couldn't reproduce this problem though. The double call I will fix as it makes no sense, not even with the internal solver, just that it is a lot faster and therefore not really noticeable in that case… (it "explains" some 'mysterious' debug behaviour though…). > E: Sub-process aspcud returned an error code (1) This check is new in 1.0.4, previously the exit code was ignored (and even segfaults…), but the documentation of the EDSP protocol specifically says that the solver should always exit with 0 even if it failed to find a solution, aka: Looks like you found a situation in which the solver exits with a non-zero statuscode. Best regards David Kalnischkies
Attachment:
signature.asc
Description: Digital signature