[opensuse] "Cleaning repository 'Packman Repository' cache" always takes a lot of time.
I have noticed this behavior on multiple machines. It takes a lot of time to finish "Cleaning repository 'Packman Repository' cache". Any ideas what might be the problem? -- Regards, Aniruddha Please adhere to the OpenSUSE_mailing_list_netiquette http://en.opensuse.org/OpenSUSE_mailing_list_netiquette -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-10-30 at 11:44 +0100, Aniruddha wrote:
I have noticed this behavior on multiple machines. It takes a lot of time to finish "Cleaning repository 'Packman Repository' cache". Any ideas what might be the problem?
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, maybe your question is for Packman mailing list. BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying. Cheers! -- Igor Jagec
On Tue, 2007-10-30 at 13:57 +0100, Igor Jagec wrote:
On Tue, 2007-10-30 at 11:44 +0100, Aniruddha wrote:
I have noticed this behavior on multiple machines. It takes a lot of time to finish "Cleaning repository 'Packman Repository' cache". Any ideas what might be the problem?
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, maybe your question is for Packman mailing list.
BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying.
Cheers!
I agree. Yast2 seems to want to scan repositories even during functions that have nothing to do with software management. As for Packman, it is a pretty big repository, thus longer scanning and initialization. I tend to disable that repository (and others) and enable it only when I want to look for something on Packman. It is annoying to have to remember to turn on and off repositories all the time. Sometimes, I just want to go to Software Management just to see what is currently installed, and not have to scan the repositories. As for the time changing, this was a bug which is claimed to be fixed with 2.16. But, even though I told them it isn't, they still consider it fixed. (shrug) Bug 327336 - https://bugzilla.novell.com/show_bug.cgi?id=327336 -- ---Bryen--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-10-30 at 08:36 -0500, Bryen wrote:
As for the time changing, this was a bug which is claimed to be fixed with 2.16. But, even though I told them it isn't, they still consider it fixed. (shrug)
I don't know, I don't use any package from the Factory tree. Here's the version I have: yast2-ntp-client-2.15.12-7.noarch -- Igor Jagec
On Tue, 2007-10-30 at 13:57 +0100, Igor Jagec wrote:
On Tue, 2007-10-30 at 11:44 +0100, Aniruddha wrote:
I have noticed this behavior on multiple machines. It takes a lot of time to finish "Cleaning repository 'Packman Repository' cache". Any ideas what might be the problem?
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, maybe your question is for Packman mailing list.
BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying.
Cheers!
I forwarded your mail to the zypp-devel since it also happens in the zypp backend. -- Regards, Aniruddha Please adhere to the OpenSUSE_mailing_list_netiquette http://en.opensuse.org/OpenSUSE_mailing_list_netiquette -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Igor Jagec escribió:
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway,
I tried changing data and time and yast does not read the package database ..what opensuse version are you using ?
BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying.
This happends because some yast modules have issues, this has been discussed in bugzilla. However in the package manager module is expected to happend. -- "Two things are infinite: the universe and human stupidity; and I'm not sure about the universe." --Albert Einstein Cristian Rodríguez R, Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-10-30 at 19:30 -0300, Cristian Rodriguez wrote:
Igor Jagec escribió:
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, I tried changing data and time and yast does not read the package database
Right click on Clock Applet of GNOME Panel - Change Date or Time - Change, and it pops up. Would it be helpful if I send you Yast logs?
what opensuse version are you using ?
10.3
However in the package manager module is expected to happend.
That's ok, but I've experienced that with Date and Time module and Language module (when I wanted to add some extra languages). -- Igor Jagec
On Tuesday 30 October 2007 07:57:22 am Igor Jagec wrote:
On Tue, 2007-10-30 at 11:44 +0100, Aniruddha wrote:
I have noticed this behavior on multiple machines. It takes a lot of time to finish "Cleaning repository 'Packman Repository' cache". Any ideas what might be the problem?
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, maybe your question is for Packman mailing list.
BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying.
Cheers!
Is that 10.2 or 10.3. In 10.2 I can confirm behavior, but in 10.3 I can't recall. Though, I can't say for date and time module in 10.2, as that is kept in sync with 'xntpd'. Apropos Packman. So far I recall they had a problem that is fixed, but /var/cashe/zypp/zypp.db might be in bad shape. Can you delete it and run YaST > Software Management or zypper refresh to create new zypp.db and then check is it slow again. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Tuesday 30 October 2007 07:57:22 am Igor Jagec wrote:
On Tue, 2007-10-30 at 11:44 +0100, Aniruddha wrote:
I have noticed this behavior on multiple machines. It takes a lot of time to finish "Cleaning repository 'Packman Repository' cache". Any ideas what might be the problem? Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, maybe your question is for Packman mailing list.
BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying.
Cheers!
Is that 10.2 or 10.3.
In 10.2 I can confirm behavior, but in 10.3 I can't recall.
Though, I can't say for date and time module in 10.2, as that is kept in sync with 'xntpd'.
Apropos Packman. So far I recall they had a problem that is fixed, but /var/cashe/zypp/zypp.db might be in bad shape. Can you delete it and run YaST > Software Management or zypper refresh to create new zypp.db and then check is it slow again.
I'll agree with Rajko. 10.2 was God awful slow. 10.3 is relatively fast compared to 10.2. But, what you have to remember is that with "refresh" set to on in yast, yast must download the xml index of all the rpms contained at the repository and then compare that list to the list of rpms installed on your system. When the index contains "new" versions of files, Yast/zypper need to clean the master index that lives on your computer to get rid of the old version information and add the new information. If it get way to slow, then you can delete your local index files and let zypper rebuild them. This has been mentioned in several threads. The question is how slow is slow in your case 30-90 seconds? Or is it start software management, go get a cup of coffee, and just check back to see if it is done yet slow? If the latter, then you might consider wiping your indexes and letting them be rebuilt. Gurus, chime in if you have better numbers on how slow is too slow. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello: This might be a little bit offtopic. I do not want to offend anybody at openSUSE and don't want to be rude but I think openSUSE could not make a decent package manager since 9.3 or 10.0. Even in 10.3. These are the reasons why I don't use YAST package manager: - YAST package manager is extremely slow. - Furthermore why does it have to refresh all repositories if you want only remove or check something? - You still can't change the order how repositories are processed (discussed elsewhere). - I am lost in the several options: online update, automatic online update, software repositories, community repositories, add on product etc. Who can follow this? And all of them after starting always refreshes and refreshes... - In the software manager takes forever to switch from one package group to the other. - In 10.2 the software manager always downloaded all the different package descriptor language files (xmls?) further slowing down refreshing. (I did not checked if it had changed in 10.3) For this reason I use smart package manager. It's search function not as good as yast's but: - much easier to switch on and off repositories - one can choose by hand which repositories and when to refresh I started using smart exlusively in 10.2. I was hoping that in 10.3 I can switch back to YAST but unfortunately it is not polished enough. What I don't undertsand that the last 1.5-2 years (since the release of 10.1) was not enough to fix substantial problems and replace a good package manager (former yast) to another that also works flawlessly. Irrespectively of this openSUSE (all versions) is generally a very stable, reliable and easy to use linux system. IG Filmek egy kattintásra tőled – Zene és szöveg, Híd Terabithia Földjére, Kiképzés és még több új film a T-Online Tékában! ________________________________________________________ http://www.teka.t-online.hu -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-10-31 at 11:22 +0100, Istvan Gabor wrote:
This might be a little bit offtopic. I do not want to offend anybody at openSUSE and don't want to be rude but I think openSUSE could not make a decent package manager since 9.3 or 10.0. Even in 10.3.
Try Yum and you'll see what slowness really is :) I use openSUSE 10.3 and command-line Zypper, and it works just fine. There are some features missing (like repo prioritisation, and so on), but that was planned for the future releases. -- Igor Jagec
Istvan Gabor wrote:
Hello:
These are the reasons why I don't use YAST package manager: - Furthermore why does it have to refresh all repositories if you want only remove or check something? ACK. - You still can't change the order how repositories are processed (discussed elsewhere). - In the software manager takes forever to switch from one package group to the other. ACK. - In 10.2 the software manager always downloaded all the different package descriptor language files (xmls?) further slowing down refreshing. (I did not checked if it had changed in 10.3) This, at least, has changed in 10.3.
For this reason I use smart package manager. It's search function not as good as yast's but: - much easier to switch on and off repositories - one can choose by hand which repositories and when to refresh I agree ...
I started using smart exlusively in 10.2. I was hoping that in 10.3 I can switch back to YAST but unfortunately it is not polished enough. Same for me. Used yast on 10.3 until I got fed up ... back to smart, now.
Some more aspects: - yast uses an incredible amount of memory - about 256MB, it seems, with opensuse oss and non-oss ftp, and packman. On a virtual machine with 384MB RAM, it is ... noteable. - zypper tries to be a faster command line tool than the full yast ... unfortunately, it does not load the cache once when starting in shell mode, but reloads for ALL operations ... Just run "info wine" twice and see how it reloads the cache each time ... resulting in "top: VIRT 188m RES 151m" after some more calls of "info wine" in the same "zypper shell": VIRT 286m RES 247m not only needs a lot of time for re-loading the cache, it seems it does not free the memory used by the previous cache loads ... (talking about zypper-0.8.25-0.1) Without this, zypper might even be usable ... smart, on comparison, has VIRT 102m RES 64m *with* the cache loaded ...
Irrespectively of this openSUSE (all versions) is generally a very stable, reliable and easy to use linux system. ACK, again.
Yours, Sebastian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dňa Wednesday 31 October 2007 11:22:38 Istvan Gabor ste napísal:
Hello:
This might be a little bit offtopic. I do not want to offend anybody at openSUSE and don't want to be rude but I think openSUSE could not make a decent package manager since 9.3 or 10.0. Even in 10.3.
I'd like to point out that slowness of the package manager was one of the top complaints about pre-zypp era ;-)
These are the reasons why I don't use YAST package manager: - YAST package manager is extremely slow. - Furthermore why does it have to refresh all repositories if you want only remove or check something?
Remove - see the discussion in the archive. Basically, removing something might mean installing something else. Check - this is way to unspecific. I agree that 'zypper info' might be optimized a bit.
- You still can't change the order how repositories are processed (discussed elsewhere). - I am lost in the several options: online update, automatic online update, software repositories, community repositories, add on product etc. Who can follow this? And all of them after starting always refreshes and refreshes...
Everything related to packagemanagement in YaST always initializes libzypp and its repos. You have a point about mess in the software management section of the YaST control center.
- In the software manager takes forever to switch from one package group to the other. - In 10.2 the software manager always downloaded all the different package descriptor language files (xmls?) further slowing down refreshing. (I did not checked if it had changed in 10.3)
For this reason I use smart package manager. It's search function not as good as yast's but: - much easier to switch on and off repositories
What's wrong with 'zypper mr' ?
- one can choose by hand which repositories and when to refresh
Just turn off autorefresh for all your repos and call zypper refresh manually. Stano -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-10-31 at 00:48 -0500, David C. Rankin wrote:
I'll agree with Rajko. 10.2 was God awful slow. 10.3 is relatively fast compared to 10.2.
I don't know, I'm an openSUSE user since 10.3. But I can tell that Zypper is much faster than Yum which I've been using on Fedora.
If it get way to slow, then you can delete your local index files and
Local index files are in /var/cache/zypper.db?
let zypper rebuild them. This has been mentioned in several threads. The question is how slow is slow in your case 30-90 seconds?
Crap, here's what Yast says: "Accessing the Package Management Failed, Another process is accessing the package database", but Zypper works just fine, and it finds a file in 35 seconds, which is quite fast. I don't know how did I manage to lock Yast's Package Manament.
Or is it start software management, go get a cup of coffee, and just check back to see if it is done yet slow? If the latter, then you might consider wiping your indexes and letting them be rebuilt.
I think it's a bit faster when I removed zypper.db and ran zypper refresh. -- Igor Jagec
On Tue, 2007-10-30 at 19:15 -0500, Rajko M. wrote:
On Tuesday 30 October 2007 07:57:22 am Igor Jagec wrote:
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, maybe your question is for Packman mailing list. BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying. Is that 10.2 or 10.3.
10.3
Though, I can't say for date and time module in 10.2, as that is kept in sync with 'xntpd'.
Maybe that has something to do with GNOME, which I use, and the new gtk2 based Yast modules.
Apropos Packman. So far I recall they had a problem that is fixed, but /var/cashe/zypp/zypp.db might be in bad shape. Can you delete it and run YaST > Software Management or zypper refresh
I did that, and I got 10 MB smaller database. Seems to be a bit faster. -- Igor Jagec
On Wednesday 31 October 2007 05:24:47 am Igor Jagec wrote:
On Tue, 2007-10-30 at 19:15 -0500, Rajko M. wrote:
On Tuesday 30 October 2007 07:57:22 am Igor Jagec wrote:
Yeah, I noticed that too. Especially when I want to do some trivial stuffs with Yast2 (such as changing date and time), since Yast2 sometimes reads package database. Anyway, maybe your question is for Packman mailing list. BTW a question to Yast developers, why Yast2 does that? Sometimes that can be very annoying.
Is that 10.2 or 10.3.
10.3
Though, I can't say for date and time module in 10.2, as that is kept in sync with 'xntpd'.
Maybe that has something to do with GNOME, which I use, and the new gtk2 based Yast modules.
Apropos Packman. So far I recall they had a problem that is fixed, but /var/cashe/zypp/zypp.db might be in bad shape. Can you delete it and run YaST > Software Management or zypper refresh
I did that, and I got 10 MB smaller database. Seems to be a bit faster.
This is about things that will be implemented when time comes, but right now has be dome manually: http://en.opensuse.org/SDB:Speed_up_Package_Manager_Stack Additionally check what is marked to be refreshed in YaST > Software Repositories I have quite a few in list, but very few enabled and currently only update can be refreshed. Apropos lock mentioned in another post we had that problem discussed in thread ' Accessing package management failed' check /var/run/ directory for stale yast.pid or zypp.pid. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Aniruddha -
Bryen -
Cristian Rodriguez -
David C. Rankin -
Igor Jagec -
Istvan Gabor -
Rajko M. -
Sebastian Brandt -
Stanislav Visnovsky