#Wanting advice on preventing future breakages.

1 messages · Page 1 of 1 (latest)

mild rivet
#

Hi everyone, I've reluctantly moved away from Gentoo at the moment because I had a problem with an emerge. Basically it was 162 package update and about half way through I got an error for qtwayland.

dev-qt/qtwayland[qml] depends on ~dev-qt/qtdeclarative-6.9.1,
but it has not been upgraded/installed yet, implies that there,
is a bug in the package manager assuming normal usage.,
ERROR: dev-qt/qtwayland-6.9.1::gentoo failed (prepare phase):,
aborting to avoid installing a broken package,
,
Call stack:,
ebuild.sh, line 136: Called src_prepare,
environment, line 1503: Called qt6-build_src_prepare,
environment, line 1374: Called die,
The specific snippet of code:,
die "aborting to avoid installing a broken package";,

Because of this I couldn't access KDE at all and was left waiting until the next day for an update for fix it. But after that my system was sluggish and sddm took about 5 minutes to initialise. Just wanted to know what the precautions are to prevent it in the future? Portage said all blocks were satisfied and the emerge proceeded as usual before qtwayland. I do want to come back to Gentoo but I don't want to keep making this mistake.

vapid yacht
#

I'm not sure about the specific build error here (would need to see more of the build log ideally) but generally there are some tips;

--keep-going is very useful if one package out of 162 is being annoying. It does what it says - avoiding crapping out entirely if one package fails

Then there is --resume for picking up a crapped out merge again without having to -uDN world

Set up logging for emerge - https://wiki.gentoo.org/wiki/Portage_log - then you can see what actually went wrong instead of the vague "called die" traces

mild rivet
#

Thanks for the response, sorry for the vague error that is all I had to go off at the time. I will definitely make use of keep going and resume if that issues arises again and elog looks really interesting so I'll read some more and put it in my make.conf the next time I install Gentoo (hopefully soon). Thanks for the advice again by the way, you've helped me a lot in the past ❤️

mild rivet
#

I haven't really delved into updating in a separate chroot but I will look into it and see how I feel about it, thanks for the links 🙂

#

When I did that emerge I did emaint --auto sync beforehand and there wasn't anything regarding a portage update, I always feel bad asking for help kekw but I should be ok with asking as it'll help me learn right. I'll ask in libera too in the future.

main token
#

Just sounds like slot conflict, nothing major

#

Next time you get one ask for help and we'll explain what to do

#

Basically portage is stopping you from getting into a mess not the other way around

mild rivet
# main token Just sounds like slot conflict, nothing major

I did ask for help but it was in the support channel and it was a bad time to ask on my part as there was another conversation going on, I'll just make a post in the help forum from now on if I'm in a situation like this again. I just feel bad asking for help because for me in particular it takes a while for stuff to stick. But I'm glad it is nothing too bad from the error I sent.

main token
mild rivet
#

Fair enough my bad ❤️

main token
#

no worries, I was trying my best to word it in a way it wouldn't sound like how you read it

#

seems I failed 🙂