On Friday 24 August 2007 06:08:23 am Stanislav Visnovsky wrote: > Dňa Friday 24 August 2007 11:58:25 Rajko M. ste napísal: > > On Friday 24 August 2007 04:41:38 am Christoph Thiel wrote: > > > On Fri, Aug 24, 2007 at 04:35:59AM -0500, Rajko M. wrote: > > > > On Friday 24 August 2007 03:43:43 am Stanislav Visnovsky wrote: > > > > > Dňa Friday 24 August 2007 10:33:46 Andreas Jaeger ste napísal: > > > > > > "Rajko M." <[EMAIL PROTECTED]> writes: > > > > > > > I added 10.3 update repository, and it takes quite some time to > > > > > > > see the end Online Update configuration. > > > > > > > > > > > > > > What is purpose of refreshing all repositories when one wants > > > > > > > to configure online update? > > > > > > > > > > > > No idea - I suggest to file a bugreport > > > > > > > > > > Definitely. > > > > > > > > > > Stano > > > > > > > > Done. > > > > bug #304211 > > > > > > > > BTW, Martin Vidner question about zypper > > > > [zypp-devel] listing patches - consider only some repos? > > > > seems to address the same. > > > > > > IIRC we used to have a flag in susetags, that could flag a repository > > > to be "none-changing". Metadata for a repository like that (e.g. the > > > ftp tree for a released product), would never have to be > > > downloaded/checked again. Klaus? > > > > > > > > > Best, > > > Christoph > > > > Under 'update/10.3' I don't expect anything except patches and there is > > no need to run all repositories refresh to get data for patches. > > AFAIK there is no way to flag a repository to be one providing patches. So, > this is almost impossible right now and will definitely fail in some use > cases.
The flag can be the name, like 'update'. > I think it is correct to refresh all repos that have autorefresh enabled. Just to make sure: - enabled repositories, with - enabled refresh. > You never know the dependencies among the packages, it might turn out that > a patch will trigger an update from a different repository. I got always feeling that (security) update repository is stand alone, it doesn't contain patches (packages) that lead to use of other repositories. If it will demand other repositories than for successful update I have to make sure that all of them are online and up to date, which brings more conditions in equation and rises chance for intermittent failures. Something that we had never before. If I was able to contact update server, I was able to get all updates. > However, configuring repositories should not refresh, there is no need to > do it. I considered first YOU start right after as a part of configuration. Having URL listed doesn't mean that I can use repository. The complaint was about long time it took to start you, like repository initialization. > Stano > > > Current setup here has only one repository that is disabled as it is > > duplicate, the rest is Factory and in a few days it will start to change > > again, so I'll keep that with refresh on. BTW, I noticed download of root and boot files, when new Factory installation was initialized!? That is increasing initialization time substantially. I stopped zypper twice, considering endles download to be another bug or metadata corruption, and then used YaST that is more verbose by default, to see what is downloaded. My Internet connection is good pipe. I can imagine how this appear on dial up. What would be need for them? Why it loads ppc in a system that is x86_64? I can see need for x86, but ppc. It will save some initialization time if there will be switch to list all architectures, and default should be the installed one. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
