When merging with "fontforge" flag, liberation-fonts fail. The upstream have changed naming scheme for installation dir from "liberation-fonts-ttf-ver.date" to "liberation-fonts-ttf-ver", so FONT_S should really be "${S}/${PN}-ttf-${PV}" Reproducible: Always
I second that, without fontforge flag using precompiled fonts it merges correctly.
On my system liberation-fonts-1.07.0 with USE="fontforge" does not fail, but the resulting fonts look absolutely horrible... I can confirm, there's something wrong with the ebuild.
Well, actually on my system _emerge_ does not fail also. It just does not install fonts. What looks like "horrible" is the result of missing font substitution by fontconfig. So, as it looks like maintainers have no intention in fixing the issue, there is fixed ebuild.
Created attachment 283805 [details] ebuild
Thank you Nikolay. Fixed in the tree.
I think the fix broke USE="-fontforge", the ttf files are no longer installed with 1.07.0-r1: # emerge -av1 media-fonts/liberation-fonts These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] media-fonts/liberation-fonts-1.07.0-r1 USE="X -fontforge" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Emerging (1 of 1) media-fonts/liberation-fonts-1.07.0-r1 * liberation-fonts-ttf-1.07.0.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking liberation-fonts-ttf-1.07.0.tar.gz to /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/work >>> Source unpacked in /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/work >>> Preparing source in /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/work ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/work ... >>> Source compiled. >>> Test phase [not enabled]: media-fonts/liberation-fonts-1.07.0-r1 >>> Install liberation-fonts-1.07.0-r1 into /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/image/ category media-fonts /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/temp/environment: line 1323: pushd: /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/work/liberation-fonts-1.07.0/liberation-fonts-ttf-1.07.0: No such file or directory install: cannot stat `*.ttf': No such file or directory !!! doins: *.ttf does not exist doins failed * Creating fonts.scale & fonts.dir ... [ ok ] /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/temp/environment: line 1332: popd: directory stack empty >>> Completed installing liberation-fonts-1.07.0-r1 into /var/tmp/portage/media-fonts/liberation-fonts-1.07.0-r1/image/ * QA Notice: file does not exist: * * doins: *.ttf does not exist # qlist liberation-fonts /usr/share/fonts/liberation-fonts/fonts.dir /usr/share/fonts/liberation-fonts/encodings.dir /usr/share/fonts/liberation-fonts/fonts.scale /etc/fonts/conf.avail/60-liberation.conf
bug #382431
(In reply to comment #7) > bug #382431 This actually breaks installation on my system with exactly described symptoms.
Ah, my bad. But the patch from #382431 should actually be like this: --- liberation-fonts-1.07.0-r1.ebuild-orig 2011-09-10 11:13:16.608293885 +0400 +++ liberation-fonts-1.07.0-r1.ebuild 2011-09-10 11:17:48.893775381 +0400 @@ -26,5 +26,6 @@ RDEPEND="" FONT_S="${S}/${PN}-ttf-${PV}" if ! use fontforge; then + FONT_S="${WORKDIR}/${PN}-ttf-${PV}" S=${FONT_S} fi
Ok, I did this differently. Everything should be fixed in liberation-fonts-1.07.0-r2.