Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - gitextensions

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: gitextensions 1:2.49-1

Git Clone URL: https://aur-dev.archlinux.org/gitextensions.git (read-only)
Package Base: gitextensions
Description: Graphical user interface for Git that allows you control Git without using the commandline.
Upstream URL: http://gitextensions.github.io/
Licenses: GPL3
Submitter: k2s
Maintainer: sebo
Last Packager: sebo
Votes: 10
Popularity: 0.331872
First Submitted: 2012-06-08 17:16
Last Updated: 2016-11-17 21:29

Latest Comments

rjbris commented on 2016-11-17 00:08

Thanks for maintaining this AUR package BTW

FSMaxB commented on 2015-05-10 13:49

Please update to 2.48.04, this fixes a bug ( at least for me ) that closing the commit window doesn't crash the entire application.

UPDATE: Actually it doesn't fix this. I'll talk with upstream. Nevertheless please update to .04

FSMaxB commented on 2015-05-10 13:46

Please update to 2.48.04, this fixes a bug ( at least for me ) that closing the commit window doesn't crash the entire application.

And1G commented on 2013-10-08 20:00

Thank you! I hope this bug gets fixed upstream.

k2s commented on 2013-10-07 06:50

uploaded temporary fix for upstream bug https://github.com/gitextensions/gitextensions/issues/1960#issuecomment-22488217

And1G commented on 2013-10-06 21:09

GitExtensions crash when I try to open a repository. The Bug seems to be related to this here, the selected solution (disabling the plugins) works: https://github.com/gitextensions/gitextensions/issues/1960#issuecomment-22488217
This is the console output I get when I try to open a repository: http://pastebin.com/FQzNVa1E
If I move the two plugins as suggested in the above comment, it works fine.
Is it possible to fix this issue in the package?