Dropped keyword for the following arches due to now fontforge build system for dejavu-2.25-r1: alpha amd64 arm ia64 ppc ppc64 s390 sh sparc x86-fbsd It's hardmasked till we get all of you back on the wagon. The following new dependencies need to be keyworded: app-i18n/unicode-data -- data-only. If it emerge -> keyword dev-perl/Font-TTF -- src_test exists, if it passes -> keyword media-gfx/fontforge -- if it builds dejavu-2.25-r1 -> keyword
*** Bug 223973 has been marked as a duplicate of this bug. ***
added ~ppc64
(In reply to comment #0) > media-gfx/fontforge -- if it builds dejavu-2.25-r1 -> keyword got a build failure with dejavu-2.25-r1 on fbsd: [5] => build/unicover.txt install -d build/ scripts/unicover.pl /usr/share/unicode-data/UnicodeData.txt /usr/share/unicode-data/Blocks.txt \ tmp/DejaVuSans.sfd "Sans" \ tmp/DejaVuSerif.sfd "Serif" \ tmp/DejaVuSansMono.sfd "Sans Mono" > build/unicover.txt [6] => build/langcover.txt install -d build/ scripts/langcover.pl /usr/share/fc-lang \ tmp/DejaVuSans.sfd "Sans" \ tmp/DejaVuSerif.sfd "Serif" \ tmp/DejaVuSansMono.sfd "Sans Mono" > build/langcover.txt Unable to open /usr/share/fc-lang : No such file or directory gmake: *** [build/langcover.txt] Error 2 * * ERROR: media-fonts/dejavu-2.25-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2133: Called die * The specific snippet of code: * emake -j1 BLOCKS=/usr/share/unicode-data/Blocks.txt UNICODEDATA=/usr/share/unicode-data/UnicodeData.txt FC-LANG=/usr/share/fc-lang full sans || die "emake failed"; * The die message: * emake failed
Aballier Fixed InCVS. Someone (hrm) forgot to bump from latest unstable to 2.6.0 when bumping fontconfig.
x86-fbsd done, thanks
~alpha/~ia64/~sparc done
Peter, as I asked you in irc, please, revert in this package possibility to work with snapshots, like media-fonts/dejavu-2.25 does. Also I don't think that enabling build of fontforge by default makes sense for most of users, so, please, don't make it default. Thank you.
~amd64 keyword added
~ppc'd
A serious question: there is somebody using arm, s390 or sh?