Bug#386299: Is lack of UTF support an RC bug? [was: Bug#386299: ekg2: Plugin/program compilation option mismatch]

2006-09-07 Thread Thomas Viehmann
Marcin Owsiany wrote:
 Who decided that we should just drop them all? After all generating a
 non-UTF locale and setting an environment variable isn't a very
 difficult workaround? I mean, when has lack of UTF support become an
 RC-bug? Charset support is not even mentioned in the policy, other than
 for debian/changelog.
There's quite a way from not properly supporting UTF, possibly mangling
characters to needs workaround for most installs otherwise being
completely unusable with opaque error message. The latter doesn't
really sound like a releasable state to me.
I think looking at the issue with the criterium the distribution better
not have a lot of packages with this type of fault or it's a completly
useless junk collection of packages one can see a big red blinking RC
bug sign for this specific bug (as opposed to all UTF problems being RC).

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#386299: ekg2: Plugin/program compilation option mismatch

2006-09-07 Thread Steve Langasek
severity 386299 serious
thanks

On Wed, Sep 06, 2006 at 06:14:55PM +0100, Marcin Owsiany wrote:

 Unicode support in ekg2 is highly experimental and not yet supported
 upstream, therefore the debian package is built without UTF-8 support.

 On Wed, Sep 06, 2006 at 05:56:17PM +0200, Tristan Seligmann wrote:
  Attempting to run ekg2 yields the following:

 Try running it in some iso-8859 locale.

That's not an acceptable answer, given that almost all locales for etch will
be Unicode by default.  This makes the package unreleasable.  Of course, the
package seems to only be in experimental at all, so I don't see why you
would bother to downgrade the bug...

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#386299: Is lack of UTF support an RC bug? [was: Bug#386299: ekg2: Plugin/program compilation option mismatch]

2006-09-07 Thread Steve Langasek
On Thu, Sep 07, 2006 at 06:25:26PM +0100, Marcin Owsiany wrote:
   Try running it in some iso-8859 locale.

  That's not an acceptable answer, given that almost all locales for etch will
  be Unicode by default.  This makes the package unreleasable.  Of course, the
  package seems to only be in experimental at all, so I don't see why you
  would bother to downgrade the bug...

 It doesn't matter for ekg2, which will stay in experimental for quite a
 while I'm afraid, but it is important for at least two other of my
 packages (which are in etch) which don't support UTF-8 at all. And I'm
 reasonably sure they are not the only packages in etch which don't
 support UTF.

 Who decided that we should just drop them all? After all generating a
 non-UTF locale and setting an environment variable isn't a very
 difficult workaround? I mean, when has lack of UTF support become an
 RC-bug? Charset support is not even mentioned in the policy, other than
 for debian/changelog.

 Don't get me wrong, I'm not against UTF-8, but just dropping everything
 that doesn't support it, without a former warning, sounds ridiculous.

It's already been pointed out that there's a big difference between won't
display non-ASCII characters correctly in a UTF-8 locale and won't work at
all in a UTF-8 locale.  There's no excuse for the latter; and as Unicode
locales *are* the default for almost all new installs of etch, this does
make such a package mostly unusable.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Bug#386299: Is lack of UTF support an RC bug? [was: Bug#386299: ekg2: Plugin/program compilation option mismatch]

2006-09-07 Thread Marcin Owsiany
On Thu, Sep 07, 2006 at 02:46:16AM -0700, Steve Langasek wrote:
 severity 386299 serious
 thanks
 
 On Wed, Sep 06, 2006 at 06:14:55PM +0100, Marcin Owsiany wrote:
 
  Unicode support in ekg2 is highly experimental and not yet supported
  upstream, therefore the debian package is built without UTF-8 support.
 
  On Wed, Sep 06, 2006 at 05:56:17PM +0200, Tristan Seligmann wrote:
   Attempting to run ekg2 yields the following:
 
  Try running it in some iso-8859 locale.
 
 That's not an acceptable answer, given that almost all locales for etch will
 be Unicode by default.  This makes the package unreleasable.  Of course, the
 package seems to only be in experimental at all, so I don't see why you
 would bother to downgrade the bug...

It doesn't matter for ekg2, which will stay in experimental for quite a
while I'm afraid, but it is important for at least two other of my
packages (which are in etch) which don't support UTF-8 at all. And I'm
reasonably sure they are not the only packages in etch which don't
support UTF.

Who decided that we should just drop them all? After all generating a
non-UTF locale and setting an environment variable isn't a very
difficult workaround? I mean, when has lack of UTF support become an
RC-bug? Charset support is not even mentioned in the policy, other than
for debian/changelog.

