Control: tags -1 confirmed patch Control: found -1 1.2.9-2 Dear English Localization Team,
Please review the attached patch for fixing the issue reported below. The current template can be found here: https://salsa.debian.org/debian/wireshark/blob/debian/master/debian/templates Thank you, Balint On Sun, Sep 8, 2019 at 6:36 PM Nils Dagsson Moskopp <nils+debian-report...@dieweltistgarnichtso.net> wrote: > > Package: wireshark > Version: 2.6.7-1~deb9u1 > Severity: minor > > Dear Maintainer, > > in the pre-install notification about installing dumpcamp so that > non-root users can capture packets it is displayed that users can > read about that feature in the file at the following path: > > /usr/share/doc/wireshark-common/README.Debian > > A file does not actually exist at the path. > After installation, it does also not exist. > However, the following path holds the file: > > /usr/share/doc/wireshark-common/README.Debian.gz > > I suggest to change path in the question and make it clear that the > file will only exist after the package is installed – even though a > text mentioning it might be shown before installation is completed. -- Balint Reczey Ubuntu & Debian Developer
From 38256c713614c857c43692ab153c369b721ac42b Mon Sep 17 00:00:00 2001 From: Balint Reczey <balint.rec...@canonical.com> Date: Sun, 8 Sep 2019 22:30:10 +0200 Subject: [PATCH] debian/templates: Fix README.Debian's path and not that it needs to be installed Change-Id: I7ebc987a8956122e1bb283d33ec3c989c5d83330 Closes: #939770 --- debian/templates | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/debian/templates b/debian/templates index dc47130770..66fb399ae2 100644 --- a/debian/templates +++ b/debian/templates @@ -17,7 +17,8 @@ _Description: Should non-superusers be able to capture packets? less of the code will run with elevated privileges. . For more detailed information please see - /usr/share/doc/wireshark-common/README.Debian. + /usr/share/doc/wireshark-common/README.Debian.gz after the package + installation is finished. . Enabling this feature may be a security risk, so it is disabled by default. If in doubt, it is suggested to leave it disabled. -- 2.17.1