If I want to emerge liberation-fonts-ttf portage said that theres no ebuild with this name, but the ebuild is in the tree. Now if I try to do: sudo ebuild /usr/portage/media-fonts/liberation-fonts-ttf/liberation-fonts-0.2.ebuild digest Appending /usr/portage to PORTDIR_OVERLAY... !!! /usr/portage does not seem to have a valid PORTDIR structure. NOTE: without sudo we also have the same problem and its the same problem in x86 and amd64 Reproducible: Always Steps to Reproduce: 1. try to emerge liberation-fonts-ttf 2. also digest the ebuild Actual Results: Don't install Expected Results: Can install liberation-fonts-ttf and unistall corefonts (maybe these two block each other?)
Please, learn how to work with portage; bugzilla is not a place for this.
kassandra cruzki # emerge liberation-fonts-ttf Calculating dependencies | emerge: there are no ebuilds to satisfy "liberation-fonts-ttf" circe cruzki # emerge liberation-fonts-ttf Calculating dependencies - emerge: there are no ebuilds to satisfy "liberation-fonts-ttf". I just sync the tree, and do an emerge portage && emerge -uDN world. So my system it's up to date and portage don't install that package. Even if I put that ebuild in an overlay. Even worse, if I force to install the ebuild in the tree I have emerge liberation-fonts-0.2.ebuild emerging by path implies --oneshot... adding --oneshot to options. *** emerging by path is broken and may not always work!!! Calculating dependencies | !!! /usr/portage/media-fonts/liberation-fonts-ttf/liberation-fonts-0.2.ebuild is not in a valid portage tree hierarchy or does not exist And I repeat I just sync the tree.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3
@cruzki - I'm terribly sorry, my CVS sync was out of date and I haven't notice the mess the maintainer created there in past couple of hours...:/
@je_fro: $ ls /usr/portage/media-fonts/liberation-fonts-ttf/ ChangeLog liberation-fonts-0.2.ebuild Manifest metadata.xml Eh?!? Would you please use repoman next time? This isn't even emergeable, how many times have you tested this? The ebuild filename is supposed to match ${CATEGORY}/${PN} for starters...
o problem. But I am curious about this issue. I try an ebuild (for other application) in the bugzilla before and I have the same problem. The follow time I want to know how to resolve this type of problem for myself. Is the name the only problem? or Is the ebuild itself?
I have temporarily reverted the changes and fixed the ebuild. However, Jeff please ping me on IRC.
I know I thought I changed the directory name after changing the ebuild. Sorry. And thanks for the public humiliation, I guess you've become an expert, jakub.
cruzki, the problem is that the ebuild and the directory which contains it have different names. liberation-fonts-ttf/ liberation-fonts
thanks for clarify my doubts (and all your work ;) )
(In reply to comment #8) > I know I thought I changed the directory name after changing the ebuild. You cannot rename anything and you cannot remove dirs in cvs.
Reopened because media-fonts/liberation-fonts-ttf was removed while media-fonts/liberation-fonts is not in the tree. See also: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=5#doc_chap6
Torsten, you must have caught it before I removed media-fonts/liberation-* and started over with media-fonts/liberation-fonts-ttf.
Fixed in CVS...sorry for the hassle everyone.
