Hello. To the best of my knowledge, all versions there have a problem with Botan2 and Botan3 in terms of the way password-handling algorithms are coded.
My current patch for Botan3 is: https://github.com/NixOS/nixpkgs/raw/master/pkgs/by-name/mo/monotone/monotone-botan-key-format.patch Additionally, it looks like Botan3 no longer has prefix for its error messages, thus the prefix-removal code now loses the first «meaningful» character. https://github.com/NixOS/nixpkgs/raw/master/pkgs/by-name/mo/monotone/monotone-botan-error-reporting.patch In the meantime, I have looked (manually) what is needed to get PCRE2 support for things Monotone actually uses, my patch is https://github.com/NixOS/nixpkgs/raw/master/pkgs/by-name/mo/monotone/monotone-pcre2.patch I think that your Botan2/Botan3 branches never passed all the testsuite? I have some patches to the tests to handle the different failure report mode with new Botan, PCRE2 now allowing longer group names etc., see the remaining patches in https://github.com/NixOS/nixpkgs/tree/master/pkgs/by-name/mo/monotone I would be interested to get some feedback so that I could improve the patches for integration, and maybe then there could be a new release of Monotone, passing all the tests on Botan3/PCRE2 (Debian stable now ships both, and previous versions are long EoL upstream, so maybe it is OK to target only the current versions). Thanks for your work! Michael Raskin >On 2025-12-25 13:07, Michael Raskin via developer discussion for >monotone wrote: >>> % mtn hea >>> mtn: branch 'net.venge.monotone.lapo.botan2' is currently merged: >>> 6ba7278b3d29ed139975347df6b88be344c53b67 [email protected] 2025-12-23 09:26:24 >> >> What is the recommended server to pull this from? (mtn/git/tarball, no >> problem with either, hopefully the official release will have a tarball >> for package bootstrapping) > >A tarball will be generated as soon as we finalize the release, yes. > >Right now you can bootstrap from github: > >https://github.com/lapo-luchini/monotone/tree/lapo.botan2 > >Or if you have a working mtn already you can: >(you probably know most of this, but just for completeness sake…) > >$ mtn -d mtn db init >$ mtn -d mtn sy 'mtn://monotone.ca/monotone?net.venge.monotone{,.*}' >$ mtn -d mtn co -b net.venge.monotone.lapo.botan2 monotone-1.2dev > >And then in either case build with: > >$ cd monotone-1.2dev >$ autoreconf >$ ./configure >$ make -j8 > >-- >Lapo Luchini >[email protected]
