stable-proposed-updates repository required

phabricator-migrator · February 19, 2024, 5:51pm

Information

ID: 200
PHID: PHID-TASK-v2ejqr7tr6dwnfmcokau
Author: Patrick
Status at Migration Time: resolved
Priority at Migration Time: Normal

Description

At the moment (work on Whonix 10 in progress) there is a discrepancy with Whonix’s apt repository. Currently packages are Whonix 10ish. Any fixes for Whonix 9 are difficult to test. Those packages have naturally lower version numbers. So people who just want to help testing the small fixes so they can migrate into the stable repository, don’t really want or should use the testers repository, because that comes with a lot more changes. The only solution I can see so far is introducing a forth, stable-fixes-testers repository. Then we’d have:

stable
stable-fixes-testers
testers
developers

If you can think of a better solution or got a better suggestion for the name as alternative to stable-fixes-testers, I am all ears.

Comments

Patrick

2016-03-30 19:42:26 UTC

Patrick

2016-03-30 20:00:21 UTC

Debian has currently:

jessie

jessie-backports

jessie-proposed-updates

jessie-updates

Qubes has currently:

jessie

jessie-testing

jessie-securitytesting

jessie-unstable

Whonix currently has:

jessie

testers

developers

The Whonix approach does not scale anymore that’s the reason for this ticket.

I think Qubes securitytesting might be overkill, but I don’t know the reasoning. Might be simpler to have testing only. Certainly overkill for Whonix.

Has it become in Qubes jessie-testing rather than jessie-proposed-updates because of a reasoning or was proposed-updates terminology just unknown? If it was unknown, would it be considered a bug fix to mirror Debian terminology at some point? @marmarek

Depending on that, to implement this I must manage to decide if I rather want to mimic the Debian or Qubes approach.

marmarek

2016-03-30 20:14:54 UTC

I think Qubes securitytesting might be overkill, but I don’t know the reasoning. Might be simpler to have testing only. Certainly overkill for Whonix.

Yes, overkill for Whonix. It is explained in [[ qubes-secpack/QSBs/qsb-023-2015.txt at master · QubesOS/qubes-secpack · GitHub | every QSB ]].

Has it become in Qubes jessie-testing rather than jessie-proposed-updates because of a reasoning or was proposed-updates terminology just unknown? If it was unknown, would it be considered a bug fix to mirror Debian terminology at some point? @marmarek

Mostly unknown terminology, we’ve simply mirrored Fedora names (and to match builder commands like update-repo-current-testing). But at this point IMHO changing it not worth the effort (and all the breakage it could lead to).

Depending on that, to implement this I must manage to decide if I rather want to mimic the Debian or Qubes approach.

Go with Debian approach.

Patrick

2016-03-31 02:52:22 UTC

Patrick

2016-04-30 01:47:08 UTC