| 8 |
====== |
====== |
| 9 |
|
|
| 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/uploading.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. |
| 20 |
|
|
| 21 |
Use debdiff, interdiff etc. |
Use debdiff, interdiff etc. Use debdiff on the binary packages, too. |
| 22 |
|
|
| 23 |
The distribution needs to be "testing-security". |
The distribution needs to be "testing-security". |
| 24 |
|
|
| 25 |
|
If you append something to the version number currently in testing, use something |
| 26 |
|
like "+lenny1" or ".0lenny1". A simple "lenny1" is not enough because of binNMUs |
| 27 |
|
adding "+b1". |
| 28 |
|
|
| 29 |
dcut does not seem to work on security-master.debian.org, but someone |
dcut does not seem to work on security-master.debian.org, but someone |
| 30 |
in the sec_public group (micah, neilm, sf, jmm) can remove broken |
in the sec_public group (micah, neilm, sf, jmm) can remove broken |
| 31 |
files from the upload queue when needed. |
files from the upload queue when needed. |
| 45 |
Autobuilds |
Autobuilds |
| 46 |
========== |
========== |
| 47 |
|
|
|
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 |
|
|
|
|
| 48 |
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 |
| 49 |
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 |
| 50 |
[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 |
| 55 |
Some time after the buildd has received the signed .changes, it will |
Some time after the buildd has received the signed .changes, it will |
| 56 |
upload the packages to klecker to |
upload the packages to klecker to |
| 57 |
/org/security.debian.org/queue/unembargoed/. "dak queue-report" gives |
/org/security.debian.org/queue/unembargoed/. "dak queue-report" gives |
| 58 |
an overview, what packges have arrived in the queue. |
an overview, what packages have arrived in the queue. |
| 59 |
|
|
| 60 |
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]. |
| 61 |
|
|
| 81 |
You can install the packages in the security archive with something |
You can install the packages in the security archive with something |
| 82 |
like: |
like: |
| 83 |
|
|
| 84 |
dak new-security-install DTSA-36-1 mydns_1.1.0-7.1lenny1_*.changes |
dak new-security-install DTSA-36-1 mydns_1.1.0-7+lenny1_*.changes |
| 85 |
|
|
| 86 |
DTSA-36-1 is an identifier that should be the name of the new DTSA. |
DTSA-36-1 is an identifier that should be the name of the new DTSA. |
| 87 |
However, every identifier can be used only once with dak. So if you |
However, every identifier can be used only once with dak. So if you |
Parent Directory
| 
Revision Log
| 
Patch