Nope, I don't, but the change should be trivial -- just change emacs to x?emacs everywhere. This is based on the listing of Emacs package names in the Debian Emacs policy, as included in /usr/share/doc/emacsen-common (I have a slightly old version; this system is still on Jaunty).
As of Karmic, only xemacs21 seems to be availble.
Off the top of my head:
-if report['Package'] in ['emacs22', 'emacs23', 'emacs-snapshot']:
+if report['Package'] in ['emacs22', 'emacs23', 'emacs-snapshot', 'xemacs21']:
# emacs add-on packages trigger byte compilation, which might fail
# we are very interested in reading the compilation log to determine
# where to reassign this report to
- regex = r'^!! Byte-compilation for emacs\S+ failed!'
+ regex = r'^!! Byte-compilation for x?emacs\S+ failed!'
if 'DpkgTerminalLog' in report and re.search(regex, report['DpkgTerminalLog'], re.MULTILINE):
for line in report['DpkgTerminalLog'].split('\n'): m = re.search(r'^!! and attach the file (\S+)', line)
Nope, I don't, but the change should be trivial -- just change emacs to x?emacs everywhere. This is based on the listing of Emacs package names in the Debian Emacs policy, as included in /usr/share/ doc/emacsen- common (I have a slightly old version; this system is still on Jaunty).
As of Karmic, only xemacs21 seems to be availble.
Off the top of my head:
-if report['Package'] in ['emacs22', 'emacs23', 'emacs-snapshot']: 'DpkgTerminalLo g'], re.MULTILINE): 'DpkgTerminalLo g'].split( '\n'):
m = re.search(r'^!! and attach the file (\S+)', line)
+if report['Package'] in ['emacs22', 'emacs23', 'emacs-snapshot', 'xemacs21']:
# emacs add-on packages trigger byte compilation, which might fail
# we are very interested in reading the compilation log to determine
# where to reassign this report to
- regex = r'^!! Byte-compilation for emacs\S+ failed!'
+ regex = r'^!! Byte-compilation for x?emacs\S+ failed!'
if 'DpkgTerminalLog' in report and re.search(regex, report[
for line in report[