WARNING: devel/icu: recent update redners openldap-server and other ports unusable!
Chris Rees
crees at bayofrum.net
Sat Feb 8 15:36:43 UTC 2014
Shane Ambler <FreeBSD at ShaneWare.Biz> wrote:
>On 08/02/2014 08:24, O. Hartmann wrote:
>>
>> Today a couple of updates has been introduced, one of them was an
>> update of port devel/icu.
>>
>> I the good manner/tradition of updating UPDATING, I expect a
>> warning/hint/advice a couple of days from now - when everybody has
>> already stepped into the mess.
>>
>> On several boxes running 11.0-CURRENT and 9.2-STABLE, updating ports
>> including devel/icu renders many ports unusable due to a library
>> version bump in libicu.
>>
>> After updating ports relying on devel/icu via
>>
>> portmaster -r devel/icu
>>
>> and the updating of port
>>
>> net/openldap24-server
>>
>> (which is openldap-sasl-server in my case), OpenLDAP doesn't start
>> anymore on all boxes affected by the update of devel/icu!
>>
>> I always get the error
>>
>> 52f5551f hdb_db_init: Initializing HDB database
>> 52f5551f olcDbDirectory: value #0: invalid path: Permission denied
>> 52f5551f config error processing olcDatabase={1}hdb,cn=config:
>> olcDbDirectory: value #0: invalid path: Permission denied 52f5551f
>> send_ldap_result: conn=-1 op=0 p=0 52f5551f slapd destroy: freeing
>> system resources. 52f5551f syncinfo_free: rid=001
>> 52f5551f slapd stopped.
>> 52f5551f connections_destroy: nothing to destroy.
>> /usr/local/etc/rc.d/slapd: WARNING: failed to start slapd
>>
>>
>> This obscure
>>
>> olcDbDirectory: value #0: invalid path: Permission denied
>>
>> is not obvious to me. The server ran minutes ago BEFORE the update,
>the
>> directories containing the DB5 databases have all the correct
>ownership
>> (ldap:ldap, I suspected first a misconfiguration as this error seems
>> typical for a misconfiguration of the ownership).
>>
>> Does anyone see the same problem? And maybe please would put out some
>> notes in UPDATING within a considerable narrow timeframe regarding
>> devel/icu! It seems, FreeBSD's ports systems get more and more messy.
>>
>> oh
>>
>
>Not the same problem but I did see building postgresql server break -
>I changed databases/postgresql92-server/makefile with the following.
>Ideally the test for *_52 should be added to configure.in rather than
>replacing the oldest.
>
>--- a/databases/postgresql92-server/Makefile
>+++ b/databases/postgresql92-server/Makefile
>@@ -355,6 +355,8 @@ post-patch:
> . if defined(SERVER_ONLY) && ${PORT_OPTIONS:MICU}
> @${REINPLACE_CMD} -E -e \
> "s|^(m4_if.*)2.6[0-9](.*Autoconf version
>)2.6[0-9]|\1${AUTOCONF_VERSION}\2${AUTOCONF_VERSION}|g" \
>+ -e "s|ucol_open_43|ucol_open_52|g" \
>+ -e "s|ucnv_fromUChars_43|ucnv_fromUChars_52|g" \
> ${WRKSRC}/configure.in
> . endif
Hmm, the ICU support was written by Palle, hence we are the upstream for it.
Palle, do you think this is a good fix?
Thanks Shane, by the way :)
Chris
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the freebsd-ports
mailing list