Trouble updating templates

[sevas]

I cant seem to update my templates.

In the debian-9 TVM I type:

sudo apt-get update
Ign:1 http://.....
Ign:2 http://.....
Ign:3 http://.....
Err:4
Err:5
Err:6 Connection Failed

E: The repo "http://..." does no longer have a Release File.
N: Updating from such a repo cant be done securely, and is therefore disabled by default.
N: See apt-secure man page.

The Fedora template doesnt seem to connect at all.

My sys-firewall is using the debian-9 template.
Type: AppVM
Rules: Allow all outgoing
Devices: none
services: n/a

The sys-net (debian-9)
Type: AppVM
Rules: n/a
Devices: Network Controller
services: clocksync

[awokd]

On Sun, March 4, 2018 7:01 am, sevas wrote:
> I cant seem to update my templates.

>

> E: The repo "http://..." does no longer have a Release File.
> N: Updating from such a repo cant be done securely, and is therefore
> disabled by default. N: See apt-secure man page.

You will get the "no release file" message when the repo is down for
updates. Only thing to do is try again later.

> The Fedora template doesnt seem to connect at all.

Check the template logs in the build-logs directory for more detailed
messages.

[sevas]

That helped.

journalctl -f in dom0 returned a block in the rpc-policy.

dom0: nano /etc/qubes-rpc/policy/qubes-UpdatesProxy

I had to change the name of my primary sys-net to the name I provided my default sys-net.

Thats what I get for going and changing things around.

Solved. Thanks!

[sevas]

ooh I spoke too soon. Its not working. Its helping! But....

journalctl returns:
Template > allowed to sys-net

Fedora template says failed to synchronize cache for repo "updates"
Debian says the same as it did previously.

And next to the "state" entry of the Qubes Manager, they both have a down arrow next to the green dot that says they are running. What does that mean?

Please excuse me while I go dig through the docs and google.

[EDIT]
fedora forums says:
add your proxy to
/etc/dnf/dnf.conf vim /etc/dnf/dnf.conf

Qubes says:

You may be encountering issue #3135
What happens after running systemctl restart qubes-updates-proxy in sys-net ?
https://github.com/QubesOS/qubes-issues/issues/3135

testing...

[Edit #2}

Fail.

journalctl -u qubes-updates-proxy.service
-empty-
Thats good, right?

/etc/dnf/dnf.conf
## This file is overridden by qubes-rpc/policy/qubes-UpdatesProxy

/usr/lib/qubes/updates-proxy-configs
## You cannot save changes to this file.

dom0: nano /qubes-rpc/policy/qubes-UpdatesProxy
# default
## $type:TemplateVM $default allow,target=sys-net
# edit#1
$type:TemplateVM $default allow,target=custom-sys-net
# edit#2
$type:TemplateVM $anyVM allow,target=custom-sys-net

Still not working...

[awokd]

On Mon, March 5, 2018 12:45 am, sevas wrote:

>
>
> dom0: nano /qubes-rpc/policy/qubes-UpdatesProxy
> # default
> ## $type:TemplateVM $default allow,target=sys-net
> # edit#1
> $type:TemplateVM $default allow,target=custom-sys-net
> # edit#2
> $type:TemplateVM $anyVM allow,target=custom-sys-net

Normally you shouldn't have to edit this file. Did you set qubes-prefs
updatevm custom-sys-net? (And why sys-net instead of sys-firewall)? Might
also want to clear dnf/yum cache in custom-sys-net.

[sevas]

> Normally you shouldn't have to edit this file. Did you set qubes-prefs
> updatevm custom-sys-net? (And why sys-net instead of sys-firewall)? Might
> also want to clear dnf/yum cache in custom-sys-net.

should it be going through the firewall? The default settings send through sys-net. Yeah, I dont have a reason. I want it set up correctly.

I see that I need to research qubes command line tools. I will try this soon...
Unfortunately, I have not done any qubes-commandline work yet. I started to edit that file because of /doc/software-update-vm/#updates-proxy ="Technical Details"

Thanks for taking the time!

[sevas]

Yes. My updateVM was set to custom-sys-net. I changed it to custom-sys-firewall, as you recommended.

I am very unfamiliar with the command-line (thats called bash, right?) tools. But qubes-prefs updatevm custom-sys-net = yes.

What I actually did:
sys-net$
yum clean all
yum repolist all
# There are no enabled repos.
dom0/sys-net$ systemctl status updates-proxy-setup
# No such service.
dom0$ systemctl status qubes-updates-proxy
# No such service.
sys-net$ systemctl status qubes-updates-proxy
# good
sys-net$ systemctl restart qubes-updates-proxy
sys-net$ spt-get update
# No new packages.
debian-9$ sudo apt-get update
# No new packages.
Fedora-26$ sudo yum update
# 84 new packages.

What I think did the trick:
Im not sure exactly what did it, but it must have something to do with
1. dom0$ qubes-prefs updatevm sys-firewall
2. $yum clean all;
3. as well as re-enabling the qubes-updates-proxy in the Qube Manager sys-net:settings>Services tab (which I had added and removed multiple times)
4. sys-net$systemctl restart qubes-updates-proxy

Thanks for your help, youre a Light Sabor!