I like that "removing" lock merely ignores the lock when proceeding to install/upgrade/remove a package locked via a wildcard. What bothers me is the prompt only offers to remove, not to disregard, then proceeds to disregard upon selecting "remove", as when doing as follows: # zypper ll | grep kern 45 | kernel-de* | package | (any) 46 | kernel-p* | package | (any) # zypper -v in kernel-default ... Selecting 'kernel-default-4.6.1-1.1.i586' from repository 'OSS' for installation. Warning: 'kernel-default' is locked. Use 'zypper removelock kernel-default' to unlock it. Resolving package dependencies... Force resolution: No Problem: conflicting requests Solution 1: remove lock to allow installation of kernel-default-4.6.1-1.1.i586[OSS] Solution 2: do not ask to install a solvable providing kernel-default.i586 = 4.6.1-1.1 Choose from above solutions by number or cancel [1/2/c] (c): 1 Applying solution 1 ... (1/1) Installing: kernel-default-4.6.1-1.1.i586 ..............................................................................[done] ... # zypper ll | grep kern 45 | kernel-de* | package | (any) 46 | kernel-p* | package | (any) # Am I the only one bothered by what I see here as an apparent inconsistency when a wildcard lock is applicable? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org