Re: ca_root_nss compile failure

I forgot to mention that this problem has been reported: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212921 El 28 de septiembre de 2016 3:20:04 CEST, George Mitchell escribió: >On 09/27/16 20:56, Carlos J. Puga Medina wrote: >> Hi George, >> >> Yes, I had the

Re: ca_root_nss compile failure

On 09/27/16 20:56, Carlos J. Puga Medina wrote: > Hi George, > > Yes, I had the same problem like you. So you only need to define your > default SSL version in /etc/make.conf > > See entry 20160616 in /usr/ports/UPDATING for further details. > > Regards, > Okay, /etc/make.conf now says:

Re: ca_root_nss compile failure

Hi George, Yes, I had the same problem like you. So you only need to define your default SSL version in /etc/make.conf See entry 20160616 in /usr/ports/UPDATING for further details. Regards, -- Carlos Jacobo Puga Medina PGP fingerprint = C60E 9497 5302 793B CC2D BB89 A1F3

Re: Bug 212597 - New port: editors/ecce Edinburgh Compatible Context Editor - stuck?

Hi Bob, The new port is ready to go, but I need my mentor's approval or authorization to commit it into the ports tree. One of my mentors will take a look ASAP, so I hope you understand. Best regards, -- Carlos Jacobo Puga Medina PGP fingerprint = C60E 9497 5302 793B CC2D

ca_root_nss compile failure

Before I file a PR, does this failure look familiar to anyone? portmaster -BDg security/ca_root_nss ===>>> Port directory: /usr/ports/security/ca_root_nss ===>>> Launching 'make checksum' for security/ca_root_nss in background ===>>> Gathering dependency list for security/ca_root_nss from

Bug 212597 - New port: editors/ecce Edinburgh Compatible Context Editor - stuck?

Hi I don't want to be a nuisance, but...! I submitted this new port just over two weeks ago. Someone made some minor cosmetic changes to the Makefile, and I approved them. Nothing has happened for nearly two weeks. I don't know if there are special procedures for new ports, but as far as I can

Re: Serial ports guru help is needed

On Tue, Sep 27, 2016 at 1:21 PM, Kurt Jaeger wrote: > Hi! > > > Are there any PROs for the change? > > I've re-read the PR and your idea to allow both cua* and tty* being > used. If that is possible and "does the right thing", it's even better. > > -- > p...@opsec.eu

Re: Needed newer version of multimedia/mp4v2

No, I haven't. Thanks to point me. I'm not sure what is 3.0.0.1 it looks like fork with unknown origins. Original code was 2.0.0 before google code died and 2.0.0 is adopted in lunux world, however not sure how they are going to build it now. On 27.09.2016 23:23, Kurt Jaeger wrote: Hi!

Re: Needed newer version of multimedia/mp4v2

Hi! > this port looks very outdated and I have an issue with saving mp4 files > in development branch of multimedia/zoneminder. Linux version of ZM > linked against 2.0.0 version, so it's worth to try to update this port > first and see if something improves. However, looks like sources are >

Re: Serial ports guru help is needed

Hi! > Are there any PROs for the change? I've re-read the PR and your idea to allow both cua* and tty* being used. If that is possible and "does the right thing", it's even better. -- p...@opsec.eu+49 171 3101372 4 years to go !

Needed newer version of multimedia/mp4v2

Hello, this port looks very outdated and I have an issue with saving mp4 files in development branch of multimedia/zoneminder. Linux version of ZM linked against 2.0.0 version, so it's worth to try to update this port first and see if something improves. However, looks like sources are gone

Re: Serial ports guru help is needed

Kurt, thank you for your really great answer. 27.09.2016 20:10, Kurt Jaeger пишет: > >> A user proposed some changes to deal with serial ports I do not quite >> understand (and tend to not agree with). Can a serial ports guru take >> a look at the PR: >>

Re: Serial ports guru help is needed

