Re: 11-CURRENT iconv build failures

2014-02-20 Thread Thomas Mueller
from CiPHER nl:

> I'm running FreeBSD 11-CURRENT r262235 (as of this morning) and building 
> Virtualbox from ports (emulators/virtualbox-ose) fails for me.
> The Makefile contains USES=iconv. Removing that did not make it use the 
> libiconv from ports instead of base iconv, as i had expected.
> Any pointers to how to get this fixed would be welcome. :)

I think you can put a line in /etc/src.conf
WITHOUT_ICONV=yes

and then build the ports version.  Would that help?  I might try that, but how 
to find which already-built ports depend on iconv?

Thomas Mueller

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


ports/186931 Misassigned to Former Maintainer

2014-02-20 Thread Ryan Frederick
Earlier today I submitted ports/186931 (Request Commit of ports/184011 
-- Patch for Preliminary pkgng Support in net-mgmt/nagios-check_ports) 
as a maintainer-update. However the GNATS Auto Assign Tool misassigned 
the pr to the port's former maintainer stating that I am not the 
maintainer. Could someone correct this for me?


Thanks,
Ryan
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: docbook again (almost there)

2014-02-20 Thread Ryan Frederick
The port creating those files is textproc/xmlcatmgr. I deinstalled all
ports on the affected systems that depend on textproc/xmlcatmgr along with
textproc/xmlcatmgr itself, removed /usr/local/share/xml, and reinstalled
textproc/xmlcatmgr  along with the previously deinstalled ports.

Ryan
Hello

can someone tell me what package creates the files:
/usr/local/share/xml/catalog
/usr/local/share/xml/catalog.ports

After the upgrade those files are missing and I could not find
what package or does create those files.


Thanks in advance,

Sergio
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


docbook again (almost there)

2014-02-20 Thread Sergio de Almeida Lenzi
Hello

can someone tell me what package creates the files:
/usr/local/share/xml/catalog
/usr/local/share/xml/catalog.ports

After the upgrade those files are missing and I could not find
what package or does create those files.


Thanks in advance,

Sergio
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: mediatomb

2014-02-20 Thread jcv



On Thu, 20 Feb 2014, Tijl Coosemans wrote:


On Thu, 20 Feb 2014 11:02:08 -0800 (PST) jcv wrote:

On Thu, 20 Feb 2014, Tijl Coosemans wrote:

On Thu, 20 Feb 2014 09:03:49 -0800 (PST) jcv wrote:

On Thu, 20 Feb 2014, Tijl Coosemans wrote:

On Thu, 20 Feb 2014 07:11:32 -0800 (PST) jcv wrote:

On Thu, 20 Feb 2014, Tijl Coosemans wrote:

On Tue, 11 Feb 2014 12:16:16 -0800 (PST) jcv wrote:

Hi - I am seeing alot of emails regarding libiconv..  Is there a work
around for mediatomb per chance??


It should work now after r345236.


Hi Tijl - Can you please advise my next steps.. I am still seeing:


Hmm, check that you actually have the fix.  The Makefile should have
this id:

$FreeBSD: head/net/mediatomb/Makefile 345236 2014-02-20 14:38:19Z tijl $

Check that you don't have any local modifications in the port or in
/usr/ports/Mk, particularly /usr/ports/Mk/Uses/iconv.mk.

If all of that checks out then send me this file:
/usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log.


Hi Tijl -  I have not modified anything in /usr/ports/Mk.

Here is what Im running:


uname -a
FreeBSD yeaguy.com 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan
16 22:34:59 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64


Thanks alot for your help:



cat /usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log


What is the output of this:

cd /usr/ports/net/mediatomb
make -V CPPFLAGS

It should be: -DLIBICONV_PLUG
If that's not the case, what's the output of this:

cd /usr/ports/net/mediatomb
grep USES Makefile


I sent you the config.log but its being approved first:


I already received it.


Here are the other cmds:

root@yeaguy:/usr/ports/net/mediatomb # make -V CPPFLAGS

root@yeaguy:/usr/ports/net/mediatomb # grep USES Makefile
root@yeaguy:/usr/ports/net/mediatomb #
root@yeaguy:/usr/ports/net/mediatomb #


This means you don't have the fix.  Try updating your ports tree
again.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"




Got it working, I just updated /usr/ports/net/mediatomb with svn and its 
working now..  Thank you so much..



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: What should be in scripts shebangs for python2?

2014-02-20 Thread Marcus von Appen
On, Thu Feb 20, 2014, Lev Serebryakov wrote:

> Hello, Marcus.
> You wrote 20 февраля 2014 г., 12:06:46:
>
> MvA> No, USE_PYTHON_BUILD=2 should provide lang/python2, which will install
> MvA> /usr/local/bin/python2. This works for many ports, so I have no idea,
> MvA> what's wrong
>  It works locally, but "pkg-fallout-buil...@freebsd.org" sends me e-mails,
> where I see, that its software installs python27 but not python2 as dependency
> and it fails:
>
> http://beefy2.isc.freebsd.org/bulk/91amd64-default/2014-02-19_20h54m43s/logs/libopencm3-0.0.20140213.log

