| 1 |
Hello, |
| 2 |
|
| 3 |
On Mon, 18 Dec 2017, Mick wrote: |
| 4 |
>On Monday, 18 December 2017 16:14:42 GMT Dale wrote: |
| 5 |
>> Grant Edwards wrote: |
| 6 |
>> > I tried following the profile 17 upgrade instructions but now I'm |
| 7 |
>> > stuck. After running for a day or so, the 'emerge -e @world' command |
| 8 |
>> > stopped when grub-0.97 failed to build. |
| 9 |
>> > |
| 10 |
>> > How do I skip grub and continue? |
| 11 |
>> > |
| 12 |
>> > Or do I have to tell emerge to start over from the beginning (skipping |
| 13 |
>> > grub)? Assuming there are other packages that are going to fail also, |
| 14 |
>> > that could take weeks... |
| 15 |
>> |
| 16 |
>> emerge --resume --skipfirst |
| 17 |
>> |
| 18 |
>> That should work. If forced, using --exclude grub might could be |
| 19 |
>> added. I've never tried that with the --resume command tho. |
| 20 |
>> |
| 21 |
>> Dale |
| 22 |
>> |
| 23 |
>Let's not forget the '--keep-going y' option too. At the end it will print a |
| 24 |
>list of all the packages that failed to emerge. |
| 25 |
|
| 26 |
Well, there's a catch though. I did: |
| 27 |
|
| 28 |
$ emerge -e --keep-going @world |
| 29 |
[some failed pkg(s)] |
| 30 |
[Ctrl-C due to going to sleep etc.] |
| 31 |
$ emerge -e --keep-going --resume @world |
| 32 |
[Ctrl-C due to going to sleep etc.] |
| 33 |
[some failed pkg(s)] |
| 34 |
$ emerge -e --keep-going --resume @world |
| 35 |
[Ctrl-C due to going to sleep etc.] |
| 36 |
[2 more failed pkg(s)] |
| 37 |
[emerge prints just those two failed pkgs that failed since the last |
| 38 |
resume] |
| 39 |
|
| 40 |
And no "failed pgks" were printed at those Ctrl-C... |
| 41 |
|
| 42 |
Only trace was probably deep in the emerge logs and the leftovers in |
| 43 |
/var/tmp/portage (-> you should not these down before you shut down if |
| 44 |
that's a tmpfs ...) |
| 45 |
|
| 46 |
I think something about this should be done / documented. |
| 47 |
|
| 48 |
Luckily, it was no big deal, as I did a switch to gcc-7.2 / -pie at |
| 49 |
the same time, so I ran my "check-pie" script (pie-only check |
| 50 |
extracted from checksec) to find the packages that (might) need a |
| 51 |
recompile. I've just a few biggies leftover to compile and a couple I |
| 52 |
want to mess with. But those have updates pending anyway. So, I'm |
| 53 |
about done. |
| 54 |
|
| 55 |
BTW: in the process, I've collected binaries/packages that won't get |
| 56 |
compiled as pie... e.g. gcc itself, grub and most (all?) haskell |
| 57 |
stuff. ATM, it's a pretty badly ad-hoc script, but I could amend that. |
| 58 |
Or at least share the list of "known non-pie-able" binaries, I guess. |
| 59 |
Hm. One could also add an output that can be fed to emerge via xargs. |
| 60 |
|
| 61 |
-dnh |
| 62 |
|
| 63 |
-- |
| 64 |
"As a sysadmin, I suppose you're familiar with something called a |
| 65 |
'worst-case scenario'?" |
| 66 |
"Isn't that what we call, "having a good day for a change"?" |
| 67 |
(Rik Steenwinkel and Graham Reed) |
Archives