#67 Incorrect FTBFS status
Closed 4 years ago by xvitaly. Opened 4 years ago by xvitaly.

Dashboard displays the wrong FTBFS status for the psi-plus (and previously psi) packages: https://packager.fedorainfracloud.org/xvitaly

failing to build for Fedora 32
  src-ppc64le, src-s390x:
    cmake(Qt5WebEngine)

Building on these architectures is disabled due to ExclusiveArch: %{qt5_qtwebengine_arches}.

Koschei has no errors with them: https://koschei.fedoraproject.org/package/psi-plus


Metadata Update from @frantisekz:
- Issue assigned to frantisekz

4 years ago

Okay, this fail is coming from Fedora Repochecker data source [0].

My guess would be that the psi-plus package was built at least once in F32, so you basically can install that package on Fedora 32 on s390x/ppc64 (even if it is in lower version before you limited the supported architectures). You can try it with:

$ mock -r fedora-32-s390x --no-bootstrap-chroot --forcearch s390x -i psi-plus
#You'll get psi-plus-1:1.4.654-6.fc32.s390x installed.

And because of that, repochecker is checking if its build dependencies can be satisfied even on s390x and ppc64. I'd say it will disappear with F32 EOL. @decathorpe , will you please correct me if I am terribly wrong somewhere :) ?

[0] https://pagure.io/ironthree/repochecker

No, that's a bug in the compose process (koji or pungi). Source packages will get included in "source" repositories even if they have been excluded by Exclude / ExclusiveArch for those architectures (EDIT: rather, they get copied to the source repositories for those architectures regardless of the architecture the source package was built on). I've added overrides for those issues in the repochecker configuration, but psi-plus switched to QtWebEngine after I updated that list the last time. I'll add it with the next deployment.

See this file for other examples of excluded packages due to QtWebEngine:
https://pagure.io/ironthree/repochecker/blob/master/f/overrides.json#_88

PS: But yes, I think you're right, my ExcludeArch / ExclusiveArch checks should exclude the package, but since it was previously available on ppc64le and s390x, they don't work.

I just deployed a new version and the new configuration. It will take a bit until it refreshes its data, but then it should be fixed. Please tell me if this is still still wrong tomorrow :)

Metadata Update from @xvitaly:
- Issue status updated to: Closed (was: Open)

4 years ago

Log in to comment on this ticket.

Metadata