Package Details: lazygit 0.20.4-2

Git Clone URL: (read-only, click to copy)
Package Base: lazygit
Description: A simple terminal UI for git commands
Upstream URL:
Licenses: MIT
Submitter: frealgagu
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 12
Popularity: 1.62
First Submitted: 2018-08-07 17:18
Last Updated: 2020-06-19 22:44

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

caleb commented on 2020-05-25 14:50

New Go package guidelines are official now and go-pie is going away. If you add me as a co-maintainer I'd be happy to bring this up to date. I maintain precompiled packages in my repo so I'd like to keep the build process clean!

caleb commented on 2020-03-20 13:40

Just a heads up, Arch go package recommendations are about to change. The main Go package can now be used with flags in a way that obsoletes go-pie, which is being dropped.

frealgagu commented on 2020-02-12 22:49

I got it. Yes, the other packages that have the go-pie dependency force to replace go by go-pie (you don't need to uninstall go manually because it's impossible due to other dependencies but replacing the package it's possible while the installation is done, then you can install go again). Other alternative is to use a build in a clean chroot.

efficientbug commented on 2020-02-12 15:28

@frealgagu yes, I only managed to build it by editing the PKGBUILD. I uninstalled it to reproduce the issue I had before (both with yay and makepkg). I don't know how other Go packages do it, but if you look at the packages go and go-pie themselves you can see that while go-pie provides go, go provides None. So maybe that's the issue, because I believe that if I have go-pie installed I can install any package that requires go or go-pie, while the other way around results in a conflict like this:

❯ makepkg -s    
==> Making package: lazygit 0.14.2-1 (Wed 12 Feb 2020 12:19:03 PM -03)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...
:: go-pie and go are in conflict. Remove go? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: go-pie and go are in conflict
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
  -> go-pie
==> ERROR: Could not resolve all dependencies.

frealgagu commented on 2020-02-12 14:18

@efficientbug go-pie is the recommended option, but that doesn't mean that you need to use go-pie instead of go. If you have go installed it should not be necessary to replace it in order to build lazygit. Do you have issues building it using go package?

efficientbug commented on 2020-02-12 01:59

@frealgagu although I understand the guidelines regarding Go software packaging on Arch, I've been having issues installing this since I can't remove Go (something else hard depends on it). Maybe the solution can be found in this Arch Bug Tracker report?

jrwrigh commented on 2020-01-16 20:40

CORRECTION: go clean -modcache should be added to the end of the build() function. This will clear the required directories so that the next incantation of makepkg doesn't have to remove them. Previous (incorrect) solution was from my misunderstanding of makepkg.

OLD: I believe replacing the line rm -rf "${srcdir}/gopath" with go clean -modcache will work correctly as long as $GOPATH is the same as $srcdir. This worked on my installation. See as a reference.

jrwrigh commented on 2020-01-16 19:29

After the latest update, the rm: cannot remove '~/.cache/yay/lazygit/src/pkg/mod/[gopackagename/gopackagefile]:' Permission denied error is still occuring.

Segaja commented on 2020-01-11 16:33

I can confirm that this annoying issue still exists and I would like to the see the package maintainer fix the PKGBUILD file so that this doesn't happen.

jrwrigh commented on 2020-01-08 16:17

I've been consistently getting rm: cannot remove '~/.cache/yay/lazygit/src/pkg/mod/[gopackagename/gopackagefile]:' Permission denied errors when attempting to update. Looking through file permissions there, somehow all the files have no write permissions at all: -r--r--r--. I'm not sure if this is a yay problem or this build, but I've only ever encountered this issue on this aur.