Arch Linux User Repository

Thanks @erikdubois it's works

Can you update the pkgbuild on the AUR - your script to update works fine

https://pastebin.com/BSg5hr3t

pkgname=vivaldi-codecs-ffmpeg-extra-bin pkgver=70.0.3538.77

Last deb : http://security.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-browser_69.0.3497.81-0ubuntu0.18.04.1_amd64.deb

Sorry for the delay, everyone. I've been off the grid for a week. But now I'm back and the package is updated. for future reference, there's a update_pkg shell script in the package that auto updates the package, feel free to use that.

Download is broken, to fix change pkgver to 68.0.3440.106 and update md5sum to 9b8e01858b346eea7c685da9faa2975f .

@martynjy You can use the same .deb file from another source, that's what I did. Edit the PKGBUILD and replace the quoted source with

https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+build/14846182/+files/chromium-codecs-ffmpeg-extra_66.0.3359.139-0ubuntu0.18.04.3_amd64.deb

Don't have to change the md5sum.

@lucifermstar, vivaldi replacing the file is exactly the problem. If vivaldi package gets updated after this package, then the file is reverted to its original version.

Anyway, the post-install script creates a file not tracked by pacman outside home folder. That doesn't sound like a very good practice IMHO.

@Aetf how is the post-install script fragile? that's not what breaks every time vivaldi updates. what happens is that the versions get incompatible and/or the file gets replaced by vivaldi.

The file should be put at /opt/vivaldi/libffmpeg.so, like the vivaldi-ffmpeg-codecs package. So there's no conflict, and no fragile post-install script, which breaks as soon as vivaldi updates.