[Bug 916587] New: zypper does not update package when used with -C
http://bugzilla.opensuse.org/show_bug.cgi?id=916587 Bug ID: 916587 Summary: zypper does not update package when used with -C Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@forge.provo.novell.com Reporter: tchatzimichos@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When I try to `zypper in -C pkg`, zypper only checks if the package is installed. I would expect it to update it as well, like when specifying the original name of it. zypper outputs below, let me know if you need further info from me please. # zypper lu ... v | home:tampakrap | dummy | 0.0.1-2.1 | 0.0.1-3.1 | noarch # zypper -v in -C dummy Verbosity: 1 Non-option program arguments: 'dummy' Initializing Target ... Loading repository data... Reading installed packages... Force resolution: No 'dummy' is already installed. Resolving package dependencies... Force resolution: No Nothing to do. # zypper -v in dummy Verbosity: 1 Non-option program arguments: 'dummy' Initializing Target ... Loading repository data... Reading installed packages... Force resolution: No Selecting 'dummy-0.0.1-3.1.noarch' from repository 'home:tampakrap' for installation. Resolving package dependencies... Force resolution: No The following package is going to be upgraded: dummy 0.0.1-2.1 -> 0.0.1-3.1 1 package to upgrade. Overall download size: 5.7 KiB. Already cached: 0 B No additional space will be used or freed after the operation. Continue? [y/n/? shows all options] (y): -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=916587 http://bugzilla.opensuse.org/show_bug.cgi?id=916587#c1 Benjamin Zeller <bzeller@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |bzeller@suse.com Resolution|--- |WONTFIX --- Comment #1 from Benjamin Zeller <bzeller@suse.com> --- Since capabilities will not necessarily always resolve to the same package, e.g. a different package provides the same cap with a higher version, we will keep the current behavior. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com