Re: x11/nvidia-{driver, settings, xconfig}: why not the latest available version (290.10)?

[Mark Felder]

On Sat, 24 Dec 2011 02:44:04 -0600, Denise H. G.  wrote:


290.10 has some issues on text redrawing as far I experience. I have
also been running 290.10 for quite a while. Some apps, especially emacs
and gnome-terminal will fail redrawing text areas while, e.g. scrolling.
And x11 cursor cannot sometimes be displayed correctly.


Are we sure this isn't a bug somewhere else? I've been having redrawing  
problems on 285.05.09 and moving to 290.10 is what fixed it for me

___
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: FreeBSD Port: php5-5.3.8

[Mark Felder]

On Mon, 09 Jan 2012 15:52:19 -0600,  wrote:


Hello

I'm trying to migrate from REDHAT EL world to FREEBSD. We have a policy  
of installing binary packages and stay away from compiling source code.
I have FreeBSD-9.0RC3 and I did pkg_add -r apache22 pkg_add -r php5, so  
now I have both packages installed but I can't get them to work  
together...


am I doing something wrong? or was it not meant to work together? or  
there is something else needs to be done that I'm missing? if possible  
I'd like to stay away from (/usr/ports), as we want to use packages only




The Apache module is missing and I don't know if there's a package for  
that or if you really do have to use ports. I've never tried using just  
packages for Apache+PHP.




Regards,



Mark
___
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/zoneminder: rc script runs mysql commands?

[Mark Felder]

Hi all,

The zoneminder port has this in its rc script which really should go away:

zm_prestart() {
local _count=0

while : ; do
echo "USE zm; SELECT Username from Users where Id=1;" | \
/usr/local/bin/mysqltest -u root zm > /dev/null  
2>&1 && return

_count=$(( $_count + 1 ))
if [ $_count -gt 10 ]; then
err 1 "${name}: mysqltest command failed"
fi

sleep 1
done
}


If you have your mysql install on a different server (which you should if  
you have tons of cameras and events) the startup fails to work. I can't  
see a reason why this should be kept, but perhaps someone else has an  
idea? This isn't a common practice in any other program that requires a  
database




Thanks,


Mark
___
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: multimedia/zoneminder: rc script runs mysql commands?

[Mark Felder]

On Wed, 11 Jan 2012 12:16:45 -0600, Boris Samorodov  wrote:


The problem is: while start-up zoneminder is launched after mysql
was started but is not responding yet. Then zoneminder can't register
it's cameras, etc. This hack was introduced to catch the moment when
mysql really is operational and then start zoneminder.
If someone has a solution -- you are welcome.


Instead of hacking up zoneminder's rc script with further patches like  
pulling out the real mysql server, database, username and password perhaps  
we should see if we can get the mysql maintainer(s) to fix the mysql rc  
script so it doesn't exit until the service is fully fired up and  
functional? I imagine what you've described is a situation where MySQL has  
a lot of databases/tables/etc and churns for a bit before accepting  
connections, but if it finally hits a badly crashed table or something and  
doesn't complete starting up but the rc script already exited... that  
wouldn't be good.


Advantage: better behavior
Disadvantage: slows up the start process of all dependent services.


This is all speculation at this point, but it seems silly that the mysql  
rc script would finish before the database can really accept connections.

___
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: multimedia/zoneminder: rc script runs mysql commands?

[Mark Felder]

On Wed, 11 Jan 2012 12:44:26 -0600, Doug Barton  wrote:



That is attractive all on its own of course, however it still doesn't
solve the OP's problem, since his mysqld is not local.



Yeah, that was me -- the OP -- and I'm sitting here brainstorming but  
haven't been able to come up with many alternatives yet unless we want to  
add what I feel is unnecessary complexity to the zoneminder rc script.  
There has to be a K.I.S.S. solution hiding somewhere

___
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: multimedia/zoneminder: rc script runs mysql commands?

[Mark Felder]

On Fri, 13 Jan 2012 03:20:13 -0600, Alex Dupre  wrote:


Boris Samorodov ha scritto:

Actually this should not happen. mysql rc script has a poststart
directive to wait until the daemon is up and running.


Last time I used the port (zoneminder) a year ago. It was the case.
Has something changed in a year?


MySQL rc script was patched 3 years ago.



Sounds like it's safe to remove this from zoneminder then.
___
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: so, FreeBSD on VMware is dead, right?

[Mark Felder]

FreeBSD on ESX here. Unfortunately our boss wants us to move to Citrix Xen  
even though they don't* support VMotion type features on FreeBSD because  
we've spent upwards of $50,000 USD in support/licensing on VMWare over the  
last year and it's been over a year without a fix to our crash bug  
directly related to bad behavior in their I/O virtualization layer. (ESX  
4.1)


So besides the few VMs that crash ~weekly, it runs great, and we have a  
ton of FreeBSD VMs which will never be changed to another OS.


FreeBSD needs more love from VMWare, but I don't think it's dead..  
However, it's rather disappointing to hear their techs say. "FreeBDS?[sic]  
What is that, some kind of Linux?"



* Citrix NetScaler product is based on a fork of FreeBSD 6.x and Citrix  
offers a VM appliance that runs on Xen and does support their VMotion  
equivalent. Why they won't port or give us the Xen Tools that exist on  
that appliance is a mystery. I've considered taking their trial appliance,  
dissecting it, and trying to make it run on stock FreeBSD with compat6x  
and what other hacks are necessary, but I'm sure they have kernel modules  
that definitely will not work on 8.x or 9.x without being recompiled

___
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: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util

[Mark Felder]

On Thu, 26 Jan 2012 11:20:27 -0600, Kevin Oberman   
wrote:



Have you run 'pkg-libchk -o | grep xcb-' from
sysutils/bsdadminscripts? it should provide a list of ports that need
to be re-built after the xcb-utils upgrade to 1.8.



What's strange is that this didn't work for me the first five times I  
tried it. I had to use the portmaster --check-depends to find a missing  
package that wasn't getting picked up by the broken things listed in  
pkg_libchk

___
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: net/freerdp 1.0.0

[Mark Felder]

On Tue, 07 Feb 2012 04:49:39 -0600, Andriy Gapon  wrote:



I would like to ask you to review and test the port in this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=164843

I also would to discuss with the port's users the best approach to  
updating it.


Thank you.



Doesn't compile.


[ 21%] Building C object  
libfreerdp-kbd/CMakeFiles/freerdp-kbd.dir/layouts_xkb.c.o
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:25:22:  
error: X11/Xlib.h: No such file or directory
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:26:24:  
error: X11/XKBlib.h: No such file or directory
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:27:36:  
error: X11/extensions/XKBfile.h: No such file or directory
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:28:37:  
error: X11/extensions/XKBrules.h: No such file or directory
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:  
In function 'init_xkb':
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:45:  
warning: implicit declaration of function 'XkbQueryExtension'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:  
In function 'detect_keyboard_layout_from_xkb':
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74:  
error: 'XkbRF_VarDefsRec' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74:  
error: (Each undeclared identifier is reported only once
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74:  
error: for each function it appears in.)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:74:  
error: expected ';' before 'rules_names'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:75:  
error: 'XKeyboardState' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:75:  
error: expected ';' before 'coreKbdState'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:76:  
error: 'XkbStateRec' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:76:  
error: expected ';' before 'state'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:80:  
warning: implicit declaration of function 'XkbRF_GetNamesProp'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:80:  
error: 'rules_names' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:85:  
warning: implicit declaration of function 'XGetKeyboardControl'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:85:  
error: 'coreKbdState' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87:  
warning: implicit declaration of function 'XkbGetState'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87:  
error: 'XkbUseCoreKbd' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87:  
error: 'state' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:87:  
error: 'Success' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:  
In function 'init_keycodes_from_xkb':
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:112:  
error: 'XkbDescPtr' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:112:  
error: expected ';' before 'xkb'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:114:  
error: 'xkb' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:114:  
warning: implicit declaration of function 'XkbGetMap'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:114:  
error: 'XkbUseCoreKbd' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:116:  
warning: implicit declaration of function 'XkbGetNames'
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:116:  
error: 'XkbKeyNamesMask' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:116:  
error: 'Success' undeclared (first use in this function)
/usr/ports/net/freerdp/work/FreeRDP-FreeRDP-cd43ba1/libfreerdp-kbd/layouts_xkb.c:156:  
warning: implicit declarati

Re: net/freerdp 1.0.0

[Mark Felder]

On Thu, 09 Feb 2012 10:36:04 -0600, Andriy Gapon  wrote:


Doesn't look like the latest version of the port's shar.




Good call -- I didn't see there were further revisions as my browser must  
not have loaded the whole page.

___
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 -> portmaster Rosetta Stone?

[Mark Felder]

On Mon, 27 Feb 2012 04:18:12 -0600, Olivier Smedts   
wrote:



-w : save old shared libraries before deinstall



Won't this leave a lot of cruft behind over time? I don't see the point in  
keeping ancient shared libraries around for years and not knowing with  
confidence what versions your ports are linked to. I'd rather just follow  
UPDATING and make sure everything is properly linked against the newest.


On that note, does portmaster at least provide a way to keep track of  
libraries it kept due to the usage of -w ?

