Your message dated Mon, 25 Feb 2008 16:01:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#302540: could you please verify?
has caused the Debian Bug report #302540,
regarding mcedit inserts spaces when copying mouse buffer
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.)


-- 
302540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302540
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: mc
Version: 1:4.6.0-4.6.1-pre3-1
Severity: normal

Hi,

the same bug as it was reported in #120179 reappeared with the latest upload
to testing.  Please veryfy whether some patches which fix this boring problem
might have been lost in the meantime.

Thanks for maintaining MidnightCommander

          Andreas.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: 
LC_ALL set to [EMAIL PROTECTED])

Versions of packages mc depends on:
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libglib2.0-0                2.6.3-1      The GLib library of C routines
ii  libgpmg1                    1.19.6-19    General Purpose Mouse - shared lib

-- no debconf information


--- End Message ---
--- Begin Message ---
Hey Andreas,
>
> As you see the header information contains an additional space which
> was not added in the mail text any more.  But looking at the original
> editor window the syntax highlighting just adds this extra space (black
> background) and thus I think the original problem is fixed and we are
> facing a new problem here (which was hidden by the reported one
> previousely).  So feel free to close this bug.
Thanks, I'll do this :) 

>
> Thanks for caring for MidnightCommender! 
NP, it is atm fun.. :) But I hope that soon someone who hs also some c 
skills will join the pkg-mc project on alioth in order to fix some bugs :)


> Does this mean upstream is awake again?
 Mh... I'm writing with upstream every day in order to make him fix some 
problems.. right now he is finally working on using a shared samba lib, 
instead the outdated samba stuff whcih is included right now in mc. 

> Can we expect better UTF-8 support soon? 
mh.. version 5.0 of mc will contain utf8 support according to the 
upstream... but I really do not know when this version will be released... 
there is right now a very good utf8 patch on the mc-devel mailinglist and 
I think over including it into debian and replacing the old one with this 
patch.... but this would cause some more work than simply applying it  
(because the hughe set of patches against mc there will be _many_ 
issues) :S

> Do you  think it makes sense to file new bug reports about those 
problems?
Mh... are there important things? :) If yes please report them... or 
discuss them beforhand with me ;-)
ATM I'll try to reduce the amount of bugs to something around ~20 open 
bugs... in order to get an overview of what have to be done.

I also work on several smaller fixes for mc (right now that folders with 
spaces or other things which should be escaped do not work correctly). 
I'll hope that these patches will made it into the upstream mc and that he 
finally release a new version. If not I'll take care of them inside of 
debian.


Greetings
Winnie

-- 
 .''`.   Patrick Winnertz <[EMAIL PROTECTED]>
:  :' :  GNU/Linux Debian Developer
`. `'`   http://www.der-winnie.de http://people.skolelinux.org/~winnie
  `-  Debian - when you have better things to do than fixing systems

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to