I can't recreate this in a local poudriere environment, so I have no idea,
what is going on on the build cluster. Excerpt from the local build:

[...]
===>   Returning to build of libopencm3-0.0.20140218
===>   libopencm3-0.0.20140218 depends on executable: python2 - not found
===>Verifying install for python2 in /usr/ports/lang/python2
===>   Installing existing package /packages/All/python2-2_2.txz
Installing python2-2_2... done
===>   Returning to build of libopencm3-0.0.20140218
===>   libopencm3-0.0.20140218 depends on executable: gmake -
[...]

The port looks fine, make all-depends-list correctly lists lang/python2,
stage builds work and all my poudriere installations handle it properly.
My best guess is, that something on the build cluster (or that specific
instance) goes wrong.

Cheers
Marcus


pgpkhqo1RyBxj.pgp
Description: PGP signature


Re: 11-CURRENT iconv build failures

2014-02-20 Thread Mike Jakubik
Same problem on 10-stable, I am unable to compile many ports including a 
VirtualBox which I depend on a daily basis.


On 02/20/14 14:27, CiPHER nl wrote:

Hello,

I'm running FreeBSD 11-CURRENT r262235 (as of this morning) and building 
Virtualbox from ports (emulators/virtualbox-ose) fails for me.
The Makefile contains USES=iconv. Removing that did not make it use the 
libiconv from ports instead of base iconv, as i had expected.
Any pointers to how to get this fixed would be welcome. :)


 kBuild: Compiling VBox-kStuffStaticBldProg - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/libs/kStuff/iprt/kRdrFile-iprt.cpp
 kBuild: Linking VBox-kStuffStaticBldProg
 kBuild: Installing VBox-kStuffStaticBldProg => 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/VBox-kStuffStaticBldProg.a
 kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scm.cpp
 kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmdiff.cpp
 kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmrw.cpp
 kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmstream.cpp
 kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmsubversion.cpp
 kBuild: Linking scm
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o):
 In function `rtstrConvertCached':
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:200:
 undefined reference to `libiconv'
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:184:
 undefined reference to `libiconv_open'
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:244:
 undefined reference to `libiconv_close'
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o):
 In function `rtStrConvertUncached':
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:315:
 undefined reference to `libiconv_open'
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:330:
 undefined reference to `libiconv'
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:351:
 undefined reference to `libiconv_close'
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:340:
 undefined reference to `libiconv_close'
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o):
 In function `rtStrIconvCacheDestroy':
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:115:
 undefined reference to `libiconv_close'
 collect2: ld returned 1 exit status
 kmk: *** 
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm]
 Error 1
 The failing command:
 @g++46-m64   -o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmdiff.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmrw.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmstream.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmsubversion.o
   -L/usr/local/lib   -lpthread   -lrt   
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a
   
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/VBox-kStuffStaticBldProg.a
   
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/rel

ease/lib/RuntimeBldProg.a   -lpthread   -lssl   -lcrypto

 *** Error code 2
  
 Stop.

 make[1]: stopped in /usr/ports/emulators/virtualbox-ose
 *** Error code 1
  
 Stop.

 make: stopped in /usr/ports/emulators/virtualbox-ose   

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports

Re: mediatomb

2014-02-20 Thread Tijl Coosemans
On Thu, 20 Feb 2014 11:02:08 -0800 (PST) jcv wrote:
> On Thu, 20 Feb 2014, Tijl Coosemans wrote:
>> On Thu, 20 Feb 2014 09:03:49 -0800 (PST) jcv wrote:
>>> On Thu, 20 Feb 2014, Tijl Coosemans wrote:
 On Thu, 20 Feb 2014 07:11:32 -0800 (PST) jcv wrote:
> On Thu, 20 Feb 2014, Tijl Coosemans wrote:
>> On Tue, 11 Feb 2014 12:16:16 -0800 (PST) jcv wrote:
>>> Hi - I am seeing alot of emails regarding libiconv..  Is there a work
>>> around for mediatomb per chance??
>>
>> It should work now after r345236.
>
> Hi Tijl - Can you please advise my next steps.. I am still seeing:

 Hmm, check that you actually have the fix.  The Makefile should have
 this id:

 $FreeBSD: head/net/mediatomb/Makefile 345236 2014-02-20 14:38:19Z tijl $

 Check that you don't have any local modifications in the port or in
 /usr/ports/Mk, particularly /usr/ports/Mk/Uses/iconv.mk.

 If all of that checks out then send me this file:
 /usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log.
>>>
>>> Hi Tijl -  I have not modified anything in /usr/ports/Mk.
>>>
>>> Here is what Im running:
>>>
>>>
>>> uname -a
>>> FreeBSD yeaguy.com 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan
>>> 16 22:34:59 UTC 2014
>>> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>>>
>>>
>>> Thanks alot for your help:
>>>
>>>
>>>
>>> cat /usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log
>>
>> What is the output of this:
>>
>> cd /usr/ports/net/mediatomb
>> make -V CPPFLAGS
>>
>> It should be: -DLIBICONV_PLUG
>> If that's not the case, what's the output of this:
>>
>> cd /usr/ports/net/mediatomb
>> grep USES Makefile
>
> I sent you the config.log but its being approved first:

I already received it.

> Here are the other cmds:
> 
> root@yeaguy:/usr/ports/net/mediatomb # make -V CPPFLAGS
> 
> root@yeaguy:/usr/ports/net/mediatomb # grep USES Makefile
> root@yeaguy:/usr/ports/net/mediatomb #
> root@yeaguy:/usr/ports/net/mediatomb #

This means you don't have the fix.  Try updating your ports tree
again.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: mediatomb

2014-02-20 Thread jcv



On Thu, 20 Feb 2014, Tijl Coosemans wrote:


On Thu, 20 Feb 2014 09:03:49 -0800 (PST) jcv wrote:

On Thu, 20 Feb 2014, Tijl Coosemans wrote:

On Thu, 20 Feb 2014 07:11:32 -0800 (PST) jcv wrote:

On Thu, 20 Feb 2014, Tijl Coosemans wrote:

On Tue, 11 Feb 2014 12:16:16 -0800 (PST) jcv wrote:

Hi - I am seeing alot of emails regarding libiconv..  Is there a work
around for mediatomb per chance??


It should work now after r345236.


Hi Tijl - Can you please advise my next steps.. I am still seeing:


Hmm, check that you actually have the fix.  The Makefile should have
this id:

$FreeBSD: head/net/mediatomb/Makefile 345236 2014-02-20 14:38:19Z tijl $

Check that you don't have any local modifications in the port or in
/usr/ports/Mk, particularly /usr/ports/Mk/Uses/iconv.mk.

If all of that checks out then send me this file:
/usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log.


Hi Tijl -  I have not modified anything in /usr/ports/Mk.

Here is what Im running:


uname -a
FreeBSD yeaguy.com 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan
16 22:34:59 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64


Thanks alot for your help:



cat /usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log


What is the output of this:

cd /usr/ports/net/mediatomb
make -V CPPFLAGS

It should be: -DLIBICONV_PLUG
If that's not the case, what's the output of this:

cd /usr/ports/net/mediatomb
grep USES Makefile



I sent you the config.log but its being approved first:

Here are the other cmds:



root@yeaguy:/usr/ports/net/mediatomb # make -V CPPFLAGS

root@yeaguy:/usr/ports/net/mediatomb # grep USES Makefile
root@yeaguy:/usr/ports/net/mediatomb #
root@yeaguy:/usr/ports/net/mediatomb #


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


11-CURRENT iconv build failures

2014-02-20 Thread CiPHER nl
Hello,

I'm running FreeBSD 11-CURRENT r262235 (as of this morning) and building 
Virtualbox from ports (emulators/virtualbox-ose) fails for me.
The Makefile contains USES=iconv. Removing that did not make it use the 
libiconv from ports instead of base iconv, as i had expected.
Any pointers to how to get this fixed would be welcome. :)


    kBuild: Compiling VBox-kStuffStaticBldProg - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/libs/kStuff/iprt/kRdrFile-iprt.cpp
    kBuild: Linking VBox-kStuffStaticBldProg
    kBuild: Installing VBox-kStuffStaticBldProg => 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/VBox-kStuffStaticBldProg.a
    kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scm.cpp
    kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmdiff.cpp
    kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmrw.cpp
    kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmstream.cpp
    kBuild: Compiling scm - 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/bldprogs/scmsubversion.cpp
    kBuild: Linking scm
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o):
 In function `rtstrConvertCached':
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:200:
 undefined reference to `libiconv'
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:184:
 undefined reference to `libiconv_open'
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:244:
 undefined reference to `libiconv_close'
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o):
 In function `rtStrConvertUncached':
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:315:
 undefined reference to `libiconv_open'
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:330:
 undefined reference to `libiconv'
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:351:
 undefined reference to `libiconv_close'
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:340:
 undefined reference to `libiconv_close'
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a(utf8-posix.o):
 In function `rtStrIconvCacheDestroy':
    
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/Runtime/r3/posix/utf8-posix.cpp:115:
 undefined reference to `libiconv_close'
    collect2: ld returned 1 exit status
    kmk: *** 
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm]
 Error 1
    The failing command:
    @g++46    -m64   -o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scm.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmdiff.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmrw.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmstream.o
 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/obj/scm/scmsubversion.o
   -L/usr/local/lib   -lpthread   -lrt   
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a
   
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/VBox-kStuffStaticBldProg.a
   
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/out/freebsd.amd64/release/lib/RuntimeBldProg.a
   -lpthread   -lssl   -lcrypto
    *** Error code 2
 
    Stop.
    make[1]: stopped in /usr/ports/emulators/virtualbox-ose
    *** Error code 1
 
    Stop.
    make: stopped in /usr/ports/emulators/virtualbox-ose
  
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: mediatomb

