php71-pdo_sqlite won't build with poudriere

[Jim Trigg]

I'm trying to set up a poudriere repository, and php71-pdo_sqlite
refuses to build.

[00:01:37] >> [02][00:00:18] Finished build of
databases/php71-pdo_sqlite: Failed: build-depends

But php71-pdo_sqlite properly depends (runtime) on php71-pdo.

Why can't the jail find the shared library? I thought that's what
poudriere was all about...

(Note: formerly a satisfied portmaster user...)

Thanks,
Jim



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
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: How to get pkg to recognize local repository?

[Thomas Mueller]

On Tue, 18 Jul 2017 02:33:22 +
"Thomas Mueller"  wrote:

> I suppose priority 99 would take priority over priority 98?

> In normal English usage, first priority or priority one is higher
> than priority two.

> Do you need the comma after the closing brace after myfirstrepo?

> I suppose myfirst repo and mysecondrepo are both in the same .conf
> file?

Bob Eager responded:

> This isn't well (or, at least, transparently) documented. However, if
> you do 'man pkg.conf' and read down, it eventually tells you the syntax
> of a repo file.
 
> I've always put them one per file, with a name that reflects that repo.

"man pkg.conf" says individual repository configuration files are processed in 
alphabetical order.

But according to the man page, one configuration file can specify more than one 
repository.

I guess I'll need to do some trial and error, given the confusing nature of the 
documentation.

I still want to get rid of the old no-longer-usable packages.  All I can think 
of now is Midnight Commander (mc) from NetBSD.

There ought to be a convenient way to remove outdated packages from a repo,  Or 
maybe there is but not documented, or at least not clearly documented?

I also want to look at how NetBSD pkgsrc defines/configures a repo so as to 
compare to FreeBSD.

Tom

___
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: www/node 8.1.4 core dumped with Kibana5

[Matthias Petermann]

Hello Miroslav,

I have run into the same issue recently. There is a ticket for this
problem:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220467

The reporter of the ticket proposes to adjust the kibana dependencies
to point to node6 which doesn't have the bug.

Would maybe a good idea to stick to the stable 6 versions, as long as
kibana doesn't neccessarily need a need a newer one. At least from the
source code side, version 6 seems to be fine:

https://github.com/elastic/kibana/blob/master/.node-version

Best regards,
Matthias




Am Mittwoch, den 19.07.2017, 01:36 +0200 schrieb Miroslav Lachman:
> I upgraded ports on our test server, it includes upgrade of node
> from  
> 7.10.0 to 8.1.4 but Kibana failed to start with the following stack
> trace
> 
> (node:13668) [DEP0022] DeprecationWarning: os.tmpDir() is
> deprecated. 
> Use os.tmpdir() instead.
> /usr/local/bin/node[13668]: ../src/env-inl.h:131:void 
> node::Environment::AsyncHooks::push_ids(double, double): Assertion 
> `(trigger_id) >= (0)' failed.
>   1: node::Abort(void) [/usr/local/bin/node]
>   2: node::Assert(char const* const[4]*) [/usr/local/bin/node]
>   3: 
> node::AsyncWrap::PushAsyncIds(v8::FunctionCallbackInfo p::PushAsyncIds::Value> 
> const&) [/usr/local/bin/node]
>   4: 
> v8::internal::FunctionCallbackArguments::Call(void(*)(v8::FunctionCal
> lbackInfo 
> const&)) [/usr/local/bin/node]
>   5: v8::internal::Isolate* 
> v8::internal::Builtins::InvokeApiFunction(v8::internal::Isolate*,
> bool, 
> v8::internal::Handle(int, 
> v8::internal::Object*, v8::internal::HeapObject)
> [/usr/local/bin/node]
>   6: v8::internal::Builtin_HandleApiCall(int,
> v8::internal::Object**, 
> v8::internal::Isolate*) [/usr/local/bin/node]
> Abort (core dumped)
> 
> I found similar issue on GitHub https://github.com/nodejs/node/issues
> /14198
> 
> Is it possible to add the fox from nightly version to port www/node? 
> Otherwise Kibana cannot run.
> 
> Kind regards
> Miroslav Lachman
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.o
> rg"
___
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: www/node 8.1.4 core dumped with Kibana5

[Miroslav Lachman]

Matthias Petermann wrote on 2017/07/19 02:38:

Hello Miroslav,

I have run into the same issue recently. There is a ticket for this
problem:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220467

The reporter of the ticket proposes to adjust the kibana dependencies
to point to node6 which doesn't have the bug.

Would maybe a good idea to stick to the stable 6 versions, as long as
kibana doesn't neccessarily need a need a newer one. At least from the
source code side, version 6 seems to be fine:

https://github.com/elastic/kibana/blob/master/.node-version


But then there will be another issue - the most of the ports are using 
www/node as dependency. If Kibana will have dependency on www/node6 then 
it cannot coexists with other ports on one machine.


This was the reason why it was updated from www/node4 to www/node

see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218250




Am Mittwoch, den 19.07.2017, 01:36 +0200 schrieb Miroslav Lachman:

I upgraded ports on our test server, it includes upgrade of node
from
7.10.0 to 8.1.4 but Kibana failed to start with the following stack
trace

(node:13668) [DEP0022] DeprecationWarning: os.tmpDir() is
deprecated.
Use os.tmpdir() instead.
/usr/local/bin/node[13668]: ../src/env-inl.h:131:void
node::Environment::AsyncHooks::push_ids(double, double): Assertion
`(trigger_id) >= (0)' failed.
   1: node::Abort(void) [/usr/local/bin/node]
   2: node::Assert(char const* const[4]*) [/usr/local/bin/node]
   3:
