Re: postfix-3.11.4,1 does not work with lmdb-1.0.0,1, requires 0.93.5,1
A FreeBSD User <[email protected]> Sun, 19 Jul 2026 15:53:12 +0200
| Newsgroups | gmane.os.freebsd.devel.ports |
|---|---|
| Message-ID | <[email protected]> |
--Sig_/HT6yUnG.g=d5V9+SZoVZvpl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Tage des Herren Sun, 5 Jul 2026 05:10:11 -0700 David Wolfskill <[email protected]> schrieb: > On Fri, Jul 03, 2026 at 11:59:27PM +0000, Einar Bjarni Halld=C3=B3rsson w= rote: > > On 7/3/26 11:47 PM, Jordan M wrote: > > ... =20 > > > Can we get databases/lmdb reverted to 0.93.5, and 1.0.0 added as a > > > separate origin? > > > =20 > >=20 > > I agree with this. Upgrading lmdb broke both knot3 and bind920 for me. = I've > > fixed it by downgrading lmdb in a ports-overlay tree that poudriere use= s. > >=20 > > .einar =20 >=20 > For my use cases, the update to lmdb affected mail/mutt and dns/bind920. I had some issues after the upgrade to lmdb 1.0.0, but all resolved after r= ecompiling theport recusively, especially bind920. After that, everything worked as expected. = Same with poudriere. I didn't see any miscompilation due to lmdb 1.0.0 - in my use ca= ses and restricteted set of ports compiled via poudriere! Reverting to 0.93.X made the whole process going backwards and really messy= ! Wasn't necessary, I presume. >=20 > However -- in my use cases -- neither was broken. >=20 > I suspect that for mutt, the use is for ephemeral caches. (And in any > case, there was an update to mutt within the last 24 hours.) And for > bind920, I do not happen to make use of features that actually use lmdb. > (Thanks for the "heads up," though, so I spent a few minutes scanning for > the existence of any possible lmdb files ... and then updated rather > more cautiously than ususal, with a few extra checking steps along the > way.) >=20 > Peace, > david --=20 A FreeBSD user --Sig_/HT6yUnG.g=d5V9+SZoVZvpl Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iJEEARYKADkWIQRQheDybVktG5eW/1Kxzvs8OqokrwUCalzW4xsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDMACgkQsc77PDqqJK82/QEAxnZnBMIIzrsfePvchcl4 0kH1MSuOnFRyDlR/7SNwb1ABALVzRK0+4hSg9uBE0tGy1eUUAOyMYZ6UpqWsSyFi HakO =dGjx -----END PGP SIGNATURE----- --Sig_/HT6yUnG.g=d5V9+SZoVZvpl--