Hi Hleb,
On Tue, Oct 11, 2016 at 03:36:13PM +0300, Hleb Valoshka wrote:
> Hi team.
> I've tried to rebuild berkshelf with sbuild, but the only result is the message:
> E: Core build dependencies not satisfied; skipping
> I've set up sbuild according with https://wiki.debian.org/sbuild
> Could anybody suggest anything?
> (--verbose and manual installation of all build dependencies to chroot
> are tried)
I tried to build it here with sbuild and the dependencies were
satisfied. I'd suggest to try to update the schroot with
update-sbuild -uadc <name_of_your_sbuild_chroot>
or even rebuild one from scratch (using for example the setup script in
the team main repo)
I had a quick look at the package which looks fine. I just got some test
failures (with cucumber). Details below.
You may also need to set 't.bundler = false' as an option for Cucumber::Rake::Task
to avoid running with bundler (and try to get berkshelf-api from remote git
repo).
I would also improve a little bit the first sentence of the long description in
debian/control: would something like this be suitable?
Berkshelf is to Chef what bundler is to rubygems: it manages
cookbooks and their dependencies.
Details of the cucumber failure in sbuild. They all pass when running
gem2deb-test-runner in my working env (with the additional t.bundler=false option)
/usr/bin/ruby2.3 -I "lib" "/usr/bin/cucumber" features -x --format progress --tags ~@ignore
............................................................................................................................F--...............F---.........................................................................................F-..................................................F--.........................................................................................F-..........................................................................................................................................................................................................................................................................F--.............................F---.............F---...................................................................F-......F.......................................................................................................................................................................................................
(::) failed steps (::)
expected "berks install" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/commands/install.feature:16:in `When I successfully run `berks install`'
expected "berks install" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/commands/install.feature:56:in `When I successfully run `berks install`'
expected "berks install" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/commands/install.feature:383:in `When I successfully run `berks install`'
expected "berks install" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/commands/install.feature:522:in `When I successfully run `berks install`'
service unavailable at: http://0.0.0.0:26210/ (Berkshelf::APIClient::ServiceUnavaiable)
./lib/berkshelf/source.rb:43:in `build_universe'
./lib/berkshelf/source.rb:57:in `universe'
./lib/berkshelf/source.rb:100:in `versions'
./lib/berkshelf/berksfile.rb:510:in `block (2 levels) in outdated'
./lib/berkshelf/berksfile.rb:509:in `each'
./lib/berkshelf/berksfile.rb:509:in `block in outdated'
./lib/berkshelf/berksfile.rb:508:in `each'
./lib/berkshelf/berksfile.rb:508:in `inject'
./lib/berkshelf/berksfile.rb:508:in `outdated'
./lib/berkshelf/cli.rb:254:in `outdated'
./lib/berkshelf/cli.rb:52:in `dispatch'
./lib/berkshelf/cli.rb:27:in `execute!'
features/commands/outdated.feature:47:in `When I successfully run `berks outdated`'
expected "berks vendor cukebooks" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/commands/vendor.feature:15:in `When I successfully run `berks vendor cukebooks`'
expected "berks vendor vendor" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/commands/vendor.feature:78:in `When I successfully run `berks vendor vendor`'
expected "berks vendor cukebooks" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/commands/vendor.feature:99:in `When I successfully run `berks vendor cukebooks`'
expected "berks install --format json" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
features/json_formatter.feature:15:in `When I successfully run `berks install --format json`'
expected: "{\n \"cookbooks\": [\n {\n \"name\": \"berkshelf-cookbook-fixture\",\n \"version\": \"...",\n \"Fetching cookbook index from http://0.0.0.0:26210...\"\n ],\n \"warnings\": [\n\n ]\n}"
got: "{\n \"cookbooks\": [\n {\n \"name\": \"berkshelf-cookbook-fixture\",\n \"version\": \"...* [Berkshelf::APIClient::ServiceUnavaiable] service unavailable at: http://0.0.0.0:26210/\"\n ]\n}"
(compared using ==)
Diff:
@@ -13,7 +13,8 @@
"Fetching cookbook index from http://0.0.0.0:26210...";
],
"warnings": [
-
+ "Error retrieving universe from source: http://0.0.0.0:26210/";,
+ " * [Berkshelf::APIClient::ServiceUnavaiable] service unavailable at: http://0.0.0.0:26210/";
]
}
(RSpec::Expectations::ExpectationNotMetError)
./features/step_definitions/json_steps.rb:22:in `/^the output should contain JSON:$/'
features/json_formatter.feature:44:in `Then the output should contain JSON:'
Failing Scenarios:
cucumber features/commands/install.feature:7 # Scenario: installing the version that best satisfies our demand
cucumber features/commands/install.feature:41 # Scenario: installing demands from all groups
cucumber features/commands/install.feature:365 # Scenario: running install when a Berksfile.lock is present
cucumber features/commands/install.feature:504 # Scenario: transitive dependencies in metadata
cucumber features/commands/outdated.feature:28 # Scenario: the dependency has no version constraint and there are new items
cucumber features/commands/vendor.feature:9 # Scenario: successfully vendoring a Berksfile with multiple cookbook demands
cucumber features/commands/vendor.feature:51 # Scenario: vendoring a cookbook with transitive dependencies when a lockfile is present
cucumber features/commands/vendor.feature:91 # Scenario: vendoring to a directory that already exists
cucumber features/json_formatter.feature:7 # Scenario: JSON output installing a cookbook from the default location
cucumber features/json_formatter.feature:36 # Scenario: JSON output installing a cookbook we already have
164 scenarios (10 failed, 154 passed)
975 steps (10 failed, 18 skipped, 947 passed)
0m11.872s
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<<PKGBUILDDIR>>/debian/berkshelf returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
Best wishes,
Cédric
Attachment:
signature.asc
Description: PGP signature