Is Qubes R3.2 still in testing branch?

Pawel Debski

unread,

Oct 16, 2016, 2:21:34 PM10/16/16

to qubes-users

Folks,

I'm planning R3.1 -> 3.2 upgrade and need explanation:

sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2 qubes-release

why do I need to enable testing repo? I thought that R3.2 has already been released as stable.

Maybe I do not understand something. Please explain.

--

Z powazaniem / Best Regards
Mit freundlichen Gruessen / Meilleures salutations
Pawel Debski

Marek Marczykowski-Górecki

unread,

Oct 16, 2016, 5:22:41 PM10/16/16

to Pawel Debski, qubes-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Oct 16, 2016 at 08:21:17PM +0200, Pawel Debski wrote:
> Folks,
>
> I'm planning R3.1 -> 3.2 upgrade and need explanation:
>
> |sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2
> qubes-release|
>
> why do I need to enable testing repo? I thought that R3.2 has already been
> released as stable.

You're right, testing repo is no longer needed. Instruction fixed.

- --
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

iQEcBAEBCAAGBQJYA++hAAoJENuP0xzK19csCFAH/2IlqrV0uzkOnMu9CBpAKx/n
bofjVit0X9IPIShAw5vHCityCyrjPNlCm7WeCpwtFCYdbYnTfZ3JYt/r7xbfgJsb
yW1RU2C1tFBSfLpFKaEf6q1Eg4PuNJtu3yLx2JcrBteZBuBLLauFAtEYgp5U9dnS
7cCwUeb6LEdBP3YTWU61YYHaZTwIeSWlVJfTCeh+O1D1YNAIF7AiIDf8raJq+tgA
I89pNUIFzB8QEpxGPkXT7VNDgzlHcYx8pbh8wLL9wODGtr4DtbIaQPB9dsg4cqS8
jY5dYJ0d1omo9hy9zp2yze2HkMwd8JYdB0wiZsnqwxplJIM1RJnRjXG9CQSW/wo=
=Ih/R
-----END PGP SIGNATURE-----

Pawel Debski

unread,

Oct 17, 2016, 1:51:51 AM10/17/16

to Marek Marczykowski-Górecki, qubes-users

On 2016-10-16 23:22, Marek Marczykowski-Górecki wrote:

On Sun, Oct 16, 2016 at 08:21:17PM +0200, Pawel Debski wrote:

Folks,

I'm planning R3.1 -> 3.2 upgrade and need explanation:

|sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2
qubes-release|

why do I need to enable testing repo? I thought that R3.2 has already been
released as stable.

You're right, testing repo is no longer needed. Instruction fixed.

The thing is, that I was getting errors until I enabled testing repo. With --enablerepo=qubes*testing the upg went on.

Andrew David Wong

unread,

Oct 17, 2016, 2:40:03 AM10/17/16

to Pawel Debski, Marek Marczykowski-Górecki, qubes-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-10-16 22:51, Pawel Debski wrote:
> On 2016-10-16 23:22, Marek Marczykowski-Górecki wrote:
>> On Sun, Oct 16, 2016 at 08:21:17PM +0200, Pawel Debski wrote:
>>> Folks,
>>>
>>> I'm planning R3.1 -> 3.2 upgrade and need explanation:
>>>
>>> |sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2
>>> qubes-release|
>>>
>>> why do I need to enable testing repo? I thought that R3.2 has already been
>>> released as stable.
>> You're right, testing repo is no longer needed. Instruction fixed.
>
> The thing is, that I was getting errors until I enabled testing repo. With --enablerepo=qubes*testing the upg went on.
>

What errors did you get?

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

iQIcBAEBCgAGBQJYBHI2AAoJENtN07w5UDAwdaoP+wXrdSOLHhdnVuhOCTsJsJr6
HmxjFry58fMhhqNr4yhVTfOt5UbuN/HCXTGXaIF2qy/Qp6pswZJpLKEvaypRdyxH
PSpmjkbQgwwMY1JUD/+PJm1fn7y0iSy0+QvBdvlug/1mcpAc03A/Ajyl8bSkdRMb
AFWo18pXoz9nAYemOaUvCbMcmJSdkO07hAYLCrPs970tS2ByXPzh8GCyvMnJa2tc
PyHA9GPVsfLzORojj/6TfeAmCiup/gPwdz0f7Fb9fJhOwBrcZ4elQib5UsNePAEY
Fg5+7wGHD8s4FtKGD4kbeccvSOux8QNWzJgkNNv8oZQvxTh59plNs+4gYcldOHlT
3OAzc2uyXT5PEhn25bVdH3Nc3urTPKabjJlf5dfjFLSBckmM5Nur/uDNf4lEvD/2
yyB1L1JEpY1ZsrmYePHwk2EEc55bm6MkTay66FwiklumG32gwLzqrFqu7T7pxrHl
+Pap9p0APU9KYb6EAg4IPmVeZTjdvOgtmnELBhXWlG3zH7QlMX4zPHYeTwiKX9pp
SuGS5qfZeYSUmaxmqFLCQrmbF7365sDqvNMIHOX/RZ6pubNzFT85dFjjeHl0Aiz5
mWHmbYIz4VF6tkZvEuilhxKdoqXMHyPmNB8zUYp/vVVoZwHJ/m2Z8YEWwyIPn9Zr
bchocc2E+CVhmU6mhoXL
=d0iS
-----END PGP SIGNATURE-----

Pawel Debski

unread,

Oct 17, 2016, 4:20:16 AM10/17/16

to Andrew David Wong, Marek Marczykowski-Górecki, qubes-users

On 2016-10-17 08:39, Andrew David Wong wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-10-16 22:51, Pawel Debski wrote:

On 2016-10-16 23:22, Marek Marczykowski-Górecki wrote:

On Sun, Oct 16, 2016 at 08:21:17PM +0200, Pawel Debski wrote:

Folks,

I'm planning R3.1 -> 3.2 upgrade and need explanation:

|sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2
qubes-release|

why do I need to enable testing repo? I thought that R3.2 has already been
released as stable.

You're right, testing repo is no longer needed. Instruction fixed.

The thing is, that I was getting errors until I enabled testing repo. With --enablerepo=qubes*testing the upg went on.

What errors did you get?

About packages not existing in repo. As I've already run first stage of the upg with --enablerepo=qubes*testing the exact errors are hard to recollect. My assumption (perhaps wrong) was that the packages are still in testing repo.

Is there any log file I can paste the errors from?

Reply all

Reply to author

Forward