Your message dated Mon, 07 Jan 2019 16:21:26 +0000
with message-id <e1ggxey-000gnn...@fasolo.debian.org>
and subject line Bug#916699: fixed in minissdpd 1.5.20180223-4
has caused the Debian Bug report #916699,
regarding Run minissdpd debconf question insufficiently detailed for an 
advanced user to answer it
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 ow...@bugs.debian.org
immediately.)


-- 
916699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: minissdpd
version: 1.5.20180223-3

Hi.  Minissdpd got pulled in on an upgrade from stretch to buster by
something--I haven't bothered to check why.  I have my debconf priority
set to medium and I got asked whether I wanted to start minissdpd
automatically.
That's fine: I asked for more questions and I got them.
However, the question didn't explain what minissdpd was, why I might
want it, and on a typical system what the consequences of not running it
might be.

You need to write debconf questions targeted both at someone who
explicitly asks for your package and that roughly knows what it is as
well as for someone who gets a package pulled in by someone else.  I'm a
fairly advanced user; I know what UPNP is c.  So, I'm not asking you to
make a medium/low priority question something a novice user could
answer, but I am asknig you to include enough detail that I can probably
answer it and definitely know what to google.
It wasn't even clear that the question was from the minissdpd package.

--Sam

--- End Message ---
--- Begin Message ---
Source: minissdpd
Source-Version: 1.5.20180223-4

We believe that the bug you reported is fixed in the latest version of
minissdpd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yangfl <mmyan...@gmail.com> (supplier of updated minissdpd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 07 Jan 2019 00:01:42 +0800
Source: minissdpd
Binary: minissdpd
Architecture: source amd64
Version: 1.5.20180223-4
Distribution: unstable
Urgency: medium
Maintainer: Thomas Goirand <z...@debian.org>
Changed-By: Yangfl <mmyan...@gmail.com>
Description:
 minissdpd  - keep memory of all UPnP devices that announced themselves
Closes: 908585 908586 910399 916699
Changes:
 minissdpd (1.5.20180223-4) unstable; urgency=medium
 .
   * Add a upgrade-only debconf note (Closes: #916699).
   * Remove START_DAEMON in /etc/default/miniupnpd (Closes: #908585).
   * Support specifying multiple interface names (Closes: #908586).
   * Add Portuguese Debconf translations, thanks to Américo Monteiro
     (Closes: #910399).
   * Add autopkgtest.
   * Bump Standards-Version to 4.3.0.
   * Bump debhelper compat to 12.
Checksums-Sha1:
 2aec7d84e47c16b60c737a1affc5054a364fb5fd 2065 minissdpd_1.5.20180223-4.dsc
 92b2476d49abbac4b79b1f2c56a46cbd47dcce9b 13128 
minissdpd_1.5.20180223-4.debian.tar.xz
 ab90cd2bd4a408b2f3438fb254cf2494384fedff 56148 
minissdpd-dbgsym_1.5.20180223-4_amd64.deb
 bb94da2a041929b8b517fe1768afee18851fc041 5724 
minissdpd_1.5.20180223-4_amd64.buildinfo
 67b9adbd6ed5667688c04c424d691efcd3f38d6a 33108 
minissdpd_1.5.20180223-4_amd64.deb
Checksums-Sha256:
 d8d845d41f9f9c1eeffdcd9192927e477cd6c1767dde8428a53840148690cc80 2065 
minissdpd_1.5.20180223-4.dsc
 00b4f792a15e339933ff0cbfb4c9325266e30c964a6a7ed575beac0a43a71521 13128 
minissdpd_1.5.20180223-4.debian.tar.xz
 4a4e227c8548e16dc773d38932835254fed42c91d306c21e330cb53fd17ade56 56148 
minissdpd-dbgsym_1.5.20180223-4_amd64.deb
 9f20d5e2af802d1757edcffc45809470d19385c0a153c4580b2fa9038c1d2740 5724 
minissdpd_1.5.20180223-4_amd64.buildinfo
 412182221f0b3458f947f66b1a3610cf1d737ffed3036b9a9d958d215bf501d6 33108 
minissdpd_1.5.20180223-4_amd64.deb
Files:
 5f984e605ad8d4f5deca93de9d97312e 2065 net optional minissdpd_1.5.20180223-4.dsc
 0b4863088192f8110b897d10e1dc90cb 13128 net optional 
minissdpd_1.5.20180223-4.debian.tar.xz
 c72e34c37938b8b56335d49336aedb8b 56148 debug optional 
minissdpd-dbgsym_1.5.20180223-4_amd64.deb
 01867c48bf5104777ee36bf7a0ede561 5724 net optional 
minissdpd_1.5.20180223-4_amd64.buildinfo
 3c13db0ad2ddf33457f06c797b8512d1 33108 net optional 
minissdpd_1.5.20180223-4_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlwzePsACgkQq1PlA1ho
d6YV1g/7BFM8bSWqQlty8nzVhwm7APKZCoGTjZWl/R2ThBvbcRWcpyqvZD+fweEp
5yfMLhFp6n4k/mmI5zGEXVJOzt/bCw8Bdb4Eojwo9O06gd2O+ogWeW4jhdIrSe8D
NLYha6LpGgl2EE7o/Aw0/DM6AthKdhv7/mD7+kylIGUHYn2dwlVx5ouSxLUgWt12
1x0+E4Ysw3YDj3vj8m9Apnm1zKyZwE+mYDu/jVpYqPsXj2kxt2TDdGEm2+AfrglY
8T0524C9ljReeaYB/00d4QBYGKO4qt9KoWezrnSo8fu3oGF7hyHYaJSkvSUR2idB
M1ckXiccnvbSff8/6UVjBbI3alb7UO0XYj/9MHhetpO++ZTwdbxxCC2DvvWYb93b
vSGoQgDFA+kHAMDHUwgJwjjRn/nsoWHcmUcDi9KfunZAmXoRFAlp+ROrHemtOCif
SePezSI7JOIR/1RmUAUS3uQLnPee9y0qCzH28WClA00Wnk9GIvBWXG2RhvtxPXFY
jYc7qKoj0/NNEH1hxbscSRK0vNyj9afIMwpakH5xd4QKQYQzFfFn0os8A5xzH0u5
DT8cQYlyBjfVFXnC4aVYEqyzylAnTENykVf8f74Du+vE7bBwAVmFhkGUMPE3z7SE
HbFsZ/RGDxYYMentGSHSKV1UnnhMGrNyYnRwZVPIybGc/5ODOpc=
=ObdM
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to