node::AsyncWrap::PushAsyncIds(v8::FunctionCallbackInfo
const&) [/usr/local/bin/node]
   4:
v8::internal::FunctionCallbackArguments::Call(void(*)(v8::FunctionCal
lbackInfo
const&)) [/usr/local/bin/node]
   5: v8::internal::Isolate*
v8::internal::Builtins::InvokeApiFunction(v8::internal::Isolate*,
bool,
v8::internal::Handle(int,
v8::internal::Object*, v8::internal::HeapObject)
[/usr/local/bin/node]
   6: v8::internal::Builtin_HandleApiCall(int,
v8::internal::Object**,
v8::internal::Isolate*) [/usr/local/bin/node]
Abort (core dumped)

I found similar issue on GitHub https://github.com/nodejs/node/issues
/14198

Is it possible to add the fox from nightly version to port www/node?
Otherwise Kibana cannot run.

Kind regards
Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.o
rg"




___
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: committer needed for new ports: Search Guard for Kibana and Elasticsearch

[Torsten Zuehlsdorff]

Aloha,


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219739


I take this one!

Greetings,
Torsten

--
Support me at:
https://www.patreon.com/TorstenZuehlsdorff
___
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"

committer needed for new ports: Search Guard for Kibana and Elasticsearch

[Miroslav Lachman]

I submitted these two ports 2017-06-02 and there were not touched by anybody

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219738

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219739

Can somebody take a look on them?

Kind regards
Miroslav Lachman
___
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: github repo to port connection

[Athanasios Douitsis]

Indeed, so instead of constructing the .shar, it is customary for the
maintainer to point the ports committer to the repo. Excellent.

Many many thanks, that helps a lot.

King regards,
Athanasios


On Tue, Jul 18, 2017 at 5:06 PM, Kurt Jaeger  wrote:

> Hi!
>
> > I think this is to fetch sources from github. What I mean is to use
> github
> > instead of having to construct a .shar for a new version of a port.
>
> You have a shar file on github or a new port ?
>
> Put the link to the github repo in the problem report, the committer
> can probably handle that case.
>
> --
> p...@opsec.eu+49 171 3101372 3 years to
> go !
> ___
> 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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: github repo to port connection

[Kurt Jaeger]

Hi!

> I think this is to fetch sources from github. What I mean is to use github
> instead of having to construct a .shar for a new version of a port.

You have a shar file on github or a new port ?

Put the link to the github repo in the problem report, the committer
can probably handle that case.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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: github repo to port connection

[Kurt Jaeger]

Hi!

> > Totally new to ports maintenance, please bear.
> > 
> > Is there a way for a port to be semi-automatically updated from a github
> > repo as its source?
> 
> Yes, see
> 
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#makefile-distfiles
> 
> and the USE_GITHUB example.

It's section 5.4.3, USE_GITHUB, in the porters handbook.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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: github repo to port connection

[Kurt Jaeger]

Hi!

> Totally new to ports maintenance, please bear.
> 
> Is there a way for a port to be semi-automatically updated from a github
> repo as its source?

Yes, see

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#makefile-distfiles

and the USE_GITHUB example.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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"

github repo to port connection

[Athanasios Douitsis]

Hello,

Totally new to ports maintenance, please bear.

Is there a way for a port to be semi-automatically updated from a github
repo as its source?

I understand that a ports committer (which I am not) must always be present
in the process, just looking for the optimal way to handle maintenance.

If this has been discussed before, my apologies.

Many thanks,
-- 
Athanasios Douitsis
___
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"

Opt-in pkg-fallout@ mail to maintainers from Tier2 architectures

[Jan Beich]

Fixing Tier2 bustage is often non-trivial due to complicated triaging and
testing. Maintainers are better positioned to come up with fixes. Sometimes
Tier* archs change over the years or committers mark ports BROKEN en masse
without giving maintainers a chance to fix in advance. However, pkg-fallout@
is a noisy list thus requires heavy filtering that in itself has to be
maintained to not grow out of sync.

Is there a easy way to subscrube to bustage e.g., on aarch64?

Related:
https://lists.freebsd.org/pipermail/freebsd-ports/2015-June/099438.html
https://lists.freebsd.org/pipermail/freebsd-ports/2013-August/085568.html
___
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: How to get pkg to recognize local repository?

[Boris Samorodov]

18.07.2017 05:33, Thomas Mueller пишет:


This looks like it might help, but PKG-REPOSITORY and FETCH have to be 
lower-case, won't work with capital letters.


That's an old unix tradition. PKG-REPOSITORY(5) and FETCH(3) mean
that one should use "man 5 pkg-repository" and "man 3 fetch" to
get the needed info.

PS. If you try the first command, at the very firts line you'll get:
---
PKG-REPOSITORY(5)FreeBSD File Formats Manual PKG-REPOSITORY(5)
---

HTH
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: emscripten port?

[Johannes Lundberg]

Hi Kurt

Thanks!

Yep, and should be easy. It builds fine on my system, all I needed to do is
point it to use 'node' from ports instead of included linux node binary.




On Tue, Jul 18, 2017 at 10:49 AM, Kurt Jaeger  wrote:

> Hi!
>
> > Is anyone working on an emscripten port?
> >
> > https://github.com/kripken/emscripten
>
> https://wiki.freebsd.org/WantedPorts
>
> and bugs.freebsd.org say: no trace of someone working on it.
>
> But: Sounds interesting.
>
> --
> p...@opsec.eu+49 171 3101372 3 years to
> go !
>
___
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

[portscout]

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
+-+
graphics/opencollada| 1.6.47  | v1.6.57
+-+


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"

Re: emscripten port?

[Kurt Jaeger]

Hi!

> Is anyone working on an emscripten port?
> 
> https://github.com/kripken/emscripten

https://wiki.freebsd.org/WantedPorts

and bugs.freebsd.org say: no trace of someone working on it.

But: Sounds interesting.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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"

emscripten port?

[Johannes Lundberg]

Hi

Is anyone working on an emscripten port?

https://github.com/kripken/emscripten
___
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: How to get pkg to recognize local repository?

[Bob Eager]

On Tue, 18 Jul 2017 02:33:22 +
"Thomas Mueller"  wrote:

> I suppose priority 99 would take priority over priority 98?
> 
> In normal English usage, first priority or priority one is higher
> than priority two.
> 
> Do you need the comma after the closing brace after myfirstrepo?
> 
> I suppose myfirst repo and mysecondrepo are both in the same .conf
> file?

This isn't well (or, at least, transparently) documented. However, if
you do 'man pkg.conf' and read down, it eventually tells you the syntax
of a repo file.

I've always put them one per file, with a name that reflects that repo.
___
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: Anybody knows how to patch tarballs that bazel extracts?

[Klaus T. Aehlig]

On Tue, Jul 18, 2017 at 08:33:57AM +0200, Klaus T. Aehlig wrote:
> Actually, it is not that far in the future; in fact, event today, bazel's
> cc_library rule accepts an .so in the sources attribute, making a work around
> possible (patching WORKSPACE to point to a hand-crafted directory under WRKDIR
> as a local_repository, with hand-crafted BUILD-files, essentially taking
> things from ${LOCALBASE}).

Related bazel issue: https://github.com/bazelbuild/bazel/issues/3402
___
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: Anybody knows how to patch tarballs that bazel extracts?

[Yuri]

On 07/17/2017 23:33, Klaus T. Aehlig wrote:

Actually, it is not that far in the future; in fact, event today, bazel's
cc_library rule accepts an .so in the sources attribute, making a work around
possible (patching WORKSPACE to point to a hand-crafted directory under WRKDIR
as a local_repository, with hand-crafted BUILD-files, essentially taking
things from ${LOCALBASE}).



Thank you Klaus,


I will follow your suggestion.


Yuri

___
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: Anybody knows how to patch tarballs that bazel extracts?

[Klaus T. Aehlig]

On Mon, Jul 17, 2017 at 09:37:34AM +0200, Klaus T. Aehlig wrote:
> However, even with that approach, you should be aware that you're
> embedding the relevant dependencies rather than using them from
> ${LOCALBASE}. So, in the long run, it might be desirable to patch the
> relevant targets in the BUILD files using those external resources to
> point to ${LOCALBASE}. Maybe, one could even lobby for a new_local_library
> WORKSPACE rule at bazel-...@googlegroups.com. But that's all long-term
> perspective...

Actually, it is not that far in the future; in fact, event today, bazel's
cc_library rule accepts an .so in the sources attribute, making a work around
possible (patching WORKSPACE to point to a hand-crafted directory under WRKDIR
as a local_repository, with hand-crafted BUILD-files, essentially taking
things from ${LOCALBASE}).
___
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"