On Fri, Feb 14, 2020 at 12:07:51PM +0000, Unman wrote: > It's somewhat difficult to see exactly what's happening in Github. > A "foolproof" method would be to watch for update-notifications for > Debian templates, and rebuilding accordingly. (If you generally use > stable you might care to set up a "testing" template and qube for this > purpose.)
Got two more questions: - the ubuntu templates have a file /etc/apt/sources.list.d/qubes-contrib-r4.0.list which contains URI's to the qubes-os server (e.g. https://contrib.qubes-os.org/deb/r4.0/vm bionic main) Those don't work for me, which makes sense as Qubes can't provide Ubuntu binaries. Correct? - the above though got me thinking... if I build using my own signing key, run a webserver on the qubes-builder VM and configure the firewall to allow the Ubuntu templates on my machine to connect to the qubes-builder VM ... then I could replace the above URI with my local qubes-builder VM IP and 'apt update' should pick it up - right? There is probably another file that I need to create for this to work ("Release file")? Thanks! PS: I know Unman is doing all this work and that's awsome ... I could just use his binaries ... but where is the fun it that ;-) /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200302203613.GB1101%40app-email-private.
signature.asc
Description: PGP signature
