Mailinglist Archive: opensuse (389 mails)

< Previous Next >
Re: [opensuse] Zypper and restart?
I added your suggestion to the zypper media backend enhancement bug

However in its current codebase zypper does not handle download
restarts. Not sure if and how easy it is
to enable this, since zypper uses already multiple downloads of the same
file from different mirrors and I don't
know if that mixes well with restarts.

For the time being you can as suggested grep the rpms it fails to
download from the log and pass them to "zypper install" manually, or
place them into cache as suggested.

On 3/15/19 2:22 AM, Anton Aylward wrote:
On 2019-03-14 4:20 p.m., Dave Howorth wrote:
But I suspect just repeating

zypper update --download-only

until zypper says it has nothing to do might work.
This does not address my problem.

Repeatedly trying to download the 65MB new kernel and having at fail at 36%,
43%, 21% ... on and on and on

if I can't download the complete RPM then your idea is not of use.

The point I am making is that the error i have is cuasing my cable modem to
reset intermittently so large downloads fail.

I don't know what zypper library uses 'under the hood.

The suggestion to get the list and then go get them manual using cURL with
restart with restart, with restart with restart until I get the complete RMP
seems the only viable one.

Oh buqquer, I hate that sort of manual work.
Why isn't zypper using cURL under the hood so that this can be automated?

No, wait a moment:
# ldd /usr/bin/zypper | grep curl => /usr/lib64/ (0x00007fa18c6f0000)


# ldd /usr/lib64/ | grep curl => /usr/lib64/ (0x00007f522a353000)

It *IS* using the curl library.
So why can't zypper do a restart?

Benjamin Zeller <bzeller@xxxxxxx>
Systems Programmer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755;
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups