Merging upstream version 0.1.37.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 7 insertions, 4 deletions

diff --git a/debputy.pod b/debputy.pod
index f27c15f..3ce9b90 100644
--- a/debputy.pod
+++ b/debputy.pod
@@ -470,8 +470,10 @@ config snippets. This data will be cross referenced with the plugin provided dat
 detect files that B<debputy> (and its plugins) does not know about, but it cannot provide any additional
 information.
 
-This part requires B<debhelper (>= 13.12~)> to work fully. With older versions, the output will include am
-B<issues> denoting that B<dh_assistant> returned non-zero.
+This part requires B<< debhelper (>= 13.12~) >> to work fully. With older versions, the output will include an
+B<issues> attribute denoting that B<dh_assistant> returned non-zero. Additionally, with B<< debhelper (>= 13.16~) >>
+the command will also provide data about files associated with some B<dh_>-commands not active with the
+current set of B<dh> addons.
 
 When B<dh_assistant list-guessed-dh-config-files> is missing a file, it is typically because the command
 that uses that config file is not introspectable. Typically, that can be fixed by patching the command
@@ -482,9 +484,10 @@ to include a command line a la:
 Assuming the command uses B<pkgfile($package, "foo")> from L<Debian::Debhelper::Dh_Lib> to look up the
 config file.
 
-Notable case that will never work is F<debian/foo.service> where there is no B<foo> package in
+Notable case that will likely not work is F<debian/foo.service> where there is no B<foo> package in
 F<debian/control> but F<debian/rules> calls B<dh_installsystemd --name foo>. This holds equally for
-all debhelper config files and related commands.
+all debhelper config files and related commands. Here, the resulting file (if detected at all) might
+be associated with the wrong package.
 
 =back