Must not break xemacs21

Bug #515630 reported by Jeff Sparkes
66
This bug affects 9 people
Affects Status Importance Assigned to Milestone
slime (Debian)
Fix Released
Unknown
slime (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: slime

After the emacs lisp package slime is installed, it's byte-compiled for each of emacs and xemacs21.
When compiling with xemacs21, the following error comes from slime-autoloads:

Loading /var/cache/dictionaries-common/emacsen-ispell-default.el...
Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el...
Loading 50festival...
Loading 50git-core...
Loading 50slime...
Loading /usr/share/xemacs21/site-lisp/slime/slime-autoloads...
slime-autodoc doesn't work with XEmacs
xemacs exiting

Perhaps load of slime-autodoc should be disabled when compiling with xemacs21.

ProblemType: Bug
Architecture: i386
Date: Mon Feb 1 13:24:16 2010
DistroRelease: Ubuntu 10.04
Package: slime 1:20090908-1
PackageArchitecture: all
ProcEnviron:
 LANG=en_CA.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic-pae
SourcePackage: slime
Uname: Linux 2.6.32-11-generic-pae i686

Revision history for this message
Jeff Sparkes (jsparkes) wrote :
Revision history for this message
era (era) wrote :

Actually the package description already contains "Conflicts: xemacs" but it should be "Conflicts: xemacs21" if that's what was intended. There is no actual xemacs package, not even as a virtual package AFAICT.

Revision history for this message
era (era) wrote :

See also bug #478418

summary: - slime cannot be compiled with xemacs21
+ Should Conflicts: xemacs21 (not just xemacs)
era (era)
summary: - Should Conflicts: xemacs21 (not just xemacs)
+ Must not break xemacs21
Revision history for this message
era (era) wrote :

According to the upstream bug, this was fixed in 1:20100220-3 which is included in the version shipping in Maverick and newer. Marking as Fix Released.

Changed in slime (Ubuntu):
status: New → Fix Released
Changed in slime (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.