• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

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.

• Run utilities/start-dev-soyuz.sh to ensure that some Soyuz-related services are running. Some of these may already be running, in which case you'll get some failures that are probably harmless. Note: these services eat lots of memory.

• Once you've set up your test database, run utilities/soyuz-sampledata-setup.py -e you@example.com (where you@example.com should be an email address you own and have a GPG key for). This prepares more suitable sample data in the launchpad_dev database. If you get a "duplicate key" error, make schema and run again.

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

• make run (or if you also want to use codehosting, make run_codehosting—some services may fail to start up because you already started them, but it shouldn't be a problem).

• Open https://launchpad.dev/ in a browser. Log in with your own email adddress and password test.

Set up the PPA

You'll find a pre-made PPA for ppa-user. It has an external dependency on Lucid. If that's not enough, or not what you want:

• Log in as admin@canonical.com:test.

• Browse to the new PPA.

• Click "Administer".

• Edit external dependencies. They normally look like:

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

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

• mkdir /var/tmp/poppy (Moving into script per bug 527170 —jtv)

• Run scripts/process-upload.py /var/tmp/poppy (creates hierarchy)

• Add to ~/.dput.cf:

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

• dput lpdev:~USERNAME/PPANAME/ubuntu some_source.changes (fixing USERNAME per bug 527170 —jtv)

• scripts/process-upload.py /var/tmp/poppy # Accept the source upload.

• If this is your first time running soyuz locally, you'll also need to publish ubuntu: scripts/publish-distro.py -C

• Within five seconds of upload acceptance, the buildd should start building. Wait until it is complete.

• scripts/process-accepted.py --ppa ubuntu # Create publishings for the binaries.

• scripts/publish-distro.py --ppa # Publish the source and binaries.

  • Note that private archive builds will not be dispatched until their source is published.

Dealing with the primary archive

• Add yourself to ~ubuntu-team. (Moving into script per bug 527170 —jtv)

• dput lpdev:ubuntu some_source.changes

• scripts/process-upload.py /var/tmp/poppy

• Watch the output -- the upload might end up in NEW.
  • If it does, go to the queue and accept it.
• Your builder should now be busy. Once it finishes, the binaries might go into NEW. Accept them if required.

• scripts/process-accepted.py ubuntu

• scripts/publish-distro.py

  • The first time, add -C to ensure a full publication of the archive.

Notes

• (No longer needed per bug 527170 —jtv)

Run the query below (e.g. using "psql -d launchpad_dev") before running make-ubuntu-sane.py in case you want to be able to set up amd64 chroots for build slaves. (Moving into script per bug 527170 —jtv)

INSERT INTO distroarchseries (distroseries, processorfamily, architecturetag, owner, official) VALUES (3, 3, 'amd64', 1, true);

• (No longer needed per bug 527170 —jtv)

You need to have some sort of MTA (e.g. postfix) running in order for the email to be placed in the root's mailbox. In cases where you have Launchpad running in a chroot you'll need to stop the "normal" MTA and start it in the chroot or configure the one in the chroot to use a different port.

Gpg CRC errors

• (No longer needed per bug 527170 —jtv)

Run gpg like this "gpg --ignore-crc-error -d <file>" in case you see the following error message while decrypting the email sent by launchpad:

gpg: malformed CRC
gpg: quoted printable character in armor - probably a buggy MTA has been used