Your message dated Sun, 3 May 2020 14:08:51 +0200
with message-id <[email protected]>
and subject line I was mistaken
has caused the Debian Bug report #959533,
regarding dh: List addons in sequence
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 [email protected]
immediately.)
--
959533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959533
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debhelper
Version: 13
Severity: wishlist
Whiles debugging an issue with a build sequence, I noticed that
dh <target> --no-act
does not list where the addons come into effect. Specifically, I have a
package that uses
--with=python3,sphinxdoc
but it's not evident where in the sequence the addons will be called to
do their magic.
Or (as is in my specific case) if they will be called at all: it's
conceivable that dh_sphinxdoc get's only called in indep targets, for
example).
It would be appreciated if the addons' activities were also listed in
the sequence.
--- End Message ---
--- Begin Message ---
Please disregard this bug, I was mistaken.
The steps are properly listed if they are within the scope of <target>.
I overlooked the fact that eg: binary-indep has more steps that build-indep.
Sorry about the noise!
--- End Message ---
