Bug 1720311 - KDE live images and network installs do not include fedora-release-kde
Summary: KDE live images and network installs do not include fedora-release-kde
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD - KDE
Version: 31
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Sebastian Vahl
QA Contact:
URL:
Whiteboard: openqa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-13 16:05 UTC by Adam Williamson
Modified: 2020-11-03 21:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-03 21:35:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2019-06-13 16:05:10 UTC
While working on an openQA self-identification test, lruzicka and I discovered that Fedora KDE live images and network installs do not actually seem to include the fedora-release-kde package. That package exists and contains all the appropriate bits to identify a 'KDE' install, but it's just...not used.

AFAICS it's not in comps and never has been. I also don't see that it's ever been in kickstarts. I am not sure if this is intentional or if it's just...never been noticed?

Comment 1 Adam Williamson 2019-07-04 18:37:50 UTC
Either Rex or Kevin (I forget which) pointed out that adding it to the comps groups might cause issues on upgrade (also on installing the group to an existing system), and might be argued not to be the right thing to do anyway - just because the KDE group is installed doesn't mean this is a "KDE" install.

Those are reasonable points, so on that basis perhaps we should add the package to kickstarts, but not to comps.

Comment 2 Ben Cotton 2019-08-13 16:58:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 3 Ben Cotton 2019-08-13 19:06:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 4 Adam Williamson 2019-08-21 20:26:07 UTC
https://pagure.io/fedora-kickstarts/pull-request/569

Comment 5 Ben Cotton 2020-11-03 17:03:01 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Adam Williamson 2020-11-03 21:35:39 UTC
PR was merged a year ago.


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