___
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"

databases/mariadb -- should we have several versions?

[Mark Felder]

How does the community feel about having multiple mariadb ports like our  
current mysql ports? It would be nice to have mariadb53-{client-server}  
and mariadb55-{client|server} as well, in my opinion.



Thoughts?
___
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: databases/mariadb -- should we have several versions?

[Mark Felder]

On Wed, 07 Mar 2012 16:48:02 -0600, Philip M. Gollucci  
 wrote:



On 03/07/12 22:03, Mark Felder wrote:

How does the community feel about having multiple mariadb ports like our
current mysql ports? It would be nice to have mariadb53-{client-server}
and mariadb55-{client|server} as well, in my opinion.


http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164072

Something similiar with another letter could be used like 'm' unless of
course mysql,percona,& maria will never share version numbers.



MariaDB doesn't exactly have corresponding version numbers.

MariaDB -> MySQL
5.1 == 5.1
5.2 == 5.1 + MariaDB extras
5.3 == 5.1 + MariaDB extras + MySQL 6.0GA (unreleased) backports
5.5 == 5.5 + ? (I assume built off previous work, but 5.5 isn't GA for  
MariaDB yet)



http://downloads.askmonty.org/mariadb/  (click the "What is MariaDB 5.x"  
links)

___
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"

p0f v3

[Mark Felder]

Is anyone working on a port of p0f v3? It is much more accurate at  
detecting newer OSes. I have seen emails from 2008R2 servers get higher  
than normal SpamAssassin scores because it thought they were Windows XP,  
which is causing spam filter accuracy issues.


I think this would be a great benefit to everyone. The current p0f port  
does not have a maintainer.



http://lcamtuf.coredump.cx/p0f3/



Cheers,



Mark
___
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: p0f v3

[Mark Felder]

On Thu, 15 Mar 2012 11:28:31 -0500, Kurt Jaeger  wrote:


As I've read your mail, I had a look at p0f 3. It looks doable.


I've been busy and didn't have a chance to reply earlier -- I look forward  
to your work. I am preparing a test environment soon so I can push some  
emails through one of our filters with an updated p0f port. If I don't get  
to the port before you I would be able to at least test it.

___
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: multimedia/zoneminder: rc script runs mysql commands?

[Mark Felder]

On Mon, 02 Apr 2012 16:37:46 -0500, wwwdrich  wrote:

I have a K.I.S.S. solution I have been running for a while. Just source  
the zm.conf file into the init script and then use the variables there 
for the mysql test.


I like this idea a lot. Is it breaking any guidelines? I assume as long as  
we aren't hardcoding the path to the zm.conf we should be OK, yes?

___
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"

xfce 4.8 upgrade errors

[Mark Felder]

How do I create a app menu, I'm getting an error when trying to load the  
menu "menus/applications.menu"

not found.


Recompile sysutils/garcon to resolve this error.

I hope this helps someone else...


Regards,


Mark
___
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: xfce 4.8 upgrade errors

[Mark Felder]

On Thu, 10 Mar 2011 06:53:56 -0600, Pavel Timofeev   
wrote:




Also opera crashes my system when I use it in xfce4. It permanently  
hangs,
no messages in logs and no response from system. If I launch opera in  
clean

Xorg (twm?) it works very good.


I also run Opera but I was getting hangs on any browser if there was flash  
playing. I haven't had the hang without flash so far. I'll report back if  
that changes.




Regards,


Mark
___
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: patch for force fetch

[Mark Felder]

On Mon, 16 May 2011 04:00:17 -0500, Peter Pentchev   
wrote:



4. Upstream makes a change without bumping the version.


Please make sure when this happens you give upstream a piece of your mind.  
This is unacceptable anywhere. If the end product changes it is wholly  
irresponsible and downright rude for them to not change the version  
number. I've been successful in changing policies of upstream before by  
making sure they know that it is NOT cool.


Regards,



Mark
___
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: emulators/wine

[Mark Felder]

On Tue, 21 Jun 2011 16:03:48 -0500, Bruce Meier   
wrote:



Does anyone know if there will ever be a wine64 port?


The guy working on it is posting packages here:

http://www.mediafire.com/wine_fbsd64

Feel free to install them -- they work very well.



Regards,


Mark
___
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"

net/haproxy doesn't stop all processes

[Mark Felder]

Hi all,

I recently installed haproxy and I am in the process of configuring  
redundant load balancers and I discovered a bug in the haproxy shutdown  
sequence. For some reason the first PID in /var/run/haproxy is the only  
one that gets a kill signal when you shutdown. In order to reproduce this  
behavior you will have to increase the number of haproxy processes with  
the following setting:



nbproc  4 # Number of processes


I can get it to kill cleanly from the shell but when I modify the  
pre_stop() it still doesn't work. Any thoughts?



Current rc script for those who don't have it installed is below.

Regards,


Mark


#!/bin/sh

# PROVIDE: haproxy
# REQUIRE: DAEMON
# KEYWORD: shutdown

###
#
# Add the following lines to /etc/rc.conf to enable haproxy:
#
# haproxy_enable (bool):default: "NO"
#   Set to "YES" to enable haproxy
# haproxy_pidfile (str):default: /var/run/${name}.pid
#   Set to the full path of the pid file
# haproxy_config (str): default: /usr/local/etc/${name}.conf
#   Set to the full path of the config file
# haproxy_flags (str):  default: Autogenerated using pidfile and  
config options

#   Set to override with your own options
#
###
#
# rc.d Script Runtime Options:
#
# start - starts application normally
# stop  - (softstop) stops all proxies and exits once all sessions  
are closed

# forcestop - (immediate) stops all proxies and kills active sessions
# reload- hot-reconfig using "-sf" option (active sessions kept)
# forcereload   - hot-reconfig using "-st" option (active sessions killed)
# restart   - equiv to "stop" then "start"
# checkconfig   - checks configuration file defined in haproxy_config
#
###

. /etc/rc.subr

name="haproxy"
rcvar=`set_rcvar`
command="/usr/local/sbin/haproxy"

# Load Configs/Set Defaults
load_rc_config $name
: ${haproxy_enable:="NO"}
: ${haproxy_config:="/usr/local/etc/${name}.conf"}
: ${haproxy_pidfile:="/var/run/${name}.pid"}
: ${haproxy_flags="-q -f ${haproxy_config} -p ${haproxy_pidfile}"}

# Update the globals
pidfile=${haproxy_pidfile}
required_files=${haproxy_config}

# Commands: start, stop, restart, reload, checkconfig
extra_commands="reload checkconfig"

checkconfig_cmd="haproxy_checkconfig"
reload_cmd="haproxy_reload"

haproxy_reload()
{
# Check configuration file quietly first
${command} -q -c -f ${haproxy_config}
if [ $? -ne 0 ]; then
echo "Error found in ${haproxy_config} - not reloading  
current process!"

return
fi
rc_pid=$(check_pidfile ${haproxy_pidfile} ${command})
if [ $rc_pid ]; then
if [ $rc_force ]; then
${command} ${haproxy_flags} -st ${rc_pid}
else
${command} ${haproxy_flags} -sf ${rc_pid}
fi
else
echo "No process found.  Maybe $command isn't running?"
fi
}

haproxy_checkconfig()
{
${command} -c -f ${haproxy_config}
}

haproxy_prestart()
{
${command} -q -c -f ${haproxy_config}
rc_flags=${haproxy_flags}
}

haproxy_prestop()
{
# SIGUSR1 = softstop, SIGTERM = faststop
if [ $rc_force ]; then
sig_stop="SIGTERM"
else
sig_stop="SIGUSR1"
fi
}


run_rc_command "$1"
___
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: PHP 5.4.0 : lang/php54

[Mark Felder]

After a reasonable amount of time has passed so more applications properly  
support it

___
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: Any news on Suhosin?

[Mark Felder]

On Tue, 05 Jun 2012 13:50:56 -0500, Paul Schmehl  
 wrote:


Thanks, Kurt.  Looks like it's never going to be included in the php  
distro again, so now I need to find out what the consequences are of not  
including it.  Googling..


It was never included in the PHP distribution.
___
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: Any news on Suhosin?

[Mark Felder]

I inferred that you meant "distribution" == "part of the core PHP project".

Yes, it has been distributed alongside PHP on many different operating  
systems.

___
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: [CFT] Xorg 7.7 ready for testing!

[Mark Felder]

On Thu, 07 Jun 2012 08:09:06 -0500, Vitaly Magerya   
wrote:



Will it be possible to provide, say pkgng repo with packages compiled
with new xorg and new mesa? That would simplify testing (and using) by a
very large factor. We'd just change PACKAGESITE and run pkg upgrade.


The ability to add multiple PACKAGESITEs somehow and the latter ones  
override the former if they provide conflicting packages would be an  
interesting way to handle testing things like 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: Horde4 eats all memory

[Mark Felder]

Are there any stable Linux distros with php 5.4 yet? I'm not aware of any  
right now.

___
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: painful process.. php53/etc

[Mark Felder]

On Fri, 22 Jun 2012 11:22:43 -0500, Bryan Drewery  wrote:



Does that actually work though?
Somehow it seems too simple given this discussion continues to come up
with various /var/db/pkg hacks.


