general info

piuparts runs on piuparts.cs.helsinki.fi aka piatti.debian.org and just like lintian and linda should be run on every developer machine before uploading

piuparts logs (currently outdated) are available at [http://piatti.debian.org http://piatti.debian.org]

#debian-qa is the irc-channel to coordinate work on irc, piuparts-devel is the project name on alioth.

how to run piuparts on piatti

the piuparts stuff is partly in the piupartsm account (master end, including debmirroring), and partly in the piuartss account (the slave, which actually runs piuparts)

run piuparts-slave.py as piupartss and watch it run via screen. the slave starts the master when it needs it, you don't need to start it manually

also read http://liw.iki.fi/liw/debian/piuparts-logfile-processing-howto

If you want to help, please don't bother liw, h01ger has access too and you should bother him.

... to be continued! ...

troubleshouting/maintainance

Sometimes the chroot tarballs in /home/piupartss/ need to be removed, currently there are sid.tar.gz and sarge.tar.gz

see /etc/piuparts/piuparts-slave.conf

developing piuparts

• alioth project

• http://wiki.debian.org/SummerOfCode2007/PiupartsImprovements

random todo-stuff

• split /fails/ into more directories

• <liw> (at some point) you may want to run as piupartsm the bin/mirror-debian script

• look at the irssi_away script to see how to monitor screen sessions, to notify when piuparts is hanging
• backup /etc (and?)