trying to build a port for vagrant and failing

Christopher J. Ruwe cjr at cruwe.de
Tue Nov 6 21:01:15 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Currently, I am trying to write up a port for vagrant, a VirtualBox
managment thing (http://vagrantup.com/). I am failing with the
dependencies and would be grateful for some help.

I have

BUILD_DEPENDS=  minitar:${PORTSDIR}/archivers/rubygem-archive-tar-minitar \

RUN_DEPENDS=    erubis:${PORTSDIR}/www/rubygem-erubis \
                rubygem-childprocess>=0.3.1:${PORTSDIR}/devel/rubygem-childprocess \
                rubygem-i18n>=0.6.0:${PORTSDIR}/devel/rubygem-i18n \
                rubygem-json>=1.5.1:${PORTSDIR}/devel/rubygem-json \
                rubygem-log4r>=1.1.9:${PORTSDIR}/sysutils/rubygem-log4r \
                rubygem-net-ssh>=2.2.2:${PORTSDIR}/security/rubygem-net-ssh \
                rubygem-net-scp>=1.0.4:${PORTSDIR}/security/rubygem-net-scp

in the makefile.

- From the build log (I am using poudriere for testing) I get


=======================<phase: run-depends>==========================
===>   rubygem-vagrant-1.0.5 depends on executable: erubis - not found
===>    Verifying install for erubis in /usr/ports/www/rubygem-erubis
===>   Installing existing package /usr/ports/packages/All/rubygem-erubis-2.7.0.tbz
===>   Returning to build of rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-childprocess>=0.3.1 - not found
===>    Verifying install for rubygem-childprocess>=0.3.1 in /usr/ports/devel/rubygem-childprocess
===>   Installing existing package /usr/ports/packages/All/rubygem-childprocess-0.3.5.tbz
===>   Returning to build of rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-i18n>=0.6.0 - not found
===>    Verifying install for rubygem-i18n>=0.6.0 in /usr/ports/devel/rubygem-i18n
===>   Installing existing package /usr/ports/packages/All/rubygem-i18n-0.6.0,2.tbz
===>   Returning to build of rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-json>=1.5.1 - not found
===>    Verifying install for rubygem-json>=1.5.1 in /usr/ports/devel/rubygem-json
===>   Installing existing package /usr/ports/packages/All/rubygem-json-1.7.5.tbz
===>   Returning to build of rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-log4r>=1.1.9 - not found
===>    Verifying install for rubygem-log4r>=1.1.9 in /usr/ports/sysutils/rubygem-log4r
===>   Installing existing package /usr/ports/packages/All/rubygem-log4r-1.1.10.tbz
===>   Returning to build of rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-net-ssh>=2.2.2 - not found
===>    Verifying install for rubygem-net-ssh>=2.2.2 in /usr/ports/security/rubygem-net-ssh
===>   Installing existing package /usr/ports/packages/All/rubygem-net-ssh-2.1.4,2.tbz
===>   Returning to build of rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-net-scp>=1.0.4 - not found
===>    Verifying install for rubygem-net-scp>=1.0.4 in /usr/ports/security/rubygem-net-scp
===>   Installing existing package /usr/ports/packages/All/rubygem-net-scp-1.0.4_1.tbz
===>   Returning to build of rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/gem18 - found
===>   rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/ruby18 - found
===================================================================

So far so good. I noticed that rubygem-net-ssh-2.1.4.2 is supposed to
satisfy >=rubygem-net-ssh-2.2.2, which I ignore for the while.

Now, building yields

=======================<phase: install  >==========================
===>  Installing for rubygem-vagrant-1.0.5
===>   rubygem-vagrant-1.0.5 depends on executable: erubis - found
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-childprocess>=0.3.1 - found
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-i18n>=0.6.0 - found
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-json>=1.5.1 - found
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-log4r>=1.1.9 - found
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-net-ssh>=2.2.2 - found
===>   rubygem-vagrant-1.0.5 depends on package: rubygem-net-scp>=1.0.4 - found
===>   rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/gem18 - found
===>   rubygem-vagrant-1.0.5 depends on file: /usr/local/bin/ruby18 - found
===>   Generating temporary packing list
===>  Checking if emulators/rubygem-vagrant already installed
/usr/bin/env  /usr/local/bin/gem18 install -l --no-update-sources --no-ri --install-dir /usr/local/lib/r\
uby/gems/1.8 /usr/ports/distfiles/rubygem/vagrant-1.0.5.gem -- --build-args
ERROR:  While executing gem ... (Gem::DependencyError)
    Unable to resolve dependencies: vagrant requires json (~> 1.5.1), net-ssh (~> 2.2.2)
*** Error code 1

The installation is right about net-ssh (confer above), but definitely
not on json (1.7.5 > 1.5.1).

Can anybody hint me on a path to pursue to resolve that error?

Many thanks, cheers,
- -- 
Christopher
TZ: 	    GMT + 2h
GnuPG/GPG:  0xE8DE2C14

Punctuation matters:
"Let's eat Grandma" or "Let's eat, Grandma" - Punctuation saves lives.
"A panda eats shoots and leaves" or "A panda eats, shoots, and leaves" -
Punctuation teaches proper biology.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBAgAGBQJQmXqUAAoJEJTIKW/o3iwUMpkQAOsxOAM+41q3XHmHKPUqRzOy
lxGtwLOxENGiy3ujrhUInVuJxwbXPEeuiD5zWs6yNgPnedpz+4jdeA+Z/FTXjsSi
2m39sOy0760H5oIH3dUjvTgpLrfPs7r7fgCF/9NOHLJWZFVXrYG652tPAkJCgJw9
EXzWSDVGo0t5ZLfEeiiOFjuQAoewW9jjGuv7piR8qAClmKPtxJl3VkYzP54bdJSh
D42+T+Vfza5jbNFPZgS03hGv3Y6ARPZ7f3UqFuX4JvRwdyyvBG26Cc2IDJamr5lL
f5vz9FOL8YdHWVVkhI3Z1OkdIKDt0pdai76Kwa7bcjN19TrHIgGJvUYEjKUvrw+N
zPE6MGn/nWVLDPhJpt9/yalXizMUfIYJL28yLPc9l+pRkZiEpD79rZxmTRrn88xy
UwmOpJarYtk0R7Y2G0KLXNj/+xg2rde6qm7+rgePrc2PK61IVbYSEE8BojJT8vWi
vsfCLVY6L8YOIuiUDN8reqVcEewil+S/XPrOdcJBeqe5+x3NRO8SE1zlHtfZ25YN
Wdt6IF6dYKNhA6lIG/00nSDZA+zcae2DAonzWrmahnjBRdkAZy7v3S+1w7nxNyKU
Gp4Vlm51tEFB7oTqr13wfwmZ6zsXQVtkVqBIGd4mID1BuZpsJGAB86p4XQr5JSHs
C15haWzOgasC1Q7n3rl3
=Ku9E
-----END PGP SIGNATURE-----


More information about the freebsd-questions mailing list