User login

Subversion client for Ubuntu: anything like TortoiseSVN?

Ben,

In windows xp I used Tortoise SVN to edit files on the server for theming purposes. Do you know of a program that is like Tortoise SVN but will work in Ubuntu? Maybe you've got to use the Wine emulator? Let me know if you have any ideas.

Thanks,

Gus

You would think the currently most popular open source free software version control system would have a spiffy GUI client to work with it on the currently most popular open source free software desktop operating system, wouldn't you?

There is not, however any true turtle available for GNU-Linux. Wine would probably work but I've never heard anyone do this, it would be very strange as Subversion itself runs very well on GNU-Linux. It's probably already installed on Ubuntu (and if not, apt-get install subversion will take care of that.)

So, the source for all things SVN:

http://subversion.tigris.org/

has it's own project for a "Multi-platform GUI front-end for the Subversion revision system."

http://rapidsvn.tigris.org/

However, I never got into using it on the Mac in it's pre-1.0 state (I use SVN from the command line), and development has slowed to a crawl, or maybe stopped entirely for a nap like Aesop's hare.

Enter another tortoise:

http://toytoisesvn.sourceforge.net/

Don't you want a convenient SVNClient for Linux?
Why no one make it, for a long time?
Thus, I'll make it.
I think someday it becomes as convenient as famous SVN Client for Windows.

Good luck!

Resolution

Learn the command line for subversion.

Sure, now I'm playing the fox in that other Aesop's fable, that features out-of-reach grapes (I climbed the tree the vine was hanging from; they weren't sour but they weren't amazing either).

http://svnbook.red-bean.com/

That Subversion book will give you all the commands you need to use SVN without the Graphical User Interface sugar coating. Yeah, tortoise does some nice things but mostly it's just wrapping around two word commands anyway:

svn checkout https://server.example.com/srv/svn/agaric myworkingcopyfolder
svn status
svn update
svn add yournewfilehere
svn add yournewdirectoryincludingfiles/
svn commit -m "I made changes.  Woohoo."

You only need to do a command like that first one once on your desktop, and then do svn update to keep it in synch with Agaric's common repository. The other advantage of using the command line on Ubuntu, Mac OS X, or anything else Unix-ish is that these will be the exact same commands you can use on our Debian GNU-Linux servers.

Searched words: 
turtle TortoiseSVN svn Linux Drupal Subversion manual tutorial SVN graphical interface

Comments

See: http://kdesvn.alwins-wor

See:

http://kdesvn.alwins-world.de/

In debian or ubuntu:

apt-get install kdesvn kompare

HTH

Eclipse

I'm guessing the reason for the lack of GUI is the SVN support built into Eclipse. I was looking for an SVN GUI till I remembered all my development will be in Eclipse so I wouldn't need an external program, anyway!

You are lame, if you are

You are lame, if you are telling ppl to learn commands. It is gui that is making job easy and you can focus on more than just remembering stupid commands and pipes and writing them over and over again :p

It's a real shame how svn plugin in eclipse works. Anyone who is not used to it's "quirks" will make real mess in it and then it takes windows and svn tortoise to fix it.

If you could or not belive...

If you could or not belive... but sometimes it is better, faster to work with commands. I think in general it is much better.

At this point I think

At this point I think rapidsvn is the way to go

(on ubuntu)
sudo aptitude install rapidsvn
sudo aptitude install meld (for diff)

and for the record, learning commands isn't lame. How many mouse clicks would it take to install rapidsvn through your precious gui package manager? The point is, sometimes command line is better, other times gui is better. You'll probably end up using both anyway, that is unless you think that commands are lame, in which case you'll be missing out...

I tried rapidsvn, and it

I tried rapidsvn, and it comes quite handy.
Thanks for the tip.

tried these

both are simple and elegant... for merge, you can also try kdiff3.

I tried rapidsvn, it is

I tried rapidsvn, it is really cool,
but I couldn't find any way to update my code easily. It really works for me in the commit part, but I can't see the updated files. Sure, I can blindly update the rep, but I don't see what's new. It doesn't have the option???

svnclient like tourtoise for ubuntu

Just look here.

http://code.google.com/p/nautilussvn/

and do this

sudo apt-get install python-nautilus python-wxgtk2.6 python-svn meld

run this

Good luck.

!/usr/bin/env bash

Nautilus extensions live in ~/.nautilus/python-extensions - make sure that this directory exists.

mkdir -p ~/.nautilus/python-extensions/

Next checkout NautilusSvn into ~/.nautilus/python-extensions/NautilusSvn

cd ~/.nautilus/python-extensions/
svn checkout http://nautilussvn.googlecode.com/svn/branches/stable NautilusSvn

Setup the emblems

mkdir -p ~/.icons/hicolor/scalable
ln -s ~/.nautilus/python-extensions/NautilusSvn/icons ~/.icons/hicolor/scalable/emblems # The current emblems folder
ln -s ~/.nautilus/python-extensions/NautilusSvn/icons ~/.icons/hicolor/scalable/icons # The old emblems folder

Finally we need to set up a symlink so that Nautilus finds the correct startup script.

ln -s NautilusSvn/NautilusSvn.py NautilusSvn.py

Now just restart Nautilus, and you should see the new Subversion menu items.

1) nautilus -q && nautilus

2) killall nautilus

3) log out and back in again

