Debian testing template

[DemiMarie]

How to file a helpful issue

The problem you're addressing (if any)

It takes some time between a new Debian version coming out and the corresponding template being released.

The solution you'd like

Have a Debian testing template that is always tested, so that when testing becomes stable, Qubes OS is ready.

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

Debian users will benefit from quicker updates when a new template comes out.

[marmarek]

I'm not sure about building actual template, as changes in development version may quickly make it obsolete (and I'd rather not rebuild template weekly or so). But packages for Debian testing are already in the current-testing repository.

[DemiMarie]

I'm not sure about building actual template, as changes in development version may quickly make it obsolete (and I'd rather not rebuild template weekly or so).

Is this because building a template is expensive? The main goal is to get test coverage on the next stable before is actually stable. Also, your comment is equally applicable to Arch or Gentoo 🙂.

[marmarek]

The main goal is to get test coverage on the next stable before is actually stable.

For that, we start preparing template before the release, but after feature freeze. That's exactly the time for fixing bugs, and we can help that by (at least) providing bug reports.

[github-actions]

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.