Package Details: age 1.0.0.beta5-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: 13
Popularity: 1.11
First Submitted: 2019-12-28 05:39
Last Updated: 2020-09-21 06:00

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

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?

caleb commented on 2020-08-13 10:16

@eistaa Please report that upstream as a problem with their test suite. We're just running go test ./... there (with our GOPATH set). You can build and install the package with makepkg --nocheck to skip this, but I haven't removed it from the packaging because it looks like it's a legitimate problem with the upstream project, not with our packaging.

eistaa commented on 2020-08-12 12:14

When installing this it fails with:

internal/bech32/bech32_test.go:46:12: conversion from untyped int to 
string yields a string of one rune, not a string of digits (did you mean 

caleb commented on 2020-05-14 19:06

@Tharre My apologies, I appear to have mixed up which machines I was running this package and which were running age-git (which does not provide the keygen). I thought I checked a build of this package but I must have still queried the git package. Thanks for adding me anyway ;-)

Tharre commented on 2020-05-14 09:15

@caleb Yeah I'm aware of that, and will update the package once the new guidelines are finalized.

I've added you as a co-maintainer.

The package will most definitely install age-keygen, not sure why you think it doesn't.

caleb commented on 2020-05-14 08:41

Just a heads up the Go packaging guidelines are changing, and go-pie is going to be dropped entirely. See here for a head start on the new guidelines, probably going in effect this weekend.

I'd be interested in co-maintaining this package as I host a precompiled package version of it and it would be nice to be able to setup reproducible builds without forking the package. Would you consider adding me?

Tharre commented on 2020-05-12 04:37

@vladimiroff The Go packaging guidelines recommend it: "All packages should preferably be built towards go-pie as this enables us to deliver secure binaries."

vladimiroff commented on 2020-05-10 20:17

Why does this require go-pie specifically? age works when compiled with the go package as well. Given that go-pie provides go, I suggest this patch.