Git Product home page Git Product logo

chef-drush's People

Contributors

alanivey avatar msonnabaum avatar patcon avatar

Stargazers

 avatar

Watchers

 avatar

chef-drush's Issues

Think about what we are going to do when upstream changes

Currently, we are pretty much heading down the path of a completely separate fork from the upstream repo. There are things in our repo that are important for vagrant-drupal (like the .drush folder symlink), but have little chance of being accepted as pull requests upstream. If there is a big change upstream that would really improve our version, I guess we'll have to go through (the pain of) manually merging those changes. Anything we do that would be useful (#1) won't really be able to go through a clean pull request.

package[git] (drush::default line 48) had an error: Chef::Exceptions::Package: git has no candidate in the apt-cache

10.04.4 and earlier needs to be specified as git-core.

[Mon, 21 May 2012 18:13:50 -0400] INFO: Processing package[git] action install (drush::default line 48)
[Mon, 21 May 2012 18:13:51 -0400] ERROR: package[git] (drush::default line 48) has had an error
[Mon, 21 May 2012 18:13:51 -0400] ERROR: package[git] (/tmp/vagrant-chef-1/chef-solo-1/cookbooks/drush/recipes/default.rb:48:in `from_file') had an error:
package[git] (drush::default line 48) had an error: Chef::Exceptions::Package: git has no candidate in the apt-cache
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/provider/package/apt.rb:69:in `block in check_package_state'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/provider/package/apt.rb:44:in `each_line'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/provider/package/apt.rb:44:in `check_package_state'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/provider/package/apt.rb:36:in `load_current_resource'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource.rb:439:in `run_action'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/runner.rb:45:in `run_action'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/runner.rb:81:in `block (2 levels) in converge'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/runner.rb:81:in `each'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/runner.rb:81:in `block in converge'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource_collection.rb:94:in `block in execute_each_resource'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource_collection/stepable_iterator.rb:116:in `call'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/resource_collection.rb:92:in `execute_each_resource'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/runner.rb:76:in `converge'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/client.rb:312:in `converge'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/client.rb:160:in `run'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/application/solo.rb:192:in `block in run_application'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/application/solo.rb:183:in `loop'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/application/solo.rb:183:in `run_application'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/lib/chef/application.rb:67:in `run'
/usr/local/rvm/gems/ruby-1.9.2-p320/gems/chef-0.10.8/bin/chef-solo:25:in `<top (required)>'
/usr/local/rvm/gems/ruby-1.9.2-p320/bin/chef-solo:19:in `load'
/usr/local/rvm/gems/ruby-1.9.2-p320/bin/chef-solo:19:in `<main>'
[Mon, 21 May 2012 18:13:51 -0400] ERROR: Running exception handlers
[Mon, 21 May 2012 18:13:51 -0400] ERROR: Exception handlers complete
[Mon, 21 May 2012 18:13:51 -0400] FATAL: Stacktrace dumped to /tmp/vagrant-chef-1/chef-stacktrace.out
[Mon, 21 May 2012 18:13:51 -0400] FATAL: Chef::Exceptions::Package: package[git] (drush::default line 48) had an error: Chef::Exceptions::Package: git has no candidate in the apt-cache

Restructure repo so it will play nicer with upstream repo

Need to separate our specific changes that aren't accepted into the upstream repo. How should we structure the branches? How would we do development on changes that could be accepted upstream? How would we do development on changes that won't be accepted upstream? #4 talks about these concerns.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.