1 |
On Sun, 16 May 2021 05:01:18 -0500 |
2 |
Dale <rdalek1967@×××××.com> wrote: |
3 |
|
4 |
> n952162 wrote: |
5 |
> > On 5/15/21 7:24 AM, Dan Egli wrote: |
6 |
> >> The R status means REBUILD. Usually, if it's an @world it's pulling |
7 |
> >> that in because something about that package changed and so it needs |
8 |
> >> to rebuild it. The --noreplace option would block that if portage |
9 |
> >> didn't think it was needed. Based on your options, I'd say that it's |
10 |
> >> probably a USE flag was changed. I don't use binpkgs myself, |
11 |
> >> preferring to compile except in certain circumstances (can we say |
12 |
> >> RUST!?) that I need to use a -bin variant. You can try without it, but |
13 |
> >> I recommend leaving your change-use and newuse flags in place and |
14 |
> >> letting the system rebuild xmodmap. |
15 |
> >> |
16 |
> >> |
17 |
> > Yes, thank you, but neither the server nor the client have any USE flags |
18 |
> > for that package defined. And the package has to be pretty stable by |
19 |
> > now ;-) |
20 |
> > |
21 |
> > |
22 |
> > |
23 |
> > |
24 |
> |
25 |
> All packages have USE flags defined somewhere even if you haven't |
26 |
> defined any yourself. Some are defined in profiles, some are defined |
27 |
> elsewhere. When I do updates, I see changes to USE flags all the time |
28 |
> that were changed by the profile, the maintainer in the ebuild or |
29 |
> somewhere else. After all, if a package doesn't have the USE flags |
30 |
> defined somewhere, emerge won't know what USE flags to include or |
31 |
> exclude support for. |
32 |
> |
33 |
> Dale |
34 |
> |
35 |
> :-) :-) |
36 |
> |
37 |
|
38 |
I t hink you are confusing enabled USE flags, with package USE flags. A |
39 |
package can have 0 USE flags (e.g. x11-apps/xmodmap, and many more). |
40 |
Enabled USE flags on the other hand are defined by user config files and |
41 |
profiles and by the package itself (i.e. they could be enabled by |
42 |
default). |
43 |
So there can very well be packages that have 0 USE flags, and xmodmap |
44 |
is one of them. |
45 |
The "problem" here is most probably a changed dependency. The |
46 |
dependencies (as defined in the ebuild) under which the package was |
47 |
built on the binhost have changed in the meantime in the ebuild file |
48 |
(without a revbump/version bump), and if the binhost has not enabled |
49 |
the flag "--changed-deps", it did not update the package to the new |
50 |
dependencies. |
51 |
If you really want to debug this, you could do a diff of the files |
52 |
/var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild |
53 |
/usr/portage/x11-apps/xmodmap/xmodmap-1.0.10.ebuild |
54 |
(or whatever your portage root directory is, I'm still using |
55 |
/usr/portage). That diff should be on the binhost! |
56 |
|
57 |
Cheers |
58 |
Andreas |