Package Base Details: gnome-sharp

Git Clone URL: (read-only, click to copy)
Submitter: quequotion
Maintainer: None
Last Packager: quequotion
Votes: 4
Popularity: 0.73
First Submitted: 2017-04-01 18:39
Last Updated: 2019-11-19 15:22

Pinned Comments

quequotion commented on 2019-11-10 09:19

This metapackage has a significant AUR dependency chain. In order to build it in a clean chroot (without using an AUR helper), you will have to preinstall its dependencies and their dependencies (after clean chroot building each of them):

makechrootpkg -c -r $CHROOT \
-I ../libgnomeui/libgnomeui-2.24.5-3-x86_64.pkg.tar.xz \
-I ../libbonoboui/libbonoboui-2.24.5-3-x86_64.pkg.tar.xz \
-I ../libgnome/libgnome-2.32.1-7-x86_64.pkg.tar.xz \
-I ../libgnomecanvas/libgnomecanvas-2.30.3-4-x86_64.pkg.tar.xz \
-I ../libgnome/libgnome-data-2.32.1-7-x86_64.pkg.tar.xz \
-I ../gnome-vfs/gnome-vfs-2.24.4-11-x86_64.pkg.tar.xz \
-I ../gnome-mime-data/gnome-mime-data-2.18.0-8-any.pkg.tar.xz \
-I ../gamin/gamin-0.1.10-9-x86_64.pkg.tar.xz \
-I ../libbonobo/libbonobo-2.32.1-4-x86_64.pkg.tar.xz \
-I ../orbit2/orbit2-2.14.19-7-x86_64.pkg.tar.xz

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

bititanb commented on 2017-09-15 15:44


Thanks for the fixes.


For now maybe we can ship the version with the patch? I got the patch from FuzzyCheese, made some fixes, so no changes needed from you.
Here are the patch and PKGBUILD:

Btw, I removed some old patches that already in upstream.

FuzzyCheese commented on 2017-09-02 23:48

Upstream problem in mono/gnome-sharp
A file is being specified "gconf-sharp.dll" instead of just the directory name in gnome-sharp/sample/gconf/ line 25.

PATCH: fix_mono_path.patch
Apply patch file to extracted gnome-sharp package snapshot: patch -i fix_mono_path.patch
The error is raised on line 438 in mono/mono/metadata/assembly.c because with a file specified it fails the directory test "g_file_test (*splitted, G_FILE_TEST_IS_DIR)"

I could only find other uses of MONO_PATH as directory and never as a file.

A file has been specified in gnome-sharp/sample/gconf/ for at least 11 years.
Two years ago mono_set_assemblies_path (mono_path) was implimented.
Prior to that change it looks like the DirectoryInfo function was used and it does not care if a file is specified as stated here:
"In members that accept a path, the path can refer to a file or just a directory."

I think the mono change on Mar 15, 2016 triggered this problem but is not the cause.

The error can be traced like this:
gnome-sharp/sample/gconf/ line 25 - Set MONO_PATH env and exicute mono.

mono/mono/tests/assembly-load-remap.cs line 30 - Use value from MONO_PATH as parameter to function mono_set_assemblies_path.

mono/mono/metadata/assembly.c line 438 - Raise warning if path value is not a directory.

glib function g_file_test() - Tests filename.

quequotion commented on 2017-06-23 01:11


Has anyone tried to build this on another distro? I'm curious if this problem is upstream or if something can or should be done about it for arch in particular.

f3flight commented on 2017-06-22 18:39

The fix is to delete error line from src/gnome-sharp-2.24.3/sample/gconf/Settings.cs and re-run makepkg / pacaur / whatever

Raqbit commented on 2017-06-13 18:45

Same issue here. Has any fix been found as of now?

zllvm commented on 2017-05-31 20:08

Have the same problem. It happens due to the following error is written into Setting.cs file as a first line:
'/tmp/yaourt-tmp-xxx/aur-gnome-sharp/src/gnome-sharp-2.24.3/gconf/GConf/gconf-sharp.dll' in MONO_PATH doesn't exist or has wrong permissions.

Related file:

Cysioland commented on 2017-05-27 14:52

Does not compile, with error

Settings.cs(1,1): error CS1012: Too many characters in character literal
Settings.cs(1,93): error CS1525: Unexpected symbol `/'
Settings.cs(1,114): error CS1012: Too many characters in character literal

quequotion commented on 2017-04-08 09:12

Indeed, it is fixed!

I've updated the package to build the git master; there's not a tarball release yet.

Yah commented on 2017-04-07 16:50

If i read that right, the problem should be fixed:

quequotion commented on 2017-04-02 08:39

See my comment below and the bug report on xamarin. Unfortunately, we cannot build this package or its dependencies (glippy, monodevelop) until a solution is found. If you still have the package that was available from [extra] in January installed don't remove it!

My hope is that having the package available will attract the attention needed to get something done about it. Although it was removed from [extra], there are still a few AUR packages that depend on it.