Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=480885
--- Comment #5 from Parag <pnemade(a)redhat.com> 2009-01-27 03:27:25 EDT ---
Just found that actually hne_IN was already successfully present in previous
glibc build. So this now looks upstream issue.
Ohh found some more messages in build.log for other indic languages
incomplete set of locale files in "as_IN.utf8"
incomplete set of locale files in "bn_BD"
incomplete set of locale files in "mai_IN"
Sorry for not writing all my observations in single comment.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=480885
--- Comment #4 from Parag <pnemade(a)redhat.com> 2009-01-27 03:20:17 EDT ---
Just checked build.log of glibc-2.9.90-2.fc11 =>
http://kojipkgs.fedoraproject.org/packages/glibc/2.9.90/2/data/logs/i386/bu…
and found
=========================
Adding hi_IN
Adding hne_IN
incomplete set of locale files in "hi_IN"
incomplete set of locale files in "hne_IN"
============================
so something gone wrong while adding hne_IN locale in usptream.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=480885
Parag <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rranjan(a)redhat.com
Summary|setlocale failed to set 3 |[hi_IN] [mai_IN] setlocale
|letter locale (anaconda |failed to set hi_IN as well
|fails to parse 3 letter |as mai_IN languages.
|locale with python 2.6) |
--- Comment #3 from Parag <pnemade(a)redhat.com> 2009-01-27 02:47:51 EDT ---
Okay So I got some more in depth information about this bug. A simple setlocale
program fails to set for hi_IN as well as mai_IN locale but setlocale can set
any other indic language.
When I check for output of "locale -a| grep hi" i got nothing on my rawhide
machine. same for mai language. But for other indic languages translations as
well as setlocale() works fine.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=480885
Parag AN(पराग) <panemade(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |panemade(a)gmail.com
Summary|anaconda fails to parse 3 |setlocale failed to set 3
|letter locale with python |letter locale (anaconda
|2.6 |fails to parse 3 letter
| |locale with python 2.6)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=429901
Padmanabhan V. K. <bugzillas+padREMOVETHISdu(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzillas+padREMOVETHISdu@g
| |mail.com
--- Comment #4 from Padmanabhan V. K. <bugzillas+padREMOVETHISdu(a)gmail.com> 2009-01-26 17:29:41 EDT ---
Using ZWJ as in bug 451203 for the combination "U+0c2f U+0c4d U+0c30 U+0c4d",
pango uses the character sequence "U+0c2f U+0c4d U+0c30 U+0c4d U+200d" as is
instead of the reordered sequence "U+0c2f U+0c30 U+0c4d U+0c4d." With the
former sequence the glyphs added are "U+0c2f+halanth below-base-U+0c30 U+200d"
whereas with the latter we get "U+0c2f below-base-U+0c30 U+0c4d" followed by
substitution of below-base-U+0c30 with a wider glyph due to the context of
U+0c2f. Now the rendering of "U+0c2f wide-below-base-U+0c30 U+0c4d" can be
fixed as suggested in bug 476427 to get "U+0c2f+halanth wide-below-base-U+0c30"
which isn't possible with ZWJ.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Missing obsoletes statement for %{fontname}-common-fonts
https://bugzilla.redhat.com/show_bug.cgi?id=481279
Summary: Missing obsoletes statement for
%{fontname}-common-fonts
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: baekmuk-ttf-fonts
AssignedTo: cchance(a)redhat.com
ReportedBy: quentin(a)armitage.org.uk
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, cchance(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
Attempting yum update of baekmuk-ttf-fonts-common fails sating conflict against
baekmuk-ttf-common-fonts 2.2.13
Version-Release number of selected component (if applicable):
2.2.15
How reproducible:
Always
Steps to Reproduce:
1.yum update
2.
3.
Actual results:
Reports conflict eror described above
Expected results:
Successful update
Additional info:
in the %package -n %{fontname}-fonts-common section of the .spec file, should
there be an obsoletes %{fontname}-common-fonts < 2.2.13(or is it 2.2.14 -
common-fonts was last in version 2.2.13).
I also noticed that when I had 2.2.13 installed, there was a
baekmuk-fonts-common version 2.2.10 still installed, and presumably that should
have been obsoleted by a previous update?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=466193
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=462711
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=461139
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.