Martin-Éric Racine wrote:
su, 2005-11-20 kello 18:14 -0800, Steve Langasek kirjoitti:
On Sun, Nov 20, 2005 at 11:43:47PM +0200, Martin-Éric Racine wrote:
su, 2005-11-20 kello 10:16 -0800, Steve Langasek kirjoitti:
On Sun, Nov 20, 2005 at 07:29:00PM +0200, Martin-Éric Racine wrote:
Given how Unicode compliance is a release goal for Etch, having libfribidi0 in Recommends is not sufficient; it
really must show in Depends.
No. "Unicode support" refers to applications functioning in a UTF-8 locale
as correctly as they do in a single-byte locale.
And it indeed doesn't function correctly here. Not putting libfribidi0
as Depends breaks newt operation on UTF-8 locales, which in turns also
affects debconf. Without it, debconf does NOT work correctly under a
UTF-8 locale using the 'dialog' front-end.
Then you should have said that (and in a separate bug report, no less)
instead of claiming that dependencies were missing. If UTF-8 isn't working
right without lifribidi0, then something's buggy in the UTF-8 support,
because libfribidi0 should *not* be required for this.
You really ought to check the whole thread for this bug before mailing.
This bug already was about the missing dependency, which the maintainer
"solved" by adding a Recommends, instead of a Depends.
The bug was fixed by fixing a segfault in libslang2 that occured when
libfribidi was not
present. That fixed, it is now possible for newt to have a Recommends:
rather
than a Depends:, hence that was changed simultaneously: it was not the
'fix'.
newt works in UTF-8 for non-BIDI languages. I am reluctant to add a
dependency on
libfribidi and inflate base for non-BIDI users: it makes using Debian
as an embedded
system much harder. A better solution I think would be to make sure
libfribidi
is installed when BIDI languages are chosen on the installer, or when X
/ graphical
console is installed.
Regards
Alastair
|
