Bug 154720

Summary:	Update installation lies about deleted packages
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Stanislav Brabec <sbrabec>
Component:	YaST2	Assignee:	Ladislav Slezák <lslezak>
Status:	VERIFIED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Critical
Priority:	P5 - None	CC:	aj, matz, suse-beta
Version:	Beta 8
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Stanislav Brabec 2006-03-02 15:10:42 UTC

YaST Update summary lies about number of packages to delete. It reports 0 packages to delete, even if it is going to delete packages.

Details:

My old package lists contain:
avahi-compat-mDNSResponder which conflicts with mDNSResponder (in GNOME selection)
gimp-unstable which conflicts with gimp (in GNOME selection)

I have started installation on CD and selected to update from previous version (updated beta3) and use GNOME selection. I decided to not delete not contained packages.

Summary shows 0 packages to delete.

Try1:

I went to manually change packages.
I see that avahi-compat-mDNSResponder and gimp-unstable are targetted to be deleted and replaced by mDNSResponder nad gimp. I selected not to install gimp and mDNSResponder and keep avahi-compat-mDNSResponder and gimp-unstable.

Actual result: Summary shows 0 packages to delete. Going to package selection again, it shows again, that avahi-compat-mDNSResponder and gimp-unstable will be deleted and mDNSResponder nad gimp will be installed.

Expected result: Report 2 packages to delete. Keep my decision.

Try 2:

I went to manually change packages.
I see that avahi-compat-mDNSResponder and gimp-unstable are targetted to be deleted and replaced by mDNSResponder nad gimp. I selected to keep avahi-compat-mDNSResponder and gimp-unstable.

Actual result: Summary shows 0 packages to delete. Going to package selection again, it shows again, that avahi-compat-mDNSResponder and gimp-unstable will be deleted.

Expected result: Report 2 packages to delete. After change in dialog, report conflict and ask for fixing the conflict in the standard way.

Comment 1 Martin Lasarsch 2006-03-02 16:49:36 UTC

y2log?

Comment 3 Klaus Kämpf 2006-03-03 09:48:48 UTC

Upgrade statistics show
2006-03-02 13:55:58 <1> linux(5185) [solver] ResolverUpgrade.cc(doUpgrade):630 totalToInstall       6
2006-03-02 13:55:58 <1> linux(5185) [solver] ResolverUpgrade.cc(doUpgrade):630 totalToDelete        77
2006-03-02 13:55:58 <1> linux(5185) [solver] ResolverUpgrade.cc(doUpgrade):630 totalToKeep          1321
2006-03-02 13:55:58 <1> linux(5185) [solver] ResolverUpgrade.cc(doUpgrade):630 --------------------------
2006-03-02 13:55:58 <1> linux(5185) [solver] ResolverUpgrade.cc(doUpgrade):630 sum                  1404

-> pkg-bindings problem ?!

Comment 4 Stanislav Visnovsky 2006-03-03 10:02:10 UTC

Why we don't use the numbers from resolver, but count the packages
on our own?

Comment 5 Stanislav Visnovsky 2006-03-06 14:48:38 UTC

*** Bug 155284 has been marked as a duplicate of this bug. ***

Comment 6 Jiri Srain 2006-03-06 18:04:11 UTC

Klaus, is there any way to get these statistics without changign state of any resolvable? I found them as output of the solver run, but I need to get them updated after user entered individual package selection...

Comment 7 Michael Matz 2006-03-09 16:24:36 UTC

I also have this problem, but it also shows zero packages to update (I
chose to update), where in the single-sw selection it clearly shows many
packages as to-be-deleted and to-be-updated.  If you need logs for this
too, I will attach them after the update finished, but I guess you already
know the reason.

Comment 8 Klaus Kämpf 2006-03-13 07:05:44 UTC

comment #6: Sure, its the 'zypp::UpgradeStatistics' set via 'zypp_ptr->resolver()->doUpgrade(stats);'

See yast2-pkg-bindings, Package.cc

(btw, this struct is identical to the one returned from yast2-packagemanager)

Comment 9 Stanislav Visnovsky 2006-03-15 14:49:27 UTC

*** Bug 152445 has been marked as a duplicate of this bug. ***

Comment 10 Jiri Srain 2006-03-16 15:44:15 UTC

*** Bug 156382 has been marked as a duplicate of this bug. ***

Comment 11 Christian Boltz 2006-03-18 14:58:36 UTC

this happened again when updating from beta6 to beta8.

"packages to update: 3, packages to install: 1219, packages to delete: 0"

The strange thing: The problem appeared after choosing not to delete unmaintained packages in the "update options".
Before that, the numbers and the disk space calculation was correct IIRC.

You can find the y2logs and the RPM database dump in bug 159340.

Maybe a related bug: even if the proposal reported 3.8 GB missing diskspace, I could continue the installation without a dialog warning about the (not really) missing diskspace.

Comment 12 Stanislav Visnovsky 2006-03-21 14:45:07 UTC

Lado, please, take a look.

Comment 13 Ladislav Slezák 2006-03-22 16:08:55 UTC

*** Bug 156638 has been marked as a duplicate of this bug. ***

Comment 14 Ladislav Slezák 2006-03-23 12:46:20 UTC

Fixed in yast2-update-2.13.10

Comment 15 Christian Boltz 2007-03-25 22:53:49 UTC

even if I'm late: VERIFIED in 10.2 - it can count again :-)