FS#62330 - rocksdb-release-5.18.3-1 has a hidden dependency on jemalloc

Attached to Project: Arch Linux
Opened by Ștefan Talpalaru (stefantalpalaru) - Saturday, 13 April 2019, 14:23 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 13 April 2019, 16:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The upstream Makefile used by this AUR recipe includes "make_config.mk": https://github.com/facebook/rocksdb/blob/v5.18.3/Makefile#L197

which is produced a couple of lines higher by "build_tools/build_detect_platform" which does library auto-detection by default: https://github.com/facebook/rocksdb/blob/v5.18.3/build_tools/build_detect_platform#L362

Jemalloc ends up detected and enabled on the builder's system, but it's not declared as a dependency in AUR, leading to a runtime error on systems without Jemalloc installed.

iamazat, the maintainer of this package, could save some time by looking at a recent ebuild in this Gentoo overlay: https://github.com/Jannis234/jm-overlay/tree/master/dev-db/rocksdb
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 13 April 2019, 16:32 GMT
Reason for closing:  None
Additional comments about closing:  AUR package are unsupported
Comment by loqs (loqs) - Saturday, 13 April 2019, 14:48 GMT Comment by Ștefan Talpalaru (stefantalpalaru) - Saturday, 13 April 2019, 15:20 GMT
Please point out where on this page does it say that the package is unsupported: https://aur.archlinux.org/packages/rocksdb-release/
Comment by loqs (loqs) - Saturday, 13 April 2019, 15:53 GMT
See the last line of Projects section I linked to which is the same page as linked to at the top of every bug report:
There is no place for reporting problems with packages in unsupported. The AUR provides a way to add comments to a package in unsupported. You should use this to report bugs to the package maintainer.
See also [1] which is linked to from [2] and you are expected to have read before using AUR.
Note: The AUR is unsupported, so any packages you install are your responsibility to update, not pacman's. If packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries.
Why would it need to say on every AUR package page that it is not supported any more than it should repeat you are expected to have base-devel installed, know how to use makepkg and manage gpg signatures.
[1] https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages
[2] https://aur.archlinux.org/

Loading...