Re: security/openvpn-auth-ldap-2.0.4 not compatible with security/openvpn-2.5.0
> Updating how? From ports by portmaster. > This suggests you need to update/rebuild lang/libobjc2 dependency as well. After rebuilding lang/libobjc2, openvpn works. Thank you. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openvpn-auth-ldap-2.0.4 not compatible with security/openvpn-2.5.0
Am 06.11.20 um 07:10 schrieb xtouqh--- via freebsd-ports: Nikita Druba wrote: Hello! After updating security/openvpn to last(2.5.0) version, it's not start anymore, because: Updating how? "2020-11-06 02:37:05 PLUGIN_INIT: could not load plugin shared object /usr/local/lib/openvpn-auth-ldap.so: /usr/local/lib/libobjc.so.4.6: Undefined symbol "ceilf" This suggests you need to update/rebuild lang/libobjc2 dependency as well. Does that mean that the PORTREVISION of lang/libobjc2 has to be bumped? Seems this is a port maintained by ports@ and nobody feels responsible? OpenPGP_signature Description: OpenPGP digital signature
Re: security/openvpn-auth-ldap-2.0.4 not compatible with security/openvpn-2.5.0
Does that mean that the PORTREVISION of lang/libobjc2 has to be bumped? Yes, this step can help. Seems this is a port maintained by ports@ and nobody feels responsible? Looks like. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: pgbarman-2.11
On 06/11/2020 20:17, Ryan Quinn wrote: > Hi Matthew! > > Would it be possible to get barman to support multiple versions of postgres? > > Here’s the background. > > I’m testing barman as a backup solution, and I upgraded barman to version > 2.11 on my test system. I wasn’t paying attention, so this is totally my > fault. Anyway, the barman 2.11 dependency on postgresql12-client caused > postgres 11 to be removed. > > Ryan > In theory, yes. That's a job for flavours. Unfortunately, for reasons that I cannot recall clearly just now, we don't have any postgresql flavour support in ports. As far as I recall, it might have been concern about the number of ports increasing beyond what the builders could handle in a reasonable time. If you build your own packages, then it's easy enough to add 'pgsql=11' to your DEFAULT_VERSIONS setting. Or, if adverse to compiling stuff, you could run the default barman package in a jail to do a "remote" backup of your main postgresql installation. barman when linked against the most recent version of libpq can work with any of the older versions of postgresql in the ports. Cheers, Matthew ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ math/cocoalib | 0.99710 | 0.99711 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
