Open nogweii opened 10 years ago
The second item. apt cache, is solved with https://github.com/evaryont/huginn-chef/commit/666cd3d137c06b19359653ce7f5476ded8c91ac1
The db:migrate
error is really a fault with huginn, not with chef. I'll open an issue there.
Using apt directly locks us into OS's that use it (eg. CentOS uses yum) I'm pretty sure there's a cookbook way that handles both, and I was pretty certain it does the update as well. Does the old code not do that for you..?
APP_SECRET_TOKEN=Your\ Gemfile\ lists\ the\ gem\ unicorn\ (>\=\ 0)\ more\ than\ once.' 'You\ should\ probably\ keep\ only\ one\ of\ them.' 'While\ it\'s\ not\ a\ problem\ now,\ it\ could\ cause\ errors\ if\ you\ change\ the\ version\ of\ just\ one\ of\ them\ later.' '371aa019a320e294052ee480d2ce15efde1e83102db567d841565afd1c5f1b089efafbcfb844358d38545926ce573668227326dcebc13b4539c44f3f2e394305;
Looks to be the issue in that prior code.
— Sent from Mailbox
On Sat, Oct 11, 2014 at 8:54 AM, No GUI notifications@github.com wrote:
The
db:migrate
error is really a fault with huginn, not with chef. I'll open an issue there.Reply to this email directly or view it on GitHub: https://github.com/alias1/huginn-chef/issues/6#issuecomment-58721273
How'd you go with fixing up those issues @evaryont ?
Just a braindump, it's 1AM my time.
apt-get update
for us.db:migrate
is broken currently. Fails to create an index, mysql complains about the size:db:reset
to load the schema.rb instead, however the init script is broken due to #5:Specifically, upstart complains about an unknown stanza. The embedded new lines from the bundler output break things.