--
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 qubes-users+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/685c74567d0c17d9504c9da70a5907bf%40damongant.de.
For more options, visit https://groups.google.com/d/optout.
On 2017-06-04 09:57, Franz wrote:
On Thu, Jun 1, 2017 at 12:10 PM, Damon Gant <m...@damongant.de> wrote:
I've been trying to get the Arch template running following the guide at https://www.qubes-os.org/doc/templates/archlinux/ on a brand new install.
I can get it to a point where the VM boots and I can spawn xterm, but pretty much everything else is broken.
- /etc/pacman.d/*.conf is not included from pacman.conf. This breaks the custom repo and updating over the proxy.
- fixing that, the GPG key is not imported to the pacman keychain by default
- updating over proxy is still broken, but custom repo works at this point
- the qubes guest tools that come with the image are a higher version than those available from repos
- upgrades are impossible due to pulseaudio and xorg version conflicts; yes that's a known issue, but suspect to me because pacman tries to downgrade
Can anyone confirm this is broken or working for them, or even maybe got an idea what's wrong?Yes, I too stopped on pulseaudio and xorg version conflicts. Also I have seen an other thread alerting on problems with Qubes inter-VM copy/move tools.So I suppose it is better to wait for Qubes 4 which changes from pv to hvm. Is it worth to make a lot of efforts, when a radical change is so close? Possibly a hvm will deal much easily with these problems.BestFran
Just add the following lines to /etc/pacman.conf in the template:
> IgnorePkg = libpulse
> IgnorePkg = pulseaudio
> gnorePkg = xf86-input-*
> IgnorePkg = xorg-server
afterwards "pacman -Syu" should work.
For me that call also appears to work after setting the environmental variables http_proxy/https_proxy to http://10.137.255.254:8082/
The only missing part for me know are the tools to copy between VMs AND (important to me) the qvm-usb proxy functionality ... how to get that fixed?
Joh