nautilus -q && nautilus

Thanks!

That simple? ;-)

We're on Git now, any recommendations there?

Wait for v0.14 ;-)

Hi, I'm one of the developers on the NautilusSvn project. Thanks for the publicity (Visitor)! The next release will be v0.12 which will be a significant improvement over the current version, see the roadmap below for more details.

We also have Git support on our roadmap:

http://code.google.com/p/nautilussvn/wiki/Roadmap

Best regards,

Bruce

Correct the Link

Friend, good tool.
the link to download the branche change:
Insted:
svn checkout http://nautilussvn.googlecode.com/svn/branches/stable NautilusSvn
The Correct is:
svn checkout http://nautilussvn.googlecode.com/svn/tags/latest-snapshot/ NautilusSvn

Thanks good Post!
From Venezuela
I will publish IT in spanish ;-)

svn noob

Just beginning to cut my teeth on svn. as I've never used Tortoise, I guess I dont know what I am missing. While I would like a nice, easy gui to ease into, something dawned on me while reading the "you are lame" comment...

Programmers complaining about having to type commands? Isn't that like, the job? sure lots of the commands will be repetitive, but its easy to write a script or just use bash history. I think I will spend the time learning the basics of the command line first. Sure I may go gui someday, but it's amazing how useful my rusty DOS knowledge comes in at critical times. Levels of abstraction for convenience are nice, but no excuse for lack of knowlege.

Thanks for the book link, but does anyone have a 5 minute quickstart guide?

Nautilus

Nautilus looks very promising from the screen shot on Google Code! Suddenly I am really excited about SVN on Linux once again. Found the command line was not automatically adding files I have added to my workspace, which is what visual SVN does. It's annoying to have to remember to svn add a file and then later on svn commit a file from command line. I hope that Nautilus can give me a TortoiseSVN functionality as that's all I really need.

Command line is brilliant in many ways, for example when installing applications it's a magical process. which I am still fascinated by.

Problem with SVN command line

The problem with the SVN command line is that it cannot keep a directory tree committed. We have an SVN server and some of us use Eclipse (the programmers) and some use KDESVN and command line SVN. (webmasters and article writers, the non-geeks.)

Those using command line and/or kdesvn are FOREVER leaving files out of SVN because they have no way to effortlessly find those new files buried deep in their directory trees. Eclipse does this effortlessly, always scanning the entire tree for file adds, treating them exactly like edits on already committed files.

This is not a minor problem. A typical web page may have half a dozen new files spread throughout a website's directory tree and if someone is working on a few such pages at once, the typical scenario, then the effort to add-before-commit makes the whole process painful and error prone.

Nothing else that we know of besides Eclipse does this, which is the real problem.

Technically the SVN protocol is the fault, with a different transaction to initially add a file to version control vs. changing that file later. Since most SVN clients simply expose the protocol they carry the same error.

Any reasonable client must hide this fault from real users. None (besides Eclipse) do this, which is why the pain and why everyone is always looking for another client. If the svn command line actually worked it would be possible to put a button on someone's desktop that committed an entire project directory tree from the root, including new files.

I'm confused. A. What's

I'm confused.

A. What's wrong with 'svn st' to list all modified files in a directory and all paths below?
B. If my developers had an effortless way to commit newly added files etc in one go, then it'd muck up the wonderful stuff you can do with SVN commit messages and post-commit hooks that allows me to see commits grouped by issues etc.

With "A" "svn st" only list

With "A" "svn st" only list changes inside directories and subdirs already under SVN. But you won't in new directories to be added

With "B", if I need to answer a single issue with changes scattered all over the place, I would have to carefully add those files one
by one.

If you're looking for

If you're looking for non-versioned files (such as new files in your working copy), look for the files with question marks before them in the "svn status" output.

And yes, you'll need to add those files one by one with whatever svn tool you use, unless you "svn add * --force" as pointed out by another poster.

The real value for me with Tortoise and RapidSVN is that I can browse the repository graphically. It's way faster than exploring with "svn ls" when you don't know where to find a file/directory/project. My problem with RapidSVN is that it seems to have terrible difficulty with svn URLs with spaces in them. Most RapidSVN commands fail on these URLs.

How I manage when I have to

I prefer to to use TortoiseSVN or Eclipse, for just this reason. When I do have to use the command line, though, the command

svn add * --force

... makes the process fairly painless. You just need to do it (from the root directory) before each commit.

Utiliza RapidSVN es un

Utiliza RapidSVN es un cliente SVN bastante completo y de facil uso.

new TortoiseSVN clone

New year, new TortoiseSVN clone.
Check it out:
https://sourceforge.net/projects/pagavcs/
It's not as good as the mighty Tortoise, but usable. And it doesn't slow down the Nautilus...

Tortoise SVN for Linux

RabbitVCS is TortoiseSVN for Linux

http://rabbitvcs.org/

Easy version control for Linux
RabbitVCS is a set of graphical tools written to provide simple and straightforward access to the version control systems you use. Currently, it is integrated into the Nautilus file manager and only supports Subversion, but our goal is to incorporate other version control systems as well as other file managers.

RabbitVCS is inspired by TortoiseSVN and others.

http://rabbitvcs.org/

RapidSVN

5 min to get it up and running on Debian. I like this app.

TortoiseSVN for Linux

TortoiseSVN for Linux

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.