Looks like an update to SLIME has been pushed to the main portage tree. This is a big problem because an overlay-based system is being forced to install cl-asdf, common-lisp-controller and cl-asdf-binary-locations. Since no serious lisp developer runs from the main tree, this is disastrous. I propose you move the new SLIME package to the overlay, and remove its dependencies on these death-packages. Or merge everything in the overlay into the main tree. Those are the only two workable options. root@sphinktop:~# emerge -av --deep --newuse --update world These are the packages that would be merged, in order: Calculating dependencies | * ERROR: dev-lisp/cmucl-20b_p001 failed: * glo-utils.eclass could not be found by inherit() * * Call stack: * ebuild.sh, line 1995: Called source '/usr/portage/local/layman/lisp/dev-lisp/cmucl/cmucl-20b_p001.ebuild' * cmucl-20b_p001.ebuild, line 6: Called inherit 'eutils' 'glo-utils' 'toolchain-funcs' * ebuild.sh, line 1376: Called die * The specific snippet of code: * [ ! -e "$location" ] && die "${1}.eclass could not be found by inherit()" * * If you need support, post the output of 'emerge --info =dev-lisp/cmucl-20b_p001', * the complete build log and the output of 'emerge -pqv =dev-lisp/cmucl-20b_p001'. * S: '/var/tmp/portage/dev-lisp/cmucl-20b_p001/work/cmucl-20b_p001' ... done! [ebuild N ] dev-lisp/cl-asdf-1.89 60 kB [0] [ebuild N ] dev-lisp/common-lisp-controller-5.13-r1 31 kB [0] [ebuild N ] dev-lisp/cl-asdf-binary-locations-20061018 8 kB [0] [ebuild UD] dev-lisp/gentoo-init-0.1 [0.4] 0 kB [?=>0] [ebuild UD] dev-lisp/cl-ppcre-1.2.16 [2.0.2] 165 kB [?=>0] [ebuild R ] app-emacs/slime-2.0_p20101103 USE="-doc -xref%" 5 kB [?=>0] [ebuild U ] www-client/w3m-0.5.3-r1 [0.5.3] USE="X gpm gtk nls ssl unicode -fbcon -imlib -lynxkeymap -migemo -nntp -xface" LINGUAS="-ja" 0 kB [0] [blocks B ] dev-lisp/cl-asdf-binary-locations ("dev-lisp/cl-asdf-binary-locations" is blocking dev-lisp/asdf-binary-locations-0.3.8-r1) [blocks B ] dev-lisp/cl-asdf ("dev-lisp/cl-asdf" is blocking dev-lisp/asdf-1.123) Total: 7 packages (1 upgrade, 2 downgrades, 3 new, 1 reinstall), Size of downloads: 266 kB Conflict: 2 blocks (2 unsatisfied) Portage tree and overlays: [0] /usr/portage [?] indicates that the source repository could not be determined * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (dev-lisp/cl-asdf-binary-locations-20061018, ebuild scheduled for merge) pulled in by dev-lisp/cl-asdf-binary-locations required by (dev-lisp/gentoo-init-0.1, ebuild scheduled for merge) (dev-lisp/asdf-1.123, installed) pulled in by dev-lisp/asdf required by @selected dev-lisp/asdf required by (dev-lisp/asdf-binary-locations-0.3.8-r1, installed) (dev-lisp/asdf-binary-locations-0.3.8-r1, installed) pulled in by dev-lisp/asdf-binary-locations required by @selected (dev-lisp/cl-asdf-1.89, ebuild scheduled for merge) pulled in by >=dev-lisp/cl-asdf-1.84 required by (dev-lisp/common-lisp-controller-5.13-r1, ebuild scheduled for merge) dev-lisp/cl-asdf required by (app-emacs/slime-2.0_p20101103, ebuild scheduled for merge) dev-lisp/cl-asdf required by (dev-lisp/cl-asdf-binary-locations-20061018, ebuild scheduled for merge) Reproducible: Always
There is not much that we can do about this at the moment. Obviously, SLIME in the main tree cannot depend on packages in the overlay. The workaround is also obvious, namely that you should install app-emacs/slime from the overlay. Which should be automatic, because the version there has always been newer than in the main tree. (In reply to comment #0) > [ebuild R ] app-emacs/slime-2.0_p20101103 USE="-doc -xref%" 5 kB [?=>0] > > Portage tree and overlays: > [0] /usr/portage > [?] indicates that the source repository could not be determined Looks like there's also something wrong with your overlay setup. What does "layman -lv" output?
layman -lv returns nothing! Does it have anything to do with this message, which I found in my lisp overlay directory, and is dated Feb 3 (today)? (Rhetorical question; it is obviously the problem.) Did not expect the entire overlay to be relocated. I will get the new overlay and see if that fixes the problem, and I'll report my findings here. root@sphinktop:/usr/portage/local/layman/lisp# cat MOVED The Gentoo Lisp overlay has been moved to git.overlays.gentoo.org. It is accessible via gitweb: http://git.overlays.gentoo.org/gitweb/?p=proj/lisp.git Read-only access: git://git.overlays.gentoo.org/proj/lisp.git or http://git.overlays.gentoo.org/gitroot/proj/lisp.git Write access for developers and members: git+ssh://git@git.overlays.gentoo.org/proj/lisp.git If you have any further questions, we can be found in the #gentoo-lisp IRC channel. Or send a mail to <lisp@gentoo.org>.
Verified: the problem was indeed the fact that the overlay moved.
Sorry for the confusion. I've now added a news item to the old overlay. Probably we should have done so in November already, when the overlay was moved.
