I sent these pull requests to fix the issues: https://github.com/gwkkwg/asdf-system-connections/pull/2 https://github.com/sionescu/iolib/pull/41
Grepping Quicklisp, it appears that two more projects needed fixes, but it's actually an example in cl-graph (of extracting a graph of ASDF dependencies, which was broken, and which I fixed, leveraging POIU's graph representation), and a trivial fix for asdf-dependency-grovel, which I could push since I'm maintainer. https://github.com/gwkkwg/cl-graph/pull/11 https://gitlab.common-lisp.net/xcvb/asdf-dependency-grovel/commit/07e3ff57a55cccc623b320da93c93ab63280fc54 I hope that's all. I would refrain from releasing an ASDF with this restriction until both asdf-system-connections and iolib have been fixed. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The difference between a programmer and a user, is that the programmer knows there is no difference between using and programming. — Faré On Wed, Nov 16, 2016 at 8:36 PM, Robert Goldman <rpgold...@sift.net> wrote: > On 11/16/16 Nov 16 -10:31 AM, Attila Lendvai wrote: >> another data point: >> >> it was caused by asdf-system-connections. i thought i got rid of that >> long ago, but it's included in ql, and it got installed on my system >> somehow. >> >> after >> >> (ql:uninstall :asdf-system-connections) >> >> my script continues, but then fails later on with iolib's >> IOLIB/GROVEL::PROCESS-OP. >> > > Thanks, filed https://github.com/sionescu/iolib/issues/40 > > Best, > r > >
