| View previous topic :: View next topic |
| Author |
Message |
roomba23
n00b
Joined: 14 Apr 2025
Posts: 2
|
 Posted: Mon Apr 14, 2025 4:51 am Post subject: emerge @golang-rebuild => There are no sets to satisfy |
 |
|
Where did @golang-rebuild go? Is it for me only or everyone is affected?
| Code: |
$ emerge @golang-rebuild
emerge: There are no sets to satisfy 'golang-rebuild'. The following sets exist:
changed-deps
changed-subslot
deprecated-live-rebuild
downgrade
installed
live-rebuild
module-rebuild
preserved-rebuild
profile
rebuilt-binaries
rust-rebuild
security
selected
selected-packages
selected-sets
system
unavailable
unavailable-binaries
world
x11-module-rebuild
|
Last edited by roomba23 on Mon Apr 14, 2025 3:40 pm; edited 1 time in total |
|
| Back to top |
|
 |
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2921
|
| Posted: Mon Apr 14, 2025 6:44 am Post subject: |
|
|
Everyone, it was removed. It used to be provided by portage itself, but it was moved to a go-sets.conf in dev-lang/go instead since portage-3.0.64... and then >=dev-lang/go-1.24.x or so stopped installing it.
I "think" this was discussed somewhere, but I forget where or the motivation -- imagine it's because the go eclass started using binding operators to trigger automatic rebuilds when updating dev-lang/go, it mostly makes golang-rebuild obsolete given the rebuilds will have happened either way, albeit using binding operators in BDEPEND can be a bit flaky and also be annoying for users that did not care to rebuild everything every go bump. |
|
| Back to top |
|
|
roomba23
n00b
Joined: 14 Apr 2025
Posts: 2
|
| Posted: Mon Apr 14, 2025 3:39 pm Post subject: |
|
|
| Ionen wrote: | | Everyone, it was removed. |
Nice. Thank you! |
|
| Back to top |
|
|
|
Portage & Programming
