How to enable testing repositories?

107 views
Skip to first unread message

Albin Otterhäll

unread,
Jun 12, 2016, 8:21:25 AM6/12/16
to qubes...@googlegroups.com
It seems to exist a testing repository; but I can't find anything in the
documentation (for developers) about how to change the default repos to
the testing one. I guess that the instructions exist there, but they are
hard to find. Could someone please link me to them?

Kind regards,
Albin

Andrew David Wong

unread,
Jun 12, 2016, 9:38:16 AM6/12/16
to Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Actually, I don't think it's documented. Anyway, you can see the
available repos in /etc/yum.repos.d/qubes-dom0.repo.

Example commands:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable

(Or enable one or more of these repos in
/etc/yum.repos.d/qubes-dom0.repo. Should be similar for other .repo
files in /etc/yum.repos.d/ and TemplateVMs.)

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXXWXAAAoJENtN07w5UDAweeIP/3UluJT5Z4nqW4dKuK8+3Q5S
3BRXoL1Bf3sWSCN3rszqPes2ZoRVAepxb0B8obDMeH+R6d8i6tUdeX6ll91Uk7qO
uZJvoC7Zzf5x5WfAnXRKRAJYyz7muHMtkvvxrijXgRDwPOo1xI5nCgfoILvVRcqB
L3vU6wrstC5VJCduglZ0GIUmlUTGKTzYFNQb2YAbQ5JEvp9Qe9OVgvwd6KXi3pYv
VKlYNOeeHJPZMYc0Een6jcWDN3Jk2fxf07pD3n72XUPmZrv4ZoZe/UiaXn0umS1v
bqn+BCHAK3oI/XnkAigmOaiXzjpGl7qddzS5TRdI9vAY5v5xeVbTy69W7t16G97C
OGTjlH0u91aysgVOBmMdnVHi0gPkAtwTl4+7WEYH9AELEDa5wudPxpKMQT4aXMn7
PsLSt/TMLM/YVgDzF/TgKIzOvWviH64unBAqVY26QEe9yGqEFP0weQ9avlf1LDI6
6Z4XJwzDQ7sPL6NN6ulGmQOexlxrwBFXHEUFRf6a1cHaOffFpv0CN/5U3E9JvtHE
NdI0N1pHN82tUgN9qxOFDQuGqZq5pm5I+Vs2Gj7ygiau/C+8n2wf+Be+3jBohCZZ
ogrBOjt7V+YYUFx7kZmv/7cnciVzv8Y41OWI6WMzVlfdoCef0wmgLRwNm72WlkM0
2iie+Hgq3O9dTWYQFP24
=NXFu
-----END PGP SIGNATURE-----

Albin Otterhäll

unread,
Jun 12, 2016, 10:23:52 AM6/12/16
to qubes...@googlegroups.com
Andrew David Wong:
> On 2016-06-12 05:21, Albin Otterhäll wrote:
>> It seems to exist a testing repository; but I can't find anything
>> in the documentation (for developers) about how to change the
>> default repos to the testing one. I guess that the instructions
>> exist there, but they are hard to find. Could someone please link
>> me to them?
>
>> Kind regards, Albin
>
>
> Actually, I don't think it's documented. Anyway, you can see the
> available repos in /etc/yum.repos.d/qubes-dom0.repo.
>
> Example commands:
>
> sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
> sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing
> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable
>
> (Or enable one or more of these repos in
> /etc/yum.repos.d/qubes-dom0.repo. Should be similar for other .repo
> files in /etc/yum.repos.d/ and TemplateVMs.)
>
>

Thanks! What's the difference between the repositories?

Andrew David Wong

unread,
Jun 12, 2016, 10:30:56 AM6/12/16
to Albin Otterhäll, qubes...@googlegroups.com, Marek Marczykowski-Górecki
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

My basic understanding is:

current-testing contains non-security-critical packages that are being
tested before they move to the stable repo.

security-testing contains security-critical packages that are being
tested before they move to the stable repo.

