Summary: | binutils downgrad bring all experimental System to death! | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | mega <dany> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | truedfx |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
mega
2007-01-25 10:27:49 UTC
binutils-2.17.50.0.8 was not keyworded ~amd64. It was hard-masked. binutils-2.17.50.0.8 was removed from the tree the 23rd, but 2.17.50.0.9 has been in since the beginning of the month already. You can't expect all versions of binutils to stay in the tree forever, you do need to keep up with newer versions. The reason why portage downgraded binutils is because you chose to unmask 2.17.50.0.8 but not any newer versions. Don't do that. And even with a non-functional binutils, there is no need to restart from scratch. As long as your system is functional, even if it cannot compile, you can install binary packages and use those to recover your system. |