Your message dated Fri, 11 Aug 2017 12:44:51 -0700
with message-id <87o9rlx51o....@iris.silentflame.com>
and subject line Closing inactive Policy bugs
has caused the Debian Bug report #215549,
regarding reconfigure argument to postinst
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.)
--
215549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=215549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-make
Version: 0.35
Severity: minor
debconf-devel says:
This is a hack because the right thing would be to pass
$1 = "reconfigure", but doing so without breaking all
the postinsts that use debconf is difficult. The migration
plan away from this hack is to encourage people to write
postinsts that accept "reconfigure", and once they all do,
begin passing that variable.
If this is still true then postinst.ex should include "reconfigure"
as one of the arguments it handles. Presumably this way would be
a good suggestion:
27c27
< configure)
---
> configure|reconfigure)
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux thanatos 2.4.22 #1 Mon Sep 1 09:45:41 CEST 2003 i686
Locale: LANG=en_IE@euro, LC_CTYPE=en_IE@euro
Versions of packages dh-make depends on:
ii debhelper 4.1.74 helper programs for debian/rules
ii dpkg-dev 1.10.15 Package building tools for Debian
ii make 3.80-4 The GNU version of the "make" util
ii perl 5.8.0-18 Larry Wall's Practical Extraction
-- no debconf information
--- End Message ---
--- Begin Message ---
control: user debian-pol...@packages.debian.org
control: usertag -1 +obsolete
control: tag -1 +wontfix
Russ Allbery and I did a round of in-person bug triage at DebConf17 and
we are closing this bug as inactive.
The reasons for closing fall into the following categories, from most
frequent to least frequent:
- issue is appropriate for Policy, there is a consensus on how to fix
the problem, but preparing the patch is very time-consuming and no-one
has volunteered to do it, and we do not judge the issue to be
important enough to keep an open bug around;
- issue is appropriate for Policy but there does not yet exist a
consensus on what should change, and no recent discussion. A fresh
discussion might allow us to reach consensus, and the messages in the
old bug are unlikely to help very much; or
- issue is not appropriate for Policy.
If you feel this bug is still relevant and want to restart the
discussion, you can re-open the bug. However, please consider instead
opening a new bug with a message that summarises and condenses the
previous discussion, updates the report for the current state of Debian,
and makes clear exactly what you think should change.
A lot of these old bugs have long side tangents and numerous messages,
and that old discussion is not necessarily helpful for figuring out what
Debian Policy should say today.
--
Sean Whitton
signature.asc
Description: PGP signature
--- End Message ---
