GSSAPI and Heimdal in Base

2014-02-16 Thread Robert Simmons
When building openssh-portable, and enabling kerb_gssapi, but using the heimdal that is in base, it gives the error: KERB_GSSAPI Requires either MIT or HEMIDAL, does not build with base Heimdal currently What is the difference between base and the port of Heimdal? _

Re: Requesting Committer Attention for ports/184011 (Pkgng support in net-mgmt/nagios-check_ports)

2014-02-16 Thread Ryan Frederick
Thanks, I'll keep that in mind. I'm actually the new maintainer of net-mgmt/nagios-check_ports, and this is the last pr left over from the previous maintainer that needs to be closed out. Ryan On 2/16/14 8:15 PM, Greg 'groggy' Lehey wrote: > On Sunday, 16 February 2014 at 20:08:28 -0600, Ryan Fr

ports-mgmt/pkg pkg-repo(8) does not catalogue latest package

2014-02-16 Thread John Marshall
Creating a repository catalogue with "pkg repo ${repo_root}" includes only the OLDEST version of any package found in a directory below the repository root. Perhaps I'm just not driving it properly? When I build ports with portmaster, I pass the -g option so that portmaster saves a (pkgng flavour

[QAT] r344636: 1x configure_error, 1x depend (configure_error in www/firefox), 7x success, 3x leftovers

2014-02-16 Thread Ports-QAT
Update to 27.0.1 - Build ID: 20140216223200-30828 Job owner: b...@freebsd.org Buildtime: 4 hours Enddate: Mon, 17 Feb 2014 02:30:13 GMT Revision: r344636 Repository:

Re: Requesting Committer Attention for ports/184011 (Pkgng support in net-mgmt/nagios-check_ports)

2014-02-16 Thread Greg 'groggy' Lehey
On Sunday, 16 February 2014 at 20:08:28 -0600, Ryan Frederick wrote: > I'd like to request that a committer take a gander at ports/184011 for > me when possible. This is a pr I submitted three months ago and was > never acted upon by the previous maintainer. Always a good idea to quote text that t

Requesting Committer Attention for ports/184011

2014-02-16 Thread Ryan Frederick
I'd like to request that a committer take a gander at ports/184011 for me when possible. This is a pr I submitted three months ago and was never acted upon by the previous maintainer. Ryan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.o

Adventures in ports, chapter 340877

2014-02-16 Thread George Mitchell
Perhaps it's just my bad luck, but updating my ports rarely goes smoothly. Here's my current collection of patches, as of svn version 340877. No patch for this, but with the replacement of openoffice-3 with openoffice-4, portmaster dies when trying to install openoffice-4 without having removed

sage 6.1.1

2014-02-16 Thread Ajtim
Hi! My system: FreeBSD 10.0-RELEASE #1: Mon Jan 20 12:44:17 EST 2014 /usr/obj/usr/src/sys/GENERIC amd64 I give a try again to sgae 6.1.1 and it doesn't build still on my system. Please, check attached log. -- Mitja --- http://www.redbubble.com/people/lumiwa __

Re: Redport builds are all "finished" without logs

2014-02-16 Thread Bernhard Fröhlich
Am 15.02.2014 21:07 schrieb "John W. O'Brien" : > > On 2/15/14 12:53 PM, John W. O'Brien wrote: > > On 2/10/14 9:52 AM, John W. O'Brien wrote: > >> Could you help me understand what's going on with this build [0]? Did an > >> admin kill the job, and if so, why? Otherwise, what happened and is it >

Re: Redport builds are all "finished" without logs

2014-02-16 Thread Bernhard Fröhlich
Am 15.02.2014 21:07 schrieb "John W. O'Brien" : > > On 2/15/14 12:53 PM, John W. O'Brien wrote: > > On 2/10/14 9:52 AM, John W. O'Brien wrote: > >> Could you help me understand what's going on with this build [0]? Did an > >> admin kill the job, and if so, why? Otherwise, what happened and is it >

Re: Why would a port use its own existence as an excuse to fail install?

2014-02-16 Thread RW
On Sat, 15 Feb 2014 22:14:54 -0600 Matthew D. Fuller wrote: > A nice thing about portmaster is that it's smarter than portupgrade. > ... > In this case, I'd guess, portmaster ... Which fails, since it's > already installed, thus... For me portupgrade did that upgrade perfectly even though I forg

Re: pkg-static segfaults when a port makes a package in chroot/nanobsd.

2014-02-16 Thread Alfred Perlstein
I have a ticket open in github for this, but I wanted to mail in and let people know that I figured the problem out somewhat: https://github.com/freebsd/pkg/issues/729 OK I sort of figured it out. Basically the build script that I have issues the following command: TARGET=amd64 TARGET_ARCH=am

Re: Update for graphics/libopenraw failed

2014-02-16 Thread Randy Pratt
On Thu, 13 Feb 2014 19:22:25 -0800 (PST) Robert English wrote: > Had a similar problem on my 8.4-Release system. After looking at the > "config.log" file, figured out it was looking for > "libboost_unit_test_framework_gcc42.so" so I made a soft link in the > "usr/local/lib" directory with that

install error nvidia-driver 331.20

2014-02-16 Thread Marco Beishuizen
Hi, I'm getting an install error when installing the nvidia-driver 331.20 from ports: ... Creating bzip'd tar ball in '/usr/ports/x11/nvidia-driver/work/nvidia-driver-331.20.tbz' tar: lib/libEGL.so: Cannot stat: No such file or directory tar: lib/libEGL.so.1: Cannot stat: No such file or dir

Re: New port cad/fritzing

2014-02-16 Thread Lars Engels
On Wed, Nov 07, 2012 at 03:34:35PM -0200, Sergio de Almeida Lenzi wrote: > Em Qua, 2012-11-07 às 21:37 +1000, Robert Backhaus escreveu: > > > I had not problems building, but when I run, I get error messages: > > > > Dialog: Sorry, we have a problem with the swapping mechanism. Fritzing > > still

graphics/digikam-kde4 does not build on HEAD

2014-02-16 Thread Rainer Hurling
When I try to build graphics/digikam-kde4 on recent HEAD amd64 I get the following error, complaining about missing -fPIC in graphics/opencv. [ 36%] Building CXX object digikam/CMakeFiles/digikamcore.dir/__/utilities/imageeditor/plugin/imagepluginloader.o [ 36%] Building CXX object digikam/CMakeF

FreeBSD ports you maintain which are out of date

2014-02-16 Thread 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