maintainer and closes all the bugs marked as fixed by the upload, and the
auto-builders may start recompiling it. The package is now publicly accessible
at <ulink url="&url-incoming;"></ulink> until it is really
maintainer and closes all the bugs marked as fixed by the upload, and the
auto-builders may start recompiling it. The package is now publicly accessible
at <ulink url="&url-incoming;"></ulink> until it is really
called the `dinstall run' for historical reasons); the package is then removed
from incoming and installed in the pool along with all the other packages.
Once all the other updates (generating new <filename>Packages</filename> and
called the `dinstall run' for historical reasons); the package is then removed
from incoming and installed in the pool along with all the other packages.
Once all the other updates (generating new <filename>Packages</filename> and
<para>
The archive maintenance software will also send the OpenPGP/GnuPG signed
<filename>.changes</filename> file that you uploaded to the appropriate mailing
<para>
The archive maintenance software will also send the OpenPGP/GnuPG signed
<filename>.changes</filename> file that you uploaded to the appropriate mailing
to <literal>stable</literal>, the announcement is sent to
&email-debian-changes;. If a package is released with
to <literal>stable</literal>, the announcement is sent to
&email-debian-changes;. If a package is released with
<literal>experimental</literal>, the announcement will be posted to
&email-debian-devel-changes; instead.
</para>
<literal>experimental</literal>, the announcement will be posted to
&email-debian-devel-changes; instead.
</para>