Re: [gentoo-user] /usr/local/portage/profiles/repo_name

2009-06-02 Thread Alan McKinnon
On Tuesday 02 June 2009 15:25:35 James wrote:
 Hello,


 Upon routine update of one gentoo system, I get this
 error message:

 WARNING: One or more repositories have missing repo_name entries:
 /usr/local/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.


 So looking in /etc/make.conf I see this entry:
 source /usr/portage/local/layman/make.conf

Check in this file if you have a reference to something in /usr/local/portage/

 Obviously there is a miss-match?


 I have no /usr/local/portage/profiles directory.
 I have not used the overlays (layman or Sunrise)
 for some time, so maybe I need to read up on
 how to set these up, as to keep current?


 Any suggestions are most welcome.


 James

-- 
alan dot mckinnon at gmail dot com



Re: [gentoo-user] /usr/local/portage/profiles/repo_name

2009-06-02 Thread Mark Knecht
On Tue, Jun 2, 2009 at 6:25 AM, James wirel...@tampabay.rr.com wrote:
 Hello,


 Upon routine update of one gentoo system, I get this
 error message:

 WARNING: One or more repositories have missing repo_name entries:
        /usr/local/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.


 So looking in /etc/make.conf I see this entry:
 source /usr/portage/local/layman/make.conf


 Obviously there is a miss-match?


 I have no /usr/local/portage/profiles directory.
 I have not used the overlays (layman or Sunrise)
 for some time, so maybe I need to read up on
 how to set these up, as to keep current?


 Any suggestions are most welcome.


 James

there was a change in layman - I never saw it documented but
apparently some devs on the pro-audio list knew about it - where
layman changed the path between /usr/local/portage and
/usr/portage/local. I think my solution was to use layman to remove
all overlays, then change my path in make.conf, then re-import the
overlays I was using. (vmware and pro-audio) IIRC corretly after
removing the overlay probably removed directories by hand, etc., and
did some cleanup. Anyway, after messing around with it things started
working again and I haven't had trouble since.

Note that I didn't have any private overlays and this happened
sometime back - maybe 2-3 months ago - so your results may vary or not
even be related.

You can probably find the thread in the proaudio users list archive if
you want to review what the dev told me.

Hope this helps,
Mark