| 69 |
<h1>Uploads to the secure-testing repository</h1> |
<h1>Uploads to the secure-testing repository</h1> |
| 70 |
|
|
| 71 |
<p> |
<p> |
| 72 |
To upload a package to the secure-testing repository, follow this |
To upload a package to the secure-testing repository, any Debian |
| 73 |
checklist: |
developer may follow this checklist: |
| 74 |
<ol> |
<ol> |
| 75 |
<li>Only upload changes that have already been made in |
<li>Only upload changes that have already been made in |
| 76 |
unstable and are blocked by reaching testing by some other |
unstable and are blocked by reaching testing by some other |
| 79 |
breaking secure-testing too badly with fixes that have not |
breaking secure-testing too badly with fixes that have not |
| 80 |
been tested first in unstable.</li> |
been tested first in unstable.</li> |
| 81 |
<li>Only make uploads for issues that the testing security |
<li>Only make uploads for issues that the testing security |
| 82 |
team plans to issue a DTSA announcement for.</li> |
team plans to issue a DTSA announcement for. It is best to |
| 83 |
|
contact the team first to avoid duplicate work.</li> |
| 84 |
<li>Use a version number that is less than the version |
<li>Use a version number that is less than the version |
| 85 |
number of the fix in unstable, but greater than the version |
number of the fix in unstable, but greater than the version |
| 86 |
number of the fix in testing. For example, if the fix is in |
number of the fix in testing. For example, if the fix is in |
| 91 |
<li>Use "testing" as the distribution in the |
<li>Use "testing" as the distribution in the |
| 92 |
changelog.</li> |
changelog.</li> |
| 93 |
<li>Build the package in a testing chroot using pbuilder |
<li>Build the package in a testing chroot using pbuilder |
| 94 |
so that all the dependencies are ok.</li> |
so that all the dependencies are ok. Be sure to build with |
| 95 |
|
the -sa switch to include source, unless the source is |
| 96 |
|
already in the secure-testing archive. |
| 97 |
|
</li> |
| 98 |
<li>Test the package.</li> |
<li>Test the package.</li> |
| 99 |
<li>Sign the package. Any Debian developer in the keyring |
<li>Sign the package. Any Debian developer in the keyring |
| 100 |
can do so.</li> |
can do so.</li> |
| 118 |
</pre> |
</pre> |
| 119 |
Build logs can be found |
Build logs can be found |
| 120 |
<a href="http://experimental.debian.net/">here</a>. |
<a href="http://experimental.debian.net/">here</a>. |
| 121 |
|
Once everything is ready, contact a team member to issue a |
| 122 |
|
DSTA. |
| 123 |
</li> |
</li> |
| 124 |
<li> |
</ol> |
| 125 |
Once everything is ready, contact a team member to create a DTSA annoucement |
|
| 126 |
(using data/DTSA/mkadvisory), contact a secure-testing-master admin |
<p> |
| 127 |
to move the upload from etch-proposed-updates to |
To issue a DTSA, team members follow this checklist: |
| 128 |
|
<ol> |
| 129 |
|
<li>Make sure everything is ready. |
| 130 |
|
<li>cd data/DTSA; ./mkadvisory</li> |
| 131 |
|
<li>svn add DTSA-n-1; svn commit</li> |
| 132 |
|
<li>Contact a secure-testing-master admin to move the upload from etch-proposed-updates to |
| 133 |
etch (using something like this, but the procedure is still being worked out: |
etch (using something like this, but the procedure is still being worked out: |
| 134 |
madison -s etch-proposed-updates -f heidi -S $package | sudo -u katie heidi -a etch) |
madison -s etch-proposed-updates -f heidi -S $package | sudo -u katie heidi -a etch; touch /org/secure-testing.debian.net/RUN-DINSTALL) |
| 135 |
and send the signed DTSA to secure-testing-announce. |
and send the signed DTSA to secure-testing-announce. |
| 136 |
</li> |
</li> |
| 137 |
|
<li>Make sure that the debs are in place. Note that |
| 138 |
|
dinstall runs at 20 and 50 past the hour. |
| 139 |
|
<li>cd data/DTSA; ./sndadvisory DTSA-n-1</li> |
| 140 |
</ol> |
</ol> |
| 141 |
</p> |
</p> |
| 142 |
|
|