For the last couple of days when I’ve run zypper dup I’ve gotten the following response:
You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
2 Problems:
Problem: shared-python-startup-0.1-6.1.noarch conflicts with python3 < 3.8 provided by python3-3.2.1-5.1.3.x86_64
Problem: python3-dbm-3.2.1-5.1.3.x86_64 requires libgdbm.so.3()(64bit), but this requirement cannot be provided
Problem: shared-python-startup-0.1-6.1.noarch conflicts with python3 < 3.8 provided by python3-3.2.1-5.1.3.x86_64
Solution 1: Following actions will be done:
keep obsolete python3-3.8.3-4.2.x86_64
keep obsolete python3-base-3.8.3-4.2.x86_64
keep obsolete libpython3_8-1_0-3.8.3-4.2.x86_64
Solution 2: deinstallation of python3-3.8.3-4.2.x86_64
Solution 3: deinstallation of shared-python-startup-0.1-6.1.noarch
I’m not sure which option to choose. Has anyone else run into this?
This should include python3-dbm. You might have it installed from a non-standard repo. I recall seeing a movement about bringing distinct python3 versions, so I guess you’ll need to find another repository for that. The other package seems to be building just fine, so let’s see if that goes away. I’m not sure.
PS: remember to send along the listing of repos you have.
I would remove those, if that does not cause problems.
I suggest you use Yast Software Management. Choose the “Repositories” view.
Toward the bottom left, you should see “Secondary Filter:”. Set that to “unmaintained packages”.
It should give the same list. Then you can mark them to be deleted.
If a conflict pops up, you can tell it to keep that package, and try again.
First remove the packages where there is no conflict that pops up. Then go back and recheck the others. Maybe the only conflict is with other packages on the same list. It’s usually a good idea to keep that list as small as possible.
And here’s a list of my repos:
I would suggest that you remove #7. That is the install media, and the packages there are out of date by now.
I’m not otherwise seeing any obvious problems. Repo #6 might be a duplicate of repo #10 in that list, but I cannot tell because you did not show the url. It doesn’t hurt to have duplicates, but it might slow updating.
After zypper dup. A few packages might be considered orphaned at this point because the repos were refreshed but the packages not yet upgraded. This happens frequently with packages suffixed with numbers. For others, maybe the local repository was removed while keeping the packages, so they don’t get updates.
I suggest you use Yast Software Management. Choose the “Repositories” view.
Toward the bottom left, you should see “Secondary Filter:”. Set that to “unmaintained packages”.
It should give the same list. Then you can mark them to be deleted.
If a conflict pops up, you can tell it to keep that package, and try again.
First remove the packages where there is no conflict that pops up. Then go back and recheck the others. Maybe the only conflict is with other packages on the same list. It’s usually a good idea to keep that list as small as possible.
Thanks–I did that. I had to keep a few packages but I was able to delete many others.
Here’s the result of zypper lr -d after I deleted a couple of repositories: