summarylogtreecommitdiffstats
path: root/.SRCINFO
AgeCommit message (Collapse)Author
2024-05-25pkgbuild: pkgver=18.2.2 pkgrel=3Bazaah
2024-05-25pkgbuild: add python-packaging to makedeps, ceph-mgrBazaah
2024-05-25pkgbuild: add pkgrel=3 patchesBazaah
2024-05-25pkgbuild: use ceph-volume backport patchesBazaah
2024-05-25pkgbuild: rm mgr-ceph-module-stub.patchBazaah
This doesn't work. Or rather it does, but badly and for reasons I didn't understand. To set the stage. 1. All mgr modules in src/pybind/mgr/*/module.py import a 'mgr_module' 2. This module is located at src/pybind/mgr_module.py 3. It imports a module, 'ceph_module' that **does not exist.** I didn't understand how this could work, as the file even remotely similiar is src/pybind/mgr/ceph_module.pyi -- note the 'i'. This is what is called a "python interface file" and basically isn't something the python runtime is aware of. It's only use is by static code checkers like mypy (and presumably the IDEs of people that work in this code). I, naively assumed that somehow previous python versions had mistaken this file for a real module hence the previous patch, where I just define the various symbols referenced from other modules. This isn't the case. Instead, the C++ mgr daemon _at runtime_ injects what is effectively a bridge module into the C++ defined ceph data structures. This, obviously doesn't work during testing, but the upstream does have some interesting machinery in src/pybind/mgr/tests/__init__.py, though I don't understand how it would propagate to other test suites, and very clearly it hasn't worked for at least since 18.2.0 for our builds. A future commit will properly fix this issue
2024-03-23pkgbuild: pkgrel=2Bazaah
2024-03-23pkgbuild: use mgr-alias-ceph-bcrypt.patchBazaah
2024-03-23pkgbuild: pkgver=18.2.2 pkgrel=1Bazaah
2024-03-23pkgbuild: add python-bcrypt sources,patchesBazaah
For our internal ceph fork of python-bcrypt
2024-03-23pkgbuild: mv {,ceph-}disable-empty-readable.sh-testBazaah
2024-03-23pkgbuild: use mgr-ceph-module-stub.patchBazaah
2024-03-23pkgbuild: use mgr-dashboard fix backportBazaah
and remove the now unneeded py deps: - python-pyjwt - python-cryptography
2024-03-23pkgbuild: rm checkdepends->python-mockBazaah
Dropped to AUR and I believe unneeded?
2024-02-06pkgbuild: pkgver=18.2.1 pkgrel=2Bazaah
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-09-09pkgbuild: pkgver=v18.2.0 pkgrel=1Bazaah
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 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-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
2023-03-06pkgbuild: use ceph-17.2.5-rgw-client-boost-string-view.patchBazaah
2023-03-06pkgbuild: use rdkafka.mpatch + set envBazaah