Your message dated Fri, 25 Jul 2025 18:19:16 +0200
with message-id <[email protected]>
and subject line Re: devscripts: [uscan] In v5 watch file, is a single stanza 
also a source?
has caused the Debian Bug report #1109881,
regarding devscripts: [uscan] In v5 watch file, is a single stanza also a 
source?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1109881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109881
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: devscripts
Version: 2.25.15
Severity: normal
X-Debbugs-Cc: [email protected];[email protected]

Hi

In the beginning of the documentation of the v5 watch file format, we find that the first paragraph must contain `Version: 5` and that any other field present will be used as default for the *next* paragraphs.

However, many of the examples we find in the man page, at least as rendered on [manpages.debian.org], shows a single stanza with the `Version` embedded into it. One such is from manpages.d.o is:

```
Version: 5
Source: http://git.ao2.it/tweeper.git
Version-Regex: refs/tags/v@ANY_VERSION@
Git-Mode: full
Mode: git
```

My reading of the documentation was that this does nothing and should have been:

```
Version: 5

Source: http://git.ao2.it/tweeper.git
Version-Regex: refs/tags/v@ANY_VERSION@
Git-Mode: full
Mode: git
```

I do not actually know what `uscan` does here. My personal preference is to use the second variant, since it follows the logic of the `debian/control` file where the first stanza is a special stanza but some fields can be inherited into the subsequent stanzas. This means that code deb822 parsers already has some logic for this pattern. It will also simplify my work on editor support in `debputy`, where documentation is by stanza type. I admit that is also one of my drivers for this preference.

Best regards,
Niels

[manpages.debian.org]: https://manpages.debian.org/experimental/devscripts/debian-watch.5.en.html#direct_access_to_the_git_repository_(tags)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Yadd:
[...]

Ho, it's a bug in Debian website: in source (pod), the blank line exists. Same in code produced by pod2html or pod2markdown or pod2man.

Which tool is used to produce these manpages ?

Indeed. I digged a bit and found that I filed a similar bug in 2022 (https://github.com/Debian/debiman/issues/141), but managed to forget about it in the mean time.

Thanks for confirming and apologies for the noise.

Best regards,
Niels


Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to