Font Awesome version 5
by Jerry James
In the review of python-pydata-sphinx-theme
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1981997), the
fact that our FontAwesome font packages are on version 4.x came up.
That new package needs version 5.x. I tried to make it work with 4.x
... no luck.
I do not want to take over the existing fontawesome-fonts package, nor
do I want to be involved in porting anything from version 4.x to
version 5.x. I am willing, however, to maintain a
parallel-installable version 5.x of the fonts, so that applications
can migrate on their own schedules (with an eye to eventually
deprecating and/or removing the existing package). I have filed a
review request:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1989300
It uses the name fontawesome-free-fonts for two reasons:
- To be different from the existing package name for parallel
installability; and
- To distinguish the Fedora package from the Pro version of the fonts.
I have two misgivings about this package and would appreciate some
input from the community on these points.
1. Does the name rationale make sense?
2. Do we actually need the web subpackage? The font guidelines say
NOT to package svg, woff, etc. versions of a font because modern
browsers can read the otf versions. On the other hand, the web
subpackage also contains JavaScript versions of the fonts (which
cannot be built from source using only Fedora packages, alas!). On
the gripping hand, the existing package has a web subpackage, and it
seems to be used (by 8 packages).
Thanks!
--
Jerry James
http://www.jamezone.org/
2 years, 8 months
how to update ssh public key
by Xiao Ni
Hi all
I've changed a new machine. So it needs to do a config before working
on it. A new ssh rsa key is generated. I want to update it to FAS. It
says "FAS2 is deprecated, and currently in read-only mode. Use Fedora
Accounts to create or manage your Fedora contributor account" on the
webpage. So I used the https://accounts.fedoraproject.org/ to update
my public key. But https://admin.fedoraproject.org/ doesn't update the
public key.
[xiao@fedora fedora-scm]$ fedpkg clone mdadm
Cloning into 'mdadm'...
xiao(a)pkgs.fedoraproject.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.
Could someone tell me how can I fix this?
Regards
Xiao
2 years, 8 months
HEADS UP: OpenEXR 3.X coming soon!
by Richard Shaw
So I've spent about 40 hours pushing through build problems in the COPR[1]
I've set up beating what packages I could into submission and moving the
ones I couldn't (or shouldn't) port to the openexr2 compat package.
Some of the ones I didn't even try porting were packages that looked to be
legacy like the kde3/kde4 ones or packages on their 40th release with no
activity upstream. I don't want to update any package when it's unlikely or
impossible (dead upstream) that OpenEXR 3 will ever be supported officially.
Some packages only needed some build system updates because of the
restructuring of the libraries. Others needed just a little bit of porting
in the code.
With all that said, I'm down to one package/problem... Blender
The problem is not with Blender itself, but rather that it depends on
OpenVDB and I've already confirmed with upstream that OpenEXR 3 will not be
supported until the next major release. Ironically they are both under the
stewardship of the Academy Software Foundation (AWSF) so great coordination
there... :/
That being said, OpenSceneGraph wasn't ready either but it was relatively
easy to port after I figured out that the EXR plugin it builds doesn't
create a fatal error during the build when it fails (frustrating!)
Ok, and as usual, writing all of this has helped me work through porting
OpenVDB... I'll see about sending the patch upstream.
I'll probably create the side-tag tomorrow and start working on the builds.
Thanks,
Richard
2 years, 8 months
