Hi,

Quoting Ralf Treinen (2015-10-01 19:26:10)
> Indeed. The problem is the new version of clasp in unstable (3.1.3-1).
> Downgrading clasp to 3.1.2-1 is a temporary workaround. I'll ask upstream to
> update aspcud to the new version of clasp.

ah that fortunately sounds as if the fix could be quick and easy! Especially
since aspcud and clasp seem to have the same upstream :)

Maybe to prevent this in the future, either a test case during package build
or/and an autopkgtest could be added to aspcud? Since it is now used to solve
installation problems on the package builders it becomes important that
problems are detected and fixed early.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to