| 1 |
On 2019.05.31 11:49, n952162@×××.de wrote: |
| 2 |
> > Gesendet: Freitag, 31. Mai 2019 um 00:02 Uhr |
| 3 |
> > Von: "Dale" <rdalek1967@×××××.com> |
| 4 |
> > An: gentoo-user@l.g.o |
| 5 |
> > Betreff: Re: Aw: Re: [gentoo-user] upgrading (profiles, too) |
| 6 |
> > |
| 7 |
> > Mick wrote: |
| 8 |
> > > On Thursday, 30 May 2019 02:18:01 BST Dale wrote: |
| 9 |
> to do. |
| 10 |
> > |
| 11 |
> > If I recall correctly, I did a merge -e world when I switched to |
| 12 |
> 17.0. |
| 13 |
> > There are some things that I'd rather rebuild everything just to be |
| 14 |
> > sure. When it is winter time, why not, I need the heat anyway. |
| 15 |
> ;-) |
| 16 |
> > |
| 17 |
> > Dale |
| 18 |
> > |
| 19 |
> > :-) :-) |
| 20 |
> > |
| 21 |
> > |
| 22 |
> |
| 23 |
> |
| 24 |
> Compiling is not the problem. Knowing what USE and KEYWORD flags to |
| 25 |
> set is what scares me. At least those. I get all these dire |
| 26 |
> warnings from the system and I don't know what I did wrong. I'm |
| 27 |
> certainly not in the experimental class. I try to do the most |
| 28 |
> standard, stable things. |
| 29 |
You may not have done anything wrong. How dire an emerge warning is is |
| 30 |
up to interpretation. One way I sometimes deal with an update that |
| 31 |
throws lots of warnings and requests to change masks or keywords or use |
| 32 |
flags is to look carefully at the list of packages that would be |
| 33 |
updated, and pick one, and just try to update that one. I even |
| 34 |
sometimes find it easier to just "emerge -1 package" (instead of -u) |
| 35 |
because that seems less likely to try to include updates not needed for |
| 36 |
the package you selected. |
| 37 |
|
| 38 |
Also - I don't think you ever said which (or at least how many) |
| 39 |
packages you already have in packages.keyword. Often, having one |
| 40 |
package in that file (especially if it is not for a single version) |
| 41 |
will want testing versions of dependencies, so you either have to add |
| 42 |
those, or not use the testing version of the first package. |
| 43 |
|
| 44 |
Portage asking for changes to USE flags is likely far less of an issue |
| 45 |
- sometimes packages are changed so that a dependency now requires a |
| 46 |
particular use flag setting which is not the default (or may be |
| 47 |
affected by some USE flag you have set (or unset) in make.conf. |
Archives