| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
the majority of this patch has been applied upstream, and we will
reintroduce the dout.h lambda fix in a followup standalone patch
|
|
fixed upstream
Upstream-ref: https://github.com/ceph/ceph/pull/53327
|
|
fixed upstream
Upstream-ref: https://github.com/ceph/ceph/pull/50216
|
|
fixed upstream
Upstream-ref: https://github.com/ceph/ceph/pull/51573
|
|
upstream no longer uses this method for finding {fmt}
|
|
Nobody has ever used this, and so far as I can tell, it was an
experiment that has been abandoned by the upstream; plus the next
major version of java will start miscompiling it
|
|
* HEAD
| \
| * 24fc5c0 <github@luxolus.com> pkgbuild: pkgver=18.2.4 pkgrel=5
| * 667cf67 <github@luxolus.com> pkgbuild: use py313-fixes.patch
| * 846e719 <github@luxolus.com> repo: add py313-fixes.patch
| * fd2f773 <github@luxolus.com> pkgbuild: use avoid-cpython-pysys-api.patch
| * 169e953 <github@luxolus.com> repo: add avoid-cpython-pysys-api.patch
| * 9192bee <github@luxolus.com> pkgbuild: update vendored python-bcrypt to 4.2.1
| * 543ea11 <github@luxolus.com> pkgbuild: use -GNinja for ceph build
| * ba0f532 <github@luxolus.com> justfile: rm tmpfs mount for chroot build
| /
| master
Signed-off-by: Bazaah <github@luxolus.com>
|
|
|
|
and add python-xmlsec + python-saml to checkdepends, as the dashboard
tox suite needs them
|
|
random stuff the python maintainers break arbitrarily so as to make sure
the python ecosystem is as fragmented as possible.
|
|
|
|
This is basically a backport+rebase of the work done in ceph/ceph#58199,
which fixes a bunch of usages of the now removed PySys_ cpython
functions / macros.
References: https://github.com/ceph/ceph/pull/58199
Upstream-ref: https://github.com/ceph/ceph/commit/f3be25433abdd3d6f4dc9f38f89b55c742b483fb
|
|
and update the relevant pyo3 patch to switch to 0.23, as is defined in
the python package
References: https://github.com/pyca/bcrypt/releases/tag/4.2.1
|
|
|
|
|
|
* HEAD
| \
| * d96f774 <github@luxolus.com> pkgbuild: pkgver=18.2.4 pkgrel=4
| /
| master
Signed-off-by: Bazaah <github@luxolus.com>
|
|
|
|
* HEAD
| \
| * 54c0f53 <github@luxolus.com> pkgbuild: pkgver=18.2.4 pkgrel=3
| * cc51155 <github@luxolus.com> pkgbuild: use fmt-formatter-const.patch
| * e717a88 <github@luxolus.com> pkgbuild: override Findfmt.cmake FMT_VERSION file lookup
| * 75a3706 <github@luxolus.com> repo: add fmt-formatter-const.patch
| /
| master
Signed-off-by: Bazaah <github@luxolus.com>
|
|
|
|
note this is a bit more complicated than the normal use-patch commit, as
part of the changes in fmt-formatter-const.patch were previously made in
fmt10-fixes.patch.
We remove those from fmt10-fixes, ensure the patch _we_ produce uses
const (...oops) and fixup file hashes
|
|
fmt11 has moved the definition of FMT_VERSION from core.h to base.h, so
we adjust the cmake function the upstream uses.
This isn't a patch because the next major version completely changes how
they look up fmt (and a lot of other things)
References: https://github.com/fmtlib/fmt/releases/tag/11.0.0
|
|
This patch ensures that _all_ fmt::formatter::format type functions
within the code base are const, as the fmt maintainers expressly mention
they should be.
Hopefully this fixes some of the random FTBS' we get when upgrading
boost/gcc/fmt
References: https://github.com/fmtlib/fmt/issues/2747
|
|
* HEAD
| \
| * 10719f1 <github@luxolus.com> pkgbuild: pkgver=18.2.4 pkgrel=2
| * 62c43be <github@luxolus.com> pkgbuild: use ceph-18.2.4-boost-1.86-fixes.patch
| * 8c5cc7d <github@luxolus.com> repo: add boost-1.86-fixes.patch
| /
| master
Signed-off-by: Bazaah <github@luxolus.com>
|
|
|
|
|
|
Fixes three issues found during rebuild:
1. Change to boost::uuids::uuid preventing *char cast
2. Missed header for boost::mt11213b
Seemingly an actual bug on ceph, this header should have been
included as far back as 1.60 but I guess was transitively included
from somewhere, and now isn't
3. undef BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS before including
<boost/python/*> headers
Apparently, you win free debugging of boost metaprogramming during
preprocessor macro expansion if you do this; who knew?
The maintainers of boost python. Because of the open 2 year old bug
report. (:
References: https://github.com/boostorg/python/issues/394
References: https://www.boost.org/doc/libs/1_86_0/libs/uuid/doc/html/uuid.html#changes_changes_in_boost_1_86_0_major_update
References: https://www.boost.org/doc/libs/1_86_0/doc/html/doxygen/headers/mersenne__twister_8hpp_1a29ac4e21d84adda27beb1803a0525ca5.html
|
|
* HEAD
| \
| * 2423fcc <github@luxolus.com> pkgbuild: pkgver=18.2.4 pkgrel=1
| * b55971a <github@luxolus.com> pkgbuild: update license to use SPDX identifier
| * e432e29 <github@luxolus.com> pkgbuild: add ceph-exporter.service to pkg.ceph-mgr
| * 879e512 <github@luxolus.com> pkgbuild: add pkg.ceph-node-proxy
| * 90b4dfa <github@luxolus.com> pkgbuild: rm included backport (mgr-dashboard-simplify-authentication-protocol)
| * 5d846f6 <github@luxolus.com> pkgbuild: rm included backport (ceph-volume-check-generic-reject-reasons)
| * 335c26f <github@luxolus.com> pkgbuild: rm superseded patch (tox-mypy-false-postive)
| * be62f5b <github@luxolus.com> repo: rm zombie patch (delete-test-librados-asio)
| /
| master
Signed-off-by: Bazaah <github@luxolus.com>
|
|
|
|
Its somewhat unclear how exactly ceph is licensed overall, and I think
my choice of licenses is not *wrong*, but may be incomplete.
References: https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0016-spdx-license-identifiers.rst
References: https://github.com/ceph/ceph/blob/v18.2.4/COPYING-LGPL3
References: https://github.com/ceph/ceph/blob/v18.2.4/COPYING-LGPL2.1
References: https://github.com/ceph/ceph/blob/v18.2.4/COPYING-GPL2
|
|
New systemd unit file for the 'ceph-exporter' daemon. There is
seemingly no official documentation for this service but I think its an
inhouse prometheus exporter that runs per node... though unclear if
'node' means 'osd' or 'mon' or something else.
References: https://github.com/ceph/ceph/tree/v18.2.4/src/exporter
|
|
This is seemingly something to do with cephadm and (Dell?) hardware
metrics using the RedFishAPI... api. Apparently it was split out because
the upstream 'needed' it in v18 but the rest of the changes around it
from v19 weren't going to be backported.
Seems fairly worthless for ArchLinux but who can say.
References: https://github.com/ceph/ceph/commit/e1630fb8fcfa4460306b5e506c6a436f68c505a8
|
|
Upstream-ref: https://github.com/ceph/ceph/commit/33d8befcabe3e60d9ccf6e4fdc2598c4db22934b
|
|
Upstream-ref: https://github.com/ceph/ceph/commit/50cdc0b66ce87888f1e634ed4323d91bd7273dcb
|
|
Since 14aff06 we now completely disable mypy, so this patch is irrelevant
|
|
Missed in 4095603 when patch was removed from pkgbuild
|
|
* HEAD
| \
| * 91a08e5 <github@luxolus.com> pkgbuild: pkgver=18.2.2 pkgrel=4
| * c95ff54 <github@luxolus.com> pkgbuild: bump ceph_bcrypt to 4.1.3
| /
| master
Signed-off-by: Bazaah <github@luxolus.com>
|
|
|
|
|
|
* HEAD
| \
| * c994ac3 <github@luxolus.com> pkgbuild: pkgver=18.2.2 pkgrel=3
| * dea7754 <github@luxolus.com> pkgbuild: rm VERBOSE=1 output from make check
| * 5867453 <github@luxolus.com> pkgbuild: add python-packaging to makedeps, ceph-mgr
| * 40c2ca2 <github@luxolus.com> pkgbuild: add pkgrel=3 patches
| * b2d88d6 <github@luxolus.com> pkgbuild: use ceph-volume backport patches
| * 9e62fb3 <github@luxolus.com> pkgbuild: cp mgr's ceph_module mocks to a dummy module
| * 0fe6e33 <github@luxolus.com> pkgbuild: rm mgr-ceph-module-stub.patch
| * ffa09b1 <github@luxolus.com> pkgbuild: add ceph_bcrypt to test suites
| * 14aff06 <github@luxolus.com> repo: add disable-mypy-flake8-tests
| * 232f0f5 <github@luxolus.com> repo: add py312-fixes.patch
| * 3a2a24a <github@luxolus.com> repo: add test-mempool-shard-select-disable
| * 709961b <github@luxolus.com> repo: add std-atomic-depreciations.patch
| * d8b813a <github@luxolus.com> repo: add gcc-14-fixes
| * acc985a <github@luxolus.com> repo: backport two fixes for ceph-volume
| /
| master
Signed-off-by: Bazaah <github@luxolus.com>
|
|
|
|
|
|
|
|
|
|
|
|
Basically, we add the initialization for the mgr's test suite to a
location that *all* mgr module test suites include in their PYTHONPATH
I'm not sure why this worked before, when it stopped exactly, and what
changed to make it stop. Yay python.
This shouldn't be copied into the CMAKE_INSTALL_DIR, but we should
double check the built packages to be 100% sure.
|
|
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
|
|
We use --file-links to hint to python that it should consider more
locations for package lookups.
Could be useful if python-xmlsec ever rears its ugly head again
|
|
A whole bunch of random lints and "x is best practice" messages have
started generating a bunch of unwanted line noise in the test suite, so
we disable them all
|