Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

[Niels Thykier]

gregor herrmann:
> On Sat, 29 Dec 2018 04:57:00 +0000, Niels Thykier wrote:
> 
>>> From the debhelper changelog:
>>>
>>> debhelper (11.5.4) unstable; urgency=medium
>>>
>>>   [ Niels Thykier ]
>>>   * Dh_Lib.pm: Reopen stdin to read from /dev/null in doit (and its sibling
>>>     functions) to prevent issues when stdin is open in write-only mode
>>>     (which is what nohup(1) does).  Thanks to Julian Gilbey for reporting
>>>     the issue and providing a sample patch for it as well.
>>>     (Closes: #913663)
>>>
>>>
>>> Can this be related? (The failing test operate on \*STDIN.)
>>> Cc'ing the debhelper bug and debhelper maintainers …
>>
>> Hi gregor,
>>
>> Indeed, that could be related.
>>
>> [...]
>> Does/did it work under nohup (without the
>> debhelper work around to make nohup work)?
> 
> Yes, in the same chroot (i.e. with the STDIN redirection commented
> out) `TERM=vt100 nohup prove --blib --verbose t/*.t' in d/rules works.
>  
> 
> Cheers,
> gregor
> 

Now I am even more puzzled.

nohup does the eqv. of

  open(STDIN, '>', '/dev/null')

and libterm-termkey-perl allegedly copes with that!?  Unless the answer
is that prove "fixes" this for us and "perl Build test --verbose" (as
run by dh_auto_test) does not have the same magic as prove?

Thanks,
~Niels

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20181229/13147b4d/attachment.sig>