| Git Clone URL: | https://aur.archlinux.org/ceph.git (read-only, click to copy) |
|---|---|
| Package Base: | ceph |
| Description: | Ceph Storage common libraries and dependencies |
| Upstream URL: | https://ceph.com/ |
| Licenses: | GPL-2.0-or-later OR LGPL-2.1-or-later OR LGPL-3.0-or-later |
| Provides: | libceph-common.so, libceph_ebd_vdo.so |
| Submitter: | foxxx0 |
| Maintainer: | pbazaah |
| Last Packager: | pbazaah |
| Votes: | 7 |
| Popularity: | 0.85 |
| First Submitted: | 2022-08-08 09:09 (UTC) |
| Last Updated: | 2024-09-17 14:56 (UTC) |
@AsGreyWolf
Could you provide more detail? Preferably a minimal reproducible case, but I'll take the logs. Open issues here: https://github.com/bazaah/aur-ceph/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc
Admittedly, I don't think I've ever used a ceph fuse client, but I do use the a minimal dashboard, and haven't encountered issues myself.
I've got non working dashboard (PyO3 modules may only be initialized once per interpreter process) and coredumping (some kind of assert) fuse client with this update.
I was unable to reproduce this in a clean chroot, 17.2.6-2 still builds successfully
@mostlyharmless
I'll take a look after $dayJob
I get a build failure because of a dependency on markupsafe, error is ImportError: cannot import name 'soft_unicode' from 'markupsafe' around 28% build. Turns out soft_unicode was deprecated in markupdafe 2.1.0, we are now at version 2.1.3. See https://bobbyhadz.com/blog/python-importerror-cannot-import-name-soft-unicode-from-markupsafe. Not really an AUR problem perhaps, but upstream? I do not want to break python by forcing markupsafe 2.0.1, nor do I want to remove ceph, as there are qemu dependencies.
@bidulock
Odd, previously makedepends('java-runtime' ...) was sufficient, but I've not built v17.2.6 recently. I'll give it a go when I have time
I had to add jdk11-openjdk to makedepends to get 17.2.6-2 to build in a clean chroot.
@diggit
Oh interesting: https://github.com/ceph/ceph/pull/39826
I somehow missed this. That said, I know many ceph devs still use Make as the build tool.
I will definitely experiment with setting ninja as the build engine for v18 and beyond.
@pbazaah I agree, it's not trivial. Official build docs are using ninja https://docs.ceph.com/en/quincy/install/build-ceph/#id1 . That's why I was asking. I may give it a shot later.
@diggit
As you mentioned, it is unlikely that switching the fundamental build system is as easy as -B ninja.
Moreover, ceph is more complex than the average cmake project, and I try to align with the upstream build as much as possible so-as to save myself a bunch of pain.
That said, feel free to fork https://github.com/bazaah/aur-ceph and play around. Hopefully it turns out to be a relatively simple change, and you can keep in sync with my tree.
Pinned Comments
pbazaah commented on 2022-10-05 13:03 (UTC) (edited on 2022-10-05 13:03 (UTC) by pbazaah)
For future commenters:
TLDR:
https://aur.archlinux.org/pkgbase/ceph | From source build (slow)
https://aur.archlinux.org/pkgbase/ceph-bin | Pre-built binaries (fast)
Unlike the original community version, this repo builds ceph from source. Ceph is a large, complicated project so this takes several hours on a good build server.
To get a similar experience to how community/ceph worked (pre-built binaries) use ceph-bin instead.