Our automated repository checks [1] have detected that the 'gmt' repository lacks masters= specification. This causes some Package Managers to be unable to use the repository, and will become fatal in Portage at some point. Master repositories provide various resources to the sub-repositories in the way of inheritance. For example, a repository inherits eclasses, licenses, mirrors provided by the master. Additionally, it requires the master repository to be enabled, therefore allowing the packages provided by it to satisfy dependencies. In particular, if your repository uses any eclasses, licenses, mirrors, global USE flags or any other resources provided by the Gentoo repository, or depends on any packages provided by it, it needs to specify in metadata/layout.conf: masters = gentoo However, if your repository is fully stand-alone and any package provided by it can be installed without any other repository being enabled, you should specify empty masters= to indicate this: masters = Please fix the issue ASAP. It prevents our tools from working on the repository, and mirroring it. We reserve the right to remove it if we do not receive any reply within 2 weeks. [1]:https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI
(In reply to Michał Górny from comment #0) > Our automated repository checks [1] have detected that the 'gmt' > repository lacks masters= specification... [snip] > In particular, [snip], it needs to > specify in metadata/layout.conf: > > masters = gentoo It does. But, this is abandon-repo for ages; any end-user-facing surfaces are likely doing slight harm by cluttering up people's search-results and so forth, without giving any benefit. So I'd prefer if we could flag it as non-published, for now (assuming it shows up in the big layman list-of-repos), anyhow, in the interest of maximizing SNR for humans. When/if I clean it out and put any useful stuff there, I can just bug infra to re-add it, again. Alternatively, I'd be happy to just disappear all the content except the required boilerplate, which would save infra the hassle, but continue to negatively impact the OOTB layman overlay-list SNR -- really not a huge tragedy.
(In reply to Gregory Turner from comment #1) > (In reply to Michał Górny from comment #0) > > Our automated repository checks [1] have detected that the 'gmt' > > repository lacks masters= specification... > [snip] > > In particular, [snip], it needs to > > specify in metadata/layout.conf: > > > > masters = gentoo > > It does. Nope, there's not even a 'metadata' directory there :). Maybe you forgot to push? :) https://cgit.gentoo.org/user/gmt.git/tree/ > But, this is abandon-repo for ages; any end-user-facing surfaces are likely > doing slight harm by cluttering up people's search-results and so forth, > without giving any benefit. > > So I'd prefer if we could flag it as non-published, for now (assuming it > shows up in the big layman list-of-repos), anyhow, in the interest of > maximizing SNR for humans. Well, I see that we share a similar view :). I've removed the repo from the public (layman) list via commit a8dfba0ffc658cb2ea. The git repository itself is still live, and if you want it republished, just ping someone to do 'git revert a8dfba0ffc658cb2ea' in api-gentoo-org :). Thanks.