This will NOT work. I've tried it before. Every time you do a portmaster  
-a it will try to upgrade all the modules to php 5.4 versions which will  
fail miserably because you have php53 installed.

___
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: Port system "problems"

[Mark Felder]

On Tue, 26 Jun 2012 04:31:40 -0500, Andrea Venturoli   
wrote:




The "effort" will be 3x processing time for portupgrade (or whatever) to  
update the package database 3 times as much as before.


pkgng uses sqlite. Please provide proof that it is as slow or slower than  
our current package database is.

___
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: Porting applications with "nice" installers

[Mark Felder]

On Tue, 26 Jun 2012 06:56:14 -0500, Fernando Apesteguía  
 wrote:




Any ports dealing with these situations that I can use as a reference?


The Opera port uses its own installer. Unfortunately if we want to split  
PORTDOCS off we'll have to install all the files manually... Keep things  
like that in mind.

___
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: Port system "problems"

[Mark Felder]

On Tue, 26 Jun 2012 13:42:54 -0500, Marcus von Appen   
wrote:


That said, I might assume that the sqlite solution is faster, but noone
can see that yet.



The new system will be much, much better overall and people just need to  
stop making conclusions without knowing all the facts. It's going to be a  
heavily revamped system so people should stop comparing it to our current  
architecture. It's only similar on the surface.

___
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: Port system "problems"

[Mark Felder]

On Tue, 26 Jun 2012 13:50:48 -0500, Marcus von Appen   
wrote:



I still do not see any reason or argument on why we would need
sub-packages.


I want up to date packages for all my servers. My servers all have  
different requirements -- I want Apache with LDAP here, and definitely  
Apache without LDAP there. Designing a package-building and deployment  
system for a non-homogenous server farm is an exercise in futility. Having  
proper sub-packages fixes this issue in a cleanly supportable fashion.

___
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: Port system "problems"

[Mark Felder]

On Tue, 26 Jun 2012 14:43:11 -0500, Marcus von Appen   
wrote:



That sound good to me and something I'd vote for, since it does not
split ports on a technical, but functional level into packages.


Yes this is exactly what we're aiming for. Right now if someone installs  
FreeBSD and they pkg_add apache22 and php5 they can't even serve PHP  
because php5 doesn't install mod_php. Things like this are as frustrating  
for new users as it is for people trying to maintain many, many servers.

___
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: [HEADSUP & CFT] pkg 1.0rc1 and schedule

[Mark Felder]

On Fri, 13 Jul 2012 09:52:24 -0500, Bryan Drewery  wrote:



This explains how you can setup your own repository and build your own
packages with poudriere+pkgng:



Yes, and it's fantastic. I'm currently using it to build updates for my  
low powered laptop at home and the package database fetch and "what needs  
to be upgraded" process is faster than any other package management system  
I've ever seen. Pkgng is a fantastic project.

___
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: port DNS/UNBOUND

[Mark Felder]

Hi Alexy,

Can you submit a PR with an appropriate patch?


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: CFT: vlc 2.0.3 - want to know where it works and where only partly

[Mark Felder]

WORKING:

- Up to date ports
- FreeBSD cr48.lan 9.0-STABLE FreeBSD 9.0-STABLE #3 r237413M: Thu Jun 21  
21:44:02 CDT 2012 r...@skeletor.feld.me:/usr/obj/tank/svn/sys/GENERIC   
amd64

- Intel i915kms.ko


Still have to test a similar system but using Nvidia
___
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: pkgng questions

[Mark Felder]

I think you're very confused about what pkgng is for. At this time, ports  
are STILL the recommended way to install things and keep them up to date.  
Pkgng is the first step required for us to get a better package management  
system so we can shift the community towards primarily using packages.


On Thu, 30 Aug 2012 05:05:57 -0500, Matt Burke   
wrote:



1. How do I get pkg to use packages built against 9.1-RC1? VirtualBox is
playing up (no ethernet, unkillable crashes, etc) and I suspect it's the
kernel module...


I'm not sure what you mean here. Do you have a 9.1-RC1 server and you're  
using a public pkgng repository? Which is probably built against 9.0?



2. Is there a list of ports like nvidia-driver, nspluginwrapper,
linux-f10-flashplugin, sampleicc (dependency of libreoffice!) which  
aren't

in pkgng?


Everything can be built into the pkgng format except a few ports that need  
workarounds. There's a list on the wiki.


http://wiki.freebsd.org/pkgng

Go to the bottom "Known Failures" section.


2a. How do I install libreoffice when a dependency isn't in pkgng?


You run your own poudriere box and setup your own private pkgng repository  
at this time and build your packages against whatever versions of  
Perl/Python/PHP/MySQL/etc that you prefer with whichever extra make.conf  
settings and port options you prefer. My own pkgng repository has  
libreoffice with no issues.



3. How do I force pkg to install/upgrade a single package, regardless of
dependencies being out of date?


You should never try to do this anyway; you'll end up with packages built  
against the wrong versions of libraries.



4. How do I get poudiere to build against a local src/obj tree, or a zfs
snapshot of a pre-built jail, instead of 9.0-RELEASE?


The poudriere man page has all the instructions needed to create jails of  
any release version to be used for building packages.


5. How do I get poudiere to build against the packages a pkgng client  
will
use instead of building everything for itself? It might help to reduce  
the

discrepancy between the 30 secs it takes to rebuild sysutils/conky from
ports on my desktop, and the >1hour it takes poudiere on a hefty server  
to

download+build X and all its dependencies


You don't do it this way. You build everything on your poudriere server  
and push all of your packages to the client. You do this every single  
time. If you decide you want a new package on your client, you build it on  
your poudriere server and have your client request it. If you're using  
poudriere/pkgng, your clients should NEVER be compiling ports or  
installing packages outside of what your poudriere server is providing.  
Poudriere is giving you a "cleanroom" environment where it can guarantee  
that all the packages and their required packages/libraries are sane.




6. Is pkgng really replacing base when poudiere requires ZFS? How will
ports work if pkg_* are gone? Seriously, shouldn't ports at least be able
to work with pkgng, and the default FreeBSD install be to a ZFS root  
before

people are stuffed with the "wrong" choices (UFS) they made?


Pkgng doesn't require ZFS -- poudriere does. Your clients should never  
have poudriere.



7. How do I configure pkg to use packages from a certain historical
release? I need my servers to be identical software-wise regardless of  
when

I install them. In other words, I DON'T want the latest versions.


Make sure your poudriere server is using the ports tree snapshot you  
desire.



8. Is there a pkgng equivalent of 'ls -lt /var/db/pkg' without firing up
sqlite?


Are you looking for the date column (not sure why that's useful as it can  
change due to many things)? Doesn't "pkg info -a" suffice?


