Josselin Mouette wrote:
Plus, unless I missed something, you are wrong I send example with
lang=fr...@utf8 set and the bug still happens. See message #29.
It is not my problem either if you think a '@' and a '.' are the same
characters. When I mean 'fr_FR.UTF-8', I don’t mean any
Le mercredi 24 décembre 2008 à 10:24 +0100, Eric Valette a écrit :
2 r-ptxp-ceva6380:~-mkdir /tmp/toto
3 r-ptxp-ceva6380:~-cd /tmp/toto
4 r-ptxp-ceva6380:/tmp/toto-echo text AA1-XXxxxé
5 r-ptxp-ceva6380:/tmp/toto-export LANG=fr_FR.utf8
6 r-ptxp-ceva6380:/tmp/toto-icedove
Josselin Mouette wrote:
Le mercredi 24 décembre 2008 à 10:24 +0100, Eric Valette a écrit :
2 r-ptxp-ceva6380:~-mkdir /tmp/toto
3 r-ptxp-ceva6380:~-cd /tmp/toto
4 r-ptxp-ceva6380:/tmp/toto-echo text AA1-XXxxxé
5 r-ptxp-ceva6380:/tmp/toto-export LANG=fr_FR.utf8
6
On Wed, Dec 24, 2008, Eric Valette wrote:
4 r-ptxp-ceva6380:/tmp/toto-echo text AA1-XXxxxé
Your shell is creating invalid UTF-8 filenames; when you do something
like:
% export LANG=foobar
% echo foo somefilename-with-8bits-chars
the bytes you send to your shell over your
Loïc Minier wrote:
On Wed, Dec 24, 2008, Eric Valette wrote:
4 r-ptxp-ceva6380:/tmp/toto-echo text AA1-XXxxxé
Your shell is creating invalid UTF-8 filenames; when you do something
like:
% export LANG=foobar
% echo foo somefilename-with-8bits-chars
the bytes
severity 509582 critical
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Le mardi 23 décembre 2008 à 18:52 +0100, Eric Valette a écrit :
Bug#509582: still puszed how a non maintainer handled the criticity
while not responding to problem
1) I am one of the maintainers.
2) This bug is not critical. This severity means “breaks the whole
system” or “root security
Josselin Mouette wrote:
Le mardi 23 décembre 2008 à 18:52 +0100, Eric Valette a écrit :
Bug#509582: still puszed how a non maintainer handled the criticity
while not responding to problem
1) I am one of the maintainers.
2) This bug is not critical. This severity means “breaks the whole
Eric Valette wrote:
Josselin Mouette wrote:
1) I am one of the maintainers.
Fix the packages maintainer page then. You are not listed!
--eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Eric Valette wrote:
Josselin Mouette wrote:
Le mardi 23 décembre 2008 à 18:52 +0100, Eric Valette a écrit :
Bug#509582: still puszed how a non maintainer handled the criticity
while not responding to problem
1) I am one of the maintainers.
2) This bug is not critical. This severity means
Hi
On Tue, Dec 23, 2008, Eric Valette wrote:
NO NO NO
Cool down
* only occurs on systems with legacy locale settings
* doesn’t occur all the time, unless you are always using
MALLOC_CHECK_=2
On experimental libc, apprently this is default. I do not set it
Loïc Minier wrote:
Ok, so if it's only in combination with the experimental libc, or with
an explicit MALLOC_CHECK_=2 export, it's fine to lower the severity a
little; this still is either important or serious.
Sure.
Right, but these aren't completely unrelated in that they use this
Le mardi 23 décembre 2008 à 19:47 +0100, Eric Valette a écrit :
2) This bug is not critical. This severity means “breaks the whole
system” or “root security hole”. This bug:
NO NO NO: breaks unrelated software. Look at the criteria given using
reportbug!
Which unrelated software does it
Eric Valette wrote:
Loïc Minier wrote:
Ok, so if it's only in combination with the experimental libc, or with
an explicit MALLOC_CHECK_=2 export, it's fine to lower the severity a
little; this still is either important or serious.
Sure.
One more comment: you do not see the *effect* of
Josselin Mouette wrote:
Which unrelated software does it break?
Using the same kind of argument because a program use libc and libc is
broken (e.g bad code in a specific function), is is not a critical bug
because all program are supposed to use libc?
Fine. And if your system doesn’t work
severity 509582 important
thanks
Le mardi 23 décembre 2008 à 21:07 +0100, Eric Valette a écrit :
Josselin Mouette wrote:
Which unrelated software does it break?
Using the same kind of argument because a program use libc and libc is
broken (e.g bad code in a specific function), is is not
16 matches
Mail list logo