unstable contains packages that are not yet stable enough to be tested
(i.e., to be moved to current-testing).

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXXXISAAoJENtN07w5UDAwdEsP/3Bdh9BbfAqUE6QGOgi86u+X
dszG8H96lkSqCorI4RQAKO53djLUNYOajDuzRGoYg2+cSo/OJwmnDDYzqdU1rLNt
Wx4HgDNrzISvM4kLY6om3lOcl1WxAnGIpDjOulok3CseGACo55K/b6703SM9S7nR
jirVVPgdS/6hk58LX7baIcG86aNauu81ViWFN3wtxe5zvzaKRoICAq7E7PkSzmOs
Pnjx9vVMFBECks8ikIr3AUhsmpOEW9DJwiKNSIWiFBJedaHHIc6YXfxQwJTN3ynl
9nm4fdP5lq2Efjo3ElwZC1aekAnNQYKKlddmCUkDn1HSTobQV6f+jlLNj2Cy6NwS
QkHGIpmKI0ewqz/RYV/pl5vLXHM0Vn5i9ZFtqqLRbc5fatmNChLojhM5j/Yg9Ewc
VuHrnYyK49BHDOhT9L7/UPwtS+kRBn16Fq7DGESgTJM8YK1rtsQVqQPtJ50nB58D
kN/T+2hc7/WoRZ0bamfd8iIeRd7jvfaIdsLY3TgBfU04sbOrGsg4aqrKMxEDyfUN
P2u+dCgSGk1aT/GgrCc9Ebsl9Ju30R7nhmTaOA4ORhFP+sYRSjhczJAnNIuBANYz
7lrqmVL/RNMhjd/3B3uvVJPtTmuzjcFrkIpAcNG5k4iy6JrEjPHISINbHts8tv+L
34QnuFOkAe7WL33zqdGJ
=vOkG
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki

unread,
Jun 12, 2016, 1:29:27 PM6/12/16
to Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
current-testing - testing packages that will eventually land in stable
("current") repository

security-testing - subset of "current-testing" that is qualified as
security fixes

unstable - packages that are not intended to land in "stable"
repository, mostly some experimental debugging packages

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXXZvvAAoJENuP0xzK19csFoEH/iD91pfpy6mQqOBRpwPCDJnc
B5n13TlqScttI11E6e51YybVItbi2EW3opuh7O5vQChy+1DUaA+kF077EWLFEAk4
/Nra5GvX4WK2juxGXO2nBZV5lFbYuZNeTq/no7MTiO0P0SJ1bV8uwqIN9KV9VM8g
JJCukUV7C9zQXc8HiRKrcVq3wvb5VNvQA2YZkkB6Gof2cnOOHyfZZ369uZy934ld
UM1ZcpV70N4opzFctaNpy2XGaMO4Inxg+RUbCjUWRtu0IWq7/DcNRkXAIqdINpPa
0UKz5Z+hQakJ7fACBYivCuBSj7z9Fnk/LWPgFMg/6Hz+uuwH8SyUgeVRcipQocA=
=GOgY
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki

unread,
Jun 12, 2016, 1:41:09 PM6/12/16
to Albin Otterhäll, Andrew David Wong, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Andrew, maybe it worth putting somewhere in the documentation? Any idea
where?

https://www.qubes-os.org/doc/software-update-vm/ ?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXXZ6tAAoJENuP0xzK19cs9PIH/RuD0rI8cy85KNGe85wcDGAI
lVDo9O+/W9VBAxcG3ct7vecXb0BI2++l3mUNyn2ZkCAvQNlbpNtQ7aH6Gh/FZMCZ
P4fPcaUVhuWoPp9Ufgb/GB+gUbevirumB3lDm4H8M1iTV7tuQ22PK702SZyQV//u
SfmuIK522BU0R6vUHOdHugfV37AxjMmF61FsDFDNCTg1DzdmGV1pFsEPB6hTpJcy
HwEg2sN9rgk/DgytxSKyoLLgkJOIhDks8dM2jRDxJ8NECi94JipYQDD6BaE/+lKI
PsLCgbUOFqCV/vP0P5yvIaXe31Lwh3Sh/DePU4km9JxgKnHcOJWjSfX9lY9GOns=
=UV6C
-----END PGP SIGNATURE-----

Andrew David Wong

