Due to the recent issues with the upgrade of db/lmdb from 0.9 to 1.0, a new port db/lmdb0 was created, and the various consumers of lmdb (net/samba423 among them) were updated to use db/lmdb0 rather than db/lmdb. I have the old version (0.9) of db/lmdb installed, and net/samba423 using it. I just tried updating to db/lmdb0, and it failed. The build is done in a clean environment (by Synth). The log shows that net/samba423 needs lmdb>=0.9.16, and Synth therefore installs lmdb0-0.9.35. However, after doing so, the build fails because an appropriate lmdb (i.e. >= 0.9.16) is not found (despite lmdb0-0.9.35 having just been successfully installed). So it knows it should install lmdb0, but then doesn't think that installing lmdb0 was good enough for what it needed? Applicable portion of the log: ===> Returning to build of samba423-4.23.8_1 ===> samba423-4.23.8_1 depends on package: lmdb>=0.9.16 - not found ===> Installing existing package /packages/All/lmdb0-0.9.35.pkg Installing lmdb0-0.9.35... Extracting lmdb0-0.9.35: .......... done ===> samba423-4.23.8_1 depends on package: lmdb>=0.9.16 - not found *** Error code 1 Stop. make: stopped making "build-depends" in /xports/net/samba423
OK, a fix for this was apparently committed after I had pulled the source code, so I'll close this bug report. However, that's failing too (for a different reason), so I'll open another. It seems weird, though, and I need sleep, so I'll investigate further later before opening the bug report. Briefly, though: Synth successfully builds it, but after doing so, it deletes the package it just built from the repository because it "failed option check", and more specifically "samba423-4.23.8_1.pkg DOCS is ON but port says it must be OFF". DOCS is among the things I turn off in Synth's equivalent of /etc/make.conf, so it's no surprise that Synth thinks it "must be OFF". But... ... the "weird" part is that in the actual build log, it sure doesn't look like the build *used* Synth's equivalent of /etc/make.conf (I have blatantly obvious comments in that file that show up in the build logs when Synth includes it, and they're not in this build log). That would, if true, explain why "DOCS is ON", but I have never before seen the file *not* be used in the actual build. Especially given that Synth knows it "must be OFF": I have no idea where it would have gotten that idea if not from this file. Anyway, like I said, I need sleep, so I'll investigate further later before adding the new bug report.
... or maybe I won't :P After sleep, I tried just building again. It worked fine. I hadn't updated the source code or anything since the failure, so I guess it was some weird temporary glitch.