Hi! > > So the change from cua* to tty* is, while not really needed, not > > really critical. > > > Folks might want to (also) consider the use case of a serial console -- > and being able to login to it (e.g., if all other access has failed, for > an out-of-band communication mechanism

Re: Serial ports guru help is needed

On Tue, Sep 27, 2016 at 07:10:33PM +0200, Kurt Jaeger wrote: > ... > So, back to this usecase: Will a software someone is using to > talk to logic analyzers, MSOs, oscilloscopes, multimeters, LCR > meters, sound level meters, thermometers, hygrometers, anemometers, > light meters, DAQs,

Re: Serial ports guru help is needed

Hi! > A user proposed some changes to deal with serial ports I do not quite > understand (and tend to not agree with). Can a serial ports guru take > a look at the PR: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211101 > and comment here (or at the PR if you wish) on proposed changes (for

Re: Need newer ports

Hi! > I am building a port of librevault and I require baminimum version > of 1.58.0 for boost and 3.0.0 of protobuf. I am wondering what would > be done to make this possible? For boost: There's a long-running PR for this, because it's really not simple to upgrade:

Need newer ports

I am building a port of librevault and I require baminimum version of 1.58.0 for boost and 3.0.0 of protobuf. I am wondering what would be done to make this possible? ___ freebsd-ports@freebsd.org mailing list

Re: Pkg doesn't care about conflict

> On 27 Sep 2016, at 5:05 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > Margaret wrote on 09/27/2016 14:55: > > [...] > >>> Did you stop pkg in the middle or did you let it go? I think it will >>> show you conflict message and ask you if you would like to deinstall PHP >>> 7.0 and install

Re: Pkg doesn't care about conflict

Margaret wrote on 09/27/2016 14:55: [...] Did you stop pkg in the middle or did you let it go? I think it will show you conflict message and ask you if you would like to deinstall PHP 7.0 and install 5.6 instead. Miroslav Lachman I stopped it immediately. If you're right about it showing a

Re: Pkg doesn't care about conflict

Hi! > Both 5.* and 7.* are current tracks at PHP, so it's not > surprising that a package is built with 5.6. What surprised me, > apart from pkg's apparent willingness to ignore an existing > install of 7.0, was that there are no pkgs built against 7.0, > even though 7.0 provides a jump in

Re: Pkg doesn't care about conflict

On Tue, 27 Sep 2016 13:02:46 +0200, Mathieu Arnold wrote: >Le 26/09/2016 à 21:42, scratch65...@att.net a écrit : >> I have the PHP 7.0 package installed under 10.2. Wanting to >> install the pecl-imagick port, I called pkg search, which >> returned a ref. I only caught the

Re: Pkg doesn't care about conflict

[Default] On Tue, 27 Sep 2016 13:40:33 +0200, Miroslav Lachman <000.f...@quip.cz> wrote: >scratch65...@att.net wrote on 09/26/2016 21:42: >> I have the PHP 7.0 package installed under 10.2. Wanting to >> install the pecl-imagick port, I called pkg search, which >> returned a ref. I only caught

Re: Serial ports guru help is needed

Hello, I'm not a serial guru, but I have used serial extensively over the past 20 - 40 years. On Tue, Sep 27, 2016 at 10:59 AM, Boris Samorodov wrote: > Hi All! > > > A user proposed some changes to deal with serial ports I do not quite > understand (and tend to not agree with).

Re: Pkg doesn't care about conflict

scratch65...@att.net wrote on 09/26/2016 21:42: I have the PHP 7.0 package installed under 10.2. Wanting to install the pecl-imagick port, I called pkg search, which returned a ref. I only caught the fact that it was going to install PHP 5.6 despite my having 7.0 installed when it started

Re: Pkg doesn't care about conflict

Le 26/09/2016 à 21:42, scratch65...@att.net a écrit : > I have the PHP 7.0 package installed under 10.2. Wanting to > install the pecl-imagick port, I called pkg search, which > returned a ref. I only caught the fact that it was going to > install PHP 5.6 despite my having 7.0 installed when it

Serial ports guru help is needed

Hi All! A user proposed some changes to deal with serial ports I do not quite understand (and tend to not agree with). Can a serial ports guru take a look at the PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211101 and comment here (or at the PR if you wish) on proposed changes (for

Re: finance/gnucash fails to build

On 09/27/16 06:27, Jonathan Chen wrote: > On 27 September 2016 at 07:57, Sérgio de Almeida Lenzi > wrote: >> Em Seg, 2016-09-26 às 21:15 +1300, Jonathan Chen escreveu: >> >> k/gnucash-2.6.14/src' >> gmake[2]: *** [Makefile:785: all-recursive] Error 1 >> gmake[2]: Leaving

PR looking for committer

Can a committer have a look at this? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212951 Thank you! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

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,

Check constistency of the installed ports

As a user of ports-mgmt/portmaster, I face very often the situation with this tool, that it fails in the very last stage of registering an installation or update of a port. So it happens to, for example, updates for print/tex-xetex and somehow (not being aware of) print/tex-luatex. Anyway, if