Archlinux Community Template Qubes OS 3.2

[J. Eppler]

Hello,

I just wanted to thank the person who created and uploaded the qubes-template-archlinux 3.0.6 to the Qubes OS 3.2 rpm repo.

Saved a lot of work.

You can installed it with:
sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-archlinux

regards
J. Eppler

[Franz]

A really nice Christmas present! Thanks

When I digit
 sudo pacman-key -populate archlinux

I get

pacman-key: invalid option -- 'p'

Best

Fran

 

regards
  J. Eppler

--
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/d812aa94-1d7f-416c-a925-c3e0afa867bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Franz]

On Thu, Dec 29, 2016 at 2:41 AM, Franz <169...@gmail.com> wrote:

On Mon, Dec 19, 2016 at 3:06 PM, J. Eppler <j.ep...@openmailbox.org> wrote:

Hello,

I just wanted to thank the person who created and uploaded the qubes-template-archlinux 3.0.6 to the Qubes OS 3.2 rpm repo.

Saved a lot of work.

You can installed it with:
sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-archlinux

A really nice Christmas present! Thanks

When I digit
 sudo pacman-key -populate archlinux

I get

pacman-key: invalid option -- 'p'

I found the issue, there is a small clerical error in the documentation with a single"-". It should be
sudo pacman-key --populate archlinux

not
sudo pacman-key -populate archlinux

Best

Fran

[Olivier Médoc]

On 12/30/2016 03:59 AM, Franz wrote:

On Thu, Dec 29, 2016 at 2:41 AM, Franz <169...@gmail.com> wrote:

On Mon, Dec 19, 2016 at 3:06 PM, J. Eppler <j.ep...@openmailbox.org> wrote:

Hello,

I just wanted to thank the person who created and uploaded the qubes-template-archlinux 3.0.6 to the Qubes OS 3.2 rpm repo.

Saved a lot of work.

You can installed it with:
sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-archlinux

A really nice Christmas present! Thanks

When I digit
 sudo pacman-key -populate archlinux

I get

pacman-key: invalid option -- 'p'

I found the issue, there is a small clerical error in the documentation with a single"-". It should be
sudo pacman-key --populate archlinux

not
sudo pacman-key -populate archlinux

By the way, the Qubes Update Proxy Service is now supported and most of the pacman configuration occurs in /etc/pacman.d/ files with requiring specific changes.



I will check that based on a new template and fix the documentation accordingly.

[Franz]

Many thanks :-))

--
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/f1c0042c-84d9-8897-fe76-3901c0f415f0%40yahoo.fr.

[hed...@tutanota.com]

@Olivier Medoc

First off, thank you for all the work you've clearly put into the Arch Linux build and documentation for Qubes.

FYI, I'd just like to add my own experiences when I tried to use the new template. (Since I was using the ready-built template, I skipped your build instructions and started at section "Package Manager Proxy Setup Section".):

1. After the initial download, the template VM wouldn't close down and was eventually killed by the qubes-dom0-update script. That behaviour was repeated after I started and tried to shutdown the template VM myself.

2. Just like Francesco, I had difficulty reading the command lines, because it is virtually impossible to distinguish a single- from a double-dash and copy/paste wasn't working. I tried in both Firefox and Chromium so it wasn't browser related. A fixed-pitch font should do the trick.

3. Since gnome-terminal wouldn't open, it would have been useful if you had specifically named the "archlinux terminal app" for those of us not versed in Arch Linux. I used xterm as a fallback, which worked, but later found out that there is an xfce4-terminal that is very like gnome-terminal.

4. Step 3 Install Pacman failed with an error about a database file not existing. Some research led me to try "pacman -Syy" (I think without "sudo") which did the trick. 

5. Step 7 Configure Powerpill...  the description (though not the example) omits the need for a comma on the preceding line.

Otherwise, it's now all up and running. Now all I have to do is get my head around Arch!

Mike

[Franz]

Mine is also working! Thanks to Olivier for your long time commitment.

Happy new Year!

 

Mike

--
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/K_LP0VH--3-0%40tutanota.com.

[dfghs...@gmail.com]

Hi to all, new bug. Any ideas?

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'

[J. Eppler]

Hello,

I have the same issue.

[Olivier Médoc]

Hello,

I'm currently trying to rebuild the gui-agent to fix this. I will
provide feedback as soon as possible.

[Franz]

Thanks

--
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/ea997223-0342-3614-7eee-2f8014793b84%40yahoo.fr.

[Tim W]

Oiivier,

Its great pacman is now supported for updating. When I was working with others to update the build and doc to work with newer archlinux versions I tried most everything asking many on the archlinux forum for help. No one could offer a good solution that did not break update security or require manual opening and closing of the firewall access.

https://groups.google.com/forum/#!searchin/qubes-users/tim$20w$20pacman/qubes-users/vT_ETcU5BvQ/sDhu879WDQAJ I also had a thread on dev.

How was the functionality added? To pacman to allow for proxy addition without going thru wget or thru a change in qubes update proxy service?

