Summary: | enhancement to news item for profile 17.1 - emerge -1v /lib32 /usr/lib32 is not sufficient, as it does not correctly order the rebuilds | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jack <ostroffjh> |
Component: | Profiles | Assignee: | Michał Górny <mgorny> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | base-system, leonard, luke, pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 506276 |
Description
Jack
2019-06-07 20:52:17 UTC
I suppose "Reproducible: Always" isn't quite right, since this task will only ever be done once on any system. Not much for toolchain@ to do here. This is a real problem for me. --deep didn't help me, so right now I'm hoping that using --exclude on problem packages and then doing a second pass over the lib32 directories will work. It feels like there's something missing from the instructions in the news item. (In reply to rnddim from comment #3) > .... --deep didn't help me, so right now I'm hoping that using --exclude on problem packages and then doing a second pass.... I'd add --keep-going, not use --exclude, and just repeat the whole thing, as long as it gets more packages done on each pass. In a different post, someone also suggested --complete-graph, but I did not need it, so don't know what difference it would make. Although not a build failure here, but the single advise in 17.1 news item $ emerge -1v --deep /lib32 /usr/lib32 /usr/lib/llvm/*/lib32 does leave some packages (fex. gnome-base/librsvg-2.40.20) providing some /lib32 dir, even if they were rebuilt during that command. Performing the same command again does rebuild the remaining packages here. Maybe repeat until 'equery b lib32' yields nothing? For the OP: Have you been able to try with '--emptytree'? Is this now sufficiently outdated to close? Not sure if it should be called Fixed, Notabug, or Worksforme? In specific reply to the last question in Comment #5, no, I did not try --emptytree, as I succeeded with a few reiterations with --keep-going. I can confirm this issue. Just happened for libX11 missing libxcb, missing xcb-proto. I am currently approximately in --keep-going cycle #3… Again asking if it's time to close this. |