-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Fri, 2019-04-19 at 13:09 -0400, sean darcy wrote:

FC29. I have a server for video encoding. I use x264, which I keep updated to the most recent git packaaged in an rpm.

rpm -q x264-libs x264-libs-0.157-0.20190331.fc29.x86_64

I then rebuild all the packages that depend on x264, including avidemux-libs. I just rebuild on my machine, without chaging the version, since the version hasn't changed, it's just linked to the new x264 version.

rpm -q avidemux-libs avidemux-libs-2.7.3-1.fc29.x86_64

But dnf want to replace my rebuild version, with the version for the repo:

dnf upgrade --refresh .............. Problem 1: package avidemux-libs-2.7.3-1.fc29.x86_64 requires libx264.so.155()(64bit), but none of the providers can be installed

• cannot install both

x264-libs-0.155-2.20180806git0a84d98.fc29.x86_64 and x264-libs-0.157-0.20190331.fc29.x86_64

I don't want to bump the avidemux-libs version, since I want to know when a new one is available. I don't want to keep adding "-x avidemux.."

Why does dnf want to replace the installed package ? How does it even know it's not the same package as the repo ?

sean

Hi,

You do need to bump in some way. You can...

Original: avidemux-libs-2.7.3-1

Your rebuild: avidemux-libs-2.7.3-1.1

Any new version from repo i.e. will be -2 or above and update as normal if/when released.

Regards

Phil

- -- *** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Twitter: kathenasorg IRC: kathenas Web: https://kathenas.org Github: https://github.com/kathenas GitLab: https://gitlab.com/kathenas

GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77