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
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
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
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"
dep
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/
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 i
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
