| 1 |
On 5/14/21 3:54 AM, n952162 wrote: |
| 2 |
> Why does portage want to build this: |
| 3 |
> |
| 4 |
> [ebuild R ] x11-apps/xmodmap-1.0.10::gentoo 0 KiB |
| 5 |
> |
| 6 |
> given this, already installed: |
| 7 |
> |
| 8 |
> /var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild |
| 9 |
> |
| 10 |
> and these on my binary server (which is apparently not working properly |
| 11 |
> for reasons I'm trying to track down): |
| 12 |
> |
| 13 |
> binpkgs/x11-apps/xmodmap-1.0.10.tbz2 |
| 14 |
> distfiles/xmodmap-1.0.10.tar.bz2 |
| 15 |
> |
| 16 |
> When I remove these options, it doesn't want to anymore: |
| 17 |
> |
| 18 |
> # --changed-use \ |
| 19 |
> # --changed-deps \ |
| 20 |
> # --newuse \ |
| 21 |
> # --backtrack=100 \ |
| 22 |
> # --deep \ |
| 23 |
> |
| 24 |
> Which option was it, I wonder, which triggered the build, and would it |
| 25 |
> bring me anything? |
| 26 |
My guess is that one of the USE flags changed. Compare which USE flags |
| 27 |
is it currently installed with and which it wants for the reinstall. It |
| 28 |
might even be that a USE flag changed in the ebuild, even if it won't |
| 29 |
actually change what gets installed. (--changed-use vs --new-use) |
| 30 |
> |
| 31 |
> The options still used are: |
| 32 |
> |
| 33 |
> emerge \ |
| 34 |
> --getbinpkg y \ |
| 35 |
> -v \ |
| 36 |
> --tree \ |
| 37 |
> --update \ |
| 38 |
> --noreplace \ |
| 39 |
> --verbose-conflicts \ |
| 40 |
> --keep-going \ |
| 41 |
> --with-bdeps=y \ |
| 42 |
> @world |
| 43 |
> |
| 44 |
> |
Archives