I found the powerpill pacman wrapper which used aria2 to allow for proxy without breaking update proxy security to be at the time the best avenue not to mention its added power and speed. The only issue to have made everything completely smooth was the reflector app to keep update mirror list current had no option to allow for a proxy entry. I planned to send a email to xyne to see if he could add it as he has been quite responsive in the past to similar request.

Really glad its now working. The reason I ask about how it was addressed is I wondered if it would allow reflector program to go thru or does it have still have the proxy option to plug in the ip?

Thanks again for keeping the distro updated and working.

[Tim W]

Mike,

The errors in syntax in the instructions are my fault. I helped update the entire instruction guide and obviously there are some typos. While I did post it all up for review those must have slipped thru. It was alot of new instructions and images. I was trying to make it so people could c&p the various cmds to try and make it that much easier. The issue being that some of them did not obviously transfer correctly and or I typo'd. Not sure how it happened as I took the images and c&p the cmds as part of a full template build which was successful but somehow it seems it did happen.

The reason powerpill was not given specific configs was at the time a number of people had posted that pacman should have had a option to config the proxy ip which ended up not being the case at least not from anything I could find. I left it up to the end user then to decide as it was not a direct part of building the actual archlinux template.

I am happy to add the powerpill config instructions but if you do a basic search on its use of aria2 that it uses its straight forward. Its a basic config file with single line item config with very basic syntax. It would have to be for me to get it to work LOL.

The instruction page is 100% editable for change submissions so any errors you see you can submit the changes to fix it. If you prefer list them here giving me the step number and the error and I can go back and fix it.

[Franz]

Tim

from your lat two emails it seems the problem was solved. But I am confused how it was solved. You posted a link to this thread https://groups.google.com/forum/#!searchin/qubes-users/tim$20w$20pacman/qubes-users/vT_ETcU5BvQ/sDhu879WDQAJ but it seems too old. May you clarify a little bit please?

Best

Fran
 

--
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/167cd847-e907-46d1-bff3-f4138099910b%40googlegroups.com.

[andr...@gmail.com]

Hi!

I saw in the repository some files about an Arch Linux Minimal template:
https://github.com/QubesOS/qubes-builder-archlinux/blob/master/scripts/packages_minimal.list

How should we install it? Must we build it?

I tried to install "qubes-template-archlinux-minimal", but it can't be found. And "qubes-template-archlinux" came only with the default template.

Also, the Arch Linux template is not shutting down normally (need to kill the VM). With a quick look at logs it seems qetty is not terminating. I can try to paste the logs here if it's an unknown bug.

Regards

[Olivier Médoc]

> Oiivier,
>
> Its great pacman is now supported for updating. When I was working with others to update the build and doc to work with newer archlinux versions I tried most everything asking many on the archlinux forum for help. No one could offer a good solution that did not break update security or require manual opening and closing of the firewall access.
>
> https://groups.google.com/forum/#!searchin/qubes-users/tim$20w$20pacman/qubes-users/vT_ETcU5BvQ/sDhu879WDQAJ I also had a thread on dev.
>
> How was the functionality added? To pacman to allow for proxy addition without going thru wget or thru a change in qubes update proxy service?

Hello,

In fact I use curl which is included by default (as pacman apparently
use curl libraries anyway). I update the configuration in /etc/pacman.d/
to use curl with a proxy by calling curl with http_proxy environment
variable.

No changes is actually required to the qubes update proxy.

> I found the powerpill pacman wrapper which used aria2 to allow for proxy without breaking update proxy security to be at the time the best avenue not to mention its added power and speed. The only issue to have made everything completely smooth was the reflector app to keep update mirror list current had no option to allow for a proxy entry. I planned to send a email to xyne to see if he could add it as he has been quite responsive in the past to similar request.
>
> Really glad its now working. The reason I ask about how it was addressed is I wondered if it would allow reflector program to go thru or does it have still have the proxy option to plug in the ip?
>
> Thanks again for keeping the distro updated and working.
>

I did not tested reflector yet.

[Olivier Médoc]

On 03/05/2017 10:13 PM, andr...@gmail.com wrote:
> Hi!
>
> I saw in the repository some files about an Arch Linux Minimal template:
> https://github.com/QubesOS/qubes-builder-archlinux/blob/master/scripts/packages_minimal.list
>
> How should we install it? Must we build it?

Yes it must be built, but you can also use the prebuilt template, check
the additional packages installed in packages.list vs
packages_minimal.list and remove packages and dependencies that you
don't want using pacman -Rsc packagename.

From what I understood, ITL try to not use minimal templates because
there are too much libraries that are needed by very useful features.
However, I often take the standard templates, check the packages that
are installed after the qubes agents in /var/log/yum.log or
/var/log/pacman.log and remove packages I dislike.

>
> I tried to install "qubes-template-archlinux-minimal", but it can't be found. And "qubes-template-archlinux" came only with the default template.
>
> Also, the Arch Linux template is not shutting down normally (need to kill the VM). With a quick look at logs it seems qetty is not terminating. I can try to paste the logs here if it's an unknown bug.
>
> Regards
>

