Package Details: amass 3.8.2-1

Git Clone URL: (read-only, click to copy)
Package Base: amass
Description: In-depth subdomain enumeration written in Go
Upstream URL:
Licenses: Apache
Submitter: architekton
Maintainer: architekton
Last Packager: architekton
Votes: 3
Popularity: 0.59
First Submitted: 2018-09-10 11:30
Last Updated: 2020-07-30 07:50

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

architekton commented on 2020-03-21 03:32

@lawnmower_man yep, updated.

lawnmower_man commented on 2020-03-20 20:18

Is it fixed in 3.5.1 released 3 days ago?

lawnmower_man commented on 2020-03-05 12:59

Thanks for your fast reply

architekton commented on 2020-03-05 10:27

@lawnmower_man The %w verb isn't allowed in format strings that don't wrap errors anymore such as Printf or Sprintf in go 1.13+. It simply doesn't make sense anymore see: which runs go1.13.7 to see why. This is an upstream problem, they should replace %w with %v. If they don't soon I'll patch it and submit a PR. As a workaround you could downgrade to go1.12.

lawnmower_man commented on 2020-03-04 21:26

I get this error when trying to install on artix arch - any ideas? TY.

==> Extracting sources...
 -> Extracting Amass-3.4.3.tar.gz with bsdtar
==> Starting build()...
==> Starting check()...
ok   (cached) [no tests to run]
ok     (cached)
ok        (cached)
? [no test files]
?  [no test files]
ok      (cached)
?      [no test files]
?        [no test files]
ok (cached)
?      [no test files]
? [no test files]
ok        (cached)
ok   (cached)
ok       (cached)
?      [no test files]
ok (cached)
ok      (cached)
ok     (cached)
ok     (cached)
services/whoisxml.go:108:34: Sprintf call has error-wrapping directive %w
FAIL [build failed]
ok     (cached)
?   [no test files]
ok      (cached)
==> ERROR: A failure occurred in check().
:: Unable to build amass - makepkg exited with code: 4`

wknapik commented on 2019-12-26 16:30

@architekton thanks, now we can install amass without removing go.

The problem was not about the dependency being compile-time, or run-time. The problem was that the go and go-pie packages cannot co-exist on the same system. So anyone with go installed was forced to remove it in favor of go-pie, to build amass. Now, with the dependency on go-pie removed, that's no longer the case.

architekton commented on 2019-12-22 00:04

@wknapik Go or go-pie are only make dependencies and can be removed after building, however I changed it back to go for non-conflict convenience.

wknapik commented on 2019-12-20 15:42

Please remove the dependency on go-pie.

wknapik commented on 2019-12-10 17:34

% pacaur -Sii amass|grep depends
Makedepends    : go-pie  git
% pacaur -S amass
:: Package amass not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...
:: go-pie and go are in conflict (go). Remove go? [y/N] N
:: unresolvable package conflicts detected
:: failed to prepare transaction (conflicting dependencies)
:: go-pie and go are in conflict
% echo $?

architekton commented on 2019-12-05 00:43

@wknapik - It isn't a hard dependency, just used during the build process, see: