Comments

342 Comments
RPM Fusion cannot do rebuilds until this update will reach stable.

Ah, right.

The issue is clearly with this update, since podman has not been updated on our systems. If this update requires podman version 2 from the other update, then the two builds need to be pushed together as one update to prevent breakages.

Our of curiosity: what version of podman are you on that you did (or are not) seeing this bug?

Is podman v2 required for this? I've got 1.9.3 here: podman-1.9.3-1.fc32.x86_64

The podman v2 update for F32 hasn't even hit testing yet, and has 0 karma so it won't get to stable any time soon either: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6660e9ee6e

karma

Hrm, seeing a regression here, but not sure what's causing it:

With the previous version, I was able to build images without any issue:

$ rpm -q containers-common
containers-common-0.2.0-1.fc32.x86_64

$ podman image build ...
Building redmine image
STEP 1: FROM ubuntu:xenial-20180705 AS ubuntu-xenial-20180705
Getting image source signatures
Copying blob 99f229f854da skipped: already exists
Copying blob c9b72a16d85e skipped: already exists
Copying blob 3620e2d282dc skipped: already exists

After the update, this doesn't work any more:

$ rpm -q containers-common
containers-common-1.0.0-1.fc32.x86_64

$ podman image build ...
Building redmine image
STEP 1: FROM ubuntu:xenial-20180705 AS ubuntu-xenial-20180705
Error: error creating build container: (image name "ubuntu:xenial-20180705" is a short name and no search registries are defined in /etc/containers/registries.conf): while pulling "ubuntu:xenial-20180705" as "localhost/ubuntu:xenial-20180705": Error initializing source docker://localhost/ubuntu:xenial-20180705: error pinging docker registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

I see that the update already has 3 karma, rather quickly in 2 days: is no one else seeing this issue apart from me? Has the Dockerfile format that podman uses changed (in which case this is a major update and should not perhaps be pushed to stable releases now, right?)

The Dockerfile is in the repository here: https://github.com/SilverLabUCL/docker-redmine-osb/blob/master/Dockerfile

So, to reproduce:

$ git clone https://github.com/SilverLabUCL/docker-redmine-osb.git
$ cd docker-redmine-osb

$ podman build --tag "redmine" -f Dockerfile
STEP 1: FROM ubuntu:xenial-20180705 AS add-apt-repositories
Error: error creating build container: (image name "ubuntu:xenial-20180705" is a short name and no search registries are defined in /etc/containers/registries.conf): while pulling "ubuntu:xenial-20180705" as "localhost/ubuntu:xenial-20180705": Error initializing source docker://localhost/ubuntu:xenial-20180705: error pinging docker registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

Works fine after downgrading.

