Re: Question about depends

2013-01-09 Thread Alexander Yerenkow
2013/1/6 Alexander Yerenkow yeren...@gmail.com

 Hello all.
 Update for nss and ca root produced rebuild of all packages in my
 poudriere :)
 Isn't it so necessary?
 Maybe there should be new type of dependency introduced - like,
 INFO_DEPENDS, means that no rebuilld of any depended packages required,
 they all only use some info from that package.
 Is there such type of dependency currently?
 Is there any reason why not introduce one?



Any feedback? Anyone? Any thought?


 --
 Regards,
 Alexander Yerenkow




-- 
Regards,
Alexander Yerenkow
___
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: devel/boost-libs looks hardwired for gcc/g++

2013-01-09 Thread Jakub Lach
Thanks for both replies, just for search reference, as a ugly hack, I've 
temporarily convinced my system that gcc is clang, and carried on... 

Didn't try with gcc47, as I think it was not buildable at all with it, last 
time I've checked.



--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/devel-boost-libs-looks-hardwired-for-gcc-g-tp5775942p5776038.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
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: Question about depends

2013-01-09 Thread Chris Rees
On 9 Jan 2013 10:05, Alexander Yerenkow yeren...@gmail.com wrote:

 2013/1/6 Alexander Yerenkow yeren...@gmail.com

  Hello all.
  Update for nss and ca root produced rebuild of all packages in my
  poudriere :)
  Isn't it so necessary?
  Maybe there should be new type of dependency introduced - like,
  INFO_DEPENDS, means that no rebuilld of any depended packages required,
  they all only use some info from that package.
  Is there such type of dependency currently?
  Is there any reason why not introduce one?
 


 Any feedback? Anyone? Any thought?

I think it's difficult.  Sure, sometimes the change is trivial, but
sometimes it may indeed require a rebuild.  Sounds like an unsafe method.

Chris
___
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: Re: kde4 rebuild - some guidance please

2013-01-09 Thread David Southwell

On 1/8/2013 5:45 PM, John Merryweather Cooper wrote:

On 01/05/13 05:23, David Southwell wrote:

Hi
I am having problems with my kde4 installation and feel the need to
deinstall and start again.
In view of the number of ports and dependencies can someone please let
me know the cleanest way of doing this. It would probably be safer to
assume an upwards and downwards recursive build.
Thanks in advance
david



I just used:

# pourtmaster --force-config x11/kde4 to rebuild my KDE4 from scratch.

You can also pass the -f switch to rebuild in place, although I prefer 
blowing away and starting fresh.

--
John M. Cooper


Hi

Thanks very much.

 I eventually solved the problems by the following a rather labourious 
sequence. with a significant number of manual interventions in the 
process of upgrading python ports. I now suspect the problems were 
primarily due to some conflicts in the python ports.

Here is what worked:
# portupgrade -f   *py*
# portupgrade -fr *kde*
# portupgrade -fr *xorg*

David





--
David Southwell ARPS AFIAP
Photographic Arts
Trained  experienced competition judge, mentor, trainer, lecturer,
Advanced digital techniques, international project photography

___
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


portupgrade/portversion and detecting lower versions

2013-01-09 Thread Oliver Lehmann

Hi,

I regulary use portversion to check if I have outdated ports installed.
Since some time I'm now getting false matches:


portversion -v | grep ''
horde-imp-6.0.2   needs updating (port has 4.3.11_1,1)  
(= 'mail/horde3-imp')
horde-ingo-3.0.1  needs updating (port has 1.2.6_1,1) (=  
'mail/horde3-ingo')
horde-kronolith-4.0.2 needs updating (port has 2.3.6_1,1) (=  
'deskutils/horde3-kronolith')




Why are they reported and how can I avoid this?
___
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: portupgrade/portversion and detecting lower versions

