php71-pdo_sqlite won't build with poudriere

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

Re: How to get pkg to recognize local repository?

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

Re: www/node 8.1.4 core dumped with Kibana5

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

Re: www/node 8.1.4 core dumped with Kibana5

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

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

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

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

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

Re: github repo to port connection

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

Re: github repo to port connection

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

Re: github repo to port connection

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

Re: github repo to port connection

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. --

github repo to port connection

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.

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

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,

Re: How to get pkg to recognize local repository?

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

Re: emscripten port?

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? > >

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,

Re: emscripten port?

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

emscripten port?

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

Re: How to get pkg to recognize local repository?

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

Re: Anybody knows how to patch tarballs that bazel extracts?

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

Re: Anybody knows how to patch tarballs that bazel extracts?

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

Re: Anybody knows how to patch tarballs that bazel extracts?

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