Re: Policy Weekly Issue #4/4: Announcing new packages before uploading them
Fabrizio Polacco wrote:
> But this needs absolutely the opinion of Ian and/or Klee. Not only
> dinstall, but also all other programs that use the changelogfile must be
> modifyed, and back-compatibility have to be studied well.
What other programs? All I know of are dinstall and the perl library
/usr/lib/dpkg/parsechangelog/debian. (For all I know, dinstall uses the
library.) /usr/lib/dpkg/parsechangelog/debian will have no problems with
back-compatability. In fact, the closes= field will be optional.
> I've seen also, in another posting, that dpkg-parsechangelog was
> rejecting the closes= statement, changing to X-closes= or somethink like
> it.
Here is a simple patch to make /usr/lib/dpkg/parsechangelog/debian handle
the closes field:
--- /tmp/debian Thu Oct 30 01:09:01 1997
+++ /usr/lib/dpkg/parsechangelog/debian Thu Oct 30 01:19:18 1997
@@ -40,9 +40,9 @@
}
}
-%mapkv=(); # for future use
+%mapkv=(Closes=>Closes); # for future use
$i=100;grep($fieldimps{$_}=$i--,
- qw(Source Version Distribution Urgency Maintainer Date Changes));
+ qw(Source Version Distribution Urgency Maintainer Date Changes Closes));
$i=1;grep($urgencies{$_}=$i++,
qw(low medium routine high urgent emergency));
And here is a little patch to dpkg-genchanges to turrn off a warning message
it would print out otherwise:
--- /tmp/dpkg-genchanges Thu Oct 30 01:21:45 1997
+++ /usr/bin/dpkg-genchanges Thu Oct 30 01:24:46 1997
@@ -166,7 +166,7 @@
#print STDERR "L key >$_< value >$v<\n";
if (m/^Source$/) {
&setsourcepackage;
- } elsif (m/^(Version|Maintainer|Changes|Urgency|Distribution|Date)$/) {
+ } elsif (m/^(Version|Maintainer|Changes|Urgency|Distribution|Date|Closes)$/) {
$f{$_}= $v;
} elsif (s/^X[BS]*C[BS]*-//i) {
$f{$_}= $v;
By the way, with these modifications, a new field appears in the .changes
file:
Closes: 10011 10102 10121
Guy should find that easy enough to parse. :-)
--
see shy jo
Reply to: