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