FreeBSD Port: php56-imap-5.6.29

Hi, i would like to suggest moving the imap extension loader priority from 20 to 40. I have seen that imap needs to be loaded last to be satisfied. If i load it at 20 i get: # php -v Segmentation fault After renaming (in /usr/local/etc/php) # mv ext-20-imap.ini ext-40-imap.ini # php -v PHP

Re: 12-CURRENT won't configure to download packagesite.txz yet

On February 7, 2017 2:35:16 AM GMT+01:00, Jeffrey Bouquet wrote: >All the files > >/etc/FreeBSD.conf >/usr/local/etc/pkg/repos/FreeBSD.conf >/usr/local/etc/pkg.conf > >I edit time after time for >{$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386 >Anytime

12-CURRENT won't configure to download packagesite.txz yet

All the files /etc/FreeBSD.conf /usr/local/etc/pkg/repos/FreeBSD.conf /usr/local/etc/pkg.conf I edit time after time for {$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386 Anytime I try to attune to freebsd:12:x86:32or FreeBSD:12:i386 ... it downloads the

Tahoe-LAFS on FreeBSD?

Hello, is there someone working on a port of Tahoe-LAFS [1,2,3] for FreeBSD? Or maybe there is one already and I'm blind? [1]: https://eprint.iacr.org/2012/524.pdf [2]: https://github.com/tahoe-lafs/tahoe-lafs [3]: http://tahoe-lafs.readthedocs.io/en/latest/ Thanks, -cpghost. -- Cordula's

Re: cmake release builds don't disable assertions (NDEBUG)

On Mon, 06 Feb 2017 22:27:01 +0100 Raphael Kubo da Costa wrote: > Michael Gmelin writes: > > > While debugging an unexpected assertion problem, I noticed that > > ports using cmake don't set -NDEBUG, even when building in Release > > mode. > > > > Is this

Re: cmake release builds don't disable assertions (NDEBUG)

Michael Gmelin writes: > While debugging an unexpected assertion problem, I noticed that ports > using cmake don't set -NDEBUG, even when building in Release mode. > > Is this intentional? Is it the software you're porting that checks for DEBUG or some library it uses? CMake

Re: No reaction - what can I do?

Hi! > li> [...] > li> > I am aware of this PR but I am still not sure of the cause since I > li> > could not reproduce it. > li> In this case, please write a note into the PR that you can > li> not reproduce it. It helps the submitter to understand the situation. > Okay, I will do it more

Re: No reaction - what can I do?

Kurt Jaeger wrote in <20170206111716.gj13...@home.opsec.eu>: li> Hi! li> li> > jh> > I have opened the PR 214665 on 19.11.2016. No reaction of the maintainer li> > jh> > until today. He also does not react to e-mails. What else can I do? li> [...] li> > I am aware of this PR

Re: /usr/ports/devel/check Port upgrade fails

Hi Kurt, Op 6-2-2017 om 16:15 schreef Kurt Jaeger: Please look for the other mail thread a few hours ago, see: https://lists.freebsd.org/pipermail/freebsd-ports/2017-February/107030.html Sorry, I have overseen that one - it worked for me. Keep up the good work, Jos

Re: devel/libcheck

On 02/06, Rainer Hurling wrote: > > Perhaps, this is something for UPDATING? > > > > No, UPDATING is for things humans need to do. portmaster should be able > > to figure this out from MOVED (which is mostly meant for machines). > > Of course, I know this about UPDATING. > > In this case

cmake release builds don't disable assertions (NDEBUG)

While debugging an unexpected assertion problem, I noticed that ports using cmake don't set -NDEBUG, even when building in Release mode. Is this intentional? Thanks, Michael -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list

Re: Seamonkey update

On Sun, 5 Feb 2017 20:05:51 -0500, roberth...@rcn.com wrote: > > Jeffrey Bouquet writes: > > > pkg today updated seamonkey, now it segfaults, > > every which way I try to run it. > > I am running SeaMonkey 2.46_5 (compiled today) under: > > FreeBSD 11.0-RC2 #0 r304729:

Re: /usr/ports/devel/check Port upgrade fails

On Mon, Feb 06, 2017 at 03:22:44PM +0100, Jos Chrispijn wrote: > Dear port maintainer, > > Just upgrading my ports and get the following error: > > --- cut --- > > ===> Installing for check-0.10.0 > ===> Checking if check already installed > ===> Registering installation for check-0.10.0 as

Re: /usr/ports/devel/check Port upgrade fails

Hi! > ===> Installing for check-0.10.0 > ===> Checking if check already installed > ===> Registering installation for check-0.10.0 as automatic [...] > can you plstell me how to solve? Thanks! Please look for the other mail thread a few hours ago, see:

/usr/ports/devel/check Port upgrade fails

Dear port maintainer, Just upgrading my ports and get the following error: --- cut --- ===> Installing for check-0.10.0 ===> Checking if check already installed ===> Registering installation for check-0.10.0 as automatic Installing check-0.10.0... pkg-static: check-0.10.0 conflicts with

Bug 215153: sysutils/apcupsd, change default options to enable SNMP driver

Hi all, I requested this change to sysutils/apcupsd so that it will be possible to access/control/monitor UPS's across the network out of the box. At present due to the SNMP driver not being enabled in the default settings this is not possible. The maintainer has not responded to the bug or

Re: devel/libcheck

Hi René, Am 06.02.2017 um 09:51 schrieb René Ladan: > 2017-02-06 9:18 GMT+01:00 Rainer Hurling >: > > Am 06.02.2017 um 07:29 schrieb Kurt Jaeger: > > Hi! > > > >> I just went to update my ports today on a machine, and there was a >

Re: No reaction - what can I do?

Hi, Reference: > From: Kurt Jaeger > Date: Mon, 6 Feb 2017 11:55:39 +0100 Kurt Jaeger wrote: > Hi! > > > > Is it normal that maintainers / committer will not respond? > [...] > > https://www.freebsd.org/portmgr/policies_contributors.html > > "The time limit for

Re: No reaction - what can I do?

Hi! > jh> > I have opened the PR 214665 on 19.11.2016. No reaction of the maintainer > jh> > until today. He also does not react to e-mails. What else can I do? [...] > I am aware of this PR but I am still not sure of the cause since I > could not reproduce it. In this case, please write a

Re: No reaction - what can I do?

"Julian H. Stacey" wrote in <201702060901.v1691t6v084...@fire.js.berklix.net>: jh> Hi, Reference: jh> > From: Jochen Neumeister jh> > Date: Mon, 6 Feb 2017 09:27:52 +0100 jh> jh> Jochen Neumeister wrote: jh> > Hello everybody,

Re: No reaction - what can I do?

Hi! > > Is it normal that maintainers / committer will not respond? [...] > https://www.freebsd.org/portmgr/policies_contributors.html > "The time limit for a maintainer to respond to a PR is two weeks. > After that period, ." The problem in this case is that nobody suggested a solution,

Re: No reaction - what can I do?

Hi, Reference: > From: Jochen Neumeister > Date: Mon, 6 Feb 2017 09:27:52 +0100 Jochen Neumeister wrote: > Hello everybody, > > I have opened the PR 214665 on 19.11.2016. No reaction of the maintainer > until today. He also does not react to e-mails. What

Re: How to see package dependencies (scponly depends on ccache?)

Am 05.02.2017 um 14:23 schrieb tech-lists: > does your /etc/make.conf have a reference to ccache ? /etc/make.conf is empty, only my poudiere make.conf holds the following: DEFAULT_VERSIONS=php=5.6 apache=2.4 mysql=10.1m bdb=6 ssl=openssl WITH_BDB6_PERMITTED=1 WITH_OPENSSL_PORT=yes

Re: No reaction - what can I do?

Hi! > What annoys me a bit: I write a PR, and he is not answered. I have some > open PRs of this type. I know we all do it voluntarily. But it is not > nice if a PR is not worked for several months. I agree, but if I look at my own list of open bugs

Re: No reaction - what can I do?

I have opened the PR 214665 on 19.11.2016. No reaction of the maintainer until today. He also does not react to e-mails. What else can I do? Is it normal that maintainers / committer will not respond? It can happen, especially if the problem is difficult to reproduce for the

Re: No reaction - what can I do?

Hi! > > I have opened the PR 214665 on 19.11.2016. No reaction of the maintainer > > until today. He also does not react to e-mails. What else can I do? > > > > Is it normal that maintainers / committer will not respond? > > It can happen, especially if the problem is difficult to reproduce >

Re: No reaction - what can I do?

Hi! > I have opened the PR 214665 on 19.11.2016. No reaction of the maintainer > until today. He also does not react to e-mails. What else can I do? > > Is it normal that maintainers / committer will not respond? It can happen, especially if the problem is difficult to reproduce for the

Re: devel/libcheck

2017-02-06 9:18 GMT+01:00 Rainer Hurling : > Am 06.02.2017 um 07:29 schrieb Kurt Jaeger: > > Hi! > > > >> I just went to update my ports today on a machine, and there was a > >> conflict between devel/check and devel/libcheck. > > > > It's more that libcheck was moved to check. >

Re: devel/libcheck

Am 06.02.2017 um 07:29 schrieb Kurt Jaeger: > Hi! > >> I just went to update my ports today on a machine, and there was a >> conflict between devel/check and devel/libcheck. > > It's more that libcheck was moved to check. > > According to /usr/ports/MOVED: > >

No reaction - what can I do?

Hello everybody, I have opened the PR 214665 on 19.11.2016. No reaction of the maintainer until today. He also does not react to e-mails. What else can I do? Is it normal that maintainers / committer will not respond? Best regards Jochen ___