using schroot in debian.org porterboxes
=======================================

When logging into Debian porterbox machine, it should display similar message:
<pre><code>
Welcome to porterbox.debian.org, the Debian arch porterbox.

See 'schroot -l' for a list of available chroots.  Start new sessions
with 'schroot --begin-session -c <chroot>', run commands in sessions using
'schroot --run-session -c <session> [-- command]', and tear down sessions
using 'schroot --end-session -c <session>'.  You can run a limited set of
privileged commands, for instance some of apt-get, using
'dd-schroot-cmd -c <session> <command>'.
Use 'schroot --list --all-sessions' or 'schroot-list-sessions [<userglob>]'
to list (your) open sessions.

This server is hosted at data centre.
</code></pre>

The previous description is rather compact and dense, so let's try to describe the usage in more friendly way.

* List available chroots:
<pre><code>
	$ schroot -l
</code></pre>

* Begin a persistent schroot session on Debian unstable:
<pre><code>
	$ schroot -b -c sid -n mysid
</code></pre>

* Update and upgrade Debian unstable chroot:
<pre><code>
	$ dd-schroot-cmd -c mysid apt-get update
	$ dd-schroot-cmd -c mysid apt-get upgrade
	[..]
	Do it for real [Y/n]: <Enter>
	[..]
</code></pre>

* Install your broken package build dependencies:
<pre><code>
	$ dd-schroot-cmd -c mysid apt-get build-dep gentoo
	[..]
	Do it for real [Y/n]: <Enter>
	[..]
</code></pre>

* Change root to Debian unstable chroot:
<pre><code>
	$ schroot -r -c mysid
</code></pre>

* Download your broken package source:
<pre><code>
	(sid_arch-dchroot)user@porterbox:~$ apt-get source gentoo
</code></pre>

* You should be able to reproduce your issue, hack on the package, fix the bug. Once you are done with your work, please, finish your schroot session:
<pre><code>
	(sid_arch-dchroot)user@porterbox:~$ exit
	$ schroot -e -c mysid
	$ exit
</code></pre>

* You should be done by now. If you find any issue, please report to debian-admin@lists.debian.org.