Piston 1.9.1: Import goodness
March 23rd, 2008
Well, with much more testing, I’m releasing another preview release of Piston. This release should import Subversion or Git repositories into Subversion or Git working copies just fine. There’s one slight problem, which is when you use piston import URL (without a target directory), it will import into a folder named repository, which isn’t what it’s supposed to do. I’m missing a couple of tests, is all.
How to grab this release ? Two ways:
git clone git://github.com/francois/piston.git- Grab a tarball
Once you have the code, run rake install_gem to install the gem. Enjoy !
March 23rd, 2008 at 07:43 PM
Ok I got 1.9.1 down – my svn repo is at https://host/svnroot/project
I want to piston for a library - I change into the directory and do
piston import https://host/svnroot/3rdParty/lib/tags/v1.0.0
Piston -guesses that it is git (which it is not) Then fails :( Sorry I think it is trying git first – then fails because it doesn’t understand https?
Am I missing an option to tell it that the repo isn’t a git repo?
March 24th, 2008 at 02:40 PM
Thanks for testing, Dirk. I haven’t tested git-ls-remote with an SSL URL. I’ll add that to my integration tests, and see if it works or not. And I have plans to add options to tell Piston what type of repository/working copy you have, so you don’t need to wait for Piston to guess.
April 11th, 2008 at 03:40 PM
Hi I get the following error Successfully built RubyGem Name: piston Version: 1.9.2 File: piston-1.9.2.gem sudo gem install—local pkg/.gem ERROR: Error installing pkg/piston-1.9.2.gem: piston requires main (~> 2.8.0) rake aborted! Command failed with status (1): [sudo gem install—local pkg/.gem…]
April 16th, 2008 at 09:51 AM
@Martin, that is another gem that is required. You’ll probably get the same error for open4 and log4r.