Created attachment 849970 [details] gns3-build.log gns3-server failed to emerge while the required dependency on busybox (static) has been set: [I] sys-apps/busybox Available versions: 1.34.1-r1^t{tbz2} **1.35.0-r1^t **9999*l^t {debug ipv6 livecd make-symlinks math mdev pam savedconfig selinux sep-usr static syslog systemd} Installed versions: 1.34.1-r1^t{tbz2}(22:33:28 05/02/23)(ipv6 savedconfig static syslog -debug -livecd -make-symlinks -math -mdev -pam -selinux -sep-usr -systemd) Homepage: https://www.busybox.net/ Description: Utilities for rescue and embedded systems The build log of gns3-server-2-2-37 fail has been attached.
The solution in this particular case was. The savedconfig USE flag has been enabled on the busybox build, while static USE flag has been set. Busybox was rebuild which triggered the issue seen in the attched buildlog. On IRC +ceamac and ano helped me to find the source of the issue. Thank you. Disabling the savedconfig USE flag on busybox, and rebuilding busybox solved the issue and gns3-server has been emerged sucessfully after it. I have been asked to open a bug for this.
Thank you! We should consider adding a warning for this case (i.e., busybox has the static flag set but savedconfig takes precedence)
Thanks for the report. I can add a note about this in gns3, but i'm not sure if I understand this correctly. AFAIK, savedconfig overrides the build config for busybox with a existing one. That means even after adding "static", savedconfig would disable static, because it was disabled before. Building busybox without the "savedconfig" useflag fixes this (and builds busybox with static enabled). - and i guess after the inital build, it's possible to add the "savedconfig" useflag again? I'm also wondering if that is something related with gns3 only. If i understand this correctly this can happen to any other package were the dependency changes to busybox[static] (and savedconfig was set before?)? In that case shouldn't be the note in the busybox ebuild?