2013-01-09 Thread Matthew Seaman
On 09/01/2013 12:07, Oliver Lehmann wrote:
 Hi,
 
 I regulary use portversion to check if I have outdated ports installed.
 Since some time I'm now getting false matches:
 
 portversion -v | grep ''
 horde-imp-6.0.2   needs updating (port has 4.3.11_1,1) (=
 'mail/horde3-imp')
 horde-ingo-3.0.1  needs updating (port has 1.2.6_1,1) (=
 'mail/horde3-ingo')
 horde-kronolith-4.0.2 needs updating (port has 2.3.6_1,1) (=
 'deskutils/horde3-kronolith')

 
 Why are they reported and how can I avoid this?

Two possibilities:

i) You've switched to pkgng but portversion still thinks you're using
pkg_tools for whatever reason.

How does the portversion output compare with:

pkg version -vIL=
pkg version -vPL=

(the first uses /usr/ports/INDEX-?, the second looks at port directories
un ${PORTSDIR}, which takes a bit longer but is more accurate.)

ii) You're still using the old-stlye pkg_tools, but you've got an
out-of-date INDEX file?  How does the portversion output compare with:

   pkg_version -vIL=
   pkg_version -vL=

Cheers,

Matthew

___
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


circular dependency issue

2013-01-09 Thread Joseph A. Nagy, Jr
I'm trying to install x11-wm/hs-xmonad but it keeps getting caught in a 
circular dependency with print/hs-hscolour


Is anyone else having issues with it?

http://pastebin.com/brjjV2pW
--
Yours in Christ,

Joseph A Nagy Jr
Whoever loves instruction loves knowledge, But he who hates correction
is stupid. -- Proverbs 12:1
Emails are not formal business letters, whatever businesses may want.
Original content CopyFree (F) under the OWL http://owl.apotheon.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


Re: circular dependency issue

2013-01-09 Thread Gabor Pali
On Wed, Jan 9, 2013 at 2:06 PM, Joseph A. Nagy, Jr
jnagyjr1...@gmail.com wrote:
 I'm trying to install x11-wm/hs-xmonad but it keeps getting caught in a
 circular dependency with print/hs-hscolour

 Is anyone else having issues with it?

You get this if you have the option HSCOLOUR set.  Disable this option
for hs- ports (this is disable by default) or install/update
print/hs-hscolour separately.  The circular dependency is because
HsColour cannot generate HsColourized documentation for itself -- so
you will have to install it without HSCOLOUR first, then build it with
HSCOLOUR, remove the old version and replace it with the new one.  Or
simply just omit the HsColourized documentation (or the documentation
at all) for print/hs-hscolour.

I am not sure that port update tools like portmaster, portupgrade and
friends will support this so you will have to do it yourself manually.

Hope that helps.
___
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: portupgrade/portversion and detecting lower versions

2013-01-09 Thread Torfinn Ingolfsen
On Wed, Jan 9, 2013 at 1:07 PM, Oliver Lehmann lehm...@ans-netz.de wrote:
 Hi,

 I regulary use portversion to check if I have outdated ports installed.
 Since some time I'm now getting false matches:

 portversion -v | grep ''

Note that portversion supports the '-L' parameter, no need for grep.
HTH
-- 
Regards,
Torfinn Ingolfsen
___
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: Why delete KDE3 ports?

2013-01-09 Thread Mikhail T.

On 08.01.2013 19:02, Jakub Lach wrote:

