Ubuntu
ack package

  1. Bug #1707979
  2. Comment #16

Comment 16 for bug 1707979

Revision history for this message
Axel Beckert (xtaran) wrote : Fwd: Re: [beyondgrep/ack2] Ubuntu Artful doesn't contain ack (nor ack-grep) (#652) [origin: notifications@github.com]

The following comment by the main ack upstream developer in the
according upstream ticket may give a hint where to look for the
failure reason:

----- Forwarded message from Andy Lester (https://github.com/beyondgrep/ack2/issues/652#issuecomment-350527181) -----
Here's something interesting: Many of the tests I see at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/a/ack/20171024_160017_5333d@/log.gz are showing `-` as filenames found in tests where actual filenames are expected, like so:

```
                # Failed test 'File on command line is always searched'
                # at t/Util.pm line 412.
                # +----+-------+---------------------------------+
                # | Elt|Got |Expected |
                # +----+-------+---------------------------------+
                # | 0|[ |[ |
                # * 1| '-' | 't/swamp/#emacs-workfile.pl#' *
                # | 2|] |] |
                # +----+-------+---------------------------------+
                # actual[
                # '-'
                # ]
                # expected[
                # 't/swamp/#emacs-workfile.pl#'
                # ]
                # Looks like you failed 1 test of 1.
```

It's a pretty consistent pattern happening throughout. Maybe there's something in how the tests get run that confuse STDIN with the filesystem?
----- End forwarded message -----

So does the autopkgtest infrastructure in Ubuntu run on a rather
exotic file system which might result in tools regarding files as
STDIN?