Repository 'x-portage' is missing ?

Message

cwc · Post by **cwc** » Sun Sep 08, 2013 2:22 pm

This is new after I did an update.
Do I need to create this file '/usr/local/portage/metadata/layout.conf' and add masters = gentoo

!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
Calculating dependencies |... done!

thanks

Moriah · Post by **Moriah** » Sun Sep 08, 2013 7:35 pm

Ditto here. I started seeing this during routine weekly updates today (Sunday 2013_09_08). All my 32 bit machines are saying this; the 64 bit ones are not. What is this all about?

platojones · Post by **platojones** » Sun Sep 08, 2013 9:47 pm

Well, all my machines, 64 bit included, are doing this. It's some feature in the latest portage, but I have no idea what it is for. It is very annoying and makes it more difficult to see errors though.

figueroa · Post by **figueroa** » Sun Sep 08, 2013 11:41 pm

I created the file adding one line with:

Code: Select all

masters = gentoo

and the error went away.

I hope that's good.

cwc · Post by **cwc** » Mon Sep 09, 2013 12:30 am

figueroa wrote:I created the file adding one line with:
Code: Select all
masters = gentoo
and the error went away.

I hope that's good.

thanks for the line.

that fixed it for me .

Moriah · Post by **Moriah** » Mon Sep 09, 2013 4:14 am

I do not want to just "fix it"; I want to know what it is all about -- what is the reason for this -- why is this suddenly necessary, and what happens if I do not "fix it".

jimmij · Post by **jimmij** » Mon Sep 09, 2013 7:58 am

Why cannot this be set automatically by overlays?

Pasketti · Post by **Pasketti** » Mon Sep 09, 2013 9:55 pm

I'd like to know why it's looking in /usr/local/portage/metadata instead of /usr/portage/metadata which is where layout.conf actually lives.

dol-sen · Post by **dol-sen** » Tue Sep 10, 2013 5:11 am

Every overlay has to now have a layout.conf. Portage use to ASSUME a default of gentoo if it was not specified. But now it is required for every repository.

Please notify the maintainers of all your overlays that do not yet include a layout.conf.

Also layman can not specify one for you if it is not there, that is a bug in the repository not meeting the package manager's requirements, not layman.

There have been a number of recent portage changes that is that have affected many of the apps that I code for, putting them all behind trying to keep up.

huuan · Post by **huuan** » Wed Sep 11, 2013 8:15 pm

dol-sen wrote:Every overlay has to now have a layout.conf. Portage use to ASSUME a default of gentoo if it was not specified. But now it is required for every repository.

Please notify the maintainers of all your overlays that do not yet include a layout.conf.

Also layman can not specify one for you if it is not there, that is a bug in the repository not meeting the package manager's requirements, not layman.

There have been a number of recent portage changes that is that have affected many of the apps that I code for, putting them all behind trying to keep up.

Code: Select all

# equery l awstats
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
 * Searching for awstats ...

I hesitate to say this since you devs are the mainstay of gentoo... but, you are kidding, right?

So just to be certain:
since the last portage update, something has changed in the way that portage handles overlays and as a result it is felt that it is the responsibility of *end-users* to "notify the maintainers of all your overlays" that something has changed (in portage) and that they should now include ?'layout.conf' in their packages?

Shouldn't that be the responsibility of whoever updated portage?

huuan · Post by **huuan** » Wed Sep 11, 2013 8:26 pm

or apparently we need to update the kernel...
http://forums.gentoo.org/viewtopic-t-969652.html

TheCubeIsALie · Post by **TheCubeIsALie** » Wed Sep 11, 2013 11:41 pm

huuan wrote:
dol-sen wrote:Every overlay has to now have a layout.conf. Portage use to ASSUME a default of gentoo if it was not specified. But now it is required for every repository.

Please notify the maintainers of all your overlays that do not yet include a layout.conf.

Also layman can not specify one for you if it is not there, that is a bug in the repository not meeting the package manager's requirements, not layman.

There have been a number of recent portage changes that is that have affected many of the apps that I code for, putting them all behind trying to keep up.
Code: Select all
# equery l awstats
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
 * Searching for awstats ...
I hesitate to say this since you devs are the mainstay of gentoo... but, you are kidding, right? So just to be certain:
since the last portage update, something has changed in the way that portage handles overlays and as a result it is felt that it is the responsibility of *end-users* to "notify the maintainers of all your overlays" that something has changed (in portage) and that they should now include ?'layout.conf' in their packages?

Shouldn't that be the responsibility of whoever updated portage?

