Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix breakage introduced in apt 2.5.0 #85

Merged
merged 1 commit into from
Aug 14, 2014
Merged

Conversation

kisoku
Copy link
Contributor

@kisoku kisoku commented Aug 14, 2014

here's a proposed fix for issue #84

@chef-supermarket
Copy link

Hi. Your friendly Curry bot here. Just letting you know that there are commit authors in this Pull Request who appear to not have signed a Chef CLA.

There are 1 commit author(s) whose commits are authored by a non GitHub-verified email address in this Pull Request. Chef will have to verify by hand that they have signed a Chef CLA.

Please sign the CLA here.

e.run_action(:run)
end

# Run apt-get update to create the stamp file
execute 'apt-get-update (first run)' do
execute 'apt-get-update' do
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After this change, the resource becomes:

# Run apt-get update to create the stamp file
execute 'apt-get-update' do
  command 'apt-get update'
  ignore_failure true
  only_if { apt_installed? }
  not_if { ::File.exists?('/var/lib/apt/periodic/update-success-stamp') }
end

If somebody notifies "execute[apt-get-update]" and the update-success-stamp file exists, should not be updated? Perhaps we need a third apt-get update resource, like previously, but with different names.

someara pushed a commit that referenced this pull request Aug 14, 2014
fix breakage introduced in apt 2.5.0
@someara someara merged commit b3fefc6 into sous-chefs:master Aug 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants