Does the Archlinux Template supports Qubes R3?

[je.e...@web.de]

Hello,

does the Archlinux Template supports Qubes R3?
I would be happy if it does.

Best regards
J. Eppler

[lanythe]

Adding oliv to this thread.

There used to be an arch template that Olivier uploaded to his FTP. It
was an unsigned, use-at-your-own-risk sort of deal. It does not work
with R3, but he recently submitted patches for the archlinux builder for
R3 support (https://groups.google.com/d/topic/qubes-devel/lOfLGqMwc2w).

It technically _is_ possible to compile the Archlinux template to work
with R3, as I was able to do so a few days ago but it required a series
of very ugly hacks. Basically the PKGBUILDs for qubes/xen tools need to
be tweaked a little bit, because they complain about /lib, /usr/sbin and
/usr/lib64 being present (even when they simply exist as symlinks for
compatability reasons). (It's entirely related to this change:
https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/)

I think that there is some logic in the current PKGBUILDs that makes
pacman refuse to install the qubes-vm-gui and qubes-vm-core (@Olivier,
is this correct?)
You can always suspend the compilation process (^z) at the points in the
VM compilation where the process is likely to fail and manually edit the
symlinks as the "qubized image" is being created (and repeat as
necessary). Additionally, the template currently builds without
installing qubes-db-vm, so networking is not operational until you
manually push the package to the VM and install through xen console.

I may have time to update the PKGBUILDs this weekend and then I could
upload a template if you trust me. Other than that, it's possible to
make a Archlinux template that works very smoothly in R3 with the
default kernel.

[je.e...@web.de]

Hello lanythe,

it would be awesome to have an Archlinux template for Qubes R3. It would be nice if you are able to provide this template for the qubes users.

Another question can upload your PKGBUILDS to the AUR repository? This would be really nice.

What I extremely like on Archlinux is that it is a rolling release distribution with a large number of up to date packages from the community.

For me Archlinux should be an ITL template.

Best regards
Jeremias

[Jeremias E.]

@lanyte how is the progress template progress going?

Best regards
 J. Eppler

[Olivier Médoc]

On 07/02/15 09:12, je.e...@web.de wrote:
> Hello lanythe,
>
> it would be awesome to have an Archlinux template for Qubes R3. It would be nice if you are able to provide this template for the qubes users.

Hello,

Sorry I didn't had any time to work on QubesR3 support. As Jeremias
said, I submitted some patches to start supporting qubesdb and so on,
but I didn't finished testing everything. Now that there is windows
agents available, I may speed up testing to use QubesR3 as my production
environment.

> Another question can upload your PKGBUILDS to the AUR repository? This would be really nice.

It is quite complicated because PKGBUILDs are currently using local
Qubes source code and won't work as is if downloaded from the AUR.

[Jeremias E.]

Hello,

I can understand that you need the Windows tools for R3.
But you could upload somewhere a alpha-archlinux-template build and ask the
community to test it.
I would like to help with the testing. I mean you are the expert for the Archlinux Qubes OS template,
but testing the template can be done by community members.

Furthermore a list with testing questions or hints what you want to be tested would be nice. I mean this would make
the testing more efficient for both sides I guess.

[Olivier Médoc]

On 07/24/15 13:28, Jeremias E. wrote:

Hello,

I can understand that you need the Windows tools for R3.
But you could upload somewhere a alpha-archlinux-template build and ask the
community to test it.
I would like to help with the testing. I mean you are the expert for the Archlinux Qubes OS template,
but testing the template can be done by community members.

Hello,

I already provided two set of patches in May and in July, but I'm still missing the GUI agent before I can try building the full template.

Furthermore a list with testing questions or hints what you want to be tested would be nice. I mean this would make
the testing more efficient for both sides I guess.

Such a checklist would be very helpful from my point of view and could benefits all template maintainers. This should at list includes:
- Standard tests to ensure that the AppVM is running smoothly
- Tests of all Qubes OS features when used as an AppVM (move, copy, clipboard, runinvm, pause, resume, backup, restore). In fact all rcp calls in /etc/qubes_rpc.
- Tests of the DispVM mecanism
- Tests that the TemplateVM itself is running correcly and can be updated
- Tests of the template used as a NetVM or FirewallVM
- Tests of specific OS features that may be broken by Qubes Agent (Sound, GTK gui, QT gui, Java swing GUI, USB stick mounting through thunar ...)

--
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...@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/174eb134-1911-4e69-b93d-b2e2c7695e72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Olivier Médoc]

