Op woensdag 18 november 2015 10:02:10 schreef Roger Oberholtzer:
On Wed, Nov 18, 2015 at 9:31 AM, Per Jessen <per@computer.org> wrote:
Wouldn't this also happen during a normal installation? (it sounds to me as if ZYPP_MULTICURL=0 cures the symptom, but not the problem).
I did the install from an ISO image. I did not choose to do updates at that time because I knew I could not specify ZYPP_MULTICURL=0 to the installer. So I thought I would do the updates after install.
It is big RPMs that seem to be most effected. For example, my update wants texlive-cm-super-fonts. It gets to +90% percent, and then immediately fails, retires to 90%, fails, etc. If I tell it to ignore the failed RPM it continues to download the others. But of course the install will fail because an RPM is missing...
I once had a similar problem in which the downloaded rpm many times failed the security check; also big rpms. In that case I found the location where the rpm should go, don't remember where, and searched for the URL of the rpm on the download.opensuse.org site. After that I used: curl -L <URL> -o <local_destination> to get the rpm, performed the security check, and started zypper again. Apparently zypper found the rpm was OK and continued with the rest. I may have needed to repeat the procedure with other rpms, but finally zypper could perform the update. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org