Search Criteria
Package Details: elvish 0.14.1-1
Git Clone URL: | https://aur.archlinux.org/elvish.git (read-only, click to copy) |
---|---|
Package Base: | elvish |
Description: | A friendly and expressive Unix shell. |
Upstream URL: | https://github.com/elves/elvish |
Keywords: | shell |
Licenses: | |
Provides: | |
Submitter: | hexchain |
Maintainer: | hexchain (xiaq, farseerfc) |
Last Packager: | hexchain |
Votes: | 16 |
Popularity: | 0.107195 |
First Submitted: | 2016-03-30 03:44 |
Last Updated: | 2020-08-16 15:38 |
Dependencies (4)
- glibc (glibc-git)
- git (git-git) (make)
- go (go-tip, go-git, go-go2go-git, gcc-go-git, gcc-go) (make)
- pandoc (pandoc-bin, pandoc-sile-git) (make)
Latest Comments
1 2 Next › Last »
xiaq commented on 2020-04-03 22:31
@vendion I have recently fixed that unit test, you should see the problem go away from the next release: https://github.com/elves/elvish/commit/df6300b1ad7f2401b22247d9962ef518f3d45a6b
vendion commented on 2020-03-24 12:40
@hexchain Oddly it built fine for me after a system reboot.
hexchain commented on 2020-03-23 19:38
@vendion: That's strange, I cannot reproduce this either on my own machine or the CI. Could you try
extra-x86_64-build
?vendion commented on 2020-03-23 12:06
Using the lasted PKGBUILD (0.13.1-2) the unit tests do not pass using Go 1.14.1-1
hexchain commented on 2020-03-22 18:58
@nuc: Hi, you need to manually remove the cache for now, either by using
sudo
or do achmod +rw -R
on the directory. I've pushed an update to make the golang modcache writable so that this kind of manual work is no longer needed in the future. Please wait for 0.13.1-2.nuc commented on 2020-03-22 08:17
Cannot build the package. Getting errors like
j605 commented on 2018-11-05 09:18
tags are now named as
v$pkgver
. Can you please update it.hexchain commented on 2017-07-12 06:59
@cjwen: Does 0.9-2 solve your problem with pacaur?
cjwen commented on 2017-07-12 06:50
How about syncing the syntax of PKGBUILD with elvish-git? This PKGBUILD will make pacaur fail to install.
fusion809 commented on 2016-09-15 15:55
Nvm re-building resolved this issue.