Search Criteria
Package Details: lldap-git 0.5.0.r101.g3d8aafa-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/lldap-git.git (read-only, click to copy) |
---|---|
Package Base: | lldap-git |
Description: | Light LDAP Daemon |
Upstream URL: | https://github.com/lldap/lldap |
Licenses: | GPL3 |
Conflicts: | lldap |
Provides: | lldap |
Submitter: | lapinot |
Maintainer: | lapinot |
Last Packager: | lapinot |
Votes: | 1 |
Popularity: | 0.000145 |
First Submitted: | 2023-02-25 01:02 (UTC) |
Last Updated: | 2024-02-28 16:11 (UTC) |
Dependencies (10)
- gcc-libs (gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-gitAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR)
- cargo (rust-nightly-binAUR, cargo-gitAUR, rustup-gitAUR, rust, rustup) (make)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-c-aresAUR, curl-gitAUR) (make)
- findutils (findutils-selinuxAUR, findutils-gitAUR, busybox-coreutilsAUR) (make)
- git (git-gitAUR) (make)
- gzip (dxcompress-gitAUR, dxcompressAUR, gzip-gitAUR, busybox-coreutilsAUR) (make)
- rust (rust-nightlyAUR, rust-nightly-binAUR, rust-gitAUR, rustup-gitAUR, rustup) (make)
- rust-wasm (rustup-gitAUR, rustup) (make)
- wasm-pack (wasm-pack-gitAUR) (make)
Latest Comments
1 2 Next › Last »
lapinot commented on 2024-02-29 12:09 (UTC) (edited on 2024-02-29 12:15 (UTC) by lapinot)
Zepman: Well then i'm puzzled as to:
Two explanations: either there is a really weird bug somewhere in rustc, or somehow the compilation process hit a resource limit and got killed by a system watchdog. In either case, i cannot see how this kind of error (someone sending SIGKILL) could be originating from the package definition, it is neither a dependency missing nor a (normal) compiler error. Supporting second explanation is the fact that i reproduced the error in low memory conditions and built without error on fresh install with high memory and swap enabled.
As to why your edits fixed the problem, perhaps if you restarted the build without doing a cleanbuild, the resource usage got lower since some dependencies were already compiled.
Note that it might also be the case that rustc/cargo uses /tmp or some other tmpfs quite enthusiastically which could add to the memory pressure. The debian farm reports 10GiB max disk space, i don't know how much of this was on /tmp.
Perhaps i'll pin a comment to check available ram and swap device if this issue pops up again. Until then i don't think i have more input to give.
Zepman commented on 2024-02-29 11:40 (UTC) (edited on 2024-02-29 11:42 (UTC) by Zepman)
@lapinot
Incorrect. My building machine (the one running stock Arch Linux system with
base-devel
installed) has 16 GB of (mostly free, since stock) memory.Furthermore, building with your recipe at the time failed. Building with my recipe at the time did not. I did not try your latest recipe.
I know building LLDAP is taxing, which is why I created lldap-bin for the stable version of LLDAP. For building I use a beefy enough configuration of which I know that it works.
lapinot commented on 2024-02-28 13:43 (UTC) (edited on 2024-02-28 13:46 (UTC) by lapinot)
Zepman: Confirming your error is caused by not enough memory available. See https://github.com/lldap/lldap/issues/660. It needs ~5GiB memory to complete.
Zepman commented on 2024-02-28 11:50 (UTC) (edited on 2024-02-28 12:39 (UTC) by Zepman)
@lapinot
You asked two questions:
My answer:
You can infer that this means "no".
Your second question:
My answer:
You can infer this means "no", since a stock Arch Linux system with
base-devel
installed does not have Rust installed.Please do not appear as if you are insinuating that others don't read your messages when claiming that others insinuate that you do not read their messages. Your questions were answered, and your claim was unnecessary.
I am being factual. The emphasis was on the word very to clarify that I really used a stock Arch Linux system with only minimal tooling (
base-devel
and yes,sudo
...) to attempt an install. There are too many bug reports that are based on AUR helpers, which are not supported and make debugging way more complex.My PKGBUILD diff (based on the PKGBUILD of lldap):
The hash of the patch file config-template.patch was changed because I created a new patch that is compatible with the latest development version:
lapinot commented on 2024-02-28 10:39 (UTC) (edited on 2024-02-28 10:56 (UTC) by lapinot)
Zepman: Please lets keep things factual, don't insinuate i don't really read your messages and don't explain to me what basic makepkg options do. Works for me and apparently also a couple other, so you're not entitled to me debugging your issue. I understand building in a fresh install is important, as i said "I will try to build in a clean VM to see if it works better". This will be fixed very soon. I asked you two questions you answered neither (if this could be a ram issue). Also
rustup update
will never be needed if rustup is not present before building, i said it might help with a stalled toolchain.In case of a fresh install, the
lldap
package indeed doesn't use rustup but the arch-provided toolchains. Perhaps i forgot a dependency but afaiu x86-64, wasm and wasm-bindgen get installed dynamically. I previously thought that because of the need for the wasm target it wasn't possible to make the package agnostic to rustup vs arch-provided, but i might be wrong. I will test and switch if it doesn't pull anything when rustup is already installed.Yes, i guess you mostly took their makedepends, but indeed i'd be happy to see a diff.
Zepman commented on 2024-02-28 09:10 (UTC) (edited on 2024-02-28 09:45 (UTC) by Zepman)
@lapinot
As I wrote before:
You must take this very literally. I did not use a chroot environment. I also did not install or configure Rust as a build dependency. The package should do this if needed. Any AUR recipe should be able to build a package when
base-devel
is installed and when a (non-root, but with sudo rights) user runsmakepkg -sr
, since-s
should take care of any build dependencies (sudo rights are only used for that and for removing packages using-r
).So no, I will not run
rustup update
before building. Such preparations should not be necessary to build any AUR recipe. Also, for diagnosing it would not do anything since rustup is not installed before I runmakepkg -sr
.For now I created a workaround based on package lldap, which seems to have a more robust build process. If you'd like, I can share that PKGBUILD with you.
lapinot commented on 2024-02-27 23:10 (UTC)
Also on my todolist: review the default config. At first it came from example config from the repo, i edited some with standard values. Maybe i should just put whatever the default value actually is for each.
lapinot commented on 2024-02-27 22:52 (UTC) (edited on 2024-02-27 22:53 (UTC) by lapinot)
rabidpug: Thanks, indeed. Will push this fix in a minute.
Zepman: Sorry for my email not being setup correctly, i just saw your orphan request on the mailing list. I'm in the process of switching my "online/dev" email and hadn't thought about me now being a maintainer of something. I will make it work soon, in the meantime i'll follow closer this comment thread.
About the compilation: the important part of your error is
(signal: 9, SIGKILL: kill)
, which most likely means the OS killed the build process for some reason. Actually i tested building in a fresh arch chroot (pacstrap + arch-chroot) and got the exact same error. Did you also try to build in a chroot? It is quite memory intensive to build and i don't think arch-chroot is particularly robust with tmpfiles / memory usage.I will try to build in a clean VM to see if it works better. In the meantime, outside of any chroot or VM: have you tried doing
rustup update
before building? The PKGBUILD will not mess with your rustup installation, so if it's already installed it will use whatever version there is, perhaps it is a bit stalled.I just built the package on my main system, running
rustup update
fixed any issue.Zepman commented on 2024-02-12 11:09 (UTC) (edited on 2024-02-12 11:47 (UTC) by Zepman)
This package fails to build. Tested on a stock Arch Linux system with
base-devel
installed, without the use of an AUR helper.rabidpug commented on 2024-01-06 03:29 (UTC)
Should this package have
backup=('etc/lldap.toml')
to preserve the existing config file on update?1 2 Next › Last »