Pkg_build_deps in ruby25 package?


Hey folks - I’m using the core/ruby25/2.5.0/20180310000657 package and the --binlink flag and I’m running into some unexpected behavior:

When I use the previous version: core/ruby25/2.5.0/20180118213246 I see no coreutils (a build time dependency).

root@5e487bbad577:/# ls -la /usr/local/bin/ | grep coreutils

With the new version I see the following:
root@cbf87998111e:/# ls -la /usr/local/bin/ | grep coreutils
lrwxrwxrwx 1 root root 50 Mar 29 20:56 [ -> /hab/pkgs/core/coreutils/8.25/20170513213226/bin/[
lrwxrwxrwx 1 root root 55 Mar 29 20:56 base32 -> /hab/pkgs/core/coreutils/8.25/20170513213226/bin/base32
lrwxrwxrwx 1 root root 55 Mar 29 20:56 base64 -> /hab/pkgs/core/coreutils/8.25/20170513213226/bin/base64
lrwxrwxrwx 1 root root 57 Mar 29 20:56 basename -> /hab/pkgs/core/coreutils/8.25/20170513213226/bin/basename
lrwxrwxrwx 1 root root 52 Mar 29 20:56 cat -> /hab/pkgs/core/coreutils/8.25/20170513213226/bin/cat
lrwxrwxrwx 1 root root 54 Mar 29 20:56 chcon -> /hab/pkgs/core/coreutils/8.25/20170513213226/bin/chcon

As you can imagine, this can cause quite a few issues, because it also brings in binutils and some other things!

I expect this isn’t the correct behavior but wanted to make sure.


It seems strange that the package would actually bring coreutils by itself, as both mentioned version of the package seem to have the exact same set of dependencies.(according to bldr)

Did you test those two packages binlink with the same version of habitat?


Yep I’ve just repro-d this behavior. Going to see if I can track down why this is happening.


There was a bug introduced in the pathing of the build program between January and March. This was actually fixed a few days ago but not all of the packages that were affected have been corrected. We’re in the process of doing a universe rebuild and once that’s done we should be able to get this rebuilt and promoted which will correct the issue.

Its possible the universe rebuild will hit this package and get it corrected as well but if not we’ll make sure to get it in. I’ll come back and update the thread when this is resolved.