Package Details: lazygit-git 0.6.r4.e09f390-1

Git Clone URL: https://aur.archlinux.org/lazygit-git.git (read-only)
Package Base: lazygit-git
Description: A simple terminal UI for git commands
Upstream URL: https://github.com/jesseduffield/lazygit
Licenses: MIT
Conflicts: lazygit
Provides: lazygit
Submitter: fuero
Maintainer: fuero
Last Packager: fuero
Votes: 2
Popularity: 0.000350
First Submitted: 2018-08-07 11:54
Last Updated: 2019-02-22 20:52

Dependencies (3)

Required by (0)

Sources (1)

Pinned Comments

fuero commented on 2018-08-11 17:22

edit: pinned. Comment on what to provide for help added.

What you guys experience is that your build environment is "tainted" by whatever packages exist on your system. I've had similar problems in the past with other packages :-(. With this particular package though, I can build it fine with and without chroot.

That's why pretty much all the distros build their packages in sane build environments.

As it's tough to figure out what plagues your systems, my recommendation stands - stick to chroot builds. I know it's a bother, but sadly that's the only help I can give you.

If it still doesn't work, please install devtools and provide a complete log of your build attempt with

extra-x86_64-build -c 2>&1 | tee build.log

Upload it to a pastebin service and post the link.

Latest Comments

1 2 Next › Last »

dindybutts commented on 2018-08-13 20:50

@fuero Can confirm it works here, Thanks a bunch.

neeks commented on 2018-08-13 04:44

@fuero happy to report it's working with yay on my box as well! Thanks for getting this resolved!

fuero commented on 2018-08-12 22:06

@neeks, dindybutts, Veras: Please try the latest version and report back - It works for me (tm) with yay.

neeks commented on 2018-08-11 20:06

Continuing from the Github issue thread...

I'm using yay like @dindybutts and I get the same errors. makepkg works as expected.

Since this is in the AUR and it's reasonable to expect people to build with AUR helpers, it be nice for this to get resolved some how.

However, I was successful in installing with pikaur, so these issues must lie in how certain AUR helpers are attempting to build.

The next course of action should be to open issues with yay and pacaur

dindybutts commented on 2018-08-11 18:09

I think the issue was something to do with my $GOPATH or $GOROOT not being set so I made a simple makefile where I set both paths and it compiles fine, It still has to invoke go get -d ./.. in the makefile though which I think is possibly unnecessary since go build should automagically get the dependencies(?) but this works for me.

Many thanks for the help @fuero

fuero commented on 2018-08-11 17:22

edit: pinned. Comment on what to provide for help added.

What you guys experience is that your build environment is "tainted" by whatever packages exist on your system. I've had similar problems in the past with other packages :-(. With this particular package though, I can build it fine with and without chroot.

That's why pretty much all the distros build their packages in sane build environments.

As it's tough to figure out what plagues your systems, my recommendation stands - stick to chroot builds. I know it's a bother, but sadly that's the only help I can give you.

If it still doesn't work, please install devtools and provide a complete log of your build attempt with

extra-x86_64-build -c 2>&1 | tee build.log

Upload it to a pastebin service and post the link.

dindybutts commented on 2018-08-11 17:06

@fuero

Here's the log you asked for: https://pastebin.com/MzTVaNyN

It's strange, it seems to build fine with the command you provided and with a simple makepgk -si but fails while using both my aur helpers, yay and pacaur

fuero commented on 2018-08-11 11:39

@dindybutts

the deps are all vendored by the author, so there's no need to download anything.

Please provide a complete log of your build attempt with

extra-x86_64-build -c 2>&1 | tee build.log

Upload it to a pastebin service and post the link.

dindybutts commented on 2018-08-11 09:44

Hi @fuero

I had the same issue as @Veras (even with devtools installed), which was resolved by running go get 6 times on various dependency urls.

Here's an image of the error: https://i.imgur.com/Fc26fr7.png

Or a pastebin if you'd prefer: https://pastebin.com/KtczQaBW

The dependency urls I needed to build were:

github.com/davecgh/go-spew/spew

github.com/fatih/color

github.com/golang-collections/collections/stack

github.com/jesseduffield/gocui

github.com/tcnksm/go-gitconfig

gopkg.in/src-d/go-git.v4

I could reproduce this on my machine by deleting the build files from my cache and building fresh.

My solution would be to pull these dependencies in during the build but since I'm not super familiar with go I'm not entirely sure how to do it.

fuero commented on 2018-08-10 17:54

I recommend building it with extra-x86_64-build (from devtools) to rule out any peculiarities from your box. Please report back if you can reproduce your errors with this.