FTBFS: ruby-rspec-core, ruby-rspec-expectations, ruby-rspec-mocks
Bug #817664 reported by
Brian Thomason
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-rspec-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ruby-rspec-expectations (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ruby-rspec-mocks (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The following three source packages were once part of the same source package, but the developer recently split them up:
ruby-rspec-core
ruby-rspec-
ruby-rspec-mocks
However, they each build-depend upon one another due to the fact functionality from each is needed to properly run their respective test suites.
After speaking with one of the Debian maintainers, Tobias Grimm, and Kees Cook from the security team, it was determined that the best course of action would be to:
1.) Remove the circular build dep and disable the test suite on initial upload to "bootstrap" the packages
2.) Add the build-deps and test suite functionality back into place and upload again
To post a comment you must log in.
This bug was fixed in the package ruby-rspec-core - 2.5.1-1ubuntu1~ bootstrap1
--------------- 1ubuntu1~ bootstrap1) oneiric; urgency=low
ruby-rspec-core (2.5.1-
* Temporarily removing ruby-rspec- expectations and ruby-rspec-mocks as
build-deps as they create a circular build dependency. These packages are
necessary for the ruby tests to be executed, so these have been temporarily
disabled as well. This upload functions as a bootstrap version of the
package. (LP: #817664)
-- Brian Thomason <email address hidden> Thu, 28 Jul 2011 13:30:32 -0400