Re: [FZH] F13 cjkuni-uming-fonts 在zh-CN下面的fontconfig优先级还是比wqy系列的高
by Peng Wu
关于上一个字体提议，还在review中，由于SC和TC的字体都需要修改，在等review通过后，一起放出。（SC和TC字体是不同的人维护的。也
可能随Fedora 14放出。）
有兴趣的话，可以试试http://pwu.fedorapeople.org/fonts-conf/的配置。
Feel free to comment.
On Apr 30, 1:04 pm, Super Cyper <supercyp...(a)gmail.com> wrote:
> 安装此字体后，系统默认字体变得很丑，wqy的配置不在起作用。。。。几位高手能去处理下么
>
> --
> (This is Carbon Copied from legacy mailing list fedora-cn(a)googlegroups.com.)
--
(This is Carbon Copied from legacy mailing list fedora-cn(a)googlegroups.com.)
13 years, 11 months
[FZH] [Test-Announce] 2010-05-18 - F-13-Final go / no go 会议要点
by He Rui
转载James的会议记录，F13-Final-RC3 通过了发布标准，准备发布！
He Rui
-------- Forwarded Message --------
From: James Laska <jlaska(a)redhat.com>
Reply-to: test(a)lists.fedoraproject.org
To: test-announce(a)lists.fedoraproject.org,
devel-announce(a)lists.fedoraproject.org
Subject: [Test-Announce] 2010-05-18 - F-13-Final go / no go meeting
recap
Date: Tue, 18 May 2010 20:33:01 -0400
======================================
#fedora-meeting: F-13-Final Go / No Go
======================================
Meeting started by jlaska at 23:58:40 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2010-05-18/f-13-final-eng...
.
Meeting summary
---------------
* Waiting for critical mass (jlaska, 23:59:07)
* Why are we here? (jlaska, 00:03:40)
* The purpose is to decide whether the Final release criteria have
been met (jlaska, 00:04:10)
* LINK:
https://fedoraproject.org/wiki/Fedora_13_Final_Release_Criteria
(jlaska, 00:04:16)
* Go or No Go? (jlaska, 00:04:42)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=587627 (adamw,
00:08:41)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=592345 (jlaska,
00:09:44)
* 1 remaining preupgrade bug -- fix needed by F-13 GA (jlaska,
00:13:21)
* AGREED: F-12 preupgrade packages don't impact decision to go / no go
(jlaska, 00:19:17)
* Validation test summary -
http://lists.fedoraproject.org/pipermail/test/2010-May/091001.html
(jlaska, 00:20:34)
* AGREED: F-13-RC3 meets Final release criteria - Go for launch!
(jlaska, 00:24:58)
* What's next? (jlaska, 00:25:17)
* LINK:
http://blog.internetnews.com/skerner/2010/05/fedora-13-delay-fixes-linux-...
< -- who is this guy? (ender2070, 00:27:37)
* ACTION: jlaska to sync up with hughsi to see if he needs more
testing on F-12 preupgrade (jlaska, 00:29:40)
Meeting ended at 00:30:47 UTC.
Action Items
------------
* jlaska to sync up with hughsi to see if he needs more testing on F-12
preupgrade
Action Items, by person
-----------------------
* jlaska
* jlaska to sync up with hughsi to see if he needs more testing on
F-12 preupgrade
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jlaska (69)
* adamw (27)
* Oxf13 (17)
* ender2070 (5)
* fenris02 (5)
* MiKylie (5)
* zodbot (3)
* stickster (3)
* gholms (2)
* poelcat (2)
* nirik (1)
* hno (1)
* McGiwer (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
--
Contacts
FAS Name: Rhe
Location: Beijing/UTC+8
TEL: 86-010-62608141
IRC nick: rhe #fedora-qa #fedora-zh
13 years, 11 months
[FZH] #D 我在 #autotools 學到的一個小技巧
by Caius Chance
在開發 ibus-table 的時候遇到一個小問題，到了 #autotools
上找牛請教；覺得裏面一些信息可能對大家也有用，就得到他的准許貼到郵件列表。
<kaio> hi is it usual that libdir is /usr/lib even for 64-bit sys, if I am
not putting --libdir=/usr/lib64 ?
<apostrophe> kaio: that is perfectly normal
<kaio> apostrophe⚙ so every time I should put --libdir=/usr/lib64 ?
<apostrophe> using /usr/lib64 and /usr/lib32 is something that's up to a
distribution to decide... and through using the --libdir option and changing
certain interesting settings when gcc is compiled
<apostrophe> kaio: in what context?
<kaio> and the problem that another prog which needs a .pc, should take the
responsibility to find in /usr/lib64 ?
<kaio> I have two packages: ibus-table-xingyin, ibus-table
<apostrophe> if pkg-config is compiled with --libdir=/usr/lib64, it will
look in /usr/lib64/pkgconfig instead of /usr/lib/pkgconfig by default
(AFAIK)
<apostrophe> kaio: doesn't redhat's binary package buildsystem automatically
put in --libdir=/usr/lib64 ?
<kaio> I downloaded the tarball of ibus-table and ran make
<apostrophe> kaio: is your hostmask lying? :-p
<kaio> the .pc was then installed to /usr/lib, but when I was trying to
build ibus-table-xingyin, it complained about .pc not found in /usr/lib
<kaio> apostrophe⚙ I built tar manually
<kaio> apostrophe⚙ given your info, I think I might need to have --libdir
set
<apostrophe> kaio: what file could ibus-table not find?
<apostrophe> no, --libdir will not influence pkg-config's searchpath
<kaio> could not find /usr/lib/ibus-table.pc by ibus-table-xingyin
<kaio> sth like that
<apostrophe> please pastebin the error along with the command you used to
get the error...
<kaio> ok, someone told me pkgconfig will search both /usr/lib/pkgconfig and
/usr/lib64/pkgconfig
<kaio> apostrophe⚙ ok I get back then
<apostrophe> thanks :-)
<antrik> lru: the Debian packages may have higher requirements than upstream
glibc though
<antrik> I remember some changelog entries talking about minimal kernel
versions
<apostrophe> kaio: btw, how did you become a fedora contributor?
<kaio> apostrophe⚙ I joined RH before I bacame a Fedora contrib.
<kaio> apostrophe⚙ some people I know in my community UG, they were start
being as packager.
<apostrophe> kaio: what does ``UG'' mean?
<lru> user group?
<apostrophe> ah
<kaio> apostrophe⚙ are you a dev of certain software?
<apostrophe> kaio: I would say I sort-of am, but I haven't really written
any chunk of code myself before ;-)
<kaio> apostrophe⚙ oic
<kaio> apostrophe⚙ I thought who managed how to use autotools, also managed
how to dev.
<kaio> because autotools is too difficult to me
<apostrophe> kaio: oh, I'm not in any way associated with autotools devs;
also, I've done more work trying to fix package's autotools setups than to
write actual software ;-)
<apostrophe> kaio: problem is, I don't understand your problem yet
<apostrophe> kaio: may you show me the code that ibus-table uses to install
ibus-table.pc ?
<kaio> github.com/kaio/ibus-table
<kaio> github.com/kaio/ibus-table-xingyin
<apostrophe> cool
<apostrophe> kaio: does /usr/lib64/pkgconfig/ibus-table.pc exist?
<apostrophe> kaio: also, files like ``missing'' and ``install-sh'' don't
belong in your source-code repository
<kaio> hmm
<kaio> apostrophe⚙ which one you are talking about now? ibus-table or
ibus-table-xingyin?
<kaio> /usr/lib/pkgconfig/ibus-table.pc exist, may be I didnt put
--libdir=/usr/lib64 when I ran make manually
<apostrophe> kaio: ibus-table-xingyin has some extra files in it that are
normally autogenerated
<apostrophe> kaio: do other files exist in /usr/lib/pkgconfig ?
<apostrophe> if ibus-table.pc is the _only_ file in there, it must be the
wrong directory
<kaio> apostrophe⚙ I actually a retard on autotools, I have no idea which
are generated ones which I should remove
<kaio> apostrophe⚙ ibus-table.pc is one of the file created in ibus-table
repo
<kaio> it has the code of ibus-table also
<apostrophe> kaio: only ``missing'' and ``install-sh'' need to be removed
for that repo ;-)
<kaio> apostrophe⚙ thx for info
<apostrophe> kaio: you should _never_ use ``./configure --prefix=/usr; make
install'' on a fedora system; you should always use the package manager for
stuff like that
<kaio> why? even I am just doing dev?
<apostrophe> kaio: even then
<apostrophe> if you want to test it on your system rather than just running
it out of its source directly, you should roll a quick rpm and install that
<kaio> could you tell me reason?
<kaio> pls
<apostrophe> because if you install files into /usr without using RPM,
you'll potentially damage already installed one and clutter your system with
orphaned files
<apostrophe> you may end up never being able to uninstall every bit of your
program when you change what files your package installs or when you
increment library versions
<kaio> apostrophe⚙ okay
<apostrophe> that can both cause trouble on your system in the future and
make it so that your program works on your machine but doesn't work on a
friend's machine
<kaio> hmm
<kaio> apostrophe⚙ you are right, I've just been too lazy XD
<apostrophe> :-p
<apostrophe> what I do is something like this:
``PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:${HOME}/lib/pkgconfig" ./configure
--prefix="${HOME}" ; make install -j -l4''
<kaio> apostrophe⚙ sometimes it just take too long is I just want to do some
minor try and error..
<apostrophe> then I add ${HOME}/bin to my PATH environment variable (in I
think ~/.bashrc)
<apostrophe> kaio: I understand, I just offered an alternative which will go
faster in most cases :-)
<kaio> apostrophe⚙ sure sure, thx, I am still digesting your command above
<kaio> apostrophe⚙ so it install to my home dir?
<kaio> very interesting
<apostrophe> yes, I do that on stuff that I'm ``developing'' ;-)
<kaio> will the sys pick up that dir instead?
<apostrophe> the PKG_CONFIG_PATH variable tells pkg-config were to look for
*.pc files
<kaio> its the first time I heard this idea
<kaio> ok I should give it a try again tonight then :)
<kaio> BTW, your info is so valuable, could I forward the log to the mailing
list?
<apostrophe> kaio: if you think my information is valuable in that way,
that's fine with me
<apostrophe> :-)
<kaio> appreciate, catch you later
--
Caius 'kaio' Chance / かいお
[Email/Gtalk] Caius.Chance(a)gmail.com | [IRC] kaio at chat.freenode.net
[Twitter] K410 | [Blog] blog.kaio.net | [Fedora]
fedoraproject.org/wiki/User:kaio
13 years, 11 months
[FZH] #D Fedora下嵌入式开发JTAG烧写工具
by cheng chen
折腾了好久，今天下午终于干掉了板子上预装的WINCE，又点亮了我的板子上的LED灯，用H-JTAG烧的～
问一下, Linux底下有没有什么好用JTAG烧写工具。arm-linux-gcc编的译，再到windows下烧好烦人啊～我的NAND
FLASH是K9F1G08的那个SJF2440不支持～
有别的好工具顺便推荐一下啊，谢谢～
--
Cheng(诚)
13 years, 11 months
[FZH] Fedora 13 Final RC Validation Test Summary
by He Rui
Greetings,
Thanks for both testers and developers' hard work on F-13-Final RC
validation test events. RC3 were finally tested and the test results are
summarized as below. For a detailed results, please refer to the Final
RC results page[1].
************************** Installation *****************************
591829 NEW - disabling /dev/loop0 LOOP_CLR_FD failed: 16
585006 NEW - livecd-creator creates i386 and x86_64 ISOs which are
larger than indicated by the ISO header
592345 NEW - preupgrade-1.1.6-1.fc12 adds extra spaces to grub.conf,
results in failed upgrade
505189 MODIFIED - Going back to repo UI screen and and modifying
Installation Repo causes traceback
587627 ON_QA - Kickstart file is not generated when no space for
install.img
589250 VERIFIED - iSCSI root install+boot fails in Fedora 13. Latest
iscsi-initiator-utils required
590518 CLOSED DUPLICATE - KeyError: <yuminstall.AnacondaYumRepo object
at 0x7f459004d7d0>
590640 CLOSED WONTFIX - SystemError: (22, 'Invalid argument')
576082 CLOSED ERRATA - Words did not translate in F13 beta during
install
580378 CLOSED RAWHIDE - Crash when no bootloader detected and upgrading
a system
591776 ASSIGNED - ‘Space’，‘Enter’, and arrow keys don't work in VNC
************************** Desktop *********************************
N/A
The Go/No Go meeting[2] will be held soon to decide if it meets the
final release criteria, please keep attention on it.
Many Thanks,
Hurry
[1]
https://fedoraproject.org/wiki/Category:Fedora_13_Final_RC_Test_Results
[2]
http://poelstra.fedorapeople.org/schedules/f-13/f-13-quality-tasks.html
--
Contacts
FAS Name: Rhe
Location: Beijing/UTC+8
TEL: 86-010-62608141
IRC nick: rhe #fedora-qa #fedora-zh
13 years, 11 months
