4.0 "current" in dom0 but "current-testing" in Fed26 based AppVM?

[john]

Hello, when I look at that "boolean" in /etc/yum.repos.d/qubes-dom0.repo

of the 4 choices the Only enabled = 1 is the 1st one "current"

so is it expected that in Fed26 based AppVMs that I will see 90% of the

$sudo dnf list installed qubes-* packages actually say "current-testing" ?



I actually installed 4.0rc5 just before it became 4.0, and have done a
dom0 update successfully


I'd like to avoid problems, so what if anything should I do if this is
not correct?


The system is very stable at present ....



--

[awokd]

On Tue, May 1, 2018 5:36 pm, john wrote:
> Hello, when I look at that "boolean" in /etc/yum.repos.d/qubes-dom0.repo

This file only applies to updates for dom0, not templates. You need to
look inside each template's repo settings (and probably disable testing if
it's enabled). See Testing Repositories under
https://www.qubes-os.org/doc/software-update-vm/.

[john]

thanks for responding, so in the Fed-26 template
sudo dnf list installed qubes-*
shows most of the packages as "current-testing" but

in Fed-26's /qubes-r4.repo only "current" has an enabled=1

not "current-testing"


so, am I getting updates to "current-testing" or "current" or If I
prefer "current" how would I fix this ?


I'll go read the URL you provided also :0

[awokd]

On Wed, May 2, 2018 7:54 am, john wrote:

>
> thanks for responding, so in the Fed-26 template sudo dnf list installed
> qubes-* shows most of the packages as "current-testing" but
>
> in Fed-26's /qubes-r4.repo only "current" has an enabled=1
>
> not "current-testing"
>
>
> so, am I getting updates to "current-testing" or "current" or If I
> prefer "current" how would I fix this ?

You're all set then- you are getting updates for "current" only. You must
have manually updated to testing at some point. Now it's just a matter of
waiting until the packages released at "current" supersede the ones you
updated earlier from testing. If you want to force it, you could reinstall
the template but I'd just wait unless you are having problems from one of
the testing packages.