Summary: | dev-lang/go depends on itself | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rick Jenkins <rick> |
Component: | Current packages | Assignee: | William Hubbs <williamh> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rick Jenkins
2021-05-03 18:04:07 UTC
Not sure what's happening here, as we have go-bootstrap.. >BDEPEND="|| ( > dev-lang/go > dev-lang/go-bootstrap )" Please provide the full emerge output along with the command used. You may need to run it *again* with --debug and attach the full output too. Have you done something weird like mask the go-bootstrap package? What does emerge -av1 dev-lang/go-bootstrap say? (It is possible we will need a higher bootstrap in future for bug 779859, but that's not strictly relevant heee). This occurred on my weekly update, which promptly died, so there is no more "emerge-output" available. Strangely, the emerge list for a world update did not include go-bootstrap, although dev-lang/go was flagged as new. A manual merge of go-bootstrap succeeds, and allows a manual emerge of dev-lang/go. (In reply to Rick Jenkins from comment #2) > This occurred on my weekly update, which promptly died, so there is no more > "emerge-output" available. Strangely, the emerge list for a world update did > not include go-bootstrap, although dev-lang/go was flagged as new. A manual > merge of go-bootstrap succeeds, and allows a manual emerge of dev-lang/go. Right, but I mean, you could've run the command manually again. Anyway, definitely weird that it succeeded manually, as it implies it wasn't masked or anything. my first reaction was to run the command manually, and it failed again. The key was your information about the need for go-bootstrap, which somehow was not being invoked automatically. (In reply to Rick Jenkins from comment #4) > my first reaction was to run the command manually, and it failed again. The > key was your information about the need for go-bootstrap, which somehow was > not being invoked automatically. Yeah. Definitely a shame we couldn't get to see why it wasn't recognising it needed -bootstrap. But all working now at least :) My apologies for collecting insufficient information. (In reply to Rick Jenkins from comment #6) > My apologies for collecting insufficient information. No worries at all, it's one of those things I wish we could debug but that's not me being annoyed at you or anything, I just wonder how it happened. These things happen and it's not always obvious what information is needed at the time. Chill! :) |