I'm on the fence. It's true, that there is no low-print feature complete
equivalent for KDE3.
Worse, KDE4 is not only much heavier (which could've been acceptable). 
It is also not compatible -- people like myself, who customized their 
desktops with additional menus, who created knotes, etc. will have to 
redo all of their settings. KDE4, as built, is not even going to look 
under the ~/.kde. Though it can be compiled to consider the old 
directory, the format/syntax for many of the config-files has changed -- 
and there is no upgrade path.

On the other hand, if nobody wants to maintain Trinity, well
it should be letten go, as sooner or later there will be problems.
Before becoming maintained, Trinity first needs to be ported -- a 
substantial effort, because, for example, the project switched to its 
own verstion Qt (Trinity Qt). All classes have been renamed from Qfoo to 
TQfoo...


This can all be handled, but meanwhile, until there ARE actual problems, 
leave the ports alone, please.


   -mi

___
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


multimedia/vlc does not find portaudio2

2013-01-09 Thread Jimmy Olgeni


Hi,

I found out that vlc does not find portaudio2 in my tinderbox, while 
it can find portaudio2 on a live system.


   http://93.62.141.59/tb/errors/9.1-amd64-x11/vlc-2.0.5,3.log

It behaves like the ${LDCONFIG} ${_LDCONFIG_FLAGS} -r check in 
bsd.port.mk is not able to see portaudio2 for some reason, even if it 
uses USE_LDCONFIG. Other dependencies look ok; the only difference is 
that portaudio2 lives in its own path under lib/.


Does anybody else see anything like this in their setup?

--
jimmy

___
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 requrest: OpenNMS

2013-01-09 Thread Paul Pathiakis
Hi,

I've requested this before, however, I still don't see it in the collection.

OpenNMS is an awesome tool for monitoring.  It takes SNMP and IPMI to an 
incredible level and the ability to monitor huge numbers of machines makes me a 
fan.  (Along with all the other features of course).  It even got me to switch 
off of NAGIOS as the amount of detail and trend graphing it provides is 
incredible.

Also, previously, my attempts surrounded a gentleman who seems to already be 
creating a FreeBSD package for it.

http://www.geeklan.co.uk/files/opennms/    -- Sevan has these files that he 
creates.  They are very useful although not an official 'port' at this time.

Thank you,  (and, no, working to create a PCBSD/FreeBSD consulting company does 
not leave me time to work on this. :-) )

Paul Pathiakis
___
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

2013-01-09 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
+-+
databases/py-PyGreSQL   | 4.1 | 4.1.1
+-+
games/uhexen2   | 1.5.1   | 1.5.5
+-+


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

If wish to stop receiving portscout reminders, please contact
portsc...@portscout.freebsd.org

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: Why delete KDE3 ports?

2013-01-09 Thread Jakub Lach
 tQT

Well, presumable to not use it with not maintained, old vanilla QT

In spite of not having 'proper' maintainer both kdelibs3/ and kdebas3/
saw substantial interest in form of patches, that indicates there are
more people who care about them, than those taking voice in this 
thread...



--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Why-delete-KDE3-ports-tp5775510p5776156.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
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


security/libssh ISSUE undefined reference to `__stack_chk_fail_local'

2013-01-09 Thread awarecons
FreeBSD 9.0-Release i386 for i386

GCC 4.6.3:

Linking C shared library libssh.so
CMakeFiles/ssh_shared.dir/agent.c.o: In function `agent_talk':
agent.c:(.text+0x3c9): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/channels.c.o: In function `ssh_channel_request_x11':
channels.c:(.text+0x3638): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/channels.c.o: In function `channel_read_buffer':
channels.c:(.text+0x44d3): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/client.c.o: In function `ssh_send_banner':
client.c:(.text+0x590): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/config.c.o: In function `.L46':
config.c:(.text+0x8c7): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/connect.c.o:connect.c:(.text+0xf7): more
undefined references to `__stack_chk_fail_local' follow
collect2: ld returned 1 exit status
*** Error code 1
1 error
*** Error code 2
[100%] Building C object src/CMakeFiles/ssh.dir/bind.c.o
Linking C static library libssh.a
[100%] Built target ssh
1 error
*** Error code 2
1 error
*** Error code 1

Stop in /usr/ports/security/libssh.
*** Error code 1

Stop in /usr/ports/security/libssh.

GCC 4.2: fine.
___
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


editors/libreoffice ISSUE webdav, icc/unxfbsdi.pro

2013-01-09 Thread awarecons
FreeBSD 9.0-Release i386 for i386

GCC 4.6.3:
---
Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 65280 occurred while making
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/xmloff/prj

 it seems that the error is inside 'xmloff', please re-run build
 inside this module to isolate the error and/or test your fix:
---

/usr/local/bin/bash
cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2
source ./Env.Host.sh
cd xmloff
gmake clean # optional
gmake -r

when the problem is isolated and fixed exit and re-run 'make' from the top-level
gmake[1]: *** [build] Error 1
gmake[1]: Leaving directory
`/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2'
gmake: *** [source-env-and-recurse] Error 2
*** Error code 1

