[opensuse] Zypper and restart?
I'm having troubles with my cable service. The symptoms are a reduced bandwidth and intermittent reset. While email can survive this and web service can - sort of - it makes a mess of updates from opensuse.org. I run 'zypper up' and hope that the updates get completed, even at the reduced bandwidth, before a rest. Not always. And certainly not for kernel updates of the larger RPMs. Now I know that cURL can continue from an aborted transfer and it seems that Wget can be a bit smarted about figuring out the 'continue' functionality. But how can I get zypper to take advantage of this? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hey there, zypper should cache everything it has already completely downloaded, to make sure update does not start before you have all required packages you can use: zypper dup --download in-advance Cheers, Benjamin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I don't think zypper can deal with that. I updated an arm board with a dodgy wifi connection, kept having to restart it - what was downloaded was fine, the rest was downloaded from scratch. -- Per Jessen, Zürich (5.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/14/2019 04:28 PM, Anton Aylward wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded, Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
Well zypper can not handle the restart of cancelled downloads. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?), then use something like curl to download them and then back to zypper to install them. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14/03/2019 18.33, Dave Howorth wrote:
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?),
Not that I know. That would be a nice feature to have on machines that are not connected to Internet, or using an expensive connection. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Thu, 14 Mar 2019 18:37:56 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 14/03/2019 18.33, Dave Howorth wrote:
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?),
Not that I know.
What does zypper list-updates do then?
That would be a nice feature to have on machines that are not connected to Internet, or using an expensive connection.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 14 Mar 2019 20:09:27 +0000 Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 14 Mar 2019 18:37:56 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 14/03/2019 18.33, Dave Howorth wrote:
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?),
Not that I know.
What does zypper list-updates do then?
Or zypper list-patches for that matter But I suspect just repeating zypper update --download-only until zypper says it has nothing to do might work.
That would be a nice feature to have on machines that are not connected to Internet, or using an expensive connection.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: <alpine.LSU.2.21.1903142211420.31131@minas-tirith.valinor> El 2019-03-14 a las 20:20 -0000, Dave Howorth escribió:
On Thu, 14 Mar 2019 18:37:56 +0100 "Carlos E. R." <> wrote:
On 14/03/2019 18.33, Dave Howorth wrote:
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?),
Not that I know.
What does zypper list-updates do then?
Or zypper list-patches for that matter
But I suspect just repeating
zypper update --download-only
until zypper says it has nothing to do might work.
Not if it hangs on big files, and it always tries them from start, not from the already downloaded point, which is what i understand Anton is saying. - -- Cheers Carlos E. R. (from openSUSE Leap 15.0 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCXIrDrBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcWvwBAIejgnqeKwY98D40IsyS 2gUQMZ0PICsiaPRvEEAUraa2AP9AaxDrijEKx77XfiZd9N/1R3CL1P61+NUpOeGI 2zBteQ== =mqQ5 -----END PGP SIGNATURE-----
On 2019-03-14 5:12 p.m., Carlos E. R. wrote:
Not if it hangs on big files, and it always tries them from start, not from the already downloaded point, which is what i understand Anton is saying.
YES! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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 libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007fa18c6f0000) and # ldd /usr/lib64/libzypp.so.1600 | grep curl libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f522a353000) It *IS* using the curl library. So why can't zypper do a restart? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/03/2019 02.22, 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?
It now uses curl library. It used other things before.
No, wait a moment: # ldd /usr/bin/zypper | grep curl libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007fa18c6f0000)
and
# ldd /usr/lib64/libzypp.so.1600 | grep curl libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f522a353000)
It *IS* using the curl library. So why can't zypper do a restart?
Good question. I suggest a hack. In the zypper og you can find exactly what file it is trying to download. You can download it yourself and put it where it is expected. The directory is, probably: /var/cache/zypp/packages/download.opensuse.org-oss_1/ The last directory you can obtain from here: zypper lr --detail | less -S It is on the Alias column, not the name column. I also suggest that on yast, repository configuration, you activate "keep downloaded packages". Explanation another day, it is 3 AM here ;-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
I added your suggestion to the zypper media backend enhancement bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1125470 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 libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007fa18c6f0000)
and
# ldd /usr/lib64/libzypp.so.1600 | grep curl libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f522a353000)
It *IS* using the curl library. So why can't zypper do a restart?
-- Benjamin Zeller <bzeller@suse.de> Systems Programmer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Mar 15, 2019 at 8:56 AM Benjamin Zeller <bzeller@suse.de> wrote:
I added your suggestion to the zypper media backend enhancement bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1125470
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.
Could you point to code? As far as I can tell, libzypp MediaCurl.cc is using cURL curl_easy_* API which is single threaded. It could be challenging to resume download though as file is stored under temporary random name until download is complete, so finding incomplete file (and verifying that it was from previous aborted attempt) is not entirely straightforward. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
You want to look here: https://github.com/openSUSE/libzypp/blob/master/zypp/media/MediaMultiCurl.cc there its using the curl_multi APIs . On 3/15/19 8:53 AM, Andrei Borzenkov wrote:
On Fri, Mar 15, 2019 at 8:56 AM Benjamin Zeller <bzeller@suse.de> wrote:
I added your suggestion to the zypper media backend enhancement bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1125470
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.
Could you point to code? As far as I can tell, libzypp MediaCurl.cc is using cURL curl_easy_* API which is single threaded.
It could be challenging to resume download though as file is stored under temporary random name until download is complete, so finding incomplete file (and verifying that it was from previous aborted attempt) is not entirely straightforward.
-- Benjamin Zeller <bzeller@suse.de> Systems Programmer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
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 libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007fa18c6f0000)
and
# ldd /usr/lib64/libzypp.so.1600 | grep curl libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f522a353000)
It *IS* using the curl library. So why can't zypper do a restart?
Just one of those things that were not considered - a mostly working internet connection. It doesn't sound too difficult to do though: if download is incomplete, just pass the current file size to the libcurl invocation. As a work around, download and install those big files manually. (with curl). -- Per Jessen, Zürich (6.7°C) member, openSUSE Heroes -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/03/2019 07.53, Per Jessen wrote:
Anton Aylward wrote:
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 libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007fa18c6f0000)
and
# ldd /usr/lib64/libzypp.so.1600 | grep curl libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f522a353000)
It *IS* using the curl library. So why can't zypper do a restart?
Just one of those things that were not considered - a mostly working internet connection. It doesn't sound too difficult to do though: if download is incomplete, just pass the current file size to the libcurl invocation.
The reason is clear from comments from Benjamin Zeller and Andrei Borzenkov: the partial download is stored with a randomized name (why? I don't know/guess). Restart zypper and it uses another name. Zypper does multiple download threads (as I thought), which is able to cope with interrupted downloads at the remote end, but not all threads failing, on the local side. Curious. It seems that the application should recover if left alone sufficient time, though. I wonder if limiting the number of simultaneous downloads would help or if it is possible. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Le 15/03/2019 à 02:22, Anton Aylward a écrit :
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.
you may need a torrent system, but wont wget do the job with http, if internet works? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2019-03-14 a las 20:09 -0000, Dave Howorth escribió:
On Thu, 14 Mar 2019 18:37:56 +0100 "Carlos E. R." <> wrote:
On 14/03/2019 18.33, Dave Howorth wrote:
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?),
Not that I know.
What does zypper list-updates do then?
Yes, it is the list of updates, but not in a form usable to do the download directly. Not like this: URL/path/file destination_directory_to_put_it_in. - -- Cheers Carlos E. R. (from openSUSE Leap 15.0 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCXIrC8Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcYjkA/1epw5l2cNgvr/hVD8CX Mnv2W+EcTgSboa4VaeIHpO7OAP9/+qfzZ4AWIoRWBYGiBi6s8ylzZH/kkc4QfCxK xK/Prg== =5Po6 -----END PGP SIGNATURE-----
Op donderdag 14 maart 2019 18:33:38 CET schreef Dave Howorth:
On Thu, 14 Mar 2019 11:28:39 -0400
Anton Aylward <opensuse@antonaylward.com> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?), then use something like curl to download them and then back to zypper to install them. AFAIK zypper uses curl. See the recent issues with zypper segfaulting on a (lib)curl bug.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-03-14 1:33 p.m., Dave Howorth wrote:
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?), then use something like curl to download them and then back to zypper to install them.
Indeed. I'm using curl to download a kernel RPM. I've had to restart it three times now and curl seems good at doing the restart :-) BUT ... I'll need to verify the integrity of the RPM, won't I? Hmm "rpm --verify ..." doesn't seem to verify the integrity of single RPM by itself, only with reference to what it is when installed. Or, if you will, verifying that what is installed has not been corrupted by comparing it with the original RPM. Which is not what I'm addressing here. Suggestions, please. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 15/03/2019 à 16:40, Anton Aylward a écrit :
Suggestions, please.
opensuse allows torrent download https://software.opensuse.org/distributions/leap may be there is a way to download the rpm by torrent, that have integrated integrity check? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
15.03.2019 18:40, Anton Aylward пишет:
I'll need to verify the integrity of the RPM, won't I?
Hmm "rpm --verify ..." doesn't seem to verify the integrity of single RPM by itself, only with reference to what it is when installed. Or, if you will, verifying that what is installed has not been corrupted by comparing it with the original RPM.
Which is not what I'm addressing here.
Suggestions, please.
rpm -K -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2019-03-15 11:40 (UTC-0400):
I'm using curl to download a kernel RPM. I've had to restart it three times now and curl seems good at doing the restart :-)
BUT ...
I'll need to verify the integrity of the RPM, won't I?
Hmm "rpm --verify ..." doesn't seem to verify the integrity of single RPM by itself, only with reference to what it is when installed. Or, if you will, verifying that what is installed has not been corrupted by comparing it with the original RPM.
I've been using wget for large downloads for well over two decades, since long before switching from POTS to broadband, in part to preserve the server's timestamps, but also to handle random needs to restart after broken internet connectivity. I quit routine verification not terribly long after. All my TW kernels, most other openSUSE kernels and occasionally other large files, such as kernel-firmware, are downloaded to LAN server as they become discovered. Subsequently TW's get installed with RPM through an NFS connection. With Leap I copy new kernels to /var/cache/zypp/packages/*, usually update/*, where zypper automatically notices their presence, then answer y to "remove lock" when zypper is asked to install. A nice side effect is a bank on the local server of previous kernel rpms otherwise unavailable for rough bisections. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/03/2019 16.40, Anton Aylward wrote:
On 2019-03-14 1:33 p.m., Dave Howorth wrote:
On Thu, 14 Mar 2019 11:28:39 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 2019-03-14 11:12 a.m., Benjamin Zeller wrote:
zypper should cache everything it has already completely downloaded,
Yes, but that is NOT what I'm talking about. I'm talking about restarting INCOMPLETE downloads.
I suspect you might need to get the list of require files from zypper (I assume that is possible?), then use something like curl to download them and then back to zypper to install them.
Indeed. I'm using curl to download a kernel RPM. I've had to restart it three times now and curl seems good at doing the restart :-)
BUT ...
I'll need to verify the integrity of the RPM, won't I?
No. When you try to install it, it will be verified prior to installing. Otherwise, read re gpg signing in rpm. I had a quick look in the man but did not locate the section. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (9)
-
Andrei Borzenkov -
Anton Aylward -
Benjamin Zeller -
Carlos E. R. -
Dave Howorth -
Felix Miata -
jdd＠dodin.org -
Knurpht-openSUSE -
Per Jessen