2014-02-20 Thread Tijl Coosemans
On Thu, 20 Feb 2014 09:03:49 -0800 (PST) jcv wrote:
> On Thu, 20 Feb 2014, Tijl Coosemans wrote: 
>> On Thu, 20 Feb 2014 07:11:32 -0800 (PST) jcv wrote:
>>> On Thu, 20 Feb 2014, Tijl Coosemans wrote:
 On Tue, 11 Feb 2014 12:16:16 -0800 (PST) jcv wrote:
> Hi - I am seeing alot of emails regarding libiconv..  Is there a work
> around for mediatomb per chance??

 It should work now after r345236.
>>>
>>> Hi Tijl - Can you please advise my next steps.. I am still seeing:
>>
>> Hmm, check that you actually have the fix.  The Makefile should have
>> this id:
>>
>> $FreeBSD: head/net/mediatomb/Makefile 345236 2014-02-20 14:38:19Z tijl $
>>
>> Check that you don't have any local modifications in the port or in
>> /usr/ports/Mk, particularly /usr/ports/Mk/Uses/iconv.mk.
>>
>> If all of that checks out then send me this file:
>> /usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log.
> 
> Hi Tijl -  I have not modified anything in /usr/ports/Mk.
> 
> Here is what Im running:
> 
> 
> uname -a
> FreeBSD yeaguy.com 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 
> 16 22:34:59 UTC 2014 
> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> 
> Thanks alot for your help:
> 
> 
> 
> cat /usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log

