Created attachment 895430 [details] emerge --info --verbose Hello, recently I keep getting blocked packages, when upgrading from 5.15.13 to 5.15.14 and I have problems to pinpoint the problems. I can only see this on most dev-qt packages: [blocks B ] <dev-qt/qtwidgets-5.15.14:5 ("<dev-qt/qtwidgets-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14) [blocks B ] <dev-qt/qtdeclarative-5.15.14:5 ("<dev-qt/qtdeclarative-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14) [blocks B ] <games-simulation/simutrans-paksets-124.0 ("<games-simulation/simutrans-paksets-124.0" is soft blocking games-simulation/simutrans-124.0) [blocks B ] <dev-qt/qtgui-5.15.14:5 ("<dev-qt/qtgui-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14) [blocks B ] <dev-qt/qtnetwork-5.15.14:5 ("<dev-qt/qtnetwork-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14) [blocks B ] <dev-qt/qtwayland-5.15.14:5 ("<dev-qt/qtwayland-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14) [blocks B ] <dev-qt/qtdbus-5.15.14:5 ("<dev-qt/qtdbus-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14) [blocks B ] <dev-qt/qttest-5.15.14:5 ("<dev-qt/qttest-5.15.14:5" is soft blocking dev-qt/qtcore-5.15.14) I had tried --verbose-conflicts, --backtrack=100, but still not able to find the problems. Can please someone point me how to track down this problem?
Please share full emerge -p -uvDU output.
Created attachment 895432 [details] emerge -pvuUN --verbose-conflicts --backtrack=100 @world I had attached the emerge info, then I launched the command, but it took a while to complete. I had changed the use flags of some packages and also I used eix-sync, for a week or so I was hoping it would resolve the problem.
(In reply to Petr Šourek from comment #2) > Created attachment 895432 [details] > emerge -pvuUN --verbose-conflicts --backtrack=100 @world > > I had attached the emerge info, then I launched the command, but it took a > while to complete. I had changed the use flags of some packages and also I > used eix-sync, for a week or so I was hoping it would resolve the problem. Packages with binding operators (like Qt, boost, icu) often generate noise if something else is preventing portage from triggering the rebuilds they need -- so first check if it's saying something else at the bottom rather than focus on the wall of dev-qt/* messages. And in this case it's: [blocks B ] <games-simulation/simutrans-paksets-124.0 ("<games-simulation/simutrans-paksets-124.0" is soft blocking games-simulation/simutrans-124.0) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (games-simulation/simutrans-paksets-123.0.1:0/0::gentoo, ebuild scheduled for merge) pulled in by games-simulation/simutrans-paksets required by @selected (games-simulation/simutrans-124.0:0/0::gentoo, ebuild scheduled for merge) pulled in by games-simulation/simutrans required by @selected --- You have both packages in @selected (aka world file), but the newer simutrans no longer uses simutrans-paksets and in fact blocks it ad . Portage can't automatically resolve this for you unless it's removed from the world file. Try could be more issues but start with sorting that out. On that note, don't really know that package but simutrans-124 will also say: elog "Since 124.0 simutrans allows you to download PakSets to your home directory," elog "therefore games-simulation/simutrans-paksets has been deprecated."
(In reply to Ionen Wolkens from comment #3) > And in this case it's: > > [blocks B ] <games-simulation/simutrans-paksets-124.0 > ("<games-simulation/simutrans-paksets-124.0" is soft blocking > games-simulation/simutrans-124.0) > > * Error: The above package list contains packages which cannot be > * installed at the same time on the same system. > > (games-simulation/simutrans-paksets-123.0.1:0/0::gentoo, ebuild scheduled > for merge) pulled in by > games-simulation/simutrans-paksets required by @selected > > (games-simulation/simutrans-124.0:0/0::gentoo, ebuild scheduled for merge) > pulled in by > games-simulation/simutrans required by @selected Sorry for that, I had overlooked it, but it was added yesterday or day before yesterday using eix-sync. I had settled this error and trying to settle most of the others and then I will add output of same command or will close this ticket as irrelevant. Its an old MacBook air so it will compile for a day or two. But I will definitely will let you know if it was my mistake (still probable). Until then, thank you for your support. I appreciate it! Thanks, Regards, Petr Sourek
