Excerpts from William Morgan's message of Mon Apr 27 11:46:43 -0600 2009: > Reformatted excerpts from John Bent's message of 2009-04-27: > > I'm sorry. I don't remember. The timestamp on my sup executable says > > Jan 13 2009. I'll try to upgrade and see if I ever see this again. > > Yeah, I think it was around March that things got merged in. Try it with > the latest & greatest and see if it happens again. > Ok, I figured out what the problem was. I used to be able to stay current with git pull; rake gem; sudo gem install pkg/sup-999.gem. But with a new work proxy and my inability to get git to work w/ a proxy, I switched to:
git clone http://git.gitorious.org/sup/mainline.git Then I couldn't figure out how to make a gem in mainline or install so I just figured out I could approximate an install by copying bin/* into my path . . . forgot the lib. Anyway, I got the scary exception again and looked at exception-log.txt and realized I had a mismatch with my libs. So now I'm doing the git clone mainline thing and using ruby -l lib -w bin/sup. Anyway, at the risk of embarrassing myself, I wanted to get this info out there in case some other poor schlub wanders down my same convoluted path. Thanks, John _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
