1 |
On Fri, 7 Jun 2019 13:24:07 +0300 |
2 |
Ilya Trukhanov <lahvuun@×××××.com> wrote: |
3 |
|
4 |
> On Fri, Jun 07, 2019 at 08:03:30AM +0100, Sergei Trofimovich wrote: |
5 |
> > On Thu, 06 Jun 2019 18:49:48 -0400 |
6 |
> > Jack <ostroffjh@×××××××××××××××××.net> wrote: |
7 |
> > |
8 |
> > > On 2019.06.06 18:38, Ilya Trukhanov wrote: |
9 |
> > > > Namely x11-libs/libX11 and dev-libs/glib: |
10 |
> > > > |
11 |
> > > > - libX11 failed during configure because it couldn't find xcb; |
12 |
> > > > - glib failed during configure because it couldn't find libmount. |
13 |
> > > > |
14 |
> > > > Looks like it is an order issue, because after rebuilding |
15 |
> > > > x11-libs/libxcb and sys-apps/util-linux, both libX11 and glib built |
16 |
> > > > just |
17 |
> > > > fine. |
18 |
> > > > |
19 |
> > > > Should I report bugs for these? The news item says: |
20 |
> > > > |
21 |
> > > > >If you have any problems with the new profiles or the migration |
22 |
> > > > >procedure, please report a bug and make it block the tracker. |
23 |
> > > > |
24 |
> > > > But I'm a little reluctant to do so for various reasons. |
25 |
> > > > |
26 |
> > > I'm in the same situation. I've had several rebuild failures that |
27 |
> > > succeeded after re-emerging one/some of what they depend on, although I |
28 |
> > > would have expected those to also be rebuilt. |
29 |
> > > |
30 |
> > > I wonder if the instructions should be "emerge -1 --deep /lib32 |
31 |
> > > /usr/lib32" ? I'll have to try it once I'm done with the current set |
32 |
> > > of emerges. |
33 |
> > > |
34 |
> > > Anyway - it probably does make sense to file the bug - the worst they |
35 |
> > > will do is close it as not a bug, and hopefully at least tell you what |
36 |
> > > you should have done to avoid the problem. |
37 |
> > > |
38 |
> > |
39 |
> > I think the emerge command as stated in the news item is incomplete |
40 |
> > as emerge does not pick correct rebuild order (it assumes all packages |
41 |
> > are installed and in order, thus picks arbitrary rebuild order). |
42 |
> > |
43 |
> > Try to add --complete-graph to it: |
44 |
> > emerge -1 --deep --complete-graph /lib32 /usr/lib32 |
45 |
> > |
46 |
> > -- |
47 |
> > |
48 |
> > Sergei |
49 |
> > |
50 |
> |
51 |
> Unfortunately this still doesn't guarantee the correct build order for |
52 |
> me. I wonder if running emerge with --keep-going a few times would work in |
53 |
> this situation? |
54 |
> |
55 |
> It might be a good idea to mention this issue somewhere on the wiki or in a |
56 |
> follow-up news item. I doubt we're the last to face this problem now |
57 |
> that 17.1 profiles are stable. |
58 |
|
59 |
Yeah, if these options help you it's totally worth reporting a bug to update news item. |
60 |
|
61 |
-- |
62 |
|
63 |
Sergei |