Custom changelog parsers must be updated for lenny+1

diff --git a/ChangeLog b/ChangeLog
index 4aa496c2f9a5676202a22afe304efe49021eb08e..06274c19bdafb96331658a2f59bc31ddd5b79123 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,6 +2,8 @@
 
        * README.feature-removal-schedule: Deprecate support of substvars
        in dpkg-source and dpkg-genchanges.
+       * README.feature-removal-schedule, README.api: Deprecate support
+       of custom changelog parsers that understand only the -v option.
 
 2008-01-27  Raphael Hertzog  <hertzog@debian.org>
 

diff --git a/README.api b/README.api
index 9eb10dd6a141ab721d3c74b502c3a1f952b80f6e..d918df116d42bf09a7c652d3de960ef593071fc3 100644 (file)
--- a/README.api
+++ b/README.api
@@ -8,3 +8,15 @@ Description:
  The API provided by these modules is not yet stable, it's only supposed to
  be used internally by dpkg for now.
 
+What: custom changelog parsers in /usr/lib/dpkg/parsechangelog
+Status: stable
+Version: 2.0
+Description:
+ Since dpkg 1.14.16, the set of command-line options that custome
+ changelog parsers must support has been expanded (see
+ dpkg-parsechangelog(1)). For compatibility, changelog parsers supporting
+ only the old options are supported in lenny. In lenny+1, that support
+ will be dropped.
+ .
+ For reference, only the -v option was supported in version 1.0 of this
+ API.

diff --git a/README.feature-removal-schedule b/README.feature-removal-schedule
index f3b6cfc93c935a0415dd46511e60ca48c980c048..4d3517eef158459c41514521b46395eda73e31b8 100644 (file)
--- a/README.feature-removal-schedule
+++ b/README.feature-removal-schedule
@@ -71,3 +71,16 @@ Why:
  substvars do not make sense during generation of .dsc and .changes files.
  This also means that it won't be possible anymore to override the Format
  field output by dpkg-genchanges.
+
+What: support of custom changelog parsers understanding only -v
+Status: obsolete
+When: lenny+1
+Warning: none
+Why:
+ The debian changelog parser has been enhanced. It supports new options
+ that enable more fine-grained retrieval of information. Those new options
+ will be used by scripts (like dpkg-genchanges).
+ .
+ Custom changelog parsers must be updated to support the new API (see
+ dpkg-parsechangelog(1) and README.api).
+