How do I make Packman apps always come from Packman repo? I know how to use ‘Switch System Packages’ in Yast2. I also know how to:
# zypper dup -r Packman
Yet for weeks I keep getting this **** about k3b:
# zypper -v patch
Verbosity: 1
Initializing Target
Checking whether to refresh metadata for KDE:/Distro:/Stable/openSUSE_11.3
Checking whether to refresh metadata for KDE:/Extra/openSUSE_11.3
Checking whether to refresh metadata for KDE:/UpdatedApps/openSUSE_11.3
Checking whether to refresh metadata for Libdvdcss-repository
Checking whether to refresh metadata for Packman
Checking whether to refresh metadata for Updates for openSUSE 11.3 11.3-1.82
Checking whether to refresh metadata for NVIDIA Repository
Checking whether to refresh metadata for openSUSE-11.3-Non-Oss
Checking whether to refresh metadata for openSUSE-11.3-Oss
Loading repository data...
Reading installed packages...
Force resolution: No
Selecting 'k3b-2785.noarch' from repository 'Updates for openSUSE 11.3 11.3-1.82' for installation.
Resolving package dependencies...
Force resolution: No
Problem: patch:k3b-2785.noarch conflicts with k3b-lang.noarch < 2.0.0-1.1.1 provided by k3b-lang-2.0.0-1.pm.2.14.noarch
Solution 1: Following actions will be done:
install k3b-lang-2.0.0-34.1.noarch (with vendor change)
http://packman.links2linux.de --> obs://build.opensuse.org/KDE
install k3b-2.0.0-34.1.x86_64 (with vendor change)
http://packman.links2linux.de --> obs://build.opensuse.org/KDE
Solution 2: do not install patch:k3b-2785.noarch
Choose from above solutions by number or cancel [1/2/c] (c):
OR is ‘zypper -v patch’ a deprecated command? My point is after repeatedly asking my system to always prefer Packman repo packages when I run ‘zypper -v patch’ it wants to install a patch on a version of k3b in OBS which I don’t even have installed. How to stop the madness?
As far as I know your choices are to manually select the update and resolve the conflict yourself OR Disable the offending repository OR place a Write Protection on the Application(s) to prevent any updates. I have not found setting a priority keeps this from going on though I do place a High Priority on Packman (lower number) so when I look at the versions Tab it will be at the top of the list. Also, while there are reasons to use Packman for using restricted file formats like MP3’s, I am not sure there is an issue in using the latest version of K3b from another repository. For instance I have installed KDE 4.5 and have updated to K3b from that repository, with no conflicts or operational issues.
The problem is in the Packman package (even if not its fault). Ask them to increase the release number of its package to something >= 1.1.1… or wait for k3b 2.0.1, and this will be automatically fixed.
Isn’t using the priority for the repository the answer here? The reason I offer that is as a result of Red Dwarf?'s mmcheck script. My thinking is that if the mmcheck has detected a problem, I would like to have the script auto-update it for me, provided I’m able to let it know what version and bit size of os I’m running. That way, I don’t have to scour the Internet everytime I wind up resetting the computer state.
Isn’t using the priority for the repository the answer here? The reason I offer that is as a result of Red Dwarf?'s mmcheck script. My thinking is that if the mmcheck has detected a problem, I would like to have the script auto-update it for me, provided I’m able to let it know what version and bit size of os I’m running. That way, I don’t have to scour the Internet everytime I wind up resetting the computer state.
Any ideas on how best to do that?
mmcheck, which I wrote based on the very fine examples originally posted by Red Dwark, can allow YOU to detect that you have problems, but the resolutions are not so simple. Not even the update applet can fix such problems right now, because the answer or resolution is based on why you have conflicting files available from multiple repositories. You must answer that problem yourself. mmcheck was written to help find those problems so you know to fix them. Often the issue comes up because we think the more repositories we add, the better off we are. But these are maintained by different people and different priorities and when you mix them up, only you can really fix the resulting file mixture mess, if you know what to do. I do agree that setting a priority is one way to deal with the mess, but there are no guaranties that this one act will keep you out of trouble.
