Hi again
I hope this is in the right foum for this question. I want to update, so i pressed the icon in the bottom right of the screen, when i press the install
button i get this message:
patch:openSUSE-2016-433-1.noach conflicts with flash-player.x86_64 < 11.2.202.616-294.1
provided by flash-player-11.2202.616-1.1.x86_64
How do i go about fixing the conflict.?
Thank you, your help is appreciated
Show us
zypper lr -d
Here is the result of zypper lr -d
[CODE# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
—±-----------------------------±-----------------------------------±--------±----------±--------±---------±-------±----------------------------------------------------------------±-------
1 | Packman | Packman | Yes | (r ) Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_13.2/ |
2 | download.nvidia.com-opensuse | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/13.2/ |
3 | libdvdcss | libdvdcss | Yes | ( p) Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/13.2/ |
4 | openSUSE-13.2-0 | openSUSE-13.2-0 | Yes | ( p) Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-DRW-24D3ST_K85E9NG0811 |
5 | repo-debug-update | openSUSE-13.2-Update-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.2/ |
6 | repo-debug-update-non-oss | openSUSE-13.2-Update-Debug-Non-Oss | No | ---- | No | 99 | NONE | http://download.opensuse.org/debug/update/13.2-non-oss/ |
7 | repo-non-oss | openSUSE-13.2-Non-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/non-oss/ |
8 | repo-oss | openSUSE-13.2-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/oss/ |
9 | repo-source | openSUSE-13.2-Source | No | ---- | No | 99 | NONE | http://download.opensuse.org/source/distribution/13.2/repo/oss/ |
10 | repo-update | openSUSE-13.2-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2/ |
11 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2-non-oss/ |
]
Thank youThere should have been a conflict resolution dialog with some choices.
It would have been easier to answer this if you had quoted those choices.
In any case, I booted up 13.2 to check what is happening.
Patch openSUSE-2016-433 does appear to be the flash update.
Flash is available in either the update-non-oss repo or in the packman repo.
It looks as if you have flash installed from packman, while that patch wants to install from update-non-oss.
One of the resolution options should have been to switch to the version in update-non-oss. This would have been described as a vendor change from packman-something to opensuse (or similar). I suggest that option.
Another option would have been to not install this patch. That would work too. But you will be faced with the same issue on the next flash update.
I suppose that this is because we have given contradictory advice. The multimedia guide says to do a vendor switch, and that would switch flash to packman.
Most folk do not run into this problem, because they did the switch to packman before the packman repo added flash. So the vendor preserving of most updating would keep flash coming from update-non-oss. However, if you added multimedia support recently, this will have happened to you.
Actually, the flash from packman should work just as well. It’s the same binary blob from adobe. But it’s going to give these conflicts on every flash update. So it is wisest to switch flash back to update-non-oss.
Sorry if that was too wordy. If you are still not sure what to do, then ask further questions. Or use Yast Software Management, search for flash, click the version tab, and select the version from update-non-oss. You will still get a conflict dialog, because it may insist on also switching the gnome utility for flash, and it might want to select the kde utility (if you are running kde).
Thank you nrickert
I thnk I have solved the problem, zypper is working as i write. Your wordy reply gave me the idea to
try zypper. I figure it must have something to do with kde.When it finishes it will let you know how it whent.
It’s hundreds of megs
Thanks
Then I slightly misunderstood your issue.
Yes, “zypper up” will do lots of updates without complaints.
If you try Yast online update, you will see the same conflict. But you will have a conflict resolution dialog.
What I failed to realize, was that your problem was with the update applet. And, yes, that does not handle problems well. It just refuses to do anything and indicates an error. So going to “zypper” gives you better results when there is a conflict.