[DRE-maint] Bug#852707: schleuder: FTBFS : refresh_keys test suite fails

[Daniel Kahn Gillmor]

On Thu 2017-01-26 10:59:21 -0500, Daniel Kahn Gillmor wrote:
> one way to resolve this in a principled fashion without skipping the
> tests is to have the test suite set up a mini-keyserver on the loopback
> (this is really just an http server that responds correctly to the
> specific queries that it might receive) and configure schleuder to use
> it during the testing.

OK, it seems that schleuder was already doing this, which is good :)

however, it was doing it by binding to 127.0.0.1:11371, which is not so
good.  In particular, it failed on a machine that has an instance of sks
already running on it, bound to the same IP address and port (which is
the typical way that one installs sks).

So at the very least, you probably want a Build-Conflicts: sks with the
current setup.  however, i saw the same problem on other hosts too that
don't have sks installed, and i haven't yet been able to diagnose why
those systems failed :(

That said, the best fix would be to launch the mock keyserver on an
OS-selected port (port 0, which means let the OS choose one that's
free), and then automatically write the selected port into the keyserver
line on spec/schleuder.yml before the tests begin.

A third alternative is to use a hard-coded port other than 11371,
possibly coupled with a hard-coded address other than 127.0.0.1.  since
127.0.0.0/8 are all loopback addresses, you could use, for example:

   127.11.3.71:17311


this is not as principled an approach as using port 0, but it's much
more likely to Just Work than the current approach.

Regards,

     --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20170126/82f55ce5/attachment.sig>