On 07/28/15 09:05, 'Olivier Médoc' via qubes-users wrote:

On 07/24/15 13:28, Jeremias E. wrote:

Hello,

I can understand that you need the Windows tools for R3.
But you could upload somewhere a alpha-archlinux-template build and ask the
community to test it.
I would like to help with the testing. I mean you are the expert for the Archlinux Qubes OS template,
but testing the template can be done by community members.

Hello,

I already provided two set of patches in May and in July, but I'm still missing the GUI agent before I can try building the full template.

Good news, the archlinux template builds and run correctly on Qubes-R3. At least I have an xterm working.

I will push my patches to github and will start testing.

I will send a link the the .rpm template as soon as I am on the right country to be able to access to my hoster web root :)

Be free to complete the testing checklist.

Furthermore a list with testing questions or hints what you want to be tested would be nice. I mean this would make
the testing more efficient for both sides I guess.

Such a checklist would be very helpful from my point of view and could benefits all template maintainers. This should at list includes:
- Standard tests to ensure that the AppVM is running smoothly
- Tests of all Qubes OS features when used as an AppVM (move, copy, clipboard, runinvm, pause, resume, backup, restore). In fact all rcp calls in /etc/qubes_rpc.
- Tests of the DispVM mecanism
- Tests that the TemplateVM itself is running correcly and can be updated
- Tests of the template used as a NetVM or FirewallVM
- Tests of specific OS features that may be broken by Qubes Agent (Sound, GTK gui, QT gui, Java swing GUI, USB stick mounting through thunar ...)

--
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...@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/174eb134-1911-4e69-b93d-b2e2c7695e72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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...@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/55B729A1.8020207%40yahoo.fr.

[Olivier Médoc]

Hello,

You can find the new archlinux minimal template here (for testing):

http://olivier.medoc.free.fr/rpm/noarch/qubes-template-archlinux-minimal-3.0.3-201507281153.noarch.rpm

It should also be possible to update a Qubes-R2 template by changing the
Qubes repository to the following url (in /etc/pacman.conf):
http://olivier.medoc.free.fr/archlinux/r3/

The template RPM is currently not signed. Use it at your own risk.

Packages found in archlinux/r3 are however all signed using my Qubes-OS
signing key.

[XO...@riseup.net]

You sir are a saviour! I am gonna give this a run, thank you VERY MUCH
Olivier for your contributions.
Prior to this post, I've been having a HELL of a time getting the
archlinux template to build on R3 - there were sooo many changes needed
to implement to get it built and running.
Since I see you posted this is for testing, I shall report back with
results.

Thank you again.

[XO...@riseup.net]

Olivier,

I tried out your newest archlinux-minimal template tonight, but was unsuccessful at launching any of the applications that come with it, namely 'XTerm' and 'UXTerm'. This is the exact same issue I ran into when attempting to build my own archlinux template on Qubes R3 rc1 using a heavily modified qubes-builder setup. The applications just never "launch".

I went so far as to gain an "archlinux-minimal"  shell from @dom0, via 'virsh -c xen:/// console archlinux-minimal''. I see that there are several systemd services in 'inactive' state, some 'not-found' that I wonder if this could be affecting us? I have attached the output of the command (run as root) 'systemctl --all|grep -i inactive > systemd--inactives.txt' to this email if you desire to take a gander.
I installed a couple other minimal terminals, just to see if I could get eitherof them to work, i.e. 'roxterm', and 'rxvt'.
Lastly, just something I observed and figured I would pass-on = upon installing the above mentioned 2 additional terminal applications, the KDE menu for Qubes did not update until I manually ran 'qvm-sync-appmenus archlinux-minimal'.
The issue remains, that we cannot interact with the archlinux template via Qubes, meaning any application launched from the main KDE menu in Qubes R3-rc1 in the 'archlinux-minimal' context never truly "launches".

