After upgrading to portage-2.2rc1 today, I now get: $emerge -uvp world WARNING: repository at /usr/local/portage is missing a repo_name entry OK, so I didn't have that yet. Fixing: $mkdir /usr/local/portage/profiles $echo local-repo > /usr/local/portage/profiles/repo_name But no luck: $emerge -uvp world WARNING: repository at /usr/local/portage is missing a repo_name entry This did not happen with the previous version 2.1.5.6. Reproducible: Always Steps to Reproduce: 1. emerge \=portage-2.2_rc1 2. create overlay 3. run emerge Expected Results: No warnings, or at least a better message with instructions how to fix the problem - not just that "something is wrong".
Created attachment 157805 [details, diff] use os.path.realpath() for comparing cannonical paths > But no luck: > $emerge -uvp world > WARNING: repository at /usr/local/portage is missing a repo_name entry Is /usr/local/portage a symlink? If so, this patch should help.
(In reply to comment #1) > Is /usr/local/portage a symlink? If so, this patch should help. Why yes, it is! How did you know? :) Applied the patch & the warning is gone. Thanks a lot.
one remark, the message is not pointing to "profiles", which almost tricked me into adding repo_name in the top-level of my tree instead ...
*** Bug 228859 has been marked as a duplicate of this bug. ***
Here, /usr/local/portage isn't a symlink, but /usr/local itself is a symlink. And unfortunately the posted patch doesn't fix the problem here.
(In reply to comment #5) > Here, /usr/local/portage isn't a symlink, but /usr/local itself > is a symlink. > And unfortunately the posted patch doesn't fix the problem here. > You didn't mention whether or not /usr/local/portage/profiles/repo_name exists. Does it? If not, that's why you're getting the message still.
(In reply to comment #6) > (In reply to comment #5) > > Here, /usr/local/portage isn't a symlink, but /usr/local itself > > is a symlink. > > And unfortunately the posted patch doesn't fix the problem here. > > > > You didn't mention whether or not /usr/local/portage/profiles/repo_name exists. > Does it? If not, that's why you're getting the message still. > Thanks, that was the reason.
[I've not applied the patch yet, just found the bug.] FWIW, I'm getting this on my main gentoo repo, as well as layman's sunrise repo, which is inside the gentoo repo directory tree. The gentoo repo is a symlink, so that's probably why it's triggering on both since layman/sunrise is inside the symlinked main tree. This may be related to bug #144630 , equery reversing main and overlay trees, which continues to bug me. It's displaying the main tree packages as all in sunrise, now. That seemed to be symlink related too. Thus maybe a similar fix?
I finally got around to testing the patch. It works here too. =8^) Now working on the other bugs I need to test stuff on. Duncan
I am getting the warning any time i use emerge command should I be worried? will portage fix itself or do i have to fix it manually? or should i just emerge -Cav layman and remove source line in make.conf (added by layman)? will removing layman fix this nagging warning? ~S
portage cant fix itself because portage isnt broken. the overlay that it is warning about is. it wont affect any of your emerge's however, so you can just ignore it.
(In reply to comment #10) > I am getting the warning any time i use emerge command Short answer to all the questions... It depends. =8^) > will portage fix itself or do i have to fix it manually? Depends. =8^) If you're getting the warning due to a symlink, apply the patch above or wait for the fix to be included, presumably with 2.2-rc2. If you're getting the warning due a missing repo_name file for the repo described by the path in the warning, it's not portage's problem, but that of the repo/overlay in question. File a bug with the person controlling the repo in question, if it's a layman or other remote repo, or create the file for yourself if it's your own repo/overlay. > should I be worried? The feature in question just allows portage to track where a package came from, nice info to have, but not vital. So it's nothing to be really worried about, but it'd be nice to have it fixed. > should i just emerge -Cav layman Depends. =8^) Are the layman repos/overlays the only ones giving you the warning? Are the packages you are using from the various repos more important to you than that message is irritating? If so or if you'd get the warning for other repos anyway, keep layman and the packages, file bugs upstream as appropriate, and don't worry about it for now. If it's irritating enough to make the packages in those repos more trouble than they are worth, unmerge them and layman, remove that source line, and be done with it.
thanks spanky and duncan for the replies i removed layman and other related stuff but the warning wont go then i remembered i had a local overlay for the faulty netkit-rsh so i made entry as suggested by Holger Hoffstätte $mkdir /usr/local/portage/profiles $echo local-repo > /usr/local/portage/profiles/repo_name and its gone now. thanks again for the help Just curious, why did it popped up suddenly(/after updating portage)? it didn't complained earlier ~S
(In reply to comment #13) > Just curious, why did it popped up suddenly(/after updating portage)? > it didn't complained earlier Because the bit about using the repo_name is new to portage 2.2. In 2.1 it was just the path to the repository/overlay that was used. So the warning came with the upgrade to the 2.2 rcs.
This is fixed in 2.2_rc2.
It seems like there is regression in portage-2.2_rc15. I had an overlay with rc14 and all worked fine, but after upgrade to rc15 the warning is appeared: WARNING: One or more repositories have missing repo_name entries: /usr/portage/profiles/repo_name NOTE: Each repo_name entry should be a plain text file containing a unique name for the repository on the first line. Could you please reopen this bug?
(In reply to comment #16) > It seems like there is regression in portage-2.2_rc15. I had an overlay with > rc14 and all worked fine, but after upgrade to rc15 the warning is appeared: Well, it's not exactly the same problem, so please file a separate bug.
I have the same warning with portage 2.2_rc61. Comment #13 $mkdir /usr/local/portage/profiles $echo local-repo > /usr/local/portage/profiles/repo_name solved it.