indirect changed the topic of #bundler to: Docs! http://bundler.io | Problems? http://bit.ly/bundler-issues | How to help: http://bit.ly/bundler-development | API Dashboard http://cl.ly/SBoH | #bundler logs: http://bit.ly/bundler-logs | Questions will be answered eventually, so hang out for a while
livingstn has joined #bundler
<tmoore> dukedave: I would recommend in general that for tools that are not dependencies of your app, don't put them in the Gemfile
<tmoore> if it's a "gem" that is not really a library but just a separate command line tool that happens to be distributed as a gem
<tmoore> otherwise, you'll often eventually end up with a conflict between that app's dependencies and your app's
<tmoore> and there's no reason to have it on your load path at runtime
<tmoore> so I think you made the right call in the end :-)
psacrifice|away has quit [Quit: PanicBNC - https://PanicBNC.net]
havenwood has quit [Remote host closed the connection]
havenwood has joined #bundler
kgrz has joined #bundler
kgrz has quit [Ping timeout: 240 seconds]
<jhass> I'd still like by default optional groups, bundle install --with mysql is much easier to explain than bundle install --without postgresql sqlite
<tmoore> jhass: popular request, that so far nobody has volunteered to implement :-)
<jhass> ah, it doesn't go against the "no local gems" doctrine?
<tmoore> it's tricky, though... see discussion at https://github.com/bundler/bundler-features/issues/59
<tmoore> and I guess someone did try to implement it, but gave up when we gave some feedback
<tmoore> jhass: that's a completely separate issue than what I was talking about before
<jhass> yeah sure
<tmoore> groups exist, and you can exclude them now, but they still have to resolve with the rest of the gems in your project
<tmoore> but, like MailCatcher for example says "don't put mailcatcher into your Gemfile" and I agree (http://mailcatcher.me/)
<tmoore> it's not something your app wants to load up into its process at runtime, so it doesn't need to be there, whereas a database driver gem is
<jhass> my idea about optional groups is to declare them as such in the Gemfile and add a --with option
<tmoore> oh so the group is opt-in instead of opt out?
<jhass> yeah
<tmoore> that actually sounds like it might address some of the problems we talked about... please feel free to write up a proposal at https://github.com/bundler/bundler-features/issues :-)
<jhass> and putting it in --without just removes it from the set of requested optional groups
<jhass> and is a noop if it wasn't requested before
<jhass> I toyed a bit with it in https://github.com/jhass/bundler/compare/optional_groups but didn't pursue it to the end and thought all edge cases through yet
<tmoore> this is probably something indirect has considered in the past... I'm relatively new to the project... there may be a wrinkle that doesn't occur to me immediately
havenwood has quit [Remote host closed the connection]
livingstn has quit []
havenwood has joined #bundler
yates has joined #bundler
<yates> i'm trying to do a "bundle install --without development test" (redmine installation) and am getting this error:
<yates> /usr/local/share/gems/gems/bundler-1.7.3/lib/bundler/vendor/thor/shell/basic.rb:355: warning: Insecure world writable dir /home in PATH, mode 040777
<yates> Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
<yates> i don't want to change my home path protection. so how do i continue?
<yates> i'm also getting this line: /usr/share/ruby/vendor_ruby/psych.rb:205:in `parse': (<unknown>): mapping values are not allowed in this context at line 34 column 11 (Psych::SyntaxError)
<yates> not sure which one is the error
kgrz has joined #bundler
<jhass> yates: why do you want everyone to be able to remove your home dir?
<yates> i'm not here to discuss my policies. they are what they are. is this the error, and if so, is there a workaround.
<yates> s/workaround./workaround?/
<jhass> since you refuse the obvious "workaround" so vehemently, fork bundler to remove that check and use your fork
<yates> the obvious workaround would break 15 other things.
kgrz has quit [Ping timeout: 258 seconds]
kgrz has joined #bundler
<yates> why does bundler enforce policies that aren't its place to enforce?
<jhass> I'd consider them broken already, but that seems to be just a warning actually (and sadly). You need to fix that YAML parsing error. Did you manually edit .bundle/config by any chance?
<yates> or at allow an override.
<yates> no.
<jhass> why don't you make a pastie with the whole output, maybe it reveals the file that's wrong too
<yates> jhass: your idea of broken is strange. it has functioned well for me for 9 years.
x1337807x has joined #bundler
<yates> sure, hang on..
<jhass> wow, 9 years and still didn't understand unix ACL system
<yates> setfacl and getfacl? never heard of them...
<yates> (and no, i didn't google or man -k for them..."
<jhass> I'd be satisfied with chmod, chrown and chrgrp for starters
<yates> chown?
<jhass> yeah
<jhass> usermod and groupmod would be bonus
<yates> why does bundler enforce policies that aren't its place to enforce?
<jhass> it doesn't enforce
<jhass> it crashes on parsing some yaml file
<jhass> probably because it has syntax errors
<yates> ah. then the last 5 minutes has been a total waste of time.
<jhass> still waiting for the pastie
<yates> it bloody won't do the install. that's
<yates> hmm.
<yates> paste buffer problem there - ignore that
<yates> hang on.
<tmoore> FWIW, the "Insecure world writable" warning comes from Ruby itself, not from Bundler https://github.com/ruby/ruby/blob/dfa336cd7ddc437314f36ce505c29e0e0d93659f/file.c#L5454
<tmoore> yates: can you post your Gemfile?
<tmoore> that error indicates an error evaluating it
<yates> tmoore: i'm very ignorant regarding ruby - what file would that be?
<tmoore> it's called Gemfile, it should be in the root of your project
<tmoore> actually, it's right there in the error /home/easl-redmine/Gemfile
<jhass> YAML::load(ERB.new(IO.read(database_file)).result)
<jhass> your config/database.yml has syntax errors
<tmoore> OK so it doesn't like something in config/database.yml
<jhass> go fix them
<yates> are you sure it's in the config/databaes.yml file, or something in the YAML parser? i saw some google searches that said the version of YAML had to be changed.
<yates> but i'll take another look at the database.yml
<yates> wups - i left out a comment
<yates> comment character, i.e.
<tmoore> well, it's a combination of the parser and the file :-)
<yates> ha.
<yates> :)
<yates> now it's running.
<tmoore> cool
<yates> thank you, tmoore and jhass
<yates> but still not to completion...
<tmoore> O_o pretty sure that means your gcc is screwed up
<jhass> or just too old
<yates> this is f20 with the latest/greatest.
<yates> gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7)
<yates> Copyright (C) 2013 Free Software Foundation, Inc.
<yates> This is free software; see the source for copying conditions. There is NO
<yates> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
<jhass> well, pg compiles here with 4.9.1, so I doubt it's too new ;)
<jhass> also pretty sure I compiled that on F20 before
<yates> must be the world-writable directory...
<jhass> yeah, maybe try fixing that :P
<tmoore> in any case... well outside of bundler territory
<yates> isn't that just when cross-compiling?
<yates> i'm not. this is native
<yates> so it's not really ruby or bundler, but rather the code ruby/bundler is executing? (that which generates that .c file?)
<jhass> where does that issue mention cross compiling?
<yates> i thought that's generally what one is up to when using binutils
<jhass> yes, both #gcc and #redmine are probably more suited at this point
<jhass> "A set of programs to assemble and manipulate binary and object files"
<tmoore> binutils are not just for cross compiling, no
<yates> well why would i use it when my package manager already provides all native assemblers/compilers ?
<tmoore> that is probably one of the packages it provides
<tmoore> it's part of the basic development toolchain on linux
<yates> aha. i didn't realize that package provides those! i was under the (mistaken) impression that it aids one in building (especially cross-compiling) those.
jhass is now known as jhass|off
x1337807x has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
yates has quit [Quit: rcirc on GNU Emacs 24.3.1]
havenwood has quit [Remote host closed the connection]
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
hagabaka has quit [Ping timeout: 260 seconds]
kgrz has quit [Ping timeout: 245 seconds]
hagabaka has joined #bundler
kgrz has joined #bundler
wsstudios has joined #bundler
kgrz has quit [Ping timeout: 260 seconds]
wsstudios has quit [Quit: Page closed]
kangguru_away is now known as kangguru
kgrz has joined #bundler
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
kgrz has quit [Remote host closed the connection]
kgrz_ has joined #bundler
heroux has joined #bundler
heroux_ has joined #bundler
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
kgrz_ has quit [Read error: Connection reset by peer]
kgrz has joined #bundler
robbyoconnor has quit [Excess Flood]
robbyoconnor has joined #bundler
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
jhass|off is now known as jhass
livingstn has joined #bundler
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
kgrz has quit [Remote host closed the connection]
kgrz has joined #bundler
kgrz has quit [Ping timeout: 272 seconds]
hagabaka has quit [Ping timeout: 272 seconds]
kangguru is now known as kangguru_away
hagabaka has joined #bundler
havenwood has joined #bundler
havenwood has quit [Client Quit]
kgrz has joined #bundler
axl_ has joined #bundler
pglombardo has joined #bundler
pglombardo has quit []
imkmf has joined #bundler
robbyoconnor has quit [Ping timeout: 260 seconds]
chouhoul_ has joined #bundler
kgrz has quit [Remote host closed the connection]
kgrz has joined #bundler
x1337807x has joined #bundler
x1337807x has quit [Max SendQ exceeded]
x1337807x has joined #bundler
chouhoulis has quit [Ping timeout: 250 seconds]
kgrz has quit [Ping timeout: 250 seconds]
chouhoul_ has quit [Ping timeout: 245 seconds]
x1337807x has quit [Ping timeout: 245 seconds]
x1337807x has joined #bundler
x1337807x has quit [Ping timeout: 272 seconds]
x1337807x has joined #bundler
x1337807x has quit [Max SendQ exceeded]
x1337807x has joined #bundler
axl_ has quit [Ping timeout: 245 seconds]
axl_ has joined #bundler
chouhoulis has joined #bundler
axl_ has quit [Ping timeout: 258 seconds]
fun has joined #bundler
<fun> hey folks
axl_ has joined #bundler
<fun> is there some easy howto on bundler?
<fun> for example how to bundle spree os commerce
<fun> or any kind of ruby apps
axl_ has quit [Ping timeout: 260 seconds]
ckrailo has joined #bundler
thumpba_ has quit [Remote host closed the connection]
x1337807x has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
thumpba has joined #bundler
newbie has joined #bundler
newbie is now known as Guest68615
<Guest68615> wondering is someone can give a newbie a quick hand... getting this error when running rails: /usr/lib/ruby/vendor_ruby/bundler.rb:85:in `ui': undefined method `new' for Bundler::UI:Module (NoMethodError)
<Guest68615> new install... ruby 2.1.2p95, Rails 3.2.19, Bundler version 1.7.3....
<Guest68615> error is dumped when bundle install is run...
<Guest68615> run bundle install /usr/lib/ruby/vendor_ruby/bundler.rb:85:in `ui': undefined method `new' for Bundler::UI:Module (NoMethodError)
pusewicz has joined #bundler
havenwood has joined #bundler
fun has quit [Ping timeout: 246 seconds]
<Guest68615> wondering is someone can give a newbie a quick hand... getting this error when running rails: /usr/lib/ruby/vendor_ruby/bundler.rb:85:in `ui': undefined method `new' for Bundler::UI:Module (NoMethodError)
<Guest68615> new install... ruby 2.1.2p95, Rails 3.2.19, Bundler version 1.7.3....
Guest68615 has quit [Quit: Page closed]
imkmf has quit [Ping timeout: 272 seconds]
imkmf has joined #bundler
imkmf_ has joined #bundler
imkmf has quit [Ping timeout: 240 seconds]
livingstn has quit []
havenwood has quit [Remote host closed the connection]
havenwood has joined #bundler
havenwood has quit [Remote host closed the connection]
WALoeIII has joined #bundler
jhass is now known as jhass|off
braidn has quit [Excess Flood]
g3funk has joined #bundler
igitoor has quit [Ping timeout: 272 seconds]
igitoor has joined #bundler
g3funk is now known as braidn
igitoor has quit [Changing host]
igitoor has joined #bundler
WALoeIII has quit []