| Summary: | Request for new atomic-workstation subpackage | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David King <amigadave> |
| Component: | fedora-release | Assignee: | Dennis Gilmore <dennis> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | amigadave, dennis, jdisnard, kevin, mclasen, pbrobinson, sgallagh, zbyszek |
| Target Milestone: | --- | Flags: | sgallagh:
needinfo?
(amigadave) |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:58:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
David King
2016-03-14 12:33:27 UTC
Just to clarify: this is a request for F25 Is this coming from the Workstation Working Group? Can you point to an official decision that states that Atomic Workstation is a planned deliverable? (Ideally a Fedora Change Proposal). Also, please identify EXACTLY what you want in the /etc/os-release file (and whether you want anything unique in /etc/issue or systemd presets to accompany this. From my memory, last weeks irc discussion eventually settled on something like VARIANT="Workstation Edition (OSTree)" VARIANT_ID=workstation.ostree to parallel VARIANT_ID=atomic.host The exact details don't matter much for us, as long as we have a different VARIANT_ID. This is not yet an official Workstation WG request, but you are right that we need to get this set up as an official F25 change. I'll bring it up in the next WG meeting. the variant is Workstation, we need an extra field that says Delivery method = ostree. we also need to consider atomic trademarks and only call things atomic that fall under projectatomic. what are the use cases for having VARIANT_ID have ostree in the name? we should also work with QA to ensure that things are suitable for them. Last week on IRC at least adamw agreed with me that it needed to have a separate field to define the use of ostree I suggested OS_UPDATER or SYSTEM_UPDATE or something along those lines This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |