Andreas Metzler wrote:
> found 400470 1.2.4-6
> # reopening as neither an explanation was given nor a change was made
> thanks
>
I did have an interim version where debconf was only a "Depends"....
> On 2006-12-02 Debian Bug Tracking System <[EMAIL PROTECTED]> wrote:
>
>> This is an automatic notification regarding your Bug report
>> #400470: imapproxy: Pre-Depends without reason,
>> which was filed against the imapproxy package.
>>
>> .
>> * Control file: debconf pre-depend *is* necessary (Closes: #400470)
>>
>
> Why is it necessary? The only reason you would need it is if you used
> debconf in preinst.
>
Having debconf as a Pre-Depends (as recommended by the Policy and
debconf's manual, AFAICR) is indeed more convenient than absolutely
necessary. The reason why it is needed: automated testing tools such as
piuparts fail horribly without a Pre-Depends (debconf is removed before
imapproxy) -- go figure.
Of course, piuparts might be buggy as hell, but it is used widely enough
to not be considered *that* buggy.
Moreover, I can't test uninstalling everything down to "essential" to
check whether this would become a real problem, so I'll have to trust
our tools.
I still cannot understand why is this Pre-Depends so important (for
you?). There are far worse dependency problems out there.
Of course, I know darn well that we are just about to enter a deep
freeze stage.
J.L.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
