Arch Linux User Repository

go get is no longer supported.

==> Starting build()... Now getting go-sqlite3... go: go.mod file not found in current directory or any parent directory. 'go get' is no longer supported outside a module. To build and install a command, use 'go install' with a version, like 'go install example.com/cmd@latest' For more information, see https://golang.org/doc/go-get-install-deprecation or run 'go help get' or 'go help install'. ==> ERROR: A failure occurred in build(). Aborting... -> error making: tmsu

I don't know much about go build system, could you please bump the issue/PR upstream so they merge that fix? It would be a better solution, but in the end I could just patch it here.

the installation was dying on me with no required module provides package github.com/oniony/TMSU: go.mod file not found in current directory or any parent directory until i ran go env -w GO111MODULE=auto as per https://github.com/oniony/TMSU/issues/224

The PKGBUILD is missing one dependency and could not be installed. I fixed it by adding "go get golang.org/x/crypto/blake2b" inside the build() function at line 31.

go should be in makedepends, and not in depends. go programs are compiled, not interpreted. The system it is being run on doesn't need to have go installed.

Everyone has bash, and also namcap is not 100% right all the time. TMSU is written in Go, so it's a dependency. Fuse is required too, and you can see in the PKGBUILD that Go bindings for it are being downloaded. Same goes with sqlite. Thanks for trying to help tho.

FYI, noticed these warnings at the end of building in a clean chroot.

Checking PKGBUILD Checking tmsu-0.7.0-1-x86_64.pkg.tar.xz tmsu E: Dependency bash detected and not included (programs ['sh', 'bash'] needed in scripts ['usr/bin/tmsu-fs-mv', 'usr/bin/tmsu-fs-merge', 'usr/bin/mount.tmsu', 'usr/bin/tmsu-fs-rm']) tmsu W: Dependency included and not needed ('go') tmsu W: Dependency included and not needed ('fuse') tmsu W: Dependency included and not needed ('sqlite')

Modifying the PATH variable is not the correct solution here. The issue is a poorly written Makefile. Neither of the tests have dependencies on the final compiled output, so running with jobs > 1 causes the tests to run in parallel with the compilation. Additionally tests shouldn't be in the build command in the first place. That's what check is for. The user should have the option to skip failing tests if the outputs are generated properly. So with all that being said I think the correct solution is to modify the PKGBUILD like ``` 28c28,33 < make --- > make dist > } > > check() { > cd "$srcdir/TMSU-$pkgver" > make test ```

Yep. CheezenOne is right. Just run make with the modified PATH env variable. Can the maintainer edit the PKGBUILD please?

I could get the PKGBUILG compile the package after changing the make command to: ``` cd "$srcdir/TMSU-$pkgver" PATH="$PATH:$(pwd)/bin" make -j1 ``` My build was failing because the path to the `tmsu` executable was not known when the tests were executed.