I just tried to switch from xemacs-packages-sumo to xemacs-packages-all but it seems that nothing works as it should. I had to comment some parts of my init.el and custom.el to have xemacs start without arrors and then : - I can't have any paren highlighting - auctex is not laoded with .tex files and I can't load it manually - probably a whole lot of other problems I didn't see... Basically, it seems like xemacs does not see any of its packages, whereas when I use the sumo-package everything works fine. Is there a variable that needs being set to tell xemacs where to look for packages? For the moment I switched back to sumo as I need to use Xemacs... Reproducible: Always Steps to Reproduce:
Taking auctex as a specific problem to work on: can you check that you've got both xemacs-packages-sumo and app-xemacs/auctex installed? My guess as to what happens is that you installed auctex first, and then later installed the sumo packages. Unfortunately the sumo package will overwrite the files from the auctex packages. When you later unmerge the sumo package, the files are gone but the package manager still thinks that the auctex files are installed. Manually reinstalling the auctex package should fix this. I'll see if it is possible to come up with an automated way to handle this, but I would appreciate confirmation that this is indeed the problem you are experiecing. (Obviously the same will apply to other packages that got installed before the sumo package was installed).
OK, I did some additional testing. I unmerged all xemacs packages, reemerged xemacs, and emerged xemacs-packages-all. This emerged 70 packages including app-xemacs/auctex-1.47. After this, I started xemacs with en empty custom.el and an init.el containing only (require 'tex-site). This should normally load auctex. When I start xemacs I do not get any error message: the init and custom files are correctly understood. But then, when I open any kind of file (.tex, .c, .java...) it never loads the correct mode and there is no way I can load the mode manually (M-X c-mode does not exist for instance). I think the problem is not specific to auctex, but it is the same for all the modes. Then, when I try to list all the packages (M-X list-packages), I get an error message (which I don't really understand): "Symbol's value as variable is void: allow-remote-paths".
I had some more time this modrning to do some more testing: I noticed that by reemergin xemacs-base, some bugs disappeared. I guess the sumo package overwrites some files about everywhere in the xemacs installation. Therefore I unmerged all the app-xemacs/* packages and unmerged xemacs. Then I reemerged xemacs and xemacs-packages-all (there were 116 packages this time) and this seems to solve all the problems I had. Auctex works fine, paren highlighting too, all the other modes... So I guess the xemacs-package-all works fine and it's just the sumo packages which is really crappy... Maybe you could add a notice in the xemacs-package-all to inform users that when upgrading from the sumo-package, everything needs to be reemerged. Anyway, thanks for your help as I didn't think the sumo package was indeed overwriting other files.
(In reply to comment #3) > I had some more time this modrning to do some more testing: I noticed that by > reemergin xemacs-base, some bugs disappeared. I guess the sumo package > overwrites some files about everywhere in the xemacs installation. Therefore I > unmerged all the app-xemacs/* packages and unmerged xemacs. Then I reemerged > xemacs and xemacs-packages-all (there were 116 packages this time) and this > seems to solve all the problems I had. Auctex works fine, paren highlighting > too, all the other modes... Great! Thanks for the feedback and testing. > So I guess the xemacs-package-all works fine and it's just the sumo packages > which is really crappy... Maybe you could add a notice in the > xemacs-package-all to inform users that when upgrading from the sumo-package, > everything needs to be reemerged. I'm thinking about doing a revision bump on all packages to make sure that they are reinstalled as part of the xemacs-packages-all update, but I won't have time for that until the weekend. The problem is that the individual packages and the sumo package both write the same files, and portage can't keep track of that, so it thinks that xemacs-base is still installed even though all the files have been removed as part of the sumo unmerge. You can guard against this general situation with the collision-protect feature that you can enable in make.conf. I'm also reopening the bug since more people may run into this and I have not implemented a suitable solution right now.
*** Bug 223123 has been marked as a duplicate of this bug. ***
Unmerging all individual xemacs packages as well as sumo then emerging xemacs-packages-all fixed the problem for me. Actually, I unmerged and remerged xemacs and xemacs-base as well. Now the c++-mode is back working, but havent tried much else yet ...
To summarise: So the problem appears to be that the un-install of the sumo-package removes files from other packages, such that the files are gone despite the packages being installed to portages knowledge. A solution is to remove all installed xemacs-packages and xemacs, and re-emerge them: [code] cd /usr/portage/ emerge -C app-xemacs/* emerge -C app-editors/xemacs emerge app-editors/xemacs app-xemacs/xemacs-packages-all [/code] Rene
(In reply to comment #7) > To summarise: > > So the problem appears to be that the un-install of the sumo-package removes > files from other packages, such that the files are gone despite the packages > being installed to portages knowledge. That is correct. My advice is to always run with FEATURES=collision-protect to catch those situations before they can happen. > A solution is to remove all installed xemacs-packages and xemacs, and re-emerge > them: > [code] > cd /usr/portage/ > emerge -C app-xemacs/* > emerge -C app-editors/xemacs > emerge app-editors/xemacs app-xemacs/xemacs-packages-all > [/code] Note that there is no need to re-emerge xemacs. Its files are separate from either the app-xemacs/* or sumo packages.
*** Bug 240716 has been marked as a duplicate of this bug. ***
I've just bumped the revisions on app-xemacs/xemacs-base and app-xemacs/mule-base, which are the packages that post-depend on app-editors/xemacs. This will hopefully fix these issues for the majority of people, so I'm closing this bug.
