Thank you thank you thank you Matthew, I was going mental trying to get this
package to stop breaking my upgrades.
Not being able to run a package because a port is busy is ok, not being able to
uninstall or reinstall a package because a very commonly used port is busy is a
bad bad bug IMHO
--
Public bug reported:
Binary package hint: common-lisp-controller
Description:Ubuntu 10.10
Release:10.10
common-lisp-controller:
Installed: 7.2
Candidate: 7.2
What I expected to happen:
I expected my quicklisp to load without problems
What happened:
It breaks with the message
would anyone care to commit to whether the bug fix will require a
complete purge and reinstall as stated above or would it be reasonable
to set up a system with all the other parts working in the mean time and
just add users and groups when it's working again? It'd be nice to not
set up a working
