Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 675410 - Make emerge/portage more verbose about missing repo's masters
Summary: Make emerge/portage more verbose about missing repo's masters
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-14 15:51 UTC by Nado
Modified: 2019-01-15 11:23 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nado 2019-01-14 15:51:54 UTC
After syncing a repository with a metadata/layout.conf configured with masters:
masters = foo gentoo

No warning is given that foo is missing.
It would help to make it more verbose so that the end user knows another repo is still needed.

I think it would be ideal to return an error at the sync phase so that you know before trying to emerge that something's wrong.

Reproducible: Always
Comment 1 Zac Medico gentoo-dev 2019-01-15 05:38:07 UTC
I see that each emerge invocation shows an early warning message like this:

Unavailable repository 'foo' referenced by masters entry in '/path/to/repo/metadata/layout.conf'

I suppose that we could mask ebuilds from any repositories that have missing masters.
Comment 2 Nado 2019-01-15 11:23:56 UTC
Ok, I'm guessing I ran some tests a bit fast to read carefully enough.

Places where no warning is given:
* after emerge --sync
* eselect profile obviously doesnt know about it