| This is fixed as we discussed on the issue you opened (https://github.com/berkshelf/berkshelf/issues/1158).
Please consider using an alternate tone in the future. I understand that you are experiencing frustration, but, in my experience, the users of the Chef mailing list are far more likely to give helpful responses if you are slightly less angry in your words.
Thanks, Seth On Apr 24, 2014, at 12:37 PM, Jesse Campbell <
">
> wrote: 3.0.1
ran "berks install" 2 days ago, got apache 1.10.2. ran it today, got
1.10.4, and it updated the lockfile
On Thu, Apr 24, 2014 at 12:10 PM, Ranjib Dey <
">
> wrote:
we had the same issue with berks 2. We didn't encounter this with berks 3.
which version of berks you are using?
On Thu, Apr 24, 2014 at 8:12 AM, Jesse Campbell <
">
> wrote:
In librarian, I can create a Cheffile.lock and test it on the dev
environment, then check it into version control, push to production,
and librarian-chef will strictly follow the lock file for what gets
installed.
In berkshelf, I can create a Berksfile.lock and test it on the dev
environment, then check it into version control, push to production,
and berkshelf will sometimes follow the lockfile, and sometimes to
whatever the fuck it wants and install newer versions of things like
apache2 that I haven't tested yet.
What am I doing wrong? Is there no option for berkshelf to strictly
follow the locksfile? Is it always just a suggestion?
|