This mornings update and zypper - A suggestion
Am 12.10.21 um 16:25 schrieb Larry Len Rainey:
zypper updates are failing again due to mirror problems - the machine in Tampa went fine but mine got stuck
How about an option in zypper instead of Abort Retry and Ignore add an option for "change repo and retry"
I assume you mean "change mirror and retry"? I guess retrying could even automatically fall back to a different mirror. (The original request to download.opensuse.org will typically be a "302 Found" that lists the best mirrors via "Link" headers. So one might just go through that list and try a couple more entries.) Though as always the question is whether that's worth it, i.e. how often does that happen, and how often is it the mirror as opposed to the user's internet connection. If you indeed want to change the repository, that would of course have to run the solver again, so you might as well abort and start a new update. The "retry" option here is just about retrying a download of that particular package version that the solver has chosen.
* Larry Len Rainey
Since 15.3 came out - I see this somewhere almost every day.
I help retired people keep their OpenSUSE working - I have some that know to retry after an hour and that sometimes works
Today 7 people said they cannot get output - I had to change their repo pointers to get them fixed.
ssh and rsync are a blessing to remote fixing. (I have 2 scripts for them - letmein - enables port 22 - and keepout - disables port 22. so they are not hacked - yes their routers forward port 22 to their computer or laptop - it also gives them the IP of their router and computer to email me (or call me and read it to them)
old repo were (http)
I had to change all the 2 list to the 1 list ( I just rsync them to that directory on my machine.)
(Yes, i know I could just use sed change the download. to provo-mirror but their might be other repos with download that do not need to be changed)
llrainey@VM1:~> grep http /etc/zypp/repos.d/2/* /etc/zypp/repos.d/2/repo-backports-update.repo:baseurl=http:// download.opensuse.org/update/leap/$releasever/backports/ /etc/zypp/repos.d/2/repo-non-oss.repo:baseurl=http://download.opensuse.org/ distribution/leap/$releasever/repo/non-oss/ /etc/zypp/repos.d/2/repo-oss.repo:baseurl=http://download.opensuse.org/ distribution/leap/$releasever/repo/oss/ /etc/zypp/repos.d/2/repo-sle-update.repo:baseurl=http://download.opensuse.org/ update/leap/$releasever/sle/ /etc/zypp/repos.d/2/repo-update-non-oss.repo:baseurl=http:// download.opensuse.org/update/leap/$releasever/non-oss/ /etc/zypp/repos.d/2/repo-update.repo:baseurl=http://download.opensuse.org/ update/leap/$releasever/oss/ llrainey@VM1:~> grep http /etc/zypp/repos.d/1/* /etc/zypp/repos.d/1/repo-backports-update.repo:baseurl=https:// provo-mirror.opensuse.org/update/leap/$releasever/backports/ /etc/zypp/repos.d/1/repo-non-oss.repo:baseurl=https://provo-mirror.opensuse.org /distribution/leap/$releasever/repo/non-oss/ /etc/zypp/repos.d/1/repo-oss.repo:baseurl=https://provo-mirror.opensuse.org/ distribution/leap/$releasever/repo/oss/ /etc/zypp/repos.d/1/repo-sle-update.repo:baseurl=https:// provo-mirror.opensuse.org/update/leap/$releasever/sle/ /etc/zypp/repos.d/1/repo-update-non-oss.repo:baseurl=https:// provo-mirror.opensuse.org/update/leap/$releasever/non-oss/ /etc/zypp/repos.d/1/repo-update.repo:baseurl=https://provo-mirror.opensuse.org/ update/leap/$releasever/oss/ llrainey@VM1:~>
On 10/12/21 12:18 PM, Aaron Puchert wrote:
Am 12.10.21 um 16:25 schrieb Larry Len Rainey:
zypper updates are failing again due to mirror problems - the machine in Tampa went fine but mine got stuck
How about an option in zypper instead of Abort Retry and Ignore add an option for "change repo and retry"
I assume you mean "change mirror and retry"? I guess retrying could even automatically fall back to a different mirror. (The original request to download.opensuse.org will typically be a "302 Found" that lists the best mirrors via "Link" headers. So one might just go through that list and try a couple more entries.)
Though as always the question is whether that's worth it, i.e. how often does that happen, and how often is it the mirror as opposed to the user's internet connection.
If you indeed want to change the repository, that would of course have to run the solver again, so you might as well abort and start a new update. The "retry" option here is just about retrying a download of that particular package version that the solver has chosen.
add specific mirrors to repos that you have difficulty with, such as: [Tumbleweed.OSS] name=openSUSE-Tumbleweed OSS enabled=1 autorefresh=0 baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ http://suse.mobile-central.org/tumbleweed/repo/oss/ http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ type=rpm-md -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
participants (3)
-
Aaron Puchert -
Larry Len Rainey -
Patrick Shanahan