Any news on 4.0.2-rc2?
119 views
Skip to first unread message
Claudia
Nov 1, 2019, 9:56:04 AM11/1/19
to qubes-users
re: https://www.mail-archive.com/qubes...@googlegroups.com/msg30379.html
So as I understand, there were two problems with rc1. Bug #5149, which
was closed as resolved three days ago. And an unknown "pending security
issue".
Where can we find more info on this pending security issue? I don't see
a QSB around the time that message was posted (Sept 2 2019).
Are there any updates regarding the release of rc2? And, is there any
way we can track its progress? Github doesn't seem to have milestones
for point releases, much less rc's.
According to the Qubes release schedule, exactly five weeks after an rc
comes out, either another rc or a stable should follow. Seeing as how
rc1 was announced July 9, it would seem we're long overdue.
The reason I ask is because I ran into problems bringing 4.0.1 up to
date, but I thought "oh well, by the time I get this figured out,
4.0.2(-rc2, at least) will be out anyways. Might as well wait and start
fresh." But now nearly 4 months later, here we sit.
I appreciate all the hard work that goes into every release. Just asking
if there are any status updates, that's all.
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
So as I understand, there were two problems with rc1. Bug #5149, which
was closed as resolved three days ago. And an unknown "pending security
issue".
Where can we find more info on this pending security issue? I don't see
a QSB around the time that message was posted (Sept 2 2019).
Are there any updates regarding the release of rc2? And, is there any
way we can track its progress? Github doesn't seem to have milestones
for point releases, much less rc's.
According to the Qubes release schedule, exactly five weeks after an rc
comes out, either another rc or a stable should follow. Seeing as how
rc1 was announced July 9, it would seem we're long overdue.
The reason I ask is because I ran into problems bringing 4.0.1 up to
date, but I thought "oh well, by the time I get this figured out,
4.0.2(-rc2, at least) will be out anyways. Might as well wait and start
fresh." But now nearly 4 months later, here we sit.
I appreciate all the hard work that goes into every release. Just asking
if there are any status updates, that's all.
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
Bill Oliver
Nov 1, 2019, 2:39:59 PM11/1/19
to qubes...@googlegroups.com
Funny you should say that. I've done the same thing! I had some
hassles trying to upgrade, and thought to myself "Well, screw it. I'll
just install Kubuntu for now and wait for 4.0.2 to come out." And it
never did. I still have faith, don't get me wrong, and I'm not the
kind of ass who would complain because smart people who are doing great
work for free aren't pandering to me enough, but yeah. I'm kinda
sitting on my hands here, too.
billo
hassles trying to upgrade, and thought to myself "Well, screw it. I'll
just install Kubuntu for now and wait for 4.0.2 to come out." And it
never did. I still have faith, don't get me wrong, and I'm not the
kind of ass who would complain because smart people who are doing great
work for free aren't pandering to me enough, but yeah. I'm kinda
sitting on my hands here, too.
billo
Franz
Nov 1, 2019, 7:14:58 PM11/1/19
to Claudia, qubes-users
Where can we find more info on this pending security issue? I don't see
a QSB around the time that message was posted (Sept 2 2019).
Well Claudia it seems pretty obvious that we do not want to publish any information about an unresolved security issue. Also we do not want to stress our much loved developers who already do miracles. So dear Claudia, use the present release, be very happy and do not waste your time worrying about things like this :-))
Andrew David Wong
Nov 3, 2019, 3:45:11 AM11/3/19
to Claudia, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2019-10-31 10:01 AM, Claudia wrote:
> re:
> https://www.mail-archive.com/qubes...@googlegroups.com/msg30379.html
>
> So as I understand, there were two problems with rc1. Bug #5149,
> which was closed as resolved three days ago. And an unknown
> "pending security issue".
>
> Where can we find more info on this pending security issue? I don't
> see a QSB around the time that message was posted (Sept 2 2019).
>
> Are there any updates regarding the release of rc2? And, is there
> any way we can track its progress? Github doesn't seem to have
> milestones for point releases, much less rc's.
>
> According to the Qubes release schedule, exactly five weeks after
> an rc comes out, either another rc or a stable should follow.
> Seeing as how rc1 was announced July 9, it would seem we're long
> overdue.
>
> The reason I ask is because I ran into problems bringing 4.0.1 up
> to date, but I thought "oh well, by the time I get this figured
> out, 4.0.2(-rc2, at least) will be out anyways. Might as well wait
> and start fresh." But now nearly 4 months later, here we sit.
>
> I appreciate all the hard work that goes into every release. Just
> asking if there are any status updates, that's all.
>
Hi Claudia,
We actually just uploaded the 4.0.2-rc2 ISO to
https://ftp.qubes-os.org/iso/ a couple days ago. We're just preparing
the announcement and letting the mirrors catch up. We plan to publish
that announcement within the next 24 hours.
I'll check with the security team about that pending security issue.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl2+k4YACgkQ203TvDlQ
MDBd5A//RxncbnD/kiEmng4jkN4tLXWl5Nz1oFXG7JZF56gnaJ2W6Hu7lSSHmBiR
ZNkJpS41m63ktzvr+g7Vo4hV0QTel18g8AK4YpB/6s3IiQr313IiJz7iXWS8bZj7
YqyoQ1ZBLpHhf+C3lxGYMUK1MK+KRnytiCPX4ltY/t9Ecmrsn2p4PMsWxeyWnx/t
YSICiXxkjmeMNbXpXlIh0LWgD0KgtlB2adl8dXq2+KcxCU/8dXbqD+hheKe7k8B6
1Pf5u3ON6CrKqOuxMBEr7t69q2w5wwDxLOJYuQainXR9FVzV8WeppUhxyG8aTmEH
dJjtTh0mRunxhWV3Hp9Ji3Qh0rGwEu2wVo6PTRRB+SX0xbBvklUpmQHTA+inW4V+
LRnHAPD6toUBC8E0B6vlaJlXHsZUaIM1kkd1ERH4jeQP1G6+5zBq0L37PGCIUumD
iTaqXWo8w0lN1BGDYfq3DPyIZvtUXxPsc+0E9zXWKI/0McrVXiWvSk/lLNS5ih/b
BH1ERXfwwjyJuIBx+Xy0BCcjUc+7Q9vYqCU3uN5+5BvZdI/8rxjlfN/VcMA6rCZc
bhWMDGH5jtArdPKq7Z0uCOsbO6pgDPMNf43u0lC34WAEYUB4M1OSn5MwXt9ILQNl
iboTT7k78TpbhCM/tEkVdu51wNFwW2SiwoExvKUhcoM7ctaIQ/0=
=9NRF
-----END PGP SIGNATURE-----
Hash: SHA512
On 2019-10-31 10:01 AM, Claudia wrote:
> re:
> https://www.mail-archive.com/qubes...@googlegroups.com/msg30379.html
>
> So as I understand, there were two problems with rc1. Bug #5149,
> which was closed as resolved three days ago. And an unknown
> "pending security issue".
>
> Where can we find more info on this pending security issue? I don't
> see a QSB around the time that message was posted (Sept 2 2019).
>
> Are there any updates regarding the release of rc2? And, is there
> any way we can track its progress? Github doesn't seem to have
> milestones for point releases, much less rc's.
>
> According to the Qubes release schedule, exactly five weeks after
> an rc comes out, either another rc or a stable should follow.
> Seeing as how rc1 was announced July 9, it would seem we're long
> overdue.
>
> The reason I ask is because I ran into problems bringing 4.0.1 up
> to date, but I thought "oh well, by the time I get this figured
> out, 4.0.2(-rc2, at least) will be out anyways. Might as well wait
> and start fresh." But now nearly 4 months later, here we sit.
>
> I appreciate all the hard work that goes into every release. Just
> asking if there are any status updates, that's all.
>
We actually just uploaded the 4.0.2-rc2 ISO to
https://ftp.qubes-os.org/iso/ a couple days ago. We're just preparing
the announcement and letting the mirrors catch up. We plan to publish
that announcement within the next 24 hours.
I'll check with the security team about that pending security issue.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl2+k4YACgkQ203TvDlQ
MDBd5A//RxncbnD/kiEmng4jkN4tLXWl5Nz1oFXG7JZF56gnaJ2W6Hu7lSSHmBiR
ZNkJpS41m63ktzvr+g7Vo4hV0QTel18g8AK4YpB/6s3IiQr313IiJz7iXWS8bZj7
YqyoQ1ZBLpHhf+C3lxGYMUK1MK+KRnytiCPX4ltY/t9Ecmrsn2p4PMsWxeyWnx/t
YSICiXxkjmeMNbXpXlIh0LWgD0KgtlB2adl8dXq2+KcxCU/8dXbqD+hheKe7k8B6
1Pf5u3ON6CrKqOuxMBEr7t69q2w5wwDxLOJYuQainXR9FVzV8WeppUhxyG8aTmEH
dJjtTh0mRunxhWV3Hp9Ji3Qh0rGwEu2wVo6PTRRB+SX0xbBvklUpmQHTA+inW4V+
LRnHAPD6toUBC8E0B6vlaJlXHsZUaIM1kkd1ERH4jeQP1G6+5zBq0L37PGCIUumD
iTaqXWo8w0lN1BGDYfq3DPyIZvtUXxPsc+0E9zXWKI/0McrVXiWvSk/lLNS5ih/b
BH1ERXfwwjyJuIBx+Xy0BCcjUc+7Q9vYqCU3uN5+5BvZdI/8rxjlfN/VcMA6rCZc
bhWMDGH5jtArdPKq7Z0uCOsbO6pgDPMNf43u0lC34WAEYUB4M1OSn5MwXt9ILQNl
iboTT7k78TpbhCM/tEkVdu51wNFwW2SiwoExvKUhcoM7ctaIQ/0=
=9NRF
-----END PGP SIGNATURE-----
Claudia
Nov 3, 2019, 1:45:48 PM11/3/19
to qubes...@googlegroups.com
Andrew David Wong:
That's great news! Thank you!
Question: Is there anything we need to be aware of when installing
rc's/betas, with regards to upgrading?
As I understand, if rc2 ultimately becomes 4.0.2 stable, then rc2 users
don't have to reinstall to upgrade to stable (they would be the same ISO
anyway). All they have to do is install updates. Is that right?
The same is true even if an rc3 comes out, right? No need to reinstall
from ISO, just install updates?
Is only time you need to reinstall from ISO when upgrading a minor
release? e.g. 4.0 -> 4.1?
Thanks
Question: Is there anything we need to be aware of when installing
rc's/betas, with regards to upgrading?
As I understand, if rc2 ultimately becomes 4.0.2 stable, then rc2 users
don't have to reinstall to upgrade to stable (they would be the same ISO
anyway). All they have to do is install updates. Is that right?
The same is true even if an rc3 comes out, right? No need to reinstall
from ISO, just install updates?
Is only time you need to reinstall from ISO when upgrading a minor
release? e.g. 4.0 -> 4.1?
Thanks
seshu
Nov 3, 2019, 4:21:28 PM11/3/19
to qubes-users
And to follow on, is there a way to tell if I have 4.0 or 4.0.1 or 4.02rc2?
Thanks!
awokd
Nov 3, 2019, 6:56:28 PM11/3/19
to qubes...@googlegroups.com
> And to follow on, is there a way to tell if I have 4.0 or 4.0.1 or
4.02rc2?
If it's like previous releases, if you have Qubes 4 patched to the
4.02rc2?
"current" (default) repository, you are running the latest point release
(4.0.1). If you have it patched to "current-testing", you're running the
current rc.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
seshu
Nov 3, 2019, 7:04:06 PM11/3/19
to qubes-users
Ok, that is right. i forgot that. Thanks!
Andrew David Wong
Nov 4, 2019, 12:44:58 AM11/4/19
to Claudia, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hash: SHA512
fact, QSB #051:
https://www.qubes-os.org/news/2019/09/10/qsb-051/
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
MDBu1w//QTH76b0HFPf2MHr4OlXY4EIsPa2ZxCX6XX30SZ4ANe88LxR+vqf08uKg
mTgYTXWwaMBabGj+uAe6Ynq5XwQsGIwP7jsvdF39D0/L7pZsn+OWXtIx/vQyd+uL
EA9GBkgn1ycmOyGNLyNkqgrnLqsPRPxBMcvHoN1X+PtxJ5wl/cl8bKuTqgf14RpB
fs85SYpB9UZhqkGLKW6vA6j5BPOXEWm3GlYPBGxDgah3oHw4tsKgiM+F+x6qNTua
dSFx2aso6MsBlUORFKzeMIRPlqAiE0DQXvO7Vitw/HlCS5kmHiStwngfWeLRsoYm
Z7XyFEmxi3ONVWXkbfBl8jtDm0+A9qGJbEeAw3fmcyd2cwveUmafPOU/snae/4j4
qc/9m+b79MVmBCWGzLLaYcNIvPKaPHoeeGSMEdmy8phkOGRZ0H9SXAihLiGxqTsf
GHQoo5/Nd8/wYMq7bSgPYQQOAuRC9dbk5g9R38F3bMMSzJhkO/Snaa4T+uz9LLjO
ZsyVtzwXfXwoPnDj8B5IrPzcQEvq+mFcvcExIRvXs+Gz0nb0TI5ovtLM6JWifh0Y
Ltlkw1U4XsJSehEb/rihebqQx6go/cXdU+tMQ6qn1ncICRzkfLOigjTDBdjfad9J
zR5dflqX230ORFVQUG4Rsbxqy+7k/vWH04uAT+gxx0iNd5LZUmw=
=3Ffx
-----END PGP SIGNATURE-----
Andrew David Wong
Nov 4, 2019, 12:51:47 AM11/4/19
to Claudia, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2019-11-01 12:16 PM, Claudia wrote:
Hash: SHA512
> Andrew David Wong: On 2019-10-31 10:01 AM, Claudia wrote:
>> [...]
>
> Question: Is there anything we need to be aware of when installing
> rc's/betas, with regards to upgrading?
>
> As I understand, if rc2 ultimately becomes 4.0.2 stable, then rc2
> users don't have to reinstall to upgrade to stable (they would be
> the same ISO anyway). All they have to do is install updates. Is
> that right?
>
Yes, if a release candidate is found to be good enough to be declared
> Question: Is there anything we need to be aware of when installing
> rc's/betas, with regards to upgrading?
>
> As I understand, if rc2 ultimately becomes 4.0.2 stable, then rc2
> users don't have to reinstall to upgrade to stable (they would be
> the same ISO anyway). All they have to do is install updates. Is
> that right?
>
the stable release, then it is essentially just renaming what already
exists. In such cases, we state this in the stable release announcement.
> The same is true even if an rc3 comes out, right? No need to
> reinstall from ISO, just install updates?
>
> Is only time you need to reinstall from ISO when upgrading a minor
> release? e.g. 4.0 -> 4.1?
>
> Thanks
>
ideal scenario, and it is often achievable, but not always. In some
cases, a clean installation may be necessary (or strongly
recommended), depending on the changes made between release candidates.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
MDCq6hAArAfnc0q1Q7GLKQ+7UFXvzPUKyKnERzwr6wUUo3w8RMNrFrOO5UtQMWe1
Cbp0oZjW0BYSatAb5xD9Qf+SXG074i3ywA3JgfQ3jt4d3gVXl8luKXq8bxBTtssb
Z+gpHsSc7oXRELSwb4HtIFKOZoDx+IouTRMuSHyv7C0Y6NR10mKJigf12jBnO4rP
WXM4XQTd6z1ljfldfkfolit0OPyWJ0efiHi7jUuIl/0PZagk4AMZSlCqTnEwHwz3
bAEkBFLlPpRXsrBa+Xf7Oo27yQKTKccUmFN7CT1L223p60fIwNUjnPNnkepwdRC4
P6Lh/ngrfxa3QmiDScCUnoyqA+u7ITQzddaWMPeedhUiJkuatR6zdHdnU/aFIdUd
KHy5KfQRGpC+Tt5WjiagkEUgaN5TllH6OngLGUzG6ZJK0l1Beb5XfUr4MVhZP5Sv
RpVSnRzgLtT+oMBOpWUloANaR8rSh+lN1LDczPhHps5jYmk4rYm47CPXjkH0eqst
stCskCASW4G1ZHPGLWQKcJIEsiHio1Tdmoaz3anqqEd8XQqMNsULlugE+1JoEo6C
CNkPbQCq4vxXgKGiUPYiVxelbhZZKDYOcBEog4hp30xDDSmVu7w2Bv/lnV7E9Rpe
Eg/IHpE1307W7AT2NWEA3yVztnkZcTv9j5hsYwl8NFZzftxxKsA=
=Sm1o
-----END PGP SIGNATURE-----
Andrew David Wong
Nov 4, 2019, 12:52:46 AM11/4/19
to seshu, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hash: SHA512
On 2019-11-03 6:04 PM, seshu wrote:
> Ok, that is right. i forgot that. Thanks!
>
> On Sunday, November 3, 2019 at 11:56:28 PM UTC, awokd wrote:
>>
>>> And to follow on, is there a way to tell if I have 4.0 or 4.0.1
>>> or
>> 4.02rc2?
>>
>> If it's like previous releases, if you have Qubes 4 patched to
>> the "current" (default) repository, you are running the latest
>> point release (4.0.1). If you have it patched to
>> "current-testing", you're running the current rc.
>>
Yes, awokd is correct. A point release does not designate a separate,
> Ok, that is right. i forgot that. Thanks!
>
> On Sunday, November 3, 2019 at 11:56:28 PM UTC, awokd wrote:
>>
>>> And to follow on, is there a way to tell if I have 4.0 or 4.0.1
>>> or
>> 4.02rc2?
>>
>> If it's like previous releases, if you have Qubes 4 patched to
>> the "current" (default) repository, you are running the latest
>> point release (4.0.1). If you have it patched to
>> "current-testing", you're running the current rc.
>>
new version of Qubes OS. Rather, it designates its respective major or
minor release (in this case, 4.0) inclusive of all updates up to a
certain point. Installing Qubes 4.0 and fully updating it results in
the same system as installing Qubes 4.0.2.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
MDAUeg/9HzfPw46VqrSvkinaXKHIpBz1o23piQJGxSH2PptRAJULkIMRhCOEPIIp
eJPcqp74p2b+llXmIueu/5ZXYsUQCULehh1ti2GdIhBB6iX5pEWuJYC7PvgOW6wu
jSaR6n7LbL4kw7OtYIIqieGcBwN0/K+72K0qI7YNJCQzPN7Ea/YdtavDQwyJMiER
CwccE/gmc4ujMX7M1EXhZtxR1eemIpNeQMnX/uylDA+AMmmfOG9jOlhM7Z57g5P3
ceEe0SU2KsJ64H+mSYNSFNjLKoZGzSO6l036oZT2I6OefGO03gGq4XmLdi33VZqA
6OBGVWjN9/RIrMzb2nWc0wNKoWHHkoep2WWZtBKVU+w/niJSkS00ga1shz1fRSWv
/HCZIllvSoGcYPJgd7eKF3yZT46dC3n0hxVDtHNMDmNh88DMBdU5xQhM6eB/+7bS
+CtlvsPlUw9KOvVxgT4s8X4xLiuuAjI4ox2x58m1NKSao3D0gC307+Srqw4QGDxG
JoGJmZdyAfXnPg55ytWyYnKxHqB8AfsYx+AbzqKy4P1b6CqIXQDvaD7W5I6R/yQh
TEFUX/whzMUpTt6b+p3waeNyIsGAbHCpWRPcOygTf47bRPrYd+j7fyfozjlqSVwr
363Z0zr6u2g4Kbwn6u4EfumrxmbzrNo7gx9oXZZ9ox9GCmIZ5/c=
=B9Oo
-----END PGP SIGNATURE-----
Claudia
Nov 4, 2019, 6:54:37 AM11/4/19
to qubes...@googlegroups.com
'awokd' via qubes-users:
enables the "current" (default) repo. However, if I install from an rc
ISO, does that enable "current-testing" repo?
My feeling is that it must, because otherwise you'd be installing
"current-testing" packages from ISO, but then updating from the
"current" repo. Installed packages would be newer than updates.
If that's the case, then installing from an rc is actually different
than installing from stable, because the former results in a system
using "current-testing" instead of "current". But then this is contrary
to saying that an rc declared stable is identical to the resulting
stable release.
So, say I install rc2, and in five weeks it is declared stable. If I
want to use a stable system, do I have to manually switch the repo over
to "current"?
>> And to follow on, is there a way to tell if I have 4.0 or 4.0.1 or
> 4.02rc2?
>
> If it's like previous releases, if you have Qubes 4 patched to the
> "current" (default) repository, you are running the latest point release
> (4.0.1). If you have it patched to "current-testing", you're running the
> current rc.
>
This got me thinking... If I install 4.0.1 from ISO, it of course
> 4.02rc2?
>
> If it's like previous releases, if you have Qubes 4 patched to the
> "current" (default) repository, you are running the latest point release
> (4.0.1). If you have it patched to "current-testing", you're running the
> current rc.
>
enables the "current" (default) repo. However, if I install from an rc
ISO, does that enable "current-testing" repo?
My feeling is that it must, because otherwise you'd be installing
"current-testing" packages from ISO, but then updating from the
"current" repo. Installed packages would be newer than updates.
If that's the case, then installing from an rc is actually different
than installing from stable, because the former results in a system
using "current-testing" instead of "current". But then this is contrary
to saying that an rc declared stable is identical to the resulting
stable release.
So, say I install rc2, and in five weeks it is declared stable. If I
want to use a stable system, do I have to manually switch the repo over
to "current"?
Andrew David Wong
Nov 5, 2019, 11:11:18 PM11/5/19
to Claudia, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hash: SHA512
On 2019-11-02 9:41 AM, Claudia wrote:
> 'awokd' via qubes-users:
>>> And to follow on, is there a way to tell if I have 4.0 or 4.0.1
>>> or
>> 4.02rc2?
>>
>> If it's like previous releases, if you have Qubes 4 patched to
>> the "current" (default) repository, you are running the latest
>> point release (4.0.1). If you have it patched to
>> "current-testing", you're running the current rc.
>>
>
> This got me thinking... If I install 4.0.1 from ISO, it of course
> enables the "current" (default) repo. However, if I install from an
> rc ISO, does that enable "current-testing" repo?
>
> My feeling is that it must, because otherwise you'd be installing
> "current-testing" packages from ISO, but then updating from the
> "current" repo. Installed packages would be newer than updates.
>
> If that's the case, then installing from an rc is actually
> different than installing from stable, because the former results
> in a system using "current-testing" instead of "current". But then
> this is contrary to saying that an rc declared stable is identical
> to the resulting stable release.
>
>
>
> So, say I install rc2, and in five weeks it is declared stable. If
> I want to use a stable system, do I have to manually switch the
> repo over to "current"?
>
I asked Marek about this. Here is his reply:
> 'awokd' via qubes-users:
>>> And to follow on, is there a way to tell if I have 4.0 or 4.0.1
>>> or
>> 4.02rc2?
>>
>> If it's like previous releases, if you have Qubes 4 patched to
>> the "current" (default) repository, you are running the latest
>> point release (4.0.1). If you have it patched to
>> "current-testing", you're running the current rc.
>>
>
> This got me thinking... If I install 4.0.1 from ISO, it of course
> enables the "current" (default) repo. However, if I install from an
> rc ISO, does that enable "current-testing" repo?
>
> My feeling is that it must, because otherwise you'd be installing
> "current-testing" packages from ISO, but then updating from the
> "current" repo. Installed packages would be newer than updates.
>
> If that's the case, then installing from an rc is actually
> different than installing from stable, because the former results
> in a system using "current-testing" instead of "current". But then
> this is contrary to saying that an rc declared stable is identical
> to the resulting stable release.
>
>
>
> So, say I install rc2, and in five weeks it is declared stable. If
> I want to use a stable system, do I have to manually switch the
> repo over to "current"?
>
"Basically the answer is 'current-testing' is disabled by default,
even in rc builds. This may mean some packages on the rc installation
image are newer than those in the stable repository, but the update
mechanism won't try to downgrade them. In practice, there are usually
very few changes affected by such a difference, as we do migrate as
much packages as possible to stable prior to building the ISO."
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
MDC6uQ//f0pBI+k1GK3xjhIEF07K2+2uJn92yUhSvzjglsFO2mLQHa/YuaYJHeFO
+TgQSbsRQDLSGFX1VBM8YRjI9tpbPhF3AOWNUL7JfNI21g4w3fth2J4eSAGmrEnh
mFUfXIiYZYbBZbr+Asm0Y9U8ButCSkQVIbUbSpnYewjr131XvNfC6ASg/PtVmcO7
i3+lkat/owRCGci2MxUCafBurvb8mV2PMVbGALhFAkX0pWCzBsX9AGug3ZMvXRsN
A1CHVqFCHLDc3B7JnXIqt6HbhCU8ctrP5MMguAZ2JkFyhdZ1Yqt0VNoCokbS2kVX
5rbYaTJghK6fN4TbCbxqPdK+SWNO30N61Iw6bnm4U8FhVZsX/BM2gQIiFsznz7J6
jpqv09WcsCXFnMzlwajyIRzQBUGI3M//ZlCHIUaZpsUrPOABzmJOOnfDruBONxXZ
ojORqzY1xiWsIn4xQdsLY2UoAG9Cs8D1JvAB1YXOQaJZDVb4WNyxhgUnB26qo8cb
M9LK6FZHtlM+i4xRIkFkK2Qz+O0VLOPF7edwb+37AvTj9/dNmVdorF6pLJisee5M
9nfqngEPg+D76aqimn24H7tQy5z6KtBu5l257dd9SNdbqCqeGn6p/lGC8UyrdBc0
GzVcgbIQxwx5toTVQf5Sw6RHbf+dZo1pAe+ybPN3qHyyDI96oiU=
=CxJF
-----END PGP SIGNATURE-----
Claudia
Nov 6, 2019, 7:49:20 AM11/6/19
to qubes...@googlegroups.com
Andrew David Wong:
> I asked Marek about this. Here is his reply:
>
> "Basically the answer is 'current-testing' is disabled by default,
> even in rc builds. This may mean some packages on the rc installation
> image are newer than those in the stable repository, but the update
> mechanism won't try to downgrade them. In practice, there are usually
> very few changes affected by such a difference, as we do migrate as
> much packages as possible to stable prior to building the ISO."
Ah, that makes sense. Thanks!
>
> "Basically the answer is 'current-testing' is disabled by default,
> even in rc builds. This may mean some packages on the rc installation
> image are newer than those in the stable repository, but the update
> mechanism won't try to downgrade them. In practice, there are usually
> very few changes affected by such a difference, as we do migrate as
> much packages as possible to stable prior to building the ISO."
Reply all
Reply to author
Forward
0 new messages