What is the output of this:

cd /usr/ports/net/mediatomb
make -V CPPFLAGS

It should be: -DLIBICONV_PLUG
If that's not the case, what's the output of this:

cd /usr/ports/net/mediatomb
grep USES Makefile

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


[QAT] r345251: 8x leftovers

2014-02-20 Thread Ports-QAT
Update dns/maradns to 2.0.09.

Copy maradns 1.4.14 to dns/maradns1.

Sponsored by:   Absolight
-

  Build ID:  20140220154600-58528
  Job owner: m...@freebsd.org
  Buildtime: 75 minutes
  Enddate:   Thu, 20 Feb 2014 17:00:51 GMT

  Revision:  r345251
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=345251

-

Port:dns/maradns 2.0.09

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281960/maradns-2.0.09.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281961/maradns-2.0.09.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281962/maradns-2.0.09.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281963/maradns-2.0.09.log

-

Port:dns/maradns1 1.4.14

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281964/maradns1-1.4.14.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281965/maradns1-1.4.14.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281966/maradns1-1.4.14.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220154600-58528-281967/maradns1-1.4.14.log


--
Buildarchive URL: 
redports 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: mediatomb

2014-02-20 Thread Tijl Coosemans
On Thu, 20 Feb 2014 07:11:32 -0800 (PST) jcv wrote:
> On Thu, 20 Feb 2014, Tijl Coosemans wrote:
>> On Tue, 11 Feb 2014 12:16:16 -0800 (PST) jcv wrote:
>>> Hi - I am seeing alot of emails regarding libiconv..  Is there a work
>>> around for mediatomb per chance??
>>
>> It should work now after r345236.
> 
> Hi Tijl - Can you please advise my next steps.. I am still seeing:

Hmm, check that you actually have the fix.  The Makefile should have
this id:

$FreeBSD: head/net/mediatomb/Makefile 345236 2014-02-20 14:38:19Z tijl $

Check that you don't have any local modifications in the port or in
/usr/ports/Mk, particularly /usr/ports/Mk/Uses/iconv.mk.

If all of that checks out then send me this file:
/usr/ports/net/mediatomb/work/mediatomb-0.12.1/config.log.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: mediatomb

2014-02-20 Thread jcv



On Thu, 20 Feb 2014, Tijl Coosemans wrote:


On Tue, 11 Feb 2014 12:16:16 -0800 (PST) jcv wrote:

Hi - I am seeing alot of emails regarding libiconv..  Is there a work
around for mediatomb per chance??


It should work now after r345236.



Hi Tijl - Can you please advise my next steps.. I am still seeing:


--- all-recursive ---
Making all in build
Making all in build
--- mediatomb ---
c++ -I../src  -I../tombupnp/ixml/inc  -I../tombupnp/threadutil/inc 
-I../tombupnp/upnp/inc  -I..-I/usr/local/include/mysql -pipe 
-fno-strict-aliasing -g -DNDEBUG  -I/usr/local/include 
-I/usr/local/include  -I/usr/local/include-D_THREAD_SAFE 
-I/usr/local/include  -I/usr/local/include  -I/usr/local/include 
-I/usr/local/include   -O2 -pipe -fno-strict-aliasing   -pthread  -lmagic 
-o mediatomb mediatomb-main.o libmediatomb.a 
../tombupnp/build/libtombupnp.a  -L/usr/local/lib-L/usr/local/lib 
-L/usr/local/lib-L/usr/local/lib -L/usr/local/lib 
-L/usr/local/lib-pthread-L/usr/local/lib/mysql -lmysqlclient_r 
-pthread -lm  -L/usr/local/lib -ljs  -lmagic  -lid3  -lexif  -lz  -lrt 
-D_THREAD_SAFE  -pthread  -lavformat -lavutil  -lffmpegthumbnailer 
-lexpat  -lmp4v2-L/usr/local/lib -lcurl -lssl -lcrypto -L/usr/lib 
-lgssapi -lheimntlm -lkrb5 -lhx509 -lcom_err -lcrypto -lasn1 -lwind 
-lheimbase -lroken -lcrypt -pthread -lz -lcurl

