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 2008-09-15 08:53:29 MDT --- KDE3 for me. -- 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 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |tgoettlicher@novell.com Status|NEEDINFO |NEW Info Provider|rodney.baker@iinet.net.au | -- 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 rodney.baker@iinet.net.au added comment https://bugzilla.novell.com/show_bug.cgi?id=420606#c5 --- Comment #5 from Rodney Baker 2008-10-02 08:56:22 MDT --- Using zypp backend. BTW, in the last couple of days I have installed KDE 4.1.1 and then upgraded to 4.1.2 on 10.3 and I see the same behaviour as with 3.5.7 so could it be related to the backend plugin rather than the updater applet? -- 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#c7 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sh@novell.com, tgoettlicher@novell.com, | |dmacvicar@novell.com Status|NEW |NEEDINFO Info Provider| |rodneybaker@iinet.net.au --- Comment #7 from Ján Kupec 2008-10-06 06:42:15 MDT --- (In reply to comment #0 from Rodney Baker)

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 rodney.baker@iinet.net.au added comment https://bugzilla.novell.com/show_bug.cgi?id=420606#c9 Rodney Baker changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #9 from Rodney Baker 2008-11-10 19:41:22 MST --- As this is still a problem, perhaps I should try to explain myself in a clearer fashion: In Yast -> Software Management, there are several options for marking packages. The key ones in question are: Taboo - Never install Protected - Do Not Modify. If a package is marked with either of these flags, they should be left alone i.e. not installed or not modified. YOU (opensuseupdater-kde) does not appear to respect the settings of these flags. For example, openmotif22-libs was not installed on my machine as I use LessTiff (for compatibility with a specific special-purpose application). YOU insisted on showing openmotif22-libs as an available (and recommended) update *despite* it being marked as Taboo - Never Install. The only way to get rid of it from the list of available updates was to install it (which I could only do after the other application was updated to fix a display problem when using openmotif instead of LessTiff, but that's another story). Similarly, every time I install the latest update of Boost (1.33 -> 1.36) zypper gets uninstalled. I have now set boost 1.33 and boost-devel 1.33 to Protected - Do Not Modify in Yast -> Software Management, yet opensuseupdater-kde still shows boost and boost-devel 1.36 as available upgrades. 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?) when deciding what packages to show as available for updates or upgrades. -- 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 changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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 changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |libzypp OS/Version|openSUSE 11.0 |openSUSE 10.3 Product|openSUSE 10.3 |openSUSE 11.1 Version|Final |Beta 3 -- 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#c13 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|rodney.baker@iinet.net.au | --- Comment #13 from Ján Kupec 2008-11-11 06:41:12 MST --- (In reply to comment #12 from Rodney Baker)

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 User rodney.baker@iinet.net.au added comment https://bugzilla.novell.com/show_bug.cgi?id=420606#c14 --- Comment #14 from Rodney Baker 2008-11-17 14:16:48 MST --- I have recently updated my desktop machine to openSuse 11.0/KDE 4.1.3 and can confirm that the same behaviour happens with the kde updater applet as previously described. I set boost 1.34 and boost-devel 1.34 to "Protected - Do Not Modify" in Yast -> Software Management, yet the updater applet still wants me to install version 1.36 (it shows it in the list of available upgrades). Since Yast now stores this status in /etc/zypp.locks, it would be a lot nicer if opensuseupdater-kde checked zypp.locks and excluded packages marked as "Protected" from the list of available upgrades. -- 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 rodney.baker@iinet.net.au added comment https://bugzilla.novell.com/show_bug.cgi?id=420606#c16 --- Comment #16 from Rodney Baker 2008-11-18 04:11:44 MST --- (In reply to comment #15 from Duncan Mac-Vicar)

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 rodney.baker@iinet.net.au added comment https://bugzilla.novell.com/show_bug.cgi?id=420606#c18 --- Comment #18 from Rodney Baker 2008-12-05 04:34:16 MST --- (In reply to comment #17 from Ján Kupec)

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 jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=420606#c20 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jnelson-suse@jamponi.net --- Comment #20 from Jon Nelson 2009-02-01 07:14:36 MST --- There seems to be a terminology problem here. I'm running openSUSE 11.1 and I think I have the same problem. 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. Taboo - Do Not Install should mean just that - *don't* install it. I really dislike the idea of a "this session only" package lock. Perhaps the language should be changed or something but I got really frustrated because the language *says* it means one thing but as soon as I finish installing/upgrading packages, and go back and see what new updates are available (more on that in a moment), the package I marked as protected is upgraded! I don't want that. This is using the QT YaST2 GUI on openSUSE 11.1 I would like the hplip* packages to be *locked* - ie, keep it this way. If a new version is available perhaps let me know but do NOT automatically select it for upgrade. The other bug I hit (and I'll be filing soon) is this: if a package is upgraded or chosen for install, and it brings in some dependencies, even though I choose "All in this list, upgrade to newest version..." it does not do that for the automatically chosen dependencies. I have to make a *second* run to get those deps. -- 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#c22 --- Comment #22 from Ján Kupec 2009-03-25 04:07:14 MST --- (In reply to comment #20)

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.