[Bug 457947] Review Request: 69oldstandard-fonts - Old Standard Fonts
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=457947
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|nicolas.mailhot(a)laposte.net |
Flag| |needinfo?(sanjay_ankur@yaho
| |o.co.in)
--- Comment #13 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> 2008-10-27 17:54:10 EDT ---
This one is much nicer but you need to work on renaming the font at build time
inside the sfds and also to work on the fontconfig rules. Please take some time
with Pablo on those.
Also it needs the same doc fix as bonveno.
--
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.
15 years, 8 months
[Bug 457955] Review Request: bonvenocf-fonts - BonvenoCF font
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=457955
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag| |needinfo?(sanjay_ankur@yaho
| |o.co.in)
--- Comment #6 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> 2008-10-27 17:42:17 EDT ---
(In reply to comment #4)
> I dint know how to tackle point 8 9 10
>
> I dont think i know enough for sposnorship yet.
Ankur, there's no need to rush, and we'll do it as slowly as you're comfortable
with. Baby steps are good.
If my requests are difficult to understand there's no shame at all asking for
clarifications on the list. Someone else may answer using different words than
mine and anyway that creates some on-line documentation for others new
packagers (the list is international so no one will object if you have some
problems with the pidgin English I use)
Likewise, if you find some part of the wiki documentation obscure, just ask for
help on the list, and propose a re-wording after you've understood the point.
That's another great way to understand packaging and getting sponsored.
If you're a bit intimidated by a public mailing list you can exchange private
mails with Martin-Gomez Pablo or try to meet in an irc channel. He's also a
novice packager, even if he's got a little more experience than you, so you may
be a bit more comfortable exchanging tips with him.
That being said:
You still need to work on 14 8 9 10. Since you've written you've taken care of
8 9 10, you may have uploaded the wrong package version (or I can elaborate if
you don't understand those points)
15. Also, you need to Buildrequire fontforge if you use it, otherwise the
package won't build in koji or mock. Since you're not sponsored yet you can't
test in koji so I strongly suggest installing mock on your system
(http://fedoraproject.org/wiki/Projects/Mock) It's a great packager helper.
16. running rpmlint on the result produces those warnings
cf-bonveno-fonts.noarch: W: wrong-file-end-of-line-encoding
/usr/share/doc/cf-bonveno-fonts-1.1/COPYING
cf-bonveno-fonts.noarch: W: wrong-file-end-of-line-encoding
/usr/share/doc/cf-bonveno-fonts-1.1/README
To fix this warning you need something like
for txt in COPYING README ; do
sed 's/\r//' $txt > $txt.new
touch -r $txt $txt.new
mv $txt.new $txt
done
(the touch is necessary so you don't end up with new doc timestamps after each
builds)
You have more complete examples of txt files fixing in the gfs font packages.
Just browse some specs there http://cvs.fedoraproject.org/viewvc/rpms/
Mostly, we want new packagers to understand why their spec files contain X or
Y, not just copy templates blindly, so please DO ask every time you feel you're
performing black magic.
--
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.
15 years, 8 months
[Bug 432184] The Visibone font test does not work with the icedtea java plugin
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=432184
--- Comment #9 from Mark Wielaard <mjw(a)redhat.com> 2008-10-27 17:21:52 EDT ---
(In reply to comment #7)
> Well they crash reliably there. Maybe that's an x86_64 vs i386 problem?
No, I also ran it on an x86_64 system. I suspect there is something different
with the setup of the accessibility tools on the systems.
It could be that you are still using the old plugin, but it doesn't seem so.
Note how it fails while initializing org.GNOME.Accessibility.JavaBridge which
tries to use corba to connect to your local orbit to work. Somehow this seems
to go wrong. I don't know why though.
--
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.
15 years, 8 months
[Bug 467982] anaconda doesn't render glyphs with the proper font
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=467982
Chris Lumens <clumens(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |besfahbo(a)redhat.com,
| |fedora-fonts-bugs-list@redh
| |at.com
Component|anaconda |fontconfig
AssignedTo|anaconda-maint-list@redhat. |besfahbo(a)redhat.com
|com |
--- Comment #4 from Chris Lumens <clumens(a)redhat.com> 2008-10-27 10:42:35 EDT ---
This happens when running anaconda on a regular system in test mode too.
--
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.
15 years, 8 months