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 +-+ sysutils/py-google-compute-engine | 2.8.16 | v20191121 +-+ 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"
Re: dns/libidn2 2.3.0 breaks gnutls for samba (was: Samba 4.10.10 can't find gnutls headers on one machine)
On Thu, Nov 21, 2019 at 03:11:28PM EST, Jonathan Chen wrote:
> On Fri, 22 Nov 2019 at 08:46, Morgan Wesström
> wrote:
> [...]
> > I downgraded libidn2 to 2.2.0 and recompiled gnutls and the other
> > packages depending on it and now samba compiles without any problems. I
> > can't say if this is a bug in libidn2, gnutls or samba so I can't file a
> > bug report for it.
>
> It's a symptom of using non-{jailed|chroot} build environments for
> your ports. Using pourdriere or synth is a better alternative.
>
> Cheers.
The same happens inside of pourdriere.
___
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: dns/libidn2 2.3.0 breaks gnutls for samba (was: Samba 4.10.10 can't find gnutls headers on one machine)
On Thu, Nov 21, 2019 at 8:46 PM Morgan Wesström wrote: > > > > On 2019-11-21 16:37, Morgan Wesström wrote: > >> Dear list, > >> > >> I need some help to figure out what I broke on my system. I have two > >> (almost) identical machines, one running 12.1-RELEASE and one waiting > >> to be upgraded and is still on 12.0-RELEASE-p10. Configuration and > >> software wise I try to keep them identical. > > I found the problem. Samba's config.log had the following error: > > err: //usr/local/lib/libidn2.so.0:(.text+0x2290): multiple definition of > `_idn2_punycode_encode@IDN2_0.0.0' > //usr/local/lib/libidn2.so.0:(.text+0x2610): multiple definition of > `_idn2_punycode_decode@IDN2_0.0.0' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > > I tracked this down to a commit made to libidn2 a week ago: > > https://gitlab.com/libidn/libidn2/commit/089616574679a017f5d45c6bd40b05816ae4db6b > > I downgraded libidn2 to 2.2.0 and recompiled gnutls and the other > packages depending on it and now samba compiles without any problems. I > can't say if this is a bug in libidn2, gnutls or samba so I can't file a > bug report for it. Hi, It's a libidn2 bug. Antoine ___ 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: dns/libidn2 2.3.0 breaks gnutls for samba (was: Samba 4.10.10 can't find gnutls headers on one machine)
On Fri, 22 Nov 2019 at 08:46, Morgan Wesström
wrote:
[...]
> I downgraded libidn2 to 2.2.0 and recompiled gnutls and the other
> packages depending on it and now samba compiles without any problems. I
> can't say if this is a bug in libidn2, gnutls or samba so I can't file a
> bug report for it.
It's a symptom of using non-{jailed|chroot} build environments for
your ports. Using pourdriere or synth is a better alternative.
Cheers.
--
Jonathan Chen
___
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"
dns/libidn2 2.3.0 breaks gnutls for samba (was: Samba 4.10.10 can't find gnutls headers on one machine)
On 2019-11-21 16:37, Morgan Wesström wrote: Dear list, I need some help to figure out what I broke on my system. I have two (almost) identical machines, one running 12.1-RELEASE and one waiting to be upgraded and is still on 12.0-RELEASE-p10. Configuration and software wise I try to keep them identical. I found the problem. Samba's config.log had the following error: err: //usr/local/lib/libidn2.so.0:(.text+0x2290): multiple definition of `_idn2_punycode_encode@IDN2_0.0.0' //usr/local/lib/libidn2.so.0:(.text+0x2610): multiple definition of `_idn2_punycode_decode@IDN2_0.0.0' cc: error: linker command failed with exit code 1 (use -v to see invocation) I tracked this down to a commit made to libidn2 a week ago: https://gitlab.com/libidn/libidn2/commit/089616574679a017f5d45c6bd40b05816ae4db6b I downgraded libidn2 to 2.2.0 and recompiled gnutls and the other packages depending on it and now samba compiles without any problems. I can't say if this is a bug in libidn2, gnutls or samba so I can't file a bug report for it. Regards Morgan ___ 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: Samba 4.10.10 can't find gnutls headers on one machine
On 2019-11-21 16:37, Morgan Wesström wrote: Dear list, I need some help to figure out what I broke on my system. I have two (almost) identical machines, one running 12.1-RELEASE and one waiting to be upgraded and is still on 12.0-RELEASE-p10. Configuration and software wise I try to keep them identical. Some additional info that should've been included with my initial post (I apologize for that). I have removed Samba with pkg delete and then run pkg autoremove. Recompiled everything on the machine and the tried to reinstall Samba but it still fails. Both machines actually do find gnutls but complains of some features not found on the broken machine. WORKING MACHINE: Checking for gnutls >= 3.4.7 : yes Checking for library gnutls : yes Checking for header gnutls/gnutls.h : yes Checking for gnutls_global_init : ok Checking for gnutls_certificate_verify_peers3 : ok Checking for header gnutls/x509.h : yes Checking for declaration of GNUTLS_CERT_EXPIRED : no Checking for declaration of GNUTLS_CERT_EXPIRED (as enum) : yes Checking for declaration of GNUTLS_CERT_NOT_ACTIVATED : no Checking for declaration of GNUTLS_CERT_NOT_ACTIVATED (as enum) : yes Checking for declaration of GNUTLS_CERT_UNEXPECTED_OWNER : no Checking for declaration of GNUTLS_CERT_UNEXPECTED_OWNER (as enum) : yes Checking for variable gnutls_x509_crt_set_version : yes Checking for variable gnutls_x509_crt_set_subject_key_id : yes Checking for gnutls_datum : yes Checking for gnutls_datum_t : yes Checking for library gcrypt : yes Checking for header gcrypt.h : yes Checking for gcry_control : ok Checking for library gpg-error : yes Checking for gpg_err_code_from_errno : ok Checking for gnutls_aead_cipher_init : ok BROKEN MACHINE: Checking for gnutls >= 3.4.7 : yes Checking for library gnutls : no Checking for header gnutls/gnutls.h : yes Checking for gnutls_global_init : not found Checking for macro gnutls_global_init : not found Checking for library gnutls : no Checking for gnutls_certificate_verify_peers3 : not found Checking for macro gnutls_certificate_verify_peers3 : not found Checking for header gnutls/x509.h : yes Checking for declaration of GNUTLS_CERT_EXPIRED : no Checking for declaration of GNUTLS_CERT_EXPIRED (as enum) : yes Checking for declaration of GNUTLS_CERT_NOT_ACTIVATED : no Checking for declaration of GNUTLS_CERT_NOT_ACTIVATED (as enum) : yes Checking for declaration of GNUTLS_CERT_UNEXPECTED_OWNER : no Checking for declaration of GNUTLS_CERT_UNEXPECTED_OWNER (as enum) : yes Checking for variable gnutls_x509_crt_set_version : yes Checking for variable gnutls_x509_crt_set_subject_key_id : yes Checking for gnutls_datum : yes Checking for gnutls_datum_t : yes Checking for library gcrypt : yes Checking for header gcrypt.h : yes Checking for gcry_control : ok Checking for library gpg-error : yes Checking for gpg_err_code_from_errno : ok Checking for library gnutls : no Checking for gnutls_aead_cipher_init : not found Checking for macro gnutls_aead_cipher_init : not found No gnutls support for AEAD encryption Compilation then fails after a while: [1384/3559] Linking bin/default/source4/auth/kerberos/libauthkrb5-samba4.so runner ['cc', '-Wl,--version-script=/usr/ports/net/samba410/work/samba-4.10.10/bin/default/source4/auth/kerberos/authkrb5.vscript', '-shared', 'source4/auth/kerberos/krb5_init_contex t.c.1.o', 'source4/lib/tls/tls.c.1.o', 'source4/lib/tls/tlscert.c.1.o', 'source4/lib/tls/tls_tstream.c.1.o', 'auth/kerberos/gssapi_pac.c.1.o', 'auth/kerberos/kerberos_pac.c.1.o', 'au th/kerberos/gssapi_helper.c.1.o', 'source4/lib/stream/packet.c.1.o', 'source4/auth/kerberos/kerberos_pac.c.2.o', '-o/usr/ports/net/samba410/work/samba-4.10.10/bin/default/source4/aut h/kerberos/libauthkrb5-samba4.so', '-Wl,-Bstatic', '-Wl,-Bdynamic', '-L/usr/ports/net/samba410/work/samba-4.10.10/bin/default/lib/dbwrap', '-L/usr/ports/net/samba410/work/samba-4.10. 10/bin/default/lib/tdb_wrap', '-L/usr/ports/net/samba410/work/samba-4.10.10/bin/default/source4/cluster', '-L/usr/ports/net/samba410/work/samba-4.10.10/bin/default/source3', '-L/usr/ ports/net/samba410/work/samba-4.10.10/bin/default/source4/lib/messaging', '-L/usr/ports/net/samba410/work/samba-4.10.10/bin/default/lib/socket', '-L/usr/ports/net/samba410/work/samba -4.10.10/bin/default/source4/lib/events', '-L/usr/ports/net/samba410/work/samba-4.10.10/bin/default/libcli/security', '-L/usr/ports/net/samba410/work/samba-4.10.10/bin/default/lib/ld b', '-L/usr/ports/net/samba410/work/samba-4.10.10/bin/default/lib/replace',
Samba 4.10.10 can't find gnutls headers on one machine
Dear list, I need some help to figure out what I broke on my system. I have two (almost) identical machines, one running 12.1-RELEASE and one waiting to be upgraded and is still on 12.0-RELEASE-p10. Configuration and software wise I try to keep them identical. I recently upgraded Samba to 4.10.10 and it worked as expected on 12.1 but the same upgrade on 12.0 fails because the configure script can't find the gnutls headers. Here's some command outputs from each machine: 12.1 # pkg info | grep gnutls gnutls-3.6.10 GNU Transport Layer Security library # pkgconf --cflags gnutls -I/usr/local/include -I/usr/local/include/p11-kit-1 # pkgconf --libs gnutls -L/usr/local/lib -lgnutls 12.0 # pkg info | grep gnutls gnutls-3.6.10 GNU Transport Layer Security library # pkgconf --cflags gnutls -I/usr/local/include -I/usr/local/include/p11-kit-1 # pkgconf --libs gnutls -L/usr/local/lib -lgnutls Everything seems identical to me. Files are installed in /usr/local/include/gnutls. Unfortunately I'm too stupid to figure out how the Samba configure script works. It seems to be made in Python and I can't figure out how it checks for gnutls. python27-2.7.17 and python36-3.6.9 are installed on both machines. Any suggestions to help me figure out what I have broken would be appreciated. Regards Morgan Wesström ___ 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"
