Temporary workaround for glibc dependency errors


#1

Greetings, fellow Habicats!

We recently did a full refresh of the Habitat core plans

Wondering why we did this? Check out this blog post for more details.

This was a massive update - 1.5 years worth of updates to some packages. We have moved to a monthly cadence for these refreshes to avoid a change that massive again.

Some issues with Habitat use on older kernels emerged after the refresh. For a full explanation of this, check out this blog post.

To help mitigate issues with Habitat on older linux kernels, we had to pin some dependencies in the Habitat components including hab-plan-build. The hab-plan-build component is what is used to build all Linux packages in a studio or on Builder.

If you wish to use these dependencies with a plan, you will need to pin them in your plan to the pre-base plans refresh version (again, this is temporary until our multi-architecture work is complete). Here is the known list (if you find more, please feel free to add them) and the pre-base-plans-refresh idents:

core/bash/4.3.42/20170513213519
core/bats/0.4.0/20170514013659
core/binutils/2.25.1/20170513201927
core/bzip2/1.0.6/20170513212938
core/coreutils/8.25/20170513213226
core/file/5.24/20170513201915
core/findutils/4.4.2/20170513214305
core/gawk/4.1.3/20170513213646
core/grep/2.22/20170513213444
core/gzip/1.6/20170513214605
core/rq/0.9.2/20170612005822
core/sed/4.2.2/20170513213123
core/tar/1.29/20170513213607
core/unzip/6.0/20180310001951
core/wget/1.19.1/20171024102323
core/xz/5.2.2/20170513214327)


Dependency conflicts between different versions of glibc