I’ve been trying to update to the latest Tumbleweed on one box since last night.
The packages start downloading then just stall out with “starting”
Mirrorbrain is sending me to a flaky mirror.
How do I override that and get a working mirror?
Hi
Just pick a mirror close by from the list and add it (and disable the download one);
http://mirrors.opensuse.org/
Thanks.
I’ll try and find a good one.
Some of them are hit or miss.
Welp
Looking at the list of what the mirrors have close by they don’t show Tumbleweed.
Factory they show but not Tumbleweed.
Factory is not Tumbleweed.
This looks like a long process.
Hi
I use this one;
http://mirrors1.kernel.org/opensuse/tumbleweed/
You need to use the full list and look in the TW column (second one).
Yes, that happened to me. However, it turned out to be the packman repo that was hanging. I don’t think mirror brain is involved with that. It looks as if packman is having problems (maybe a DoS attack?).
It’d hang on downloading packages too
Never hung on getting the list really except for the first try and it was on the OSS repo.
Blew right through Packmans repos and the Google stuff.
I do zypper -v dup so I can see what’s going on.
Only 3 US Tumbleweed mirrors from what I saw.
That’s not good.
That needs to be addressed too.
Hi
The mirror issue (as in what’s available) is at the discretion of the mirror owners, in that case you would need to contact a mirror owner in your locale and ask them if they could add the tumbleweed repo.
I’m experiencing the same problem installing Leap into a virtual machine. I’m very confused. Isn’t zypper supposed to be implementing metalink? Shouldn’t a stuck download time out and try another mirror automatically? If not, what was the point of adding metalink to zypper in the first place?
I can’t get any system here to update without perpetually hanging, 13.2 or Leap. Something is really wrong with the North American mirrors right now and I don’t get why Metalink isn’t routing around it (or even why zypper doesn’t time out).
Hi
I just did a force refresh and it all worked fine on Tumbleweed (@download.opensuse.org), then installed pithos, it installed fine along with it’s dependencies…
Now I only have Oss and Update repos active, no packman or other repos.
So as a test I added my OBS openSUSE general project and installed a couple of packages, all worked fine…
Searching for software at software.opensuse.org also appears to be failing with this message:
Error connecting to http://download.opensuse.org/tumbleweed/repo/oss/suse/setup/descr/appdata-86c7f26f7065aabfbabf52ef0e7d5f9e.xml.gz: Response was: #<Net::HTTPNotFound:0x00000004dd1798> <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01//EN” “http://www.w3.org/TR/html4/strict.dtd”> <html> <head> <title>404 - Not Found</title> <style type=“text/css”> body { font-size: 62.5%; } #container { font-size: 62.5%; max-width: 600px; margin: auto; margin-top: 2%; border: 4px solid #efefef; padding: 0px 20px; color: #444; font-family: Verdana,helvetica,sans-serif; font-size: 1.25em; } h1 { color: #6D84B4; font-size: 1.5em; } #footer { text-align: right; margin-top: 25px; } </style> </head> <body> <div id=“container”> <h1>Error 404 - Not Found</h1> <p>The requested resource was not found.<br>Make sure you entered the correct URL in your browser.</p> <p id=“footer”>lighttpd/2 - openSUSE is good for you</p> </div> </body> </html>
The lizard is falling apart. 
Hi
A known (reoccurring) issue since Friday evening, bit hard to get it fixed over the weekend since it’s in Germany…
It’s back to “normal” from here.
I had exactly the same problem – North America, zypper up after a LEAP 42.1 install – two days ago.
I’m going to submit a crazy feature request: That there be a weekly update re-release of the stable (42.1,13.2) ISO images. Not the same as Tumbleweed – just the stable release but with all the latest RPMs from the stable repositories. Exactly what you end up with via a net install or afterzypper up on top of the stale ISOs that are there now.
I don’t like relying on online installs/updates because these kinds of failures can result in a broken system. If an ISO download completes and the md5sum/shaNsum/pgp’s confirm, you know you’re good to go.
The question in cases like this is not whether it can be done or not, but who’s going to do it. Stuff like this needs maintenance and people who do the job.
BTW: are you aware of SUSE Studio? It takes of bit of learning, but it allows you to build your own install / live media.
I know I’m being naive, but in the best case scenario this could be a cron job. I’m assuming there has to be a script that builds a release from a mount point / directory tree / or something. You’re probably right, though, that at minimum someone would have to check up on it, the mirrors would have to pick it up, etc.
BTW, my experiences this past weekend illustrate why it would be useful. I installed 42.1 from an ISO dated 2015-10-29, and the post-installzypper up updated over 800 packages – approximately as many as in the install itself. I was effectively doing a net install, just with double the work.
I’m going to try to file the request, and if it falls on deaf ears, so be it.
Yes, thanks. I looked briefly at it and the learning curve looked fairly steep. I plan on trying it at some point. Unclear how I would get all the RPMs (not just the ones on my running system), but I’ll read/research/experiment and see how far I get.