unread,
Jun 12, 2016, 1:44:57 PM6/12/16
to Marek Marczykowski-Górecki, Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Yes, absolutely.
Wouldn't it make more sense in
https://www.qubes-os.org/doc/software-update-dom0/ ?

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXXZ+RAAoJENtN07w5UDAwAIIP/iNt/GrgqXIr2WYk68bVWAKn
IhlifqGF9cjOlGpWwx6nKZ+tFYHsc1t+CjQiNmp9di4e8GicTDyTMJlqpGSDij+g
u2oZ2ZAjzC7E5J3OtmvOOU6wgkLJk/ZOlN4qPmpR31T2ddL6IeHe3vD3qAwN7k0g
f4uRU6qQP3v3lOkdC3esHc6CYVt80xcp7fSY9ydtNrb/OX9Il9dijFCbCHd5ZywT
C7L42v6BVV2iBzcHHYmBPf45u2HM5NTxf7Uu3Vxw39odE4kgNwR+tdLQbFGBZJGl
CfEujnLq5BqwXWrGql67GLQhY2V1tFWDE+zkcXpobCKVzWgu58U2zBb6zflL9hDD
/AmxhppKwT9Ck4LpUfYC2e/ai7G0yC2Eqw7nNtmUmHr8DGOEfDWgyirhzEvvDKHU
IuAXNpJKExA+x4uYsqdCTQjTc4itWpGlxZ1sAFjgzz40Y3a9OUxSDSlDvt4i08Th
GhC2NkFKrhxIfh13cgs3k+o7m9O4l88d9vcfusFyL+LMPClojkr6Fvk64zYPoMPX
0y2w9zPJQGpiJYwrO5gtlDFen4HFu0hoppUWnC5rMeKOzwlEgGLi/sMZ5HHAMtcB
XDlXBEkIYwHs34IZfXhZEY4S5mPlyMrvMeQ4SjlwJIf6eiid1WRxWY/Xm5xYnMUM
FkQU8v1DPj/BXJGJcGUk
=8DQg
-----END PGP SIGNATURE-----

Albin Otterhäll

unread,
Jun 12, 2016, 1:46:51 PM6/12/16
to qubes...@googlegroups.com
Marek Marczykowski-Górecki:
> security-testing - subset of "current-testing" that is qualified as
> security fixes

If I enable "current-testing", do I receive the same updates and at the
same time as "security-testing", or should I enable both of them?

Albin Otterhäll

unread,
Jun 12, 2016, 1:56:35 PM6/12/16
to qubes...@googlegroups.com
Marek Marczykowski-Górecki:
> unstable - packages that are not intended to land in "stable"
> repository, mostly some experimental debugging packages

Btw, wouldn't "experimental" be a better name for a repository with that
purpose? I think that it can be quite confusing, especially with the
Debian project using a similar naming scheme but is different.

E.g. Qubes' testing is like Debian's testing, but Qubes' unstable is
like Debian's experimental and Qubes hasn't any repo comparable to
Debian's unstable.

Marek Marczykowski-Górecki

unread,
Jun 12, 2016, 2:15:44 PM6/12/16
to Andrew David Wong, Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
This applies to both VM and dom0 updates, so not sure what would be the best
place...

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXXabKAAoJENuP0xzK19csov0IAI1E3gNS9kikdB0GXzwzVPLl
QbAk8d5xLWD16o9t4czEguiNri1QH8OYj2r7qn9BzRLIi4EtgflxYJ2BS8v4c+qR
Y8cmivRwj74WMtgGXYNkp79Rpo0RsRGE1IrXr1Bq0c9c0hu/jepftagBUWhVvDK9
VQ6JKrUEWRQLf7W2qY5vV1aPRsUk9rDuWFxBeTI2/BbIsmlOBFAPsG35t4XOdJky
pgLwL4MoPBoAcCXFNCFAL9UIBqs69CrojAmPEDVEBCxNxU3Gf3tE+Z8DsfKekEKI
iCz6EvvXTYLKFmhT9ljTjVKC1bsIdlrbIif6feKH1a0iABWoRl0wN/6mB7LRLdg=
=l3g3
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki

