.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "DEBOCKER" "8" "July 2015" "Debian" "debocker"
+.TH "DEBOCKER" "8" "August 2015" "Debian" "debocker"
.
.SH "NAME"
\fBdebocker\fR \- build Debian packages with docker
\fBDebocker\fR builds Debian packages inside docker\. The build process is contained in docker images and (almost) no other tools are needed to develop Debian packages on the main system\. Moreover, docker\'s image cache reuses the same system state whenever possible\. In particular, when a package is built for the second time, its dependecies and buildchain are not downloaded nor installed again\.
.
.P
+\fBDo not use debocker to build packages that will will be uploaded to the Debian archive\fR, unless you use a trusted Debian base image (I mean it)\. Currently, \fBdebocker\fR uses Debian images from Docker registry which cannot be trusted for such use\.
+.
+.P
\fBDebocker\fR is also able to create a self\-contained \fIbundle\fR with everything necessary to build a package with docker only\.
.
.P
The build process consists of 5 steps:
.
.IP "1." 4
-\fIuprade\fR \- the base image is updated to the most recent packages (with apt\-get)
+\fIupgrade\fR \- the base image is updated to the most recent packages (with apt\-get)
.
.IP "2." 4
\fIinstall\-utils\fR \- the Debian toolchain is installed
And probably many more\.
.
.SH "AUTHOR"
-Initial idea and coding has been done by Tomasz Buchert \fItomasz@debian\.org\fR\.
+Initial idea and coding has been done by Tomasz Buchert\.
.
.P
Initial packaging, many ideas and a lot of support by Dariusz Dwornikowski\.
The semi\-official homepage is \fIhttp://debocker\.debian\.net\fR\.
.
.SH "SEE ALSO"
-pbuiler(8), docker(1), devscripts(1), pristine\-tar(1)
+pbuilder(8), docker(1), devscripts(1), pristine\-tar(1)
particular, when a package is built for the second time, its
dependecies and buildchain are not downloaded nor installed again.</p>
+<p><strong>Do not use debocker to build packages that will will be uploaded to
+the Debian archive</strong>, unless you use a trusted Debian base image (I
+mean it). Currently, <strong>debocker</strong> uses Debian images from Docker
+registry which cannot be trusted for such use.</p>
+
<p><strong>Debocker</strong> is also able to create a self-contained <em>bundle</em> with
everything necessary to build a package with docker only.</p>
<p>The build process consists of 5 steps:</p>
<ol>
-<li> <em>uprade</em> - the base image is updated to the most recent
+<li><em>upgrade</em> - the base image is updated to the most recent
packages (with apt-get)</li>
-<li> <em>install-utils</em> - the Debian toolchain is installed</li>
-<li> <em>install-deps</em> - the build dependencies of the package are
+<li><em>install-utils</em> - the Debian toolchain is installed</li>
+<li><em>install-deps</em> - the build dependencies of the package are
installed</li>
-<li> <em>extract-source</em> - the source package is extracted</li>
-<li> <em>build</em> - the proper build is executed</li>
+<li><em>extract-source</em> - the source package is extracted</li>
+<li><em>build</em> - the proper build is executed</li>
</ol>
<h2 id="AUTHOR">AUTHOR</h2>
-<p>Initial idea and coding has been done by Tomasz Buchert
-<a href="mailto:tomasz@debian.org" data-bare-link="true">tomasz@debian.org</a>.</p>
+<p>Initial idea and coding has been done by Tomasz Buchert.</p>
<p>Initial packaging, many ideas and a lot of support by Dariusz
Dwornikowski.</p>
<h2 id="SEE-ALSO">SEE ALSO</h2>
-<p><span class="man-ref">pbuiler<span class="s">(8)</span></span>, <span class="man-ref">docker<span class="s">(1)</span></span>, <span class="man-ref">devscripts<span class="s">(1)</span></span>, <span class="man-ref">pristine-tar<span class="s">(1)</span></span></p>
+<p><span class="man-ref">pbuilder<span class="s">(8)</span></span>, <span class="man-ref">docker<span class="s">(1)</span></span>, <span class="man-ref">devscripts<span class="s">(1)</span></span>, <span class="man-ref">pristine-tar<span class="s">(1)</span></span></p>
<ol class='man-decor man-foot man foot'>
<li class='tl'>Debian</li>
- <li class='tc'>July 2015</li>
+ <li class='tc'>August 2015</li>
<li class='tr'>debocker(8)</li>
</ol>
particular, when a package is built for the second time, its
dependecies and buildchain are not downloaded nor installed again.
+**Do not use debocker to build packages that will will be uploaded to
+the Debian archive**, unless you use a trusted Debian base image (I
+mean it). Currently, **debocker** uses Debian images from Docker
+registry which cannot be trusted for such use.
+
**Debocker** is also able to create a self-contained *bundle* with
everything necessary to build a package with docker only.
The build process consists of 5 steps:
- 1. *uprade* - the base image is updated to the most recent
+ 1. *upgrade* - the base image is updated to the most recent
packages (with apt-get)
2. *install-utils* - the Debian toolchain is installed
3. *install-deps* - the build dependencies of the package are
## AUTHOR
-Initial idea and coding has been done by Tomasz Buchert
-<tomasz@debian.org>.
+Initial idea and coding has been done by Tomasz Buchert.
Initial packaging, many ideas and a lot of support by Dariusz
Dwornikowski.
## SEE ALSO
-pbuiler(8), docker(1), devscripts(1), pristine-tar(1)
+pbuilder(8), docker(1), devscripts(1), pristine-tar(1)