Tim Rühsen <tim.rueh...@gmx.de> writes: > Are you going to merge all of those into your master branch, so that > e.g. latest GnuTLS can be build it ?
I will, but not with urgency. And possibly with slightly different organization (but the implementation and the new rsa_sec_decrypt api will be the same). And I'll be a bit busy both coming week and next weekend. And naturally, getting the 3.4.1 release out has the highest priority, which should happen in a day or two. I would have hoped for a bit more testing, but I'll have to make release very soon regardless. > Currently I see a several automated builds breaking. It's those with > the latest GnuTLS (from git master) as dependency. They normally pull in > all dependencies (nettle and others) in their latest version from git > repos (mostly branch 'master'). There's both a branch "release-3.4-fixes", and a tag "nettle_3.4.1rc1". Could you use either of them for the Nettle dependency in the mean time? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
