Mailinglist Archive: opensuse-bugs (7842 mails)

< Previous Next >
[Bug 420606] zypper up/lu ignores patch/pattern/product locks
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 1 Feb 2009 07:14:39 -0700 (MST)
  • Message-id: <20090201141439.0CA11CC7D4@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=420606

User jnelson-suse@xxxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=420606#c20


Jon Nelson <jnelson-suse@xxxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |jnelson-suse@xxxxxxxxxxx




--- Comment #20 from Jon Nelson <jnelson-suse@xxxxxxxxxxx> 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.

< Previous Next >
This Thread
  • No further messages