Mathias Brodala wrote: > Hi. > > Jim Meyering, 11.04.2011 09:13: >> Mathias Brodala wrote: >>>> FAIL: misc/tail (exit: 1) >>>> ========================= >> ... >>>> f-pipe-1.p... >>>> tail: test f-pipe-1.p: stderr mismatch, comparing f-pipe-1.p.E >>>> (actual) and f-pipe-1.p.3 (expected) >>>> *** f-pipe-1.p.E Sat Apr 9 22:58:08 2011 >>>> --- f-pipe-1.p.3 Sat Apr 9 22:58:08 2011 >>>> *************** >>>> *** 1 **** >>>> - tail: cannot determine location of `standard input'. reverting to >>>> polling: Function not implemented >>>> --- 0 ---- >> >> Thanks. >> However, that's nothing serious (certainly not "grave"). >> Even if it were, how often does anyone run tail -f on a pipe? > > The usual "dmesg | tail -f" comes into mind. ;-)
tail -f still works on pipes. The test fails because it's printing a diagnostic (when none was expected) when reverting from inotify-based to the classic polling-based method. > Aside from that I actually meant this report to be about the FTFBS issue > alone since that pretty much makes the package unusable to me. If I > can’t compile it, then I cannot make modifications. Failing a single nit-picky test should not be seen as making the entire 100+-program package unusable. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
