From Newsgroup: muc.lists.freebsd.ports

I see a few entries on the dovecot mail list where people are working with dovecot 2.4. I see an entry in the web port/package list for dovecot24 which I presume is the proper item. However, pkg will not find it on amd64 or arch64 using either current or latest. Am I doing something wrong?
-- Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Hi!

I see a few entries on the dovecot mail list where people are
working with dovecot 2.4. I see an entry in the web port/package
list for dovecot24 which I presume is the proper item. However,
pkg will not find it on amd64 or arch64 using either current or
latest. Am I doing something wrong?

I think because of some pkg-plist problem this does not yet build
on the package cluster.

@work, but slowly...
--
pi@FreeBSD.org +49 171 3101372 Now what ?


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Tue, 25 Aug 2026 09:47:48 +0200, Doug Hardie wrote:

I see a few entries on the dovecot mail list where people are
working with dovecot 2.4. I see an entry in the web port/package
list for dovecot24 which I presume is the proper item. However, pkg
will not find it on amd64 or arch64 using either current or latest.
Am I doing something wrong?

% pkg search dovecot24
dovecot24-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-cdb-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-ldap-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-mysql-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-pgsql-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-sqlite3-2.4.4 Secure, fast and powerful IMAP and POP3 server

But dovecot24-pigeonhole was still not added.


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Aug 25, 2026, at 00:52, Kurt Jaeger <pi@freebsd.org> wrote:

N++Hi!

I see a few entries on the dovecot mail list where people are
working with dovecot 2.4. I see an entry in the web port/package
list for dovecot24 which I presume is the proper item. However,
pkg will not find it on amd64 or arch64 using either current or
latest. Am I doing something wrong?

I think because of some pkg-plist problem this does not yet build
on the package cluster.

@work, but slowly...

Thanks. For once itrCOs not something I did wrong
rCo Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Aug 25, 2026, at 00:55, Herbert J. Skuhra <herbert@gojira.at> wrote:

On Tue, 25 Aug 2026 09:47:48 +0200, Doug Hardie wrote:

I see a few entries on the dovecot mail list where people are
working with dovecot 2.4. I see an entry in the web port/package
list for dovecot24 which I presume is the proper item. However, pkg
will not find it on amd64 or arch64 using either current or latest.
Am I doing something wrong?

% pkg search dovecot24
dovecot24-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-cdb-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-ldap-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-mysql-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-pgsql-2.4.4 Secure, fast and powerful IMAP and POP3 server dovecot24-sqlite3-2.4.4 Secure, fast and powerful IMAP and POP3 server

But dovecot24-pigeonhole was still not added.

All of my systems yield:
test# pkg search dovecot24
test#
-- Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 8/25/26 00:47, Doug Hardie wrote:

I see a few entries on the dovecot mail list where people are working with dovecot 2.4. I see an entry in the web port/package list for dovecot24 which I presume is the proper item. However, pkg will not find it on amd64 or arch64 using either current or latest. Am I doing something wrong?

-- Doug

For each of amd64 vs. aarch64 (a.k.a. arm64):

packages built for: main [so: 16] vs. 15.0 vs. 14.4 ?
packages built for: latest (a.k.a. default) vs. quarterly?

Different combinations need not get the same build result for every
build. (Plus such builds and distributions need not be in the same time
frames for the same ports tree vintage.)
--
===
Mark Millard
marklmi at yahoo.com


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Kurt Jaeger <pi@freebsd.org> wrote:

I see a few entries on the dovecot mail list where people are
working with dovecot 2.4. I see an entry in the web port/package
list for dovecot24 which I presume is the proper item. However,
pkg will not find it on amd64 or arch64 using either current or
latest. Am I doing something wrong?

I think because of some pkg-plist problem this does not yet build
on the package cluster.

Both mail/dovecot24 and mail/dovecot24-pigeonhole are fixed and ready to become committed.
Same status for the mail/dovecot24-wormhole port.
I am using these three ports for some weeks now, successfully.

@work, but slowlyrCa

True.
Regards,
Michael
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 2026-08-25 9:51, Doug Hardie wrote:

All of my systems yield:

test# pkg search dovecot24 > test#

