[Pkg-privacy-maintainers] Bug#613678: Testsuite fails when build in a long file path

[Antoine Beaupre]

On Wed, Feb 16, 2011 at 12:02:15PM -0500, Daniel Kahn Gillmor wrote:
> On 02/16/2011 11:32 AM, Moritz Mühlenhoff wrote:
> > I would propose to either skip the "basic" test suite if the length of pwd is 
> > below a threshold or to run the testsuite in 
> > (mktemp -d /tmp/mstest.XXXXXXXXX) rightaway.
> 
> one downside of running the testsuite under /tmp (assuming that it's
> even possible) is that the usual permissions for /tmp (01777) are too
> loose for sshd to accept files in there as legitimate authorizedkeys files.
> 
> as a result, the test suite will run with StrictModes off, which
> effectively disables some features of the test suite (meaning less
> coverage).  bleah.
> 
> i guess it's better than no test suite coverage at all, though.

agreed.

also, do note that even if socat would magically be fixed (and it
can't), gpg-agent would be the next to fail (#847206).

i stumbled upon this in another package (#920387).

a.

-- 
For every complex problem, there is an answer that is clear, simple -
and wrong.
                        - H.L. Mencken
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20190127/63ec61e5/attachment.sig>