obsolete

clang-18.1.3-2.fc40, compiler-rt-18.1.3-1.fc40, & 11 more

FEDORA-2024-556229bb4a created by tstellar a year ago for Fedora 40

LLVM 18.1.3 Update.

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

a year ago
User Icon amusil provided feedback a year ago
karma

This update has been submitted for testing by bodhi.

a year ago

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

a year ago
User Icon cmorris commented & provided feedback a year ago
karma

There appears to be a conflict when one attempts to install both the 32-bit and the 64-bit libraries:

sudo dnf upgrade clang-18.1.3-2.fc40.x86_64.rpm clang-resource-filesystem-18.1.3-2.fc40.noarch.rpm clang-libs-18.1.3-2.fc40.i686.rpm clang-libs-18.1.3-2.fc40.x86_64.rpm ... Running transaction check Transaction check succeeded. Running transaction test Error: Transaction test error: file /etc/clang/clang++.cfg conflicts between attempted installs of clang-libs-18.1.3-2.fc40.i686 and clang-libs-18.1.3-2.fc40.x86_64 file /etc/clang/clang.cfg conflicts between attempted installs of clang-libs-18.1.3-2.fc40.i686 and clang-libs-18.1.3-2.fc40.x86_64

This update has been pushed to testing.

a year ago

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
User Icon agurenko commented & provided feedback a year ago
karma

Same error as @cmorris

Error: Transaction test error:
  file /etc/clang/clang++.cfg conflicts between attempted installs of clang-libs-18.1.3-2.fc40.i686 and clang-libs-18.1.3-2.fc40.x86_64
  file /etc/clang/clang.cfg conflicts between attempted installs of clang-libs-18.1.3-2.fc40.i686 and clang-libs-18.1.3-2.fc40.x86_64

User Icon trn commented & provided feedback a year ago
karma

Same conflict as others are seeing, preventing if you need both update with 32- and 64-bit libraries.

User Icon nerijus commented & provided feedback a year ago
karma

Same here.

This update has been obsoleted.

a year ago

Isn't this a recurring problem that the updates-testing repo doesn't handle multilib correctly?

I don't think so, not if dnf is reporting an actual conflict between the packages from this update, and they're supposed to be parallel installable.


Please log in to add feedback.

Metadata
Type
unspecified
Karma
-3
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Thresholds
Minimum Karma
+2
Minimum Testing
14 days
Dates
submitted
a year ago
in testing
a year ago

Automated Test Results