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 +-+ databases/mysql-connector-odbc | 5.3.4 | 8.0.14 +-+ 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 Thanks. ___ 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"
which port installed what other port
Hi, Is there a command (or a port) I can use which, when fed an installed port name, can tell me what installed it? I don't mean libraries. I mean the actual port name. thanks, -- J. ___ 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: which port installed what other port
On 21/01/19 17:26, tech-lists wrote: > Hi, > > Is there a command (or a port) I can use which, when fed an installed > port name, can tell me what installed it? > > I don't mean libraries. I mean the actual port name. > Not sure what you're looking for anyway pkg has such functionality for run time dependencies: pkg info -d '*name*' shows packages on which any package matching '*name*' depends. You also have pkg info -r '*name*' which shows all packages requiring a specific package. This works only for run time dependencies (libraries and other), not for build time dependencies, which are not registered in the pkg database. Such information is not saved anywhere and is registered only in the port Makefiles. Check pkg-info(8) for further reference. Hope this helps. -- Guido Falsi ___ 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: which port installed what other port
Hello, On 1/21/19 9:26 AM, tech-lists wrote: > Hi, > > Is there a command (or a port) I can use which, when fed an installed > port name, can tell me what installed it? > > I don't mean libraries. I mean the actual port name. You can use "pkg info -d portname" to see what ports "portname" depends on (IE: What dependencies "portname" installed). You can also use "pkg info -r portname" to see the what the portname is a dependency of (what installed this port). Does that help at all? Regards, Janky Jay, III signature.asc Description: OpenPGP digital signature
Re: which port installed what other port
On Mon, Jan 21, 2019 at 09:35:20AM -0700, Alan Somers wrote: Try "pkg info -r ". And to go the other direction, use "pkg info -d ". -Alan OK thank you, I'll try that -- J. ___ 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"
PHP 7.2: SIGSEGV in OpenSSL
I'm seeing a lot of coredumps with a stack trace similar to this, on a 12-stable machine: # gdb /usr/local/sbin/httpd /httpd.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `/usr/local/sbin/httpd -DNOHTTPACCEPT'. Program terminated with signal 11, Segmentation fault. ... (gdb) bt #0 openssl_lh_strcasehash (c=0x803466cf2 ) at /freebsd/checkout/src/12/crypto/openssl/crypto/lhash/lhash.c:361 #1 0x00080138564d in obj_name_hash (a=0x7fffe9d0) at /freebsd/checkout/src/12/crypto/openssl/crypto/objects/o_names.c:166 #2 0x00080143be77 in OPENSSL_LH_delete (lh=0x800a27240, data=0x7fffe9d0) at /freebsd/checkout/src/12/crypto/openssl/crypto/lhash/lhash.c:302 #3 0x0008013852c8 in OBJ_NAME_remove ( name=0x803466cf2 , type=1) at obj_lcl.h:12 #4 0x00080143c15a in OPENSSL_LH_doall (lh=0x800a27240, func=0x8013855c0 ) at /freebsd/checkout/src/12/crypto/openssl/crypto/lhash/lhash.c:198 #5 0x000801385558 in OBJ_NAME_cleanup (type=1) at obj_lcl.h:12 #6 0x000801392918 in evp_cleanup_int () at /freebsd/checkout/src/12/crypto/openssl/crypto/evp/names.c:83 #7 0x00080146e39d in OPENSSL_cleanup () at /freebsd/checkout/src/12/crypto/openssl/crypto/init.c:567 #8 0x0008007a24e5 in __cxa_finalize (dso=0x0) at /freebsd/checkout/src/12/lib/libc/stdlib/atexit.c:233 #9 0x0008007320e1 in exit (status=54947058) at /freebsd/checkout/src/12/lib/libc/stdlib/exit.c:62 #10 0x000800a55118 in ?? () #11 0x7fffeb90 in ?? () The one case I could isolate the PHP code is calling stream_socket_enable_crypto(), but I suspect there might be others. Is anybody else seeing this? Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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"
CFT japanese/man on arm and mips
Hi there, This patch[1] seems to fix the build problem of japanese/man. I already tested in i386 and amd64, but can any in the list test in the following platforms? aarch64 armv6 armv7 mips Thanks! [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235058 ___ 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"
