On 5/14/21 6:07 PM, Jack wrote:
On 5/14/21 3:54 AM, n952162 wrote:
Why does portage want to build this:
[ebuild R ] x11-apps/xmodmap-1.0.10::gentoo 0 KiB
given this, already installed:
/var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild
and these on my binary server (which is apparently not working properly
for reasons I'm trying to track down):
binpkgs/x11-apps/xmodmap-1.0.10.tbz2
distfiles/xmodmap-1.0.10.tar.bz2
When I remove these options, it doesn't want to anymore:
# --changed-use \
# --changed-deps \
# --newuse \
# --backtrack=100 \
# --deep \
Which option was it, I wonder, which triggered the build, and would it
bring me anything?
My guess is that one of the USE flags changed. Compare which USE
flags is it currently installed with and which it wants for the
reinstall. It might even be that a USE flag changed in the ebuild,
even if it won't actually change what gets installed. (--changed-use
vs --new-use)
There are no use flags defined for any of the packages I did a random
check for, either on the server or the client. I am worried that it is
as you say: that the ebuild has a change of USE flags, which, of course,
has nothing to do with me, the user.
I wish dearly that I could find a print out of the reasons why a package
is rejected, listing new and old USE flags, for example.
