[debhelper-devel] Bug#766795: afterstep binnmu related issues

[Robert Luberda]

unmerge 766795
reassign 766795 afterstep 2.2.12-3
retitle 766795 afterstep should stop using --link-doc
tag 766795 =pending
thanks

Niels Thykier writes:

>> Please note that the issue had came up a week or so before the
>> freeze, and in my opinion implementing the work-around was the
>> best action I could take at that moment.
>
> ... while keeping --link-doc.  For reference, we are debating a
> disk cost of 1.3Mb right now.

The real cost is the time needed to prepare & test the package. Also
in my opinion removing --link-doc was too risky to do shortly before
the freeze. Besides I believed than that this would be fixed by
debhelper; now I know this is unlikely to happen.


> I said you reopened #766711, not #767839, and reassigned #767839
> back to debhelper.  Right now debhelper has both #766711 and
> #767839 - it is not clear to be that they are distinct bugs.  I
> will probably merge this one into the other.

I've recently started working on afterstep to fix its other bug, and
recollected this discussion. Debhelper has 3 merged bugs, and
afterstep does not have any about this issue,  so let me unmerge
766795 and reassign it back to afterstep...

>> thanks to the work-around afterstep *is* currently binNMU safe.
>> However this is only `work-around', which means that even me is
>> not fully glad of this solution, and I promise to fix it one way
>> or another for jessie+1.

...in order to fix it as promised: afterstep will simply stop using
--link-doc in its next upload to experimental, even though I haven't
changed my mind and still think that linking docs between arch:any and
arch:all should be allowed, so it is rather debhelper's issue than
afterstep's one.

Regards,
robert