Soyuz/HowToUseSoyuzLocally

Not logged in - Log In / Register

Revision 44 as of 2010-03-08 08:07:50

Clear message

Setting up a local Soyuz

You're going to run Soyuz in a branch you create for the purpose. To get the whole experience, you'll also be installing the slave-side launchpad-buildd package on your system.

After this, your sample data will include a realistic sampling of Ubuntu releases, and you'll have a user called "ppa-user" with password "test" and using your own email address. You'll be able to log in with your own email address, and sign things for this user with your own GPG key. The user is an Ubuntero and a member of ubuntu-team.

Configure an account and PPA

Set up the PPA

The testing PPA has an external dependency on Lucid. If that's not enough, or not what you want:

deb http://archive.ubuntu.com/ubuntu %(series)s main restricted universe multiverse

Configure a buildd

wget -O - -q https://edge.launchpad.net/api/devel/ubuntu/lucid/i386/chroot_url | xargs wget

Please note a "builder" and a "chroot" are not the same thing, nor are they "associated" in any way. The logic is as follows:

Upload a source to the PPA

[lpdev]
fqdn = ppa.launchpad.dev:2121
method = ftp
incoming = %(lpdev)s
login = anonymous

Dealing with the primary archive

Notes

Errors importing key to local zeca

If you are getting an error when importing your key to zeca and you are running Lucid, and bug 452194 is not fixed, you will need to:

  1. Grab the one line patch.,

  2. Apply it (patch -p0 sourcecode/pygpgme/src/pygpgme-context.c < pygpgme.patch)

  3. make compile and then restart your local development zeca as well as the web app.