On Wed, 25 Jul 2018 16:43:02 +0200 Andreas Stieger <astieger@suse.de> wrote:
Hello Dave,
On 07/25/2018 11:37 AM, Dave Howorth wrote:
I've just got a 'security' update for chromium, together with an 'optional' update. The optional update lists a load of ffmpeg packages which on my system come from packman, not opensuse. So my instinct was to refuse the optional update.
See https://lists.opensuse.org/opensuse-updates/2018-07/msg00068.html
If you read the summary and description, the update contains a number of Chromium dependencies. If you do not use Chromium, you do not need to install the update, but you can. If you do use the openSUSE Chromium build and decide to install the associated security update released right thereafter, some of the of the ffmpeg dependencies *introduced* by the optional update will be pulled in. This is supposed to happen with a package based distribution with shared library dependency tracking. It is also an enabling feature for your to replace some of the Chromium run-time dependencies with those from Packman.
That would mean I have a mixture of libav* components from packman and opensuse. Is that wise? What is supposed to happen here?
The Packman project is expected to provides matching builds in due time.
Why does a web browser care so much about the particular versions of my multimedia libraries anyway?
Because of kitten videos.
Andreas
Thanks Andreas, we're getting closer. But it's not the optional update I'm talking about; I turned that down. It's the updates (actually completely new installs) in the security update. My libav* comes from packman; this update wants to install new libav* files from opensuse. Surely that is going to bork my system? There are no corresponding files on packman, AFAIK. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org