unread,
Jun 12, 2016, 2:19:26 PM6/12/16
to Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Indeed it somehow matches Debian's "experimental". But I don't think it
worth the effort to change this. It's just one of distribution supported
in Qubes. Later someone could say "hey, in distribution X it's named Y,
lets rename it".

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXXaenAAoJENuP0xzK19csluQH/28vQUgPasGR4DXtePAWNxaa
IMlbuxIn5jFzFz1WKzKBGorLlvHfXqOCadw4wS/4G4gY/lTXk1N9n78K6t16nFCn
fISEKbx9JS5n5XTVaZl8LqFzmJgMNnGvO4vER2Ist2l+CpaeIeS+mkRWgl1M+tD4
PH6wjvpnY94wcKQTsyihpaK/L5i6DSfx6x094Hz1eY9Q05SQMTQp8x94xMo63m3V
ym6bCe5/ryUmALLUdvvR4u+a0ZV4/LtSj3fqUl023CWd4RJCo+NjldmtkAibPeGx
vyzmvprBO9r30q9GX5RPh+Pnot4dYM0T3gIvoW5Oq1cgBh7C0HV6yH2Y17oXuis=
=9sFq
-----END PGP SIGNATURE-----

Andrew David Wong

unread,
Jun 12, 2016, 2:43:44 PM6/12/16
to Marek Marczykowski-Górecki, Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-06-12 11:15, Marek Marczykowski-Górecki wrote:
> On Sun, Jun 12, 2016 at 10:44:50AM -0700, Andrew David Wong wrote:
>> On 2016-06-12 10:41, Marek Marczykowski-Górecki wrote:
>>> Andrew, maybe it worth putting somewhere in the documentation?
>
>> Yes, absolutely.
>
>>> Any idea where?
>>>
>>> https://www.qubes-os.org/doc/software-update-vm/ ?
>>>
>
>> Wouldn't it make more sense in
>> https://www.qubes-os.org/doc/software-update-dom0/ ?
>
> This applies to both VM and dom0 updates, so not sure what would
> be the best place...
>

Added to both pages:

https://github.com/QubesOS/qubes-doc/commit/
c664629e4b053f93ce41a0e7358846555a141ad9

https://github.com/QubesOS/qubes-doc/commit/
4f0aad927024dbcafff437c6e5e5b08adeccac6a

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXXa1VAAoJENtN07w5UDAw1CUP/39vIdnXL7/d2m+Z9Tay13qA
6/rQaLI6mCpybGhYMGY2TQVLnt9BTDz3Q53YTkhjlvvgStPq9Kp03Ddh/5cFnDVx
VEow4xQGjNqy7kAFoUbrUp4QV/XLN3nMkRDvLxVPPbuw7PtL02G738BT7o8ibIA+
j9G7ia49ar8CKD8IOhd7A3WF0+847moozu0/mD9Ygeg42CcvLMPUhCgp6WBWMcap
WIvxJxGZkoZONJMgL/c5OXPdsEI2VCVppUK1yyHT5RsWSX59arMIHn7m+C+j++R3
mSTnSxbUX0eZmaitcib4SEXsqqUKQok9GWgScN7RQmZ9rroDbVefadgI17cuvCak
JIpZMfUqgAUgrXDTsg0h5HcHkT/nFbiXC3UNjyaK3zgCFACLeMcj/GnF6U5sZnYQ
pQSUwD0W7vtTdbdPQNYN8aSRTaEppD9h0+1gVhkJs/yvVZVGzz+vt0E2K/SnXVj7
f0+AH3UM9wFYDPmBPr78Z0GAbqKyBO/4dS/e0KhSbMLmsKqQP+tfTTU4/NTDmNz1
p+Lcc5FZ1qB92V3zgaz1EB0pgZ1Rs2EcOU6u4Xnki1PEFkeo/9bD71OIzoSIWIFb
FZT5MDz5I4lg6+fioJ+oXCD3znH0VvqJ/mUyL/XN34WUzrKc+nwRCPVBc+BNXjbD
TsjQXCrwghptk3rHagIt
=qMRp
-----END PGP SIGNATURE-----

Albin Otterhäll

unread,
Jun 12, 2016, 3:14:43 PM6/12/16
to qubes...@googlegroups.com
Marek Marczykowski-Górecki:
> Indeed it somehow matches Debian's "experimental". But I don't think it
> worth the effort to change this. It's just one of distribution supported
> in Qubes. Later someone could say "hey, in distribution X it's named Y,
> lets rename it".

