Note
It’s recommended to read this Quickstart on the mini-buildd instance in question itself, else some of the links here will not work as-is.
As a convention, we write code you should run as root like:
# apt-get install xyz
and code you should run as user like:
? mini-buildd-tool HOST status
Goal: Initial fully working setup with the sandbox repository test.
Prepare to set your admin password when installing, otherwise just stick to the defaults:
# apt-get install mini-buildd
Note
In case you are both, extraordinary hasty and adventurous, you may just run this:
? /usr/share/doc/mini-buildd/examples/auto-setup
This will basically try to run this whole section non-interactively, with all defaults. If you really just want a quick test-drive, this might be for you. All others should just read on.
Note
Read Setup below: Run the full prepare, check and activate treat (ugh!) from model’s list view to make them green.
Note
Using the wizards is mostly harmless; calling them is idempotent, and they will never touch any existing setup.
Enter the web application’s configuration section and login as superuser admin.
Daemon green? Go on.
Note
Daemon prepare will generate your instance ID (read: GnuPG key); you may need to generate some entropy (install haveged maybe) on the system if this stalls.
Note
The Daemon identity will herafter be referred to as ARCHIVE.
All wanted sources green? Go on.
Note
Setup of Sources will implicitly pull in architectures and components, and also implicitly sets up the apt keys associated to them. Purists may want to re-check them manually.
test repo green? Go on.
All wanted chroots green? Done!
Note
Preparing chroots may take a while; if you cancel the HTTP request in your browser, preparation will continue anyway.
Enter web application’s home (stay logged-in as admin).
Start the daemon.
Note
Just reload the home page to update the packager and builder status.
Note
Just show “Last packages”, and click on the keyring’s source package name to get to the package’s overview where you can migrate (also see the User’s Quickstart).
Optionally build the internal test packages.
Goal: Walk through the most important use cases.
Access API calls from the command line via mini-buildd-tool:
# apt-get install python-mini-buildd
The remaining Quickstart will just use mini-buildd-tool as example, however the API could also just be accessed via the web interface.
Setup the apt sources on your system somewhat like that:
# mini-buildd-tool HOST getsourceslist $(lsb_release -s -c) >/etc/apt/sources.list.d/my-mini-buildd.list
# apt-get update
# apt-get --allow-unauthenticated install ARCHIVE-archive-keyring
# apt-get update
A user account may be needed to, for example, create package subscriptions, access restricted API calls, or upload your GnuPG public key.
Install dput, and setup your ~/.dput.cf:
# apt-get install dput ? mini-buildd-tool HOST getdputconf >>~/.dput.cf
Upload authorization works via a GnuPG allowed keyring.
As this depends on the setup of the mini-buildd instance and/or repository your are using, this cannot be answered generically.
You will be able to upload to a repository when
? dput mini-buildd-ARCHIVE *.changes
You will always find the packages currently being build displayed here, plus a list of the last N packages build, and of course appropriate links to build logs, changes, etc.
You can search for (binary and source) package names via API:list:
? mini-buildd-tool HOST list '*-archive-keyring'
You can view a source package overview via the API:show call (put in your actual daemon identity):
? mini-buildd-tool HOST show ARCHIVE-archive-keyring
There are also find appropriate links to API::migrate, API::remove, API::port in this web page overview.
You will also find a convenience external port link on a repository overview web page to do and external port via API::portext.