http://www.slhess.com/pictures/52111pman.jpg
Why is this going on? I use this machine to watch media like heck I would remove these files and break 50%+ of my functionality. There is a whole pile of “red” entries in this repo and it’s all multimedia stuff mostly.
You do not get the point of those red entries. It simply means that those packages are offered in newer versions. What makes you think they are going to be removed?
When the entries are blue it means there are newer versions from my experience. Red means something is amiss and you will get a pop waring you that some conditions will be unsatisfied if you make a selection of a red entry because it will remove the package and something else depends on it.
Hi
That would indicate a wayward repository. Not pointing at unixheads?
On 2011-05-22 00:36, FlameBait wrote:
>
> [image: http://www.slhess.com/pictures/52111pman.jpg]
> Why is this going on? I use this machine to watch media like heck I
> would remove these files and break 50%+ of my functionality. There is a
> whole pile of “red” entries in this repo and it’s all multimedia stuff
> mostly.
Red does not mean “remove”.
Nothing is going to be removed on the photo you posted.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
On 2011-05-22 01:36, FlameBait wrote:
>
> When the entries are blue it means there are newer versions from my
> experience. Red means something is amiss and you will get a pop waring
> you that some conditions will be unsatisfied if you make a selection of
> a red entry because it will remove the package and something else
> depends on it.
Red means that the package installed is not available in the repos. Check
the version tab to see what is available for update and from which repo. I
bet that the installed version is from a different repo (not packman).
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
http://www.slhess.com/pictures/52111pman2.jpg
Looks like it will remove it and cause all kinds of problems to me.
repo is ftp.uni-erlangen.de
server is /pub/mirrors/packman/suse/11.3/
All these files are from packman. they even have pm in ehe filename.
Other files in this repo were blue and I updated them.
Sorry, I obviously misunderstand the colour-code myself, which is because I never use YaST for package management, only zypper - I didn’t wanted to confuse anyone.
Things are uneasy to judge by some barely legible screenshots, since they do not provide all the information needed. Please switch to the command line and post the output of
zypper lr -d
zypper se -si | grep "(System" | grep .pm.
zypper -v up
The last command would trigger an update, however, when asked whether to actually install these updates, you can say “no”, I’d still be interested in the exact output.
Please post them in code tags.
On 2011-05-22 02:36, FlameBait wrote:
> All these files are from packman. they even have pm in ehe filename.
No, the one in parenthesis yes, the installed one has no ‘pm’
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
FlameBait wrote:
>
> [image: http://www.slhess.com/pictures/52111pman2.jpg]
> Looks like it will remove it and cause all kinds of problems to me.
>
>
No that is completely correct to use the first joice it gives you, it now
removes inconsistencies and if you read exactly what it tells you is that it
replaces an existing library with another version and does not remove
anything.
–
PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.3 | GeForce
9600 GT | 4GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
ION | 3GB Ram
On 2011-05-22 02:36, FlameBait wrote:
>
> [image: http://www.slhess.com/pictures/52111pman2.jpg]
> Looks like it will remove it and cause all kinds of problems to me.
As you do not show the “versions” tab, I can not judge.
Trying to upgrade causes conflicts. You have to be clever and solve them.
It is your job, you are the administrator >:-)
I would choose “break ffmpeg” and then look at libavdevice and check what
you can do there.
And it is possible you can not solve it, because there are reported
problems with packman.
And no, YaST is not going to uninstall anything. /You/ are, when you click
the inappropriate option. 
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
The red color means the installed package has a higher version than the package available in the repository. Just look at the list and user “zypper vcmp” when in doubt to verify. The first number is the installed version and the version in parenthesis is the version available in the repo.
It could be that you have versions installed from repositories different to Packman. But if you look in detail to the versions it should be obvious that for some time Packman published packages without the “<release>.pm.” part. It was an error in Packman that is now fixed.
Now you go and say to it that you want to install the ffmpeg version available in the repository. The version from the repository is newer, sure, but it has a lower version number and so it’s a downgrade.
What happens? Well, the ffmpeg version from the repository requires the libavdevice52 version from the repository. So if you want to “downgrade” ffmpeg (something you explicitly requested, so no further questions from YaST) you also need to “downgrade” libavdevice52.
Since downgrade is something bad (when it’s a real downgrade) YaST asks you: “Are you sure you want to downgrade libavfilter52?”, which is the first option in the “Conflict Resolution”.
I fixed this problem with just a “zypper dup”, without further questions from zypper. But that’s because I have my repositories well configured for what I want… Depending on what you want you can do this, just manually “downgrade” all the packages or something else.
To make it clear. If someone installed the packman packages without the “<release>.pm.” part, now a “zypper up” will not update them. There can be more people with the problem but without knowing.
Just after an update run:
LC_ALL=C zypper se -s -t package | fgrep '(System Packages)'
to check (I think in 11.3 this was a lot faster than in 11.4).
Here we go.
flamebait@fuuyuu:~> zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
---+-------------------------------------+-------------------------------------+---------+---------+----------+--------+-------------------------------------------------------------------+--------
1 | Updates for openSUSE 11.3 11.3-1.82 | Updates for openSUSE 11.3 11.3-1.82 | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/11.3/ |
2 | download.nvidia.com-opensuse | NVIDIA Repository | Yes | Yes | 99 | rpm-md | ftp://download.nvidia.com/opensuse/11.3/ |
3 | download.opensuse.org-games | openSUSE BuildService - Games | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_11.3/ |
4 | ftp.uni-erlangen.de-suse_1 | Packman Repository | Yes | Yes | 90 | rpm-md | http://ftp.uni-erlangen.de/pub/mirrors/packman/suse/11.3/ |
5 | google-chrome | google-chrome | Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
6 | hamradio | hamradio | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/hamradio/openSUSE_11.3/ |
7 | opensuse-guide.org-repo | libdvdcss repository | Yes | Yes | 90 | rpm-md | http://opensuse-guide.org/repo/11.3/ |
8 | repo-debug | openSUSE-11.3-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/11.3/repo/oss/ |
9 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/non-oss/ |
10 | repo-oss | openSUSE-11.3-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/oss/ |
11 | repo-source | openSUSE-11.3-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/11.3/repo/oss/ |
flamebait@fuuyuu:~> zypper se -si | grep "(System" | grep .pm.
i | kde4-partitionmanager | package | 1.0.2-0.pm.1.8 | x86_64 | (System Packages)
i | libaudid3tag2 | package | 2.3-2.pm.2.1 | x86_64 | (System Packages)
i | libcaca0 | package | 0.99.beta17-1.pm.2.7 | x86_64 | (System Packages)
i | libdvdcss2 | package | 1.2.10-2.pm.3.1 | x86_64 | (System Packages)
i | libdvdread3 | package | 0.9.7-7.pm.7.1 | x86_64 | (System Packages)
i | libvamp-hostsdk3 | package | 2.1-0.pm.1.1 | x86_64 | (System Packages)
i | libx264-106 | package | 0.106svn20101002-1.pm.1.1 | x86_64 | (System Packages)
i | libx264-107 | package | 0.107svn20101016-1.pm.1.6 | i586 | (System Packages)
i | libx264-112 | package | 0.112svn20110115-1.pm.1.2 | x86_64 | (System Packages)
i | python-beaker | package | 1.5.4-0.pm.1.1 | noarch | (System Packages)
i | python-pyxdg | package | 0.19-0.pm.1.1 | noarch | (System Packages)
i | wxWidgets | package | 2.8.10.1-2.pm.4.2 | x86_64 | (System Packages)
fuuyuu:/home/flamebait # zypper -v up
Verbosity: 1
Initializing Target
Checking whether to refresh metadata for Updates for openSUSE 11.3 11.3-1.82
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for NVIDIA Repository
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for openSUSE BuildService - Games
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for Packman Repository
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for google-chrome
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for hamradio
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for libdvdcss repository
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for openSUSE-11.3-Non-Oss
Retrieving: content [done]
Retrieving: media [done]
Checking whether to refresh metadata for openSUSE-11.3-Oss
Retrieving: content [done]
Retrieving: media [done]
Loading repository data...
Reading installed packages...
Force resolution: No
The following package updates will NOT be installed:
audacity 1.3.13-1.pm.56.1
curl 7.21.6-58.1
DirectFB 1.4.5-18.1
gstreamer-0_10 0.10.34-3.pm.56.1
gstreamer-0_10-plugin-gnomevfs 0.10.34-1.pm.45.1
gstreamer-0_10-plugins-base 0.10.34-1.pm.45.1
kaffeine 1.2.2-1.pm.1.3
libcurl4 7.21.6-58.1
libcurl4-32bit 7.21.6-58.1
libdrm 2.4.23-53.2
libdrm-32bit 2.4.23-53.2
libGLEW1_5 1.5.8-22.2
libgstapp-0_10-0 0.10.34-1.pm.45.1
libgstinterfaces-0_10-0 0.10.34-1.pm.45.1
libgstreamer-0_10-0 0.10.34-3.pm.56.1
libmodman0 0.4.3-4.1
libopenal1-soft 1.13-6.1
liborc-0_4-0 0.4.13-30.2
libproxy1 0.4.3-4.1
libschroedinger-1_0-0 1.0.10-20.3
libSDL-1_2-0 1.2.14-37.1
libSDL_image-1_2-0 1.2.10-6.2
libSDL_mixer-1_2-0 1.2.11-18.2
libSDL_ttf-2_0-0 2.0.9-316.2
libsndfile 1.0.24-22.2
libtheora0 1.1.1-8.4
libvdpau1 0.4.1-14.9
libvdpau-devel 0.4.1-14.9
libvdpau_trace1 0.4.1-14.9
mjpegtools 1.9.0.0-5.pm.5.4
openal-soft 1.13-6.1
python-numpy 1.5.1-25.1
python-pygame 1.9.1-2.2
The following packages are going to be upgraded:
libaudclient2 2.5.0-4.2 -> 2.5.1-1.pm.2.1
libaudcore1 2.5.0-4.2 -> 2.5.1-1.pm.2.1
libaudgui1 2.5.0-4.2 -> 2.5.1-1.pm.2.1
libaudtag1 2.5.0-4.2 -> 2.5.1-1.pm.2.1
4 packages to upgrade.
Overall download size: 104.0 KiB. No additional space will be used or freed after the operation.
Continue? [y/n/?] (y): N
I have packman set to priority 90 in YAST repository management.
It seems I believe I have packman packages of some packages that I actually don’t perhaps.
Then start fixing all that 
An example, wxWidgets is not available in Packman anymore since March 10th as announced by Pascal ([packman] Disabled our wxWidgets]([packman] Disabled our wxWidgets)). Reinstall the openSUSE version. This kind of things are fixed automatically by a “zypper dup”.
All those “libx264-XXX” can be removed. x264 changes a lot and they are kept there.
And you probably want to install all the “gstreamer-0_10*” and “libgst*” apps from Packman. zypper up isn’t doing it because it’s a vendor change. And a zypper dup will only do it if the Packman repo has a higher priority than “repo-oss” and “Updates for openSUSE 11.3 11.3-1.82”.
You have the “libdvdcss repository” but then the libdvdcss2 package installed from Packman (it was published in Packman for some days because of an error).
And well… you know what you want in your system. Look at the list and fix the errors.
Oh, and the “grep .pm.” part of “zypper se -si | grep “(System” | grep .pm.” is not correct. The problem we are searching for is precisely installed Packman packages without “.pm.”!!! (the “-i” part is an improvement over what I said)
I am kind of confused as to what I should be putting in for zypper to look for that this point.
We are veering off to /multimedia now but I know I want Packman kaffeine, gstreamer and mpplayer/smplayer/gmplayer and I have at least some of those. Also K3B, audicatity and some xmms packages I want to make sure that is what I have at this point.
I am also noticing some differences in naming conventions that really don’t tell me if what I am doing is actually a downgrade or a upgrade.
I removed the old libdvdcss that came from when it was in packman and added it back in from the new repository.
Packman’s priority is 90 so it’s higher than 99 which is where everything else is.
I am kind of confused here. Really confused.
RedDwarf I don’t know what the errors are and I only know how to use YAST to manage this stuff.
It looks like the naming conventions for lots of these files got changed from what they were and YAST thinks they are down grades but when I get hit with a popup telling me danger you are going to bork you system I don’t know what to do. So far I have been able to do mplayer and k3b but some of these want to change all kinds or things I have no knowledge about and I am afraid to do anything. I don’t want these things being in red. And am not sure what is safe. This is my main computer and I don’t want to make it unusable for it’s intended purpose.
Since you have Packman as the repo with the highest priority I understand that in all the cases where there are multiple versions of a package you want the one from Packman. So use “zypper dup --from ftp.uni-erlangen.de-suse_1” or click on the “Switch system packages to the versions in this repository (Packman Repository)” message from your first screenshot.
“zypper dup” shouldn’t give you any scary message, not sure about YaST.
After that you will continue having wxWidgets from Packman and other problems, but most if not all of the red packages will be fixed.
I manually got rid of wxWidgets and added back in the right one as I did for libdvdcss.
I used YAST and went through the packages one at a time and let the “downgrade” that were actually a update due to changes in package naming and switching vendor to packman take place letting YAST take the action it recommended. No more entries in red.
How are you supposed to keep abreast in changes in Packman? I know it’s a heck of a lot of work being done by just a few people so the changes they are making are to make it less work for them and to make sense out of some things that didn’t make sense to them.
You were, I wasn’t. Don’t tell me what is correct to look for, kay? 
Either way, I also recommend a ‘zypper dup’.
Should be solved after the ‘zypper dup’.