Update currently blocked here by the lack of the corresponding -freeworld update on rpmfusion from the looks of it. Jan, would you be taking care of that bit too please?


 Problem 1: package qt5-qtenginio-1:1.6.2-28.fc32.x86_64 requires qt5-qtbase(x86-64) = 5.13.2, but none of the providers can be installed
  - package qt5-qtenginio-1:1.6.2-28.fc32.x86_64 requires libQt5Core.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers can be installed
  - cannot install both qt5-qtbase-5.14.2-5.fc32.x86_64 and qt5-qtbase-5.13.2-5.fc32.x86_64
  - cannot install both qt5-qtbase-5.13.2-5.fc32.x86_64 and qt5-qtbase-5.14.2-5.fc32.x86_64
  - cannot install both qt5-qtbase-5.13.2-4.fc32.x86_64 and qt5-qtbase-5.14.2-5.fc32.x86_64
  - cannot install the best update candidate for package qt5-qtenginio-1:1.6.2-28.fc32.x86_64
  - cannot install the best update candidate for package qt5-qtbase-5.13.2-5.fc32.x86_64
 Problem 2: package qt5-qtwebengine-freeworld-5.13.2-3.fc32.x86_64 requires libQt5Gui.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers can be installed
  - cannot install both qt5-qtbase-gui-5.14.2-5.fc32.x86_64 and qt5-qtbase-gui-5.13.2-5.fc32.x86_64
  - cannot install both qt5-qtbase-gui-5.13.2-5.fc32.x86_64 and qt5-qtbase-gui-5.14.2-5.fc32.x86_64
  - cannot install both qt5-qtbase-gui-5.13.2-4.fc32.x86_64 and qt5-qtbase-gui-5.14.2-5.fc32.x86_64
  - cannot install the best update candidate for package qt5-qtwebengine-freeworld-5.13.2-3.fc32.x86_64
  - cannot install the best update candidate for package qt5-qtbase-gui-5.13.2-5.fc32.x86_64
 Problem 3: problem with installed package qt5-qtwebengine-freeworld-5.13.2-3.fc32.x86_64
  - package qt5-qtwebengine-freeworld-5.13.2-3.fc32.x86_64 requires qt5-qtwebengine(x86-64) = 5.13.2, but none of the providers can be installed
  - cannot install both qt5-qtwebengine-5.14.2-2.fc32.x86_64 and qt5-qtwebengine-5.13.2-4.fc32.x86_64
  - cannot install both qt5-qtwebengine-5.13.2-4.fc32.x86_64 and qt5-qtwebengine-5.14.2-2.fc32.x86_64
  - cannot install the best update candidate for package qt5-qtwebengine-5.13.2-4.fc32.x86_64
 Problem 4: problem with installed package qt5-qtenginio-1:1.6.2-28.fc32.x86_64
  - package qt5-qtenginio-1:1.6.2-28.fc32.x86_64 requires qt5-qtbase(x86-64) = 5.13.2, but none of the providers can be installed
  - package qt5-qtenginio-1:1.6.2-28.fc32.x86_64 requires libQt5Core.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers can be installed
  - cannot install both qt5-qtbase-5.14.2-5.fc32.x86_64 and qt5-qtbase-5.13.2-5.fc32.x86_64
  - cannot install both qt5-qtbase-5.13.2-5.fc32.x86_64 and qt5-qtbase-5.14.2-5.fc32.x86_64
  - cannot install both qt5-qtbase-5.13.2-4.fc32.x86_64 and qt5-qtbase-5.14.2-5.fc32.x86_64
  - package python3-qt5-5.14.2-3.fc32.x86_64 requires libQt5Core.so.5(Qt_5.14)(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package python3-qt5-5.13.2-5.fc32.x86_64

(Not given negative karma because this isn't an issue with this update)

karma

Same issue here. Awaiting a new release :)

Works, thanks very much!

BZ#1835864 Updating to adwaita-qt5-1.1.2-1.fc32.x86_64 causes Qutebrowser to crash consistently

The new adwaita-qt5 package causes Qutebrowser to crash. Filed bug:

BZ#1817659 annobin ICE: attempting to access a gcc command line option that is not stored in global_options
karma

works well, no regressions noted here

karma

works well, no regressions noted here

Seems OK.

Seems OK.

karma

Works fine, no regressions noted. @ersen, that does not necessarily imply a bug in this update: please see systemctl status ssd.service etc to see what the issue is.

Works well, no regressions noted.

Fixes the crashes. Thanks very much.

BZ#1812482 Fedora 32 qtwebengine crashes: affects both qutebrowser and falkon: [abrt] qt5-qtwebengine: sandbox::CrashSIGSYS_Handler(): QtWebEngineProcess killed by SIGSEGV
karma

Downloaded the builds off koji. Fixes the bug, boxes works once more! Thanks everyone!

I'm seeing a lot of new denials after updating to this package, such as:

https://bugzilla.redhat.com/show_bug.cgi?id=1816383

Could you please have a look?

Works OK in normal usage, no regressions noted.

Works OK in normal usage, no regressions/crashes noted.