<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Thank you.<div><br></div><div>I had all kinds of other issues as well, so I was starting to wonder my MacPorts registry was corrupted</div><div><br></div><div>E.g. clamav-server did not activate because an older <span style="font-family: Menlo; font-size: 11px;">/opt/local/etc/</span><span style="font-family: Menlo; font-size: 11px;">clamd.conf.macports.orig</span> was still there. Or a just installed certbot that on clean quits with an error because certbot is not installed. But iyt may have been macports/sources.conf location confusion or an interrupted update..</div><div><div><div><br></div><div>Anyway, is there a way to rebuild the registry (without losing all my configs in /opt/local/etc and elsewhere)? Just in case it is corrupted?</div><div><br></div><div>Gerben Wierda (<a href="https://www.linkedin.com/in/gerbenwierda">LinkedIn</a>, <a href="https://newsie.social/@gctwnl">Mastodon</a>)<br><a href="https://ea.rna.nl/">R&A IT Strategy</a> (main site)<br>Book: <a href="https://ea.rna.nl/the-book/">Chess and the Art of Enterprise Architecture</a><br>Book: <a href="https://ea.rna.nl/the-book-edition-iii/">Mastering ArchiMate</a></div><div><a href="http://www.youtube.com/@GerbenWierda">YouTube Channel</a></div>
</div>
<div><br><blockquote type="cite"><div>On 22 May 2024, at 23:45, Ryan Schmidt <ryandesign@macports.org> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="auto"><div dir="ltr"></div><div dir="ltr">On May 22, 2024, at 16:25, Gerben Wierda wrote:</div><div dir="ltr"><blockquote type="cite"><br></blockquote></div><blockquote type="cite"><div dir="ltr">I was able to circumvent this autoconf failure by installing gettext before installing dovecot, I don't know if that is the best solution, but ot works (as in, it now installs).</div></blockquote><br><div>Yes that is the solution and I committed it here:</div><div><br></div><div><a href="https://github.com/macports/macports-ports/commit/8addb4df7ea4e8da28e059e28052f68b8bad02cb">https://github.com/macports/macports-ports/commit/8addb4df7ea4e8da28e059e28052f68b8bad02cb</a></div><div><br></div><div>Only when you use the +apns variant, dovecot regenerates the configure script from configure.ac (because it applies a patch to configure.ac). configure.ac references the AM_ICONV macro so the port that provides that macro must be present at build time. From its name it seems like the AM_ICONV macro should be provided by the libiconv port but for whatever reason it's actually provided by the gettext port.</div></div></div></blockquote></div><br></div></div></div></div></div></body></html>