Let me know if you desire any help, or need someone to test things here and there, as I am glad to lend my assistance. I am really looking forward to getting an archlinux template up and running on Qubes R3!

Again, thank you for all your efforts and contributions.

[Olivier Médoc]

On 07/29/15 11:01, XO...@riseup.net wrote:

Olivier,

I tried out your newest archlinux-minimal template tonight, but was unsuccessful at launching any of the applications that come with it, namely 'XTerm' and 'UXTerm'. This is the exact same issue I ran into when attempting to build my own archlinux template on Qubes R3 rc1 using a heavily modified qubes-builder setup. The applications just never "launch".

I went so far as to gain an "archlinux-minimal"  shell from @dom0, via 'virsh -c xen:/// console archlinux-minimal''. I see that there are several systemd services in 'inactive' state, some 'not-found' that I wonder if this could be affecting us? I have attached the output of the command (run as root) 'systemctl --all|grep -i inactive > systemd--inactives.txt' to this email if you desire to take a gander.
I installed a couple other minimal terminals, just to see if I could get eitherof them to work, i.e. 'roxterm', and 'rxvt'.
Lastly, just something I observed and figured I would pass-on = upon installing the above mentioned 2 additional terminal applications, the KDE menu for Qubes did not update until I manually ran 'qvm-sync-appmenus archlinux-minimal'.
The issue remains, that we cannot interact with the archlinux template via Qubes, meaning any application launched from the main KDE menu in Qubes R3-rc1 in the 'archlinux-minimal' context never truly "launches".

Let me know if you desire any help, or need someone to test things here and there, as I am glad to lend my assistance. I am really looking forward to getting an archlinux template up and running on Qubes R3!

Again, thank you for all your efforts and contributions.

Hello,

Same problem here when running a program from the menu.

A workaround is to right click on the AppVM > Run command in VM > xterm

The problem is probably caused by the wrapper called inside the appvm when running desktop icons (qubes-desktop-run) script. I add it to my testing checklist.

--
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...@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/55B89651.40202%40riseup.net.

[fno...@riseup.net]

beautiful, great minds think alike. I was juuust researching that command ('qubes-desktop-run') as I type this ;)
A cursory glance over 'qubes-desktop-run' it's calling '#!/usr/bin/python' vs '#!/usr/bin/python2'

thanks again for all your work.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/55B8ABB9.5080307%40yahoo.fr.

[fno...@riseup.net]

Olivier,

I worked out the kinks, and found that your 'archlinux-minimal' template was/is missing the 'python2-gobject' (3.16.x) package provided by archlinux extra repo. Once the 'python2-gobject' package is installed, one just needs to modify the file '/usr/bin/qubes-desktop-run', specifically the '#!/usr/bin/python' line to call python2 ::
    sudo sed 's:#!/usr/bin/python:#!/usr/bin/python2:' -i /usr/bin/qubes-desktop-run

We are then in business! Any application can now be run directly from the main Qubes KDE menu flawlessly.

Cheers.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/55B8B183.2000500%40riseup.net.

[Jeremias E.]

Hello,

I tested the archlinux-template:

# Archlinux Test #

### Archlinux VM Type ###
AppVM                      works
FirewallVM                 works (without any modifications)
NetVM                       not tested

### Qubes OS Tools - CLI ###

qvm-copy-to-vm                    works (both directions)
qvm-open-in-dvm                   works
qvm-open-in-vm                     works

the qubes os tools does not have a manuasl entry. This should be improved.

### Upgrade and Update ###
works fine (via pacman)

### Application ###
Run command in VM works fine (Workaround to start xterm at the beginning)

Applications did not start without:

1. pacman -S python2-gobject
   
2. sudo sed 's:#!/usr/bin/python:#!/usr/bin/python2:' -i /usr/bin/qubes-desktop-run

-> Still nautilus can not be started via graphical the menu (Use qvm-run nautilus instead)

Java + SWT (Eclipse)      works
Java + Swing                  not tested
Java + FXML                   not tested
KDE                               works
Gnome                           works
Cinnamon                       failed

better looking after installing:
 + kde-base-artwork
 + gnome-themes-standard
 + ttf-freefont

sound                             works
video                              works

