From 8b8344c3982326d9c9b99e7bca8e667746b77691 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Mon, 17 Jun 2024 18:40:52 +0200 Subject: Merging upstream version 0.1.37. Signed-off-by: Daniel Baumann --- debputy.pod | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'debputy.pod') 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 (and its plugins) does not know about, but it cannot provide any additional information. -This part requires B= 13.12~)> to work fully. With older versions, the output will include am -B denoting that B returned non-zero. +This part requires B<< debhelper (>= 13.12~) >> to work fully. With older versions, the output will include an +B attribute denoting that B returned non-zero. Additionally, with B<< debhelper (>= 13.16~) >> +the command will also provide data about files associated with some B-commands not active with the +current set of B addons. When B 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 from L to look up the config file. -Notable case that will never work is F where there is no B package in +Notable case that will likely not work is F where there is no B package in F but F calls B. 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 -- cgit v1.2.3