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