Package Details: goland 2022.1.3-1

Git Clone URL: (read-only, click to copy)
Package Base: goland
Description: Capable and Ergonomic Go IDE
Upstream URL:
Licenses: custom:jetbrains
Conflicts: gogland
Replaces: gogland
Submitter: freswa
Maintainer: freswa
Last Packager: freswa
Votes: 47
Popularity: 0.25
First Submitted: 2017-11-02 17:42 (UTC)
Last Updated: 2022-06-23 12:51 (UTC)

Dependencies (3)

Required by (0)

Sources (3)

Pinned Comments

Latest Comments

freswa commented on 2022-04-08 14:51 (UTC)

Added to my git staging area, will be implemented with 2022.1

dcelasun commented on 2022-04-08 14:30 (UTC)

@freswa can you update the package to use goland.svg instead goland.png as the icon? It's newer and much sharper. Just changing line 36 is enough.

freswa commented on 2021-01-19 22:22 (UTC)

You can overwrite the vmoptions in ~/.config/JetBrains/GoLand2020.3/goland64.vmoptions e.g. with

# custom IntelliJ IDEA VM options


vstollen commented on 2021-01-19 22:17 (UTC)

After I updated jre-openjdk (14.0.2.u12-1 -> 15.0.1.u9-1) Goland didn't start for me with the error message:

Unrecognized VM option 'UseConcMarkSweepGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Installing goland-jre fixed this. When starting goland using the goland-jre I get the following warning:

OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.

Could it be, that the option is dropped in the new version and jre-openjdk therefore isn't a valid java-runtime for this package anymore?

x1unix commented on 2020-07-09 21:59 (UTC)

GoLand 2020.1.4 recently released. Can you please provide an package update?

ArchFeh commented on 2020-03-01 20:43 (UTC)

I think the icon path in the jetbrains-goland.desktop is /opt/goland/bin/goland,there is no need with suffix .svg, because with suffix in launcher of KDE cant show icon properly

commented on 2020-02-10 14:07 (UTC)

@freswa @zrhoffman found the reason.

when download it from China with the url: get wrong sha512sum.

So, i use a server in HongKong, wget the file again. sha512sum is right now. looks like use a cdn , and the cdn is not sync all right everywhere.

freswa commented on 2020-02-10 12:55 (UTC)

I'm still getting the checksum in the PKGBUILD...

zrhoffman commented on 2020-02-10 12:55 (UTC)

@rool: Removing the downloaded files and rebuilding the package, I get 9741675570ee4d17251ce5a7661e8ff052d3b5753de9c297f847631c99e74ab22793450b6738cb222a587063ae26d4fda0e4c5a1f69573282d8b03bc3578736c for goland-2019.3.2.tar.gz's sha512.

commented on 2020-02-10 12:39 (UTC)

Install goland faild. I found that: in PKGBUILD file goland-2019.3.2.tar.gz


but when i

sha512sum goland-2019.3.2.tar.gz

59216cc207f6c55bc7c2711bcd6eba86e91120cb439d8c464612e08d696122b1301760d21736b53240c4618270788297b652ea5872757aaf066ad9ad0e18ecd0  goland-2019.3.2.tar.gz

freswa commented on 2019-07-24 19:18 (UTC)

There is no circular dependency in this package.

alexykot commented on 2019-07-24 18:28 (UTC)

@zrhoffman And I don't say it is. I say that the requirements of goland and goland-jre create a circular dependency issue and any of them fails to install.

zrhoffman commented on 2019-07-16 16:44 (UTC)

@alexykot goland-jre is not required if you have a package that provides java-runtime.

alexykot commented on 2019-05-20 18:01 (UTC)

Install with packer fails for me right now with error: 'goland-jre-2019.1.2-1-x86_64.pkg.tar.xz': duplicate target

Seems like goland and goland-jre require each other and both packages build each other and end up trying to install two copies of both goland-2019.1.2-1-x86_64.pkg.tar.xz and goland-jre-2019.1.2-1-x86_64.pkg.tar.xz. I workarounded by installing built packages manually with pacman -U goland-2019.1.2-1-x86_64.pkg.tar.xz and pacman -U goland-jre-2019.1.2-1-x86_64.pkg.tar.xz.

freswa commented on 2018-11-11 12:02 (UTC)

@beanaroo: I don't modify the desktop.file. It's an export from goland.

beanaroo commented on 2018-11-11 04:12 (UTC)

Thanks for maintaining this, @freswa!

I'd like to request the .desktop file to use Icon=goland instead of an absolute path. This allows the theme icon to be used (like for IntelliJ and Pycharm).

I believe this will also require copying the included icon to the system icons path. i.e.

  install -D -m644 "$pkgdir"/opt/$pkgbase/bin/goland.png "$pkgdir"/usr/share/pixmaps/"$pkgname".png

Liikt commented on 2018-01-09 12:18 (UTC)

Ah okay. That worked smoothly. Thank you very much

dcelasun commented on 2018-01-09 09:10 (UTC) (edited on 2018-01-09 09:10 (UTC) by dcelasun)

Yes, the folder name is wrong. As a quick fix, run the following in the build directory:

$ makepkg -o
$ mv src/GoLand-2017.3{,.1}
$ makepkg -esi

Liikt commented on 2018-01-09 07:52 (UTC)

Could it be that the name of the folder that is compressed is wrong currently? The folder that comes out for me is called GoLand-2017.3 and should be GoLand-2017.3.1.

hexvalid commented on 2017-12-15 09:49 (UTC)

oh sorry, its working

hexvalid commented on 2017-12-15 08:23 (UTC)

expired build

nerzhul commented on 2017-11-26 09:35 (UTC)


agilob commented on 2017-09-26 16:57 (UTC)

Gogland no longer starts after upgrade to jdk9 Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. intx MaxJavaStackTraceDepth=-1 is outside the allowed range [ 0 ... 1073741823 ] Improperly specified VM option 'MaxJavaStackTraceDepth=-1' Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.

n0rad commented on 2017-06-15 22:38 (UTC)

debugging test is not working until you run : # sudo chmod +x /opt/gogland/plugins/intellij-go-plugin/lib/dlv/linux/dlv

mixedCase commented on 2017-03-22 19:19 (UTC)

Split packages cause issues with AUR helpers, which is why maintainers tend to avoid them for the AUR.

freswa commented on 2017-03-19 20:18 (UTC)

@ginabythebay: This is a so called "split package". What is the exact error you got?

ginabythebay commented on 2017-03-19 18:30 (UTC)

Like intagger, I am now also unable to update gogland because this aur entry now seems to contain two packages. I tried uninstalling gogland and reinstalling it and got the same failure.

freswa commented on 2017-02-20 05:16 (UTC)

I split the package due to a discussion on the aur mailing list. It's now easier to install gogland without the bundled jre.

intagger commented on 2017-02-19 21:02 (UTC)

Why you have added the gogland-jre in the PKGBUILD? +pkgname=(gogland gogland-jre) I was unable to update the gogland, because it wants to install two packages now: gogland and gogland-jre.

intagger commented on 2017-02-19 07:39 (UTC)

Y U do not update?

freswa commented on 2016-12-25 00:45 (UTC)

This will follow the EAP branch until gogland hits stable. It will then switch to the stable releases immediately.

farwayer commented on 2016-12-16 12:23 (UTC)

@justinus gogland is in closed beta still.

justinus commented on 2016-12-16 06:08 (UTC)

==> Retrieving sources... ==> ERROR: {pkgname}-2016.3.tar.gz was not found in the build directory and is not a URL. ==> ERROR: Makepkg was unable to build gogland.