[Fedora-i18n-bugs] [Bug 569352] Broken dependencies for 1:openoffice.org-langpack-en-3.2.0-12.7.fc13.x86_64
by Red Hat Bugzilla
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=569352
Féliciano Matias <feliciano.matias(a)free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |feliciano.matias(a)free.fr
--- Comment #5 from Féliciano Matias <feliciano.matias(a)free.fr> 2010-03-06 10:17:13 EST ---
(In reply to comment #4)
> As I suggested in [url=https://bugzilla.redhat.com/show_bug.cgi?id=568784]bug
> 568784[/url] I think this error is only related to openoffice 3.2.0-12.7. I had
> this problem trying to update from 3.2.0-12.6 to 3.2.0-12.7, but not to
> 3.2.0-12.8.
>
> Today I also updated from 3.2.0-12.8 to 3.2.0-12.9 without any problem in
> dependencies check.
>
> I suggest you to do a yum erase openoffice.org-langpack-en, then a yum update
> will update openoffice and install the needed langpack.
I have this problem when updating from openoffice.org 3.2.0-12.9.fc13 to
3.2.0-12.10.fc13.
---------------------------------------------------
# cat /etc/yum/pluginconf.d/langpacks.conf
[main]
enabled=1
langpack_locales = en, fr
# LANG=C yum update
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en, fr to language list
................
Installing langpack for openoffice.org-core
Adding openoffice.org-langpack-en to transaction
Adding openoffice.org-langpack-en to transaction
Adding openoffice.org-langpack-fr to transaction
Adding openoffice.org-langpack-fr to transaction
Installing langpack for hunspell
Adding hunspell-en to transaction
Adding hunspell-fr to transaction
--> Running transaction check
---> Package hunspell-en.noarch 0:0.20090216-7.fc12 set to be updated
---> Package hunspell-fr.noarch 0:3.5-1.fc13 set to be updated
---> Package openoffice.org-langpack-en.x86_64 1:3.2.0-12.9.fc13 set to be
updated
--> Processing Dependency: openoffice.org-core = 1:3.2.0-12.9.fc13 for package:
1:openoffice.org-langpack-en-3.2.0-12.9.fc13.x86_64
---> Package openoffice.org-langpack-fr.x86_64 1:3.2.0-12.9.fc13 set to be
updated
--> Processing Dependency: openoffice.org-core = 1:3.2.0-12.9.fc13 for package:
1:openoffice.org-langpack-fr-3.2.0-12.9.fc13.x86_64
--> Finished Dependency Resolution
Error: Package: 1:openoffice.org-langpack-fr-3.2.0-12.9.fc13.x86_64 (fedora)
Requires: openoffice.org-core = 1:3.2.0-12.9.fc13
Removing: 1:openoffice.org-core-3.2.0-12.9.fc13.x86_64 (@fedora)
Installing: 1:openoffice.org-core-3.2.0-12.10.fc13.x86_64
(updates-testing)
Error: Package: 1:openoffice.org-langpack-en-3.2.0-12.9.fc13.x86_64 (fedora)
Requires: openoffice.org-core = 1:3.2.0-12.9.fc13
Removing: 1:openoffice.org-core-3.2.0-12.9.fc13.x86_64 (@fedora)
Installing: 1:openoffice.org-core-3.2.0-12.10.fc13.x86_64
(updates-testing)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
---------------------------------------------------
It's OK if I disable yum-langpacks (openoffice.org-langpack-fr and
openoffice.org-langpack-en are updated).
--
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.
14 years, 1 month
[Fedora-i18n-bugs] [Bug 565710] New: %{_bindir}/fbterm is not working for normal users unless a setcap is done.
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: %{_bindir}/fbterm is not working for normal users unless a setcap is done.
https://bugzilla.redhat.com/show_bug.cgi?id=565710
Summary: %{_bindir}/fbterm is not working for normal users
unless a setcap is done.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: fbterm
AssignedTo: dchen(a)redhat.com
ReportedBy: cchance(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
ibus-fbterm is not working except a setcap is done as follows:
"sudo setcap cap_sys_tty_config+ep /path/to/fbterm"
I have added this in the %post of ibus-fbterm, but I thought changes in fbterm
pkg is more appropriate.
Version-Release number of selected component (if applicable):
fbterm-1.6-1.fc12.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. install fbterm
2. install ibus-fbterm
(http://kaio.fedorapeople.org/pkgs/ibus-fbterm-0.9.1-5.fc12.src.rpm However, it
has setcap in the %post already.
3. execute 'ibus-fbterm-launch'
Actual results:
ibus-fbterm complained about capability problems.
Expected results:
ibus-fbterm is started properly.
Additional info:
`man fbterm` has this section:
SECURITY NOTES
FbTerm tries to change linux kernel key map table to setup shortcuts,
which requires SYS_TTY_CONFIG capability from kernel version 2.6.15. It
means FbTerm should be a setuid 0 program to allow non-root users to use
shortcuts. FbTerm only switches to root privilege temporarily when
changing key map table, we believe it’s pretty much free from security
problems.
If you really don’t like this and not use VESA support, and have a linux
kernel with file system capabilities enabled, which allow user to give
binaries a subset of root’s powers without using setuid 0 (official kernel
2.6.27 includes it), you can run command "sudo setcap ’cap_sys_tty_config+ep’
/path/to/fbterm".
--
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.
14 years, 1 month
[Fedora-i18n-bugs] [Bug 569430] New: Wrong directory ownership
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Wrong directory ownership
https://bugzilla.redhat.com/show_bug.cgi?id=569430
Summary: Wrong directory ownership
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: man-pages-ko
AssignedTo: dchen(a)redhat.com
ReportedBy: ovasik(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Based on the check done on F-12 system, your package owns directories owned by
filesystem.
This is not allowed by Fedora policies.
See
http://fedoraproject.org/wiki/Packaging/Guidelines#File_and_Directory_Own...
for details.
(Sub)package man-pages-ko:
/usr/share/man/ko/man6
/usr/share/man/ko/man7
/usr/share/man/ko/man1
/usr/share/man/ko
/usr/share/man/ko/man3
/usr/share/man/ko/man2
/usr/share/man/ko/man8
/usr/share/man/ko/man5
/usr/share/man/ko/man4
This is autogenerated bugzilla, I'm sorry if the problem is already fixed or
reported. Additionally I apologize if that directory ownership was requested
earlier by some bugzilla (some directories were probably added into filesystem
package later, so your package should no longer own that directory).
--
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.
14 years, 1 month
[Fedora-i18n-bugs] [Bug 568613] Plan to change wqy-microhei-fonts and wqy-zenhei-fonts fontconfig conf files.
by Red Hat Bugzilla
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=568613
--- Comment #6 from Qianqian Fang <fangqq(a)gmail.com> 2010-03-05 11:54:30 EST ---
I responded by email last night, but it did not show up, so I paste my response
again.
> --- Comment #5 from Peng Wu<pwu(a)redhat.com> 2010-03-04 21:19:09 EST ---
> Actually what we want to change is as following:
> 1. Make wqy-zenhei as default for Simplified Chinese users,
> Make UMing as default for Traditional Chinese users.
>
I am not sure which language did you use in
the past, but I do see a couple of problems here:
First of all, Zen Hei and UMing are fonts of different styles.
one is Sans, one is Serif (let's ignore the embedded bitmaps
for a second). They are more like Dejavu Sans vs. Dejavu Serif,
than like Droid Sans Fallback vs. Droid Sans Japanese.
They mean to represent different types of visual elements
in the text layout (and used simultaneously), and not
meant to represent the same information for different languages.
Second, UMing/UKai are not "consistently" traditional
Chinese styled. For most glyphs, they are rather mainland
Chinese styled. It does contain traditional Chinese styled
characters as merged from AR PL Mingti2L Big5, but they
are not consistent, for example, all the components
with "角" are SC-styled (唃嘝嘴嶰廨懈斛桷槲檞澥确繲薢角觙
觚觛觜觞觟觠解觥觧觫觭觯觲觳觺觻邂鵤); many "骨" components
are TC, but several are SC, such as "骶骺髅髋髌鹘"; all
the "今" components are SC, such as in "今仱侺吟妗岑岒庈
忴扲昑枔棽涔琌琴矜笒紟耹肣芩蚙衿軡鈐钤霒霠黔"; almost
all chars with radical "黑" are SC, except "黓" is TC.
I can not give all of the examples, there are so many
inconsistencies. If you are interested, you can download a copy of
Unicode code chart (second column) and compare with Uming glyphs:
http://unicode.org/charts/PDF/U4E00.pdf
> When user choose "Sans" / "Serif" / "MonoSpace":
> 1. In zh_CN locale, it will use "Zen Hei" as default,
> 2. In zh_TW locale, it will use "UMing" as default.
>
Personally, I like the way Ubuntu handles this: Zen Hei is
the default CJK Sans font, and UMing is the default Serif font.
On LiveCDs where space is limited, only one font is installed,
before 9.10, it was UMing, after 9.10, it was ZenHei.
> If you installed both zenhei and Uming/Ukai, I think it will show in font list
> when querying with fontconfig.
>
> In brief, we just want to change the default fonts for SC and TC users. The
> font styles is still available when the fonts is installed.
>
At this point, there is no TC-shaped fonts available. So,
you can't really solve this by splitting zenhei/uming,
as both of them are mostly SC-styled Unicode fonts. I do have the plan
to create TC variant of ZenHei, and Arne also split the font
names to UMing CN/UMing TW, but there are lot of things
need to be done to make them TC consistent.
> Currently I am trying to change font conf to achieving this, but meet some
> problems. Maybe you could help me on this.
>
As I said, set zenhei/microhei for sans, set uming for serif, that's
probably the best we can do. In addition, giving users an easy
way to switch between bitmaps and anti-aliased glyphs is probabily
a much useful feature than setting SC/TC with separate default fonts.
--
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.
14 years, 1 month
[Fedora-i18n-bugs] [Bug 570680] New: ibus-anthy support NICOLA-F and NICOLA-A thumb-shift layouts.
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: ibus-anthy support NICOLA-F and NICOLA-A thumb-shift layouts.
https://bugzilla.redhat.com/show_bug.cgi?id=570680
Summary: ibus-anthy support NICOLA-F and NICOLA-A thumb-shift
layouts.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus-anthy
AssignedTo: tfujiwar(a)redhat.com
ReportedBy: tfujiwar(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, tfujiwar(a)redhat.com,
phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Recently thumb-shift layouts are enhanced to support NICOLA-F and NICOLA-A
thumb-shift layouts in upstreamed community.
I think it's better to import the features for rawhide before deliver the new
tarball in upstreamed community and integrate it in f13.
--
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.
14 years, 1 month