I installed RabbitVCS on my linux box which went without a hitch. Now I'm having trouble running the thing, I want to bring up the GUI. Naturally I tried rabbitvcs from the command line, then rabbitvcs SVN but no luck ( see output below ). I get usage info, but that didn't seem to help me much. How can I run it in GUI mode ?
--------------------------------------
flipper#matrix ~ $ rabbitvcs
Usage: rabbitvcs module [path1] [path2] ...
Available Modules
SVN:
about, add, annotate, applypatch, branch, browser, changes, checkmods,
checkout, cleanup, commit, createpatch, create, delete, diff, editconflicts,
export, ignore, import, lock, log, merge, properties, open, relocate, rename,
markresolved, revert, settings, switch, unlock, update, updateto
Git:
about, add, annotate, applybranch, branches, changes, checkout, clean,
clone, commit, createpatch, create, delete, diff, editconflicts, export,
ignore, log, merge, open, push, rename, remotes, reset, revert, settings,
tags, update
For module specific help type: rabbitvcs -h
flipper#matrix ~ $ rabbitvcs SVN
flipper#matrix ~ $ rabbitvcs SVN -h
flipper#matrix ~ $
As you can see here, RabbitVCS is actually a Nautilus plugin. Try taking a look at your working copy through Nautilus.
It has no separate GUI.
By the way, I actually tried using it for a while, but I found it somewhat slow and clumsy. I switched to using the SVN and git console commands.
I later found that meld actually provides me with a very nice visual diff. It understands SVN and git, but you'll need the very latest version to make the git diff work just right.
To me
nautilus -q
after installation was enough to show up in Ubuntu.
I am currently using Opensuse 13.1
My problem was that there was no RABBITVCS menu on nautilus.
When starting Nautilus, I discovered that nautilus clomplaims of not having the "python3-simplejson python-simplejson" libraries.
Unfortunately i don't know why the zypper didn't install it when installing rabbitVCS package.
Uninstall rabbitvcs using sudo apt-get purge rabbitvcs* and reinstall it using below command lines on Ubuntu.
sudo add-apt-repository ppa:rabbitvcs/ppa
sudo apt-get update
sudo apt-get install rabbitvcs-nautilus
nautilus -q
and close the already opened window and reopen and right click. You will get RabbitVCS SVN, Git and Hg option on the screen. It's tested on Ubuntu 18.04 and 16.04.
Related
So, in addition to GitKraken won't let me clone from a private repo on GitHub
I get this screen when opening my GitLab Repo:
Anyone got a solution of how to make my Repo 'non-private' or how to make GitKraken let me open this without the Pro Plan?
Already tried:
Generating new SSH Key in GitKraken
Removing Repo, Generate new GitLab connection, Clone Repo
Checked GitLab: GitKraken is an Authorized applications
Git Pull via command line gives no trouble, so no permission issue
...
6.5.1 is the last version to support private repo. You can see the release details at this link https://blog.axosoft.com/gitkraken-v6-0/#pricing-changes OR https://support.gitkraken.com/release-notes/6x/
And you can also download it (Mac version) from Axosoft https://release.axocdn.com/darwin/GitKraken-v6.5.1.zip OR https://release.gitkraken.com/darwin/GitKraken-v6.5.1.zip
I not sure how to turn off the automatic update function, so if you turn off GitKraken completely and reopen it, it will update to the latest version.
=======
Updated
Block IP Address for updating
For MacOS
echo "127.0.0.1 release.gitkraken.com" >> /private/etc/hosts
Windows 10 – “C:\Windows\System32\drivers\etc\hosts”
Linux – “/etc/hosts”
Mac OS X – “/private/etc/hosts”
Installing older version of Gitkraken is the only solution I guess to work on private repo if you want it for free and without student developer pack.
From the release notes, the last version to support private repo is v6.5.1.
Download link:
For windows: https://release.gitkraken.com/win64/GitKrakenSetup-6.5.1.exe
For linux (debian): https://release.axocdn.com/linux/GitKraken-v6.5.1.deb
For linux (tar.gz): https://release.axocdn.com/linux/GitKraken-v6.5.1.tar.gz
For mac: https://release.axocdn.com/darwin/GitKraken-v6.5.1.zip
Download old version of app
Official download URL for macOS. For Win you have link on Comments in this answer
EDIT:
OMG! I found it.
There is auto patcher who was build over yarn
https://github.com/5cr1pt/GitCracken
Work like a sharm 💪
Note:
It take a decent time to install, so be patient.
I had the same problem, this what I found:
They say, and I quote -
This was a licensing change we made 3 months ago. When we made the
change, we gave all existing users a 3 month free trial, which are all
expiring this week. Sounds like yours is one of them
BTW worth noting that if you're a student, you can use GitKraken for free:
https://www.gitkraken.com/student-resources
My solution is to uninstall GitKraken and install Fork, a very similar program with all the options that I have used previously in GitKraken. It's free and has a dark mode too :-)
(window users)
In your %appdata%/../Local/gitkraken, remove latest gk version you just updated, remove updater & use the previous version (& maybe buy a license)
(Windows solution)
I think this solution should work:
Since Private repo is moved to paid plan after v6.5.1 so make sure you download an earlier version (For example Windows: 5.0.4 - Change version number to any desired one)
If you had a newer version installed, get rid of it like this:
Uninstall that version
Go to C:/Users/USERNAME/appdata/local/ and remove GitKraken
Go to C:/Users/USERNAME/appdata/roaming/ and remove .gitkraken
Install the selected older version
Go to C:/Users/USERNAME/appdata/local/gitkraken and rename Update.exe to Update_.exe (Don't remove it. Needed for uninstalling)
Use it
Note: I had issues with some repos even with this solution and that could be because gitkraken saves config file in the repo (which is not shared with remote). So make sure you remove the local project and get it from remote again.
(Note: Newer version obviously contains more features. You may want to purchase a license to be updated and fine, as well as supporting the company)
If you have tried running GitKraken 6.5.1 on a recent version of Ubuntu, you have probably noticed that it has dependencies that can't be satisfied (gvfs-bin). However, you can run it in Docker by building an image for it based on Ubuntu 18.04!
Download the GitKraken package:
wget https://release.axocdn.com/linux/GitKraken-v6.5.1.deb
Create a Dockerfile. Replace YOURUSERNAME with your local username. Replace 1000 with your actual user and group IDs respectively:
FROM ubuntu:18.04
COPY GitKraken-v6.5.1.deb /tmp
RUN apt update && apt install gconf2 gconf-service libgtk2.0-0 libnotify4 libxtst6 libnss3 libxkbfile1 python gvfs-bin xdg-utils xauth libxss1 libasound2 -y
RUN dpkg -i /tmp/GitKraken-v6.5.1.deb
RUN groupadd -g 1000 YOURUSERNAME && useradd -u 1000 -g 1000 YOURUSERNAME
CMD ["/usr/bin/gitkraken", "--no-sandbox"]
Build the Docker image:
docker build -t gitkraken .
Allow Docker to connect to your local XServer:
xhost +local:docker
Run your GitKraken in a container, mapping your local home directory into the container. Again, replace your username and IDs:
docker run -ti --rm -e DISPLAY=$DISPLAY --network=host -v /home/YOURUSERNAME:/home/YOURUSERNAME --user 1000:1000 gitkraken
Uninstall and use an older version of gitkraken. V5.0.4 will continue to work as always.
Gitkraken does not update automatically in Linux, so Axosoft can't shove it down your throat. For Windows, there's SourceTree. Consolations to Mac users.
I have the GitKraken individual plan and can only use my account on one computer.
My laptop displays the same message regarding the private repository and blocks me. I thought that the individual plan would allow my single account on multiple computers.
I have been using GitKraken free version for more than an year. I ran into the same issue recently. I was able to get it working by reinstalling an older version.
Note: You need to do this whenever you restart your computer or Gitkraken.
My solution:
Remove the latest version from (window users) appdata%/../Local/gitkraken
Create a short cut to the folder where the previous version is installed.
Open shortcut
Start executable.
What happens when the update come up again. I will see then.
If anyone is looking for a solid Git linux client, try GitClient, they have an AppImage,
it doesnt have all features of Kraken but very solid,
https://github.com/francescmm/GitQlient
Save your files of Repository - Without Folder (.git)
Create new public repository
Copy and Commit your Files
Open your Repo (Git Kraken).
To expose your project from gitlab, go to Settings => General and select public under the "Visibility, project features, permissions" section.
To open a private repo under GitKraken, subscribe to their licence.
I had downloaded sublime previously directly from the browser as tarball and saved it in a folder (and of course extracted it).But this way I wasn't able to make Sublime my default editor and it didn't feature as an application when I tried to open a text file with a right-click.I read somewhere installing sublime text 3 using commands:
sudo add-apt-repository ppa:webupd8team/sublime-text-3
sudo apt-get update
sudo apt-get install sublime-text-installer
will solve my problem. So I directly deleted the Sublime_text3 folder saved in my Downloads directory and then used the given commands. But when I entered the 3rd command line I got the following error(just writing the error part):
subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:/var/cache/apt/archives/sublime-text-installer_3126-2~webupd8~1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Can anyone explain why this error is coming and suggest a way to solve this problem? Also if anyone can tell how I can set Sublime as my default text editor from the tarball downloaded from the sublime text 3 website. Thanks in advance!
you can try this command to install Sublime Text using Snap Store..
sudo snap install sublime-text --classic
I'm not sure overall how to fix that error or what's going on (I use Slackware and not Ubuntu/Debian), but for a long while there have been official Sublime repositories several different Linux distributions, including Ubuntu/Debian.
It's highly recommended that you use those if you want to go the package route and not use existing solutions such as the one referenced in your question or in the other response here, if for no other reason than only the official repository is guaranteed to contain an unmodified version of Sublime. Additionally the official repositories are always updated on release, which may or may not happen in a timely manner in other repositories.
The links referenced above contain instructions on how to set up and use Sublime from those repositories, and if you have any issues a good place to ask is the forum.
One thing to note which isn't mentioned explicitly in the above pages is that to use the official repositories, you should:
Choose only one of them (stable or dev, noting that you need a license to run a dev version) and not add both repositories or things will not work as expected
Ensure that other repositories that you've added (such as the one in your question) are removed to make sure that the package system definitely pulls the correct package
There are a couple of ways to go if you want to install Sublime from the tarball version. The easiest way would be to extract it, then manually set up launcher shortcuts and so on based on what falls out. How exactly you would register it as a text editor in that case, I'm not entirely sure since I don't use the same distribution as you.
Presuming that the process would be easier if Sublime was installed in a way similar to how the package manager would do it, the tarball comes with a desktop file and icons, so the following steps can be used to (presumably) do what the package installer would do.
The proviso here is that although these steps work on my non-Ubuntu machine, I don't know if all of the referenced tools are installed by default on an Ubuntu system, so so more setup work may be involved.
Note also that the files in the tarball are not entirely self-consistent, which makes this a little bit more work.
First, you need to extract the tarball (replace tarball filename as appropriate for location and build):
cd /opt
sudo tar xvf ~/Downloads/sublime_text_3_build_3176_x64.tar.bz2
This creates the folder /opt/sublime_text_3/ and fills it with the contents of the tarball.
Next, you want to install the icons contained in the tarball. As far as I have been able to tell, the icons in the tarball aren't in the correct directory structure, requiring each to be copied into place individually. We also need to update the icon cache to ensure that the new icon is noticed by the system:
cd /usr/share/icons/hicolor/
sudo cp /opt/sublime_text_3/Icon/16x16/sublime-text.png 16x16/apps/
sudo cp /opt/sublime_text_3/Icon/32x32/sublime-text.png 32x32/apps/
sudo cp /opt/sublime_text_3/Icon/48x48/sublime-text.png 48x48/apps/
sudo cp /opt/sublime_text_3/Icon/128x128/sublime-text.png 128x128/apps/
sudo cp /opt/sublime_text_3/Icon/256x256/sublime-text.png 256x256/apps/
sudo gtk-update-icon-cache -f -t .
Now we want to install the sublime_text.desktop file that is in the tarball. Note however that like the icons, it seems kind of broken; the tarball extracts to sublime_text_3 but the desktop file assumes that the application is actually in /opt/sublime_text instead.
As such, you either need to rename the folder that was extracted to sublime_text to match what is in the desktop file, or edit the desktop file to make the path correct.
The following steps assume that we want to keep the folder the same and rewrite the desktop file. These commands will generate a new file named sublime_text_3.desktop with the changes.
cd /opt/sublime_text_3/
sed -e "s^/sublime_text/^/sublime_text_3/^" sublime_text.desktop | sudo tee sublime_text_3.desktop
Now you can install the desktop file. You do that with desktop-file-install, passing it the name of the desktop file. For accessing Sublime from the command line, you also want to set up a subl link to the installed copy of Sublime.
Adjust the paths as appropriate here if you decided to rename the folder instead of editing the desktop file:
sudo desktop-file-install sublime_text_3.desktop --rebuild-mime-info-cache
sudo ln -s /opt/sublime_text_3/sublime_text /usr/bin/subl
At this point Sublime should show up as an installed application, or at least it does in my Window Manager; if not, executing sudo update-desktop-database may help refresh it.
You can try this once. i hope it will help
wget https://download.sublimetext.com/files/sublime-text_build-4126_amd64.deb
sudo dpkg -i sublime-text_build-4126_amd64.deb
I am trying to install package control in Sublime Text editor 3 on Ubuntu 14.04 . I follow simple instruction from https://sublime.wbond.net/installation.
But I get follow error:
Package Control: Error downloading channel. b'curl: (7) Failed to connect to sublime.wbond.net port 443: Network is unreachable' downloading https://sublime.wbond.net/channel.json.
error: Package Control
Go back to the installation page and follow the instructions in the Manual section:
Click the Preferences > Browse Packages… menu
Browse up a folder and then into the Installed Packages/ folder
Download Package Control.sublime-package and copy it into the Installed Packages/ directory
Restart Sublime Text
This should install Package Control for you without any problems.
EDIT
Please read through this issue here, and follow wbond's instructions to install from git. First, completely quit Sublime, then remove all traces of Package Control - any folders in ~/.config/sublime-text-3/Packages, any files in ~/.config/sublime-text-3/Installed Packages, the folder ~/.config/sublime-text-3/Packages/User/Package Control.cache, and any files in ~/.config/sublime-text-3/Packages/User that start with Package Control.* - Package Control.last-run, Package Control.sublime-settings, Package Control.system-ca-bundle, and anything else you can find.
Next, assuming you have git installed (run sudo apt-get install git if you don't), switch to ~/.config/sublime-text-3/Packages and run
git clone https://github.com/wbond/package_control.git "Package Control"
to clone the master repo (make sure you've completely quit Sublime before running this). Restart Sublime and see if everything installs properly. If not, follow the instructions for creating a debug log, restart Sublime to generate the log, open the Console by selecting View -> Show Console, then copy the entire contents (it'll be a lot) into a new file. Open a new issue and describe exactly what the problem is, including all the details above and the fact that you just installed from the master branch, and paste in the contents of the debug log (make sure you put it in a code block by adding triple backticks ``` before and after). Will Bond (wbond) should get in touch with some suggestions.
Good luck!
Note for users of other operating systems: I'm not sure if this is a Linux-only problem or not, but in case it isn't, Mac users will find Packages and Installed Packages in ~/Library/Application Settings/Sublime Text 3, while Windows users with standard (i.e., non-portable installs) will find them in your user directory under AppData\Roaming\Sublime Text 3. For Windows portable installs, the directories should be in your install directory under Data.
For the sublime text version 3126 onward Package Control is disabled by default. Just go to Preferences > Settings and remove Package Control from the ignored_packages setting.
I was having the same problem on Linux Mint 18.1 (Ubuntu derivative), and after reading a few posts here and there, it occurred to me that something had likely become corrupted, so I: 1) uninstalled sublime; AND then 2) deleted everything related to sublime from "/home/thom/.config/". Step 2 was the real key. Then I reinstalled sublime according to "apt" section HERE. Once reinstalled, package control was able to install without error.
I'm really frustrated with getting going using VIM. I'm just trying to do some minor customizations to the vimrc file. I made some minor changes, but they didn't do what I had hoped. So, I went back in and removed the lines that I had added, reverting back to my original file. Now, I can't even get into VIM! When I type "vim filename.xxx" from the terminal, I just go right back to a command prompt. No error message, no file opens, nothing. It's as if I just hit the enter key.
I tried uninstalling and reinstalling VIM, but same results. Does anyone know what I can do to get VIM back to its original state? I'm using Ubuntu 11.
I would suggest first uninstalling but purging, reinstalling, and making sure your local user edits are removed.
Purge to remove the package config files: sudo apt-get purge vim.
Clean out any personalizations: rm -Rf ~/.vim ~/.vimrc ~/.viminfo.
Reinstall Vim again: sudo apt-get install vim.
Try removing the ~/.vimrc and ~/.viminfo files and the ~/.vim directory. These usually contain configuration information so getting rid of them should give you a fresh start
I'm getting "skipping XXX: it is not a regular file" every time I run ctags -R XXX. For one reason or another, ctags on Cygwin isn't recursing directories. Surely, I must be doing something stupid.
Whenever I try the de-facto standard ctags -R in my project root, it complains that I didn't specify any input files. When I specify a directory, it seems to think its a file.
I'm a tad stumped. I installed a fresh Cygwin build last week from scratch. I installed everything. I rarely use Cygwin. ctags works perfectly on all my BSD, Linux, Mac and Solaris boxes.
I thought Perforce's read-only permissions might have been the culprit, but chmod 777 changes nothing.
Any ideas? Should I recompile from source?
As is currently being discussed on the Cygwin mailing list, the xemacs-tags and ctags packages both install /bin/ctags. The behaviour you're seeing is from the xemacs version.
The developers will sort it out, although that may take a little while. In the meantime, do the following to get Exuberant Ctags (with its working -R option) installed:
Run the Cygwin installer again (download setup.exe again if you need to).
At the package list, search for "tags" and click the "New" column for both "ctags" and "xemacs-tags" until they say either "Skip" or "Uninstall" (one's under "Devel", the other under "Editors".
Hit "Next".
Once the install has completed, click "Back" instead of "Finish" (if you do this wrong, just restart the installer).
At the package list, select to install "ctags" only. As of today (12 December 2012), that'll specify version 5.8-1.
Click Next and let the install finish.
That'll give you the "ctags" package without the "xemacs-tags" package, and you should be good to go.
I'm getting the same problem, just installed full Cygwin Oct 2012. Downloaded Exuberant Ctags source, compiled, and no more problem.