Bug 2440511 - Update for Fedora 44 branch
Summary: Update for Fedora 44 branch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-appstream-metadata
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Timothée Ravier
QA Contact:
URL:
Whiteboard: openqa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-18 00:31 UTC by Adam Williamson
Modified: 2026-02-24 01:49 UTC (History)
2 users (show)

Fixed In Version: fedora-appstream-metadata-20260217-1.fc43
Clone Of:
Environment:
Last Closed: 2026-02-24 01:49:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2026-02-18 00:31:57 UTC
/usr/share/metainfo/org.fedoraproject.fedora.metainfo.xml does not contain an f44 entry. It should, since f44 has now branched.

We should probably add this to the branching SOP and do it at branch time.

This causes openQA's KDE upgrade tests to fail.

Comment 1 Fedora Update System 2026-02-18 00:55:39 UTC
FEDORA-2026-88f58c797c (fedora-appstream-metadata-20260217-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-88f58c797c

Comment 2 Adam Williamson 2026-02-18 00:56:03 UTC
Went ahead and did this since travier is away ATM.

Comment 3 Fedora Update System 2026-02-19 00:51:51 UTC
FEDORA-2026-88f58c797c has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-88f58c797c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-88f58c797c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-02-24 01:49:39 UTC
FEDORA-2026-88f58c797c (fedora-appstream-metadata-20260217-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.