quarterly or latest? dovecot24 landed after 2026Q3


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Aug 25, 2026, at 13:17, Jordan M <freebsdlists@montesse.ca> wrote:

N++On 2026-08-25 9:51, Doug Hardie wrote:

All of my systems yield:
test# pkg search dovecot24 > test#

quarterly or latest? dovecot24 landed after 2026Q3

Same results for both
rCo Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Aug 25, 2026, at 13:13, Jordan M <freebsdlists@montesse.ca> wrote:

On 2026-08-25 9:51, Doug Hardie wrote:

All of my systems yield:
test# pkg search dovecot24 > test#

quarterly or latest? dovecot24 landed after 2026Q3

Tonight dovecot24 showed up in pkg. This is on a Raspberry 5 and I think it is using quarterly.
-- Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Dovecot24 has been in the latest packages for awhile. I have it up and running on a test system. However, before I can move it onto the production mail server, it needs to have pigeonhole working. Is there any prognosis when pigeonhole might be available in packages?
-- Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Doug Hardie <bc979@lafn.org> wrote:

Dovecot24 has been in the latest packages for awhile. I have it up and running on a test system. However, before I can move it onto the production mail server, it needs to have pigeonhole working. Is there any prognosis when pigeonhole might be available in packages?

Actually there are two ports ready and waiting for becoming committed: mail/dovecot24-pigeonhole: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298046 mail/dovecot24-wormhole: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703
I really don't know what the reasons are that both ports ain't become committed, yet.
I am using both ports for a couple of weeks now, without any issues rCa Regards,
Michael
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Sep 5, 2026, at 12:55, Michael Grimm <trashcan@ellael.org> wrote:

Doug Hardie <bc979@lafn.org> wrote:

Dovecot24 has been in the latest packages for awhile. I have it up and running on a test system. However, before I can move it onto the production mail server, it needs to have pigeonhole working. Is there any prognosis when pigeonhole might be available in packages?

Actually there are two ports ready and waiting for becoming committed:

mail/dovecot24-pigeonhole: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298046

mail/dovecot24-wormhole: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703

I really don't know what the reasons are that both ports ain't become committed, yet.

I am using both ports for a couple of weeks now, without any issues rCa

I created the port files using those from bug 298046. However, make failed with a few errors:

dovecot24-pigeonhole-2.4.5 depends on file: /usr/local/lib/libcrypto.so.50 - not found
libressl-3.6.2 depends on package: pkgconf>=1.3.0_1 - not found
libressl-3.6.2 depends on package: pkgconf>=1.3.0_1 - not found

I didn't expect that libressl would be required or that /usr/local/lib/libcrypto.so.50 would be needed. I am running on FreeBSD 15.1 and /usr/local/lib/libcrypto.so.57 is the current version.
libressl is at version 4.3.2
Found a later patch. Trying that. Different errors:

dovecot24-pigeonhole-2.4.5 depends on package: dovecot24>=2.4.5 - not found

Error a dependency refers to a non existing origin: /usr/ports/mail/dovecot24 in BUILD_DEPENDS

dovecot24-pigeonhole-2.4.5 depends on package: pkgconf>=1.3.0_1 - not found
dovecot24-pigeonhole-2.4.5 depends on package: pkgconf>=1.3.0_1 - not found

dovecot2.4.5 is not available as a package yet.
pkgconf is at 3.0.5,1
I can force these to the available versions, but will that work?
-- Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Sep 5, 2026, at 15:54, Doug Hardie <bc979@lafn.org> wrote:

On Sep 5, 2026, at 12:55, Michael Grimm <trashcan@ellael.org> wrote:

Doug Hardie <bc979@lafn.org> wrote:

Dovecot24 has been in the latest packages for awhile. I have it up and running on a test system. However, before I can move it onto the production mail server, it needs to have pigeonhole working. Is there any prognosis when pigeonhole might be available in packages?

Actually there are two ports ready and waiting for becoming committed:

mail/dovecot24-pigeonhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298046

mail/dovecot24-wormhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703

I really don't know what the reasons are that both ports ain't become committed, yet.

I am using both ports for a couple of weeks now, without any issues rCa

