Andrei Borzenkov wrote:
Did you lock some packages to prevent their updates?
Yes, I see now that I did, due to my misunderstandings about zypper conflict resolution. Thanks for pointing it out, and apologies for my newbie errors. Ben Greiner wrote:
You have a lock that you did not mention before. It prevents the update of Qt5. Probably from a Solution selection "keep" for python3-pyside2 before.
As per the comment above, yes, I understand that now. Again, I apologize.
There is your answer. As of now you can only keep the distribution package for Cura if you stay on the old snapshot. The Cura package system broke apart with the switch to python311: Cura requires the libraries libArcus and libSavitar. They need to be updated first, because the old versions in the distribution still require obsolete python3-sip < 5 which is not compatible with python311. Cura upstream did switch to more modern tools months ago, but the openSUSE Tumbleweed package did not keep up. I suggest switching to Cura flatpak, appimage or the like. ... With a lot of manual intervention, you could reinstall the old packages after the dup. I get this:
Thanks very much for the detailed explanation and tutorial. Disappointing that nobody is maintaining openSUSE Cura, but that's how it goes with open source software. I browsed the Cura codebase a year or two ago when it stopped working with direct USB connections to 3D printers and Ultimaker said they wouldn't address that as a bug because none of theirs use USB. Fair enough, and at least they do contribute their industry-leading software as open source.
If you want to go down that route, good luck.
Yes, I'd need it. ;) But in a massive example of irony, I went back to try all of these suggestions today, and with 20230620 vs the 20230619 I was using yesterday, Cura *did* update successfully. (Yes, I understand that Tumbleweed is a moving target.) The only problem I had was that FreeCAD broke in almost the same way Cura was doing yesterday. But with my newfound knowledge (thanks again) I accepted deinstallation of it and the "dup" with 4086 packages completed successfully. (It also removed 8 other packages, all of which I need as well as FreeCAD, but hopefully the Tumbleweed churn will eventually bring them back.) Once again, thanks for all the help. I think my problems were a lack of understanding combined with my "dup"s straddling the very large Python 3.10 -> 3.11 change. The final irony is that I had delayed "dup"-ing while waiting for the nouveau driver patch, and despite the fact that it was committed both upstream and in https://github.com/openSUSE/kernel, it isn't in kernel-source-6.3.7-1.2.noarch nor (I assume because I'm still getting the lockup/kernel-fault) the running Tumbleweed vmlinuz-6.3.7-1-default kernel. So now I'm off to fight that battle. :( Thanks again for everyone's help.