/usr/share/doc/mini-buildd/html/quickstart.html is in mini-buildd 1.0.33.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Quickstart — mini-buildd 1.0.33 documentation</title>
<link rel="stylesheet" href="_static/classic.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: './',
VERSION: '1.0.33',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true,
SOURCELINK_SUFFIX: '.txt'
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<link rel="shortcut icon" href="/static/favicon.ico" />
<link rel="stylesheet" type="text/css" href="/static/css/sphinx.css" />
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="Administrator’s Manual" href="admin.html" />
<link rel="prev" title="Introduction" href="introduction.html" />
</head>
<body>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="admin.html" title="Administrator’s Manual"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="introduction.html" title="Introduction"
accesskey="P">previous</a> |</li>
<li><a title="mini-buildd Home" href="../"><img class="logo" src="_static/img/icon_48x48.png" alt="mini-buildd logo" /></a></li>
<li class="nav-item nav-item-0"><a href="index.html">mini-buildd 1.0.33 documentation</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="quickstart">
<h1>Quickstart<a class="headerlink" href="#quickstart" title="Permalink to this headline">¶</a></h1>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">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.</p>
</div>
<p>As a convention, we write code you should run as <code class="docutils literal"><span class="pre">root</span></code> like:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># apt-get install FOO</span>
</pre></div>
</div>
<p>and code you should run as <code class="docutils literal"><span class="pre">user</span></code> like:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>? mini-buildd-tool HOST status
</pre></div>
</div>
<p>In code snippets, names written all-capital (<code class="docutils literal"><span class="pre">FOO</span></code>, <code class="docutils literal"><span class="pre">HOST</span></code>)
are not meant literal but placeholders for customized values.</p>
<div class="section" id="administrator-s-quickstart">
<h2>Administrator’s Quickstart<a class="headerlink" href="#administrator-s-quickstart" title="Permalink to this headline">¶</a></h2>
<p><strong>Goal</strong>: Initial fully working setup with the sandbox
repository <code class="docutils literal"><span class="pre">test</span></code>.</p>
<div class="section" id="install">
<h3>Install<a class="headerlink" href="#install" title="Permalink to this headline">¶</a></h3>
<p>Prepare to set your admin password when installing, otherwise
just stick to the defaults:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># apt-get install mini-buildd</span>
</pre></div>
</div>
</div>
<div class="section" id="configure">
<h3>Configure<a class="headerlink" href="#configure" title="Permalink to this headline">¶</a></h3>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p>In case you are both, <strong>extraordinary hasty and
adventurous</strong>, you may just run this:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>? /usr/share/doc/mini-buildd/examples/auto-setup
</pre></div>
</div>
<p class="last">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. <strong>All others should just read on</strong>.</p>
</div>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Read <code class="docutils literal"><span class="pre">Setup</span></code> below: Run the full <code class="docutils literal"><span class="pre">prepare</span></code>,
<code class="docutils literal"><span class="pre">check</span></code> and <code class="docutils literal"><span class="pre">activate</span></code> treat (ugh!) from model’s
<em>list view</em> to make them green.</p>
</div>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Using the wizards is mostly harmless; calling them is
idempotent, and they will never touch any existing
setup.</p>
</div>
<ol class="arabic">
<li><p class="first">Enter the <a class="reference external" href="/admin/mini_buildd/">web application’s configuration section</a> and login as superuser <code class="docutils literal"><span class="pre">admin</span></code>.</p>
</li>
<li><dl class="first docutils">
<dt>Setup <strong>the Daemon</strong> (-> <a class="reference internal" href="admin.html#admin-daemon"><span class="std std-ref">Manual</span></a>).</dt>
<dd><ol class="first arabic simple">
<li>Edit the one Daemon instance. Get the <code class="docutils literal"><span class="pre">identity</span></code> and the <code class="docutils literal"><span class="pre">gnupg</span> <span class="pre">template</span></code> right, changing these later will call for trouble.</li>
<li><code class="docutils literal"><span class="pre">Setup</span></code> the Daemon instance.</li>
</ol>
<p>Daemon green? Go on.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Daemon <code class="docutils literal"><span class="pre">prepare</span></code> will generate your instance ID
(read: GnuPG key); you may need to generate some
<strong>entropy</strong> (install <code class="docutils literal"><span class="pre">haveged</span></code> maybe) on the
system if this stalls.</p>
</div>
<div class="last admonition note">
<p class="first admonition-title">Note</p>
<p class="last">The Daemon <code class="docutils literal"><span class="pre">identity</span></code> will hereafter be referred to as <code class="docutils literal"><span class="pre">ARCHIVE</span></code>.</p>
</div>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>Setup <strong>Sources</strong> (-> <a class="reference internal" href="admin.html#admin-sources"><span class="std std-ref">Manual</span></a>).</dt>
<dd><ol class="first arabic simple">
<li>Call at least one wizard for each: <em>Archives</em>, <em>Sources</em>, <em>PrioritySources</em>.</li>
<li><code class="docutils literal"><span class="pre">Setup</span></code> all the Sources you want to use.</li>
</ol>
<p>All wanted sources green? Go on.</p>
<div class="last admonition note">
<p class="first admonition-title">Note</p>
<p class="last"><code class="docutils literal"><span class="pre">Setup</span></code> 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.</p>
</div>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>Setup <strong>Repositories</strong> (-> <a class="reference internal" href="admin.html#admin-repositories"><span class="std std-ref">Manual</span></a>).</dt>
<dd><ol class="first arabic simple">
<li>Call these wizards, in this order: <em>Layouts:Defaults</em>, <em>Distributions:Defaults</em>, and finally <em>Repositories:Sandbox</em>.</li>
<li><code class="docutils literal"><span class="pre">Setup</span></code> the sandbox repository <code class="docutils literal"><span class="pre">test</span></code>.</li>
</ol>
<p class="last"><code class="docutils literal"><span class="pre">test</span></code> repository green? Go on.</p>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>Setup <strong>Chroots</strong> (-> <a class="reference internal" href="admin.html#admin-chroots"><span class="std std-ref">Manual</span></a>).</dt>
<dd><ol class="first arabic simple">
<li>Call the <em>DirChroot:Defaults</em> wizard.</li>
<li><code class="docutils literal"><span class="pre">Setup</span></code> all the Chroots you want to use.</li>
</ol>
<p>All wanted chroots green? Done!</p>
<div class="last admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Preparing chroots may take a while; if you cancel the HTTP request in your browser, preparation will continue anyway.</p>
</div>
</dd>
</dl>
</li>
</ol>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last"><strong>Don’t add or delete Uploader instances manually</strong>; these
are bound to users, and come automatically when new
users are created. The administrator only changes
these instances to grant rights.</p>
</div>
</div>
<div class="section" id="start-and-test">
<h3>Start and test<a class="headerlink" href="#start-and-test" title="Permalink to this headline">¶</a></h3>
<ol class="arabic">
<li><p class="first">Enter <a class="reference external" href="/mini_buildd/">web application’s home</a> (stay logged-in as <code class="docutils literal"><span class="pre">admin</span></code>).</p>
</li>
<li><p class="first"><strong>Start</strong> the daemon.</p>
</li>
<li><dl class="first docutils">
<dt><strong>Build keyring packages</strong>.</dt>
<dd><div class="first last admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Just reload the home page to update the packager and builder status.</p>
</div>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt><strong>Migrate</strong> the <strong>keyring packages</strong> up all staged suites (i.e. ->testing->stable).</dt>
<dd><div class="first last admonition note">
<p class="first admonition-title">Note</p>
<p class="last">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).</p>
</div>
</dd>
</dl>
</li>
<li><p class="first">Optionally <strong>build</strong> the internal test packages.</p>
</li>
</ol>
</div>
<div class="section" id="epilogue">
<h3>Epilogue<a class="headerlink" href="#epilogue" title="Permalink to this headline">¶</a></h3>
<div class="section" id="going-real-beyond-the-test-repository">
<h4>Going real (beyond the test repository)<a class="headerlink" href="#going-real-beyond-the-test-repository" title="Permalink to this headline">¶</a></h4>
<p>When your are confident with the test repository setup, just
create a new <code class="docutils literal"><span class="pre">Repository</span></code> instance with the actual <code class="docutils literal"><span class="pre">ID</span></code> you
want to use for production.</p>
<p>Think about how you want to do upload authorization for that
production repository; see <a class="reference internal" href="#authorization">authorization</a> below.</p>
</div>
</div>
</div>
<div class="section" id="user-s-quickstart">
<h2>User’s Quickstart<a class="headerlink" href="#user-s-quickstart" title="Permalink to this headline">¶</a></h2>
<p><strong>Goal</strong>: Walk through the most important use cases.</p>
<div class="section" id="bootstrap-a-system-s-apt-for-a-mini-buildd-archive">
<h3>“Bootstrap” a system’s APT for a mini-buildd archive<a class="headerlink" href="#bootstrap-a-system-s-apt-for-a-mini-buildd-archive" title="Permalink to this headline">¶</a></h3>
<p>The resp. archive’s <em>keyring package</em> includes both, the APT key
as well as a “library” of all sources available (for easy
integration via <code class="docutils literal"><span class="pre">/etc/apt/sources.list.d/</span></code>).</p>
<p>However, the <em>keyring package</em> also is <strong>in</strong> the archive, so we
need some initial fiddling to get it installed in the first
place.</p>
<p><strong>1st</strong>, on <a class="reference external" href="/mini_buildd/">mini-buildd’s home</a>, jump to the
repository overview page (if there are more than one, use the
repository you intend to actually use on the system
later). Select the <code class="docutils literal"><span class="pre">stable</span></code> suite of your base distribution’s
(i.e., squeeze, wheezy, jessie,…) APT line, and then:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># echo "APT_LINE" >/etc/apt/sources.list.d/tmp.list</span>
<span class="c1"># apt-get update</span>
<span class="c1"># apt-get --allow-unauthenticated install ARCHIVE-archive-keyring</span>
<span class="c1"># rm /etc/apt/sources.list.d/tmp.list</span>
</pre></div>
</div>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">You may also get the resp. APT line via
<code class="docutils literal"><span class="pre">mini-buildd-tool</span></code> via the <code class="docutils literal"><span class="pre">getsourceslist</span></code> API
call in case you have it installed already.</p>
</div>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">You may compare the key’ fingerprint (<code class="docutils literal"><span class="pre">apt-key</span>
<span class="pre">finger</span></code>) with the one on <a class="reference external" href="/mini_buildd/">mini-buildd’s home</a>. There might also be other means set
up by the local administrator to cross-verify the key.</p>
</div>
<p><strong>2nd</strong>, re-add the stable sources.list back in via
“sources.list library”, somewhat like:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># cd /etc/apt/sources.list.d</span>
<span class="c1"># ln -s /usr/share/mini-buildd/sources.list.d/CODENAME_ARCHIVE_REPO_stable.list .</span>
<span class="c1"># apt-get update</span>
</pre></div>
</div>
<p>Now you can <strong>opt in or out other sources</strong> from the archive
just by <em>adding or removing symlinks</em>.</p>
</div>
<div class="section" id="install-the-command-line-tool">
<h3>Install the command line tool<a class="headerlink" href="#install-the-command-line-tool" title="Permalink to this headline">¶</a></h3>
<p>Access API calls from the command line via <code class="docutils literal"><span class="pre">mini-buildd-tool</span></code>:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># apt-get install python-mini-buildd</span>
</pre></div>
</div>
<p>The remaining Quickstart will just use <code class="docutils literal"><span class="pre">mini-buildd-tool</span></code> as
example, however the API could also just be accessed via the web
interface.</p>
</div>
<div class="section" id="setup-your-user-account">
<h3>Setup your user account<a class="headerlink" href="#setup-your-user-account" title="Permalink to this headline">¶</a></h3>
<p>A user account may be needed to, for example, create package subscriptions, access restricted API calls, or upload your GnuPG public key.</p>
<ol class="arabic simple">
<li><a class="reference external" href="/accounts/register/">Register a user account</a>.</li>
<li><a class="reference external" href="/mini_buildd/accounts/profile/">Setup your profile</a> (package subscriptions, GnuPG key upload).</li>
</ol>
</div>
<div class="section" id="setup-dput">
<h3>Setup dput<a class="headerlink" href="#setup-dput" title="Permalink to this headline">¶</a></h3>
<p>Install <code class="docutils literal"><span class="pre">dput</span></code>, and setup your <code class="docutils literal"><span class="pre">~/.dput.cf</span></code>:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span># apt-get install dput
? mini-buildd-tool HOST getdputconf >>~/.dput.cf
</pre></div>
</div>
</div>
<div class="section" id="authorize-yourself-to-do-package-uploads">
<span id="authorization"></span><h3>Authorize yourself to do package uploads<a class="headerlink" href="#authorize-yourself-to-do-package-uploads" title="Permalink to this headline">¶</a></h3>
<p>Upload authorization works via a GnuPG <code class="docutils literal"><span class="pre">allowed</span></code> keyring.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">For the administrator: See
<code class="docutils literal"><span class="pre">/usr/share/doc/mini-buildd/examples/ssh-uploader-command</span></code>
should you be interested in manually setting up a
ssh-based authorization wrapper.</p>
</div>
<p>As this depends on the setup of the mini-buildd instance and/or
repository your are using, this cannot be answered generically.</p>
<p>You will be able to upload to a repository when</p>
<ol class="arabic simple">
<li>the repository you upload for has <strong>authorization disabled</strong>
completely (like in the sandbox repository <code class="docutils literal"><span class="pre">test</span></code>).</li>
<li>your key is included in the <strong>per-repository predefined GnuPG
keyrings</strong>.</li>
<li>your <strong>django user account</strong> profile has your GnuPG key uploaded, and
your account was approved and enabled for the repository.</li>
</ol>
<p>For the latter, the workflow is roughly:</p>
<div class="section" id="workflow-upload-authorization-via-django-user">
<h4>Workflow: Upload authorization via django user<a class="headerlink" href="#workflow-upload-authorization-via-django-user" title="Permalink to this headline">¶</a></h4>
<ol class="arabic simple">
<li><dl class="first docutils">
<dt>Create a new user account; either</dt>
<dd><ol class="first last loweralpha">
<li>the user does it itself via the <a class="reference external" href="/accounts/login/">web application’s account manager</a>, or</li>
<li>the administrator creates the user via the <a class="reference external" href="/admin/mini_buildd/">web application’s configuration section</a>.</li>
</ol>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>A GPG key is added to the user’s Uploader instance; either</dt>
<dd><ol class="first last loweralpha">
<li>the user uploads his GnuPG key via the <a class="reference external" href="/mini_buildd/accounts/profile/">user’s profile</a>, or</li>
<li>the administrator inserts the GnuPG key to the user’s Uploader instance via the <a class="reference external" href="/admin/mini_buildd/">web application’s configuration section</a>.</li>
</ol>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>The administrator (via <a class="reference external" href="/admin/mini_buildd/">web application’s configuration section</a>)</dt>
<dd><ul class="first last">
<li>verifies and approves the user’s GnuPG key by <em>activating</em> the user’s Uploader instance.</li>
<li>allows upload to specific repositories by <em>changing</em> the user’s Uploader instance.</li>
</ul>
</dd>
</dl>
</li>
</ol>
</div>
</div>
<div class="section" id="upload-packages-to-mini-buildd">
<h3>Upload packages to mini-buildd<a class="headerlink" href="#upload-packages-to-mini-buildd" title="Permalink to this headline">¶</a></h3>
<p>Just like always, via <code class="docutils literal"><span class="pre">dput</span></code>. For the default configuration
you get via <code class="docutils literal"><span class="pre">getdputconf</span></code> it’s something like:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>? dput mini-buildd-ARCHIVE FOO.changes
</pre></div>
</div>
</div>
<div class="section" id="control-your-package-build-results">
<h3>Control your package build results<a class="headerlink" href="#control-your-package-build-results" title="Permalink to this headline">¶</a></h3>
<ul class="simple">
<li><dl class="first docutils">
<dt>Per notify (read: Email): A notification mail is sent to</dt>
<dd><ul class="first last">
<li><em>the uploader</em> (unless the repository is not configured to
do so, or the mail address does not match the allowed list),</li>
<li><em>any subscriber</em> or</li>
<li>your Email is configured by the administrator to always be
notified for that repository.</li>
</ul>
</dd>
</dl>
</li>
<li>Per web on <a class="reference external" href="/mini_buildd/">mini-buildd’s home</a>: 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.</li>
</ul>
</div>
<div class="section" id="manage-packages">
<h3>Manage packages<a class="headerlink" href="#manage-packages" title="Permalink to this headline">¶</a></h3>
<p>You can <strong>search</strong> for (binary and source) package names via
<a class="reference external" href="/mini_buildd/api?command=list&pattern=*-archive-keyring">API:list</a>,
using shell-like patterns:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>? mini-buildd-tool HOST list '*-archive-keyring'
</pre></div>
</div>
<p>You can <strong>view a source package</strong> overview via the <a class="reference external" href="/mini_buildd/api?command=show&package=ARCHIVE-archive-keyring">API:show</a>
call (put in your actual daemon identity):</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>? mini-buildd-tool HOST show ARCHIVE-archive-keyring
</pre></div>
</div>
<p>You will find more options to manage packages like
<code class="docutils literal"><span class="pre">API::migrate</span></code>, <code class="docutils literal"><span class="pre">API::remove</span></code>, <code class="docutils literal"><span class="pre">API::port</span></code> in this web
page overview.</p>
</div>
<div class="section" id="porting-packages-automatic-no-changes-ports">
<h3>Porting packages (“automatic no-changes ports”)<a class="headerlink" href="#porting-packages-automatic-no-changes-ports" title="Permalink to this headline">¶</a></h3>
<p>You can automatically port packages already in the repository
(<code class="docutils literal"><span class="pre">API::port</span></code>) as well as arbitrary external source packages
(<code class="docutils literal"><span class="pre">API::portext</span></code>).</p>
<p>For <strong>internal ports</strong>, checkout the options you have in the source
package view; for <strong>external ports</strong>, go to <a class="reference external" href="/mini_buildd/">mini-buildd’s home</a> and check the options for the repositories.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Internal ports may also be triggered automatically on
uploads via a ‘magic lines’ in the Debian changelog,
see (-> <a class="reference internal" href="user.html#user-upload"><span class="std std-ref">Manual</span></a>).</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<h3><a href="index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Quickstart</a><ul>
<li><a class="reference internal" href="#administrator-s-quickstart">Administrator’s Quickstart</a><ul>
<li><a class="reference internal" href="#install">Install</a></li>
<li><a class="reference internal" href="#configure">Configure</a></li>
<li><a class="reference internal" href="#start-and-test">Start and test</a></li>
<li><a class="reference internal" href="#epilogue">Epilogue</a><ul>
<li><a class="reference internal" href="#going-real-beyond-the-test-repository">Going real (beyond the test repository)</a></li>
</ul>
</li>
</ul>
</li>
<li><a class="reference internal" href="#user-s-quickstart">User’s Quickstart</a><ul>
<li><a class="reference internal" href="#bootstrap-a-system-s-apt-for-a-mini-buildd-archive">“Bootstrap” a system’s APT for a mini-buildd archive</a></li>
<li><a class="reference internal" href="#install-the-command-line-tool">Install the command line tool</a></li>
<li><a class="reference internal" href="#setup-your-user-account">Setup your user account</a></li>
<li><a class="reference internal" href="#setup-dput">Setup dput</a></li>
<li><a class="reference internal" href="#authorize-yourself-to-do-package-uploads">Authorize yourself to do package uploads</a><ul>
<li><a class="reference internal" href="#workflow-upload-authorization-via-django-user">Workflow: Upload authorization via django user</a></li>
</ul>
</li>
<li><a class="reference internal" href="#upload-packages-to-mini-buildd">Upload packages to mini-buildd</a></li>
<li><a class="reference internal" href="#control-your-package-build-results">Control your package build results</a></li>
<li><a class="reference internal" href="#manage-packages">Manage packages</a></li>
<li><a class="reference internal" href="#porting-packages-automatic-no-changes-ports">Porting packages (“automatic no-changes ports”)</a></li>
</ul>
</li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="introduction.html"
title="previous chapter">Introduction</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="admin.html"
title="next chapter">Administrator’s Manual</a></p>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="_sources/quickstart.rst.txt"
rel="nofollow">Show Source</a></li>
</ul>
</div>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<div><input type="text" name="q" /></div>
<div><input type="submit" value="Go" /></div>
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="admin.html" title="Administrator’s Manual"
>next</a> |</li>
<li class="right" >
<a href="introduction.html" title="Introduction"
>previous</a> |</li>
<li><a title="mini-buildd Home" href="../"><img class="logo" src="_static/img/icon_48x48.png" alt="mini-buildd logo" /></a></li>
<li class="nav-item nav-item-0"><a href="index.html">mini-buildd 1.0.33 documentation</a> »</li>
</ul>
</div>
<div class="footer" role="contentinfo">
© Copyright 2018, 2013, mini-buildd maintainers.
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.6.5.
</div>
</body>
</html>
|