Stop in /usr/ports/editors/libreoffice.
*** Error code 1

Stop in /usr/ports/editors/libreoffice.

Detailed error:

[ build CXX ] xmloff/source/style/PageMasterImportContext
R=/usr/ports/editors/libreoffice/work  S=$R/libreoffice-core-3.5.7.2
 O=$S/solver/unxfbsdi.pro  W=$S/workdir/unxfbsdi.pro   mkdir -p
$W/CxxObject/xmloff/source/style/
$W/Dep/CxxObject/xmloff/source/style/  g++46 -DCPPU_ENV=gcc3
-DENABLE_GRAPHITE -DENABLE_GTK -DENABLE_KDE4 -DFREEBSD -DGCC
-DGXX_INCLUDE_PATH=/usr/local/lib/gcc46/include/c++
-DHAVE_GCC_VISIBILITY_FEATURE -DHAVE_THREADSAFE_STATICS -DINTEL
-DNDEBUG -DOPTIMIZE -DOSL_DEBUG_LEVEL=0 -DPRODUCT -DSOLAR_JAVA
-DSUPD=350 -DUNIX -DUNX -DVCL -DX86 -D_PTHREADS -D_REENTRANT
-DXMLOFF_DLLIMPLEMENTATION   -Wall -Wendif-labels -Wextra
-fmessage-length=0 -fno-common -pipe  -fPIC -Wsign-promo
-Woverloaded-virtual -Wno-non-virtual-dtor -Wno-unused-parameter
-fvisibility=hidden  -fvisibility-inlines-hidden  -std=gnu++0x
-Wno-deprecated-declarations -Wno-deprecated   -DEXCEPTIONS_ON
-fexceptions -fno-enforce-eh-specs -O2 -c
$S/xmloff/source/style/PageMasterImportContext.cxx -o
$W/CxxObject/xmloff/source/style/PageMasterImportContext.o -MMD -MT
$W/CxxObject/xmloff/source/style/PageMasterImportContext.o -MP -MF
$W/Dep/CxxObject/xmloff/source/style/PageMasterImportContext.d
-I$S/xmloff/source/style/ -I$O/inc/stl -I$S/xmloff/inc
-I$O/inc/external -I$O/inc -I$S/solenv/inc/unxfbsdi -I$S/solenv/inc
-I$S/res -I/usr/local/openjdk6/include
-I/usr/local/openjdk6/include/freebsd
-I/usr/local/openjdk6/include/bsd -I/usr/local/openjdk6/include/linux
-I/usr/local/openjdk6/include/native_threads/include
-I/usr/local/include  -I$O/inc/udkapi -I$O/inc/offapi
[ build CXX ] xmloff/source/style/PageMasterImportPropMapper
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/xmloff/source/style/PageHeaderFooterContext.cxx:
In member function 'virtual SvXMLImportContext*
PageHeaderFooterContext::CreateChildContext(sal_uInt16, const
rtl::OUString, const
com::sun::star::uno::Referencecom::sun::star::xml::sax::XAttributeList)':
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/xmloff/source/style/PageHeaderFooterContext.cxx:91:1:
error: 'p' was not declared in this scope
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/xmloff/source/style/PageHeaderFooterContext.cxx:91:5:
error: expected ';' before 'return'
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/xmloff/source/style/PageHeaderFooterContext.cxx:92:1:
warning: no return statement in function returning non-void
[-Wreturn-type]
gmake[1]: *** 
[/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/workdir/unxfbsdi.pro/CxxObject/xmloff/source/style/PageHeaderFooterContext.o]
Error 1
gmake[1]: *** Waiting for unfinished jobs
gmake[1]: Leaving directory
`/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/xmloff'
gmake: *** [source-env-and-recurse] Error 2


GCC 4.2+:
---
Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 65280 occurred while making
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/ucb/source/ucp/webdav
ERROR: error 65280 occurred while making
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/l10ntools/source
ERROR: error 65280 occurred while making
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.7.2/icc/source/create_sRGB_profile

 it seems you are using a threaded build, which means that the
 actual compile error is probably hidden far above, and could be
 inside any of these other modules:
 ucb l10ntools
 please re-run build inside each one to isolate the problem.
---

/usr/local/bin/bash
cd 

Re: security/libssh ISSUE undefined reference to `__stack_chk_fail_local'

