Christian, thank you for so quickly uploading a fixed medit into Debian.
I notice from http://bjorn.haxx.se/debian/testing.pl?package=medit
that your patched package is 0 days old, and must be 10 days old to
go in. So the minimum wait for critical bugfixes is 10 days? Why is
the wait so long? C
By the way: I asked Yevgen if this bug affects medit 0.8.2. Yevgen
replied "I think yes".
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X-Debbugs-Cc: [EMAIL PROTECTED]
Package: medit
Version: 0.9.2-1+b2
Tags: patch
Severity: critical
Justification: data loss bug in a text editor
Hello, and thanks for maintaining medit. [1] says a new version of
medit has been released (0.9.4) which fixes some critical data-loss
bugs found by lone
2008/10/8 Christian Perrier <[EMAIL PROTECTED]> wrote:
I think this is RC because it's a bug that can cause data loss. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501590#15 . If you
think this should not be release critical, then please lower the
severity. I will accept your decision a
2008/10/8 Julien Cristau <[EMAIL PROTECTED]> wrote:
> No, I'm saying this is not data loss. This is a 'it hurts when I shoot
> myself in the foot' kind of bug.
I maintain that it *is* data loss. PrtSc is a single unmodified key
press. It's not so hard to press by accident. I pressed it and it
or a long time until a more recent
version of the keymaps came out (shipped with kbd), I completely
understand; go ahead and lower the severity.
--
Jason Spiro: software/web developer, trainer, IT consultant. I support
Linux, UNIX, Windows, and more. Contact me to discuss your needs.
613-668-
sing the application to immediately
abort and dump core.
== What should have happened ==
* When you press PrtSc, the kernel should not send ^\ -- it should
either send a different key combination, or send nothing at all.
~~~
Greg Grossmeier wrote:
I can confirm this behavior in 8.10.
~~~
Jason
forwarded 321434 http://bugs.freedesktop.org/show_bug.cgi?id=17726
thanks
I reported this bug upstream, but in a different form: I titled the
bug "Please stop distributing xedit binaries until this data loss bug
in xedit is fixed", and I described both the dataloss-on-quit problem
and the double-
2008/9/22 Muammar El Khatib <[EMAIL PROTECTED]> wrote:
...
>> I am just curious: why does it no longer segfault? Is this a
>> mysteriously-disappearing problem, or was some known bug fixed which
>> made smc work?
>
> No, it is not a mysteriously-disappearing problem. The problem is that
> current
2008/9/22 Julien Cristau <[EMAIL PROTECTED]> wrotw:
> On Mon, Sep 15, 2008 at 16:24:48 -0400, Jason Spiro wrote:
>
>> severity 321434 grave
>> thanks
>>
>> Raising severity to grave as Herman and Gernot requested. I verified
>> today that the bug still ex
think?
Please use the Reply to All command to reply to this email.
Kind regards,
Jason Spiro
[1] http://osdir.com/ml/linux.debian.devel.legal/2002-08/msg00356.html
[2] http://osdir.com/ml/linux.debian.devel.legal/2002-10/msg00113.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
y.
Thanks go to Bas Wijnen for suggesting symlinking;
I am a newbie to Debian packaging and would not have thought of that
timesaving idea.
Regards,
Jason Spiro <[EMAIL PROTECTED]>
diff -ruN5 falconseye-1.9.3/debian/falconseye-data.dirs
falconseye-1.9.3-new/debian/falconseye-data.dirs
---
12 matches
Mail list logo
