[Bug 420606] New: OpenSuse Updater does not honour package protection status set in Yast package management
https://bugzilla.novell.com/show_bug.cgi?id=420606 Summary: OpenSuse Updater does not honour package protection status set in Yast package management Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rodney.baker@iinet.net.au QAContact: jsrain@novell.com Found By: --- The openSuse updater applet insists on wanting to install updates to packages that have been marked as protected or Do Not Install in Yast's package management utility. For example, I have openmotif22-libs (the 64bit package) marked as "Do Not Install", yet YOU still shows it as being available. I also have x11-video-nvidiaG01 and nvidia-gfxG01-kmp-default marked as protected, but updates are still shown for them also. Accordingly, the openSuse updater icon always shows that updates are available and waiting to be installed. It appears that either Yast does not correctly set the protected status or openSuse updater ignores the value as set in Yast. -- 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=420606
User chrubis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c1
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=420606
User mrmazda@ij.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c2
--- Comment #2 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=420606
User rodney.baker@iinet.net.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c3
--- Comment #3 from Rodney Baker
https://bugzilla.novell.com/show_bug.cgi?id=420606
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=420606
User tgoettlicher@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c4
Thomas Göttlicher
https://bugzilla.novell.com/show_bug.cgi?id=420606
User rodney.baker@iinet.net.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c5
--- Comment #5 from Rodney Baker
https://bugzilla.novell.com/show_bug.cgi?id=420606
User tgoettlicher@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c6
Thomas Göttlicher
https://bugzilla.novell.com/show_bug.cgi?id=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c7
Ján Kupec
It appears that either Yast does not correctly set the protected status or openSuse updater ignores the value as set in Yast.
Hi! Neither of these, it seems. "Do Not Install" does not mean locking or 'protecting' the package. "Taboo" is meant for that IIRC. "Do Not Install" just means that you don't want this package to be installed in this session/run. It also means that the package will not be auto-selected for installation due to Recommends dependencies in the next session/run, but it still can be selected for installation by Requires (hard) dependencies, or by explicit install/update request. So, was it just a misunderstanding from your side, or is some improvement in documentation or help texts or tooltips needed? -- 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=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c8
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=420606
User rodney.baker@iinet.net.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c9
Rodney Baker
https://bugzilla.novell.com/show_bug.cgi?id=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c10
Ján Kupec
As this is still a problem, perhaps I should try to explain myself in a clearer fashion:
Thanx, it is clear now. However what do you mean with 'now'? Are you still on openSUSE 10.3, or is the bug also in the latest 11.1? If it is 10.3 this would be a zypper bug, but we won't fix that. If it is 11.1, we'd like to fix it, and if you can reproduce it right now, it would help if you could attach a solver test case (the available updates are computed by dependency resolver for packages). See http://en.opensuse.org/Zypper/Troubleshooting#Solver_Test_Case. I'll try to reproduce it on 11.1 myself as well.
YOU (opensuseupdater-kde)
YOU and opensuseupdater-kde are not the same. YOU is a yast module, the updater has nothing to do with yast.
So it appears that it is still ignoring at least these two package status flags (which I assume are stored in the rpm package database?)
No, on 10.3 they're not stored at all. Since 11.0 they're stored in /etc/zypp/locks. -- 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=420606
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c11
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=420606
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=420606
User rodney.baker@iinet.net.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c12
--- Comment #12 from Rodney Baker
https://bugzilla.novell.com/show_bug.cgi?id=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c13
Ján Kupec
I guess I should also raise another bug re boost updates uninstalling zypper/libzypp, although again this may be just a 10.3 issue.
Zypper requires boost-devel >= 1.33.1, libzypp just boost-devel, so upgrade to 1.36 should work. But yes, it would be nice to check that on a newer system, since such bug would not be serious enough to fix it for 10.3, only for the upcoming 11.1. -- 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=420606
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=420606
User rodney.baker@iinet.net.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c14
--- Comment #14 from Rodney Baker
https://bugzilla.novell.com/show_bug.cgi?id=420606
User dmacvicar@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c15
Duncan Mac-Vicar
https://bugzilla.novell.com/show_bug.cgi?id=420606
User rodney.baker@iinet.net.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c16
--- Comment #16 from Rodney Baker
I Don't understand. This bug is marked for 11.1 , and the reporter "just" upgraded to 11.0 ?
Yes, I have just upgraded to 11.0 from 10.3 (where I originally noticed the behaviour and reported the issue). I had not noticed the update to the bug summary or the change in product from 10.3 to 11.1, hence the comment confirming that since upgrading to 11.0 the behaviour was the same. I'll read things more carefully next time... -- 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=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c17
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=420606
User rodney.baker@iinet.net.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c18
--- Comment #18 from Rodney Baker
Rodney, we won't fix this bug for older openSUSEs. Only for 11.1 or even 11.2. As i said in c#11, what you describe works in 11.1.
That is fair enough. I don't really have a problem with that.
I'm keeping this bug to do something about zypper ignoring locked non-packages (patterns, etc).
Also, please remove the NEEDINFO status from the bug when you provide the requested info.
OK, will do. I understood that the person who intially requested the info would do that if the response provided what was required. Now that I know that's not the case, I'll remember for future reports.
Some notes regarding this bug: * 'update of a pattern' needs to be defined first. If we can't define it, we will not allow 'zypper lu/up -t pattern'. If we can, we need to implement it taking the locked patterns into account.
What is a pattern? A specific collection of packages e.g. KDE4, KDE3? Is it possible to lock a pattern, or only specific packages within a pattern? If updating a pattern and specific packages within that pattern are locked, those packages (and any that depend on them) should be left untouched. I've never tried to lock an entire "pattern" so I'm not sure if this is (or should be) possible or not.
* 'zypper lu/up -t product/patch' needs fixing to take locked products/patches into account. Locking a product/patch should make it appear as 'locked' in 'lu' and ignored in 'up' (or 'patch' command). * the 'locked patch' should be displayed as 'taboo' in YaST, and ignored in KDE updater.
* Also, if a patch is set to "Taboo" in YaST, then that status should persist until it is explicitly removed i.e. it should be stored in /etc/zypp.locks, and * If a package is set to "protected - do not modify", then all patches/package updates that relate to that package should be treated as "Taboo" i.e. a protected package should never be modified (i.e. by YaST or KDE updater) unless the protected status is explicitly removed (which I think probably says the same thing as your last 2 points, if I understand them correctly). -- 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=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c19
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=420606
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c20
Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=420606
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c21
--- Comment #21 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c22
--- Comment #22 from Ján Kupec
When I mark a package as "Protected - Do Not Modify" I want it to mean just that - do not upgrade, downgrade, or remove without asking me first.
We agree on this :O)
Taboo - Do Not Install should mean just that - *don't* install it.
This one, too. BTW, it says "Taboo - Never Install".
I really dislike the idea of a "this session only" package lock. Perhaps the
AFAICT, these are both permanent, not "this session only". If you see something else, it is a bug, but please open a separate report for that particular case and attach a solver test case (immediately after you see the problem, click Extras -> Generate Dependency Resolver Testcase) and yast logs to it.
the package I marked as protected is upgraded! I don't want that.
Neither do we. The bug report would help. -- 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=420606
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c23
--- Comment #23 from Ján Kupec
Will any action be taken on this bug or should it be marked as WONTFIX?
Note that this bug is in fact about zypper (the updater applet with zypp backend), not YaST. Yes, it will be dealt with somehow, just a bit later.
It seems to me that my last comment (the part about Protected and Taboo) is not unreasonable.
see my comment #22. -- 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.
participants (1)
-
bugzilla_noreply@novell.com