Hello Mark,
Thanks for your reply. I didn't know about the elasticsearch_env="" - so
thanksfor that. So my follow-up questions are:
* How would I have to set up elasticsearch_env="", cause according to
the man of env elasticsearch_env="-S -P
/usr/local/bin:/usr/local/sbin" wouldn't do t
On Sat, Mar 31, 2018, at 02:25, Leander Schäfer wrote:
> Hello Mark,
>
> Thanks for your reply. I didn't know about the elasticsearch_env="" - so
> thanksfor that. So my follow-up questions are:
>
> * How would I have to set up elasticsearch_env="", cause according to
> the man of env ela
While the actual change to the Perl version works fine for me, I
find that invoking "pkg updating" fails to display the 20180330
ports/UPDATING entry. I got lucky, because I found out about the
change a different way.
I maintain /usr/ports as an SVN working copy, using a local private
mirror (upd
Hello.
I used to read ports' UPDATING via RSS, but now the feed I was using
(from versia) seems to be gone.
Anyone knows of another one?
I looked into FreshPorts, but didn't find a way to get this specific feed.
bye & Thanks
av.
___
freebs
Christoph Moench-Tegeder writes:
> > Socket.c: loadable library and perl binaries are mismatched
> > (got handshake key 0xd200080, needed 0xdf00080)
>
> The perl default version changed - are you sure your perl and modules
> still match? See UPDATING 20180330.
> The error message is just
On Fri, Mar 30, 2018 at 9:45 AM, Andrea Venturoli wrote:
> Hello.
>
> I used to read ports' UPDATING via RSS, but now the feed I was using (from
> versia) seems to be gone.
>
> Anyone knows of another one?
>
> I looked into FreshPorts, but didn't find a way to get this specific feed.
>
> bye & T
Hello all,
The binary node package on FreeBSD 11.1-RELEASE has a bad dependency on libuv.
I had libuv 1.17.0 installed and installed node with `pkg install node`, which
installed node v9.9.0.
Running `node` at this point would return the following error message:
> /usr/local/bin/node: Undefine
## Robert Huff (roberth...@rcn.com):
> On a system with over 850 ports, 32 starting with "p5-", the
> list of dependent ports portmaster created from
> "pkg shlib -qR libperl.so.5.24" was over 200, including things like
> FireFox and llvm50 (llvm is required for mesa-dri).
That sound like "
Christoph Moench-Tegeder writes:
> ## Robert Huff (roberth...@rcn.com):
>
> >On a system with over 850 ports, 32 starting with "p5-", the
> > list of dependent ports portmaster created from
> > "pkg shlib -qR libperl.so.5.24" was over 200, including things like
> > FireFox and llvm50 (
On Sat, Mar 31, 2018 at 1:22 PM, Robert Huff wrote:
>
> Christoph Moench-Tegeder writes:
>
> > ## Robert Huff (roberth...@rcn.com):
> >
> > >On a system with over 850 ports, 32 starting with "p5-", the
> > > list of dependent ports portmaster created from
> > > "pkg shlib -qR libperl.so.5
On Sat, Mar 31, 2018 at 7:25 AM, David Wolfskill
wrote:
> While the actual change to the Perl version works fine for me, I
> find that invoking "pkg updating" fails to display the 20180330
> ports/UPDATING entry. I got lucky, because I found out about the
> change a different way.
>
> I maintain
On Sat, Mar 31, 2018 at 04:23:54PM -0700, Kevin Oberman wrote:
> On Sat, Mar 31, 2018 at 7:25 AM, David Wolfskill
> wrote:
> ...
> > But "pkg updating -i" fails to display the 20180330 entry for me;
> > it does show entries for some(?) other ports I have installed:
> ...
> > Is the above a demost
12 matches
Mail list logo
