On Sunday 15 April 2007 23:36, Mark Goldstein wrote: > On 4/16/07, Rajko M. <[EMAIL PROTECTED]> wrote: > > Mark, > > > > look at TCP/IP traffic. > > There is nothing if you disable refresh for all sources. > > What I see is short burst when it is refreshing update repository, > > packman and guru, and than nothing. The rest of activity is data base > > check. > > Thanks Rajko, > > My impression is that somehow local data base was "invalidated". I did > not analyze traffic, but I used "zypper -v up" and also observed it in > YaST2 message boxes, that both updaters were definitely re-reading > patches and package descriptions from non-oss and oss repositories on > download.opensuse.org. So it took a lot of time (and during this time > I observed zypper indicating [-21879%] readiness of package file :-( ) > . I thought it may be something with my home machine, but today I ran > update on my office machine that was NOT on the network yesterday and > I can see that zypper re-reads oss and non-oss repositories also. > Looks like there is some indication for updater to re-read repository > even though it is marked as non-refreshable.
My first post was about YOU (online updates) that is not that verbose. Now zypper -v pch and it downloaded only repositories marked to be refreshable. zypper -v ref refreshed everything as expected. zypper -v up is acting like first command zypper -v pch. > [-21879%] I got even better, but temporary, the final number is 100%. and observed even more glitches in output, but I have to run zypper in another terminal to see the output. Done. It is the same. So it seems to be a bug in zypper output. -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
