In this commit the ebuild was modified to remove the libressl use flag https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=beea04c481c315ecfe368a9fb70c0eddf5ab6805 but the package revision was not incremented after that. This causes installation from binary package that was created before its removal to fail because of non-matching use flags. Reproducible: Always Steps to Reproduce: 1. binpkg host creates the package before commit beea04c4 with libressl use flag still present (whether it's enabled or not, doesn't matter) 2. binpkg consumer tries to install the package after beea04c4 which causes it to detect non-matching use flags and fall back to a source build (if so configured) 3. a simple 'emerge -1 net-misc/openntpd' on the binpkg host fixes the issue
I'd say this is INVALID. It doesn't seem justified to force rebuild on everyone to workaround what is essentially a limitation in your binary package builder.
(In reply to Michał Górny from comment #1) > I'd say this is INVALID. It doesn't seem justified to force rebuild on > everyone to workaround what is essentially a limitation in your binary > package builder. Then should this be a portage bug/improvement instead? If the binary package has a disabled use flag present but the ebuild doesn't have that use flag present at all, it should ignore the mismatch?
There's no rule saying whether flag disappearing means "disabled", "enabled unconditionally" or "something else". What really needs to happen is your binpkg builder detecting USE change and rebuilding the package.
(In reply to Michał Górny from comment #3) > There's no rule saying whether flag disappearing means "disabled", "enabled > unconditionally" or "something else". What really needs to happen is your > binpkg builder detecting USE change and rebuilding the package. I was updating my binpkg host with what I thought was correct, 'emerge -auDU @world' but now that I know that, I see I should be using -N instead of -U. So it was my error and this is indeed INVALID. Maybe a warning about not using -U should be added to the wiki though. I think on pages https://wiki.gentoo.org/wiki/Upgrading_Gentoo#Updating_packages add: "If you are building binary packages, you most likely should not use --changed-use. Also see the [Binary package guide#Maintaining_binary_packages]" and on https://wiki.gentoo.org/wiki/Binary_package_guide#Maintaining_binary_packages add subsection "Updating the binary package host" with the instruction to use the "--newuse" option (-auDN) when updating @world. What do you think? I can edit the wiki if you agree.
Yes, please update the Wiki. I think it makes sense.