9. Why didn't pkg upgrade tell me it replaced my custom-built packages?  
I'd
have liked for it to not break stuff when /var/db/ports/*/options  
differed

from the options I can see pkgng keeps in its metadata...


Your poudriere server can use you preferred options when it builds  
packages. Check the man page.



Long story short: poudriere is a tool for you to build your OWN private  
package repositories (which is really handy!). Pkgng is just the first  
step towards a large goal of greatly improving the enduser experience with  
FreeBSD. I don't believe pkgng is default on any release yet, so you  
shouldn't be using public pkgng repositories for anything but testing. You  
should either be running your own poudriere server or you should just be  
using the new pkgng format with ports.


I'm sure someone will chime in with more details and possibly corrections  
if I've missed something.

___
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: pkgng questions

[Mark Felder]

On Thu, 30 Aug 2012 08:43:54 -0500, Jamie Paul Griffin   
wrote:


Can i ask, why is it that shifting the community to using packages is  
deemed to be a better approach? I like being able to select  
configuration options to build software. I have never installed a  
pre-compiled package since using FreeBSD version 6.x.


The long-term goal is subpackages so this need is alleviated. The only  
reason to compile yourself then is to play with the CFLAGS. :-)


Example: right now if you want to build a webserver running Apache and PHP  
quickly with FreeBSD you have no choice but to use ports. The PHP package  
doesn't provide the Apache PHP module. But if we had packages for the  
independent options: php5-apache, php5-php-fpm, php5-cli, php5-cgi You  
see where this is going. It's moving toward the modularization that many  
Linux distros use. Some people are going to hate this, but it makes  
support for the ports team MUCH more consistent because everyone runs the  
same binaries.

___
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: pkgng questions

[Mark Felder]

On Thu, 30 Aug 2012 09:44:42 -0500, Matt Burke   
wrote:



On 08/30/12 13:01, Mark Felder wrote:
I think you're very confused about what pkgng is for. At this time,  
ports
are STILL the recommended way to install things and keep them up to  
date.


Really? I think the last time I compiled X or a web browser (until using
poudriere) was about 10 years ago.



Yes, but an example I gave in another thread reply is PHP. You can't  
pkg_install PHP right now and get Apache support. You HAVE to compile. The  
new pkg format is a step towards sub-packages so we can have a better  
public package repository that can fill 99% of everyone's needs.




I had a couple of questions I wanted to answer -

1) How easy does it make keeping my desktop (currently releng/9.1 built
with dtrace) up-to-date


It should be no different -- perhaps easier even.


2) How much easier will it be to maintain production and testing servers?




It will be no different. In fact, if you have a lot of servers but you  
have consistent, customized options across them all it will be EASIER to  
deploy and update packages with pkgng and poudriere.



The answer has made me start downloading an OpenIndiana iso.



I don't see what OpenIndiana gains you...?




I don't see any of the examples I gave listed, apart from nvidia-driver




Because the examples you gave have no issues with pkgng. If they're not in  
the public repository that's not a pkgng problem, it's a repository  
problem. You should be using pkg_* until the ports@ team has stated that  
the public pkgng repository is the one everyone should be using. pkgng 1.0  
has just been announced, but that just means the tool has reached  
maturity, not the package management of FreeBSD has instantly changed to  
pkgng.




You're suggesting that I should upgrade an entire machine which may have
proven itself over a period of years to be perfectly stable, just  
because I

need a small utility which really doesn't care about the man page typo
which caused gettext-0.1.2_3 to change to gettext-0.1.2_4?



I'm not sure how you've come to this conclusion? If you have a poudriere  
server building packages and you only want to install one new utility,  
just tell poudriere to build only that utility and not build your entire  
list of packages. Yes, if that utility depends on gettext you'll find  
poudriere upgrading gettext and everything that depends on it. That's what  
poudriere does -- make sure that everything is built against whatever is  
current in the ports tree provided. But again, we're getting into the  
realm of mixing ports and packages which you should always take great  
caution when doing. You'll still be able to do that with pkgng.


4. How do I get poudiere to build against a local src/obj tree, or a  
zfs

snapshot of a pre-built jail, instead of 9.0-RELEASE?


The poudriere man page has all the instructions needed to create jails  
of

any release version to be used for building packages.


No, the man page doesn't mention anything about specifying where to pull
the distribution from, only what method of access to use.


poudriere jail -c -v 8.3-RELEASE -a amd64 -j 8stable-amd64

This builds a jail from 8.3-RELEASE. If you want to update it to 8-STABLE  
build the 8-STABLE world and "make installworld  
DESTDIR=/path/to/poudriere/jail/named/8stable-amd64"


Does that help?



I am confused. If pkg_* are removed, how is a person with a single  
desktop
machine (worst case, a netbook) expected to operate if they need a  
specific
port build? Are they to spend a week compiling 1000+ ports themselves in  
a

poudriere VM?

Or is the flexibility of FreeBSD ports just not deemed to be useful to  
the

end user (or person unable to provide a dedicated any more?



Do not change what you are currently doing. Keep using pkg_* until the  
pkgng repositories are deemed to be the official package repositories of  
FreeBSD. If you really know what you're doing, you can still mix ports and  
packages with pkgng. Later when we have subpackages you probably will  
never need to do a "specific port build" because you want different  
options.




8. Is there a pkgng equivalent of 'ls -lt /var/db/pkg' without firing  
up

sqlite?


Are you looking for the date column (not sure why that's useful as it  
can

change due to many things)? Doesn't "pkg info -a" suffice?


'ls -lt /var/db/pkg' will show me what packages were installed sorted by
day. It is very useful on servers which aren't routinely upgraded to the
latest and greatest untested versions



There has been discussion to backport creation /var/db/pkg entries and  
make it readonly. I understand your need because I use that too sometimes.




9. Why didn't pkg upgrade tell me it replaced my custom-built  
packages? I'd
have liked for it to not break stuff when /v

Re: Need a reality check: "portmaster --list-origins" misses entries?

[Mark Felder]

It's listing the *origins*. If you install everything listed from the  
output of portmaster --list-origins, it would install those ports and all  
their dependencies which should make up the entire contents of your  
current /var/db/pkg (all 796 you have installed, unless some dependencies  
are no longer valid).


It will work. Try it :-)
___
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: 'pkg check -d' showing missing dependencies after upgrading lang/perl

[Mark Felder]

On Thu, 25 Oct 2012 06:04:05 +1100
andrew clarke  wrote:

> I noticed at some point after installing and switching to pkgng, then
> upgrading Perl from 5.12 to 5.14 with 'portmaster -o lang/perl5.14
> lang/perl5.12', the 'pkg check -d' command would still list some ports
> with perl5.12 as a missing dependency:
> 

I think this is a bug with portmaster. Portmaster should have run this
command on your behalf:

# pkg set -o lang/perl5.14:lang/perl5.12

This runs a query in the pkg sqlite database and update dependencies.
This clearly didn't happen for you yet, so thats where your errors come
from. There's a way to do this manually but I can't find it in my
notes. Hopefully someone can quickly reply to you with the solution or
perhaps I'll find it in a few minutes...
___
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"

CFT: lang/mono 5.10.2

[Mark Felder]

Hi all,

It's time to get us on a modern stable mono version. I've had nothing but 
issues with mono 5.2 and it seems I'm not alone. I have a port update ready for 
testing here:

https://reviews.freebsd.org/D15780

Initially I intended to bring us to the very latest release, mono 5.12, but 
that seems to have compatibility issues. I run some ports that just don't work 
with it, so per suggestion I am tracking the  "really stable" release which is 
what Mono ships with MS Visual Studio on Linux.

Please let me know if you have any feedback. I'm hoping to get this committed 
before the 2018Q3 tree gets cut.

-- 
  Mark Felder
  ports-secteam & portmgr member
  f...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Rancid3 update to 3.9?

[Mark Felder]

Kurt, if you are an active user of Rancid you're welcome to take the port from 
me. I use it but don't pay attention to it much, and @ my old job we moved to 
Oxidized anyway for some extra features.

I just committed your patch but can't get into my bugzilla account right now to 
close the issue.


Cheers,

Mark

On Wed, Feb 20, 2019, at 01:57, Kubilay Kocak wrote:
> On 20/02/2019 2:19 pm, Kubilay Kocak wrote:
> > On 20/02/2019 10:23 am, Dan Mahoney (Gushi) wrote:
> >> All,
> >>
> >> Rancid3 has been updated to 3.9, upstream.  I've contacted the 
> >> maintainer, but it might be stuck.  Would a patch be helpful?
> >>
> >> -Dan Mahoney
> >>
> > 
> > Hi Dan,
> > 
> > Patches are always welcome (and desirable) :)
> > 
> > Best is a Bugzilla issue created "net-mgmt/rancid3: Update to 3.9" with 
> > a patch (unified diff against the port dir) attached. This will also 
> > automatically assign and notify the maintainer (CC'd).
> > 
> > Bonus points for QA testing it with portlint and poudriere, 
> > details/instructions here:
> > 
> > https://www.freebsd.org/doc/en/books/porters-handbook/testing.html
> > 
> > #freebsd-ports on freenode IRC if you have any questions or need help!
> > 
> > ./koobs
> 
> net-mgmt/rancid3: Update 3.7 -> 3.9
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235875
> 
> Thanks Kurt!
>

-- 
  Mark Felder
  ports-secteam & portmgr member
  f...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: unifi5-5.10.25

[Mark Felder]

On Thu, Sep 12, 2019, at 04:18, Jon Otterholm wrote:
>  
> Hi.
> 
> 
> Any plans for updating this port to the latest release?
> 
> 

Hello,

I've been traveling to conferences last few weeks which has kept me distracted, 
but I'm about to test the latest update. It will be in ports shortly.


Thanks for the reminder!


Mark


-- 
  Mark Felder
  ports-secteam & portmgr alumni
  f...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Dropbox on FreeBSD

[Mark Felder]

On Thu, 20 Dec 2012 13:45:13 +
Chris Rees  wrote:

> It needs porting to kevent.

Last time I talked to the Dropbox guys they said kevent isn't good enough. 
Something about tracking a large tree is too difficult. Similar to what the dev 
of lsync said. (rsync daemon that initiaties transfers when it noticies files 
changing).

I smell bovine feces.
___
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: opera 12.12

[Mark Felder]

On Wed, 19 Dec 2012 22:04:49 +0100
Matthieu Volat  wrote:

> 2. (maybe) use symlinks to trick opera to use the new one and hope that there 
> is enough compatibility between both version of icu

Isnt this what /etc/libmap.conf is for? You should NEVER use symlinks.

http://www.freebsd.org/cgi/man.cgi?query=libmap.conf
___
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: Dropbox on FreeBSD

[Mark Felder]

On Fri, 21 Dec 2012 19:27:24 +0200
Mikhail Kupchik  wrote:

> Maybe a FUSE filesystem, kind of "filtering layer" above real 
> filesystem, can be used to track all changes in the large tree without 
> consuming kernel resources for each subdirectory?

We'll probably have to wait for FUSE to stabilize in FreeBSD first. I tend to 
not trust much of anything that wants FUSE these days because of the number of 
kernel panics it's caused. I know there's some significant work in progress, 
though.
___
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: Citrix

[Mark Felder]

On Sun, 30 Dec 2012 18:55:40 -0800
"jmdennis @dslextreme.com"  wrote:

> It would be nice to be able to use version 12.1 of the receiver.  I
> know you have to download it yourself but it expects an old version
> which can no longer be found.  It would be nice if you would put down
> where you can make changes so that you can build a more recent
> version.  It does have to go into /etc/make.conf to make changes but
> that if for a certification.  I know I need this to connect to my work
> so will go back to Linux until I can get a work around for this.
> 

Can you provide a bit more details on what your problem is? Are you
talking about the Citrix Receiver/ICA software? (net/citrix_ica)

If you need that updated to 12.1 I'm sure we can assist you. There clearly 
aren't many users of it on FreeBSD so that's why it's still version 10.6.

Please let us know what we can do to help! :)
___
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: Monitoring a switch

[Mark Felder]

On Tue, 08 Jan 2013 12:30:25 -0600, Andrea Venturoli   
wrote:



Hello.
I'm looking for some software which can monitor a SNMP-enabled switch.
Sure I can use Cacti to monitor bandwidth of every single port... or  
Nagios to warn me if some port gets some defined amount of traffic for a  
defined amount of time...


I was wondering though, if there was some more specific tool which might  
be faster to setup and would do some magic automatically, like computing  
the total traffic flowing through, identifying bottlenecks, etc...




Observium might be something worth looking into. They generally want you  
to run the the latest commit to their svn repo, so I wouldn't recommend  
the version in ports right now.


http://www.observium.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: How to launch services that do not fork to background using the rc infrastructure?

[Mark Felder]

Also look at the wrapper script used by net/socat. There are a few ports  
using that.

___
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: The upcoming phpMyAdmin 4.0.0

[Mark Felder]

If upstream is abandoning 3.x (which they should, it's full of security  
holes so 4.x better be an improvement) then I would say just bump it to  
4.x and don't make a separate phpMyAdmin port.

___
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: Is there an easy way to find out which port loads which library?

[Mark Felder]

On Sun, 17 Feb 2013 15:56:26 -0600, Chris Rees  wrote:


Most shells won't allow an argument list that long.
% find /usr/ports -depth 3 -name pkg-plist -exec grep libfoobar.so \{} \;
has been shown to be faster than hacking around arg list limits with  
echo |

xargs.


The following may prove to be even faster as it fills the shell argument  
list as full as possible for each execution of grep.


% find /usr/ports -depth 3 -name pkg-plist -exec grep libfoobar.so \{} +

(notice the + at the end)

It's something I picked up from here: http://www.etalabs.net/sh_tricks.html

___
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: FreeBSD port for redirecting printer

[Mark Felder]

On Wed, 27 Feb 2013 05:56:47 -0600, Matthias Apitz   
wrote:



another issue, how do you print an UTF-8 encoded text file, containing
for example Hebrew and Greek? With CUPS' lpr(1) you just say:


You can print almost any file format using the base system lpr and  
print/apsfilter. You really don't need CUPS to print -- even if the  
destination printer doesn't understand postscript.


If someone can provide me with this UTF-8 encoded text file I'll prove  
whether or not it prints it.

___
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: FreeBSD port for redirecting printer

[Mark Felder]

On Fri, 01 Mar 2013 06:51:53 -0600, Matthias Apitz   
wrote:



I do not believe that this will work for UTF-8 coded data, but you might
convince me (hopefully);


If I simply do

# lpr CUPS-UTF-8.txt

I end up with an exact replica of the data within that file -- noise.


If I open CUPS-UTF-8.txt in gedit and print via lpr it works great.

I guess it's been a while since I've played with anything in UTF-8 and  
completely forgot how UTF-8 really looks when you aren't using  
Unicode-aware applications.

___
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 am i doing wrong

[Mark Felder]

On Fri, Apr 5, 2013, at 9:39, Bjorn Carlsson wrote:
> > [root@kaguzi /home/bc]# pkg upgrade
> Updating repository catalogue
> Repository catalogue is up-to-date, no need to fetch fresh copy
> Nothing to do

You're running your own private package repository, right? Unfortunately
there is no public one available yet. So you either have to run your own
or just build from ports like usual, but have WITH_PKGNG=YES in
/etc/make.conf.
___
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's PHP port incomplete; missing ftp_ssl_connect function

[Mark Felder]

I'm hoping someone out there can help come up with a solution or a clever  
patch because right now the only alternative I see is an extremely painful  
patch to the ports tree that I'd never be able to successfully maintain at  
my place of employment.


The problem is that the way FreeBSD handles PHP -- complete modularization  
-- breaks the FTP module. The FTP module cannot be built with support for  
FTPS unless it is built statically into PHP along with OpenSSL. You can  
test this yourself by running the following command:


php -r 'if(function_exists('ftp_ssl_connect')) {echo "ftp_ssl_connect  
exists\n";} else {echo "ftp_ssl_connect does not exist\n";}'



As documented here: http://php.net/manual/en/function.ftp-ssl-connect.php


Note: Why this function may not exist
ftp_ssl_connect() is only available if both the ftp module and the  
OpenSSL
support is built statically into php, this means that on Windows this 
function will be undefined in the official PHP builds. To make this  
functionavailable on Windows you must compile your own PHP binaries.


If you look at Debian and Redhat Linux distros there is no php5-ftp or  
php5-openssl package. It's statically built into the base php5 package.  
Even Gentoo appears to be doing it right because the ebuild just lets you  
choose what options you want and it compiles the entire thing statically.


http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-lang/php/php-5.3.23.ebuild?view=markup

I've already submitted a PR, but I'd like some further input from the  
community. I'm really in a sticky situation here because we were forced to  
require FTPS everywhere and now things like Wordpress' self-upgrading  
capability is broken. If we could flip everyone to SFTP I'd gladly do it,  
but there are too many obstacles in the way for that to become a reality.



In short, is anyone out there interested in trying to figure out how to  
get the FTP module to build with the SSL capability?




(Vinnie here has the same reaction I do:  
https://bugs.php.net/bug.php?id=38951)

___
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: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function

[Mark Felder]

On Wed, 08 May 2013 07:37:02 -0500, Alex Dupre  wrote:



Actually you can get a ssl-enabled php5-ftp in a very simple way: build
php5-ftp after php5-openssl.
Said so, such behavior should be harmonized, probably you could get a
ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch.


That makes total sense but I never experimented further after seeing the  
"official" PHP response saying you have to do it statically and seeing  
what other Linux distros were doing.


However, this would still exclude cleanroom package building environments  
like poudriere or tinderbox, correct? We're deploying our software to our  
servers with pkgng packages and building with poudriere. I guess if you  
make php5-ftp have a build option for SSL that pulls in php5-openssl as a  
build dependency this might work, right?


I really hope this is a simpler solution than I thought!
___
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: The vim port needs a refresh

[Mark Felder]

On Fri, 24 May 2013 16:23:18 -0500, Kenta Suzumoto  wrote:

- It fetches almost 700 patches from what seems like a dial-up  
connection in AUSTRALIA.


Australia's deploying fiber, so joke's on you!

But honestly this is horrible. I'm sitting at my desk at a well-peered ISP  
with plenty of bandwidth and low, low latency and these patches are taking  
forever. Someone should just add a pre-fetch routine that downloads the  
first 1000 patches in a tarball, puts them in distfiles, and they well all  
be verified and the remaining few be fetched normally.


Someone should teach upstream a serious lesson about versioning. Maybe  
someone just needs to fork vim and tag releases on github so we can  
actually have a sane upstream.


Good grief!
___
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 was the ventrilo-server port removed?

[Mark Felder]

On Tue, Jun 4, 2013, at 16:34, Bob Willcox wrote:
> I just noticed that the port for audio/ventrilo-server has been removed. 
> The
> 'depricated because' reason says "No more public distfiles", yet as far
> as I
> can tell the distfile for the freebsd version is still available from
> www.ventrilo.com. It requires a manual download as you have to accept the
> license agreement, but I don't think that has changed from when I first
> downloaded it.
> 
> So, anyone know if there some other reason for its removal?
> 

I don't know what the policy is because there are other ports that have
restricted distfiles. Maybe it was just unmaintained? You could submit a
patch to make it interactive and display a message about manually
fetching the distfile. 
___
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: [CFH] FreeBSD 10 and ports

[Mark Felder]

As someone familiar with doing ports but can't write a lick of code
beyond some basic scripting or Perl -- how can I help? Are there
guidelines for this project? Should we take known broken ports and test
them against different versions of GCC and CLANG in the ports tree until
we find one that works?
___
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: Owncloud port update

[Mark Felder]

On Tue, 11 Jun 2013 12:33:57 -0500, Loïc BLOT  
 wrote:



Hi all,
i'm not the maintainer, but i send the pr since owncloud 5.0.0 to
upgrade the port.
The current port version is 5.0.5, which has many critical issues
(security & stability).
Since 3 days the the 5.0.7 is out. I have also sent a 5.0.6 patch 1
month ago and the maintener seems to not be there.
How can we speed up the port update process ? (i use 5.0.6 and now 5.0.7
in production and all works perfect).


file a PR asking for maintainership. I'm guessing kevlo@ is busy or not  
using Owncloud very much anymore


Active port maintainers are certainly desired to keep our endusers happy  
and safe.

___
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: net-mgmt/cflowd 2.1.b1 build failure

[Mark Felder]

I just did a build of this in poudriere with no issues. I'd guess you
have a dirty build environment. Can you post the contents of your
make.conf?


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: Proposal: further OptionsNG improvements

[Mark Felder]

So we just got done porting most of the tree to a new options syntax and  
now we want to change it 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: OptionsNG and defaults

[Mark Felder]

On Thu, 20 Jun 2013 09:52:35 -0500, Boris Samorodov  wrote:


OK, let's say I as a maintainer _want_ to not install examples by
default. The reason _why_ is out of a scope here. Do you say that
I do not have a possibility to switch EXAMPLES option off by default?


Edit your port to be completely void of the word "EXAMPLES"

The only way the EXAMPLES are being installed is if you have something  
like this in your port:


.if ${PORT_OPTIONS:MEXAMPLES}
@${MKDIR} ${EXAMPLESDIR}
${INSTALL_DATA} ${WRKSRC}/examples/* ${EXAMPLESDIR}
.endif


Just don't put that in your port and everything will work as expected.  
There is no magic here; there is no possible way for the port to  
automatically detect and install EXAMPLES. It's up to you as the  
maintainer to define what the EXAMPLES are in order for them to be  
installable.

___
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: pkgng seems to be out of date?

[Mark Felder]

On Tue, Jun 25, 2013, at 7:50, Ben Laurie wrote:
> 
> Hmmm. pkg updating doesn't actually show the relevant 20130206 entry -
> so not actually useful.
>

pkg updating literally just reads /usr/ports/UPDATING... is your ports
tree up to date? Did the committer of this tcl incident commit the
changes before touching UPDATING and you're caught inbetween? I suppose
this could use a bit of investigation...
___
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"

CFT: dovecot2-pigeonhole (sieve) users

[Mark Felder]

Hi all,

I'm hoping someone reading this list is a Dovecot2 user that can spend a  
few minutes testing a patch to the pigeonhole port.


Basically, there's a conflict between mail/dovecot2 and  
mail/dovecot2-pigeonhole that breaks the ability to use pkgng with those  
ports. What I need from you is to test this patch and let me know if you  
experience any problems with utilizing pigeonhole (sieve). It should be an  
instantaneous result: either it works and lets you make changes, or it  
doesn't. My brief testing proved that it binds to the correct port and  
responds, but I don't have a proper test environment to go further.


The main difference is that the dovecot2-pigeonhole port could now be  
installed in a PREFIX if needed and its docs and headers are in their own  
directories: %%PREFIX%%/share/doc/dovecot-pigeonhole/ and  
%%PREFIX%%/lib/dovecot-2.2-pigeonhole/sieve/


The attached is an svn diff. Your feedback would be much appreciated.


Thanks

pigeonhole.diff
Description: Binary data
___
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: Is there a problem with categ/newport-0 ?

[Mark Felder]

On Wed, 03 Jul 2013 15:15:25 -0500, Marcel Bonnet   
wrote:




Is it mandatory to drop the MAJOR_VERSION from the port suffix name? Is  
it

optional? Is it mandatory to follow the upstream convention?


We have plenty of ports with multiple major versions in the ports tree.  
Look at MySQL, Postgres, PHP, Perl, phpMyAdmin, etc etc.


However, just because port doesn't have a version number in its name  
doesn't mean the shared library name include directory must be without. I  
don't believe you'll be breaking any conventions by installing the  
libraries in a way upstream prefers.

___
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: Ardour 3.x

[Mark Felder]

On Wed, 10 Jul 2013 17:43:50 -0500, Super Bisquit   
wrote:



Has it been accepted into the ports tree as of yet along with the
dependencies?



Do you have a list of PRs?
___
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: Latest snapshot

[Mark Felder]

I can confirm, I'm hitting this too. I've worked around it by using svn  
for the moment.

___
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: Port system changes.

[Mark Felder]

Recently MAKE_JOBS was enabled by default in ports. I don't have any
further details than that at the moment.
___
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: portmaster WITH_PKGNG and cpan

[Mark Felder]

On Thu, Jul 18, 2013, at 5:16, Marko Cupać wrote:
> 
> Is there a solution for this?
>

I'm not sure, but we can certainly get that extension added to ports.
Would you be willing to test the port for me? We have RT here, but we
don't use that extension...
___
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: portmaster WITH_PKGNG and cpan

[Mark Felder]

On Thu, Jul 18, 2013, at 7:59, Marko Cupać wrote:
> 
> If I remember well, I had all the ports installed back in days of
> pkg_tools,
> and converted pkg_* database to pkg with pkg2ng. Do you say that, if I
> had pkg
> from the start, it wouldn't even register in the pkg database? If so, how
> are people supposed to keep track of installed cpan modules in pkg era?
> 

I'm honestly not sure how that's supposed to be handled... The whole
"bsdcpan" thing seemed like a hack to me, and I've had problems with it
during OS upgrades over the years...

Marko, what version of RT are you running? I see that with versions
older than 4.0.8 you're supposed to "patch" RT with an included diff to
add some functionality. This violates guidelines though, as it will
break RT in the eyes of pkg and it won't properly get uninstalled
because of a checksum mismatch. I plan on making this port require
>4.0.8. I hope that's OK.
___
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: portmaster WITH_PKGNG and cpan

[Mark Felder]

Marko, can you try this?

http://feld.me/freebsd/rt-extension-mandatoryontransition.tar.gz


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: r253680 in CURRENT breaks GH ports and maybe others

[Mark Felder]

On Wed, Jul 31, 2013, at 8:05, Nikolai Lifanov wrote:
> 
> I fully agree. We already checksum the *distfiles*.
> It shouldn't be important what the source is.
> 
> Are there any objections to adding --no-verify-peer to FETCH_ARGS across 
> the board?
> 

Won't that break fetch for users whose fetch doesn't support
--no-verify-peer?

# fetch --no-verify-peer https://foo.com/bar.tar.gz
fetch: illegal option -- -
___
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: KDE4 woes

[Mark Felder]

On Thu, Aug 1, 2013, at 6:35, Stan Gammons wrote:
> I decided to start from scratch and reinstalled FreeBSD 9.1 RELEASE, ran
> freebsd-update, fetched the latest ports tree with portsnap, installed
> portmanager, installed xorg, then attempted to install KDE4 using
> "portmaster x11/kde4" from /usr/ports.  After going through all of the
> options and only selecting pulseaudio and SDL for the audio options on
> the sound related packages, the build starts and bombs with errors that
> it's unable to update several of the KDE apps. Seems like KDE PIM was one
> of several apps that prompted the errors.  So, it looks the forwarder I
> go, the behinder I get :(   Other than give up, does anyone have any
> suggestions?
> 

I would like to try to reproduce this. Can you tar up /var/db/ports and
put it somewhere so I can download it? 

Also, have you made any make.conf changes?


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: KDE4 woes

[Mark Felder]

Sorry this weekend was quite busy. I have the build running now.
___
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: poudriere issue with www/apache22

[Mark Felder]

I use that module without any issues and we build in poudriere. It looks
like you're having a fetch error -- can you go to www/apache22 and do
"make fetch" and see what happens?


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: sysutils/fusefs-ntfs & fusefs_enable="YES"

[Mark Felder]

On Wed, Aug 21, 2013, at 17:09, RW wrote:
> On Wed, 21 Aug 2013 23:44:41 +0200
> Dominic Fandrey wrote:
> 
> > On 21/08/2013 23:39, RW wrote:
> > > The README.FreeBSD file for sysutils/fusefs-ntfs and several howtos
> > > suggest adding the line:
> > > 
> > > fusefs_enable="YES"
> > > 
> > > to rc.conf, but as far as I can see this doesn't affect anything
> > > since the port doesn't install an rc.d file. I would have expected
> > > such a file to load the fuse kernel module which I'm having to load
> > > myself.
> > 
> > The file is there. fusefs-kmod
> 
> I see what's happened. Earlier in the year,against my better judgement,
> I move to CURRENT in futile attempt to make intel KMS work. It looks
> like fuse has been moved into the base system, but /etc/rc.d/ hasn't yet
> been updated to reflect that. 
>

There isn't an /etc/rc.d/ for every kernel module. If you want to use
fuse on FreeBSD 10 and later just put fuse_load="YES" in loader.conf.
The rc.d script in the port was just a nice courtesy. I don't think it's
likely we'll see an /etc/rc.d/fuse script appear in the base system.
___
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: sysutils/fusefs-ntfs & fusefs_enable="YES"

[Mark Felder]

On Thu, Aug 22, 2013, at 8:16, RW wrote:
> On Thu, 22 Aug 2013 06:41:33 -0500
> Mark Felder wrote:
> 
> > On Wed, Aug 21, 2013, at 17:09, RW wrote:
> 
> > > I see what's happened. Earlier in the year,against my better
> > > judgement, I move to CURRENT in futile attempt to make intel KMS
> > > work. It looks like fuse has been moved into the base system,
> > > but /etc/rc.d/ hasn't yet been updated to reflect that. 
> > >
> > 
> > There isn't an /etc/rc.d/ for every kernel module. If you want to use
> > fuse on FreeBSD 10 and later just put fuse_load="YES" in loader.conf.
> > The rc.d script in the port was just a nice courtesy. I don't think
> > it's likely we'll see an /etc/rc.d/fuse script appear in the base
> > system.
> 
> I have added it to loader.conf, but the reason I brought it up was that
> I thought the documentation might be out of date, which appears to be
> the case. 
> 
> If nothing's been decided I can't really submit a documentation
> patch.
> 
> If anyone's interested the relevant files are:
> 
> sysutils/ntfsprogs/files/README.FreeBSD
> sysutils/fusefs-ntfs/files/README.FreeBSD
> 

I forgot about the READMEs that come with those ports. We might want to
mention FreeBSD 10+ specific setup there I guess.
___
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: Perl port to select in make.conf

[Mark Felder]

On Sun, Sep 1, 2013, at 13:31, Dmitry Morozovsky wrote:
> Dear colleagues,
> 
> which variable should be defined in make.conf to switch from current 5.14
> to, 
> say, 5.16 (for poudriere package building)? 
> 
> Naive 
> 
> PERL_VER=5.16
> 
> does not seem to work, and I want to not chase minor version changes.
> 

PERL_PORT

example:

PERL_PORT=perl5.14
___
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: Perl port to select in make.conf

[Mark Felder]

On Tue, Sep 3, 2013, at 8:59, Dmitry Morozovsky wrote:
> On Tue, 3 Sep 2013, Mark Felder wrote:
> 
> > > which variable should be defined in make.conf to switch from current 5.14
> > > to, 
> > > say, 5.16 (for poudriere package building)? 
> > > 
> > > Naive 
> > > 
> > > PERL_VER=5.16
> > > 
> > > does not seem to work, and I want to not chase minor version changes.
> > > 
> > 
> > PERL_PORT
> > 
> > example:
> > 
> > PERL_PORT=perl5.14
> 
> Unfortunately, this variable seems to be slave to PERL_VERSION, not vice
> versa.
> 

I've been using solely PERL_PORT in my poudriere make.conf for about...
8 months now with no issues. I get exactly the perl train I want and all
ports are built properly against the version I want. Can you provide any
details indicating this method is incorrect?
___
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: Perl port to select in make.conf

[Mark Felder]

Please provide the entire poudriere build log. There's something fishy
going on here; I have never had this problem.

Here's my build log:

http://pkg.feld.me/logs/bulk/91amd64-default/latest-per-pkg/help2man-1.43.3.log


I'll even build it with a different PERL_PORT if you'd like to see that.
___
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: Perl port to select in make.conf

[Mark Felder]

Build happening now. Everything is getting rebuilt against 5.16

http://pkg.feld.me/logs/bulk/head-default/2013-09-03_13h33m40s/
___
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: Perl port to select in make.conf

[Mark Felder]

I've recreated this issue now. Not all ports seem to be picking up the
new version correctly. 

I've raised this issue with the ports team and will report back when I
have any news.
___
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: FreeBSD Port: zoneminder-1.25.0_2

[Mark Felder]

I've also been in contact with upstream and they've been looking at our
patches. It sounds like a lot has changed for 1.26.x and they're very
much interested in making sure it works with CLANG, too.

FYI, NetBSD fixed CLANG builds earlier this year

http://mail-index.netbsd.org/pkgsrc-changes/2013/03/24/msg086668.html

___
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: [patch] audio/mumble: urgent unbreak

[Mark Felder]

On Tue, Oct 8, 2013, at 13:05, David Demelier wrote:
> Hello folks,
> 
> Sorry to ask you a second time for a maintainer timeout but it's
> critical because audio/mumble is unusable currently because of a CELT
> detection failure.
> 
> Two patches were sent over PR, one from me [1] and one from Natacha
> Porté. [2] Both are working, I think her is a bit better as it won't
> break if the standalone celt library install the same name.
> 
> Please commit the one you find the best but as soon as possible
> because you just *can't* speak / hear anything, which is pretty
> useless on a VoIP application :-).
> 

Natacha's solution is the right way because there may be a conflict with
the celt ports in the future. In fact, it used to be done this way as
there was a conflict in the past. I'm not sure how/why this broke but
I'll take this PR and get this sorted.
___
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: stagedir vs. jail

[Mark Felder]

Do I understand this situation correctly:

Users are having issues with building/installing packages with STAGEDIR
enabled in lightweight jails that use symlinks to share parts of the
base system between many jails to make it easier to upgrade the jails
and avoid duplication/wasted disk space? It seems that the handbook and
ezjails may both replicate this behavior.

http://www.freebsd.org/doc/handbook/jails-application.html

If this is correct, the only workaround may be for you to use a private
package repository constructed by poudriere and to not actually build
your packages within the jails you intend to use them in. The types of
jails you are using are certainly a supported method for running jails,
but I can see the severe limitations it imposes on the newer package
building method which is designed to ensure packages are built as
accurately and reliably as possible. Maybe bapt & co can find a
workaround for this, but this does sound like an edge case. 

Please keep in mind that there are some growing pains as the ports team
attempts to mature packages on FreeBSD so we can one day go from 90%
users build from ports and only 10% using packages to a reality where
90% of the users are able to use packages and only 10% have to build
from ports.

I should note that I successfully run these types of jails but I run
poudriere from the host to have private package repositories. It makes
it very easy to pop into a jail and run "pkg upgrade" and instantly the
jail is updated and I can restart services or quickly restart the entire
jail.
___
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: news/nzbget updated

[Mark Felder]

On Tue, Oct 15, 2013, at 13:52, Nicolas Raspail wrote:
> Hi
> 
> I just have seen that the news/nzbget port has been updated (fixing bug 
> ports/182867). So I think someone can close the bugs ports/177669 and 
> ports/180832 .
> 
> I have noted some things in the Makefile :
>* I don't see any reference to python, but the new version 11.0 
> provides postinstall scripts written in Python
> 
>* the configure argument "--enable-sigchld-handler " is still 
> present, but from the developer, "since revision r712 (before the 
> release of the 11.0 version) --enable-sigchld-handler shouldn't be 
> necessary anymore on 64-Bit BSD. But instead --disable-sigchld-handler 
> is needed on 32-Bit BSD". I have removed this line from the Makefile, 
> recompile the port, install it, download a file and the postinstall 
> scripts terminate successfully.
> 
>* if you copy /usr/local/share/nzbget/nzbget.conf to 
> /usr/local/etc/nzbget.conf, WebDir and ConfigTemplate will be defined 
> with correct paths
> 
>* Maybe we can add two options to install unrar/rar and 7zip
> 

I've started using it recently and noticed these issues. I'll look into
those PRs.
___
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: news/nzbget updated

[Mark Felder]

I have just submitted a PR regarding these issues.
___
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: Stage and /var ?

[Mark Felder]

On Thu, Oct 31, 2013, at 9:20, Thierry Thomas wrote:
> 
> Hello,
> 
> How should we stagify ports writing out of their $PREFIX for
> good reasons, e.g. a statedir like /var/foo/$PORTNAME.
> 
> I don't like the idea of $PREFIX/var, and prefer the real /var.
> 

Can you give an example? If it's in /var/db or /var/run it's probably
OK, but otherwise it might be breaking hier(7)...
___
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: Problems with "spaces" in file names during stage-qa

[Mark Felder]

On Mon, Nov 4, 2013, at 12:27, Danilo E. Gondolfo wrote:
> On 11/03/13 20:56, Matthias Andree wrote:
> > Am 03.11.2013 14:16, schrieb Danilo E. Gondolfo:
> >> Hello folks,
> >>
> >>  I've had some problems with blank chars in file names during stage-qa.
> >>
> >> Problems like that:
> >>
> >> > Running Q/A tests (stage-qa)
> >> sed:
> >> /home/barba/Sources/freebsd-working/ports/games/lincity-ng/work/stage/usr/local/share/lincity-ng/music/01:
> >> No such file or directory
> >> sed: -: No such file or directory
> >> sed: pronobozo: No such file or directory
> >> sed: -: No such file or directory
> >> sed: lincity.ogg: No such file or directory
> >> sed:
> >> /home/barba/Sources/freebsd-working/ports/games/lincity-ng/work/stage/usr/local/share/lincity-ng/music/03:
> >> No such file or directory
> >> sed: -: No such file or directory
> >> sed: Robert: No such file or directory
> >> sed: van: No such file or directory
> >> sed: Herk: No such file or directory
> >> sed: -: No such file or directory
> >> sed: Architectural: No such file or directory
> >> sed: Contemplations.ogg: No such file or directory
> >> sed:
> >> /home/barba/Sources/freebsd-working/ports/games/lincity-ng/work/stage/usr/local/share/lincity-ng/music/02:
> >> No such file or directory
> >> sed: -: No such file or directory
> >> sed: Robert: No such file or directory
> >> sed: van: No such file or directory
> >> sed: Herk: No such file or directory
> >> sed: -: No such file or directory
> >> sed: City: No such file or directory
> >> sed: Blues.ogg: No such file or directory
> >>
> >>
> >> I've fixed this with the attached patch. What do you think?
> > Thanks for taking a stab at this.
> >
> > However, the patch goes only halfway. If we really want to proof it
> > against blanks, we need to tweak IFS - and that would still not proof it
> > against tabs or line feeds in filenames.
> >
> > As reference, I found David A. Wheeler's article most elucidating:
> > 
> >
> > Would you like to take another, more robust, stab at the script?
> Tweak IFS is smarter :D
> It reduced my patch to this:
> 
> Index: qa.sh
> ===
> --- qa.sh(revision 332718)
> +++ qa.sh(working copy)
> @@ -110,6 +110,7 @@
>  ret=0
>  cd ${STAGEDIR}
>  for check in ${checks}; do
> +IFS="$(printf '\n\t')"
>  ${check} || ret=1
>  done
> 
> But the problem with other blanks remains... =/
> 

This is at least a step in the right direction -- it fixes the hundreds
of errors when I build my multimedia/plexmediaserver port. Sadly, it
looks like nobody has a real solution for 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: Anyone looked at making a port for https://www.eff.org/https-everywhere ?

[Mark Felder]

On Thu, Nov 7, 2013, at 7:34, Julian H. Stacey wrote:
> Has anyone looked at making a ports wrapper for 
> https://www.eff.org/https-everywhere
> ?
> 
> Sources: 
> https://www.eff.org/https-everywhere/development
> 
> PS on current/ports, grep https-everywhere shows nothing,
> grep www.eff.org shows just security/switzerland/, port creator
> Alexey Dokuchaev  added to CC.
> 

Do we actually have ports for other browser plugins (besides
flash/java)? 
___
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 default version system

[Mark Felder]

On Nov 8, 2013, at 20:34, Allan Jude  wrote:

> and change the default version of php from lang/php5 to lang/php53

Wouldn't that need to be set to lang/php54 as default?
___
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 default version system

[Mark Felder]

On Nov 9, 2013, at 11:09, Allan Jude  wrote:

> On 2013-11-09 11:00, Mark Felder wrote:
>> On Nov 8, 2013, at 20:34, Allan Jude  wrote:
>> 
>>> and change the default version of php from lang/php5 to lang/php53
>> Wouldn't that need to be set to lang/php54 as default?
> The port for php 5.4 is called lang/php5 
> 
> confusingly, the default port for php is always lang/php5, and every
> other version is lang/php53 or lang/php55 etc. so when the default gets
> bumped, php 5.4 will become lang/php54 and php5.5 will change from
> lang/php55 to lang/php5
> 

Maybe this should be coordinated with the move of lang/php5 to lang/php54 then? 
PHP 5.3 is EOL as of March and only receives critical security fixes now. It 
would also unexpectedly downgrade existing users to 5.3 in some scenarios.

___
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 default version system

[Mark Felder]

On Nov 9, 2013, at 11:47, Florian Smeets  wrote:

> On reading this a second time it became clear to me that he is not
> suggesting changing the default PHP to 5.3, it was merely an example
> what users can do if they build their own packages.

Yep. My mistake!
___
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: NfSen Port PATCH

[Mark Felder]

On Nov 13, 2013, at 12:27, Chad Gross  wrote:

> I found an issue with the nfsen port Makefile. It is not properly
> configured to expand the %%PORTNAME%% variable used when generating the
> nfsen config file.
> 
> 
> For example, the config that is installed shows this:
> 
> $VARDIR="${BASEDIR}/var/%%PORTNAME%%";
> 
> 
> When it should be this:
> 
> $VARDIR="${BASEDIR}/var/nfsen";
> 
> I have attached the patch, but also included it in-line below. I emailed
> the maintainer, but hadn't heard a response so figured I would send it here
> just in case.
> 
> 
> --- Makefile2013-11-03 12:31:00.0 -0500
> 
> +++ Makefile.new2013-11-03 12:30:51.0 -0500
> 
> @@ -37,6 +37,7 @@
> 
> SUB_LIST+= "PORTVERSION=${PORTVERSION}"
> 
> SUB_LIST+= "PREFIX=${PREFIX}"
> 
> SUB_LIST+= "WWWDIR=${WWWDIR}"
> 
> +SUB_LIST+= "PORTNAME=${PORTNAME}"
> 
> 
> 
> NO_STAGE=  yes
> 
> post-patch:
> 
> 
> Thanks,
> 

Thanks for catching this. I’m not sure how I missed this when I rewrote the 
port… I definitely tested clean installs, but I must have provided my own 
configs



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Solving PORTNAME/PORTREVISION/DISTNAME/DISTVERSION mess

[Mark Felder]

On Wed, Jan 8, 2014, at 8:10, Big Lebowski wrote:
> Hi,
> 
> I am working on updating databases/postgresql-libpqxx to use sources with
> version 4.0.1. The current PORTVERSION is 4.0, and the 4.0.1 sources are
> not bumping the lib version, are not changing the lib api version, but
> instead, have compile bug fixes. That suggest using PORTREVISION at 1, to
> make the PORTVERSION 4.0_1, but then I cant download proper sources with
> 4.0.1 suffix. I've tried different combinations of
> DISTNAME/DISTVERSION/PORTVERSION/PORTREVISION but cant get it working and
> at the same time being processed with portlint not yelling at me for
> using
> above in cominations, so what would be proper solution to that problem?
> 
> The closes to working solution I got was while using these:
> 
> PORTNAME=   libpqxx
> PORTVERSION=4.0
> PORTREVISION=   1
> CATEGORIES= databases
> MASTER_SITES=   http://pqxx.org/download/software/libpqxx/
> PKGNAMEPREFIX=  postgresql-
> DISTNAME=   ${PORTNAME}-${PORTVERSION}.${PORTREVISION}
> DIST_SUBDIR=postgresql
> 
> but then the portlint screams with:
> 
> WARN: Makefile: only one MASTER_SITE configured.  Consider adding
> additional mirrors.
> FATAL: Makefile: DISTNAME contains a reference to PORTREVISION.  You
> should
> only be using PORTVERSION
> WARN: Makefile: Consider defining LICENSE.
> 1 fatal error and 2 warnings found.
>

I don't understand what you're trying to accomplish, but please see my
patch:

https://feld.me/freebsd/libpqxx.diff

I had to replace their "split-config" script with the one from 4.0
because they apparently rewrote it in python and it does not work in our
build environment. I didn't feel like debugging this further; this was
the easy fix.
___
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: FreeBSD Port: unifi4-4.2.0

[Mark Felder]

On Tue, Mar 24, 2015, at 04:50, Ruud Boon wrote:
> Hi,
> 
> I’m wondering. Are there any plans to upgrade the unifi port to the
> latest 4.6.0 version?
> 
> All the best.
> Ruud
> 

I had not noticed 4.6.0 is out. I'll definitely get the port updated,
but I don't use unifi4 anywhere right now. I've been on 3.x because of
some horror stories... :-)
___
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: I want to tell pkg to just forget about an installed port

[Mark Felder]

On Fri, Mar 27, 2015, at 08:41, Richard Kuhns wrote:
> Hello,
> 
> How can I tell pkg to completely forget about an installed port, without
> deleting it?
> 
> Specifically, I installed net-mgmt/observium a couple of months ago. I
> really like it and have paid for a subscription so what is currently on
> disk is mostly *not* what was installed by the port, so I'd like to tell
> pkg to forget about it.
> 

Why not just move /usr/local/www/observium out of the way, pkg delete
observium, and then move it back?
___
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: Pourdriere produces faulty build results due to bsd.openssl.mk bug

[Mark Felder]

On Wed, Apr 1, 2015, at 16:21, Bryan Drewery wrote:
> On 4/1/2015 3:59 PM, Yuri wrote:
> > I found that packages produced by poudriere likely link with base
> > openssl, while port make likely links with the port openssl.
> > This is because of the lines in bsd.openssl.mk which check for the
> > presence of openssl shared library and headers under PREFIX, and set
> > WITH_OPENSSL_BASE when they aren't present. In case of port make files
> > are likely present, and in case of poudriere build files are likely not
> > present.
> > 
> > Example is ftp/curl (with GSSAPI=NONE,  OPENSSL=yes options). *Poudriere
> > produces curl library, that causes VirtualBox to break* due to the
> > openssl base vs. port conflicts. See recent emulation@ ML threads. Port
> > make produces curl library that works fine with VirtualBox.
> > 
> > I think both WITH_OPENSSL_BASE and WITH_OPENSSL_PORT should be retired,
> > and code checking file presence also should be removed, and all ports
> > should be made to build with an openssl port instead. Ports should never
> > use base OpenSSL.
> > 
> > Only <100 ports touch WITH_OPENSSL_... variables. Somebody who is able
> > to make such decisions and has the commit bit should bit should look
> > into this. Otherwise, massively faulty package repositories are produces.
> > 
> > Yuri
> 
> I've wanted this for a long time. I think we should just do it.
> 

What are the risks of something linking to OpenSSL in ports also
requiring something from base which in turn... links in OpenSSL from
base?
___
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: is it safe to run net/haproxy as root?

[Mark Felder]

On Thu, Apr 9, 2015, at 08:26, Mark Martinec wrote:
> 
> Perhaps the haproxy port maintainer can be persuaded to assign
> some account entry for this purpose.
> 

This wouldn't be a perfect solution. If you're going to be proxying port
80 and 443 you need to initially run as root, but perhaps by default in
the config file we could drop privs to the haproxy user?

Sounds like we need some better documentation on best practices, too.
___
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"