Best just use an example to explain this so please read "Steps to Reproduce" first. My issue is that it says "that the source repository could not be determined" even though the manifest has not changed nor has anything else. Is this a bug or just a limitation to emerge design? Can it be fixed ?, I wonder.... Reproducible: Always Steps to Reproduce: 1) I created my own ebuild for the package "sys-fs/fuse-2.7.4" 2) I have put it correctly into my PORTDIR_OVERLAY directory which is "/usr/local/portage" and created the manifest. 4) I use "emerge -va fuse" to install it and it correctly outputs following: ----------------------------------------------- These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-fs/fuse-2.7.4 0 kB [0=>1] Total: 1 package (1 reinstall), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /usr/local/portage ----------------------------------------------- 5) It installed with no problems. 6) I run "emerge -va fuse" again. See "Actual Results" and "Expect Results" Actual Results: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-fs/fuse-2.7.4 0 kB [?=>1] Total: 1 package (1 reinstall), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /usr/local/portage [?] indicates that the source repository could not be determined Expected Results: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-fs/fuse-2.7.4 0 kB [1] Total: 1 package (1 reinstall), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /usr/local/portage
Add profiles/repo_name to your overlay. This is not a bug.
This is no real critical error. It just means that portage cannot determine from which ebuild repository you emerged this package from. My guess is that you either don't have a file /usr/local/portage/profiles/repo_name which contains the name of your overlay or you installed the package a long time ago when portage didn't save the origin of a package in its package-database. Nevertheless, this message is no reason portage would refulse to install the package again. Just try it out :)
(In reply to comment #2) > This is no real critical error. It just means that portage cannot determine > from which ebuild repository you emerged this package from. My guess is that > you either don't have a file /usr/local/portage/profiles/repo_name which > contains the name of your overlay or you installed the package a long time ago > when portage didn't save the origin of a package in its package-database. > Nevertheless, this message is no reason portage would refulse to install the > package again. Just try it out :) > I wasn't saying it was a critical error, I did mark it as trivial. I didn't know about "/usr/local/portage/profiles/repo_name" so thanks to both Samuli Suominen and Lars Wendler (Polynomial-C) for pointing that out. Is it mentioned in Gentoo Documentation anywhere? Just wondering... I understand the reinstall works anyway that was why I maked it as "trivial" and no it wasn't a old ebuild, I used a brand new to test this issue. Cheers