Don't get me wrong, I'm not against UTF-8, but just dropping everything
that doesn't support it, without a former warning, sounds ridiculous.

regards,

Marcin
-- 
Marcin Owsiany [EMAIL PROTECTED] http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216


signature.asc
Description: Digital signature


Bug#386299: ekg2: Plugin/program compilation option mismatch

2006-09-06 Thread Tristan Seligmann
Package: ekg2
Version: 20060826+0920-1
Severity: grave
Justification: renders package unusable

Attempting to run ekg2 yields the following:

plugin ncurses cannot be loaded because of mishmashed compilation...
program compilated with: --enable-unicode
 plugin compilated with: --disable-unicode
plugin gtk cannot be loaded because of mishmashed compilation...
program compilated with: --enable-unicode
 plugin compilated with: --disable-unicode
No UI-PLUGIN!
plugin jabber cannot be loaded because of mishmashed compilation...
program compilated with: --enable-unicode
 plugin compilated with: --disable-unicode
plugin gg cannot be loaded because of mishmashed compilation...
program compilated with: --enable-unicode
 plugin compilated with: --disable-unicode
plugin irc cannot be loaded because of mishmashed compilation...
program compilated with: --enable-unicode
 plugin compilated with: --disable-unicode
Error opening script variable file..

Without being able to load the UI or network plugins, this seems to
render the package essentially non-functional.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages ekg2 depends on:
ii  libaspell15  0.60.4-4GNU Aspell spell-checker runtime l
ii  libatk1.0-0  1.12.1-1The ATK accessibility toolkit
ii  libc62.3.6.ds1-2 GNU C Library: Shared libraries
ii  libcairo21.2.4-1 The Cairo 2D vector graphics libra
ii  libexpat11.95.8-3.2  XML parsing C library - runtime li
ii  libfontconfig1   2.3.2-7 generic font configuration library
ii  libgadu3 1:1.7~rc2-1 Gadu-Gadu protocol library - runti
ii  libglib2.0-0 2.10.3-3The GLib library of C routines
ii  libgnutls13  1.4.2-1 the GNU TLS library - runtime libr
ii  libgpmg1 1.19.6-22   General Purpose Mouse - shared lib
ii  libgtk2.0-0  2.8.20-1The GTK+ graphical user interface 
ii  libjpeg626b-13   The Independent JPEG Group's JPEG 
ii  libncurses5  5.5-2   Shared libraries for terminal hand
ii  libpango1.0-01.12.3-2Layout and rendering of internatio
ii  libperl5.8   5.8.8-6.1   Shared Perl library
ii  libsqlite3-0 3.3.7-1 SQLite 3 shared library
ii  libssl0.9.8  0.9.8b-2SSL shared libraries
ii  libungif4g   4.1.4-2 shared library for GIF images (run
ii  libx11-6 2:1.0.0-8   X11 client-side library
ii  libxcursor1  1.1.5.2-5   X cursor management library
ii  libxext6 1:1.0.0-4   X11 miscellaneous extension librar
ii  libxfixes3   1:3.0.1.2-4 X11 miscellaneous 'fixes' extensio
ii  libxi6   1:1.0.0-5   X11 Input extension library
ii  libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii  libxosd2 2.2.14-1.3  X On-Screen Display library - runt
ii  libxrandr2   2:1.1.0.2-4 X11 RandR extension library
ii  libxrender1  1:0.9.0.2-4 X Rendering Extension client libra
ii  python   2.4.3-11An interactive high-level object-o
ii  python-central   0.5.5   register and build utility for Pyt
ii  python2.42.4.3-8 An interactive high-level object-o
ii  zlib1g   1:1.2.3-13  compression library - runtime

Versions of packages ekg2 recommends:
ii  perl  5.8.8-6.1  Larry Wall's Practical Extraction 

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#386299: ekg2: Plugin/program compilation option mismatch

2006-09-06 Thread Marcin Owsiany
severity 386299 minor
retitle 386299 Fails when run in UTF-8 environment
thanks

Unicode support in ekg2 is highly experimental and not yet supported
upstream, therefore the debian package is built without UTF-8 support.

On Wed, Sep 06, 2006 at 05:56:17PM +0200, Tristan Seligmann wrote:
 Attempting to run ekg2 yields the following:

Try running it in some iso-8859 locale.

 plugin ncurses cannot be loaded because of mishmashed compilation...
 program compilated with: --enable-unicode
  plugin compilated with: --disable-unicode

This is not true, everything was built without unicode support. The
messages need to be fixed.

Marcin
-- 
Marcin Owsiany [EMAIL PROTECTED] http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]