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, 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/netpbm | 10.35.98| 10.47.63 +-+ 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"
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-unsubscr...@freebsd.org"
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 directory >> '/tmp/usr/ports/finance/gnucash/work/gnucash-2.6.14' >> gmake[1]: *** [Makefile:638: all] Error 2 >> gmake[1]: Leaving directory >> '/tmp/usr/ports/finance/gnucash/work/gnucash-2.6.14' >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/finance/gnucash >> >> What am I missing? >> >> >> Just delete the package before building it again >> cd/usr/ports/finance/gnucash >> make deinstall >> make clean >> make install >> >> it worked for me > > I can confirm that this worked for me as well. Thanks for the feedback, and sorry for the delay. I'll be having a look at the logs you sent me to make sure there isn't a problem with the port anyway. -- Guido Falsi ___ 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"
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 serial ports changes). In brief (as I understand). Currently there is a support for cua* ports only (no support for tty* ports). The proposed changes restrict using cua* but allow tty* ports, which will act like cua* ports. As for me I'll add tty* ports without removing cua*. Thank you. -- 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: 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 started
> downloading 5.6.
>
> Given that PHP is one of the pillars of a FAMP setup, I'd think
> that pkg should be aware of conflicts like that and return a
> notice ("No version for PHP 7.0. Install PHP 5.6?") rather than
> blythely assume it'd be okay to install an older version of PHP
> (or Apache, or MariaDB/MySQL, mutatis mutandis) despite an
> already-installed later version.
Right now, the default php version is php 5.6, which is used for the
official package builds. If you want to use another PHP version as the
default, you have to build your ports locally.
--
Mathieu Arnold
signature.asc
Description: OpenPGP digital signature
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
downloading 5.6.
Given that PHP is one of the pillars of a FAMP setup, I'd think
that pkg should be aware of conflicts like that and return a
notice ("No version for PHP 7.0. Install PHP 5.6?") rather than
blythely assume it'd be okay to install an older version of PHP
(or Apache, or MariaDB/MySQL, mutatis mutandis) despite an
already-installed later version.
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
___
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: 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). 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 > serial ports changes). > > In brief (as I understand). Currently there is a support for cua* ports > only (no support for tty* ports). The proposed changes restrict using > cua* but allow tty* ports, which will act like cua* ports. > > As for me I'll add tty* ports without removing cua*. Sounds like the best way forward, IMHO. cua and tty ports have existed for a long time, they each fulfil a role, and they are not the same. One or the other should not be removed unless a _good_ reason (be it technical or practical) is explained here, IMNSHO. Those who do not remember the past are condemned to repeat it. -- Regards, Torfinn Ingolfsen ___ 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: 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 the fact that it was going to
>> install PHP 5.6 despite my having 7.0 installed when it started
>> downloading 5.6.
>>
>> Given that PHP is one of the pillars of a FAMP setup, I'd think
>> that pkg should be aware of conflicts like that and return a
>> notice ("No version for PHP 7.0. Install PHP 5.6?") rather than
>> blythely assume it'd be okay to install an older version of PHP
>> (or Apache, or MariaDB/MySQL, mutatis mutandis) despite an
>> already-installed later version.
>
>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 conflct message (my memory
says you are), I'd think it would be friendlier to print the
message first, before anything is downloaded. It routinely
checks versions, so putting out the conflict message immediately,
even before showing the proposed downloads, shouldn't be hard.
___
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: 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 fact that it was going to
>> install PHP 5.6 despite my having 7.0 installed when it started
>> downloading 5.6.
>>
>> Given that PHP is one of the pillars of a FAMP setup, I'd think
>> that pkg should be aware of conflicts like that and return a
>> notice ("No version for PHP 7.0. Install PHP 5.6?") rather than
>> blythely assume it'd be okay to install an older version of PHP
>> (or Apache, or MariaDB/MySQL, mutatis mutandis) despite an
>> already-installed later version.
>
>Right now, the default php version is php 5.6, which is used for the
>official package builds. If you want to use another PHP version as the
>default, you have to build your ports locally.
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 performance that's so large
it's visible to the naked eye.
___
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: 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 performance that's so large > it's visible to the naked eye. The pkg-tooling right now does not support a repo with pre-built pkg's for both PHP versions. So the default repo is 5.6 for now. Right now it's not simple (or probably impossible) to say that a port can depend on either php56 or php70. I think this is called variants, and that feature is still @work for pkg. Those that plan to migrate better setup a repo with 7.0, and start testing for their applications. -- p...@opsec.eu+49 171 3101372 4 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: 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 conflct message (my memory says you are), I'd think it would be friendlier to print the message first, before anything is downloaded. It routinely checks versions, so putting out the conflict message immediately, even before showing the proposed downloads, shouldn't be hard. I think that conflicts are defined in package metadata so pkg don't know about conflict until package is downloaded. Maybe I am wrong. I didn't examine pkg internals too deep. 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: 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 5.6 instead. >>> >>> Miroslav Lachman >> >> I stopped it immediately. >> >> If you're right about it showing a conflct message (my memory >> says you are), I'd think it would be friendlier to print the >> message first, before anything is downloaded. It routinely >> checks versions, so putting out the conflict message immediately, >> even before showing the proposed downloads, shouldn't be hard. > > I think that conflicts are defined in package metadata so pkg don't know > about conflict until package is downloaded. Maybe I am wrong. I didn't > examine pkg internals too deep. There is no concept of conflicts in package metadata. The resolver will figure out if packages conflict at runtime and it may run into conflicts later due to replacing or installing packages that use the same files, different shared libraries and maybe more (IDK). It has occasionally stripped innocent top packages in systems for me. It looks like it doesn't virtually resolve through the whole process but goes ahead with some operations that it later can't roll back and just goes on taking a previous "y" as a base line. Cheers, Franco ___ 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"
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 https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199601 So in short: It's not there yet, but it might be close. If you can test/help with the open issues in that PR, that might speed up a new boost into the tree. For protobuf, there's a brand-new PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212973 I searched for dependent ports in /usr/ports using grep -Rl 'devel/protobuf' * > /tmp/file and reduced it by the depends that aren't exactly protobuf. Using that way, I found 33 other ports. It needs to be checked if they still build with the new protobuf and probably if they run, too. I assume there are many indirect dependencies, so other ports might be affected as well. It's not a trivial task. -- p...@opsec.eu+49 171 3101372 4 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: 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 > serial ports changes). Asking Gert Doering from mgetty, he explained the reason for two seperate names in the filesystem for the same device. In the long-gone past of unix, serial ports were a scarce resource, so ports were connected to modems and used for both dial-in and dial-out usage. The two names/devices had different behaviour which allowed them to be used in parallel, for either dial-in or dial-out: - getty waits on tty*, as long as the DCD-pin is low (open() blocked) - dialout applications like kermit or cu(1) use cua* for outgoing calls During an outgoing call, no incoming call will be received anyway. - If a call comes in, the modem takes the call, signals DCD on the serial port and getty's open() call finally suceeds and getty presents the 'login:'. - As long as getty has the serial port blocked for incoming use, open()'ing cua* will return EBUSY For a similar explanation see: https://en.wikipedia.org/wiki/Data_Carrier_Detect 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, dataloggers, function generators, spectrum analyzers, power supplies, GPIB interfaces, and more, really be used on a serial port that is used to log in (the getty usecase) ? In general, I guess: No. So the change from cua* to tty* is, while not really needed, not really critical. -- p...@opsec.eu+49 171 3101372 4 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: 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, dataloggers, function generators, spectrum > analyzers, power supplies, GPIB interfaces, and more, really > be used on a serial port that is used to log in (the getty usecase) ? > > In general, I guess: No. > > 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 with a remote, headless server). Peace, david -- David H. Wolfskill da...@catwhisker.org Those who would murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
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 with a remote, headless server). Will those precious serial console ports of headless servers really be used to access logic analyzers etc ? -- p...@opsec.eu+49 171 3101372 4 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: 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: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211101 >> and comment here (or at the PR if you wish) on proposed changes (for >> serial ports changes). > > Asking Gert Doering from mgetty, he explained the reason for > two seperate names in the filesystem for the same device. > > In the long-gone past of unix, serial ports were a scarce resource, > so ports were connected to modems and used for both dial-in and > dial-out usage. > > The two names/devices had different behaviour which allowed them > to be used in parallel, for either dial-in or dial-out: > > - getty waits on tty*, as long as the DCD-pin is low (open() blocked) > - dialout applications like kermit or cu(1) use cua* for outgoing calls > During an outgoing call, no incoming call will be received anyway. > - If a call comes in, the modem takes the call, signals DCD > on the serial port and getty's open() call finally suceeds > and getty presents the 'login:'. > - As long as getty has the serial port blocked for incoming use, > open()'ing cua* will return EBUSY > > For a similar explanation see: > > https://en.wikipedia.org/wiki/Data_Carrier_Detect > > 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, dataloggers, function generators, spectrum > analyzers, power supplies, GPIB interfaces, and more, really > be used on a serial port that is used to log in (the getty usecase) ? > > In general, I guess: No. > > So the change from cua* to tty* is, while not really needed, not > really critical. In other words, there is almost no gain while little harm. So why do those changes in the first place? However, the change may be treated as a POLA violation and contradicts the FreeBSD Handbook: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serial.html - In FreeBSD, each serial port is accessed through an entry in /dev. There are two different kinds of entries: Call-in ports are named /dev/ttyuN where N is the port number, starting from zero. If a terminal is connected to the first serial port (COM1), use /dev/ttyu0 to refer to the terminal. If the terminal is on the second serial port (COM2), use /dev/ttyu1, and so forth. Generally, the call-in port is used for terminals. Call-in ports require that the serial line assert the “Data Carrier Detect” signal to work correctly. Call-out ports are named /dev/cuauN on FreeBSD versions 10.x and higher and /dev/cuadN on FreeBSD versions 9.x and lower. Call-out ports are usually not used for terminals, but are used for modems. The call-out port can be used if the serial cable or the terminal does not support the “Data Carrier Detect” signal. - Are there any PROs for the change? Thanks all for help and discussion. -- WBR, bsam ___ 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"
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 recently. Any ideas? :) ___ 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: 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 ! ___ 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: 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 > gone recently. > > Any ideas? :) Have you seen https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212785 which discusses an update ? Can you comment on that PR ? -- p...@opsec.eu+49 171 3101372 4 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: 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! 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 recently. Any ideas? :) Have you seen https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212785 which discusses an update ? Can you comment on that PR ? ___ 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: 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+49 171 3101372 4 years to > go ! > ___ > > You are right because if you think "sender" and "receiver" working on the same computer , when assumed FreeBSD is supporting a complex laboratory system ( you mentioned in previous message such a possible devices list , someone sending and someone receiving messages ) . Mehmet Erol Sanliturk ___ 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"
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 see it is ready to go. Can anyone tell me what is happening, please? Thanks. -- Bob ___ 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"
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 ports ===>>> Initial dependency check complete for security/ca_root_nss ===>>> Starting build for security/ca_root_nss <<<=== ===>>> All dependencies are up to date ===> Cleaning for ca_root_nss-3.26 ===> License MPL accepted by the user ===> Found saved configuration for ca_root_nss-3.22.2 ===> ca_root_nss-3.26 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by ca_root_nss-3.26 for building ===> Extracting for ca_root_nss-3.26 => SHA256 Checksum OK for nss-3.26.tar.gz. ===> Patching for ca_root_nss-3.26 ===> ca_root_nss-3.26 depends on package: perl5>=5.20<5.21 - found ===> Configuring for ca_root_nss-3.26 ===> Building for ca_root_nss-3.26 ## Untrusted certificates omitted from this bundle: 20 openssl x509 failed with exit code 139 at /usr/ports/security/ca_root_nss/work/MAca-bundle.pl line 78. *** Error code 255 Stop. make[1]: stopped in /usr/ports/security/ca_root_nss *** Error code 1 Stop. make: stopped in /usr/ports/security/ca_root_nss ===>>> make build failed for security/ca_root_nss ===>>> Aborting update ===>>> You can restart from the point of failure with this command line: portmaster security/ca_root_nss svnlite info Path: . Working Copy Root Path: /usr/ports URL: svn://svnmirror/ports/head Relative URL: ^/head Repository Root: svn://svnmirror/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 422822 Node Kind: directory Schedule: normal Last Changed Author: araujo Last Changed Rev: 422822 Last Changed Date: 2016-09-27 13:50:45 -0400 (Tue, 27 Sep 2016) /etc/make.conf: WITH_PKGNG=yes DISABLE_VULNERABILITIES=yes DEFAULT_VERSIONS+=linux=c6 OVERRIDE_LINUX_NONBASE_PORTS=c6 Thanks for your attention.-- George ___ 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: 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 BB89 A1F3 5D66 E6D0 5453 signature.asc Description: This is a digitally signed message part
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 5D66 E6D0 5453 signature.asc Description: This is a digitally signed message part
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: WITH_PKGNG=yes DISABLE_VULNERABILITIES=yes DEFAULT_VERSIONS+= linux=c6 ssl=base OVERRIDE_LINUX_NONBASE_PORTS=c6 Did I do that right? I still get the same failure. -- George ___ 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: 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 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: > >WITH_PKGNG=yes >DISABLE_VULNERABILITIES=yes >DEFAULT_VERSIONS+= linux=c6 ssl=base >OVERRIDE_LINUX_NONBASE_PORTS=c6 > >Did I do that right? I still get the same failure. -- George -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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: Bug 212597 - New port: editors/ecce Edinburgh Compatible Context Editor - stuck?
On Wed, 28 Sep 2016 02:40:54 +0200 "Carlos J. Puga Medina" wrote: > 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, Thanks. I thought that might be the issue; I didn't think it was you! -- Bob ___ 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"
