Tool: Simple Set-up of New Qubes and Software

This has been discussed before.
The issue is that the update notification mechanism depends on qubes
being able to check if updates are available.
qubes that are offline,or are restricted to specific IP addresses will not
be able to do this.
qubes that do not have qrexec will not be able to do this.
qubes that inherit repository definitions that have been altered to work
with cacher will not be able to do this.

This mechanism makes sense if you have many qubes sharing a template.
Then it doesn’t matter if an offline qube cant check for updates
because one of the other qubes using that template should be able to
check.
Once you begin to use specific templates the mechanism starts
to break down.

There are a number of possible approaches:

  1. Ignore notifications and update all templates.
  2. Change the repo definitions back to normal in qubes.
  3. Set cacher upstream of most qubes and set proxy definition to access
    cacher by IP
  4. Set up proxy over qrexec in qubes.
  5. Probably others…

I favour 1.