I don't think it's something very important, but in UX perspective I
think that "experimental" is more descriptive of the repository's
purpose than "unstable".

Could you please also answer my other question stated in the mail before
the one you replied to?

Marek Marczykowski-Górecki

unread,
Jun 12, 2016, 4:02:28 PM6/12/16
to Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yes, security fixes are uploaded to both of them.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXXb/NAAoJENuP0xzK19cs6gAH/2JoW/nBuiJFgAJ8SeYv6WrC
GnHx5WrP0D3hZy0/qE+n3AlTYx9RtTsw9KqKlQQ2DZPF4H6Gp2F1yeQpjjR4A/nY
13TNilmEYGHhDCqBSj+rMWit2hbrZxTfnz1mzfii0Fw6xhfzz3f1zsJ/9Gz8vvgL
exLuGJgxEvQgF1L3sAwrLsRwneOSsHK2+ccnsGho8Gwu/tXtBRFBXPsNpS6DYJhz
72+jPFAJksDgiBFXaHPNLEsIN4i+dF1ye3ftDZb093GFcAGrenjzNtbWlo7yJLTS
0MiATHWAOiplUjy15DSMst6tOAUVJX6lRkLXXu9NPXZIGRrR12qMgVYemgxt7J0=
=7BIA
-----END PGP SIGNATURE-----

Albin Otterhäll

unread,
Jun 12, 2016, 6:23:35 PM6/12/16
to qubes...@googlegroups.com
Marek Marczykowski-Górecki:
> On Sun, Jun 12, 2016 at 05:46:34PM +0000, Albin Otterhäll wrote:
>> Marek Marczykowski-Górecki:
>>> security-testing - subset of "current-testing" that is qualified as
>>> security fixes
>
>> If I enable "current-testing", do I receive the same updates and at the
>> same time as "security-testing", or should I enable both of them?
>
> Yes, security fixes are uploaded to both of them.
>
>

Do I need to do something else other than just enable the
"current-testing" and do a update in dom0? E.g. KDE5 will come
automatically?

Marek Marczykowski-Górecki

unread,
Jun 12, 2016, 7:23:36 PM6/12/16
to Albin Otterhäll, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Jun 12, 2016 at 10:23:16PM +0000, Albin Otterhäll wrote:
> Marek Marczykowski-Górecki:
> > On Sun, Jun 12, 2016 at 05:46:34PM +0000, Albin Otterhäll wrote:
> >> Marek Marczykowski-Górecki:
> >>> security-testing - subset of "current-testing" that is qualified as
> >>> security fixes
> >
> >> If I enable "current-testing", do I receive the same updates and at the
> >> same time as "security-testing", or should I enable both of them?
> >
> > Yes, security fixes are uploaded to both of them.
> >
> >
>
> Do I need to do something else other than just enable the
> "current-testing" and do a update in dom0? E.g. KDE5 will come
> automatically?

KDE5 is part of Qubes 3.2, not 3.1. Enabling current-testing repository
will not give you next Qubes version automatically, this upgrade still
needs to be done explicitly. (There is no upgrade path 3.1->3.2 yet).

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXXe7wAAoJENuP0xzK19cswH4H/jmDdUz5rvH57RxofrPKfyQ7
SB9lOyMZS8zTcxwF1q2ZkkUWq+RK1wss1EUOJo14YFeZFo+o4AMVHUG0XlomrjOk
dCXq4M6lgBX9AA1LcXWqMLtuWWL6dlYotFA9rNatIg/8n5Att4seXQwaeuKcdvT0
QV4vqeRtfTq8FUG9BgdaE6gmObVKTggujePdMVDJ5shE+vOs6lNuoWElb2TJULns
SvS31yVUsfu686o+NvjTxB4ng9ItSd3uxKQ0lrSydFh5fwf9Zr512pPqGfTWucd/
iZy1sXB+7JIrS3ZFw+2nWmFk6BBqVM32Ke4Nqj8KaYN7hCW+QhfTpviRT4lx8/o=
=Q6a5
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages