Re: Fix: My dovecot install fails after macOS Sonoma 14.5 update and MacPorts update

2024-05-22 Thread Ryan Schmidt
On May 22, 2024, at 16:25, Gerben Wierda wrote:
> 
> 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).

Yes that is the solution and I committed it here:

https://github.com/macports/macports-ports/commit/8addb4df7ea4e8da28e059e28052f68b8bad02cb

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.

Fix: My dovecot install fails after macOS Sonoma 14.5 update and MacPorts update

2024-05-22 Thread Gerben Wierda
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).

Gerben Wierda (LinkedIn , Mastodon 
)
R IT Strategy  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 
YouTube Channel 

> On 22 May 2024, at 22:43, Gerben Wierda  wrote:
> 
> I did my normal upgrade round, that is, update macOS, then a clean update of 
> MacPorts and a reinstall of my port collection. This is generally routine for 
> me.
> 
> But this now fails at dovecot (which is nasty,. I really need that mail 
> server, now running on the Linux backup server)
> 
> port -N install dovecot +apns +solr
> --->  Configuring dovecot
> Error: Failed to configure dovecot: autoreconf failure: command execution 
> failed
> Error: See 
> /opt/local/var/macports/logs/_Users_sysbh_MacPortsDev_macports-ports_mail_dovecot/dovecot/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets if you believe 
> there is a bug.
> Error: Processing of port dovecot failed
> 
> and the log ends with
> 
> :info:configure ./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
> :info:configure lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from...
> :info:configure lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
> :info:configure ./lib/autoconf/libs.m4:100: AC_CHECK_LIB is expanded from...
> :info:configure m4/want_stemmer.m4:1: DOVECOT_WANT_STEMMER is expanded from...
> :info:configure configure.ac:762: the top level
> :info:configure configure.ac:763: warning: The macro 'AC_ERROR' is obsolete.
> :info:configure configure.ac:763: You should run autoupdate.
> :info:configure ./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
> :info:configure m4/want_textcat.m4:1: DOVECOT_WANT_TEXTCAT is expanded from...
> :info:configure configure.ac:763: the top level
> :info:configure configure.ac:765: warning: The macro 'AC_ERROR' is obsolete.
> :info:configure configure.ac:765: You should run autoupdate.
> :info:configure ./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
> :info:configure m4/want_icu.m4:1: DOVECOT_WANT_ICU is expanded from...
> :info:configure configure.ac:765: the top level
> :info:configure configure.ac:285: error: possibly undefined macro: AM_ICONV
> :info:configure   If this token and others are legitimate, please use 
> m4_pattern_allow.
> :info:configure   See the Autoconf documentation.
> :info:configure autoreconf: error: /opt/local/bin/autoconf failed with exit 
> status: 1
> :info:configure Command failed:  cd 
> "/opt/local/var/macports/build/_Users_sysbh_MacPortsDev_macports-ports_mail_dovecot/dovecot/work/dovecot-2.3.21"
>  && autoreconf -fvi 
> :info:configure Exit code: 1
> :error:configure Failed to configure dovecot: autoreconf failure: command 
> execution failed
> :debug:configure Error code: NONE
> :debug:configure Backtrace: autoreconf failure: command execution failed
> :debug:configure while executing
> :debug:configure "$procedure $targetname"
> :error:configure See 
> /opt/local/var/macports/logs/_Users_sysbh_MacPortsDev_macports-ports_mail_dovecot/dovecot/main.log
>  for details.
> 
> 
> 
> Gerben Wierda (LinkedIn , Mastodon 
> )
> R IT Strategy  (main site)
> Book: Chess and the Art of Enterprise Architecture 
> 
> Book: Mastering ArchiMate 
> YouTube Channel 



My dovecot install fails after macOS Sonoma 14.5 update and MacPorts update

2024-05-22 Thread Gerben Wierda
I did my normal upgrade round, that is, update macOS, then a clean update of 
MacPorts and a reinstall of my port collection. This is generally routine for 
me.

But this now fails at dovecot (which is nasty,. I really need that mail server, 
now running on the Linux backup server)

port -N install dovecot +apns +solr
--->  Configuring dovecot
Error: Failed to configure dovecot: autoreconf failure: command execution failed
Error: See 
/opt/local/var/macports/logs/_Users_sysbh_MacPortsDev_macports-ports_mail_dovecot/dovecot/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there 
is a bug.
Error: Processing of port dovecot failed

and the log ends with

:info:configure ./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
:info:configure lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from...
:info:configure lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
:info:configure ./lib/autoconf/libs.m4:100: AC_CHECK_LIB is expanded from...
:info:configure m4/want_stemmer.m4:1: DOVECOT_WANT_STEMMER is expanded from...
:info:configure configure.ac:762: the top level
:info:configure configure.ac:763: warning: The macro 'AC_ERROR' is obsolete.
:info:configure configure.ac:763: You should run autoupdate.
:info:configure ./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
:info:configure m4/want_textcat.m4:1: DOVECOT_WANT_TEXTCAT is expanded from...
:info:configure configure.ac:763: the top level
:info:configure configure.ac:765: warning: The macro 'AC_ERROR' is obsolete.
:info:configure configure.ac:765: You should run autoupdate.
:info:configure ./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
:info:configure m4/want_icu.m4:1: DOVECOT_WANT_ICU is expanded from...
:info:configure configure.ac:765: the top level
:info:configure configure.ac:285: error: possibly undefined macro: AM_ICONV
:info:configure   If this token and others are legitimate, please use 
m4_pattern_allow.
:info:configure   See the Autoconf documentation.
:info:configure autoreconf: error: /opt/local/bin/autoconf failed with exit 
status: 1
:info:configure Command failed:  cd 
"/opt/local/var/macports/build/_Users_sysbh_MacPortsDev_macports-ports_mail_dovecot/dovecot/work/dovecot-2.3.21"
 && autoreconf -fvi 
:info:configure Exit code: 1
:error:configure Failed to configure dovecot: autoreconf failure: command 
execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: autoreconf failure: command execution failed
:debug:configure while executing
:debug:configure "$procedure $targetname"
:error:configure See 
/opt/local/var/macports/logs/_Users_sysbh_MacPortsDev_macports-ports_mail_dovecot/dovecot/main.log
 for details.



Gerben Wierda (LinkedIn , Mastodon 
)
R IT Strategy  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 
YouTube Channel 


Re: new certificates using apple-pki-bundle

2024-05-22 Thread Eric Gallager via macports-users
On Tue, May 21, 2024 at 4:37 AM Riccardo Mottola via macports-users
 wrote:
>
> Hi,
>
> Nils Breunese wrote:
> >> what certificates do you use with apple-pki-bundle? I got those from curl 
> >> (cacert.pem from https://curl.se/docs/caextract.html)
> >> On old Macs in Safari even a simple page like wikipedia is not loadable, I 
> >> thought it is a certificate issue, but it did not help. Firefox has its 
> >> own.
> >> Perhaps it is enforcing SSL 1.3 and I am busted?
> > What version of macOS and Safari are you using? According to sslscan 
> > en.wikipedia.org supports TLS 1.2 and 1.3.
>
> MacOS 10.9 and Safari 9.1.3
>
> I suppose that installed certificates should be available to all apps,
> if I did it right, the new certificates should be available system wide,
> right? Not just macports apps.
> So curl, wget..but also Safari or similar.
>

I think that the `certsync` port (alternative to curl-ca-bundle) is
supposed to help with this...

>
> Riccardo