I tried pkg upgrade today and dovecot2.4.5 showed up. Completed the upgrade and then did another make. Got lots farther along before the following error:
libtool: compile: cc -DPACKAGE_NAME=\"libressl\" -DPACKAGE_TARNAME=\"libressl\" -DPACKAGE_VERSION=\"3.6.2\" "-DPACKAGE_STRING=\"libressl 3.6.2\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libressl\" -DVERSION=\"3.6.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_TIME_T=8 -DHAVE_SYMLINK=1 -DHAVE_ENDIAN_H=1 -DHAVE_MACHINE_ENDIAN_H=1 -DHAVE_ERR_H=1 -DHAVE_READPASSPHRASE_H=1 -DHAVE_NETINET_IP_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_ARPA_NAMESER_H=1 -DHAVE_NETDB_H=1 -DHAVE_RESOLV_H=1 -DHAVE_ASPRINTF=1 -DHAVE_MEMMEM=1 -DHAVE_READPASSPHRASE=1 -DHAVE_REALLOCARRAY=1 -DHAVE_RECALLOCARRAY=1 -DHAVE_STRLCAT=1 -DHAVE_STRLCPY=1 -DHAVE_STRNDUP=1 -DHAVE_STRNLEN=1 -DHAVE_STRSEP=1 -DHAVE_STRTONUM=1 -DHAVE_TIMEGM=1 -DHAVE_GETPROGNAME=1 -DHAVE_SYSLOG=1 -DHAVE_ACCEPT4=1 -DHAVE_PIPE2=1 -DHAVE_POLL=1 -DHAVE_SOCKETPAIR=1 -DHAVE_ARC4RANDOM=1 -DHAVE_ARC4RANDOM_BUF=1 -DHAVE_ARC4RANDOM_UNIFORM=1 -DHAVE_EXPLICIT_BZERO=1 -DHAVE_TIMINGSAFE_BCMP=1 -DHAVE_TIMINGSAFE_MEMCMP=1 -DHAVE_DL_ITERATE_PHDR=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DHAS_GNU_WARNING_LONG=1 -I. -I../include -I../include/compat -DLIBRESSL_INTERNAL -D__BEGIN_HIDDEN_DECLS= -D__END_HIDDEN_DECLS= -DLIBRESSL_CRYPTO_INTERNAL -I../crypto/asn1 -I../crypto/bio -I../crypto/bn -I../crypto/bytestring -I../crypto/dh -I../crypto/dsa -I../crypto/ec -I../crypto/ecdh -I../crypto/ecdsa -I../crypto/evp -I../crypto/hmac -I../crypto/modes -I../crypto/ocsp -I../crypto/pkcs12 -I../crypto/rsa -I../crypto/x509 -I../crypto -D_FORTIFY_SOURCE=2 -O2 -pipe -fpic -DPIC -Wl,-rpath,/usr/local/lib -Wl,--as-needed -fstack-protector-strong -fno-strict-aliasing -Wall -std=gnu99 -fno-strict-aliasing -fno-strict-overflow -fstack-protector-strong -DHAVE_GNU_STACK -Qunused-arguments -Wno-pointer-sign -MT compat/arc4random.lo -MD -MP -MF compat/.deps/arc4random.Tpo -c compat/arc4random.c -fPIC -DPIC -o compat/.libs/arc4random.o
compat/arc4random.c:197:1: error: redefinition of 'arc4random_buf'
197 | arc4random_buf(void *buf, size_t n)
| ^
/usr/include/ssp/stdlib.h:38:22: note: previous definition is here
38 | __ssp_redirect(void, arc4random_buf, (void *__buf, size_t __len),
| ^
1 error generated.
I don't see how that is a redefinition.
I tried with MAKE_JOBS_UNSAFE=yes but it made no difference.
-- Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Sun, 06 Sep 2026 04:24:20 +0200, Doug Hardie <bc979@lafn.org> wrote:

On Sep 5, 2026, at 15:54, Doug Hardie <bc979@lafn.org> wrote:

On Sep 5, 2026, at 12:55, Michael Grimm <trashcan@ellael.org> wrote:

Doug Hardie <bc979@lafn.org> wrote:

Dovecot24 has been in the latest packages for awhile. I have it
up and running on a test system. However, before I can move it
onto the production mail server, it needs to have pigeonhole
working. Is there any prognosis when pigeonhole might be
available in packages?

Actually there are two ports ready and waiting for becoming committed:

mail/dovecot24-pigeonhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298046

mail/dovecot24-wormhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703

I really don't know what the reasons are that both ports ain't become committed, yet.

I am using both ports for a couple of weeks now, without any issues $B!D(B

I tried pkg upgrade today and dovecot2.4.5 showed up. Completed the upgrade and then did another make. Got lots farther along before the following error:

libtool: compile: cc -DPACKAGE_NAME=\"libressl\"

-DPACKAGE_TARNAME=\"libressl\" -DPACKAGE_VERSION=\"3.6.2\" "-DPACKAGE_STRING=\"libressl 3.6.2\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libressl\" -DVERSION=\"3.6.2\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\"
-DSIZEOF_TIME_T=8 -DHAVE_SYMLINK=1 -DHAVE_ENDIAN_H=1
-DHAVE_MACHINE_ENDIAN_H=1 -DHAVE_ERR_H=1 -DHAVE_READPASSPHRASE_H=1 -DHAVE_NETINET_IP_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_ARPA_NAMESER_H=1 -DHAVE_NETDB_H=1 -DHAVE_RESOLV_H=1
-DHAVE_ASPRINTF=1 -DHAVE_MEMMEM=1 -DHAVE_READPASSPHRASE=1
-DHAVE_REALLOCARRAY=1 -DHAVE_RECALLOCARRAY=1 -DHAVE_STRLCAT=1
-DHAVE_STRLCPY=1 -DHAVE_STRNDUP=1 -DHAVE_STRNLEN=1 -DHAVE_STRSEP=1 -DHAVE_STRTONUM=1 -DHAVE_TIMEGM=1 -DHAVE_GETPROGNAME=1 -DHAVE_SYSLOG=1 -DHAVE_ACCEPT4=1 -DHAVE_PIPE2=1 -DHAVE_POLL=1 -DHAVE_SOCKETPAIR=1 -DHAVE_ARC4RANDOM=1 -DHAVE_ARC4RANDOM_BUF=1 -DHAVE_ARC4RANDOM_UNIFORM=1 -DHAVE_EXPLICIT_BZERO=1 -DHAVE_TIMINGSAFE_BCMP=1
-DHAVE_TIMINGSAFE_MEMCMP=1 -DHAVE_DL_ITERATE_PHDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DHAS_GNU_WARNING_LONG=1 -I. -I../include -I../include/compat -DLIBRESSL_INTERNAL -D__BEGIN_HIDDEN_DECLS= -D__END_HIDDEN_DECLS= -DLIBRESSL_CRYPTO_INTERNAL -I../crypto/asn1 -I../crypto/bio
-I../crypto/bn -I../crypto/bytestring -I../crypto/dh -I../crypto/dsa -I../crypto/ec -I../crypto/ecdh -I../crypto/ecdsa -I../crypto/evp -I../crypto/hmac -I../crypto/modes -I../crypto/ocsp -I../crypto/pkcs12 -I../crypto/rsa -I../crypto/x509 -I../crypto -D_FORTIFY_SOURCE=2 -O2
-pipe -fpic -DPIC -Wl,-rpath,/usr/local/lib -Wl,--as-needed -fstack-protector-strong -fno-strict-aliasing -Wall -std=gnu99 -fno-strict-aliasing -fno-strict-overflow -fstack-protector-strong -DHAVE_GNU_STACK -Qunused-arguments -Wno-pointer-sign -MT
compat/arc4random.lo -MD -MP -MF compat/.deps/arc4random.Tpo -c compat/arc4random.c -fPIC -DPIC -o compat/.libs/arc4random.o

compat/arc4random.c:197:1: error: redefinition of 'arc4random_buf'
197 | arc4random_buf(void *buf, size_t n)
| ^
/usr/include/ssp/stdlib.h:38:22: note: previous definition is here
38 | __ssp_redirect(void, arc4random_buf, (void *__buf, size_t __len),
| ^
1 error generated.

I don't see how that is a redefinition.
I tried with MAKE_JOBS_UNSAFE=yes but it made no difference.

1. Do you use ssl=libressl (DEFAULT_VERSIONS in /etc/make.conf)? The
dovecot24 packages are built with openssl (from base).

2. When did you last update /usr/ports? libressl 3.6.2 is from March
18th, 2023. The current version in ports is 4.3.2.



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Sep 6, 2026, at 00:35, Herbert J. Skuhra <herbert@gojira.at> wrote:

On Sun, 06 Sep 2026 04:24:20 +0200, Doug Hardie <bc979@lafn.org> wrote:

On Sep 5, 2026, at 15:54, Doug Hardie <bc979@lafn.org> wrote:

On Sep 5, 2026, at 12:55, Michael Grimm <trashcan@ellael.org> wrote:

Doug Hardie <bc979@lafn.org> wrote:

Dovecot24 has been in the latest packages for awhile. I have it
up and running on a test system. However, before I can move it
onto the production mail server, it needs to have pigeonhole
working. Is there any prognosis when pigeonhole might be
available in packages?

Actually there are two ports ready and waiting for becoming committed: >>>>
mail/dovecot24-pigeonhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298046

mail/dovecot24-wormhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703

I really don't know what the reasons are that both ports ain't become committed, yet.

I am using both ports for a couple of weeks now, without any issues rCa

I tried pkg upgrade today and dovecot2.4.5 showed up. Completed the upgrade and then did another make. Got lots farther along before the following error:

libtool: compile: cc -DPACKAGE_NAME=\"libressl\"

-DPACKAGE_TARNAME=\"libressl\" -DPACKAGE_VERSION=\"3.6.2\" "-DPACKAGE_STRING=\"libressl 3.6.2\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libressl\" -DVERSION=\"3.6.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\"
-DSIZEOF_TIME_T=8 -DHAVE_SYMLINK=1 -DHAVE_ENDIAN_H=1 -DHAVE_MACHINE_ENDIAN_H=1 -DHAVE_ERR_H=1 -DHAVE_READPASSPHRASE_H=1> -DHAVE_NETINET_IP_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_NETINET_IN_H=1
-DHAVE_ARPA_NAMESER_H=1 -DHAVE_NETDB_H=1 -DHAVE_RESOLV_H=1
-DHAVE_ASPRINTF=1 -DHAVE_MEMMEM=1 -DHAVE_READPASSPHRASE=1 -DHAVE_REALLOCARRAY=1 -DHAVE_RECALLOCARRAY=1 -DHAVE_STRLCAT=1 -DHAVE_STRLCPY=1 -DHAVE_STRNDUP=1 -DHAVE_STRNLEN=1 -DHAVE_STRSEP=1 -DHAVE_STRTONUM=1 -DHAVE_TIMEGM=1 -DHAVE_GETPROGNAME=1 -DHAVE_SYSLOG=1 -DHAVE_ACCEPT4=1 -DHAVE_PIPE2=1 -DHAVE_POLL=1 -DHAVE_SOCKETPAIR=1 -DHAVE_ARC4RANDOM=1 -DHAVE_ARC4RANDOM_BUF=1 -DHAVE_ARC4RANDOM_UNIFORM=1 -DHAVE_EXPLICIT_BZERO=1 -DHAVE_TIMINGSAFE_BCMP=1
-DHAVE_TIMINGSAFE_MEMCMP=1 -DHAVE_DL_ITERATE_PHDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DHAS_GNU_WARNING_LONG=1 -I. -I../include -I../include/compat -DLIBRESSL_INTERNAL -D__BEGIN_HIDDEN_DECLS= -D__END_HIDDEN_DECLS= -DLIBRESSL_CRYPTO_INTERNAL -I../crypto/asn1 -I../crypto/bio
-I../crypto/bn -I../crypto/bytestring -I../crypto/dh -I../crypto/dsa -I../crypto/ec -I../crypto/ecdh -I../crypto/ecdsa -I../crypto/evp -I../crypto/hmac -I../crypto/modes -I../crypto/ocsp -I../crypto/pkcs12 -I../crypto/rsa -I../crypto/x509 -I../crypto -D_FORTIFY_SOURCE=2 -O2
-pipe -fpic -DPIC -Wl,-rpath,/usr/local/lib -Wl,--as-needed -fstack-protector-strong -fno-strict-aliasing -Wall -std=gnu99 -fno-strict-aliasing -fno-strict-overflow -fstack-protector-strong -DHAVE_GNU_STACK -Qunused-arguments -Wno-pointer-sign -MT compat/arc4random.lo -MD -MP -MF compat/.deps/arc4random.Tpo -c compat/arc4random.c -fPIC -DPIC -o compat/.libs/arc4random.o

compat/arc4random.c:197:1: error: redefinition of 'arc4random_buf'
197 | arc4random_buf(void *buf, size_t n)
| ^
/usr/include/ssp/stdlib.h:38:22: note: previous definition is here
38 | __ssp_redirect(void, arc4random_buf, (void *__buf, size_t __len),
| ^
1 error generated.


I don't see how that is a redefinition.
I tried with MAKE_JOBS_UNSAFE=yes but it made no difference.

1. Do you use ssl=libressl (DEFAULT_VERSIONS in /etc/make.conf)? The dovecot24 packages are built with openssl (from base).

2. When did you last update /usr/ports? libressl 3.6.2 is from March
18th, 2023. The current version in ports is 4.3.2.

None of my systems have a file /etc/make.conf. It looks like the ports were updated on May 21 2023. I'll try updating them tomorrow and run again.
-- Doug
jj--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Hi!

mail/dovecot24-wormhole: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703

I really don't know what the reasons are that both ports ain't become committed, yet.

No committer found the time, myself included.
--
pi@FreeBSD.org +49 171 3101372 Now what ?


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Sep 6, 2026, at 01:19, Doug Hardie <bc979@lafn.org> wrote:

On Sep 6, 2026, at 00:35, Herbert J. Skuhra <herbert@gojira.at> wrote:


1. Do you use ssl=libressl (DEFAULT_VERSIONS in /etc/make.conf)? The
dovecot24 packages are built with openssl (from base).

2. When did you last update /usr/ports? libressl 3.6.2 is from March
18th, 2023. The current version in ports is 4.3.2.

None of my systems have a file /etc/make.conf. It looks like the ports were updated on May 21 2023. I'll try updating them tomorrow and run again.

I updated /usr/ports and did another make. (removed the work* directory first). The build went fine with no errors. However, install failed:

Installing for dovecot24-pigeonhole-2.4.5
Checking if dovecot24-pigeonhole is already installed
Registering installation for dovecot24-pigeonhole-2.4.5

pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/in/sieve-filter:No such file or directory
pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/in/sieve-test:No such file or directory
pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/in/sievec:No such file or directory
pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/nclude/dovecot/sieve/edit-mail.h:No such file or directory
pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/nclude/dovecot/sieve/mail-raw.h:No such file or directory
pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/nclude/dovecot/sieve/pigeonhole-config.h:No such file or directory
pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/nclude/dovecot/sieve/pigeonhole-version.h:No such file or directory
pkg-static: Unable to access file /usr/ports/mail/dovecot24-pigeonhole/work-default/stage/usr/local/nclude/dovecot/sieve/rfc2822.h:No such file or directory
*** Error code 1
Note that the first letter of the directory name after local is missing. in for bin and nclude for include. A quick check did not find the location in the Makefiles where that happened. Will try again later today. I am presuming that all the various files in stage/usr/local need to be installed.
-- Doug
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Kurt Jaeger <pi@freebsd.org> wrote:

mail/dovecot24-wormhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703

I really don't know what the reasons are that both ports ain't become committed, yet.

No committer found the time, myself included.

Sorry, but I haven't had committers in mind as the only reason. I have had also in mind what contributors to those PR might have missed to deliver.
Regards,
Michael--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 9/6/26 13:57, Michael Grimm wrote:

Kurt Jaeger <pi@freebsd.org> wrote:

mail/dovecot24-wormhole:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297703

I really don't know what the reasons are that both ports ain't become committed, yet.

No committer found the time, myself included.

Sorry, but I haven't had committers in mind as the only reason. I have had also in mind what contributors to those PR might have missed to deliver.

Committers are likely the ones that check the sufficiency of the PR
materials. If they start to handle the PR but notice some problem with
the materials, they likely would explicitly ask for the issue to be fixed.

Regards,
Michael

--
===
Mark Millard
marklmi at yahoo.com


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2