On Sat, Sep 20, 2014 at 08:46:01AM +0000, Potter, Tim (Cloud Services) wrote: > On 19/09/14 8:37 AM, "Potter, Tim (Cloud Services)" > <timothy.potter@hp.com> wrote: > There are 300 or so unit tests > that are part of the package that I have managed to get running. Great news! > I found a circular build dependency though between two gems used by the > ruby-elasticsearch test harness. It doesn't look like it can be > introduced into the repository without disabling the tests (temporarily?) > for one of the packages. I think the ports guys might get upset by this > though. Introducing an unbuildable set of packages is probably bad form. > Other packages I created to get this working are currently in my > toot-guest public_git repository: > ruby-ae > ruby-brass > ruby-jsonify > ruby-qed > ruby-lemon > ruby-prof > ruby-ansi Is the circular build-dependency caused by ruby-lemon/ruby-ansi/ruby-ae? Another package uses ruby-lemon for tests (ruby-hashery). I simply gave up momentarily about those tests. You can either do the same or if you manage to build those three packages in a clean way, then we could enable tests in ruby-hashery, which would be an improvement. In this list, can you precise which packages are needed for the tests, and which are just build-dependencies of those packages? Would you mind importing those packages in the team directory? Thanks! Cédric
Attachment:
signature.asc
Description: Digital signature