|
Size: 832
Comment:
|
Size: 941
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| 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 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 :) |
| Line 9: | Line 9: |
| = how to run piuparts = | = how to run piuparts on piatti = |
| Line 14: | Line 14: |
If you want to help, please don't bother liw, h01ger has access too and you should bother him. |
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)
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.
random todo-stuff
inspect the cronjobs..
<liw> (at some point) you may want to run as piupartsm the bin/mirror-debian script
.. to be continued...