Your message dated Sun, 02 Nov 2014 20:24:02 +0100
with message-id <[email protected]>
and subject line Re: unable to reproduce
has caused the Debian Bug report #552995,
regarding ecb: ecb prevents breaks the 'Python' menu
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 [email protected]
immediately.)
--
552995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552995
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ecb
Version: 2.32-1
Severity: normal
After the instalation of the ecb package the Python entry in the menu bar
does not work. The entry appears but it does not drop down.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (400, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ecb depends on:
ii cedet-contrib 1:1.0pre4-3 Collection of Emacs Development En
ii cogre 1:1.0pre4-3 Connected Graph Editor
ii eieio 1:1.0pre4-3 Enhanced Implementation of Emacs I
ii emacs22-gtk [emacsen] 22.3+1-1.1 The GNU Emacs editor (with GTK use
ii semantic 1:1.0pre4-3 Parser Infrastructure for Emacsen
ii speedbar 1:1.0pre4-3 Everything browser, or Dired on st
ecb recommends no packages.
ecb suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
fixed 552995 2.40+git20140216-1
thanks
On Tue, 12 Jul 2011 10:43:58 -0400 Mike O'Connor <[email protected]> wrote:
> tag 552995 + unreproducible
> thanks
>
> I'm not able to reproduce this with a current version of emacs and ecb.
> I suspect that whatever was causing your problem has since been fixed.
>
> Can you confirm whether or not you are still able to reproduce this bug?
Still not reproducible, closing the bug.
Cheers,
Balint
--- End Message ---
