[Bug 625426] New: packages from OSS repository are bypassed on upgrade
http://bugzilla.novell.com/show_bug.cgi?id=625426 http://bugzilla.novell.com/show_bug.cgi?id=625426#c0 Summary: packages from OSS repository are bypassed on upgrade Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: antoine.mechelynck@belgacom.net QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:2.0b2pre) Gecko/20100701 Lightning/1.1a1pre SeaMonkey/2.1a3pre - I installed the Mercurial package while still on openSUSE 11.2; at the time, its version was 1.3.1 - When upgrading from 11.2 to 11.3 by means of a downloaded DVD image, the 11.3 OSS repository was enabled by the upgrade, but its version (1.5) of the Mercurial package was not installed. - Since then, the "Online Update" function of YaST never told me that a nawer version of Mercurial was available: I had to complain about a bug on the Mercurial mailing list to be told that, actually, the Mercurial version shipped with openSUSE 11.3 was Mercurial 1.5 (it never came to my mind that YaST would not propose a newer version if one was available). Reproducible: Always Steps to Reproduce: See above Actual Results: YaST never told me a Mercurial upgrade was available on the OSS repository. Expected Results: YaST should, as a minimum, have told me (either during the 11.2 => 11.3 upgrade or when I invoked "Online Update" thereafter) that an upgrade was available. Additional info: I don't know (how _could_ I know) which other OSS and/or non-OSS packages, if any, are still ready for an upgrade which YaST won't tell me is available. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=625426
http://bugzilla.novell.com/show_bug.cgi?id=625426#c
yang xiaoyu
http://bugzilla.novell.com/show_bug.cgi?id=625426
http://bugzilla.novell.com/show_bug.cgi?id=625426#c1
Jiří Suchomel
http://bugzilla.novell.com/show_bug.cgi?id=625426
http://bugzilla.novell.com/show_bug.cgi?id=625426#c2
Tony Mechelynck
http://bugzilla.novell.com/show_bug.cgi?id=625426
http://bugzilla.novell.com/show_bug.cgi?id=625426#c3
Michael Andres
http://bugzilla.novell.com/show_bug.cgi?id=625426
http://bugzilla.novell.com/show_bug.cgi?id=625426#c4
--- Comment #4 from Tony Mechelynck
http://bugzilla.novell.com/show_bug.cgi?id=625426
http://bugzilla.novell.com/show_bug.cgi?id=625426#c5
Michael Andres
http://bugzilla.novell.com/show_bug.cgi?id=625426
http://bugzilla.novell.com/show_bug.cgi?id=625426#c6
--- Comment #6 from Tony Mechelynck
@Thomas: 'update if newer version is available' could be easily improved to match 'zypper up'. With this being done, Tony could complete the update without leaving YaST ;)
In particular, the first bootup of the newly version-upgraded system (which doesn't use the same inittab or whatever than all later bootups, but, unlike the part of the update which is run from the DVD system, has a working Internet connection) might propose (from a YaST window maybe, opened at "Installation Summary" to allow user tweaks, and with the usual [ Cancel ] [ Accept ] at bottom) to update all packages for which a new version is available. This would allow upgrading from other repositories than the main DVD disk image, and it would make this "update packages" function of YaST more discoverable. BTW, that "zypper up" job launched shortly after comment #4 is still running: package 1094 of 2016, kernel-desktop-debuginfo. I'll leave it running later today when I go to the snackbar, it seems to work quite well unattended. But YaST+Qt is better-looking. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c9
Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c10
Jiří Suchomel
@Thomas: 'update if newer version is available' could be easily improved to match 'zypper up'. With this being done, Tony could complete the update without leaving YaST ;)
I guess here is the place for improvement/change. It is not in yast2-online-update, but in software manager widget. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c11
Thomas Göttlicher
@Thomas: 'update if newer version is available' could be easily improved to match 'zypper up'. Could you please explain how YQPackageSelector::globalUpdatePkg( bool force ) and YQPkgObjList::setAllItemStatus( S_Update) needs to be improved?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c12
--- Comment #12 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c13
--- Comment #13 from Michael Andres
Could you please explain how YQPackageSelector::globalUpdatePkg( bool force ) and YQPkgObjList::setAllItemStatus( S_Update) needs to be improved?
- In YQPkgObjListItem::init I see _installedIsNewer/_candidateIsNewer set based on a simple version compare: ( candidate->edition() < installed->edition() ) - In YQPkgList::globalSetPkgStatus I see in 'case S_Update:' 'doChange = ( installed->edition() < candidate->edition() );' - In YQPkgObjList::setAllItemStatus I see 'if ( newStatus == S_Update ) if ( item->candidateIsNewer()': 'item->setStatus( newStatus ). So the UI simply looks at the version and then selects the package. This is bad, because the highest version is not necessarily the best choice, especially if the same package is provided by multiple repos/vendors. The flaw in the current approach is that the UI should not look for a higher version, but check whether there is an 'updateCandidateObj' for this selectable. The Selectable will return an item which is likely to be chosen by the solver as well (at least an item that fits all active solver policies), or NULL if no available package fits the current solver policies. (Keep in mind that you need to call setCandidate, if the updateCandidateObj and candidateObj are different) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c
Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c
Thomas Göttlicher
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c14
Thomas Göttlicher
https://bugzilla.novell.com/show_bug.cgi?id=625426
https://bugzilla.novell.com/show_bug.cgi?id=625426#c
Martin Vidner
participants (1)
-
bugzilla_noreply@novell.com