Archlinux - QubesR3 Support

[Olivier Médoc]

Hello,

I started to build archlinux packets for QubesR3. Please find attached the patches that can be applied to the R3 git branches:

vmm-xen:
0001-Use-fedora-patching-script-instead-of-specifiying-ea.patch
0002-archlinux-Change-var-run-to-run-as-it-is-handled-as-.patch

core-vchan-xen:
0001-archlinux-Change-library-name-to-match-QubesR3-name.patch

core-qubesdb:
0001-archlinux-create-build-scripts-for-archlinux-and-upd.patch

For core-qubesdb, I have a problem with the environment variable BACKEND_VMM which is not properly stored in the chroot build environment. In consequence, I currently have to change core-qubesdb/Makefile to hardcode BACKEND_VMM=xen in order to build the packet.

Is it working properly in fedora build scripts ? Maybe I should ensure that environment variable are forwarded when using the archlinux chroot environment or sudo (using sudo -E) ?

[Olivier Médoc]

Sorry, I tested sudo -E just after writing this email and that fix my problem. Please find the patch attached:

builder-archlinux:
0001-makefile-ensure-that-environment-variable-such-as-BA.patch


P.S: Do you prefer working with email submitted patches, or should I clone the github repositories ?

Best Regards,
Olivier Médoc

[Jason M]

This is awesome!  I look forward to build and taking archlinux for a test drive.

You may find it more convenient to submit PR via github; that's what I use now-a-days.

 

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, May 20, 2015 at 02:49:33AM -0700, Jason M wrote:
>
>
> On Wednesday, 20 May 2015 03:25:15 UTC-4, Olivier Médoc wrote:
> >
> > On 05/19/15 17:49, Olivier Médoc wrote:
> >
> > Hello,
> >
> > I started to build archlinux packets for QubesR3. Please find attached the
> > patches that can be applied to the R3 git branches:
> >

> > *vmm-xen:*
> > 0001-Use-fedora-patching-script-instead-of-specifiying-ea.patch
> > 0002-archlinux-Change-var-run-to-run-as-it-is-handled-as-.patch
> >
> > *core-vchan-xen:*
> > 0001-archlinux-Change-library-name-to-match-QubesR3-name.patch
> >
> > *core-qubesdb:*

> > 0001-archlinux-create-build-scripts-for-archlinux-and-upd.patch
> >
> > For core-qubesdb, I have a problem with the environment variable
> > BACKEND_VMM which is not properly stored in the chroot build environment.
> > In consequence, I currently have to change core-qubesdb/Makefile to
> > hardcode BACKEND_VMM=xen in order to build the packet.
> >
> > Is it working properly in fedora build scripts ? Maybe I should ensure
> > that environment variable are forwarded when using the archlinux chroot
> > environment or sudo (using sudo -E) ?
> >
> > Sorry, I tested sudo -E just after writing this email and that fix my
> > problem. Please find the patch attached:

Take a look at builder plugin documentation[1], especially the part
about CHROOT_ENV - it contains BACKEND_VMM exactly for this purpose. For
example Fedora plugin have this:
https://github.com/QubesOS/qubes-builder-fedora/blob/master/Makefile.fedora#L77

[1]
https://github.com/QubesOS/qubes-builder/blob/master/doc/BuilderPluginAPI.md


> > *builder-archlinux:*

> > 0001-makefile-ensure-that-environment-variable-such-as-BA.patch
> >
> >
> > P.S: Do you prefer working with email submitted patches, or should I clone
> > the github repositories ?
> >
> > Best Regards,
> > Olivier Médoc
> >
>
> This is awesome! I look forward to build and taking archlinux for a test
> drive.
>
> You may find it more convenient to submit PR via github; that's what I use
> now-a-days.

Yes, pull requests can be more convenient and harder to miss the
patches. Also it makes possible to add a signed tag so later anyone can
verify it was indeed your contribution :)
But if you prefer to use mails, I'm ok with that.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVXJcVAAoJENuP0xzK19csfjwH/jS6f09nPgC+oG5NamDtZPrN
h1/ZX2VhdbCSzfDh6t28XDG9JxjzINN5XG+lct+n6HJaKpmp48vAgFFGXEa/J+El
xwD8sRG/7BjjoOg6kqCCJ6l14Rk2TSIhrrAiuKsjlSAl/1hMgts0S+3AfeEAzQJc
yJ+yOdLft6RxMPJaMTsxf3N+t87LZAIOMCVFIIQBIWQ1kjWXV7eftPm72KYwtb7h
d/nojzJXmtGzLFqyatb82FvyB9vkwgxDUi+BCWbkOWn9NkrLYp+TNS1ewyDEnQiX
1lLY67Hk0Iw16i4WpCMUNb0qIVacR6vgjz8eihuLCkwu0ZbFwZH34KY5RMCZyp4=
=GaQt
-----END PGP SIGNATURE-----

[Olivier Médoc]

So it seems more advanced than a simple sudo -E (which may be unsafe
anyway). I will change to the same environment variables usage than the
fedora Makefile. You can ignore my archlinux patch for builder
repository for now.

>
> >> *builder-archlinux:*
> >> 0001-makefile-ensure-that-environment-variable-such-as-BA.patch
> >>
> >>
> >> P.S: Do you prefer working with email submitted patches, or should
> I clone
> >> the github repositories ?
> >>
> >> Best Regards,
> >> Olivier Médoc
> >>
>
> > This is awesome! I look forward to build and taking archlinux for a
> test
> > drive.
>
> > You may find it more convenient to submit PR via github; that's what
> I use
> > now-a-days.
>
> Yes, pull requests can be more convenient and harder to miss the
> patches. Also it makes possible to add a signed tag so later anyone can
> verify it was indeed your contribution :)
> But if you prefer to use mails, I'm ok with that.
>

I submitted the same patch through github pull requests. I created new
branches in my forks (archfix-201505). It should make things simpler for
reviewing.

See you,
Olivier MEDOC