Search Criteria
Package Details: mongodb-tools 4.2.8-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: | |
Submitter: | felixonmars |
Maintainer: | jamespharvey20 (chrbayer) |
Last Packager: | chrbayer |
Votes: | 4 |
Popularity: | 0.137411 |
First Submitted: | 2019-02-14 16:05 |
Last Updated: | 2020-08-20 22:43 |
Dependencies (2)
- libpcap (libpcap-git)
- go-pie (go) (make)
Required by (8)
- holland-mongodump
- mongodb (optional)
- mongodb-3.4 (optional)
- mongodb-bin (optional)
- mongodb-bin-3.2 (optional)
- mongodb-bin-3.6 (optional)
- mongodb-bin-4.0 (optional)
- mongodb-shell-bin (optional)
Latest Comments
1 2 Next › Last »
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 ofC.struct_
, as you mentioned. Just pushed 4.0.6-2, which fixes upstream's code. Upstream bugreport: https://jira.mongodb.org/browse/TOOLS-2233jghodd 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.Helloagain commented on 2019-02-28 09:25
@jamespharvey20: Yes I can install it now with yay.
Thank you for your efforts, I appreciate it!
Linux2Brain commented on 2019-02-28 08:15
Hi, I can't install version 4.0.6-1 due to missing utils, this seems to be a circular problem: (see @Helloagain)
jamespharvey20 commented on 2019-02-27 23:48
@Helloagain, if you retry, it should succeed now. It did need a change in the PKGBUILD. It wasn'a bug in
yay
, but just thatyay
runs the PKGBUILD functions separately, so environment variables set in one aren't seen in another. I made the PKGBUILD change, because asyay
points out,makepkg
supports running the functions separately.Helloagain commented on 2019-02-27 23:06
Thanks @jamespharvey20 for filing a bug report!
Helloagain commented on 2019-02-27 23:05
D'oh I deleted my post accidentally:
I get the following error (upgrading mongodb-tools from 4.0.5-2 to 4.0.6-1 with yay):
Building bsondump... bsondump/main/bsondump.go:11:2: cannot find package "github.com/mongodb/mongo-tools/bsondump" in any of: /usr/lib/go/src/github.com/mongodb/mongo-tools/bsondump (from $GOROOT) /home/local_user/go/src/github.com/mongodb/mongo-tools/bsondump (from $GOPATH) bsondump/main/bsondump.go:12:2: cannot find package "github.com/mongodb/mongo-tools/common/db" in any of: /usr/lib/go/src/github.com/mongodb/mongo-tools/common/db (from $GOROOT) /home/local_user/go/src/github.com/mongodb/mongo-tools/common/db (from $GOPATH) bsondump/main/bsondump.go:13:2: cannot find package "github.com/mongodb/mongo-tools/common/log" in any of: /usr/lib/go/src/github.com/mongodb/mongo-tools/common/log (from $GOROOT) /home/local_user/go/src/github.com/mongodb/mongo-tools/common/log (from $GOPATH) bsondump/main/bsondump.go:14:2: cannot find package "github.com/mongodb/mongo-tools/common/options" in any of: /usr/lib/go/src/github.com/mongodb/mongo-tools/common/options (from $GOROOT) /home/local_user/go/src/github.com/mongodb/mongo-tools/common/options (from $GOPATH) bsondump/main/bsondump.go:15:2: cannot find package "github.com/mongodb/mongo-tools/common/signals" in any of: /usr/lib/go/src/github.com/mongodb/mongo-tools/common/signals (from $GOROOT) /home/local_user/go/src/github.com/mongodb/mongo-tools/common/signals (from $GOPATH) bsondump/main/bsondump.go:16:2: cannot find package "github.com/mongodb/mongo-tools/common/util" in any of: /usr/lib/go/src/github.com/mongodb/mongo-tools/common/util (from $GOROOT) /home/local_user/go/src/github.com/mongodb/mongo-tools/common/util (from $GOPATH) ==> ERROR: A failure occurred in build(). Aborting... Error making: mongodb-tools
*Edit: For better formatting: https://pastebin.com/pry6acRJ
jamespharvey20 commented on 2019-02-27 22:27
@Helloagain, this is a bug with
yay
. I filed a bugreport here: https://github.com/Jguer/yay/issues/896I recommend using
makepkg
orextra-x86_64-build
which is part of package devtools. They build this just fine.jamespharvey20 commented on 2019-02-24 10:14
I believe it's just the general preference for PIE (i.e. better security.)
Ultimately, it's there now because it was changed from
go
togo-pie
in 3.4.9-1. My first change to this package was a few days ago. Before then, it was part of the community repo. My only changes were upgrading from 4.0.5 to 4.0.6, and making inconsequential changes to the PKGBUILD.In the community repo history, I can see it was changed from
go
togo-pie
in 3.4.9-1, around Oct 18 2017. This roughly corresponds to whengo-pie
became a split package fromgo
. This is also roughly around when Arch made the change to making PIE default.When I look at
go
, I see 12 official repo packages require it, but 118 requirego-pie
.Is this causing a problem, or just wondering?