Hi, Thanks for the report.
On 17-01-26 16:51:19, [email protected] wrote: > From: Daniel Kahn Gillmor <[email protected]> > > I think that looks like 3.0.1-1 was uploaded to debian with both > source and binary packages [0], so the buildd's don't have a chance to > build it. If you do future uploads as source-only builds > ("dpkg-buildpackage -S" or "gbp buildpackage -S") then that gives the > buildds a chance to build cleanly and run the test suites. That's correct, I've asked Sebastien Badia already to do another source only upload. > I note that having a test suite contact the network (as the two > failing tests appear to want to do) is also probably not a great idea. > It means that the test suite will fail on a build daemon that doesn't > have network access, and also that it may intermittently fail based on > whether the remote network service is available. The tests are using spec/sks-mock.rb to mock the behaviour of the keyservers out there. Cheers, Georg -- To receive the public gpg key for this address send a mail to [email protected].
pgp3nN5sWYpwy.pgp
Description: PGP signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
