[SLE] When will delta and patch rpms be supported again?
Hi, Can anybody give an approximate date for the update system's resumption of the use of delta and patch RPMs, which had been working well for a long time? So far this morning, the update has been running for about three quarters of an hour, and has got to "18%". Most of that time has been network traffic (on 1Mb/s ADSL, at about 120-130kB/s), although there's been a lot of CPU as well. On a related note, it seems that downloading and installing updates happen alternately, rather than the download process being continuous, and each update being installed in parallel with the ongoing download process once it has arrived. This strikes me as very inefficient, since downloading data and installing RPMs are approximately orthogonal in their use of resources (the former uses lots of network bandwidth, and a proportionally very small amount of CPU and disc bandwidth, whereas the latter uses lots of disc bandwidth and CPU). Allowing subsequent downloads to continue as each package is installed would surely speed up the process significantly ... anything which does that would be welcome (hence my original subject line!) -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wednesday 26 July 2006 09:59, William Gallafent wrote:
Can anybody give an approximate date for the update system's resumption of the use of delta and patch RPMs, which had been working well for a long time?
Speaking of "Working well", today the updater got as far as about 42%, then a dialogue box "Transaction failed" appeared. So, I dismiss that dialogue box, then my (2xAthlonMP 1.6GHz) CPUs and HDDs (RAID0, about 60MB/s) get hammered for well over a minute, and three patches appear in the update window. Unfortunately, another dialogue box appears, saying "zmd isn't running" or words to that effect. When I dismiss that one, my updates window disappears, as does the icon in the system tray. No indication what I'm supposed to do next. So, I ran "Software Update" from the KDE/System/Configuration menu, which has produced the three updates as before. I pressed update, and the progress bar moved quite quickly to 100%. It then sat there, with everything greyed out, for about _two_ minutes before changing to 99% and saying "Finishing ...". This is utterly insufficient progress reporting. This new updater was apparently pre-alpha-quality when 10.1 was released, and is perhaps beta now, and should not have replaced the old system until a few more bugs had been ironed out. It does seem to work now, albeit with occasional crashes, which is good news, but the hugely excessive network bandwidth and CPU usage is still a problem, as is the insufficient progress reporting - sitting for ages with a progress bar at 0 or 100, the only way to tell something's happening being to watch CPU, disc or network activity with e.g. gkrellm. Thankfully, "the update was successful". That leaves me with one final question: How can I straightforwardly check that I actually have a fully updated system? Crashes mid-way through updates have not left me feeling confident that everything that should be installed is installed. Today, for example, there must have been between ten and twenty first time round -> crashed at 42% -> only three more when I restart the updater ... suspicious. -- Bill Gallafent. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (1)
-
William Gallafent