Installing using pacman command

[joseph....@gmail.com]

While trying to use an installation command like, say,

localhost% sudo pacman -Syu wine

I get the following response:

error: GPGME error: No data
error: xyne-x86_64: missing required signature
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: failed retrieving file 'xyne-x86_64.db' from xyne.archlinux.ca : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed to update xyne-x86_64 (download library error)
error: database 'xyne-x86_64' is not valid (invalid or corrupted database (PGP signature))

How do I get to make installations on Archlinux?

[joseph....@gmail.com]

I forgot to add, but I've modified the pacman.conf as specified in the Qubes documentation for the creation of an Archlinux Template VM.

[tezeb]

On 01/12/17 15:14, joseph....@gmail.com wrote:
> I forgot to add, but I've modified the pacman.conf as specified in the Qubes documentation for the creation of an Archlinux Template VM.
>

Are you running it in TemplateVM or AppVM?
Do you allow it to connect via update proxy? (Firewall Rules->Allow
connection to Updates Proxy)?

[joseph....@gmail.com]

Temporarily disabled the firework. Different error:

:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date

:: Starting full system upgrade...
resolving dependencies...
:: There are 4 providers available for lib32-libgl:
:: Repository multilib
1) lib32-mesa-libgl 2) lib32-nvidia-304xx-libgl
3) lib32-nvidia-340xx-libgl 4) lib32-nvidia-libgl

Enter a number (default=1): 1
looking for conflicting packages...
:: xorg-server and xf86-input-joystick are in conflict (X-ABI-XINPUT_VERSION). Remove xf86-input-joystick? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: qubes-vm-gui: installing xorg-server (1.19.1-1) breaks dependency 'xorg-server<1.19.0'

[joseph....@gmail.com]

Template VM. Yes.

[Tim W]

Did this get resolved. If not try opening up the firewall setting for 10 mins and try the download. I know recently the archlinux build has been fixed to allow update proxy via Qubes update proxy setting. Prior this it could not be done directly thru Pacman without breaking the proxy firewall rule. You needed to install and use Powerpill wrapper for Pacman. Set update proxy IP in Aria2. I think I had this all in the Qubes Doc for Archlinux with example of the config file settings. IMHO Powerpill wrapper is far superior in every way to default Pacman with Wget or Curl. Its faster for granular config, allows for parallel and segmented downloads. With Reflector you can get the very fastest up today mirrors for you location. XYNE controls all the code for those apps and from my experience has been restive to requests and suggestions.

Anyways take a look.

The only issue with reflector is no place to enter a proxy IP which I will be asking of xyne to see if he can add it. This is tech a sep issue from Pacman and Powerpill which the later has proxy line entry in config via Aria2 config keeping to update proxy secpol.

With that said according to the post by Olivier update proxy now functions properly with pacman. I have not personally tested this yet so can no comment personally beyond what I read.

[trule...@gmail.com]

Hi, Tim. Olivier said :

"Archlinux currently upgraded xorg and pulseaudio, however the integrated
archlinux gui agent must be build for strict versions of xorg-server and
pulseaudio. For this reason, you have to rebuild the agent using the
most recent qubes repository, or wait for binary agents to be available. "

Powerpill or Pacman, it doesn't matter, update system and break dependency and can't install anything.

[Tim W]

Ok I miss understood the issue. Yes that is the same issue we ran into if you do a search on the template a while back. For that is was pulseaudio. When xorg or pulseaduio versions are updated by ARchlinux we end up having to rebuild the template from source. If not you just get the failed errors when trying to update.

The issue I was originally speaking of was not being able to assign pacman a proxy ip to use the qubes update proxy. AT least not without breaking the security model for it hence the while powerpill etc comments.

THere is another thread running concurrently that is dealing with the same issue so maybe best to just use that thread to address the issue.

[Olivier Médoc]

Hello,

Using the proxy instead of opening the firewall is actually fixed in the
qubes-core-agent-linux code (qubes-vm-core in archlinux).

If you take a look, qubes specific pacman configuration has been added
in /etc/pacman.d. I made the change some time ago, but I discovered
recently that I made an error in the package install file that enable
configuration files in /etc/pacman.d.

Another point is that I provide signed binary packages (as documented
https://www.qubes-os.org/doc/templates/archlinux/) that you have to
enable explicitly, so that you don't have necessarilly to rebuild packages.