Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 228595 - sys-apps/portage-2.2_rc1: confusing WARNING message regarding repo_name
Summary: sys-apps/portage-2.2_rc1: confusing WARNING message regarding repo_name
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
: 228859 (view as bug list)
Depends on:
Blocks: 210077
  Show dependency tree
 
Reported: 2008-06-20 17:11 UTC by Holger Hoffstätte
Modified: 2010-01-28 14:20 UTC (History)
6 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
use os.path.realpath() for comparing cannonical paths (repo_realpath.patch,507 bytes, patch)
2008-06-20 18:01 UTC, Zac Medico
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Hoffstätte 2008-06-20 17:11:18 UTC
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".
Comment 1 Zac Medico gentoo-dev 2008-06-20 18:01:58 UTC
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.
Comment 2 Holger Hoffstätte 2008-06-20 18:28:14 UTC
(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.
Comment 3 Fabian Groffen gentoo-dev 2008-06-20 18:41:33 UTC
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 ...
Comment 4 Martin Väth 2008-06-22 16:46:59 UTC
*** Bug 228859 has been marked as a duplicate of this bug. ***
Comment 5 Helmut Jarausch 2008-06-23 08:03:43 UTC
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.
Comment 6 Zac Medico gentoo-dev 2008-06-23 08:57:10 UTC
(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.
Comment 7 Helmut Jarausch 2008-06-23 09:15:11 UTC
(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.
Comment 8 Duncan 2008-06-23 20:43:36 UTC
[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?
Comment 9 Duncan 2008-06-27 11:01:48 UTC
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
Comment 10 ~S 2008-06-30 09:25:01 UTC
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
Comment 11 SpanKY gentoo-dev 2008-06-30 10:06:09 UTC
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.
Comment 12 Duncan 2008-06-30 10:36:47 UTC
(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.
Comment 13 ~S 2008-06-30 10:52:49 UTC
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
Comment 14 Duncan 2008-06-30 13:07:44 UTC
(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.
Comment 15 Zac Medico gentoo-dev 2008-07-23 07:56:57 UTC
This is fixed in 2.2_rc2.
Comment 16 Mike Limansky 2008-11-24 20:32:19 UTC
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?
Comment 17 Zac Medico gentoo-dev 2008-11-24 20:39:24 UTC
(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.
Comment 18 René Leonhardt 2010-01-28 14:20:16 UTC
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.