Package Details: mongodb-tools 1:100.10.0-1

Git Clone URL: https://aur.archlinux.org/mongodb-tools.git (read-only, click to copy)
Package Base: mongodb-tools
Description: Import, export, and diagnostic tools for MongoDB
Upstream URL: https://github.com/mongodb/mongo-tools
Licenses: MIT, ISC, Apache-2.0, BSD-3-Clause, BSD-2-Clause, MPL-2.0
Submitter: felixonmars
Maintainer: Scimmia
Last Packager: Scimmia
Votes: 8
Popularity: 0.011067
First Submitted: 2019-02-14 16:05 (UTC)
Last Updated: 2024-08-02 12:02 (UTC)

Required by (13)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4

Linux2Brain commented on 2019-02-28 08:15 (UTC) (edited on 2019-02-28 08:17 (UTC) by Linux2Brain)

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 (UTC)

@Helloagain, if you retry, it should succeed now. It did need a change in the PKGBUILD. It wasn'a bug in yay, but just that yay runs the PKGBUILD functions separately, so environment variables set in one aren't seen in another. I made the PKGBUILD change, because as yay points out, makepkg supports running the functions separately.

Helloagain commented on 2019-02-27 23:06 (UTC)

Thanks @jamespharvey20 for filing a bug report!

Helloagain commented on 2019-02-27 23:05 (UTC)

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 (UTC)

@Helloagain, this is a bug with yay. I filed a bugreport here: https://github.com/Jguer/yay/issues/896

I recommend using makepkg or extra-x86_64-build which is part of package devtools. They build this just fine.

jamespharvey20 commented on 2019-02-24 10:14 (UTC)

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 to go-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 to go-pie in 3.4.9-1, around Oct 18 2017. This roughly corresponds to when go-pie became a split package from go. 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 require go-pie.

Is this causing a problem, or just wondering?

illuser commented on 2019-02-23 19:08 (UTC)

Is there a reason to have the go requirement explicitly set to go-pie?

« First ‹ Previous 1 2 3 4