You are here


Eclipse Luna: java: /build/buildd/gtk2-engines-oxygen-1.4.5/src/animations/oxygencomboboxdata.cpp:87: void Oxygen::ComboBoxData::setButton(GtkWidget*): Assertion `!_button._widget' failed.

Submitted by Druss on Mon, 2015-02-02 18:03

After installing the shiny new version of Eclipse entitled 'Luna' on a Kubuntu 14.10 box, I found that it crashed/hung when trying to import/clone a Git repository. Starting the application from the command-line triggered the following notice before the crash:

Force a git merge "theirs" (even though it doesn't exist)

Submitted by Druss on Thu, 2012-02-09 23:12

A note to myself on how to force-sync my really outdated master branch with an active branch. This is taken from this excellent post:

git checkout -b tmp origin/upstream
git merge -s ours downstream
git checkout downstream
git merge tmp
git branch -D tmp

where upstream is the branch whose commits we want and downstream is the branch we want to merge into.

Resolving merge conflicts fixed manually in Eclipse/eGit

Submitted by Druss on Tue, 2012-01-03 23:03

I'm using Eclipse (Indigo) and eGit, its Git plugin. Earlier today, when I merged the contents of one branch with my master, I ran into a bunch of conflicts. While I suspect that I should have used the "Team > Merge Tool" to resolve them, as they were rudimentary in nature, I just sorted them out manually. However, eGit did not notice that the conflicts (and their in-file markers) were gone and retained the conflicted icon for each of the affected files.

SVN: Deleting removed/missing files

Submitted by Druss on Mon, 2011-11-07 22:56

I currently work with an SVN checkout which tracks a separate GIT checkout (for reasons of managerial short-sightedness). When I update my git checkout, I find that the SVN checkout does not like the fact that files deleted by the git update have effectively been removed from the SVN checkout without the use of svn rm. Consequently, it is impossible to commit the updated checkout into the SVN repository.

git-receive-pack not permitted error on pushing upstream

Submitted by Druss on Fri, 2011-07-08 22:53

If you ever run into a git-receive-pack not permitted error when using Git, chances are that it's a configuration issue on your end. In my case, I had cloned the repository using via https (which required authentication). However, pushing failed with the aforementioned error. This was due to the fact that I was only allowed to push via SSH. Therefore, once I changed the protocol in the configuration for my checkout, all was well again.

Subscribe to RSS - git