summarylogtreecommitdiffstats
path: root/.SRCINFO
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-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
2022-12-21pkgbuild: pkgrel=5Bazaah
2022-12-21pkgbuild: package_ceph backup /etc/ confBazaah
Backport-to: ceph-bin Issue: https://github.com/bazaah/aur-ceph/issues/9 Closes: #9
2022-12-21pkgbuild: add logrotate-ignore-dups.patchBazaah
This fixes an unfortunate issue in the upstream's provided logrotate, and the one which `cephadm` creates during runs. Unfortunately, logrotate throws an error if more than one rule matches a given file, which is the case between our '.../ceph/*.log' and the cephadm generated one: '.../ceph/cephadm.log'. Because the file is generated we can't really complain to the maintainer for cephadm, and we also can't change our rule because ceph may generate any pattern matching '<cluster>-<svc>-<id>', all of which are user / cluster specific. Fortunately, the most recent (as of this commit) logrotate as introduced a workaround: 'ignoreduplicates' which does what you expect. We patch the upstream logrotate.conf to include this keyword, fixing this issue. See the issue for more. References: https://github.com/logrotate/logrotate/pull/473 References: https://github.com/ceph/ceph/blob/v17.2.5/src/cephadm/cephadm#L9408 Closes: #8 Issue: https://github.com/bazaah/aur-ceph/issues/8 Reported-by: snack@aur.archlinux.org
2022-12-21pkgbuild: add mgr-sqlite-pragmas.patchBazaah
This patch is taken directly from an (at the time of writing) open PR of the upstream which fixes a crash in the mgr's device_metrics module when using a later version of the python sqlite driver. The upstream docs for libcephsqlite specifically call out that file based temp tables are not supported. See: https://docs.ceph.com/en/quincy/rados/api/libcephsqlite/#temporary-tables Closes: #5 Issue: https://github.com/bazaah/aur-ceph/issues/5 Upstream-Ref: https://github.com/ceph/ceph/pull/48449
2022-11-06pkgbuild: pkgrel=4Bazaah
3 is skipped to accommodate a screwup in the sister ceph-bin package
2022-11-06pkgbuild: add ceph.sudoers to package_ceph()Bazaah
This file is inspired by the upstream's 'sudoers.d/ceph-smartctl' file, however, unlike their one; isn't a security threat if anyone nasty ever elevates to the 'ceph' user. We use the latest and greatest in sudo technology: regexes. Sudo is only 4 decades late to the party, and we welcome them in with open arms, though unfortunately all the pizza has been eaten, along with most of the soda drinks, and most of the party's participants are tired, like this metaphor.
2022-11-05pkgbuild: rm zstd overwrite in prepare()Bazaah
Since 35b4e84 we no longer need to play funny games with the upstream around zstd.
2022-11-05pkgbuild: pkgrel=2Bazaah
2022-11-05pkgbuild: rm broken cmake depends patchesBazaah
- ceph-17.2.4-common-legacy-gen-depends.patch - ceph-17.2.4-compressor-common-depends.patch These do not *actually* solve the problem they were originally added as fixes for. Here's the real problem: Sometime between v16 and v17 the upstream changed how they handle internal configuration. Previously, they had headers that were included "globally" -- in a common ${CMAKE_PROJECT_PATH}/include -- dir, and everything just imported these headers, without an explicit dependency on src/common/options ('s targets). This was okay because: 1. The headers always exist 2. You can include headers that haven't yet had their source file compiled. You only need to ensure that by link time the relevant .o files exist. However. These "global" header files *now require an arbitrarily slow python script to generate them*. And CMake is not aware of this dependency, leading to compile fails because other sources are importing headers that don't exist yet. I tried for a long time to catch all the targets that depend on these headers' CMake target, and gave up after about 30ish; as even if it was possible, that patch is simply unmaintainable long term. Instead, we'll take a much dumber, simpler solution: just run the generate step before building. See this commit's parent for more.
2022-10-26pkgbuild: pkgver=17.2.5Bazaah
Normally I don't do point upgrades in the same patch set as major upgrades, however the upstream made an 'oops' in their release train for v17 that lead to a couple important regressions. See the changelog below for an overview, and the link for the full story. Changlog: * c6e18266dfb mgr/telemetry: handle daemons with complex ids * 6a1a427fc5f ceph-volume: fix regression in activate * feeadd7e2a8 mgr/rook: fix error when trying to get the list of nfs services * 1d8a2b46bd3 Revert "osd/PeeringState: fix missed `recheck_readable` from laggy" * c67f74c3c76 Revert "osd/PeeringState: proc_lease_ack break once found from OSD" Link: https://ceph.io/en/news/blog/2022/v17-2-5-quincy-released Upstream-Ref: https://github.com/ceph/ceph/pull/48519
2022-10-26pkgbuild: enable rgw features aqmp,kafkaBazaah
also enforce WITH_FIO=OFF (the current default)
2022-10-26pkgbuild: update package runtime depends()Bazaah
According to namcap. Remember to port these to `aur/ceph-bin`, me!
2022-10-26pkgbuild: fix-iterator-depreciations.patchBazaah
This commit patches the few instances of std::iterator usage in the upstream. There's no real benefit here, besides reducing the line noise during builds... and yet this is one of the change sets I've liked making the most. Followed the fluentcpp guide for understanding the fix: https://www.fluentcpp.com/2018/05/08/std-iterator-deprecated/ and used this ripgrep to find the definition sites: `rg ':\s*(public)?\s*(std::)?iterator\s*<' .`
2022-10-26pkgbuild: pybind-unmock-cythonize.patchBazaah
This is a strange one. Each of pybind/{rados,rbd,cephfs,rgw}/setup.py has a clause which potentially mocks cythonize(): ``` if (len(sys.argv) >= 2 and any(i in sys.argv[1:] for i in ('--help', 'clean', 'egg_info', '--version') )): def cythonize(x, **kwargs): return x ``` The important thing here is 'egg_info', which is _always_ invoked by the cmake functions the upstream uses in cmake/modules/Distutils... leading to failures that look like this: ``` IF BUILD_DOC: ^ ------------------------------------------------------------ rados.pxd:7:3: Compile-time name 'BUILD_DOC' not defined Error compiling Cython file: ------------------------------------------------------------ ``` This commit patches the setup.py(s), removing this clause which then allows the cython builds to work just fine. I have no idea how or even if the upstream gets clean builds as the parts that make up this bug haven't been touched in six years.