Aren't overlays unofficial? Wouldn't that make it the overlay maintainer's responsibility to keep up with Gentoo updates?

huuan · Post by **huuan** » Thu Sep 12, 2013 1:41 am

That makes sense.
I don't know enough about portage to understand why portage can't run a script to add whatever is needed. Perhaps it can but it should be as you say the responsibility of the overlay maintainer. I stand corrected.

Ant P. · Post by **Ant P.** » Thu Sep 12, 2013 9:30 pm

TheCubeIsALie wrote:Aren't overlays unofficial? Wouldn't that make it the overlay maintainer's responsibility to keep up with Gentoo updates?

It's a single line of effort on overlay maintainers' part, and has been detailed in the Gentoo Package Manager Specification for years. The only change here is Portage becoming less sloppy about adhering to its own standards. Other PMs already aren't as lenient.

Would you be fine with people writing websites that only worked right in one outdated browser?

mv · Post by mv » Thu Sep 12, 2013 9:59 pm

Ant P. wrote:has been detailed in the Gentoo Package Manager Specification for years.

layout.conf is not mentioned in pms and AFAIK is a portage-only thing. Moreover, the particular masters attribute is rather new.

Moriah · Post by **Moriah** » Fri Sep 13, 2013 4:06 am

Would you be fine with people writing websites that only worked right in one outdated browser?

I'm not happy with it, but it certainly happens all the time. Many government sites, especially state ones, require an outdated and insecure version of Internet Explorer.

Ant P. · Post by **Ant P.** » Fri Sep 13, 2013 2:34 pm

mv wrote:
Ant P. wrote:has been detailed in the Gentoo Package Manager Specification for years.
layout.conf is not mentioned in pms and AFAIK is a portage-only thing. Moreover, the particular masters attribute is rather new.

I take that back, I was getting it confused with the repo_name file.

Though the fact it's not specified doesn't help matters.

paraw · Post by **paraw** » Sat Sep 14, 2013 11:15 am

dol-sen wrote:Every overlay has to now have a layout.conf. Portage use to ASSUME a default of gentoo if it was not specified. But now it is required for every repository.
Please notify the maintainers of all your overlays that do not yet include a layout.conf.
Also layman can not specify one for you if it is not there, that is a bug in the repository not meeting the package manager's requirements, not layman.
There have been a number of recent portage changes that is that have affected many of the apps that I code for, putting them all behind trying to keep up.

That's all fine, but the error seems to be on a repository named "x-portage". Now, I definitely have not installed such overlay, so the source of the problem is not there. Then the question is, what is "x-portage" exactly?

soka · Post by **soka** » Sat Sep 14, 2013 4:25 pm

That's all fine, but the error seems to be on a repository named "x-portage". Now, I definitely have not installed such overlay, so the source of the problem is not there. Then the question is, what is "x-portage" exactly?

Check if you have defined PORTDIR_OVERLAY in make.conf, in that case you have to add layout.conf to your local overlay.

paraw · Post by **paraw** » Sat Sep 14, 2013 4:28 pm

I do have PORTDIR_OVERLAY defined in make.conf, but I also have

Code: Select all

source /var/lib/layman/make.conf

in there too. Incidentally, the only overlay I use has the masters correctly defined in layout.conf.

Ant P. · Post by **Ant P.** » Sat Sep 14, 2013 6:40 pm

paraw wrote:Then the question is, what is "x-portage" exactly?

It assumes that from /usr/local/portage/ if you don't have a repo_name file.

paraw · Post by **paraw** » Sat Sep 14, 2013 6:50 pm

OK, the only overlay I have is the steam overlay. If I

Code: Select all

cat /var/lib/layman/steam/profiles/repo_name

I get

Code: Select all

steam-overlay

This suggests that the repo_name file is there and it has the correct content...

Ant P. · Post by **Ant P.** » Sat Sep 14, 2013 9:28 pm

Well then... I have no idea what portage is doing in that case.

tld · Post by **tld** » Thu Sep 19, 2013 4:19 am

I ran into this and had to copy /usr/portage/metadata/layout.conf to a new metadata directory in my /usr/local/portage overlay.

So portage 2.2 goes stable...I have to search to figure out these errors...apparently the ebuilds in my overlay need to be addressed as they're causing all sorts of errors. Luckily there are none I need desperately for now, so I just moved them out of there until I can sort it out...and not so much as a news item about 2.2 going stable?...really??

Tom

jakeluck · Post by **jakeluck** » Tue Oct 22, 2013 4:51 pm

Code: Select all

layman --sync-all

this should up all your overlays and remove the error