| 10 |
The upload can be done by any DD and is described in |
The upload can be done by any DD and is described in |
| 11 |
.../website/index.html. |
.../website/index.html. |
| 12 |
|
|
| 13 |
|
If the orig.tar.gz is already on security.debian.org (either stable-security |
| 14 |
|
or testing-security), then DON'T include it. Otherwise a bug in dak will |
| 15 |
|
prevent the buildds from building it. |
| 16 |
|
|
| 17 |
It is a good idea to check in the buildlog that all new patches |
It is a good idea to check in the buildlog that all new patches |
| 18 |
actually get applied. Maybe you forgot to put them in patches/series |
actually get applied. Maybe you forgot to put them in patches/series |
| 19 |
or because of some bug dpatch ignored a patch. |
or because of some bug dpatch ignored a patch. |
| 41 |
Autobuilds |
Autobuilds |
| 42 |
========== |
========== |
| 43 |
|
|
|
There seems to be a bug in dak: If the orig.tar.gz is already in |
|
|
stable-security, the orig.tar.gz is not symlinked into the |
|
|
buildd/lenny directory and the buildds cannot download the source. |
|
|
Workaround: Ask aj to create the symlink manually |
|
|
|
|
| 44 |
When you have the buildlogs and the builds look ok, you have to sign |
When you have the buildlogs and the builds look ok, you have to sign |
| 45 |
the changes file embedded in the buildlog and send it to the buildd |
the changes file embedded in the buildlog and send it to the buildd |
| 46 |
[1]. If you use your own script to do that: the Subject needs to be |
[1]. If you use your own script to do that: the Subject needs to be |
| 51 |
Some time after the buildd has received the signed .changes, it will |
Some time after the buildd has received the signed .changes, it will |
| 52 |
upload the packages to klecker to |
upload the packages to klecker to |
| 53 |
/org/security.debian.org/queue/unembargoed/. "dak queue-report" gives |
/org/security.debian.org/queue/unembargoed/. "dak queue-report" gives |
| 54 |
an overview, what packges have arrived in the queue. |
an overview, what packages have arrived in the queue. |
| 55 |
|
|
| 56 |
If a buildd has problems: A list with the admins is at [3]. |
If a buildd has problems: A list with the admins is at [3]. |
| 57 |
|
|