Package Details: mongodb-tools 1:4.2.18_rc0-1

Git Clone URL: https://aur.archlinux.org/mongodb-tools.git (read-only, click to copy)
Package Base: mongodb-tools
Description: The MongoDB tools provide import, export, and diagnostic capabilities.
Upstream URL: https://github.com/mongodb/mongo-tools
Licenses: Apache
Submitter: felixonmars
Maintainer: ayr-ton (chrbayer)
Last Packager: ayr-ton
Votes: 5
Popularity: 0.003210
First Submitted: 2019-02-14 16:05
Last Updated: 2021-12-29 22:59

Dependencies (2)

Required by (11)

Sources (1)

Latest Comments

1 2 Next › Last »

ayr-ton commented on 2021-12-29 23:00

@mirsella: Fixed

mirsella commented on 2021-12-21 16:37

how can we merge the new working pkgbuild into this package in the AUR repo ? seems like the maintainer is not active anymore

Allen_Hong commented on 2021-10-10 17:02

@rafaelff, Thank you for noting, you saved me a lot of time! Here are two adjustments.

  • [ -n $GOPATH ] --> [ -n "$GOPATH" ]
  • export $GOPATH --> export GOPATH

rafaelff commented on 2021-07-17 21:12

Packager, I have some notes on the PKGBUILD.

LT;DR:

Here is a suggestion of PKGBUILD which works for me, and is updated to 4.2.15:
http://ix.io/3tiS

  • set_goenv.sh is meant to declare some functions to be used on go build command line, as can be seen in build.sh in the source directory. Since this PKGBUILD is using none of the declared functions, running set_goenv.sh. shouldn't be required.

  • Reading the Go packaging guidelines in Archwiki, one can see the recommendation to export some variables. One particular case is PIE attribute to LDFLAGS: namcap complains on the lack of PIE in files contained in the built package, which is solved by exporting the variables mentioned in the wiki page. NOTE: I'm not sure which one are necessary. See below a PKGBUILD suggestion that works for me.

  • If $GOPATH is empty, which seems to happen when building in a clean chroot, build with failed with message missing GOPATH due to export GOPATH="$GOPATH:$srcdir/build". I suggest using a different approach to check whether is GOPATH is empty to set $srcdir/build directly or just to append. For instance:

  [ -n $GOPATH ] && GOPATH="$GOPATH:$srcdir/build" || GOPATH="$srcdir/build"
  export $GOPATH

oriba commented on 2021-03-25 15:57

Building the tools from the github-clone works neat. So the problem is located in this AUR-package.

oriba commented on 2021-03-25 15:49

Same problem as qlem has, I also have. go-pie does not exist. It's now go-2. Package is outdated.

qlem commented on 2021-03-15 12:46

Hello, I have module issues while build:

Building bsondump... bsondump/main/bsondump.go:13:2: no required module provides package github.com/mongodb/mongo-tools-common/log: go.mod file not found in current directory or any parent directory; see 'go help modules' bsondump/main/bsondump.go:14:2: no required module provides package github.com/mongodb/mongo-tools-common/signals: go.mod file not found in current directory or any parent directory; see 'go help modules' bsondump/main/bsondump.go:15:2: no required module provides package github.com/mongodb/mongo-tools-common/util: go.mod file not found in current directory or any parent directory; see 'go help modules' bsondump/main/bsondump.go:16:2: no required module provides package github.com/mongodb/mongo-tools/bsondump: go.mod file not found in current directory or any parent directory; see 'go help modules'

Edit: for better error formatting: https://pastebin.com/2iz0SGFC

Any help is welcome.

jamespharvey20 commented on 2019-03-05 22:57

@jghodd, thanks for your bugreport. Arch just added go 2:1.12 5 days ago, which will fail on code using _Ctype_struct_ instead of C.struct_, as you mentioned. Just pushed 4.0.6-2, which fixes upstream's code. Upstream bugreport: https://jira.mongodb.org/browse/TOOLS-2233

jghodd commented on 2019-03-05 19:22

@jamespharvey20, am getting the following error while building:

vendor/github.com/google/gopacket/pcap/pcap.go:173:7: identifier "_Ctype_struct_bpf_program" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:384:13: identifier "_Ctype_struct_pcap_stat" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:421:49: identifier "_Ctype_struct_bpf_program" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:444:10: identifier "_Ctype_struct_bpf_program" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:462:41: identifier "_Ctype_struct_bpf_insn" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:538:66: identifier "_Ctype_struct_bpf_program" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:551:19: identifier "_Ctype_struct_bpf_insn" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:659:34: identifier "_Ctype_struct_pcap_addr" may conflict with identifiers generated by cgo vendor/github.com/google/gopacket/pcap/pcap.go:662:56: identifier "_Ctype_struct_pcap_addr" may conflict with identifiers generated by cgo ==> ERROR: A failure occurred in build(). Aborting...

Any ideas?

Edit: looks like the problem is here - https://github.com/andelf/go-curl/issues/66

Any instances of "_Ctype_struct" need to be replaced with "C.struct". I modified a tmp version of the code and the build goes through just fine.

jamespharvey20 commented on 2019-03-01 04:17

@Linux2Brain, can you try again? An update I pushed a few hours before your comment fixed the same problem Helloagain was having, which was happening because yay compiles a PKGBUILD by running its functions separately. The latest update should take care of this.