This is an automated email from the git hooks/post-receive script.

guillem pushed a commit to branch main
in repository dpkg.

View the commit online:
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=e6eb9f0b8db30b23453a3ec9b960ce92e8150e69

commit e6eb9f0b8db30b23453a3ec9b960ce92e8150e69 (HEAD -> main)
Author: Guillem Jover <guil...@debian.org>
AuthorDate: Fri Oct 13 20:38:38 2023 +0200

    man: Document all dpkg-parsechangelog(1) output fields
    
    These were not documented as they were supposedly obvious, but not doing
    so is more confusing, as it looks as if the following ones being
    documented also cover previously undocumented ones. Or their semantics
    might not be as obvious as expected.
---
 man/dpkg-parsechangelog.pod | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/man/dpkg-parsechangelog.pod b/man/dpkg-parsechangelog.pod
index 4a6ffb182..5524be532 100644
--- a/man/dpkg-parsechangelog.pod
+++ b/man/dpkg-parsechangelog.pod
@@ -98,10 +98,19 @@ first entry (usually the most recent entry), except 
otherwise stated:
 
 =item B<Source:> I<pkg-name>
 
+The source package name.
+
 =item B<Version:> I<version>
 
+The source version number.
+B<Note>: For binary-only releases there might be no corresponding source
+release.
+
 =item B<Distribution:> I<target-distribution>
 
+A space-separated list of one or more distribution names where this version
+should be installed when it is uploaded.
+
 =item B<Urgency:> I<urgency>
 
 The highest urgency of all included entries is used, followed by the

-- 
Dpkg.Org's dpkg

Reply via email to