About the template not shutting down, I had this issue but I do not have
this problem anymore. Try updating the Qubes agents by enabling the
archlinux QubesOS repository inside your TemplateVM.

[andr...@gmail.com]

Thanks for the reply!

Olivier Médoc:

> Yes it must be built, but you can also use the prebuilt template, check
> the additional packages installed in packages.list vs
> packages_minimal.list and remove packages and dependencies that you
> don't want using pacman -Rsc packagename.
>
> From what I understood, ITL try to not use minimal templates because
> there are too much libraries that are needed by very useful features.
> However, I often take the standard templates, check the packages that
> are installed after the qubes agents in /var/log/yum.log or
> /var/log/pacman.log and remove packages I dislike.

Ok, using non-minimal template.

> About the template not shutting down, I had this issue but I do not have
> this problem anymore. Try updating the Qubes agents by enabling the
> archlinux QubesOS repository inside your TemplateVM.

It seams to have solved by itself, maybe after upgrading Qubes dom0 or Arch Linux Template (for the later I had to IgnoreGroup xorg-server and pulseaudio).

There are still a few problems, but I don't know if they are related to this template, because I'm not using another:

- /usr/local is beeing reset at my AppVMs on every reboot.
- Sometimes an AppVM starts with /home reseted. Rebooting the AppVM seems to fix it. I think it happens when I made changes to the template, shutdown the AppVM and start it again before it had time to receive the changes.

Both my Arch AppVMs and Template are in a external hdd (followed the method at the wiki: https://www.qubes-os.org/doc/secondary-storage/ ), not sure if this can be related.


Trying to install software only at one AppVM, but not at the Template (to avoid exposing multiples VMs to "dangerous" software), I came up with some dirty lines that I would like to share. Maybe they can be usefull to someone else:

https://github.com/andresmrm/qubes_archlinux_custom_install/blob/master/custom_install.sh

Basically it downloads/builds packages to a custom folder and then symlinks the files to system folders. The later step needs to be repeated after every reboot, but it should be much faster than downloading or building everything everytime.
Tested with "jre" and "wine" so far.


Regards

[Franz]

andresmrm

On Thu, Mar 9, 2017 at 4:35 PM, <andr...@gmail.com> wrote:

Thanks for the reply!

Olivier Médoc:
> Yes it must be built, but you can also use the prebuilt template, check
> the additional packages installed in packages.list vs
> packages_minimal.list and remove packages and dependencies that you
> don't want using pacman -Rsc packagename.
>
> From what I understood, ITL try to not use minimal templates because
> there are too much libraries that are needed by very useful features.
> However, I often take the standard templates, check the packages that
> are installed after the qubes agents in /var/log/yum.log or
> /var/log/pacman.log and remove packages I dislike.

Ok, using non-minimal template.

> About the template not shutting down, I had this issue but I do not have
> this problem anymore. Try updating the Qubes agents by enabling the
> archlinux QubesOS repository inside your TemplateVM.

It seams to have solved by itself, maybe after upgrading Qubes dom0 or Arch Linux Template (for the later I had to IgnoreGroup xorg-server and pulseaudio).

For me IgnoreGroup has no effect, but IgnorePkg = xorg-server pulseaudio  does prevent the update of xorg-server and pulseaudio,  but the same, after that I get:

warning: pulseaudio: ignoring package upgrade (9.0-1 => 10.0-2)
warning: xorg-server: ignoring package upgrade (1.18.4-1 => 1.19.2-1)
resolving dependencies...
looking for conflicting packages...
:: xf86-input-evdev and xorg-server are in conflict. Remove xorg-server? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: xf86-input-evdev and xorg-server are in conflict (xorg-server<1.19.0)

I have no idea how to handle that.

Best

Fran

[Andres MRM]

[2017-03-09 19:24] Franz:

> For me IgnoreGroup has no effect, but IgnorePkg = xorg-server pulseaudio  does
> prevent the update of xorg-server and pulseaudio,  but the same, after that I
> get:
>
> warning: pulseaudio: ignoring package upgrade (9.0-1 => 10.0-2)
> warning: xorg-server: ignoring package upgrade (1.18.4-1 => 1.19.2-1)
> resolving dependencies...
> looking for conflicting packages...
> :: xf86-input-evdev and xorg-server are in conflict. Remove xorg-server? [y/N]
> n
> error: unresolvable package conflicts detected
> error: failed to prepare transaction (conflicting dependencies)
> :: xf86-input-evdev and xorg-server are in conflict (xorg-server<1.19.0)
>
> I have no idea how to handle that.

Hi, Franz!

I just kept adding the packages to IgnorePkg, until I added one to IgnorePkg
and the two main ones to IgnoreGroup. Then it worked. That's why I thought the
IgnoreGroup ignored the rest of them, but maybe I just added them all to
IgnorePkg.


Regards