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