Package Details: age 1.0.0.beta7-1

Git Clone URL: (read-only, click to copy)
Package Base: age
Description: A simple, modern and secure file encryption tool
Upstream URL:
Licenses: BSD
Submitter: Tharre
Maintainer: Tharre (caleb)
Last Packager: caleb
Votes: 14
Popularity: 1.18
First Submitted: 2019-12-28 05:39
Last Updated: 2021-02-08 19:25

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

nilsw commented on 2021-02-11 11:24

@ansemjo I didn't check. I compared this project to the yay Makefile and didn't see the line there. And I wouldn't want anything to be readonly, so I just remove the line, too.

ansemjo commented on 2021-02-10 10:18

afaik you can keep -mod=readonly as that should only apply to modifications of the go.mod file itself?

nilsw commented on 2021-02-10 10:15

I had to chmod and rm the cache dir for every update I have ever done. Looking at other Go projects I realized that the go mod download line is not needed, go build will download the modules just fine, and will keep the files read-write. If I remove the entire prepare() function, and the -mod=readonly line, it works perfectly.

ansemjo commented on 2021-02-10 08:19

I don't think it's due to bad builds .. but rather simply any previous build? I've noticed a few times that Go tends to set readonly permissions that won't let you simply rm -rf a package cache directory -- specifically dr-x------.

Running GOPATH="$PWD/src" go clean -modcache helped but then I got the same errors during clean-up. That didn't fail the build at least.

It appears that the initial go mod download already leaves the cache read-only.

caleb commented on 2021-02-10 05:30

@nilsw That's probably the result of a bad old build. You should clear your yay cache of everything age related to get rid of the bad file(s).

nilsw commented on 2021-02-09 14:42

On updates and reinstalls I always get permission errors in my AUR helper cache dir, like rm: cannot remove '/home/nils/.cache/yay/age/src/pkg/mod/': Permission denied. Apparently the modcache permission flag is not correct.

caleb commented on 2020-12-19 12:18

@hardfalcon I understand that, but unfortunately the very first version that was posted was already screwed up, so there is really nothing to be done for it now. We might as well wait to add the epoch until an actual 1.0.0 gets cut, and if we're lucky upstream will have a release glitch and need to fire off 1.0.1 fast enough that we can avoid saddling ourselves with an epoch for life.

hardfalcon commented on 2020-11-20 05:01

The version numbering that is currently used for this package will break when the final version 1.0 (without a suffix like "beta5") is released.

The proper way to do this would be to remove the dot in front of the "beta5" suffix, as described man 8 vercmp:

Additionally, a line "epoch=1" will need to be added to the PKGBUILD to allow for overcoming the issue caused by the current numbering scheme with the erronous dot in front of the "beta5" suffix.

eldios commented on 2020-10-10 12:04

it was apparently fixed in July too... so the last comments should not be a problem anymore:

07c72f3b (Shimmy Xu        2020-09-07 09:07:10 -0500 46)                {"spl" + string(rune(127)) + "t1checkupstagehandshakeupstreamerranterredcaperred2y9e3w", false},

eldios commented on 2020-10-10 12:01

[eldios@dev age]$ go test ./...
ok  0.460s
ok   0.017s
ok    0.020s
ok  0.002s
?   [no test files]
ok  0.009s
?  [no test files]
ok  0.020s

This is working for me. It's also working when installing from AUR.

Which version of Go are you guys using?