https://bugzilla.novell.com/show_bug.cgi?id=731090
https://bugzilla.novell.com/show_bug.cgi?id=731090#c3
Michael Andres changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|ma@suse.com |
--- Comment #3 from Michael Andres 2011-11-18 10:01:34 CET ---
By now I can't verify this. The only difference seems to be the url schema (dir
vs. file). But both work for me as they should:
$ zypper ar --type Plaindir /Local/Repo/ extra
...URI: dir:///Local/Repo
$ zypper ar --type Plaindir file:///Local/Repo/ extra2
...URI: file:/Local/Repo/
$ zypper ref extra extra2
Retrieving repository 'extra' metadata [done]
Building repository 'extra' cache [done]
Retrieving repository 'extra2' metadata [done]
Building repository 'extra2' cache [done]
Specified repositories have been refreshed.
$ zypper se -s -r extra -r extra2
| Name | Type | Version | Arch | Repository
--+---------------------+------------+----------------+--------+-----------
v | WindowMaker | package | 0.94.0.crm-208 | x86_64 | extra
v | WindowMaker | package | 0.94.0.crm-208 | x86_64 | extra2
...
- And also downloading the packages.
- And also the same with 'zypper --root /tmp/T' incl. download
- And also the call from comment#1, just whithout the --config.
So maybe your config is broken?
--
Apropos config! Maybe you hit the same bug in zyppers augeas lense I did a few
days ago:
## Valid values: remove, install, update, patch, verify
## Default value: remove
# forceResolutionCommands = remove
forceResolutionCommands = install
The above does not work. Zypper treats it as multiple definition of
'forceResolutionCommands' (one commented and one uncommented), and falls back
to it's default (and not to the uncommented one). You have to use:
## Valid values: remove, install, update, patch, verify
## Default value: remove
forceResolutionCommands = install
I fixed this together with bnc#715057.
--
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.