/usr/bin/ld: : invalid DSO for symbol `libiconv_open' definition
//usr/local/lib/libiconv.so.3: could not read symbols: Bad value
c++: error: linker command failed with exit code 1 (use -v to see 
invocation)

*** [mediatomb] Error code 1

make[4]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1/build
1 error

make[4]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1/build
*** [all-recursive] Error code 1

make[3]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
1 error

make[3]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
*** [all] Error code 2

make[2]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
1 error

make[2]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure 
to

the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/net/mediatomb
*** Error code 1

Stop.
make: stopped in /usr/ports/net/mediatomb
root@yeaguy:/usr/ports/net/mediatomb #
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


[QAT] r345219: 11x leftovers, 4x depend (ignored: please enable with_new_xorg, libglesv2 needs libdrm higher then 2.4.24 in graphics/libglesv2), 1x depend (runaway_process in x11/kde4-runtime)

2014-02-20 Thread Ports-QAT
- Fix plist after recent KDE SC update
-

  Build ID:  20140220115401-61144
  Job owner: m...@freebsd.org
  Buildtime: 4 hours
  Enddate:   Thu, 20 Feb 2014 16:04:54 GMT

  Revision:  r345219
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=345219

-

Port:audio/amarok-kde4 2.7.0_5

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281768/amarok-2.7.0_5.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (RUNAWAY_PROCESS IN X11/KDE4-RUNTIME)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281769/kde-runtime-4.12.2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281770/amarok-2.7.0_5.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281771/amarok-2.7.0_5.log

-

Port:deskutils/basket 1.81_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281772/basket-1.81_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281773/basket-1.81_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281774/basket-1.81_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281775/basket-1.81_2.log

-

Port:finance/kmymoney-kde4 4.6.4_3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281776/kmymoney-4.6.4_3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281777/kmymoney-4.6.4_3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281778/kmymoney-4.6.4_3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220115401-61144-281779/kmymoney-4.6.4_3.log

-

Port:x11-themes/kde4-style-oxygen-transparent 2013.01.02_3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (IGNORED: PLEASE ENABLE WITH_NEW_XORG, LIBGLESV2 
NEEDS LIBDRM HIGHER THEN 2.4.24 IN GRAPHICS/LIBGLESV2)

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (IGNORED: PLEASE ENABLE WITH_NEW_XORG, LIBGLESV2 
NEEDS LIBDRM HIGHER THEN 2.4.24 IN GRAPHICS/LIBGLESV2)

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   DEPEND (IGNORED: PLEASE ENABLE WITH_NEW_XORG, LIBGLESV2 
NEEDS LIBDRM HIGHER THEN 2.4.24 IN GRAPHICS/LIBGLESV2)

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   DEPEND (IGNORED: PLEASE ENABLE WITH_NEW_XORG, LIBGLESV2 
NEEDS LIBDRM HIGHER THEN 2.4.24 IN GRAPHICS/LIBGLESV2)


--
Buildarchive URL: 
redports 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: How do submit updates to ports?

2014-02-20 Thread Warren Block

On Thu, 20 Feb 2014, Fernando Apesteguía wrote:


El 20/02/2014 02:28, "A.J. 'Fonz' van Werven" 
escribió:


Daniel Morante wrote:


How do I send updates to ports that I created/maintain?


Send a PR, either by using send-pr(1) or through the web interface at
http://www.freebsd.org/send-pr.html

If you are the maintainer, be sure to set the class to maintainer-update.



Also have a look at the porters handbook for good practices

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/


The sections on submitting a PR lack specifics:

Enter a PR.
synopsis: [patch] category/portname: update category/portname to n.nnn
category: [ports]
   class: [maintainer-update]

Entering the category and portname in that format help the automatic 
scripts to identify the port and maintainer.  The second use could 
probably just be the portname.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: docbook updates fiasco continues...

2014-02-20 Thread Warren Block

On Thu, 20 Feb 2014, Serpent7776 wrote:


On Thu, 20 Feb 2014 12:05:07 +0100
kaltheat  wrote:


Hi,

just for the records:
The instructions in UPDATING did not work for me in tcsh (which is
standard shell in FreeBSD as far as I know). I had to switch to bourne
shell (/bin/sh) to pkg delete docbook-ports.


Same for me. I think all special symbols should be escaped, so
pkg_delete -f docbook-xml* docbook-sk* docbook[2345]??-* docbook-4*
should be
pkg_delete -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\*


Right.  I noticed this yesterday, and after testing and feedback, fixed 
UPDATING earlier today.  Sorry about the delay.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


[QAT] r345222: 20x leftovers, 4x ???, 4x depend (ignored: does not build with qt 4.8 in ports-mgmt/packagekit-qt4), 20x success, 4x depend (ignored: please enable with_new_xorg, libglesv2 needs libdrm

2014-02-20 Thread Ports-QAT
- Add stage support
- Squeeze MASTER_SITES/MASTER_SITE_SUBDIR
- Convert LIB_DEPENDS to new style
- Use options helpers
- Remove useless LATEST_LINK
-

  Build ID:  20140220130200-56805
  Job owner: m...@freebsd.org
  Buildtime: 2 hours
  Enddate:   Thu, 20 Feb 2014 15:30:00 GMT

  Revision:  r345222
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=345222

-

Port:audio/taglib-extras 1.0.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281792/taglib-extras-1.0.1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281793/taglib-extras-1.0.1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281794/taglib-extras-1.0.1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281795/taglib-extras-1.0.1.log

-

Port:devel/automoc4 0.9.88_3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281796/automoc4-0.9.88_3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281797/automoc4-0.9.88_3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281798/automoc4-0.9.88_3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281799/automoc4-0.9.88_3.log

-

Port:graphics/kcoloredit 2.0.0.4.4.0_3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281800/kcoloredit-2.0.0.4.4.0_3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281801/kcoloredit-2.0.0.4.4.0_3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281802/kcoloredit-2.0.0.4.4.0_3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281803/kcoloredit-2.0.0.4.4.0_3.log

-

Port:graphics/kiconedit 4.4.0_3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281804/kiconedit-4.4.0_3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281805/kiconedit-4.4.0_3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281806/kiconedit-4.4.0_3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281807/kiconedit-4.4.0_3.log

-

Port:graphics/kphotoalbum-kde4 4.4_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281808/kphotoalbum-4.4_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281809/kphotoalbum-4.4_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281810/kphotoalbum-4.4_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281811/kphotoalbum-4.4_1.log

-

Port:graphics/kpovmodeler 1.1.3.4.3.1_10

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140220130200-56805-281812/kpovmodeler-1.1.3.4.3.1_10.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redp

Re: could somebody please close ports/185614?

2014-02-20 Thread Ruslan Makhmatkhanov

Hello,

Christopher J. Ruwe wrote on 20.02.2014 18:45:

1) Could somebody with a commit bit please close ports/185614
(http://www.freebsd.org/cgi/query-pr.cgi?pr=185614) The issue I
reported has gone away (or never was a real problem, I do not
know).


Done, thanks for updating on this.


2) We recently had a huge discussion about piles of old PRs sitting in
GNATS and  gathering dust.

Would it be possible to grant reporters commit rights to "their" PR
so that they could close the report themselves (and document why,
of course)? As a reporter, I think it is my responsibility to
accompany "my" PR over it's life. At this moment, PR reporters
abilities are restricted to pestering freebsd-ports@, encouraging a
more active role would not hurt, wouldn't it?


Cheers and thanks,


I believe not with GNATS. But such a feature is available in bugzilla, 
that will replace our GNATS in future. In bugzilla user may mark his 
ticket as resolved at least.


--
Regards,
Ruslan

T.O.S. Of Reality
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Ports with duplicate LATEST_LINKs

2014-02-20 Thread Brad Davis
On Thu, Feb 20, 2014 at 04:56:36PM +0400, Ruslan Makhmatkhanov wrote:
> Ports Index build wrote on 20.02.2014 16:40:
> > Dear port maintainers,
> >
> > The following list includes ports maintained by you that have duplicate
> > LATEST_LINK values.  They should either be modified to use a unique
> > PKGNAME, e.g. by using PKGNAMESUFFIX.  Note that NO_LATEST_LINK is
> > deprecated.  See the portmgr blog post for more information:
> > http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/
> >
> >
> > Thanks,
> > Erwin "Annoying Reminder Guy III" Lansing
> >
> >
> > LATEST_LINK  PORTNAME   MAINTAINER
> > ==
> > liblogging   sysutils/libloggingb...@freebsd.org
> > liblogging   devel/liblogging   po...@freebsd.org
> >
> 
> Duplicate port has been added today in sysutils. May be it should be 
> removed and devel/liblogging should be taken/updated instead. Adding 
> sysutils port maintainer to Cc:.

Doh, I will fix it. Thanks!


Regards,
Brad Davis
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


could somebody please close ports/185614?

2014-02-20 Thread Christopher J. Ruwe
1) Could somebody with a commit bit please close ports/185614
   (http://www.freebsd.org/cgi/query-pr.cgi?pr=185614) The issue I
   reported has gone away (or never was a real problem, I do not
   know). 

2) We recently had a huge discussion about piles of old PRs sitting in
   GNATS and  gathering dust.

   Would it be possible to grant reporters commit rights to "their" PR
   so that they could close the report themselves (and document why,
   of course)? As a reporter, I think it is my responsibility to
   accompany "my" PR over it's life. At this moment, PR reporters
   abilities are restricted to pestering freebsd-ports@, encouraging a
   more active role would not hurt, wouldn't it?


Cheers and thanks,
-- 
Christopher 
TZ: GMT + 1h
GnuPG/GPG:  0xE8DE2C14
 
FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013
c...@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE
 
  
Punctuation matters:
"Lets eat Grandma." or "Lets eat, Grandma." - Punctuation saves lives.
"A panda eats shoots and leaves." or "A panda eats, shoots, and
leaves." - Punctuation teaches proper biology.

"With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead." (RFC 1925)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: mediatomb

2014-02-20 Thread Tijl Coosemans
On Tue, 11 Feb 2014 12:16:16 -0800 (PST) jcv wrote:
> Hi - I am seeing alot of emails regarding libiconv..  Is there a work 
> around for mediatomb per chance??

It should work now after r345236.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: mail/mu does not install mu4e

2014-02-20 Thread Eygene Ryabinkin
Jo!

Mon, Feb 17, 2014 at 04:45:29PM +0100, _1126 wrote:
> The port mail/mu builds its Emacs extension mu4e, but it does not
> install it. I had to manually copy 'work/mu4e' into
> '/usr/local/share/emacs/site-lisp/' in order to be able to use mu4e.
> 
> I am not yet experienced in working with ports, so I am not (yet) able
> to provide a patch, but maybe it is easy for you to do so ;)

Relatively easy.  The reason why I wasn't included mu4e is that I am
not using Emacs, so wasn't able to test it.  Will send you patch to
enable this in a couple of days.
-- 
Eygene Ryabinkin,,,^..^,,,
[ Life's unfair - but root password helps!   | codelabs.ru ]
[ 82FE 06BC D497 C0DE 49EC  4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]


pgpIQTTgNjGfD.pgp
Description: PGP signature


Re: VirtualBox & vim no longer building

2014-02-20 Thread Sunpoet Hsieh
On Thu, Feb 20, 2014 at 6:37 AM, Bryce Edwards  wrote:

> Here's the build logs with details:
>
> https://dl.dropboxusercontent.com/u/141097/virtualbox-ose-4.3.6.log
>
> https://dl.dropboxusercontent.com/u/141097/vim-7.4.182.log
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>

For editors/vim port, please run "make config" and turn on "CONSOLE" option.
Thanks.

Regards,
sunpoet
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: What should be in scripts shebangs for python2?

2014-02-20 Thread Lev Serebryakov
Hello, Marcus.
You wrote 20 февраля 2014 г., 12:06:46:

MvA> No, USE_PYTHON_BUILD=2 should provide lang/python2, which will install
MvA> /usr/local/bin/python2. This works for many ports, so I have no idea,  
MvA> what's wrong
 It works locally, but "pkg-fallout-buil...@freebsd.org" sends me e-mails,
where I see, that its software installs python27 but not python2 as dependency
and it fails:

http://beefy2.isc.freebsd.org/bulk/91amd64-default/2014-02-19_20h54m43s/logs/libopencm3-0.0.20140213.log

MvA> with your port. Do you mind to send me a shar of the port, so I can  
MvA> have a look?
 It is committed, devel/libopencm3
 Thank you!

-- 
// Black Lion AKA Lev Serebryakov 

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Ports with duplicate LATEST_LINKs

2014-02-20 Thread Ruslan Makhmatkhanov

Ports Index build wrote on 20.02.2014 16:40:

Dear port maintainers,

The following list includes ports maintained by you that have duplicate
LATEST_LINK values.  They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX.  Note that NO_LATEST_LINK is
deprecated.  See the portmgr blog post for more information:
http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/


Thanks,
Erwin "Annoying Reminder Guy III" Lansing


LATEST_LINK  PORTNAME   MAINTAINER
==
liblogging   sysutils/libloggingb...@freebsd.org
liblogging   devel/liblogging   po...@freebsd.org



Duplicate port has been added today in sysutils. May be it should be 
removed and devel/liblogging should be taken/updated instead. Adding 
sysutils port maintainer to Cc:.


--
Regards,
Ruslan

T.O.S. Of Reality
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Ports with duplicate LATEST_LINKs

2014-02-20 Thread Ports Index build
Dear port maintainers,

The following list includes ports maintained by you that have duplicate
LATEST_LINK values.  They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX.  Note that NO_LATEST_LINK is
deprecated.  See the portmgr blog post for more information:
http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/


Thanks,
Erwin "Annoying Reminder Guy III" Lansing


LATEST_LINK  PORTNAME   MAINTAINER  
==
liblogging   sysutils/libloggingb...@freebsd.org 
liblogging   devel/liblogging   po...@freebsd.org   

Total: 2 ports
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: docbook updates fiasco continues...

2014-02-20 Thread Dr. Peter Voigt
Am Thu, 20 Feb 2014 12:05:07 +0100
schrieb kaltheat :

> 
> Hi,
> 
> just for the records:
> The instructions in UPDATING did not work for me in tcsh (which is
> standard shell in FreeBSD as far as I know). I had to switch to bourne
> shell (/bin/sh) to pkg delete docbook-ports.
> 
> Regards,
> kaltheat
> 
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to
> "freebsd-ports-unsubscr...@freebsd.org"

Well, as allway I tried to upgrade without reading /usr/ports/UPDATING
before -). I usually go there only, if something goes wrong.

But this time, I did not even read UPDATING though I suddenly found
that the old docbook packages where still shown with "pkg version" but
where no longer installed: They have been marked as "orphaned
packages". At the same time I found missing dependencies. I manually
deinstalled the orphaned packages and installed the new docbook packages
and have run into next problems because docbook-utils could not be
upgraded.

And all the above problems occured right after having had trouble
because KDE could not be upgraded due to an error in docbook-xml.

Well, all together a lot of trouble with docbook packages. But now all
docbook related problems are solved and all packages are up to date
without portmaster/pkg detecting any dependency errors.

By the way: I am running FreeBSD 10.0-RELEASE with Bash as login shell
for root.

Regards,
Peter 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: docbook updates fiasco continues...

2014-02-20 Thread Serpent7776
On Thu, 20 Feb 2014 12:05:07 +0100
kaltheat  wrote:

> Hi,
> 
> just for the records:
> The instructions in UPDATING did not work for me in tcsh (which is
> standard shell in FreeBSD as far as I know). I had to switch to bourne
> shell (/bin/sh) to pkg delete docbook-ports.

Same for me. I think all special symbols should be escaped, so
pkg_delete -f docbook-xml* docbook-sk* docbook[2345]??-* docbook-4*
should be
pkg_delete -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\*

-- 
//
// Serpent7776
//

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Updating KDE

2014-02-20 Thread Max Brazhnikov
On Thu, 20 Feb 2014 05:50:15 -0500 Jerry wrote:
> I was just perusing  as shown in the
> UPDATING file regarding KDE4. I saw the following notation:
> 
> Enable in /etc/make.conf: 
> WITH_NEW_XORG=yes
> WITH_GALLIUM=yes 
> 
> I am running "FreeBSD 10.0-RELEASE #0 r260789" with a nVidia card using the
> latest nVidia driver available in the ports system. Do I have to enter that
> information shown above in my "/etc/make.conf" file prior to updating KDE?

For nvidia you need only WITH_NEW_XORG=yes.

Max
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: docbook updates fiasco continues...

2014-02-20 Thread kaltheat

Hi,

just for the records:
The instructions in UPDATING did not work for me in tcsh (which is
standard shell in FreeBSD as far as I know). I had to switch to bourne
shell (/bin/sh) to pkg delete docbook-ports.

Regards,
kaltheat

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Updating KDE

2014-02-20 Thread Jerry
I was just perusing  as shown in the
UPDATING file regarding KDE4. I saw the following notation:

Enable in /etc/make.conf: 
WITH_NEW_XORG=yes
WITH_GALLIUM=yes 

I am running "FreeBSD 10.0-RELEASE #0 r260789" with a nVidia card using the
latest nVidia driver available in the ports system. Do I have to enter that
information shown above in my "/etc/make.conf" file prior to updating KDE?

-- 
Jerry
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Port: emacs-nox11-24.3_10,3

2014-02-20 Thread Nicolas Edel
Hi,

Just to let you know the current port of emacs-nox11 (and probably
emacs) doesn't compile on FreeBSD-10.0/sparc64 target and relates to
patch-src_sysdep.c. Once applied, the src.sysdep.c files looks like:


#ifdef __FreeBSD__
#include 
#include 
#include 
#endif

#ifdef __FreeBSD__
#include 
/* machine/frame.h in Sparc/ARM has 'struct frame' which conflicts
with Emacs' 'struct frame', so rename it */
#if defined(__sparc__) || defined(__arm__)
#define frame freebsd_sparc_frame
#endif
#include 
#if defined(__sparc__) || defined(__arm__)
#undef frame
#endif
#include 
#include 
#endif


As you may notice, you patch add code but don't replace the old one.
It has therefore no effect. Please find attached the modified patch
(that wou'll prefer to generate by yourself, I know ^^).


Cheers,

:Nicolas
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


FreeBSD ports you maintain which are out of date

2014-02-20 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 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
+-+
www/groupoffice | 3.7.24  | 5.0.44
+-+


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
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Error build the port devel/glib20

2014-02-20 Thread Mark Knight
On 19/02/2014 13:21, Tijl Coosemans wrote:
> I had another look at it and it turns out to be problem during
> installation, not during compilation.  It should be fixed now in
> r345090.

Yes, that fixed it - thanks :)
-- 
Mark Knight
Mobile: +44 7753 250584.  http://www.knigma.org/
Email: ma...@knigma.org.  Skype: knigma
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: What should be in scripts shebangs for python2?

2014-02-20 Thread Marcus von Appen

Lev Serebryakov :


Hello, Marcus.
You wrote 19 февраля 2014 г., 19:55:00:


MvA> In short:
MvA> * Use ${PYTHON_CMD} to replace the shebang lines or references of the
MvA> python command
  So, it is not possible to use "static" patch? It is pity :(


It should be avoided, if possible. Especially, when it is a shebang  
line, since

we have a quite powerful mechanism to replace shebangs with minimal effort.


MvA> * Use the proper supported python version (yes for any, 2 or 3 for a
MvA> branch, X.Y for a release)
MvA>for USE_PYTHON_BUILD
 I've hoped, that USE_PYTHON_BUILD=2 guarantee me, that here is
/usr/local/bin/python2 in system, but looks like it depends on something
else.


No, USE_PYTHON_BUILD=2 should provide lang/python2, which will install
/usr/local/bin/python2. This works for many ports, so I have no idea,  
what's wrong
with your port. Do you mind to send me a shar of the port, so I can  
have a look?


[...]

Cheers
Marcus

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"