2013-01-09 Thread John Marino

It is pointless to post about every instance of __stack_chk_fail_local.
The problem, as I mentioned before, is really with every gcc compiler in 
ports (with the possible exception of gcc-aux, it may or may not be 
patched yet).  If the compiler is patched, all the 
__stack_chk_fail_local failures disappear.


I still think these posts belong in a PR, not on a mail list.  We are 
all aware a PR takes some time to write and it takes 10 seconds to blast 
out an email.  But the PR system exists for a reason.


John


On 1/9/2013 19:04, awarecons wrote:

FreeBSD 9.0-Release i386 for i386

GCC 4.6.3:

Linking C shared library libssh.so
CMakeFiles/ssh_shared.dir/agent.c.o: In function `agent_talk':
agent.c:(.text+0x3c9): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/channels.c.o: In function `ssh_channel_request_x11':
channels.c:(.text+0x3638): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/channels.c.o: In function `channel_read_buffer':
channels.c:(.text+0x44d3): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/client.c.o: In function `ssh_send_banner':
client.c:(.text+0x590): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/config.c.o: In function `.L46':
config.c:(.text+0x8c7): undefined reference to `__stack_chk_fail_local'
CMakeFiles/ssh_shared.dir/connect.c.o:connect.c:(.text+0xf7): more
undefined references to `__stack_chk_fail_local' follow
collect2: ld returned 1 exit status
*** Error code 1
1 error
*** Error code 2
[100%] Building C object src/CMakeFiles/ssh.dir/bind.c.o
Linking C static library libssh.a
[100%] Built target ssh
1 error
*** Error code 2
1 error
*** Error code 1

Stop in /usr/ports/security/libssh.
*** Error code 1

Stop in /usr/ports/security/libssh.

GCC 4.2: fine.
___
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


Re: Ports requrest: OpenNMS

2013-01-09 Thread Scot Hetzel
On Wed, Jan 9, 2013 at 9:01 AM, Paul Pathiakis pathia...@yahoo.com wrote:
 Hi,

 I've requested this before, however, I still don't see it in the collection.

 OpenNMS is an awesome tool for monitoring.  It takes SNMP and IPMI to an 
 incredible level and the ability to monitor huge numbers of machines makes me 
 a fan.  (Along with all the other features of course).  It even got me to 
 switch off of NAGIOS as the amount of detail and trend graphing it provides 
 is incredible.

 Also, previously, my attempts surrounded a gentleman who seems to already be 
 creating a FreeBSD package for it.

 http://www.geeklan.co.uk/files/opennms/-- Sevan has these files that he 
 creates.  They are very useful although not an official 'port' at this time.


Until Sevan submits his port to FreeBSD, you'll have to use his unofficial port.

It would be best to ask Sevan if he feels his port is complete enough
to be submitted.

-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.
___
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


VirtualBox 4.2.6 and VBoxHeadless VNC

2013-01-09 Thread Shawn Webb
Hey All,

I just upgraded VirtualBox to 4.2.6 on my headless dev server. I use VNC
with VBoxHeadless. After upgrading, I had to change the command-line
options I use for starting the VMs (which is totally fine). It seems that
now VNC is asking for a password, which I never set. Prior to upgrading,
VNC was passwordless. Attempting to connect with a blank password fails to
work as does password. I'm not sure where to proceed from here. Anyone
know how to disable the password or what the default password is?

Thanks,

Shawn Webb
___
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: VirtualBox 4.2.6 and VBoxHeadless VNC

2013-01-09 Thread Larry Rosenman

On 2013-01-09 13:33, Shawn Webb wrote:

Hey All,

I just upgraded VirtualBox to 4.2.6 on my headless dev server. I use 
VNC

with VBoxHeadless. After upgrading, I had to change the command-line
options I use for starting the VMs (which is totally fine). It seems 
that
now VNC is asking for a password, which I never set. Prior to 
upgrading,
VNC was passwordless. Attempting to connect with a blank password 
fails to
work as does password. I'm not sure where to proceed from here. 
Anyone

know how to disable the password or what the default password is?

Thanks,

Shawn Webb
___
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

-e VRDEproperty VNCPassword=whatever


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
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: Why delete KDE3 ports?

2013-01-09 Thread Adam Vande More
On Wed, Jan 9, 2013 at 8:07 AM, Mikhail T. mi+t...@aldan.algebra.comwrote:

 Worse, KDE4 is not only much heavier (which could've been acceptable).


This is simply not true, or at least easily remediable.  A few clicks leads
to nice UI experience with roughly the same amount of overheard as the 3.x
series.  There are a number of quasi-legit investigations into the matter.
 Regardless of those methodologies, at the end of the day KDE4 requires
only slightly more memory than 3 if at all.


 It is also not compatible -- people like myself, who customized their
 desktops with additional menus, who created knotes, etc. will have to redo
 all of their settings. KDE4, as built, is not even going to look under the
 ~/.kde. Though it can be compiled to consider the old directory, the
 format/syntax for many of the config-files has changed -- and there is no
 upgrade path.


I don't use knotes, but have you tried the solution here?
http://forum.kde.org/viewtopic.php?f=22t=84823


 This can all be handled, but meanwhile, until there ARE actual problems,
 leave the ports alone, please.


Actual problems have already been cited for it.  Fighting change can
often lead much more wasted effort than simply adjusting to modern
offerings.  It's easy enough to pull the port out of archive for the small
amount of users who will insist on using a deprecated DE with known
security issues.  I don't think it reflects well on the project to continue
to offer this as an option, and IMO at the very least needs to come with a
blinking red light disclaimer if the port continues to exist.

Jakub Lach:
 In spite of not having 'proper' maintainer both kdelibs3/ and kdebas3/ saw
substantial interest in form of patches

Not recently, unless you mean bulk patches for patches to options
framework, clang, or some other general change such as
http://svnweb.freebsd.org/ports?view=revisionrevision=297915


-- 
Adam Vande More
___
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: VirtualBox 4.2.6 and VBoxHeadless VNC

2013-01-09 Thread Shawn Webb
On Wed, Jan 9, 2013 at 2:52 PM, Larry Rosenman l...@lerctr.org wrote:

 -e VRDEproperty VNCPassword=whatever


 That works. Thanks! Another question. After pausing the VM by calling
`VBoxManage controlvm [VM name here] savestate` I now can't resume
execution by calling `VBoxHeadless -s [VM name here] [more arguments here
for VNC]`. What would be the proper way to resume execution of a VM after
its been paused via savestate?

The error I'm getting is this:

VBoxManage: error: Cannot resume the machine as it is not paused (machine
state: Saved)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002),
component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: Resume() at line 120 of file
VBoxManageControlVM.cpp

Thanks,

Shawn
___
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: VirtualBox 4.2.6 and VBoxHeadless VNC

2013-01-09 Thread Larry Rosenman

On 2013-01-09 14:05, Shawn Webb wrote:
On Wed, Jan 9, 2013 at 2:52 PM, Larry Rosenman l...@lerctr.org 
wrote:



-e VRDEproperty VNCPassword=whatever


 That works. Thanks! Another question. After pausing the VM by
calling `VBoxManage controlvm [VM name here] savestate` I now can't
resume execution by calling `VBoxHeadless -s [VM name here] [more
arguments here for VNC]`. What would be the proper way to resume
execution of a VM after its been paused via savestate?

The error I'm getting is this:

VBoxManage: error: Cannot resume the machine as it is not paused
(machine state: Saved)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE
(0x80bb0002), component Console, interface IConsole, callee
nsISupports
VBoxManage: error: Context: Resume() at line 120 of file
VBoxManageControlVM.cpp

Thanks,

Shawn

I haven't solved that one yet :(

I also am having issues with a 2 vCPU FBSD10 VM not keeping time worth 
a flip



--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
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: Why delete KDE3 ports?

2013-01-09 Thread Mikhail T.

On 09.01.2013 14:53, Adam Vande More wrote:
I don't use knotes, but have you tried the solution here? 
http://forum.kde.org/viewtopic.php?f=22t=84823
Obviously, knotes was just an example. All other customizations (such as menus, 
backgroundsscreen-savers, email accounts -- everything under ~/.kde) have to be 
redone too and, frankly, I do not trust today's KDE project to not do the same 
nonsense again, when they decide to abandon KDE4 for 5 (can't be long now that 
the release is 4.8).


The very existence of the project Trinity is a sign, that my opinion is shared 
by a few more people.


This can all be handled, but meanwhile, until there ARE actual problems,
leave the ports alone, please.


Actual problems have already been cited for it.
No, they have not. The minor security threat cited is easily managed by simply 
not using kdm on a system, where less than trusted users have access. kdm is a 
minor part of KDE anyway (I, for one, use xdm).

Fighting change can often lead much more wasted

Yes, it often can. But not in this case. Yours,

   -mi

___
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: Why delete KDE3 ports?

2013-01-09 Thread Jakub Lach
I was thinking of December patches. Till now, each time kde3 broke,
in few weeks someone would sent patch.

 A few clicks leads to nice UI experience with roughly the same 
 amount of overheard as the 3.x

I simply do not believe that. Stripped (!) KDE3 is workable on PIII 
system, to think the same of KDE4  with much heavier Qt and
default configuration would be really stretching  plausibility... 

In the end, I do not care enough (or even like KDE) to support 
KDE3, but I understand some of the concerns, as I was supporting
one KDE3 system, where I wouldn't even try to change to KDE4.




--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Why-delete-KDE3-ports-tp5775510p5776226.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
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: devel/boost-libs looks hardwired for gcc/g++

2013-01-09 Thread Shane Ambler

On 09/01/2013 18:26, Baptiste Daroussin wrote:


FYI I'm working on an update to 1.52.0 version, which will not be hard wired
anymore

http://people.freebsd.org/~bapt/boost-1.52.0.diff



I just had a quick look over the patch - with 1.48 boost-python-libs
generates libboost_python and libboost_python3 when built against
python 3.x - does 1.52 still do this or has it been merged?

___
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: devel/boost-libs looks hardwired for gcc/g++

2013-01-09 Thread Baptiste Daroussin
On Thu, Jan 10, 2013 at 12:09:10PM +1030, Shane Ambler wrote:
 On 09/01/2013 18:26, Baptiste Daroussin wrote:
 
  FYI I'm working on an update to 1.52.0 version, which will not be hard wired
  anymore
 
  http://people.freebsd.org/~bapt/boost-1.52.0.diff
 
 
 I just had a quick look over the patch - with 1.48 boost-python-libs
 generates libboost_python and libboost_python3 when built against
 python 3.x - does 1.52 still do this or has it been merged?
 

I haven't check yet exactly boost-python-libs, but I will pay attention to that

regards,
Bapt


pgpUh9fV_iQch.pgp
Description: PGP signature