Scott Kitterman wrote:
> <listitem>
> <para>
> The <systemitem role="package">spf-milter-python</systemitem>
> package
> will be removed in the Bullseye release. It is replaced by the
[...]
> <listitem>
> <para>
> The <systemitem role="package">dkim-milter-python</systemitem>
> package
> will be removed in the Bullseye release. It is replaced by the
I'd like to suggest a less repetitive version:
<listitem>
<para>
The packages <systemitem role="package">spf-milter-python</systemitem>
and <systemitem role="package">dkim-milter-python</systemitem> are no
longer
actively developed upstream, but their more feature-rich replacements,
<systemitem role="package">pyspf-milter</systemitem> and <systemitem
role="package">dkimpy-milter</systemitem>, are available in buster.
Users
should migrate to the new packages before the old ones are removed in
bullseye.
</para>
</listitem>
Releasenames are usually lowercase, or of course we could use
&releasename; and &nextreleasename;.
The attached patch puts this at the end of "deprecated-components".
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/issues.dbk b/en/issues.dbk
index 11a50932..83c89ce9 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -202,6 +202,16 @@ information mentioned in <xref linkend="morereading"/>.
under active development.
</para>
</listitem>
+ <listitem>
+ <para>
+ The packages <systemitem role="package">spf-milter-python</systemitem>
+ and <systemitem role="package">dkim-milter-python</systemitem> are no longer
+ actively developed upstream, but their more feature-rich replacements,
+ <systemitem role="package">pyspf-milter</systemitem> and <systemitem
+ role="package">dkimpy-milter</systemitem>, are available in buster. Users
+ should migrate to the new packages before the old ones are removed in bullseye.
+ </para>
+ </listitem>
</itemizedlist>
</section>
