[X2Go-Dev] Raspberry Pi Builds and How to Handle Authentication/Signing

[Michael DePaulo]

Hi guys,

1st of all, I recall that someone else offered to setup a Raspberry Pi
for X2Go Jenkins builds, but I forget who it was. I also cannot find
anything about it in my IRC logs or emails.

Anyway, I started (but did not finish) adapting buildscripts.git for
Raspberry Pi builds with Raspbian:
http://code.x2go.org/gitweb?p=buildscripts.git;a=shortlog;h=refs/heads/feature/raspbian
(For one thing, I need to replace the logic that always calls
qemubuilder with logic to use regular (chroot) pbuilder.)

For those of you who are unfamiliar, the challenge with Raspbian is
that while Debian's "armhf" binaries are ARMv7 hard-float, Raspbian's
"armhf" binaries are ARMv6 hard-float. This is a necessary
complication to maximize performance out of the Raspberry Pi 1. Even
on the Raspberry Pi 2, which does support ARMv7 hard-float, Raspbian
users are currently still using these binaries.

I figured I would setup my Raspberry Pi 2 at my apartment as a Jenkins
slave. However, it appears that I would need to upload the packages to
code.x2go.org with dupload, which would in turn call scp in batch
mode. That means setting up SSH public key authentication.

We would also have to figure out package signing.

So before I continue, I want to know:

1. Should I continue setting this up, or should we try to use
qemubuilder on japsand with a Raspberry Pi version of QEMU?

2. If I continue setting this up, how should we setup the SSH and GPG keys?

-Mike#2