Package Details: mongodb-tools 1:100.9.4-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: Apache
Submitter: felixonmars
Maintainer: Scimmia
Last Packager: Scimmia
Votes: 8
Popularity: 1.06
First Submitted: 2019-02-14 16:05 (UTC)
Last Updated: 2023-12-08 00:03 (UTC)

Dependencies (3)

Required by (12)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

PolarianDev commented on 2023-04-19 09:37 (UTC)

I have packaged mongodb-tools to my unofficial arch linux repository, you can find more information about this repository on the arch wiki, and the git repository for it (which also contains a list of packages):

Once the repository is added you can simply install mongodb-tools using pacman:

pacman -Syu mongodb-tools

And update it like usual:

pacman -Syu

Scimmia commented on 2022-12-04 13:40 (UTC)

Works for me, of course. Make sure you're building the package in a clean chroot.

sarutabiko commented on 2022-12-04 11:47 (UTC)

Doesn't work. Gave Segmentation fault on every command, while building from the GitHub page worked.

SpineEyE commented on 2022-03-16 15:23 (UTC)

By the way, I accidentally specified the wrong version when I flagged this out of date. The lastet version is: 100.5.2. They jumped a few versions... https://docs.mongodb.com/database-tools/#versioning

SpineEyE commented on 2022-03-16 13:43 (UTC)

Hey there. The binary doesn't have a version:

$ /usr/bin/mongodump --version
mongodump version: built-without-version-string
git version: build-without-git-commit

Maybe you can build with build.go to get the version string?

ayr-ton commented on 2021-12-29 23:00 (UTC)

@mirsella: Fixed

mirsella commented on 2021-12-21 16:37 (UTC)

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 (UTC) (edited on 2021-10-10 17:03 (UTC) by Allen_Hong)

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

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