[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#284292: marked as done (ilisp: emacs doesn't respond and cpu usability is 100%)

Your message dated Thu, 29 May 2008 16:49:28 +0100
with message-id <200805291549.m4TFnSdI011755@kmos.homeip.net>
and subject line ilisp has been removed from Debian, closing #284292
has caused the Debian Bug report #284292,
regarding ilisp: emacs doesn't respond and cpu usability is 100%
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
284292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284292
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ilisp
Version: 5.12.0+cvs.2004.10.29
Severity: important

Emacs uses nearly 100% of cpu and doesn't respond. This matters only in
ilisp mode - i use cmucl. This behaviour is quite often (minimally ones
a day). Last time I wrote '(defmethod' ..., after emacs new start
this worked ok.


Jan Gregor

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.21-xfs
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (ignored: LC_ALL set to cs_CZ)

Versions of packages ilisp depends on:
ii  common-lisp-controller        4.11       This is a Common Lisp source and c
ii  debconf                       1.4.16     Debian configuration management sy
ii  emacsen-common                1.4.13     Common facilities for all emacsen.

-- debconf information:
* ilisp/fsf-compliant: true

--- End Message ---
--- Begin Message --- 
Version: 5.12.0+cvs.2004.12.26+rm

The ilisp package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/284376 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---
Reply to: