Hi, is this a known "feature" or a bug: When you use Yast2 Software Management (beta9) to delete a rpm, it is no longer written in the window "deleting foobar.rpm". Instead nothing is printed and you just sit there and wait and think nothing is going on. This "deleting package" message was there at least in 9.2 and I think it got lost with the change to libzypp. So, is this worth a bugzilla entry? Regards, Andreas -- Andreas Vetter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Vetter wrote:
is this a known "feature" or a bug: When you use Yast2 Software Management (beta9) to delete a rpm, it is no longer written in the window "deleting foobar.rpm". Instead nothing is printed and you just sit there and wait and think nothing is going on. This "deleting package" message was there at least in 9.2 and I think it got lost with the change to libzypp.
So, is this worth a bugzilla entry?
That's definitely worth a bug to me. It's pretty annoying, given how you
describe it (and we'll end up again with this being asked 100 times
every day on IRC).
Whether it's a blocker or not has to be decided by AJ.
Always file a bug: if it's not in Bugzilla, then it's not there ;)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
2006/4/11, Pascal Bleser
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andreas Vetter wrote:
is this a known "feature" or a bug: When you use Yast2 Software Management (beta9) to delete a rpm, it is no longer written in the window "deleting foobar.rpm". Instead nothing is printed and you just sit there and wait and think nothing is going on. This "deleting package" message was there at least in 9.2 and I think it got lost with the change to libzypp.
So, is this worth a bugzilla entry?
That's definitely worth a bug to me. It's pretty annoying, given how you describe it (and we'll end up again with this being asked 100 times every day on IRC).
Whether it's a blocker or not has to be decided by AJ. Always file a bug: if it's not in Bugzilla, then it's not there ;)
With "smart upgrade", smart after installing the packages deletes it, but if they are older packages from incompletes upgrades (for example when the packages changes in the server during the upgrade), smart do'nt delete those older packages. The other detail, smart hangs if I do'nt kill the zmd daemon.
On Tue, 11 Apr 2006, Juan Erbes wrote: [...]
The other detail, smart hangs if I do'nt kill the zmd daemon.
This is a known "feature", as zmd tries to read the rpmdb as soon as it changes, which is indeed happening, when you install/update packages. Unfortunately there is no other fix than disabeling zmd at the moment. Regards Christoph
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christoph Thiel wrote:
On Tue, 11 Apr 2006, Juan Erbes wrote: [...]
The other detail, smart hangs if I do'nt kill the zmd daemon. This is a known "feature", as zmd tries to read the rpmdb as soon as it changes, which is indeed happening, when you install/update packages. Unfortunately there is no other fix than disabling zmd at the moment.
Although it rather seems that zmd is locking the RPM database
permanently, right ?
If it's using inotify (or some other similar mechanism, kinda getting
lost with this API in the kernel as it's changing with almost every
release) on the Berkeley hash files of the RPM database to get notified
instantly of changes, why does it have to lock the database ?
If would be sufficient to
- - lock
- - read
- - unlock
- - get back to inotify
Or am I missing something ?
If that was the case, smart wouldn't hang - or rather, smart would hang
until the RPM database is unlocked, then lock it, do its stuff, and
unlock the database.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Tue, Apr 11, 2006 at 03:04:43PM +0200, Pascal Bleser wrote:
Although it rather seems that zmd is locking the RPM database permanently, right ?
It does not on my systems. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
On 11 Apr 2006 at 15:07, Robert Schiele wrote:
On Tue, Apr 11, 2006 at 03:04:43PM +0200, Pascal Bleser wrote:
Although it rather seems that zmd is locking the RPM database permanently, right ?
It does not on my systems.
Maybe cat /proc/locks might help; or is it mandatory locking? Regards, Ulrich
On Tue, 11 Apr 2006, Pascal Bleser wrote:
The other detail, smart hangs if I do'nt kill the zmd daemon. This is a known "feature", as zmd tries to read the rpmdb as soon as it changes, which is indeed happening, when you install/update packages. Unfortunately there is no other fix than disabling zmd at the moment.
Although it rather seems that zmd is locking the RPM database permanently, right ?
No, it doesn't.
If it's using inotify (or some other similar mechanism, kinda getting lost with this API in the kernel as it's changing with almost every release) on the Berkeley hash files of the RPM database to get notified instantly of changes, why does it have to lock the database ?
If would be sufficient to - - lock - - read - - unlock - - get back to inotify
Or am I missing something ?
If that was the case, smart wouldn't hang - or rather, smart would hang until the RPM database is unlocked, then lock it, do its stuff, and unlock the database.
That's what actually happening, smart hangs while zmd is reading the database, which should be working just fine in theory. But it doesn't :( So, the way to go is just to disable zmd for now. Regards Christoph
On Tue, 11 Apr 2006, Pascal Bleser wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andreas Vetter wrote:
is this a known "feature" or a bug: When you use Yast2 Software Management (beta9) to delete a rpm, it is no longer written in the window "deleting foobar.rpm". Instead nothing is printed and you just sit there and wait and think nothing is going on. This "deleting package" message was there at least in 9.2 and I think it got lost with the change to libzypp.
So, is this worth a bugzilla entry?
That's definitely worth a bug to me. It's pretty annoying, given how you describe it (and we'll end up again with this being asked 100 times every day on IRC).
Whether it's a blocker or not has to be decided by AJ. Always file a bug: if it's not in Bugzilla, then it's not there ;)
AJ is on CC, too. https://bugzilla.novell.com/show_bug.cgi?id=165197 Summary: yast2: remove packages is silent Product: SUSE Linux 10.1 Version: Beta 9 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: asvetter@cip.physik.uni-wuerzburg.de QAContact: visnov@suse.de Open Yast2 / Software Management delete a package, click accept. In the following window no hint is given, that a package is removed. In former SL versions it was printing something like "removing package foobar-version.rpm". When deleting an amount of packages you sit and wait and don't know what's going on. -- Andreas Vetter Tel: +49 (0)931 888-5890 Fakultaet fuer Physik und Astronomie Fax: +49 (0)931 888-5508 Universitaet Wuerzburg
participants (6)
-
Andreas Vetter -
Christoph Thiel -
Juan Erbes -
Pascal Bleser -
Robert Schiele -
Ulrich Windl