Summary: | [ppc64le] Missing profiles/repo_name | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Overlays | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://qa-reports.gentoo.org/output/repos/ppc64le.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 552950 |
Description
Michał Górny
2016-06-30 21:58:34 UTC
While the report is actually pointing to an issue within pkgcore, the root issue is: you are missing profiles/repo_name. (In reply to Michał Górny from comment #1) > While the report is actually pointing to an issue within pkgcore, the root > issue is: you are missing profiles/repo_name. Your automatic bug-o-matic hit me up twice, you may want to see why. Anyhow thanks it fixed. *** This bug has been marked as a duplicate of bug 587672 *** (In reply to Anthony Basile from comment #2) > (In reply to Michał Górny from comment #1) > > While the report is actually pointing to an issue within pkgcore, the root > > issue is: you are missing profiles/repo_name. > > Your automatic bug-o-matic hit me up twice, you may want to see why. Anyhow > thanks it fixed. > > *** This bug has been marked as a duplicate of bug 587672 *** It's not automatic ;-). I just fixed it to report appropriate issues, so I confirmed opening the new bug. It can't check this one until the more important one is fixed, so when you fixed that, it would be able to confirm this one and close it ;-P. (In reply to Michał Górny from comment #3) > (In reply to Anthony Basile from comment #2) > > (In reply to Michał Górny from comment #1) > > > While the report is actually pointing to an issue within pkgcore, the root > > > issue is: you are missing profiles/repo_name. > > > > Your automatic bug-o-matic hit me up twice, you may want to see why. Anyhow > > thanks it fixed. > > > > *** This bug has been marked as a duplicate of bug 587672 *** > > It's not automatic ;-). I just fixed it to report appropriate issues, so I > confirmed opening the new bug. It can't check this one until the more > important one is fixed, so when you fixed that, it would be able to confirm > this one and close it ;-P. okay. it wasn't clear what was going on. |