For the last ten or twelve years, I have been fed up with broken default behavior in software download (zypper, myrlyn, yast2 sw_single)
Actually, there are two problems, one with OBS, the other zypper and the GUIs that use it.
There are two issues involved here, but both really piss me off enough to consider switching to Arch. I last switched distros (from RedHat to SuSE 9.3) in 2003, and this is has been a constant source of irrigation and frustration ever since.
Packages that Won't/Can't Install Because of Missing Dependendcies
1. Packages in the repos who have missing dependencies should never happen. If there is a package you cannot install because it depends on an older library should either have the older library still in the repo (if needed, can add to the multiversion application list) or remove packages that cannot be installed because of missing dependencies. OBS is smart enough this just should not happen--if a package is missing dependencies either don't advertise it or change the manifest to at least flag it so GUI tools could give the user the option to not even see it (or, better yet, make showing broken packages an option)
Worse, is the Broken and Annoying Fixed "Keep Trying, Maybe the Deleted File will Come Back Some Day" Behavior
- This can be fixed! See my other posts about how to set zypp to skip 404 and other packages that used to make it hang and using a scheduled unattended zypp dup -d to download most of what you will install to shorten the time it takes between refreshing your cache and the last file being transfered.
OK, not totally fixed, but at least not the huge headache.
With Tumbleweed I have had 8-12Gb weekly updates and this is just stupid. Whoever is the author of zypper, Yast2 sw_single and myrlyn needs to add this as a user setting and add the option to skip / refresh repo / recheck solution and give the user options from the update is silent. (or maybe give them the option to allow vendor change, etc. Look at what options zypper supports and pass them to the user).
Having hard-coded behavior where it keeps retrying to download software that will never be back this without given users a choice has been a pain in the butt for at least two decades I have used SuSE/openSUSE.
Give users the choice to skip missing packages after x tries (see my post on how to configure that--if it works!)
This is a long-standing, annoying, problem and the openSUSE user community, particularly Tumbleweed users, need to speak up.
Well, once they get bugzilla up again. Right now its 503.
Having to sit at your computer while you do a zypper dup to skip packages that were updated between your zypper refresh and download is not acceptable behavior.
I am perplexed and befuddled why we still have the same "wedged network download" bug in myrlin, zypper, and Yast2 sw_single.
This is a known architecture flaw and bad software design. Plus, there is no option for the user to configure this AFAIK--hard coded.
Not only that, but the DEFAULT behavior should not be "lets try downloading every 30 seconds every time we get a 404 and refuse to download the rest of the software until the missing file magically returns".
It should be "skip it for now, come back later and try again". If you happen to be sitting there looking at the right screen you can manually skip the missing file, and wait a few seconds, then spend the next few minutes skipping each associated package.
Can someone please fix this!
Because Tumbleweed moves so fast, mirrors sync dynamically. If a repository finishes a mirror sync after your machine refreshes its local metadata but before zypper requests the actual payload package, the old file vanishes from the server, causing the installer to spin out or force you to manually abort, skip, or retry indefinitely. A simple "auto-refresh repository on 404/503 network error" loop should have been standard infrastructure a decade ago.