* gmrender-resurrect: cc96ede -> v0.0.8
* gmrender-resurrect: add ashkitten as maintainer
* gmrender-resurrect: readability and idiomacy improvements
* gmrender-resurrect: fetchpatch is not used
* gmrender-resurrect: fix version number format for nix
Alioth is now offline -> https://wiki.debian.org/Salsa/AliothMigration
Sources moved to other forges (Salsa for example)
Some release tarballs are available on alioth-archive.debian.org
I don't really understand why this works:
- Building with python3 because python2 fails with "error: invalid command
'bdist_wheel'".
- Specifying the path to prompt_toolkit v1 because otherwise the dependency
resolution fails with "ERROR: Could not find a version that satisfies the
requirement prompt-toolkit<2.0.0,>=1.0.0 (from http-prompt==1.0.0) (from
versions: none) ERROR: No matching distribution found for
prompt-toolkit<2.0.0,>=1.0.0 (from http-prompt==1.0.0)".
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
* 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.
