summarylogtreecommitdiffstats
path: root/PKGBUILD
AgeCommit message (Collapse)Author
2023-12-31pkgbuild: pkgver=18.2.1 pkgrel=1Bazaah
2023-12-31repo: rm ceph-17.2.6-mgr-dashboard-node-version.patchBazaah
No longer needed, the upstream as upped their nodejs version. References: https://github.com/ceph/ceph/pull/52828 Upstream-Ref: https://github.com/ceph/ceph/commit/47f49e5b1ae2e5bf7aad5df23d877ae5df00210c
2023-11-06pkgbuild: pkgrel=2Bazaah
2023-11-06pkgbuild: tidy up check()Bazaah
pkill is not required by checkdepends anymore rendering this loop useless, and I haven't seen orphan processes so far. Can always add it back later if needed.
2023-11-06pkgbuild: switch off verbose buildBazaah
The build is in a good enough spot now that the extra verbosity is unneeded for most operations.
2023-09-09pkgbuild: pkgver=v18.2.0 pkgrel=1Bazaah
2023-09-09pkgbuild: updates to install files for v18Bazaah
Minor updates to the installed files for: - ceph-common - librbd - librgw - ceph-cephadm
2023-09-09pkgbuild: enable optional rbd componentsBazaah
- WITH_RBD_RWL, WITH_RBD_SSD_CACHE Enables the rbd writeback cache, both pmem and ssd variants. - WITH_RBD_MIRROR Enables mirroring rbd images between ceph clusters, similar to rgw multi-zonal replication These changes were prompted by github.com/Enelar in github.com/bazaah/aur-ceph/pull/18/commits/41a3081df83fb7ab9fd9d94f736ded417afb58da References: https://docs.ceph.com/en/reef/rbd/rbd-persistent-write-log-cache References: https://docs.ceph.com/en/reef/rbd/rbd-mirroring/
2023-09-09pkgbuild: disable proprietary rgw backendsBazaah
These are some seagate/intel specific features, seemingly to use ceph rgw as the S3 interface to their products, and/or supporting some intel encrypt/decrypt hardware. These are (currently) disabled by default, but I have added them for future proofing. I think these will never be valid/useful compile options on Archlinux.
2023-09-09pkgbuild: disable tracing / opentelemetryBazaah
My reasoning here is to avoid adding _even more_ dependencies to ceph-libs. I do want to revisit these when/if I break up the mega packages into separate libs
2023-09-09pkgbuild: reenable system utf8procBazaah
Was switched to default disabled, reenabling it here for our builds. Upstream-Ref: https://github.com/ceph/ceph/commit/90662cad562fffbdeac33f3b79eac6a02eff8c2a
2023-09-09pkgbuild: use backport-log-runway-expansion.patchBazaah
2023-09-09pkgbuild: use fix-ecode-shec-test.patchBazaah
2023-09-09pkgbuild: use ceph-18.2.0-fmt10-fixes.patchBazaah
2023-09-09repo: update ceph-17.2.4-test-bluefs-split.patchBazaah
mostly fixes to line offsets, but there was one real if small change to a variable init.
2023-09-09repo: rm upstreamed iterator depreciationsBazaah
This commit removes the patches to three files from ceph-17.2.5-fix-iterator-depreciations: - src/include/xlist.h - src/include/rados/librados.hpp - src/crimson/os/seastore/omap_manager/btree/string_kv_node_layout.h As the upstream has fixed them. However, the patches to the following have not yet been applied upstream, and thus remain: - src/include/rangeset.h - src/msg/async/dpdk/circular_buffer.h Upstream-Ref: https://github.com/ceph/ceph/commit/77a3ed56a7b7326814ea5d37214bec1d88ec334e Upstream-Ref: https://github.com/ceph/ceph/commit/691119c389e119a03aea606b7c4093d46c6db43d Upstream-Ref: https://github.com/ceph/ceph/commit/905969611d256b6613bd86347bd51ddeb0603b79 Upstream-Ref: https://github.com/ceph/ceph/commit/c662ee698c6366e1b53856eb1a2c903c301a426f
2023-09-09pkgbuild: update tox-mypy-false-postive.patchBazaah
same patch as before, but context needs updating to apply correctly
2023-09-09pkgbuild: rm upstreamed gcc13 patchesBazaah
The changes within are now included in the upstream, and are no longer needed Upstream-ref: https://github.com/ceph/ceph/pull/50438
2023-09-09pkgbuild: rm delete-test-librados-asio.patchBazaah
No longer applies to the upstream
2023-09-09pkgbuild: rm -DFMT_DEPRECATED_OSTREAMBazaah
There seems to just be a large amount of effort across the entire project for this one. Not surprising, given my investigations but it does make it difficult to provide a singular upstream reference for this change. Instead I'll just link directly to all the commits involved since v17.2.0... - ceph/ceph@d8d93b0fe3b crimson/osd: correct the fmt::formatter<WatchTimeoutRequest> - ceph/ceph@71b9344f299 crimson/os: specialize fmt::formatter<> for StagedIterator - ceph/ceph@32e207da3f3 crimson/os: include fmt/os.h for printing std::error_code - ceph/ceph@85830863fa4 crimson: specialize fmt::formatter<> for formatting using {fmt} - ceph/ceph@76e4c5d83c2 test/librados/aio_cxx: use fmt formatting - ceph/ceph@2e7aea7b0fd crimson/os: print pointer using fmt::ptr() - ceph/ceph@c9569f8eb02 crimson: specialize fmt::formatter<> - ceph/ceph@01f6bef6e52 *: specialize fmt::formatter<> for formatting using {fmt} - ceph/ceph@3f67d67ede1 crimson: specialize fmt::formatter<> to print using {fmt} - ceph/ceph@42dc970392e crimson/net: print shared_ptr using fmt::ptr() - ceph/ceph@fe1e6b6c4eb neorados: compile with fmt v9 - ceph/ceph@b2c61113ffb crimson/net: define fmt::formatter for write_state_t - ceph/ceph@1f1398bc515 mon: Fix snprintf truncation warning by switching to fmtlib - ceph/ceph@93dfb7e88b9 common: improving fmtlib handling of ceph::utime_t - ceph/ceph@3d7a895d197 include/object_fmt: mark fmt::formatter<>::format() const - ceph/ceph@2901943618f common/LogEntry: specialize fmt::formatter<LogEntry> - ceph/ceph@6e223a68021 common/Journald: include msg/msg_fmt.h - ceph/ceph@c0a3d460297 mon: use fmt::format for stderr cluster logging - ceph/ceph@cef04bc4ed0 common: use fmt::format for stderr logging - ceph/ceph@31aa539f266 osd: use fmt/ranges.h for printing ranges - ceph/ceph@b7b7ff4cce3 include/types_fmt: use fmt::join() to format containers - ceph/ceph@b287fadde3e fmt: pickup v8.1.1 - ceph/ceph@3c46dd64bbc cmake: bump up required fmt version - ceph/ceph@01f9dc84826 msg/msg_type: use fmt::format to print entity_addr - ceph/ceph@ac114ad172b crimson/os: use fmt::format() instead of sstream - ceph/ceph@bb9d099ede8 crimson: specialize fmt::formatter<>() for crimson types - ceph/ceph@3fd91d7e6d9 crimson/os/seastore: drop compile-time fmt validation
2023-09-09pkgbuild: rm ceph-17.2.4.-tox-cephadm-rm.patchBazaah
Underlying issue found in f5af709 has been fixed upstream, re-enabling test. Upstream-Ref: https://github.com/ceph/ceph/commit/b5218528d63ae87ca77229bce1635c62411959e8
2023-09-09repo: revert backport-with-fmt-version.patchBazaah
This was a temporary fix for a v17 rebuild. The upstream has fixed many, many fmt issues in the new release. Reverts: 7dfdbe1 Reverts: 34d11c3
2023-09-09pkgbuild: add inetutils,xmlstarlet to checkdependsBazaah
As the check_generated.sh test now depends on xmlstarlet, and `hostname` is used a bunch.
2023-09-09pkgbuild: add makedepend 'thrift'Bazaah
required by the upstream now
2023-09-09pkgbuild: cleanup pkgname, reorganize arch,pkgdescBazaah
Mostly updating the pkgname array to reflect the refactoring done on packaging, and a slight change in field ordering to move pkgdesc higher in the file
2023-09-09pkgbuild: reorganize makedepends, checkdependsBazaah
Improve formatting, and breakup into groups (system and python, currently), so as to escape the giant word soup that currently exists.
2023-09-09pkgbuild: package virtual targetsBazaah
These are virtual (dependency only) packages that serve a couple purposes: 1. Backwards compatibility with the existing Archlinux ceph packages. That is: - ceph-libs: all non-binary packages - ceph-mgr: (same as before / not virtual) - ceph: all binary packages 2. Stable targets for certain functionality, namely cluster components and the `ceph` CLI utility which is used for most interactions with a cluster. - ceph-libs - ceph-cluster - ceph-cli - ceph
2023-09-09pkgbuild: package misc. ceph tooling / libsBazaah
These are mostly used by the upstream development team for interacting with various internals of the cluster and live tests. However, the impetus for this entire patchset also lurks: java-cephfs. A package that requires we pull in the entire java runtime, likely for a package absolutely no one uses. Good riddance. - ceph-tools - ceph-test - java-cephfs
2023-09-09pkgbuild: package more client / utilsBazaah
These are a couple useful utilities for interfacing with ceph, of which ceph-volume is likely the most important, as is it responsible for provisioning devices for use as OSDs. cephadm is an honorable mention, being a 9k line python file used in managing clusters... if you like the idea of having 9k lines of python sitting between you and your entire storage backplane. (I do not) - ceph-volume - cephfs-shell - cephfs-top - ceph-cephadm
2023-09-07pkgbuild: package ceph cluster componentsBazaah
These comprise the daemons and associated tooling that form the cluster or "backend" of a ceph deployment. Notably, they have a dependencies on both the core libs, python libs _and_ librgw (a client), as despite being a backend or server component; ceph-rgw is _actually_ a client of ceph (and librgw specifically), that just so happens to run as a daemon -- providing object storage. - ceph-base - ceph-mon - ceph-mgr - ceph-osd - ceph-mds - ceph-rgw
2023-09-07pkgbuild: package ceph python libsBazaah
These are python bindings to the underlying C/C++ libs, and are used for most of the ancillary CLI tooling ceph provides, including as support tooling for cluster components. - python-ceph-common - python-rados - python-rbd - python-cephfs - python-rgw
2023-09-07pkgbuild: package core clientsBazaah
These form the core clients for ceph; rbd (block), cephfs (filesystem), rgw (object). - librbd - ceph-rbd - libcephfs - ceph-cephfs - librgw
2023-09-07pkgbuild: package core libsBazaah
These are the core / common libraries that almost everything else will depend on at some level. libcephsqlite is an outlier, but is also depended on by other ceph components despite _technically_ being a RADOS client, hence its inclusion. - ceph-compressor - ceph-crypto - ceph-erasure - ceph-common - librados - ceph-rados - libcephsqlite
2023-09-07pkgbuild: add func _make_ceph_packagesBazaah
The true workhorse for packaging ceph, this function is responsible for calling make install, and _ensuring all files accounted for_ -- moved or deleted -- before yielding. It will contain a series of `_package` invocations, one per package, with each actual package function being a thin wrapper around: 'mv __pkg__/$pkgname/* "$pkgdir"'
2023-09-07pkgbuild: add _package, _print funcsBazaah
These are the beginning of a refactoring of how we handle the package_* functions. Currently, we run `make install` once per packaging function and attempt to delete the bits that aren't related to the package currently running. This has several downsides, including conflicting file owners, missed addition(al file)s in later versions and speed. These new functions will serve as the engine for enumerating the precise file dependencies for each package, and provide a pretty output during the packaging process of this list.
2023-09-07pkgbuild: rm old package() functionsBazaah
2023-09-06pkgbuild: pkgrel=4Bazaah
Rebuild for boost, thrift and some python stuff
2023-07-30pkgbuild: pkgrel=3Bazaah
2023-07-30pkgbuild: use ceph-17.2.6-cython-fixes.patchBazaah
2023-07-30pkgbuild: use backport-with-fmt-version.patchBazaah
Issue: https://github.com/bazaah/aur-ceph/issues/17 Reported-by: https://aur.archlinux.org/account/UweSauter Reported-in: https://aur.archlinux.org/pkgbase/ceph#comment-926651
2023-05-12pkgbuild: pkgrel=2Bazaah
2023-05-12pkgbuild: use cherrypy, pylint patchesBazaah
2023-05-08pkgbuild: use mgr-dashboard-node-version.patchBazaah
2023-05-08pkgbuild: use gcc13 patchesBazaah
2023-04-10pkgbuild: pkgver=17.2.6, pkgrel=1Bazaah
2023-04-10pkgbuild: rm disable-test-cls-fifo.patchBazaah
Upstream appears to have removed the test Upstream-Ref: https://github.com/ceph/ceph/commit/62121704f019f225b1df4b0c63ba2d89fe9be9ca
2023-04-10pkgbuild: revert ceph-18.0.0-mgr-sqlite-pragmas.patchBazaah
As this is now backported in the upstream Upstream-Ref: https://github.com/ceph/ceph/commit/b49753e374e0ba30e61eab0b7d88abb5104e5975 Reverts: 82a7efacca33c5640103622e251755a5523e78cd
2023-04-10pkgbuild: revert rdkafka.mpatch, use thereinBazaah
No longer needed, as the Archlinux package has fixed this issue by reverting to an older (?) method for building rdkafka, which doesn't contain the bug this patch worked around. Reverts: dd2565ded777ce438f5063d6e9cc8b2fe22244e7 Reverts: d0451743748d9c381a598fb45b658c3669ee357f References: https://github.com/archlinux/svntogit-community/commit/924fddef74a86f020ec6813291979946f6da55da
2023-04-10pkgbuild: rere tox-mypy-false-postive.patchBazaah
Same patch, just updated to follow upstream changes to src/pybind/mgr/tox.ini
2023-03-06pkgbuild: pkgrel=6Bazaah