package install                failed
package source               works
package update               works

### Features ###
+ automatic syncing to application menu in pacman does not work
+ Qubes Tools did not appear in the nautilus context menu (Copy to VM, Move to VM)

+ Not Tested: Notifications

### Bugs ###
+ Get Icon problem (see: https://gist.github.com/Jeeppler/89f45a7dc4727efb0446)

##  Conclusion ##
The main functionalities in the archlinux-template work very well. But it is not perfect. It would be nice if the qubes tools can be used over the nautilus context menu and it would be nice to have an automatic appsync mechanism, to synchronize the vm menu after installing new applications.

One really nice thing about the archlinux-template: it is fast. Fast means it is possible to start and close applications in a short time.

Best regards
  J. Eppler

[Jeremias E.]

Hello,

my special thanks goes to Olivier Médoc, for creating a usable Archlinux-Template for Qubes 3.

Best regards
  J. Eppler

[Olivier Médoc]

On 07/29/15 19:16, Jeremias E. wrote:

Hello,

I tested the archlinux-template:

Thanks a lot for your testing. I'm quite busy right now and have limited time to do full testing.

# Archlinux Test #

### Archlinux VM Type ###
AppVM                      works
FirewallVM                 works (without any modifications)
NetVM                       not tested

### Qubes OS Tools - CLI ###

qvm-copy-to-vm                    works (both directions)
qvm-open-in-dvm                   works
qvm-open-in-vm                     works

the qubes os tools does not have a manuasl entry. This should be improved.

### Upgrade and Update ###
works fine (via pacman)

### Application ###
Run command in VM works fine (Workaround to start xterm at the beginning)

Applications did not start without:

1. pacman -S python2-gobject
   
2. sudo sed 's:#!/usr/bin/python:#!/usr/bin/python2:' -i /usr/bin/qubes-desktop-run

I will fix this in the qubes agents PKGBUILDs.

-> Still nautilus can not be started via graphical the menu (Use qvm-run nautilus instead)

Java + SWT (Eclipse)      works
Java + Swing                  not tested
Java + FXML                   not tested
KDE                               works
Gnome                           works
Cinnamon                       failed

better looking after installing:
 + kde-base-artwork
 + gnome-themes-standard
 + ttf-freefont

I provided several recommendation to improve looking in a mail last year. The hard thing is to support both GTK2, GTK3 and QT when selecting a look and feel. I will search for this mail later.

A second issue is to enforce look and feel in the template instead of the Appvms to avoid making a lookandfeel change several times.

I think it can be the subject of a full wiki article.

sound                             works
video                              works

package install                failed

Do you have more information on that ? (use pacman -Sy first to synchronize archlinux repository)

package source               works
package update               works

### Features ###
+ automatic syncing to application menu in pacman does not work

Yes, the problem is that pacman does not have any hooks to run qvm-sync-appmenus after installing a package.

+ Qubes Tools did not appear in the nautilus context menu (Copy to VM, Move to VM)

OK, it is probably a separate Qubes app-plugin. However, you can probably add items manually in nautilus context menu (use the binaries qvm-copy-to-vm ...). Same thing can be done in thunderbird instead of installing Qubes plugins (qvm-start-in-dvm...)

+ Not Tested: Notifications

### Bugs ###
+ Get Icon problem (see: https://gist.github.com/Jeeppler/89f45a7dc4727efb0446)

OK, these icons problems can probably be reproduced when using qvm-sync-appmenus in dom0. In fact, it probably means that several .desktop files are either malformed or are using icons that are invalid or do not pass sanity checks (because icons are transformed to change their color and to ensure that dangerous icons are not imported in dom0?).

##  Conclusion ##
The main functionalities in the archlinux-template work very well. But it is not perfect. It would be nice if the qubes tools can be used over the nautilus context menu and it would be nice to have an automatic appsync mechanism, to synchronize the vm menu after installing new applications.

One really nice thing about the archlinux-template: it is fast. Fast means it is possible to start and close applications in a short time.

Best 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...@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/888374c6-bd43-41e8-b20d-834b22010e6b%40googlegroups.com.

[Jeremias E.]

Am Donnerstag, 30. Juli 2015 09:28:18 UTC+2 schrieb Olivier Médoc:

On 07/29/15 19:16, Jeremias E. wrote:

Hello,

I tested the archlinux-template:

Thanks a lot for your testing. I'm quite busy right now and have limited time to do full testing.

# Archlinux Test #

### Archlinux VM Type ###
AppVM                      works
FirewallVM                 works (without any modifications)
NetVM                       not tested

### Qubes OS Tools - CLI ###

qvm-copy-to-vm                    works (both directions)
qvm-open-in-dvm                   works
qvm-open-in-vm                     works

the qubes os tools does not have a manuasl entry. This should be improved.

### Upgrade and Update ###
works fine (via pacman)

### Application ###
Run command in VM works fine (Workaround to start xterm at the beginning)

Applications did not start without:

1. pacman -S python2-gobject
   
2. sudo sed 's:#!/usr/bin/python:#!/usr/bin/python2:' -i /usr/bin/qubes-desktop-run

I will fix this in the qubes agents PKGBUILDs.

perfect :-)

-> Still nautilus can not be started via graphical the menu (Use qvm-run nautilus instead)

Java + SWT (Eclipse)      works
Java + Swing                  not tested
Java + FXML                   not tested
KDE                               works
Gnome                           works
Cinnamon                       failed

better looking after installing:
 + kde-base-artwork
 + gnome-themes-standard
 + ttf-freefont

I provided several recommendation to improve looking in a mail last year. The hard thing is to support both GTK2, GTK3 and QT when selecting a look and feel. I will search for this mail later.

A second issue is to enforce look and feel in the template instead of the Appvms to avoid making a lookandfeel change several times.

I think it can be the subject of a full wiki article.

Yes, it should. Actually every minimal template for Qubes OS has the same problem. After installing the themes for KDE or Gnome and some fonts, everything was looking very nice. 

sound                             works
video                              works

package install                failed

Do you have more information on that ? (use pacman -Sy first to synchronize archlinux repository)

Pacman works perfectly fine. Installing and updating packages is not a problem at all. But the problem occurs only by using the graphical qubes vm tools for updating and installing packages!

package source               works
package update               works

### Features ###
+ automatic syncing to application menu in pacman does not work

Yes, the problem is that pacman does not have any hooks to run qvm-sync-appmenus after installing a package.

I mean it would be nice to have something similar, but it works fine with the command line tools.

+ Qubes Tools did not appear in the nautilus context menu (Copy to VM, Move to VM)

OK, it is probably a separate Qubes app-plugin. However, you can probably add items manually in nautilus context menu (use the binaries qvm-copy-to-vm ...). Same thing can be done in thunderbird instead of installing Qubes plugins (qvm-start-in-dvm...)

+ Not Tested: Notifications

### Bugs ###
+ Get Icon problem (see: https://gist.github.com/Jeeppler/89f45a7dc4727efb0446)

OK, these icons problems can probably be reproduced when using qvm-sync-appmenus in dom0. In fact, it probably means that several .desktop files are either malformed or are using icons that are invalid or do not pass sanity checks (because icons are transformed to change their color and to ensure that dangerous icons are not imported in dom0?).

To you need more information about that and if yes what information?

[Connor Page]

On Tuesday, 28 July 2015 19:58:54 UTC+1, Olivier Médoc wrote:

Hello,

You can find the new archlinux minimal template here (for testing):

http://olivier.medoc.free.fr/rpm/noarch/qubes-template-archlinux-minimal-3.0.3-201507281153.noarch.rpm

It should also be possible to update a Qubes-R2 template by changing the
Qubes repository to the following url (in /etc/pacman.conf):
http://olivier.medoc.free.fr/archlinux/r3/

The template RPM is currently not signed. Use it at your own risk.

Packages found in archlinux/r3 are however all signed using my Qubes-OS
signing key.

Thank you very much! I hesitated to try your template but now I really enjoy it as a lighweight base. I expect things to break someday so how quickly qubes updates appear in your repo? Would you consider maintaining PKGBUILDS in AUR? And BTW the links to PKGBUILDS in the documentation (I mean the article that uses Archlinux as guide to porting qubes stuff) are wrong. I guess the packages are not there anymore, are they?

I haven't done any extensive testing but so far I've only encountered the known bugs and missing features.

[Connor Page]

qubes-gpg-split is missing

[Connor Page]

I provided several recommendation to improve looking in a mail last year. The hard thing is to support both GTK2, GTK3 and QT when selecting a look and feel. I will search for this mail later.

A second issue is to enforce look and feel in the template instead of the Appvms to avoid making a lookandfeel change several times.

I think it can be the subject of a full wiki article.

Oh yeah! This is a very time consuming process. Especially when Archlinux doesn't have packages for the themes (and engines) already installed in Fedora or Debian :) Turns out Qt5 apps take their style from the desktop environment which is not set in this minimal template...

+ Not Tested: Notifications

Perhaps I needed to read more about the gnome notification daemon that gets installed but I didn't see any notifications. I use dunst in fedora templates, it works with archlinux out of the box.

### Bugs ###
+ Get Icon problem (see: https://gist.github.com/Jeeppler/89f45a7dc4727efb0446)

OK, these icons problems can probably be reproduced when using qvm-sync-appmenus in dom0. In fact, it probably means that several .desktop files are either malformed or are using icons that are invalid or do not pass sanity checks (because icons are transformed to change their color and to ensure that dangerous icons are not imported in dom0?).

Some icons are just missing, at least I couldn't find the icon for xterm. Looks like the package hicolor-icon-theme should help as most applications add their icons to that icon theme. Other themes like Adwaita and oxygen inherit icons from hicolor.

[Jeremias E.]

Am Freitag, 21. August 2015 01:10:26 UTC+2 schrieb Connor Page:

I provided several recommendation to improve looking in a mail last year. The hard thing is to support both GTK2, GTK3 and QT when selecting a look and feel. I will search for this mail later.

A second issue is to enforce look and feel in the template instead of the Appvms to avoid making a lookandfeel change several times.

I think it can be the subject of a full wiki article.

Oh yeah! This is a very time consuming process. Especially when Archlinux doesn't have packages for the themes (and engines) already installed in Fedora or Debian :) Turns out Qt5 apps take their style from the desktop environment which is not set in this minimal template...

 

better looking after installing:
 + kde-base-artwork
 + gnome-themes-standard
 + ttf-freefont

this package are available on fedora and archlinux and style the applications. I don't know if TTF-Freefonts are really necessary.

[Connor Page]

On Tuesday, 28 July 2015 19:58:54 UTC+1, Olivier Médoc wrote:

An update is broken. archlinux/pkgs started to serve R2 packages. qubes-vm-core updated causes the following errors:

Packages (1) qubes-vm-core-3.0.13-3

Total Installed Size:  2.04 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
Pre upgrade...
(1/1) upgrading qubes-vm-core                      [######################] 100%
warning: directory permissions differ on /etc/sudoers.d/
filesystem: 750  package: 755
warning: directory permissions differ on /etc/polkit-1/rules.d/
filesystem: 700  package: 755
ln: failed to create symbolic link ‘/etc/sysconfig/iptables’: File exists
ln: failed to create symbolic link ‘/etc/sysconfig/ip6tables’: File exists
ln: failed to create symbolic link ‘/etc/xdg/autostart/notification-daemon.desktop’: File exists
/tmp/alpm_VdOur8/.INSTALL: line 70: /etc/selinux/config: No such file or directory
mv: cannot stat ‘/etc/selinux/config.processed’: No such file or directory
Created symlink from /etc/systemd/system/getty.target.wants/ge...@tty1.service to /usr/lib/systemd/system/getty@.service.

Do these error require attention and manual intervention? I am somewhat concerned about selinux.

[Jeremias E.]

@Connor Page have you found a solution yet?

[Connor Page]

On Tuesday, 1 September 2015 16:23:55 UTC+1, Jeremias E. wrote:

@Connor Page have you found a solution yet?

Well, it still works. I believe more restrictive permissions are correct and there's no SElinux in arch template. The bug that probably still persists is that the qubes repo in pacman is linked to R2 packages, not R3. So you have to change that to the correct link that Olivier posted in his announcement and import his key. Pacman will actually tell you which key is needed because it will fail to upgrade without it.