~ # OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING="yes" emerge -q1 openssh >>> Running pre-merge checks for net-misc/openssh-9.3_p1-r1 * net-misc/openssh does not support USE='hpn' anymore. * The Base system team *STRONGLY* recommends you not rely on this functionality, * since these USE flags required third-party patches that often trigger bugs * and are of questionable provenance. * * If you must continue relying on this functionality, switch to * net-misc/openssh-contrib. You will have to remove net-misc/openssh from your * world file first: 'emerge --deselect net-misc/openssh' * * In order to prevent loss of SSH remote login access, we will abort the build. * Whether you proceed with disabling the USE flags or switch to the -contrib * variant, when re-emerging you will have to set * * OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING=yes * ERROR: net-misc/openssh-9.3_p1-r1::gentoo failed (pretend phase): * Building net-misc/openssh[-hpn] without OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING=yes * * Call stack: * ebuild.sh, line 136: Called pkg_pretend * environment, line 2418: Called die * The specific snippet of code: * die "Building net-misc/openssh[${disabled_eol_flags%,}] without OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING=yes"; * * If you need support, post the output of `emerge --info '=net-misc/openssh-9.3_p1-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-misc/openssh-9.3_p1-r1::gentoo'`. * The complete build log is located at '/var/log/emerge-log/net-misc:openssh-9.3_p1-r1:20230605-095230.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/net-misc/openssh-9.3_p1-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/openssh-9.3_p1-r1/temp/environment'. * Working directory: '/var/tmp/portage/net-misc/openssh-9.3_p1-r1/empty' * S: '/var/tmp/portage/net-misc/openssh-9.3_p1-r1/work/openssh-9.3_p1' >>> Failed to emerge net-misc/openssh-9.3_p1-r1, Log file: >>> '/var/log/emerge-log/net-misc:openssh-9.3_p1-r1:20230605-095230.log' * Messages for package net-misc/openssh-9.3_p1-r1: * Log file: /var/log/emerge-log/net-misc:openssh-9.3_p1-r1:20230605-095230.log * net-misc/openssh does not support USE='hpn' anymore. * The Base system team *STRONGLY* recommends you not rely on this functionality, * since these USE flags required third-party patches that often trigger bugs * and are of questionable provenance. * * If you must continue relying on this functionality, switch to * net-misc/openssh-contrib. You will have to remove net-misc/openssh from your * world file first: 'emerge --deselect net-misc/openssh' * * In order to prevent loss of SSH remote login access, we will abort the build. * Whether you proceed with disabling the USE flags or switch to the -contrib * variant, when re-emerging you will have to set * * OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING=yes * * The following package has failed to build, install, or execute postinst: * * (net-misc/openssh-9.3_p1-r1:0/0::gentoo, binary scheduled for merge), Log file: * '/var/log/emerge-log/net-misc:openssh-9.3_p1-r1:20230605-095230.log' * [binary U ] net-misc/openssh-9.3_p1-r1::gentoo [9.1_p1-r3::gentoo] USE="pam (pie) ssl -X -audit (-debug) -kerberos -ldns -libedit -livecd -security-key (-selinux) -static -test -verify-sig -xmss (-X509%) (-hpn%*) (-sctp%)" 0 KiB
Please include the environment file, the full build.log, and emerge --info.
Can reproduce from a quick try, albeit I did cheat to trigger the check given I don't have openssh[hpn] around by using: if [[ ${MERGE_TYPE} == binary && ${OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING} != yes ]]; then And then setting OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING=yes accomplished nothing when doing emerge -K1 openssh with it. Unless missing something obvious, I guess(?) binpkgs simply stick to what's in the environment file? Not something I ever looked at.
I guess we'll skip it for binaries then.
(In reply to Sam James from comment #3) > I guess we'll skip it for binaries then. Yeah doesn't hurt I guess, albeit this does feel like an edge case given (as far as I can tell) it'd mean having created the binpkg /without/ using this variable, and then have a target machine that differs and still has openssh[hpn] or so installed.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=af815ce4c7a7933c36b36b24c29b655bfec37105 commit af815ce4c7a7933c36b36b24c29b655bfec37105 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-08-02 12:38:57 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-08-02 12:38:57 +0000 net-misc/openssh: skip sanity-check for binpkgs Because of environment saving, we can't allow users to override for binpkgs, so just elide the check there. Closes: https://bugs.gentoo.org/907892 Signed-off-by: Sam James <sam@gentoo.org> net-misc/openssh/openssh-9.3_p2.ebuild | 3 +++ 1 file changed, 3 insertions(+)
