Fix building with libavif 0.8.2

How to install

sudo dnf upgrade --refresh --advisory=FEDORA-2020-db7df6b305

This update has been submitted for testing by asn.

a year ago

This update's test gating status has been changed to 'ignored'.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

asn edited this update.

New build(s):

  • libavif-0.8.2-1.fc33

Karma has been reset.

a year ago

This update's test gating status has been changed to 'ignored'.

a year ago

This update has been pushed to testing.

a year ago
User Icon nphilipp commented & provided feedback a year ago
karma
 Problem: package efl-1.25.1-1.fc33.x86_64 requires libavif.so.6()(64bit), but none of the providers c
an be installed                                                                                       
  - cannot install both libavif-0.8.2-1.fc33.x86_64 and libavif-0.8.1-1.fc33.x86_64
  - cannot install both libavif-0.8.1-1.fc33.x86_64 and libavif-0.8.2-1.fc33.x86_64
  - package darktable-3.2.1-8.fc33.x86_64 requires libavif.so.7()(64bit), but none of the providers ca
n be installed      
  - cannot install the best update candidate for package efl-1.25.1-1.fc33.x86_64
  - cannot install the best update candidate for package darktable-3.2.1-7.fc33.x86_64

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

a year ago

Hmm, attempting to rebuild the efl package doesn't work because of API changes between libavifseries 0.7.x and 0.8.x.

For the issue that efl 1.25.1 cannot be built with libavif 0.8.2, I've reported efl upstream: https://phab.enlightenment.org/T8844

For rawhide, I've once disabled libavif support for efl: efl-1.25.1-3.fc34

This update can be pushed to stable now if the maintainer wishes

a year ago

The libavif API still changes as 0.x versions are pre-releases.

If you can't fix avif support for a package yourself, I would suggest not to enable support for it till version 1.0 is out. It is likely that this will happen again!

If you're up for the task, I can create a build root overwrite if it already expired and we rebuild elf and add it here. Or you disable avif support in elf for f33. How do you want to proceeed?

User Icon lruzicka commented & provided feedback a year ago
karma

Works as expected. Thank you.

@asn could you push this to stable?

As efl upstream seems slow for fixing FTBFS for libavif 0.8.2, perhaps it is better we drop libavif support from efl for now. @spot , ideas?

User Icon lbrabec commented & provided feedback a year ago
karma

works

So we should really handle efl v.s libavif dependency error. Currently (although I am not maintainer for efl or for libavif, ) I am for disabling libavif support on elf. Everyone, how do you think?

This update has been submitted for stable by asn.

a year ago

This update has been pushed to stable.

a year ago

Please login to add feedback.

Metadata
Type
bugfix
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
a year ago
in testing
a year ago
in stable
a year ago
modified
a year ago

Automated Test Results