| 1 |
On Thursday, May 7, 2020 7:31 AM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
|
| 3 |
> Rich Freeman wrote: |
| 4 |
> |
| 5 |
> OP, odds are the emerge failure is what triggered the problem. If it had |
| 6 |
> completed without failure, it would likely have been a clean update. This is |
| 7 |
> why I set up a chroot and do my updates there and use the -k option to |
| 8 |
> install on my actual system. It takes very little time and so far, no |
| 9 |
> breakages on my real system. If any thing fails, it's more likely to be in |
| 10 |
> the chroot which won't hurt anything. If you able, may be a option worth |
| 11 |
> thinking about for yourself as well. |
| 12 |
> |
| 13 |
> Dale |
| 14 |
> |
| 15 |
> :-) :-) |
| 16 |
|
| 17 |
ya. i said it already. emerge's update failed |
| 18 |
with some package midways (some package needed |
| 19 |
some USE flag change), but then layman stopped |
| 20 |
working in this incomplete state. |
| 21 |
|
| 22 |
also the issue was simple. but i pointed out that |
| 23 |
the inconvenience of having a fancy dependency on |
| 24 |
a pms is still there. |
Archives