Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CentOS Stream 10 template #9716

Closed
DemiMarie opened this issue Jan 15, 2025 · 2 comments
Closed

CentOS Stream 10 template #9716

DemiMarie opened this issue Jan 15, 2025 · 2 comments
Labels
C: CentOS P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: declined Resolution: While a legitimate bug or proposal, it has been decided that no action will be taken.

Comments

@DemiMarie
Copy link

How to file a helpful issue

The problem you're addressing (if any)

CentOS Stream 10 was recently released.

The solution you'd like

Ship a CentOS Stream 10 template. CentOS Stream 10 is Wayland-only: there is no xorg-x11-server-Xorg package. Therefore, the Qubes GUI agent cannot work. This means that one of the following is required:

The value to a user, and who that user might be

Users who want to use CentOS Stream 10 will be able to.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

@DemiMarie DemiMarie added T: enhancement P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Jan 15, 2025
@marmarek
Copy link
Member

Almost nobody cared about CentOS template when we had it before, so there is no point in spending time on the next one until there is some specific interest.

@marmarek marmarek closed this as not planned Won't fix, can't repro, duplicate, stale Jan 15, 2025
@andrewdavidwong andrewdavidwong added R: declined Resolution: While a legitimate bug or proposal, it has been decided that no action will be taken. C: CentOS labels Jan 16, 2025
Copy link

This issue has been closed as "declined." This means that the issue describes a legitimate bug (in the case of bug reports) or proposal (in the case of enhancements and tasks), and it is actionable, at least in principle. Nonetheless, it has been decided that no action will be taken on this issue. Here are some examples of reasons why an issue may be declined:

  • No solution can be found.
  • The proposed action is not possible.
  • The proposed action would weaken security to an unacceptable degree.
  • The proposed action would be too costly (in time, money, or other resources) relative to the benefits it would provide.
  • The proposed action would make some things better while making other things worse, and the trade-off is not worthwhile.

These are just general examples. If the specific reason for this particular issue being declined has not already been provided, please feel free to leave a comment below asking for an explanation.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "declined" is not accurate, please leave a comment below saying so, and the Qubes team will review this issue again. For more information, see How issues get closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: CentOS P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: declined Resolution: While a legitimate bug or proposal, it has been decided that no action will be taken.
Projects
None yet
Development

No branches or pull requests

3 participants