correct platforms. ceph currently doesn't build on aarch64-linux. So
let's not lie in meta.platforms.
ceph: fix multiple output
We currently just move $out/share/ceph/mgr to
$lib/lib/ceph, and then remove all references to $out with a find
command.
I checked $out, the only reference to $out is in
$lib/lib/ceph/libceph-common.so.0, coming from src/common/options.cc:
https://github.com/ceph/ceph/blob/master/src/common/options.cc#L5050:
> Option("mgr_module_path", Option::TYPE_STR, Option::LEVEL_ADVANCED)
> .set_default(CEPH_DATADIR "/mgr")
> .add_service("mgr")
> .set_description("Filesystem path to manager modules."),
Just removing the reference might break some behaviour - it should point
to $lib/ceph/mgr instead.
We can fix this in a much more elegant fashion by just passing a custom
CMAKE_INSTALL_DATADIR to the build system.
ceph: fix outdated Boost::python substitutions
Instead of substituting in CMakeLists.txt files, one now needs to set
MGR_PYTHON_VERSION.
ceph: clean up PYTHONPATH wrapping
Set `pythonPath` instead of exporting PYTHONPATH.
Use `toPythonPath` to construct the PYTHONPATH where we need manual
wrapping. There's no ceph-volume, only ceph-mgr.
ceph: set doCheck = false explicitly
and describe why.
ceph: patch more shebangs
ceph: use system-provided gtest and rocksdb
* Update trousers to latest, use regular openssl (#68338)
trousers: cleanup
* some CFLAGS and LDFLAGS are not needed anymore
* libtool file fixup was a no-op
* license is now BSD-3 since:
0160d229f8/
This commit updates twa from version 1.8.0 to version 1.9.1,
specifying its new 'jq' dependency.
It also moves 'makeWrapper' from the build inputs to the native
build inputs, as it's not necessary during runtime.
* circus: fix incompatible dependency of python-circus
* circus: move out of python packages set
* circus: remove directly used python packages arguments
This reverts commits 53a536c698
and af931c172d.
The repology.org info was incorrect, pulling in a development version
of mu as a release. The current (stable) release of mu is still 1.2:
https://github.com/djcb/mu/releases
* srt-vtt: init at 2019-01-03
* Append 'unstable' to pname
Co-Authored-By: Marek Mahut <marek.mahut@gmail.com>
* Fix version
* Remove which validation
* Add support to linux only
Co-Authored-By: Evils-Devils <30512529+Evils-Devils@users.noreply.github.com>
biber: 2.12 -> 2.13
Vendored potrace was moved from libs/potrace to
texk/dvisvgm/dvisvgm-src/libs/potrace. Unfortunately, it is not trivial
to remove it from there, so for now dvisvgm seems to be using its
vendored dependencies.
Without providers (also called plugins) pulumi doesn't do much. The way
they work, if you want to use a provider, pulimi will look for it in
your PATH, and if not found it will download it. Providers are just
executables, but third party binaries usually don't work on nixos unless
they are patched with the patchelf utility. Because of that, I'm
installing some patched providers with the main pulumi binary.
I'm also adding a small script helper to generate the hashes for all the
binaries.
tre is a improved version of the command `tree`. Its main additions:
1. colored output
2. ignores paths specified in .gitignore
3. editor alias for each entity listed
Source/Homepage: https://github.com/dduan/tre
all: update from 4.6.0 to 4.7.2
keybase:
- added gnupg as a dependency and patch fix-patch-keybase.patch
kbfs:
- added fuse as a dependency and patch fix-patch-kbfs.patch
* acme-client: 0.1.16 -> 0.2.3 (#71853)
The upstream acme-client that used to be at [1] has now been integrated
into OpenBSD, and the portable version that it links to at [2] is marked
as unmaintained. However, letsencrypt.org links to [3] for a portable
version, and indeed, that repository contains a version that has recent
activity, so I switched over to that.
It is hard to tell what the difference is between the OpenBSD version
and what is on Github, and even if that would be easy, there are a lot
of Linux-specific changes. This program is dealing with certificates, so
I feel it is important to at least check that thare are no obviously
unintended differences between the previous version and the new, but I
don't know of a good way of doing that at this point. I will continue
to investigate before I open a pull request.
[1]: https://kristaps.bsd.lv/acme-client/
[2]: https://github.com/kristapsdz/acme-client-portable
[3]: https://github.com/graywolf/acme-client-portable
* acme-client: fix Linux build of new upstream
The new source does not include a configure script in the repository,
but we can generate it with automake. Also, the new acme-client-portable
has an OpenSSL compatibility layer, but that actually breaks building
against LibreSSL. Avoid this issue by patching the compatibility layer
to be less eager to define things when linking against LibreSSL. I will
also submit a pull request for that upstream.
I don't expect this to work on Darwin, and the current package suggests
it does, but if the upstream (portable) version is no longer maintained,
for Darwin, perhaps we should just drop support for it. But maybe it
will just work, CI or somebody with a Darwin system will have to try.
* acme-client: 0.2.3 -> 0.2.4
My LibreSSL compatibility patch has been merged upstream into
acme-client-portable, and version 0.2.4 that includes it has been
released, so we can remove the patch here.
* acme-client: address review feedback
* Replace the manual autoreconf invocation with autoreconfHook.
* Remove DEFAULT_CA_FILE, which no longer affects the build.
The patch prevents the following error:
[2/7] Generating manpages with a custom command.
../sshfs.rst:210: (ERROR/3) Unexpected indentation.
../sshfs.rst:211: (WARNING/2) Block quote ends without a blank line; unexpected unindent.
